Correlation does not work when request closure data is mapped to reply closure data for request response invocation service in BW?

Correlation does not work when request closure data is mapped to reply closure data for request response invocation service in BW?

book

Article ID: KB0090269

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Adapter for Websphere MQ -
Not Applicable -

Description

Resolution:
Description:
=========
In the Request/Response Invocation adapter service, the response correlation ID has to match to the requests that has been set.

Environment:
==========
ALL

Symptoms:
========
Adapter request response invocation service throws error "Closure is NULL".  

Cause:
=====
Closure fields type should be substituted as binary for the adapter to accept these. In the adapter repository configuration file the closure data in the output of the 'Respond To Adapter' task in BW is not substituted properly. Hence, if these fields are not properly sent to the adapter then it will result in miss-matched or zero correlation IDs for the replies.

Resolution:
========
Modify the closure fields to the required binary type.
1. Select the "caret_closure_caret" node in the 'Activity Input' panel.
2. Click on the 'Edit Statement' icon in the same panel. This is the icon with the     exclamation mark on it (!).
3. This will open the 'Edit Statement' dialog. Go to the 'Type' tab in the dialog.
4. Check the 'Type Substitution' option.
5. In the 'Type' drop box select '01 Binary'.
6. Select 'Base 64' for 'Encoding'. Click Ok.

Repeat these steps for user closure field.

Issue/Introduction

Correlation does not work when request closure data is mapped to reply closure data for request response invocation service in BW?