Developing a Magic xpi Project (Magic xpi 4.5)
This topic discusses the main considerations when developing a new project, and gives you the best practices to complete your task efficiently and successfully.
Data is the bits and bytes of any project. When data is received, it has to be handled. Data is:
-
Transferred to a secondary destination, such as another application or a messaging queue.
-
Converted to another format.
-
Saved in one or more tables and DBMSs.
-
Used as conditions for other activities.
Magic xpi provides various methods of managing data, such as:
The Data Mapper is a very powerful tool, but has an overhead of time and memory. Consider using the Data Mapper only when you need mapping capabilities. For instance:
-
Use the Flow Data instead of the Data Mapper to update variables.
-
Use the Data Mapper’s Call flow option only when you need to process many records. Use the Invoke Flow if you need to process one record only.
-
When you need to store data temporarily, it is more efficient to use a flat file saved in a variable than to use the ODS. The ODS is a table stored in a database and thus consumes more memory than a flat file in memory. However, the ODS is persistent and can be recovered from failure.
When working with Magic xpi, there may be occasions when you need to add your own specific code to perform a necessary functionality that is not provided by Magic xpi Integration Platform. The Magic xpi Studio’s Connector Builder provides this capability.
As with any Magic xpi-provided component, the user-defined component exposes a number of user-defined methods, each with their own parameters, which may be used in a step or trigger in a flow.
These methods will be exposed in Method and XML interfaces.
User-defined components may be created using .NET or Java. Click here for more detailed information.
See also: How Do I Move a User-Defined Component to the Deployment Environment?
Magic xpi’s Recovery system lets you recover data lost due to a system crash or flow timeout. You can define the Recovery policy for each flow during project development. You define the Recovery policy in the Flow Properties dialog box.
The Checker runs automatically when creating a deployment package. At this stage, it loads all flows into memory in order to be able to run a full check on the project. The Checker does not run on inactive flows.
