IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
  • 1.  Large Document in TN

    Posted Wed April 30, 2003 04:06 PM

    Hi- I’ve been using Large Document handling successfully in my development environment (HP-UX). When I made the changes in the production environment (Solaris), the same large docs no longer work. The document in question is 22 meg and is being sent in via HTTP post with content-type=text/xml.

    These are the settings:
    properties.cnf
    tn.BigDocTreshold=9437184
    tn.xml.xqlThreshold=65536
    tn.tspace.location=/local/webMethods/largeDocTemp
    tn.tspace.max=262144000

    server.cnf
    watt.server.keepAliveTimeout=720000

    When I query both the Production and Development BizDocContent tables, these
    are differences I can see:
    PRODUCTION has the BizDocContent.MimeType = " text/xml; charset=UTF8 "
    DEVELOPMENT has the BizDocContent.MimeType =" text/xml; encoding=UTF-8" for
    a document that is considered LARGE

    There are JVM differences:
    PRODUCTION = 1.3.1-b24
    DEVELOPMENT = 1.3.1 1.3.1.01-release-010816-13:34-PA_RISC2.0 PA2.0, mixed mode

    I ran this to determine what the encoding was set for on each machine:

    System.out.println("Default encoding: " +
    new InputStreamReader(System.in).getEncoding());

    PRODUCTION: Default encoding: ASCII
    DEVELOPMENT: Default encoding ISO8859_1

    ***Does anyone know how to change the JVM default encoding? Which file is the change done in? Is there ANYTHING else to consider?

    Thanks much for your suggestions!
    Pam


    #webmethods-Protocol-and-Transport
    #Integration-Server-and-ESB
    #webMethods