Skip to main content

13.5 Integrating OLIVE Connectivity in Excel

Overview​

You can integrate OLIVE directly within Excel to trigger connectivity. This allows you to pass information from your Excel sheet to connectors and integrate orchestration results back into the workbook.

Please note that there are different ways to integrate OLIVE in Excel. This documentation describes one solution pattern.

Getting Started with the Example​

A complete demonstration of how to integrate OLIVE into Excel can be found in the latest development package. The package includes an Excel workbook (.xlsm file) with working examples and detailed step-by-step instructions in the OLIVE Excel Readme sheet.

General Principle​

The integration uses VB (Visual Basic) macros to create the connection between Excel and OLIVE:

  • Read from Excel: Macros read data from Excel sheets
  • Call OLIVE: The macros make requests to OLIVE's REST API (Data Orchestrator)
  • Integrate Results: Results are written back into specified cells or ranges in the workbook

The example workbook includes a dedicated configuration sheet that allows you to set parameters such as:

  • The API endpoint for the Data Orchestrator
  • Optionally the API endpoint of the Identity Provider to obtain authentication tokens

Authentication for Production Environments​

When your OLIVE deployment requires authentication (typical in production scenarios), use the Windows Credential Manager to securely store your credentials.

A workbook built against a development deployment will stop working in production

A development deployment has no authentication, so the macros can call the Data Orchestrator without any credentials — which is why the integration appears to need no setup while you build it. Against an authenticated deployment the same call returns 401 Unauthorized.

Moving the workbook to such an environment therefore means configuring the token endpoint and the client credentials below. This is one of the two adaptations every solution needs on the way to production; the other one concerns the datapoints inside the solution. See From a Development Deployment to Production and Triggers that worked without credentials in development.

Windows Credential Manager​

Windows Credential Manager is a built-in Windows feature that securely stores credentials on your machine. Instead of hardcoding sensitive information in your VB macros, credentials are stored in the Credential Manager and retrieved at runtime. This keeps your confidential information safe.

Configuration in the Example​

The example includes a configuration section where you can specify:

  • The identity provider token endpoint URL (where authentication tokens are obtained)

The macros will use this endpoint to retrieve access tokens, which are then used to authenticate with OLIVE.

Information Required from OLIVE Administrator​

To connect to OLIVE from Excel, you need the following information from your Tenant Admin:

  • Client ID: The identifier for your Excel application integration
  • Client Secret: The secret key associated with the client ID
  • Token API URL: The endpoint URL for obtaining authentication tokens
  • OLIVE API URL: The URL to your Data Orchestrator instance

Your Tenant Admin can provide all required information.

Complete Instructions​

For detailed step-by-step setup and configuration instructions, refer to the OLIVE Excel Readme sheet included in the example workbook in the development package.