Hi Tamilarasan,
Your confusion is quite understandable. Think of the Portal as more or less a presentation layer that sits on top of all your sources of data.
So, the Portal can have iViews which each communicate with different back end systems. i.e., on one page you can have multiple iViews (components) each showing you different data. One of these iViews could be pointing to a SAP CRM system, another points to an SEM system and another iView points to a BW system. Each a 'physically' different instance.
Having said that, there is also the possibilty that you have another page with multiple iViews ALL pointing to the same backend R/3 system. i.e., a page with say three iViews, each showing a different R/3 transaction from the same back end system.
In terms of the singular database, I'm not quite sure what you are asking. If the data is all integrated into this singular database, then the meaningful extraction of this data for presentation in the Portal (as an iView) would most likely fall to a Portal developer.
Hopefully, I've cleared up some stuff for you and I'm sure others will add to this...
Good luck 😉
Mike
Add comment