1 Reply Latest reply on Feb 8, 2006 9:30 AM by (Tom_Warfield)

    New to this Products

      I designed a sample template by using adobe output designer.
      And i want to test it in a adobe central output server.

        • 1. Re: New to this Products
          Level 1
          You state you are new to the product so I'll go into great detail here regarding the steps necessary. What I don't cover are all of the parameters and options that might be necessary. All of my instructions assume you are using the Windows version of the software. If you are using some other version I have no idea what the differences might be.

          It is actually a simple process but it can be daunting for someone that is unfamiliar with the process.

          The first step is to "compile" the form and get the .MDF file into the folder that Central is configured to look for them. Your Central Server administrator should be able to tell you where that is. If that is you, then log onto the server and start the "Central Control" program. Then use the mouse to click on the "Configuration" menu and select "Configure Central and Agents...". Then click on "Print Agent" and "Edit File". Make a note of the location shown for "Form files" (this is where the MDF file needs to go). Also note the location indicated for "Data files" (you will need this for a following step).

          Next, you need a Central job defined within the "Job Management Database" on the server that runs the "JFMERGE" task. This is done by logging onto the server, starting the Central Control program and clicking on "File" and "Job Management Database" and then click on "Jobs". Click on the "New Job..." button, enter a short name (like "TEST") and click OK. Click on "New Step..." and it should already have "JFMERGE" in the "Task id". It will also have "TEST.mdf" for the "Form file" name. Replace "TEST.mdf" in the Form file name with an asterisk (*). You can select a Printer name at this time but I suggest that it be left as an asterisk so you can specify the printer in the test data file.

          If your desired printer is not already defined within the Job Management database, it must be added. Select "File" on the Central Control menu, click on "Job Management Database" and then on "Printers". Click the "New Printer" button and fill out the "Printer Name" with whatever you want. Enter the address of the printer in the "Physical Device" field (a UNC designation such as "\\SERVER\PRINTER" works just fine if you are set up to be able to do that). It is a good idea to also put the printer driver parameter in the "Print Agent options" field but this could also be a parameter in your test data file. Whether as a parameter in the data file or in the printer setup it would be "-aspXXXXXXXX" with the X's replaced by the file name of the "Presentation Target". To determine the file name, load your form in the Output Designer software, click on "File" then "Presentation Targets". Look at the printer you want to send the form to (probably the default printer). At the end of the label is some text within square brackets []. This is the file name you would use for the "-asp" parameter (without the brackets).

          Make a note of the Printer Name that is used for defining it to Central. This name will be needed when creating the test data file.

          Once you are through working with the Job Management Database you need to click through the dialogs to close it and then click on "Control" on the Central Control screen and click on "Reload Job Managagement DB" and then respond to the subsequent prompts.

          The final step is to create a test data file and place it in the "Data files" location determined in the first step. As a minimum this data file would contain a "job" statement as well as a line that references your compiled form. The job statement will include the parameter that tells Central what printer to use as well as the print driver parameter if it isn't defined within the Job Management Database for the printer.

          A sample file to print a blank form (no data) might look like the following (this assumes you are not using XML data files):

          ^job TEST -zPRINTER -aspDRIVER
          ^form FORM-NAME.mdf

          This file would be placed in the "data" folder on the server (noted in step 1 and would be called something like XXXXXXXXX.DAT (the .DAT extension is the Central server default extension for data files). Replace the XXXXXXX with anything you want but if you include spaces it could cause problems.

          "TEST" is the job name defined in the Job Management Database (JMD). "PRINTER" is the Printer Name defined in the JMD. DRIVER is the physical file name for the print driver (comes from the stuff within [] in Output Designer and is not required if it is included within the printer definition in the JMD. "FORM-NAME" is the name of the form file you designed in Output Designer and compiled and placed on the server. Be sure to press the "Enter" key on your keyboard after the form name so that there is a "blank line" at the end of the file. If this isn't done the form might not print.

          If you have more than one form you can include multiple "^form" statements. If you have data you want printed you will have to include appropriate "^field" and/or "^global" statements. Do a "Test Presentation" from within Output Designer and click on "Create Sample Data File" and once the file is created click on "Edit" to see what these ^field and/or ^global statements would look like for your form. When using Test Presentation to create a sample test file, the XXXXXXX that it uses is where your real data would go.

          Once you have the test job and printer defined within the Job Management Database, future tests only require the creation of the test .DAT file referencing the appropriate form name.

          FYI: We set up FTP on the server that has the data folder as it's root folder. This way we can put DAT files onto the server without having to have much in the way of individual rights on the server.