5 Configuring Oracle WebLogic Communication Services

This chapter describes how to install and configure the Oracle WebLogic Communication Services in different topologies, using the Oracle WebLogic Server Configuration Wizard.

You only need to configure one of the topologies in this chapter. If you are installing OWLCS All-in-One Managed Server, then you only need to perform the actions in that section. To configure an Enterprise Deployment topology, then follow the instructions in that section.

In the Configure JDBC Component Schema screen, check all component schemas, fill common database information (everything except Schema Owner).Check one datasource at a time and enter the Schema Owner. For example:

Table 5-1 Schema owners

Component Schema

schema_owner

User Messaging Service

<prefix>_orasdpm

Location Service

<prefix>_orasdpls

Subscriber Data Service

<prefix>_orasdpsds

Presence

<prefix>_orasdpxdms

OWSM MDS Schema

<prefix>_mds

Click Next. The Test Component Schema screen appears.

In the Test Component Schema screen, all data source connections are tested. Recheck if there is a failure. If there aren't any, click Next. The Configuration Summary screen appears.

In the Configuration Summary screen click Create.

Click Done.

5.1.1 Using Pre-configured Machine Realm

OWLCS is pre-configured with realm example.com. If you want to use this realm, modify the machine's hosts file, pointing example.com to the local IP to enable the server to lookup and resolve example.com. The absolute path to that file is:

Use $DOMAIN_HOME is the directory of your domain, (that is, $MW_HOME/user_projects/domains/base_domain)<admin server host>: The host name of the machine on which you installed the server<admin server port>: The port on which the admin server is listening

In our example, <admin server port> is 7001.

Click the MBeans tab.

Change value of the following mbean attribute for AggregationProxy mbean:

Use $DOMAIN_HOME is the directory of your domain, i.e, $MW_HOME/user_projects/domains/base_domain<admin server host>: The host name of the machine on which you installed the server<admin server port>: The port on which the admin server is listening

In our example, <admin server port> is 7001.

Click the MBeans tab.

Change value of the following mbean attribute for ThirdPartyCall mbean:

PAssertedIdentityURI=sip:tpcc.user@<your realm>

Configure Machine with the new realm:

UNIX: /etc/hosts

Windows: C:\WINDOWS\system32\drivers\etc\hosts

5.1.3 Start the Administration Server

To start the Administration Server:

Navigate to MW_HOME/user_projects/domains/base_domain/bin

Run this command:

UNIX: ./startWebLogic.sh

Windows: startWebLogic.cmd

5.1.4 Start the Managed Server

To start the Managed Server:

Open a new terminal

Navigate to MW_HOME/user_projects/domains/base_domain/bin

Run this command:

UNIX: ./startManagedWebLogic.sh wlcs_server1

Windows: startManagedWebLogic.cmd wlcs_server1

Enter the Administrator user name and password.

Verify that the Managed Server is running when you see the console message: <Server started in RUNNING mode>. Production Mode will require you to enter credentials when starting.

5.1.5 Provisioning Test Users

To confirm that the installation was successful, you should create a few test users to test out OWLCS using Oracle Communicator.

Start sash:

On UNIX: $DOMAIN_HOME/bin/launch_sash.sh -p 8001

On Windows: $DOMAIN_HOME/bin/launch_sash.cmd -p 8001

Note:

By default the managed server picks up port 8001. If you configured the port to be something else, use that instead.

Provision the user: Run the following command; replace alice with username and example.com with your realm. Enter your password.

5.1.6 Testing the Installation

Provision a test user in OWLCS as described above (for example: sip:alice@example.com).

Create an Oracle Communicator account for sip:alice@example.com.

Login to Oracle Communicator, disregard the login pop up if it appears.

Click the menu button on the top left (Settings).

Choose Preferences.

Click the Network tab.

Check Use a proxy server, and enter the canonical host name of the load balancer in the Address field.

Do the same for XDMS Host. Ensure that the XDMS port is the HTTP listen port of the load balancer http pool.

Click OK.

Restart Oracle Communicator and log in.

Enter the username and the password (as chosen previously). If you can register and change your Presence status, the installation was successful.

You can create an account for another user similarly and add him/her as a buddy to the first user. User1 should be able to send instant messages to User2, and they should be able to see each other's presence.

5.1.7Logging

All logs are written to a single file (per server) at the following location: MW_HOME/user_projects/domains/base_domain/servers/wlcs_server1/logs/wlcs_server1-diagnostic.log

5.2 Configuring an All-in-One Administration Server

If you clicked Yes in the last screen for installing Communication services, skip Step 1 below. If you clicked No, then complete Step 1 below.

In the Configure JDBC Component Schema screen, check all component schemas, fill common database information (everything except Schema Owner).Check one datasource at a time and enter the Schema Owner. For example:

Table 5-2 Schema owners

Component Schema

schema_owner

User Messaging Service

<prefix>_orasdpm

Location Service

<prefix>_orasdpls

Subscriber Data Service

<prefix>_orasdpsds

Presence

<prefix>_orasdpxdms

OWSM MDS Schema

<prefix>_mds

Click Next. The Test Component Schema screen appears.

In the Test Component Schema screen, all data source connections are tested. Recheck if there is a failure. If there aren't any, click Next. The Configuration Summary screen appears.

In the Configuration Summary screen click Create.

Click Done.

5.2.1 Using Pre-configured Machine Realm

OWLCS is pre-configured with realm example.com. If you want to use this realm, modify the machine's hosts file, pointing example.com to the local IP to enable the server to lookup and resolve example.com. The absolute path to that file is:

Use $DOMAIN_HOME is the directory of your domain, (that is, $MW_HOME/user_projects/domains/base_domain)<admin server host>: The host name of the machine on which you installed the server<admin server port>: The port on which the admin server is listening

In our example, <admin server port> is 7001.

Click the MBeans tab.

Change value of the following mbean attribute for AggregationProxy mbean:

Use $DOMAIN_HOME is the directory of your domain, i.e, $MW_HOME/user_projects/domains/base_domain<admin server host>: The host name of the machine on which you installed the server<admin server port>: The port on which the admin server is listening

In our example, <admin server port> is 7001.

Click the MBeans tab.

Change value of the following mbean attribute for ThirdPartyCall mbean:

PAssertedIdentityURI=sip:tpcc.user@<your realm>

Configure Machine with the new realm:

UNIX: /etc/hosts

Windows: C:\WINDOWS\system32\drivers\etc\hosts

5.2.3 Start the Administration Server

To start the Administration Server:

Navigate to MW_HOME/user_projects/domains/base_domain/bin

Run this command:

UNIX: ./startWebLogic.sh

Windows: startWebLogic.cmd

Verify that the Administration Server is running when you see the console message: <Server started in RUNNING mode>. Production Mode will require you to enter credentials when starting.

5.2.4 Provisioning Test Users

To confirm that the installation was successful, you should create a few test users to test out OWLCS using Oracle Communicator.

Start sash:

On UNIX: $DOMAIN_HOME/bin/launch_sash.sh

On Windows: $DOMAIN_HOME/bin/launch_sash.cmd

Note:

By default the managed server picks up port 7001. If you configured the port to be something else, use that instead.

Provision the user: Run the following command, replace alice with username and example.com with your realm (for example: yourcompany.com). Enter your password.

5.2.5 Testing the Installation

Provision a test user in OWLCS as described above (for example: sip:alice@example.com).

Create an Oracle Communicator account for sip:alice@example.com.

Login to Oracle Communicator, disregard the login pop up if it appears.

Click the menu button on the top left (Settings).

Choose Preferences.

Click the Network tab.

Check Use a proxy server, and enter the canonical host name of the load balancer in the Address field.

Do the same for XDMS Host. Ensure that the XDMS port is the HTTP listen port of the load balancer http pool.

Click OK.

Restart Oracle Communicator and log in.

Enter the username and the password (as chosen previously). If you can register and change your Presence status, then the installation was successful.

You can create an account for another user similarly and add him or her as a buddy to the first user. User1 should be able to send instant messages to User2, and they should be able to see each other's presence.

5.2.6Logging

All logs are written to a single file (per server) at the following location: MW_HOME/user_projects/domains/base_domain/servers/AdminServer/logs/AdminServer-diagnostic.log

5.3 Configuring OWLCS Enterprise Deployment

This section describes how to complete the installation and configuration for the high-availability installation of OWLCS. The Enterprise Deployment topology is the OWLCS high-availability deployment solution.

5.3.1 Introducing Enterprise Deployment Topology

The Enterprise Deployment Topology supports High-Availability. In the event of a failover, load balancers can continue directing traffic to functioning (available) nodes. As shown in Figure 5-5, there are three domains within each node: wlcs_sipinfra, wlcs_services and wlcs_presence. They correspond to SIP Infrastructure, Services and Presence components respectively. State replication (that is, sharing of state information across two managed servers) is supported between the wlcs_sipinfra1engine and wlcs_sipinfra2 replica. If one node goes down, the other can continue to serve existing and new requests because state information is replicated and saved on the other node.

5.3.3.1 Creating Database Schema using RCU

This section describes how to create database schema using Repository Creation Utility (RCU).

Note:

The procedure in this section can be skipped if the database schema has already been created. You can reuse a schema that you have already created. Remember to use the same schema prefix when entering database information while configuring the data sources as described in the procedure.

If skipping this procedure, ensure that you have created all component schema required by OWLCS, specifically, the Presence, User Messaging, Subscriber Data Service, Location Service, and OWSM MDS schema.

Provide the details for any one of the RAC hosts and use the service name of the DataBase.

Note:

In general, users will be using database servers that are configured to use UTF-8 encoding. If you are not using a database server configured to use UTF-8 encoding, then a warning message appears informing you that your database is not using UTF-8 format by default. Click Ignore and continue with the installation.

On Step 3 of 7 (Components), perform the following steps:

Select Create a new prefix, and choose a schema prefix (such as OWLCS).

Note:

Ensure you make note of this schema prefix; you will need to use it later in the installation.

Check the checkbox in front of WebLogic Communication Services. OWLCS and accompanying components are automatically selected for you (Metadata Services, Presence, SIP Infrastructure Subscriber Data Services SIP Infrastructure Location Service, and User Messaging Service). Ensure that those five components are selected before proceeding. If any of those five components are not selected, select them manually. Then, click OK when completed.

On Step 4 of 7 (Schema Passwords), perform the following steps:

Select Use same passwords for all schemas.

Enter your password in the field provided and confirm it.

Click Next.

On Step 5 of 7 (Map Tablespaces), perform the following steps:

For this installation, click Next. A Repository Creation notification will appear.

Click OK. Tablespaces will be created, and the progress will be displayed in a pop-up notification.

he Middleware Home Directory is the root directory for the OWLCS Base Platform installation. Middleware Home Directory is referred to as MW_HOME in this book. When you see MW_HOME or $MW_HOME, that means the absolute path to your Middleware Home directory.

On the Choose Product Installation Directories screen, perform the following steps:

Though you can change locations, Oracle Corporation recommends that you use the default locations whenever possible.

Click Next.

On the Choose Shortcut Location screen (Microsoft Windows only), do the following:

Select the All Users Start Menu folder.

Click Next.

On the Installation Summary screen, click Next.

On the Installation Complete screen, click Next.

5.3.3.3 Installing OWLCS Components

Perform the following procedures to install Oracle WebLogic Communication Services, which includes SIP Infrastructure, Services and Presence components, for each of the domains.

Navigate to the OWLCS directory on your installation media or staged installation directory, and run one of the following commands, depending on your operating system:

UNIX: owlcs/Disk1/runInstaller

Windows: owlcs\Disk1\setup.exe

Enter <absolute path to middleware home>/jdk160_11 when asked to specify the JRE/JDK location.

Note:

The Java VM that you use here to run the installation process is not related to the Java VM that will be used by OWLCS at runtime. Selecting Sun JDK here does not preclude you from using JRockit at runtime.

On the Welcome screen click Next. The Prerequisites Checklist appears.

In the Prerequisites Checklist screen, verify that a check mark in the Status column appears for each of the prerequisites. If a failure notification appears, you must correct the problem (ensure that the operating system and service packs are correct, and the memory is adequate), then click Continue.

5.3.3.4 Repeating the Installation for Machine 2

Ensure that you use exactly the same MW_HOME path as you used for Machine 1.

For example, if your MW_HOME on Machine 1 is /home/owlcsuser/mw_home, Machine 2 should have exactly the same MW_HOME, /home/owlcsuser/mw_home.

5.3.3.5 Configuring Load Balancers

Route network traffic through a Load Balancer. Load Balancers must be capable of routing both HTTP and SIP traffic, and must be configured to do so. This section details the properties of the Virtual Hosts and Ports for proper configuration.

5.3.3.5.1 HTTP Pools

Configure two HTTP Pools. They are configured at the Load Balancer and route to ports 8001 and 8011 on the two Communication Server machines. The former is the location of the SIPInfra Containers. The latter is the location of the Services container used by external client applications such as Oracle WebCenter.

5.3.3.5.2 Main SIP Pools

The Main SIP pool is used by SIP clients on the external network, including Oracle Communicator. This SIP pool must support both TCP and UDP.

5.3.3.5.3 Presence SIP Pools

Presence SIP Pools are the SIP pools used for accessing the Presence Server. These must support both UDP and TCP and need only be available internally.

5.3.3.5.4 Configuring Virtual Servers on the Load Balancer

Configure the Load Balancer with Virtual Servers to support the pools listed above. Recommended settings are shown in Table 5-3.

5.3.3.7 Changing Realm from example.com

After installation, the realm must be configured to be example.com. This value must be changed to reflect the real domain name used in the installation. This section describes all the places where this needs to be changed and how to change it.

SIP Server

Login to the Administration Console for managing the wlcs_sipinfra domain. Administration Console for wlcs_sipinfra domain is located at: http://<machine host 1>:7001/console

Click the SipServer link on left navigation pane.

In the Configuration->General tab, scroll down to Domain Aliases: and enter the realm you want to choose (for example: myrealm.com).

Digest Authentication

Login to the Administration Console of the wlcs_sipinfra domain. It can be accessed from: http://<machine 1 host>:7001/console

Click Security Realms on the left navigation pane.

Click myRealm.

Click the Providers tab.

Click DigestIdentityAsserter.

Click the Provider Specific tab.

Scroll down to DigestRealmName attribute and choose the appropriate realm (for example: myrealm.com).

Note:

Repeat steps 1-7 above for wlcs_services and wlcs_presence domains. The wlcs_services domain Admin Console can be accessed from http://<machine 1 host>:7002/console and the wlcs_presence domain can be accessed from http://<machine 2 host>:7003/console.

5.3.3.9 Provisioning Test Users

To confirm that the installation was successful, you should create a few test users to test out OWLCS using Oracle Communicator.

On Machine 1, start sash:

On UNIX: $DOMAIN_HOME/bin/launch_sash.sh -p 8001

On Windows: $DOMAIN_HOME/bin/launch_sash.cmd -p 8001

Note:

$DOMAIN_HOME is any domain home (wlcs_sipinfra, wlcs_services, wlcs_presence). By default the wlcs_sipinfra1 or 2 managed server picks up port 8001. If you configured the port to be something else, use that instead.

Provision the user: run the following command, replacing alice with username and example.com with your realm (for example: yourcompany.com).

5.3.4 Testing the Installation

Provision a test user in OWLCS as described above (for example: sip:alice@example.com).

Create an Oracle Communicator account for sip:alice@example.com.

Login to Oracle Communicator, disregard the login pop up if it appears.

Click the menu button on the top left (Settings).

Choose Preferences.

Click the Network tab.

Check Use a proxy server, and enter the canonical host name of the load balancer in the Address field.

Do the same for XDMS Host. Ensure that the XDMS port is the HTTP listen port of the load balancer http pool.

Click OK.

Restart Oracle Communicator and log in.

Enter the username and the password (as chosen previously). If you can register and change your Presence status, then the installation was successful.

You can create an account for another user similarly and add him/her as a buddy to the first user. User1 should be able to send instant messages to User2, and they should be able to see each other's presence.

5.3.5 Starting JConsole to Modify MBeans on UNIX

In order to start JConsole to perform some of the modifications in this chapter, follow these steps: