http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/index.html

Domains Running In Production Mode Without PointBase

For WebLogic Integration 8.1 domains running in production mode without the PointBase database, the nopointbase option must be passed to startWebLogic.cmd or startWebLogic.sh. Otherwise, the server will not start correctly; WebLogic Integration 8.1 enables PointBase even when it is not used by the configuration.

Upgrading an Application That Uses an Application Integration Control

For an application using an Application Integration control that was originally deployed using the WebLogic Workshop auto-deploy feature, you must first undeploy the application and then redeploy it using the WebLogic Integration Administration Console or the command line deployer.

Upgrading an Existing WebLogic Integration 8.1 SP2 or SP3 Domain to WebLogic Integration 8.1 SP4

This section provides the steps for upgrading either an existing single node or clustered domain generated for WebLogic Integration 8.1 SP2 or SP3 to WebLogic Integration 8.1 SP4. Another way to update to a WebLogic Integration 8.1 SP4 domain is to create a new WebLogic Integration 8.1 SP4 domain and move your existing WebLogic Integration 8.1 SP2 or SP3 application to the new domain. To learn more see "Creating a New Domain and Deploying Applications Into It" in Roadmap for Upgrading WebLogic Platform available at the following URL:

http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/roadmap.html

To upgrade a domain generated for WebLogic Integration 8.1 SP2 or SP3 to WebLogic Integration 8.1 SP4, complete the following steps:

Set the correct environment and paths:
Go to BEA_HOME_814/weblogic81/common/bin directory.

In the preceding line, BEA_HOME_814 represents the directory where WebLogic Platform 8.1 SP4 is installed.

Execute the environment script by entering the following:

UNIX using sh or ksh: . ./commEnv.sh

Windows: commEnv.cmd

Shut down any instances of WebLogic Server running on the domain being upgraded.
If you are using PointBase as your database, follow the procedure in Upgrading PointBase, then continue with the next step.
Locate the options.properties.sample file in the following directory:

BEA_HOME_814/weblogic81/integration/upgrade

In the preceding line, BEA_HOME_814 represents the directory where WebLogic Platform 8.1 SP4 is installed.

Using the options.properties.sample file as a template, create a file named options.properties, and specify the following values in it:

Note: Use "/" as a file separator.

• current.version—The version of WebLogic Platform from which you want to upgrade.
• domain.path—Path of the domain to upgrade.
• beahome.path—Path to the WebLogic Integration 8.1 SP2 or SP3 installation.
• beahome.4.path—Path to the WebLogic Integration 8.1 SP4 installation.

Note: If you have upgraded to WebLogic Integration 8.1 SP4 using Smart Update, beahome.path and beahome4.path should specify the same directory path. For example, on Windows if you installed WebLogic Integration 8.1 SP2 in the c:/bea directory and then used the Smart Update to upgrade that installation to WebLogic Integration 8.1 SP4, both beahome.path and beahome4.path should point to the c:/bea directory.

Windows example: If WebLogic Integration 8.1 SP2 is installed on C:/beaSP2, WebLogic Integration 8.1 SP4 is installed on C:/beaSP4, and the WebLogic Integration 8.1 SP4 domain to upgrade is located at C:/beaSP2/user_projects/domains/integration, you would set these properties as follows:

• current.version=sp2
• domain.path=C:/beaSP2/user_projects/domains/integration
• beahome.path=C:/beaSP2
• beahome.4.path=C:/beaSP4

UNIX example:

• current.version=sp2
• domain.path=/home/beaSP2/user_projects/domains/integration
• beahome.path=/home/beaSP2
• beahome.4.path=/home/beaSP4

Note: BEA recommends that you use the option backup=true. Setting this option to true in your options.properties file means that the domain specified in the domain.path is backed up to domain.path_BK_timestamp.

Locate the upgrade scripts in the following directory:

BEA_HOME_814/weblogic81/integration/upgrade

In the preceding line, BEA_HOME_814 represents the directory where WebLogic Platform 8.1 SP4 is installed.

Determine if you need or want to manually upgrade the database or use the upgrade script.

Upgrading the database structure is implicit in the upgrade process. If you are using PointBase or prefer to do this as a separate step, you must invoke the upgrade script with the database flag set to false as follows: -Ddb_upgrade=false and then upgrade the database manually.

To learn more about upgrading the database manually, see Upgrading PointBase or Manually Upgrading WebLogic Integration 8.1 SP2 or SP3 Databases to WebLogic Integration 8.1 SP4.

Note: The databases must be upgraded before you start the WebLogic Integration 8.1 SP4 server in the upgraded domain.

Run the following ant target to upgrade the JDK version reference:

ant -f domain_upgrade.xml update_paths

Run the upgrade script for the domain that you have created:

ant -f domain_upgrade.xml upgrade 
   -Doptions.properties=[<your options file>]    -Dcurrent.version=[sp2|sp3]
   -Dsingle.node=[true|false]
   -Ddb_type=[oracle|sybase|mssql|db2|pointbase]
   -Ddb_user=[<user_name>]
   -Ddb_password=[<password>] -Ddb_server=[<server>:<port>]
   -Ddb_name=[<database_name>]

The your_options_file is usually called the options.properties. The user_name and password are the valid username and password for the database. For help on the ant syntax, type ant on the command line.

Note: If you are upgrading your database using the script, the data source must be connected to an active database.

Warning: Do not upgrade your domain more than once. If you do, the domain upgrade process will fail with an error.

If you are upgrading a clustered domain from WebLogic Integration 8.1 SP2, create the WebLogic Integration queues in WebLogic Integration 8.1 SP4. See Creating the Required WebLogic Integration Queues For a Clustered Domain when Upgrading from WebLogic Integration 8.1 SP2.
If you are upgrading a clustered domain, delete the staging directories for the administration and managed servers in the upgraded domain.

This ensures that all the servers get the upgraded WebLogic Integration applications from the WebLogic Integration 8.1 SP4 installation rather than the local staging directories, which may be outdated.

For example, if your domain contains an administration server named cgServer and two managed servers named new_managedServer_1 and new_managedServer_2, go to the directory that contains the domain and delete the directories (including the contents) named cgServer, new_managedServer_1, and new_managedServer_2.

Note: To learn more about domains, see "System Administration" in the WebLogic Server documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/admin.html

Manually Upgrading WebLogic Integration 8.1 SP2 or SP3 Databases to WebLogic Integration 8.1 SP4

If you suppressed the automatic upgrading of the databases when you upgraded the domain, you must upgrade the database manually before you can start the WebLogic Server 8.1 SP4 server. If you did not suppress the database upgrade during the domain upgrade process, you need not do any further database upgrade.

The database schemas in WebLogic Integration 8.1 SP4 have changed from WebLogic Integration 8.1 SP2 and SP3. To update your databases manually, you need to run the script for the databases that you use. Scripts are provided for the following databases:

• Oracle 8.1.7 and 9.2.0
• PointBase 4.4
• Sybase 12.5
• DB2 8.1
• Microsoft SQL Server 2000

To manually upgrade databases from WebLogic Integration 8.1 SP2 or SP3 to WebLogic Integration 8.1 SP4, complete the following steps:

Note: If you are using the PointBase database, see Upgrading PointBase.

Locate the database upgrade scripts in the following directory:

On Windows:

BEA_HOME_814\weblogic81\integration\dbscripts\db_directory

On UNIX:

BEA_HOME_814/weblogic81/integration/dbscripts/db_directory

In the previous paragraphs, BEA_HOME _814 represents the directory in which you installed WebLogic Platform 8.1 SP4, and db_directory represents oracle, pointbase, sybase, db2, or mssql.

Run one of the following database upgrade scripts, depending on whether you are upgrading from WebLogic Integration 8.1 SP2 or SP3:
• upgrade_runtime_sp2_sp4.sql
• upgrade_runtime_sp3_sp4.sql
Start the WebLogic Integration 8.1 SP4 server from the upgraded domain.

Creating the Required WebLogic Integration Queues For a Clustered Domain when Upgrading from WebLogic Integration 8.1 SP2

To finish upgrading your clustered domain, perform the following steps on the upgraded domain:

Note: You should be familiar with working with clustered domains before performing these steps. For more information about clustered domains, see System Administration in the WebLogic Server documentation at the following URL:

http://download.oracle.com/docs/cd/E13222_01/wls/docs81/admin.html

Start the WebLogic Integration 8.1 SP3 server for your domain.
Create the following distributed queues from the WebLogic Server Administration Console and distribute them on each Managed Server in the cluster.

wli.b2b.mt.event.stream

wli.b2b.mt.event.stream_error

wli.process.event.stream

wli.process.event.stream_error

In the WebLogic Server Administration Console, create the queues named wli.internal.scheduling.queue and wli.internal.scheduling.queue_error.

Note: Both these queues are not distributed queues.

For each distributed member of wli.b2b.mt.event.stream, set the error destination queue to wli.b2b.mt.event.stream_error.
For each distributed member of wli.process.event.stream, set the error destination queue to wli.process.event.stream_error.
For wli.internal.scheduling.queue, set the error destination queue to wli.internal.scheduling.queue_error.

Note: wli.internal.scheduling.queue is not a distributed queue.

Modify the following attributes on error queues:
For each distributed member of wli.b2b.mt.event.stream_error, set RedeliveryLimit="0".
For each distributed member of wli.process.event.stream_error, set RedeliveryLimit="0".
For each distributed member of wli.internal.scheduling.queue_error, set RedeliveryLimit="0".
For each distributed member of wli.b2b.mt.event.stream, set RedeliveryLimit="1" and RedeliveryDelayOverride="5000".
For each distributed member of wli.process.event.stream, set RedeliveryLimit="1" and RedeliveryDelayOverride="5000".

Upgrading PointBase

If you are using the PointBase database, you must upgrade it manually. To manually upgrade the PointBase database from WebLogic Integration 8.1 SP2 or SP3 to WebLogic Integration 8.1 SP4, complete the following steps:

Start the PointBase server:
Open either a UNIX shell or a Windows command prompt window and navigate to the domain root for the domain you just upgraded.
Run the setdomainenv script.
Start the PointBase server:

On Windows:

WL_HOME\common\bin\startPointBase.cmd -port=9093 -debug=0 -console=false -background=true -ini=DOMAIN_HOME\pointbase.ini > DOMAIN_HOME/pointbase.log 2>&1

On UNIX:

WL_HOME/common/bin/startPointBase.sh -port=9093 -debug=0 -console=false -background=true -ini=DOMAIN_HOME\pointbase.ini > DOMAIN_HOME/pointbase.log 2>&1

In the preceding line, WL_HOME is the weblogic81 directory of the WebLogic Platform 8.1 SP4.

Note: This is a generic PointBase startup command. You may need to customize this command if you are not using the default directories.

To upgrade the database, execute the following command:

ant -f domain_upgrade.xml upgrade_dbs