UCF file upload with ucfContent

Hi All!

I would like to upload a file with UCF on DFS 6.5.

Is it necessary for the content to be UcfContent or can it be of type DataHandlerContent?

I haven't found too much documentation about creating UcfContent, so I assume, that filePath in the code above represents the local path based on which the File object can be instantiated.

         UcfContent ucfContent = new UcfContent();
        ucfContent.setContentTransferMode(ContentTransferMode.UCF);
        ucfContent.setFormat(format);
        ucfContent.setLocalFilePath(filePath);

However my create call fails, and I extracted the following fragment from the 500 response:

<exceptionClass>com.emc.documentum.fs.rt.ServiceInvocationException</exceptionClass><genericType>java.lang.Exception</genericType><message>File not found &quot;/dms/dctm/shared/jboss4.2.0/server/c:/Users/myuser/Documents/NetBeansProjects/DokufunnelBasic/res/tomcat.gif&quot;</message><messageId>E_CONTENT_DOES_NOT_EXIST</messageId>

It concatenated a server path with my filePath which is the latter one...

The following UCF init code might be relevant:

        UcfConnection connection = new UcfConnection(ucfServerUrl);        String jsessionId = connection.getJsessionId(); // = req.getParameter("jsessionId");        logger.log(Level.CONFIG, "JSessionID is: {0}", jsessionId);        String uid = connection.getUid(); // = req.getParameter("uid");        logger.log(Level.CONFIG, "uID is: {0}", uid);        activityInfo = new ActivityInfo();        activityInfo.setActivityId(uid);        activityInfo.setSessionId(jsessionId);        activityInfo.setAutoCloseConnection(false);        ContentTransferProfile ct = new ContentTransferProfile();        ct.setTransferMode(ContentTransferMode.UCF);        ct.setActivityInfo(activityInfo);        ServiceContext serviceCtx = ServiceContextManager.getServiceContext();        if (serviceCtx != null) {            serviceCtx.getProfiles().clear();            serviceCtx.getProfiles().add(ct);        }        ServiceContextManager.registerContext();

Could someone please help me?

Thanks!

Find more posts tagged with

Comments

mszurap

Hi,

I think you should add the ct (ContentTransferProfile) object to the OperationOptions of the ObjectService.create() method.

Please keep in mind that if you do not close your UCF connections (autoCloseConnection = false), they might timeout after a time, and your calls may fail, and besides you use server resources for no reason. It might be used, if you know that you will do several calls in a batch ("in a transaction", of course it is not a transaction, but you should handle it like it was, so ensure that the last call sets the autoCloseConnection to true).

Cheers

Miklós

darvasip

Hi!

Thanks for your response!

I've already added the profile, just omitted that fragment of code from my initial post.

I've set the profile both in serviceContext and OperationOptions as UCF is stated not to work otherwise.

            OperationOptions options = new OperationOptions();            ContentTransferProfile contentTransferProfile = new ContentTransferProfile();            contentTransferProfile.setTransferMode(ContentTransferMode.UCF);            options.getProfiles().add(contentTransferProfile);            logger.log(Level.INFO, "Invoking the create operation on the Object Service.");            dataPackage = ServiceManager.getServiceManager().getObjectServicePortWithInjectedToken().create(dataPackage, options);

You are right about the autoCloseConnection flag, setting it to false was a result of my experimentations searching the possible solution for my problem, with no success..

Is content type of ucfContent necessary in the case of UCF (I think so..)?

Is my filePath correct?

Any other ideas?

BR,

Peter

mszurap

Hi,

It seems that you have not set the ActivityInfo (containing the uid and jsessionid) on the ContentTransferProfile object which you pass to the OperationOptions.

I think you can use simply "FileContent" instead of UcfContent, it does not matter.

Mike

darvasip

Hi!

Thanks, setting the activity info to contentTransferProfile resulted in another type of inner exception:

<exceptionClass>com.emc.documentum.fs.rt.impl.ResourceLookupException</exceptionClass><genericType>java.lang.Exception</genericType><message>Session is not found.</message><messageId>E_UCF_SESSION_NOT_FOUND</messageId>

I continued experimenting after that and noticed, that setting closed (from which I found no documentation) parameter of activityinfo to true resulted the same old exception of file not found

activityInfo.setClosed(true);

<genericType>java.lang.Exception</genericType><message>File not found &quot;/dms/dctm/shared/jboss4.2.0/server/c:/Users/myuser/Documents/NetBeansProjects/Df/res/tomcat.gif&quot;</message><messageId>E_CONTENT_DOES_NOT_EXIST</messageId>

I assume that FileContent can only be used with Productivity Layer, which I cannot use for some reasons.

So I am still stucked..

Regards,

Peter

mszurap

You have not mentioned yet what is the output of your log file. Is JSESSIONID and UID valid (does UID increasing each time)?

Are you using the same server (host, port and server application) for DFS calls and for the UCF server url?

darvasip

Hi!

I assume that the ids' formats are ok.

CONFIG: JSessionID is: 4F269D3A74ED74E954007BB07D6F33ECCONFIG: uID is: 40

The UCF server address I received has another port but the same host.

I discovered that UCF connection can be established on both ports with service URL-s below.

URL url = new URL("http://hostname:8080/dfs/services/core/");

URL url = new URL("http://hostname:9080/services/core/");

Unfortunately, the same exception occurs in both cases.

Regards,

Peter

mszurap

Please use the same host and port (and context!) for the DFS and UCF calls. There may be more than one DFS server application installed on a single host and they could be on a separe JVM thus they do not share anything.

Have you tried to not to call the "registerContext()" method?

Do you use a JAX-WS based client generated from WSDL client? Please try the "official" EMC DFS SDK.