DSPD2AD:Examining a Dirsync Profile (4287970)

Issue

You have received a Dirsync Pro profile from a customer in order to troubleshoot a sync issue.  If you attempt to open the file all that’s displayed is garbage characters.

Solution

Here is a screen shot of a downloaded profile as received from a customer:

The information within the brackets in the name indicates the DSP product type (DominoToAD or ADtoAD) and the version number installed (ie:  19.7.xxxx).  The first part of the name of the profile reflects the profile name as it exists in DSP. 

In order to view the contents of the profile you need to perform the following steps:

• Rename the profile’s file extension (type) from dsprofile to zip.
• Unzip the profile

The unzipped results will contain the following file set:

Viewing the Profile

When you double click on profile.xml the file will be opened in a browser window by default.  This allows you to review a formatted version of the profile.  This is helpful to view the specific settings of the profile.  (an example is shown here)

Opening the profile in an editor such as Notepad, Wordpad, etc. allows you to easily search the profile for a specific text string but the profile is unformatted when viewed through an editor. 

MAPPINGS

The mappings.json file contains the mappings defined in DSP for all profiles (the mappings.json file included in any exported profile is identical to any other mappings.json file you will receive from a particular customer).  In order to view a formatted version of the mappings.json file you need to open it with Code Writer.  (Code Writer can be downloaded from the Internet).  When you open the mappings.json file you with see something similar to this:

Each block of information in the left-hand panel represents a unique mapping.

• SyncType accepted values: DominoToAD or ADToAD
• SourceEntryType/TargetEntryTypex values: any, user, group, room, resource. 
  • Mappings with a source of ‘any’ apply to all profiles
  • Mappings with values ‘user, group, room, or resource’ apply only to that specific type of profile
• SourceField: any valid field from the Domino or AD source record
• InternalField: the field defined within SQL to receive the data from the source
• TargetField: any valid field in the AD target

Clicking on the magnifying glass icon in the right border of the Code Writer screen allows you to search the contents of the mappings.json file for specific data.  The results will be displayed in the left-hand display panel (see example below):

Viewing the profile and mappings will help you trouble shoot a customer’s DSP environment.

OTHER .JSON FILES

The Meta.json file (shown here) contains the following specifics:

• SyncType values: DominoToAD, ADtoAD, or ADToDomino
• VerProduct displays the specific version of DSP installed at a customer site
• TimeStamp reflects the date/time of the last successful sync of the profile
• SyncName is the profile name within the customer’s configuration.

The Target.json file displays the following information shared by all similar profiles:

• DomainName will reflect the target Domain
• ServerFQDN will display the FQDN of the target server
• ServerIP displays the IP address of the target server
• Name displays the common name for the target server

The Source.json file contains nothing of value and can be ignored.