Restriction: You cannot benefit from the one-phase commit optimization in the following circumstances:

yIf your application uses a reliability attribute other than assured persistent for its JMS messages.

yIf your application uses Bean Managed Persistence (BMP) entity beans, or JDBC clients.

Before you configure your system, ensure that you consider all of the components of your J2EE application that might be affected by one-phase commits. Also, since the JDBC datasource connection will now be shared by the messaging engine and the EJB container, you need to ensure that you increase the number of connections allocated to the connection pool. To optimize for one-phase commit transactions, refer to the following website:

Http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.doc/tasks/t jm0280_.html

WebSphere Application Server V51 Express

For information on WAS V51 Express, please refer to older versions of the Performance Capabilities Reference Manual that can be found here: http://www.ibm.com/systems/i/solutions/perfmgmt/resource.html

IBM i 6.1 Performance Capabilities Reference - January/April/October 2008

 

© Copyright IBM Corp. 2008

Chapter 6 - Web Server and WebSphere

106

Page 106
Image 106
Intel AS/400 RISC Server, 170 Servers, 7xx Servers manual WebSphere Application Server V51 Express