Skip to Content
avatar image
Former Member

2004s AreaGroupPage and PCD objects in Portal

I know in NW04 ESS, in the portal we would create 2 pages to a workset:

(one for displaying the menu and one for displaying the services)

And 2 Iviews:

1) An SAP Web Dynpro iView that calls the XSSMenuArea application
2) An SAP Web Dynpro iView
You create this iView on the page that is to display the services.
You must enter a system ID for this iView. The system ID must refer to the J2EE server
on which the Web Dynpro services are executed.

How does this change in 2004s??? I dont see the need to create 2 pages anymore?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 03, 2008 at 05:39 PM

    we are going to build our own roles with turning off certain apps....i am wondering if i should follow this same methodology of adding 2 pages with to every workset etc....

    Add comment
    10|10000 characters needed characters exceeded

    • Yeh....follow SAP's model there....like I said, the "placeholder" works great as the resource is what tells the iView on the page which webdynpro to call. It cuts down on a lot of just plain "dummy" iViews. Need help just ask.

  • Sep 03, 2008 at 03:13 AM

    Uhmmmm nothing changed....

    (1) one iView for Area Group page

    (2) one iView for EACH Area page

    (3) the actual iViews for all your services

    sooo where are you confused?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 03, 2008 at 02:27 PM

    Look at the structure of the business package for NW04...

    There is 2 of the same iviews and 2 pages for every application.

    For example:

    
    - Personal Information (page)
            - Personal Information (iview)
    - Personal Information (page)
            - Personal Information (iview)
    
    

    Add comment
    10|10000 characters needed characters exceeded

    • Yes....I know what you mean. Mmmm....how to explain this...

      (1) one of the pages is STILL for the Area Page itself

      (2) the other one you see is kind of like a "placeholder" for ALL of the actual services. Since they are Webdynpros, look at the actual HF config for that resource and you will see that it calls the actual WD over there now. Kind of odd I know but cuts down on having lots of redundant portal objects.

      Make sense? If not, just keep looking at the backend services' actual resources for like "bank" or "address" or such and you will see what I mean.