A) WAS V7 profile templates
----> cell
----> Default
----> Managed
----> dmgr
----> management
----> secureproxy
12) What is the use of Service Integration Bus ?
A) ----> WAS 6.0, has a new feature called "Service Integration Bus" i.e. a new pure-Java JMS engine.
----> SIB is a complete JMS v1.1 provider implementation.
----> A bus is a group of one or more interconnected servers or server clusters that have been added as members of the bus. Applications connect to a bus at one of the messaging engines associated with its bus members.
----> The following capabilities are provided by a service integration bus:
1. Application sharing message with other system.
2. A message-producing application
3. A message-consuming application
----> A service integration bus supports asynchronous messaging; that is, sending messages asynchronously.
----> Asynchronous messaging is possible regardless of whether the consuming application is running or not, or if the destination is available or not.
----> Point-to-point and publish/subscribe messaging are also supported
13) How do you check heap is used by JVM ?
A) ----> You can use third party monitoring tools like Wily Introscope or ITCAM and also there is inbuild monitoring tool in admin console called TPV ( Tivoli Performance Viewer) under Monitoring and Tuning.
14) How will you verify the version of WAS in WebSphere?
A) ----> go to directory bin directory of web sphere install root
/opt/IBM/WebSphere/App Server/bin
and run the command
./versionInfo.sh
You can get the version of web sphere application server installed.
14) What are the differences between web sphere 4.0,5.0 and 6.0.
A) -----> Web Sphere Studio 3.5, comes up with Visual Age for Java.
-----> WSAD 5.0 supports J2EE 1.3 java specifications.
------> RAD 6.0 (RATIONAL APPLICATION DEVELOPER) supports J2EE 1.4 and integrated with Eclipse 3.0, UML Visual Editor, Tomcat Jakarta, Ant scripting, EJB universal test client and SOA tools.
15) In IBM WSAD, server crashes sometime while running in debug mode .Is there any way to prevent it ?
A) -----> you need to increase the memory allocated to java process in WAS. In WASD deployment description there is a setting for java process memory allocation. Increase the Xml values in it and see
(OR)
-----> You need to bump the heap size memory default is 0,0 Enable administrative console in the wsad in the server settings I believe its configuration tab or environment . And log on to the admin console on port 9060 when u start the server in normal mode HTTP://localhost:9060/admin. Then go to server/ server1/process definition/JVM Increase the initial heap and maximum heap size in there.. Give atleast (512MB,1.5Gb) And restart the server in debug mode. Its should work.
13) How do you check heap is used by JVM ?
A) ----> You can use third party monitoring tools like Wily Introscope or ITCAM and also there is inbuild monitoring tool in admin console called TPV ( Tivoli Performance Viewer) under Monitoring and Tuning.
14) How will you verify the version of WAS in WebSphere?
A) ----> go to directory bin directory of web sphere install root
/opt/IBM/WebSphere/App Server/bin
and run the command
./versionInfo.sh
You can get the version of web sphere application server installed.
14) What are the differences between web sphere 4.0,5.0 and 6.0.
A) -----> Web Sphere Studio 3.5, comes up with Visual Age for Java.
-----> WSAD 5.0 supports J2EE 1.3 java specifications.
------> RAD 6.0 (RATIONAL APPLICATION DEVELOPER) supports J2EE 1.4 and integrated with Eclipse 3.0, UML Visual Editor, Tomcat Jakarta, Ant scripting, EJB universal test client and SOA tools.
15) In IBM WSAD, server crashes sometime while running in debug mode .Is there any way to prevent it ?
A) -----> you need to increase the memory allocated to java process in WAS. In WASD deployment description there is a setting for java process memory allocation. Increase the Xml values in it and see
(OR)
-----> You need to bump the heap size memory default is 0,0 Enable administrative console in the wsad in the server settings I believe its configuration tab or environment . And log on to the admin console on port 9060 when u start the server in normal mode HTTP://localhost:9060/admin. Then go to server/ server1/process definition/JVM Increase the initial heap and maximum heap size in there.. Give atleast (512MB,1.5Gb) And restart the server in debug mode. Its should work.
No comments:
Post a Comment