See Update the Root User and Glassfish Admin Passwords. This is the administrator for the built-in account if single-tenant systems, or for the initial account for multi-tenant. The username of the administrator account in the Controller UI.
Iconsole application password#
This password is used for the admin user of the built-in Glassfish application server as well. The Glassfish admin user lets you access the Glassfish console and the asadmin utility. See Access the Administration Console.Īllowed characters in the password are: a-z, A-Z, 0-9. The root user is a Controller user account with privileges for accessing the system Administration Console. The password of the user account that the Controller uses to access its MySQL database.ĭo not use the single quotation mark ('), double quotation mark ("), or at sign characters in this password.
Password Requirementsĭue to browser incompatibilities, AppDynamics recommends using only ASCII characters for usernames, account names, and passwordsĬonfigure your installation using these password settings:
Iconsole application how to#
See Required Libraries for how to install libaio and other libraries on some common flavors of the Linux operating system. This library provides for asynchronous I/O operations on the system. Linux systems must also have the libaio library installed. On systems that run Linux, you must have cURL and netstat installed. See Enterprise Console Requirements and Prepare the Controller Host to make sure you meet the minimum space requirements. However, when the Enterprise Console host is not shared with the Controller host, then it requires additional disk and memory space. There is no need for additional memory for the Enterprise Console when it shares the same host as the Controller. The host must have enough disk space for the Enterprise Console and a platform, which includes a Controller. When installing the Enterprise Console on an AWS host, you must add the values for the following hostnames and IP addresses to the SAN: See HTTPS Support for the Enterprise Console.Ĭross-platform (OS) installation, e.g., installing the Enterprise Console on Linux and the Controller on Mac or Windows is not supported. You can enable HTTPS for the Enterprise Console during installation. To avoid such conflicts, the Enterprise Console should generally be used by a single user at a time. If a second user attempts to run a command while another command is in progress, the second command is not completed and an error message appears indicating that another command is in progress. The Enterprise Console prevents multiple users from running commands at the same time. The Enterprise Console installation path you choose must be writeable, i.e. the user who installed the Enterprise Console should have write permissions to that directory. You must also avoid port conflicts with the Controller database, which is 3388 by default, whereas the Enterprise Console database is 3377 by default. For instance, if the Controller is installed in /opt/appdynamics/controller, the Enterprise Console might be in /opt/appdynamics/enterpriseconsole. If you install the Enterprise Console on the Controller machine, it must be in a different directory in order to keep data separate.
0 kommentar(er)
