Tutorial 1: Preparation
Prerequisites
● An Application Server Java (AS Java) with usage type SAP NetWeaver Development Infrastructure (NWDI) for the Design Time Repository (DTR) server is installed.
● Two PCs are installed with a SAP NetWeaver Developer Studio and AS Java on each.
Procedure
Configure the DTR
● Creating two users USER1and USER2 as described in Creating Users and Assigning Groups Using UME. We use them to represent the roles of the developer 1 and developer 2 in a team.
To create the users you do not need the user CMSadm, because the Change Management Service (CMS) is not used in this scenario; you must create an Admin user only if in the last step you want to grant separate authorizations for developers and administrators.
● Creating a hierarchy of workspace folders (workspace folder scenario1contains workspace folder tax) with a DTR workspace dev: scenario1/tax/dev. More information: Creating Workspace Folders.
● Granting read and write permissions to both users in a new workspace is optional – if you do not grant any permissions explicitly, then all user have all rights. More information: Granting Initial Privileges.
Configuration of DTR Client in the Developer Studio
Before a DTR repository can be used from inside the Developer Studio, you must perform some configuration steps:
...
1. Start the Developer Studio.
2. To open the Design Time Repository perspective, choose Window → Open Perspective → Other → Design Time Repository.
3. Switch to the Repository Browser view.
The browser view displays a single entry named OFFLINE. This indicates that you are not yet connected to the DTR.
4. Click OFFLINE with the secondary mouse button and in the context menu, choose Create Client.
5. In the dialog that appears enter USER1as client name.
6. Enter the URL of the DTR server in the form http://<host>:<port>/dtr.
Replace <host> and <port> with the corresponding values of your DTR server instance. For example, if the DTR server has been installed as dtr-server.example.comlistening on port 50000, enter http://dtr-server.example.com:50000/dtr.
7. Enter a local root directory that is used to replicate sources to your local PC: Replace the default value by c:\JDI for this scenario.
8. To commit your changes, choose OK.
An info box appears telling you, that the client has been created.
Repeat these steps for the second Developer Studio installation, but name the DTR client USER2.
Select Files for Automatic Storage in the DTR
Files are stored in the DTR or created new if necessary. This depends on the file type and the development scenario. In scenario Java Development with DTR as Central Storage for the Source Files, storage of two file types is required, which are newly created for the component-based development (scenario Components Development with the NWDI) and, therefore, are by default excluded from the storage. This is the reason why you must change the selection.
...
1. Start the Developer Studio.
2. Choose Window → Preferences → Team → Ignored Resources
A list of file types appears. By default, all types are selected, which means that they are not automatically added to activities and stored in the DTR.
3. Uncheck the following file types:
a. .project
b. .classpath
When creating projects, the unchecked file types are added to activities to be stored in the DTR.
Configuration of Runtime System in the Developer Studio
...
1. Start the Developer Studio.
2. Choose Window → Preferences → SAP J2EE Engine.
3. Select SAP J2EE Engine is installed on local host and choose Browse.
A dialog box appears.
4. Select your local AS Java instance as Local Engine Installation and choose OK.
5. The system name, instance numbers and root paths of your engine are displayed in the Preferences dialog. Complete the dialog.
Perform these steps for both Developer Studio installations.
Starting and Stopping the Runtime System in the Developer Studio
...
1. In the Developer Studio from the menu path, choose Window → Show View → Other → J2EE → J2EE Engine.
The new view J2EE Engine appears. It displays the engines selected in the settings.
2. In the root node of the AS Java, choose:
a. Start Local Engine to start the AS Java.
b. Stop Local Engine if you no longer need the AS Java.
Next Step