data can be integrated and synchronized codeless with various external systems, on premises or in the cloud, using the Layer2 Cloud Connector
. You will find a selection of 100+ supported systems and apps
including Microsoft Office 365, SharePoint, Dynamics and Exchange here
Oracle Integration and Synchronization with Office 365 and 100+
Benefits of Oracle Data Integration via Layer2 Cloud Connector
Oracle data integration via Layer2 Cloud Connector has the following features and benefits:
- Connect and sync your Oracle data queries with 100+ other data sources, on-premises or cloud-based, including Office 365, SharePoint Dynamics and others, keeping them always up-to-date.
- High speed of implementation: No programming or tools required. Predefined sample connection templates included. Setup in a few minutes guided by wizards. Remote setup support (30 minutes are free).
- Low risk in project: No installation or customizing for the Oracle data source and the data destination required. Just install on a computer in your network, in the cloud, or even your laptop. No administrative rights required. Read or write access rights to Oracle and the connected system is enough.
- Fully compatible with vendor specific or 3rd-party data providers: Data providers of the application vendors (SQL, MySQL, IBM, etc.), 3rd-party data providers, or included Layer2 data providers can be used to access 100+ data sources.
- One-way and two-way connections supported: If provided by driverthe data providers. Several options are built in to solve possible replication conflicts. Flexible sync options.
- 100% compatible with all Office 365, OneDrive and SharePoint editions and plans: Including on-premises, remotely hosted, sandboxed, (e.g. Microsoft SharePoint Online / Microsoft Office 365 (ALL plans) or OneDrive for Business (1TB/User)). Uses the CSOM Web Services API model for sync.
- Highest Security: Connection via secure web services (SSL). Disconnected systems: A connection is only required for data exchange – not for list or library usage. Users do not have direct access to external corporate data sources. You don't have to open your network for the Internet. The application runs where your data resides today - on a server or client inside your corporate network. No data is exposed to 3rd-parties or clouds.
- Highest performance: Can manage very large databases, lists and libraries. No 5,000 items limit with SharePoint. Can scale-out to multiple servers or to the Microsoft Azure Cloud, if required.
- Virtually any data sources supported: ODBC, OLEDB, OData, SOAP, Microsoft .NET based providers, Files (Excel, XML, CSV, Text), RSS / XML feeds, SQL databases like MS SQL, SQL Azure, Oracle, MySQL, IBM DB2, IBM AS/400, IBM Informix; Notes, SharePoint (lists and libraries), local file system, cloud-based file stores, Exchange, Active Directory, Dynamics NAV/CRM, Navision, SAP and many more. More complex data sources, REST-based web services, custom COM, or .NET objects can be connected using 3rd-party add-ons. Cloud-to-cloud connections, e.g. to salesforce.com, Twitter, Facebook, Google, Amazon, BOX.NET and others are also supported.
- Layer2 CSOM Data Provider included: You can connect and sync Oracle data with SharePoint 2010 / 2013 lists on-premise or in the Office 365 / OneDrive for Business cloud.
- Layer2 OData Data Provider included: You can connect Oracle to all OData sources, e.g. Microsoft CRM/ERP or SAP via NetWeaver.
- Layer2 XML Data Provider included: You can connect Oracle to XML-based files and web requests, and filter results by XPath query language.
- Layer2 RSS Data Provider included: You can simply pull or aggregate RSS news feeds into any data source including Oracle. Please note that this provider is also included as sample source code to build your own provider.
- Layer2 Exchange Data Provider included: You can sync contacts, tasks, calendar events, notes, and email bi-directionally with Oracle using Exchange Web Services (EWS). Exchange 2007, 2010, and 2013 are supported as well as Exchange Online. Shared & Site Mailboxes supported.
- Layer2 SOAP Web Services Provider: Connect to SOAP-based web services codeless to Oracle with flexible parameters.
- Very flexible sync options: Uni- and bi-directional sync are supported. Start a specific connection sync scheduled in background (Windows Service) or on demand (e.g. by command line). Sync all data or pre-selected subsets only. Select source and target folders, make use of additional no-delete, no-insert, no-update options.
- Data type conversion included: Sync SharePoint links, lookups, managed metadata, and more with Oracle using advanced options.
- Process integration via SharePoint: Raise change notifications and start workflows in the cloud, triggered on external data changes. Find your Oracle data changes in Delve via Office Graph. All features of native SharePoint lists and libraries are supported, e.g. views, sorting, filtering, grouping, search, mobile and offline access, social features like tagging and enterprise metadata, RSS feeds, change notifications per email, or workflows in the cloud on external data change. You can also add your own business logic.
- Additional unmapped "SharePoint-only" columns can be created: Ranking, rating, managed metadata, comments or file attachments.
- Data aggregation: Multiple connections can combine several different Oracle data sources into one list.
- Flexible logging and alerts: You can log to files, databases, and Windows Event Log via NLOG.
- Free Shareware Edition: You can test the free Shareware Edition as long as you want or you can use in production with limited features. You can upgrade an evaluation / Shareware version to a licensed version at any time without new installation.
- Flexible, cost-effective licensing: Personal or Professional Edition, depending on requirements. Licensing per installation (no user CALs, not bound to any SharePoint server or site, just a one-time fee - no data volume-related costs). Easy to setup and maintain. You can save user CAL license costs for the connected on-premises systems, e.g. ERP/CRM using SharePoint or Office 365 as front-end with external data in sync.
Oracle Specific Configuration Settings
In the Layer2 Cloud Connector, the data source or destination entity must be configured as follows to connect to Oracle. Please find specific configuration settings below.
Fig. Example Oracle connection in the Layer2 Layer2 Cloud Connector.
Please note the following about settings, features and possible issues.
- You need to have the Oracle Data Access Components and Tools - .NET and Windows on the computer that runs the Layer2 Cloud Connector. You can find the component on the Oracle software download page.
- Install either the 32-bit or 64-bit data provider (it MUST match your Cloud Connector installation architecture).
- Please select the Oracle Data Provider for .NET from the list of installed providers.
- You can make use of any connection strings for Oracle as usual, e.g.:
Data Source=myOracleDatabase; User Id=myUser; Password=myPassword.
You will find more information about Oracle connection strings here.
- Note that you can use integrated authentication for better security or encrypt the connection string. You can set NTFS access rights to the connection file (.../connections/myConnectionName.xml) as well.
- You can make use of all SQL queries your data provider supports. You can also use stored procedures that returns records, exec myStoredProcedure().
- You can make use of aliases in query to force auto-mapping in the Cloud Connector, e.g. select customername as title, to auto-map to a SharePoint title column.
- The primary key is normally set automatically, if available.
- Bi-directional sync is fully supported.
Oracle Data Integration - Known Issues & Workarounds
For Oracle Integration via Layer2 Cloud Connector we have found the following issues and workarounds:
- In case of integrated authentication (trusted connection) please make sure that the current user has appropriate database access rights. Also take care about access rights of the Layer2 Cloud Connector Windows Service. Best to use basic authentication with a specific user.
- In case of issues with the Oracle TNS please google the specific error messages for any solutions. Make sure that both the current user and the Layer2 Cloud Connector Windows Service has access to the TNS.
- Blobs or other binary fields are not supported at this time, means e.g. email attachments or SharePoint list attachments cannot be managed by the connector and data providers.
- If using two-way sync, your query must be updatable (most joins are not). You will also need write access rights for this.
Step-by-Step Intros for typical Oracle Integration Scenarios
You will find more information about specific scenarios here:
Next Steps for Product Evaluation
You can register to download and evaluate the Layer2 Cloud Connector here