Home › Forums › Luminis Platform / System

updated migrator jar file

Mon, 2008-09-01 16:55 — bsteward

Where do I put the updated a_mig-2-8.jar? Also, do I need to rename it and does it replace a particular file? I've gotten conflicting responses from SGHE.

0
No votes yet
‹ Desire2Learn (D2L) Web Service Setup CAS SSO for INB, Self_Serv and Luminis ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Thu, 2008-09-04 16:25 — jhord

re: updated migrator jar file

From what I was able to gather by reading through various entries on the support site, it should go in $CP_WEBINF/lib. No renaming is needed and it doesn't replace an existing file. Just copy it to that directory and you should be good to go.

Wed, 2008-10-01 19:32 — Pederson

Setting the CLASSPATH - for the Migrator script

Like many of you, we have been having problems getting the migrator script to complete. We have updated the migrator script and jar file, etc from the FACS 1-3AU6BM.

The migration now gets as far as:
## executing operation: transform the pds ldif file
INFO: Transforming the pds LDIF...
INFO: A PdsId mapping file has been found
INFO: transforming LDIFException in thread "main" java.lang.NoClassDefFoundError: org/apache/pluto/om/common/PreferenceSet
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)

Our TSM came back with 'make sure you are running as the Luminis admin user, your CLASSPATH is not set. ' We are running as Luminis Admin. But our .cprc does not set the CLASSPATH. Can anyone give us a clue as to what the CLASSPATH should look like.

Denise Pederson
Systems Administrator
University of Saskatchewan

Thu, 2008-10-02 14:51 — Pederson

Setting the CLASSPATH - fo the Migrator script

It turns out that the CLASSPATH had nothing to do with it. The fact is that the migrator code has the tomcat-cp directory hardcoded, so if you have set the server.instance.id parameter in your install to something other than cp (ie. we use usask). The migrator files to find the PLUTO_JAR points to ${CP_ROOT}"/products/tomcat/tomcat-cp/shared/lib/pluto-1.0.1-rc2.jar.

We created a symbolic link for tomcat-cp to tomcat-usask, the migrator is now transforming the pds ldif file.

Denise Pederson
Systems Administrator
University of Saskatchewan

Wed, 2008-10-08 18:55 — Jason

migrator code

When we did the migration about a year ago, I learned that searching the migrator script often is a quick way to find why it is not working. Look for those "INFO: A.." lines and you can often see what happens next that causes it to halt.

We used one from many versions ago, but I recall having to change many of the hard coded paths.

The only thing that you can't easily track down are database errors, as those are in the .class files found in a_migxxx.jar