Milestone 4: Installing Standalone File-AID/EX Execution Server(s)

While every installation of Topaz Workbench with Topaz Enterprise Data feature includes a plugin that runs a local execution server, such execution servers are limited and intended only for developing and debugging File-AID/EX specifications. Automated executions of the specifications and processing of large volumes of data should be performed on Standalone execution servers, that should typically be installed on more powerful server-level hardware.

When the mapping specifications are complex, transformations are CPU-intensive. Also, a good network performance while accessing the data (including source, target, lookup tables, etc.) is critical for execution performance. Planning for the location of the Standalone execution servers should include analysis of network bandwidth, latency, and throughput when accessing the data.

The execution server can connect directly to a variety of relational data environments as well as MVS data types through MVS Access Modules. It enables data conversion among the major MVS data types and between mainframe and distributed data types. It can also read existing File-AID/RDX extract files and import metadata from the extract file.

The execution server is designed for high performance and full functionality. It includes compiler technology designed to convert mapping specifications defined in the repository directly into Java Byte Code (JBC). This provides improved performance since the execution server acts as a compiler rather than an interpreter.

Prior to installation of a Standalone execution server, make sure that there is an available installation of a compatible version of Topaz Workbench with Topaz Enterprise Data feature, and that it's configured following the steps described in Milestone-3-Installing-Topaz-for-Enterprise-Data-Client: