Applying a Configuration 

Use

This procedure enables you to select and apply a configuration template to a Java instance that is installed and the SAP NetWeaver components running on it.

You must apply the same configuration template to all Java instances in the cluster. The template configuration comes into effect after you restart the configured instance.

Prerequisites

You have installed all required SAP NetWeaver components on all hosts in the cluster.

Make sure the database is running when you apply the configuration templates.

Procedure

Applying a Configuration on a Central Instance

       1.      Start the Template Configuration Tool and choose Next on the Welcome screen.

       2.      Select Apply and then choose Next.

       3.      Enter the following parameters:

○     Template filename – select an archive (ZIP) file that contains the relevant configuration templates depending on the components you have installed. For more information about the appropriate template for each scenario, see Selecting the Appropriate Template.

○     Working dir – enter the working directory of the Template Configuration Tool. By default, this is the working folder in the tool’s installation directory.

○     Instance dir – enter the installation directory of the Java instance – for example, C:\usr\sap\J2E\JC00 on Windows, or /usr/sap/C11/DVEBMGS00 on UNIX.

       4.      Choose Next.

       5.      On the Edit System Dependencies screen you can maintain the settings of the Java instance.

The system dependencies are detected automatically. Avoid changing them manually as this may damage the system.

       6.      Choose Next.

       7.      On the Edit Hardware Preferences screen you can maintain the hardware-related parameters that are relevant for the system configuration. These parameters determine the resources that the Java instance will use. Note that most of the parameters are detected automatically.

                            a.      To specify the amount of memory (in MB) that will be allocated to the Java instance you are configuring, use the AMOUNT_MEMORY option. This parameter will determine the number of server processes that will be created for this instance and the heap size that will be allocated to each of them.

                            b.      To specify the number of CPUs that the Java instance will use, use the CPU_COUNT parameter. This will affect some internal parameters, such as the number of concurrent users that the Java instance will be able to process.

Make sure that you take into account the memory and CPU consumption by the other components or processes (for example, database systems, other ABAP or Java instances) running on the same physical host. That is, if you have a Java instance and a database system running on the same host, you should consider the amount of memory used by the database system, and then choose an appropriate AMOUNT_MEMORY value for the Java instance.

Do not configure the usage factor (USAGE_FACTOR). The system does not take its value into account.

       8.      Choose Next.

       9.      On the Advanced options screen, you can choose to create a backup for the current system configuration. The backup is created in a subfolder of the working directory, called backup.

We recommend that you use the backup option, so that you can restore the configuration if necessary.

Leave the option Instance Local Configuration Only deselected.

In the J2EE Engine you can apply two configuration categories – global or local configuration. The global configuration includes modifications that are applied to the entire cluster, such as starting and stopping services, changes to the service startup mode, and so on. The local configuration is applied to the current Java instance only and includes actions such as setting service and manager local properties. If you leave the Instance Local Configuration Only option unchecked, both the global and the local configurations are applied.

On this screen, you can set logging preferences using Logging options….

   10.      Choose Next.

   11.      On the Preview component screen, you can select the components that you are configuring. By choosing Preview… you can see the changes that the Template Configuration Tool will apply to the existing system marked in red. Optionally, by choosing Export to XML… you can save in an XML file the list of parameters with their old and new values.

   12.      Choose Next.

   13.      Review the selected options and confirm them by choosing Finish.

   14.      Wait for the process to finish and close the console by choosing OK.

You can select the output in the console and copy it for logging purposes.

   15.      Restart the instance.

Applying a Configuration on a Dialog Instance

...

       1.      Mount the global SAP directory on the central instance host as a local drive for the relevant dialog instance host.

       2.      On the dialog instance host, start the Template Configuration Tool from the script file located in the global SAP directory. Choose Next on the Welcome screen.

       3.      Select Apply and choose Next.

       4.      Select an appropriate template.

Make sure you select the same template that you already applied to the central instance of the cluster.

For Instance dir, select the path on the local physical host to the of the installation directory of the dialog – for example, C:\usr\sap\J2E\JC00 on Windows, or/usr/sap/C11/DVEBMGS00 on UNIX. Choose Next.

       5.      Repeat steps 5 through 9 from the above procedure.

       6.      On the Advanced Options screen, enable the Instance Local Configuration Only option.

       7.      Complete the procedure as described in steps 11 through 15 above.