cancel
Showing results for 
Search instead for 
Did you mean: 

DTR access

Former Member
0 Kudos

I have a ID which I use to access DTR all the time. It has the JDI.administration role which is configured according to instguide.

But the ID stopped working, I can no longer access the ~/dtr web page. System responsed that I can view the web page. As far as I can see, neither UME or ABAP security has changed for this user.

Any ideas?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Apart from DTR, are you abel to access CBS and CMS try this solution

The problem seems to be with your DTR client. I increased the trace

level in LogConfigurator, and this is the error which is displayed:

Invalid ACE Entry. Non-existing principal: NEW DTR Client1

To solve this, first you must ensure that you have a DTR client for

DTR root.

Start the DTR Admin Plug-In.

2. In the repository browser, select the root node.

Usually, this node is labeled <user> on <system>.

3. In the context menu, choose View Permissions.

The Permissions view of folder /ws appears.

4. To maintain authorizations for the root directory, enter

From the title bar of the Permissions view View Permissions for URL...,

choose Menu.

Usually, the proposed value is exactly the URL of the root directory

(ht(http://<server>:<port>/dtr/), so that you can just accept this valueThe Permissions view of the root directory appears.

5. In the Permissions view, choose Add Principal from the

context menu.

A dialog window appears.

6. Make the following settings:

a. As the Principal Type, select ALL.

b. Select the following principles:

access

read

c. Confirm your settings with OK.

You must also follow the below steps to the ACL once you verify the

root.

Please add the following

lines to the ACL:

<ace>

<isgroup />

<principal>CMSadm</principal>

<grant>

<privilege>access</privilege>

<privilege>read</privilege>

<privilege>write</privilege>

<privilege>checkin</privilege>

<privilege>import</privilege>

<privilege>export</privilege>

<privilege>integrate</privilege>

<privilege>adminA</privilege>

<privilege>adminX</privilege>

</grant>

Regards,

RK

:P.S Consider rewarding suitable points if the given info helped you!!!

Former Member
0 Kudos

Hi,

Have a very basic question. Because I imported CMS tracks, a DTR client got automatically created (with the track name). Everytime I open NWDS, I see OFFLINE at the root of repository browser and after I login, I see the DTR client for the track that was last opened.

Now my problem is I dont see the root node that the help manual talks about, where I need to first set the permissions for the administrator.

How do I get to the ROOT or the <system> or <user> folder in the repository browser.

Thx

Bhaskar

Message was edited by: Bhaskar Vedamurthy

htammen
Active Contributor
0 Kudos

Hi Bhaskar,

1. you should have asked your question in a new task.

2. to solve your problem you have to create a separate DTR Client from within the Eclipse perspective DTR. There you can choose "DTR -> Create Client". In the wizard define "DTR Server URL" as "/".

Regards

Helmut

Former Member
0 Kudos

Thanks for the response. I tried giving "/" for the DTR Server URL but it gives me the error URL should start with a protocol specifier". Over that, it forces me to enter a host name. So entering "/" wont work. Any other suggestion.

And yes I will post a new msg in the future. Thought it would be better to get an answer from the folks who are closer to the problem I am facing.

I had tried creating a new DTR

Thx

Bhaskar

htammen
Active Contributor
0 Kudos

Hi Bhaskar,

sorry, I haven´t been exactly enough. The server URL of course has to look like this:

If you´re using SSL you should of course use https instead of http.

Regards

Helmut

Former Member
0 Kudos

Thanks Helmut. I had created the New DTR Client earlier (2 days back) with that url for Root, but didnt see any nodes underneath it. But now after you suggested it, I tried again and I am seeing the hierarchy with all the tracks under it, including <system> node. Dont know what changed, but I would attribute it to the refresh issues I am seeing with the NW studio.

Thanks once again in resolving this issue

-Bhaskar