wm.tn.doc:handleLargeDoc

Submits an inputStream to Trading Networks through a content handler so that the pipeline is formatted as if the inputStream had been submitted by an external client.

Input Parameters

inputStream	Object The inputStream to submit to Trading Networks.
content-type	String The content-type of the inputStream. The value can be a standard content type, such as text/xml or image/gif, or a custom type. The content-type should be a content type for which a content handler has been registered with Integration Server.
content-length	String The length of inputStream.

Output Parameters

None.

Usage Notes

The output of the wm.tn.doc:handleLargeDoc service varies depending on the value of the following:

The content-type variable

The Content Handler registered to handle that type of content

The length of the content specified in the content-length variable

For example, if the content-type is text/xml and no custom content handler has been registered for that type, the built-in Trading Networks XML content handler is used to format the pipeline. In this case, if the length is less than the value of the tn.BigDocThreshold system property, the pipeline will contain a variable of type com.wm.lang.xml.Document, named node. If the length is greater than or equal to tn.BigDocThreshold, the pipeline will contain a variable of type com.wm.util.tspace.Reservation, named $reservation.

Any items that are in the pipeline when the wm.tn.doc:handleLargeDoc service is invoked will also be included in the pipeline that is produced by this service.

This service is useful when you have a facility running within the Integration Server that needs to send a document into Trading Networks. Without this service, you would use the pub.client:http service to create a connection to Integration Server and transmit the document that way. It is much more efficient to invoke this service to format the pipeline, invoke wm.tn:receive, wm.tn.doc:routeXml, or wm.tn.doc:routeFlatFile.