Image Serving components

Last update: 2023-09-28
  • Created for:
  • Developer
    User

Dynamic Media Image Serving consists of the following components:

Component

Description

Server Supervisor

A stand-alone executable responsible for starting, stopping, and ensuring the health of the other components.

Apache Tomcat

It provides the environment for most Java-based components.

Monitoring/Alerting Service

J2EE application. Provides server monitoring and email alerting.

Platform Server

J2EE application. Manages client connections, logging, communications with other components. HTTP access at /is/image.

Caching Service

J2EE application. Manages the Platform Server's data caches. HTTP access at /is/cache.

Image Server

It performs all image-processing and image file I/O operations. Both 32-bit and 64-bit executables are available for Linux® (32 bit only for Windows).

ATE Text Render Component

One or more instances of the text rendering service may be active when textPs= operations are run.

SVG Render Component

Stand-alone Java™ application (not hosted by Tomcat).

Dynamic Media Image Rendering (aka. Render Server)

It requires a separate license to activate. HTTP access at /ir/render. All Image Rendering functionality is integrated into the Platform Server and the Image Server, with no separate executable components.

Additional configuration settings are provided by the default catalog ( default.ini) or specific image catalogs (see Image Catalogs for details).

On this page