Table of Contents

Search

  1. Preface
  2. Understanding PowerExchange for WebSphere MQ
  3. Configuring PowerExchange for WebSphere MQ
  4. Working with WebSphere MQ Sources
  5. MQ Source Qualifier Transformation
  6. Working with WebSphere MQ Targets
  7. Creating and Configuring WebSphere MQ Workflows
  8. Appendix A: Datatype Reference
  9. Appendix B: Code Pages for PowerExchange for WebSphere MQ
  10. Appendix C: Glossary of Terms

PowerExchange for WebSphere MQ User Guide for PowerCenter

PowerExchange for WebSphere MQ User Guide for PowerCenter

Configuring Resilience

Configuring Resilience

You can configure a WebSphere MQ reader session to make multiple attempts to connect or reconnect to WebSphere MQ. If a connection attempt fails because of a network failure or if the WebSphere MQ queue manager is not running, the PowerCenter Integration Service tries to connect to the queue for a specified period of time before the session fails.
You cannot configure connection resiliency for WebSphere MQ targets.
You can configure the period of time you want the PowerCenter Integration Service to attempt to connect to WebSphere MQ in a Message Queue connection. Set the Connection Retry Period property in the Message Queue connection.
When you configure resilience, also configure the following session properties:
  • Recovery Strategy.
    Set the Recovery Strategy to Resume from Last Checkpoint.
  • Destructive Read.
    Select the Destructive Read option in the session properties.
When you set the Connection Retry Period greater than zero, the PowerCenter Integration Service is resilient to the initial connection to the WebSphere MQ queue manager. The initial connection is resilient even if you do not configure the session for recovery or destructive reads.
When you run a session configured for resilience, and the PowerCenter Integration Service loses the connection to the WebSphere MQ queue, the following filter conditions continue to increment while the PowerCenter Integration Service attempts to reconnect to the queue:
  • ForcedEOQ(
    n
    )
  • FlushLatency(
    n
    )
  • Idle(
    n
    )
  • MsgCount(
    n
    )
For example, you configure a session with the Idle(30) filter condition. The PowerCenter Integration Service is idle for 10 seconds, and it loses the connection to the WebSphere MQ queue. While the PowerCenter Integration Service attempts to reconnect to the queue, the idle value continues to increase. After 15 seconds, the PowerCenter Integration Service reconnects to the queue. The PowerCenter Integration Service has been idle for 25 seconds. If it remains idle for five more seconds, the session ends.

0 COMMENTS

We’d like to hear from you!