Configuring the Service Manager Adapter Sender Properties
Specify the properties for the sender section of the Service Manager adapter configuration file as described in Configuring the Service Manager Adapter Sender Properties. The sender controls creating RFCs in OpenText PPM with the converted data.
Table 9-3. Service Manager adapter sender properties
|
Property Name (*Required)
|
Description
|
Default Value
|
|
*userName
|
User name in OpenText PPM by whose credentials requests are created.
This user name must include only single-byte characters.
|
(None)
|
|
*password
|
Password of the userName. You must encrypt this password by using the kEncrypt.sh script, which is located in the bin directory of the PPM Server. Encrypted passwords must be created in a CDATA section.
|
(None)
|
|
*requestType
|
OpenText PPM request type that should be created for the converted changes.
For example:
ALM - Request for Change (RFC)
|
(None)
|
|
updateRequest
|
If set to true, enables updates made to Service Manager changes to be automatically sent to existing OpenText PPM requests.
We recommend retaining the default value of false because usually, after Service Manager changes are converted to OpenText PPM requests, processing takes place entirely in OpenText PPM.
|
false
|
|
*ticketIdFieldName a
|
Field in OpenText PPM containing the Service Manager ticket ID. This field is presented in the OpenText PPM request as the Ticket Id field in the Service Desk Info section.
|
(None)
|
|
*sdSystemFieldName a
|
Field in OpenText PPM containing the Service Manager system name. This field is presented in the OpenText PPM request as the System Name field in the Service Desk Info section.
|
(None)
|
|
*staticFieldNames
(Applicable and required only for bidirectional integration)
|
List of OpenText PPM request fields (separated by semicolons) that are not to be updated when changes are made to their mapped Service Manager change fields.
This list is used to prevent inappropriate update of Service Manager tickets for bidirectional integration. For example, to prevent a ticket from being updated when the last update time in OpenText PPM changes, specify the following:
REQD-SD_LAST_UPDATE
|
(None)
|
|
a. If OpenText PPM is integrated with multiple Service Manager servers, the combination of values in the ticketIdFieldName and sdSystemFieldName properties ensures that all the tickets from all the Service Manager servers are uniquely identified in OpenText PPM.
|
The sender is the last section of the adapter configuration file. Make sure the file ends with the following lines:
</adapter>
</settings>
This completes the configuration of the Service Manager adapter configuration file.
Note: If OpenText PPM is operating in a clustered server configuration, share or copy the <PPM_Home>/sdi-persistency directory and the <PPM_Home>/conf/sdi directory among all the servers in the cluster.
If you want to establish bidirectional integration, proceed to Configuring the OpenText PPM Adapter Configuration File. Otherwise, go to Configure the server.conf parameter in OpenText PPM.
