27 Scaling Procedures for an Enterprise Deployment
The scaling procedures for an enterprise deployment include scale out and scale in. During a scale-out operation, you add Managed Servers to new nodes. You can remove these Managed Servers by performing a scale in operation.
This chapter includes the following topics:
- Scaling Out the Topology
When you scale out the topology, you add new Managed Servers to new nodes. - Scaling In the Topology
When you scale in the topology, you remove new Managed Servers or instances or both from your running system.
Scaling Out the Topology
When you scale out the topology, you add new Managed Servers to new nodes.
This section describes the procedures to scale out the Identity Management topology.
Parent topic: Scaling Procedures for an Enterprise Deployment
Scaling Out Oracle Unified Directory
This section lists the prerequisites for scaling out Oracle Unified Directory, explains the procedure, and describes the steps to verify the scale-out process.
- Prerequisites for Scaling Out
- Scaling Out by Adding a New Replicated Instance
- Verifying the Scale Out
Parent topic: Scaling Out the Topology
Prerequisites for Scaling Out
Before you perform a scale out of the OUD topology, ensure that you meet the following requirements:
- As the starting point, you have at least one OUD server instance running. This is the primary instance.
- A Kubernetes worker node is available with sufficient capacity to host the new pod.
Parent topic: Scaling Out Oracle Unified Directory
Scaling Out by Adding a New Replicated Instance
Parent topic: Scaling Out Oracle Unified Directory
Verifying the Scale Out
After scaling out and starting the server, proceed with the following verifications:
Parent topic: Scaling Out Oracle Unified Directory
Scaling Out a WebLogic Domain
This section describes the procedures to scale out a WebLogic domain such as Oracle Access Manager.
- Prerequisites for Scaling Out
- Scaling Out a Domain
- Scaling Out the Cluster Using the Sample Script
- Verifying the Scale Out
Parent topic: Scaling Out the Topology
Prerequisites for Scaling Out
Before you perform a scale out of the topology, you must ensure that you meet the following requirements:
-
The starting point is a cluster with Managed Servers already running.
- A Kubernetes worker node is available with sufficient capacity to host the new pod.
-
It is assumed that the cluster syntax is used for all internal RMI invocations, JMS adapter, and so on.
- You are currently not running the maximum number of servers you defined when at the time of creating the domain.
Parent topic: Scaling Out a WebLogic Domain
Scaling Out a Domain
kubectl patch cluster -n <NAMESPACE> <DOMAIN_NAME>-<CLUSTER_NAME> --type=merge -p '{"spec":{"replicas":<NO OF REPLICAS>}}'
kubectl patch cluster -n oamns accesdomain-oam-cluster --type=merge -p '{"spec":{"replicas":3}}'
Parent topic: Scaling Out a WebLogic Domain
Scaling Out the Cluster Using the Sample Script
fmw-kubernetes/<PRODUCT>/kubernetes/domain-lifecycle
./scaleCluster.sh -d <DOMAIN_NAME> -n <NAMESPACE> -c <CLUSTER_NAME> -r <REPLICAS>
Parent topic: Scaling Out a WebLogic Domain
Verifying the Scale Out
Parent topic: Scaling Out a WebLogic Domain
Scaling In the Topology
When you scale in the topology, you remove new Managed Servers or instances or both from your running system.
Parent topic: Scaling Procedures for an Enterprise Deployment
Scaling In Oracle Unified Directory
This section lists the prerequisites for scaling in Oracle Unified Directory, explains the procedure, and describes the steps to verify the scale-in process.
Parent topic: Scaling In the Topology
Prerequisites for Scaling In
Before you perform a scale in of the OUD topology, ensure that you have at least two OUD server instance running.
Parent topic: Scaling In Oracle Unified Directory
Scaling In by Removing a Replicated Instance
Parent topic: Scaling In Oracle Unified Directory
Verifying the Scale In
After scaling in and starting the server, proceed with the following verifications:
Parent topic: Scaling In Oracle Unified Directory
Scaling In a WebLogic Domain
This section lists the prerequisites for scaling in a WebLogic domain such as Oracle Access Manager and Oracle Identity Governance, and explains the procedure to scale in the domain.
- Prerequisites for Scaling In
- Scaling In a Domain
- Scaling In the Cluster Using the Sample Script
- Verifying the Scale In
Parent topic: Scaling In the Topology
Prerequisites for Scaling In
Before you perform a scale In of the topology, you must ensure that you meet the following requirements:
- The starting point is a cluster with Managed Servers already running.
- It is assumed that the cluster syntax is used for all internal RMI invocations, JMS adapter, and so on.
Parent topic: Scaling In a WebLogic Domain
Scaling In a Domain
Scaling in the domain involves asking the WebLogic Operator for Kubernetes to stop extra pods (Managed Servers). You can use one of the following ways to scale in the domain:
domain.yaml
/domain_oim_soa.yaml
file- Locate the entry for the cluster you want to scale in. Decrease the value of the parameter replicas to the desired number of servers you want to start. For example: replicas: 1
- Save the file and apply the changes using the following
command:
kubectl apply -f domain.yaml
- Use the following
command:
kubectl edit domain <domain_name> -n <namespace>
For example:kubectl edit domain accessdomain -n oamns
- Locate the entry for the cluster you want to scale in. Decrease the value of the parameter replicas to the desired number of servers you want to start. For example: replicas: 1
- Save the file. The operator will automatically start the required number of servers.
Parent topic: Scaling In a WebLogic Domain
Scaling In the Cluster Using the Sample Script
fmw-kubernetes/<PRODUCT>/kubernetes/domain-lifecycle
./scaleCluster.sh -d <DOMAIN_NAME> -n <NAMESPACE> -c <CLUSTER_NAME> -r <REPLICAS>
Parent topic: Scaling In a WebLogic Domain
Verifying the Scale In
After scaling in and starting the server, proceed with the following verifications:
Parent topic: Scaling In a WebLogic Domain