Add an integration instance in Service Manager

To set up the downtime exchange integration, you must add an instance of this integration in the Service Manager Integration Suite (SMIS).

To add the SMBSM_DOWNTIME instance, follow these steps:

1. Click Tailoring > Integration Manager. Integration Instance Manager opens.
2. Click Add. The Integration Template Selection wizard opens.
3. Select SMBSM_DOWNTIME from the Integration Template list. Ignore the Import Mapping check box, which has no effect on this integration.
4. Click Next. The Integration Instance Information page opens.

5. Do the following:

   • Modify the Name and Version fields to the exact values you need.
   • In the Interval Time(s) field, enter a value based on your business needs in regard to downtime exchange frequency. Note that a short interval time can be safe because the next scheduled task will not start until the previous task is completed and the interval time passed.
   • In the Max Retry Times field, enter a value. This is the maximum allowed number of retries (for example, 10) for each failed task.
   • In the Log File Directory field, specify a directory where log files of the integration will be stored. This must be a directory that already exists on the Service Manager server. By default, logging message is output to sm.log.
   • (Optional) In the SM Server field, specify a display name for the Service Manager server host. For example: my_local_SM.
   • (Optional) In the Endpoint Server field, specify a display name for the BSM server host. For example: my_BSM_1.
   • (Optional) In the Log Level field, change the log level from INFO (default) to another level. For example: WARNING.
   • (Optional) If you want this integration instance to be automatically enabled when the Service Manager Server service is started, select Run at system startup.
6. Click Next. The Integration Instance Parameters page opens.

7. On the General Parameters tab, complete the following fields as necessary:

   Name	Category	Value	Description
   WithdrawDowntime	General	true/false	Set this value to true: When authorized users are manually changing the phase of a change record which has 'valid' outage, a window will open and provide choices of withdrawing the outage. Set this value to false: The pop-up window is disabled. This operation may cause some unapproved planned downtimes be synchronized to BSM. By default, this value is set to true.
   Category or workflow (Process Designer) name of changes	Change	The final approval phase for changes	Set the final approval phase for downtime, which is the indication of valid downtime information.
   Category or workflow (Process Designer) name of tasks	Task	The final approval phase for tasks	Set the final approval phase for downtime, which is the indication of valid downtime information.
   sm.host	General	<sm server name >	Set the Service Manager server host name or DNS name to compose the External Process Reference and the Reference Number of Scheduled Downtime CI in UCMDB. Note: Do not include a colon in this field. Otherwise, the logic will be broken.
   sm.reference.prefix	General	urn:x-hp:2009:sm	Set the prefix to compose the External Process Reference of Scheduled Downtime CI in UCMDB. Note: This field has a fixed value. Do not change it.

   Notes:

   1. Type category or workflow name of change/task in the Name column. This value is case-sensitive and it must match the record in Service Manager database.
   2. Set the value to Change for changes in the Category column. Similarly, set the value to Task for tasks.
   3. Type the final approval phase in the Value column. This value is case-sensitive and it must match the record in Service Manager database.You can separate multiple phases by semicolons, which must be the English character.
   4. Detailed information will be displayed in the integration log when the following errors occur:
      • User input of categories/phases for the changes/tasks is not correct.
      • The category and phase pair does not exist in the database.
   5. For Change Management categories which do not have approval phase, the downtime integration will treat its downtime information as final approved once created. You do not need to define any phases in SMIS parameters.

   6. For the category or workflow name of the changes and the tasks, the integration will ignore all the final phases defined for the redundant category or workflow.

8. Click Next twice and then click Finish. Leave the Integration Instance Mapping and Integration Instance Fields settings blank. This integration does not use these settings.

   Service Manager creates the instance. You can edit, enable, disable, or delete it in Integration Manager.

9. Enable the integration instance. SMIS will validate all the final phases you filled in the Integration Instance Parameters page and print warning messages if there are errors.

Related topics

Downtime Exchange between OMi and Service Manager

Tailor Service Manager to handle phase change
Verify the OMi-SM downtime synchronization setup