SAP ®

HORIZON

Release: 1.1

JDI Cookbook for ESS

Customers
Modification guide for ESS

History
Version Status Date
1.0 Released 2-03-2005
1.1 Released 31-07-2005
1.2 Released 23-03-2007
Storage location of this document:

© 2005 SAP AG Title: JDI Cookbook for ESS Page 1 of 16

Neurottstr. 16 Version: 1.02
D-69190 Walldorf Date: 3/22/2007
SAP ®

Contents
1 Introduction.......................................................................................... 3
1.1 Motivation: why this guide? ............................................................................. 3
1.2 External documentation................................................................................... 3
2 Overview of process............................................................................ 4
3 Initial Configuration of JDI.................................................................. 6
3.1 Pre-requisites.................................................................................................. 6
3.2 Step by step process....................................................................................... 6
3.2.1 Define a domain in CMS ................................................................................. 6
3.2.2 Create a new Track using the Landscape Configurator ................................... 6
3.2.3 Add Software Components to track................................................................. 7
3.2.4 Configure Runtime Systems in the track.......................................................... 8
3.2.5 Import Software Components into this track .................................................... 8
3.2.5.1 Download Archives.......................................................................................... 8
3.2.5.2 Check-In archives ........................................................................................... 9
3.2.5.3 Import the checked in archives into the Development system ......................... 9
3.2.5.4 Import the checked in archives into the Consolidation system....................... 10
3.2.6 Import the Development Configuration .......................................................... 10
3.2.7 Keep a copy of this SP in a new track ........................................................... 11
4 Preparing for the first Support Package.......................................... 12
4.1 Close development in current track ............................................................... 12
4.2 Create two copies of current track ................................................................. 12
4.3 Import new Support Package archives into new Tracks ................................ 13
4.3.1 Download SP archives from service marketplace.......................................... 13
4.3.2 Check-In and import archives into new Tracks .............................................. 13
4.4 Switch runtime systems from old to new track ............................................... 13
4.5 Import new Development Configuration......................................................... 13
4.6 Re-Implement modifications in new Track ..................................................... 14
4.7 Close the old track ........................................................................................ 15
5 Importing subsequent Support Packages....................................... 16

© 2007 SAP AG Title: JDI Cookbook for ESS Page 2 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

1 Introduction
Before you start, make sure you have the latest version of this document. You can find the latest
version as attachment of note 872892. Furthermore please consider the related notes of that
note.
This document describes the process of configuring the Java Development Infrastructure (JDI)
in a way that supports the modification of sources delivered by ESS.

1.1 Motivation: why this guide?

When ESS source-code delivered by SAP is modified by customers, the import of the next sup-
port package will result in conflicts (between the modified customer versions and the new SAP
versions). While JDI supports merging of source files through text-based merge tools, the
WebDynpro elements that are in conflict require model-based merge tools (which can merge
logical objects spanning multiple files). These model-based merge tools are not yet available.
Hence, JDI recommends an alternative process that will help customers avoid a situation where
un-resolvable conflicts are created after the import of a Support Package. This guide describes
this alternate process of configuring and using the JDI landscape.

1.2 External documentation

This document refers to the following official documents delivered by SAP in the help portal
( http://help.sap.com ) :

Administration manual of JDI :

o http://help.sap.com/saphelp_nw04/helpdata/en/49/e98876e9865b4e977b54
fc090df4ed/frameset.htm

© 2007 SAP AG Title: JDI Cookbook for ESS Page 3 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

2 Overview of process
The following pictures provide an overview of the process that must be followed. Initially, two
tracks are created, and the intial version of ESS ( say SPx ) is imported into both tracks, one of
which is used for making customer modifications.

When the first Support Package (SP) is applied, two new tracks are created, and the new SP is
imported into both these tracks. Using the WebDynpro diff tool, you now can compare the
states of different DCs and get an overview of the new changes contained in this SP the
changes you made to the previous SP. Using this information, you now can re-implement your
changes in one new track.

After you have applied the first SP in this manner, your landscape should look as shown below.

© 2007 SAP AG Title: JDI Cookbook for ESS Page 4 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

For the next SP (and all subsequent ones), you have to create one new track, and repeat the
process. This is depicted in the diagram below:

© 2007 SAP AG Title: JDI Cookbook for ESS Page 5 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

3 Initial Configuration of JDI

This chapter describes how to configure the JDI in order to start modifying the ESS software
components. The steps in this chapter are relevant immediately after an installation (the next
chapter describes the steps needed to handle a Support Package upgrade).
For the purpose of illustration, this chapter assumes you are importing SP10.

3.1 Pre-requisites
This chapter assumes that you have met the following pre-requisites:
JDI has been installed
An “Admin User” which has access to all the JDI servers (DTR, CBS, CMS) has
been created and has been assigned necessary privileges (See Administration
manual in help portal for details).
The System Landscape Directory (SLD) has the new content (of the Software Com-
ponents delivered with this release).

3.2 Step by step process

3.2.1 Define a domain in CMS

Create a domain in CMS, as described in the help portal document at the following location:
http://help.sap.com/saphelp_nw04/helpdata/en/b9/086b4066d9bf49e10000000a1550b0/frames
et.htm

3.2.2 Create a new Track using the Landscape Configurator

On the “Track Data” tab of the Landscape Configurator, enter the general data as shown below:

© 2007 SAP AG Title: JDI Cookbook for ESS Page 6 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

Substitute the URLs with the appropriate ones from your landscape.
In the following sections of this document, this track will be referred to as “SP10Mod” (since this
will contain your modifications).

3.2.3 Add Software Components to track

On the same “Track Data” tab, add the following Software Components
SAP_ESS
SAP_MSS
An example is shown below:

After this step, the bottom half of this tab will look as shown below:

© 2007 SAP AG Title: JDI Cookbook for ESS Page 7 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

As shown, the following “Required Software Components” are automatically populated:

SAPPCUI_GP
SAP_JTECHS
SAP-JEE
SAP_BUILDT

Save your changes by clicking on the “Save” button on this tab.

3.2.4 Configure Runtime Systems in the track

Configure your runtime systems as described in the following topic in the help portal:
http://help.sap.com/saphelp_nw04/helpdata/en/35/1cd66947184aa8915ca1831c59b6c1/content
.htm

3.2.5 Import Software Components into this track

3.2.5.1 Download Archives

The Software Component archives ( .sca files ) must be downloaded from the Service Market-
place ( http://service.sap.com/patches ) and placed into the “inbox” folder of the CMS. (The
“inbox” folder can be found under the following path: “<CMS Transport Direc-
tory>\CMS\inbox”, where the <CMS Transport Directory> is specified in the “Domain Data” tab
of the CMS Landscape Configurator).

© 2007 SAP AG Title: JDI Cookbook for ESS Page 8 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

The following .sca files must be placed into the CMS inbox folder:

o SAP_JTECHS.sca
o SAP_BUILDT.sca
o SAP-JEE.sca
o SAPPCUI_GP.sca
o SAP_ESS.sca
o SAP_MSS.sca
( Note: The names of .sca files could be different – they may include version
numbers, vendor name, etc )

3.2.5.2 Check-In archives

In the “Check-In” tab of the CMS Transport Studio CMS perform a “Check-In” : select each of
the above archives and click on the “Check-In” button.

3.2.5.3 Import the checked in archives into the Development system

In the “Development” tab, select the checked-in components and click the “Import” button.

© 2007 SAP AG Title: JDI Cookbook for ESS Page 9 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

This import will run for several hours (if all the components are selected together). After the
import the “state” (field on the extreme right in the picture above) will be shown as “Import Fin-
ished”

3.2.5.4 Import the checked in archives into the Consolidation system

Repeat the above step in the “Consolidation” tab.

3.2.6 Import the Development Configuration

Now that the servers in the landscape have been configured, development can begin. The first
step on the client side (using the NetWeaver Developer Studio) is to import the Development
Configuration which corresponds to the “Development” system of this track that has been cre-
ated.
An example is shown below:

Modifications to the ESS Development Components (in either SAP_ESS or SAP_MSS) can now
proceed under this Development Configuration.

© 2007 SAP AG Title: JDI Cookbook for ESS Page 10 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

3.2.7 Keep a copy of this SP in a new track

In parallel to your development in the track created in the above steps, you must create a new
track and import the same SCAs into that track. This new track can be created as a copy of the
first track:
In the CMS Landscape Configurator, select your current track and choose the “Save as…” but-
ton on the ‘Track Data’ tab. This will bring up the following popup:

Give a new name (preferably denoting the Support Package number) and save the copied track
definition. Note that this copy only copies the track definition, and not its contents. Hence, you
will now have to import the same set of SCAs into this track.
Although this track will only be used when the next SP is imported, it is recommended to be
created earlier, due to the long duration of the import process.
At this point, your landscape should look as follows:

The track created in this step will be referred in this document as the “SP10” track.

© 2007 SAP AG Title: JDI Cookbook for ESS Page 11 of 16

Version: 1.2
Date: 3/22/2007
SAP ®
HORIZON

4 Preparing for the first Support Package

This chapter describes the steps necessary (from the landscape and infrastructure point of
view) to move to a new Support Package for ESS components delivered by SAP. For the pur-
pose of illustration, the new SP is denoted as “SP11”.

4.1 Close development in current track

Before a new Support Package can be imported, it is important to close all development in the
current track. This involves the following steps:
Using NetWeaver Developer Studio,
o Check-in all open activities, and activate them.
o Release all unreleased activities (This will queue them for import into the Con-
solidation system)
From the CMS Transport Studio, import the released activities into the Consolidation
system
o The released activities will appear in the Import Queue on the Consolidation tab
of the CMS Transport Studio.

4.2 Create two copies of current track

Create two copies of the track you are using for modification. The procedure to copy a track
definition is described in section 3.2.7
Name one of them “SP11” (this will be used only for comparison) and the other “SP11Mod” (this
will contain your modifications). The names can be suitably adjusted based on the SP you are
importing.
The landscape after this step should look as shown below (note the two new tracks):

© 2005 SAP AG Title: JDI Cookbook for ESS Page 12 of 16

Neurottstr. 16 Version: 1.02
D-69190 Walldorf Date: 3/22/2007
SAP ®

4.3 Import new Support Package archives into new Tracks

4.3.1 Download SP archives from service marketplace

As explained in section 3.2.5.1, download the .sca files released for the new Support Package
and place it into the CMS inbox directory.

4.3.2 Check-In and import archives into new Tracks

In the new Tracks, perform the Check-In and Import steps as described in sections 3.2.5.2 ,
3.2.5.3 and 3.2.5.4

4.4 Switch runtime systems from old to new track

The runtime systems that were associated with the old track (“SP10Mod”, containing your modi-
fications) must now be connected to the new track (“SP11Mod”). For details on how to config-
ure runtime systems, refer to the following section in the help portal:
http://help.sap.com/saphelp_nw04/helpdata/en/35/1cd66947184aa8915ca1831c59b6c1/content
.htm

4.5 Import new Development Configuration

So far, the only development configuration imported was the one for the track containing the
original modifications (“SP10Mod”). Now, for the purpose of comparison, we need two addi-
tional development configurations. This can be seen from the diagram below which depicts the
three tracks (or states) that need to be compared:

© 2007 SAP AG Title: JDI Cookbook for ESS Page 13 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

Further, you need an additional development configuration to re-implement you changes in the
new SP.
Thus, you need to import development configurations corresponding to the “SP10”, “SP11” and
“SP11Mod” tracks.

4.6 Re-Implement modifications in new Track

The “SP11Mod” track, which now contains the latest sources from SAP (corresponding to the
imported Support Package), must be used as a base for re-implementing customer modifica-
tions made in the previous track (“SP10Mod”).
This following tools offer help in this re-implementation task:

Meta-Data Comparison tool for WebDynpro projects

Using this tool you can compare two WebDynpro projects and examine the differences
in the different logical entities (like Applications, Components, Models etc).
To examine the differences between a DC modified by you and the same DC delivered
by SAP, the steps given below can be followed:
o In the ‘Inactive DCs’ view of the Development Configurations perspective, se-
lect your DC in the configuration corresponding to the “SP10Mod” track, and
create a project for this DC.
o Next select the same DC in the configuration corresponding to the “SP10” track,
and create a project for this DC.
o Shift to the WebDynpro Perspective, and open the ‘Navigator’ view. There you
will see two projects you just created.
o Select both projects and choose “Compare Metadata” from the context menu.
This will open a dialog box that displays the differences between the two DCs.
For more details about this tool, refer to the following documents on the SAP
Help Portal :
http://help.sap.com/saphelp_nw04/helpdata/en/c4/29104
11db1d349e10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/6e/0e184
188b4f16fe10000000a1550b0/frameset.htm

Repeat the above steps to examine the changes delivered by SAP in the new support
package by performing a “compare” operation between DCs in “SP10” and “SP11”
tracks.
These two sets of comparisons will give you an overview of which modifications made
by you (in “SP10Mod” ) are still relevant in the new SP (For instance, a change made
by you to the SP10 state may have become part of the standard in SP11, and hence it
need not be a part of the re-implementation steps.)

© 2007 SAP AG Title: JDI Cookbook for ESS Page 14 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

Copy & Paste functionality in WebDynpro

A number of WebDynpro elements can be copied and pasted from one DC to another.
So if your modifications include a new Application, Component or a Data-Type, you can
copy it from your DC (from the development configuration corresponding to the old
track) and paste it on to the new DC (in the development configuration corresponding to
the new track).

4.7 Close the old track

After all the re-implementation has been completed and your tests on the runtime systems con-
nected to the new track have been successful, you can close the old track (“SP10Mod”) by fol-
lowing the guidelines given below:
Reset permissions such that your developers do not have edit permissions on the DTR
workspaces of the old track. This will ensure that no new modification can be attempted
in the old track.
In the NetWeaver Developer Studio, remove the Development Configuration that corre-
sponds to the old track.

At this point, your landscape should like this:

© 2007 SAP AG Title: JDI Cookbook for ESS Page 15 of 16

Version: 1.2
Date: 3/22/2007
SAP ®

5 Importing subsequent Support Packages

Importing subsequent SPs can be done using a process similar to the one described in the pre-
vious chapter. The only difference is that instead of creating two new tracks (as described in
section 4.2 ), you only need one new track, as depicted in the landscape diagram below:

Thus, you can re-use one of the two older tracks containing the earlier SP to import the latest
SP, as shown above.

© 2007 SAP AG Title: JDI Cookbook for ESS Page 16 of 16

Version: 1.2
Date: 3/22/2007