xCP 2.1 - Viewer Widget not working for an unknown reason

Hi experts,

I'm currently evaluating xCP 2.1 with the developer edition and i'm trying to display the content of a pdf document in the standard widget viewer but i'm unable to do that.

Capture1.PNG.png

I retrieve the Object ID and Content Type from a Result List populated thanks to a stateless process. When I click on the row, the viewer seems to react but the name of the document and the content never appear.

I set in xCP Designer to use Acrobat Reader as the viewer for pdfs but it seems that it's xCP Content Viewer which is used.

Capture2.PNG.png

As you can see in the previous picture, the r_object_id and the a_content_type are successfully retrieve from the selection but for an unknown reason the display doesn't work.

I must be missing something but I don't know what.

Could you please help me ?

Thanks in advance

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

nking

Then I think the problem is related to the fact that the viewer in 2.1 requires an xCP URN for the object Id, and not just the normal Documentum r_object_id value. Offhand it is something like this - contents/<type>/<r_object_id>

What is confusing here is that if you bind the r_object_id which is the output of a real-time-query or an object model, the runtime implicitly passes the URN, whereas if it comes from a stateless process, it is not a URN.

All comments

Jeremy Saumen

Hi,

Sorry, I forgot something : by using the developper tools from Chrome, it seems that the URL used to retrieve the content doesn't seems to work (404) :

http://demo-server:8000/ID_Check/090007c28000e7fe/view?ann=false&man=false&prn=false&contentType=pdf&thm=false&mdc=false&_dc=1457009031862&location=

Does any know why am I facing this issue ?

Thanks

nking

It relies on the ACS server, so can you confirm that the ACS service actually works.

Sent from my iPhone

Jeremy Saumen

Hi Nick,

It seems so :

Capture3.PNG.png

And the xDM example seems to work as intended

Capture4.PNG.png

But it seems that the URL generated to access the file through xDM is different (the type of the document isn't present in my url) :

http://demo-server:8000/xCelerated_Document_Management/contents/xdm_contract/090007c28000cddf/view?ann=false&man=false&prn=false&contentType=pdf&thm=true&mdc=false&_dc=1457012149070&location=

It seems that this url retrieve informations about the document as a JSON content.

{"objectId":"090007c28000cddf","provider":"AcrobatReader","objectName":"Hazelcast_Deployment_And_Operations_Guide_v0.4_web.pdf","providerType":"iframe","format":"pdf","versionLabel":"1.0,CURRENT","automationLibrary":"","pageCount":37,"allowThumbnail":false,"allowPageModify":false,"displayAnnotations":false,"allowAnnotate":false,"supportUrlFallback":false,"optionalData":"","userAnnotationUrl":"","allAnnotationsUrl":"","documentUploadUrl":"","annotationUploadUrl":"","printAuditUrl":"","exportAuditUrl":"","viewerAutomationUrl":"","pageDeletionUrl":"","pageReorderUrl":"","pageInsertionUrl":"","pageExtractionUrl":"","attributeList":[{"name":"src","value":"/xCelerated_Document_Management/contents/xdm_contract/090007c28000cddf/stream?provider=AcrobatReader"}],"objectUri":"contents/xdm_contract/090007c28000cddf"}

This JSON contents objectURI to download the file

http://demo-server:8000/xCelerated_Document_Management/contents/xdm_contract/090007c28000cddf/stream?provider=AcrobatReader

Jeremy Saumen

Well, I was able to do what I wanted using a Stateless Process (containing a single step : an Execute Java Service containing a custom code in charge of retrieving an ACS content from an r_object_id) and a value display (of data type html in charge of displaying the url generated by the ACS server).

Capture5.PNG.png

Capture6.PNG.png

It works fine but if you have an explanation why i'm unable to use the default viewer, I would be interested to know.

nking

shilpy

It may appears like a "commercial" and it is a bit

if you need extra features for viewing there is also a certified solution called ARender4Documentum we have a deep integration ready for xCP2. it comes with a cost of course, but it is very powerful as well

Jeremy Saumen

Thank you Nick, I didn't catch your last message that's why my response is a bit late.

I'm a step further now : by modifying the attribute Object Id from the component Viewer from "widgets.results_list.selected_row.out_r_object_id" to "'contents/'+ widgets.results_list.selected_row.out_r_object_type + '/'+ widgets.results_list.selected_row.out_r_object_id", now I'm able to retrieve the json object.


{
  "objectId":"090007c28000e565",
  "provider":"AcrobatReader",
  "objectName":"Saumen Jeremy.pdf",
  "providerType":"iframe",
  "format":"pdf",
  "versionLabel":"1.0,CURRENT",
  "automationLibrary":"",
  "pageCount":-1,
  "allowThumbnail":false,
  "allowPageModify":false,
  "displayAnnotations":false,
  "allowAnnotate":false,
  "supportUrlFallback":false,
  "optionalData":"",
  "userAnnotationUrl":"",
  "allAnnotationsUrl":"",
  "documentUploadUrl":"",
  "annotationUploadUrl":"",
  "printAuditUrl":"",
  "exportAuditUrl":"",
  "viewerAutomationUrl":"",
  "pageDeletionUrl":"",
  "pageReorderUrl":"",
  "pageInsertionUrl":"",
  "pageExtractionUrl":"",
  "attributeList":[
  {
  "name":"src",
  "value":"/ID_Check/contents/pwc_client_document/090007c28000e565/stream?provider=AcrobatReader"
  }],
  "objectUri":"contents/pwc_client_document/090007c28000e565"
}

The viewer component is now displaying the title of the document but the content is not available and the following stacktrace is generated on the AppHostServer.

SEVERE: Servlet.service() for servlet [PwCDocumentViewerServlet] in context with path [/ID_Check] threw exception [DfContentObjectAccessException:: THREAD: $
DfContentObjectAccessException:: THREAD: http-bio-8000-exec-60; MSG: [DM_SYSOBJECT_E_CANT_GET_CONTENT]error:  "Cannot access content for id '090007c28000e57$
        at com.documentum.fc.client.content.DfContentObjectAccessException.newCantAccessContentObjectException(DfContentObjectAccessException.java:20)
        at com.documentum.fc.client.content.impl.ContentFinder.getContent(ContentFinder.java:71)
        at com.documentum.fc.client.content.impl.ContentManager.getContentNoPermissionCheck(ContentManager.java:144)
        at com.documentum.fc.client.content.impl.ContentManager.getContentSize(ContentManager.java:1398)
        at com.documentum.fc.client.DfSysObject.getContentSize(DfSysObject.java:4586)
        at com.emc.xcp.runtime.aspect.impl.DataTypeAspect___PROXY.getContentSize(DataTypeAspect___PROXY.java)

It turns out that I need to have the aspect "defaultdatatypeaspect" attached to the document for the viewer to work : as soon as the aspect is attached, everything works has intended.

Do you know if there is a way to prevent that ? Or could you give me an explanation why this has to work like that ?

Thanks in advance

samir.vaidya

Just one quick observation - xCP Developer Edition does not come with CTS, and without the renditions generated by CTS, Viewer can't display images. I may be wrong though. Someone who has been able to make Viewer work in Developer Edition can correct me.

Jeremy Saumen

Hi Samir,

I know that CTS is not supported but i'm not using the default xCP viewer with my application, i'm using the Adobe Reader viewer which doesn't require CTS.

Capture.PNG.png

The viewer is working fine now but I don't understand why the aspect "defaultdatatypeaspect" is necessary.

We are evaluating the use of xCP on already existing documents to develop an application for a limited number of users and if the aspect is necessary we will have to migrate of part of these documents for the application to work. In fact, I think that the final version of my application probably won't use any of those viewers because the documents are encrypted with IRM for Documentum and I probably will have to create my own viewer. My question is only for my personal knowledge.

samir.vaidya

Sorry, didn't notice that you are not using OOTB viewer.

I am not sure about "defaultdatatypeaspect". Is the data type of the content defined within xCP app? If not, then try adopting that data type in your app.

Jeremy Saumen

Hi Samir,

I already have adopted the type in my xCP application but no luck : at the beginning, I tried to use a Real-Time Query to retrieve the list of documents to treat, so I adopted my custom type but I wasn't able to continue this way because a part of my query is based on some values on an aspect created outside of xCP (and I didn't find a way to import this aspect into xCP), so the realtime query was remove but the adopted type stayed to be exploited through several stateless processes.