Ects Charm Sp12

Configuration andOperation Guide forEnhanced Changeand Transport System(One Transport Order)in Change RequestManagementVersion 1.00 – July 2007

Applicable Releases:SAP Solution Manager 4.0

© Copyright 2006 SAP AG. All rights reserved.

No part of this publication may be reproducedor transmitted in any form or for any purposewithout the express permission of SAP AG. Theinformation contained herein may be changedwithout prior notice.

Some software products marketed by SAP AGand its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft, Windows, Outlook, and PowerPointare registered trademarks of MicrosoftCorporation.

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 aretrademarks or registered trademarks of IBMCorporation in the United States and/or othercountries.

Oracle is a registered trademark of OracleCorporation.

UNIX, X/Open, OSF/1, and Motif are registeredtrademarks of the Open Group.

Citrix, ICA, Program Neighborhood,MetaFrame, WinFrame, VideoFrame, andMultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarksor registered trademarks of W3C®, World WideWeb Consortium, Massachusetts Institute ofTechnology.

Java is a registered trademark of SunMicrosystems, Inc.

JavaScript is a registered trademark of SunMicrosystems, Inc., used under license fortechnology invented and implemented byNetscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp,and other SAP products and servicesmentioned herein as well as their respectivelogos are trademarks or registered trademarks

contained in this document serves informationalpurposes only. National product specificationsmay vary.

These materials are subject to change withoutnotice. These materials are provided by SAPAG and its affiliated companies ("SAP Group")for informational purposesonly, without representation or warranty of anykind, and SAP Group shall not be liable forerrors or omissions with respect to thematerials. The only warranties for SAPGroup products and services are those that areset forth in the express warranty statementsaccompanying such products and services, ifany. Nothing herein should be construed asconstituting an additional warranty.

These materials are provided “as is” without awarranty of any kind, either express or implied,including but not limited to, the impliedwarranties of merchantability, fitness for aparticular purpose, or non-infringement.SAP shall not be liable for damages of any kindincluding without limitation direct, special,indirect, or consequential damages that mayresult from the use of these materials.SAP does not warrant the accuracy orcompleteness of the information, text, graphics,links or other items contained within thesematerials. SAP has no control over theinformation that you may access through theuse of hot links contained in these materials anddoes not endorse your use of third party webpages nor provide any warranty whatsoeverrelating to third party web pages.SAP NetWeaver “How-to” Guides are intendedto simplify the product implementation. Whilespecific product features and procedurestypically are explained in a practical businesscontext, it is not implied that those features andprocedures are the only approach in solving aspecific business problem using SAPNetWeaver. Should you wish to receiveadditional information, clarification or support,please refer to SAP Consulting.Any software coding and/or code lines / strings(“Code”) included in this documentation are onlyexamples and are not intended to be used in aproductive system environment. The Code isonly intended better explain and visualize thesyntax and phrasing rules of certain coding.SAP does not warrant the correctness andcompleteness of the Code given herein, andSAP shall not be liable for errors or damages

of SAP AG in Germany and in several othercountries all over the world. All other productand service names mentioned are thetrademarks of their respective companies. Data

caused by the usage of the Code, except if suchdamages were caused by SAP intentionally orgrossly negligent.

1 Introduction...............................................................................................52 Scenarios..................................................................................................53 Operation..................................................................................................5

3.1 Requirements ....................................................................................53.2 Definition of Systems in SMSY ..........................................................5

3.2.1 Definition of Java Systems in SMSY ..........................................53.2.2 Definition of ABAP Systems in SMSY ........................................8

3.3 Definition of Logical Components in SMSY .....................................103.3.1 Definition of Logical Component for ABAP System ..................103.3.2 Definition of Logical Component for Java Systems ..................13

3.4 Definition of an SMI Project and a Task List ....................................14

One Transport Order Configuration and Operation Guide 5

1 IntroductionThis guide explains step by step how to set up and configure the enhanced Change andTransport System (enhanced CTS) scenario within the Change Request Management atcustomer site.

Note: This document refers to enhanced Change and Transport System, but it may alsobe refered to as One Transport Order (OTO).

2 ScenariosThis guide covers the integration scenarios for SAP NetWeaver Portal (EP) and SAPExchange Infrastructure (XI).

3 Operation

3.1 Requirements

The enhanced CTS is available within Change Request Management as of SAP SolutionManager 4.0, SPS12.

To use enhanced CTS in the Change Request Management environment, you mustperform some configuration tasks in the SAP Solution Manager.

Note: The transport routes in the transport management system (TMS) must have clientindependent definitions since there are no clients in non-ABAP systems.

3.2 Definition of Systems in SMSY

First you have to define Java and ABAP systems. The systems definitions can beautomatically imported in transaction SMSY.

3.2.1 Definition of Java Systems in SMSYWarning: In systems prior to SAP Solution Manager 4.0 SPS13, the enhanced CTS doesnot support double-stack systems (systems with an ABAP stack and a Java stack)

Hint: There is a slight difference whether you have an SAP NetWeaver Portal or an SAPExchange Infrastructure environment. The differences are marked bold and italic in thefollowing.

You can either automatically retrieve some data from the System Landscape Directory(SLD). This is called a landscape fetch. If you do not use the SLD landscape fetch, youhave to define your Java system component manually.

To use the landscape fetch, call transaction SMSY, choose Goto -> Setup SystemLandscape Maintenance. Choose System and Landscape Directory (SLD) and make


entries for your Java system in the fields Host, Port, and Planned Data Transfer. TheSLD defines a system component of type Java for your Java system. Depending on yourSupport Package level, it may also define a system wrapping for this system component.

Call transaction SMSY, chooseLandscape Components -> SystemComponents -> Java-System

If you use the SLD landscape fetch,select your Java system component,otherwise create it this way: MarkSystem Components and use the rightmouse and click Create New SystemComponent.

In the following dialog box, fill in thevalues:

System Component: <name of yourJava system component>

Type: From the value help, choose JavaSystem

Installation Number: <any number>.

Save your entries.In the following screen, fill in the valueson the tab Header Data. The followingfields are important:

Description: <a descriptive text,for example the system ID>

Dispatcher: <message server ofyour Java system>

Port Number: <port number ofyour system; depends on whatURL you want to be led towhen logon on to your Javasystem>


On the tab strip Instances, fill in thevalues:

Instance: J2EESERVER_<servername>_<instance key>,for example,J2EESERVER_server1_01

Server Role: J2EE Server

Server: <your server>

Save your entries.

Depending on your Support Packagelevel, the SLD landscape fetch mayhave defined a system with this systemcomponent. If not, create it here;otherwise verify that it was defined.

The assignment of the system to aproduct may not be unique. Searchingthe system with the button Other Object,will get you a dialog to choose theproduct definition. Select SAPNETWEAVER.

If you need to define the system withyour system component:

In the transaction SMSY, chooseLandscape Components -> System.Click the right mouse button, chooseCreate New System

A dialog box appears. Fill in the values:

System: <name of Java system>

Product: From the value help, chooseSAP NETWEAVER

Product Version: From the value help,choose SAP NETWEAVER 2004S

Installation Number: <any number>.

Save your entries.


On the following screen, in the columnMain Instance remove the flag Relevantfrom the entry for Application ServerABAP

Enterprise Portal:Set the flag Relevant in the lineEnterprise Portal.

Exchange Infrastructure:For the line Application Server Java,make entries in the following columns:

Relevant: Set the flag System Component Assignment:

Set the flagSystem Component: <Javasystem ID>Type: Java System

Save your entries.

Enterprise Portal:

Exchange Infrastructure:

Proceed with all your Java Systems in the same way.

3.2.2 Definition of ABAP Systems in SMSY

If it is not already performed automatically by the system landscape fetch, define yourABAP system, in which the transport requests will be created.


Call transaction SMSY, chooseLandscape Components-> System

Click the right mouse button, chooseCreate New System


System: <name of ABAP system>



Save your entries.

On the following screen, in the columnMain Instance, verify that the flagRelevant is set for line ApplicationServer ABAP

Ensure that no other Main Instanceswith an assignment to a non-ABAPsystem type are marked as Relevant.

Save your entries.

Next, import the systems data defined in the TMS domain controller into the SAPSolution Manager.


Let the SMSY gather the data from yoursystems automatically.

Find the ABAP system, in which thetransport requests will be created. Intransaction SMSY, choose:-> Landscape Components-> System

Double-click the system and choose thetab strip Header Data.

Fill in the values:Data Source: Manual (AutomaticRefresh)

Choose tab strip Selection of MainInstance

Double-click on Main InstanceApplication Server ABAP and go into thechange mode

Choose button Read System DataRemote

3.3 Definition of Logical Components in SMSY

Now you have to define logical components for setting up your system landscape. Youwill need two logical components:

One logical component for the ABAP system One logical component for the JAVA system.

3.3.1 Definition of Logical Component for ABAP System


To define a logical component for theABAP system in which the transportrequests will be created, call transactionSMSY, choose System Groups andLogical Components -> LogicalComponents

Click the right mouse button, chooseCreate New Logical Component

A dialog box appears. Fill in the valuesas follows:

Logical Component: <descriptivetext>

Product: From the value help, chooseSAP NETWEAVER (product of yourABAP system in which the transportrequests will be created)

Product Version: From the value help,choose SAP NETWAEVER 2004S(product version of your ABAP system inwhich the transport requests will becreated)

Main Instance: From the value help,choose Application Server ABAP(ABAP main instance of your ABAPsystem in which the transport requestswill be created)


To ensure that the assignment of yoursystem roles to the role types is correct,choose the button System Roles.

A dialog box appears. Verify the settingsas follows:

Role C assigned to the Type ofRole Source Systems

Role T assigned to the Type ofRole Target System.

Role P assigned to the Type ofRole Production Systems

If not, change the assignmentaccordingly.

After leaving the dialog box, save thenew logical component.

In the following screen, fill in the valueson the tab strip Current SystemAssignments:

Development System: <ABAP systemin which the transportrequests will be created>

Save your entries.


3.3.2 Definition of Logical Component for Java Systems

To define a logical component for yourJava systems, call transaction SMSY,choose System Groups and LogicalComponents -> Logical Components

Click the right mouse button, chooseCreate New Logical Component.


Logical Component: <name as youlike>



Enterprise Portal:Main Instance: From the valuehelp, choose Enterprise Portal

Exchange Infrastructure:Main Instance: From the valuehelp, choose Application ServerJAVA

Enterprise Portal:

Exchange Infrastructure:

In the following screen, fill in the valueson the tab strip Current SystemAssignments:

Quality Assurance System: <Javasystem ID>

Production System: <Java systemID>

Save your entries.


3.4 Definition of an SMI Project and a Task ListTo use Change Request Management, you need to define a project in the SolutionManager for Implementation (SMI project) in transaction SOLAR_PROJECT_ADMIN.Defining an SMI project requires the systems definition and the creation of logicalcomponents in transaction SMSY.

As the next step, define an SMI project with your new logical components.Call transactionSOLAR_PROJECT_ADMIN, chooseNew Project.


Project: <descriptive text>

Type: From the value help, chooseMaintenance Project

In the following screen, fill in the valueson the tab strip General Data:

Title: <descriptive text>

Project Language: <descriptivetext>


Choose tab strip System Landscapeand then tab strip Logical Components.To fill in both your new logicalcomponents, use the value help.

Save your entries.

Choose OK on the following dialog boxEnhancements for Docu.

Choose tab strip Change Requests.

Select Activate Change RequestManagement.

Confirm the following dialog box withYes.

Choose Create Task List.


Name in Maintenance Cycle: <as youlike>.


In the following dialog box, choose TaskList

In the next screen you see thegenerated task list.

Choose Status.

In the next dialog box, select Activate.

Choose Continue.


You return to the task list.

Mark the line Project Track <SMIproject> (Source Systen <ABAPsystem>) and click the right mousebutton. Choose Lock/UnlockGroup/Subsequent Groups.

Now you can use the Change Request Management within/with help of this task list.

Ects Charm Sp12

Documents

Transcript of Ects Charm Sp12