The article outlines the process of migrating TIBCO Business Works (BW) applications from the 5.x version to the cloud-native TIBCO Business Works Container Editions (BWCE) 2.x version. It emphasizes the need for comprehensive application analysis to assess dependencies, shared modules, and unsupported components prior to migration. Critical requirements include schema validation, removal of naming conflicts, and necessary refactoring of local files and configurations. Steps for actual migration such as utilizing the TIBCO Business Studio for BW are also detailed to guide users through the process effectively.
"The initial phase is to evaluate the existing BW applications, assessing dependencies like shared modules, libraries, adapters, and unsupported components to ensure compatibility with the cloud."
"To avoid conflicts during the migration, ensure that schemas, WSDLS, or DTDs do not have the same name nor any special characters, and convert all BW Projlib's into shared Modules."
Collection
[
|
...
]