Can we write DFS custom code (using productivity layer) using java1.4

karthik.b.venkatarama

Hi,

I have created a custom code which consumes the existing objectservice utilities provided in DFS 6.5 sp2 and jdk 1.5, this

works fine.

Since there are some environment issues, and this custom code needs to be used by application which is on jdk 1.4, I want to

know if I will be able to write a DFS code (using productivity layer ) using jdk 1.4.

Can anyone answer this please as this is urgent.

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

FabianLee-EMC

The initial question has been resolved. Go ahead and mark this thread answered and create a new thread if you want to ask another question.

All comments

FabianLee-EMC

You must have Java 1.5 to use the productivity libraries, if you must stay at Java 1.4 you might want to consider using an older version of Axis to generate the client proxies.

karthik.b.venkatarama

Hi,

Thanks for the reply...

Intially i created a dfs code as per our requirements which makes use of objectservice, queryservice, contentdeliveryservice etc...using DFS productivity layer with JDK 1.5 and this is working perfectly fine.

Since I have a requirement to create a custom DFS using JDK1.4, I am facing issues while using the same code after some changes during runtime (major minor version problem).

In the manual they have mentioned if we need to use DFS in environments lower than JDK 1.5 then we need to do it without using DFS productivity layer (WSDL -axis2 or JAXWS).

I tried generating wsdl proxies with axis2 jars (jdk 1.5 environment and jdk 1.4 environments) but facing issues when trying to use the "AxisDfsConsumer.java" code provided in DFS samples as there are some method signature problems.

Using JAX - tried what ever was mentioned in the site "https://community.emc.com/docs/DOC-3038;jsessionid=0C153F69106D8AFED27607ABC1079388" and this is working fine with JDK 1.5 but not with 1.4.

Can you please suggest me how to consume DFS services using axis2 or JAX-WS on JDK 1.4 environment.

I tried with axis1 jars as well which was similar to the one which existed on 5.3 webservice frame work but not finding a proper code to use it as the stubs generated are different from the 5.3 environment and confused with the method calls.

Can you please suggest me how to go about this.

FabianLee-EMC

For JAX-WS you are going to need Java 1.5. Try using Axis 1.4.

karthik.b.venkatarama

Hi,

I tried generating wsdl proxies using the jars mentioned below :

commons-discovery-0.2.jar
axis-1.4.jar
commons-logging-1.0.4.jar
jaxrpc.jar
log4j-1.2.8.jar
saaj.jar
wsdl4j-1.6.1.jar

java org.apache.axis.wsdl.WSDL2Java http://epsun006:9080/services/core/runtime/ContextRegistryService?wsdl
java org.apache.axis.wsdl.WSDL2Java http://epsun006:9080/services/core/SchemaService?wsdl
java org.apache.axis.wsdl.WSDL2Java http://epsun006:9080/services/core/ObjectService?wsdl

I have attached the generated proxies "axis1.4_wsdl.rar", Iam trying to use the scheme service but facing authorisation error as mentioned below, can you please let me know how to set the SOAP header if Iam using AXIS1.4 jars ::

I have also attached the code used to consume the service "TestService.java"

#####################################

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Authorization failed, could not find identities in service context with token "temporary/127.0.0.1-1256639785291--744204631585623572"
faultActor:
faultNode:
faultDetail:
{http://rt.fs.documentum.emc.com/}SerializableException:<exceptionBean><attribute><name>messageId</name><type>java.lang.String</type><value><value>E_SERVICE_AUTHORIZATION_FAILED_NO_IDENTITIES</value></value></attribute><attribute><name>messageArgs</name><type>[Ljava.lang.Object;</type><value><value><item xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xsi:type="xs:string">temporary/127.0.0.1-1256639785291--744204631585623572</item></value></value></attribute><exceptionClass>com.emc.documentum.fs.rt.AuthenticationException</exceptionClass><genericType>java.lang.Exception</genericType><message>Authorization failed, could not find identities in service context with token "temporary/127.0.0.1-1256639785291--744204631585623572"</message><messageId>E_SERVICE_AUTHORIZATION_FAILED_NO_IDENTITIES</messageId></exceptionBean><message>Authorization failed, could not find identities in service context with token "temporary/127.0.0.1-1256639785291--744204631585623572"</message>

Authorization failed, could not find identities in service context with token "temporary/127.0.0.1-1256639785291--744204631585623572"

#########################################

FabianLee-EMC

We've been through this several times on the EMC Support Forums:

http://forums.emc.com/forums/thread.jspa?threadID=75235

http://forums.emc.com/forums/thread.jspa?threadID=65362

karthik.b.venkatarama

Hi Fabian,

Thanks for the reply, this was very helpful.

I was able to write a code to createfodlers and objects using the object service.

I have attached the code which i used for testing the services.

But Iam facing issues while setting up the folder relationships and using query services, can you please tell me where Iam going wrong below is the code snippet::

############# Query service ###############

String[] repoName= new String[1];
                    repoName[0] = docbase;
                    PassthroughQuery query = new PassthroughQuery();
                    String objectQuery = "select r_object_id from dm_sysobject where object_name='" + o.getObjectName() + "' and folder('" + o.getFolder() + "')";
                    query.setQueryString(objectQuery);
                      System.out.println("QUERY :: "+objectQuery);
                    query.setRepositories(repoName);

                    QueryExecution queryEx = new QueryExecution();
                    queryEx.setCacheStrategyType(CacheStrategyType.DEFAULT_CACHE_STRATEGY);

                    QueryServiceLocator querySvcLocator=new QueryServiceLocator();
                    QueryServicePortBindingStub queryStub= (QueryServicePortBindingStub)querySvcLocator.getQueryServicePort();
                    queryStub.setHeader(new SOAPHeaderElement(ele));

                    OperationOptions operationOptions = null;
                    QueryResult queryResult = queryStub.execute(query, queryEx, operationOptions);

                    DataPackage resultDp = queryResult.getDataPackage();
                    DataObject[] dataObjects = resultDp.getDataObjects();

                    int numberOfObjects = dataObjects.length;

                    if(numberOfObjects > 0 ){
                        exists = true;
                        info.setErrorCode(1);
                        info.setError(o.getObjectName() + " is already in " + o.getFolder() + ". Please be sure to use a unique file name.");
                        IDs[i] = info;
                        log.warn(o.getObjectName() + " is already in " + o.getFolder() + ".");
                    }

#################### setting up folder relationship ################

try {
                            ObjectPath objectPath = new ObjectPath();
                            objectPath.setPath(o.getFolder());
                            System.out.println("Object Path :: "+objectPath.getPath());
                            ObjectIdentity folderIdentity = new ObjectIdentity();
                            folderIdentity.setObjectPath(objectPath);
                            folderIdentity.setRepositoryName(docbase);
                            System.out.println("FOLDER IDENTITY ::"+folderIdentity.getObjectPath().getPath());

                            ReferenceRelationship folderRelationship = new ReferenceRelationship();
                            folderRelationship.setName("folder");
                            folderRelationship.setTarget(folderIdentity);
                            folderRelationship.setTargetRole("parent");

                            System.out.println("Relationship :: "+folderRelationship.getTarget().getObjectId().getId());
                            relationship[0] = folderRelationship;
                        } catch (Exception e) {
                            e.printStackTrace();
                        }

                        log.debug("Now setting the object content ");
                        BinaryContent[] binContent = new BinaryContent[1];
                        dataObject[0] = mydataObject;
                        binContent[0] = getBinaryContent(binaryData, o.getContentType());
                        dataObject[0].setContents(binContent);
                        dataObject[0].setRelationships(relationship);
                        dataObject[0].setType(o.getObjectType());
                        dataPackage.setDataObjects(dataObject);
                        dataPackage.setRepositoryName(docbase);

########## error occured :::

AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server
faultSubcode:
faultString: Failed to read a response: javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: Unable to create an instance of com.emc.documentum.fs.datamodel.core.Relationship
- with linked exception:
[java.lang.InstantiationException]]
faultActor:
faultNode:
faultDetail:
    {http://xml.apache.org/axis/}stackTrace:Failed to read a response: javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: Unable to create an instance of com.emc.documentum.fs.datamodel.core.Relationship
- with linked exception:
[java.lang.InstantiationException]]
    at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
    at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
    at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
    at weblogic.apache.xerces.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:585)
    at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleEndElement(XMLNamespaceBinder.java:898)
    at weblogic.apache.xerces.impl.XMLNamespaceBinder.endElement(XMLNamespaceBinder.java:644)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1008)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1469)
    at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
    at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
    at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
    at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
    at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
    at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:138)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
    at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
    at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
    at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
    at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
    at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
    at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
    at org.apache.axis.client.Call.invoke(Call.java:2767)
    at org.apache.axis.client.Call.invoke(Call.java:2443)
    at org.apache.axis.client.Call.invoke(Call.java:2366)
    at org.apache.axis.client.Call.invoke(Call.java:1812)
    at com.emc.documentum.fs.services.core.ObjectServicePortBindingStub.create(ObjectServicePortBindingStub.java:1048)
    at com.supervalu.ecm.service.ObjectService.importObject(ObjectService.java:390)
    at com.emc.documentum.tst.DAMSystemWrapper.main(DAMSystemWrapper.java:119)

FabianLee-EMC

The initial question has been resolved. Go ahead and mark this thread answered and create a new thread if you want to ask another question.

dijap

I'm faced with exactly the same problem, I can't get my Axis 1.4 webservice client running in a 1.4 JVM to work with the DFS. The URL's posted at 27-Oct-2009 10:36 are broken, is there any other information how to get this thing working? Preferably including a working sample.

DavidHaveman

Anyone have any updates on this? The links posted on Oct-27th are still dead..

Thanks,