Migrating Projects with Adapter Subscriber Activity and Publication Service

You can migrate projects that use the Adapter Subscriber from the ActiveEnterprise Adapter palette and Publication service of ActiveMatrix Database Adapter for Database to the Data Event Poller Activity in ActiveMatrix BusinessWorks Plug-in for Database in the following manner:

Procedure

  1. Start TIBCO Business Studio.
  2. On the menu bar, click Project > Migrate BW Projects.
  3. In the Project Migration Wizard, the default selection is Migrate Single BusinessWorks 5.x Project in the Migration Project Type section. Click Migrate Multiple BusinessWorks 5.x Projects to migrate multiple 5.x projects.
  4. In the Select Project Location section, click Browse to add the project location to the Select Project(s) to be Migrated field and select the project you want to migrate.
  5. Select the migrated project location by clicking Browse next to the Select Migrated Project Location field.
  6. Click Migrate Project.
  7. After the migration is completed, click Finish.
    Name of the migrated shared resource is the name of the ActiveDatabase Adapter Configuration and the extension of the shared resource. For example, ActiveDatabaseConfiguration.adbResource.

    All the configurations of the Publication service are migrated to the respective fields of DBPoller on the Schema tab of the ADB Configuration resource.

    All the fields of the Adapter Subscriber activity and Publication service are migrated to the General > Advanced tab of the Data Event Poller activity.

    On the General tab of the migrated Data Event Poller activity, the migrated shared resource is mapped to the Configuration Resource field. The schema selected in the Publication service is mapped to the schema picker of the migrated Data Event Poller activity.

    Note: In the migrated activity, the fields that are not present in the Publication service but are present in the Data Event Poller activity have default values. These fields can be configured by using the JSON preference file. For more information about the JSON preference file, see Working with Preference File (JSON) for Migration.