MGI Installation Procedures

WebSTAR 3.x/4.x Configuration on Macintosh

  1. Quit WebSTAR if the application is running.
  2. Increase the memory allocation for the WebSTAR server. We recommend a total of 80 MB of RAM allocated to WebSTAR (increase memory by 5 MB minimum).
  3. Double-click the MGI VISE installer.
    • Click continue.
    • Read and accept the MGI License Agreement.
    • If multiple copies of WebSTAR are installed on your server, select the copy of WebSTAR where MGI should be installed.
    • Enter the owner name (User name), owner organization, and serial number/authorization code. Enter the serial number and authorization code without spaces. Your existing owner name, owner organization and serial number/authorization code are pre-filled from your MGI preferences. If the serial number/authorization code is left blank, MGI will install in demo mode. Demo mode displays a header and footer on each page that is processed and served by MGI.
    • Enter your Username and Password for the MGI Server Admin. Your existing username is pre-filled and your existing password, although not pre-filled, will be used if another password is not entered. If the password is left blank during an original installation, the password defaults to "MGI" (case-sensitive).
  4. Restart the WebSTAR application. Check the log window to make sure the MGI modules were initialized properly.
  5. Launch the WebSTAR Admin application and open the Server Settings.
  6. Under the "Suffix Mapping" option, configure the suffix mappings for any suffix that you want MGI to process and serve. You can have any suffix such as ".mgi", ".mgi2", ".html", or ".htm" processed by MGI. However, only one processor such as MGI can process any given suffix. In addition, you may have better server performance overall if MGI only processes pages that contain MGI tags rather than every page. The settings for an MGI-enabled suffix should be as follows: Action (MGI2), Type (*), Creator (*), MIME Type (text/html). Note that the ".MGIMODULE" suffix is pre-configured. Click the "Save" button to save the suffix mappings.
  7. If you wish to use MGI to determine the default index pages for your server (i.e., to serve an index page when one is not specifically given in a URL request such as "http://www.domain.com/" actually serves "http://www.domain.com/index.mgi"), enter a page name with an MGI suffix as the Default index name under the "File Names" option. For example, if the ".mgi" suffix is mapped to MGI2, then you might enter "index.mgi" as your default index page in the Server Settings. Click the "Save" button to save the settings.
  8. We do not recommend that you run caches on a production server. We recommend that you turn all cache settings off in the WebSTAR Admin. Click the "Save" button to save the settings
  9. Quit the WebSTAR Admin.
  10. Set up web site accounts as usual. That is, put a web site folder or alias to a web site folder in the WebSTAR root folder, configure virtual hosts for domain accounts using an application such as WebSTAR Virtual Host or Welcome, and configure related services such as FTP and secure services.
  11. If accounts are not set up in the MGI Server Admin, then any domain using MGI functions will do so under the Default Domain. The consequences of multiple accounts using MGI functions under the Default Domain is shared database access, shared module access, etc. To avoid shared access, set up each web site in the MGI Server Admin. We also recommend that you disable modules under the Default Domain if you are running a shared server environment (e.g., hosting services, etc.). Read additional instructions for setting up domains and regions in the MGI Server Admin.

IIS 4.0/5.0 Configuration on NT

  1. Double-click the MGI VISE installer.
    • Click continue.
    • Read and accept the MGI License Agreement.
    • Enter the owner name (User name), owner organization, and serial number/authorization code. Enter the serial number and authorization code without spaces. Your existing owner name, owner organization and serial number/authorization code are pre-filled from your MGI preferences. If the serial number/authorization code is left blank, MGI will install in demo mode. Demo mode displays a header and footer on each page that is processed and served by MGI.
    • Enter your Username and Password for the MGI Server Admin. Your existing username is pre-filled and your existing password, although not pre-filled, will be used if another password is not entered. If the password is left blank during an original installation, the password defaults to "MGI" (case-sensitive).
  2. Open the Internet Services Manager. The following steps may be made to the Master Properties which apply to the entire server or may be made to the properties of selected web sites.
    • Open the Master Properties or the Properties of a selected web site.
    • Click the "Home Directory" tab (where the virtual root directory is configured). Click the "Configuration..." button. This is where you configure the extension mappings for MGI. First, add the required extension mapping for ".mgimodule". To add an extension mapping, click the "Add" button. In the "Executable" field, enter or browse the path to the file "mgi2.dll". Note: The path CANNOT have spaces in it. In the "Extension" field, enter the suffix that is mapped to MGI, ".mgimodule" in this case. Leave all other settings as they default and click the "OK" button to add the extension. Add additional extension mappings for any extension you want MGI to process and serve. You can have any extension such as ".mgi", ".mgi2", ".html", or ".htm" processed by MGI. However, only one processor such as MGI can process any given extension. In addition, you may have better server performance overall if MGI only processes pages that contain MGI tags rather than every page. Click "OK" to save the extension mappings.
    • Click the "Documents" tab. Check the "Enable Default Document" checkbox to list default index pages that will server for all web sites or the selected web site. To add a default page name, click the "Add" button, enter the default index page (e.g., "index.mgi") and click the "OK" button. Default pages are served and listed in the order entered. To rearrange the order of default index pages, select a default index page and use the up and down arrow buttons.
    • Click the "Directory Security" tab. Click the "Edit..." button in the "Anonymous access and authentication control" section. Leave "Anonymous access" checked, but uncheck all others (basic, NTLM, digest authentication, and especially Integrated Windows authentication). This is required for MGI to be able to authenticate the MGI Server Admin, the MGI Domain Admin and any page with MGI authentication tags. IIS will intercept the authentication before MGI gets a chance to process it if any of these options are enabled. Click "OK" to save the authentication settings.
    • Although virtual hosts are used by MGI to detect which domain settings to use, you must still configure virtual hosts in the Internet Services Manager for each web site. As usual, virtual hosts are configured by clicking the "Web Site" tab. On the "Web Site" tab, click the "Advanced..." button to view the virtual host list. To add a virtual host, click the "Add..." button, enter the TCP Port as "80" and enter the virtual host name (e.g., "www.domain.com") in the "Host Header Name" field. Click the "OK" button to save the virtual host. Click "OK" again to save the Advanced Web Site settings.
    • To save all changes in the Master Properties or selected domain properties, click the "Apply" button and close the window or click the "OK" button.
  3. If accounts are not set up in the MGI Server Admin, then any domain using MGI functions will do so under the Default Domain. The consequences of multiple accounts using MGI functions under the Default Domain is shared database access, shared module access, etc. To avoid shared access, set up each web site in the MGI Server Admin. We also recommend that you disable modules under the Default Domain if you are running a shared server environment (e.g., hosting services, etc.). Read additional instructions for setting up domains and regions in the MGI Server Admin.

Installing Module Updates

During the course of MGI development, PagePlanet Software releases updates to modules which contain bug fixes and new features. You can download module updates from the PagePlanet Software web site or via the Version Tracker feature of the MGI Server Admin. Use these instructions to install a new module.

  1. Download the module from the PagePlanet Software web site or via Version Tracker.
  2. Transfer the module to the server and uncompress the module file.
  3. Access the MGI Server Admin.
  4. Under Module Management, unload the module you are replacing.
  5. Copy the new module into the MGI File/Modules/ folder.
  6. Under Module Management in the MGI Server Admin, reload the module. The new module will be active on your server as soon as it is reloaded.

[System Requirements] [Installation] [Domain Configuration] [Server Admin] [Domain Admin] [Licensing]

[MGI Guides Main Menu] [Admin Guide Main Menu]