Configuring Runtime Systems in NWDI
In NetWeaver Development Infrastructure (NWDI), you develop software that you run in a runtime environment. By deploying the software component archives (SCAs) to the runtime system, you create the connection between the software design environment – the local development environment – and the runtime environment.
NWDI provides you with the option of connecting the design environment and runtime environment in a single integrated system. (See also The Term ‘System’ in CMS. In an NWDI development track, the runtime environment is a SAP NetWeaver Application Server Java (NetWeaver AS Java).
Prerequisites
If you configure runtime systems in the track, deployment takes place in CMS during import. To enable the deployment, you must provide CMS with information about the deployment tool used by Web AS Java. Since AS Java in NetWeaver 2004s and NetWeaver 2007 use different deployment tools, CMS uses the message server of the runtime systems to get the required information. The connection with the message server runs through an HTTP connection. You therefore need to specify the message server’s HTTP port.
To find the port, proceed as follows:
● NW 04 and NW 2004s
Visual Administrator → Cluster → Server → Services → Message Info → Runtime → Parameters → Parameter: ms/http_port
● NW 2007
NetWeaver Administrator → Problem Management → Infrastructure Management → Message Server → Show: Message Server Parameters → Parameter: ms/http_port
Input Parameters
Host Name: Enter the name of the host on which the runtime system is installed.
HTTP Port of Message Server: HTTP port of the message server that belongs to the instance of the runtime system.
SDM Password: The password you specified during the installation of the SAP NetWeaver AS Java for Software Deployment Manager (SDM).
You no longer need the SDM password in NetWeaver 2007 systems, as the deploy controller for SAP NetWeaver Web AS Java is responsible for the deployment. The deploy controller requires the following parameters.
J2EE Engine User: The user with deployment authorization for the specified runtime system.
J2EE Engine Password: Password of the user that you entered in the previous field.
Options
● Switch off automatic deployment
For the Development and Consolidation runtime systems, you can also select the Disable Automatic Deployment option. When you do this, you remove the link between automatic deployment and activation in SAP NetWeaver Developer Studio. You then have to start the deployment manually.
We recommend that you keep the default settings.
● Integrate runtime systems into the Support Package process with Software Update Manager (SUM) or Java Support Package Manager (JSPM)
You use SUM, or JSPM in previous releases (see SAP Note 1589311), to update the runtime systems directly with SAP Support Packages. To synchronize any modifications with the developed software components, NWDI and SUM or JSPM have to exchange information about the software components involved. You can enhance the configuration of the runtime system for this process (Maintenance of an NWDI-Driven Software Landscape).
This requires the following additional settings:
○ The URL of SAP NetWeaver AS Java
○ The J2EE Engine User: The user with deployment authorization for the specified runtime system.
○ J2EE Engine Password: Password of the user that you entered in the previous field.
If you select the option Integrate Runtime System into Update/Upgrade Scenario, CMS makes these settings automatically during configuration with the Configuration Wizard.
See also:
Where-Used Check for Runtime Systems