pub:iview8setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
pub:iview8setup [2018/08/30 13:02] – [Installation and Configuration] kkramer | pub:iview8setup [2020/04/20 13:44] – [Front end - Apache Tomcat] kkramer | ||
---|---|---|---|
Line 4: | Line 4: | ||
- | iView version 8 is significantly different than it's previous versions. | + | iView version 8 is significantly different than it's previous versions |
===== Installation and Configuration ===== | ===== Installation and Configuration ===== | ||
- | Iview is comprised of two parts: | + | iView is comprised of two parts: |
- | Apache Tomcat is used to deploy your Java Servlets and JSPs. So in your Java project you can build your WAR (short for Web ARchive) file, and just drop it in the deploy directory in Tomcat. So basically Apache is an HTTP Server, serving HTTP. Tomcat is a Servlet and JSP Server serving Java technologies. | + | |
- | The iView back end is typically provided in a savefile. To install, upload the savefile to the IBM i and restore it with a command like this ( you will need to populate this command with the names you are using on your system ): | + | ==== Front end - Apache Tomcat ==== |
- | + | ==Download iView WAR file== | |
- | < | + | The iView front end is typically provided in a war file. Download |
- | RSTLIB SAVLIB(IVIEW800) DEV(*SAVF) SAVF(QGPL/ | + | |
- | </ | + | |
- | + | ||
- | Add the iView library to the top of the library list and execute | + | |
- | + | ||
- | < | + | |
- | | + | |
- | | + | |
- | iView Archive Applications | + | |
- | 1. Work with iView Applications | + | |
- | 2. Work with iView Processing Log CALL IVRELOG | + | |
- | + | ||
- | iView Server | + | |
- | 10. Work with iView Servers | + | |
- | + | ||
- | | + | |
- | 20. Work with Administrative Menu GO IVIEWADM | + | |
- | + | ||
- | | + | |
- | | + | |
- | + | ||
- | + | ||
- | | + | |
- | </ | + | |
- | + | ||
- | Take option 20, then option 8 to set the iView location and path. Set the parameters as appropriate to your installation | + | |
- | + | ||
- | < | + | |
- | | + | |
- | + | ||
- | Type choices, press Enter. | + | |
- | + | ||
- | iView Library | + | |
- | iView IFS path . . . . . . . . . | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | | + | |
- | | + | |
- | | + | |
- | + | ||
- | </pre></html> | + | |
==Download Tomcat distribution file== | ==Download Tomcat distribution file== | ||
Download Tomcat 6.x from FTP site at:\\ | Download Tomcat 6.x from FTP site at:\\ | ||
- | | + | |
- | and upload | + | |
+ | and upload | ||
- | Change your current working directory to /www then decompress Tomcat distribution file using qshell command: | ||
< | < | ||
+ | call qp2term | ||
+ | cd /www | ||
ajar -x / | ajar -x / | ||
</ | </ | ||
+ | |||
==Add environment variable JAVA_HOME at system level== | ==Add environment variable JAVA_HOME at system level== | ||
Set JAVA_HOME environment variable: go to directory / | Set JAVA_HOME environment variable: go to directory / | ||
Line 74: | 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== | ||
- | Tomcat uses 8005, 8080, and 8009 by default among which 8080 is the default HTTP port. Enter the command NETSTATOPTION(*CNN) to verify whether the ports are in use. If port 8009 and 8080 are occupied, edit the configuration file / | + | Tomcat uses 8005, 8080, and 8009 by default among which 8080 is the default HTTP port. Enter the command NETSTATOPTION(*CNN) to verify whether the ports are in use. If port 8009 and 8080 are occupied, edit the configuration file / |
- | << | + | {{: |
==Change security for Tomcat folder== | ==Change security for Tomcat folder== | ||
Type command: | Type command: | ||
Line 90: | Line 50: | ||
< | < | ||
< | < | ||
- | << | + | {{: |
==Start Tomcat== | ==Start Tomcat== | ||
Tomcat is installed and configured successfully. Now you can start Tomcat by using command: (Where the job queue is where you want to run Tomcat) | Tomcat is installed and configured successfully. Now you can start Tomcat by using command: (Where the job queue is where you want to run Tomcat) | ||
< | < | ||
- | STRTOMCAT JOBQ | + | STRTOMCAT JOBQ(FMGJOBQ) |
</ | </ | ||
- | And open your web browser, enter the URL [[http:// | + | To open your web browser, enter the URL [[http:// |
- | << | + | {{: |
==Stop Tomcat== | ==Stop Tomcat== | ||
Use command **ENDTOMCAT** to stop Tomcat | Use command **ENDTOMCAT** to stop Tomcat | ||
- | The iView front end is typically provided in a war file. Download this file to your home directory in the IFS using **binary** file transfer, | + | ==== Back end - IBMi ==== |
+ | The iView back end is typically provided in a savefile. To install, upload the savefile | ||
< | < | ||
- | call qp2term | + | RSTLIB SAVLIB(IVIEW844) DEV(*SAVF) SAVF(QGPL/IVIEW844) MBROPT(*ALL) ALWOBJDIF(*ALL) |
- | cd /home/user | + | |
- | tar -xf iView8.00-FrontEnd-Php5.4.tar | + | |
- | cd / | + | |
- | find . -type d -print | xargs chmod 755 | + | |
- | find . -type f -print | xargs chmod 644 | + | |
- | chmod 666 i5_def.php | + | |
- | chown -R qtmhhttp | + | |
</ | </ | ||
- | You should now add the following stanza | + | Add the iView library |
- | This file is / | + | |
< | < | ||
- | & | + | IVIEW iView Version 8.44 02.20.18 |
- | PasswdFile %%SYSTEM%% | + | System: |
- | AuthType Basic | + | iView Archive Applications |
- | AuthName "i5 User Profile" | + | 1. Work with iView Applications |
- | | + | 2. Work with iView Processing Log CALL IVRELOG |
- | | + | |
- | & | + | |
- | </ | + | |
- | + | ||
- | These statements establish browser authentication against the IBM i profile. iView will not work without user authentication. You may establish user authentication through any means that Apache will allow. | + | |
- | + | ||
- | At this point, if your machine' | + | |
- | + | ||
- | If this is an upgrade, you can migrate the meta data files, configuration and license keys with the command IVCOPYDATA. | + | |
- | + | ||
- | < | + | |
- | | + | |
| | ||
- | Type choices, press Enter. | + | iView Server |
+ | 10. Work with iView Servers | ||
| | ||
- | | + | |
- | New iView Library | + | 20. Work with Administrative Menu GO IVIEWADM |
- | | + | |
| | ||
+ | | ||
+ | | ||
| | ||
- | | ||
- | | ||
- | | ||
| | ||
+ | | ||
</ | </ | ||
- | + | ==== Enter License Keys and Set Location | |
- | 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. | + | 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. |
- | + | ||
- | + | ||
- | ===== Archive Configuration ===== | + | |
- | + | ||
- | + | ||
- | Menu IVIEW, option 1: | + | |
< | < | ||
- | 8/ | + | 8/ |
- | 10:17:09 iView Archive Application | + | 14:02:21 iDocs Installation Library Set |
| | ||
- | Type options, press Enter. | + | System Information |
- | | + | |
- | | + | |
| | ||
- | | + | |
- | | + | |
- | Opt Application Description | + | |
- | ATPICKLIST | + | |
- | | + | Location settings |
- | | + | |
- | | + | |
- | BOYDTABLE | + | |
- | BOYDTOFLOW | + | |
- | BROCKAPIVW | + | |
- | CARBSTMT | + | |
- | | + | |
- | | + | |
- | | + | |
- | 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 | ||
- | | ||
| | ||
+ | | ||
+ | | ||
+ | Press enter to continue | ||
+ | | ||
</ | </ | ||
- | * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended. | + | Press <Enter> and then **F6** to add the 3 iView License keys: |
- | * **Description**: | + | |
- | * **Library**: | + | |
- | | + | |
- | * **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: | + | |
< | < | ||
- | | + | |
- | *ORIGINAL | + | 14: |
- | | + | |
- | | + | |
- | </ | + | |
+ | |||
+ | | ||
+ | |||
+ | | ||
+ | |||
+ | | ||
- | * **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. | + | |
- | < | + | |
- | | + | |
- | *SPLFOWNER | + | |
</ | </ | ||
+ | Then use option 8 to set the iView location and path. Set the parameters as appropriate to your installation or upgrade and press < | ||
- | * **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 | + | |
- | + | ||
- | **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/ | + | |
- | | + | |
| | ||
- | | + | |
- | 1=Select | + | |
| | ||
- | Position to Name | + | iView Library |
+ | iView IFS path . . . . . . . . . | ||
| | ||
- | 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 | ||
| | ||
+ | | ||
+ | | ||
+ | | ||
+ | |||
</ | </ | ||
- | + | ==== Migrating Any Meta Data Files ==== | |
- | * **Archive Original Spool File To**: This is the endpoint for the original spool file. | + | If this is an upgrade, |
- | * ** 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: | + | |
< | < | ||
- | | + | |
| | ||
Type choices, press Enter. | Type choices, press Enter. | ||
| | ||
- | | + | Current |
- | User . . . . . . . . . . . . . . *CURRENT | + | New iView Library |
- | Job queue . . . . . . . . . . . *JOBD | + | Action on Metadata Files . . . . *copy *MOVE, *COPY, *NONE |
- | Save job log . . . . . . . . . . *NO *YES, *NO | + | |
| | ||
| | ||
Line 382: | Line 172: | ||
</ | </ | ||
- | | + | The use of ***MOVE** rather than ***COPY** for the meta data files may be appropriate |
- | * **Job Queue**: Job queue to which the engine is submitted. This can be any queue leading | + | |
- | | + | |
\\ | \\ |
pub/iview8setup.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1