Understanding the Regions of the Oracle Java Cloud Service - SaaS Extension Control Home Page
The Oracle Java Cloud Service - SaaS Extension Control home page provides statistics on performance, data sources, response and load, using Oracle Java Cloud Service - SaaS Extension jobs, applications, and resource usage.
The metrics shown represent the most recent values available. For all "per minute" statistics, they are per minute in the last five minutes.
The Oracle Java Cloud Service - SaaS Extension Control page is made up of the following regions:
Region | Description |
---|---|
Restart Service |
If the Oracle Java Cloud Service - SaaS Extension instance somehow reaches an inconsistent state, for example, due to a network error, you can use the Restart Service option to restart the service, which will restart all the managed nodes in the service's domain. |
Performance Summary |
Displays usage metrics for a single Oracle Java Cloud Service - SaaS Extension. All metrics represent the most recent values available. The metric descriptions are: General
Servlets and JSPs
JDBC Usage
You can also download your service-specific log files using the View Log Messages link. Clicking this link takes you to the Log Messages page. This page display the log messages based on the search criteria which you provided. |
Data Sources |
Identifies the data sources accessed by the service. |
Response and Load |
Use this region to review the response and load charts associated with each server in the Java service. Using this data, you can determine if the servers are behaving as expected, if any server is overloaded, or if a server is taking too long to respond and load. If a server is overloaded or taking too long to respond and load, request an upgrade (add more servers) or ask the Cloud administrator to restart your servers if they are performing poorly. |
Jobs |
The Jobs region shows the jobs submitted for this service and the status for each of these jobs. You can also get additional details (view logs) for each of these jobs. Click an Activity ID and select View Activity Logs. For a typical deploy job, there are five logs: Virus Scan, Application Whitelist Validation, WLS Compile, Cloud Compile, and Deploy Application. These logs are text documents that you can either open or save. These logs are the result of background jobs that ran against the application and determined whether the application contains a virus or could otherwise cause problems. If a deploy job fails, the best course of action is to view the logs for the job. Depending on the different job logs available, you can determine where the failure occurred. If there are Java API validations, the Whitelist Validation may not reject the application from being deployed. Instead, it would create a warning report against the violations. You can refresh the Jobs region using the Refresh control located at the top right of the region. This is useful when you have just submitted a job and you want to see if the status has changed. By default, the refresh control is set to manual. You can change it to auto-refresh using the available time intervals. |
Applications |
Use this region to see the list of applications available for this service. To study the statistics associated with a particular application and to view its log files, click the name of the application.
|
Libraries |
Use this region to see the list of libraries available for this service.
|
Resource Usage |
Use this region to review the CPU and Heap usage for each server in the Java service. Using this data, you can determine if the servers are behaving as expected, if any server is overloaded or using too much of the resources.If a server is overloaded or using too many resources, request an upgrade (add more servers) or ask the Cloud administrator to restart your servers if they are performing poorly. |