Working with the SDM 

The Software Deployment Manager (SDM) is the standard tool that you use to install J2EE components on the AS Java. The SDM is a client/server application. The SDM Server runs on the AS Java side. This server is started automatically with the AS Java. A graphical user interface is available as a client.

SDM Password

The SDM Server recognizes only one user, the SDM administrator. Anybody who has the password of this user can perform any activity in the SDM (such as deployment and undeployment). It is not easy to trace which user performed a particular activity.

To make access to the SDM server secure, change the default password as soon as possible after the installation. Use restrictive guidelines for the password. Also keep the group of people that knows the SDM password as small as possible. For more information, see SDM Remote GUI Client.

When you install SAP Web Application Server 6.40 (J2EE Stack) from Support Package 5, you have the option of entering a new password for the SDM directly, during the installation. You do not have this option if you upgrade with the patch procedure.

If your logon fails three times, the SDM Server (from SAP Web Application Server 6.40 SP5) stops automatically. You can then restart the SDM Server explicitly.

SDM Server

To prevent unauthorized persons from accessing the SDM Server, do not start it until you are installing J2EE components in the AS Java. Shut down the SDM Server again after the installation. For information on starting and stopping the SDM, see Starting and Stopping the Software Development Manager.

You can also use the command line interface of the SDM for deployments on the server host of the central instance of the AS Java. In this case, you do not need to start the SDM Server. For detailed information about the command line interface of the SDM, see the SDM installation directory (under <SDM-Install-Dir>/program/doc/SDMCommandLineDoc630_en_final.pdf).

As well as the deployment of software, you can also use the command line interface to perform administration tasks for the SDM Server, such as changing the password of the SDM Server. Any operating system users who can access the installation directory of the central instance can potentially perform any of these tasks. For this reason, carefully restrict access to the file system to trusted users.

Deployment with the SDM

To deploy J2EE components in the AS Java, use one of the following tools:

●      SDM Remote GUI

●      The command line interface of the SDM (local deployment on the central instance)

●      Eclipse Deployment Plug-In

These tools all use the same communications protocol between the SDM server and SDM client. In all cases, the client-server connection is non-secure.

If you install sensitive components and data in central systems (such as a production server), you must make the connection secure by setting up a virtual private network (VPN) between the client and the server.