Post Installation Steps of Usage Type
DI
Use
This document offers an introduction on how to configure the SAP NetWeaver Development Infrastructure (NWDI), that is, usage type DI.
To configure usage
type Development Infrastructure (DI), you use the
Configuration
Wizard. With this you configure either the entire usage type DI after
completing the installation or its individual services. The configuration
itself consists of a number of steps which the tool automatically executes.
You only provide the parameters and trigger the execution process.
Procedure
Starting Automatic Post Installation Configuration
...
...
1. To start the Configuration Wizard, start the SAP NetWeaver Administrator and log on as an administrator. Choose Deploy and Change → Configuration Wizard.
You have to choose the configuration task to execute from the list.
2. Select the configuration task Initial setup of functional unit Development Infrastructure (DI all-in-one).
3. Choose Start and follow the steps of the wizard.
Once CMS domain is configured using the configuration wizard, it is only possible to change configuration data (for example, transport directory) in CMS manually. The reason is that changing domain data affects all tracks configured in CMS. So the person changing these data must have an overview of all existing tracks (are there configured tracks or not, are there productive tracks or not, and so on). Such an overview is not possible in the configuration wizard.
Manually Configuring the Usage Type DI
If for some reason the automatic post installation wizard fails, you can try to manually execute the configuration steps. Here you can find information about the exact manual configuration steps:
...
3. Set Up Privileges, Roles, and Groups.
4. Granting Initial Privileges.
5. Preparing the System Landscape Directory (SLD)
6. Setting Up the Name Service
8. Creating a Development Track
9. Importing SCAs for the Track
You can use also the configuration tasks:
■ Change Management Service (CMS): Create an Application Skeleton to create tracks for some common application types, for example xApps or Composites.
■ Change Management Service (CMS): Modify a Software Component to create a track for modification of an SC, for example for SAP_ESS.