Using Non-Repudiation Logging; Using Message Store - IBM E02HRLL-G - WebSphere Partner Gateway Express Administration Manual

Administration guide
Table of Contents

Advertisement

v Upload the necessary validation map to WebSphere Partner Gateway. See
v For DTD based validation, associate DTD against validation map under its
v For schema-based validation, optionally, you can associate the validation map
v While uploading schema into WebSphere Partner Gateway, use the SystemId for
v Choose the built-in action SOAP Body Validate to validate SOAP Body under
v You can optionally choose not to validate the response by setting the Response
v By enabling/disabling Content Validation routing object attribute, the content

Using non-repudiation logging

About this task
WebSphere Partner Gateway increases the configuration options for using
non-repudiation by enabling a Trading Partner or internal partner to configure it at
the package, protocol, and document flow levels. By using this configuration, you
can start or stop non-repudiation for each connection rather than stopping all the
connections.
For example, to initiate non-repudiation for an AS2 connection between a Trading
partner and a internal partner perform the following steps:
1. Create a partner connection between AS > None.
2. List the partner connection between Trading Partner and Community Manager.
3. Edit the attributes for the AS2 package setting the NonRepudiationRequired
4. Edit the attributes for the none package setting the NonRepudiationRequired
See the WebSphere Partner Gateway Hub Configuration Guide for more information
about setting the non-repudiation attributes at the package, protocol, and
document type.

Using message store

About this task
WebSphere Partner Gateway increases the configuration options for using message
store by enabling a trading partner or internal partner to configure it at the
package, protocol, and document flow levels. By using this configuration, you have
Configuring document types chapter of WebSphere Partner Gateway Hub Configuration
Guide for uploading validation maps onto WebSphere Partner gateway.
respective WebService channel. See Configuring document types chapter of
WebSphere Partner Gateway Hub Configuration Guide for associating validation
map to channel.
under its respective Webservice channel.
file name. If you follow the WebSphere Partner Gateway schema location
functionality and industry standard way of specifying the schema location in
XML, it is not required to externally associate schema against validation map
under the respective Webservice channel.
the Webservice request channel.
Validation routing object attribute to "No". On the target side, modify the
routing object attribute Response Validation.
validation over payload XML can be altered. By default, Content Validation is
enabled.
attribute to yes.
attribute to no.
Chapter 4. Hub administration tasks
39

Advertisement

Table of Contents
loading

This manual is also suitable for:

Websphere partner gateway

Table of Contents