Checker Messages (Magic xpi 4.13)
The Checker checks the metadata structure of your project to find various incompatibilities. The Checker Results screen lists items where there is a potential problem. The errors are displayed with an indication of their severity on three levels:
|
|
|
|
Error
See: Error Messages
|
This, the most severe level, indicates a fatal error in the metadata. In this case, the project will not be able to work with the Magic xpi Server.
An example of a severe error is:
Mandatory field is empty: This indicates that mandatory configuration information is missing from some element in the project. The Results window displays where the error is located. You can double click the error to open the dialog box in the Studio that is missing the information and fix the error.
|
|
Warning
See: Warning Messages
|
This indicates an error that does not prevent the metadata from working on the Server. Results at deployment may not be what you expect to happen based on your project definitions.
An example of a warning-type error type is:
Transactional flow has a non-transactional step: This indicates that you placed a component in a flow that is not configured to support transactions although the flow properties are configures to support transactions. A transaction will not take place in this step even if that is what you expected. The Results window displays where the error is located. You can double click the error to open the flow in the Studio where the problem is, to fix it if you want. If you do not want a transaction to take place in that step, then you can do nothing or change the flow properties configuration.
|
|
Information
See: Information Messages
|
This indicates efficiency-type problems, such as insufficient Server capabilities for the relevant flows.
An example of an Information message is:
Peripheral server has too many flows: This indicates that you have a peripheral server that can handle a specified number of flows and you have defined more that the specified number of flows to run on that server. In this case the project can still run, but some or all of the flows assigned to that peripheral server will not run. The Results window displays where the peripheral server is located. You can then re-assign the various flows so that you do not have too many flows assigned to the Server.
|
