Installation Guide > Harmony Installation Guide > Installing on Linux > Configuring Harmony to Share Scene Data
Download Toon Boom DocumentationDownload Documentation

Configuring Harmony to Share Scene Data

This section shows how to share the Harmony data for different network configuration.

Related Topics 

Export Harmony Directories for Mac OS X and Linux Clients
Configure the Link Server
Configure Samba

Export Harmony Directories for Mac OS X and Linux Clients

Before you can install Harmony on Linux clients, you must export the Toon Boom Harmony directories from the server. The NFS and NFS locking services must be running so that all machines can access the data directories you export.

To start NFS services and export data directories from the server:

1. To share files with other Linux machines, you must start the NFS service. Type the following in a shell:

/etc/init.d/nfs restart

/sbin/chkconfig nfs on

Note that if you are using Fedora 16, this would be:

systemctl start nfs-server.service

/sbin/chkconfig nfs-server on

2. The NFS lock manager must run on all Linux stations on your network. Without this service, they will not be able to access the database without receiving numerous "read lock"  error messages. Type the following in a shell:

/etc/init.d/nfslock restart

/sbin/chkconfig nfslock on

Note that if you are using Fedora 16, this would be:

systemctl start nfs-lock.service

/sbin/chkconfig nfs-lock on

Now you are ready to export the Toon Boom Harmony directory.

3. Use a text editor to edit the /etc/exports file. Add the names of /USA_DB,
/usadata000 and /usr/local/ToonBoomAnimation/harmony_10.0 directories to the file, like this: #

/USA_DB *(rw,sync)

/usadata000 *(rw,sync)

/usr/local/ToonBoomAnimation/harmony_10.0 *(rw,sync)

4. Run the export command to finalize the exports. In a shell, type:

/usr/sbin/exportfs -r

5. To check what is being exported from the server, type the following in a shell:

/usr/sbin/showmount --exports

A report appears listing all of the shares that are being exported from the server.

Configure the Link Server

If you are running Harmony in a mixed environment where the server is on Fedora Linux and some of the clients are running Windows, you must start the Link Server.

The Link Server makes it possible for Windows machines to communicate with the database.

To configure the Link Server on the server in a mixed network environment:

1. Use a text editor to create the Link_srv.conf file in the /USA_DB directory. This file must contain the following two lines:

hostname harmonyserver

port 5679

Replace harmonyserver with the name of the database server. You can find the name of a computer by using the uname -n command.

Note: you can find the example of Link_srv.conf under /usr/local/ToonBoomAnimation/harmony_10.0/resources/samples/. You can copy and paste it from there and change it accordingly.

2. Change the permissions on the Dbserver.conf file to 644. In a shell, type the following:

chmod 644 Link_srv.conf

3. Start the Link Server. Type the following in a shell:

/etc/init.d/USAnimation_link_srv start

A message will appear in the shell indicating that the script has been successful.

4. A log file will be generated in /tmp/Link_srv.log. Check this file to make sure there are no errors written to this file.

Configure Samba

Finally, you must modify the /etc/samba/smb.conf file. To do this, add entries for each database directory you want to share with Windows clients in the /etc/samba/smb.conf file. Then, you must add options to the [Global] section of the file.

Configure the Samba Service to Start at Boot Time
Configure the server.ini File
Reboot
Set Up Linux Clients
Install Start Application Menu Entries and Batch Processing on Clients

Following is an example of entries in the smb.conf file. You can add these to the end of the smb.conf file.

[USA_DB]

comment = Toon Boom Harmony Database

browseable = yes

read only = no

guest ok = no

create mask = 0777

directory mask = 0777

path = /USA_DB

[usa]

comment = Toon Boom Harmony binaries & stuff

browseable = yes

read only = no

guest ok = no

create mask = 0777

directory mask = 0777

path = /usr/local/ToonBoomAnimation/harmony_10.0

[usadata000]

comment = Toon Boom Harmony data 000

browseable = yes

read only = no

guest ok = no

create mask = 0777

directory mask = 0777

path = /usadata000

[usadata001]

comment = Toon Boom Harmony data 001

browseable = yes

read only = no

guest ok = no

create mask = 0777

directory mask = 0777

path = /usadata001/

You must also either add or modify the following entries to the [Global] section of smb.conf:

[global]

encrypt passwords = no

 

blocking locks = no

oplocks = no

level2 oplocks = no

 

follow symlinks = yes

unix extensions = no

wide links = yes

Once you have done all the changes and saved the smb.conf file, run the testparm command to validate the smb.conf configuration file for internal correctness.

testparm

Configure the Samba Service to Start at Boot Time

By default, Samba is not set up to run automatically.

To start the Samba service:

1. To configure the Samba to run as a service at boot, type the following in a shell:

/sbin/chkconfig smb on

2. To start the Samba service immediately, type the following in a shell:

/sbin/service smb start

Configure the server.ini File

Before you install Harmony on Windows clients, you must create the
/usr/local/ToonBoomAnimation/harmony_10.0/etc/server.ini file on the database server. The server.ini file provides information necessary for the Windows configuration wizard to set up a Windows client.

When creating the server.ini file, be attentive to spelling and character spacing and case.

The following is an example of the /usr/local/ToonBoomAnimation/harmony_10.0/etc/server.ini file. In this example, the database server name is harmonyserver and there are two usadata directories, usadata000 and usadata001.

[WizardConfig]

ServerName=harmonyserver

InstallationDrive=C

UsaShare=usa

UsadbDrive=C

UsadbShare=USA_DB

FileSystem0=C usadata000 harmonyserver

FileSystem1=C usadata001 harmonyserver

Do not worry about the references to "Drive C". These references are necessary for Windows clients and will be ignored by Linux.

 

You can find the example of server.ini under
/usr/local/ToonBoomAnimation/harmony_10.0/resources/samples.
You can copy and paste it from there and change it accordingly.

Any sharing folder name should be case sensitive.

Reboot

At this point, you should reboot the Toon Boom Harmony server to verify that all the Harmony services are properly configured to start automatically.

Set Up Linux Clients

To run Toon Boom Harmony on Linux clients, you must mount the binaries and data directories stored on the server. To access the directories exported from the server, the network file server (NFS) and NFS locking services must be running.

To start NFS services and mount Toon Boom Harmony directories on clients:

1. To access the mounted directories, you must start the NFS service. Type the following in a shell:

/etc/init.d/nfs restart

/sbin/chkconfig nfs on

Note that if you are using Fedora 16, this would be:

systemctl start nfs-server.service

/sbin/chkconfig nfs-server on

2. The NFS lock manager must run on all Linux stations on your network. Without this service, they will not be able to access the database without receiving numerous "read lock" error messages. Type the following in a shell:

/etc/init.d/nfslock restart

/sbin/chkconfig nfslock on

Note that if you are using Fedora 16, this would be:

systemctl start nfs-lock.service

/sbin/chkconfig nfs-lock on

Now you are ready to mount the directories from the server.

3. On each client computer, create directories for:

/usr/local/ToonBoomAnimation/harmony_10.0

/USA_DB

/usadata000.

The directory names must match the names on the Toon Boom Harmony server.

mkdir /usr/local/ToonBoomAnimation/harmony_10.0

mkdir /USA_DB

mkdir /usadata000

4. To mount the directories on the client machine edit the /etc/fstab file.

In the following example, the server is the machine name of the database server.

server:/USA_DB /USA_DB nfs rw,soft,intr,bg 0 0

server:/usadata000 /usadata000 nfs rw,soft,intr,bg 0 0

server:/usr/local/ToonBoomAnimation/harmony_10.0 /usr/local/ToonBoomAnimation/harmony_9.2 nfs rw,soft,intr,bg 0 0

This will cause the Toon Boom Harmony directories to mount with the default version of NFS on your system.

If you encounter errors, you should try using NFS version 2. In this case, you should modify the fstab file to match the following:

server:/USA_DB /USA_DB nfs rw,soft,intr,bg,vers=2 0 0

server:/usadata000 /usadata000 nfs rw,soft,intr,bg,vers=2 0 0

server:/usr/local/ToonBoomAnimation/harmony_10.0 /usr/local/ToonBoomAnimation/harmony_10.0 nfs rw,soft,intr,bg,vers=2 0 0

5. At a command line, type the mount all command.

mount -av

To verify that all of the shares are mounted, type the following in a shell:

mount

A report appears listing all of the shares mounted on the client.

6. To test that the mount has worked, you can open one of the mounted directories and list the contents. You can also open the sample scene in Harmony Stage.
To list the contents of the mounted directories, type the following in a shell:

cd /usr/local/ToonBoomAnimation/harmony_10.0

ls

A list appears of the directories in /harmony_10.0. They are:

etc help lang lnx86_64 Plugins resources

To open the sample scene in the Harmony Stage type the following in a shell:

Stage

Select the Connect to Database radio button and login using the usabatch user name.
Open the sample scene.
If you have any problems opening the sample scene on a Linux client, see Troubleshooting.

Install Start Application Menu Entries and Batch Processing on Clients

To make it easier for users to start Toon Boom Harmony, you should install the application menu entries for KDE. You should also include the -p installation option to start batch processing services on rendering machines.

To install menu entries and batch processing:

1. Go to the directory that contains the Linux installation files.
2. Run the install script with the -p and -kde options.

./install -p -kde

Related Topics 

Troubleshooting