Show TOC

Working with Development Infrastructure - Basic OperationsLocate this document in the navigation structure

Prerequisites

  • You are logged on to the development infrastructure.

  • You have at least one open activity.

Procedure

Checking the Activity into the Design Time Repository

Activities contain versions of resources such as development components. After checking in an activity, all changes that are assigned to the activity are stored in the repository and the new version of the resource becomes visible to other users. In SAP NetWeaver Development Infrastructure (NWDI) this is the Design Time Repository (DTR).

Note

You can exchange the DTR with another repository if you want to. However, this may result in some loss of the development infrastructure's functionality.

To check an open activity into the DTR:

  1. Open the Development Infrastructure perspective.

  2. In the Open Activities view, click the activity node with the secondary mouse button and choose Checkin .

    In the dialog that appears, you can add a description or change the name of the activity.

  3. Choose OK .

  4. In the dialog that appears, choose No . You can activate the resources in a separate step.

Check the messages displayed on the DTR Console view. In particular, no errors should be displayed there. As a result of a successful procedure, the activity will be closed and the corresponding node will be removed from the Open Activities view.

The new version of the resources is stored on the server and is visible to other users. Log on to the NWDI with another valid user and check the visibility.

Activating Activities in the Component Build Service (CBS)

After you have checked in your DCs, they are stored as an inactive version in the DTR. To activate the changes from within the Developer Studio:

  1. Open the Activation view.

  2. Click the activity node with the secondary mouse button and choose Activate .

    The Activation dialog appears. If an activity has dependencies to other DCs, the windows shows it. In this case, you will see a button Activate with all Predecessors ; if there are no dependencies, you will see only the button Activate .

  3. Choose Activate or Activate with all Predecessors .

  4. To trace the build process in the Activation Requests view, choose Open Request View ; otherwise choose OK .

The source files in your activity are now built centrally and activated in the CBS. In this process, the predecessors of an activity are activated as well - however, only those that are required by the selected activity because it is built on them.

You can check whether the activated DC is also displayed in the Active view mode of the Development Infrastructure perspective.

Releasing Activities using Change Management Service (CMS)

Once the activation is successful, the changes can be released for transport.

To perform this task, proceed as follows:

  1. Open the Transport view.

  2. Select the node of the workspace whose activities you want to release.

  3. Expand the Waiting node. Under the <default> change request, you see the list of activities you have selected.

  4. Select the activities that you want to release and choose Release from the context menu.

  5. In the Release for Transport window that appears, choose Release again.

You have packed one or more activities in a change request and released them for transport.

Check whether, depending on what happens after they are released, the activities appear either under the Released node or Failed node in the Transport View .