Differences

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

--- pub:iview8setup [2018/08/30 14:28] – [Front end - Apache Tomcat] kkramer
+++ pub:iview8setup [2022/06/25 17:02] (current) – external edit 127.0.0.1
@@ Line 8: / Line 8: @@
 ===== Installation and Configuration =====
-iView is comprised of two parts:  The **iView front end or Tomcat Server**, and the **back end running on the IBMi**.
+iView is comprised of two parts:  The **iView front end running on Tomcat Server (version 5.x or above)**, and the **back end running on the IBMi (V6R1 or above)**.
-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.
 ==== Front end - Apache Tomcat ====
+==Download iView WAR file==
+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, and then execute these commands ( populating the names with those used in your installation ). The directory /home/user is meant to refer to your user profile's home directory
 ==Download Tomcat distribution file==
 Download Tomcat 6.x from FTP site at:\\
- [[ftp:// ftp.informdecisions.com/ftpRoot/CustomerFTP/iView/apache-tomcat-6.0.39.zip]]\\
+ [[ftp://ftp.informdecisions.com/iView/apache-tomcat-6.0.39.zip]]\\
-and upload Tomcat distribution file to an IFS directory, for example /home/download. \\
+and upload this file to /home/user directory
-Change your current working directory to /www then decompress Tomcat distribution file using qshell command:
 <html><pre>
+call qp2term
+cd /www
 ajar -x /home/download/apache-tomcat-6.0.39.zip
 </pre></html>
 ==Add environment variable JAVA_HOME at system level==
 Set JAVA_HOME environment variable: go to directory /qibm/ProdData/Java400 and choose a JDK version that you want to set for JAVA_HOME, then type command:
@@ Line 28: / Line 33: @@
 With xyz is the JDK folder of the version you want to set.
 <html><pre>
-ADDENVVAR ENVVAR(JAVA_OPTS) VALUE(' -Dos400.awt.native=true -Djava.awt.headless=true -server
+ADDENVVAR ENVVAR(JAVA_OPTS) VALUE('-Dos400.awt.native=true -Djava.awt.headless=true -Dserver
--Xms1536m -Xmx3072m -XX:NewSize=256m -XX:MaxNewSize=1024m -XX:Perm Size=256m -XX:MaxPermSize=1024m') LEVEL(*SYS)
+-Xms1536m -Xmx3072m -XX:NewSize=256m -XX:MaxNewSize=1024m -XX:PermSize=256m -XX:MaxPermSize=1024m') LEVEL(*SYS)
 </pre></html>
 ==Verify the availability of the ports used by Tomcat==
@@ Line 49: / Line 54: @@
 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)
 <html><pre>
-STRTOMCAT JOBQ
+STRTOMCAT JOBQ(FMGJOBQ)
 </pre></html>
 To open your web browser, enter the URL [[http://your.server.name:8080]]
@@ Line 55: / Line 60: @@
 ==Stop Tomcat==
 Use command **ENDTOMCAT** to stop Tomcat
-==Download iView WAR file==
-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, and then execute these commands ( populating the names with those used in your installation ). The directory /home/user is meant to refer to your user profile's home directoryl
-<html><pre>
-call qp2term
-cd /home/user
-tar -xf iView8.00-FrontEnd-Php5.4.tar
-cd /www/zendsvr6/htdocs/iview800
-find . -type d -print | xargs chmod 755
-find . -type f -print | xargs chmod 644
-chmod 666 i5_def.php
-chown -R qtmhhttp
-</pre></html>
-You should now add the following stanza to the Apache configuration file used by the Zend Server.
-This file is /www/zendsvr6/conf/httpd.conf. You may append this to the file:
-<html><pre>
- &lt;LocationMatch "/iview*"&gt;
- 	        PasswdFile %%SYSTEM%%
- 	        AuthType Basic
- 	        AuthName "i5 User Profile"
- 	        Satisfy All
- 	        Require valid-user
- &lt;/LocationMatch&gt;
- </pre></html>
- 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's IP is 192.168.0.2 you should be able to point your browser at http://192.168.0.2/iview800 and get a response.
 ==== Back end - IBMi ====
 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 ):
 <html><pre>
-RSTLIB SAVLIB(IVIEW800) DEV(*SAVF) SAVF(QGPL/IVIEW800) MBROPT(*ALL) ALWOBJDIF(*ALL)
+RSTLIB SAVLIB(IVIEW844) DEV(*SAVF) SAVF(QGPL/IVIEW844) MBROPT(*ALL) ALWOBJDIF(*ALL)
 </pre></html>
@@ Line 114: / Line 91: @@
 </pre></html>
 ==== Enter License Keys and Set Location ====
-Take option 20, then option 10 and when prompted 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.
+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.
 <html><pre>
@@ Line 125: / Line 102: @@
  iDocs Production Information
     Product version . . . . . :
-    iDocs Installation Library: IDOCS6     Name, F4 for list
+    iDocs Installation Library: FMG       Name, F4 for list
  Location settings
@@ Line 158: / Line 135: @@
   F3=Exit   F10=Update   F12=Previous
 </pre></html>
-Take option 20, then option 8 to set the iView location and path. Set the parameters as appropriate to your installation or upgrade and press <enter> to update. These values are stored in the data areas DSIVIEWLIB (for iView Library) and DSIVIEWDIR (for iView IFS Path).
+Then use option 8 to set the iView location and path. Set the parameters as appropriate to your installation or upgrade and press <enter> to update. These values are stored in the data areas DSIVIEWLIB (for iView Library) and DSIVIEWDIR (for iView IFS Path).
 <html><pre>
@@ Line 196: / 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.
-===== Archive Configuration =====
-Menu IVIEW, option 1:
-<html><pre>
-/30/18                          iView                              IV1000C1
-:17:09                  iView Archive Application                  KKRAMER
- Type options, press Enter.
-=Select   3=Copy   4=Delete   7=Rename   8=Clone Archive Structure
-=Archive Spool File
- Position to              Name
-                                           Target  iDocs       Last    Monitor
- Opt Application Description               Format  Application Field   Event
-     ATPICKLIST  AllTrade Pick List        *PDF                INDEX04
-     AWINVOICE   Adel Wiggins In-bound Inv *PDF                INDEX07
-     AWTEST      Adel Wiggins Test         *PDF                INDEX03
-     BOYDCHECK   Boyd Gaming A/P Checks    *PDF    BOYD805     INDEX05
-     BOYDTABLE   Boyd Example Table        *PDF                INDEX04
-     BOYDTOFLOW  Boyd Gaming A/P Checks    *TIFF   BOYD805     INDEX05
-     BROCKAPIVW  BROCKAP Check             *PDF    BROCKAP     INDEX08
-     CARBSTMT    Seprod Statement          *PDF    CARB STMT   INDEX03
-     CJCINVOICE  Invoices incoming for A/P *PDF                INDEX09
-     DCYJOBLOG   Test Archive JobLog       *PDF                INDEX06
-     DCYTEST     DCY Testing               *PDF    *INDEX01    INDEX01
-                                                                        More...
-  F3=Exit   F5=Refresh   F6=Add
-</pre></html>
-This display is used to add or change an archive definition.
-===== Archive Options =====
-Option 1 to select:
-<html><pre>
-/30/18                          iView                              IV1000C3
-:18:07                  iView Archive Application                  KKRAMER
-  Application. . : ATPICKLIST   Description: AllTrade Pick List
-  Library. . . . : IVIEW7       Directory. : /iview
-  PDF Output Name: *NAME-*DATE-*TIME
-  Disposition Opt. *ORIGINAL    Table Import N Y/N      Allow Null Value N Y/N
-  Processing Opt.: *SYSTEM      iDocs App. :            Storage Format : *PDF
-  Product. . . . :              Printing Queue (Signature) *LIBL
-       Index   Field             From     To    So Bu- Sig        No. Pgs Ty
- Seq#  Field   Description      Row Col Row Col rt rst Tag Page#  Indexed pe Upd
-  INDEX01 Name               1   1   1  35  0  N   N  *FIRST          A  N
-  INDEX02 Warehouse Number   1   1   1  15  0  N   N  *FIRST          A  N
-  INDEX03 Date               1   1   1  10  0  N   N  *FIRST          A  N
-  INDEX04 FORMID             1   1   1  25  0  N   N  *FIRST          A  N
-                                            0  N      *FIRST          A  N
-                                            0  N      *FIRST          A  N
-                                            0  N      *FIRST          A  N
-                                            0  N      *FIRST          A  N
-                                                                        More...
-  F3=Exit   F8=Metadata Monitor   F10=Save   F11=Alt View   F12=Cancel
- F14=FTP Definition   F18=Signature Output Routing
-</pre></html>
-  * **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.
-  * **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:
-<html><pre>
-  *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.
-  * **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.
-<html><pre>
-  *SYSTEM        Use iView System Profile
-  *SPLFOWNER     Use Splf Owner Profile
-</pre></html>
-  * **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.
-  * **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.
-<html><pre>
-*PDF       *USERASCII PDF Conversion
-*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.
-**Seq#**: You can change the order of the columns of the meta data table by keying a different sequence number\\
-and pressing <enter>.
-**Sorting** is specified as it is in iDocs:
-<html><pre>
-          Primary Sort Ascending
-          Primary Sort Descending
-          Secondary Sort Ascending
-          Secondary Sort Descending
-          Third Sort Ascending
-          Third Sort Descending
-          Forth Sort Ascending
-          Forth Sort Descending
-          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.
-===== 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.
-<html><pre>
-/30/18                          iView                              IV2000C1
-:38:24                      Engine Maintenance                     KKRAMER
- Type options, press Enter.
-=Select   3=Copy   4=Delete   7=Rename   8=Start   9=End
- Position to              Name
- Opt Engine      Description                --- Archive Queue --- Status
-     BOYDIVWENG  Boyd Check iView Engine    ARCHIVIEW  OFERRER
-     BROCKAPSVR  BROCKAP iView Engine       BROCK      *SAME
-     CARBSTMTEN  Seprod Engine              SEPROD     QASPLFL
-     CDATEST     CDA Test                   ARCHIVE    IDOCS6
-     DCYIVWSRV   DCY iView Server           OUTQARC    DCYQC
-     DEMOENGINE  Demo Engine                ARCHIVE    *SAME
-     DENSOIVENG  Denso-Diam iView Engine    ARCHIVIEW  OFERRER
-     GRABBERENG  Grabber Form               ANGUYEN    QGPL
-     HOPINVENG   Hops Invoice Engine        ARCHIVE    OFERRER
-     IVIEWSEVER  Testing iView Server                  *LIBL
-     IVIEWSEVE2  Testing iView Server       IVWARCH    *SAME
-     IVIEWSRV1   Testing iView Server       GRABBER    *SAME
-                                                                        More...
-  F3=Exit   F5=Refresh   F6=Add
-</pre></html>
-Select the appropriate engine with option 1:
-<html><pre>
-/30/18                          iView                              IV2000C2
-:39:58                    Engine Maintenance                       KKRAMER
- 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.
 \\