Table of Contents

1.1 Attachments..............................................................................................4 1.2 Change History.........................................................................................4 1.3 Document Reviews and Audits.................................................................4 1.4 Document purpose....................................................................................4 2. Document updates and distribution.............................................................5 2.1 Document distribution list........................................................................5 2.2 Rules for revision of document.................................................................5

Handbook Mlnlycke Health Care SAP PI Systems

3. Monitoring routines.......................................................................................5 3.1 Persons Working with System Monitoring...............................................5 3.1.1 Problem Handling.............................................................................6 3.2 Monitoring Tools .....................................................................................7 3.2.1 CA Unicenter TNG (External Tool).................................................7 3.2.2 Solution Manager..............................................................................8 3.3 System Management.................................................................................8 3.3.1 Monitoring Activities PI System.......................................................8 *Daily = Once a day in the morning.......................................................10 3.3.2 Work Processes...............................................................................10 3.3.3 Update Error Handling ...................................................................10 3.3.4 ABAP Dumps ................................................................................10 3.3.5 Lock entries.....................................................................................11 3.3.6 System log.......................................................................................11 3.3.7 Backup status..................................................................................11 3.3.8 System performance........................................................................11 3.3.9 Tuning Buffers................................................................................12 3.3.10 Update TCC Tool..........................................................................12 3.4 Integration Adapters...............................................................................12 3.5 Adapter and interface overview..............................................................12 3.6 System Maintenance Downtime.............................................................12 3.6.1 Stopping and Starting the PI System...............................................13 3.7 Background Processing...........................................................................14 *Daily = Once a day in the morning.......................................................15 3.7.1 Periodic Jobs...................................................................................15

3.8 Transport routines..................................................................................15 3.8.1 Transport Management Systems ..................................................................................................................15 3.8.2 Change Management Service..........................................................16 3.8.3 TREX..............................................................................................16 3.8.4 WEB Dispatcher.............................................................................17 3.9 Users, Authorizations and Profile Generator..........................................18 4. Printing.........................................................................................................18 5. Database Administration ORACLE..........................................................18 5.1 ORACLE ...............................................................................................18 5.1.1 Database performance.....................................................................19 5.1.2 Starting and Stopping an ORACLE Database................................19 5.1.3 DBA Planning Calendar..................................................................20 *Daily = Once a day in the morning.......................................................20 5.2 Backup Strategy......................................................................................20 5.2.1 Backup schema...............................................................................21 5.2.2 General information for recovery of system landscape..................22 5.3 Database Growth Management...............................................................22 *Daily = Once a day in the morning.......................................................23 5.4 Database Performance............................................................................23 5.4.1 Database Reorganization.................................................................23 5.4.2 Quickly growing tables ..................................................................23 6. SAP Exchange Infrastructure (PI).............................................................24 6.1 Hardware Components...........................................................................24 6.1.1 System Landscape ..................................................................................................................25 6.2 Software Components ............................................................................25 6.3 Availability Plan.....................................................................................25 6.4 Monitoring Components.........................................................................25 *Daily = Once a day in the morning........................................................26 6.4.1 Integration Engine - Monitoring ....................................................26 6.4.2 Start Integration Builder..................................................................27 6.4.3 Integration Engine - Administration..............................................27 6.4.4 Test SLD Connection .....................................................................28 6.4.5 Certificates......................................................................................28 6.4.6 Business Processes Engine (BPE)...................................................28 6.4.7 Queue Monitoring ..........................................................................28 6.4.8 Outbound/Inbound scheduler queue ..............................................30 6.4.9 Communication Monitoring............................................................31 *Daily = Once a day in the morning.......................................................31 6.4.10 Relevant SAPNet Notes................................................................32 6.5 Third party and PI environment..............................................................32

6.5.1 JDBC integration through the database. .....................................32 6.5.2 XML................................................................................................32 6.5.3 Java proxy.......................................................................................32 6.5.4 Flat file............................................................................................32 6.5.5 Runtime Workbench.......................................................................33 6.5.6 Integration Builder..........................................................................33 6.5.7 System Landscape Directory..........................................................33 6.5.8 Integration Clients...........................................................................33 6.5.9 Proxy Framework............................................................................34 6.5.10 Internal communication................................................................34 6.5.11 External communication.............................................................35

Document information 1.1

1 2

Attachments
Number Title Service window Capgemini Acando 3.1.1.2 Date Version

1.2
0.9 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9

Change History
Version Date 2007-05-30 2007-06-07 2007-06-13 2007-06-14 2007-06-27 2007-07-09 2007-09-05 2007-09-25 2007-10-18 2007-11-15 2007-12-28 Changed by Peter Wastelius Anette Hallgren, Gran Karlsson Anders Damm Anette Hallgren Anette Hallgren Susanne Eriksson Anette Hallgren Anette Hallgren Anette Hallgren Susanne Eriksson Susanne Eriksson
Update contactlist Small changes after review by Susanne E. Update according to input EDB and ICC Update according to input Anders Damm Update contact information Updated due to implementation of automatic monitoring of PIP Add information about scripts for SMQ1 and SMQ2

Change

1.3

Document Reviews and Audits

Date Name Position

1.4

Document purpose

This document describes the overall actions needed for maintenance of Mlnlycke Health Care`s SAP PI system. It includes daily/weekly/monthly/initial actions needed by AM Acando and IM EDB. The purpose of this document is to: Guide AM Acando and IM EDB in normal delivery, actions to fulfil agreed SLAs Mlnlycke Health Care, MHC through this document.

2.
2.1

Document updates and distribution Document distribution list

Name Anders Damm Jane Lundstrm Henrik Virking ERP Analysteam MHC Krister Jnsson Jan Kll Company MHC Capgemini EDB EDB EDB Acando Role SAP Basis Service Manager Service Manager SAP Basis, Oracle DBA SAP Solution Architect Account Manager

2.2

Rules for revision of document o Document owner: Service Manager Capgemini. o Revision of the document should be done once per year and when changing SLA, upgrades etc. o EDB will perform updates of the document. This will be handled as a CHR (Change Request). o Document updates and changes (everyone is permitted to initiate changes) need to be confirmed with permitted persons. Latest version of the document is saved in EDB:s documentation system webdoc.

Persons permitted to approve changes See 2.1

3.
3.1

Monitoring routines
Persons Working with System Monitoring
Role AM / PI Comment Contact Phonenumber

PERSONS WORKING ON SYSTEM MANAGEMENT Company Acando

solutionsupport@acando.com

0200 11 11 55
+46

31 21 92 14 (from abroad)
Acando EDB IM EDB IM MHC MHC AM/PI SAP Basis DBA Helpdesk AM (ICC) PI AM (ICC)
TNG, scripts, Daily monitoring

Jan.kall@acando.com
ore-erp.analysteam@edb.se helpdesk.mhc@edb.com

+46 31 345 34 16 +46 19 766 49 50

+46 19 766 49 50

iccsupport@molnlycke.com mirela.nilsson@molnlycke.com +46 31 722 30 18

Company MHC MHC

Role AM (ICC) AM (ICC)

Comment

Contact

Phonenumber

tommy.claesson@molnycke.com henrik.liljedahl@molnlycke.com

+46 31 722 32 14 +46 31 722 33 24

3.1.1 Problem Handling This section includes problem-handling procedures IM EDB and AM Acando. 3.1.1.1 IM - EDB

The EDB Helpdesk is available for problem reporting 00:00-24:00, 7/24.

Service level Avail. target Prime Service Hour Service Hour (Supervision) 00:00 - 24:00 (7/24) 00:00 - 24:00 (7/24) 00:00 - 24:00 (7/24) Prime Support Time Prio 1-6 cases 08:00 17:00 Weekdays 08:00 17:00 Weekdays 08:00 17:00 Weekdays Support Time Prio 1 and 2 case 00:00 24:00 (7/24) Help Desk Reporting 00:00 24:00 (7/24) 00:00 24:00 (7/24) 00:00 24:00 (7/24)

High Normal Low

99,93% 03:30 17:00 Weekdays 99,50% 98,00%

Definitions: Service Hour Up-Time Down-Time Availability Prime support time Support time

Time when the system is planned to be up and running, open for use and users. Time when the system has been up and running, open for use and users. Time when the system has NOT been up and running. Percentages calculated. Handling all types of cases. Handling priority 1 and 2 cases.

Reported problems will be taken care of depending on priority.

Description Severity Definition Code 1 2 3 4 5 6 Start Resolution (Hours) Immediate Immediate 30 min 8 hours As agreed As agreed Complete resolution delay (Hours) 1 hour 4 hours 8 hours 3 days As agreed As agreed

All users affected and no available workaround Business critical process Internal business consequenses Workaround exist Service request, agreed delivery Request for change

Extremly High Very High High Medium Low RFC

Problems that have been detected in the daily monitoring will be taken care of by the responsible person. Basis failures -> an Ears ticket is made up, assigned to ORE_ERP. When prio 1, 2 and 3 a call to responsible (see 3.1) is also done. AM failures detected in daily monitoring -> an Ears ticket is made up assigned to ORE_SD_X_IT and the information is forward in a mail to Acando - Solution Support (see 3.1).

3.1.1.2

AM Acando

Acandos Helpdesk is available for service requests and problem reporting on normal working days and weekend see attachment.

Service windows CAP_o_Acando.xls

Problems that have been detected in the daily monitoring will be taken care of by the responsible part. AM failures -> is forwarded to Acando Solution Support. Acando report Basis failures to EDB Helpdesk (see 3.1). 3.2 Monitoring Tools

Purpose You are using external monitoring tools. Procedure Use external tools. 3.2.1 CA Unicenter TNG (External Tool) CA Unicenter For System Management CA Unicenters TNG is used. TNG ping control are used for all servers. TNG:s Unix-module is used for all servers to monitor file system usage, CPU and Memory utilization.

3.2.2 Solution Manager SAP:s centralized solution management platform that provides tools, integrated contents to support and monitor the system landscape. 3.2.2.1 Monitoring Routine Solution Manager

Production Solution Manager SMP (gylfe), check twice a day, service covered by Agreement:MHC IM 7*24 Check if http://10.245.1.207:50100/index.html is displayed No logon needed Start SAPGui, verify that the logon screen is displayed and client 100 is set as default. No logon is needed. You may have to add this system manually to saplogon.ini Ipaddress: 10.245.1.207 SystemID: SMP System Number: 01 Development Solution Manager SMD (grim), check twice a day, service covered by Agreement:MHC IM - 8-17 Check if http://10.245.1.204:50100/index.html is displayed No logon needed Start SAPGui, verify that the logon screen is displayed and client 100 is set as default. No logon is needed. You may have to add this system manually to saplogon.ini Ipaddress: 10.245.1.204 SystemID: SMD System Number: 01 These checks should be performed, one time in the morning (06.00-08.00) and one in the afternoon around 15,00 (swedish time)

3.3

System Management

3.3.1 Monitoring Activities PI System Purpose Regular task

Procedure Monitoring PI Systems is one of the important routine activities of the system administrator. System monitoring should be preventive in nature. The following table lists the PI monitoring tasks, including the menu path, responsible persons, and the frequency with wich the task should be performed. On which systems (Dev, Quality, Prod) the tasks should be performed should be listed in the agreement. The list does not include the monitoring tasks for the database system see 5.3 and queue monitoring see 6.4. As of November 2007 we have implemented automatic monitoring for some of the tasks. See column "CCMS below.
SMAP TASKS
Task Checking work process status Responsibl e IM/EDB Frequency (*Daily) Menu Path Tools | Administration | Monitor | System monitoring | Process overview Tools | CCMS | Control/Monitoring | Performance Menu | Setup/Buffers Tools | Administration | Monitor | System log Transactio n SM50 Action See 3.3.2 CCMS Implemented as automatic alerts in CCMS Implemented as automatic alerts in CCMS Implemented as automatic alerts in CCMS Implemented as automatic alerts in CCMS

Buffer tuning

IM/EDB

(*Daily)

ST02

See 3.3.9

Checking the system IM/EDB log

(*Daily)

SM21

See 3.3.6

Analyzing ABAP short dumps

IM/Action AM (*Daily)

Tools | Administration | Monitor | Dump analysis Tools | CCMS |

ST22

See 3.3.4

Monitor Java Components Checking the update service

IM/EDB

RZ20

IM/EDB

(*Daily)

Tools | Administration | Monitor | Update

SM13

Checking lock entries Checking background jobs

IM/EDB

*Daily

Tools | Administration | Monitor | Lock entries Tools | CCMS | Jobs | Maintenance

SM12

IM/EDB

(*Daily)

SM37

System performance IM/EDB

*Daily

Tools | CCMS | Control/Monitoring | Performance Menu | Operating System

ST06+

Not configured for the moment See 3.3.3 Implemented as automatic alerts in CCMS See 3.3.5 Will be implemented soon See 3.7 Implemented as automatic alerts in CCMS TNG See 3.3.8

Backup and archivelogs

IM/EDB

(*Daily)

DB12

See 3.3.7

Implemented as automatic alerts in CCMS

Service Tool Update

IM/EDB

Once a month

SE38 => rtcctool

See 3.3.10

*Daily = Once a day in the morning 3.3.2 Work Processes Transaction SM50 Process Overview displays information: Check that all processes have status working or running. If too many processes are in hold status, then it influences system performance. Typical reasons are: Debugging, CPIC activity, locks, updates, GUI (system waits for response from the SAPGUI front-end program, for example, for a remote function call (RFC)). PRIV indicates the work process has exceeded the limit of the SAP memory that is used by other processes. PRIV transactions are automatically ended when the user is not active in the transaction. You can set this parameter abap/heaplimit in the SAP system profile. If a work process aborts during its startup, the system automatically sets restart to No. This protects against endless attempts to restart a process if a database system is not available, or another serious problem is affecting the system. After correcting the problem, you can change restart to yes so that the system starts the work processes. Err indicate how many times a work process has aborted Sem normally, this field should be empty. If one or more semaphore numbers frequently appears, evaluate the performance of your system. Problem with processes been detected, System Administrator analyse and contact the process owner (user whose request is currently being processed) and notify before the process being cancelled. 3.3.3 Update Error Handling Purpose Update error, cancelled updates. Procedure Update errors in the system need to be investigated. Create EARS ticket and assign to team ORE_SD_X_IT. They will then forward information to Acando AM (Solution Support) for further investigation . 3.3.4 ABAP Dumps Purpose An ABAP dump has occurred.

Procedure No users in PI, so this is only relevant when background jobs fail If needed create EARS ticket and assign to team ORE_SD_X_IT. They will then forward information to Acando AM (Solution Support) for further investigation . 3.3.5 Lock entries Purpose Detect and rectify lock entry problems. Procedure Transaction SM12 In general, you should not delete lock entries manually with the deletion functions in lock management. Unreleased locks are almost always a symptom of a different problem. When you solve the problem, the lock entry will be released automatically. System Administrator analyses problem and might have to contact end-user for further investigation.

3.3.6 System log Procedure Transaction SM21 selects the time interval you want to display. Most of the problems that occur in the system appear in the system log errors and warnings need to be analyzed to avoid problems. System Administrator analyse the system log. If AM related issues appear create an EARS ticket and assign to ORE_SD_X_IT. They will then forward information to Acando AM (Solution Support) for further investigation .

3.3.7 Backup status Transaction DB12 displays BRBACKUP and BRARCHIVE logs and archive directory status (free space). This check won't be necessary when online backups via RMAN is implemented.

3.3.8 System performance Transaction ST06 - Check performance operating system (CPU average load, Memory and Swap space is monitored via TNG) and database performance.

Check for bottlenecks in this area, compare performance one day/week back for deviations. 3.3.9 Tuning Buffers Purpose Find bottlenecks in buffer parameters Procedure Transaction ST02 Check the overall values of the buffers. If red values occur we may have to adjust the buffer parameters. Create an EARS ticket.

3.3.10 Update TCC Tool Purpose Keep the tools needed for SAP Service Preparation up-to-date Procedure Start transaction SE38 and execute program RTCCTOOL. If something is marked as red please create an EARS ticket.

3.4

Integration Adapters

Purpose Procedure Integration Adapters are used to convert various protocols and data formats into the Integration Servers XML based message objects and vice versa. The Integration Server comes with some built in adapters but most adapters are additional components. 3.5 Adapter and interface overview

Acando is responsible and monitor interfaces and adapters in the PI systems.

3.6

System Maintenance Downtime

Maintenance: All servers are normally available except for: - Planned maintenance third Sunday each calendar month, between 15:00 18:00 - Full backup third Sunday each calendar month between 00:00 04:00 - Other planned maintenance (is to be agreed at least 3 weekdays before the actual stop and shall be communicated to involved Solution Groups, SDM and Customer.

3.6.1 Stopping and Starting the PI System Purpose Stop and / or start the PI system Prerequisite MHC informed, and MHC decides if maintenance is allowed Procedure The following table lists the tasks related to stopping the PI system, including the responsible person, and the frequency with which the task should be performed for the production system, the quality assurance system, and the development system. The database administrator or the PI System administrator is responsible for starting and stopping the PI System according to instructions in webdoc (EDB documentation system). Note: For detailed description stop and start of the PI system contact System Administrator EDB IM See 3.1
STOPPING ACTIVITIES Activity Displaying active users Responsible IM/EDB Frequency Before shutdown Menu Path Tools | Administration | Monitor | Performance | Exceptions/Users | Active Users | Users global Tools | Administration | Administration | System Messages | Create Tools | CCMS | Control/Monitoring | All work processes Tools | CCMS | Jobs | Maintainance Transaction AL08

Sending system messages

IM/EDB

Before shutdown

SM02

Displaying the status IM/EDB of work processes Displaying background jobs IM/EDB

Before shutdown

SM66

Before shutdown

SM37

Activity Checking adapters

Responsible IM/EDB

Frequency After startup

Menu Path RWB | Component Monitoring | Adapter Engine | Communication Channnel Monitoring

Transaction SXMB_MONI + Adapter & Communication channel monitoring in RWB R/3: SMQS

Stop Outbound OLTP R/3 queues

IM/EDB

Stop Inbound qRFC- IM/EDB queues

Before shutdown Reverse during start up Before shutdown Reverse during start up

SMQR

3.7

Background Processing

Purpose Regular task Procedure Background processing is used for tasks which require no user intervention during execution. The user is not required to be present. Examples of such tasks include: Archiving large data volumes on to paper or microfiche Transferring data from PI to other applications Converting large data volumes for particular PI reports Executing particular programs regularly or at specific times Administration for background processing includes scheduling jobs, and checking job logs and spool lists. The following table lists the tasks related to background processing, including the menu path, the activity group (person responsible), and the frequency with which the task should be performed. After PI installation or configuration changes, the technical team leader determines which background jobs are scheduled. New jobs, changes to jobs, and removal of jobs should be documented in the same ways as R/3; CRM, SCM and BW environment. Documents are stored in MHC Oracle Collaboration Suite.

TASKS FOR BACKGROUND JOBS

Task Scheduling Jobs Checking job status and job logs Responsible IM/EDB IM/EDB Frequency By request from MHC (*Daily) Menu Path Tools | CCMS | Jobs | Definition Tools | CCMS | Jobs | Maintenance Transactio n SM 36 SM 37 Implemented as automatic alerts in CCMS CCMS

*Daily = Once a day in the morning 3.7.1 Periodic Jobs Purpose Regularly task Procedure For an PI System to continue to function, it is necessary for specific jobs to be executed at more or less regular intervals. Depending on the application used, or whether or not you are using your own custom applications, additional jobs may be necessary. See also Note 820622: Standard jobs, reorganization jobs PI The following table is for standard jobs in PI.
SMAP TASK: REORGANIZATION JOBS Job Name
SAP_REORG_ABAPDUMPS SAP_COLLECTOR_FOR_JOBSTATISTIC SAP_COLLECTOR_FOR_NONE_R3_STAT

Program
RSSNAPDL RSBPCOLL

Start Time

Period
Daily Daily Hourly

Task
Delete old shortdumps Collect values for statistics None R/3 statistic collector Performance collector Job for monitoring Delete old jobs Delete old spool files Delete old job statistics

SAP_COLLECTOR_FOR_PERFMONITOR SAP_CCMS_MONI_BATCH_DP SAP_REORG_JOBS SAP_REORG_SPOOL SAP_REORG_JOB_STATISTIC

RSCOLL00 RSAL_BATCH_TOOL_DISPATCHING RSBTCDEL RSPO0041 RSBPSTDE

Hourly Hourly Daily Daily Monthly

3.8

Transport routines

3.8.1 Transport Management Systems Purpose ABAP customizing and SAP support packages. Procedure ABAP customizing is transported manually between the systems no routine is established for the moment .

Java specific customizing objects need to be copied manually between the systems on OS level, files (export import) until CMS is configured see 3.8.2. 3.8.2 Change Management Service Purpose CMS is designed for use in java development and is used to transport changes and customer development. Procedure CMS will be configured for the java customizing in the PI system landscape. Monitoring routines will be describe when CMS is in use. 3.8.2.1 Monitoring Routine CMS

Note: Manual routine described below is used until automatic monitoring is established. CMS CMP (hagbard) check connection twice a day, service covered by Agreement:MHC IM 7*24. Confirm that http://10.245.1.188:50100 is displayed Username and password is required see: password database. If problem with connection forward for further investigation -> ICC support and Solution support (see 3.1). Stop and start of CMS should be performed by system administrator EDB IM (see 3.1) 3.8.3 TREX A search engine service for PI communication that replicates business objects from the database into the TREX system. When a user enters a search query, the TREX system responds to it, not the database. 3.8.3.1 Monitoring Routine TREX

Note: Manual routine described below is used until automatic monitoring is established. Production system TREX TXP (brimer), check twice a day, service covered by Agreement:MHC IM 7*24

Confirm that http://10.245.1.206:30011 s displayed . No username or password is required . Development system TREX TXD (bore), check twice a day, service covered by Agreement:MHC IM - 8-17 Confirm that http://10.245.1.203:30011 is displayed No username or password is required These checks should be performed, one time in the morning (06.00-08.00) and one in the afternoon around 15,00 (swedish time) If problem with connection forward for further investigation -> ICC support and Solution support (see 3.1). Stop and start of TREX should be performed by system administrator EDB IM (see 3.1) 3.8.4 WEB Dispatcher SAP Web dispatcher lies between the Internet and your SAP system. It is the entry point for HTTP(s) requests into your system, which consists of one or more NetWeaver application servers. As a "software web switch", the SAP Web dispatcher can reject or accept connections. 3.8.4.1 Monitoring Routine WEB Dispatcher

Note: Manual routine described below is used until automatic monitoring is established. Production system Web dispatcher MWP (sinir), check twice a day, service covered by Agreement:MHC IM 7*24 Confirm that http://10.245.5.36:60001/sap/wdisp/admin/default.html is displayed Username and password is required see: password database. Development system Web dispatcher MWD (signe), check twice a day, service covered by Agreement:MHC IM - 8-17 Confirm that http://10.245.5.35:60001/sap/wdisp/admin/default.html is displayed Username and password is required see: password database.

These checks should be performed, one time in the morning (06.00-08.00) and one in the afternoon around 15,00 (swedish time) If problem with connection forward for further investigation -> ICC support and Solution support (see3.1). Stop and start of webdispatcher should be performed by system administrator EDB IM (see 3.1). 3.9 Users, Authorizations and Profile Generator

Purpose PI scope doesnt require extensive user maintenance. User-ids and passwords for the applications are handled by the Customer. See Contact List MHC

4.

Printing
The current use of PI doesnt include any printing from PI Online.

5.
5.1

Database Administration ORACLE

ORACLE

Purpose This section explains the basic ORACLE database administration tasks. Where PI is used in conjunction with an ORACLE database, PI System administration requires familiarity with ORACLE database functions. You need to monitor database activity and intervene where necessary, using database tools and PI tools. On the database level, the most important tool is BRTOOLS. Procedure The following table lists the basic ORACLE database administration tasks, including the menu path, the activity group (person responsible), and the frequency with which the task should be performed for the production system, the quality assurance system and the development system. The database administrator is responsible for database administration, see 3.1.

ORACLE BASICS TABLE Task Using the Information System for the ORACLE Database Responsibl e IM/EDB( Frequency *Daily) Menu Path Transactio n Action See 5.1.1 CCMS
Implemented as automatic alerts in CCMS

Tools | Administration | DB02 Monitor | Performance | Database | Tables/Indexes

Tablespace Critical objects Starting IM/EDB BRTOOLS (UNIX) Documenting the IM/EDB ORACLE configuration

When needed

brtools

Initial and when Tools | Administration | ST04 changed Monitor | Performance | Database | Activity | Detail Analysis Menu | Parameter Changes | Active

*Daily = Once a day in the morning Note: When major data load is planned, EDB need information in advance.

5.1.1 Database performance Check current size of tablesspaces. For database administration BRTOOLS is used. We also do a check for Critical Objects, but since we nowadays use Locally Managed tablespaces this would only occur for SYSTEM tablespace.

5.1.2 Starting and Stopping an ORACLE Database Purpose Start or stop the system immediately Procedure Starting and stopping the ORACLE database, menu path, activity group (person responsible), and the frequency with which the task should be performed for the PI production system, test system, and development system. The database administrator is responsible for starting and stopping the database.

Note: For detailed description start and stop ORACLE in the PI system contact System Administrator EDB IM See 3.1.

5.1.3 DBA Planning Calendar Purpose Regular task Procedure The following table lists the tasks related to the DBA Planning Calendar, including the menu path, the activity group (person responsible), and the frequency with which the task should be performed for the PI production system, test system, and development system. .
DBA PLANNING CALENDAR TASKS Task Scheduling database tasks Checking scheduled database tasks Responsibl e IM/EDB Frequency Daily/ Check db 3 times a week/ Update statistics (*Daily ) Menu Path Tools | CCMS | DB administration | DBA scheduling Tools | CCMS | DB administration | DBA scheduling Transactio n DB13 CCMS

IM/EDB

DB13

Implemented as automatic alerts in CCMS

*Daily = Once a day in the morning

5.2

Backup Strategy

For detailed description reference to R/3 information, see document MHC Backup R/3 Production Environment. Onlinebackups using RMAN will be implemnted very soon for the production system.

5.2.1 Backup schema

Backup MHC PI environment Server Group Info

Schedule

Web dispatcher Saga Signe Sinir PI servers Mjlner Mjlner hugin hugin munin munin pmunindb tor tor tyr tyr ptordb Solution Manager Grim Grim Gylfe Gylfe Trex Bore Brimer Global zones Ymer Sleipner CMS Hagbard Hagbard MHC_0100 MHC_SAP_ARCH_1730 Hagbard Zone Hagbard Zone ssssssF Archive logs MHC_2100 MHC_2100 Global zone (mjlner,bore,grim) Global zone (hagbard,brimer,gylfe) iiiFiii iiiiFii MHC_0100 MHC_SAP_OFF_0025 TXD zone TXP zone iiiiiiF iiiiiiF MHC_0015 MHC_SAP_ARCH_1730 MHC_SAP_OFF_0015 MHC_SAP_ARCH_1730 SMD zone SMD zone SMP zone SMP zone sssFsss Archive logs ssssssF Archive logs MHC_0000 MHC_SAP_ARCH_1730 MHC_2100 MHC_0800 MHC_2100 MHC_0800 MHC_SAP_ARCH_1730 MHC_2100 MHC_0800 MHC_2100 MHC_0800 MHC_SAP_ARCH_1730 PID zone PID zone PIQ PIQ PIQ PIQ PIQ PIP PIP PIP PIP PIP Fssssss Siiiiii Fssssss Siiiiii iiFiiii sssssFs iiiiiSi sssssFs iiiiiSi iiiiiiF (archive logs) (obs run in lemon) (archive logs) ssssssF Archive logs (obs run in lemon) MHC_1700 MHC_0100 MHC_SAP_OFF_0015 Global zone MWD zone MWP zone iFiiiii iiiFiii iiiiiFi no savepnpc no savepnpc

*Schedule symbol explanation:

i = incremental backup F= Full backup s= Skip 5.2.2 General information for recovery of system landscape One of the most difficult questions regarding a restore and recovery is how to ensure interface consistency in a complex system landscape after a restore / recovery. Solutions to this question are: Avoid an incomplete recovery (Note 434645). If an incomplete recovery is necessary, see Note 434647. You can find further details under: http://service.sap.com/atg-> Backup & Restore

5.3

Database Growth Management

Purpose Database space requirements grow constantly due to continual data entry. Although at installation there is a quantity of free space, after a certain amount of production operation the database must be extended. To extend the database, create a new data file and allocate it to a tablespace. It is also possible to resize an existing datafile to reduce the number of datafiles. Procedure The following table lists the storage space management tasks, including the menu path, the activity group (person responsible), and the frequency with which the task should be performed for the production system, the quality assurance system, and the development system. The database administrator is responsible for database storage space management.

STORAGE MANAGEMENT Task Documenting the PI database Responsible IM/EDB Frequvency Initial and when changed Menu Path SAPDBA or Tools | Administration | Monitor | Performance | Database | Tables/Indexes brtools brarchive Transaction

Extending the PI database Emptying a full archive log directory

IM/EDB IM/EDB

When needed Once a day at 17:30 (PIP)

*Daily = Once a day in the morning

5.4

Database Performance

5.4.1 Database Reorganization

SMAP TASK Task Identify Tables/Indexes that require reorganization Reorganize Tables Reorganize Indexes Reponsible T&M Frequency RFC Menu Path Transaction

T&M T&M

RFC RFC

5.4.2 Quickly growing tables In PI: SXMSCLUR SXMSPHIST SXMSPFRAWH SWWWIHEAD This tables can cause problem if no archiving deletion take place. Checks if the number of entries is constant, start troubleshoot if the tables start increase.

For further information check the listed OSS notes below.

Topic
Oracle DB parameter settings PI Performance PI Recommended settings Java Sun JDK

Note Number
874378 812158 723909

716604

6.
6.1

SAP Exchange Infrastructure (PI)

Hardware Components
Server Name Hardware type V245 V245 V445 Zon in Sleipner Zon in Sleipner Zon in Sleipner Hardware vendor Sun Sun Sun OS Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10 Solaris 10

HARDWARE COMPONENTS OF THE SERVER LANDSCAPE PI (PRODUCTION SYSTEM) Server Role

PI System Database Tor server PI System Central Tyr Instance Sleipner CMS_Prod Hagbard Trex_Prod Brimer Solman_Prod Gylfe

HARDWARE COMPONENTS OF THE SERVER LANDSCAPE PI (TEST SYSTEM) Server Role PI system DB server PI system CI Server Server Name Munin Hugin Hardware type V240 V240 Hardware vendor Sun Sun OS Solaris 10 Solaris 10

HARDWARE COMPONENTS OF THE SERVER LANDSCAPE PI (OTHER) Server Role WEB Disp_Dev WEB Disp_Prd Server Name Saga Signe Sinir Hardware type V445 Zon in Saga Zon in Saga Hardware vendor Sun OS Solaris 10 Solaris 10 Solaris 10

HARDWARE COMPONENTS OF THE SERVER LANDSCAPE PI (DEVELOPMENT) Server Role PI Dev Trex Dev Solman Dev Server Name Ymer Mjlner Bore Grim Hardware type V445 Zon in Ymer Zon in Ymer Zon in Ymer Hardware vendor Sun OS Solaris 10 Solaris 10 Solaris 10 Solaris 10

6.1.1 System Landscape

6.2

Software Components

The current level on each component can be found by logging on to the system. In the menu use the following path. System / Status: and then viewing the information stored in the SAP system data section. 6.3 Availability Plan

The availability plan is covered in the Service Level Agreement (SLA) 6.4 Monitoring Components

Purpose The following list contains all monitoring tasks that are necessary for SAP Exchange Infrastructure PI monitoring and defines responsibilities.

Procedure Monitor the listed components.

SMAP TASKS Task Integration engine monitoring Responsibl e AM/Acando Frequenc y Daily Menu Path Transaction Action See 6.4.1 CCMS

SXMB_MONI Exchange Infrastructure | Monitoring | Integration Engine | Monitoring SXMB_IFR SXMB_IFR

Component monitoring End-to-end message monitoring Administrat e integration engine System Landscape Directory check Certificates

IM/Acando AM/Acando

*Daily Daily

See 6.4.2.2 See 6.4.2.1

IM/Acando

On request

SXMB_ADM

See 6.4.3

IM/EDB

(*Daily)

SLDCHECK

See 6.4.4

Implemented as automatic alerts in CCMS

IM/EDB

Monthly

SE38

Business Process Engine

AM/Acando

Daily

Run program SSF_ALERT_CERTEXPIRE See 6.4.5 SWF_XI_SWI1 See 6.4.6

*Daily = Once a day in the morning 6.4.1 Integration Engine - Monitoring Purpose Monitor for Processed XML Messages Procedure Transaction SXMB_MONI monitor for processed XML messages Enter a date/time that suits the daily work - Check If there are other messages than the checked flag in the status column. Notice! If end-to-end message monitoring is done, then this wont need to be done See 3.1.

6.4.2 Start Integration Builder Purpose Monitor that the components are all running properly. Runtime workbench: Message monitoring, Communication channel monitoring, Procedure Transaction SXMB_IFR this will bring up a browser. 6.4.2.1 Message monitoring

Acando is responsible for Message monitoring. Select your central AdapterEngine from the drop down menu. Enter the time interval that suits your daily work. You can restrict your selection by the status. Check if there is any other status than successful Repeat this for every decentred adapter you are using. 6.4.2.2 Communication channel monitoring

Acando is responsible for monitoring Communication channels. Check that the adapters have a green light, green lights indicate that the adapter is up and running. Yellow lights indicate that the adapter is initializing and red lights indicate an error. If an error occurs in the adapters a detailed description can either be found in the adapter log file or in the trace file. For the trace file push the trace link of the adapter trace with the lowest size (to get most resent). 6.4.2.3 Performance monitoring

Acando is responsible for Performance monitoring Go to Runtime workbench Performance monitoring leave the display as default and choose time interval (e.g last day). The aggregation of an interval gives the best idea of throughput and peak times. Identify peak times and compare with the last days/weeks. Note, that the rate msg/hour can be misleading.

6.4.3

Integration Engine - Administration Acando is responsible for Engine administration

Transaction SXMB_ADM Especially deletion procedures should be checked to ensure the performance of the engine. 6.4.4 Test SLD Connection System Landscape Directory (SLD) test transaction SLDCHECK. A test has been implemented in CCMS (transaction GRMG) 6.4.5 Certificates Run program SSF_ALERT_CERTEXPIRE in transaction SE38. Set interval for the next 2 months. The program check certificate expiration day. 6.4.6 Business Processes Engine (BPE) Monitor BPE transaction SWF_XI_SWI1

6.4.7 Queue Monitoring

SMAP TASK Task qRFC Outbound Queue Monitor Responsibl e IM/EDB Frequenc y Daily * Transactio n SMQ1 Menu Path Middleware | Monitoring | Queues | Display Outbound RFC Queues Action See 6.4.7.1 CCMS
Implemented check of number of records in queue via unix script Implemented as automatic alerts in CCMS + unix script

qRFC Inbound Queue Monitor

IM/EDB

(Daily) *

SMQ2

Middleware | Monitoring | Queues | Display Inbound RFC Queues

See 6.4.7.1

Blocked queues QOUT IM/EDB Scheduler QIN Scheduler IM/EDB

Daily Daily

SMQS SMQR

6.4.8 6.4.8

* Script implemented that checks number of records in queue twice an hour

6.4.7.1

Procedure for checking inbound and outbound queues

In the daily monitoring try to get a feeling how many queues / entries the system usually uses.

Check the number of queues and the number of entries. Hit refresh to check if the number of entries increases / decrease / remain the same. An increase of queues / entries points to a bottleneck and should be monitored. Select Alarm bell (push button) to see only queues with error status. If there are queues in error status please create an EARS ticket. If problem is AM related assign to ORE_SD_X_IT. They will then forward info to Acando Solution Support. Step 1: Check outbound queue in transaction SMQ1.

Step 2: Selection criteria as in step 1 and press F8.

If result is "Nothing selected" then everything is okay and you can go to step 6, otherwise go to step 3.

Step 3: Double click the queue:

Step 5: Check for errors

Report error. Step 6: Repeat step 1 to 5 for transaction SMQ2 (inbound queues).

A new script has been implemented that checks if number of entrys in Inbound/Outbound queue is larger that 1000 and then sends an e-mail to our "PIP CCMS Monitoring " folder. Check is done twice an hour.

6.4.8 Outbound/Inbound scheduler queue Transaction SMQS and SMQR Monitors on destination Level Usually not constantly working shows as INACTIVE only if entries in the outbound queue Check Last Update will show when something was processed the last time If a number of LUWs are being processed, status will be Waiting Can stop outbound processing by Deregistering the queue should be for maintenance only.

6.4.9

Communication Monitoring

Purpose Because of the close connection between PI middleware and the OLTP system, you can expect additional workload in the R/3 system. Procedure The monitoring of Transactional RFC and Gateway is most important in distributed system environments.
SMAP TASKS Task Monitoring the tRFC Responsibl e IM/EDB Frequency (*Daily) Menu Path Transactio n Action CCMS

Monitoring the Gateway / Connection List

IM/EDB

*Daily

Basis Tools | SM58 Administration | Monitor | Transactional RFC Basis Tools | SMGW Administration | Monitor | System Monitoring | Gateway Monitor

See 6.4.9.1 Implemented

as automatic alerts in CCMS

See 6.4.9.2

*Daily = Once a day in the morning

6.4.9.1

Transactional RFC Idoc adapter

Purpose Check outgoing trfc calls. (Problem with incoming idocs it's necessary to check in sending system). Procedure Transaction SM58 is not showing successful transactions. Check if there are transactions with errors, check the error message Responsible person should do further investigation see 3.1.

6.4.9.2

Gateway Monitoring

Check for red entries and entries with last request that have an old time stamp.

6.4.10 Relevant SAPNet Notes

RELEVANT SAPNET NOTES Topic Queue status in SMQ1, SMQ2 and table ARFCRSTATE Note Number 378903

6.5

Third party and PI environment

With its diversity of adapters, PI offers third party systems the integration method which suits the system best. For integration with SAP the following methods are recommended 6.5.1 JDBC integration through the database. This method will require building some interface tables that will either be populated by the third-party system or by PI. Retrieving and sending data will be done either by SQL or through Stored Procedures. This integration is recommended for systems that are within the network and are database centered. A requirement is that the database has JDBC support (JDBC drivers exists) i.e Oracle, Sybase, DB2, SQL server. 6.5.2 XML XML Integration through XML requires a third party system that has XML support (XML parser). XML offers better data integrity than flat files and as PI is an XML based application, the use of XML schemas will reduce development time on the PI server. The transport mechanism will either be HTTP(S) or FTP. PI also has SOAP support for systems that are compatible with Simple Object Access Protocol. 6.5.3 Java proxy This integration method generates an PI client that runs on the third party system. This method is recommended for java based applications that are application centred (ie component oriented J2EE). It is important to have java developers that know the third party system. 6.5.4 Flat file

This integration method should only be used when none of the above suits the third party system.

6.5.5 Runtime Workbench Purpose Procedure The Runtime Workbench is used to test and monitor the individual components of the SAP Exchange Infrastructure. You can display the business systems that are defined in the system landscape. Its also possible to make security settings for communicating with the Integration Server. 6.5.6 Integration Builder Integration Repository (IR) The Integration Repository provides collaboration knowledge available at design time, for example, business scenarios, business processes, mappings, interfaces, and components. It is built in Java and follows Java 2 Enterprise Edition standards. The information in the Integration Repository is used by the Integration Directory, which adds configuration specific information that is needed for execution. Integration Directory (ID) The Integration Directory contains detailed collaboration knowledge about the current system landscape around the SAP Integration Server. It is a description of routing relations, mapping relations, endpoint definitions, logon data and the specific system landscape. The Integration Directory details the information from the Integration Repository that is specific to the configuration. 6.5.7 System Landscape Directory Purpose Procedure The System Landscape Directory is composed of the Component Repository and the Landscape Directory. The Component Repository includes a description of all SAP Components whereas the Landscape Directory includes a complete description of the actually installed SAP system landscape. 6.5.8 Integration Clients Purpose

Procedure The Integration Repository and Directory require specific Java client software, which is stored on the Integration Server and will be automatically installed on the client side using Java Web Start. This client software can be used during design time to develop new interfaces and mappings and to configure services, routings and mappings. 6.5.9 Proxy Framework Purpose Procedure The Proxy Framework consists of the Proxy Generator and the Proxy Runtime. The Proxy Framework for ABAP (generator and runtime) is part of the SAP Exchange Infrastructure Add-On 2.0. Proxy Generation for Java The Integration Builder provides the functions used for generating Java proxies. Using the Java proxy generation function, you can create Java classes or Java proxy objects from the interface description in the Interface Repository. Java Proxy Runtime The Proxy Runtime for Java is mandatory for all Java programs to exchange messages with the SAP Integration Server. In doing so the proxy runtime converts the used java classes into XML messages. These XML messages are sent to the Integration Server using http protocol. 6.5.10 Internal communication Purpose Procedure The central part of the SAP Exchange Infrastructure is the Integration Server that receives message objects from the sending application and sends these message objects to the requested application. This message object transfer is run through different adapters to enable different kinds of applications to connect to the Integration Server using different protocols and data formats. All necessary data for logical and technical routing as well as mapping is provided to the Integration Server by the Integration Directory. All these data is persistently cached within the database of the Integration Server. That makes the Integration Server resilient against communication failure with the Integration Directory and ensures the "standalone" capability of this runtime critical component.

6.5.11 External communication Purpose Procedure The Integration Server provides various Integration Adapters supporting different kinds of protocols and data formats. The adapters convert the application specific message and data format into the Integration Server's internal XML based message format. The Integration Server then applies predefined routing and mapping rules on the incoming message objects to obtain the outgoing message. After determining the target application system the outgoing message object is then again passed through an adapter required to convert the message to the target systems message and data format. This enables different kinds of systems to connect to the Integration Server.