Migrating Design Time Libraries (DTL) as Shared Modules
ActiveMatrix BusinessWorks 5.x design time library source projects are migrated as TIBCO Cloud Integration shared modules.
Migrating Design Time Libraries Using TIBCO Business Studio for BusinessWorks
Use the TIBCO Cloud Integration framework to migrate ActiveMatrix BusinessWorks 5.x projects where the business process uses design time libraries to define processes, resources, and subprocesses.
- TIBCO Business Studio for BusinessWorks option in
- Procedure
- In the Project Migration Wizard dialog box, click Migrate Single BusinessWorks 5.x Project and select the Migrate as Shared Module check box.
- Provide the Project Location details and the XPATH Function Group Configuration details if a custom XPath is used in the project.
- To browse for third party jars only if your project contains a custom XPath, click the Select Third Party JARs folder field .
- Click Migrate Project.
After migration, do not perform refactoring operations on any of the resources, such as the schema, TIBCO Cloud Integration shared resources, and service definitions. The resource properties, and naming conventions must be retained as they are. Mapping issues, if any, can be corrected, and resource specific properties of the shared resources can be changed.
Limitations
- Shared module migration does not support ActiveMatrix BusinessWorks 5.x AE schemas. AE Schemas are migrated as part of the application module.
- Custom XPath function project duplication should be managed manually by deleting the duplicate source projects.
- DTL migration does not support the Process Name Dynamic Override feature of the Call Process activity. Instead, add the process name manually.
Migrating Application Modules
ActiveMatrix BusinessWorks 5.x projects using design time libraries can be migrated as application modules by linking the corresponding shared modules to the DTL libraries.
Select the Link DTL to Shared Module check box.
Select the required DTL project, and click OK.
Mapping the DTL to the <Do Not Migrate> option does not link the DTL to the shared module.