Answer the following questions before you start your installation.
Will you run HA for Oracle Traffic Director with a logical hostname or a shared address? See the Oracle Solaris Cluster Concepts Guide document for information on the two types of network resources.
Where will the installation and configuration directories and files reside?
Do other Oracle Solaris Cluster resources have dependencies on the services that Oracle Traffic Director provides or does Oracle Traffic Director depend on any services provided by other Oracle Solaris Cluster resources? If so, resource dependencies might exist between the resources so that one starts or stops before the other. See the r_properties (5) man page for a description of the resource property Resource_dependencies that sets these dependencies.
When using a logical hostname, HA-Oracle Traffic Director must be configured to bind to INADDR_ANY since a logical hostname can be present on only one node at a time.
Determine the resource groups to use for network addresses and application resources and the dependencies between them. See the rg_properties (5) man page for a description of the resource group property RG_dependencies that sets these dependencies.
Provide the logical hostname (for failover services) or shared address (for scalable services) for clients to use to access the data service.
Because you can configure Oracle Traffic Director to bind to INADDR_ANY, if you plan to run multiple instances of the Oracle Traffic Director data service or multiple data services on the same node, each instance must bind to a unique network address and port number.
Determine where to place logs and error files on the local file system.
Determine where to place the contents on the cluster file system.