know your websphere application server(http://websphereknowledge.com)

Sunday, 1 December 2013

Websphere MQ Notes and interview questions

IBM Websphere MQ interview Questions Part 1 - Middleware News
===============================================================

What is MQ and what does it do?

Ans. MQ stands for MESSAGE QUEUEING. WebSphere MQ allows application programs to use message queuing to participate in message-driven processing. Application programs can communicate across different platforms by using the appropriate message queuing software products.

What is Message driven process?

Ans . When messages arrive on a queue, they can automatically start an application using triggering. If necessary, the applications can be stopped when the message (or messages) have been processed.

What are advantages of the MQ?

Ans. 1. Integration.

2. Asynchrony

3. Assured Delivery

4. Scalability.

How does it support the Integration?

Ans. Because the MQ is independent of the Operating System you use i.e. it may be Windows, Solaris,AIX.It is independent of the protocol (i.e. TCP/IP, LU6.2, SNA, NetBIOS, UDP).It is not required that both the sender and receiver should be running on the same platform

What is Asynchrony?

Ans. With message queuing, the exchange of messages between the sending and receiving programs is independent of time. This means that the sending and receiving application programs are decoupled; the sender can continue processing without having to wait for the receiver to acknowledge receipt of the message. The target application does not even have to be running when the message is sent. It can retrieve the message after it is has been started.

What are the hardware and Software requirements for MQ Installation in AIX?

Ans. WebSphere MQ for AIX, V5.3 runs on any machine that supports the AIX V4.3.3 PowerPC® 32.bit, or AIX® V5.1 Power 32 bit only operating system.

Disk Storage: Typical storage requirements are as follows:

1 Server installation: 50 MB

2. Client installation: 15 MB

3 Data storage (server): 50 MB

4. Data storage (client): 5 MB.

Software Requirements:

Operating system: The operating systems supported by WebSphere MQ for AIX, V5.3 are:

1. AIX V4.3.3, with PTF U472177, running in a 32 bit environment, on 32 or 64 bit hardware.

2. AIX V5.1, with PTFs U476879, U477366, U477367 and U477368, and APAR fix IY29345 running 32 bit kernel running on 32 or 64 bit hardware.

3. AIX V5.1, with PTF U476879, U477366, U477367 and U477368, and APAR fix IY29345 running 64 bit kernel running on 64 bit hardware.

Connectivity The network protocols supported by WebSphere MQ for AIX, V5.3 are:

1. TCP/IP

2. SNA LU 6.2.

Databases: DB2 7.1, 7.2

Oracle 8i and 9i

Sybase v12 or v 12.5

Java: If you want to use the Java Messaging Support, you need the Java Runtime Environment Version 1.3 or later

What are the software and hardware requirements for installing MQ on Windows?

Ans: MQ v 5.3 supports Windows 2000, Windows 2000XP,Windows 2000NT,

Windows 2003 SE, Windows 2003EE.

Disk Storage: Typical storage requirements are as follows:

1 Server installation: 50 MB

2. Client installation: 15 MB

3 Data storage (server): 50 MB

4. Data storage (client): 5 MB.

Connectivity The network protocols supported by WebSphere MQ for AIX, V5.3 are:

1. TCP/IP

2. SNA LU 6.2.

3. LU 6.2

4. NetBIOS

Databases: DB2 7.1, 7.2

Oracle 8i and 9i

Sybase v12 or v 12.5

Java: If you want to use the Java Messaging Support, you need the Java Runtime Environment Version 1.3 or later

what is a Message and what does it contain?

Ans: 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 is 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. For a complete description of the message descriptor,

What is the Max Length of the message does MQ support/

Ans: The default maximum message length is 4 MB, although you can increase this to a maximum length of 100 MB (where 1 MB equals 1 048 576 bytes).

What is the difference between Persistent and Non Persistent Messages?

Ans: In Web Sphere MQ, messages can be either persistent or non persistent. Persistent messages are logged and can be recovered in the event of a WebSphere MQ failure. Thus, persistent messages are guaranteed to be delivered once and only once. Nonpersistent messages are not logged. Web Sphere still guarantees to deliver them not more than once, but it does not promise to deliver them once.

What is the effect of using Persistant messages?

Ans: Persistent messages are usually logged. Logging messages reduces the performance of your application, so use persistent messages for essential data only. If the data in a message can be discarded if the queue manager stops or fails, use a nonpersistent message.

WebSphere MQ messages:

Messages are made up of Two parts: Message descriptor, Application data

Types of messages?

Datagram: A Message sent with no response expected.

Request: A Message sent for which a response is expected.

Reply: A Response Message for a requested message.

Report: A Message that describes the occurrence or event

Ex COA/COD
Sizes ?

Qmanagerà10000 Msgs Maxmsglengthà4 Mb

Queueà5000 Msgs Maxmsglengthà4 Mb

What is the attribute used to see the Message length?

Ans: MaxMsgLength

What is MQ Client?

Ans: A Web Sphere MQ client is a component that allows an application running on a system to issue MQI calls to a queue manager running on another system. The output from the call is sent back to the client, which passes it back to the application.

What is MQ Server?

Ans: A Web Sphere MQ server is a queue manager that provides queuing services to one or more clients. All the Web Sphere MQ objects, for example queues, exist only on the queue manager machine (the Web Sphere MQ server machine), and not on the client. A Web Sphere MQ server can also support local Web Sphere MQ

Applications

What are the Objects used in Web sphere MQ?

Ans: 1. Queue Manager 2. Queues

3. Channels 4. Processes 5. Name lists.

Mention the No of Characters required for creating names of the MQ objects?

Ans: For MQ Channels it is 20 Characters

For Remaining objects it is 48 characters.

What about is the Default port number for MQ Queue Manager?

Ans: 1414
Difference between MQSC commands and Control commands?

MQSC Commands – These commands are used to handle the admin related functions for the components that are present in the MQ Series. In general MQSC commands are used for creating and maintaining Message channels, Queue Managers, Clusters etc…

Control Commands – These commands are used to manage the processes and services that are helpful in the functioning of the MQ Series. In general these commands are used for Channel listener, Channel Initiator, Trigger monitor etc…

Is the MQSC attributes are Case sensitive?

Ans: MQSC commands, including their attributes, can be written in uppercase or lowercase. Object names in MQSC commands are folded to uppercase (that is, QUEUE and queue are not differentiated), unless the names are enclosed within single quotation marks. If quotation marks are not used, the object is processed with a name in uppercase.

SCRIPT COMMANDS:-

After entering in to queue manager we can find script commands.

Script commands are same for every queue manager.

(These Commands should be used in CAPITAL LETTERS)

· DEFINE :-To define/create MQ manager objects like queue,

Channels, process, and listener.

· ALTER :-to update or modify the existing objects

· DISPLAY :-to view all the properties of a particular object or to

Display all objects

· DELETE :-to delete created objects

· CLEAR :-to clear the message from the queue

· END :-to come out of the queue manager

· PING :-to check whether other side channel / queue manager is ready to accept our request.

· START :- to start the particular channel or listener

· STOP :-to stop particular channel or listener

· REFRESH :-used to refresh the security every time after giving or executing, set mgr or command for queue manager or object

· RESET :-used to reset channel,cluster,queue manager

· RESOLVE :-to resolve the channel which is in indoubt state

· SUSPEND :-to suspend a queue manager from a cluster environment

· RESUME :-to remove a queue manager from a cluster environment

How can we write the MQSC commands that have too many parameters/

Ans: 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.
What is programmable command format (PCF) commands?

These commands are issued from a programme for local or remote administration done by programmers.

What are commands used for creating the Queue manager from the Command prompt?

Ans: crtmqm -q -d MY.DEFAULT.XMIT.QUEUE -u DEAD.LETTER.QUEUE QM1

Here -q used to define the Queue manager QM1 as a Default Queue manager

-d is used to define the default transmission Queue -u is used to define the default dead letter queue.

How can U make the existing Queue Manager as an default Queue Manager?

Ans: On Windows systems, use the Web Sphere MQ Services snap-in to display the properties of the queue manager, and check the Make queue manager the default box. You need to stop and restart the queue manager for the change to take effect.

Where are the backup files are present after creating the Queue Manager?

Ans: Windows systems: If you use Web Sphere MQ for Windows NT and Windows 2000, configuration information is stored in the Windows Registry.

UNIX Systems: 1. When you install the product, the Web Sphere MQ configuration file (mqs.ini) is created. It contains a list of queue managers that is updated each time you create or delete a queue manager. There is one mqs.ini file per node.

2. When you create a new queue manager, a new queue manager configuration file (qm.ini) is automatically created. This contains configuration parameters for the queue manager.

What is the command used for starting the Queue Manager?

Ans: strmqm QMName

What is the command used for stopping the Queue manager?

Ans: endmqm -w QMName

The command waits until all applications have stopped and the queue manager has ended.

endmqm –i QMName

This type of shutdown does not wait for applications to disconnect from the queue manager.

What’s the message code for Stopping a Queue Manager?

AMQ4044 Queue manager stopping

What is the command used to delete the QueueManager?

Ans: dltmqm QMName

Display the attributes of the Queue Manager QM1?

Ans: runmqsc QM1 Display qmgr

IBM Websphere MQ interview Questions Part 2

What is Queue?

Ans: A queue is a data structure used to store messages. A queue manager owns each queue. The queue manager is responsible for maintaining the queues it owns, and for storing all the messages it receives onto the appropriate queues

What is the Default max Queue depth?

Ans 5000
Types of Queues?

Local Queue Remote Queues Alias Queues

Model Queue Dynamic Queues Cluster Queues.

Queue: A safe place to store messages for Prior-To-Delivery, it belongs to the Qmgr to which the application is connected.

Model Queue: Model queue is a template of a queue definition that uses when creating a dynamic queue.

Alias Queue: Queue definition, which is Alias to an actual Local or Remote Q. Used for security and easy maintenance.

Remote Queue: Object that defines a Queue belongs to another Q Manager (Logical Def).

Initiation Queue: An initiation queue is a local queue to which the queue manager writes a trigger message when certain conditions are met on another local queue

Dynamic Queue: Such a queue is defined “on the fly” when the application needs it. Dynamic queues may be retained by the queue manager or automatically deleted when the application program ends. Use- To store intermediate results.

Cluster Queue: Custer queue is a local queue that is known throughout a cluster of queue managers.

Reply-To-Queue: A request message must contain the name of the queue into which the responding program must put the Reply Message.

Queue Manager: Provides Messaging services and manages the Queues, Channels, and Processes that belongs to it.

Alias Q Manager: Queue-manager aliases, are created using a remote-queue definition with a blank RNAME.

What are the attributes required for the Remote Queue Definition?

Ans: 1.Name of the Queue 2. Transmission Queue Name.

3. Remote QueueManager name 4. Remote Local Queue Name

How can U define Queues in MQ?

Ans: Queues are defined to Web Sphere MQ using:

1. The MQSC command DEFINE

2. The PCF Create Queue command

What is Transmission Queue?

Ans: Transmission queues are queues that temporarily store messages that are destined for a remote queue manager. You must define at least one transmission queue for each remote queue manager to which the local queue manager is to send messages directly.

What is Initiation Queues?

Ans: Initiation queues are queues that are used in triggering. A queue manager puts a trigger message on an initiation queue when a trigger event occurs. A trigger event is a logical combination of conditions that is detected by a queue manager.

What is Dead Letter Queue?

Ans: A dead-letter (undelivered-message) queue is a queue that stores messages that cannot be routed to their correct destinations. This occurs when, for example, the destination queue is full. The supplied dead-letter queue is called SYSTEM.DEAD.LETTER.QUEUE. For distributed queuing, define a dead-letter queue on each queue manager involved.

What is the Max size that Queues support in MQ v5.3?

Ans.They support around 2GB of Size

How can u create a Transmission Queue from a local Queue?

Ans. Change the usage attribute from normal to Transmission

Define a Local Queue LQ using the MQSC Commands in the QM QM1

Ans: runmqsc QM1

Define qlocal (LQ)

What are the Difference B/W Predefined & Dynamic Queues?

Ans: Queues can be characterized by the way they are created:

1. Predefined queues are created by an administrator using the appropriate MQSC or PCF commands. Predefined queues are permanent; they exist independently of the applications that use them and survive Web Sphere MQ restarts.

2 Dynamic queues are created when an application issues an MQOPEN request specifying the name of a model queue. The queue created is based on a template queue definition, which is called a model queue.

What is the Algorithm followed in retrieving the Messages from the Queue?

Ans: 1.First-in-first-out (FIFO).

2.Message priority, as defined in the message descriptor. Messages that have the same priority are retrieved on a FIFO basis.

3. A program request for a specific message.

What is Process Definition and what are the attributes does it contain?

Ans: A process definition object defines an application that starts in response to a trigger event on a WebSphere MQ queue manager. The process definition attributes include the application ID, the application type, and data specific to the application.
What is intercommunication and its components to send message ?

What is Intercommunication?

Ans: In Web Sphere MQ, intercommunication means sending messages from one Queue manager to another. The receiving queue manager could be on the same machine or another; nearby or on the other side of the world. It could be running on the same platform as the local queue manager, or could be on any of the platforms supported by Web Sphere MQ. This is called a distributed environment.

Message channels Message channel agents

Transmission queues Channel initiators and listeners

Channel-exit programs

What is Distributed Queue Management (DQM).

Web Sphere MQ handles communication in a distributed environment such as this using DQM.The local queue manager is sometimes called the source queue manager and the remote queue manager is sometimes called the target queue manager or the partner queue manager.

What is the Objects required for the DQM?

Ans: On source QueueManager:

1. Transmission Queue 2. Remote queue definition.

3. Dead Letter Queue(recommended) 4. Sender Channel

On Target Queue Manager

1. Local Queue 2. Dead Letter Queue 3. Receiver Channel 4.Listenr

***.The sender and receiver channels names should be same.

What is channel and mention different types of channels in MQ?

Ans: 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
What are MQI channels and there types?

MQI channels are the channels that carry messages from MQ Client application to the MQ server and vice versa.They are Bi-directional Channels

1. Server-connection 2. Client-connection
How many Channel Combinations?

1.Sender-receiver Channel 4.Requester-server Channel

2.Requester-sender Channel 5. Server-receiver Channel

3.Cluster-Sender- Receiver Channel 6.Client-Server Channel

What are the attributes required for the Sender Channel?

Ans: 1. The Name of the Channel 4.Transport Type

2. The Connection name 5.Scyexit

What are different Channel status?

Ans: Channel Status:

1. Inactive 3.Retrying

2. Running 4.Stopped

What about Initializing & Binding states?

Ans: Before running state first the channel will initializes the listener & Binds with the Receiver Channel then it goes into running mode.

Tell me Some Channel Attributes?

Batch Heartbeat Interval (BATCHHB): This heartbeat interval allows a sending channel to verify that the receiving channel is still active just before committing a batch of messages. If the receiving channel is not active, the batch can be backed out rather than becoming in-doubt, Batch interval (BATCHINT), Batch size (BATCHSZ), Channel type (CHLTYPE), Cluster (CLUSTER), Cluster namelist (CLUSNL), Connection name (CONNAME), Convert message (CONVERT), Disconnect interval (DISCINT), Heartbeat interval (HBINT), KeepAlive Interval (KAINT), Long retry count (LONGRTY), Long retry interval (LONGTMR), Maximum message length (MAXMSGL)
Why is Channel RETRYINT attribute used?

If a message is places in DLQ because of put inhibited or queue full condition, the DLQ handler attempts to put the message back to the destination queue. This interval is called as RETRYINT by default the retry interval is 60 seconds.

Receiver Cluster Receiver Requester
What is channel disconnect interval?

This is a time-out attribute, specified in seconds, for the server, cluster-sender, and cluster-receiver channels. The interval is measured from the point at which a batch ends, that is when the batch size is reached or when the batch interval expires and the transmission queue becomes empty. If no messages arrive on the transmission queue during the specified time interval, the channel closes down
Explain the channel attribute BATCHSIZE?

BATCHSIZE denotes the maximum number of messages that can be sent through a channel before taking a checkpoint. This parameter is valid only for channels with a channel type (CHLTYPE) of SDR, SVR, RCVR, RQSTR, CLUSSDR, or CLUSRCVR. The value must be in the range 1 through 9999.

What is BATCH HEARTBEAT INTERVAL?

Ans: The batch heartbeat interval allows a sending channel to verify that the receiving channel is still active just before committing a batch of messages, so that if the receiving channel is not active, the batch can be backed out rather than becoming in-doubt, as would otherwise be the case. By backing out the batch, the

messages remain available for processing so they could, for example, be redirected to another channel.

What is Keep Alive Interval?

Ans: The Keep Alive Interval parameter is used to specify a time-out value for a channel. The Keep Alive Interval parameter is a value passed to the communications stack specifying the Keep Alive timing for the channel. It allows you to specify a different keep alive value for each channel. The value indicates a time, in seconds, and must be in the range 0 to 99999.

What is LONG Retry count?

Ans: Specify the maximum number of times that the channel is to try allocating a session to its partner. If the initial allocation attempt fails, the short retry count number is decremented and the channel retries the remaining number of times.
What are the ways to start a channel?

Use the MQSC command START CHANNEL

Use the control command runmqchl to start the channel as a process

Use the channel initiator to trigger the channel

Type of channel states:

Inactive and Current- Stopped, Starting, Retrying and Active
What are the three options for stopping channels?

QUIESCE FORCE TERMINATE
What are the components of message channel?

A queue manager to communicate with another queue manager uses message channel. The components of a message channel are

1. Sender Message channel agent: Sender MCA is a program that transfers messages from a transmission queue to a communication link

2. Receiver MCA: It transfers messages from the communication link into the target queue

3. Communication protocol: Responsible for transferring messages A message channel is unidirectional.

What is Message Channel agent (MCA)?

Ans: A message channel agent (MCA) is a program that controls the sending and receiving of messages. There is one message channel agent at each end of a channel. One MCA takes messages from the transmission queue and puts them on the communication link. The other MCA receives messages and delivers them onto a queue on the remote queue manager.

A message channel agent is called a caller MCA if it initiated the communication; otherwise it is called a responder MCA.

What is Channel initiator and Listeners?

Ans: 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 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.

Channel Errors?

Due to: 1. Xmitq is set to get disabled 2. Network Issues

3.QueueManager Stopped 4. Listener is not running 5.TriggerTurned Off
Explain Channel-Exit programs and what are the types?

Channel-exit programs are called at defined places in the processing carried out by MCA programs

Security Exit: You can use security exit programs to verify that the partner at the other end of a channel is genuine

Message Exit: Message Exit can be used for Encryption on the link, message data conversion, validation of user ID,

Message-retry Exit: Message-retry exit is called when an attempt to open the target queue is unsuccessful

Sender and receiver Exit: You can use the send and receive exits to perform tasks such as data compression and decompression

Channel auto-definition Exit Transport-retry Exit

What is the Different Logging Methods available?

Ans: 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.

What is the Default location where the logs are stored and mention the default sizes?

Ans: Default location:

Windows: C:\Program Files\IBM\WebSphere MQ\log\qmgr

UNIX: /var/mqm/log

What is the log file size?

Ans: In Web Sphere MQ for Windows NT and Win 2000, the minimum value is 32, and the maximum is 16 384. The default value is 256, giving a default log size of 1 MB.

In Web Sphere MQ for UNIX systems, the minimum value is 64, and the maximum is 16 384. The default value is 1024, giving a default log size of 4 MB.

How will you change the log file size?

Ans ; You cannot change the log file size. For this you need to drop and re-create the queue manager. The number of log files primary & secondary can be changed but you need to restart the Q manager for the changes to take effect.

what is the number for log primary and secondary file allocated?

Ans: Primary log files: The number of primary log files to be allocated is 3 by default the minimum is 2 and MAX in Win 253 / Unix 510

Secondary log files: The number of secondary log files to be allocated is 2 by default the minimum is 1 and MAX in Win 252 / Unix 509

What is the command used for creating the listener?

Ans: crtmqlsr -t tcp -m QMNAME -p portno

What is the commands used for running listener in 5.3 Version?

Ans: runmqlsr -t tcp -m QMNAME -p portno

What is command used to perform task on the MQ services?

Ans: amqmdain

What are commands used on the Command server?

Ans: 1.strmqcsv: to start the command server

2. dspmqcsv: to display the command server

3. endmqcsv: To end the command server.

Is there is any chance for the Message lost?

Ans: If the target queuemanager doesn.t contain the dead letter queue defined and if the messages are running on a fast channel and of non persistant,Then there is a chance of the message loss.

What is the command that is used to provide authorization for the clients?

Ans: setmqaut -m QMName -t queue -n Queuename -p GUEST +all

What are the common errors u get in DQM? Explain how to resolve ?

Ans: mqrc 2058: MQRC_Q_MGR_NAME_ERROR

Mqrc 2059: MQRC_Q_MGR_NOT_AVAILABLE.

Mqrc 2033: MQRC_NO_MSG_AVAILABLE.

Mqrc 2085: MQRC_UNKNOWN_OBJECT_NAME.

Mqrc 2009: MQRC_CONNECTION_BROKEN.

Mqrc 2043: MQRC_OBJECT_TYPE_ERROR.

Mqrc 2086: MQRC_UNKNOWN_OBJECT_Q_MGR.

Mqrc 2035: MQRC_NOT_AUTHORIZED.

INTERVIEW QUESTIONS

1. Tell me about self (or) take me through your resume?

2. What are the different types of Logs?

We have two types of logs.

1. Transactional logs:

2. Error logs.

3. Difference between Errors and Qmgr errors?

Errors: This will contain all S/W level errors and Information

QMGR:This will contains all the information of QMGR objects and errors

4. How you enable Trace?

* Or start a high detail trace for one queue manager:

strmqtrc -t all -t detail -m MY.QMGR

* Or start a high detail wrapping trace and limit the file size to 5MB :

strmqtrc -l 5 -t all -t detail -m MY.QMGR

# End all tracing:

endmqtrc -a

# Format the trace files:

dspmqtrc *.TRC

Or format wrapping trace files:

dspmqtrc *.TRC *.TRS

5. What does the FDC contain?

FDC File:Failure data capture,If any S/W related error occurs this file will be created,in FDC we have prob-Id based on that we will find the solution in IBM Tech notes.

probid

userid

application name

major error code

minor error code

problem civierty

probtype

process

6. Channel in doubt and in flight state?

The INDOUBT count specifies the number that were interrupted between phase-1 and phase-2 of the commit process. These must undergo forward recovery to ensure that resources modified by them are unavailable until their INDOUBT status is resolved.

The INFLIGHT count specifies the number that neither completed phase-1 of the commit process nor began the process of backing out. These must undergo backward recovery to restore resources modified by them to their previous consistent state

7. Sequence number wrap?

This is the highest number the message sequence number reaches before it restarts at 1.

The value of the number should be high enough to avoid a number being reissued while it is still being used by an earlier message. The two ends of a channel must have the same sequence number wrap value when a channel starts up; otherwise, an error occurs.

The value may be set from 100 through 999 999 999

8. Difference between Full & Partial Repository?

Full repository: This will contains all the information of Cluster QMgrs and other objects.

Partial repository: This will Contains the information of that particular Qmgr and Other instances for communication.

9. Where do we find the cluster information?

We have one Queue i.e SYSTEM.CLUSTER.REPOSITORY.QUEUE, in that all the cluster info will stored

10. What does contain in Auto define channel?

It contains channel name, port No. and Ip address That are mentioned in the Receiver channel

11. What is the backup Queue of the QMGR?

Dead letter queue

12. How you set Authentication?

Using SETMQAUT, this is used assign permissions to the user

SETMQAUT -M QMname -n objname -t objtype -p principle/-g group +all

dmpmqaut -m qmname -n objectname -t objecttype -p user to display set of all users given permission on the object

dspmqaut ------ to display set of all the permission for the user on the object

13. Will you give permission only for USER or GROUP, if GROUP why?

We can assign permissions to user and if you want assign permissions to group also.if asign permissions to group that are assign all the user who are under that group.

14. Difference between Receiver & Requester channel?

requester and reciver are same except that the reuqesters can starts the sender from requester side.

15. Why do we go clustering?

we have so many advantages using cluster

1.administration task will be redused

2.work load balancing

3.increase resource utilization

4.high availability

16. Components of the cluster?

Clussend and clusrcvr channels

SYSTEM.CLUSTER.REPOSITORY.QUEUE

SYSTEM.CLUSTER.COMMAND.QUEUE

SYSTEM.CLUSTER.TANSMISSION.QUEUE (Please do not disable the put or get attribute on cluster)

17. Which types of Logs are using in your Organization?

Depending upon client requirement we are using both linear and circular loggings

18. How you check the Status of the Queue?

dis qs(qname) type(handle)

19. Default path of the Error logs & Transaction Logs?

In windows:\Program files\IBM/Web spear MQ\Log\ Qmgrs\active

C:\Program file\IBM\Web spear MQ\Qmgrs\QMname\Errors

In Unix:/var/mqm/log/Qmgrs/active

/var/mqm/Qmgrs/Qmname/errors

20. What is the use of PROBID in Fdc?

Using ProbID: we can find the solution in IBM info center, If before anybody face that problem, otherwise we will rise PMR(problem management report) and it will contains Application name, major error, minor error and so on..

21. Difference stopping status of QMGRs?

End immediately, End abnormally, ended normally

22. How do you enable the Trigger?

we need to set some properties on queue’s

Trigger on

Trigtype (First/every/depth)

Trigdepth

Trigdata(chalname)

initq()

23. Which types of tickets do you mostly resolved?

instant tickets

24. How to Suspend a Qmgr from the cluster?

Suspend qmgr cluster (clusname)

25. How to add existing Qmgr into the cluster?

If you add it as full repository, you need to add repos keyword to Qm, and create one clussdr and clusrcvr channels, add cluster attributes to other objects

If you want to add it as partial repository, create clusrcvr channel to that QM and a clussdr to a queue manager in full repository and set cluster attribute to objects

26. What is the use of alias queue?

This queue is act as reference queue to local, remote and cluster queue’s.

the advantage of alias queue is

1. Hide the details of reference queue to clients.

2. used for follow the naming conventions,

3. Provide different levels of access.

Why do we give ‘Conname’ at Receiver Channel side in Cluster?

In cluster sdr channels are auto generated, based on the receiver channel attributes only the sdr channel will generated

27. How can you install all the Packages in Linux at a time?

rpm -ivh name of the packages with spaces

28. Tell me the process of installation on Windows and Linux?

on linux

df -k df -h to check the disk space

rpm (redhat package manager)

Create mqm userid and make mqm as its primary group.

the installation directory for mqm are opt/mqm

the working data is stored in var/mqm

./mqlicense.sh -accept --- to accept the license

then run the commands to install all the packages required. rpm -ivh packagename

rpm -ivh ( i- install v- verbose h- hash format)

to check the packages installed rpm -qa ! grep mq

ps -ef ! grep mq to end all the processes.

29. Difference between V5, V6 & V7?

30. Differences between persistent and non persistent messages?

1. Persistent msg’s are important, at any cost those must be deliver to destination QM,if any problem occur Those are placed in Xmitq or in DLQ.

2. Nonpersistent msg’s are not important; if any problem occurs those are discarded.

31. Types of tickets?

1. Instant tickets

2. Change order tickets

32. How many Qmgrs are in your current project?

Nearly 400.

33. How do you convert linear to circular?

we don’t have that type of operation if you want to change,

1. First stop the channels

2. Stop the Qmgr

3. Take the back up of qmanager using save queue manager

4. Delete the Qmgr

5. Recreate it with linear logging

6. Recreate all the queue definitions and give the permission to the queues

34. How many applications connect to your current project?

Display conn(*)

35. Reason codes for 2033, 2053, 2085, 2035, 2537…

2033: Msg not available

2053: Q full

2085: unknown obj name

2035: Not authorized

2537: channel not available

2016 (07E0) (RC2016): MQRC_GET_INHIBITED

2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q

2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR

2042 (07FA) (RC2042): MQRC_OBJECT_IN_USE

2051 (0803) (RC2051): MQRC_PUT_INHIBITED

2057 (0809) (RC2057): MQRC_Q_TYPE_ERROR

2058 (080A) (RC2058): MQRC_Q_MGR_NAME_ERROR

2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE

36. What are the errors we can get at the time of installation?

1. user is not a member of mqm group.

2. Some mq series processes are running while installing.

37. How do you connect MQ Client to MQ Server?

we have three types options for connecting client to server

1.MQCONNX

2.MQSERVER

3.Clientchannel tab

38. Qmgr attributes?

dEADQ,REPOS(),REPOSNL(),CLWLUSEQ(),MAXHANDS(),MAXPRTY()

39. What is listener and port?

Listener is a program running continuously listening for request msg from sdr

Port:unique entry point for a QManager

40. Where the configuration information stores on Linux and windows?

in windows it is stored at registry. in linux it is stored in mqs.ini file.

41. What is the difference between qm.ini and mqs.ini file?

A queue manager configuration file, qm.ini, contains information relevant to a specific queue manager. There is one queue manager configuration file for each queue manager. The qm.ini file is automatically created when the queue manager with which it is associated is created.

The WebSphere® MQ configuration file, mqs.ini, contains information relevant to all the queue managers on a WebSphere MQ installation. It is created automatically during installation. In particular, the mqs.ini file is used to locate the data associated with each queue manager

42. How do you configure the Qmgr before you install fix pack?

43. Difference between upgradation and migration?

---->An "upgrade" generally refers to an enhanced version of the software

---->if you migrate from a previous version of WebSphere MQ for Linux, you mustuninstall your current version before installing WebSphere MQ Version

44. Which tool you use to connect with Linux and mainframes?

putty to connect to linux.

telnet or ssh to connect to mainframes.

45. How many channels we can create in Distribution Queuing for a Qmgr?

One sender and receiver channel

46. If you create 100 channels for a Qmgr… How can you create 101 Channel?

Normal way like:Define chl(chlname) chltype(type) conname(Ip&port)

47. How many years of experience you have?

3.3 YEARS

48. Are you supporting for L2 or L3?

49. Who is your Vendor?

wipro

50. Who is your Client?

Carrefour

51. Project name?

Infrastructure engineering services.

52. Which ticketing tool you are using?

BMC REMEDY,RADIX, OPEN HP view

53. Which monitoring tool you are using?

OMEGAMON XE , Q pasa, BMC Main View

54. Your monitoring and ticketing tools belong to?

BMC

55. Your mail server and chat server?

lOTUSNODES, sametime

Microsoft outlook, office communicator

56. At which location your L3 team will be?

Client location

57. How can you recover the damaged object and its syntax?

using media recovery we can recreate damaged objects

rcrmqobj -m Qmname -t objtype -n objname

58. Channel attributes?

chltype(),discint(),batchhb(),trptype(),maxmsgl(),xmitq() conname() rqmname()

59. Different status of channel?

initializing,binding,retrying,running,inactive,stopped,paused

60. Are you supporting for 24*7 or on-call?

i have supported on-call .

61. Why do we go for MQ Client?

. No need for a full WebSphere MQ implementation on the client machine.

. Hardware requirements on the client system are reduced.

. System administration requirements are reduced.

. Application running on a client can connect to multiple queue managers on different systems.

. Alternative channels using different transmission protocols can be used

. Reduce the burden on other clients

62. In your company which Client-Server architecture is using?

63. Do you raise any PMR so far?

i have never raised PMR(problem management record)

64. Who send the tickets to you?

users, application team, all the members who are involved in the current project

65. How do you escalate the ticket to L3?

66. Have you ever raised any tickets so far?

yes.

67. Have you ever raised change order?

68. Which flavor you are using on Linux?

Red hat

69. Differences between MQI and MSG Channels?

MQI channels are used between MQ client and MQ sever, those are bi-directional

Types: server connection channel

Client connection channel

MSG channels are uni-directional, and used between QM

1. Sender

2. Receiver

3. Cluster sender

4.cluster rceiver

5.server

6. Client

7.requster

70. Default objects in Cluster?

SYSTEM.CLUSTER.REPOSITORY.QUEUE

SYSTEM.CLUSTER.COMMAND.QUEUE

SYSTEM.CLUSTER.TRANSMISSION.QUEUE

Queues and channels.

71. Difference between Dead-Letter Header and Handler?

if msg’a are come to DLQ, QM will add dead letter header to msg,it contains reason for failure, destination queue and QM details such type of info’n

using dead letter handler you pick the msg’s from DLQ placed it in destination queue

72. What is sync point?

This is nothing but unit of work in two phase commit

73. Tell me something about unit of work?

the period of updates between two sync points is called unit of work.

74. Can you change the log file size?

No.

75. Where the latest information stores in error logs and why?

In the first file.

76. Can you increase the no. of error logs?

77. What is the command to check the disk space on Linux?

df -k df -h

78. Which command we use to check the installed packages on Linux?

rpm -qa | grep mq

79. Command to kill the process on Linux?

$ ps ux ----------to list all the processes.

$ kill -9 Pid -------------to kill particular process...

80. Do you run the runmqdlq program every time?

Depending upon the messages those are coming to the DLQ.

81. How can you check the listener port is running from your desktop?

NETSTAT -a

82. What is the use of telnet, ping and tracert?

ping is used to check the status of remote channel.

telnet is used for remote access of another system.

it shows path taken to reach a particular destination over a network.

83. How can you connect to remote server from your desktop?

Using MSTSC

84. How many primary and secondary logs we can create on windows & Linux (Max)?

windows:primary file:254 ,secondary:253

linux:primary files:510,secondary:509

85. Explain the concept of cluster workload balance?

86. What are the attributes of workload balance?

Defbind(notfixed)

put()

clwluseq(local/any/QMGR)

clwlrank(0-9)

clwlprty(0-9)

clwlwght()

clwlmruse()

87. Explain client-server architecture?

88. What are the pre-requisites for MQ before install?

1. Hardware requirements----disk space

2. Software requirements----o/s specifications

89. Explain the process migration?

90. Have you ever done migration and how?

91. How can we take the Qmgr backup?

- create the backup queue manager

- copy the data and log files from your primary queue manager over the backup queue manager's data and logs

- flag backup qmgr as a backup and replay log extents (strmqm -r)

- periodically copy over the log files prior to the CURRLOG value from the queue manager

saveqmgr -m MQ_BACKUP -r MQ_C1_01 -f MQ_C1_01.txt

92. Error log file name?

error log file name is:AMQERR01,AMQERR02,AMQERR03

93. What is the use of client channel tables?

Using client channel table we can connect with different QM’s and different clients will connect to single QM

94. How many max channels can connect to a Qmgr?

The default for maximum channels is 100 for qmgr. it can be set to higher in the qm.ini.

95. How can you find the max channels are connected to a Qmgr?

dis qmstatus conns

96. Channel components?

chltype() conname() trptype() xmitq() batchsz() hbint()

97. What is the use of trig data in channel?

which chnnel you want to up at trigger event fired.provide channel name

98. What does initiation queue contain?

This will contains trigger massage generated by QM

99. How can we check whether the Qmgr contain Dead-latter queue or not?

DIS QMGR DEADQ(*)

100. How many servers, Qmgrs in your environment?

100 servers. 400 qmgrs.

101. Which programs you use for running the trigger monitor when you use your own initiation queue?(in application and channel triggering)

In application triggering we are using RUNMQTRM

in channel RUNMQCHI INITQ()

102. What is the default size of /var /mqm and /opt /mqm?

Allow 130 MB as a minimum for a WebSphere MQ server and 15 MB as a minimum for a WebSphere MQ client.

x-86 201 mb iseries -183

103. What is the difference between Control & Runmqsc Commands?

RUNMQSC commands are used with in Qm for creating Qm objects and altering QMGR.

CONTROL commands are used for creating starting and running QM, and for set authentication ...

104. In Cluster for Round-Robin process defbind (open) what is happen?

if you set defbind open, all msg’s are placed where the first msg is place

105. Explain the distributed queuing setup?

106. What is meant by distribution queuing?

107. What is difference between distribution and clustering?

in distributions queing we have to create more no of objects like remoteqs. transmission ques and sender, reciever channels for every remote queue manager.

in clustering we can logically connect queue managers with the creation of less no.of qmgr objects .

108. Why we go for clustering?

1.simplifying system administration

2.work load management

3.less no of qm objects like rqd, channels.

4.high availability

109. In cluster we have 4 Qmgrs and having same instance in all Qmgrs I have to send messages to a particular Qmgr then how u configure?

assign clwlrank and clwlprty for particular queue.

110. Tel me prerequisites for MQ admin?

111. R u configured SSL setup?

yes.

ssl address following important security considerations.

1.authantication

2.confidentiality

3.integrity

to install and configure ssl we need

1. a server certificate key store.

2. an https connector

112. Which key u r using in SSL?

symmetric key--- secret keys

Asymmetric key----------public private key pairs

113. What is the command to see the authentications?

DSPMQAUT: It will display the authenticated users

114. What may be reasons for getting channel is in retrying state?

1. if other side receiver channel is not defined

2. may channel was not started

115. What are the reasons for getting messages in dead letter queue?

1.if queue is full

2. Queue put inhibited.

3.Mag’s length is exceeded

116. What happen to messages (persistence& non persistence) if destination queue is full if there is no dead letter queue?

PERSISTENT: if queue is full, msg are coming back to xmitq and channel will be going to retrying state.

NON-PERSISTENT: That type of msg’s are discarded.

117. What is channel state in above case?

retrying

118. Tel me some system default queues?

1.SYSTEM.DEFAULT.ALIAS.QUEUE

2.SYSTEM.DEFAULT.INITIATIONS.QUEUE

3.SYSTEM.DEFAULT.LOCAL.QUEUE

4.SYSTEM.DEFAULT.MODELS.QUEUE

5.SYSTEM.DEFAULT.REMOTE..QUEUE

121.

IBM Websphere MQ interview Questions Part 2

INTERVIEW QUESTIONS

1. Tell me about self (or) take me through your resume?

2. What are the different types of Logs?

We have two types of logs.

1. Transactional logs:

2. Error logs.

3. Difference between Errors and Qmgr errors?

Errors: This will contain all S/W level errors and Information

QMGR:This will contains all the information of QMGR objects and errors

4. How you enable Trace?

* Or start a high detail trace for one queue manager:

strmqtrc -t all -t detail -m MY.QMGR

* Or start a high detail wrapping trace and limit the file size to 5MB :

strmqtrc -l 5 -t all -t detail -m MY.QMGR

# End all tracing:

endmqtrc -a

# Format the trace files:

dspmqtrc *.TRC

Or format wrapping trace files:

dspmqtrc *.TRC *.TRS

5. What does the FDC contain?

FDC File:Failure data capture,If any S/W related error occurs this file will be created,in FDC we have prob-Id based on that we will find the solution in IBM Tech notes.

probid

userid

application name

major error code

minor error code

problem civierty

probtype

process

6. Channel in doubt and in flight state?

7. Sequence number wrap?

This is the highest number the message sequence number reaches before it restarts at 1.

The value may be set from 100 through 999 999 999

8. Difference between Full & Partial Repository?

Full repository: This will contains all the information of Cluster QMgrs and other objects.

Partial repository: This will Contains the information of that particular Qmgr and Other instances for communication.

9. Where do we find the cluster information?

We have one Queue i.e SYSTEM.CLUSTER.REPOSITORY.QUEUE, in that all the cluster info will stored

10. What does contain in Auto define channel?

It contains channel name, port No. and Ip address That are mentioned in the Receiver channel

11. What is the backup Queue of the QMGR?

Dead letter queue

12. How you set Authentication?

Using SETMQAUT, this is used assign permissions to the user

SETMQAUT -M QMname -n objname -t objtype -p principle/-g group +all

dmpmqaut -m qmname -n objectname -t objecttype -p user to display set of all users given permission on the object

dspmqaut ------ to display set of all the permission for the user on the object

13. Will you give permission only for USER or GROUP, if GROUP why?

We can assign permissions to user and if you want assign permissions to group also.if asign permissions to group that are assign all the user who are under that group.

14. Difference between Receiver & Requester channel?

requester and reciver are same except that the reuqesters can starts the sender from requester side.

15. Why do we go clustering?

we have so many advantages using cluster

1.administration task will be redused

2.work load balancing

3.increase resource utilization

4.high availability

16. Components of the cluster?

Clussend and clusrcvr channels

SYSTEM.CLUSTER.REPOSITORY.QUEUE

SYSTEM.CLUSTER.COMMAND.QUEUE

SYSTEM.CLUSTER.TANSMISSION.QUEUE (Please do not disable the put or get attribute on cluster)

17. Which types of Logs are using in your Organization?

Depending upon client requirement we are using both linear and circular loggings

18. How you check the Status of the Queue?

dis qs(qname) type(handle)

19. Default path of the Error logs & Transaction Logs?

In windows:\Program files\IBM/Web spear MQ\Log\ Qmgrs\active

C:\Program file\IBM\Web spear MQ\Qmgrs\QMname\Errors

In Unix:/var/mqm/log/Qmgrs/active

/var/mqm/Qmgrs/Qmname/errors

20. What is the use of PROBID in Fdc?

21. Difference stopping status of QMGRs?

End immediately, End abnormally, ended normally

22. How do you enable the Trigger?

we need to set some properties on queue’s

Trigger on

Trigtype (First/every/depth)

Trigdepth

Trigdata(chalname)

initq()

23. Which types of tickets do you mostly resolved?

instant tickets

24. How to Suspend a Qmgr from the cluster?

Suspend qmgr cluster (clusname)

25. How to add existing Qmgr into the cluster?

If you add it as full repository, you need to add repos keyword to Qm, and create one clussdr and clusrcvr channels, add cluster attributes to other objects

If you want to add it as partial repository, create clusrcvr channel to that QM and a clussdr to a queue manager in full repository and set cluster attribute to objects

26. What is the use of alias queue?

This queue is act as reference queue to local, remote and cluster queue’s.

the advantage of alias queue is

1. Hide the details of reference queue to clients.

2. used for follow the naming conventions,

3. Provide different levels of access.

Why do we give ‘Conname’ at Receiver Channel side in Cluster?

In cluster sdr channels are auto generated, based on the receiver channel attributes only the sdr channel will generated

27. How can you install all the Packages in Linux at a time?

rpm -ivh name of the packages with spaces

28. Tell me the process of installation on Windows and Linux?

on linux

df -k df -h to check the disk space

rpm (redhat package manager)

Create mqm userid and make mqm as its primary group.

the installation directory for mqm are opt/mqm

the working data is stored in var/mqm

./mqlicense.sh -accept --- to accept the license

then run the commands to install all the packages required. rpm -ivh packagename

rpm -ivh ( i- install v- verbose h- hash format)

to check the packages installed rpm -qa ! grep mq

ps -ef ! grep mq to end all the processes.

29. Difference between V5, V6 & V7?

30. Differences between persistent and non persistent messages?

1. Persistent msg’s are important, at any cost those must be deliver to destination QM,if any problem occur Those are placed in Xmitq or in DLQ.

2. Nonpersistent msg’s are not important; if any problem occurs those are discarded.

31. Types of tickets?

1. Instant tickets

2. Change order tickets

32. How many Qmgrs are in your current project?

Nearly 400.

33. How do you convert linear to circular?

we don’t have that type of operation if you want to change,

1. First stop the channels

2. Stop the Qmgr

3. Take the back up of qmanager using save queue manager

4. Delete the Qmgr

5. Recreate it with linear logging

6. Recreate all the queue definitions and give the permission to the queues

34. How many applications connect to your current project?

Display conn(*)

35. Reason codes for 2033, 2053, 2085, 2035, 2537…

2033: Msg not available

2053: Q full

2085: unknown obj name

2035: Not authorized

2537: channel not available

2016 (07E0) (RC2016): MQRC_GET_INHIBITED

2030 (07EE) (RC2030): MQRC_MSG_TOO_BIG_FOR_Q

2031 (07EF) (RC2031): MQRC_MSG_TOO_BIG_FOR_Q_MGR

2042 (07FA) (RC2042): MQRC_OBJECT_IN_USE

2051 (0803) (RC2051): MQRC_PUT_INHIBITED

2057 (0809) (RC2057): MQRC_Q_TYPE_ERROR

2058 (080A) (RC2058): MQRC_Q_MGR_NAME_ERROR

2059 (080B) (RC2059): MQRC_Q_MGR_NOT_AVAILABLE

36. What are the errors we can get at the time of installation?

1. user is not a member of mqm group.

2. Some mq series processes are running while installing.

37. How do you connect MQ Client to MQ Server?

we have three types options for connecting client to server

1.MQCONNX

2.MQSERVER

3.Clientchannel tab

38. Qmgr attributes?

dEADQ,REPOS(),REPOSNL(),CLWLUSEQ(),MAXHANDS(),MAXPRTY()

39. What is listener and port?

Listener is a program running continuously listening for request msg from sdr

Port:unique entry point for a QManager

40. Where the configuration information stores on Linux and windows?

in windows it is stored at registry. in linux it is stored in mqs.ini file.

41. What is the difference between qm.ini and mqs.ini file?

42. How do you configure the Qmgr before you install fix pack?

43. Difference between upgradation and migration?

---->An "upgrade" generally refers to an enhanced version of the software

---->if you migrate from a previous version of WebSphere MQ for Linux, you mustuninstall your current version before installing WebSphere MQ Version

44. Which tool you use to connect with Linux and mainframes?

putty to connect to linux.

telnet or ssh to connect to mainframes.

45. How many channels we can create in Distribution Queuing for a Qmgr?

One sender and receiver channel

46. If you create 100 channels for a Qmgr… How can you create 101 Channel?

Normal way like:Define chl(chlname) chltype(type) conname(Ip&port)

47. How many years of experience you have?

3.3 YEARS

48. Are you supporting for L2 or L3?

49. Who is your Vendor?

wipro

50. Who is your Client?

Carrefour

51. Project name?

Infrastructure engineering services.

52. Which ticketing tool you are using?

BMC REMEDY,RADIX, OPEN HP view

53. Which monitoring tool you are using?

OMEGAMON XE , Q pasa, BMC Main View

54. Your monitoring and ticketing tools belong to?

BMC

55. Your mail server and chat server?

lOTUSNODES, sametime

Microsoft outlook, office communicator

56. At which location your L3 team will be?

Client location

57. How can you recover the damaged object and its syntax?

using media recovery we can recreate damaged objects

rcrmqobj -m Qmname -t objtype -n objname

58. Channel attributes?

chltype(),discint(),batchhb(),trptype(),maxmsgl(),xmitq() conname() rqmname()

59. Different status of channel?

initializing,binding,retrying,running,inactive,stopped,paused

60. Are you supporting for 24*7 or on-call?

i have supported on-call .

61. Why do we go for MQ Client?

. No need for a full WebSphere MQ implementation on the client machine.

. Hardware requirements on the client system are reduced.

. System administration requirements are reduced.

. Application running on a client can connect to multiple queue managers on different systems.

. Alternative channels using different transmission protocols can be used

. Reduce the burden on other clients

62. In your company which Client-Server architecture is using?

63. Do you raise any PMR so far?

i have never raised PMR(problem management record)

64. Who send the tickets to you?

users, application team, all the members who are involved in the current project

65. How do you escalate the ticket to L3?

66. Have you ever raised any tickets so far?

yes.

67. Have you ever raised change order?

68. Which flavor you are using on Linux?

Red hat

69. Differences between MQI and MSG Channels?

MQI channels are used between MQ client and MQ sever, those are bi-directional

Types: server connection channel

Client connection channel

MSG channels are uni-directional, and used between QM

1. Sender

2. Receiver

3. Cluster sender

4.cluster rceiver

5.server

6. Client

7.requster

70. Default objects in Cluster?

SYSTEM.CLUSTER.REPOSITORY.QUEUE

SYSTEM.CLUSTER.COMMAND.QUEUE

SYSTEM.CLUSTER.TRANSMISSION.QUEUE

Queues and channels.

71. Difference between Dead-Letter Header and Handler?

if msg’a are come to DLQ, QM will add dead letter header to msg,it contains reason for failure, destination queue and QM details such type of info’n

using dead letter handler you pick the msg’s from DLQ placed it in destination queue

72. What is sync point?

This is nothing but unit of work in two phase commit

73. Tell me something about unit of work?

the period of updates between two sync points is called unit of work.

74. Can you change the log file size?

No.

75. Where the latest information stores in error logs and why?

In the first file.

76. Can you increase the no. of error logs?

77. What is the command to check the disk space on Linux?

df -k df -h

78. Which command we use to check the installed packages on Linux?

rpm -qa | grep mq

79. Command to kill the process on Linux?

$ ps ux ----------to list all the processes.

$ kill -9 Pid -------------to kill particular process...

80. Do you run the runmqdlq program every time?

Depending upon the messages those are coming to the DLQ.

81. How can you check the listener port is running from your desktop?

NETSTAT -a

82. What is the use of telnet, ping and tracert?

ping is used to check the status of remote channel.

telnet is used for remote access of another system.

it shows path taken to reach a particular destination over a network.

83. How can you connect to remote server from your desktop?

Using MSTSC

84. How many primary and secondary logs we can create on windows & Linux (Max)?

windows:primary file:254 ,secondary:253

linux:primary files:510,secondary:509

85. Explain the concept of cluster workload balance?

86. What are the attributes of workload balance?

Defbind(notfixed)

put()

clwluseq(local/any/QMGR)

clwlrank(0-9)

clwlprty(0-9)

clwlwght()

clwlmruse()

87. Explain client-server architecture?

88. What are the pre-requisites for MQ before install?

1. Hardware requirements----disk space

2. Software requirements----o/s specifications

89. Explain the process migration?

90. Have you ever done migration and how?

91. How can we take the Qmgr backup?

- create the backup queue manager

- copy the data and log files from your primary queue manager over the backup queue manager's data and logs

- flag backup qmgr as a backup and replay log extents (strmqm -r)

- periodically copy over the log files prior to the CURRLOG value from the queue manager

saveqmgr -m MQ_BACKUP -r MQ_C1_01 -f MQ_C1_01.txt

92. Error log file name?

error log file name is:AMQERR01,AMQERR02,AMQERR03

93. What is the use of client channel tables?

Using client channel table we can connect with different QM’s and different clients will connect to single QM

94. How many max channels can connect to a Qmgr?

The default for maximum channels is 100 for qmgr. it can be set to higher in the qm.ini.

95. How can you find the max channels are connected to a Qmgr?

dis qmstatus conns

96. Channel components?

chltype() conname() trptype() xmitq() batchsz() hbint()

97. What is the use of trig data in channel?

which chnnel you want to up at trigger event fired.provide channel name

98. What does initiation queue contain?

This will contains trigger massage generated by QM

99. How can we check whether the Qmgr contain Dead-latter queue or not?

DIS QMGR DEADQ(*)

100. How many servers, Qmgrs in your environment?

100 servers. 400 qmgrs.

101. Which programs you use for running the trigger monitor when you use your own initiation queue?(in application and channel triggering)

In application triggering we are using RUNMQTRM

in channel RUNMQCHI INITQ()

102. What is the default size of /var /mqm and /opt /mqm?

Allow 130 MB as a minimum for a WebSphere MQ server and 15 MB as a minimum for a WebSphere MQ client.

x-86 201 mb iseries -183

103. What is the difference between Control & Runmqsc Commands?

RUNMQSC commands are used with in Qm for creating Qm objects and altering QMGR.

CONTROL commands are used for creating starting and running QM, and for set authentication ...

104. In Cluster for Round-Robin process defbind (open) what is happen?

if you set defbind open, all msg’s are placed where the first msg is place

105. Explain the distributed queuing setup?

106. What is meant by distribution queuing?

107. What is difference between distribution and clustering?

in distributions queing we have to create more no of objects like remoteqs. transmission ques and sender, reciever channels for every remote queue manager.

in clustering we can logically connect queue managers with the creation of less no.of qmgr objects .

108. Why we go for clustering?

1.simplifying system administration

2.work load management

3.less no of qm objects like rqd, channels.

4.high availability

109. In cluster we have 4 Qmgrs and having same instance in all Qmgrs I have to send messages to a particular Qmgr then how u configure?

assign clwlrank and clwlprty for particular queue.

110. Tel me prerequisites for MQ admin?

111. R u configured SSL setup?

yes.

ssl address following important security considerations.

1.authantication

2.confidentiality

3.integrity

to install and configure ssl we need

1. a server certificate key store.

2. an https connector

112. Which key u r using in SSL?

symmetric key--- secret keys

Asymmetric key----------public private key pairs

113. What is the command to see the authentications?

DSPMQAUT: It will display the authenticated users

114. What may be reasons for getting channel is in retrying state?

1. if other side receiver channel is not defined

2. may channel was not started

115. What are the reasons for getting messages in dead letter queue?

1.if queue is full

2. Queue put inhibited.

3.Mag’s length is exceeded

116. What happen to messages (persistence& non persistence) if destination queue is full if there is no dead letter queue?

PERSISTENT: if queue is full, msg are coming back to xmitq and channel will be going to retrying state.

NON-PERSISTENT: That type of msg’s are discarded.

117. What is channel state in above case?

retrying

118. Tel me some system default queues?

1.SYSTEM.DEFAULT.ALIAS.QUEUE

2.SYSTEM.DEFAULT.INITIATIONS.QUEUE

3.SYSTEM.DEFAULT.LOCAL.QUEUE

4.SYSTEM.DEFAULT.MODELS.QUEUE

5.SYSTEM.DEFAULT.REMOTE..QUEUE

121.can we define remote queue defination without XMITQ? is it working?

we can define remote queue defination without XMITQ,but XMITQ name should be remote Queue manager name.

121.can we take the backup from XMIT queue massages?

when you are trying to get the backup of xmit queue massages,it will store error information the file. i.e 2016=MQRC_GET_INHIBITED.

122.How to take backup of massages from queue?

amqbcg Qname QMname > E:/mq

123.how to increase no. of primary and secondary log files size?

Go to registry edit,in that only you can change the number of primary and secondary files.after changing the number ,imediatlly those are not effected,when the default primary files are full than only other files are come into picture.

can we define remote queue defination without XMITQ? is it working?

we can define remote queue defination without XMITQ,but XMITQ name should be remote Queue manager name.

121.can we take the backup from XMIT queue massages?

when you are trying to get the backup of xmit queue massages,it will store error information the file. i.e 2016=MQRC_GET_INHIBITED.

122.How to take backup of massages from queue?

amqbcg Qname QMname > E:/mq

123.how to increase no. of primary and secondary log files size?

Tuesday, 26 November 2013

To mount a CD-ROM in different OS.

Using CD-ROMs during installation

WebSphere Application Server is installed from CD-ROM. (Fixpaks are available via download .) The information provided here will be helpful when dealing with CD-ROMs in these various configurations, since each operating system handles CD-ROMs differently.

AIX

In AIX, a CD-ROM must be logically mounted before it can be accessed by the system for installation.
To mount a CD-ROM in AIX:

Insert the CD-ROM into the CD-ROM drive.
Log in as user ROOT or type su - root to login using the root profile.
Create a /cdrom directory by entering mkdir /cdrom.
Enter smit to add a CD-ROM file system.
Select System Storage Management (Physical & Logical Storage) -> File Systems -> Add/Change/Show/Delete File Systems -> CDROM File Systems -> Add a CDROM File System.
Select a device name, such as cd0. CD-ROM file system device names must be unique.
Type /cdrom to get the Mount Point prompt.
Select OK, or press Enter if using the smit ASCII interface, returning to the previous smit level, System Storage Management (Physical & Logical Storage).
Select File Systems -> Mount a File System.
For file system name, select /dev/cd0.
For directory over which to mount, select /cdrom.
For type of file system, select cdrfs.
For Mount as a READ-ONLY system, select Yes.
Select OK, or press Enter if using the smit ASCII interface.
Exit smit.

To install WebSphere Application Server from CD-ROM using tar files:

Add and mount the CD-ROM, following the steps above.
Log in with root authority.
Change the directory to /cdrom.
Invoke ./install.sh by following the standard installation instructions.
When the installation is complete, dismount the CD-ROM by typing: cd .. umount /cdrom.
Eject the CD.

Solaris

If Volume Management is running on Solaris, the operating system will logically mount the CD-ROM as soon as it is inserted into the drive. If Volume Management is not running, you will need to logically mount the CD-ROM.
To mount a CD-ROM on Solaris:

Login as root.
Start the Volume Management daemon by executing the commands: /etc/init.d/volmgt start ps -ef | grep vold
Process /usr/sbin/vold should then be started.

To install WebSphere Application Server from CD-ROM using tar files:

Insert the CD-ROM into the CD-ROM drive and mount, if necessary. The CD-ROM will be mounted, for example, as /cdrom/was350. When a CD-ROM is inserted as root, a File Manager window will be started. Do not kill it. You need this window to eject the CD-ROM. If you kill the window, an orphan process will be using the CD-ROM, resulting in "device busy" errors when you try to eject the CD.
Log in as root and run the CD by typing: cd /cdrom/was350
Invoke ./install.sh by following the standard installation instructions.
When the installation is complete, dismount the CD-ROM by typing: cd eject cdrom.

To detect if a CD-ROM is already in the drive, use the volcheck command. For example: $ volcheck -v /cdrom. If no CD-ROM is present, the message /cdrom has no media will display.

HP-UX

In HP-UX, a CD-ROM must be logically mounted before it can be accessed by the system for installation.
To mount a CD-ROM on HP-UX:

Insert the CD-ROM into the CD-ROM drive.
Log in as user ROOT or type su - root to login using the root profile.
Issue the mount command to determine if the CD-ROM file system is already mounted and operational by verifying that /cdrom is listed. If it is, then you may install the contents of the CD. If not, then you need to create a file system and then logically mount the CD-ROM by continuing with the remaining steps.
Create a directory for the CD-ROM, by typing: mkdir /cdrom.
Type: sam &
Select Disks -> File Systems -> Disk Devices -> CDFS (for CD-ROM File System).
From the menu bar, select Actions -> View more information -> Show Device Files.
Do not select raw devices such as /dev/rdsk/c0t2d0. Make a note of the value for Device File. For example, in HP-UX 10, it might be: /dev/dsk/c0t2d0.
Close the windows and exit sam.
Logically mount the CD-ROM drive manually with the command: mount /dev/dsk/c0t2d0 /cdrom
Issue the mount command again and verify that /cdrom is listed.

The normal mount in HP-UX is sometimes unable to handle very long file names, which may hinder the installation of DB2. To overcome this:

Mount the CD-ROM with the command: pfs_mountd & pfsd 4& pfs_mount /CDROM
Proceed with the installation as normal.
When you have finished using the CD, unmount the CD usith the command: pfs_umount /CDROM

Always unmount the CD before logging out of the session to avoid shutdown problems or the need to reboot.

Windows

Windows recognizes the CD-ROM drive during boot and treasts it as a read-only drive.

Monday, 30 September 2013

JMS

You can configure a stand-alone JMS client and JMS nodes to communicate with service integration bus (SIBus) in WebSphere® Application Server Version 6 and Version 7.

Complete the following steps in WebSphere Application Server. For more information, see the WebSphere Application Server documentation.
1. Create a messaging bus.
2. Add a bus member.
3. Restart the WebSphere Application Server server.
4. Create a queue destination on the bus.
5. Create a JMS queue on the default messaging provider.
6. Create a Queue Connection Factory (QCF) on the default messaging provider.
  Ensure that the messaging provider URL is specified in the QCF definition, particularly if the JMS client and messaging bus are on different computers. The provider endpoint URL must have the following format:
```
bus_member_host_name:7276:BootstrapBasicMessaging
```
  where 7276 is the default SIB endpoint address. Do not use 127.0.0.1 or localhost for the bus member host name.
Test the WebSphere Application Server configuration by using a stand-alone JMS client and completing the following steps.
1. Put the following two JAR files in your class path: com.ibm.ws.sib.client.thin.jms_7.0.0.jar and com.ibm.ws.ejb.thinclient_7.0.0.jar.
  Copy these JAR files from the WebSphere Application Server Version 7 installation directory under the runtimes subdirectory. If you are using a non-IBM JRE, you also need the com.ibm.ws.orb_7.0.0.jar file.
2. Ensure that the provider URL is set to iiop://WAS_server_host_name:boot_strap_port.
3. Ensure that you specify the correct boot strap port.
4. Ensure that the Queue Connection Factory and JMS Queue properties are set to the values defined in the WebSphere Application Server configuration.
5. Compile the JMS client code.
6. Run the JMS client with the following IBM® ORB debug parameters turned on.
```
java -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.D ebug.Output=client.logJMS_Client_Class
```
  This command produces CORBA debug output in the client.log file in the same directory.
Complete the following steps in WebSphere Message Broker.
1. Stop the broker.
2. Create a directory (for example, c:\WebSphere_WAS_Client) and copy the following two JAR files from WebSphere Application Server Version 7 Thin Client for JMS.
  - com.ibm.ws.sib.client.thin.jms_7.0.0.jar
  - com.ibm.ws.ejb.thinclient_7.0.0.jar
  Alternatively, you can copy these files from the WebSphere Application Server installation directory WAS home/runtimes.
3. Configure the JMS service in WebSphere Message Broker by using the mqsichangeproperties command. The JMS provider WebSphere_WAS_Client exists; therefore you can change the client JAR file path for that provider.
```
mqsichangeproperties broker_name -c JMSProviders -o WebSphere_WAS_Client -n jarsURL -v WAS_thin_client_JAR_file_path
```
4. Configure the JMSInput node as shown in the following example. For more information about these properties, see JMSInput node.
  - Specify the name of the JMS provider; for example, Client for WebSphere Application Server.
  - Specify the initial context factory; for example, com.ibm.websphere.naming.WsnInitialContextFactory.
  - Specify the location of the JNDI bindings in the format iiop://WAS_server_host_name:WAS_server_boot_strap_port.
  - Set the connection factory name to QCF.
5. Ensure that the JMS connection has been established before the message flow starts by using the Windows Event Viewer.

Wednesday, 25 September 2013

Importent Definitions asked in interview

What is a ketstore?

A keystore is a database that contains private keys with their associated certificates. The keystore will be used for encrypting/signing something with your private key

What is A truststore ?

What is a Truststore contains certificates to trust like CA certs and remote server certs. Trust stores will be used mostly to authenticate remote servers etc.

What is root certificate?

a root certificate is either an unsigned public key certificate or a self-signed certificate that identifies the Root Certificate Authority (CA). Digital certificates are verified using a chain of trust. The trust anchor for the digital certificate is the Root Certificate Authority (CA).

A root certificate is the top-most certificate of the tree, the private key of which is used to “sign” other certificates. All certificates immediately below the root certificate inherit the trustworthiness of the root certificate. Certificates further down the tree also depend on the trustworthiness of the intermediates.

The root certificate is usually made trustworthy by some mechanism other than a certificate, such as by secure physical distribution. For example, some of the most well-known root certificates are distributed in the Internet browsers by their manufacturers. [From Wikipedia]

What is an intermediate certificate?

Trusted Root CA certificate can also be used to create another certificate, which in turn will then be used to issue SSL Certificates. So, an intermediate certificate is a subordinate certificate issued by the trusted root specifically to issue end-entity server certificates. The result is a certificate chain that begins at the trusted root CA, through the intermediate and ending with the SSL certificate issued to you. Such certificates are called chained root certificates. As the Intermediate Certificate is issued by the Trusted Root CA, any SSL Certificates issued by the Intermediate Certificate inherits the trust of the Trusted Root – effectively creating a certification chain of trust.

Why to use intermediate certificates?

There are mainly two advantages.

1) Creating certificates directly from the CA root certificate increases the risk of root certificate compromise, and if the CA root certificate is compromised, the entire trust infrastructure built by the SSL provider will fail. The usage of intermediate certificates for issuing SSL certificates to end entities, therefore, provides an added level of security.

2) Intermediates also help by constraining the size of the Certificate Revocation List (CRL) associated with a certificate product. By periodically rolling over the intermediate CA that signs the end entity certificates CRL’s are kept to a minimum. Maintaining optimal CRL sizes ensures that customers have a smooth and seamless experience visiting SSL-secured websites while full security is maintained transparently to customers/end users.

What is in-bound and out-bound on the SSL settings in websphere?

Simply imagine the bus routes in your city. They are named north-bound/souuth-bound etc.. Based on the direction they travel.

In websphere inbound/outbound does the same. They specify the direction of the SSL connection. Inbound represents all server endpoints that receive connection. Outbound represents all the client side connections from the carious servers within the cell.

What is a WebSphere application server release means?

Simply it is a new version. Like 6.0, 6.1, 7.0, 8.0 etc. These releases include major new function, archictural changes etc..

What is a refresh pack?

A refresh pack includes minor new features and fixes. Say 6.0.1 is a refresh pack for 6.0 and 6.0.2 is a refresh pack for 6.0.1. Say now you are applying refresh pack 6.0.2, it includes all the fueatures and fixes in 6.0.1 plus fixpack and interm fixes published for 6.0.1. So a refresh pack is cumulative.

What is a fix pack?

A fix pack is a package of fixes. Fixpacks install on top of refresh packs or on top of previous packs. For example your present software version is 6.1.0 and you are applying 6.1.0.23, this is called fixpack and will also be called as fixpack 23 for 6.1.0. After applying this fixpack23, your server version will be 6.1.0.23.

A fix pack uninstalls all interm fixes applied to the release since the lasr refresh pack or fixpack was installed. Therefore IBM suggests checking the list of delivered fixes to determine if an intermfix needs to be installed.
May not be correct but in other words, a fix pack is a package of fixes for a refresh pack.

What is fix/interim fix/Emergency fix etc..?

These are single fixes published to resolve/fix an product defect/known issue. The next release of fixpack will contain these interim/emergency fixes and you are expected to apply the new fix pack

Session Replication

What is session?
————————–
* A Session is a series of requests to a servlet, originating from the same user at the same browser

How session works?
——————————
* session ID Allows to keep track of individual users
* Session ID generated on first request and send back to browser with first response.
* Session ID then arrives with each subsequent request
* Cookies, URL rewriting and SSL (if request is on HTTPS) are ways to track the session IDs

Distributed sessions
——————————
Session management can store session-related information in …
* In application server memory (the default). This storage options is knows as in-memory sessions.
* In a database. This storage option is known as database persistent sessions.
* In another WebSphere Application Server instance. This storage option is known as memory-to-memory sessions.

* Distributed sessions are essential for using HTTP sessions for the failover facility
* Plug-in maintains Session affinity by sending requests with session ID to cluster member where that session has been previously created
* On the failure of cluster member, plug-in routes requests to other members
* When cluster member receives a request associated with a session ID that it currently does not have in memory, it can obtain the required session state by accessing the external store (database or memory-to-memory).

Memory-Memory replication
—————————————–
* In Memory-to-Memory session replication, session data from owner server replicates (copies) in one or more other application server using Data Replication Service
=>Data Replication Service (DRS) is an internal WebSphere Application Server component that replicates data. You can configure DRS by creating a replication domain. Replication Domain can be created either manually from Environment page of admin console or automatically at cluster create time.
* This requires creation of a data replication service instance in owner server that communicates to other data replication service instances in remote application servers
* This can be achieved by creating a replication domain and configuring the session manager of cluster members to use memory-to-memory replication.

* A server can run in one of the following three modes:
* Client mode: server only sends copies of sessions it owns
* Server mode: server only stores backup copies of other servers
* Both mode: server sends copies of session it owns and acts as a backup table for sessions owned by other application server

* Two different topologies are possible based on above three modes
* Peer-to-Peer topology
* Client/Server topology

=> Peer-to-Peer topology
* Each server stores a session in it’s own memory and also stores sessions to, and retrieves from, other application servers.
* Each application server acts as client by retrieving session from other servers and acts as server by providing sessions to other application servers

* This is the default configuration and each application server can:
* Host the Web Application leveraging the HTTP Session
* Send Changes to the HTTP Session that it owns
* Receive backup copies of the HTTP session from all of the other servers in the cluster

=>Steps to configure
1. Create replication domain
configure request timeout, encryption and number of replicas
2. go to Servers ->Application servers -> First Cluster member -> Sessionmanagement -> Distributed environment settings -> Memoryto-memory replication
3. Select the replication domain created in first step
4. Select “Both Client and Server” as replication mode
5. Click Ok and Save to master configuration
6. Repeat above steps for all the cluster members
7. Once done, restart the cluster

=>Advantages
* No additional processes and products are required to avoid a single point of failure.
* Reduce the time and cost required to configure and maintain additional processes or products
=>Disadvantages
* It can consume large amounts of memory with many users. This can cause a performance impact
* Does not provide stable configuration for cluster with only 2 members, because of two way replication?

=>Client/Server topology
* Application Servers act as either a replication Client or a Server
* Replication servers store sessions in there own memory and provide session info to clients.
* Dedicated replication servers just store session but do not respond to users’ requests
* Client application servers send session information to replication servers and retrieve as needed. Clients respond to user requests
* Application servers configured as Server can not host any applications. They act as pure data store for backup sessions and receive updates from Clients
* Backup data is isolated into a separate JVM
* Client replicas will contain only local session data
* Application servers configured as Servers must be started before starting Clients

=>Steps to configure
1. Create replication domain
configure request timeout, encryption and number of replicas
2. go to Servers ->Application servers -> First Cluster member -> Sessionmanagement -> Distributed environment settings -> Memoryto-memory replication
3. configure cluster1 members as client
4. configure cluster2 members as Server
5. start cluster2 first and then cluster1

=>Advantages
* Clearly distinguishes the role of client and server.
* Reduces the consumption of memory on each application server
* Better performance
* Allows recycle of a backup server without affecting the servers running applications
* Better choice if your hardware varies across the cluster
=>Disadvantages
* Additional application servers have to be configured and maintained over and above those that interact with the user
* Need multiple replication servers to avoid a single point of failure

Deployment of application through WSADMIN

Now let us learn how to install, start/stop and update or deployment tasks of applications using WSADMIN on to clusters and single servers.

Deploying Applications

You can install the application in batch mode, using the install command, or you can install the application in interactive mode using the installinteractive command. Interactive mode prompts you through a series of tasks to provide information.All the options available to use are listed here in the IBM documentation.

note: words in bold are command or options and in italic are your inputs

To find out the options available to install the EAR file, run:

AdminApp.options()

Installing EAR application:

Using Batch Mode:

If you are deploying on single servers….make sure that server is running before you execute the commands.

AdminApp.install(‘/home/joseph/applications/SampleApp.ear’, ‘[-server test_server1]‘)

If you are deploying it in network deployment/ Clusters, you must connect to WSADMIN of deployment manager.

AdminApp.install(‘/home/joseph/applications/SampleApp.ear’, ‘[-cluster sample_cluster]‘)

Using Interactive Mode:

AdminApp.installInteractive(‘/home/joseph/applications/SampleApp.ear’)

now it will take you through a series of questions before finishing the deployment.

After the deployment is done, you need to perform two more steps

step1. Save the changes by issuing

AdminConfig.save()

step2. Synchronize the changes across all nodes by using

Sync1 = AdminControl.completeObjectName(‘type=NodeSync,node=myNodeName,*’)

and then

AdminControl.invoke(Sync1, ‘sync’)

step2 is required only for network deployment models.

Starting Applications

this involves two steps.
step1: getting the handler of the application, means .. locating where the application is running. To do this we use a variable and use querynames option on admincontrol object

appHandle= AdminControl.queryNames ‘cell=SampleCell,node=virt_node1,type=ApplicationManager,process=test_server1,*’)
print appHandle

then you will get an output like the one below

WebSphere:cell=SampleCell,name=ApplicationManager,mbeanIdentifier=ApplicationManager,type=ApplicationManager,node=virt_node1,process=test_server1

step2: Now we execute the command to start the application

AdminControl.invoke(appHandle, ‘startApplication’, ‘Dynamic Cache Monitor’)

You can do both steps at once by using the below format

AdminControl.invoke(‘WebSphere:name=ApplicationManager,process=test_server1,node=virt_node1,type=ApplicationManager,mbeanIdentifier=ApplicationManager,cell=SampleCell, ‘startApplication‘, ‘["Dynamic Cache Monitor"]‘, ‘[java.lang.String]‘)

Stopping Application

The steps are same as starting the application except ‘startApplication’ should be renamed to ‘stopApplication’

But, if you want to stop all applications running on a server… after executing step1 of above
Step2: you need to first get the list of applications

# get line separator
import java.lang.System as sys
lineSeparator = sys.getProperty(‘line.separator’)
apps_list = AdminControl.queryNames(‘cell=SampleCell,node=virt_node1,type=Application,process=test_server1,*’).split(lineSeparator)
print apps_list

Step3: now we need to create a loop to stop the applications one by one

for app in apps_list:
appName = AdminControl.getAttribute(app, ‘name’)
AdminControl.invoke(appHandle, ‘stopApplication’, appName)

Updating Application

We have different options to update applications, like, full update, module update, single file update etc…Similar to the install, we do have both batch mode and interactive mode for updating [update and updateinteractive]. All the options available to use are listed here in the IBM documentation.

updating entire application
AdminApp.update(‘SampleApp’, ‘app’, ‘[-operation update -contents /home/joseph/applications/SampleAppv2.ear ]‘)

Adding a new module to EJB
AdminApp.update(‘SampleApp’, ‘modulefile’, ‘[-operation addupdate -contents /home/joseph/applications/Increment.jar -contenturi Increment.jar -nodeployejb
-BindJndiForEJBNonMessageBinding [["Increment Enterprise Java Bean" Increment Increment.jar,META-INF/ejb-jar.xml Inc]]]’)

Updating Single file
AdminApp.update(‘SampleApp’, ‘file’, ‘[-operation update -contents /home/joseph/applications/my.xml -contenturi SampleApp/my.xml]‘)

TIP: Use the taskInfo command of the AdminApp object to obtain information about the data that is needed for your application.

for example, you want to know what options you need to supply for mapping modules to servers…use the following taskinfo command

AdminApp taskInfo <ear file> MapModulesToServers

TO VIEW JVM settings:

w to enable the verbose gc logging on Websphere Application server

Wednesday, June 19, 2013, 5:41 AM

Posted By: Akhilesh

Hi Everyone,

Execute the following steps to enable the verbose:gc logging in your setup. Or you can use some steps to check the current status of your Java Virtual Machine configuration by using wsadmin tool

1.Launch the wsadmin. Run these commands in a command prompt window:

:/IBM/WebSphere/AppServer/profiles/AppSrv01/bin

:/IBM/WebSphere/AppServer/profiles/AppSrv01/bin $ ./wsadmin.sh

This output will appear after running the command:

WASX7209I: Connected Node DefaultNode ?process "server1" by SOAP connector Process Type UnManagedProcess

wsadmin>

2. Set the server environment.

wsadmin>set server1 [$AdminConfig getid /Cell:mycell/Node:mynode/Server:server1/]

server1(cells/DefaultNode/nodes/DefaultNode/servers/server1|server.xml#Server_1214551833906)

3.Get the definition of JVM.

wsadmin>set jvm [$AdminConfig list JavaVirtualMachine $server1]

(cells/DefaultNode/nodes/DefaultNode/servers/server1|server.xml#JavaVirtualMachine_1214551833937)

4.Check the current JVM setting.

wsadmin>$AdminConfig show $jvm

{bootClasspath {}}

{classpath {}}

{debugArgs "-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket.server=y,suspend=n,address=7777"}

{debugMode false}

{disableJIT false}

{genericJvmArguments {}}

{hprofArguments {}}

{initialHeapSize 128}

{maximumHeapSize 256}

{runHProf false}

{systemProperties {}}

{verboseModeClass false}

{verboseModeGarbageCollection false}

{verboseModeJNI false}

5.Set the verboseModeGarbageCollection variable to true.

wsadmin>$AdminConfig modify $jvm {{verboseModeGarbageCollection true}}

6.Check the changed JVM setting.

wsadmin>$AdminConfig show $jvm

{bootClasspath {}}

{classpath {}}

{debugArgs "-Djava.compiler=NONE -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777"}

{debugMode false}

{disableJIT false}

{genericJvmArguments {}}

{hprofArguments {}}

{initialHeapSize 128}

{maximumHeapSize 256}

{runHProf false}

{systemProperties {}}

{verboseModeClass false}

{verboseModeGarbageCollection true}

{verboseModeJNI false}

7.Save the JVM setting.

wsadmin>$AdminConfig save

8.Close the wsadmin console.

wsadmin>quit

9.Restart the Windows service IBM WebSphere Application Server.

10.Check the verbose:gc logs. By Default, the verbose:gc logs are located here:

/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1 $ cat native_stdout.log

/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1 $ cat native_stderr.log

Sunday, 1 December 2013

Websphere MQ Notes and interview questions

Tuesday, 26 November 2013

To mount a CD-ROM in different OS.

Using CD-ROMs during installation

AIX

Solaris

HP-UX

Windows

Monday, 30 September 2013

JMS

Wednesday, 25 September 2013

Importent Definitions asked in interview

Session Replication

Deployment of application through WSADMIN

w to enable the verbose gc logging on Websphere Application server

Monday, 29 July 2013

Unable to login to remote system.

Search This Blog

About Me