<?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-4875218282209868040</id><updated>2011-10-18T09:55:03.543+05:30</updated><category term='jsr 286'/><category term='IHS'/><category term='portlet service'/><category term='url'/><category term='jcr'/><category term='wcm api'/><category term='wsadmin'/><category term='portlet preference'/><category term='web'/><category term='URL navigation'/><category term='member fixer'/><category term='wps6.1'/><category term='spring portlet mvc'/><category term='session timeout'/><category term='command cache'/><category term='Portal Upgrades'/><category term='portal update'/><category term='ldap'/><category term='wcmsearch'/><category term='rad'/><category term='web 2.0'/><category term='wcm upgrade'/><category term='troublshooting'/><category term='custom portlet'/><category term='portal'/><category term='WebSphere administration'/><category term='portal access control'/><category term='search center'/><category term='vmm'/><category term='ltpa'/><category term='wps 5.1'/><category term='troubleshooting portal'/><category term='custom user attribute'/><category term='portal installation'/><category term='logout'/><category term='jsr 168'/><category term='sso'/><category term='ajax'/><category term='wcm version'/><category term='portal page'/><category term='wcm'/><category term='g-zip'/><category term='WebAppIntegrator'/><category term='spi'/><category term='websphere portal faq'/><category term='DOJO'/><category term='xmlaccess'/><category term='webseal junction'/><category term='wcm workflow'/><category term='wps 6.1'/><category term='syndication'/><category term='DraftDetectionModule'/><category term='Best Practices'/><category term='portlet'/><category term='portal info center'/><category term='wmm'/><category term='integration with portal'/><category term='desktop'/><category term='portal config'/><category term='skin'/><category term='wps'/><category term='content api'/><category term='wps login'/><category term='search'/><category term='ssl'/><category term='was'/><category term='Portal Design'/><category term='Application group'/><category term='wsrp'/><category term='Portal admin utility'/><category term='fixes'/><category term='IBM HTTP Server'/><category term='WebSphere Password Decoder'/><category term='wcm jsp'/><category term='widget'/><category term='wps 6.0'/><title type='text'>Best Practice : WebSphere Portal &amp; WCM</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://kaushalksinha.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><link rel='next' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default?start-index=101&amp;max-results=100'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>239</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8742568093388351829</id><published>2010-06-01T01:02:00.002+05:30</published><updated>2010-06-01T01:03:01.915+05:30</updated><title type='text'>Using wsadmin to modify configuration variables</title><summary type='text'>The backupConfig and restoreConfig commands for the WebSphere Application Server are pretty handy. The backupConfig command allows you to back up all of the configuration for a selected profile to an archive. The restoreConfig command allows you to restore (or import) the configuration from such an archive to a target profile. You can employ these commands for many purposes such as sharing a </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8742568093388351829'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8742568093388351829'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/06/using-wsadmin-to-modify-configuration.html' title='Using wsadmin to modify configuration variables'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7171370815868052737</id><published>2010-06-01T01:01:00.002+05:30</published><updated>2010-06-01T01:02:02.550+05:30</updated><title type='text'>Changing cell names, node names, host names</title><summary type='text'>how to change cell names, node names, and host names for a given WebSphere Application Server environment. It usually starts by someone asking me what configuration files they need to change when they want to update this information, and is followed by their surprise when I tell them none. The reason I say that is because it’s time consuming, hard, and unnecessary for you to figure this out. </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7171370815868052737'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7171370815868052737'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/06/changing-cell-names-node-names-host.html' title='Changing cell names, node names, host names'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7620624875050146813</id><published>2010-05-31T23:50:00.000+05:30</published><updated>2010-05-31T23:51:06.530+05:30</updated><title type='text'>Render pzn cmpnt using wcm api</title><summary type='text'>How can I render a Personalization (PZN) component using the IBM® Web Content Management (WCM) API? AnswerThe WCM API provides features to render content items as well as library components such as the Web Content Management Personalization component.Summary of how to render personalization component in WCMFirst get the user workspaceNext set the web content library.Get the document iterator for </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7620624875050146813'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7620624875050146813'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/render-pzn-cmpnt-using-wcm-api.html' title='Render pzn cmpnt using wcm api'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4831860311724993773</id><published>2010-05-31T18:46:00.000+05:30</published><updated>2010-05-31T18:47:01.195+05:30</updated><title type='text'>Changing the language used in the log file</title><summary type='text'>Changing the language used in the log fileBy default, information in the log file is written in the language that was used for the WebSphere Portal installation. However, because WebSphere Portal supports a number of languages, you can choose to have the log file information written in a language other than that used during installation.To change the language used for the log file, edit the file </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4831860311724993773'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4831860311724993773'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/changing-language-used-in-log-file.html' title='Changing the language used in the log file'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3467831838376573001</id><published>2010-05-31T18:32:00.000+05:30</published><updated>2010-05-31T18:44:08.080+05:30</updated><title type='text'>Configuring Netegrity SiteMinder to Work with IBM WebSphere Portal</title><summary type='text'>Before the configuring Netegrity SiteMinder, please make sure you  finish the following tasks:1. Install WebSphere Application server  6.0.2.17 and WebSphere Portal server 6.0.12. Install HTTP server 6.03.  Install Web Server plug-in for WebSphere Application ServerIn  the following instructions, WebSphere Application Server and HTTP server  6.0 are installed on the same machine: for example</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3467831838376573001'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3467831838376573001'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/configuring-netegrity-siteminder-to.html' title='Configuring Netegrity SiteMinder to Work with IBM WebSphere Portal'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3742481823887528123</id><published>2010-05-31T18:31:00.000+05:30</published><updated>2010-05-31T18:32:00.645+05:30</updated><title type='text'>WebSphere Application Server production environment set up practice guidelines</title><summary type='text'>WebSphere Application Server production environment and demonstrates the structures there are many different environments, due to the diversity of production environments, application performance tuning scene, error diagnosis and other strict requirements, WebSphere Application Server production environment involves the installation of the pre-installation system inspection, installation, </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3742481823887528123'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3742481823887528123'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/websphere-application-server-production.html' title='WebSphere Application Server production environment set up practice guidelines'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3436816186429895278</id><published>2010-05-11T20:57:00.002+05:30</published><updated>2010-05-11T21:07:21.099+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='websphere portal faq'/><title type='text'>Some more portal faq</title><summary type='text'>Q:Is it possible to apply CSS for WCM rich-text editor?A:To get a consistent style of texts created with an authoring template, so the CSS is able to be applied into rich text editor. In the Content Form Properties you can define default styles and add your CSS file for rich text field in the Authoring template.Q:Is it possible to change subadmin groups of virtual portal after virtual portal was </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3436816186429895278'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3436816186429895278'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/some-more-portal-faq.html' title='Some more portal faq'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4966811712303203365</id><published>2010-05-11T20:50:00.000+05:30</published><updated>2010-05-11T20:53:04.095+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='websphere portal faq'/><title type='text'>portal faqs</title><summary type='text'>Q: How can I change a realm’s name after I made the configuration?     A: Remember to back up the wimconfig.xml file, located in /config/cells/ cellname/wim/config/.Two methods, Manually edit wimconfiq.xml file and replace as below,name="oldPortalRealm" securityUse="active"allowOperationIfReposDown="false"&gt;OrRun ConfigEngine.bat wp-rename-realm afteradding/modifying the following properties in </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4966811712303203365'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4966811712303203365'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/portal-faqs.html' title='portal faqs'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4784978363968969072</id><published>2010-05-11T20:45:00.002+05:30</published><updated>2010-05-11T20:50:38.265+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='websphere portal faq'/><title type='text'>Some portal faqs</title><summary type='text'>Q:Why does portlet become active even it was inactive before publishing?A:Under the 'Portlet Publishing' section, "create pages for portlets" was selected by default setting, which creates a page on the portal server under the default label "Rational Portlets" and adds the published portlet to the page. So when you deselect it, portlet is inactive.Q:How to let Dojo css are not being loaded on </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4784978363968969072'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4784978363968969072'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2010/05/some-portal-faqs.html' title='Some portal faqs'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3637015845955773554</id><published>2009-11-17T23:34:00.001+05:30</published><updated>2009-11-17T23:35:58.885+05:30</updated><title type='text'>Simplest SSO implementation</title><summary type='text'>OA needs to be done with the project and the Portal of the SSO, two applications were on different servers, but top-level domain name is identical to the simple formula, and I said, it used domain cookie bar, they still will not talk for a long time doing,囧~~~~, Suppose portal's domain name is portal.xxxx.com in the Portal log is complete, set a cookie: &lt;% @ Page language = "java" pageEncoding</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3637015845955773554'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3637015845955773554'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/simplest-sso-implementation.html' title='Simplest SSO implementation'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4753307354958097848</id><published>2009-11-17T23:33:00.002+05:30</published><updated>2009-11-17T23:34:07.285+05:30</updated><title type='text'>Can a URL mapping and friendly URL contain the same name?</title><summary type='text'>Question   In IBM WebSphere Portal, can a URL mapping and a friendly URL have the same name? For example, can you specify both a friendly URL via the Page Properties administrative portlet for your home page named "Home", and also create a URL mapping named "Home" for your home page via the URL Mapping administrative portlet?     Answer   The usage of identical names for friendly URLs and URL </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4753307354958097848'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4753307354958097848'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/can-url-mapping-and-friendly-url.html' title='Can a URL mapping and friendly URL contain the same name?'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2193187597564820334</id><published>2009-11-17T23:33:00.001+05:30</published><updated>2009-11-17T23:33:21.081+05:30</updated><title type='text'>Getting Page Title</title><summary type='text'>Using Model SPI to get Page titleIBM WebSphere Portal uses a concept of Models for content aggregation, to track user's pages etc. The Model SPI provides access to these models. The attached code provides an example to illustrate on how to get a title of a page using model SPI in JSR 286 portlet. Here is the code snippet to get title of pagepublic String getTitle(PortletRequest request, </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2193187597564820334'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2193187597564820334'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/getting-page-title.html' title='Getting Page Title'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4777901085670141320</id><published>2009-11-17T23:31:00.001+05:30</published><updated>2009-11-17T23:32:17.381+05:30</updated><title type='text'>How to get the seedlist for the WebSphere Portal search engine in version 6.1.x Portal for either the portal collection or the WCM collection</title><summary type='text'>How do I generate the output for the search seedlist in portal version 6.1.x for either the portal collection or the WCM collection?      Cause   The reason for this is to examine if there is a problem with the search engine crawler or the seedlist servlet that provides a list of documents to be crawled and indexed in the portal. This is used in debugging if it is suspected that the proper amount</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4777901085670141320'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4777901085670141320'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/how-to-get-seedlist-for-websphere.html' title='How to get the seedlist for the WebSphere Portal search engine in version 6.1.x Portal for either the portal collection or the WCM collection'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-9182375729577522840</id><published>2009-11-17T23:13:00.004+05:30</published><updated>2009-11-17T23:24:25.222+05:30</updated><title type='text'>Just JSR 168</title><summary type='text'>The Java Standardization Request 168 (JSR 168) defines a portlet specification, including a contract between the portlet container and the portlet. JSR 168 is defined by the Java Community Process (JCP). The JSR 168 was co-led by IBM and Sun and had a large Expert Group that helped to create the final version which is now available. This Expert Group consisted of Apache Software Foundation, Art </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9182375729577522840'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9182375729577522840'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/just-jsr-168.html' title='Just JSR 168'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4366292383835888661</id><published>2009-11-17T22:55:00.000+05:30</published><updated>2009-11-17T22:56:48.416+05:30</updated><title type='text'>Comparing JSR 168 and the IBM Portlet API</title><summary type='text'>Comparing JSR 168 and the IBM Portlet APIThis section gives a high level comparison between the new JSR 168 Portlet API and the IBM Portlet API. First, it covers the concepts that are similar; then, it explains some of the differences between the two.SimilaritiesThe following concepts are very similar in JSR 168 and the IBM Portlet API.Feature Similarities Differences Portlet modesBoth support </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4366292383835888661'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4366292383835888661'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/comparing-jsr-168-and-ibm-portlet-api.html' title='Comparing JSR 168 and the IBM Portlet API'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-9004435901098052059</id><published>2009-11-17T22:45:00.002+05:30</published><updated>2009-11-17T22:55:03.939+05:30</updated><title type='text'>Cross Site Request Forgery. What it is and how to work around it.</title><summary type='text'>    If there's a way to solve the Cross Site Request Forgery (CSRF) issue that has been highlighted by every web Security Team. Previously, normal a common filter application (J2EE Filter) that filters out Cross Site Scripting Characters from a request and response. This helped  tremendously in passing the security assessment as all they have to do is define the filter on their applications and </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9004435901098052059'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9004435901098052059'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/cross-site-request-forgery-what-it-is.html' title='Cross Site Request Forgery. What it is and how to work around it.'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-944639899667721411</id><published>2009-11-17T22:43:00.000+05:30</published><updated>2009-11-17T22:45:54.269+05:30</updated><title type='text'>Portlet Context,Portlet Config and Portal Context</title><summary type='text'>PortletContext  is similar to servletConext and is used to get  values declared in web.xml.Inside doView method of your custom portlet ( implementing GenericPortlet.), you can get context param as below getPortletContext().getInitParameter("ContextParam") PortletContext scope is application wide.If you set any attribute to portletContext, that would be available to all the portlets in that </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/944639899667721411'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/944639899667721411'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/portlet-contextportlet-config-and.html' title='Portlet Context,Portlet Config and Portal Context'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3819560159380511608</id><published>2009-11-17T22:42:00.000+05:30</published><updated>2009-11-17T22:43:47.481+05:30</updated><title type='text'>WebSphere Portal DataBases</title><summary type='text'>Understanding the Portal Server ConfigurationSo far, you have seen and hopefully understood how to install and verify the WebSpherePortal server. Now you will see how the Portal server’s configuration data is stored in thedefault Cloudscape database and in files in the file system. If you want to configure andmaintain your portal server in a production environment then you need to have acomplete </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3819560159380511608'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3819560159380511608'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/websphere-portal-databases.html' title='WebSphere Portal DataBases'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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://3.bp.blogspot.com/_sHlXLfpCp6I/SlxKST9L80I/AAAAAAAACwM/ynqwOHbYUvk/s72-c/Untitled.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2544863870943259885</id><published>2009-11-17T22:41:00.000+05:30</published><updated>2009-11-17T22:42:47.188+05:30</updated><title type='text'>How to take a heapdump and a javacore on a WebSphere Portal server</title><summary type='text'>     Sometimes taking a heapdump or a javacore on a Portal system can help to diagnose hung threads or a stalled system. A heapdump is a dump of the memory of the Java heap. A javacore provides insights into the various processing running inside of the heap at a given time.Javacores should be taken two minutes apart in order determine if processes are hanging across intervals.Depending on the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2544863870943259885'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2544863870943259885'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/how-to-take-heapdump-and-javacore-on.html' title='How to take a heapdump and a javacore on a WebSphere Portal server'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1437588166970326083</id><published>2009-11-17T22:40:00.001+05:30</published><updated>2009-11-17T22:40:58.177+05:30</updated><title type='text'>Accessing parameter from QueryString in IBM WebSphere Portal V6.1</title><summary type='text'>   This is very simple in IBM WebSphere Portal V 6.1Consider we have url : https://localhost:60035/wps/portal/test?PhoneId=35102Import com.ibm.ws.portletcontainer.core.impl.RenderRequestImplWrite down code in Portlet.public void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException {RenderRequestImpl renderRequestImpl = (RenderRequestImpl)request;String </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1437588166970326083'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1437588166970326083'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/accessing-parameter-from-querystring-in.html' title='Accessing parameter from QueryString in IBM WebSphere Portal V6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2356014472469116198</id><published>2009-11-17T22:39:00.001+05:30</published><updated>2009-11-17T22:39:56.803+05:30</updated><title type='text'>How to get path(/wps/portal or /wps/myportal) in IBM WebSphere Portal V6.1 theme</title><summary type='text'>   Import following object in jsp or classimport com.ibm.portal.state.accessors.url.ServerContext;import com.ibm.wps.services.ServiceManager;import com.ibm.wps.services.config.ConfigService;import com.ibm.wps.state.accessors.url.ServerContextOnConfigFactory;import com.ibm.wps.state.phases.ServerContextFactory;ConfigService configService = (ConfigService)ServiceManager.getService(</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2356014472469116198'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2356014472469116198'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/11/how-to-get-pathwpsportal-or-wpsmyportal.html' title='How to get path(/wps/portal or /wps/myportal) in IBM WebSphere Portal V6.1 theme'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8040259915787543699</id><published>2009-10-28T01:19:00.000+05:30</published><updated>2009-10-28T01:22:57.063+05:30</updated><title type='text'>WebSphere Portal site management - publishing pages using a SUN Web server</title><summary type='text'>Problem(Abstract)   Even if you successfully configured your portal with a SUN Web server as the target server for site management, the browser might prompt you for the Web server administrator user ID and password when you publish a page to this target server several times.     Symptom   When you use portal site management to publish a page to the SUN target Web server, the browser prompts you </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8040259915787543699'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8040259915787543699'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/websphere-portal-site-management.html' title='WebSphere Portal site management - publishing pages using a SUN Web server'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2236347814079604380</id><published>2009-10-28T01:16:00.002+05:30</published><updated>2009-10-28T01:18:07.737+05:30</updated><title type='text'>Monitoring IBM WebSphere Portal caches using IBM Tivoli Performance Viewer</title><summary type='text'>  Question   The correct sizing of internal caches used by IBM WebSphere Portal is critical to the product performance. In order to configure and tune the caches of IBM WebSphere Portal, monitoring of the caches is required under load conditions. How can the internal caches be monitored without installing extra analysis tooling?     Answer   A selection of the internal caches of IBM WebSphere </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2236347814079604380'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2236347814079604380'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/monitoring-ibm-websphere-portal-caches.html' title='Monitoring IBM WebSphere Portal caches using IBM Tivoli Performance Viewer'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5011009631591809535</id><published>2009-10-26T20:31:00.001+05:30</published><updated>2009-10-26T20:33:56.459+05:30</updated><title type='text'>JSR286 : Action scope request attribute</title><summary type='text'> Introduction  The core features of any Internet portal are content aggregation from different   information sources, web-page personalization and single sign-on. Java portlets   act as the building blocks of any J2EE based portal implementation. Java portlets   are very similar to Java servlets in many ways. They too are web components,   managed by a container, that generate dynamic content. </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5011009631591809535'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5011009631591809535'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/jsr286-action-scope-request-attribute.html' title='JSR286 : Action scope request attribute'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-144616756959941170</id><published>2009-10-23T14:59:00.002+05:30</published><updated>2009-10-23T15:03:19.469+05:30</updated><title type='text'>Adding Log4j Logging to a Portlet</title><summary type='text'>System.out is used to put one feel that it give any Performance performance. Now change to try and see Log4j may helpSet out how to write well. 1. First, they need to download log4j before here http://logging.apache.org/log4j/1.2/download.html. 2. When we have already loaded the file will be much different to many files for extension. Jar.It is outmostEg. Zip to extract the directory name </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/144616756959941170'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/144616756959941170'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/adding-log4j-logging-to-portlet.html' title='Adding Log4j Logging to a Portlet'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8335041763131771005</id><published>2009-10-04T00:06:00.000+05:30</published><updated>2009-10-04T22:45:03.588+05:30</updated><title type='text'>Steps to remove a damaged Primary Node and assign a new Primary Node to a Portal Cluster</title><summary type='text'>         What are the steps that can be used to remove a damaged Primary Node from an IBM® WebSphere® Portal cluster and assign another node to the role of Primary Node ?       If there is an event that causes issues with the Primary Node in the cluster, such as a failed upgrade, hardware failure, etc, there is a requirement that a Primary Node be identified in the Portal Cluster for maintenance </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8335041763131771005'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8335041763131771005'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/steps-to-remove-damaged-primary-node.html' title='Steps to remove a damaged Primary Node and assign a new Primary Node to a Portal Cluster'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-91501900798186434</id><published>2009-10-04T00:01:00.001+05:30</published><updated>2009-10-04T00:04:17.982+05:30</updated><title type='text'>To install/configure the personalization sample in WPS 6.1</title><summary type='text'>To install/configure the personalization sample by following these task in WPS 6.1Step 1: ConfigEngine.bat create-pzndemo-users -DPortalAdminPwd=passwordStep 2: ConfigEngine.bat install-pzndemo -DPortalAdminPwd=password -DWasPassword=password</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/91501900798186434'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/91501900798186434'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/10/to-installconfigure-personalization.html' title='To install/configure the personalization sample in WPS 6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6965996755610161436</id><published>2009-09-24T00:40:00.001+05:30</published><updated>2009-09-24T01:16:25.929+05:30</updated><title type='text'>Additional steps needed after updating wps.ear</title><summary type='text'>Problem After an effort to update the wps.ear to include new configuration for IBM® WebSphere® Portal, the deployment completes successfully, but browsing to the Portal to verify the update results in errors on the page. Symptom You will see content errors on the Portal page in the browser.   Errors logged for this issue:[date/time] 0000002e Helpers W NMSV0605W: A Reference object looked up from </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6965996755610161436'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6965996755610161436'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/additional-steps-needed-after-updating.html' title='Additional steps needed after updating wps.ear'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4952422388878441240</id><published>2009-09-24T00:38:00.001+05:30</published><updated>2009-09-24T00:40:06.430+05:30</updated><title type='text'>How to restore WebSphere Portal back to the out-of-the-box security configuration</title><summary type='text'>                             &lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;        Question   Sometimes you may encounter a problem when you configure IBM WebSphere Portal security (standalone or federated). This problem can cause the system configuration files to be in an inconsistent state. Can you revert back to the original file </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4952422388878441240'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4952422388878441240'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/how-to-restore-websphere-portal-back-to.html' title='How to restore WebSphere Portal back to the out-of-the-box security configuration'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4327542422370130088</id><published>2009-09-23T14:13:00.000+05:30</published><updated>2009-09-23T14:14:45.787+05:30</updated><title type='text'>Use IBM Workplace Web Content Management 6.0</title><summary type='text'>&lt;!-- End Title --&gt;                                                                                                 &lt;!-- Start Main Content --&gt;  Use this training path to see the courses you need to take to achieve this skill or certification. Click on the course boxes to access a course description, view its schedule, and enroll.    PDF version (103KB)                    AudienceThis roadmap is </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4327542422370130088'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4327542422370130088'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/use-ibm-workplace-web-content.html' title='Use IBM Workplace Web Content Management 6.0'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1961672680481735989</id><published>2009-09-23T14:08:00.001+05:30</published><updated>2009-09-23T14:10:44.049+05:30</updated><title type='text'>System Administrator Skills for WebSphere Portal V6.1</title><summary type='text'>&lt;!-- End Title --&gt;                                                                                                 &lt;!-- Start Main Content --&gt;  Use this training path to see the courses you need to take to achieve this skill or certification. Click on the course boxes to access a course description, view its schedule, and enroll.       PDF version (30KB)                                        </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1961672680481735989'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1961672680481735989'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/system-administrator-skills-for.html' title='System Administrator Skills for WebSphere Portal V6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6764258285917674808</id><published>2009-09-23T12:53:00.000+05:30</published><updated>2009-09-23T12:54:26.666+05:30</updated><title type='text'>Skills for WebSphere Portal V6.1</title><summary type='text'>Application Development            &lt;!-- End Title --&gt;                                                                                                  &lt;!-- Start Main Content --&gt;  Use this training path to see the courses you need to take to achieve this skill or certification. Click on the course boxes to access a course description, view its schedule, and enroll.       PDF version (31KB)</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6764258285917674808'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6764258285917674808'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/skills-for-websphere-portal-v61.html' title='Skills for WebSphere Portal V6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6939308922209970426</id><published>2009-09-23T02:04:00.000+05:30</published><updated>2009-09-23T02:05:11.351+05:30</updated><title type='text'>How to Update the Database Administrator Password on Portal 6.0 and 6.1</title><summary type='text'>      &lt;!-- OneX body.doc --&gt;&lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;         Question   I have to change the database administrator password.  Now how do I update Portal with the new DB password?      Answer   You can update the database administrator passwords for Portal by changing the datasource, as noted in the Portal </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6939308922209970426'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6939308922209970426'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/how-to-update-database-administrator.html' title='How to Update the Database Administrator Password on Portal 6.0 and 6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6791955557431244955</id><published>2009-09-23T01:51:00.000+05:30</published><updated>2009-09-23T01:53:08.550+05:30</updated><title type='text'>How to configure the portlet for different settings for different users?</title><summary type='text'>How to configure the portlet for different settings for different users?      Need:   Need to configure portlet for individual users     Solution:   If the Portal Administrator sets the Shared Settings for the Rendering Portlets, then later attempts to configure the portlet with the "Configure" option, they will receive this Informational Message:The shared settings of this portlet have been </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6791955557431244955'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6791955557431244955'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/how-to-configure-portlet-for-different.html' title='How to configure the portlet for different settings for different users?'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-840644020251009289</id><published>2009-09-21T01:20:00.000+05:30</published><updated>2009-09-21T01:22:03.273+05:30</updated><title type='text'>Support Content Highlight for WebSphere Portal/WCM (September 2009)</title><summary type='text'>Support Content Highlight for WebSphere Portal/WCM (September 2009)        Introduction This document contains links to technical support documents for IBM WebSphere Portal that are frequently requested or identified by IBM as valuable for the time period covered by this notification. This is key information to help you derive the most value from your software licenses, find answers to common </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/840644020251009289'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/840644020251009289'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/support-content-highlight-for-websphere.html' title='Support Content Highlight for WebSphere Portal/WCM (September 2009)'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6364251186142944555</id><published>2009-09-16T20:35:00.002+05:30</published><updated>2009-09-16T20:43:54.333+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='url'/><title type='text'>Nested URL opens in new browser window instead of current window</title><summary type='text'>How do i do : In IBM WebSphere Portal, when creating a new external URL using the Manage Pages administration portlet, it behaves differently depending on which the level used. * Example 1: If you go to Content Root --&gt; Home --&gt; Level 2 URL (mapped to www.ibm.com) and leave Portal administration, when you click the new URL, it opens www.ibm.com in the same window.* Example 2: If you go to Content</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6364251186142944555'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6364251186142944555'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/nested-url-opens-in-new-browser-window.html' title='Nested URL opens in new browser window instead of current window'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1114278056261704313</id><published>2009-09-16T20:22:00.002+05:30</published><updated>2009-09-16T20:35:21.289+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='URL navigation'/><title type='text'>How to modify theme so that all URL links open in a new window</title><summary type='text'>     You create a new URL link using the Manage Pages portlet in IBM®  WebSphere® Portal version 6.0. When a user clicks on this new URL link, it  displays the target page in the same window as opposed to opening a new Web  browser window. How can you force it to open a new browser window when clicking  the URL link?       How do i do  In this scenario, the customer was working on a page </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1114278056261704313'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1114278056261704313'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/how-to-modify-theme-so-that-all-url.html' title='How to modify theme so that all URL links open in a new window'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4198708147814267354</id><published>2009-09-15T22:45:00.000+05:30</published><updated>2009-09-15T22:47:03.724+05:30</updated><title type='text'>Portlet configuration preference layers and portlet modes</title><summary type='text'>Portlet configuration preference layers and portlet modesType of configuration Description Portlet mode   Deployment descriptor preferences They are associated with a deployed portlet, represented by a  tag in portlet.xml. They apply to all occurrences of that portlet on all pages for all users.    Administrator preferences They are associated with a portlet definition, that is a particular copy </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4198708147814267354'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4198708147814267354'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/portlet-configuration-preference-layers.html' title='Portlet configuration preference layers and portlet modes'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3556493950343887845</id><published>2009-09-06T14:07:00.000+05:30</published><updated>2009-09-06T14:08:13.032+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='wsrp'/><title type='text'>Using WSRP for distributing load</title><summary type='text'>                                One of the common gripes that I hear from portal customers is that it’s very expensive to scale portal. This can be true especially if the portlets suffer from ‘bloat’ and carry out more processing than they should. I know of one organisation here in the UK that was seriously considering abandoning WebSphere Portal to return to straightforward servlet development </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3556493950343887845'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3556493950343887845'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/using-wsrp-for-distributing-load.html' title='Using WSRP for distributing load'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4942130457333921041</id><published>2009-09-05T19:55:00.000+05:30</published><updated>2009-09-05T20:02:03.913+05:30</updated><title type='text'>Apache + Active Directory Authentication How To</title><summary type='text'>OverviewUse Kerberos integration to fetch valid users and their passwords from the Active Directory to authenticate access to a web directory served by Apache.SystemAD Server: correladsWeb Server: correlprodWeb Service: Apache2 + mod_auth_kerbProtected directory: /var/www/mrtgConfigurationApache + KerberosVerify that mod_auth_kerb is available on the system (/usr/lib64/httpd/modules/). If not </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4942130457333921041'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4942130457333921041'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/apache-active-directory-authentication.html' title='Apache + Active Directory Authentication How To'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-9052782215409680295</id><published>2009-09-05T19:52:00.000+05:30</published><updated>2009-09-05T19:53:06.320+05:30</updated><title type='text'>Portal JSR</title><summary type='text'> Portlet JSRs       The Portlet specification will define a Portlet API that provides means for aggregating several content sources and applications front ends. It will also address how the security and personalization is handled. Portlets are web components -like Servlets- specifically designed to be aggregated in the context of a composite page. Usually, many Portlets are invoked to in the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9052782215409680295'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9052782215409680295'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/portal-jsr.html' title='Portal JSR'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2421103363767525351</id><published>2009-09-05T14:44:00.002+05:30</published><updated>2009-09-05T14:53:16.621+05:30</updated><title type='text'>Best Practices – Build and Deployment</title><summary type='text'>Table of Contents1. Introduction 12. Lessons Learned 13. Web Services Standards Gap 34. Tools Gap 35. Design Constraint Implications 36. Best Practices &amp; Recommendations 46.1 Using open source tools ANT and DPTK 46.1.1 Ant 46.1.2 Design Pattern Toolkit (DPTK) 46.2 Deployable Portal Artifacts 46.3 The Build and Deploy Sequences 76.4 Interaction between the Architecture Layers 127. Conclusion 13 5/</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2421103363767525351'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2421103363767525351'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/best-practices-build-and-deployment.html' title='Best Practices – Build and Deployment'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5871923598658518656</id><published>2009-09-05T01:29:00.001+05:30</published><updated>2009-09-05T01:32:24.768+05:30</updated><title type='text'>How do you display additional attributes on the Person Card?</title><summary type='text'>&lt;!-- OneX body.doc --&gt;&lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;           You have configured the People Finder portlet. You then search for a user, and you have the ability to display the Person Card by hovering over the search results. You are able to see the Person Card but want to display additional attributes on the Person </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5871923598658518656'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5871923598658518656'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/09/how-do-you-display-additional.html' title='How do you display additional attributes on the Person Card?'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-9008405294298780222</id><published>2009-08-31T01:12:00.001+05:30</published><updated>2009-08-31T01:13:32.164+05:30</updated><title type='text'>How to combine the results of queries based on two criteria in the Web Content Management local rendering portlet</title><summary type='text'>&lt;!-- OneX body.doc --&gt;&lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;               When using an IBM® Web Content Management (WCM) local rendering portlet, how can one utilize the combined query results based on two criteria? **Note:** This information is not included in the WebSphere Portal information center topic: Defining menu </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9008405294298780222'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/9008405294298780222'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/how-to-combine-results-of-queries-based.html' title='How to combine the results of queries based on two criteria in the Web Content Management local rendering portlet'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1118488065620146100</id><published>2009-08-31T01:05:00.001+05:30</published><updated>2009-08-31T01:08:10.150+05:30</updated><title type='text'>Steps to Expand and Collapse content items within Navigator Component</title><summary type='text'> How can I configure an IBM® Web Content Management (WCM)  Navigator component to expand and collapse the content item tree?        Edit the Navigator component.Set the following fields:"Start Type" to Selected"Ancestor Level" to All"Descendent Level" to "1 Level" as shown in the diagram.( This setting will display only the Site Areas beneath the selected Site Area ( Environment Program )  </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1118488065620146100'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1118488065620146100'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/steps-to-expand-and-collapse-content.html' title='Steps to Expand and Collapse content items within Navigator Component'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8766400901973223846</id><published>2009-08-25T23:31:00.003+05:30</published><updated>2009-08-26T00:50:04.342+05:30</updated><title type='text'>Using Log4J from a WebSphere Based Application</title><summary type='text'>Log4J is an easy to use and powerful logging system. This article will show you how to best configure and use Log4J from a typical WebSphere based application. We will develop a J2EE 1.3 application and test it with WebSphere V5. Initializing Log4J Initializing Log4J has been a thorny problem for a J2EE application. There are two ways  to initialize Log4J: Call PropertyConfigurator.configure(</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8766400901973223846'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8766400901973223846'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/using-log4j-from-websphere-based.html' title='Using Log4J from a WebSphere Based Application'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1092582126904799076</id><published>2009-08-24T22:54:00.001+05:30</published><updated>2009-08-24T22:54:41.514+05:30</updated><title type='text'>Adding Web 2.0 skins</title><summary type='text'>In conventional portal skins, a Control.jsp implements the code to render the decoration around a portlet. With the portal Web 2.0 theme, the portal renders the pages on the client. Therefore, rather than invoke a JSP to render the skin, it requires to execute an XSLT transformation. To achieve this, the portlet needs to register the following at bootstrap time in head_extras.jspf : The skin name</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1092582126904799076'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1092582126904799076'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/adding-web-20-skins.html' title='Adding Web 2.0 skins'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1039012691580884178</id><published>2009-08-24T22:12:00.000+05:30</published><updated>2009-08-24T22:45:02.689+05:30</updated><title type='text'>Configuring SSO with LTPA</title><summary type='text'>just wasted a few hours of my life because of some careless mistake made by our computer engineers.  I was tasked to configure single sign on for two servers, a Websphere Application Server v6 and a Websphere Portal Server v6. I configured my application server to use the same LDAP configuration as the portal. Export the LTPA key from Websphere Portal and import it to WAS.  I thought it will work</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1039012691580884178'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1039012691580884178'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/configuring-sso-with-ltpa.html' title='Configuring SSO with LTPA'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7855648889162518431</id><published>2009-08-24T21:09:00.001+05:30</published><updated>2009-08-24T22:11:56.761+05:30</updated><title type='text'>Adding Custom Attributes to WebSphere Portal</title><summary type='text'>Before adding any new attribute, the current attribute configuration should be validated and corrected with proper mappings and removing not required attributes.How to Validate/Verify the Attribute Mapping ?Run ConfigEngine.bat wp-validate-standalone-ldap-attribute-config -DWasPassword=secretAfter successfully completing the above command, review the ConfigTrace.log file from \ConfigEngine\log </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7855648889162518431'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7855648889162518431'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/adding-custom-attributes-to-websphere.html' title='Adding Custom Attributes to WebSphere Portal'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2214918865237979448</id><published>2009-08-24T21:08:00.002+05:30</published><updated>2009-08-24T21:09:50.556+05:30</updated><title type='text'>Configuring WebSphere Portal 6.1 Security using Sun One LDAP</title><summary type='text'>     Scenario: Sun One LDAP Version 5.2 is installed on the same machine as WebSphere Portal 6.1. To use a custom LDAP schema as I extended the inetOrgPerson object and created a vPerson Object.Once the LDAP Server is installed, I created a suffix called dc=mycompany,dc=com and initialized this suffix. All these steps can be done using Sun One Administration Console.After the LDAP installation, I</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2214918865237979448'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2214918865237979448'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/configuring-websphere-portal-61.html' title='Configuring WebSphere Portal 6.1 Security using Sun One LDAP'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3529739761287637497</id><published>2009-08-21T19:46:00.003+05:30</published><updated>2009-08-21T20:12:08.896+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='wcm jsp'/><title type='text'>WCM custom jsp files can be placed as separate ear/war inWebsphere portal 6.1</title><summary type='text'>Now we can get rid of copying the wcm custom jsp files of wcm jsp component or custom rich text editor/ custom jsp for element in authoring template into wcm product wars i.e. wcm.ear, local/remote/authoring portlets of the file system.This enhancement is part of WPS 6.1 and for custom jsp of wcm can be deployed as separate j2ee ear application on portal. Deployment and update of jsp now can be </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3529739761287637497'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3529739761287637497'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/wcm-custom-jsp-files-can-be-placed-as.html' title='WCM custom jsp files can be placed as separate ear/war inWebsphere portal 6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8650122045451408711</id><published>2009-08-21T02:45:00.001+05:30</published><updated>2009-08-21T02:45:53.628+05:30</updated><title type='text'>Considerations before Creating database for Websphere Portal</title><summary type='text'>View some important considerations before setting up Oracle databases to work with WebSphere Portal.  For information about creating databases, refer to the Oracle product documentation. For information on the recommended database architecture and the databases you will need to create, see the Planning for Oracle topic. Be sure that all databases to be used with WebSphere Portal are created as </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8650122045451408711'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8650122045451408711'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/considerations-before-creating-database.html' title='Considerations before Creating database for Websphere Portal'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3873842681149917908</id><published>2009-08-17T01:57:00.000+05:30</published><updated>2009-08-17T01:58:25.625+05:30</updated><title type='text'>IBM Lotus Connections, in plain English</title><summary type='text'>In my opinion, IBM Lotus Connections is primarily social networking software, not collaboration software. The social task management bit, however, is all about collaboration. And arguably, collaboration has spontaneously occurred in the blogs bit more than a few times (e.g., a problem with our internal intranet search was fixed because of a blog entry). And ok, the same could be said for forums </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3873842681149917908'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3873842681149917908'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/ibm-lotus-connections-in-plain-english.html' title='IBM Lotus Connections, in plain English'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1365046296126778286</id><published>2009-08-17T01:33:00.001+05:30</published><updated>2009-08-17T01:35:54.666+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='wsadmin'/><title type='text'>Quick hit JVM heap size change</title><summary type='text'>if you tasked to change the JVM heap size in approximately 2,500 servers today. ## Update the Heap size## ./wsadmin.sh -lang jython -f updateJVM.py#as = AdminConfig.getid('/Cell:YOUR_CELL_NAME/Node:YOUR_NODE_NAME/Server:YOUR_SERVER_NAME/')jvm = AdminConfig.list('JavaVirtualMachine', as)AdminConfig.modify(jvm, [['initialHeapSize', '512'], ['maximumHeapSize', "768"]])AdminConfig.save()# set the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1365046296126778286'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1365046296126778286'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/quick-hit-jvm-heap-size-change.html' title='Quick hit JVM heap size change'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4786846319819761044</id><published>2009-08-17T01:31:00.000+05:30</published><updated>2009-08-17T01:33:44.799+05:30</updated><title type='text'>wsadmin rotate jvm log files</title><summary type='text'>Simple, working, rotates logs at 10mb saving max 5 files.# rotateWasLogEPRN.py# Setup WAS Log file rotations# for yourserver## Implement:# ./wsadmin.sh -lang jython -f $FILE_LOCATION/rotateWasLogEPRN.py &gt;&gt; $TO_LOG_FILE## You can add this as you have other scripts in the deployment script# if you need help please let me know.##print "Changing the SystemOut &amp; SystemErr log file rotation </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4786846319819761044'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4786846319819761044'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/wsadmin-rotate-jvm-log-files.html' title='wsadmin rotate jvm log files'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2694320502792161151</id><published>2009-08-17T01:30:00.003+05:30</published><updated>2009-08-17T01:31:35.526+05:30</updated><title type='text'>Apache or IBM HTTP Server access_log rotation script</title><summary type='text'>We didn't have anything in place until one day, our access_log grew to over 2gig, OUCH :). Anyway, here is a simple cron script you could setup to execute nightly.#The script below creates a numbered copy of the log and then clears it#The date tag at the end of the copied log rotates from 0-6 so we never keep more than 7 days of logs#crontab is setup to run /usr/IHS/webserver*/bin/rotateaccess.sh</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2694320502792161151'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2694320502792161151'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/apache-or-ibm-http-server-accesslog.html' title='Apache or IBM HTTP Server access_log rotation script'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1130647299952999624</id><published>2009-08-17T01:30:00.001+05:30</published><updated>2009-08-17T01:30:29.687+05:30</updated><title type='text'>Create J2C authentication alias and assign to database</title><summary type='text'>Here you can create a J2C authentication alias and then assign it to a database.# create a new J2C authentication entry# set the security objectset security_root [$AdminConfig list Security]# set the attributes for the new objectset auth_alias [list alias "$alias"]set auth_descr [list description "Login for 4.0 Application"]set auth_userId [list userId "$username"]set auth_password [list password</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1130647299952999624'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1130647299952999624'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/create-j2c-authentication-alias-and.html' title='Create J2C authentication alias and assign to database'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2102837029858838788</id><published>2009-08-17T01:27:00.003+05:30</published><updated>2009-08-17T01:29:10.281+05:30</updated><title type='text'>Stopping and Starting a Cluster using wsadmin and jython for 5.1</title><summary type='text'>A simple jython script that accepts two incoming arguments to stop a cluster within a cell. This script is built with global use in mind, meaning you can create multiple shell scripts to pass the arguments to stopCluster.py. This can easily be manipulated to start the cluster too!Let the script begin########################################################### This program may be used, executed, </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2102837029858838788'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2102837029858838788'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/stopping-and-starting-cluster-using.html' title='Stopping and Starting a Cluster using wsadmin and jython for 5.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6952870615754536762</id><published>2009-08-15T17:47:00.001+05:30</published><updated>2009-08-15T17:49:01.301+05:30</updated><title type='text'>Restricting authentication based on group membership when configured for standalone LDAP</title><summary type='text'>How do you configure IBM WebSphere Portal so that only members of a specific group can log in if WebSphere Portal security is configured to use a standalone LDAP? The same general steps will be taken for each supported LDAP although the specific userFilter will differ depending on the LDAP brand and/or version.First, check with your LDAP administrator to confirm that your LDAP implements an </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6952870615754536762'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6952870615754536762'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/restricting-authentication-based-on.html' title='Restricting authentication based on group membership when configured for standalone LDAP'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1475054834370015717</id><published>2009-08-15T17:46:00.000+05:30</published><updated>2009-08-15T17:47:25.280+05:30</updated><title type='text'>How to restore WebSphere Portal back to the out-of-the-box security configuration</title><summary type='text'>&lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;         Question   Sometimes you may encounter a problem when you configure IBM WebSphere Portal security (standalone or federated). This problem can cause the system configuration files to be in an inconsistent state. Can you revert back to the original file registry configuration if </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1475054834370015717'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1475054834370015717'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/how-to-restore-websphere-portal-back-to.html' title='How to restore WebSphere Portal back to the out-of-the-box security configuration'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1923338631927807754</id><published>2009-08-15T17:44:00.000+05:30</published><updated>2009-08-15T17:45:32.893+05:30</updated><title type='text'>Allowing multiple login attributes in a non-realm environment</title><summary type='text'>Question   If you enable security with non-realm support, is it possible to allow users to log in with one of several possible attributes?    Answer   Yes. You must update the userFilter in the LDAP settings in the WebSphere® Application Server administrative console. For example, given the case where administrative users have "uid" but not "cn", and non-administrative users have "cn" but not "</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1923338631927807754'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1923338631927807754'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/allowing-multiple-login-attributes-in.html' title='Allowing multiple login attributes in a non-realm environment'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3805740754438077498</id><published>2009-08-12T22:27:00.003+05:30</published><updated>2009-08-12T22:28:12.462+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='jsr 168'/><title type='text'>JSR 168 Portlet Specifications</title><summary type='text'>Agenda•    What are JSR and JCP?•    What is a Portlet as per JSR 168?•    JSR168 SpecificationsPortlet Lifecycle MethodsPortlet ModesPortlet Window StatesPortlet Data ModelsDispatching requestsCaching and Security.•    A sample Portlet.What are JSR and JCP?JCP – Java Community ProcessThe international Java community develops and evolves Java™ technology specifications using the Java Community </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3805740754438077498'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3805740754438077498'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/jsr-168-portlet-specifications.html' title='JSR 168 Portlet Specifications'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-837150423997631133</id><published>2009-08-12T22:22:00.000+05:30</published><updated>2009-08-12T22:26:39.536+05:30</updated><title type='text'>Some Portal Servers</title><summary type='text'>List of Portal servers • Liferay - Liferay deploy portlets that adhere to the Portlet API (JSR 168).Its one of the most popular and most talked upon potal server in the recent market. It has lots of portlets bundled with the portal (Mail,Workflow, Document Library, Calendar, Message Boards,Wiki, to name a few) and can be used to develop for adding your own custom portlets.The Ext environment in </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/837150423997631133'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/837150423997631133'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/some-portal-servers.html' title='Some Portal Servers'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2362528381629241517</id><published>2009-08-12T22:21:00.000+05:30</published><updated>2009-08-12T22:22:08.449+05:30</updated><title type='text'>Portal and Portlets</title><summary type='text'>Traditional Web Application•    Shortcomings of traditional Web Application•    What is needed?•    What are Portlets? Portals?....•    The New Generation answer …..Traditional Web Application•    The “W W W”  --The world wide web ,subset of internet is responsible for information sharing.•    The Website Approach ---each application is developed separately like a website and deployed singly on a</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2362528381629241517'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2362528381629241517'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/portal-and-portlets.html' title='Portal and Portlets'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4566165909997189195</id><published>2009-08-12T02:00:00.000+05:30</published><updated>2009-08-12T02:01:44.071+05:30</updated><title type='text'>How to write Alphablox JSR168 Portlet in WebSphere Environment</title><summary type='text'> 					 						document.body.oncopy = function() { 							if (window.clipboardData) { 								setTimeout(function() { 									var text = clipboardData.getData("text");  									if (text &amp;&amp; text.length&gt;300) { 										text = text + "\r\n\n本文来自CSDN博客，转载请标明出处：" + location.href; 										clipboardData.setData("text", text);  									} 								}, 100); 							} 						} 					 					function StorePage</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4566165909997189195'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4566165909997189195'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/how-to-write-alphablox-jsr168-portlet.html' title='How to write Alphablox JSR168 Portlet in WebSphere Environment'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3060857237762091125</id><published>2009-08-11T21:13:00.000+05:30</published><updated>2009-08-12T01:59:18.900+05:30</updated><title type='text'>WebSphere Portal XMLAccess: discover different ways to refer resources in XML script</title><summary type='text'> 					 						document.body.oncopy = function() { 							if (window.clipboardData) { 								setTimeout(function() { 									var text = clipboardData.getData("text");  									if (text &amp;&amp; text.length&gt;300) { 										text = text + "\r\n\n本文来自CSDN博客，转载请标明出处：" + location.href; 										clipboardData.setData("text", text);  									} 								}, 100); 							} 						} 					 					function StorePage</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3060857237762091125'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3060857237762091125'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/websphere-portal-xmlaccess-discover_11.html' title='WebSphere Portal XMLAccess: discover different ways to refer resources in XML script'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8663046723249656680</id><published>2009-08-11T21:11:00.000+05:30</published><updated>2009-08-11T21:13:02.090+05:30</updated><title type='text'>Use Portal 6.0 Advanced URL Generation Helper Class ServletURLGenerator to Generate URL of portlet</title><summary type='text'> 					 						document.body.oncopy = function() { 							if (window.clipboardData) { 								setTimeout(function() { 									var text = clipboardData.getData("text");  									if (text &amp;&amp; text.length&gt;300) { 										text = text + "\r\n\n本文来自CSDN博客，转载请标明出处：" + location.href; 										clipboardData.setData("text", text);  									} 								}, 100); 							} 						} 					 					function StorePage</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8663046723249656680'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8663046723249656680'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/use-portal-60-advanced-url-generation.html' title='Use Portal 6.0 Advanced URL Generation Helper Class ServletURLGenerator to Generate URL of portlet'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-802032461758697237</id><published>2009-08-11T01:14:00.000+05:30</published><updated>2009-08-11T01:18:16.835+05:30</updated><title type='text'>Set correct HTTP response-cache headers to improve response times</title><summary type='text'>ProblemYou experience slow responses when accessing Lotus® Quickr™ services for WebSphere® Portal on a remote network or over a slow network connection (for example, DSL, Cable Modem). Resolving the problemSetting the proper response-cache headers in the HTTP server configuration allows caching of the static Lotus Quickr resources on the HTTP server and improves response times. To do so, use the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/802032461758697237'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/802032461758697237'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/set-correct-http-response-cache-headers.html' title='Set correct HTTP response-cache headers to improve response times'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1906283547382212576</id><published>2009-08-11T00:30:00.000+05:30</published><updated>2009-08-11T01:14:03.647+05:30</updated><title type='text'>How to install the Information Center help system plug-in into Rational development tools</title><summary type='text'>      &lt;!-- OneX body.doc --&gt;&lt;!--BEGIN MAIN BODY CONTENT--&gt;    &lt;!--BEGIN CONTENT--&gt; &lt;!-- ******** PASTE MAIN BODY CONTENT HERE ******** --&gt;         Problem(Abstract)   Many IBM® products such as WebSphere© Application Server, WebSphere Portal Server, IBM Java Runtime Environment, make their Help available on the Internet as an Information Center. These information centers can be downloaded as </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1906283547382212576'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1906283547382212576'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/how-to-install-information-center-help.html' title='How to install the Information Center help system plug-in into Rational development tools'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-4450449645996855735</id><published>2009-08-10T23:06:00.000+05:30</published><updated>2009-08-10T23:45:48.369+05:30</updated><title type='text'>Enable GZIP compression on HTTP server to improve response time</title><summary type='text'>       Problem   You experience slow responses when accessing Lotus® Quickr™ services for WebSphere® Portal on a remote network or over a slow network connection (for example, DSL, Cable Modem).     Resolving the problem   Enabling GZIP compression on the HTTP Server serving Lotus Quickr resources reduces the amount of content that has to be downloaded and improves response times. To do so, use </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4450449645996855735'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/4450449645996855735'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/enable-gzip-compression-on-http-server.html' title='Enable GZIP compression on HTTP server to improve response time'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5630000211024019102</id><published>2009-08-10T23:04:00.003+05:30</published><updated>2009-08-10T23:06:13.705+05:30</updated><title type='text'>Extending and Customizing WAS Authentication and WPS 51 Login</title><summary type='text'>SSO! is a three letter word but there is more to it. If you need to bypass portal login in order to control Authentication through a third party customized securtiy framework, the only way to do it is by writing a middleware class called Trust Association Interceptor.When you configure WAS to user LTPA and Trust Association with a customized interceptor. Your WAS becomes partly ready for </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5630000211024019102'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5630000211024019102'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/extending-and-customizing-was.html' title='Extending and Customizing WAS Authentication and WPS 51 Login'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7489758604277097465</id><published>2009-08-01T21:51:00.000+05:30</published><updated>2009-08-01T21:52:21.019+05:30</updated><title type='text'>Export / Import LTPA-Keys for Single Sign On (SSO)</title><summary type='text'>Sometimes its necessary to implement an SSO-Enviroment over different WebSphere-Cells (e.g. Production-Cell and Acceptance-Cell). To do this both cells need the same LTPA-Keys.The synchronization of LTPA-Keys can be done over Admin-Console.1. To Export  LTPA-Keys from a Cell navigate toSecurity &gt; Secure administration, applications, and infrastructure &gt;                    Authentication </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7489758604277097465'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7489758604277097465'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/export-import-ltpa-keys-for-single-sign.html' title='Export / Import LTPA-Keys for Single Sign On (SSO)'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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://3.bp.blogspot.com/_JB53H1eiJxU/SA7uwRhxzOI/AAAAAAAAAAs/9FNKEm394s0/s72-c/exportkeys.JPG' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8565995315912388854</id><published>2009-08-01T21:50:00.001+05:30</published><updated>2009-08-01T21:50:44.167+05:30</updated><title type='text'>Startup behavior of an application</title><summary type='text'>When you need to disable the auto-start option of an application go to "Enterprise Applications &gt; Name of Application &gt; Target specific application status", select Application Server and click "Disable Auto Start".To adjust the startup order go to "Enterprise Applications &gt; Name of Application &gt; Startup behavior" and adjust to Startup order by changing the field-value.Applications with lowest </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8565995315912388854'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8565995315912388854'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/startup-behavior-of-application.html' title='Startup behavior of an application'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3170234016897652021</id><published>2009-08-01T21:48:00.000+05:30</published><updated>2009-08-01T21:49:36.857+05:30</updated><title type='text'>Reinstall Admin Console (isclite)</title><summary type='text'>If administrative console is broken or was accidentally uninstalled (happens typically in base-version of WAS), re-deployment (reinstall) of console-application can be done with jython script deployConsole.py located in bin-folder.1. First a clean removal of the old admin-console deployment is nessacary"System-folder"/bin/wsadmin.sh -lang jython -f deployConsole.py remove2. Now reinstall of </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3170234016897652021'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3170234016897652021'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/reinstall-admin-console-isclite.html' title='Reinstall Admin Console (isclite)'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5854500139544800264</id><published>2009-08-01T21:47:00.000+05:30</published><updated>2009-08-01T21:48:25.092+05:30</updated><title type='text'>Increase performance of applications with servlet caching</title><summary type='text'>WebSphere Application Server (Version 5,6,6.1) provides the servlet caching option to increase the performance of applications. If servlet caching is enabled, the servlet output will be held in RAM of the physical application server. As an result clients can be served faster. In my tests i noticed a performance increase about 50 percent.So how to enable servlet caching?1. In administrative </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5854500139544800264'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5854500139544800264'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/increase-performance-of-applications.html' title='Increase performance of applications with servlet caching'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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/_JB53H1eiJxU/SEU5Y4rp-jI/AAAAAAAAABQ/vIDYVKLQ_RM/s72-c/dynamiccacheservices.JPG' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-873038763070088675</id><published>2009-08-01T21:46:00.001+05:30</published><updated>2009-08-01T21:46:48.539+05:30</updated><title type='text'>Rebuilding an application EAR-File</title><summary type='text'>Sometimes its nessesary to extract an application and to (re)-build an EAR-File which can be deployed on another Application Server.Tools needed: Eclipse WTP1. Copy  the application-folder to your local harddrive2. Start Eclipse WTP and create an new project2.1 Select File &gt; New &gt; Project... &gt; Dynamic Web Project2.2 Enter a project name2.3 Select "Add project to an EAR" and click "New"2.4 Enter a</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/873038763070088675'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/873038763070088675'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/rebuilding-application-ear-file.html' title='Rebuilding an application EAR-File'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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/_JB53H1eiJxU/SE4wyMnlhLI/AAAAAAAAABg/L5Fkpw1A7GU/s72-c/webcontent.JPG' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2571950222141396747</id><published>2009-08-01T21:42:00.000+05:30</published><updated>2009-08-01T21:44:09.369+05:30</updated><title type='text'>Copy resource declarations to other cell</title><summary type='text'>If you setting up an new WAS Node/Cell with a own Deployment Manager configuration (installation) you can easily import the resource declarations (JDBC-Resources,Data Sources) from an already working WAS Installation to the newly created WAS Node/Cell/Profile.Steps:1. Import LTPA-Keys to new Cell2. Copy over /"Profile_Path"/config/cells/"Cell_Name"/resources.xml to the new installation2.1 Ensure </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2571950222141396747'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2571950222141396747'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/copy-resource-declarations-to-other.html' title='Copy resource declarations to other cell'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5534913614835118450</id><published>2009-08-01T21:41:00.000+05:30</published><updated>2009-08-01T21:42:26.533+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='was'/><title type='text'>Enable session failover in clusters</title><summary type='text'>Sometimes its necessary to synchronize the whole session between two (or more) cluster members. Especially when some important attributes are stored in the session (search,...).WebSphere offers an option called "Session Replication" to avoid the lost of a session because of a crashed  Cluster Member.First you need to setup a replication domain for the cluster1.1. Go to Enviroment &gt; Replication </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5534913614835118450'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5534913614835118450'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/enable-session-failover-in-clusters.html' title='Enable session failover in clusters'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2968693095303275036</id><published>2009-08-01T21:39:00.000+05:30</published><updated>2009-08-01T21:40:01.706+05:30</updated><title type='text'>Show all JNDI-entries</title><summary type='text'>Sometimes you need to get all entries in the JNDI-namespace (JNDI=Java Naming and Directory Interface). In order to do this you can use the script dumpNameSpace.sh (.bat).Just execute dumpNameSpace.shThe script is located in the bin-folder of the profile-root./"WebSphere_Profile_Root"/bin/dumpNameSpace.sh(.bat)Its possible to limit the output to a cell or a node. All avaiable parameters can be </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2968693095303275036'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2968693095303275036'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/show-all-jndi-entries.html' title='Show all JNDI-entries'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1356834936449764941</id><published>2009-08-01T21:37:00.001+05:30</published><updated>2009-08-01T21:37:54.886+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='wsadmin'/><title type='text'>Stop and uninstall an application using wsadmin</title><summary type='text'>Before the application can be unsinstalled it must be stopped.Steps:1. Open wsadmin (with jython)1.1 Go to "WebSphere_Profile_Root"/bin1.2 Executewsadmin.sh(.bat) -lang jython1.3 Enter UserID/Password (if promted)2. Define needed cell and node variables2. Executecell=AdminConfig.list('Cell')cellname=AdminConfig.showAttribute(cell,'name')nodes=AdminConfig.list('Node',cell)nodename=</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1356834936449764941'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1356834936449764941'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/stop-and-uninstall-application-using.html' title='Stop and uninstall an application using wsadmin'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1858043316907855825</id><published>2009-08-01T21:36:00.001+05:30</published><updated>2009-08-01T21:36:45.699+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='wsadmin'/><title type='text'>Install and start an application using wsadmin</title><summary type='text'>Copy the application ear-file to /installableApps1. Open wsadmin (with jython)1.1 Go to "WebSphere_Profile_Root"/bin1.2 Executewsadmin.sh(.bat) -lang jython1.3 Enter UserID/Password (if promted)2. Define needed cell and node variables2. Executecell=AdminConfig.list('Cell')cellname=AdminConfig.showAttribute(cell,'name')nodes=AdminConfig.list('Node',cell)nodename=AdminConfig.showAttribute(nodes,'</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1858043316907855825'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1858043316907855825'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/install-and-start-application-using.html' title='Install and start an application using wsadmin'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5326296913400343089</id><published>2009-08-01T21:30:00.001+05:30</published><updated>2009-08-01T21:34:33.888+05:30</updated><title type='text'>websphere</title><summary type='text'>Cell:A Cell is a logical group of all nodes and there deployment manager.Node:A node is a group of profiles. Typically one node represents a physical server.However its possible to install/run more than one node on a physical server (through profiles).Node agent:A Node agent is managing a node. The node agent is needed to access the applications.JVM (App server):A JVM (Java Virtual Machine) is a </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5326296913400343089'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5326296913400343089'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/websphere.html' title='websphere'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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/_0JAfDlaB6OA/SnRngxXgfUI/AAAAAAAAACw/sGXsV29VXzw/s72-c/WebSphere+Nomenclatur.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5945277387049522837</id><published>2009-08-01T21:29:00.000+05:30</published><updated>2009-08-01T21:30:44.972+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='sso'/><title type='text'>Liferay and WebSphere SSO (simplistic)</title><summary type='text'>Since Liferay is providing CAS (Central Authentication Service) support its possible to access Liferay through WebSphere SSO (LTPA tokens) login credentials.So what to do?I can not post all of our source code because of "some security" issues :-)Steps:1. Edit portel-ext.properties (or portal-impl.jar//portal.properties)1.1 Add/Edit the CAS configuration lines#### CAS##cas.auth.enabled=</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5945277387049522837'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5945277387049522837'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/liferay-and-websphere-sso-simplistic.html' title='Liferay and WebSphere SSO (simplistic)'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1197401820111563036</id><published>2009-08-01T18:24:00.001+05:30</published><updated>2009-08-01T18:24:53.339+05:30</updated><title type='text'>How to compare 2 LDAP-Directories</title><summary type='text'>The comparison of the LDAP-Directories is a bit harder as it sounds.The biggest problem is the lack of tools to do this research.Finally i found i tool a called ldapcmp. It seems its quite old but it works under Windows XP.How to:1. Download the SUN LDAP C SDK (you need to register) - Platform: Windows 95 4.0 for XP2. Extract the zip file3. Copy the ldapcmp.exe from \tools to \lib4. Execute the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1197401820111563036'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1197401820111563036'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/how-to-compare-2-ldap-directories.html' title='How to compare 2 LDAP-Directories'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-5971260719610730692</id><published>2009-08-01T18:22:00.000+05:30</published><updated>2009-08-01T18:23:19.312+05:30</updated><title type='text'>Enable SSL (HTTPs) for IBM HTTP Server</title><summary type='text'>To enable SSL on a IBM HTTP Server (Client -&gt; IHS), you need to generate a proper certificate first.Steps to generate self-signed-certificate for https traffic:1. Open //bin/ikeyman2. Select CMS as type and specify a file name and a location for the certificate file3. When prompted for a password type in your desired password.4. Click Create &gt; New Self-Signed Certificate in iKeyman. Type in your </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5971260719610730692'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/5971260719610730692'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/enable-ssl-https-for-ibm-http-server.html' title='Enable SSL (HTTPs) for IBM HTTP Server'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6285783001329069686</id><published>2009-08-01T18:21:00.000+05:30</published><updated>2009-08-01T18:22:48.380+05:30</updated><title type='text'>Form Login for WebSphere Application Server 6.1</title><summary type='text'>To enable a form based login (instead of a Basic Authentification) edit the web.xml of the application and add a login configuration:FORMExample Form-Based Authentication Area/login.jsp/error.jspThe login.jsp contains the login form (ibm example):&lt;!DOCTYPE HTML PUBLIC "-//W3C/DTD HTML 4.0 Transitional//EN"&gt; Security FVT Login Page Form Login  Enter user ID and password:  User ID  Password    </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6285783001329069686'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6285783001329069686'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/form-login-for-websphere-application.html' title='Form Login for WebSphere Application Server 6.1'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1738255182244767283</id><published>2009-08-01T18:20:00.000+05:30</published><updated>2009-08-01T18:21:03.771+05:30</updated><title type='text'>Enable g-zip for IBM HTTP Server</title><summary type='text'>In order to deflate the content served form a IBM HTTP Server (IHS) it is possible to enable the g-zip-option in httpd.conf to compress the traffic between a client and a IHS.To enable g-zip add this lines at the bottom of httpd.conf:# compress everything but imagesLoadModule deflate_module modules/mod_deflate.soDeflateFilterNote Input instreamDeflateFilterNote Output outstreamDeflateFilterNote </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1738255182244767283'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1738255182244767283'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/enable-g-zip-for-ibm-http-server.html' title='Enable g-zip for IBM HTTP Server'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-737676966443398209</id><published>2009-08-01T18:18:00.000+05:30</published><updated>2009-08-01T18:19:05.834+05:30</updated><title type='text'>Set HTTP Response Header Cache-Control and enable mod_cache for higher performance</title><summary type='text'>To enable the ability of caching of pictures open the httpd.conf of your IBM HTTP Server and add following linesLoadModule headers_module modules/mod_headers.soHeader add Cache-Control "public, max-age=432000, post-check=172000"These lines enable the module mod_headers.so and are setting a Cache-Control header. A Cache-Control header enables clients, webservers and proxys to cache pictures.Adding</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/737676966443398209'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/737676966443398209'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/set-http-response-header-cache-control.html' title='Set HTTP Response Header Cache-Control and enable mod_cache for higher performance'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2088939535787969485</id><published>2009-08-01T13:22:00.000+05:30</published><updated>2009-08-01T13:24:25.567+05:30</updated><title type='text'>WebSphere Portal XMLAccess: discover different ways to refer resources in XML script</title><summary type='text'>One of the important topics in XMLAccess is how to refer existing resources in portal. In most cases, three kinds of concepts are used, they are ObjectID, Symbolic object ID, and unique name. Here I make a comparison between them.Comparison between ObjectID, Symbolic object ID, and unique name 	 Object ID	ID generating modeObject Id(Symbolic object ID)	Unique nameUsed to </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2088939535787969485'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2088939535787969485'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/08/websphere-portal-xmlaccess-discover.html' title='WebSphere Portal XMLAccess: discover different ways to refer resources in XML script'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-803864510109890151</id><published>2009-07-27T21:30:00.000+05:30</published><updated>2009-07-27T21:31:36.246+05:30</updated><title type='text'>Achieving optimal Authoring performance in v6 of Web Content Management</title><summary type='text'>How can you achieve optimal performance for Authoring in Web Content Management version 6? If you do not tune the system, users can experience slow Authoring performance, which can slow down the content creation process. Performance degradation can manifest itself during save or delete operations, during UI navigation, and during other key Web Content Management functions. CauseAs with any </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/803864510109890151'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/803864510109890151'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/achieving-optimal-authoring-performance.html' title='Achieving optimal Authoring performance in v6 of Web Content Management'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1966740087474947507</id><published>2009-07-25T16:27:00.000+05:30</published><updated>2009-07-25T16:29:00.661+05:30</updated><title type='text'>Alternatives for fixing unchecked redirect vulnerabilities</title><summary type='text'>Unchecked redirect vulnerabilities are annoying to fix for our customers. Sometimes the developers need to link to a constantly changing selection of partners and they always have to support different redirect URLs for testing, integration, and production. Sometimes these redirect mechanisms span different applications even though they live on the same domain, too. Given the unstable nature of </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1966740087474947507'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1966740087474947507'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/alternatives-for-fixing-unchecked.html' title='Alternatives for fixing unchecked redirect vulnerabilities'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-3769884544259485954</id><published>2009-07-25T16:21:00.000+05:30</published><updated>2009-07-25T16:22:04.497+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='sso'/><title type='text'>Single Sign-On fails with SiteMinder due to incorrect agent group settings</title><summary type='text'>Problem(Abstract)After configuring eTrust SiteMinder for WebSphere Portal, you still get prompted for the portal server login after authenticating via the SiteMinder login feature.CauseTAI not added to agent group in SiteMinderResolving the problemCheck the Agent Groups section via the SiteMinder Administration Console. Agent groups can be specified which allow you to add multiple TAIs into one </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3769884544259485954'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/3769884544259485954'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/single-sign-on-fails-with-siteminder.html' title='Single Sign-On fails with SiteMinder due to incorrect agent group settings'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-8249448092824683882</id><published>2009-07-25T16:16:00.000+05:30</published><updated>2009-07-25T16:17:02.907+05:30</updated><title type='text'>Window useful commands</title><summary type='text'>* &amp;&amp; - Command Chaining    * %SYSTEMROOT%\System32\rcimlby.exe -LaunchRA - Remote Assistance (Windows XP)    * appwiz.cpl - Programs and Features (Formerly Known as "Add or Remove Programs")    * appwiz.cpl @,2 - Turn Windows Features On and Off (Add/Remove Windows Components pane)    * arp - Displays and modifies the IP-to-Physical address translation tables used by address resolution protocol (</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8249448092824683882'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/8249448092824683882'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/window-useful-commands.html' title='Window useful commands'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6091714842378864859</id><published>2009-07-25T02:50:00.001+05:30</published><updated>2009-07-25T02:51:53.556+05:30</updated><title type='text'>How to use the WCM API to retrieve content element information such as image component file size</title><summary type='text'>QuestionYou would like to use the IBM® Web Content Management (WCM) API to access a content item's element and retrieve information. How can you retrieve the size of an image file stored in an image component? AnswerThe WCM API provides methods which allow access to a content item's elements, such as an image component.Summary: How to access a content's element.In this example, we retrieve the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6091714842378864859'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6091714842378864859'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/how-to-use-wcm-api-to-retrieve-content.html' title='How to use the WCM API to retrieve content element information such as image component file size'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7957115188705157035</id><published>2009-07-24T22:18:00.001+05:30</published><updated>2009-07-24T22:19:48.147+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='Best Practices'/><title type='text'>Best Practice: Catching and re-throwing Java Exceptions</title><summary type='text'>QuestionWhat is the correct Java™ programming best practice to catch, print, and re-throw Java exceptions? CauseProblem determination is often hampered by mysterious errors, misleading information, or missing stack traces. AnswerIt is a well-known best practice that a Java application should not suppress caught exceptions with blank catch blocks; however, there are more subtle mistakes that Java </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7957115188705157035'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7957115188705157035'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/best-practice-catching-and-re-throwing.html' title='Best Practice: Catching and re-throwing Java Exceptions'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-6725347248516242415</id><published>2009-07-22T01:20:00.000+05:30</published><updated>2009-07-22T01:22:12.966+05:30</updated><title type='text'>The Portal Scripting Interface</title><summary type='text'>One of the great advantages of the WebSphere software platform is that it's been built with a great deal of flexibility. A product simply wouldn't bear the WebSphere name if there weren't several different ways to do things. WebSphere Portal Server is no exception. With the release of version 5.1 IBM has added another way to administer the configuration of the Portal. This is sure to delight the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6725347248516242415'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/6725347248516242415'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/portal-scripting-interface.html' title='The Portal Scripting Interface'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-1857255074541183035</id><published>2009-07-21T22:26:00.002+05:30</published><updated>2009-07-21T22:33:35.057+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='syndication'/><title type='text'>How to troubleshoot :Users do not have access to syndicated content</title><summary type='text'>Problem:After syndicating between two or more Web Content Management (WCM) instances, on the subscriber instance users do not have access to the newly syndicated content. In the security section of the content items, the users appear to have been given access; however, the content is still not accessible to these users in the new environment. In some cases you may no longer see the Author/Owner </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1857255074541183035'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/1857255074541183035'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/how-to-troubleshoot-users-do-not-have.html' title='How to troubleshoot :Users do not have access to syndicated content'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-2221251818735258914</id><published>2009-07-20T22:31:00.002+05:30</published><updated>2009-07-20T22:40:52.595+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='sso'/><category scheme='http://www.blogger.com/atom/ns#' term='desktop'/><title type='text'>Single SignOn from the operating system desktop to WebSphere Portal</title><summary type='text'>How To: A browser can automatically authenticate a user against the WebSphere Portal, based on the login to the operating system desktop. This feature is sometimes requested by customers for employee portals.   Solution Warning: Some of the configurations described here are not officially supported. For details, see the Hint and Tip document 1104689: "Basic authentication is not supported as a </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2221251818735258914'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/2221251818735258914'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/single-signon-from-operating-system.html' title='Single SignOn from the operating system desktop to WebSphere Portal'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-7657057108028102176</id><published>2009-07-19T22:03:00.000+05:30</published><updated>2009-07-19T22:04:33.380+05:30</updated><title type='text'>How to assign a new portal administration group aside from wpsadmins</title><summary type='text'>For a client who is using a single LDAP repository for both Staging and Production. However, they wanted a separate portal admin group for Staging and Production. For production environment, wpsadmins is sufficient but for staging, aside from wpsadmins, they wanted to add a new group meant for the staging administrators. Staging administrators can only access staging server and shouldn't access </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7657057108028102176'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/7657057108028102176'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/how-to-assign-new-portal-administration.html' title='How to assign a new portal administration group aside from wpsadmins'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry><entry><id>tag:blogger.com,1999:blog-4875218282209868040.post-274203255025195293</id><published>2009-07-19T13:59:00.001+05:30</published><updated>2009-07-19T14:10:16.697+05:30</updated><category scheme='http://www.blogger.com/atom/ns#' term='portal access control'/><title type='text'>How to fix Portal Access Control settings after user/group external identifiers have changed</title><summary type='text'>The access controls on resources in IBM WebSphere Portal are linked to external identifiers associated with each user/group stored in LDAP. The requirements for such an external identifier includes that it be static and unique.However, in certain scenarios in which an LDAP server is changed or users or groups are removed and re-added directly to the LDAP, the external identifiers are no longer </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/274203255025195293'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/4875218282209868040/posts/default/274203255025195293'/><link rel='alternate' type='text/html' href='http://kaushalksinha.blogspot.com/2009/07/how-to-fix-portal-access-control.html' title='How to fix Portal Access Control settings after user/group external identifiers have changed'/><author><name>Kaushal Blog</name><uri>http://www.blogger.com/profile/04551809763904798508</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></entry></feed>
