Liquent InSight Rendering 4.4 Administration

Eliminating the Single Point of Failure

You configure InSight Publisher to have the URL for an IRS that handles all job requests to Liquent InSight Rendering. However, if this IRS fails, InSight Publisher cannot communicate with Liquent InSight Rendering.

To eliminate this single point of failure, you can use several industry-standard, third-party, load-balancing and fail-over solutions. All the solutions require IRS to be installed on more than one InSight Rendering server. You can contract the Parexel Client Enablement team to configure these solutions.

If you do not use a software or hardware load balancer, you can create a DNS alias for the InSight Rendering server.

If you do not implement a fail-over solution and the IRS fails, you must configure the InSight application to have a new URL. Then you must restart the InSight Rendering server.

JavaScript must be enabled in order to use this site.Please enable JavaScript in your browser and refresh the page.

Eliminating the Single Point of Failure

You configure InSight Publisher to have the URL for an IRS that handles all job requests to Liquent InSight Rendering. However, if this IRS fails, InSight Publisher cannot communicate with Liquent InSight Rendering.

To eliminate this single point of failure, you can use several industry-standard, third-party, load-balancing and fail-over solutions. All the solutions require IRS to be installed on more than one InSight Rendering server. You can contract the Parexel Client Enablement team to configure these solutions.

If you do not use a software or hardware load balancer, you can create a DNS alias for the InSight Rendering server.

If you do not implement a fail-over solution and the IRS fails, you must configure the InSight application to have a new URL. Then you must restart the InSight Rendering server.