Add an Operations Orchestration integration

Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Applies to User Roles:

System Administrator

To use the Service Manager to OO integration, you must add and enable an instance of this integration in Integration Manager. Optionally, you can enable Lightweight Single Sign-On (LW-SSO) in OO and in Service Manager to bypass the log-in prompts.

To add and enable a Service Manager to OO integration instance:

Log on to the Service Manager Windows or Web client.

Click Tailoring > Integration Manager. Integration Instance Manager opens.

Click Add. The Integration Template Selection wizard opens.

Select SMOO from the Integration Template list. Ignore the Import Mapping check box, which has no effect on this integration.

Click Next. The Integration Instance Information page opens.

Complete the following fields as necessary.

Field	Value	Description
Name (required)	User-defined. Default: `SMOO`.	Name of the integration instance.
Version (required)	1.1	Version number of the integration.
Interval Time (s) (required)	User-defined. For example: `600`.	Polling interval (in seconds) for Operations Orchestration flow synchronization.
Max Retry Times (required)	Enter 0 (zero) for this field.	Maximum allowed number of retries if the background scheduler fails to run. SMOO does not use this value.
SM Server	Enter a name that identifies your Service Manager server host. For example, `sm_host1`.	Display name for your Service Manager server host.
Endpoint Server	Enter a name that identifies your Operations Orchestration server host. For example, `oo_host1`.	Display name for your Operations Orchestration server host.
Log Level (required)	Select a level from the drop-down list. Default: `INFO`.	Level of diagnostic information that the Service Manager server logs to the log file directory. The possible log levels are: DEBUG, INFO (default), WARNING, ERROR, and OFF.
Log File Directory (required)	Specify a directory. For example: `c: \smoologs`.	This is a directory that exists on the Service Manager server host where log files of the Service Manager to OO integration are stored. The log files are generated in the following format: `SMOO-<yyyy><mm><dd>.log` (for example, `SMOO-20100328.log`) Note: If you specify a directory that does not exist, the log files will get lost; if you do not specify a directory, the Service Manager to OO integration will not work.
Run at system startup	Selected/not selected	Automatically enable/disable the integration instance when the Service Manager server is started.
Description	Micro Focus Operations Orchestration flows linked to Service Manager.	Description of the integration instance.

Click Next. The Integration Instance Parameters page opens.

Click the General Parameters and Secure Parameters tabs, and modify the parameter values as shown in the table below:

Parameter	Value	Example
oo.server.url	Server address of Operations Orchestration Central: `https://[servername]:[port]`. Note that [servername] should be the fully qualified domain name (FQDN) of the Operations Orchestration server host. Note SSL is recommended for communication between the servers.	`https://oo.microfocus.com:8443` Note If you are using OO 10.x, mark the Enable Authentication check box to ensure the integration API can pass the authentication.
oo.user.name	User name of the Operations Orchestration user account that the Service Manager server uses to access Operations Orchestration Central to synchronize and launch OO flows. Note If domain user accounts are used for OO login, you need to specify a domain user account by using the DOMAIN\username format (for example, Internal\admin); otherwise Service Manager will fail to connect to the OO server. Note For security reason, we recommend that you only grant the necessary rights to the user account that is used in the integration.	`admin` or `Internal\admin`
oo.password	Password of oo.user.name.	`admin`
basepath.delimiter	Delimiter between multiple basepaths. The default delimiter is a semicolon (;).	;
basepath	basepath1;bathpath2;... The paths are separated by the basepath delimiter. Only the OO flows under the basepath and its sub-folders will be synchronized from OO.	/Library/ITIL/Change Management;/Library/ ITIL/Incident Management
Accept-Language	REST Request Language Setting	en
http.conn.timeout	Http Connection Timeout setting (seconds)	30
http.rec.timeout	Http Receive Timeout setting (seconds)	30
OOKM	Set to true/false to enable/disable the visibility of this integration instance in Knowledge Management (default: true).	`true` or `false`
OOCM	Set to true/false to enable/disable the visibility of the OO integration instance in Change Management (default: true).	`true` or `false`

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.

Enable the integration instance.

Optionally: