...
- Download, set up, and start Oracle WebLogic Server.
- Start WSO2 ESB.
- Wrap the weblogic client jar and build a new OSGi bundle using the following pom.xml. The exporting of
javax.jmspackage andjavax.xml.namespacepackage of the client jar should be prevented. - Copy the client libraries file
wlthint3client.jarfrom the<WEBLOGIC_HOME>/wlserver/server/libdirectory to the<ESB_HOME>/repository/components/dropinsdirectory.
Configuring the WebLogic server
Configure the required connection factories and queues in WebLogic. An entry for a JMS queue would look like the following. The configuration files can be found in configuration inside <WEBLOGIC_HOME>/user_projects/domains/<DOMAIN_NAME>/config/jms/.Alternatively you can configure using the weblogic web console which can be accessed through http://localhost:7001 with default configurations.be as follows:
| Code Block | ||
|---|---|---|
| ||
<queue name="wso2MessageQueue">
<sub-deployment-name>jms</sub-deployment-name>
<jndi-name>jms/wso2MessageQueue</jndi-name>
</queue> |
<WEBLOGIC_HOME>/user_projects/domains/<DOMAIN_NAME>/config/jms/ directory. Alternatively, you can configure using the weblogic web console, which can be accessed via http://localhost:7001 with default configurations.Once you start the WebLogic server with the above changes, you 'll be able to will see the following on STDOUT.
| Code Block |
|---|
<Jun 25, 2013 11:20:02 AM IST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "wso2" running in Development Mode> <Jun 25, 2013 11:20:02 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING> <Jun 25, 2013 11:20:02 AM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode> |
You will now need to configure the transport listener, sender, and message store in WSO2 ESB. For details on JMS configuration parameters used in the code segments, see JMS Connection Factory Parameters.
...