Import

There are general settings that are relevant for all source systems. Connection strings and import source systems are common settings, while master data settings are specific to source systems.

ODW Connection strings

The connection strings to the ODW databases are maintained in a common configuration file named Omada ODW ConnectionString.dtsConfig, which is located at C:\Program Files\Omada Identity Suite\Datawarehouse\Common. This file is used by all the Omada ODW SSIS packages.

The file Omada ODW ConnectionString.dtsConfig contains four connection string settings that you can configure. These settings are described in the table below.

You should normally enter these strings in the installation wizard, but you can edit them if the connections change.

Setting	Description
OLE_CON ODW	The OLE DB connection string to the Omada Identity Data Warehouse database.
OLE_CON ODWMD	The OLE DB connection string to the Omada Identity Data Warehouse Master database.
OLE_CON ODWS	The OLE DB connection string to the Omada Identity Data Warehouse Staging database.
OLE_CON SSIS	The OLE DB connection string to the SQL Server instance on the SSIS Server. The name of the SQL Server instance was entered during the installation of the Omada ODW SSIS packages.

important

Due to hardened security, customers who use SQL user/password authentication are required to manually encrypt password in the connection strings present in the ConnectionString.dtsConfig file with the StringEncrypter. If the password is not encrypted, data import will not be possible.

With the help of the StringEncrypter tool it is possible to encrypt the entire ConnectionString, for example,

Initial Catalog=Omada Data Warehouse;Data Source=localhost;Uid=test;Pwd=sa1dd1f;Provider=MSOLEDBSQL19;

as

AES256:LZ7qTetSlqe8G4+pr0jkaDiojSkH5ryzb/ZxhjTEFGw6RX5SrzHwprIuxZrg/bYqzCf+tUDrKSf4/iffprX9SOE4UrY3VRGOMDCee+ylqfnX+zQq0ITALhG0kyl2vG24pk0ks/txclFHb+6swqtT6w===AES256

or create a partially encrypted ConnectionString with the full password section encrypted, for example,

Initial Catalog=Omada Data Warehouse;Data Source=localhost;Uid=test;AES256:kqieFRqaXqoJaiG3zmo9qA===AES256;Provider=MSOLEDBSQL19;

info

This solution does NOT work only in the case of encrypting the password itself, as the Pdw= section is stripped during import.

Troubleshooting

In case if the encryption key is set incorrectly and connection strings in the Omada ODW ConnectionString.dtsConfig are encrypted with this invalid key, the imports will not be started correctly, and no logs will be recorded due to inability to access log table [sysssislog]. However, this situation causes listing an error in the Windows Event log.

ODW Web Service configuration settings

You can edit the following settings in the Omada ODW Webservice.dtsConfig file. In a default installation, it is located at C:\Program Files\Omada Identity Suite\Datawarehouse\Common.

Setting	Description
WebServiceURL	The URL for the Enterprise Server data object exchange web service.
UseDefaultCredentials	This setting must be True or False. If you set this setting to True, the web service is called using integrated security, with the user that runs the ODW Import package. If you set this setting to False, the web service is called using basic authentication, with the configured credentials. The user calling the Enterprise Server web service must be a member of the Data Admin group in Enterprise Server.
Domain	The domain of the user that calls the web service. If your organization uses basic authentication in Enterprise Server, the value should be the Customer name as specified in the tblCustomer table in the Enterprise Server database.
User	The user that calls the web service, when basic authentication is in use.
Password	The encrypted password of the user that calls the web service when basic authentication is in use.
SecurityProtocol	The SecurityProtocol value. If the value is not set, configured packages will use the default security protocols of TLS 1.0. For the possible values of the SecurityProtocol enumeration, see the following link and use the numeric value (for example, 3072 for TLS 1.2): SecurityProtocolType Enum.