SiteBuilder 4.5 was EOLed by the vendor and no longer supported by Odin Automation. Before upgrading to Odin Automation Premium 7.0, SiteBuilder 4.5 must be removed or substituted with Web Presence Builder 12.

In order to prepare for the upgrade, one have an option just to detach all websites from SiteBuilder 4.5 and remove the corresponding resource from Service Templates and subscriptions, or to substitute SiteBuilder 4.5 with Web Presence Builder 12.

Case #1. Removing SiteBuilder 4.5

Overview

This scenario is suitable if the pre-check "Check subscriptions that used SiteBuilder for content management" does not report any subscriptions, or you decided to detach reported websites from SiteBuilder and do not substitute them with Web Presence Builder instead.

Removing

  1. Back up websites data on the SiteBuilder server. The main items that you need to back up are:

    • Linux: MySQL database called sitebuilder3, and contents of the directory /usr/local/sitebuilder/htdocs/sites or /opt/sitebuilder/htdocs/sites.
    • Windows: MS SQL Server database called sitebuilder, and contents of the directory C:\Program Files\Sitebuilder\Sites.

  2. Download scripts:

    • sb4_fix_oa.py to the Management Node.

      IMPORTANAT NOTE: If version of installed python is lower than 2.5 which does not support Conditional expressions, please use sb4_fix_oa.py from attachment.

    • sb4_fix_ba.pl to the Business Automation Application Node.

  3. Execute the script in the --dry-run mode. In this mode the script does not make any modifications. It only lists action that will be executed.

    1. Run the following command on the Management Node:

      python ./sb4_fix_oa.py --remove --dry-run

    2. If OA is integrated with BA, the script will ask you to execute the command in the dry-run mode on the Business Automation Application Node, like this:

      perl sb4_fix_ba.pl --remove --dry-run
    3. Check the output for possible errors and fix them.

  4. Execute script again to totally remove SiteBuilder:

    1. Run the following command on the Management Node:

      python ./sb4_fix_oa.py --remove

    2. If OA is integrated with BA, the script will ask you to execute the command on the Business Automation Application Node to remove SiteBuilder resources in BA:

      perl sb4_fix_ba.pl --remove
  5. Wait until the SiteBuilder unprovisioning tasks are processed (Operations > Tasks).
  6. Deactivate the SiteBuilder service branding on the brands (System > Settings > Brands > [Brand] > Service Branding > Plesk Sitebuilder 4.5 for ... > Deactivate Branding).
  7. Remove all SiteBuilder-related Resource Types from the system (Products > Resources > [Shared hosting users in Plesk Sitebuilder for Linux/Unix] > Delete).

Case #2. Switching SiteBuilder 4.5 to Web Presence Builder 12.

Overview

This scenario is suitable if the pre-check "Check subscriptions that used SiteBuilder for content management" lists subscriptions that actually use SiteBuilder for websites and you decided to substitute SiteBuilder 4.5 with Web Presence Builder 12.

The script is designed to automatically reconfigure service templates and subscriptions to disable content management through SiteBuilder and enable Web Presence Builder. Migration of a site content from SiteBuilder to Web Presence Builder is performed by end-customer with the "Import Site from SiteBuilder 4.5" feature of Web Presence Builder (see for details).

The script automates the following operations:

  • Web Presence Builder will be included in all service templates and subscriptions containing SiteBuilder.
  • SiteBuilder will be removed from all Service Templates/Service Plans. Content management of SiteBuilder will be unprovided from all subscriptions.
  • All unpublished changes will be lost. (To get a list of unpublished sites see KB129053)
  • SiteBuilder resources will be replaced by WPB in all places in BA (Service Templates, Service Plans, Subscriptions, etc.)

Switching

  1. Back up websites data on the SiteBuilder server. The main items that you need to back up are:

    • Linux: MySQL database called sitebuilder3, and contents of the directory /usr/local/sitebuilder/htdocs/sites or /opt/sitebuilder/htdocs/sites.
    • Windows: MS SQL Server database called sitebuilder, and contents of the directory C:\Program Files\Sitebuilder\Sites.

  2. Deploy new instance of WPB according to the instruction: pa-presence-builder-12.0-integration-providers-guide.pdf

  3. Create necessary WPB resource types. Write down ID of the created Web Presence Builder site application resource type (PCP > Products > Resources).

  4. Download scripts:

  5. Execute the script in the --dry-run mode. In this mode the script does not make any modifications. It only lists action that will be executed.

    1. Run the following command on the Management Node:

      python ./sb4_fix_oa.py --switch --wpb-rt-id=<wpb_rt_id> --dry-run

where:
    <wpb_rt_id> - ID of Web Presence Builder site application resource type

      For example:

      python ./sb4_fix_oa.py --switch --wpb-rt-id=1000256 --dry-run

      With the key --dry-run the script does not make any modifications.

    2. If OA is integrated with BA, the script will ask you to execute the command in the dry-run mode on the Business Automation Application Node, like this:

      perl sb4_fix_ba.pl --switch --wpb-rt-id=<wpb_rt_id> --dry-run
    3. Check the output for possible errors and fix them.

  6. Execute the script again to switch SiteBuilder to WPB:

    1. Run the following command on the Management Node:

      python ./sb4_fix_oa.py --switch --wpb-rt-id=<wpb_rt_id>

    2. If OA is integrated with BA, the script will ask you to execute the command on the Business Automation Application Node to switch the SiteBuilder resources to WPB in BA:

      perl sb4_fix_ba.pl --switch --wpb-rt-id=<wpb_rt_id>
  7. Wait until the SiteBuilder unprovisioning tasks are processed (Operations > Tasks).
  8. Deactivate SiteBuilder service branding on the brands (System > Settings > Brands > [Brand] > Service Branding > Plesk Sitebuilder 4.5 for ... > Deactivate Branding).
  9. Remove all SiteBuilder-related Resource Types from the system (Products > Resources > [Shared hosting users in Plesk Sitebuilder for Linux/Unix] > Delete).
  10. Create notification messages for customers to instruct them how to import existing sites from SiteBuilder to WPB. (Subscriptions that use SiteBuilder for content management are listed by pre-check "Check subscriptions that used SiteBuilder for content management".)

Additional notes

The sb4_fix_ba.pl script will not automatically unprovision SiteBuilder resources from Provider's subscription.

If any of resources are used by Provider, unprovide them using the pem.setResourceTypeLimit API method.

Internal content