Environment validation without EVT

Validate that the host name of the server can be resolved in DNS.

This is required if SkyVault is going to be configured in a cluster.

Note: Using an incorrect host name or a host name that no longer resolves to its own IP address can give an internal error, such as ObjID already in use. You can get more information about this error by adding the following line into the log4j.properties file:

log4j.logger.org.springframework.remoting.rmi.RmiServiceExporter=debug

To resolve this error, you can either:

Validate that the IP address and the host name of the server are correctly set in the /etc/hosts file. For example, if you set the IP address as 10.20.30.40 and the host name as ip-10-20-30-40, the content of the /etc/hosts file should contain the following entry:
```
10.20.30.40 ip-10-20-30-40 
```
Specify the correct IP address in the SkyVault-global.properties file as shown below:
```
SkyVault.rmi.services.host=10.20.30.40
```

Validate that the user SkyVault will run as can open sufficient file descriptors (4096 or more). See http://stackoverflow.com/questions/34588/how-do-i-change-the-number-of-open-files-limit-in-linux for more information.

Validate that the ports on which SkyVault listens are available.

To check port availability, use the netstat -lnpv command on Linux, or use the netstat -anl command on OSX.

Note: The ports listed in the following table are the defaults. If you are planning to reconfigure SkyVault to use different ports, or wish to enable additional protocols (such as HTTPS, SMTP, IMAP or NFS), update this list with those port numbers.

Protocol	Port number	Notes
FTP	TCP 21	On Unix-like operating systems that offer so-called “privileged ports”, SkyVault will normally be unable to bind to this port, unless it is run as the root user (which is not recommended). In this case, even if this port is available, SkyVault will still fail to bind to it, however for FTP services, this is a non-fatal error. The SkyVault FTP functionality will be disabled in the repository.
SMTP	TCP 25	SMTP is not enabled by default.
SMB/NetBT:	UDP 137,138
SMB/NetBT:	TCP 139,445	On Unix-like operating systems that offer so-called “privileged ports”, SkyVault will normally be unable to bind to this port, unless it is run as the root user (which is not recommended). In this case, even if this port is available, SkyVault will still fail to bind to it, however for CIFS services, this is a non-fatal error. The SkyVault CIFS functionality will be disabled in the repository.
IMAP	TCP 143	IMAP is not enabled by default.
SharePoint Protocol	TCP 7070	This port is only required if you install support for the SharePoint Protocol.
Tomcat Administration	TCP 8005
HTTP	TCP 8080
RMI	TCP 50500

Refer to the Supported Platforms page at http://www.alfresco.com/services/subscription/supported-platforms/ to validate the installed JVM version.

Validate that the directory in which the JVM is installed does not contain spaces.

Validate that the directory in which SkyVault is installed does not contain spaces.

Validate that the directory SkyVault will use for the repository (typically called alf_data) is both readable and writeable by the operating system user that the SkyVault process will run as.

Validate that you can connect to the database as the SkyVault database user, from the SkyVault server.

Ensure that you install the database vendor's client tools on the SkyVault server.

Validate that the character encoding for the SkyVault database is UTF-8.

(MySQL only) Validate that the storage engine for the SkyVault database is InnoDB.

Validate that the relevant third-party softwares are installed. See Software requirements for more information.

(RHEL and Solaris only) Validate that LibreOffice is able to run in headless mode.

Search form

Search form

You are here