Miscellaneous JMS Properties Configuring External JMS Jar Files

Configuring Oracle Enterprise Repository Workflow 9-69 4. Restart Oracle Enterprise Repository for the configuration changes to take effect.

9.6.2.3 Miscellaneous JMS Properties

The following miscellaneous System Settings can also be configured: ■ Event Manager JMS Subscribers Enabled : If set to False, then the internal JMS subscribers will not be enabled. This is to make sure that the embedded JMS server is started, but an external tool can be used to connect to the embedded server using the given durable subscriber name and the stored events can be cleaned up. ■ JMS Subscribers Client ID : Specifies the JMS durable subscriber ID. For example, ALER_JmsSubscriber. The property name is cmee.eventframework.jms.subscribers.client.id. ■ JMS Producers Client ID : Specifies the JMS producer’s client ID. For example, ALER_JmsProducer. The property name is cmee.eventframework.jms.producers.client.id. ■ Lazy Initialize Event Engine : When enabled, the Event Manager is initialized when an event is produced for the first time. This property should be enabled for either of the following reasons: – If there is a large number of events stored by the JMS server and if it is required that these events should not be processed as soon as Oracle Enterprise Repository is started. – There are startup issues that occur because of the timing of initializing the embedded JMS server. The property name is cmee.eventframework.lazy.load.

9.6.2.4 Configuring External JMS Jar Files

If an external JMS server is being used, then the external JMS server-related JAR files should be copied to the WEB-INF\lib directory.

9.6.3 Configuring the Embedded ActiveMQ JMS Server to Use a Database

By default, the ActiveMQ JMS server uses a file-based store to store events. However, you can specify to have events stored in a database. Simply, configure the activemq.xml file in the WEB-INF\classes directory to use your database parameters. For example: persistenceAdapter journaledJDBC journalLogFiles=5 dataDirectory=..activemq-data dataSource=oracle-ds -- To use a different datasource, use the following syntax : -- -- journaledJDBC journalLogFiles=5 dataDirectory=..activemq-data dataSource=postgres-ds -- -- Oracle DataSource Sample Setup -- - bean id=oracle-ds class=org.apache.commons.dbcp.BasicDataSource destroy-method=close property name=driverClassName value=oracle.jdbc.driver.OracleDriver property name=url value=jdbc:oracle:thin:localhost:1521:AMQDB property name=username value=scott Note: You must restart Oracle Enterprise Repository after changing any Eventing property in order for the changes to take effect.