On-premises scenarios for Operations Management
This topic presents the scenarios available in a deployment of Operations Management together with the associated architectures.
Deployment scenarios
This section describes possible deployment scenarios.
- Deployment scenario 1: low capacity with IDUC channel
- Deployment scenario 2: medium capacity with AEN channel
- Deployment scenario 3: medium capacity with IDUC channel
- Deployment scenario 4: high capacity with IDUC channel
- Deployment scenario 5: high capacity with AEN channel
- Deployment scenario 6: very high capacity with AEN channel
Deployment scenario 1: low capacity with IDUC channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | Illustration of this architecture |
---|---|---|---|---|---|
Inserts only | Basic, failover, and desktop architecture | Low | Not applicable | IDUC | See Figure 1. Disregard the reference to reinserts in item 1 . |
Deployment scenario 2: medium capacity with AEN channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | Illustration of this architecture |
---|---|---|---|---|---|
Inserts and reinserts | Basic, failover, and desktop architecture | Medium | Not applicable | AEN | See Figure 1. |
Deployment scenario 3: medium capacity with IDUC channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | Illustration of this architecture |
---|---|---|---|---|---|
Inserts only | Multitier | Medium | Aggregation layer | IDUC | See Figure 2. Disregard the reference to reinserts in item 1 . |
Deployment scenario 4: high capacity with IDUC channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | |
---|---|---|---|---|---|
Inserts only | Multitier | High | Collection layer | IDUC | See Figure 3. Disregard the reference to reinserts in item 1 . |
Deployment scenario 5: high capacity with AEN channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | |
---|---|---|---|---|---|
Inserts and reinserts | Multitier | High | Aggregation layer | AEN | See Figure 2. |
Deployment scenario 6: very high capacity with AEN channel
Event volume | Architecture of Netcool/OMNIbus | Capacity of Operations Analytics - Log Analysis | Connection layer | IDUC or AEN | |
---|---|---|---|---|---|
Inserts and reinserts | Multitier | Very high | Collection layer | AEN | See Figure 3. |
Illustrations of architectures
The following sections show the architecture of Operations Analytics - Log Analysis deployments and how they fit into the various architectures of Netcool/OMNIbus deployments with the Gateway for Message Bus.
The data source that is described in the figures is the raw data that is ingested by the Operations Analytics - Log Analysis product. You define it when you configure the integration between the Operations Analytics - Log Analysis and Netcool/OMNIbus products.
Basic, failover, and desktop architectures
The following figure shows how the integration works in a basic, failover, or desktop Netcool/OMNIbus architecture. This figure is an illustration of the architectures that are described in Table 1 and Table 2. In the case of the architecture in Table 1, disregard item 1 in this figure.
Multitier architecture, events are sent from the Aggregation layer
The following figure shows how the integration works in a multitier Netcool/OMNIbus architecture, with events sent from the Aggregation layer. This figure is an illustration of the architectures that are described in Table 3 and Table 5. In the case of the architecture in Table 3, disregard item 1 in this figure.
Multitier architecture, events are sent from the Collection layer
The following figure shows how the integration works in a multitier Netcool/OMNIbus architecture, with events sent from the Collection layer. This is a best practice for integrating the components. This figure is an illustration of the architectures that are described in Table 4 and Table 6. In the case of the architecture in Table 4, disregard item 1 in this figure.