================================================================================
                  Xitex WebContent M1 1.8 Installation File
================================================================================

(c) Copyright XITEX Software 1999 - 2004. All rights reserved.

================================================================================
CONTENTS
================================================================================

1. System requirements
2. How to obtain a license key for your trial version
3. Installation
4. Troubleshooting for installation and customization
5. How to contact us


================================================================================
1. SYSTEM REQUIREMENTS
================================================================================

Xitex WebContent M1 is developed for Java 2 platform (J2EE) and it uses 
MySQL for data storage. Java 2 makes the product very powerful and effective! 
Our CMS is scalable, operational system independable, and reliable.


1.1 Server requirements

The server requirements regarding program part (all software are free of 
charge) are as follows: 

  * Any operational system with JRE 1.4.2 realization 
    (Win*, Linux, FreeBSD, MacOS, Solaris, etc.). Most of our users usually 
    prefer Windows 2000, Red Hat 6.2, Red Hat 9.0, ASP Linux 7.3. 
  * Application server, which supports Servlet  2.3/JSP 1.2 specification. 
    Tomcat 4.1.29 is recommended for usage. 
  * Web server. You don't have to use a separate web server if the application 
    server is able to perform as a web server as well. We recommend any 
    version of Apache with JK connector. 
  * The minimum size of virtual memory should be 128 Mb. We recommend JDK 
    1.4.2_03 with launch in server mode. 
  * Database is MySQL 3.23 or higher. 

The server minimum requirements regarding hardware are as follows: 

  * Pentium 3 or higher.
  * RAM 256Mb.
  * 10 Mb of free space on hard disc for program itself. Additional need of 
    hard disc space depends on quantity and size of web-sites served by CMS. 

Note: You have not to buy extra expensive software! It is not necessary for 
Xitex WebContent M1 to use dedicated server.

1.2 Clients' requirements

For client PC only any web-browser is needed (IE 6.0, Netscape 6, Mozilla, 
Opera 7.0, etc).

Clients' computer configuration depends only on web-browser you use. So, if 
you can browse web on your computer it can be used as a client PC to Xitex 
WebContent M1. If you suppose working with M1 Word.Java WYSIWYG editor you 
need Java Virtual Machine 1.4.2 or higher. 


================================================================================
2. HOW TO OBTAIN A LICENSE KEY FOR YOUR TRIAL VERSION
================================================================================

The process of getting a 45-days trial key is as follows:

  * Fill in the form http://webcontent-m1.com/m1/en/buyonline/trial_version
    and press the REGISTER button below the form.
    Please be sure to enter only valid data in all fields. 
    Note, that license key will be sent to e-mail you enter in the form!
  * Revise entered data on new opened page. 
    If there is a mistake click an EDIT button and correct data.
    In case of no mistake you can click CONFIRM button to go to next step.
  * If everything is done propely you'll receive a letter with a trial 
    activation code. Also you'll see a page with more available download 
    versions of a trial.


================================================================================
3. INSTALLATION
================================================================================

3.1 Prior installations

DRAW ATTENTION:
The system Xitex WebContent M1 and its software environment demand of necessary 
connection to the Internet. Users' activity will be sufficiently productive in 
online mode of Internet working.

3.1.1 Database for Xitex WebContent M1

Content Management System Xitex WebContent M1 is working with database used for 
content saving and service operations. Below is showed an example of actions for
installation of database MySQL. CMS Xitex WebContent M1 needs MySQL version 3.23
or higher for correct work.

3.1.1.1 Download process

Check the MySQL downloads page (http://dev.mysql.com/downloads/) for information
about the current version and for downloading instructions. For a complete 
up-to-date list of MySQL download mirror sites, see 
http://dev.mysql.com/downloads/mirrors.html. 

There you will also find information about becoming a MySQL mirror site and how 
to report a bad or out-of-date mirror. Main mirror is located at 
http://mirrors.sunsite.dk/mysql/. 

3.1.1.2 Installing of MySQL on Windows

To install MySQL on Windows using a binary distribution, follow this procedure:

  * If you are working on a Windows NT, 2000, or XP machine, make sure that you 
    have logged in as a user with administrator privileges. 
  * If you are doing an upgrade of an earlier MySQL installation, it is 
    necessary to stop the current server. On Windows NT, 2000, or XP machines, 
    if you are running the server as a Windows service, stop it as follows from 
    the command prompt: 
       C:\> NET STOP MySQL
    If you plan to use a different server after the upgrade (for example, if you
    want to run mysqld-max rather than mysqld), remove the existing service: 
       C:\> C:\mysql\bin\mysqld --remove
    You can reinstall the service to use the proper server after upgrading. If 
    you are not running the MySQL server as a service, stop it like this: 
       C:\> C:\mysql\bin\mysqladmin -u root shutdown
  * Exit the WinMySQLAdmin program if it is running. 
  * Unzip the distribution file to a temporary directory. 
  * Run the setup.exe program to begin the installation process. If you want to 
    install MySQL into a location other than the default directory ('C:\mysql'),
    use the Browse button to specify your preferred directory. If you do not 
    install MySQL into the default location, you will need to specify the 
    location whenever you start the server. The easiest way to do this is to 
    use an option file, as described in section
       http://dev.mysql.com/doc/mysql/en/Windows_prepare_environment.html 
  * Finish the install process. 
    To start the server, enter this command: 
    C:\> C:\mysql\bin\mysqld --console
    When the server finishes its startup sequence, you should see a message 
    that the server is ready to service client connections.
    The server will continue to write to the console any further diagnostic 
    output it produces. You can open a new console window in which to run 
    client programs. 
    If you omit the --console option, the server writes diagnostic output to 
    the error log in the data directory (`C:\mysql\data' by default). The error
    log is the file with the '.err' extension. 

Note: The accounts that are listed in the MySQL grant tables initially have no 
passwords. After starting the server, you should set up passwords for them 
using the instructions in section 
http://dev.mysql.com/doc/mysql/en/Post-installation.html. 

3.1.1.3 Installing of MySQL on Linux

The recommended way to install MySQL on Linux is by using the RPM packages. The 
MySQL RPMs are currently built on a SuSE Linux 7.3 system, but should work on 
most versions of Linux that support rpm and use glibc. To obtain RPM packages, 
see http://dev.mysql.com/doc/mysql/en/Getting_MySQL.html.
 
Many Linux distributions still ship with MySQL 3.23 and they usually link 
applications dynamically to save disk space. If these shared libraries are in a 
separate package (for example, MySQL-shared), it is sufficient to simply leave 
this package installed and just upgrade the MySQL server and client packages 
(which are statically linked and do not depend on the shared libraries). For 
distributions that include the shared libraries in the same package as the MySQL
server (for example, Red Hat Linux), you could either install our 3.23 
MySQL-shared RPM, or use the MySQL-shared-compact package instead. 

The following RPM packages are available:
 
  * MySQL-server-VERSION.i386.rpm The MySQL server. You will need this unless 
    you only want to connect to a MySQL server running on another machine. 
    Note: Server RPM files were called MySQL-VERSION.i386.rpm before MySQL 
    4.0.10. That is, they did not have -server in the name. 
  * MySQL-Max-VERSION.i386.rpm The MySQL-Max server. This server has additional 
    capabilities that the one provided in the MySQL-server RPM does not. You 
    must install the MySQL-server RPM first, because the MySQL-Max RPM depends 
    on it. 
  * MySQL-client-VERSION.i386.rpm The standard MySQL client programs. You 
    probably always want to install this package. 
  * MySQL-bench-VERSION.i386.rpm Tests and benchmarks. Requires Perl and the 
    DBD::mysql module. 
  * MySQL-devel-VERSION.i386.rpm The libraries and include files that are needed
    if you want to compile other MySQL clients, such as the Perl modules. 
  * MySQL-shared-VERSION.i386.rpm This package contains the shared libraries 
    (libmysqlclient.so*) that certain languages and applications need to 
    dynamically load and use MySQL. 
  * MySQL-shared-compat-VERSION.i386.rpm This package includes the shared 
    libraries for both MySQL 3.23 and MySQL 4.0. Install this package instead 
    of MySQL-shared if you have applications installed that are dynamically 
    linked against MySQL 3.23 but you want to upgrade to MySQL 4.0 without 
    breaking the library dependencies. This package has been available since 
    MySQL 4.0.13. 
  * MySQL-embedded-VERSION.i386.rpm The embedded MySQL server library (from 
    MySQL 4.0). 
  * MySQL-VERSION.src.rpm This contains the source code for all of the previous 
    packages. It can also be used to rebuild the RPMs on other architectures 
    (for example, Alpha or SPARC). 

To see all files in an RPM package (for example, a MySQL-server RPM), run: 
shell> rpm -qpl MySQL-server-VERSION.i386.rpm

To perform a standard minimal installation, run: 
shell> rpm -i MySQL-server-VERSION.i386.rpm
shell> rpm -i MySQL-client-VERSION.i386.rpm

To install just the client package, run: 
shell> rpm -i MySQL-client-VERSION.i386.rpm

RPM provides a feature to verify the integrity and authenticity of packages 
before installing them. If you would like to learn more about this feature, see 
http://dev.mysql.com/doc/mysql/en/Verifying_Package_Integrity.html. 

The server RPM places data under the '/var/lib/mysql' directory. The RPM also 
creates a login account for a user named mysql (if one does not already exist) 
to use for running the MySQL server, and creates the appropriate entries in 
'/etc/init.d/' to start the server automatically at boot time. (This means that 
if you have performed a previous installation and have made changes to its 
startup script, you may want to make a copy of the script so that you don't 
lose it when you install a newer RPM.) See 
http://dev.mysql.com/doc/mysql/en/Automatic_start.html for more information on 
how MySQL can be started automatically on system startup. 

If you want to install the MySQL RPM on older Linux distributions that do not 
support initialization scripts in '/etc/init.d' (directly or via a symlink), 
you should create a symbolic link that points to the location where your 
initialization scripts actually are installed. For example, if that location is
'/etc/rc.d/init.d', use these commands before installing the RPM to create 
'/etc/init.d' as a symbolic link that points there: 
shell> cd /etc
shell> ln -s rc.d/init.d

However, all current major Linux distributions should already support the new 
directory layout that uses `/etc/init.d', because it is required for LSB (Linux 
Standard Base) compliance. 

If the RPM files that you install include MySQL-server, the mysqld server should
be up and running after installation. You should now be able to start using 
MySQL. 

If something goes wrong, you can find more information in the binary 
installation section. See 
http://dev.mysql.com/doc/mysql/en/Installing_binary.html.  

Note: The accounts that are listed in the MySQL grant tables initially have no 
passwords. After starting the server, you should set up passwords for them using
the instructions in http://dev.mysql.com/doc/mysql/en/Post-installation.html.

3.1.2 Installing and configuring Tomcat

Tomcat is the servlet container that is used in the official Reference 
Implementation for the Java Servlet and JavaServer Pages technologies. The Java 
Servlet and JavaServer Pages specifications are developed by Sun under the Java 
Community Process. 

Servlets are memory-resident Java programs, running inside a servlet container 
(e.g., Tomcat). Because they're memory-resident, they can quickly respond to 
requests, as they do not incur the overhead of process creation and subsequent 
cleanup, unlike CGI-based scripting, e.g. perl, etc.

Containers are the interface between a component and the low-level 
platform-specific functionality that supports the component. Before a Web, 
enterprise bean, or application client component can be executed, it must be 
assembled into a J2EE module and deployed into its container. 

The assembly process involves specifying container settings for each component 
in the J2EE application and for the J2EE application itself. Container settings 
customize the underlying support provided by the J2EE server.

Java Servlet technology provides Web developers with a simple, consistent 
mechanism for extending the functionality of a Web server and for accessing 
existing business systems. A servlet can almost be thought of as an applet that
runs on the server side--without a face. Java servlets make many Web 
applications possible. Tomcat 4.x implements a new servlet container (called 
Catalina) that is based on completely new architecture. The 4.x releases 
implement the Servlet 2.3 and JSP 1.2 specifications.

In order to use Tomcat 4.x for developing web applications, you must first 
install it (and the software it depends on). The required steps are outlined in 
the following subsections.

The system Xitex WebContent M1 needs Tomcat version 4.1.29 or higher worked 
under JDK 1.4.2. The Tomcat should be configured with default root auto-deploy 
of web application option on.

3.1.2.1 Why you need a JDK

Tomcat will operate under any Java Development Kit (JDK) environment that 
provides a JDK 1.2 or later platform. You will need a Java Development Kit, as 
opposed to a Java Runtime Environment, so that your servlets, other classes, 
and JSP pages can be compiled. 

  1. Download and Install the Software Development Kit (SDK)
     Download the Java 2 SDK from: http://java.sun.com/j2se/ 

DRAW ATTENTION:
Downloading the Java Runtime Environment (JRE) instead is not sufficient for 
most users because Tomcat uses the javac.exe that is not present in the JRE to 
compile JSP pages. Unless you are very sure of what you are doing, please use 
the full SDK.

  2. Install the SDK according to the instructions included with the release.
  
  3. Set an environment variable JAVA_HOME to the pathname of the directory 
     into which you installed the SDK release.

3.1.2.2 Tomcat installing

  1. You may download Tomcat from http://jakarta.apache.org/site/binindex.cgi.
  
  2. Unpack the binary distribution into a convenient location so that the 
     distribution resides in its own directory (conventionally named 
     "jakarta-tomcat-4.0").  For the purposes of the remainder of this document,
     the symbolic name "${catalina.home}" is used to refer to the full pathname 
     of the release directory.

  3. There are two techniques by which Tomcat can be started:
     
     * Via an environment variable:

       a) Set an environment variable CATALINA_HOME to the path of the directory
          into which you have installed Tomcat.
       b) Execute the shell command:
          %CATALINA_HOME%\bin\startup          (Windows)
          $CATALINA_HOME/bin/startup.sh          (Unix)

     * By modifying your current working directory execute the following shell 
       commands:

       cd %CATALINA_HOME%\bin                  (Windows)
       startup                                 (Windows)

       cd $CATALINA_HOME/bin                     (Unix)
       ./startup.sh                              (Unix)

After startup, the default web applications included with Tomcat will be 
available by browsing:

    http://localhost:8080/ 

Further information about configuring and running Tomcat can be found in the 
documentation included here, as well as on the Tomcat web site:

    http://jakarta.apache.org/tomcat/ 

3.1.3 APACHE HTTP SERVER

3.1.3.1 What is the Apache HTTP Server Project?

The Apache Project is a collaborative software development effort aimed at 
creating a robust, commercial-grade, featureful, and freely-available source 
code implementation of an HTTP (Web) server. The project is jointly managed by 
a group of volunteers located around the world, using the Internet and the Web 
to communicate, plan, and develop the server and its related documentation. 
These volunteers are known as the Apache Group. In addition, hundreds of users 
have contributed ideas, code, and documentation to the project. 

3.1.3.2 Downloading Apache

Information on the latest versions of Apache can be found on the web site of the
Apache web server at http://httpd.apache.org/download.cgi. There you will find 
the current release, as well as more recent alpha or beta test versions, and a 
list of HTTP and FTP mirrors from which you can download the Apache web server. 
Please use a mirror near to you for a fast and reliable download.

For Windows installations you should download the version of Apache for Windows 
with the .msi extension. This is a single Microsoft Installer file, which 
contains a ready-to-run version of Apache. There is a separate .zip file, which 
contains only the source code. You can compile Apache yourself with the 
Microsoft Visual C++ (Visual Studio) tools.

3.1.3.3 Apache Installing

You need Microsoft Installer 1.2 or above for the installation to work. On 
Windows 9x you can update your Microsoft Installer to version 2.0 here and on 
Windows NT 4.0 and 2000 the version 2.0 update can be found here. Windows XP 
does not need this update.

Note that you cannot install two versions of Apache 2.0 on the same computer 
with the binary installer. You can, however, install a version of the 1.3 series
and a version of the 2.0 series on the same computer without problems. If you 
need to have two different 2.0 versions on the same computer, you have to 
compile and install Apache from the source 
http://httpd.apache.org/docs-2.0/platform/win_compiling.html.

Run the Apache .msi file you downloaded above. The installation will ask you for
these things:

  1. Network Domain. Enter the DNS domain in which your server is or will be 
     registered in. For example, if your server's full DNS name is 
     server.mydomain.net, you would type mydomain.net here.
  2. Server Name. Your server's full DNS name. From the example above, you would
     type server.mydomain.net here.
  3. Administrator's Email Address. Enter the server administrator's or 
     webmaster's email address here. This address will be displayed along with 
     error messages to the client by default.
  4. For whom to install Apache Select for All Users, on Port 80, as a Service -
     Recommended if you'd like your new Apache to listen at port 80 for incoming
     traffic. It will run as a service (that is, Apache will run even if no one 
     is logged in on the server at the moment) Select only for the Current User,
     on Port 8080, when started Manually if you'd like to install Apache for 
     your personal experimenting or if you already have another WWW server 
     running on port 80.
  5. The installation type. Select Typical for everything except the source code
     and libraries for module development. With Custom you can specify what to 
     install. A full install will require about 13 megabytes of free disk space.
     This does not include the size of your web site(s).
  6. Where to install. The default path is C:\Program Files\Apache Group under 
     which a directory called Apache2 will be created by default.

During the installation, Apache will configure the files in the conf 
subdirectory to reflect the chosen installation directory. However, if any of 
the configuration files in this directory already exist, they will not be 
overwritten. Instead, the new copy of the corresponding file will be left with 
the extension .default. So, for example, if conf\httpd.conf already exists, it 
will be renamed as conf\httpd.conf.default. After the installation you should 
manually check to see what new settings are in the .default file, and if 
necessary, update your existing configuration file.

Also, if you already have a file called htdocs\index.html, it will not be 
overwritten (and no index.html.default will be installed either). This means it 
should be safe to install Apache over an existing installation, although you 
would have to stop the existing running server before doing the installation, 
and then start the new one after the installation is finished.

After installing Apache, you must edit the configuration files in the conf 
subdirectory as required. These files will be configured during the installation
so that Apache is ready to be run from the directory it was installed into, 
with the documents server from the subdirectory htdocs. There are lots of other 
options which you should set before you really start using Apache. However, to 
get started quickly, the files should work as installed. 

3.2 Distribution

3.2.1 Download Xitex WebContent M1

To download product and necessary manuals please visit:
http://download.webcontent-m1.com.

3.2.2 How to obtain a license key for your trial version

The process of getting a 30-days trial key is as follows:

  * Fill in the form http://trial.webcontent-m1.com and press the REGISTER 
    button below the form. Please be sure to enter only valid data in all 
    fields. Note, that license key will be sent to e-mail you enter in the form!
  * Revise entered data on new opened page. If there is a mistake click an EDIT 
    button and correct data. In case of no mistake you can click CONFIRM button 
    to go to next step.
  * If everything is done properly you'll receive a letter with a trial 
    activation code. Also you'll see a page with more available download 
    versions of a trial.

This license key you may use in installation process below.

3.2.3 Deploying Xitex WebContent M1

  1. Place the file m1.war into default root folder of Tomcat. 
  2. Install it using Tomcat Manager or simply restart Tomcat.
  3. Tomcat will automatically deploy m1.war. 
  4. You will see the Xitex WebContent M1 folder within Tomcat default root. 
  5. From now Xitex WebContent M1 is accessible via path /m1.
  6. You can change this path by adding of context name.

3.2.3 First step for the system to start

  1. To start Xitex WebContent M1 installation process enter URL address in 
     browser like follows: http://my.site:8080/m1/backoffice 
  2. The URL address could be changed depending on your domain name and Tomcat 
     or Apache listened port. 
  3. After entering forgoing URL address you will find the first system 
     installation window on your screen.

To accomplish installation follow the installation process pages in your 
browser.

3.3 System start

3.3.1 Initial entrance to the system

When required components are allocated and created on the server, please start 
your browser. When you go to the address showed before, the first system window 
will open on your screen. 

You can realize an installation process in the following way:

  * Selection of installation language.
    You have to select a language of installation process in accordance with 
    your desire.
  * Product license confirmation.
    You have to read a text of the License agreement and confirm it by input of 
    the product license key.
  * System adjustment.
    You make necessary system settings concerning basic functional and service 
    parameters of the System.

The process of Xitex WebContent M1 installation is very easy and clear! 

3.3.2 Preparatory stage

3.3.2.1 Language selection

First of all you should select the language of installation process. The 
required language you can choose in the line: 

  "Please choose the language of installation:"

There you just have to mark the required line in drop-down list. 
Then please press Continue.

3.3.2.2 License agreement

After the language has been chosen Xitex WebContent M1 opens a window to 
license the product.

You should get to know the text of the License agreement. Then you should enter 
the license key given on the label positioned on the backside of installation 
CD. 

If you agree with terms and conditions of the current license agreement, please 
press the button Next. 

3.4 Basic tuning/System adjustment

System will jump to the settings window. Setting procedure consists of some 
functional parts. Entering lines are joined in four groups. Following lines are
in the next groups:

3.4.1 Database settings

In this part are the parameters in accordance with settings were made during 
procedure MySQL installation described in a chapter Prior Installations of the 
manual.

You need to enter data in shown lines.

Server			- address of the database server.
Port			- port of the database server (For MySQL - 3306).
Database name  		- name of the database.
Delete the content 
of database?		- if you place this mark, the database will be cleared.
User name		- name of database user.
User password		- password of database user.

Please verify all the entered data.


3.4.2 System settings

The group of system attributes defines some processes in system working. 

Enter the data:

System language		- language of system interface.
Host of SMTP server	- host of the post server for sending out of messages.
Port of SMTP server	- port of the post server (as a rule, 25).
Maximal number of 
elements in cache	- sizes of system cache (by default, 100). 
                          System cache speeds up the system work, but its 
                          extension reduces free space of system server 
                          memory. 

3.4.3 Waiting

You may to define a time that every user will be out of access to the edited 
page after wrong interruption of this process.

Please remember that: 60 000 ms = 60 seconds = 1 minute. 

Waiting period of the 
blocked page in 
milliseconds		- period when page access was blocked during the 
                          editing was absent. 

3.4.4 Administration

Here are two words or symbol sets for authentication in the system as the system
administrator. Only English alphabet is acceptable. 

Login of the admin	- entrance login of the system administrator. 
Password of the admin	- password for entrance of the system administrator. 
Confirmation of the 
admin's password	- repeated entry of the password. 

3.4.5 After all adjustment settings are entered, click OK. 

System opens a window for authorization of system user. Further actions are 
expounded in other guides. 

If you are the system administrator, for authorization you should enter login 
and password assigned above in parameters of the administrator. 

================================================================================
4. TROUBLESHOOTING FOR INSTALLATION AND CUSTOMIZATION
================================================================================

4.1 During the installation process a system message occurs "Licensing error. 
    Invalid license key entered". 

It means that the License Key you had entered was not found on the 
Registration Server. The most common reason for it is that you've misspelled 
your License Key while installing.

4.2 During the installation process a system message occurs "Can not connect to 
database". 

That could happen due to:
  * You have entered wrong data about the database user account.
  * Database has not been created.
  * You have misspelled the database server's network path.
  * The user you have set has not proper rights for the database access or has 
    not been created.

4.3 During the installation process a system message occurs "Licensing error. 
    Server is unreachable". 

That can happen if the server, which is used for Xitex WebCotent M1 
installation is protected by a firewall. You should check out whether your 
firewall allows this server to transmit TCP packets into the Internet. While 
installing and further work Xitex WebContent M1 uses license data retrieved 
from Registration Servers. So, they should always be accessible.

4.4 After the system installation onto the existing database you can't enter 
    the backoffice. 

That can happen if you have defined new system administrator parameters, 
which are ignored in this case. You should simply enter with the use your 
previous existing system administrator parameters.

4.5 After the system reinstallation onto the existing database you can't get 
    into the system. 

That could happen if you have entered new License Key while reilstallation. You 
should always use the same License Key during the same website management.


================================================================================
5. HOW TO CONTACT US
================================================================================

5.1 E-mail

For contacting us you can use either http://webcontent-m1.com/m1/en/contact_us
or e-mail addresses below:

General questions:       info@xitex.net
Support questions:       support@xitex.net
Newsletter subscription: newsletter@xitex.net
Sales department:        sales@xitex.net

5.2 Tel/Fax

Also feel free to contact our support department by phone/fax:
+380 (62) 305.62.62
+380 (62) 305.62.63
+380 (62) 305.64.44

5.3 Postal address

Our postal address:
XITEX Software
46, Kievskiy avenue, 83054,
Donetsk, Ukraine


--------------------------------------------------------------------------------
(c) Copyright XITEX Software 1999 - 2004. All rights reserved.