This rule creates a department container in the destination data store, if one does not exist. Implement the rule on the Command Transformation policy in the driver. You can implement the rule on either the Subscriber or the Publisher channel or on both channels.
There are two steps involved in using the predefined rules: creating a policy in the Command Transformation policy set and importing the predefined rule. If you already have a Command Transformation policy that you want to add this rule to, skip to Importing the Predefined Rule.
From the
view or the view, select the Publisher or Subscriber channel.Select the Command Transformation policy set in the Policy Set view, then click
icon to create a new policy.Click
, then click .Name the policy.
Use the default location or browse and select another location to place the policy in the driver.
Select
, then click .Select
for the type of policy, then click .A file conflict window appears with the message “ Before editing this item you need to save. Do you wish to save the editor’s changes and continue?” Click . The Policy Builder is launched and the new Command Transformation policy is saved.
Continue with Section 8.1.2, Importing the Predefined Rule.
Right-click in the Policy Builder, then click
> or .Select
, then click .Right-click in Policy Builder and click
> or .Select
, then click .Save the rule by clicking
> .There is no information to change that is specific to your environment.
IMPORTANT:Make sure that the rules are listed in order. Part 1 must be executed before Part 2.
This rule is used when the destination location for an object does not exist. Instead of getting a veto because the object cannot be placed, this rule creates the container and places the object in the container.
Part 1 looks for any Add event. When the Add event occurs, two local variables are set. The first local variable is named target-container. The value of target-container is set to the destination DN. The second local variable is named does-target-exist. The value of does-target-exist is set to the destination attribute value of objectclass. The class is set to OrganizationalUnit. The DN of the OrganizationalUnit is set to the local variable of target-container.
Part 2 checks to see if the local variable does-target-exist is available. It also checks to see if the value of the local variable does-target-exist is set to a blank value. If the value is blank, then an Organizational Unit object is created. The DN of the organizational unit is set to the value of the local variable target-container. It also adds the value for the OU attribute. The value of the OU attribute is set to the local variable of target-container. It uses the source format as the destination DN and the destination format is dot format.