Skip to main content
21-Topaz II
January 25, 2012
Question

Installing and Configuring PDM/Link

  • January 25, 2012
  • 22 replies
  • 5100 views
Hello,



I'm new to the list as we are looking to implement PDM/Link on a trial
basis. We own 8 heavy seats with our 8 Pro/E seats, but haven't used it
due to the perceived cost of the overhead in terms of day to day use.
In other words, it seemed like overkill in an environment like ours of
rapidly changing projects and very little ongoing data. However, when
we do larger projects with more than a couple of people working on the
same database, we realize that a data management solution would be a
benefit.



Since we have the licenses and a server with extra capacity, we want to
see if we can get it set up and give it a trial run on an upcoming
project. I've been given the task of getting it set up for that project
which is due to launch in approximately 2 weeks.



My biggest question is, is it reasonable to think that in 2 weeks I can
learn enough to install and configure PDM link properly so we have a
good test of whether it meets our needs? We should not have a complex
installation; we simply want to manage revisions and who's working on
what. What I don't want to do is get something set up, but not
properly, we then have a bad experience and dismiss PDM Link due to poor
implementation. Or worse, the implementation hampers getting the actual
work done.



Is going from zero to running in 2 weeks (without a consultant)
reasonable?



Doug Schaefer

22 replies

1-Visitor
January 30, 2012
David and Rohan

thanks for the pointers. Corporate ldap has two special characters in the
password. And due to this, there were two extra "\"s in codebase\web-inf\map
credential text file. Once we clean up the map credential file, the migrator
is moving ahead.



Thanks again for pointing the correct direction.



Best Regards

Swamy Senthil


1-Visitor
January 30, 2012
Senthil,



In situations where you are using the same LDAP for both source and target,
restarting the Upgrade Manager could remove LDAP entries.



See the below workaround developed by Datafrond Team, resolution logged
within the Datafrond database. If you experience similar symptoms, try
applying the below resolution.




Upgrade Manager Fails at Step: Execute Standalone Migrators

WC10SERVER1

PTC Support Case 10540246 (Workaround)



Refer to an existing SPR 2095047, however differnet symptoms. Follow the
below workaround for Customer until PTC provides a resolution.

Customer Symptom: Each time you exit upgrade manager, pending users node in
LDAP gets deleted.

Workaround: As a pre-ugprade step, ensure that the pending users node exists
in the Windchill DS. If doesn't load the pending users data has been
modified to reflect the new domain - corp.cusotmername.com







Hemant Jatla | Datafrond LLC - hjatla@datafrond.com