Notifications from the application server Web Services Distributed Management resources
Use this topic to learn about application server Web Services Distributed Management (WSDM) resources and their life cycle events.
Important: WSDM is a system application and it is disabled by default when the product is installed. We must first enable WSDM before we can use it to manage the product resources. Use scripting to enable WSDM.
There are different life cycle events that can occur for any resource. The notifications associated with these lifecycle events are resource definition events and resource state events. Resource definition events are:
- Created
- Deleted
- Changed
Resource state events are:
- Started
- Stopped
- Suspended
The following resources are discussed in detail. We can review WSDM manageability capabilities for application server resource types for information about each resource endpoint address and manageability capabilities.
The application server instances support definitional notifications. Whenever a resource definition event occurs, the configuration of an application server is created, modified, or deleted and a notification is generated by the WebSphere Application Server domain. The notification includes the configuration documents that have been changed.
The product installation is performed and managed by the underlying operating system. There is no runtime entity that represents the product installation. There are no life cycle notifications currently planned for events related to the product installation. There are no state event notifications associated with the lifecycle of the overall product installation.
There is an administrative agent process created as part of a WAS profile. This administrative agent process, once created, becomes available to emit life cycle notifications for the profile. Since any configuration modification might be considered a change to the profile, there is no generic profile changed notification. Instead, there are specific notifications for some configuration changes. In addition, there is no state change notification for profiles because a profile does not actually run, it simply exists or does not exist.
Applications installed into the product support both definitional and operational notifications. Whenever an application is installed, a notification is produced to indicate an instance of that application managed resource has been created. A notification is generated each time the application is started, stopped, or updated. When an application is uninstalled, the resource destroyed notification is produced.
Individual deployed modules have independent life cycles. There are create, modify, delete, start, and stop notifications for individual deployed objects in the product.
Even though web services are not robust applications, there is a need to understand the life cycle for these essential deployed objects. Notifications are produced in accordance to the MOWS specification such as when a web service is installed, modified, started, stopped or uninstalled.
Related:
Web Services Distributed Management Enable WSDM Making deployed web services applications available to clients Configure application and system policy sets for web services Secure requests to the trust service using system policy sets Web Services Distributed Management manageability capabilities for WAS resource types Web Services Distributed Management in a stand-alone application server instance Web Services Distributed Management in a WAS ND cell Programming model APIs and specifications