Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

Create JMS system modules

JMS resources are configured and stored as modules similar to standard J2EE modules. You can administratively configure and manage JMS modules as global system resources.

To create a JMS system module:

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the Administration Console, expand Services > Messaging and select JMS Modules.
  3. On the Summary of JMS Modules page, click New.

    Note: Once you create a module, you cannot rename it. Instead, you must delete it and create another one that uses the new name.

  4. On the Create JMS System Module page:
    1. In Name, enter a name for the JMS system module.
    2. In Descriptor File Name, optionally enter a name for module's underlying descriptor file. The system will automatically add a "-jms.xml" extension to this name. If you do not provide a name, a default name will be assigned.
    3. In Location in the Domain, optionally, enter where you want to place the descriptor for the system module. This location must be relative to the JMS configuration subdirectory of your domain, which is the config/jms subdirectory of the domain directory.
    4. Click Next to proceed to the targeting page.

    For more information about these fields see Configuration Options.

  5. On the Targets page, select the server instance or cluster target on which to deploy the JMS system module, and then click Next.
  6. On the Add Resources page, indicate whether you want to be able to immediately add resources to this JMS Module after it's created.
  7. Click Finish.

    If you chose not to continue adding resources, the JMS module creation is complete, and you are taken to the JMS Modules summary page where you can access the new module to edit it and add resources to it. However, if you chose to continue adding resources, then you are automatically taken to the JMS Modules: Configuration page where you can continue adding resources to the module.

  8. On the Configuration page, click New above the Summary of Resources table.
  9. On the Create a New JMS System Module Resource page, select one of the following JMS system resources:
    • Quota - controls the allotment of system resources available to destinations.
    • Template - provides an efficient means of defining multiple queues and topics with similar configuration settings.
    • Destination Key - defines a sort order for the messages as they arrive on destinations.
    • Topic - defines a publish/subscribe (pub/sub) destination, which enables an application to send a message to multiple applications.
    • Queue - defines a point-to-point (PTP) destination, which enables one application to send a message to another.
    • Connection Factory - defines a set of connection configuration parameters that enable JMS clients to create JMS connections.
    • Distributed Topic - a single set of JMS topics that are accessible as a single, logical topic to a client. The members of the distributed topic are usually distributed across multiple servers within a cluster, with each topic member belonging to a separate JMS server.
    • Distributed Queue - a single set of JMS queues that are accessible as a single, logical topic to a client. The members of the distributed queue are usually distributed across multiple servers within a cluster, with each topic member belonging to a separate JMS server.
    • Foreign Server - represents a third-party JMS provider that is outside WebLogic Server. It contains information that allows a local server instance to reach a remote JNDI provider, thereby allowing for a number of foreign connection factory and destination objects to be defined on one JNDI directory.
    • SAF Imported Destination - defines a collection of imported SAF (store-and-forward) queues or topics that represent JMS destinations in a remote server instance or cluster.
    • Remote SAF Context - specifies the login context that SAF imported destinations use to connect to a remote destination.
    • SAF Error Handling - specifies the action to be taken when the SAF service fails to forward messages to a remote destination.
  10. Click Next.

    Depending on the type of resource you select, you will be prompted to enter basic information to create the resource.

  11. Enter the required information for the selected resource:
    • For Topic, Queue, Connection Factory, Distributed Topic, Distributed Queue, Foreign Server, and SAF Imported Destination resources, you can optionally click Next to select or configure an appropriate subdeployment. A subdeployment is the mechanism by which targetable JMS module resources (such as queues, topics, and connection factories) are grouped and targeted to a server resource (such as JMS servers, server instances, or cluster). Click Finish to complete the configuration with basic default values.
    • For Quota, Template, Destination Key, SAF Remote Context, and SAF Error Handling resources, simply click OK to complete the configuration with basic default values.

    Note: Most JMS resource have additional parameters that can be modified after they are created. For example, you modify the default message threshold values or enable message logging for queues, topics, and templates.

  12. On the Configuration page, you can either:
    • Configure subdeployments, security, or notes for the system module.
    • Click a configured JMS resource the in Summary of Resources table to modify its default values.
    • Click New again to add another JMS resource to the module.
  13. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).


Skip navigation bar   Back to Top