In a scaled Rendition Server environment with multiple Managing Nodes, it's crucial to ensure uninterrupted connectivity between Worker Nodes and Managing Nodes. However, in certain cases, a Worker Node may encounter difficulties establishing a connection with the configured Managing Node. To address this issue, the Rendition Server offers a fallback option. This troubleshooting guide will explain how to configure the fallback option for Worker Nodes when they are unable to connect to the Managing Node.
Step 1: Adding the Fallback Option in WorkerNodeConfig.user.xml
To activate the user-defined fallback option, follow these steps:
- Open the WorkerNodeConfig.user.xml configuration file.
- Locate the
<configSections>
element. - Add a new
<section>
element within<configSections>
as shown below:
<configuration>
...
<configSections>
...
<section
name="fallbackManagingNodes"
type="Foxit.RenditionServer.Node.FallbackManagingNodeConfig,
RsWorkerNode,
Version=1.0.0.0,
Culture=neutral,
PublicKeyToken=d52f2a2656bb87e9"/>
...
<configSections>
...
</configuration>
Note: Ensure that the value of the Version
attribute matches the other <section>
elements in the file.
Step 2: Defining Alternative Managing Nodes
After adding the <section>
element, you can specify the list of alternative Managing Nodes as follows:
- Locate the
<configuration>
element in WorkerNodeConfig.user.xml. - Within
<configuration>
, add the<fallbackManagingNodes>
element. - Specify the alternative Managing Nodes using the
<fallback>
address attribute. For example:
<configuration>
...
<fallbackManagingNodes>
<fallback address="<scheme>://<host1>:<port>/<path>" />
<fallback address="<scheme>://<host2>:<port>/<path>" />
...
</fallbackManagingNodes>
...
</configuration>
Note: Replace <scheme>
, <host1>
, <port>
, and <path>
with the appropriate values for the alternative Managing Nodes.
By following these steps, you can configure the fallback option for Worker Nodes in a scaled Rendition Server system. The fallback option allows Worker Nodes to establish connections with alternative Managing Nodes when they encounter difficulties connecting to the configured Managing Node. This configuration ensures the continuous availability and optimal performance of the Rendition Server environment, even in the event of connection issues.