8 Scaling Services Gatekeeper

This chapter explains how to scale your Oracle Communications Services Gatekeeper implementation up by adding new network tier (NT) and access tier (AT) servers on remote systems.

Understanding Scaling

This section assumes that you have a multi-tier Services Gatekeeper installed and configured and want to add additional processing capability by creating more NT and AT servers on remove systems. You do this by adding additional hardware systems and installing an AT or NT server on each one. You then connect the working Services Gatekeeper administration server to the new servers.

During this process you will install a complete multi-tier implementation of Services Gatekeeper on each system, but you will only start and use the NT or AT server for it.

Adding Remote NT/AT Servers to Services Gatekeeper

This section assumes that you have:

  • Installed a Services Gatekeeper implementation on one system, and will use that Services Gatekeeper administration server to manage the new AT and NT servers.

  • Created a list of the customizations you made to the system with the administration server. Including any custom configuration files or JAR files.

  • Prepared an additional system ready to receive the new AT/NT server by adding the same operating system to it. Each system must have a unique IP address.

To add an additional NT or AT server:

  1. Log on to the system to receive the new NT or AT server.

  2. Follow the instructions in ”"Installing Services Gatekeeper" to install the JDK and a multi-tier implementation of Services Gatekeeper on the system.

    Note:

    You must install the same version of Services Gatekeeper on every system.

  3. Follow the instructions in "Configuring the Services Gatekeeper Domain" to create and configure a domain for the NT or AT server.

  4. Add any customized property files or JAR files from the system with the administration server to the new system with the AT or NT server.

  5. Log on to the system running your database, and have your database administrator back up the database schema.

  6. Log on to the system running your administration server,.

  7. Make a backup of the domains.

  8. Start the Administration Console.

  9. Create a new AT and NT node by navigating to Environment, then Machines and creating new machines for each NT or AT.

  10. Create a new NT or AT server by navigating to Environment, then Servers and creating a new server.

  11. Add the new NT or AT node to the cluster by navigating to Environment, then Clusters and adding the new AT or NT.

  12. Create a new JMS server for the new AT or NT by navigating to Services, then Messaging ,then JMS Servers, and creating a new JMS server.

  13. Navigate to Services, then Messaging ,then JMS Modules, and then:

    1. Click WLNGEDRResource, then the Subdeployments tab.

    2. Click WLNG_JMS_CLUSTER and make sure that JMSServer-NTx is selected as the target.

  14. Navigate to Environment, then Servers, then servername, then Protocols, then Channels and create a new channel for each AT or NT server.

  15. Restart the administration server and all of the AT and NT servers on all systems.

  16. Test your services to be sure the administration server communicates with the new AT or NT server.

Automating the Process of Scaling Services Gatekeeper

If you will configure a lot of Services Gatekeeper implementations, or add a lot of NT or AT servers to scale a Services Gatekeeper implementation, you may find it easier to automate the process. See: