4 Configuring WebLogic Server

This chapter includes the steps required to configure the application server to run the Oracle Role Manager (Role Manager) server and Web application.

This chapter includes the following sections:

• Before You Configure the Application Server

• Configuring Oracle WebLogic Server in a Nonclustered Mode

• Configuring Oracle WebLogic Server in a Clustered Mode

4.1 Before You Configure the Application Server

Role Manager is intended to be deployed on only one server platform per installation. The server platform can be one of the following:

• Oracle WebLogic Server

• JBoss

• IBM WebSphere

The procedures in this chapter assume the following:

• The application server system has network access to the database server host.

• The Role Manager software is accessible by the application server system.

• You know the application server's listener port and host name.

• If running on WebSphere, a server, cell, and node to use for Role Manager have been created and configured.

While configuring the application servers, you may require to modify the following files:

• webui.war file - This file is used for customizing Oracle Role Manager to the user's requirement.

  Note:

  For WebSphere application server, webui.ear file is used and not webui.war file.

• orm-ds.xmlfile - This file is used to configure the data source information. Refer Step 5 of the "Configuring JBoss Server in a Nonclustered Mode" for information about how to modify the data source information in the orm-ds.xml file.

4.2 Configuring Oracle WebLogic Server in a Nonclustered Mode

You can configure the WebLogic server either manually or automatically, following an extension template. This section provides the information about automated configuration of WebLogic server. If you want to configure the WebLogic server manually, refer to Appendix A.

Note:

Before you run the automated configuration of WebLogic server, ensure that the WebLogic server is installed and the node manager is up and running. You can start the node manager by running the BEA_HOME/wlserver_10.3/server/bin/startNodeManager.sh script for Linux.

BEA_HOME/wlserver_10.3/server/bin/startNodeManager.cmd script for Microsoft Windows.

You must configure WebLogic server in SSL mode to operate in a secure environment. For information about configuring SSL for WebLogic server, refer to the following URL:

http://e-docs.bea.com/wls/docs103/secmanage/ssl.html

This section includes the following topics:

• Configuring WebLogic Server Based On Template

• Setting Up Commons Logging

• Configuring Administrative Console

• Deploying Role Manager

4.2.1 Configuring WebLogic Server Based On Template

To perform the template based configuration of WebLogic server:

1. Run the configuration wizard in WebLogic server directory:

   BEA_HOME\wlserver_10.3\common\bin\config.exe or config.sh

2. When the configuration wizard is displayed, select Create a new WebLogic Domain and click Next.

3. Select Base this domain on an existing template, go to the following path and click Next:

   ORM_HOME/weblogic/templates/10.3/orm_createdomain_template_103.jar

4. In the Specify Domain Name and Location window, type domain name and click Next.

5. In the Configure Administrator Username and Password window, type User Name and Password and click Next.

6. Configure server start mode and JDK by performing the following steps:

   1. On the left side of the window, select Production Mode.

   2. On the right side of the window, select appropriate JDK and click Next.

7. In the Configure Data Sources window, for both the ORM Data Source and the ORM XA Data Source, type the DBMS details such as User Name, Password, DBMS/Service, Host, and Port and click Next.

   Note:

   If you are using RAC database, provide the following string while creating the data source, by substituting the values for hostname, port, and service name of your instance:

   jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host1-vip)(PORT=1521))(ADDRESS=(PROTOCOL=TCP)(HOST=host2-vip)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl.us.oracle.com)))
   

8. In the Test JDBS Data Sources window, ensure that you click Test Connections to test the data connection for each datasource and then click Next.

9. In the Select Optional Configuration window, select all check boxes and click Next.

10. In the Configure Administration Server window, set the Listen Address to a value appropriate to your setup such as, LocalHost, IP Address, DNS equivalent and Listen Port and then click Next.

11. In the Configure Managed Servers window, set the Listen Address to a value appropriate to your setup such as, LocalHost, IP Address, DNS equivalent and Listen Port and then click Next.

12. In the Configure Clusters window, click Next.

13. In the Configure Machines window:

    • for UNIX machine, click the UNIX machine tab, the Oracle Role Manager machine name is auto populated. Click Next.

    • for Windows machine, click the UNIX machine tab and delete the existing Oracle Role Manager machine name, ormMachine. On the Machine tab, click Add and then type Oracle Role Manager machine name, ORM_Machine, Node manager listen address, and Node manager listen port, and then click Next.

14. In the Assign Servers to Machines window, ensure that ORMServer is listed under ormMachine on the right window and then click Next.

    Note:

    For Microsoft window, select ORM_Machine on the right window.

15. In the Target Services to Clusters or Servers window, click Next.

16. In the Configure RDBMS Security Store Database window, click Next.

17. In the Configuration Summary window, verify the details and click Create. The domain is created and the following are configured automatically:

    1. Admin server is created.

    2. Oracle Role Manager Managed server, ORMServer is created.

    3. Non-XA Data Source, ORM Data Source is created.

    4. XA Data Source, ORM XA Data Source is created.

    5. JMS Server, ORM JMSServer is created.

    6. JMS Module, ORM JMSModule is created.

    7. Subdeployment, ORM JMSSubdeployment is created.

    8. Topic, ORM NotificationTopic is created.

    9. Queues, ORM FinisherQueue, ORM LoaderQueue, and ORM IncomingEventQueue are created.

    10. Connection Factory such as ORM Connection Factory and Finalization ORM Connection Factory are created.

18. Click Done.

4.2.2 Setting Up Commons Logging

Set up the Commons Logging by performing the steps described in "Setting Up Commons Logging".

Note:

Logging will take effect the next time WebLogic Administration server and Oracle Role Manager server are started.

4.2.3 Configuring Administrative Console

1. Start the server and log in to the WebLogic Administrative Console.

2. Set the JTA transaction timeout parameter by performing the following steps:

   1. In the domain tree, select Services, JTA.

   2. In the Timeout Seconds field, type 1200.

   3. In the Abandon Timeout Seconds field, ensure that the value is 86400.

   4. Click Save.

      Note:

      The value of Abandon Timeout Seconds must always be greater than Timeout Seconds and Stuck Thread Max Time.

3. Set the Stuck Thread Max Time parameter by performing the following steps:

   1. In the domain tree, select Environment, Servers, ORMServer.

   2. Click the Tuning tab.

   3. In the Stuck Thread Max Time field, type 3000.

   4. Click Save.

      Note:

      The value of Stuck Thread Max Time must be at least twice that of the value of Timeout Seconds.

4. Configure the JMS Connection Factory by performing the following steps:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMS Module.

   3. Click ORM ConnectionFactory.

   4. Ensure that the Default Targeting Enabled field is selected.

   5. Click Save.

   6. Click the Transactions tab, ensure that the XA Connection Factory Enabled field is selected and then click Save.

   7. In the domain tree, select Services, Messaging, JMS Modules.

   8. Click ORM JMS Module.

   9. Click Finalization ORM ConnectionFactory.

   10. Ensure that the Default Targeting Enabled field is selected.

   11. Click Save.

   12. Click the Transactions tab, ensure that the XA Connection Factory Enabled field is selected and then click Save.

5. Configure the Redelivery Limit by performing the following steps:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMS Module.

   3. Click ORM FinisherQueue.

   4. Click Delivery Failure.

   5. Set Redelivery Limit value to 3.

   6. Click Save.

   7. In the domain tree, select Services, Messaging, JMS Modules.

   8. Click ORM JMS Module.

   9. Click ORM IncomingEventQueue.

   10. Click Delivery Failure.

   11. Set Redelivery Limit value to 3.

   12. Click Save.

   13. In the domain tree, select Services, Messaging, JMS Modules.

   14. Click ORM JMS Module.

   15. Click ORM LoaderQueue.

   16. click Delivery Failure.

   17. set Redelivery Limit value to 3.

   18. Click Save.

6. In the domain tree, select Environment, Servers, ORM Server and navigate to the Control tab and click Start to start the managed server.

   Note:

   You must start node manager before starting the managed server.

4.2.4 Deploying Role Manager

Note:

Perform this procedure only if you are repeating the deployment of the same Role Manager server.

If this is your first installation, then skip this section and continue with "To deploy the Role Manager server application".

To deploy Role Manager:

1. Start up the Role Manager server that contains the JMS server.

2. Navigate to Services, Messaging, and JMS Modules.

3. Click ORM JMSModule.

4. From the resource list, select the ORMFinisherQueue.

5. On the Monitoring tab, select the ORM JMSModule! ORM Finisher Queue destination and click Show Messages.

6. Click Delete and from the list of options, select Delete All.

7. In the confirmation page, click Yes.

To deploy the Role Manager server application:

1. Select Deployments in the left part of the Administration Console window.

2. Click Install in the right part of the Administration Console window.

3. In the ORM_HOME, navigate to the server.ear file and select it. Click Next.

   Note:

   The server.ear file can be accessed from the path ORM_HOME/lib/server.ear.

4. Select Install this deployment as an application. Click Next.

5. Select ORM Server as the target in the Target field. Click Next.

6. In the Name field, type the name of the Role Manager server application, for example, ORM ServerApp.

7. Click Next and in the Install Application Assistant page, click Finish.

8. Click Save to activate the changes.

   Note:

   You must restart the ORMServer to login.

9. In the right part of the Administration Console window, under Deployments, check the State of ORM Server App. If it displays: Prepared, then select the checkbox next to the name of it. Click Start and from the list, select Servicing All Requests. When the status of the application is Active, you can log into the Oracle Role Manager Console.

10. To test the server installation, ensure that you can get to the Role Manager administrative console from a Web browser. For example:

    http://localhost:<port>/ormconsole

    Note:

    The default Oracle Role Manager application server port is 9001.

    You should see the Home page of the Role Manager administrative console.

To deploy the Role Manager Web application:

1. Select Deployments in the left part of the Administration Console window.

2. Click Install in the right part of the Administration Console window.

3. Navigate to the webui.war file and select it. Click Next.

   Note:

   The webui.war file can be accessed from the path ORM_HOME//webui/weblogic/10.3/webui.war.

4. Select Install this deployment as an application. Click Next.

5. In the Target field, select ORMServer as the target and then click Next.

6. In the Name field, type the name of the Web user interface application.

7. Select Custom Roles and Policies: Use only roles and policies that are defined in the Administration Console from the Security list.

8. Click Next and then click Finish.

9. In the right part of the Administration Console window, under Deployments, check the State of Webui App. If it displays: Prepared, then select the checkbox next to the name of it. Click Start and from the list, select Servicing All Requests. When the status of the application is Active, you can log into the Oracle Role Manager Console.

10. Test the Web application installation as follows:

    1. In a Web browser, navigate to the Role Manager Web application address. For

       example:

       http://localhost:<port>/webui

    2. Log in as the Role Manager Administrator created in "Installing Role Manager".

       Note:

       Data must be loaded into the system to expose all the functionality of the application. Refer to "Loading Sample Data" for instructions.

       You should see the Home page of the Role Manager Web application.

To start the server application and the Web application for WebLogic:

Starting the server application and the Web application are automatically taken care for WebLogic. If server is running in Production mode, then application will be in prepared state. To change it to active state, perform the following steps:

1. Click Deployments and select an application.

2. In the right part of the Administration Console window, under Deployments, check the State of ORM Server App. If it displays:

   • Active, then the application is started and you need not perform the following steps.

   • Prepared, then select the checkbox next to the name of it. Click Start and from the list, select Servicing All Requests. When the status of the application is Active, you can log into the Oracle Role Manager Console.

4.3 Configuring Oracle WebLogic Server in a Clustered Mode

This section explains how to deploy Oracle Role Manager in a clustered Oracle WebLogic Server environment.

This section discusses the following topics:

• About Oracle WebLogic Server Clusters

• Configuring WebLogic Clusters

• Configuring Apache Failover Proxy

4.3.1 About Oracle WebLogic Server Clusters

A clustered installation requires multiple host computers. The instructions in this chapter involve deployment and running of Oracle Role Manager on three host computers. These instructions assume that you have three computers, of which one is used to host the Web server and the other two are used for Oracle Role Manager cluster.

Table 4-1 describes the entities needed for a cluster, the computers that the entities run on, and the software required for the entities. Host computers and entities are labeled.

Table 4-1 WebLogic-Based Oracle Role Manager Cluster Host Computers

Host Computers	Entities	Software	Description
PRIMARY_NODE on ORM_Machine	WebLogic Admin Server, and WebLogic Node Manager	WebLogic Server	Administrative server for the WebLogic domain and WebLogic Node Manager
	ORM Finalization Server	Oracle Role Manager	ORM Finalization Server
	ORM_SERVER1	Oracle Role Manager	WebLogic Managed Server, part of ORM_CLUSTER
	ORM_CLUSTER	Oracle Role Manager	Name of the WebLogic cluster that hosts Oracle Role Manager (logical entity).
SECONDARY_NODE on ORM_Machine1	WebLogic Node Manager	WebLogic Server	WebLogic Node Manager
	ORM_SERVER2	Oracle Role Manager	WebLogic Managed Server 2, part of ORM_CLUSTER
	ORM_CLUSTER		Name of the WebLogic cluster that hosts Oracle Role Manager (logical entity).
THIRD_NODE on ORM_Machine2	Apache Web Server	Apache HTTP Server 2.2 with WebLogic 10.3 Apache plugin	Apache Failover Proxy

Caution:

Deploying an application in a clustered installation is a complex procedure. This document assumes that you have expertise in installing and running applications on an Oracle WebLogic Server cluster. This chapter provides Oracle Role Manager-specific information only. It does not cover the procedure to set up an Oracle WebLogic Server cluster. For more information about clustering, refer to Oracle WebLogic Server documentation.

4.3.2 Configuring WebLogic Clusters

The instructions mentioned in this section are for installing Role Manager in a WebLogic cluster of two machines with two Role Manager servers, one Admin Server and one finalization server. Therefore there are four servers, the PRIMARY_NODE on first machine (ORM_Machine) hosts Admin, Finalization, and Managed Server1 and the SECONDARY_NODE on second machine (ORM_Machine1) hosts Managed Server2. In addition, the data store for the queues are database-based and not file-based.

4.3.2.1 Configuring WebLogic Server in a Clustered Mode

To configure WebLogic server in a clustered mode:

1. On the primary node, complete the single instance of WebLogic server configuration, install and deploy Role Manager, load sample data, and ensure that the server is running. Refer to "Configuring WebLogic Server Based On Template" for instructions on configuring the WebLogic server.

   The following are the configuration details for the primary node:

   Host: PRIMARY_NODE

   Machine: ORM_Machine

   BEA_Home: BEA_HOME

   WLS_HOME: WLS_HOME

   DOMAIN_HOME: DOMAIN_HOME

   ADMIN_PORT: ADMIN_PORT

   ORM server: ORMServer

   ORM server Port: ORMServer_Port (9001)

   Node_manager Port: NODE_MANAGER_PORT (5556, ssl)

   To control your Managed Servers remotely from the Administrative Server, you must set up and configure Node Manager on each of the remote systems hosting Managed Servers by following the instructions on the BEA e-docs page: http://e-docs.bea.com/wls/docs103/nodemgr/nodemgr_config.html

   The default location of the nodemanager.properties file is:

   BEA_HOME/wlserver_10.3/common/nodemanager

2. Install WebLogic on a secondary node.

3. Start the node manager on both the nodes and start the administrative server on primary node if it is not running.

4. Log in to the administrative server console on the primary node. For example: http://primarynode:7001/console.

5. Shutdown ORMServer on the primary node as follows:

   1. In the domain tree, select Environment, Servers.

   2. Click the Control tab.

   3. Select ORM Server and then click Shutdown.

6. Create a Machine, for example, ORM_Machine1 for the secondary node as follows:

   1. In the domain tree, select Environment, Machines.

   2. Click New.

   3. In the Name field, type ORM_Machine1.

      Note:

      For UNIX flavors, in the Machine OS field, select UNIX.

   4. Click OK.

7. Configure the machine to access Node Manager on secondary machine as follows

   1. In the domain tree, select Environment, Machines.

   2. Click on the machine that you created, for example, ORM_Machine1.

   3. Click the Node Manager tab.

   4. In the Listen Address field, type the IP address of the secondary node and click Save.

8. Create a server, for example, ORMServer1 which uses the port, for example, ORMServer_Port1(7071) as follows:

   1. In the domain tree, select Environment, Servers.

   2. Click New.

   3. In the Server Name field, type ORMServer1.

   4. In the Server Listen Port field, type 7071.

   5. Click Finish.

9. Ensure that ORMServer1 is assigned to ORM_Machine1 as follows:

   1. In the domain tree, select Environment, Machines, ORM_Machine1, Node Manager.

   2. Check whether the IP address is same as the secondary node.

   3. Click the Servers tab and select Add.

   4. Choose Select an existing server, and associate it with this machine and from the Select a server list, select ORMServer1.

   5. Click Finish.

   The following are the configuration details of the secondary node:

   Host: SECONDARY_NODE

   Machine: ORM_Machine1

   BEA_Home: BEA_HOME1

   WLS_HOME: WLS_HOME1

   DOMAIN_HOME: No domain yet

   ADMIN_PORT: No admin server on secondary node

   ORM server: ORMServer1

   ORM server Port: ORMServer_Port1 (7071)

   Node_manager Port: NODE_MANAGER_PORT1 (5556, ssl)

10. Create cluster as follows:

    1. In the domain tree, select Environment, Clusters.

    2. Click New.

    3. In the Name field, type ORMCluster.

    4. In the Messaging Mode list, select Multicast.

       Note:

       The default values for multicast address and multicast port can be used only if they do not conflict with any other cluster in the same domain.

    5. Click OK.

    6. Click ORMCluster.

    7. Click Servers tab.

    8. Click Add to add a server to cluster.

    9. Select the server, ORMServer and click Finish.

    10. Repeat the steps g to h and select the second server, ORMServer1.

4.3.2.2 Configuring JDBC Stores

1. Configure the JDBC data sources as follows:

   1. In the domain tree, select Services, JDBC, Data Sources.

   2. Click ORM Data Source.

   3. Click the Targets tab.

   4. Select ORMCluster, All servers in the cluster.

   5. Click Save.

   6. Repeat the steps a to f for ORM XA Data Source, except that in the Step c, click ORM XA Data Source.

2. Create a JDBC Store as follows:

   1. In the domain tree, select Services.

   2. Click Persistent Stores.

   3. Click New and select Create JDBC Store from the list.

   4. In the Name field, type JDBCStore.

   5. In the Target field, select ORMServer.

   6. In the DataSource field, select ORM Data Source.

   7. In the Prefix Name field, type jdbcstore.

   8. Click OK.

3. Create another JDBC Store as follows:

   1. In the domain tree, select Services.

   2. Click Persistent Stores.

   3. Click New and select Create JDBCStore from the list.

   4. In the Name field, type JDBCStore1.

   5. In the Target field, select ORMServer1.

   6. In the DataSource field, select ORM Data Source.

   7. In the Prefix Name field, type jdbcstore1.

   8. Click OK.

4.3.2.3 Configuring JMS Servers

1. Create a JMS server for the secondary node as follows:

   1. In the domain tree, select Services, Messaging.

   2. Click JMS Servers, ORM JMSServer.

   3. In the Persistent Store field, select JDBCStore.

   4. click Save.

2. Create another JMS server in the secondary node as follows:

   1. In the domain tree, select Services, Messaging.

   2. Click JMS Servers.

   3. Click New.

   4. In the Name field, type ORM JMSServer1.

   5. In the Persistent Store field, select JDBCStore1 and then click Next.

   6. In the Target field, select ORMServer1.

   7. Click Finish.

3. Configure JMS Modules as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMSModule.

   3. Click the Targets tab.

   4. Select ORMCluster, All servers in the cluster.

   5. Click Save.

4.3.2.4 Configuring a Subdeployment

1. Create a Subdeployment as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMSModule.

   3. Click the Subdeployments tab.

   4. Click New.

   5. In the Subdeployment Name field, type ORM JMSSubdeployment1.

   6. Click Next and select ORM JMSServer1 as the target JMS server.

   7. Click Finish.

2. Create a second Subdeployment as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMSModule.

   3. Click the Subdeployments tab.

   4. Click New.

   5. In the Subdeployment Name field, type cf-sub.

   6. Click Next and select ORMCluster, All servers in the cluster.

   7. Click Finish.

4.3.2.5 Configuring JMS Topics and Queues

1. Create JMS Topics and Queues using Distributed Option as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click ORM JMSModule.

   3. Select ORM NotificationTopic, ORM FinisherQueue, ORM LoaderQueue, ORM IncomingEventQueue, Finalization ORM ConnectionFactory.

   4. Click Delete.

2. Recreate the Oracle Role Manager NotificationTopic as follows:

   1. Click New.

   2. Select Distributed Topic.

   3. Click Next.

   4. In the Name field, type ORM NotificationTopic.

   5. In the JNDI Name field, type orm/topic/NotificationTopic.

   6. Click Finish.

3. Recreate the Oracle Role Manager LoaderQueue as follows:

   1. Click New.

   2. Select Distributed Queue.

   3. Click Next.

   4. In the Name field, type ORM LoaderQueue.

   5. In the JNDI Name field, type orm/queue/LoaderQueue.

   6. Click Finish.

4. Recreate the Oracle Role Manager IncomingEventQueue as follows:

   1. Click New.

   2. Select Distributed Queue.

   3. Click Next.

   4. In the Name field, type ORM IncomingEventQueue.

   5. In the JNDI Name field, type orm/queue/IncomingEventQueue.

   6. Click Finish.

4.3.2.6 Configuring Finalization Server

1. Create a server, ORMFinalizationServer as follows:

   Note:

   The new server can be in a different domain, or in the same domain, but not in the cluster.

   1. In the domain tree, select Environment, Servers.

   2. Click New.

   3. In the Server Name field, type ORMFinalizationServer.

   4. In the Server Listen Port field, type 7074.

   5. Click Finish.

2. Configure a machine for the Oracle Role Manager FinalizationServer as follows:

   1. In the domain tree, select Environment, Servers.

   2. Click ORMFinalizationServer.

   3. Click Machine and select ORM_Machine on which this server is to be run.

   4. Click Save.

3. Create a JMS Server as follows:

   1. In the domain tree, select Services, Messaging, JMS Servers.

   2. Click New.

   3. In the Name field, type FinalizationJMSServer.

   4. Click Next.

   5. In the Target field, select ORMFinalizationServer.

   6. Click Finish.

4. Create a JMS module as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click New.

   3. In the Name field, type FinalizationJMSModule.

   4. Click Next.

   5. In the Target field, select ORMFinalizationServer.

   6. Click Next.

   7. Click Finish.

5. Create a Subdeployment in the JMS module as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click FinalizationJMSModule.

   3. Click the Subdeployments tab.

   4. Click New.

   5. In the Subdeployment Name field, type ORM JMSSubdeployment.

   6. Click Next and select FinalizationJMSServer as the target JMS server.

   7. Click Finish.

6. Create a connection factory as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click FinalizationJMSModule.

   3. Click New.

   4. Select Connection Factory and click Next.

   5. In the Name field, type Finalization ORM ConnectionFactory.

   6. In the JNDI Name field, type orm/remote/jms/FinalizationConFac.

   7. Click Next and then click Finish.

   8. Click Finalization ORM ConnectionFactory.

   9. Click the Transactions tab.

   10. Select XA Connection Factory Enabled.

   11. Click Save.

7. Create a queue as follows:

   1. In the domain tree, select Services, Messaging, JMS Modules.

   2. Click FinalizationJMSModule.

   3. Click New.

   4. Select Queue and click Next.

   5. In the Name field, type ORM FinalizationQueue.

   6. In the JNDI Name field, type orm/remote/queue/BtFinisherQueue.

   7. Click Next.

   8. In the Subdeployments field, select ORM JMSSubdeployment.

   9. Click Finish.

8. Change the configuration of Oracle Role Manager Data Source to target ORMFinalizationServer as follows:

   1. In the domain tree, select Services, JDBC, Data Sources.

   2. Click ORM Data Source.

   3. Click the Targets tab.

   4. Select ORMFinalizationServer, and ensure that ORMCluster is selected.

   5. Click Save.

9. Create a JDBC Store as follows:

   1. In the domain tree, select Services, Persistent Stores.

   2. Click New and select Create JDBCStore from the list.

   3. In the Name field, type ORMJDBCStoreF.

   4. In the Target field, select ORMFinalizationServer.

   5. In the DataSource field, select ORM Data Source.

   6. In the Prefix Name field, type ORMF.

   7. Click OK.

10. Create a foreign server as follows:

    1. In the domain tree, select Services, Messaging, JMS Modules.

    2. Click ORM JMSModule and click New.

    3. Select Foreign Server and click Next.

    4. In the Name field, type FinalizationServer, click Next and then click Finish.

    5. Click FinalizationServer.

    6. In the JNDI Initial Context Factory field, type weblogic.jndi.WLInitialContextFactory.

    7. In the JNDI Connection URL field, type t3://machine_name:7074.

       Note:

       The machine_name is the name of the machine where ORMFinalizationServer is deployed. You must not use localhost as a machine name.

    8. Select Default Targeting Enabled and click Save.

    9. Click the Destinations tab and click New.

    10. In the Name field, type ORM FinalizationQueue.

    11. In the Local JNDI Name field, type orm/queue/BtFinisherQueue.

    12. In the Remote JNDI Name field, type orm/remote/queue/BtFinisherQueue and click OK.

    13. Click the Connection Factories tab and click New.

    14. In the Name field, type ORM Finalization ConnectionFactory.

    15. In the Local JNDI Name field, type orm/jms/FinalizationConFac.

    16. In the Remote JNDI Name field, type orm/remote/jms/FinalizationConFac and click OK.

4.3.2.7 Configuring Connection Factory

Configure the connection factory as follows:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMSModule.

3. Click ORM ConnectionFactory.

4. Deselect Default Targeting Enabled.

5. Click Save.

6. Click Subdeployment tab.

7. In the Subdeployment field, select cf-sub and click Save.

4.3.2.8 Setting the Target

Change the deployed applications (ORMServerApp and webui) to ORMCluster All servers in the cluster as target.

4.3.2.9 Ensuring the Default Target Enabled for Topics and Queues

Ensure that ORM IncomingEventQueue, ORM LoaderQueue, and ORM NotificationTopic have Default Targeting enabled by performing the following steps:

1. In the domain tree, select Services, Messaging, JMS Modules.

2. Click ORM JMSModule.

3. Click on ORM IncomingEventQueue.

4. Ensure that the Default Targeting Enabled is selected.

5. Click Save.

6. Repeat the same for ORM LoaderQueue and ORM Notification Topic.

4.3.2.10 Configuring SSL

Configure SSL for the admin server as follows:

1. In the domain tree, select Environment, Servers.

2. Click AdminServer(admin).

3. Click the SSL tab.

4. Click Advanced.

5. In the Hostname Verification field, select None.

6. Click Save.

Note:

You must shutdown all servers after performing the preceding step

4.3.2.11 Pack/unpack the Domain to Secondary Node

Note:

Ensure that all server node managers are running while performing the following steps.

1. On primary node, run the following command:

   >cd WLS_HOME/common/bin
   
   >pack.cmd -domain=$DOMAIN_HOME -template=/tmp/template_x.jar -template_name="template_x" -managed=true
   

2. Copy template_x.jar to secondary node.

   On secondary node, run the following command:

   >cd $WLS_HOME/common/bin
   
   >unpack.cmd -template=??/template_x.jar -domain=$DOMAIN_HOME
   
   

3. Note:

   Start ORMFinalizationServer before starting the Managed Server.

4.3.3 Configuring Apache Failover Proxy

To configure Apache failover proxy:

1. Install Apache HTTP server 2.2.

2. Download the WebLogic Apache plug-in from:

   http://www.oracle.com/technology/products/weblogic/index.html

3. Unzip and copy:

   win/mod_wl_22.so to apache_home/modules directory

4. Add the following to httpd.conf file by substituting the values for IP addresses and ports for your environment:

   LoadModule weblogic_module modules/mod_wl_22.so
   
    
   
   <IfModule mod_weblogic.c>
   
     WebLogicCluster node1_ip:port,node2_ip:port
   
   </IfModule>
   
    
   
   <Location /webui>
   
     SetHandler weblogic-handler
   
   </Location>
   
    
   
   <Location /ormconsole>
   
     SetHandler weblogic-handler
   
   </Location>
   

5. Restart Apache and all WebLogic servers.

You must be able to access webui and console at:

http://myApacheServer/webui

http://myApacheServer/ormconsole

For more information about installing and configuring the Apache HTTP Server Plug-In, refer to the following URL:

http://e-docs.bea.com/wls/docs103/plugins/apache.html