Show TOC

Design Time Repository Web UILocate this document in the navigation structure

Use

You can use the Design Time Repository (DTR) Web UI both to review and analyse the available information in the repository, and to directly manipulate files and folders. This means that for certain activities you do not need to use the SAP NetWeaver Developer Studio perspective as an administrative tool.

You access the DTR Web UI using the following URL:

http://<host>:<http-port>/dtr

To access certain configuration and querying facilities of the DTR, use the following URL:

http://<host>:<http-port>/dtr/system-tools

Configuration Tools

These tools are related to DTR administration and configurations. To access them, use the following URL:

http://<host>:<http-port>/dtr/system-tools/administration

For more information about Repository display names, the configuration tool and the name server configuration tool, see DTR Web UI Configuration Areas .

Reporting Tools

You use these tools to retrieve information about activities, integrations, collisions, and so on from the DTR. To access them, use the following URL:

http://<host>:<http-port>/dtr/system-tools/reports

In the DTR Web UI you can use the following options:

Activity Search

You can search for activities that have been created in the DTR using the following options:

  • Workspace : Search only for activities that have been created in the specified workspace.

  • User : Limit search to activities that have been created by the specified user.

  • Open/Closed only : Filter activities to those which are closed (checked-in) or open. The default behavior is to search for both open and closed activities.

  • From ISN ... to ISN : When an activity is checked in or integrated into a workspace, it receives a unique number applicable within that workspace. This is the Integration Sequence Number (ISN). The activity search can be limited to a particular sequence number range.

  • Nonempty only : Filter out activities that are empty.

  • Include propagation lists : The default behavior is to exclude propagation lists from the activity search. Select this option to include propagation lists in the search.

  • Propagation lists only : Search for propagation lists only. Activities are not included in the search results.

You can limit the search to a particular Folder Path . In this case, only those activities are displayed that contain at least one resource (file or folder) in the specified path.

File/Folder Search

You can search for files and folders. This includes searching for deleted files. You have the following choice of search criteria:

  • Search Folder : Here you specify the path. You can determine the path by browsing and selecting the desired workspace.

  • The following search criteria are available which you can use individually or together; you can use wildcards for both criteria.

    • Path Pattern

    • Name Pattern

You can also choose to search for deleted paths and define whether you want to sort by folder or path.

Resource Lookup

You can review the properties of a particular resource in the DTR. You should know either the unique path identifying the resource or the unique resource identifier of the resource.

Workspace Comparison

Use this tool to compare the contents of two workspaces. There are two comparison modes:

  • File level comparison:

    The individual files in both workspaces are compared. Whenever the same version is not active in both workspaces for a certain file, a difference will be reported. For example, there could be two different versions of the same object with the same content in the two workspaces. The comparison will report that the object versions are different even though they have the same content.

  • Integration level comparison:

    Here, the individual files are not compared, but which activities/propagation lists are integrated into both workspaces. Differences will be presented not on specific files but in the form of activities which have been integrated into one workspace but not into the other one.

You can use the following options:

  • Left and Right Workspaces :

    The workspaces you want to compare. Both are required.

  • Folder Path :

    Limit the comparison to only those resources that are present under the specified folder path. If the same object exists in the two workspaces but under different paths, then the object will be considered for comparison if it exists with the specified path in at least one of the workspaces.

Workspace Integrations

You can search for integrations of activities or propagation lists that have been performed on a given workspace using the following options:

  • Workspace : The workspace in which the integrations are to be queried.

  • IntegrationFilter : Limit the integration search based on the integration sequence numbers.

  • Limit integrations to only those that contributed to the folder path : Limit integrations to only those activities/propagation lists that have at least one resource in them under the specified path.

You can also specify additional search options under Query Options .

Conflict Search

You can search for collisions in the repository using the following options.

  • Workspace or Folder Containing Workspace(s) : Search only for collisions that have been created in the specified workspace.

  • Show only those conflicts that correspond to resources under the folder path [Optional] : Filter collisions to only those that correspond to resources under the specified folder path.

  • Owner (User owning either of the conflicting or the active versions) : The user who created either the colliding version or the version that is currently active in the workspace.

  • Conflic State : Search for only open, resolved locked or all types of collisions.

  • From ISN... to ISN : Collisions are created due to integrations of activities/propagation lists into a workspace. Each integration results in the assignment of an integration sequence number that is unique to the workspace. Limit collisions to only those that are caused due to integrations having a sequence number within the specified range.

Repository Browser

You can use the repository browser as follows:

  • To review existing baselines.

    A baseline represents a label that marks a concrete state of the workspace. For example, you can call the baseline Release 1 to mark a concrete release that exists inside the workspace, and later on using the DTR Web UI you can compare this Release 1 to another baseline in this workspace.

    To create a baseline you have to use the DTR command line tool.

  • To review deleted files. You can also restore deleted versions of files.

  • To compare version sets

    You can compare:

    • Baseline to baseline.

    • Baseline to workspace.

    • Baseline to single activity.

    • Baseline to propagation list.

  • For each change you make you can directly create an activity and associate files with this activity.