Skip to Content

Installation order of BSM Interoperability

Although other valid implementations exist, when BMC built and tested the BSM Reference Stack, products were installed in the order shown in this topic. Consult the documentation for each product for detailed information about planning, installation, and configuration.

Information
Recommendation

The Suite Stack Installer (SSI) automatically installs a mid tier on the BMC Remedy AR System server. For performance reasons, BMC recommends that you disable the mid tier on the BMC Remedy AR System server and instead install the mid tier separately on its own computer.

The following table shows the high-level installation order used in testing. Components and products marked with an asterisk (*) can be installed with the SSI.

Installation order

Order

Product or component

Special installation and configuration information

1.

Platform products — Enterprise

 

a.

BMC Remedy AR System*

 

b.

BMC Atrium Core*

 

c.

BMC Remedy IT Service Management*

 

d.

BMC Atrium Web Services

 

e.

BMC Atrium Integration Engine

 

f.

BMC Remedy Mid Tier*

Using the installation planner, you can install the BMC Remedy Mid Tier separately (recommended for optimal performance).

2.

Platform products — Cloud

 

a.

BMC Remedy AR System — Cloud:

  • Enterprise AR Cloud Portal and Public Extensions
  • Cloud AR Public and Private Extensions

Specific to the BMC Cloud Lifecycle Management Installation Planner

b.

BMC Atrium Core — Cloud

Specific to the BMC Cloud Lifecycle Management Installation Planner

3.

Service Operations — Data Center Automation products


a.

BMC BladeLogic Server Automation

 

b.

BMC BladeLogic Decision Support for Server Automation

The Oracle databases created for the BladeLogic OM and BMC BladeLogic Decision Support for Server Automation data warehouse must have the same character set.

c.

BMC BladeLogic Atrium Integration

 

d.

BMC Atrium Orchestrator Platform

 

e.

BMC BladeLogic Network Automation

Prerequisites:

  • BCAN_USER must be added and configured.
  • The BCAN database must be created before the installation.

    Note: Install the Microsoft SQL Server Native client before installing BMC BladeLogic Decision Support for Network Automation on Microsoft Windows 2008 R2.

4.

Service Operations — Proactive Operations products

 

 

BMC ProactiveNet Performance Management

  • BMC ProactiveNet Performance Management Extensions
  • BMC ProactiveNet Server (Server, Master Cell, Admin Cell, Publishing Server)
  • Impact Integration Web Services (IIWS)
  • Integration for BMC Remedy Service Desk (IBRSD)
  • When integrating BMC Capacity Optimization 4.5 with BMC ProactiveNet Performance Management 8.6.02, BMC Capacity Optimization might not receive data from the BMC ProactiveNet Performance Management database unless you have the BMC ProactiveNet Performance Management agent on the server.
  • BMC Remedy AR System and BMC Remedy ITSM components should be installed before BMC ProactiveNet Performance Management is installed.
  • BMC ProactiveNet Performance Management extensions need to be applied before running the BMC ProactiveNet Performance Management installer.
  • If you receive BMC Atrium Explorer plugin errors, ensure that Multiple Assign Groups is set in BMC Remedy AR System in the Server Information > Configuration tab, and then restart the BMC Remedy AR System server and reinstall the extensions.

5.

Other products and components

 

a.

BMC Atrium Orchestrator Content

  • To enable certain use cases (such as Triage & Remediation and Continuous Compliance use cases), modules from BMC Atrium Orchestrator Content 7.6.05_04 must be applied.
  • CLM AO Content is installed for BMC Cloud Lifecycle Management.

b.

BMC Cloud Platform (OSGi)

Specific to the BMC Cloud Lifecycle Management Installation Planner

c.

BMC PATROL

 

d.

BMC Capacity Optimization

 

e

BMC BladeLogic Decision Support for Network Automation

 

f.

BMC BladeLogic Decision Support for Server Automation

 

g.

BMC Dashboards for BSM

 

h.

BMC Analytics for BSM

 

i.

BMC IT Business Service Management

 

j.

BMC Atrium Discovery

If using virtual machines (VMs), configure the VM to discover BMC BladeLogic VMs or the BMC BladeLogic-BMC Atrium Discovery merge might fail, resulting in duplicated CIs in the Asset dataset.

6.

Solutions configuration

 

a.

Configure BMC Cloud Lifecycle Management

Use fully qualified domain names as host names.

b.

Configure BMC ProactiveNet Performance Management: Triage and Remediation (TnR)

 

c.

Configure BMC ProactiveNet Performance Management: Probable Cause Analysis (PCA)

 

d.

Configure BMC BladeLogic Data Center Automation: Continuous Compliance for Servers/Networks (CC-S/N)

Solutions should use different users when using the same setup to run different workflows and should not all use the default "orchestrationuser" account.

 

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

BSM Interoperability and BSM Reference Stack