Passing a document type as input to pubclienthttp

, ,
1

Hi,

I want to pass a document to pub.client:http service.
Can anyone tell me how to do this?

Thanks
ramesh

2
  1. Use pub.xml:documentToXMLString to convert your doctype to an XML string, []set the content-type of your HTTP post to “text/xml”, by using the pipeline editor to add a text variable called “content-type” to the headers document type and setting its value to “text/xml” []map the xmldata variable created in Step 1 to the \Data\string input parameter of the pub.client:http service

Mark

3

Mark,

Thanks a ton.that helped me.
i was trying to add a doctype variable under Data and was trying to map my doc to this variable.i was wrong.

ramesh

4

Mark,

I’m getting the following exception sometimes:
error---- com.wm.net.NetException: [ISC.0064.9314] Authorization Required: Invalid Session ID or Session Expired
errorType---- com.wm.app.b2b.server.ServiceException

i’m passing authorization variable as Administrator/manage,even then it is throwing this error.
Can you throw some light on this?

Thanks
ramesh

5

Hi,

I tried to relogin into the Integration Server and changed the session timeout period.this helped me solve the problem.

Thanks
ramesh.

6

Ramesh,

Your remote session has probably expired.

You can set the following extended setting:
watt.net.useCookies=false
To turn off the use of cookies.

Unfortunately, this is a server-wide config setting, and so if you WANT to issue multiple http requests in the same session, this is a problem.

It would be nice for pub.client:http to offer a cookie lifetime parameter, eh?

7

Mark,

Yes, i do issue multiple http requests in the same session.
so, what is the solution for this problem?
i think even if we change the session timeout period, what i did right now, will not help.
once in production we cant relogin to IS always.

ramesh.

8

Session timeout seems to be one of those configuration settings that vary from server to server (i.e. webLogic, webSphere, Tomcat, etc.) Some severs differentiate between an idle timeout, and a connect limit from the time of login.

If all you are dealing with is an idle timeout, I suppose that you could ‘ping’ the remote server on a regular basis to prevent an idle timeout.

Still not an ideal solution because you probably want the session to die at some point.

Needless to say… you could bypass pub.client:http and write your own Java code to control http client sessions (and therefore the use of cookies) on your own.

Anyone else have any ideas how to deal with this?