Creating Development Configurations in the Configuration Wizard 

Use

You create a development configuration to develop a state of a software component (SC). You need this procedure only in scenario 2, because in the scenarios 2+ and 3, the development configurations are created in the Change Management Service.

This service should be used only by a user at a central position, such as a quality manager or administrator.This user creates the development configuration and stores it centrally in a file. This file can then be distributed to all developers participating in the development project. This allows you to ensure that the entire team uses the same development configuration.

Creating development configurations is an online service of the server; no local installation is required.

Prerequisites

The SAP J2EE engine and the development infrastructure are installed.

Procedure

The service is available under a Uniform Resource Locator (URL) in the following structure:

http://<host and port of the J2EE engine instance>/CBSUtils/devconfwiz.jsp

http://myserver.mydomain.com:50000/CBSUtils/devconfwiz.jsp 

...

...

...

       1.      Enter the URL in your browser.

A form appears. It contains the following sections:

¡        Development Configuration

¡        First Software Component

¡        Second Software Component

¡        Third Software Component

Section Development Configuration

       2.      In the field Configuration Name, enter the desired name of the new development configuration according to these rules:

                            a.      The maximum length is 20 characters.

                            b.      Allowed are A..Z , a...z , 0..9 , - , _ , ! , . ,  $

       3.      If applicable, specify the URL of the Name Service as follows:

                            a.      Specify the URL of your name service in the field Name Server URL (http://<host>:<port>).

This is optional. If you leave this field blank, no name service will be used.

SAP urgently recommends that you use a name service, because this service prevents a duplicate use of DC names, database names, and so on.

Sections First/Second/Third Software Component

In the sections First/Second/Third Software Component, you can enter parameters for up to three software components (SCs), which you want to develop or change in this development configuration.

Enter at least one SC (otherwise, the development configuration would make no sense). If you want to specify only one or two software components, leave the other lines blank.

The pre-installed SAP software components SAP_JTECHS, SAP-JEE, and SAP_BUILDT are automatically added to the development configuration; therefore, you must not include them in this list.

Parameters of the Software Components

       4.      Specify the following parameters for every software component:

                            a.      Vendor of the <first/second/third> software component: The vendor of the software component is the organization that originally defined this SC. We recommend to use the Internet domain of the enterprise, for example, sap.com.

§         The maximum length is 20 characters.

§         Vendor names consist of several parts, separated by ‘.’.

§         Each part can contain the characters A..Z , a...z , 0..9  or '-'.

§         There must be at least one part.

§         A part must not begin or end with ‘-‘.

                            b.      Name of the <first/second/third> software component: The name of the software component.

§         The maximum length is 20 characters.

§         Component names consist of several parts, separated by ‘/’.

§         There must be at least one part.

§         Each part can contain the characters A..Z , a...z , 0..9 , - , _ , ! , . ,  $

                            c.      DTR Workspace for the <first/second/third> software component: The URL of the workspace in the Design Time Repository, which contains the source files of this SC, for example, http://dtr.mydomain.com:50000/dtr/ws/carrental/dev.

The last two rows of each SC section contain checkboxes.

       5.      Select a checkbox, if the use dependency named there is true.

For every SC, the other two SCs are specified as use options.

Generating the Development Configuration

       6.      After entering your data, choose Generate Configuration.

The server outputs an XML file containing the development configuration definition.

       7.      Store this file in the local file system under a meaningful name. This name can contain, for example, the name of the SC to be developed and the development state – such as dev or cor.

You can now share the development configuration with all developers. By importing this development configuration, settings are made in the SAP NetWeaver Developer Studio that enable the developers to access the specified workspaces in the DTR or the specified name service.