SBP KNOWLEDGE MANAGEMENT SYSTEM

SBP001

BAW UPGRADE MANUAL

VERSION: 1.0
29-Dec-2020

Prepared by:
Revision Chart

Version Author(s) Description of Change Effective Date

0.1 Owais Hasan (Techlogix) Initial draft created by Owais 24-Sep-2020
0.2 Syed Bilal (SBP) Further updates done 23-Dec-2020
0.3 Owais Hasan (Techlogix) Final draft 31-Dec-2020
Contents
Pre-Requisites:............................................................................................................................................4
Backups:..................................................................................................................................................4
Setups......................................................................................................................................................4
Miscellaneous:.........................................................................................................................................4
Fail-over and Restore Scenario:...................................................................................................................5
DR Environment Upgrade:...........................................................................................................................6
Post Upgrade Steps:....................................................................................................................................6
Upgrade Procedure.....................................................................................................................................7
Pre-Requisites:
Before starting upgrade activity, following pre-requisites should be verified.

 The HADR replication of BPM Production database to DR database should be stopped before
taking backup. This step should be done on Friday 7 PM.

Backups:
This step should be done on Friday 8 PM.

 It is mandatory to take VM snapshot backup of BPM Production stack (Application and

database) at the time of 8:00 PM after closure of business.
 It is mandatory to take VM snapshot backup of BPM DR (Application and database) at the time
of 8:00 PM after closure of business.
 It is also mandatory to have cold backups of All BPM databases (BPMDB, CMNDB, PDWDB,
KM_ECM) at the time of 8:00 PM after closure of business.
 It is also advised to take cold VM backup of BPM Production and DR Application servers at the
time of 8:00 PM after closure of business.

Setups:
This step should be done on Wednesday 11 PM.

Following setup files should be present on BPM Production and DR server at designated directory:

 BAW_20_0_0_1_Linux_x86_3_of_3.tar.gz
 BAWE_20_0_0_1_Linux_x86_1_of_3.tar.gz
 BAWE_20_0_0_1_Linux_x86_2_of_3.tar.gz
 workflow.20001.delta.repository.zip
 8.6.20020001-WS-BPM-IFJR62453.zip
 8.6.20020001-WS-BPM-IFJR62480.zip
 8.6.20020001-WS-BPM-IFJR62974.zip (this file needs to be re-downloaded from following link:
https://www.ibm.com/support/fixcentral/swg/downloadFixes?parent=ibm
%2FWebSphere&product=ibm/WebSphere/
IBM+Business+Automation+Workflow&release=All&platform=All&function=fixId&fixids=8.6.200
20001-WS-BPM-
IFJR62974&includeRequisites=1&includeSupersedes=0&downloadMethod=http)

Miscellaneous:
 It is mandatory to have GUI Access enabled on BPM Production and DR Application servers. This
should be verified by Wednesday 4 PM.
 The OAW authenticator application should be stopped from ECM Production WebSphere. This
should be verified by Friday 6 PM.
  Since the BPM Process portal is still accessible to users from direct hostname URL, the users can
still access the application even if OAW application is stopped. It is recommended to block the
end user access by restricting following access from the user machines:
o Pr-bpmapp.sbp.org.pk 9081, 9444
o Dr-bpmapp.sbp.org.pk 9081, 9444
 It is important to note that this access should not be blocked on DBA user machines, as they
would need to access these machines during upgrade. Further, it is also important to note that
this Port block is temporary and should be enabled once the upgrade activity is completed. This
should be verified by Friday 6 PM.

Fail-over and Restore Scenario:

Although we have performed testing on UAT environment, and have taken consent from respective
business departments, it is possible that the BAW upgrade does not succeed on production. IBM has
ended support of BPM 8.6 version and it is mandatory for us to do this upgrade, so whatever the
problem is we cannot go back to using 8.6 version. Therefore, in case of any failure scenario, the
Development and UAT environment would not be reverted back to older version 8.6. The goal would be
to resolve the issue that has occurred on production environment and perform successful upgrade after
resolving any problem.

Below are the different fail-over scenarios and their respective resolutions. It is important to note that
these considerations are built on consideration that BPM application would be shut down for business
users at 6:PM Friday evening, and then we have the backups available as described in the Backup
section. It is also important to note that below scenarios also consider that ITSPMD has taken
application downtime from Friday 6:00 PM to Monday 6:00 AM.

 If BAW upgrade fails during the upgrade activity, first we would try to resolve the problem by
analyzing the issue and tracing out log files. We would also raise PMR with Severity 1 to IBM
Support to get their urgent support. The cut of time to stop looking into resolution is
recommended to be 3:PM Sunday Afternoon. After that, we should proceed with restoring the
backups. Before restoring, the BPM log files should be saved for analyzing the problem later.
 If BAW upgrade fails once business has resumed to normal on Monday morning, first we would
try to resolve the problem by analyzing the issue and tracing out log files. We would also raise
PMR with Severity 1 to IBM Support to get their urgent support. It is important to note that
since business cases would be down, we would need a cut-off time given by ITSPMD to stop
looking into resolution and move for restoration. We recommend to have 2 hours as cut-off time
for the efforts to resolve the problem. In case we go ahead with backup restore, it is important
to note that the business data from 9:00 AM in the morning would be lost, and once the backup
is restored, this data would need to resubmitted on the application.
DR Environment Upgrade:
In Production, we have HADR environment setup, where a separate BPM environment is present on DR
server, and its database is present as Standby mode. Both Production and DR environment are currently
on 8.6.201803, and we plan to upgrade both of them to 20.0.0.1.

The upgrade steps involve database scripts execution. During UAT upgrade, we observed that the scripts
upgrade existing databases (BPMDB, CMNDB etc.), and also create new database CPEDB. We
recommend following approach:

1. Stop HADR from Primary to Secondary environment. Turn on the BPM Services on DR site, and
verify that Process Portal and Admin Console are working correctly. This is to verify that DR site
is in working state before upgrade.
2. Perform all the upgrade steps in parallel on Production and DR site. All the steps including
database scripts step should be executed on both Production and DR.
3. Once the upgrade is successful on Production and DR, we need to verify both environments
after starting services. Both environments should be in working state.
4. Now, we need to setup HADR of all databases (BPMDB, CMNDB, PDWDB, KM_ECM, CPEDB)
from scratch (Restore cold backup from Production on DR database and then setup HADR).
5. Once HADR is successfully setup, we need to verify the application Production and then switch
over to DR environment to verify the application from DR site.

Post Upgrade Steps:

 The Maximum Query String parameter on reverse proxy server should be set to 4096, the BAW
process portal will not work on reverse proxy if this setting is not applied.
 In ECPM process, the rich text editor UI problem is resolved for new instances. However, for
existing instances, user will have to Save for Later and then re-open the task. This needs to be
sent as broadcast to concerned business users so that they are informed about this behavior.
 The following port access that was blocked in Pre-Requisite Step should be enabled for all
business users.
o Pr-bpmapp.sbp.org.pk 9081, 9444
o Dr-bpmapp.sbp.org.pk 9081, 9444
Upgrade Procedure
Before upgrade Verify that applications are working fine
- Stop all application services.
 - Copy the following files:

Create directory UpgradeMedia

Cd /bpmapp/bpmuser/UpgradeMedia

Copy the following 5 files:

BAW_20_0_0_1_Linux_x86_3_of_3.tar.gz 100% 2982MB 72.9MB/s 00:40
BAWE_20_0_0_1_Linux_x86_1_of_3.tar.gz 100% 1436MB 71.8MB/s 00:20
BAWE_20_0_0_1_Linux_x86_2_of_3.tar.gz 100% 4544MB 73.7MB/s 01:01
workflow.20001.delta.repository.zip 100% 4082MB 71.6MB/s 00:57
8.6.20020001-WS-BPM-IFJR62453.zip 100% 247KB 11.6MB/s 00:00

- untar the following BAW files:

tar –xvzf BAWE_20_0_0_1_Linux_x86_1_of_3.tar.gz

tar –xvzf BAWE_20_0_0_1_Linux_x86_2_of_3.tar.gz

tar –xvzf BAW_20_0_0_1_Linux_x86_3_of_3.tar.gz

- File should look like below screenshot after extraction:

After untar change owner to 744

[bpmuser@uat-bpmapp UpgradeMedia]$ pwd

/bpmapp/bpmuser/UpgradeMedia

[bpmuser@uat-bpmapp UpgradeMedia]$ chmod 744 -R *

 Upgrading Installation Manager to from v1.8 to v1.9

Cd /bpmapp/bpmuser/UpgradeMedia/IM64

./userinst
Click on restart IM to verify the verion.
 - After successful update, run the installation manager from below command:

cd IBM/InstallationManager/eclipse/

./IBMIM

- Verify the version from Help - > About Installaiton Manager

Add repository as shown in below screenshot:
- Remove the previous selected repositories if any
- Click on update from the main page of installation manager
 --------------------------- this step is optional for WAS version verification --------
- Start the services, validate Websphere version:

- Create an ICM case, and verify BPM is working as expected by moving case one step.

Stop the application services if started.

 Now we will upgrade BPM 8.6 to BAW 20.0.0.1

- Remove the previous selected repositories if any

- Provide the zip file in repository as shown in picture below

- Click Update on installation Manage home screen

 Now, we create/upgrade the BPM databases.

Created following directory on BPM database server:

/bpmdb/bpmdb/BAWscripts

Response File

Move the response.xml file to bpm app server review and update if any:
 - Execute below command:

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -update -profile DmgrProfile -de SBPPROD -

caseConfigure -responseFile /bpmapp/bpmuser/caseConfigureResponseFile.xml

- After successful execution of above command, go in following directory and check files:

/bpmapp/bpmuser/ibm/BPM/v8.5/profiles/DmgrProfile/dbscripts/PSCell1.SBPPROD/DB2/CPEDB
- Copy these files to BPM database server, we need to execute them.

Go on database server, and go in the directory where files are copied.

 Review the script file and update
createDatabase_ECM.sql
createDatabase_ECM.sh (adjust the directories as per env)

- ./createDatabase_ECM.sh
 Review and update directory as per env
createTablespace_ECM_DOS.sql
- db2 -tvsf createTablespace_ECM_DOS.sql
 Review and update directory as per env

createTablespace_ECM_TOS.sql

db2 -tvsf createTablespace_ECM_TOS.sql

 Review and update directory as per env

createTablespace_ICN.sql

- db2 –tvsf createTablespace_ICN.sql

- /bpmapp/bpmuser/ibm/BPM/v8.5/bin/DBUpgrade.sh -validate -profileName DmgrProfile -de
SBPPROD -bpmSchemaAdminUser bpmdbusr -bpmSchemaAdminPassword sbp@dmin
- Execute below command:
/bpmapp/bpmuser/ibm/BPM/v8.5/bin/DBUpgrade.sh -profileName DmgrProfile -de SBPPROD
Upgrade process completed.
Start the services:

- Execute below commad:

cd /bpmapp/bpmuser/ibm/BPM/v8.5/profiles/DmgrProfile/bin
sh startManager.sh (Took 40 minutes)

- Execute below command:

cd /bpmapp/bpmuser/ibm/BPM/v8.5/profiles/Node1Profile/bin
sh startNode.sh
Command took 5-10 min to complete
 Stop the all services and start using standard start stop script.

Post Upgrade:

Stop All services and make changes in following file:

- Add following entry in 100Custom.xml

100Custom File path:

/bpmapp/bpmuser/ibm/BPM/v8.5/profiles/DmgrProfile/config/cells/PSCell1/nodes/Node1/
servers/AppClusterMember1/process-server/config

Changes to be made:

<system-maintenance-monitor merge="replace" enabled="true">

<monitor type="NAMED_SNAPSHOTS" merge="replace" enabled="true"
servertype="PS">
<critical-threshold>1050</critical-threshold>
<warning-threshold>800</warning-threshold>
<prevent-lifecycle-action>INSTALL</prevent-lifecycle-action>
</monitor>
</system-maintenance-monitor>

<bpd-engine>
<enable-legacy-behavior-for-dur-msg-when-msg-event-is-in-
loop merge="replace">true</enable-legacy-behavior-for-dur-
msg-when-msg-event-is-in-loop>
</bpd-engine>
 Apply Fix-pack patch 8.6.20020001-WS-BPM-IFJR62453.zip Size = 247KB

1. Stop the apps services.

2. Copy the patch to 8.6.20020001-WS-BPM-IFJR62453.zip to
/bpmapp/bpmuser/UpgradeMedia

3. Open Installation manager and Provide the zip file of fix pack in Add repository section of
Installation Manager. Click Update on main screen of installation manager.

[bpmuser@uat-bpmapp eclipse]$ pwd

/bpmapp/bpmuser/IBM/InstallationManager/eclipse
[bpmuser@uat-bpmapp eclipse]$ ./IBMIM
Once done with above step, please run below command (Path need to be changed
according to environment)

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile DmgrProfile

Now run the following command:

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile Node1Profile

Start BPM application services.

 Applying 2 fix packs by IBM and TL team 8 Dc 2020 on UAT BPM APPS

1. 8.6.20020001-WS-BPM-IFJR62974.zip this fix pack was unistaled and applied new one by
IBM
2. 8.6.20020001-WS-BPM-IFJR62480.zip

Step 1: Stop the BPM UAT APPS services:

Step 2: copy the fix pack files.

Applying fix pack 8.6.20020001-WS-BPM-IFJR62480.zip

Step 3: Open Installation manager and Provide the zip file of fix pack in Add repository section of
Installation Manager. Click Update on main screen of installation manager.

Remove the old repositories if any.

[bpmuser@uat-bpmapp eclipse]$ pwd

/bpmapp/bpmuser/IBM/InstallationManager/eclipse
[bpmuser@uat-bpmapp eclipse]$ ./IBMIM
Clink apply and ok

Click on upgrade
Once done with above step, please run below command (Path need to be changed
according to environment)

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile DmgrProfile

Now run the following command:

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile Node1Profile

 Now applying fix pack 8.6.20020001-WS-BPM-IFJR62974.zip

Open Installation manager and Provide the zip file of fix pack in Add repository section of Installation
Manager. Click Update on main screen of installation manager.

Remove the old repositories if any.

[bpmuser@uat-bpmapp eclipse]$ pwd

/bpmapp/bpmuser/IBM/InstallationManager/eclipse
[bpmuser@uat-bpmapp eclipse]$ ./IBMIM
Once done with above step, please run below command (Path need to be changed
according to environment)

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile DmgrProfile

 Now run the following command:

/bpmapp/bpmuser/ibm/BPM/v8.5/bin/BPMConfig.sh -upgrade -profile Node1Profile

Start the PBM APPS Services.

Steps by IBM PMR: (How to open BPM Document Store Acce in BAW 20.0.0.1)

1.Go to the dmgr machine, and navigator to the folder

2.BPM_INSTALL_ROOT/CaseManagement/configure and run the configmgr In the eclipse windows, click

open profile which is located at dmgr_profile_root/CaseManagement_DE_name/profiles/ICM_dev or
ICM_proc

3.then open the first task (Register the Administrator Console for Content Engine (ACCE) Plug-in) and
run it
Open the case management dmgr proifle:

Double clink on ICM_prod.cfgp

Double click on task 1.

Register the Administrator Console for Content Engine (ACCE) Plug-in and run.
On successful completion. Restart bpm apps services.

------ End of Document --------------

Execution of RegenTheme Commands:

After starting the server, Following commands should be executed on BPM application server:

/bpmapp/bpmuser/ibm/BPM/v8.5/profiles/Node1Profile/bin/wsadmin.sh -conntype SOAP -port 8881 -

host uat-bpmapp -user wasadmin -password sbp@dm1n -lang jython
AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'BID', '-targetContainerSnapshotAcronym',
'BID6', '-outputFile', '/bpmapp/bpmuser/regenThemeLogBID1.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'BID', '-targetContainerSnapshotAcronym',

'BID5.2', '-outputFile', '/bpmapp/bpmuser/regenThemeLogBID2.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'BPMA', '-targetContainerSnapshotAcronym',

'V0.0.40', '-outputFile', '/bpmapp/bpmuser/regenThemeLogBPMA1.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'BPMA', '-targetContainerSnapshotAcronym',

'V0.0.34', '-outputFile', '/bpmapp/bpmuser/regenThemeLogBPMA2.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'DT', '-targetContainerSnapshotAcronym',

'V0.29.U', '-outputFile', '/bpmapp/bpmuser/regenThemeLogDT.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ECPM', '-targetContainerSnapshotAcronym',

'V1.07.U', '-outputFile', '/bpmapp/bpmuser/regenThemeLogECPM.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ERD', '-targetContainerSnapshotAcronym',

'V0.4.27', '-outputFile', '/bpmapp/bpmuser/regenThemeLogERD.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'FT', '-targetContainerSnapshotAcronym',

'V0.4.99', '-outputFile', '/bpmapp/bpmuser/regenThemeLogFT.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'IACD', '-targetContainerSnapshotAcronym',

'V1.03.4', '-outputFile', '/bpmapp/bpmuser/regenThemeLogIACD1.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'IACD', '-targetContainerSnapshotAcronym',

'V1.48.0', '-outputFile', '/bpmapp/bpmuser/regenThemeLogIACD2.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ICM', '-targetContainerSnapshotAcronym',

'V3.49.U', '-outputFile', '/bpmapp/bpmuser/regenThemeLogICM1.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ICM', '-targetContainerSnapshotAcronym',

'V1.00.I', '-outputFile', '/bpmapp/bpmuser/regenThemeLogICM2.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ICM', '-targetContainerSnapshotAcronym',

'V0.30.0', '-outputFile', '/bpmapp/bpmuser/regenThemeLogICM3.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'ICM', '-targetContainerSnapshotAcronym',

'V0.47UA', '-outputFile', '/bpmapp/bpmuser/regenThemeLogICM4.txt'])

AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'RA', '-targetContainerSnapshotAcronym',

'V0.0.5P', '-outputFile', '/bpmapp/bpmuser/regenThemeLogRA.txt'])
AdminTask.BPMRegenTheme(['-targetContainerAcronym', 'TM', '-targetContainerSnapshotAcronym',
'V0.0.15', '-outputFile', '/bpmapp/bpmuser/regenThemeLogTM.txt'])

Security Setting Command:

Following command should be executed after stopping the server:

/bpmapp/bpmuser/ibm/BPM/v8.5/profiles/DmgrProfile/bin/wsadmin.sh -conntype none -lang jython

AdminTask.setBPMProperty(['-de', 'SBPPROD', '-name', 'Security.ContentSecurityPolicyHeaderValue', '-

value', "default-src 'self' 'unsafe-inline' 'unsafe-eval' *.sbp.org.pk; frame-ancestors 'self' 'unsafe-inline'
'unsafe-eval' *.sbp.org.pk; img-src 'self' 'unsafe-inline' 'unsafe-eval' *.sbp.org.pk data:; font-src 'self'
'unsafe-inline' 'unsafe-eval' fonts.gstatic.com *.sbp.org.pk"])

AdminConfig.save()

exit