7.1 IBM Workflow Center 8.6
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.Repository/Repository.jsp?v=8.6.1.19002
7.1.1 Restarting and upgrading the system
The original RHEL Linux 8.0 system build for Business Automation Workflow Center 8.6 is 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.
- 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 username and password (wasadm/filenet on this system).
- Stop the IBM FileNet Content Engine Application Server using the following commands:
[root@ECMUKDEMO8 bin]# cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
[root@ECMUKDEMO8 bin]# ./stopServer.sh server1
A pop-up window prompts for the WebSphere username and password (wasadm/filenet on this system).
- Stop the deployment environment as shown in Figure 7.1:
https://ecmukdemo8:9043/ibm/console/login.do?action=secure
Figure 7.1: The deployment environment is stopped
- Stop the node agent:
[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 - 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 - 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
DB2
0000I 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 - 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 - The following command was used to remove the old Linux kernel from the /boot system, as shown in Figure 7.2:
yum remove kernel-4.18.0-305.12.1.el8_4.x86_64
Figure 7.2: The original old Linux kernel is removed
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 7.3.
Figure 7.3: The dnf update command now completes successfully
- Reboot the system at this point, as shown in Figure 7.4:
d enough space. The dnf update command was then run successfully, as shown in Figure 7.3.
