8/13/2019 GTS10.0 Operations Guide
1/56
Operations GuideSAP BusinessObjects Global Trade Services 10.0 OperationsGuide
Target Audience Technical Consultants System Administrators Solution Consultants Business Process Owner Support Specialist
PUBLICDocument version: 1.0 2010-12-13
8/13/2019 GTS10.0 Operations Guide
2/56
SAP AGDietmar-Hopp-Allee 16
69190 WalldorfGermany
T +49/18 05/34 34 34
F +49/18 05/34 34 20 www.sap.com
Copyright 2010 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permissionof SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10,z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA,AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium,Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implementedby Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germanyand in several other countries all over the world. All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational purposes only. National product specificationsmay vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies(SAP Group) for informational purposes only, without representation or warranty of any kind, and SAP Group shall notbe liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, if any. Nothing hereinshould be construed as constituting an additional warranty.
DisclaimerSome components of this product are based on Java. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressly prohibited, as is any decompilation of these components.Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified oraltered in any way.
2 /56 PUBLIC 2010-12-13
8/13/2019 GTS10.0 Operations Guide
3/56
Typographic Conventions
Example Description Angle brackets indicate that you replace these words or characters with appropriate
entries to make entries in the system, for example, Enter your.ExampleExample
Arrows separating the parts of a navigation path, for example, menu options
Example Emphasized words or expressionsExample Words or characters that you enter in the system exactly as they appear in the
documentationhttp://www.sap.com Textual cross-references to an internet address/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web123456 Hyperlink to an SAP Note, for example, SAP Note123456Example Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options. Cross-references to other documentation or published works
Example Output on the screen following a user action, for example, messages Source code or syntax quoted directly from a program File and directory names and their paths, names of variables and parameters, andnames of installation, upgrade, and database tools
EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example,SELECT and INCLUDE
EXAMPLE Keys on the keyboard
2010-12-13 PUBLIC 3 /56
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=123456&_NLANG=en&_NVERS=0http://www.sap.com/8/13/2019 GTS10.0 Operations Guide
4/56
Document History
CAUTION
Before you start the implementation, make sure you have the latest version of this document.You can find the latest version at the following location: http://service.sap.com/swdc SAPInstallations and Upgrades Installations and Upgrades - Entry by Application Group SAP Solutions for GovernancRisk and Compliance SAP Global Trade Services Installation and Upgrade.
The following table provides an overview of the most important document changes. Version Date Description
1.0 2010-12-13 Initial Version
4 /56 PUBLIC 2010-12-13
http://service.sap.com/swdc8/13/2019 GTS10.0 Operations Guide
5/56
Table of Contents
Chapter 1 G etting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.1 Global Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.2 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Chapter 2 Technical System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
2.1 Scenario/Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.2 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Chapter 3 Monitoring of SAP BusinessObjects Global Trade Services . . . . . . . . . . . 133.1 Alert Monitoring with CCMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143.1.1 Central System Monitoring Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . .153.1.2 CCMS Monitoring Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.1.3 Component-Specific Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.2 Detailed Monitoring and Tools for Problem and Performance
Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.2.1 Trace and Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.2.2 Interface Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.2.3 Workload Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243.2.4 Data Growth and Data Archiving Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . .243.2.5 Specific Problem Analysis Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253.3 Data Consistency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Chapter 4 Logging On and Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Chapter 5 Management of SAP Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315.1 Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315.2 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315.3 Administration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325.4 Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .335.5 Application Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .345.6 Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
5.6.1 Scheduled Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
2010-12-13 PUBLIC 5 /56
8/13/2019 GTS10.0 Operations Guide
6/56
5.6.2 Required Manual Periodic Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .355.7 Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .365.8 User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
5.9 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Chapter 6 High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Chapter 7 Software Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .417.1 Transport and Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .417.2 Development Requests and Development Release Management . . . . . . . . . . .427.3 Quality Management and Test Management . . . . . . . . . . . . . . . . . . . . . . . . . .427.4 Support Packages and Patch Implementation . . . . . . . . . . . . . . . . . . . . . . . . .427.5 Release and Upgrade Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Chapter 8 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Chapter 9 Support Desk Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479.1 Remote Support Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479.2 Problem Message Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .479.3 Services for SAP BusinessObjects Trade Services . . . . . . . . . . . . . . . . . . . . . . . .47
9.3.1 Solution Management Assessment (SMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . .479.3.2 GoingLive Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .489.3.3 Early Watch Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .489.3.4 Technical Integration Check (TIC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .489.3.5 Volume Test Optimization (VTO) package . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49A.1 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49A.1.1 Related Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
A.1.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
Chapter B Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51B.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
6 /56 PUBLIC 2010-12-13
8/13/2019 GTS10.0 Operations Guide
7/56
1 Getting Started
CAUTION
This guide does not replace the daily operations handbook that we recommend customers createfor their specific production operations.
Designing, implementing, and running your SAP applications at peak performance 24 hours a day hasnever been more vital for your business success than now.
This guide provides a starting point for managing your SAP applications and maintaining and runningthem optimally. It contains specific information for various tasks and lists the tools that you can useto implement them. This guide also provides references to the documentation required for these tasks,so you need other guides such as the Master Guide, Technical Infrastructure Guide, TechnicalOperations Manual for SAP NetWeaver and SAP Library.
1.1 Global DefinitionsSAP Application:
An SAP application is an SAP software solution that serves a specific business area like ERP, CRM, PLM,SRM, SCM, or Global Trade Services. The delivery of an application contains SAP components, whichare essential for implementing all application-related business scenarios, processes, and functions.
Business Scenario:
From a microeconomic perspective, a business scenario is a cycle, which consists of several differentinterconnected logical processes in time. Typically, a business scenario includes several companydepartments and involves other business partners. From a technical point of view, a business scenarioneeds at least one SAP application for each cycle and possibly other third-party systems. A business
scenario is a unit, which can be implemented separately and reflects the customers prospective courseof business.
Component:
A component is the smallest individual unit considered within the Solution Development Lifecycle;components are separately produced, delivered, installed, and maintained.
1 Getting Started
1.1 Global Definitions
2010-12-13 PUBLIC 7 /56
8/13/2019 GTS10.0 Operations Guide
8/56
1.2 Important SAP NotesCAUTION
Check regularly for updates of the Application Operations Guide.
Important SAP Notes
SAP Note Number Title
30289 SAProuter documentation19227 Get the latest saposcol209834 CCMS agent technology
1 Getting Started
1.2 Important SAP Notes
8 /56 PUBLIC 2010-12-13
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=209834%20&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=19227%20&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=30289&_NLANG=en&_NVERS=08/13/2019 GTS10.0 Operations Guide
9/56
2 Technical System Landscape
2.1 Scenario/Component Matrix
This section provides an overview of which product area of SAP BusinessObjects Global Trade Servicesuses which software unit. All product areas of the software component SLL-LEG are optional dependingon the business needs.For the latest component version and patch level requirements, see http://service.sap.com/scl .
SoftwareComponent
Business ScenariosX = mandatory; (X) = optional; = not part of the business scenario
ComplianceManagement
CustomsManagement
PreferenceProcessing
Letter ofCredit
RestitutionHandling
ElectronicComplianceReporting
SLL-LEG 900 X X X X X XSLL-PI 900_* X X X X X (X)SAP_AP 700 X X X X X XSAPNetWeaverABAP Stack
X X X X X X
SAPNetWeaver Java Stack forAdobeDocumentServer (ADS)
(X) X X (X) X -
SAPInteractiveFormssoftware byAdobe
(X) X X (X) X -
AP PricingEngine of SAPNetWeaverApplicationServer forABAP
- (X) - - - -
SAPNetWeaverSearch andClassification(TREX)
(X) - - - - -
2 Technical System Landscape
2.1 Scenario/Component Matrix
2010-12-13 PUBLIC 9 /56
http://service.sap.com/scl8/13/2019 GTS10.0 Operations Guide
10/56
SoftwareComponent
Business ScenariosX = mandatory; (X) = optional; = not part of the business scenario
ComplianceManagement
CustomsManagement
PreferenceProcessing
Letter ofCredit
RestitutionHandling
ElectronicComplianceReporting
SAPNetWeaverBusinessIntelligence *
(X) (X) (X) (X) (X) -
SAPNetWeaver BIContentBI_CONT 7.03
(X) (X) (X) (X) (X) -
ContentLifecycleManagementPOA_SBC_100 _702
(x) - - - - -
ConverterSoftware(Third PartySoftware)
- X - - - -
BusinesspackageGRC_POR1000 as
prerequisitefor using theapplicationuser roles inSAPNetWeaverPortal
(x) (x) (x) (x) (x) (x)
Adobe AcrobatReader
(X) (X) (X) (X) (X) -
* PI_BASIS 2005_1_700 of SAP NetWeaver is a prerequisite for using SAP NetWeaver Business IntelligenceThe ABAP component of Content Lifecycle Management (CLM) is POASBC POA Shared BusinessComponents.For more information about the software units of CLM, see the Master Guide for the application.
2.2 Related Documentation
For more information about the technical system landscape, see the following table:
2 Technical System Landscape
2.2 Related Documentation
10 /56 PUBLIC 2010-12-13
8/13/2019 GTS10.0 Operations Guide
11/56
Topic Guide/Tool Location
Application-specific areassuch as the following: Compliance
Management Customs Management Preference Processing Letter of Credit Restitution Electronic Compliance
Reportingl
Master Guide http://service.sap.com/swdc SAP Installations andUpgrades Installations and Upgrades - Entry by Application Group
SAP Solutions for Governance, Risk and Compliance SAP GlobalTrade Services Installation and Upgrade
Technology Componentssuch as SAP NetWeaverApplication Server
Master Guide forSAP NetWeaver
http://service.sap.com/instguides
Sizing Quick Sizer Tool http://service.sap.com/sizing
Technical Configuration TechnicalInfrastructureGuide
http://service.sap.com/installnw70 1- PlanningTechnical Infrastructure GuideScalability
High AvailabilitySecurity Security Map http://service.sap.com/security
SAPBusinessObjectsGlobal TradeServices SecurityGuide
http://service.sap.com/swdc SAP Installations andUpgrades Installations and Upgrades - Entry by Application Group
SAP Solutions for Governance, Risk and Compliance SAP GlobalTrade Services Installation and Upgrade
SAP NetWeaverSecurity Guide
http://service.sap.com/security Security in Detailorhttp://help.sap.com/nw70 System AdministrationSecurity Guide
Operations of NetWeaverusage types
TechnicalOperations Manual
http://help.sap.com/nw70 System AdministrationTechnical Operations Manual
Monitoring with CCMS SAP NetWeaverLibrary
http://help.sap.com/nw70 Functional View SAPNetWeaver by Key Capability Solution Life Cycle Management
Solution Monitoring Monitoring in the CCMS
2 Technical System Landscape
2.2 Related Documentation
2010-12-13 PUBLIC 11 /56
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://service.sap.com/securityhttp://service.sap.com/swdchttp://service.sap.com/securityhttp://service.sap.com/installnw70http://service.sap.com/sizinghttp://service.sap.com/instguideshttp://service.sap.com/swdc8/13/2019 GTS10.0 Operations Guide
12/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
13/56
3 Monitoring of SAP BusinessObjectsGlobal Trade Services
Within the management of SAP Technology, monitoring is an essential task. A section has thereforebeen devoted solely to this subject.The aim of this section is to provide information and documentation to monitor SAP BusinessObjectsGlobal Trade Service 10.0, for example by utilizing the Computing Center Management System (CCMS)and create a user-defined monitor set reflecting a customer-specific system landscape for SAPBusinessObjects Global Trade Services. For more information about the underlying technology, seethe SAP NetWeaver Administrators Guide - Technical Operations Manual, particularly the section onMonitoring, in SAP Library at http://help.sap.com/nw70 System Administration Technical OperationsManual .As SAP BusinessObjects Global Trade Service 10.0 is powered by SAP NetWeaver 7.0 includingEnhancement Package 22, we recommend that you set up the monitoring infrastructure as describedin the Monitoring Setup Guide for SAP NetWeaver at service.sap.com/operationsnw70
Monitoring.
The monitoring setup described in the Monitoring Setup Guide (MSG) for SAP NetWeaver is thefoundation for the following sections and contains all the information relevant to monitor the SAPNetWeaver components used in SAP BusinessObjects Global Trade Service 10.0. Proficient knowledgein system monitoring and basic knowledge in SAP NetWeaver is required to set up and manage user-defined monitors recommended within this guide.
NOTE
To build the necessary skills in system monitoring, we recommend the SAP courses and e-learningon that topic. For more information, see the information available on SAP Service Marketplace
at service.sap.com/monitoring System Monitoring and Alert ManagementEducation &Workshops
Monitoring of SAP NetWeaver is an essential task within the management of SAP solutions, includingContent Lifecycle Management (CLM). The aim of this section is to provide information anddocumentation to monitor CLM, for example by utilizing the Computing Center Management System(CCMS) and NetWeaver ABAP monitoring tools.
3 Monitoring of SAP BusinessObjects Global Trade Services
2010-12-13 PUBLIC 13 /56
http://help.sap.com/nw70http://service.sap.com/monitoringhttp://service.sap.com/operationsnw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
14/56
RECOMMENDATION
Since Content Lifecycle Management is powered by SAP NetWeaver 7.02 and higher, werecommend that you set up the monitoring infrastructure as described in the Monitoring Setup
Guide for SAP NetWeaver on SAP Service Marketplace athttp://service.sap.com/instguides.
By default, CCMS monitoring capabilities are restricted to the local system and as CLM involvesinteractions with more than one system in a typical landscape, it could be beneficial to monitor othersystems through CCMS from central CLM system.In this case, CLM, as the central monitoring system, can be configured to link CCMS monitoring fromapplication systems. Since currently CLM only communicates with ABAP-based systems, RFCconnection type can be used to enable monitoring across multiple systems. For more information aboutconfiguring the central monitoring system, see SAP Help Portal at http://help.sap.com SAP
NetWeaver .
3.1 Alert Monitoring with CCMS
Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP systemenvironment. SAP provides you with the infrastructure and recommendations needed to set up youralert monitoring in CCMS to recognize critical situations for SAP BusinessObjects Global Trade Servicesas quickly as possible. For more information, see the Monitoring Setup Guide for SAP NetWeaver at
http://service.sap.com/operationsnw70Monitoring.To configure alert monitoring with CCMS for SAP BusinessObjects Global Trade Service 10.0, you must
set up a Central Monitoring System (CEN) and connect the components for SAP BusinessObjects GlobalTrade Serviceto this CEN system. For a list of these components and the business scenarios for whichthey are relevant, see the section forScenario/Component Matrix in this guide.Since SAP BusinessObjects Global Trade Service 10.0 utilizes the complete stack of SAP NetWeaver 7.0including Enhancement Package 2, you have to apply the Monitoring Setup Guide for SAP NetWeaverto the component of SAP BusinessObjects Global Trade Service, first. In addition to this, you can definespecial monitors for SAP BusinessObjects Global Trade Service in the CEN Systems CCMS. You can
access the Monitoring templates for SAP BusinessObjects Global Trade Services, called SAPBusinessObjects Global Trade Services using transaction RZ20 (see sectionAlert Monitoring for SAPBusinessObjects Global Trade Services in this guide for full details).In addition to this, you can define special monitors in the CEN systems CCMS for your own needs.There are also some additional monitoring objects designed to monitor cross-componentcommunication and other scenario-specific critical situations.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
14 /56 PUBLIC 2010-12-13
http://service.sap.com/operationsnw70http://service.sap.com/operationsnw708/13/2019 GTS10.0 Operations Guide
15/56
3.1.1 Central System Monitoring Architecture
We recommend that you integrate monitoring SAP BusinessObjects Global Trade Service into yourexisting Central Monitoring System (CEN) to monitor different SAP systems in a computing centerenvironment. The administration effort is significantly lower if a centralized system monitoring is usedrather than monitoring each system separately. The CEN should have the same SP level or higher asthe highest available SAP NetWeaver Application Server (ABAP) SP level of SAP NetWeaver 7.0 includingEnhancement Package 2 within the system landscape.For detailed instructions on how to set up a CEN system, seeConfiguring the Monitoring Architecture in SAPNetWeaver documentation in SAP Library at https://help.sap.com/nw70 Functional View SAP NetWeaverby Key Capability Solution Life Cycle Management Solution Monitoring Monitoring in the CCMS.The CEN system can be connected to the SAP Solution Manager if the monitoring scenario is configured
and used. For more information about SAP Solution Manager, see the information available on SAPService Marketplace at http://service.sap.com/solutionmanager .Systems and applications can be monitored with SAP Agent Technology. There are three differentagents available for System Monitoring: SAPCCM4X for SAP NetWeaver Application Server (ABAP) SAPCCMSR for SAP NetWeaver Application Server (Java) with Adobe Document Server (ADS),
Search & Classification (TREX), Internet Pricing and Configurator (IPC) for using Transaction TaxEngine (TTE) in customs duty calculation
CCMSPING for availability monitoring from CEN A fourth agent, SAPOSCOL, monitors the operating system data for each host from the CEN system.For more information about CCMS agents, see the documentation available on SAP Service Marketplaceat https:://service.sap.com/monitoring Monitoring in Detail CCMS Agents: Features, Installation andUsage .
System Groups
Before creating new monitors for SAP BusinessObjects Global Trade Service, we recommend that youfirst maintain the system groups in transaction RZ21 .A system group consists of a series of systems that you wish to display together in the CCMS monitoringarchitecture. You can specify a system group when you are defining a monitor the monitor thencontains all systems that belong to the system group.Definitions of system groups are stored in the CCMS System Component Repository (SCR). The SCRis a component that maps to one or more SAP systems. To set up the system groups, go to transactionRZ21 and choose Technical Infrastructure Configure Central System Maintain System Groups. Here, you canalso expand the tree to display the groups that have alreadybeen defined.For detailed instructions on how to maintain system groups, see Maintaining System Groups in SAPNetWeaver documentation in SAP Library at http://help.sap.com/nw70 Functional View SAP
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
2010-12-13 PUBLIC 15 /56
http://service.sap.com/solutionmanagerhttps://help.sap.com/nw70http://help.sap.com/nw70http://service.sap.com/solutionmanagerhttps://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
16/56
NetWeaver by Key Capability Solution Monitoring Monitoring in the CCMS The Alert Monitor Customizing theAlert Monitor System Groups in the Alert Monitor .
EXAMPLEThe following table shows how you can create your system group:
System Group System
GTS_Systems SAP SLL-LEG 900 J2EE_Systems LACWPS SAP NetWeaver Application Server 702XI_Systems SAP NetWeaver Process Integration (SAP NetWeaver PI, formerly Exchange Infrastructure,
XI)
Properties Variant
You should also create a properties variant (for example, SLLLEG900_Default) to save yourCustomizing and configuration during the setup of the CEN.A monitoring properties variant contains the following data: Settings for properties Method assignments for monitoring tree elements (MTE) MTE classes and attribute groups.Every change made to these settings is assigned to a properties variant.
3.1.2 CCMS Monitoring Installation and SetupFor using the application-specific alert monitors for SAP BusinessObjects Global Trade Services 10.0,see SAP Note 1296394. With this SAP Note, you can install the application-specific monitors, calledSAPGRC Global Trade Services, by using the XML file that is attached to this SAP Note.To enable the auto-alert mechanism of CCMS, see SAP Note617547.
RECOMMENDATION
We recommend the usage of SAP NetWeaver for Central Monitoring.
3.1.3 Component-Specific Monitoring
One approach for monitoring an SAP BusinessObjects Global Trade Service 10.0 landscape is to monitoreach component separately in the CEN system. The other approach is to monitor across componentsbased on a business scenario. This section gives you an overview of how each component for runningSAP BusinessObjects Global Trade Services could be monitored using CCMS. Which components needto be monitored depends on the scenarios and application areas you implemented for SAPBusinessObjects Global Trade Services. SAP BusinessObjects Global Trade Services is based oncomponent SLL-LEG 900 for which you can set up monitors using CCMS.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
16 /56 PUBLIC 2010-12-13
http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=617547&_NLANG=en&_NVERS=0http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1296394&_NLANG=en&_NVERS=08/13/2019 GTS10.0 Operations Guide
17/56
NOTE
This monitoring set for SAP BusinessObjects Global Trade Services includes component-relatedmonitors such as for the application component SLL-LEG 900 of SAP BusinessObjects Global Trade
Services as well as for the logistics processes in the feeder system that are channeled through theplug-in for further processing in SAP BusinessObjects Global Trade Services. These monitors arenot delivered by SAP but can be created in the CEN system. All Monitoring Tree Elements (MTE)used for these monitors are based on the default monitoring templates delivered by SAP.For information about editing or creating monitors and monitor sets, see the Monitoring SetupGuide for SAP NetWeaver on SAP Service Marketplace atservice.sap.com/operationsnw70
Monitoring.
Alert Monitoring for SAP NetWeaver
SAP NetWeaver 7.0 including Enhancement Package 2 is the integration and application platform forSAP BusinessObjects Global Trade Service 10.0, therefore the following SAP NetWeaver componentsmust be integrated into the monitoring infrastructure: SAP NetWeaver Application Server (ABAP) [for SAP BusinessObjects Global Trade Service 10.0 and
its component SLL-LEG 900] SAP NetWeaver Application Server (Java) [for the use of Adobe Document Server (ADS) for printing
in SAP BusinessObjects Global Trade Service 10.0 or for running SAP NetWeaver Portal to use theapplication user roles]
SAP NetWeaver Search and Classification (TREX) SAP NetWeaver Usage Type Process Integration (PI) SAP NetWeaver Business Intelligence (BI)For more information and detailed procedures, see the Monitoring Setup Guide and the TechnicalOperations Manual for SAP NetWeaver.
Alert Monitoring for SAP BusinessObjects Global Trade Services
The component SLL-LEG 900 for SAP BusinessObjects Global Trade Service 10.0 is based on SAPNetWeaver Application Server for ABAP. You can find information about monitoring the SAP
NetWeaver AS for ABAP in the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplaceat http://service.sap.com/operationsnw70 Monitoring and the Technical Operations Manualin SAP Library at http://help.sap.com/nw70 System Administration.What to MonitorThe primary failure points of SAP BusinessObjects Global Trade Services 10.0 are within the technicalinfrastructure. Application-specific alert monitoring is available for component SLL-LEG 900 as well asthe dependent plug-in component of SAP BusinessObjects Global Trade Services in the feeder systemSAP ERP, SLL_PI 900_.You can set up additional monitors for specific processes in SAP BusinessObjects Global Trade Service
according to your needs, for example, IDoc monitoring in the communication processes.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
2010-12-13 PUBLIC 17 /56
http://help.sap.com/nw70http://service.sap.com/operationsnw70http://service.sap.com/operationsnw70http://help.sap.com/nw70http://service.sap.com/operationsnw70http://service.sap.com/operationsnw708/13/2019 GTS10.0 Operations Guide
18/56
Prerequisites Your SAP BusinessObjects Global Trade Service 10.0 is connected to the CEN and registered as a
remote system. The SAPCCM4X agent is registered and running for the instance of SAP BusinessObjects Global Trade
Service.Procedure1. Go to transaction RZ20 and select the monitor SAP BusinessObjects Global Trade Services.2. On the top level, you can choose between the following monitoring areas:
AvailabilityThe availability monitor allows you to monitor RFC connections between connected systemsin a system landscape. This monitor uses the standard SAP NetWeaver monitor for checkingthe RFC connection. You must have set up the RFC destination to the connected systembefore you can use the monitor. You can use this monitor in both components, SLL-LEG 900for SAP BusinessObjects Global Trade Services as well as the corresponding plug-in in thefeeder system SLL-PI_900_.
LoggingThe logging monitor collection that you can use for SLL-LEG 900 comprises virtual monitorsthe following log objects that you can use. Note that the logging subtree in this monitor onlycontains information if the system has logged error messages. With successful operations inthe system, only the logging summary node is shown in the monitor.
CCMS Monitor Log Object Sub-Object Description Minimum Severity*
Communication with FeederSystems
/SAPSLL/ BOM /SAPSLL/ BOM_R3 Bill of Material Transfer from Feeder System (SAPERP)
Error
/SAPSLL/ BP /SAPSLL/ BP_DISTR Business Partner DistributionError/SAPSLL/ ECC /SAPSLL/ MAT_R3 Product from Feeder System
(SAP ERP)Error
Communication withAuthorities
/SAPSLL/ ECC /SAPSLL/ ECC_IN ECC: Inbound ProcessingError/SAPSLL/ ECC_OUT ECC: Outbound ProcessingError
Operational Error /SAPSLL/ TREX /SAPSLL/ TREX_LOAD SAPGTS: GeneratingComparison Index for SAPTREX
Error
/SAPSLL/ TSPL_STERMS SLL: Legal Control: SPL: SPLIndex
-
* Minimum severity level at which log entries influence the monitor.To enable the auto-alert mechanism of CCMS, see SAP Note 617547.The monitoring sets from CCMS monitoring in RZ20 can help analyze most critical bottlenecks;however, the following table points to some problem-oriented scenarios and a recommended trackingmechanism for CLM:
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
18 /56 PUBLIC 2010-12-13
8/13/2019 GTS10.0 Operations Guide
19/56
CLM Scenario/Activity Problem Possible Causes Recommended Monitoring
Extraction of contentfrom application system
Exception Occurred RFC connection failure,system failure, noauthorization for RFC calls
Check system trace file(ST01)/ SM59 / SMT1 fortrusted connections. CLMlog in SLG1
Extraction in progress fora long time
Large amount of content Check background task inSM37 and CCMS CLMmonitor
Validation errors Content in incorrectformat
SLG1 application log forCLM
Importing content from aCLM package (zip)
Exception occurred Malformed content ortempered content format
SLG1 application log forCLM
Time out Package size is too big Check CCMS memory orbuffer sizes to free
resources, increase timeout limits for profileparameters, but usuallycannot be resolved
Exporting CLM content toa package (zip)
Exception occurred Content was changed afterincluding in package
SLG1 or check status ofcontent group
- Time out Content size is too big Remove hugeattachments, split packageinto two smaller packages
Deploy Content Exception occurred Incompatible system forapplication deployment ofcontent, RFC connectionfailure, system failure, noauthorization for RFCcalls, no trusted system
SLG1 application log forCLM, system trace file(ST01), SMT1 for trustedconnections
Deployment takes toolong
Large amount of content SM37 or CCMS for CLMdeployment and pollingresults background job
Non-recognized status indeployment log
Failure on applicationdeployment
Check target applicationsystem, ST22, for anyexceptions, authorizationfailures
No deployment possible Existing deployment ontarget system already ongoing
Check DB locks in SM12(table /POA/ S_CLM_DEPLKEY)
Alert Monitoring for Content Lifecycle Management in SAP BusinessObjects Global TradeServices
Existing CCMS monitoring sets can be used to monitor various resources, objects, and performance.For example, SAP CCMS monitor template, which can be used to monitor system, database, andbackground processing for the application server where CLM is running. CLM provides monitoring
set Content Lifecycle Management Monitor Set and monitors for CLM-relevant background jobs and CLM-
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
2010-12-13 PUBLIC 19 /56
8/13/2019 GTS10.0 Operations Guide
20/56
relevant system resources as part of this set. This can be accessed in NetWeaver ABAP system usingCCMS transaction RZ20.The following existing monitors within RZ20 can be used by CLM to monitor critical conditions:
Background ProcessingFor extraction and deployment scenarios in CLM, background jobs are created for a content group.CCMS view for background processing underContent Lifecycle Management Monitor Set can be used to retrievestatistics such as a list of long-running background jobs, number of free or occupied work processes,and any CLM job that was stopped abruptly.
NOTE
Transaction SM37 can be used to monitor background jobs initiated by CLM.
Database M onitoringA connection RDBMS with the system where CLM is installed and being used can be monitored usingdatabase monitor within CCMS.Operating System MonitoringOperating system monitoring capabilities within CCMS administration workplace are used to analyzeCPU, memory, paging, disks, file system, and their corresponding health statuses.Dialog OverviewUsing dialog monitoring inRZ20 , the response time for dialog, network time, and number of currently
logged-in users can be observed.For CLM, it is important to observe Web Dynpro ABAP-related attributes such as date transferred,session timeouts, and number of roundtrips against CLM Web Dynpro application - /POA/WD_CLM.This view is also part of the delivered CLM-specificContent Lifecycle Management Monitor Set .
Alert Monitoring for Scenarios
An addition to the component alert monitoring for all scenarios of SAP BusinessObjects Global TradeService 10.0 monitoring of remote function calls (RFCs) is required.The scenarios of SAP BusinessObjects Global Trade Service 10.0 use standard monitoring functions
provided by SAP NetWeaver to perform alert monitoring on RFCs. For more information, seeMonitoring qRFC and tRFC Calls in SAP NetWeaver documentation in SAP Library athttp://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Life Cycle Management
Solution Monitoring Monitoring in the CCMS The Alert Monitor Special Monitoring Functions of the AlertMonitor .The communication process for importing and exporting goods with Customs Management of SAPBusinessObjects Global Trade Service 10.0 also requires IDoc alert monitoring for which it uses standardalert monitoring of SAP NetWeaver. For more information, seeCentral Monitoring Using ALE CCMSMonitor in SAP NetWeaver documentation in SAP Library at http://help.sap.com/nw70 FunctionalView SAP NetWeaver by Key Capability Application Platform by Key Capability Platform-Wide Services
3 Monitoring of SAP BusinessObjects Global Trade Services
3.1 Alert Monitoring with CCMS
20 /56 PUBLIC 2010-12-13
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
21/56
Connectivity Components of SAP Communication Technology Classical SAP Technologies (ABAP) IDInterface/ALE Administration Administering ALE Functions Monitoring Message Exchange
3.2 Detailed Monitoring and Tools for Problem andPerformance Analysis
SAP BusinessObjects Global Trade Service 10.0 with its component SLL-LEG 900 is technically based onSAP NetWeaver Application Server (AS) of SAP NetWeaver 7.0 including Enhancement Package 2For information about technical problem analysis, for example for database, operating system, workloadanalysis, and so on, refer to the Technical Operations Manual for SAP NetWeaver in SAP Library at
http://help.sap.com/nw70 System Administration Technical Operations Manual.
The Operation Guide for SAP BusinessObjects Global Trade Service 10.0 covers only differences andadditional information specific to the SAP BusinessObjects Global Trade Service.
3.2.1 Trace and Log Files
Logging and tracing for SAP BusinessObjects Global Trade Service 10.0 with its ABAP component SLL-LEG 900 is done in the application log. The application logs for all scenarios of SAP BusinessObjectsGlobal Trade Service 10.0 are integrated into the relevant functions for the individual business processescontent and can be accessed within the individual functions.To select application logs from a single point of entry, the standard transactionSLG1 can be utilizedthat is provided by SAP NetWeaver. Each log has the attributes Object and Sub-object. These attributesidentify the application that wrote the log. You can find the objects and sub-objects of SAPBusinessObjects Global Trade Service by selecting software componentSLL-LEG and object /SAPSLL/* with all assigned sub-objects.
Application logs for the following objects and their sub-objects
Application Log Name Description/SAPSLL/API_INBOUND API Inbound Processing/SAPSLL/BOM Bill of Materials (Preference)/SAPSLL/BOP Bill of Product (Restitution)/SAPSLL/BP Business Partner /SAPSLL/CUC Customs Code Lists/SAPSLL/CUHD Customs Shipments and Customs Declarations (Documents for Customs Management)/SAPSLL/CUHD_ARCHIVE Customs Document: Archiving/SAPSLL/CUHD_MAP Mapping of API Interface to Customs Document /SAPSLL/CUHD_SPL Document SPL screening (scenario B2/C2)/SAPSLL/CUHD_SYNCH Synchronization of Document with Feeder System/SAPSLL/CUPED Supplementary Customs Declaration/SAPSLL/CUPED_ARCH Supplementary Customs Declaration: Archiving
3 Monitoring of SAP BusinessObjects Global Trade Services
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
2010-12-13 PUBLIC 21 /56
http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
22/56
Application Log Name Description/SAPSLL/CUST Legal Services/SAPSLL/ECC Electronic Communication
/SAPSLL/GEN Generation/SAPSLL/IVM Inventory Management /SAPSLL/KMAT Configurable Materials/SAPSLL/LCLIC Legal Control: License/SAPSLL/LLNS Tariff Number System/SAPSLL/PR Customs Product /SAPSLL/PREF Preference/SAPSLL/RES Restitution/SAPSLL/REX Reexport /SAPSLL/SPL_ARCHIVE Archiving of the Sanctioned Party List Screening Data/SAPSLL/TLC Customs Value/SAPSLL/TREX Sanctioned Party List Screening with TREX /SAPSLL/TSPL Master Data for Sanctioned Party List Screening/SAPSLL/WL Logistics Integration Worklist /SAPSLL/WL_ARCHIVE Archiving for Logistics Integration Worklist
For more information about the process-integrated application log, see the relevant process andfunctional documentation for SAP BusinessObjects Global Trade Service scenarios in SAP Library at
http://help.sap.com/grc Global Trade Services < Release> Application Help < Language> .SAP BusinessObjects Global Trade Service uses standard SAP NetWeaver technology for its system logsand traces. For more information, see sectionTools in the Technical Operations Manual for SAPNetWeaver in SAP Library at http://he lp.sap.com/nw70 System Administration Technical OperationsManual Administration of SAP NetWeaver Systems AS ABAP (Application Server for ABAP) Monitoring.Content Lifecycle Management LogsCLM writes logs during various activities at runtime; these can be used by administrators for auditingand monitoring purposes. Application Log: Every CLM operation and corresponding steps carried out during that operation
are recorded in the application log:Transaction SLG1, object: /POA/CLMThe application log includes detailed information about error messages and sequential flow withrespect to CLM technical processing.This object includes the following subobjects or categories: PACKAGE: Use this subobject to monitor and analyze the logs specific to CLM packages (all
steps performed under Manage Packages function on CLM UI) CHECKPOINT: All actions performed underManage Content Groups function in CLM are
recorded for analysis under this application log subobject
3 Monitoring of SAP BusinessObjects Global Trade Services
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
22 /56 PUBLIC 2010-12-13
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/grchttp://help.sap.com/grchttp://help.sap.com/nw70http://help.sap.com/grc8/13/2019 GTS10.0 Operations Guide
23/56
DEPLOYMENT: Application logs related to deployment step from CLM are recorded underthis subobject
TECHNICAL: Additional technical log details are recorded under this subobject. Deployment Log: This is available on CLM UI. It displays statuses and messages for deployments
from CLM to the application. The deployment log provides details of application-specific messagesper deployment system and per content group.
Change Log or Change History: For all actions that can be carried out in CLM UI, such as editing,deployment, import, and export. CLM logs the change history using the change documentsfunction of ABAP. CLM change logging is enabled for packages and content groups and relatedtables. This can be seen in CLM UI withView History function.
Customizing object or Table Logging: All Customizing, control, and system database tables
defined in CLM are enabled for logging. Analysis of this logging can be done using SCU3 transactionin NetWeaver ABAP system if logging is switched on.Content Lifecycle Management (CLM) does not provide any special tracing and log files facility as thiscan be easily obtained from the NetWeaver ABAP framework.It is essential to collect trace and log files for RFC calls. CLM carries out critical operations throughRFC protocol to extract and deploy the contents onto application systems.Important Log and Trace Files for CLM
Component Content File Path
- System Trace Analysis RFC, HTTP, DB - Transaction ST01
- SQL Performance Trace and Analysis RFC, HTTP, DB - Transaction ST05
3.2.2 Interface Monitors
Interface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, and HTTP.For more information, see the Monitoring Setup Guide for SAP NetWeaver on SAP Service Marketplace at
http://service.sap.com//operationsnw70 Monitoring Monitoring Setup Guide for NW 7.0 SP Stack and the Technical Operations Manual at http://help.sap.com/nw70 System Administration
Technical Operations Manual Administration of SAP NetWeaver Systems AS ABAP (Application Server for AAdministration Connectivity.
Content Lifecycle Management (CLM) communicates with application system using RFC. For certainintensive operations, such as content extraction, interface monitors could be used to analyze the timespent on each RFC call.
InterfaceDetailedDescription Technology Used
You configure APIs and RFC functions in Customizing forContent LifecycleManagement under Maintain System Registry API Groups.
ABAP WebDynproapplication uses
these calls and
RFC
3 Monitoring of SAP BusinessObjects Global Trade Services
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
2010-12-13 PUBLIC 23 /56
http://help.sap.com/nw70http://service.sap.com//operationsnw70http://help.sap.com/nw70http://service.sap.com//operationsnw708/13/2019 GTS10.0 Operations Guide
24/56
InterfaceDetailedDescription Technology Usedinterfaces atruntime
/POA/CLM_WD ABAP WebDynproapplication isaccessed usingHTTP
HTTP
3.2.3 Workload Monitors
A default workload collector as part of CCMS monitoring and workload monitor through transactionST03N can be used to observe the workload records at application server level.
Component Monitor Detailed Description Prerequisites
- Workload Monitor TransactionST03N
Detailed analysis of workload ofapplication servers
-
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscape.It is an efficient method of transporting a selected number of requests into a group of transport targets,and uses clearly defined approval steps to ensure the quality of your target systems.For more information, see the Technical Operations Manual on SAP Help Portal at http://help.sap.com
SAP NetWeaver .
3.2.4 Data Growth and Data Archiving Monitors
You can monitor archiving of objects, such as documents or audit trails, independently of SAPBusinessObjects Global Trade Service, for example in any SAP ERP system. You can access the ArchiveInformation System (AS) for this in transactionSARA and by choosing Archive Explorer. From here,you can select the archived objects you want to display.
For more information, see the following documentation available on SAP Library:Monitor Documentation
Data Archiving Monitor(SAR_SHOW_MONITOR)
Technical Operations Manual in SAP Library at http://help.sap.com/nw70 SystemAdministration Technical Operations Manual General Administration Tasks and one of thefollowing options Data Archiving Database Administration
Database Monitoring(ST04 , DB02 )
The following table lists the fastest growing tables for SAP BusinessObjects Global Trade Service 10.0.If you integrated your processes into the logistics processes of SAP ERP as your feeder system, youshould also refer to the feeder system tables listed below.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
24 /56 PUBLIC 2010-12-13
http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
25/56
Component Table
SLL-LEG 900 CDPOSCDHDR
BALHDR/SAPSLL/CORREF
/SAPSLL/CUIT
/SAPSLL/CUPEDRI
/SAPSLL/CUSWLD
/SAPSLL/CUSWLF
/SAPSLL/CUSWLQ
/SAPSLL/PRPREF
Feeder System /SAPSLL/OBJIDX/SAPSLL/SSF
Component Monitor Detailed Description Prerequisites
CLM DB tables ST05 Observe critical operations and tablesthat take more time along with their hitand miss ratio
Switch the trace on before performingcostly operations, such as extractingcontent groups
Some of the intensive database tables that can be viewed during critical long-running operations: /POA/D_CLM_CP02 CLM Content group and Entity relationship /POA/D_CLM_DPLR Table for storing entity processing messages
/POA/D_CLM_ENT01 CLM Entity Table /POA/D_CLM_ENT02 CLM Entity Fields value Table /POA/D_CLM_ENT03 CLM Entity Entity Relationship /POA/D_CLM_ENT10 CLM Entity Raw Data Extract TableFor more information about archiving objects, see the following documentation in SAP Library at
http://help.sap.com/grc Global Trade Services < Release> Application Help < Language> SystemAdministration Archiving Data.For information about periodic tasks required to contain data growth (that is, to reorganize temporarydata), seePeriodic Tasks in this guide.
3.2.5 Specific Problem Analysis Tools
SAP BusinessObjects Global Trade Service 10.0 uses the following monitoring functions provided bySAP NetWeaver Application Server ABAP in SAP NetWeaver 7.0 including Enhancement Package 2,which are particularly vital for the processes in SAP BusinessObjects Global Trade Service.
IDoc Monitoring
For communicating with the feeder system or the converter software, you can monitor transactionalremote function calls (tRFC) using transaction sm58 . There, you can display the tRFCs that were sent
3 Monitoring of SAP BusinessObjects Global Trade Services
3.2 Detailed Monitoring and Tools for Problem and Performance Analysis
2010-12-13 PUBLIC 25 /56
http://help.sap.com/grc8/13/2019 GTS10.0 Operations Guide
26/56
asynchronously and determine whether any errors occurred. Then choose System AdministrationSystem Communication IDoc Monitoring to monitor the following:
IDoc List Display
You can display all the inbound and outbound IDocs IDoc Search
You can search for specific IDocs IDoc Statistics
You can call inbound and outbound IDocs that were sent and received during a specific time frame.You can also see which errors occurred in the IDoc processing.
IDoc Status MonitoringYou can display the status of IDocs that still have to be processed.
For more information about the communication process with the authorities, see the documentationin SAP Library at http://help.sap.com/grc Global Trade Services < Release> Application Help System Administration System Monitoring Communication between SAP GTS, EDI Converter, and
Customs Authorities.
Transactio nal Remote Function Call Monito ring
For communicating with the feeder system or the converter software, you can monitor transactionalremote function calls (tRFC) using transaction sm58 . There, you can display the tRFCs that were sentasynchronously and determine whet her any errors occurred.
Distributed Statistical Records
For more information about the motivation behind distributed statistical records and how to defineand use them, see section Technology in the Monitoring Setup Guide for SAP NetWeaver on SAPService Marketplace at http://service.sap.com/operationsnw70 Monitoring Monitoring SetupGuide (CEN 7.0 EHP SP Stack ) .
3.3 Data Consistency
SAP BusinessObjects Global Trade Service 10.0 only consists of one application component. Thus datainconsistency and data storage errors between different components cannot occur.Content Lifecycle Management (CLM) is used as a repository containing application content. Thecontent in the CLM repository can be added either by extraction from various application systems orby importing a new vendor-delivered package. During these operations CLM always loads the data firstand performs validations on top of such content to report functional inconsistencies. If there are abruptblockages, such as connection timeout, it can result in differences between the data maintained in CLMand data present in other sources.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.3 Data Consistency
26 /56 PUBLIC 2010-12-13
http://service.sap.com/operationsnw70http://help.sap.com/grchttp://service.sap.com/operationsnw70http://help.sap.com/grc8/13/2019 GTS10.0 Operations Guide
27/56
RECOMMENDATION
In this scenario, we recommend rerunning the operation as there is no impact of this operationon any business function in CLM.
3 Monitoring of SAP BusinessObjects Global Trade Services
3.3 Data Consistency
2010-12-13 PUBLIC 27 /56
8/13/2019 GTS10.0 Operations Guide
28/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
29/56
4 Logging On and Load Balancing
4 Logging On and Load Balancing
2010-12-13 PUBLIC 29 /56
8/13/2019 GTS10.0 Operations Guide
30/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
31/56
5 Management of SAP Application
SAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related to technicaladministration and operation. This infrastructure provides the following: A central interface for managing administrative middleware tasks Improved problem resolution processes for the entire solution Standardized administration of user profilesFor more information about the underlying technology, see the Technical Operations Manual of SAPNetWeaver 7.0 including Enhancement Package 2.
5.1 Starting and Stopping
SAP BusinessObjects Global Trade Service 10.0 is an add-on and therefore complies with the Start andStop Sequence and Tools of SAP NetWeaver 7.0 including Enhancement Package 2, on which SAPBusinessObjects Global Trade Service is installed.
For more information, see Starting and Stopping the System in the Technical Operations Manual forSAP NetWeaver in SAP Library athttp://help.sap.c om/nw70 System AdministrationTechnicalOperations Manual Administration of SAP NetWeaver Systems AS ABAP (Applicatoin Server for ABAP)
Management .For the list of components required for each scenario, seeSoftware Component Matrix in this guide.Refer to Troubleshooting in this guide for analyzing problems if a component does not start properly.
5.2 Software ConfigurationThis chapter explains which components or scenarios used by this application are configurable andwhich tools are available for adjusting.
Application configuration tools
Configuration Tool(s) Description
Customizing You can access the Customizing in the application system with transaction codeSPRO. TheCustomizing is the standard SAP tool for ABAP-based systems used for componentCustomizing.
SAP SolutionManager
SAP Solution Manager is the standard tool for process- and scenario-based configuration.For more information, see SAP Note1230438.
5 Management of SAP Application
5.1 Starting and Stopping
2010-12-13 PUBLIC 31 /56
http://help.sap.com/nw70http://help.sap.com/nw70http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=1230438&_NLANG=en&_NVERS=0http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
32/56
Note that SAP BusinessObjects Global Trade Service only requires the configuration of the businessscenarios and processes. With SAP BusinessObjects Global Trade Service being an add-on to SAPNetWeaver, no technical configuration is required that is specific to SAP BusinessObjects Global Trade
Service. It only uses basis parameters for database, operating system, and Application Server ABAPprovided by SAP NetWeaver.For more information about configuration and its concept, see SAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by KeyCapability Customizing.
5.3 Administration Tools
SAP BusinessObjects Global Trade Service 10.0 and its component SLL-LEG 900 are technically basedon SAP NetWeaver. For information about the relevant administration tools, see the TechnicalOperations Manual for SAP NetWeaver 7.0 in SAP Library athttp://help.sap.com/nw70 SystemAdministration.Content Lifecycle Management Administrator/Developer UtilitiesCLM provides utilities for testing purposes, which are intended for administrators and developer usergroups.Application API Adapter testing: Since CLM calls the RFC function modules while communicatingwith application systems, it expects a certain format and interface for these API/RFC function modules.
Moreover, an appropriate system setup is also required via system registry configuration where newapplication systems and their APIs are registered. For more information, see Customizing forContentLifecycle Management under Maintain System Registry.In actual scenarios or for productive usage; before you run CLM with system registry settings, it isadvisable to run the test adapter utility using transaction /POA/CLM_API_TESTER. You need to providethe system registry ID. The transaction checks API interfaces and also performs a test run for extractionand deployment operations.Cleaning up the CLM database: If you are running CLM for test purposes or on a test system, and
you find CLM database tables increasing in size over time; you can use transaction /POA/ CLM_CLEANUP to delete the CLM-specific database tables.
NOTE
This program completely deletes all CLM data and does not allow any preferences to be set forspecific entry deletion from CLM database tables. Hence it is intended to be used for cleaning upgarbage or unused data from the test CLM system only.
5 Management of SAP Application
5.3 Administration Tools
32 /56 PUBLIC 2010-12-13
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
33/56
5.4 Backup and Restore
You need to back up your system landscape regularly to ensure that you can restore and recover it incase of failure. The backup and restore procedure for SAP BusinessObjects Global Trade Service 10.0 asadd-on is identical to the one of SAP NetWeaver 7.0 including Enhancement Package 2 on which SAPBusinessObjects Global Trade Service is installed.For more information about the following topics see the mentioned section in the Technical OperationsManual for SAP NetWeaver in SAP Library at http://help.sap.com/nw70 System Administration
Technical Operations Manual: For Backup and Recovery, see Administration of SAP NetWeaver Systems AS ABAP (Application Server
for ABAP) Administration Backup and Recovery For High Availability, see section General Administration Tasks
The backup and restore strategy for applications consists of two parts: Backup and restore coverage for each component (see table below) Cross-system data dependencies and handlingThe backup and restore strategy for your system landscape should not only consider SAP systems butshould also be embedded in overall business requirements and incorporate your companys entireprocess flow.In addition, the backup and restore strategy must cover disaster recovery processes, such as the loss ofa data center through fire. It is most important in this context that you ensure that backup devices arenot lost together with normal data storage (separation of storage locations).
Categories ofSystemComponents
CategoryProperties Suggested Methods for Backup and Restore Examples
I Only software,noconfigurationor applicationdata
No backup, new installation in case of arecovery or
Initial software backup after installation andupgrade
Backup of log files
BDOC modeler
II Only softwareandconfigurationinformation,no applicationdata
Backup after changes have been applied or No backup, new installation and
configuration in case of a recovery Backup of log files
SAP GatewayComm. StationSAP Business ConnectorSAP IPC (2.0C)
IX Originalapplicationdata, dataexchange withother systems,data notmanaged by aDBMS
Data Application specific file system backup, data
consistency with other systems must beconsidered
Backup of software, configuration, log files
-
5 Management of SAP Application
5.4 Backup and Restore
2010-12-13 PUBLIC 33 /56
http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
34/56
Categories ofSystemComponents
CategoryProperties Suggested Methods for Backup and Restore Examples
XI Original
applicationdata, dataexchange withother systems,based on SAPNetWeaverApplicationServer
Data
Database and log backup, application logbackup (such as job logs in file system), dataconsistency with other systems must beconsidered
Backup of software, configuration, log files
SAP ERP
SAP CustomerRelationshipManagement (SAPCRM)
SAP NetWeaverBusiness Intelligence(SAP NetWeaver BI)
Component Categories Data to be backed up Application Data
SLL-LEG 900 XI Database and logbackup
File system backup(full and/orincremental)
Original Replicated
SLL_PI 900_
IX Database and log backup Original
SAP NetWeaver TREX I File system backup -SAP NetWeaver ADS II File system backup Original
Categories ofSystemComponents
CategoryProperties Suggested Methods for Backup and Restore Examples
VIII Originalapplicationdata,standalonesystem basedon SAP WebAS
Data: Database and log backup, application log backup (such
as job logs in file system) Backup of software, configuration log files
StandaloneSAP R/3
The following table lists the CLM components relevant for backup and recovery:
Component Data to be Backed Up Backup Method/Tool Recommended Backup FrequencyPOASBC Application database tables, logs Database and log backup Yearly
5.5 Application Copy
For more information about prerequisites, procedures, and limitations for copying components of SAPBusinessObjects Global Trade Service, see section System Copy in the Technical Operations Manualfor SAP NetWeaver in SAP Library athttP://help.sap.com/nw70 System Administration TechnicalOperations Manual Administration of SAP NetWeaver Systems Administration Background Processing.
5 Management of SAP Application
5.5 Application Copy
34 /56 PUBLIC 2010-12-13
http://http//help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
35/56
5.6 Periodic Tasks
5.6.1 Scheduled Periodic Tasks
For more information about standard background jobs and periodical tasks for SAP NetWeavercomponents, see the Technical Operations Manual for SAP NetWeaver in SAP Library athttp://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaveSystems Administration Background Processing.CLM uses background jobs for the execution of some operations at runtime. The following table givesan overview of the exact programs that are scheduled in the background and the frequency at whichthese are executed.Scheduled periodic tasks for Content Lifecycle Management:
Program Name/Task
Task-Scheduling
ToolRecommendedFrequency Detailed Description
/POA/ R_CLM_DEPLOY_RESULTS_POLL
Automatic 10 minutes: This can bechanged inCustomizing for ContentLifecycle Managementunder Maintain TechnicalSettings
Used to retrieve the deploymentresults of application contentfrom target application systems.For more information, seeContentGroup Deployment in SAP Librarydocumentation under ContentLifecycle Management Content Groupand Package Management ContentGroup Deployment .
Other background tasks in Content Lifecycle Management that are scheduled to run immediately:
Program Name/Task Task-Scheduling Tool Recommended Frequency Detailed Description
/POA/R_CLM_EXTRACT Automatic Immediately when theoperation is triggered
Background task duringcontent group extraction
/POA/R_CLM_DEPLOY Automatic Immediately when theoperation is triggered
Background task forcontent group upload anddeployment
5.6.2 Required Manual Periodic Tasks
This chapter describes all manual tasks required to run periodically to keep the application runningsmoothly over time. A manual task needs a person to for each execution in comparison to the scheduledtasks listed above which can be automated using a task scheduler program. It is important that youmonitor the successful execution of these tasks on a regular basis.SAP BusinessObjects Global Trade Service creates log files to identify problems. You need to check thelog files on a regular basis, for example, to detect blocked documents. This enables you to identifyproblems promptly and to react accordingly.Also, the following application-specific tasks are relevant for execution of background jobs or requireexecution in background jobs:
5 Management of SAP Application
5.6 Periodic Tasks
2010-12-13 PUBLIC 35 /56
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
36/56
In the feeder system: Check change pointers for master data and transfer changed data from feeder system to SAP
BusinessObjects Global Trade Service Creditors relevant for all scenarios in the application Debitors relevant for all scenarios in the application Material master relevant for all scenarios in the application Bill of materials relevant for Trade Preference Processing and Legal Control of the
application Transfer duty-paid stock for customs warehousing relevant for Imports and Exports with
Customs Management of the applicationFor more information about the periodic tasks in the feeder system for SAP BusinessObjects GlobalTrade Service, see section Data Replication in the Configuration Guides on SAP Service Marketplaceat http://service.sap.com/swdc SAP Installations and Upgrades Installations and Upgrades - Entryby Application Group SAP Solutions for Governance, Risk and Compliance SAP Global Trade Services
Installation and Upgrade. In SAP BusinessObjects Global Trade Service
Distribute Product Data to Feeder System for Special Customs Procedures relevant forimports and exports with Customs Management of the application
http://help.sap.com/grc Global Trade Services < Release> Application Help < Language>
Customs Management Master Data. Further functions can also be scheduled for background processing but do not require
periodical execution. The relevant functional descriptions contain references if execution ofthe programs using background jobs is possible.For more information, see the documentation in SAP Library at http://help.sap.com/grc
Global TradeServices < Release> Application Help < Language> System Administration SystemMonitoring.
5.7 Load BalancingSAP BusinessObjectsGlobal Trade Service uses no specific load balancing methods for its onecomponent SLL-LEG. If necessary, it only applies methods provided by the basis technology of SAPNetWeaver.For more information about the load balancing with SAP NetWeaver, see SAP Library athttp://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaverSystems.As a web-based application, the basis for logon and load balancing in Content Lifecycle Management
is a high availability landscape setup together with a load balanced network setup.
5 Management of SAP Application
5.7 Load Balancing
36 /56 PUBLIC 2010-12-13
http://help.sap.com/nw70http://help.sap.com/grchttp://help.sap.com/grchttp://help.sap.com/grchttp://help.sap.com/grchttp://help.sap.com/grchttp://service.sap.com/swdchttp://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/grchttp://help.sap.com/grchttp://service.sap.com/swdc8/13/2019 GTS10.0 Operations Guide
37/56
For more information about network load balancing, see the Technical Infrastructure Guide for SAPNetWeaver on SAP Service Marketplace athttp://service.sap.com/instguides.A load-balanced network using SAP Web Dispatcher together with logon groups in the SAP NetWeaver
systems can be used to redirect certain users to specific application servers.
5.8 User Management
SAP BusinessObjects Global Trade Service uses the user management tools provided by SAP NetWeaver.For more information, see http://help.sap.com/nw70 Functional View SAP NetWeaver by KeyCapability Solution Lifecycle Management by Key Capability Identity Management Identity Management oApplication Server ABAP .
All scenarios and components in Content Lifecycle Management use the user management functionsprovided by NetWeaver.For more information about user administration and authentication, see the application security guideon SAP Service Marketplace athttp://service.sap.com/securityguide.
5.9 Printing
SAP BusinessObjects Global Trade Service uses the SAP NetWeaver technology for printing. For moreinformation about printing, see SAP Library at http://help.sap.com/nw70 Functional View SAPNetWeaver by Key Capability Solution Lifecycle Management by Key Capability System Management SAPGuide (BC-CCM-PRN).
5 Management of SAP Application
5.8 User Management
2010-12-13 PUBLIC 37 /56
http://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
38/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
39/56
6 High Availability
The processes of SAP BusinessObjects Global Trade Service are based on master and transaction datafrom one or more feeder systems. If a failure on SAP BusinessObjects Global Trade Service componentSLL-LEG occurs, all business processes in the feeder system based on action in SAP BusinessObjectsGlobal Trade Service cannot be performed. To avoid any inconveniences SAP BusinessObjects GlobalTrade Service provides a recovery scenario. In SAP Compliance Management, for example, thediscontinuation of the logistics processes in the feeder systems depends on customizing settings foreach area within SAP Compliance Management. If action from SAP BusinessObjects Global TradeService is required by the feeder system at a time when SAP BusinessObjects Global Trade Service is notavailable, you can configure your system in such a way that one of the following options holds true: Either all subsequent processes are blocked until SAP BusinessObjects Global Trade Service is
available again and can perform the tasks needed before continuing the processes in the feedersystem.
All subsequent processes can be performed without getting a response from SAP BusinessObjectsGlobal Trade Service and SAP BusinessObjects Global Trade Service will perform the tasks once
the system becomes available again. Alternatively, you can allow all subsequent processes to be performed without any checks if SAP
BusinessObjects Global Trade Service is not available.The main framework of Content Lifecycle Management is based in SAP NetWeaver. If the softwarecomponent for CLM becomes unavailable, all business scenario concerning CLM stop working.Unavailability of CLM does not break any other software components or application functions.
ComponentDetailedDescription HA Setup Description
POASBC - POAShared BusinessComponents 1.0
CLM is part ofthe POASBCSoftwarecomponent
For more information about high availability and switchover, see theTechnical Operations Manual on SAP Help Portal at http://help.sap.com
SAP NetWeaver .
NOTE
We recommend you also refer to the following documentation: BC SAP High Availability for SAP NetWeaver 7.0 including Enhancement Package 2
This document provides a general discussion and sound introduction to the topic of highavailability for the SAP NetWeaver Application Server. It is part of the standard SAPdocumentation package delivered with SAP NetWeaver Application Server. It dealscomprehensively with safeguarding SAP NetWeaver Application Server system operation.
6 High Availability
2010-12-13 PUBLIC 39 /56
8/13/2019 GTS10.0 Operations Guide
40/56
You can find this document on SAP Service Marketplace at http://service.sap.com/haMedia Library Documentation HA Documentation.
Switchover
For information about switchover, see on SAP Service Marketplace the infrastructureinformation at http://service.sap.com/installnw70 1- Planning Technical InfrastructureGuide High Availability Support for Failover Clustering (HA) Switchover Unitsand in theinstallation information at http://service.sap.com/installnw70 2- Installation - SAPNetWeaver Systems SAP NetWeaver 7.0 incl. EHP2 - Installation Guides
6 High Availability
40 /56 PUBLIC 2010-12-13
http://service.sap.com/installnw70http://service.sap.com/installnw70http://service.sap.com/ha8/13/2019 GTS10.0 Operations Guide
41/56
7 Software Change Management
Software Change Management standard izes and automates software distribution, maintenance, andtesting procedures for complex software landscapes and multiple software development platforms.These functions support your project teams, development teams, and application support teams.The goal of Software Change Management is to establish consistent, solution-wide change managementthat allows for specific maintenance procedures, global rollouts (including localizations), and openintegration with third-party products.SAP BusinessObjects Global Trade Service 10.0 and its component SLL-LEG 900 are based on SAPNetWeaver Application Server ABAP of SAP NetWeaver 7.0 including Enhancement Package 2. Youcan find information about the Software Change Management in the according document section ofthe Technical Operations Manual for SAP NetWeaver in SAP Library athttp://help.sap.com/nw70
System Administration Technical Operations Manual Administration of SAP NetWeaver Systems AS ABA(Application Server for ABAP) Software Logistics.The following topics are covered in the SAP NetWeaver document: Transport and Change Management - Enables and secures the distribution of software changes
from the development environment to the quality assurance and production environment. Development Request and Development Release Management - Enables customer-specific
maintenance procedures and open integration with third-party products. Support Packages and SAP Notes Implementation - Provide standardized software distribution and
maintenance procedures. Release and Upgrade Management - Reduces time, cost, and risk associated with upgrades. Quality Management and Test Management - Reduce the time, cost, and risk associated with
software changes. Template Management - Enables and secures the rollout of global templates, including
localizations.
7.1 Transport and Change Management
SAP NetWeaver includes the Change and Transport System (CTS) which is a tool that helps you toorganize development projects in the ABAP Workbench and in Customizing, and then transport thechanges between the SAP Systems in your system landscape.For more information, see Technical Operations Manual for SAP NetWeaver in SAP Library athttp://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP NetWeaveSystems AS ABAP (Application Server for ABAP) Software Logistics. Change and Transport System.
7 Software Change Management
7.1 Transport and Change Management
2010-12-13 PUBLIC 41 /56
http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
42/56
7.2 Development Requests and Development ReleaseManagement
The transport workflow provides a framework for transporting enhancements or new developmentsof existing business functions in a system landscape. It provides a direct connection betweendevelopment and transport administration. The transport workflow manages the transport process,determines the user for each individual step automatically, and then displays an interface that they canuse to perform the task directly.It is an efficient method of transporting a selected number of requests into a group of transport targets,and uses clearly defined approval steps to ensure the quality of your target systems.For more information, see the Technical Operations Manual for SAP NetWeaver in SAP Library at
http://help.sap.com/nw70 System Administration Technical Operations Manual Administration of SAP
NetWeaver Systems AS ABAP (Application Server for ABAP) Software Logistics. Releasing Software Changes andQuality Management .
7.3 Quality Management and Test Management
You can test interfaces with the test workbench for SAP NetWeaver Application Server (ABAP).For more information, see the documentation in SAP Library at http://help.sap.com/ nw70
Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key CapabilityTesting .
7.4 Support Packages and Patch Implementation
Information about the Support Packages (SPs) available for SAP BusinessObjects Global Trade Service10.0 can be found in the Release Information on SAP Service Marketplace athttp://service.sap.com/ocs-schedules .Support Packages for components based on the SAP NetWeaver Application Server ABAP are appliedusing the Support Package Manager. For more information, see the Technical OperationsManual for
SAP NetWeaver in SAP Library athttp://help.sap.com/nw70 < SPSxx > Support Package Stack Guide .SAP Notes that require code changes for components based on the SAP NetWeaver Application ServerABAP can be applied using the SAP Note Assistant. For more information, see the documentation inSAP Library at http://help.sap.com/nw70 Functional View SAP NetWeaver by Key Capability SolutionLifecycle Management by Key Capability Software Lifecycle Management Note Assistant .
7 Software Change Management
7.2 Development Requests and Development Release Management
42 /56 PUBLIC 2010-12-13
http://service.sap.com/ocs-scheduleshttp://help.sap.com/nw70http://help.sap.com/nw70http://help.sap.com/nw70http://service.sap.com/ocs-scheduleshttp://service.sap.com/ocs-scheduleshttp://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
43/56
7.5 Release and Upgrade Management
You can check which components are installed in your system by logging on to your SAPBusinessObjects Global Trade Services and selecting from the menu options System Status.For more information about release and upgrade options or plans for SAP BusinessObjects Global TradeServices, see http://service.sap.com/pam .
7 Software Change Management
7.5 Release and Upgrade Management
2010-12-13 PUBLIC 43 /56
http://service.sap.com/pam8/13/2019 GTS10.0 Operations Guide
44/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
45/56
8 Troubleshooting
In case of problems, refer to the troubleshooting guide for SAP NetWeaver Application Server. For moreinformation, see SAP Library at http://help.sap.com/nw70 System Administration Technical OperationsManual General Administration Tasks Troubleshooting for SAP Web Application Server .The SAP NetWeaver Problem Analysis Guide contains the following problem analysis scenarios for thevarious components of the usage type Application Server. Security Problem Analysis Scenarios Adobe Document Services Problem Analysis Scenarios System Landscape Directory Problem Analysis Scenarios Process Monitoring Infrastructure Problem Analysis Scenarios SAP Knowledge Warehouse Problem Analysis Scenarios Web AS Java
Change Management Server Problem Analysis Scenarios J2EE Engine Problem Analysis Scenarios Web Dynpro Java (ESS Scenario) Problem Analysis Scenarios
Design Time Repository Problem Analysis Scenarios SAP Java Connector Problem Analysis Scenarios
For more information about problem analysis and troubleshooting for all SAP NetWeaver Usage Types,see the SAP NetWeaver Problem Analysis Guide (PAG) in SAP Library athttp://help.sap.com/nw70
Functional View SAP NetWeaver by Key Capability Solution Lifecycle Management by Key Capability SNetWeaver PAG Usage Type Application Server ABAP .If you encounter specific problems in executing processes you need to check the logs in the feedersystem and in SAP BusinessObjects Global Trade Service. If no monitoring information is displayed inthe CCMS Alert Monitor with transaction RZ20 of the central monitoring system, see CCMS
Monitoring Infrastructure Problem Analysis Guide (PAG).In addition, a troubleshooting section for the communication process between SAP BusinessObjectsGlobal Trade Service, the converter system, and the Customs authorities when processing imports andexports with Customs Management is included in SAP Library for SAP BusinessObjects Global TradeService. For more information, see SAP Library at http://help.sap.com/grc Global Trade Services
Application Help < Language> System Administration System Monitoring.
8 Troubleshooting
2010-12-13 PUBLIC 45 /56
http://help.sap.com/grchttp://help.sap.com/nw70http://help.sap.com/nw708/13/2019 GTS10.0 Operations Guide
46/56
This page is left blank for documents that are printed on both sides.
8/13/2019 GTS10.0 Operations Guide
47/56
9 Support Desk Management
Support Desk Management enables you to set up an efficient internal support desk for your supportorganization that seamlessly integrates your end users, internal support employees, partners, and SAPActive Global Support specialists with an efficient problem resolution procedure.For support desk management, you need the methodology, management procedures, and toolsinfrastructure to run your internal support organization efficiently.
9.1 Remote Support Setup
SAP support needs to be able to work remotely for highest efficiency and availability. For this support,SAP uses the remote connection with SAProuter for a specific problem that you log by creating acustomer message in the SAP Support Portal. For information about SAProuter, see SAP Note486688and the SAP Notes this SAP Note refers to for specific settings or parameters that are necessary. Furtherassistance provides SAP Note812386
9.2 Problem Message Handover
For sending problem messages/tickets to SAP use components SLL-LEG* and provide a detailed andreproducible problem description.
9.3 Services for SAP BusinessObjects Trade Services
SAP BusinessObjects Global Trade Service offers, for example, the follow