This section will guide you through the process of setting up the import from custom ODBC-enabled data source. If you already have the data source prepared in required format, you can continue to chapter Setting Up the ODBC Import.

 

Before you start to configure the import, you need to prepare data in required format. You need to migrate them to the tables with following structure or create views with the same structure.

 

Source Data Structure

 

Here you can find required format of source data. You don't have to provide all tables - provide only those that you need. You can also enhance the tables/views with any additional columns from your database.

 

		Performance
		If you're going to import large amounts of data using the ODBC provider, it's recommended that you create and fill tables called View_MembersOfGroup, View_MembersOfOU, etc. instead of creating views of that name. Then you should create a separate index on each column and run the import.

 

View_Users - list of users

Column Name	Data Type	Description
AR_ObjectGUID	varchar(255)	unique ID of the user
AR_ObjectAlias	varchar(255)	unique object alias, it can be same as the AR_ObjectGUID or AR_Login
AR_ObjectName	varchar(255)	full name that will be displayed
AR_Login	varchar(255)	unique login name of the user

 

View_Groups - list of user groups

Column Name	Data Type	Description
AR_ObjectGUID	varchar(255)	unique ID of the user
AR_ObjectAlias	varchar(255)	unique object alias, it can be same as the AR_ObjectGUID or AR_Login
AR_ObjectName	varchar(255)	full name that will be displayed

 

View_OrgUnits - list of organizational units

Column Name	Data Type	Description
AR_ObjectGUID	varchar(255)	unique ID of the user
AR_ObjectAlias	varchar(255)	unique object alias, it can be same as the AR_ObjectGUID or AR_Login
AR_ObjectName	varchar(255)	full name that will be displayed

 

View_MembersOfGroup - list of members of groups

Column Name	Data Type	Description
Group_AR_ObjectGUID	varchar(255)	unique ID of the group (AR_ObjectGUID value used in the View_Groups)
Member_AR_ObjectGUID	varchar(255)	unique ID of the member (AR_ObjectGUID value used in the View_Groups or View_Users or View_OrgUnits)

 

View_MembersOfOU - list of members of organizational units

Column Name	Data Type	Description
OrgUnit_AR_ObjectGUID	varchar(255)	unique ID of the organizational unit  (AR_ObjectGUID value used in the View_OrgUnits)
Member_AR_ObjectGUID	varchar(255)	unique ID of the member  (AR_ObjectGUID value used in the View_Groups or View_Users or View_OrgUnits)

 

Each record in view_users, view_groups and view_orgunits must be uniquely identified within all of them by its AR_ObjectGUID column value. You may ensure it by creating AR_ObjectGUID value based on table specific prefix + primary key value; e.g.:

• AR_ObjectGUID for users may have the following format: 'Users_UserID=12345'
• AR_ObjectGUID for groups may have the following format: 'Groups_GroupID=12345'
• and AR_ObjectGUID for organizational units may have the following format: 'OrgUnits_OrgUnitID=12345'.
  

The real format of AR_ObjectGUID value is up to you, but bear in mind that it must uniquely identify records within all view_users, view_groups and view_orgunits tables and it mustn't be changed in time otherwise the relation between records in Secure Access catalog and the data source will be broken.

 

AR_ObjectAlias column used in view_users, view_groups and view_orgunits refers to the Object Alias field in the Secure Access application. The AR_ObjectAlias values should be unique within table - the import process will ensure it by automatic adding numerical suffixes (1,2,3,4,...) to the values if necessary.

 

AR_ObjectName column used in view_users, view_groups and view_orgunits refers to the Name field in the Secure Access application. There are no restrictions on the AR_ObjectName values.

 

AR_Login column used in view_users refers to the User Name field in the Secure Access application. The AR_Login values should be unique within table - the import agent will ensure it by adding numerical suffixes (1,2,3,4,...) to the values if necessary.

 

The order of columns in the view_* tables is not critical, however they must contain at least columns specified above.

 

Once you have the data structure prepared you can continue to setting up the import itself.