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 Connection Factories
  • 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

  1. Select Services, Persistence Stores.
  2. Select New, Create File Store. Create a file store with the following values.
    Name
    Target
    Directory

    LoggerFileStore

    Select Your Server (AdminServer)

    Directory Location to Save Store (such as $WEBLOGIC_HOME/user_projects/domains/commandcenter_domain/config/FileStore)

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.
    Name
    Persistent Store
    Target

    LoggerJMSServer

    LoggerFileStore

    Select Your Server (AdminServer)

Configuring JMS Connection Factories for Command Center

To create JMS Connection Factories you must first create the Module.

To create the JMS Module

  1. Click Services, Messaging, and the JMS Modules link on the Administration Console page for the Command Center domain. Click Lock and Edit to allow configuration changes to be made.
  2. Click New to create a new JMS Module. Set the name of the JMS system Module, and provide the JMS Module properties. Click Next.
    Property
    Description
    Example

    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

  3. Select the check boxes to target the system Module at the servers running the Command Center application, click Next, and then click Finish.

Once you have created the Module you can add a factory to the new module.

To create a JMS Connection Factory

  1. Click the JMS Modules link on the Administration Console page for the Command Center domain. Click Lock and Edit to allow configuration changes to be made.
  2. Click the link for the module you created in the previous procedure.
  3. Click New, select Connection Factory, and then click Next.
  4. Add one Connection Factories using the following parameters. Click Finish.
    Connection Factory Type
    Name
    JNDI Name
    Target

    Connection Factory

    LoggerConnectionFactory

    edx.lcf

    Select Your Server (AdminServer)

  5. Click on the new connection factory, and select XA Transaction on the Transactions tab.

You must set up a JMS queue for the Command Center.

Configuring a JMS Queue for the Command Center

You must create a JMS Queue for the Command Center application.

To add the JMS Queue Destination

  1. Click the JMS Modules link on the Administration Console page for the Command Center domain. Click Lock and Edit to allow configuration changes to be made.
  2. Click the link for the module you created. Click New, select Queue, and then click Next.
  3. Provide the Queue Name and the JNDI Name as shown in the following table. Click Next.
    Name
    JNDI Name
    Target

    LoggerQueue

    edx.queue.logger

    LoggerJMSServer

  4. Click Create a New Subdeployment. Oracle WebLogic shows the newly created queue name as Subdeployment Name.
  5. Accept the name, then click OK. If you plan to add more JMS resources into the subdeployment, you can rename it. Select the newly created Subdeployment and the corresponding target JMS Server.
  6. Click Activate Changes to commit changes after the JMS configuration is complete.
Installation Guide for Oracle Self-Service E-Billing Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices.