+

Search Tips   |   Advanced Search

Set up a support server for the portal farm

Certain portal functions, including seedlist generation and subscriptions, are designed to run on a single node in a cluster. For a portal farm with a shared file system, farm workers read their configuration information from a single, master server. The enable-farm-mode task we ran to configure this functionality also disables function designed to run on a single node. Disabling these functions keeps different members from running the same services at the same time.

To use search, configure a dedicated support server to run these tasks.

The support server is unique in some of its configurations, and shares other configurations with the other farm members, including database connections and security configurations.

When the support server is on its own server, copy the master server profile to the support server. Directory paths must match on between the master and support server. Use the base portal and WAS binary installation directories shared on the master file system. Reference the local file system for the profile.


Messaging Bus

The following annotations apply to the image labels:

    1. Messaging engine
    The messaging engine is optional. To create, run the task...

      create-wcm-jms-resources

    ...which is described in the document Set up farm instances as unique installations. If not created, run on the farm master also.

    2. Subscriber
    This server is the syndication subscriber. No action is required on this profile.

    3. Search engine
    Follow the instructions to set up a remote search server in a cluster.

    4. Shared portal
    Shared portal with the filesystem replication or sharing techniques.

    5. Shared application server
    Shared application server with filesystem replication or sharing techniques.

    6. Unique profile
    Unique profile with filesystem replication or multiple profiles support. This profile is configured differently than the farm master. It is isolated from the farm workers to support operations in this list.

    7. JCR database domain
    The JCR database domain is inherited from the initial farm profile configuration. There is no need to change the database domains.

    8. Customization database domain
    The Customization database domain is inherited from the initial farm profile configuration. There is no need to change the database domains.

    9. Communication database domain
    The Communication database domain is inherited from the initial farm profile configuration. There is no need to change the database domains.

    10. Release database domain
    The Release database domain is inherited from the initial farm profile configuration. There is no need to change the database domains.

Set up the support server to match the configuration of the portal farm, either GPFS or non-GPFS, with the following deviations:

  • Configure the master portal installation to the shared database, custom applications, and security settings

  • Before setting up a farm with a shared file configuration...

    1. Create a local copy of the directory; preserve the profile configuration.
    2. Move the copy to the local file system of the support server.
    3. Verify the local directory on the support server matches the directory location on the master server.

  • On the support server, mount the remote directories. Read the directory from the support server local file system.

  • Continue to setup the farm on the master server with one of the following topics:

    • Set up farm instances using a GPFS file shared configuration
    • Set up farm instances using non-GPFS file shared configuration

The wpsScheduler is used to clean up the database for non-immediate tasks, such as page deletions, and must be enabled only on the farm support server. We must disable wpsScheduler on the farm master. Go to...

...and set...

    daemonAutoStart = false

...with type set to java.lang.String. Then restart the server.


Parent Set up farm instances using a shared configuration

Related concepts:
Work with syndicators and subscribers
Set up farm instances as unique installations
Configure a shared file system
Configure search in a cluster