5.4.1 Background

It is to be expected that a new user of Overlord:DTG may already have some number of Solutions in production (or working towards production).  These existing Solutions have been created using alternative tooling or no formal tooling at all.  The user may want to reverse engineer a Solution in Overlord:DTG from existing assets.

5.4.2 Participants

• Arlen [Architect]
• Debbie [Developer]

5.4.3 System Narrative

Debbie uses external development tools to create an application (e.g. a JAX-WS web application or a Switchyard application) and package it into a Deployment Unit.  Additionally, existing Deployment Units already in production can be gathered together.

Debbie adds these new and existing Deployment Units to Overlord:DTG, either manually through the UI or via integration with a build system such as Maven.  The system allows Debbie to upload multiple Deployment Unit files all at once, to make this process easier.

Debbie navigates to the Deployment Unit Management page.  She finds and selects multiple Deployment Units (e.g. the collection of Deployment Units she just uploaded) and chooses the “Generate Solution” action.  The system uses the Component artifacts that were automatically detected in the Deployment Unit to generate a new Solution containing a set of logical artifacts.  For example, each WSDL ServiceComponent found will result in a logical Service artifact being included in the generated Solution.  Likewise, each BPEL CompositionComponent will result in a new logical Composition being included in the Solution.

Debbie is presented with a summary of all logical artifacts that will be created by the Solution.  She will be given the opportunity to exclude certain artifacts and modify the details of all the artifacts prior to clicking the “Generate” button.  Once clicked, the system will create the new Solution and all the logical artifacts (optionally automatically linking the Components to their respective logical artifacts).