Changing Tomcat Java Connector Ports
The default port numbers for Coyote and Warp connectors in Parallels Plesk Panel are 9080 and 9008.
If you want Tomcat Java to work on other ports (e.g. 8090 and 8009), you should connect to the Parallels Plesk Panel database and add two parameters to the database as in the following example:
insert into misc (param,val) values (’coyote_connector_port’, ‘8090′);
insert into misc (param,val) values (’warp_connector_port’, ‘8009′);
Note: It is recommended that you change the Tomcat Java ports right after Parallels Plesk Panel is installed on server, or prior to enabling the Tomcat Java service for your domains.
Including Directives into Web Server Configuration File - Plesk
Note: you can change the location of virtual host directories using the transvhosts.pl utility, which is located either in /usr/local/psa/bin/ or /opt/psa/bin/ directory, depending on your operating system.
You can include domain-specific Apache configuration directives into web server configuration file. In Parallels Plesk Panel, each domain has virtual hosts configuration stored in a separate file httpd.include.
On all Linux systems, this file is located in the directory /var/www/vhosts/domain-name/conf/.
On FreeBSD systems, this file is located in the directory /usr/local/psa/home/vhosts/domain-name/conf/.
To use custom directives or redefine those inserted by Parallels Plesk Panel, you need to create the files vhost.conf or vhost_ssl.conf with necessary directives in the directory /path_to_vhosts/domain-name/conf/ for a domain, and /path_to_vhosts/domain-name/subdomains/subdomain-name/conf/ for a subdomain.
Resource: http://parallels.com/Plesk/
Restoring Mail Configuration in Plesk
Sometimes, Parallels Plesk Panel mail server configuration becomes corrupt and it is necessary to restore it. The restoration is carried out by internal mchk utility, intended for use by Parallels Plesk Panel.
However, as administrator, you can use it for restoring the Qmail and Courier-imap configuration when needed.
By default mchk is running in the background mode.
To execute it in the foreground, use the -v option. For example:
/usr/local/psa/admin/sbin/mchk -v
Reference : http://parallels.com/Plesk/
Blocking Access to Updater Functions from the Control Panel Linux Hosting
If you delegate server administration tasks to other users, but do not want them to use the Updates function or change the updating settings from the control panel, you can remove the screens related to Updater settings and the Updates icon from the control panel.
To do this, use the following MySQL command:
echo ‘REPLACE misc SET param=”disable_updater”, val=”true”‘ | mysql psa -uadmin -p`cat /etc/psa/.psa.shadow`
To restore the Updates icon and screens in the control panel, use the following MySQL command:
echo ‘REPLACE misc SET param=”disable_updater”, val=”false”‘ | mysql psa -uadmin -p`cat /etc/psa/.psa.shadow`
Reference : parallels.com/Plesk/
Upgrading Your Plesk Control Panel
You can easily install the necessary updates, control panel add-ons, and even upgrade your control panel to the latest available release using Parallels Plesk Panel Updater function within your control panel.
To upgrade your Parallels Plesk Panel or update its components:
1. Go to Home > Updates (in the Help & Support group).
The control panel connects to the Parallels official update server at URL http://autoinstall.plesk.com, retrieves information on the available releases, then analyses the components installed in the system and displays the lists of available releases and component updates. For each release a brief description of available operations is displayed.
Select the release version that you want to update, or upgrade to. A list of available components appears.
Select the check boxes corresponding to the components you wish to install and click Install. A confirmation screen appears.
Specify your e-mail address. You will be sent a notice by e-mail once update is completed. To confirm installation of the selected components, select the check box and click OK. The components/updates you selected will be downloaded and automatically installed in the background mode.
You can check for errors in the autoinstaller.log file located in the /tmp directory on the server hard drive.
