How to Configure a JMS Adapter Manually

7-8 Oracle Complex Event Processing Developers Guide ■ Section 7.5.1, JMS Inbound Adapter EPN Assembly File Configuration ■ Section 7.5.2, JMS Outbound Adapter EPN Assembly File Configuration 2. Update the component configuration file of the application by adding a jms-adapter element for each inbound and outbound JMS adapter you want to use in your application. Example 7–5 shows the jms-adapter element for the JMS inbound adapter in Example 7–4 . Example 7–5 jms-adapter Element for Inbound Adapter jms-adapter nameinboundJmsAdapter1name ... jms-adapter For each jms-adapter element, the name child element must be set to the corresponding wlevs:adapter element id child element. See: ■ Section 7.6.1, JMS Inbound Adapter Component Configuration ■ Section 7.6.2, JMS Outbound Adapter Component Configuration 3. Decide how you want to convert between JMS messages and Oracle CEP event types: a. If you want the JMS adapters to perform automatic conversion, specify an event type using the jms-adapter element event-type child element in the JMS adapter component configuration file. See: – Section 7.6.1, JMS Inbound Adapter Component Configuration – Section 7.6.2, JMS Outbound Adapter Component Configuration b. If you want the JMS adapters to perform custom conversion, create a custom converter Java class and register it in the EPN assembly file. See Section 7.3, Creating a Custom Converter Between JMS Messages and Event Types . 4. Configure the jms-adapter elements for your Oracle WebLogic Server JMS provider. Example 7–6 shows the jms-adapter elements for a JMS inbound and JMS outbound adapter. Example 7–6 jms-adapter Elements for an Oracle WebLogic Server JMS Provider ... jms-adapter nameJmsInboundname event-typeSimpleMapEventevent-type jndi-provider-urlt3:localhost:7001jndi-provider-url destination-jndi-nameQueueIndestination-jndi-name userweblogicuser passwordwelcome1password work-managerJettyWorkManagerwork-manager concurrent-consumers1concurrent-consumers session-transactedfalsesession-transacted delivery-modenonpersistentdelivery-mode jms-adapter Configuring JMS Adapters 7-9 jms-adapter nameJmsOutboundname event-typeSimpleMapEventevent-type jndi-provider-urlt3:localhost:7001jndi-provider-url destination-jndi-nameQueueIndestination-jndi-name userweblogicuser passwordwelcome1password message-selectormessage-selector session-transactedfalsesession-transacted delivery-modenonpersistentdelivery-mode jms-adapter ... See: – Section 7.6.1, JMS Inbound Adapter Component Configuration – Section 7.6.2, JMS Outbound Adapter Component Configuration 5. If you specify JMS provider client passwords in the component configuration file, consider encrypting them. See Section 7.4, Encrypting Passwords in the JMS Adapter Component Configuration File . 6. If you are using Java Object messages, you must create a JMS client application library that contains the Java classes used for messaging need to be packaged in a library bundle. For more information, see Section 24.1.3.3, Creating Application Libraries . 7. If you are using Java Object messages, copy the Java classes for messaging application library to the appropriate Oracle CEP server application library directory: a. If your bundle is a driver, you must put it in the library extensions directory. See Section 24.1.3.2, Library Extensions Directory . b. If your bundle is not a driver, you may put it in the library directory. See Section 24.1.3.1, Library Directory For more information, see Section 24.3.4, How to Update an Application Library Using Oracle CEP IDE for Eclipse . 8. If you created a custom converter class in step 3, update the MANIFEST.MF file of your application to add the following packages to the Import-Package header: Import-Package: javax.jms,javax.naming, ... ... Note: This JMS client JAR application library must: ■ Export the Java classes used for messaging. ■ Import javax.jms and javax.naming. The application bundle does not need to export provider-specific packages. The application bundle must import Java classes used for messaging, if applicable. 7-10 Oracle Complex Event Processing Developers Guide See Section 4.7.5, How to Import a Package .

7.2.4 How to Configure a JMS Adapter for Tibco EMS JMS Manually

Oracle CEP supports TIBCO Enterprise Message Service EMS version 4.2.0 or higher. To use the Tibco EMS JMS provider, you must add the following Tibco EMS client JAR files to the Oracle CEP server library directory: ■ tibjms.jar For more information, see: ■ Section 7.2, Configuring a JMS Adapter for a JMS Service Provider ■ Section 24.1.3.1, Library Directory You can manually configure the built-in JMS inbound and outbound adapter to use the Tibco EMS JMS provider. The simplest way to create and configure a JMS adapter is using the Oracle CEP IDE for Eclipse adapter wizard as Section 7.2.1, How to Configure a JMS Adapter Using the Oracle CEP IDE for Eclipse describes. After using the adapter wizard to create and specify the basic JMS adapter configuration, review this procedure to complete the configuration. To configure a JMS adpater for Tibco EMS JMS manually: 1. In the EPN assembly file of the application, add a wlevs:adapter element for each inbound and outbound JMS adapter you want to use in your application. Example 7–7 shows the wlevs:adapter element for a JMS inbound adapter. Example 7–7 wlevs:adapter Element for Inbound Adapter wlevs:adapter id=inboundJmsAdapter1 provider=jms-inbound ... wlevs:adapter See: ■ Section 7.5.1, JMS Inbound Adapter EPN Assembly File Configuration ■ Section 7.5.2, JMS Outbound Adapter EPN Assembly File Configuration 2. In the component configuration file of the application, add a jms-adapter element for each inbound and outbound JMS adapter you want to use in your application. Example 7–8 shows the jms-adapter element for the JMS inbound adapter in Example 7–7 . Example 7–8 jms-adapter Element for Inbound Adapter jms-adapter nameinboundJmsAdapter1name ... jms-adapter For each jms-adapter element, the name child element must be set to the corresponding wlevs:adapter element id child element. See: ■ Section 7.6.1, JMS Inbound Adapter Component Configuration