Hi, I have been reproducing the following [1] JIRA in BAM.
I would like to get a heads up y'all in coming up with a solution, especially form the ESB team. *Issue in summary,* Consider a case where BAM mediator is used alongside with a proxy server. After successfully deploying the setup, say we wanted to change a configuration in the BAM server profile (ex: IP, ports etc). Once the change is made, it updates the profile config in the registry. BUT the changes are not updated in the back-end of ESB. So, after saving the changes if you perform any action, ESB would still use the first BAM profile configuration. In order to update the new configuration we would have to manually update synapse config (by going to source view and update) OR restart the ESB server. The need is, once a profile config is edited, the changes should readily be applied at the backend. *Detailed issue* - Following BAM documentation on BAM mediator setup [2] - BAM and ESB servers running (with a port offset 2 at ESB) - Made a BAM server profile in ESB with a single stream - Deployed SampleStockQuoteService in ESB axis2 server on port 9000 - Made a proxy service in ESB - Added BAM mediator on the in-sequence (as per the docs) - synapse config gets updated successfully - Sent requests using ESB sample clients - Setup is working and the BAM cassandra database receives the messages. - CHANGED the BAM server profile authentication port to 9999 and receiver port to 8888 - profile config gets updated in the registry. - Sent a request using ESB client - message gets mediated successfully, whereas it should have given a connection error. this means that the port changes are not updated in the ESB back-end. - Updated the synapse config manually (by going to source view and update) - Expected connection error appears - port changes are updated in the backend. In my opinion, this is a case of ESB caching the configurations. Few clarifications, 1. Can we change the runtime variables which affect the BAM mediator, while the server is running? 2. Can we update the synapse config (as the update option in the source view) once a configuration changes? Would this (updating synapse config automatically when a config is changed) be a considerable performance trade-off in ESB? 3. How can we update the synapse config, is there an admin service call? Thank you in advance [1] https://wso2.org/jira/browse/BAM-1797 [2] https://docs.wso2.com/display/BAM241/Setting+up+BAM+Mediator Cheers -- *Niranda Perera* Software Engineer, WSO2 Inc. Mobile: +94-71-554-8430 Twitter: @n1r44 <https://twitter.com/N1R44>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
