Frequently Asked Questions
This chapter provides answers to common questions about migrating from the legacy GIS integration to the modern Oracle Integration Cloud-based integration model. These FAQs are intended to help customers clarify migration requirements, understand support boundaries, and plan the transition from the legacy integration to the modern file-based and message-based synchronization framework.
Can customers remain on ArcGIS 10.9.1 and use the file-based integration?
The Oracle Integration Cloud accelerator for file-based integration is officially supported with ESRI ArcGIS 11.3 or later.
Customers who remain on ArcGIS 10.9.1 cannot use the Oracle Integration Cloud accelerator as an out-of-the-box supported solution. In this case, a custom integration layer is required.
Are GIS to WACS Asset Class mappings affected when using Utility Network in ArcGIS 10.x?
The mappings are affected only if the Asset Class values or related mapping definitions change. If the Asset Class values remain unchanged, the existing mappings can continue to be used.
Note: All configured asset classes must be accessible as feature layers in ArcGIS.
What if Oracle Integration Cloud cannot be used?
If Oracle Integration Cloud cannot be used, a custom integration is required.
Reminder: Always ensure custom integrations comply with Oracle security policies.
Can file-based inbound synchronization be combined with legacy outbound synchronization?
No. File-based inbound synchronization should not be combined with legacy outbound synchronization. Customers should migrate to the full file-based integration model for both inbound and outbound asset synchronization.
Can legacy asset outbound synchronization still occur immediately after an update?
No. Use the file-based asset outbound synchronization instead.
Are ArcGIS 11.x versions earlier than 11.3 supported for file-based integration?
No. The Oracle Integration Cloud accelerator officially supports ESRI ArcGIS 11.3 or later. Earlier ArcGIS 11.x versions are not supported out of the box for file-based integration and may require a custom integration approach.
Is Oracle Integration Cloud the only supported integration platform?
Oracle support is limited to the Oracle Integration Cloud-based integration solution delivered for this integration. Other integration platforms may be used if they comply with the required JSON standards.
Can non-ESRI GIS integration be supported?
Yes. Non-ESRI GIS integrations can be implemented through a custom JSON-based integration. Oracle does not provide out-of-the-box support for non-ESRI GIS integrations.
Is rollback to the legacy integration possible?
Yes. While ArcGIS 10.x is available and configuration remains compatible.
Is the GIS Map Viewer affected by the migration?
No. The GIS Map Viewer works with both ArcGIS 10.x and ArcGIS 11.x. However, work locations created from the Map Viewer require the modern OIC-based messaging synchronization flow to complete synchronization with ArcGIS.