Entering content frame

Procedure documentation Using the Repository Browser View Locate the document in its SAP Library structure

In the Design Time Repository client, you can access all files that are stored in the DTR server and in your local file system.

Note

Whenever possible, you should use the special views of the SAP NetWeaver Developer Studio, which are available for working with any kind of object. They provide a logical view on all objects you develop and they automatically distinguish between objects you must check in into the DTR and those you needn’t.

The storage of resources in the DTR server is structured by means of workspace folders, Structure linkworkspaces and folders; to this structure in the server, a particular area in the local file system is assigned and administered by the DTR. These two areas are determined (except in Scenario 1) by development configurations, which are used to configure the SAP NetWeaver Developer Studio.

The Repository Browser view enables you to access both storage areas (local and central). Files and folders may exist in the server, in the file system, or in both. The Repository Browser shows a combined view of both storage areas; all objects are displayed graphically together with their properties.

Note

The most important functions available in the Repository Browser view appear in the views of other perspectives as well. For example, you need not leave the Development Components view to synchronize contents from the local file system with contents from the server.

Browsing the DTR

...

       1.      To open the Repository Browser, choose Window  ® Show View  ® Repository Browser.

The Repository Browser view appears (you can position the window anywhere you like). It shows the root node This graphic is explained in the accompanying text of the repository contents that is visible to you.

       2.      Open the root node. You see the following elements:

Below the root appears the workspace folder This graphic is explained in the accompanying text Workspace folders organize workspaces. For different software statuses different workspaces can exist (for example, for the SAP HR software component there may be one workspace for development and one for correction); related workspaces are combined in a workspace folder.

       3.      Open a workspace folder.

Below the workspace folders appear the workspaces This graphic is explained in the accompanying text They contain the resources that belong to a software component; the resources are organized in files and folders.

       4.      Open a workspace.

Below the workspace appear folders This graphic is explained in the accompanying text. They contain other folders and files. If you develop according to the Component Model, the folder structure depends on the naming convention of the Development Components in the DTR. For more information, refer to Component Names.

       5.      Open a folder structure.

Below the folder structure appear the resources.

Identifying Resource Properties

Due to the combined view of the local and central storage, properties of objects in the DTR (folders or files) are displayed as symbols next to the object icons. You can derive the properties of a resource from the combination of the icons.

Example

This graphic is explained in the accompanying text + This graphic is explained in the accompanying text means that this resourceThis graphic is explained in the accompanying text exists only in the local file system This graphic is explained in the accompanying text ; it is displayed like this: This graphic is explained in the accompanying text.

After transferring it to the server, the icon changes to This graphic is explained in the accompanying text Resource synched to latest, meaning that the resource is in the same state both on the DTR server and locally.

When you check out the resource (to change it), the icon changes to: This graphic is explained in the accompanying text

For more information on icons, refer to Icons in the DTR Client. The properties of the Repository Browser objects are displayed as texts in the Properties view. To open this view, choose Window  ® Show View  ® Repository Browser.

Note

If you have reason to believe that the contents of the Repository Browser (or of any other view) are not up to date, use the Refresh function.

Editing Resources

The context menu of the Repository Browser offers several editing functions. The functions vary according to the type of resource. For example, you cannot delete a workspace in the Repository Browser, but you can delete a file or a folder.

Workspace Folder

You can display it in the Browser or add it to your favorites.

Workspace

You can use the functions available for workspace folders. In addition, you can synchronize the local file system with the server contents or delete the contents from the local file system. Use Sync to date to add a date to the workspace.

Folder

You can use the functions available for workspaces. In addition, you can:

·        Edit files in the folder or in the folder including its subfolders (check out)

·        Add the folder on its own or including its files – including or excluding the subfolders – to the Repository contents.

This option is available only as long as the objects exist only in the local file system.

·        Delete the folder including or excluding its subfolders

·        Assign the entire folder to an Structure linkactivity. This is advisable if you will make several logically connected changes to the objects in this folder.

·        Uncheck out a folder

·        Upload the folder, upload it by force, or download the folder.

·        Create a project in the folder.

File

You can use the functions available for folders. In addition, there are functions for solving a Structure linkconflict:

·        Display changes

·        Compare to the current version

·        Merge the file with another file

·        Keep the active version

·        Keep the conflicting version

Finally, you can:

·        Display the file contents

·        Display the Structure linkversion graph of the file.

 

 

 

 

Leaving content frame