IBM Support

IBM Cloud Orchestrator Interim Fix 1 for 2.4.0.2

Download


Abstract

IBM Cloud Orchestrator and IBM Cloud Orchestrator Enterprise Edition 2.4.0.2_iFix001 has been made generally available and contains fixes to version 2.4.0.2.

Download Description

Table of Contents
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.
Supporting Documentation
Document Description

Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions.

IBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.

Click to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family.

Prerequisites

Prerequisites include:

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.

Review the Prerequisites tab in the system requirements report for supported versions of Data Protection and Recovery, Databases and Process Management tools.

Back to top

Installation Instructions

This iFix can only be installed as an upgrade of an existing IBM Cloud Orchestrator 2.4 Fix Pack 2 installation.

You can upgrade IBM Cloud Orchestrator or IBM Cloud Orchestrator Enterprise Edition.

Perform the following steps:

Table of Contents:

  1. Stop IBM Cloud Orchestrator
  2. Back up IBM Cloud Orchestrator
  3. Copy and extract IBM Cloud Orchestrator 2.4.0.2_iFix001
  4. Update Java 64-bit installation
  5. Update IBM WebSphere Application Server installation
  6. Update IBM HTTP Server installation
  7. Upgrade PDcollect tool
  8. Upgrade OpenStack components
  9. Update IBM Cloud Orchestrator core toolkits
  10. Update OrchestratorEAR.ear
  11. Add custom property to IBM Business Process Manager
  12. Update Self-service user interface
  13. Inventory Tagging on Central Server 2
  14. Restart IBM Cloud Orchestrator


1 Stop IBM Cloud Orchestrator
-------------------------------

1) Stop IBM Cloud Orchestrator on Central Server 1

Change to directory: /opt/ibm/orchestrator/scorchestrator/

Stop SmartCloud Orchestrator: ./SCOrchestrator.py --stop
===>>> Stopping Smart Cloud Orchestrator
...
===>>> Stopping Smart Cloud Orchestrator complete

Wait until all components have stopped.

You can check if all components have been stopped using ./SCOrchestrator.py --status


Back to top


2 Back up IBM Cloud Orchestrator
----------------------------------

1) Back up your IBM Cloud Orchestrator installation

Back up the Central Server and Region Server virtual machines


Back to top


3 Copy and extract IBM Cloud Orchestrator 2.4.0.2_iFix001
------------------------------------------------------------------

1) Copy and extract 2.4.0.2-CSI-ICO-IF0001.tar on Deployment Server

Extract 2.4.0.2-CSI-ICO-IF0001.tar in a directory of your choice <your_dir> by running the following command:

Note: Do not place the package under /root path

tar -xvf 2.4.0.2-CSI-ICO-IF0001.tar

The following files are extracted:

      |-- IBM_Cloud_Orchestrator-2.4.0.2-IF0001.fxtag
      |-- bpm
      |   |-- 8.5.5-WS-WAS-FP0000006-part1.zip
      |   |-- 8.5.5-WS-WAS-FP0000006-part2.zip
      |   `-- cookbooks
      |       `-- bpm
      |           |-- attributes
      |           |   `-- default.rb
      |           |-- files
      |           |   `-- default
      |           |       `-- fixpack
      |           |           |-- 8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip
      |           |           |-- 8.5.0.1-WS-BPM-IFJR49893.zip
      |           |           |-- 8.5.0.1-WS-BPMPCPD-IFIT05359.zip
      |           |           `-- 8.5.0.1-WS-BPMPCPD-IFJR50589.zip
      |           `-- recipes
      |               |-- bpm_download_fixpack.rb
      |               `-- bpm_install_fixpack.rb      
      |-- ihs
      |   |-- 8.5.5-WS-WASSupplements-FP0000006-part1.zip
      |   |-- 8.5.5-WS-WASSupplements-FP0000006-part2.zip
      |   `-- cookbooks
      |       `-- ihs
      |           |-- recipes
      |           |   `-- ihs.rb
      |           `-- templates
      |               `-- default
      |                   `-- ihssilent.erb
      |-- java
      |   |-- cookbooks
      |   |   `-- java
      |   |       `-- attributes
      |   |           `-- default.rb
      |   `-- ibm-java-sdk-7.0-9.10-linux-x86_64-nolicense.tgz
      |-- openstack
      |   |-- 62017.122.000.rtc-208910-horizon-78b6f5ed61-ifix-el6-tar.gz
      |   |-- manager.py
      |   |-- nova-vmware-driver-2014.1-201509151826.ibm.noarch.rpm
      |   |-- rtc-203984-nova-6481b3166-el6-ifix.tgz
      |   `-- rtc-207025-cinder-b0e5535ed5-el6-ifix.tar.gz
      |-- orchestrationear
      |   |-- com.ibm.orchestrator.core.jar
      |   `-- TaskResource.class
      |-- pdcollect
      |   `-- pdcollect.tar.gz
      |-- scui
      |   |-- com.ibm.orchestrator.ui.framework.jar
      |   `-- com.ibm.orchestrator.ui.jar      
      `-- toolkits
          |-- 00_SCOrchestrator_Toolkit_2402_20150914_ifix1.twx
          |-- 10_SCOrchestrator_Scripting_Utilities_Toolkit_2402_20150914_ifix1.twx
          |-- 20_SCOrchestrator_Support_IaaS_Toolkit_2402_20150914_ifix1.twx
          |-- 30_SCOrchestrator_Support_vSys_Toolkit_2402_20150914_ifix1.twx
          |-- 35_SCOrchestrator_Multi-Tenancy_Toolkit_2402_20150914_ifix1.twx
          |-- 40_SCOrchestrator_Service_Composition_Toolkit_2402_20150914_ifix1.twx
          |-- 45_SCOrchestrator_Email_Notification_Toolkit_2402_20150914_ifix1.twx
          |-- 50_SCOrchestrator_Nova_Support_Toolkit_2402_20150914_ifix1.twx
          |-- 65_SCOrchestrator_Support_vSys_Next_Toolkit_2402_20150914_ifix1.twx
          |-- 70_SCOrchestrator_Heat_Support_Toolkit_2402_20150914_ifix1.twx
          |-- 72_SCOrchestartor_OpenstackBlockStorage_Toolkit_2402_20150914_ifix1.twx
          `-- 76_SCOrchestrator_IAAS_Assets_2402_20150914_ifix1.twx        


Back to top


4 Update Java 64-bit installation
-----------------------------------

Execute the following steps to update IBM Java runtime instances from the Deployment Server:

(1) Execute commands from the keystonerc file in the /root directory:
source keystonerc

(2) List the deployment jobs:
ds job-list

Note: Usually the job list returned contains a job for the Central Servers install/upgrade (prefixed sco-central-servers),
a job for the VMware Region Servers install/upgrade (prefixed vmware_region) and
a job for the KVM Region Servers install/upgrade (prefixed kvm_region).

Remember the associated job IDs displayed in column labeled id.

(3) List the environments:
knife environment-list -c /etc/chef/knife.rb

Note: Use the job ID obtained from the list of deployment jobs to identify the environments for the Central Server upgrade.

(4) Update the environment for the Central Servers install/upgrade job
export EDITOR=vi
knife environment edit OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> -c /etc/chef/knife.rb

Locate the Java download URL in the environment file:
"java": {
"download_url": "http://<ds>:<port>/scp/java/ibm-java-sdk-7.0-8.10-linux-x86_64-nolicense.tgz"
},

Change the Java archive name to ibm-java-sdk-7.0-9.10-linux-x86_64-nolicense.tgz and save your changes
...
Saved OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE>

(5) Copy the IBM Java 7 7.0.9.10 package to the file server location on the Deployment Server:

cp -p java/ibm-java-sdk-7.0-9.10-linux-x86_64-nolicense.tgz /data/repos/scp/java/

(6) Download the Java cookbook in a directory of your choice and rename:

knife cookbook download java -d /tmp/ico2402_ifix1 -c /etc/chef/knife.rb
...
Cookbook downloaded to /tmp/ico2402_ifix1/java-0.0.1

mv /tmp/ico2402_ifix1/java-0.0.1/ /tmp/ico2402_ifix1/java/

(7) Copy the Java cookbook attributes file to the downloaded cookbook directory and confirm overwrite:

cp -p java/cookbooks/java/attributes/default.rb /tmp/ico2402_ifix1/java/attributes/

(8) Upload the modified Java cookbook:

knife cookbook upload java -o /tmp/ico2402_ifix1/ -c /etc/chef/knife.rb
...
Uploading java [0.0.1]
Uploaded 1 cookbook.

(9) Execute the Java cookbook as bootstrap operation for Central Server 2:

knife bootstrap <CENTRAL_SERVER_2_FQDN_OR_IP> \
--node-name <UNIQUE_NAME> \
--template-file /etc/heat/erb/topology.erb \
--ssh-user root \
--identity-file /root/.ssh/smartcloud \
--run-list "recipe[java::jdk]" \
--environment OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> \
--no-host-key-verify

Note: Specify a unique name by using the --node-name option for each of your bootstrap commands, 2402_IFIX1_CS2_JAVA

...

Connecting to <CENTRAL_SERVER_2_FQDN_OR_IP>
...
Starting Chef Client, version 11.12.8
Creating a new client identity for <UNIQUE_NAME> using the validator key.
resolving cookbooks for run list: ["java::jdk"]
...
Recipe: java::jdk
* directory[/opt/ibm] action create (up to date)
* script[download and unzip the package from http://.../ibm-java-sdk-7.0-9.10-linux-x86_64-nolicense.tgz] action run
- execute "bash" "/tmp/chef-script20150903-14171-gaehhf"

* directory[Delete installed jdk files] action delete
- delete existing directory /opt/ibm/java-x86_64-70

* execute[move files to install path] action run
- execute mv /tmp/java/* /opt/ibm/java-x86_64-70

* file[Delete downloaded jdk package file] action delete
- delete file /opt/ibm/java-x86_64-70.tgz

* directory[Delete extracted jdk files] action delete
- delete existing directory /tmp/java

* template[jdk.sh] action create (up to date)

Running handlers:
Running handlers complete

Chef Client finished, ...

(10) Check that IBM Java was upgraded to SR9 FP10 on Central Server 2:

Run the java -fullversion command to display the installed version.

/opt/ibm/java-x86_64-70/bin/java -fullversion

java full version JRE 1.7.0 IBM Linux build pxa6470sr9fp10-20150708_01(SR9 FP10)

(11) Repeat steps (9) and (10) for Central Server 3 where IBM Workload Deployer is running.

(12) Copy new security (unrestricted) policy files on Central Server 3 where IBM Workload Deployer is running.

cp -p /opt/ibm/java-x86_64-70/demo/jce/policy-files/unrestricted/*.jar /opt/ibm/java-x86_64-70/jre/lib/security/


Back to top


5 Update IBM WebSphere Application Server installation
--------------------------------------------------------

Execute the following steps to update IBM WebSphere Application Server runtime instances from the Deployment Server:


(1) Update the environment for the Central Servers install/upgrade job
export EDITOR=vi
knife environment edit OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> -c /etc/chef/knife.rb

Locate the WAS download URL in the environment file:
"bpm": {
"bpm_binaries": {
...
"was_fixpack": {
"download_url": {
"part_1": "http://<ds>:<port>/scp/bpm-part_1/8.5.5-WS-WAS-FP0000004-part1.zip",
"part_2": "http://<ds>:<port>/scp/bpm-part_2/8.5.5-WS-WAS-FP0000004-part2.zip"
}
}
}
}

Change the IBM WebSphere Application Server fixpack name to 8.5.5-WS-WAS-FP0000006-part1.zip and 8.5.5-WS-WAS-FP0000006-part2.zip, respectively, and save your changes
...
Saved OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE>

(2) Copy the IBM WebSphere Application Server 8.5.5.6 packages to the file server location on the Deployment Server:

cp -p 8.5.5-WS-WAS-FP0000006-part1.zip /data/repos/scp/bpm-part_1/
cp -p 8.5.5-WS-WAS-FP0000006-part2.zip /data/repos/scp/bpm-part_2/

(3) Download the BPM cookbook in a directory of your choice and rename:

knife cookbook download bpm -d /tmp/ico2402_ifix1 -c /etc/chef/knife.rb
...
Cookbook downloaded to /tmp/ico2402_ifix1/bpm-0.1.5

mv /tmp/ico2402_ifix1/bpm-0.1.5/ /tmp/ico2402_ifix1/bpm/

(4) Copy the BPM cookbook artifacts to the downloaded cookbook directory and confirm overwrite:

cp -p bpm/cookbooks/bpm/attributes/default.rb /tmp/ico2402_ifix1/bpm/attributes/
cp -p bpm/cookbooks/bpm/files/default/fixpack/* /tmp/ico2402_ifix1/bpm/files/default/fixpack/
cp -p bpm/cookbooks/bpm/recipes/bpm_*_fixpack.rb /tmp/ico2402_ifix1/bpm/recipes/

(5) Upload the modified BPM cookbook:

knife cookbook upload bpm -o /tmp/ico2402_ifix1/ -c /etc/chef/knife.rb
...
Uploading bpm [0.1.5]
Uploaded 1 cookbook.

(6) Remove the temporary installation directory on Central Server 2:

rm -rf /opt/ibm/BPM/ico/tmp/was

(7) Execute the BPM cookbook as bootstrap operation for Central Server 2:

knife bootstrap <CENTRAL_SERVER_2_FQDN_OR_IP> \
--node-name <UNIQUE_NAME> \
--template-file /etc/heat/erb/topology.erb \
--ssh-user root \
--identity-file /root/.ssh/smartcloud \
--run-list "recipe[bpm::bpm_download_fixpack],recipe[bpm::bpm_install_fixpack]" \
--environment OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> \
--no-host-key-verify

Note: Specify a unique name by using the --node-name option for your bootstrap commands, 2402_IFIX1_CS2_BPM

...

Connecting to <CENTRAL_SERVER_2_FQDN_OR_IP>
...
Starting Chef Client, version 11.12.8
Creating a new client identity for <UNIQUE_NAME> using the validator key.
resolving cookbooks for run list: ["bpm::bpm_download_fixpack", "bpm::bpm_install_fixpack"]
...
Recipe: bpm::bpm_download_fixpack
* directory[/opt/ibm/BPM/ico/tmp] action create (skipped due to not_if)
* directory[/opt/ibm/BPM/ico/tmp/was] action create
- create new directory /opt/ibm/BPM/ico/tmp/was
- change mode from '' to '0755'
- change owner from '' to 'root'

* remote_file[/opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part2.zip] action create_if_missing
- create new file /opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part2.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part2.zip from none to 7ff536
- suppressed sensitive resource

* remote_file[/opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part1.zip] action create_if_missing
- create new file /opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part1.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.5-WS-WAS-FP0000006-part1.zip from none to 6cfc51
- suppressed sensitive resource

* execute[extract 8.5.5-WS-WAS-FP0000006-part2.zip] action run
- execute extract 8.5.5-WS-WAS-FP0000006-part2.zip

* execute[extract 8.5.5-WS-WAS-FP0000006-part1.zip] action run
- execute extract 8.5.5-WS-WAS-FP0000006-part1.zip

* cookbook_file[/opt/ibm/BPM/ico/tmp/8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip] action create
- create new file /opt/ibm/BPM/ico/tmp/8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip from none to 103542
- suppressed sensitive resource

* directory[/opt/ibm/BPM/ico/tmp/ifixes/8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip] action create
- create new directory /opt/ibm/BPM/ico/tmp/ifixes/8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip
- change mode from '' to '0755'
- change owner from '' to 'root'

* execute[extract 8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip] action run
- execute extract 8.5.0.0-WS-WASJavaSDK-LinuxX64-IFPI37006.zip

* cookbook_file[/opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPM-IFJR49893.zip] action create
- create new file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPM-IFJR49893.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPM-IFJR49893.zip from none to e2585a
- suppressed sensitive resource

* directory[/opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPM-IFJR49893.zip] action create
- create new directory /opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPM-IFJR49893.zip
- change mode from '' to '0755'
- change owner from '' to 'root'

* execute[extract 8.5.0.1-WS-BPM-IFJR49893.zip] action run
- execute extract 8.5.0.1-WS-BPM-IFJR49893.zip

* cookbook_file[/opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFJR50589.zip] action create
- create new file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFJR50589.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFJR50589.zip from none to 55f185
- suppressed sensitive resource

* directory[/opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPMPCPD-IFJR50589.zip] action create
- create new directory /opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPMPCPD-IFJR50589.zip
- change mode from '' to '0755'
- change owner from '' to 'root'

* execute[extract 8.5.0.1-WS-BPMPCPD-IFJR50589.zip] action run
- execute extract 8.5.0.1-WS-BPMPCPD-IFJR50589.zip

* cookbook_file[/opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFIT05359.zip] action create
- create new file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFIT05359.zip
- update content in file /opt/ibm/BPM/ico/tmp/8.5.0.1-WS-BPMPCPD-IFIT05359.zip from none to 7213e6
- suppressed sensitive resource

* directory[/opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPMPCPD-IFIT05359.zip] action create
- create new directory /opt/ibm/BPM/ico/tmp/ifixes/8.5.0.1-WS-BPMPCPD-IFIT05359.zip
- change mode from '' to '0755'
- change owner from '' to 'root'

* execute[extract 8.5.0.1-WS-BPMPCPD-IFIT05359.zip] action run
- execute extract 8.5.0.1-WS-BPMPCPD-IFIT05359.zip

Recipe: bpm::bpm_install_fixpack
* ruby_block[stop bpm-server before installing fixpack] action run
- execute the ruby block stop bpm-server before installing fixpack

* ruby_block[stop bpm before installing fixpack] action run
- execute the ruby block stop bpm before installing fixpack

* execute[uninstall java fixpack] action run (skipped due to only_if)
* execute[install BPM fixpacks] action run
- execute install BPM fixpacks

* execute[install WAS fixpack] action run
- execute install WAS fixpack

* execute[clean the OSGi cache] action run
- execute clean the OSGi cache

* execute[upgrade the profile] action run
- execute upgrade the profile

* execute[upgrade the profile] action run
- execute upgrade the profile

Running handlers:
Running handlers complete

Chef Client finished, ...


(8) Check that IBM WebSphere Application Server was upgraded to 8.5.5.6 on Central Server 2:

Run the versionInfo.sh command to display the installed version.

/opt/ibm/BPM/v8.5/bin/versionInfo.sh

...

Product List
--------------------------------------------------------------------------------
ND installed
BPMSTD installed

Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server Network Deployment
Version 8.5.5.6
ID ND
Build Level cf061521.02
Build Date 5/29/15
Package com.ibm.websphere.ND.v85_8.5.5006.20150529_0536
Architecture x86-64 (64 bit)
Installed Features IBM 64-bit WebSphere SDK for Java
WebSphere Application Server Full Profile
EJBDeploy tool for pre-EJB 3.0 modules
Embeddable EJB container
Sample applications
Stand-alone thin clients and resource adapters

Installed Product
--------------------------------------------------------------------------------
Name IBM Business Process Manager Standard
Version 8.5.0.1
ID BPMSTD
Build Level 20131107-140634
Build Date 11/7/13
Package com.ibm.bpm.STD.v85_8.5.1.20131107_1830
Architecture x86-64 (64 bit)
Installed Features Business Process Manager Standard Process Center

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------


Back to top


6 Update IBM HTTP Server installation
---------------------------------------

Execute the following steps to update IBM HTTP runtime instances from the Deployment Server:


(1) Update the environment for the Central Servers install/upgrade job
export EDITOR=vi
knife environment edit OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> -c /etc/chef/knife.rb

Locate the IBM HTTP Server download URL in the environment file:
"ihs": {
"http_port": "8480",
"ihs_fixpack": {
"download_url": {
"part_1": "http://<ds>:<port>/scp/ihs-part_1/8.5.5-WS-WASSupplements-FP0000003-part1.zip",
"part_2": "http://<ds>:<port>/scp/ihs-part_2/8.5.5-WS-WASSupplements-FP0000003-part2.zip"
}
},

Change the IBM HTTP Server fixpack name to 8.5.5-WS-WASSupplements-FP0000006-part1.zip and 8.5.5-WS-WASSupplements-FP0000006-part2.zip, respectively, and save your changes
...
Saved OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE>

(2) Copy the IBM HTTP Server 8.5.5.6 packages to the file server location on the Deployment Server:

cp -p 8.5.5-WS-WASSupplements-FP0000006-part1.zip /data/repos/scp/ihs-part_1/
cp -p 8.5.5-WS-WASSupplements-FP0000006-part2.zip /data/repos/scp/ihs-part_2/

(3) Download the IBM HTTP Server cookbook in a directory of your choice and rename:

knife cookbook download ihs -d /tmp/ico2402_ifix1 -c /etc/chef/knife.rb
...
Cookbook downloaded to /tmp/ico2402_ifix1/ihs-0.5.1

mv /tmp/ico2402_ifix1/ihs-0.5.1/ /tmp/ico2402_ifix1/ihs/

(4) Copy the IBM HTTP Server cookbook recipe and template files to the downloaded cookbook directory and confirm overwrite:

cp -p ihs/cookbooks/ihs/recipes/ihs.rb /tmp/ico2402_ifix1/ihs/recipes/
cp -p ihs/cookbooks/ihs/templates/default/ihssilent.erb /tmp/ico2402_ifix1/ihs/templates/default/

(5) Upload the modified Java cookbook:

knife cookbook upload ihs -o /tmp/ico2402_ifix1/ -c /etc/chef/knife.rb
...
Uploading ihs [0.5.1]
Uploaded 1 cookbook.

(6) Execute the IHS cookbook as bootstrap operation for Central Server 2:

knife bootstrap <CENTRAL_SERVER_2_FQDN_OR_IP> \
--node-name <UNIQUE_NAME> \
--template-file /etc/heat/erb/topology.erb \
--ssh-user root \
--identity-file /root/.ssh/smartcloud \
--run-list "recipe[ihs::ihs]" \
--environment OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> \
--no-host-key-verify \
-c /etc/chef/knife.rb

Note: Specify a unique name by using the --node-name option for your bootstrap commands, 2402_IFIX1_CS2_IHS

...

Connecting to <CENTRAL_SERVER_2_FQDN_OR_IP>
...
Starting Chef Client, version 11.12.8
Creating a new client identity for <UNIQUE_NAME> using the validator key.
resolving cookbooks for run list: ["ihs::ihs"]
...
Recipe: ihs::ihs
* directory[/tmp/ihsinstall] action create
- create new directory /tmp/ihsinstall
- change mode from '' to '0755'
- change owner from '' to 'root'

* directory[/tmp/ihsinstall/fixpacks] action create
- create new directory /tmp/ihsinstall/fixpacks
- change mode from '' to '0755'
- change owner from '' to 'root'

* remote_file[/tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part1.zip] action create_if_missing
- create new file /tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part1.zip
- update content in file /tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part1.zip from none to 014543
- suppressed sensitive resource

* execute[unpack #{local_file}] action run
- execute unpack #{local_file}

* execute[clean up] action run
- execute clean up

* remote_file[/tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part2.zip] action create_if_missing
- create new file /tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part2.zip
- update content in file /tmp/ihsinstall/fixpacks/8.5.5-WS-WASSupplements-FP0000006-part2.zip from none to 2fec49
- suppressed sensitive resource

* execute[unpack #{local_file}] action run
- execute unpack #{local_file}

* execute[clean up] action run
- execute clean up

* template[/tmp/ihsinstall/ihsSilent.xml] action create
- create new file /tmp/ihsinstall/ihsSilent.xml
- update content in file /tmp/ihsinstall/ihsSilent.xml from none to 83e8cd
- suppressed sensitive resource
- change mode from '' to '0440'
- change owner from '' to 'root'
- change group from '' to 'root'

* execute[install IBM HTTP Server] action run
- execute install IBM HTTP Server

* execute[clean up install files] action run
- execute clean up install files


Running handlers:
Running handlers complete

Chef Client finished, ...



(7) Check that IBM HTTP Server was upgraded to 8.5.5.6 on Central Server 2:

Run the versionInfo.sh command to display the installed version.

/opt/IBM/HTTPServer/bin/versionInfo.sh

...

Product List
--------------------------------------------------------------------------------
IHS installed

Installed Product
--------------------------------------------------------------------------------
Name IBM HTTP Server for WebSphere Application Server
Version 8.5.5.6
ID IHS
Build Level cf061521.02
Build Date 5/29/15
Package com.ibm.websphere.IHS.v85_8.5.5006.20150529_0536
Architecture x86-64 (64 bit)
Installed Features IBM HTTP Server 64-bit with Java, Version 6
Core runtime

--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------


Back to top


7 Upgrade PDcollect tool
--------------------------

Execute the following steps to upgrade PDcollect tool:

(1) Extract pdcollect.tar.gz

cd pdcollect ; tar -xvzf pdcollect.tar.gz

(2) Follow the installation instructions in pdcollect/pdcollect/README to upgrade PDcollect tool.

Note: Refer to the PDcollect tool help (./pdcollect.py -help) for information how to use the new capabilities.


Back to top


8 Upgrade OpenStack components
--------------------------------

(1) Make a backup of nova.conf and vmware-discovery.conf on your VMware Region Server and KVM Compute Nodes:

cp -p /etc/nova/nova.conf /etc/nova/nova.conf_2402_ifix1_bak
cp -p /etc/vmware-discovery.conf /etc/vmware-discovery.conf_2402_ifix1_bak (only on VMware Region Server)


Execute the steps (2) to (6) for each VMware Region Server if you have not already applied
LA fix 2.4.0.2-CSI-ICO-LA00004 to your IBM Cloud Orchestrator environment.


(2) Verify if fix is already installed on your VMware Region Server

- Check if RPMs are already installed using:

rpm -qa |grep 201507202031

(3) Copy fix package rtc-207025-cinder-b0e5535ed5-el6-ifix.tar.gz to a folder on your VMware Region Server

scp -p openstack/rtc-207025-cinder-b0e5535ed5-el6-ifix.tar.gz root@<vmwrs>:/tmp

(4) Extract rtc-207025-cinder-b0e5535ed5-el6-ifix.tar.gz on your VMware Region Server

cd /tmp ; tar -xzf rtc-207025-cinder-b0e5535ed5-el6-ifix.tar.gz

The following RPMs will be extracted from the tgz:

noarch/openstack-cinder-2014.1.4-201507202031.ibm.el6.129.noarch.rpm
noarch/openstack-cinder-doc-2014.1.4-201507202031.ibm.el6.129.noarch.rpm
noarch/python-cinder-2014.1.4-201507202031.ibm.el6.129.noarch.rpm

(5) Apply the fix on your VMware Region Server

- Switch to directory you extracted the driver to

/tmp/noarch

- Install all RPMs by means of "yum install *.rpm" (type "y" when required)

(6) Verify installation on your VMware Region Server

- Check that all RPMs were successfully installed using:

rpm -qa |grep 201507202031


Execute the steps (7) to (15) for each VMware Region Server and KVM Compute Node if you have not
already applied LA fixes 2.4.0.2-CSI-ICO-LA00005 and 2.4.0.2-CSI-ICO-LA00006 to your
IBM Cloud Orchestrator environment.


(7) Verify if fix is already installed on your VMware Region Server and KVM Compute Node

- Check if RPMs are already installed using:

rpm -qa |grep 201506182123
rpm -qa |grep nova-vmware-driver (only on VMware Region Server)

(8) Copy fix package rtc-203984-nova-6481b3166-el6-ifix.tgz to a directory on your VMware Region Server and KVM Compute Node

scp -p openstack/rtc-203984-nova-6481b3166-el6-ifix.tgz root@<server>:/tmp

(8.1) Copy fix package nova-vmware-driver-2014.1-201509151826.ibm.noarch.rpm on your VMware Region Server

scp -p openstack/nova-vmware-driver-2014.1-201509151826.ibm.noarch.rpm root@<vmwrs>:/tmp

(9) Extract rtc-203984-nova-6481b3166-el6-ifix.tgz on your VMware Region Server and KVM Compute Node

tar -xvzf rtc-203984-nova-6481b3166-el6-ifix.tgz

The following RPMs will be extracted from the tgz:

openstack-nova-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-api-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-cells-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-cert-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-common-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-compute-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-conductor-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-console-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-doc-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-network-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-novncproxy-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-objectstore-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
openstack-nova-scheduler-2014.1.4-201506182123.ibm.el6.181.noarch.rpm
python-nova-2014.1.4-201506182123.ibm.el6.181.noarch.rpm

(9.1) Uninstall existing nova vmware driver on your VMware Region Server

- Run following command to get existing driver version

rpm -qa |grep nova-vmware-driver

- Uninstall the current nova vmware driver based on the output above

rpm -e nova-vmware-driver-2014.1-201503311127.ibm.noarch

(10) Apply the fix(rtc-203984-nova-6481b3166-el6-ifix.tgz) on your VMware Region Server and KVM Compute Node

- Switch to directory you extracted the driver to

cd /tmp/noarch

- Install all RPMs by means of "rpm -ivh --force *.rpm"

(10.1) Apply the fix(nova-vmware-driver-2014.1-201509151826.ibm.noarch.rpm) on your VMware Region Server

- Switch to directory you copied the driver to

cd /tmp

- Install driver by running rpm -ivh --force nova-vmware-driver-2014.1-201509151826.ibm.noarch.rpm

(11) Verify installation on your VMware Region Server and KVM Compute Node

- Check that all RPMs were successfully installed using:

rpm -qa |grep 201506182123
...
openstack-nova-common-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-novncproxy-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-conductor-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-cells-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-console-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-scheduler-2014.1.4-201506182123.ibm.el6.181.noarch
python-nova-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-cert-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-network-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-compute-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-doc-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-api-2014.1.4-201506182123.ibm.el6.181.noarch
openstack-nova-objectstore-2014.1.4-201506182123.ibm.el6.181.noarch

rpm -qa |grep nova-vmware-driver (only on VMware Region Server)
...
nova-vmware-driver-2014.1-201509151826.ibm.noarch


(12) Restore backup of nova.conf and vmware-discovery.conf on your VMware Region Server and KVM Compute Nodes:

cp -p /etc/nova/nova.conf_2402_ifix1_bak /etc/nova/nova.conf
cp -p /etc/vmware-discovery.conf_2402_ifix1_bak /etc/vmware-discovery.conf (only on VMware Region Server)

(13) Add parameters to nova.conf on your VMware Region Server

The OpenStack VMware driver code will add the ability to filter
the available datastores to be used for a deploy, based on amount of space available.

When the filter is enabled, the default is to use datastores that are less than 80% utilized.
The utilization value may be configured.

With the code change installed, to enable the function:
add the following two lines in the [vmware] section of nova.conf:

enable_disk_utilization_filter=true
disk_utilization_ratio=0.7

(14) Modify nova configuration file on your VMware Region Server and KVM Compute Node

Identify the nova-compute services configured in the environment:
- chkconfig --list|grep nova-compute

Make sure all nova-compute services are running in the environment:
- service openstack-nova-compute status
service openstack-nova-compute start (if required)

If there are multiple nova-compute services running in the environment, need to modify all of them.
- Open all nova conf files and add one line destroy_after_evacuate=False at the end of all of them.

e.g.:
[root@vpcmgmtsconr01 ~]# ps -ef|grep compute | grep -v grep
nova 1178 1 27 Aug02 ? 21:26:30 /usr/bin/python /usr/bin/nova-compute --config-file /etc/nova/nova-service-drdatastore.conf --logfile /var/log/nova/compute-drdatastore.log
nova 26541 1 32 Aug04 ? 06:34:27 /usr/bin/python /usr/bin/nova-compute --config-file /etc/nova/nova.conf --logfile /var/log/nova/compute.log

Make sure to add a new line destroy_after_evacuate=False into nova-service-drdatastore.conf and nova.conf.
e.g.:
---
[workarounds]
destroy_after_evacuate=False

(15) Replace manager.py on your VMware Region Server

Note: Perform this step only for your VMware Region Server.

- Back up /usr/lib/python2.6/site-packages/nova/compute/manager.py (if present)

- Copy new manager.py and put it at the place of the old one.

scp -p openstack/manager.py root@<node>:/usr/lib/python2.6/site-packages/nova/compute/


Execute the steps (16) to (25) to update OpenStack Horizon on Central Server 2 if you have not
already applied LA fix 2.4.0.1-CSI-ICO-LA00010 to your IBM Cloud Orchestrator environment.


(16) Start DB2 and OpenStack

Change to directory: /opt/ibm/orchestrator/scorchestrator/
Start SmartCloud Orchestrator: ./SCOrchestrator.py --start -p db2,qpidd,openstack
===>>> Starting Smart Cloud Orchestrator
...
===>>> Starting Smart Cloud Orchestrator complete

Wait until all components have started

(17) Make sure the correct base URL is configured in ico.repo on Central Server 2:

vi /etc/yum.repos.d/ico.repo

Verify if baseurl is in the following form, correct if not (port is missing).

baseurl=http://<ds-fqdn>:3080/scp/

(18) Extract the contents of 62017.122.000.rtc-208910-horizon-78b6f5ed61-ifix-el6-tar.gz to the directory

tar -xvzf openstack/62017.122.000.rtc-208910-horizon-78b6f5ed61-ifix-el6-tar.gz -C /tmp

There will be a new directory created called noarch.

(19) Copy new RPMs for Horizon from noarch directory to ICO DS repo

cp -p /tmp/noarch/*.rpm /data/repos/scp/openstack-noarch/

(20) Refresh yum repos

createrepo /data/repos/scp/openstack-noarch/

(21) Verify new rpms are available from yum

yum list |grep dashboard
openstack-dashboard.noarch 2014.1.4-72.ibm.el6.1 openstack-noarch
openstack-dashboard-theme.noarch 2014.1.4-72.ibm.el6.1 openstack-noarch
yum list |grep horizon
python-django-horizon.noarch 2014.1.4-72.ibm.el6.1 openstack-noarch
python-django-horizon-doc.noarch 2014.1.4-72.ibm.el6.1 openstack-noarch

Note: If not available perform a "yum clean all"

(22) Back up existing Horizon installation conf file on Central Server 2, back up the existing local_settings conf file

cd /etc/openstack-dashboard/
cp -p local_settings local_settings_backup_2.4.0.2_ifix1

(23) Remove existing horizon rpms on Central Server 2

On Central Server 2 run the following command
yum remove python-django-horizon.noarch

Note: This will also remove dependencies reply y to yum

(24) Install Horizon using Chef on Central Server 2

Run the following commands:

yum clean all
chef-client -o "role[os-dashboard-sco]" -c /etc/chef/central_server_2-< >-client.rb

chef-client -o "role[os-dashboard-sco]" -c /etc/chef/central_server_2-euklzj3x3q5d-client.rb

Note: This will use Chef to reinstall Horizon, there will be only one rb file in /etc/chef/ that has the prefix central_server_2

(25) Install IBM Cloud Orchestrator extensions for Horizon on Central Server 2

Run the following command:

chef-client -o "role[sco_horizon]" -c /etc/chef/central_server_2-< >-client.rb

chef-client -o "role[sco_horizon]" -c /etc/chef/central_server_2-euklzj3x3q5d-client.rb


Back to top


9 Update IBM Cloud Orchestrator core toolkits
-----------------------------------------------

Execute the following steps to update BPM core toolkits from the Deployment Server:

(1) Copy the BPM toolkits to the temporary installation directory on the Central Server 2:

- Create the directory (if not present) on Central Server 2:
mkdir -p /opt/ibm/BPM/ico/tmp/toolkits

- Copy the toolkits to the directory created in the previous step:
scp -p toolkits/*.twx root@<cs2>:/opt/ibm/BPM/ico/tmp/toolkits/

Note: Directory /opt/ibm/BPM/ico/tmp is the default BPM download directory used by
IBM Cloud Orchestrator 2.4.


(2) Make sure IBM Business Process Manager is started

- service bpm status

root: bpm-dmgr (31395): ::: bpm-dmgr status monitor detected bpm-dmgr ONLINE.
root: bpm-node (31416): ::: bpm-node status monitor detected bpm-node ONLINE.
root: bpm-server (31437): ::: bpm-server status monitor detected bpm-server ONLINE.

Start the processes if required using service bpm start


(3) Execute the BPM cookbook "bpm_import_toolkits" as bootstrap operation for Central Server 2:

knife bootstrap <CENTRAL_SERVER_2_FQDN_OR_IP> \
--node-name <UNIQUE_NAME> \
--template-file /etc/heat/erb/topology.erb \
--ssh-user root \
--identity-file /root/.ssh/smartcloud \
--run-list "recipe[bpm::bpm_import_toolkits]" \
--environment OC_ENV-<JOB_ID_FOR_CENTRAL_SERVERS_INSTALL_UPGRADE> \
--no-host-key-verify

Note: Specify a unique name by using the --node-name option for your bootstrap commands, 2402_IFIX1_CS2_BPM_IMPORT_TK

...

Connecting to <CENTRAL_SERVER_2_FQDN_OR_IP>
...
Starting Chef Client, version 11.12.8
Creating a new client identity for 2402_IFIX1_CS2_BPM_IMPORT_TK using the validator key.
resolving cookbooks for run list: ["bpm::bpm_import_toolkits"]

...
Recipe: bpm::bpm_import_toolkits
* cookbook_file[/opt/ibm/BPM/ico/tmp/import_toolkits.py] action create
- create new file /opt/ibm/BPM/ico/tmp/import_toolkits.py
- update content in file /opt/ibm/BPM/ico/tmp/import_toolkits.py from none to 988f70
- suppressed sensitive resource

* package[unzip] action upgrade (up to date)
* package[zip] action upgrade (up to date)
* directory[/opt/ibm/BPM/ico/tmp] action create (skipped due to not_if)
* remote_file[/opt/ibm/BPM/ico/tmp/orchestrator.zip] action create
- create new file /opt/ibm/BPM/ico/tmp/orchestrator.zip
- update content in file /opt/ibm/BPM/ico/tmp/orchestrator.zip from none to c5813d
- suppressed sensitive resource

* execute[extract orchestrator.zip] action run
- execute extract orchestrator.zip

* bash[modify the 0*_SCOrchestrator_Toolkit] action run
- execute modify the 0*_SCOrchestrator_Toolkit

* execute[import all toolkits into BPM] action run
- execute import all toolkits into BPM

* directory[/var/ibm/sco/scriptRepo] action create (skipped due to not_if)
* cookbook_file[/var/ibm/sco/scriptRepo/HelloWorld.sh] action create (skipped due to not_if)

Running handlers:
Running handlers complete

Chef Client finished, ...


(4) Check that the BPM core toolkits were updated successfully:

- Open the IBM Process Designer

- Click View the Process Center

- Click Toolkits

- Click SCOrchestrator_Toolkit (SCOTLKT) and make sure you see this version as top level version (right below Current):

2402_20150914_ifix1

- Repeat this step for the following toolkits:

SCOrchestrator_Scripting_Utilities_Toolkit (SCOSUTK)
SCOrchestrator_Support_IaaS_Toolkit (SCOIAAS)
SCOrchestrator_Support_vSys_Toolkit (SCOVSYS)
SCOrchestrator Multi-Tenancy Toolkit (SCOMT)
SCOrchestrator Service Composition Toolkit (SCOSCT)
SCOrchestrator Email Notification Toolkit (SCOEMAI)
SCOrchestrator Nova Support Toolkit (SCONOVA)
SCOrchestrator_Support_vSys_Ne... (SCOVSYN)
SCOrchestrator Heat Support Toolkit (SCOHEAT)
SCOrchestartor_OpenstackBlockStorage_Toolkit (SUPCIND)
SCOrchestrator_IAAS_Assets (ICIAASA)

You can also check the BPM core toolkit versions using the IBM Process Center using
the following URL: https://<cs2-fqdn>:8443/ProcessCenter


Back to top


10 Update OrchestratorEAR.ear
-------------------------------

Execute the following steps to update OrchestratorEAR.ear if you have not already applied
LA fix 2.4.0.2-CSI-ICO-LA00008 to your IBM Cloud Orchestrator environment.


(1) Back up com.ibm.orchestrator.core.jar and TaskResource.class on Central Server 2:

- Back up com.ibm.orchestrator.core.jar:

cp -p /opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/com.ibm.orchestrator.core.jar \
/opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/com.ibm.orchestrator.core.jar_2402_ifix1_bak

- Back up TaskResource.class:

cp -p /opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/com.ibm.orchestrator.core.rest.v2.war/WEB-INF/classes/com/ibm/orchestrator/core/rest/v2/resources/TaskResource.class \
/opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/com.ibm.orchestrator.core.rest.v2.war/WEB-INF/classes/com/ibm/orchestrator/core/rest/v2/resources/TaskResource.class_2402_ifix1_bak


(2) Update com.ibm.orchestrator.core.jar and TaskResource.class on Central Server 2:

- Update com.ibm.orchestrator.core.jar:

scp -p orchestrationear/com.ibm.orchestrator.core.jar \
root@<cs2>:/opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/

- Update TaskResource.class:

scp -p orchestrationear/TaskResource.class \
root@<cs2>:/opt/ibm/BPM/v8.5/profiles/Node1Profile/installedApps/PCCell1/OrchestratorEAR.ear/com.ibm.orchestrator.core.rest.v2.war/WEB-INF/classes/com/ibm/orchestrator/core/rest/v2/resources/


Back to top


11 Add custom property to IBM Business Process Manager
--------------------------------------------------------

Execute the following steps to add a custom property to IBM Business Process Manager
if you have not already applied LA fix 2.4.0.2-CSI-ICO-LA00009 to your
IBM Cloud Orchestrator environment.


(1) Back up 100Custom.xml on Central Server 2:

cp -p /opt/ibm/BPM/v8.5/profiles/DmgrProfile/config/cells/PCCell1/nodes/Node1/servers/SingleClusterMember1/process-center/config/100Custom.xml \
/opt/ibm/BPM/v8.5/profiles/DmgrProfile/config/cells/PCCell1/nodes/Node1/servers/SingleClusterMember1/process-center/config/100Custom.xml_2402_ifix1_bak


(2) Make sure IBM Business Process Manager Deployment Manager is running but IBM Business Process Manager node and server are stopped

- service bpm status

root: bpm-dmgr (31395): ::: bpm-dmgr status monitor detected bpm-dmgr ONLINE.
root: bpm-node (31416): ::: bpm-node status monitor detected bpm-node OFFLINE.
root: bpm-server (31437): ::: bpm-server status monitor detected bpm-server OFFLINE.

Stop/Start the processes if required using service bpm-server stop, service bpm-node stop, and service bpm-dmgr start

(3) Insert the following section in 100Custom.xml:

- Edit /opt/ibm/BPM/v8.5/profiles/DmgrProfile/config/cells/PCCell1/nodes/Node1/servers/SingleClusterMember1/process-center/config/100Custom.xml

- Add the following section at the end of the file (but before the closing </properties> tag)

<common>
<security merge="mergeChildren">
<vmm-options>
<user-full-name-prop>displayName</user-full-name-prop>
</vmm-options>
</security>
</common>

Make sure the </properties> is the last line of the 100Custom.xml file and the <common> tag is outside the comment block.

(4) Synchronize the changes into Node1 Profile on Central Server 2:

/opt/ibm/BPM/v8.5/profiles/Node1Profile/bin/syncNode.sh <cs2-fqdn> 8879

ADMU0116I: Tool information is being logged in file
/opt/ibm/BPM/v8.5/profiles/Node1Profile/logs/syncNode.log
ADMU0128I: Starting tool with the Node1Profile profile
ADMU0401I: Begin syncNode operation for node Node1 with Deployment Manager
<cs2-fqdn>: 8879
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node Node1 has been synchronized with
Deployment Manager <cs2-fqdn>: 8879

(5) Restart IBM Business Process Manager and make sure it is running

- service bpm restart

- service bpm status

root: bpm-dmgr (31395): ::: bpm-dmgr status monitor detected bpm-dmgr ONLINE.
root: bpm-node (31416): ::: bpm-node status monitor detected bpm-node ONLINE.
root: bpm-server (31437): ::: bpm-server status monitor detected bpm-server ONLINE.

(6) Verify that your changes were populated in TeamWorksConfiguration.running.xml on Central Server 2

- View /opt/ibm/BPM/v8.5/profiles/Node1Profile/config/cells/PCCell1/nodes/Node1/servers/SingleClusterMember1/process-center/TeamWorksConfiguration.running.xml

- Verify that it contains the following section:

<vmm-options>
<user-full-name-prop>displayName</user-full-name-prop>
</vmm-options>


Back to top


12 Update Self-service user interface
---------------------------------------

Execute the following steps to update Self-service user interface if you have not already
applied LA fix 2.4.0.2-CSI-ICO-LA00010 to your IBM Cloud Orchestrator environment.


(1) Back up com.ibm.orchestrator.ui.framework.jar and com.ibm.orchestrator.ui.jar on Central Server 2:

- Back up com.ibm.orchestrator.ui.framework.jar:

cp -p /opt/ibm/ccs/scui/lib/com.ibm.orchestrator.ui.framework.jar \
/opt/ibm/ccs/scui/lib/com.ibm.orchestrator.ui.framework.jar_2402_ifix1_bak

- Back up com.ibm.orchestrator.ui.jar:

cp -p /opt/ibm/ccs/scui/lib/com.ibm.orchestrator.ui.jar \
/opt/ibm/ccs/scui/lib/com.ibm.orchestrator.ui.jar_2402_ifix1_bak


(2) Update com.ibm.orchestrator.ui.framework.jar and com.ibm.orchestrator.ui.jar on Central Server 2:

- com.ibm.orchestrator.ui.framework.jar:

scp -p scui/com.ibm.orchestrator.ui.framework.jar \
root@<cs2>:/opt/ibm/ccs/scui/lib/

- Update com.ibm.orchestrator.ui.jar:

scp -p scui/com.ibm.orchestrator.ui.jar \
root@<cs2>:/opt/ibm/ccs/scui/lib/


Back to top


13 Inventory Tagging on Central Server 2
------------------------------------------

To make it easier for support to find out which IBM Cloud Orchestrator
fixes are installed on your system, copy IBM_Cloud_Orchestrator-2.4.0.2-IF0001.fxtag
to /opt/ibm/SmartCloud_Orchestrator/properties/version/ on Central Server 2.

scp -p ./IBM_Cloud_Orchestrator-2.4.0.2-IF0001.fxtag \
<cs2>:/opt/ibm/IBM_Cloud_Orchestrator/properties/version

Back to top


14 Restart IBM Cloud Orchestrator
-----------------------------------

1) Stop IBM Cloud Orchestrator on Central Server 1

Change to directory: /opt/ibm/orchestrator/scorchestrator/
Stop SmartCloud Orchestrator: ./SCOrchestrator.py --stop
===>>> Stopping Smart Cloud Orchestrator
...
===>>> Stopping Smart Cloud Orchestrator complete

Wait until all components have stopped

You can check if all components have been stopped using ./SCOrchestrator.py --status

2) Start IBM Cloud Orchestrator on Central Server 1

Change to directory: /opt/ibm/orchestrator/scorchestrator/
Start SmartCloud Orchestrator: ./SCOrchestrator.py --start
===>>> Starting Smart Cloud Orchestrator
...
===>>> Starting Smart Cloud Orchestrator complete

Wait until all components have started

You can check if all components have been started using ./SCOrchestrator.py --status


Back to top

Download Package

The following sections provide detailed information related to this release.

Click the FC link below to obtain the release from Fix Central.


How critical is this fix?

Impact Assessment
Impact Description

Corrective

This is a maintenance release. It contains fixes for client-reported and internally found defects.

Review Security Bulletin - 1967033 for a list of security vulnerabilities addressed in this release.

Test Results

Close [x]

Definitions

Regression: An error in the Maintenance Delivery Vehicle (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed.
This includes:

  • Coding errors that cause a regression
  • Documentation or packaging problems that cause a regression
  • Errors reported in a new function delivered in a MDV that cause a regression

Incomplete: An error in the MDV has not regressed, but does not work as designed.
This includes:

  • Fixed APARs which did not solve the original problem but did not break anything new
  • APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression

Notes:
  • Regression and incomplete APARs are considered fix-in-error or MDV-in-error
  • Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)
  • Issues in major releases due to new functionality do not apply in this definition

There are no known regressions to report.

Back to top

Problems Solved

Defects resolved

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

Review the following list of known issues and open defects:

Open defects

Review the following list of open defects for IBM Cloud Orchestrator on the IBM Support Portal.

Back to top

Change History

What's new

This iFix provides the following serviceability items:
Serviceability - PDcollect:

  • PDcollect can easily and quickly enable trace logging for a specific component
  • To get the right environment details, a tool is needed that can be simply executed and generates a report with the current software environment (such as the ListUI command)
  • PDcollect provides the capability to switch on/off logging for various components.

Back to top

Click the link in the Download Options column:

On
[{"DNLabel":"ICO 2.4.0.2 fixes","DNDate":"30 Sep 2015","DNLang":"English","DNSize":"1","DNPlat":{"label":"Linux","code":"PF016"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ETivoli&product=ibm/Tivoli/IBM+SmartCloud+Orchestrator&release=2.4.0.2&platform=All&function=all&source=fc","DNURL_FTP":" ","DDURL":null}]

Technical Support


Follow IBM Cloud Tech Support on Twitter



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




Back to top

[{"Product":{"code":"SS4KMC","label":"IBM SmartCloud Orchestrator"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"2.4.0.2","Edition":"Enterprise;Standard","Line of Business":{"code":"LOB45","label":"Automation"}}]

Problems (APARS) fixed
SE62330;SE62453;SE62608;SE62671;ZZ00375;ZZ00394;ZZ00457;ZZ00463;ZZ00468;ZZ00288;ZZ00290;ZZ00291;ZZ00296;ZZ00300;ZZ00303;ZZ00307;ZZ00308;ZZ00309;ZZ00310;ZZ00311;ZZ00319;ZZ00320;ZZ00323;ZZ00324;IT06033;IT06086;IT06144;IT06322;IT06359;IT06488;IT06604;IT06954;IT07223;IT07315;IT07431;IT07489;IT07809;IT07836;IT07961;IT08046;IT08186;SE61056;SE61576;ZZ00259;ZZ00266;ZZ00294;ZZ00300;ZZ00312;ZZ00322;ZZ00340;ZZ00343;ZZ00344;ZZ00345;ZZ00346;ZZ00347;ZZ00348;ZZ00350;ZZ00351;ZZ00352;ZZ00353;ZZ00354;ZZ00358;ZZ00360;ZZ00361;ZZ00362;ZZ00363;ZZ00364;ZZ00367;ZZ00371;ZZ00376;ZZ00377;ZZ00383;ZZ00389;ZZ00392;ZZ00393

Document Information

Modified date:
05 April 2019

UID

swg24040617

Page Feedback