pub:iview8be
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
pub:iview8be [2018/09/04 18:27] – kkramer | pub:iview8be [2018/09/05 15:18] – [FTP Log File] kkramer | ||
---|---|---|---|
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:==== |
< | < | ||
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. | * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended. | ||
Line 124: | Line 128: | ||
*TIFF Tiff Image | *TIFF Tiff Image | ||
</ | </ | ||
- | **F8=Metadata Monitor:** | + | === 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 < | ||
+ | |||
+ | |||
+ | **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. | ||
+ | |||
+ | |||
+ | 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, | ||
+ | |||
+ | ==== F8=Metadata Monitor | ||
< | < | ||
Line 151: | Line 188: | ||
| | ||
</ | </ | ||
- | **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 243: | ||
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 275: | ||
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 335: | ||
| | ||
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:==== | ||
+ | Work with iView Servers | ||
+ | < | ||
+ | 9/ | ||
+ | | ||
+ | | ||
+ | Type options, press Enter. | ||
+ | 1=Select | ||
+ | | ||
+ | | ||
+ | | ||
+ | Opt Engine | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | More... | ||
+ | F3=Exit | ||
+ | </ | ||
+ | * **1**: Select | ||
+ | * **2**: Copy | ||
+ | * **4**: Delete | ||
+ | * **7**: Rename | ||
+ | * **8**: Start Server | ||
+ | * **9**: End Server | ||
+ | ===== Menu IVIEWADM: ===== | ||
- | |||
- | |||
- | ===== 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 < | ||
- | |||
- | |||
- | **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. | ||
- | |||
- | |||
- | 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