Sizing requirements

Your environment must meet sizing requirements for WebSphere Automation.

WebSphere Automation sizing

Choose a sizing profile that fits your purposes. By default, WebSphere Automation is deployed with the production profile, a sizing profile that is configured to provide a highly available (HA) service for larger-scale production use. The production profile provides multiple replicas of the underlying service components for redundancy. For smaller-scale production needs, or for development or testing purposes, you can use the starter profile with single replicas. For more information about customizing replica, resource requirement, or other settings, see WebSphereAutomation and WebSphereSecure custom resources.

The tradeoff between the production profile and starter profile is higher availability at the cost of more resource consumption. Both profiles support several hundreds of servers. If many hundreds of servers or more are to be managed, the production profile is better suited than the starter profile. In all cases, production traffic to the application servers is not impacted by the availability of WebSphere Automation. An unavailability of WebSphere Automation impacts only the administrative and operational tasks that are done by WebSphere Automation.

If you choose to install WebSphereSecure instead of WebSphereHealth (which contains both the health and security capabilities), use the Security only values in parentheses in the tables.

Note: The values in the tables only consider the sizing needs of the various components of WebSphere Automation and not the sizing needs for Red Hat® OpenShift®. For more information, see Red Hat OpenShift Container Platform requirements.
Note: The values in the tables do not include any requirements inherent in the storage provider. The storage infrastructure might require more resources (for example, CPU or memory) from the worker nodes.
Table 1. Production profile. Use the production profile for high availability (HA) production workloads and testing. The production profile supports multiple replicas. The production profile has been tested to ensure up to 4,000 registered instances of WebSphere Application Server or WebSphere Application Server Liberty can be supported.
Project CPU request (cores) Memory request (Gi) Disk space (Gi) Notes
IBM Cloud Pak® foundational services 4.17 7.737   For a cluster
Platform UI 1.55 4.496 50 For a deployment of WebSphere Automation within a cluster
IBM Cloud Pak foundational services 11.5 20.125 60 For a deployment of WebSphere Automation within a cluster
WebSphere Automation (Security only) 15.2 (9.9) 16.281 (9.375) 130 (80) For a deployment of WebSphere Automation within a cluster
Total* (Total for Security only) 32.42 (27.12) 48.639 (41.733) 240 (190)  

* Totals that are shown in Table 1 do not include sizing requirements for Red Hat OpenShift.

It is only possible to have one deployment of WebSphere Automation per namespace.

To deploy a starter profile, see Starter profile configuration.

Table 2. Starter profile. Use the starter profile for smaller non-production workloads, development, and testing. The starter profile is ideal for conducting Proof of Concept (PoC) validation. Refrain from using the starter profile in production environments, as it might lead to potential outages in WebSphere Automation, resulting in the persistence of inaccurate estate and vulnerability statuses upon availability restoration. Also, the starter profile does not configure multiple replicas. The starter profile supports up to 1,000 registered instances of WebSphere Application Server or WebSphere Application Server Liberty.
Project CPU request (cores) Memory request (Gi) Disk space (Gi) Notes
IBM Cloud Pak foundational services 4.17 7.737   For a cluster
Platform UI 1.05 2.598 50 For a deployment of WebSphere Automation within a cluster
IBM Cloud Pak foundational services 4.5 4.125 12 For a deployment of WebSphere Automation within a cluster
WebSphere Automation (Security only) 6.3 (3.9) 8.531 (3.625) 110 (60) For a deployment of WebSphere Automation within a cluster
Total* (Total for Security only) 16.02 (13.62) 22.991 (18.085) 172 (122)  

* Totals that are shown in Table 2 do not include sizing requirements for Red Hat OpenShift.

IBM Cloud Pak foundational services, Platform UI, and IBM Cloud Pak foundational services are dependencies of WebSphere Automation. For more information on IBM Cloud Pak foundational services and its dependencies, see system requirements in the IBM Cloud Pak foundational services documentation.