Server (Magic xpi 4.13)

The Magic xpi Server is the engine that runs your integration project during deployment. Magic xpi Servers use the information contained in the ibp file that you generated in the Magic xpi Studio to run the project. Magic xpi Servers contain various systems that manage the different aspects of flow execution. Magic xpi Server deployment is governed by the start.xml file, which is located under the project’s folder.

Magic xpi Servers contain a set of systems that provide a range of flow-management services, such as messaging. The Servers also provide logging and monitoring functionality that help you carry out performance modifications and enhancements.

• The Flow Manager is the main Server module that manages flow invocation and ongoing flow execution.

• The Publish and Subscribe (PSS), Operational Data Storage (ODS), Locking, and Messaging (MSG) systems are used for data management and storage in the project. The PSS and the Locking system are handled in the Space, while the Messaging system and the ODS are handled in the database.

• The Recovery system is used for recovery operations.

• The Scheduler system manages the timing of flow execution.

You make server-related configurations in the Magic xpi Studio during the project-development stage. There is a flag called StepRetryLimit= in the ifs.ini file. This flag determines the number of times that the Magic xpi Server will retry to execute a step in which the error behavior is set to Retry. If you are using multiple Magic xpi Servers, make sure that the machines' clocks are all synchronized.

Management Thread

Each Magic xpi server runs a dedicated management thread when you start the server. The management thread is responsible for consuming and handling the following management messages:

• Timeouts.

• Wait for completion steps.

• Flow completion notification to the activity thread.

• Recovery.

The management thread is not active when all of the following conditions are met:

• The Recovery policy for all flows in the current project is set to None.

• There is no timeout defined for all flows in the current project.

• No flows in the project have steps that are set to Wait for Completion.

• Flow start/completion is not logged in the Activity Log.

If the first three conditions are met, and the activity log is not loaded, the management thread will not be loaded. If the first three conditions are met and flow start/completion is not logged in the Activity Log, the management thread is loaded, but it does not receive any messages.

Activity thread

Activity threads write messages to the activity log.

Related Topics

Starting and Stopping a Project

Server Initialization

Activity Log

Errors

How Do I Control the Magic xpi Server Messages?

How Do I Monitor Running Threads in Magic xpi Projects?

Server Performance Considerations – Technical Note