500-430 Exam Dumps : Cisco AppDynamics Professional Implementer(CAPI)

To prepare a Linux environment for the installation of an AppDynamics Controller with a Large performance profile, which is suitable for monitoring up to 1000 agents, you need to perform the following steps:

• Install libaio on the host machine if it does not already have it installed. This library facilitates asynchronous I/O operations on the system, which are required by the Controller. You can use the package manager of your Linux distribution to install libaio, such as yum or apt-get. For example, on CentOS, you can run yum install libaio1.
• Verify the open file descriptor limit on the system. The file descriptor limit determines how many files a process can open at a time. The Controller requires a high file descriptor limit to handle the large number of connections and transactions. AppDynamics recommends setting the file descriptor limit to at least 65535 for the user account that runs the Controller. You can check the current file descriptor limit by running ulimit -n and modify it by editing the /etc/security/limits.conf file2.
• Verify the process limit on the system. The process limit determines how many processes a user can run at a time. The Controller requires a high process limit to handle the large number of threads and subprocesses. AppDynamics recommends setting the process limit to at least 65535 for the user account that runs the Controller. You can check the current process limit by running ulimit -u and modify it by editing the /etc/security/limits.conf file2.

Other steps that are not required but recommended for the Controller installation are verifying the user account permissions, configuring the virus scanners, installing the netstat network utility, and setting the NUMA configuration2. You do not need to install MySQL or Java separately, as they are included in the Controller installation package3. References: Prepare Linux for the Controller, Install the Controller on Linux, and Controller System Requirements in the AppDynamics documentation.

The AppDynamics Controller is a Java web application that runs on a GlassFish application server and uses a MySQL database. During the installation of the Controller, two user accounts are created by default:

• The GlassFish asadmin user is the administrative user for the GlassFish server. This user has the authority to start, stop, and configure the GlassFish server and its domains. The default username for this user is admin and the default password is appdynamics. You can change the password for this user after the installation by using the asadmin command-line tool1.
• The customer-specified Controller administrator account is the user account that you provide during the installation wizard. This is the account that you use to access the AppDynamics User Interface (UI) for the first time and perform various tasks such as creating applications, configuring agents, managing users and groups, and so on. You can choose any username and password for this account, but AppDynamics recommends using only ASCII characters. You can also create additional user accounts in the Controller UI after the installation2.

The other options are not user accounts that are created by the Controller installation. The Elastic search root user, the REST API user, and the MySQL appd admin user are user accounts that are used internally by the Controller components and are not exposed to the end user. The OS user that will run the controller is a user account that you need to create on the host machine before the installation, and it is not created by the Controller installation3. References: Controller Installation, Manage Users and Groups, and Update the Root User and Glassfish Admin Passwords in the AppDynamics documentation.

Custom correlation is needed when the default detection mechanisms of AppDynamics are not capable of auto-correlating transactions across tiers or across parent-child threads in complex multithreaded applications. Custom correlation enables the user to configure AppDynamics to propagate a unique correlation key by using the extension points of the distributed protocol or by decorating the payload. Among the four options, a custom TCP concurrent server is the most likely to require the implementation of custom correlation, as it is an unsupported framework and protocol that may not have easily-defined method calls or payload objects to configure as exit points or entry points. The other options, such as SOAP, JMS, and WCF, are supported by AppDynamics and can be automatically correlated by the agents without the need for custom configuration. References: Custom Correlation for Java Applications and Configure Custom Correlation for .NET Applications in the AppDynamics community.