Using Oracle Java Cloud Service - SaaS Extension Control

Oracle Java Cloud Service - SaaS Extension Control is the management console that enables you to deploy and monitor hosted applications.

Topics:

Use Oracle Java Cloud Service - SaaS Extension Control to:

  • View the list of services you own, including the metrics and availability of each service

  • Deploy and redeploy applications

  • Start and stop applications on any of the services you own

  • View job logs to see recent activity

The primary Oracle Java Cloud Service - SaaS Extension Control user is the service administrator. The service administrator has privileges to access Oracle Java Cloud Service - SaaS Extension Control and can deploy and redeploy applications, as well as start and stop deployed applications.

Understanding Oracle Java Cloud Service - SaaS Extension Control

The Oracle Java Cloud Service - SaaS Extension Control displays usage metrics for a single Oracle Java Cloud Service - SaaS Extension instance.

Video icon Video

Video icon Tutorial

The metrics shown on Oracle Java Cloud Service — SaaS Extension Control include performance (availability and metrics), CPU/heap usage for the service, and response and load charts. It also shows available applications and libraries. You use this tool to deploy/redeploy and start/stop applications. As shown in the next illustration, the Oracle Java Cloud Service - SaaS Extension Control is divided into regions.

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.

For more information, see Restarting a Java Service Instance.

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

  • Service Version - the version number of the running Using Oracle Java Cloud Service - SaaS Extension.

  • Customer Disk Usage - the amount of disk space, in megabytes, the customer has consumed.

Servlets and JSPs

  • Active Sessions - Number of active sessions

  • Request Processing Time (ms) - Average number of servlet or JSP (Java Service Pages) invocations per minute in the last five minutes

  • Requests (per minute) - Average number of invocations per minute of the selected servlet or JSP in the last five minutes

JDBC Usage

  • Open JDBC Connections - Number of JDBC (Java Database Connectivity) connections currently in use

  • JDBC Connection Creates (per minute) - Number of database connections created per minute in the last five minutes

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.

From more information, see Viewing the Service and Application Logs.

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.

For more information, see Viewing the Activity Logs.

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.

  • View

    By using the View list, you can conveniently choose the columns to be displayed in the table.

    To test an application, click the Test Application icon associated with the application. This launches a dialog containing a list of URLs from which you can access the application. Click a given URL and the application appears in a new window.

  • Deploy New

    Once your application is ready for use, you can upload the application for deployment. The application goes through a number of checks to ensure compliance with Oracle standards. These checks include a virus scan and a whitelist validation.

    After the application passes these tests, deployment of the application begins. Note that deployment is asynchronous. You will be prompted to verify the status of the job submitted for deployment.

    You can check the status of the deployment by manually refreshing the Jobs table at the bottom of the page. You can also use the control on the top right corner of the table to set the auto-refresh interval for the table.

    Note: The welcome-app is pre-deployed to each service instance. It provides links to the SDK documentation, samples, blogs, and white papers, and more.

  • Delete Application

    When an application is no longer of value, delete it from the Oracle Java Cloud Service - SaaS Extension Control.

  • Redeploy

    Use this option when you upgrade or make changes to an application.

  • Start and Stop

    You can easily start and stop an application. Use these options after you have deployed the application.

    Note: If these applications are exposed to your external users, you need to inform these users of potential downtime when you stop the application.

For more information, see Managing Applications.

Libraries

Use this region to see the list of libraries available for this service.

  • View

    By using the View list, you can conveniently choose the columns to be displayed in the table.

  • Deploy New

    Once your library is ready for use, you can upload the library for deployment.

  • Delete Library

    When a library is no longer of value, delete it from the Oracle Java Cloud Service - SaaS Extension Control.

  • Redeploy

    Use this option when you upgrade or make changes to a library.

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.

Resolving Performance Issues

If you notice performance issues with your application, upgrading the underlying Using Oracle Java Cloud Service - SaaS Extension instance may help resolve the problem. Additional information is available in the service logs.

For more information on using the service logs, see Viewing the Service and Application Logs

The following are indications of performance issues:

  • Response times are slow or request throughput is high.
  • Server CPU or Java Heap memory usage is high.

Restarting a Java Service Instance

When you need to restart an instance, you can use the Restart Service option to restart your service. This restarts all managed servers in service’s domain.

One example of when you might need to restart an instance might be when adding an SSL certificate to the ssl trust-store requires a service restart for the changes to take effect. For more information, see Managing SSL Truststores.

To restart a Using Oracle Java Cloud Service - SaaS Extension instance:

  1. Click Restart Service Instance.

  2. From the Service Features menu, select Restart Service.

  3. Click Yes on the Confirmation dialog if you are you sure you want to restart service.

    Note: In some cases, it may be necessary to force the service to restart even if there are active jobs running. In that case, select the Force the service restart, even if there are active jobs? check box on the Confirmation dialog to force the restart.

  4. The service restart Confirmation dialog explains how a service restart works in single-server and multi-server environments. Note that there is a default minimum time-out of 10 minutes to allow active jobs to complete.

    The Confirmation dialog also has the following options:

    • In some situations, it may be necessary to force the service to restart even if there are active jobs running. Therefore, you can select the Force the service restart, even if there are active jobs? check box to force a service restart.

    • You can allow more time for active jobs to complete by increasing the Restart Timeout value longer than the 10-minute default value.

  5. Click Yes when you are ready to restart your service instance.

  6. When the service restart begins, there will be a "Restart Service Instance" log entry in the activity logs in the Jobs region and it will show a Status of Running. When the restart is complete, the Status column for the restart will indicate that, as shown in this illustration:

  7. When the service has restarted, the View Job Logs becomes active. To save or view the log for the restart process:

    1. Click View Job Logs.

    2. From the drop-down menu, select Restart Service.

      The download dialog associated with your specific browser appears.

    3. You can either save the log to disk or view it immediately in a text editor.

      This is a sample log for restarting single managed-server service:

      2014-07-08 15:15:07 PDT: Starting action "Restart Service"
      2014-07-08 15:15:07 PDT: Restart Service started
      2014-07-08 15:15:07 PDT: Restarting service: server restart timeout = 600000 ms ...
      2014-07-08 15:15:07 PDT: 
      Stopping server m0 : current state = RUNNING ...
      2014-07-08 15:15:09 PDT: Server m0 stopped
      2014-07-08 15:15:09 PDT: 
      Starting server m0 : current state = SHUTDOWN ...
      2014-07-08 15:16:16 PDT: Server m0 started
      2014-07-08 15:16:16 PDT: "Restart Service" complete: status SUCCESS
      Server m0 started

Restarting a Single Managed Server Service

For single managed-server services, there may be some service downtime until the managed-server is restarted. Therefore, options like Application Deploy, Start, and Stop on the Oracle Java Cloud Service - SaaS Extension Control are disabled while a service restart is in progress.

Restarting a Multiple Managed Server Service

For multiple managed-server services, there should not be any service downtime because the managed servers are restarted sequentially, as follows:

  • Restarts one server at a time.

  • Waits for each server to boot up before executing restart on the next server.

  • Restarts in sequence of m0, m1, m2, m3, etc.

  • Time-outs after waiting for three minutes for a server to restart, and then triggers a restart on the next server.

Managing Applications

You can deploy, redeploy, and delete an application using the Applications pane of the Home page. Use the View menu to add, remove, or reorder the columns in the Applications table on the Java Cloud Service — SaaS Extension Control home page.

Video icon Video

Video icon Tutorial

This illustration shows the Applications pane on the Java Cloud Service Control home page with a single application, welcome-app, deployed. This application is pre-deployed to each service instance. It provides links to the SDK documentation, samples, blogs, and white papers, and more.

For more information on managing applications, see:

Deploying an Application

Deploy applications from the Deploy Applications page, which you can access from the Oracle Java Cloud Service - SaaS Extension Control home page. Upon deployment, the application undergoes a series of security checks before it is actually deployed.

To deploy an application:

  1. Locate the Applications region in the Oracle Java Cloud Service - SaaS Extension Control page and click Deploy. The Deploy Application page appears.

  2. Enter a name for the application you are deploying, and then click Browse to search your local file steam for the application archive to be deployed. After locating the archive, click Deploy Application.

    Oracle Java Cloud Service - SaaS Extension Control uploads and deploys the selected WAR (Web Application Archive) file or EAR (Enterprise Archive) file.

Validating Deployed Applications

Once deployed, each application undergoes a series of security checks before it is actually deployed. These checks include a virus scan and a whitelist validation. For technical and security reasons, a small number of specific APIs are prevented from executing in Oracle Cloud. Once the application passes these tests, deployment of the application begins. To learn more, see About the Application Deployment Validation Process and Run-time Security.

Verifying Deployment Status

Deployment is asynchronous so you will be prompted to verify the status of the job submitted for deployment. You can check the status of the deployment by manually refreshing the Recent Activity table at the bottom of the home page. You can also use the control on the top right corner of the table to set the auto-refresh interval for the table.

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. For information about how to see the logs for a job, see Viewing the Activity Logs.

If whitelist validation fails, deploy is never run and so there will be no deploy log.

Deleting an Application

When an application is no longer needed, you can remove it from the Oracle Java Cloud Service - SaaS Extension Control.

To delete an application:

  1. Locate the Applications region in the Oracle Java Cloud Service - SaaS Extension Control
  2. Highlight the application you want to delete and click Delete Application.

Redeploying an Application

Redeploy an application whenever you upgrade or otherwise make changes to an application. In most situations you need to stop the application, make the necessary changes, and then redeploy the application.

To redeploy an application:

  1. Locate the Applications region in the Oracle Java Cloud Service - SaaS Extension Control.
  2. Highlight the application of interest and click Redeploy.

Starting and Stopping Applications

Once an application is deployed, you can start and stop the application as needed. If the application is exposed to external users, inform them of potential downtime before stopping the application.

To start or stop an application:

Note: If this application is exposed to your external users, you need to inform these users of potential downtime when you stop the application.

  1. Locate the Applications region in the Oracle Java Cloud Service - SaaS Extension Control.
  2. Highlight the application of interest and click either Start or Stop.

Managing Shared Libraries

Oracle Java Cloud Service - SaaS Extension Control enables you to deploy and manage any shared Java EE library and optional package supported Oracle WebLogic Server. This include both OOTB libraries and optional packages provided by Oracle Cloud, as well as any user -defined custom shared libraries or optional packages that are packaged using the standard process as supported by WebLogic Server

About Shared Java EE Libraries and Optional Packages

The shared Java EE library feature in WebLogic Server provides an easy way to share one or more different types of Java EE modules among multiple Enterprise applications.

A shared Java EE library is a single module or collection of modules that is registered with the Java EE application container upon deployment. It can be any of the following:

  • Standalone EJB module

  • Standalone web application module

  • Multiple EJB modules packaged in an enterprise application

  • Multiple web application modules package in an enterprise application

  • Single plain JAR file

WebLogic Server also supports optional packages, which provide similar functionality to Java EE libraries, allowing you to easily share a single JAR file among multiple applications. As with Java EE libraries, optional packages must first be registered with WebLogic Server by deploying the associated JAR file as an optional package. After registering the package, you can deploy Java EE modules that reference the package in their manifest files.

For more information about the shared Java EE libraries and optional packages supported in WebLogic Server, see Supported Deployment Units in Oracle Fusion Middleware Deploying Applications to Oracle WebLogic Server.

Creating Shared Java EE Libraries and Optional Packages

Oracle Java Cloud Service - SaaS Extension provides a number of OOTB libraries and optional packages. However, you can package your own content into a shared library or an optional package using the standard process as supported by WebLogic Server. You can then deploy, and then use the Oracle Java Cloud Service - SaaS Extension Control to deploy to them your Oracle Java Cloud Service - SaaS Extension instance.

For more information about, see Creating Shared Java EE Libraries and Optional Packages in Oracle Fusion Middleware Developing Applications for Oracle WebLogic Server.

Deploying, Redeploying, and Deleting Libraries

To deploy, redeploy, and delete a library in Oracle Java Cloud Service — SaaS Extension, use the Libraries pane of the Home page.

The Libraries pane lists all the shared libraries that are installed and available in the Oracle Java Cloud Service - SaaS Extension instance.

This table describes the columns in the Libraries table. Use the View menu to add, remove, or reorder the columns in the table.

Column Description

Library Name

Library or optional package name.

Specification Version

Specification version of the shared library.

Implementation Version

Implementation version of the shared library.

Type

Type of application archive associated with the library, such a WAR or EAR.

State

States whether the library is Active or Inactive?.

Deployment Type

Type of deployed library or optional package, such as Read-only or Custom.

Referencing Applications

Indicates the number of applications that are referencing the library, if any.

For library deployment, redeployment, and deletion instructions, see:

Deploying a Library

Use the Deploy Library page of Oracle Java Cloud Service - SaaS Extension Control to deploy libraries.

Once deployed, a library goes through a number of checks to ensure compliance with Oracle standards. o deploy a library, do the following:

  1. Locate the Libraries region in the Oracle Java Cloud Service - SaaS Extension Control and click Deploy New. The Deploy Library page appears.
  2. Click Browse to search your local file system for the library archive to be deployed. After locating the archive, click Deploy.

    Oracle Java Cloud Service - SaaS Extension Control uploads and deploys the selected library archive. Once deployed, a library goes through a number of checks to ensure compliance with Oracle standards.

Redeploying a Library

Use the Deploy Library page of Oracle Java Cloud Service - SaaS Extension Control to redeploy libraries.

After you have upgraded or otherwise make changes to a library, you need to redeploy it. Click Deploy New or Redeploy as necessary.

Deleting a Library

Use the Deploy Library page of Oracle Java Cloud Service - SaaS Extension Control to delete libraries.

When a library is no longer needed, click Delete Library to remove it from Oracle Java Cloud Service - SaaS Extension Control.

Viewing Application-Specific Statistics

The Application Home page shows how well the application is working. Data shown includes availability and performance metrics, as well as version, state of the application, and application URLs for testing the application.

From the Application menu, you can: start, stop, redeploy, and delete the application, as described in Operations. There is also an option for monitoring the performance of ADF applications, as described in Monitoring the Performance of ADF Applications

To view the Application Home page:

  1. Locate the Applications region on the Oracle Java Cloud Service - SaaS Extension Control
  2. Click the Name of the application of interest. The application's home page appears.

Understanding the Metrics and Operations on the Application Home Page

The Application Home page contains system availability and performance metrics, as well as version, state of the application, and application URLs for testing the application.

The application home page contains the following metrics and control operations:

Tip:

If your application is running slowly, consider upgrading your service to the next performance level.

Metrics

This table describes the server and JSP metrics for the application.

Metric Description

Active Sessions

This metric shows the number of active sessions for the selected application.

Request Processing Time (ms)

The average amount of time (in milliseconds) spent executing servlets and/or JSPs (Java Service Pages) over the last five minutes

Requests per minute

The average number of servlet and JSP (Java Service Pages) invocations per minute, averaged over the past five minutes.

This table describes the work manager metrics for the application.

Metric Description

Requests (per minute)

The number of work manager requests processed per minute, averaged over the past five minutes.

Pending Requests

The number of work manager requests waiting in the queue.

This table describes the URL option for the application.

Metric Description

URL

Click a URL to go to the application's web page.

Operations

This table describes the operations available from the Application menu.

Operation Description

Start

Use this option after you have deployed the application. Note: If this application is exposed to your external users, you need to inform these users of potential downtime when you stop the application.

Stop

Use this option after you have deployed the application and you need to stop it. Click Yes on the confirmation page to stop the application.

Note: If this application is exposed to your external users, you need to inform these users of potential downtime when you stop the application.

Redeploy

Use this option when you are upgrading or otherwise making changes to an application. In most situations, you would stop the application, make the requisite changes, then redeploy the application.

Delete Application

When an application is no longer of value, delete if from the Oracle Java Cloud Service - SaaS Extension Control.

ADF Performance

Use this option to examine performance information of your application's web pages that may help you to identify problems that may be slowing down applications. See Monitoring the Performance of ADF Applications.

Monitoring the Performance of ADF Applications

Use the ADF Performance page to monitor the performance of Oracle ADF applications deployed to an Oracle Java Cloud Service - SaaS Extension instance.

The ADF Performance page contains sub-tabs for viewing performance information about active application module pools and task flows, that can help you to identify problems that may be slowing down applications.

By default, the performance charts on the Application Module Pools and Task Flows pages display data for the preceding day. However, at the top of each page, you can select a different time interval (Past 2 hours or Past 15 minutes), use the Slider to select another time interval (from 08:00 AM to 08:30 AM), or use the Calendar to enter another date and time.

Tip:

If your ADF application is running slowly, consider upgrading your service to the next performance level.

Understanding ADF Application Module Pool Metrics

The Application Module Pools page displays active application module pools, which is a collection of application module instances of the same type. Data on this page includes size and performance information about pool connections.

The Application Module table enables you to filter the list by Application Module name or apply an ascending/descending sort to any of the following columns. You can click View to specify the columns to display or reorder the columns in the table.

Metric Description

Application Module

Name of the active application module instance in the pool. Click an application module to display additional information about it, for example, Requests, Pool Use, and Instances.

Total Requests

Number of requests that were made for an application module in the pool during the selected time interval.

Average Creation Time (ms)

Average time (in milliseconds) required to complete a request for an application module in the pool during the selected time interval.

Activations

Number of times session state is restored when an application module in the pool is reused for requests from a different session during the selected time interval.

Passivations

Number of times session state information is saved to the passivation store when an application module in the pool is reused for requests from a different session during the selected time interval.

Average Response Time (ms)

Average time (in milliseconds) required to respond to a request for the application module during the selected time interval.

Pool Check Out Failures

Number of times an application module failed to load from the pool.

Pool Check Outs

Number of times an application module was loaded from the pool.

Pool Check Ins

Number of times an application module was released back into the pool.

Referenced Modules Reused

Number of reused application module instances in the pool that are available for the next request from the session that used them last before releasing them back into the pool.

Referenced Modules Recycled

Number of reused application module instances in the pool that available for requests by other sessions.

When you select an Application Module in the tabular view, the details section shows Requests, Pool Use, and Instances charts that allow you to compare related metrics for the selected time interval. For each chart, you can choose the Table View link to view the actual metric data.

Understanding ADF Task Flow Metrics

Task flows provide a modular and transactional approach to navigation and application control. Use the Task Flows tab to monitor the task flows used in the current Application and Metrics for each task flow.

The Taskflow table reports each taskflow that has been invoked at least once during the specified time period. Therefore, if a taskflow has not been invoked in a specified interval (e.g., "2 hours"), then it will not be displayed.

You can filter the list by Taskflow name or apply an Ascending/Descending Sort to any of the following metrics.

Metric Description

Taskflow Name

Name of the active taskflow.

Total Entered

Total number of times a Taskflow was entered during the selected time interval

When you select a Taskflow in the tabular view, the details section shows a chart that allow you to compare related metrics for the selected time interval. For each chart, you can choose the Table View link to view the actual metric data. In addition to the default Entered Taskflows metric, you can use the drop-down menu to select other metrics to display in the chart:

  • Activated Taskflows – Records the number of instances of the taskflow that are currently active.

  • Entered Taskflows – Records the taskflow no matter what mechanism was used to enter it.

  • Invoked Taskflows – Only records taskflows that were invoked in a region or invoked directly on a URL.

  • Taskflow Invoked Time – The average time taken to invoke a taskflow. Typically, this value includes processes like permission checks, invoking any taskflow initializer (EL expression), evaluating input parameters, etc., where a large value might indicate a problem.

Viewing the Activity Logs

Activity logs show the status and progress of activities, such as application deployment and service restarts.

You can access activity logs from the Oracle Java Cloud Service - SaaS Extension Control Jobs region, which is at the bottom of Oracle Java Cloud Service - SaaS Extension Control.

When you choose a Job ID in the Oracle Java Cloud Service - SaaS Extension Control Jobs section of the Oracle Java Cloud Service - SaaS Extension Control home page, the View Job Logs drop-down menu becomes active, and you can choose from the following list of activity logs:

  • Virus scan

  • Application Whitelist Validation

  • WLS Compile

  • Cloud Compile

These logs are text documents that you can either open or save, and they are the result of background jobs that ran against the application to check relevant information, for example, to determine whether the file contains a virus or could otherwise cause problems. These background jobs run asynchronously.

Viewing the Service and Application Logs

All application logs, along with certain service logs, are available for troubleshooting purposes by using either the Oracle Java Cloud Service - SaaS Extension Control or with the command-line interface provided through Oracle Java Cloud Service - SaaS Extension SDK.

Note:

For more information on using the Oracle Java Cloud Service - SaaS Extension command-line interface, refer to Using the Command-Line Interface to Monitor Oracle Java Cloud Service - SaaS Extension.

To view service/application log messages with Oracle Java Cloud Service - SaaS Extension Control, click the View Log Messages link in the Servlets and JSPs area of the Performance Summary pane. That link displays the Log Messages - <service-name> page, where you can select a date range, message type, and so on, and can view or export messages to a file, as shown in the following illustration.

To view log messages:

  1. From Oracle Java Cloud Service - SaaS Extension Control, click the View Log Messages link in the Servlets and JSPs area of the Performance Summary pane.
  2. If necessary, Expand Search and specify the date range, message types, message text, and application name.

    The Log Messages table appears.

  3. To view the details of a message, select the message.

    By default, the messages are sorted by time, in ascending order. You can sort the messages by the any of the columns, such as Message Type, by clicking the column name.

    For information on the Log Messages page, see Understanding the Search Fields and Results Table on the Log Messages Page.

Understanding the Search Fields and Results Table on the Log Messages Page

All application logs, along with certain service logs, are available for troubleshooting purposes using the Oracle Java Cloud Service - SaaS Extension Control. Here, this information is presented on the Log Messages page.

This table describes the fields you use to define the search criteria for locating messages you want to see.

Field Description

Message Types

The log message type can include any of combination of Incident Error, Error, Warning, Notification, Trace, and Unknown.

Record Contains

Type the text that you are searching for. You can add multiple text elements using a comma to separate the elements. An OR operation will be applied between the text elements.

Text should be case sensitive. There is no limit to the number of characters in the field.

Name

Name of deployed Java application.You can add multiple application names using a comma for separation. An OR operation will be applied among the application names.

Search

Sort the messages by log file types using one of these sort options:

  • All Logs

  • Log4J Logs

  • System Logs

This table describes the columns in the Log Messages table. Use the View menu to add or remove columns from the table. Click Export Messages to File to save the messages. A file browser opens and here you can choose a file name to export the messages.

Metric Description

Timestamp

Date and time when the message was generated. This reflects the local time zone.

Message Type

Type of message. Possible values are: Incident Error, Error, Warning, Notification, and Trace. In addition, the value Unknown may be used when the type is not known.

Message Level

Message level, represented by an integer value, that qualifies the message type. Possible values are from 1 (highest severity) through 32 (lowest severity).

Message

Text of the error message.