Alfresco-Ingres Installation Bundle for Ingres 2006 Release 3 on Linux

1.0 Welcome

2.0 System Requirements

3.0 Installation Considerations
3.1 Installing the Alfresco-Ingres Installation Bundle
3.2 Uninstalling the Alfresco-Ingres Installation

4.0 Configuring Your Ingres Installation
4.1 Ingres Online Documentation References

5.0 Known Issues
5.1 Ingres Related Issues
5.2 Operating System Related Issues
5.3 Alfresco Related Issues

6.0 Contacting the Community

1.0 Welcome

Welcome to the "Alfresco-Ingres" installation. The installation bundle contains the Alfresco 2.1. and the Ingres 2006 Release 3 community editions for Linux environments.

This readme contains important information about the installation of Ingres with Alfresco using the installer provided by Ingres Corporation. This readme also describes how to contact the Ingres community and provides strategic references to the Ingres documentation. For more information, please visit the Ingres website at http://ingres.com/.

2.0 System Requirements

To install Ingres and enable a satisfactory Alfresco ECM environment, the following minimum requirements must be met:

• On installations with less than a 256 MB shared memory segment, Ingres will fail to start and the Alfresco database will not be created. To avoid this problem, use the following values:

  kernel.shmall = 2097152
  
  kernel.shmmax = 2147483648
  

• The minimum disk space required for an evaluation installation that will provide a usable amount of space for Ingres and Alfresco to install, and for user content to be loaded is 5 to 10 GB. No recommendations are provided for a production environment as the requirement will depend on the individual needs of the organization.

3.0 Installation Considerations

The following tools or packages must be installed with your Linux distribution.

Development tools required:

• gcc

Notes:

• The gcc tool is required for this Alfresco-Ingres bundle, which is shipped with the Ingres Community edition ii9.2.0(int.lnx/118) NPTL. The gcc tool is not required with Ingres ii9.2.0(int.lnx/127) NPTL.

3.1 Installing the Alfresco-Ingres Installation Bundle

To install in Linux environments

1. Log on to your system using the user account that will own the installation.

2. Download the self-installing installation image Ingres-Alfresco-2.1.0-5-linux-installer.bin.

3. Change to the directory that the installer was downloaded to:

   cd /home/user_account
   

4. Depending on the operating system, you may have to change the properties of the file using the following command:

   chmod 777 Ingres-Alfresco-2.1.0-5-linux-installer.bin
   

5. Start the installation by running the self-installing image:

   ./Ingres-Alfresco-2.1.0-5-linux-installer.bin
   

6. Follow the steps provided by the installation wizard.

7. Start the installation:

   1. Change to the root directory where the Alfresco-Ingres files were installed. Assuming the current user directory, issue the following command:

      cd /home/user_account/Ingres-Alfresco-2.1.0.5
      

   2. Start the Alfresco-Ingres installation using the control script, which starts Ingres first, and then Alfresco:

      sh ctlscript.sh start
      

   Starting the Alfresco-Ingres installation the first time initializes the Alfresco environment. Startup may take several minutes depending on the server.

Notes:

• The included Tomcat application container is configured to use the connection port 8080 by default. If other servers are running on this port, an optional screen is displayed that must be completed to enable the installer to continue using user-defined ports.

  In addition, Tomcat control ports must also be manually configured. By default, these are 8005 and 8009.

• The included Alfresco application container is configured to use an integral FTP service on connection port 2121 by default. If this port is not available, an optional screen is displayed that must be completed to enable the installer to continue using a user-defined port.

• Alfresco requires a port itself. To have more than one Alfresco installation on one machine, each installation requires its own RMI port. The included Alfresco application container is configured to use the RMI connection port 50500 by default. If this port is not available, an optional screen is displayed that must be completed to enable the installer to continue using a user-defined port.

• By default Ingres is configured to use the installation identifier AF. If there is already an Ingres installation using this identifier, choose an alternative identifier during the installation.

3.2 Uninstalling the Alfresco-Ingres Installation

The Alfresco-Ingres installation can uninstalled by shutting down the installation and deleting the installation's root directory and installed files.

A script named "uninstall" is provided for this purpose in the installation root directory.

To uninstall manually

1. Log on to your system as the user that owns the installation.

2. Change to the installation directory:

   cd /home/user_account/Ingres-Alfresco-2.1.0.5
   

3. Stop your installation.

   sh ctlscript.sh stop
   

4. Change to one directory above the installation directory and install directory:

   cd..
   
   rm –rf Ingres-Alfresco-2.1.0.5
   

Notes:

• Stopping the installation may take a few minutes. Before removing the directory we recommend that you make sure that the installation is stopped. This command will return an empty list of processes:

  ps –elf | grep '<'  | grep –v 'grep'
  

4.0 Configuring Your Ingres Installation

The Alfresco-Ingres installation has been configured and installed for evaluation purposes. If you want to use your Ingres installation for production, some configuration changes—especially those related to the number of available locks on database objects—may be necessary. Further details can be found in the Ingres online documentation.

4.1 Ingres Online Documentation References

Links to relevant Ingres configuration details in the online documentation are provided here:

http://docs.ingres.com/dba/UnderstandingtheLockingSystem
http://docs.ingres.com/cmdref/cbfCommandStartConfigurationByForms
http://docs.ingres.com/sysadm/ConfiguringIngres
http://docs.ingres.com/sysadm/LockingSystemConfiguration

5.0 Known Issues

Issues identified during the testing of the Alfresco-Ingres installation bundle are documented here.

5.1 Ingres Related Issues

• If Ingres is using the UTF8 character set, the maximum size of text (varchar, byte varying, ...) columns is 16K instead 32K. The Alfresco repository database was adapted to take this into account.

• Ingres installation fails because of issues related to re-linking the server if using the latest version of Ubuntu. Later versions of Ingres 2006 Release 3 do not require the server to be re-linked.

5.2 Operating System Related Issues

• Shared memory should be configured to have approximately 256 MB of memory available. Tests with Ubuntu show that it is configured for less than 256 MB by default. In this case, the kernel parameter shmmax should be set to a minimum 268435456 bytes of shared memory.

5.3 Alfresco Related Issues

• Alfresco comes with its own JAVA-implemented FTP and CIFS server. It has been reported that they are not working out of the box if your machine already runs an FTP server, a CIFS/Samba-server, a firewall, or the user that starts the installation does not have enough permissions to bind the related ports.

6.0 Contacting the Community

For online technical assistance from our community, please visit http://community.ingres.com , where you can find Forums, the Ingres Community Wiki, contacts, and mailing lists.