Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Applies to:
SAP NetWeaver Composition Environment (CE 7.1 and above), SAP Netweaver Development Infrastructure (NWDI), SAP NetWeaver Platform, Application Lifecycle Management. For more information, visit the Composition homepage.

Summary
This article provides step-by-step guide on How to migrate Local Developments built on Composition Environment (CE 7.1 and above platform) to a Centralized NWDI environment from Developer's Point of View, in 10 simple steps. Author: Shreyas Pandya

Company: Enteg Infotech Pvt. Ltd. Created on: 26 February 2011

Author Bio
Shreyas Pandya is a SAP Netweaver Enterprise Portal Consultant at Enteg Infotech Pvt. Ltd, India. His areas of expertise in SAP technologies include Netweaver Development Infrastructure (NWDI), WebDynpro Java, Composition Environment, and Enterprise Portal

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Table of Contents
Introduction: ........................................................................................................................................................ 3 Step 1: Making Local Development Environment Consistent ............................................................................ 3 Step 2: Importing Development Configurations from System Landscape Directory .......................................... 4 Step 3: Copying Local DCs to NWDI Track SC .................................................................................................. 5 Step 4: Modifying the DC Permissions ............................................................................................................... 6 Step 5: Resolving DC Dependencies ................................................................................................................. 7 Step 6: Making the Track Environment Consistent ............................................................................................ 8 Step 7: Adding DCs to Source Control ............................................................................................................... 9 Step 8: Check-In ............................................................................................................................................... 10 Step 9: Activate ................................................................................................................................................. 10 Step 10: Release .............................................................................................................................................. 11 Related Content ................................................................................................................................................ 12 Disclaimer and Liability Notice .......................................................................................................................... 13

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Introduction:
This article provides step-by-step guide on How to migrate Local Developments built on Composition Environment (CE 7.1 and above platform) to a Centralized NWDI environment from Developer's Point of View, in 10 simple steps. For migrating any projects to NWDI compatible environment, there are certain prerequisites that must be fulfilled as below. The project being migrated must follow the SAP's Component Model Standards. From now on the Project will be associated with a Product, composed of Software Components (SCs), which in turn are made up of Development Components (DCs) of different types. Please refer to the blog NWDI Empowered Landscape vs. Landscape without NWDI Setup for more information. Here, in this guide we assume that, Product is already defined and Software Component SC is also created with its build time dependencies declared in SLD. And now, the Track is ready with its runtime systems and SC configured inside Landscape Configurator. Please refer to the video NWDI-based Development Process for detailed overview. The Entire Process is operated from Development Infrastructure Perspective of NetWeaver Developer Studio (NWDS)

Step 1: Making Local Development Environment Consistent

Build all the DCs present in your local environment individually. All the DCs must go through a successful DC build operation before starting the migration process.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 2: Importing Development Configurations from System Landscape Directory

Configure SLD if not configured, and then import your track from System Landscape Directory (SLD),

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Before Finishing you will see all the build-time dependencies of your Track SC. After clicking on Finish, you will be asked to provide the Login Credentials of Development Infrastructure. The Track (Finished Goods CAF_dev) will now appear in your current workspace.

Step 3: Copying Local DCs to NWDI Track SC

Copy all the DCs present in your Local Environment (under MyComponents) and Paste all of them inside your Track SC (FGCAF_SC).

After Copy operation is over, you will see all the DCs inside your Track SC (FGCAF_SC).

Remember that the DCs that you have copied are still not associated in any ways with the Central Repository. We will see how to associate these DCs to a centralized repository in later steps.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 4: Modifying the DC Permissions

When you perform the copy operation as described in STEP 3, the DC permissions are also copied as it is. Here, we need to understand that, the DCs which we have copied are no more contained inside MyComponent SC of Local Developments, but instead they are now contained inside the Track SC (FGCAF_SC). So now we must make sure that, access permissions for each of the copied DC is now pointing to the Track SC (FGCAF_SC) and not to MyComponents. Inside "Permissions" tab, remove MyComponent permission if present , and replace it with track SC (FGCAF_SC) one by one for each selected DC. To remove permission use remove button, for adding new permission use Add button.

By performing this crucial operation, we announce that all our DCs are now contained inside the Track SC (FGCAF_SC).

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 5: Resolving DC Dependencies

Dependencies are the list of DCs that are required for your target DC (under development) to perform successful build operation. Each Dependency (required DC) is contained inside an SC. For Example, tc/wd/api is a standard DC, which is contained inside a standard SC named WD-RUNTIME. This DC is required for developing and building DCs of type Web Dynpro. Inside "Dependencies" tab, click on Resolve All button to resolve the DC dependencies. After the above operation is successful, all the red marks will be removed.

In the above screenshots all the dependencies that you can see were previously referred from your Local Development Environment (Local Machine), but now these dependencies will be referred from the build time dependencies that are declared in SLD for your Track SC.

(At this stage, if you get an error like "Not all the dependencies could be resolved" then, it indicates that some build-time dependencies are missing. To resolve it you need to add those build time dependencies to your track SC, update the CMS, import them into development and consolidation runtime systems of your track from CMS transport studio and re-import the track in NWDS.)

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 6: Making the Track Environment Consistent

Once the dependencies are resolved, create project structure for each DC by selecting "Sync/Create Project" option from DC context menu.

Once all the DC project structures are created, build all the DCs at a time by selecting all, or build individually. All the DCs must go through a successful DC build operation before proceeding to next step.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 7: Adding DCs to Source Control

Now, one by one add all the DCs into one or multiple activities by choosing Add to Source Control option from the DC context menu. Repeat the same procedure for all the DCs present in track.

All the DCs should now display a plus icon indicator.

After you complete this step successfully, we can say that all your DCs are now associated with the DTR-Client. If you now open the DTR perspective of your Developer Studio & check your track inside Inactive Workspace for Development, you will see the file system of your DCs. But still these changes are not incorporated in DTR-Server. If you open the DTR-Server in DTR Web interface, you will not be able to see the same file structure that is present in your DTR-Client.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Step 8: Check-In
From the open activity view "Check-In" the activities. This action implies that, you are checking-in the activity containing your source code into the inactive development workspace of your track in Design Time Repository (DTR) Server.

Here we need to understand the difference between the STEP 7 & STEP 8, as the operations described in both the steps appears to be somewhat analogous. But wait; here is the difference, After STEP 7, the DCs were just associated with the DTR-Client temporarily in the form of Open Activities. If you Delete or Revert the Activities that were created as a result of Add to Source Control Operation, then it will also remove DC file structure that was created in Inactive Development Workspace of your track from Client DTR. After STEP 8, the DCs will be incorporated in DTR-Server permanently in the form of Closed Activities. And will be available to other Developers too.

Step 9: Activate
From the Activation View, "Activate" the activities. Activating the Checked-In activity implies that, on successful activation your source code will be incorporated in the Active Development Workspace of Design Time Repository (DTR) Server and your latest changes will be deployed on J2EE engine from the ID that is maintained as a deployment User in the Development Runtime system of your Track.

From the Activation Requests View, check the status of the activities that were activated from Activation View by clicking on refresh button. A unique Request ID is assigned to each activation request. Activation request status should be in running state initially (A Man Running indicator) and after successful activation; it will show the green success indicator.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Its also very important not to forget that after a successful activation process, a compiled (built) form of your source code is also incorporated into CBS build space of your track.

Step 10: Release

From the Transport View, click on the refresh button and Release the activities present under the waiting yellow flag.

Releasing the activated activities implies that these activities will now be available in the import queue of the Consolidation runtime system of your track. Developer's Job gets over when; activities are released from the Developer studio. Transport Manager takes care of the rest of the Transport Process via CMS Transport Studio. Import into consolidation step is followed by the assembly step, where all the changes are incorporated into a single Software Component Archive (SCA) which is later imported or transported to Quality Server for testing.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Related Content
NWDI-based Development Process NWDI Empowered Landscape vs. Landscape without NWDI Setup SAP NETWEAVER DEVELOPMENT INFRASTRUCTURE Best Practices for NWDI: Track design for ongoing development For more information, visit the Composition homepage.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

Migrating Local Developments to a Centralized NWDI Environment (Developers Viewpoint)

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 13