454 - 7 - PD Accepted - AS

1
Installation, Upgrade and Configuration of IBM FileNet Information Management Software on

RedHat Linux 8.0, Windows 10 and IBM Cloud platforms - IBM FileNet ECM and Case Manager
Installation on RHEL 8.0
CHAPTER 7
IBM BAW 21.0.3
Upgrade Installation
from BAW 18.6.1.19002
Introduction
This chapter covers the upgrade installation of IBM BAW 21.0.3 (Business Automation
Workflow).
It will upgrade to version 21.0.3 from 18.0.0.x, 19.0.0.x, 20.0.0.x, or version 21.0.1.
There is an IBM support URL as follows which describes this procedure:

https://www.ibm.com/support/pages/node/6507343, and specifically for upgrades:
https://www.ibm.com/support/pages/node/6507347
Note: This upgrade only works successfully from Db2 Version 10.5.0.0 (unless the
option to defer schema creation is set).
The starting point of this upgrade is based on the installation of Business Workflow
Automation Version 8.6.1.19.0.0.2.
The installation of the Db2 database for this base version is covered in the IBM DB2
Administration Guide (ISBN 978-93-55511-669) Chapter 5, IBM Workflow Center 8.6 for IBM
BAW 18.0 Database Creation , which covers the creation of the four DB2 databases used by
the BAW system, and the ResearchGate download, with the link,
https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation phase1 preprint
with install of IBM Workflow Center 8.6.1.19002, which covers the installation and fix pack
upgrade of IBM Business Automation Workflow to version 8.6.1.19.0.0.2.
For IBM Business Automation Workflow 21.0.3., before the upgrade, at least 18 GB of free
disk space is required, including temporary disk space.
2
IBM Process Federation Server (PFS) includes an embedded Elasticsearch instance,

indexers, retrievers, REST services, and a relational database. For federating the IBM
Business Automation Workflow installed on-premise with IBM Process Federation Server
containers installed using the "OpenShift with Platform UI service" option enabled use the
IBM Support link procedure: https://www.ibm.com/support/pages/node/6514469
Structure
In this chapter, we will discuss the following topics:
• Restarting and upgrading the system
• Transferring the downloaded upgrade software packages

• Using the IBM Installation manager to run the upgrade
o IMPORTANT post installation upgrade
• Adding an unmanaged node
• Installing a stand-alone installation in IBM BPM 8.x
• Creating the PFS process federation server on Liberty

• IBM Business process management V8.5.7
• Advanced Linux custom using the command line with DB2 Express
o Settings using the Advanced BPMConfig installation
Objectives
After studying this unit, you will be able to download and install the IBM Business
Automation Workflow version 21.0.3 and identify the supporting components for installation
and configuration.
7.1 IBM Workflow Center 8.6 Deleted: Centre
The following link on the base VMWare system, shows the current status of IBM BAW 8.6,
before the upgrade, it includes the BAW version number, version 8.6.1.19002:
https://ecmukdemo8:9447/ProcessCenter/repository/com.lombardisoftware.repository.Rep
ository/Repository.jsp?v=8.6.1.19002
3
7.1.1 Restarting and upgrading the system.
The original RHEL Linux 8.0 system build for Business Automation Workflow Center 8.6 is Deleted: Centre
described in the step-by step free download word document on ResearchGate, listed in the
introduction to this chapter. This base installation is used as the starting point for the IBM
Business Automation Workflow upgrade which is described in this Chapter.
The following link is useful for a traditional upgrade of a non-container installation:
https://www.ibm.com/docs/en/baw/20.x?topic=v2103-traditional-installing-configuring-
migrating-business-automation-workflow
First, we need to back up the current VMWare for the ECMUKDEMO8 server which hosts the
base system, since we have to selectively delete install package .bin files and the original
zipped install files to provide the additional space required. There are also old kernel installs
to be removed to provide the 25 Mbytes of space required on the /boot partition.
1. Stop the IBM Case Manager and IBM Content Navigator Application Server using the
following commands.
[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv02/bin
[root@ECMUKDEMO8 bin]# ./stopServer.sh server1
A pop-up window prompts for the WebSphere user name and password (wasadm/filenet on
this system)
2. Stop the IBM FileNet Content Engine Application Server using the following
commands.
[root@ECMUKDEMO8 bin]# ./stopServer.sh server1
A pop-up window prompts for the WebSphere user name and password (wasadm/filenet on
this system)
3. Stop the deployment environment as shown in Figure 7.1.

https://ecmukdemo8:9043/ibm/console/login.do?action=secure
Formatted: Centred
Figure 7.1: The deployment environment is stopped
4. Stop the node agent.

4
[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/bin

[root@ECMUKDEMO8 bin]# ./stopNode.sh
(Note: Enter wasadm/filenet in the pop-up window)
5. Stop the deployment manager.
[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/bin

[root@ECMUKDEMO8 bin]# ./stopManager.sh
(Note: Enter wasadm/filenet in the pop-up window)
6. Stop the DB2 Database

[db2inst1@ECMUKDEMO8 ~]$ db2 CONNECT TO CPEDB
Database Connection Information
Database server = DB2/LINUXX8664 11.1.0

SQL authorization ID = DB2INST1
Local database alias = CPEDB
[db2inst1@ECMUKDEMO8 ~]$ db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS

DB20000I The QUIESCE DATABASE command completed successfully.
[db2inst1@ECMUKDEMO8 ~]$ db2 CONNECT RESET
DB20000I The SQL command completed successfully.
[db2inst1@ECMUKDEMO8 ~]$ db2 DEACTIVATE DATABASE CPEDB
SQL1495W Deactivate database is successful
[db2inst1@ECMUKDEMO8 ~]$ db2stop
[db2inst1@ECMUKDEMO8 ~]$ db2 list applications
7. Update the RHEL 8.0 Linux server with the latest packages using dnf update.
The first time this was run it reported that there was insufficient /boot disk space.
First the current Linux kernel version was checked :
[root@ECMUKDEMO8 boot]# uname -r
4.18.0-348.12.2.el8_5.x86_64
8. The following command was used to remove the old Linux kernel from the /boot
system, as shown in Figure 7.2: Formatted: Font: Italic
yum remove kernel-4.18.0-305.12.1.el8_4.x86_64
Figure 7.2: The original old Linux kernel is removed

5
9. The command df -k was run to check that the /boot mount point disk area had
enough space. The dnf update command was then run successfully, as shown in Figure Formatted: Font: Italic
7.3.
Figure 7.3: The dnf update command now completes successfully

10.Reboot the system at this point, as shown in Figure 7.4: Deleted: !
Formatted: Font: Italic
Figure 7.4: The hostnamectl command shows that the RHEL 8.0 is updated to version 8.6
11.Start the DB2 Database.
[root@ECMUKDEMO8 ~]# su - db2inst1
Last login: Wed Sep 28 11:37:32 PDT 2022 on pts/0
[db2inst1@ECMUKDEMO8 ~]$ db2start
09/28/2022 14:27:02 0 0 SQL1063N DB2START processing was successful.
SQL1063N DB2START processing was successful.
[db2inst1@ECMUKDEMO8 ~]$
12. Start the node agent.

[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/bin
[root@ECMUKDEMO8 bin]# ./startNode.sh

CWUPO0001I: Running configuration action detectNewProducts.ant
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/Node1Profile/logs/nodeagent/startServer.log
ADMU0128I: Starting tool with the Node1ProfileRHEL8 profile
ADMU3100I: Reading configuration for server: nodeagent
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server nodeagent open for e-business; process id is 21260
[root@ECMUKDEMO8 bin]# pwd
/opt/IBM/WebSphere/AppServer/profiles/Node1Profile/bin
[root@ECMUKDEMO8 bin]#
13. Start the deployment manager.
[root@ECMUKDEMO8 bin]# pwd

/opt/IBM/WebSphere/AppServer/profiles/Node1Profile/bin
6
[root@ECMUKDEMO8 bin]# cd ../../DmgrProfile/bin
[root@ECMUKDEMO8 bin]# ./startManager.sh
/opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/logs/dmgr/startServer.log
ADMU0128I: Starting tool with the DmgrProfileRHEL8 profile
ADMU3100I: Reading configuration for server: dmgr
ADMU3000I: Server dmgr open for e-business; process id is 21706
14. Start the deployment environment
https://ecmukdemo8:9043/ibm/console/login.do?action=secure
15. Select Deployment Environments in the menu tree as shown in Figure 7.5:
Figure 7.5: The current status of the IBM Business Automation Workflow, V19.0.0.2
The web page should be refreshed after around 5 minutes to see the started applications as
shown in Figure 7.1 (there are a large number of web application components!). Deleted: -
The IBM Business Automation Workflow Center web application is loaded to check the Formatted: Font: Italic
starting point of the system is running correctly: Deleted: Centre
https://ecmukdemo8:9447/ProcessCenter/
giving the security warning as shown in Figure 7.6:
Formatted: Centred
Figure 7.6: The Advanced command option is selected to accept the risk
7
This redirects to the full URL as follows:
https://ecmukdemo8:9447/ProcessCenter/repository/com.lombardisoftware.repository.Rep
ository/Repository.jsp?v=8.6.1.19002
The web page appears as illustrated in Figure 7.7. Formatted: Font: Palatino Linotype
Formatted: Font: Palatino Linotype, Italic
Formatted: Font: Palatino Linotype
Figure 7.7: The IBM Workflow Center 8.6.1.19002 is loaded as expected

The first listed item, Audit Master for BS5750/ISO9000 Audit Process App is clicked to open it
as shown in Figure 7.8: Formatted: Font: Italic
8
Figure 7.8 The Audit Master for BS5750/ISO9000 Audit Process Workflow
Start the IBM FileNet Content Engine Application Server.
[root@ECMUKDEMO8 bin]# ./startServer.sh server1
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3000I: Server server1 open for e-business; process id is 11054
Start the IBM Case Manager and IBM Content Navigator Application Server.
[root@ECMUKDEMO8 bin]# ./startServer.sh server1
/opt/IBM/WebSphere/AppServer/profiles/AppSrv02/logs/server1/startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: server1
9
ADMU3000I: Server server1 open for e-business; process id is 11621
7.1.2 Transferring the downloaded upgrade software

packages
The three downloaded software packages are copied to the RedHat 8.6 Linux server, using
the VMware, /mnt/hgfs mount point, as shown in Figure 7.9: Formatted: Font: Italic
Figure 7.9: The installation packages for IBM Business Automation 21.0.3 are copied
The installation packages are unpacked:
[root@ECMUKDEMO8 BAW_21_0_3]# tar -zxvf BAW_Enp_21.0.3_Lnx641.tar.gz
[root@ECMUKDEMO8 BAW_21_0_3]# tar -zxvf BAW_Etp_21.0.3_Lnx64_2of3.tar.gz
[root@ECMUKDEMO8 BAW_21_0_3]# tar -zxvf BAW_Etp_21.0.3_Lnx64_3of3.tar.gz
The Fix Packs for the Process Federation Server and Workflow components, are shown in
Figure 7.10, after downloading from the IBM Fix Central web site:
Figure 7.10: The initial location of the 21.0.3 Fix packs

The IBM Business Automation 21.0.3 Fix Pack upgrade software packages are copied to the
Install_21_03 sub-folder which is mapped to the RedHat Linux RHEL8 VMWare server as
illustrated in Figure 7.11:
10
Figure 7.11: The IBM Business Automation Workflow version 21.0.3 packages are copied.
The Linux bash cp copy command is used to copy the IBM Business Automation v 21.0.3 FixPack
zipped files from the /mnt/hgfs VMware mapped drive to the installation folder as shown in
Figure 7.12:
Figure 7.12: The IBM BAW v 21.0.3 Fix Packs are copied to the Linux server
The unpacked FixPack repository.config file is selected for loading using the Browse
command button after choosing the IBM Installation Manager File| Preferences menu
item as shown in Figure 7.13:
11
Figure 7.13: The IBM BAW Fix Pack 21.0.3 repository.config file is selected
The Update Packages list is displayed for WebSphere and the IBM BPM 21.0.3 versions in the
IBM Installation Manager Update command option window as illustrated in Figure 7.14:
Figure 7.14: The IBM Installation Manager Update command window lists the updates
The IBM Fix Central web page shows the latest available Fix Packs for IBM Business
Automation Workflow as shown in Figure 7.15:
12
Figure 7.15: The Installed Version option is used to select the current base version
The search results show the latest Fix pack first, which is for IBM Business Automation
Workflow version 21.0.3.1 shown in Figure 7.16:
Figure 7.16: The latest Fix pack for IBM Business Automation Workflow, version 21.0.3.1
The search results also show the required Fix Packs for the base IBM Business Automation
Workflow Version 21.0.3 and the base IBM Process Federation Server version 21.0.3, which we
select for download as shown in Figure 7.17:
Figure 7.17: The required Fix Packs for the base IBM Business Automation Workflow Version 21.0.3 and the base IBM
Process Federation Server version 21.0.3
The IBM Download Director option is used to download the selected Fix Packs as shown in
Figure 7.18:
13
Figure 7.18: The IBM Download Director is used to download the required Fix Packs
The Details command button is used after IBM Download Director completes to display the
downloaded Fix Pack for IBM Business Automation Workflow version 21.0.3.1 as illustrated
in Figure 7.19:
Figure 7.19: The downloaded Fix Pack for IBM Business Automation Workflow version 21.0.3.1
The Find by text option for searching in the IBM Software Access Catalog web site is shown
in Figure 7.20:
14
Figure 7.20: The Find by text option for searching in the IBM Software Access Catalog
The resulting list is scrolled down to select the required Linux version components of IBM
Business Automation Workflow we need for upgrading our existing system as illustrated in
Figure 7.21:
Figure 7.21: The required Linux version components of IBM Business Automation Workflow 21.0.3 for download
The IBM Download Director Details command button is used to display the downloaded IBM
Business Automation Workflow 21.0.3 installation files as shown in Figure 7.22:
15
Figure 7.22: The downloaded IBM Business Automation Workflow 21.0.3 installation files
7.1.3 Using the IBM Installation Manager to run the

Upgrade
The first install attempt to run the IBM Installation Manager is shown below:
[root@ECMUKDEMO8 IM64]# cd /mnt/sda4/installs/BAW_21_0_3/IM64
[root@ECMUKDEMO8 IM64]# ./install

\00:02.49 ERROR [main] com.ibm.cic.agent.internal.ui.AgentUI reportStatus
Installation Manager 1.9.2.1 (internal version: 1.9.2001.20211222_1411) is
already installed at location "/opt/IBM/InstallationManager/eclipse" and is using
"/var/ibm/InstallationManager" for its data location. Use the installed Installation
Manager.
[root@ECMUKDEMO8 IM64]#
The downloaded version of the IBM Installation Manager has detected an existing version
which we must use for the upgrade, located in the /opt/IBM/InstallationManager/eclipse
directory.
So, we use the following commands:

cd /opt/IBM/InstallationManager/eclipse
ulimit -n 8192
See Pages 484 to 514 of the ResearchGate download, with the link,
with install of IBM Workflow Center 8.6.1.19002,for the complete screen shots showing the
installation procedures which we outline(we will just show the updated screen versions,
where they differ from the 19.0.0.2 upgrade).
16
We can launch the IBM Installation Manager using the ./launcher program:
./launcher
1. First, we install the PFS (Process Federation Server) Fix Pack system. Create a PFS
sub-directory for the 21.0.3 version, under the /opt/IBM/Installs directory using the root
user:
[root@ECMUKDEMO8 Installs]# cd /opt/IBM/Installs
[root@ECMUKDEMO8 Installs]# mkdir PFS21
[root@ECMUKDEMO8 Installs]# cd PFS21
And copy the downloaded PFS base installation and fix packs as shown in Figure 7.23:
Figure 7.23: The IBM PFS base installation Fix Packs are copied to Linux
[root@ECMUKDEMO8 PFS21]# cd /opt/IBM/Installs/PFS21
[root@ECMUKDEMO8 PFS21]# cp /mnt/hgfs/Install_21_03/BAW_FixPacks_To_21.0.3/*.zip .
[root@ECMUKDEMO8 PFS21]# cp /mnt/hgfs/Install_21_03/BAW_Base_System/Process*.gz .
Unpack the IBM PFS 21.0.3 tar.gz file
tar -zxvf Process_Fed_21.0.3_Lnx64.tar.gz
Remove the unpacked gzip file to save space
rm -rf Process_Fed_21.0.3_Lnx64.tar.gz
Run the installer and get the Installation screen as shown in Figure 7.24.
./installPFS.sh
17
Figure 7.24: The IBM Installation Manager displays the versions to install
(Note: Ignore the Check for Other Versions, Fixes and Extensions button!) Click on
the Next command button as illustrated in Figure 7.25.
Figure 7.25: The Next command is selected to install the IBM WebSphere Fixes
Click the I accept radio button and the Next|command button as illustrated in Figure 7.26.
18
Figure 7.26: The I accept… License agreements is selected and Next clicked
This IBM License acceptance gives access to use the supporting programs as listed:
• IBM API Connect Professional
• IBM Db2 Standard Edition

• IBM Installation Manager and Packaging Utility for the Rational Software Platform
• IBM Support Assistant DataCollector

• IBM Security Directory Suite Limited Edition
• IBM WebSphere Application Server Network Deployment
• IBM FileNet Content Manager
• IBM Cognos Real-time Monitoring
• IBM FileNet eForms
• IBM Content Navigator
• IBM Watson Explorer Advanced Edition
• IBM WebSphere Liberty
• IBM Cloud Pak for Automation
• IBM Event Streams

19
(Note: Only to support the Licensee's use of the Principal Program under
the Agreement).
Also, the License allows the use of the following Functions:
• Case Manager Crawler of Analytical Components
(only for the purpose of building Analytics Collections (of IBM Watson Explorer
Advanced Edition))
• Content Analytics Miner
(only for the purpose of analyzing the Analytics Collections (of IBM Watson Explorer
Advanced Edition))
o Business Automation Insight (of IBM Cloud Pak for Automation)

o Business Automation Application Engine (of IBM Cloud Pak for Automation)
o IBM Business Automation Navigator (of IBM Cloud Pak for Automation)
A new WebSphere Liberty package group is selected and a new folder path:
/opt/IBM/WebSphere/Liberty2
The English language is the only language available in this upgrade package, so Next
is clicked. The IBM Business Automation Workflow Non-Production License is
selected as illustrated in Figure 7.27:
20
Figure 7.27: The Non-Production License option is selected and then Next
Leave the Recommended radio button option selected and Click Next as shown in Figure 7.28:
Figure 7.28: The default Recommended installation option is left and Next clicked
Note the End Of Support for Java 1.7, then we click Next, we click on Install as shown in
Figure 7.29:
21
Figure 7.29: The installation options are reviewed and the Install command clicked
Click Finish.
Fix Packs are then added to the base:
Unzip the workflow.2103.delta.repository.zip repository:

mkdir PFS_2103
cd PFS_2103
mv ../pfs.2103.delta.repository.zip .
unzip pfs.2103.delta.repository.zip
rm -rf *.zip
ulimit -n 8192
Remove the unzipped file and load installation manager
./launcher
Select
File>Preferences
The Update icon is clicked in the IBM Installation Manager;
Then select the unpacked Fix Pack repository.config file.
Install Fix Pack workflow.21031.delta.repository.zip
[root@ECMUKDEMO8 PFS_2103]# cd ..
[root@ECMUKDEMO8 PFS21]# mkdir PFS_21031

22
[root@ECMUKDEMO8 PFS21]# cd PFS_21031
[root@ECMUKDEMO8 PFS_21031]# cp
/mnt/hgfs/Install_21_03/BAW_FixPacks_To_21.0.3/workflow.21031.delta.repository.zip .
unzip workflow.21031.delta.repository.zip
[root@ECMUKDEMO8 PFS_21031]# rm workflow.21031.delta.repository.zip
rm: remove regular file 'workflow.21031.delta.repository.zip'? y

[root@ECMUKDEMO8 PFS_21031]#
Remove the unzipped file and load installation manager

./launcher
Select File|Preferences and browse to the unpacked repository.config file as shown in Figure Formatted: Font: Italic
7.30.
Figure 7.30: The IBM WebSphere Liberty fix packs are selected and the Next is clicked
The scrollable License text box, displays the Supporting Programs and deployed software
packages as shown in Figure 7.31:
23
Figure 7.31: The Supporting Programs and Deployment software lists.

The size and status of the downloading packages in the IBM Installation Manager are
displayed as illustrated in Figure 7.32:
Figure 7.32: The downloading software size and status is shown

In the /opt/IBM/Installs/PFS subdirectory:
[root@ECMUKDEMO8 PFS21]# cd /opt/IBM/Installs/PFS21
mkdir WF_2103
cd WF_2103
Move the workflow.2103.delta.repository.zip file to the subdirectory:
mv ../workflow.2103.delta.repository.zip .
and then
unzip workflow.2103.delta.repository.zip
Remove the zipped file after unpacking it to make space:
rm -rf workflow.2103.delta.repository.zip
Launch the IBM Installation Manager as for the first upgrade package
ulimit -n 8192
24
./launcher
Next, we can open the new Application servers web ports:
firewall-cmd --zone=public --permanent --add-port=2815/tcp
firewall-cmd --reload
7.1.3.1 IMPORTANT post Installation upgrade

After the installs are complete run:
cd /opt/IBM
chown wasadm:root WebSphere -R
chmod 775 WebSphere -R
(Otherwise, the profiles will be unable to restart!)
7.1.4 Adding an Unmanaged Node

Next follow the procedures on pages 517 through 521 of the ResearchGate download, with the link,
with install of IBM Workflow Center 8.6.1.19002,to add an unmanaged Node.
7.1.5 Installing a stand-alone installation in IBM BPM

8.x
Next, we follow the procedures on pages 521 through 535 of the ResearchGate download, with the
link, https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation phase1
preprint with install of IBM Workflow Center 8.6.1.19002,to Install the IBM Business Process
Manager web application version 8.6.
7.1.6 Creating the PFS Process Federation Server on

Liberty
Next, we follow the procedures on pages 536 through 544 of the ResearchGate download, with the
link, https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation phase1
preprint with install of IBM Workflow Center 8.6.1.19002, to Create the PFS Process Federation
Server and the four databases it uses.
7.1.7 IBM Business Process Management V8.5.7

Next, we follow the procedures on pages 545 through 565 of the ResearchGate download, with
the link, https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation phase1
25
preprint with install of IBM Workflow Center 8.6.1.19002,to update the standalone Liberty
Web Server with IBM Business Process Management components, V 8.5.7.
7.1.8 Advanced Linux Custom using the Command Line

with DB2 Express
Next, we follow the procedures on pages 566 through 590 of the ResearchGate download, with
the link, https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation phase1
preprint with install of IBM Workflow Center 8.6.1.19002,to configure and run the
BPMConfig.sh script file.
7.1.8.1 Settings using the Advanced BPMConfig installation

The procedures Starting from page 566 through to page 590 of the ResearchGate download,
with the link, https://doi.org/10.13140/RG.2.2.27345.89440 - IBM BAW 18.0 Installation
phase1 preprint with install of IBM Workflow Center 8.6.1.19002, which describes the editing
of the BPMConfig.properties file and the running of the BPMConfig.sh shell script.
Conclusion
In this chapter, we covered the “Bill of Materials” and the upgrade installation of IBM BAW
21.0.3 (Business Automation Workflow).
It will upgrade to version 21.0.3 from 18.0.0.x, 19.0.0.x, 20.0.0.x, or version 21.0.1. We also
covered the supporting software required for the related IBM Information Management
Products to be installed, with the download site URLs, Product Codes, Descriptions and size
and name of the download gzip tar files for each Software Download. In the next Chapter 8,
Cloud Based Systems, we cover the IBM Cloud based systems; IBM Cloud Private and the
IBM FileNet P8 CPIT Installation; Installation of Eclipse Codewind, with Docker Compose
using IBM Cloud Private CE and IBM Cloud Private P8 Docker Container CPIT Installation
for the preparation of a new Object Store.
Points to Remember
• Remember to back up the whole system before upgrading!
• Remember, this upgrade to version 21.0.3 only works successfully from Db2 Version
10.5.0.0 (unless the option to defer schema creation is set).
• Ignore the Check for Other Versions, Fixes and Extensions button on IBM Installation
Manager for the upgrade.
• The supporting IBM Software Packages are only included to support the Licensee's
use of the Principal IBM Upgrade Program under the Agreement.
26
• The End Of Support for Java 1.7, means the upgrade to Java 1.8 is required.
• DB2 11.1 is the earliest fully supported Database version.

(IBM announced Continuing Support for Db2 versions 8.2, 9.1 and 9.5 will be discontinued on
September 30, 2022.)
See https://www.ibm.com/support/pages/db2-continuing-support
Multiple Choice Questions

1) What is the earliest supported IBM Business Automation Workflow (BAW) major
version for the upgrade to IBM BAW 21.0.3?
a) 19.0.0.x
b) 18.0.0.x
c) 21.0.1
d) 20.0.0.x
2) What is the first step you should perform before starting the actual upgrade to IBM
Business Automation Workflow 21.0.3 on a Linux RHEL version 8.0 system?
a) Restart and upgrade the system.
b) Stop the deployment environment.
c) Upgrade the Operating System environment to RHEL version 8.6
d) Backup the existing working system.
3) In what order should you start the IBM Business Automation System components?
a) Start the node agent, Start the DB2 Database, Start the deployment manager, Start
the deployment environment
b) Start the node agent, Start the deployment manager, Start the deployment
environment, Start the DB2 Database
c) Start the DB2 Database, Start the node agent, Start the deployment manager, Start
d) Start the DB2 Database, Start the deployment environment, Start the node agent,
Start the deployment manager
4) What is the earliest DB2 version fully supported by IBM (as of January 2022)?
a) DB2 10.5
b) DB2 11.1
c) DB2 11.5
d) DB2 9.5
Multiple Choice Answers Formatted: Heading 1 [BPB HEB], None, Don't keep
with next, Don't keep lines together
b) 18.0.0.x
d) Backup the existing working system
c) Start the DB2 Database, Start the node agent, Start the deployment manager, Start
b).DB2 11.1
27
Questions
1. How much disk space would you provision for the downloads recommended in this
Chapter? (Hint: this is specifically defined including the temporary disk space
required).
2. What web site could you browse to view any IBM software compatibility issues and
limitations for products which are used by IBM Business Automation Workflow
upgrade?
3. What import post-installation upgrade steps must you take to ensure the WebSphere
application can run correctly?
4. Where would you find the procedures to create the IBM PFS Process Federation Server
and the four databases it uses?
Key Terms
• CPEDB- Content Platform Engine Database - Used for the IBM FileNet Content server
software service Database name
• API The Application Programmer Interface (API)
• PFS – IBM Business Automation, Process Federation Server

454 - 7 - PD Accepted - AS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

454 - 7 - PD Accepted - AS

Uploaded by

Copyright:

Available Formats

1

Installation, Upgrade and Configuration of IBM FileNet Information Management Software on

There is an IBM support URL as follows which describes this procedure:

IBM Process Federation Server (PFS) includes an embedded Elasticsearch instance,

• Restarting and upgrading the system

• Transferring the downloaded upgrade software packages

o IMPORTANT post installation upgrade

• Adding an unmanaged node

• Installing a stand-alone installation in IBM BPM 8.x

• Creating the PFS process federation server on Liberty

o Settings using the Advanced BPMConfig installation

7.1 IBM Workflow Center 8.6 Deleted: Centre

The following link is useful for a traditional upgrade of a non-container installation:

3. Stop the deployment environment as shown in Figure 7.1.

Figure 7.1: The deployment environment is stopped

4. Stop the node agent.

[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/Node1Profile/bin

5. Stop the deployment manager.

[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/DmgrProfile/bin

6. Stop the DB2 Database

Database Connection Information

Database server = DB2/LINUXX8664 11.1.0

[db2inst1@ECMUKDEMO8 ~]$ db2 QUIESCE DATABASE IMMEDIATE FORCE CONNECTIONS

yum remove kernel-4.18.0-305.12.1.el8_4.x86_64

Figure 7.2: The original old Linux kernel is removed

Figure 7.3: The dnf update command now completes successfully

12. Start the node agent.

[root@ECMUKDEMO8 bin]# ./startNode.sh

13. Start the deployment manager.

[root@ECMUKDEMO8 bin]# pwd

starting point of the system is running correctly: Deleted: Centre

Figure 7.7: The IBM Workflow Center 8.6.1.19002 is loaded as expected

7.1.2 Transferring the downloaded upgrade software

Figure 7.10: The initial location of the 21.0.3 Fix packs

7.1.3 Using the IBM Installation Manager to run the

[root@ECMUKDEMO8 IM64]# ./install

So, we use the following commands:

• IBM Db2 Standard Edition

• IBM Support Assistant DataCollector

• IBM FileNet Content Manager

• IBM Cognos Real-time Monitoring

• IBM FileNet eForms

• IBM Content Navigator

• IBM Watson Explorer Advanced Edition

• IBM WebSphere Liberty

• IBM Cloud Pak for Automation

• IBM Event Streams

Also, the License allows the use of the following Functions:

• Case Manager Crawler of Analytical Components

o Business Automation Insight (of IBM Cloud Pak for Automation)

Unzip the workflow.2103.delta.repository.zip repository:

Then select the unpacked Fix Pack repository.config file.

Install Fix Pack workflow.21031.delta.repository.zip

[root@ECMUKDEMO8 PFS21]# mkdir PFS_21031

[root@ECMUKDEMO8 PFS_21031]# rm workflow.21031.delta.repository.zip

rm: remove regular file 'workflow.21031.delta.repository.zip'? y

Remove the unzipped file and load installation manager

Figure 7.31: The Supporting Programs and Deployment software lists.

Figure 7.32: The downloading software size and status is shown

7.1.3.1 IMPORTANT post Installation upgrade

7.1.4 Adding an Unmanaged Node

7.1.5 Installing a stand-alone installation in IBM BPM

7.1.6 Creating the PFS Process Federation Server on