!--a11y-->
Applying a ConfigurationThis 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.
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.
¡ 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.
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. Note that most of the parameters are detected automatically. You should set the average CPU speed (AVERAGE_CPU_SPEED) and the usage factor (USAGE_FACTOR) manually.
The usage factor is a floating point number in the range from 0 to 1 inclusive. It indicates which percentage of the available hardware resources is to be used by the instance.
8. Choose Next.
9. The Available components screen displays the component templates that are available with the tool. Choose Next.
10. 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.
In addition, you can choose to apply a local configuration only. 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.

Use the Instance Local Configuration Only option when you configure a Java instance. When applying configuration to a central services instance, leave this option unchecked.
On this screen, you can set logging preferences using Logging options….
11. Choose Next.
12. Review the selected options and confirm them by choosing Finish.
13. 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.
