Transporte GP Sap netweaver

1. How-to Guide
Beginning with SAP NetWeaver 2004s SPS06
How To…
Transport in GP
Version 2.00 – January 2006
Applicable Releases:
Beginning with SAP NetWeaver 2004s SPS06

2. © 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 PowerPointare
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 MultiWinare 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, SAP
NetWeaver, and other SAP products and services
mentioned herein as well as their respective logos are
trademarks or registered trademarks 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 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 caused by the usage of
the Code, except if such damages were caused by SAP
intentionally or grossly negligent.

3. - -1
1. Table of Contents
1. TABLE OF CONTENTS.....................................................................................................................1
2. SCENARIO ..........................................................................................................................................2
3. INTRODUCTION................................................................................................................................2
3.1 RELATED DOCUMENTS ..................................................................................................................2
4. THE STEP BY STEP SOLUTION.....................................................................................................3
4.1 CREATING A TRANSPORT PACKAGE ..............................................................................................3
4.2 FURTHER ACTIONS WITH THE TRANSPORT PACKAGE .....................................................................6
5. IMPORTING A TRANSPORT PACKAGE USING SDM..............................................................7
5.1 RELEASING IMPORTED OBJECTS..................................................................................................10
6. TRANSPORTING GP CONTENT WITH THE NWDI ................................................................12
7. APPENDIX.........................................................................................................................................16

4. - -2
2. Scenario
You have created callable objects, actions, blocks and processes in CAF-GP and would
like to deploy these objects to another machine.
3. Introduction
This How-to guide shows you how you can create a transport package, import a
transport package and release the imported objects. The idea behind this whole
transport mechanism is to create an archive (SDA file) so that you can move it to the
required system and deploy it using the Software Deployment Manager (SDM).
Note that only objects created with the GP design time tool can be transported. Objects
that are created using other tools should be transported using the relevant transport
mechanism. For example, WebDynpro componentscallable implementing GP Interface
should be transported using the SAP NetWeaver Development Infrastructure (NWDI).
4. Related documents
[1]. Administration Overview

5. - -3
5. The Step By Step Solution
All the options for transportation can be found in the Guided Procedure Administration
tab.
5.1 Creating a Transport Package
1. Click the Create Transport
Request link.
2. Give your transport package a
technical name and click “Next”.

6. - -4
3. Click Add to navigate to the object
selection menu.
4. You can now select the objects you
want to be transported. Click the
box to select multiple objects.
If you select an object that contains
further objects, the dependencies
will be detected and all the
dependent objects will be
automatically added to the transport
package.
Important: Ensure that all your
objects to be transported are in
Active state and all deprecated
objects have been updated.
5. Once you have selected all your
objects, click Add to List.

7. - -5
6. A summary of the objects in the
transport package will be displayed.
Click Next.
7. If you want to create a local
transport file, select Export to Local
file. Export to SAP System using
End Point will export the data to an
SAP System. Then you can select
Import Transport Requests later to
import your data. For this example,
Export to Local File is selected.
After selecting the type of transport,
click Export.
8. If you choose Export to Local File,
a deployable archive will be created.
You can click Download sca file to
get a copy of the file. You can now
deploy it to other servers using
SDM.
9. A copy of the archive can also be
found in the server directory:
usrsap<SID>JC<INST
NO>j2eeclusterserver0

8. - -6
5.2 Further actions with the transport package
Now you have the selected Guided Procedure components in a single .sda file in your
local file system. There are two ways of transporting it to the target server:
• Using the software Deployment Manager (SDM)
• Using the NetWeaver Development Infrastructure (NWDI)
Using the SDM is more straightforward and simple. If you do not want to edit the content
of the .sda file, use SDM for transporting.
Applications creating content would use the NWDI deployment rather than sending the
sda file to the customer.

9. - -7
6. Importing a Transport Package using SDM
1. Start SDM and click the Add button.
Note:
You will find the files to start the SDM in
the following path:
usrsap<SID>JC<INST NO>SDM.
Start your server using
“StartServer.bat”
Start the SDM using “RemoteGui.bat”
In the folowing log-in pop-up you
have to enter your password, and the
system you want to deploy to.
2. Select the .sda file you want to
import and click Choose.

10. - -8
3. The sda file is now added to the list
of files to be deployed. Click Next
twice.
4. Now, click Start to start the
deployment.

11. - -9
5. The deployment should be
successfully completed. Now click
Confirm to complete the
deployment.
6. To check if the deployment was
successful, go to the gallery. You
should see that your folder has been
created. However, there is no object
in the folder. This is because the
objects have to be released
manually by default. Check the
Appendix section to see how to
automatically release the object after
deployment.

12. - -10
6.1 Releasing Imported Objects
1. To release the imported objects,
choose Manage Imported Objects.
2. Click Add to see a list of objects that
can be released.

13. - -11
3. Navigate and select the object that
needs to be released.
4. A summary of the objects and their
dependency objects will be
displayed. All the objects in the
summary will be released. Click
Next to continue.
5. Click Release to release the objects.
A message will appear, confirming
that the objects have been released
successfully.
All the objects you selected are now
available for use.
By clicking on an object in the list,
you can edit the object's permissions
in place.

14. - -12
7. Transporting GP Content with the NWDI
1. Extract the archive file to your file
system.
It contains another archive file with
the extension .gpa, which holds the
definitions of the GP objects.
Extract the GPA file as well.
You can use an archiving program,
such as WinZip or WinRAR.
2. In the SAP NetWeaver Developer
Studio, Choose File → New →
Project.

15. - -13
3. Choose Development Component →
Development Component Project.
Choose Next.
4. Choose your configuration and
software component. In this
example, the configuration “Local
Development”, and the software
component “MyComponents” is
used.
Choose Next.

16. - -14
5. Enter the required data for the DC
name. For type, select Content →
Guided Procedures 2.0.
Choose Finish.
6. Copy the content of the GPA file that
you extracted on your file system
into the src folder of the new DC
project.
To find out where the folder is
located into the file system, select it
in the Developer Studio and open its
context menu. Then choose
Properties.
The structure on the file system will
be the following:
C:Documents and
settingsI024180.dtc
LocalDevelopment
DCssap.commyGpContent_comp
src
Where the refer is as follows:
Development Configuration that
has been selected in step 4:
LocalDevelopment
Vendor of development
Component: sap.com (s. step 5)
Name of development
component: myGpContent (s. step
5)
_compsrc

17. - -15
7. In the SAP Netweaver Developer
Studio choose your component,
open the context menu and click
“refresh”.
The src folder should contain the
content of the extracted gpa-file.
8. To build the DC, in the Package
Explorer view choose Development
Component → Build from the
context menu.
A deployable SDA file is created in
the gen folder of the project.
9. Browse to the SDA file, select it, and
choose Deploy from the context
menu. You can also go to the
Development Configurations
perspective, and deploy the DC.
The GP objects are deployed to your
system and you should be able to
find them in the gallery.
Note. Please consider that you have
to deploy to a system where the
content is no longer available to
check whether the functionality
works. If you deploy the content
within the same system you not be
able to check this.

18. - -16
8. Appendix
In the Visual Admin, <SID> Server Services caf/eu/gp/model, there is a property
devobj.after_import_processing that can be configured in such a way that the
imported object can be released automatically. By default, it is set to true and an
administrator needs to release the imported objects manually. Set the property to false
and objects will automatically be released when imported.

19. www.sap.com/netweaver