Managing Environments

Learn how to manage the environments where your Fusion Applications are deployed.

Before You Create an Environment

Before you create an environment, ensure the following:

You have the correct permissions to manage environments. See Managing Oracle Cloud Users with Specific Job Functions.
You or another administrator has created an environment family for this environment. See Managing Environment Families.
You're familiar with the information in Planning an Environment.

Understanding the Health Status and Lifecycle State

During the lifecycle of a Fusion Applications environment, it can display different states. The state of the environment is independent from the status of the applications running on the environment. This topic explains the status values and what they mean for the availability of your applications.

When you view the list of environments on the Environments list page, you see two status indicators:

Health status
You can think of the health status as the status of your Fusion Applications. As long as the Health status is Available, your end users can access and use the running applications.
Lifecycle state is the state of the Fusion environment.
Before you can perform lifecycle updates, the Health status must be Available and the Lifecycle state must be Active.
End users can still access the applications when some updates are occurring on the environment, even though modifications on the environment are disabled (such as when the Lifecycle state is Updating because you made updates to environment settings by adding an access control list (ACL) or a language pack, for example).

Health Status

The following table shows the possible values for an environment's Health status:

Status	Description	Fusion Appplications Available?
Available	The environment is available. This is the normal working status.	Yes
Maintenance in progress	The environment is undergoing planned maintenance. To view the estimated completion time of the maintenance, select Maintenance on the environment details page.	No
Refresh in progress	The environment is undergoing a refresh from another environment. When the refresh is complete, the status returns to Available.	No
Not Applicable	When the Lifecycle state of the Fusion environment is Creating, Failed, Disabled, Deleting, or Deleted.	No
Unavailable	The environment is unavailable. Contact Oracle Support for more information.	No

Environment Lifecycle State

The following table shows the possible values for an environment's Lifecycle state:

Status	Description	Fusion Applications Available?
Creating	The environment resource is being created.	No
Active	The environment resource is available.	Yes
Updating	The environment resource is updating. This state occurs when configurations or changes are being implemented, such as network access control rules, language packs, or updating an administrator. In this state, the applications are still available, but you can't make any other changes to the environment resource settings (such as editing the maintenance schedule or adding tags) until this update is complete.	Yes
Disabled	This state occurs when the managed key has been disabled. All users are forced out of the application. The key must be enabled before the environment can be restarted again. For more information, see Disabling and Enabling Keys.	No
Deleting	The environment resource is in the process of being deleted.	No
Deleted	The environment resource has been deleted.	No
Failed	The environment resource creation failed.	No

Understanding Work Requests

Some updates that you make to the environment aren't immediate. When you make a change, such as adding an administrator, a work request is initiated to make the update to the environment. While the work request is running, the environment's Lifecycle state changes to Updating and the Health status changes to Unknown. You can't make additional updates to the environment until the work request completes.

To view the status of a work request, select an environment from the Environments list page and then select Work requests. While the work request is running, the fields that aren't updateable are unavailable.

If an operation fails, the work request can provide details to help you troubleshoot the issue or provide information to Oracle Support.

When Environment Modifications Are Not Allowed

There will be times when you won't be able to update a Fusion Applications environment. You might see a message on the environment details page stating that updates to the environment are disabled, or else a message displays after you attempt an update.

A banner message displays when maintenance is in progress, or when the environment is updating. A message also displays when the environment is being created, has been deleted, or is in the state of deleting. You can make updates to the environment when the maintenance or current update is complete, unless the environment is unavailable due to deletion.

Type of update or change	Environment change cut-off time
Add an administrator Add language packs Add tags Rename the environment Update network access control lists (ACLs) Move the environment to a different compartment Add an integration	4 days before scheduled maintenance
Refresh the environment	5 days before scheduled maintenance
Update maintenance policy	10 days before scheduled maintenance

If you try to make one of these updates during the period in which they're disabled, you'll get an error letting you know that the environment is within the maintenance window. Wait until the scheduled maintenance is complete to make these updates.

When maintenance is in progress, you'll see a banner across the details page of the environment letting you know that updates are disabled until the maintenance completes.

Creating an Environment

If your tenancy doesn't yet have any environment families or environments, you can use the Fusion Applications Environment Setup Wizard to streamline the initial setup process. If you already have an environment family set up in your tenancy, use this procedure to create environments.

Before you begin, ensure that you understand the options you'll select when you create the environment.

To create an environment

Navigate to the Applications home page of the Console. Under Subscriptions, in the Fusion Applications tile, select Go to service.
On the Fusion Applications Overview page, select Environment families and then select the environment family where you want to create the environment.
On the environment family's Environments page, under Environments, select Create environment.
Enter a friendly name for the environment that's easy to identify. Avoid entering confidential information.
The environment family is already preselected for you.
Tip

If you launched this workflow from another starting point, you're prompted to select the environment family. If you don't see the environment family in the list, you might need to change the compartment that you're viewing. Under Advanced options, you can select a different compartment.
Select the environment type: Production, Test, or Development. For more information, see About Environment Types.
Review the applications to be installed in this environment. Select the expand arrow to see details about each subscription. The applications included are defined by the environment family selection and can't be changed here.
Add Fusion Applications administrator credentials.
This administrator is the service administrator for the applications in this environment, and can create other applications users.
1. Enter the administrator's first and last name.
2. Enter the administrator's email address.
3. To have the administrator sign in with their email address, leave the Use the email address as the username toggle selected.
4. To have the administrator sign in with their username, clear the Use the email address as the username toggle and, in the Username field, enter the username that the administrator will use to sign in to the Console.
(Optional) In the Tags region, select Add tag to add tags to the environment.
If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, skip this option or ask an administrator. You can apply tags later.
Select Advanced options to configure additional settings. If you don't want to configure these options now, select Create environment. The environment will be ready to use after several minutes, when the environment health status shows as Available.
All advanced options can be edited after environment creation except the DNS prefix. To customize the DNS prefix, go to the optional Networking step below.
(Optional) Expand the Maintenance region to configure the environment's maintenance schedule.
You can accept the default schedule from the environment family, or you can edit the monthly patching and patching cadence for this environment. For more information about these options, see Understanding Environment Maintenance.
To edit the settings, select Custom.
- Monthly patching – when enabled, this option delivers bug fixes every month so you don't have to wait until the quarterly update. Only bug fixes are delivered through monthly patching. If you don't select this option, bug fixes are delivered with quarterly maintenance updates. The default state of Enabled or Disabled is determined by the environment family, but you can change it.
  Note
  
  Monthly patching is mandatory and can't be disabled in the following cases:
  - If the environment family contains an active subscription of Oracle PCI Compliance Cloud Service SKU B93112. This is to ensure compliance with the Payment Card Industry (PCI) Security Standards.
  - If you're a US or UK Government customer. This is to ensure compliance with the regulatory frameworks.
- Patching cadence – maintenance can be performed in the first week of the month (non-production) or in the third week of the month (production). Typically, you would select Non-production for test and development environments, and Production for production environments. See Types of Maintenance and Schedules for more details.
(Optional) Expand the Compartment region to select a different compartment in which to create this environment. Select the new compartment from the list.
(Optional) Expand the Languages region to add language packs to this environment. English is selected by default and can't be deselected. You can select up to 2 languages at provisioning time, and you can add more languages after the environment is created. For more information about language packs, see Understanding Language Packs.
(Optional) Expand the Networking region to customize the DNS prefix and add network access control rules.
(Optional) Add a DNS prefix to customize the URL you use to access the Fusion Applications home page. The prefix can be 1-20 characters. As you enter the prefix, the URL preview is displayed.
(Optional) Add network access control rules to restrict network access to your environment. You can allow access only from a specific CIDR block range or from a virtual cloud network.
1. Under Network access control rules, select Create rule.
2. On the Create network access control rule page, select the IP notation type.
  1. If you select CIDR block, enter the CIDR block range.
  2. If you select Virtual Cloud Network, select the VCN. If the VCN is located in a different compartment than the one you're creating the environment in, select the compartment.
  3. If you select Virtual Cloud Network (OCID), specify the OCID of the VCN.
  4. To further restrict access to a CIDR block within a VCN, enter the VCN CIDR block range.
3. Add a description. Avoid entering confidential information.
4. To add additional rules, select Add rule.
5. When finished adding rules, select Create rule.
(Optional) To disable content acceleration, turn off the Enable internet cache toggle. You must disable this option if:
- You're configuring this environment for private access over VPN or FastConnect. For more information, see Securing Network Access to a Fusion Applications Environment.
- You plan to enable support for IPv6 in this environment. See the next step.
(Optional) To enable IPv6 networking ingress in this environment, verify that the Enable IPv6 toggle is turned on. (This feature is currently available in government regions only.)
Important

Before enabling the IPv6 setting, review the usage restrictions in Enabling Support for IPv6.
(Optional, available only with the purchase of specific subscriptions) Expand the Encryption region to encrypt the environment with customer-managed keys. For details, see Customer-Managed Keys for Oracle Break Glass.
After configuring advanced options, select Create environment.
While the environment is provisioning, the health status of the environment is Not applicable and the lifecycle state is Creating. The environment is ready to use when the health status is Available.

Environment Management Tasks

To list environments

Navigate to the Applications home page of the Console. Under Subscriptions, in the Fusion Applications tile, select Go to service.
Alternatively, open the navigation menu and select My Applications. Under Applications, select Fusion Applications.
On the Fusion Applications Overview page, select Environments.
All environments in all regions are listed.

If you don't see the environments you're expecting, ensure that you're viewing the correct compartment and region.

To view environment details

After the environment is created, you can view the details in the Console.

Tip

To get a guided tour of the environment details page: On the Fusion Applications Overview page, under Guided learning, find the Environment details page tile, and select Start tour. You're provided step-by-step assistance to view the details of an environment. During the tour, you can navigate to the previous or next step by using the Back or Next button. At the end of the tour, select Done. To exit the tour at any point, select Close. You can submit feedback about the guided tour after you close or complete it.

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.

The details page displays information about the environment and provides access to resources associated with the environment. See the subsequent topics in this section for more information about the resources.

Environment information includes:

Name of the compartment where the environment is located.
Environment family that this environment belongs to. Select the name to view the family details.
Application URL for accessing the applications.
The Oracle Cloud Identifier (OCID) of the environment. This identifier is useful when logging service requests.
Type of environment (development, production, or test).
System name of the environment.
The Fusion Applications version.
Create date.
The next scheduled maintenance date. See also To check for upcoming maintenance.
The health status and lifecycle state. See Understanding the Health Status and Lifecycle State.
The associated identity domain.

To add or remove Fusion administrators

You can add an administrator in one of the following ways:

Follow the step-by-step guide on the user interface of the Console: On the Fusion Applications Overview page, under Guided learning, find the Fusion administrator tile, and select Add administrator. You're provided step-by-step assistance to perform the task. To exit the task at any point, select Close. You can submit feedback about the guided task after you close or complete it.
Use the following procedure in the Console:
Note

You can add administrators either through the Fusion Applications Security Console or through the environment details page of the Oracle Cloud Console. When you add the administrator using the environment details page described in this procedure, you must also perform a step in the Fusion Applications Security Console to import the user (see Importing Users into Applications).
Before you add a Fusion administrator, you must ensure that the administrator doesn't already exist in the environment's identity domain or hasn't been added through Creating a User in the Security Console.
1. On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
2. On the environment details page, select Fusion administrators.
3. Select Add administrator and complete the required fields.
4. Select Add administrator.
5. Sign in to your Oracle Applications Cloud service environment as the service administrator, and in the Setup and Maintenance work area, perform the Run User and Roles Synchronization Process task. The procedure is identical regardless of which Fusion Applications you have provisioned in your environment. To reference the task in a specific guide, you can go to:
  - Securing HCM: Synchronize User and Role Information
  - Securing SCM: Synchronize User and Role Information
  - Securing ERP: Synchronize User and Role Information

To remove an administrator, follow these steps:

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Fusion administrators.
To remove an administrator, select the Actions menu (three dots) and then select Delete. Confirm when prompted.
You can't delete the primary administrator.

To reset the Fusion administrator password

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Fusion administrators.
To reset an administrator's password, select the Actions menu (three dots) and then select Reset password.
Select Continue password reset.
Enter the username or email, and select Forgot Password?
Complete the steps to reset your password.
An email with instructions for resetting the password is sent to the email address for the user.

To view or add language packs

You can add language packs to an environment. For more information about language packs, see Understanding Language Packs. Note that you can't remove a language pack.

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Language packs.
Select Add.
- On the Install language packs panel, select the language to include. You can add two language packs at a time.
- Select Install.
- Follow the confirmation prompts.

To check for upcoming maintenance

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Details.
The maintenance schedule details are displayed:
- Next maintenance displays the date and time of the next scheduled maintenance.
- Select View to see more maintenance details, or select the Maintenance tab.
  Details are displayed when Oracle finalizes the content of the scheduled maintenance.

To edit the maintenance schedule of an environment

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Maintenance.
Select Edit maintenance.
Under Schedule type, select Environment family to use the environment family schedule.
Or, to set up specific maintenance schedule options for this environment, select Custom.
If you select Custom, you can change the following:
- Monthly patching: Activate or deactivate monthly patching for this environment. Monthly patching delivers bug fixes every month so you don't have to wait until the quarterly update. New features and other updates are still delivered quarterly.
  Note
  
  Monthly patching is mandatory and can't be disabled in the following cases:
  - If the environment family contains an active subscription of Oracle PCI Compliance Cloud Service SKU B93112. This is to ensure compliance with the Payment Card Industry (PCI) Security Standards.
  - If you're a US or UK Government customer. This is to ensure compliance with the regulatory frameworks.
- Patching cadence: Maintenance can be performed in the first week of the month (non-production cadence) or in the third week of the month (production cadence). Typically, you would select Non-Production for test and development environments, and Production for production environments. See Types of Maintenance and Schedules for more details.
Select Save changes.

To edit network access control rules

You can add, update, or delete access control rules for the environment.

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Networking.

Update a rule

Find the rule you want to update, select the Actions menu (three dots), and then select Update.
Update the fields in the rule and then select Save changes.

Add a rule

You can add a rule in one of the following ways:

Follow the step-by-step guide on the user interface of the Console: On the Fusion Applications Overview page, in the Network access control rule section of Guided learning, select Add rule. You're provided step-by-step assistance to perform the task. To exit the task at any point, select Close. You can submit feedback about the guided task after you close or complete it.
Or, use the following procedure on the environment details page:
1. On the environment details page, select Networking.
2. Under Access control rules, select Create rule.
3. On the Create network access control rule page, select the IP notation type:
  - To add a rule to allow access only from a CIDR block range, select CIDR Block, then enter the CIDR block range.
  - To add a rule to allow access only from a virtual cloud network (when you know the VCN name), select Virtual Cloud Network, then select the VCN from the list. If the VCN is located in a different compartment than the environment is in, select the different compartment. To further restrict access to only a CIDR block within that VCN, enter the VCN CIDR block range.
  - To add a rule to allow access only from a virtual cloud network (when you know the VCN OCID), select Virtual Cloud Network (OCID), then enter the VCN OCID. To further restrict access to only a CIDR block within that VCN, enter the VCN CIDR block range.
4. Select Create rule.

Delete a Rule

Find the rule you want to delete, select the Actions menu (three dots), and then select Delete.
Select Delete to confirm deletion.

To disable or enable internet cache

For information about when to disable internet cache, see Enabling Support for IPv6 and Securely Accessing Fusion Applications.

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Networking.
Under Networking details, the current Internet cache setting is displayed.
Select Edit to update the setting.
Select Save changes.

To enable or disable IPv6 support

You can configure a Fusion environment with dual-stack IPv4 and IPv6 connectivity by enabling support for IPv6 networking ingress. This feature is currently available in government regions only.

Important

Before changing the IPv6 setting, review the usage restrictions in Enabling Support for IPv6.

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, select Networking.
Under Networking details, the current IPv6 setting is displayed.
Select Edit to update the setting.
Select Save changes.

To rename an environment

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, from the Actions menu, select Rename.
On the Rename environment panel, enter the new name. The name can contain only letters, numbers, dashes, and underscores.
Select Save changes.

To move an environment to a different compartment

Note

When you move an environment to a different compartment, it's accessible only to those users who have permissions to access resources in the new compartment. Also, moving the environment doesn't move the instances of your integrated applications. If you want your integrated applications (such as Visual Builder or Digital Assistant) to reside in the same compartment as the environment, you must move those separately by navigating to the details page of each instance.

To move an environment to a different compartment:

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, from the Actions menu, select Move environment.
On the Move resource panel, select the destination compartment.
Select Move resource.

To delete a development environment

Self-service delete for environments is only supported for non-production development environments.

Note

Integrated services that were auto-provisioned with the environment are deleted. Services integrated through self-service integration are detached from the environment, but aren't deleted.

The identity domain for the environment isn't deleted.

To delete a development environment:

On the Environments list page, select the environment that you want to work with. If you need help finding the list page, see To list environments.
On the environment details page, from the Actions menu, select Delete.
If the development environment is undergoing a lifecycle operation, the Delete option isn't enabled. Wait until the operation is completed and try again.
On the Delete Fusion Applications environment panel, type the name of the development environment and select Delete.

When the request is accepted, the environment state is updated to Deleting.

To delete a production or test environment

Self-service delete for non-development environments (production and test) isn't supported. To delete a non-development environment, open a Support Request.

Oracle Cloud Infrastructure Documentation