Creating WebLogic Configurations Using the Configuration Wizard
WebLogic JMS gives you access to enterprise messaging systems that make it possible for applications to communicate with one another. To familiarize yourself with the features of WebLogic JMS, see Programming WebLogic JMS at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/index.html
The wizard gives you the option of configuring a JMS messaging service. To configure JMS, define the following components:
The Messaging (JMS) Options window prompts you to configure WebLogic Java Message Service (JMS). If you select No, the wizard uses settings for your JMS configuration exactly as defined in the configuration source that you selected earlier. If you select Yes, you are prompted, in subsequent windows, to define the configuration as described in the following table.
Note: If you are creating an extension template using the Configuration Template Builder and you select No, the next step in your procedure is to set up security for your application. See Configuring Security Options in Your Extension Template.
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
A connection factory object encapsulates connection configuration information, and enables JMS applications to create connections.
The Configure JMS Connection Factories window prompts you to create JMS connection factories. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a valid name for a JMS connection factory: a string of characters that can include spaces. The default value for this field is |
|
Enter a valid pathname to be used to look up the connection factory within the JNDI namespace. |
|
From the drop-down list, select a default delivery mode to be used for messages for which a delivery mode is not explicitly defined. The following default delivery modes are available:
For more information, see "Message Persistence" in Programming WebLogic JMS at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/fund.html#fund004 |
|
Enter a default priority to be used for messages for which a priority is not explicitly defined. Any numeric value between 0 and 9 is valid, with 0 specifying the lowest priority: |
|
From the drop-down list, specify an acknowledge policy to be used for non-transacted sessions run in
For more information, see "Non-transacted Session" in Programming WebLogic JMS at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/fund.html#nontransacted |
"Connection Factory Object" in Programming WebLogic JMS at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/fund.html#jms_connection_factory
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
Destination keys are used to define the sort order for messages that arrive on a specific destination.
The Configure JMS Destination Key(s) window prompts you to configure JMS destination keys. In subsequent windows, you can create JMS templates and, if you like, assign these destination keys to JMS templates. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
A JMS template provides an efficient means of defining multiple destinations with similar attribute settings. When you use JMS templates, you can take advantage of the following benefits:
The Configure JMS Template(s) window prompts you to configure JMS templates. This step is optional.
Note: Default values may vary, based on the configuration source you selected earlier. To toggle the display mode for the list of templates between table and tab formats, click Switch Display.
Enter a valid name for the JMS template: a string of characters that can include spaces.
The default for this field is new_JMSTemplate_
n
, where n
specifies a numeric value that is used to differentiate among all default JMS template names; the value of n
for the first JMS template is 1. The value is incremented by 1 for each template that is added.
Configuring JMS Destination Keys
Assigning JMS Destination Keys
"JMS Template Tasks" in the WebLogic Server Administration Console Online Help at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/jms_config.html#jms_template_create
The JMS Destination Key Assignment window prompts you to assign destination keys to a template. This window is displayed only if you have defined JMS destination keys and one or more JMS templates. This step is optional.
Configuring JMS Destination Keys
A JMS file store is a disk-based file in which persistent messages can be saved.
The Configure JMS File Stores window prompts you to configure JMS file stores as required for your configuration. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a name for the JMS file store: a string of characters that can include spaces. The name of the JMS file store must be unique among all configuration component names within the domain. The default value for this field is |
|
Enter the pathname of the directory on the file system where the JMS file store is kept. This directory must reside on your system. Alternatively, you can click in this field to enable the Browse button to navigate to the directory on the file system where the JMS file store is kept. If such a directory does not exist, enter the pathname for one in the Location field. In this case, you are prompted to indicate whether you want to have this type of directory created for you. |
|
From the drop-down list, select one of the following synchronous write policies to determine how the file store writes data to disk:
This parameter setting affects performance, scalability, and reliability. Note: If the JMS file store is used exclusively for paging non-persistent messages to disk, the synchronous write policy is ignored. For more information, see "Improving JMS File Store Performance" in the WebLogic Server Administration Console Online Help at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/ |
A JMS JDBC store is a JDBC-accessible database used to save persistent messages. A JMS connection factory is required for creating a JMS JDBC store.
The Configure JMS JDBC Store window prompts you to create JMS JDBC stores as required for your configuration. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a valid name for the JMS JDBC store: a string of characters that can include spaces. The name of the JMS JDBC store must be unique among all configuration component names within the domain. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
From the drop-down list, select a valid JDBC connection pool for this persistent store. Note: Only connection pools that use non-XA drivers are supported. If you are using a template that specifies a connection pool with a non-XA driver as a JMS JDBC store, and you change the driver to an XA driver, the JMS JDBC store is invalid and the connection pool is not available in the drop-down list. |
|
Enter a prefix name that uniquely identifies JMS tables in the backing store. Any continuous string of characters may be used as a valid name; spaces within names are not supported. By specifying unique prefixes you can enable multiple stores to reside in the same database. Such prefixes are prepended to table names when:
When prepended to a JMS table name, a prefix specified in the following format will result in a valid table name: |
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
A JMS server manages connections and message requests on behalf of clients.
The Configure JMS Servers window prompts you to create JMS servers as required for your configuration. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a valid JMS server name: a string of characters that can include spaces. The name of the JMS server must be unique among all configuration component names within the domain. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
From the drop-down list, select one of the following for the JMS server: A persistent store or JDBC store may be used by only one JMS server. A value of |
|
From the drop-down list, select a valid JMS paging store for the JMS server or Each JMS server must have its own paging store, which is used exclusively for paging out non-persistent messages for the JMS server and its destinations. Before you can select a paging store, you must first configure a JMS file store to be used exclusively as a paging store. The selected paging store cannot be any of the following: a) the same as the selected non-paging store; b) the same store used by any other JMS server; or c) a JMS JDBC store. Note: By default, message paging is disabled. However, a message paging store is created automatically when either bytes paging or messages paging is enabled on the JMS server or destinations of the JMS server and a message paging store is not already configured. For more information, see "Paging Out Messages to Free Up Memory" in the WebLogic Server Administration Console Online Help.To access this document, select the help icon from the Administration Console interface or go to: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/ |
|
Note: This field refers to a JMS template, not a configuration or extension template. |
From the drop-down list, select an existing JMS template to be used for the creation of temporary queues and topics for this JMS server. When a value is specified for this field, JMS applications can create temporary destinations. The attribute values for a temporary destination are derived from this JMS template. If provided as part of the template, the Store attribute values are ignored because temporary destinations do not support persistent messaging. If this attribute is set to none, attempts to create a temporary destination (queue or topic) fail. |
Enter the amount of time, in seconds, that you want the JMS server to pause between its cycles of scanning its destinations for expired messages to process (according to the specified Expiration Policy for the destinations). A value of 0 indicates that active scanning is disabled: expired messages are passively removed as they are discovered. The default value in this field is 30. For guidelines on setting this value, see the JMS server configuration information in the WebLogic Server Administration Console Online Help. To access this information, select the help icon from the Administration Console interface or go to: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/ConsoleHelp/ |
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
The Assign JMS Servers to WebLogic Servers window prompts you to assign the JMS servers to WebLogic Server instances. This window is displayed only if you have defined one or more JMS servers.
The name of the JMS server is removed from the JMS Server pane and added, below the name of the target WebLogic Server instance, in the Server pane.
If necessary, you can remove a JMS server from a WebLogic Server instance in one of the following ways:
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
JMS topics support the publish/subscribe (pub/sub) messaging model, which enables an application to send a message to multiple applications. Pub/sub messaging applications send and receive messages by subscribing to a topic.
The Configure JMS Topics window prompts you to configure JMS topics required for your configuration.This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
If multiple JMS Servers are defined, the wizard displays the JMS topics for each JMS Server on a separate tab. To view a particular JMS Server, you select the corresponding tab.
Enter a valid name for the JMS topic: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
Enter a valid JNDI pathname to be used to look up the topic within the JNDI namespace. The JNDI name must be unique among all JMS servers defined for the WebLogic Server instance. |
|
From the drop-down list, select a flag to specify whether or not the destination uses the persistent store specified by the JMS server. If the If the If the If |
|
Note: This field refers to a JMS template, not a configuration or extension template. |
From the drop-down list, select a valid JMS template from which the destination is to be derived. If a template is not defined ( Attributes that are set to default values inherit their destination values from the JMS template at run time. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination. |
"Messaging Models" in Programming WebLogic JMS at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/fund.html#fund001
JMS queues support the point-to-point (PTP) messaging model. This model enables one application to send a message to another. PTP messaging applications send and receive messages using named queues.
The Configure JMS Queues window prompts you to configure JMS queues required for your configuration. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
If multiple JMS Servers are defined, the wizard displays the JMS topics for each JMS Server on a separate tab. To view a particular JMS Server, you select the corresponding tab.
Enter a name for the JMS queue: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
Enter a valid JNDI pathname to be used to look up the queue within the JNDI namespace. The JNDI name must be unique among all JMS servers defined for the WebLogic Server instance. |
|
From the drop-down list, select a flag specifying whether or not the destination uses the persistent store specified by the JMS server. If the flag you select is:
|
|
From the drop-down list, select a valid JMS template from which the destination is to be derived. If no template is defined ( Attributes that are set to their default values inherit their destination values from the JMS template at run time. If this attribute is not defined, then the attributes for the destination must be specified as part of the destination. |
Note: If you are creating an extension template using the Configuration Template Builder, the next step in your procedure is to set up security for your template. See Configuring Security Options in Your Extension Template.
"Messaging Models" in Programming WebLogic JMS at http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/fund.html#fund001
Tutorial: Creating a Custom Domain With Managed Servers, a Cluster, and Application Services
A distributed topic consists of a set of physical topics that maintain continuous service in the event of a WebLogic Server failure within a cluster. For more information about JMS distributed topics, see "Using Distributed Destinations," in Programming WebLogic JMS at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/implement.html#using_distributed_destinations
The Configure JMS Distributed Topics window prompts you to configure JMS distributed topics required for your configuration. This window is displayed only if you have configured a cluster, as described in Configuring Clusters. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a valid name for the JMS distributed topic: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
Enter a valid JNDI pathname to be used to look up the distributed topic within the JNDI namespace. |
|
From the drop-down list, select a load-balancing policy that can be used by producers sending messages to this distributed queue in order to balance the message load across the members of a distributed destination. The following options are available: |
A distributed queue consists of a set of physical queues that maintain continuous service in the event of a WebLogic Server failure within a cluster. For more information about JMS distributed queues, see "Using Distributed Destinations," in Programming WebLogic JMS at the following URL:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/implement.html#using_distributed_destinations
The Configure JMS Distributed Queues window prompts you to configure the JMS distributed queues required for your configuration. This window is displayed only if you have configured a cluster, as described in Configuring Clusters. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
Enter a valid name for the JMS distributed queue: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
Enter a valid JNDI pathname to be used to look up the distributed queue within the JNDI namespace. |
|
From the drop-down list, select a load-balancing policy that can be used by producers sending messages to this distributed queue in order to balance the message load across the members of a distributed destination. |
|
Enter the amount of time, in seconds, that a distributed queue member holding messages for which it has no consumers waits before forwarding the messages to other queue members that do have consumers. A value of -1 indicates that no messages are forwarded to other queue members. |
The Assign JMS Distributed Destinations to Servers or Clusters window prompts you to assign JMS distributed queues or topics to a WebLogic Server instance or cluster. This window is displayed only if you have defined JMS distributed queues or topics. This step is optional.
The name of the JMS distributed queue or topic is removed from the JMS Distributed Destination pane and added, below the name of the target WebLogic Server or cluster, to the Target pane.
If necessary, you can remove a JMS distributed queue or topic from a WebLogic Server or cluster in one of the following ways:
The Configure JMS Distributed Topic Members window prompts you to assign members to the JMS distributed topic. This window is displayed only if you have configured a distributed topic, as described in Configuring JMS Distributed Topics. This step is optional.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
If multiple JMS Distributed Topics are defined, the wizard displays the distributed topic members for each JMS Distributed Topic on a separate tab. To view a particular component, you select the corresponding tab.
Enter a valid name for the JMS distributed topic member: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
From the drop-down list, select the associated JMS topic. If you are adding a JMS distributed topic member, this drop-down list is not populated until you select a JMS distributed topic from the JMS Distributed Topic field. Only JMS topics with the same target as the associated JMS distributed topic are displayed in the drop-down list. |
|
Enter a numeric value to indicate the weight (that is, a measure of ability to handle message load) of the topic member with respect to other topic members in the distributed destination. The default value is 1. For more information, see "Random Distribution" in Programming WebLogic JMS at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/implement.html#random_weight |
|
If you are adding a distributed topic member, select the JMS distributed topic to which this member is assigned from the drop-down list. For existing distributed topic members, no action is required; the JMS distributed topic associated with the distributed topic member is displayed in the field. |
The Configure JMS Distributed Queue Members window prompts you to assign members to the JMS distributed queue. This window is displayed only if you have configured a distributed queue, as described in Configuring JMS Distributed Topics.
Note: The wizard provides two display modes: a concise tabular view of all the defined components, and an individual view, in which each component is represented by a tab, and you view a particular component by selecting the corresponding tab. To toggle the display mode between table and tab formats, click Switch Display.
If multiple JMS Distributed Queues are defined, the wizard displays the distributed topic members for each JMS Distributed Queue on a separate tab. To view a particular component, you select the corresponding tab.
Enter a valid name for the JMS distributed queue member: a string of characters that can include spaces. The default value in this field is Note: If autoconfiguration has been applied in this configuration, the default value in this field may vary. For more information, see Autoconfiguration of Applications and Services. |
|
From the drop-down list, select the associated JMS queue. If you are adding a JMS distributed queue member, this drop-down list is not populated until you select a JMS distributed queue from the JMS Distributed Queue field. Only JMS queues with the same target as the associated JMS distributed queue are displayed in the drop-down list. |
|
(Optional) Enter a numeric value for the weight (that is, a measure of ability to handle message load) of the queue member with respect to other queue members in the distributed destination. The default value is 1. For more information, see "Random Distribution" in Programming WebLogic JMS at the following URL: http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jms/implement.html#random_weight |
|
If you are adding a distributed queue member, select the JMS distributed queue to which this member is assigned from the drop-down list. For existing distributed queue members, no action is required; the JMS distributed queue associated with the distributed queue member is displayed in the field. |