Migrating from WindchillDS to OpenDJ or Another v3-compliant Directory Server
If you are updating to PTC Arbortext Content Delivery 7.2.x.x server, you must import the LDIF file generated from WindchillDS to OpenDJ. Following are the available upgrade and update paths:
• Upgrade: InService 6.x to PTC Arbortext Content Delivery 7.2.x.x
• Update: PTC Arbortext Content Delivery 7.x.x.x to 7.2.x.x
 |
• Ensure that WindchillDS is uninstalled. To uninstall the standalone installed WindchillDS, perform the following steps to avoid errors during your LDAP server installation.
1. Run the uninstall files as follows:
▪ For Windows: Navigate to the WindchillDS_HOME/InS_SW/SW/System/WindchillDS/Server/ folder and run uninstall.bat
▪ For Linux: Navigate to the WindchillDS_HOME/InS_SW/SW/System/WindchillDS/Server/ folder and run uninstall.sh
2. Select all the options present on the uninstaller panel and then uninstall the WindchillDS.
3. Once the uninstall process is complete, remove the WindchillDS folder manually.
|
Migrating to the OpenDJ Server
To migrate the user data from WindchillDS to OpenDJ server, perform the following steps:
1. Install OpenDJ Community Edition LDAP v3-compliant Directory Server.
2. Create the same Base DN as in PTC Arbortext Content Delivery (for example, o=ptc)
3. Export a .ldif file of the users from WindchillDS.
4. Edit the .ldif file in a text editor and replace objectClass:ptcSubtree with objectClass:organizationalRole.
ptcSubtree is a PTC custom class used in WindchillDS for DN nodes starting with cn. You must change it when you migrate the users to another Directory Server, while retaining the DN structure of the users. For example,
◦ cn=InService,o=ptc
◦ cn=AdministrativeLdap,cn=InService,o=ptc
|
|
If custom attributes are present for users in WindchillDS, make sure you create those attributes in OpenDJ before import.
To add the attributes in OpenDJ, see Mapping User Enterprise Attributes
|
5. Import the .ldif file to OpenDJ Community Edition.
6. Clear the Schema Validation option.
Migrating to Another v3-compliant Directory Server
Migrating users to any other v3-compliant Directory Server has requirements that are unique to the implementation and attribute mapping for a specific system and corporate policy. For this reason, you must consider migrations of this type as independent projects adapted for the specific need. PTC recommends the engagement of professional services for assistance in the development of migration process and tooling.