Configuration Page

Specify the Oracle WebLogic JMS Adapter queue or topic values.

Configuring Oracle WebLogic JMS Adapter Produce Message (Invoke/Outbound) Configuration Properties

Element	Description
Schema Location	Select an existing XML schema or schema archive. A schema archive can have a single top-level schema with nested imports and includes that contain absolute or relative paths. You can upload ZIP files for complex schemas with imports. If no XSD is selected, an opaque is assumed.
Schema Element	Select the schema element.
Destination Name	Identify the Java Naming and Directory Interface (JNDI) destination name.
Connection Factory JNDI	Identify the JNDI connection factory. A connection factory defines configuration parameters for client connections, and must be hosted on the same server or cluster as the client's destinations. Select one of the following options: Use the default (in which case, the default connection factory provided by the JMS provider is used). Use a user-defined connection factory.
Message Type	Specify the message type.
Delivery Mode	Specify the delivery mode. Two values are available: Persistent and Nonpersistent.
Priority	Specify the message priority from zero (lowest priority) to nine (highest priority).
Time to Live	Specify the time to live (the amount of time before a message expires and is no longer available for consumption).
Do you want to define a Schema for this endpoint?	Yes: Provide the XSD file for the request payload. No: The payload type defaults to an opaque schema.

Configuring Oracle WebLogic JMS Adapter Consume Message (Trigger/Inbound) Configuration Properties

Element	Description
Schema Location	Select an existing XML schema or schema archive. A schema archive can have a single top-level schema with nested imports and includes that contain absolute or relative paths. You can upload ZIP files for complex schemas with imports. If no XSD is selected, an opaque is assumed.
Schema Element	Select the schema element.
Destination Name	Identify the JNDI destination name.
Connection Factory JNDI	Identify the JNDI connection factory. A connection factory defines configuration parameters for client connections, and must be hosted on the same server or cluster as the client's destinations. Select one of the following options: Use the default (in which case, the default connection factory provided by the JMS provider is used). Use a user-defined connection factory.
Message Type	Specify the message type.
Durable Subscriber	Select Yes or No. This option ensures that consumers receive published messages even when the subscribers are not up and running. The durable subscription involves registering the consumer with a unique ID for retrieving messages sent when the consumer was inactive. These messages are persisted by the JMS provider and are either sent to the consumer when it becomes active again or purged from storage if the message expires. This field is displayed when you select Topic as the Component Type on the Basic Info page. This field is not available when the destination (topic) is targeted to a cluster.
Subscription Name	Specify the durable subscription name. This field is displayed when you select Topic as the Component Type on the Basic Info page.
Message Selector	Specify the message selector.
Do you want to define a Schema for this endpoint?	Yes: Provide the XSD file for the request payload. No: The payload type defaults to an opaque schema.