Ok, so I have done some additional reading and I've found out that Livecycle forms can be submitted via reader without reader extensions so long as the submit is via HTTP Post or as XML data only.
This effectively means you can collect the data from the submitted forms for processing, but you can not re-render the form from the form template and the XML without the presumably expensive server component, Reader Extensions, which for all I know, requires other components to run.
This all seems awfully expensive for a solution to host a dozen or so forms and archive the submissions in one place where they can be re-opened and added to.
I don't undestand why it's so prohibitively expensive to submit dynamic PDF forms as PDF vs submitting static PDF forms as PDF, which can be done with Acrobat Pro all by itself at ~$500.
We are a SMALL 501c6 Membership Corp and have the same issue. Only about 24 very redundant forms we'd love to host from designing them in Livecycle, but the cost of the Livecycle server prhibits us from doing so. We email the beautiful interactive pdf forms we create in Livecycle to a vendor who chops them up into xml and css.
Members go to his site through our site. They complete the form and it submits and resides on his server securely.
Our staff then logs into his server, and downloads the pdf output which does not look like the original forms and is less than lovely.
What have you found is the best way to take and host securely, the pdf forms we create in livecycle for members?
We are using CreativeCloud and its a shame there is not a Livecycle forms Cloud and Secure Storage product for SMBs and Non-Profits... Or is there?????
If it makes you feel worse Adobe will manage your 24 forms for a minimum of $250,000 per year. Did you ever find a solution?