JMS Inbound Adapter EPN Assembly File Configuration

7-20 Oracle Complex Event Processing Developers Guide connection-user Optional. When Oracle CEP calls the createConnection method on the javax.jms.ConnectionFactory to create a connection to the JMS destination JMS queue or topic, it uses the connection-user and connection-password or connection-encrypted-password settings, if configured. Otherwise, Oracle CEP uses the user and password or encrypted-password settings. You can use the connection-user and connection-password or connection-encrypted-password settings in applications where one security provider is used for JNDI access and a separate security provider is used for JMS access. destination-jndi-name Required. The JNDI name of the JMS destination. Note: Specify either destination-jndi-name or destination-name, but not both. destination-name Required. The actual name of the JMS destination. Note: Specify either destination-jndi-name or destination-name, but not both. event-type Event type whose property names match inbound JMS Map Message property names. Specify this property only if you want Oracle CEP to automatically perform the conversion between JMS messages and events. If you have created your own custom converter bean, then do not specify this property For more information, see Section 7.3, Creating a Custom Converter Between JMS Messages and Event Types . jndi-factory Optional. The JNDI factory name. Default value is weblogic.jndi.WLInitialContextFactory, for Oracle CEP server JMS. jndi-provider-url Required. The URL of the JNDI provider. message-selector JMS message selector to use to filter messages. Only messages that match the selector will produce events. Default: there is no selector; all messages will produce events. password encrypted-password Required. Either the password, or encrypted password, for user. Note: Specify either password or encrypted-password, but not both. See Section 7.4, Encrypting Passwords in the JMS Adapter Component Configuration File for details on encrypting the password. session-ack-mode-name Determines how messages are acknowledged. Once a message is successfully acknowledged it will never be resent following a failure. Valid values from javax.jms.Session are: ■ AUTO_ACKNOWLEDGE: With this acknowledgment mode, the session automatically acknowledges a clients receipt of a message either when the session has successfully returned from a call to receive or when the message listener the session has called to process the message successfully returns. ■ CLIENT_ACKNOWLEDG: With this acknowledgment mode, the client acknowledges a consumed message by calling the messages acknowledge method. ■ DUPS_OK_ACKNOWLEDGE: This acknowledgment mode instructs the session to lazily acknowledge the delivery of messages. Default: AUTO_ACKNOWLEDGE. Table 7–1 Cont. jms-adapter Inbound Child Elements Child Element Description Configuring JMS Adapters 7-21 The following configuration file shows a complete example of configuring an inbound JMS adapter. ?xml version=1.0 encoding=UTF-8? n1:config xsi:schemaLocation=http:www.bea.comnswlevsconfigapplication wlevs_application_ config.xsd xmlns:n1=http:www.bea.comnswlevsconfigapplication xmlns:xsi=http:www.w3.org2001XMLSchema-instance jms-adapter namejmsInboundname jndi-provider-urlt3:localhost:7001jndi-provider-url destination-jndi-nameQueue1destination-jndi-name userweblogicuser passwordweblogicpassword work-managerMyWorkManagerwork-manager concurrent-consumers1concurrent-consumers session-transactedfalsesession-transacted jms-adapter jms-adapter namejmsOutboundname event-typeJMSEventevent-type jndi-provider-urlt3:localhost:7001jndi-provider-url destination-jndi-nameTopic1destination-jndi-name delivery-modenonpersistentdelivery-mode jms-adapter n1:config session-transacted Boolean value that specifies whether or not the session is transactional. If the session is transacted then do not specify session-ack-mode-name. Default: False. user Required. When Oracle CEP acquires the JNDI InitialContext, it uses the user and password or encrypted-password settings. work-manager Name of a work manager, configured in the Oracle CEP server config.xml file. This name corresponds to the value of the name child element of the work-manager element in config.xml. If concurrent-consumers is greater than 1 and you want all the consumers to be run concurrently, then consider the configuration of the work-manager you associate with this JMS inbound adapter: ■ If the work-manager is shared with other components such as other adapters and Jetty then set the work-manager attribute max-threads-constraint greater than or equal to the concurrent-consumers setting. ■ If the work-manager is not shared that is, it is dedicated to this inbound JMS adapter only then set the work-manager attribute max-threads-constraint equal to the concurrent-consumers setting. The default value is the work manager configured for the application itself. For more information, see Section F.44, work-manager . Table 7–1 Cont. jms-adapter Inbound Child Elements Child Element Description