*userName

User name in 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

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 PPM requests.

We recommend retaining the default value of false because usually, after Service Manager changes are converted to PPM requests, processing takes place entirely in PPM.

false

*ticketIdFieldName ^a

Field in PPM containing the Service Manager ticket ID. This field is presented in the PPM request as the Ticket Id field in the Service Desk Info section.

(None)

*sdSystemFieldName ^a

Field in PPM containing the Service Manager system name. This field is presented in the PPM request as the System Name field in the Service Desk Info section.

(None)

*staticFieldNames

(Applicable and required only for bidirectional integration)

List of 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 PPM changes, specify the following:

REQD-SD_LAST_UPDATE

(None)

    a.    If 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 PPM.