Upgrade the Deployment Agent included in the platform

The following steps enable you to upgrade the deployment agent included in the platform.

Upgrading the deployment agent will require downtime on each node you want to upgrade. Before upgrading please verify that an upgrade is needed. You can determine the current version of the deployment agent by using an internet browser and navigating to http://NODE:8177.

Prerequisites

Newest Version The newest version of the deployment agent intended for production use is available on the Fredhopper Extranet in the directory https://extranet.fredhopper.com/deployment/Deployment-agent/

The upgrade process will not change existing configuration or data.

The following instructions show command line snippets written for a bourne shell, and assume that they are executed from the Fredhopper installation directory (typically /home/fredhopper/fredhopper or c:\fredhopper)

You must execute the steps for each node.

Step-By-Step Instructions

Step 1: Shutdown all running processes

Before the deployment agent can be upgraded you need to shut down all running processes. You can use the bin/instance script for this, or do it manually by invoking the stop verb on each process, for example using the following script:

for i in `bin/deployment-agent-client list-instances`; do
  for p in `bin/deployment-agent-client list-processes $i`; do
    s=`bin/deployment-agent-client invoke $i $p status`
    if [ "RUNNING" = "$s" ]; then
      echo "Stopping $i:$t"
      bin/deployment-agent-client invoke $i $p stop
    fi
  done
done

Step 2: Shutdown the deployment agent itself

Execute: 

bin/deployment-agent-client stop-agent to stop the agent.

Step 3: Backup the old deployment agent directory

Execute

 mv deployment-agent deployment-agent.before-upgrade (unix)

or 

ren deployment-agent deployment-agent.before-upgrade (Windows).

Step 4: Unzip the new deployment agent distribution

The deployment agent distribution will create a new directory, for example deployment-agent-1.1.

If you're using Unix you also should make the extracted scripts executable:

$ chmod +x deployment-agent-1.1/bin/*
$ chmod -x deployment-agent-1.1/bin/*.bat

Step 5: Rename the directory

Execute: 

mv deployment-agent-1.1 deployment-agent (unix)

or 

ren deployment-agent-1.1 deployment-agent (Windows).

Step 6: Start the deployment agent

Start the deployment agent, in the same way you would usually start it (using a SysV init script, Windows service).

You can also start the deployment agent on the current console, by executing bin/deployment-agent.

Step 7: Verify the upgrade

Check that http://NODE:8177 reports the new version now.

Step 8: Start other processes

Start all processes that should be running on this node.

Troubleshooting

If something does not work you can always restore the previous version from the backup directory created in step 3.

1. Stop everything
2. Remove the deployment-agent directory
3. Move deployment-agent.before-upgrade back to deployment-agent
4. Start the agent and processes.