SolOpGuide MAMC30 V12 En

Solution Operation Guide

SAPTM

IS-M/AMC

Release SAP IS-MAMC 3.0Document Version 1.2 – June 2007

© Copyright 2004 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in anyform or for any purpose without the express permission of SAP AG.The information contained herein may be changed without priornotice.

Some software products marketed by SAP AG and its distributorscontain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registeredtrademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation 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 theOpen Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,VideoFrame, and MultiWin are trademarks or registered trademarks ofCitrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registeredtrademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., usedunder license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, andother SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All otherproduct and service names mentioned are the trademarks of theirrespective companies. Data contained in this document servesinformational purposes only. National product specifications mayvary.

These materials are subject to change without notice. These materialsare provided by SAP AG and its affiliated companies ("SAP Group")for informational purposes only, without representation or warranty ofany kind, and SAP Group shall not be liable for errors oromissions with respect to the materials. The only warranties for SAPGroup products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any.Nothing herein should be construed as constituting an additionalwarranty.

DisclaimerSome components of this product are based on Java™. Any codechange in these components may cause unpredictable and severemalfunctions and is therefore expressively prohibited, as is anydecompilation of these components.

Any Java™ Source Code delivered with this product is only to be usedby SAP’s Support Services and may not be modified or altered in anyway.

Documentation in the SAP Service MarketplaceYou can find this documentation at the following Internet address:service.sap.com/instguides

SAP AGNeurottstraße 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com

Typographic ConventionsType Style Represents

Example Text Words or characters thatappear on the screen. Theseinclude field names, screentitles, pushbuttons as well asmenu names, paths andoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrasesin body text, titles of graphicsand tables

EXAMPLE TEXT Names of elements in thesystem. These include reportnames, program names,transaction codes, tablenames, and individual keywords of a programminglanguage, when surrounded bybody text, for example,SELECT and INCLUDE.

Example text Screen output. This includesfile and directory names andtheir paths, messages, namesof variables and parameters,source code as well as namesof installation, upgrade anddatabase tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

<Example text> Variable user entry. Pointedbrackets indicate that youreplace these words andcharacters with appropriateentries.

EXAMPLE TEXT Keys on the keyboard, forexample, function keys (suchas F2) or the ENTER key.

IconsIcon Meaning

Caution

Example

Note

Recommendation

Syntax

Solution Operation Guide for SAP IS-M/AMC

Contents

4 June 2007

Contents

1 Getting Started .........................................................................61.1 Global Definitions ...................................................................61.2 Important SAP Notes ..............................................................71.3 History of Changes .................................................................8

2 Technical System Landscape ................................................92.1 Graphic Landscape Description ............................................92.2 Scenario/Component Matrix ..................................................9

2.2.1 Sales of Classified Ads in the CIC ............................................92.2.2 Sales of Classified Ads in the Internet ...................................102.2.3 Search of Classified Ads in the Internet.................................10

2.3 Related Documentation ........................................................113 Monitoring of SAP IS-M/AMC ...............................................11

3.1 Alert Monitoring with CCMS.................................................113.1.1 Component Alert Monitoring...................................................123.1.2 Alert Monitoring of Scenarios .................................................13

3.2 Detailed Monitoring and Tools for Problem andPerformance Analysis ....................................................................14

3.2.1 Component Specific Analysis Tools.......................................143.2.2 Scenario-specific Problem Analysis Tools ............................15

4 Management of SAP IS-M/AMC ............................................174.1 Administration Tools of Software Components ................174.2 Starting and Stopping...........................................................174.3 Backup and Restore .............................................................184.4 System Copy .........................................................................184.5 Periodic Tasks.......................................................................19

4.5.1 Scheduled Periodic Tasks.......................................................194.5.2 Required Manual Periodic Tasks ............................................19

4.6 Logging On and Load Balancing.........................................194.7 User Management .................................................................194.8 Printing...................................................................................21

5 High Availability.....................................................................216 Software Change Management ............................................22

6.1 SAP IS-M/AMC .......................................................................226.1.1 Transport and Change Management ......................................22


Contents

June 2007 5

6.1.2 Development Requests and Development ReleaseManagement ..........................................................................................226.1.3 Template Management.............................................................236.1.4 Quality Management and Test Management..........................236.1.5 Support Packages and Patch Implementation.......................23

7 Appendix.................................................................................237.1 Categories of System Components for Backup andRestore.............................................................................................237.2 Related Guides ......................................................................257.3 Related Information ..............................................................25


1.1 Global Definitions

6 June 2007

1 Getting Started

This guide does not replace the daily operations handbook that SAP recommendscustomers create for their specific production operations.

About this Guide

Design, implementation and optimized operation of your SAP solution 24 hours a day has neverbeen more vital for your business success.

This guide provides a starting point for managing your SAP solutions and maintaining and runningthem to their full potential. It contains specific information for various tasks and lists the tools thatyou can use to implement them. This guide also provides references to the documentation requiredfor these tasks, meaning that you will sometimes also need other guides, such as the MasterGuide, SAP NetWeaver Technical Operations Manual , and SAP Library.

The following NetWeaver documentation is particularly important and must be used in conjunctionwith this SAP IS-M/AMC Solution Operations Guide, since the SAP IS-M/AMC guide only coversSAP IS-M/AMC-specific topics, and not general NetWeaver topics:

Document Available From:

Technical OperationsManual for SAPNetWeaver

service.sap.com/nw04 SAP NetWeaver 2004s - Release-Specific Information Documentation Technical Operations Manual

Monitoring SetupGuide for SAPNetWeaver

service.sap.com/nw04 SAP NetWeaver 2004s - Release-Specific Information Documentation Monitoring and Operations Monitoring and Supportability

SAP NetWeaverSecurity Guide

help.sap.com/nw04 SAP NetWeaver 2004s SAP Library SAP NetWeaver Library Administrator’s Guide SAP NetWeaverSecurity Guide

Target Groups:

Technical Consultants

System Administrators

Solution Consultants

Business Process Owner

Support Specialist

1.1 Global DefinitionsSAP Solution:

A SAP solution represents a market view of groups of related business scenarios. The delivery of asolution contains SAP components which are essential for implementing all solution-relatedbusiness scenarios, processes, and functions. Implementation knowledge is included with eachsolution.

Business Scenario:

From a microeconomic perspective, a business scenario is a cycle, which consists of severaldifferent interconnected logical processes in a time sequence. Typically, a business scenario

1 Getting Started

1.2 Important SAP Notes

June 2007 7

includes several company departments and involves with other business partners. From a technicalpoint of view, a business scenario needs at least one SAP application component (SAP ECC, SAPIS-M/AMC, and so forth) for each cycle and possibly other third-party systems. A business scenariois a unit which can be implemented separately and reflects the customer’s perspective course ofbusiness.

Component:

A component is the smallest individual unit that is considered within the Solution DevelopmentLifecycle; components are produced, delivered, installed and maintained separately.

1.2 Important SAP Notes

Check regularly to see which SAP Notes are available for the Solution OperationGuide.

Important SAP Notes

SAP NoteNumber

Title Comment

1033651 Note on SAP IS-M/AMCdocumentation

Collective note

1024503 Current Applet VersionIS-M/AMC Web Editor 3.0

This note contains the latest IS-M/AMC UIapplet.

841814 Java BadI Implementationfor IS-M/AMC UI

209834 CCMS agent technology Collective note

1058757 Problems with X-Serverand rendering on Linux

Requirements for graphical componentsavailable on Linux

1067317 Integrating IS-MAMC UIin the CustomerInteraction Center

This note contains a reference to the IS-M/AMC Configuration Guide

1015990 Installation of Web EditorIS-MAMC

1016455 Installation of WebComponents IS-MAMC3.0

1069457 Implementation of WebScenarios Using IS-MAMC

This note contains a reference to the S-M/AMCWeb Implementation Guide


1.3 History of Changes

8 June 2007

1.3 History of Changes

Make sure you use the current version of the Solution Operation Guide.The current version of the Solution Operation Guide is atservice.sap.com/instguides on SAP Service Marketplace.

The following table provides an overview of the most important changes in prior versions.

Version Important Changes

1.00 First version of SAP IS-M/AMC Solution Operation Guide

2 Technical System Landscape

2.1 Graphic Landscape Description

June 2007 9

2 Technical System Landscape2.1 Graphic Landscape Description

2.2 Scenario/Component Matrix2.2.1 Sales of Classified Ads in the CIC

Business Scenario/Software Component Matrix (M = mandatory / O = optional):

Business Scenario

Sales of Classified Ads in the CIC

Software Component

… with Ad ContentCreation in EditorMode

… with Ad ContentCreation in TemplateMode

SAP ERP 2005

Advertising Management (IS-M/AM)

Document Management System(DMS)

M

MO

M

MO

SAP NetWeaver 2004s M M


2.2 Scenario/Component Matrix

10 June 2007

Adobe Document Services O O

SAP IS-M/AMC 3.0

IS-M/AMC Server

IS-M/AMC UI

M

M

M

M

M

M

2.2.2 Sales of Classified Ads in the InternetBusiness Scenario/Software Component Matrix (M = mandatory / O = optional):

Business Scenario

Sales of Classified Ads on the Internet

Software Component

… with Ad ContentCreation in EditorMode

… with Ad ContentCreation in TemplateMode

SAP ERP 2005



M

M

O

M

M

O

SAP NetWeaver 2004s

Adobe Document Services

M

O

M

O

SAP IS-M/AMC 3.0

IS-M/AMC Server

IS-M/AMC Web

IS-M/AMC Web Editor

M

M

M

O

M

M

M

O

2.2.3 Search of Classified Ads in the InternetBusiness Scenario/Software Component Matrix (M = mandatory / O = optional):

Business ScenarioSoftware Component

Search for classified Ads in the Internet

SAP ERP 2005



M

M

O

SAP NetWeaver 2004s

Adobe Document Services

M

O

SAP IS-M/AMC 3.0 M

3 Monitoring of SAP IS-M/AMC

2.3 Related Documentation

June 2007 11

IS-M/AMC Server

IS-M/AMC Web

IS-M/AMC Web Editor

M

M

O

2.3 Related DocumentationThe following table lists where you can find more information about the technical systemlandscape.

Topic Guide/Tool Quick Link or Path

Application- andIndustry-specificComponents such asSAP Financials andSAP Retail

Master Guide service.sap.com/instguides

TechnologyComponents such asSAP Web ApplicationServer

Master Guide service.sap.com/instguides

Sizing Quick Sizer Tool service.sap.com/sizing

Technical Configuration Technical InfrastructureGuide

service.sap.com/ti

Scalability Technical InfrastructureGuide

service.sap.com/ti

High Availability Technical InfrastructureGuide

service.sap.com/ti

Security Technical InfrastructureGuide

service.sap.com/ti

service.sap.com/security

Component Monitoringwith CCMS

Monitoring Setup Guide forSAP NetWeaver

service.sap.com/nw04 SAPNetWeaver 2004s – Release-Specific informationDocumentation Monitoringand OperationsMonitoring andSupportability

3 Monitoring of SAP IS-M/AMCMonitoring is an essential task within management of SAP Technology. A section has thereforebeen devoted solely to this subject.

You can find more information about the underlying technology in the Technical Operations Manualfor SAP Technology in the SAP Library under mySAP Technology Components.

3.1 Alert Monitoring with CCMS



12 June 2007

Proactive, automated monitoring is the basis for safeguarding reliable operations within your SAPsystem environment. SAP provides you with the infrastructure and recommendations required toset up your alert monitoring to identify critical situations for SAP IS-M/AMC as quickly as possible.

For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) atservice.sap.com/nw04 SAP NetWeaver 2004s - Release-Specific Information Documentation Monitoring and Operations Monitoring and Supportability.

3.1.1 Component Alert MonitoringSAP IS-M/AMC is based on NetWeaver 2004s Usage type AS-ABAP and AS-Java. For generalinformation about Alert Monitoring, see the Technical Operations Manual for SAP NetWeaver in theSAP Help Portal at help.sap.com under SAP NetWeaver Adminstrator’s Guide.

For information on enabling the auto-alert mechanism of CCMS, see SAP Note 617547.

3.1.1.1 SAP NetWeaver 2004sSAP NetWeaver 2004s is the integration and application platform for SAP IS-M/AMC 3.0.Therefore, the following SAP NetWeaver components must be integrated into the monitoringinfrastructure:

SAP Web Application Server (ABAP) 7.00 (for IS-M/AMC Server 3.0)

SAP Web Application Server (Java) 7.00 (for SAP IS-M/AMC Web, ADS)

For more information and detailed procedures, see the Monitoring Setup Guide for SAP NetWeaver(MSG) and the NetWeaver 2004s Technical Operations Manual.

3.1.1.2 IS-M/AMC Server 3.0The main component in your SAP IS-M/AMC Solution is IS-M/AMC Server 3.0. It is based on SAPWeb Application Server (ABAP) 7.00. For information on monitoring the Web AS (ABAP), see theMonitoring Setup Guide for SAP NetWeaver (MSG) and the NetWeaver 2004s TechnicalOperations Manual.

3.1.1.3 GRMG CustomizingIf you are using the automatic upload of the CCMS/GRMG configuration, the GRMG Customizingsettings for the application should already be available in the central CCMS system. If this is not thecase, perform the upload manually:

Select the Server-Services cluster tab node in the J2EE Admin Tool.

Select the Monitoring service.

Select the GRMG Customizing on the Runtime tab

Navigate to the application sap.com/is~ism~amc~web~engine

When you click on the Upload button, the system creates the Customizing file in thefolder usr\sap\PRFCLOG\grmg in your J2EE engine.

Call transaction grmg in the central CCMS system.



June 2007 13

Upload the Customizing file generated by clicking on the Upload button.

Perform monitoring by using transaction rz20 in CCMS.

Access the Monitor by selecting the node SAP CCMS Monitor Templates->Availabilityand Performance Overview

Monitor the availability of the SAP IS-M/AMC web application by navigating to the nodeGRMG-Tested Availability (Web Components).

3.1.2 Alert Monitoring of ScenariosIn addition to the required monitoring of each component, some additional monitoring objects aredesigned to monitor cross-component communication and other scenario-specific critical situations.

Business Scenario Sales of Classified Ads in the CIC

… with Ad Content Creation inEditor Mode

… with Ad Content Creation inTemplate Mode

Monitoring Tool There is no specific monitoring tool for this business scenariovariant. See, the Technical Operations Manual for SAPNetWeaver.


3.2 Detailed Monitoring and Tools for Problem and Performance Analysis

14 June 2007

3.2 Detailed Monitoring and Tools forProblem and Performance Analysis

3.2.1 Component Specific Analysis Tools

3.2.1.1 IS-M/AMC Server 3.0IS-M/AMC Sever 3.0 technology is based on Web Application Server Release 7.00. For informationabout technical problem analysis (such as with a database, the operating system, or workloadanalysis), see the Solution Operation Guide for Web Application Server. This guide only covers thedifferences and additional information specific to this solution.

Trace Files and Log FilesTrace files and log files are essential for analyzing problems.

IS-M/AMC Server 3.0 application-specific logging information is written in logs files. You canactivate logging for specific users in Customizing under SAP Media MAMC Tools MakeTechnical Settings for User.

The user can switch ON logging for IS-M/AMC UI. Logging can be switched ON by user in thesystem. There are two levels of logging:

Debug: The system displays all messages.

Error: The system only displays information if an error occurs.

The user can specify whether IS-M/AMC UI should write messages to the Java console or to a logfile in the user cache.



June 2007 15

3.2.1.2 IS-M/AMC Web 3.0Select the Server-Services cluster tab node in the J2EE Admin Tool:

Select the Log Configurator service.

Select the Locations tab on the Runtime tab

Navigate to the location com.sap.ism.amc

Define the trace level according to your requirements

The following specific settings must be made to log communication to the Web-Editor Applet:

Navigate to location com.sap.ism.amc.web.editor.server

Define the trace level according to your requirements

Select the Server-Services cluster tab node in the J2EE Admin Tool:

Select the Log Viewer service.

Navigate to the log folder for the current server on the Runtime tab.

Display the trace file by clicking on the defaultTrace.trc node.

3.2.1.3 IS-M/AMC Web-Editor Applet 3.0A specialist parameter for defining the logging properties is available for the Web Editor Applet:

logPropertiesURL URL, from which the Property file is loaded, which defines thesettings for logging and tracing in the Web Editor.

For more information, see the Syntax and Semantics of theProperties File unit of the Java Development Manual in the SAPLibrary.

If this parameter is not defined, the system copies the IS-M/AMC Server settings (see 3.2.1.1)settings.

3.2.2 Scenario-specific Problem Analysis ToolsThe following information applies to all SAP IS-M/AMC 3.0 business scenarios.

3.2.2.1 InterfacesInterface monitors are essential for analyzing problems with interfaces such as RFC, IDoc, andHTTP. For more information, see the Monitoring Setup Guide for SAP NetWeaver (MSG) and theNetWeaver 2004s Technical Operations Manual.



16 June 2007

Data Archiving MonitorsFor more information, see the following documentation available on the SAP Help Portal:

Monitor Documentation

Performance database collector(RSDB_TDB)

Database monitoring (ST04, DB02)

Monitoring Setup Guide for SAP NetWeaver(MSG)

NetWeaver 2004s Technical Operations Manual

The top fastest growing tables are: JQTADCOMPONENT

JQTCOMP_CLUST

JQTPREVIEWFORMAT

JQTPREVIEW_CLUST

JQTADC

JQTPRINTFORMAT

JQTPRINTF_CLUST

Reorganization Report

There is a reorganization report provided to delete ad content. Various options are provided fordeleting ad content.

Delete ad content completely Delete all ad content information.

Delete inactive versions Only delete inactive versions of ad content.

Delete print formats Delete print formats stored in the system.

Delete preview formats Delete preview formats stored in the system.

For information on the periodic tasks required to contain data growth (that is, to reorganizetemporary data), see to the periodic tasks section in this guide.

Distributed Statistical RecordsFor a detailed explanation of the Distributed Statistical Records, see the Technical OperationsManual for SAP NetWeaver Administration of SAP NetWeaver Systems AS ABAP(Application Server for ABAP) Monitoring Global Workload Monitor.

4 Management of SAP IS-M/AMC

4.1 Administration Tools of Software Components

June 2007 17

For more information, see also the Technical Operations Manual for SAP NetWeaverAdministration of SAP NetWeaver Systems AS Java (Application Server for Java) Monitoring

Tasks Monitoring Performance and Resource Usage.

4 Management of SAP IS-M/AMCSAP provides you with an infrastructure to help your technical support consultants and systemadministrators effectively manage all SAP components and complete all tasks related tomiddleware technology.

This infrastructure provides:

A central interface for managing administrative middleware tasks

Improved problem resolution processes for the entire solution

Standardized administration of user profiles

For more information about the underlying technology, see the Technical Operations Manual in theSAP Library under SAP NetWeaver.

4.1 Administration Tools of SoftwareComponents

SAP NetWeaver is used as a technical basis for all SAP IS-M/AMC 3.0 components. Forinformation on the relevant administration tools, see the NetWeaver 2004s Technical OperationsManual.

4.2 Starting and StoppingStart and Stop Sequences and Tools

Start and Stop Sequences and ToolsSoftware Component

Sequence Tool Detailed Description

Sales of Classified Ads

SAP IS-M/AMCtogether with SAPNetWeaver

When you startApplication Server ABAP,the J2EE engine and theapplications running onABAP and J2EE arestarted.

Technical OperationsManual for SAP NetWeaver

General AdministrationTasks Starting andStopping SAP NetWeaverABAP and Java.

J2EE Started J2EE is started on aLinux engine

For more information, seeSAP Note 1058757.


4.3 Backup and Restore

18 June 2007

4.3 Backup and RestoreYou need to back up your system landscape regularly to ensure that you can restore and recover itin the event of failure.

The backup and restore strategy for SAP IS-M/AMC consists of two parts:

Backup and restore coverage for each component

Cross-system data dependencies and handling

The backup and restore strategy for your system landscape should not only consider SAP systemsbut should also be embedded in the overall business requirements and take account of yourcompany’s entire process flow.

The backup and restore strategy must also cover disaster recovery processes, such as the loss ofa data center due to a fire. In this situation, it is essential to ensure that backup devices are not losttogether with normal data storage (separation of storage locations).

Based on the type of application data contained in a component, we have introduced acategorization scheme for system components that can be used to analyze the backuprequirements of any system component and to easily determine an appropriate backup method forthis component. The following table contains a component list for your solution and the appropriateCategories of System Components for Backup & Restore.

Component Category Application DataType

Backup Method forApplication Data

SAP IS-M/AMC XI Original Database and logbackup

File systembackup (full and/orincremental)

For more information, see the best-practices document Backup and Restore for mySAP in SAPNetunder the quick link bp-roadmap Operations Implementation Backup and Restore formySAP.

4.4 System CopyFor more information on prerequisites, procedures, and limitations for copying components of SAPSRM, see the document Homogeneous and Heterogeneous System Copy for SAP Systems Basedon SAP NetWeaver 2004s on SAP Service Marketplace atservice.sap.com/installnw2004s Installation and Upgrade Guides SAP NetWeaver

Release 2004s Installation 2 Installation SAP NetWeaver 2004s.

4 Management of SAP IS-M/AMC

4.5 Periodic Tasks

June 2007 19

4.5 Periodic Tasks4.5.1 Scheduled Periodic Tasks

4.5.1.1 SAP NetWeaver 2004sFor more information on standard background jobs and periodical tasks for SAP NetWeavercomponents, see the NetWeaver 2004s Technical Operations Manual.

4.5.1.2 SAP IS-M/AMC 3.0Standard, Housekeeping Jobs

Program Name/Task RecommendedFrequency

Detailed Description

Reorganize ad content User defined

4.5.2 Required Manual Periodic TasksNot relevant.

4.6 Logging On and Load BalancingAn application-specific tool is not used for logon and load balancing. Both the ABAP based SAP IS-M/AMC component and the SAP J2EE, use the Application Server ABAP standard mechanisms forload balancing. For more information, see the Technical Operations Manual for SAP NetWeaver.

4.7 User ManagementAll scenarios use the User Management functions from SAP NetWeaver. For more information, seethe documentation in the SAP Help Portal at help.sap.com/nw04 SAP NetWeaver 2004s SAPLibrary SAP NetWeaver Library Administrator’s Guide SAP NetWeaver Security Guide User Administration and Authentication.

For more information on SAP IS-M/AMC user profiles, you can also see the security guide for SAPIS-M/AMC.

Install IS-M/AMC UI on User’s PC

Installation of IS-M/AMC UI on the user's PC is largely automated. However, you should alsoperform the following steps to ensure that IS-M/AMC UI can be installed:

1. A Java Runtime Environment (JRE) must be installed on the user's PC to execute IS-M/AMCUI. JRE 1.4.2 from Sun is currently used. You can download and install this fromhttp://www.java.sun.com.

However, if the JRE has not been installed on the user's PC, the system attempts to install itfrom this website automatically when IS-M/AMC UI is accessed for the first time using theISM_AMC_APPLET BSP application. You should only therefore perform this installation

http://www.java.sun.com/


4.7 User Management

20 June 2007

manually if the automatic installation fails, for instance as a result of the security regulationsdefined by your company.

To ensure that program terminations do not occur as a result of insufficient memory beingavailable when users edit large ad content, you should define the following runtime parametersfor the Java Virtual Machine:

Xms256m (Initial size of allocated memory)

Xmx512m (Maximum size of allocated memory)

You can access the JVM runtime parameters in Windows under Start -> Settings -> ControlPanel -> Java Plug-In.

2. IS-M/AMC UI uses the SAP Java Connector (JCo) to access IS-M/AM and IS-M/AMC Server.The system currently uses SAP JC 2.1.7, which you can download and install fromwww.service.sap.com/connectors.

You must ensure that the librfc32.dll and sapjcorfc.dll files installed on theuser's PC are not older than SAP JCo 2.1.4, which you have downloaded. If you replacethese files with a newer version, you must close the SAP GUI first.

You must also ensure that these files have only been installed on the user's PC once in adirectory that can be accessed by the operating system. In Windows, these files areusually found in the "c:\windows\system32" directory. In Windows NT or 2000, these filesare usually found in the "c:\winnt\system32" directory.

Note: If you are using SAP GUI for Windows 6.20 / 700, you must also see SAP note 684106.

For more information about integration of IS-M/AMC UI in the SAP Media Customer InteractionCenter, see SAP note 1067317.

Create and Configure Users in IS-M/AM

Make the following settings in IS-M/AM:

1. Create the users as dialog users using the User Maintenance (SUO1) transaction. To assign aunique ID to the user, enter the user name <USER> as a value for theJHFRONTENDID_USER parameter ID on the Parameters tab page. This value must notcontain more than 10 characters. See note 737432 here.

2. Create an RFC destination for the user using the Display and Maintain RFC Destinations(SM59) transaction:

a. Enter the name of the user in the name of the RFC destination, for exampleAMC.<USER>.

b. Check that the RFC destination is a TCP/IP connection (connection type T).

c. Select the Registered Server Program indicator on the Technical Settings tab page andassign a program ID. You can also enter the user name here, for example AMC.<USER>.Observe upper and lower case here.

If more than one application server is used in your system, specify gateway options toensure that the RFC destination also points to the gateway to which IS-M/AMC UI issubject. These gateway options must match the gateway options that you recorded in theuser profile for the user.

If your system is a unicode system, select the unicode indicator on the Special Optionstab page.

3. Assign the RFC destination you created in step two to the technical system for IS-M/AMC UIand the front end ID that you specified for the JHFRONTENDID_USER parameter ID inCustomizing under Connection of Media Technical Systems -> Assign RFC Destination.

http://www.service.sap.com/connectors

5 High Availability

4.8 Printing

June 2007 21

Create and Configure Users in IS-M/AMC Server

Make the following settings in IS-M/AMC Server:

1. Access the User Maintenance (SU01) transaction to create users as dialog users. The username does not have to be identical to the user name in IS-M/AM. However, if the user namesare identical in IS-M/AM and IS-M/AMC Server, it is easier for the agent to log on.

2. Provide the user with the authorizations that are described in the Define Authorizations IMGactivity.

3. Assign the user profile, which you defined previously in the Set Up System IMG activity, to thisuser in the Assign User Profile and Program ID IMG activity. You should also assign theprogram ID, which you previously recorded for the RFC destination in IS-M/AM, to this user.

User Management Tools

User Profiles in SAPIS-M/AMC

Detailed Description

SAP_ISM_MAMC_BASIC_USER

Within these user profiles you can define:

Whether the user is allowed to create or display ad content

Which actions in IS-M/AMC UI the user is allowed to execute

Which ad content validation errors the user is allowed toconfirm

4.8 PrintingNot relevant.

5 High AvailabilityComponent Business Impact if Unavailable

SAP ERP 2005 Business-critical

IS-M/AMC Server 3.0 Business-critical: Single point of failure for all scenarios


6.1 SAP IS-M/AMC

22 June 2007

6 Software Change ManagementSoftware Change Management standardizes and automates software distribution, maintenance,and testing procedures for complex software landscapes and multiple software developmentplatforms. These functions support your project teams, development teams, and applicationsupport teams.

The goal of Software Change Management is to establish consistent, solution-wide changemanagement that allows for specific maintenance procedures, global rollouts (includinglocalizations), and open integration with third-party products.

This section provides additional information about the most important software components. Thefollowing topics are covered:

Transport and Change Management - Enables and secures the distribution of softwarechanges from the development environment to the quality assurance and productionenvironment.

Development Request and Development Release Management – Enables customer-specific maintenance procedures and open integration with third-party products.

Template Management – Enables and secures the rollout of global templates, includinglocalizations.

Quality Management and Test Management - Reduce the time, cost, and risk associatedwith software changes.

Support Packages and SAP Notes Implementation – Provide standardized softwaredistribution and maintenance procedures.

Release and Upgrade Management – Reduces the time, cost, and risk associated withupgrades.

6.1 SAP IS-M/AMC6.1.1 Transport and Change Management

SAP NetWeaver includes the Change and Transport System (CTS), which is a tool that helps youto organize development projects in the ABAP Workbench and in Customizing, and then transportthe changes between the SAP Systems in your system landscape.

For more information, see the NetWeaver 2004s Technical Operations Manual.

6.1.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 theycan use to perform the task directly.

It is an efficient method of transporting a selected number of requests into a group of transporttargets, and uses clearly defined approval steps to ensure the quality of your target systems.

7 Appendix

7.1 Categories of System Components for Backup and Restore

June 2007 23


6.1.3 Template ManagementNot relevant.

6.1.4 Quality Management and Test ManagementNot relevant.

6.1.5 Support Packages and Patch ImplementationFor information on the Support Packages available for SAP IS-M/AMC 3.0, see the ReleaseInformation Note (RIN).

Support Packages for components based on the SAP Web Application Server (ABAP) 7.00 (suchas IS-M/AMC Server 3.0) are applied using the Support Package Manager.

Updates to IS-M/AMC Applet can be uploaded to the BSP application on the SAP Web ApplicationServer.


Detailed Instructions on applying a Support Package Stack to SAP NetWeaver are given in theSupport Package Stack Guide for SAP NetWeaver 2004s.

For more information, see the documentation on SAP Service Marketplace atservice.sap.com/nw04 SAP NetWeaver 2004s – Release Specific Information Documentation Maintenance Support Package Stack Guide.

SAP Notes that require code changes for components based on the SAP Web Application Server(ABAP) 7.00 can be applied using the SAP Note Assistant.

For more information, see the documentation in the SAP Help Portal at help.sap.com/nw04SAP NetWeaver 2004s SAP Library SAP NetWeaver by Key Capability Solution Life CycleManagement by Key Capability Software Life Cycle Management Software Maintenance Note Assistant.

7 Appendix7.1 Categories of System Components for

Backup and RestoreCategories ofSystemComponents

Category Properties Suggested Methods for Backup andRestore

Examples

I Only software, no configurationor application data

No backup, new installation in caseof a recovery or

Initial software backup afterinstallation and upgrade

BDOC modeler


7.1 Categories of System Components for Backup and Restore

24 June 2007

Categories ofSystemComponents


Examples

Backup of log files

II Only software andconfiguration information, noapplication data

Backup after changes have beenapplied or

No backup, new installation andconfiguration in case of a recovery

Backup of log files

SAP Gateway

Comm. Station

SAP BusinessConnector

SAP IPC (2.0C)

III Only replicated applicationdata, replication time issufficiently small for a recovery

Data:

No data backup needed

Backup of software, configuration,log files

SAP IMS/SearchEngine

SAP IPC (2.0B)

Webserver

SAP ITS

IV Only replicated applicationdata, backup recommendedbecause replication time is toolong, data not managed by aDBMS

Data:

Application specific file systembackup or

Multiple instances


SAP IMS/SearchEngine

Webserver

V Only replicated applicationdata, backup recommendedbecause replication time is toolong, data managed by aDBMS

Data:

Database and log backup or

Multiple instances


SAP IPC (2.0B)

Catalog Server

VI Original application data,standalone system, data notmanaged by a DBMS

Data:

Application specific file systembackup


Webserver

VII Original application data,standalone system, datamanaged by a DBMS, notbased on SAP WebAS

Data:

Database and log backup


VIII Original application data,standalone system, based onSAP WebAS

Data:

Database and log backup,application log backup (such as joblogs in file system)


Standalone SAP-System

7 Appendix

7.2 Related Guides

June 2007 25

Categories ofSystemComponents


Examples

IX Original application data, dataexchange with other systems,data not managed by a DBMS

Data:

Application specific file systembackup, data consistency withother systems must be considered


X Original application data, dataexchange with other systems,data managed by a DBMS, notbased on SAP WebAS

Data:

Database and log backup, dataconsistency with other systemsmust be considered


SAP liveCache

SAP Mobile

Workbench

XI Original application data, dataexchange with other systems,based on SAP WebAS

Data:

Database and log backup,application log backup (such as joblogs in file system), dataconsistency with other systemsmust be considered


SAP ECC

SAP CRM

SAP APO

SAP BW

7.2 Related GuidesFor more information about installation and configuration, see the Master Guide.

7.3 Related InformationThe following table contains links to information relating to the Solution Operation Guide:

Content Quick Link to the SAP Service Marketplace(service.sap.com)

Master Guide, Installation Guide andUpgrade Guide

instguides

ibc

Related SAP Notes Notes

Released Platforms Platforms

Network Security securityguide

network

Technical Infrastructure Ti

SAP Solution Manager solutionmanager


7.3 Related Information

26 June 2007

Date post:	20-Dec-2015
Category:	Documents
Upload:	mandar
View:	12 times
Download:	0 times

SolOpGuide MAMC30 V12 En

Documents