================================================================================
              W I N D O W S   I N S T A L L A T I O N   N O T E S
================================================================================

NOTE: THESE ARE MANUAL INSTALLATION NOTES for installing rollouts outside of the
      Bamboo deployment process. With Bamboo deployments, all these steps are done automatically.
      The instructions below assume that a REFS rollout was created with the
      Bamboo build task and now we want to manually install this. 
      Manual installation is not recommended, only in exception cases.

    1.  Log in as the Windows administrator to the portal instance where you
        want to install the rollout.

    2.  Open Administrative Tools > Services program.

    3.  On the Services window, scroll down to the application service where you
        want to install the rollout, and then stop it.

        Example: the service name is typically displayed as REFS (<InstanceName>)

    4.  In Windows File Explorer window, navigate to the "rollouts" folder for
        your instance.

        Example: <Drive>:\JDA\<Instance Name>\rollouts

    5.  If it doesn't already exist, create a "rollouts" directory at the same
        level as %REFSDIR%.

        Example: <Drive>:\JDA\<Instance Name>\rollouts

    6.  Download the rollout distribution directory into the environment's "rollouts"
        directory.

        Example: <Drive>:\JDA\<Instance Name>\rollouts\${rolloutName}

    9.  Open Command Prompt program.

   10.  On the Command Prompt window, change to the %REFSDIR% directory of your
        instance with the following command:

        > cd <Drive>:\JDA\<Instance Name>\rpweb

   11.  Type env.bat, and then press Enter to set the environment variables.

        > env.bat

   12.  Install the rollout.

        > cd %REFSDIR%\..\rollouts\${rolloutName}
        > deploy.cmd

        NOTE: -skipRefsDb argument can be passed to the deploy.cmd command to
              skip performing portal database steps. Typically, you want to
              change the database. However, if you are installing rollout in a
              clustered environment where several instances use the same
              database, then only the first instance's installation should run
              the database-related scripts. For the subsequent instances'
              installations, skip the change database step since the database
              was already changed with the first instance.

   13.  Switch back to the Services program and start the same portal service,
        which was stopped in the step #3 above.

================================================================================
              U N I X   I N S T A L L A T I O N   N O T E S
================================================================================

NOTE: THESE ARE MANUAL INSTALLATION NOTES for installing rollouts outside of the
      Bamboo deployment process. With Bamboo deployments, all these steps are done automatically.
      The instructions below assume that a REFS rollout was created with the
      Bamboo build task and now we want to manually install this.
      Manual installation is not recommended, only in exception cases.

    1.  Log in as the UNIX user to the portal instance where you want to install
        the rollout.

    2.  Shutdown the environment.

        $ cd $REFSDIR/bin
        $ refs-server stop

    3.  If it doesn't already exist, create a "rollouts" directory at the same
        level as $REFSDIR.

        $ cd $REFSDIR/..
        $ mkdir rollouts

    4.  Copy the rollout distribution file into the environment's "rollouts"
        directory and extract the compressed rollout file.

        $ cd $REFSDIR/../rollouts
        $ mkdir ${rolloutName}
        $ cd ${rolloutName}
        $ cp <SOURCE_DIR>/${rolloutName}.zip .
        $ unzip ${rolloutName}.zip

    5.  Install the rollout.

        $ cd $REFSDIR/../rollouts/${rolloutName}
        $ sh deploy

        NOTE: -skipRefsDb argument can be passed to the deploy command to
              skip performing portal database steps. Typically, you want to
              change the database. However, if you are installing rollout in a
              clustered environment where several instances use the same
              database, then only the first instance's installation should run
              the database-related scripts. For the subsequent instances'
              installations, skip the change database step since the database
              was already changed with the first instance.

    6.  Start up the environment.

        $ cd $REFSDIR/bin
        $ refs-server start
