VB.NET to download or upload files

I cannot locate anything besides C# or Java examples for connecting to the webservices.

I have been able to authenticate my Admin user and use the token to connect via the DocumentManagement objects (that were added as a web reference and then imported into the module) to get a list of all the files and folders for the Admin user. What is not clear is how one is to go about downloading or uploading a file. I assume it has something to do with ContentService, but I cannot find any useful examples for this.

Can anyone point me in the proper direction? Thanks in advance.

Find more posts tagged with

Comments

sgrasley

Uploading and Downloading content is described in the Client Guide, although the examples are somewhat limited. There are no VB.NET examples.

I think you'll have better luck if you use a Service Reference instead of a Web Reference if you want to stream documents using the ContentService service.

Thanks,

Scott

sgrasley

I should also point out that the examples in the Client Guide are using WCF proxies (i.e. Service References).

Scott

Darko_Poletto

The problem with that is I need to integrate your services into a web application. The only way to use service references is with a desktop app. Going that route would mean I would have to create a seperate application that would have to use socket technology to listen for request from the web app.

I have been able to download a file using web references and the DocumentManagement structure. When I try and upload a file using the same structure I get the error "Error adding version to 'Test1.txt'".

Quoted Scott Grasley (sgrasley) on 2010/01/26 13:21:

Uploading and Downloading content is described in the Client Guide, although the examples are somewhat limited. There are no VB.NET examples.

I think you'll have better luck if you use a Service Reference instead of a Web Reference if you want to stream documents using the ContentService service.

Thanks,

Scott

Kyle_Swidrovich

Hello Darko,

In Visual Studio 2008 you can definitelyadd a service reference to a VB Web Application project.

I suspect you’re using an olderversion of VS without WCF extensions. It wasn’t until .NET 3.0 thatnative WCF support was introduced.

Please try again with VS 2008 and let usknow if you’re able to add the reference to your project.

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: Tuesday, January 26, 201012:23 PM
To: eLink Recipient
Subject: VB.NET to download orupload files 2

VB.NET to download or upload files 2

Posted by dpoletto@skeinc.com (Poletto, Darko ) On 2010/01/26 12:21

Quoted Scott Grasley (sgrasley) on 2010/01/26 13:21:

Uploading and Downloading content is described in the Client Guide, although the examples are somewhat limited. There are no VB.NET examples.

I think you'll have better luck if you use a Service Reference instead of a Web Reference if you want to stream documents using the ContentService service.

Thanks,

Scott

[To post a comment, use the normal reply function]
Topic:	VB.NET to download or upload files
Forum:	Enterprise Web Services 9.7.1 Forum
Livelink Server:	knowledge-wlweb01

Darko_Poletto

I was not aware of this. I will try this on a 2008 dev machine and post results. Thanks

Darko_Poletto

I have VS 2008 up and running (after a failed attempt on a 2008 Server VM, but that a different story).

The line where you are retrieving a contextID: "contextID = dmService.AddVersionContext( otAuth, doc.ID, null ); " what does the doc.ID represent? Is this the ID of an already existing document? If so, how would you go about uploading a document that doesn't already exist in the system?

sgrasley

Hi, Darko.

I think the CreateDocumentContext method is the one you're looking for. You pass it information about the document you want to create and details about the file you're going to upload, then call ContentServer.UploadContent with the context ID.

Thanks,

Scott

Darko_Poletto

At some point in time this morning I was able to upload a file. I'm not sure yet which piece of code performed it since the service is always timing out on the livelink server. The error that I get is "The request channel timed out while waiting for a reply after 00:01:00. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.".

I am only trying to upload a 4kb text file. Any thoughts?

Darko_Poletto

It is the CreateDocumentContext that allows for the UploadContent to work when creating a new doc. Still having the timeout issue though. Nothing seems obvious as to why that is occuring.

sgrasley

Hi, Darko.

It might be worth checking the Livelink thread logs to see if there is anything useful there. You should see the web service requests in those logs (assuming the logs are enabled).

Thanks,

Scott

Darko_Poletto

I have sent log files from the "failed" upload to support. The tech said that the logs show that the file is uploaded in about 1 second, there are no errors and that the db requests are all successful as well. The tech said that the issue lies within the .NET Framework and that it is not supported by them.

We have made a slight breakthrough with this issue this morning. If the application is run on the machine that has livelink installed, it works fine. It will not run from the 2008 nor the XP development machines we've tried it on though. Also of note, I can download a file through the Document Management service, but when I tried to download the same one through the Content Service, it timed out. Something with the Content Service is being stubborn for both uploads and downloads.

Thoughts?

Quoted Scott Grasley (sgrasley) on 2010/02/09 12:45:

Hi, Darko.

It might be worth checking the Livelink thread logs to see if there is anything useful there. You should see the web service requests in those logs (assuming the logs are enabled).

Thanks,

Scott

Ferdinand Prantl

I would try to compare application.config, web.config and machine.config files on both machines - according to in which context your application runs. There can be some difference especially under the system.web section. (We had a problem with proxy settings for Internet Explorer which are taken in account by default unless turned off in the web.config, for example.)

You can also turn on verbose logging in for System.Net.Socket to learn what happens at the socket level in the .NET framework.

--- Ferda

Darko_Poletto

I will check those over later today. Thanks for the input

Quoted Ferdinand Prantl (ferdipr) on 2010/02/10 11:59:

You can also turn on verbose logging in for System.Net.Socket to learn what happens at the socket level in the .NET framework.

--- Ferda

Darko_Poletto

There are no differences between the config files. There is either some small setting I am missing, or there is a flaw in the livelink services.

Ferdinand Prantl

Hmm, if comparison of the configuration did not help, maybe verbose logging could say more. As long as both sides (client and server) use the MS .NET framework for the network communication, it is possible to turn network logging on both sides. Microsoft utilizes the System.Diagnostics funtionality you are probably familiar with already. If you put the following element under the <configuration> root in your application/web config, you will be able to trace everything what is happening on the sockets:

<system.diagnostics>

<add name="SystemNetLog" type="System.Diagnostics.TextWriterTraceListener"

initializeData="C:\System.Net.log" traceOutputOptions="DateTime,ProcessId,ThreadId" />

</sharedListeners>

</switches>

</listeners>

</source>

</listeners>

</source>

</listeners>

</source>

</listeners>

</source>

</sources>

</system.diagnostics>

Browsing big logs can take some time but you can control the log verbosity by turning on just specific trace switches. (This helped me to solve the problem with automatic proxy redirections which was not visible from the API level.)

--- Ferda