WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Upgrading the Business Space database manually

After migrating the server from version 6.1.2, you must manually upgrade the Business Space database to a new database schema before you start the version 6.2 server.

Before you begin

About this task

After migrating WebSphere® ESB from version 6.1.2 to version 6.2, the Business Space database is still configured to be used with Business Space 6.1.2. You must upgrade the Business Space database before it is accessed by Business Space version 6.2. This step consists of running two database scripts. The first script upgrades the database schema. The second script modifies data in the Business Space database to prepare it for use by Business Space version 6.2.
Note: Before running the scripts, you need to edit them and replace all occurrences of the @SCHEMA@ string with the schema name of the Business Space database. The default schema name is IBMBUSSP. When running the script, the database user must have sufficient authorization to modify the database.
Procedure
  1. Make sure that you are using a user ID with sufficient authority to update the database schema.
  2. Back up the database.
  3. Locate the directory where the database scripts are located: install_root/dbscripts/BusinessSpace \database_type.

    Where:

    install_root
    is the root directory of the WebSphere ESB version 6.2 installation file system.
    database_type
    is a name corresponding to the database product you are using. Applicable database types and their directory names are as follows:
    Database type Directory name
    DB2® for z/OS® Version 8.x

    DB2zOSV8

    Use scripts in this directory if your initial database configuration used DB2 z/OS v8 or later (uses long table names)

    Note: If you used DB2 z/OS v7 during your initial database configuration, refer to the relevant technote at the WebSphere Enterprise Service Bus support site.
    DB2 for z/OS Version 9.x

    DB2zOSV9

    Use the scripts in this directory if your initial database configuration used DB2 z/OS v9 and a DB2 z/OS v9 key

    Note: If you used DB2 z/OS v7 during your initial database configuration, refer to the relevant technote at the WebSphere Enterprise Service Bus support site.
    Derby Derby
    Note: If you have an existing Cloudscape database for a previous (6.0.x) installation of WebSphere ESB, the database must first be upgraded from a Cloudscape database to a Derby database. See . Then, once you have a Derby database that corresponds to that same (6.0.x) WebSphere ESB version, you must then upgrade the database to correspond to WebSphere ESB version 6.2 with the scripts in this directory.
    For specific database product names and versions see Database configurations.
  4. Locate the migration scripts for the database and current schema version, where schema_version has the value 612 for version 6.1.2. For example, to upgrade the Business Space database schema for DB2 from WebSphere ESB version 6.1.2 to version 6.2, you need install_root/dbscripts/BusinessSpace/DB2/upgradeSchema612_BusinessSpace.sql.
    Note: You also need the upgradeData612_BusinessSpace.sql script.
  5. Copy the appropriate scripts from the directory in which you found them to the system on which the database is running.
  6. Modify the SQL scripts upgradeSchema612_BusinessSpace.sql and upgradeData612_BusinessSpace.sql to meet your requirements. For example, you must change the schema name of the database, and you might need to change a user name, password, or file path.
  7. Using your database client, connect to the database. This is to ensure that it can connect.
  8. Run your version of the upgrade SQL scripts. For information on how to execute a .sql script with your database, refer to the documentation for your database product.
    1. Run upgradeSchema612_BusinessSpace.sql to upgrade the database schema.
    2. Run upgradeData612_BusinessSpace.sql to modify the data in the Business Space database.
  9. If there are any errors, or failure is indicated in your database client output, fix the reported errors and retry step 8.

Results

The database has been updated, and is ready for use by Business Space version 6.2. After you run the script to upgrade the database schema, the database can no longer be used by Business Space version 6.1.2.

task Task topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/doc/tmig_vtv_upg_bsdb.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).