The document discusses shortcomings of the 4.0 Deployment and Configuration (D&C) specification and what is being asked for in a revised 5.0 specification. The 4.0 specification allows for launching and tearing down component-based applications but does not provide standardized ways to control applications after launch, establish or remove connections, change component attributes, or control and monitor deployment engines. The proposed 5.0 specification aims to address these issues and provide a flexible deployment engine that can reconfigure, redeploy, monitor, and guard applications in their target environment.

1. Deployment and Configuration 5.0
mars/2011-09-05
Copyright © 2011 Page 1

2. D&C 5.0 (1/2)
The D&C specification was originally developed
to launch and tear down a Component- based
applications in a target environment in a
defined manner
Copyright © 2011 Page 2

3. D&C 5.0 (2/2)
The 4.0 D&C specification doesn't offer a
standardized way to :
– control the behavior of a launched application
– monitor the internals of a deployment engine
– control the behavior of a deployment engine
Copyright © 2011 Page 3

4. Shortcomings 4.0 D&C
specification
At this moment the D&C specification specifies
a static environment: launch and tear down an
application
There is no standardized way to
– add components to a launched application
– remove components from a launched
application
Copyright © 2011 Page 4

5. Shortcomings continued
No standardized way to
– establish connections after launch
– disconnect connections after launch
– change the components attributes after
launch
– control the behavior of a deployment engine
– monitor the internals of a deployment engine
Copyright © 2011 Page 5

6. What do we ask for ?
A revised D&C specification which defines how
to
▪ add components to a launched application
▪ remove components from a launched application
▪ establish connections after launch
▪ disconnect connections after launch
▪ change attributes of components after launch
Copyright © 2011 Page 6

7. What do we ask for ?
A revised D&C specification which defines how
to
– control the behavior of a deployment engine
– monitor the internals of a deployment engine
– handle requests, like preparePlan and startLaunch:
▪ asynchronous
▪ event driven
▪ scheduling of events
▪ interceptors
Copyright © 2011 Page 7

8. Our goal
A Deployment and Configuration
specification which gives Executors a
flexible deployment engine which is able to
reconfigure, redeploy, guard, and monitor an
entire application in its target environment
Copyright © 2011 Page 8

9. Thanks
Thanks for your attention.
Johnny Willemsen
<jwillemsen@remedy.nl>
http://www.remedy.nl
Copyright © 2011 Page 9