How to integrate ElasticSearch using Informatica PowerCenter

Learn how to quickly and efficiently connect ElasticSearch with Informatica PowerCenter for smooth data access.

Read and write Elasticsearch data effortlessly. Integrate, manage, and automate indexes and documents — almost no coding required. You can do it all using the high-performance ElasticSearch ODBC Driver for Informatica PowerCenter (often referred to as the ElasticSearch Connector). We'll walk you through the entire setup.

Ready to dive in? Download the product to jump right in, or follow the step-by-step guide below to see how it works.

Introduction

JSON / REST API is becoming more and more popular each day as everyone embrace cloud-centric services. This article is primarily focused on Informatica users who want to access ElasticSearch data or may be other API Integration in Informatica. However many tips and techniques described in this article will help you to understand how to integrate ElasticSearch / XML SOAP / JSON / REST API in other ETL / Reporting apps such as Tableau, Power BI, SSRS, Talend, Excel and many more.

After going through this article you will learn how to Read ElasticSearch / JSON / REST API data in Informatica and understand the concept of JSON / REST API. We will go through many screenshots and step-by-step examples to demonstrate  ElasticSearch or REST API integration in Informatica PowerCenter.

XML / JSON can come from a local file or REST API service (internal or public) so we will include both examples in this article (i.e. Read JSON files in Informatica,  Import REST API in Informatica). So let’s get started. Next article will focus on how to write data to API in Informatica (POST / PUT data)

Requirements

This article assumes that you have full filled following basic requirements.

1. Download Install ZappySys ODBC PowerPack (API Driver for ElasticSearch included)
2. Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
3. Access to a Relational database such as SQL Server (or use any of your choice e.g. Oracle, MySQL, DB2 ). If nothing available then you can use flat file target.

High level Steps for Import ElasticSearch data using Informatica (Read ElasticSearch API data)

Before we dive deep to learn how to load ElasticSearch data in Informatica (i.e. ElasticSearch to SQL Table), Here the summary of high-level steps you need to perform to import ElasticSearch in Informatica (same steps for Import JSON / XML / REST API).

1. Download and Install ZappySys API Driver (for connecting to ElasticSearch)
2. Create ODBC DSN using ZappySys API driver and choose ElasticSearch Connector during Wizard
3. Create Relational > ODBC Connection in Informatica Workflow designer (Point to DSN we created in the previous step)
4. Import ElasticSearch Source Definition in the Informatica Mapping Designer > Sources Tab
5. Import Target Table Definition in the Informatica Mapping Designer > Targets Tab
6. Create source to target mapping in Mappings tab
7. Save mapping (name m_API_to_SQL_Load )
8. Create Session using the mapping we created in the previous step
9. Save Workflow and execute to load ElasticSearch data into SQL Table. Verify your data and log.
   

   Loading ElasticSearch data to SQL Table in Informatica (Import REST API or JSON Files)

Video Tutorial – Read any API / JSON data in Informatica (Load ElasticSearch to SQL Table)

Getting Started – Import ElasticSearch to SQL Server in Informatica

Now let’s get started. For example purpose, we will read data from ElasticSearch and load data into SQL Server Table using Informatica Workflow.

Create data source using ElasticSearch ODBC Driver

Step-by-step instructions

To get data from ElasticSearch using Informatica PowerCenter, we first need to create an ODBC data source. We will later read this data in Informatica PowerCenter. Perform these steps:

1. Download and install ODBC PowerPack (if you haven't already).

2. Search for odbc and open the ODBC Data Sources (64-bit):

   

3. Create a User data source (User DSN) based on the ZappySys API Driver driver:

   ZappySys API Driver

   
   • Create and use a User DSN if the client application runs under a User Account. This is the ideal option at design time (e.g., when developing in Visual Studio). Use it for both types of applications (64-bit and 32-bit).
   • Create and use a System DSN if the client application runs under a System Account (e.g., as a Windows Service). This is usually the required option in a production environment. If your Windows Service is a 32-bit application, you must use the 32-bit ODBC Data Source Administrator to configure this

4. When the Configuration window appears give your data source a name if you haven't done that already, then select "ElasticSearch" from the list of Popular Connectors. If "ElasticSearch" is not present in the list, then click "Search Online" and download it. Then set the path to the location where you downloaded it. Finally, click Continue >> to proceed with configuring the DSN:

   ElasticsearchDSN

   ElasticSearch

   

5. Now it's time to configure the Connection Manager. Select Authentication Type, e.g. Token Authentication. Then select API Base URL (in most cases, the default one is the right one). More info is available in the Authentication section.

   Basic Authentication (UserId/Password)

   ElasticSearch authentication

   For Local / Hosted Instance by you

   1. Get your userid / password and enter on the connection UI

   For Managed Instance (By Bonsai search)

   If your instance is hosted by bonsai then perform these steps to get your credentials for API call

   1. Go to https://app.bonsai.io/clusters/{your-instance-id}/tokens
   2. Copy Access Key and Access Secret and enter on the connection UI. Click Test connection.
   3. If your Cluster has no data you can generate sample data by visiting this URL and click Add Sample Data https://{your-cluster-id}.apps.bonsaisearch.net/app/home#/tutorial_directory

   API Connection Manager configuration

   Just perform these simple steps to finish authentication configuration:

   1. Set Authentication Type to Basic Authentication (UserId/Password) [Http]
   2. Optional step. Modify API Base URL if needed (in most cases default will work).
   3. Fill in all the required parameters and set optional parameters if needed.
   4. Finally, hit OK button:

   ElasticsearchDSN

   ElasticSearch

   Basic Authentication (UserId/Password) [Http]

   http://localhost:9200

   Optional Parameters
   User Name (or Access Key)
   Password (or Access Secret)
   Ignore certificate related errors

   

   Windows Authentication (No Password)

   ElasticSearch authentication

   No instructions available.

   API Connection Manager configuration

   Just perform these simple steps to finish authentication configuration:

   1. Set Authentication Type to Windows Authentication (No Password) [Http]
   2. Optional step. Modify API Base URL if needed (in most cases default will work).
   3. Fill in all the required parameters and set optional parameters if needed.
   4. Finally, hit OK button:

   ElasticsearchDSN

   ElasticSearch

   Windows Authentication (No Password) [Http]

   http://localhost:9200

   Optional Parameters
   Ignore certificate related errors

   

6. Once the data source connection has been configured, it's time to configure the SQL query. Select the Preview tab and then click Query Builder button to configure the SQL query:

   

   ZappySys API Driver - ElasticSearch

   Read and write Elasticsearch data effortlessly. Integrate, manage, and automate indexes and documents — almost no coding required.

   ElasticsearchDSN

   

7. Start by selecting the Table or Endpoint you are interested in and then configure the parameters. This will generate a query that we will use in Informatica PowerCenter to retrieve data from ElasticSearch. Hit OK button to use this query in the next step.

   SELECT * FROM Indexes

   
   Some parameters configured in this window will be passed to the ElasticSearch API, e.g. filtering parameters. It means that filtering will be done on the server side (instead of the client side), enabling you to get only the meaningful data much faster.

8. Now hit Preview Data button to preview the data using the generated SQL query. If you are satisfied with the result, use this query in Informatica PowerCenter:

   

   ZappySys API Driver - ElasticSearch

   Read and write Elasticsearch data effortlessly. Integrate, manage, and automate indexes and documents — almost no coding required.

   ElasticsearchDSN

   SELECT * FROM Indexes

   
   You can also access data quickly from the tables dropdown by selecting <Select table>.
   A WHERE clause, LIMIT keyword will be performed on the client side, meaning that the whole result set will be retrieved from the ElasticSearch API first, and only then the filtering will be applied to the data. If possible, it is recommended to use parameters in Query Builder to filter the data on the server side (in ElasticSearch servers).

9. Click OK to finish creating the data source.

Video Tutorial

Create Connection in Informatica Workflow Designer

Once you create DSN using API Driver our next step is to define a connection for ElasticSearch source in Informatica PowerCenter Workflow designer.

1. Open Workflow designer [W] icon
2. Goto Connections > Relational
   

   Create a new connection for ElasticSearch in Informatica

3. Click New and select ODBC
   

   Select ODBC connection type in Informatica (Using ZappySys API ODBC DSN)

4. Now on the ODBC connection setup enter connection name, some fake userid / password (this is a required field but its ignored by JSON Driver)
5. In the Connection String field enter the exact same name of DSN (Open ODBC Data Sources UI to confirm)
   

   Configure ElasticSearch connection in Informatica for REST API – Using ZappySys API Driver

6. Click OK to close the connection properties.

That’s it. Now we ready to move to next step (define source and target in Mapping Designer).

Import ElasticSearch Source Definition in Informatica Mapping Designer

Now let’s look at steps to import ElasticSearch table definition.

1. Open Informatica Mapping Designer (Click [D] icon)

2. Click on Source Icon to switch to Sources designer

3. From the top menu > Click on Sources > Import from Database …

   

   Import ElasticSearch Source definition in Informatica Mapping Designer (JSON file or REST API)

4. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)

5. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.

   DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
   —————————————————-
   Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
   

   Select ElasticSearch Source Table in Informatica Mapping Designer (JSON file or REST API)

6. Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
7. Optionally once table structure is imported you can rename it
   

   Rename imported table definition in Informatica Source Designer

8. That’s it, we are now ready to perform similar steps to import Target table structure in the next section.

Import SQL Server Target Definition in Informatica Mapping Designer

Now let’s look at steps to import Target table definition (very similar to the previous section, the only difference is this time we will select DSN which points to SQL Server or any other Target Server).

Now lets look at steps to import target table definition in Informatica mapping designer.

1. In the Mapping Designer, Click on Target Icon to switch to Target designer
2. From the top menu > Click on Targets > Import from Database …
3. Select DSN for your Target server (if DSN doesn’t exist then create one by opening ODBC Sources just like we created one for JSON API source (see the previous section about creating DSN).
   

   Import target Table Definition in informatica

4. Enter your userid , password and Schema name and click Connect to see tables
5. Select Table name to and click OK import definition.
   

   Import Target SQL Table Definition in Informatica – Select table from the list

Create Source to Target Mapping in Informatica (Import JSON to SQL Server)

Once you have imported source and target table definition, we can create mapping and transformation to load data from JSON to SQL Table.

1. First open Mapping Designer (Click [D] icon)
2. Drag JSON Source from sources folder
3. Drag SQL Table from Targets folder
4. Map desired columns from Source to target
   

   Define Source to Target mapping for ElasticSearch to SQL Table load in Informatica

5. For certain columns you may have to do datatype conversion. For example to convert OrderDate form nstring to DataTime you have to use Expression Transform like below and map it to target. In below example, our JSON has date format (e.g. 2018-01-31 12:00:00 AM ). To import this to DateTime field in SQL server we need to convert it using TO_DATE function. Use double quotes around T to make this format working.
   

   TO_DATE(OrderDate,'YYYY-MM-DD H12:MI:SS AM')
   
    --For ISO use below way
           TO_DATE(OrderDate,'YYYY-MM-DD"T"HH24:MI:SS')

   

   Informatica ElasticSearch to SQL Table Mapping – Datatype conversion (nstring to datetime)

6. Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
7. Now lets move to next section to create workflow.

Create Workflow and Session in Informatica

Now the final step is to create a new workflow. Perform following steps to create workflow which with a session task to import JSON data into SQL table.

1. Open workflow designer by click [W] icon.
2. Launch new workflow creation wizard by click Workflow top menu >  Wizard
   name your workflow (e.g. wf_Api_Tp_Sql_Table_Import)
   

   Creating Informatica Workflow – Wizard UI (Import ElasticSearch data to SQL Table)

3. Finish the wizard and double-click the Session to edit some default properties.
4. First change Error settings so we fail session on error (By default its always green)
   

   Fail Informatica Session on error (ElasticSearch data to SQL Load)

5. Select JSON connection for Source
   

   Select ElasticSearch Source Connection in Informatica – Load ElasticSearch data to SQL Table

6. Change default Source query if needed. You can pass parameters to this query to make it dynamic.
   

   Modify ElasticSearch Source SQL query – Pass parameters, change URL, set filter etc

7. Select Target connection of SQL Target Table
   

   Select SQL Target Connection in Informatica – Load ElasticSearch data to SQL Table

8. Save workflow
9. That’s it. We ready to run our first workflow to load JSON data to SQL.

Execute Workflow and Validate Log in Informatica

Now once you are done with your workflow, execute it to see the log.

Loading ElasticSearch data to SQL Table in Informatica (Import REST API or JSON Files)

POST data to ElasticSearch in Informatica

There will be a time when you like to send Source data to REST API or SOAP Web Service. You can use below Query for example. For detailed explanation on how to POST data in Informatica check this article .

Video Tutorial – How to POST data to REST API in Informatica

Here is detailed step by step video on REST API POST in informatica PowerCenter

Keywords

how to import ElasticSearch in informatica | how to read ElasticSearch data in informatica powercenter | how to test json from informatica | how to use ElasticSearch data as source in informatica power center | how to connect ElasticSearch in informatica 10 | informatica how to import data from ElasticSearch | informatica jtx to import ElasticSearch (use of java transformation) | informatica plugin for restful api using json | informatica power center and ElasticSearch support | informatica read ElasticSearch | informatica rest api | informatica ElasticSearch connector | json parser import informatica

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide ElasticSearch data access to multiple users or services. Configuring the data source on a Data Gateway creates a single, centralized connection point for this purpose.

This configuration provides two primary advantages:

• Centralized data access
  The data source is configured once on the gateway, eliminating the need to set it up individually on each user's machine or application. This significantly simplifies the management process.
• Centralized access control
  Since all connections route through the gateway, access can be governed or revoked from a single location for all users.

To achieve this, you must first create a data source in the Data Gateway (server-side) and then create an ODBC data source in Informatica PowerCenter (client-side) to connect to it.

Let's not wait and get going!

Create ElasticSearch data source in the gateway

In this section we will create a data source for ElasticSearch in the Data Gateway. Let's follow these steps to accomplish that:

1. Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:

   

2. Go to the Users tab and follow these steps to add a Data Gateway user:

   • Click the Add button
   • In the Login field enter a username, e.g., john
   • Then enter a Password
   • Check the Is Administrator checkbox
   • Click OK to save
   

3. Now we are ready to add a data source:

   • Click the Add button
   • Give the Data source a name (have it handy for later)
   • Then select Native - ZappySys API Driver
   • Finally, click OK
   ElasticsearchDSN

   ZappySys API Driver

   

4. When the ZappySys API Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the ElasticSearch ODBC data source created and configured, and follow these steps on how to Import data source configuration into the Gateway:

   • Open ODBC data source configuration and click Copy settings:
     

     ZappySys API Driver - Configuration [Version: 2.0.1.10418]

     ZappySys API Driver - ElasticSearch

     Read and write Elasticsearch data effortlessly. Integrate, manage, and automate indexes and documents — almost no coding required.

     ElasticsearchDSN

     
   • The window opens, telling us the connection string was successfully copied to the clipboard:

   • Then go to Data Gateway configuration and in data source configuration window click Load settings:

     ElasticsearchDSN

     

     ZappySys API Driver - Configuration [Version: 2.0.1.10418]

     ZappySys API Driver - ElasticSearch

     Read and write Elasticsearch data effortlessly. Integrate, manage, and automate indexes and documents — almost no coding required.

     ElasticsearchDSN

     
   • Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.

5. Once done, go to the Network Settings tab and Add a firewall rule for inbound traffic:

   
   • This will initially allow all inbound traffic.
   • Click Edit IP filters to restrict access to specific IP addresses or ranges.

6. Crucial Step: After creating or modifying the data source, you must:

   • Click the Save button to persist your changes.
   • Hit Yes when prompted to restart the Data Gateway service.

   This ensures all changes are properly applied:

   
   Skipping this step may cause the new settings to fail, preventing you from connecting to the data source.

Create ODBC data source to connect to the gateway

In this part we will create an ODBC data source to connect to the ZappySys Data Gateway from Informatica PowerCenter. To achieve that, let's perform these steps:

1. Search for odbc and open the ODBC Data Sources (64-bit):

   

2. Create a User data source (User DSN) based on the ODBC Driver 17 for SQL Server driver:

   ODBC Driver 17 for SQL Server

   
   If you don't see the ODBC Driver 17 for SQL Server driver in the list, choose a similar version.

3. Then set a Name for the data source (e.g. Gateway) and the address of the Data Gateway:

   ZappySysGatewayDSN

   localhost,5000

   
   Make sure you separate the hostname and port with a comma, e.g. localhost,5000.

4. Proceed with the authentication part:

   • Select SQL Server authentication
   • In the Login ID field enter the user name you created in the Data Gateway, e.g., john
   • Set Password to the one you configured in the Data Gateway
   

5. Then set the default database property to ElasticsearchDSN (the one we used in the Data Gateway):

   ElasticsearchDSN

   ElasticsearchDSN

   
   Make sure to type the data source name manually or copy/paste it directly into the field. Using the dropdown might fail because the Trust server certificate option is not enabled yet (next step).

6. Continue by checking the Trust server certificate option:

   

7. Once you do that, test the connection:

   

8. If the connection is successful, everything is good:

   

9. Done!

We are ready to move to the final step. Let's do it!

Access data in Informatica PowerCenter via the gateway

Finally, we are ready to read data from ElasticSearch in Informatica PowerCenter via the Data Gateway. Follow these final steps:

1. Go back to Informatica PowerCenter.

2. Open Informatica Mapping Designer (Click [D] icon)

3. Click on Source Icon to switch to Sources designer

4. From the top menu > Click on Sources > Import from Database …

   

   Import ElasticSearch Source definition in Informatica Mapping Designer (JSON file or REST API)

5. Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)

6. Click Connect button to get a list of tables. Any array node is listed as a table. Also, you will see array node with parent columns (e.g. value_with_parent). You may get some warning like below but they are harmless so just ignore by clicking OK.

   DLL name entry missing from C:\Informatica\PowerCenter8.6.1\client\bin\powrmart.ini Section = ODBCDLL Entry = ZappySys JSON Driver
   —————————————————-
   Using EXTODBC.DLL to support ZappySys JSON Driver. For native support of ZappySys JSON Driver make an entry in the .ini file.
   

   Select ElasticSearch Source Table in Informatica Mapping Designer (JSON file or REST API)

7. Read the data the same way we discussed at the beginning of this article.

8. That's it!

Now you can connect to ElasticSearch data in Informatica PowerCenter via the Data Gateway.

Supported ElasticSearch Connector actions

Got a specific use case in mind? We've mapped out exactly how to perform a variety of essential ElasticSearch operations directly in Informatica PowerCenter, so you don't have to figure out the setup from scratch. Check out the step-by-step guides below:

• Count documents
• Create Index
• Delete documents
• Delete Index
• Get document by ID from Index or Alias
• Get documents from Index or Alias
• Get Index or Alias metadata
• Insert documents
• List aliases
• List indexes
• Search or Query documents
• Update documents
• Upsert documents
• Make Generic REST API Request
• Make Generic REST API Request (Bulk Write)

Conclusion

In this article we showed you how to connect to ElasticSearch in Informatica PowerCenter and integrate data without writing complex code — all of this was powered by ElasticSearch ODBC Driver.

Download ODBC PowerPack now or ping us via chat if you have any questions or are looking for a specific feature (you can also reach out to us by submitting a ticket):

Explore Informatica PowerCenter connectors

Amazon Ads

Amazon Athena

Amazon Selling Partner (SP-API)

Apache Derby

Apache Hive

Apache Spark

Asana

Azure DevOps

Cosmos DB

Dropbox

DuckDB (Parquet)

FastSpring

Gmail

Google Ads

Google BigQuery

Google Calendar

Google Drive

Google Search Console

Google Sheets

Hubspot

Infor Data Lake

Jira

Mailchimp

ManageEngine ServiceDesk Plus (Zoho)

MariaDB

MySQL

Neo4j

OData

OneDrive

Outlook Mail (Office 365)

Power BI

ServiceNow

SharePoint Online

Shopify

Smartsheet

Starburst

Stripe

Trino

YouTube

Zendesk

Zoho CRM

Zoho SalesIQ

Zoom

REST API

JSON

JSON File

XML

SOAP

XML File

JDBC-ODBC Bridge

Salesforce

CSV

Amazon S3 JSON File

Amazon S3 XML File

Amazon S3 CSV File

Azure Blob JSON File

Azure Blob XML File

Azure Blob CSV File

FTP/SFTP JSON File

FTP/SFTP XML File

FTP/SFTP CSV File

Build your own Custom API Connector

More ElasticSearch integrations

SSIS

SQL Server

Microsoft Fabric

Power BI

SSRS

MS Access

Excel

SSAS

C#

Python

Java

Tableau

SAP Crystal Reports

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Talend Studio

UiPath

PowerShell

Alteryx

ODBC