Dear Mr. Ram KM,
The business mentioned above by you was absolutely perpect.
Adobe LiveCycle® ES (Enterprise Suite) is an integrated server solution that blends data capture, information assurance, document output, process management, and content services.
I may guess you have to install ADOBE LIVECYCLE WORKBENCH ES. The Adobe liveCycle Designer ES comes with Workbench ES once you installed. Please go through the below information, you may get some idea.
---------------------------------
1. Significance of folders in Documentum Repository (for all regions)
WorkBench -> where all work in progress or finalized templates should reside. Designer must carry his/her development of Form/Template design in this folder.
Schema -> where the XML Schema (Using which data needs to bound to the template) should reside. This schema should be the same across the entire region (dev, UAT, Prod).
Templates -> This is the run time folder. CPR application points to this folder while searching for templates. Designer should never work on this folder or move/copy any template from WorkBench to this folder. This action will be taken care of by CPR application.
Master Fragment Library -> All the fragments should reside inside this folder. Once one fragment is changed in this folder then change will be reflected immediately to all the templates that use this fragments.
NEW TEMPLATE DESIGN
2. Design approach through workbench ES.
Designer selects UAT region through WorkBench ES to do the development of the Forms/Templates.
Designer opens up an existing form/letter or creates a new form/letter through designer in Workbench ES
He/She caries out the design (forms/letters) in Workbench folder.
He/She carries out the design of fragments in Master Fragment Library folder.
Once designer is satisfied with design he/she right clicks on the document and goes to the history popup.
Select the latest document in the list and click on Save as button in the popup screen to save it to the local hard disk or any file system.
Designer now goes to CPR Application and click on Add button.
The Add popup opens up.
Designer clicks on Browse button and adds the letter/forms she had downloaded to his/her disk and adds corresponding Meta data. He/She then hits Done. At this point behind the scene CPR application puts the corresponding letter/Form into Templates folder with all the meta data set.
The UAT test on the newly uploaded templates then happens.
Once the UAT is successful then the corresponding templates need to be promoted to Production.
First Step: Promoting new Fragments to Production
Administrator directly logs into Production fragment library folder and creates the fragments again in production. This needs to be done very carefully as this fragments will be available immediately for end users (on click of Save in the designer).
Note: The downloaded fragments (from UAT region) can be moved to production directly using drag and drop feature of Workbench ES.
Second Step: Promoting new templates to Production
If UAT is successful Administrator then uploads the template file into production the way he/she did in UAT region. He/she needs to put appropriate meta data in production also.
EXISTING TEMPLATE MODIFICATION
3. Design approach through workbench ES.
Designer selects UAT region through WorkBench ES to do the change of the existing Forms/Templates.
Designer opens up an existing form/letter or creates a new form/letter through designer in Workbench ES
He/She caries out the design (forms/letters) in Workbench folder.
He/She carries out the design of fragments in Master Fragment Library folder.
Once designer is satisfied with design he/she right clicks on the document and goes to the history popup..
Select the latest document in the list and click on Save as button in the popup screen to save it to the local hard disk or any file system.
Designer now goes to CPR Application and finds the templates he/she wants to modify.
Designer highlights the corresponding row and hits on Modify.
The Modify popup opens up.
Designer clicks on Browse button and adds the letter/forms she had downloaded to his/her disk and edits corresponding Meta data (if needed). He/She then hits Done. At this point behind the scene CPR application puts the corresponding letter/Form into Templates folder with all the meta data set. Also it inactivates the older version if any.
The UAT test on the newly uploaded templates then happens.
Once the UAT is successful then the corresponding templates need to be promoted to Production.
First Step: Promoting existing Fragments to Production
Administrator directly logs into Production fragment library folder and updates the fragments again in production. This needs to be done very carefully as this fragments will be available immediately for end users (on click of Save in the designer).
Note: The downloaded fragments (from UAT region) can be moved to production directly using drag and drop feature of Workbench ES.
Second Step: Promoting existing templates to Production
If UAT is successful Administrator then uploads the template file into production the way he/she did in UAT region. He/she needs to put appropriate meta data in production also.
-----------------------------------------------------
FormFragsRenderPdfServlet:
---------------------------
import java.util.Properties;
import java.io.*;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.ServletOutputStream;
import com.adobe.etech.FileUtils;
import com.adobe.formServer.client.EJBClient;
import com.adobe.formServer.interfaces.*;
import com.adobe.pso.eforms.model.XDPWrapper;
import com.adobe.pso.eforms.model.FragmentMetadata;
import com.adobe.pso.eforms.model.TemplateMetadata;
import com.adobe.pso.eforms.model.XSDReference;
import com.adobe.pso.eforms.util.FormServerDefinition;
import com.adobe.pso.eforms.util.RenderFormOptions;
import com.adobe.pso.eforms.util.RenderUtils;
import com.adobe.pso.eforms.util.XDPUtils;
/**
* @version 1.0
* @author
*/
public class FormFragsRenderPDFServlet extends HttpServlet {
protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException {
System.err.println("RenderPdfServletScott - doGet");
try {
ServletContext context = this.getServletContext();
// 1. Construct the web app's context url
String contextURL = request.getScheme()
+ "://"
+ request.getServerName()
+ ":"
+ request.getServerPort()
+ request.getContextPath();
// 1a. If making an EJB remote call to FS, construct the JNDI properties object.
Properties jndiProps = new Properties();
jndiProps.setProperty("java.naming.factory.initial","com.ibm.websphere.naming.WsnInitialContextFactory");
jndiProps.setProperty("java.naming.factory.url.pkgs","com.ibm.ws.naming");
jndiProps.setProperty("java.naming.provider.url","corbaloc:iiop:127.0.0.1:2809");
// 2. Create FormServerDefinition object to define the form server invocation method
FormServerDefinition fServDef = new FormServerDefinition();
fServDef.setInvocationMethod(FormServerDefinition.EJB_REMOTE);
fServDef.setJndiProperties(jndiProps);
//Specify the path to load the data from
byte[] cXMLData = getBytesFromFile(new File (context.getRealPath("/data/data.xml")));
// 3. Set the various options for rendering the form. The setFormQuery() method establishes the name
// of the temporary file created on the filesystem to hold the "pre-rend
