I'm currently involved at a client who wants to install LiveCycle on an IBM mainframe running Z/OS (Not AIX). From what I gather, Z/OS has a built-in Linux component called IFL (Integrated facility for Linux), which is apparently based on SUSE, but I'm not an expert in that area.
Has anyone done something similar to this before? If yes, were the results positive?
LiveCycle has some non-Java C++ components. By their very nature, these have to be compiled for the mainframe CPU architecture. They are not. LiveCycle is supported on SUSE Linux, but only on the Intel/AMD x86 and x64 CPU architecture. LiveCycle on SUSE Linux on IBM's POWER architecture running AIX 5.3L (L stands for Linux support), won't work either, due to the same reason.
LiveCycle has some non-Java C++ components. By their very nature, these have to be compiled for the mainframe CPU architecture. They are not. LiveCycle is supported on SUSE Linux, but only on the Intel/AMD x86 and x64 CPU architecture. LiveCycle on SUSE Linux on IBM's POWER architecture running AIX 5.3L (L stands for Linux support), won't work either, due to the same reason.
Do we have the list of components that cause this problem. I am looking at a proposal where I want to use only a small subset of the features i.e. Remoting Service with Java Adapters.
You won't get technical support from Adobe if you do this.
However, to answer your question - Forms ES, Output ES and possibly PDF Generator ES are out of the question. This is because Forms and Output use XMLForm which is a C++ component.
