Page tree
Skip to end of metadata
Go to start of metadata

There are three different tools that are used to do certain Java engine administration tasks. This attempts to describe each.

The NetWeaver Administrator is designed to replace Visual Administrator in future releases.

This wiki page contains details about the main tools plus a link to some common activities that a portal administrator might need to do with the tools.

Some common tasks.

This is a list of any child pages with the label ep_admintasks.

The tools.

Configuration tool (aka 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

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

Visual administrator

  • 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!)

After connecting (and waiting for some time...)

The Visual Administrator can be deployed to a Windows desktop by taking the whole admin folder and copying it to the desktop and installing a JRE.

On Windows, the admin folder is at disk:\usr\sap\<SID>\JCnn\admin

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)