Right now each of our product use it's own way to define BAM server profiles, it would be nice if we can follow an unified process when configuring BAM servers and to enable/disable server level data publishing. FYI these are some of the approaches used by our products.
ESB - Through BAM server profile UI and no configuration file. AS - Use bam.xml to enable disable server level data publishing and Webapp/Service Data Publishing UI for server configuration. BPS - Through bps.xml and writing a BAMServerProfile.xml file. API-M - Through api-manager.xml file. IMHO we can unified this process among all the servers up to some extend, as an example 1. Configuring BAM server details - urls, user name, password 2. Globally enable and disable data publishing 3. Name of the stat database 4. Publishing protocol and it's configuration I have two suggestion on this. a.) As BAM publishing is common for most of the product define new element called <Analytic> under carbon.xml to hold above common configurations. b.) Alternatively define bam.xml file to hold above common configurations. WDYT ? NOTE - I only considered BAM but I guess we can consider CEP as well. Thanks ! -- Sagara Gunathunga Senior Technical Lead; WSO2, Inc.; http://wso2.com V.P Apache Web Services; http://ws.apache.org/ Linkedin; http://www.linkedin.com/in/ssagara Blog ; http://ssagara.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
