HP P4518A - Traffic Management Server Sa7150 How to use

hp e-commerce/
xml
server accelerator
sa7150
release notes

© Copyright 2001 Hewlett-Packard Company. All rights reserved.
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304-1185
Publication Number
5971-3005
March 2001
Disclaimer
The information contained in this document is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY
KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or consequential damages
in connection with the furnishing, performance, or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its
software on equipment that is not furnished by Hewlett-Packard.
Warranty
A copy of the specific warranty terms applicable to your Hewlett-Packard
products and replacement parts can be obtained from
http://www.hp.com/serverappliances/support.
*Other brands and names are the property of their respective owners.
A54704-001


HP e-Commerce Server Accelerator SA7150
1
Known Issues
SA7150 SNMP support is read-only
SNMP support on the SA7150 is intended for monitoring purposes
only and cannot be used for configuration. Attempts to write to MIBs
result in write failures and errors returned to the SNMP agent.
The SA7150 cannot test root element data in XML
patterns.
For example, given <e1>abc</e1> No pattern exists that allows you
to test [e1="abc"]. The SA7150 requires that the filter expression
([e1="abc"]) be preceded by a path expression, however no such
expressions are effective in this context (e.g., /, //, /*, //*, /e1, and //
e1.)
Remote service ports can be set to port numbers
used by other services.
When all remote services are enabled (telnet, ssh, snmp, traps) it is
possible to configure ports in such a way that services conflict.
User Guide: Command Line Reference entry,
p. 96, setsnmp snmp enable | disable command
needs additional information
An IP address and a netmask must be assigned to the device before
SNMP can be enabled. If these are unassigned when you attempt to
enable SNMP, the device will prompt you for them before allowing
you to proceed. The CLI Reference entry on page 96 of the
HP e-Commerce/XML Server Accelerator SA7150 User Guide
should have included a reference to this fact.
CAUTION: When you
assign an IP address to
the SA7150 (a
requirement if you intend
to use SNMP) the device
becomes visible on the
network. Be sure to
consider security issues
when you assign an IP.
Syntax:
Intel SA7150> setsnmp snmp enable
Need an IP address to start SNMP service.
Enter IP Address [10.1.2.65]: 1.1.1.0
Need a netmask to start SNMP service.
Enter Netmask [255.255.255.0]:
Optional Default Route to start SNMP service.
Enter Default Route (’none’ to delete) [none]:
SNMP Service started.
Intel SA7150>

Release Notes for Version 2.4.1.0.24
2
User Guide: summary of XML parsing
Chapter 3 of the HP e-Commerce/XML Server Accelerator SA7150
User Guide, “Theory of Operations,” should contain the following
summary outlining how the SA7150 parses incoming XML
documents:
1. MAP intercepts HTTP requests, receives the entire request and
replaces “Connection: Keep-Alive” with “Connection: Close” (if
it exists.)
2. If the request is not an HTTP POST or if XML is disabled for the
MAP, the request goes to the mapped server.
3. If the request is an HTTP POST and XML is enabled, the
SA7150 parses the POSTed document. If the document is not
XML, the request goes to the mapped server.
4. If any portion of the document is malformed:
• If the command xml_well_formed is set to enable, a 403
error (“POSTed data was not well-formed.”) is returned.
• If the command xml_well_formed is set to disable, the
request goes to the mapped server.
5. The parser extracts the URI from the request’s URL.
6. The extracted URI is compared to the URI expression of each
XML pattern for each XML server in order. If a match is found,
the parser then compares the XML expression portion of the
XML pattern to the document.
7. If both parts of an XML pattern (URI expression and XML
expression) on an XML server match the request, then the
request goes to that server.
8. If only the URI expression matches and an XML pattern using
the keyword default as the XML expression has been created for
a server for the matching URI expression, then the request goes
to that server.
9. If an XML pattern with the keyword default has not been created
for a server for the matching URI expression then the request
goes to the mapped server.