Upgrading HP Operations Orchestration included with Matrix OE to HP Operations Orchestration 9.00 (Full Version)

CMS updates and upgrades
In case the CMS has been upgraded (e.g. 6.3 to 6.3U1, 6.3 to 7.0, 7.0 to 7.1, 7.1 to 7.2, 7.2 to 7.2U1…) all the steps
provided in this document must be re-executed to guarantee the updated files are carried on to the OO server.
The full OO version must also be reviewed to match or exceed the embedded OO version deployed in the CMS. This is
especially important after major upgrades (6.3 to 7.0, 6.3 to 7.1, 7.0 to 7.1…). If necessary upgrade OO before performing
the steps described in this document.
The table below shows embedded OO versions deployed by Matrix Operating Environment. Platform version can be
checked in OO Studio’s
Help/About Studio…
menu item. Content version number is found at
%ICONCLUDE_HOME%\RAS\Java\Default\webapp\logs\wrapper.log
(look for JRASRepository.jar last reference in this file,
the version number looks like 9.00.00.xxx where the last 3 build digits can be discarded).
Table 1: Embedded OO versions deployed by Matrix OE
Matrix OO Platform Embedded OO Content
6.3 9.00 build: 201007061653 9.00.00
7.0 9.00 build: 201007061653 9.00.03
7.1 9.02 build: 201111151655 patch: 9.02.0002 9.00.06
7.2 9.06 build: 201211081714 patch: 9.06.0001 9.00.09
Special attention must be taken for libraries with version suffixes like
saxon-9.1.0.7.j.jar
,
ganymed-ssh2-build210.jar
…
Java always uses the first library it finds, so if an updated copy is carried on to OO server it may be ignored if the older
version is not deleted.
When following this document’s instructions after updates and upgrades, all files and folders copies from the CMS to the
OO server must be followed by OO server content review looking for libraries duplications. In this case the older version
must be deleted. Example: After 6.3 U1 to 7.2 upgrade the
%ICONCLUDE_HOME%\RAS\Java\Default\repository\lib\hpio-
oo
folder may contain both
log4j-1.2.16.jar
(or older) and
log4j-1.2.17.jar
files. In this case
log4j-1.2.16.jar
must be
deleted. The same applies to other version numbered libraries like
commons-collections-*.jar
,
commons-configuration-
*.jar
,
commons-jxpath-*.jar
,
commons-lang-*.jar
,
commons-logging-*.jar
,
saxon-*.jar
,
iControl-jdk*.jar
, and others
.
Install/Use full OO on a separate server
If the customer wanting IO integration with full OO does not have full OO installed on a server, see Appendix A for sample
OO installation instructions first.
If the customer wanting IO integration with full OO already has full OO installed on a server, continue reading on the
instructions.
The examples in this document are using the hosts depicted in the table below:
Table 2: Hosts used in the examples
Host Type FQDN IP
CMS cms1.company.com 192.168.100.1
OO server oo1.company.com 192.168.100.2
SMTP server smtp1.company.com 192.168.100.3
Install infrastructure orchestration OO jars on the OO server
Infrastructure orchestration OO flows execute Java code packaged in JAR files in OO’s Remote Action Service (RAS). These
JARs must be installed in full OO’s RAS and the RAS must be configured to reference the JARs.
To identify OO folder on the CMS: