Known Issues

This chapter describes known issues with the used BMC platforms.

BAO User Limitations

E-Bonding Runbook makes use of several BAO users for internal and external webservice calls. One example is the BAO user in the E-Bonding Runbook Partner Configuration.

Figure 30 BAO User Limitations
BMC Atrium Orchestrator is limited for such users. Please avoid and special characters in user names and passwords.

BAO Remedy Actor Adapter for Attachments

The BMC Remedy Actor Adapter (ro-adapter-remedy-actor) has an issue in older versions than version
In older versions, if an attachment is uploaded to Remedy ARS, then the full path of the attachment is stored in the attachment-name value.
Please visit the vendor website and check for hotfixes or use the adapter version mentioned above (and newer).

Import E-Bonding Runbook Deployable Application

In BMC Remedy AR System 8.x, at the end of the import of the Deployable Application (VIPCON E-Bonding Runbook for BMC Atrium Orchestrator) a known error can show up. The error is about a timeout and can be ignored.
In addition, the import report shows warnings (in case of a E-Bonding Runbook upgrade) that can be ignored as well.

Figure 31 Import E-Bonding Runbook Deployable Application

Upgrading the E-Bonding Runbook for BMC Atrium Orchestrator modules

In case of an upgrade of the BMC Atrium Orchestrator module example: "VIP_BGI_Core", the process execution permissions may get lost.
Please check the permissions in the Grid Manager according to chapter 5.6.

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