I have been working on adapter sync notification and having problem calling the target Flow service. I wrote an adapter that listens on a port, accepts a client TCP/IP connection. When the client sends a msg to the adapter I saw that the connection and the listener got the message, but somehow the target service was not called.
Here are the details:
The listening notification has 2 parameter fields:
inputString - “inString” - WmTemplateDescriptor.INPUT_FIELD_NAMES
outputString - “outString” - WmTemplateDescriptor.OUTPUT_FIELD_NAMES
2 doc types got created:
All make sense. Here are the questions:
If the target flow service is not called, should I see some error somewhere?
If the target flow service is not called, could it be input/output signature not matching, or something else?
In the target flow service, should I specify:
or not to specfy input/output at all?
Note that with async notification you create a trigger and select the doc type you want to handle and never have this problem.
- in the adapter’s runNotification(), I am supposed to call:
// details omitted
wrReq = WmRecordFactory.getFactory().createWmRecord("[some name]");
wrResp = invokeService(wrReq);
Now how does the names of wrReq, wrResp and the names of their IData correspond to the input/output names of my listen notify template above?
wrReq " Wait4MsgRequestDocument"
- IData “docReq”
– String “outString”
- String “outString”
or something else?
Any help is appreciated!