Registration in a de-coupled environment

1. A method for registration in a de-coupled environment, comprising:

reporting an intention to create a spawned component from a parent component to a manager;

creating the spawned component by the parent component;

providing an identity of the spawned component to the manager by the parent component;

self-initializing by the spawned component;

reporting a status of the spawned component by the spawned component to the manager in response to the spawned component successfully starting;

taking a predetermined action in response to the spawned component failing to report its status to the manager after a preset time period, wherein the predetermined action by the manager comprises one of: halting associated with the spawned component, halting mainline processing by the system, advising other active components of the failure, and attempting corrective action; and

registering the spawned component with the manager in response to the spawned component successfully starting and reporting its status to the manager, the manager including the spawned component in the system by registering the spawned component.

2. The method of claim 1 , further comprising allowing mainline processing in response to all monitored components of a plurality of components being healthy and registered with the manager.

3. The method of claim 1 , wherein the manager comprises an observable interface and the parent component comprises an observer interface.

4. A system for registration in a de-coupled environment, comprising:

a processor;

a manager operable on the processor;

a parent component adapted to report an intention to create a spawned component from a parent component to the manager, create the spawned component, and provide an identity of the spawned component to the manager, the spawned component self-initializes in response to being created and reports its status to the manager in response to successfully starting; and

wherein the manager is adapted to receive the identity of the spawned component and to take a predetermined action in response to the spawned component failing to report its status after a present time period, the predetermined action by the manager comprising one of: halting a system associated with the spawned component, halting mainline processing by the system, advising other active components of the failure, and attempting corrective action; and

wherein the manager registers the spawned component in response to the spawned component successfully starting and reporting its status to the manager, the manager including the spawned component in the system by registering the spawned component.

5. The system of claim 4 , wherein the parent component and the spawned component each comprise an observer interface and wherein the manager comprises an observable interface.

6. The system of claim 4 , wherein the manager comprises one of a state manager, a GUI listener, a gateway and a publication/subscription recipient.

7. The system of claim 4 , wherein the manager is adapted to allow mainline processing in response to all monitored components of a plurality of components being healthy and registered with the manager.

8. A computer program product for registration in a de-coupled environment, the computer program product comprising:

a tangible computer useable storage medium having computer useable program code embodied therein, the computer useable medium comprising:

computer useable program code to report an intention to create a spawned component from a parent component to a manager;

computer useable program code to create the spawned component by the parent component;

computer useable program code configured to provide an identity of the spawned component by the parent component to the manager;

computer useable program code configure to initialize the spawned component;

computer useable program code configured to report a status of the spawned component to the manager in response to the spawned component successfully starting;

computer useable program code configured to take a predetermined action in response to the spawned component failing to report its status to the manager after a preset time period, wherein the predetermined action by the manager comprises one of: halting a system associated with the spawned component, halting mainline processing by the system, advising other active components of the failure, and attempting corrective action; and

computer useable program code configured to register the spawned component with the manager in response to the spawned component successfully starting and reporting its status to the manager, the manager including the spawned component in the system by registering the spawned component.

9. The computer program product of claim 8 , further comprising computer useable program code configured to allow mainline processing in response to all monitored components of a plurality of components being healthy and registered with the manager.

10. The computer program product of claim 8 , wherein the manager comprises an observable interface and the parent component comprises an observer interface.