This appendix provides guidelines for the recommended minimum hardware requirements to achieve daily service. Use these guidelines to calculate the required hardware for the Oracle Communications Design Studio users to whom you will distribute a preconfigured installation.
Because vendors continuously update their hardware models, check vendor websites for the latest models and specifications. All hardware estimates are guidelines based on Oracle Communications performance lab testing and deployment experience.
Note:
The sizing estimates contained in this appendix are based on the assumptions of proper application configuration and tuning, in a manner consistent with leading practices of Oracle Communications consulting and performance engineering. This information is provided for informational purposes only and is not intended to be, nor shall it be construed as a commitment to deliver Oracle programs or services. This appendix shall not form the basis for any type of binding representation by Oracle and shall not be construed as containing express or implied warranties of any kind. You understand that information contained in this appendix will not be a part of any agreement for Oracle programs and services. Business parameters and operating environments vary substantially from customer to customer and as such not all factors, which may impact sizing, have been accounted for in this appendix.Use the following procedure to determine the recommended minimum hardware required to achieve daily service:
Review the number of ASAP atomic actions, the Order and Service Management (OSM) order complexity, the number of Inventory services, and the number of Network Integrity model entities in all of your application cartridges.
The number and type of these entities determine whether your implementation falls into the small, medium, or large category. See "Design Studio Implementation Size Definitions" for more information.
Calculate your Design Studio requirement score for the implementation size.
See "Design Studio Hardware Requirement Scores" for more information.
Use the Design Studio hardware requirement score to determine the hardware size category that your installation requires.
See "Design Studio Hardware Requirement Size Categories" for more information.
Refer to the minimum hardware requirements for your hardware size category.
See "Recommended Minimum Hardware Requirements" for more information.
Table A-1 illustrates how Oracle defines Design Studio implementation size definitions, based on the total number of entities of all application cartridges.
Table A-1 Design Studio Implementation Size Definitions
| Application Cartridge | Small | Medium | Large |
|---|---|---|---|
|
ASAP number of atomic actions |
Fewer than 50 |
50 to 300 |
More than 300 |
|
OSM order complexity (x1000) |
Fewer than 10 |
10 to 75 |
More than 75 |
|
Inventory number of services |
Fewer than 30 |
30 to 60 |
More than 60 |
|
Network Integrity number of model entities |
Fewer than 40 |
40 to 80 |
More than 80 |
Note:
Order complexity is calculated by adding the total number of order data nodes and the total number of task data nodes in all OSM application cartridges.To help determine your hardware requirements, a Design Studio requirement score is applied to each application implementation size. Use Table A-2 to determine your total Design Studio hardware requirement score.
The sum of the Design Studio hardware requirement scores for all application cartridges determines the hardware size category for your installation. Table A-3 displays the ranges for each hardware requirement size category.
The minimum hardware requirement recommendation for your installation is determined by the hardware sizing category. See the following topics for more information:
Table A-4 displays the minimum hardware requirements recommended for the small hardware sizing category.
Table A-5 displays the hardware requirements recommended for the medium hardware sizing category.
Table A-6 displays the hardware requirements recommended for the large hardware sizing category.
The following example describes how to determine the hardware sizing category for an installation that contains ASAP, OSM, and UIM application cartridges.
To determine the hardware sizing category for an installation:
Count the number of ASAP atomic actions in all ASAP application cartridges.
In this example, there are 151 atomic actions.
Determine the implementation size for your ASAP cartridges.
In this example, 151 atomic actions is equal to a medium size implementation, as defined in Table A-1.
Calculate the Design Studio requirement score for the ASAP implementation size.
In this example, a medium size ASAP implementation receives a score of 2, as defined in Table A-2.
Determine the OSM order complexity for all OSM application cartridges.
In this example, there are 88 order data nodes and 304 task data nodes. The order complexity is the sum of the order data and task data nodes, or 392.
Determine the implementation size for your OSM cartridges.
The order complexity is 392, which is equal to a small size implementation, as defined in Table A-1.
Calculate the Design Studio requirement score for the OSM implementation size.
In this example, a small size OSM implementation receives a score of 2, as defined in Table A-2.
Calculate the number of Inventory services in all Inventory application cartridges.
In this example, there are 26 Inventory services.
Determine the implementation size for your Inventory cartridges.
The number of Inventory services is 26, which is equal to a small size implementation, as defined in Table A-1.
Calculate the Design Studio requirement score for the Inventory implementation size.
In this example, a small size Inventory implementation receives a score of 2, as defined in Table A-2.
Calculate the number of Network Integrity model entities in all Network Integrity application cartridges.
In this example, there are 82 Network Integrity model entities.
Determine the implementation size for your Network Integrity cartridges.
The number of Network Integrity model entities is 82, which is equal to a large size implementation, as defined in Table A-1.
Calculate the Design Studio requirement score for the Network Integrity implementation size.
In this example, a large size Network Integrity implementation receives a score of 2, as defined in Table A-2.
Calculate the sum of the ASAP, OSM, Inventory, and Network Integrity Design Studio requirement scores.
Each application implementation received a requirement score of 2, the sum of which is equal to 8.
Determine the hardware sizing category of your installation.
In this example, the hardware sizing category is medium, as defined in Table A-3.
Review the recommended hardware sizing category minimum requirements for your installation.
For this example, the installation falls into the medium size hardware sizing category, and the recommendations are defined in Table A-5.