Skip to main content
Feedback

JMS V2 (Early Access) Communication Method configuration

note

The JMS V2 Communication Method is part of Boomi's Early Access program, which offers beta versions of Boomi innovations on an "as is" basis, with no warranties. These features are not final production releases, are unsupported under Boomi's service agreements and support services, and are not intended for production use. While Boomi will work to address issues encountered during the preview and welcomes participant feedback, any feedback provided — whether ideas, suggestions, code, or recommendations, oral or written — is irrevocably assigned to Boomi, LP. By participating, you confirm you have the authority to provide that feedback, will not assert any intellectual property claims against Boomi, and that Boomi may freely implement it without violating any party's rights. If a beta feature doesn't meet Boomi's standards or raises significant concerns, it may never reach general availability, and Boomi cannot guarantee any particular innovation will be released in a supported form. Note that some innovations may only be available as open source or for specific runtime configurations. Documentation may be provided as PDFs, online, or on Community forums.

Refer to the Early Access page to view current programs and request Early Access for a specific feature.

To set up JMS V2 (Early Access) as a communication method for a trading partner, you can use default settings (configured in a My Company trading partner), shared communication (configured in a Communication Channel component), or manually configure specific settings in the Edit JMS V2 (Early Access) Configuration dialog. The dialog opens from within the trading partner Communication tab when you add JMS V2 (Early Access) as a communication method or click JMS V2 (Early Access) in the Communication Method list.

note

To manually configure settings, be sure to uncheck the Use Default Settings box in the Settings, Listen Options, Get Options, and Send Options sections.

Settings

  • Use Default Settings - When checked, the default settings configured in a My Company trading partner are used. Unchecking this option exposes the Connection and JMS Properties sections.

Connection

  • Test Connection - Test the JMS connection by selecting the runtime that you want to use with the connector and then click Next to start the test

  • JMS Version - The JMS version used by the connector to connect to the service

  • Server Type - The JMS vendor. Use Generic JNDI if your preferred server type is not available

  • Use Authentication - When checked, authentication is required to establish the connection to the service and the following fields appear:

    • Username - The username for logging into your JMS service account
    • Password - The password for logging into your JMS service account

  • Connection Factory JNDI Lookup - The Java Naming and Directory Interface (JNDI) name of the connection factory

  • Initial Context Factory - The fully qualified class name of the factory class that creates the initial context

  • Provider URL - The URL for the service provider

  • JMS Properties - Use the Add Property button to add custom configuration properties that are used when connecting to the JMS service. You can encrypt properties to secure sensitive information.

  • Use Connection Pool - When checked, connection pooling is enabled. This might increase performance by using resources more efficiently. Enabling connection pooling exposes the following options:

    • Pool Maximum Connections - The maximum number of connections allowed in the pool at any time. Setting this value to 0 indicates an unbounded number of connections. You will receive an error if you attempt to exceed the maximum.
    • Pool Minimum Connections - The minimum number of connections allowed in the pool at any time. This number must be less than or equal to the Pool Maximum Connections setting
    • Pool Maximum Idle Time - The length of time in milliseconds that a connection can remain open in an idle state
    • Pool Maximum Wait Time - The length of time in milliseconds to wait for a connection from the pool
    • Pool Exhausted Action - Whether to wait for a connection or immediately fail when a connection pool becomes exhausted

Listen Options

  • Use Default Settings - When checked, the default settings configured in a My Company trading partner are used. When unchecked, the following configuration options are exposed:

  • Delivery Policy - The delivery policy specifies how to handle the receipt and acknowledgment of messages. At least once acknowledges message receipt after successfully processing the message. At most once acknowledges message receipt before processing the message.

  • Use Transactions - When checked, transactional mode is enabled

  • Message Selector - The selector expression to filter the messages based on their properties

  • Durable Subscription (only for Topics) - When checked, the server returns every non-expired message to the named subscription, including those published while the subscriber was inactive.

    • Subscription Name - The unique ID with which Durable Subscription will be identified

  • Maximum Concurrent Executions - The maximum number of process executions that are allowed to run simultaneously in a single runtime container

  • Singleton Listener - If checked, the Listen operation will start in a single node for multi-node runtimes, with only one instance of the singleton operation per container. If unchecked, the listener will be started in all available nodes by default.

  • Client ID - A unique identifier for topic subscriptions

  • Destination - The destination from where to retrieve that messages

  • Data Processing Options - The data processing steps are completed in the order specified after receiving the data before standards processing occurs.

Get Options

  • Use Default Settings - When checked, the default settings configured in a My Company trading partner are used. When unchecked, the following configuration options are exposed:

  • Use Transactions - When checked, transactional mode is enabled

  • Message Selector - The selector expression to filter the messages based on their properties

  • Durable Subscription (only for Topics) - When checked, the server returns every non-expired message to the named subscription, including those published while the subscriber was inactive.

    • Subscription Name - The unique ID with which Durable Subscription will be identified

  • Client ID - A unique identifier for topic subscriptions

  • Receive Mode - Specifies how the connector fetches messages from JMS. Select one of the following options:

    • No Wait - Retrieve a single message already available in the destination
    • Limited Number of Messages - Configure the number of messages the connector fetches before returning them in the Number of Messages field
    • Limited Number of Messages with Timeout - Configure the number of messages to be fetched and the number of milliseconds the connector waits before returning them in the Maximum Number of Messages and Receive Timeout fields
    • Unlimited Number of Messages with Timeout - Configure the number of milliseconds the connector fetches messages before returning them in the Receive Timeout field

  • Destination - The destination from where to retrieve that messages

  • Data Processing Options - The data processing steps are completed in the order specified after receiving the data before standards processing occurs.

Send Options

  • Use Default Settings - When checked, the default settings configured in a My Company trading partner are used. When unchecked, the following configuration options are exposed:

  • Use Transactions - When checked, transactional mode is enabled and the following option is exposed:

    • Transaction Batch Size - The number of messages to be sent within a transactional batch

  • Correlation ID - The correlation ID for the message. A correlation ID is a message header field used to link one message to another.

  • Message Type - The value to which to set the JMS message type, for example, Bytes, Text, Stream, Map.

  • Priority - The priority level for this message

  • Reply To - The Destination object to which a reply to this message should be sent

  • Time to Live - The length of time in milliseconds from its dispatch time that a produced message should be retained by the message system. The value must be greater than or equal to zero. Zero indicates that the message does not expire.

  • Client ID - A unique identifier for topic subscriptions

  • Destination - The destination from where to retrieve messages

  • Destination Type - The destination type (used with Oracle AQ server): Text Message, Text Message (XML), Map Message, or Byte Message

  • Custom Properties - Add properties values with their specified name into the message

  • Data Processing Options - The data processing steps are completed in the order specified after receiving the data before standards processing occurs.

On this Page