Step 2. In the ELVIS_URL option, define the URL of the Elvis Server to connect to.

define('ELVIS_URL', 'http://localhost:80');

Notes:

The URL is typically 'localhost' (if Elvis and Enterprise are running on the same machine), or the internal IP address of the Elvis Server.

The URL should not end with a trailing slash.

Step 3. Save the file.

2. Setting up data synchronization from Enterprise to Elvis

Whenever an asset is updated in Elvis (such as updating its metadata, opening it in an external editor, or deleting it), Enterprise users need to be made aware of this. Similarly, when an Enterprise user makes a change to an asset, this needs to be communicated to the Elvis users.

This communication is provided through a script named sync.php that runs on Enterprise Server using cURL. It is a long-polling PHP script which periodically checks the Elvis Server for asset updates.

Once an asset update is received it is applied directly to the corresponding Enterprise shadow object.

Note: This script can be run simultaneously on multiple application servers. This is because the script is semaphore protected: only one sync.php file is executed to perform the synchronization even when many are installed and called.

Setting up cURL

The script is executed on Enterprise Server by using cURL.

Installation is done as follows:

For Mac OS X and Linux: cURL is pre-installed on these systems, no installation steps are necessary.

Enterprise Admin user name and password, needed for synchronizing metadata
between Elvis and Enterprise. By default a user which is used which is known in both
systems with the same credentials.

Step 3. Save and close the file.

3. Defining how Elvis assets are used in Enterprise

An asset that is stored in Elvis can be used in Enterprise in one of the following ways:

As a shadow object that is created in Enterprise and that is linked to the asset in Elvis (default setting). Only when the Elvis file needs to be worked on is the original file — together with the file preview, thumbnail, metadata and versions — retrieved from Elvis and stored on the local system of the user.

As a copy that is created in Enterprise and that is not linked to the original in Elvis.

As a variant: a copy that is stored in Elvis and linked to a shadow object in Enterprise. The variant is also linked to the original image, thereby making it possible to see the original asset and all its variants. Variants are stored in a dedicated folder in Elvis, known as a 'Production Environment'. Multiple Production Environments can be set up, one for each Brand / Category combination. This makes it possible to use the same asset across different Brands.