Sterling B2B Integrator nodes causing a data center failure

Edit online

Sterling B2B Integrator nodes are down, resulting in a failed data center.

Symptoms

Message processing for Global Mailbox continues in both data centers, but message replication fails.

Diagnosing the problem

  1. Check IBM® Control Center for a red circle on Global Mailbox present in Sterling B2B Integrator within the Data center view.
  2. Check if you are able to connect to the Sterling B2B Integrator servers to send files.

Resolving the problem

Once you resolve the issue causing the Sterling B2B Integrator node outage, complete the following steps to reprocess stuck files:

  1. Restart the Sterling B2B Integrator nodes using runAll.sh.
  2. Redeliver the files that failed delivery within the surviving data center.
    1. Use Advanced Search in Sterling File Gateway to find all files where Status=Failed delivery.
    2. Manually start BP FileGatewayReroute so that file reprocessing occurs immediately rather than on the next scheduled interval.
    3. Wait until all redelivery is complete to proceed.
  3. Replay the files that failed routing within the surviving data center.
    1. Use Advanced Search in Sterling File Gateway to find all files where Status=Failed routing.
    2. Manually start BP FileGatewayReroute so that file reprocessing occurs immediately rather than on the next scheduled interval.
    3. Wait until all routing is complete to proceed.
  4. Use the eventUtility script to resend events for incomplete messages.
    1. Run the eventUtility to list the unprocessed files on data centers.
      ./eventUtility.sh listEvents --appName=B2Bi --processStatus="PROCESSING" --sourceDC=<failed DC> --targetDC=<Surviving DC>
    2. Run the eventUtility to resend events for files that were in the middle of processing in the failed data center:
      ./eventUtility.sh resendEvents --appName=B2Bi --processStatus="PROCESSING" --sourceDC=<failed DC> --targetDC=<Surviving DC> --adminUser=<userid> --adminPassword=<password>
    3. Run the eventUtility to resend events for unprocessed files in the failed data center:
      ./eventUtility.sh resendEvents --appName=B2Bi --processStatus="UNPROCESSED" --sourceDC=<failed DC> --targetDC=<Surviving DC> --adminUser=<userid> --adminPassword=<password>
    4. Run the eventUtility to complete an Evaluate for messages that do not have an event associated with them:
      ./eventUtility.sh evaluateRules --appName=B2Bi --outputFile=<file name> --adminUser=admin --adminPassword=<password>
    Tip: For more information, see eventUtility script.