The following extract from a configuration file contains the changes required for the example in section Customizing the configuration file.
<?xml version="1.0" encoding="utf-8"?>
<SynchronizationEditorWorkspace Version="1.0">
<Parameters>
<Parameter Name="Database" Display="Connected database" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="DBUser" Display="Database server user" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="DBPassword" Display="Database server password" IsQueryParameter="true" IsSecret="true"></Parameter>
<Parameter Name="SystemUser" Display="One Identity Manager system user" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="SystemPassword" Display="Password of system user" IsQueryParameter="true" IsSecret="true"></Parameter>
<Parameter Name="Domain" Display="Distinguished name of the domain" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="DomainController" Display="Distinguished name of the domain controller" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="ADUser" Display="Active Directory user" IsQueryParameter="false" IsSecret="false"></Parameter>
<Parameter Name="ADUserPassword" Display="Password of Active Directory user" IsQueryParameter="true" IsSecret="true"></Parameter>
<Parameter Name="SyncProject" Display="Synchronization ProjectA collection of all data required for synchronizingThe processSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database. and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this." IsQueryParameter="false" IsSecret="false"></Parameter>
</Parameters>
<Global>
<Data Name="WorkDatabase.ConnectionString" Display="Connection string" Type="System.String, mscorlib">data source=Database server;initial catalog=$Database$;user id=$DBUser$;pooling=false;Password=$DBPassword$</Data>
<Data Name="WorkDatabase.AuthenticationString" Display="Authentication string" Type="System.String, mscorlib">ModuleA module is a closed unit with a defined functionality. A module includes descriptive information, the binaries (exe, DLL), the documentation, and information about the database (see also One Identity Manager schema).=Authentication method;User[VI.DB_USER]=$SystemUser$;(Password)Password[VI.DB_Password]=$SystemPassword$</Data>
<!-- … -->
</Global>
<Editors>
<Editor Name="ShellWizard" Type="VI.Projector.Editor.Wizards.ShellWizard, VI.Projector.Editor">
<!-- … -->
<Data Name="ShellDisplay" Display="Script display name" Type="System.String mscorlib">$SyncProject$</Data>
<!-- … -->
<Data Name="MainConnection.ConnectionParameter" Display="Connection parameter" Type="System.String, mscorlib">Authentication=ProjectorAuthenticator;data source=databaseserver; DBFactory="VI.DB.ViSqlFactory, VI.DB";initial catalog=$Database$;password=$DBPassword$; pooling=False;user id=$DBUser$</Data>
<!-- … -->
<Data Name="ConnectedSystemConnection.ConnectionParameter" Display="Connection parameter" Type="System.String, mscorlib">ADAuthentication=1;ADEnableras=False;ADEnablerecyclebin=False; ADEnableterminal=True;ADPort=389;ADRootdn=$Domain$;ADServer=$DomainController$; ADTypeEnableExtensions=True;ADTypeExtensions=;baseloginaccount=$ADUser$; basepassword=$ADUserPassword$</Data>
<!-- … -->
</Editor>
</Editors>
</SynchronizationEditorWorkspace>