Installation Guide for Oracle Self-Service E-Billing > Configuring Oracle WebLogic > Process of Configuring Oracle WebLogic for the Command Center Application >
Configuring JMS Resources for the Command Center on Oracle WebLogic
You must configure the following JMS resources for the Command Center:
- JMS persistence store
- JMS servers
- JMS module and connection factory
- JMS queues
This task is a step in Process of Configuring Oracle WebLogic for the Command Center Application. Configuring a JMS Persistence Store for the Command Center
You must configure a JMS persistence store for the Command Center. To configure a JMS persistence store
- Select Services, Persistence Stores.
- Select New, Create File Store. Create a file store with the following values.
|
|
|
LoggerFileStore |
Select Your Server (AdminServer) |
Directory Location to Save Store (such as WL_HOME/user_projects/domains/commandcenter_domain/config/FileStore ) |
EventFileStore |
Select Your Server (AdminServer) |
Directory Location to Save Store |
Configuring a JMS Server
You must set up a JMS server for the Command Center. To configure a JMS server
- Select Services, Messaging, JMS Servers, and New. Create one JMS Server, using the following values.
|
|
|
LoggerJMSServer |
LoggerFileStore |
Select Your Server (AdminServer) |
EventJMSServer |
EventFileStore |
Select Your Server (AdminServer) |
Creating the JMS Module and Connection Factory for the Command Center
You must create a JMS module and add a JMS connection factory to the module for the Command Center. To create the JMS module and connection factory
- Click Services, Messaging, and the JMS Modules link on the Administration Console page for the Command Center domain.
- Click New to create a new JMS Module. Set the name of the JMS system Module, and provide the JMS Module properties. Click Next.
|
|
|
Name |
Your JMS Module Name |
CC_JMSFactories |
Descriptor File Name |
Your Descriptor File Name |
CC_JMSFactories |
Location in Domain |
Your Location in Domain |
CC_JMSFactories |
Targets |
Select Your Server |
AdminServer |
- Select the check boxes to target the system Module at the servers running the Command Center application, click Next, and then click Finish.
- Click the JMS Modules link on the Administration Console page for the Command Center domain.
- Click the link for the module you created in the previous procedure.
- Click New, select Connection Factory, and then click Next.
- Add one Connection Factory, using the following parameters. Click Finish.
|
|
|
|
Connection Factory |
LoggerConnectionFactory |
edx.lcf |
Select Your Server (AdminServer) |
Connection Factory |
EventConnectionFactory |
edx.qcf |
Select Your Server (AdminServer) |
- Click on the new connection factory, and select XA Transaction on the Transactions tab.
Configuring a JMS Queue for the Command Center
You must create two JMS queues for the Command Center application. To create the JMS queues
- Click the JMS Modules link on the Administration Console page for the Command Center domain.
- Click the link for the module you created. Click New, select Queue, and then click Next.
- Provide the Queue Name and the JNDI Name as shown in the following table. Click Next.
|
|
|
LoggerQueue |
edx.queue.logger |
LoggerJMSServer |
EventQueue |
edx.queue.outbound |
EventJMSServer |
- Click Create a New Subdeployment. Oracle WebLogic shows the newly created queue name as Subdeployment Name.
- Accept the name, then click OK. If you plan to add more JMS resources to the subdeployment, then you can rename it. Select the new subdeployment and the corresponding target JMS Server.
- Click Activate Changes to save changes after the JMS configuration is complete.
|