Displaying Applications 

Use

The application display in the VMC System Administration provides the following overview information and administration options:

●     Overview of Java applications activated on the instance

●     Overview of activation groups

●     Overview of components installed in the database (instance-specific)

●     Options for changing the configuration data stored in the database (instance-specific)

Prerequisites

To understand the terminology used, read the following sections in the architecture part of the documentation:

Java Applications in the VM Container

Life Cycle of Active Applications

Architecture of the VM Container

Procedure

On the initial screen of the VMC system administration (SM53) in the structure on the left side under Navigation choose Applications.

A hierarchical structure is displayed containing the following areas: Activated Applications, Activation Groups, one or multiple Installations (with timestamps) and Configuration.

The areas are described in detail below:

Activated Applications

If you open the node Activated Applications, you can see the applications activated on this instance. Each activation is identified by a unique ID number and the component name. The subnodes show the associated bindings, the resources used, and, if available, obsolete versions of the application. Choose In Sessions to see which sessions and activation groups the activation contains.

Activation Groups

Each activation group has a unique number. An activation group corresponds to a session (see Displaying and Managing Sessions): it combines all applications running in this session.

The names of the activations in this group are shown as a subnode of the activation group ID. They also appear under Activated Applications. The subnodes are the same as the ones for activated applications.

These nodes are also instance-specific.

Installation

Beneath this node you can see the components that are installed in the database.This node is not instance-specific so you may see components that are not currently running on this instance.

An installation has the following subnodes:

●     Components: You can see the name of the component and the associated modules, files, and bindings.

●     Bindings: Here you can see an overview of all the bindings of the installation, usually bindings from several components.  

●     Imports: This displays the transport tables, and is not specific to the timestamp. The installation status, component name, date, and time of the installation are shown for each module. The installation status can have the following values:

○     New: The module has been imported into the system, but is not yet installed in the database. Choose  Integrate Transports to copy the module from the transport tables into runtime tables.

○     Installed and Active: The module is installed and activated in the database.  You can also find it under Installation under the relevant module.

○     For Deletion: The module is selected for deletion, which means the module is still active but will become inactive when the next transport is integrated.

○     Installed but Inactive: The module is installed but is inactive (deleted).

○     With Errors: an error occurred during installation.

You can perform the following actions when installing a module. For background information about the processes and operations see Java Applications in the VM Container.

●      Install Components. You can install components from your local PC.

You should only use this function in consultation with SAP.

●      Integrate Transports. You can trigger data transfer from transport tables into runtime tables.

You should only use this function in consultation with SAP.

●      Clean Up Database This performs a compaction operation on the database – versions no longer needed are removed and space is freed up.

●      Selection with Timestamp. This lets you display the components installed at the time you specify (not in the future).  Choose  Selection with Timestamp and enter a timestamp in the format YYYYMMDDHHMMSS. You will get another installation node showing the installation that existed at the time specified. The timestamp shows the time when the last installation was made.

 

If you enter the timestamp 20051109160000, you will get a node of type . The installation was changed on the 7 November at 6pm, and not again until 9 November at 4pm.

As soon as the tree is refreshed, the nodes created with Selection with Timestamp disappear, and you see only the one system installation node.

Configuration

There are configuration files for some components installed in the database.  Under the node Components you see a node with the component name and underneath this are further nodes named after components.Beneath this node you will find the subnodes SAP configurations and customer configurations.

You cannot change the SAP configurations, but you can create a copy of each SAP configuration as a customer configuration and then overwrite the SAP configuration values. To do this choose a configuration version from the SAP configurations. On the right you see the settings.Above the right-hand frame choose  New Customer Configuration.

This configuration then exists as a new version under customer configurations, and you can change it using  Edit, Save, and Activate. To edit it you have to double-click the specific entry.The customer configuration of a component always overrides the associated SAP configuration. To return to the SAP configuration, simply delete the changes to the customer configuration.