Technical Operations Manual for SAP NetWeaver

Designing, implementing, and running SAP NetWeaver at peak performance 24 hours a day has never been more vital for your business success than today.

This guide provides a starting point for administrators in procedures for the optimal operation and use of SAP NetWeaver. It contains specific information for various administration tasks, and lists the tools that you can use to carry them out. It also refers to documentation required for these tasks. You can use this guide only in connection with other guides such as the Master Guide, and the SAP Library.

Constraints

In this document, it is assumed that the system or systems are running, or could at least be started once. This documentation therefore contains no information about installation. Configuration tasks are only described if they also occur during running operation.

About this Document

With SAP NetWeaver 2004s, installable software units (systems, Standalone Engines, and client) and IT scenarios have been defined. The documentation in this operations manual reflects the new concept.

For more information about the new division into installable software units and IT scenarios, see section 3 of the Master Guide (http://service.sap.com/installnw2004s ® Master Guide). For more information about IT landscapes, see section 4 of the Master Guide.

This Technical Operations Manual is accordingly structured into the following main sections:

Sections	Description of the Subsections
General Administration	Contains over-arching topics that cannot be specifically restricted to one SAP NetWeaver system or one standalone engine, such as high availability, security and user administration, database administration, system copy, and licensing.
Administration of SAP NetWeaver Systems	Contains the administration tasks for SAP NetWeaver systems on which one or more Usage Types of SAP NetWeaver are installed and configured. The Usage Types of SAP NetWeaver, which you can select during installation, include: · Application Server ABAP (AS ABAP) · Application Server Java (AS JAVA) · EP Core (EPC) · Enterprise Portal (EP) · Business Intelligence (BI) · Mobile Infrastructure (MI) · Process Integration (PI), which covers the contents of the previous product component XI · Development Infrastructure (DI)
Administration of Standalone Engines	Contains the administration tasks for additional installable entities that function “standalone”, and which are not really SAP NetWeaver systems. They provide a specific server function in combination with one or more Usage Types of SAP NetWeaver, which include: · Search and Classification (TREX) · SAP liveCache Technology · RTC Application Sharing Server · SAP Content Server · SAP NetWeaver Landscape-Wide Job Scheduler · SAP Web Dispatcher · Standalone Enqueue Server
Administration of Client Programs	Contains the administration tasks for client programs. Client programs are additional installable programs that are either on the local front end PCs of users or on backend systems. They are used to access functions of NW systems or standalone engines in landscapes. These include: · SAP NetWeaver Developer Studio · J2SE Adapter Engine (PI) · SAP NetWeaver Developer Workplace
Administration of SAP NetWeaver IT Scenarios	Contains administration information that is specific to the individual IT scenarios.

The subsections include information about the following points (if available):

· Technical system landscape (architecture)

· Monitoring

· Administration (tasks); these can be divided into periodic tasks and “on demand” tasks

· Software Logistics

· Troubleshooting

Example

During installation, you have selected the Usage Type Process Integration (PI) in addition to Application Server for Java (AS Java) and Application Server for ABAP (AS ABAP), and require more information about the administration of a specific PI scenario, such as Enabling Application-to-Application Processes or Enabling Business-to-Business Processes.

In this case, for basic information that applies equally to all scenarios that use PI, such as user administration, logging, and tracing, and software logistics, see the Technical Operations Manual, Administration of SAP NetWeaver Systems section ® PI subsection.

For information about additional administration tasks for the scenarios, such as monitoring in the Partner Connectivity Kit (PCK), see the sections for the relevant scenarios under Administration of SAP NetWeaver IT Scenarios.

Starting and Stopping SAP NetWeaver ABAP and Java

When you start SAP NetWeaver, you start the system database, the application servers, and the respective processes of which the system consists.

In general, the database starts first, and then the instance. When you start the central instance, the database is therefore automatically also started. However, the database is not stopped when you stop the central instance.

The following sections describe how you start and stop SAP NetWeaver ABAP, Java and the add-in installation (ABAP + Java). The description is limited to the activities in the case of a central system that consists of a database and a central instance (ABAP, Java, ABAP + Java) on one host. Only Microsoft Windows and UNIX are considered at operating system level:

Starting and Stopping SAP NetWeaver ABAP Under Microsoft Windows

Starting and Stopping SAP NetWeaver Java Under Microsoft Windows

Starting and Stopping SAP NetWeaver ABAP Under UNIX

Starting and Stopping SAP NetWeaver Java Under UNIX

In the case of an add-in installation (ABAP + Java), when you start and stop ABAP instances, the corresponding Java instances are automatically also started and stopped, by default. If you want to deactivate the automatic starting of the Java instances, you need to set the instance profile parameter rdisp/j2ee_start to the value 0 in transaction RZ10. You can then restart the Java instance as described in the section Restarting the Java Stack of an SAP NetWeaver Add-In Installation. When you stop an ABAP instance, however, the associated Java instance is always also stopped.

Additional Information

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

· For information about starting and stopping Application Services (such as SAP instances) with Adaptive Computing, see Starting and Stopping Application Services with Adaptive Computing.

Adaptive Computing is only supported if you are using the Adaptive Computing Controller 1.0 for SAP NetWeaver Release ’04 (see SAP Note 725397). However, the Adaptive Computing Controller 1.0 can control all releases from SAP R/3 4.6C to SAP NetWeaver 2004s (Managed Adaptive Landscape).

Starting and Stopping SAP NetWeaver ABAP Under Microsoft Windows

Proceed as follows to start and stop SAP NetWeaver ABAP under Microsoft Windows:

Starting

...

1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in.

2. Select the system ID of your system and open the context menu by right-clicking.

3. Choose Start.

The database, all ABAP instances, and all additional processes of your system are started. If all instance icons appear green, the start was successful.

In the case of an add-in installation (ABAP + Java), the Java instances are automatically started together with the corresponding ABAP instances.

Stopping

4. Start the Microsoft Management Console (MMC) that contains the SAP snap-in.

5. Select the system ID of your system and open the context menu by right-clicking.

6. Choose Stop.

In the case of an add-in installation, the Java instances are automatically stopped together with the corresponding ABAP instances. If all instance icons appear gray, the stop was successful.

The database is not stopped automatically when you stop SAP NetWeaver. Use database-specific tools to stop the database. For more information, see database administration.

Example

The figure below shows the started instances of system NBS.

Starting and Stopping SAP NetWeaver Java Under Microsoft Windows

Proceed as follows to start and stop SAP NetWeaver Java under Microsoft Windows:

Starting

...

1. Start the Microsoft Management Console (MMC) that contains the SAP snap-in.

2. Select the system ID of your system and open the context menu by right-clicking.

3. Choose Start.

The database, all Java instances, and all additional processes of your system are started. If all instance icons appear green, the start was successful.

Stopping

4. Start the Microsoft Management Console (MMC) that contains the SAP snap-in.

5. Select the system ID of your system and open the context menu by right-clicking.

6. Choose Stop.

If all instance icons appear gray, the stop was successful.

The database is not stopped automatically when you stop SAP NetWeaver. Use database-specific tools to stop the database. For more information, see database administration.

Example

The figure below shows the stopped instances of system J2E:

Starting and Stopping SAP NetWeaver ABAP Under UNIX

Proceed as follows to start and stop SAP NetWeaver ABAP under UNIX:

Starting

...

1. Log on to the host of your central system as the SAP administrator adm.

2. Enter startsap ALL to start SAP NetWeaver ABAP.

The database, the ABAP instances, and all other processes for your system are started on this host.

In the case of an add-in installation (ABAP + Java), the Java instances are automatically started together with the corresponding ABAP instances.

Stopping

3. Log on to the host of your central system as the SAP administrator adm.

4. Enter stopsap R3 to stop SAP NetWeaver ABAP.

In the case of an add-in installation (ABAP + Java), the Java instances are automatically stopped together with the corresponding ABAP instances.

The stopsap command with the R3 switch does not stop the database simultaneously. If you want to stop the database simultaneously, use the command stopsap or stopsap ALL.

Starting and Stopping SAP NetWeaver Java Under UNIX

Proceed as follows to start and stop SAP NetWeaver Java under UNIX:
Starting

...

1. Log on to the host of your central system as the SAP administrator adm.

2. Enter startsap ALL to start SAP NetWeaver Java.

The database, all Java instances, and all other processes for your system are started on this host.
Stopping

3. Log on to the host of your central system as the SAP administrator adm.

4. Enter stopsap J2EE to stop SAP NetWeaver Java.

Note

The command Stopsap with the switch J2EE does not stop the database simultaneously. If you want to stop the database simultaneously, use the command stopsap or stopsap ALL.

Restarting the Java Stack of an SAP NetWeaver Add-In Installation

With an add-in installation, a Java instance is assigned to an ABAP instance. The Internet Communication Manager (ICM) of the ABAP instance starts and stops the associated Java instance as required.

Proceed as follows to restart the Java stack of your SAP NetWeaver add-in installation (ABAP + Java):

...

1. Log on to the ABAP stack of SAP NetWeaver.

2. Open the list of SAP servers by calling transaction SM51.

3. Double-click the instance for which you want to restart the Java stack.

You are now connected to the selected instance.

4. Start the ICM Monitor (transaction SMICM) by entering /nSMICM in the command field.

5. In transaction SMICM, choose Administration ® J2EE Server ® Send Soft Shutdown ® With Restart.

6. The corresponding SAP NetWeaver Java stack for your instance is stopped and restarted.

Starting or Stopping Application Services via Adaptive Computing

The procedure for starting and stopping the application services with Adaptive Computing is discussed in the corresponding section:

Adaptive Computing is only supported by using Adaptive Computing Controller 1.0 only running on SAP NetWeaver Release '04 (see SAP Note 725397) which of course can adaptively control all releases from SAP R/3 4.6C up to SAP NetWeaver 04s.

Starting an Application Service:

To access this information, go to: help.sap.com and choose Documentation ® SAP NetWeaver ®Adaptive Computing Controller 1.0, navigate to Adaptive Computing Controller Main Window ® Logical Landscape ® Application Service Detailed Information ® Application Service ® Starting an Application Service.

.

Stopping an Application Service:

To access this information, go to: help.sap.com and choose Documentation ® SAP NetWeaver ®Adaptive Computing Controller 1.0, navigate to Adaptive Computing Controller Main Window ® Logical Landscape ® Application Service Detailed Information ® Application Service ® Stopping an Application Service.

High Availability Netweaver

The tasks for the system administrator depend on the high availability features that you have implemented. In general, you need to minimize both planned downtime and unplanned downtime for your SAP system. The tasks listed below are important to minimizing downtime in your system.

Getting Started

For a full checklist of what features you need to consider when designing high availability into your system, see General Checklist. Consider especially switchover software.

High availability is a technically complex area, and implementation considerations vary according to your system setup.

For technical guidance when developing a high availability strategy or when implementing a specific product or feature, contact the appropriate source, such as your SAP consultant or your hardware partner.

For more information, see SAP Note 803018 and the SAP High Availability documentation.

Technical System Landscape

For more information on a system landscape for high availability, see the Technical Infrastructure Guide – SAP NetWeaver 2004s at:

service.sap.com/installNW2004s ® Planning

Tasks on Demand

Reason	Task	More Information
System failure	Restore database	Database Administration
SAP system upgrade required	Upgrade SAP system	service.sap.com/upgrade service.sap.com/nw04upgrade ® Upgrade
Database upgrade required	Upgrade database	service.sap.com/instguides ® Other Documentation ® Database Upgrades
Operating system upgrade required	Upgrade operating system	Operating system documentation

Periodic Tasks

Frequency	Task	More Information
Regularly	Test switchover functionality	service.sap.com/ha ® Media Library ® Documentation ® Switchover
Regularly	Database backup, online or offline, possibly with split-mirror	Database Administration

How often you perform the periodic tasks depends on the requirements and nature of your installation.

For example, the frequency with which you expect a switchover to occur determines how often you test switchover functionality – if you expect frequent switchovers you need to frequently test switchover functionality.