Directory for deployment manager
Profiles are a set of user files that represent a WAS configuration
It’s a home directory for Application Server
Profile and node are the same thing
Logical group of WAS instances or JVM’s
Logical group of physical servers having WAS installed
It’s a cell with servers
It’s a deployment manager with servers.
Whenever an application server is restarted.
When a new datasource is created or an exiting datasource is modified
Whenever a Web server is restarted.
When a new virtual host is created or an existing virtual host is modified.
Through bootstrap port number
Default host port on application server
Through 9060 port no.
Creating a virtual host on app server and accessing using the defined port
It’s a deployment manager node.
Node with Node Agent.
It’s an application server which manages configuration
A node that is part of a cell
Global security can be set up while installing the application server.
After installation by making changes in deployment manager.
Both the above
None of the above.
Enable java 2 security
Creating a security repository.
Both the above
None of the above
You did not restart the application server machine.
You did not generate plug-in.
You did not generate and propagate plug-in.
You did not restart Web Server after propagating new plug-in.
Using the add node command from dmgr machine
Using the federate node command from node machine
Using federate node command from dmgr machine
Using the add node command from node machine
StartServer.log, stopServer.log, serverstatus.log
Two application servers in a cluster can have different applications.
Two application servers in a cluster should necessarily be a part of one node group.
Two application servers in a cluster can be a part of multiple node groups.
A cluster can be created by using two or more existing servers in a cell.
It is the master server process which controls the configuration of all the nodes
These are the configuration files stored on Dmgr and synced to nodes on regular intervals
It’s a configuration file contained in a standalone application server
None of the above
Deployment manager profile
Application server profile
WebSphere V6 comes in three packages.
Only WebSphere ND package can be used for clustering.
Only WebSphere ND package comes with a WebServer and built in plug-in.
WebSphere Express v6 comes with a Rational Developer suite.
Write a script to monitor WebServer activities on remote system.
Create a WebServer Definition and add node as managed/unmanaged node
Deployment manager automatically manages WebServer
There is no feature like this available
D. none of the above.
A Web container, processes HTTP requests, servlets, and JSPs
A Web Container, processes HTTP, Servlet, JSPs and EJB beans
A web container can be used to serve standalone application clients
None of the above.
Delete a profile
Secure a profile
Federate a profile
Update profile templates
The Web server installed successfully
The WebSphere Application Server installed successfully
The InstallShield Wizard executed successfully to launch WebSphere Application Server installation.
The target operating system determined that it is compatible with WebSphere Application Server and had configured environment variables for it.
Use the Log Analyzer to view the servers activity.log file
View the servers startServer.log and native_stdout.log files.
Examine the SystemOut.log file for the current server process.
Log in to the administrative console and examine the runtime messages.
Create an XML file for each database configurations and ask developer use this XML to connect to DB.
This kind of configuration is not possible
Create two datasources and JNDI with same name but different scope one for each application
Create two datasources and JNDi names with different name and direct application code to use respective resource.
J2C authentication data
Key stores and certificates
Web security trust association.
JAAS login module in WebSphere.
Configure the LDAP directory servers as generic servers.
Configure a federated repository including all of the LDAP directory servers.
Configure WebSphere security to authenticate against all of the LDAP servers
Configure a standalone LDAP registry for each directory server and enable multiple realms.
Security is enabled on the administrative console.
An updated plugin-cfg.xml is generated and propagated to the Web server.
The Web server and the WebSphere Application Server must be installed on the same physical server.
The Web server plug-in and the WebSphere Application Server must be installed on the same physical server.
When a resource is defined at a more general scope, greater isolation is provided.
In the administrative console, All scopes can be selected to create a new resource.
Resources that are defined at more specific scopes override duplicate resources that are defined at more general scopes.
Resources such as Java Database Connectivity (JDBC) providers, namespace bindings, or shared libraries can only be defined at a single scope.
To enable encryption over the secure HTTP ports
To prevent other applications from using these ports
To avoid port conflicts with other servers on the same node
To ensure that cluster members on different hosts have unique ports
Session affinity in Web server plug-in
Memory--to-memory replication in Both Mode
Memory--to-memory replication in Server Mode
External HTTP Server, HTTP Server Plug-in and EJB Container
Load Balancer, Embedded HTTP Server, HTTP Server Plug-in and Web Container
Edge Component, HTTP Server Plug-in, external HTTP Server, and Web Container
External HTTP Server, HTTP Server Plug-in, embedded HTTP Server and Web container
There is no facility to view the plug-in configuration file in the administrative console.
From the web servers list, select a particular web server. In the properties view, click Plug-in properties and then click View next to the Plug-in configuration file name
On the left navigation bar, expand Servers, Server Types, and then Web Servers. Click on a particular web server. The path of the plug-in file is shown here. Use a text file reader to view the file.
On the left navigation bar, expand System Administration. Click on Server Management and go to Web Servers. Select Plug-in File Management. Clicking on the View link runs Notepad with the plug-in file open
Allows applications to obtain references to objects such as datasources.
Allows Java programs (clients and Java EE applications) to create, send, receive, and read asynchronous requests, as messages.
Provides a runtime environment for enterprise beans within the application server.
Provides a secure facility to support Customer's basic organizational entity management needs.
JCA resource adapter
High availability server
JMS activation specification
Specified in the installation.properties file
Specified as a parameter in the launchpad user interface
Included as a command-line option on the install command
Included as a command-line option on the launchpad application
Invokewsadmin and run the updateDMgrFileRepository command to update the password.
Manually edit the primary administrative users password in the fileRegistry.xml file.
Use the Manage Users page in the administrative console and change the primary administrative users password.
Configure the Federated repositories realm using the administrative console and change the primary administrative users password.
Segment multiple security domains within a WebSphere cell.
Define the logical grouping of application servers to scale horizontally or vertically.
Enable mixed nodes with different capabilities within the same cell for administration purposes.
Allow application servers having the same applications installed to be grouped logically for workload management.
Enable sewer affinity for each HTTP server in the cluster
Implement the Tivoli Access Manager as a load balancer
Implement the caching proxy server component of the Edge Components
Use the Load Balancer component of the Edge Components
Managed HTTP servers
Unmanaged HTTP servers
The node agent if its administrative security is enabled
The add Node command itself since it is password protected
The node to be federated if its administrative security is enabled
The deployment manager if its administrative security is enabled
The administrative console will not be able to generate a plug-in configuration file for this Web server.
Applications will not be able to use this Web sewer as a deployment target.
The plug-in configuration file must be manually propagated to the Web server host.
This Web server will not be able to perform workload management of requests to a cluster of application servers
Web server plug-in, Load balancer
Caching proxy, Deployment manager
Load balancer, Deployment manager
Federate nodes and create multiple clusters
Load balance multiple HTTP servers using Edge Components
Deploy multiple database servers using a high availability software product
Federate nodes and create cluster members across multiple machines.