Configuring the J2EE Engine - Way2SAPBASIS.com

1 SAP NetWeaver '04. Configuration Guide Configuring the j2ee Engine Document Version January 2006. SAP AG. Neurottstra e 16. 69190 Walldorf Germany T +49/18 05/34 34 24. F +49/18 05/34 34 20. SAP, R/3, mySAP, , xApps, xApp, SAP NetWeaver, Copyright 2005 SAP AG. All rights reserved. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of No part of this publication may be reproduced or transmitted in SAP AG in Germany and in several other countries all over the any form or for any purpose without the express permission of world. All other product and service names mentioned are the SAP AG.

2 The information contained herein may be changed trademarks of their respective companies. Data contained in this without prior notice. document serves informational purposes only. National product specifications may vary. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. These materials are subject to change without notice. These Microsoft, Windows, Outlook, and PowerPoint are registered materials are provided by SAP AG and its affiliated companies trademarks of Microsoft Corporation. ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP.

3 IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, Group shall not be liable for errors or omissions with respect to MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, the materials. The only warranties for SAP Group products and pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, services are those that are set forth in the express warranty WebSphere, Netfinity, Tivoli, and Informix are trademarks or statements accompanying such products and services, if any. registered trademarks of IBM Corporation in the United States Nothing herein should be construed as constituting an additional and/or other countries. warranty. Oracle is a registered trademark of Oracle Corporation.

4 Disclaimer UNIX, X/Open, OSF/1, and Motif are registered trademarks of Some components of this product are based on Java . Any code the Open Group. change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, decompilation of these components. VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. Any Java Source Code delivered with this product is only to be used by SAP's Support Services and may not be modified or HTML, XML, XHTML and W3C are trademarks or registered altered in any way. trademarks of W3C , World Wide Web Consortium, Massachusetts Institute of Technology.

5 Documentation on SAP Service Marketplace Java is a registered trademark of Sun Microsystems, Inc. You can find this documentation at JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. Typographic Conventions Icons Type Style Represents Icon Meaning Example Text Words or characters quoted from Caution the screen. These include field names, screen titles, Example pushbuttons labels, menu names, menu paths, and menu options. Note Cross-references to other Recommendation documentation. Example text Emphasized words or phrases in Syntax body text, graphic titles, and table titles.

6 EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

7 EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER. Contents 1 Configuring THE j2ee 1. 2 CLUSTERING THE j2ee Engine .. 2. Setting Up the j2ee Engine Cluster .. 3. Template Configuration Tool .. 4. Adding Java Instances .. 14. Adding Server 15. 3 Configuring THE j2ee Engine 16. Configuring Cluster Elements .. 17. Connections 18. Activities .. 18. Setting Service Load Timeout .. 21. Managing Cluster Elements Startup and Shutdown .. 22. Configuring the Message Server Communication .. 24. Configuring the Session 25. Configuring the Lazy Communication .. 26. Setting Service Stop 27. Setting Event 28. 4 Configuring ADDITIONAL PARAMETERS OF THE j2ee Engine .

8 29. Tuning Web Container .. 30. Tuning EJB Request Processing .. 32. Tuning Remote 32. Tuning Database Connectivity .. 33. Tuning JMS 34. 5 REFERENCES AND RECOMMENDED FURTHER READINGS .. 35. Configuring the j2ee Engine January 2006. 1 Configuring the j2ee Engine Purpose The j2ee Engine installation procedure provides a system that is ready to be run and used. However, you may need to configure the j2ee Engine additionally to adapt the system to the needs and requirements of a particular business scenario. This guide assumes that you have already installed successfully Web Application Server Java. Features This guide provides general guidelines about: Clustering the j2ee Engine [Page 2].

9 Configuring the j2ee Engine Cluster [Page 16]. Configuring Some Additional Parameters of the j2ee Engine [Page 29]. References and Recommended Further Readings [Page 35]. Configuring the j2ee Engine 1. Clustering the j2ee Engine January 2006. 2 Clustering the j2ee Engine This section is an introduction to the j2ee Engine cluster. It provides information about: The j2ee Engine cluster architecture Procedures how to scale the j2ee Engine cluster The initial configuration steps to run your j2ee Engine cluster Links to more advanced configuration topics What is a Cluster? The cluster is a set of processes that work together to build a scalable and reliable system.

10 The cluster structure is transparent to the clients and appears to them as a single server unit. The j2ee Engine cluster consists of one or more Java dispatchers, several server processes, the Central Services (Message Service and Enqueue Service), and the database. Why Clustering? Clustering provides the following advantages: Scalability of the system In case of high system load, you can easily enlarge the current system. High availability of the system The set of mechanisms that the system provides guarantees normal system operation with its ability to transparently recover in case of failures within the cluster. To make use of the clustering features, you need to set up and configure the j2ee Engine according to the deployed applications and the expected workload.