Deployment is the final stage of application development and it involves the transfer of application data to the target system. The AS Java uses a server side Deploy Controller to manage software deployment.
The Deploy Controller enables client applications to use APIs to enable deployment of software components on the AS Java server process. The client applications that use the Deploy Controller APIs use the P4 communication protocol for the connection to the AS Java.
The standard tools below use the Deploy Controller APIs and enable you to deploy software components on the AS Java
During software deployment, the SAP NetWeaver Developer Studio connects to the Deploy Controller on the AS Java server using the Deploy Controller API. The connection between the NWDS and the target AS Java uses the P4 communication protocol.
For telnet deployment, you open a Telnet session to the AS Java and then use the Deploy Controller functions for software deployment. To secure the communication, we recommend that you can use a VPN.
For more information about using these tools in your deployment scenario, see Deployment: Putting It All Together in the Development Manual. For an overview of the communication flow, see the figure below.
Communication Flow for Software Deployment
For an overview of the remote communication paths, the protocols used, the data transferred see the table below.
Communication path | Protocols Used | Type of Data Trasferred | Available Security Protection |
---|---|---|---|
Deploy Controller Client to AS Java |
P4 |
|
VPN |
Shell Administration |
Telnet |
|
VPN |
See also: