!--a11y-->
Scenario 2: Preparation 
...
· A SAP NetWeaver J2EE Engine with DTR server is installed.
· Three PCs are installed with a SAP NetWeaver Developer Studio and a SAP NetWeaver J2EE engine on each.
...
1.
Configure the
DTR user
management.
2.
Create
three
DTR
users USER1, USER2, and USER3.
3. Create two DTR workspaces named ws/scenario2/technology/dev and ws/scenario2/application/dev.
4.
Grant
read and write
permissions to all users in the new workspace.

For a number of frequently used administrator tasks
– such as creating workspaces and maintaining authorizations for
resources in the DTR – you can use the
DTR Administrator
Plug-In.
Access to the required workspaces is regulated in development configurations. The development configuration must correspond to the previously created workspaces.
...
1. Use the self-service to create a development configuration.
a. Start an Internet browser and enter http://<host>:<port>/CBSUtils/devconfwiz.jsp in the address line.
b. Replace <host> and <port> with the corresponding parameters of your DTR server instance.

For example, if the DTR server has been installed as server.example.com listening on port 50000, enter http://server.example.com:50000/CBSUtils/devconfwiz.jsp.
2. In the self-service form enter CONFIG1 as name of the development configuration.

A name server, which would check the uniqueness of DC names, is not used in this example.
3. Enter the following two rows in table Software Components and again replace <host> and <port> with the parameters of your DTR server instance:
a. SC1:
§ SC Vendor: example.org
§ SC Name: technology
§ DTR Workspace: http://<host>:<port>/dtr/ws/scenario2/technology/dev
b. SC2:
§ SC Vendor: example.org
§ SC Name: application
§ DTR Workspace: http://<host>:<port>/dtr/ws/scenario2/application/dev
4. Finally, for SC application mark the checkbox in column use SC1.

This allows the software component application to use software component technology.
5. Choose Generate Configuration.
The self-service creates a development configuration and displays it in the browser window.
6. Save the content of this window to a file named configuration.xml.
The import of a development configuration automatically makes the settings required for the DTR access in the SAP NetWeaver Developer Studio.
...
...
...
1. Start the SAP NetWeaver Developer Studio.
2. Open the Development Configurationperspective.
3.
In the
toolbar, choose
Development Configuration to import a
configuration.
4. In the import wizard, select local development configuration file.
5. Choose Browse to locate the configuration.xml file in the file system.
6. Choose Next and then Finish.
7. If you are not yet logged on to the DTR, a logon window will appear. Enter USER1 and the corresponding password.
8. In the Development Configuration perspective, switch to the Active DCsview.
You should see a single entry CONFIG1 that represents your configuration. The SAP NetWeaver Developer Studio is now configured.
Repeat the import for the other SAP NetWeaver Developer Studio installations. To do this, you must copy the configuration.xml file manually to the other developers’ workplaces.

You can do this, for example, by e-mail.
Not all files are meant to be stored in the DTR. Unlike in scenario 1, in scenario 2 there is no need to store the file types .project and .classpath.
...
1. In the menu chose Window ® Preferences.
The Preferences dialog window appears.
2. ChooseTeam ®Ignored Resources.
A list of file types appears that are not stored in the DTR.
3. If required, mark the checkboxes for .project and .classpath.
Perform these steps for all developer installations.
...
1. Start the SAP NetWeaver Developer Studio.
2. Choose Window ® Preferences ® SAP J2EE Engine.
3. Select SAP J2EE Engine is installed on local host and choose Browse.
A dialog window Local Engine Installations appears.
4. Select your local SAP J2EE engine instance and choose OK.
The system name, instance numbers and root paths of your engine are displayed in the Preferences dialog.
5. To commit your changes, choose OK.
Perform these steps for all developer installations.
