Installing RJS iPrint Packet Printing Software - Support

Installing RJS iPrint Packet Printing Software

From Support

Jump to: navigation, search

Contents

[edit]

Installation

[edit]

iSeries Required Product Installs

RJS iSeries Office Integrator - RJSOFFICE [1]

iPrint Document Packet Printing Library Installer - RJSPACKET [2]

Optional: WebDocs iSeries Edition library - RJSIMAGE

  • NOTE: iSeries Software Licenses are required for each of the libraries listed above.

iPrint Document Packet Printing Library Installer [3]


[edit]

PC Server Component Required Installs

1.) MS Office 2000 or above (Word/Excel used to print Excel or Word to PDF)

2.) Adobe Acrobat Reader 7.0 or above

3.) VB5 Runtime Files [4]

4.) Microsoft DotNet Framework 1.1 [5]

5.) RJS PDF Viewer [6]]

6.) iSeries Office Integrator V1.1.64 and latest update [7] [8]

7.) PDF Creator [9]

8.) RJS PDF Merger [10]

9.) MKDIR C:\RJSTEMP

10.)RJS Document Image Viewer (Used to print TIF to PDF) [11]

11.) RJS Document Image Viewer Update (V1.0.67 or above) [12]


[edit]

RJS iPrint Packet Printing Main Menu Access

To access the Main Menu of the RJSPACKET library, run the followin commands on the command line: 

ADDLIBLE RJSPACKET

GO RJSPACKET
[edit]

Setting Up Library List when Using the Packet Printing API's

Make sure RJSOFFICE and RJSPACKET are in your library list.

Note: If using WebDocs documents with the packet printing APi's, make sure RJSIMAGE is also in your library list. 

ADDLIBLE RJSOFFICE

ADDLIBLE RJSPACKET

ADDLIBLE RJSIMAGE


[edit]

Individual Packet Printing API's Available

Note: API calls should always be single threaded to each PC component since the PC component is currently NOT multi-threaded. This can usually be done by setting up a single threaded job queue for running commands in batch or allow each user to merge documents by installing the PC component on their desktop.


[edit]

Start a New PDF Packet

  • PKTNEWPDF - Generate new PDF document (always required as first step. Sets up temporary file prefix data area objects and PDF names in the current users' QTEMP library)

Note: API calls should always be single threaded to each PC component since the PC component is currently NOT multi-threaded. This can usually be done by setting up a single threaded job queue for running commands in batch or allow each user to merge documents by installing the PC component on their desktop.

[edit]

Building a PDF Packet

Any combination of the following to build a PDF packet after PKTNEWPDF has been called:

  • OFCIFSSND - If you want to send your own files from the IFS to the PC for merging, use this command. It sends the file to /RJSTEMP folder on PC and then calls one of the following commands: PKTCPYPDF, PKTTIFPDF, PKTWORDPDF or PKTXLSPDF commands to merge into your current temp PDF file as long as PKTNEWPDF has already been called at least once.
  • PKTCPYPDF - This command copy existing PC based PDF file from iSeries IFS to PC temp folder and stage for merging. (PDF gets copied to C:\RJSTEMP as temp PDF on PC)
  • PKTDOC2PDF - Given a WebDocs Document ID, this command sends the document to PC and converts the PDF, TIF, XLS or WORD file to PDF. (The PDF is created on the PC in the the C:\RJSTEMP as a temporary PDF)
  • PKTSPLPDF - This command converts an iSeries spool file to PDF document and send to PC. (The PDF is created on the PC in the the C:\RJSTEMP as a temporary PDF)
  • PKTTIFPDF - This command prints and Converts the PC-based TIF document file to a PDF document. (The PDF is created on the PC in the the C:\RJSTEMP as a temporary PDF)
  • PKTWORDPDF - This command prints and converts the PC-based Word document file to PDF document. (The PDF is created on the PC in the the C:\RJSTEMP as a temporary PDF)
  • PKTXLSPDF - This command prints and converts the PC-based Excel document file to PDF document. (The PDF is created on the PC in the the C:\RJSTEMP as a temporary PDF)
[edit]

Complete a PDF Packet

  • PKTMRGPDF - Merge all PDF's to final composite PDF doc on PC in C:\RJSTEMP


[edit]

Get PDF Packet from Remote PC to /RJSTEMP on the iSeries (if desired)

  • PKTGETPDF - Copies the final merged PDF from PC Server to /RJSTEMP in the IFS. This temporary IFS file name gets placed into the data area PDFFILEIFS in library QTEMP. This should only be called after PKTMRGPDF has been completed.
[edit]

Print Final PDF to Selected PC/Network Printer

  • RJSOFFICE/OFCPDFPRT - This command prints the PDF as needed to selected PC/network printer connected to the PC where the original merging process was done.

Note: Printer names are case-sensitive and names must exactly match the PC or network printer name.

[edit]

Perform Cleanup after Packet has been generated and/or printed

  • PKTCLNPDF - This command clean up all temporary PDF files in the C:\RJSTEMP directory on the PC.


[edit]

Sample API Call Sequence

The following is a sample sequence of API calls that will merge and print documents from WebDocs and check the final composite PDF into WebDocs as a new document.

NOTE: Remember to add all three product libraries into the library list (see "Setting Up Library List when Using the Packet Printing API's" Section)

  • PKTNEWDPDF - Create new PDF (Stages new temp PDF prefix name on PC via iSeries Integrator)
  • PKTDOC2PDF - Convert PDF, TIF, XLS or WORD to PDF from a WebDocs Doc ID. (PDF gets created in temp PDF on PC)

(There May be multiple calls to PKTDOC2PDF if including multiple WebDocs docs in the PDF)

  • PKTMRGPDF - Merge all PDF's to final composite PDF doc on PC
  • RJSOFFICE/OFCPDFPRT - Print PDF as needed to selected PC/network printer connected to PC where merging was done.

Note: Printer names are case-sensitive and names must exactly match the PC or network printer name.

  • PKTGETPDF - Get PDF from PC to IFS (If checking in to to WebDocs)

Temp IFS file name gets placed into data area PDFFILEIFS in library QTEMP

  • DOCCHKIN - If checking doc into WebDocs, retreive IFS file name from PDFFILEIFS data area and check in document to WebDocs.
  • PKTCLNPDF - Clean up all temp PDF's on PC side.

Repeat process for each pdf packet.


[edit]

Options for Automatic Packet Printing from WebDocs

1.) Packet Printer Maintenance - Enter packet destination printers.

2.) Packet Definition Maintenance - Enter the definition for a packet.

3.) Packet Build Maintenance - Enter a list of documents to be assembled into a packet.

10.) PKTPRINT command - This command drives the assembly and printing of a document packet based on a trigger document ID and document type in WebDocs.

The PKTPRINT command would normally be triggered from the WebDocs document checkin or any user written program. However the command can be run standalone during testing.

PKTPRINT Parmeters:

  • Document ID - WebDocs document ID for trigger document
  • Trigger Document Type - WebDocs Document Type for trigger document ID.
  • New Document Check-in user ID - WebDocs user ID or *CURRENT to use current iSeries user as checkin user.
  • Stop if DOCSRCH finds no docs - Stop packet processing and issue an error if one of the documents is not found in WebDocs. Default - *NO

NOTE: If your rules are very stringent and a document must exist for each entry in the Packet Build file, then this setting should be set to *YES. *NO is a more tolerant option that will allow one or more documents for the packet to be missing or not found in WebDocs.

  • Log commands - Log all packet assembly CL commands to the command log file PKTLOG00. This is a great way to debug issues with the packet assembly and printing and see what values are being passed to the packet assembly commands. Default - *YES

11.) Display Packet Log - Logs all packet building CL commands. The log file can be cleared as ften as desired and is mainly used for debugging.

12.) Clear Packet Log - Clears packet CL command log.

Retrieved from "http://wiki.rjssoftware.com/wiki/index.php/Installing_RJS_iPrint_Packet_Printing_Software"
Personal tools