IBM WEBSPHERE/ JSR 168, JSR 286,JSR 301 PORTAL/PORTLET PROGRAMMING/Administration in INDIA, USA & CANADA
(Training will be given online- Voice and Video, For in-class room sessions ** based on availability and Courses & number of students).
Course Fee and Deliverance charges: Every Student who registers before MARCH 31st - 2011 can get the First Three classes for free to evaluate the training session.
(if satisfied you can continue by paying for the rest of the classes to complete the course).
Pls Note: The Free Classes would be every 1st weekend of every month. So do register prior to that
Course Information
Topics :
1.Exploring WebSphere Portal --- FREE TO EVALUATE
2.JSR 168, 286 and 301 Portlet Specifications --- FREE TO EVALUATE
3.What, Why and Hows of Portlet Programming --- FREE TO EVALUATE
4.Creating and Testing Portlets
5.Working with the API Core Objects
6.Leveraging Tag Libraries
7.Processing Portlet Input
8.Customizing Portlet Behavior
9.Tying Portlets Together: Event Processing
10.Building JavaServer Faces Portlets
11.Creating Ajax Portlets
12.Implementing Web 2.0 portlets
13.Implementing Personalization
14.Creating a Portal Brand
15.Web Content Management
16.Support Activities & How to handle Challenges in Production and Post Production environments
1. Our asynchronous IO is blocked based on analysis of the thread dumps. The recommendation is to disable the AIO permanently, using mechanism 1 of the attached link:
Superperformance Stocks
-How I Made 2,000,000 in the Stock Market
-How Charts Can Help You in the Stock Market
-Reminiscences of a Stock Operator
-Market Wizards
-The New Market Wizards
-Stock Market Wizards
-How to Trade in Stocks
-Stock Market Blueprints
-The Battle for Investment Survival
* Servlets and portlets are web based components that utilize Java for their implementation
* Portlets are managed by a portlet container similar to a servlet container
* Both of these components generate content, which can be static or dynamic
* Both portlets and servlets have a lifecycle that is controlled by the container
* The client/server model is used for both servlets and portlets
* The packaging and deployment are essentially the same
* The manner in which the classes are loaded and the class loaders that perform the work are also the same
* Lifecycle management is similar
* The Request and Response semantics are also similar
Here are some differences:
* Servlets can provide complete web pages, whereas portlets only provide fragments. These fragments are then aggregated to form a complete web page by the portal
* Portlets aren’t allowed to generated HTML code that contains tags such as base, body, frame, frameset, head, html, or title. The iframe tag can be used with caution.
* The user cannot access a portlet directly using a URL in the way that a servlet is accessed. Instead, the URL points to the page containing all of the portlets on one page
* Communication between the web client and the portlets is performed through the portal
* Portlets can be provided with buttons or controls to manipulate the portlets’ window states or portlet modes
* Multiple instances of a single portlet can be placed onto the same page
* Portlets support persistent configuration and customization
* Portlets also support user profile information
* Portlets support two scopes within the session; application scope and portlet scope
There are several things that servlets are allowed to do, but portlets aren’t. These include the following:
* Portlet aren’t allowed to set the character set encoding of the response
* Portlet also aren’t allowed to set the HTTP headers on the response
* Portlet cannot manipulate the URL of the client request to the portal
JSR 168 implementation on WPS,
life cycle of portlet,
portlet API
Request and Response(Action and Render phases), Advanced url generation,
user attributes(PUMA),
Themes and Skins(various jsp files),
inter portlet communication,
packaging of portlets and deployment tool,
portlet preferences,
portlet service,
portlet session with portlet scope and application scope,still more...depends on your implmentation. hope this helps.
What is Portal:
software architecture where a server-side component is used to aggregate content generated by small subcomponents called portlets.
A portal is a Web application that presents content from multiple sources. Portlets are Web components that generate content fragments (typically pieces of markup such as HTML, XML, or WML). By aggregating the content generated by many portlets, a portal is able to generate a single user interface which integrates many disparate sources.
Portlet Specification is built on top of the
Java Servlet Specification 2.3 and
Java Server Pages version 1.2
The Portlet, PortletConfig, PortletRequest, and PortletResponse interfaces
What is a Portlet? Explain its capabilities.
Portlets are pluggable UI components which are managed, displayed using a web portal.
Markup code fragments are produced by the portlets which are aggregated into a portal page.
A portlet resembles an application that is web based and is hosted in a portal. Email, discussion forums, news, blogs, weather reports are some of the examples of portlets.
The core implementation of the portal is UI, hosted by a Portal server. The HTTP requests, HTML responses, and returning appropriate portal pages are handled by the Portal UI. Enterprise Web application also can be handled by the Portal Server.
The portal architecture has the following: AISCCAR
Automaton Server, Image Server, Search Server, Collaboration Server, Content Server, Authentication Server, Remote Server,
Automaton Server: This server performs the management of job scheduling and implementation of a portal. It accesses all remote crawlers and profile services retrieved and stored from a remote database.
Image Server: This server hosts images and other web page content used by web services and a portal. With this configuration, large static files are to be sent directly to the browser without portal server impacts.
Search Server: This server indexes and searches all the information, applications, communities, documents, web sites through portal.
Collaboration Server: Web content publication and management for portals and web applications are supported by this server. Its functionality can be accessed by a remote web services through Enterprise Web Development kit.
Content Server: Publication and management of web content for portals and web applications along with form based publishing, branding, templates, content expiration is allowed by this server.
Authentication Server: This server handles the portal authentication for users and remote services can be accessed through EDK.
Remote Servers: Web services written using the EDK are hosted by remote servers. The servers can be in different countries, on different platforms and domains.
What is PortletSession interface?
User identification across many requests and transient information storage about the user is processed by PortletSession interace.
One PortletSession is created per portlet application per client.
The PortletSession interface provides a way to identify a user across more than one request and to store transient information about that user.
The storing of information is defined in two scopes- APPLICATION_SCOPE and PORTLET_SCOPE.
APPLICATION_SCOPE: All the objects in the session are available to all portlets,servlets, JSPs of the same portlet application, by using APPLICATION_SCOPE.
PORTLET_SCOPE: All the objects in the session are available to the portlet during the requests for the same portlet window. The attributes persisted in the PORTLET_SCOPE are not protected from other web components.
What is PortletContext interface?
The portlet view of the portlet container is defined by PortletContext. It allows the availability of resources to the portlet. Using this context, the portlet log can be accessed and URL references to resources can be obtained. There is always only one context per portlet application per JVM.
wp_profile_root/bin
startServer.bat WebSphere_Portal
To verify that the WebSphere Portal
http://portal61.ibmdemo.com:10040/wps/portal
Login to WAS by typing the below url :
ohttp://portal61.ibmdemo.com:10027/ibm/console
JSR 286 IMprovements
major enhancements of JSR-286 include inter-portlet communication, WSRP 2.0 alignment, support for Ajax, and portlet filters and listeners.
Problem: Error occurs when exporting files from various portlets
When you export files from the Manage Pages, Template Library or Policy administrative portlets, you may receive one of the error messages below if using Internet Explorer:
WebSphere Portal 6.1, the instance of the IBM Dojo Toolkit is based on version 1.1.1
Saturday, October 24, 2009
Date: 10/24/2009
Problem: in RAD 7.5
"IWAL0071E No corresponding public render parameter definition"
Resolution: the identifier block is missing the identifier element in the Public-render-parameter section in Portlet.xml
check the portlet.xml for any missing identifier sections.
Problem: class file has wrong version 50.0, should be 49.0
solution: downgrade your JDK to 1.5
Below are a list of some of the version numbers and their corresponding Java runtimes:
Version 50.0 = Java 1.6.x
Version 49.0 = Java 1.5.x
Version 48.0 = Java 1.4.x
experiencing issue of out of memory where you run out of permgen space especially when there is HA Manager DCS events are taking place. **********Please Note this might be a case by case issue,for exact problem with your case , please contact IBM support by opening a PR using your client account ID***********************
hope this might surely give some insight on the problem
CoordinatorCo W HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 165 seconds. SystemOut O java.lang.OutOfMemoryError: PermGen space
Apply all the fixpacks available for the Portal server
The following are IBM recommendations:
1# Configure Default Thread Pool size to help DRS traffic. Based on IBM WebSphere Portal 6101 performance tunning guide. How-To Set: Portal Server->Thread Pools ->DefaultPool=150/150 and disable isGrowable (default=5/20 and isGrowable is set to true)
2#.Remove the following JVM property based on suggestion from WAS L2 team. Currently set to true -Dcom.ibm.ws.cache.CacheConfig.propogateInvalidationsNotShared=true Remove or set it -Dcom.ibm.ws.cache.CacheConfig.propogateInvalidationsNotShared=false
3#. Change the value of the IBM_CS_DATASTACK_MEG custom property to 100MB as suggested by WASCET L2 team. 1. In the administrative console, click Servers > Core groups > Core group settings > core_group_name. 2. Under Additional Properties, click Custom Properties. 3. Change the value specified for the IBM_CS_DATASTACK_MEG custom property.
If the IBM_CS_DATASTACK_MEG property already exists, click on the property name and, in the Value field, specify the maximum amount of memory that you want to let the core group transport allocate for buffering incoming messages.If this property does not already exist, click New and then: a. In the Name field, specify IBM_CS_DATASTACK_MEG. b. In the Value field, specify the maximum amount of memory you want to let the core group transport allocate for buffering incoming messages. 4. Click OK, and then click Save to save your changes.
4#. Change the size of the Transport Buffer. The maximum amount of heap memory that is specified for the IBM_CS_DATASTACK_MEG custom property should be less than or equal to the size of the transport buffer. a. In the administrative console, click Servers > Application servers > server_name, and then, under Additional Properties, click Core group service. b. In the Transport buffer size field, specify, in megabytes the size of the transport buffer. Set this to 200MB. Based on IBM WebSphere Portal 6101 performance tunning guide. c. Click OK. d. Repeat the previous three steps for all of the application servers that are members of this core group. Specify the same transport buffer size for all of these core group members. e. Click System administration > Node agents > node_agent_name, and then under Additional properties, click Core group service. f. In the Transport buffer size field, specify, in 200 megabytes the size of the transport buffer. g. Click OK. h. Repeat the previous three steps for all of the node agents that are members of this core group. i. Click System administration > Deployment Manager, and then under Additional properties, click Core group service. j. In the Transport buffer size field, specify, in 200 megabytes the size of the transport buffer. k. Click Review to review your changes. l. Select Synchronize changes with Nodes, and then click Save to save your changes. Restart all members of the core group.
6# Apply all the recommended fixes on top of 6102. You can find those fixes on Fix central link.
6.1 Go to fix central link : - http://www-933.ibm.com/support/fixcentral/ 6.2 Select WebSphere under Product Group pull down menu. 6.3 Select WebSphere Portal under Product 6.4 Select 6102 Installed Version 6.5 Select All in OS menu. 6.6 Click continue. 6.7 Select Recommended radio button and click continue. This will provide all the recommended ifixes to be applied on top of 6102 for Portal and Web Content Management
few more suggestions,
1. Our asynchronous IO is blocked based on analysis of the thread dumps. The recommendation is to disable the AIO permanently, using mechanism 1 of the attached link:
