2 Unified Inventory Management System Requirements
This chapter describes the hardware, operating system, software, server, and database requirements for installing Oracle Communications Unified Inventory Management (UIM) and its affiliated services.
Software Requirements
For details about the software required to support the UIM components, see "UIM Software Compatibility" in UIM Compatibility Matrix.
Hardware Sizing Guidelines for UIM Application
Table 2-1 provides hardware sizing guidelines for UIM application.
Note:
- The information in this section is meant as a guideline. The values in this section are approximate and consider distributed HA. Accurate sizing for a production system requires a detailed analysis of the proposed business requirements and subsequent performance tests in the desired environment.
- The following sizing guidelines are based on an average CPU utilization rate of 60% - 70%. These guidelines do not account for Disaster Recovery environments or other environments such as testing and development.
- The following benchmarking is performed on AMD EPYC™ 77J3 or any equivalent processor.
- For deployments on Oracle Cloud Infrastructure tenancies, the equivalent server is VM.Standard.E4.Flex with the specified OCPUs and memory.
UIM Volume Characteristics
Table 2-1 UIM Volume Characteristics
| Deployment Size | Small | Medium | Large | Extra-Large |
|---|---|---|---|---|
| UIM Volume Characteristics | ||||
|
Services/day |
<= 300,000 |
<= 600,000 |
<= 1,500,000 |
<= 3,000,000 |
|
Services/hour |
<= 33,500 |
<= 66,500 |
<= 166,500 |
<= 333,000 |
|
Number of Subscribers Base (in Millions) |
<= 10 |
<= 20 |
<= 50 |
<= 100 |
Note:
UIM volume characteristics are based on the 5G Mobile cartridge pack, where one service invokes five Web service operations against UIM. Each service is composed of 1 CFS and 2 RFS.
UIM Application Server Sizing
Table 2-2 UIM Application Server Sizing
| Deployment Size | Small | Medium | Large | Extra-Large |
|---|---|---|---|---|
|
UIM Traditional Application Serverx86-64/Linux Platform |
CPU: 2 x 2 core - 2.55 GHz 8 threads RAM: 2 x 30 GB HDD: 2 x 150 GB |
CPU: 2 x 4 core - 2.55 GHz 16 threads RAM: 2 x 60 GB HDD: 2 x 300 GB |
CPU: 8 x 4 core - 2.55 GHz 64 threads RAM: 8 x 60 GB HDD: 8 x 300 GB |
CPU: 14 x 4 core - 2.55 GHz 112 threads RAM: 14 x 60 GB HDD: 14 x 300 GB |
|
UIM Cloud Native Application Server |
Number of PODS: 2 Compute/POD(OCPUs): 2 RAM/POD (GB): 32 |
Number of PODS: 2 Compute/POD(OCPUs): 4 RAM/POD (GB): 64 |
Number of PODS: 4 Compute/POD(OCPUs): 4 RAM/POD (GB): 64 |
Number of PODS: 7 Compute/POD(OCPUs): 8 RAM/POD (GB): 128 |
Note:
UIM 7.5 and later cloud native deployments require an additional 5% compute resources for Kubernetes and container management.
UIM 7.5 and later versions have native application monitoring capabilities which require a minimum 2 GB additional allocation in the heap if the monitoring feature is enabled.
The Table 2-3 provides database sizing information.
UIM Database Server Sizing
Table 2-3 UIM Database Server Sizing
| Deployment Size | Number of RAC Nodes | Compute/POD (OCPUs) | RAM/POD (GB) | Initial Storage (TB) | Storage Growth (Annual in TB) |
|---|---|---|---|---|---|
| Small | 2 | 8 | 120 | 0.4 | 1.2 |
| Medium | 2 | 16 | 240 | 2 | 4 |
| Large | 2 | 24 | 320 | 4 | 6 |
| Extra-Large | 2 | 24 | 320 | 6 | 12 |
Hardware Sizing Guidelines for UIM Services
The UIM application features several components that run in a containerized form within a Kubernetes environment. The sizing for each of these components is listed in the following tables. The total value represents the hardware footprint that is required to run each component on Kubernetes. The sizing is divided between application components and database components.
Table 2-4 provides hardware sizing guidelines for UIM services.
ATA Volume Characteristics
Table 2-4 ATA Volume Characteristics
| Deployment Size | Small | Medium | Large | Extra-Large |
|---|---|---|---|---|
|
Vertices and Edges |
10 Million |
25 Million |
50 Million |
60 Million |
|
Number of Network Nodes |
0.5 Million |
1 Million |
2.5 Million |
3.5 Million |
|
Number of Equipment |
0.5 Million |
2 Million |
7.5 Million |
10 Million |
|
Number of Locations and Network Entity Codes |
0.5 Million |
1 Million |
2.5 Million |
3.5 Million |
|
Number of Connectivity |
1 Million |
2 Million |
4 Million |
6 Million |
Sizing for Application Components
This section provides hardware sizing guidelines for application components.
Note:
-
Network Plan and Design (NPD) is a module using which you can create, edit, and view networks in UIM. It uses OpenSearch and SmartSearch for searching locations, resources and connectivity to build a network using a guided flow. For more information on using NPD, see "Creating Networks" in UIM Online Help.
-
The block storage is essential for OpenSearch PODs to operate effectively. Oracle recommends you to attach block storage volume claims of the setups that are greater than 20GB with Open Source OpenSearch cluster setup. Block storage is essential for Message Bus to operate effectively.
-
The suggested sizing of ATA Consumer Unified Operations Message Bus allows a seamless processing of up to 20, 30, 50, 70 TPS respectively for Small, Medium, Large, Extra-Large size. This can be scaled up based on your requirement.
-
The suggested sizing of Alarm Consumer Unified Operations Message Bus allows a seamless processing of up to 10, 20, 40, 50 TPS respectively for Small, Medium, Large, Extra-Large size. It can be scaled up based on your requirement.
Deployment Size: Small
Table 2-5 Application Components Hardware Sizing Guidelines - Deployment Size: Small
| Component | Application POD | Number of Pods | Compute/POD (OCPUs) | RAM/POD (GB) |
|---|---|---|---|---|
| NPD or Service Impact Analysis Components | SmartSearch | 2 | 0.5 | 1 |
| SmartSearch Consumer | 1 | 0.5 | 1 | |
|
OpenSearch (Data node and Leader node) |
3 | 2 | 3 | |
| OpenSearch Dashboard | 1 | 0.25 | 1 | |
| Impact Analysis API | 1 | 0.5 | 1 | |
| Alarm Consumer | 3 | 0.25 | 1 | |
|
ATA Service and In-memory Graph |
ATA API | 2 | 1 | 3 |
| ATA UI | 1 | 4 | 6 | |
| ATA Consumer | 2 | 0.25 | 1 | |
| PGX | 2 | 2 | 10 | |
| Unified Operations Message Bus | Kafka Broker | 2 | 0.5 | 2 |
| Strimzi Operator | 1 | 0.25 | 1 | |
| Kafka Controller | 2 | 0.5 | 1 | |
| Common Authentication (optional) | OAM | 1 | 0.5 | 8 |
| OHS | 1 | 0.5 | 4 |
Deployment Size: Medium
Table 2-6 Application Components Hardware Sizing Guidelines - Deployment Size: Medium
| Component | Application POD | Number of Pods | Compute/POD (OCPUs) | RAM/POD (GB) |
|---|---|---|---|---|
| NPD and Service Impact Analysis | SmartSearch | 2 | 0.5 | 1 |
| SmartSearch Consumer | 1 | 0.5 | 1 | |
|
OpenSearch (Data node and Leader node) |
3 | 3 | 3 | |
| OpenSearch Dashboard | 1 | 0.25 | 1 | |
| Impact Analysis API | 2 | 0.5 | 1 | |
| Alarm Consumer | 3 | 0.25 | 1 | |
|
ATA Service and In-memory Graph |
ATA API | 3 | 1 | 3 |
| ATA UI | 1 | 4 | 6 | |
| ATA Consumer | 3 | 0.25 | 1 | |
| PGX | 2 | 2 | 15 | |
| Unified Operations Message Bus | Kafka Broker | 3 | 0.5 | 2 |
| Strimzi Operator | 2 | 0.25 | 1 | |
| Kafka Controller | 2 | 0.5 | 1 | |
| Common Authentication (optional) | OAM | 1 | 1 | 8 |
| OHS | 1 | 0.5 | 4 |
Deployment Size: Large
Table 2-7 Application Components Hardware Sizing Guidelines - Deployment Size: Large
| Component | Application POD | Number of Pods | Compute/POD (OCPUs) | RAM/POD (GB) |
|---|---|---|---|---|
| NPD and Service Impact Analysis | SmartSearch | 3 | 0.5 | 1 |
| SmartSearch Consumer | 2 | 0.5 | 1 | |
|
OpenSearch (Data node and Leader node) |
3 | 3 | 3 | |
| OpenSearch Dashboard | 1 | 1 | 2 | |
| Impact Analysis API | 3 | 0.5 | 1 | |
| Alarm Consumer | 5 | 0.25 | 1 | |
|
ATA Service and In-memory Graph |
ATA API | 3 | 1 | 3 |
| ATA UI | 1 | 6 | 9 | |
| ATA Consumer | 5 | 0.25 | 1 | |
| PGX | 2 | 2 | 25 | |
| Unified Operations Message Bus | Kafka Broker | 3 | 0.5 | 2 |
| Strimzi Operator | 2 | 0.25 | 1 | |
| Kafka Controller | 3 | 0.5 | 1 | |
| Common Authentication (optional) | OAM | 1 | 1 | 8 |
| OHS | 1 | 0.5 | 4 |
Deployment Size: Extra-Large
Table 2-8 Application Components Hardware Sizing Guidelines - Deployment Size: Extra-Large
| Component | Application POD | Number of Pods | Compute/POD (OCPUs) | RAM/POD (GB) |
|---|---|---|---|---|
| NPD and Service Impact Analysis | SmartSearch | 3 | 0.5 | 1 |
| SmartSearch Consumer | 2 | 0.5 | 1 | |
|
OpenSearch (Data node and Leader node) |
4 | 3 | 3 | |
| OpenSearch Dashboard | 1 | 1 | 2 | |
| Impact Analysis API | 3 | 0.5 | 1 | |
| Alarm Consumer | 7 | 0.25 | 1 | |
|
ATA Service and In-memory Graph |
ATA API | 3 | 1 | 3 |
| ATA UI | 2 | 4 | 6 | |
| ATA Consumer | 5 | 0.25 | 1 | |
| PGX | 2 | 2 | 40 | |
| Unified Operations Message Bus | Kafka Broker | 3 | 0.5 | 2 |
| Strimzi Operator | 2 | 0.25 | 1 | |
| Kafka Controller | 3 | 0.5 | 1 | |
| Common Authentication (optional) | OAM | 1 | 1 | 8 |
| OHS | 1 | 0.5 | 4 |
Sizing for Database Components
This section provides hardware sizing guidelines for database components.
Deployment Size: Small
Table 2-9 Database Components Hardware Sizing Guidelines - Deployment Size: Small
| Component | Database POD | Number of RAC Nodes | Compute/POD (OCPUs) | RAM/POD (GB) | Initial Storage (TB) | Storage Growth (Annual in TB) |
|---|---|---|---|---|---|---|
| Database Component | ATA DB | 2 | 4 | 60 | 0.3 | 0.2 |
| OAM DB (Optional) | 1 | 2 | 30 | 0.1 | 0.1 |
Deployment Size: Medium
Table 2-10 Database Components Hardware Sizing Guidelines - Deployment Size: Medium
| Component | Database POD | Number of RAC Nodes | Compute/POD (OCPUs) | RAM/POD (GB) | Initial Storage (TB) | Storage Growth (Annual in TB) |
|---|---|---|---|---|---|---|
| Database Component | ATA DB | 2 | 8 | 120 | 0.5 | 1 |
| OAM DB (Optional) | 1 | 2 | 30 | 0.1 | 0.1 |
Deployment Size: Large
Table 2-11 Database Components Hardware Sizing Guidelines - Deployment Size: Large
| Component | Database POD | Number of RAC Nodes | Compute/POD (OCPUs) | RAM/POD (GB) | Initial Storage (TB) | Storage Growth (Annual in TB) |
|---|---|---|---|---|---|---|
| Database Component | ATA DB | 2 | 12 | 160 | 1 | 1.5 |
| OAM DB (Optional) | 1 | 4 | 60 | 0.2 | 0.2 |
Deployment Size: Extra-Large
Table 2-12 Database Components Hardware Sizing Guidelines - Deployment Size: Extra-Large
| Component | Database POD | Number of RAC Nodes | Compute/POD (OCPUs) | RAM/POD (GB) | Initial Storage (TB) | Storage Growth (Annual in TB) |
|---|---|---|---|---|---|---|
| Database Component | ATA DB | 2 | 16 | 320 | 1.5 | 3 |
| OAM DB (Optional) | 1 | 4 | 60 | 0.2 | 0.2 |
Information Requirements
During UIM installation, you are required to enter configuration values such as host names and port numbers. You define some of these configuration values when you install and configure the Oracle database and WebLogic Server.
If you have already installed Oracle Communications products, the installer reads the values from the existing Oracle Communications products and uses them as default values. If no Oracle Communications products are installed, the installer uses the default values shown in the following tables.
Each chapter contains tables for the configuration values.