DRL accessibility on WDK
Comments
-
You don't need to add the DRL component to your custom folder unless you want to override the default behavior.
What exactly is the problem ? You should probably first try to fetch the DRL if a test document (e.g. via Properties page) and then try to access it.
0 -
Thanks for responding. I have a wdk.war and i deployed it on tomcat. When i try to access the DRL and test with one document's object id, I am getting the error message pop up "401, URL is not authenticated:".
the tag <url-addressable-enabled/> is present in drl component xml on wdk layer. but still i am getting the url authentication issue. The below is the url i am trying to access:
http://localhost:8080/wdk/component/drl?objectId=0903944780015934
0 -
The syntax for DRLs is http://localhost:8080/wdk/drl/objectId/0903944780015934
And you can add optional parameters such as format, page, etc, e.g. http://localhost:8080/wdk/drl/objectId/0903944780015934/format/pdf
Like I wrote before, get the DRL from the properties page of your document.
0 -
I can access above DRL from webtop application. but i have vanilla wdk.war and deployed it on tomcat and i don't have any customization there in custom layer.
I couldn't access none of the WDK components. Even login page itself is not coming up on the browser. Did i miss any configuration or do i have to customize the DRL component in order to access it from wdk layer?
0
Categories
- All Categories
- 111 Developer Announcements
- 49 Articles
- 102 General Questions
- 123 IM Services
- 40 OpenText Hackathon
- 31 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 898 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 124 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 1 XM Fax