How to integrate Neo4j using Informatica PowerCenter

Integrate Informatica PowerCenter and Neo4j

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

Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required. You can do it all using the high-performance Neo4j ODBC Driver for Informatica PowerCenter (often referred to as the Neo4j 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.

Neo4j ODBC Driver Powering this integration

High performance
Bidirectional
Low-code / No-code
Easy to use

Built on the ZappySys JDBC Bridge Driver, the Neo4j ODBC Driver is a high-performance, low-code / no-code solution. It enables you to connect to Neo4j data without any coding right in your SQL Server, or any ODBC/JDBC application. Part of the ODBC PowerPack.

Documentation

Prerequisites

Before we begin, make sure you meet the following prerequisite: Java Runtime Environment (JRE) or Java Development Kit (JDK) must be installed on your system.

Minimum required version: Java 17
- Amazon Corretto 17
- Oracle JRE 17
Recommended Java version: Java 21
- Amazon Corretto 21
- Oracle JRE 21

If your JDBC Driver targets a different Java version (e.g., 11 / 17 / 21), install the corresponding or newer Java version.

If you already have a JRE installed, you can try using it too. However, if you experience any issues, we recommend using one of the distributions mentioned above (you can install an additional JRE next to the existing one; just don't forget to configure the default Java in the Windows Environment Variables).

Download Neo4j JDBC driver

To connect to Neo4j in , you will have to download JDBC driver for it, which we will use in later steps. Let's perform these little steps right away:

Visit MVN Repository.
Download the JDBC driver, and save it locally, e.g. to E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar.
Done! That was easy, wasn't it? Let's proceed to the next step.

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 Neo4j 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 Neo4j / 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 Neo4j / 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 Neo4j 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)

If you need to consume API which is not listed on connector library page then please refer to the below article links. It talks about how to read / write pretty much any API and not just Neo4j API. It explains various API tips / tricks using our other Universal Drivers not mentioned in this article (i.e. ZappySys JSON / XML and CSV Drivers).

Requirements

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

Download Install ZappySys ODBC PowerPack (API Driver for Neo4j included)
Install Informatica PowerCenter Client Tools (e.g. Workflow and Mapping Designers)
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 Neo4j data using Informatica (Read Neo4j API data)

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

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

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

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

Below video is not about Neo4j API but its showing API access in general (for any API). By watching following ~5 min video can learn steps listed in this article to load JSON API data into SQL Server Table using ZappySys JSON Driver. You can go though full article to learn many useful details not covered in this video.

Getting Started – Import Neo4j to SQL Server in Informatica

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

Create data source using Neo4j ODBC Driver

Step-by-step instructions

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

Download and install ODBC PowerPack (if you haven't already).
Search for odbc and open the ODBC Data Sources (64-bit):
Create a User data source (User DSN) based on the ZappySys JDBC Bridge Driver driver:

ZappySys JDBC Bridge 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
Now, we need to configure the JDBC connection in the new ODBC data source. Simply enter the Connection string, credentials, configure other settings, and then click Test Connection button to test the connection:

Neo4jDSN

jdbc:neo4j://neo4j-instance-host-name:7687?enableSQLTranslation=true

E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar

neo4j

***************

[]

For Non-SSL Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j://neo4j-instance-host-name:7687?enableSQLTranslation=true
- JDBC driver file(s): E:\Drivers\JDBC\neo4j-jdbc-full-bundle.jar
- User name: neo4j
- User password: ***************
- Connection parameters: []
  Use enableSQLTranslation=true attribute in the connection string to query Neo4j database using SQL queries, e.g.:
```
SELECT * FROM Movie
```
For Non-SSL Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j://neo4j-instance-host-name:7687
  Excluding enableSQLTranslation=true from the connection allows you to query Neo4j database using Cypher queries, e.g.:
```
MATCH (m:Movie) RETURN m.title AS Movie
```
For SSL Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://neo4j-instance-host-name:7687?enableSQLTranslation=true
For SSL Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://neo4j-instance-host-name:7687
For Neo4j AuraDB Connection (SQL queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://1234abcd.databases.neo4j.io?enableSQLTranslation=true
For Neo4j Aura Connection (Cypher queries), use these values when setting parameters:
- Connection string: jdbc:neo4j+s://1234abcd.databases.neo4j.io
You should see a message saying that connection test is successful:

Otherwise, if you are getting an error, check out our Community for troubleshooting tips.
We are at the point where we can preview a SQL query. For more SQL query examples visit JDBC Bridge documentation:
Neo4jDSN
```
SELECT * FROM Movie
```
```
SELECT * FROM Movie
```
You can also click on the <Select Table> dropdown and select a table from the list.

The ZappySys JDBC Bridge Driver acts as a transparent intermediary, passing SQL queries directly to the JDBC driver, which then handles the query execution. This means the Bridge Driver simply relays the SQL query without altering it.

Some JDBC drivers don't support INSERT/UPDATE/DELETE statements, so you may get an error saying "action is not supported" or a similar one. Please, be aware, this is not the limitation of ZappySys JDBC Bridge Driver, but is a limitation of the specific JDBC driver you are using.
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 Neo4j source in Informatica PowerCenter Workflow designer.

Open Workflow designer [W] icon
Goto Connections > Relational

Create a new connection for Neo4j in Informatica
Click New and select ODBC

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

Configure Neo4j connection in Informatica for REST API – Using ZappySys API Driver
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 Neo4j Source Definition in Informatica Mapping Designer

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

Open Informatica Mapping Designer (Click [D] icon)
Click on Source Icon to switch to Sources designer
From the top menu > Click on Sources > Import from Database …

Import Neo4j Source definition in Informatica Mapping Designer (JSON file or REST API)
Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
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 Neo4j Source Table in Informatica Mapping Designer (JSON file or REST API)
Select Table you wish to get (You can filter rows by custom SQL query. We will see later in this article how to do)
Optionally once table structure is imported you can rename it

Rename imported table definition in Informatica Source Designer
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.

In the Mapping Designer, Click on Target Icon to switch to Target designer
From the top menu > Click on Targets > Import from Database …
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
Enter your userid , password and Schema name and click Connect to see tables
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.

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

Define Source to Target mapping for Neo4j to SQL Table load in Informatica
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 Neo4j to SQL Table Mapping – Datatype conversion (nstring to datetime)
Once you done with mapping save your mapping and name it (i.e. m_Api_To_SQL)
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.

Open workflow designer by click [W] icon.
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 Neo4j data to SQL Table)
Finish the wizard and double-click the Session to edit some default properties.
First change Error settings so we fail session on error (By default its always green)

Fail Informatica Session on error (Neo4j data to SQL Load)
Select JSON connection for Source

Select Neo4j Source Connection in Informatica – Load Neo4j data to SQL Table
Change default Source query if needed. You can pass parameters to this query to make it dynamic.

Modify Neo4j Source SQL query – Pass parameters, change URL, set filter etc
Select Target connection of SQL Target Table

Select SQL Target Connection in Informatica – Load Neo4j data to SQL Table
Save workflow
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 JSON data to SQL Table in Informatica (Import REST API or JSON Files)

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

POST data to Neo4j 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

Optional: Centralized data access via ZappySys Data Gateway

In some situations, you may need to provide Neo4j 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.

	Data Gateway	Local ODBC data source
Simple configuration
Installation	Single machine	Per machine
Connectivity	Local and remote	Local only
Connections limit	Limited by License	Unlimited
Central data access
Central access control
More flexible cost

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 Neo4j data source in the gateway

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

Search for gateway in the Windows Start Menu and open ZappySys Data Gateway Configuration:
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
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 JDBC Bridge Driver
- Finally, click OK
Neo4jDSN

ZappySys JDBC Bridge Driver
When the ZappySys JDBC Bridge Driver configuration window opens, go back to ODBC Data Source Administrator where you already have the Neo4j 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 JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys JDBC Bridge Driver - Neo4j
  
  Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required.
  
  Neo4jDSN
- 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:
  
  Neo4jDSN
  
  ZappySys JDBC Bridge Driver - Configuration [Version: 2.0.1.10418]
  
  ZappySys JDBC Bridge Driver - Neo4j
  
  Read and write Neo4j data effortlessly. Query, integrate, and manage nodes, relationships, and graph data — almost no coding required.
  
  Neo4jDSN
- Once a window opens, just paste the settings by pressing CTRL+V or by clicking right mouse button and then Paste option.
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.
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:

Search for odbc and open the ODBC Data Sources (64-bit):
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.
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.
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
Then set the default database property to Neo4jDSN (the one we used in the Data Gateway):

Neo4jDSN

Neo4jDSN

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).
Continue by checking the Trust server certificate option:
Once you do that, test the connection:
If the connection is successful, everything is good:
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 Neo4j in Informatica PowerCenter via the Data Gateway. Follow these final steps:

Go back to Informatica PowerCenter.
Open Informatica Mapping Designer (Click [D] icon)
Click on Source Icon to switch to Sources designer
From the top menu > Click on Sources > Import from Database …

Import Neo4j Source definition in Informatica Mapping Designer (JSON file or REST API)
Select ODBC data source from the dropdown (Find out DSN we created earlier to use as JSON Source)
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 Neo4j Source Table in Informatica Mapping Designer (JSON file or REST API)
Read the data the same way we discussed at the beginning of this article.
That's it!

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

If you are asked for authentication details, use Database authentication, SQL authentication or Basic authentication option and enter the credentials you used when configuring the Data Gateway, e.g. john and your password.

Troubleshooters & resources (JDBC Bridge Driver)

Below are some useful community articles to help you troubleshoot and configure the ZappySys JDBC Bridge Driver:

How to combine multiple JAR files
Learn how to merge multiple .jar dependencies when your JDBC driver requires more than one file.
How to fix JBR error: “Data lake is not available / Unable to verify trust for server certificate chain”
Resolve SSL or certificate validation issues encountered during JDBC connections.
System Exception: “Java is not installed or not accessible”
Fix Java path or environment issues that prevent the JDBC Bridge from launching Java.
JDBC Bridge Driver disconnect from Java host error
Troubleshoot unexpected disconnection problems between SSIS and the Java process.
Error: Could not open jvm.cfg while using JDBC Bridge Driver
Resolve JVM configuration path errors during driver initialization.
How to enable JDBC Bridge Driver logging
Enable detailed driver logging for better visibility during troubleshooting.
How to pass JDBC connection parameters (not by URL)
Learn how to specify connection properties programmatically instead of embedding them in the JDBC URL.
How to fix JDBC Bridge error: “No connection could be made because the target machine actively refused it”
Troubleshoot firewall or local port binding issues preventing communication with the Java host.
How to use JDBC Bridge options (System Property for Java command line, e.g., classpath, proxy)
Configure custom Java options like classpath and proxy using JDBC Bridge system properties.

Conclusion

In this article we showed you how to connect to Neo4j in Informatica PowerCenter and integrate data without writing complex code — all of this was powered by Neo4j ODBC Driver. It's worth noting that ZappySys JDBC Bridge Driver allows you to connect not only to Neo4j, but to any Java application that supports JDBC (just use a different JDBC driver and configure it appropriately).

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):

Download Chat