Configuring the NFS Client (Windows, Linux)Added by IBM on July 16, 2013 | Version 1 (Original)
|Usually, IBM® Docs, the Document Format Conversion server, and IBM File Viewer host the NFS client side, so you must configure these steps on the nodes that run the IBM Docs, Conversion and Files Viewer applications.
About this task
Configure the NFS client on each node that must access the shared folders that are hosted on the NFS server. The following variables show the example information for configuring the NFS client.
NFS (S)erver (H)ost:<SH>= 188.8.131.52
NFS (S)erver (M)ount (P)ath: <SMP>= /opt/data
NFS (C)lient (H)ost for (L)inux:<CH4L>= 184.108.40.206
NFS (C)lient (M)ount (P)ath for (L)inux: <CMP4L>= /opt/shared_data
NFS (C)lient (H)ost for (W)indows: <CH4W>= 220.127.116.11
NFS (C)lient (M)ount (P)ath for (W)indows: <CMP4W>= z:
The assumptions for this procedure are as follows:
- docs_nfs is the userid under which your WebSphere Application Server deployment on the IBM Docs server is running.
- 5050 is the UID for this user.
- On Linux™, this user must match the user and UID used on the WebSphere Application Server deployment on the IBM Docs server.
- On Windows™, the UID and group ID of this user must match when you set the Windows registry AnonymousUID and AnonymousGID values.
- For the File Viewer client, <SMP>, <CMP4L>, and <CMP4W> are different values than in the preceding examples, matching the values that are configured on the NFS server
NFS (S)erver (M)ount (P)ath:<SMP>= /opt/viewer_data
NFS (C)lient (M)ount (P)ath for (L)inux:<CMP4L>= /opt/viewer_shared_data
NFS (C)lient (M)ount (P)ath for (W)indows: <CMP4W>= v:
Parent topic: Configuring a shared data folder
- On Windows, complete the following steps:
- Start the command console as the administrator (Click Start -> All Programs -> Accessories. Right-click the Command Prompt, and select Run as administrator).
- Run the following command to install FS-NFS-Services: servermanagercmd.exe -install FS-NFS-Services.
- Run nfsadmin client stop.
- Run Add and Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousUID=5050, as DWord (32-bit) Decimal.
- Run Add and Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default\AnonymousGID=5050, as DWord (32-bit) Decimal.
- Run nfsadmin client start.
- Run nfsadmin client localhost config fileaccess=700 SecFlavors=+sys -krb5 -krb5i.
- On Linux, run the following commands:
- adduser -u 5050 docs_nfs
- mkdir -p <CMP4L>
- chown docs_nfs <CMP4L>
- chgrp docs_nfs <CMP4L>
- chmod 755 <CMP4L>
- service portmap start
- service nfslock start
- umount -f <CMP4L>
- mount -t nfs -o sec=sys,bg,soft,retry=1,timeo=60,actimeo=0,nfsvers=3 <SH>:<SMP> <CMP4L>
If the server is rebooted, the mount points for Linux
are not mounted automatically. The mount points must be added to your fstab or equivalent, or be remounted when the server is rebooted.
- Restart the NFS client service with as follows:
nfsadmin client stop
nfsadmin client start
- Mount the NFS server on Linux, as follows: mount -o mtype=soft retry=10 timeout=6 casesensitive=yes anon [nfs server hostname]:/local/home/nonroot/data/shared y:
- On Windows, the shared data path in cfg.properties must look like //18.104.22.168/opt/data, not z:/opt/data.
There are several ways to grant the non-root user read, write, and run permissions. One way is to change the group of the target directory to the non-root group and then grant the group the permissions for example:
chgrp -R <non-root_user_group><app_server_root>
chmod -R g+wrx <app_server_root>
Where <non-root_user_group> is a user group that contains the non-root user account and <app_server_root> is the target directory.