Show TOC

Background documentationChecking the Availability Without a Central System Locate this document in the navigation structure

 

If your AS Java is not connected to a central system, you cannot automatically check the availability of the main components, but must rather perform a few checks yourself.

The basic check should be:

  • Are the servers of the Java cluster running?

  • Is the database running?

  • Is the Web Container running?

  • Can I connect to the Visual Administrator?

If you have connected to the Visual Administrator, you can choose the Monitor Service and check the status of the system and the individual managers and services there.

Are the Servers of the Java Cluster Running?

In the SAP Management Console, check whether the J2EE Engine is actually running.

The processes of the J2EE Engine are usually started as services or daemons. Thus, you must also initially check whether these processes are actually running. Under Microsoft Windows, you can do this in the SAP Management Console.

The Management Console displays all the installed components in a hierarchy. When you open the hierarchy, an icon for each server instance appears; this icon may be green, yellow, or gray. The system database is a blue icon.

A completely gray server indicates that the server has been shut down, while a completely or partly yellow display indicates that there is a problem with a subsystem.

You can find the relevant system by opening the other subtrees.

Is the Web Container Running?

You can use a Web browser to check whether at least the Web Container of the system is running. In your browser, enter: http://<hostname>:50000, where <hostname> is the name of the computer in the network on which the J2EE Engine is installed.

This should display the standard Web page of the server in the browser, which displays a graphic, the name of the server, and a number of links to examples and documentation. If this is displayed, you can move to the next step.

If an error message is displayed, you should consider the following:

  • You could have used the wrong <host name>.

  • The server's standard port for HTTP could have been changed.

  • The basic configuration of the server could have been changed.

Server error messages (such as the HTTP 404 or 500 errors) mean that the server is definitely active and basically functioning.

Is the Visual Administrator Working?

Open the Visual Administrator.

When logging on to the server, you can choose three different protocols for communicating with the server:

  • No Layer This option uses the protocol P4, an internal server protocol, that you usually only use hidden.

  • HTTP Tunneling Use HTTP Tunneling if you want to administer the server through a firewall, as it uses the HTTP protocol to pass the firewall using this port.

  • SSL and HTTPS Only relevant if you need to use secure connections.

Once you have successfully created a connection to the server, you can check whether all services are functioning correctly. The Visual Administrator displays the services in a tree structure. Under Services, you can quickly gain an overview of which services are inactive, as a red cross indicates these there.