Summary: Configuring a generic JMS server, destinations and connection factory; setting listener port; defining the custom property.
Overview
The steps below summarize the procedures required for setting the GigaSpaces JMS to work with the BEA WebLogic 8.1.3 Application Server (AS) WorkShop MDB:
- Integrate the IBM WSAD 5.1.3 with the GigaSpaces JMS by using the WSAD Generic JMS Provider option. GS JMS administrated objects must be bound on the GS RMI Registry service while the WSAD will look it up.
- To enable the WSAD Generic JMS Provider to look up the GS JMS Administrated Objects, define the same object name (used to bind on the RMI Registry), of the WSAD in the appropriate Remote JNDI Name fields.
 | While using this lookup option, you must neither use the GS External JNDI option, nor add the IBM jar files to the JMS client's classpath. |
- As a reference, import the GSJMSExampleEAR file, which is located inside the <GigaSpaces Root Dir>/examples/Messaging/MDB/IBMWSGenericJMSProvider_GS_JMS_MDB_example.zip.
- Using the IBM WSAD Server, you must define the following System Properties:
- java.security.policy
- com.gs.home
- java.rmi.server.codebase
- Make sure no jndi.properties file exists in the IBM WSAD classpath.
| For more details on IBM WSAD, refer to:
|
More in this Section
Previous release
Add GigaSpaces wiki search to your browser search engines! 