Software Component node

A Software Component node represents an instance of a Software Component running inside a Software Instance, for example a deployed application inside a J2EE application server.

Software Component node lifecycle

The following section describes the scenarios in which a Software Component node is created, updated or removed.

Creation/update

This is under the full control of patterns and as a result there is no default Software Component node behavior.

The key for a Software Component node is entirely dependent on the pattern that creates the Software Component node. It is advised therefore that you take extra care when constructing the key attribute, as it will need to be unique amongst all Software Component nodes. Achieving this uniqueness would typically be done by including the following information in the key:

The type attribute
The parent node's key attribute

Removal

Software Component node can be destroyed either manually or automatically.

To remove a Software Component node manually, find the necessary Software Component, select it in the list and pick Destroy from the Actions list.

Automatic removal happens according to the following scenarios.

Authoritative removal by the pattern that creates/updates the Software Component node should be considered. The pattern not only needs to create the correct Software Component structure, it also needs to maintain it as the configuration changes
Built in removal rules will remove all the contained Software Component nodes if an SI/BAI/Host is removed.