Space banner


This documentation supports the 20.02 version of BMC Digital Workplace Advanced.

To view the latest version, select the version from the Product Version menu.

Integrating Remedy applications with BMC Digital Workplace Catalog

Enable the Remedy Action Request System (AR System) application integration so BMC Digital Workplace Catalog workflows can communicate with Remedy applications or applications developed on the Remedy platform.

Functionality enabled through Remedy application integration

The following table shows a few examples of the features that require this integration.

Remedy applicationExample of integrated functionality
BMC Approval Central

A service catalog administrator can design a workflow that sends a request for approval before fulfilling the request. 

For more information, see Workflow to request approval.

BMC Service Request Management or BMC HR Case Management

Information is sent from the Remedy server back to BMC Digital Workplace Catalog. For example, the integration script installs the INT:DWPWOI:WOI:ServiceRequestStubUpdate_WorkOrderStatusChange filter in Remedy IT Service Management. This filter sends a work order status each time the value is changed.

Custom applications developed on the Remedy platform

A BMC Digital Workplace Catalog workflow can use generic actions to create and modify records through any AR System form.

For more information, see Remedy connector.

Integration process overview

The following diagram illustrates the process for integrating Remedy applications with BMC Digital Workplace Catalog so that end users can request services.

An administrator runs the integration script on each AR System server that hosts a unique Remedy application. The integration script installs the required objects and populates the database entries that support the integration. Afterwards, the administrator must create records through the configuration forms to define the relationship between the Remedy application and the BMC Digital Workplace Catalog server. For Remedy applications deployed in a server group, run the integration on the primary server only. Then, duplicate the ARSystemInstallDir/remoteaction folder onto each of the secondary servers.

The catalog administrator configures a connection that uses the Remedy connector to connect to the Remedy application server. If applications run on different servers, the catalog administrator must create and configure a connection for each server, and must also set the default connection for ITSM functionality.  After completing the integration, the catalog administrator creates services that use the connection, and end users request the services.

Before you begin


If you have installed BMC Remedy ITSM 19.02 Patch 1, and also downloaded and installed the Remedy ITSM Version 19.02.00 Patch 001 Deployment Management Package for BMC Digital Workplace Advanced 19.05.00 patch, you do not need to download and install the BMC Digital Workplace Advanced ITSM Integration Patch Version 19.05.00 patch from the BMC Digital Workplace installation files. You must configure connections for ITSM functionality as described below.

The Remedy ITSM Version 19.02.00 Patch 001 Deployment Management Package for BMC Digital Workplace Advanced 19.05.00 patch is also compatible with BMC Remedy ITSM 18.08 Patch 1 and 19.02.00.

  • Download the file from BMC Electronic Product Distribution (EPD).

    For instructions, see Downloading the BMC Digital Workplace Catalog installation files.


    If you are upgrading BMC Digital Workplace Catalog from an earlier version, perform the integration with the latest script version to ensure compatibility with this release.

    Before you perform the integration on an AR System server, rename the existing ARSystemInstallDir/remoteaction folder so that the script will create a new folder.


    • (Windows) Rename C:\Program Files\BMC\ARSystem\remoteaction to C:\Program Files\BMC\ARSystem\remoteactionOLD.
    • (Linux) Rename /opt/bmc/ARSystem/remoteaction to /opt/bmc/ARSystem/remoteactionOLD.
  • Obtain the credentials to administer the AR System server.

    ParameterExample value

  • For each application to be integrated, enable the AR System Object List on the server.
    For instructions, see "To enable and use the AR System Object List" in Setting up a Remedy Mid Tier for system administration of the BMC Digital Workplace Catalog server.

  • (Optional) To inspect the objects that the integration script creates, configure BMC Remedy Developer Studio with access to the AR System server.
    For instructions, see  Starting and logging on to Remedy Developer Studio Open link .

To run the Remedy application integration script

  1. Copy the file onto the AR System server, and extract the files into a temporary folder.

    Example: CurrentUser\Downloads\Remedy-ITSM-integration-patch-for-BMC-Digital-Workplace-Catalog

  2. Open a command-line or terminal window.
  3. Ensure that the JAVA_HOME environment variable is set.


    > echo %JAVA_HOME%


    # echo $JAVA_HOME

    If the JAVA_HOME environment variable is not set, set it.


    > set JAVA_HOME="C:\Program Files\Java\latest"


    # export JAVA_HOME=/usr/java/latest
  4. Run the script for the server operating system.


    > install.bat
    Enter AR System install directory :C:\Program Files\BMC Software\ARSystem
    Enter AR System admin user :Demo
    Enter AR System Password :password
    Enter ITSM hostname :bmc-itsm-sample
    Enter port number [zero if no port] : 0


    # sh ./
    Enter AR System install directory :/opt/bmc/ARSystem
    Enter AR System admin user :Demo
    Enter AR System Password :password
    Enter ITSM hostname :bmc-itsm-sample
    Enter port number [zero if no port] :0


    The Linux script packaged in the zip archive is not executable. To run the script, perform one of the following tasks:

    • Invoke the sh command-line interpreter to run ./
    • Issue the command chmod +x to make the script executable.

    The script copies the required files and installs the forms, filters, and escalations.

To verify that the installation is complete

After you run the integration script the first time, you might want to inspect the files, forms, filters, and escalations that were loaded onto the server. You do not have to verify the creation of these objects with every integration.

  1. Open the Remedy AR System ARSystemInstallDir folder and check for the creation of a remoteaction folder. The same files are created on both Windows and Linux systems.

    Contents of C:\Program Files\BMC\ARSystem\remoteaction folder

  2. Open BMC Remedy Developer Studio and log on as the AR System administrator.

  3. Verify whether the following forms have been created. Also verify that filters and escalations have been created for the forms listed below.


If all the files, forms, filters, and escalations were created as described, then the installation was successful.

To configure the callback to the BMC Digital Workplace Catalog server from the AR System server

Use the Remedy Mid Tier for the AR System server to create records to specify the BMC Digital Workplace Catalog server that will receive the callbacks.

  1. Open the AR System Objects List on the mid tier by using a URL similar to the following example. Replace <>  with the address of the AR System server.

  2. When you are prompted, log in as an administrative user who has access permission to use the SB:RemoteApprovalConfiguration forms to create records:


    Some systems require the AR System administrator to access these forms. Other systems allow an application administrator to access these forms. Contact your IT administrator if you are not sure.

  3. Search for the SB:RemoteApprovalConfiguration form, and create the following record with values that match your system configuration:



    Values that apply to the target BMC Digital Workplace Catalog server


    Server name of the BMC Digital Workplace Catalog server. You do not need to specify http or https.

    If the BMC Digital Workplace Catalog server is configured with a load balancer for SSL access or high availability deployment, specify the hostname of the load balancer.

    Remote Port8008

    Port number used to access the BMC Digital Workplace Catalog application, not the platform (9988).


    Enable if the BMC Digital Workplace Catalog server is configured for SSL access.

    Remote User Namehannah_admin@calbroservices.comTenant administrator user account.
    SBE Login End point/api/myit-sb/users/loginEndpoint for authentication.
    SBE Signal End point/api/myit-sb/processes/signalEndpoint for process completion responses.

To configure connections for ITSM functionality

A catalog administrator must configure at least one connection that uses the Remedy connector. To use Atrium Configuration Management Database (CMDB) functionality, a catalog administrator must also configure a connection that uses the CMDB connector.  When you create the first connection for the Remedy connector, the system sets this connection as the default connection for entitlements and approvals. If you are integrating with Atrium Configuration Management Database (CMDB), when you create the first connection for the CMDB connector, the system sets this as the default CMDB connection. For information on creating connections, see Configuring service connectors.

To set the default connections for ITSM functionality

If you have more than one connection that uses the Remedy connector or more than one connection that uses the CMDB connector, a catalog administrator can set the default connection in BMC Digital Workplace Catalog. 

To change the default connections from the default values set by the system:

  1. Click the configuration gear () to open the Application Settings panel.
  2. In the Connectors section, click the arrow (>) to open the Default Connections panel, and select the applicable connections:
    • Entitlement/Approval—Displays connections that use the Remedy connector. Select the connection to the BMC Service Request Management server. The connection to this server is used for entitlements and approvals, and should connect to the same Remedy ITSM server that is configured in BMC Digital Workplace.
    • CMDB—Displays connections that use the CMDB connector. Select the connection to Atrium CMDB. 
  3. Click Save.

Troubleshooting the integration

Perform these tasks if you experience any problems while running workflows after you configure the integration to an AR System server.

Options to troubleshoot the AR System server integration

  • To monitor a request to observe the fields that a filter action updated, log on to the mid tier to access the AR System server and search for records created through the SB:ServiceRequestStub form.
  • To investigate issues with the integration script, log in to the AR System server and examine the following log:
    • (WindowsC:\Program Files\BMC Software\ARSystem\log\remoteaction.log
    • (Linux/opt/bmc/ARSystem/log/remoteaction.log
  • To troubleshoot issues with the approval engine, log in to the AR System server and examine the approval log (which must be enabled):
    • (WindowsC:\Program Files\BMC Software\ARSystem\arserver\db\arapprov.log
    • (Linux/opt/bmc/ARSystem/arserver/db/arapprov.log
    To enable the approval log, log in to the mid tier and update the setting under Quick Links > Approval Administration Console > Server Settings.
    For more information, see Remedy Approval Server configuration file settings Open link .

To troubleshoot the communication from the BMC Digital Workplace Catalog server

  1. Open the BMC Digital Workplace Catalog server file system. Replace <installLocation> with the location of your BMC Digital Workplace Catalog application, for example:
  2. Review the following log: <installLocation>/db/bundle.log
    • (RecommendedRun-time log example

      # tail -f /opt/bmc/digitalworkplace/db/bundle.log
    • Text editor log example

      # vi /opt/bmc/digitalworkplace/db/bundle.log

Where to go from here

To configure connections to additional Remedy application servers, see Configuring service connectors.

To import services from Remedy Service Request Management, see Importing service catalog items from external systems.

To create services, see Adding and updating services.

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


  1. Jonatan Garicano

    After running the Remedy application integration script version 20.02.02 from the, the SB:LocalApprovalConfiguration form is missing. I checked out the content of SB_Approval_App.def and there is not such form in it. Is that form still needed or has been deprecated?

    Aug 19, 2021 06:43
    1. Ravee Panjwani

      Thanks for your comment, Jonatan Garicano. You are right, that form has been deprecated. I will update the content and publish an update later this week.

      Aug 23, 2021 01:19