Migrating Decision Server Rules
Decision Server includes your development environment and your runtime environment.
- Migration scenarios
Before migrating, you must assess the impact of the new version of Operational Decision Manager on your applications. Migrating to a new version of Operational Decision Manager can require you to upgrade your databases, application servers, or both. - Migrating customizations
If you customized your development environment in any way in a previous version, you must reapply your customizations to the new version. Examples of customization include changes to rule model extensions, extension mechanisms for permissions, lifecycle management, and any modification to the editors. - Migrating classic rule projects to decision services
Make sure that your classic rule projects meet the prerequisites and use the migration wizard to migrate them to decision services in Rule Designer. You can also use Ant tasks to migrate your projects. - Migrating from classic rule engine to decision engine
The classic rule engine is deprecated, so you must migrate your rule projects to use the decision engine. New rule projects in a decision service automatically use the decision engine. - Migrating the development environment
After you have migrated your customizations to the new version of Operational Decision Manager, you can migrate your Eclipse projects. - Migrating the runtime environment
The runtime environment is your application running in production, in contrast to other phases of the application lifecycle.
Parent topic: Upgrading and migrating