Below you can see the database scheme for the current ESME server. This isn’t described any where else and I thought it might be useful for developers to see what lies beneath the code. This might be especially relevant for those developing administration applications.
Note: Please be aware that this current database scheme. As the ESME core evolves, there will probably be changes in this scheme.
Note: This blog doesn’t have any code but focuses on ideas. Later blogs will have code examples.
This morning, I started considering other possibilities to integrate ESME into the enterprise IT environment. Previously, I’ve looked at clients based on development languages (Java, etc.). This time, I would like to discuss a few ideas regarding integration of ESME into database applications.
The basic idea is to use trigger mechanisms to send messages when certain events occur. For this scenario to work a database must support triggers and support HTTP-based communication. Initially, I looked at Microsoft Access (thought it might be “low-hanging fruit”) but unfortunately, it appears that it doesn’t support triggers.
I then looked at Oracle and found two examples of PL/SQL applications that send twitter messages and another example that reads the twitter message stream. Both are linked to the OraTweet application and use the PL/SQL package UTL_HTTP to communicate via HTTP. Based on these examples, a simple ESME client for ORACLE should be easy.
TwitterTalk