home  author concepts Download Developing Process Tutorial |
JayCE
Component concept
Components
The main conceptual idea in JayCe was to create a framework existing of reuseable components to avoid multiple errorsources in messageprocessing and increase integration-time of enterprise business applications.
Messageflow
Different components where linked together in pipelines so the output of one component will be the input for 1..n components.
Each component will process the message in the defined way and redirect the changed message to the connected components. The connection between the component is established using a persistent queue mechanism so faults in the message processing pipeline will not cause a lost of messages and informations. After fixing the faulty component the message flow will continue at the point it last stopped.
persisent queue mechanism
Every component runs in a separate Thread, so receiving of messages is still possibly althrough a message processor hangs on cause of error.
Message Flow Concept
The configuration file
To config which components to start you have to edit the config.xml file in the working path of your jayce-server-instance. The config.xml file defines which plugins to be loadded at server startup and the properties of the server. The roottag of config.xml always is configuration
Maintags
| system | defines system plugins as errorhandlers, controllers and so on |
| components | defines components to be load and start on startup. |
| chains | defines the linking of the components (which output will be input of which component) |
Component Definition Tags
in the components tag you can define one component tag for every component to be loaded. The component tag itself have the attribute active definining if the component really is activ (and so get loaded and started) or not. Every component-tag is followed by tags defining the component:| name | |
| classname | |
| property |
example config
State Level System
State Levels