Do I Need to Configure deployerConfigContext.xml when Deploying CAS on a Secondary Node? (Doc ID 1473738.1)

Last updated on NOVEMBER 03, 2022

Applies to:

Oracle WebCenter Sites - Version 7.6.1 and later
Information in this document applies to any platform.

Goal

When deplying the cas.war (from the primary node) on a secondary node, we notice in deployerConfigContext.xml it has a loginUrl property pointing to the primary node.

Why is the cas.war on the primary node not generic? Do we need to configure deployerConfigContext.xml for clustering CAS?

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

Do I Need to Configure deployerConfigContext.xml when Deploying CAS on a Secondary Node? (Doc ID 1473738.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!