WoodWing Help Center

Installing Elvis 4 Server

Installing Elvis 4 Server

On Windows or Mac OS X

The Elvis installer makes it easy to set up and configure a basic Elvis environment. This is done in a few short steps. To install the server you need to be logged in with an administrator account.

Before starting the installer:

  • Read the system requirements.
  • Read the articles about server administration. Some of them may be applicable to your situation.

Next run the Elvis installer and follow the on-screen instructions.

  • On Windows:
  • The Elvis data folder will be used to store all the data (originals, thumbnail, search index etc.)
  • Change the server port when the default port is already in use.
  • After the installation open the Elvis server entry in the windows Start Menu.
  • From here you can view the config, logs and documentation and stop and start the server.
  • You can also stop and start the Elvis server form the windows Services management console.
  • On Mac OS X:
  • After the installation open your Applications folder and double-click the Elvis server icon. This will open the Elvis server launcher.
  • From here you can view the config, logs and documentation and stop and start the server.

Next license your installation and then start or restart the Elvis server.

To check if Elvis has started up correctly, view the log files or connect to the server by installing the Elvis desktop client.

  • You can log in using the default admin user with password changemenow, make sure to change the password in the internal user properties.

You can monitor server operation using the Server Status page.

Note: To enable e-mail notifications on the sharing functionality added in Elvis 3.6.1, you need to configure serverAdminEmail in the config.properties.txt

Installing demo content

To ease setting up a demonstration of Elvis, the server installer comes with a package of demo content. This content pack has examples of different types of media, like text, video and images. When you perform a clean installation of Elvis, the installer will allow you to fill your server with this initial set of demo content.

On Linux

This article describes how to use the Linux (processing) server installer and the way it operates on a minimal install of CentOS 6.3/6.4 or RHEL 6. It may work on other systems that use SysVInit as init script system, but they are currently not supported.

Notes:

  • A 64-bit system is mandatory. 32-bit systems are not supported, the server will not start on 32-bit systems.
  • Not all file types are supported when using a Linux (processing) server. For an overview, see Supported file types.

Installing

Download the installer archive to a directory on the server and unpack it.

$ bzip2 -d elvis-x.x.x.x(-processing)-server-linux.bin.bz2

Starting the installation

The decompressed file is an installation script with a binary payload. Run it as root by either making it executable or running it through sh.

# chmod +x elvis-x.x.x.x(-processing)-server-linux.bin

# ./elvis-x.x.x.x(-processing)-server-linux.bin

or

# sh elvis-x.x.x.x(-processing)-server-linux.bin

This will show you the "usage information" for the installer. The (processing) server can either be installed in interactive or in silent mode. When running the installer interactively, you will be asked for configuration properties during installation. Running the installer in silent mode will cause the installer to use configuration parameters defined on the command line or use the default values for any parameters not defined explicitly.

Installation process

Make sure you read the usage information, which is shown by running the installer without any arguments or with -h. The installation is straightforward, just check the usage information for any configurable options and run the installer in silent or interactive mode.

Warning: Do not install Demo data if you intend to place the elvis-data and/or elvis-hot-data folders into locations which you intend to mount but have not done yet.

The installer will show progress information while it is running.

Extracting APP payload to /srv/elvis-server... [ OK ]

Extracting CONFIG payload to /srv/elvis-server... [ OK ]

Extracting INIT_SCRIPT payload to /etc/rc.d/init.d... [ OK ]

Extracting WRAPPER_CONF payload to /srv/elvis-server/app/wrapper/conf... [ OK ]

Extracting POSTGRES_CONF payload to /srv/elvis-server/app/tools/linux/postgres/share... [ OK ]

When successful, the status will show [ OK ] for all payloads. Otherwise, you'll see them listed as [ FAIL ] with the cause. Make sure you run the installer as root, or all will fail.

Final steps

There are some final steps you need to perform before the server can be used.

License file

To be able to run the server, you'll need to put a valid license file into the server's config directory. This is located at /srv/elvis-server/config. You can do this using scp for example, as follows.

scp /path/to/license.lic root@hostname:/srv/elvis-server/config/

This step is really up to the system administrator though, as Linux installations differ.

Mounting file systems

It is possible to mount file systems at the locations selected during installation for the Elvis data. This is something that should be done by a system administrator that knows how to work with *NIX mount commands. How to do that depends on your system and is out of scope for this article.

Configuring the firewall

The port selected during installation should be opened in your firewall configuration. How to do that depends on your system and preferences, so it is out of scope for this article to explain. (On CentOS, you can install system-config-firewall-tui to get an ncurses configuration tool).

Starting the (processing) server

Note: If you don't have Perl installed by now, it should be installed before doing anything else. Without Perl, the server will not be able to extract and embed metadata.

The installer will have placed an initscript in /etc/init.d/elvis(-processing)-server. You can now start/stop/restart the server using service.

service elvis(-processing)-server start

service elvis(-processing)-server stop

service elvis(-processing)-server restart

Monitor the files in /var/log/elvis(-processing)-server to see if the server is properly starting.

Start server at system boot

It's possible to automatically start the (processing) server when the system boots by running:

chkconfig elvis(-processing)-server on

to turn it off again, use:

chkconfig elvis(-processing)-server off

Disable scheduled cleanup of var/tmp

Some Linux versions may clean the var/tmp folder which may result in server failures. To prevent this, use one of the following methods:

 

File system layout

Described below is the server's file system layout.

/srv/elvis-server/

app/

config/

config.properties.txt

ldap-config.properties.txt

logging.properties.txt

... other config files

license.lic (should be placed here before starting the server)

elvis-data/ (default location)

elvis-hot-data/ (default location)

/var/log/elvis-server/ (log files, monitor these to see what's happening)

/var/tmp (important files needed by server, written when server is running)

And the processing server's layout:

/srv/elvis-processing-server/

app/

config/

config.properties.txt

logging.properties.txt

/var/log/elvis-processing-server/ (log files, monitor these to see what's happening)

/var/tmp (important files needed by server, written when server is running)

Was this article helpful?
0 out of 0 found this helpful / Created: / Updated:
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.