cancel
Showing results for 
Search instead for 
Did you mean: 

JDBC select with synchronous receiver

Former Member
0 Kudos

Hello,

We have implemented a BPM to select from a AS400 DB table data started by a async call from SAP..

The select is something like successful but there is an issue we don´t understand.

The message structure for the select is shown in this payload

which is defined as 0...UNBOUNDED in the data type.

STATEMENT and STATEMENT_response are defined as 1...unbounded too.

We did a connect via Excel with a query where we can see the results we expect to get.

So where could the mistake being hidden?

Best regards

Dirk

Accepted Solutions (1)

Accepted Solutions (1)

justin_santhanam
Active Contributor
0 Kudos

Meinhard,

What I would suggest is - open the receiver communication channel go to the advanced mode and give the below parameter

logSQLStatement "true" {without quotes)

Run the scenario and check the Audit log in the communication channel - it will have the SQL query on how it got generated. Now copy this SQL query and run on ur AS400 to see how many records you are getting.

I don't know if it will help, but for debugging , we will take this as first approach.

Thanks!

Former Member
0 Kudos

Ok,

Correction:

The select statement returns more than one entry. We cans ee this in the RWB message monitoring and in the SXMB_MONI

in the response message display.

But the select result list from the payload in "Inbound message" gets lost in the payload of "Request Message mapping"

where we only find the first select result.

Then the system continues with this single result for the next step.

We didn´t change the message type anywhere in the BPM or in the mapping or in any interface !

Has anybody an idea what is wrong?

Regards

Dirk

Edited by: Meinhard Dirk on Mar 30, 2010 7:30 PM

Edited by: Meinhard Dirk on Mar 30, 2010 7:50 PM

former_member200962
Active Contributor
0 Kudos
We cans ee this in the RWB message monitoring and in the SXMB_MONI in the response message display.
But the select result list from the payload in "Inbound message" gets lost in the payload of "Request Message mapping" where 
we only find the first select result.

The above two statements should mean that the DB returns proper response and is even seen in XI/ PI.....just that your response mapping is not able to take all the occurences.....can you confirm that the response mapping program is able to consider all the results (across all the contexts)....if tested in IR does your mapping give proper output?

Regards,

Abhishek.

Former Member
0 Kudos

Sorry guys, not to be able to provide other information.

After a support package update it symply seems that our best friend, the cache update problem is back.

Integtraion Server gets no updated data in realtime.

Regards

Dirk

Answers (1)

Answers (1)

Former Member
0 Kudos

Solved on my own!