Table of Contents
Advertisement
Appendix B. Processing Policy procedures
Stylesheet policies can be created using two slightly different methods. The first
method (referred to as the inline rule method) initially creates the processing policy
and then defines transformation and filtering rules specific to that policy. The
second method (referred to as the global rule method) initially defines
transformation and filtering rules that are available to all stylesheet policies. These
global rules are later associated with a Processing Policy during its creation.
Stylesheet policies using inline rules
Use the following procedure to implement a Processing Policy using inline rules.
1. Use the matching command to enter Matching Rule configuration mode and to
2. Use the urlmatch or httpmatch command to populate matching rules with
3. Use the Global stylepolicy command to create a Processing Policy and enter
4. For XML Firewall services only, use the request-rule, response-rule, or rule
5. For both XML Firewall and XSL Proxy services, use the request-rule,
6. Use the stylesheet-policy command (XML Firewall and XSL Proxy) to associate
© Copyright IBM Corp. 1999, 2008
create a named matching rule or rules.
shell-style match patterns. The URL or HTTP match patterns specify the
conditions under which policy-based XSL filtering or transformation will be
performed.
You can use wildcards to define a match pattern as follows:
The string wildcard matches 0 or more occurrences of any character.
*
?
The single character wildcard matches one occurrence of any single
character.
[]
The delimiters bracket a character or numeric range:
Matches 1, 2, 3, 4, or 5
[1-5]
Matches x or y
[xy]
Processing Policy configuration mode. You can also use the stylepolicy
command to specify a default style sheets used for SOAP filtering and XSL
transformations of candidate documents that fail to match Processing Policy
rules.
commands in conjunction with the filter and validate actions to add
direction-specific filters to the Processing Policy. Filters (which result in an
accept or reject decision) enable validation of an XML document against a
specified schema, verification of a document's digital signature, or
content-based XML/SOAP filtering.
Each filtering rule references a named matching rule (created in Steps 1 and 2).
If the candidate URL or HTTP header matches a pattern in the matching rule,
XSL filtering is immediately performed as defined by the rule.
response-rule, or rule commands in conjunction with the xform and xformpi
actions to add direction-specific transformation rules to a Processing Policy.
Each transformation rule references a named matching rule (created in Steps 1
and 2), and defines a transform procedure. If the candidate URL or HTTP
header matches a pattern in the matching rule, XSL transformation is
immediately performed as defined in the rule.
the Processing Policy with either an XML firewall or an XSL proxy.
999
Advertisement
Table of Contents
