Desktop Integration Siebel Agent
Initially released with IP15.9/14.15 back in February, DISA served to replace like-for-like functionalities previously implemented using (insecure) Java Applets. One of the most visible: replacing the Java Applet based in-line attachment edit-and-save-back feature. Further: CTI Hoteling and Send Mail (F9) using Outlook instead of the Siebel email client will be added with IP16. Who knows what follows!
Truly exciting: with IP16 – Siebel will open-up and document the DISA API for customers. Meaning endless extensibility options. Advanced interactions between Siebel and the desktop (bi-directional) will be possible. Although DISA itself communicates in a secure way with Siebel, the developer has due to nearly unlimited access to the desktop its responsibilities.
Below a high-level architectural overview of the DISA framework.
DISA uses a message-based approach to communicate between Siebel and the ‘client’ through a (secure) WebSocket connection. The DISA ‘client’ is a Java ‘plug-in’ which will have full access to the desktop. That means as simple as it sounds, Siebel could run a command-line operation, start an application, have access to the local filesystem, … Multiple plug-ins can be made available. These should be separately deployed. Not difficult to imagine a DISA plug-in to ‘deploy’ at run-time a custom plug-ins from a certain location. Either brand new ones, or updated ones.
So yes, if you don’t own them yet – you need to get access to or learn Java 🙂 As a starter, Oracle will be providing some examples through Github. Going forward the ConfiguringSiebel repository on the OracleSiebel Git will serve for this purpose. Oracle’s Siebel development will further supervise the Git and motivates the Siebel developer eco-system to share, add & commit! So jump along the bandwagon!