pub:iviewqntc
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | pub:iviewqntc [2022/06/25 17:02] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ====== Using iView With the QNTC FileSystem ====== | ||
+ | |||
+ | Using IBM's SMB client functionality, | ||
+ | |||
+ | These instructions were prepared in September of 2007 on a V5R2 machine. | ||
+ | |||
+ | |||
+ | **Requirements**: | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Windows Server Setup ===== | ||
+ | |||
+ | 1. If using Windows Server 2003 with Active Directory, you must **disable SMB signing** on the Windows server before the QNTC SMB client will interface with it. | ||
+ | |||
+ | 2. Next, make certain that you **can see the Windows server from your pc**. From the Start button select Run, and then type the name of the server preceeded by two backslashes and press < | ||
+ | |||
+ | 3. **On the windows server create two user profiles**. The first will be user iview, and the second will be a working System i profile that is not QSECOFR (that must exist on the System i). This second profile will be used to test QNTC. Use exactly the same passwords on Windows Server as you do on the System i. Passwords are case sensitive. User profile iview probably does not have a password on the System i (for security reasons) and will later be given a password identical to what is specified to the Windows Server. | ||
+ | |||
+ | 4. Also **create a file share** to which to export the iView documents - in this example ivwshare. Make certain that user iview and the working System i profile have full access to this file share. **Create a subdirectory** in the file share with the name of the iView archive application in question, in this example ivwarchive. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== System i SMB Setup ===== | ||
+ | |||
+ | 1. Using **Operations Navigator**, | ||
+ | |||
+ | **Network -> Servers -> TCP/IP** | ||
+ | |||
+ | and right click on **iSeries NetServer**, | ||
+ | |||
+ | |||
+ | Under the **General Tab** | ||
+ | * **Server Name**: | ||
+ | * **Domain Name**: | ||
+ | |||
+ | |||
+ | Under the **WINS Configuration Tab** | ||
+ | * Primary and secondary **WINS servers**: leave blank if accessing Windows servers in the System i's subnet. | ||
+ | |||
+ | Then right click on the iSeries NetServer and select Start to start the server. | ||
+ | |||
+ | 2. On the System i, log in as the work profile. | ||
+ | |||
+ | **wrklnk '/ | ||
+ | |||
+ | There will be a delay while the System i server queries Windows machines for file shares. | ||
+ | One should then see a list of Windows servers. In this example we are using BATMAN as the name | ||
+ | of the Windows server, so in the directory list will be the directory BATMAN. | ||
+ | |||
+ | Using option 5, **drill down into the server**. One should see the file share ivwshare at the next level, and | ||
+ | below that the directory ivwarchive created to contain the iView files. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== iView Server Setup ===== | ||
+ | |||
+ | |||
+ | 1. If one is able to use wrklnk to view the iView data directory on the Windows server, one can now | ||
+ | **setup iView to use it**. Presuming that the iView archive application is already defined, a subdirectory | ||
+ | of /iview exists to contain the archived documents. In this example that subdirectory is ivwarchive. | ||
+ | |||
+ | Start QShell: | ||
+ | |||
+ | Change to the iView directory: | ||
+ | |||
+ | Remove the existing (empty) archive directory: | ||
+ | |||
+ | Create a link, named ivwarchive, to the networked Windows directory: **ln -s / | ||
+ | |||
+ | Now, change directory into ivwarchive: | ||
+ | |||
+ | and then print the current directory: | ||
+ | |||
+ | **OS/400 should echo back**: | ||
+ | |||
+ | 2. Next, **work with user profiles** and give user iView the same password as was specified on the Windows Server. Passwords are case sensitive. | ||
+ | |||
+ | 3. **Check iView release**. To archive and retrieve from the /qntc file system requires iView 3.02 with updated IVR8000, or a later release of iView. | ||
+ | |||
+ | |||
+ | At this point the iView server can be started and archiving can proceed into the archive. | ||
+ | |||
+ | **Caution** - if networked file systems operations fail and the document is not successfully copied to the remote folder, iView will put a message in the job log if logging is enabled but will otherwise continue processing. Additionally, | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Enabling Document Retrieval Over the Web Using Apache ===== | ||
+ | |||
+ | 1. Start the web configuration manager per the [[installiview# | ||
+ | Under **General Server Configuration**, | ||
+ | |||
+ | 2. From the OS/400 command line logged in as a user with high authority, execute this: | ||
+ | **CHGAUT OBJ('/ | ||
+ | |||
+ | 3. Start or restart the web server. | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ===== Cautions ===== | ||
+ | |||
+ | In the event of access problems to the /qntc file system, the iView server will issue error messages into its job log which will be visible if logging is specified, but otherwise will not behave differently. Thus, before clearing the archive outqueue IVWARCH the administrator is urged to do a **reasonability check** on the files on the remote server. Such a check could include using the web front end to access the first document processed, the last document processed, and a document archived in mid-processing. | ||
+ | |||
+ | |||
+ | |||
+ | ---- | ||
+ | < | ||
+ | |||
pub/iviewqntc.txt · Last modified: 2022/06/25 17:02 by 127.0.0.1