Macromedia live cycle 7.2 매뉴얼
Adobe LiveCycle
Post-deployment
Installing and Configuring LiveCycle for JBoss
LiveCycle Forms post-deployment tasks 28
LiveCycle Forms post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Forms.
You can now create custom applications for LiveCycle Forms. (See the Developing Custom Applications
guide.) For details on the Form Server Module, see the Form Server Module API Reference. For details on the
XML Form Module API, see the XML Form Module API Reference.
guide.) For details on the Form Server Module, see the Form Server Module API Reference. For details on the
XML Form Module API, see the XML Form Module API Reference.
You can optionally install LiveCycle Print to enable LiveCycle Forms to output forms as Adobe PostScript,
Printer Control Language (PCL), and Zebra Programming Language (ZPL) print streams, in addition to PDF
and HTML forms. Without LiveCycle Print, LiveCycle Forms cannot output forms as print streams. Instead,
LiveCycle Forms sends forms across a network and renders them to client devices, such as web browsers,
as PDF or HTML forms.
Printer Control Language (PCL), and Zebra Programming Language (ZPL) print streams, in addition to PDF
and HTML forms. Without LiveCycle Print, LiveCycle Forms cannot output forms as print streams. Instead,
LiveCycle Forms sends forms across a network and renders them to client devices, such as web browsers,
as PDF or HTML forms.
Verifying the LiveCycle Forms deployment
You can verify that LiveCycle Forms is deployed and running properly by accessing the Installation
Verification Sample application that is installed with the product.
Verification Sample application that is installed with the product.
➤
To access the Installation Verification Sample:
1. Copy the FormsIVS.ear file from the [LiveCycle root]/components/forms/samples/
common/ directory to the [appserver root]/server/all/deploy directory.
2. Restart the application server.
3. Type the following URL in a web browser:
http://[host name]:[port]/FormsIVS
where [host name] is the name of the server on which Forms has been deployed. If you are invoking
FormsIVS on the server itself, provide the server name instead of “localhost”.
FormsIVS on the server itself, provide the server name instead of “localhost”.
Note:
For information about using the sample application, click the Help link in the Samples page in
the web browser.
the web browser.
LiveCycle Print post-deployment tasks
This section describes the post-deployment tasks specific to LiveCycle Print.
Verifying deployment
You can verify that LiveCycle Print is deployed and running properly using any of the following methods:
●
Deploying and running the Print Installation and Verification Sample (PrintIVS) web application.
●
Running the Print Submitter console application (you do not have to deploy this application).
Both of these applications invoke LiveCycle Print by using the LiveCycle Print API (this API consumes
the LiveCycle Print web service).
the LiveCycle Print web service).
●
Running the Forms Installation and Verification Sample (FormsIVS) application. If LiveCycle Print is
deployed, the Output format list contains three additional options: PostScript, ZPL, and PCL. For
information about the Installation Verification Sample application, see
deployed, the Output format list contains three additional options: PostScript, ZPL, and PCL. For
information about the Installation Verification Sample application, see
.