Migrate Apama, Application Platform, Business Process, and Business Rule Projects
1. If you are migrating Apama, copy any files you modified from the old work directory to the new work directory.
2. If your projects are stored in a source control system, use the import wizard for that system (for example, Import SVN > Project from SVN).
If your projects are stored in the Software AG Designer workspace, do the following:
a. Go to the File > Import wizard.
b. In the Select panel, go to General > Existing Projects into Workspace and click Next.
c. In the Import Projects panel, do the following:
a. Click Select Root Directory and go to the workspace that contains a type of project you want to import, or click Select Archive File and go to the directory that contains a type of project you want to import.
b. In the Projects box, select the projects to import. Select Copy projects into workspace. Click Finish.
3. If you are migrating Apama, use Project > Clean to force a rebuild of generated project artifacts under the control of Software AG Designer.
4. Verify the projects.
The table below explains how to verify the projects for the listed products.
Product | Verify |
Apama | All projects build without errors. If errors appear in the Problems tab, click each error and resolve it. |
Application Platform | All projects compile without errors. If errors appear in the Problems tab, click each error and resolve it. For example, if you see errors indicating that classes cannot be resolved to a type, edit the project’s class path configuration. |
Business Process | All imported business process projects appear in the Solutions tab under the Processes node. |
Business Rules | All imported business rules projects appear in the Solutions tab under the Rules node. |
5. If you imported Business Rule projects, right-click each project in the Rules Explorer and then click Upgrade Project.
6. If you are migrating Apama:
a. Re-run any build or deployment scripts to make sure generated artifacts such as Apama queries, plug-ins, and scenarios from your projects are up to date. This task could include re-exporting and re-running Ant scripts, executing engine_deploy, rebuilding Docker images, and re-running custom scripts. Review the output for errors and warnings.
b. If you use Apama dashboard deployments, create new deployment packages and install the deployment packages.
c. If any project imports event types from Digital Event Services, you might need to re-import those event types. Open the project, open the EventTypeList file under config/connectivity/DigitalEventServices, and click Sync from Digital Event Services. If you see changes, save the file.
d. If any project includes a custom configuration for Digital Event Services, you will see a /DigitalEventServices directory. Erase the custom configuration and re-create it from scratch using Digital Event Services tooling or Command Central.