This is an old revision of the document!
Table of Contents
Connectors
A connector in EasyMorph holds information about connection settings required to connect to an external system, such as a database, cloud service, email, enterprise application, or REST API.
Connectors can be embedded into a project, or can be stored in a shared repository. Connectors can be copied/pasted from any location to any location, e.g. from one project to another project, from project to repository, from one repository to another repository, etc.
Embedded connectors
Embedded connectors are stored right in project. It allows using projects on different computers using the same connection settings without relying on a shared repository. However, if connection settings change (e.g. credentials changed) then all embedded connectors for this connection should be changed manually.
Shared connector repository
Shared connector repositories can be used in cases when many users need to use the same connection settings in a controllable, centralized fashion.
An empty shared repository is created automatically by EasyMorph upon first run. It can also be created manually from Connector Manager invoked by menu Project → Manage connectors, or by pressing F7. It is possible to have several repositories, but only one repository can be active in EasyMorph. Switching to another repository can be done through Connector Manager. Shared connectors are referenced in projects by name. Therefore, if you switch between two repositories (e.g. one for development and one for production), make sure that connector name is the same in both repositories.
To reduce a chance of human error, a shared repository can be protected with a password requested for adding new or modifying existing connectors. Using a connector for importing data doesn't require a password. Passwords can be set up and changed in Connector Manager.
Having shared repositories is also convenient for migrating projects from dev to test/prod environments as shared connectors are referenced by name. I.e. a project can query a database that is specified by connector "Customers". In a test environment a connector named "Customers" can point to a test database, while in a production environment a connector named also "Customers" point to a production database. When moved from one environment to another, the project will use necessary connector automatically.
Server-hosted connector repository
A shared repository can be served to Desktop users from EasyMorph Server. This provides better security as the repository files can't be accessed by Desktop users. Additionally, connectors can be protected from copying and thus embedding. Finally, if a repository is provided from a Server space with Active Directory authentication model, then only the users that are whitelisted in the space settings can access and use the repository.
In order to use a Server-hosted repository, the Server Link must be configured in Desktop. For more details please read the "EasyMorph Server Administrator Guide" which comes with the Server installer.
Database connectors
Currently EasyMorph supports these database types and SQL dialects:
Database type | Driver type |
---|---|
Oracle | ODBC / Native |
SQL Server | ODBC / Native |
MySQL | ODBC / Native |
PostgreSQL | ODBC / Native |
SQLite | ODBC / Native |
Azure SQL Database | ODBC / Native |
Amazon Redshift | ODBC only |
DB2 | ODBC only |
DB2 for iSeries (AS/400) | ODBC only |
Vertica | ODBC only |
SAP HANA | ODBC only |
Generic SQL:2003 | ODBC only, custom SQL only |
Email connectors
System connectors
- SSH (used also for SFTP/SCP transfers)
- Web location (used also for REST API)
Enterprise applications
Cloud services/applications
Security considerations
While EasyMorph encrypts connection passwords stored in projects and repositories, this can't be considered a strong security measure. Therefore for addition security consider the following:
- Use Server-hosted connector repositories when possible, otherwise limit access to shared repositories using standard Windows file system permissions
- Use in connectors accounts that are read-only and doesn't expose unnecessary objects (e.g. schemas, tables, etc.)
- Don't use embedded connectors for sensitive information
- Keep in mind that users may write custom SQL queries/statements using connectors