Blogs by

Rory Murphy

I have been writing a series of (very occasional) blogs about configuration issues which can cause lots of headaches for portal administrators and result in many support messages reaching SAP unnecessarily, based on my experience

I want to use this blog to highlight a configuration issue which has caused quite a number of support messages to reach us on the Enterprise Portal team. That is the use of the Message

In my Accessing Backend Content through the Enterprise Portal from the Internet, ‘Accessing Backend Content through the Enterprise Portal from the Internet’, I discussed the requirement for the browser to be able to communicate with

In my  experience, there is a quite prevalent misconception about how the portal works with regards to integration of ‘backend’ SAP web applications (BSPs, BW Reports, ABAP or Java WebDynpros, transactions using WebGUI, IACs). Specifically,

Of course the SAP NetWeaver Enterprise Portal is the only portal framework you’ll ever need, but what if you have an existing website – based on a third-party or custom framework – and you want

Say that you want to call an application (could be a SAP Application like a BSP or a custom web application) in the Enterprise Portal using the applicaton integrator. Additionally you want to pass some