cancel
Showing results for 
Search instead for 
Did you mean: 

Minimum requirements for creating an iView from a J2EE application.

Former Member
0 Kudos

Is it possible to have a j2ee application communicating with an iView in an environment without using SAP NetWeaver Development Studio, Portal Development Kit, etc. Is it possible to just download a JAR file or similar and do something like this:

import com.sapportals.portal.prt.component.*;
public class MyComponent extends AbstractPortalComponent {
   pubilc void doContent(IPortalComponentRequest req, IPortalComponentResponse resp) {
      //...
   }
}

...and where do i get this file.

And how do I implement this iView into the Enterprise Portal. I'm a beginner ... sorry!

I'm asking because it would be easy for java-people to do something like this without using to much time learning the SAP NetWeaver stack and the Developer Studio and so on.

Thanks for any help,

Audun

Accepted Solutions (1)

Accepted Solutions (1)

detlev_beutner
Active Contributor
0 Kudos

Hi Audun,

first, welcome on SDN!

About your question: Of course you could use a text editor to write your code, set a reasonable compile time classpath and compile using javac command, create file structure corresponding to the portal archive definition, zip that structure and rename it to PAR.

And of course, it is possible to make fire using to sticks of wood.

But hey, be honest, you don't go that way, do you?

As you are used to use a lighter for fire, you should get used to get all advantages from the NWDS - which is nothing else than an (old) Eclipse minus some plugins plus many plugins.

> for java-people to do something like this without

> using to much time learning the SAP NetWeaver stack

> and the Developer Studio

"Java people" should know Eclipse! Nobody is forced to love it, but every Java developer should be able to use it! So if you are not familiar with Eclipse, the time learning NWDS means the time learning Eclipse, too, so you should invest this independent if it's for SAP or not...

Start here, for example: http://help.sap.com/saphelp_nw2004s/helpdata/en/19/4554426dd13555e10000000a1550b0/frameset.htm

Hope it helps

Detlev

PS: Please consider rewarding points for helpful answers on SDN. Thanks in advance!

Former Member
0 Kudos

Hi!

Thanks for the reply!

As I understand: With a java-application I could either build a java component and use the structure required by PAR-files and load it onto the Portal. Or I could load an application directly through a URL iView. In this case I need to use JSP or similar to show the content because URL iView communicate with the application over HTTP.

1. Is the reasoning above correct?

2. Are there any other possibilities having a java application communicating with the Portal through iViews(disregarding Web Dynpro, ABAP, BSP application, ASP/.Net, SAP Connector iView)? I.e. does there exist a Java iView, similar to the BSP iView??

3. Using the URL iView. How do the application get notified when the user minimizes, maximizes, closes, changes the size of the iView window, and so on??

Thanks in advance!

Audun

PS. I like answers with specific examples.

detlev_beutner
Active Contributor
0 Kudos

Hi Audun,

Right, you can develop a SAP specific portal application, consisting of one or more components and/or services, deploy it, and create iViews directly out of the PAR components.

Or you can develop a standard J2EE application (or .NET or whatever), in short: a web application, running on the SAP server or on some third server, and integrate it into the portal using URL iViews or the ApplicationIntegrator.

No, there is nothing like a general "Java iView". As said, if you want to integrate a web application, in general it is independent on which technology this has been set up.

Using an URL iView (or AppIntegrator), the application in general won't react on changing iView settings, if you don't provide explicit JavaScript reacting on such things (which wouldn't make much sense, as if you develop a web application without special regard to the portal, you won't do this; and if you develop a web application with special regard to the portal, you should implement a portal application).

Hope it helps

Detlev

Former Member
0 Kudos

Thanks for the answers and the fast response.

Audun

Answers (0)