JR56366: Sterling OMS Heartbeat timeout is too long

7.0.0.0-WS-WC70Fep7Server-IFJR56366
7.0.0.0-WS-WC70Fep7Developer-IFJR56366

APAR status

• Closed as program error.

Error description

• Currently, the Sterling Order Management (OMS) Heartbeat call
  does not provide the ability to set or configure the timeout
  value. Therefore, if OMS is not available, then WebSphere
  Commerce waits for the HTTP call to timeout based on the system
  default timeout. This APAR provides the ability to configure the
   timeout value of this Heartbeat call.
  

Local fix

Problem summary

• USERS AFFECTED:
  WebSphere Commerce environments on Version 7 Feature Pack 5 or
  later, and integrated with Sterling Order Management.
  
  PROBLEM ABSTRACT:
  Sterling OMS Heartbeat timeout is too long
  
  BUSINESS IMPACT:
  When Sterling OMS is not available, WebSphere Commerce takes a
  long time to return a timeout exception.
  
  RECOMMENDATION:
  

Problem conclusion

• Added support for a new configuration to specify a timeout
  value.
  
  For more information about how to configure the timeout value,
  see
  http://www.ibm.com/support/knowledgecenter/SSZLC2_8.0.0/com.ibm.
  commerce.install.doc/tasks/tig_JR56366.htm.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WC BUS EDITION

• Fixed component ID

  5724I3800

Applicable component levels

• R700 PSY

     UP