A.Change the owner of the LOG directory /var/log to match that of the Cloud agent user.

B.Add read permissions for the agent user on /var/log/cron*.

C.Stop and start the agent.

D.Uninstall and reinstall the agent.

A.drill down to logs related to and in context to a specific application server

B.view AJAX performance in the log files

C.drill down to the JDBC connect string

D.receive alerts when an error is logged

A.Include the web proxy IP address, port, and username and password into the agent install command line.

B.Configure the agent.rsp file with values for OMC_PROXYHOST and OMC_PROXYPORT.

C.Connect to the Gateway via SSH and from the command line issue the command SET PROXY ON.

D.Include the path to the agent.rsp file in the agent install command line.

E.Enter the web proxy IP address, port, and username and password into the gateway.properties file.

F.Set the https_proxy environment variable.

A.Management Cloud Home > Application Navigator > Agents > Heartbeat

B.Management Cloud Home > Administration > Agents > Cloud Agents

C.Management Cloud Home > Data Explorer > Log > Entity

D.Management Cloud Home > Data Explorer > Log > Log Source

E.Management Cloud Home > Administration > Agents > Gateways

A.Run the AgentInstall.sh script with the -analyze parameter on your target.

B.Bulk upload the target data to the OMC data cube.

C.Manually enter your target data into the OMC console.

D.Define your target in the Configuration Management Database (CMDB)

E.Enable Enterprise Edition on the entity.