How important is it to insert (that is, embed) enterprise Web applications within enterprise Web applications?

I'm not talking about special-purpose "widgets", like pop-up calendars and what not, which you embed in Web pages. And I'm not talking about enterprise back-end APIs, which have no visual aspect.

I'm talking about embedding a visual enterprise Web application inside a visual enterprise Web application.

For Flux's OEM customers, the answer to the above question is, Very important.

(An OEM is simply a software company that builds and sells their software application with Flux embedded in it.)

Many of our OEM customers are financial software companies selling their software products to their corporate customers. Other times, our OEMs are different kinds of software companies whose target market is financial institutions.

Financial companies want enterprise functionality, such as payments, accounts, and receivables management. As part of that enterprise functionality, our OEMs want to provide Web-based job, workflow, and business process editing and near-real-time monitoring capabilities. Flux 7.5 and the upcoming Flux 7.6 (available 12 Nov 2007) provide those capabilities.

Take the case of our fictitious friend, Gotham Financial.



Gotham Financial wants its enterprise Web application to be "branded" with their "look" -- their colors, their logo, their style. Hence the Gotham Financial style that you see in the image above.

Gotham Financial also wants its software vendor (a Flux OEM) to embed visual job scheduling, workflow, and business process editing and near-real-time monitoring capabilities in its enterprise Web application. Gotham Financial wants to enable its own staff to design workflows customized to their needs.

All of this is a capsule of why Web Embeddable is so important.