IBM E02HRLL-G Administration Guide - Page 45
Using non-repudiation logging, Using message store
![]() |
View all IBM E02HRLL-G manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 45 highlights
v Upload the necessary validation map to WebSphere Partner Gateway. See Configuring document types chapter of WebSphere Partner Gateway Hub Configuration Guide for uploading validation maps onto WebSphere Partner gateway. v For DTD based validation, associate DTD against validation map under its respective WebService channel. See Configuring document types chapter of WebSphere Partner Gateway Hub Configuration Guide for associating validation map to channel. v For schema-based validation, optionally, you can associate the validation map under its respective Webservice channel. v While uploading schema into WebSphere Partner Gateway, use the SystemId for 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. v Choose the built-in action SOAP Body Validate to validate SOAP Body under the Webservice request channel. v You can optionally choose not to validate the response by setting the Response Validation routing object attribute to ″No″. On the target side, modify the routing object attribute Response Validation. v By enabling/disabling Content Validation routing object attribute, the content validation over payload XML can be altered. By default, Content Validation is enabled. 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 attribute to yes. 4. Edit the attributes for the none package setting the NonRepudiationRequired attribute to no. 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 Chapter 4. Hub administration tasks 39
![](/manual_guide/products/ibm-e02hrllg-administration-guide-f948001/45.png)