Ivory Service Architect exploits the zIIP, or System z Integrated Information Processor, specialty engine to dramatically reduce mainframe MIPs usage for mainframe integration and SOA workloads. The Ivory Server for z/OS fully exploits the zIIP specialty engine, offering MIPs reductions for SOA and mainframe integration workloads.
IBM provided an API for software vendors to leverage the zIIP Specialty processors by using Work Load Management Enclaves. Ivory Service Architect has been completely redesigned to exploit the zIIP, with four key areas of Ivory workload now running on the zIIP. The in-bound SOAP packet XML parsing, the Ivory runtime XML parsing, the outbound SOAP XML packet processing, and Ivory data movements can all be run natively on the zIIP.
In the future GT will look at other functions that will benefit from the use of WLM Enclave processing. Again in order to provide clients control and choice In addition to offering support for the zIIP specialty engine, Ivory Service Architect provides clients with an easy to use method to manage the workload with the new Ivory SOA Workload Manager. This console allows clients to select which services will be processed on the zIIP, and which may be better off running on the general purpose processor. With Ivory, you can choose to run workload on the zIIP, the zAAP, both the zIIP and zAAP together, or on the general purpose processor. Ivory Service Architect makes it easy to reduce MIPS across your SOA workload, resulting in a dramatically lower TCO.
