This guideline is not subject to your license agreement or any other service or subscription agreements with SAP ("SAP Agreements") or does not constitute any part of SAP Agreements.
SAP assumes no responsibility for errors or omissions in this material. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material.
These pages are provided without a warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.
This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected.
SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages or their content.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations.
Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of the publication date, and they should not be relied upon in making purchasing decisions.
Standard Scenario I - On Premise
- Easy to implement - a single optional SAProuter installation and a central SAProuter configuration.
- Standard industry security level for customers.
Standard Scenario II - On Premise
- More effort during implementation and configuration as each installation has a dedicated SAProuter installation and SAProuter configuration.
Advanced security level due to isolated environments for each installation with high security regulations.
Enhanced Scenario - PMC
Enhanced setup for Cloud providers, which reflects the special needs and requirements in this market leveraging the advantages of onPremise scenario II.
Increased number of supported SAProuters parallel (<25).
Partner in charge of system data maintenance.
Tips for SAP Solution Manager Set up in PMC model
One central SAP Solution Manager that grants access only to PMC partner operators (#3 in the illustration)
can be used with the precondition that all the information of connected customers are visible to the operators.
Operators can distinguish data by customers.
- For the Incident Management (Helpdek) function, partners can grant their customers to access the SAP Solution Manager, while ensuring the data segregation.
Refer to the ITSM Set Up Guideline for configuration tips.
Individual SAP Solution Manager for each customer (#1 & #2) is mandatory to grant access for customers in order to use all functions.
KBA , XX-SER-NET , Network connection , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.