Enabling Advanced Features

To utilize advanced features within your fleet, follow the steps below:

Enable advanced features using one of the following workflows:
- Create Fleet
  In the Advanced features section, you can either choose all options by using the Select all advanced features checkbox or select individual options.
- Fleet Actions
  - Select Edit Properties under More actions.
  - In the Advanced features section, you can either select all options by using the Select all advanced features checkbox or select individual options.
Note
- Advanced features should be turned on only on OCI instances and hosts covered by Java SE subscription terms. See the JMS Service Description for more details.
- Turning on advanced features might impact the performance of running applications in your fleet as JMS collects additional data from the applications and Java Virtual Machines (JVMs) in the fleet.
The Manage Advanced Features panel opens. Acknowledge and consent to the terms in the Acknowledgment section.
On agreeing to the terms in the Acknowledgment section, the Manage advanced features panel will present the Resources for advanced features section. OCI administrators, who have the highest privileges in OCI, can use the wizard to create these resources. Users belonging to user groups that don't have the necessary privileges to create the resources are required to create the resources manually by working with users from user groups who have the necessary privileges, like OCI administrators. Once they have manually created the resources, non-OCI admins will be able to enable the advanced features by selecting The policy and dynamic group are already created using the instructions in Enabling advanced features checkbox in the Resources for advanced features section.
In order to enable advanced features, JMS requires the following resources:
- Object storage bucket for Crypto event analysis, Performance analysis, JDK Flight recorder (JFR), and Java migration analysis to store the crypto event analysis report and JFR recordings:
  - Object storage bucket jms_<fleet_OCID>
  To manually create an object storage bucket, see create an object storage bucket.
- Log object for Crypto event analysis:
  - Crypto log object <fleet_name>_Crypto_log, a custom log for storing the summarized crypto events collected by JMS agents.
    Note
    
    The crypto log object is created only when you enable the Crypto Event Analysis.
  To manually create a log object, see create a log.
- Policy JMS_Advanced_Features with statements:
```
ALLOW dynamic-group JMS_DYNAMIC_GROUP to MANAGE object-family IN COMPARTMENT Fleet_Compartment
ALLOW group FLEET_MANAGERS to MANAGE object-family IN COMPARTMENT Fleet_Compartment
ALLOW resource jms SERVER-COMPONENTS to MANAGE object-family IN COMPARTMENT Fleet_Compartment
```
  Note
  
  See JMS Fleets Policy Statements for the description of these policy statements.
  To manually create a policy, see create a policy.
Click Continue.

Oracle Cloud Infrastructure Documentation