This page is under construction and should not be deemed reliable or complete

This is the third option from the entrance page.

The license key file is uploaded through a dialog at the top. The Zend Server ID that is licensed will appear in green.

• iView Schema: The name of the iView library, not infrequently IVIEW.
• iView Archive Root: The root directory of the document store. Usually /iview/. Use leading and trailing slashes.
• iView Script URL: The script directory relative to document root. Usually /iview/. Use leading and trailing slashes.
• Database: Name of the DB2 database. Usually *LOCAL.
• DB User Name: Name of a user to connect to the DB2 database.
• DB User Password: User's password.
• IBM i5 Server IP:Port: Use format 999.999.999.999:99999, or valid IPv6 equivalent.
• iView Admin Profile: *ANYONE or user profile. This profile can configure the archives and administer archive permissions.
• iMail Library: library containing iMail, or blank if not present.
• Jobqueue library/name: Job queue to submit emails to iMail, if present. A multi-threaded jobqueue is better.
• Log file library/name: Usually the file is named WEBLOG and put in the iView library, as specified above. iView does not maintain or rotate this log.
• Maximum upload file size ( bytes ): Used to set upload_max_filesize. Specify in bytes.
• Different File Access Profile: *NONE or profile. If specified iView will adopt the authority of the profile before trying access the document store.
• Number Of Row Per Page: In search results the number of documents per page.
• Show Spool File Attributes In Searching: If *YES will allow you to search on the external spool file attributes of spool files archived through the engine. Otherwise specify *NO.
• Required For Search: Globally enables this feature, which is then configured in the Archive Configuration.
• Default Search Case Sensitivity: Case insensitive or not. This is the default - you can change it in the search dialog.

This is option 4 from the entrance page.

Select an archive to configure from the pull down list and let the definition load.

• Search Results Setup: Specify here if you wish the contents of this meta data field to be displayed in the search results summary page as a search context hint. You can specify it also for display as the file name. If you do use it as a file name, the point and click delete function will not work.

• Related Document Setup: Specify data fields that two archives have in common to setup Related documents. These fields are used to do a SQL join. You must specify the join in both directions - both to another archive and from it. So if there are two archives that have customer number in common, to setup related documents one would specify

table1:customerNbr corresponds to table2:customerNbr
table2:customerNbr corresponds to table1:customerNbr

This is option 6 from the entrance page.

You must configure access to an archive before anyone, including the administrator, can access it through the front end.

iView uses the browser, and thus the Apache webserver, to authenticate. This means that any mechanism for user authentication supported by Apache can be used to authenticate users.

Typically, we setup iView to authenticate against the IBM i user profile. This is accomplished by adding the following stanza to the Zend Server Apache configuration file: /www/zendsvr6/conf/httpd.conf:

 <LocationMatch "/iview*">
 	        PasswdFile %%SYSTEM%%
 	        AuthType Basic
 	        AuthName "i5 User Profile"
 	        Satisfy All
 	        Require valid-user
 </LocationMatch>
 

All this mechanism does is authenticate to the browser a particular user name.

Please remember that password authentication alone is not adequate protection for a web application accessible from the general internet.

The iView user manager matches the user name authenticated to the browser to a set of permissions. The user profile in iView is not per se connected to any profile object on any system. It is a user name that the browser authenticates.

In practice on an IBM i system, using the above Apache configuration with user names that exist on the IBM i allows web users to authenticate using their greenscreen user profile and password.

To create a profile, you may select a profile from the IBM i profile list (which may not be complete, depending on the access your current authenticated profile has to IBM i *USRPRF objects), or may type any name. You may optionally type a description, such as a full name, and press <update>.

The user will be added to the iView user table.

You may create a user group by typing the name and clicking the <update> button.

Once the group and a user exists, you may add the user to the group by selecting the user from the pull downlist for the group and clicking <update>.

A user can be removed from a group by mousing over the user name and clicking on the 'x'. The user name should strike through. At that point clicking <update> should remove the user from the group. You can strike through multiple users before clicking <update> to remove many users at once.

You can delete a group by mousing over the group name and clicking on the 'x'.

The access section allows you to control access by users and groups to an archive.

To add access, select the user or group from the pull down list and click <update>. To remove a user or group from access, mouse over the user/group name and click the 'x'. The name should strike through. You may then click <update> to remove the user/group from access to the archive. You may select multiple groups/users for removal at once.

Once a user/group has access to an archive, you may change the access to be read ® or read/write (rw). Read/write access allows the user/group to delete single documents from the archive from the search results screen.

Select an archive to perform archive maintenance. The specific maintenance to traverse the archive annotation file and purge records that have no existing associated archived document.

This feature provides configuration to iView that allows it to attempt to instruct the browser how to handle the archived document.

• File Extension: Specify the file type by extension.
• Content Type: Specify the internet media type. See Wikipedia for a list.
• Disposition: inline or attachment. By default, most browsers will prompt the user to download a file object that it does not know how to open. This is the “attachment” disposition. If the browser has the capability, either builtin or through add-ons, to open a file in its own window then specifying the file type with the disposition “inline” may persuade the browser to open the document in its window. This of course works well with PDF documents.

To search for an archived document, take:

Option 1: Search the Archives

Then select the archive from the list of archives to which you have read access.

At the search screen, specify search criteria for the define meta data fields and/or the external spool file attributes.

You may use a wildcard * (asterisk).

Whether or not the search is case sensitive by default depends on the global setting in iView setup. You may toggle that setting using the at the top left.

If you wish to see the results in a particular order then select a sort sequence. You can select multiple sort fields. If you do not select sort fields then the results will be presented in whatever order db2 returns them to the browser.

In the results listing, clicking on the file name should open the archived document in a separate browser tab. This behavior may vary per browser.

Use the related documents link to execute the search just performed across all the archives defined as related to the current archive in the archive setup. If this has not been setup then the related document search should be empty.

Use the email link to originate an email, with this document as an attachment, from the IBM i via iMail. The iMail library must be provided in iView Setup. iMail is a module of the iDocs Suite

To enable signatures in an archive:

• Change the storage format: from *PDF to *PDFSIG .
• Specify meta data field(s) used to search for documents to sign in the archive definition
• Setup printing. Specify one outqueue by entering it or use F18 to setup multiple printer queues conditionally.

The archive is now ready to accept documents for signature.

The document must be archived through an engine or through option 15 - manual import.

• Navigate to the document: Use the main page option 2, then search for the document. ( The search field(s) are the meta data fields with the SIGTAG switch set to Y ). The document should open in the signature capture app.
• Click on the 'sign' link.
• Click the sign button.
• Sign the document with your mouse, stylus or finger.
• Click save .
• Optionally print the signed document by clicking
• Optionally email by clicking the button. The iMail address book is used for addressing, or key the email addresses.
• Click

Documents in pending signature status can not be searched for in the regular archive, and vice versa. Clicking changes the document status to regular archived document.

[ Up To Index ]