pub:iview8be
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:iview8be [2018/09/04 18:27] – kkramer | pub:iview8be [2022/06/25 17:02] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
====== iView 8 IBMi (back end) Usage ====== | ====== iView 8 IBMi (back end) Usage ====== | ||
- | **Menu IVIEW:** | + | ===== Menu IVIEW: |
< | < | ||
Line 30: | Line 30: | ||
| | ||
</ | </ | ||
- | **Menu IVIEW, option 1:** | + | ==== Menu IVIEW, option 1: Archive Configuration ==== |
+ | This display is used to add or change an archive definition. | ||
< | < | ||
9/ | 9/ | ||
Line 57: | Line 57: | ||
F3=Exit | F3=Exit | ||
</ | </ | ||
- | **Select an iView Archive Application with option 1:** | + | If the metadata file is being monitored, you will see an indicator at Archive list screen:\\ |
+ | | ||
+ | * **U**: monitoring for Updating event | ||
+ | * **D**: monitoring for Deleting event | ||
+ | ==== Select an iView Archive Application with option 1:===== | ||
< | < | ||
Line 85: | Line 89: | ||
</ | </ | ||
- | ===== Archive Options | + | === Archive Options === |
- | | + | * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended. |
+ | * **Description**: | ||
* **Library**: | * **Library**: | ||
* **Directory**: | * **Directory**: | ||
- | * **File Name**: Specify the file system object name of the archived document using constants and these keywords: | + | * **PDF Output |
- | < | + | |
- | *DATE to include QDATE | + | | *NAME | The archive name | |
- | *TIME to include QTIME | + | | *DATE | Processing date in format YYMMDD | |
- | *INDEX01 | + | | *TIME | Processing time in format HHMMSS | |
- | </ | + | | *INDEX01 |
* **Disposition Options**: This controls the fate of the original spool file: | * **Disposition Options**: This controls the fate of the original spool file: | ||
< | < | ||
- | *RETAIN | + | *RETAIN |
*ORIGINAL | *ORIGINAL | ||
*SYSTEM | *SYSTEM | ||
*NONE Do Not Archive | *NONE Do Not Archive | ||
</ | </ | ||
- | + | | |
- | | + | * **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. | + | |
< | < | ||
*SYSTEM | *SYSTEM | ||
Line 113: | Line 117: | ||
</ | </ | ||
- | iDocs Application: | + | * **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. | + | |
< | < | ||
- | | + | *PDF |
- | *TIFF Tiff Image | + | *PDFSIG |
+ | *TIFF Tiff Image | ||
</ | </ | ||
- | **F8=Metadata Monitor:** | + | |
+ | * **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. | ||
+ | |||
+ | **Seq#**: You can change the order of the columns of the meta data table by keying a different sequence number\\ | ||
+ | and pressing < | ||
+ | |||
+ | |||
+ | **Sorting** is specified as it is in iDocs: | ||
+ | < | ||
+ | 1 Primary Sort Ascending | ||
+ | 2 Primary Sort Descending | ||
+ | 3 Secondary Sort Ascending | ||
+ | 4 Secondary Sort Descending | ||
+ | 5 Third Sort Ascending | ||
+ | 6 Third Sort Descending | ||
+ | 7 Forth Sort Ascending | ||
+ | 8 Forth Sort Descending | ||
+ | 9 Fifth Sort Ascending | ||
+ | </ | ||
+ | |||
+ | 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, | ||
+ | |||
+ | **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 | ||
+ | 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, | ||
+ | |||
+ | ==== F8=Metadata Monitor | ||
< | < | ||
Line 151: | Line 197: | ||
| | ||
</ | </ | ||
- | **F11=Alt View:** | + | < |
+ | Monitor archive data changes (STRIVMONAR) | ||
+ | |||
+ | Type choices, press Enter. | ||
+ | |||
+ | Mail Subject (*INDEXxx) | ||
+ | |||
+ | |||
+ | iMail Job Queue . . . . . . . . | ||
+ | | ||
+ | iMail Library Name . . . . . . . > IDOCS6 | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
+ | ==== F11=Alt View: ==== | ||
< | < | ||
Line 181: | Line 252: | ||
change the meta data fields after the archive is created.\\ | change the meta data fields after the archive is created.\\ | ||
- | **F14=FTP Definition:** | + | ==== F14=FTP Definition: |
+ | |||
+ | iView can be configured to ftp the document that it is about to archive, and optionally an exported text file of the index values of the document, to a remote host. | ||
+ | |||
+ | At the time of archiving, which is after sorting and bursting and after any specified iDocs merge, iView will initiate an FTP session with the specified host and transfer the archived document to the specified host and directory. Optionally it will export the index values for that document in a text file. The original document is then archived in iView. | ||
< | < | ||
Line 208: | Line 284: | ||
F3=Exit | F3=Exit | ||
</ | </ | ||
- | **F18=Signature Output Routing:** | + | |
+ | * **User**: | ||
+ | * **Password**: | ||
+ | * **Directory**: | ||
+ | * **System Type**: | ||
+ | * **AS/400 Namefmt**: 0 for the DB2/400 file system and 1 for the Integrated File System format. | ||
+ | * **Log Lib/ | ||
+ | * **Log Level**: | ||
+ | * **Job Queue**: | ||
+ | * **Export Index File**: If *YES specified iView will create a text file containing the iView archive fields and their values for the document separated by a space, and will ftp this file to the same target with the archived document. The file name is the same as the archived document except that the file extension is **.txt**. This file is not retained on the System i. | ||
+ | * **Post FTP Cmd**: | ||
+ | |||
+ | |||
+ | === FTP Log File === | ||
+ | |||
+ | iView FTP logs into a file if logging is specified, by default FTPLOG. The file format is: | ||
+ | |||
+ | < | ||
+ | |||
+ | A R FTPLOGR | ||
+ | A LPROCESSED | ||
+ | A LTIMESTAMP | ||
+ | A LHOST 128A | ||
+ | A LFILE 128A | ||
+ | A LLOGDATA | ||
+ | |||
+ | </ | ||
+ | |||
+ | * **LPROCESSED**: | ||
+ | * **LTIMESTAMP**: | ||
+ | * **LHOST**: | ||
+ | * **LFILE**: | ||
+ | * **LLOGDATA**: | ||
+ | |||
+ | ==== F18=Signature Output Routing: | ||
< | < | ||
Line 234: | Line 344: | ||
| | ||
F3=Exit | F3=Exit | ||
+ | </ | ||
+ | ==== Menu IVIEW, option 2:==== | ||
+ | Work with iView Processing Log | ||
+ | < | ||
+ | 9/ | ||
+ | | ||
+ | | ||
+ | Type options, press Enter. | ||
+ | 1=Detail | ||
+ | | ||
+ | | ||
+ | Opt Name | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | F3=Exit | ||
</ | </ | ||
+ | * **1**: Details | ||
+ | * **4**: Delete | ||
+ | * **5**: Work With | ||
+ | * **6**: Reprocess | ||
+ | | ||
+ | ==== Menu IVIEW, option 10:iView Servers (Engines) ==== | ||
+ | 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 | ||
+ | < | ||
+ | 8/ | ||
+ | | ||
+ | | ||
+ | Type options, press Enter. | ||
+ | 1=Select | ||
+ | | ||
+ | | ||
+ | | ||
+ | Opt Engine | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | F3=Exit | ||
+ | </ | ||
+ | Select the appropriate engine with option 1: | ||
+ | < | ||
+ | 8/ | ||
+ | | ||
+ | | ||
+ | Edit Engine . . . . . . . . . : BOYDIVWENG Boyd Check iView Engine | ||
+ | Spool File Endpoint . . . . . : OFERRER | ||
+ | Data Queue. . . . . . . . . . : QUSRSYS | ||
+ | | ||
+ | | ||
+ | Job Queue / Library: | ||
+ | AND ----- Originating ----- | ||
+ | OR Library | ||
+ | OFERRER | ||
+ | | ||
+ | More... | ||
+ | F3=Exit | ||
+ | | ||
+ | </ | ||
+ | * **Archive Original Spool File To**: This is the endpoint for the original spool file. | ||
+ | * ** Data Queue**: Provide a name and library for the engine' | ||
+ | * **Originating Outqueue and Library**: This is the monitored outqueue. Note that you can not have multiple dataqueue engines monitoring one outqueue. | ||
+ | * **Spool Attribute**: | ||
+ | |||
+ | | *FORM | | ||
+ | | *USRPRF | ||
+ | | *JOBNAME | Job Name of the Spool | | ||
+ | | *SPLFILE | Print File Name | | ||
+ | | *USRDTA | ||
+ | * **Spool Value**: Specify the specific value to test the selected external spool file attribute against. | ||
+ | * **Archive Application**: | ||
- | ===== Meta Data Fields ===== | ||
- | The meta data fields are defined by their position | + | You can have an unlimited number of engines |
- | **Seq#**: You can change the order of the columns of the meta data table by keying a different sequence number\\ | + | Use option 8 and 9 to start and stop the engines: |
- | and pressing < | + | |
+ | < | ||
+ | Start iView Server (STRIVWSRV) | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | iView Server Name . . . . . . . > IVIEWSEVER | ||
+ | User . . . . . . . . . . . . . . | ||
+ | Job queue . . . . . . . . . . . | ||
+ | Save job log . . . . . . . . . . | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
- | **Page#**: Use keywords | + | |
- | value is scraped. | + | * **Job Queue**: Job queue to which the engine |
- | + | * **Save Job Log**: If you want the log saved, enter *YES. In normal production this would not be necessary. | |
- | **No. Pgs Indexed**: Key the number of pages from which spool text is scraped and concatenated | + | |
- | meta data for the meta data field. Left blank, 1 page is scraped unless | + | |
+ | ===== Menu IVIEWADM: ===== | ||
- | Sorting is specified as it is in iDocs: | ||
< | < | ||
- | 1 Primary Sort Ascending | + | |
- | | + | |
- | | + | Configuration Options |
- | | + | 8. Change iView Library & IFS Path |
- | | + | |
- | | + | Maintenance Options |
- | | + | 10. Purge iView Indices |
- | | + | |
- | | + | |
+ | | ||
+ | |||
+ | 90. Signoff | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | | ||
+ | |||
+ | |||
+ | | ||
+ | © Copyright 1994-2007 inFORM Decisions, | ||
</ | </ | ||
+ | ==== Menu IVIEWADM, option 8:==== | ||
+ | Use option 8 to set the iView location and path. Set the parameters as appropriate to your installation or upgrade and press < | ||
- | 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. | + | Change iView Library & IFS Dir (CHGIVWLIB) |
- | You can define text blocks as meta data but the searching dynamics should be considered. | + | |
- | \\ | + | Type choices, press Enter. |
- | Meta data is stored in the meta data file, having the same name as the archive application, | + | |
+ | iView Library | ||
+ | | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | | ||
+ | | ||
+ | | ||
- | Bursting works as it does in iDocs and as one would intuitively expect. | + | </ |
+ | ==== Menu IVIEWADM, option 10:==== | ||
+ | Purge iView Indices | ||
+ | < | ||
+ | Purge iView Index (PRGIVWIDX) | ||
+ | | ||
+ | Type choices, press Enter. | ||
+ | | ||
+ | | ||
+ | Purge Older/Newer MM/DD/YYYY . . | ||
+ | Purge Indices Older/Newer Days | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
- | ===== Path Variables ===== | + | ==== Menu IVIEWADM, option 20:==== |
+ | Take option 20, then press enter to enter the permanent or temporary license provided by your account manager. iView should have 3 key components: IVIEWWEB, IVIEW1, IVIEW2. Once entered, iView is now ready to use. | ||
- | {{pub:iview6:iview6archivepathdef.png?600|}} | + | < |
+ | 8/ | ||
+ | 14:02:21 iDocs Installation Library Set KKRAMER | ||
+ | |||
+ | | ||
+ | Serial Number: | ||
+ | |||
+ | iDocs Production Information | ||
+ | Product version | ||
+ | iDocs Installation Library: FMG Name, F4 for list | ||
+ | |||
+ | | ||
+ | Country Code . . . . . . .: US | ||
+ | Code Page. . . . . . . . .: 37 1-65535 | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | Press enter to continue | ||
+ | | ||
+ | </ | ||
+ | Press < | ||
+ | < | ||
+ | 8/ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
- | A path is defined to create a directory structure in the archive. The directories | + | |
- | are in the IFS and are real, not virtual. The archived document is placed in the path | + | |
- | created by the path definition. | + | |
- | + | ||
- | At archive time the engine creates a file path using the specified meta data fields, | + | |
- | creates the directories if they are not present, then places the archived document in the | + | </pre></html> |
- | path. | + | |
- | + | ||
- | Example: | + | |
- | + | ||
- | Archive application is INVOICES.\\ | + | |
- | *PATH01 is INDEX01, which evaluates to 100100 at archive time for a specific document.\\ | + | |
- | *PATH02 is INDEX02, which evaluates to 2013JANUARY at archive time.\\ | + | |
- | The iView IFS root is /iview6 ( data area DSIVIEWDIR ).\\ | + | |
- | + | ||
- | The archived document ( named 01000010001.pdf ) is placed thus:\\ | + | |
- | / | + | |
\\ | \\ |
pub/iview8be.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1