Follow these steps to upgrade the existing profiles in a stand-alone environment.
For each stand-alone profile, complete the following steps:
Before upgrading an existing installation, run the backupConfig command to back up the configuration files of each profile that the refresh pack can update. See Backing up and restoring administrative configuration files in the WebSphere® Application Server Information Center for more information about running this command.
After you upgrade your installation and before you start the server or a cluster, replace the XSL transformation files with the backup version.
WebSphere Application Server refresh pack installation might update the WASServiceMsg.dll file. If any of the WebSphere servers (including node agents and deployment manager) are configured to start automatically using Windows services, the WASServiceMsg.dll file gets locked by the Microsoft Windows operating system.
If you see a WASServiceMsg.dll file cannot be replaced error during the refresh pack installation of WebSphere Application Server, change the starting option for all the WebSphere services so that they start manually. Then restart the machine where the updates are being made before installing the WebSphere Application Server refresh pack.
Refer to the Technote WASServiceMsg.dll is locked when installing fix packs for more information.
Refer to the technote Update Instructions for V8.0.1 for the IBM Business Process Manager (BPM) products, which contains specific instructions for using both the IBM Installation Manager graphical user interface (GUI) and the silent installation methods to install Refresh Pack V8.0.1.
Install the new version of IBM Business Process Manager as described in Obtaining and installing the product code.
bin/ws_ant.sh -f util/BPMProfileUpgrade.ant -profileName profile_name -Dupgrade=true
where profile_name is the name of the stand-alone profile (which on z/OS® is default).
If you are prompted for information about your database setup, specify the relevant values for your environment. When prompted, enter Y to confirm that you want to generate the scripts.
Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@. Then connect to the DB2 for z/OS database, and run the script against the database by using your preferred tool.
Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@. Then connect to the DB2 for z/OS database, and run the script against the database by using your preferred tool.
database.is.db2zos=true
where profile_name is the name of the stand-alone profile. For more information about the parameters that you can use with the upgradeProcessData command, see upgradeProcessData command-line utility.
where profile_name is the name of the stand-alone profile. For more information about the parameters that you can use with the upgradeProcessData command, see upgradeProcessData command-line utility.
where profile_root is the root directory of the standalone profile, db_type is the database type, db_name is the database name, and schema_name is the (possibly empty) schema name.
If success --> CWWBB0613I: Database migration: completed successfully 751/1 to 801/0.
If failed --> CWWBB0615E: Database migration failed 751/1 to 801/0.
The
value after the "/" character is a binary flag that is reset
to zero after successful migration, it is not part of the product
version number. If the database migration failed, check the log file
for other failure messages, and fix any problems before trying to
restart the server.