Installation guide

2. Compare the privileges in the database with the role mapping in the migrate-users.exe.config
file.
3. To map an IMPAX or WEB1000 privilege to a custom IMPAX 6.5.3 role, add additional map
entries.
For example, to map a user with RADIOLOGIST privileges to a custom role called Pediatric
Radiologist in IMPAX 6.5.3, add the following line before the default privileges_level line:
<map privilege_level="RADIOLOGIST"
role="Pediatric Radiologist" dn="cn=Radiology" />
4. Save the file.
A detailed comparison of operations and access controls in IMPAX 6.5.3 and privileges and
components in IMPAX 5.2 or 5.3 is available in the “Privilege and permission comparison” section
(topic number 54910) of the IMPAX Migrations Reference Guide. Most of this information also
applies to IMPAX 4.5.
Converting both IMPAX and WEB1000 user
information to LDF
(Topic number: 6700)
5.
When using the migrate-users tool in the xml2ldf mode, and processing both IMPAX and WEB1000
users, the following rules apply:
1. An IMPAX user is exported to the .ldf file with all exported preferences that are to be migrated
to IMPAX 6.5.3.
2. A WEB1000 user with no corresponding IMPAX userid is exported to the .ldf file, but only the
privilege level is migrated to the IMPAX 6.5.3 role; WEB1000 preferences and team information
is not migrated.
3. Any user with a matching user name but different userid will have a number appended to the
user name, because LDAP requires user names to be unique.
4. Any WEB1000 user with a matching userid and password in IMPAX is assumed to be the same
user, so the WEB1000 user is discarded and the IMPAX profile is used.
5. Any WEB1000 user with the same userid but different password is possibly a different user, so
the WEB1000 userid has a suffix appended, and is written to a different .ldf file (conflicts.ldf).
This file must be imported separately with ldifde.exe if these additional users are to be migrated.
Converting the user data to LDF
(Topic number: 6719)
6.
In IMPAX 6.5.3, user authentication, user preferences, and user permissions are stored in an AD
LDS database or an external LDAP. Before the user data can be migrated from the IMPAX or
WEB10000 MVF database into the AD LDS database, the exported MVF data must first be converted
AS300 Preparing to Upgrade Guide—IMPAX 4.5, 5.2, 5.3,or WEB1000 to IMPAX 6.5.3 97
Agfa Company Confidential—Subject to Non-Disclosure Obligation