IBM C9510-418 - Questions & Answers

Delete the plugin-cfg.xml file in the profile_root/config/cells directory before you use the GenPluginCfg command. Otherwise, configuration changes do not persist to the plugin-cfg.xml file. However, do not delete the plugin-cfg.xml file if you have custom properties that you previously set in it that you need to persist.

Note: You can update the global plugin-cfg.xml file using the administrative console or running the GenPluginCfg command for all of the clusters in a cell. However, you must delete the config/cells/plugin-cfg.xml file before you update the global plugin-cfg.xml file. If you do not delete the config/cells/plugin-cfg.xml file, only the new properties and their values are added to the global plugin-cfg.xml file. Any updates to existing plug-in property values are not added to the global plugin-cfg.xml file.

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

In the WebSphere Integrated Solutions Console, the web server is represented as a specific server type, and you can view or modify all of the configuration properties used in the plugin-cfg.xml file for the web server plug-in from the WebSphere Integrated Solutions Console.

References:
https://www.ibm.com/support/knowledgecenter/en/SSHRKX_8.0.0/plan/plan_ihs.html

You can install an enterprise application file on an application server or cluster by dragging or copying an enterprise archive (EAR), web application archive (WAR), Java archive (JAR), or Session Initiation Protocol (SIP) archive (SAR) to a monitored directory.

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

The thread pool WMQJCAResourceAdapter is referenced by the WebSphere MQ (WMQ) resource adapter inbound delivery to MDB's. When WebSphere MQ resource adapter is used in conjunction with the activation specs, the resource adapter's Work Manager uses the values defined for the WMQJCAResourceAdapter for utilizing the total number of threads defined.

Ideally the default values provides for the WMQJCAResourceAdapter will be sufficient for the resource adapter. But in case there is an heavy load on the system processing huge number of messages, you can increase the maximum number of threads the thread pool can hold.

References:
http://www-01.ibm.com/support/docview.wss?uid=swg21383363

If you want to monitor the activity of threads on which system alarms execute, add the following JVM generic arguments to the server settings.
-Dcom.ibm.websphere.alarmthreadmonitor.generate.javacore

Set to any value to cause a javacore dump to be created when an hung system alarm thread is detected.
The threads section of the javacore dump can be analyzed to determine what the reported thread and other related threads are doing.

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

Federated repositories enable you to use multiple repositories with WebSphere?Application Server. These repositories, which can be file-based repositories, LDAP repositories, or a sub-tree of an LDAP repository, are defined and theoretically combined under a single realm. All of the user repositories that are configured under the federated repository functionality are invisible to WebSphere Application Server.

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

The deployment manager is an administration application that runs in a special application server, which is created when you install the WebSphere Application Server Network Deployment product or when you create a management profile using the deployment manager profile template.

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

Depending on the operating system in use, the verboseGC output will be written to the following file by default: AIX, Linux, or Windows: native_stderr.log Solaris or HP-UX native_stdout.log

References:
http://www-01.ibm.com/support/docview.wss?uid=swg21114927

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

Provided that it uses the correct protocols (SOAP, HTTP, WSDL), any web service client can access a stateless session bean, whether or not the client is written in the Java programming language. The client doesn't even "know" what technology implements the service: stateless session bean, JAX-WS, or some other technology. In addition, enterprise beans and web components can be clients of web services. This flexibility enables you to integrate Java EE applications with web services.

References:
http://docs.oracle.com/javaee/6/tutorial/doc/gipjf.html