Application Environments

Important: This information only applies to Oracle Field Service environments. You can verify whether you've Oracle Field Service or Oracle Fusion Field Service, by signing in and checking on the About page.

Oracle Field Service environments include one production and one test environments provisioned as a part of your ordered service. The Production environment is dedicated to production use and test environments are dedicated to non-production use. You can expand the service with additional non-production environments subject to additional fees.

Environment Names

Each Oracle Field Service environment can have two names. The first name is provided by Oracle and is used for creating the environment and ensuring that this name is unique among all other Oracle Field Service environments. You can't change this name and it remains reserved for the environment for its lifetime.

The other name typically indicates that the environment is dedicated to a certain business or a company. This name is called 'alternate name'. When you provision the environment, an alternate name is generated based on your customer account. You can change this name from the Service Console. All environment names are displayed on the About page of your environment.

Domains for Your Environments

Domains for a Production Environment

Each production environment might be supplied with several URLs depending on the provided alternate name and domain zones. These domains are always constructed from two parts:

Either environment name (mentioned as the 'environment_name' parameter in the example below) or an alternate name
Domain zones available for an environment

The standard set of addresses for any environment is:

https://{environment_name}.fs.ocs.oraclecloud.com
https://{alternate_name}.fs.ocs.oraclecloud.com

For legacy environments that are created before June 2021, domains are also registered within the etadirect.com zone. For example:

https://{environment_name}.etadirect.com
https://{alternate_name}.etadirect.com

Domains for Non-Production Test Environments

The rules for provisioning of end points for test environments are almost the same as that of production environments. The only difference here's that for tests the application automatically adds the suffix '.test' after the name. This logic is applied to easily distinguish between production and test environments. The example of an end point for a test environment is https://{environment_name}.test.fs.ocs.oraclecloud.com.

Domains Not Recommended

Oracle Field Service supports two centralized entry points:

login.etadirect.com - to access from browser and installed apps
api.etadirect.com - for integration using APIs

Oracle keeps these domains to support backward compatibility for customers who are already using them. However, these addresses aren’t recommended for usage, because they can be served by any of the datacenters in the cloud causing additional redirects to a datacenter where target Oracle Field Service the environment is running. This might lead to:

latency for processing of requests
increased error rate
issues with data residency

Based on this information, the best practice is to use a direct address to access an Oracle Field Service environment. If you're still using a not-recommended domain, you must change to using a direct environment address as soon as possible.