Planning an Applications Environment

Options to consider when you set up your environment.

When you create an environment, you are presented with several decisions to make about your environment, including choices that impact the location, the type of environment, and access. Not all application services present the same choices. This topic describes the most common things to consider. Some options can be changed after you have created the environment, but some, such as region can't be changed after you create the environment.

Choosing a Region for an Environment

The region is the geographical location that your environment is provisioned in. Oracle Cloud Infrastructure supports regions around the world and when you signed up for a tenancy, you selected a home region where your tenancy is located. If you have not subscribed to additional regions, your home region is selected by default. You can choose to provision your environment in any region supported by Oracle Cloud Infrastructure and your application. The region can't be changed after you create the environment.

Things to consider when selecting a region:

  • The geographical location of your organization.
  • The geographical location of your customers. Be aware of data privacy laws that might require customer data to be maintained within specific geographical borders.
  • The regions supported by the services you wish to use. For a list of supported regions by service, see Cloud Regions.

For a list of all regions available in Oracle Cloud Infrastructure, see Regions and Availability Domains.

For information on how to enable more regions for your tenancy, see Managing Regions.

For information on how to change the region you are working in and viewing in the Console, see Switching Regions.

Selecting the Environment Type or Instance Type

The environment types available to you are determined by the SKUs you purchased. Typically, your subscription includes a production environment and at least one non-production environment. Some applications, provide instance type options, instead. Oracle Maxymiser provides the options of "Maxymiser" and "Recommendations".

Before the environment types are available for selection, you must have activated the subscription activated the subscription in the tenancy and you must have permissions to read subscriptions.

Assigning an Environment Administrator

When you create an environment, you assign an administrator for the environment. When the environment is provisioned, this user is the default Administrator of the applications. Different applications might refer to this default administrator by different names (for example, Service Administrator). See the following table for more details about a specific application.

Application Suite Required Information for Environment Creation Role Assigned in Application

Email address

The email address entered must be for an existing user in the identity domain.

Account Administrator

For more information about roles in Maxymiser see User roles and permissions (on the Oracle Maxymiser Help Center).

Oracle Commerce

Email address

The email address entered must be for an existing user in the identity domain.


For more information about roles in Commerce, see Understand role-based access control in Using Oracle Commerce.

Oracle Transportation and Global Trade Management Cloud

Email address

The email address entered must be for an existing user in the identity domain.

Service Administrator

For more information about roles in .

Choosing a Compartment

A compartment is a logical grouping of resources for controlling access to those resources. By default, your tenancy has one compartment, called the root compartment.

If you have a simple setup and don't need to separate your resources, you can place all your resources in the default root compartment of the tenancy (sometimes referred to as "putting resources in the tenancy"). If you have multiple applications or multiple types of environments, you might consider creating multiple compartments to clearly define access for each. For example, if your subscription includes both production and test environments, you can restrict access to each environment to different groups of users by creating a Test compartment and a Production compartment and placing the environments in the different compartments. You can then write a policy that allows one group of users access to only the Test compartment, reserving access to the Production compartment to another group of users.

When you create an environment, if you don't specifically choose a compartment (or if your organization has not set up multiple compartments) the environment will be created in the root compartment of the tenancy (displayed in the Console as "<tenancy_name> (root)"). If your organization chooses to set up compartments later, you can move the environment to a different compartment.

If your setup stays simple, you can continue to use the default root compartment for any additional resources you set up. If you'd like to learn more about compartments, see Learn Best Practices for Setting Up Your Tenancy.

Planning Encryption Options

If you purchased a subscription that includes Oracle Break Glass, you can encrypt your environment using a key that you manage, referred to as a customer-managed key. You create and manage keys using the OCI Vault service. For more details, see Customer-Managed Keys for Oracle Break Glass.

Applying Tags

Oracle Cloud Infrastructure Tagging allows you to add metadata to resources, which enables you to define keys and values and associate them with resources. You can use the tags to organize and list resources based on your business needs.

When you create a resource, such as an environment, you have the option to apply tags to it. You can also add tags later, after you have created a resource.

For more information about how you can use tags, see Resource Tags.