Understanding the Import Process

Typically, it is the administrator's responsibility to create import jobs to populate the Oracle Identity Analytics Identity Warehouse. Data can be imported from a text file or by using the Oracle Waveset (Sun Identity Manager) Data Exporter feature (if using Oracle Waveset / Sun Identity Manager as a provisioning server). Oracle Identity Analytics inserts or updates data in the data warehouse, and archives all of the data feeds.

The following import jobs can be executed in Oracle Identity Analytics:

User import
Resource metadata import
Resources import
Account import
Roles import
Policies import
Glossary import
Business structure import

To execute import jobs, you must have the schema file and the input file.

Note - You can import resource metadata and resources only if Oracle Identity Analytics is integrated with Oracle Waveset (Sun Identity Manager). For more information on importing resource metadata and resources, see “Integrating With Oracle Waveset (Sun Identity Manager)” in the Oracle Identity Analytics System Integrator's Guide.

Importing Users

Schema file - The schema file for the global user import is a standard .rbx file that needs to be located in the schema folder. The username field is mandatory, whereas the other fields are optional. A sample schema file for user import is shown here:

username,firstname,lastname,middlename,fullname,street,city,state,zip,country

The naming convention for the schema file is users.rbx.

Input File - The input file for user import maps every attribute in it to the schema file. The mapping between the user's schema file and the import file needs to be one-to-one.

The naming convention for the user import files is users <file number>.

The contents of a sample mapped user import file are shown here:

"Cox01","Alan 01","Cox","M","Alan,Cox, M","Test","Test","Test","90007","USA"

To Import Users

Add the users01 file
- For Windows - C:\Oracle\OIA_11gR1\import\in
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the users.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Schedule the import.

See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.
To Verify the Import, see Verifying Imports.

Importing Accounts

Schema file - Oracle Identity Analytics imports accounts by resource type. Each resource type has a schema file that defines the resource type's entitlements, and the order that the entitlements need to be listed in the input file. The file extension of the schema file is .rbx. The following declaration is required to map accounts to a resource type:

# @iam:namespace name="<resource type's Name>" shortName="<resource type's Short Name>"

username, endpoint, and domain are mandatory fields, whereas others are optional. The naming convention for the schema file is <resource type's Short Name>_accounts.rbx.

A sample schema file for the LDAP resource type is shown here:

# @iam:namespace name="LDAP" shortName="LDAP"

username<CorrelationKey>,comments,endpoint,domain,suspended,locked,AcidAll,AcidXAuth,FullName,GroupMemberOf,InstallationData,ListDataResource,ListDataSource,M8All

The previous example illustrates the list of attributes or entitlements that are defined for the LDAP resource type. The first entry has the name of the user account, and this is also the correlation or cross-reference key between user accounts and global users. The correlation key should have <Correlation Key> defined next to it. The resource refers to the target directories on the resource type. A list of entitlements used in LDAP are defined, and each entitlement is comma-separated from the other. If a custom entitlement from a resource type is to be imported, it can be defined in the schema file by adding the attribute in Oracle Identity Analytics and adding an entry in the schema file.

Input file — An input file contains the list of user accounts and a list of user entitlements in the accounts. Each file can be differentiated from the different resource types by the naming convention used in each file.

The naming convention for the files is <resource type's Short Name>_<file number>_accounts.

Sample content from this input file is shown here:

"Cox01","CNBNT","VAAU","rbactest.com",5,"false","false","CN=DomainUsers","consultant","","","DomainUsers""Consultant"

To Import Accounts

Add the LDAP_01_accounts file.
- For Windows — C:\Oracle\OIA_11gR1\import\in
- For UNIX — /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the LDAP_accounts.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Schedule the import.
- See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.
To Verify the Import, see Verifying Imports.

Importing Roles

Schema file - The schema file for the role import is a standard .rbx file that needs to be specified under the schema folder. The rolename field is mandatory, whereas the other fields are optional.

A sample schema file for role import is shown here:

RoleName<use=mandatory>,RoleDescription<use=required defaultValue="No Role Description">,customProperty2<use=required defaultValue="No Role Owner">

The naming convention for the schema file is roles.rbx.

Input file - The input file for roles maps every attribute in it to the schema file. The mapping between the role's schema file and import file needs to be one-to-one. The file name for the role import file needs to be roles <file number>. The contents of a sample mapped role import file are shown here:

"Auditor","EERS MODEL ID SG-RPAC","Auditor"

To Import Roles

Add the roles01 file.
- For Windows - C:\Oracle\OIA_11gR1\import\in
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the roles.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Schedule the import.

See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.

Importing Policies

Schema file - The schema file for the policy import is a standard .rbx file that needs to be located in the schema folder. The following declaration is required to map policies to a resource type:

# @iam:namespace name="<resource type's Name>" shortName="<resource type's Short Name>"

The EndPointName and policyname fields are mandatory, whereas the other fields are optional. The naming convention for the schema file is <resource type's Short Name>_policies.rbx.

A sample schema file for role import is shown here:

# @iam:namespace name="LDAP" shortName="LDAP"

Endpoints<use=mandatory >,PolicyName,Roles,policycomments,PolicyDescription,ldapGroups

Input file - The mapping between the policy's schema file and the import file needs to be one-to-one. Each file can be differentiated from the different resource types by the naming convention used in each file. The naming convention for the files is <resource type's Short Name>_<filenumber>_policies. The contents of a sample policy import file mapped are shown here:

"LDAP","Investment Management Attorney_LDAP","Investment Management Attorney","Manual Policy import","Investment Management Attorney_LDAP","CN=DEPT_LEGL,ou=Groups,dc=identric,dc=com"

To Import Policies

Add the LDAP_01_policies file.
- For Windows - C:\Oracle\OIA_11gR1\import\in
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the LDAP_policies.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Schedule the import.

See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.

Importing Business Structures

Schema file - The schema file for the business structure import is a standard .rbx file that needs to be located in the schema folder. The businessUnitname field is mandatory, whereas the other fields are optional. The naming convention for the schema file is businessstructure.rbx.

A sample schema file for business structure import is shown here:

businessUnitName,parentBusinessUnitName,statusKey,division,mainPhone,otherPhone,fax,email,website,street1,street2,street3,city,stateOrProvince,zipOrPostalCode,countryOrRegion,

businessUnitType,businessUnitOwner,businessUnitAdministrator,mailCode,businessUnitDescription,businessUnitCode,serviceDeskTicketNumber,businessUnitManagers

Input file - The mapping between the business structure's schema file and the import file needs to be one-to-one. The naming convention for the files is businessstructure_<file number>

To Import Business Structures

Add the businessstructure_01 file.
- For Windows - C:\Oracle\OIA_11gR1\import\in
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the businessstructure.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Schedule the import.

See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.

Importing Glossary Definitions

Schema file - The schema file for the glossary import is a standard .rbx file that needs to be located in the schema folder. Previously, glossary import did not require a schema file. The following declaration is required to map glossary to a resource type:

# @iam:namespace name="<resource type's Name>" shortName="<resource type's Short Name>"

The EndPointName, attributeName, and attributeValueValue fields are mandatory, whereas the other fields are optional. The naming convention for the schema file is

<resource type's Short Name>_glossary.rbx.

A sample schema file for glossary import is shown below:

# @iam:namespace name="LDAP" shortName="LDAP"

endPointName,attributeName,attributeValueValue,owner,highPrivileged,classification,definition,comments

Input file - The mapping between the glossary's schema file and the import file needs to be one-to-one. Each file can be differentiated from the different resource types by the naming convention used in each file. The naming convention for the files is <resource type's Short Name>_glossary<file number>.

To Import Glossary Definitions

Add the LDAP_glossary01 file.
- For Windows - C:\Oracle\OIA_11gR1\import\in
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/in
Add the LDAP_glossary.rbx file.
- For Windows - C:\Oracle\OIA_11gR1\import\schema
- For UNIX - /opt/Oracle/OIA_11gR1/rbacx/import/schema
Glossary import jobs can only be scheduled through the back-end. See Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter for more information.

Scheduling Import and Export Jobs

For information about scheduling import and export jobs, see Scheduling Import and Export Jobs in Oracle Identity Analytics in the Oracle Identity Analytics Scheduling chapter.

Skip Navigation Links
Exit Print View
	Oracle Identity Analytics Business Administrator's Guide 11g Release 1