Differences

This shows you the differences between two versions of the page.

--- pub:iview8be [2018/09/06 10:01] – [Menu IVIEW, option 1:] kkramer
+++ pub:iview8be [2018/09/06 10:31] – [Menu IVIEW, option 10:iView Servers (Engines)] kkramer
@@ Line 91: / Line 91: @@
 === Archive Options ===
-  * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended.
+   * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended.
+  * **Description**: Enter a recognizable description to identify this application.
   * **Library**: This is the library in which the meta data file is stored and is a global setting stored in data area DSIVIEWLIB.
   * **Directory**: This is the root of the iView IFS archives. It is a global setting stored in data area DSIVIEWDIR.
-  * **File Name**: Specify the file system object name of the archived document using constants and these keywords:\\
+  * **PDF Output Name**: Specify the file system object name of the archived document using constants and these keywords:\\
-<html><pre>
-    *DATE to include QDATE
+| *NAME | The archive name |
-    *TIME to include QTIME
+| *DATE | Processing date in format YYMMDD |
-    *INDEX01 - *INDEX20 to include the current values of these meta data fields
+| *TIME | Processing time in format HHMMSS |
-</pre></html>
+| *INDEX01 to *INDEX20 | Contents of meta data fields |
   * **Disposition Options**: This controls the fate of the original spool file:
 <html><pre>
-  *RETAIN        Retain in Outqueue
+  *RETAIN        Retain in Output queue
   *ORIGINAL      Archive Original
   *SYSTEM        Archive Post Processing
   *NONE          Do Not Archive
 </pre></html>
+  * **Table Import**: Controls use of tables when importing from prior implementations of iScan. This field is not used with current software and should be set to N.
-  * **Table Import**: Controls use of tables when importing from prior implementations of iScan. This field is not used
+  * **Allow Null Value**: Y/N
-with current software and should be set to N.
+  * **Processing Options**: Process spool file under the iView user profile or under the profile of the spool file owner. This will impact what profile owns the spool file post-processing.
-  * **Processing Options**: Process spool file under the iView user profile or under the profile of the spool file owner.
-This will impact what profile owns the spool file post-processing.
 <html><pre>
   *SYSTEM        Use iView System Profile
@@ Line 117: / Line 117: @@
 </pre></html>
-iDocs Application: If you want the spool file processed through iDocs before archiving specify the
+  * **iDocs Application**: If you want the spool file processed through iDocs before archiving specify the application here. If specified what is archived is a laser document, else it is a pdf document made from the text spool file.
-application here. If specified what is archived is a laser document, else it is a pdf document made from the
+  * **Storage Format**: Specify the document type of the file. *PDF is the usual selection due to ease of use with a browser. PDF is also the front end default and any other selection may require front end configuration changes. The use of *PDFSIG enables signature capture in the archive.
-text spool file.
-Product: Specify IDOCS to create a laser document using the iDocs Suite. Otherwise leave blank.
-This field is used for integrations with other document products.
-Storage Format: Specify the document type of the file. *PDF is the usual selection due to ease of use
-with a browser. PDF is also the front end default and any other selection may require front end configuration changes.
 <html><pre>
-  *PDF           *USERASCII PDF Conversion
+*PDF       *USERASCII PDF Conversion
-  *TIFF          Tiff Image
+*PDFSIG    PDF Convert for Signature
+*TIFF      Tiff Image
 </pre></html>
+  * **Product**: Specify IDOCS to create a laser document using the iDocs Suite. Otherwise leave blank. This field is used for integrations with other document products.
+  * **Printing Queue (Signature)** Printing queue and queue library are specified to hold the output from the print option in signature capture. This is unconditional. Multiple and conditional print output from Signature Capture can also be configured using **F18**.
 === Meta Data Fields ===
 The meta data fields are defined by their position in a *SCS spool file.
@@ Line 135: / Line 133: @@
-**Page#**: Use keywords *FIRST, *LAST, *ALL, or a specific page number to specify from which page the meta data\\
+**Sorting** is specified as it is in iDocs:
-value is scraped.
-**No. Pgs Indexed**: Key the number of pages from which spool text is scraped and concatenated to form the \\
-meta data for the meta data field. Left blank, 1 page is scraped unless *ALL pages is specified.
-Sorting is specified as it is in iDocs:
 <html><pre>
           Primary Sort Ascending
@@ Line 154: / Line 145: @@
           Fifth Sort Ascending
 </pre></html>
+Since this is text against which users will search in a browser, the normal practice
+is to define short, one line text fields as meta data. Fields such as customer name, customer number, etc.
+You can define text blocks as meta data but the searching dynamics should be considered.
+\\
+Meta data is stored in the meta data file, having the same name as the archive application, in the iView library.
+**Bursting** works as it does in iDocs and as one would intuitively expect.
+**Sigtag**: Specify a Y to display this field on the Signature Capture search dialog. You should define at least one field as sigtag for a Signature Capture application ( see Storage Format above ).
+**Page#**: Use keywords *FIRST, *LAST, *ALL, or a specific page number to specify from which page the meta data\\
+value is scraped.
+**No. Pgs Indexed**: Key the number of pages from which spool text is scraped and concatenated to form the \\
+meta data for the meta data field. Left blank, 1 page is scraped unless *ALL pages is specified.
+**Type**: Specify blank or A for an alpha string. Specify D for a date field. If a date field, use **F11** to enter a date format. The format specified should match the format in the spool file -- i.e. tell iView how to parse the spool file date.\\
 Since this is text against which users will search in a browser, the normal practice
@@ Line 369: / Line 378: @@
   * **6**: Reprocess
-==== Menu IVIEW, option 10:====
+==== Menu IVIEW, option 10:iView Servers (Engines) ====
- Work with iView Servers
+iView servers are defined from menu IVIEW, option 10.
+iView engines are architected similarly to iDocs engines in that they are single threaded, and you can define and run an unlimited number of them in any subsystem.
+  * **1**: Select
+  * **2**: Copy
+  * **4**: Delete
+  * **7**: Rename
+  * **8**: Start Server
+  * **9**: End Server
 <html><pre>
-/05/18                          iView                              IV2000C1
+/30/18                          iView                              IV2000C1
-:42:56                      Engine Maintenance                     KKRAMER
+:38:24                      Engine Maintenance                     KKRAMER
  Type options, press Enter.
@@ Line 396: / Line 413: @@
   F3=Exit   F5=Refresh   F6=Add
 </pre></html>
-  * **1**: Select
+Select the appropriate engine with option 1:
-  * **2**: Copy
+<html><pre>
-  * **4**: Delete
+/30/18                          iView                              IV2000C2
-  * **7**: Rename
+:39:58                    Engine Maintenance                       KKRAMER
-  * **8**: Start Server
-  * **9**: End Server
+ Edit Engine . . . . . . . . . : BOYDIVWENG Boyd Check iView Engine
+ Spool File Endpoint . . . . . : OFERRER    / ARCHIVIEW  Name
+ Data Queue. . . . . . . . . . : QUSRSYS    / BOYDIVWDTQ
+ Engine processing log : N Y/N
+ Process SPLF in Separate Job: N Y/N
+   Job Queue / Library:            / *LIBL       Job Priority: *JOBD
+    AND   ----- Originating -----   Spool        Spool        Archive
+    OR    Library      Queue Name   Attribute    Value        Application
+          OFERRER      ARCHIVE2     *SPLFILE     AP290A#      BOYDCHECK
+                                                                        More...
+  F3=Exit   F10=Save   F12=Cancel
+</pre></html>
+  * **Archive Original Spool File To**: This is the endpoint for the original spool file.
+  * ** Data Queue**: Provide a name and library for the engine's data queue. This must be unique. The engine will create it if it is not present at engine startup. A dataqueue is a filesystem object.
+  * **Originating Outqueue and Library**: This is the monitored outqueue. Note that you can not have multiple dataqueue engines monitoring one outqueue.
+  * **Spool Attribute**: Specify the external spool file attribute to test to recognize the spool file and select the correct archive application. Specify one of:
+| *FORM    |   Original Spool Form Type   |
+| *USRPRF  |   User Profile of Spool      |
+| *JOBNAME |   Job Name of the Spool      |
+| *SPLFILE |   Print File Name            |
+| *USRDTA  |   User data Value in Spool   |
+  * **Spool Value**: Specify the specific value to test the selected external spool file attribute against.
+  * **Archive Application**: Prompt for and select the archive application to process the spool file for which the specified external spool file attribute matches the provided value.
+You can have an unlimited number of engines in iView. You may define up to 9,999 engines in this dialog.
+Use option 8 and 9 to start and stop the engines:
+<html><pre>
+                         Start iView Server (STRIVWSRV)
+ Type choices, press Enter.
+ iView Server Name  . . . . . . . > IVIEWSEVER    Value, or F4 for list
+ User . . . . . . . . . . . . . .   *CURRENT      Name, IVIEW, *CURRENT
+ Job queue  . . . . . . . . . . .   *JOBD         Name, *JOBD
+ Save job log . . . . . . . . . .   *NO           *YES, *NO
+                                                                         Bottom
+ F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display
+ F24=More keys
+</pre></html>
+  * **User**: user profile to run the engine. This profile must have ***JOBCTL** and ***SPLCTL** authority, and if it is running iDocs merges must also have a profile define in the system directory.
+  * **Job Queue**: Job queue to which the engine is submitted. This can be any queue leading to a batch subsystem.
+  * **Save Job Log**: If you want the log saved, enter *YES. In normal production this would not be necessary.
 ===== Menu IVIEWADM: =====