Tuesday, June 17, 2008

define "composite applications". define "mashups"

I admit. I am shamelessly quoting from this article because now you have a good definition of 'composite applications' versus 'mashups':

Composite Applications

Composite applications involve a “service-oriented” wiring between applications and are deployed to enterprise platforms. This event-based wiring of data between applications can create a dynamic desktop where, as the workflow inside one application is completed, all other applications that rely on this application can reflect the change. The completed application is then placed in the background and the user focuses on the next task. This enables not only component reuse within an organization, but also provides a framework for application reuse across the business. In this way, both line of business (LOB) and Information Technology (IT) applications can be integrated together on the desktop.


A ″mashup″ combines data from multiple applications into an extremely lightweight application rendered in a browser. Mashups can extend enterprise data with services from the public internet such as Google Maps for location services, RSS (Really Simple Syndication) Feeds to publish content or Widgets (web plug-ins) that provide specific functions such as blog, wiki or social networking capabilities. Mashups are not intended to be strategic, systematically built, industrial-strength enterprise applications; rather, they are created quickly or opportunistically to meet a focused tactical need. Mashups are generally personalized to fulfill personal productivity needs rather than the requirements of a long-standing corporate role. 1 Mashups leverage content and logic from other Web sites and Web applications, they’ are lightweight in implementation and are built with a minimal amount of code (which can be client-side JavaScript™ or server-side scripting languages, such as PHP or Python). These are not fixed requirements, but reflect the original implementation of the mashup concept in Web 2.0 startup companies, which typically do not use enterprise oriented platforms, such as Java or .NET.

Monday, June 09, 2008

fixing was and portal (continued)

following my previous post on this topic, the following story is something we found by trial and error actions at a customer site. Actually, the story is about what to do in order to make sure that fixes are applied successfully on WebSphere Portal 6.0.x

We'll see if this process has been improved in WebSphere Portal 6.1, when it will be out and I will get the opportunity to play with it.

So, turns out that you'd be better applying e-fixes by hand, manually, one by one, from the command line. Forget the Java Wizard of UpdateInstaller for Portal, and forget the fix-packs, for instance the installing script for fix-pack which is supposed to apply about 100 patches does not get the job done, properly. This is because fix-pack is trying to start/stop/start/stop the Portal itself several times and probably it gets something wrong on the way.

As such, load yourself with patience, plan for 2 man/day effort and proceed as following:
1. Get all your fixes from Fix Central site. Usually, if using IBM's DownloadDirector, you'll have several zip files downloaded on your folder.
2. Get the Portal UpdateInstaller, unzip it and place it under . On my install, I have this under d:\ibm\WebSphere\PortalServer\UpdateInstaller
3. Create your fix folder as in d:\ibm\WebSphere\PortalServer\fix
4. Then, do the following: read each of the fixpack readme :) Yes, really, do that :) Because some have other fixes as required for successful installation, then you might need to run for certain fixes commands like 'WPSconfig.bat apply-pk35496'
5. So, if you decide to apply a fix, copy its jar file into the d:\ibm\WebSphere\PortalServer\fix folder.
6. Decide how many fixes you want to apply, copy their jar files into the fix folder, making sure required other fixes are already applied or installed in the same run of UpdateInstaller.bat
7. The command line to apply a set of fixes is, from the UpdateInstaller folder, as seen below:

D:\ibm\WebSphere\PortalServer\UpdateInstaller>updatePortal.bat -install -installDir "d:\ibm\WebSphere\PortalServer" -fix -fixDir "d:\ibm\WebSphere\PortalServer\fix" -fixes PK35276 PK37018 PK32211 PK32501 PK32562 PK32570 PK32573 PK32626 PK33082 PK33379 PK33783 PK34220 PK34611 PK34624 PK34828 PK35170 PK35496

Happy patching :)

Disclaimer: The information in this weblog is provided "AS IS" with no warranties whatsoever, and confers no rights to any institution/person/organization. These are my personal thoughts and ideas. When I am inspired by others I give credit, I do not assume other's work and efforts. This site is NOT supported, approved, blessed etc. by Lotus Software and/or IBM Corporation.

Creative Commons License

This work is licensed under a Creative Commons Attribution 3.0 License.