Integration-related updates for SP1

The following topics describe the integration-related updates in version 8.2 SP1.

Transaction identifier support

In versions of BMC Server Automation earlier than 8.2 SP1, requests to BMC Server Automation did not contain unique information to distinguish one request from another. Consequently, the output logs for the requests did not contain details about the originating request. If a request failed, determining the root cause of the failure was difficult. 

Starting with BMC Server Automation version 8.2 SP1, requests to BMC Server Automation can include an optional transaction identifier. When the request is serviced, the transaction identifier becomes available in the output logs, allowing the current status or the root cause of failures to be easily determined.

Scope

In version 8.2 SP1, the Transaction Identifier is available in only the Appserver logs.

Format

The Transaction Identifier can be any character string up to 36 characters long. 

Supported interfaces

In version 8.2 SP1, the Transaction Identifier supports the following interfaces:

  • REST webservice
    • include the Transaction Identifier in the transactionId header 
  • SOAP webservice
    • include the Transaction Identifier in the transactionId header
  • BLCLI command-line
    • specify the transaction identifier as an argument using the -t flag

Enabling the transaction identifier

To allow the transaction to be available in the Appserver logs, you must perform the following actions:

  1. Execute the blasadmin command:
    SetLoggingLogformat <transactionIdentifier>
  2. Restart the Appserver.

REST schema version change

In versions earlier than 8.2 SP1, if the schema version specified in REST webservice calls was lower than 8.2, then the REST response depended on the value specified for the RestAssetAttributesUseInternalNames blasadmin flag: if set to true, the response for any REST GET call on an asset has the internal name of the asset attributes; if set to false, the display name of the asset attributes is used. The default is true

Starting with version 8.2 SP1, if the schema version specified in REST webservice calls is 8.2 or higher, then the REST response uses internal names for asset attributes, irrespective of the value specified for the RestAssetAttributesUseInternalNames blasadmin flag. 

Was this page helpful? Yes No Submitting... Thank you

Comments