Overview

To summarize the procedures required for setting the GigaSpaces JMS (Real Time Data Bus) to work with the BEA WebLogic 8.1.3 ApplicationServer (AS) WorkShop MDB.

• We integrate the WL AS 8.1.3 with the GigaSpaces JMS using the WL Foreign JMS Server option. The GS JMS administrated objects can be bound on the WL lookup service (using the t3 protocol and the GS JMS External JNDI option), or they can be bound on the GS RMI Registry service, which is the preferred option.
• In order to enable the WL Foreign JMS to lookup the GS JMS Administrated Objects, define the same object name (used to bind on the RMI Registry), in the WL Consol in the appropriate Remote JNDI Name fields (see the screen shots below).

  While using this lookup option, you do not need to use the GS External JNDI operation nor add the weblogic.jar file to the JMS clients classpath.

• As a reference you can import the GSJMSExampleEAR.ear file as an example.
• Using the WL workshop server, define the following System Properties:
  • java.security.policy
  • com.gs.home
  • java.rmi.server.codebase

Updating startWebLogic.cmd in WebLogic AS

Add the GigaSpaces Security Policy file and the SecurityManager, with the policy.all, for example, <GigaSpaces Root Dir>/policy/policy.all.

-Djava.security.policy=%WL_HOME%\server\lib\policy.all:
-Djava.security.manager
-Djava.security.policy==%WL_HOME%\server\lib\policy.all.

Updating setDomainEnv.cmd in WebLogic AS

Update the classpath variable with the GigaSpaces jars:

• <GigaSpaces Root>\lib\JSpaces.jar.
• <GigaSpaces Root>\lib\jini\jsk-platform.jar.
• <GigaSpaces Root>\lib\jini\jsk-lib.jar.

For more details about setting the classpath, refer to the Setting Classpath section.

You can also update the classpath in the server WL Workshop Application Properties dialog, under Server Classpath Additions.

Starting WebLogic Server

In order to configure a new foreign JMS Server, open the WebLogic Server Console, from the Menu bar -> Tools -> WebLogic Server -> WebLogic Console (http://localhost:7001), login (using "weblogic" as the default username and password values) and perform the following steps:

Enter the username and password.

Configuring Foreign JMS Server in WebLogic AS

Update the following fields:

• Name: GSJMSServer.
• JNDI Initial Context Factory: com.sun.jndi.rmi.registry.RegistryContextFactory.
• JNDI Connection URL: rmi://localhost:10098 (define the host name and port of the GigaSpaces server).

Configuring Foreign JMS Connection Factories in WebLogic AS

For GSQueueConnectionFactoryImpl, update the following fields:

• Name: GSQueueConnectionFactoryImpl
• Local JNDI Name: GigaSpaces;<container name>;<space name>;GSQueueConnectionFactoryImpl
• Remote JNDI Name: GigaSpaces;<container name>;<space name>;GSQueueConnectionFactoryImpl

For GSTopicConnectionFactoryImpl, update the following fields:

• Name: GSTopicConnectionFactoryImpl
• Local JNDI Name: GigaSpaces;<container name>;<space name>;GSTopicConnectionFactoryImpl
• Remote JNDI Name: GigaSpaces;<container name>;<space name>;GSTopicConnectionFactoryImpl

Configuring Foreign JMS Destination in WebLogic AS

For a queue, update the following fields:

• Name: MyQueue.
• Local JNDI Name: GigaSpaces;<container name>;<space name>;jms;destinations;MyQueue.
• Remote JNDI Name: GigaSpaces;<container name>;<space name>jms;destinations;MyQueue.

For a Topic update the following fields:

• Name: MyTopic.
• Local JNDI Name: GigaSpaces;<container name>;<space name>;jms;destinations;MyTopic.
• Remote JNDI Name: GigaSpaces;<container name>;<space name>jms;destinations;MyTopic.

You can trace the JMS weblogic execution by adding the following verbose debug flags into setDomainEnv.cmd:

set verboseLoggingFlag=true

and into startWebLogic.cmd:

-Dweblogic.ejb.jms.connect.debug=true -Dweblogic.ejb.jms.connect.verbose=true

For more details, refer to the following links: bea; Simple Access to Remote or Foreign JMS Providers bea; Message-Driven EJBs bea;Table 7-3, weblogic-application.xml Elements for MDBs, Table 7-4 Key J2EE Deployment Elements for MDBs bea; Modifying the weblogic.policy file for General Use