Upgrade Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
This section provides information on upgrading to BEA WebLogic Integration 8.1 Service Pack 6 (SP6).
Ways to Upgrade WebLogic Integration 8.1 SP4 or SP5 to WebLogic Integration 8.1 SP6
Manually Upgrading WebLogic Integration 8.1 SP4 or SP5 Databases to WebLogic Integration 8.1 SP6
Describes the process of manually upgrading databases created in WebLogic Integration 8.1 SP3 or SP4 to SP5.
WebLogic Integration 8.1 SP6 is installed as part of WebLogic Platform 8.1 SP6. You can upgrade from WebLogic Integration 8.1 SP4 and SP5 to WebLogic Integration 8.1 SP6 using one of the following ways:
For information about upgrading WebLogic Platform 8.1 SP6 as a separate installation, see Installing WebLogic Platform at the following URL:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/index.html
For information about upgrading WebLogic Platform 8.1 SP6 as an upgrade installation, see "Installing Service Packs and Rolling Patches" in Installing WebLogic Platform at the following URL:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/install/update.html
Domains created for WebLogic Integration 8.1 SP5 must be upgraded to run with WebLogic Integration 8.1 SP6.
To help you upgrade your WebLogic Integration domains, upgrade scripts are included in WebLogic Integration 8.1 SP6. These scripts facilitate upgrading domains, including those domains created with the BEA WebLogic 8.1 SP6 Configuration Wizard.
This section includes information on the following topics:
This section contains information you should be aware of before upgrading WebLogic Integration 8.1 SP4 or SP5 to WebLogic Integration 8.1 SP6. To learn more about upgrading your WebLogic Platform installation, see "Before You Upgrade Your Systems" in Upgrade Planning Guide at the following URL:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/index.html
Note: If your WebLogic Integration 8.1 SP6 domain contains both WebLogic Integration and WebLogic Portal® resources, please review the information in the "Upgrading WebLogic Platform Domains and Applications to the Latest Service Pack" section in the Upgrade Planning Guide available at the following URL:
http://download.oracle.com/docs/cd/E13196_01/platform/docs81/upgrade/index.html
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.
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.
This section provides the steps for upgrading either an existing single node or clustered domain generated for WebLogic Integration 8.1 SP5 to WebLogic Integration 8.1 SP6. Another way to update to a WebLogic Integration 8.1 SP5 domain is to create a new WebLogic Integration 8.1 SP6 domain and move your existing WebLogic Integration 8.1 SP5 applications 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 SP5 to WebLogic Integration 8.1 SP6, complete the following steps:
ANT_OPTS
environment variable on your machine to -Xmx256m
, to ensure that Ant has enough memory available to complete the domain upgrade procedure. To set the ANT_OPTS
variable, enter the command appropriate for your operating system:
BEA_HOME_816
/weblogic81/integration/upgrade
In the preceding line, BEA_HOME_816
represents the directory where WebLogic Platform 8.1 SP6 is installed.
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.
Table 2-1 Values for the options.properties file
The version of WebLogic Platform from which you want to upgrade. For example, |
|
The absolute path to the WebLogic Integration 8.1 SP5 installation. For example: |
|
Absolute path to the WebLogic Integration 8.1 SP6 installation. For example: |
|
Specify the platform on which the software is being upgraded, ideally use the default value Note: Note: If you specify the property |
|
Name of the directory in which WebLogic Integration SP5 is installed. Default value is |
|
Name of the directory in which WebLogic Integration SP6 is installed. Default value is |
|
Ideally use the default value |
|
Set the value as |
Note: If you have upgraded to WebLogic Integration 8.1 SP6 using Smart Update, beahome.path
and beahome.latest.path
should specify the same directory path. For example, on Windows if you installed WebLogic Integration 8.1 SP5 in the c:/bea
directory and then used the Smart Update to upgrade that installation to WebLogic Integration 8.1 SP6, both beahome.path
and beahome.latest.path
should point to the c:/bea
directory.
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
.
BEA_HOME_816
/weblogic81/integration/upgrade
In the preceding line, BEA_HOME_816
represents the directory where WebLogic Platform 8.1 SP6 is installed.
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 SP4 or SP5 Databases to WebLogic Integration 8.1 SP6.
Note: The databases must be upgraded before you start the WebLogic Integration 8.1 SP6 server in the upgraded domain.
ant -f domain_upgrade.xml update_paths
ant -f domain_upgrade.xml upgrade
-Doptions.properties=[<your options file>] -Dcurrent.version=[sp3|sp4]
-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.
.wlnotdelete
subdirectory and all its contents. This subdirectory, which contains the server's cache, is located in the domain's server directory. For example: c:\bea\user_projects\domains\mydomain\examplesServer\.wlnotdelete
Removing the .wlnotdelete
subdirectory ensures that all domain upgrade changes become effective when the server is restarted.
Note: Note: To see the available Ant targets and a description of each, enter the following command from the WL_HOME
/integration/upgrade
directory:
This ensures that all the servers get the upgraded WebLogic Integration applications from the WebLogic Integration 8.1 SP6 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
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 SP6 server. If you did not suppress the database upgrade during the domain upgrade process, you can skip this section.
The database schemas in WebLogic Integration 8.1 SP6 have changed from WebLogic Integration 8.1 SP5. To update your databases manually, you need to run the script for the databases that you use. Scripts are provided for Oracle®, PointBase®, Sybase®, DB2® and Microsoft® SQL ServerTM databases.
To manually upgrade databases from WebLogic Integration 8.1 SP5 to WebLogic Integration 8.1 SP6, complete the following steps:
Note: If you are using the PointBase database, see Upgrading PointBase.
BEA_HOME_816
\weblogic81\integration\dbscripts\db_directory
BEA_HOME_816
/weblogic81/integration/dbscripts/db_directory
In the previous paragraphs, BEA_HOME_816
represents the directory in which you installed WebLogic Platform 8.1 SP5, and db_directory
represents oracle
, pointbase
, sybase
, db2
, or mssql
.
options.properties
file, the respective upgrade scripts will be executed. ant -f domain_upgrade.xml upgrade_dbs
Note: Ensure the db_upgrade
property is set to true
in order to successfully execute the command.
If you are using the PointBase database, you must upgrade it manually.
To manually upgrade the PointBase database from WebLogic Integration 8.1 SP4 or SP5 to WebLogic Integration 8.1 SP6, complete the following steps:
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
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 SP6.
ant -f domain_upgrade.xml upgrade_dbs
Note: Ensure the db_upgrade
property is set to false
in order to successfully execute the command.
![]() ![]() |
![]() |
![]() |