RE: WebDynpro + NWDI/JDI into Portal Application

[Former Member]

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|http://help.sap.com/saphelp_nw04s/helpdata/en/32/98e6418b7eca17e10000000a155106/frameset.htm] - but it appears to be based on a different scenario.

Help would be greatly appreciated. Thank you.

[Karin · Accepted solution]

Hi,

if you deployed your Web Dynpro Application, you can create an iView out of it. Please find the details on [help.sap.com|http://help.sap.com/saphelp_nw70/helpdata/EN/62/b3dc4281de2878e10000000a155106/frameset.htm]

You can also develop components especially for the portal if you'd like to use portal service for instance. this is also documented on [help.sap.com|http://help.sap.com/saphelp_nw70/helpdata/EN/d0/f6584289e59041e10000000a1550b0/frameset.htm]

Kind reagrds

karin

[Former Member · Accepted solution]

Thanks Karin,

I'm looking into portal services now.

Moreover, would it be right to think that once you have 'approved' the NWDI track you created on the CBS, will it be considered as deployed? And from the portal, you can then access the specific webdynpro application and make it to a PAR file?

Another question, I think I've read somewhere that you can also create a portal application module component to have your WebDynpro application be 'deployable' to the portal?

Regards,

Jan

[Former Member · Accepted solution]

I suggest you have a look at the different component types available, since you are mixing up a lot of things: http://help.sap.com/saphelp_nw70/helpdata/EN/d7/fc139ba1549047a5372ad3c0d540ea/frameset.htm.

[Former Member · Accepted solution]

Approval means that you have tested the component in the Test stage and approve it to go to production. It then becomes available for Import in the import queue of the Production Stage, so it is NOT yet on Production at that point in time.

[Former Member · Accepted solution]

Thanks for the reponse Pascal,

Well, what we actually executed is this [tutorial|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0b53558-6df6-2910-cfbf-a63316bb0fad] - And so it pretty much involves a few more different types of components. Dictionary to WebDynpro.

Though at the moment, we have imported the the 'released' activities into assembly. Unfortunately, we encountered an error: broken DCs. Assuming that we have successfully "assembled" the DCs into an SCA, will we be able to see that under Web Dynpro Content Administrator's Deployed Content folder? Meaning, we can finally create those WebDynpro objects into iViews and assign them user roles?

Thanks in advance, Pascal. Greatly appreciated.

Pardon for the novice question.

[Former Member · Accepted solution]

Which runtime systems do you have defined for the track? Your Web Dynpro's should already be available in the runtime systems connected to the stages before the Assembly stage (Development and Consolidation).

Where do you have these Broken DC's? If you are getting this error in the Assembly stage, then you have broken DCs in Consolidation (Assembly just grabs the DC build results from the Consolidation stage and packages them into an SCA). You may have forgotten to import the required SCA's into the Consolidation stage (SAP_BUILDT, etc.).

[Former Member · Accepted solution]

Which runtime systems do you have defined for the track? Your Web Dynpro's should already be available in the runtime systems connected to the stages before the Assembly stage (Development and Consolidation).

Unfortunately, we were not able to define the runtime systems before completing exercise. (Would that be an issue?) Though we just defined both runtime systems for Development and Consolidation. On that configuration though, we did not define the J2EE Engine URL, J2EE Engine User, J2EE Engine Password (should we define this one as well? though from the guide, it did not made mention of this.)

Where do you have these Broken DC's? If you are getting this error in the Assembly stage, then you have broken DCs in Consolidation (Assembly just grabs the DC build results from the Consolidation stage and packages them into an SCA). You may have forgotten to import the required SCA's into the Consolidation stage (SAP_BUILDT, etc.).

Yes, it's in the Assembly part. Also we have the following SCA's:

- SAP-JEE

- SAP_BUILDT

- SAP_JTECHS

Also from a different issue and research, it stated that we also need to patch our engine with this: SAP CR CONTENT SAP MASTER DATA FOR SLD 2.0 (presently, we haven't yet as this was related to creating portal application module components...)

We are on SP9, by the way.

This is very much appreciated Pascal. Thank you.

[Former Member · Accepted solution]

You can use the CBS WebUI to check what's going on concerning builds, etc. Use that to verify that you have all required DCs in your consolidation stage (the *_C compartment). For nw04s tracks you should see these numbers under Total DCs:

sap.com_SAP-JEE_1 89

sap.com_SAP_BUILDT_1 49

sap.com_SAP_JTECHS_1 100

You can also view the build logs for your broken components there to figure out what is going wrong. Perhaps you can post a build log of a broken DC, so we can have a look at it.

You do not need to specify the J2EE stuff; for deployment only the SDM stuff is required.

[Former Member · Accepted solution]

Thank you Pascal.

At the moment, we have finally successfully assembled the releases. And we have configured the Runtime Systems for each DEV and CONS tracks.

But at the moment, we cannot locate those components. From what I've learned is that everytime you "Activate" the activities you checked in, CBS will automatically deploy your components to the DEV runtime system. Sadly, we cannot see the components there.

Anything we should check or look into? At present we're bouncing our EP system to see if the system can "refresh" and see the changes.

Thanks in advance.

Regards,

Jan

[Former Member · Accepted solution]

Please check the following things:

Is the "Disable automatic deployment" checkbox for the Development runtime system checked? Yes -> NWDI will not auto-deploy after a succesfull build. You will then have to do it manually using the TCS Deployer: http://<nwdi server>:<port>/TCS/Deployer.

Are your SDM settings for the Development runtime system correct? Expand the "View/Edit Deployment Substitution Parameters" by clicking the icon on the right. You should get a populated table. If not, your SDM settings are incorrect.

[Former Member · Accepted solution]

Thanks,

This issue got resolved after restarting the server cluster - two areas I might look into later though:

- SDM Runtime System configuration did not take effect after "Save and Restore"

- there was a Deploy Service Error

- Consolidation required SCAs not imported

Moreover, glad this is closed now.

Hope this helps developers who's just starting as well.

Thanks all.

-Jan

Edited by: Jan Michael Jaudian on Aug 13, 2008 7:44 AM