com.ptc.windchill.upgrade.directives
Interface JavaMigrator

All Known Implementing Classes:

AccessControlObjectMigrator, AclEntrySetMigrator, BulkItemsMigratorX05, ContentHandlingR8, CreateParameterMapMigratorX05, CreateUpdateCounterMigratorX05, DropGeneratedStoredProcsMigrator, ECADMigratorR7, I3MigratorR7, LCAdHocAclUpdateTool, LoadDefaultOrgContainer, LoadExchangeContainer, LoadWindchillPDMContainer, MigrateControlBranches, MigrateDiscussionPosting_R6ToR62, MigrateDomainAccess, MigrateGroupDomainsR6ToR7, MigrateHistoricalIterations, MigratePersonalCabinetData, MigrateProjectToTeamObject, MigrateReportTemplates, MigrateUserCabFolderToXchgContainer, OrganizationReferenceMigrator, PJL_PDML_SystemCabinetMigrator, PJL_PDML_WTContainedMigrator, PolicyRuleMigrator, QueueEntryMigrator, RequiredBlobMigrator, UpgradeUFIDsR6toR7, WTContainedMigrator, WtxToWtMigrator

public interface JavaMigrator

Migration of data in a new schema can occur in two ways. One is via SQL scripts the other is programatically. This interface can be implemented by programmatic migration applications and then be run in a controlled manner by the Update Tool.

Once you develop a Migrator consult the ADG or Development Library Cookbook for information on authoring incremental updates for the Update Tool.

Note about exceptions

The interface declares that it throws Throwable. This allows migrators to conveniently not handle unexpected errors and let the MigratorRunner do so. If, for some reason, you decide to catch them inside the migrator, it will be helpful for diagnosis, to write them to the log using the syntax:

    ...
    catch(SomeException ex)
    {
       ex.printStackTrace(log_writer);
    }
 

Example - Using the POM

When using the POM you may need to use an access controller (e.g. for queries). The code below shows how to create an AccessControllerAdapter if the need arises.

    public boolean runMigration(DirectiveServices directive_services)
       throws wt.pom.PersistenceException,
          wt.query.QueryException,
          wt.util.WTPropertyVetoException
    {
       // To use the POM you will need to instantiate an AccessController.
       // This one does no checks.
       wt.pds.AccessControllerAdapter aca = new wt.pds.AccessControllerAdapter();
  
       // perform the work (e.g. query some objects and change them)
       wt.query.QuerySpec qs = new wt.query.QuerySpec(...);
       PersistentObjectManager pom = directive_services.getPOM();
       QueryResult result = pom.query(qs, aca); // notice the required use of aca
       while(result.hasMoreElements())
       {
          ... // do the migration work
       }
  
       // return success
       return true;
    }
 

See Also:

MigratorRunner

Method Summary

boolean

runMigration(DirectiveServices directive_services) Run the migration.

Method Detail

runMigration

public boolean runMigration(DirectiveServices directive_services)
                     throws Throwable

Run the migration.

Migrators should log all output to the given PrintWriter. This is the log that is created by RunMigrators. It is an autoflush writer.

Migrators should return true if they successfully completed migration and false otherwise. It is the migrator's responsibility to log failure reasons to the log.

Migrators should not concern themselves with committing the work on the connection. The MigratorRunner will commit the connection work after running each Migrator.

Parameters:

directive_services - provide access to database, logging, and versioning information

Throws:

Throwable - declared so that migrators can let exceptions contibuting to failure pass out of the method. The migrator runner will handle these by logging them.