Applications Manager does not start when it is installed in a directory that contains non-english characters.
Reason: This is because the absolute path of the working directory will be updated in server.xml and tomcat server will not start if non-english charaters are present in server.xml.
Solution: As of now, Applications Manager should be installed in a directory that has english characters only.
New to ADSelfService Plus?
Related Articles
How to start Applications Manager when Linux Boots
You can start Applications Manager when Linux boots by making the following changes: 1. Add the following line as the first line in startApplicationsManager.sh file: cd <APPMANAGER-INSTALLEDDIRECTORY>/AppManager15/ Eg. cd ...Migrating the JRE bundled in Applications Manager
JRE Upgrade Document for Applications Manager This document helps the end-user in upgrading to the latest version of Java used in Applications Manager. The steps for Java upgrade in both Windows (Service and Non-Service mode) and Linux installations ...How do I migrate Applications Manager installed in one machine to a different machine?
Migrating Professional Edition of Applications Manager In order to migrate Applications Manager and its contents to a new machine, you need to ensure that the version of Applications Manager you install in the new machine matches that of the old ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...How to start/stop Applications Manager in Linux?
Starting Applications Manager From the command line, go to <Applications Manager Home> directory (by default it is /opt/ManageEngine/AppManager14) and execute the below command to start the product: nohup sh startApplicationsManager.sh & Execute the ...