If you need to modify one or more properties for an IBM® Business Automation
Workflow data source, or you find that your initial
configuration is incorrect for an Oracle data source, you must use the BPMConfig
command to make the required updates. You cannot make the updates using the administrative
console.
Before you begin
Before changing any data source information, gracefully shut
down all JVMs that are associated with the deployment environment
to ensure that no active distributed transactions remain. If you fail
to shut the JVMs down gracefully, it can result in unrecoverable pending
transactions and inconsistency in the database. To complete all active
transactions, you can run the WebSphere Application Server startServer command
with the -recovery parameter, which will recover
transactions and then shut down the server.Note: Modification of
the database .schema
property is not supported in
Business Automation Workflow.
Procedure
To update Business Automation Workflow data
sources:
- To update properties for a non-Oracle data source, complete the following steps:
- Run the following BPMConfig command to export the existing
configuration and generate a configuration properties
file:
BPMConfig -export -profile profile_name [-de deployment_environment_name]
If
there is only one deployment environment in the WebSphere cell, you can omit the
-de option. More information about the
BPMConfig command is
found in the topic
BPMConfig command-line utility.
-
Open the generated configuration properties file in a text editor or in the IBM Business Automation
Workflow Configuration
Editor. See "Configuring your environment with the IBM Business Automation
Workflow Configuration
editor."
- Edit one or more of the following properties in the configuration properties
file:
bpm.de.db.#.hostname=myHost
bpm.de.db.#.portNumber=myPortNumber
bpm.de.db.#.databaseName=myDatabase
- Save the file and run the following BPMConfig command:
BPMConfig -update -dataSource modified_properties_file
- To update properties for an Oracle data source, complete the following steps:
- Run the following BPMConfig command to export the existing
incorrect configuration and generate a configuration properties
file:
BPMConfig -export -profile profile_name [-de deployment_environment_name]
If
there is only one deployment environment in the WebSphere cell, you can omit the
-de option. More information about the
BPMConfig command is
found in the topic
BPMConfig command-line utility.
-
Open the generated configuration properties file in a text editor or in the IBM Business Automation
Workflow Configuration
Editor. See "Configuring your environment with the IBM Business Automation
Workflow Configuration
editor."
- Locate the following properties in the configuration properties file:
bpm.de.db.#.hostname=myHost
bpm.de.db.#.portNumber=myPortNumber
bpm.de.db.#.databaseName=serviceName
Note: If the Oracle database is accessed through the Single Client Access Name (SCAN) feature, then
the hostname
, portNumber
, and databaseName
properties are exported. The url
property (described in the following step) is only
exported if a non-SCAN URL is configured, in which case the hostname
and
portNumber
properties will not be set.
-
Replace those properties with the following properties:
bpm.de.db.#.hostname=
bpm.de.db.#.portNumber=
bpm.de.db.#.databaseName=systemID
bpm.de.db.#.url=myURL //For example: jdbc:oracle:thin:@myHost:myPortNumber:systemID
In
these properties, the
hostname
and
portNumber
properties are set
to empty strings because the
url
property is used instead. The value specified for
the
databaseName
property needs to be consistent with the service name or SID that
is specified for the
url
property.
Note: If you want to configure a SCAN URL, then
set the hostname
, portNumber
, and databaseName
properties but do not set the url
property. If you want to configure a non-SCAN
URL, then set the databaseName
and url
properties, but do not set
the hostname
and portNumber
properties. (You will need to add the
url
property when you switch from using a SCAN URL to a non-SCAN
URL.)
- Run the following BPMConfig command:
BPMConfig -update -dataSource modified_properties_file
What to do next
When you move the database to a new server, the data sources are generally updated using the
BPMConfig command. However, BPMConfig does not update the
transaction log data sources. The data sources for transaction logs must be updated in the admin
console or using wsadmin commands. The target database requires XA and same user
privilege. See Configuring XA transactions for your database type, for example: Configuring XA transactions for Oracle in a network environment on Windows.