This chapter offers detailed information regarding required software versions and sizing of the E-Bonding Runbook platforms.

Platform Requirements

VIPCON E-Bonding Runbook for BMC Atrium Orchestrator extends and makes use of the following BMC Software technology platforms:

• BMC Remedy ITSM Suite 7.6.04 or higher
• BMC Atrium Orchestrator 7.6.04 or higher

The extension of BMC Remedy ITSM Suite in fact is a Remedy deployable application that can be installed in addition to the ITSM forms and workflows. The E-Bonding Runbook deployable application leaves the ootb code as it is. This ensures the BMC upgrade capabilities for 100%. The module comes along with clear defined groups and roles.
The extension of BMC Atrium Orchestrator is implemented in multiple Orchestrator modules. The BMC upgrade capability is 100% given.
The picture shows how E-Bonding Runbook integrates into the BMC Software platforms BMC Remedy ITSM Suite and BMC Atrium Orchestrator. In addition to those platforms, E-Bonding Runbook requires a database schema for the Transaction Database.

Figure 1 E-Bonding Runbook Architecture
The following list of BMC Software tools is required to perform the E-Bonding Runbook installation:

• BMC Remedy Data Import
• BMC Remedy Development Studio
• BMC Remedy Midtier
• BMC Atrium Orchestrator Development Studio
• BMC Atrium Orchestrator Grid Manager

Sizing Requirements

E-Bonding Runbook mainly challenges the BAO platform. This chapter describes 3 sizing recommendations for BAO platforms to operate E-Bonding Runbook.

Small Environment

For a small BAO environment we recommend following architecture:

Figure 2 Small Environment
The environment consists of two HA-CDPs, installed on separate servers. All servers can be virtual with following properties:

Medium Environment

For a medium BAO environment we recommend following BAO architecture:

Figure 3 Medium Environment
The environment consists of two HA-CDPs and one ActivityPeer (AP) all running on separate servers. All servers can be virtual with following properties:

Large Environment

For a large BAO environment we recommend following BAO architecture:

Figure 4 Large Environment
The environment consists of two HA-CDPs and two ActivityPeers (AP) all running on separate servers. All servers can be virtual with following properties:

Prepare the ITSM Suite

Prior to the installation, the E-Bonding Runbook Atrium Orchestrator environment must be configured in ITSM.

Orchestrator Configuration

The Orchestrator configuration is a prerequisite for the Event Engine to work correctly.

• Login with a Remedy ARS "Administrator" user
• AR System Administration > AR System Administration Console > System > General > Orchestrator Configuration

Figure 5 AR System Orchestrator Configuration Sample
Additional information how to configure BAO for ITSM is available at the BMC product documentation.

Orchestrator User Configuration

The BAO VIP_BGI_Core module requires a Remedy ARS admin user with sufficient permissions.
Minimum permissions for the E-Bonding Runbook Incident Management module *:

• Administrator
• Incident Master
• Asset Viewer
• BGI Admin
• BGI User

Minimum permissions for the E-Bonding Runbook Change Management module *:

• Administrator
• Change Master
• Asset Viewer
• BGI Admin
• BGI User

• The permissions can be combined if customers use both modules E-Bonding Runbook Incident & Change.
  The user requires a "Fixed" license.
  Additional information how to configure ITSM users is available at the BMC product documentation.