Ratha, Let's have chat on this tomorrow morning. will sleep on this... /sumedha
On Thu, Sep 2, 2010 at 8:34 PM, ratha <rat...@wso2.com> wrote:
Hi all,
This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_
* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)
bam-db
Please share your thoughts..It is urgent..
Thanks. -Ratha.
_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Forgot to attach diagram.. ratha wrote:
Hi all,
This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_
* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)
bam-db
Please share your thoughts..It is urgent..
Thanks. -Ratha.
_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
Hi all,
This is how BAM database is designed.. (# diagram) Currently we are able to track service stats using ActivityID(activity-->message-->operation-->service). For the message tracing requirement we need to track ESB messages too. ie: we need to map messages with sequence/endpoint/proxy. With the current design it is not possible, since we have FK (foreign key ) pointing only the operation table and activity table. How do we need to address this? Currently all three mediation data are stored in a single table as a key value pair(SERVER_USER_DATA table) and we have separate dimension tables(hour/month..) for each mediation type. So , we fetch data from the common table to fill those dimension tables. _ Difficulties_
* We can not introduce a new column (FK) with existing message table to point mediation data.( There is no separate tables for Proxy, Endpoint,Sequence. All are stored in a common table as mentioned above. And when we try to save WSAS messages it wont be possible)
bam-db
Please share your thoughts..It is urgent..
Thanks. -Ratha.
_______________________________________________ Architecture mailing list Arch...@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture