Example Deployments
Contents
apmdevops97
Contents
2
General deployment recommendations depend on these situations:
- You are deploying for the first time (Introscope-only, CA CEM-only, or CA APM).
- You are upgrading to add CA APM functionality (CA CEM and the application triage map) to your existing Introscope 9.6 deployment.
The CA Technologies sizing recommendations provide resource recommendations by environment.
Introscope-only Example Deployments
These examples show deployments in which Introscope agent monitoring is used and CA CEM monitoring is not used.
Standalone Enterprise Manager
You can use a 32-bit or 64-bit JVM.
Introscope Maximum Cluster
The MOM requires a 64-bit JVM.
Collectors handling an agent load can be 32-bit or 64-bit JVMs.
Introscope-only Example Deployment Components
Standalone Enterprise Manager
- Standalone Enterprise Manager (32 or 64 bit)
- APM database
- CA EEM (optional)
Introscope maximum cluster
- MOM (64-bit)
- Up to 10 Collectors (32- or 64-bit)
- APM database
- CA EEM (optional)
CA CEM-only Example Deployments
These examples show deployments in which CA CEM-only monitoring is used and agent monitoring is not used.
CA CEM-only On a Standalone Enterprise Manager (64-bit JVM)
If sufficient machine resources are available, all Enterprise Manager services can be colocated in a single standalone Enterprise Manager.
A 64-bit JVM is required.
Depending on machine resources, the APM database can be co-hosted on the same machine or separately hosted.
CA EEM is required.
In a CA CEM-only deployment, the Introscope Workstation or WebView not expected to be commonly used.
CA CEM-only Cluster (32-bit JVM)
A CA CEM-only deployment has only TIM monitoring, and no agent monitoring. In a CA CEM-only deployment in a 32-bit environment the following statements are true:
- One Collector hosts the TIM Collection service.
- The MOM hosts the Stats Aggregation service and the DB Cleanup service.
- Depending on machine resources, the MOM and Collector can be colocated.
- No components make active use of the SmartStor, Transaction Events, or baselines databases. Therefore the deployment does not have the file system requirements that are needed for Collectors handling an agent metrics load.
- The APM database can be on the same machine as the Collector or MOM, or on a separate machine.
- CA EEM is required.
- The MOM resource requirements are reduced because there are no Introscope users running Introscope historical queries, Workstations, or the application triage map.
CA CEM-only Example Deployment Components
These components are for an environment that performs CA CEM-only monitoring and
no
agent monitoring.CA CEM-only on a standalone Enterprise Manager (64 bit)
- Standalone Enterprise Manager (64 bit)
- APM database
- CA EEM
- TIMs
CA CEM-only cluster (32-bit JVMs)
- MOM (hosting Stats Aggregation service)
- Collector (hosting TIM Collection service and collectingnoagent metrics)
- APM database
- CA EEM
- TIMs
CA APM Example Deployments
These examples show deployments in which both agent and CA CEM monitoring are used.
CA APM Minimal Cluster (32-bit JVMs)
To support a deployment for both an agent load and CA CEM monitoring on 32-bit operating systems, a cluster deployment is required.
A CA APM minimal cluster for 32-bit JVMs can consist of a MOM and three Collectors:
- One Collector handling the agent metrics load
- One Collector hosting the TIM Collection service (no agent metrics load)
- One Collector hosting the Stats Aggregation service and the DB Cleanup service (no agent metrics load).
Do not enable agent load balancing or failover.
Depending on machine resources, the MOM and Collectors can be colocated. The Collectors hosting Enterprise Manager services do not make active use of the SmartStor, Transaction Events, or baselines databases. Therefore this deployment does not have the file system requirements that are needed for Collectors handling an agent metrics load.
CA EEM is required.
CA APM Maximum Cluster (32-bit Collectors Only)
If all your Collectors must run on 32-bit operating systems, then the maximum supported CA APM deployment is a 10 Collector cluster with 8 Collectors running agent metric workloads. The TIM Collection service and the Stats Aggregation service are each deployed on a separate Collector. In this deployment:
- Up to 8 Collectors run only agent metric load.
- One Collector hosts the TIM Collection service (no agent metrics load).
- One Collector hosts the Stats Aggregation service and the DB Cleanup service (no agent metrics load).
The maximum number of Collectors in a cluster remains 10, regardless of the distribution of the agent metrics load or the Enterprise Manager services assignments.
CA APM Maximum Cluster (At Least Two 64-bit Collectors)
The CA APM deployment with the maximum supported agent and CA CEM monitoring capacity is a 10 Collector cluster with at least two Collectors running in 64-bit JVMs. In this deployment:
- Up to 8 Collectors run only agent metric load.
- One Collector hosts the TIM Collection service and agent metrics load.
- One Collector hosts the Stats Aggregation service and agent metrics load.
The DB Cleanup service can be assigned to any Collector in the cluster because it makes relatively light use of system resources.
The maximum number of Collectors in a cluster remains 10, regardless of the distribution of the agent metrics load or the Enterprise Manager services assignments.
For the maximum number of frontend locations, agents, and metrics, all 10 Collectors can support agent connections.
CA APM Example Deployment Components
The DB Cleanup service can be assigned to any Collector in the cluster because it makes relatively light use of system resources.
Minimal cluster (32-bit platforms)
- MOM
- Collector (hosting TIM Collection service and collectingnoagent metrics)
- Collector (hosting Stats Aggregation service and collectingnoagent metrics)
- Collector (collecting agent metrics)
- APM database
- CA EEM
- TIMs
Maximum cluster (32-bit Collectors)
- MOM (64-bit)
- Collector (hosting TIM Collection service and collectingnoagent metrics)
- Collector (hosting Stats Aggregation service and collectingnoagent metrics)
- Up to 8 Collectors (32-bit) (collecting agent metrics)
- APM database
- CA EEM
- TIMs
Maximum cluster (At least two 64-bit Collectors)
- MOM (64-bit)
- Collector (64-bit) (hosting TIM Collection service and collecting agent metrics)
- Collector (64-bit) (hosting Stats Aggregation service and collecting agent metrics)
- Up to 8 Collectors (32- or 64-bit) (collecting agent metrics)
- APM database
- CA EEM
- TIMs
Upgrade from Introscope 9.6 to CA APM 9.6 to Provide CA CEM Monitoring
Upgrading from Introscope 9.6 to CA APM 9.6 requires that you understand the desired bandwidth of the monitored application traffic in your environment and how to size the number of TIMs needed.
If your existing Introscope deployment is fully utilizing its existing hardware resources, providing resources for the Enterprise Manager services is likely to require additional hardware.
The information in the following examples assumes
no
increase in monitored frontends, metrics, or number of agents. In this situation, you are upgrading only
to add CA CEM and you have no plans to increase Introscope usage.Standalone Enterprise Manager (Introscope-only 9.6)
The following additional resources are needed for upgrade:
- 64-bit Collector to host the Enterprise Manager services.
- Resources for the APM database
- Standalone Enterprise Manager converted to a Collector.
- TIMs
Post-upgrade example deployment (CA APM 9.6)
- MOM
- Collector (64-bit) hosting TIM Collection service and Stats Aggregation service and processingnoagent metrics
- Collector collecting agent metrics
- APM database
- CA EEM
- TIMs
Introscope-only, Clustered 8 or Fewer Collectors (One Computer per Collector)
The following additional resources are needed for upgrade:
- 64-bit Collector to host the Enterprise Manager services.
- Resources for the APM database
- TIMs
Post-upgrade example deployment (CA APM 9.6)
- MOM
- Collector (64-bit) hosting TIM Collection service and Stats Aggregation service and processingnoagent metrics
- Up to 8 Collectors processing agent metrics
- APM database
- CA EEM
- TIMs
Introscope-only, Clustered, 10 Collectors (One Computer per Collector)
The following additional resources are needed for upgrade:
- Replace two 32-bit Collectors with 64-bit Collectors.
- Resources for the APM database
- TIMs
Post-upgrade example deployment (CA APM 9.6)
- MOM (64-bit)
- Collector (64-bit) (hosting TIM Collection service and collecting agent metrics)
- Collector (64-bit) (hosting Stats Aggregation service and collecting agent metrics)
- Up to 8 Collectors (32- or 64-bit) (collecting agent metrics)
- APM database
- CA EEM
- TIMs