# Installation Guide

# 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. These include

- Complete Post-Install Tasks
- Configure Oracle Communications Services Gatekeeper

## 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 Oracle Communications Services Gatekeeper installation so that you can use the Management 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 the System Administration Guide, a separate document in this set. The following is an overview only:

1. Start Oracle Communications Services Gatekeeper on the Administrative Server.

In a command prompt window, go to the domain\bin directory. In the default installation, this would be`<beahome>\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.

Note: | You can also log into the NT server, and run the `startManagedWebLogic` script from there.

1. Watch the command prompt window as the NT server loads. Wait until the prompt indicates that the server is in state RUNNING.
2. 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 Administrative Server and port is the ListenAddress assigned during Domain Configuration. The default value is 7001.

3. Login using your login credentials.

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

4. 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 Management 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

Oracle Communications Services Gatekeeper does not require the JCE files, but you can install them if you wish to use JCE providers. For more information, please see the section about the nCipher JCE Provider in Oracle WebLogic Server Securing WebLogic Server at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/.

### Set Up Oracle Service Bus to Run with Oracle Communications Services Gatekeeper

If your installation is using the SOA Facade with Oracle Service Bus, you will need to take a number of steps to integrate Oracle Communications Services Gatekeeper with Oracle Service Bus. See Installation of SOA Facades for more information.

### Add a Custom Password Validator

Using features available through Oracle. WebLogic Server 10.3, you can create and configure a Password Validation Provider. This will allow you to enforce rules concerning the composition of passwords used with Oracle Communications 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 Securing WebLogic Server, at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/secmanage/atn.html#wp1212863. You will need to use WLST to create and configure your Password Validation Provider.

## Configure Oracle Communications Services Gatekeeper

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

- Create administrative user accounts
- Configure Oracle Communications 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
- Configure and deploy any backwards-compatible (Access, deprecated container services, etc.) modules as necessary. For more information, see the Retired container services section of the “Deployment model” chapter of the System Administrator’s Guide, a separate document in this set.

## For Further Information

To learn more about installing WebLogic Server products in general, and about the installer program in particular in regard to WebLogic Server, see the WLS Installation Guide.