Configuring Large Document Handling

5. Go to the Integration Server_directory \instances\instance_name\config directory, open the server.cnf file, and update the properties listed below.

Set the watt.server.tspace.location property to the absolute directory path to the hard disk drive space in which to temporarily store large documents. The directory you specify is on the same machine as the host Integration Server. Examples are watt.server.tspace.location=D:\LargeDocTemp for Windows, or watt.server.tspace.location=/opt/webmethods/ for UNIX. If you do not set this property, Trading Networks uses the Java system property java.io.tmpDir, which defaults to the value of the environment variable Temp on most operating systems.

Note:

In a clustered environment, each Integration Server must have its own tspace location. Do not share the tspace location.

If you are setting up large document handling for multiple webMethods products, all products use this property. Integration Server manages the allotment of space to each product.

Each file stored in this directory is given the name DocResxxxxx.dat, where xxxxx can vary in length and character.

Set the watt.server.tspace.max to the maximum number of bytes to store at any one time in the hard disk drive space defined on the watt.server.tspace.location property. If Trading Networks (or another webMethods product) tries to write a large document to the hard disk drive space that will cause the specified number of bytes to be exceeded, an error message is displayed on the Integration Server console and the document is not stored. Specify a positive integer in bytes. The default is 52,428,800 bytes (50 MB).

If you are setting up large document handling for multiple webMethods products, all products use this property. The Integration Server makes sure the hard disk drive space used for all products does not exceed the value you specify.

Note:

The size of the hard disk drive space for temporarily saving documents varies based on the number of documents you process concurrently and the size of the documents you process. For example, if your typical concurrent document load is 10, you would need a hard disk drive space that is 10 to 15 times the combined size of the documents being processed concurrently.

When you submit a document using a Java InputStream over a network to Integration Server, Integration Server makes a request to read from a network InputStream. Set the watt.server.keepAliveTimeout property to the number of milliseconds Integration Server should wait for a response. If Integration Server does not receive a response in the specified amount of time, it times out with the error Connection reset by peer. Specify a positive integer in milliseconds. Software AG recommends that you set this property to 180000 (3 minutes). The default value is 15000 (15 seconds).

Note:

The value you specify does not have to be long enough to accommodate reading the entire document, only to accommodate the length of time it takes to receive a response to a read request.

Set the watt.server.tspace.timeToLive property to the number of milliseconds to temporarily store documents in tspace. Setting this property prevents the deletion of a document as soon as it is created, thus preventing any resulting exceptions that occur when you try to read back from the document. For example, if you want to delete the documents from tspace three minutes after they are created, set this property to 180000 milliseconds.

The default value 0 tells Integration Server to delete documents from tspace only after creating a document in tspace. For example, if tspace contains 10 documents and this property is set to 0, Integration Server deletes the 10 documents only after it creates a document.