OTN Home > Oracle WebLogic Server 10.3.6.0 Documentation > Administration Console Online Help > Create JMS servers

Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Create JMS servers


JMS servers are environment-related configuration entities that act as management containers for JMS queue and topic destinations in JMS modules that are targeted to them. Multiple JMS modules can be targeted to each JMS server in a domain.

To create a JMS server:

  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 Servers.
  3. On the Summary of JMS Servers page, click New.

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

  4. On the Create a JMS Server page:
    1. In Name, enter a name for the JMS server.
    2. In Persistent Store, select a pre-configured custom file or JDBC store that will be used by the JMS server or click the Create a New Store button to create a store on the fly. If you leave this field set to none, then the JMS server will use the default file store that is automatically configured on each targeted server instance. For more information about configuring stores, see Configure custom persistent stores.

      Note: When a JMS server is targeted to a migratable target, it cannot use the default store, so a custom store must be configured and targeted to the same migratable target.

    3. Click Next to proceed to the targeting page.
  5. On the Select Targets page, select the server instance or migratable server target on which to deploy the JMS server. Migratable targets define a set of WebLogic Server instances in a cluster that can potentially host a pinned service, such as a JMS server.

    Note: In a clustered server environment, a recommended best practice is to target a JMS server to a migratable target, so that a member server will not be a single point of failure. A JMS server can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services.

  6. Click Finish.
  7. On the Summary of JMS Servers page, click the new JMS server to open it.

    Note that there are many optional parameters that can be set on the JMS server configuration tabs, including General configuration parameters, Thresholds and Quotas, Logging, and Server Session Pools. For more information about configuring these parameters, see Configure JMS servers.

  8. After modifying any values, click Save.
  9. 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).

Back to Top