Show TOC

Procedure documentationManaging Development Configurations in the Landscape Locate this document in the navigation structure

 

Use this application to manage the development configurations for those Java systems that you would like to manage in TMS (build location, repository location, software components to be developed). In addition, you can use this application to set up your Java development environment (for example, runtime system, build location, repository location, software components to be developed, and so on) for local use without transport routes to other configurations and without embedding into a CTS Transport Landscape. Note that this tool is used by administrators to include non-ABAP systems using an NWDI to manage and build Java Sources into the Transport Domain in TMS. You can import or update the development configurations that are edited using this tool into the SAP NetWeaver Developer Studio.

For more information, see http://help.sap.com/NW70 -> SAP NetWeaver 7.0 including Enhancement Package 1 -> <language> —> SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Solution Life Cycle Management by Key Capability -> Software Life-Cycle Management -> Software Logistics -> Change and Transport System -> Change and Transport System - Overview (BC-CTS) -> Transporting Non-ABAP Objects in Change and Transport System -> Performing Configuration Steps for Non-ABAP Transports -> Defining and Configuring Non-ABAP Systems..

Prerequisites

Add the required actions to your user’s role (for example: users SAP_DI_Administrator, SAP_DI_Developer, SAP_NWDI_Administrator). An administrator’s role should have in addition to already existing CBS admin actions all of the listed below actions. The actions available for CMS (Configuration Service, Import Service and Deploy Service) are:

  • DICMServices.Create — to be able to create configurations within Development Infrastructure Configuration Service, the user used for communication between ABAP and Java (HTTP Destination) needs to have this permission.

  • DICMServices.Modify — to be able to modify configurations within Development Infrastructure Configuration Service, the user used for communication between ABAP and Java (HTTP Destination) needs to have this permission.

  • DICMServices.Delete — to be able to delete configurations within Development Infrastructure Configuration Service, the user used for communication between ABAP and Java (HTTP Destination) needs to have this permission.

  • DICMServices.Export — to be able to trigger a Release (Export) within Developer Studio of own activities.

  • DICMServices.ExportForeign — to be able to trigger an Release (Export) in NWDS for own and foreign activities.

  • DICMServices.ExportAll — you need DICMServices.Export and DICMServices.ExportForeign to be able to Export within the Export Service (SDAs and SCAs export).

  • DICMServices.Display — to be able to display configurations in Development Infrastructure Configuration Service.

  • DIImportService.Import — to be able to trigger an import, the user used for the DeployWebProxy Destination needs to have this permission.

  • DIDeployService.Display — to be able to view pending deployments, for example with the DI Deployer Servlet.

  • DIDeployService.Deploy — to be able to deploy on the runtime system, the user used for the DeployWebProxy Destination needs to have this permission.

  • DIDeployService.Configure — to be able to configure the deploy service, the user used for communication between ABAP and Java (HTTP Destination) needs to have this permission.

  • DIDeployService.Administrator — to be able to administrate the deploy service, the user used for communication between ABAP and Java (HTTP Destination) needs to have this permission.

A Developer role should have (in addition to already existing CBS developer actions): DICMServices.Display, DIDeployService.Display, DICMServices.Export and (if required to be able to export other user’s activities) DICMServices.ExportForeign.

Procedure

Creating New Development Configuration

  1. Open the SAP NetWeaver Administrator tool. Choose   Configuration Management   Infrastructure  .

  2. Open the Development Infrastructure link.

  3. Choose Create New... pushbutton. In the dialog that appears specify the name of the development configuration you want to create and confirm the dialog.

    Note Note

    In general up to eight letters can be used as name for development configurations. User can also load development configurations that were created from within STMS, these configurations always have only three letters. You have to comply to this naming rules to be able to manage the transports within the ABAP Transaction STMS (CTS+). You can also load development configurations that were created from within STMS; these configurations always have only three letters.

    End of the note.
Loading Development Configuration

  1. Open the SAP NetWeaver Administrator tool. Choose   Configuration Management   Infrastructure  .

  2. Open the Development Infrastructure link.

  3. In the Development Configuration dropdown menu choose the name of the development configuration to load.

  4. Choose Enter.

    The development configuration is loaded.

Editing Development Configuration

  1. Load the development configuration and switch to editing mode.

  2. For each development configuration, you can change the properties in each of the tab pages.

  3. Choose Save pushbutton to apply the changes.

    If you want to reject the changes you made and restore the development configuration properties to the last saved state, choose Cancel pushbutton.

Copying Existing Development Configuration Settings

You can make your development configuration to have the same local environment and software component (SC) definitions as in an already existing development configuration. This can be useful in case you need similar development configurations for your different systems. The development configurations you can use as template are shown in the dropdown menu. You can see all development configurations configured within the configuration service you are actually logged on to. To copy the settings of an existing development configuration you have to:

  1. Load the development configuration you want to overwrite and switch to editing mode.

  2. Activate the check box in front of Copy Definition from to enable the copy functionality.

  3. Choose the development configuration that you want to use as template from the Copy Definition from dropdown menu. In the dialog that appears, choose OK pushbutton.

    The settings are overwritten. Review the Local Environment and Software Component Definition tab pages to make sure everything is correct.

  4. Choose Save pushbutton to apply the changes.

Grouping Development Configurations

You can group development configurations by putting them in a logical path. To do that:

  1. Load the development configuration and switch to editing mode.

  2. Open the Local Environment tab page.

  3. Specify the logical grouping path in the Path field.

  4. Choose Save pushbutton to apply the changes.

Managing Transport Settings

You can specify settings for export service. Export is needed in case you want to obtain something out of the system (for example, for distribution, shipment, and so on). Export Location is used by Export Service. The objects exported with export service will be stored in the defined export location. To specify the export location:

  1. Load the development configuration and switch to editing mode.

  2. Open the Local Environment tab page.

  3. Specify the type of files to export under Transport Settings. Note, that it is not allowed to activate both Activity Export and DC Export at the same time.

    • Activity Export

      Choose this checkbox when you want to allow transport of changes on source level, released by developers in Developer Studio. Then this system of your CTS landscape needs to have at least one target system of type DI with defined repository location. Note, that if there is no target system of type DI connected with this system it makes no sense to transport on source level and the import will fail.

    • DC Export

      Choose this checkbox when you want to allow transport of changes on development component level, released by developers in Developer Studio. All changed deployable DCs, affected by the source changes, will be transported. Note, that these transport requests do not contain sources. During import only the runtime system will be updated.

    • SCA Export

      Choose this checkbox when you want to allow the export on software component level. The export is done in the Export Service Web UI. Note, that with this type of export you can ensure the consistency of the exported SCs because all active changes of the SC will be exported.

    • SDA Export

      Choose this checkbox when you want to allow the export on development component level for the selected SC. All selected development components will be exported. The export is done in the Export Service Web UI. Note, that with this type of export you can not ensure the consistency of the exported SCs because the user doing the export needs to know the DC dependencies.

  4. (Optional) Specify the export destination. You have to define the destination using the AS Java. You use the destination alias to connect the AS Java system and the hosting CM Services, with the CTS+ landscape. The destination needs to point to the communication system defined for this system (of the development configuration) in the CTS+ landscape. For example: sap.com/com.sap.tc.di.CTSserver.

  5. Choose Save pushbutton to apply the changes.

Specifying Repository and Build Location

You can configure the desired repository for the development as well as the desired build tool location. To specify the location of the Design Time Repository (DTR):

  1. Load the development configuration and switch to editing mode.

  2. Open the Local Environment tab page.

  3. Choose the Repository Location check box and specify the path to the DTR in the format http://host:port/dtr or https://host:port/dtr.

  4. Specify the Communication User and Password.

  5. Choose Save pushbutton to apply the changes.

To specify the build tool location:

  1. Load the development configuration and switch to editing mode.

  2. Open the Local Environment tab page.

  3. Choose the Build Tool Location check box and specify the path to the build tool location in the format http://host:port or https://host:port.

  4. Specify the Communication User and Password if you have not done so already.

  5. Choose Save pushbutton to apply the changes.

Managing Runtime Systems

  1. Load the development configuration and switch to editing mode.

  2. Open the Local Environment tab page.

  3. Choose the type of the runtime system you want to use and specify the connection settings.

  4. (Optional) To disable the automatic deployment of the developed SCs added to the development configuration, uncheck the Enable Autodeployment of Developed Software Components checkbox. You can select exactly which SCs to be deployed or not in the table.

  5. Choose Save pushbutton to apply the changes.

Managing Software Component Definitions

For each development configuration, you can specify the SCs to be used. The desired SCs must be created and configured in the SLD.

To add SCs:

  1. Load the development configuration and switch to editing mode.

  2. Open the Software Component Definition tab page.

  3. Choose the Add SC pushbutton for a list of SC that you can add to the development configuration.

  4. Select the desired SCs from the list that appears and choose Add pushbutton.

  5. To mark a SC for development select it from the Software Components list and choose To Be Developed checkbox.

  6. (Optional) For each development configuration you can specify build options. You can either specify build options that make sense in your own development configuration, or choose from the list of supported build option. The default state is to have no build options. For more information about the supported build options, see Build Options.

    Note Note

    The Apply Variant to all SCs pushbutton allows you to apply all build options of one developed SC to all SCs. However, it is not possible to apply single build options to other SCs. Note that required SCs do not have build options at all.

    End of the note.

  7. Choose Save pushbutton to apply the changes.

Exporting Development Configuration

If you want you can take the development configuration you configured and distribute it in a suitable for you way (for example, send it in an e-mail). The development configuration is exported in XML format. You can import it in your SAP NetWeaver Developer Studio. To export the development configuration:

  1. Load the desired development configuration.

  2. Save the development configuration, if you have changed it.

  3. Choose the Download Development Configuration link and navigate to the location where you want to store the development configuration.

Deleting Development Configuration

  1. Load the development configuration and switch to editing mode.

  2. Choose Delete pushbutton.

  3. In the dialog that appears, confirm that you want to delete the development configuration from the SLD.