A system administrator has deployed an application. The development team has updated a new version of this application. The administrator needs to immediately deploy this updated application and guarantee that only this new edition is used by clients and that any service requests for the application are queued during the deployment of the new application.
How can the administrator achieve this task without any downtime to the application?
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.
A WebSphere system administrator needs to install the Installation Manager (IM) on an unmanaged node on a host named
What step must the administrator take before submitting a job from the Integrated Solutions Console (ISC) to install the IM on
Submitting jobs to install Installation Manager on remote hosts
In a flexible management environment, you can submit the Install IBM Installation Manager job to install the Installation Manager on registered hosts of the job manager.
A system administrator needs to configure a JDBC provider and a data source for an application in a clustered environment. The administrator also needs to copy the JDBC drivers from the database server to the application server machines.
How can the administrator meet these requirements?
A web application has a configured session timeout of eight hours and a default LTPA token timeout of two hours. After every two hours, the users have to log in again from their HTTP browser. The system administrator is required to make configuration changed so users only have to log in once, while keeping the above mentioned timeouts the same. The authentication mechanism available is Kerberos.
How should the administrator do this?
In WebSphere Application Server Version 6.1, a trust association interceptor (TAI) that uses the Simple and Protected GSS-API Negotiation Mechanism (SPNEGO) to securely negotiate and authenticate HTTP requests for secured resources was introduced. This function was deprecated In WebSphere Application Server 7.0. SPNEGO web authentication has taken its place to provide dynamic reload of the SPNEGO filters and to enable fallback to the application login method.
A system administrator discovers an issue that requires a change to a federated server. In this cell, WebSphere administrative security is enabled, but application security is not enabled.
How should the administrator make this change?
The administrator should use:
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
Mari
1 months agoArletta
2 months agoNana
2 months agoGeorgiann
2 months agoLorrine
3 months agoLucy
3 months agoRasheeda
3 months agoOdelia
3 months agoZachary
3 months agoLoreen
4 months agoEdda
4 months agoKindra
4 months agoKimi
5 months agoMaile
5 months agoGeoffrey
5 months agoLavonda
5 months agoRoyce
6 months agoCatherin
6 months agoDana
6 months agoOna
6 months agoMarilynn
7 months agoNaomi
7 months agoColeen
7 months agoFloyd
7 months agoMattie
7 months agoBritt
8 months agoMelissa
8 months agoAsha
8 months agoDaryl
9 months agoLoise
10 months agoTiera
10 months ago