Databases Reference
In-Depth Information
Edit the config.xml file:
1. Log in as a wls user to the first machine prod01 and navigate to the folder:
[wls@prod01]$ cd $DOMAIN_HOME/config
2. Make a backup of the config.xml file:
[wls@prod01]$ cp config.xml config.xml_backup
3. Open config.xml to be edited:
[wls@prod01]$ vi config.xml
4. Find the <cluster> definition tag of PROD_Cluster :
<cluster>
<name>PROD_Cluster</name>
<cluster-messaging-mode>unicast</cluster-messaging-
mode>
</cluster>
5. Add the <message-ordering-enabled tag:
<cluster>
<name>PROD_Cluster</name>
<cluster-messaging-mode>unicast</cluster-messaging-
mode>
<message-ordering-enabled>true</message-ordering-
enabled>
</cluster>
6. Type :wq! to save the file and exit.
7. Copy the file to all machines in the domain:
[wls@prod01]$ scp config.xml wls@prod02:$DOMAIN_HOME/config
8. Start the Administration Server.
How it works...
The -Dweblogic.unicast.HttpPing=true argument enables an internal health check on
Unicast communications that improves its reliability.
The <message-ordering-enabled> tag forces Unicast communications to be processed in
order, avoiding some issues with JNDI updates and JMS Topics.
 
Search WWH ::




Custom Search