TOCPREVNEXTINDEX

Ensim Corporation


Chapter 3
Customizing the control panel using skins

Introduction

This chapter provides information and instructions on customizing the control panel using skins.

Topics include:


Important icon

To customize the Ensim Pro control panel, you must be familiar with scripts, XML, and HTML programming.


About skins

Skins are customizable interfaces that allow you to change the “look and feel” of your Ensim Pro server.

Using skins, you can:

About Ensim Pro skins

Ensim Pro offers two visual styles:

Mercury skin

The Mercury skin provides an intuitive visual interface with informative dashboards that provide targeted information for each user type.

Some of its key features are:

Classic skin

The Classic skin adopts the look and feel of previous Ensim Pro versions and provides a simple interface to manage the hosting environment. The visual look stays consistent throughout the different administrative levels.

Creating a new skin

Creating a new skin consists of two steps.

Step 1: Setting up a directory for the new skin

The first step is to set up a skin directory to hold the various files and directories required to customize the Ensim Pro skin—such as httpd.conf, images, html, php, and stylesheets.

The skin directory will also contain the skin’s py file, <skin_name>.py. This file includes all the necessary implementation details.

The following procedure provides instructions on creating a <skin_name>.py file.


Procedure icon

To create a <skin_name>.py file:

  1. Log onto the Ensim Pro server as the root user.
  2. Create a new directory, <skin_name>, under the /usr/lib/opcenter/skins directory. All the skin components will be located in this directory.
  3. #mkdir /usr/lib/opcenter/skins/<skin_name>

    where <skin_name> refers to the name of the skin directory.

    This directory will store the components that make up the skin, that is the HTML files, the PHP files, the images, and the stylesheets.

    The following is a representation of a typical skin directory structure.

    • Root directory - /usr/lib/opcenter/skins/mercury
    • HTML files directory - /usr/lib/opcenter/skins/mercury/html
    • Image files - /usr/lib/opcenter/skins/mercury/images
    • HTTPD configuration code - /usr/lib/opcenter/skins/mercury/httpdconf

Note icon

The HTTPD configuration code specifies the rewrite rules for stylesheets and images, and for the shortcut, dashboard, and navigation bar pages.


  1. Create a directory, httpdconf, under the /usr/lib/opcenter/skins/<skin_name> directory. This directory will contain the “redirect” directives. These directives enable you to override an existing Ensim Pro page with your custom page.
  2. #mkdir /usr/lib/opcenter/skins/<skin_name>/httpdconf

  3. Create an html directory, html, under the /usr/lib/opcenter/skins/<skin_name> directory. This directory will contain the custom HTML pages of your skin.
  4. #mkdir /usr/lib/opcenter/skins/<skin_name>/html

  5. Create a default skin py file. You can do so by copying an existing skin (for example the classic skin).
  6. # cp /usr/lib/opcenter/skins/classic/classic.py/usr/lib/opcenter/skins/myskin/myskin.py


Note icon

If you now log on to the Appliance Administrator control panel and access the "Manage Skins" page, you should see the new skin <skin_name>.


Now that you have set up the skin directory, you need to create redirects that will enable you to implement the customization.

Step 2: Creating redirects

Redirects enable you to override a Ensim Pro page with your custom page.

A redirect uses 2 arguments:

Table 3-1 provides a list of redirect rules ( RewriteRules) for the home page, the navigation bar page, the shortcut page, and the top panel for all the control panels.


Note icon

The variable, <FILEPATH>, refers to the full directory path of the HTML or PHP page of your custom page. Replace <FILEPATH> with your custom page.


Select the page that you want to override and populate the /usr/lib/opcenter/<skin_name>/httpdconf/custompage file with one or more of the following RewriteRules.

Table 3-1. RewriteRules for pages to be overwrittten 
Control panel
Page to be overridden
RewriteRule (as one line)
Appliance Administrator
Home
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/$ <FILEPATH>
Navigation bar
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/navbar <FILEPATH>
Shortcut
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/view_shortcuts <FILEPATH>
Top panel
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/topbar <FILEPATH>
Reseller Administrator
Home
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/reseller/resellercp/$ <FILEPATH>
Navigation bar
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/reseller/resellercp/navbar <FILEPATH>
Shortcut
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/reseller/resellercp/view_shortcuts <FILEPATH>
Top panel
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/reseller/resellercp/topbar <FILEPATH>
Site Administrator
Home
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/siteadmin/$ <FILEPATH>
Navigation bar
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/siteadmin/navbar <FILEPATH>
Shortcut
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/siteadmin/view_shortcuts <FILEPATH>
Top panel
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/siteadmin/topbar <FILEPATH>
User Administrator
Home
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/useradmin/$ <FILEPATH>
Navigation bar
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/useradmin/navbar <FILEPATH>
Shortcut
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/useradmin/view_shortcuts <FILEPATH>
Top panel
RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/services/virtualhosting/useradmin/topbar <FILEPATH>

Overriding the top panel

The following is a simple example of a custom page. Ensim Pro also offers the ability to manage complex customizations using Dashboard XMLs. For example, you can customize the skin to dynamically load data about sites, resellers, and users onto your control panel dashboard. See Customizing the Dashboard XML for more information on this feature.


Example icon

To override the top panel:

  1. Follow the previous procedure and create a new skin, myskin.
  2. Create a file, custompages, under the /usr/lib/opcenter/skins/myskins/httpdconf directory with the following content:
  3. RewriteRule ^/fastcgiwebhost/fastcgiwebhost/webhost/topbar /usr/lib/opcenter/skins/myskin/html/appl_topbar.html

  4. Create a shortcut page for the Appliance Administrator control panel, appl_topbar.html, under the /usr/lib/opcenter/skins/myskins/html directory, with the following content.
  5. <html>

    <body>

    Welcome to Ensim Pro

    </body>

    </html>

  6. If your custom pages need to reference image files, create a directory, for example, images under /usr/lib/opcenter/skins/myskins, and place the images in the directory.
  7. Add a new rewrite line to the file, /usr/lib/opcenter/skins/myskins/httpdconf/custompages
  8. RewriteRule /images/(.+).gif /usr/lib/opcenter/skins/myskin/images/$1.gif

    The Welcome to Ensim Pro page in Step 3 would then be:

    <html>

    <body>

    <img src="/images/mylogo.gif" border=0> Welcome to Ensim Pro

    </body>

    </html>

  9. Restart Ensim Pro.

Important icon

You must restart Ensim Pro whenever you modify a rewrite rule.


Customizing the Dashboard XML

The Dashboard XML provides a source of data for skin developers. It can be used to design skins that display a rich set of appliance, reseller, site, or user properties as well as statistics.

The Dashboard XMLs are provided to skin developers and can contain the following data:

Dashboard XMLs allows skin developers to update the skin with dynamic information, depending on the administrative level. Ensim Pro provides four XML URLs that correspond to the four administrative levels: Appliance Administrator, Reseller Administrator, Site Administrator, and User Administrator.

The following are examples of data used in the Dashboard XML for each administrative level.

Appliance Administrator

Reseller Administrator

Site Administrator

User Administrator

Refer to the Dashboard XML examples for the complete data provided by the Dashboard XMLs.

Using Dashboard XMLs to customize the dashboard

Dashboard XMLs provides four XML URLs that provide access to the dashboard.


Important icon

These XML URLs are protected; they are not public URLs accessible to unauthorized users. To obtain the Dashboard XMLs, you must pass special authentication cookies.


The following section provides a sample implementation of the Dashboard XML (the sample skin used is called myskin) that contains the implementation of the dashboard parser and the function get_dashboard_data, that contains the commands required to obtain as well as parse the dashboard data.


Note icon

The sample skin, myskin, is provided as an RPM, webppliance-skin-myskin-3.5.2-3.i386.rpm.


Table 3-2 lists the functions and constants contained in the dashboard library, dashboard_lib.php file.

Table 3-2. Functions and constants used in the dashboard_lib.php file 
Functions
string get_dashboard_data(string urlstring)

This function returns a PHP hash data structure.
get_dashboard_data makes a HTTPS connection to the given urlstring, url-path. It performs authentication by using the globally available cookie variable 'ocw_cookie' to load the XML. The function then takes the XML and parses it into a PHP hash data structure. The parsing-to-php-data-structure is done by the phpxml module (which is included as part of the sample skin, myskin.
Documentation on the data structure as well as the parser is available at http://www.devdump.com/phpxml.php
Constants
$AA_dash
Refers to the Appliance Administrator Dashboard URL
$RA_dash
Refers to the Reseller Administrator Dashboard URL
$SA_dash
Refers to the Site Administrator Dashboard URL
$UA_dash
Refers to the User Administrator Dashboard URL

Invoking the Dashboard XML

The following example illustrates how the sample skin (myskin) uses a PHP code sample (appl_topbar.php located under /usr/lib/opcenter/skins/myskin/html) to load the Appliance Administrator XML and display the server uptime and server name on the dashboard panel.

Loading the server uptime and server name information on the dashboard panel


Example icon

<HTML>

<HEAD>

<LINK REL="stylesheet" HREF="/webhost/stylesheet/" TYPE="text/css">

</HEAD>

<BODY leftmargin ="15" topmargin ="2" marginwidth="15" marginheight="2" bgcolor="#ffffff">

<TABLE BORDER="0" WIDTH=750>

<TR>

<TD CLASS="help">

<?php

// load the dashboard API

include("dashboard_lib.php");

// dashbard url for appliance admin

global $AA_dash;

// load the URL, and parse the XML into a PHP data structure

// (for more information on the data structure, visit

// http://www.devdump.com/phpxml.php)

$xtree = get_dashboard_data($AA_dash);

// pull uptime and hostname from the appliance admin XML

$uptime = $xtree["APPLIANCE"][0]["PROPERTIES"][0]["UPTIME"][0]["VALUE"];

$server = $xtree["APPLIANCE"][0]["PROPERTIES"][0]["SERVER_NAME"][0]["VALUE"];

echo "Server: $server<BR>";

echo "Uptime (secs): $uptime<BR>";

?>

</TD>

</TR>

</TABLE>

</BODY>

</HTML>

Dashboard XML examples

The following XML examples (for each administrative level) display output samples generated by the Dashboard URL.

Appliance Administrator


Example icon

1

<?xml version="1.0" ?>

<appliance>

<properties>

<uptime>5185839</uptime>

<server_name>example1.example.com</server_name>

<server_ip>1.2.3.4</server_ip>

<services>

<item>siteinfo</item>

<item>aliases</item>

<item>bandwidth</item>

<item>develenv</item>

<item>logrotate</item>

<item>vhbackup</item>

<item>files</item>

<item>analog</item>

<item>ipinfo</item>

<item>diskquota</item>

<item>telnet</item>

<item>ssh</item>

<item>bind</item>

<item>users</item>

<item>proftpd</item>

<item>apache</item>

<item>sendmail</item>

<item>imap</item>

<item>anonftp</item>

<item>openssl</item>

<item>mysql</item>

<item>reseller</item>

<item>cgi</item>

<item>ssi</item>

<item>weblogs</item>

<item>mod_perl</item>

<item>tomcat4</item>

<item>subdomain</item>

<item>vacation</item>

<item>majordomo</item>

<item>sqmail</item>

<item>frontpage</item>

<item>mivamerchant</item>

<item>webalizer</item>

</services>

<domain_count>2</domain_count>

<hidden_services/>

</properties>

<statistics>

<disk_total>8940.969</disk_total>

<disk_used>4740.809</disk_used>

</statistics>

</appliance>

Reseller Administrator


Example icon

2

<?xml version="1.0" ?>

<reseller>

<properties>

<username>joe</username>

<reseller_email>reseller@example.com</reseller_email>

<uptime>5186036</uptime>

<server_ip>10.0.1.13</server_ip>

<server_name>example1.example.com</server_name>

<reseller_fullname>reseller</reseller_fullname>

<hidden_services/>

<reseller_id>3</reseller_id>

</properties>

<statistics>

<users_used>0</users_used>

<bandwidth_total>50000.0</bandwidth_total>

<ipinfo_nb_used>0</ipinfo_nb_used>

<diskquota_used>0.0</diskquota_used>

<bandwidth_used>0.0</bandwidth_used>

<ipinfo_ip_total>5</ipinfo_ip_total>

<ipinfo_nb_total>30</ipinfo_nb_total>

<users_total>5000</users_total>

<diskquota_total>50000.0</diskquota_total>

<ipinfo_ip_used>0</ipinfo_ip_used>

</statistics>

</reseller>

Site Administrator


Example icon

3

<?xml version="1.0" ?>

<site>

<properties>

<files>

<enabled>1</enabled>

</files>

<cgi>

<scriptalias>cgi-bin</scriptalias>

<enabled>1</enabled>

</cgi>

<users>

<maxusers>50</maxusers>

<enabled>1</enabled>

</users>

<sendmail>

<enabled>1</enabled>

<preference>10</preference>

<mailserver>mail.example1-name1.example.com</mailserver>

</sendmail>

<proftpd>

<ftpserver>ftp.example1-name1.example.com</ftpserver>

<enabled>1</enabled>

</proftpd>

<bandwidth>

<threshold>5368709120</threshold>

<enabled>1</enabled>

<rollover>1</rollover>

</bandwidth>

<siteinfo>

<domain>example1-name1.example.com</domain>

<admin_user>myadmin</admin_user>

<admin>admin1</admin>

<enabled>1</enabled>

<passwd1>***</passwd1>

<email>example1@example.com</email>

<passwd2>***</passwd2>

</siteinfo>

<telnet>

<enabled>1</enabled>

<jail>1</jail>

</telnet>

<majordomo>

<enabled>1</enabled>

</majordomo>

<aliases>

<enabled>0</enabled>

<aliases/></aliases>

<logrotate>

<enabled>1</enabled>

</logrotate>

<tomcat4>

<enabled>0</enabled>

</tomcat4>

<ssi>

<enabled>1</enabled>

</ssi>

<ssh>

<enabled>1</enabled>

<jail>1</jail>

</ssh>

<mysql>

<enabled>0</enabled>

<dbaseadmin>myadmin</dbaseadmin>

<dbaseprefix>example1-name1_example_com_-_</dbaseprefix>

<dbasenum>1</dbasenum>

</mysql>

<apache>

<enabled>1</enabled>

<webserver>www.example1-name1.example.com</webserver>

<jail>0</jail>

</apache>

<imap>

<enabled>1</enabled>

</imap>

<analog>

<enabled>1</enabled>

</analog>

<anonftp>

<enabled>1</enabled>

</anonftp>

<vhbackup>

<enabled>1</enabled>

</vhbackup>

<develenv>

<enabled>0</enabled>

</develenv>

<ipinfo>

<ipaddrs/>

<namebased>1</namebased>

<enabled>1</enabled>

<nbaddrs>

<item>1.2.3.4</item>

</nbaddrs>

</ipinfo>

<reseller>

<enabled>1</enabled>

<reseller_id>0</reseller_id>

</reseller>

<diskquota>

<units>MB</units>

<enabled>1</enabled>

<quota>500.0</quota>

</diskquota>

<bind>

<enabled>1</enabled>

</bind>

<weblogs>

<enabled>1</enabled>

</weblogs>

<vacation>

<enabled>1</enabled>

</vacation>

<webalizer>

<enabled>0</enabled>

</webalizer>

<sqmail>

<enabled>1</enabled>

</sqmail>

<mod_perl>

<alias>perl</alias>

<enabled>0</enabled>

</mod_perl>

<mivamerchant>

<enabled>0</enabled>

</mivamerchant>

<openssl>

<enabled>0</enabled>

</openssl>

<subdomain>

<wildcards>0</wildcards>

<max>5</max>

<enabled>0</enabled>

<base>/var/www</base>

</subdomain>

<frontpage>

<enabled>1</enabled>

</frontpage>

</properties>

<statistics>

<subdomain_used>0</subdomain_used>

<mysql_total>0</mysql_total>

<bandwidth_total>5120.0</bandwidth_total>

<mysql_used>0</mysql_used>

<diskquota_used>8.9</diskquota_used>

<subdomain_total>0</subdomain_total>

<bandwidth_used>0.0</bandwidth_used>

<users_used>0</users_used>

<users_total>50</users_total>

<diskquota_total>500.0</diskquota_total>

</statistics>

</site>

User Administrator


Example icon

4

<?xml version="1.0" ?>

<user>

<properties>

<username>name</username>

<siteinfo_domain>example1-name1.example.com</siteinfo_domain>

</properties>

<statistics>

<username>name</username>

<siteinfo_domain>example1-name1.example.com</siteinfo_domain>

<diskquota_used>0.039</diskquota_used>

<diskquota_total>20.0</diskquota_total>

</statistics>

</user>

Advanced skin dashboard for the Site Administrator control panel

The Site Administrator control panel includes an advanced skin dashboard that provides Site Administrators with statistical information on key hosting resources. The skin dashboard is accessible using the Dashboard option on the Site Administrator control panel. Refer to Table 3-3 for the list of hosting information that is accessible to the Site Administrator.

Table 3-3. Hosting information introduced in the skin dashboard
Site backup information
  • The date and time of the last backup
  • The date and time when the next backup is scheduled
Bandwidth information
  • The network traffic categorized by Web / FTP/ Email
  • The bandwidth used in the current and previous month
Site user information
  • The number of site users along with information about the allocated disk quota and amount of disk space used
MySQL database information
  • The list of databases along with the amount of disk space used by each database
Email information (Sendmail)
  • The number of responders
  • The number of email messages in the mail queue
  • The total size of the mailbox across all the users
  • The size of the mailbox for each user
  • The number of aliases
  • The number of mailing lists
Subdomain information
  • The total number of subdomains hosted on the site
Webalizer and Analog statistics
  • The number of page hits
  • Total history (7 day / 7 month) of page hits
Service information
  • The active or inactive status of the services—Web, FTP, Email, Mail access protocols (POP, IMAP), and MySQL.
Site Administrator information
  • The date and time of the last login

The skin dashboard uses a new XML file to provide the site information. The XML file can be accessed at https://<host_name>:19638/webhost/services/virtualhosting/siteadmin/info_xml where <host_name> is the name of the Ensim Pro server.


Important icon

If you are using the PHP library file dashboard_lib.php that is referenced in the section Using Dashboard XMLs to customize the dashboard, you must call the function get_dashboard_data with the argument webhost/services/virtualhosting/siteadmin/info_xml instead of using the constant $SA_dash ($SA_dash is set to the value webhost/services/virtualhosting/siteadmin/dashboard). For details on usage of the get_dashboard_data function, please refer to Table 3-2.


Advanced dashboard XML example

The following XML example displays a sample output generated by the dashboard URL.


Example icon

<?xml version="1.0" ?>

<site>

<properties>

<files>

<enabled> 1 </enabled>

</files>

<cgi>

<scriptalias> cgi-bin </scriptalias>

<enabled> 1 </enabled>

</cgi>

<users>

<maxusers> 50 </maxusers>

<enabled> 1 </enabled>

</users>

<mailscanner>

<scan_outgoing> 1 </scan_outgoing>

<scan_incoming> 1 </scan_incoming>

<enabled> 0 </enabled>

</mailscanner>

<sendmail>

<enabled> 1 </enabled>

<preference> 10 </preference>

<mailserver> mail.mailexample.com </mailserver>

</sendmail>

<proftpd>

<ftpserver> ftp.ftpexample.com </ftpserver>

<enabled> 1 </enabled>

</proftpd>

<bandwidth>

<threshold> 5368709120 </threshold>

<enabled> 1 </enabled>

<rollover> 1 </rollover>

</bandwidth>

<siteinfo>

<fstgeneration> 21 </fstgeneration>

<domain> example.com </domain>

<admin_user> admin </admin_user>

<admin> admin3 </admin>

<passwd1> *** </passwd1>

<enabled> 1 </enabled>

<email> example@ensim.com </email>

<passwd2> *** </passwd2>

</siteinfo>

<telnet>

<enabled> 1 </enabled>

<jail> 1 </jail>

</telnet>

<majordomo>

<enabled> 1 </enabled>

</majordomo>

<aliases>

<enabled> 0 </enabled>

<aliases/>

</aliases>

<logrotate>

<enabled> 1 </enabled>

</logrotate>

<tomcat4>

<enabled> 0 </enabled>

</tomcat4>

<aspmgr>

<siteopti_add> 1 </siteopti_add>

<payment_manage> 1 </payment_manage>

<sslcerts_manage> 1 </sslcerts_manage>

<siteopti_manage> 1 </siteopti_manage>

<payment_add> 1 </payment_add>

<emailmark_manage> 1 </emailmark_manage>

<enabled> 1 </enabled>

<emailmark_add> 0 </emailmark_add>

<sslcerts_add> 1 </sslcerts_add>

</aspmgr>

<ssh>

<enabled> 1 </enabled>

<jail> 1 </jail>

</ssh>

<mysql>

<enabled> 1 </enabled>

<dbaseadmin> admin </dbaseadmin>

<dbaseprefix> example_ </dbaseprefix>

<dbasenum> 5 </dbasenum>

</mysql>

<apache>

<enabled> 1 </enabled>

<webserver> www.example.com </webserver>

<jail> 0 </jail>

</apache>

<spam_filter>

<enabled> 1 </enabled>

</spam_filter>

<imap>

<enabled> 1 </enabled>

</imap>

<analog>

<enabled> 1 </enabled>

</analog>

<anonftp>

<enabled> 1 </enabled>

</anonftp>

<vhbackup>

<enabled> 1 </enabled>

</vhbackup>

<develenv>

<enabled> 0 </enabled>

</develenv>

<ipinfo>

<ipaddrs/>

<namebased> 1 </namebased>

<enabled> 1 </enabled>

<nbaddrs>

<item> 1.2.3.4 </item>

</nbaddrs>

</ipinfo>

<reseller>

<enabled> 1 </enabled>

<reseller_id> 0 </reseller_id>

</reseller>

<diskquota>

<units> MB </units>

<enabled> 1 </enabled>

<quota> 500.0 </quota>

</diskquota>

<bind>

<enabled> 1 </enabled>

</bind>

<weblogs>

<enabled> 1 </enabled>

</weblogs>

<vacation>

<enabled> 1 </enabled>

</vacation>

<webalizer>

<enabled> 1 </enabled>

</webalizer>

<sqmail>

<enabled> 1 </enabled>

</sqmail>

<mod_perl>

<alias> perl </alias>

<enabled> 0 </enabled>

</mod_perl>

<mivamerchant>

<enabled> 0 </enabled>

</mivamerchant>

<openssl>

<enabled> 0 </enabled>

</openssl>

<ssi>

<enabled> 1 </enabled>

</ssi>

<subdomain>

<wildcards> 0 </wildcards>

<max> 5 </max>

<enabled> 1 </enabled>

<base> /var/www </base>

</subdomain>

<frontpage>

<enabled> 1 </enabled>

</frontpage>

<scriptsmgr>

<enabled> 0 </enabled>

</scriptsmgr>

</properties>

<statistics>

<vhbackup>

<next_scheduled> 2004-03-30 05:06 </next_scheduled>

</vhbackup>

<users>

<user_count> 4 </user_count>

<user_list>

<item>

<username> first_name </username>

<disk_quota> 20971520 </disk_quota>

<virtuser> 1 </virtuser>

<uid> 22001 </uid>

<fullname> First Name </fullname>

<disk_used> 11464704 </disk_used>

<privileged> 0 </privileged>

</item>

<item>

<username> admin </username>

<disk_quota> 524288000 </disk_quota>

<virtuser> 1 </virtuser>

<uid> 507 </uid>

<fullname> example.com </fullname>

<disk_used> 32223232 </disk_used>

<privileged> 1 </privileged>

</item>

<item>

<username> xxx </username>

<disk_quota> 20971520 </disk_quota>

<virtuser> 1 </virtuser>

<uid> 22000 </uid>

<fullname> xxx </fullname>

<disk_used> 32768 </disk_used>

<privileged> 0 </privileged>

</item>

<item>

<username> yyy </username>

<disk_quota> 20971520 </disk_quota>

<virtuser> 1 </virtuser>

<uid> 22002 </uid>

<fullname> yyy </fullname>

<disk_used> 36864 </disk_used>

<privileged> 0 </privileged>

</item>

</user_list>

<user_max> 50 </user_max>

</users>

<sendmail>

<total_responders> 0 </total_responders>

<queue_size> 0 </queue_size>

<total_mailbox_size> 29820488 </total_mailbox_size>

<user_count> 4 </user_count>

<user_mailboxes>

<item>

<user> aaa </user>

<mailbox> 9968320 </mailbox>

</item>

<item>

<user> admin </user>

<mailbox> 19852168 </mailbox>

</item>

<item>

<user> xxx </user>

<mailbox> 0 </mailbox>

</item>

<item>

<user> yyy </user>

<mailbox> 0 </mailbox>

</item>

</user_mailboxes>

<sendmail_status> 1 </sendmail_status>

<total_aliases> 6 </total_aliases>

<mail_disk_space> 29820488 </mail_disk_space>

<queue_total_mails> 0 </queue_total_mails>

<user_max> 50 </user_max>

</sendmail>

<proftpd>

<proftpd_status> 1 </proftpd_status>

</proftpd>

<siteinfo>

<site_last_login> 2004-03-29 17:01 </site_last_login>

</siteinfo>

<webalizer>

<monthly_avg_hits> 16 </monthly_avg_hits>

<last_7_days_hits>

<item>

<hits> 0 </hits>

<epoch> 1080580448.76 </epoch>

<day> 3/29 </day>

</item>

<item>

<hits> 0 </hits>

<epoch> 1080494048.76 </epoch>

<day> 3/28 </day>

</item>

<item>

<hits> 0 </hits>

<epoch> 1080407648.76 </epoch>

<day> 3/27 </day>

</item>

<item>

<hits> 0 </hits>

<epoch> 1080321248.76 </epoch>

<day> 3/26 </day>

</item>

<item>

<hits> 0 </hits>

<epoch> 1080234848.76 </epoch>

<day> 3/25 </day>

</item>

<item>

<hits> 1 </hits>

<epoch> 1080148448.76 </epoch>

<day> 3/24 </day>

</item>

<item>

<hits> 0 </hits>

<epoch> 1080062048.76 </epoch>

<day> 3/23 </day>

</item>

</last_7_days_hits>

<current_yyyymm> 200403 </current_yyyymm>

<this_month_total_hits> 16 </this_month_total_hits>

<last_month_total_hits> 0 </last_month_total_hits>

<last_7_months_hits>

<item>

<hits> 16 </hits>

<epoch> 1080580448.76 </epoch>

<month> 3/2004 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1078074848.76 </epoch>

<month> 2/2004 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1075396448.76 </epoch>

<month> 1/2004 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1072718048.76 </epoch>

<month> 12/2003 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1070126048.76 </epoch>

<month> 11/2003 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1067447648.76 </epoch>

<month> 10/2003 </month>

</item>

<item>

<hits> 0 </hits>

<epoch> 1064855648.76 </epoch>

<month> 9/2003 </month>

</item>

</last_7_months_hits>

</webalizer>

<majordomo>

<total_mlists> 0 </total_mlists>

<membership_counts/>

</majordomo>

<diskquota>

<max_diskspace> 524288000 </max_diskspace>

<current_diskspace> 43823104 </current_diskspace>

</diskquota>

<bandwidth>

<usage_by_category>

<web> 64724 </web>

<ftp> 50300 </ftp>

<console> 0 </console>

<unknown> 0 </unknown>

<mail> 50300 </mail>

</usage_by_category>

<limit> 5368709120 </limit>

<last_month_usage> 0 </last_month_usage>

<this_month_usage> 165324 </this_month_usage>

</bandwidth>

<ssh>

<sshd_status> 1 </sshd_status>

</ssh>

<mysql>

<db_count> 1 </db_count>

<db_max> 5 </db_max>

<mysqld_status> 1 </mysqld_status>

<db_list>

<item>

<disk_used> 9578 </disk_used>

<dbname> example_hello </dbname>

</item>

</db_list>

</mysql>

<apache>

<httpd_status> 1 </httpd_status>

</apache>

<apache13>

<httpd13_status> 1 </httpd13_status>

</apache13>

<subdomain>

<subdomain_count>

<usage> 1 </usage>

</subdomain_count>

<subdomain_max> 5 </subdomain_max>

</subdomain>

<imap>

<imap_status> 1 </imap_status>

</imap>

<analog>

<this_month_total_hits> 0 </this_month_total_hits>

<monthly_avg_hits> 15 </monthly_avg_hits>

<last_month_total_hits> 0 </last_month_total_hits>

<last_7_months_hits>

<item>

<epoch> 1080518400.0 </epoch>

<hits> 15 </hits>

<month> 3/2004 </month>

</item>

<item>

<epoch> 1078012800.0 </epoch>

<hits> 0 </hits>

<month> 2/2004 </month>

</item>

<item>

<epoch> 1075334400.0 </epoch>

<hits> 0 </hits>

<month> 1/2004 </month>

</item>

<item>

<epoch> 1072656000.0 </epoch>

<hits> 0 </hits>

<month> 12/2003 </month>

</item>

<item>

<epoch> 1070064000.0 </epoch>

<hits> 0 </hits>

<month> 11/2003 </month>

</item>

<item>

<epoch> 1067385600.0 </epoch>

<hits> 0 </hits>

<month> 10/2003 </month>

</item>

<item>

<epoch> 1064793600.0 </epoch>

<hits> 0 </hits>

<month> 9/2003 </month>

</item>

</last_7_months_hits>

</analog>

</statistics>

<services>

<aspmgr>

<site_asps>

<item>

<category> web </category>

<caption> Email Marketing </caption>

<manage> https://test.ignite.example.com/manage.asp?epid=3234523513&amp;sid=emailmark </manage>

<sa_desc> Increase traffic with email campaigns. </sa_desc>

<sa_title> Market My Web Site </sa_title>

<asp_id> emailmark </asp_id>

</item>

<item>

<category> web </category>

<caption> Site Optimization </caption>

<add> https://test.ignite.example.com/add.asp?epid=3234523513&amp;sid=siteopti </add>

<manage> https://test.ignite.example.com/manage.asp?epid=3234523513&amp;sid=siteopti </manage>

<sa_desc> Submit your site to top search engines. </sa_desc>

<sa_title> Promote My Web Site </sa_title>

<asp_id> siteopti </asp_id>

</item>

<item>

<category> web </category>

<caption> SSL Certs </caption>

<add> https://test.ignite.example.com/add.asp?epid=3234523513&amp;sid=sslcerts </add>

<manage> https://test.ignite.example.com/manage.asp?epid=3234523513&amp;sid=sslcerts </manage>

<sa_desc> Use SSL for site authentication. </sa_desc>

<sa_title> Secure My Web Site </sa_title>

<asp_id> sslcerts </asp_id>

</item>

<item>

<category> web </category>

<caption> Payment Processing </caption>

<add> https://test.ignite.example.com/add.asp?epid=3234523513&amp;sid=payment </add>

<manage> https://test.ignite.example.com/manage.asp?epid=3234523513&amp;sid=payment </manage>

<sa_desc> Offer a secure payment gateway. </sa_desc>

<sa_title> Power Your e-Business </sa_title>

<asp_id> payment </asp_id>

</item>

</site_asps>

</aspmgr>

</services>

</site>


Ensim Corporation
www.ensim.com

Contact Ensim
www.ensim.com/about/contact.html

TOCPREVNEXTINDEX