Before You Start: Important Information

To modify the Knowledge Management standard delivery to your business requirements, you can use the open configuration framework, which is available for administrators in the portal in the form of a configuration iView.

Always make all significant settings in the configuration in the customer namespace or customer area.

This restriction has the following objectives:

• Avoiding negative impact on standard or system functions
• Preventing undesired impact on performance and stability
• Preventing malfunctions during system upgrades and when using standard functions
• Secure transfer of customer-specific configurations and changes during updates or when switching to another version
• Protection and retention of existing data

Therefore, you create your own repository managers, user interface elements, and so on and generate new instances of services, if this is technically possible.

 

You must bear in mind that some changes to the configuration can damage or significantly affect the entire functioning and stability of the system. These types of changes to the standard system can result in support no longer being possible because in certain circumstances, some settings cannot be undone without causing data loss.

However, it may be necessary to change SAP standard configuration objects in cases where the configuration framework does not permit additional configuration objects or where it makes no sense from a technical perspective.

Significant changes that affect configuration objects in the SAP standard system and that have serious impact on their function are not permitted. For example, you are not allowed to change the persistence mode of a CM repository manager. This type of change would lead to data loss.

In general, when making changes, you should consider carefully whether you can undo them again, independent of whether you change delivered configuration objects or customer configuration objects.

 

You are not allowed to use standard system repositories and their folders to store customer-specific content. The reasons for this include:

• SAP standard repositories contain important system data and support major system functions.
• In contrast to the default configurations, you can optimize the configuration of customer-specific repositories according to your specific business requirements. The assigned repository services, the persistence mode, the caches, and so on can influence performance in customer-specific repositories.
• It is easier to monitor the size and functioning of the repositories.
• It is easier to integrate the required security aspects in the security concept.

For these reasons, we strongly recommend creating customer-specific repositories for customer content.