Configuring Policy and Distribution Services with Novell Cluster Services ensures high availability of Tiered Electronic Distribution (TED). Installing a TED Distributor and Subscriber in a cluster ensures the transmission and reception of policies and software.
Installing the ZENworks database for Distribution and policies information in a cluster ensures that the database is always available when the Distributor and Policy/Package Agents need to log Distribution processing information.
Installing the Web components and supporting software in a cluster ensures that you can always monitor and manage the distribution process throughout your network.
The installation program walks you through installing the Policy and Distribution Services software for Distributors, Subscribers, and the Policy/Distribution database.
You can install Policy and Distribution Services in a cluster in the following scenarios:
In the latter two scenarios, the TED.NCF file on the cluster volume must be edited to add the -hosts switch before you offline the cluster to bring up ZfS. This is documented in Step 2 below.
To install Policy and Distribution Services to a cluster:
Follow the instructions provided in Installing Policy and Distribution Services on NetWare and Windows Servers, keeping in mind the following cluster-specific details:
IMPORTANT: You can install only one instance of Policy and DIstribution Services (one Distributor and/or one Subscriber) in a cluster because Policy and Distribution Services treats a cluster as if it were a single server.
You can also select non-clustered servers at the same time you are installing to a cluster.
IMPORTANT: Do not use double-byte or extended characters in any part of an installation path, including a NetWare volume name.
The installation program installs the Policy and Distribution Services software on the specified cluster-enabled volume. From that location, the Distributor Agent, Subscriber Agent, and Policy/Package Agent will be able to run on any of the nodes in the cluster. If the node where they are running goes down, they automatically fail over to another node in the cluster.
The installation program also updates the load and unload scripts associated with the Cluster object, which makes the failover/failback process possible.
If you only installed a Subscriber to the cluster (its software to the cluster volume and its object into the same tree where the Cluster object resides), or you installed the Distributor and Subscriber software to the cluster volume, but their objects to a different tree than where the Cluster object resides, do the following:
Open the following file in a text editor:
Installation_path\ZENWORKS\PDS\TED\TED.NCF
Scroll to the bottom of the file and locate the class:
.com.novell.application.zenworks.ted.TED
Insert the -hosts switch after the class.
Examples where the cluster is known by another DNS name or IP address (do not list those that are bound to the server's NIC card):
.com.novell.application.zenworks.ted.TED -hosts cluster1.novell.com
or
.com.novell.application.zenworks.ted.TED -hosts 123.456.78.9
Example where the cluster is known by multiple DNS names and/or IP addresses:
.com.novell.application.zenworks.ted.TED -hosts 123.456.78.9:cluster2.novell.com:cluster3.novell.com
Your list of DNS names and IP addresses should be delimited by a colon (:).
Save your changes > exit the text editor.
To start the TED agents for the first time, offline the cluster and then online it again.
This causes the clustering software to reread the updated load script and load the TED agents.