Error adding document (LAPI Java)

[awiesauer]

Hello,

I always get an error when uploading a document to livelink (using a File, not an InputStream): "Server does not respond, maybe Livelink could be down".

Other LAPI methods work fine, like listObjects or GetObjectInfo, which are called before addDocument.

The application runs within Tomcat (it's a webapp for Livelink). We use a secure, tunnelled connection (HTTPS).

Thanks for your help!
Andy

 

[appnair]

if you are the same person having problems with LAPI and siteminder,I would advise you to see if you can add documents as the Admin user,not thru tunneling and see how it fares.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[awiesauer]

No that was not me.

I can't try it without tunneling, because this is prevented by a firewall.

 

[appnair]

Sorry about that.
Can you get a file from livelink using the FetchVersion stuff.Are you making a call to the livelink web server(usually 80) or to the livelink appserver(usually 2099)
What is the file's upload path on the livelink server.Does this lapi user have write access to that file folder.It has to otherwise how will you transfer the file.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[awiesauer]

First of all, thank you for your help.

Downloading files by using FetchVersion works perfectly. The user has the right to upload the file (write into folder).

I make the call to the webserver (80).

The error message sounds strange to me: "Server does not respond". If it would be a permission problem, the message would state this. It seems as if the server does not answer to the call.

 

[appnair]

I think you misunderstand the problem.When a user in livelink(lapi or person) has to add a file into a folder,true the user has to have livelink permissions ,but think where the physical file is coming from.It is on a server,it gets dumped into the livelink webserver's temp directory by default,or if the livelink admin has set a file upload path.Normally that is wide open.From there livelink takes over and puts it into its external file store.It is two hops into the livelink file store.
Server Did Not Respond usually means that it is an unhandled exception.Usually those things can be found by enabling logs on the livelink server with this setting
Debug=2,wantlogs=true in the ini file and re-starting the livelink server.When you get the error message you will also get a trace<nn> file which will indicate which livelink thread crashed.Sometimes it will reveal something very easy but sometimes we have to involve OT to figure out what it means.

Well, if I called the wrong number, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

 

[awiesauer]

Hello appnair,

thank for your help. It seems that the file transfer was blocked due to an cgi-configuration error. It was fixed by our administrative stuff and is working now.