Ivory Service Architect allows you to redirect 100% of your web services workload onto specialty engines such as IFL, zAAP and zIIP so mainframe integration has zero impact on your general purpose processor (GPP).
Ivory Service Architect can take full advantage of the IFL specialty engine for Linux on System z. Not only does 100% of the Linux on System z workload run on the IFL, there are no speed restrictions applied. By using Linux on z with Ivory, you are still leveraging your mainframe as the primary application server in the enterprise. Using Ivory with Linux on z also enhances communications back to the GPP due to the availability of Hipersockets, which provide near memory speed within the zServer architecture for IP processing.
The zIIP specialty engine was primarily intended for DB2 workload but is able to be leveraged by Ivory. The zIIP processor provides an API to shift eligible workload to the zIIP. This decreases MIP usage on the z/OS GPP and leads to processing cost reductions.
The zAAP specialty engine, initially intended for Java workloads, is also utilized when you leverage XML system services. This can be used by an application like Ivory Service Architect that runs in CICS or outside of CICS, and is the only option to leverage a specialty engine should you desire a CICS-based deployment.
