JMS Inbound Adapter Component Configuration

7-22 Oracle Complex Event Processing Developers Guide

7.6.2 JMS Outbound Adapter Component Configuration

Table 7–2 lists the jms-adapter element child elments applicable to the JMS outbound adapter. Table 7–2 jms-adapter Outbound Component Configuration Child Elements Child Element Description connection-jndi-name Optional. The JNDI name of the JMS connection factory. Default value is weblogic.jms.ConnectionFactory, for Oracle CEP server JMS. connection-password connection-encrypted-password Optional. Either the password, or encrypted password, for connection-user. Note: Specify either connection-password or connection-encrypted-password, but not both. See Section 7.4, Encrypting Passwords in the JMS Adapter Component Configuration File for details on encrypting the password. 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. delivery-mode Specifies the delivery mode: persistent default value or nonpersistent. 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. 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-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. Configuring JMS Adapters 7-23 The following configuration file shows a complete example of configuring an outbound 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-managerJettyWorkManagerwork-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 user Required. When Oracle CEP acquires the JNDI InitialContext, it uses the user and password or encrypted-password settings. Table 7–2 Cont. jms-adapter Outbound Component Configuration Child Elements Child Element Description 7-24 Oracle Complex Event Processing Developers Guide 8 Configuring HTTP Publish-Subscribe Server Adapters 8-1 8 Configuring HTTP Publish-Subscribe Server Adapters This section contains information on the following subjects: ■ Section 8.1, Overview of HTTP Publish-Subscribe Server Adapter Configuration ■ Section 8.2, Configuring an HTTP Pub-Sub Adapter ■ Section 8.4, Configuring the HTTP Pub-Sub Adapter EPN Assembly File ■ Section 8.5, Configuring the HTTP Pub-Sub Adapter Component Configuration File

8.1 Overview of HTTP Publish-Subscribe Server Adapter Configuration

An HTTP Publish-Subscribe server pub-sub server is a mechanism whereby Web clients, such as browser-based clients, subscribe to channels, receive messages as they become available, and publish messages to these channels, all using asynchronous messages over HTTP. A channel is similar to a JMS topic. Every instance of Oracle CEP includes a pub-sub server that programmers can use to implement HTTP publish-subscribe functionality in their applications. The pub-sub server is configured in the config.xml file along with other server services such as Jetty and JDBC datasources. The pub-sub server is based on the Bayeux protocol see http:svn.xantus.orgshortbustrunkbayeuxbayeux.html proposed by the cometd project see http:cometd.com . The Bayeux protocol defines a contract between the client and the server for communicating with asynchronous messages over HTTP. In Oracle CEP, programmers access HTTP publish-subscribe functionality by using the following built-in HTTP publish-subscribe adapters pub-sub adapters: ■ Publishing to a channel: see Section 8.1.1, Overview of the Built-In Pub-Sub Adapter for Publishing – Local publishing to a channel: see Section 8.1.1.1, Local Publishing . – Remote publishing to a channel: see Section 8.1.1.2, Remote Publishing . ■ Subscribing to a channel: see Section 8.1.2, Overview of the Built-In Pub-Sub Adapter for Subscribing . Oracle CEP also provides a pub-sub API for programmers to create their own custom pub-sub adapters for publishing and subscribing to a channel, if the built-in pub-sub adapters are not adequate. For example, programmers might want to filter incoming messages from a subscribed channel, dynamically create or destroy local channels, and so on. The built-in pub-sub adapters do not provide this functionality, which is why