Moving to Release 10.0 - running the migration tasks using NFS mounting

Although it is recommended that you run the migration tasks from the database server instead of the application server to avoid significant network overhead, you have the option of using NFS mounting. With NFS mounting, you can avoid installing Sterling Order Management System Software on the database server.

About this task

To use NFS mounting:

Procedure

  1. Create a user on the database server with the same UID and GID as the user you used to install Sterling Order Management System Software on your application server. This user should preferably have the same user name. For example, if the UNIX user used for installing and running Release 10.0 is Sterlite, with a UID of 5001 and GID of 101, the user that you create on the database server must have a UID of 5001 and GID of 101, and should preferably be named Sterlite.
  2. Share the <INSTALL_DIR> directory in the application server.
  3. Mount the <INSTALL_DIR> directory on the database server using the same path used in the application server. For example, if your <INSTALL_DIR> is /apps/ on the application server, mount it as /apps/ on the database server.
  4. Share the <JAVA_HOME> directory that you are using for Sterling Order Management System Software from the application server. You might have multiple Java™ versions installed on the application server for various reasons. Exercise and share the same <JAVA_HOME> directory that you are using for Sterling Order Management System Software.
  5. Mount the <JAVA_HOME> directory on the database server using the same path used in the application server. For example, if your <JAVA_HOME> was /apps/java on the application server, you should mount it as /apps/java on the database server.
  6. Log in as the Sterling Order Management System Software Administrator on the database server.