Manualshelf

Server workflows for HP Matrix Operating Environment

ManualsBrandsHP ManualsSoftwareHP Matrix Operating Environment w/Insight Control 24x7 Supp 1 Server Lic
11121314151617181920
12
4. In the Import window, expand the items using “+” button task bar.
5. Select the ESA folder from the items list, and make sure that “Upper Arrow” symbol is selected under “Action”
column. The “Description” column will display “Modify in repository” against all the selected items.
Note: If the Insight Dynamics/Matrix OE 6.3 release or later is being upgraded, then only the changed items will be
selected for upgrade. The “Description” column will display “Modify in repository” for only those items.
1. Click on the “Apply” button, the last icon on the task bar. This will start importing ESA server workflows into OO
repository
2. Click OK to close the import window.
3. On the left side of OO Studio, select the folder “ESA” located under Library\Hewlett-Packard. Right click and
select Repository -> Check-In Tree operation to check-in the new imported workflows.
This will complete the upgrade process of the server workflows on a remote standalone OO server.
Note: Normally, the upgrade of server workflows retain the previous OO configuration. However, if the upgraded
version of Insight Dynamics is 6.2 U1, then on OO studio, the Hpio_Install_Path system property needs to be
configured to C:\Program Files\HP\Matrix infrastructure orchestration.
Refer the section “Configuring OO” for more details.
Security
ESA communicates with Matrix OE and the OO over a secure channel (https).
ESA uses jetty as web server which will listen on both secure port 52001 and non-secure port 52000, to interact with
its clients and OO. The sections below explain the jetty configuration for ESA to interact with OO.
The callbacks from OO to ESA are, by default, over non-secure (http) channel. However, it is possible to configure
ESA and OO to have secure callbacks, as explained in the “Securing OO Callback” section below.
Jetty Settings when OO is running on the CMS
The default value for jetty.host property under “addConnector” configuration in jetty.xml file should be set to
“localhost”, as below.
<Set name="host"><SystemProperty name="jetty.host" default=”localhost”/></Set>
This will restrict ESA to listen to clients that are running within the CMS only.
Jetty Settings when OO is running on a remote standalone OO server
When OO is running on a remote standalone OO server, the jetty settings will be as follows:
<Set name="host"><SystemProperty name="jetty.host"/></Set>