![]() ![]() ![]() In this article, contributed by Vivek Gupta, we show how to debug IBM i program called from Mule API. The connector logs the exception and the trace, however in some cases it’s really useful to take a look at what’s going on during program execution. Most commonly the issues are caused by the incorrect parameter definitions, where parameter mode, data type or length or sequence mismatch cause the program to bomb. Right… in real life there are quite a few things that could go wrong with remote program call. ![]() Took just under 15 minutes to build and works like a charm at the first try. In the previous post we wrapped an IBM i business logic program into an easy to consume API with Mulesoft Anypoint platform and IBM i Connector. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |