Show TOC

Procedure documentationSetting Up Tracks Using the Configuration Template Locate this document in the navigation structure

 

During development, you can decide that you want your track to be reserved for concrete types of development. For example, if you know that your application is used only for pure Java development, you can create a track that supports only Java development. Then you can exclude all the other standard software components (SCs) provided by default in a standard track. This allows you to have a simpler development landscape. You do this track setup inside the SAP NetWeaver Administrator’s Configuration Wizard.

Setting Up a Track for Composition Development in SAP NetWeaver 7.0 System

Instead of using a track from your SAP NetWeaver 7.1 CE development infrastructure, you can connect your SAP NetWeaver CE to an existing installation of SAP NetWeaver 7.0 with its own SAP NetWeaver Development Infrastructure (NWDI) and use this already set up infrastructure. The configuration template allows you to connect to an existing SAP NetWeaver 7.0 system, and directly configures the track in the Change Management Service (CMS) for the type of development you want. The available track configurations in this case are marked with <type of development> 7.0in the wizard (for example CAF Application for 7.0).

Prerequisites

General Prerequisites

  1. You must have permissions in the Change Management Service (CMS) of the SAP NetWeaver Development Infrastructure (NWDI) to create and maintain tracks.

  2. You have a valid location that contain the required Software Component Archive (SCA) files for your desired type of development.

  3. You work in the SAP NetWeaver Administrator.

Prerequisites for Setting Up a Track for Composition Development in SAP NetWeaver 7.0 System

You have to:

  • SAP NetWeaver 7.0 you plan to use must have minimum SP level SP13. SAP NetWeaver Composition Environment requires JDK 1.5 or higher version while usage type NWDI of SAP NetWeaver 7.0 requires JDK 1.4. Make sure you have both JDK versions installed in your system.

  • Update the CIM in the SLD so that current versions of the dependent software component (SC) definitions are available. The CR content of the SLD of the SAP NetWeaver 7.0 must be up-to-date.

    Note that the CR Content is independent from the SLD release. Therefore, you must always import the latest CR Content into each SLD. For more information about how to update the CR content, see SAP Note 669669.

  • Create a product and SC meant to be developed and define the SC dependencies within the SLD.

  • Enable the Component Build Service (CBS) to use a Java 5 SDK to compile the Java source files.

  • Create a track for CE development within the Change Management Service (CMS).

  • Configure the track to trigger CBS to use the Java 5 SDK (in the tracks XML configuration file).

Procedure

  1. Log on to the SAP NetWeaver Administrator. Open   Configuration Management   Scenarios   tab page and choose Configuration Wizard.

  2. Under the Configuration Tasks list, select the Change Management Service (CMS): Create an Application Skeleton task.

  3. Choose Start and follow the steps of the wizard.

  4. In the Software Component step, specify a concrete type of development that you want to be performed inside the track. You can choose to create tracks for J2EE, Web Dynpro, Portal, CAF, Composite, Business Process Management applications, and other types of development.

  5. Set the Enhancement Package number.

    To reflect the Enhancement Package strategy of SAP in the configuration of track templates it was necessary to introduce an additional input parameter. During the configuration of a software component you need to specify certain required relations for build time so that the central build environment can do its work. The central build environment (CBS) is depending on the release of the build archives that are imported into the build environment. Therefore it is necessary to add this release information to the required software components of a track. Since the release number is derived from the Enhancement Package of the major release, the input in the Enhancement Package field adds this variable information. Thus leaving the default 0 in the enhancement package field will result in a required software component release 7.10, while an entry of 1 will result in release 7.11.

  6. Complete the wizard.

Note Note

For more information about the dependant SCs used for each type of development, see SAP Note1080927 and 1463541.

End of the note.