test

Deploying JMSJCA on WebLogic

ProcedureTo Create a JNDI Name for the Respective JMS Provider

  1. Click on Lock & Edit in the Change Center to modify the settings for the sun-jms-adapter.

  2. Click Deployments from the Domain tree structure and navigate to the sun-jms-adapter.

    Note –

    The state of the deployed application changes from Active state to Prepared state.

  3. Click on sun-jms-adapter.

  4. On the Settings for sun-jms-adapter page, click the Configuration- Tab. This selection defaults to the Outbound Connection Pools tab.

  5. Click New from the Outbound Connection Pool Configuration Table. You can create an instance for the resource adapter to display the Outbound Connection Groups.

  6. Choose any one of the following Outbound Connection Groups to create an instance.

    • javax.jms.ConnectionFactory

    • javax.jms.QueueConnectionFactory

    • javax.jms.TopicConnectionFactory

      Select javax.jms.QueueConnectionFactory from the group and click Next.

  7. On the Create a New Outbound Connection page, enter the JNDI name that is needed to obtain the new connection instance.

    For example, the JNDI Name can be either SunMQConnectionPool or SunSTCMSConnectionPool or SunJMSGridConnection Pool.

    In the current example, enter the JNDI Name as SunMQConnectionPool. Click Finish.

    Note –

    This field is mandatory.

    This displays the Save Deployment Plan page. You can save the new deployment plan on this page, if the configuration has changed. Select a directory to receive these files (for example, select jmsjca) and click Finish.

    A confirmation message appears on the right panel of the screen.


    A new deployment plan has been successfully created in root\JavaCAPs6\appserver\addons\
caps\common\jmsjca\Plan.xml

  8. Click on Activate Changes in the Change Center.

    The following message appears on the right panel of the screen.


    All changes have been activated. No restarts are necessary

  9. Click on Lock & Edit in the Change Center to modify the settings for the sun-jms-adapter.

  10. Click Deployments from the Domain tree structure and navigate to the sun-jms-adapter.

  11. Click on sun-jms-adapter.

  12. On the Settings for sun-jms-adapter page, click on the Configuration- Tab. The selection defaults to the Outbound Connection Pools tab.

  13. Expand the javax.jms.QueueConnectionFactory in the Outbound Connection Pool Configuration Table to see the newly created JNDI.

    In the current example, it is SunMQConnectionPool

  14. Click on SunMQConnectionPool.

  15. On the Settings for SunMQConnectionPool page, set the following list of parameters with specified values in Outbound Connection Properties table (that is, fill values according to the message provider),

    1. Set the Property Value for the JMQ ConnectionURL property as mq://host:port|7676/jms

      Provide the Password and UserName to connect to JMQ.

      Note –

      The default Password is guest and the default UserName is guest.

    2. Set the Property Value for the STCMS ConnectionURL property as stcms://host:port|18007

      Provide the Password and UserName to connect to JMQ.

      Note –

      The default Password is adminadmin and the default UserName is admin.

    3. Set the Property Value for the ConnectionURL property as tcp://host:port|50607

      Provide the Password and UserName to connect to JMQ.

      Note –

      The default Password is admin and the default UserName is admin.

      The following message appears on the right panel of the screen after completing the above steps.


      Deployment plan has been successfully updated
      Note –

      Provide the same UserName and Password as defined in the Optional Settings screen.

      Click Save after every entry.

      This completes setting the properties for the Connector Outbound Connection Configuration Properties table.

  16. Follow the Deployments link and update the properties for the sun-jms-adapter. Activate the changes on the WebLogic Server Administration Console.

  17. Place the following .jar files in the weblogic lib directory based on the selected message provider

    1. imq.jar (for SunJMQ)

      Note –

      For example, place the .jar file from the following class path root:\JavaCAPS6\appserver\imq\lib\imq.jar to root:\bea\wlserver_10.0\server\lib which is now available for WebLogic. This establishes communication with the SunJMQ provider

    2. wave.jar (for SunJMSGrid)

    3. com.stc.jms.stcjms.jar (JMS IQ Manager)

  18. Restart the Weblogic Appserver.

  19. Execute the non-caps Application. Send a message to a particular configured message provider.

On WebLogic

As Weblogic 9.2 doesn't support editing an URL (that is, In Outbound Connection Properties), the XML file has to be edited accordingly.