Docs 1.0.6 Conversion server changes

I finally came around to do my first Docs 1.0.6 installation these days and had to find out that there where some minor changes to the Conversion server which unfortunately can result in some major usage problems.
Let’s do a review:

IBM changed the way of mounting the NFS share under Windows from an automated process during WAS startup to a manual one which needs to be executed by the user or system. You can find the corresponding instructions in the IBM wiki:

18. In order to mount the share automatically with windows restart:

    Create a batch file, for example, c:IBMConversionNFSnfsmount.bat, and type:

    mount -o mtype=soft retry=10 timeout=6 casesensitive=yes anon W:
    mount -o mtype=soft retry=10 timeout=6 casesensitive=yes anon Y:

    Click Start > Administrative Tools > Task Scheduler.
    Click Create Task in Task Scheduler (Local).
    Click General, and type nfs_auto_mount for Name. In Security options, click Change User or Group > Advanced > Find Now, and select SYSTEM. Select Run with highest privileges, and click OK.
    Click Triggers > New, select At startup for Begin the task. Click OK.
    Click Actions > New > Browse, select c:IBMConversionNFSnfsmount.bat and click OK.
    Click OK.


“… and select SYSTEM.”

This is the really crucial part. Since you will probably configure the nodeagent and the application server to run as Windows service you will need to mount the NFS share as SYSTEM user, or else the java task will have no access to the share. Thanks to Martti Garden poiting this out in his blog post: .

After configuring the mount script for SYSTEM user the Conversion service worked and I could use the Docs and Viewer components successfully.
Unfortunately however not that long, because as soon as I logged out of the Windows server, the service was not available any longer. After dealing with the error above, the cause of the new problems yet was quickly found:
The two scheduled Conversion tasks “sym_monitor” and “kill_timeout” where the source of evil 😉

The IBM documentation left out the part where you would also have to configure these two tasks as SYSTEM user. After installing with the local administrative user they would run under this user account and therefor not be available after you log out of the system.

So I applied the changes and restarted the two scheduled tasks and voilà – it’s still working!

I will do another post in the next few days describing how to get Docs working with internal HTTPS communications (be warned – not supported from IBM).

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.