Skip Navigation
Expand
Oracle Field Service (OFS) Infrastructure Migration to the Oracle Cloud Infrastructure (OCI)
Answer ID 11265   |   Last Review Date 05/26/2020

What can I expect during the OFS (Oracle Field Service) Infrastructure Migration to the Oracle Cloud Infrastructure (OCI)?

Environment:

Migration is available for Oracle Field Service instances running on Service Update 11 for 20A or higher:

  • Preview Test
  • Production
  • Remaining Test

Resolution:

Oracle has a longstanding reputation for providing innovative technologies that empower organizations to meet their most demanding business needs. One of our latest advancements is Oracle Cloud Infrastructure (OCI). As the foundation of Oracle's second-generation cloud, OCI is a purpose-built, best-in-class platform for running enterprise applications. OCI is engineered from the ground up to run mission-critical databases, workloads, and applications while providing end-to-end security. Oracle's data centers around the globe are standardizing on the new OCI architecture which will deliver even greater performance and reliability.

To ensure continued success as your business grows and evolves, your Field Service environments will be migrated to the OCI, enabling you to eventually run all of your SaaS and PaaS solutions from the same data center. 


The OFS Infrastructure Migration to the OCI will occur in three separate migration phases:


Phase 1: Preview Test Environment Migration

The first phase, Preview Test Environment Migration, will change location of your Preview Test Environment.

Downtime of the Test environments is not expected.

Conditional action items that have to be done before the phase begins:

  • If you use IPs of our services in your Test middleware, they should be replaced by URLs.
  • If your Preview Test network has firewall rules, email anti-relay or anti-spam measures, proxy, antivirus or other filtering, you will need to revise the rules to whitelist domains associated with the OCI (see Frequently Asked Questions below).
  • If you use VPN connection between your facilities and the Oracle DCs (primary and failover ones) and are going to use it in the new OCI , you have to establish new VPN connections in advance.


In order to be prepared for the next phase (Production Environment Migration), please perform appropriate testing of your migrated test environment. Your production environment migration will typically be two weeks after your test environment migration. 


Phase 2: Production Environment Migration

The second phase, Production Environment Migration, will change location of your Production Environment.

Downtime of the Production Environment is not expected.

Conditional action items that have to be done before the phase begins:

  • If you use IPs of our services in your Production middleware, they should be replaced by URLs. 
  • If your Production network has firewall rules, email anti-relay or anti-spam measures, proxy, antivirus or other filtering, you will need to revise the rules to whitelist domains associated with the OCI (see Frequently Asked Questions below).


Phase 3: Remaining Test Environments Migration

The third phase, Remaining Test Environments Migration, will change location of all your remaining Test environments.

Downtime of the Test Environment is not expected.

Conditional action items that have to be done before the phase begins:

  • If you use IPs of our services in your Remaining Test middleware, they should be replaced by URLs. 
  • If your Remaining Test network has firewall rules, email anti-relay or anti-spam measures, proxy, antivirus or other filtering, you will need to revise the rules to whitelist the IP addresses associated with the OCI (see Frequently Asked Questions below).



Frequently Asked Questions


Q. Why is Oracle migrating OFS customers to the OCI and what will be the benefits?

A. Oracle is migrating OFS customers to the OCI it order to ensure continued success as your business grows and evolves enabling you to eventually run all of your SaaS and PaaS solutions from the same data center. These migrations address continual improvement efforts towards availability, reliability, security, performance and integration. Oracle strongly suggests that you select the datacenter location that we have provided in the email notification as it is closest to your region. This will ensure that you have the fastest response speed and avoid any latency that could be caused by being hosted in a location further away. It will also eliminate or diminish your dependency on political, financial, weather and other conditions in other countries or geographical regions. Higher availability via an Active-Active configuration is provided for customers using Akamai.  Lastly it could potentially remove any compliance or data concerns by having your data hosted close to your region.


Q. Who will be included in the OFS Infrastructure Migration to the OCI?

A. All OFS customers currently hosted in Oracle's legacy DCs.


Q. When will the OFS Infrastructure Migration to the OCI take place?

A. The OFS Infrastructure Migration to the OCI began in December 2019. Information and instructions will be provided via email.


Q. Are there any actions that I need to take to prepare?

A.  As part of moving to OCI DC we recommend using the following URL configurations to access Oracle Field Service:

  • As OCI follows pro-active, always-on security, it uses Akamai as its standard. Automated disaster recovery solution will be provided for customers behind Akamai. If your organization requires VPN connectivity, prior to the migration you must aquire OCI tenancy to build a VCN. See details in Connectivity Options.pdf and Creating a VPN on OCI.pdf;
  • Core Application URL and Legacy Manage: should be changed from login.etadirect.com to <instance_name>.etadirect.com URL scheme. Instance name is definied in Your Provisioned Instances in the Cloud Portal found on the Service Console. This would be the same name you setup for your OFS instance. For example, if you entered "moresunshine", your URL will be "moresunshine.etadirect.com"
  • API requests: should be sent to <instance_name>.etadirect.com URL scheme instead of api.etadirect.com. The Oracle assigned Instance Name that is defined in Your Provisioned Instances in the Cloud Portal found on the Service Console.  This name begins with â€˜ofsc'. If the Instance Name in the Service Console is 'ofsc-1111', the API URL would be 'ofsc-1111.etadirect.com'. Example of API request: https://ofsc-1111.etadirect.com/rest/ofscCore/v1/activities/{activityId}
  • If your network has firewall rules, email anti-relay or anti-spam measures, proxy, antivirus or other filtering, you will need to revise the rules to whitelist:
    * for the Incoming traffic (Customer >> Oracle): domain *.etadirect.com;
    * for the Outgoing traffic (Oracle >> Customer): download and use the JSON with the IP Address Ranges (see IP blocks marked by tag "OSN").
  • URLs with the domain name of toadirect.com will no longer be supported. As a result, customers who previously used toadirect.com must use login.etadirect.com for user access and must use api.etadirect.com for API access. URLs <instance_name>.etadirect.com will become available after additionally announced .toadirect.com removal (which will first be completed for TEST instances, then PROD instances).


Q. What is the process of the OFS Infrastructure Migration to the OCI?

A. The migration will occur in three phases:
Phase 1: Preview Test Environment Migration
Phase 2: Production Environments Migration
Phase 3: Remaining Test Environments Migration
Oracle will proceed with a schedule designed to assure that the migration of all environments occurs as smoothly and efficiently as possible. Oracle will notify customers of pre-migration and/or post - migration actions (if necessary).


Q. How can I change the suggested target datacenter location?

A. Oracle strongly suggests that you select the datacenter location that we have provided in the email notification as it is closest to your region. This will ensure that you have the fastest response speed and avoid any latency that could be caused by being hosted in a location further away. It will also eliminate or diminish your dependency on political, financial, weather and other conditions in other countries or geographical regions. Higher availability via an Active-Active configuration is provided for customers using Akamai. Lastly it could potentially remove any compliance or data concerns by having your data hosted close to your region. To switch the datacenter location, create a Service Request in the CX Portal.


Q. Is there in-depth description of OCI connectivity methods?

A. See Overview and procedures to connect using Oracle Cloud Infrastructure in the Connectivity Options.pdf


Q. How do I go about creating a VPN on OCI?

A. See Overview and procedures to create a VPN in the Creating a VPN on OCI.pdf.


Q. Will there be any downtime?

A. We do not anticipate any downtime during each phase of the migration. You will be notified 30 and 2 days prior to your scheduled migration time. In the event that you cannot access the OFS service after the migration, do not hesitate to submit a Service Request to the CX Portal or contact us directly.


Q. Can I refuse/cancel the OFS Infrastructure migration to the OCI?

A. Oracle Field Service is a multi-tenant solution so it is not possible to refuse/cancel the OFS Infrastructure migration. Please refer to the schedule for OFS Infrastructure migration.


Q. Will I be able to perform instance re-creation within the stages of migration to OCI?

A. It is not possible to perform instance re-creation if the instances are on different infrastructures - legacy OFS and OCI. Migrating instances will temporarily be hidden from the Service Console until the end of Phase 3.


Q. Is it mandatory to change the Core Application URL, Legacy Manage, and API url schemes to instance_name as suggested above?

A. It is not a mandatory action to do this prior to your OCI migration. It is however suggested that you eventually change to this scheme if you have not already. Oracle plans to remove the old schemes in the future.


Q. Do we need to change Client ID/Secret of OFS applications after we switch to <instance_name>.etadirect.com URL scheme?

A. No further changes to the Client ID/Secret are required. The authentication structure stays the same as mentioned in REST API for Oracle Field Service. The only change is from the single point of contact API portal to the instance-defined URL (that is, from api.etadirect.com to <instance_name>.etadirect.com).


Stay updated and subscribe to any future changes  by using the "Notify me" button on the panel to the right.

If you have any other questions or concerns in the meantime, do not hesitate to submit a Service Request to the CX Portal or contact us directly.