Show TOC

Procedure documentationStarting JSPM Locate this document in the navigation structure

Prerequisites

  • All server processes on the Java instance are started before you start JSPM on this instance.

  • 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. For more information, see below.

    Note Note

    On systems, where there is no <sid>adm user, you can run JSPM with different user provided it has enough permissions.

    End of the note.

  • You have logged to the JSPM with an AS Java user with enough permissions to deploy.

Procedure

Switching to <SID>adm user
For Windows OS

You can do this in two ways:

With menu options

  1. Open   Start   Programs   Accessories  

  2. Click with the secondary mouse button on the Command Prompt icon.

  3. From the context menu, choose Run As.

  4. Choose <SID>adm user.

  5. Start JSPM from the new console.

With runas command

Use the following command line:

runas /profile /user:<domain or host>\<sid>adm <full path to JSPM\go.bat>

Example Example

runas /profile /user:%COMPUTERNAME%\j70adm D:\usr\sap\J70\JC03\j2ee\JSPM\go.bat

End of the example.
For UNIX OS

  1. Use the following command:

    su - <sid>adm

  2. Start JSPM.

For IBM i

  1. Log on as user <SID>ADM.

  2. Start JSPM (as described in Starting JSPM on an IBM i Host).

Starting JSPM on Any Operating System except IBM i

Note Note

When JSPM is started it automatically starts its GUI on the local machine, that is the machine JSPM is running on. If SAP system is on UNIX and a Windows PC is used as a client this requires some kind of X server software to run on the Windows PC to display JSPM GUI.

We recommend that you redirect JSPM GUI to a Windows machine using Hummingbird Exceed software. Other X servers (like XMing) cannot be guaranteed to work flawlessly. In this case the whole eventing mechanism of Java Swing seems to be improperly transported back and forth, leading to an unresponsive GUI.

While it is possible to run JSPM GUI in X-Windows on UNIX systems, this setup has not been validated by SAP and is not guaranteed to work.

If such a functionality is necessary, we recommend that you use JSPM remote UI. See below for details.

End of the note.

Note Note

We recommend that to speed up the update procedure, you should select an instance on the most powerful machine with the fastest access to the database. Additionally you can stop the other AS Java instances before the update and start them after that.

End of the note.

  1. In the file system, go to the /usr/sap/<SID>/<Instance name>/j2ee/JSPM directory.

    Note Note

    Depending on the system, the name of the primary application server instance has the following syntax:

    End of the note.

    • For a standalone system - J<xx>

    • For an add-on system - DVEBMGS<xx>,

      where xx is the number of the primary application server instance.

  2. To start JSPM, run the go script file.

    Note Note

    In this step you can specify a temporary inbox directory. For more information, see Detecting and Changing the Global EPS Inbox Directory.

    End of the note.
Starting JSPM with Remote UI

Start JSPM with this command line:

go -remoteui

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:

http://<host>:5<xx>19

<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.

Starting JSPM on an IBM i Host

  1. Run the go script on the IBM i host using the following command:

    CALL PGM(QP2TERM) PARM('/usr/sap/<SID>/<primary application server instance>/j2ee/JSPM/go')

    JSPM is starting. This process might take some time.

    Note Note

    You always can end your terminal session by pressing F3. This will not stop the JSPM.

    End of the note.

    Note Note

    A job JSPM starts in the subsystem of your primary application instance on your IBM ihost.

    End of the note.

  2. Open a web browser on a GUI capable host and go to http://<host>:5<instance_number>19.

  3. To open JSPM GUI, choose Start JSPM Frontend (SDTGui).

    Note Note

    When you stop the JSPM, the job JSPM disappears in your subsystem of your primary application instance on your IBM i host. The local port 5<instance_number>17 will take a few minutes until it is released. Before local port 5<instance_number>17 on IBM i is not free, you will not be able to start the JSPM again. Use the command NETSTAT option 3 to check the local port 5<instance_number>17 and then use option 4 to end the port (if required).

    End of the note.