40 replies
by write2munish
If you offer more than a few portlets within your portal, then you need to think about how people will navigate between and among them. While it is tempting to just let users click the back button until they make it back to the portlet page, this is a highly inefficient method. When you have complete control over the development of the application that the portlet accesses, you should include breadcrumb navigation trails, links to the main sections of the portal site, and links to related portlets.Information architecture has to be designed for a portal and its application just as in the development of any other Web application. A good navigation scheme within a portal should allow the user to answer each of the following seven questions from anywhere within the portal or its applications.
Seven questions to determine a good navigation scheme:
1. Am I still in the portal?
2. How do I get to the main page of the portal?
3. What are the major areas of this portal?
4. Where am I in relation to the main page of the portal and the other applications I have visited?
5. Where can I go from here?
6. How can I go back to where I came from?
7. When I leave this screen, will I be able to get back to it?
Filed in:
WPS
by write2munish
Portlets are not the solution to every design challenge. Here are a few things that portlets do not do well:* Complex user interfaces do not translate well to portlets. The markup languages like HTML and WML simply cannot describe some interfaces. Try to imagine implementing an integrated development environment (IDE) like Eclipse or Visual Basic in HTML and you'll have the idea. Native applications and Java applications work better for this. (If you have a complex user interface and still want to take advantage of the benefits of portlets, WebSphere Portal does support Struts, which can be very helpful.)
* User interfaces with data that must be constantly updated are also not portlet material. When you update one portlet, all portlets on the entire page must be re-drawn, so it is generally not a good practice to have your portlets automatically reload themselves with new data. On the other hand, you can have "refresh" option in the portlet so your users can choose when to reload the page. You cannot be sure how often users will choose to refresh the page, so if your data must not be out-of-date, use a native application or a Java application instead of a Web application.
* Highly interactive user interfaces do not translate well to Web applications in general, or portlets in particular. If you want your interface to change automatically when a user takes some action, like selecting an entry in a drop-down list, you can either submit the form and reload the entire page (annoying), or use a scripting language to re-draw the portlet (very difficult). If you use a scripting language, you will need to make sure it works for all of the devices you want to support, and you will also need to make sure your portlet still works if scripts are disabled by some of your users. For mobile devices, you will probably need to have alternate JSP pages that do not use scripts. Native applications or Java applications are easier to make highly interactive than are Web applications.
* Portlets need to live "within their box." Be careful if you have a link in a portlet that takes you to a Web page outside of the portal server environment, because it is difficult to get back to the portal after that. Frames are not allowed (Internal frames are allowed, but only Microsoft Internet Explorer users can see them). Pop-up windows and scripts usually cannot be used for mobile devices. If you can't make your application fit into the portal framework, don't make it into a poorly-behaved portlet.
* If you will want to provide services to other applications, consider writing a Web service first. Once you implement a Web service, you can write a portlet to use it, and you can publish the Web service to share it with other applications. The stock portlet is a good example: the stock quote service should be a Web service that the stock quote portlet and other applications can use. In this case, you might also write a program that automatically sends users a text pager message when a stock reaches a certain price.
* If the company does not have a portal server yet, and does not plan to invest in one immediately, one can go ahead and implement the application as a servlet using JSP pages for the output. One can always convert it to a portlet later.
Filed in:
WPS
by write2munish
Last time, I blogged about when not to use portals. This time, I am blogging about when portlets make sense. So,now if your goal is to bring together your Web applications and information into one convenient place, portlets are the obvious choice. If your development goals are somewhat different, consider these other portlet and portal server features that you might want to take advantage of:* Portlets can be extended to work on many client devices. The users can move from computer to computer, and mobile device to mobile device, and still use the infomation and applications they need.
* Portlets allow you to easily customize their content for different user groups, and individual users can rearrange and tailor them to their needs.
* One can make the portlets have a unified look, and change their appearance quickly, using Cascading Style Sheets along with themes and skins that the portal server provides. You can create your own themes and skins as well, to better reflect your company's image and style.
* Portlets can be published as Web services, so that companies outside of your portal server's environment can easily write programs to use them.
* The IBM WPS provides excellent support for internationalization, beyond what the Web Application server provides. It is straightforward to develop portlets that will display correctly for international users, even in double-byte or bidirectional languages like Chinese and Arabic.
* Portlets help divide complex applications into tasks: in general, one group of closely related tasks equals one portlet. WPS's administration portlets are a good example: like the administration tasks can be broken down into categories (Portlets, Portal Settings, etc.), groups of related tasks (Manage Users, Manage User Groups), and single tasks (Search for users, Create new user).
* Portlets make it easy to add features to your applications later. If the new feature is large, one can create a new portlet. For small updates, you can update the existing portlets without losing users' individual preferences.
* Portlets, like other Web applications, play well with firewalls. They use standard Web protocols to receive and display information.
* You only need to install and configure portlets once for all of your users, which is much easier than working with stand-alone applications on each computer. This logic applies to the other Web applications as well.
* The portal server works with the Web application server to provide security, installation support, reliability, and availability for many users, so you don't need to spend a large part of your development effort working on these features.
* Once you do invest in a portal server, you may find its advanced features useful: content management, transcoding, voice support, and offline browsing, among others, useful for integrating into your application
Filed in:
WPS
by write2munish
Although there is no automated method to move Portal applications from one environment to another, there are two options:* Completely replace the old release with a new release. The drawbacks of this option is that any data that was customized by the user is lost. While this option works, it is not the recommended way.
* Use the XMLAccess tool to load incremental or differential release
The XML configuration interface
The XML configuration interface is more commonly referred to as the XMLAccess tool, because xmlaccess is the command that is executed. The tool provides a batch processing interface for Portal configuration updates and allows you to export an entire Portal configuration or parts of a configuration. For example, you can process and export specific pages to an XML file. You can then re-create the exported configuration from a file on another Portal.
While XMLAccess is as simplified bulk transfer utility, there is no magic button that automatically moves all the components of your Portal to the next environment. The XMLAccess tool is best for the initial loading of Portal application and for doing incremental releases. However, it is increasingly being used as a command line Portal administration tool.
I will talk more about XMLAccess next time.
Filed in:
WPS
by write2munish
Last time, I talked about the Release process for WPS using XMLAccess as the tool, here. Now, I going for more details on the XMLAccess to help gain an indepth understanding of the tool.Why use XMLAccess
The major benefit of XMLAccess is its ability to update pages and
portlets without losing user customization. If you perform your updates
via XMLAccess, any user customization to a page or a portlet is
retained because the object IDs are retained.For example, the organization may have deployed a stock portlet
that the user can customize to monitor certain stocks by adding just
those stocks to the portlet. If you update this portlet, you do not
want the user customization to be lost. The XMLAccess tool allows you
to maintain the user?s customization. When exporting and importing via
the XMLAccess tool, the object IDs of the portlet application are
maintained. When a user customizes a portlet or a page, these
customizations are stored in your back-end database. All these
customizations are stored relative to the actual portlet application.
The key that ties all of these customized versions of a portlet or page
back to its parent is the object ID.How XMLAccess works
The XMLAccess command line client is a small separate program that
connects to the server using an HTTP connection, which allows you to
configure the Portal remotely. The XMLAccess command is located in the
wp root/bin directory of the Portal server and is xmlaccess.bat (on
Windows) or xmlaccess.sh.The syntax for the command is as follows:
xmlaccess -user wpsadmin -pwd itso -in file.xml -out result.xml -url myhost:9082/wps/config
In the command line, use the following file names:
* file.xml: The name of a file containing the XML request (configuration export or update) that should be processed.
* result.xml: The name of the result file containing the XML output
(configuration export). You can later use that file to re-import the
exported configuration.* url: The URL to access the Portal configuration servlet. This URL
consists of the Portal host name, the base Uniform Resource Identifier
for the Portal, as specified during installation (for example /wps),
and the servlet extension /config.You can use the XMLAccess tool to transfer a complete configuration, including:
* Portlets
* Access Control List
* Portal Web application configurations (portlet applications)
* Portal skin definitions
* Portal theme definitions
* Portal portlet configurations
* Portal site map (pages, labels, and links)
* Portal URL mappingsWith the XMLAccess tool, you can also:
* Load the WebSphere
Portal default portlets configuration during the initial install and
transfer parts of Portal configuration.
* Create and modify existing Portal artifacts incremental releases.
*
Delete Portal artifacts. However, you must manually add delete commands
to the input file. Keep in mind, although the XMLAccess tool is a bulk
transfer utility, the command does not know history. It only knows the
Portal configuration at specific point in time.
Filed in:
WPS
by write2munish
To create more complex portlet applications, using frameworks can save
a lot of development effort and assure that these portlet applications
are well-designed and maintainable. WebSphere Portal supports three
different frameworks: Struts, Java Server Faces, and the JSF Widget
Library.
Struts
Struts is one of the oldest Web
development frameworks, and it has a very large developer community and
very good tools support. Struts is an open source project at Apache
[Struts] and was created to provide servlet and JSP programmers with a
multi-page, Model-View-Controller (MVC) framework. Because Struts was
developed for servlets, it does not work out-of-the-box with portlets;
portlets have the MVC patterns strictly built into the interface, with
an action and a render phase. In addition, the portlet and servlet
request/response are different and must be adapted. WebSphere Portal
provides a special version of the Struts V1.1 library that was modified
to support JSR 168 portlets on WebSphere Portal.
Java Server Faces (JSF)
Java Server Faces is a UI
framework for Java Web applications which was standardized through the
Java Community Process. Because it is quite new, it took portlets into
account and can work with portlets and servlets out-of-the-box. In
addition to the UI components, JSF also provides infrastructure support
for state handling, validation, and event processing for these
components. It is a very powerful and flexible framework that works
well with portlets.
WebSphere Portal supports JSF by including
the JSF library so that themes and skins can utilize this UI framework.
Rational Application Developer provides tooling support. You can create
JSF-based portlets using a wizard, and you can use additional JSF UI
widgets that portlets might use.
JSF Widget Library (JWL)
JWL
is provided by Rational Application Developer and enables portal and
portlet programmers to use an additional widgets based on JSF. A
noteworthy feature of this library is that these widgets have client
capabilities. The widgets can perform processing on the client in order
to update their views, which saves round trips to the server,
dramatically improving the user experience because the response time is
shortened by orders of magnitude. You can deploy WebSphere Portal
portlets which use these widgets just like any other portlets.
by ananomouse1
I appreciate the links to the mentioned frameworks also.
by alind
by write2munish
There are several use cases when a portlet needs to obtain the object
ID used to uniquely identify a portlet or a page. For example, the
object ID of a page definition is required for a portlet to launch a
dynamic instance of that page. You can use the lookup() method of the
JNDI Context class to obtain the object ID for a portlet or a page,
passing the unique name of the page or portlet. As an alternative for
portlets, you can obtain the object ID by using JNDI lookup() and
passing a combination of the portlet application ID and the portlet
name.
? For JSR 168 compliant portlets, the portlet application ID is the value of the ID attribute of the
element in the portlet.xml. However, this attribute is not required by
the Java Portlet Specification. If the ID attribute is not set, the
portlet WAR file name is used as the portlet application ID.
? For IBM portlets, the portlet application ID is the UID attribute of the element. This attribute is required.
The following example shows both ways to find an object ID.
************************************************************
// initialization
Context ctx = new InitialContext();
// portal:uniquename prefix is required for unique name lookup
Name uniqueName = new CompositeName("portal:uniquename");
// portal:config/ prefix required for portlet definition lookup
Name portletName = new CompositeName("portal:config/portletdefinition");
// the unique name assigned to the page is example.org.page
uniqueName.add(org.example.page);
ObjectID oidForName = (ObjectID) ctx.lookup(uniqueName);
// appID and portletName have already been set programmatically
portletName.add(appID);
portletName.add(portletName);
ObjectID portletDefOID = (ObjectID) ctx.lookup(portletName);
************************************************************
The
Name used for the lookup() method is created from a CompositeName,
which is prepopulated with the required portal prefixes enclosed in
quotes. This technique is used to avoid having to escape special
characters in the prefix.
by write2munish
Portal Search has undergone significant changes in the WPS V5.1
Search Portlets
There is a new Portal Search Box and Search Center portlets that presents a search box on every portal page. When the users enter a search string and click Search, the portal takes them to the new Search Center portlet and applies the search criteria and shows them the search results.
Catalog
Another, new development is the Portal Search can be assigned to external/internal web sites. Portal Search allows crawling and indexing portal pages. The crawler can fetch and index all pages with portlets to which it has access rights. This way you can enable users to search those pages. You can define which portlets on which pages you want to make searchable. You can do this by granting the required access permissions to the crawler user.
Security
Another feature is limiting the search results based on the user privileges. Each individual search collection is now a separate portal resource. You can give users access permissions on them and thereby make different search sources available to different users or user groups. This applies to all search collections. For example, in the Search Center users see only the tabs for those search collections to which they have access.
Some of the drawbacks, I encoutered is the lack of availability of search features for anonymous users. Also, settings up the search with results in mulitple languages is very tedious. The whole crawlong and cataloging of the pages and documents takes too long.
by write2munish
IBM is planning to release WPS 6 sometime about in 3rd Quarter 2006. I recently
had a chance to check out some of the new features, WPS 6 will be getting
shipped with.
- Updated Themes and Skins, Roll over menus
-
Adding
portlets have become easy. Now, one can easily drag and drop the same on to the
page -
Document Manager look and feel have been updated. Out goes the drab
look of the earlier Document Manager Portlet -
The Portlet search has been
improved and ability to integrate better with external search engines - After
the BowStreet acquisition by IBM, the same have been integrated in WPS. So, now
you have the WebSphere Portal Factory and Portal Application Templates to jump
start your portlet development - The WCM component has also undergone the
look and feel change, with simplified administration and the same has been
integrated with portal administration -
Portal Personalization has been
improved, now the personalization rules can be applied to both portlets and
portal pages -
Another new feature is the ability to bind the WPS with
multiple LDAP's. This will go a long way in helping the user management. -
Improvements have been made in terms of scalability and performance of portal
sites
Must say, exciting times are ahead for the WPS folks. I am eagerly
waiting for the release of WPS 6.
by write2munish
The following code snippet shows how to render a breadcrumb
trail that shows the current selection path.
|
<%@ taglib <%@ page <%@ page <%@ page <%@ page <%@ page <%@ page <%@ page <%@ page <%@ page
<% try{ Context if (home NavigationSelectionModel model = for { if (i.hasNext()) { %>
<a <% } { %> <% } } } } catch (ModelException mx) { %>
<p><span
<% } catch (NamingException nx) { %>
<p><span
<% } %> |
The example uses a JNDI lookup to obtain the navigation
selection model. The model is then iterated and for each node a title is
produced using the <portal:title/> tag. Until the last node is reached
the <portal:navigationUrl/> tag is used to generate links to the
referenced pages. The code can be put in
the WebSphere Portal default theme (Default.jsp)
by write2munish
| Guideline | Effect on functionality | Effect on performance |
|---|---|---|
| Remove Show tools icon from the toolbar | Prevents users from displaying icons on pages and portlets used to arrange or remove content on the page. |
High impact on pathlength required to generate the page |
| Remove enrollment icon from the toolbar | Prevents new visitors to the site from creating a new account for themselves. | High impact on pathlength required to generate the page |
| Remove self care icon from the toolbar | Prevents users from updating account information. | High impact on pathlength required to generate the page |
| Remove AdminLinkBarInclude.jsp | Removes context-sensitive links that allow authorized users to create a new page, edit the current page, or assign permissions to the current page. |
High impact on pathlength required to generate the page |
| Remove <portal:favoritesLoop/> and supporting code | Removes the ability for users to bookmark pages in the portal for quick retrievability | High impact on pathlength required to generate the page |
| Shrink lines of text to remove white space | With some editors, white space might be used to aid in readability during theme development | Low impact on bandwidth required to transmit the page. |
| Change all HTML comments to JSP comments | None | Low impact on bandwidth required to transmit the page. |
Filed in: WPS
by write2munish
For any new technology, the first thing is to build a HelloWorld kind of Application. I found a good tuturial on helping you build your first Ajax application here.
Filed in:
J2EE
by write2munish
Adobe labs has released an Ajax framework. The framework gives javascript libraries that will help you get started on building Ajax enabled application. Examples of how to use the Spry libraries are also provided. Check out the framework here.
Filed in:
J2EE
by write2munish
Sometime, I had talked about the WebSphere's Dyna cache feature here. There is a new article that details about to design your application to make use of the WAS Dyna cache feature from day one. Check out the article here.
Filed in:
WAS
by write2munish
The XFire team has released version 1.1, an open source Java SOAP framework with support for Web services standards, Spring, JBI and pluggable bindings.New features in this release include:
MTOM attachment support
WS-Security support
Improved WSDL code generator
Filed in:
J2EE
by write2munish
With Apache Pluto, Java? developers have a freely available tool for testing whether their portlets comply with the JSR 168 Portlet Specification. This article takes you thru the steps of, install Pluto and build, compile, package, and deploy a simple portlet to Pluto to test it for JSR 168 compliance. You'll also get a hint of what's in store for the next version of the Portlet Specification.
Filed in:
WPS
by write2munish
This guide describes a comprehensive procedure for installing, configuring, and building an IBM? WebSphere? Portal V5.1 cluster.
Filed in:
WPS
by write2munish
Learn how to exploit WebSphere? Portal V5.1 key capabilities in an IP-TV (Television over Internet Protocol) environment. You see how to configure a portal for heterogeneous Digital Television (DTV) services to enable a central "home dashboard" for communication and entertainment on a TV. Check out the article here.
Filed in:
WPS
by write2munish
WebSphere Portal supports the use of tags from the JSP Standard Tag Library (JSTL). Portal themes, skins, and screens can retrieve translated text by using the fmt tags from the JSP Standard Tag Library (JSTL). This method is preferred over using the tag from the engine tag library, which is deprecated. The following tags from the JSTL tag library are used to retrieve translated text:
<fmt:setBundle/> - specifies the resource bundle to use.
<fmt:message/> - specifies the key to retrieve from the bundle and writes the value to output.The underlying getLocales() method of the HTTPServletRequest is overwritten to return the language preference in the user profile, if available.
Support for the JSTL tag library is provided by WebSphere Portal. To use the JSTL tags, the following directive must be provided in the JSP.
<%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %>
The following example shows how the HTML help link in the toolbar can be created using the JSTL tags for the link text.
<%-- help button --%>
<td class="wpsToolBar" valign="middle" align="<%=bidiAlignRight%>" nowrap="nowrap">
<a class="wpsToolBarLink" href='<%= wpsDocURL %>/InfoCenter/help/index.html' target="...
<fmt:setBundle baseName="nls.engine">
<fmt:message key="link.help"/>
</fmt:setBundle>
</a>
</td>Test this code by changing your language preference in the portal user profile and logging back in to the portal.
Filed in: WPS
by write2munish
As an application developer, you have all the liberty to log anything. But are there any guidelines on what is the bare minimum an application should log?Things like Method entry/exit, method parameters, info logging in the algorithm, exception logs, Transaction time period and so on.
One can log anything, but any guidelines/experience which says the application should log minimum of these things.
Join the debate here
Filed in:
J2EE
by write2munish
When configuring WPS for personalization, there are 3 options:Simple filtering A site displays content based on predefined groups of site visitors. For example, if a site visitor is in the Human Resources department, the site provides access to URLs containing Human Resources policy manuals.
Rules engines
In a rules based system, the site owner defines a set of business rules which determine what category of content is shown when a certain profile type visits the site. An example would be: Display all four wheel drive SUVs to visitors in the northeast in the 21 to 35 age group.
This approach has the advantage of driving the site's behavior with the business objectives of the site owner. The site owner is usually the owner of a marketing campaign or some other business manager.Collaborative filtering
A site visitor rates a selection of products, explicitly or implicitly. Those ratings are compared with the ratings offered by other visitors. Software algorithms detect similarities. For example, a visitor receives book recommendations based on the similar purchases of others.
Filed in:
WPS
by write2munish
I have always found it difficult to keep track of the RAD tools and where are they supposed to be used. Today, I am listing down the RAD Tool options for Design and construction phase.Design and construction tools
IBM Rational provides tools for architecture, design modeling, construction, model-driven development, architected rapid application development (RAD), component testing and runtime analysis activities. These tools help developers maximize their productivity when building business applications, software products and systems, and embedded systems and devices.
- IBM Rational Software Architect: A design and construction tool for software architects and senior developers creating applications for the Java platform or in C++ that leverages model-driven development with the UML and unifies all aspects of software application architecture
- IBM Rational Software Modeler: A UML-based visual modeling and design tool for architects, system analysts, and designers that need to ensure that their specifications, architecture, and designs are clearly defined and communicated with their stakeholders
- IBM Rational Web Developer for WebSphere Software: Build, test and deploy Web, Web services and Java applications with an IDE that is easy to learn and use.
- IBM Rational Application Developer for WebSphere Software: Quickly design, develop, analyze, test, profile and deploy Web, Web services, Java, J2EE and Portal applications with a comprehensive IDE.
- IBM Rational Rose Technical Developer: Supports the most advanced modeling constructs, including model execution and fully executable code generation, resulting in the highest levels of productivity.
Hopefully, it helps in selecting the right tools for the right work.
Filed in:
IBM
by write2munish
This compilation of tips and guidelines from services, development, and support personnel about IBM? Workplace Web Content Management? is based on daily product experience including real customer engagements. This information includes selected topics and applies to version 5.1.0.x.; other versions might have different best practices. If you are currently involved in or just considering implementing a Workplace Web Content Management system, you can use it to help guide your work. You need a basic understanding of the Web Content Management product to understand the topics discussed.
Filed in:
WPS
by write2munish
Continuing my previous post which detailed on what Rational Tools are available to build and construct, here is the list of the Tools from Rational used for Software Testing.Testing tools enable running quality assurance on software products, testing for code consistency, quality, functionality and performance.
- IBM Rational Manual Tester: A manual test authoring and execution solution employing principles of automation, organization and reuse to innovate a commonly used testing practice.
- IBM Rational Functional Tester: An advanced, automated functional and regression testing tool for testers and GUI developers who need fine-grained control and flexibility for their testing of Java, .NET and Web-based applications.
- IBM Rational Performance Tester: A performance test creation, execution and analysis tool for teams validating the scalability and reliability of their Web-based applications before deployment.
- IBM Rational PurifyPlus allows developers to create faster, more reliable J2EE and J2SE code. It provides host-based memory profiling, performance profiling, and code coverage analysis.
- IBM Rational Test RealTime provides host-based memory profiling, performance profiling, and code coverage analysis for the J2SE/J2ME developer, plus adds runtime tracing, and does so for cross-platform development efforts. Rational Test RealTime also has an integration with JUnit to extend the value of the Java industry's popular unit testing tool to the J2ME and embedded marketplace.
Filed in:
IBM
by write2munish
Liferay Portal 4.0.0 has been released, with fine-grained permissioning, support for Websphere 6, and Weblogic 8.x, Alfresco integration, JSR-170 support, full-page caching, and more. It includes many bundled portlets and themes, and can be deployed on most application server/database combinations, including deployment in servlet containers (as opposed to a full application server).Liferay also supports single-signon and user customization.
Filed in:
Portals
by write2munish
You have built a Java Application. Now, as the application usage increases, the application needs to be scaled up. The only way to go is scale up (horizontal or vertical). Now the problem is that the application was never built to run in multiple JVM?s. There is no data synchronization, failover, session replication, distributed cache mechanism built in.This is the need that the following products intend to fulfill.
? GemStone
Filed in:
J2EE
by write2munish
I was looking at products for scaling up an existing client/server kinda of application. I am posting here my findings on Terracotta.TerraCotta
Allows the applications to be clustered to run on multiple JVM?s without changing source code and to get linear scalability and total fault tolerance. Terracotta injects clustering and caching into off-the-shelf JVMs.
How it works?
The technical approach that Terracotta uses is client/server, relies on byte code manipulation to track object changes, uses XML descriptors to define data synchronization points, and communicates object deltas. Theoretically, it should have efficiency advantages if you have a very large object graph and you frequently access that graph but only change small bits of information within it.
Technical Architecture
At the heart of the Terracotta architecture sits the Terracotta Server. Terracotta provides a set of infrastructure software installed on an inexpensive server. Multiple Terracotta Servers can be clustered together to make a high-availability hub shared by many application servers, even across dispersed geographies.
The server's primary job is to replicate state across application servers in the data center, manage connections from various clustered JVMs, and ensure coherence and consistency of application data. A single Terracotta server can provide clustering services for all of the Terracotta modules in use in the Data Center.
Existing servers within the data center need only have the Terracotta libraries installed on them. Terracotta libraries provide various 'modules' which communicate with the Terracotta server and enable a variety of clustering services.Terracotta Fail over
The Terracotta Server can operate with a 'hot back-up' to meet availability requirements. In the event of a failure in the active Terracotta Server, the back-up will automatically take over transactions from various clustering clients and ensure that the replicated state is maintained. No state or cache information is lost in any application node. And, failover takes only seconds. Connected clients will notice only a brief pause during the failover process.
Advantages
? API Less ? One can simply plug in Terracotta (install the libraries), configure (edit appropriate configuration files), and play (start Terracotta and run the application)
? Provides a management console to provide metrics about connected clients, object/content cachesDisadvantages
? Requires an external server
? Supports session replication for WebLogic Server 8.1 and Tomcat 5.0
? Terracotta server required a hot backup for 24X7 applications
Filed in:
J2EE
by write2munish
This tutorial shows how to develop a WebSphere portlet application for IBM? WebSphere? Portal V5.1 using Eclipse and WebSphere Portlet Factory. It also shows you, how to use WebSphere Portlet Factory to develop a portlet that retrieves and displays data from a database.
Filed in:
WPS
by write2munish
DB2 9 introduces pureXML? support, which means that XML data is stored and queried in its inherent hierarchical format. To query XML data, DB2 offers two languages, SQL/XML and XQuery. You can use XQuery and SQL separately, but you can also use XQuery embedded in SQL and vice versa. This gives you a lot of flexibility and options for querying your XML data.Check out more here.
Filed in:
IBM
by write2munish
This collection of best practices, tips, and suggestions from the IBM? WebSphere? Portlet Factory development team is for developers who are either currently using or are expecting to use WebSphere Portlet Factory.Developers with any level of experience can use Portlet Factory to quickly create complex portlets and integrate them with their WebSphere Portal based portals. As with the use of any tool, there are good practices for architectural, application structure, and solid implementation. This document provides guidance for those practices based on many person-years of experience. It also includes a section on selecting Builders to help you navigate the Builder palette.
Filed in:
WPS
by write2munish
Design your processes and set up your environments for developing, building, and deploying your portal. Learn how to control the source code and build components, ways to manage continuous integration and deployment to test environments, and how to deploy production release packages. Learn best practices, which tools to use, and strategies for creating you own processes.Check out here.
Filed in:
WPS
by write2munish
Subversion 1.3.2 has been released. Subversion has been touted as the next generation of CVS, where it takes on the strengths of CVS and has added quite a new set of features to the release.Check out here.
Filed in:
J2EE
by write2munish
I had talked about scaling the existing applications to work in a cluster environment here. Subsequently, I had posted on findings on the products available in the market Terracotta here.As part of the same study, I came across this article, which details what all goes into building a strong, extensible, and flexible J2EE apps, tap into a WebSphere? cluster environment. This article describes what you need to consider when designing a Web-based application in a WebSphere Application Server cluster environment, including application file update and synchronization, serialization of session objects, and dynamic caching.
Filed in:
J2EE
by write2munish
The wsadmin scripting interface is a useful interface for managing your WebSphere? configuration, particularly when you need to automate tasks or perform other custom management. However, using Java Management Extensions (JMX) extends this powerful solution even further, allowing administrative capability to be directly embedded in the functions of your J2EE application.This article explains how a wsadmin script works, and how it can be easily rewritten as a servlet to accomplish the same task in JMX. We briefly discuss how WebSphere maintains its configuration information in XML files, and how equivalent JMX code can be used to accomplish what is done by way of wsadmin. Using IBM Rational Application Developer, the example demonstrates how JMX can provide a valuable solution in advanced custom administration for system integrators, independent service vendors, and application developers.
Filed in:
WAS
by write2munish
JBoss Rules is the supported and branded release of the Drools project and part of the JBoss JEMS product range. Drools is an enhanced Rules Engine implementation, ReteOO, based on Charles Forgy's Rete algorithm tailored for the Java language.Drools provides for Declarative Programming and is flexible enough to match the semantics of your problem domain with Domain Specific Languages.
Check out the same here.
Filed in:
J2EE
by write2munish
JBoss SEAM 1.0 represents a redefinition of web application architecture that extends the POJO + annotation-driven and configuration-by-exception programming model of EJB 3.0 into the entire web application stack. It integrates Java EE 5 technologies like EJB 3.0, JSF and JMS into a unified programming model and narrows the semantic gap between the business domain and the Java programming language by deeply integrating technologies like jBPM for business process and user interaction modelling and Drools for management of business rules.Seam 1.0 has the following new features:
* Seam Remoting - an AJAX-based remoting layer for EJB 3.0 components and JMS - allows client-side JavaScript to call EJB session beans directly
* Support for JSR-168 compliant portal engines such as JBoss Portal
* Elegant handling of internationalization and JSF messages via EL-based interpolation
* Helper components for JMS senders/publishers
* JSF tag library
* Redesigned XML-based configuration facility
* Support for integrating databinding architectures
* Eventing architecture for loosely-coupled components
* Seam Logging
* JBoss Cache integration for cluster-wide state replication
* Experimental Drools integration
* Compatibility with the Java EE 5 reference implementation
* Provides unique contextual state management architectureCheck out for more details here.
Filed in:
J2EE
by write2munish
I was evaulating JMS vendors for our messaging needs. I could not find any one single source which details the various JMS vendors in the market. So, I have compiled a list of vendors which came across
Open Source Implementations
ActiveMQ
JBossMQ
Mantaray
OpenJMSOthers
Arjuna
FioranoMQ
iBus
Joram
Nirvana
SonicMQ
SwiftMQthen you have the biggies of the messaging world.
IBM
TIBCO
WebLogic
Oracle
Sun
Filed in: J2EE
by write2munish
Every application has business logic. The logic might be some kind of validations or making calls in an order or doing some number crunching and spitting out the results. The business logic now can reside in multiple places. The business logic can reside from Presentation layer to business layer to the data layer ( even go down to Stored Procedures).
In my experience, what I have seen, the
This discussion is closed to new replies.
Trending After Hours posts
Sort by Trending