What is the supported runtime environment for a stand-alone thin client?
Answer : C
A stand-alone thin client is a Java program that uses the thin client runtime libraries of WebSphere Application Server to invoke enterprise beans or other remote services. It is called stand-alone because it does not run in an application client container; it is launched like any other Java application, with its own main method. The platform that supports it is therefore Java SE, the standard Java runtime, with the thin client classes on the class path, which is option C. The client carries out its own initialisation of JNDI, security, and the ORB, without the services that a container provides. The Java EE client container, option B, is the runtime for a different client type, the application client, which is packaged as a module and run by the product's application client launcher. Apache Geronimo and JBoss, options A and D, are other vendors' Java EE application servers, and they are not runtime environments for the product's thin client. When selecting the thin client, the developer should supply the thin client jar for the product and a JRE of a supported level, and should handle configuration, such as the provider URL and the security properties, in the code or in system properties. Where declarative resource references and container-managed security are wanted, the Java EE application client is the more suitable choice.
Which two functions does Transformation Advisor provide?
Choose two
Answer : B, E
Transformation Advisor is an IBM tool that analyses existing applications and the environments on which they run, in order to help plan a move to a modern platform such as containers or a cloud service. Its collector examines the application and server configuration and produces an assessment. Two functions from the list belong to it, options B and E. First, it determines the complexity of applications: the report assigns each application a rating, such as simple, moderate, or complex, together with an estimated development effort for migration. Second, it identifies the application changes that are required for modernisation, listing issues in the code or configuration, grouped by severity, that must be addressed for the target runtime. The other statements go beyond what the tool provides. Option A, a comparison of benefits for each supported provider, is not a report function, because the output evaluates applications and not the commercial features of providers. Option C, suggesting changes that would make applications faster in the cloud, confuses migration readiness with performance tuning, which the tool does not perform. Option D, partitioning an application and generating microservices, is refactoring work that the tool does not undertake; it can recommend a target but does not decompose code. The recommendations are typically used to prioritise which applications to move first and to estimate the effort involved.
An administrator receives the following error while upgrading WebSphere Application Server ND from 9.0.5.2 to 9.0.5.14:
CRIMA1020E ERROR: Error during ''install'' phase:
The administrator determines that the installation is corrupt. How can the corrupt installation be resolved with minimum effort?
Answer : C
The error CRIMA1020E during the install phase tells the administrator that Installation Manager could not complete the update, and in this case the installation files themselves are damaged. The aim is to return to a good installation, apply the fix pack, and keep the existing configuration, with as little work as possible. The most economical approach combines the product's backup and restore tools with a file-system restore. The administrator first runs backupConfig, which saves the configuration of the profile to an archive. The installation is then repaired by restoring the file system from the last working backup, which brings back a consistent set of product files. The upgrade to the target level is applied next, and finally restoreConfig reloads the saved configuration. Option C describes this sequence. Option A, uninstalling and re-installing the product, takes more effort because it needs a fresh installation, with the fixes reapplied to reach the required level, before the configuration can be restored. Option B restores the file system and then reconfigures the environment by hand, which is slow and error-prone, and the configuration in the file-system backup may be out of date. Option D, restoring a virtual machine snapshot and reconfiguring, has the same drawback, since the manual reconfiguration is the expensive part. Before any restore, the administrator should stop all the processes of the installation, and should verify the result with imcl listInstalledPackages and the versionInfo command.
An administrator wants to use the addNode command to federate an application server installation into a cell. They use the --includeapps option to bring over the applications from the node. One application on that node is the default application, which is already installed on another server in the cell.
What is the outcome?
Answer : A
The addNode command federates a stand-alone application server node into a cell, and its -includeapps option brings the node's installed applications into the cell's master repository. The default application, supplied with the product, is a sample application that is commonly present on every base server. When the cell already contains an application with the same name, installed through another node, the command does not install it again. The existing application is retained and the duplicate from the new node is skipped, with a message in the addNode log noting that it was not installed because an application of that name already exists. Option A is correct. Option B is wrong because two applications with the same name cannot coexist in a cell, since application names must be unique. Option C is wrong because the command does not ignore the product's shipped applications as a class of its own; the outcome results from the name conflict, and applications with unique names would be included. Option D is wrong because no merging of applications takes place, whatever the similarity of their binaries. An administrator who wants the applications of a node preserved should confirm names are unique before the federation. If the application that was skipped needs to run on the new node as well, it can be mapped to the node's server afterwards, through the console's module mapping, or by reinstalling it with that target added.
How can multiple base WebSphere Application Servers, running in different operating-system environments, be managed by a WebSphere ND cell?
Answer : A
A Network Deployment cell is built around a deployment manager, which holds the master configuration, and nodes that are federated into it. Each node runs a node agent that communicates with the deployment manager, and the operating system of each node is independent of the others. Because the communication between the cell's processes uses platform-neutral protocols, a cell may contain nodes running on different operating systems, which is called a heterogeneous cell. To bring base application servers on several platforms under central management, the administrator creates a deployment manager and then federates each application server profile into the cell with the addNode command. Option A states that procedure. Option B, creating new nodes for the applications, would discard the existing servers' configuration instead of bringing them under management. Option C misapplies the job manager. The job manager coordinates administrative jobs across multiple deployment managers and administrative agents, and it is a way of managing groups of separate environments, but it does not replace federation for placing nodes in a cell. Option D is incorrect because heterogeneous cells are supported, subject to the product's requirements for compatible versions. Before federating, the administrator should check that the node's product version is no higher than the deployment manager's, since a node at a later release cannot join. Time synchronisation and name resolution between hosts must also work reliably.
Which extra feature does the Intelligent Management Java ODR offering provide when compared with Intelligent Management ODRLib?
Answer : B
Intelligent Management offers the on demand router in two forms. The Java ODR is a full server process in the cell, running as an application server-based proxy that participates in the cell's management and uses the product's high availability and dynamic workload management infrastructure. ODRLib is a library variant that is embedded in IBM HTTP Server through its plug-in, allowing the web server to use the routing logic and the service policies without a separate Java process. It provides routing but has a narrower set of functions than the Java ODR. Among the features listed, support for the high availability deployment manager belongs to the Java ODR, which is option B. In a cell with a high availability deployment manager, the ODR nodes take part in the management structure, as the role-related question on the same topic suggests, whereas ODRLib has no such involvement. The other capabilities are not exclusive to the Java ODR. Automatic routing, option A, is the basic function that both forms perform. Dynamic cluster support, option C, concerns the dynamic clusters controlled by the application placement controller, which operate irrespective of the router type. Application edition rollout, option D, is a function of the edition management facilities of Intelligent Management, and is not attributed specifically to the choice of router. The administrator should pick ODRLib where a lightweight route is sufficient, and the Java ODR where the full set of autonomic features is required.
An administrator has set up a federated repository in the WebSphere Application Server ND administrative console. What must they do to configure multiple repositories beneath the federated repository realm?
Answer : B
A federated repository realm combines several user registries, such as LDAP directories and a file-based repository, into one virtual realm that WebSphere Application Server uses for authentication and authorisation. Each repository contributes a portion of the overall name space, and the realm must give every user and group a unique distinguished name. To avoid collisions and to make the combined tree coherent, each repository is mapped to a base entry within the realm, and the realm defines which entity types, such as PersonAccount and Group, are supported and where new entries of each type are created. In the console, this is done by configuring the supported entity types and specifying a base entry for the default parent. Option B is correct. The other items are part of repository setup but do not accomplish this particular requirement. Group attribute definitions, option A, tell the repository how group membership is read. The property-to-LDAP-attribute mapping, option C, translates logical property names to directory attributes for one repository. A baseDN, option D, is defined within each repository configuration to identify the subtree used, which is a precondition for the realm's base entries but is not what allows more than one repository below the realm. When adding repositories, administrators must also verify that the base entries are unique and do not overlap in the realm's name space, because overlapping entries cause ambiguous lookups.