WebSphere Portal now comes with something called "portal light mode". Once enabled, a set of portlet applications are not started during portal startup. it works on line of lazy loading wherin these portlet applications are started when portal recieves a first http request for the portlet.
wp.base_ProfileEarAttributesTargetMapInclList.jacl contains the list of portlet applications that has to be lazily loaded.
COMMAND TO ENABLE LIGHT MODE
ConfigEngine.bat enable-portal-light-startup-performance -DWasPassword=password
COMMAND TO ENABLE LIGHT MODE
ConfigEngine.bat enable-portal-light-startup-performance -DWasPassword=password
Tuesday, January 5, 2010
Saturday, January 2, 2010
WPS 6.1.5 installation issue: CreateProcess failed ==> %1 is not a valid Win32 application
I was trying to install WPS 6.1.5 on my windows XP and it was failing with following error:
CreateProcess failed ==> %1 is not a valid Win32 application
after some troubleshooting i could resolve this. It was happening because i had two user variables defined in windows environment variables as follows:
TEMP = %USERPROFILE%\Local Settings\Temp
TMP = %USERPROFILE%\Local Settings\Temp
with this install.bat was having problems with directory name having spaces.
I tried changing it to TEMP = c:\mytemp
at this time i started getting
CreateProcess failed ==> %1 is not a valid Win32 application
later i realised that there are two system variables defined as well with similar name TEMP and TMP as follows:
TEMP = c:\Windows\TEMP
TMP = c:\Windows\TEMP
so, i removed the uservariables TEMP and TMP and tried the installer once again and it installed successfuly. :)
CreateProcess failed ==> %1 is not a valid Win32 application
after some troubleshooting i could resolve this. It was happening because i had two user variables defined in windows environment variables as follows:
TEMP = %USERPROFILE%\Local Settings\Temp
TMP = %USERPROFILE%\Local Settings\Temp
with this install.bat was having problems with directory name having spaces.
I tried changing it to TEMP = c:\mytemp
at this time i started getting
CreateProcess failed ==> %1 is not a valid Win32 application
later i realised that there are two system variables defined as well with similar name TEMP and TMP as follows:
TEMP = c:\Windows\TEMP
TMP = c:\Windows\TEMP
so, i removed the uservariables TEMP and TMP and tried the installer once again and it installed successfuly. :)
Thursday, December 17, 2009
Enabling SiteAnalyzer in WebSphere Portal
1.Edit wp_profile\PortalServer\config\SiteAnalyzerLogService.properties and add/change: -
SiteAnalyzerFileHandler.fileName=logs/$APPSERVER_NAME/sa.log
SiteAnalyzerPageLogger.isLogging=true
SiteAnalyzerPortletLogger.isLogging=true
SiteAnalyzerSessionLogger.isLogging=true
SiteAnalyzerJSRPortletLogger.isLogging=true
SiteAnalyzerUserManagementLogger.isLogging=true
SiteAnalyzerPortletActionLogger.isLogging=true
SiteAnalyzerApplicationActionLogger.isLogging=true
2.Push the updated properties into the portal configuration
1)Open a command prompt
2)type “cd \ibm\websphere\wp_profile\configengine”
3)type “ConfigEngine.bat update-properties”
3.Restart the portal.
SiteAnalyzerFileHandler.fileName=logs/$APPSERVER_NAME/sa.log
SiteAnalyzerPageLogger.isLogging=true
SiteAnalyzerPortletLogger.isLogging=true
SiteAnalyzerSessionLogger.isLogging=true
SiteAnalyzerJSRPortletLogger.isLogging=true
SiteAnalyzerUserManagementLogger.isLogging=true
SiteAnalyzerPortletActionLogger.isLogging=true
SiteAnalyzerApplicationActionLogger.isLogging=true
2.Push the updated properties into the portal configuration
1)Open a command prompt
2)type “cd \ibm\websphere\wp_profile\configengine”
3)type “ConfigEngine.bat update-properties”
3.Restart the portal.
Subscribe to:
Posts (Atom)