Académique Documents
Professionnel Documents
Culture Documents
3: Add entry
<connection-factory-jndi-name>jms/sai/JMSConnectionFactoryLocal</connection-factory-jndi-
name>
<weblogic-enterprise-bean>
<ejb-name>FileadeOrderTracking</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
</pool>
<destination-jndi-name>sai/jms/topic/OrderImplementationTopic</destination-jndi-name>
<connection-factory-jndi-name>jms/sai/JMSConnectionFactoryLocal</connection-factory-
jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<reference-descriptor>
</reference-descriptor>
</weblogic-enterprise-bean>
MailPollerServlet.java
SESAM CHANGE:-
Add entry
<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated</param-value>
</session-param>
In Weblogic.xml.
Test scenario:
1. All Functional testing.
2. Load Testing.
3.
ADVANTAGE:-
1. By using Cluster the availability of resources will be double so it will improve Application
Performance.
RISK:-
1. As we are using Queue instead of Topic the order creation will be stopped if there is any
Non-Deliverable message is in Queue.