HP e-CommerceXML Accelerator sa7150 - Manual (Page 27)

C H A P T E R 3 XML Operations
17
• Which XML elements, attributes, or text and HTTP fulfillment
locations contained or identified in the anticipated XML traffic
should be used for XML pattern matching?
• Which servers will be assigned the XML patterns that you
create?
• Do you intend to use the SA7150’s SSL capabilities?
General Considerations
Some general facts to keep in mind concerning XML operations with
the current version of the SA7150 are listed below. These facts do not
apply to SSL operations.
• The SA7150 uses an abbreviated version of the XPATH syntax.
• The SA7150 works with any XML application the supports XML
1.0 and that is transported via HTTP or HTTPS POST request
methods.
• Transport protocols other than HTTP and HTTPS such as FTP
and SMTP are not supported.
• Content of incoming documents must be of type “text.”
• URL encoding is supported.
• Base64 encoding is not supported.
• The complete XML data stream must be encapsulated in the
body of the HTTP(S) POST request.
• Multi-part MIME messages are not supported.
• The first character of the POST request’s body must be the “less
than” (<) character; the final character must be the “greater than”
(>) character.
Server Mappings
Because the SA7150’s purpose is to send XML messages with
specific content to specific servers, it must be configured to recognize
these servers. This configuration is managed through the use of
“server mappings.” A server mapping consists of three items:
• A server’s IP address
• Network port
• Server port