Component Integration Environment
Integration Architect decides what systems to include
The system of systems is defined by specifying generically what systems will particpate.
The system may also include synthetic elements which modify, fuse, or otherwise alter the basic system outputs.
The system may also include synthetic elements which modify, fuse, or otherwise alter the basic system outputs.
System Owners decide on the message content to be exchanged
The owners of the participating systems specify the content that they can provide or need.
The number and format of messages is determined by agreement among the owners.
The number and format of messages is determined by agreement among the owners.
Programmer selects and extends the Java adapter/connector library
The standard library already includes many connectors and adapters.
Databases, corba objects, and many other objects may be accessed without additional programming.
In addition, each project leaves a set of command and control objects, which if well designed, may be reused.
Even if the message is new, very little programming is required to complete a new connector or adapter.
Databases, corba objects, and many other objects may be accessed without additional programming.
In addition, each project leaves a set of command and control objects, which if well designed, may be reused.
Even if the message is new, very little programming is required to complete a new connector or adapter.
Integration Architect creates a graphical representation of the system
Using the graphical interface, the Integration Architect creates a model of the system.
Message flows are drawn between the components and assemblies. The design tool retrieves component definitions from the repository and prohibits incorrect linkages.
The assembly or model is defined without referencing specific machines or message sources. Many configurations can be made from a single model by specifying the location of the participating systems, data bases, or object servers.
Message flows are drawn between the components and assemblies. The design tool retrieves component definitions from the repository and prohibits incorrect linkages.
The assembly or model is defined without referencing specific machines or message sources. Many configurations can be made from a single model by specifying the location of the participating systems, data bases, or object servers.
System Operator selects and registers a model
A system controller may select and register one of the available configurations using a web page.
Individual system owners may then start their publisher or subscriber as part of the run.
Individual system owners may then start their publisher or subscriber as part of the run.
Participating System Owners download the connection software from a web site
The connection component is downloaded from a web page to a partipating system. This is initiated by the owner of the system. The security environment of the participating system is preserved.
The process is self-loading and unloading. The particpant may cease particpation at any time.
The process is self-loading and unloading. The particpant may cease particpation at any time.
System Operators/Viewers control and monitor the model from a web site
Through a web based controller, viewers and operators may observe and monitor a working system.
Participants may talk to one another through a chat window. Individual components may be disabled or enabled changing the character of the model within the basic configuration. Component status can be displayed for any component. Logging and playback can be initiated from the web page.
Participants may talk to one another through a chat window. Individual components may be disabled or enabled changing the character of the model within the basic configuration. Component status can be displayed for any component. Logging and playback can be initiated from the web page.
