Page tree
Skip to end of metadata
Go to start of metadata


Attivio 5.6 is more strict in its DNS requirements. Be sure to review the System Requirements’ DNS Settings section and that a reverse DNS lookup of the server name return the internal IP of the host.

Now that we've gone through the process of modifying both the XML configuration and Java code, we can attempt to deploy and start our project using the default, unclustered environment.

See Starting and Stopping Attivio for details on how to stop your 5.5.1 project and Agent and then start your project in 5.6.

Starting Up Procedure

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

  1. Stop the 5.5.1 processes
    If you have not stopped the 5.5.1 version of the project, do so now 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 hosts. You will not be able to start the 5.6 project in later steps if the 5.5.1 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:

    rm -rf <DATA-AGENT_DIR>/projects/<PROJECT_NAME>/<ENVIRONMENT_NAME>/data/data-<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 Attivio Platform Agent service using the executable from the 5.6 installation but point it at the same data-agent directory as before using the -d parameter.

  4. Open the 5.6 AIE-CLI
    Start the AIE-CLI using the executable from the 5.6 installation and pass it the location of the upgraded project using the -p parameter.

  5. Start the Store (unclustered projects only)
    If your project is unclustered, execute the start store command in the AIE-CLI and use the status command to monitor its progress.

  6. Start Attivio Hadoop cluster services (Attivio Hadoop clustered projects only)
    If your project uses an Attivio Hadoop cluster, execute the start hadoop command 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 to the Attivio Platform Agent.

    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 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 project's Attivio nodes and use the status command to monitor 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.

  • No labels