Hi All, Found the reason for the above. IoTSever pack was missing the proxy-service *"WorkflowCallbackService.xml" *thats available in the APIM 1.10.0.
It is this service that is set as the callback URL in the workflow creation request sent to BPS. Hence when the task is approved and BPS tries to contact this service it is unable to find it. When I included this service in the IoTS pack all worked fine. However, it is strange that there was no error or warning that was printed on the BPS console with regards to this. In addition, shouldn't this callback proxy-service be part of the apimgt feature if someone installs it another product? *@Lalaji: Got your reply whilst typing this.* Yeah, that's right. I have been debugging for sometime trying to find out where this method was getting called. And checked the request sent to BPS which has the callback URL and found that it was not there in the IoTS Pack. Thanks Very Much ------------------------------------- *Shabir Mohamed* *Software Engineer* WSO2 Inc.; http://wso2.com Email: [email protected] <[email protected]> Mobile: +94 77 3516019 | +94 71 6583393 On Sun, Apr 10, 2016 at 5:25 PM, Shabir Mohamed <[email protected]> wrote: > Hi All, > > I am trying to do $subject for the IoTServer as explained in [1] > <https://docs.wso2.com/display/AM1100/Adding+an+API+Subscription+Workflow> > . > > However, since the jaggeryapp *"admin-dashboard"* is not copied from the > *bin.xml* whilst the distribution is packed I have copied it manually to > the jaggeryapp folder in the IoTS pack. > > In addition given that the jaggeryapp *"store"* and the corresponding > jaggery-modules are renamed as *"apimstore"* in the IoTS pack I have > changed all places in the admin-dashboard jaggeryapp which says > *"require('apistore')"* to *'require(apimstore)'.* > > I have also configured BPS accordingly as explained in [1]. I have written > my custom extension for APISubscription workflow and engaged it in > *"wokflow-extensions.xml"*. > > When I create an API the *"execute()"* method of the WorkflowExecutor gets > triggered and my custom logic is executed. However, when I approve a > subscription task in the admin-dashboard jaggeryapp the *"complete()"* > method of the WorkflowExecutor is not triggered as expected. > > This behaviour is only evident when I try the custom extension in the IoTS > Pack. Works fine for the APIM 1.10.0 pack. > > *IoTServer users the carbon-apimgt component version: 5.0.3* > > Any guidance & insight with regards to this will be a huge help :)..... > > > [1] > https://docs.wso2.com/display/AM1100/Adding+an+API+Subscription+Workflow > ------------------------------------- > *Shabir Mohamed* > *Software Engineer* > WSO2 Inc.; http://wso2.com > Email: [email protected] <[email protected]> > Mobile: +94 77 3516019 | +94 71 6583393 >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
