User manual PARALLELS PLESK PANEL 10.1 DEPLOYMENT GUIDE REV 1.0

[. . . ] Parallels Plesk Panel ® Copyright Notice Parallels Holdings, Ltd. c/o Parallels International GMbH Vordergasse 49 CH8200 Schaffhausen Switzerland Phone: +41 526320 411 Fax: +41 52672 2010 Copyright © 1999-2011 Parallels Holdings, Ltd. This product is protected by United States and international copyright laws. The product's underlying technology, patents, and trademarks are listed at http://www. parallels. com/trademarks. [. . . ] Standalone deployment of the Panel is performed using the Parallels Installer utility. The utility connects to a Parallels Plesk Panel update server where the Panel packages are stored, retrieves required packages and installs them. Parallels Installer works in either interactive mode (via the Web graphical user interface or command line), or automatic when it is run from command line with particular options specified. The latter allows automating the Panel deployment by using shell scripts. There are several distributions of Parallels Installer created for different operating systems and platforms, so be sure to obtain the Parallels Installer matching your host operating systems. Normally, Parallels Installer binaries are distributed under names in the following format: parallels_installer_v<installer version>_<build date>_os_<operating system name>_<operating system version>_<platform>. Note: When describing Parallels Installer CLI, we assume that the Parallels Installer utility is called parallels_installer. Official Parallels Plesk Panel repository is autoinstall. plesk. com (Linux/Unix packages) . You may want to set up custom mirrors for the Panel repositories within your hosting environment to save time, reduce traffic, and secure the installation. In this section: Getting Release ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Getting List of Product Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Installing the Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Installer CLI Reference (Reduced) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Installation Script (Linux/Unix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Standalone Deployment 21 Getting Release ID Release ID is a unique identifier of the Panel release, for example, Parallels Plesk Panel 10. 1. 0. To get a list of available release IDs, issue the following command: parallels_installer--show-releases on a Linux/Unix server parallels_installer. exe--show-releases on a Windows server A list of product versions will be displayed. For example: PLESK_10_1_0 (Parallels Plesk Panel for Linux/Unix 10. 1. 0) Getting List of Product Components To get a list of the release components, issue the command of the following format: parallels_installer--select-release-id <ID> --show-components For Parallels Plesk Panel 10 on a Linux/Unix server: parallels_installer--select-release-id PLESK_10_1_0 --show-components For Parallels Plesk Panel 10 on a Windows server: parallels_installer. exe--select-release-id PANEL_10_1_0_WIN--show-components A list of components is displayed with component names in the left part, and indication of whether this component can be installed ([install]) or upgraded ([upgrade]), with brief descriptions in the right part, for example (fragment): base autoinstaller postfix [install] - Parallels Plesk Panel base packages [install] - Parallels Installer [upgrade] - Postfix mail server The actual components are marked by [up2date]. 22 Standalone Deployment Installing the Panel To install Parallels Plesk Panel, issue a command of the following format: parallels_installer <packages source options> --select-release-id <ID> <components installation options> [other options] where packages source options define the location where the installer should obtain the Panel packages for installation <packages source options> = --source <URL> if using a mirror of the Panel Updates server OR --source <path> if using local file system OR none if installing from the Panel Updates server components installation options define what Panel components should be installed <components installation options> = --install-everything OR --install-component component1 [--install-component component2 [. . . [--install-component componentN]]] other options include those that define proxy settings, installation logging and so on. For full details, please refer to the Installer CLI Reference section Examples, Linux/Unix 1. The following command installs Parallels Plesk Panel 10 (release ID is PANEL_10_1_0) from the mirror set up on server available via HTTP at host mirror. example. com. Installation files will temporarily be stored at /tmp/panel, and the installation status will be reported to email admin@example. com. The installed components are base Panel packages, PostgreSQL server, and SpamAssassin spam filter. . /parallels_installer--source http://mirror. example. com/ --target /tmp/panel--select-release-id PLESK_10_1_0 --install-component base--installcomponent postgresql--install-component spamassassin--notify-email admin@example. com 2. The following command performs the complete installation (all available product components are installed) of Parallels Plesk Panel 10 (release ID is PANEL_10_1_0) from the Parallels Update server. All installer output will be redirected to an XML file. . /parallels_installer--select-release-id PLESK_10_1_0 --install-everything-- enable-xml-output Standalone Deployment 23 Examples, Windows 1. [. . . ] Edit the plesk. inf3 file removing all the build elements except those of the operating systems and architectures you wish to be supported by the mirror. Edit the billing. inf3 and pp-sitebuilder. inf3 files removing all the build elements except those of the operating systems and architectures you wish to be supported by the mirror. After the mirror is created, add the rsync calls to an executable file, and run it when you need to update the mirror data. For more information about the Rsync utility, visit http://samba. anu. edu. au/rsync/ CHAPTER 5 Installing and Upgrading License Keys In this chapter: Installing License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Upgrading a Trial License Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . [. . . ]