Oracle Cloud Infrastructure Documentation

Set Up Using a Wizard

To enable you to swiftly get going with Java Management Service Fleets, the Prerequisite Wizard creates and checks required policies and other configurations, while the Log Configuration Wizard covers missing log configurations. This section describes how to use the Prerequisite Wizard and Log Configuration Wizard.

Note

The Prerequisite Wizard sets up JMS Fleets using the standard OCI resources. To customize the OCI resources being created, follow the Manual Setup.
Prerequisites:
  • You've signed up for an account with Oracle Cloud Infrastructure and have received your sign-in credentials.
  • You've logged in to the Oracle Cloud Infrastructure Console and selected Fleets under Java Management from the navigation menu.

Using the Prerequisite Wizard

Note

  • The wizard is designed to set up JMS prerequisites in first-level child compartments, and should be executed either from the root or first-level child compartments. Follow the Manual Setup to setup JMS prerequisites in other compartments.
  • The wizard may not correctly identify all prerequisite resources if some resources were manually configured earlier. To ensure the correct setup of the required resources, review the configuration steps in the Manual Setup and JMS Fleets Policy Statements.
  • You've OCI administrator privileges to run the Prerequisite wizard.
  • For current known issues, see Known Issues for Prerequisite wizard.
  1. Click Inspect Prerequisites. JMS will inspect your tenancy for the required policies and configurations.
    • If all the required resources are correctly configured, you'll see the message in the fleet dashboard - Prerequisites for JMS have been correctly set up for the compartment <compartment_name>. JMS is now ready to use.
    • If there are any missing resources, you'll see the message - Missing JMS prerequisites were detected while inspecting your tenancy. Set up the missing resources using the prerequisite wizard.
  2. Click Setup JMS to configure the missing resources.
  3. In the Setup JMS screen:
    1. In the Compartment for your JMS resources field, edit the compartment name, if required. The default value is Fleet_Compartment, which is created under the root compartment.
    2. In the User group for JMS Fleet administrators field, edit the user group name, if required. The default value is Fleet_Managers.
    3. In Monitor OCI instances field, Yes is selected by default, which allows you to monitor the OCI instances in your tenancy region. Click + Add row and select the compartment name to monitor the OCI instances in that compartment. You can add more than one compartment.
    4. In the Add policy for installation script field, select the Add dynamic policy for installation script checkbox if you want to set up OCI Linux instances using the installation script. See Set up OCI Linux instances for JMS Fleets.
    5. Click Review.

    The page displays all the Resources, Policy statements, Dynamic group statements, and OCID of the compartments that you had selected to monitor. Click Confirm to set up JMS in the compartment you specified in the Setup JMS screen.

After successful setup, a message is displayed in the Fleet dashboard - JMS set up is successful. Refresh the console to see the new compartment.

See JMS Fleets Policy Statements to view the policy statements that are created during JMS setup.

Using the Log Configuration Wizard

  1. The Log Configuration wizard is presented by JMS if at least one fleet in a compartment has missing log configurations. Click Enable log configuration to automate log configuration for all fleets with missing log configurations.

    You'll be presented with an error message if JMS isn't successful in setting up log configuration, and JMS will roll back any changes.

  2. Optional steps:
    1. Click View Details to view the fleets that have missing log configuration.
    2. Use the check box to define the scope of the operation.
    3. Click Enable log configuration to automate the creation of log configuration for all selected fleets. You'll be presented with a list of errors and their causes if JMS isn't successful. JMS will roll back any changes.
Note

To see the changes, you'll need to refresh the page or log off and then log on again.