Configuration and Operation Guide for Enhanced Change and Transport System (One Transport Order) in Change Request

Management
Version 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 reproduced or transmitted in any form or for any purpose without the express permission of 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 software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks 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 IBM Corporation 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 registered trademarks 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 implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks

contained in this document serves informational purposes only. National product specifications may 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 not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages

of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data

caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

1 2 3

Introduction ...............................................................................................5 Scenarios..................................................................................................5 Operation ..................................................................................................5 3.1 Requirements ....................................................................................5 3.2 Definition of Systems in SMSY ..........................................................5 3.2.1 Definition of Java Systems in SMSY ..........................................5 3.2.2 Definition of ABAP Systems in SMSY ........................................8 3.3 Definition of Logical Components in SMSY .....................................10 3.3.1 Definition of Logical Component for ABAP System ..................10 3.3.2 Definition of Logical Component for Java Systems ..................13 3.4 Definition of an SMI Project and a Task List ....................................14

1 Introduction
This guide explains step by step how to set up and configure the enhanced Change and Transport System (enhanced CTS) scenario within the Change Request Management at customer site. Note: This document refers to enhanced Change and Transport System, but it may also be refered to as One Transport Order (OTO).

2 Scenarios
This guide covers the integration scenarios for SAP NetWeaver Portal (EP) and SAP Exchange Infrastructure (XI).

3 Operation
3.1 Requirements

The enhanced CTS is available within Change Request Management as of SAP Solution Manager 4.0, SPS12. To use enhanced CTS in the Change Request Management environment, you must perform some configuration tasks in the SAP Solution Manager. Note: The transport routes in the transport management system (TMS) must have client independent 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 be automatically imported in transaction SMSY.
3.2.1 Definition of Java Systems in SMSY

Warning: In systems prior to SAP Solution Manager 4.0 SPS13, the enhanced CTS does not 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 SAP Exchange Infrastructure environment. The differences are marked bold and italic in the following. 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, you have to define your Java system component manually. To use the landscape fetch, call transaction SMSY, choose Goto -> Setup System Landscape Maintenance. Choose System and Landscape Directory (SLD) and make

One Transport Order Configuration and Operation Guide

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

Call transaction SMSY, choose Landscape Components -> System Components -> Java-System If you use the SLD landscape fetch, select your Java system component, otherwise create it this way: Mark System Components and use the right mouse and click Create New System Component.

In the following dialog box, fill in the values: System Component: <name of your Java system component> Type: From the value help, choose Java System Installation Number: <any number>. Save your entries. In the following screen, fill in the values on the tab Header Data. The following fields are important: Description: <a descriptive text, for example the system ID> Dispatcher: <message server of your Java system> Port Number: <port number of your system; depends on what URL you want to be led to when logon on to your Java system>

One Transport Order Configuration and Operation Guide

On the tab strip Instances, fill in the values: Instance: J2EESERVER_<server name>_<instance key>, for example, J2EESERVER_server1_01 Server Role: J2EE Server Server: <your server> Save your entries.

Depending on your Support Package level, the SLD landscape fetch may have defined a system with this system component. If not, create it here; otherwise verify that it was defined. The assignment of the system to a product may not be unique. Searching the system with the button Other Object, will get you a dialog to choose the product definition. Select SAP NETWEAVER. If you need to define the system with your system component: In the transaction SMSY, choose Landscape Components -> System. Click the right mouse button, choose Create New System A dialog box appears. Fill in the values: System: <name of Java system> Product: From the value help, choose SAP NETWEAVER Product Version: From the value help, choose SAP NETWEAVER 2004S Installation Number: <any number>. Save your entries.

One Transport Order Configuration and Operation Guide

On the following screen, in the column Main Instance remove the flag Relevant from the entry for Application Server ABAP Enterprise Portal: Set the flag Relevant in the line Enterprise Portal. Exchange Infrastructure: For the line Application Server Java, make entries in the following columns: Relevant: Set the flag System Component Assignment: Set the flag System Component: <Java system ID> Type: Java System

Enterprise Portal:

Save your entries.

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 your ABAP system, in which the transport requests will be created.

One Transport Order Configuration and Operation Guide

Call transaction SMSY, choose Landscape Components-> System Click the right mouse button, choose Create New System

A dialog box appears. Fill in the values: System: <name of ABAP system> Product: From the value help, choose SAP NETWEAVER Product Version: From the value help, choose SAP NETWEAVER 2004S Save your entries.

On the following screen, in the column Main Instance, verify that the flag Relevant is set for line Application Server ABAP Ensure that no other Main Instances with an assignment to a non-ABAP system type are marked as Relevant. Save your entries.

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

One Transport Order Configuration and Operation Guide

Let the SMSY gather the data from your systems automatically. Find the ABAP system, in which the transport requests will be created. In transaction SMSY, choose: -> Landscape Components -> System Double-click the system and choose the tab strip Header Data. Fill in the values: Data Source: Manual (Automatic Refresh)

Choose tab strip Selection of Main Instance Double-click on Main Instance Application Server ABAP and go into the change mode Choose button Read System Data Remote

3.3

Definition of Logical Components in SMSY

Now you have to define logical components for setting up your system landscape. You will 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

One Transport Order Configuration and Operation Guide

10

To define a logical component for the ABAP system in which the transport requests will be created, call transaction SMSY, choose System Groups and Logical Components -> Logical Components Click the right mouse button, choose Create New Logical Component

A dialog box appears. Fill in the values as follows: Logical Component: <descriptive text> Product: From the value help, choose SAP NETWEAVER (product of your ABAP system in which the transport requests will be created) Product Version: From the value help, choose SAP NETWAEVER 2004S (product version of your ABAP system in which the transport requests will be created) Main Instance: From the value help, choose Application Server ABAP (ABAP main instance of your ABAP system in which the transport requests will be created)

One Transport Order Configuration and Operation Guide

11

To ensure that the assignment of your system roles to the role types is correct, choose the button System Roles. A dialog box appears. Verify the settings as follows: Role C assigned to the Type of Role Source Systems Role T assigned to the Type of Role Target System. Role P assigned to the Type of Role Production Systems If not, change the assignment accordingly. After leaving the dialog box, save the new logical component. In the following screen, fill in the values on the tab strip Current System Assignments: Development System: <ABAP system in which the transport requests will be created> Save your entries.

One Transport Order Configuration and Operation Guide

12

3.3.2

Definition of Logical Component for Java Systems

To define a logical component for your Java systems, call transaction SMSY, choose System Groups and Logical Components -> Logical Components Click the right mouse button, choose Create New Logical Component. A dialog box appears. Fill in the values as follows: Logical Component: <name as you like> Product: From the value help, choose SAP NETWEAVER Product Version: From the value help, choose SAP NETWEAVER 2004S

Enterprise Portal:

Exchange Infrastructure:

Enterprise Portal:
Main Instance: From the value help, choose Enterprise Portal

Exchange Infrastructure:
Main Instance: From the value help, choose Application Server JAVA In the following screen, fill in the values on the tab strip Current System Assignments: Quality Assurance System: <Java system ID> Production System: <Java system ID> Save your entries.

One Transport Order Configuration and Operation Guide

13

3.4

Definition of an SMI Project and a Task List

To use Change Request Management, you need to define a project in the Solution Manager for Implementation (SMI project) in transaction SOLAR_PROJECT_ADMIN. Defining an SMI project requires the systems definition and the creation of logical components in transaction SMSY.

As the next step, define an SMI project with your new logical components. Call transaction SOLAR_PROJECT_ADMIN, choose New Project.

A dialog box appears. Fill in the values as follows: Project: <descriptive text> Type: From the value help, choose Maintenance Project

In the following screen, fill in the values on the tab strip General Data: Title: <descriptive text> Project Language: <descriptive text>

One Transport Order Configuration and Operation Guide

14

Choose tab strip System Landscape and then tab strip Logical Components. To fill in both your new logical components, use the value help. Save your entries. Choose OK on the following dialog box Enhancements for Docu.

Choose tab strip Change Requests. Select Activate Change Request Management. Confirm the following dialog box with Yes. Choose Create Task List.

A dialog box appears. Fill in the values: Name in Maintenance Cycle: <as you like>.

One Transport Order Configuration and Operation Guide

15

In the following dialog box, choose Task List

In the next screen you see the generated task list. Choose Status.

In the next dialog box, select Activate. Choose Continue.

One Transport Order Configuration and Operation Guide

16

You return to the task list. Mark the line Project Track <SMI project> (Source Systen <ABAP system>) and click the right mouse button. Choose Lock/Unlock Group/Subsequent Groups.

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

One Transport Order Configuration and Operation Guide

17