Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Integration Settings

Log in to subscribe to topics and get notified when content changes.

Integration Settings

Most of the configuration for the integration will take place in the Setting module of the application.

Figure 1. CA SOI Settings module
Table 1. CA SOI Setting module
Setting Description
Alert Maturity (in minutes) Some alerts may clear themselves shortly after firing. This integration provides a holding queue for new alerts. After the specified age of the alerts, if they are still active, an incident is created.
CA Integration User Password The password for the user that will be used to authenticate against the CA SOI web service
CA SOI Alarm Resource URI This is required by the SOI web service. It likely will not change between installations.
CA SOI Integration User ID The user name for the user that will be used to authenticate against the CA SOI web service
CA SOI Web Service Endpoint This will be the SOAP endpoint for your CA SOI installation
Enable debug logging Allow a very verbose set of log statements to be created in the system log. Disable if you are not debugging an issue.
Inbound processor URL for inbound subscription notifications

The URL to the inbound notification processor. This is the URL that we will provide to the subscription service in SOI. HTTP Posts from SOI will be delivered to this URL. In most cases this should be your instance URL with the processor URI of "". However, some installations/configurations of SOI may not allow a post to happen to an HTTPS url. If that is the case, you may have to point this to a non-https url and page that then reposts the request to your page.

Sample PHP code that can be used to forward on an SOI POST to a ServiceNow instance:
$https_user = "admin"; $https_password ="admin"; $https_server = "";

$body = file_get_contents('php://input');

$opts = array('http' =>
   'method'  => 'POST',
   'header'  => "Content-Type: text/xml\r\n".
     "Authorization: Basic ".base64_encode("$https_user:$https_password")."\r\n",
   'content' => $body,
   'timeout' => 60

$context = stream_context_create($opts);

$c = curl_init(); curl_setopt($c, CURLOPT_URL, $https_server); curl_setopt($c, CURLOPT_POST, true); curl_setopt($c, 
CURLOPT_HTTPHEADER, array("Content-Type: text/xml", "Authorization: Basic 
".base64_encode("$https_user:$https_password"))); curl_setopt($c, CURLOPT_POSTFIELDS, "$body"); $result = curl_exec 
($c); curl_close ($c);
Max number of HTTP Request retries used by the SOICommunicator If the SOAP request times out due to a service error the integration will immediately retry it. This setting dictates how many times we will retry.
MID Server brokering communication between ServiceNow and CA SOI The name of the MID Server that will process the integration requests.
Return MID Server log snippets The MID Server probe that processes the API communication generates debug statements as well and can be returned in each ECC Queue input entry. This will greatly increase the size of the response in the ECC Queue. Only use this during debugging. If the "Enable debug logging" is not set, then this setting doesn't apply.