<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-7932682</id><updated>2012-01-01T06:21:39.258+05:30</updated><category term='UNIX'/><category term='IHS'/><category term='Vista'/><category term='Fedora'/><category term='WPS'/><category term='JAVA'/><category term='Performance Monitoring'/><category term='VirtualBox'/><category term='CM'/><category term='RAD 7.0'/><category term='OS X Lion'/><category term='3rd party'/><category term='Environment'/><category term='TechNote'/><category term='AE'/><category term='commands'/><category term='Logs'/><category term='tips'/><category term='Solaris'/><category term='Test 252'/><category term='windows'/><category term='SSL'/><category term='Virtualization'/><category term='Migration Notes'/><category term='503'/><category term='WAS'/><category term='uninstall'/><category term='64 bit'/><category term='Plugin'/><category term='JVM'/><category term='6.0'/><category term='VMWARE'/><category term='SLES'/><category term='Troubleshooting'/><category term='502'/><category term='faq'/><category term='PMR'/><category term='FileNet'/><category term='Workplace'/><category term='WebSphere'/><category term='WAS 7'/><category term='Best Practices'/><category term='PERL'/><category term='gunzip'/><category term='Profiles'/><category term='tar'/><category term='Open Source'/><category term='vmdk'/><category term='X86'/><category term='Definitions'/><category term='6.1'/><category term='Linux'/><category term='WMQ'/><category term='InfoCenter'/><category term='MIGRATION'/><category term='fixpacks'/><category term='unzip'/><category term='collector'/><category term='AIX'/><category term='Installation'/><title type='text'>WebSphere</title><subtitle type='html'>WebSphere Administration and much more</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>85</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7932682.post-4524886054370715143</id><published>2011-11-30T08:49:00.008+05:30</published><updated>2011-11-30T08:57:51.579+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Virtualization'/><category scheme='http://www.blogger.com/atom/ns#' term='VMWARE'/><category scheme='http://www.blogger.com/atom/ns#' term='X86'/><category scheme='http://www.blogger.com/atom/ns#' term='vmdk'/><category scheme='http://www.blogger.com/atom/ns#' term='OS X Lion'/><title type='text'>vmdk fails to kick installer</title><content type='html'>Loaded the vmx file, along with vmdk as hard drive and 40GB file as another hard drive.&lt;br /&gt;Loading process failed. So, went to boot manager &gt; boot options menu, selected efi SCSI Device 1, and started over again.&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-ud8vBEo-XJ0/TtWhuscqnaI/AAAAAAAAG5A/TFwTh3fhjY8/s1600/bootmanager.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 235px;" src="http://4.bp.blogspot.com/-ud8vBEo-XJ0/TtWhuscqnaI/AAAAAAAAG5A/TFwTh3fhjY8/s400/bootmanager.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5680624328575196578" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/-OK1MJMJP4uU/TtWhnOgVbrI/AAAAAAAAG40/ukS891k0XJQ/s1600/bootdevice.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 245px;" src="http://1.bp.blogspot.com/-OK1MJMJP4uU/TtWhnOgVbrI/AAAAAAAAG40/ukS891k0XJQ/s400/bootdevice.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5680624200278437554" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/-6WkStf_woL0/TtWhh3jVMnI/AAAAAAAAG4o/SOyGBxplzEo/s1600/efiboot.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 222px;" src="http://4.bp.blogspot.com/-6WkStf_woL0/TtWhh3jVMnI/AAAAAAAAG4o/SOyGBxplzEo/s400/efiboot.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5680624108217643634" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/-OlVXfMG0Vwo/TtWg5C5bbCI/AAAAAAAAG4c/d6OaVTA-4M8/s1600/error.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 247px;" src="http://3.bp.blogspot.com/-OlVXfMG0Vwo/TtWg5C5bbCI/AAAAAAAAG4c/d6OaVTA-4M8/s400/error.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5680623406888479778" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4524886054370715143?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4524886054370715143/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4524886054370715143' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4524886054370715143'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4524886054370715143'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/11/vmdk-fails-to-kick-installer.html' title='vmdk fails to kick installer'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-ud8vBEo-XJ0/TtWhuscqnaI/AAAAAAAAG5A/TFwTh3fhjY8/s72-c/bootmanager.PNG' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4872892058470902276</id><published>2011-10-31T06:15:00.001+05:30</published><updated>2011-10-31T06:20:01.341+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='Best Practices'/><category scheme='http://www.blogger.com/atom/ns#' term='tips'/><category scheme='http://www.blogger.com/atom/ns#' term='TechNote'/><title type='text'>Webcast replay: Best Practices for Installing WebSphere Application Server V7 Feature Packs</title><content type='html'>IBM Webcast on "&lt;span style="font-weight:bold;"&gt;Best Practices for Installing WebSphere Application Server V7 Feature Packs&lt;/span&gt;"&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg27023316&amp;myns=swgws&amp;mynp=OCSSEQTP&amp;mync=R"&gt;&lt;br /&gt;http://www-01.ibm.com/support/docview.wss?uid=swg27023316&amp;myns=swgws&amp;mynp=OCSSEQTP&amp;mync=R&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4872892058470902276?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='related' href='http://www-01.ibm.com/support/docview.wss?uid=swg27023316&amp;myns=swgws&amp;mynp=OCSSEQTP&amp;mync=R' title='Webcast replay: Best Practices for Installing WebSphere Application Server V7 Feature Packs'/><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4872892058470902276/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4872892058470902276' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4872892058470902276'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4872892058470902276'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/10/webcast-replay-best-practices-for.html' title='Webcast replay: Best Practices for Installing WebSphere Application Server V7 Feature Packs'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3254559819382799980</id><published>2011-08-02T21:54:00.002+05:30</published><updated>2011-08-02T21:56:27.217+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='3rd party'/><category scheme='http://www.blogger.com/atom/ns#' term='Open Source'/><category scheme='http://www.blogger.com/atom/ns#' term='Performance Monitoring'/><category scheme='http://www.blogger.com/atom/ns#' term='JVM'/><category scheme='http://www.blogger.com/atom/ns#' term='JAVA'/><title type='text'>Java monitoring tools</title><content type='html'>&lt;h1 class="title topictitle1"&gt;Java monitoring tools&lt;/h1&gt; &lt;div class="body refbody"&gt;&lt;p class="shortdesc"&gt;There are a few tools you can use to monitor and identify performance inhibitors in your Java™ applications.&lt;/p&gt; &lt;div class="section"&gt; &lt;dl class="dl"&gt;&lt;dt class="dt"&gt;vmstat&lt;/dt&gt;&lt;dd class="dd"&gt;Provides information about various system resources.  It reports statistics on kernel threads in the run queue as well as in the wait queue, memory usage, paging space, disk I/O, interrupts, system calls, context switches, and CPU activity. &lt;/dd&gt;&lt;dt class="dt"&gt;iostat&lt;/dt&gt;&lt;dd class="dd"&gt;Reports detailed disk I/O information.&lt;/dd&gt;&lt;dt class="dt"&gt;topas&lt;/dt&gt;&lt;dd class="dd"&gt;Reports CPU, network, disk I/O, &lt;span class="ph"&gt;Workload Manager&lt;/span&gt; and process activity.&lt;/dd&gt;&lt;dt class="dt"&gt;tprof&lt;/dt&gt;&lt;dd class="dd"&gt;Profiles the application to pinpoint any hot routines or methods, which can be considered performance problems.&lt;/dd&gt;&lt;dt class="dt"&gt;ps -mo &lt;em class="ph i"&gt;THREAD&lt;/em&gt;&lt;/dt&gt;&lt;dd class="dd"&gt;Shows to which CPU a process or thread is bound.&lt;/dd&gt;&lt;dt class="dt"&gt; Java profilers [-Xrunhprof, Xrunjpa64]&lt;/dt&gt;&lt;dd class="dd"&gt;Determines which routines or methods are the most heavily used. &lt;/dd&gt;&lt;dt class="dt"&gt;java -verbose:gc&lt;/dt&gt;&lt;dd class="dd"&gt;Checks the impact of garbage collection on your application.  It reports total time spent doing garbage collection, average time per garbage collection, average memory collected per garbage collection, and average objects collected per garbage collection.&lt;/dd&gt;&lt;/dl&gt;&lt;br /&gt;&lt;p&gt;Here are 10 tools useful for Java application performance troubleshooting.&lt;/p&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;b&gt;jconsole&lt;/b&gt;  comes together with JDK 1.5 and above. It is a Java Monitoring and  Management Console - JMX-compliant graphical tool for monitoring a Java  virtual machine. It can monitor both local and remote JVMs.&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="https://visualvm.dev.java.net/"&gt;&lt;font color="#7f1d1d"&gt;VisualVM&lt;/font&gt;&lt;/a&gt;  is a visual tool that integrates several existing JDK software tools  and lightweight memory and CPU profiling capabilities. This tool is  designed for both production and development time use and further  enhances the capability of monitoring and performance analysis for the  Java SE platform.&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="http://www.alphaworks.ibm.com/tech/heapanalyzer?open&amp;amp;S_TACT=105AGX59&amp;amp;S_CMP=GRsite-jw22"&gt;&lt;font color="#7f1d1d"&gt;HeapAnalyzer&lt;/font&gt;&lt;/a&gt;  allows the finding of a possible Java™ heap leak area through its  heuristic search engine and analysis of the JavaTM heap dump in Java  applications. It analyzes Java heap dumps by parsing the Java heap dump,  creating directional graphs, transforming them into directional trees,  and executing the heuristic search engine.&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="http://java.sun.com/developer/technicalArticles/Programming/perfanal/"&gt;&lt;font color="#7f1d1d"&gt;PerfAnal&lt;/font&gt;&lt;/a&gt; is a GUI-based tool for analyzing the performance of applications on the Java 2 Platform. You can use &lt;code&gt;PerfAnal&lt;/code&gt; to identify performance problems in your code and locate code that needs tuning.&lt;/li&gt;  &lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="http://jamonapi.sourceforge.net/"&gt;&lt;font color="#7f1d1d"&gt;JAMon&lt;/font&gt;&lt;/a&gt; is a free, simple, high performance, thread safe, Java API that allows developers to easily monitor production applications.&lt;/li&gt;  &lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="http://www.eclipse.org/mat/"&gt;&lt;font color="#7f1d1d"&gt;Eclipse Memory Analyzer&lt;/font&gt;&lt;/a&gt; is a fast and feature-rich &lt;b&gt;Java heap analyzer&lt;/b&gt; that helps you find memory leaks and reduce memory consumption.&lt;/li&gt;  &lt;/ul&gt;&lt;ul&gt;&lt;br /&gt;&lt;li&gt;&lt;a href="http://www.tagtraum.com/gcviewer.html"&gt;&lt;font color="#7f1d1d"&gt;GCViewer&lt;/font&gt;&lt;/a&gt;  is a free open source tool to visualize data produced by the Java VM  options -verbose:gc  and -Xloggc:&amp;lt;file&amp;gt;. It also calculates  garbage collection related performance metrics (throughput, accumulated  pauses, longest pause, etc.).&lt;/li&gt;&lt;/ul&gt;&lt;p&gt; &lt;/p&gt;&lt;/div&gt; &lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3254559819382799980?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3254559819382799980/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3254559819382799980' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3254559819382799980'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3254559819382799980'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/08/java-monitoring-tools.html' title='Java monitoring tools'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3095435829129944805</id><published>2011-04-06T23:30:00.002+05:30</published><updated>2011-04-06T23:35:23.673+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='commands'/><title type='text'>WASServiceCmd utility</title><content type='html'>I faced lot of issues with WebSphere services on Windows 2008 R2 64bit boxes.&lt;br /&gt;WASService adds the WAS Services to Windows services list, but fails to stop/start them.&lt;br /&gt;&lt;br /&gt;&lt;p class="MsoNormal" style=""&gt;If I bounce the box, then services are getting started. If I stop them, it is setting the service status as blank. If I start it again, it throws "Windows could not start IBM WebSphere Application Server – servicename on local computer". When checked in the event logs "&lt;span style="font-size: 9pt; font-family: &amp;quot;Segoe UI&amp;quot;,&amp;quot;sans-serif&amp;quot;;"&gt;The IBM WebSphere Application Server V7.0 - CellManager01 service terminated with service-specific error %%134220456." is the message.&lt;/span&gt;&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt; &lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;This is how I have added WAS Services to Windows Services&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;D:\IBM\WebSphere\AppServer\bin\WASService.exe -add CellManager01 -serverName dmgr -profilePath D:\IBM\WebSphere\AppServer\profiles\Dmgr01 -wasHome D:\IBM\WebSphere\AppServer -logFile D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr\SystemOut.log -logRoot D:\IBM\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr -restart true -startType automatic -stopArgs &amp;quot;-username xxxxxxxxx -password xxxxxxx&amp;quot; –encodeParams&lt;/p&gt;&lt;p class="MsoNormal" style=""&gt;&lt;br /&gt;&lt;/p&gt;&lt;p class="MsoNormal" style=""&gt;To solve this, one can use WASServiceCmd Utility. This utility is easy to use, grabs all the info you need to pass, creates the service command, executes it.&lt;/p&gt;  &lt;p class="MsoNormal" style=""&gt;&lt;br /&gt;&lt;/p&gt;&lt;p class="MsoNormal" style=""&gt;Here is the technote about WASServiceCmd&lt;br /&gt;&lt;/p&gt;  &lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;amp;uid=swg21397335"&gt;http://www-01.ibm.com/support/docview.wss?rs=180&amp;amp;uid=swg21397335&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Here is my WASServiceCmd log entry&lt;br /&gt;wasservice.exe -add &amp;quot;CellManager01&amp;quot; -serverName &amp;quot;dmgr&amp;quot; -profilePath &amp;quot;D:\IBM\WebSphere\AppServer\profiles\Dmgr01&amp;quot; -encodeParams -stopArgs &amp;quot;-username xxxxxxxx -password ******** -startType automatic -restart true &lt;br /&gt;  wasservice.exe -add &amp;quot;Node01&amp;quot; -serverName &amp;quot;nodeagent&amp;quot; -profilePath &amp;quot;D:\IBM\WebSphere\AppServer\profiles\wlmprime01&amp;quot; -encodeParams -stopArgs &amp;quot;-username xxxxxxx -password ******** -startType automatic -restart true&lt;br /&gt;  &lt;br /&gt;These services are now, properly working.&lt;br /&gt; &lt;br clear="all"&gt;&lt;span style="color: rgb(153, 153, 153);"&gt;--&lt;br /&gt;Thanks and Regards&lt;/span&gt;&lt;br style="color: rgb(153, 153, 153);"&gt;&lt;span style="color: rgb(153, 153, 153);"&gt;Bhaskar Ramaraju&lt;/span&gt;&lt;br style="color: rgb(153, 153, 153);"&gt;  &lt;a style="color: rgb(153, 153, 153);" href="http://www.linkedin.com/in/ramarajubhaskar" target="_blank"&gt;http://www.linkedin.com/in/ramarajubhaskar&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3095435829129944805?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3095435829129944805/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3095435829129944805' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3095435829129944805'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3095435829129944805'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/04/wasservicecmd-utility.html' title='WASServiceCmd utility'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5944575685642720248</id><published>2011-03-28T21:47:00.001+05:30</published><updated>2011-03-28T21:49:48.752+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='64 bit'/><title type='text'>Elevated user privileges</title><content type='html'>Problem: I have edited a file, say, httpd.conf on Windows 2008 R2 64 bit server. I saved the file and bounced the apache. But, my changes were not in effect. I looked deep into it, then realized that, Windows is storing a copy of httpd.conf on Desktop in VirtualData folder, under this folder, created entire folder structure and stored the file in there.&lt;br /&gt;   To avoid this, edit the files or run the commands as an administrator or disable User Access Control (UAC).&lt;br /&gt;&lt;br /&gt;Technote from IBM&lt;br /&gt; &lt;table border="0" cellpadding="0" cellspacing="0" width="443"&gt; &lt;tbody&gt; &lt;tr valign="top"&gt; &lt;td height="80"&gt;&lt;h1 class="smalltitle"&gt;&lt;font size="2"&gt;Running WebSphere Application Server command-line tools  might require elevated Microsoft Windows user account privileges&lt;/font&gt;&lt;/h1&gt;&lt;font size="2"&gt;&lt;img class="display-img" alt="" src="//www.ibm.com/i/c.gif" height="6" width="1"&gt;&lt;/font&gt;  &lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt; &lt;table border="0" cellpadding="0" cellspacing="0" width="443"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td class="docfnt"&gt;  &lt;table border="0" cellpadding="0" cellspacing="0" width="443"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td width="443"&gt; &lt;table border="0" cellpadding="0" cellspacing="0"&gt; &lt;tbody&gt; &lt;tr valign="top"&gt; &lt;td width="438"&gt; &lt;table border="0" cellpadding="0" cellspacing="0" width="443"&gt; &lt;tbody&gt; &lt;tr&gt; &lt;td class="v14-header-1efix" height="19" valign="top" width="443"&gt;&lt;font size="2"&gt;&lt;b&gt; Technote  (troubleshooting)&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;font size="2"&gt; &lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td height="20" valign="bottom" width="443"&gt;&lt;font size="2"&gt;&lt;b&gt;Problem(Abstract)&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td width="443"&gt;&lt;font size="2"&gt;To successfully use some IBM WebSphere Application Server  command-line tools, you might need to explicitly elevate Microsoft Windows user  account privileges if you are not using the built-in administrator account to  run the commands. This action is applicable to the Windows 7, Windows Vista,  Windows Server 2008 R2, and Windows Server 2008 operating systems  only.&lt;br /&gt;&lt;br /&gt;If Windows User Account Control (UAC) is disabled on your system,  then this document is not applicable. &lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;font size="2"&gt; &lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr valign="top"&gt; &lt;td width="438"&gt; &lt;font size="2"&gt;&lt;br /&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt; &lt;td height="20" valign="bottom" width="443"&gt;&lt;font size="2"&gt;&lt;b&gt;Cause&lt;/b&gt;&lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td width="443"&gt;&lt;font size="2"&gt;You must use a Windows user account that has full Administrator  account privileges for certain operations on Windows 7, Windows Vista, Windows  Server 2008 R2, and Windows Server 2008 operating systems. Commands that involve  Windows services or access to the Windows system registry require that type of  full authority due to the Windows User Account Control implementation for those  two operating systems. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;For example, if you use a regular  administrator group account that is not the built-in Administrator account, then  you will likely need to explicitly elevate your user account privileges when you  run the launchpad or Profile management tool commands. This action assumes that  your operating system is running with the default values for system-wide  security policies that are related to the Windows User Account Control.  &lt;/font&gt;&lt;/td&gt;&lt;/tr&gt; &lt;tr&gt; &lt;td&gt;&lt;font size="2"&gt; &lt;/font&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;font size="2"&gt;&lt;br /&gt;&lt;/font&gt;&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;amp;context=SSEQTP&amp;amp;q1=Win7_2008_R2&amp;amp;uid=swg21315375&amp;amp;loc=en_US&amp;amp;cs=utf-8&amp;amp;lang=en"&gt;http://www-01.ibm.com/support/docview.wss?rs=180&amp;amp;context=SSEQTP&amp;amp;q1=Win7_2008_R2&amp;amp;uid=swg21315375&amp;amp;loc=en_US&amp;amp;cs=utf-8&amp;amp;lang=en&lt;/a&gt;&lt;br clear="all"&gt;  &lt;span style="color: rgb(153, 153, 153);"&gt;--&lt;br /&gt;Thanks and Regards&lt;/span&gt;&lt;br style="color: rgb(153, 153, 153);"&gt;&lt;span style="color: rgb(153, 153, 153);"&gt;Bhaskar Ramaraju&lt;/span&gt;&lt;br style="color: rgb(153, 153, 153);"&gt; &lt;a style="color: rgb(153, 153, 153);" href="http://www.linkedin.com/in/ramarajubhaskar" target="_blank"&gt;http://www.linkedin.com/in/ramarajubhaskar&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5944575685642720248?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5944575685642720248/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5944575685642720248' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5944575685642720248'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5944575685642720248'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/03/elevated-user-privileges.html' title='Elevated user privileges'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1349394261588125029</id><published>2011-01-20T23:34:00.001+05:30</published><updated>2011-01-20T23:38:47.260+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='503'/><category scheme='http://www.blogger.com/atom/ns#' term='502'/><category scheme='http://www.blogger.com/atom/ns#' term='InfoCenter'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>Proxy Error Bad Gateway</title><content type='html'>&lt;p class="mobile-photo"&gt;&lt;a href="http://4.bp.blogspot.com/_nWTtVfnJrDY/TTh5UC6RnYI/AAAAAAAAFc0/RKOGmtK5qqk/s1600/infocenter_error-704437.jpg"&gt;&lt;img src="http://4.bp.blogspot.com/_nWTtVfnJrDY/TTh5UC6RnYI/AAAAAAAAFc0/RKOGmtK5qqk/s400/infocenter_error-704437.jpg"  border="0" alt="" id="BLOGGER_PHOTO_ID_5564330724901887362" /&gt;&lt;/a&gt;&lt;/p&gt;&lt;dl&gt;&lt;dt&gt;InfoCenter is down.&lt;/dt&gt;&lt;/dl&gt;To understand whats wrong - Proxy error, bad gateway etc, this is a temp state. Upstream server response is broken and so the message.&lt;br /&gt;&lt;br /&gt;&lt;dl&gt;&lt;dt&gt;502 Bad Gateway&lt;/dt&gt;&lt;dd&gt;The server was acting as a gateway or proxy and received an invalid response from the upstream server.&lt;sup id="cite_ref-RFC_2616_1-42" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#cite_note-RFC_2616-1"&gt;&lt;span&gt;[&lt;/span&gt;2&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/dd&gt;  &lt;dt&gt;&lt;span id="503"&gt;&lt;/span&gt;503 Service Unavailable&lt;/dt&gt;&lt;dd&gt;The server is currently unavailable (because it is overloaded or down for maintenance).&lt;sup id="cite_ref-RFC_2616_1-43" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#cite_note-RFC_2616-1"&gt;&lt;span&gt;[&lt;/span&gt;2&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt; Generally, this is a temporary state.&lt;/dd&gt;  &lt;dt&gt;&lt;span id="504"&gt;&lt;/span&gt;504 Gateway Timeout&lt;/dt&gt;&lt;dd&gt;The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.&lt;sup id="cite_ref-RFC_2616_1-44" class="reference"&gt;&lt;a href="http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#cite_note-RFC_2616-1"&gt;&lt;span&gt;[&lt;/span&gt;2&lt;span&gt;]&lt;/span&gt;&lt;/a&gt;&lt;/sup&gt;&lt;/dd&gt;  &lt;/dl&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1349394261588125029?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1349394261588125029/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1349394261588125029' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1349394261588125029'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1349394261588125029'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2011/01/proxy-error-bad-gateway.html' title='Proxy Error Bad Gateway'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_nWTtVfnJrDY/TTh5UC6RnYI/AAAAAAAAFc0/RKOGmtK5qqk/s72-c/infocenter_error-704437.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8112992475452687102</id><published>2010-12-20T21:44:00.002+05:30</published><updated>2010-12-21T09:35:17.419+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='JAVA'/><title type='text'>Xms!=Xmx</title><content type='html'>Setting the initial Java heap minimum equal to the Java heap maximum is  not recommended.  Doing so can delay the start of garbage collection  until the heap is full.  Therefore, the first time the Garbage Collector  runs is a very expensive operation. &lt;br /&gt; The heap is also likely to be very fragmented by the time heap  compaction is required.  This is also a very expensive operation. &lt;br /&gt; &lt;br clear="all"&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21160795&amp;amp;acss=was121610"&gt;http://www-01.ibm.com/support/docview.wss?uid=swg21160795&amp;amp;acss=was121610&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8112992475452687102?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8112992475452687102/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8112992475452687102' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8112992475452687102'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8112992475452687102'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/12/xmsxmx.html' title='Xms!=Xmx'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4019395884911379489</id><published>2010-11-12T22:51:00.001+05:30</published><updated>2010-11-13T21:42:55.516+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='PERL'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>password recovery from stash file</title><content type='html'>----------------&lt;a href="http://unstash.pl"&gt;unstash.pl&lt;/a&gt; begin ------------------------&lt;br /&gt;use strict;&lt;br /&gt;&lt;br /&gt;die &amp;quot;Usage: $0 &amp;lt;stash file&amp;gt;\n&amp;quot; if $#ARGV != 0;&lt;br /&gt;&lt;br /&gt;my $file=$ARGV[0];&lt;br /&gt;open(F,$file) || die &amp;quot;Can&amp;#39;t open $file: $!&amp;quot;;&lt;br /&gt;  &lt;br /&gt;my $stash;&lt;br /&gt;read F,$stash,1024;&lt;br /&gt;&lt;br /&gt;my @unstash=map { $_^0xf5 } unpack(&amp;quot;C*&amp;quot;,$stash);&lt;br /&gt;&lt;br /&gt;foreach my $c (@unstash) {&lt;br /&gt;    last if $c eq 0;&lt;br /&gt;    printf &amp;quot;%c&amp;quot;,$c;&lt;br /&gt;}&lt;br /&gt;printf &amp;quot;\n&amp;quot;;&lt;br /&gt;  ---------------------&lt;a href="http://unstash.pl"&gt;unstash.pl&lt;/a&gt; end-----------------&lt;br /&gt;&lt;br /&gt;perl &lt;a href="http://unstash.pl"&gt;unstash.pl&lt;/a&gt; key.sth&lt;br /&gt;where key.sth is the stash file&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4019395884911379489?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4019395884911379489/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4019395884911379489' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4019395884911379489'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4019395884911379489'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/11/password-recovery-from-stash-file.html' title='password recovery from stash file'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6736464930377317280</id><published>2010-09-25T02:58:00.002+05:30</published><updated>2010-09-25T03:01:40.960+05:30</updated><title type='text'>recycle logs</title><content type='html'>To recycle JVM Logs [a.k.a SystemOut.log and SystemErr.log] -&lt;br /&gt;We have separate log slice for SystemOut and SystemErr. Whenever I bounce the server, I try to clear the logs, take a backup of the logs in a folder with time and date stamp for reference. I may hold such historical backup of the logs for say two months.&lt;br /&gt;  Here is a batch script to create a folder with todays date and time stamp, move the files into that folder.&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM This script is to recycle the jvm logs&lt;br /&gt;&lt;br /&gt;@REM To recycle&lt;br /&gt;@REM 1. set the log home&lt;br /&gt;  set jvm_log_home=&amp;quot;&amp;lt;YOUR_LOG_HOME&amp;gt;&amp;quot;&lt;br /&gt;set log_bak_home=&amp;quot;&amp;lt;YOUR_LOG_BACKUP_HOME&amp;quot;&lt;br /&gt;@REM 2. Set Date variable&lt;br /&gt;set today=%date:~4,2%-%date:~7,2%%date:~10,4%%time:~0,2%%time:~3,2%%time:~6,2%%&lt;br /&gt;  @REM 3. create a folder with date stamp&lt;br /&gt;mkdir %log_bak_home%\%today%&lt;br /&gt;@REM 3. move the logs to that folder&lt;br /&gt;move %jvm_log_home%\*.* %log_bak_home%\%today%&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Whenever I bounce the server, I try to cleanup the cache too. Here is the script to clean up the cache.&lt;br /&gt;  Here is the batch script to clean the cache -&lt;br /&gt;&lt;br /&gt;@echo off&lt;br /&gt;@REM This script is to recycle the temp/cache on the local server&lt;br /&gt;@REM To cleanup the cache&lt;br /&gt;@REM 1. goto profile home temp&lt;br /&gt;set profile_temp_home=&amp;quot;&amp;lt;YOUR_PROFILEHOME_TEMP_NODE&amp;quot;&lt;br /&gt;  echo &amp;quot;profile path=%profile_temp_home%&amp;quot;&lt;br /&gt;@REM 2. goto servername&lt;br /&gt;set server_name=&amp;quot;&amp;lt;YOUR_SERVER_NAME&amp;quot;&lt;br /&gt;@REM 3. delete all under servername&lt;br /&gt;echo &amp;quot;here i am %profile_temp_home%&amp;quot;&lt;br /&gt;  FOR /D %%i IN (%profile_temp_home%\%server_name%\*) DO (&lt;br /&gt;@REM echo %%i&lt;br /&gt;rmdir /S /Q &amp;quot;%%i&amp;quot;&lt;br /&gt;)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6736464930377317280?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6736464930377317280/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6736464930377317280' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6736464930377317280'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6736464930377317280'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/09/recycle-logs.html' title='recycle logs'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-799665507156625235</id><published>2010-08-31T02:31:00.001+05:30</published><updated>2010-08-31T02:40:47.468+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WMQ'/><title type='text'>MQ Notes ... continued</title><content type='html'>Use the control commands with a command file&lt;br /&gt;__ Prepare a WebSphere MQ command file with the same commands you entered&lt;br /&gt;       interactively in Step 2. Call the file &amp;quot;E1_ST03.txt&amp;quot;.&lt;br /&gt;            DIS QMGR&lt;br /&gt;            DIS Q(SYSTEM*)&lt;br /&gt;            DEF QL(QL.A) DESCR(&amp;#39;QL.A Text&amp;#39;)&lt;br /&gt;            DIS QL(QL.A)&lt;br /&gt;            ALTER QL(QL.A) MAXDEPTH(1000)&lt;br /&gt;            DIS QL(QL.A)&lt;br /&gt;            DEF QL(QL.B) DESCR(&amp;#39;QL.B Text&amp;#39;)&lt;br /&gt;            DEF QL(QL.B) REPLACE +&lt;br /&gt;            MAXDEPTH(2000)&lt;br /&gt;            DIS QL(QL.B)&lt;p&gt;__ Process the command file and direct the results to the file &amp;quot;report&amp;quot;. Have a look at&lt;br /&gt;       the file containing the results.&lt;br /&gt;                         • runmqsc &amp;lt; E1_ST03.txt &amp;gt; report&lt;p&gt;5724-H72 (C) Copyright IBM Corp. 1994, 2005.  ALL RIGHTS RESERVED.&lt;br /&gt;Starting MQSC for queue manager MQ.QM1.&lt;p&gt;&lt;br /&gt;     1 : DIS QMGR&lt;br /&gt;AMQ8408: Display Queue Manager details.&lt;br /&gt;   QMNAME(MQ.QM1)                          ACCTCONO(DISABLED)&lt;br /&gt;   ACCTINT(1800)                           ACCTMQI(OFF)&lt;br /&gt;   ACCTQ(OFF)                              ACTIVREC(MSG)&lt;br /&gt;   ALTDATE(2010-08-18)                     ALTTIME(12.21.00)&lt;br /&gt;   AUTHOREV(DISABLED)                      CCSID(1208)&lt;br /&gt;   CHAD(DISABLED)                          CHADEV(DISABLED)&lt;br /&gt;   CHADEXIT( )                             CHLEV(DISABLED)&lt;br /&gt;   CLWLDATA( )                             CLWLEXIT( )&lt;br /&gt;   CLWLLEN(100)                            CLWLMRUC(999999999)&lt;br /&gt;   CLWLUSEQ(LOCAL)                         CMDLEVEL(600)&lt;br /&gt;   COMMANDQ(SYSTEM.ADMIN.COMMAND.QUEUE)    CRDATE(2010-08-18)&lt;br /&gt;   CRTIME(12.21.00)                        DEADQ( )&lt;br /&gt;   DEFXMITQ( )                             DESCR( )&lt;br /&gt;   DISTL(YES)                              INHIBTEV(DISABLED)&lt;br /&gt;   IPADDRV(IPV4)                           LOCALEV(DISABLED)&lt;br /&gt;   LOGGEREV(DISABLED)                      MAXHANDS(256)&lt;br /&gt;   MAXMSGL(4194304)                        MAXPRTY(9)&lt;br /&gt;   MAXUMSGS(10000)                         MONACLS(QMGR)&lt;br /&gt;   MONCHL(OFF)                             MONQ(OFF)&lt;br /&gt;   PERFMEV(DISABLED)                       PLATFORM(UNIX)&lt;br /&gt;   QMID(MQ.QM1_2010-08-18_12.21.00)        REMOTEEV(DISABLED)&lt;br /&gt;   REPOS( )                                REPOSNL( )&lt;br /&gt;   ROUTEREC(MSG)                           SCHINIT(QMGR)&lt;br /&gt;   SCMDSERV(QMGR)                          SSLCRLNL( )&lt;br /&gt;   SSLCRYP( )                              SSLEV(DISABLED)&lt;br /&gt;   SSLFIPS(NO)                          &lt;br /&gt;   SSLKEYR(/var/mqm/qmgrs/MQ!QM1/ssl/key)&lt;br /&gt;   SSLRKEYC(0)                             STATACLS(QMGR)&lt;br /&gt;   STATCHL(OFF)                            STATINT(1800)&lt;br /&gt;   STATMQI(OFF)                            STATQ(OFF)&lt;br /&gt;   STRSTPEV(ENABLED)                       SYNCPT&lt;br /&gt;   TRIGINT(999999999)                   &lt;br /&gt;     2 : DIS Q(SYSTEM*)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.ACCOUNTING.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.ACTIVITY.QUEUE)      TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.CHANNEL.EVENT)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.LOGGER.EVENT)        TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.PERFM.EVENT)         TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.QMGR.EVENT)          TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.STATISTICS.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.TRACE.ROUTE.QUEUE)   TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.AUTH.DATA.QUEUE)           TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CHANNEL.INITQ)             TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CHANNEL.SYNCQ)             TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CICS.INITIATION.QUEUE)     TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE)     TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.REPOSITORY.QUEUE)&lt;br /&gt;   TYPE(QLOCAL)                         &lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEAD.LETTER.QUEUE)         TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.ALIAS.QUEUE)       TYPE(QALIAS)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.INITIATION.QUEUE)&lt;br /&gt;   TYPE(QLOCAL)                         &lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.LOCAL.QUEUE)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.MODEL.QUEUE)       TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.REMOTE.QUEUE)      TYPE(QREMOTE)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.MQEXPLORER.REPLY.MODEL)    TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.MQSC.REPLY.QUEUE)          TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.PENDING.DATA.QUEUE)        TYPE(QLOCAL)&lt;br /&gt;     3 : DEF QL(QL.A) DESCR(&amp;#39;QL.A Text&amp;#39;)&lt;br /&gt;AMQ8150: WebSphere MQ object already exists.&lt;br /&gt;     4 : DIS QL(QL.A)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-18)&lt;br /&gt;   ALTTIME(13.55.59)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.05)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR(QL.A QUEUE A BLAH)                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(1000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                        &lt;br /&gt;     5 : ALTER QL(QL.A) MAXDEPTH(1000)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;     6 : DIS QL(QL.A)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-19)&lt;br /&gt;   ALTTIME(11.39.46)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.05)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR(QL.A QUEUE A BLAH)                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(1000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                        &lt;br /&gt;     7 : DEF QL(QL.B) DESCR(&amp;#39;QL.B Text&amp;#39;)&lt;br /&gt;AMQ8150: WebSphere MQ object already exists.&lt;br /&gt;     8 : DEF QL(QL.B) REPLACE +&lt;br /&gt;       : MAXDEPTH(2000)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;     9 : DIS QL(QL.B)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.B)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-19)&lt;br /&gt;   ALTTIME(11.39.46)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.16)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR( )                                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(2000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                        &lt;br /&gt;9 MQSC commands read.&lt;br /&gt;No commands have a syntax error.&lt;br /&gt;2 valid MQSC commands could not be processed.&lt;p&gt;&lt;br /&gt;Use the sample programs&lt;br /&gt;__ Put messages on the local queue QL.A.&lt;br /&gt;   • amqsput QL.A&lt;br /&gt;   (The queue manager name is optional, because it is the default queue manager)&lt;br /&gt;   amqsput is a sample program. This can be found in mqm/samp/bin&lt;br /&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QL.A&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QL.A&lt;br /&gt;bhaskar&lt;br /&gt;ramaraju&lt;br /&gt;so what&lt;br /&gt;know what&lt;br /&gt;yes a lot&lt;p&gt;__ Browse the messages of the queue. Direct the output to a file and look at the results.&lt;br /&gt;   • amqsbcg QL.A &amp;gt; out&lt;br /&gt;   (The queue manager name is optional, because it is the default queue manager)&lt;p&gt;&lt;br /&gt;AMQSBCG0 - starts here&lt;br /&gt;**********************&lt;br /&gt; &lt;br /&gt; MQOPEN - &amp;#39;QL.A&amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; MQGET of message number 1 &lt;br /&gt;****Message descriptor****&lt;p&gt;  StrucId  : &amp;#39;MD  &amp;#39;  Version : 2&lt;br /&gt;  Report   : 0  MsgType : 8&lt;br /&gt;  Expiry   : -1  Feedback : 0&lt;br /&gt;  Encoding : 546  CodedCharSetId : 1208&lt;br /&gt;  Format : &amp;#39;MQSTR   &amp;#39;&lt;br /&gt;  Priority : 0  Persistence : 0&lt;br /&gt;  MsgId : X&amp;#39;414D51204D512E514D312020202020207D736D4C02090020&amp;#39;&lt;br /&gt;  CorrelId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  BackoutCount : 0&lt;br /&gt;  ReplyToQ       : &amp;#39;                                                &amp;#39;&lt;br /&gt;  ReplyToQMgr    : &amp;#39;MQ.QM1                                          &amp;#39;&lt;br /&gt;  ** Identity Context&lt;br /&gt;  UserIdentifier : &amp;#39;mqm         &amp;#39;&lt;br /&gt;  AccountingToken : &lt;br /&gt;   X&amp;#39;0335303200000000000000000000000000000000000000000000000000000006&amp;#39;&lt;br /&gt;  ApplIdentityData : &amp;#39;                                &amp;#39;&lt;br /&gt;  ** Origin Context&lt;br /&gt;  PutApplType    : &amp;#39;6&amp;#39;&lt;br /&gt;  PutApplName    : &amp;#39;amqsput                     &amp;#39;&lt;br /&gt;  PutDate  : &amp;#39;20100819&amp;#39;    PutTime  : &amp;#39;18442779&amp;#39;&lt;br /&gt;  ApplOriginData : &amp;#39;    &amp;#39;&lt;p&gt;  GroupId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  MsgSeqNumber   : &amp;#39;1&amp;#39;&lt;br /&gt;  Offset         : &amp;#39;0&amp;#39;&lt;br /&gt;  MsgFlags       : &amp;#39;0&amp;#39;&lt;br /&gt;  OriginalLength : &amp;#39;-1&amp;#39;&lt;br /&gt; &lt;br /&gt;****   Message      ****&lt;br /&gt; &lt;br /&gt; length - 7 bytes&lt;br /&gt; &lt;br /&gt;00000000:  6268 6173 6B61 72                                 &amp;#39;bhaskar         &amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; MQGET of message number 2 &lt;br /&gt;****Message descriptor****&lt;p&gt;  StrucId  : &amp;#39;MD  &amp;#39;  Version : 2&lt;br /&gt;  Report   : 0  MsgType : 8&lt;br /&gt;  Expiry   : -1  Feedback : 0&lt;br /&gt;  Encoding : 546  CodedCharSetId : 1208&lt;br /&gt;  Format : &amp;#39;MQSTR   &amp;#39;&lt;br /&gt;  Priority : 0  Persistence : 0&lt;br /&gt;  MsgId : X&amp;#39;414D51204D512E514D312020202020207D736D4C03090020&amp;#39;&lt;br /&gt;  CorrelId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  BackoutCount : 0&lt;br /&gt;  ReplyToQ       : &amp;#39;                                                &amp;#39;&lt;br /&gt;  ReplyToQMgr    : &amp;#39;MQ.QM1                                          &amp;#39;&lt;br /&gt;  ** Identity Context&lt;br /&gt;  UserIdentifier : &amp;#39;mqm         &amp;#39;&lt;br /&gt;  AccountingToken : &lt;br /&gt;   X&amp;#39;0335303200000000000000000000000000000000000000000000000000000006&amp;#39;&lt;br /&gt;  ApplIdentityData : &amp;#39;                                &amp;#39;&lt;br /&gt;  ** Origin Context&lt;br /&gt;  PutApplType    : &amp;#39;6&amp;#39;&lt;br /&gt;  PutApplName    : &amp;#39;amqsput                     &amp;#39;&lt;br /&gt;  PutDate  : &amp;#39;20100819&amp;#39;    PutTime  : &amp;#39;18443040&amp;#39;&lt;br /&gt;  ApplOriginData : &amp;#39;    &amp;#39;&lt;p&gt;  GroupId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  MsgSeqNumber   : &amp;#39;1&amp;#39;&lt;br /&gt;  Offset         : &amp;#39;0&amp;#39;&lt;br /&gt;  MsgFlags       : &amp;#39;0&amp;#39;&lt;br /&gt;  OriginalLength : &amp;#39;-1&amp;#39;&lt;br /&gt; &lt;br /&gt;****   Message      ****&lt;br /&gt; &lt;br /&gt; length - 8 bytes&lt;br /&gt; &lt;br /&gt;00000000:  7261 6D61 7261 6A75                               &amp;#39;ramaraju        &amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; MQGET of message number 3 &lt;br /&gt;****Message descriptor****&lt;p&gt;  StrucId  : &amp;#39;MD  &amp;#39;  Version : 2&lt;br /&gt;  Report   : 0  MsgType : 8&lt;br /&gt;  Expiry   : -1  Feedback : 0&lt;br /&gt;  Encoding : 546  CodedCharSetId : 1208&lt;br /&gt;  Format : &amp;#39;MQSTR   &amp;#39;&lt;br /&gt;  Priority : 0  Persistence : 0&lt;br /&gt;  MsgId : X&amp;#39;414D51204D512E514D312020202020207D736D4C04090020&amp;#39;&lt;br /&gt;  CorrelId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  BackoutCount : 0&lt;br /&gt;  ReplyToQ       : &amp;#39;                                                &amp;#39;&lt;br /&gt;  ReplyToQMgr    : &amp;#39;MQ.QM1                                          &amp;#39;&lt;br /&gt;  ** Identity Context&lt;br /&gt;  UserIdentifier : &amp;#39;mqm         &amp;#39;&lt;br /&gt;  AccountingToken : &lt;br /&gt;   X&amp;#39;0335303200000000000000000000000000000000000000000000000000000006&amp;#39;&lt;br /&gt;  ApplIdentityData : &amp;#39;                                &amp;#39;&lt;br /&gt;  ** Origin Context&lt;br /&gt;  PutApplType    : &amp;#39;6&amp;#39;&lt;br /&gt;  PutApplName    : &amp;#39;amqsput                     &amp;#39;&lt;br /&gt;  PutDate  : &amp;#39;20100819&amp;#39;    PutTime  : &amp;#39;18443598&amp;#39;&lt;br /&gt;  ApplOriginData : &amp;#39;    &amp;#39;&lt;p&gt;  GroupId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  MsgSeqNumber   : &amp;#39;1&amp;#39;&lt;br /&gt;  Offset         : &amp;#39;0&amp;#39;&lt;br /&gt;  MsgFlags       : &amp;#39;0&amp;#39;&lt;br /&gt;  OriginalLength : &amp;#39;-1&amp;#39;&lt;br /&gt; &lt;br /&gt;****   Message      ****&lt;br /&gt; &lt;br /&gt; length - 7 bytes&lt;br /&gt; &lt;br /&gt;00000000:  736F 2077 6861 74                                 &amp;#39;so what         &amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; MQGET of message number 4 &lt;br /&gt;****Message descriptor****&lt;p&gt;  StrucId  : &amp;#39;MD  &amp;#39;  Version : 2&lt;br /&gt;  Report   : 0  MsgType : 8&lt;br /&gt;  Expiry   : -1  Feedback : 0&lt;br /&gt;  Encoding : 546  CodedCharSetId : 1208&lt;br /&gt;  Format : &amp;#39;MQSTR   &amp;#39;&lt;br /&gt;  Priority : 0  Persistence : 0&lt;br /&gt;  MsgId : X&amp;#39;414D51204D512E514D312020202020207D736D4C05090020&amp;#39;&lt;br /&gt;  CorrelId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  BackoutCount : 0&lt;br /&gt;  ReplyToQ       : &amp;#39;                                                &amp;#39;&lt;br /&gt;  ReplyToQMgr    : &amp;#39;MQ.QM1                                          &amp;#39;&lt;br /&gt;  ** Identity Context&lt;br /&gt;  UserIdentifier : &amp;#39;mqm         &amp;#39;&lt;br /&gt;  AccountingToken : &lt;br /&gt;   X&amp;#39;0335303200000000000000000000000000000000000000000000000000000006&amp;#39;&lt;br /&gt;  ApplIdentityData : &amp;#39;                                &amp;#39;&lt;br /&gt;  ** Origin Context&lt;br /&gt;  PutApplType    : &amp;#39;6&amp;#39;&lt;br /&gt;  PutApplName    : &amp;#39;amqsput                     &amp;#39;&lt;br /&gt;  PutDate  : &amp;#39;20100819&amp;#39;    PutTime  : &amp;#39;18444307&amp;#39;&lt;br /&gt;  ApplOriginData : &amp;#39;    &amp;#39;&lt;p&gt;  GroupId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  MsgSeqNumber   : &amp;#39;1&amp;#39;&lt;br /&gt;  Offset         : &amp;#39;0&amp;#39;&lt;br /&gt;  MsgFlags       : &amp;#39;0&amp;#39;&lt;br /&gt;  OriginalLength : &amp;#39;-1&amp;#39;&lt;br /&gt; &lt;br /&gt;****   Message      ****&lt;br /&gt; &lt;br /&gt; length - 9 bytes&lt;br /&gt; &lt;br /&gt;00000000:  6B6E 6F77 2077 6861 74                            &amp;#39;know what       &amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; MQGET of message number 5 &lt;br /&gt;****Message descriptor****&lt;p&gt;  StrucId  : &amp;#39;MD  &amp;#39;  Version : 2&lt;br /&gt;  Report   : 0  MsgType : 8&lt;br /&gt;  Expiry   : -1  Feedback : 0&lt;br /&gt;  Encoding : 546  CodedCharSetId : 1208&lt;br /&gt;  Format : &amp;#39;MQSTR   &amp;#39;&lt;br /&gt;  Priority : 0  Persistence : 0&lt;br /&gt;  MsgId : X&amp;#39;414D51204D512E514D312020202020207D736D4C06090020&amp;#39;&lt;br /&gt;  CorrelId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  BackoutCount : 0&lt;br /&gt;  ReplyToQ       : &amp;#39;                                                &amp;#39;&lt;br /&gt;  ReplyToQMgr    : &amp;#39;MQ.QM1                                          &amp;#39;&lt;br /&gt;  ** Identity Context&lt;br /&gt;  UserIdentifier : &amp;#39;mqm         &amp;#39;&lt;br /&gt;  AccountingToken : &lt;br /&gt;   X&amp;#39;0335303200000000000000000000000000000000000000000000000000000006&amp;#39;&lt;br /&gt;  ApplIdentityData : &amp;#39;                                &amp;#39;&lt;br /&gt;  ** Origin Context&lt;br /&gt;  PutApplType    : &amp;#39;6&amp;#39;&lt;br /&gt;  PutApplName    : &amp;#39;amqsput                     &amp;#39;&lt;br /&gt;  PutDate  : &amp;#39;20100819&amp;#39;    PutTime  : &amp;#39;18444667&amp;#39;&lt;br /&gt;  ApplOriginData : &amp;#39;    &amp;#39;&lt;p&gt;  GroupId : X&amp;#39;000000000000000000000000000000000000000000000000&amp;#39;&lt;br /&gt;  MsgSeqNumber   : &amp;#39;1&amp;#39;&lt;br /&gt;  Offset         : &amp;#39;0&amp;#39;&lt;br /&gt;  MsgFlags       : &amp;#39;0&amp;#39;&lt;br /&gt;  OriginalLength : &amp;#39;-1&amp;#39;&lt;br /&gt; &lt;br /&gt;****   Message      ****&lt;br /&gt; &lt;br /&gt; length - 9 bytes&lt;br /&gt; &lt;br /&gt;00000000:  7965 7320 6120 6C6F 74                            &amp;#39;yes a lot       &amp;#39;&lt;br /&gt; &lt;br /&gt; &lt;br /&gt; &lt;br /&gt; No more messages &lt;br /&gt; MQCLOSE&lt;br /&gt; MQDISC&lt;p&gt;&lt;p&gt;__ Get the messages from the queue to make the queue empty.&lt;br /&gt;   • amqsget QL.A&lt;br /&gt;   (The queue manager name is optional, because it is the default queue manager)&lt;br /&gt;Sample AMQSGET0 start&lt;br /&gt;message &amp;lt;bhaskar&amp;gt;&lt;br /&gt;message &amp;lt;ramaraju&amp;gt;&lt;br /&gt;message &amp;lt;so what&amp;gt;&lt;br /&gt;message &amp;lt;know what&amp;gt;&lt;br /&gt;message &amp;lt;yes a lot&amp;gt;&lt;br /&gt;no more messages&lt;br /&gt;Sample AMQSGET0 end&lt;p&gt;This cleans the queue.&lt;p&gt;&lt;br /&gt;Work with alias queues&lt;br /&gt;__ Create an alias queue QA.A which resolves to your local queue QL.A.&lt;br /&gt;                       • DEF QA(QA.A) TARGQ(QL.A)&lt;br /&gt;__ Inhibit put requests on the alias queue.&lt;br /&gt;                       • ALTER QA(QA.A) PUT(DISABLED)&lt;br /&gt;__ Change QL.B to inhibit put requests on your local queue QL.B.&lt;br /&gt;                       • ALTER QL(QL.B) PUT(DISABLED)&lt;br /&gt;__ Create an alias queue QA.B which resolves to your local queue QL.B.&lt;br /&gt;                       • DEF QA(QA.B) TARGQ(QL.B)&lt;br /&gt;DEF QA(QA.A) TARGQ(QL.A)&lt;br /&gt;     1 : DEF QA(QA.A) TARGQ(QL.A)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;ALTER QA(QA.A) PUT(DISABLED)&lt;br /&gt;     2 : ALTER QA(QA.A) PUT(DISABLED)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;ALTER QL(QL.B) PUT(DISABLED)&lt;br /&gt;     3 : ALTER QL(QL.B) PUT(DISABLED)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;DEF QA(QA.B) TARQG(QL.B)&lt;br /&gt;     4 : DEF QA(QA.B) TARQG(QL.B)&lt;br /&gt;AMQ8405: Syntax error detected at or near end of command segment below:-&lt;br /&gt;DEF QA(QA.B) T&lt;p&gt;AMQ8427: Valid syntax for the MQSC command:&lt;p&gt;  DEFINE QALIAS(q_name)                                                       &lt;br /&gt;     [ CLUSNL(namelist_name) ]               [ CLUSTER(cluster_name) ]         &lt;br /&gt;     [ DEFBIND( NOTFIXED | OPEN ) ]          [ DEFPRTY(integer) ]              &lt;br /&gt;     [ DEFPSIST( YES | NO ) ]                [ DESCR(string) ]                 &lt;br /&gt;     [ GET( ENABLED | DISABLED ) ]           [ LIKE(qalias_name) ]             &lt;br /&gt;     [ REPLACE | NOREPLACE ]                 [ PUT( ENABLED | DISABLED ) ]     &lt;br /&gt;     [ SCOPE( QMGR | CELL ) ]                [ TARGQ(string) ]                 &lt;br /&gt;     [ CLWLRANK(integer) ]                   [ CLWLPRTY(integer) ]             &lt;br /&gt; &lt;br /&gt;DEF QA(QA.B) TARGQ(QL.B)&lt;br /&gt;     5 : DEF QA(QA.B) TARGQ(QL.B)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;END&lt;br /&gt;     6 : END&lt;br /&gt;5 MQSC commands read.&lt;p&gt;__ Try to put messages on both alias and local queues using the sample program.&lt;br /&gt;                       • amqsput QL.A&lt;br /&gt;                       • amqsput QA.A&lt;br /&gt;                       • amqsput QL.B&lt;br /&gt;                       • amqsput QA.B&lt;p&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QL.A&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QL.A&lt;br /&gt;bhaskar is the name of the this person&lt;br /&gt;u know if u dont know you better know&lt;p&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QA.A&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QA.A&lt;br /&gt;do you really want to test the alias queues&lt;br /&gt;MQPUT ended with reason code 2051&lt;br /&gt;Sample AMQSPUT0 end&lt;br /&gt;[mqm@localhost ~]$ &lt;p&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QL.B&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QL.B&lt;br /&gt;I am testing ql.b&lt;br /&gt;MQPUT ended with reason code 2051&lt;br /&gt;Sample AMQSPUT0 end&lt;p&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QA.B&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QA.B&lt;br /&gt;This is the time to test QA.B&lt;br /&gt;MQPUT ended with reason code 2051&lt;br /&gt;Sample AMQSPUT0 end&lt;p&gt;&lt;br /&gt;The thing here is&lt;br /&gt;We have an alias queue per local queue. QA.A is alias for QL.A and QA.B is the alias for QL.B.&lt;br /&gt;ALTER QA(QA.A) PUT(DISABLED)&lt;br /&gt;This disabled PUT on QA.A&lt;br /&gt;Alias has muted PUT.&lt;p&gt;ALTER QL(QL.B) PUT(DISABLED)&lt;br /&gt;This muted the PUT on local queue itself.&lt;p&gt;&lt;br /&gt;Working with queues&lt;br /&gt;__ 1. Put some messages on your queues QL.A and QL.B.&lt;p&gt;On QL.B, put is disabled above. So, reset it to enable&lt;br /&gt;ALTER QL(QL.B) PUT (ENABLE)&lt;br /&gt;     1 : ALTER QL(QL.B) PUT (ENABLE)&lt;br /&gt;AMQ8405: Syntax error detected at or near end of command segment below:-&lt;br /&gt;ALTER QL(QL.B) PUT (E&lt;p&gt;AMQ8427: Valid syntax for the MQSC command:&lt;p&gt;  ALTER QLOCAL(q_name)                                                        &lt;br /&gt;    [ FORCE ]                               [ BOQNAME(string) ]                &lt;br /&gt;    [ BOTHRESH(integer) ]                   [ CLUSNL(namelist_name) ]          &lt;br /&gt;    [ CLUSTER(cluster_name) ]               [ DEFBIND( NOTFIXED | OPEN ) ]     &lt;br /&gt;    [ DEFPRTY(integer) ]                    [ DEFPSIST( YES | NO ) ]           &lt;br /&gt;    [ DESCR(string) ]                       [ DEFSOPT( EXCL | SHARED ) ]       &lt;br /&gt;    [ DISTL( YES | NO ) ]                   [ GET( ENABLED | DISABLED ) ]      &lt;br /&gt;    [ INITQ(string) ]                       [ MAXDEPTH(integer) ]              &lt;br /&gt;    [ MAXMSGL(integer) ]                    [ MSGDLVSQ( PRIORITY | FIFO ) ]    &lt;br /&gt;    [ HARDENBO | NOHARDENBO ]               [ SHARE | NOSHARE ]                &lt;br /&gt;    [ TRIGGER | NOTRIGGER ]                 [ PROCESS(string) ]                &lt;br /&gt;    [ PUT( ENABLED | DISABLED ) ]           [ QDEPTHHI(integer) ]              &lt;br /&gt;    [ QDEPTHLO(integer) ]                   [ QDPHIEV( ENABLED | DISABLED ) ]  &lt;br /&gt;    [ QDPLOEV( ENABLED | DISABLED ) ]       [ QDPMAXEV( ENABLED | DISABLED ) ] &lt;br /&gt;    [ QSVCIEV( NONE | HIGH | OK ) ]         [ QSVCINT(integer) ]               &lt;br /&gt;    [ RETINTVL(integer) ]                   [ SCOPE( QMGR | CELL ) ]           &lt;br /&gt;    [ TRIGDATA(string) ]                    [ TRIGDPTH(integer) ]              &lt;br /&gt;    [ TRIGMPRI(integer) ]                                                      &lt;br /&gt;    [ TRIGTYPE( FIRST | EVERY | DEPTH | NONE ) ]                               &lt;br /&gt;    [ USAGE( NORMAL | XMITQ ) ]             [ NPMCLASS( NORMAL | HIGH ) ]      &lt;br /&gt;    [ STATQ( QMGR | ON | OFF ) ]            [ ACCTQ( QMGR | ON | OFF ) ]       &lt;br /&gt;    [ MONQ( QMGR | OFF | LOW | MEDIUM | HIGH ) ]                               &lt;br /&gt;    [ CLWLRANK(integer) ]                   [ CLWLPRTY(integer) ]              &lt;br /&gt;    [ CLWLUSEQ( LOCAL | ANY | QMGR ) ]  &lt;br /&gt;ALTER QL(QL.B) PUT (ENABLED)&lt;br /&gt;     2 : ALTER QL(QL.B) PUT (ENABLED)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;END&lt;p&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QL.B&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QL.B&lt;br /&gt;blah blah QL.B blah blah&lt;br /&gt;its working now enable and enabled...awesome difference&lt;p&gt;&lt;p&gt;&lt;br /&gt;__ 2. Show the CURDEPTH of all the queues you have created.&lt;br /&gt;                     • DISPLAY Q(Q*) CURDEPTH&lt;br /&gt;DISPLAY Q(Q*) CURDEPTH&lt;br /&gt;     1 : DISPLAY Q(Q*) CURDEPTH&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QA.A)                             TYPE(QALIAS)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QA.B)                             TYPE(QALIAS)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   CURDEPTH(6)                          &lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.B)                             TYPE(QLOCAL)&lt;br /&gt;   CURDEPTH(2)                          &lt;p&gt;__ 3. Define an new local queue QL.X with the attributes of QA.A&lt;br /&gt;                     • DEFINE QLOCAL(QL.X) LIKE(QA.A)&lt;br /&gt;DEFINE QLOCAL(QL.X) LIKE (QA.A)&lt;br /&gt;     2 : DEFINE QLOCAL(QL.X) LIKE (QA.A)&lt;br /&gt;AMQ8138: The WebSphere MQ queue has an incorrect type.&lt;p&gt;That says, one cannot create a queue like an alias&lt;p&gt;&lt;br /&gt;__ 4. Error? Now use the attributes of QL.A.&lt;br /&gt;                     • DEFINE QLOCAL(QL.X) LIKE(QL.A)&lt;p&gt;DEFINE QL(QL.X) LIKE (QL.A)&lt;br /&gt;     3 : DEFINE QL(QL.X) LIKE (QL.A)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;p&gt;&lt;br /&gt;__ 5. Put some messages on QL.X.&lt;br /&gt;                     • amqsput QL.X&lt;br /&gt;[mqm@localhost ~]$ /opt/mqm/samp/bin/amqsput QL.X&lt;br /&gt;Sample AMQSPUT0 start&lt;br /&gt;target queue is QL.X&lt;br /&gt;Here is my new queue buddy QL.X&lt;br /&gt;Let me test this guy out&lt;p&gt;&lt;br /&gt;__ 6. Change the description of QL.A.&lt;br /&gt;                     • ALTER QL(QL.A) DESCR(&amp;#39;QL.A Text new&amp;#39;)&lt;br /&gt;ALTER QL(QL.A) DESCR(&amp;#39;QL.A Text new&amp;#39;)&lt;br /&gt;     4 : ALTER QL(QL.A) DESCR(&amp;#39;QL.A Text new&amp;#39;)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;p&gt;&lt;br /&gt;__ 7. Display the DESCR attribute of all your queues.&lt;br /&gt;                     • DISPLAY Q(Q*) DESCR&lt;p&gt;&lt;br /&gt;__ 8. Any change?&lt;br /&gt;QL.X has QL.A&amp;#39;s description&lt;br /&gt;QL.A has new description&lt;p&gt;__ 9. Clear queue QL.A&lt;br /&gt;                     • CLEAR QL(QL.A)&lt;br /&gt;CLEAR QL(QL.A)&lt;br /&gt;     6 : CLEAR QL(QL.A)&lt;br /&gt;DISPLAY Q(QL.A) CURDEPTH&lt;br /&gt;    7 : DISPLAY Q(QL.A) CURDEPTH&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   CURDEPTH(0) &lt;p&gt;AMQ8022: WebSphere MQ queue cleared.&lt;br /&gt;__ 10. Clear queue QA.A&lt;br /&gt;                     • CLEAR QA(QA.A)&lt;p&gt;CLEAR QA(QA.A)&lt;br /&gt;    11 : CLEAR QA(QA.A)&lt;br /&gt;AMQ8405: Syntax error detected at or near end of command segment below:-&lt;br /&gt;CLEAR QA&lt;p&gt;AMQ8426: Valid MQSC commands are:&lt;p&gt;    CLEAR QLOCAL&lt;p&gt;&lt;p&gt;__ 11. Successfully? Give the reason why.&lt;p&gt;Means that you cannot clear an alias queue. Makes sense, alias queue is just a pointer to a queue, it does not hold any info in it.&lt;p&gt;__ 12. Delete QL.X&lt;br /&gt;                     • DELETE QL(QL.X)&lt;p&gt;DELETE QL(QL.X)&lt;br /&gt;    12 : DELETE QL(QL.X)&lt;br /&gt;AMQ8143: WebSphere MQ queue not empty.&lt;p&gt;&lt;br /&gt;Lets see the depth of the QL.X&lt;p&gt;DISPLAY Q(QL.X) CURDEPTH&lt;br /&gt;    13 : DISPLAY Q(QL.X) CURDEPTH&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.X)                             TYPE(QLOCAL)&lt;br /&gt;   CURDEPTH(2) &lt;p&gt;So one cannot delete an non empty queue&lt;p&gt;__ 13. Successfully deleted? If not, modify the command&lt;br /&gt;                     • DELETE QL(QL.X) purge&lt;p&gt;DELETE QL(QL.X) purge&lt;br /&gt;    14 : DELETE QL(QL.X) purge&lt;br /&gt;AMQ8007: WebSphere MQ queue deleted.&lt;p&gt;&lt;p&gt;My MQ Notes&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-799665507156625235?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/799665507156625235/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=799665507156625235' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/799665507156625235'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/799665507156625235'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/08/mq-notes-continued.html' title='MQ Notes ... continued'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3288908135255177154</id><published>2010-08-19T06:12:00.003+05:30</published><updated>2010-08-31T02:43:32.465+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='WMQ'/><category scheme='http://www.blogger.com/atom/ns#' term='Logs'/><title type='text'>My MQ Notes</title><content type='html'>Installed MQM on RHEL 5.&lt;br /&gt;first created uid:mqm, gid:mqm&lt;br /&gt;Downloaded WMQ linux gz file.&lt;br /&gt;Copied to /tmp/mqinst&lt;br /&gt;tar -zxvf gz file&lt;br /&gt;&lt;br /&gt;su &lt;br /&gt;&lt;br /&gt;./mqlicense.sh -accept&lt;br /&gt;&lt;br /&gt;Then kick start to install&lt;br /&gt;&lt;br /&gt;rpm -ivh MQSeriesServer, runtimes yata yata yata&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;1. create a default q manager&lt;br /&gt;call it MQ.QM1&lt;br /&gt;[mqm@localhost ~]$ crtmqm MQ.QM1&lt;br /&gt;There are 90 days left in the trial period for this copy of WebSphere MQ.&lt;br /&gt;WebSphere MQ queue manager created.&lt;br /&gt;Creating or replacing default objects for MQ.QM1.&lt;br /&gt;Default objects statistics : 40 created. 0 replaced. 0 failed.&lt;br /&gt;Completing setup.&lt;br /&gt;Setup completed.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;2. Start Q Manager&lt;br /&gt;&lt;br /&gt;[mqm@localhost ~]$ strmqm MQ.QM1&lt;br /&gt;There are 90 days left in the trial period for this copy of WebSphere MQ.&lt;br /&gt;WebSphere MQ queue manager &amp;#39;MQ.QM1&amp;#39; starting.&lt;br /&gt;5 log records accessed on queue manager &amp;#39;MQ.QM1&amp;#39; during the log replay phase.&lt;br /&gt;Log replay for queue manager &amp;#39;MQ.QM1&amp;#39; complete.&lt;br /&gt;Transaction manager state recovered for queue manager &amp;#39;MQ.QM1&amp;#39;.&lt;br /&gt;WebSphere MQ queue manager &amp;#39;MQ.QM1&amp;#39; started.&lt;br /&gt;&lt;br /&gt;Note : &lt;br /&gt;[mqm@localhost ~]$ ps -ef | grep mqm&lt;br /&gt;root      6040  6024  0 12:12 pts/1    00:00:00 su - mqm&lt;br /&gt;mqm       6043  6040  0 12:12 pts/1    00:00:00 -bash&lt;br /&gt;mqm       6418     1  0 12:22 ?        00:00:00 amqzxma0 -m MQ.QM1&lt;br /&gt;mqm       6422  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzfuma -m MQ.QM1&lt;br /&gt;mqm       6424  6418  0 12:22 ?        00:00:00 amqzmuc0 -m MQ.QM1&lt;br /&gt;mqm       6429  6418  0 12:22 ?        00:00:00 amqzmur0 -m MQ.QM1&lt;br /&gt;mqm       6432  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqrrmfa -m MQ.QM1 -t2332800 -s2592000 -p2592000 -g5184000 -c3600&lt;br /&gt;mqm       6434  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzdmaa -m MQ.QM1&lt;br /&gt;mqm       6436  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzmgr0 -m MQ.QM1&lt;br /&gt;mqm       6449  6418  0 12:22 ?        00:00:00 amqzlaa0 -mMQ.QM1 -fip0&lt;br /&gt;mqm       6450  6436  0 12:22 ?        00:00:00 /opt/mqm/bin/runmqchi -m MQ.QM1 -r&lt;br /&gt;mqm       6452  6436  0 12:22 ?        00:00:00 /opt/mqm/bin/amqpcsea MQ.QM1&lt;br /&gt;mqm       6482  6043  0 12:22 pts/1    00:00:00 ps -ef&lt;br /&gt;mqm       6483  6043  0 12:22 pts/1    00:00:00 grep mqm&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;What are these amqzlaa0 -mMQ.QM1 -fip0&lt;br /&gt;runmqxhi&lt;br /&gt;amqzmqr0&lt;br /&gt;amqzfuma&lt;br /&gt;------------------------&lt;br /&gt;3. Once QM starts, create local queues using script.&lt;br /&gt;         Use the control commands interactively&lt;br /&gt; Use the control command runmqsc to perform the following tasks. Enter all the&lt;br /&gt;       WebSphere MQ commands interactively and display the results at the terminal.&lt;br /&gt;&lt;br /&gt;[mqm@localhost errors]$ runmqsc&lt;br /&gt;5724-H72 (C) Copyright IBM Corp. 1994, 2005.  ALL RIGHTS RESERVED.&lt;br /&gt;AMQ8146: WebSphere MQ queue manager not available.&lt;br /&gt;&lt;br /&gt;No MQSC commands read.&lt;br /&gt;No commands have a syntax error.&lt;br /&gt;All valid MQSC commands were processed.&lt;br /&gt;[mqm@localhost errors]$ &lt;br /&gt;&lt;br /&gt;As MQ.QM1 is not set as the default queue manager, runmqsc is returning back stating, hey, WebSphere MQ queue manager not available.&lt;br /&gt;&lt;br /&gt;To further dig into this, verified logs at -&lt;br /&gt;i./var/mqm/errors/AMQERR01.LOG&lt;br /&gt;ii. /var/mqm/qmgrs/MQ!QM1/errors/AMQERR01.LOG&lt;br /&gt;In the above i. being the mq error log and ii. being the queue manager error log.&lt;br /&gt;&lt;br /&gt;There is this MQ configuration file called mqs.ini, default location is /var/mqm&lt;br /&gt;My mqs.ini is like this -&lt;br /&gt;-----------------------------&lt;br /&gt;AllQueueManagers:&lt;br /&gt;   #********************************************************************#&lt;br /&gt;   #* The path to the qmgrs directory, below which queue manager data  *#&lt;br /&gt;   #* is stored                                                        *#&lt;br /&gt;   #********************************************************************#&lt;br /&gt;   DefaultPrefix=/var/mqm&lt;br /&gt;&lt;br /&gt;ClientExitPath:&lt;br /&gt;   ExitsDefaultPath=/var/mqm/exits&lt;br /&gt;   ExitsDefaultPath64=/var/mqm/exits64&lt;br /&gt;&lt;br /&gt;LogDefaults:&lt;br /&gt;   LogPrimaryFiles=3&lt;br /&gt;   LogSecondaryFiles=2&lt;br /&gt;   LogFilePages=1024&lt;br /&gt;   LogType=CIRCULAR&lt;br /&gt;   LogBufferPages=0&lt;br /&gt;   LogDefaultPath=/var/mqm/log&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;QueueManager:&lt;br /&gt;   Name=MQ.QM1&lt;br /&gt;   Prefix=/var/mqm&lt;br /&gt;   Directory=MQ!QM1&lt;br /&gt;-----------------------------&lt;br /&gt;&lt;br /&gt;In the content, there is no listing of default queue manager....&lt;br /&gt;looked in IBM MQ InfoCenter and a sample file looked like this - &lt;br /&gt;-----------------------------&lt;br /&gt;AllQueueManagers:&lt;br /&gt;#***********************************************************************#&lt;br /&gt;#* The path to the qmgrs directory, below which queue manager data     *#&lt;br /&gt;#* is stored                                                           *#&lt;br /&gt;#***********************************************************************#&lt;br /&gt;DefaultPrefix=/var/mqm&lt;br /&gt;&lt;br /&gt;LogDefaults:&lt;br /&gt;   LogPrimaryFiles=3&lt;br /&gt;   LogSecondaryFiles=2&lt;br /&gt;   LogFilePages=1024&lt;br /&gt;   LogType=CIRCULAR&lt;br /&gt;   LogBufferPages=0&lt;br /&gt;   LogDefaultPath=/var/mqm/log&lt;br /&gt;&lt;br /&gt;QueueManager:&lt;br /&gt;   Name=saturn.queue.manager&lt;br /&gt;   Prefix=/var/mqm&lt;br /&gt;   Directory=saturn!queue!manager&lt;br /&gt;&lt;br /&gt;QueueManager:&lt;br /&gt;   Name=pluto.queue.manager&lt;br /&gt;   Prefix=/var/mqm&lt;br /&gt;   Directory=pluto!queue!manager&lt;br /&gt;&lt;br /&gt;DefaultQueueManager:&lt;br /&gt;   Name=saturn.queue.manager&lt;br /&gt;&lt;br /&gt;ApiExitTemplate:&lt;br /&gt;   Name=OurPayrollQueueAuditor&lt;br /&gt;   Sequence=2&lt;br /&gt;   Function=EntryPoint&lt;br /&gt;   Module=/usr/ABC/auditor&lt;br /&gt;   Data=123&lt;br /&gt;&lt;br /&gt;ApiExitCommon:&lt;br /&gt;   Name=MQPoliceman&lt;br /&gt;   Sequence=1&lt;br /&gt;   Function=EntryPoint&lt;br /&gt;   Module=/usr/MQPolice/tmqp&lt;br /&gt;   Data=CheckEverything&lt;br /&gt;-----------------------------&lt;br /&gt;&lt;br /&gt;So let me edit my file with appropriate default queue settings -&lt;br /&gt;Just added these two lines at the end of the file -&lt;br /&gt;DefaultQueueManager:&lt;br /&gt;   Name=MQ.QM1&lt;br /&gt;&lt;br /&gt;Now the changes comes into action only after restarting the queue manager.&lt;br /&gt;How to restart the queue manager?&lt;br /&gt;Search in MQ info center - says, ps -ef | grep QNAME lists all the available processes, pick the queue manager process and kill -9.&lt;br /&gt;Wow...&lt;br /&gt;Let me see what I got here -&lt;br /&gt;[mqm@localhost mqm]$ ps -ef | grep mqm | grep -i qm1&lt;br /&gt;mqm       6418     1  0 12:22 ?        00:00:00 amqzxma0 -m MQ.QM1&lt;br /&gt;mqm       6422  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzfuma -m MQ.QM1&lt;br /&gt;mqm       6424  6418  0 12:22 ?        00:00:00 amqzmuc0 -m MQ.QM1&lt;br /&gt;mqm       6429  6418  0 12:22 ?        00:00:00 amqzmur0 -m MQ.QM1&lt;br /&gt;mqm       6432  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqrrmfa -m MQ.QM1 -t2332800 -s2592000 -p2592000 -g5184000 -c3600&lt;br /&gt;mqm       6434  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzdmaa -m MQ.QM1&lt;br /&gt;mqm       6436  6418  0 12:22 ?        00:00:00 /opt/mqm/bin/amqzmgr0 -m MQ.QM1&lt;br /&gt;mqm       6449  6418  0 12:22 ?        00:00:00 amqzlaa0 -mMQ.QM1 -fip0&lt;br /&gt;mqm       6450  6436  0 12:22 ?        00:00:00 /opt/mqm/bin/runmqchi -m MQ.QM1 -r&lt;br /&gt;mqm       6452  6436  0 12:22 ?        00:00:00 /opt/mqm/bin/amqpcsea MQ.QM1&lt;br /&gt;mqm      13218  7791  0 13:34 pts/1    00:00:00 grep -i qm1&lt;br /&gt;&lt;br /&gt;pid 6418 is the parent pid for all these process. &lt;br /&gt;kill -9 6418 :)&lt;br /&gt;&lt;br /&gt;Yeah, &lt;br /&gt;[mqm@localhost mqm]$ ps -ef | grep mqm | grep -i qm1&lt;br /&gt;mqm      13397  7791  0 13:39 pts/1    00:00:00 grep -i qm1&lt;br /&gt;&lt;br /&gt;So, good to go now, start queue manager now&lt;br /&gt;&lt;br /&gt;[mqm@localhost mqm]$ strmqm&lt;br /&gt;There are 90 days left in the trial period for this copy of WebSphere MQ.&lt;br /&gt;WebSphere MQ queue manager &amp;#39;MQ.QM1&amp;#39; starting.&lt;br /&gt;17 log records accessed on queue manager &amp;#39;MQ.QM1&amp;#39; during the log replay phase.&lt;br /&gt;Log replay for queue manager &amp;#39;MQ.QM1&amp;#39; complete.&lt;br /&gt;Transaction manager state recovered for queue manager &amp;#39;MQ.QM1&amp;#39;.&lt;br /&gt;WebSphere MQ queue manager &amp;#39;MQ.QM1&amp;#39; started.&lt;br /&gt;&lt;br /&gt;I have not mentioned the FQQMN (Fully Qualified Queue Manager Name), it picked the MQ.QM1 as default and start the manager.&lt;br /&gt;Now, lets check runmqsc &lt;br /&gt;:):)&lt;br /&gt;[mqm@localhost mqm]$ runmqsc&lt;br /&gt;5724-H72 (C) Copyright IBM Corp. 1994, 2005.  ALL RIGHTS RESERVED.&lt;br /&gt;Starting MQSC for queue manager MQ.QM1.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Its waiting for my interactive command.&lt;br /&gt;:):)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;   __ a. Display all the attributes of the queue manager.&lt;br /&gt;DISPLAY QMGMR&lt;br /&gt;     1 : DISPLAY QMGMR&lt;br /&gt;AMQ8405: Syntax error detected at or near end of command segment below:-&lt;br /&gt;DISPLAY QMG&lt;br /&gt;&lt;br /&gt;AMQ8427: Valid syntax for the MQSC command:&lt;br /&gt;&lt;br /&gt;  DISPLAY QMODEL(generic_q_name)&lt;br /&gt;                          &lt;br /&gt;     [ WHERE( filter_keyword operator filter_value ) ]&lt;br /&gt;                          &lt;br /&gt;     [ ALL      ] [ ALTDATE  ] [ ALTTIME  ] [ BOTHRESH ] [ BOQNAME  ]&lt;br /&gt;     [ CRDATE   ] [ CRTIME   ] [ DEFPRTY  ] [ DEFPSIST ] [ DEFSOPT  ]&lt;br /&gt;     [ DEFTYPE  ] [ DESCR    ] [ DISTL    ] [ GET      ] [ HARDENBO ]&lt;br /&gt;     [ INITQ    ] [ MAXDEPTH ] [ MAXMSGL  ] [ MSGDLVSQ ] [ PROCESS  ]&lt;br /&gt;     [ PUT      ] [ QDEPTHHI ] [ QDEPTHLO ] [ QDPHIEV  ] [ QDPLOEV  ]&lt;br /&gt;     [ QDPMAXEV ] [ QSVCIEV  ] [ QSVCINT  ] [ QTYPE    ] [ RETINTVL ]&lt;br /&gt;     [ SHARE    ] [ TRIGDATA ] [ TRIGDPTH ] [ TRIGGER  ] [ TRIGMPRI ]&lt;br /&gt;     [ TRIGTYPE ] [ TYPE     ] [ USAGE    ] [ NPMCLASS ] [ MONQ     ]&lt;br /&gt;     [ ACCTQ    ] [ STATQ    ]&lt;br /&gt;DISPLAY Q&lt;br /&gt;     2 : DISPLAY Q&lt;br /&gt;AMQ8405: Syntax error detected at or near end of command segment below:-&lt;br /&gt;DISPLAY Q&lt;br /&gt;&lt;br /&gt;AMQ8427: Valid syntax for the MQSC command:&lt;br /&gt;&lt;br /&gt;  DISPLAY QUEUE(generic_q_name)&lt;br /&gt;                          &lt;br /&gt;     [ WHERE( filter_keyword operator filter_value ) ]&lt;br /&gt;                          &lt;br /&gt;     [ CLUSTER(generic_cluster_name) ]      [ CLUSNL(generic_namelist_name) ]&lt;br /&gt;     [ TYPE( QALIAS | QCLUSTER | QLOCAL | QMODEL | QREMOTE ) ]&lt;br /&gt;     [ ALL      ] [ ALTDATE  ] [ ALTTIME  ] [ BOTHRESH ]&lt;br /&gt;     [ BOQNAME  ] [ CLUSDATE ] [ CLUSINFO ] [ CLUSNL   ] [ CLUSQMGR ]&lt;br /&gt;     [ CLUSQT   ] [ CLUSTER  ] [ CLUSTIME ] [ CRDATE   ] [ CRTIME   ]&lt;br /&gt;     [ CURDEPTH ] [ DEFBIND  ] [ DEFPRTY  ] [ DEFPSIST ] [ DEFSOPT  ]&lt;br /&gt;     [ DEFTYPE  ] [ DESCR    ] [ DISTL    ] [ GET      ] [ HARDENBO ]&lt;br /&gt;     [ INITQ    ] [ IPPROCS  ] [ MAXDEPTH ] [ MAXMSGL  ] [ MSGDLVSQ ]&lt;br /&gt;     [ OPPROCS  ] [ PROCESS  ] [ PUT      ] [ QDEPTHHI ] [ QDEPTHLO ]&lt;br /&gt;     [ QDPHIEV  ] [ QDPLOEV  ] [ QDPMAXEV ] [ QMID     ] [ QSVCIEV  ]&lt;br /&gt;     [ QSVCINT  ] [ QTYPE    ] [ RETINTVL ] [ RNAME    ] [ RQMNAME  ]&lt;br /&gt;     [ SCOPE    ] [ SHARE    ] [ TARGQ    ] [ TRIGDATA ] [ TRIGDPTH ]&lt;br /&gt;     [ TRIGGER  ] [ TRIGMPRI ] [ TRIGTYPE ] [ TYPE     ] [ USAGE    ]&lt;br /&gt;     [ XMITQ    ] [ MONQ     ] [ CLWLRANK ] [ CLWLPRTY ] [ CLWLUSEQ ]&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;   __ b. List the names of all the queues whose names begin with the characters&lt;br /&gt;         &amp;quot;SYSTEM&amp;quot;.&lt;br /&gt;DISPLAY Q(SYSTEM*)&lt;br /&gt;     3 : DISPLAY Q(SYSTEM*)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.ACCOUNTING.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.ACTIVITY.QUEUE)      TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.CHANNEL.EVENT)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.COMMAND.QUEUE)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.LOGGER.EVENT)        TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.PERFM.EVENT)         TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.QMGR.EVENT)          TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.STATISTICS.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.ADMIN.TRACE.ROUTE.QUEUE)   TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.AUTH.DATA.QUEUE)           TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CHANNEL.INITQ)             TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CHANNEL.SYNCQ)             TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CICS.INITIATION.QUEUE)     TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.COMMAND.QUEUE)     TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.REPOSITORY.QUEUE)&lt;br /&gt;   TYPE(QLOCAL)                         &lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.CLUSTER.TRANSMIT.QUEUE)    TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEAD.LETTER.QUEUE)         TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.ALIAS.QUEUE)       TYPE(QALIAS)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.INITIATION.QUEUE)&lt;br /&gt;   TYPE(QLOCAL)                         &lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.LOCAL.QUEUE)       TYPE(QLOCAL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.MODEL.QUEUE)       TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.DEFAULT.REMOTE.QUEUE)      TYPE(QREMOTE)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.MQEXPLORER.REPLY.MODEL)    TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.MQSC.REPLY.QUEUE)          TYPE(QMODEL)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(SYSTEM.PENDING.DATA.QUEUE)        TYPE(QLOCAL)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;   __ c. Create a local queue QL.A. Its definitions should include a text description.&lt;br /&gt;&lt;br /&gt;DEFINE QL(QL.A)&lt;br /&gt;     4 : DEFINE QL(QL.A)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;I forgot to add description. What to do?&lt;br /&gt;ALTER QL(QL.A) DESCR (&amp;#39;QL.A QUEUE A BLAH&amp;#39;)          &lt;br /&gt;     6 : ALTER QL(QL.A) DESCR (&amp;#39;QL.A QUEUE A BLAH&amp;#39;)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;&lt;br /&gt;   __ d. Display all the attributes of the queue.&lt;br /&gt;&lt;br /&gt;DISPLAY QL(QL.A)&lt;br /&gt;     9 : DISPLAY QL(QL.A)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-18)&lt;br /&gt;   ALTTIME(13.52.49)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.05)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR(QL.A QUEUE A BLAH)                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(5000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                        &lt;br /&gt;&lt;br /&gt;   __ e. Change the maximum number of messages allowed on the queue to 1000.&lt;br /&gt;&lt;br /&gt;We need to change the maximum number of messages allowed to 1000.&lt;br /&gt;MAXIMUM NUMBER OF MESSAGES is nothing but maxdepth&lt;br /&gt;&lt;br /&gt;ALTER QL(QL.A) MAXDEPTH(1000)&lt;br /&gt;    10 : ALTER QL(QL.A) MAXDEPTH(1000)&lt;br /&gt;AMQ8008: WebSphere MQ queue changed.&lt;br /&gt;&lt;br /&gt;In the above maxdepth is MAXDEPTH(5000)&lt;br /&gt;&lt;br /&gt;   __ f. Again display the queue attributes. Was the modification successful and is the&lt;br /&gt;         queue description unchanged?&lt;br /&gt;                      • DISPLAY QL(QL.A)&lt;br /&gt;DISPLAY QL(QL.A)&lt;br /&gt;     1 : DISPLAY QL(QL.A)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.A)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-18)&lt;br /&gt;   ALTTIME(13.55.59)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.05)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR(QL.A QUEUE A BLAH)                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(1000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                        &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;   __ g. Define a second local queue QL.B with a text description.&lt;br /&gt;&lt;br /&gt;DEFINE QL(QL.B)&lt;br /&gt;     5 : DEFINE QL(QL.B)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;&lt;br /&gt;   __ h. Display all the attributes of the queue.&lt;br /&gt;                      • DISPLAY QL(QL.B)&lt;br /&gt;DISPLAY QL(QL.B)&lt;br /&gt;     3 : DISPLAY QL(QL.B)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.B)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-18)&lt;br /&gt;   ALTTIME(13.58.55)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.16)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR(QL.B B QUEUE BLAH)                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(5000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)                      &lt;br /&gt;&lt;br /&gt;   __ i. Change the maximum number of messages allowed on the queue to 2000 this&lt;br /&gt;         time using -DEFINE with REPLACE- instead of the -ALTER- command.&lt;br /&gt;DEFINE QL(QL.B) REPLACE MAXDEPTH(2000)&lt;br /&gt;     4 : DEFINE QL(QL.B) REPLACE MAXDEPTH(2000)&lt;br /&gt;AMQ8006: WebSphere MQ queue created.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;   __ j. Display again the queue attributes of QL.B. Was the creation of the queue&lt;br /&gt;         successful and is there a queue description?&lt;br /&gt;&lt;br /&gt;DISPLAY QL(QL.B)&lt;br /&gt;     5 : DISPLAY QL(QL.B)&lt;br /&gt;AMQ8409: Display Queue details.&lt;br /&gt;   QUEUE(QL.B)                             TYPE(QLOCAL)&lt;br /&gt;   ACCTQ(QMGR)                             ALTDATE(2010-08-18)&lt;br /&gt;   ALTTIME(14.12.18)                       BOQNAME( )&lt;br /&gt;   BOTHRESH(0)                             CLUSNL( )&lt;br /&gt;   CLUSTER( )                              CLWLPRTY(0)&lt;br /&gt;   CLWLRANK(0)                             CLWLUSEQ(QMGR)&lt;br /&gt;   CRDATE(2010-08-18)                      CRTIME(13.50.16)&lt;br /&gt;   CURDEPTH(0)                             DEFBIND(OPEN)&lt;br /&gt;   DEFPRTY(0)                              DEFPSIST(NO)&lt;br /&gt;   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)&lt;br /&gt;   DESCR( )                                DISTL(NO)&lt;br /&gt;   GET(ENABLED)                            HARDENBO&lt;br /&gt;   INITQ( )                                IPPROCS(0)&lt;br /&gt;   MAXDEPTH(2000)                          MAXMSGL(4194304)&lt;br /&gt;   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)&lt;br /&gt;   NOTRIGGER                               NPMCLASS(NORMAL)&lt;br /&gt;   OPPROCS(0)                              PROCESS( )&lt;br /&gt;   PUT(ENABLED)                            QDEPTHHI(80)&lt;br /&gt;   QDEPTHLO(20)                            QDPHIEV(DISABLED)&lt;br /&gt;   QDPLOEV(DISABLED)                       QDPMAXEV(ENABLED)&lt;br /&gt;   QSVCIEV(NONE)                           QSVCINT(999999999)&lt;br /&gt;   RETINTVL(999999999)                     SCOPE(QMGR)&lt;br /&gt;   SHARE                                   STATQ(QMGR)&lt;br /&gt;   TRIGDATA( )                             TRIGDPTH(1)&lt;br /&gt;   TRIGMPRI(0)                             TRIGTYPE(FIRST)&lt;br /&gt;   USAGE(NORMAL)&lt;br /&gt;__ 4. Exit the runmqsc mode&lt;br /&gt;&lt;br /&gt;END is the command to exit the runmqsc.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3288908135255177154?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3288908135255177154/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3288908135255177154' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3288908135255177154'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3288908135255177154'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/08/my-mq-notes.html' title='My MQ Notes'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1047818627873959318</id><published>2010-05-26T23:36:00.002+05:30</published><updated>2010-05-26T23:45:01.997+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='RAD 7.0'/><category scheme='http://www.blogger.com/atom/ns#' term='JAVA'/><title type='text'>major minor version errors</title><content type='html'>These types of errors are caused by a Java version mismatch between the  compiled proxies and your runtime.&lt;span&gt;&lt;h1&gt;&amp;quot;bad class file. class file has wrong version 50.0, should be 48.0.&amp;quot;&lt;/h1&gt;Unsupported major.minor version 50.0&lt;br /&gt;JSPG0091E: An error occurred at line: 2 in the file: /login.jsp&lt;br /&gt;  JSPG0093E: Generated servlet error from file: /login.jsp &lt;br /&gt;  &lt;p&gt;Below are a list of some of the version numbers and their corresponding Java  runtimes:&lt;br /&gt;Version 50.0 = Java 1.6.x&lt;br /&gt;Version 49.0 = Java 1.5.x&lt;br /&gt;Version  48.0 = Java 1.4.x&lt;/p&gt;&lt;p&gt;The server is expecting 48.0 version of the code, meaning, code built with 1.4.x version of jvm, but, the supplied code was built against version 50.0 meaning 1.6.x version of the jvm.&lt;/p&gt;&lt;p&gt;What one can do to solve this is, if you use RAD kind of tools to build the code, configure build path to have appropriate JRE, clean your builds and re build.&lt;/p&gt;  &lt;p&gt;&lt;br /&gt;&lt;/p&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1047818627873959318?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1047818627873959318/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1047818627873959318' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1047818627873959318'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1047818627873959318'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/05/major-minor-version-errors.html' title='major minor version errors'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8653899812649288614</id><published>2010-05-26T23:30:00.003+05:30</published><updated>2010-05-27T07:50:43.485+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='commands'/><title type='text'>uptime</title><content type='html'>&lt;b&gt;uptime&lt;/b&gt; is a &lt;a href="http://en.wikipedia.org/wiki/Measurement" title="Measurement"&gt;measure&lt;/a&gt; of the &lt;a href="http://en.wikipedia.org/wiki/System_time" title="System time"&gt;time&lt;/a&gt;  a &lt;a href="http://en.wikipedia.org/wiki/Machine" title="Machine"&gt;machine&lt;/a&gt;  has up been.&lt;br /&gt;This is pretty useful command.&lt;br /&gt;&lt;br /&gt;To know since when the system is up one can do like this at the terminal prompt&lt;br /&gt;$uptime&lt;br /&gt;11:10:27 up 9 mins, 2 users,       Load average: 0.02, 0.24, 0.18&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;h2&gt;&lt;span class="mw-headline" id="Determining_system_uptime"&gt;Determining  system uptime in windows -&lt;/span&gt;&lt;/h2&gt;1. &lt;br clear="all"&gt;&lt;div dir="ltr" class="mw-geshi" style="text-align: left;"&gt; &lt;div class="text source-text" style="font-family: monospace;"&gt; &lt;pre class="de1"&gt;C:\&amp;gt; systeminfo | find &amp;quot;Time:&amp;quot;&lt;br /&gt;System Up Time:            0 Days, 8 Hours, 7 Minutes, 19 Seconds&lt;br /&gt;&lt;/pre&gt;&lt;/div&gt; &lt;/div&gt; &lt;p&gt;&lt;i&gt;Note: Windows Vista  Business 64-bit and Windows 7 do not return a &amp;quot;System Up Time&amp;quot; but  &amp;quot;System Boot Time&amp;quot; instead.&lt;/i&gt;&lt;/p&gt;2. &lt;br /&gt;&lt;pre class="de1"&gt;C:\&amp;gt; net statistics server | find &amp;quot;since&amp;quot;&lt;br /&gt;Server Statistics for \\COMPUTERNAME&lt;br /&gt; &lt;br /&gt;Statistics since 8/31/2009 8:52:29 PM&lt;br /&gt;&lt;/pre&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8653899812649288614?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8653899812649288614/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8653899812649288614' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8653899812649288614'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8653899812649288614'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/05/uptime.html' title='uptime'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3598066885027821428</id><published>2010-04-22T22:30:00.001+05:30</published><updated>2010-04-22T22:34:09.241+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='tips'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='commands'/><title type='text'>remove directory</title><content type='html'>If you need to remove a directory, or files and or folders under a directory, in say, Solaris you do like this,&lt;br /&gt;say to remove cache under wstemp&lt;br /&gt;rm -r wstemp/*&lt;br /&gt;which removes files folders under wstemp recursively.&lt;br /&gt;rm test.txt&lt;br /&gt;deletes test.txt file&lt;br /&gt;rm -i wstemp/*&lt;br /&gt;inquires and prompts yes or no for each file&lt;br /&gt;In Linux&lt;br /&gt;rm -f - force removes a file&lt;br /&gt;rm -fr - force removes directory&lt;br /&gt;&lt;br /&gt;In DOS -&lt;br /&gt;rmdir is the command to remove a directory.&lt;br /&gt;rmdir dSample&lt;br /&gt;removes if dSample dir is empty.&lt;br /&gt;To force remove&lt;br /&gt;rmdir /S dSample&lt;br /&gt;removes dSample directory but inquires&lt;br /&gt;rmdir /S /Q dSample&lt;br /&gt;removes dSample directory and its sub directories quietly.&lt;br /&gt;&lt;br /&gt;Enjoy your day.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3598066885027821428?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3598066885027821428/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3598066885027821428' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3598066885027821428'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3598066885027821428'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/04/remove-directory.html' title='remove directory'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-167799387613974129</id><published>2010-04-12T23:29:00.002+05:30</published><updated>2010-04-12T23:37:51.871+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><title type='text'>Administrative console throws error 500 with java.lang.NullPointerExcetion</title><content type='html'>Last Sunday, one of my friend got this problem.&lt;br /&gt;&lt;br /&gt;Admin Console, when accessed, throws error 500 with java.lang.NullPointerExcetion.&lt;br /&gt;SystemOut.log has the following entries&lt;br /&gt;&lt;br /&gt;5ea42ee7 WebGroup      I SRVE0180I: [adminconsole] [/admin] [Servlet.LOG]: /secure/logon.jsp: init&lt;br /&gt;5ea42ee7 WebGroup      I SRVE0180I: [adminconsole] [/admin] [Servlet.LOG]: /secure/layouts/browser_detection.jsp: init&lt;br /&gt;5ea02ee7 WebGroup      I SRVE0180I: [adminconsole] [/admin] [Servlet.LOG]: /secure/console.jsp: init&lt;br /&gt;5ea02ee7 WebGroup      E SRVE0026E: [Servlet Error]-[]: java.lang.NullPointerException&lt;br /&gt;at org.apache.jsp._console._jspService(_console.java:172)&lt;br /&gt;&lt;br /&gt;I found this &lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg21177893"&gt;technote http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg21177893&lt;/a&gt; regarding NullPointerException, which states -&lt;br /&gt;Resolving the problem&lt;br /&gt;To resolve this issue:&lt;br /&gt;&lt;br /&gt;   1. Clean up the disk space problem.&lt;br /&gt;   2. Delete the &lt;WAS_HOME&gt;/wstemp/&lt;user_dir&gt;/preferences.xml file.&lt;br /&gt;   3. Try to login to administrative console. This should build a new preferences.xml with the correct data and should allow the user to login to administrative console. &lt;br /&gt;&lt;br /&gt;My friend followed these steps and resolved the problem.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-167799387613974129?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/167799387613974129/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=167799387613974129' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/167799387613974129'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/167799387613974129'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/04/administrative-console-throws-error-500.html' title='Administrative console throws error 500 with java.lang.NullPointerExcetion'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-9056605291100286104</id><published>2010-03-10T08:51:00.005+05:30</published><updated>2010-03-27T02:12:29.980+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><title type='text'>Installation Issues</title><content type='html'>Mr.X installed WAS like this on Win 08 server-&lt;br /&gt;&lt;br /&gt;Started to launcher.&lt;br /&gt;Selected WAS installer.&lt;br /&gt;The installer had successfully passed OS verification.&lt;br /&gt;Then selected Cell Topology. WAS 6.1 and above gives you an option to install a Cell. Meaning, installer installs Dmgr, installs an appserver, and federates that to dmgr.&lt;br /&gt;Now, with all the needed inputs, the installer started to install binaries, installed successfully dmgr, appserver and even successfully federated everything.&lt;br /&gt;&lt;br /&gt;Now, as this guy didnt configured security at the time of installation, wants to do it in the post installation.&lt;br /&gt;&lt;br /&gt;He did like this -&lt;br /&gt;After immediately installing, he ran the ivt (installation verification test).&lt;br /&gt;Then went to admin console, kicked in security setup process.&lt;br /&gt;&lt;br /&gt;WHAT IS HE MISSING?&lt;br /&gt;&lt;br /&gt;The error what he got was - after configuring security, he wanted to bounce the services, bounce dmgr, bounce node agent, bounce server.&lt;br /&gt;server was failing to start.&lt;br /&gt;dmgr cannot recognize server.&lt;br /&gt;&lt;br /&gt;What to do?ADMR0111E is one of the errors.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-9056605291100286104?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/9056605291100286104/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=9056605291100286104' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9056605291100286104'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9056605291100286104'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/03/installation-issues.html' title='Installation Issues'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6313031738271784529</id><published>2010-03-09T06:17:00.004+05:30</published><updated>2010-03-27T02:13:10.899+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><title type='text'>WASService command</title><content type='html'>Today one of colleague was trying to add a jvm to Windows Service.&lt;br /&gt;This is the syntax for the command -&lt;br /&gt;WASService.exe -add service_name&lt;br /&gt;   -serverName server_name&lt;br /&gt;   -profilePath server_profile_directory&lt;br /&gt;   [-wasHome &lt;br /&gt;app_server_root]&lt;br /&gt;   [-configRoot configuration_repository_directory]&lt;br /&gt;   [-startArgs additional_start_arguments]&lt;br /&gt;   [-stopArgs additional_stop_arguments]&lt;br /&gt;   [-userid user_id -password password]&lt;br /&gt;   [-logFile service_log_file]&lt;br /&gt;   [-logRoot server_log_directory]&lt;br /&gt;   [-restart true | false]&lt;br /&gt;   [-startType automatic | manual | disabled]&lt;br /&gt;&lt;br /&gt;This guy is fighting with some set of parameters. He is executing, command runs, he goes to the services, he finds that specific jvm in the services, but when he starts it, it simply says *started*, upon right clicking on the service, he sees only start option, remaining faded out.&lt;br /&gt;&lt;br /&gt;So, whats the problem?&lt;br /&gt;Go through the command options properly - &lt;br /&gt;&lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html"&gt;http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rins_wasservice.html&lt;/a&gt;&lt;br /&gt;He was trying to add jvm to win services like this -&lt;br /&gt;WASService.exe add blabla -logFile path/to/a/location/server.log -logRoot path/to/a/location/&lt;br /&gt;&lt;br /&gt;yata yata yata&lt;br /&gt;&lt;br /&gt;The problem is - one should pass SERVER LOG FILE as logFile and SERVER_LOG_LOCATION not to another location.&lt;br /&gt;The WASService command looks for a file named server_name .pid to determine if the server is running.&lt;br /&gt;&lt;br /&gt;So, if you want to add a jvm, by name server1 to Win services, you need to pass server1 log location.&lt;br /&gt;&lt;br /&gt;Have Fun&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6313031738271784529?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6313031738271784529/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6313031738271784529' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6313031738271784529'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6313031738271784529'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/03/wasservice-command.html' title='WASService command'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8455970594269292328</id><published>2010-02-27T10:08:00.002+05:30</published><updated>2010-02-27T10:11:04.620+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='SLES'/><category scheme='http://www.blogger.com/atom/ns#' term='vmdk'/><title type='text'>WAS ND 7 Hypervisor Edition</title><content type='html'>&lt;a href="http://1.bp.blogspot.com/_pLl9xjdgPbU/S4iiCrvA3ZI/AAAAAAAAABE/g95Unk6xpQ8/s1600-h/vmware_was_nd_7.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 237px;" src="http://1.bp.blogspot.com/_pLl9xjdgPbU/S4iiCrvA3ZI/AAAAAAAAABE/g95Unk6xpQ8/s400/vmware_was_nd_7.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5442778316660596114" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://1.bp.blogspot.com/_pLl9xjdgPbU/S4iiJBmKGcI/AAAAAAAAABM/HMLWTs8Txg4/s1600-h/was_nd_7_hypervisor.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 223px;" src="http://1.bp.blogspot.com/_pLl9xjdgPbU/S4iiJBmKGcI/AAAAAAAAABM/HMLWTs8Txg4/s400/was_nd_7_hypervisor.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5442778425608247746" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is vmware on Windows 7 64 bit.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8455970594269292328?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8455970594269292328/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8455970594269292328' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8455970594269292328'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8455970594269292328'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/02/was-nd-7-hypervisor-edition.html' title='WAS ND 7 Hypervisor Edition'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/_pLl9xjdgPbU/S4iiCrvA3ZI/AAAAAAAAABE/g95Unk6xpQ8/s72-c/vmware_was_nd_7.PNG' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1837750751647359748</id><published>2010-02-04T06:11:00.002+05:30</published><updated>2010-02-06T22:13:12.677+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='RAD 7.0'/><category scheme='http://www.blogger.com/atom/ns#' term='Vista'/><title type='text'>RAD7.0 Failure on Vista</title><content type='html'>You have installed RAD on Vista Pista.&lt;br /&gt;But, somehow, when you try to load or open up ur RAD IDE, you got the following error -&lt;br /&gt;&lt;br /&gt;eclipse.buildId=unknown&lt;br /&gt;java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows 2000 x86-32 j9vmwi3223-20061001 (JIT enabled)&lt;br /&gt;J9VM - 20060915_08260_lHdSMR&lt;br /&gt;JIT  - 20060908_1811_r8&lt;br /&gt;GC   - 20060906_AA&lt;br /&gt;BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US&lt;br /&gt;Framework arguments:  -product com.ibm.rational.rad.product.ide&lt;br /&gt;Command-line arguments:  -os win32 -ws win32 -arch x86 -product com.ibm.rational.rad.product.ide&lt;br /&gt;&lt;br /&gt;!ENTRY org.eclipse.osgi 4 0 2010-02-04 00:36:38.094&lt;br /&gt;!MESSAGE Application error&lt;br /&gt;!STACK 1&lt;br /&gt;java.lang.UnsatisfiedLinkError: &lt;span style="font-weight:bold;"&gt;swt-win32-3235&lt;/span&gt; (Not found in java.library.path)&lt;br /&gt; at java.lang.ClassLoader.loadLibraryWithPath(Unknown Source)&lt;br /&gt; at java.lang.ClassLoader.loadLibraryWithClassLoader(Unknown Source)&lt;br /&gt; at java.lang.System.loadLibrary(Unknown Source)&lt;br /&gt; at org.eclipse.swt.internal.Library.loadLibrary(Unknown Source)&lt;br /&gt; at org.eclipse.swt.internal.win32.OS.&lt;clinit&gt;(Unknown Source)&lt;br /&gt; at java.lang.J9VMInternals.initializeImpl(Native Method)&lt;br /&gt; at java.lang.J9VMInternals.initialize(Unknown Source)&lt;br /&gt; at org.eclipse.swt.widgets.Display.&lt;clinit&gt;(Unknown Source)&lt;br /&gt; at java.lang.J9VMInternals.initializeImpl(Native Method)&lt;br /&gt; at java.lang.J9VMInternals.initialize(Unknown Source)&lt;br /&gt; at org.eclipse.ui.internal.Workbench.createDisplay(Unknown Source)&lt;br /&gt; at org.eclipse.ui.PlatformUI.createDisplay(Unknown Source)&lt;br /&gt; at org.eclipse.ui.internal.ide.IDEApplication.createDisplay(Unknown Source)&lt;br /&gt; at org.eclipse.ui.internal.ide.IDEApplication.run(Unknown Source)&lt;br /&gt; at org.eclipse.core.internal.runtime.PlatformActivator$1.run(Unknown Source)&lt;br /&gt; at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)&lt;br /&gt; at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)&lt;br /&gt; at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)&lt;br /&gt; at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)&lt;br /&gt; at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&lt;br /&gt; at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)&lt;br /&gt; at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)&lt;br /&gt; at java.lang.reflect.Method.invoke(Unknown Source)&lt;br /&gt; at org.eclipse.core.launcher.Main.invokeFramework(Unknown Source)&lt;br /&gt; at org.eclipse.core.launcher.Main.basicRun(Unknown Source)&lt;br /&gt; at org.eclipse.core.launcher.Main.run(Unknown Source)&lt;br /&gt; at org.eclipse.core.launcher.Main.main(Unknown Source)&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Solution - Simple&lt;br /&gt;Goto RAD inst directory, c:\program files\IBM\SDP70\&lt;br /&gt;Right click on eclipse.exe, select run as Administrator&lt;br /&gt;&lt;br /&gt;:):)&lt;br /&gt;Enjoy&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1837750751647359748?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1837750751647359748/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1837750751647359748' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1837750751647359748'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1837750751647359748'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/02/rad70-failure-on-vista.html' title='RAD7.0 Failure on Vista'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5576163150507706196</id><published>2010-01-31T23:37:00.009+05:30</published><updated>2010-02-01T01:23:36.182+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='tar'/><category scheme='http://www.blogger.com/atom/ns#' term='gunzip'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='SLES'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='VirtualBox'/><category scheme='http://www.blogger.com/atom/ns#' term='vmdk'/><title type='text'>WebSphere Hypervisor Setup</title><content type='html'>Well, Lets see what we need to for this.&lt;br /&gt;WebSphere Hypervisor version 7. Follow this URL &lt;a href="http://www-01.ibm.com/software/webservers/appserv/hypervisor/"&gt;http://www-01.ibm.com/software/webservers/appserv/hypervisor/&lt;/a&gt;&lt;br /&gt;You need to download the following&lt;br /&gt;&lt;br /&gt;&lt;a href="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XPrCZcO8I/AAAAAAAAAAU/sBacbPlWPxE/s1600-h/tgz.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 62px;" src="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XPrCZcO8I/AAAAAAAAAAU/sBacbPlWPxE/s320/tgz.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432976863777274818" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;When searched in infocenter for hypervisor, it gave me very clear instructions. Here are those links&lt;br /&gt;&lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.virtualimages.doc/info/ae/ae/welcome_virtual.html"&gt;http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.virtualimages.doc/info/ae/ae/welcome_virtual.html&lt;/a&gt;&lt;br /&gt;&lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.virtualimages.doc/info/ae/ae/tins_virt_install_vmware_esx.html"&gt;http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.virtualimages.doc/info/ae/ae/tins_virt_install_vmware_esx.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;So, you those files from IBM. Whatelse you need?&lt;br /&gt;&lt;br /&gt;1. SLES 10, sp3.&lt;br /&gt;Goto novell.com, get SuSE Linux Enterprise Edition.&lt;br /&gt;&lt;br /&gt;2. VirtualBox -&lt;br /&gt;&lt;a href="http://www.virtualbox.org/"&gt;http://www.virtualbox.org/&lt;/a&gt;&lt;br /&gt;Download virtualbox, install it, create a suse virtual machine.&lt;br /&gt;&lt;br /&gt;3. Get cygwin.&lt;br /&gt;&lt;a href="http://www.cygwin.com/"&gt;http://www.cygwin.com/&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;4. Before you begin, you need to mount these tgz files to cygwin.&lt;br /&gt;When cygwin is installed it creates directories like this &lt;br /&gt;Directory Structure&lt;br /&gt;&lt;br /&gt;Cygwin attempts to duplicate the directory structure of a Linux System within the "c:\cygwin" folder:&lt;br /&gt;&lt;a href="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XP79DJCDI/AAAAAAAAAAc/nE1P159iz9s/s1600-h/direc_cygwin.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 130px;" src="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XP79DJCDI/AAAAAAAAAAc/nE1P159iz9s/s320/direc_cygwin.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432977154399340594" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;To not waste time on mounting another directory into cygwin, simply copy those tgz files to c:\cygwin\tmp, which are avaliable thru cygwin shell.&lt;br /&gt;&lt;br /&gt;5. Now, openup a cygwin shell.&lt;br /&gt;You have downloaded tgz file. A tgz file is a gunzip file. To uncompress it, in general, one can use gunzip command.&lt;br /&gt;gunzip filename.tgz&lt;br /&gt;is an example.&lt;br /&gt;Or, on linux platforms, tar gives a switch *z* to uncompress gz, tgz files&lt;br /&gt;Now, at the cygwin prompt -&lt;br /&gt;cd /tmp&lt;br /&gt;tar xvzf filename.tgz&lt;br /&gt;Use the above command and replace filename.tgz with all those four files.&lt;br /&gt;This uncompresses tgz file to a tar file and tar file will be uncomplressed.&lt;br /&gt;6. Above command creates files like &lt;br /&gt;vmdk, vmx files.&lt;br /&gt;7. For ease of use, I have created another directory say, c:\vmdk_files&lt;br /&gt;and copied all these files into that directory. These are the files -&lt;br /&gt;&lt;a href="http://3.bp.blogspot.com/_pLl9xjdgPbU/S2XO4GNjs_I/AAAAAAAAAAM/W39CI9_zg6Y/s1600-h/vmdk_files.PNG"&gt;&lt;img style="float:center; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 162px;" src="http://3.bp.blogspot.com/_pLl9xjdgPbU/S2XO4GNjs_I/AAAAAAAAAAM/W39CI9_zg6Y/s320/vmdk_files.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432975988627846130" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;8. So, we have vmdk files, and virtual machine. By the way, what is a vmdk file? :)&lt;br /&gt;vmdk = virtual machine disk.&lt;br /&gt;When we create a virtual machine, it will create a hdd readable by it. virtualbox by default creates vdi file. vmdk is another kind of such virtual disk file. Now, we need to add that virtual disk to the virtual machine as a secondary disk.&lt;br /&gt;&lt;br /&gt;9. This is how you do it -&lt;br /&gt;Open ur virtualbox&lt;br /&gt;point to the virtual machine&lt;br /&gt;&lt;a href="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XSk0t10zI/AAAAAAAAAAk/hggurybb-Wc/s1600-h/vm_suse.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 241px;" src="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XSk0t10zI/AAAAAAAAAAk/hggurybb-Wc/s320/vm_suse.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432980055560409906" /&gt;&lt;/a&gt;&lt;br /&gt;As pointed in the above, I have selected suse, under that, select *Storage*.&lt;br /&gt;10. &lt;br /&gt;&lt;a href="http://3.bp.blogspot.com/_pLl9xjdgPbU/S2XTemQZD7I/AAAAAAAAAAs/mx9URdBqmlE/s1600-h/vm_storage_add.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 240px;" src="http://3.bp.blogspot.com/_pLl9xjdgPbU/S2XTemQZD7I/AAAAAAAAAAs/mx9URdBqmlE/s320/vm_storage_add.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432981048111206322" /&gt;&lt;/a&gt;&lt;br /&gt;As shown above, hit on that *Add Attachment*, it gives two options, add hard disk or cd/dvd/. Select, obviously, disk.&lt;br /&gt;11. &lt;a href="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XXqWT7kpI/AAAAAAAAAA0/1Z-tKTuCdUg/s1600-h/vm_storage_added.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 239px;" src="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XXqWT7kpI/AAAAAAAAAA0/1Z-tKTuCdUg/s320/vm_storage_added.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432985648036024978" /&gt;&lt;/a&gt;&lt;br /&gt;So, we mounted these vmdsiks to our virtual machine. Lets start and see -&lt;br /&gt;12. These 4 are the mounted disks -&lt;br /&gt;&lt;a href="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XYvYp_CjI/AAAAAAAAAA8/-vNE9XvQW2E/s1600-h/suse_with_vmdks.PNG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 265px;" src="http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XYvYp_CjI/AAAAAAAAAA8/-vNE9XvQW2E/s320/suse_with_vmdks.PNG" border="0" alt=""id="BLOGGER_PHOTO_ID_5432986834076371506" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5576163150507706196?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5576163150507706196/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5576163150507706196' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5576163150507706196'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5576163150507706196'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/websphere-hypervisor-setup.html' title='WebSphere Hypervisor Setup'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_pLl9xjdgPbU/S2XPrCZcO8I/AAAAAAAAAAU/sBacbPlWPxE/s72-c/tgz.PNG' height='72' width='72'/><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4474839630366521052</id><published>2010-01-30T03:26:00.002+05:30</published><updated>2010-01-30T03:29:05.562+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='tar'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='VirtualBox'/><category scheme='http://www.blogger.com/atom/ns#' term='vmdk'/><title type='text'>tar</title><content type='html'>was.7005.nd.linux.vmware.esx.sles.os.tgz is big file, 2.33GB. When uncompress, its 12GB.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;$tar xvfz was.7005.nd.linux.vmware.esx.sles.os.tgz &lt;br /&gt;SLES10SP2-32-flat.vmdk&lt;br /&gt;tar: SLES10SP2-32-flat.vmdk: Wrote only 4607 of 10240 bytes&lt;br /&gt;SLES10SP2-32.vmdk&lt;br /&gt;tar: Exiting with failure status due to previous errors&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;What to do??&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4474839630366521052?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4474839630366521052/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4474839630366521052' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4474839630366521052'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4474839630366521052'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/tar.html' title='tar'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1401113070622397801</id><published>2010-01-29T11:20:00.002+05:30</published><updated>2010-01-29T11:25:29.320+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS 7'/><category scheme='http://www.blogger.com/atom/ns#' term='SLES'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='VirtualBox'/><category scheme='http://www.blogger.com/atom/ns#' term='64 bit'/><category scheme='http://www.blogger.com/atom/ns#' term='vmdk'/><title type='text'>vmdk disks</title><content type='html'>While I was going through Dileep Kumar's Blogpost &lt;a href="http://blogs.sun.com/dkumar/entry/websphere_hypervisor_edition_and_virtualbox"&gt;WebSphere Hypervisor Edition and VirtualBox&lt;/a&gt;, Hypervisor version attracted me a lot. So, I wanted to tryout installation the Hypervisor version 7.0.0.5 on my VirtualBox.&lt;br /&gt;&lt;br /&gt;I have lot to share on this and tomorrow I will publish that.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1401113070622397801?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1401113070622397801/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1401113070622397801' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1401113070622397801'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1401113070622397801'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/vmdk-disks.html' title='vmdk disks'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2651395016956628397</id><published>2010-01-28T01:09:00.002+05:30</published><updated>2010-01-28T01:13:52.117+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='502'/><category scheme='http://www.blogger.com/atom/ns#' term='InfoCenter'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>InfoCenter 6.1</title><content type='html'>Today, InfoCenter URL is spitting with this message&lt;br /&gt;&lt;br /&gt;Proxy Error&lt;br /&gt;&lt;br /&gt;The proxy server received an invalid response from an upstream server.&lt;br /&gt;The proxy server could not handle the request GET /infocenter/wasinfo/v6r1/advanced/searchView.jsp.&lt;br /&gt;&lt;br /&gt;Reason: Error reading from remote server&lt;br /&gt;&lt;br /&gt;IBM_HTTP_Server/6.0.2.13 Apache/2.0.47 (Unix) Server at publib.boulder.ibm.com Port 80&lt;br /&gt;&lt;br /&gt;According to IBM Technote &lt;a href="http://www-01.ibm.com/support/docview.wss?rs=177&amp;context=SSEQTJ&amp;dc=DB560&amp;dc=DB520&amp;uid=swg21316599&amp;loc=en_US&amp;cs=UTF-8&amp;lang=en&amp;rss=ct177websphere"&gt;http://www-01.ibm.com/support/docview.wss?rs=177&amp;context=SSEQTJ&amp;dc=DB560&amp;dc=DB520&amp;uid=swg21316599&amp;loc=en_US&amp;cs=UTF-8&amp;lang=en&amp;rss=ct177websphere&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Problem(Abstract)&lt;br /&gt;A Proxy Error in IBM® HTTP Server (IHS) causes a 502 error response in the browser.&lt;br /&gt; &lt;br /&gt;Symptom&lt;br /&gt;The user sees a 502 Proxy Error in the browser that says:&lt;br /&gt;&lt;br /&gt;The proxy server received an invalid response from an upstream server. The proxy server could not handle the request ....&lt;br /&gt;&lt;br /&gt;The IBM HTTP Server error log displays errors similar to:&lt;br /&gt;&lt;br /&gt;proxy: Error reading from remote server returned by ....&lt;br /&gt; &lt;br /&gt;&lt;br /&gt;Cause&lt;br /&gt;The most common cause of this problem is when the back-end web server is either not using KeepAlive, or is using too low of a value for KeepAlive.&lt;br /&gt; &lt;br /&gt;Environment&lt;br /&gt;IBM HTTP Server is configured as a proxy or reverseproxy in front of some other back-end web server.&lt;br /&gt; &lt;br /&gt;Resolving the problem&lt;br /&gt;There are two possible solutions to this problem: &lt;br /&gt;&lt;br /&gt;1) Disable KeepAlive in IBM HTTP Server, by adding these directives into your IBM HTTP Server config (httpd.conf):&lt;br /&gt;&lt;br /&gt;SetEnv force-proxy-request-1.0 1&lt;br /&gt;SetEnv proxy-nokeepalive 1&lt;br /&gt;&lt;br /&gt;OR &lt;br /&gt;&lt;br /&gt;2) Increase the KeepAlive value in the back-end web server. The KeepAlive value for the back-end web server should be at least double or triple whatever IBM HTTP Server is using for KeepAlive. The default KeepAlive for IBM HTTP Server is 15 seconds. So the back-end web server should be configured to use KeepAlive of 30 or 45 seconds.&lt;br /&gt;-------------------------------------&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Here the question is, who is going set those values on the IBM remote servers? :):)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2651395016956628397?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2651395016956628397/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2651395016956628397' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2651395016956628397'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2651395016956628397'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/infocenter-61.html' title='InfoCenter 6.1'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1987003507731423364</id><published>2010-01-27T00:52:00.002+05:30</published><updated>2010-01-27T01:03:26.692+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='MIGRATION'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Migration Notes'/><title type='text'>Migration Notes #2</title><content type='html'>The migration tools are used as part of a four-step migration process:&lt;br /&gt;1. Run WASPreUpgrade on the existing WebSphere Application Server configuration.&lt;br /&gt;2. Uninstall the existing version of WebSphere Application Server.&lt;br /&gt;3. Install the new version of WebSphere Application Server.&lt;br /&gt;4. Run WASPostUpgrade on the new version.&lt;br /&gt;In the second step, it is recommended that rather than uninstalling the existing version, it be made dormant. By keeping the existing software installed on the machine, it will be much easier to back out of the migration should unexpected problems arise.&lt;br /&gt;&lt;br /&gt;The fully automated migration includes the following steps:&lt;br /&gt;1. Migrate the existing Version 5.x deployment manager to Version 6.0 using the migration&lt;br /&gt;tools.&lt;br /&gt;2. Migrate the HTTP servers and HTTP server plug-ins on all Web tier nodes.&lt;br /&gt;3. Individually migrate the application server nodes using the migration tools.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;The WASPreUpgrade and WASPostUpgrade tools effectively move the existing configuration into WebSphere Application Server Version 6.0.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1987003507731423364?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1987003507731423364/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1987003507731423364' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1987003507731423364'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1987003507731423364'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/migration-notes-2.html' title='Migration Notes #2'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3636449725909384564</id><published>2010-01-26T23:23:00.002+05:30</published><updated>2010-01-26T23:24:11.947+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Environment'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><title type='text'>Ideal WAS Environment</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_nWTtVfnJrDY/S18sPs8S4oI/AAAAAAAAEZ8/nyYGS0NMSpU/s1600-h/ideal_env.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 340px;" src="http://2.bp.blogspot.com/_nWTtVfnJrDY/S18sPs8S4oI/AAAAAAAAEZ8/nyYGS0NMSpU/s400/ideal_env.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5431108323905823362" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3636449725909384564?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3636449725909384564/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3636449725909384564' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3636449725909384564'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3636449725909384564'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/ideal-was-environment.html' title='Ideal WAS Environment'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_nWTtVfnJrDY/S18sPs8S4oI/AAAAAAAAEZ8/nyYGS0NMSpU/s72-c/ideal_env.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6372174060184094955</id><published>2010-01-26T22:55:00.003+05:30</published><updated>2010-01-27T00:53:40.026+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='MIGRATION'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Migration Notes'/><title type='text'>Migration Notes #1</title><content type='html'>Why to migrate?&lt;br /&gt;Two important things to my understanding.&lt;br /&gt;For new features.&lt;br /&gt;For maintenance support.&lt;br /&gt;-&gt; New Features&lt;br /&gt;Again two views. Developer view and support view.&lt;br /&gt;ex., My developer called me one day, said, struts framework x.xx version is throwing error on the development. I paid a look into the log and search for the errors in the IBM. Found that, that version of JVM donot support this version of struts. So, what to do? Its the developers call to have the latest copy the JVM which can support this version of struts and apps.&lt;br /&gt;This is what is developer initiated migration.&lt;br /&gt;Admin initiated migration -&lt;br /&gt;Admin may initiate the migration too. Some of the app server errors must have been addressed in the new version of the application server and so the need for migration.&lt;br /&gt;-&gt; Support&lt;br /&gt;If the product is end of the support, there is a need to migrate to supported version.&lt;br /&gt;&lt;br /&gt;While migrating, one should need to understand inconsistencies and deprecations between the target and source environments.&lt;br /&gt;In considering the incompatibilities and deprecations, we look at these major areas:&lt;br /&gt;* J2EE differences&lt;br /&gt;* J2SE/JDK differences&lt;br /&gt;* Application Server runtime differences&lt;br /&gt;* Programming Model Extension differences&lt;br /&gt;* Third Party Library differences&lt;br /&gt;&lt;br /&gt;-&gt; J2EE Differences &lt;br /&gt;Java Code, as we all know, is forward compatible. Meaning that, code compiled in JDK 1.3.0 runs on 1.4.0, but, may throw some deprecation warnings.&lt;br /&gt;Its a good practice for the developers to address those deprecations in the code. So, when one plans to migrate from x version to y version, the development team should plan to revisit their code.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6372174060184094955?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6372174060184094955/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6372174060184094955' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6372174060184094955'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6372174060184094955'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2010/01/migration-notes-1.html' title='Migration Notes #1'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4218814290514172849</id><published>2009-12-24T02:24:00.002+05:30</published><updated>2009-12-24T02:31:38.570+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><category scheme='http://www.blogger.com/atom/ns#' term='Installation'/><title type='text'>BUILD SUCCESS</title><content type='html'>At last -&lt;br /&gt;A Fresh installation of RedHat 5.2 on my laptop. Setting Hostname as surya.site.com, the installation went smooth.&lt;br /&gt;Successfully installed WebSphere Portal Server 6.1.0 Express Edition on Linux.&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Completed install step: Finalizing Portal Server settings.&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ReadPropertyAction, msg2, Read value: 10027 for property: WC_adminhost in file: /opt/IBM/WebSphere/Portal/PortalServer/package/tempportsWP.txt&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, Reading in ASCII file /opt/IBM/WebSphere/Portal/PortalServer/exp_inst/wp.config.firststeps/firststeps/launchpad/content/Work_with.properties.&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, /REPLACE TEXT: localhost:10027 ON LINE: 26/&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.installshield.wizardx.ascii.ModifyFile, msg2, anchor_launchAdm=&lt; A href="javascript:void 0" name="test" onclick="viewPage(NO_DISKID, 'http://localhost:10027/ibm/console')"&gt;&lt;img src="./images/popup.gif" border="0"&gt;&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.Os400AsciiFileUpdate, msg2, Attempting to change file permissions to 777: /opt/IBM/WebSphere/Portal/PortalServer/exp_inst/wp.config.firststeps/firststeps/launchpad/content/Work_with.properties&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, fileName=/opt/IBM/WebSphere/Portal/AppServer/profiles/wp_profile/ConfigEngine/log/ConfigTrace.log&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, Search string not found&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.MsgLogAction, msg2, Entering MsgLogAction, action=LOG_INFO&lt;br /&gt;(Dec 22, 2009 11:25:24 AM), PortalExpress.install, com.ibm.wps.install.MsgLogAction, msg2, Sending message log: &lt;span style="font-weight:bold;"&gt;EJPIC0004I: The installation has completed successfully.&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4218814290514172849?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4218814290514172849/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4218814290514172849' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4218814290514172849'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4218814290514172849'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/build-success.html' title='BUILD SUCCESS'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6739974807833356604</id><published>2009-12-19T09:58:00.002+05:30</published><updated>2009-12-19T10:02:46.992+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='windows'/><category scheme='http://www.blogger.com/atom/ns#' term='commands'/><title type='text'>unix like commands in dos</title><content type='html'>are you looking for commands like tail, follow this url, &lt;a href="http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=9d467a69-57ff-4ae7-96ee-b18c4790cffd&amp;displayLang=en"&gt;http://www.microsoft.com/downloads/en/confirmation.aspx?familyId=9d467a69-57ff-4ae7-96ee-b18c4790cffd&amp;displayLang=en&lt;/a&gt; download rktools.exe and enjoy the following commands -&lt;br /&gt;    * Acctinfo.dll (documented in Readme.htm)&lt;br /&gt;    * Adlb.exe: Active Directory Load Balancing Tool&lt;br /&gt;    * Admx.msi: ADM File Parser&lt;br /&gt;    * Atmarp.exe: Windows ATM ARP Server Information Tool&lt;br /&gt;    * Atmlane.exe: Windows ATM LAN Emulation Client Information&lt;br /&gt;    * Autoexnt.exe: AutoExNT Service&lt;br /&gt;    * Cdburn.exe: ISO CD-ROM Burner Tool&lt;br /&gt;    * Checkrepl.vbs: Check Replication&lt;br /&gt;    * Chklnks.exe: Link Check Wizard&lt;br /&gt;    * Chknic.exe: Network Interface Card Compliance Tool for Network Load Balancing&lt;br /&gt;    * Cleanspl.exe: Spooler Cleaner&lt;br /&gt;    * Clearmem.exe: Clear Memory&lt;br /&gt;    * Clusdiag.msi: Cluster Diagnostics and Verification Tool&lt;br /&gt;    * Clusfileport.dll: Cluster Print File Port&lt;br /&gt;    * Clusterrecovery.exe: Server Cluster Recovery Utility&lt;br /&gt;    * Cmdhere.inf: Command Here&lt;br /&gt;    * Cmgetcer.dll: Connection Manager Certificate Deployment Tool&lt;br /&gt;    * Compress.exe: Compress Files&lt;br /&gt;    * Confdisk.exe: Disk Configuration Tool&lt;br /&gt;    * Consume.exe: Memory Consumers Tool&lt;br /&gt;    * Creatfil.exe: Create File&lt;br /&gt;    * Csccmd.exe: Client-Side Caching Command-Line Options&lt;br /&gt;    * Custreasonedit.exe: Custom Reason Editor (documented in Readme.htm)&lt;br /&gt;    * Delprof.exe: User Profile Deletion Utility&lt;br /&gt;    * Dh.exe: Display Heap&lt;br /&gt;    * Diskraid.exe: RAID Configuration Tool&lt;br /&gt;    * Diskuse.exe: User Disk Usage Tool&lt;br /&gt;    * Dnsdiag.exe: SMTP DNS Diagnostic Tool (documented in Readme.htm)&lt;br /&gt;    * Dumpfsmos.cmd: Dump FSMO Roles&lt;br /&gt;    * Dvdburn.exe: ISO DVD Burner Tool&lt;br /&gt;    * Empty.exe: Free Working Set Tool&lt;br /&gt;    * Eventcombmt.exe: Check Replication&lt;br /&gt;    * Fcopy.exe: File Copy Utility for Message Queuing&lt;br /&gt;    * Frsflags.vbs&lt;br /&gt;    * Getcm.exe: Connection Manager Profile Update&lt;br /&gt;    * Gpmonitor.exe: Group Policy Monitor&lt;br /&gt;    * Gpotool.exe: Group Policy Objects&lt;br /&gt;    * Hlscan.exe: Hard Link Display Tool&lt;br /&gt;    * Ifilttst.exe: IFilter Test Suite&lt;br /&gt;    * Ifmember.exe: User Membership Tool&lt;br /&gt;    * Inetesc.adm: Internet Explorer Enhanced Security Configuration&lt;br /&gt;    * Iniman.exe: Initialization Files Manipulation Tool&lt;br /&gt;    * Instcm.exe: Install Connection Manager Profile&lt;br /&gt;    * Instsrv.exe: Service Installer&lt;br /&gt;    * Intfiltr.exe: Interrupt Affinity Tool&lt;br /&gt;    * Kerbtray.exe: Kerberos Tray&lt;br /&gt;    * Kernrate.exe: Kernel Profiling Tool&lt;br /&gt;    * Klist.exe: Kerberos List&lt;br /&gt;    * Krt.exe: Certification Authority Key Recovery&lt;br /&gt;    * Lbridge.cmd: L-Bridge&lt;br /&gt;    * Linkd.exe&lt;br /&gt;    * Linkspeed.exe: Link Speed&lt;br /&gt;    * List.exe: List Text File Tool&lt;br /&gt;    * Lockoutstatus.exe: Account Lockout Status (documented in Readme.htm)&lt;br /&gt;    * Logtime.exe&lt;br /&gt;    * Lsreport.exe: Terminal Services Licensing Reporter&lt;br /&gt;    * Lsview.exe: Terminal Services License Server Viewer&lt;br /&gt;    * Mcast.exe: Multicast Packet Tool&lt;br /&gt;    * Memmonitor.exe: Memory Monitor&lt;br /&gt;    * Memtriage.exe: Resource Leak Triage Tool&lt;br /&gt;    * Mibcc.exe: SNMP MIB Compiler&lt;br /&gt;    * Moveuser.exe: Move Users&lt;br /&gt;    * Mscep.dll: Certificate Services Add-on for Simple Certificate Enrollment Protocol&lt;br /&gt;    * Nlsinfo.exe: Locale Information Tool&lt;br /&gt;    * Now.exe: STDOUT Current Date and Time&lt;br /&gt;    * Ntimer.exe: Windows Program Timer&lt;br /&gt;    * Ntrights.exe&lt;br /&gt;    * Oh.exe: Open Handles&lt;br /&gt;    * Oleview.exe: OLE/COM Object Viewer&lt;br /&gt;    * Pathman.exe: Path Manager&lt;br /&gt;    * Permcopy.exe: Share Permissions Copy&lt;br /&gt;    * Perms.exe: User File Permissions Tool&lt;br /&gt;    * Pfmon.exe: Page Fault Monitor&lt;br /&gt;    * Pkiview.msc: PKI Health Tool&lt;br /&gt;    * Pmon.exe: Process Resource Monitor&lt;br /&gt;    * Printdriverinfo.exe: Drivers Source&lt;br /&gt;    * Prnadmin.dll: Printer Administration Objects&lt;br /&gt;    * Qgrep.exe&lt;br /&gt;    * Qtcp.exe: QoS Time Stamp&lt;br /&gt;    * Queryad.vbs: Query Active Directory&lt;br /&gt;    * Rassrvmon.exe: RAS Server Monitor&lt;br /&gt;    * Rcontrolad.exe: Active Directory Remote Control Add-On&lt;br /&gt;    * Regini.exe: Registry Change by Script&lt;br /&gt;    * Regview.exe (documented in Readme.htm)&lt;br /&gt;    * Remapkey.exe: Remap Windows Keyboard Layout&lt;br /&gt;    * Robocopy.exe: Robust File Copy Utility&lt;br /&gt;    * Rpccfg.exe: RPC Configuration Tool&lt;br /&gt;    * Rpcdump.exe&lt;br /&gt;    * Rpcping.exe&lt;br /&gt;    * RPing: RPC Connectivity Verification Tool&lt;br /&gt;    * Rqc.exe: Remote Access Quarantine Client&lt;br /&gt;    * Rqs.exe: Remote Access Quarantine Agent&lt;br /&gt;    * Setprinter.exe: Spooler Configuration Tool&lt;br /&gt;    * Showacls.exe&lt;br /&gt;    * Showperf.exe: Performance Data Block Dump Utility&lt;br /&gt;    * Showpriv.exe: Show Privilege&lt;br /&gt;    * Sleep.exe: Batch File Wait&lt;br /&gt;    * Sonar.exe: FRS Status Viewer&lt;br /&gt;    * Splinfo.exe: Print Spooler Information&lt;br /&gt;    * Srvany.exe: Applications as Services Utility&lt;br /&gt;    * Srvcheck.exe: Server Share Check&lt;br /&gt;    * Srvinfo.exe: Remote Server Information&lt;br /&gt;    * Srvmgr.exe: Server Manager&lt;br /&gt;    * Ssdformat.exe: System State Data Formatter&lt;br /&gt;    * Subinacl.exe&lt;br /&gt;    * Tail.exe&lt;br /&gt;    * Tcmon.exe: Traffic Control Monitor&lt;br /&gt;    * Timeit.exe (documented in Readme.htm)&lt;br /&gt;    * Timezone.exe: Daylight Saving Time Update Utility&lt;br /&gt;    * Tsctst.exe: Terminal Server Client License Dump Tool&lt;br /&gt;    * Tsscalling.exe: Terminal Services Scalability Planning Tools&lt;br /&gt;    * Uddicatschemeeditor.exe: UDDI Services Categorization Scheme Editor&lt;br /&gt;    * Uddiconfig.exe: UDDI Services Command-line Configuration Utility&lt;br /&gt;    * Uddidataexport.exe: UDDI Data Export Wizard&lt;br /&gt;    * Usrmgr.exe: User Manager for Domains&lt;br /&gt;    * Vadump.exe: Virtual Address Dump&lt;br /&gt;    * Vfi.exe: Visual File Information&lt;br /&gt;    * Volperf.exe: Shadow Copy Performance Counters&lt;br /&gt;    * Volrest.exe: Shadow Copies for Shared Folders Restore Tool&lt;br /&gt;    * Vrfydsk.exe: Verify Disk&lt;br /&gt;    * Winexit.scr: Windows Exit Screen Saver&lt;br /&gt;    * Winhttpcertcfg.exe: WinHTTP Certificate Configuration Tool&lt;br /&gt;    * Winhttptracecfg.exe: WinHTTP Tracing Facility Configuration Tool&lt;br /&gt;    * Winpolicies.exe: Policy Spy&lt;br /&gt;    * Wins.dll: WINS Replication Network Monitor Parser&lt;br /&gt;    * Wlbs_hb.dll &amp; Wlbs_rc.dll: Windows Load Balancing Server Network Monitor Parsers&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6739974807833356604?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6739974807833356604/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6739974807833356604' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6739974807833356604'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6739974807833356604'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/unix-like-commands-in-dos.html' title='unix like commands in dos'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3265099178644566012</id><published>2009-12-14T23:45:00.004+05:30</published><updated>2009-12-14T23:49:43.397+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='TechNote'/><title type='text'>What you want to know about HTTP session persistence</title><content type='html'>Comment lines: Erik Burckart: What you want to know about HTTP session persistence -&lt;br /&gt;&lt;br /&gt;Just the FAQs&lt;br /&gt;&lt;br /&gt;In general, I get a lot of questions from various customers about HTTP session persistence. With Web 2.0 technologies taking off, more and more Web applications are being redesigned, and as they get changed, these same questions come up even more frequently. If you are involved in redesigning any Web applications for Web 2.0, here are answers to some of the questions you might soon be asking.&lt;br /&gt;&lt;br /&gt;   1. If I don’t need session persistence, can I turn it off?&lt;br /&gt;&lt;br /&gt;      Yes, you can configure session management to run with in-memory sessions, which is actually the default. You can still use HttpSessions in this mode, but if a failure occurs, the data stored in the HttpSessions will be lost.&lt;br /&gt;.............read the remaining from this technical library article&lt;br /&gt;&lt;a href="http://www.ibm.com/developerworks/websphere/techjournal/0809_col_burckart/0809_col_burckart.html"&gt;Comment lines: Erik Burckart: What you want to know about HTTP session persistence&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3265099178644566012?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3265099178644566012/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3265099178644566012' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3265099178644566012'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3265099178644566012'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/comment-lines-erik-burckart-what-you.html' title='What you want to know about HTTP session persistence'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7355564854878101296</id><published>2009-12-12T02:37:00.002+05:30</published><updated>2009-12-12T08:30:47.712+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Fedora'/><category scheme='http://www.blogger.com/atom/ns#' term='64 bit'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='Installation'/><title type='text'>selinux blocks jvm</title><content type='html'>SELinux is preventing java from loading /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so which requires text relocation.&lt;br /&gt;Detailed DescriptionThe java application attempted to load /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so which requires text relocation. This is a potential security problem. Most libraries do not need this permission. Libraries are sometimes coded incorrectly and request this permission. The SELinux Memory Protection Tests web page explains how to remove this requirement. You can configure SELinux temporarily to allow /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so to use relocation as a workaround, until the library is fixed. Please file a bug report against this package.&lt;br /&gt;Allowing Access&lt;br /&gt;If you trust /software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so to run correctly, you can change the file context to textrel_shlib_t. "chcon -t textrel_shlib_t '/software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so'" You must also change the default file context files on the system in order to preserve them even on a full relabel. "semanage fcontext -a -t textrel_shlib_t '/software/inst/JDK/jre.pak/repository/package.java.jre/java/jre/bin/libj9thr23.so'"&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7355564854878101296?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7355564854878101296/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7355564854878101296' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7355564854878101296'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7355564854878101296'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/selinux-is-preventing-java-from-loading.html' title='selinux blocks jvm'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6351403896488762608</id><published>2009-12-11T23:48:00.003+05:30</published><updated>2009-12-12T00:08:56.095+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Fedora'/><category scheme='http://www.blogger.com/atom/ns#' term='Virtualization'/><category scheme='http://www.blogger.com/atom/ns#' term='VirtualBox'/><category scheme='http://www.blogger.com/atom/ns#' term='64 bit'/><title type='text'>VT-X/AMD-V acceleration error</title><content type='html'>&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_nWTtVfnJrDY/SyKNKlRzt7I/AAAAAAAAEXY/y3jW4ysWCPo/s1600-h/fedora.JPG"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://2.bp.blogspot.com/_nWTtVfnJrDY/SyKNKlRzt7I/AAAAAAAAEXY/y3jW4ysWCPo/s400/fedora.JPG" border="0" alt=""id="BLOGGER_PHOTO_ID_5414044914997770162" /&gt;&lt;/a&gt;&lt;br /&gt;When searched in the virtualbox discussion board, found this URL&lt;br /&gt;&lt;a href="http://forums.virtualbox.org/viewtopic.php?f=7&amp;t=16951&amp;start=0"&gt;http://forums.virtualbox.org/viewtopic.php?f=7&amp;t=16951&amp;start=0&lt;/a&gt;&lt;br /&gt;What to do?&lt;br /&gt;In the BIOS, enabled AMD-Virtualization.&lt;br /&gt;error is gone&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6351403896488762608?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6351403896488762608/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6351403896488762608' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6351403896488762608'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6351403896488762608'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/vt-xamd-v-acceleration-error.html' title='VT-X/AMD-V acceleration error'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_nWTtVfnJrDY/SyKNKlRzt7I/AAAAAAAAEXY/y3jW4ysWCPo/s72-c/fedora.JPG' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2570368729586525796</id><published>2009-12-02T08:18:00.002+05:30</published><updated>2009-12-02T08:21:49.086+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='3rd party'/><title type='text'>Phurnace Deliver onfiguration Viewer for WAS</title><content type='html'>The Phurnace Deliver Configuration Viewer for WebSphere&lt;br /&gt;&lt;br /&gt;The Phurnace Deliver Configuration Viewer provides WebSphere customers with a graphical presentation of applications, configurations, servers, clusters, nodes, and domains of an application server environment. The view can be customized by scope, application, or individual component. Interrelations between the components are shown as connected lines, so at a glance, customers can determine if a configuration is associated with a particular server, cluster, or application.&lt;br /&gt;&lt;br /&gt;Screenshots: &lt;a href="http://phurnace.com/landing/configurationviewer"&gt;http://phurnace.com/landing/configurationviewer&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Recorded Demo: &lt;a href="http://www.youtube.com/phurnacesoftware "&gt;http://www.youtube.com/phurnacesoftware &lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2570368729586525796?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2570368729586525796/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2570368729586525796' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2570368729586525796'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2570368729586525796'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/12/phurnace-deliver-onfiguration-viewer.html' title='Phurnace Deliver onfiguration Viewer for WAS'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2201397144276764236</id><published>2009-11-28T00:01:00.002+05:30</published><updated>2009-11-28T00:28:14.225+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><title type='text'>hostname issues</title><content type='html'>I am still fighting with Portal Express installation. Now, I have changed my strategy and  trying to install as silent with responsefile.&lt;br /&gt;&lt;br /&gt;-silent&lt;br /&gt;-G licenseAccepted="true"&lt;br /&gt;-W setupTypePanel.selectedSetupTypeId="full"&lt;br /&gt;-W globalInstall.location="/opt/IBM/WebSphere"&lt;br /&gt;-W wasPanel.installChoice="install"&lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;#&lt;br /&gt;# EXISTING WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION&lt;br /&gt;#&lt;br /&gt;# Description: This is the value of the existing WebSphere Application Server&lt;br /&gt;# if you selected to install on an existing instance.&lt;br /&gt;#&lt;br /&gt;# Be sure to follow the convention for specifying path information on your&lt;br /&gt;# platform.  For example,&lt;br /&gt;#&lt;br /&gt;# Windows: C:\WebSphere\AppServer&lt;br /&gt;# AIX: /usr/WebSphere/AppServer&lt;br /&gt;# Linux: /opt/WebSphere/AppServer&lt;br /&gt;# Solaris: /opt/WebSphere/AppServer&lt;br /&gt;# iSeries ND:   /QIBM/ProdData/WebSphere/AppServer/V7/ND&lt;br /&gt;# iSeries Base: /QIBM/ProdData/WebSphere/AppServer/V7/Base&lt;br /&gt;################################################################################&lt;br /&gt;&lt;br /&gt;# -W wasListPanel.existingWasLocation=""&lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;# &lt;br /&gt;# OPTIONAL:&lt;br /&gt;# UNDETECTED WEBSPHERE APPLICATION SERVER INSTALLATION LOCATION (NON-ISERIES)&lt;br /&gt;#&lt;br /&gt;# Description: Sometimes the Portal install program cannot detect an existing&lt;br /&gt;# WebSphere Application Server(WAS).   You cannot know this until install runtime&lt;br /&gt;# when the silent install fails because the value of the above parameter&lt;br /&gt;# wasListPanel.existingWasLocation cannot be validated. &lt;br /&gt;#&lt;br /&gt;# When this error occurs, and you are certain that there is a valid WAS at the&lt;br /&gt;# location specified above, uncomment this parameter and enter the same value&lt;br /&gt;# specified above. &lt;br /&gt;#&lt;br /&gt;# Be sure to follow the convention for specifying path information on your&lt;br /&gt;# platform.  For example,&lt;br /&gt;#&lt;br /&gt;# Windows: C:\WebSphere\AppServer&lt;br /&gt;# AIX: /usr/WebSphere/AppServer&lt;br /&gt;# Linux: /opt/WebSphere/AppServer&lt;br /&gt;# Solaris: /opt/WebSphere/AppServer&lt;br /&gt;#&lt;br /&gt;################################################################################&lt;br /&gt;&lt;br /&gt;# -W was.undetectedWas="/opt/IBM/WebSphere/AppServer"&lt;br /&gt;&lt;br /&gt;and so on.&lt;br /&gt;Now, as the responsefile expected, I have installed AppServer. I just wanted run and check, so called startServer.sh server1, to my surprise, it failed.&lt;br /&gt;Stacktrace - &lt;br /&gt;SystemErr R com.ibm.ws.exception.ConfigurationError:javax.naming.ConfigurationException: Cannot get canonical host name for server.&lt;br /&gt;&lt;br /&gt;serverindex.xnl has hostname="null".&lt;br /&gt;This is because -&lt;br /&gt;Portal Server expected localhost.localdomain.com as hostname to localhost.localdomain.&lt;br /&gt;&lt;br /&gt;I reverted /etc/hosts back to localhost.localdomain&lt;br /&gt;and I have typed in hostname="localhost" in serverindex.xml.&lt;br /&gt;Server started successfully.&lt;br /&gt;&lt;br /&gt;Now, to kick start the PortalExpress, I am a kinda stuck, because, portal expects hostname as localhost.localdomain.com.&lt;br /&gt;Portal cannot work with hostname as  "localhost.localdomain.com", AppServer cannot run with host name *localhost.localdomain.com*. What a DEADLOCK!!!!!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2201397144276764236?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2201397144276764236/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2201397144276764236' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2201397144276764236'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2201397144276764236'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/hostname-issues.html' title='hostname issues'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4065087295060179299</id><published>2009-11-26T19:18:00.003+05:30</published><updated>2009-11-26T19:33:49.504+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><title type='text'>build failed again</title><content type='html'>Well!! n-th run, build failed again with same message as posted here - &lt;a href="http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html"&gt;http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;After this step. installation aborts.&lt;br /&gt;Checked the App Server installation log, it was a successful installation.&lt;br /&gt;Though its a failed installation, I tried to start the app server services.&lt;br /&gt;I found some *amazing* things in startServer.log -&lt;br /&gt;[11/25/09 22:31:28:005 EST] 0000000a ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.&lt;br /&gt;[11/25/09 22:31:28:157 EST] 0000000a AdminTool     A   ADMU0128I: Starting tool with the wp_profile profile&lt;br /&gt;[11/25/09 22:31:28:159 EST] 0000000a AdminTool     A   ADMU3100I: Reading configuration for server: WebSphere_Portal&lt;br /&gt;[11/25/09 22:31:32:605 EST] 0000000a WsServerLaunc E   ADMU3002E: Exception attempting to process server WebSphere_Portal&lt;br /&gt;[11/25/09 22:31:32:607 EST] 0000000a WsServerLaunc E   ADMU3007E: Exception com.ibm.ws.process.exception.InvalidExecutableException: PROC0004E: Executable: [/opt/XYZWEBSPHEREXYZ/AppServer/java/bin/java] does not appear to be a valid executable.  Process could not be created.&lt;br /&gt; at com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:159)&lt;br /&gt; at com.ibm.ws.process.ProcessFactory.create(ProcessFactory.java:69)&lt;br /&gt; at com.ibm.ws.management.launcher.ProcessLauncher.launch(ProcessLauncher.java:70)&lt;br /&gt; at com.ibm.ws.management.launcher.LaunchCommand.launchProcess(LaunchCommand.java:246)&lt;br /&gt; at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:309)&lt;br /&gt; at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)&lt;br /&gt; at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:120)&lt;br /&gt; at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&lt;br /&gt; at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)&lt;br /&gt; at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)&lt;br /&gt; at java.lang.reflect.Method.invoke(Method.java:618)&lt;br /&gt; at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)&lt;br /&gt;&lt;br /&gt;This line in the above stack trace *Executable: [/opt/&lt;span style="font-weight:bold;"&gt;XYZWEBSPHEREXYZ&lt;/span&gt;/AppServer/java/bin/java] does not appear to be a valid executable.  Process could not be created.* amazed me.&lt;br /&gt;Why startServer is trying to look for java in /opt/&lt;span style="font-weight:bold;"&gt;XYZWEBSPHEREXYZ&lt;/span&gt;/AppServer/java/bin/java? &lt;br /&gt;&lt;br /&gt;So, I have created folder structure like /opt/&lt;span style="font-weight:bold;"&gt;XYZWEBSPHEREXYZ&lt;/span&gt;/AppServer/java/bin/ and created a softlink to original appserver/java/bin/java.&lt;br /&gt;But, its looking for remaining binaries in the same location.&lt;br /&gt;So, need to create softlink for the entiar installation under /opt/&lt;span style="font-weight:bold;"&gt;XYZWEBSPHEREXYZ&lt;/span&gt;/AppServer/&lt;br /&gt;&lt;br /&gt;Lets see...&lt;br /&gt;BTW - Found a technote on this -&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21202564"&gt;http://www-01.ibm.com/support/docview.wss?uid=swg21202564&lt;/a&gt;&lt;br /&gt;The technote mentions that, because its a broken installation, you get such an error.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4065087295060179299?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4065087295060179299/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4065087295060179299' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4065087295060179299'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4065087295060179299'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/build-failed-again.html' title='build failed again'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8999217707009349697</id><published>2009-11-26T07:55:00.001+05:30</published><updated>2009-11-26T07:56:59.470+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='unzip'/><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><title type='text'>unzip</title><content type='html'>On linux (RHEL),&lt;br /&gt;to unzip a zip file,&lt;br /&gt;unzip file.zip&lt;br /&gt;To unzip to a specific folder -&lt;br /&gt;unzip file.zip -d /path-to-destination&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8999217707009349697?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8999217707009349697/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8999217707009349697' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8999217707009349697'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8999217707009349697'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/unzip.html' title='unzip'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8604447716779800648</id><published>2009-11-24T01:43:00.005+05:30</published><updated>2009-11-24T19:25:38.567+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><title type='text'>BUILD FAILED on line 3121</title><content type='html'>(Nov 23, 2009 1:56:17 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: &lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: BUILD FAILED&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/exp_inst/wp.config/config/includes/wp.config_cfg.xml:46: The following error occurred while executing this line:&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/config/actions/db_cfg_mgr.xml:277: The following error occurred while executing this line:&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:95: The following error occurred while executing this line:&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: /software/IBM/WebSphere/PortalExpress/PortalServer/base/wp.db.impl/config/includes/wp.db.impl_cfg.xml:337: ERROR: Error during the execution of the sql files.&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: &lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdErr: Total time: 38 seconds&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: &lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: &lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction$OutputWatcher, msg2, StdOut: &lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Return code = 1&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Executing command: completed&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ExternalCommandAction, msg2, Completed install step: Please wait while the WebSphere Portal Express database is initialized.&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, fileName=/software/IBM/WebSphere/PortalExpress/AppServer/profiles/wp_profile/ConfigEngine/log/ConfigTrace.log&lt;br /&gt;(Nov 23, 2009 1:56:18 PM), PortalExpress.install, com.ibm.wps.install.ScanFileAction, msg1, Found text BUILD FAILED on line 3121&lt;br /&gt;(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, err, Logged message: EJPIC0017E: Portal installation failed.  The Portal configuration step completed with errors.  Please refer to the log file /software/IBM/WebSphere/PortalExpress/PortalServer/log/wpinstalllog.txt for additional information.  The installer will now exit.&lt;br /&gt;(Nov 23, 2009 1:57:06 PM), PortalExpress.install, com.ibm.wps.install.SwingPopUp, msg2, Exiting installer.&lt;br /&gt;What to do?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Follow Up - &lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21291586"&gt;http://www-01.ibm.com/support/docview.wss?uid=swg21291586&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8604447716779800648?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8604447716779800648/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8604447716779800648' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8604447716779800648'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8604447716779800648'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/build-failed-on-line-3121.html' title='BUILD FAILED on line 3121'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6673137322891029296</id><published>2009-11-23T20:58:00.005+05:30</published><updated>2009-11-23T23:55:41.608+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><title type='text'>EJPIC0229E</title><content type='html'>My DB2Express installation on Linux is failing with the above error - EJPIC0229E: The DB2 Express installation step failed.&lt;br /&gt;&lt;br /&gt;Just above to this log entry -&lt;br /&gt;error while loading shared libraries: libstdc++.so.5: cannot pen shared object file: No such file or directory.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Follow up -&lt;br /&gt;Found this technote &lt;a href="http://www-01.ibm.com/support/docview.wss?rcss=faqtt_1Q09&amp;uid=swg21297575"&gt;http://www-01.ibm.com/support/docview.wss?rcss=faqtt_1Q09&amp;uid=swg21297575&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Follow up -&lt;br /&gt;As mentioned in the above technote, I have downloaded and installed     compat-libstdc++-33-3.2.3-61.i386.rpm. I got this from &lt;a href="http://rpm.pbone.net/index.php3/stat/4/idpl/3416184/com/compat-libstdc++-33-3.2.3-61.i386.rpm.html_"&gt;http://rpm.pbone.net/index.php3/stat/4/idpl/3416184/com/compat-libstdc++-33-3.2.3-61.i386.rpm.html_&lt;/a&gt;.&lt;br /&gt;DB2Express successfully installed.&lt;br /&gt;&lt;br /&gt;Now!! PortalExpress process get past Db2 hickup and installing WAS. Lets see what happens.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6673137322891029296?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6673137322891029296/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6673137322891029296' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6673137322891029296'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6673137322891029296'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/ejpic0229e.html' title='EJPIC0229E'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1566720593649588822</id><published>2009-11-20T20:48:00.002+05:30</published><updated>2009-11-20T20:52:40.698+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Linux'/><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='WPS'/><title type='text'>EJPIC0067E</title><content type='html'>I am installing PortalExpress v 6.1.0.0 on RHEL 5.2 on my laptop.&lt;br /&gt;&lt;br /&gt;Some tips -&lt;br /&gt;Run install.sh -console&lt;br /&gt;&lt;br /&gt;You may encounter EJPIC0067E error.&lt;br /&gt;EJPIC0067E: {0} requires a fully-qualified host name that is recognized by the DNS server. Short host names, loopback addresses, IP addresses and illegal characters such as blanks are not allowed. Enter the host name again.&lt;br /&gt;Explanation: This installation requires a fully-qualified host name. Short host names, loopback addresses, and IP addresses are not allowed.&lt;br /&gt;User Response: Enter the host name again.&lt;br /&gt;&lt;br /&gt;To resolve this -&lt;br /&gt;Just check the complete name of your box&lt;br /&gt;uname -a&lt;br /&gt;for me it is&lt;br /&gt;localhost.localdomain&lt;br /&gt;Now -&lt;br /&gt;vi /etc/hosts as root&lt;br /&gt;edit localhost.localdomain to localhost.localdomain.com&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1566720593649588822?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1566720593649588822/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1566720593649588822' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1566720593649588822'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1566720593649588822'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/11/ejpic0067e.html' title='EJPIC0067E'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7205781017665675077</id><published>2009-10-30T23:19:00.003+05:30</published><updated>2009-10-30T23:27:42.746+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Profiles'/><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='6.0'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><category scheme='http://www.blogger.com/atom/ns#' term='Installation'/><category scheme='http://www.blogger.com/atom/ns#' term='6.1'/><title type='text'>Profile Creation, New in 6.1</title><content type='html'>In 6.0 - To create a profile one can call AppServerPath/bin/ProfileCreator/pctSolaris.bin command or wasprofile.sh command.&lt;br /&gt;&lt;br /&gt;Ex., &lt;br /&gt;./wasprofile.sh -create -profileName bladetcb6profile -profilePath /usr/IBM/WebSphere/AppServer/profiles/bladetcb6profile -templatePath /usr/WebSphere/AppServer -profileTemplates/default -nodeName bladetcb6node -cellName bladetcb6Cell -hostName bladetcb6.rtp.raleigh.ibm.com&lt;br /&gt;&lt;br /&gt;Or you can kick this process thru firststeps.&lt;br /&gt;&lt;br /&gt;In 6.1, wasprofile.sh command is available too but it is depricated. Instead you have manageprofil.sh command.&lt;br /&gt;ex.,&lt;br /&gt;manageprofiles.sh -create&lt;br /&gt;              -profileName shasti &lt;br /&gt;              -profilePath /shasti/WebSphere &lt;br /&gt;              -templatePath /opt/IBM/WebSphere/AppServer/profileTemplates/dmgr&lt;br /&gt;              -cellName cell1&lt;br /&gt;              -hostName planetaix &lt;br /&gt;              -nodeName dmgr1&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7205781017665675077?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7205781017665675077/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7205781017665675077' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7205781017665675077'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7205781017665675077'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/10/profile-creation-new-in-61.html' title='Profile Creation, New in 6.1'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-9113853562579383567</id><published>2009-10-30T23:10:00.003+05:30</published><updated>2009-10-30T23:19:20.804+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Troubleshooting'/><category scheme='http://www.blogger.com/atom/ns#' term='Installation'/><category scheme='http://www.blogger.com/atom/ns#' term='6.1'/><title type='text'>6.1.0.2 installer fails to create profile.</title><content type='html'>Issue -&lt;br /&gt;WAS 6.1.0.2 installer fails to create profile.&lt;br /&gt;log.txt -&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: 97SInstallInvokeWSProfile - /software/IBM/WebSphere/AppServer/properties/version/nif/config/install/97SInstallInvokeWSProfile.ijc&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: clearClassCache, percent complete: 25%&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: os400fp, percent complete: 50%&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: copyEmbedProductFile, percent complete: 75%&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: runISCDeployRestore, percent complete: 100%&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=2&lt;br /&gt;Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, &lt;span style="font-weight:bold;"&gt;INSTCONFPARTIALSUCCESS&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;trace.txt -&lt;br /&gt;&lt;span style="font-weight:bold;"&gt;INSTCONFPARTIALSUCCESS&lt;/span&gt;: Partially successful install of: zip:///software/tempinst/WAS/was.installconfig.pak&lt;br /&gt;I Current install/uninstall process is successful. Process type is: install&lt;br /&gt;I CWUPI0000I: EXITCODE=2&lt;br /&gt;I &lt;span style="font-weight:bold;"&gt;INSTCONFPARTIALSUCCESS&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Solution -&lt;br /&gt;Install without creating a profile, apply latest fix packs and then create profile.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-9113853562579383567?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/9113853562579383567/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=9113853562579383567' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9113853562579383567'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9113853562579383567'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/10/6102-installer-fails-to-create-profile.html' title='6.1.0.2 installer fails to create profile.'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8220138419484823876</id><published>2009-09-12T01:50:00.004+05:30</published><updated>2009-09-15T19:06:25.085+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='6.0'/><category scheme='http://www.blogger.com/atom/ns#' term='6.1'/><title type='text'>6.0 and 6.1 Co-exist topology</title><content type='html'>You have 6.0.xx installed on a machine. You wanted to install 6.1 on the same machine and migrate 6.0.xx to 6.1 later.&lt;br /&gt;Now, You found that, your 6.1 installation going on smooth, but, you are amazed to see this message at the end of your log.txt&lt;br /&gt;(Sep 11, 2009 4:00:11 PM), Process, &lt;span style="font-weight:bold;"&gt;com.ibm.ws.install.ni.ismp.installtoolkitbridge.ISMPInstallToolkitBridgeForNIFramework, wrn, Config action failed: 97SInstallInvokeWSProfile - /software/IBM/WebSphere61/AppServer/properties/version/nif/config/install/97SInstallInvokeWSProfile.ijc&lt;/span&gt; &lt;br /&gt;(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: clearClassCache, percent complete: 25%&lt;br /&gt;(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: os400fp, percent complete: 50%&lt;br /&gt;(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: copyEmbedProductFile, percent complete: 75%&lt;br /&gt;(Sep 11, 2009 4:00:11 PM), Process, com.ibm.ws.install.ni.ismp.actions.InstallNIFPackage, msg1, Running configuration command: runISCDeployRestore, percent complete: 100%&lt;br /&gt;(Sep 11, 2009 4:04:37 PM), Process, com.ibm.ws.install.ni.ismp.actions.SettleNIFRegistryAction, msg1, Current install/uninstall process is successful. Process type is: install&lt;br /&gt;(Sep 11, 2009 4:04:37 PM), Process, &lt;span style="font-weight:bold;"&gt;com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=2&lt;/span&gt;&lt;br /&gt;(Sep 11, 2009 4:04:37 PM), Process, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, &lt;span style="font-weight:bold;"&gt;INSTCONFPARTIALSUCCESS&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The reason for this is, since you already installed 6.0.xx, you have already used default ports. Now, for the new installation, you need to tell the installer not to look for default ports.&lt;br /&gt;&lt;br /&gt;Explore the following technote -&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;context=SSEQTP&amp;q1=wrn%2c+Config+action+failed%3a+97SInstallInvokeWSProfile&amp;uid=swg21261120&amp;loc=en_US&amp;cs=utf-8&amp;lang=en"&gt;&lt;br /&gt;http://www-01.ibm.com/support/docview.wss?rs=180&amp;context=SSEQTP&amp;q1=wrn%2c+Config+action+failed%3a+97SInstallInvokeWSProfile&amp;uid=swg21261120&amp;loc=en_US&amp;cs=utf-8&amp;lang=en&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8220138419484823876?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8220138419484823876/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8220138419484823876' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8220138419484823876'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8220138419484823876'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/09/60-and-61-co-exist-topology.html' title='6.0 and 6.1 Co-exist topology'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2572740619524571527</id><published>2009-08-25T00:13:00.002+05:30</published><updated>2009-08-25T00:16:04.022+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='MIGRATION'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Plugin'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>WAS Migration Step By Step</title><content type='html'>Here is the IBM WAS Tech Library Article on "A quick guide for migrating to WebSphere Application Server V6.1"&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.ibm.com/developerworks/websphere/library/techarticles/0608_chalmers/0608_chalmers.html"&gt;http://www.ibm.com/developerworks/websphere/library/techarticles/0608_chalmers/0608_chalmers.html&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2572740619524571527?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2572740619524571527/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2572740619524571527' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2572740619524571527'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2572740619524571527'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/08/was-migration-step-by-step.html' title='WAS Migration Step By Step'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2643110615247460022</id><published>2009-08-20T21:26:00.002+05:30</published><updated>2009-08-21T23:40:37.747+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><category scheme='http://www.blogger.com/atom/ns#' term='JAVA'/><title type='text'>64 bit or 32 bit JVM?</title><content type='html'>How to know your WAS version is 32 bit or 64 bit?&lt;br /&gt;This is a machine which has WAS 64 bit&lt;br /&gt;$ ./java -d64 -version&lt;br /&gt;java version "1.5.0_06"&lt;br /&gt;Java(TM) 2 Runtime Environment, Standard Edition (IBM build 1.5.0_06-erdist-20060404 20060511)&lt;br /&gt;Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-erdist-20060404, mixed mode)&lt;br /&gt;IBM Java ORB build orb50-20060511a (SR2)&lt;br /&gt;XML build XSLT4J Java 2.7.4&lt;br /&gt;XML build IBM JAXP 1.3.5&lt;br /&gt;XML build XML4J 4.4.5&lt;br /&gt;&lt;br /&gt;This is a machine which has WAS 32bit&lt;br /&gt;$ ./java -d64 -version&lt;br /&gt;execv(): No such file or directory&lt;br /&gt;Error trying to exec /software/opt/IBM/WebSphere/AppServer/java/jre/bin/sparcv9/java.&lt;br /&gt;Check if file exists and permissions are set correctly.&lt;br /&gt;Failed to start a 64-bit JVM process from a 32-bit JVM.&lt;br /&gt;Verify all necessary J2SE components have been installed.&lt;br /&gt;(Solaris SPARC 64-bit components must be installed after 32-bit components.)&lt;br /&gt;&lt;br /&gt;So acid Test is -&lt;br /&gt;goto App Server javahome&lt;br /&gt;/path/to/washome/java/jre/bin&lt;br /&gt;./java -d64 -version&lt;br /&gt;&lt;br /&gt;if it is 64 bit, it returns with version info.&lt;br /&gt;otherwise returns with no such file or directory.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2643110615247460022?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2643110615247460022/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2643110615247460022' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2643110615247460022'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2643110615247460022'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/08/64-bit-or-32-bit-jvm.html' title='64 bit or 32 bit JVM?'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-9192728046967291551</id><published>2009-07-27T19:44:00.003+05:30</published><updated>2009-08-18T01:31:02.341+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='SSL'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Plugin'/><category scheme='http://www.blogger.com/atom/ns#' term='TechNote'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>SSL Technotes</title><content type='html'>Here are some useful technotes on implementing custome SSL on WAS.&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21215717"&gt;Creating Custom Secure Socket Layer (SSL) Key Files for V5.0 using a CA Certificate&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21221261"&gt;Creating Custom Secure Socket Layer (SSL) Key Files for V6.0 using a CA Certificate&lt;/a&gt;&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;uid=swg21305596"&gt;Manually Replacing SSL Certificates in V6.1  &lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Note -&lt;br /&gt;Please join in my WebSphere Community in Orkut, &lt;a href="http://www.orkut.com/Main#Community.aspx?cmm=92119372"&gt;WebSphere Zone&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-9192728046967291551?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/9192728046967291551/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=9192728046967291551' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9192728046967291551'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9192728046967291551'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/07/ssl-technotes.html' title='SSL Technotes'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3847129540065772272</id><published>2009-07-23T20:04:00.002+05:30</published><updated>2009-07-23T20:12:16.146+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='PMR'/><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='collector'/><title type='text'>Collector Tool</title><content type='html'>Someone asked me how to run collector tool. IBM Doc says, run the tool not from APPSERVER_INST_PATH/bin, but run from working directory. What exactly is that?&lt;br /&gt;&lt;br /&gt;The collector tool gathers information about your WebSphere Application Server installation and packages it in a Java archive (JAR) file that you can send to IBM Customer Support to assist in determining and analyzing your problem. Information in the JAR file includes logs, property files, configuration files, operating system and Java data, and the presence and level of each software prerequisite.&lt;br /&gt;&lt;br /&gt;collector command - summary option&lt;br /&gt;&lt;br /&gt;WebSphere Application Server products include an enhancement to the collector tool beginning with Version 5.0.2, known as the collector summary option.&lt;br /&gt;&lt;br /&gt;The collector summary option helps you communicate with WebSphere Application Server technical staff at IBM Support. Run the collector tool with the -Summary option to produce a lightweight text file and console version of some of the information in the Java archive (JAR) file that the tool produces without the -Summary parameter. You can use the collector summary option to retrieve basic configuration and prerequisite software level information when starting a conversation with IBM Support.&lt;br /&gt;&lt;br /&gt;The collector summary option produces version information for the WebSphere Application Server product and the operating system as well as other information. It stores the information in the Collector_Summary.txt file and writes it to the console. You can use the information to answer initial questions from IBM Support or you can send the Collector_Summary.txt file directly to IBM Support.&lt;br /&gt;&lt;br /&gt;Collector tool collect key information including ffdc, configuration, logs, and so on and makes a jar file with all the information. So, depending on your configuration and all, jar file may occupy lot of space. So, IBM docs says that, create a folder out of appserver installation path.&lt;br /&gt;Example,&lt;br /&gt;mkdir /tmp/collector&lt;br /&gt;cd /tmp/collector&lt;br /&gt;&lt;br /&gt;Then run the script as needed&lt;br /&gt;/appserver/instpath/profiles/profilename/bin/collector.sh&lt;br /&gt;or &lt;br /&gt;/appserver/instpath/profiles/profilename/bin/collector.sh -summery&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3847129540065772272?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3847129540065772272/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3847129540065772272' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3847129540065772272'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3847129540065772272'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/07/collector-tool.html' title='Collector Tool'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-9042088915481591907</id><published>2009-07-23T19:30:00.006+05:30</published><updated>2009-07-23T20:03:31.096+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>Symbolic links</title><content type='html'>Sometimes, in the process of WebSphere, IHS Administration, it may require you to create symbolic links. This is the procedure.&lt;br /&gt;&lt;br /&gt;ln is the command to create symbolic links.&lt;br /&gt;$man ln&lt;br /&gt;User Commands ln&lt;br /&gt;&lt;br /&gt;NAME&lt;br /&gt;     ln - make hard or symbolic links to files&lt;br /&gt;&lt;br /&gt;SYNOPSIS&lt;br /&gt;     /usr/bin/ln [-fns] source_file [target]&lt;br /&gt;&lt;br /&gt;     /usr/bin/ln [-fns] source_file... target&lt;br /&gt;&lt;br /&gt;     /usr/xpg4/bin/ln [-fs] source_file [target]&lt;br /&gt;&lt;br /&gt;     /usr/xpg4/bin/ln [-fs] source_file... target&lt;br /&gt;&lt;br /&gt;DESCRIPTION&lt;br /&gt;     In the first synopsis form, the ln  utility  creates  a  new&lt;br /&gt;     directory   entry   (link)   for   the   file  specified  by&lt;br /&gt;     source_file, at the destination path specified by target. If&lt;br /&gt;     target  is  not  specified,  the link is made in the current&lt;br /&gt;     directory. This first synopsis  form  is  assumed  when  the&lt;br /&gt;     final  operand  does not name an existing directory; if more&lt;br /&gt;     than two operands are specified and  the  final  is  not  an&lt;br /&gt;     existing directory, an error will result.&lt;br /&gt;&lt;br /&gt;     In the second synopsis form, the ln utility  creates  a  new&lt;br /&gt;     directory  entry  for  each  file specified by a source_file&lt;br /&gt;     operand, at a destination path  in  the  existing  directory&lt;br /&gt;     named by target.&lt;br /&gt;..............................&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Example -&lt;br /&gt;Developers wanted to have a look at SystemOut.log and SystemErr.log. They dont have uid on the box. So, I need to create a web link to this through HTTP Server.&lt;br /&gt;I did like this.&lt;br /&gt;I have created a document root called logs.&lt;br /&gt;/logs&lt;br /&gt;I created symbolic links to SystemOut.log and SystemErr.log like this&lt;br /&gt;ln -s source destination&lt;br /&gt;This creates a softlink *from* a file to a *file*&lt;br /&gt;$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log SystemOut.log&lt;br /&gt;$ln -s /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log SystemErr.log&lt;br /&gt;This created me two files SystemOut.log and SystemErr.log under /logs&lt;br /&gt;if I ls -ltr on /logs, I get this list&lt;br /&gt;SystemOut.log -&gt; /path/to/appserver/profiles/profilename/logs/servername/SystemOut.log &lt;br /&gt;SystemErr.log -&gt; /path/to/appserver/profiles/profilename/logs/servername/SystemErr.log&lt;br /&gt;&lt;br /&gt;Now, I have created a html file, say, index.html with hyperlinks like this -&lt;br /&gt;Server Logs&lt;br /&gt;&lt; A HREF="SystemOut.log"&gt;SystemOut&lt; / A&gt;&lt; br /&gt;&lt;br /&gt;&lt; A HREF="SystemErr.log"&gt;SystemErr&lt; / A&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-9042088915481591907?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/9042088915481591907/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=9042088915481591907' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9042088915481591907'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/9042088915481591907'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/07/symbolic-links.html' title='Symbolic links'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7712369317646441045</id><published>2009-07-14T21:05:00.004+05:30</published><updated>2009-07-14T21:23:31.510+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Plugin'/><title type='text'>Enable Trace in Plugin-cfg.xml</title><content type='html'>WebServer Plugin writes a log, by default its named as http-plugin.log, by default placed under PLUGIN_HOME/logs/&lt;br /&gt;Plugin writes Error messages into this log. The attribute which deals with this is &lt;br /&gt;&lt; Log &gt; in the plugin-cfg.xml&lt;br /&gt;Ex.,&lt;br /&gt;&lt; Log LogLevel="Error" Name="/usr/IBM/WebSphere/Plugins/logs/http_plugin.log" / &gt;&lt;br /&gt;&lt;br /&gt;According to above line all Error messages will be written into http-plugin.log.&lt;br /&gt;&lt;br /&gt;How to enable trace in the plugin-cfg.xml? if that is the question, do like this -&lt;br /&gt;&lt;br /&gt;&lt; Log LogLevel="Trace" Name="/usr/IBM/WebSphere/Plugins/logs/http_plugin.log" / &gt;&lt;br /&gt;&lt;br /&gt;From the InfoCenter -&lt;br /&gt;Plug-in Problem Determination Steps &lt;br /&gt;The plug-in provides very readable tracing which can be beneficial in helping to figure out the problem. By setting the LogLevel attribute in the config/plugin-cfg.xml file to Trace, you can follow the request processing to see what is going wrong. &lt;br /&gt;Note: If you are using a Veritas File System with large file support enabled, file sizes up to two terabytes are allowed. In this case, if you set the LogLevel attribute in the plugin-cfg.xml file to LogLevel=Trace, then the http_plugin.log file might grow quickly and consume all available space on your file system. Therefore, you should set the value of the LogLevel attribute to ERROR or DEBUG to prevent high CPU utilization.&lt;br /&gt;At a high level, complete these steps.&lt;br /&gt;The plug-in gets a request. &lt;br /&gt;The plug-in checks the routes defined in the plugin-cfg.xml file. &lt;br /&gt;It finds the server group. &lt;br /&gt;It finds the server. &lt;br /&gt;It picks the transport protocol, HTTP or HTTPS. &lt;br /&gt;It sends the request. &lt;br /&gt;It reads the response. &lt;br /&gt;It writes it back to the client. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Here is the URL for &lt;span style="font-weight:bold;"&gt;&lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/rtrb_plugincomp.html"&gt;Web server plug-in troubleshooting tips&lt;/a&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7712369317646441045?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7712369317646441045/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7712369317646441045' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7712369317646441045'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7712369317646441045'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/07/enable-trace-in-plugin-cfgxml.html' title='Enable Trace in Plugin-cfg.xml'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8683392969787267663</id><published>2009-07-14T20:32:00.002+05:30</published><updated>2009-07-14T20:35:22.540+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WAS'/><category scheme='http://www.blogger.com/atom/ns#' term='Plugin'/><category scheme='http://www.blogger.com/atom/ns#' term='fixpacks'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>Multiple Authentication Bypass Vulnerabilities within IBM WAS</title><content type='html'>Multiple Authentication Bypass Vulnerabilities within IBM WebSphere Application Server&lt;br /&gt;&lt;br /&gt;OVERVIEW:&lt;br /&gt;Two vulnerabilities in IBM WebSphere Application Server have recently been made public.  IBM WebSphere Application Server is a software application server that uses web technologies and can be implemented on many common operating systems. Both vulnerabilities may allow malicious users to bypass authentication required to access a service running on the vulnerable server. Successful exploitation may allow attackers to gain unauthorized access to the service, which may lead to other attacks.&lt;br /&gt;&lt;br /&gt;SYSTEMS AFFECTED:&lt;br /&gt;The vulnerability identified by IBM in PK72138 (Bugtraq ID 35594):&lt;br /&gt;*         IBM WebSphere Application Server 7.0 1&lt;br /&gt;*         IBM WebSphere Application Server 6.1 23&lt;br /&gt;*         IBM WebSphere Application Server 6.1 22&lt;br /&gt;*         IBM WebSphere Application Server 6.1 21&lt;br /&gt;*         IBM WebSphere Application Server 6.1 20&lt;br /&gt;*         IBM WebSphere Application Server 6.1 19&lt;br /&gt;*         IBM WebSphere Application Server 6.1 18&lt;br /&gt;*         IBM WebSphere Application Server 6.1 17&lt;br /&gt;*         IBM WebSphere Application Server 6.1 15&lt;br /&gt;*         IBM WebSphere Application Server 6.1 13&lt;br /&gt;*         IBM WebSphere Application Server 6.1 12&lt;br /&gt;*         IBM WebSphere Application Server 6.1 10&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .9&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .7&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .6&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .5&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .3&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .2&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .14&lt;br /&gt;*         IBM WebSphere Application Server 6.1 .1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 6.1&lt;br /&gt;*         IBM WebSphere Application Server 7.0&lt;br /&gt;&lt;br /&gt; The vulnerability identified by IBM in PK75992 (Bugtraq ID 35610):&lt;br /&gt;*         IBM WebSphere Application Server 7.0 1&lt;br /&gt;*         IBM WebSphere Application Server 6.1 21&lt;br /&gt;*         IBM WebSphere Application Server 6.1 19&lt;br /&gt;*         IBM WebSphere Application Server 6.1 17&lt;br /&gt;*         IBM WebSphere Application Server 6.1 15&lt;br /&gt;*         IBM WebSphere Application Server 6.0.2 31&lt;br /&gt;*         IBM WebSphere Application Server 6.0.2 29&lt;br /&gt;*         IBM WebSphere Application Server 6.0.2 27&lt;br /&gt;*         IBM WebSphere Application Server 6.0.2 .25&lt;br /&gt;*         IBM WebSphere Application Server 7.0&lt;br /&gt;&lt;br /&gt;RISK:&lt;br /&gt;Government:&lt;br /&gt;*         Large and medium government entities: High&lt;br /&gt;*         Small government entities: High&lt;br /&gt;&lt;br /&gt;Businesses:&lt;br /&gt;*         Large and medium business entities: High&lt;br /&gt;*         Small business entities: High&lt;br /&gt;&lt;br /&gt;Home users: N/A&lt;br /&gt;&lt;br /&gt;DESCRIPTION:&lt;br /&gt;IBM has confirmed the existence of two vulnerabilities that may allow a remote attacker to bypass application server authentication. Exploiting these vulnerabilities could allow an attacker to access restricted services, which may then lead to other attacks. Both vulnerabilities are associated with WS-Security, which is the security implementation within the Java API for XML Web Services (JAX-WS).&lt;br /&gt;The first vulnerability discovered within WS-Security, referenced and addressed by IBM in PK72138, can only be exploited when the security policy is implemented at the 'Operational  Level'.  When this policy is established, WS-Security does not properly handle inbound requests that lack a SOAPAction or WS-Addressing Action. An attacker can craft a malicious inbound request to exploit this vulnerability. Successful exploitation may allow attackers to bypass certain security restrictions, which may then lead to other attacks.&lt;br /&gt;The second vulnerability, referenced and addressed by IBM in PK75992, arises in the way WS-Security validates the 'UsernameToken' object. It is possible for WS-Security to incorrectly validate these tokens, allowing a malicious user to bypass the authentication process. This may allow a malicious user to conduct further attacks.&lt;br /&gt;&lt;br /&gt;RECOMMENDATIONS:&lt;br /&gt;We recommend the following actions be taken:&lt;br /&gt;*         Apply appropriate patches provided by IBM to vulnerable systems immediately after appropriate testing.&lt;br /&gt;*         Deploy network intrusion detection systems to monitor network traffic for malicious activity.&lt;br /&gt;&lt;br /&gt;REFERENCES:&lt;br /&gt;&lt;br /&gt;IBM:&lt;br /&gt;&lt;a href="http://www-01.ibm.com/support/docview.wss?rs=180&amp;context=SSEQTP&amp;dc=D600&amp;uid=swg21367223&amp;loc=en_US&amp;cs=UTF-8&amp;lang=en&amp;rss=ct180WebSphere"&gt;http://www-01.ibm.com/support/docview.wss?rs=180&amp;context=SSEQTP&amp;dc=D600&amp;uid=swg21367223&amp;loc=en_US&amp;cs=UTF-8&amp;lang=en&amp;rss=ct180WebSphere&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Security Focus:&lt;br /&gt;&lt;a href="http://www.securityfocus.com/bid/35594"&gt;http://www.securityfocus.com/bid/35594&lt;/a&gt; &lt;br /&gt;&lt;a href="http://www.securityfocus.com/bid/35610"&gt;http://www.securityfocus.com/bid/35610&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;CVE:&lt;br /&gt;&lt;a href="http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0903"&gt;http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0903&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8683392969787267663?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8683392969787267663/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8683392969787267663' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8683392969787267663'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8683392969787267663'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/07/multiple-authentication-bypass.html' title='Multiple Authentication Bypass Vulnerabilities within IBM WAS'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7263224160837732389</id><published>2009-06-29T19:02:00.004+05:30</published><updated>2009-07-01T20:26:27.555+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='SSL'/><category scheme='http://www.blogger.com/atom/ns#' term='JAVA'/><title type='text'>Applet Security -</title><content type='html'>When an app is accessed through https, if there is no trust between app server and browser jre, client jvm may spit SSL HandShake Error. Error may go like this -&lt;br /&gt;Error Occured during session initialization: Error SSL connecting to server:9446:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target&lt;br /&gt;&lt;br /&gt;Its very simple to solve this. One needs to import client certificate into jre/lib/security/cacerts which is the trust store of the JVM.&lt;br /&gt;example -&lt;br /&gt;"C:\Program Files\Java\jre1.5.0_11\bin\keytool" -import -trustcacerts -keystore "C:\Program Files\Java\jre1.5.0_11\lib\security\cacerts" -storepass changeit -noprompt -alias ALIAS_NAME -file "&lt;PATH TO CERTIFICATE&gt;\CERTIFICATE_NAME"&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7263224160837732389?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7263224160837732389/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7263224160837732389' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7263224160837732389'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7263224160837732389'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/applet-security.html' title='Applet Security -'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5392934785970354581</id><published>2009-06-22T23:52:00.002+05:30</published><updated>2009-06-22T23:55:09.332+05:30</updated><title type='text'>10000</title><content type='html'>I am happy to announce that this blog crossed 10000 hits.&lt;br /&gt;&lt;br /&gt;Thanks to all for viewing my blog on webshpere.&lt;br /&gt;&lt;br /&gt;Please mail me if u have any questions or for any info or any suggestions.&lt;br /&gt;&lt;br /&gt;admin.websphere@gmail.com&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5392934785970354581?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5392934785970354581/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5392934785970354581' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5392934785970354581'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5392934785970354581'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/10000.html' title='10000'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6837707163376620787</id><published>2009-06-17T20:45:00.003+05:30</published><updated>2009-06-17T20:53:08.751+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='AIX'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><title type='text'>While using df</title><content type='html'>Solaris&lt;br /&gt;df -h is the command to display available disk free space in bytes&lt;br /&gt;e.g.,&lt;br /&gt;$df -h&lt;br /&gt;Filesystem                      size     used     avail     capacity  Mounted on&lt;br /&gt;/dev/md/dsk/d84        3.9G   136M   3.8G     4%           /var&lt;br /&gt;swap                                6.6G    992K   6.6G     1%           /tmp&lt;br /&gt;/dev/md/dsk/d101      20G    7.8G     12G      41%         /software&lt;br /&gt;&lt;br /&gt;Equivalent df in AIX&lt;br /&gt;df -g&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6837707163376620787?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6837707163376620787/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6837707163376620787' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6837707163376620787'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6837707163376620787'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/while-using-df.html' title='While using df'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6265324862452549534</id><published>2009-06-17T20:35:00.000+05:30</published><updated>2009-06-17T20:36:24.715+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='AIX'/><title type='text'>AIX df command</title><content type='html'>&lt;h2 id="a10192b83"&gt;df Command&lt;/h2&gt;  &lt;a name="a10192b85"&gt;&lt;/a&gt; &lt;h3 id="a10192b85"&gt;Purpose&lt;/h3&gt; &lt;p&gt;Reports information about space on file systems. This document describes the AIX &lt;strong&gt;df&lt;/strong&gt; command as well as the &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#systemvdf"&gt;System V version of &lt;strong&gt;df&lt;/strong&gt;&lt;/a&gt;.&lt;/p&gt; &lt;a name="d6164f4862mart"&gt;&lt;/a&gt; &lt;h3 id="d6164f4862mart"&gt;Syntax&lt;/h3&gt; &lt;p&gt;&lt;strong&gt;df&lt;/strong&gt; [ [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#yqjki2d9ria"&gt;&lt;strong&gt;-P&lt;/strong&gt;&lt;/a&gt; ] | [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#a10192b8f"&gt;&lt;strong&gt;-I&lt;/strong&gt;&lt;/a&gt; |  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#a10192b90"&gt;&lt;strong&gt;-M&lt;/strong&gt;&lt;/a&gt; |  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#a10192b79"&gt;&lt;strong&gt;-i&lt;/strong&gt;&lt;/a&gt; |  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#xepmi1acria"&gt;&lt;strong&gt;-t&lt;/strong&gt;&lt;/a&gt; |  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#a1119b5a"&gt;&lt;strong&gt;-v&lt;/strong&gt;&lt;/a&gt; ] ] [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#kxjki2dfria"&gt;&lt;strong&gt;-k&lt;/strong&gt;&lt;/a&gt; ] [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#dfminusmflag"&gt;&lt;strong&gt;-m&lt;/strong&gt;&lt;/a&gt; ] [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#dfminusgflag"&gt;&lt;strong&gt;-g&lt;/strong&gt;&lt;/a&gt; ] [  &lt;a href="http://publib.boulder.ibm.com/infocenter/systems/topic/com.ibm.aix.cmds/doc/aixcmds2/df.htm#a10192b8e"&gt;&lt;strong&gt;-s&lt;/strong&gt;&lt;/a&gt; ] [&lt;em&gt;FileSystem &lt;/em&gt;... | &lt;em&gt;File...&lt;/em&gt; ]&lt;/p&gt; &lt;a name="a10192b89"&gt;&lt;/a&gt; &lt;h3 id="a10192b89"&gt;Description&lt;/h3&gt; &lt;a name="f006d19183mela"&gt;&lt;/a&gt; &lt;p id="f006d19183mela"&gt;The &lt;strong&gt;df&lt;/strong&gt; command displays information about total space and available space on a file system. The &lt;em&gt;FileSystem&lt;/em&gt; parameter specifies the name of the device on which the file system resides, the directory on which the file system is mounted, or the relative path name of a file system. The &lt;em&gt;File&lt;/em&gt; parameter specifies a file or a directory that is not a mount point. If the &lt;em&gt;File&lt;/em&gt; parameter is specified, the &lt;strong&gt;df&lt;/strong&gt; command displays information for the file system on which the file or directory resides. If you do not specify the &lt;em&gt;FileSystem&lt;/em&gt; or &lt;em&gt;File&lt;/em&gt; parameter, the &lt;strong&gt;df&lt;/strong&gt; command displays information for all currently mounted file systems. File system statistics are displayed in units of 512-byte blocks by default.&lt;/p&gt; &lt;a name="f006d19457mela"&gt;&lt;/a&gt; &lt;p id="f006d19457mela"&gt;The &lt;strong&gt;df&lt;/strong&gt; command gets file system space statistics from the &lt;strong&gt;statfs&lt;/strong&gt; system call. However, specifying the &lt;strong&gt;-s&lt;/strong&gt; flag gets the statistics from the virtual file system (VFS) specific file system helper. If you do not specify arguments with the &lt;strong&gt;-s&lt;/strong&gt; flag and the helper fails to get the statistics, the &lt;strong&gt;statfs&lt;/strong&gt; system call statistics are used. Under certain exceptional conditions, such as when a file system is being modified while the &lt;strong&gt;df&lt;/strong&gt; command is running, the statistics displayed by the &lt;strong&gt;df&lt;/strong&gt; command might not be accurate.&lt;/p&gt; &lt;a name="wq292"&gt;&lt;/a&gt; &lt;div class="notetitle" id="wq292"&gt;Note:&lt;/div&gt; &lt;div class="notebody"&gt;Some remote file systems, such as the Network File System (NFS), do not provide all the information that the &lt;strong&gt;df&lt;/strong&gt; command needs. The &lt;strong&gt;df&lt;/strong&gt; command prints blanks for statistics that the server does not provide.&lt;/div&gt; &lt;p&gt;The &lt;strong&gt;df&lt;/strong&gt; command does not fully support NFSv4 filesystems. Use the &lt;strong&gt;nfs4cl&lt;/strong&gt; command to extract block and space information.&lt;/p&gt; &lt;a name="a10192b8d"&gt;&lt;/a&gt; &lt;h3 id="a10192b8d"&gt;Flags&lt;/h3&gt;  &lt;a name="wq293"&gt;&lt;/a&gt; &lt;table id="wq293" summary="" rules="none" width="100%" border="0" frame="void"&gt; &lt;tbody valign="top"&gt; &lt;tr&gt; &lt;td width="10%"&gt; &lt;a id="dfminusgflag" name="dfminusgflag"&gt;&lt;/a&gt;&lt;strong&gt;-g&lt;/strong&gt;&lt;/td&gt; &lt;td width="89%"&gt; Displays statistics in units of GB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a10192b79" name="a10192b79"&gt;&lt;/a&gt;&lt;strong&gt;-i&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays the number of used inodes and the percentage of inodes in use for the file system. This output is the default when the specified file system is mounted.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a10192b8f" name="a10192b8f"&gt;&lt;/a&gt;&lt;strong&gt;-I&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays information on the total number of blocks, the used space, the free space, the percentage of used space, and the mount point for the file system.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="kxjki2dfria" name="kxjki2dfria"&gt;&lt;/a&gt;&lt;strong&gt;-k&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays statistics in units of 1024-byte blocks.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="dfminusmflag" name="dfminusmflag"&gt;&lt;/a&gt;&lt;strong&gt;-m&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays statistics in units of MB blocks. The output values for the file system statistics would be in floating point numbers as value of each unit in bytes is significantly high.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a10192b90" name="a10192b90"&gt;&lt;/a&gt;&lt;strong&gt;-M&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays the mount point information for the file system in the second column.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="yqjki2d9ria" name="yqjki2d9ria"&gt;&lt;/a&gt;&lt;strong&gt;-P&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays information on the file system in POSIX portable format.   &lt;p&gt;When the &lt;strong&gt;-P&lt;/strong&gt; flag is specified, the header line appears similar to:&lt;/p&gt;   &lt;pre class="xmp"&gt;Filesystem 512-blocks Used Available Capacity Mounted on\n&lt;/pre&gt;  &lt;p&gt;If the &lt;strong&gt;-k&lt;/strong&gt;, &lt;strong&gt;-m&lt;/strong&gt; or &lt;strong&gt;-g&lt;/strong&gt; flag is specified in addition to the &lt;strong&gt;-P&lt;/strong&gt; flag, the column  heading 512-blocks is replaced by the respective units, depending on which  of these flags is used with the &lt;strong&gt;-P&lt;/strong&gt; flag.&lt;/p&gt;  &lt;p&gt;File system statistics are displayed on one line in the following order:&lt;/p&gt;  &lt;p&gt;&lt;em&gt;FileSystem, TotalSpace, UsedSpace, FreeSpace, UsedPercentage, MountPoint&lt;/em&gt;&lt;/p&gt;&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a10192b8e" name="a10192b8e"&gt;&lt;/a&gt;&lt;strong&gt;-s&lt;/strong&gt;&lt;/td&gt; &lt;td&gt; Displays statistics on unmounted JFS or Enhanced JFS file systems by the command line arguments. If there are no arguments specified, the &lt;span class="pk"&gt;-s&lt;/span&gt; flag has no effect. If the file systems specified by the argument are currently mounted or an argument is a file, the &lt;span class="pk"&gt;-s&lt;/span&gt; flag has no effect for that particular argument. To collect statistics on unmounted file systems, an argument must be a JFS or Enhanced JFS file system mount point or device, the file system must be listed in &lt;strong&gt;/etc/filesystems&lt;/strong&gt;, and the user must have read access to the device.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="xepmi1acria" name="xepmi1acria"&gt;&lt;/a&gt;&lt;strong&gt;-t&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;  Includes figures for total allocated space in the output.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a1119b5a" name="a1119b5a"&gt;&lt;/a&gt;&lt;strong&gt;-v&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;  Displays all information for the specified file system.&lt;/td&gt; &lt;/tr&gt; &lt;/tbody&gt; &lt;/table&gt;&lt;p class="indatacontent"&gt;The values of the output parameters with the flags &lt;strong&gt;-m&lt;/strong&gt; and &lt;strong&gt;-g&lt;/strong&gt; would be rounded  off to nearest second decimal digit.  If all or any two of the &lt;strong&gt;-k&lt;/strong&gt;, &lt;strong&gt;-m&lt;/strong&gt; and &lt;strong&gt;-g&lt;/strong&gt; flags are specified, the last one  specified takes effect.&lt;/p&gt; &lt;a name="ac3335f290mike"&gt;&lt;/a&gt; &lt;h3 id="ac3335f290mike"&gt;Exit Status&lt;/h3&gt; &lt;a name="f006d1b058mela"&gt;&lt;/a&gt; &lt;p id="f006d1b058mela"&gt;This command returns the following exit values:&lt;/p&gt; &lt;a name="wq294"&gt;&lt;/a&gt; &lt;table id="wq294" summary="" rules="none" width="100%" border="0" frame="void"&gt; &lt;tbody valign="top"&gt; &lt;tr&gt; &lt;td width="9%"&gt; &lt;a id="ac3335f737mike" name="ac3335f737mike"&gt;&lt;/a&gt;&lt;strong&gt;0&lt;/strong&gt;&lt;/td&gt; &lt;td width="90%"&gt;  Successful completion.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="ac33360182mike" name="ac33360182mike"&gt;&lt;/a&gt;&lt;strong&gt;&gt;0&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;  An error occurred.&lt;/td&gt; &lt;/tr&gt; &lt;/tbody&gt; &lt;/table&gt; &lt;a name="a10192b91"&gt;&lt;/a&gt; &lt;h3 id="a10192b91"&gt;Examples&lt;/h3&gt; &lt;ol type="1"&gt;&lt;li&gt;To display information about all mounted file systems, enter:   &lt;pre class="xmp"&gt;df&lt;/pre&gt;&lt;p class="indatacontent"&gt; If your system has the &lt;strong&gt;/&lt;/strong&gt;,&lt;strong&gt; /usr&lt;/strong&gt;, &lt;strong&gt;/site&lt;/strong&gt;, and &lt;strong&gt;/usr/venus&lt;/strong&gt; file systems mounted, the output from the &lt;strong&gt;df&lt;/strong&gt; command resembles the following: &lt;/p&gt; &lt;pre class="xmp"&gt;Filesystem 512-blocks Free   %Used   Iused  %Iused  Mounted on&lt;br /&gt;/dev/hd0    19368     9976    48%     4714    5%     /&lt;br /&gt;/dev/hd1    24212     4808    80%     5031   19%     /usr&lt;br /&gt;/dev/hd2     9744     9352     4%     1900    4%     /site&lt;br /&gt;/dev/hd3     3868     3856     0%      986    0%     /usr/venus &lt;/pre&gt;&lt;/li&gt;&lt;li&gt;To display information about /test file system in 1024-byte blocks, enter:   &lt;pre class="xmp"&gt;df -k /test&lt;/pre&gt; &lt;pre class="xmp"&gt;Filesystem    1024 blocks    Free    %Used   Iused  %Iused  Mounted on&lt;br /&gt;/dev/lv11         16384     15824       4%      18      1%  /tmp/ravi1&lt;/pre&gt;  This displays the file system statistics in 1024-byte disk blocks.&lt;/li&gt;&lt;li&gt;To display information about /test file system in MB blocks, enter:   &lt;pre class="xmp"&gt;df -m /test&lt;/pre&gt; &lt;pre class="xmp"&gt;Filesystem    MB blocks    Free    %Used    Iused  %Iused  Mounted on&lt;br /&gt;/dev/lv11       16.00     15.46       4%       18      1%  /tmp/ravi1&lt;/pre&gt; This displays file system statistics in MB disk blocks rounded off to  nearest 2nd decimal digit.&lt;/li&gt;&lt;li&gt;To display information about the &lt;strong&gt;/test&lt;/strong&gt; file system in GB blocks, enter:   &lt;pre class="xmp"&gt;df -g /test&lt;/pre&gt;   &lt;pre class="xmp"&gt;Filesystem    GB blocks   Free     %Used    Iused  %Iused  Mounted on&lt;br /&gt;/dev/lv11          0.02   0.02        0%       18      1%  /tmp/ravi1&lt;/pre&gt;  This displays file system statistics in GB disk blocks rounded off to  nearest 2nd decimal digit.&lt;/li&gt;&lt;li&gt;To display available space on the file system in which your current directory resides, enter:   &lt;pre class="xmp"&gt;cd/&lt;br /&gt;df .&lt;/pre&gt;&lt;p class="indatacontent"&gt; The output from this command resembles the following: &lt;/p&gt; &lt;pre class="xmp"&gt;Device   512-blocks  free   %used   iused   %iused  Mounted on&lt;br /&gt;/dev/hd4    19368    9976    48%     4714    5%     / &lt;/pre&gt;&lt;/li&gt;&lt;/ol&gt; &lt;a name="a10192b9f"&gt;&lt;/a&gt; &lt;h3 id="a10192b9f"&gt;Files&lt;/h3&gt;  &lt;a name="wq296"&gt;&lt;/a&gt;   &lt;table id="wq296" summary="" rules="none" width="100%" border="0" frame="void"&gt;&lt;tbody valign="top"&gt;&lt;tr&gt; &lt;td width="26%"&gt; &lt;a id="a10192ba1" name="a10192ba1"&gt;&lt;/a&gt;&lt;strong&gt;/etc/filesystems&lt;/strong&gt;&lt;/td&gt; &lt;td width="73%"&gt;  Lists the known file systems and defines their characteristics.&lt;/td&gt; &lt;/tr&gt; &lt;tr&gt; &lt;td&gt; &lt;a id="a15798a9" name="a15798a9"&gt;&lt;/a&gt;&lt;strong&gt;/etc/vfs&lt;/strong&gt;&lt;/td&gt; &lt;td&gt;  Contains descriptions of virtual file system types.&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6265324862452549534?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6265324862452549534/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6265324862452549534' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6265324862452549534'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6265324862452549534'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/aix-df-command.html' title='AIX df command'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-405537395517375414</id><published>2009-06-17T20:11:00.004+05:30</published><updated>2009-06-17T20:22:45.654+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='Solaris'/><title type='text'>Solaris df, du, ls commands</title><content type='html'>Solaris df command&lt;br /&gt;&lt;br /&gt;New df, du, and ls Options&lt;br /&gt;&lt;br /&gt;The df, du, and ls commands have a new h option for displaying disk usage and file or file system sizes that are easy to understand.&lt;br /&gt;&lt;br /&gt;The default form of the df command displays file system size in blocks (512 bytes). The df output, in kilobytes, follows:&lt;br /&gt;&lt;br /&gt;$ df -k / /usr&lt;br /&gt;Filesystem                   kbytes     used         avail         capacity    Mounted on&lt;br /&gt;/dev/dsk/c0t0d0s0     192056       94788        78063         55%             /&lt;br /&gt;/dev/dsk/c0t0d0s6    1982988    829966   1093533  44%             /usr&lt;br /&gt;&lt;br /&gt;The same file system sizes displayed in powers of 1024 follows:&lt;br /&gt;&lt;br /&gt;$ df -h / /usr&lt;br /&gt;Filesystem                  size       used    avail    capacity     Mounted on&lt;br /&gt;/dev/dsk/c0t0d0s0      188M    93M      76M       55%               /&lt;br /&gt;/dev/dsk/c0t0d0s6      1.9G     811M   1.0G       44%               /usr&lt;br /&gt;&lt;br /&gt;The default form of the du command displays disk space in blocks (512 bytes). The du output, in blocks, follows:&lt;br /&gt;&lt;br /&gt;% du -s k*&lt;br /&gt;100     kadmin&lt;br /&gt;98      kadmin.local&lt;br /&gt;98      kdb5_util&lt;br /&gt;90      keyserv&lt;br /&gt;10      killall&lt;br /&gt;&lt;br /&gt;The same disk space displayed in powers of 1024 follows:&lt;br /&gt;&lt;br /&gt;% du -h k*&lt;br /&gt; 50K   kadmin&lt;br /&gt; 49K   kadmin.local&lt;br /&gt; 49K   kdb5_util&lt;br /&gt; 45K   keyserv&lt;br /&gt;  5K   killall&lt;br /&gt;&lt;br /&gt;The default form of the ls -l command displays file size in bytes. Use the ls -lh command to display file size in powers of 1024:&lt;br /&gt;&lt;br /&gt;% ls -lh k&lt;br /&gt;-r-xr-xr-x   1 root     bin          49K Nov 30 03:32 kadmin&lt;br /&gt;-r-xr-xr-x   1 root     bin          49K Nov 30 03:32 kadmin.local&lt;br /&gt;-r-xr-xr-x   1 root     bin          49K Nov 30 03:32 kdb5_util&lt;br /&gt;-r-xr-xr-x   1 root     sys          44K Nov 25 04:37 keyserv&lt;br /&gt;-r-xr-xr-x   1 root     bin         4.3K Nov 25 04:36 killall&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-405537395517375414?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/405537395517375414/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=405537395517375414' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/405537395517375414'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/405537395517375414'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/df.html' title='Solaris df, du, ls commands'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6086452567657869685</id><published>2009-06-10T01:49:00.002+05:30</published><updated>2009-06-10T01:50:28.821+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='AIX'/><title type='text'>AIX Command Tips</title><content type='html'>Displaying top CPU_consuming processes:&lt;br /&gt;#ps aux | head -1; ps aux | sort -rn +2 | head -10&lt;br /&gt;Displaying top 10 memory-consuming processes:&lt;br /&gt;#ps aux | head -1; ps aux | sort -rn +3 | head&lt;br /&gt;Displaying process in order of being penalized:&lt;br /&gt;#ps -eakl | head -1; ps -eakl | sort -rn +5&lt;br /&gt;Displaying process in order of priority:&lt;br /&gt;#ps -eakl | sort -n +6 | head&lt;br /&gt;Displaying process in order of nice value&lt;br /&gt;#ps -eakl | sort -n +7&lt;br /&gt;Displaying the process in order of time&lt;br /&gt;#ps vx | head -1;ps vx | grep -v PID | sort -rn +3 | head -10&lt;br /&gt;Displaying the process in order of real memory use&lt;br /&gt;#ps vx | head -1; ps vx | grep -v PID | sort -rn +6 | head -10&lt;br /&gt;Displaying the process in order of I/O&lt;br /&gt;#ps vx | head -1; ps vx | grep -v PID | sort -rn +4 | head -10&lt;br /&gt;Displaying WLM classes&lt;br /&gt;#ps -a -o pid, user, class, pcpu, pmem, args&lt;br /&gt;Determinimg process ID of wait processes:&lt;br /&gt;#ps vg | head -1; ps vg | grep -w wait&lt;br /&gt;Wait process bound to CPU&lt;br /&gt;#ps -mo THREAD -p &lt;PID&gt;&lt;br /&gt;Cpu usage with priority levels&lt;br /&gt;#topas -P&lt;br /&gt;&lt;br /&gt;#svmon -Put 10 will give the memory mapping for the&lt;br /&gt;top ten memory consuming processes.&lt;br /&gt;&lt;br /&gt;#top&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Remember, some commands needs you to be root. So, you switch to su to root.&lt;br /&gt;Two important things here -&lt;br /&gt;1. from ur profile, if u say&lt;br /&gt;$su root&lt;br /&gt;takes you to root with current shell. Means that, though u r root, u still carry ur .profile and ur env variables.&lt;br /&gt;2. if u want to have root's env variables -&lt;br /&gt;su - root or&lt;br /&gt;su root&lt;br /&gt;after getting into root&lt;br /&gt;. ./.profile&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6086452567657869685?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6086452567657869685/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6086452567657869685' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6086452567657869685'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6086452567657869685'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/aix-command-tips.html' title='AIX Command Tips'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4299303537823001228</id><published>2009-06-10T01:46:00.002+05:30</published><updated>2009-06-10T01:50:04.102+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='AIX'/><title type='text'>AIX commands</title><content type='html'>Found some AIX commands thru google. Thought to share here. Enjoy :)&lt;br /&gt;1.    Useful commands&lt;br /&gt;Note  All AIX commands reference can be found under  &lt;br /&gt;http //www.austin.ibm.com/doc_link/en_US/a_doc_lib/aixgen/wbinfnav/CmdsRefTop.htm&lt;br /&gt;1.1    Memory&lt;br /&gt;bootinfo –r    shows how much RAM does my machine has (as root)&lt;br /&gt;lsattr –E –l sys0 –a realmem   shows how much RAM does my machine have (as non root)&lt;br /&gt;rmss -c 512&lt;br /&gt;rmss -r        sets the memory size to 512 MB&lt;br /&gt;resets the memory size to the original one&lt;br /&gt;1.2    Devices&lt;br /&gt;&lt;br /&gt;lsattr  -El  en0    displays en0 driver params&lt;br /&gt;lsattr  -El  ent0    displays ent0 HW params&lt;br /&gt;lsattr -El rmt0    displays tape params&lt;br /&gt;lscfg -vp -l rmt0    (all information about a tape drive)&lt;br /&gt;lsattr  -El  sys0    displays system type, firmware, etc  driver params&lt;br /&gt;lscfg –v    lists all system HW config (NVRAM)&lt;br /&gt;lsdev –Csscsi    list all scsi devices&lt;br /&gt;lsdev –Cspci    list all pci devices&lt;br /&gt;lsparent –Ck scsi    list all scsi adapters&lt;br /&gt;lsdevfc    list fiberchannel devices&lt;br /&gt;cfgmgr    Configures devices&lt;br /&gt;lsdev -Ccdisk     Shows all disks&lt;br /&gt;lsdev -Cctape              Shows all tapes&lt;br /&gt;cfgmgr -v -l device –v   Specifies verbose output. The cfgmgr command writes information about what it is doing to standard output.&lt;br /&gt;cfgmgr -v -l device      Name Specifies the named device to configure along with its children.&lt;br /&gt;If you only turned on a disk tower at e.g. scsi2 cfgmgr -v -l scsi2 will only configure this with detailed output.&lt;br /&gt;lsdisp    To check which graphic adapter is installed.&lt;br /&gt;lscfg -vp -l mga0     (all information about a adapter)&lt;br /&gt;lscfg -vp -l hdisk0 | grep Machine    gives info about the disk manufacture type&lt;br /&gt;lsslot -c pci    For 6F1 only !!!! Lists all slots ,voltage,boards,etc !!!!&lt;br /&gt;bootlist -m normal cd0  rmt0 hdisk0   Changes the default bootlist&lt;br /&gt;lsmcode -c    display the system firmware level and service processor&lt;br /&gt;lsmcode -r -d scraid0    display the adapter microcode levels for a RAID adapter scraid0&lt;br /&gt;lsmcode -A    display the microcode level for all supported devices&lt;br /&gt;    &lt;br /&gt;    &lt;br /&gt;1.3    System info&lt;br /&gt;&lt;br /&gt;/usr/bin/uname -m    Get machine ID&lt;br /&gt;/usr/bin/uname -M    Get platform type&lt;br /&gt;oslevel    Displays current AIX level&lt;br /&gt;oslevel -r    Displays current AIX maintenance level&lt;br /&gt;oslevel -g    List filesets at levels later than maintenance level !!!&lt;br /&gt;lsps -a    Paging space settings.&lt;br /&gt;lscfg -vp -l proc0  (1,2,3)   (all information about a processor[s])&lt;br /&gt;lscfg -vp -l mem0 |pg    (all information about memory modules installed)&lt;br /&gt;env ulimit    Environment setings - show user ulimit&lt;br /&gt;bootinfo –s hdisk0     Displays disk size&lt;br /&gt;lsattr -El sys0 -a systemid   Determines the system serial number&lt;br /&gt;lscfg –vp|grep ROM|grep -v CD  Determines the system Firmware level&lt;br /&gt;1.4    System issues&lt;br /&gt;&lt;br /&gt;TERM=vt100      -If you execute a command/application and it responds with msg&lt;br /&gt;‘ The type of your terminal is unknown to the system’,run those commands (In ‘ksh’)&lt;br /&gt;set term=vt100   -Same (In tcsh’)&lt;br /&gt;rcp -rp /dataVolumes/brisque1.1.0/jobs/flower.job sciroot@ripro3:/dataVolumes/ripro3.3.0/jobs/ -Copying a file from one Unix machine (Brisque) to another (Server) the assumption is that both machines know each other’s names (in hosts file)&lt;br /&gt;dd if=/dev/fd0 of=/temp/diskimage bs=4096 -Duplicate a diskette copy from diskette to hard drive&lt;br /&gt;dd if=/temp/diskimage of=/dev/fd0 bs=4096  -copy diskette image onto diskette&lt;br /&gt;/usr/lpp/X11/bin/xset -display unix 0 s off  -Kill display timeout&lt;br /&gt;lsfs -v jfs  -List of Filesystem items.&lt;br /&gt;lsfs -q -v jfs         -you can see also the parameter of a filesystem and thus see if e.g. /backup was or is a big_filesystem_enabled one.&lt;br /&gt;Important for the 2GB File limit.&lt;br /&gt;lsuser –f root    Shows all user parameters (max .file size,etc)&lt;br /&gt;sysdumpdev -L    Check last system dump status&lt;br /&gt;sysdumpdev -l    Check system dump device settings&lt;br /&gt;lslpp -f Upd_Timna_DTM.obj    List contents of the package&lt;br /&gt;1.5    Networking&lt;br /&gt;&lt;br /&gt;ksh&lt;br /&gt;for ENT in ` lsdev –Cs pci|grep ent | awk '{ print $1 }'|cut –c 1,2,4 `;do&lt;br /&gt;    mktcpip –S $ENT&lt;br /&gt;done&lt;br /&gt;exit      -Shows all interfaces IP config+mask+router+DNS !&lt;br /&gt;host timna1    displays station default IP address – works ONLY in DNS environment&lt;br /&gt;ifconfig en0    displays en0 driver params&lt;br /&gt;netstat  -i    displays network interfaces setting&lt;br /&gt;mktcpip -S en0    #host:addr:mask:_rawname:nameserv:domain:gateway:type:start&lt;br /&gt;syslab18:192.9.100.1:255.255.255.0:en0:10.4.2.12:csil.creoscitex.com:10.4.30.1:N/A:no&lt;br /&gt;GREAT TCPIP info in one command !!!&lt;br /&gt;showmount –e    displays all exported volumes&lt;br /&gt;showmount -a    show who's got my filesystemsses mounted over IP !&lt;br /&gt;lssrc –g tcpip    displays all IP oriented processes status&lt;br /&gt;entstat -drt ent0 |grep –i error    display any communication errors on etn0&lt;br /&gt;entstat -r    Resets all the statistics back to their initial values.&lt;br /&gt;arp -a    shows a local arp cache&lt;br /&gt;cd /usr/local/es/;res    restarts appletalk&lt;br /&gt;netstat  -ptcp    shows IP statistics&lt;br /&gt;netstat  -pudp    shows UDP statistics&lt;br /&gt;netstat  -c&lt;br /&gt;         -s&lt;br /&gt;         -m    client only;&lt;br /&gt;server only&lt;br /&gt;NFS mount&lt;br /&gt;netstat -I en0 10    Trace en0 every 10 seconds&lt;br /&gt;netstat -rn    Display routing info with IP address (10.4.27.182)&lt;br /&gt;netstat -in    Shows the state of all configured interfaces&lt;br /&gt;netstat -r    Display routing info with full hostnames (timna2.csil.creoscitex)&lt;br /&gt;    nfsstat  –z      ;to    reset NFS stats without reboot&lt;br /&gt;cat /etc/resolv.conf    Check DNS settings&lt;br /&gt;stopsrc –g NFS     To stop NFS services on a client&lt;br /&gt;startsrc –g NFS     To start NFS services on a client&lt;br /&gt;traceroute 149.115.39.1    Trace all hobs (interconnections=routers) to the destination  IP&lt;br /&gt;netpmon -o netpmon.out&lt;br /&gt;trcstop    Traces all network processes activity into a logfile. Must be preceede by a trcstop command !&lt;br /&gt;nslookup hostname    Shows the DNS server name and address&lt;br /&gt;ping -R -c 1 bnc2    Ping with displaying the routing info&lt;br /&gt;namerslv -s | grep domain | awk '{ print $2 }'    Displays a fully qualified domain name of a host&lt;br /&gt;rup    Shows the status of a remote host on the local network&lt;br /&gt;nmonnfs    Traces all NFS processes activity&lt;br /&gt;mount hostname:/filesystem /mount-point    Mount an NFS filesystem&lt;br /&gt;mknfsexp -d /directory     Creates an NFS export directory&lt;br /&gt;mknfsmnt                            Creates an NFS mount directory&lt;br /&gt;rmnfs                               Stops and un-configures NFS services&lt;br /&gt;mknfs                               Configures and starts NFS services&lt;br /&gt;exportfs -u (filesystem)            Un-exports a filesystem&lt;br /&gt;exportfs                            Lists all exported filesystems&lt;br /&gt;exportfs -a                        Exports all fs's in /etc/exports file&lt;br /&gt;1.6    Disks&lt;br /&gt;&lt;br /&gt;synclvodm -vP svg3    synchronizes ODM and the disk VG info.&lt;br /&gt;redefinevg svg3    Redfined VG definition in ODM&lt;br /&gt;lqueryvg -p hdisk0 –Avt  -reads logical volumes info from disk&lt;br /&gt;bootinfo -s hdiskx    Shows Megabytes available even if no volume group is assigned.&lt;br /&gt;lspv -p  hdiskx     (PP's used, location on disk, mount point)&lt;br /&gt;lscfg -vp -l hdiskx      (all information about a disk/raid)&lt;br /&gt;1.7    Filesystem&lt;br /&gt;&lt;br /&gt;chfs -a size=+200000 /var    increases /var FS by 100MB&lt;br /&gt;du -sk /john          shows directory used space in kb !!!!&lt;br /&gt;mount all    mounts all FS&lt;br /&gt;umount /dataVolumes/rtest9.1.0    unmounts a FS&lt;br /&gt;fuser -k /dev/cd0    Releases a CD that will not unmount !&lt;br /&gt;fuser –c /dataVolumes/rtest9.1.0  -Find out which process_id lock the FS&lt;br /&gt;istat &lt;filename&gt;    Shows when the file was last created/modified/accessed !!!!&lt;br /&gt;1.8    System monitoring&lt;br /&gt;&lt;br /&gt;istat &lt;filename&gt;    Shows create/modify/access file info&lt;br /&gt;alog -o -t boot | more    displays system boot log&lt;br /&gt;w    Lists login users and their programs.&lt;br /&gt;who    Identifies the users currently logged in&lt;br /&gt;/usr/local/es/swho     Identifies the Ethershare users currently logged in&lt;br /&gt;last  |more    shows last logins&lt;br /&gt;last –20    Shows recent 20 lines&lt;br /&gt;last root    Shows username ‘root’ login/logout record&lt;br /&gt;last ftp     Shows all FTP session in the record&lt;br /&gt;mount    shows all mounted filesystems (nfs+local)&lt;br /&gt;ps -ef    show all running processes&lt;br /&gt;ps -ef |grep Scitex     show all scitex running processes&lt;br /&gt;du -ak /scitex|sort -n -r|head –10  -Display 10 biggest directories on the volume by size&lt;br /&gt;find /scitex -xdev -size +2048 -ls|sort -rn +6|head –10  -to find 10 top files in the root (/) directory larger than 1 MB.”-xdev” helps searching ONLY in “/” !!!!!!!!!&lt;br /&gt;history    Last commands run on the system by this user&lt;br /&gt;alog -ot boot    Lists a log of all boot operations&lt;br /&gt;grep TX /etc/environment    Verify daylight settings&lt;br /&gt;1.9    Performance issues&lt;br /&gt;&lt;br /&gt;nmon    a nice monitor - runs only on AIX5 and up&lt;br /&gt;topas    a nice monitor - runs only on AIX 4.3.3 and up&lt;br /&gt;monitor -top 10 -s 2    monitors system 10  top processes with 2 seconds&lt;br /&gt;iostat 2    displays disks activity every 2 seconds refresh interval&lt;br /&gt;iostat –a 2            AIX5 ONLY !!!!&lt;br /&gt;displays disks and ADAPTER !!!! activity every 2 seconds refresh interval&lt;br /&gt;vmstat 2    ;monitors virtual memory statistics every 2 seconds (see appendix A)&lt;br /&gt;sar –P ALL 2 2    Show all CPU’s activity on an SMP machine&lt;br /&gt;svmon –i 2    Monitors real and virtual memory&lt;br /&gt;ps auxw | sort –r +3 |head –10  -Shows top 10 memory usage by process&lt;br /&gt;ps auxw | sort –r +2 |head –10  -Shows top 10 CPU usage by process&lt;br /&gt;ps –auw | grep defunct    Shows zombies processes (to kill – reboot or kill the parent)&lt;br /&gt;filemon –O all –o filemon.out ; find / -name core ; trcstop    Traces FS,LV,disks,files activityof a “find” command into a logfile (filemon.out). Must be preceded by a trcstop command.&lt;br /&gt;tprof –x find / -name core ; trcstop    Traces CPU activityof a “find” command Severall logfile are created. Must be preceded by a trcstop command.&lt;br /&gt;tprof -ske -x "sleep 30"    -Trace CPU activity for next 30 seconds.Results in file sleep.tprof&lt;br /&gt;&lt;br /&gt;lvmstat –ev svg1&lt;br /&gt;lvmstat –v svg1 2    AIX5 ONLY !!!!&lt;br /&gt;enable gathering the VG statistics&lt;br /&gt;Display VG logical volumes statistics every 2 seconds&lt;br /&gt;1.10    Remote issues (working over the modem)&lt;br /&gt;&lt;br /&gt;pdelay tty0; pdisable tty0 &gt;/dev/null ;penable tty0  &lt;br /&gt;-Resets tty0&lt;br /&gt;stty erase '^?'    Makes bakespace to work&lt;br /&gt;/scitex/version/utils/modem/kermit -l /dev/ttyx –c atdt {phone #}     Use Unix to Dail-out  (for any reason) ttyx is the serial port the cable is connected&lt;br /&gt;/scitex/version/utils/modem/kermit -s /u/d0/ripro_messages -i    Sends a file to a remote desktop in binary mode&lt;br /&gt;/scitex/version/utils/modem/kermit –r&lt;br /&gt;-Receives a file to from remote desktop&lt;br /&gt;1.11    Browsing errlog with errpt&lt;br /&gt;&lt;br /&gt;errpt -a  -s 0604090601  -e 0605090901    browse the errlog in  detail for all errors within a timeframe&lt;br /&gt;errpt -a  -N SYSPROC |more&lt;br /&gt;errpt -a  -N SYSPROC  &gt; /tmp/err.log    Browse the errlog for the SYSPROC resource, can be into the file&lt;br /&gt;errpt -j 5DFED6F1   -Browse the errlog by the identifier&lt;br /&gt;errpt –A    -AIX5 ONLY !!!! Shows less detailes then errpt -a&lt;br /&gt;errpt –D    -AIX5 ONLY !!!! eliminates double entries&lt;br /&gt;1.12    Security issues&lt;br /&gt;&lt;br /&gt;chmod -s Filename    Remove Sticky Bit to a file or directory&lt;br /&gt;&lt;br /&gt;chmod +r+w+x+t Filename     Add Read+Write+Execute+Temp mode to a file or directory.&lt;br /&gt;This is a ‘blanket’ change for all owner, user &amp; group.&lt;br /&gt;Numeric Access Modes  &lt;br /&gt;0 (---) - no access&lt;br /&gt;1 (--x) - execute permissions; search permissions for directories&lt;br /&gt;2 (-w-) - write access&lt;br /&gt;3 (-wx) - execute/search permission and write access&lt;br /&gt;4 (r--) - read access&lt;br /&gt;5 (r-x) - execute/search permission and read access&lt;br /&gt;6 (rw-) - read and write access&lt;br /&gt;7 (rwx) - execute/search permission and read and write access&lt;br /&gt;mkpasswd -f    rebuild the /etc/passwd indexes in case of suspected corruption&lt;br /&gt;1.13    Miscellaneous&lt;br /&gt;ksh&lt;br /&gt;find / -type f|xargs grep "10.4.27.181" 2&gt; /dev/null&lt;br /&gt;-Find all files containing my IP address&lt;br /&gt;compress -c file &gt; file.Z    Compresses the files while keeps the original&lt;br /&gt;whereis  &lt;command-ame&gt;    Returms full path of program&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4299303537823001228?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4299303537823001228/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4299303537823001228' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4299303537823001228'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4299303537823001228'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/06/aix-commands.html' title='AIX commands'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7932648079973566809</id><published>2009-05-26T20:56:00.003+05:30</published><updated>2009-05-26T21:01:06.697+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>How to reload .profile</title><content type='html'>You made a change to your .profile. How to reload your .profile?&lt;br /&gt;One way is, exit from the session, telnet or ssh again to that host. Another way is -&lt;br /&gt;After you changing the .profile, save and quit. Then at the command prompt type in this&lt;br /&gt;$. ./.profile&lt;br /&gt;&lt;br /&gt;This reloads your .profile.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7932648079973566809?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7932648079973566809/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7932648079973566809' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7932648079973566809'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7932648079973566809'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/05/how-to-load-profile.html' title='How to reload .profile'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2705992167337639325</id><published>2009-04-28T20:24:00.001+05:30</published><updated>2009-04-28T20:25:40.581+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>tar.Z file</title><content type='html'>How to extract a tar.Z file on unix box?&lt;br /&gt;This is the way&lt;br /&gt;&lt;br /&gt;zcat file.tar.Z | tar xvf -&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2705992167337639325?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2705992167337639325/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2705992167337639325' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2705992167337639325'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2705992167337639325'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/04/tarz-file.html' title='tar.Z file'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6336391753611782425</id><published>2009-03-27T19:27:00.003+05:30</published><updated>2009-03-27T19:38:28.969+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='uninstall'/><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><category scheme='http://www.blogger.com/atom/ns#' term='fixpacks'/><title type='text'>uninstall fixpacks</title><content type='html'>Someone asked me how to troubleshoot fixpack uninstallation process.&lt;br /&gt;&lt;br /&gt;Befroe going into that, read the following from UpdateInstaller README. You can find this under Update_Inst_Path/docs/raedme_updateinstaller.txt/pdf/html&lt;br /&gt;&lt;br /&gt;3.0 Uninstalling maintenance packages&lt;br /&gt;&lt;br /&gt;This topic describes how to use the Update Installer for WebSphere&lt;br /&gt;Software to uninstall interim fixes, fix packs, and refresh packs. The&lt;br /&gt;Update Installer for WebSphere Software is also known as the update&lt;br /&gt;installer program, the updateInstaller program, and the Update&lt;br /&gt;installation wizard.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Use the proper authorizations to successfully uninstall product updates.&lt;br /&gt;Use the update installer program as the root user on a Linux or UNIX&lt;br /&gt;platform, or as the administrator on a Windows platform.&lt;br /&gt;&lt;br /&gt; The Update Installer wizard is an InstallShield for Multiplatforms&lt;br /&gt;wizard that runs with either a graphical user interface or in silent&lt;br /&gt;mode with a response file.&lt;br /&gt;&lt;br /&gt;Important: See 4.3, "Known problems and workarounds for the update&lt;br /&gt;      command" for information about known problems and workarounds.&lt;br /&gt;&lt;br /&gt; The following descriptions contain reference information about&lt;br /&gt;uninstalling interim fixes, fix packs, and refresh packs on WebSphere&lt;br /&gt;Application Server products: &lt;br /&gt;&lt;br /&gt;Overview of the uninstall procedure&lt;br /&gt;         To uninstall a maintenance package: &lt;br /&gt;         1. Use the update installer to install the maintenance package,&lt;br /&gt;            which creates a backup file in the&lt;br /&gt;            app_server_root/properties/version/nif/backup directory. IBM&lt;br /&gt;            does not support user modifications to backup files.&lt;br /&gt;         2. Use the update installer program to remove the maintenance&lt;br /&gt;            package as described in this topic.&lt;br /&gt;&lt;br /&gt;Viewing the fix level of the node&lt;br /&gt;         You can use the 5.0, "versionInfo command" in the&lt;br /&gt;         app_server_root/bin directory to display the exact fix and&lt;br /&gt;         version level of the product. However, do not use the&lt;br /&gt;         versionInfo command while installing or uninstalling a&lt;br /&gt;         maintenance package.&lt;br /&gt;&lt;br /&gt; Do not launch multiple copies of the Update Installer wizard at one&lt;br /&gt;time: Concurrent launches of the update installer program are not&lt;br /&gt;supported. Performing more than one update at the same time can produce&lt;br /&gt;unpredictable results, which might include a failed or faulty&lt;br /&gt;installation.&lt;br /&gt;&lt;br /&gt; Required information&lt;br /&gt;&lt;br /&gt; The graphical interface requires the following information that you&lt;br /&gt;must supply: &lt;br /&gt;&lt;br /&gt;Table 4. Information required when uninstalling a maintenance package&lt;br /&gt;+-----------------------+----------------------+----------------------+&lt;br /&gt;| Field                 | Valid values         | Description          |&lt;br /&gt;+-----------------------+----------------------+----------------------+&lt;br /&gt;| File path of the      | Identify the         | The Update Installer |&lt;br /&gt;| installation root     | installation root    | application defaults |&lt;br /&gt;| directory of the      | directory for one of | to the last-visited  |&lt;br /&gt;| WebSphere product and | the following        | product location.    |&lt;br /&gt;| the Update Installer  | products:            |                      |&lt;br /&gt;|                       |  * IBM WebSphere     |                      |&lt;br /&gt;|                       | Application Server   |                      |&lt;br /&gt;|                       |  * IBM WebSphere     |                      |&lt;br /&gt;|                       | Application Server - |                      |&lt;br /&gt;|                       | Express              |                      |&lt;br /&gt;|                       |  * Embedded version  |                      |&lt;br /&gt;|                       | of the IBM WebSphere |                      |&lt;br /&gt;|                       | Application Server - |                      |&lt;br /&gt;|                       | Express              |                      |&lt;br /&gt;|                       |  * IBM WebSphere     |                      |&lt;br /&gt;|                       | Application Server   |                      |&lt;br /&gt;|                       | Network Deployment   |                      |&lt;br /&gt;|                       |  * IBM WebSphere     |                      |&lt;br /&gt;|                       | Extended Deployment  |                      |&lt;br /&gt;|                       |  * IBM Application   |                      |&lt;br /&gt;|                       | Client for WebSphere |                      |&lt;br /&gt;|                       | Application Server   |                      |&lt;br /&gt;|                       |  * IBM WebSphere     |                      |&lt;br /&gt;|                       | Business Integration |                      |&lt;br /&gt;|                       | Server Foundation    |                      |&lt;br /&gt;|                       |  * Web server        |                      |&lt;br /&gt;|                       | plug-ins for         |                      |&lt;br /&gt;|                       | WebSphere            |                      |&lt;br /&gt;|                       | Application Server   |                      |&lt;br /&gt;+-----------------------+----------------------+----------------------+&lt;br /&gt;| File name of the      | Select a maintenance | The default          |&lt;br /&gt;| maintenance package   | package to uninstall | maintenance package  |&lt;br /&gt;| to uninstall.         | from the             | is the package with  |&lt;br /&gt;|                       | app_server_root/prop | the latest date      |&lt;br /&gt;|                       | erties/version/      | stamp and time stamp |&lt;br /&gt;|                       | update/backup        | in the               |&lt;br /&gt;|                       | directory.           | app_server_root      |&lt;br /&gt;|                       |                      | /properties/version/ |&lt;br /&gt;|                       |                      | update/backup        |&lt;br /&gt;|                       |                      | directory.           |&lt;br /&gt;+-----------------------+----------------------+----------------------+&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;The following procedure describes how to uninstall a maintenance&lt;br /&gt;package.&lt;br /&gt;&lt;br /&gt;1. Log on to the operating system. &lt;br /&gt;&lt;br /&gt;   [Linux] In addition, verify that the umask setting is 022. To verify&lt;br /&gt;   the umask setting, issue the following command:&lt;br /&gt;&lt;br /&gt;   umask&lt;br /&gt;&lt;br /&gt;   To set the umask setting to 022, issue the following command:&lt;br /&gt;&lt;br /&gt;   umask 022&lt;br /&gt;&lt;br /&gt;2. Change directories to the updi_root directory.&lt;br /&gt;3. [Windows] Use the Windows Services panel to stop all services for&lt;br /&gt;   WebSphere Application Server processes.&lt;br /&gt;4. Stop all Java processes that use the IBM Software Developer Kit (SDK)&lt;br /&gt;   that the WebSphere Application Server product provides. &lt;br /&gt;&lt;br /&gt;   Before uninstalling interim fixes, fix packs, and refresh packs on a&lt;br /&gt;   machine, stop all Java processes on the machine that use the IBM SDK,&lt;br /&gt;   Java Technology Edition that WebSphere Application Server provides.&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;   WebSphere Application Server processes include: &lt;br /&gt;   *  Application server processes&lt;br /&gt;   *  The nodeagent process on an application server node when the node&lt;br /&gt;      is federated into a deployment manager cell&lt;br /&gt;   *  The dmgr process for the deployment manager server&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;   Stop all Java processes if necessary. If you uninstall a maintenance&lt;br /&gt;   package while a WebSphere Application Server-related Java process&lt;br /&gt;   runs, IBM does not guarantee that the product can continue to run&lt;br /&gt;   successfully, or without error.&lt;br /&gt;&lt;br /&gt;5. Use the update installer to uninstall the maintenance package. &lt;br /&gt;&lt;br /&gt;   Uninstall the interim fix on each application server node in a cell&lt;br /&gt;   before uninstalling the maintenance package from the deployment&lt;br /&gt;   manager node.&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;   Issue one of the following commands to uninstall with the graphical&lt;br /&gt;   interface: &lt;br /&gt;&lt;br /&gt;Table 5. Update installer commands for uninstalling with the graphical &lt;br /&gt;   interface&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| Command example                | Type of     | Description          |&lt;br /&gt;|                                | installatio |                      |&lt;br /&gt;|                                | n           |                      |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -W                  | Graphical   | Initializes the      |&lt;br /&gt;| update.type="uninstall"        | interface   | maintenance package  |&lt;br /&gt;|                                | mode        | field with the name  |&lt;br /&gt;|                                |             | of the maintenance   |&lt;br /&gt;|                                |             | package that was     |&lt;br /&gt;|                                |             | most recently        |&lt;br /&gt;|                                |             | installed.           |&lt;br /&gt;|                                |             | Accept all of the    |&lt;br /&gt;|                                |             | default values to    |&lt;br /&gt;|                                |             | uninstall the        |&lt;br /&gt;|                                |             | maintenance package  |&lt;br /&gt;|                                |             | with the most recent |&lt;br /&gt;|                                |             | date stamp and time  |&lt;br /&gt;|                                |             | stamp.               |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -W                  | Graphical   | Overrides the        |&lt;br /&gt;| product.location="e:           | interface   | graphical interface  |&lt;br /&gt;| \IBM\WebSphere\AppServer" -W   | mode        | with the location of |&lt;br /&gt;| update.type="uninstall"        |             | the WebSphere        |&lt;br /&gt;|                                |             | software to update.  |&lt;br /&gt;|                                |             | The default          |&lt;br /&gt;|                                |             | maintenance package  |&lt;br /&gt;|                                |             | to uninstall is the  |&lt;br /&gt;|                                |             | most recently        |&lt;br /&gt;|                                |             | installed            |&lt;br /&gt;|                                |             | maintenance package  |&lt;br /&gt;|                                |             | for that software.   |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -W                  | Graphical   | Overrides the        |&lt;br /&gt;| backup.package="PQ20029.pak"   | interface   | maintenance package  |&lt;br /&gt;| -W update.type="uninstall"     | mode        | field with the name  |&lt;br /&gt;|                                |             | of the maintenance   |&lt;br /&gt;|                                |             | package to           |&lt;br /&gt;|                                |             | uninstall.           |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -W                  | Graphical   | Overrides the        |&lt;br /&gt;| product.location="e:           | interface   | location of the      |&lt;br /&gt;| \IBM\WebSphere\AppServer" -W   | mode        | WebSphere software   |&lt;br /&gt;| backup.package="PQ20029.pak"   |             | to update and the    |&lt;br /&gt;| -W update.type="uninstall"     |             | name of the          |&lt;br /&gt;|                                |             | maintenance package  |&lt;br /&gt;|                                |             | to uninstall.        |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -options            | Graphical   | Overrides all        |&lt;br /&gt;| "responsefiles/file_name"      | interface   | default values with  |&lt;br /&gt;|                                | mode with   | values that you      |&lt;br /&gt;|                                | an options  | specified in the     |&lt;br /&gt;|                                | file        | options response     |&lt;br /&gt;|                                |             | file.                |&lt;br /&gt;|                                |             | If you omit either   |&lt;br /&gt;|                                |             | value from the       |&lt;br /&gt;|                                |             | response file, the   |&lt;br /&gt;|                                |             | default maintenance  |&lt;br /&gt;|                                |             | package is the       |&lt;br /&gt;|                                |             | installed package    |&lt;br /&gt;|                                |             | with the most recent |&lt;br /&gt;|                                |             | date stamp and time  |&lt;br /&gt;|                                |             | stamp. The default   |&lt;br /&gt;|                                |             | software is the      |&lt;br /&gt;|                                |             | software installed   |&lt;br /&gt;|                                |             | in the parent        |&lt;br /&gt;|                                |             | directory.           |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;&lt;br /&gt;    &lt;br /&gt;&lt;br /&gt;   Issue the following command to use the silent interface: &lt;br /&gt;&lt;br /&gt;Table 6. Update installer command for uninstalling in silent mode&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| Command example                | Type of     | Description          |&lt;br /&gt;|                                | installatio |                      |&lt;br /&gt;|                                | n           |                      |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;| update.bat -silent -options    | Silent mode | Overrides all        |&lt;br /&gt;| "responsefiles/file_name"      | with an     | default values with  |&lt;br /&gt;|                                | options     | values that you      |&lt;br /&gt;|                                | file        | specified in the     |&lt;br /&gt;|                                |             | options response     |&lt;br /&gt;|                                |             | file.                |&lt;br /&gt;|                                |             | Always use a         |&lt;br /&gt;|                                |             | response file that   |&lt;br /&gt;|                                |             | is based on the      |&lt;br /&gt;|                                |             | response file under  |&lt;br /&gt;|                                |             | updi_root/responsefi |&lt;br /&gt;|                                |             | les.                 |&lt;br /&gt;+--------------------------------+-------------+----------------------+&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;This procedure results in uninstalling maintenance packages to update&lt;br /&gt;WebSphere software.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;After uninstalling maintenance packages, you can continue to use the&lt;br /&gt;WebSphere software.&lt;br /&gt;&lt;br /&gt; Rolling back changes to existing profiles: Some maintenance packages&lt;br /&gt;for WebSphere Application Server products, such as Refresh Pack 2,&lt;br /&gt;update existing profiles. If you roll back a maintenance package that&lt;br /&gt;contains a profile update, also use any undo scripts provided with the&lt;br /&gt;profile update script to roll back changes to the existing profiles.&lt;br /&gt;&lt;br /&gt; The readme file for a maintenance package describes scripts that update&lt;br /&gt;and scripts that roll back profile fix levels. For example, Refresh Pack&lt;br /&gt;2 for WebSphere Application Server includes required service for the&lt;br /&gt;JDBC resource provider templates in existing profiles. See the readme&lt;br /&gt;for the profile update and undo scripts for the JDBC-related update for&lt;br /&gt;more information.&lt;br /&gt;&lt;br /&gt; Deleting profiles created by a service level that is now rolled back:&lt;br /&gt;See Profiles remain at the Version 6.0.2 level after roll back for a&lt;br /&gt;description of a limitation that requires profiles to be at the same&lt;br /&gt;service level or at a lower service level that the WebSphere Application&lt;br /&gt;Server product.&lt;br /&gt;&lt;br /&gt; For example, suppose that you install Fix Pack 1 for Version 6.1&lt;br /&gt;(Version 6.1.0.1), create a new profile, and then roll back Fix Pack 1.&lt;br /&gt;You must delete the profile that you created at the Version 6.1.0.1&lt;br /&gt;level to avoid possible problems.&lt;br /&gt;&lt;br /&gt;3.1 uninstall.txt&lt;br /&gt;&lt;br /&gt;The Update Installer for WebSphere Software can use an options response&lt;br /&gt;file to uninstall maintenance packages from a command line interface.&lt;br /&gt;&lt;br /&gt;The uninstall.txt file has one directive that identifies the backup file&lt;br /&gt;for uninstalling a service update. Comments in the file describe how to&lt;br /&gt;set the string value.&lt;br /&gt;&lt;br /&gt;The Update Installer for WebSphere Software wizard reads the options&lt;br /&gt;file to determine uninstall choices. The Update Installer uninstalls the&lt;br /&gt;maintenance package in silent mode, instead of displaying a graphical&lt;br /&gt;user interface.&lt;br /&gt;&lt;br /&gt;3.1.1 Location of the response file&lt;br /&gt;&lt;br /&gt;The sample options response file is named uninstall.txt. The file is in&lt;br /&gt;the updi_root/responsefiles directory after you unzip the Update&lt;br /&gt;Installer for WebSphere Software into the installation root directory of&lt;br /&gt;the WebSphere software product.&lt;br /&gt;&lt;br /&gt;3.1.2 Uninstalling silently&lt;br /&gt;&lt;br /&gt;The options file supplies the values to the Update installer wizard when&lt;br /&gt;uninstalling silently. The wizard reads the options file to determine&lt;br /&gt;responses and does not display the graphical user interface.&lt;br /&gt;&lt;br /&gt;The following command uses a copy of the options file named&lt;br /&gt;myresponsefile.txt to provide uninstall option responses during a silent&lt;br /&gt;uninstall:&lt;br /&gt;&lt;br /&gt;./update.sh -options "responsefiles/myresponsefile.txt" -silent&lt;br /&gt;&lt;br /&gt;If you do not use the -silent option, the wizard uses the response file&lt;br /&gt;to provide initial values for the graphical interface:&lt;br /&gt;&lt;br /&gt;./update.sh -options "responsefiles/myresponsefile.txt"&lt;br /&gt;&lt;br /&gt;3.1.3 Response file user entry validation&lt;br /&gt;&lt;br /&gt;In a silent uninstall, response file validation has been coded into the&lt;br /&gt;uninstall process. If the validation does not pass, the failure is&lt;br /&gt;recorded in the log files in the app_server_root/logs/update/tmp&lt;br /&gt;directory.&lt;br /&gt;&lt;br /&gt;Location of the maintenance package to be uninstalled&lt;br /&gt;         &lt;br /&gt;&lt;br /&gt;         Default directive setting&lt;br /&gt;                  -W backup.package=""&lt;br /&gt;&lt;br /&gt;         Valid setting&lt;br /&gt;                  You must set this directive to the location of the&lt;br /&gt;                  backup file. The backup file reverses the application&lt;br /&gt;                  of the maintenance. For example, you might specify the&lt;br /&gt;                  following location on a Linux system:&lt;br /&gt;                  /opt/properties/version/nif/backup/maintenance_package_to_uninstall&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;         Error identifiers:&lt;br /&gt;                  &lt;br /&gt;                  *  The maintenance package cannot be uninstalled.&lt;br /&gt;                     Uninstalling the maintenance would break the&lt;br /&gt;                     following superseding maintenance packages.&lt;br /&gt;                     Uninstall the superseding maintenance packages&lt;br /&gt;                     first: list_of_superseding_maintenance_packages&lt;br /&gt;                  *  This maintenance package cannot be uninstalled. The&lt;br /&gt;                     following maintenance packages are dependent on the&lt;br /&gt;                     package that you are attempting to uninstall:&lt;br /&gt;                     list_of_dependent_maintenance_packages&lt;br /&gt;                  *  This maintenance package cannot be uninstalled. The&lt;br /&gt;                     following maintenance packages are dependent on the&lt;br /&gt;                     APARs you are attempting to uninstall:&lt;br /&gt;                     list_of_dependent_maintenance_packages&lt;br /&gt;                  *  No installation backup packages are available for&lt;br /&gt;                     uninstalling maintenance.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Product location&lt;br /&gt;         &lt;br /&gt;&lt;br /&gt;         Although uninstalling maintenance from another product is&lt;br /&gt;         possible, always use the Update installer wizard from the&lt;br /&gt;         directory structure of the product that you are updating if&lt;br /&gt;         possible. Problems can occur when a mismatch between product&lt;br /&gt;         SDKs occurs, for example.&lt;br /&gt;&lt;br /&gt;          &lt;br /&gt;&lt;br /&gt;         Do not use this directive unless absolutely necessary.&lt;br /&gt;&lt;br /&gt;          &lt;br /&gt;&lt;br /&gt;         Default directive setting&lt;br /&gt;                  -W&lt;br /&gt;                  product.location="SPECIFY_PRODUCT_INSTALL_LOCATION_HERE"&lt;br /&gt;&lt;br /&gt;         Valid setting&lt;br /&gt;                  You must set this directive to the installation root&lt;br /&gt;                  directory of the alternate product. For example, you&lt;br /&gt;                  might specify the following location on a Linux&lt;br /&gt;                  system:&lt;br /&gt;                  /opt/IBM/WebSphere/AppServer2&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;         Error identifiers:&lt;br /&gt;                  &lt;br /&gt;                  *  The maintenance package cannot be uninstalled.&lt;br /&gt;                     Uninstalling the maintenance would break the&lt;br /&gt;                     following superseding maintenance packages.&lt;br /&gt;                     Uninstall the superseding maintenance packages&lt;br /&gt;                     first: list_of_superseding_maintenance_packages&lt;br /&gt;                  *  This maintenance package cannot be uninstalled. The&lt;br /&gt;                     following maintenance packages are dependent on the&lt;br /&gt;                     package that you are attempting to uninstall:&lt;br /&gt;                     list_of_dependent_maintenance_packages&lt;br /&gt;                  *  This maintenance package cannot be uninstalled. The&lt;br /&gt;                     following maintenance packages are dependent on the&lt;br /&gt;                     APARs you are attempting to uninstall:&lt;br /&gt;                     list_of_dependent_maintenance_packages&lt;br /&gt;                  *  No installation backup packages are available for&lt;br /&gt;                     uninstalling maintenance.&lt;br /&gt;                  *  &lt;br /&gt;&lt;br /&gt;3.1.4 Usage notes&lt;br /&gt;&lt;br /&gt;*  The file is not a read-only file.&lt;br /&gt;*  Edit this file directly with your flat file editor of choice, such as&lt;br /&gt;   Kate on SLES or WordPad on a Windows platform.&lt;br /&gt;*  The file must exist to perform a silent uninstall. The Update&lt;br /&gt;   installer wizard reads this file to determine uninstall parameters.&lt;br /&gt;   Provide the fully qualified file path to the backup file.&lt;br /&gt;*  Save the copy of the options file in the responsefiles directory for&lt;br /&gt;   best results.&lt;br /&gt;&lt;br /&gt;3.1.5 Example uninstall.txt file&lt;br /&gt;&lt;br /&gt;Edit the version of the file that is included in the Update Installer&lt;br /&gt;for WebSphere Software ZIP file. The following example is not guaranteed&lt;br /&gt;to be an accurate representation of the actual file. &lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;#&lt;br /&gt;# This is the silent install response file for uninstalling maintenance packages&lt;br /&gt;# using the update installer.&lt;br /&gt;# &lt;br /&gt;# A common use of an options file is to run the wizard in silent mode. This lets&lt;br /&gt;# the options file author specify wizard settings without having to run the&lt;br /&gt;# wizard in graphical or console mode. To use this options file for silent mode&lt;br /&gt;# execution, *uncomment* and modify the parameters defined within.&lt;br /&gt;#&lt;br /&gt;# Use the following command line when running the wizard from the update &lt;br /&gt;# installer directory:&lt;br /&gt;# &lt;br /&gt;#    update -options responsefiles/uninstall.txt -silent&lt;br /&gt;#&lt;br /&gt;# Please enclose all values within a single pair of double quotes.&lt;br /&gt;#&lt;br /&gt;################################################################################&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;#&lt;br /&gt;# Used to input the maintenance backup package filename to be uninstalled. &lt;br /&gt;# This is the same filename as the package that was originally installed.&lt;br /&gt;# A maintenance package can only be uninstalled if a backup package exists.&lt;br /&gt;#&lt;br /&gt;# ie. -W backup.package="PQ20029.pak"&lt;br /&gt;#&lt;br /&gt;# Note: If no package is specified, a default of the last installed maintenance &lt;br /&gt;# package will be used.&lt;br /&gt;#&lt;br /&gt;#-W backup.package=""&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;#&lt;br /&gt;# Used to modify the product install location that will be updated. &lt;br /&gt;# This value should be left commented out if the Update Installer is &lt;br /&gt;# being run from the recommended location&lt;br /&gt;#&lt;br /&gt;# ie. -W product.location="C:\Program Files\IBM\WebSphere\AppServer"&lt;br /&gt;#&lt;br /&gt;# Note: The product install location should always been specified, and it should&lt;br /&gt;# always be the full path.&lt;br /&gt;#&lt;br /&gt;-W product.location="&lt;SPECIFY_PRODUCT_INSTALL_LOCATION_HERE&gt;"&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;################################################################################&lt;br /&gt;#&lt;br /&gt;# Do not edit these values.&lt;br /&gt;#&lt;br /&gt;-W update.type="uninstall"&lt;br /&gt;&lt;br /&gt;.....................................................................&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;So, according to documentation, &lt;br /&gt;1. uninstall process requires you to log in as correct privileges.&lt;br /&gt;2. you need to make sure that you are using correct UpdateInstaller.&lt;br /&gt;3. in general, if the uninstallation fails, may mean that, installation is partial success.&lt;br /&gt;4. check the dependencies.&lt;br /&gt;5. you need to tail app_server_root/logs/update/maintenance_package.uninstall this log for any issues and act accordingly&lt;br /&gt;6. Sometimes, this could be a reason -&lt;br /&gt;(Sep 27, 2006 12:33:10 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.PopulateTitleBarAction, msg1, IBM Update Installer for WebSphere Software V6.0.2.7&lt;br /&gt;(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.PopulateUninstallMaintenancePanelAction, err, CWUPI0024E: /software/IBM/WebSphere/AppServer/updateinstaller/maintenance/6.0.2-WS-WAS-SolarisSparc-FP0000005.pak is not a valid maintenance package or may be corrupted.&lt;br /&gt;(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.SetExitCodeAction, msg1, CWUPI0000I: EXITCODE=1&lt;br /&gt;(Sep 27, 2006 12:33:11 PM), UpdateInstaller, com.ibm.ws.install.ni.ismp.actions.ISMPLogSuccessMessageAction, msg1, INSTCONFFAILED&lt;br /&gt;&lt;br /&gt;In such cases, you can manually remove the pack and update corresponding maintenance files.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6336391753611782425?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6336391753611782425/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6336391753611782425' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6336391753611782425'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6336391753611782425'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/03/uninstall-fixpacks.html' title='uninstall fixpacks'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1292986378258779997</id><published>2009-03-24T20:32:00.002+05:30</published><updated>2009-03-24T20:35:08.539+05:30</updated><title type='text'>Today's Event - Ask The Experts</title><content type='html'>FYI&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_nWTtVfnJrDY/Scj2hZz7cKI/AAAAAAAADpU/yg3HRmGdjxM/s1600-h/experts.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 375px; height: 400px;" src="http://3.bp.blogspot.com/_nWTtVfnJrDY/Scj2hZz7cKI/AAAAAAAADpU/yg3HRmGdjxM/s400/experts.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5316770413835677858" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1292986378258779997?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1292986378258779997/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1292986378258779997' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1292986378258779997'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1292986378258779997'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/03/todays-event-ask-experts.html' title='Today&apos;s Event - Ask The Experts'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://3.bp.blogspot.com/_nWTtVfnJrDY/Scj2hZz7cKI/AAAAAAAADpU/yg3HRmGdjxM/s72-c/experts.jpg' height='72' width='72'/><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2828538718336787755</id><published>2009-03-02T19:40:00.001+05:30</published><updated>2009-03-02T19:40:02.189+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><category scheme='http://www.blogger.com/atom/ns#' term='Logs'/><title type='text'>Log Rotation</title><content type='html'>What is log rotation?&lt;br /&gt;&lt;br /&gt;WebSphere Application Server process writes different logs to log different events and errors.&lt;br /&gt;They are &lt;br /&gt;1. Diagnostic Trace&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://2.bp.blogspot.com/_nWTtVfnJrDY/SZCLVpdhdZI/AAAAAAAADhE/fi8wVg524Ak/s1600-h/trace.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 320px; height: 191px;" src="http://2.bp.blogspot.com/_nWTtVfnJrDY/SZCLVpdhdZI/AAAAAAAADhE/fi8wVg524Ak/s320/trace.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5300889965438268818" /&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;You can set the max file size to say, 20MB, and when ever the file maxes out, the server rotates it taking historical number. Maximum number of Historical Files Specifies the maximum number of rolled over files to keep. If historical number is 1, means that, when trace.log maxes out, it renames the trace.log with trace_currentdate.log and keep on writing into trace.log and so on.&lt;br /&gt;&lt;br /&gt;Here is the &lt;br /&gt;${SERVER_LOG_ROOT}/trace.log&lt;br /&gt;&lt;br /&gt;2. JVM Logs&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_nWTtVfnJrDY/SZCLfOpNoUI/AAAAAAAADhM/Inks6whGuIM/s1600-h/jvm.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 284px; height: 320px;" src="http://4.bp.blogspot.com/_nWTtVfnJrDY/SZCLfOpNoUI/AAAAAAAADhM/Inks6whGuIM/s320/jvm.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5300890130038235458" /&gt;&lt;/a&gt;&lt;br /&gt;These are SystemOut.log and SystemErr.log&lt;br /&gt;You can rotate the with Size and time.&lt;br /&gt;&lt;br /&gt;3. Process Logs&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://3.bp.blogspot.com/_nWTtVfnJrDY/SZCLmdJ7YoI/AAAAAAAADhU/4YgXhbPDWqU/s1600-h/process.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 288px; height: 131px;" src="http://3.bp.blogspot.com/_nWTtVfnJrDY/SZCLmdJ7YoI/AAAAAAAADhU/4YgXhbPDWqU/s400/process.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5300890254192632450" /&gt;&lt;/a&gt;&lt;br /&gt;These are native_stdout.log and native_stderr.log&lt;br /&gt;If you verbose gc, gc information will be written into native_Stdout.log. If you dump threads on a live process, this is file which dump thread process dumps the thread information. If you have any process related errors, native_stderr.log is the location to find them. You cannot rotate these files. &lt;br /&gt;4. Service Log&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://1.bp.blogspot.com/_nWTtVfnJrDY/SZCLu1wT40I/AAAAAAAADhc/Tu3s3cfL8C4/s1600-h/service.jpg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 288px; height: 171px;" src="http://1.bp.blogspot.com/_nWTtVfnJrDY/SZCLu1wT40I/AAAAAAAADhc/Tu3s3cfL8C4/s400/service.jpg" border="0" alt=""id="BLOGGER_PHOTO_ID_5300890398235026242" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2828538718336787755?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2828538718336787755/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2828538718336787755' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2828538718336787755'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2828538718336787755'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/03/log-rotation.html' title='Log Rotation'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://2.bp.blogspot.com/_nWTtVfnJrDY/SZCLVpdhdZI/AAAAAAAADhE/fi8wVg524Ak/s72-c/trace.jpg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6678313867845350978</id><published>2009-02-28T01:00:00.000+05:30</published><updated>2009-02-28T01:00:01.220+05:30</updated><title type='text'>What's new in Version 6.1?</title><content type='html'>&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6678313867845350978?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='related' href='http://www.ibm.com/developerworks/websphere/library/techarticles/0606_petersonr/0606_petersonr.html' title='What&apos;s new in Version 6.1?'/><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6678313867845350978/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6678313867845350978' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6678313867845350978'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6678313867845350978'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/02/whats-new-in-version-61.html' title='What&apos;s new in Version 6.1?'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1129789954808679504</id><published>2009-02-27T21:01:00.001+05:30</published><updated>2009-02-27T21:02:52.011+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>httpd</title><content type='html'>httpd is the Apache HyperText Transfer Protocol (HTTP) server program. It is designed to be run as a standalone daemon process. When used like this it will create a pool of child processes or threads to handle requests.&lt;br /&gt;&lt;br /&gt;In general, httpd should not be invoked directly, but rather should be invoked via apachectl on Unix-based systems&lt;br /&gt;&lt;br /&gt;httpd [ -d serverroot ] [ -f config ] [ -C directive ] [ -c directive ] [ -D parameter ] [ -e level ] [ -E file ] [ -k start|restart|graceful|stop ] [ -R directory ] [ -h ] [ -l ] [ -L ] [ -S ] [ -t ] [ -v ] [ -V ] [ -X ]&lt;br /&gt;&lt;br /&gt;Read more about this &lt;a href="http://publib.boulder.ibm.com/httpserv/manual60/programs/httpd.html"&gt;here&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1129789954808679504?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1129789954808679504/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1129789954808679504' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1129789954808679504'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1129789954808679504'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/02/httpd.html' title='httpd'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7235020053417503064</id><published>2009-02-23T19:40:00.001+05:30</published><updated>2009-02-23T19:40:01.786+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='SSL'/><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><category scheme='http://www.blogger.com/atom/ns#' term='IHS'/><title type='text'>IKEYMAN</title><content type='html'>ikeyman is a UI tool comes with IHS/WAS with which one can create certificates, extract them, import them, export them, create self signed certificates and so on.&lt;br /&gt;&lt;br /&gt;When to use ikeyman?&lt;br /&gt;When your certificates expire, you need to have new certificates. You use ikeyman to import the new certificates&lt;br /&gt;When you want create self signed certificates. You use ikeyman.&lt;br /&gt;You have to eshtablish trust between different clients and your server. You use ikeyman.&lt;br /&gt;&lt;br /&gt;Here is a &lt;a href="http://www-01.ibm.com/support/docview.wss?uid=swg21215717"&gt;technote &lt;/a&gt;on Creating Custom Secure Socket Layer (SSL) Key Files using a CA Certificate&lt;br /&gt;&lt;br /&gt;Here is the ikeyman doc. Click &lt;a href="http://www-01.ibm.com/software/webservers/httpservers/doc/v10/ibm/9atikeyu.htm"&gt;here&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.verisign.com/support/mpki-for-ssl-support/flash/Install-SSL-Certificate-using-IBM-iKeyman.htm"&gt;Install SSL Certificate using IBM ikeyman&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7235020053417503064?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7235020053417503064/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7235020053417503064' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7235020053417503064'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7235020053417503064'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/02/ikeyman.html' title='IKEYMAN'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2554666534391578046</id><published>2009-02-18T23:56:00.002+05:30</published><updated>2009-02-19T01:09:50.774+05:30</updated><title type='text'>Virtual Box</title><content type='html'>Just to show RHEL 5.2 running as guest OS on my Windows XP thru Virtual Box hypervisor.&lt;br /&gt;&lt;object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=9,0,18,0" width="425" height="319" id="divflv"&gt;&lt;param name="movie" value="http://www.divshare.com/flash/video2?myId=6588412-bd2" /&gt;&lt;param name="allowFullScreen" value="true" /&gt;&lt;embed src="http://www.divshare.com/flash/video2?myId=6588412-bd2" width="425" height="319" name="divflv" allowfullscreen="true" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2554666534391578046?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2554666534391578046/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2554666534391578046' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2554666534391578046'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2554666534391578046'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/02/virtual-box.html' title='Virtual Box'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6053831981026566691</id><published>2009-02-16T19:40:00.001+05:30</published><updated>2009-02-16T19:40:03.792+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><title type='text'>Websphere Migration</title><content type='html'>Migration &lt;br /&gt;This term has many definitions and a broad scope. In this document, the meaning of migration is limited to the actions associated with moving Java™ 2 Enterprise Edition (J2EE™) applications (EARs) and Application Server configuration data (such as resources and security settings) from a previous version of Application Server to V6. &lt;br /&gt;&lt;br /&gt;WASPreUpgrade (tool) &lt;br /&gt;Refers to the first step of the two-step migration process. The tool associated with this step will extract information from the previous version of Application Server and store it in a backup directory. This tool can be run by itself from the command line or as part of the migration wizard. &lt;br /&gt;&lt;br /&gt;WASPostUpgrade (tool) &lt;br /&gt;Refers to the second step of the two-step migration process. The tool associated with this step will take information from a directory created by the WASPreUpgrade tool and import it into a V6 profile. This tool can be run by itself from the command line or as part of the migration wizard. &lt;br /&gt;&lt;br /&gt;Backup directory &lt;br /&gt;Refers to a directory structure created by the WASPreUpgrade tool that contains all the information necessary for migration from the previous version of Application Server. &lt;br /&gt;&lt;br /&gt;Migration wizard &lt;br /&gt;Refers to the graphical user interface (GUI) that interactively performs the migration. This GUI tool performs the WASPreUpgrade and WASPostUpgrade steps. &lt;br /&gt;&lt;br /&gt;FirstSteps (tool) &lt;br /&gt;Tool provided in V6 to simplify and organize many actions that customers may wish to perform with a newly installed system. It can be found in the firststeps directory under each profile and can be used to launch the migration wizard. &lt;br /&gt;&lt;br /&gt;Profiles &lt;br /&gt;This concept expands on the idea of "instances" in V5. It refers to the collection of all the configuration data for an Application Server in V6. Application Server V6 provides for multiple profiles with only one install of the binaries. A single profile is required as the destination for the data being migrated from a previous version. (See Installing Application Server V6.) &lt;br /&gt;&lt;br /&gt;Cell &lt;br /&gt;Refers to the collection of one or more nodes controlled by a single deployment manager. &lt;br /&gt;&lt;br /&gt;Federate or Federated &lt;br /&gt;Refers to the action of adding a node to a cell; also refers to a node that is part of a cell. This term has been expanded to also refer to a node in a multi-node V4 domain. &lt;br /&gt;&lt;br /&gt;Deployment manager profile (dmgr profile) &lt;br /&gt;This profile acts as the deployment manager, and is the destination for the migration of the V5 deployment manager, and as a new deployment manager for V4 migrations. There can be only one deployment manager profile for each cell.&lt;br /&gt;&lt;br /&gt;Standalone or Application Server profile &lt;br /&gt;Refers to a profile that is analogous to a single node install of Application Server. This type of profile is the destination for the migrations of a node either in a cell or not in a cell. &lt;br /&gt;&lt;br /&gt;Clusters &lt;br /&gt;This term replaces the idea of ServerGroups from V4. Clusters are sets of servers that are used for distributing workload within a cell. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.ibm.com/developerworks/websphere/library/techarticles/0504_chalmers/0504_chalmers.html"&gt;A quick guide for migrating to IBM WebSphere Application Server V6&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6053831981026566691?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6053831981026566691/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6053831981026566691' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6053831981026566691'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6053831981026566691'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/02/websphere-migration.html' title='Websphere Migration'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5296139894100654298</id><published>2009-02-09T12:46:00.000+05:30</published><updated>2009-02-10T00:46:39.233+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><title type='text'>security.xml file is corrupted</title><content type='html'>If security.xml file is corrupted how will restore it?&lt;br /&gt;First, what is file corruption?&lt;br /&gt;&lt;span class="mContent"&gt;&lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;Corrupted&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; files are files that suddenly become inoperable or unusable.  There are several reasons why a &lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;file&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; may become &lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;corrupted&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;.  In some cases, it is possible to recover and fix the &lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;corrupted&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; &lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;file&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;, while at other times it may be necessary to delete the &lt;span class="yellowFade"&gt;&lt;span&gt;&lt;span style="position: relative;" class="yellowFadeInnerSpan"&gt;file&lt;/span&gt;&lt;/span&gt;&lt;/span&gt; and replace it with an earlier saved version.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;What are the chances of security.xml becoming corrupted? There are chances for any config file to become corrupted.&lt;br /&gt;&lt;br /&gt;Things to understand:-&lt;br /&gt;1. How to avoid this?&lt;br /&gt;2. What to do when this happens?&lt;br /&gt;&lt;br /&gt;1. How to avoid this?&lt;br /&gt;When you plan to edit Security.xml or any configuration file, better to take a hard copy back up or run backupConfig script. Hard copy backup, cp file as security_bak.xml, then make make changes to security.&lt;br /&gt;&lt;br /&gt;2. What to do when this happens?&lt;br /&gt;Say, on 5th, Tuesday, Feb you made changes to your security, it got fat fingured or corrupted, goto your system admin, revert it back to last working copy.&lt;br /&gt;I would do like this. I would talk to my system admin and ask him to load security.xml from lastnights backup. We at our office, have nightly backups and weekly backups. We retain a months historical backups.&lt;br /&gt;&lt;br /&gt;OR - If you know your security model completely, you can manually goto security.xml file, set security to false. save and recycle your server. It sets secutiy to false means no security. Now,  set your security again.&lt;br /&gt;&lt;br /&gt;Again, When will you modify security.xml? This is not an every day task. You will edit your security at the time of setting up new installation, or when you have a change in LDAP info or, when there is a need to add a new user or group etc. So, its always a good practice to take security.xml backup before you modify it.&lt;br /&gt;&lt;br /&gt;There is even a better way to do this, specially in Production Environments. Let your versioning system take care of it. Meaning, check in your configuration into a version control system. If you make any change, it can be tracked.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5296139894100654298?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5296139894100654298/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5296139894100654298' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5296139894100654298'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5296139894100654298'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/01/securityxml-file-is-corrupted.html' title='security.xml file is corrupted'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-3351238638392988391</id><published>2009-02-08T19:25:00.000+05:30</published><updated>2009-02-08T08:58:53.602+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><title type='text'>Backups in WebSphere</title><content type='html'>How we take backups in WebSphere?&lt;br /&gt;To know this one should understand what is backup?, how it can be done?, what to backup?, when to backup?.&lt;br /&gt;What is backup? A Backup is a routine runs everyday/week/month per your schedule, takes a copy of the file system or Snapshot of entire OS and so on.&lt;br /&gt;How it can be done?&lt;br /&gt;This is done a special group called System Administrators. They may use a  specific software and schedule backup task, like Veritas NetBackup. When will the scheduler runs? Depends on the enterprise backup policy. It can a nightly backups, or over the weekend and so on.&lt;br /&gt;Backup in view of WebSphere - One can backup WebSphere Configuration time to time or as and when required.&lt;br /&gt;How to take Backup in WebSphere?&lt;br /&gt;WebSphere supplies a command called &lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.multiplatform.doc/info/ae/ae/rxml_backupconfig.html"&gt;backupConfig&lt;/a&gt;&lt;br /&gt;backupConfig.sh backup_file [options]where backup_file specifies the file to which the backup is written. If you do not specify one, a unique name is generated.&lt;br /&gt;Options&lt;br /&gt;-nostop -quiet -logfile logfile_name -profileName profile_name -replacelog -trace -username user_name -password password -help -?&lt;br /&gt;&lt;br /&gt;nostop &lt;br /&gt;Tells the backupConfig command not to stop the servers before backing up the configuration &lt;br /&gt;-quiet &lt;br /&gt;Suppresses the progress information that the backupConfig command prints in normal mode &lt;br /&gt;-logfile file_name &lt;br /&gt;Specifies the location of the log file to which trace information is written&lt;br /&gt;By default, the log file is named backupConfig.log and is created in the logs directory.&lt;br /&gt;&lt;br /&gt;-profileName profile_name  &lt;br /&gt;Defines the profile of the application server process in a multi-profile installation&lt;br /&gt;The -profileName option is not required for running in a single-profile environment. The default for this option is the default profile.&lt;br /&gt;&lt;br /&gt;-replacelog &lt;br /&gt;Replaces the log file instead of appending to the current log &lt;br /&gt;-trace &lt;br /&gt;Generates trace information into the log file for debugging purposes &lt;br /&gt;-username user_name &lt;br /&gt;Specifies the user name for authentication if security is enabled in the server; acts the same as the -user option &lt;br /&gt;-user user_name &lt;br /&gt;Specifies the user name for authentication if security is enabled in the server; acts the same as the -username option &lt;br /&gt;-password password &lt;br /&gt;Specifies the password for authentication if security is enabled in the server &lt;br /&gt;-help &lt;br /&gt;Prints a usage statement &lt;br /&gt;-? &lt;br /&gt;Prints a usage statement&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-3351238638392988391?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/3351238638392988391/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=3351238638392988391' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3351238638392988391'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/3351238638392988391'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/01/backups-in-websphere.html' title='Backups in WebSphere'/><author><name>WebSphere</name><uri>http://www.blogger.com/profile/00659452307672147319</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2333871503942246820</id><published>2009-01-31T02:14:00.000+05:30</published><updated>2009-01-31T02:14:00.281+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Workplace'/><category scheme='http://www.blogger.com/atom/ns#' term='AE'/><category scheme='http://www.blogger.com/atom/ns#' term='FileNet'/><title type='text'>Credentials Exception</title><content type='html'>This is a very common error you get when you access Workplace. &lt;br /&gt;&lt;br /&gt;Description &lt;br /&gt;&lt;br /&gt;Error Message:&lt;br /&gt;Credentials Exception &lt;br /&gt;&lt;br /&gt;Exception Class:&lt;br /&gt;com.filenet.wcm.toolkit.util.WcmException &lt;br /&gt;&lt;br /&gt;There could be more than one reason for getting this exception. If you see something like this in the Error Stack Trace - &lt;br /&gt;&lt;br /&gt;"Caused by: org.omg.CORBA.COMM_FAILURE: CAUGHT_EXCEPTION_WHILE_CONFIGURING_SSL_CLIENT_SOCKET: JSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: com.ibm.jsse2.util.h: No trusted certificate found vmcid: 0x49421000 minor code: 70 completed: No " which leads to the hand shake failure between Content Engine and Application Engine. &lt;br /&gt;&lt;br /&gt;Lets first understand the architecture. &lt;br /&gt;&lt;br /&gt;Application Engine comes with a J2EE application called Workplace to be hosted on an application server say, WebSphere. Workplace is a fontend window for your FileNet System, where you can have process configuration, workflow management, initiating workflows, search designs and so on. So, Workplace alone is a J2EE app unless you configure and point to your process engine, content engine and so on. &lt;br /&gt;&lt;br /&gt;In FileNet version 4.0, Content Engine is also a J2EE application. So this has to be deployed on, say, WebSphere. &lt;br /&gt;&lt;br /&gt;The Workplace's authentication is carried out through Content Engine. Meaning, When you access workplace, workplace throws you a page to authenticate, the credentials what you give are first passed to Content Engine, and the Content Engine, sends a query to LDAP and so on. As soon as it gets your Authentication and Authorization, it passes response to workplace. And workplace knows what to show you with your set of credentials. &lt;br /&gt;&lt;br /&gt;So, AE communicates with CE on a specific port and with specific set of parameters. It needs Security check. If you do not implement SSL Handshake between your AE and CE this is the thing whats going to happen: AE takes your login and password from the browser, tries to pass the info to CE, CE App Server checks the incoming request for its Cert info. If it is a trusted request, it allows the request to reach its service methods, otherwise, it rejects the request, and your FileNet API, com.filenet.wcm.toolkit.util.WcmException catches that error and throws this Error Message "Credentials Exception". &lt;br /&gt;&lt;br /&gt;How to deal with it? &lt;br /&gt;&lt;br /&gt;Keeping FileNEt 4, WAS 6.1.xx versions in mind - &lt;br /&gt;&lt;br /&gt;You need to make sure SSL Fruitful Handshake to happen between AE and Ce, meaning you need to make sure CE trusts AE to access its resources. &lt;br /&gt;&lt;br /&gt;In WAS 6.1.xx, Trust stores are no more in WAS_PROFILE_HOME/etc but in WAS_PROFILE_HOME/config/cells/cellname/nodes/nodename. The Default trust store is trust.p12 &lt;br /&gt;&lt;br /&gt;So you need to open this guy, export as a crm file. Do this on AE and CE too. &lt;br /&gt;&lt;br /&gt;Meaning, Add CE arm file to AE Trust Store and Add AE arm file to CE Trust store. &lt;br /&gt;&lt;br /&gt;You can bounce all the services and recycle temp.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2333871503942246820?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2333871503942246820/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2333871503942246820' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2333871503942246820'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2333871503942246820'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/01/credentials-exception.html' title='Credentials Exception'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7935577127272027206</id><published>2009-01-30T02:00:00.002+05:30</published><updated>2009-01-30T02:03:23.126+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='CM'/><category scheme='http://www.blogger.com/atom/ns#' term='FileNet'/><title type='text'>Component Manager Error</title><content type='html'>The User ID What I used, in configuring the Component Manager is on the LDAP Tree and belongs to CEADMIN group.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://4.bp.blogspot.com/_nWTtVfnJrDY/SYISdSB6P8I/AAAAAAAADgA/7djI_xlBur0/s1600-h/compmgr.jpeg"&gt;&lt;img style="display:block; margin:0px auto 10px; text-align:center;cursor:pointer; cursor:hand;width: 400px; height: 300px;" src="http://4.bp.blogspot.com/_nWTtVfnJrDY/SYISdSB6P8I/AAAAAAAADgA/7djI_xlBur0/s400/compmgr.jpeg" border="0" alt=""id="BLOGGER_PHOTO_ID_5296816406006480834" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7935577127272027206?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7935577127272027206/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7935577127272027206' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7935577127272027206'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7935577127272027206'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/01/component-manager-error.html' title='Component Manager Error'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/_nWTtVfnJrDY/SYISdSB6P8I/AAAAAAAADgA/7djI_xlBur0/s72-c/compmgr.jpeg' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-2658526750357915875</id><published>2009-01-24T00:43:00.002+05:30</published><updated>2009-01-24T00:46:32.661+05:30</updated><title type='text'>My WebSphere Podcasts</title><content type='html'>Apple has approved my WebSphere Podcasts. To subscribe to my podcasts, one can click on this &lt;a href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewPodcast?id=303248558 "&gt;&lt;strong&gt;url&lt;/strong&gt;&lt;/a&gt;. This looks for itunes on your machine. You can download itunes from apple free.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-2658526750357915875?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/2658526750357915875/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=2658526750357915875' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2658526750357915875'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/2658526750357915875'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2009/01/my-websphere-podcasts.html' title='My WebSphere Podcasts'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-942725313880541674</id><published>2008-12-23T01:34:00.002+05:30</published><updated>2008-12-23T01:43:37.918+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><title type='text'>activity.log</title><content type='html'>The application server creates the activity.log file from the activity of the various WebSphere Application Server components. you cannot read this log with a text reader. You ca use this script called, showlog under appserver root.&lt;br /&gt;Ex.,&lt;br /&gt;./WAS_INST_ROOT/bin/showlog PATH_TOACTIVITY_LOG/activity.log&lt;br /&gt;like this&lt;br /&gt;websphe: /software/opt/IBM/WebSphere/AppServer/bin&lt;br /&gt;$ ./showlog ../profiles/AppSrv*/logs/activity.log&lt;br /&gt;This displays ur activity log something like this, just as a sample:&lt;br /&gt;ExtendedMessage:&lt;br /&gt;---------------------------------------------------------------&lt;br /&gt;ComponentId: Application Server&lt;br /&gt;ProcessId: 18124&lt;br /&gt;ThreadId: 0000005d&lt;br /&gt;ThreadName: WebContainer : 4&lt;br /&gt;SourceId: com.ibm.ws.webcontainer.srt.SRTServletResponse&lt;br /&gt;ClassName:&lt;br /&gt;MethodName:&lt;br /&gt;Manufacturer: IBM&lt;br /&gt;Product: WebSphere&lt;br /&gt;Version: Platform 6.0 [BASE 6.0.2.0 o0526.07]&lt;br /&gt;ServerName: Node01Cell\Node01\server1&lt;br /&gt;TimeStamp: 2008-12-22 12:27:17.175000000&lt;br /&gt;UnitOfWork:&lt;br /&gt;Severity: 2&lt;br /&gt;Category: WARNING&lt;br /&gt;PrimaryMessage: WARNING: Cannot set status. Response already committed&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-942725313880541674?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/942725313880541674/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=942725313880541674' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/942725313880541674'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/942725313880541674'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/12/activitylog.html' title='activity.log'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-8758920027439907142</id><published>2008-12-02T23:59:00.003+05:30</published><updated>2008-12-06T00:03:09.372+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><title type='text'>How can we configure Remote Plugin?</title><content type='html'>This is the procedure&lt;br /&gt;Machine A: WAS&lt;br /&gt;Machine B: IHS&lt;br /&gt;Thumb Rule: Install Plugins on IHS Machine and propagrate them to WAS.&lt;br /&gt;Procedure&lt;br /&gt;Machine A : Install WAS.&lt;br /&gt;Machine B: Install IHS&lt;br /&gt;Machine B : Install Plugins: In the installation process, you have to select remote WAS, and name for ur webserverconfig, say webserver1. After installation, in the IHS_INST/conf/httpd.conf check for IBM Module entry and Plugin installation paths&lt;br /&gt;Goto the plugin installation path/bin&lt;br /&gt;Check for configurewebserver1.sh/bat&lt;br /&gt;Now,&lt;br /&gt;Copy that file, configurewebserver1.sh/bat to WAS box, that is Machine A. The file contains this info.&lt;br /&gt;./wsadmin.sh -f configureWebserverDefinition.jacl webserver1 IHS '/software/IBM/IHS' '&lt;br /&gt;/software/IBM/IHS/conf/httpd.conf' 7700 MAP_ALL '/software/IBM/Plugins' unmanage&lt;br /&gt;d webserver1 hostname solaris&lt;br /&gt;(This is an example, 7700 is port number.)&lt;br /&gt;If you already have enabled global security on WAS, you need to add -username adminusername and -password hispassword at the end of the above script.&lt;br /&gt;&lt;br /&gt;Then run the script.&lt;br /&gt;&lt;br /&gt;Which creates a WebServer definition in the AppServer.&lt;br /&gt;&lt;br /&gt;U need to configure WAS to remote admin WebServer.&lt;br /&gt;&lt;object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" codebase="http://fpdownload.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=8,0,0,0" width="335" height="85" id="divplaylist"&gt;&lt;param name="movie" value="http://www.divshare.com/flash/playlist?myId=6010213-640" /&gt;&lt;embed src="http://www.divshare.com/flash/playlist?myId=6010213-640" width="335" height="85" name="divplaylist" type="application/x-shockwave-flash" pluginspage="http://www.macromedia.com/go/getflashplayer"&gt;&lt;/embed&gt;&lt;/object&gt;&lt;br /&gt;Click &lt;a href="http://www.divshare.com/download/6010213-640"&gt;Here&lt;/a&gt; to Download&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-8758920027439907142?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/8758920027439907142/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=8758920027439907142' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8758920027439907142'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/8758920027439907142'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/12/how-can-we-configure-remote-plugin.html' title='How can we configure Remote Plugin?'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-4292721190431720838</id><published>2008-12-02T23:41:00.003+05:30</published><updated>2008-12-02T23:45:41.477+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><category scheme='http://www.blogger.com/atom/ns#' term='faq'/><title type='text'>configuration change when fedarated</title><content type='html'>1. what are all configuration files got changed when we add a node into cell?&lt;br /&gt;&lt;br /&gt;When you federate, dmgr takes control of ur federated node. so, it copys DMGRCell into ur node, and pushes ur node info into dmgrcell.&lt;br /&gt;&lt;br /&gt;2. What are server.xml and serverindex.xml?&lt;br /&gt;&lt;br /&gt;Server.xml is an xml file :). Which contains the information needed for your JVM, like, ur jvm name, clustername, services, properties, threadpoolsettings, process definitions, components and so on&lt;br /&gt;serverindex.xml :&lt;br /&gt;This is the file whoch holds : host name info, deployed application info, ur app server ports info, etc&lt;br /&gt;&lt;br /&gt;3. what is FFDC?&lt;br /&gt;&lt;br /&gt;FFDC - First Failure Data Capture.&lt;br /&gt;WebSphere Application Server V6 includes a feature called First Failure Data&lt;br /&gt;Capture (FFDC). The FFDC feature runs in the background and collects events&lt;br /&gt;and errors that occur during WebSphere Application Server runtime. The&lt;br /&gt;information that it collects are written to log files in the&lt;br /&gt;&lt;WAS_install_root&gt;/profiles/&lt;profile&gt;/logs/ffdc directory.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-4292721190431720838?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/4292721190431720838/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=4292721190431720838' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4292721190431720838'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/4292721190431720838'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/12/configuration-change-when-fedarated.html' title='configuration change when fedarated'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>4</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5774370051385413936</id><published>2008-11-10T20:44:00.001+05:30</published><updated>2008-11-10T20:51:33.753+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><title type='text'>Maintenance Packs Info</title><content type='html'>How to check for interim packs, APARs covered in installated Fix Packs or Refresh Packs?&lt;br /&gt;WAS_INST_ROOT/properties/version/update/backup&lt;br /&gt;This the place holder for all the fix packs, interim fix packs if u have install them seperately, refresh packs and so on.&lt;br /&gt;Here you see the following files along with .pak files&lt;br /&gt;update.status.xml&lt;br /&gt;maintenanceStack.xml&lt;br /&gt;maintenanceHistory.xml&lt;br /&gt;If you are looking for a specific APAR, The best way to do it is&lt;br /&gt;grep for that apar in this file maintenanceHistory.xml.&lt;br /&gt;maintenanceStack.xml lists all the apars.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5774370051385413936?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5774370051385413936/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5774370051385413936' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5774370051385413936'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5774370051385413936'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/11/maintenance-packs-info.html' title='Maintenance Packs Info'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6285665131644857953</id><published>2008-09-26T20:56:00.002+05:30</published><updated>2008-09-26T21:25:12.656+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><title type='text'>truss</title><content type='html'>truss is a command to trace system calls and signals&lt;br /&gt;&lt;br /&gt;SYNOPSIS&lt;br /&gt;truss [-fcaeildDE] [- [tTvx] [!] syscall ,...]&lt;br /&gt;      [- [sS] [!] signal ,...] [- [mM] [!] fault ,...]&lt;br /&gt;      [- [rw] [!] fd ,...]&lt;br /&gt;      [- [uU] [!] lib ,... : [:] [!] func ,...]&lt;br /&gt;      [-o outfile] command | -p pid[/lwps]...&lt;br /&gt;&lt;br /&gt;DESCRIPTION&lt;br /&gt;The truss utility executes the specified  command  and  produces  a  trace ofthe system calls it performs, the signals it receives, and the machine faults it incurs. Each line  of the  trace output reports either the fault or signal name or  the system call name with its arguments and return value(s).&lt;br /&gt;System call arguments are displayed symbolically when possible using defines from relevant system headers. For any path name  pointer  argument, the pointed-to string is displayed.&lt;br /&gt;Error returns  are  reported  using  the  error  code  names described in intro(3). If, in the case of an error, the kernel  reports  a  missing  privilege,  a  privilege  name  as described in privileges(5) is reported in square brackets ([&lt;br /&gt;]) after the error code name.&lt;br /&gt;Optionally (see  the  -u  option),  truss  also  produce  an entry/exit  trace  of  user-level function calls executed by the traced process, indented to indicate nesting.&lt;br /&gt;&lt;br /&gt;Why to know about truss?&lt;br /&gt;&lt;br /&gt;In the day today admin job, you may want to see what a process is doing? or you may want to check an installation process. Or ur installation process is failing, you want check whats going on. You use truss in such conditions.&lt;br /&gt;&lt;br /&gt;Some examples:&lt;br /&gt;&lt;br /&gt;truss -p pid &lt;br /&gt;gives you that specific pids systemcalls &lt;br /&gt;$ truss -p 883&lt;br /&gt;/14:    lwp_cond_wait(0x0193BFF8, 0x0193BFE0, 0xD287F710, 0) Err#62 ETIME&lt;br /&gt;/14:    lwp_cond_broadcast(0x016BA688)                  = 0&lt;br /&gt;/14:    lwp_cond_broadcast(0x01299A98)                  = 0&lt;br /&gt;/205:   lwp_cond_wait(0x016BA688, 0x016BA670, 0xD187F748, 0) = 0&lt;br /&gt;/205:   lwp_cond_broadcast(0x0193BFF8)                  = 0&lt;br /&gt;/14:    lwp_cond_wait(0x0193BFF8, 0x0193BFE0, 0x00000000, 0) = 0&lt;br /&gt;/205:   lwp_mutex_wakeup(0x0193BFE0)                    = 0&lt;br /&gt;/14:    lwp_mutex_timedlock(0x0193BFE0, 0x00000000)     = 0&lt;br /&gt;/205:   lwp_mutex_wakeup(0x000F8AD8)                    = 0&lt;br /&gt;/14:    lwp_mutex_timedlock(0x000F8AD8, 0x00000000)     = 0&lt;br /&gt;/14:    lwp_cond_broadcast(0x000D2E80)                  = 0&lt;br /&gt;/205:   stat64("/software/IBM/WebSphere/AppServer/profiles/AppSrv01/installedApps/hornblowerNode01Cell/FRPApp.ear/FRPApp-WebModule.war/WEB-INF/classes/us/ny/state/oag/model/OrganizationDetail.class", 0xD187F628) = 0&lt;br /&gt;&lt;br /&gt;883 is a WebSphere pid.&lt;br /&gt;&lt;br /&gt;$ truss -o example.out -p 883&lt;br /&gt;truss traces pid 883 and outputs to example.out&lt;br /&gt;&lt;br /&gt;$truss -o example.out install.sh&lt;br /&gt;install.sh is an installer of a software. truss traces the installation process's system calls and outputs to example.out&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6285665131644857953?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6285665131644857953/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6285665131644857953' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6285665131644857953'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6285665131644857953'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/09/truss.html' title='truss'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-1392007074922087050</id><published>2008-09-18T19:53:00.003+05:30</published><updated>2008-09-18T20:19:09.012+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>find, grep</title><content type='html'>&lt;strong&gt;find&lt;/strong&gt;:&lt;br /&gt;NAME    &lt;br /&gt;      find - find files&lt;br /&gt;SYNOPSIS&lt;br /&gt;     /usr/bin/find  [-H   -L] path... expression&lt;br /&gt;     /usr/xpg4/bin/find  [-H   -L] path... expression&lt;br /&gt;DESCRIPTION&lt;br /&gt;     The find utility recursively descends the directory  hierar-     chy for each path seeking files that match a Boolean expres-     sion written in the primaries given below.&lt;br /&gt;     find is able to  descend  to  arbitrary  depths  in  a  file     hierarchy  and  does not fail due to path length limitations     (unless a path operand specified by the application  exceeds     PATH_MAX requirements).&lt;br /&gt;&lt;br /&gt;Examples :&lt;br /&gt;find . -name "bla.log" -print&lt;br /&gt;This command will search in the current directory and all sub directories for a file named bla.log.&lt;br /&gt;Note: The -print option will print out the path of any file that is found with that name. In general -print wil print out the path of any file that meets the find criteria.&lt;br /&gt;&lt;br /&gt;find /usr/src -not \( -name "*,v" -o -name ".*,v" \) '{}' \; -print&lt;br /&gt;This command will search in the /usr/src directory and all sub directories. All files that are of the form '*,v' and '.*,v' are excluded. Important arguments to note are:&lt;br /&gt;-not means the negation of the expression that follows&lt;br /&gt;\( means the start of a complex expression.&lt;br /&gt;\) means the end of a complex expression.&lt;br /&gt;-o means a logical or of a complex expression. In this case the complex expression is all files like '*,v' or '.*,v'&lt;br /&gt;find . -exec grep "size" '{}' \; -print&lt;br /&gt;This command will search in the current directory and all sub directories. All files that contain the string will have their path printed to standard output.&lt;br /&gt;&lt;strong&gt;grep:&lt;/strong&gt;&lt;br /&gt;&lt;strong&gt;&lt;/strong&gt;&lt;br /&gt;NAME&lt;br /&gt;     grep - search a file for a pattern&lt;br /&gt;SYNOPSIS&lt;br /&gt;     /usr/bin/grep    [-bchilnsvw]     limited-regular-expression     [filename...]&lt;br /&gt;     /usr/xpg4/bin/grep [-E  -F]  [-c  -l    -q]   [-bhinsvwx]     -e pattern_list...  [-f pattern_file]... [file...]&lt;br /&gt;     /usr/xpg4/bin/grep [-E  -F]  [-c  -l    -q]   [-bhinsvwx]     [-e pattern_list...] -f pattern_file... [file...]&lt;br /&gt;     /usr/xpg4/bin/grep [-E  -F]  [-c  -l    -q]   [-bhinsvwx]     pattern [file...]&lt;br /&gt;DESCRIPTION&lt;br /&gt;     The grep utility searches  text  files  for  a  pattern  and     prints  all lines that contain that pattern.  It uses a com-     pact non-deterministic algorithm.&lt;br /&gt;     Be careful using the characters $, *, [, ^, , (, ),  and  \     in  the pattern_list because they are also meaningful to the     shell. It is safest to enclose the  entire  pattern_list  in     single quotes '...'.&lt;br /&gt;     If no files are specified, grep assumes standard input. Nor-     mally,  each  line  found  is copied to standard output. The     file name is printed before each line found if there is more     than one input file.&lt;br /&gt;  /usr/bin/grep     The /usr/bin/grep utility uses limited  regular  expressions     like  those  described on the regexp(5) manual page to match     the patterns.&lt;br /&gt;  /usr/xpg4/bin/grep     The options -E and  -F  affect  the  way  /usr/xpg4/bin/grep     interprets     pattern_list.    If    -E    is    specified,     /usr/xpg4/bin/grep interprets pattern_list as a full regular     expression  (see  -E  for description).  If -F is specified,     grep interprets pattern_list as a fixed string.  If  neither     are specified, grep interprets pattern_list as a basic regular expression as described on regex(5) manual page.&lt;br /&gt;&lt;br /&gt;Example:&lt;br /&gt;U want to find a string "size" in a folder and in its subfloders. This is the example&lt;br /&gt;grep -i size `find . name *.* -print`&lt;br /&gt;&lt;br /&gt;Grep can be used in so many ways and for so many reasons.&lt;br /&gt;If I want to check the java processes&lt;br /&gt;ps -ef  grep java&lt;br /&gt;If I want to check java processes owned by a particular user&lt;br /&gt;ps -ef  grep java  grep websphe&lt;br /&gt;&lt;br /&gt;If I want to check network statistics and specifically for a specific host&lt;br /&gt;netstat -a  grep hostname&lt;br /&gt;..&lt;br /&gt;netstat -a  grep 8080&lt;br /&gt;&lt;br /&gt;and so on.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-1392007074922087050?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/1392007074922087050/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=1392007074922087050' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1392007074922087050'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/1392007074922087050'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/09/find-grep.html' title='find, grep'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5831320403790170129</id><published>2008-09-09T19:23:00.002+05:30</published><updated>2008-09-10T07:34:25.548+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>cp</title><content type='html'>U might know this&lt;br /&gt;But, just FYI&lt;br /&gt;&lt;br /&gt;If you want to copy a file in UNIX, cp is the command&lt;br /&gt;man cp gives the following info.&lt;br /&gt;cp - copy files&lt;br /&gt;&lt;br /&gt;SYNOPSIS     /usr/bin/cp [-fip@] source_file target_file&lt;br /&gt;     /usr/bin/cp [-fip@] source_file... target&lt;br /&gt;     /usr/bin/cp -r  -R [-H  -L  -P] [-fip@] source_dir... target&lt;br /&gt;     /usr/xpg4/bin/cp [-fip@] source_file target_file&lt;br /&gt;     /usr/xpg4/bin/cp [-fip@] source_file... target&lt;br /&gt;     /usr/xpg4/bin/cp -r  -R [-H  -L  -P] [-fip@] source_dir... target&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Usage Example:&lt;br /&gt;&lt;br /&gt;$ mkdir testcp&lt;br /&gt;$ mkdir testcpdest&lt;br /&gt;$ cd testcp&lt;br /&gt;$ touch x1.txt&lt;br /&gt;$ cd ..&lt;br /&gt;$ cp -r testcp testcpdest&lt;br /&gt;&lt;br /&gt;I made a dir called testcp (which is the source dir)&lt;br /&gt;I made another dir called testcpdest (destination dir)&lt;br /&gt;I have touched a file x1.txt  in testcp&lt;br /&gt;I have copied testcp to testcpdest with files using cp -r meaning copy recursively.&lt;br /&gt;&lt;br /&gt;Another ex.,&lt;br /&gt;I have a file like this&lt;br /&gt;-rw-r--r--   1 websphe  websphe    13593 Mar 18 11:53 n1.log&lt;br /&gt;I want to cp it to n2.log with the same time stamp and same uid,gid permissions. This is the way&lt;br /&gt;cp -p n1.log n2.log&lt;br /&gt;n2.log will have same time stamp and other info as n1.log&lt;br /&gt;-rw-r--r--   1 websphe  websphe    13593 Mar 18 11:53 n2.log&lt;br /&gt;-rw-r--r--   1 websphe  websphe    13593 Mar 18 11:53 n1.log&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5831320403790170129?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5831320403790170129/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5831320403790170129' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5831320403790170129'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5831320403790170129'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/09/cp.html' title='cp'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-5343928756341838017</id><published>2008-08-05T22:06:00.002+05:30</published><updated>2008-08-05T22:18:38.643+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>umask</title><content type='html'>umask stands for user file creation mode mask.&lt;br /&gt;777 stands for rwxrwxrwx. first set of rwx is for user, second set of rwx for group and last set is for others. to know what umask u have, at the prompt type umask, which will return a value, say 022.&lt;br /&gt;What does that mean o22?&lt;br /&gt;Its simple.&lt;br /&gt;777-022=755.&lt;br /&gt;umask 022 = rwxr-xr-x, meaning, user has all permissions, group has read and execute, others have read and execute.&lt;br /&gt;To understand umask in permissions mode try this command, umask -S&lt;br /&gt;for example&lt;br /&gt;$ umask&lt;br /&gt;022&lt;br /&gt;$ umask -S&lt;br /&gt;u=rwx,g=rx,o=rx&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-5343928756341838017?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/5343928756341838017/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=5343928756341838017' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5343928756341838017'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/5343928756341838017'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/08/umask.html' title='umask'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-7384195196816379027</id><published>2008-03-19T01:38:00.001+05:30</published><updated>2008-03-19T01:39:53.722+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Test 252'/><title type='text'>Another Practise Test 252</title><content type='html'>1. A developer at a customer site asks the system administrator to help setup IBM Rational Application Developer (IRAD) to debug the application.  The system administrator must make sure the developer has the correct remote JVM debug port configured. Which of the following is the default remote JVM debug port?&lt;br /&gt;A. 7777&lt;br /&gt;B. 8888&lt;br /&gt;C. 9060&lt;br /&gt;D. 9080&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt; &lt;br /&gt;2. A system administrator is asked to help explain why a NameNotFoundException is happening while attempting to access an enterprise bean, data source, messaging resource, or other resource.  What action would be the LEAST useful to do to explain the problem?&lt;br /&gt;A. Browse the properties of the target object in the administrative console, and verify that the JNDI name it specifies matches the JNDI name the client is using.&lt;br /&gt;B. Browse the properties of the target object in its deployment descriptor, and verify that the JNDI name it specifies matches the JNDI name the client is using.&lt;br /&gt;C. Determine if the object being looked up resides on a server different from the one from which the initial context was obtained since, in this case, the fully qualified name must be used.&lt;br /&gt;D. Use the showNameSpace utility to export the entire JNDI tree to determine if the desired resource is listed.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;Correct : A&lt;br /&gt;&lt;br /&gt;3. A system administrator is asked to configure the JVM log files for log file rollover. Which parameters can be configured to control log file rollover?&lt;br /&gt;A. By file size and/or time&lt;br /&gt;B. By the number or Fatal errors and/or by file size and/or time&lt;br /&gt;C. By file size and/or by time and/or by wsadmin command&lt;br /&gt;D. By file size only&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;4. A systems manager is creating a new virtual host that will be used in a clustered environment. After building the virtual host, the system administrator knows that if the new virtual host is to operate properly in a clustered environment, it is very important to:&lt;br /&gt;A. Set the DNS alias to the TCP/IP host name and port number for servlet requests.&lt;br /&gt;B. Register all host aliases used by servers in the cluster in the virtual host.&lt;br /&gt;C.&lt;br /&gt;map the correct Multi-Purpose Internet Mail Extensions (MIME) to the cluster members in the virtual host.&lt;br /&gt;D.&lt;br /&gt;map Web modules to the new virtual host&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;I think A is correct&lt;br /&gt;&lt;br /&gt;5. A system administrator is designing a connection between a Service Integration Bus (SIB) and a WebSphere Message Queue (MQ) manager.  The system administrator wants the design to incorporate the following topologies.  All of the following are correct EXCEPT:&lt;br /&gt;A. design the WebSphere message queue to coexist on the same machine as the WebSphere default-messaging provider.&lt;br /&gt;B. design the messaging engine to participate in a WebSphere MQ cluster.&lt;br /&gt;C. design the messaging engine to look like another queue manager to WebSphere MQ.&lt;br /&gt;D. design WebSphere applications to send messages directly to WebSphere MQ and destinations on the SIB.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;6. A system administrator needs to check the state of an enterprise application within a federated cell. The system administrator can connect using either the administrative console or wsadmin to which of the following components?&lt;br /&gt;&lt;br /&gt;A. Application server&lt;br /&gt;B. JMS Server&lt;br /&gt;C. Deployment manager&lt;br /&gt;D. Node agent&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;7. After changing the JNDI name of a datasource, what must be changed within an application using this datasource to keep them running correctly?&lt;br /&gt;&lt;br /&gt;A. The reference to resource mappings. &lt;br /&gt;B. The EJB references to match the new JNDI name.&lt;br /&gt;C. The name of the JDBC provider to match the new datasorce name.&lt;br /&gt;D. The datasources.xml file for the application.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;8. What is the significance of the vpd.properties file in the WebSphere Application Server V6 Network Deployment package?&lt;br /&gt;&lt;br /&gt;A. It contains information of usernames and passwords that can install, operate and deploy applications on the application server(s).&lt;br /&gt;B. It contains information about previous installations of WebSphere Application Server products and helps installation program to control options for new installations.&lt;br /&gt;C. It contains the port numbers to be assigned by the installation program during the new install.&lt;br /&gt;D. It contains the list of applications including date and time stamps and user that installed the application.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;9. A system administrator has configured the Web Container thread pool with the "Allow thread allocation beyond maximum thread size" option enabled (checked). What is the MOST significant performance implication of this configuration setting? &lt;br /&gt;&lt;br /&gt;A. It will allow the system to scale well and eliminate any bottlenecks&lt;br /&gt;B. It could allow unexpectedly high load into the system possibly rendering the system unusable&lt;br /&gt;C. It can cause timeouts in the plugin &lt;br /&gt;D. It can cause thrashing&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;10. A system administrator requires that an EJB JAR file be part of two Enterprise Application Archive (EAR) files. How can this be BEST accomplished using the Application Server Toolkit (AST)? &lt;br /&gt;&lt;br /&gt;A. Use the JDK's JAR utility to include the WAR file in the EAR files.&lt;br /&gt;B. Use the Application Deployment Descriptor editor to add the EJB module to each of the applications.&lt;br /&gt;C. Open the Properties dialog for the EJB project and select the applications in the Project References dialog.&lt;br /&gt;D. Open the Properties dialog for both Enterprise Application projects and select the EJB module in the Project References dialog.&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;11. Application code can write messages to a server's SystemOut and SystemErr log files. All of the following configurations are valid for application code log messages EXCEPT:&lt;br /&gt;&lt;br /&gt;A. application log messages can be excluded or included entirely.&lt;br /&gt;B. application log messages can be formatted like WebSphere Application Server system messages.&lt;br /&gt;C. application log messages can be excluded from either SystemErr.log or SystemOut.log individually.&lt;br /&gt;D. application log messages can not be formatted like WebSphere Application Server system messages.&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;12. A system administrator created an application server profile using the profile creation wizard.   The system administrator then ran the Installation Verification program (IVT) immediately after creating it to verify the creation. Which of the following will indicate the appropriate behavior of the IVT program after its invocation?&lt;br /&gt;&lt;br /&gt;A. IVT will fail as application server (server1) was not started after profile creation.&lt;br /&gt;B. IVT verifies the log files for accuracy and does not need to be connected to the application server (server1).&lt;br /&gt;C. IVT will start the application server (server1) if it was not already started and verifies the installation.&lt;br /&gt;D. IVT will verify by connecting to the application server (server1) that was started by the profile creation wizard after its creation.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;13. A backup configuration was created using the backupConfig command. The configuration must now be restored.  Which of the following commands should be used to avoid stopping the server before restoring the configuration? &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A. restoreConfig&lt;br /&gt;B. restoreConfig -nostop&lt;br /&gt;C. restoreConfig -nowait&lt;br /&gt;D. restoreConfig -safeMode&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;14. A system administrator wants to be sure that seven days of SystemOut.log information are available on the local server's disk.  What is the easiest way to ensure this will happen using the Log File rotation?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A. Set the "Maximum Size" option to 1 week.&lt;br /&gt;B. Set the "Start Time" option to Sunday and the "Maximum Number of Historical Log Files" to 1.&lt;br /&gt;C. Set the "Maximum Number of Historical Log Files" to 7 and the Time options to Start Time to 1 and Repeat Time to 24.&lt;br /&gt;D. Set the "Maximum Log Files" option to 7.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;15. A system administrator would like to deploy an enterprise application running on WebSphere that exchanges messages with a WebSphere MQ based application. What J2EE messaging provider would be the BEST fit?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A. The WebSphere V5 messaging provider&lt;br /&gt;B. The Default messaging provider&lt;br /&gt;C. The generic JMS Provider&lt;br /&gt;D. The Embedded JMS Provider&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;16. A system administrator is asked to help diagnose some application problems. The system administrator considers asking for the log messages to be logged in the Advanced Format. Why might this help the system administrator to diagnose the problem?&lt;br /&gt;&lt;br /&gt;A. The exact line of code where an exception occurred will be decompiled and shown as part of the message.&lt;br /&gt;B. The JVM heap metrics at the time of the error will be included in the message.&lt;br /&gt;C. Information about an event, when possible, will be added to the message.&lt;br /&gt;D. Information about the distributed transaction will be included.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;17. A system administrator has federated a node while creating the custom profile with the profile creation wizard. The system administrator does not see the entries for that node using the deployment manager administrative console. Which log file will give more information about the problem?&lt;br /&gt;&lt;br /&gt;A. addNode.log under &lt;PROFILE-ROOT&gt;\logs directory&lt;br /&gt;B. addNode.log under &lt;DEPLOYMENT-MANAGER-ROOT&gt;\logs directory&lt;br /&gt;C. federate.log under &lt;PROFILE-ROOT&gt;\logs directory&lt;br /&gt;D. federate.log under &lt;DEPLOYMENT-MANAGER-ROOT&gt;\logs directory&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;18. Cluster creation requires the system administrator to specify the weight for a cluster member. This weight is significant because it is used in the WebSphere WLM runtime by the:&lt;br /&gt;&lt;br /&gt;A. Random scheduling algorithm&lt;br /&gt;B. Round Robin scheduling algorithm &lt;br /&gt;C. Both Random and Round Robin scheduling algorithm&lt;br /&gt;D. Weighted Random algorithm&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;19. While performing a node federation, the addNode operation failed.  From the following list of options, what would MOST likely induce this failure? &lt;br /&gt;&lt;br /&gt;A. The cell already exists&lt;br /&gt;B. The cell's deployment manager is running before the addNode command was run&lt;br /&gt;C. The name of the new node is not unique in the cell&lt;br /&gt;D. The addNode did not specify to carry over the applications&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;20. Immediately following federation, the process started by the custom profile is the:&lt;br /&gt;&lt;br /&gt;A. Deployment manager&lt;br /&gt;B. Application server&lt;br /&gt;C. Nodeagent&lt;br /&gt;D. Web server&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;20. Which of the following is the MOST accurate description of how the "Single" application class loader policy functions?&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A. A single application class loader is used to load all EJBs, utility JARs, and shared libraries within the application server JVM.&lt;br /&gt;B. An application class loader first delegates the loading of classes to its parent class loader before attempting to load the class from its local class path.&lt;br /&gt;C. The class loader attempts to load classes from its local class path before delegating the class loading to its parent.&lt;br /&gt;D. A single application class loader is used to load only the utility JARs and Web modules within the application server JVM.&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;21. After federating a custom node, an examination of the entries in a log file shows an "INSTCONFFAIL" indicator which denotes a complete failure.  All of the following can be contributors to the failure EXCEPT:&lt;br /&gt;&lt;br /&gt;A. the deployment manager is not running.&lt;br /&gt;B. the node agent failed to start.&lt;br /&gt;C. security was enabled.&lt;br /&gt;D. a reserved name was used for the node name.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;22. A system administrator has received an EAR file from the development team. The system administrator has been asked to install it into an application server.  The system administrator has been told that there are some J2EE security roles defined within the EAR that need to be mapped to users and groups within the defined user registry.  All of the following can be used to map users and groups to J2EE security roles EXCEPT:&lt;br /&gt;&lt;br /&gt;A. during initial installation of an Enterprise Application using the administrative console.&lt;br /&gt;B. after the Enterprise Application has already been installed through the administrative console.&lt;br /&gt;C. after the Enterprise Application has already been installed through wsadmin.&lt;br /&gt;D. while installing the Enterprise Application by editting the was.policy file.&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;23. An administrator is configuring the Message Driven Bean (MDB) activation specification to service a queue.  Which of the following properties is required when setting up a queue?&lt;br /&gt;&lt;br /&gt;A. destinationType&lt;br /&gt;B. messageSelector&lt;br /&gt;C. acknowledgeMode&lt;br /&gt;D. subscriptionDurability&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;24. When using local session management, which of the following configuration settings could cause the loss of user session objects?&lt;br /&gt;&lt;br /&gt;A. If HTTP Persistence connections are not used&lt;br /&gt;B. If the Allow overflow property setting is not enabled&lt;br /&gt;C. If Memory-to-memory replication is not configured&lt;br /&gt;D. If the datasource used by the session database is not defined&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;25. During a WebSphere V6 Network Deployment installation, the system administrator did not select to install "Application Server Samples".  Later, the system administrator decided to install "Application Server Samples". Which of the following steps are required to complete this installation?&lt;br /&gt;&lt;br /&gt;A. Connect to the admin console. Navigate to Applications -&gt; Enterprise Applications and click on 'Install' tab.  Provide sampleapp.ear under samples directory.&lt;br /&gt;B. Start the installation wizard. Select "Add features to the existing copy of the V6 Application Server product".  Choose "Application Server Samples" option during the installation. &lt;br /&gt;C. Start the installation wizard. Select "Add features to the existing copy of the V6 Application Server product".  Choose "Application Server Samples" option during the installation. Run "install.bat" under samples\bin directory to deploy sample applications.&lt;br /&gt;D. Start the installation wizard. Select "Upgrade existing copy of the V6 Application Server product" and select "Network Deployment" option during the installation. &lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;26. A system administrator has been assigned the task of defining a Custom User Registry for a federated cell.  The administrative console will be used.  All of the following entries are required in the process of configuring the Custom User Registry EXCEPT:&lt;br /&gt;&lt;br /&gt;A. Server user ID&lt;br /&gt;B. Server user password&lt;br /&gt;C. Server host name&lt;br /&gt;D. Custom registry implementation class name&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;27. Which of the following adjustments to the Web module parameter would result in improved response time for servlet clients?&lt;br /&gt;&lt;br /&gt;A. Setting the distributable flag.&lt;br /&gt;B. Setting the reload interval to 20 seconds or less.&lt;br /&gt;C. Enabling load on startup.&lt;br /&gt;D. Disabling load on startup.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;28. A system administrator notices a number of "ConnectionWaitTimeoutException" exceptions associated with a datasource in the SystemOut.log file. Which of the following is the MOST likely cause of this error? &lt;br /&gt;&lt;br /&gt;A. The Connection Timeout on the data source has been set to 0.&lt;br /&gt;B. The number of physical connections to the database has reached the number of Maximum Connection as specified in the datasource settings.&lt;br /&gt;C. The number of physical connections to the database has reached the number of Minimum Connection as specified in the Data source settings.&lt;br /&gt;D. The database transaction isolation is set too high.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;29. A J2EE enterprise application is being assembled to take advantage of J2EE security.  During this process, there are a number of configurations and mappings that need to be made.  Which of the following items can a method permission be mapped to? &lt;br /&gt;&lt;br /&gt;A. Web resources&lt;br /&gt;B. An EJB&lt;br /&gt;C. A login mechanism&lt;br /&gt;D. A security realm&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;30. A system administrator is setting up SSL communications between the plugin and the application server.  A new keyring file is being used.  Which of the following elements in the plugin-cfg.xml file would need to be defined? &lt;br /&gt;&lt;br /&gt;A. The public key and the private key &lt;br /&gt;B. The public key and the password file &lt;br /&gt;C. The keyring file and the password file &lt;br /&gt;D. The keyring file and the stashfile&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;31. A new JDBC provider is being created in a cell in which the servers run different operating systems.  Which of the following scopes should be used?&lt;br /&gt;&lt;br /&gt;A. Cluster scope&lt;br /&gt;B. Server scope&lt;br /&gt;C. Node scope&lt;br /&gt;D. Cell scope &lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;32. A system administrator has installed the Network Deployment Manager package and now wishes to build a clustered server environment using custom profiles. All of the following steps are necessary EXCEPT:&lt;br /&gt;&lt;br /&gt;A. create a deployment manager profile.&lt;br /&gt;B. accept default values, create one custom profile on each node on which application servers will be run.&lt;br /&gt;C. federate each custom profile to the deployment manager. &lt;br /&gt;D. create new application servers and clusters on the nodes from the administrative console.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;33. A Java client is residing in a client container.  The Java client needs to make a request to the EJB container of an application server in a distributed cell.  Which of the following protocols is MOST appropriate for the client request? &lt;br /&gt;&lt;br /&gt;A. JDBC&lt;br /&gt;B. RMI/IIOP&lt;br /&gt;C. SOAP&lt;br /&gt;D. HTTP(S)&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;34. Which of the following sets of Web server plugin properties can be modified by using the administrative console's request routing configuration tab?&lt;br /&gt;&lt;br /&gt;A. Caching policy and log level&lt;br /&gt;B. Refresh interval and log file location&lt;br /&gt;C. Enable/disable automatic plug-in propagation&lt;br /&gt;D. Load balancing option and retry interval&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;35. How can a system administrator persist trace output that is written to the memory buffer of a running application server?&lt;br /&gt;&lt;br /&gt;A. Configure the time interval and/or the memory buffer max size parameters so that if either is reached the memory buffer will be dumped into a file.&lt;br /&gt;B. In the Admin Console, click "Troubleshooting -&gt; Logs and Trace -&gt; &lt;server name&gt; -&gt; Diagnostic Trace" and then go to the Configuration tab and chose to Dump the memory buffer&lt;br /&gt;C. In the Admin Console, click "Troubleshooting -&gt; Logs and Trace -&gt; &lt;server name&gt; -&gt; Diagnostic Trace" and then go to the Runtime tab and chose to Dump the memory buffer&lt;br /&gt;D. It is not possible to perform this task in a running application server.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;36. An HTTP plug-in configuration file can be regenerated from the administrative console by selecting which of the following?&lt;br /&gt;&lt;br /&gt;A. Servers-&gt;Web servers, select a Web server, and click Generate Plug-in&lt;br /&gt;B. Servers-&gt;Application servers-&gt;server-&gt;Web container, and click Generate Plug-in&lt;br /&gt;C. Environment-&gt;Update Web Server Plug-in, and click OK&lt;br /&gt;D. Environment-&gt;Virtual Hosts, and click Generate Plug-in&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;37. Before enabling Global security, an administrator must first configure various security settings.  All of the following steps are required to be configured before enabling global security, EXCEPT:&lt;br /&gt;&lt;br /&gt;A. the default SSL keystore and truststore files.&lt;br /&gt;B. a user registry.&lt;br /&gt;C. the authentication mechanism.&lt;br /&gt;D. the server user ID for the given user registry.&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;38. A system administrator wants to implement the Upstream Queuing model to improve performance.  Which of the following adjustments MUST be made?&lt;br /&gt;&lt;br /&gt;A. Set the all cluster members to have the same JVM heap size.&lt;br /&gt;B. Tune each Web container to have a smaller queue than the Web server.&lt;br /&gt;C. Tune the queues to decrease in size from the Web server to the backend resource.&lt;br /&gt;D. Tune the queues to increase in size from the Web server to the backend resource.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;39. In order to set up memory-to-memory replication in a WebSphere Application Server V6 clustered environment, which of the following should be created?&lt;br /&gt;&lt;br /&gt;A. Replication Domain and specify cluster members to use this Replication Domain&lt;br /&gt;B. Replication Domain on each cluster member and create partitions for each Replication Domain&lt;br /&gt;C. Replication Domain and specify the cell associates with the Replication Domain&lt;br /&gt;D. Replication partition and attach cluster to the partition&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;40. A system administrator received a message that the Installation Verification (IVT) failed after creating a profile using the profile creation wizard. Which log file(s) should the system administrator review to find out more information about the failure? &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A. ivtClient.log under &lt;PROFILE-ROOT&gt;\logs&lt;br /&gt;B. wasprofile_create_profileName.log under &lt;INSTALL-ROOT&gt;\logs\wasprofile directory&lt;br /&gt;C. ivtlog.txt under &lt;INSTALL-ROOT&gt;\logs directory&lt;br /&gt;D. installlog.txt under system temp directory&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;41. Java 2 security must be configured through the console.  Which of the following administrative roles is the required minimum?  &lt;br /&gt;&lt;br /&gt;A. Administrator&lt;br /&gt;B. Security &lt;br /&gt;C. Configurator  &lt;br /&gt;D. Operator&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;42. A system administrator is called to suggest how to determine the cause of an application error. The system administrator recommends that the Log Analyzer be used over and above just reading the JVM logs because Log Analyzer can:&lt;br /&gt;&lt;br /&gt;A. Show a series of errors as one unit of work.&lt;br /&gt;B. Analyze the logs and pinpoint the root cause of an error and then suggest a fix.&lt;br /&gt;C. Collate all logs from every system component and pinpoint the root cause of the error.&lt;br /&gt;D. Dynamically monitor log files at runtime and send an alert when errors occur.&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;43. A system administrator was asked to develop artifacts specifically for the installation of a WebSphere Application Server V6 Network Deployment package. The system administrator also created an application server profile using silent installation scripts (response files). What approach will enable the system administrator to complete the task without using GUI based tools?&lt;br /&gt;&lt;br /&gt;A. Create two response files where the first response file is used to install the product binaries and causes the second response file to be used for creating the application server profile.&lt;br /&gt;B. Create a response file that installs product binaries and creates the application server profile.&lt;br /&gt;C. Create a response file that installs product binaries and use profile creation wizard to create the application server profile.&lt;br /&gt;D. Install product binaries using installation wizard and create a response file to create the application server profile.&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;44. The Servlet 2.4 specification requires that an HTTP session honor session affinity. In a clustered environment, a cluster member could possibly fail. Which of the following mechanisms is used to ensure session affinity?&lt;br /&gt;&lt;br /&gt;A. Database session persistence&lt;br /&gt;B. Memory-to-memory replication&lt;br /&gt;C. Web Server plug-in&lt;br /&gt;D. Replication Domain&lt;br /&gt;&lt;br /&gt;D&lt;br /&gt;&lt;br /&gt;45. Which of the following would have to be configured in order to implement memory-to-memory HTTP Session persistence?&lt;br /&gt;&lt;br /&gt;A. The Data Replication Service and Web Container&lt;br /&gt;B. EJB session beans and EJB Container&lt;br /&gt;C. The HTTP Plug-in and Embedded HTTP Server&lt;br /&gt;D. The JMS Server and Queue Manager&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;46. Which of the following statements is valid about the First Failure Data Capture (FFDC) tool?&lt;br /&gt;&lt;br /&gt;A. The First Failure Data Capture tool does not affect the performance of the IBM WebSphere Application Server.&lt;br /&gt;B. The First Failure Data Capture tool is only available in application servers that have been federated into a Network Deployment cluster.&lt;br /&gt;C. The First Failure Data Capture tool is not compatible with J2EE 1.4. &lt;br /&gt;D. The First Failure Data Capture tool is not available on all platforms.&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt;&lt;br /&gt;47. Which of the following are used in order to administer the application server?&lt;br /&gt;&lt;br /&gt;A. MBeans and XML files&lt;br /&gt;B. A relational database repository and datasources&lt;br /&gt;C. Security service and LDAP user registry&lt;br /&gt;D. External HTTP server and HTTP server plugin&lt;br /&gt;&lt;br /&gt;A&lt;br /&gt; &lt;br /&gt;49. A WAR file in an enterprise application has been changed. How can a system administrator update it on the server with a minimal amount of work?&lt;br /&gt;&lt;br /&gt;A. Re-package the EAR file using Application Server Toolkit then use the "Update -&gt; Full application" function on the administrative console.&lt;br /&gt;B. Use the "Update -&gt; Single file" function of the Administrative console to replace the WAR file.&lt;br /&gt;C. Use the "Update -&gt; Single module" of the Administrative console to replace the WAR file.&lt;br /&gt;D. Use the "Update -&gt; Partial application" of the Administrative console to replace the WAR file.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;50. A customer has configured an HTTP session via the Session Manager properties interface. The session is set to timeout in about 30 minutes. However, it typically takes more than 30 minutes and sometimes 35 minutes for a session to timeout. What is the MOST likely cause of the delay?&lt;br /&gt;&lt;br /&gt;A. There is a bug in the Session Manager configuration.&lt;br /&gt;B. The Least Recently used algorithm is slow.&lt;br /&gt;C. The session invalidation process is running approximately every 5 minutes.&lt;br /&gt;D. The session timeout is set too high.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;51. A system administrator is adding a cluster member to an existing cluster. What is the minimum requirement for the cluster member to qualify for immediate addition to the cluster?&lt;br /&gt;&lt;br /&gt;A. Any standalone application server qualifies if it is available on the network.&lt;br /&gt;B. Any application server qualifies if it uses the same hardware and operating system as the other servers in the cell qualifies.&lt;br /&gt;C. The new cluster member is part of a node in the cell, and belongs to the same node group and core group as other servers in the cluster.&lt;br /&gt;D. The new cluster member must belong to a node in the same cell where the cluster is defined.&lt;br /&gt;&lt;br /&gt;C&lt;br /&gt;&lt;br /&gt;52. Assume that a load balancer and a Federated cell have been installed and are functional. All of the following contain built-in failover capabilities EXCEPT:&lt;br /&gt;&lt;br /&gt;A. HTTP server&lt;br /&gt;B. Deployment manager&lt;br /&gt;C. Web container&lt;br /&gt;D. EJB container&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;53. The Tivoli Performance Viewer can provide several summary reports to include performance statistics for various application and application server components. Which of the following lists contains the complete set of available summary reports?&lt;br /&gt;&lt;br /&gt;A. EJBs, EJB Methods, Connection Pool, Thread Pool, J2C Container&lt;br /&gt;B. Servlets, EJBs, HTTP plug-in, ORB plug-in, JVM&lt;br /&gt;C. Servlets, EJBs, EJB Methods, Connection Pool, Thread Pool&lt;br /&gt;D. Servlets, EJBs, Connection Pool, Thread Pool, Dynamic Cache&lt;br /&gt;&lt;br /&gt;B&lt;br /&gt;&lt;br /&gt;54. A security role has been mapped to the special group Everyone. What is the result of this action?&lt;br /&gt;&lt;br /&gt;A. Every user defined for the group has access to the resource.&lt;br /&gt;B. Everyone will be denied access to the resource.&lt;br /&gt;C. Every user has access to the resource.&lt;br /&gt;D. Anyone logged in has access to the resource.&lt;br /&gt;a&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-7384195196816379027?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/7384195196816379027/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=7384195196816379027' title='6 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7384195196816379027'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/7384195196816379027'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2008/03/another-practise-test-252.html' title='Another Practise Test 252'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>6</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-84957117578017892</id><published>2007-12-07T21:19:00.000+05:30</published><updated>2007-12-07T21:51:40.197+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Definitions'/><title type='text'>Some Definitions</title><content type='html'>&lt;b&gt;proxy server&lt;/b&gt;&lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;In an enterprise that uses the Internet, a proxy server is a server that acts as an intermediary between a workstation user and the Internet so that the enterprise can ensure security, administrative control, and caching service. A proxy server is associated with or part of a gateway server that separates the enterprise network from the outside network and a firewall server that protects the enterprise network from outside intrusion. &lt;br /&gt;A proxy server receives a request for an Internet service (such as a Web page request) from a user. If it passes filtering requirements, the proxy server, assuming it is also a cache server, looks in its local cache of previously downloaded Web pages. If it finds the page, it returns it to the user without needing to forward the request to the Internet. If the page is not in the cache, the proxy server, acting as a client on behalf of the user, uses one of its own IP addresses to request the page from the server out on the Internet. When the page is returned, the proxy server relates it to the original request and forwards it on to the user. &lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;To the user, the proxy server is invisible; all Internet requests and returned responses appear to be directly with the addressed Internet server. (The proxy is not quite invisible; its IP address has to be specified as a configuration option to the browser or other protocol program.) &lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;An advantage of a proxy server is that its cache can serve all users. If one or more Internet sites are frequently requested, these are likely to be in the proxy's cache, which will improve user response time. In fact, there are special servers called cache servers. A proxy can also do logging. &lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;The functions of proxy, firewall, and caching can be in separate server programs or combined in a single package. Different server programs can be in different computers. For example, a proxy server may in the same machine with a firewall server or it may be on a separate server and forward requests through the firewall. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;&lt;b&gt;gateway&lt;/b&gt;&lt;br /&gt; &lt;br /&gt;A gateway is a network point that acts as an entrance to another network. On the Internet, a node or stopping point can be either a gateway node or a host (end-point) node. Both the computers of Internet users and the computers that serve pages to users are host nodes. The computers that control traffic within your company's network or at your local Internet service provider (ISP) are gateway nodes. &lt;br /&gt;In the network for an enterprise, a computer server acting as a gateway node is often also acting as a proxy server and a firewall server. A gateway is often associated with both a router, which knows where to direct a given packet of data that arrives at the gateway, and a switch, which furnishes the actual path in and out of the gateway for a given packet. &lt;br&gt;&lt;br /&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;&lt;b&gt;node &lt;/b&gt;&lt;br /&gt; &lt;br /&gt;In a network, a node is a connection point, either a redistribution point or an end point for data transmissions. In general, a node has programmed or engineered capability to recognize and process or forward transmissions to other nodes.  &lt;br&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;&lt;b&gt;router &lt;/b&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;In packet-switched networks such as the Internet, a router is a device or, in some cases, software in a computer, that determines the next network point to which a packet should be forwarded toward its destination. The router is connected to at least two networks and decides which way to send each information packet based on its current understanding of the state of the networks it is connected to. A router is located at any gateway (where one network meets another), including each point-of-presence on the Internet. A router is often included as part of a network switch. &lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;A router may create or maintain a table of the available routes and their conditions and use this information along with distance and cost algorithms to determine the best route for a given packet. Typically, a packet may travel through a number of network points with routers before arriving at its destination. Routing is a function associated with the Network layer (layer 3) in the standard model of network programming, the Open Systems Interconnection (OSI) model. A layer-3 switch is a switch that can perform routing functions.&lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;An edge router is a router that interfaces with an asynchronous transfer mode (ATM) network. A brouter is a network bridge combined with a router.&lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;For home and business computer users who have high-speed Internet connections such as cable, satellite, or DSL, a router can act as a hardware firewall. This is true even if the home or business has only one computer. Many engineers believe that the use of a router provides better protection against hacking than a software firewall, because no computer Internet Protocol address are directly exposed to the Internet. This makes port scans (a technique for exploring weaknesses) essentially impossible. In addition, a router does not consume computer resources as a software firewall does. Commercially manufactured routers are easy to install, reasonably priced, and available for hard-wired or wireless networks. &lt;br&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt; &lt;br /&gt;&lt;b&gt;switch &lt;/b&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;In a telecommunications network, a switch is a device that channels incoming data from any of multiple input ports to the specific output port that will take the data toward its intended destination. In the traditional circuit-switched telephone network, one or more switches are used to set up a dedicated though temporary connection or circuit for an exchange between two or more parties. On an Ethernet local area network (LAN), a switch determines from the physical device (Media Access Control or MAC) address in each incoming message frame which output port to forward it to and out of. In a wide area packet-switched network such as the Internet, a switch determines from the IP address in each packet which output port to use for the next part of its trip to the intended destination. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;In the Open Systems Interconnection (OSI) communications model, a switch performs the layer 2 or Data-Link layer function. That is, it simply looks at each packet or data unit and determines from a physical address (the "MAC address") which device a data unit is intended for and switches it out toward that device. However, in wide area networks such as the Internet, the destination address requires a look-up in a routing table by a device known as a router. Some newer switches also perform routing functions (layer 3 or the Network layer functions in OSI) and are sometimes called IP switches. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;On larger networks, the trip from one switch point to another in the network is called a hop. The time a switch takes to figure out where to forward a data unit is called its latency. The price paid for having the flexibility that switches provide in a network is this latency. Switches are found at the backbone and gateway levels of a network where one network connects with another and at the subnetwork level where data is being forwarded close to its destination or origin. The former are often known as core switches and the latter as desktop switches. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;In the simplest networks, a switch is not required for messages that are sent and received within the network. For example, a local area network may be organized in a Token Ring or bus arrangement in which each possible destination inspects each message and reads any message with its address. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;Circuit-Switching version Packet-Switching&lt;br /&gt;A network's paths can be used exclusively for a certain duration by two or more parties and then switched for use to another set of parties. This type of "switching" is known as circuit-switching and is really a dedicated and continuously connected path for its duration. Today, an ordinary voice phone call generally uses circuit-switching. &lt;br&gt;&lt;br /&gt;Most data today is sent, using digital signals, over networks that use packet-switching. Using packet-switching, all network users can share the same paths at the same time and the particular route a data unit travels can be varied as conditions change. In packet-switching, a message is divided into packets, which are units of a certain number of bytes. The network addresses of the sender and of the destination are added to the packet. Each network point looks at the packet to see where to send it next. Packets in the same message may travel different routes and may not arrive in the same order that they were sent. At the destination, the packets in a message are collected and reassembled into the original message. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;&lt;b&gt;layer 2 &lt;/b&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;Layer 2 refers to the Data Link layer of the commonly-referenced multilayered communication model, Open Systems Interconnection (OSI). The Data Link layer is concerned with moving data across the physical links in the network. In a network, the switch is a device that redirects data messages at the layer 2 level, using the destination Media Access Control (MAC) address to determine where to direct the message.&lt;br&gt;&lt;br /&gt;The Data-Link layer contains two sublayers that are described in the IEEE-802 LAN standards: &lt;br /&gt;&lt;br&gt;&lt;br /&gt;-&gt;Media Access Control (MAC) sublayer &lt;br /&gt;-&gt;Logical Link Control (LLC) sublayer &lt;br /&gt;-&gt;The Data Link layer ensures that an initial connection has been set up, divides output data into data frames, and handles the acknowledgements from a receiver that the data arrived successfully. It also ensures that incoming data has been received successfully by analyzing bit patterns at special places in the frames.  &lt;br /&gt; &lt;br&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;&lt;b&gt;bridge &lt;/b&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;In telecommunication networks, a bridge is a product that connects a local area network (LAN) to another local area network that uses the same protocol (for example, Ethernet or Token Ring). You can envision a bridge as being a device that decides whether a message from you to someone else is going to the local area network in your building or to someone on the local area network in the building across the street. A bridge examines each message on a LAN, "passing" those known to be within the same LAN, and forwarding those known to be on the other interconnected LAN (or LANs). &lt;br&gt;&lt;br /&gt;In bridging networks, computer or node addresses have no specific relationship to location. For this reason, messages are sent out to every address on the network and accepted only by the intended destination node. Bridges learn which addresses are on which network and develop a learning table so that subsequent messages can be forwarded to the right network. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;Bridging networks are generally always interconnected local area networks since broadcasting every message to all possible destinations would flood a larger network with unnecessary traffic. For this reason, router networks such as the Internet use a scheme that assigns addresses to nodes so that a message or packet can be forwarded only in one general direction rather than forwarded in all directions. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;A bridge works at the data-link (physical network) level of a network, copying a data frame from one network to the next network along the communications path. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;A bridge is sometimes combined with a router in a product called a brouter.&lt;br /&gt; &lt;br&gt;&lt;br /&gt;&lt;b&gt;firewall&lt;/b&gt; &lt;br /&gt; &lt;br&gt;&lt;br /&gt;A firewall is a set of related programs, located at a network gateway server, that protects the resources of a private network from users from other networks. (The term also implies the security policy that is used with the programs.) An enterprise with an intranet that allows its workers access to the wider Internet installs a firewall to prevent outsiders from accessing its own private data resources and for controlling what outside resources its own users have access to. &lt;br /&gt;Basically, a firewall, working closely with a router program, examines each network packet to determine whether to forward it toward its destination. A firewall also includes or works with a proxy server that makes network requests on behalf of workstation users. A firewall is often installed in a specially designated computer separate from the rest of the network so that no incoming request can get directly at private network resources. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;There are a number of firewall screening methods. A simple one is to screen requests to make sure they come from acceptable (previously identified) domain name and Internet Protocol addresses. For mobile users, firewalls allow remote access in to the private network by the use of secure logon procedures and authentication certificates. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;A number of companies make firewall products. Features include logging and reporting, automatic alarms at given thresholds of attack, and a graphical user interface for controlling the firewall. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;Computer security borrows this term from firefighting, where it originated. In firefighting, a firewall is a barrier established to prevent the spread of fire. &lt;br /&gt;&lt;br&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;&lt;b&gt;reverse proxy server &lt;/b&gt;&lt;br /&gt; &lt;br&gt;&lt;br /&gt;A reverse proxy server is a proxy server that relays connection requests for inbound network traffic &lt;br /&gt;&lt;br&gt;&lt;br /&gt;&lt;b&gt;Web Proxies&lt;/b&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;A proxy server is a gateway for users to the Web at large. Users configure the proxy in their browser settings, and all HTTP requests are routed via the proxy. Proxies are typically operated by ISPs and network administrators, and serve several purposes: for example, &lt;br /&gt;&lt;br&gt;&lt;br /&gt;-&gt;to speed access to the Web by caching pages fetched, so that popular pages don't have to be re-fetched for every user who views them. &lt;br /&gt;-&gt;to enable controlled access to the web for users behind a firewall. &lt;br /&gt;-&gt;to filter or transform web content. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;&lt;b&gt;Reverse Proxies&lt;/b&gt;&lt;br /&gt;&lt;br&gt;&lt;br /&gt;A reverse proxy is a gateway for servers, and enables one web server to provide content from another transparently. As with a standard proxy, a reverse proxy may serve to improve performance of the web by caching; this is a simple way to mirror a website. But the most common reason to run a reverse proxy is to enable controlled access from the Web at large to servers behind a firewall. &lt;br /&gt;&lt;br&gt;&lt;br /&gt;The proxied server may be a webserver itself, or it may be an application server using a different protocol, or an application server with just rudimentary HTTP that needs to be shielded from the web at large. Since 2004, reverse proxying has been the preferred method of deploying JAVA/Tomcat applications on the Web, replacing the old mod_jk (itself a special-purpose reverse proxy module). &lt;br /&gt;&lt;br&gt;&lt;br /&gt;The Funda of Reverse Proxy - The web server will service any HTTP or HTTPS requests and CAN operate in reverse proxy mode. In this mode, the destination server will be hidden from the user and all requests will appear as though they are being fulfilled at the proxy. The web agent acts as a filter for requests directed to the proxy server. The web agent will intercept all requests directed to the web server where it is loaded and will communicate with SiteMinder to determine if the requested resource is protected. If the resource is protected, the web agent will challenge the user to provide an authorised set of credentials. Otherwise, the request is release to the web server for processing.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-84957117578017892?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/84957117578017892/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=84957117578017892' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/84957117578017892'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/84957117578017892'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2007/12/some-definitions.html' title='Some Definitions'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-275839244414334035</id><published>2007-09-24T19:59:00.000+05:30</published><updated>2007-09-24T20:07:03.486+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><title type='text'>tar tips</title><content type='html'>If you want to make a tar of a folder, a typical examle :-&lt;br /&gt;You have a mount, say, /servermount/swfcopy, in which you have to copy a folder foo to ur box.&lt;br /&gt;Do like this&lt;br /&gt;cd /servermount/swfcopy&lt;br /&gt;tar cvf /where_to_keep_folder/filename.tar ./foo&lt;br /&gt;say, tar cvf /export/home/myfolder/foo.tar ./foo&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-275839244414334035?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/275839244414334035/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=275839244414334035' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/275839244414334035'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/275839244414334035'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2007/09/tar-tips.html' title='tar tips'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-6137679901775639941</id><published>2007-08-13T22:44:00.001+05:30</published><updated>2007-08-13T22:45:45.883+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Test 252'/><title type='text'>Test 252</title><content type='html'>Question 1: A WSAS administrator needs to plan a WSAS topology to allow for firewalls and DMZ. Which of the following topologies would meet this goal?&lt;br /&gt;&lt;br /&gt;A. Multiple cells&lt;br /&gt;Question 2: A WSAS administrator monitoring the performance of an Entity Bean EJB in a WSAS application, notices a lot of lock escalations and deadlocks in the underlying database. Which of the following deployment descriptors could cause this problem?&lt;br /&gt;&lt;br /&gt;A. EJB methods are not marked with forUpdate flag.&lt;br /&gt;B. EJB methods are marked with multiVersionControl flag.&lt;br /&gt;C. EJB methods are marked with readOnly flag.&lt;br /&gt;D. EJB methods are marked with treeLocking flag.&lt;br /&gt;E. EJB methods are marked with useIntentLock flag.&lt;br /&gt;Question 3: While deploying an EJB application, the WSAS administrator notices the following error:&lt;br /&gt;&lt;br /&gt;WSVR0040E: addEjbModule failed for MyApp-EJB.jar [class com.ibm.ws.runtime.component.DeployedModuleImpl] java.lang.NoClassDefFoundError: com/ibm/ejs/ras/Tr&lt;br /&gt;&lt;br /&gt;Which of the following could cause the error?&lt;br /&gt;&lt;br /&gt;A. The WSAS installation is missing the EJB deployment library.&lt;br /&gt;B. Security permissions are not given for the application in the installation_root\properties\server.policy file&lt;br /&gt;C. The EJB jar file first has not been encapsulated in a J2EE EAR file.&lt;br /&gt;D. The EJBrmic tool has not been run prior to deploying.&lt;br /&gt;E. The EJB jar file has a misconfigured ejb-jar.xml file.&lt;br /&gt;me: Possible causes of this error include:&lt;br /&gt;&lt;br /&gt;Security permissions are not given for the application in the installation_root\properties\server.policy file.&lt;br /&gt;Check the server.policy file to see if the security permissions are given for the application.&lt;br /&gt;&lt;br /&gt;Give permissions for the application in the server.policy file. For example: &lt;br /&gt;&lt;br /&gt;//purchaseOrder permission &lt;br /&gt;grant codeBase "file:${was.install.root}/installedApps/myApp.ear/-"{ &lt;br /&gt;permission java.security.AllPermission; &lt;br /&gt;}; &lt;br /&gt;where myApp.ear is the application name.&lt;br /&gt;&lt;br /&gt;A was.policy file does not exist in the application/META-INF directory, while deploying the application to the server.&lt;br /&gt;Check for syntax errors in the was.policy file in theapplication\META-INF directory and make sure the application ear file name is given correctly. &lt;br /&gt;Create a was.policy file in the EAR of the application containing the problem enterprise bean, under the application\META-INF directory with the following contents:&lt;br /&gt;// WebSphere Application Server Security Policy for the application you are running&lt;br /&gt;grant codeBase "file:myApp.ear" &lt;br /&gt;{ &lt;br /&gt;permission java.security.AllPermission; &lt;br /&gt;}; &lt;br /&gt;.&lt;br /&gt;&lt;br /&gt;Exception: Class must implement the inherited abstract method AnnuityHolder20BeanCacheEntry_25ce2e23.setACustEmail(String) &lt;br /&gt;&lt;br /&gt;The following error might appear when you use the Application Server Toolkit (ASTK) to regenerate deployment code. &lt;br /&gt;&lt;br /&gt;Description:Class must implement the inherited abstract method &lt;br /&gt;AnnuityHolder20BeanCacheEntry_25ce2e23.setACustEmail(String)&lt;br /&gt;On Resource:AnnuityHolder20BeanCacheEntryImpl_25ce2e23.java&lt;br /&gt;In Folder:Annuity20EJB/ejbModule/com/ibm/wssvt/tc/pli/ejb/websphere_deploy/DB2UDBNT_V72_1This error occurs because when you regenerate the deployment code, the old code is not deleted. &lt;br /&gt;&lt;br /&gt;To correct this problem delete the folder com.ibm.wssvt.tc.pli.ejb.websphere_deploy.DB2UDBNT_V72_1&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Question 4: A WSAS administrator notices the following error in the SystemOut.log:&lt;br /&gt;&lt;br /&gt;javax.jms.InvalidDestinationException:&lt;br /&gt;MQJMS0003: Destination not understood or no longer valid.&lt;br /&gt;&lt;br /&gt;Which of the following could have caused this error?&lt;br /&gt;&lt;br /&gt;A. The JMS destination requires IIOP protocol for access. The JMS client is using the default JMS message protocol.&lt;br /&gt;B. The JMS destination is running on a non-WebSphere environment.&lt;br /&gt;C. The JMS destination was accidentally deleted.&lt;br /&gt;D. The JNDI binding to the destination was changed.&lt;br /&gt;E. The JMS destination is listening on a non standard TCP port.&lt;br /&gt;me: http://www-1.ibm.com/support/docview.wss?uid=swg1IY60708&lt;br /&gt;PROBLEM SUMMARY:&lt;br /&gt;This problem is caused by using JMS interfaces to access MQ JMS&lt;br /&gt;classes (i.e. casting a com.ibm.mq.MQQueue to a&lt;br /&gt;javax.jms.Queue).&lt;br /&gt;&lt;br /&gt;The use of an (instanceof MQQueue) test was returning false&lt;br /&gt;when an MQQueue object had been cast as a javax.jms.Queue. The&lt;br /&gt;logic then treated this as an invalid object, and threw an&lt;br /&gt;InvalidDestinationException.&lt;br /&gt;&lt;br /&gt;Question 5: An administrator manages a WSAS deployment for a stock brokerage firm. The firm receives stock feeds from several exchanges. The current WebSphere Express configuration is running into performance issues as more stock feeds are added. Which of the following are valid approaches to address the problem?&lt;br /&gt;&lt;br /&gt;A. Increase the weight assigned to the node running the Express configuration.&lt;br /&gt;B. Run standalone JMS servers using the Network Configuration.&lt;br /&gt;C. Reduce the frequency of commits to disk.&lt;br /&gt;D. Increase the JVM garbage collection interval.&lt;br /&gt;E. Throttle the rate at which stock feeds arrive by using the WSAS live feed manager.&lt;br /&gt;Question 6: A JavaMail application running on a WSAS server is throwing "name not found" JNDI exceptions. Which of the following are valid resolutions for this problem?&lt;br /&gt;&lt;br /&gt;A. Ensure recipient's email address is valid.&lt;br /&gt;B. Ensure the SMTP or POP3 username is registered in JNDI name space.&lt;br /&gt;C. Ensure the JavaMail security deployment descriptors allow SMTP relaying.&lt;br /&gt;D. Ensure the JavaMail session object name is registered in the application servers name space using the administrative console.&lt;br /&gt;E. Ensure the sender's email address is not on a SPAM block list.&lt;br /&gt;&lt;br /&gt;Question 7: Which of the following changes to the session database will improve the performance of the WSAS session management module?&lt;br /&gt;&lt;br /&gt;A. Striping the database across multiple disk drives&lt;br /&gt;B. Database buffer pool tuning&lt;br /&gt;C. Creating database index on session ID&lt;br /&gt;D. Using multi-row sessions&lt;br /&gt;E. Using database generated physical row ID instead of WSAS generated session ID&lt;br /&gt;Question 8: A WSAS application has modules that depend on native code using Java's JNI facility. Which of the following are valid approaches to deploy this application?&lt;br /&gt;&lt;br /&gt;A. Put the modules using JNI on a static classpath.&lt;br /&gt;B. For the application classloader, turn on the JNI mode.&lt;br /&gt;C. Copy the modules using JNI to the WEB-INF/lib/jni directory.&lt;br /&gt;D. Put the application modules on the classpath of the JNIClassLoader.&lt;br /&gt;E. Setup a module classloader with the native library path on its classpath.&lt;br /&gt;Question 9: An administrator at a WSAS site needs to setup strong security such that only well known Web clients are allowed access. Which of the following are valid methods to meet this goal?&lt;br /&gt;&lt;br /&gt;A. Use Web client IP based access control in WSAS HTTP server.&lt;br /&gt;B. Turn on SSL based encryption in the WSAS HTTP server.&lt;br /&gt;C. Use Web client certificates that are signed by a Certificate Authority (CA) trusted by the WSAS HTTP server.&lt;br /&gt;D. Use realm based HTTP digest authentication between the Web clients and WSAS server.&lt;br /&gt;E. Turn on HTTP cookie based Web client tracking in the WSAS HTTP server.&lt;br /&gt;Question 10: A WSAS application server has been running normally for several weeks when the associated Node Agent server crashes. Which of the following situations will result from this server failure?&lt;br /&gt;&lt;br /&gt;A. The application server configuration data cannot be updated.&lt;br /&gt;B. The WSAS cell can not be reconfigured till the attached Node Agent is restarted.&lt;br /&gt;C. The application server JVM will stop soon after.&lt;br /&gt;D. From other nodes, remote EJB invocations will stop working.&lt;br /&gt;E. The message driven beans (MDB) will no longer be accessible.&lt;br /&gt;Question 11: Which of the following steps must be completed in order to use the WSAS Administrative Console?&lt;br /&gt;&lt;br /&gt;A. Configure the password used to access the Deployment Manager using the wspasswd tool.&lt;br /&gt;B. Complete the installation of the Deployment Manager using the dmgrSetup tool.&lt;br /&gt;C. Install the J2EE application contained in adminconsole.ear.&lt;br /&gt;D. Ensure the Deployment Manager is running via startManager tool.&lt;br /&gt;E. Configure the administrative database used by the Deployment Manager using the dmgrDatabase tool.&lt;br /&gt;Question 12: To distribute workload across a cluster of WSAS servers, an administrator would like to use an external hardware loadbalancer instead of using WSAS plug-in based load balancing. Which of the following setup methods would allow an external hardware loadbalancer to be used?&lt;br /&gt;&lt;br /&gt;A. In the DNS A entry, point to the hardware loadbalancer.&lt;br /&gt;B. Modify the loadbalancer-cfg.xml and specify the Ethernet MAC address of the hardware loadbalancer.&lt;br /&gt;C. Configure the hardware loadbalancer to redirect to port 80 of WSAS HTTP server.&lt;br /&gt;D. In the plugin-cfg.xml specify the ClusterAddress to point to the IP of the hardware loadbalancer.&lt;br /&gt;E. Install the external loadbalancer extensions module in the WSAS cluster manger.&lt;br /&gt;Question 13: A WSAS administrator at an insurance exchange, is trying to setup access to a WebSphere nameserver from a BEA WebLogic application server environment. Which of the following are valid approaches to address this issue?&lt;br /&gt;&lt;br /&gt;A. Use a corbaloc URL that has an object key of NameServiceServerRoot&lt;br /&gt;B. Setup a JNDI server proxy for the WSAS nameserver.&lt;br /&gt;C. Export the WSAS namespace using the CORBA CosNaming import facility.&lt;br /&gt;D. Use a remoteCorbaProvider URL that points to a valid WSAS bootstrap server.&lt;br /&gt;E. Use the J2EE Interoperable Naming Service (INS).&lt;br /&gt;Question 14: A WSAS administrator is performing a full application upgrade. The current version of the application has several bindings that need to be merged with the bindings from the new version of the application. Which of the following statements about the merge process supported by WSAS are valid?&lt;br /&gt;&lt;br /&gt;A. If new bindings are not present for existing application artifacts, then the current installed version’s bindings will be used.&lt;br /&gt;B. If the bindings conflict and a conflict resolution script is specified, the resolution script would be used to resolve the conflicts.&lt;br /&gt;C. If the new version has bindings for application artifacts, then these will be part of the merged binding information.&lt;br /&gt;D. If bindings are not present in the old version and if the default binding generation option is disabled, then the default bindings will be part of the merged binding information.&lt;br /&gt;E. The administrator has the opportunity to change any of the merged deployment bindings before finally applying the upgrade.&lt;br /&gt;Question 15: Which of the following WSAS configuration options require the installation of a Web server plug-in?&lt;br /&gt;&lt;br /&gt;A. To connect with WSAS XML Web Services&lt;br /&gt;B. To increase the performance of the WSAS servlet container&lt;br /&gt;C. To run a WSAS instance inside the firewall&lt;br /&gt;D. To connect with the WSAS Tivoli performance viewer&lt;br /&gt;E. To connect with the EJB container in WSAS using Web transport&lt;br /&gt;Question 16: A B2B Web site uses HTTP/SSL for all requests from the Web client. The WSAS administrator wants to take advantage of this setup by using SSL based session ID for tracking user sessions. Which of the following scenarios would cause SSL based session tracking to not work?&lt;br /&gt;&lt;br /&gt;A. Cookies or URL rewriting is not used to maintain session affinity in a clustered environment.&lt;br /&gt;B. The SSL session ID for some Web clients is not compatible with WSAS session ID format.&lt;br /&gt;C. The Web client is using certificate-based client-authentication.&lt;br /&gt;D. Web browsers might not leave the SSL session ID active long enough to be useful as a mechanism for session tracking.&lt;br /&gt;E. If the SSL version 2 protocol is being used, it does not generate a SSL session ID.&lt;br /&gt;Question 17: Which of the following situations can cause the WSAS EJB container to generate a system core dump file on an AIX machine running an EJB application?&lt;br /&gt;&lt;br /&gt;A. The EJB container was sent a HUP POSIX signal.&lt;br /&gt;B. The IBM Tivoli EJB resource monitoring agent embedded in the EJB container generated log events in the system core file.&lt;br /&gt;C. The WSAS debug adapter could not attach to the EJB container JVM and, therefore, created a system core file.&lt;br /&gt;D. The JNI component invoked by an EJB had a memory related bug.&lt;br /&gt;E. The stateful EJBs were passivated into the disk-based system core file.&lt;br /&gt;Question 18: A WSAS administrator observes that many incoming connections to the ORB used for remote IIOP requests to EJBs are being rejected. Which of the following are valid tuning options for the WebSphere ORB?&lt;br /&gt;&lt;br /&gt;A. Increase the connection pool size in the ORB.&lt;br /&gt;B. Use persistent connections in the ORB.&lt;br /&gt;C. Increase the listen queue length specified by com.ibm.CORBA.ServerSocketQueueDepth.&lt;br /&gt;D. Increase the connection keep-alive timeout.&lt;br /&gt;E. Use UDP instead of TCP for RMI/IIOP connections to the ORB.&lt;br /&gt;me: com.ibm.CORBA.ServerSocketQueueDepth &lt;br /&gt;This property corresponds to the length of the TCP/IP stack listen queue and prevents WebSphere Application Server from rejecting requests when there is not space in the listen queue. If there are several simultaneous clients connecting to the server-side ORB, you can increase this parameter to support up to 1000 clients. The default value is 50. A valid range is between 50 and the maximum Java int value. &lt;br /&gt;Question 19: An administrator managing a WSAS node, notices the following error in WSAS system log when an application server tries to start up:&lt;br /&gt;&lt;br /&gt;WsServer E WSVR0003E: Server WebHAbbMember3 failed to start&lt;br /&gt;com.ibm.ws.exception.RuntimeError&lt;br /&gt;at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:227)&lt;br /&gt;at&lt;br /&gt;com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:3&lt;br /&gt;43)&lt;br /&gt;at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)&lt;br /&gt;at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:180)&lt;br /&gt;at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)&lt;br /&gt;at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)&lt;br /&gt;at java.lang.reflect.Method.invoke(Native Method)&lt;br /&gt;at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)&lt;br /&gt;---- Begin backtrace for nested exception&lt;br /&gt;com.ibm.ejs.EJSException: Could not register with Location Service Daemon;&lt;br /&gt;nested exception is:&lt;br /&gt;org.omg.CORBA.TRANSIENT: Host unreachable:&lt;br /&gt;connect:host=10.2.90.84,port=9900 minor code: 4942F301 completed: No&lt;br /&gt;org.omg.CORBA.TRANSIENT: Host unreachable: connect:host=10.2.90.84,port=9900&lt;br /&gt;minor code: 4942F301 completed: No&lt;br /&gt;at&lt;br /&gt;com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase&lt;br /&gt;.java:338)&lt;br /&gt;&lt;br /&gt;Which of the following situations could cause this error?&lt;br /&gt;&lt;br /&gt;A. The WSAS ORB failed to start because ORB port 9900 is in use.&lt;br /&gt;B. The EJB server with IP 10.2.90.84 is not running.&lt;br /&gt;C. The Node Agent is not running.&lt;br /&gt;D. The EJB container failed to authenticate with Location Service Daemon (LSD) and hence EJBs could not be registered with LSD.&lt;br /&gt;E. The Deployment Manager is not running.&lt;br /&gt;me: Software &gt; Application Servers &gt; &lt;br /&gt;&lt;br /&gt;Server not starting after enabling Security with exceptions WSVR0003E and ADMC0019E &lt;br /&gt;Technote (FAQ) &lt;br /&gt;&lt;br /&gt;Problem &lt;br /&gt;After enabling security, the application server does not start up (in this case, DMGR and nodeAgent comes up but not the servers). &lt;br /&gt;&lt;br /&gt;Cause &lt;br /&gt;When security is enabled, the SOAP connector needs to obtain the Secure Sockets Layer (SSL) configuration to intialize the SSL server socket. The error occurs when no SSL configuration is specified for the secure SOAP connector. &lt;br /&gt;The error stack would look like this:&lt;br /&gt;[12/27/06 14:19:33:297 EST] e28a61 WsServer E WSVR0003E: Server &lt;br /&gt;server_name failed to start &lt;br /&gt;com.ibm.ws.exception.RuntimeError &lt;br /&gt;at &lt;br /&gt;com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurit &lt;br /&gt;yComponentImpl.java:206) &lt;br /&gt;&lt;br /&gt;Question 20: An administrator deploying EJBs in a WSAS cell does not want to hardwire the path to the EJB objects or host:port of the nameserver in the JNDI name space. Which of the following bindings can the administrator use?&lt;br /&gt;&lt;br /&gt;A. Indirect Name Binding&lt;br /&gt;B. Simple Name Binding&lt;br /&gt;C. CORBA Name Binding&lt;br /&gt;D. Compound Name Binding&lt;br /&gt;E. Federated Name Binding&lt;br /&gt;Question 21: An administrator at an application hosting company needs to setup a WSAS deployment topology for easy site maintenance. The site needs to be frequently upgraded to meet the throughput requirements of the hosted applications. Which of the following deployment topologies represent valid choices for meeting the above requirement?&lt;br /&gt;&lt;br /&gt;A. Setup WSAS with multiple hot standby servers.&lt;br /&gt;B. Setup a horizontally scalable WSAS topology with an IP sprayer at the network edge.&lt;br /&gt;C. Create a WSAS cell with a process pair topology.&lt;br /&gt;D. Setup WSAS on a SMP machine with a large number of CPUs.&lt;br /&gt;E. Mirror the WSAS instances on a secondary box.&lt;br /&gt;Question 22: A WSAS administrator is trying to choose between several different global sharing policies for cache replication in WSAS. Which of the following are valid tradeoffs in selecting a policy?&lt;br /&gt;&lt;br /&gt;A. The Not Shared policy offers better overall memory utilization.&lt;br /&gt;B. A disadvantage of the Push policy is that caches are not synchronized.&lt;br /&gt;C. With Push and Pull policy, retrieving the content from the remote cache can take longer compared to the local cache.&lt;br /&gt;D. An advantage of the Push and Pull policy is that the content is distributed immediately.&lt;br /&gt;E. The Synchronous policy offers the best cache coherency.&lt;br /&gt;Question 23: A WSAS administrator is having trouble keeping the Web site available when the production database server goes down. The WSAS based Web site uses the production database for session persistence. Which of the following are valid approaches to increase the availability of the site while still providing session persistence?&lt;br /&gt;&lt;br /&gt;A. Use WebSphere internal messaging instead of database persistence&lt;br /&gt;B. Use database replication&lt;br /&gt;C. Use WebSphere Process Group based sessions&lt;br /&gt;D. Use WebSphere cluster with in-memory only sessions&lt;br /&gt;E. Use distributed coordination engine-based sessions&lt;br /&gt;Question 24: A WSAS administrator has been struggling to get the WebSphere installation to work as expected. After several re-tries and re-installs, the administrator decides to contact IBM WebSphere Technical Support. Which of the following are valid approaches to communicating information about a current WSAS installation to IBM Support?&lt;br /&gt;&lt;br /&gt;A. Run the collector.sh tool and send the &lt;hostname&gt;-ND|Base-WASenv.jar file to IBM Support.&lt;br /&gt;B. Create a disk image of the WSAS machine and ship it to IBM Support.&lt;br /&gt;C. Run the validate-wsas-env perl script and let it automatically send an email to IBM Support.&lt;br /&gt;D. Create a tar ball of the current WSAS install-logs directory and send it to IBM Support.&lt;br /&gt;E. Run the WSAS LogAnalyzer with the Failure Data Capture Log option and send the logs to IBM Support.&lt;br /&gt;Question 25: Which of the following server types are supported by WSAS?&lt;br /&gt;&lt;br /&gt;A. LDAP Server&lt;br /&gt;B. Application Server&lt;br /&gt;C. JMS Server&lt;br /&gt;D. CORBA Object Server&lt;br /&gt;E. Event Server&lt;br /&gt;Question 26: A WSAS based supply-chain application, needs to deployed onsite at several suppliers' data centers. Multiple authentication schemes are in use at these data centers. Short of customizing the application for each supplier, which of the following are valid approaches to deal with heterogeneous authentication schemes?&lt;br /&gt;&lt;br /&gt;A. Use security role mapping at each supplier&lt;br /&gt;B. Use WS-Security Gateway&lt;br /&gt;C. Use CSIv2 Single Sign On&lt;br /&gt;D. Use JAAS-based login modules&lt;br /&gt;E. Use the RunAs deployment descriptor&lt;br /&gt;Question 27: Which of the following are valid WSAS classloaders?&lt;br /&gt;&lt;br /&gt;A. WebSphere JNDI classloader&lt;br /&gt;B. JCA Resource Archive classloader&lt;br /&gt;C. Web Archive classloader&lt;br /&gt;D. EJB Archive classloader&lt;br /&gt;E. JMS Archive classloader&lt;br /&gt;Question 28: Which of the following components can be declared in a WSAS EAR file?&lt;br /&gt;&lt;br /&gt;A. JDBC DataSource objects&lt;br /&gt;B. JMX MBeans&lt;br /&gt;C. JMS ConnectionFactory and Destination objects&lt;br /&gt;D. Classes that are triggered when an application is deployed or un-deployed&lt;br /&gt;E. Native libraries required to implement a JCA resource adapter&lt;br /&gt;Question 29: Which of the following are valid reasons for choosing WebSphere MQ JMS provider over the WebSphere embedded JMS provider?&lt;br /&gt;&lt;br /&gt;A. Multi-broker capability&lt;br /&gt;B. Support for communication with non-JMS destinations&lt;br /&gt;C. Full compliance with the J2EE 1.3 specifications&lt;br /&gt;D. Support for clusters&lt;br /&gt;E. Support for Point-to-Point messaging&lt;br /&gt;Question 29: A WSAS administrator recently encountered a disaster scenario whereby the entire cluster failed causing all the remote EJBs to be unavailable. Which of the following are valid approaches to deal with this?&lt;br /&gt;&lt;br /&gt;A. Set up a cluster watchdog to restart the cluster.&lt;br /&gt;B. Set up a backup cluster.&lt;br /&gt;C. Run more EJB servers in the cluster.&lt;br /&gt;D. Reduce the cluster failure probability by using weighted round-robin workload management between cluster members.&lt;br /&gt;E. Use a hardware workload balancer instead of WSAS software based workload management.&lt;br /&gt;Question 31: A WSAS administrator checks the status of the servers on the local node using the command below:&lt;br /&gt;&lt;br /&gt;$ serverStatus.sh -all&lt;br /&gt;&lt;br /&gt;Which of the following statements provides a possible result of the command execution?&lt;br /&gt;&lt;br /&gt;A. The status of all the servers excluding the node agent are reported.&lt;br /&gt;B. The command reads the node’s local serverindex.xml configuration file to determine the JMX connector ports for each of the servers on the node.&lt;br /&gt;C. The &lt;WAS_HOME&gt;/logs/allServerStatus.log contains the status of all the servers.&lt;br /&gt;D. The command will fail if it is not run from the bin directory of the server installation root: &lt;WAS_HOME&gt;/bin.&lt;br /&gt;E. The command bypasses any WebSphere security that the administrator might have setup.&lt;br /&gt;Question 32: A popular sports Web site running WSAS uses local session management. The administrator notices that on the days when key matches are played, the WSAS server crashes frequently with out of memory exceptions. Which of the following could cause this problem?&lt;br /&gt;&lt;br /&gt;A. The Allow overflow setting on the session manager is enabled.&lt;br /&gt;B. The WSAS instance is running out of TCP buffer space when handling a large number of simultaneous connections.&lt;br /&gt;C. WSAS is running out of SWAP space.&lt;br /&gt;D. The first session cache is using the default settings which permit an unlimited number of in-memory sessions.&lt;br /&gt;E. The WSAS JVM is configured to use the mark and sweep heap garbage collector.&lt;br /&gt;Question 33: A WSAS administrator notices the following exception when deploying a J2EE application in WSAS:&lt;br /&gt;&lt;br /&gt;ConnectionFac E J2CA0102E: Invalid EJB component: Cannot use an EJB module with version 1.1 using The Relational Resource Adapter&lt;br /&gt;&lt;br /&gt;Which of the following could cause this problem?&lt;br /&gt;&lt;br /&gt;A. An EJB developed to the EJB 1.1 specification is deployed with a WebSphere Application Server Version 5 J2C-compliant data source.&lt;br /&gt;B. The EJB module is using WSAS version 1.1 style deployment descriptors.&lt;br /&gt;C. The EJB interfaces were compiled using EJB 1.1 based WSAS rmic compiler.&lt;br /&gt;D. The WSAS JCA resource is compliant with EJB 2.0 specification only.&lt;br /&gt;E. The WSAS JCA container needs to be configured to EJB 1.1 specification support.&lt;br /&gt;me: This error occurs when an enterprise bean developed to the EJB 1.1 specification is deployed with a WebSphere Application Server V5 J2C-compliant data source, which is the default data source. By default, persistent enterprise beans created under WebSphere Application Server V4.0's using the fulfill the EJB 1.1 specification. To run on WebSphere Application Server V5, these enterprise beans must be associated with a WebSphere Application Server V4.0-type data source.&lt;br /&gt;Question 34: An administrator needs to install WSAS on a Windows 2003 server machine. Which of the following are valid installation steps for a Windows 2003 install of WSAS?&lt;br /&gt;&lt;br /&gt;A. Elect to install an xinetd.d entry for WSAS startup&lt;br /&gt;B. Setup a Web administrator account using htpasswd utility&lt;br /&gt;C. Modify /etc/profile to include a path to WSAS installation&lt;br /&gt;D. Elect to run WSAS as a service&lt;br /&gt;E. Elect to setup a Windows Active Directory instance for managing WSAS access control lists&lt;br /&gt;Question 35: Which of the following statements correctly describe the WSAS installation defined by the deployment directory structure below?&lt;br /&gt;&lt;br /&gt;cells/cellA/applications/bank.ear/ contains -&lt;br /&gt;commerce.ear&lt;br /&gt;cells/cellA/applications/bank.ear/deployments/bank contains -&lt;br /&gt;deployment.xml&lt;br /&gt;META-INF/application.xml&lt;br /&gt;META-INF/ibm-application-bnd.xmi&lt;br /&gt;META-INF/ibm-application-ext.xmi&lt;br /&gt;META-INF/was.policy&lt;br /&gt;&lt;br /&gt;A. The META-INF/application.xml specifies the allocation of application modules to application servers.&lt;br /&gt;B. The META-INF/was.policy specifies the application-specific Java 2 security configuration.&lt;br /&gt;C. The application EAR file name commerce.ear is invalid as it does not match with the application directory name bank.ear&lt;br /&gt;D. The deployment.xml specifies the module startup order.&lt;br /&gt;E. The META-INF/ibm-application-ext.xmi specifies all the IBM-specific external resources used by the application.&lt;br /&gt;Question 36: Which of the following are valid approaches to configure connectivity from a WSAS server to a legacy IBM CICS system?&lt;br /&gt;&lt;br /&gt;A. From the Administrative Console, install a CICS RAR archive.&lt;br /&gt;B. Run a WSAS object request broker on the CICS machine.&lt;br /&gt;C. At installation time, configure a WebSphere CICS server.&lt;br /&gt;D. From the Deployment Manager, install a CICS WAR archive and CICS native dlls.&lt;br /&gt;Question 37: In order to secure EJBs in a WSAS EJB container, which of the following steps must be completed?&lt;br /&gt;&lt;br /&gt;A. Define J2EE roles for EJB modules&lt;br /&gt;B. Specify WS-Security principal mappings for valid EJB roles&lt;br /&gt;C. Create Kerberos credentials for EJB users&lt;br /&gt;D. Assign EJB method permissions&lt;br /&gt;E. Setup WebSphere ACL on EJB interfaces&lt;br /&gt;Question 38: Which of the following are valid statements about session affinity in WSAS?&lt;br /&gt;&lt;br /&gt;A. Session affinity only works with persistent sessions.&lt;br /&gt;B. The JSESSIONID cookie contains the server ID for session affinity.&lt;br /&gt;C. The URL rewriting session tracking method can not be used when session affinity is desired.&lt;br /&gt;D. Session affinity ensures a user agent is always routed to the same JVM in a WSAS cluster.&lt;br /&gt;E. WSAS supports session affinity for only desktop Web user agents and not for mobile Web user agents.&lt;br /&gt;Question 39: Which of the following are valid statements about session failover in WSAS?&lt;br /&gt;&lt;br /&gt;A. Session failover can improve the overall performance of a WSAS cell.&lt;br /&gt;B. Session failover ensures a WSAS session can never timeout.&lt;br /&gt;C. Session persistence must be enabled for session failover.&lt;br /&gt;D. Session failover only works in a WSAS cluster configuration.&lt;br /&gt;E. Session failover can be setup on a single node WSAS configuration provided hardware clustering is available.&lt;br /&gt;Question 40: A WSAS administrator while monitoring the performance of a WSAS application, observed the following statistics:&lt;br /&gt;&lt;br /&gt;The Web Server can process 50 requests in 100 ms.&lt;br /&gt;The Web container can process 18 requests in 300 ms.&lt;br /&gt;The EJB container can process 9 requests in 150 ms.&lt;br /&gt;The datasource can process 40 requests in 50 ms.&lt;br /&gt;&lt;br /&gt;Which of the following are valid tuning strategies to remove immediate bottlenecks and improve the overall system performance?&lt;br /&gt;&lt;br /&gt;A. If possible use read-only EJB beans.&lt;br /&gt;B. Setup dynamic caching in the Web Container.&lt;br /&gt;C. Setup a kernel mode Web server.&lt;br /&gt;D. Add more CPUs to the database machine.&lt;br /&gt;E. Use a hardware loadbalancer.&lt;br /&gt;Question 41: Which of the following WSAS configuration files require manual editing in order to make configuration changes?&lt;br /&gt;&lt;br /&gt;A. cell.xml&lt;br /&gt;B. admin-authz.xml&lt;br /&gt;C. integral-jms-authorizations.xml&lt;br /&gt;D. multibroker.xml&lt;br /&gt;E. variables.xml&lt;br /&gt;Question 42: Which of the following approaches can a WSAS administrator take to configure the Web server plug-in so that it sends Web requests to all the HTTP servers in the cell?&lt;br /&gt;&lt;br /&gt;A. Use the deployWebPlugin tool to automate discovery and configuration of all HTTP servers in the cell.&lt;br /&gt;B. First run the gencellplugin -all tool and then run the setupplugin command line tool.&lt;br /&gt;C. Use the GenPluginCfg command line tool&lt;br /&gt;D. Run the wsadmin -webplugin -all command line tool&lt;br /&gt;E. Use the wsinstance tool on each node to create it's local Web server plug-in configuration&lt;br /&gt;Question 43: A WSAS administrator notices frequent StaleConnectionException from a JDBC WSAS Version 4 resource. Which of the following are valid causes for this problem?&lt;br /&gt;&lt;br /&gt;A. The JDBC database is reaping the connection.&lt;br /&gt;B. The JDBC connection orphan timeout is too small.&lt;br /&gt;C. The TCP keepalive timeout for the JDBC connection was exceeded.&lt;br /&gt;D. A transaction was rolled back on the JDBC connection and thus marked as stale.&lt;br /&gt;E. A duplicate JDBC connection was established causing the old connection to become stale.&lt;br /&gt;&lt;br /&gt;me: The application tries to get a connection and fails, as when the database is not started. &lt;br /&gt;A connection is no longer usable because of a database failure. When an application tries to use a previously obtained connection, the connection is no longer valid. In this case, all connections currently in use by the application can get this error when they try to use the connection. &lt;br /&gt;The connection is orphaned (because the application had not used it in at most two times the value of the unused timeout setting) and the application tries to use the orphaned connection. This case applies only to Version 4.0 data sources. &lt;br /&gt;The application tries to use a JDBC resource, such as a statement, obtained on a stale connection. &lt;br /&gt;A connection is closed by the Version 4.0 data source auto connection cleanup and is no longer usable. Auto connection cleanup is the standard mode in which connection management operates. This mode indicates that at the end of a transaction, the transaction manager closes all connections enlisted in that transaction. This enables the transaction manager to ensure that connections are not held for excessive periods of time and that the pool does not reach its maximum number of connections prematurely. &lt;br /&gt;&lt;br /&gt;Question 44: A company manages a digital marketplace portal which processes high value transactions ($1 million and higher) in small volumes. Which of the following WSAS topologies are valid choices for the portal?&lt;br /&gt;&lt;br /&gt;A. Setup a network deployment topology with memory-to-memory replication of session state.&lt;br /&gt;B. Setup a WSAS cluster on a 64-CPU SMP box to handle the high value transactions.&lt;br /&gt;C. Setup a front-end WSAS Web redirector, spraying requests to multiple WSAS instances.&lt;br /&gt;D. Setup a cluster of WSAS nodes and have them use database based session persistence.&lt;br /&gt;E. Setup a WSAS cluster with process pair topology.&lt;br /&gt;&lt;br /&gt;Question 45: Which of the following files store WSAS extensions to standard J2EE deployment descriptors?&lt;br /&gt;&lt;br /&gt;A. ibm-ejb-mdb-bean.xmi&lt;br /&gt;B. ibm-ejb-jndi-ext.xmi&lt;br /&gt;C. ibm-ejb-jar-bnd.xmi&lt;br /&gt;D. ibm-ejb-jar.xml&lt;br /&gt;E. ibm-web-session.xmi&lt;br /&gt;Question 46: When using Generic JMS providers in WSAS, which of the following valid limitations exist?&lt;br /&gt;&lt;br /&gt;A. The provider may not provide JMS tools that can register its objects&lt;br /&gt;in the WebSphere name space.&lt;br /&gt;B. The generic JMS providers do not allow integration into non-WebSphere MQ based environments.&lt;br /&gt;C. The generic JMS providers can not link to the WebSphere security infrastructure.&lt;br /&gt;D. JMS resources can not be managed using WebSphere administration tools.&lt;br /&gt;E. The generic JMS providers do not support Message Driven Beans (MDB).&lt;br /&gt;Question 47: Which of the following are valid approaches to change the JDBC data sources contained in the system partition of the WSAS JNDI namespace?&lt;br /&gt;&lt;br /&gt;A. Use the JNDI APIs directly&lt;br /&gt;B. Use the IBM Tivoli JNDI system manager&lt;br /&gt;C. Modify the WSAS system partition database using the IBM DB2 system tool&lt;br /&gt;D. Use the JNDI administration client&lt;br /&gt;E. Use the IBM data source manager tool&lt;br /&gt;Question 48: Which of the following are valid statements about WSAS classloaders?&lt;br /&gt;&lt;br /&gt;A. The system classloader is responsible for loading the code that is found on java.class.systempath.&lt;br /&gt;B. The system classloader is the parent for the extensions classloader.&lt;br /&gt;C. Each Java class must be loaded by a classloader.&lt;br /&gt;D. The bootstrap classloader is responsible for loading the EJB dependency JARs.&lt;br /&gt;E. A class loaded by a specific classloader can reference classes that this&lt;br /&gt;classloader or its children classloaders load.&lt;br /&gt;Question 49: A Web application (servlet context /bank) contained in the webbank.war module has been deployed on a WSAS application server (www.webank.com). However when a user agent tries to access the application (at http://www.webbank.com/bank), it gets a page not found exception. Which of the following could cause this problem?&lt;br /&gt;&lt;br /&gt;A. The webbank.war module has not been bound to the WSAS virtual host (www.webank.com).&lt;br /&gt;B. The war module does not have the deployment file bank.xml in it.&lt;br /&gt;C. The war file name and the server host name do not match.&lt;br /&gt;D. The user agent needs to use a secure URL like https://www.webbank.com/bank to access the banking application.&lt;br /&gt;E. The WSAS Web plug-in needs to be regenerated for the war module.&lt;br /&gt;Question 50: Which of the following statements correctly describe node usage in WSAS?&lt;br /&gt;&lt;br /&gt;A. A node is a logical grouping of WebSphere-managed server processes.&lt;br /&gt;B. A node is associated with one physical installation of WebSphere Application Server.&lt;br /&gt;C. A node can contain multiple WSAS cells.&lt;br /&gt;D. In the Express and Base configurations of WebSphere Application Server, there is only one node.&lt;br /&gt;E. A node can only support embedded HTTP transport.&lt;br /&gt;Question 51: Which of the following steps must be completed in order to correlate log files from multiple WSAS processes?&lt;br /&gt;&lt;br /&gt;A. From the application server toolkit, merge the imported log files into a single file.&lt;br /&gt;B. From the application server toolkit, select the type of correlation desired.&lt;br /&gt;C. From the application server toolkit, run the log file cruncher.&lt;br /&gt;D. From the application server toolkit, import all the log files to correlate.&lt;br /&gt;E. From the application server toolkit, execute the log file record filter.&lt;br /&gt;Question 52: Which of the following TCP ports can be specified during a WSAS installation?&lt;br /&gt;&lt;br /&gt;A. LDAP port&lt;br /&gt;B. JavaMail port&lt;br /&gt;C. ORB listener port&lt;br /&gt;D. FTP port&lt;br /&gt;E. Message Send Protocol (MSP) port&lt;br /&gt;&lt;br /&gt;Question 53: In which of the following cases, can the physical machine, configured to run the Web container, be up and running while the Web container is unavailable?&lt;br /&gt;&lt;br /&gt;A. Network cable is disconnected&lt;br /&gt;B. JVM crash&lt;br /&gt;C. Operating system crash&lt;br /&gt;D. Application server weight is inappropriate&lt;br /&gt;E. System memory board failure&lt;br /&gt;Question 54: Which of the following requirements must be met by WebSphere cluster members&lt;br /&gt;in order to participate in WSAS clustering?&lt;br /&gt;&lt;br /&gt;A. Have identical application components&lt;br /&gt;B. Have identical heap sizes&lt;br /&gt;C. Have identical JVM versions&lt;br /&gt;D. Have identical weights&lt;br /&gt;E. Have identical deployment descriptors&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-6137679901775639941?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/6137679901775639941/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=6137679901775639941' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6137679901775639941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/6137679901775639941'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2007/08/test-252.html' title='Test 252'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-114858934335264854</id><published>2006-05-26T02:02:00.000+05:30</published><updated>2006-05-26T02:05:43.353+05:30</updated><title type='text'>Logging Levels</title><content type='html'>The "Logging levels" table describes the different logging levels that you can set through the administrative console.&lt;br /&gt;Note: To view log events that are below the Detail level, you must enable the Diagnostic Trace Service. Log events that are at Detail level or above can be viewed in the SystemOut log, the IBM(R) Service log (when enabled), or the Diagnostic Trace Service (when enabled).&lt;br /&gt;Logging levels&lt;br /&gt;&lt;a href="http://photos1.blogger.com/blogger/6916/513/1600/loglevel.1.jpg"&gt;&lt;img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;" src="http://photos1.blogger.com/blogger/6916/513/320/loglevel.1.jpg" border="0" alt="" /&gt;&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-114858934335264854?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/114858934335264854/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=114858934335264854' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114858934335264854'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114858934335264854'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2006/05/logging-levels.html' title='Logging Levels'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-114735469017476384</id><published>2006-05-11T19:05:00.000+05:30</published><updated>2007-08-13T22:47:03.377+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Test 252'/><title type='text'>IBM Test 252</title><content type='html'>1. After changing the JNDI name of a datasource, what must be changed within an application using this datasource to keep them running correctly?&lt;br /&gt;A. The reference to resource mappings.&lt;br /&gt;B. The EJB references to match the new JNDI name.&lt;br /&gt;C. The name of the JDBC provider to match the new datasorce name.&lt;br /&gt;D. The datasources.xml file for the application.&lt;br /&gt;-A&lt;br /&gt;2. A security role has been mapped to the special group Everyone. What is the result of this action?&lt;br /&gt;A. Every user defined for the group has access to the resource.&lt;br /&gt;B. Everyone will be denied access to the resource.&lt;br /&gt;C. Every user has access to the resource.&lt;br /&gt;D. Anyone logged in has access to the resource.&lt;br /&gt;Security role to user and group mapping&lt;br /&gt;Use this page to map security roles to users. You can map roles to specific users, to specific groups, or to different categories.&lt;br /&gt;To view this administrative console page, click Applications &gt; Install New Application. While running the Application Installation Wizard, prompts display to help you map security roles to users or groups. To change role to user or group mappings for deployed applications, click Applications &gt; Enterprise Application &gt; deployed_application &gt; Security roles to user/group mapping.&lt;br /&gt;Everyone&lt;br /&gt;Specifies to map roles to everyone. Mapping a role to everyone means that anyone can access resources protected by this role, and essentially, there is no security.&lt;br /&gt;-D&lt;br /&gt;3. A WAR file in an enterprise application has been changed. How can a system administrator update it on the server with a minimal amount of work?&lt;br /&gt;A. Re-package the EAR file using Application Server Toolkit then use the "Update -&gt; Full application" function on the administrative console.&lt;br /&gt;B. Use the "Update -&gt; Single file" function of the Administrative console to replace the WAR file.&lt;br /&gt;C. Use the "Update -&gt; Single module" of the Administrative console to replace the WAR file.&lt;br /&gt;D. Use the "Update -&gt; Partial application" of the Administrative console to replace the WAR file.&lt;br /&gt;Single module&lt;br /&gt;Under Update options, specifies to replace a module in or add a module to an installed application. The module can be a Web module (.war file), enterprise bean module (EJB .jar file), or resource adapter module (connector .rar file).&lt;br /&gt;After selecting this option, specify whether the module is on a local or remote file system and the full path name of the module. The path provides the location of the updated module before installation. For information on Local file system and Remote file system, refer to the description of Full application above.&lt;br /&gt;-C&lt;br /&gt;If you select Update, you will be given with four options&lt;br /&gt;Full Application&lt;br /&gt;Single Module&lt;br /&gt;Single File&lt;br /&gt;Partial Application&lt;br /&gt;Full Application :&lt;br /&gt;Select this option to replace the enterprise archive (*.ear) file for an installed application. The uploaded enterprise archive replaces the existing installed application.&lt;br /&gt;Single module&lt;br /&gt;Select this option to update an existing module or to add a new module to the application. If the relative path to the module matches an existing path to a module in the installed application, the uploaded module replaces the existing module. If the relative path to the module does not exist in the installed application, the uploaded module is added to the application.&lt;br /&gt;Single file&lt;br /&gt;Select this option to update an existing file or to add a new file to the application. If the relative path to the file matches an existing path to a file in the installed application, the uploaded file replaces the existing file. If the relative path to the file does not exist in the installed application, the uploaded file is added to the application.&lt;br /&gt;Partial application&lt;br /&gt;Select this option to update or add several files to an application. Use a valid compressed file format such as .zip or .gzip. The compressed file is unzipped into the installed application directory. If the uploaded files exist in the application with the same paths and file names, the uploaded files replace the existing files. If the uploaded files do not exist, the files are added to the application. You can remove existing files from the installed application by specifying metadata in the compressed file.&lt;br /&gt;4. While performing a node federation, the addNode operation failed. From the following list of options, what would MOST likely induce this failure?&lt;br /&gt;A. The cell already exists&lt;br /&gt;B. The cell's deployment manager is running before the addNode command was run&lt;br /&gt;C. The name of the new node is not unique in the cell&lt;br /&gt;D. The addNode did not specify to carry over the applications&lt;br /&gt;-A&lt;br /&gt;5.Cluster creation requires the system administrator to specify the weight for a cluster member. This weight is significant because it is used in the WebSphere WLM runtime by the:&lt;br /&gt;A. Random scheduling algorithm&lt;br /&gt;B. Round Robin scheduling algorithm&lt;br /&gt;C. Both Random and Round Robin scheduling algorithm&lt;br /&gt;D. Weighted Random algorithm&lt;br /&gt;&lt;br /&gt;In the simplest case, the cluster contains only one server definition. In the case in which more than one server is defined, the plug-in will load balance across the defined servers using either a Round Robin or a Random algorithm. The default is Round Robin.&lt;br /&gt;LoadBalanceWeight (zero or one attribute for each Server)&lt;br /&gt;Specifies the weight associated with this server when the plug-in does weighted Round Robin load balancing. The starting value for a server can be any integer between 0 and 20. However, zero should be specified only for a server that is shut down.&lt;br /&gt;The algorithm for this attribute decrements all weights within the server cluster until all weights reach zero. After the weight specified for a particular server reaches zero, no more requests are routed to that server until all servers in the cluster have a weight of zero. After all servers reach zero, the weights for all servers in the cluster are reset and the algorithm starts over.&lt;br /&gt;When a server is shut down, it is recommended that you set the weight for that server to zero. The plug-in can then reset the weights of the servers that are still running, and maintain proper load balancing.&lt;br /&gt;The answer for this is Weighted Round Robin&lt;br /&gt;6. A new JDBC provider is being created in a cell in which the servers run on different operating systems. Which of the following scopes should be used?&lt;br /&gt;A. Cluster scope&lt;br /&gt;B. Server scope&lt;br /&gt;C. Node scope&lt;br /&gt;D. Cell scope&lt;br /&gt;??&lt;br /&gt;7. A system administrator is asked to help explain why a NameNotFoundException is happening while attempting to access an enterprise bean, data source, messaging resource, or other resource. What action would be the LEAST useful to do to explain the problem?&lt;br /&gt;A. Browse the properties of the target object in the administrative console, and verify that the JNDI name it specifies matches the JNDI name the client is using.&lt;br /&gt;B. Browse the properties of the target object in its deployment descriptor, and verify that the JNDI name it specifies matches the JNDI name the client is using.&lt;br /&gt;C. Determine if the object being looked up resides on a server different from the one from which the initial context was obtained since, in this case, the fully qualified name must be used.&lt;br /&gt;D. Use the showNameSpace utility to export the entire JNDI tree to determine if the desired resource is listed.&lt;br /&gt;Incorrect lookup name&lt;br /&gt;If you encounter a NameNotFoundException when trying to access an enterprise bean, data source, messaging resource, or other resource:&lt;br /&gt;Determine the cause of the NameNotFoundException.&lt;br /&gt;Browse the properties of the target object in the administrative console, and verify that the JNDI name it specifies matches the JNDI name the client is using.&lt;br /&gt;If you are looking up an object that resides on a server different from the one from which the initial context was obtained, you must use the fully qualified name.&lt;br /&gt;If access is from another server object such as a servlet accessing an enterprise bean and you are using the default context, not specifying the fully qualified JNDI name, you might get a NameNotFoundException if the object is hosted on a different server.&lt;br /&gt;If access is from a standalone client, it might be that the object you are attempting access is on a server different from the server from which you obtained the initial context.&lt;br /&gt;Use the fully-qualified JNDI name to correct the problem.&lt;br /&gt;If the object is in a single server, the fully-qualified JNDI name is as follows:&lt;br /&gt;cell/nodes/nodeName/servers/serverName/jndiName&lt;br /&gt;Restriction: Objects are not supported in this release.&lt;br /&gt;If the object is on a server cluster, the fully-qualified JNDI name is as follows:&lt;br /&gt;cell/clusters/clusterName/jndiName&lt;br /&gt;-A&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-114735469017476384?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/114735469017476384/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=114735469017476384' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114735469017476384'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114735469017476384'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2006/05/ibm-test-252.html' title='IBM Test 252'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7932682.post-114693295216472129</id><published>2006-05-06T21:55:00.000+05:30</published><updated>2007-08-13T22:47:33.484+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='WebSphere'/><title type='text'>WebSphere Administration</title><content type='html'>&lt;div align="center"&gt;&lt;strong&gt;WebSphere Administration&lt;/strong&gt;&lt;/div&gt;&lt;div align="justify"&gt;&lt;strong&gt;&lt;/strong&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;strong&gt;I would like to post some information on WebSphere Application Server Administration, starting from How to start, Wherer to Start, Installation Issues, Configuring, Performance Tuning.&lt;br /&gt;&lt;/div&gt;&lt;/strong&gt;&lt;div style="TEXT-ALIGN: center"&gt;&lt;strong&gt;-: Installation :-&lt;br /&gt;&lt;/strong&gt;&lt;div style="TEXT-ALIGN: justify"&gt;So, How to install WebSphere 6.0, Base/ND on Windows/Solaris?&lt;br /&gt;Recently I got to install and provide WAS on Solaris Hardware. The requirement was to provide a DEV enviroment for a development team. The demand was to provide WAS 6.0.2.5 on Solaris 10 Hardware. We have license of WAS 6.0.&lt;br /&gt;The installation process I have followed goes like this.&lt;br /&gt;1. Identification of Installation Topology.&lt;br /&gt;2. Preparing the Hardware for Installation.&lt;br /&gt;3. Installation Steps&lt;br /&gt;4. Post Installation Steps.&lt;br /&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;span style="FONT-WEIGHT: bold"&gt;1. Identification of Installation Topology.&lt;/span&gt;&lt;br /&gt;First we need to identify what is the installation topology. Means, How we have to proceed for installation. The scenarios for installation are&lt;br /&gt;* Scenario 1: Single-machine installation of WebSphere Application Server&lt;br /&gt;* Scenario 2: Single-machine installation of WebSphere Application Server and a Web server&lt;br /&gt;* Scenario 3: Two-machine installation of WebSphere Application Server and a Web server&lt;br /&gt;* Scenario 4: Creating multiple profiles that use one installation of WebSphere Application Server&lt;br /&gt;The Demand for my DEV Team matches Secnario 1.&lt;br /&gt;&lt;br /&gt;&lt;span style="FONT-WEIGHT: bold"&gt;2. Preparing the Hardware for Installation.&lt;/span&gt;&lt;br /&gt;Refer this link for this step&lt;br /&gt;&lt;a href="http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/txml_callappinstall.html"&gt;http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/&lt;br /&gt;txml_callappinstall.html&lt;/a&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;strong&gt;3. Installation Process&lt;br /&gt;&lt;/strong&gt;You have prepared the OS for the WAS Installation. Now it is the time to install WAS 6.0.&lt;br /&gt;You can do that manually, or you can develop script for this process. Before coming into the details of developing of script or manual installation, you need to know some more things. In Solaris, you cannot see the GUI. Everything will be at the command line and you have to chose non UI installation.&lt;br /&gt;For any software to install, you see different modes of installations, viz. Typical, Custom. When you are installation in the UI Mode, you can select the appropriate option. But, in a non UI mode how will you do that? You have to mention all your properties in a file and give that file, means pass that file to the installation process, called RESPONSE_FILE.&lt;br /&gt;To install WAS on Solaris, you need to select the &lt;strong&gt;silent installation process&lt;/strong&gt;.&lt;br /&gt;These are the steps:&lt;br /&gt;1. Have the path of the software.&lt;br /&gt;For example, a CD_SHARE_SERVER, or media. Or ask your Solaris Admin to give the path. In my case, the Solaris Admin mapped the CD_SHARE_SERVER for me.&lt;br /&gt;2. Prepare the Response file.&lt;br /&gt;You can have the sample response file from the following location.&lt;br /&gt;You can take that modify that.&lt;br /&gt;&lt;br /&gt;My responsefile goes like this:&lt;br /&gt;I have stored this as responsefile.base.txt in /myfolder on the server box.&lt;br /&gt;&lt;br /&gt;-W silentInstallLicenseAcceptance.value="true"&lt;br /&gt;-P wasProductBean.installLocation="/software/IBM/WebSphere/AppServer"&lt;br /&gt;-W setuptypepanelInstallWizardBean.selectedSetupTypeId="Custom"&lt;br /&gt;-P samplesProductFeatureBean.active="true"&lt;br /&gt;-P javadocsProductFeatureBean.active="true"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.WC_defaulthost="9080"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.WC_adminhost="9060"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9443"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9043"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2809"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;SOAP_CONNECTOR_ADDRESS="8880"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9401"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9403"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9402"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9100"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9353"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7276"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;SIB_ENDPOINT_SECURE_ADDRESS="7286"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5558"&lt;br /&gt;-W defaultprofileportspanelInstallWizardBean.&lt;br /&gt;SIB_MQ_ENDPOINT_SECURE_ADDRESS="5578"&lt;br /&gt;-W nodehostandcellnamepanelInstallWizardBean.nodeName="bristowNode01"&lt;br /&gt;-W nodehostandcellnamepanelInstallWizardBean.hostName="bristow"&lt;br /&gt;-W setcellnameinglobalconstantsInstallWizardBean.value="bristowCell01"&lt;br /&gt;-W winservicepanelInstallWizardBean.accountType="localsystem"&lt;br /&gt;-W winservicepanelInstallWizardBean.startupType="manual"&lt;br /&gt;-W winservicepanelInstallWizardBean.userName="websphe"&lt;br /&gt;-W winservicepanelInstallWizardBean.password="admin1"&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;strong&gt;4. Once you have the response file, it’s the time to actual installation.&lt;/strong&gt;&lt;br /&gt;Goto the CD_SHARE_PATH or Media Mount, locate WAS6.0 installable folder.&lt;br /&gt;For example&lt;br /&gt;/koppell_cd_share/cd_share/WebSphere/wasv6_base_solsparc&lt;br /&gt;This is my installable folder.&lt;br /&gt;Traverse to WAS folder.&lt;br /&gt;U r at&lt;br /&gt;/koppell_cd_share/cd_share/WebSphere/wasv6_base_solsparc/WAS/&lt;br /&gt;now, issue the command&lt;br /&gt;install -options “/myfolder/responsefile.base.txt” -silent&lt;br /&gt;&lt;br /&gt;This silently installs the WAS 6.0.&lt;br /&gt;&lt;br /&gt;The another way of doing this writing as shell script like, name it as installer.sh&lt;br /&gt;#!/usr/bin/ksh&lt;br /&gt;MEDIA_DIR=/koppell_cd_share/cd_share/WebSphere/wasv6_base_solsparc&lt;br /&gt;INSTALL_DIR=/software/IBM&lt;br /&gt;RESPONSEFILE=/myfolder/responsefile.base.txt&lt;br /&gt;if [[ ! -f ${MEDIA_DIR}/WAS/install ]]&lt;br /&gt;then&lt;br /&gt;echo "\nCannot find webSphere Install Program"&lt;br /&gt;exit 1&lt;br /&gt;fi&lt;br /&gt;&lt;br /&gt;umask 022&lt;br /&gt;&lt;br /&gt;echo "\nNow installing websphere..."&lt;br /&gt;${MEDIA_DIR}/WAS/install -options ${RESPONSEFILE} -silent&lt;br /&gt;&lt;br /&gt;sleep 15&lt;br /&gt;FOUND=0&lt;br /&gt;while [[$FOUND -eq 0 ]]&lt;br /&gt;do&lt;br /&gt;sleep 5&lt;br /&gt;if [[ `/usr/bin/grep INSTCONFFAIL&lt;br /&gt;${INSTALL_DIR}/WebSphere/AppServer/logs/log.txt /usr/bin/wc -l` -gt 0&lt;br /&gt;]]&lt;br /&gt;then&lt;br /&gt;echo "\nWebSphere install Failed"&lt;br /&gt;FOUND=1&lt;br /&gt;exit 1&lt;br /&gt;fi&lt;br /&gt;if [[ `/usr/bin/grep INSTCONFPARITALSUCCESS&lt;br /&gt;${INSTALL_DIR}/WebSphere/AppServer/logs/log.txt /usr/bin/wc -l` -gt 0&lt;br /&gt;]]&lt;br /&gt;then&lt;br /&gt;echo "\nWebSphere install partial success"&lt;br /&gt;FOUND=1&lt;br /&gt;exit 1&lt;br /&gt;fi&lt;br /&gt;if [[ `/usr/bin/grep INSTCONFSUCCESS&lt;br /&gt;${INSTALL_DIR}/WebSphere/AppServer/logs/log.txt /usr/bin/wc -l` -gt 0&lt;br /&gt;]]&lt;br /&gt;then&lt;br /&gt;echo "\nWebSphere Installation Success"&lt;br /&gt;FOUND=1&lt;br /&gt;fi&lt;br /&gt;done&lt;br /&gt;echo "\nWebSphere products installed SUCCESSFULLY"&lt;br /&gt;exit 0&lt;br /&gt;&lt;br /&gt;Hopefully this should work with out any script errors, anyhow, my idea is to give an idea about the script, but not to see the script errors.&lt;br /&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;strong&gt;5. Post Installation&lt;/strong&gt;&lt;br /&gt;What Now!! We have installed the Application server. Now, this is the time to check post installation steps. Remeber that, the installation creates a profile for you called default. You can find that at WAS_HOME/profiles directory.&lt;br /&gt;&lt;br /&gt;First you need to see the logs&lt;br /&gt;WAS_HOME/logs&lt;br /&gt;check the log.txt.&lt;br /&gt;&lt;br /&gt;Goto the WAS_HOME (WAS_HOME is nothing but the Installed path of the WAS). That is /software/IBM/WebSphere/AppServer/profiles/default/bin.&lt;br /&gt;Give this command&lt;br /&gt;$ ivt.sh SERVER_NAME PROFILE_NAME&lt;br /&gt;that is&lt;br /&gt;ivt.sh server1 default&lt;br /&gt;This will tell you whether the installation is successful or not.&lt;br /&gt;&lt;br /&gt;I said that the installation will create a default profile for you called “default”. You should know what a profile is and how it can help you.&lt;br /&gt;The WebSphere Application Server profile defines the runtime environment. The profile includes all of the files that the server processes in the runtime environment and can change.&lt;br /&gt;&lt;br /&gt;Administration is greatly enhanced when using profiles instead of multiple product installations. Not only is disk space saved, but updating the product is simplified when you maintain only a single set of product core files. Also, creating new profiles is faster and less prone to error than full product installations, allowing a developer to create separate profiles of the product for development and testing.&lt;br /&gt;&lt;br /&gt;Now, the WAS is installed. You can access the admin console like this&lt;br /&gt;http://hostName:9060/ibm/console/&lt;br /&gt;&lt;br /&gt;If you have planned to have a Web Server, it is the time for you to install it. You do the same steps for installing Web Server. The WAS Supports Apache, IHS, IIS, etc. Pick yous choice of Web Server and proceed for the installation.&lt;br /&gt;&lt;br /&gt;After installing the Web Server, You have to install Plugins. This installation will generate plugin-config.xml, which is supposed to be the communication between Web Server and the WAS.&lt;br /&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;strong&gt;6. Refresh Packs and Fix Packs&lt;/strong&gt;&lt;br /&gt;As I said, my goal is to install WAS 6.0.2.5 and I have installed only WAS6.0. How to bring the installation to 6.0.2.5? For that, you need to goto ibm and download fix packs and refresh packs. What I did is, first I have installed Refresh Pack 2 and on that I have installed a fix pack.&lt;br /&gt;Note: Before applying fix packs or refresh packs, make sure that you have stopped the server.&lt;br /&gt;This raises a question, How to install these fix packs and refresh packs?&lt;br /&gt;Note: As a good practice, before installing any fix packs or patches, or refresh packs, take a backup of the existing configuration. How to do that?&lt;br /&gt;Goto WAS_HOME/profiles/default/bin&lt;br /&gt;issue this command&lt;br /&gt;./stopServer.sh server1&lt;br /&gt;This will stops the server.&lt;br /&gt;&lt;br /&gt;Now, goto the WAS_HOME/bin&lt;br /&gt;$./backupConfig.sh&lt;br /&gt;This will take the backup of the server including the default profile.&lt;br /&gt;The back will be stored as WebSphereConfig_YYYY_MM_DD.zip&lt;br /&gt;Again it is a good practice to have separate folder for backups, and this will be according to the company policy.&lt;br /&gt;&lt;br /&gt;I have first downloaded refresh pack 2. That comes as a tar.&lt;br /&gt;Download the tar 6.0-WS-WAS-SolarisSparc-RP0000002.tar into the WAS_HOME. Untar it like this.&lt;br /&gt;tar -xvf 6.0-WS-WAS-SolarisSparc-RP0000002.tar&lt;br /&gt;&lt;br /&gt;This will create a folder updateinstaller in the WAS_ROOT.&lt;br /&gt;In the updateinstaller folder, search for responsefiles subfolder.&lt;br /&gt;You can see install.txt and uninstall.txt.&lt;br /&gt;These two are responsefiles.&lt;br /&gt;Edit the install.txt for your environment. I have edit that like this&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;-W maintenance.package="/software/IBM/WebSphere/updateinstaller&lt;br /&gt;/maintenace/6.0-WS-WAS-SolarisSparc-RP0000002.pak"&lt;br /&gt;-W product.location="/software/IBM/WebSphere/AppServer"&lt;br /&gt;-W update.type="install"&lt;br /&gt;&lt;br /&gt;Goto the /WAS_HOME/bin&lt;br /&gt;at the command prompt issue this command&lt;br /&gt;$setupCmdLine.sh&lt;br /&gt;Now, again come to the updateinstaller folder and at the command prompt issue this&lt;br /&gt;$ ./update -options responsefiles/install.txt -silent&lt;br /&gt;This silently installs the refresh pack.&lt;br /&gt;You have to check whether that installer installed properly or not. For that you need to goto the logs.&lt;br /&gt;/WAS_HOME/logs/update/&lt;br /&gt;check all the logs in all the foldrs in this folder.&lt;br /&gt;&lt;br /&gt;Once you are done with the confirmation INSTCONFSUCCESS,&lt;br /&gt;goto WAS_HOME/bin/&lt;br /&gt;$./versionInfo.sh&lt;br /&gt;This will give you the version of the current installation.&lt;br /&gt;Now, start the server&lt;br /&gt;WAS_HOME/profiles/default/bin&lt;br /&gt;$./startServer.sh server1&lt;br /&gt;If the installation is successful, the server will start.&lt;br /&gt;&lt;br /&gt;Now, I have to install Fix Pack.&lt;br /&gt;For that the procedure is same.&lt;br /&gt;First I have cleaned up updateinstaller.&lt;br /&gt;By the way, how to remove a folder which has files in that in Solaris?&lt;br /&gt;rm -r updateinstaller&lt;br /&gt;This is the command.&lt;br /&gt;Now, the folder is deleted. Again download the fix pack 6.0.2-WS-WAS-SolarisSparc-FP0000005.tar&lt;br /&gt;Stop the server as usual. And take the back up of the server as above.&lt;br /&gt;Prepare the install.txt response file and install the fix pack in the silent mode.&lt;br /&gt;Uff!!! Long process!!&lt;br /&gt;Now, check the versionInfo of the product.&lt;br /&gt;WVER0010I: Copyright (c) IBM Corporation 2002, 2005; All rights reserved.&lt;br /&gt;WVER0011I: WebSphere Application Server Release 6.0&lt;br /&gt;WVER0012I: VersionInfo reporter version 1.15.3.1, dated 4/25/05&lt;br /&gt;&lt;br /&gt;-------------------------------------------------------------------&lt;br /&gt;IBM WebSphere Application Server Product Installation Status Report&lt;br /&gt;-------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;Report at date and time 2006-05-02 15:12:41-0400&lt;br /&gt;&lt;br /&gt;Installation&lt;br /&gt;-------------------------------------------------------------------&lt;br /&gt;Product Directory /software/IBM/WebSphere/AppServer&lt;br /&gt;Version Directory /software/IBM/WebSphere/AppServer/properties/version&lt;br /&gt;DTD Directory /software/IBM/WebSphere/AppServer/properties/version/dtd&lt;br /&gt;Log Directory /software/IBM/WebSphere/AppServer/logs&lt;br /&gt;Backup Directory /software/IBM/WebSphere/AppServer/properties/version/update/backup&lt;br /&gt;TMP Directory /var/tmp&lt;br /&gt;&lt;br /&gt;Installation Platform&lt;br /&gt;------------------------------------------------------------------&lt;br /&gt;Name IBM WebSphere Application Server&lt;br /&gt;Version 6.0&lt;br /&gt;&lt;br /&gt;Product List&lt;br /&gt;------------------------------------------------------------------&lt;br /&gt;BASE installed&lt;br /&gt;&lt;br /&gt;Installed Product&lt;br /&gt;------------------------------------------------------------------&lt;br /&gt;Name IBM WebSphere Application Server&lt;br /&gt;Version 6.0.2.5&lt;br /&gt;ID BASE&lt;br /&gt;Build Level cf50549.21&lt;br /&gt;Build Date 12/8/05&lt;br /&gt;&lt;br /&gt;------------------------------------------------------------------&lt;br /&gt;End Installation Status Report&lt;br /&gt;------------------------------------------------------------------&lt;br /&gt;&lt;br /&gt;Start the server, access the Admin Console. You will see the 6.0.2.5 admin console. &lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;strong&gt;7. Profiles:&lt;/strong&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;As I said, the installation will create a default profile. If you want you can create your own profile depending on the need.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;I will discuss the process of creating your own profile.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;There is a command in WAS to create a profile.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;In Solaris, the can be created silently using pctSolaris.bin&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;pctSolaris.bin is the profile creation tool. How to use it and where to find it.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Goto WAS_HOME/bin/ProfileCreator&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;You will see &lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;pct.jar&lt;br /&gt;responsefile.BaseProfile..txt&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;pctSolaris.bin&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;So, to install a profile u can have a responsefile and use pctSolaris.bin to create it. There is another way of create profile. That is by using wasprofile.sh.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;simply call wasprofile.sh at the command prompt, it will give you the available modes : create, augment, delete, etc....&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;The syntax of creating profile using wasprofile.sh&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;wasprofile.sh -create -profileName &lt;name&gt;-profilePath &lt;profilepath&gt;-templatePath &lt;templatepath&gt;-nodename &lt;nodename&gt;-cellName &lt;cellname&gt;-hostName &lt;hostname&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Let us see how to create a profile using pctSolaris.bin&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;First prepare a responsefile for the profile.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;My response file goes like this&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;# Profile Name devirs-&lt;br /&gt;W silentInstallLicenseAcceptance.value="true" &lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;-W profilenamepanelInstallWizardBean.profileName="devirs"&lt;br /&gt;-W profilenamepanelInstallWizardBean.isDefault="false"&lt;br /&gt;-P installLocation="/software/IBM/WebSphere/AppServer/profiles/devirs"&lt;br /&gt;# Node name&lt;br /&gt;-W nodehostnamepanelInstallWizardBean.nodeName="bristowdevirsNode"&lt;br /&gt;# Host name&lt;br /&gt;-W nodehostnamepanelInstallWizardBean.hostName="bristow"&lt;br /&gt;# Cell name&lt;br /&gt;-W setnondmgrcellnameinglobalconstantsInstallWizardBean.value="bristowdevirsCell"&lt;br /&gt;# Port value assignment&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost="9081"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost="9063"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.WC_defaulthost_secure="9446"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.WC_adminhost_secure="9044"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.BOOTSTRAP_ADDRESS="2899"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.SOAP_CONNECTOR_ADDRESS="8881"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.&lt;br /&gt;SAS_SSL_SERVERAUTH_LISTENER_ADDRESS="9406"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.&lt;br /&gt;CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS="9407"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.&lt;br /&gt;CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS="9408"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.ORB_LISTENER_ADDRESS="9102"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.DCS_UNICAST_ADDRESS="9355"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.SIB_ENDPOINT_ADDRESS="7279"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.&lt;br /&gt;SIB_ENDPOINT_SECURE_ADDRESS="7289"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.SIB_MQ_ENDPOINT_ADDRESS="5588"&lt;br /&gt;-W pctdefaultprofileportspanelInstallWizardBean.&lt;br /&gt;SIB_MQ_ENDPOINT_SECURE_ADDRESS="5598"&lt;br /&gt;-W winservicepanelInstallWizardBean.accountType="localsystem"&lt;br /&gt;-W winservicepanelInstallWizardBean.userName="websphe"&lt;br /&gt;-W winservicepanelInstallWizardBean.password="admin1"&lt;br /&gt;-W winservicepanelInstallWizardBean.startupType="manual"&lt;br /&gt;-W profiletypepanelInstallWizardBean.selection="default"&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Now, your responsefile is ready.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Start creating a profile using pctSolaris.bin like this:&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;goto WAS_HOME/bin/ProfileCreator&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;$pctSolaris.bin -options "mypath/responsefile.txt" -silent&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Thats it.&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Now, Where to see the logs of your profile for the verification?&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;goto WAS_HOME/logs/wasprofile&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;This is the place to check for the creation and deletion logs for your profile. The logs will be created like this wasprofile_create_YOURPROFILENAME.log and wasprofile_delete_YOURPROFILENAME.log. If in creation is not successful, that pctSolaris command will throw errors into the wasprofile_create_YOURPOFILENAME.log&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;Assume that we have created a profile called "Gongura"&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;What to do next? You need to verify the installation. How to do that? as I said earlier, you need to goto the WAS_HOME/profiles/Gongura/bin. From now on, WAS_HOME/profiles/Gongura is our PROFILE_HOME. We need to check for the installation verification by calling the command &lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;ivt.sh server1 profilename&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;After this is successfully returns the profile creation information, its the time to start the server. Before that check the status of the server. The ivt.sh starts the server. To know the status of the server, &lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;goto PROFILE_HOME/bin&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;serverStatus.sh server1&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;If the server is up, it returns&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;The Application server appears to be started&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;otherwise&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;stopped&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;br /&gt;&lt;/div&gt;&lt;div style="TEXT-ALIGN: justify"&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7932682-114693295216472129?l=javagongura.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://javagongura.blogspot.com/feeds/114693295216472129/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7932682&amp;postID=114693295216472129' title='4 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114693295216472129'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7932682/posts/default/114693295216472129'/><link rel='alternate' type='text/html' href='http://javagongura.blogspot.com/2006/05/websphere-administration.html' title='WebSphere Administration'/><author><name>భాస్కర్ రామరాజు</name><uri>http://www.blogger.com/profile/17905547816696931628</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='24' src='http://2.bp.blogspot.com/-WWrkRqvEqRI/TrNXBXk77KI/AAAAAAAAGz8/FFCgxTSYbFA/s220/100.JPG'/></author><thr:total>4</thr:total></entry></feed>
