Starting and Stopping 

This section describes the sequence in which you stop and start the components in the portal landscape.

In a secure and highly available production environment, other third party tools, such as a proxy server, also play a role in the portal environment.

For more information about starting and stopping, see Starting and Stopping SAP Systems and Instances.

Purpose

Use the information in this section to stop and start portal processes in your system landscape: in which all the components of the portal reside on a single machine, or in a production environment within which the portal has been clustered and made highly available.

Prerequisites

The portal works with the following systems:

●     A relational database management system (RDBMS)

●     An existing user storage mechanism, Users Persistence Storage, such as a directory service (LDAP). These systems are prepared before the portal is installed.

●     SAP Web Application Server

Before you stop or start components in the portal landscape, make sure that:

●     The portal runs without any issues

●     You have administration rights and privileges to start and stop the processes of the  components of the portal

Workflow

There are occasions when you may need to shut down the portal environment, for example, to perform system maintenance such as offline backup and so on.

Stop Sequence

To shut down the portal environment, you must stop the processes of the various portal components. The following is the sequence for stopping the components in the portal landscape:

...

       1.      JAVA instances of the SAPWeb Application Server

       2.      Database

       3.      User Persistence Store

Start Sequence

The following is the sequence for starting the components in the portal landscape:

...

       1.      User Persistence Store

       2.      Database

       3.      JAVA instances of the SAP Web Application Server

Starting and Stopping the J2EE Engine

The portal is installed on an instance of the J2EE engine of the SAP Web Application Server, as such, starting and stopping the J2EE instances affect portal functionality.

For more information about starting and stopping J2EE instances, see Starting and Stopping the SAP System.

For more information about the J2EE startup framework, see Java Startup and Control Framework.