BMC CMDB deployment
A CMDB is a database that holds configuration information about devices and logical constructs within the technical environment. These devices or logical constructs, called configuration items (CIs), could be assets such as servers, routers, switches, telephones, mobile devices, laptops, PCs, smoke alarms, moisture detectors, or they could be more complex, nonphysical entities such as clusters, virtual machines, or services. The CMDB stores attributes of the CIs and their relationships with other CIs. For more information about the BMC CMDB components and architecture, see in the BMC CMDB documentation.
Deploying the BMC CMDB components
The following image shows the BMC CMDB components and where to install them:
BMC Atrium Core
BMC Atrium Core is the central component of BMC CMDB that contains the CMDB engine, normalization engine, reconciliation engine, user interface, and other required plug-ins.
You must install BMC Atrium Core on the same computer where you install the Remedy Action Request System (AR System) server.
For more information about BMC Atrium Core installation, see Installing BMC Atrium Core.
BMC Atrium Core Web Services components
BMC Atrium Core Web Services provides the following components for BMC CMDB:
- Web Services infrastructure-Modified Apache Axis2 infrastructure
- BMC Atrium Core Web Services-Necessary web services for BMC Atrium Core functionality
- UDDI Web Services Registry-Central service registry (a modified Apache jUDDI Server) that makes web services available to other services and clients
You must install all of the web services components on the same computer. You can install the web services components on the same server where the BMC CMDB is installed, or on a separate server. In a server group environment, if you install the web services components on a remote computer, you must configure the web services to point to the primary server.
For more information about installing the BMC Atrium Core Web Services components, see Installing BMC Atrium Core Web Services components.
Atrium Integrator is an integration engine that helps you transfer data from external datastores to CMDB classes and AR System forms. You can connect to a wide variety of input sources, such as flat files, complex XML, JDBC, ODBC, JMS, native databases, web services, and others by using connectors. You can define the way in which external data maps to BMC CMDB and transform external data by using various rules before transferring it to CMDB classes or AR System forms.
Atrium Integrator consists of the Atrium Integrator server and Atrium Integrator client.
|Atrium Integrator server
The Atrium Integrator server processes and loads the data from an external datastore to BMC CMDB. You must install the Atrium Integrator server on the same computer where the BMC Atrium Core is installed.
After you install the Atrium Integrator server, the Atrium Integrator console is available in the Applications list on the AR System server home page. The Atrium Integrator console contains the following components:
|Atrium Integrator client
Use the Atrium Integrator client to design and run jobs that collect and send data from external data sources to the Atrium Integrator server. The server then processes and loads the data to the BMC CMDB.
You can install the Atrium Integrator client on any Windows-based computer. You need not install the client on the same computer where you install the Atrium Integrator server.
For more information about installing Atrium Integrator, see Installing Atrium Integrator.
Installation with separate Remedy AR System user accounts
In UNIX environments, if you use different accounts to run the AR System server and Apache Tomcat web server, you must be logged in with the AR System account to install all Atrium Core components. However, one exception to this rule is the BMC Atrium Web Services components.
To install BMC Atrium Web Services, you must be logged in with the Apache Tomcat web server user's account because the AR System account does not have permission to write files to the web server.
If you do not follow these steps, the root user will not be able to correct any installation error. If you run the installer as root, it does not recognize the temporary files and system variables set up by the installer with any other accounts.