Syntax for oidprovtool Managing Provisioning Profiles Using oidprovtool

13-6 Oracle Fusion Middleware Administrators Guide for Oracle Directory Integration Platform event_mapping_rules=EMP:l=AMERICA:l=AMER,cn=users,dc=company,dc=com event_mapping_rules=EMP::cn=users,dc=company,dc=com event_permitted_operations=OBJECT:DOMAIN:OPERATIONattributes,... Required for create and modify operations on INBOUND events only. This property is used to define the types of events that the application is allowed to send to the Oracle Directory Integration Platform service. A provisioning profile can have multiple permitted operations defined. For example, if you wanted to permit the application to send events whenever a user object was added or deleted, or when certain attributes were modified, you would have three permitted operations such as this: event_permitted_operations=USER:dc=mycompany,dc=com:ADD event_permitted_operations=USER:dc=mycompany,dc=com:MODIFYcn,sn,mail,password event_permitted_operations=USER:dc=mycompany,dc=com:DELETE event_subscription=USER | GROUP:DOMAIN:OPERATIONattributes,... Required for create and modify operations on OUTBOUND events only. This property is used to define the types of events that the Oracle Directory Integration Platform service should send to the application. A provisioning profile can have multiple event subscriptions defined. For example, if you wanted the directory integration server to send events to the application whenever a user or group object was added or deleted, you would have four event subscriptions such as this: event_subscription=GROUP:dc=mycompany,dc=com:ADD event_subscription=GROUP:dc=mycompany,dc=com:DELETE event_subscription=USER:dc=mycompany,dc=com:ADD event_subscription=USER:dc=mycompany,dc=com:DELETE max_events_per_schedule=number Optional for create and modify operations only. The maximum number of events to be provisioned in one schedule. The default is 100. max_retries=number Optional for create and modify operations only. The number of times a failed event should be retried. The default is 5. profile_group=number Required for create and modify operations only. The group number of the profile. Default is DEFAULT. This is required to address scalability issues when different Oracle Directory Integration Platform server instances will be used to execute different selected groups. profile_status=ENABLED | DISABLED Required for the create operation only. Determines whether the profile is enabled or disabled. The default is ENABLED. profile_debug=debug_level Required. The debug level for the profile.

13.2.3 Tasks and Examples for oidprovtool

You can perform the following tasks using oidprovtool: Deploying Provisioning-Integrated Applications 13-7 ■ Creating a Provisioning Profile ■ Modifying a Provisioning Profile ■ Deleting a Provisioning Profile ■ Disabling a Provisioning Profile

13.2.3.1 Creating a Provisioning Profile

The following example creates a new provisioning profile that makes Portal aware of updates to the user and group information that is maintained in Oracle Internet Directory. Example: oidprovtool operation=create ldap_host=myhost.mycompany.com ldap_port=389 \ ldap_user_dn=cn=orcladmin application_ dn=orclApplicationCommonName=PORTAL,cn=Portal,cn=Products,cn=OracleContext \ organization_dn=dc=us,dc=mycompany,dc=com interface_name=PORTAL.WWSEC_OID_SYNC \ interface_type=PLSQL interface_connect_info=myhost:1521:iasdb:PORTAL:password \ schedule=360 event_subscription=USER:dc=us,dc=mycompany,dc=com:DELETE \ event_subscription=GROUP:dc=us,dc=mycompany,dc=com:DELETE \ event_ subscription=USER:dc=us,dc=mycompany,dc=com:MODIFYorclDefaultProfileGroup,userpa ssword \ event_subscription=GROUP:dc=us,dc=mycompany,dc=com:MODIFYuniqueMember \ profile_mode=OUTBOUND

13.2.3.2 Modifying a Provisioning Profile

The following example modifies an existing provisioning profile for the Portal application. It changes the event subscription for the attributes that are provisioned when a user entry is modified. Example: oidprovtool operation=modify ldap_host=myhost.mycompany.com ldap_port=389 \ ldap_user_dn=cn=orcladmin application_ dn=orclApplicationCommonName=PORTAL,cn=Portal,cn=Products,cn=OracleContext \ organization_dn=dc=us,dc=mycompany,dc=com \ subscription=USER:dc=us,dc=mycompany,dc=com:MODIFYorclDefaultProfileGroup,userpa ssword,mail,cn,sn

13.2.3.3 Deleting a Provisioning Profile

The following example disables a provisioning profile for the Portal application. Example: oidprovtool operation=delete ldap_host=myhost.mycompany.com ldap_port=389 \ ldap_user_dn=cn=orcladmin application_ dn=orclApplicationCommonName=PORTAL,cn=Portal,cn=Products,cn=OracleContext \ organization_dn=dc=us,dc=mycompany,dc=com

13.2.3.4 Disabling a Provisioning Profile

The following example disables a provisioning profile for the Portal application.