WPG Update Installer (UPDI) Validator utility

Content

Prerequisites

Following are the prerequisites:

1. Setup WebSphere Partner Gateway database (DB2 or ORACLE).
2. Install WebSphere Partner Gateway hub (any mode).
3. Download and install IBM Update Installer 7.0.0.1 or above on all machines at http://www.ibm.com/support/docview.wss?uid=swg24020212, where components of WebSphere Partner Gateway are installed.
4. Download WebSphere Partner Gateway Update Installer version specific file (<version>.zip ) from http://www.ibm.com/support/docview.wss?uid=swg27015150.

Instructions to set up WPG Update Installer (UPDI) Validator

1. Download the appropriate "<version>_WPGUPDIValidator.zip" file using the following URLs and place it under <WPG Install Locations> on all machines, having any WebSphere Partner Gateway components installed. For example: /opt/IBM/bcghub-dmgr or /opt/IBM/bcghub-distrib or /opt/IBM/bcgappsdb or /opt/IBM/bcgmasdb etc.
   
   a. You can download WPG UPDI Validator for WPG V6.2.1
   
   b. You can download WPG UPDI Validator for WPG V6.2.0
   
2. Unzip the <version>_WPGUPDIValidator.zip file under <WPG Install Locations>.
3. When you extract the "<version>_WPGUPDIValidator.zip" file, the files will be extracted in the updivalidation and the bin folders. Note that the existing "bin" folder will be updated with the extracted files.
4. The "<version>_WPGUPDIValidator.zip" file when extracted, displays the following files:

a) WPG Install Location>/updivalidation/updivalidator.jar
b) WPG Install Location>/updivalidation/log4j-1.2.13.jar
c) WPG Install Location>/updivalidation/log4j.properties
d) WPG Install Location>/updivalidation/README.txt
e) WPG Install Location>/updivalidation/Deploy/BCGConsole.ear
f) WPG Install Location>/updivalidation/Deploy/DBScripts/DB2/metadata/Metadata.sql
g) WPG Install location>/updivalidation/Deploy/DBScripts/DB2/Procedure/
DB_SYSPROPERTIESU_UPDI.sql
h) WPG Install Location>/updivalidation/Deploy/DBScripts/Oracle/metadata/Metadata.sql
i) WPG Install Location>/updivalidation/Deploy/DBScripts/Oracle/Procedure/
DB_SYSPROPERTIESU_UPDI.sql
j) WPG Install Location>/bin/updivalidator.bat
k) WPG Install Location>/bin/appendclasspath.bat
l) WPG Install Location>/bin/updivalidator.sh

After successfully extracting the files, you are now ready to use the WPG Update Installer (UPDI) Validator utility.

Usage instructions

The script can be run by using any one of the following three modes:

1. CONFIG
2. DEPLOY
3. VERIFY

1. CONFIG: Run the script in the Config mode to setup the WPG UPDI.

Note: This step is required at all WPG installed locations, where WPG UPDI setup is not done. For WPG621 and above users, since WPG UPDI is already setup, CONFIG mode should not be run.

The CONFIG step should be first executed on Websphere Partner Gateway Deployment Manager location or WebSphere Partner Gateway Hub location, and then on other WebSphere Partner Gateway locations.

After running the script using the CONFIG mode, the <installed-location> will have "properties" and "responsefiles" directories created with all the required files inside respective directories.

Usage of the CONFIG mode:

1. Under the Common File System(CFS), create "UPDI" directory.
2. Place the "WPG UPDI <version>.zip file (corresponding to the WPG Version)" under CFS/UPDI location. For example, WPG UPDI 6.2.0.0.zip.
3. If the Database is Oracle, place the "ojdbc*.jar" file or the "classes.zip" file under CFS/UPDI location.
4. Go to the "bin" directory located under <WPG Install Location>.
5. The UPDI validator script can be run by calling "updivalidator.bat" file or the "updivalidator.sh" file depending upon the operating system. For example, run "updivalidator.bat CONFIG" on Windows systems and run "updivalidator.sh CONFIG" on non-Windows systems.
6. When the validator asks for the absolute path of the CFS, enter a valid path to CFS. For example, C:\Program Files\IBM\WPG\bcghub-distrib\common or /opt/IBM/bcghub-distrib/common.
7. The CONFIG mode extracts the WPG UPDI <version>.zip file (mentioned in step - 2) to <WPG Install Location>, depending upon the location from where the UPDI validator is being run.
8. The execution logs can be found under <WPG Install Location>/updivalidation/UPDISetup.log, depending upon the location from where the UPDI validator is being run.

2. DEPLOY: Run the script in the DEPLOY mode to deploy the WPG UPDI console changes.

When you run the script in the DEPLOY mode, the changes for UPDIValidator in the WebSphere Partner Gateway console are updated.

Note: The DEPLOY mode can be run from "bcghub-dmgr" or "bcghub-simple" locations only. Ensure that the WPG DMGR and all nodes in case of distributed mode, and WPG HUB in case of Simple mode are running.

Usage of the DEPLOY mode:

1. Go to the "bin" directory located under <WPG Install> location.
2. The UPDI Validator script can be run by calling "updivalidator.bat" or "updivalidator.sh" depending upon the operating system. For example, run "updivalidator.bat DEPLOY" on Windows systems and run "updivalidator.sh DEPLOY" on non-Windows systems.
3. When the validator asks for database credentials and SOAP port, input valid values.
4. The DEPLOY mode deploys the WPG UPDI console changes.
5. After DEPLOY mode is successful, restart the bcgconsole application server.
6. The execution logs can be found under <WPG Install Location>/updivalidation/UPDISetup.log, depending upon the location from where the UPDI validator is being run.

3. VERIFY: Run the script in the VERIFY mode to update the response files and validate its properties.

1. Ensure the following things before running the validator in the VERIFY mode:

Case A: If UPDI is already used to apply any WPG iFix or WPG Fixpacks:
a) UPDI is already setup.
b) If response files are filled with correct values, then run the validator in VERIFY mode (as shown in step 3 below).

OR

Case B: When WPG UPDI is set up using the UPDIValidator CONFIG mode:
a) If the response files are not filled with correct values, update the response file properties from WPG console as illustrated below:
i) Open WPG Console in the browser and login to the console.
ii) Go to System Administration tab.
iii) Under the System Administrator tab, go to Update Installer tab.
iv) Edit and save the response file properties.
v) Run the UPDI validator in VERIFY mode (as shown in step 3 below)

2. Go to the "bin" directory located under <WPG Install> location, where you want to run the WPG UPDI Validator in the VERIFY mode.
3. The UPDI validator script can be run by calling "updivalidator.bat" or "updivalidator.sh" depending upon the operating system. For example, run "updivalidator.bat VERIFY" on Windows system and run "updivalidator.sh VERIFY" on non-Windows system. Verification results will display on the screen, where the "updivalidator.bat" or the "updivalidator.sh" script was executed.
4. The execution logs can be found under <WPG Install Location>/updivalidation/UPDISetup.log, depending upon the location from where the UPDI validator was run.

Important information

1. While running the WPG UPDI Validator in the VERIFY mode, if the database used is Oracle, then the apps owner name should be verified manually.
2. While running the WPG UPDI Validator in the VERIFY mode, if the database used is Oracle, then the group name should be verified manually.
3. While running the WPG UPDI Validator in the DEPLOY or the VERIFY mode, if the SOAP port verification happens, warning or error messages are generated and shown. These messages are related to WAS messages which cannot be suppressed and they do not impact the execution of the WPG UPDI Validator.
4. If "appsdb" and "masdb" are installed on a machine which is different from the machine where the Common File System(CFS) exists, then before running the WPG UPDI Validator in the CONFIG or the VERIFY mode, mount the CFS on the machine where appsdb and masdb are installed.
5. While using the standalone WPG UPDI Validator utility prepared for WPG 620 Base or WPG 621 Base, and before you extract the UPDIValidator.zip file, you need to set executable permission on the UPDI Validator files, if the permission is not already set on the Validator files.