The internal identifier of the deployed application installation.
The internal identifier of the deployed application. ApplicationKey will be identical for deployed applications with different applicationSourcePaths.
The name of the deployed application.
The full path to source WAR or EAR file for deployed application.
The type of the deployed application.
The approximate count of Java Server instances running the deployed application installations. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
The OCID of the related fleet.
Whether or not the deployed application is clustered.
Upper bound of the specified time period filter. JMS provides a view of the data that is per day. The query uses only the date element of the parameter.
The date and time the resource was first reported to JMS. This is potentially before the specified time period provided by the filters. For example, a resource can be first reported to JMS before the start of a specified time period, if it is also reported during the time period.
The date and time the resource was last reported to JMS. This is potentially after the specified time period provided by the filters. For example, a resource can be last reported to JMS before the start of a specified time period, if it is also reported during the time period.
Lower bound of the specified time period filter. JMS provides a view of the data that is per day. The query uses only the date element of the parameter.
Summarize usage information about an application deployed on Java servers including installation information during a specified time period. The main difference between DeployedApplicationInstallationUsageSummary and DeployedApplicationUsage is the presence of the applicationSourcePath. DeployedApplicationUsage provides only an aggregated view to the deployed applications without installation information. It therefore doesn\u2019t distinguish between applications with the identical deployment information deployed to different paths. DeployedApplicationInstallationUsageSummary contains installation information, and it\u2019s therefore possible to target actions.