Integrating .NET web app into IBM Websphhere portal

S

Shikari Shambu

Hi,
I would like to integrate a .NET web application into IBM Websphere
portal. Whati is the best way of integrating these two beasts?

Is there are way to get my .NET application to return XML compliant with JSR
168?

TIA
 
J

Joerg Jooss

Shikari said:
Hi,
I would like to integrate a .NET web application into IBM Websphere
portal. Whati is the best way of integrating these two beasts?

Is there are way to get my .NET application to return XML compliant
with JSR 168?

I don't think such a component exists -- you'll have to write on yourself.

Cheers,
 
D

Dino Chiesa [Microsoft]

Chiming in. . .

The best way to integrate WebSphere Portal with .NET is via webservices, a
model based on well-thought out and well-supported standards. IBM has
examples of how a Websphere portlet can consume a webservice and emit potlet
UI. This is simple, and just works.

It is less optimal to integrate portal artifacts at the UI level. There is
a WSRP standard that attempts to cover this, but it is (IMO) neither well
thought out nor well-supported by either Websphere or .NET.
Architecturally, WSRP is an odd bird, and the implementation itself
introduces lots of challenges.

However, if you insist on pursuing WSRP, there are some technologies that
may help:
- NetUnity (www.netunity.com) has a framework to enable WSRP-enabled
portlets in .NET. These are not Sharepoint artifacts, but NetUnity
portlets.
- There is a WSRP producer workspace on GotDotNet, not really usable in
production, but more a proof of concept. It's a Web service product that
ships a HTTP table (with all the right WSRP DHTML class taggin info) in a
WSRP-compliant SOAP envelope. Using this I think there is some manual
construction of HTML, which is then embedded in a WSRP envelope. NetUnity
does quite a bit more.

WSRP Toolkit for Sharepoint
http://www.gotdotnet.com/workspaces/workspace.aspx?id=805b3559-c810-4119-86f4-11ba5c16a5b0

-Dino
 
M

Mike

As Dino writes NetUnity Software actually at http://www.netunitysoftware.com
allows the integration of .NET to any compliant WSRP Portal including
WebSphere Portal.

The framework matches fairly well with the JSR-168 since WSRP and JSR-168
were developed at the same time and share a lot of common features. The WSRP
..NET Framework is a web Service as (WSRP - Web Services Remote Portlets)
NetUnity portlets use attributed code to describe the metadata of the
portlets and even allow ASP.NET pages to be executed to return the fragments
of markup for the WSRP Portlet.

Example "Hello World" portlet in the NetUnity WSRP .NET Framework:

using System;
using NetUnity.eWSRP;

namespace NetUnityExample
{
[OfferedHandle("5f8a7896-ae46-45b3-a3f4-8b420af6a563")]
[Title("Hello World")]
[Description("Displays Hello World")]
[Modes(PortletMode.View)]
[WindowStates(WindowState.Maximized, WindowState.Minimized,
WindowState.Normal, WindowState.Solo)]
public class HelloWorldPortlet : NetUnity.eWSRP.Portlet
{
protected override void OnRenderView()
{
Response.Write("Hello World");
}
}
}

WSRP is a good start in standardizing the world of portals. If you have
little or no experience in JSR-168 or Java and want to integrate your Portal
with .NET the NetUnity WSRP .NET Framework would seem to be your best
solution.

- Mike

Dino Chiesa said:
Chiming in. . .

The best way to integrate WebSphere Portal with .NET is via webservices, a
model based on well-thought out and well-supported standards. IBM has
examples of how a Websphere portlet can consume a webservice and emit potlet
UI. This is simple, and just works.

It is less optimal to integrate portal artifacts at the UI level. There is
a WSRP standard that attempts to cover this, but it is (IMO) neither well
thought out nor well-supported by either Websphere or .NET.
Architecturally, WSRP is an odd bird, and the implementation itself
introduces lots of challenges.

However, if you insist on pursuing WSRP, there are some technologies that
may help:
- NetUnity (www.netunity.com) has a framework to enable WSRP-enabled
portlets in .NET. These are not Sharepoint artifacts, but NetUnity
portlets.
- There is a WSRP producer workspace on GotDotNet, not really usable in
production, but more a proof of concept. It's a Web service product that
ships a HTTP table (with all the right WSRP DHTML class taggin info) in a
WSRP-compliant SOAP envelope. Using this I think there is some manual
construction of HTML, which is then embedded in a WSRP envelope. NetUnity
does quite a bit more.

WSRP Toolkit for Sharepoint
http://www.gotdotnet.com/workspaces/workspace.aspx?id=805b3559-c810-4119-86f4-11ba5c16a5b0

-Dino
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,768
Messages
2,569,574
Members
45,050
Latest member
AngelS122

Latest Threads

Top