You have installed the basic components of the cluster.
Make sure the AS Java is stopped.
More information: Starting and Stopping Systems and Instances .
The installation procedure configures the optimal number of server processes in an instance based on the available hardware resources. This enables optimal utilization of the hardware resources and of the capacity of the ICM to handle multiple server processes.
When planning the number of server processes you want to have in an AS Java instance, you can allocate one of them for debugging. This means that when you start AS Java, this debuggable server process will not be operational in order to reduce the system resources consumption. When a problem appears in AS Java, you can start this server process using the SAP MC and connect to it with debugger.
The debug server process is not included in the load balancing so end users will not experience stale requests (due to debugger breakpoints). However, you will still be able to monitor how your application/components behave in a cluster, inspect data and evaluate expressions.
More information: Enabling Debugging
If you need to add more server processes to an existing Java instance, you can do that manually using the Config Tool.
You can configure the number of server processes on two levels:
If you define a number of server processes on a template level, the number will be relevant for all Java instances in the cluster.
Java instance level
If you specify a number of server processes for a particular Java instance, the number will be relevant only for this particular Java instance.
This option is available at instance level only.
If the template configuration allows you to enter a formula instead of an exact value, then the Check Value option calculates the formula and displays the value.
You can set only one node for debugging in an instance. For more information, see the NOTE paragraph at the beginning of this page.