Thursday, January 20, 2011
For (eg) to add a new LDAP attribute (PreferredGivenName) , Just add this below xml section to wimxmlextension.xml ,
<wim:propertySchema nsURI="http://www.ibm.com/websphere/wim" dataType="String" multiValued="false" propertyName="PreferredGivenName"> <wim:applicableEntityTypeNames>PersonAccount</wim:applicableEntityTypeNames> </wim:propertySchema>
<config:attributes name="PreferredGivenName" propertyName="PreferredGivenName"> <config:entityTypes>PersonAccount</config:entityTypes> <config:entityTypes>Group</config:entityTypes> </config:attributes>
to wimconfig.xml as mentioned in the above directory location. Repeat the above for additional new attributes. Except for LA (Lookaside) to need to update the LAPROP table in the db.
Sunday, January 16, 2011
If you look at the above stats , since Oct 2009 I used to get like an average of 150 visitors/day and then it suddenly dropped just like 30 visitors/day. Nothing really happened, same number of blog posts, nothing deleted , no changes in terms of blog settings or nothing. There was no clue why it dropped suddenly which then i followed up with google several time using their webmaster tools for reconsideration of my website to re-index or fix. But never really got anything useful from them except their automated generated message and really got frustrated and gave up,
Google's reply ,
We received a request from a site owner to reconsider how we index the following site: http://webspherehelp.blogspot.
We've now reviewed your site. When we review a site, we check to see if it's in violation of our Webmaster Guidelines. If we don't find any problems, we'll reconsider our indexing of your site. If your site still doesn't appear in our search results, check our Help Center for steps you can take.
This is an automated message from Webmaster Tools. Please do not reply to this email. For help, please visit http://www.google.com/support/
Sunday, January 3, 2010
<executor name="webThreadPool" nameprefix="web-" maxthreads="100" minsparethreads="10"></executor>
Based on the above configuration, 0 threads will be created after the tomcat startup, depending on the number of concurrent requests number of threads will be created in the thread pool, for instance if there are 5 concurrent requests then 5 threads will be created in the pool and these threads are further reused by subsequent requests until more concurrent requests come where further threads will be created. Because of the minSpareThreads value of 10 all the threads created up to 10 will not be discarded irrespective of whether the threads are idle or not. Thread pools shrink based on the maxIdleTime which by default is 60000 ms/ 60 secs / 1 minute meaning if a thread is idle for 60 secs tomcat will discard it from the pool.Suppose there is a spike in the number of concurrent requests say 50 then about 50 threads will be created in the pool to accommodate the spike. if your average is 1 request/sec except during the spike you would expect the threadpool to shrink after the spike, but unfortunately this is not how tomcat does. Tomcat uses the logic in such a way that the threads are picked and used in a round-robin manner from the pool, since you are getting about a average of 1 requests/sec the thread pool won't shrink since all the 50 existing threads in the pool will be used at least once within a minute when there are 1 requests/sec coming. Ideally, I would expect tomcat to reuse the same free/idle thread (Most Recently Used thread) as much as possible instead of the round-robin policy to be able to discard the idle thread. Since it's not working as expected the only way to control is to reduce the maxIdle time with an optimal value, but reducing the maxIdle time also possess some risks. This also becomes an inconvenience if your monitoring system is alerting based on the number of thread pool count, in such cases using activeCount value of the thread pool is a wise thing to avoid false alerts.
<executor name="webThreadPool" nameprefix="web-" maxthreads="400" minsparethreads="10" maxidletime="3000"></executor>
Sunday, September 20, 2009
Saturday, September 19, 2009
1) If you suspect if the problem is product related, start by opening a service request or PMR (Problem Management Record) either through online or by calling the IBM Support 1-800-IBM-SERV. You might need a IBM customer number.
2) Start with a simple description of the problem when you open a PMR.
3) Make sure you provide a clear description in such a way it represents the problem area so that your PMR gets assigned to the right team as there are several teams with different specialization within the same product , so that you will save time by getting the problem assigned to the correct team. If you know the team before hand then specify the team queue in the PMR.
4) Specify mode of communication in the PMR either by email or phone. If you think the problem is complex and need some explanation to do, then specify phone call back so that IBM support representative can call back and understand the problem, if you think the problem something trivial a little description in the PMR would make them understand then specify email.
5) Collect MustGather documents either manually or using http://www-01.ibm.com/software/support/isa/ IBM Support Assistant tool and then attach the the logs to PMR which will help in faster resolution to the PMR.
6) If possible, try to create a reproducible test case preferably outside to your custom application, so that IBM can use this test case to test it in the lab and provide a solution, Also it will also help to isolate that the problem is not related to your company's custom code or the environment.
7) Please use commonly used terminologies when updating the PMR or talking to IBM Support representative instead of the terminologies that you might use within your IT department as it might confuse the person handling the PMR as different companies use different ways to describe a problem. Clarify things if and when needed.
8) Specify the severity and priority in the PMR, Be reasonable and provide a business justification, set your expectations like when you need the next update and when the problem should be resolved, so that they can work towards it.
9) Please update the PMR with any new findings and updates as and when you come to know or also when you need progress updates from IBM.
10) Understand the escalation procedure and use it to escalate when things are not moving as reasonably expected.
11) Be friendly and appreciate the IBM Support representative work when problem gets resolved.
12) Follow the instructions from IBM even though it doesn't make sense sometimes , otherwise it would become a bottleneck to proceed to the next step in debugging the problem.
13) Besides doing all the above you can also self serve simultaneously by searching support knowledge base, infocenter , forums , etc, as there might be problems with an already known resolution.
Thursday, September 17, 2009
You can still continue to vote though:
Poll: On what OS your WebSphere AppServer is installed ?
Tuesday, September 8, 2009
Here are some of the IBM WebSphere related twitters having interesting tweets on various topics related to IBM WebSphere Product Family.
IBM_WAS IBM WAS SupportIBM WebSphere Application Server support news, updates, and information.
IBM_Commerce IBM Commerce SupportIBM WebSphere Commerce support news, updates, and information.
IBM_WPS IBM WPS SupportIBM WebSphere Process Server support news, updates, and information.
IBM_Monitor IBM Monitor SupportIBM WebSphere Business Monitor Support page.
IBM_Modeler IBM Modeler SupportIBM WebSphere Business Modeler support.
WebSphereBUZZ WebSphere Buzz News.
WebSpherePortal WebSphere PortalYour location for interesting links associated with IBM WebSphere Portal.
WebSphereHelp WebSphere Help, Tips & Tricks.