1.

Why Shouldn’t I Use The External-facing Portal For Internal Implementations?

Answer»

It is RECOMMENDED not to use this solution for internal use because some FUNCTIONALITY that is commonly used for internal IMPLEMENTATIONS is not supported.

Specifically, session management and WorkProtect mode are not supported as they require the use of the client FRAMEWORK JAVASCRIPT. Therefore, some standard SAP content – such as Web Dynpro, SAP business packages and KM (especially collaboration) – that uses these features are also not supported.

In addition, to get the full benefit of the performance improvements in an external-facing portal, the content must be “light” and supported by the light framework page. Content in internal implementations generally does not meet these requirements. For more information on recommended content for an external-facing portal, see the Content section.

It is recommended not to use this solution for internal use because some functionality that is commonly used for internal implementations is not supported.

Specifically, session management and WorkProtect mode are not supported as they require the use of the client framework JavaScript. Therefore, some standard SAP content – such as Web Dynpro, SAP business packages and KM (especially collaboration) – that uses these features are also not supported.

In addition, to get the full benefit of the performance improvements in an external-facing portal, the content must be “light” and supported by the light framework page. Content in internal implementations generally does not meet these requirements. For more information on recommended content for an external-facing portal, see the Content section.



Discussion

No Comment Found