Apple Shake (Qmaster 1.2) Distributed Rendering (10.3) - Manual (Page 14)

14
Note: In this example, the name “Blue” will be used for this Xserve.
Remember to plug in and connect all of your network cables, since you will need the
network for these steps. Take the time to make sure you have all cables properly connected.
Step 2: Make a note of the Server Admin LDAP settings
Open Server Admin (located in /Applications/Server) and then:
1 Connect to the Xserve (for example, blue.local).
2 Go to the Open Directory page, then the Settings page, and click the Protocols tab.
3 Write down the Search Base that appears on this page. You will use this information in
the next step.
Step 3: Use Directory Access to specify the Xserve as the LDAP server
Open the Directory Access utility (located in /Applications/Utilities) and do the
following:
1 In the Service pane, select LDAPv3, then click Configure.
2 Click Show Options, then click New to create a new LDAP configuration.
3 Enter a Configuration Name that is similar to your Xserve name (for example,
Blue LDAP).
4 Set the Server Name or IP Address to the Rendezvous name of your Xserve (for
example, blue.local).
5 Set the Search Base to the value you noted in step 2 (for example, dc=blue).
6 In the Authentication pane, choose Custom Path from the Search pop-up menu.
7 Click Add, then choose the Xserve LDAP server (for example, /LDAPv3/blue.local).
Step 4: Install Shake and Shake Qmaster on the Xserve and on the
client computers
Install the necessary components of Shake and Shake Qmaster on the Xserve and on the
client (user) computers. Keep in mind that the Xserve will act as a service node and
cluster controller, as well as an administrator computer. For details on how to install Shake
and Shake Qmaster, refer to the Installing Your Software booklet that came with Shake.
Note: You will install Shake and Shake Qmaster on the cluster nodes in a later step,
using Apple Remote Desktop.
Warning: Because having an additional primary domain controller on your network
could cause an existing primary domain controller to behave unpredictably, you
should not enable a Windows primary domain controller unless you are familiar with
the ramifications.
90180SET Page 14 Thursday, April 15, 2004 3:32 PM