How to Encrypt Passwords in the JMS Adapter Component Configuration File

7-18 Oracle Complex Event Processing Developers Guide -- Event bean that is an event sink -- wlevs:event-bean id=mySink class=com.customer.MySink -- Inbound JMS adapter with custom converter class; adapter sends events to mySink event bean-- bean id=myConverter class=com.customer.MessageConverter wlevs:adapter id=jmsInbound provider=jms-inbound wlevs:instance-property name=converterBean ref=myConverter wlevs:listener ref=mySink wlevs:adapter beans

7.5.2 JMS Outbound Adapter EPN Assembly File Configuration

If you are specifying an outbound JMS adapter, set the provider attribute to jms-outbound, as shown: wlevs:adapter id=jmsOutbound provider=jms-outbound The value of the id attribute, in this case jmsOutbound, must match the name specified for this JMS adapter in its configuration file. The configuration file configures the JMS destination to which this outbound JMS adapter sends messages. Because no converter bean is specified, Oracle CEP automatically converts the incoming event types to outgoing JMS messages by mapping the property names. The following sample EPN assembly file shows how to configure an outbound JMS adapter. The network is simple: a custom adapter called getData receives data from some feed, converts it into an event type and passes it to myProcessor, which in turn sends the events to the jmsOutbound JMS adapter via the streamOne channel. Oracle CEP automatically converts these events to JMS messages and sends the messages to the JMS destination configured in the component configuration file associated with the jmsOutbound adapter. ?xml version=1.0 encoding=UTF-8? beans xmlns=http:www.springframework.orgschemabeans xmlns:xsi=http:www.w3.org2001XMLSchema-instance xmlns:osgi=http:www.springframework.orgschemaosgi xmlns:wlevs=http:www.bea.comnswlevsspring xsi:schemaLocation= http:www.springframework.orgschemabeans http:www.springframework.orgschemabeansspring-beans.xsd http:www.springframework.orgschemaosgi http:www.springframework.orgschemaosgispring-osgi.xsd http:www.bea.comnswlevsspring http:www.bea.comnswlevsspringspring-wlevs-v11_1_1_3.xsd wlevs:event-type-repository wlevs:event-type type-name=JMSEvent wlevs:classcom.customer.JMSEventwlevs:class wlevs:event-type wlevs:event-type-repository -- Custom adapter that gets data from somewhere and sends it to myProcessor -- wlevs:adapter id=getData class=com.customer.GetData wlevs:listener ref=myProcessor wlevs:adapter wlevs:processor id=myProcessor wlevs:adapter id=jmsOutbound provider=jms-outbound -- Channel for events flowing from myProcessor to outbound JMS adapter -- wlevs:channel id=streamOne wlevs:listener ref=jmsOutbound wlevs:source ref=myProcessor wlevs:channel beans Configuring JMS Adapters 7-19

7.6 Configuring the JMS Adapter Component Configuration File

You configure the JMS adapters in their respective configuration files, similar to how you configure other components in the event processing network, such as processors or streams. The root element for configuring a JMS adapter is jms-adapter. The name child element for a particular adapter must match the id attribute of the corresponding wlevs:adapter element in the EPN assembly file that declares this adapter. This section describes: ■ Section 7.6.1, JMS Inbound Adapter Component Configuration ■ Section 7.6.2, JMS Outbound Adapter Component Configuration For more information, see: ■ Section 1.1.5, Component Configuration Files. ■ Section B.2, Component Configuration Schema wlevs_application_config.xsd

7.6.1 JMS Inbound Adapter Component Configuration

Table 7–1 lists the jms-adapter element child elments applicable to the JMS inbound adapter. Table 7–1 jms-adapter Inbound Child Elements Child Element Description bindings Bindings are used to configure horizontal scale-out and are an advanced feature. Using the com.oracle.cep.cluster.hagroups.ActiveActiveGro upBean, you can partition an incoming JMS stream in Oracle CEP applications by utilizing the notification groups that the ActiveActiveGroupBean creates. Use this element to associate a notification group with a particular message-selector value. For more information, see Section 22.2.2, ActiveActiveGroupBean concurrent-consumers Number of consumers to create. Default value is 1. If you set this value to a number greater than 1: ■ Consider the work-manager configuration. ■ Be sure that your converter bean is thread-safe because the converter bean will be shared among the consumers. For more information, see Section 7.3, Creating a Custom Converter Between JMS Messages and Event Types . 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.