Note 739788 - SAP NetWeaver: Template-Based Configuration - Composite Note

Note 739788 - SAP NetWeaver: Template-Based Configuration - Composite Note

Summary

Symptom

This is a composite SAP Note for template-based configuration of SAP
NetWeaver components.

Other terms

SAP Web AS, J2EE Engine, SAP NetWeaver, Template Configuration Tool

Reason and Prerequisites

Additional Information about the use of Template Configuration Tool and the application of the configuration templates.

Solution

 

General Information ===================

Read this note before installation of SAP NetWeaver components to get the latest information about the usage of the Template Configuration Tool.
The Template Tool is only for use with Netweaver 2004 installations (see below)!

Using the Template Configuration Tool =====================================

Use the Template Configuration Tool for every new installation of the J2EE Engine 6.40 SP10 or above (corresponds to NetWeaver'04 SP Stack 10) .
Use the Template Configuration Tool for the integrated J2EE Engine as part of Web AS ABAP+Java as well.
Do not use the Template Tool after upgrade; SAP does not support this case and you could lose the configuration which was done before partially (please see section 'Additional documentation' for further information).
If you are using the template tool for the first time please pay special attention to release information, workarounds and additional documentation.

Release information ===================

templates are released for the following Netweaver platforms:

• Windows NT

• Windows NT on Itanium (64 Bit)

• Linux

• Solaris

• HP-UX (PA-RISC)

• HP on Itanium (64 Bit)

• IBM AIX

• Tru64 (except templates for the portal scenario)

the usage of the template configuration tool for IBM eServer System i is not yet released but will be in the near future.

Additional documentation ========================

This information is in addition to the official documentation.

High Availability Setup
In case you are planning High Availability Setup of the J2EE Engine, apply the Template Configuration first and only then apply any changes to the hostname.
The parameter ${INSTANCE_HOST} should contain the original hostname which has been used during installation.

For the Portal scenario on AIX we recommend a minimum resource of 2.5 GB (for single server installation).

Do not use the Template Configuration Tool for J2EE Engine installation that is part of the Developer Workplace installation.
It is unnecessary (but not harmful) because this J2EE Engine is ready for use after installation. Also, do not use the tool for an existing SAP Web AS (Java) system, which you have upgraded to SP7 or higher. SAP does not support this case. The engine may not start after using the Template Configuration Tool or you could lose all configuration that you have applied to the J2EE Engine before. If you want to use the Template Configuration Tool, consider installing a new system instead.

In SAP Web AS Java the usage factor parameter is ignored.
Therefore, you cannot set the the resources available to the Java instance using this parameter, as described in the documentation of the Template Configuration Tool("Applying a Configuration"). Instead, you should use the CPU_COUNT and the AMOUNT_MEMORY parameters to set the hardware resources for the instance.
For example, if an Oracle database is running on the same machine as the J2EE Engine consuming 1.5 GB of the available 4 GB of memory, you should set the AMOUNT_MEMORY parameter to 2.5 GB. If other processes consume 20% of the CPU on a 4-CPU machine, you should set the CPU_COUNT parameter to 3 so that only the system is configured to use the available 80% of CPU. If the CPU usage is lower - for example, 3-4%, you can allocate all 4 CPU to the J2EE Engine.

Workarounds ==================

Single CPU machines for Portal scenario
In addition to the templates provided with the installation and described in the documentation, you can also download the following template from this note (see the instructions below):

• Template Portal_1CPU.zip - use this template for SAP Enterprise Portal on single-processor machines

Note: To apply template-based configuration on a portal application, at least 2GB of memory should be available to the SAP Web AS, on which the portal is running.

Setting the CPU Count to Circumvent Clustering Restrictions ===========================================================

Some components have restrictions regarding clusters or instances with more than one server node. In these cases, which are listed below, you have to take special steps when using the Template Configuration Tool.

• If you intend to use Adobe Document Services (ADS) you must force the Template Configuration Tool to create a J2EE Engine instance with only one server node (see instructions below). Multiple single-node instances on separate hosts or even on the same host can be used together with ADS as a workaround for achieving scalability until the issue is fixed.

• If you intend to use the SAP System Landscape Directory (SLD) you can force the Template Configuration Tool to create a J2EE Engine instance with only one server node (see instructions below) and install only one instance. This is because on a clustered J2EE Engine you have to switch off the SLD cache, which slows down SLD requests by a factor 2-3. See http://service.sap.com/sld for details.

You can force the Template Configuration Tool to create a J2EE Engine instance with exactly one cluster node. To achieve this, manually set the parameter ${CPU_COUNT} to 1. The parameter can be accessed on screen "Edit Hardware Dependencies". Select the parameter from the list, enter the value "1" and accept the new value by selecting the button "Add".

How to Download Templates From This Note ========================================

Updated templates are distributed as attachments to this note. To use them, select the tab "Attachments", then right click the desired template.zip file and download it to your computer. (This description applies to SAP Service Marketplace Web Frontend.) Then transfer this file to the directory /usr/sap/<SID>/SYS/global/TemplateConfig on your application server. Now you can select the downloaded template from the Template Configuration Tool just like any other template which comes with the tool itself.

Header Data

Release Status:	Released for Customer
Released on:	03.07.2006  07:16:19
Priority:	Recommendations/additional info
Category:	Customizing
Primary Component:	BC-JAS-COR Enterprise Runtime, Core J2EE Framework

Releases

Software Component Release From Release To Release And subsequent SAP-JEE 60 6.40 6.40

<script type="text/javascript">var evt_array = new Array('empty','empty','empty','empty','empty','');try { for (i=0;i!=evt_array.length;i++) { if(evt_array[i]=='empty') continue; obj=document.getElementById('releases_tab'); obj.setAttribute('colEvt' +( i + 1),evt_array[i] ); } } catch (e) {};</script>

Related Notes

781882 - Mandatory and optional services in J2EE engine 6.40
772752 - Fine tune performance of NW04 EP 6.0 on WebAS 6.40
723909 - Java VM settings for J2EE 6.30/6.40/7.0
709140 - Recommended JDK and VM Settings for the WebAS630/640/7.0

Attachments

Filetype Filename Language Filesize ZIP Portal1CPU.zip English 2 KB ZIP BW.zip English 4 KB ZIP J2EE-Engine-only.zip English 2 KB ZIP JDI-DTR-and-CBS.zip English 4 KB ZIP JDI-DTR-only.zip English 4 KB ZIP Portal.zip English 2 KB