Monday, October 10, 2011

Google Dashboard

Have you ever thought how many Google service you have joined. I think not. Every time you might have come across some new service from Google and you might have joined or linked your Gmail account to other service.

Now Google has created a Dashboard where you can see all your services and change settings If you think you are sharing your personal and sensitive data.

https://www.google.com/dashboard/b/0/


Monday, October 1, 2007

IBM Websphere Training

IBM Education Assistant: Websphere All Product
http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/index.jsp

Business Process Choreographer samples

http://publib.boulder.ibm.com/bpcsamp/index.html

DB2 Tips

Question: How to get Current Date in DB2?
Ans: select current date from sysibm.sysdummy1
Same way we can get current time and timestamp using following command
"current time" and "current timestamp"

Alternatively we can use following commands
values(current date)
values(current time)
values(current timestamp)
to get current Date, Time and Timestamp

-> To see maximum active agent:
db2 get dbm cfg | grep "(MAXAGENTS)"

-> To see maximum application connected to a particular database:
db2 get dbm cfg for REPLACE_WITH_DB_NAME | grep "(MAXAPPLS)"

Thursday, September 6, 2007

PORTLET and AJAX

Asynchronous Rendering of Portlet Content With Ajax Technology:

http://developers.sun.com/portalserver/reference/techart/asynch_rendering.html

Best Practices for Applying Ajax to JSR 168 Portlets:
http://developers.sun.com/portalserver/reference/techart/ajax-portlets.html


Using Ajax with WebSphere Portal:
http://www.ibm.com/developerworks/websphere/library/techarticles/0606_bishop/0606_bishop.html

Building an Ajax portlet for WebSphere Portal:
https://www6.software.ibm.com/developerworks/education/websphere/0608_bishop/section8.html

Web Services for Remote Portlets (WSRP) 2.0 Draft Available

Taken from :
http://www.infoq.com/news/-Web-Services-for-Remote-Portlet

Details:
The OASIS Web Services for Remote Portlets TC recently has approved the latest revision 2.0 of the Web Services Remote Portlets as Committee Draft and approved the package for public review.

According to Subbu Allamaruaju, Staff engineer at BEA and a voting member of the technical committee, WSRP 2.0 is a major improvement over WSRP 1.0 and that the most important benefit of 2.0 is better user interaction - you can build more lively portlet applications with WSRP 2.0. The spec does improve upon WSRP 1.0 by adding a new operation to talk to portlets using technologies like AJAX. The WSRP TC already started working on developing a more comprehensive model for solving more complex AJAX use cases.

While WSRP 1.0 provided the basic plumbing for aggregating remote portlets, WSRP 2.0 makes the protocol more useful, and lets developers build more interactive applications using remote portlets.

Mr Allamaruaju went on to add "The key features that I'm most excited about are (a) coordination, which allows portlets to talk to each other in a loosely couple manner, (b) new interfaces to migrate portlets from environment to environment, which ease the pain of managing large remote portlet deployments, and (c) improved resource handling, which will address some of the AJAX use cases. There are a number of other changes in WSRP 2.0 which help clarify the spec better and make interoperability easier to archive."

As far as the relationship of JSR168 and JSR268 to this effort, Allamaruaju said "JSR-168/286 and WSRP have always been orthogonal. The Java specs define a programming model for portlets, while WSRP defines a remote protocol between portal applications and portlet containers. Although JSR-286 effort started later than WSRP 2.0, the JSR-286 EG (I'm member of this EG) is committed to developing a Java API that fully takes advantage of all WSRP 2.0 improvements. I'm happy to see that these specs are evolving together, which I think is a key requirement for the success of both."

Web Services for Remote Portlets Specification v2.0

The public review starts today, 14 June 2006, and ends 13 August 2006. The technical committee strongly encourages feedback from potential users, developers and others, whether OASIS members or not, for improving the interoperability and quality of OASIS work.

You can find more information about the committee at its home page. Comments may be submitted to the TC by any person, by a web-form that can be reached either on that page, via the button marked "Send A Comment" at the top of that page, or using a web based form. Submitted comments (for this work as well as other works of that TC) are publicly archived. All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members.

The specification document and related files are available in HTML format and PDF. The specification weighs in at about 200 pages. There are also XSD, WSDL interfaces available.

What is Google upto?

http://blogs.ittoolbox.com/km/vikramark/archives/what-is-google-upto-9058