Changing the database information for Process Server and the Performance Data Warehouse for the IBM Business Process Manager (BPM) products

Technote (FAQ)


Question

How do you change the database information for the Process Server and the Performance Data Warehouse Database?

Answer

The database connection information for the Process Server and the Performance Data Warehouse are saved under various configuration files. If you need to change the password for a database user, or you previously made a mistake entering the database information during the profile creation or cluster creation processes, this document provides instructions for changing the database information for the data source configuration, the 98Database.xml property file, and the bpm.standard.standalone.dbDesign or bpm.standard.nd.dbDesign file.


Note:

  • If the database is already created with a different user ID or schema name, you cannot use the same database. You can regenerate the necessary database scripts again using a database design tool and recreate the required database.
  • This document is applicable for Process Server and the Performance Data Warehouse database changes. This document is not applicable to the common database and other advanced component database because the database contains topology information in the database.
  • This document is not applicable to a V8.5.x deployment environment where properties from 98Database.xml file are no longer used . Also, the new features, such as the Enterprise Content Management (ECM) component, save security-related information in the common database so you can not reuse the populated common database with a new deployment environment.


The following topics are covered in this document:


Changing the JDBC data source using the Administrative Console:

  1. Open the WebSphere administrative console.

  2. Click Resources > JDBC > Data sources.

  3. Select the appropriate scope for your configuration.


    For example: Data source for a stand-alone IBM Business Process Manager Standard configuration:


  4. Select the data source that requires modification.


    Data source properties contain the database name, server name, and port number. The following screen shot shows the data source property values.




  5. Note the authentication alias name if you see authentication aliases configured in the security settings on the data source properties panel. The user ID and password that are defined for this Authentication Alias are used to connect to the database. The following screen shot shows the authentication alias values.




  6. Click JAAS - J2C authentication data under Related Items if you need to change the user ID and password. The following screen shot shows the JAAS - J2C authentication data panel:




  7. Change the messaging engine data store.


    If you change the messaging engine Java™ database connectivity (JDBC) data source, you have to make sure that the Schema name and Authentication alias values are correct for the messaging engine data store.
    1. In the WebSphere Administrative Console, click Service integration > Buses > bus_name > [Topology] Messaging engines > engine_name .

    2. Click Message Store. The following screen shot shows the data store properties for the messaging engine:




      On this panel, the Schema name value should match the schema names that are used when the database tables are created for the messaging engine data store. When you select the Create tables option, the selected SIB tables are created automatically during the messaging engine start up process. The user ID should have the required privileges.

  8. Save the changes.

  9. Synchronize the nodes if it is a Network Deployment environment.



Changing the 98Database property file

For BPM V 7.5.x and V 8.0.x, the database information from the 98Database.xml file is used to make a connection to the database. Depending on your configuration, the location of the 98Database.xml file is located under different configuration scope.

File location for the stand-alone profile


    Process Center

    PROFILE-DIR\config\cells\cell_name\nodes\node_name\servers\server_name\process-center\config\system

    Process Server

    PROFILE-DIR\config\cells\cell_name\nodes\node_name\servers\server_name\process-server\config\system

    Performance Data Warehouse

    PROFILE-DIR\config\cells\cell_name\nodes\node_name\servers\server_name\performance-data-warehouse\config\system


File location for a Network Deployment and a cluster environment
    • Modify the appropriate 98Database.xml file under the Deployment Manger profile config directory. Do not modify the configuration files under node profile; instead, use the node synchronization operation, which copy the files from deployment manager configuration to the node configuration.

    • If you have a clustered environment, you must update the 98Database.xml files at the cluster level and all cluster member-level 98Database.xml files. For example, modify the following files for all node and member combinations of the Process Center cluster:
      • DMGR-PROFILE-DIR\config\cells\cell_name\clusters\cluster_name\process-center\config\system\98Database.xml

      • DMGR-PROFILE-DIR\config\cells\cell_name\nodes\node_name\servers\member_name\process-center\config\system\98Database.xml

Best practice to c hange values in the 98Database.xml file.

To preserve the integrity of the 98Database.xml file you might have used the 100custom.xml file to override the values set in the 98Database.xml file. The 98Database.xml file is directly used by some of the components and using the 100custom.xml file to change the database is not always effective. Because the database changes are permanent changes, make a backup of the configuration files and change the desired values in the 98Database.xml file directly. Do not keep a backup of this file in the same directory because all the files under this directory are used to generate the TeamWorksConfiguration.running.xml file. You can visit Teamworks Config File Overview to learn more on how the Teamworks configuration is generated.

  1. Stop all the Java™ virtual machines (JVM), including the deployment manager, node agents and cluster members.
  2. Backup your configuration files in the profile_root/config directory where profile_root is the stand-alone profile directory or the deployment manger profile directory in a Network Deployment environment.

  3. Open the appropriate 98Database.xml file and locate the following lines:
    <databases>
    <default-database-name>default</default-database-name>
    <database type="default">
    <driver>com.ibm.db2.jcc.DB2Driver</driver>
    <url>jdbc:db2://localhost:50000/PCBPMDB</url>
    <user>db2admin</user>
    <schema></schema>
    <encrypted-password>fRRui5hb6t8xqhkn6Fcnw==</encrypted-password>
    <db-name>PCBPMDB</db-name>
    <storage-group></storage-group>
    </database>
    </databases>

  4. You can change the user name to match the change made to the data source.

  5. Follow the steps in the product documentation topic entitled, Encrypting passwords, to generate the encrypted password and replace the encrypted-password value.

  6. Save the changes.

  7. If the configuration changes were made to the network deployment environment, you must synchronize the nodes that contain Process Center, Process Server, or Performance Data Warehouse cluster members.

    1. Start the Deployment Manger and the node agents.

    2. In the administrative console, click System administration > Nodes.

    3. Select all of the nodes and click Full Resynchronize.

    4. Stop and restart all of the clusters and servers.


  8. If the Process Server database is a new database, you must create the database and run the bootstrapProcessServerData command before you try to start the servers or cluster members.
    Note: For existing databases, the user ID that is configured for the Process Server and Performance Data Warehouse database should match for existing database user IDs.

    Changing the database design file (bpm.standard.standalone.dbDesign or bpm.standard.nd.dbDesign)

    The database design file gets generated during the stand-alone profile creation process under the <profile-root>/properties/db/ directory or the cluster creation process under the <profile-root>/properties/db/<cluster_name >/ directory. This file does not get used by any of the runtime components. However, some of the upgrade commands like the upgrade7x.bat command, make use of this file to determine the database information.

    Locate the bpm.standard.{standalone/nd}.dbDesign file and update the database information with the same values that you used for the data source and the 98Database.xml file.

    You can use the DbDesignGenerator in edit mode to change the bpm.standard.standalone.dbDesign or bpm.standard.nd.dbDesign file. Complete the following steps:

    1. Run one of the following commands:
      • <install_root>/util/dbutil/DbDesignGenerator.sh -e bpm.standard.standalone.dbDesign.

      • <install_root>/util/dbutil/DbDesignGenerator.sh -e bpm.standard.nd.dbDesign.


        The <install_root> variable is the location of your installation.

    2. Follow the DbDesignGenerator wizard to make the necessary changes.

    3. Replace the existing file under the <profile-root>/properties/db directory.


    You can also use the same tool to regenerate DDL scripts as needed and create the new database.



    Validating the changes

    1. Use the Test button in the data source to verify that the changes to the data source are correct.

    2. Inspect the TeamWorksConfiguration.running.xml file, which is generated after you restart the server or the cluster member, to verify your settings. Modifications to the 100custom.xml / 98Database.xml files are merged and TeamWorksConfiguration.running.xml file is generated under the appropriate server config directory.

    3. Check all the systemout.log files to make sure that database connection-related errors do not exist.

    Related information

    Teamworks Config File Overview
    Changing IBM Process Server properties
    Database design tool

    Cross reference information
    Segment Product Component Platform Version Edition
    Business Integration IBM Business Process Manager Express Databases Linux 8.0.1, 8.0, 7.5.1, 7.5
    Business Integration IBM Business Process Manager Advanced Databases AIX, Linux, Linux zSeries, Solaris, Windows 8.0.1, 8.0, 7.5.1, 7.5

    Product Alias/Synonym

    BPM

    Rate this page:

    (0 users)Average rating

    Document information


    More support for:

    IBM Business Process Manager Standard
    Databases

    Software version:

    7.5, 7.5.1, 8.0, 8.0.1

    Operating system(s):

    AIX, Linux, Linux zSeries, Solaris, Windows

    Reference #:

    1587850

    Modified date:

    2012-05-16

    Translate my page

    Machine Translation

    Content navigation