Problem when Integrate Webdynpro into ESS

[Former Member]

Hi everyone, i need to integrate my application into ESS. In My Ess there is link to "Career and Job". When I click this link,there will be 3 link (3 different application). I have develop one application under one project in NWDS and i have success integrate this application into ESS (so there is one link that will navigate to my custom application). My Question is for other link (so there still 2 link left), must I create 2 other project in NWDS ? Is exists another way to do this ? Because in both application i need to use some view that same with first application and I'm lazy to create again this views in another project. Thank you.

Regards,

Satria

[Former Member · Accepted solution]

Hi ,

You can use the same project , but create one more application alone and link to the necessary component.Each application will have its own start up interface view.. and each application will have a different url .. even if its in the same project..

http://host:port/dispatcher/webdynpro/local/projname/appname1 or appname 2 or appname 3..

Create appropriate service for each of these in IMG and u r ready to go..

Regards

Bharathwaj..

[Former Member · Accepted solution]

Thank you, it's works. But this lead me to another questions.

1) In my first application I have use one custom controller with name "Core". When i create another application,it is best to use same custom controller or i create another custom controller?

2) If there is bug in my first application or another problem at my first application, is this affect my another application in ESS ?

3) How should i arrange name for package ? This question arise when I choose another package name for another application. Before I add my second application, I assign first application, models,custom controller, view,windows into one package name. Is it best practice or it is bad ? If it's bad, what the best practice? Thank you

Regards,

Satria

[Former Member · Accepted solution]

> Thank you, it's works. But this lead me to another

> questions.

>

> 1) In my first application I have use one custom

> controller with name "Core". When i create another

> application,it is best to use same custom controller

> or i create another custom controller?

If the actual process is same , you can use the same custom controller .. For usability sake , if there are many functions specific to each of the applicaitions it would make sense to split them into seperate custom controllers .

> 2) If there is bug in my first application or another

> problem at my first application, is this affect my

> another application in ESS ?

If the bug is a view or component which is used in the other application too.. then it wud affect..

> 3) How should i arrange name for package ? This

> question arise when I choose another package name for

> another application. Before I add my second

> application, I assign first application,

> models,custom controller, view,windows into one

> package name. Is it best practice or it is bad ? If

> it's bad, what the best practice? Thank you

com.<company name >.projectname.comp - For component

com.<company name >.projectname.comp.views - For views

com.<company name >.projectname.apps - for apps

somethin lik this..

For better design , you can create seperate components for each app.. and if you want to reuse some view from other component , make them as used components and access their interface views..

Regards

Bharathwaj