Infrastructure Management installation and configuration process overview
Before you install, you must plan the deployment. If you are upgrading from a previous version, see Upgrading the Infrastructure Management components.
| Step | Task | Reference |
|---|---|---|
| 1 | Install Remedy Single Sign-On and the Presentation Server, and import the Infrastructure Management PATROL repositories. Note The Remedy Single Sign-On Server must be installed before the Presentation Server. | |
| 2 | Download the installation distribution and perform prerequisite tasks for the host systems. Run the preinstallcheck utility. | |
| 3 | Install one or more TrueSight Infrastructure Management Servers according to your deployment plan. Choose to install with the standard installer or with the silent installer. For high availability deployments, you must Install Infrastructure Management in high availability mode. Also, choose the appropriate installer for the host system platform and database (SAP SQL Anywhere or Oracle). The TrueSight Infrastructure Management Server installation includes the following components:
| Installing the Infrastructure Management Server (standard installer) Installing Infrastructure Management silently Installing Infrastructure Management in high availability cluster mode |
| 4 | License the server and verify the installation was successful. | Applying Infrastructure Management licenses Obtaining the fingerprint for the Infrastructure Management Server |
| 5 | (Optional) If you chose Oracle as the database, and you have multiple Infrastructure Management servers, connect those servers to the same Oracle database. | Considerations and best practices for deploying the Oracle database Configuring multiple Infrastructure Management child servers to connect to the same Oracle database |
| 6 | Depending upon your deployment architecture, install at least one (if not more) remote Integration Service nodes. Best practice The Integration Service must always be installed on a dedicated computer separate from the TrueSight Infrastructure Management Server. This setup avoids unexpected performance impact of the Integration Service on the Infrastructure Management Server and of the Infrastructure Management Server on the Integration Service. This setup also allows for a more scalable architecture as the number of PATROL Agents increases. | Installing the Integration Service and Cell. |
| 7 | (Optional) Install the Infrastructure Management Central Server. A Central Server is only required in the following scenarios: | Infrastructure Management multiple-server deployment architecture Installing the Infrastructure Management Server (standard installer) Installing Infrastructure Management silently Installing Infrastructure Management in high availability cluster mode |
| 8 | Install the Infrastructure Management administrator console on a remote computer | Downloading and installing the administrator console on remote computers. |
| 9 | Install BMC product integrations. | Installing the BMC CMDB Extensions to enable integration with Atrium CMDB Installing BMC Impact Model Designer Installation and upgrade considerations for BMC Event Adapters |
| 10 | Configure the Infrastructure Management system components. The following items can be configured during the installation:
| Configuring Infrastructure Management after installation |
| 11 | If you did not do so during the installation, configure the performance and tuning parameters (heap size, and so on) based on the size of your deployment and type of deployment. | Performance tuning recommendations for data and event management Performance tuning recommendations for event and impact management |
| 12 | (Optional) Configure the Integration Service on the Infrastructure Management Servers to be a staging Integration Service. This protects the Infrastructure Management Server by preventing the Integration Service node installed on it from consuming resources related to data collection. Dedicate the resources on the BMC TrueSight Infrastructure Management Server to server activities and distribute all of the data collection. |
Managing Integration Service
|
| 13 | Connect additional remote Integration Service nodes to the Infrastructure Management Server and configure according to best practices. Implement a standard naming practice that uniquely identifies each Integration Service node and has technical relevance. For example, name the nodes according to the domain in which they are installed. | Integration Service host deployment and best practices for event processing and propagation |
| 14 | For high availability, configure Integration Service clusters. Do not perform when you are connecting the Integration Service nodes to the Infrastructure Management Servers. |
Administering Integration Service clusters
High-availability deployment and best practices for Infrastructure Management |
| 15 | Configure integrations. These integrations can be configured during installation:
|
Where to go next
For monitoring data configuration, go to
Monitoring parameter configuration best practices
.
For service model configuration, go to
Defining service models
.
Related topics
Implementation phases for Operations Management for TrueSight Operations Management
Comments
Log in or register to comment.