Table of Contents
Advertisement
Guidelines
When a Multi-Protocol Gateway is in SOAP mode, either on the request or
response side, it validates incoming messages against a W3C Schema that defines
the format of a SOAP message.
It is possible to customize which schema is used on a per-gateway basis by
changing this property to accommodate nonstandard configurations or other
special cases.
Examples
v Sets the URL of the SOAP schema to validate SOAP message formats to a file
ssl
Assigns an SSL Proxy Profile.
Syntax
ssl name
no ssl
Parameters
name
Guidelines
An SSL Proxy Profile specifies the SSL operational mode (client, server, or
two-way) and identifies the cryptographic resources (key, certificates, and cipher
lists) available to the SSL proxy.
The SSL Proxy Profile must have previously created with the sslproxy command.
Assignment of an SSL Proxy Profile to a Multi-Protocol Gateway is optional, unless
the Backend URL begins with HTTPS.
Use the no ssl command to remove the SSL Proxy Profile assignment.
Examples
v Assigns the SSL1 SSL Proxy Profile to the current Multi-Protocol Gateway.
v Removes the assignment of an SSL Proxy Profile.
contained in the local file space denoted as local://custom-soap-schema.xsd.
# soap-schema-url local://custom-soap-schema.xsd
#
Specifies the name of an existing SSL Proxy Profile. If not specified, the
Multi-Protocol Gateway and server exchanges are accomplished over a
nonsecure connection.
# ssl SSL1
#
# no ssl
#
Chapter 49. Multi-Protocol Gateway configuration mode
463
Advertisement
Table of Contents
