Installation of the Remedy ITSM Component


This chapter describes the installation of the Remedy ITSM components of VIPCON E-Bonding Runbook for BMC Atrium Orchestrator.

Import of the E-Bonding Runbook Groups

File: 01_EBONDING_Groups.arx

  • Login with a Remedy ARS "Administrator" user
  • Login with the BMC Remedy Data Import Tool
  • Connect to the Remedy ARS Server, where ITSM is installed and the new E-Bonding Runbook needs to be installed. For server groups, we recommend to connect to admin node.
  • Create new mapping file…
  • Select the import data (.arx archive)
  • Select the target server
  • Select the target form name: Group
  • Auto Map…
  • Start importing…

worddavf854c1d7a99078419d8d9eb6e7814ae3.png
Figure 11 Import E-Bonding Runbook Groups

Import of the E-Bonding Runbook Permission Groups

File: 02_EBONDING_Permissions.arx

  • Login with a Remedy ARS "Administrator" user
  • Login with the BMC Remedy Data Import Tool
  • Connect to the Remedy ARS Server, where ITSM is installed and the new E-Bonding Runbook needs to be installed. For server groups, we recommend to connect to admin node.
  • Create new mapping file…
  • Select the import data (.arx archive)
  • Select the target server
  • Select the target form name: LIC:SYS-License Permission Map
  • Auto Map…
  • Verify options…

worddavf201ba0fe2201eff9186b9effc0c4524.png
Figure 12 Import Options

  • Start importing…

worddave345ab7688d1d27992c4235e05664ed2.png
Figure 13 Import E-Bonding Runbook Permission Groups

Import of the E-Bonding Runbook Application

  • Login with a Remedy ARS "Administrator" user
  • Login with the BMC Remedy Developer Studio
  • Connect to the Remedy ARS Server, where ITSM is installed and the new E-Bonding Runbook needs to be installed. For server groups, we recommend to connect to the group's admin node.
  • Make sure, that the mode "Base Development" is activated within the BMC Remedy Developer Studio.

worddav25adfa8150f255ad77e2a91ffc537cfc.png
Figure 14 Base Development Mode
Import of the E-Bonding Runbook Application .def archive:
 File: 03_EBONDING_Application.def
 File > Import > Application > Select target server > Choose import file > Finish
Import of the E-Bonding Runbook Flashboards .def archive:
 File: 04_ EBONDING_Flashboards.def
 File > Import > Object Definitions > Select target server > Choose import file > All objects… > Finish
Import of the E-Bonding Runbook Event Filter .def archive:
 File: 05_ EBONDING_EventFilter.def
 File > Import > Object Definitions > Select target server > Choose import file > All objects… > Finish

Activating the E-Bonding Runbook Application

Assigning the VIPCON E-Bonding Runbook Roles

  • Login with a Remedy ARS "Administrator" user
  • Login with the BMC Remedy Midtier Application
  • Use this URL:

http://<MIDTIER_SERVER_NAME>/arsys/forms/<ITSM_SERVER_NAME>/Roles/Default+Admin+View

  • Assign the corresponding groups to the role "BGI Admin"

worddav2bb68366507685ebd47b0a946eff6085.png
Figure 15 BGI Admin Role

  • Assign the corresponding groups to the role "BGI User"

worddavff4ae12596bd1f2f3c5ebf69ec1384c4.png
Figure 16 BGI Runbook User Role
Activation of the VIPCON E-Bonding Runbook Application:

  • Login with a Remedy ARS "Administrator" user
  • Login with the BMC Remedy Developer Studio
  • Connect to the Remedy ARS Server, where ITSM is installed and the new E-Bonding Runbook needs to be installed. For server groups, we recommend to connect to the group's admin node.
  • Make sure, that the mode "Base Development" is activated within the BMC Remedy Developer Studio.
  • Remedy ARS Server > All Objects > Applications
  • Open the application VIPCON E-Bonding Runbook for BMC Atrium Orchestrator
  • Change the state of the application under "General" to "Production" and save the application.

worddav60c02e83f1c2236a6fb14cade98a73c8.png
Figure 17 Application State

Activating BAO Filter

The E-Bonding Runbook application is imported with filters that perform outbound calls to the E-Bonding Runbook Atrium Orchestrator.
 After the installation of the deployable application, the filters are disabled. They need to be enabled and reconfigured manually. This applies to the following list of filters:

  • VIP:BGI:CORE:Sync:PerformAOCall
  • VIP:BGI:CORE:Retry:PerformAOCall
  • VIP:BGI:EE:IM:PerformAOCall (required for E-Bonding Runbook Incident module)
  • VIP:BGI:EE:IM:TS:PerformAOCall (required for E-Bonding Runbook Incident module)
  • VIP:BGI:EE:CM:PerformAOCall (required for E-Bonding Runbook Change module)
  • VIP:BGI:EE:CM:TS:PerformAOCall (required for E-Bonding Runbook Change module)

The next chapters describe the adjustments of the filter workflow. Unfortunately, this has to be done manually. By today, BMC Software doesn't support parameterized imports of filter workflows.
Prerequisite: The BAO module VIP_BGI_Core must be activated on the Grid to perform these steps.

VIP:BGI:CORE:Sync:PerformAOCall

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddav7e8a0ee33b2437f5f99cdf2cc256f212.png
Figure 18 VIP:BGI:CORE:Sync:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: PartnerConfiguration:ARCall:updatePartnerDefinition

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    Action -> ztmp_Action
    PartnerID -> ztmp_PartnerId

    The result should look similar to this:
    worddav28aa52d42b7c19d7af460acc0575fa10.png
    Figure 19 VIP:BGI:CORE:Sync:PerformAOCall Set Fields Action

    VIP:BGI:CORE:Retry:PerformAOCall

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddav2cfe3d5bc63e1da60656d24b8368989b.png
Figure 20 VIP:BGI:CORE:Retry:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: MessageLibrary:Outbound:ARCall:retryMessage

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    MessageID -> ztmp_MessageID
    TransactionID -> ztmp_TransactionID

    The result should look similar to this:
    worddav546ae0961c239efc91348677aba1bf51.png
    Figure 21 VIP:BGI:CORE:Retry:PerformAOCall Set Fields Action

    VIP:BGI:EE:IM:PerformAOCall

    Hint: This filter configuration is only needed for customers, using E-Bonding Runbook Incident.

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddavbd680e7fc60c9494980eb21c2de1b3b2.png
Figure 22 VIP:BGI:EE:IM:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: MessageLibrary:Outbound:ARCall:saveEvent

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    ChildRequestNumber -> ChildRequestNumber
    ITSMTicketID -> Incident Number
    Operation -> EnabledForMessage
    PartnerID -> PartnerId
    PartnerTicketID -> PartnerTicketId
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c3b96738-588c-414b-9978-f18e369e8268"><ac:plain-text-body><![CDATA[Status -> [EMPTY]

    ]]></ac:plain-text-body></ac:structured-macro>

    The result should look similar to this:
    worddav8e833c4dc47d0e590ec5d5385fc1f7f5.png
    Figure 23 VIP:BGI:EE:IM:PerformAOCall Set Fields Action

    VIP:BGI:EE:IM:TS:PerformAOCall

    Hint: This filter configuration is only needed for customers, using E-Bonding Runbook Incident.

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddav6683b3c73eac7e044c4872f216f4be1b.png
Figure 24 VIP:BGI:EE:IM:TS:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: MessageLibrary:Outbound:ARCall:saveEvent

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    ChildRequestNumber -> ChildRequestNumber
    ITSMTicketID -> IncidentNumber
    Operation -> EnabledForMessage
    PartnerID -> PartnerId
    PartnerTicketID -> PartnerTicketId
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="f1e1cae4-5819-46f2-b80e-df085cac68c3"><ac:plain-text-body><![CDATA[Status -> [EMPTY]

    ]]></ac:plain-text-body></ac:structured-macro>

    The result should look similar to this:
    worddav8e833c4dc47d0e590ec5d5385fc1f7f5.png
    Figure 25 VIP:BGI:EE:IM:TS:PerformAOCall Set Fields Action

    VIP:BGI:EE:CM:PerformAOCall

    Hint: This filter configuration is only needed for customers, using E-Bonding Runbook Change.

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddav708844af654832cd06ba9867d4002bee.png
Figure 26 VIP:BGI:EE:CM:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: MessageLibrary:Outbound:ARCall:saveEvent

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    ChildRequestNumber -> ChildRequestNumber
    ITSMTicketID -> ChangeID
    Operation -> EnabledForMessage
    PartnerID -> PartnerId
    PartnerTicketID -> PartnerTicketId
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="c850c98b-aaa6-4752-8847-62d1432cf20b"><ac:plain-text-body><![CDATA[Status -> [EMPTY]

    ]]></ac:plain-text-body></ac:structured-macro>

    The result should look similar to this:
    Different on customer environments worddav96008b8d50f8b2ef4975d244ad54cd4c.png
    Figure 27 VIP:BGI:EE:CM:PerformAOCall Set Fields Action

    VIP:BGI:EE:CM:TS:PerformAOCall

    Hint: This filter configuration is only needed for customers, using E-Bonding Runbook Change.

  • Open the filter
  • Change the state to "Enabled"
  • Delete the existing Set Fields – If Action

worddaveecfc6fc5ee0b6f8c60e6282310c581d.png
Figure 28 VIP:BGI:EE:CM:TS:PerformAOCall

  • Create a new Set Fields action with this list of settings

    Setting

    Value

    Data Source

    BMC ATRIUM ORCHESTRATOR

    Configuration Name

    Select the Atrium Orchestrator Server

    Service URL

    Filled automatically

    Grid Name

    Filled automatically

    Operation

    Asynchronous Execution

    Add Process

    Module: VIP_BGI_Core
    Process: MessageLibrary:Outbound:ARCall:saveEvent

    Input Mapping

    Username: Filled automatically
    Password: Filled automatically
    ChildRequestNumber -> ChildRequestNumber
    ITSMTicketID -> ChangeNumber
    Operation -> EnabledForMessage
    PartnerID -> PartnerId
    PartnerTicketID -> PartnerTicketId
    <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="49f1d1d1-33e7-4e57-acbc-1a565483b9c2"><ac:plain-text-body><![CDATA[Status -> [EMPTY]

    ]]></ac:plain-text-body></ac:structured-macro>

    The result should look similar to this:
    Different on customer environments worddav96008b8d50f8b2ef4975d244ad54cd4c.png
    Figure 29 VIP:BGI:EE:CM:TS:PerformAOCall Set Fields Action

    Finishing the Installation

    It's recommended to restart the following Remedy server components after the installation procedure is finished:

  • Restart of the BMC Remedy ARS server (all nodes in case of a server group)
  • Restart of the BMC Remedy Midtier server (all nodes in case of a server group)


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

VIPCON E-Bonding Run Book for BMC Atrium Orchestrator version 2.0