System Landscape, Performance, Transport and Permissions in SAP Enterprise Portal 7.3
In the following sections you are informed on some important portal system administration topics like portal landscape administration, performance management, portal transport features and on portal permission handling.
Portal System Landscape
The portal system landscape is a collection of systems - the portal objects that represent external, or back-end applications or Web services - and the tools needed for managing them. The portal uses systems to connect to the applications and retrieve data from them to display in portal iViews.For more information on the system landscape see the Portal Administration Guide for SAP NetWeaver 7.0 and SAP NetWeaver 7.3.
The next paragraphs provide general recommendations and tips for building a portal infrastructure.
This presentation contains recommendations for SAP NetWeaver Portal deployments and for SAP NetWeaver Portal system landscapes. It also covers Adobe Document Services and SAP NetWeaver Business Process Management in SAP NetWeaver Portal based system landscapes.
Dependent on the targeted use cases there are several possibilities, how to design a portal landscape. Considering these facts and also reflecting SAP's actual portal strategy, this presentation provides a clear message about the recommended landscape setups for the portal with SAP NetWeaver 7.0.
Lessons Learned and Examples: This session provides general recommendations and tips for building a portal infrastructure. Based on various business scenarios and real-life examples we will demonstrate how to set up your portal landscape.
These guides will help the system administrator to maximize the performance of SAP NetWeaver Portal and to improve the content consumption performance by using the caches available in SAP NetWeaver Portal 7.3:
- Performance Best Practices Guide for SAP NetWeaver 7.0
- Performance Best Practices Guide for SAP NetWeaver Portal 7.3
- SAP NetWeaver Portal 7.3 - Tuning Caches
Portal Transport and CTS+
To get a general introduction on transporting possibilities in the portal, please have a look at the transport documentation in the Portal Administration Guide.
Integration of CTS+ into SAP NetWeaver Portal
Since SAP NetWeaver 7.0 SPS 12 / 13, you can also use the enhanced mechanisms of the Change and Transport System (CTS+) of the ABAP Stack to transport Java objects. The idea is to provide all the transport logistics and monitoring options that are well known from the ABAP stack to the Java transports as well.
Since SAP NetWeaver SPS 13 the Package Export Editor in SAP NetWeaver Portal supports CTS+. If a CTS+ system is integrated and configured accordingly, the Portal administrator/developer user can choose whether he would like to use the ‘classical' way of exporting via the file system or the new CTS+ way.
You can find general information on the Change and Transport System page on SDN. In this presentation, you can learn more about transporting options in Portal and KMC and how they are integrated with CTS+.
The following demos are available:
- Demo Part I: Shows how the Portal export works without CTS+.
- Demo Part II: Shows how to configure CTS+ for the Portal.
- Demo Part III: Shows how the Portal Transport works with CTS+.
Have also a look at the blog Use Cases in Life-Cycle Management – Change and Transport System
You find more information on CTS+ and SAP NetWeaver Portal on the page Resources on CTS+
To learn more about CTS in general, please have a look at help.sap.com (Change and Transport System). In the section 'Non-ABAP Transports in Change and Transport System' you can also find details on how Java objects can be transported and how the configuration looks like.
CTS+ in SAP NetWeaver 7.3
Starting with SAP NetWeaver 7.3, there is a new functionality for CTS+ called "Change Recording". This functionality is available for Portal content objects.
Read also Which way of exporting Portal Content should I use? which explains in which scenarios "Change Recording" can be used.
Portal permissions define user access rights to objects in the Using the Portal Catalog, which includes the Portal Content Directory (PCD) and the GPAL Repositories. Permissions in the portal are based on access control list (ACL) methodology. Essentially, every portal object can be assigned directly to an inpidual user or collectively to groups of users through user groups and roles. To extend initial access rights to portal content and functionality for users in the organization, the super administrator needs to delegate portal permissions as needed.
To troubleshoot "Access Denied" errors which may indicate a permissions issue, see Troubleshooting the "Access Denied" Message in the Portal.