regular tickets for an application server and webserver
Answers were Sorted based on User's Feedback
Answer / vivek
Regular tickets that we get for an
Application server is : deployements,apps server restarts
due to hung threads ,configuration changes, changing
urls,creating data source,application not loading
properly,Node agents out of sync
for Web Server : paged not found,application login url does
not work,pluggin not getting loaded properly , instance
restarts.
| Is This Answer Correct ? | 13 Yes | 1 No |
Answer / guest
For ApplicationServer :1)deployments.2)AppServer restarts
due to hung threads.3)Configure changes.4)Changing URL's.
5)Creating DataSource.6)Application not loaded properly.
7)NodeAgent out of synchronization.
For WebServer : 1)page not found.2)Application logging URL
doesn't work.3)Flugin not loaded properly. 4)Instance
restart.
| Is This Answer Correct ? | 5 Yes | 3 No |
what are the different ways for giving input without using mqinput node?
Is it necessary to register a controller command in cmdreg table?
How many types of deployment descriptors are available? What are they?
How many no full repository queue managers are required for creating a cluster. What is the difference between full and partial repositories?
Explain something about attribute?
what is the command used for stopping the queue manager?
what is the content of the configuration manager repository?
Which script to change the java sdk used by profile?
when you use migration wizard (pmt) for websphere application server 8, do you expect to have all profile services up and running again?
what are the objects used in web sphere mq?
What is the master repository?
When you are deploying an application, if you got Out Of Memory exception, what you will do