Frequently Asked WebSphere Interview Questions

31. What portal resources can’t be separated for the virtual portal?
Answer:

Themes and skins.
Vault segments and vault slots.
Supported clients and markups.
Composite applications and templates.
Policies.
32. How do you enable temporary and extended trace logging for WebSphere Portal?
Answer: Temporary traces can be set for a temporary period by using the administration portlet Enable Tracing or the IBM WebSphere Application Server administrative console and also using the Enable Tracing portlet in the portal administration page.
To enable extended trace settings for a longer period of time, that is, for more than one session, switch them on in the WebSphere Application Server configuration, save the updates and restart the portal server.

33. What are the different states of the syndication process?
Answer:
Idle: No syndication is occurring.
Pending: A request has been made to the syndicator, but it has yet to initiate a request to the syndication application.
Queued: The syndicator has sent a request to the syndication application, but syndication is not yet active.
Active: Syndication is occurring between the syndicator and subscriber.
Disabled: Syndication is currently disabled.

34. State some of the features present in the web sphere?
Answer:
Some of the features which are present in the web sphere are:

Order management
Web sphere commerce accelerator
Analytical and business intelligence
Open standards such as Java, EJB, etc
Web sphere commerce payments and customer care, etc
35. Explain the various Administrator benefits using Web sphere?
Answer: Web sphere almost reduces the work of the server administrator as he can manage the load on servers efficiently without any hassles. It also gives him the flexibility to divide the load and applications among different server farms. He can also predict the incoming load on servers. Email alerts, restart options, memory leak detection, etc.

36. Explain the attribute CHANNEL in web sphere MQ?
Answer: CHANNEL specifies the name of the server connection channel. Generally, this is the Web Sphere MQ network abstraction. The default standard used by CHANNEL is SVRCONN which is the server connection channel. This server is generally used to communicate to the queue manager by the client.

37. What is JDBC?
Answer: JDBC technology is an API (included in both J2SE and J2EE releases) that provides cross-DBMS connectivity to a wide range of SQL databases and access to other tabular data sources, such as spreadsheets or flat files. With a JDBC technology-enabled driver, you can connect all corporate data even in a heterogeneous environment.

38. What is the WebSphere Application Server Console and what is its role? What is the default URL and port for accessing it?
Answer: The administrative console is a browser-based interface that allows you to configure application server settings, deploy and manage applications, and perform additional tasks that are not included in the HTTP Server Administration interface. It used to be a Java application, however, to be firewall safe it was made into a web-based application.
It runs on the default install port 9060 e.g

39. What is the master repository?
Answer: deployment manager contains the MASTER configuration and application files. All updates to the configuration files should go through the deployment manager.

40. What are difference b/w dmgr and other profiles?
Answer:

dmgr app custom- it’s used for administration
the admin console is there plain node purpose of remaining profiles initially one app server there empty node it supports the distributed work independently environment. Put applications it is not included app server the admin console is there work independently do not put applications
41. Explain Portal architecture.
Answer: The core implementation of the portal is UI, hosted by a Portal server. The HTTP requests, HTML responses, and returning appropriate portal pages are handled by the Portal UI. Enterprise Web application also can be handled by the Portal Server.
The portal architecture has the following:
Automaton Server: This server performs the management of job scheduling and implementation of a portal. It accesses all remote crawlers and profile services retrieved and stored from a remote database.
Image Server: This server hosts images and other web page content used by web services and a portal. With this configuration, large static files are to be sent directly to the browser without portal server impacts.
Search Server: This server indexes and searches all the information, applications, communities, documents, web sites through the portal.
Collaboration Server: Web content publication and management for portals and web applications are supported by this server. Its functionality can be accessed by a remote web service through Enterprise Web Development kit.
Content Server: Publication and management of web content for portals and web applications along with form-based publishing, branding, templates, content expiration are allowed by this server.
Authentication Server: This server handles the portal authentication for users and remote services can be accessed through EDK.
Remote Servers: Web services written using the EDK are hosted by remote servers. The servers can be in different countries, on different platforms and domains.

42. List me the steps involved in building a release in WebSphere Portal?
Answer: If you have a completely new installation of the staging server and the production server:
Install the staging server, then install the production server.
Develop a release on the staging server.
Build the release on the staging server.
Empty portal contents on the production server by running the WPSconfig.sh|bat action-empty-portal task.
Import that releases onto the production server. Refer to Transferring a complete configuration for information.
If you already have a production server without a staging system:
Export the release of your production server.
Install an empty staging server using one of the following two methods:
Install the staging server with the flag -W empty Portal.active=True.
After installing and configuring the staging server, run the WPSconfig.sh|bat action-empty-portal task.
Import the production release onto the staging server. Refer to Transferring a complete configuration for information.
Develop and build a new release on the staging server.
Export that new release from the staging server.
Use ReleaseBuilder to generate the differential between the two releases.
Import the differential onto the production server.

43. What are the advantages of the MQ?
Answer:
1. Integration.
2. Asynchrony
3. Assured Delivery
4. Scalability.

44. what is a Message and what does it contain?
Answer: A message is a string of bytes that is meaningful to the applications that use it. Messages are used to transfer information from one application program to another (or between different parts of the same application). The applications can be running on the same platform, or on different platforms.
WebSphere MQ messages have two parts:
1. The application data. The content and structure of the application data are defined by the application programs that use it.
2. A message descriptor. The message descriptor identifies the message and contains additional control information, such as the type of message and the priority assigned to the message by the sending application. WebSphere MQ defines the format of the message descriptor.

45. Mention the Different Types of MQ Queues?
Answer:
There are four types of Queues Available in Web sphere MQ –
Local queue object: A local queue object identifies a local queue belonging to the queue manager to which the application is connected. All queues are local queues in the sense that each queue belongs to a queue manager and, for that queue manager; the queue is a local queue.
Remote queue object: A remote queue object identifies a queue belonging to another queue manager. This queue must be defined as a local queue to that queue manager. The information you specify when you define a remote queue object allows the local queue manager to find the remote queue manager so that any messages destined for the remote queue go to the correct queue manager.
Alias queue object An alias queue allows applications to access a queue by referring to it indirectly in MQI calls. When an alias queue name is used in an MQI call, the name is resolved to the name of either a local or a remote queue at run time. This allows you to change the queues that applications use without changing the application in any way; you merely change the alias queue definition to reflect the name of the new queue to which the alias resolves. An alias queue is not a queue, but an object that you can use to access another queue.
Model queue object A model queue defines a set of queue attributes that are used as a template for creating a dynamic queue.

46. What are the channel and mention different types of channels in MQ?
Answer: Channels are objects that provide a communication path from one queue manager to another. Channels are used in distributed queuing to move messages from one queue manager to another.

They shield applications from the underlying communications protocols.

The queue managers might exist on the same, or different, platforms.
Different types of Channels:

1. Sender-Receiver Channels
2. Requester-Server Channels
3. Client Connection channels
4. Server Connection Channels.
5. Cluster Sender.
6. Cluster Receiver Channels

47. How can we write the MQSC commands that have too many parameters?
Answer: For commands that have too many parameters to fit on one line, use continuation characters to indicate that a command is continued on the following line:
1. A minus sign ( ) indicates that the command is to be continued from the start of _ the following line.
2. A plus sign (+) indicates that the command is to be continued from the first nonblank character on the following line.

48. What is the Different Logging Methods available?
Answer: There are two different types available:
1. Circular: The circular logging is used for restart recovery. It is the default logging method. Circular is used in Development and Testing Queues. Circular logging keeps all restart Data in a ring of log files. Logging fills the first file in the ring, then moves on to the and so on, until all the files are full. It then goes back to the first file in the ring and starts This continues as long as the product is in use, and has the advantage that you never run out of log files.
2. Linear: Linear logging gives you both restart recovery and media recovery. It is used in Production. Linear logging keeps the log data in a continuous Sequence of files. Space is not reused, so you can always retrieve any record logged from the time that the queue manager was created. As disk space is finite, you might have to think about some form of archiving. It is an administrative task to manage your disk space for the log, reusing Or extending the existing space as necessary.

49. What is Channel initiators and Listeners?
Answer: A channel initiator acts as a trigger monitor for sender channels, because a transmission queue may be defined as a triggered queue. When a message arrives on a transmission queue that satisfies the triggering criteria for that queue, a message is sent to the initiation queue, triggering the channel initiator to start the
appropriate sender channel. You can also start-server channels in this way if you specified the connection name of the partner in the channel definition. This means that channels can be started automatically, based upon messages arriving on the appropriate transmission queue.
You need a channel listener program to start receiving (responder) MCAs. Responder MCAs are started in response to a startup request from the caller MCA; the channel listener detects incoming network requests and starts the associated channel.

50. How many no Full Repository Queue Managers are required for creating a cluster. What is the difference between full and partial repositories?
Answer: In each cluster, you must select at least one, preferably two, or possibly more of the queue managers to hold full repositories. A cluster can work quite adequately with only one full repository but using two improves availability. Every cluster has at least one (preferably two) queue managers holding full repositories of information about the queue managers, queues, and channels in a cluster. These repositories also contain requests from the other queue managers in the cluster for updates to the information. The other queue managers each hold a partial repository, containing information about the subset of queues and queue managers with which they need to communicate.