Let me know if this sounds familiar…
- You download the latest version of EngageOne Compose
- You update the deploy.properties and try to run the installation scripts on your development environment
- The configure step for one of the bundles fails
- You try to troubleshoot the issue only to make the problem worse
Did you have this experience? I sure did… then I discovered the five common installation mistakes that cause most install issues, and I want to share them with you.
Here’s the best part:
Once you know the 5 common mistakes, you will be able to prevent a lot of issues and complete the installation quickly.
Pre-requisites not met
A new release of EngageOne Compose may require some tweaks to your environment. A simple permission change or naming convention. If you don’t read the documentation, you may miss this new requirement and have a failed installation.
Corrupt install media
I had this issue twice. The anti-virus on your computer partially blocked the download, and the result was a corrupt media.
The solution… simple, download a new copy and install again
Miss the sequence
When you install EngageOne Designer and EngageOne Server, you need to follow a specific sequence to avoid install failures. You should complete EngageOne Designer setup before you start EngageOne Compose install.
Incorrect database configuration
In an enterprise, your database team may be responsible for the EngageOne Compose database setup. You have to make sure the database meets the recommended configuration.
Intermediate validation
EngageOne Compose installation script eos.groovy allows you to validate the installation. If your implementation plan has several EngageOne Compose environments (Development, Training, QA, Production, etc.) each with multiple nodes, then the groovy script is invaluable.
You will be able to validate your installation before you configure the bundles on each node and avoid significant rework.
The above five mistakes are generally the root cause for a majority of support issues for EngageOne Compose. Avoid these mistakes, and you will have a working installation in no time.
A quick question…
Did you try the new EngageOne Compose 4.4 SP8? If not, go ahead and give it a try. Don’t forget to read the release notes before you install.