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.
As described in the first scenario, Operational Decision Manager can be used only by IT teams, who work exclusively with Rule Designer, typically with a source code control tool to centralize the artifacts.
However, as described in the third scenario, the goal is to have business users own the rules and manage them in Decision Center, where Rule Designer is only used to manage the rule flow and the BOM.
The second scenario is the intermediary step to transfer the rule ownership from IT to business users: the latter are gradually given access to see and modify the rules, with IT handling the rule changes less and less, in order to focus on the application architecture and other IT projects.
| Scenarios | |||
|---|---|---|---|
| Migration steps |
Rules are authored in Rule Designer and Decision Center is not used |
Rules are authored in Rule Designer and synchronized to Decision Center regularly |
Rules are authored in Decision Center and Rule Designer is only used to manage the BOM and ruleflow |
| Before you begin - Preparing your migration |
 |
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
|
|
|