C9510-401 Sample Questions Answers

Performing an atomic rollout activates the new edition on half of the cluster first, and then activates the edition on the remaining half of the cluster. While the first half of the cluster is taken offline and updated, application requests are routed to the second half of the cluster. Verify that half the cluster can handle the entire load during the rollout period.

References: http://www.aiotestking.com/ibm/how-can-the-administrator-achieve-this-task-without-any-downtime-to-the-application/

Process embedded configuration

Specifies whether the embedded configuration should be processed. An embedded configuration consists of files such as resource.xml, variables.xml, and deployment.xml. You can collect WebSphere Application Server-specific deployment information and store it in the application EAR file. Such an EAR file can then be installed into a WebSphere Application Server configuration, using application management interfaces that are described in the topic, Installing an application through programming.

One such application EAR file is an enhanced EAR file, which is created when you export an already installed application. The embedded configuration check box identifies such an enhanced EAR file. By default, the check box for "process embedded configuration" is checked if the application is detected to be an enhanced EAR. The application install options are prepopulated with the information from the embedded configuration whether the check box for "process embedded configuration" is checked or not. Users can overwrite these values during the deployment process.

References: https://www.ibm.com/support/knowledgecenter/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/urun_rapp_installoptions.html

The admin_host virtual host is used for access to the WebSphere administrative console.

At installation time, the host is configured to match requests on the wc_adminhost and wc_adminhost_secure ports for the stand-alone server or deployment manager.

References: WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile (July 2013), page 303

A dynamic cluster is a server cluster that uses weights and workload management to balance the workloads of its cluster members dynamically, based on performance information that is collected from the cluster members. Dynamic clusters enable application server virtualization.

A dynamic cluster is an application deployment target that can expand and contract depending on the workload in your environment. Dynamic clusters work with autonomic managers, including the application placement controller and the dynamic workload manager to maximize the use of your computing resources. Dynamic clusters are required for many of the Intelligent Management autonomic functions, including high availability and service policies.

References: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/cwve_odrdynamiccluster.html

The IBM Monitoring and Diagnostic Tools for Java - Health Center is a lightweight tool that monitors active IBM Virtual Machines for Java with minimal performance overhead. The Health Center suggests live tuning recommendations for Garbage Collection, profiles methods including call stacks, and highlights contended locks. This information can help you optimize performance, improve stability and optimize system resource usage.

The tool is provided in two parts:

• An agent, which collects data from a running application. Java applications are monitored by the Health Center agent
• The Health Center client, an Eclipse-based GUI which connects to the agent. The client interprets the data that is obtained by the agent and provides recommendations to improve the performance of the monitored application. The client is available as an Eclipse plug-in and as part of IBM Support Assistant (ISA).

References: https://www.ibm.com/support/knowledgecenter/SS3KLZ/com.ibm.java.diagnostics.healthcenter.doc/homepage/plugin-homepage-hc.html

Problem(Abstract)

The SystemOut.log contains a WSVR0605W message, also called a hung thread message. A javacore, or thread dump on Solaris and HP-UX, is needed in order to determine how to resolve the potentially hung threads.

Cause

WebSphere Application Server attempts to report potentially hung threads using the hung thread detector. Depending on how the hung thread detector policy is configured, a thread running for a certain interval (default 10 minutes) might be reported as hung and a WSVR0605W message is printed in the SystemOut.log file:

WSVR0605W: Thread has been active for and may be hung. There are in total in the server that may be hung.

References: https://www-01.ibm.com/support/docview.wss?uid=swg21448581