Skip Headers
Oracle® Communications Services Gatekeeper Installation Guide
Release 5.0

Part Number E16615-02
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
View PDF

6 Completing Post-Installation

This chapter describes the tasks you may have to complete after installing Oracle Communications Services Gatekeeper and configuring the WebLogic Server domain for use with it.

Complete Post-Install Tasks

You may not need to do all of the following tasks depending on the type of installation with which you are working.

Create JMS Servers for Any Additional NT Servers

If you have added any Network Tier servers to the initial two provided by the domain template, you must edit the configuration to add support for the EDR Service. Each server in the Network Tier requires its own JMS server in order for the EDR Service to work correctly.

For the following task, you must start the Administrative Server in your Services Gatekeeper installation so that you can use the Administration Console to make the necessary adjustments. Unless you are setting up an all in one domain, you will also need to start at least one Network Tier server (this prevents a null pointer error in initializing the Console). For more information on using the Console, please see System Administrator's Guide, a separate document in this set. The following is an overview only.

  1. Start Services Gatekeeper on the Administrative Server.

    In a command prompt window, go to the domain/bin directory. In the default installation, this would be Services_Gatekeeper_Home/user_projects/domains/ocsg-domain/bin.

    Run the startWebLogic script.

    The Administrative Server will load.

  2. Watch the command prompt window as the server loads. Wait until the prompt indicates that the server is in state RUNNING.

  3. Start a Network Tier server.

    In a separate command prompt window, go to the domain/bin directory. See step 1 above. Enter the following:

    startManagedWebLogic networknode0-0 t3://adminhost:7001

    replacing the first parameter with the name of the NT server and the second with the URL of the Administration Server.


    You can also log in to the NT server, and run the startManagedWebLogic script from there.
  4. Watch the command prompt window as the NT server loads. Wait until the prompt indicates that the server is in state RUNNING.

  5. Once both servers are in state RUNNING, bring up the Administrative Console.

    In your browser, enter the following address:


    where hostname is the hostname of the Administrative Server and port is the ListenAddress assigned during domain configuration.

  6. Log in using your login credentials.

    If this is the first time you have logged in, you should use username: weblogic and a password that you create. There are instructions in the System Administration Guide on changing these values once your system is fully configured.

  7. Before you can make any changes using the Console, you must click Lock & Edit in the Change Center on the left side of the window.

(In the example below, assume that the additional server WLNG_NT3 was created.)

In the Administration Console:

  1. Select Home > Services > Messaging >JMS Servers > New.

  2. In the Name text box, enter the name of the JMS Server. In our example, this would be JMSServer-NT3.

  3. In the Target dropdown menu, select the appropriate server. In our example, this would be WLNG_NT3.

  4. Click Finish.

  5. Click Activate Changes.

Install Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files, if desired

Services Gatekeeper does not require the JCE files, but you can install them if you wish to use JCE providers. For more information, see “Using the nCipher JCE Provider with WebLogic Server” in Oracle Fusion Middleware Securing Oracle WebLogic Server at:

Install Orbacus

The Orbacus ORB is not provided in the standard Services Gatekeeper installation.

The communication services that rely on Orbacus do not function without the Orbacus ORB, so you need to perform a set of tasks to use these communication services. The communications services that need the Orbacus ORB are:

  • Parlay X 3.0 Third Party Call/Parlay MultiParty Call Control

  • Parlay X 3.0 Call Notification/Parlay MultiParty Call Control

  • Parlay X 3.0 Audio Call/Parlay MultiParty Call Control and Call User Interaction

To install Orbacus ORB:

  1. Get Orbacus 4.3.2 from Progress Software.

  2. Copy the following JAR files to a temporary directory (Orbacus_temp):

    • OB.jar

    • OBBiDir.jar

    • OBEvent.jar

    • OBNaming.jar

    • OBUtil.jar

  3. Change directory to Services_Gatekeeper_Home/ocsg_5.0/patch_others/ob, where Services_Gatekeeper_Home is the installation directory for Services Gatekeeper.

  4. Unzip the file to a temporary directory (Ob_patch).

  5. Change directory to Ob_patch.

  6. If you are using Unix or Linux, run the install script: Orbacus_temp Services_Gatekeeper_home

    If you are using Windows, run the install script:

    ob_patch.bat Orbacus_temp Services_Gatekeeper_home

    Replace Services_Gatekeeper_Home with the installation directory for Services Gatekeeper.

Add a Custom Password Validator

Using features available through Oracle WebLogic Server, you can create and configure a Password Validation Provider. This will allow you to enforce rules concerning the composition of passwords used with Services Gatekeeper. In general, the rules include:

  • Whether the password may contain the user's name, or the reverse of that name

  • A minimum or maximum password length (composition rules may specify both a minimum and maximum length)

  • Whether and how many of the following characters must be in the password:

    • Numeric characters

    • Lowercase alphabetic characters

    • Uppercase alphabetic characters

    • Non-alphanumeric characters (e.g., parentheses or asterisks)

For more information, see “Configuring Authentication Providers” in Oracle Fusion Middleware Securing Oracle WebLogic Server at:

You will need to use WLST to create and configure your Password Validation Provider.

Configure Services Gatekeeper

After you have installed the software, configured the domain, and completed any necessary post-installation steps, you can proceed to configuring Services Gatekeeper itself. The specifics for doing these tasks are presented in the System Administrator's Guide and Accounts and SLAs Guide. The following list gives a general outline of the initial tasks you must perform:

For Further Information

To learn more about installing WebLogic Server products in general, see the WebLogic documentation set page at: