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.

Before You Create a Demo Environment

Before creating a demo environment, ensure that:

You have already purchased a separate Oracle Fusion Demonstration Environment Cloud Service - Each SKU. For more information, contact your Oracle Customer Success Manager or sales representative.
You have access to the Cloud Console.
An environment family exists for this environment. See Managing Environment Families.

For more information, see About Demo Environments.

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 ingress 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 ingress 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.

Prerequisites

See Before You Create an 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, Development, or Demo. 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. 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.
Note

This isn't applicable for demo environments.
(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.
Note

Demo environments come preinstalled with all available languages.
(Optional) Expand the Networking region to customize the DNS prefix and add ingress and egress access control rules.
(Optional) Add a DNS prefix to customize the domain you use to access the Fusion Applications home page. The prefix can be 1-20 characters. As you enter the prefix, the domain preview is displayed.
You can configure a prefix now or later. To configure it later, you'll have to create a vanity domain. See Add a custom prefix to the application domain.
(Optional) Add ingress 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. If you don't create any rules, all inbound traffic is allowed.
1. Under Ingress access control rules, select Create rule.
2. On the Create ingress 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 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.
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) Add egress access control rules to allow additional outbound network traffic from your environment to external destinations.
You can connect to any IP and CIDR range on a specific port or range of ports.
Note

Each environment comes with a read-only default egress rule that allows outbound traffic to well-known ports only (22, 25, 80, 443, 465, 587, 631, 993). If you don't add any additional egress rules, this is the only outbound traffic that will be permitted from this environment. The rules you create support only TCP protocol.
1. Under Egress access control rules, select Create rule.
2. On the Create egress access control rule page, enter the destination in CIDR notation. You can enter:
  - A single IPv4 address with a /32 subnet mask
  - A CIDR range
    Note
    
    CIDR ranges that cover only private networks (per RFC1918) aren't supported.
  - 0.0.0.0/0
    This allows outbound traffic to all IPv4 addresses.
3. Under Port, select either Single port or Port range, then enter the destination port details.
  If entering a port range, the best practice is to pick the most specific destination port range possible.
4. Enter a description for the rule. Avoid entering confidential information.
5. Select Create.
  You can create up to 50 egress access control rules. If you need more than that, contact Oracle Support.
For more information, see To add egress access control rules.
(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.

Important

If you created a demo environment, it's almost ready for use. Once the health status is Available, sign in and complete a few setup steps before using it for demos and training. See Get Started with Oracle Fusion Demonstration Environment Cloud Service.

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 Vanity URL is also displayed if you have configured a vanity domain. Both URLs link to the application home page.
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 Add User Accounts in the Fusion Applications 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

Note

This isn't applicable for demo environments.

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 ingress access control rules

You can add, update, or delete ingress access control rules that restrict network access to your environment. You can allow access only from a specific CIDR block range or from a virtual cloud network. If you don't create any rules, all inbound traffic is allowed.

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 Ingress access control rule section of Guided learning, select Start to add a 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 Ingress access control rules, select Create rule.
3. On the Create ingress 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 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. Add a description. Avoid entering confidential information.
5. To add additional rules, select Add rule.
6. When finished adding rules, 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 add egress access control rules

You can add, update, or delete egress access control rules that allow additional outbound network traffic to external destinations. You can connect to any IP and CIDR range on a specific port or range of ports.

Note

Each environment comes with a read-only default egress rule that allows outbound traffic to well-known ports only (22, 25, 80, 443, 465, 587, 631, 993). If you don't add any additional egress rules, this is the only outbound traffic that will be permitted from this environment. The rules you create support only TCP protocol.

Add a rule

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 Egress access control rules, select Create rule.
On the Create egress access control rule page, enter the destination in CIDR notation. You can enter:
- A single IPv4 address with a /32 subnet mask
- A CIDR range
  Note
  
  CIDR ranges that cover only private networks (per RFC1918) aren't supported.
- 0.0.0.0/0
  This allows outbound traffic to all IPv4 addresses.
Under Port, select either Single port or Port range, then enter the destination port details.
If entering a port range, the best practice is to pick the most specific destination port range possible.
Enter a description for the rule. Avoid entering confidential information.
Select Create.
You can create up to 50 egress rules. If you need more than that, contact Oracle Support.

Update a rule

On the environment details page, select Networking.
Under Egress access control rules, 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 Update.

Delete a rule

On the environment details page, select Networking.
Under Egress access control rules, 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.

Note

If internet cache is disabled for an environment and you then configure a vanity domain, you cannot later enable internet cache yourself. Instead, you must create a service request with Oracle Support.

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 configure a vanity domain

You can configure a user-friendly vanity domain for your Fusion environment (such as apps.vision.com), so that your users don't have to access their applications using the Oracle-assigned application domain (for example, abcdef.fa.ocs.oraclecloud.com).

Oracle assigns an application domain to a Fusion environment when the environment is first provisioned. At this point, you can't set up a vanity domain just yet. You can set up a vanity domain only after the environment is provisioned.

Let's look at both domains in more detail:

Application domain

The application domain is an automatically assigned Oracle domain and remains the same for the life of the Fusion environment. You do have the option to add a custom prefix when you provision the environment, such as visionapps-abcdef.fa.ocs.oraclecloud.com.

If you add a prefix when you provision the environment, then the prefix becomes part of the permanent application domain. If you want to later change the prefix to something else, such as visionappsnew, you'll need to configure a vanity domain.

Vanity domain

After the environment is provisioned, you can no longer change the application domain. You can, however, add a vanity domain, either by registering a custom domain with your company's branding (such as apps.vision.com) or by adding a custom prefix (such as visionappsnew-abcdef.fa.ocs.oraclecloud.com).

Configuring a custom domain involves these steps:
1. Create the custom domain for the Fusion environment.
2. Update the DNS configuration for the new custom domain with your domain registrar.
3. Configure a new SSL certificate for the custom domain.
4. Schedule the vanity domain update for the environment.
Adding a custom prefix, on the other hand, is a simpler process because you don't have to register a custom domain. See Add a custom prefix to the application domain.

Note

Vanity domains are supported only for environments that have been updated to use identity domains and are on Fusion Applications 26B and later. If your environment was updated to 26B in April or May, then please request the 15-May-26 Weekly Maintenance Pack for Fusion Middleware before configuring a vanity domain for your Fusion environment.

Note

You can configure a vanity domain only once. If you need to change it again, you must create a service request with Oracle Support. See also Understanding Vanity Domains.

Tip

If you've set up an Akamai Client Access Control (CAC) configuration and now you want to configure a vanity domain, you must create a service request with Oracle Support.
If you previously configured a vanity domain for the candidate experience in Oracle Recruiting, you must make a minor adjustment to your Oracle Recruiting setup so that the two vanity domains can coexist. See Set Up Search Engine Optimized Career Site Vanity URL on My Oracle Support (KB86401).

Step 1 Create the custom domain

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.
The Application domain is displayed but can't be changed.
Important

Even after configuring a vanity domain, you must continue to use the application domain for any external third-party and API integrations. Do not use the vanity domain.
Next to Vanity domain, select Configure.
On the Edit vanity domain panel, select Custom domain.
In Custom domain name, enter the custom domain name you want to use for this environment.
In the Company details section, enter the information needed to generate the Certificate Signing Request (CSR) file.
(In Step 3, you'll submit the CSR file to your certificate authority (CA) to obtain a new SSL certificate.)
Select Update.

Step 2 Update the DNS configuration with your domain provider

On the Networking tab, next to DNS configuration, select Configure.
Select Download to download the DNS records for the new custom domain.
Sign in to your domain provider and add the DNS records you downloaded.
Tip

In your account, look for DNS Management or DNS Settings to add these records.
After updating your domain provider with the DNS records for the custom domain, return to the environment's Networking tab to confirm completion of this step and to activate the DNS configuration:
1. Next to DNS configuration, select Configure.
2. Select the I have added the required DNS records... checkbox and then select Activate.
Activation can take up to 30 minutes. Once completed, the DNS configuration displays as Active.

Step 3 Configure your SSL certificate

On the Networking tab, next to Environment certificate status, select Configure.
Select Download to download the Certificate Signing Request (CSR) file for the new custom domain.
Submit the CSR file to your certificate authority.
After you receive the certificate from your certificate authority, return to the environment's Networking tab to add the details and to activate the configuration:
1. Next to Environment certificate status, select Configure.
2. Upload or paste the SSL certificate details.
3. Select Activate.
Activation can take a few minutes. Once completed, the Environment certificate status displays as Active.
Note that the Environment certificate expiration date now displays the certificate expiration date.
Oracle sends notifications 45, 30, 15, and 7 days before your SSL certificate expires, and finally on the day before the expiration date itself.
Before the expiration date, return to this page and select Renew to upload a new certificate.

Note

In addition to the SSL certificate that you obtain and upload in this step, Oracle also uses its own certificate provider for its Content Delivery Network (CDN). If your business requires you to use your own SSL, however, create a service request with Oracle Support.

Step 4 Schedule the vanity domain update

Select when to apply the vanity domain to your environment. This change requires an environment downtime which can last around 30 to 45 minutes.

On the Networking tab, next to Scheduled update status, select Schedule.
Select the date and time to apply these vanity domain changes.
Select Schedule.
The Scheduled update status now displays as Accepted.
- If needed, you can cancel and reschedule the update while the status is Accepted.
- During the update, the status changes to Updating. At this point, changes to the scheduled update are no longer possible.
Once the Scheduled update status displays as Completed, the status of the Vanity domain changes from Inactive to Active.
Tip

After completing the vanity domain setup, you can go to the environment's details page to view both the original Application URL and the new Vanity URL. Both URLs link to the application home page. After the Vanity URL becomes active, any browser-based access to Fusion Applications using the Application URL will be redirected to the Vanity URL.

After completing any setup step (updated the DNS configuration, activated a new SSL certificate, or scheduled the vanity domain update), you can no longer change the vanity domain yourself. To change the vanity domain to something else, you must create a service request with Oracle Support.

Note

If your environment is using iFrames or window.postMessage calls, review the additional setup tasks to ensure your setup continues to work as expected after the introduction of a vanity domain.

Add a custom prefix to the application domain

Instead of configuring your own custom domain (such as apps.vision.com), you can add a prefix to the automatically assigned Oracle-owned application domain (such as visionapps-abcdef.fa.ocs.oraclecloud.com). You can add a prefix when you first provision the environment or after the environment's already been provisioned:

If you add a custom prefix when the environment is first provisioned, then this prefix remains part of the application domain for the life of the environment.
See Fusion Applications Environment Setup Wizard and To create an environment.
After provisioning, you can no longer change the application domain. To add or change a custom prefix at this point, you must configure a vanity domain. Here's how:

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.
The Application domain is displayed but can't be changed.
Important

Even after configuring a vanity domain, you must continue to use the application domain for any external third-party and API integrations. Do not use the vanity domain.
Next to Vanity domain, select Configure.
On the Edit vanity domain panel, select DNS prefix and enter the custom prefix name.
The prefix can be 1-20 characters. As you enter the prefix, the vanity domain preview is displayed.
In Schedule DNS prefix update, select when to apply the DNS prefix to your environment. This change requires an environment downtime.
Select Update.

Note

You can configure a vanity domain only once. If you need to change it again, you must create a service request with Oracle Support.

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 or demo environment

Self-service delete for environments is supported only for non-production development and demo 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