Deployment Item
Figure 1: Deployment Items in Xyna Factory Manager
Figure 3: ''Deployment State'' subpanel (inside [[Detail View or Deployment Items section)]]
A Deployment Item is an object, living in the Xyna Factory, that can be deployed. A list of all Deployment Items can be watched and managed via the ''Deployment Items'' section in Xyna Factory Manager (cf. fig. 1) or via CLI.
The listing of Deployment Items can be very useful if it comes to the deployment of a single Workflow or even the building of a new Application. It supports filtering for items with problematic Deployment State to speed up the overall deployment readiness. A detailed description of the concrete problem and a proper solution is supplied by the Deployment State subpanel inside the Detail View of the Xyna Process Modeller or the detail area inside the Deployment Items section (cf. fig. 3).
| Icon | Name | Description |
|---|---|---|
|
Workflow | A composition of Process Steps |
|
Data Type | Declaration of properties and actions; this type of item may also contain Service Groups and Instance Services |
|
Exception Type | Declaration of properties and actions to classify errors |
|
Trigger | Protocol adapter as interface to receive requests |
|
Trigger Instance | Instance of a Trigger to enable/disable |
|
Filter | To be attached to a Trigger to define the behavior for specific kinds of requests |
|
Filter Instance | Instance of a Filter to enable/disable |
The following list provides the most common problems resulting in a problematic Deployment State:
- A Workflow has one or more issues, e.g. one of the following:
- Unconnected Input or Output Parameter of Process Steps
- Invalid Mapping assignments or any other invalid Formula Modeling term
- Still existing Prototype Services or Prototype Data Types
- A deployed item has inconsistencies and thus causes problems with other objects. These problems can be fixed by a deployment
- The signature of a Service has changed and the implementing Jar file has to be updated
- The deployed version of the implementing Jar file is older or newer than the currently saved version
- Missing saved or deployed version of the implementing Jar file
- ...