Showing posts with label SAP Portal. Show all posts
Showing posts with label SAP Portal. Show all posts

Friday, December 14, 2007

FAQs

Please note the URL of POST (Portlet Open Source Trading Site) jointly formed by Plumtree, documentum, bea, and Sun.

http://portlet-opensrc.sourceforge.net/

I wish, IBM would be there too.

FAQs Says as follows -

What are the new JSR 168 and WSRP portal standards?
To help our customers create a better user experience while trimming their integration and customization costs, leading software vendors can help ensure portlets use open portal standards such as JSR 168 and WSRP.

JSR 168, developed by the Java Community Process and formally approved, was created to establish a standard portlet application programming interface (API) to ensure interoperability among portals, portlets, applications and other content sources.

Java Specification Request 168 (JSR 168), has been developed and governed by the Java Community Process (JCP) standards committee
Approved October 2003
Java only – backed by all portal vendors, BEA, IBM, SUN, Plumtree to name a few
All portal vendors will release standard compliant product by the end of 2003 or during the first half of 2004.
WSRP, created by the Organization for the Advancement of Structured Information Standards (OASIS), is a Web Services standard that allows the integration of remote content and applications into portals.

Web Services Remote Portlets (WSRP), has been developed and governed by the OASIS standards committee
Approved, WSRP v1.0, September 2003
Web services standard which supports any language and is also backed by all major vendors
A more radical approach, which is more immature and needs to be refined. Slow uptake.

What is the open source site POST and why is Documentum, BEA, SUN and Plumtree creating and launching this site?
Documentum, BEA Systems, SUN Microsystems and Plumtree are working together to support the freedom to build standards-based application components that can be assembled within any portal. The POST (Portlet Open Source Trading site) provides a forum to help customers develop portlets and components based on the new JSR 168 and WSRP portal standards.

POST is found at http://sourceforge.net/projects/portlet-opensrc

Some cool articles

Applying the State Pattern to WebSphere Portal Portlets -- Part 1 Overview
http://www7b.software.ibm.com/wsdd/library/techarticles/0212_hanis/hanis1.html

Applying the State Pattern to WebSphere Portal Portlets -- Part 2 Implementation
http://www7b.software.ibm.com/wsdd/library/techarticles/0212_hanis/hanis2.html

Create your own portlet and Web service
http://www-106.ibm.com/developerworks/ibm/library/i-wsportlets/

IBM Portal Server Resources
http://e.bis.business.utah.edu/resources/wps_project.htm

The case for portlets
http://www-106.ibm.com/developerworks/ibm/library/i-portletintro/

WebSphere Portal Programming Pervasive Portlet Development
http://www7b.software.ibm.com/wsdd/techjournal/0207_wanderski/wanderski.html

WebSphere Portal Server programming Portlet application programming, Part 1
http://www-106.ibm.com/developerworks/ibm/library/i-portal/

WebSphere Portal programming Portlet application programming, Part 2
http://www-106.ibm.com/developerworks/ibm/library/i-portal2/

Portlets USENET Groups

As we all know that newsgroups are still best discussion medium on Internet. I was searching for portlets related discussion and found following two (one from IBM and other from BEA) -

NEWS SERVER: newsgroups.bea.com
GROUP ADDRESS: weblogic.developer.interest.portal

NEWS SERVER: news.software.ibm.com
GROUP ADDRESS: ibm.software.websphere.portal-server

I hope it will be usefu

Thursday, December 13, 2007

SAP J2EE server node hanging on startup

Have you ever had that dreadfull experience of a SAP J2EE not wanting to start?

A few days ago I restarted a Netweaver Portal (7.0) server and it's J2EE server nodes "hanged" on status STARTING APPS.
I created a dump stack trace of one of the server nodes, searched some OSS notes and realized it was the Application Thread's that was not enough.I increased the MaxThreadCount parameter of the ApplicationThreadManager as per Note 950921 (using the Configtool) to 100 and restarted the Portal server again, it then started up OK. SAP recommends that for XI system this parameter should at least be 150.
Here's a screenshot of the affected parameter in the Configtool:




The reason for this problem could be additional applications being deployed to the J2EE which uses more application threads or changes to the behaviour of deployed apps so always be sure to check this parameter value from time to time.

You can uses the thread dump viewer supplied by SAP Note 10202246 to make reading the dumps you create in the J2EE easier to read. Here's a screenshot of the viewer :


The following SAP Notes provide good starting points for J2EE troubleshooting:
Note 764417 - Information for troubleshooting of the SAP J2EE Engine 6.40
Note 710154 - How to create a thread dump for the J2EE Engine 6.40