Configuring Runtime Systems 

Use

When you configure runtime systems, you add systems to the development track. You can then import software changes into these systems automatically and test the software under runtime conditions.

Prerequisites

You are in Landscape Configurator.

You have configured a domain.

You have installed one or more Web AS Java that you can use as runtime systems.

Procedure

To configure runtime systems in a development track, proceed as follows:

Configuration with the Configuration Wizard

...

       1.      In the track list, select the track for which you want configure runtime systems.

       2.      To switch to change mode, choose Change.

       3.      Select the Runtime Systems tab page.

       4.      Under Selected Runtime Systems, select the runtime system that you need for your track.

When you deselect a checkbox, you delete the systems that you no longer need in your track.

The Runtime System Configuration Wizard dialog box appears.

       5.      Enter the required data.

       6.      Choose Next. CMS connects to the message server of the runtime system and determines the deployment tool of the runtime system, and the valid deploy port. This information is displayed in a dialog.

If communication with the message server fails, the wizard will display an error message. You can then either continue or terminate the configuration process.

       7.      Enter the authorization data for the deployment in the runtime system:

       8.      Optional: If Deploy Controller is used you can specify whether the deployment should be done over a secured P4 connection. If the checkbox Use secure connection is selected make sure that the Deploy Port is the P4S port and that secure communication between CMS and the target server is possible. See also Configuring the Use of SSL on the J2EE Engine.

       9.      Select the options Disable Automatic Deployment and Integrate runtime system in Update/Upgrade Scenario if this is required for your configuration. See also Configuring Runtime Systems in NWDI.

   10.      Choose Finish. The data for the runtime system is copied to the runtime system configuration.

   11.      Repeat the procedure for all runtime systems that you want to configure.

   12.      Optional: Expand the View/Edit Deployment Substitution Parameters.

The CMS gets the data for the deployment substitution variables from the appropriate deployment tool and displays them in the table. In the table, you can modify the variables or add extra deployment substitution variables. You must save any modified deployment substitution variables by choosing Save Variables ...

Any changes you make to deployment substitution variables could cause the deployment to fail. For this reason, we recommend that you retain the defaults.

You can use the Read Substitution Variables function to get the substitution variables again. You might need to do this if you could not connect to the SDM at the first attempt.

   13.      After you have configured all the runtime systems and entered the parameters for a new track, choose Save.

Configuration Without Configuration Wizard

If you already know all the configuration-relevant data of a runtime system, you can configure it without the wizard. Procedure:

...

       1.      In the track list, select the track that you want configure runtime systems for.

       2.      To switch to change mode, choose Change.

       3.      Select the Runtime Systems tab page.

       4.      Under Selected Runtime Systems, select the runtime system that you need for your track. The Runtime System Configuration Wizard dialog box appears.

       5.      Choose Configure RTS Without Wizard. The wizard exits and you can enter the configuration data directly in the appropriate fields.

       6.      Optional: If Deploy Controller is used you can specify whether the deployment should be done over a secured P4 connection. If the checkbox Use secure connection is selected make sure that the Deploy Port is the P4S port and that secure communication between CMS and the target server is possible. See also Configuring the Use of SSL on the J2EE Engine.

       7.      Save your data.

 

Result

In the selected track, you have added or deleted one or more runtime systems.

 

See:

Organization of Development in the ABAP Workbench

Where-Used Check for Runtime Systems.