# Installation Guide

# Configuring the Domain for Oracle Communications Services Gatekeeper

This chapter describes how to use the Oracle Communications Services Gatekeeper domain configuration tools to set up Oracle WebLogic Server for use with Oracle Communications Services Gatekeeper. It covers:

- Domain Overview
- The Graphical Mode Configuration Wizard
- The Console Configuration Wizard
- The Oracle WebLogic Scripting Tool scripts

Before you run the domain tools, you should have:

- Read Task Overview for an overview of the entire process
- Installed the database, as covered in Installing the Database,and the software, as covered in Installing Oracle Communications Services Gatekeeper

## Domain Overview

In order to run Oracle Communications Services Gatekeeper, its container, Oracle WebLogic Server, must be given basic information about the various parts of the system. This is called configuring the domain. A domain is the basic administrative unit in Oracle WebLogic Server. It consists of an Administration Server and, usually, one or more Managed Servers, which may be associated into clusters.

Figure 7-1 Oracle WebLogic Domains

The Administration Server provides a central point for managing the domain and providing access to the Oracle WebLogic Server administration tools.

Note: | A single Oracle WebLogic Server instance can function as both the Administration Server and a Managed Server, depending on the needs of the installation. For example, developers creating communication service extensions using the Platform Development Studio commonly might run both the Administration Server and Managed Servers on a single machine.

Managed Servers are often grouped together into clusters. Clusters are groups of server instances that work together to provide scalability and high availability. Clusters improve performance and provide failover should a server instance become unavailable. The servers within a cluster can run on the same machine, or they can reside on different machines. To the client, a cluster appears as a single Oracle WebLogic Server instance.

Figure 7-2 Initial server instances added to clusters

Managed Servers, or the clusters into which they are linked, host application components - in this case, the communication services - and resources, which are also deployed and managed as part of the domain. In Figure 7-3 below, the applications (`wlng_nt_<communication-service-name#version>` and `wlng_at_<communication-service-name#version>`) are assigned to the two clusters (`WLNG_NT_Cluster` and `WLNG_AT_Cluster`). But each Network Tier server must have its own JMS resources, so they are shown per server.

Figure 7-3 Managed servers/clusters host applications and resources

Each server instance is also assigned to a Machine, a logical representation of actual hardware. The Machine representation is used by the Administration Server to start and stop remote servers using the Node Manager. Multiple server instances can run in a single Machine.

Figure 7-4 Servers are assigned to Machines

For more information on Oracle WebLogic Server domains, see Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html.

Note: | All servers must have their domains configured. You can either use one of the methods below to manually configure each server in your installation, or you can configure the domain on your Administration server and then use the pack and unpack commands provided by WLS to package the configuration data for copying to all the other servers. For more information on `pack` and`unpack`, see Oracle WebLogic Server Creating Templates and Domains Using the pack and unpack Commands at http://download.oracle.com/docs/cd/E12840_01/common/docs103/pack/. The scripts themselves are located in the `<wlsserver>/common/bin` directory. In the default installation, this would be `<beahome>\wlserver_10.3\common\bin.`

## The Graphical Mode Configuration Wizard

Use the following instructions if you wish to use the GUI-based Configuration Wizard to configure Oracle WebLogic Server for Oracle Communications Services Gatekeeper.

Note: | If you want to use the GUI-based Wizard, the console attached to the machine on which you are configuring the domain must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX/Linux systems do. If you attempt to start the configuration program in graphical mode on a system that cannot support a graphical display, the configuration program automatically starts console-mode installation.

### Launch the GUI Configuration Wizard - Windows

You can start the Configuration Wizard in graphical mode from either the Windows Start menu or from the command line.

- To start the GUI Configuration Wizard from the Windows Start menu, choose the Configuration Wizard option from the BEA program group in the Windows Start Menu:

`Start->Programs->Oracle Communications Services Gatekeeper<ver#>->OCSG 4.1->Tools->Configuration Wizard`

Note: | If you have used the GUI-based installer, and the Run Quickstart box is checked in the Installation Complete window, the Quickstart window opens automatically. Simply click Start Domain Configuration Wizard to launch the Wizard.

- To start the GUI Configuration Wizard from the command line:

1. Log in to the target system
2. Open a command prompt window
3. Go to the WebLogic Server `\common\bin` subdirectory. For example:

    cd c:\<beahome_dir>\wlserver_10.3\common\bin

4. At the prompt, type `config` and `Enter`
5. The Configuration Wizard starts in graphical mode

Note: | You can also use Explorer to find the `config.cmd` file in c:\<beahome_dir>\wlserver_10.3\common\bin, and simply double-click it.

### Launch the GUI Configuration Wizard - UNIX/Linux

To start the GUI Configuration Wizard:

1. Log in to the target system
2. Open a command shell window
3. Go to the `/common/bin` subdirectory. For example:

    cd c:/<beahome_dir>/wlserver_10.3/common/bin

4. Invoke the following script:

    sh config.sh

Note: | If you are configuring an HP-UX installation, you must modify the `config.sh` script before running it.

1. Open `config.sh` in a text editor and scroll down to the following section:

    "${JAVA_HOME}/bin/java" -Dprod.props.file=${WL_HOME}/.product.properties -Dpython.cachedir=/tmp/cachedir ${MEM_ARGS} com.bea.plateng.wizard.WizardController ${ARGUMENTS}

2. Add the`-Djava.security.egd` flag, so that the section reads:

    '${JAVA_HOME}/bin/java' -Djava.security.egd=/dev/random -Dprod.props.file=${WL_HOME}/.product.properties -Dpython.cachedir=/tmp/cachedir ${MEM_ARGS}com.bea.plateng.wizard.WizardController ${ARGUMENTS}

5. The Configuration Wizard starts in graphical mode

### Respond to the Prompts

The GUI Configuration Wizard prompts you to enter specific information about your system and configuration. For instructions on responding to the prompts during installation, see the following table

Note: | If you are going to be using any CORBA based functionality that in one way or another connects to a machine other than your own, you should not use the value “localhost” in any of your configuration choices.
In this window... | Perform the following action...
--- | ---
Welcome | Make sure Create WebLogic domain is selected. Click Next to proceed with the installation. You may cancel the installation at any time by clicking Exit and you may go back to a previous window by clicking Previous.
Select a Configuration Template | There are five standard domain templates that have already been constructed. Click on the plus next to the Oracle folder to display your options. Select the appropriate template depending on your needs: OCSG Basic HA configuration Creates a basic domain with two servers, each with an AT and an NT instance and a database. This configuration can be expanded later in the process. OCSG Domain with Access and Network Clusters Creates a basic distributed domain, with a two instance Access cluster and a two instance Network cluster. This configuration can be expanded later in the process. OCSG Domain with Access and Network Clusters with Oracle RAC Configuration Creates a basic distributed domain, with a two instance Access cluster and a two instance Network cluster. This configuration can be expanded later in the process. It also creates the additional datasources required for use with an Oracle RAC based installation. Basic Oracle Communications Services Gatekeeper Domain Creates an all-in-one domain, with the Access and Network Tier and the Administration Server all on a single machine. This configuration is common for development machines. OCSG OSB Integration Configuration Creates a domain for integration with Oracle Service Bus, using the SOA Facade. If you are using this template, you need additional special information. Please look in Installation of SOA Facades for this information. After selecting the appropriate template, click OK to continue. When you return to the Select Domain Source window, click Next.
Configure Administrator Username and Password | Specify the username of the main Administrative user. This name is used to boot the Administration Server and connect to it. For setup purposes, this username should be “weblogic”. User names are case sensitive. Do not use commas or any characters in the following comma-separated list: `\t, < >, #, |, &, ?, ( ), { }` Specify the password for the Administrative user. For setup purposes, this password should be “weblogic.” You can change it later. A valid password is a string of at least 8 case-sensitive characters. The password value is encrypted. Re-enter the password. Optionally, enter a login description for this username. Click Next to continue.
Configure Server Startup Mode and JDK | On the left side of the window, select the appropriate startup mode for your installation: Development Mode Production Mode
Note: | If you select Production Mode, you should not enable SSL unless you have a trusted key. For more information on startup modes, see see Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html.
On the right side of the window, you should select the BEA Supplied JDK’s radio button and choose the appropriate JDK. Click Next to continue.
Customize Environment and Services Settings | Select Yes. For more information on the values you might enter in the following windows in the general context of WebLogic Server, see the description on customizing the environment in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html. Click Next to continue.
Configure RDBMS Security Store Database | Leave the “I don’t want to change anything here” radio button selected.
Configure the Administration Server | Change the `Listen address` from `host-admin.bea.com` to the IP number or DNS name of your Administration Server and make any other changes necessary based on your installation. Click Next to continue.
Configure Managed Servers | Use this window to add or change connection information for Managed Servers. Each Managed Server is an instance of WebLogic Server. Some information may already be filled in. Change the `Listen address` of each of your servers, based on your installation values. You can add Managed Server instances at this time. (You can also do this using the Management Console at any time.).
Note: | The `Listen address` and `Listen port` per server combination must be unique. The values for the Listen address can include alphanumeric characters, dots [.], and dashes [-] only.
Click Next to continue.
Configure Clusters This window does not appear if you selected Create Oracle Communications Services Gatekeeper Basic Domain | Use this window to change connection information for clusters. Clusters are logical representations that for reasons of scalability and high availability allow multiple Managed Servers to act as if they were a single host. The `wlng-access-network-domain.jar` templates create two clusters, with each cluster containing two Managed Server instances.Change the `Cluster address` to reflect the addresses and ports you set in the previous window. Values should be comma-delimited, with no spaces. You may also change the `Multicast address` if your installation requires it. Click Next to continue.
Assign Servers to Clusters This window does not appear if you selected Create Oracle Communications Services Gatekeeper Basic Domain | Use this window to add any additional Managed Servers you listed in the Configure Managed Servers window to clusters configured in the Configure Clusters window. Select the appropriate cluster in the right pane, the appropriate Managed Server in the left pane, and assign them to each other by clicking the right arrow button. Click Next to continue.
Configure Machines/Configure Unix Machines | Use this window to add or change information about Machines. In the context of WebLogic Server, a Machine is the logical representation of the system that hosts one or more WebLogic Server instances, for the purposes of starting and stopping remote servers using the Node Manager. In a domain, machine definitions identify a particular, physical piece of hardware and are used to associate a computer with the Managed Servers it hosts. For more information about the various fields, see the section on how to configure machines in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html. Click Next to continue.
Assign Servers to Machines This window does not appear if you selected Create Oracle Communications Services Gatekeeper Basic Domain | Use this window to assign Servers (either Administration or Managed) to their appropriate Machines, if necessary. Select the appropriate Machine in the right pane and the server(s) in the left pane and assign them to each other by clicking the right arrow button. Click Next to continue.
Configure JDBC Datasource This window appears if you are installing a non-RAC based Gatekeeper. | Use this window to make adjustments to the Oracle Communications Services Gatekeeper JDBC datasources if you are using a non-RAC database. A JDBC datasource contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a datasource on the JNDI tree, and then request a connection. In a non-RAC configuration, you must configure two datasources using the two tabs in this window.
NON-RAC TAB ONE: wlng.datasource | Use the first tab to make adjustments in the datasource for the transactional datasource. Typically, fields you may need to edit include: Database type: The default is Oracle Driver: The driver appropriate to the database type Supports global transactions should be checked, and either Two phase commit (Oracle) or Emulate two phase commit (MySQL) should be selected DBMS name: The name of the database you created in Installing the Database DBMS host: Where the database is located DBMS port: The port for contacting the database. User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database Password: The Oracle Communications Services Gatekeeper password you created when you installed the database
Note: | Do not change the Name or JNDI name fields.
Click the wlng.localTX.datasource tab to continue
NON-RAC TAB TWO wlng.localTX.datasource | Use this second tab to make adjustments in the datasource for local transactions. You will need to set the values as in wlng.datasource, with the following exceptions: Driver: If you are using Oracle, you should select the non-XA driver for this datasource Supports global transactions should not be checked, for either Oracle and MySQL. Click Next to continue.
Configure JDBC Datasource This window appears if you are installing a RAC based Gatekeeper. | Use this window to make adjustments to the Oracle Communications Services Gatekeeper JDBC datasources if you are using a RAC database. A JDBC datasource contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a datasource on the JNDI tree, and then request a connection. In a RAC-based configuration, you must configure four datasources (two of each type) using the four tabs in this window.
RAC TAB ONE: wlng.localTX.datasource-1 | Use the first tab to make adjustments in the first datasource for local transactions. Typically, fields you may need to edit include: Supports global transactions should not be checked. DBMS name: The name of the first database instance you created in Installing the Database DBMS host: Where the first database instance is located DBMS port: The port for contacting the first database instance. User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database. Password: The Oracle Communications Services Gatekeeper password you created when you installed the database. You must confirm the password
Note: | Do not change the Name or JNDI name fields.
Click the wlng.localTX.datasource - 2 tab to continue
RAC TAB TWO: wlng.localTX.datasource-2 | Use this tab to make adjustments in the second datasource for local transactions. You should enter the same values as in wlng.localTX.datasource-1 with the following exceptions: DBMS name: The name of the second database instance you created in Installing the Database DBMS host: Where the second database instance is located Click the wlng.datasource - 1 tab to continue
RAC TAB THREE wlng.datasource - 1 | Use this tab to make adjustments in the first transactional datasource. Typically, fields you may need to edit include: Supports global transactions should be checked, with Two phase commit DBMS name: The name of the first database you created in Installing the Database. This is the same name you used in wlng.localTX.datasource-1. DBMS host: Where the first database instance is located. This is the same value you used in wlng.localTX.datasource-1 DBMS port: The port for contacting the first database instance. This is the same value you used in wlng.localTX.datasource-1 User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database Password: The Oracle Communications Services Gatekeeper password you created when you installed the database. You must confirm the password.
Note: | Do not change the Name or JNDI name fields.
Click the wlng.datasource - 2 tab to continue
RAC TAB FOUR wlng.datasource - 2 | Use this tab to make adjustments in the second transactional datasource. You should enter the same values as in wlng.datasource-1 with the following exceptions: DBMS name: The name of the second database instance you created in Installing the Database. This is the same name you used in wlng.localTX.datasource-2. DBMS host: Where the second database instance is located. This is the same value you used in wlng.localTX.datasource-2 Click Next to continue
Review Oracle Communications Services Gatekeeper Domain | Use this window to confirm that your domain is configured as it needs to be. The Summary View dropdown menu provides multiple views of the configuration. Clicking on an item in the Summary view window brings up information associated with that item. Click Next to continue
Create Oracle Communications Services Gatekeeper Domain | Use this window to change the domain name or the location in which the domain’s configuration files will be stored. Usually the default values are acceptable. Make sure the installing user has write permission for this directory. Click Create to generate your domain
Creating Domain | A status bar indicates the progress of domain creation. When Domain Created Successfully! appears, click Done to exit the Configuration Wizard.

## The Console Configuration Wizard

Use the following instructions if you wish to use the Console-based Configuration Wizard to configure Oracle WebLogic Server for Oracle Communications Services Gatekeeper. Specific instructions on launching the Wizard by platform are found after the next section.

### Using the Console Configuration Wizard

The Console Configuration Wizard is designed to mimic as closely as possible the choices available in the GUI version, but in a completely text-based form. The following images give you a sense of the way the Console Screen displays certain types of workflow choices.

Figure 7-5 Select Options

In Figure 7-5 above, the top of the current screen is marked by the Oracle Communications Services Gatekeeper Wizard banner. The top part of the screen displays the set of configuration parameters that can be set - in this case, configuration information for Managed Servers. The center of the screen indicates the range of options - in this case, Add a server, Modify a server, or Delete a server. The bottom part of the screen prompts for the user input that is available in this screen - in this case

    Enter option number to select or [Exit][Previous][Next]>

Here the user can either enter an option (indicated by number) or choose to use one of the standard navigation commands. In this case, option `1`, Add a server, has been chosen. The entry is confirmed by pressing the Enter key:

Figure 7-6 Add a Managed Server

In Figure 7-6, the bottom of the screen displays the user input prompt:

    Enter name for a new OR [Exit][Previous][Next]>

The name for the new Managed Server to be added, WLNG_NT3, has been filled in. Again the input is confirmed by pressing the Enter key.

Figure 7-7 Finish work on the selected item

In Figure 7-7 the new Managed Server, WLNG_NT3, has been added. Note the right arrow (`->`) next to the new Server’s name. This indicates that this is the selected item, and that any options chosen will affect that item. To finish with this server and select another item in the list, enter `5 - Done` and the Enter key.

Figure 7-8 Indicate your next configuration task

In Figure 7-8 the center section again presents you with work options. In this case, additional modifications need to be done. The user enters `2` for Modify and then Enter to confirm.

Figure 7-9 Select the configuration to modify

In Figure 7-9, the user input prompt asks which item needs modification. The row number of the Managed Server WLNG_NT1 is chosen. Once Enter is pressed, WLNG_NT1 will be the selected item.

There are a number of different options throughout the Wizard process, but in general they all follow this same pattern: the top of the screen indicates what is being configured; the center of the screen indicates the range of options; and the bottom of the screen prompts for user input.

### Launch the Console Configuration Wizard - Windows

To start the Console Configuration Wizard:

1. Log in to the target system
2. Open a command prompt window
3. Go to the `\common\bin` subdirectory. For example:

    cd c:\<beahome_dir>\wlserver_10.3\common\bin

4. At the prompt, type `config` -mode=console and `Enter`
5. The Configuration Wizard starts in console mode

### Launch the Console Configuration Wizard - UNIX/Linux

To start the Console Configuration Wizard:

1. Log in to the target system
2. Open a command shell window
3. Go to the `/common/bin` subdirectory. For example:

    cd c:/<beahome_dir>/wlserver_10.3/common/bin

4. Invoke the following script:

    sh config.sh

Note: | If you are configuring an HP-UX installation, you must modify the `config.sh` script before running it.

1. Open`config.sh` in a text editor and scroll down to the following section:

    "${JAVA_HOME}/bin/java" -Dprod.props.file=${WL_HOME}/.product.properties -Dpython.cachedir=/tmp/cachedir ${MEM_ARGS} com.bea.plateng.wizard.WizardController ${ARGUMENTS}

2. Add the`-Djava.security.egd` flag, so that the section reads:

    '${JAVA_HOME}/bin/java' -Djava.security.egd=/dev/random -Dprod.props.file=${WL_HOME}/.product.properties -Dpython.cachedir=/tmp/cachedir ${MEM_ARGS}com.bea.plateng.wizard.WizardController ${ARGUMENTS}

5. The Configuration Wizard starts in console mode

### Respond to the Prompts

To create your domain, respond to the prompts in each section by entering the number associated with your choice, pressing Enter, or typing next (or n) to accept the current selection. For instructions on responding to the prompts during installation, see the following table.

Note: | If you are going to be using any CORBA based functionality that in one way or another connects to a machine other than your own, you should not use the value “localhost” in any of your configuration choices.

The right arrow (`->`) indicates the value currently selected. To quit the Configuration Wizard, enter Exit in response to any prompt. To review or change your selection, enter Previous at the prompt.

Note: | Instead of typing complete words when you want to enter [Exit], [Previous], and [Next], you can use the following one-letter shortcuts: x, p, and n, respectively.

On this screen... | Perform the following action...
--- | ---
Welcome | Select `1`, Create Oracle Communications Services Gatekeeper Domain. Type `n` to continue.
Select a Domain Template | There are five standard domain templates included with the console version of the Oracle Communications Services Gatekeeper Configuration Wizard. Select the number of the template you wish to use: OCSG Basic HA configuration 10.3.0.0 Creates a domain with two servers, each with an AT and an NT instance and a database. Replication of the database must be set up separately. This configuration can be expanded later in the process OCSG Domain with Access and Network Clusters 10.3.0.0 Creates a basic distributed domain, with a two instance Access cluster and a two instance Network cluster. This configuration can be expanded later in the process. OCSG Domain with Access and Network Clusters with Oracle RAC Configuration 10.3.0.0 Creates a basic distributed domain, with a two instance Access cluster and a two instance Network cluster. This configuration can be expanded later in the process.It also creates the additional datasources required for use with an Oracle RAC based installation Basic Oracle Communications Services Gatekeeper Domain 10.3.0.0 Creates an all-in-one domain, with Access and Network Tier and Administration on a single machine. This configuration is common for development machines. OCSG OSB Integration Configuration Creates a domain for integration with Oracle Service Bus, using the SOA Facade. If you are using this template, you need additional special information. Please look in Installation of SOA Facades for this information.
Note: | Option 5 is on a separate console screen. If you wish to use it, use the <Down> option shown at the bottom of the first screen.
Configure Administrator Username and Password | Specify the username of the main Administrative user. This name is used to boot the Administration Server and connect to it. For setup purposes, you should use “weblogic”. User names are case sensitive. Do not use commas or any characters in the following comma-separated list: `\t, < >, #, |, &, ?, ( ), { }` Specify the password for the Administrative user. For setup purposes, you should use “weblogic”. You can change it later. A valid password is a string of at least 8 case-sensitive characters. The password value is encrypted. Re-enter the password. Optionally, enter a login description for this username. Type `n` to continue.
Domain Mode Configuration | Select the number for the appropriate mode configuration for this domain. 1 -Development Mode 2 - Production Mode
Note: | If you select Production Mode, you should not enable SSL unless you have a trusted key. For more information on startup modes, see see Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html.
Type `n` to continue.
Java SDK Selection | Select the appropriate SDK for your installation. Type `n` to continue.
Choose Configuration Option | Select `1`, Yes. For more information on the values you might enter in the following screens in the general context of WebLogic Server, see the description on customizing the environment in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html. Type `n` to continue.
Configure RDBMS Security Store Options | Select 1, I don’t want to change anything here.
Configure the Administration Server | Modify the `Listen address` from `host-admin.bea.com` to the IP address or DNS name of the host in your installation that is to serve as the Administration Server. Make any other changes that are necessary. Type `n` to continue.
Configure Managed Servers This window contains no configuration information if you selected Create Oracle Services Gatekeeper Basic Domain | Use this window to add or change connection information for Managed Servers. Each Managed Server is an instance of WebLogic Server. Some information may already be filled in. Modify the `Listen addresses` of each of your instances. You can add more Managed Server instances you wish to include in your domain here, or you can use the Management Console later.
Note: | The `Listen address` and`Listen port` per server combination must be unique. The values for the Listen address can include alphanumeric characters, dots [.], and dashes [-] only.
Type n to continue.
Configure Clusters This window contains no configuration information if you selected Create Oracle Communications Services Gatekeeper Basic Domain | Use this window to modify connection information for clusters. Clusters are logical representations that for reasons of scalability and high availability allow multiple Managed Servers to act as if they were a single host. The `WLNG Domain with Access and Network Clusters 10.3.0.0` template creates two clusters, with each cluster containing two Managed Server instances. Modify the Cluster address values to reflect the changes you made in the previous screen. Values should be comma-delimited, with no spaces. You can also change the `Multicast adress` if your installation requires it. Type n to continue.
Assign Servers to Clusters This window does not appear if you selected Create Oracle Communications Services Gatekeeper Basic Domain | Use this window to add any additional Managed Servers you created in the Configure Managed Servers window to clusters configured in the Configure Clusters window. Select the number of the appropriate cluster, then indicate which servers you would like to assign by selecting or unselecting them, using the appropriate number. When you have finished making your assignments, hit Enter to accept your choices.
Configure Machines This window contains no configuration information if you selected Create Basic Oracle Communications Services Gatekeeper Domain | Use this window to add or change information about Machines. In the context of WebLogic Server, a Machine is the logical representation of the system that hosts one or more WebLogic Server instances, for the purposes of starting and stopping remote servers using the Node Manager. In a domain, machine definitions identify a particular, physical piece of hardware and are used to associate a computer with the Managed Servers it hosts. For more information about the various fields, see the section on how to configure machines in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html. Type `n` to continue.
Configure Unix Machines This window contains no configuration information if you selected Create Basic Oracle Communications Services Gatekeeper Domain | Use this window to add or change information about UNIX Machines. In the context of WebLogic Server, a Machine is the logical representation of the system that hosts one or more WebLogic Server instances. In a domain, machine definitions identify a particular, physical piece of hardware and are used to associate a computer with the Managed Servers it hosts. The Administration Server and the Node Manager application use this machine definition to start remote servers. For more information about the various fields, see the section on how to configure UNIX machines in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard at http://download.oracle.com/docs/cd/E12840_01/common/docs103/confgwiz/index.html. Type `n` to continue.
Assign Servers to Machines This window does not appear if you selected Create Basic Oracle Communications Services Gatekeeper Domain | Use this window to assign Servers (either Administration or Managed) to their appropriate Machines, if necessary. Select the number of the appropriate Machine, then indicate which servers you would like to choosing to change by selecting or unselecting them, using the appropriate number. When you have finished making your assignments, hit Enter to accept your choices. Type `n` to continue.
Configure JDBC Datasource This window appears if you are installing a non-RAC based Gatekeeper. | Use this window to make adjustments to the Oracle Communications Services Gatekeeper JDBC datasources if you are using a non-RAC database. A JDBC datasource contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a datasource on the JNDI tree, and then request a connection. You must modify the wlng.localTX.datasource, used for local transactions, and the wlng.datasource, used for transactionally-based database access. Type`1` and Enter to Modify, and then the number of the datasource you wish to configure. Type Enter to continue. In a non-RAC configuration, you must configure two datasources using the two options in this window.
wlng.datasource Non-RAC Option 1 | Use this window to make adjustments to the Oracle Communications Services Gatekeeper transactional JDBC data source. A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. To edit the data source, enter `1` - Modify and then `1` -> wlng.datasource. Typically, fields you may need to edit include: 2 - Database type: The default is Oracle 3 - Driver: The driver appropriate to the database type 4 - DBMS name: The name of the database you created in Installing the Database 5 -DBMS host: Where the database is located 6 - DBMS port: The port for contacting the database. 7 - User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database 8 - Password: The Oracle Communications Services Gatekeeper password you created when you installed the database (it will not be echoed on the screen) 9 - Confirm user password: Re-enter the password 12 - Supports global transactions should be selected, and either Two phase commit (Oracle) or Emulate two phase commit (MySQL) should be selected
Note: | Do not change the Name or JNDI name fields.
Type `n` to continue.
wlng.localTX.datasource Non-RAC Option 2 | Use this window to make adjustments in the data source for local transactions. The values should be the same as in wlng.datasource with these differences: 3 - Driver: If you are using Oracle, you should select the non-XA driver for this data source 12 - Supports global transactions: Select 4 - Unspecified Type`n` to continue.
Configure JDBC Datasources This window appears if you are installing a RAC based Oracle Communications Services Gatekeeper. | Use this window to make adjustments to the Oracle Communications Services Gatekeeper JDBC datasources if you are using a RAC database. A JDBC datasource contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a datasource on the JNDI tree, and then request a connection. Use this window to modify each of the necessary datasources in order. The two wlng.localTX.datasources are used for local transactions. The two wlng.datasources are used for transactionally-based database access. Type`1` and Enter to Modify, and then the number of the datasource you wish to configure. Type Enter to continue. In a RAC-based configuration, you must configure four datasources (two of each type) using the four options in this window.
wlng.localTX.datasource-1 RAC Option 1 | Use this window to make adjustments to the first datasource for local transactions. A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. Enter the option you would like to modify by number. Typically, fields you may need to edit include: 4 - DBMS name: The name of the first database instance you created in Installing the Database 5 - DBMS host: Where the first database instance is located 6 - DBMS port: The port for contacting the first database instance. 7 - User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database 8 - Password: The Oracle Communications Services Gatekeeper password you created when you installed the database (it will not be echoed on the screen) 9 - Confirm user password: Re-enter the password 12 - Supports global transactions: Select 4 - Unspecified
Note: | Do not change the Name or JNDI name fields.
When you have completed your edits, type Enter to return to the selection window.
wlng.localTX.datasource-2 RAC Option 2 | Use this window to make adjustments to the second datasource for local transactions. You should enter the same values as in wlng.localTX.datasource-1 with the following exceptions: 4 - DBMS name: The name of the second database instance you created in Installing the Database. 5 - DBMS host: Where the second database instance is located 6 - DBMS port: The port for contacting the second database instance. When you have completed your edits, type Enter to return to the selection window.
wlng.datasource-1 RAC Option 3 | Use this window to make adjustments to the first transactional datasource. A JDBC data source contains a pool of database connections that are created when the data source instance is created—when it is deployed or targeted, or at server startup. Applications look up a data source on the JNDI tree, and then request a connection. Enter the option you would like to modify by number. Typically, fields you may need to edit include: 4 - DBMS name: The name of the first database instance you created in Installing the Database. This should be the same value you entered for wlng.localTX.datasource-1. 5 - DBMS host: Where the first database instance is located. This should be the same value you entered for wlng.localTX.datasource-1. 6 - DBMS port: The port for contacting the first database instance. This should be the same value you entered for wlng.localTX.datasource-1. 7 - User name: The Oracle Communications Services Gatekeeper user name you created when you installed the database 8 - Password: The Oracle Communications Services Gatekeeper password you created when you installed the database (it will not be echoed on the screen) 9 - Confirm user password: Re-enter the password 12 - Supports global transactions and Two phase commit
Note: | Do not change the Name or JNDI name fields.
When you have completed your edits, type Enter to return to the selection window.
wlng.datasource-2 RAC Option 4 | Use this window to make adjustments to the second transactional datasource. You should enter the same values as in wlng.datasource-1 with the following exceptions: 4 - DBMS name: The name of the second database instance you created in Installing the Database. This should be the same value you entered for wlng.localTX.datasource-2. 5 - DBMS host: Where the second database instance is located. This should be the same value you entered for wlng.localTX.datasource-2. 6 - DBMS port: The port for contacting the second database instance. This should be the same value you entered for wlng.localTX.datasource-2. When you have completed your edits, type Enter to return to the selection window. When you have completed making all your changes to datasources, type n to accept the changes you made and move on to the next task.
Select the target domain directory for this domain | Use this window to change the location on the Administration Server in which the domain’s configuration files will be stored. Usually the default value is acceptable. The installing user must have write permission on this directory.
Edit Domain Information | Use this screen to edit the domain’s name. Usually the default value is acceptable.
Creating Domain | A status bar indicates the progress of domain creation. Domain Created Successfully! appears when the process is complete, and the Configuration Wizard exits.

## The Oracle WebLogic Scripting Tool scripts

Use the following instructions if you wish to use scripts and the Oracle WebLogic Scripting Tool to configure Oracle WebLogic Server for Oracle Communications Services Gatekeeper. The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators can use to monitor and manage Oracle WebLogic Server instances and domains. The WLST scripting environment is based on the Java scripting interpreter, Jython. For more general information on WLST, see Oracle WebLogic Server WebLogic Scripting Tool at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/.

Caution: | WLST is a powerful, flexible tool, and has a significant learning curve associated with its effective use. If you do not know how to use WLST and do not wish to spend the time to become familiar with it, consider using one of the Configuration Wizards to set up your domains instead.

### Set Up Your Environment

You must set a number of environment variables for WLST to run properly. To simplify this, the Oracle Communications Services Gatekeeper installer provides shell/cmd scripts that must be run before WLST is invoked. The scripts are found at `<beahome>/wlng400/server/bin.` There are both `setWLSEnv.sh` and `setWLSEnv.cmd` versions available. It is usually enough simply to run the appropriate script, but some shells may require using source, as in:

    source <beahome>/wlserver10.3/server/bin/setWLSEnv.sh

If this still does not work, you may need to change shells. There have been some issues reported with bash, particularly on HPUX machines. If you are having problems with your shell, change to an `sh` shell before running the script.

### Choose from the Provided Scripts

Oracle Communications Services Gatekeeper provides five possible WLST scripts from which you can select. The scripts are found in the `<beahome>/wlserver10.3/common/templates/scripts/wlst/` directory:

- `basic-ocsg-ha.py` uses the domain template `basic-ocsg-ha-domain.jar` for its basic setup. This creates a a domain with two servers, each with an AT and an NT instance and a database. Replication of the database must be set up separately.
- `ocsg-cluster.py` uses the domain template `ocsg-domain.jar` for its basic setup. This creates an all-in-one domain typical of development environments. .
- `access-network-cluster.py` uses the domain template `ocsg-access-network-domain.jar` for its basic setup. This creates a domain with separate Access and Network clusters.
- `access-network-rac-cluster.py` uses the domain template `ocsg-access-network-rac-domain.jar` for its basic setup. This creates a domain with separate Access and Network clusters with the additional datasources that a RAC installation requires.
- `ocsg-osb-integ.py` uses the domain template `ocsg-osb-integ-domain.jar` for its basic setup. This creates a domain for integration of Oracle Communications Services Gatekeeper with Oracle Service Bus.

Note: | If you are configuring an HP-UX installation, you must run the script using the `-Djava.security.egd` flag. For example, you would invoke the `basic-ocsg-ha.py` script by typing:

    java -Djava.security.egd=/dev/random weblogic.WLST  basic-ocsg-ha.py

### Edit the Scripts

- If you are using `wlng-cluster.py` to set up a development machine, you can use the script as is.
- If you are using one of the other four scripts, you must set a few variables found at the top of the script, and, in some situations, edit a few other values.See Multi-cluster standard
- If you are using one of the two other scripts and you also wish to create additional servers, you must make more complex edits. See Multi-cluster with additions
- If you wish to keep any communication services from ever being deployed, you may edit whichever script you are using. See Keep unused communication services from being deployed.

Note: | It is also possible to remove communication services after the initial deployment. See the System Administration Guide for information on accomplishing this.

#### Multi-cluster standard

If you are setting up the standard version of one of the multi-cluster domains, only a few variables need to be set at the top of the script, in the section called Configuration (INPUT) Parameters.

Listing 7-1 The Configuration (INPUT) Parameters section from access-network-rac.py

    #=========================================================================

    # Configuration (INPUT) Parameters

    #=========================================================================

    # listen address input parameters

    # example: hostname can be DNSName or IPAddress

    AdminServerListenAddress = "host-admin.bea.com"

    AdminServerListenPort    =  7001

    NT1ServerListenAddress   = "host-nt1.bea.com"

    NT1ListenPort            =  8001

    NT2ServerListenAddress   = "host-nt2.bea.com"

    NT2ListenPort            =  8001

    AT1ServerListenAddress   = "host-at1.bea.com"

    AT1ListenPort            =  8001

    AT2ServerListenAddress   = "host-at2.bea.com"

    AT2ListenPort            =  8001

    NTClusterAddress         = "host-nt1.bea.com:8001,host-nt2.bea.com:8001"

    ATClusterAddress         = "host-at1.bea.com:8001,host-at2.bea.com:8001"

    NTClusterMultiCastAddress = '237.0.0.101'

    NTClusterMultiCastPort    = 8050

    ATClusterMultiCastAddress = '237.0.0.102'

    ATClusterMultiCastPort    = 8050

    # DataSource Settings

    # RAC Node-1 Settings

    RACNode1URL      = "SETME_URL"

    # RAC Node-2 Settings

    RACNode2URL      = "SETME_URL"

    # Database settings

    OracleXADriver    = "SETME_XADRIVER"

    OracleNonXADriver = "SETME_nonXADRIVER"

    DBUser            = "SETME_USER"

    DBPassword        = "SETME_PASSWORD"

##### Make these edits

1. Set the Listen Address and Listen Port for the Administration Server, the two Access Tier servers, and the two Network Tier servers.

- Replace the`host*.bea.com` values with either the DNSName or the IP Address of the appropriate servers.
- Replace the Listen Port values as necessary.

Note: | The Listen Address:Port combinations must be unique.

1. Fill in the appropriate Listen Address:Port combinations to assign the servers to the appropriate clusters. The entry should be comma delimited, with no spaces.
2. Fill in the appropriate Multicast Addresses per cluster.
3. Set the appropriate URLs for each of the RAC instances (only in RAC scripts)
4. Set the appropriate values for the transactional (XA) and localTX(nonXA) datasources (in RAC scripts).

Set the appropriate values for the `wlng.datasource` (in non-RAC scripts)

5. Set the appropriate values for the `wlng.localTX.datasource.` The values should be non-XA (only in non-RAC scripts).

The following change may also need to be made:

1. If you want to be able to use the Administration Console and Node Manager to start remote servers, you must change the `NodeManager ListenAddress` values in the Configure Managed Servers section. To do so edit the following line for each managed server
   `set('ListenAddress','localhost')` to change localhost to the correct ListenAddress.

#### Multi-cluster with additions

If you want to use the WLST script to set up a multi-cluster domain and, at the same time, to add additional servers, you must first make the same edits as in the Multi-cluster standard case. You must also make the following additional kinds of edits. Exactly which edits you need to make depends on how your particular installation is set up.

WLST in offline mode, which is the mode that Oracle Communications Services Gatekeeper scripts use, can access and update only those configuration objects that have been previously persisted to a configuration file. All the provided WLST scripts create this configuration file automatically as they run, but each adds only those objects that are specified in the domain templates. If you need to add more configuration objects, such as additional Managed Servers or Machines, you must add statements to the script to create them before you can configure them.

Note: | You can also add servers and machines using the Administrative Console GUI after you set up your core domain. This is a simpler way of accomplishing the same goal.

##### Create Machines

For example, if you need to add additional Machines, you must create them in the script before you assign Managed Servers to them.

Comment Section | Code to add | Value
--- | --- | ---
Configure managed servers | `cd('/') create('new_Machine_5','Machine’) cd('Machine/new_Machine_5') create('new_Machine_5','NodeManager’)` | Add as many of these statements as you need, replacing new_Machine_5 with whatever value is appropriate

##### Create Managed Servers

After you create the Machine, you can assign Managed Servers to them. You can also add new Managed Servers. In the code below, the new Managed Server `WLNG_NT3` is created and then assigned to `new_Machine_5,` created above.

Comment Section | Statement to edit | Value
--- | --- | ---
Configure managed servers | `cd('/') create('WLNG_NT3', 'Server') cd('Server/WLNG_NT3') set('ListenPort', 8001) set('ListenAddress', 'myserver5') set('Machine','new_Machine_5'`) | Create new servers as needed, and set the ListenAddress

##### Set NodeManager Listen Address

You must also add a section to configure any new Machine (and its Node Manager) being added.:

Comment Section | Statement to add | Value
--- | --- | ---
Configure managed servers | `cd('/') cd('Machine/new_Machine_5') set('Name','new_Machine_5') set('Address','new_Machine_5') cd('NodeManager/new_Machine_5') set('ListenAddress','myserver5') set('ListenPort',5556)` | One section per added Machine.

##### Assign New Managed Servers to the appropriate cluster

You must assign any newly-created managed servers to their appropriate cluster by adding an “assign server” line

Comment Section | Statement to add | Value
--- | --- | ---
Configure a cluster and assign the Managed Servers to that cluster. | `cd('/') [standard]` `assign('Server', 'WLNG_NT3','Cluster','WLNG_NT_Cluster')` | One line per added Managed Server.

#### Keep unused communication services from being deployed

It is always possible to remove communication services after the initial deployment of Oracle Communications Services Gatekeeper. If you know that your installation is not using one or more communication services and you prefer that they not be deployed at all in your system, you can add the following information to your configuration script. Remember that all communication services consist of two .ear files, an Access Tier version and a Network Tier version. You will need to address both files to completely remove the communication service.

For example, to keep the PX 3.0 Third Party Call communication service from being deployed, add the following to your script:

`#===================================================================`

`# Unassign applications to target`

`#===================================================================`

`cd(‘/’)`

`unassign('Application', ‘wlng_at_third_party_call_px30#4.0 ', 'Target', 'WLNG_AT_Cluster')`

`unassign('Application', ‘wlng_nt_third_party_call_px30#4.0 ', 'Target', 'WLNG_NT_Cluster')`

### Run the Script

Once you have made all necessary changes to the script, run it using the following command:

    java weblogic.WLST <appropriate-version>.py

## Where to Go From Here

You must now:

- Complete post-installation
- Configure the Oracle Communications Services Gatekeeper software

See Completing Post-Installation for more information.