Re-posting: WebDynpro + NWDI/JDI into Portal Application

[Former Member]

Hello reposting this fromt the NWDI category in hopes of getting the answer..

A beginner question.. hope you can help. Thanks!

-

---

Hello all,

We are fairly new to portal development. Presently, we're executing a tutorial on WebDynpro component-based development under NWDI. Of which we have the following components : Dictionary, Java, Library, EJB, EAR, Web Service, WebDynpro.

After completing the application, we were wondering on how can we have it as an accessible iView in our EP?

Are we to create Portal Application Module or a Portal Application Standalone component and have all these components be referenced on this project? If so, how do we go about it? Are there any guides available?

I've browsed through this link - but it appears to be based on a different scenario.

Help would be greatly appreciated. Thank you.

[Former Member · Accepted solution]

Hi Jan,

Usually you develop applications based on certain scenarios.

IF you have developed a WebDynpro Java/ABAP component you can create an iview on the portal and assign it to a user via a role and use it. However in development environements you can simply right click the application in NWDS and say run and it will run within a browser.

Typically you will create an EJB/EAR projects depending on the usage. The project where I worked had EJB which was consumed in a WD application.

Try to think of a scenario and develop an application which uses EJB's DYnpros and finally the portal

Thanks,

GLM

[Former Member · Accepted solution]

Thanks for the prompt response GLM,

Well, this WebDynpro application is done actually. We can test it on our local developer workplace. But now, we want to make it available in our EP as an iView so we can assign it to a user.

We are trying to deploy it via CMS/CBS.. hoping that will make the webdynpro application available in the portal content directory..

So, the bottomline is, since we are new to this, we don't know how to deploy the WebDynpro application via the NWDI (alongside the other development components) in the EP to convert it into an iView. Though, when it's a local and simple WebDynpro application, we don't have any problem deploying it into a PAR and from that convert it into a DC.

Thanks again GLM for the response.

Edited by: Jan Michael Jaudian on Aug 11, 2008 9:07 AM

[chintan_virani · Accepted solution]

Jan Michael,

Firstly convert your existing local project to a DC project. Check this link:-

http://help.sap.com/saphelp_nw70/helpdata/en/42/c8204dd57f136fe10000000a1553f7/frameset.htm

Once the project is converted to DC project, activate your changes and the NWDI Adminstrator will import this activity in the Dev Portal thru CBS/CMS tools.

Also you will not find the WD project in the Portal PCD. If you want this to show up in portal then you need to create a WD iView for your applcaition and assign it to a role.

Some links that may help you:-

http://help.sap.com/SAPHELP_NW04S/helpdata/EN/db/bd3642e2a3ab04e10000000a1550b0/frameset.htm

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/0c7b2f25-0c01-0010-f2a2-f8a65a9d...

http://help.sap.com/saphelp_nwce10/helpdata/en/45/fe4bf16db104a7e10000000a114a6b/content.htm

Chintan

[Former Member · Accepted solution]

Hello Chintian,

Thanks for the response.

Presently we have a WebDynpro project patterned from this [tutorial|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0b53558-6df6-2910-cfbf-a63316bb0fad].

So all the components are ready and well running on our Developer Workplace. And you mentioned that:

"Once the project is converted to DC project, activate your changes and the NWDI Adminstrator will import this activity in the Dev Portal thru CBS/CMS tools."

We have successfully released the activities and imported that from Consolidation. And now we're on Assembly (though we are having problems with broken DCs). Assuming that the assembly executes successfully, we have the SCA of the entire project, right?

If you want this to show up in portal then you need to create a WD iView for your applcaition and assign it to a role.

Will that SCA be present in the Deployed Component folder on our EP? From where, we can turn it into an iView and then finally assign it to a role?

And where will our project appear if it's not in the PCD?

Thank you very much.

Pardon for the novice questions.

[chintan_virani · Accepted solution]

Jan Michael,

You DO NOT create a Web Dynpro iView out of the SCA file. Check the document in previous post and create a WD iView for your applcation accordingly.

In brief the steps should be :

1. Right click on your folder --> Select iView option

2.Select WD java option

3. Select your applciation and views

The source code you have checked in will reside in the DTR (where your NWDI is.).

The tracks in NWDI will have a runtime system. For eg: The DEV track will have your DEV portal as its runtime system, similarly for QA and PRODUCTION.

Now when you build the file in consolidation the content gets deployed on the JAVA AS of QA portal, so the changes you have done will be available in QA portal.

I am not sure on the exact location on where you can check the SCA file but if your application has been deployed correctly then you should get it in Step 3 while creation of WD iViews.

You can also start / stop application or create JCo Destinations for the R/3 system by logging onto WebDynpro content Administrator by going to http://<yourserver>:<yourportnum>/index.html -

---

> Web Dynpro -

---

> Content Administrator. You can logon here with Admin id and password.

Chintan

[Former Member · Accepted solution]

Thank you again, Chintan.

As it appears, we were not able to define the Runtime Systems when we created the DEV and Consolidation tracks. And have yet to define the JAVA Engine URL and User-Password for it.

At the moment this is starting to be more clear.

One last question, if you don't mind, will it matter if we are testing/deploying via our Developer Workplace? I mean - do we need to also deploy these components on our actual EP? (Build & Deploy them again on a different J2EE engine from the NWDS or we don't have to since the files in the DTR are the ones that will matter?)

Thank you again.

-Jan

[Former Member · Accepted solution]

Hi Jan,

Any app that you develop locally and deploy to the WAS engine will be deployed under the following location:

/usr/sap/<SID>/JC00/j2ee/cluster/server0/apps/local.

During deployment the application is bundled into an ear file and not a sca file.

The deployment of your application will depend on your landscape design. If you have only one server where you EP is running then I guess you must have already configured the tracks in NWDI to deploy you application to the WAS engine of that server. Unless you have an EP box and then yet another WAS engine then your deplloyment will happen to the WAS engine and will be available in your EP server through iviews.

Thanks,

GLM

[Former Member · Accepted solution]

Hello GLM,

Thanks for the response.

At the moment, we have finally configured the Tracks and their runtime sytems (Development and Consolidation). After the activation of the activities.. the build from the activation log contained no errors.

But right now, we can't seem to find the WD component I built from the WebDynpro Content Administrator page and even with the Step 3 in creating the iView.. I can't locate the component there..

What should be done?

thank you in advance.

[Former Member · Accepted solution]

Hi,

Make sure that the component is deployed on this server by checking it from the Visual Admin

or

Try to redeploy to the server once again.

Hope the server where you deploy and the one you are configuring the portal iview is the same.

Regards

Ayyapparaj

[Former Member · Accepted solution]

Hello,

Thanks for the response.

 Try to redeploy to the server once again.

We are testing the WD component on a local developer workplace environment. Also we have NWDI set up.. so the components should be on the DTR right?

Do we need to change the J2EE admin to its remote location and not on our local? And redeploy all the components from there?

[chintan_virani · Accepted solution]

Jan,

After you activate the activities, & release them from your local Developer workplace the respective transports should be available in the Import queue of your DEV/QA system with "Waiting for Import" message.

Now once the NWDI Admin imports these actvities they come into the DEV/QA portal and the status should read as Import finished.

After this step is completed, it should definitely show up in the Content Admin as well while iView creation.

Also after you do these changes just verify the path given by GLM and check if you see your content deployed there.

Also if possible go thru this sap chapter, it should give you better idea

http://www.sap-press.de/download/dateien/817/sappress_java_programming.pdf

Chintan

[Former Member · Accepted solution]

Hello Chintan,

Thanks for all the help on this one. I've finally managed to create the iView/s of the WD components created.

Also, what's interesting is that the old components we developed earlier started to appear as well.. that's after bouncing the server.

Probably, the NWDI track changes we configured did not take effect immediately. Also the 'import' of the released activities helped as well.

Thanks a lot.

Points awarded. And hope this helps others as well who's just starting out.

[chintan_virani · Accepted solution]

Jan,

Well server restart is not generally required but glad to know that your problem is solved.

Chintan