-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment
The Deployment of an XMOM Object means, that it is prepared for execution within the Xyna Factory. Given that the Xyna Factory is running on a Java platform the deployment of XMOM Objects leads to the compilation of Java-executable items.
In contrast to saved objects, deployed objects are executable. This distinction is especially relevant for Workflows: Workflows are the only objects which may be saved without a Deployment. All other objects (Data Types, Exception Types, Coded Services and Service Groups) will always be saved and deployed at the same time. The reason behind this is, that all other objects are always in a deployable state while Workflows may, for instance, contain Prototype Services and Prototype Data Types to enable Rapid Prototyping.
Please note: There are other objects than Workflows, that can be saved without being deployed. This occurs, e.g. when an object gets saved and deployed and causes an error during Deployment. In this case, you will be informed by a message.
If you edit an already deployed XMOM Object and only save your changes without deploying the object again, the last deployed state of the object will be used during execution. To cope with this kind of problems all deployable items are monitored inside the Deployment State overview of the Xyna Process Modeller or the Deployment Items section of the Xyna Factory Manager.