Configuring the Properties File

Configuring User Attributes 13-23 Enter OIM UDF Name to be Synchronized: Specify the Oracle Identity Manager entity attribute which has been created successfully. Enter the LDAP attribute name in LDAP schema: Specify the LDAP attribute present in the LDAP directory server as well as in the OVD schema. This is an optional parameter for the DELETE operation. One set of operation is completed. If the operation is successful, then you are prompted, as shown: Want to continue adding deleting more attributes yn? Enter y if you want to start the input process for another operation. Otherwise, enter n to end the program. ■ Run the utility with values for the -Dinputfile and -Dconfig.properties command-line parameters. The input is read from the input file. The input file can contain multiple inputs, one per line. Each input contains four parameters for ADD operation or three parameters for DELETE operation. If you provide the fourth parameter for a DELETE operation, then it is ignored.

13.6 Configuration Management Architecture

For all attribute definitions and the Configuration Management pages in the UI, the configuration file for maintaining the user entity attributes is User.xml. This configuration file defines all attributes of user entity and their properties. The mapping of the attribute to the backend attributes or columns is also specified in the file. The attributes to be displayed on the UI are determined based on the attribute properties. For example, if an attribute is system-controlled, then the attribute is not displayed in the UI. Example 13 1 shows the code for a sample User.xml configuration file: Example 13 1 The User.xml Configuration File ?xml version=1.0 encoding=UTF-8? tns:entity-definition xmlns:tns=http:www.oracle.comschemaoimentity xmlns:xsi=http:www.w3.org2001XMLSchema-instance xsi:schemaLocation=http:www.oracle.comschemaoimentity ..entity.xsd entity-type child-entity=falseUserentity-type -- Defines the repository and data provider to use for this entity -- provider-instance repository-instanceOperationalDBrepository-instance provider-typeUserDataProviderprovider-type parameters parameter name=table valueusrvalue parameter parameter name=id_column valueusr_keyvalue parameter parameter name=usr_foreign_key_column valueusr_manager_keyvalue parameter parameter name=org_table valueactvalue parameter 13-24 Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager parameter name=org_id_column valueact_keyvalue parameter parameter name=org_foreign_key_column valueparent_keyvalue parameter parameter name=foreign_search_table valueact:usrvalue parameter parameter name=foreign_search_table_alias valueactorg:usrmgrvalue parameter parameter name=foreign_search_table_to_join_key valueactorg.act_key:usrmgr.usr_keyvalue parameter parameter name=foreign_search_table_from_join_key valueusr.act_key:usr.usr_manager_keyvalue parameter parameter name=foreign_search_column valueactorg.act_name:usrmgr.usr_display_namevalue parameter parameter name=foreign_search_column_label valueOrganization Name:Manager Loginvalue parameter parameter name=foreign_search_column_alias valueactorg_act_name:usrmgr_usr_loginvalue parameter parameter name=foreign_search_column_outer_join valuefalse:truevalue parameter parameters provider-instance container-capability enabledfalseenabled container-capability -- entity-attributes define the attributes at the API level. These are the attribute names that the API will return and expects -- entity-attributes attribute name=usr_key typenumbertype searchabletruesearchable requiredfalserequired MLSfalseMLS multi-representedfalsemulti-represented attribute-groupBasicattribute-group -- The metadata attachment defines the enttiy attribute properties. These properties will be common across all entities -- metadata-attachment -- Whether the attribute is searchable by the user -- metadata nameuser-searchablename valuetruevalue categorypropertiescategory metadata -- Whether the attribute can be updated in bulk -- metadata namebulk-updatablename valuefalsevalue