Oracle® Identity Manager Installation and Configuration Guide for JBoss Application Server Release 9.1.0.1 Part Number E14046-03 |
|
|
View PDF |
When two or more nonclustered JBoss Application Server installations connected to the Apache Web server point to a single database, you must configure the individual JBoss Application Server instances to use different JMS tables.
Complete the following procedure on the second and all other JBoss Application Server instances by using the same Oracle Identity Manager database so that they use different JMS tables:
Open the JBOSS_HOME
\server\default\deploy\jms\
database_name
-jdbc2-service.xml
file in a text editor.
Note that database_name
refers to the common database used by multiple JBoss Application Server instances.
In all the queries and statements in the sqlProperties section of the database_name
-jdbc2-service.xml
file, change the names of the tables represented by JMS_MESSAGES and JMS_TRANSACTIONS to new, unique, and valid values.
Add the following statements to the end of the file:
DELETE_TEMPORARY_MESSAGES = DELETE FROM NEW_JMS_MESSAGES_NAME WHERE TXOP='T' CREATE_IDX_MESSAGE_TXOP_TXID = CREATE INDEX NEW_JMS_MESSAGES_NAME_TXOP_TXID ON NEW_JMS_MESSAGES_NAME (TXOP, TXID) CREATE_IDX_MESSAGE_DESTINATION = CREATE INDEX NEW_JMS_MESSAGES_NAME_DESTINATION ON NEW_JMS_MESSAGES_NAME(DESTINATION)
Note:
NEW_JMS_MESSAGES_NAME
represents the new name of the JMS_MESSAGES tables you changed in Step 2.Save and close the file.