Using the Project Packager (Magic xpi 4.1)
To package a Magic xpi project for deployment:
-
From the File menu, select Close to close your current Magic xpi project.
-
From the File menu, select Project Packager to open the Project Packages Maintenance dialog box. In this dialog box, you can use the buttons on the bottom of the screen to define a New package, Delete an existing package, or Edit an existing package (pairs of zip and XML files) located in the \packages directory. You can also Extract the package and overwrite an existing project and all packed files in the \projects folder.
-
Click New to display the Package Definition dialog box's General tab, in which you define the following fields:
|
|
Project Name
|
Select an existing project name.
|
Package Name
|
The name generated for the package. This is the name of the project with the text _package added to it. If you rename the package, new files will be created with the new name; the existing package will not be overwritten.
|
Package Description
|
Enter text describing the package.
|
Last Modified
|
A read-only date and time field.
|
Modified By
|
Enter text identifying the last user who performed modifications to the project.
|
-
Click the Configuration tab to customize what is to be included and where the relevant files reside.
|
|
Project Resources File
|
Edit the displayed Resource file name and directory path.
|
Project Services File
|
Edit the displayed Services file name and directory path.
|
Project Env. Variables
|
Edit the package's Environment Variables Repository. The package's environment variables are the deployment definition only and are saved in the ifs.ini file.
|
Included Folders
|
Navigate through the displayed folders to specify which directories are to be included in the package. By default the tree includes the specified project directory and the \User Resources\Components directory. When an existing package is opened, the source directory is not included. Click Add to open a folder dialog box to select additional folders. Selected folders will be added to the package and to the existing display. Click Delete to remove the selected directory from the package and from the list.
|
Excluded Folders & Files
|
The Package Content pane on the left displays the directories and files that are part of the package. Select the directories and files that you want to move to the Excluded Files pane on the right.
You can also remove directories or files from the excluded list. By default, the sources are excluded for new projects; if this is left this way, the next time the package is edited, then they will not be part of the package and will not appear at all. You can always add this folder to an existing package.
|
-
Click Pack to execute the packaging utility and pack all files defined as included, using the zip utility.
-
Click Extract to extract the package and overwrite the existing project and all packed files. The extract will overwrite the information in the Magic xpi installation folder and its subfolders. The Package project, for example, will be extracted under the Projects folder of the installation. The same is true for the User Resources and other folders of the package.
Note:
|
If the extracted package project does not exist in the Magic xpi installation under the projects folder, the package can still contain files that are outside of the project folder, such as User components. So, for example, if a User component exists in the package and the same User component exists in the Magic xpi installation, the extracting of the package will overwrite the installed User component.
A message is not issued during the Extract process that this file will be overwritten.
There is a general confirmation dialog box, but not a specific one for each file in the package. If you are not sure about the content of the package, then it is recommended that you first edit the package and make sure that you know which folders and files will be overwritten. You can then modify the package and save it by another name and only then extract it.
|
|
To deploy the packaged project on the target server: