Check if your preferred environment is supported by Alfresco. A support stack list is available on www.alfresco.com.

Validate the hardware in terms of the CPU and I/O subsystems. This will help ensure a good response time.

Tune your database. Alfresco does not provide support to tune and maintain your database. It will have to be carried out by the Database Administrator at your end.

Ensure your OS is on the Alfresco Support Stack list.

Tune JVM and verify that it is certified to be used with your Alfresco.

Check that the server host name can be resolved in DNS.

Validate the listening ports and the JVM Version. JVM 1.6 is the required version.

Check the directory names for spaces.

Check the read and write properties of the directory that will be the Alfresco Repository.

Verify the database connections. Validate that the character encoding for the Alfresco database is UTF-8.

Ensure that the MySQL storage engine for Alfresco is InnoDB.

If you plan to install third-party tools such as OpenOffice and ImageMagick separately, ensure that you have the appropriate versions. OpenOffice needs Version 3.1 or newer and ImageMagick Version 6.2 or newer.

Double-click on the downloaded file. Under the Setup Alfresco Enterprise window, click on Next.

Select the installation language, as shown in the following screenshot. This sets the language to be used for the remainder of the installation wizard:

In the Installation Type window, you can choose either of the following options:

The default installation type option is Easy; click on Next, as shown in the following screenshot:

In the Select Components window, select the components that you want to install. You can select from the following list of components:

These are depicted in the following screenshot:

The following components are installed by default and you cannot deselect them:

Once you have selected the options to install, click on Next.

In the Database Installation window, you can choose to use the bundled PostgreSQL database, which is installed with Alfresco, or use an existing database instance. Choose the bundled PostgreSQL database, and then click on Next.

In the PostgreSQL Credentials window, type a root password for the bundled PostgreSQL database. Confirm the password.

In the Admin Password window, type a password. Repeat the password, and then click on Next. This sets the password for the Alfresco Administrator user account (admin), as shown in the following screenshot:

If you are installing the Quickr Connector Support component, the Quickr Content Services window will be displayed. Enter the host and port details for your Quickr server, and then click on Next. For example, the default is localhost and the port number is 6060. These settings are added to the configuration file for Quickr. This is optional.

Under the Ready to Install window, click on Next; the Installing window is displayed showing the progress of the installation.

Under the Completing the Alfresco Enterprise Setup Wizard window, click on Finish, as shown in the following screenshot. By default, when you click on Finish, the Readme file will be displayed, click on OK:

Log on to Alfresco Share as the admin user. Enter the password that you specified in the Admin Password window. The Alfresco server is launched automatically as a Windows service.

In order to manage the server, open the Control Panel Services window. The services that must be running for Alfresco are as follows:

If you did not automatically launch Alfresco at the end of the installation wizard, to start Alfresco you need to start all three services. Use the servicerun start script in the installation directory. Alternatively, select All Programs | Alfresco Enterprise | Alfresco Enterprise Service | Start Alfresco Enterprise Service.

In order to stop Alfresco completely, you must stop all three services. Use the scripts in the installation directory to start or stop the services: servicerun start and servicerun stop.

On the Setup Alfresco Enterprise window, click on Next.

On the Installation Type window, choose how you want to use the setup wizard. There are two types of installation in the setup wizard: Easy, with the default options and configurations; and Advanced, where you can set the ports and choose the components to be installed, and configure service properties. For the Easy setup:

In order to complete the Advanced setup wizard, select Advanced, and then click on Next. Follow the steps mentioned here to complete the installation with the Advanced option.

On the Select Components window, select the components that you want to install. Deselect the components that you do not want to install.

You can select from the following components:

You cannot deselect the Alfresco component because it is installed by default; click on Next.

The Database Server Parameters window prompts you to enter a port number for your database.

Under the Tomcat Port Configuration window, enter the following Tomcat configuration parameters:

Default values for each of these are given.

Now enter the port number for the Alfresco FTP server, RMI service.

To set the password for the Alfresco Administrator user account, on the Admin Password window, type a password. Repeat the password, and then click on Next.

Optionally, if you are installing SharePoint Protocol Support, Quickr Connector Support component, or the OpenOffice component, enter the relevant details of the ports and servers.

On the Service Startup Configuration window, you are presented with two options for starting up the Alfresco services. These are:

Select the services start up option, and then click on Next.

Click on Next under the Ready to Install window. The Installing window displays, showing the progress of the installation.

On the Completing the Alfresco Enterprise Setup Wizard window, click on Finish. By default, when you click on Finish, the Readme file will be displayed; click on OK.

The Alfresco server starts and then Alfresco Share launches in your default browser.

Log on to Alfresco Share as the admin user. Enter the password that you specified in the Admin Password window.

The Alfresco server is launched automatically as a service named alfresco. This service comprises the following individual services:

If you did not automatically launch Alfresco at the end of the setup wizard, to start Alfresco, you need to start all the services. Manually start the Alfresco server: service alfresco start. To start only the Tomcat service: service alfresco start tomcat.

In order to fully stop Alfresco, you must stop all the services: service alfresco stop.

Download the Tomcat Version 6.0.26 from http://tomcat.apache.org. Install Tomcat by following the instructions included in the release.

Create the directories required for an Alfresco installation:

Open the<TOMCAT-HOME>/conf/catalina.properties file and change the value of the shared.loader property to the following:

shared.loader=${catalina.base}/shared/classes,${catalina.base}/shared/lib/*.jar

If you have used alternative names for the directories, you must specify these names in the shared.loader property.

Copy the JDBC drivers for the database you are using to lib/.

Edit the<TOMCAT_HOME>/conf/server.xml file. Set the character encoding to UTF-8 on the Tomcat connector. By default, Tomcat uses ISO-8859-1 character encoding when decoding URLs that are received from a browser. This may cause problems when creating, uploading, and renaming files with international characters.

Locate the Connector section, and then add the URIEncoding="UTF-8" property, as follows:

<Connector port="80" protocol="HTTP/1.1" URIEncoding="UTF-8" connectionTimeout="20000" redirectPort="8443" />

Save the server.xml file.

Browse to the Alfresco Enterprise download area, and download the alfresco-enterprise-3.4.3.zip and specify a location for the download.

Extract the WAR file. The WAR bundle will extract into the following directory structure:

The WAR bundle also contains the README.txt file. The following table shows files that are contained within the suggested subdirectories for the Tomcat application server:

Install a new Tomcat instance.

Modify the /conf/server.xml file for the new Tomcat instance as follows:

Change the port number in the line:

<Server port="<server port number>" shutdown="SHUTDOWN">

Change the port number in the section:

<!-- Define a non-SSL HTTP/1.1 Connector on port 8080 -->
<Connector port="<connector port number>">"...>

Move the share.war file from the original Tomcat webapps directory to the new Tomcat /webapps directory.

Start the original Tomcat using the Alfresco supplied batch files.

Check that a copy of the commons-el.jar file is in the Share Tomcat lib directory.

If you are running the Share Tomcat on a separate machine, modify the override file in the Share Tomcat web-extension directory, as follows:

Save the file without the .sample extension.

Start the new Share Tomcat. You can use copies of the Alfresco supplied batch files, or your own methods.

Download the latest (stable) version of OpenOffice for your platform from http://download.openoffice.org.

When prompted, specify a download destination. Browse to the location of your downloaded file, and install the application.

A wizard guides you through the installation.

Accept the license agreement, and then click on Next.

Enter customer information as appropriate, and then click on Next.

Select Setup type as Custom, and then click on Next, as shown in the following screenshot:

Change the installation directory to:

Optionally, select the files for which you want OpenOffice to be the default application, and then click on Next, as shown in the following screenshot:

Start one of the OpenOffice programs for the initial registration, and then close the program.

Modify the ooo.exe property in the<classpathRoot>/alfresco-global.properties file to point to the OpenOffice binary office.exe.

For Windows, set the path using the \ separator or use the forward slash (/) Unix path separator. For example: c:\Alfresco\OpenOffice\soffice.exe, or c:/Alfresco/OpenOffice/soffice.exe.

For Solaris, ensure that the<configRoot>/classes/alfresco/subsystems/OOoDirect/default/openoffice-transform-context.xml file can start.

Remove the quotes from the connection string values:<value>-accept=socket,host=localhost,port=8100;urp;StarOffice.ServiceManager</value><value>- env:UserInstallation=file:///${ooo.user}</value>.

If the Alfresco server is running, [stop and start], or restart the server.

Verify if ImageMagick is already installed on your system by running the convert command, which is part of ImageMagick and usually located in /usr/bin (on Linux).

If ImageMagick is not installed on your system, browse to the ImageMagick download site and install the appropriate package for your platform.

Modify the img.root and img.exe properties in the<classPathRoot>/alfrescoglobal.properties file to point to the ImageMagick root directory. For example, on Windows:

For Linux:

Ensure that you do not include a slash (/) at the end of the path, for example, /ImageMagick/.

Browse to the Alfresco Community Edition download area.

Run the Microsoft setup file: alfresco-community-office2003-addins-3.2.zip.

This example refers to the Office installer that installs all three Add-ins. You can also use individual installers to add Alfresco to one of the three Office applications. These individual installers are as follows:

Run setup.exe.

If required, the setup program will download the required components from the Microsoft website. These components are .NET 2.0 framework, and Visual Studio 2005 Tools for Office Second Edition runtime. The setup is complete.

Run the Office application, for example, Word.

A Welcome window with configuration options displays. You can return to the configuration options at any time using the link at the bottom of the Add-In window.

In the Web Client URL field, enter the location of Alfresco Explorer, for example, http://server:8080/alfresco/.

In the WebDAV URL field, append webdav/ to the Alfresco Explorer URL, for example, http://server:8080/alfresco/webdav/.

In the CIFS Server field, enter the path to the CIFS server. The add-in will try to autocomplete this value, but you should verify it for the correct address, for example, \server_aalfresco or \serveraalfresco.

If you intend to use the CIFS interface to save documents through the add-in, it is very important that you are authenticated automatically. Limitations in the Microsoft Office APIs mean that an error is shown instead of an authentication dialog box, if the Alfresco CIFS interface rejects your connection attempt. If you are not in an enterprise environment, where it may not be possible to configure automatic authentication, you can map a network drive to the Alfresco CIFS interface instead.

In the Authentication area, enter your Alfresco username and password.

The add-in will always try to automatically log you into Alfresco in order to present your checked out documents (that were checked out) and your assigned tasks. If you are using the CIFS interface, authentication is usually automatic. However, sometimes the add-in needs to present your Alfresco username and password for authentication. It is recommended that you enter, and save, your Alfresco credentials. All values are stored in the Windows registry and your password is encrypted against casual hacking attempts.

Click Save Settings.

Browse to the Adobe Flash Player download website: http://www.adobe.com/products/flashplayer.

Download the latest (stable) version of Flash Player for your platform.

Browse to the location of your downloaded file and install the application. A wizard guides you through the installation.

When the installation is complete, click Close.

Browse to the TinyMCE website: http://tinymce.moxiecode.com/download_i18n.php and download the required TinyMCE language pack.

Unpack the language file:

Ensure that the browser cache is cleared.

Browse to the /bin directory:

Run the following command:

java -jar alfresco-mmt.jar install <AMPFileLocation> <WARFileLocation>[options]

Please specify the option in the preceding command as per the details mentioned in the following table. The various options for the same are also listed:

This command installs the files found in the AMP into the Alfresco WAR. If the module represented by the AMP is already installed and the installing AMP is of a higher release version, then the files for the older version are removed from the WAR and replaced with the newer files. The following commands show examples of how to install the example-amp.amp, and assumes that the AMP file is in the same directory as the WAR file:

java -jar alfresco-mmt.jar install example-amp.amp alfresco.war - preview

Review the modification to check the changes that will update any existing files.

The following example will install the AMP file:

java -jar alfresco-mmt.jar install example-amp.amp alfresco.war - verbose

The modified Alfresco WAR can then be redeployed back into your application server. On restarting the application server, the console will show that the custom class was initialized during the startup.

Verify that the AMP is installed using the MMT list command. For example:

java -jar alfresco-mmt.jar list <WARFileLocation>.

This command provides a detailed listing of all the modules currently installed in the WAR file specified. When the repository is now started, the installed module configuration will be detected. The repository will now be bootstrapped to include the new module functionality and data. It is not recommended that you overwrite an existing file in an AMP unless necessary.

The MMT makes a backup copy of the updated file and stores it in the WAR. When an update of the module occurs and the old files are removed, this backup will be restored prior to the installation of the new files. The alfresco.war file is backed up and the copy is stored in a new file named alfresco.war.bak in the same directory as that of the original .war file.

Go to the URL: http://sourceforge.net/projects/alfresco. Click on Download to display the available Alfresco Content Management downloads.

Locate Firefox extension and click on Download. Click on the link alfrescoext-0.91.xpi.

In the list of download sites, click on Download for the site nearest to you. Allow permission to install the extension.

Shut down your Alfresco server.

Browse to the download area and download the vti-module.amp file.

Move the file to the amps directory.

Install the vti-module.amp file into the alfresco.war file using the Module Management Tool (MMT). The vti-module.amp file holds the functionality for the SharePoint connector. For Tomcat, alternatively, run the apply_amps.bat command, which is in the root Alfresco directory. This batch file applies to all the amps that are located in the amps directory.

Start your Alfresco server to expand the directory structure.

Verify that you have applied the SharePoint AMP to Alfresco by checking that you have the following directory:

/webapps/alfresco/WEB-INF/classes/alfresco/module/org.alfresco.module.vti/context.

Open the alfresco-global.properties file.

2 Add the following properties:

vti.server.port=7070
vti.alfresco.deployment.context=/alfresco
vti.alfresco.alfresoHostWithPort=http://your-host:8080
vti.share.shareHostWithPort=http://your-share-host:8080

The following table describes the properties:

The vti.properties file in <TOMCAT_HOME>/webapps/alfresco/WEB-INF/classes/alfresco/module/org.alfresco.module.vti/context contains the full list of properties.

Do not change the properties in this file; use only the alfresco-global.properties file.

Save the alfresco-global.properties file.

Restart your Alfresco server. The Microsoft SharePoint Protocol Support functionality is installed and configured.

Go to the<classpathroot> directory.

Open the alfresco.global.properties.sample file. To make modifications, remove the comment character #.

Include a root location for storing content binaries and index files in the dir.root property, for example, dir.root=C:/Alfresco/alf_data.

Now set the database connection properties.

Other database properties can also be configured. The other tools and software that are configured with Alfresco also need to have their location specified. This can also be done in the alfresco-global.properties file.

The properties for the database are grouped into sections for various databases such as MySQL, Oracle, SQL Server, and PostgreSQL.

Uncomment the db.driver and db.url properties for the database that you require.

Select a JDBC driver used with the connection type.

Now add the global custom configurations.

Save your file without the .sample extension.

Restart your Alfresco server for the configuration changes to take effect.

Open a command prompt.

To install Alfresco as a Windows service, enter the following commands (we assume here that Alfresco is installed at c:alfresco for Tomcat 6):

cd c:alfresco	omcatin
service.bat install alfresco
tomcat6 //IS//Tomcat6 --DisplayName="Alfresco Server" 
--Install="C:Program FilesTomcatin	omcat6.exe" -Jvm=auto 
--StartMode=jvm --StopMode=jvm 
--StartClass=org.apache.catalina.startup.Bootstrap -- StartParams=start 
--StopClass=org.apache.catalina.startup.Bootstrap --StopParams=stop

To edit your service settings, enter the following commands (for Tomcat 6):

cd c:alfresco	omcatin
tomcat6w.exe //ES//alfresco

Locate the service named Alfresco Server in the Services panel.

Start the Alfresco Server service. You can uninstall the service using the following commands: