Installation Guide
Release Notes

Installing the Asset server

The latest available version of the Unity Asset Server is 2.0.0f4. You can download it from the following locations:

Depending on which platform you are going to install the asset server, follow the steps below:

Installing on Windows

The exe file contains an automated installer. Simply download the installer exe file and execute it to launch the installer. You have to have administrator privileges on the machine to install it.

After installing, you should be able to fire up Unity and use it to create projects and users on the newly installed Asset Server.

Installing on Mac OS X

The disk image contains a simple Apple Installer package file. Simply download and open the disk image and double click on the package file to install it. You need administrator privileges to install the package. The software requires a system reboot after installation.

You should now be able to fire up Unity and use it to create projects and users on the newly installed Asset Server.

Note on upgrading from 1.0.x: Since the Asset Server is now built from a new version of PostgreSQL which is not binary compatible with the version used in 1.0, the installer will have to perform a full dump and restore when upgrading for the first time. If you are upgrading a large installation, the installer postprocessing step might take a while to complete. (A huge installation could take up to a couple of hours.)

During the upgrade, the existing installation will be moved to /Library/UnityAssetServer.bak. The upgrade will require at least the same amount of additional disk space as the size of that folder.

Installing on Linux

Depending on which flavour of Linux distribution you are using, choose one of the options below.

Installing the rpm package

Run the following command on the server:

sudo rpm -Uvh http://download.unity3d.com/asset_server/unity_asset_server-2.0.0.i386.rpm

If this is a new installation, you will also have to supply an initial password for the admin user:

sudo /opt/unity_asset_server/bin/reset_admin_password

When prompted, please supply a new password for the admin user.

You should now be able to fire up Unity and use it to create projects and users on the newly installed Asset Server.

Note on upgrading from 1.0.x: Since the Asset Server is now built from a new version of PostgreSQL which is not binary compatible with the version used in 1.0, the installer will have to perform a full dump and restore when upgrading for the first time. If you are upgrading a large installation, the installer postprocessing step might take a while to complete. (A huge installation could take up to a couple of hours.)
During the upgrade, the existing installation will be moved to /opt/unity_asset_server.bak. The upgrade will require at least the same amount of additional disk space as the size of that folder.

Installing the deb package

Run the following commands on the server:

wget http://download.unity3d.com/asset_server/unity-asset-server_2.0.0_i386.deb
sudo dpkg -i unity-asset-server_2.0.0_i386.deb
If this is a new installation, you will also have to supply an initial password for the admin user:

sudo /opt/unity_asset_server/bin/reset_admin_password

When prompted, please supply a new password for the admin user.

You should now be able to fire up Unity and use it to create projects and users on the newly installed Asset Server.

Note: if you don't have wget installed on the server, you should download the tgz file to your local machine and use some other means to transfer it to the server, such as scp or an ftp client.

You could also simply double-click on the deb file after downloading, if you are running a graphical desktop on the machine.

Installing from source

We recommend that you try installing the rpm first. Should that fail, you can try compiling it yourself from the source tarball. Before attempting the installation please make sure you have the following installed on the server machine:

  • make
  • gcc
  • bison
  • perl

On the server machine, run the following commands as root:

wget http://download.unity3d.com/asset_server/unity_asset_server-2.0.0.tgz
tar xvzf unity_asset_server-2.0.0.tgz
cd unity_asset_server-2.0.0
./install.sh

When prompted, please supply a new password for the admin user.

You should now be able to fire up Unity and use it to create projects and users on the newly installed Asset Server.

Note: if you don't have wget installed on the server, you should download the tgz file to your local machine and use some other means to transfer it to the server, such as scp or an ftp client.

Using the VMware image

Download the image archive. Extension of downloaded file is .vmx.tar.gz.

On Linux and Mac OS X, you can extract it by double clicking on the archive file. You can also run tar xvzf unity_asset_server.i686-2.0.0a1-26422.wmx.tar.gz from the command line.

Windows users must download and install an extraction tool, such as 7-zip. Using 7-zip is a two step process. Uncompressing the .tar.gz file will produce a plain .tar file, which you'll have to unarchive by opening it again in 7-zip.

After extraction you will see a new subdirectory with 2 files: .vmdk and .vmx

You will need the VMware Player (or VMware Fusion on Mac OS X) to start this image.

If this tool is installed, the .vmx should be associated with it and start with one click.

When the appliance is started, log into it as root. The default password for root is unity. Reset the Asset Server admin password:

/opt/unity_asset_server/bin/reset_admin_password

You should also change the root password to something different:

passwd root

By default, the appliance is configured to use dhcp to configure the IP address. You can find the current IP address in the output from running ifconfig. If you want to change the network setup, please read section 20.6, Configuring a Network Connection Manually in the openSUSE 11.1 Reference Guide

Firewall configuration.

In order to connect to the asset server, Unity has to be able to connect to TCP port 10733 on the server. Please consult the documentation for your operating system or firewall on how to accomplish this.

If you use APF to manage firewall settings on the server machine, the rpm and source installs will automatically open up port 10733 when installed.

If you use the built-in Windows or Mac OS X firewalls, the port will be automatically opened during installation.