nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Problem with Import XML for a Blog..

Chandra_Sekhar_Saripaka

I am running with a Problem during the Import XML for a Blog. I do not know whether to post it here or not. I am able to do the XML Import Perfectly using the URL Approach. But, for my approach I need to do that with the ESWS API. I have Obtained Context of the Community Folder (I got the COntext ID )in which I have to import the XML OBJECT. I am using the ContentService MTOM CLient to Upload the COntent of the XML File. The issue here is , blog is getting created, but its is throwing an Exception.

I am sending the snippet of code:

//ImportXMLContent Requires the Parameters to be Parent ID and Import Options.

String contextID = getXmlService(authToken).importXmlContext(parentNodeId, impOptions);

ContentService fContent = getContentService();

WebServiceUtil.setSoapHeader((WSBindingProvider) fContent, authToken, contextID, fileAtts);

fContent.uploadContent( new DataHandler(new FileDataSource(uploadFile)));

Exception :

javax.xml.ws.soap.SOAPFaultException: ContentService.UploadContent() failed on the Livelink Server. No results were returned. Check the Livelink Server thread logs.

at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188)

at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:116)

at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119)

at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89)

at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)

at $Proxy39.uploadContent(Unknown Source)

Expecting a help from you guys..

Thanks,

Chandra.

Find more posts tagged with

Comments

sgrasley

Hi, Chandra.

It looks like an error is occurring on the Livelink side, most likely a stack crawl. Can you provide information from the relevant thread log (ensure that Debug=2 is set in the opentext.ini) as well as any trace files that are generated?

Also, can you confirm that you're using LES 9.7.1?

Thanks,

Scott

Chandra_Sekhar_Saripaka

HI Scott,

Sorry for the late Reply . I am attaching the thread log , the code and the imported xml. Kindly verify this issue and I am unable to import the Blog XML either.

Thanks,

Chandra.

LL_exported.zip

Chandra_Sekhar_Saripaka

Here is the trace File too.. that got generated.

trace5-1255356405.out

Kyle_Swidrovich

Hi Chandra,

Two comments here…

<![if !supportLists]>1) <![endif]>Importing a blog must be done through the specialized communityinterface (function menu) and not through standard XML import means. TheXML is treated differently in that case, so you need to use the GUI.

<![if !supportLists]>2) <![endif]>From a cursory analysis of the trace file, it looks like yourimport file is 6.2 GB. That’s excessively large and will mostlikely fail during an import attempt.

Unfortunately, I can’t think of agood way to do this without having to write specialized OScript code that runsdirectly on the Content Server instance.

-- Kyle

From: eLink Entry:Enterprise Web Services 9.7.1 Forum[mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, October 13, 20098:13 AM
To: eLink Recipient
Subject: Problem with Import XMLfor a Blog..

Problem with Import XML for a Blog..

Posted by csiripak (Siripaka, Chandra Sekhar) On 2009/10/12 10:22

Here is the trace File too.. that got generated.

Attachment Links:

trace5-1255356405.out (88 KB)

[To post a comment, use the normal reply function]
Topic:	Problem with Import XML for a Blog..
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

sgrasley

This trace file is due to a problem converting from a long to an integer. Trying using a (much) smaller file for your import.

Thanks,

Scott

Hans Stoop

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

It will always be possible to create your own webservice in the enterprise server that does the same OScript calls as are done via the GUI interface.

Hans

From: eLink Entry: Enterprise Web Services 9.7.1 Forum [mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, October 13, 2009 4:06 PM
To: eLink Recipient
Subject: RE Problem with Import XML for a Blog..

RE Problem with Import XML for a Blog..

Posted by kswidrov (Swidrovich, Kyle) On 2009/10/13 10:05

Hi Chandra, Two comments here… <![if !supportLists]>1) <![endif]>Importing a blog must be done through the specialized community interface (function menu) and not through standard XML import means. The XML is treated differently in that case, so you need to use the GUI. <![if !supportLists]>2) <![endif]>From a cursory analysis of the trace file, it looks like your import file is 6.2 GB. That’s excessively large and will most likely fail during an import attempt. Unfortunately, I can’t think of a good way to do this without having to write specialized OScript code that runs directly on the Content Server instance. -- Kyle From: eLink Entry: Enterprise Web Services 9.7.1 Forum [mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, October 13, 2009 8:13 AM
To: eLink Recipient
Subject: Problem with Import XML for a Blog.. Problem with Import XML for a Blog..

Posted by csiripak (Siripaka, Chandra Sekhar) On 2009/10/12 10:22

Here is the trace File too.. that got generated.

Attachment Links:

trace5-1255356405.out (88 KB)

[To post a comment, use the normal reply function]
Topic:	Problem with Import XML for a Blog..
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

[To post a comment, use the normal reply function]
Topic:	Problem with Import XML for a Blog..
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

Chandra_Sekhar_Saripaka

Hi Everyone,

Thank you for the response. This issue is because of the file Size. However, I am not importing a file of 6.2 GB Size , but the file Size from the file Attributes Header as a part of SOAP Header is going there as Long Value : L5136322560. So, I corrected this problem. and so now I am able to import the Blog, With the same Exception Still Existing.. { UploadContent() failed . No Results are Returned. Please Check the Server Thread Logs.}.. However I have one more trace file attached for you. Now the dataFork Size is: 3953.

I am attaching the trace and thread log for you.

Thanks,

Chandra.

trace3-1255488095.txt

Kyle_Swidrovich

Hello Chandra,

As I previously mentioned, blogs must beimported through the GUI unless you write your own web service extension toreplicate the import operation seen in the GUI.

The trace file is being generated becausethe “request” is seen as undefined.

I do not have a communities system readilyavailable to me to look into this further; however, I suspect that the requestwould be populated with a GUI request but not with an API request.

-- Kyle

From: eLink Entry:Enterprise Web Services 9.7.1 Forum[mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: Tuesday, October 13, 200911:23 PM
To: eLink Recipient
Subject: RE RE Problem with ImportXML for a Blog..

RE RE Problem with Import XML for a Blog..

Posted by csiripak (Siripaka, Chandra Sekhar) On 2009/10/13 23:20

Hi Everyone,

I am attaching the trace and thread log for you.

Thanks,

Chandra.

Attachment Links:

trace3-1255488095.txt (33 KB)

[To post a comment, use the normal reply function]
Topic:	Problem with Import XML for a Blog..
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

Chandra_Sekhar_Saripaka

Hi Kyle,

I am still able to import the Blog through the Service based approach. Using the Xml Service and the Content Services.. Can you clarify something if we could use the Content-Servlet which is also available with the les-services to import the Blogs. Is it a feasible option.We cant have a GUI based processing for our execution, as it ishould be more or less a service based call..which talks between 2 different systems. So, if you can direct me to the relevant articles of writing a new webservice or writing through a specialized Oscript, it would be nice [We dont have any knowledge on Oscript ]. If you can try to bring out a certification on any Service for importing the Blog XML would be great enough.

Thanks,

Chandra.

sgrasley

Hi, Chandra.

The Content Servlet is basically another mechanism for accessing the ContentService, so you'll see the same behaviour.

I think to pursue this further would require some effort from the Content Server Solutions team that deals with CoP.

Thanks,

Scott

Kyle_Swidrovich

Hi Chandra,

There’s no Enterprise Web Servicesextension that I’m aware of to support manipulation of Communitiesobjects (blogs, wikis, etc.)

Unfortunately, it will requireconsiderable OScript knowledge to implement a new extension to EWS to supportimporting blogs programmatically.

If you’re looking for a samplewalkthrough, please feel free to check out the Programming portion of thedocumentation, also posted here on OTDN:

https://knowledge.opentext.com/knowledge/llisapi.dll/open/15627559

Regards,

_________________________________________

Kyle Swidrovich

Principal Search / SDK Product Specialist
Livelink Escalations Support Team
Open Text Corporation

275 Frank Tompa Dr.
Waterloo, ON, CANADA

Phone : +1-800-540-7292
Online: http://support.opentext.com
_________________________________________

From: eLink Entry:Enterprise Web Services 9.7.1 Forum[mailto:otdnenterprisewebservices971forum@elinkkc.opentext.com]
Sent: Wednesday, October 14, 20095:17 AM
To: eLink Recipient
Subject: RE RE RE Problem withImport XML for a Blog..

RE RE RE Problem with Import XML for a Blog..

Posted by csiripak (Siripaka, Chandra Sekhar) On 2009/10/14 05:13

Hi Kyle,

Thanks,

Chandra.

[To post a comment, use the normal reply function]
Topic:	Problem with Import XML for a Blog..
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

Chandra_Sekhar_Saripaka

Hi, Kyle & Scott, thanks for the response.

To Kyle: Well I have just started looking at the link you have sent..

ThankYou,

Chandra.