● All server processes on the Java instance are started before you start JSPM on this instance.
● The SDM server is running.
● No application is connected to the SDM server. There can be only one connection to the SDM server at a time. For example, if you have an open SDM GUI, you must disconnect from the SDM server. Otherwise, the JSPM cannot connect to the SDM server to apply support packages and to deploy software components.
● Directories and files have not been deleted, renamed, or created in the following directories and their subdirectories: /usr/sap/<SID>/SYS/exe and /usr/sap/<SID>/SYS/profile. Otherwise, JSPM cannot detect the kernel and the system profiles, and cannot be started. If a backup of the kernel and the system profiles has been required, it has been created in a different directory.
● You have logged on to the operating system as a <SID>adm user. If you have not done this, you must switch to it before starting to use JSPM. Fore more information, see below.
● If your system is an IBM eServer iSeries:
○ You have logged on as a <SID>adm or a <SID>ofr user.
○ The release of JSPM is not lower than SAP NetWeaver 7.0 SPS06.
○ If you have to deploy JSPM as of SAP NetWeaver 7.0 SPS06, the go and StartGui scripts have been downloaded. For more information, see SAP Note 885063.
You can do this in two ways.
1. Open Start → Programs →Accessories
2. Click with the secondary mouse button on the Command Prompt icon.
3. From the pop-up menu, choose Run As.
4. Choose <SID>adm user.
5. Start JSPM from the new console.
Use the following command line:
runas /profile /user:<domain or host>\<sid>adm <full path to JSPM\go.bat>
runas /profile /user:%COMPUTERNAME%\j70adm D:\usr\sap\J70\JC03\j2ee\JSPM\go.bat
1. Use the following command:
su - <sid>adm
2. Start JSPM.
1. In the file system, go to the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM directory.
Depending on the system, the name of the central instance has the following syntax:
● For a standalone system – JC<xx>
● For an add-on system – DVEBMGS<xx>, where xx is the number of the central instance.
2. To start JSPM, run the go script file.
In this step you can specify a temporary inbox directory. See.
3. Enter your password for the SDM and choose Log On.
If you enter an incorrect password three times in a row, the SDM server will be stopped. You must start it and log on to the JSPM again. For more information about starting the SDM server, see Starting and Stopping the Software Deployment Manager.
Start JSPM with this command line:
Wait for this message to appear on the console:
Waiting for SDTServer to connect ...
Open a web browser on another host with Java runtime installed. Browse to this address:
<host> is the host on which you have started JSPM and <xx> is the number of the instance from which you have started JSPM.
On the web page choose the link Start JSPM Frontend (SDTGui). JSPM GUI will be downloaded and started locally by Java Web Start technology. Then you can proceed as starting on any other operating system. Just keep in mind that JSPM actually runs on the remote host.
For more information, see SAP Note 1013976.
1. To prevent JSPM from automatically starting its GUI, in the /usr/sap/<SID>/<Central instance name>/j2ee/JSPM/param/jspm_config.txt file, change the /dialog/SDTServerConnection/SDTGui/launch property from true to false.
2. Run the go script on the IBM eServer iSeries host using the following OS/400 command:
QSH CMD('/usr/sap/<SID>/<Central instance name>/j2ee/JSPM/go').
3. To start the JSPM GUI, from the mounted /usr/sap/<SID>/<Central instance name>/j2ee/JSPMdirectory, run the StartGui script.
The JSPM GUI appears.
4. In the Host field, enter the target IBM eServer iSeries host.
5. Enter your password for the SDM and choose Log On.