Upgrading Business Integration Connect

This upgrade procedure assumes that the same environment will be used for the new version, including the same version MQSeries queue manager configuration. It is also assumed that the upgrade is for the same Business Integration Connect Edition (for example, from Enterprise version 4.2.x -> Enterprise version 4.2.x).

To upgrade to Business Integration Connect to the latest version:

Shut down the previous version:

  1. Stop the Receiver by using the shutdown_bcg.* script that is appropriate for your operating system. The shutdown_bcg.* script is located in the following directory:
    {WBIC INSTALL DIR}/receiver/was/bin 
    

    Check the console Document Viewer to verify that documents in progress have finished processing.

  2. Stop the Document Manager by using the shutdown_bcg.* script that is appropriate for your operating system. The shutdown_bcg.* script is located in the following directory:
    {WBIC INSTALL DIR}/router/was/bin
    
  3. Stop the Community Console by using the stopServer.* script that is appropriate for your operating system. The stopServer.* script is located in the {WBIC INSTALL DIR}/console/was/bin directory. Specify server1 as the server name. For example:
    {WBIC INSTALL DIR}/console/was/bin/stopServer.* server1
    

Back up the previous version:

  1. Back up the database. Refer to your database administrator or database documentation for information on how to do this. This step is important because the database contains Business Integration Connect data that is difficult to recreate.
  2. Back up the shared, common directory tree, located in {WBIC INSTALL DIR}/common. This step is important because the shared, common tree contains Business Integration Connect data, such as the non-repudiation and message store directories, that is difficult to recreate.
  3. Back up the previous Business Integration Connect installation directories. For example: {WBIC INSTALL DIR}/console, {WBIC INSTALL DIR}/receiver, and {WBIC INSTALL DIR}/router.


    Alternatively, you can repeat the following steps to backup only the specified configuration data:

    1. Back up the embedded WAS configuration by calling the was/bin/backupConfig.* script that is appropriate for your operating system. Copy the WebSphereConfig*.zip backup file to the backup location.
    2. Back up the was/jndi/WBIC subdirectory tree.
    3. Back up the was/wbic/config subdirectory tree.

Run the DBLoader installer:

  1. Uninistall the Database Loader by entering the following command (as an Administrator user on Windows or as a root user on UNIX):
    {WBIC INSTALL DIR}/DBLoader/_uninst/uninstall
    

    Important:
    Do not select "Drop the database" during the uninstallation. Dropping the database causes data loss if it has not been backed up. The existing database will be upgraded in subsequent steps.
  2. Run the upgraded Database Loader from the media location, using the setup* launcher that is specific to your operating system. For example:
    {CD_ROM/MEDIA DIR}/DBLoader/setup*
    

    Note:
    For Windows, make sure that you are logged in as the user that owns the database. That user is typically DB2ADMIN.

    Follow the guidelines below:

    1. Specify the same input values used in the previous version. For example: userids, passwords, database vendor, etc.
    2. Verify the configuration defaults and override as needed.
    3. Do not select "Run the SQL Files automatically".
  3. Run the BCGUpgrade*.sql script, located in the {WBIC INSTALL DIR}/DBLoader/scripts/DB2 or {WBIC INSTALL DIR}/DBLoader/scripts/Oracle directory.
    Note:
    Each BCGUpgrade_from-ver_to-ver.sql script must be run starting with the oldest version that applies to your system and continuing with each subsequent script.

    DB2

    Run the following commands:

    1. UNIX: su - db2inst1
      Windows: Start the DB2CLP
      Note:
      For Windows, make sure that you are logged in as the user that owns the database. That user is typically DB2ADMIN.
    2. db2start (if the database is not started)
    3. db2 connect to bcgapps (where "bcgapps" is the database name)
    4. cd {WBIC INSTALL DIR}/DBLoader/scripts/DB2
    5. Run one of the following scripts, depending on your existing version, to upgrade the database:
      4.2.0 to 4.2.1:
      db2 -td! -f BCGUpgrade_420_421.sql -z
       /tmp/WBIConnect/logs/BCGUpgrade_420_421.log
      

      4.2.1.0 to 4.2.1 (Fix Pack 1 not installed):

      db2 -td! -f BCGUpgrade_421_421FP1.sql -z
       /tmp/WBIConnect/logs/BCGUpgrade_421_421FP1.log
      

      4.2.1.1 to 4.2.2:

      db2 -td! -f BCGUpgrade_421FP1_422.sql -z
       /tmp/WBIConnect/logs/BCGUpgrade_421FP1_422.log
      
    6. Run the save_inputs.sql script to load the DBLoader user inputs into the database. For example:
      db2 -td! -f save_inputs.sql -z
       /tmp/WBIConnect/logs/save_inputs.log
      

    Oracle

    Run the following commands:

    Note:
    For Windows, you must be logged in as an Administrator user.
    1. cd {WBIC INSTALL DIR}/DBLoader/scripts/Oracle
    2. Run one of the following scripts, depending on your existing version, to upgrade the database:
      4.2.1.0 to 4.2.1 (Fix Pack 1 not installed):
      sqlplus -L bcgapps/password @BCGUpgrade_421_421FP1.sql
       >/tmp/WBIConnect/logs/BCGUpgrade_421_421FP1.log
      

      4.2.1.1 to 4.2.2:

      sqlplus -L bcgapps/password @BCGUpgrade_421FP1_422.sql
       >/tmp/WBIConnect/logs/BCGUpgrade_421FP1_422.log
      
    3. Run the save_inputs.sql script to load the DBLoader user inputs into the database. For example:
      sqlplus -L bcgapps/password @save_inputs.sql
       >/tmp/WBIConnect/logs/save_inputs.log
      

Update the MQSeries/JMS queue configuration:

Note:
For Windows, you must be logged in as an Administrator user.
  1. For UNIX: su -mqm
  2. Run the following command:
    runmqsc bcg.queue.manager < {CD_ROM/MEDIA DIR}
    /Tools/MQSeries/BCGUpgrade_Queues_v422.mqsc
    

    Where bcg.queue.manager is the MQSeries queue manager name.

Uninstall the previous version of Business Integration Connect:

  1. As an Administrator user on Windows or as a root user on UNIX, uninstall the previous version by entering the following command:
    {WBIC INSTALL DIR}/_uninst/uninstaller
    

    Select all features for uninstallation. If prompted with a message that a file "exists on this system and it has been modified since installation. Do you want to remove this file?" Click No

  2. Delete the remaining directory trees.
    Important:
    Do not delete the {WBIC INSTALL DIR}/common tree. That is where many of the runtime documents and data are stored. Deleting the common tree will cause data loss if it has not been backed up.

Install Business Integration Connect:

As an Administrator user on Windows or as a root user on UNIX, install Business Integration Connect using the setup* launcher appropriate for your operating system. For example: CD_ROM/MEDIA DIR}/hub/setup*

  1. Specify the same input values used in the previous version. For example: userids, passwords, database vendor, etc.
  2. Verify the configuration defaults and override as needed.
  3. Confirm that the common, shared directory tree is correct.

Restore custom configurations:

Restore any customized configuration from the previous version. Changes to the Receiver and Document Manager configuration files have been introduced with version 4.2.2. The new 4.2.2 configuration files must be used. Do not replace the 4.2.2 version of the configuration files with the older version from the backup directory.

To identify configuration file changes which may have been made to your 4.2.1 installation, compare the contents of each of the files in the 4.2.1 backup and 4.2.2 installation directories. Manually merge any changes into the 4.2.2 files.

Note:
The version.properties files in these directories should not be changed.

Compare the contents of the files located in the following directories:

console/was/wbic/config

receiver/was/wbic/config

router/was/wbic/config

The router/was/wbic/config/bcg.properties file contains the bcg.alertNotifications.mail* properties and the RosettaNet contact information, located in the bcg.A01.from* properties. If these values were not entered properly during the 4.2.2 hub installation, the values can be copied from the 4.2.1 bcg.properties file into the new 4.2.2 router/was/wbic/config/bcg.properties file.

Note:
A change to the base RosettaNet V02.00 package requires that it be re-loaded via the console if it had been previously installed.

Start Business Integration Connect:

For UNIX, refer to Starting Business Integration Connect.

For Windows, refer to Starting Business Integration Connect.

Copyright IBM Corp. 2003, 2004