Download
Abstract
IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise Edition 2.4.0.3 has been made generally available and contains fixes to version 2.4 including all predecessor fix packs
Download Description
Sections | Description |
---|---|
The Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. |
|
The How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected. |
|
The Prerequisites section provides important information to review prior to the installation of this release. |
|
The Download package section provides the direct link to obtain the download package for installation in your environment. |
|
The Installation instructions section provides the installation instructions necessary to apply this release into your environment. |
|
The Known side effects section contains a link to the known problems (open defects) identified at the time of this release. |
Review the Prerequisites tab in the system requirements report for supported versions of Data Protection and Recovery, Databases and Process Management tools. |
Review the Software prerequisites page in the IBM Knowledge Center to ensure your environment meets the minimum hypervisor and operating system requirements, especially if you are upgrading from a previous release of IBM Cloud Orchestrator. |
Installation Instructions
This fix pack can be installed as a fresh installation or as an upgrade of an existing installation. Follow the instructions in the tabs below.
Tab navigation
- Fresh Installation- selected tab,
- Upgrade
- Post Installation/Upgrade
Fresh installation of IBM Cloud Orchestrator
Step 1: Review the installation page in the IBM Knowledge Center.
Exceptions:
Note the following instructions about the Downloading the required image files topic in the IBM Knowledge Center:
- In step 4, do not download the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Note the following instructions about the Installing the Deployment Service topic in the IBM Knowledge Center:
- In step 5, do not copy the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Step 2: Review the information on the Post Install/Upgrade tab above.
Fresh installation of IBM Cloud Orchestrator Enterprise Edition
Step 1: Review the installation page in the IBM Knowledge Center.
Exceptions:
Note the following instructions about the Downloading the required image files topic in the IBM Knowledge Center:
- In step 4, do not download the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Note the following instructions about the Installing the Deployment Service topic in the IBM Knowledge Center:
- In step 5, do not copy the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Step 2: Review the information on the Post Install/Upgrade tab above.
Upgrade of IBM Cloud Orchestrator
The following upgrade scenarios are supported:
- IBM Cloud Orchestrator V2.4 -> IBM Cloud Orchestrator V2.4 Fix Pack 3
- IBM Cloud Orchestrator V2.4 Fix Pack 1 -> IBM Cloud Orchestrator V2.4 Fix Pack 3
- IBM Cloud Orchestrator V2.4 Fix Pack 2 -> IBM Cloud Orchestrator V2.4 Fix Pack 3
- IBM Cloud Orchestrator V2.4 Fix Pack 2 Interim Fix 1 -> IBM Cloud Orchestrator V2.4 Fix Pack 3
Step 1: Disable the fault monitor daemon (db2fmcd) process (to avoid potential problems during the upgrade)
Perform the following steps on each IBM DB2 database server of your IBM Cloud Orchestrator environment (Deployment Server, Central Server 1, etc...).
Note: Review technote 1224009: How to disable the fault monitor daemon (db2fmcd) process for additional details.
- Check whether the DB2 fault monitor daemon is running:
ps aux | grep db2fmcd
- If the DB2 fault monitor daemon is running, make a backup copy of the DB2 fault monitor daemon configuration file and disable the daemon:
/opt/ibm/db2/V10.5/bin/db2fmcu -d
- Restart the server.
- Check whether the DB2 fault monitor daemon is running:
ps aux | grep db2fmcd
Step 2: Review the Upgrading topic in the IBM Knowledge Center.
Exception:
Note the following instructions about the Downloading the required image files topic in the IBM Knowledge Center:
- In Step 3(c), the additional fix package is also required if you are upgrading from IBM Cloud Orchestrator V2.4 Fix Pack 2.
- In step 4, do not download the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Note the following instructions about the Installing the Deployment Service topic in the IBM Knowledge Center:
- In step 5, do not copy the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Step 3: Review the information on the Post Install/Upgrade tab above.
Upgrade of IBM Cloud Orchestrator Enterprise Edition
The following upgrade scenarios are supported:
- IBM Cloud Orchestrator Enterprise Edition V2.4 -> IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 3
- IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 1 -> IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 3
- IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 2 -> IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 3
- IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 2 Interim Fix 1 -> IBM Cloud Orchestrator Enterprise Edition V2.4 Fix Pack 3
Step 1: Disable the fault monitor daemon (db2fmcd) process (to avoid potential problems during the upgrade)
Perform the following steps on each IBM DB2 database server of your IBM Cloud Orchestrator environment (Deployment Server, Central Server 1, etc...).
Note: Review technote 1224009: How to disable the fault monitor daemon (db2fmcd) process for additional details.
- Check whether the DB2 fault monitor daemon is running:
ps aux | grep db2fmcd
- If the DB2 fault monitor daemon is running, make a backup copy of the DB2 fault monitor daemon configuration file and disable the daemon:
/opt/ibm/db2/V10.5/bin/db2fmcu -d
- Restart the server.
- Check whether the DB2 fault monitor daemon is running:
ps aux | grep db2fmcd
Step 2: Review the Upgrading topic in the IBM Knowledge Center.
Exception:
Note the following instructions about the Downloading the required image files topic in the IBM Knowledge Center:
- In Step 3(c), the additional fix package is also required if you are upgrading from IBM Cloud Orchestrator V2.4 Fix Pack 2.
- In step 4, do not download the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Note the following instructions about the Installing the Deployment Service topic in the IBM Knowledge Center:
- In step 5, do not copy the IBM Business Process Manager V8.5 packages. Instead, use the IBM Business Process Manager V8.5.6 packages that are provided in IBM Cloud Orchestrator V2.4 Fix Pack 3.
Step 3: Review the information on the Post Install/Upgrade tab above.
Post installation information
After you install or upgrade the IBM Cloud Orchestrator or IBM Cloud Orchestrator Enterprise Edition software, complete the following tasks.
Step 1: Resolve vulnerabilities
For vulnerability details and information about fixes, review the Impact assessment section below for details.
Post upgrade information
Step 1: Complete the above tasks first.
Step 2: Disable the SSLv3 protocol
Note: This task is necessary only if upgrading to IBM Cloud Orchestrator 2.4.0.3 or IBM Cloud Orchestrator Enterprise Edition 2.4.0.3. In a fresh installation of IBM Cloud Orchestrator 2.4.0.3 or IBM Cloud Orchestrator Enterprise Edition 2.4.0.3, the SSLv3 protocol is disabled by default.
The required Workload Deployer emergency fixes are included in the 2.4.0-CSI-ICO-FP0003-WORKLOAD-DEPLOYER-efixes.tgz file.
To mitigate known security vulnerabilities in already deployed instances, disable the SSLv3 protocol as described in the Disabling SSLv3 protocol in deployed instances topic in the IBM Knowledge Center:
Note the following updates to the "Disabling the SSLv3 protocol in deployed instances" topic:
- The following file names are incorrect:
- Java_Update_AIX.zip should be Java_Update_AIX_for_WorkloadDeployerPatternInstances_ICO_2.4.0.3.zip.
- Java_Update_Linux.zip should be Java_Update_Linux_for_WorkloadDeployerPatternInstances_ICO_2.4.0.3.zip.
- Java_Update_Windows.zip should be Java_Update_Windows_for_WorkloadDeployerPatternInstances_ICO_2.4.0.3.zip.
- The current topic does not mention upgrading from IBM Cloud Orchestrator (or IBM Cloud Orchestrator Enterprise Edition) V2.4 Fix Pack 2.
- If you are upgrading from IBM Cloud Orchestrator (or IBM Cloud Orchestrator Enterprise Edition) V2.4 Fix Pack 1 or earlier, complete the steps in the topic to disable the SSLv3 protocol, which will remediate the POODLE vulnerability and update Java to the latest version.
- If you are upgrading from IBM Cloud Orchestrator (or IBM Cloud Orchestrator Enterprise Edition) V2.4 Fix Pack 2, and you previously completed the steps in this procedure to disable the SSLv3 protocol, you should use the new efix package supplied in IBM Cloud Orchestrator V2.4 Fix Pack 3 to update Java on all deployed instances, to provide additional security fixes.
Step 3: Update the IBM Process Designer
After you upgrade your IBM Cloud Orchestrator installation, you must update the Process Designer to the same level. Review the Configuring IBM Cloud Orchestrator after upgrading from V2.4 topic in the IBM Knowledge Center for details.
Download Package
The following sections provide detailed information related to this release.
Click the HTTP link below to obtain the release from Fix Central. Image directory contents
|
Impact | Description |
---|---|
Corrective |
This is a maintenance release. It contains fixes for client-reported and internally found defects. |
Critical |
This release also contains fixes to multiple security vulnerabilities.
|
There are no known regressions to report. |
Problems Solved
Click the Fix List link in the table of contents above to review a list of the problems solved in this release. |
Known Side Effects
There are no known issues to report. |
Review the Known errors and limitations section of the IBM Knowledge Center for issues related to this release. Additional Issues:To strengthen security and remove weak cipher suites for Apache HTTP Server, complete the following configuration changes:
When you install IBM Cloud Orchestrator V2.4 Fix Pack 3, the IBM HTTP Server for WebSphere Application Server V8.5.5 software is re-installed.If you previously replaced existing certificates to strengthen security in your environment, you must replace the certificates again after the installation of IBM Cloud Orchestrator V2.4 Fix Pack 3.During the installation of IBM Cloud Orchestrator V2.4 Fix Pack 3, backup copies of the following files are created on Central Server 2: IBM HTTP Server for WebSphere Application Server V8.5.5 keystore files:
IBM WebSphere Application Server Network Deployment V8.5.5 keystore and truststore files:
In some situations, when you create a job by using the Deployment Service wizard, the Deployment Service fails to execute the job. If the job passed all the prerequisite checks, the job is created successfully but is not run. In such cases, you can quit the Deployment Service wizard and run the job manually.
Cloning a virtual image is not supported. If you click PATTERNS > Pattern Design > Virtual Images, select an image, and click the clone icon, the action fails.In the Simplified Chinese and Traditional Chinese translations of the catalogTool.sh file, the description of the export parameter is mistranslated (it refers to "import" instead of "export").Before you can use the BPM2VMW toolkit to automate the VMware vCenter, you must complete the following steps:
For Public Cloud Gateway installations only: In a multiple-NIC environment, you must complete additional post configuration steps to ensure that the Public Cloud Gateway can communicate with OpenStack Keystone. Otherwise, the pcg.log file includes the following error:Unable to generate admin token org.apache.http.conn.HttpHostConnectException: Connection to URL refused Solution:
For IBM Cloud Orchestrator Enterprise Edition installations only: The installation of IBM SmartCloud Cost Management might fail with the following error:package ibm-java-x86_64-sdk-7.0-7.0.x86_64 is already installed Solution:
For high-availability installations only: After you download the SA_MP_v4.1_Lnx.tar file, you must rename the file to SA_MP_4.1_Linux.tar or the installation will fail.For high-availability deployments only: During the installation of a high-availability topology, a default
Solution: |
Open defectsReview the following list of open defects for IBM Cloud Orchestrator on the IBM Support Portal. |
Change History
The following new features or functions have been included in this release:
|
For information about the new features and enhancements, review the What is new in this release topic in the IBM Knowledge Center. |
Click the link in the Download Options column:
Technical Support
Review the IBM Cloud Support BLOG article Enhance your IBM Cloud Support Experience for a complete list of the different support offerings along with a brief description on the best way to use each resource to improve your experience using IBM Cloud products and services. Forums | Communities | Documentation | Contacting Support | Helpful Hints |
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
05 April 2019
UID
swg24040281