pub:iview8setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pub:iview8setup [2018/09/05 11:13] – [Enter License Keys and Set Location] kkramer | pub:iview8setup [2022/06/25 17:02] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 33: | Line 33: | ||
With xyz is the JDK folder of the version you want to set. | With xyz is the JDK folder of the version you want to set. | ||
< | < | ||
- | ADDENVVAR ENVVAR(JAVA_OPTS) VALUE(' | + | ADDENVVAR ENVVAR(JAVA_OPTS) VALUE(' |
- | -Xms1536m -Xmx3072m -XX: | + | -Xms1536m -Xmx3072m -XX: |
</ | </ | ||
==Verify the availability of the ports used by Tomcat== | ==Verify the availability of the ports used by Tomcat== | ||
Line 173: | Line 173: | ||
The use of ***MOVE** rather than ***COPY** for the meta data files may be appropriate if the meta data files are large. Note that the archived documents themselves, in the IFS, are not normally moved. You can copy them to a new location if you wished with the shell command **cp -R**. See system documentation regarding the use of that command. | The use of ***MOVE** rather than ***COPY** for the meta data files may be appropriate if the meta data files are large. Note that the archived documents themselves, in the IFS, are not normally moved. You can copy them to a new location if you wished with the shell command **cp -R**. See system documentation regarding the use of that command. | ||
- | |||
- | |||
- | ===== Archive Configuration ===== | ||
- | |||
- | |||
- | Menu IVIEW, option 1: | ||
- | |||
- | < | ||
- | 8/ | ||
- | | ||
- | | ||
- | Type options, press Enter. | ||
- | 1=Select | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | Opt Application Description | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | More... | ||
- | F3=Exit | ||
- | </ | ||
- | |||
- | |||
- | |||
- | This display is used to add or change an archive definition. | ||
- | |||
- | |||
- | |||
- | ===== Archive Options ===== | ||
- | |||
- | Option 1 to select: | ||
- | |||
- | < | ||
- | 8/ | ||
- | | ||
- | | ||
- | Application. . : ATPICKLIST | ||
- | Library. . . . : IVIEW7 | ||
- | PDF Output Name: *NAME-*DATE-*TIME | ||
- | Disposition Opt. *ORIGINAL | ||
- | Processing Opt.: *SYSTEM | ||
- | Product. . . . : Printing Queue (Signature) *LIBL | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | More... | ||
- | F3=Exit | ||
- | | ||
- | | ||
- | </ | ||
- | * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended. | ||
- | * **Description**: | ||
- | * **Library**: | ||
- | * **Directory**: | ||
- | * **PDF Output Name**: Specify the file system object name of the archived document using constants and these keywords:\\ | ||
- | |||
- | | *NAME | The archive name | | ||
- | | *DATE | Processing date in format YYMMDD | | ||
- | | *TIME | Processing time in format HHMMSS | | ||
- | | *INDEX01 to *INDEX20 | Contents of meta data fields | | ||
- | |||
- | * **Disposition Options**: This controls the fate of the original spool file: | ||
- | < | ||
- | *RETAIN | ||
- | *ORIGINAL | ||
- | *SYSTEM | ||
- | *NONE Do Not Archive | ||
- | </ | ||
- | |||
- | * **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. | ||
- | * **Allow Null Value**: Y/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. | ||
- | < | ||
- | *SYSTEM | ||
- | *SPLFOWNER | ||
- | </ | ||
- | |||
- | * **iDocs Application**: | ||
- | * **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. | ||
- | < | ||
- | *PDF | ||
- | *PDFSIG | ||
- | *TIFF Tiff Image | ||
- | </ | ||
- | * **Product**: | ||
- | * **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. | ||
- | |||
- | ===== iView Servers (Engines) ===== | ||
- | |||
- | iView servers are defined from menu IVIEW, option 10. | ||
- | |||
- | iView 8 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. | ||
- | < | ||
- | 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**: | ||
- | |||
- | |||
- | 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: | ||
- | |||
- | < | ||
- | Start iView Server (STRIVWSRV) | ||
- | | ||
- | Type choices, press Enter. | ||
- | | ||
- | iView Server Name . . . . . . . > IVIEWSEVER | ||
- | User . . . . . . . . . . . . . . | ||
- | Job queue . . . . . . . . . . . | ||
- | Save job log . . . . . . . . . . | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | | ||
- | </ | ||
- | |||
- | * **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. | ||
- | |||
\\ | \\ |
pub/iview8setup.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1