Archive for the ‘WebSphere Portal’ Category
WebSphere Portal 8 General Availability – Friday May 4
Download the gold release of IBM WebSphere Portal 8 on Friday May 4th. This is the estimated general availability for media downloads.
This includes the latest version of IBM Web Content Management and IBM Web Experience Factory.
Here’s the announcement letter:
http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS212-132#h2-pubx
This latest version improves manageability of content, delivery of content to mobile platforms, and increases integration of features into the portal core.
Thanks t0 Stuart McIntyre’s Portal2Portal blog I caught up on an announcement I overlooked.
Tip: Rational Application Developer & Portal Home Page
You might be using a development server where another team has implemented a page hierarchy. You know something is wrong when you try to run your portlet application on the server and the pages used by Rational to display the portlet aren’t available.
What happened? In all likelihood the original label named Home has been deleted. This isn’t a bad thing but Rational expects to find a page whose unique name was associated with that label. To fix the problem choose a location in the page hierarchy such as a top node in your custom hierarchy and create a sibling (or a child) and provide ibm.portal.Home as the unique name. This, of course, assumes you don’t already have a node with such a name. Furthermore, if you do have such a node, then there is another problem than the one this tip assumes.
Now, when you attempt to run your portlet application on the server, the tool can create a child of the predefined node and launch the page that displays your portlet.
Getting to Know the Browser: Working with Client Profile Information in Portlets
WebSphere Portal supports the integration of data from disparate systems in order to manage and deliver it to clients. How users experience this content continues to vary depending on the user’s browser. To assist in content delivery, WebSphere Portal provides an API named “CC/PP” that presents a profile of the user’s browser through a request attribute.
To work with this profile you will need to import two objects:
javax.ccpp.Attribute and javax.ccpp.Profile
As an example consider the following:
Profile clientProfile = (Profile) portletRequest.getAttribute(PortletRequest.CCPP_PROFILE);
// By getting an instance of a Profile named clientProfile we can then extract
// one of the members of the profile such as manufacturer of the browser, Vendor.
String vendor null;
if (clientProfile != null) {
Attribute attribute = clientProfile.getAttribute(“Vendor”);
if (attribute != null) {
vendor = attribute.toString();
}
}
// Now that you know the Vendor you can do something interesting.
What are some other members of the profile?
The browser name, version, markup supported, style sheet support, etc.
You may ask why we shouldn’t handle this in JavaScript? One reason I can think of right away is mobile access.
The volume of information to push to the mobile browser can be significantly reduced by determining the markup (JSP) before rendering the page for the client.
Taking Notez - Island Pond Consulting 