Page History

...

Execute the following steps in order to ensure you start your project up again with the upgraded configuration:

1. After stopping

   Stop the 5.5.1 processes
   If you have not stopped the 5.5.1 version of the project and its agent, do so now and close the CLI. Note: Be sure you open the CLI pointed at using the 5.5.1 AIE-CLI, then quit that AIE-CLI and stop the 5.5.1 Attivio Platform Agent service on all Attivio project to shut it down, not the upgraded project.
   

   Note

   hosts. You will not be able to start the 5.6 project in later steps if the 5.5.1

   project and Agent, in order for the Business Center, Dictionary Admin, API Security and other JSP-based UIs to function properly, you must remove old

   Agent services are still running on these hosts.

   
   

2. Clean old web-application files out of the data-agent directory
   Remove old web-application compiled class files from the existing data-agent directory by executing the following command, replacing the bracketed placeholder strings with your project, environment, and node names as appropriate:

   Code Block
   language text theme DJango
   rm -rf <data-agent location> <DATA-AGENT_DIR>/projects/ <project-name>/<environment-name> <PROJECT_NAME>/<ENVIRONMENT_NAME>/data/data- <node-name> <NODE_NAME>/admin.webappService/*

   This step is necessary to enable the 5.6 versions of the Business Center, Dictionary Admin, API Security and other JSP-based UIs to function properly.
   

   
   

3. Start the 5.6 Attivio Platform Agent . service
   Start the agent Attivio Platform Agent service using the executable from the 5.6 installation but point it at the same same data-agent directory  directory as before using the -d parameter.
   
   
4. Open the 5.6 AIE-CLI.
   Note: When starting the new 5.6 project, be sure you are running the 5.6 Agent, you use Start the AIE-CLI using the executable from the 5.6 CLI installation and pass it the location of the upgraded project using the -p parameter. 
   
   
5. Start the Store (unclustered projects only).
   Execute
   If your project is unclustered, execute the start store command if your project is unclustered in the AIE-CLI and use the status command to monitor its progress.
   
   
6. Start the Attivio Hadoop cluster services (Attivio Hadoop clustered projects only).
   Execute
   If your project uses an Attivio Hadoop cluster, execute the start hadoop command if your project is an Attivio Cluster and monitor and use the status command monitor its progress.
   
   

7. Deploy the updated project

   .

   
   Execute the deploy force command in the AIE-CLI to push the latest project changes

   and start the index processes for your Attivio Cluster.
    Be sure you execute deploy force not deploy so that the upgrade project files are pushed to the agent, replacing the older project files. Do not execute any update command

   to the Attivio Platform Agent.

   Note
   Be sure you execute deploy force (rather than just deploy without the force parameter) so that the upgraded project files overwrite the existing files for the 5.5.1 project in the Agent. Do not execute any update command if prompted.

   
   

8. Start the perfmon.Performance Monitor service
   Execute the start perfmon command if your project is unclustered and use the status command to monitor its progress.
   
   
9. Start the Attivio nodes.
   Execute the start all command to start the remaining processes project's Attivio nodes and use the status command to monitor its their progress.
   
   

It is possible there will be issues detected at runtime that will need to be addressed. This may take a few iterations. It is difficult to anticipate the specific issues which may be reported for your project. As always, if you are unable to resolve a specific error, contact us and we'll be glad to help.

...