Deploying a Java XOM from a rule project

You can deploy a Java™ XOM that is associated with a rule project in Rule Designer to a Rule Execution Server instance through a Rule Execution Server configuration.

About this task

The deployed Java XOM is then stored to the Rule Execution Server persistence layer and is a manageable artifact in the same way as a RuleApp.

By deploying a Java XOM from a rule project, you can deploy the XOM alone. This mode is useful if you deploy RuleApps and rulesets later from Decision Center. You can then reference rulesets as managed URIs in the Rule Execution Server console by associating a ruleset with a managed URI manually.

Note:

The XOM is always deployed as a major version. To set deployment parameters, use Ant tasks. For more information, see Ant tasks for Java XOM management.

Procedure

To deploy a Java XOM to Rule Execution Server:

In the Rule Explorer, right-click the rule project name, and then select Rule Execution Server > Deploy XOM from the contextual menu.
From the Deploy XOM dialog, select an existing Rule Execution Server configuration or create a temporary one.

Results

After a first deployment to a Rule Execution Server instance, the URL, the user name, and the password are saved in an encrypted form to the workspace cache, so that the deployment wizard can keep track of the resources. The resulting resource list is stored to a file named deployment.xml. The deployment.xml file is taken into account during the synchronization process and enables further deployment to the specified Decision Server from Decision Center.