Salesforce

Deploying Magic xpi Projects (Magic xpi 3.x)

Printable View
« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Deploying Magic xpi Projects (Magic xpi 3.x)

When you are ready to deploy your projects, prepare the Server environment. To prepare the Server, you must:

  1. Copy the project to the production environment: There are two options for doing this, as shown below:

  1. Option 1: This is usually used for copying the project into the production environment for the first time:

    • Copy the project folder and all its content from the development environment to the production environment. It is important to keep the same project structure, or the project will not run correctly when deployed.

    • Modify the following project elements to fit the production environment settings (for example, license name, paths, and logical names):

      • The ifs.ini file

      • The shortcuts' reference

    • If necessary, modify the Magic.ini file in the production environment to fit the Magic.ini file in the development environment (for example, license name, paths, and logical names, such as currentproject and DB_SERVER_NAME).

  2. Option 2: This is usually used when the project already exists in the production environment, and you want to update it with changes that you made to the project while it was in the development environment:

    • Copy the following project elements from the development environment's project folder into the production environment's project folder:

      • The project's ibp file

      • The service.xml and the resource.xml (if changes were made)

      • The ifs.ini file or part of its content (if changes were made)

    • If necessary, modify the Magic.ini file in the production environment to fit the Magic.ini file in the development environment (for example, license name, paths, and logical names).

Note:

  • It is recommended to turn off logging, since logging significantly slows down the execution of the program.

  • In all cases, parameters' names and values are case sensitive.

  • Because Unix, Linux, and IBM i operating systems are case sensitive, you should be careful when naming files or other components in your project. Otherwise, the project will not run correctly. If you only use lowercase letters when you name your files and other components, you can copy the contents of the projects folder directly into the Projects directory of the server without making any changes.

  • If you created a custom component in your development environment, you need to copy the resource_types.xml file from the development environment's Magic xpi root folder to the deployment environment. The resource_types.xml file supplied with the Magic xpi installation only includes Magic xpi's native components.

  • You can use the Project Packager to bundle all relevant Magic xpi project files, and any other files used by the project, into a single zip file.

  1. Copy other files into the project directory: You should copy any other files that you created for use in your project. Make sure that they have the same name that you gave them and that they are in the same directory and or subdirectory as in the development environment.

Note:

To enable the broker to recover any projects that may fail, all projects must have an entry in the Mgrb.ini file, even if you do not want the broker to start the Servers. Without these entries, the broker recovery mechanism cannot recover the projects.
You can find the relevant entries under each project's Reload_MGRB.txt file. These should then be added to the Mgrb.ini file.
If you do not want the broker to start the Server automatically at startup, you should replace the entry's last value with 0.
For example:
IFSMyProj=MgxpiServer.exe @projects\MyProj\ifs.ini ,,,,1
Should be changed to:
IFSMyProj=MgxpiServer.exe @projects\MyProj\ifs.ini ,,,,0

  1. Map external resources: Map all external resources, such as Java libraries or databases to the Magic xpi server in exactly the same way they are mapped to the development environment. For example, if you use a Java library called Java A on Computer A in the development environment, you must map the Magic xpi Server to Java A on Computer A. You must be sure to map to the same library or an exact copy in the same location. This is also true for databases or any other resources that reside on remote computers.

For information about deployment on a clustered environment, click here.

Reference
Attachment 
Attachment