WebLogic Server 8.1 Service Pack 4

WebLogic Server 8.1 Service Pack 4

Configuring JMS for WebLogic Server 8.1

To configure the JMS topics, go through the following steps:

1. Using an Internet browser, go to WebLogic's console (for example http://localhost:7001/console) and login.

2. On the left panel, navigate to Services > JMS > Connection Factories.

3. On the right panel, select Configure a new JMS Connection Factory.

4. Enter a Name (for example, ConnectionFactory) and a JNDI name (for example, ConnectionFactory), and then click Create.

5. Select a server as the target and click Apply.

6. On the left panel, navigate to Services > JMS > Servers > WSStoreForwardInternalJMSServermyserver > Destinations (where myserver is the name of your server).

7. On the right panel, select Configure a new JMS Topic.

8. Enter icefaces.contextEventTopic for both the Name and JNDI name, and then click Create.

9. Repeat steps 6 to 8 for icefaces.responseTopic.

For more information on how to configure JMS on WebLogic, refer to JMS: Configuring which can be found at:

http://e-docs.bea.com/wls/docs81/ConsoleHelp/jms_config.html

Web Server Plug-Ins

Plug-ins are modules that can be added to a web server installation and can be configured to enable interaction between the web server of choice and the application server of choice. Typically, plug-ins can be used as a load-balancer for the web server by proxying the requests to the back-end application servers, or can be used to proxy requests for dynamic content to the back-end server(s).

Apache HTTP Server 2.0.x

The following is a simple solution for installing and configuring WebLogic's plug-in for the Apache HTTP Server.

1. First, copy the mod_wl_20.so module supplied by BEA into the Apache's /module directory. You can obtain the mod_wl_20.so module from WebLogic's installation from this directory:
[bea home dir]/weblogic81/server/lib/[os]/

2. Create a new file called mod_wl_20.conf in the Apache's /conf directory and add the following code to it:
 
LoadModule weblogic_module modules/mod_wl_20.so
 

 
<IfModule mod_weblogic.c>
 
    WebLogicHost host
 
    WebLogicPort port
 
</IfModule>
 

 
<LocationMatch ^/application-name(?!/block/receive-updated-views)>
 
    SetHandler weblogic-handler
 
</LocationMatch>
 

 
The LocationMatch container is responsible for forwarding all the requests to the ICEfaces application deployed to WebLogic with the exception of the blocking requests. To explain the regular expression used in the LocationMatch container, the following is a breakdown:

^/application-name
if the location begins with (^) the literal string "/application-name", where
application-name is the name of the ICEfaces application, and
(?!/block/receive-updated-views)
is not followed by (?!) the literal string "/block/receive-updated-views".

This regular expression ensures that the following possible locations get handled by the plug-in:

/application-name (initial request)
/application-name/ (initial request)
/application-name/xmlhttp/icefaces-d2d.js (part of initial request)
/application-name/block/receive-send-updates?<query> (synchronous request)
/application-name/block/send-updates?<query> (UI request)

But it prevents that the following possible location gets handled by the plug-in:

/application-name/block/receive-updated-views?<query> (asynchronous request)

3. The mod_wl_20.conf file needs to be loaded. To achieve this, add the following to Apache's configuration file right after the LoadModule directives:
Include conf/mod_wl_20.conf
 
4. Finally, the ProxyPass and ProxyPassReverse directives, which route all requests other than the blocking requests to the application server, need to be removed from the Apache configuration file.

For more information on how to install and configure WebLogic's plug-ins, refer to BEA WebLogic Server - Using Web Server Plug-Ins with WebLogic Server, which can be found at:

http://e-docs.bea.com/wls/docs81/pdf/plugins.pdf

Apache HTTP Server 2.2.x

BEA plans to have a plug-in for Apache HTTP Server 2.2.x available with the WebLogic Server 8.1 SP 7 and 9.5 releases.

Clustering

This section explains how to set up a clustered deployment of WebLogic Servers. It includes steps for configuring the cluster, JMS and the web server. The following discussion relates to a clean installation of WebLogic Server, and represents a simplified process for configuring WebLogic for clustered deployments of ICEfaces applications. Additional deployment-specific issues may exist. Refer to your WebLogic documentation for additional information.

This example cluster consists of two Managed Servers and an Administration Server, which itself is not part of the cluster, as shown in the table below.

IP Address

Server Name

Description

192.168.1.100

Admin

Administration Server

192.168.1.101

Managed1

Managed Server

192.168.1.102

Managed2

Managed Server

Configuring the Cluster

Ensure that you have WebLogic Server installed on each machine. Refer to your WebLogic documentation for additional information.

The following three procedures describe the steps to create a cluster formed by Managed1_Server and Managed2_Server and administered by Admin_Server.

Configuring the Individual Servers

1. On machine Admin go to [bea-home-dir]/weblogic81/common/bin and start the BEA WebLogic Configuration Wizard using:
./config.sh -mode=console
 

 
Use config.cmd on a Windows platform.

2. Select Create a new WebLogic configuration.

3. Select Basic WebLogic Server Domain.

4. Do not run in express mode; select No.

5. Modify the Name of the Administration Server to Admin_Server and select Next.

6. Do not configure the Managed Servers, Clusters and Machines; select No.

7. Do not configure JDBC; select No.

8. Do not configure JMS; select No.

9. Do not configure Advanced Security; select No.

10. Modify the user as desired and select Next.

11. Select Production Mode.

12. Select JRockit SDK version 1.4.2.

13. Leave the Target Location at its default.

14. Modify the Name of the domain to ICEfaces_Cluster_Domain and select Next.

15. Repeat steps 1 to 14 for Managed1_Server on Managed1 and Managed2_Server on Managed2.

Configuring the Cluster

1. On machine Admin go to
[bea-home-dir]/user_projects/domains/ICEfaces_Cluster_Domain
and start the server using:
./startWebLogic.sh
 

 
Use startWebLogic.cmd on a Windows platform.

2. Using an Internet browser, go to http://192.168.1.100:7001/console and login as the user specified in step 10 of Configuring the Individual Servers.

3. On the left panel, navigate to Clusters.

4. On the right panel, select Configure a new Cluster.

5. Enter ICEfaces_Cluster for Name and then click Create.

6. On the left panel, navigate to Machines.

7. On the right panel, select Configure a new Machine.

8. Enter Managed1 for Name and then click Create.

9. Repeat steps 6 to 8 for Managed2.

10. On the left panel, navigate to Servers.

11. On the right panel, select Configure a new Server.

12. Enter Managed1_Server for Name, select Managed1 for Machine and ICEfaces_Cluster for Cluster; enter 192.168.1.101 in the Listen Address field, and then click Create.

13. Repeat steps 10 to 12 for Managed2_Server running on Managed2 (192.168.1.102).

Starting the Cluster

1. On machine Managed1 go to
[bea-home-dir]/user_projects/domains/ICEfaces_Cluster_Domain
and start the server using the following command:
./startManagedWebLogic.sh Managed1_Server http://192.168.1.100:7001
 

 
2. Use startManagedWebLogic.cmd on a Windows platform.

3. Repeat step 1 for Managed2_Server.

4. Using an Internet browser, go to http://192.168.1.100:7001/console and login.

5. On the left panel, navigate to Servers.

6. On the right panel, verify that all servers (Admin_Server, Managed1_Server and Managed2_Server) have their state set as RUNNING.

Configuring JMS for the Cluster

The following steps describe how to create a ConnectionFactory that is available throughout the cluster and an ICEfaces_JMS_Server deployed on Managed1 servicing the JMS topics, icefaces.contextEventTopic, icefaces.renderTopic, and icefaces.responseTopic, throughout the cluster.

1. Using an Internet browser, go to http://192.168.1.100:7001/console and login.

2. On the left panel, navigate to Services > JMS > Connection Factories.

3. On the right panel, select Configure a new JMS Connection Factory.

4. Enter ConnectionFactory for Name and JNDI Name, and then click Create.

5. Select All servers in the cluster for Targets and then click Apply.

6. On the left panel, navigate to Services > JMS > Servers.

7. On the right panel, select Configure a new JMS Server.

8. Enter ICEfaces_JMS_Server for Name and then click Create.

9. Select Managed1_Server for Target and then click Apply.

10. On the left panel, navigate to Services > JMS > Servers > ICEfaces_JMS_Server > Destinations.

11. On the right panel, select Configure a new JMS Topic.

12. Enter icefaces.contextEventTopic for Name and JNDI Name, select False for Enable Store, and then click Create.

13. Repeat steps 10 to 12 for icefaces.renderTopic and icefaces.responseTopic.

Web Server Plug-Ins

Apache HTTP Server 2.0.x

The following is a simple solution for installing and configuring WebLogic's plug-in for Apache 2.0.x and a cluster of WebLogic Servers. Refer to the previous Apache HTTP Server 2.0.x section for the initial installation and configuration of WebLogic's plug-in for Apache 2.0.x.

1. The contents of the file mod_wl_20.conf, created in step 1 of the previous Apache HTTP Server 2.0.x section, should be changed to the following:
 
LoadModule weblogic_module modules/mod_wl_20.so
 

 
<IfModule mod_weblogic.c>
 
    WebLogicCluster 192.168.1.101:7001,192.168.1.102:7001
 
</IfModule>
 

 
<LocationMatch ^/application-name(?!/block/receive-updated-views)>
 
    SetHandler weblogic-handler
 
</LocationMatch>
 
Apache HTTP Server 2.2.x

BEA is planning to have a plug-in for Apache HTTP Server 2.2.x available with the releases of WebLogic Server 8.1 SP 7 and 9.5.

IP Address	Server Name	Description
192.168.1.100	Admin	Administration Server
192.168.1.101	Managed1	Managed Server
192.168.1.102	Managed2	Managed Server