Enabling Control IBM Sterling Center OSA support via SSP CM command-line

Edit online

You can enable Open Server Architecture (OSA) support through the startCM.sh. The following Java System properties will be used to configure OSA support.

Enabling OSA support

To enable Control Center OSA support in Secure Proxy, an admin user must specify this verbiage in the startup script of SSP CM.

-Dssp.osa.enable=true|false

Configuring the Control Center EP Hosts and Ports for OSA support

To configure a series of EPs for communicating with the OSA, you must use the verbiage:

-Dssp.osa.ep.host=xxxxxxx:zzzzz;xxxxxxxx:zzzzz

where xxxxxx is the host and zzzzz is the port. A series of EP host/port must be separated by semicolon. Example, be
```
-Dssp.osa.ep.secure=true:osaKeyCert
```

Configuring the EPs secure connection

To enable secure connection to the EP hosts/ports, you must use the verbiage:

-Dssp.osa.ep.secure=xxxx:yyyy

where xxxx is true or false, and yyyy is the keycert alias to be used when establishing the secure connection with EP. Example,
```
-Dssp.osa.ep.secure=false:osaKeyCert
```
If ssp.osa.ep.secure is set to false or is not specified then, secure connection to EP will be disabled.

Configuring the EP admin User and Password

While sending OSA events to an EP through SSP, following verbiage must be configured in SSP startCM script to provide the user credential to be used to authenticate the IBM Sterling Control Center admin.

Note: Use GUI to configure OSA connection to avoid entering password.

-Dssp.osa.user.admin=xxxx:yyyy

where xxxx is the userId and yyyy is the admin password.

Example:

-D ssp.osa.user.admin=myUserId:myAdminPassword.

There will be no defaults for these two values. It must be specified if user authentication is desired when sending events to a configured EP.

Configuring Control Center EP Service URL

The Service URL routes events and statuses to IBM Sterling Control Center. If not specified, the default Service URL will be /sccwebclient/. To specify and configure different values, the JAVA system property ssp.osa.service.url must be specified. For example,

-Dssp.osa.service.url= /sccwebclient/events

EP Configuration

Table 1. Control Center EP configuration properties
Property Name	Acceptable Value	Description
ssp.osa.enable	True or false `-Dssp.osa.enable=true` Default: false	Use to enable or disable OSA support
ssp.osa.ep.host	Valid IP/Host and port. Example: `-Dssp.osa.ep.host=10.120.136.135:3365`	Each IP/host pair must be separated by colon. Each EP set must be separated by semicolon
ssp.osa.ep.secure	True\| false and keycert Alias Example: `-Dssp.osa.ep.secure=true:osaKeycert` Default: false	keycert alias must be followed by the true/false value
ssp.osa.service.url	Default: /sccwebclient/events	Used to specify Control Center service that will handle status and events

Importing EP trusted certificate into SSP CM default truststore

To establish TLS/SSL connection with an EP, the trusted certificate for that EP must be imported into SSP CM truststore using configureCmSsl.sh or configureCmSsl.bat script. Here is a sample command to import an EP’s trusted certificate into SSP CM default truststore:

<SSP CM Install Dir>\bin>configureCmSsl.bat -u trustedCert=trustedFileName

where “trustedFileName” is the location of the EP’s trusted certificate