When the technical and security-related prerequisites are in place, you're ready to create a remote source. There are two main ways to do that:
- In the catalog of the SAP HANA Database Explorer, with the graphical user interface
- In any SQL console connected to your local/target database, with an SQL statement
Let's discuss the graphical user interface-based creation process first.
To Create a Remote Source with the Graphical User Interface
- Navigate the Catalog to the Remote Sources section.
- Right-click Remote Sources, and choose Add Remote Source.
- Define the remote source name.
- Choose the relevant Adapter.
- For SDI remote sources, specify an adapter location ("Source Location").
- Fill in the remote source property.
- Choose Create.
Launch this video to learn how to create a Smart Data Access remote source with the form-based editor in SAP HANA Database Explorer.
Creating remote sources for Smart Data Integration scenarios with the graphical user interface is very similar to what we have just discussed. One key difference is that, because the adapters aren't running on the indexserver of the SAP HANA database instance, it's necessary to specify where the adapters are located. Here's a reminder:
- OData adapters run on the data provisioning server (inside the database).
The location dpserver is automatically assigned and can’t be changed.
- All others Smart Data Integration adapters run on a data provisioning agent
You specify either a data provisioning agent, either a data provisioning agent group in case several agents are part of a high-availability agent group.
Note
The configuration of agents is determined by the system administration team. What you just need from them is the information on which agent or agent group should be used in a particular scenario.
Launch this video to learn how to create a Smart Data Integration remote source with the form-based editor in SAP HANA Database Explorer.
Checking a Remote Source
When you create a remote source in the SAP HANA Database Explorer with a form, two successive automatic checks are executed.
- Remote source consistency – Blocking
The remote source definition must be "syntactically" correct with all the required parameters filled out.
The check might fail, for example, if you forgot the server name or didn’t provide the user name and password for a technical user.
In that case, the remote source can't be created. You must modify the definition of the remote source and try to save it again.
Note
In the remote source definition form, all mandatory parameters are identified with a red asterisk. - Remote source connectivity – Non-blocking
This second-level check, automatically triggered in the SAP HANA database explorer form, verifies whether the remote source definition allows SAP HANA to connect to the remote system and authenticate the remote user.
If this check isn’t passed, you only receive a warning, which does NOT prevent the creation of the remote source.
The check might fail, for example, due to an error in the server name or in the SAP Cloud Connector configuration (if applicable), or simply because the remote server isn't currently available. Another reason could be because the remote source is defined with secondary credentials but no credential currently exists for your user.
In that case, only a warning is issued. You can modify the definition of the remote source immediately (for example, if you identify an obvious error), but you can also save the remote source definition as is, and modify it later on.