Skip Navigation Links | |
Exit Print View | |
Deploying Oracle Java CAPS JMSJCA on WebLogic Java CAPS Documentation |
1. Deploying JMSJCA on WebLogic
Perform the following tasks to deploy JMSJCA to a WebLogic Server:
You can create this project using Oracle SOA Suite, for example.
http://hostname:port/console
This lets you make changes using the Administration Console, and modify, add or delete items in the domain.
Note - Release Configuration in the Change Center allows others to edit the domain and ensures no pending changes exist.
The standalone application modules and Java EE applications are listed.
Follow this path to deploy sun-jms-adapter.rar on WebLogic 10.
root\JavaCAPS_Home\appserver\addons\caps\common\jmsjca
Tip - Use the Next and Forward buttons to navigate forward and backwards during installation.
The targets can be a server, clusters of servers and virtual hosts on which this deployment will function. Choose one of the following targets:
Install this deployment as an application
Install this deployment as a library
Install this deployment as an application is the default deployment method.
In the current example, it is sun-jms-adapter. By default, the name of the deployment is specified.
Use the defaults defined by the deployment's targets
Copy this application onto every target for me
I will make the deployment accessible from the following location
Location: root\JavaCAPS_Home\appserver\addons\caps\common\jmsjca\sun-jms-adapter.rar
Use the defaults defined by the deployment's targets is the default selection.
Note - Make the required changes to the Console and click Save.
The following message appears on the right panel of the screen.
All changes have been activated. No restarts are necessary
See Also
Some changes you make in the Administration Console take place immediately when you activate them. Other changes require you to restart the server or module affected by the change. Such changes are called non-dynamic changes. Non-dynamic changes are indicated in the Administration Console.
Note - If you edit a non-dynamic configuration setting, no edits to dynamic configuration settings will take effect until the server is restarted.
Note - The state of the deployed application changes from the Active state to the Prepared state.
This selection defaults to the Outbound Connection Pools tab.
You can create an instance for the resource adapter to display the Outbound Connection Groups.
javax.jms.ConnectionFactory
javax.jms.QueueConnectionFactory
javax.jms.TopicConnectionFactory
For example, SunMQConnectionPool, SunSTCMSConnectionPool, or SunJMSGridConnection Pool.
Note - This field is mandatory.
The Save Deployment Plan page appears. 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
The following message appears on the right panel of the screen.
All changes have been activated. No restarts are necessary
The selection defaults to the Outbound Connection Pools tab.
Provide the Password and UserName to connect to JMQ.
Note - The default Password is guest and the default UserName is guest.
Provide the Password and UserName to connect to JMQ.
Note - The default Password is adminadmin and the default UserName is admin.
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.
imq.jar (for JMQ)
Note - For example, copy the JAR file from JavaCAPS_Home\appserver\imq\lib\imq.jar to WebLogic_Home\server\lib. This establishes communication with the JMQ provider
wave.jar (for SunJMSGrid)
com.stc.jms.stcjms.jar (JMS IQ Manager)
As Weblogic 9.2 doesn't support editing a URL in Outbound Connection Properties, the XML file must be edited accordingly.