Table of Contents

[ Up To Index ]

Configuring iView 6 Front End Options

Global Options

From the iView home page take the option: iView Setup.

to upload a front end license file. When licensed, the Server ID licensed displays in green.

contains the meta data and other tables needed by the web server.

This name is stored in data area DSIVIEWDIR.

THis is the location of the scripts and front end configuration.

any defined database in WRKRDBDIRE.

Normally this will be the IP of the IBM i server lpar and port 80. If using port 80 it can be omitted
since it is the default http port. Port 10088 is the default install port for the Zend Server.

as a user in the User Manager.

library name here.

It must be accessible to the Zend Server and Zend profiles. QGPL/QS36EVOKE, which is multi-threaded as shipped from IBM,
is probably a good setting.

Users and Groups

In iView 6 users, groups and access must be defined in the front end.
Prior implementations used a simpler access control mechanism defined in greenscreen.
Any existing security implementation is ignored by iView 6.

user must also exist in the IBM i user profiles. Most implementations use this authentication method.

Access now defaults to read access, “r”, by default for backward compatibility. Read/Write “rw” access
allows users to add to the archive by dragging and dropping to the browser, and to delete from the archive.

Content Types

iView 6 permits binary archiving, i.e. an authorized user may drag/drop any type of file
from their desktop into the archive. In order for the web server to properly serve the file
to the browser the content type must be configured.

Note that browsers are designed to work with certain types of documents and the prompting for download
is the default behaviour when the browser does not know how to handle the file type. Even correct
configuration of the content type may not prevent this.

A list of internet media types can be found here: http://en.wikipedia.org/wiki/Internet_media_type

iView will use this configuration in its instructions to the browser.

For content type, it will issue this instruction: Content-type: <content type>

For disposition:

if the disposition is attachment, it will issue this instruction: Content-Disposition: attachment; filename=<fileName>
Otherwise it will issue this instruction: Content-Disposition: <content disposition>

Important: Enter the file extensions in lower case, and enter the content type and disposition in mixed case as appropriate.


[ Up To Index ]