The Fleet-unique identifier of the related application.
Additional fields to include into the returned model on top of the required ones. This parameter can also include 'approximateApplicationCount', 'approximateInstallationCount' and 'approximateManagedInstanceCount'. For example 'approximateApplicationCount,approximateManagedInstanceCount'.
The OCID of the Fleet.
The distribution of the Java Runtime.
The Fleet-unique identifier of the related Java Runtime.
The security status of the Java Runtime.
The vendor of the Java Runtime.
The version of the Java Runtime.
The maximum number of items to return.
The Fleet-unique identifier of the related managed instance.
The client request ID for tracing.
The operating system type.
The page token representing the page at which to start retrieving results. The token is usually retrieved from a previous list call.
RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made
The field to sort JRE usages. Only one sort order may be provided. Default order for timeFirstSeen, timeLastSeen, and version is descending. Default order for timeFirstSeen, timeLastSeen, version, approximateInstallationCount, approximateApplicationCount and approximateManagedInstanceCount is descending. Default order for distribution, vendor, and osName is ascending. If no value is specified timeLastSeen is default.
The sort order, either 'asc' or 'desc'.
The end of the time period during which resources are searched (formatted according to RFC3339).
The start of the time period during which resources are searched (formatted according to RFC3339).
Click here to see how to use SummarizeJreUsageRequest.