SAP NETWEAVER

JAVA Tools
Visual Admin
Configtool
SDM
JSPM
NWA
3
Visual Administrator
The J2EE Engine Visual Administrator is a
graphical user interface (GUI) that enables
administration of all cluster elements and all
modules running on them. It provides remote
monitoring and management of managers,
services, libraries, and interfaces working on
each element in a single GUI.
4
Features

Generally used to run administration tasks, such
as look at log files, changing key store etc
Requires the Java engine to be running
Password protected
Replaced by NWA for NW AS Java >= 7.1
Can connect to multiple Java engines (one at a
time!)
Visual Admin



7
Visual Administrator: Overview
There are two different views in the Visual Administrator: the view for global
configuration, and the view for local configuration, which is also called cluster
configuration.

With cluster configuration, all active nodes of the cluster are
visible and can be maintained with the Visual Administrator.

In the case of global configuration, a distinction is made between maintaining the
dispatcher nodes and the server nodes using the corresponding tab pages.
Visual Admin
Configuration tool(Config Tool)
Generally used to make changes to VM (virtual
memory) settings, and and remove server nodes
and change UME (user management engine)
Requires the Java database be started
Is not password protected (uses a secure
storefor authentication)
Also leads to the configuration editor
Configtool
Configtool by default is read only, but can be changed into
read/write to make changes. The Java engine should be stopped
(but of course, not the underlying database) before any changes
are made.
Config Tool: Overview
The window on the left in the Config Tool displays the structure of the
cluster in global settings and in settings for the individual cluster elements.
The cluster elements are always assigned to an instance with an instance
number. This instance number is also contained in the name of the dispatcher
or server processes.
Configuration of the Java VM Settings with the Config
Tool
The settings for the Virtual Machine (VM) are maintained with the Config
Tool. We maintain the VM Settings by selecting a dispatcher or server node
of the instance in the window of the left of the Config Tool. The VM
parameters with their settings then appear in the window on the right. The
runtime parameters are on the General tab page. See also the figure VM
Settings. The Bootstrap tab page contains the settings for the start process
NetWeaver Administrator (NWA)
Browser based tool to manage Java engine, including
starting and stopping
Java engine must be running
Password protected
Runs as a servlet on the Java engine
(http://portal:port/nwa)
Administration in the NWA:
The Administration area in the NWA contains areas for
system and applicationadministration as well as for user
management.
Starting and stopping instances (see figure: SAP NWA: System
Administration).
Starting and stopping cluster elements (dispatcher, server,
SDM)
Starting and stopping applications

If it is necessary to start or stop instances or cluster nodes the
authentication via the operating system user <sid>adm is required
Software Deployment Manager (SDM)
The Software Deployment Manager (SDM) is the standard tool that you use
to install J2EE components on the SAP J2EE Engine. The SDM is a
client/server application. The SDM Server runs on the SAP J2EE Engine
side. This server is started automatically with the J2EE Engine. A graphical
user interface is available as a client.
Features
SDM Modes
Starting and Stopping the Software Deployment Manager
Working with the Graphical User Interface (GUI)
SDM Repository
Deployment
Undeployment
Log Viewer

SDM Modes
Use
SDM modes allow you to specify how to run the Software Deployment Manager
(SDM) in relation to the J2EE Engine.
Integration
The SDM modes determine if the SDM will have link to the Java
Control Framework or not.
Features
The following SDM modes are available:
Standalone the SDM does not have a link to the Java Control Framework
Integrated the SDM does have a link to the Java Control Framework

Changing SDM Modes
Prerequisites
To change the SDM mode, you need to stop the SDM Server as described under Starting
and Stopping the Software Deployment Manager.
Procedure
To remove the link between the SDM and the Java Control Framework, proceed as
follows:
1. Navigate to the usr/sap/<SID>/<INSTANCE_NAME>/SDM/program directory
of your J2EE Engine.
2. Open a command prompt in this directory.
a. To remove the link between the SDM and the Java Control Framework execute the
following command in the command line:
sdm jstartup "mode=standalone" for Windows
sdm.sh jstartup mode=standalone for UNIX
b. To integrate the SDM in the Java Control Framework, use the following command:
sdm jstartup "mode=integrated" for Windows
sdm.sh jstartup mode=integrated for UNIX
3. Start the SDM Server again as described under Starting and Stopping the Software
Deployment Manager.

SDM
JAVA SUPPORT PACK MANAGER(JSPM)
We can use the Java Support Package Manager (JSPM) to apply
support packages on deployed software components.
We can also deploy SAP and third-party software components to
which you can then apply support packages and patches.
Wecan deploy new business packages of mySAP Business Suite.
We can also upgrade and update business packages of mySAP
Business Suite that are deployed on the system to a higher release
and support package level respectively.
In addition, JSPM detects SAP software components that have
been modified and allows you to apply support packages to
them.
Features of JSPM
Integration
JSPM connects to the SDM server to deploy support packages and
software components. The SDM server performs additional validation of the
support packages and software components for deployment.
JSPM is integrated with the SAP NetWeaver Development
Infrastructure (NWDI). JSPM detects SAP software components that have been
modified and allows you to apply support packages to them.
JSPM has the following features
Maintenance certificate
We can update SAP components only if you have a valid maintenance certificate.
Usability
Offers a simple and intuitive graphical user interface (GUI)
Shares common GUI with SAPinst and SAPJup
Automatically detects and offers you only components that can upgrade
deployed components
Shows only necessary information. Shows additional details at your request.
Starting JSPM

Prerequisites
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
subdirectories: /usr/sap/<SID>/SYS/exe and /usr/sap/<SID>/SYS/profil
e. 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.
JSPM Contd
For Windows OS
With runas command
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