7 Completing Post-Installation

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

Complete Post-Install Tasks

You may not need to do all of the following tasks depending on your installation requirements.

Create a Portal Manager Account

If you have installed the optional reporting support described in Chapter 5, "Installing Services Gatekeeper Reporting and Portal Support," use the ManagementUserMBean MBean to create a Services Gatekeeper user with the following attributes:

• Type: 1 (Partner Relationship Manager operator)

• User Level: 666 (read/write access)

See "Managing Management Users and Management User Groups" in Oracle Services Gatekeeper System Administrator's Guide, a separate document in this set, for details.

Create JMS Servers for Any Additional NT Servers

If you have added any Network Tier (NT) servers to those provided by the domain template you used, you must edit each NT server's configuration to add support for the EDR Service. Each server in the NT 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 NT server (this prevents a null pointer error in initializing the console). For more information on using the console, see Oracle Services Gatekeeper System Administrator's Guide, a separate document in this set.

To create additional NT servers:

1. Start Services Gatekeeper on the administrative server.

   In a command prompt window, go to the Services_Gatekeeper_Home/domain/bin directory where Services_Gatekeeper_Home is the home directory of your Services Gatekeeper installation. In the default installation, this would be Services_Gatekeeper_Home/user_projects/domains/ocsg-domain/bin.

   Run the startWebLogic.sh script.

   The administrative server starts.

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 and 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.

   Note:

   You can also log in to the NT server, and run the startManagedWebLogic.sh script from there.

   If you are running Services Gatekeeper on Solaris, you will need to add the following line to startManagedWebLogic.sh:

   JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.ThreadPoolSize=100 -Dweblogic.ThreadPoolPercentSocketReaders=50"

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:

   http://hostname:port/console

   where hostname is the hostname of the administrative server and port is the administration port assigned during domain configuration.

6. Log in using credentials for an administrative user.

7. Before you can make any changes using the Administration 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 then Services then Messaging then JMS Servers then 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 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.1/patch_others/ob, where Services_Gatekeeper_Home is the installation directory for Services Gatekeeper.

4. Unzip the ob_patch.zip 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:

   ob_patch.sh 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.

(Optional) Add a Custom Password Validator

Using features available through WebLogic Server, you can create and configure a Password Validation Provider. This allows 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 the discussion on configuring authentication providers in Oracle Fusion Middleware Securing Oracle WebLogic Server at:

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13707/atn.htm

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

(Optional) Adding Java Cryptography Extensions

Services Gatekeeper does not require JCE features to run, but you can install them if you wish. For more information, see the discussion on using the nCipher JCE Provider with WebLogic Server in Oracle Fusion Middleware Securing Oracle WebLogic Server at:

http://download.oracle.com/docs/cd/E12839_01/web.1111/e13707/ssl.htm

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 Oracle Communications Services Gatekeeper System Administrator's Guide and Accounts and SLAs Guide. The following list gives a general outline of the initial tasks you must perform:

• Create administrative user accounts

• Configure Services Gatekeeper Container Services

• Configure communication services

• Configure connections with OSA/Parlay gateways, as necessary

• Set up and configure Web Services Security and OAM (JMX) Security

• Configure the Partner Relationship Management interfaces, as necessary

• Configure geo-redundancy, if necessary

• Create service provider and application accounts

• Create service provider and application SLAs

• Create network SLAs

For Further Information

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

http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html