Salesforce

Preparing the Project for Deployment (Magic xpi 4.5)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Preparing the Project for Deployment (Magic xpi 4.5)

Magic xpi project development is carried out in the Magic xpi Studio. You build your project with the Magic xpi Studio, which runs on Windows. Magic xpi Integration Platform includes the Studio, the Magic xpi Monitor, and a development server. This allows you to build your project and test it in a controlled environment. Because the testing and development environments both run on the Windows operating system, there should be very few problems with running the flows in a project. However, if you plan to deploy your project on a Unix, Linux, or IBM i server, you should consider the differences in the operating systems when you develop your project.

To be sure that your project will run when you deploy it on the server you must consider the following issues:

  • Use only lowercase letters when you assign names to files and components. Names of files and components in the Windows operating system are not case sensitive. However, other operating systems, such as Unix or IBM i, are case sensitive. To ensure that the names are recognized across platforms, you should be consistent in naming your files and components. Therefore you should use only lowercase letters.

  • Use environment variables when you provide names or addresses to servers, messaging queues, and aliases. An environment variable is a Magic xpi naming convention that is written with two percent (%) signs. For example, %server1%. You can assign this environment variable to a server regardless of the actual name of the server. You assign a value to this environment variable (in this case the actual name of the server) in the Magic.ini configuration file. See Deploying Magic xpi Projects for more information on using the Magic.ini file in deploying your project.

  • Assign environment variables to context, global, or flow variables in a project. This lets you use variables when you assign an environment variable to configure components or services in Magic xpi. If you use variables, you do not have to check each component’s configuration at deployment time to update the Magic.ini configuration file. You can see the list of environment variables used in the Variable Repositories.

  • You should use the same database type for the Magic xpi internal and application databases that you are going to use in deployment environments. This means that if your development internal database was Microsoft SQL Server, you should use the same server type in deployment.

Note:

  • It is recommended that you disable or clear all debugging code from the project before deploying. For example, disable or clear the flows, messages, and programs used for debugging purposes.

  • You should not use mapped network drives during project development, because the recipient of the project is unlikely to have the same mapped network drives available at the point of deployment.

When your project is ready for deployment:

  • Create an executable file (ibp) by opening the project’s Build menu and selecting the Rebuild Solution option.

Reference
Attachment 
Attachment