Deploying an OEM Application Update

Once updates for an OEM application are complete, the application changes must then be deployed. There are two ways in which the update can be deployed, as described below.

Replacing the entire MicroStrategy project in the existing system

Once updates for an OEM application are complete, the project can be replaced in an OEM application. This is commonly done by duplicating the updated OEM project, and then merging that project into the production OEM application.

These tasks can be achieved using the MicroStrategy Project Duplication Wizard and Project Merge Wizard. Both of these tools can perform their tasks from the command line, which can allow the project duplication and replacement process to be automated. The steps to use these tools to duplicate and replace a project are provided in the System Administration Help.

Merging modified objects into a project in an OEM application

Once updates for an OEM application are complete, the updates to the project can be deployed through the use of update packages. An update package is a file containing a set of object definitions and conflict resolution rules. When you create an update package, you first add objects, and then specify how any conflicts involving the objects are resolved.

These update packages can be developed using Object Manager. Once the package is ready for deployment, it can be deployed using the graphical interface with Object Manager or using the unattended execution with Command Manager Runtime. For information on creating and deploying an update package with Object Manager, refer to the information on managing projects provided in the System Administration Help. For information on Command Manager Runtime, refer to the System Administration Guide.