This article describes the approach taken on a recent WebSphere Portal deployment project to secure specific pages on the portal that collect and display personal information about the user. Portal administrators and developers might be able to use this technique for your WebSphere Portal deployment.
This article describes Java™ API for XML-Based RPC (JAX-RPC) handlers and demonstrates how to easily generate, implement and add a JAX-RPC handler to an existing WebSphere Web service imported from the IBM® Rational® Application Developer Samples Gallery. Handlers are pluggable applications for handling XML messages and can be registered to run before or after the Web service or Web service client is invoked. They are frequently used in common functions such as processing message headers, logging activity, and measuring performance. This article shows you how to implement and deploy a message logging handler.
The article shows how to set up a portal project infrastructure in IBM® Rational® Application Developer that can be used to perform daily builds using Apache Maven. You walk through a complete example which covers the primary aspects of the build and deployment process. You see how to extract source from a version control system, build the source, deploy the resulting artifacts on IBM WebSphere® Portal Server V5.1, and generate reports about the process.
Each year JAVAPro magazine turns to its readership and asks it to select the best tool it uses to get the job done — whether the task is on an individual or a team basis. This year, IBM WebSphere Portal won the Best Java™ Enterprise Portal Technology category competing against BEA, Oracle and Sun Microsystems.
Check out the article here.
Service-oriented architecture (SOA) is hot. And as today's primary entry point for SOA, the emerging enterprise service bus (ESB) market is heating up, too. For example, within the last few months two major application platform vendors, BEA Systems and IBM, formally entered the ESB market, legitimizing the concept for many potential buyers. To assess the state of the ESB market and see how the vendors stack up against each other, Forrester evaluated the strengths and weaknesses of top ESB vendors using 100 criteria. The result: The market has two segments, with different leaders in each. The ESB suites segment is led by Cape Clear Software, Fiorano Software, BEA Systems, and Sonic Software, whereas the comprehensive ESB suites segment is led by Oracle, TIBCO, and Sun Microsystems.
The analysis that led to this view of market segmentation was based on customer interviews, which led us to group ESB buyers in two groups:
* The "keep it simple" group wants simple and low-cost integration, support for service orchestration, and the core of future support for managing services through their full life cycle.
* The "I want it all now" group wants ESB capabilities in the context of their leading application or integration platform, combined with richer service life-cycle support, and BPM capabilities needed to support business transformation.
Both groups want full support for SOA and a wholehearted embrace of open industry standards.
Tune in to the insight and outlook of IBM visionaries and leading technical practitioners as they comment on issues facing IT architects today and in the future. This month they respond to the question, Why should you care about SOA, and when is it the right choice and when is it the wrong choice?
Check out the article here.
Web services have become a standard way of implementing Service Oriented Architectures. Developers have used many patterns of developing these Web services, but these patterns have not been well-defined or discussed.
The article identifies and describes three development patterns:
* Bottom-up pattern: Start with Java to produce WSDL.
* Top-down pattern: Start with WSDL to produce Java.
* Round-trip pattern: Start with WSDL to produce Java, which is then used to produce WSDL, which is then used to produce Java.
The article then goes on to explain the each pattern, its advantages and disadvantages. Pretty basic but good to read.
Check out the article here.
The article shows you how to use IBM WebSphere Process Server to take control of the connectivity and persistence logic for container-managed persistence (CMP) beans, enabling them to be stored to non-relational datastores. You learn about the various data access patterns that are supported and step through basic usage scenarios that include demonstrated examples ranging from very simple to somewhat complex. This article covers some best practices, such as using Service Component Architecture (SCA) from within the special Java class, UserDefinedPushDownMethodsImpl, enabling reuse of services that expose legacy systems via a service-oriented architecture (SOA), and insulating you from needing to know all of the details involved in communicating with the non-relational datastore.
A number of new tutorials have been published on the IBM Developerworks Site, on creating JSR 168 Portlets, which allow you to implement inter-portlet communication, portlet service and WSRP portlets. Check out all these tuturials here.
Creating a JSR 168 portlet for use by diverse portals using Web Services for Remote Portlets
Creating and deploying a portlet service for IBM and JSR168 portlets
Implementing JSR 168 inter-portlet communication using Rational Application Developer V6.0 and WebSphere Portal V5.1
Subscribe to:
Posts
(
Atom
)
