| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Java CAPS Management and Monitoring APIs Java CAPS Documentation |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Java CAPS Management and Monitoring APIs Java CAPS Documentation |
Java CAPS Management and Monitoring APIs
To Start Using APIs to Create Applications
Connecting to the Server Through APIs
CAPSManagementClientFactory Definition
Services -- JavaCAPSManagementAPI
Performance Measurement Service
Master Data Management (MDM) Service
Java CAPS Adapters Management Service
Target Option Behavior for the Management Client
To Set Up a Database Using Enterprise Manager
To Set Up a Database Using a Scripting Utility
Using Oracle and Other Databases for Alert Persistence
To Set Up an Oracle Database for Alert Persistence
Downloading, Installing, and Setting Up A Scripting Environment
Setting Up a Scripting Environment to Invoke Java CAPS Management and Monitoring APIs
To Modify the Environment Variables in env.bat
Using a Scripting Language to Exercise the Java CAPS Management and Monitoring APIs
Exercising the Administration Service
Exercising the Administration Service in Groovy
Exercising the Configuration Service
Exercising the Configuration Service in Groovy
Exercising the Deployment Service
Exercising the Deployment Service in Groovy
Exercising the Installation Service
Exercising the Installation Service in Groovy
Exercising the Runtime Management Service
Exercising the Runtime Management Service in Groovy
Exercising the JMS Management Service
Exercising the JMS Management Service in Groovy
Exercising the BPEL Management Service
Exercising the BPEL Management Service in Groovy
Exercising the HTTP Administration Service
Exercising the HTTP Administration Service in Groovy
Exercising the Notification Service
Exercising the Notification Service in Groovy
Use the Java code samples to write your own Java Code to access the APIs. The samples are included with the software delivery as zipped files.
When the Alert Management Subsystem receives alerts it sends them to subscribers, such as Enterprise Manager or Groovy. There are two ways the process works.
When persistence is not turned on alerts are sent directly to all subscribers that use the client API. If there are no subscribers the alerts are dropped.
When persistence is turned on alerts are sent to a database. If there are no subscribers the alerts are persisted in the database until subscribers are ready to consume them. Optionally, you can enable journaling, which ensures that the alerts are never deleted.
|