Common B2B XB60 configuration mistakes - IBM Websphere

Next,we describe several common configuration mistakes.

The hard disk array is unresponsive or down

Symptoms:

  • The RAID disk drive is unresponsive for several hours.
  • Error messages result when you create the B2B Gateway Service.

Solving the problem:

  • Check to make sure that the hard drives are synchronized completely.
  • Make sure that the hard drive directory name is not the same name as any application domain name on the appliance.
  • Reconfigure the hard drive storage and verify the configuration.

B2B Gateway is unresponsive (down)

Symptoms:

The B2B Gateway Service reverts to the down state if:

  • Any object associated with the B2B Gateway Service is in the operational state of down.
  • Any crypto identification credentials are down,and the associated partner profile and theassociated gateway revert to the down state.
  • B2B persistence is not initialized properly.

To solve the problem, correct the problem in the underlying object and save the domain configuration.

Restart the domain if necessary.

B2B Transaction Viewer not visible to partners

The symptom is the B2B Transaction Viewer is inaccessible.

To solve the problem:

  • The B2B Transaction Viewer is not accessible by default.
  • Check the user’s group access profile and each underlying access policy.

B2B Gateway not sending MDNs as expected

The B2B Gateway is not sending Message Disposition Notifications (MDNs) as expected. Symptomsinclude, when requesting asynchronous MDNs,the MDN is not sent correctly, because:

  • The redirection URL is not specified correctly in the B2B Gateway Service.
  • The redirection URL is not specified correctly in the partner profile.

Solving the problem:

  • We recommend that you always specify the redirection URL in the B2B Gateway. In the case where the URL is specified in both places, the value in the partner profile overrides the B2B
  • Gateway.
  • Make sure that the redirection URL that is specified is external to the gateway.

Binary documents are not routed properly

The problem is that binary documents are not routed properly.

Symptoms
When working to code the Document Routing Preprocessor stylesheet,the following error messages might appear in the appliance log (assuming that the log level is set to debug):

  • 0x80000001 b2bgw: x12 sender-id, "111" does not match partner-from, "333" specified by headers.”
  • 0x80000001 b2bgw: error extracting EDI partner info from message.”
  • 0x03130001 b2bgw:Invalid business ID and 0x82c00001 b2bgw ():
  • Invalid business ID.”

Solving the problem
The Document Routing Preprocessor stylesheet,which is available on the Advanced tab when configuring a B2B Gateway,can be used to set partner IDs for outgoing B2B transactions processing binary files.

The stylesheet sets partner information for the transaction by setting two DataPower service contextvariables as shown in Example below.

Stylesheet sets two DataPower service context variables

By default,the IBM WebSphere DataPower B2B Appliance XB60 is configured to route electronic datainterchange (EDI) documents between systems inside an enterprise network and a similar B2B Gateway at another company. The XB60 natively understands ANSI X12 and EDIFACT documents and has special handling for XML-formatted EDI messages. All other messages are handled as binary messages.

Possible causes
The stylesheet might not be setting the service context variables properly or the partner IDs might not be properly configured. Also, be aware that there are restrictions for inbound and outbound messages, which might cause problems.

Version restriction:All of the inbound and outbound message flows through a B2B Gateway Service are assumed to be contained in B2B messaging protocols,such as AS2 or AS3 headers.

Inbound messages
The XB60 receives “inbound” messages from an external trading partner and routes them to an internal system. These messages are always received using AS2 or AS3 wire protocols. In these protocols:

  • The AS2-From:or AS3-From: header identifies the trading partner that sends the message.
  • The AS2-To: or AS3-To: header identifies the trading partner to receive the message.

These protocols also use the MIME Content-Type: header to identify the type of message.Inbound binary documents are routed in the same manner as other inbound documents. The B2B Gateway finds the corresponding partner profile that contains the ID of the trading partner from the AS2-To: or AS3-To: header, finds the first destination on the partner profile that lists “binary” as an Enabled Document Type, and forwards the document to the URL for that destination.

Outbound messages
The XB60 receives “outbound” messages from an internal system and routes hem to an external trading partner. The XB60 often receives these messages via a protocol,such as WebSphere MQ,that does not have the same routing headers as AS2 or AS3. For X12 and EDIFACT messages,the XB60 can parse the message contents and find the partner IDs from the ISA and UNA headers.

The XPath Routing Policies tab on the B2B Gateway configuration tells the XB60 how to find the partner IDs for XML documents. For binary messages, an appliance administrator must configure an XSLTstylesheet as the Document Routing Preprocessor for the gateway to route the message properly.

The routing stylesheet is an XSLT 1.0 stylesheet with standard DataPower extensions available run over an empty tree as input. The default stylesheet is store:///b2b-routing.xsl.For gateway implementations, an administrator will make a copy of this stylesheet either in the appliance per-domain local:directory or on an external Web server, edit it to the needs of a particulargateway, and update the B2B Gateway configuration to point at the modified stylesheet. Each B2B Gateway can be configured with a different routing stylesheet.

Diagnosing the problem
In order to diagnose the problem, add the <xsl:message> element to your stylesheet to include debug information in the DataPower system logs.this <xsl:message> writes a simple message to the log indicating that the stylesheet is reaching the element that sets the service context variables.

Add the <xsl:message> element to your stylesheet

Use the Troubleshooting icon from the DataPower Control panel to set the log level to debug to see the <xsl:message> output written by your stylesheet.

The information that the routing stylesheet needs is available through a set of service variables via the DataPower dp:variable() XSLT extension. The store:///b2b-routing.xsl stylesheet contains several examples in comments about how to use this extension function. Next,we list several common error messages that you might encounter during the development of the document routing preprocessor stylesheet with their accompanying remediation suggestions:

  • “0x80000001 b2bgw: x12 sender-id, "x" does not match partner-from, "y" specified by headers.”

The gateway is treating the request associated with the transaction as an X12 EDI document. Include this line in the stylesheet to have the request processed as a binary file:

  • “0x80000001 b2bgw: error extracting EDI partner info from message.”

The stylesheet did not properly set the value of the var://service/b2b-partner-from variables. Make sure that the literal values for the service variables are properly enclosed in quotes:

Use the previous <xsl:message> technique to display the value that you are setting in the log.

  • “0x03130001 b2bgw: Invalid business ID and 0x82c00001 b2bgw (): Invalid business ID.”

The stylesheet might set partner information for outgoing transactions,so the following must be true:

  • The value of var://service/b2b-partner-from must be a partner ID for an Internal partner profile.
  • The value of var://service/b2b-partner-to must be a partner ID for an External partner profile.

Choose the B2B Partner Profile icon from the DataPower Control Panel and verify that your partnerconfigurations are configured for an outgoing transaction.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM Websphere Topics