After you have configured the client, you must set up the NFS mounts to provide access to shared custom server information. You must also set up access to the voice server, if that is separate. To do this:
mknfsmnt -f /home/dirTalk/current_dir/ca.ssi -d /home/dirTalk/current_dir/ca.local -h server -m ssi -H -p 32 -A -w bg -o 10 -K 3 -k udp -R 2
On the -h flag, for server specify the host name of the database server.
Use the -H option above to hard mount the custom server directories. This is important because is allows Blueworx Voice Response to mount the file systems when required. If the /ca directory is inaccessible because it is set to soft, the AIX Virtual Memory Manager causes a bus error that causes the custom server to core dump. When the mount is set to hard, the custom server waits until the /ca directory becomes available.
For more information, see The mknfsmnt command.
mknfsmnt -f /home/dirTalk/current_dir/voice.ssi -d /home/dirTalk/current_dir/voice.local -h server -m ssi -S -p 32 -A -w bg -o 10 -K 3 -k udp -R 2
On the -h flag, for server specify the host name of the network interface that you want to use for NFS data on the voice server.
Use the -S option above to soft mount the voice files so that requests to play voice segments can time-out if the server is unavailable.
For more information, see The mknfsmnt command.
If you already use NFS on your installation, you might want to specify other flags on the mknfsmnt command so that you maintain the integrity of your system. In the commands shown above, the flags are used like this:
For more information on this NFS command, see the Commands Reference .