Generally, I have seen Handler tester being used to debug IB subscription code. In development environments, I write a simple AE in which I call the IB message transaction ID directly and do debug for each line (just like any other AE debug). In this way, you can get to know the code (if not developed by you) thoroughly. It is just my way of doing. You can always go with your own approach.
import IB_EXAMPLE:IBSubscriptionTest (example);
Local Message &ibMsg;
Local IB_EXAMPLE:IBSubscriptionTest &ibSubT =
create IB_EXAMPLE:IBSubscriptionTest();
Local string &TransactionId = "Transaction ID from Operation Instance";
&ibMsg = %IntBroker.GetMessage(&TransactionId, %IntBroker_BRK);
&ibSubT.OnNotify(&ibMsg);
4. Run the AE in debugger mode.
If some error occurred in user testing or production environment, I used to export data and insert the data in development and do debugging as explained above. It helps me.
- Create an AE program
- Add a step and select peoplecode action
- Write the following code in Peoplecode action
import IB_EXAMPLE:IBSubscriptionTest (example);
Local Message &ibMsg;
Local IB_EXAMPLE:IBSubscriptionTest &ibSubT =
create IB_EXAMPLE:IBSubscriptionTest();
Local string &TransactionId = "Transaction ID from Operation Instance";
&ibMsg = %IntBroker.GetMessage(&TransactionId, %IntBroker_BRK);
&ibSubT.OnNotify(&ibMsg);
4. Run the AE in debugger mode.
If some error occurred in user testing or production environment, I used to export data and insert the data in development and do debugging as explained above. It helps me.
No comments:
Post a Comment