• Installation Instructions
  • Installation Instructions - (tutorial)

  • See Getting Started Tutorial>

  • Soup up NT/IIS

    • < Test update by installing in parallel first. >




    Nature of a parallel system:
    As of tame 3.864, a parallel release can be installed and tested without disturbing the running shopping system. Working with the parallel release is easy, you simply place the tame binary in the cgi-bin under the name tamex or tamex.exe. Tame detects this alternate binary name and runs on a parallel system.

    A parallel system shares the web documents and mirror trees with the active system. The parallel release has it's own set of configuration files and a separate global tree.


    Parallel system differences:

    Active Parallel
     tameroot/global
    mirror/domain.tag
    mirror/shop/config.tag
    mirror/shop/custom.tag
    mirror/shop/payments.tag

    Parallel
    tameroot/global tameroot/global.x
    mirror/domain.tag mirror/domain.tag.x
    mirror/shop/config.tag mirror/shop/config.tag.x
    mirror/shop/custom.tag mirror/shop/custom.tag.x
    mirror/shop/payments.tag mirror/shop/payments.tag.


    Installing the system:
    There is only one tricky part to installing a parallel release. If you unzip the new release normally, you will be unzipping it to your active global directory. Please don't do this!

    To get the new release into the global.x directory instead of the active global directory, unzip as follows:

    1) Rename your global directory as global.sav
    2) Unzip the new release.
    3) Rename the unzipped global directory as global.x
    4) Rename your global.sav directory as global.
    Now copy the tame or tame.exe binary to your cgi-bin under the name tamex or tamex.exe. Be careful not to copy over the active binary!

    Run the browser install wizard accessing the tamex or tamex.exe binary.


    Particulars to using a parallel system:
    A parallel system has it's own configuration files so you can use shopping system admin to change configurations without affecting the live system.

    A parallel system shares web pages. If you make changes to web pages, you will be affecting both systems.

    Sometimes it is necessary to change or fix panels while testing the parallel system. To do this you will need to create a copy of your global.x/panels directory, I suggest calling it global.x/panels.x.

    Once you have a copy of the panels, go to your mall admin pages (on the parallel system) and set up the following.

    1) Change the panels directory to point to your
        new panels directory.
    2) Turn "off" the setting for using shop panel
        overrides. This will prevent the live panels in the
        shop from being used. Only the panels in your new
         panels directory will be used.
    3) Apply the admin changes with the "apply" button.
    4) Modify the panels in your new directory as needed.


    Switching new system over to active system:
    Once you have determined that the parallel system is functioning correctly, you do the reinstall again for the live system and merge any panel changes.

    1) Unzip the new system to the active global tree.
    2) Copy the new tame binary to the active binary in
         the cgi-bin.
    3) Run the browser install wizard on the new tame
        binary.
    4) Make any admin configuration changes you needed
        again. The changes you made to the parallel
        system will not be transferred to the new active
        system.
    5) If you modified panels, either copy the modified
        panels from the modified panels directory to the
        respective shop directories. OR Copy the entire
        modified panels directory to the new global tree
        and set up the system to use this panels
        directory instead of the default.