This can be accomplished in a variety of ways. Most EAI vendors provide a software development kit (SDK) for connector development. Alternatively, some off-the-shelf infrastructure connectors, e.g. file or database connectors, can be employed to achieve a connection. For example, the generic file read/write connector may well be useful in a situation where no connectors are available, but the application supports a file-based interface. A final note on connectors. When asked about the availability of a given connector, a vendor may well reply in the affirmative. But be sure to ask the right question. The question has to be phrased in terms of the specific application release (i.e. MetaSolv TBS V5.0.1), the specific EAI version (i.e. Vitria 3.0), the specific platform (i.e. Sun Solaris 8) and possibly the database (i.e. Oracle 8.0.2). 15.2 Where Do I Manage Workflow? A source of considerable confusion when discussing OSS integration is the role of workflow techniques and technology. One source of confusion can simply be attributed to the word "workflow," which appears to mean different things to different people. To some people it means task queues, work-lists, and document management, to others it implies an integration engine and a process automator. Another point of confusion (and contention) can be the The Ultimate Guide to Building and Delivering OSS/BSS role of independent workflow products versus the workflow capabilities frequently embedded in the products of package vendors. Yet another source of confusion is the role of the workflow managers provided by some EAI vendors. Here we will try sorting through the confusion and identify the role of workflow in OSS application integration. The easiest place to start is with the OSS applications. Many vendors bundle workflow capabilities into their products. Providers of order management functionality are the most notable examples. They are not alone. SFA, CRM, and even billing vendors (for collections processing, for example) typically include some notion of wor