Determining the Packaging Scheme to Use
The following table summarizes the packaging schemes to use for your
new resource types.
Table 4-1 Determining the
Packaging Scheme to Use | | |
|---|
Make property changes in only the RTR file.
| ANYTIME
| Deliver only new RTR file.
|
Update the methods.
| ANYTIME
| Place the updated methods in a different path than the old methods.
|
Install the new monitor program.
| WHEN_UNMONITORED
| Overwrite only the previous version of the monitor.
|
Update the methods. The new Update and Stop methods
are incompatible with the old Start methods.
| WHEN_OFFLINE
| Place the updated methods in a different path than the old methods.
|
Update the methods and add new properties to the RTR file. The new methods
require new properties. The goal is to allow the containing resource group to remain online
but prevent the resource from coming online if the resource group moves from
the offline state to the online state on a node.
| WHEN_DISABLED
| Overwrite the previous versions of the methods.
|
Update the methods and add new properties to the RTR file. New methods
do not require new properties.
| ANYTIME
| Overwrite the previous versions of the methods.
|
Update the methods. The new Fini method is incompatible
with the old Init method.
| WHEN_UNMANAGED
| Place the updated methods in a different path than the old methods.
|
Update the methods. No changes are made to the RTR file.
| Not applicable. No changes are made to the RTR file.
| Overwrite the previous versions of the methods. Because you made no
changes to the RTR file, the resource does not need to be registered or upgraded.
|
|