Skip to Content

Introduction

KM Folders are utilized as the base platform in which KM Documents are stored. For example through KM End-Users can access, obtain, manage and review data information through documents sourced from the business intranets, external WWW feeds, and file servers. The KM Documents themselves are presented in the standard formats of PPT, excel, word documents and html.

KM – Hot Deployment References

A common occurrence with KM (Knowledge Management) problematic based scenarios can often be traced to Hot-Deployment occurrences especially when we are dealing with configuration setups. Hot Deployment references can be encountered in the form of exception highlights within default trace files or also lead to on-screen graphically represented errors. Such occurrences are often associated with recent upgrades, migrations and system restarts involving component configuration changes.

As the name hot-deployment might suggest this process refers to an abrupt & quick means of transferring underlying KM/KMC Code within a KM Service Landscape. The catch with Hot-Deployment is that such a process involving the code does not require the end-user or system admin to perform a restart of the corresponding container base. To elaborate further on this point if we take the Enterprise Portal as the backdrop we know that such an environment consists of multiple core component areas. From solely the perspective of KMC, hot-deployment means you are able to redeploy KMC Components freely without touching the corresponding Portal Components which provide the platform base on which KM runs.

The major point of highlight surrounding Hot-Deployment is that such an action is NOT supported, encouraged or recommended as it can lead to a wide array of different issues. If you come across hot-deployment references within the default trace files you’re findings will be identical or similar to the sample exception outlined below:

  • #0-500#Error#com.sapportals.wcm.crt.CrtClassLoaderRegistry# #EP-KM-FWK-RF#sap.com/com.sap.netweaver.bc.crt##sap.com/com.sap.nw.r#com.sapportals.wcm.crt.CrtClassLoaderRegistry[HT T P Worker ,5,Dedicated_Application_Thread]#Plain.Stacktrace of classloader registration attempt. [EXCEPTION] java.lang.Exception #0-500#Error#com.sapportals.wcm.crt.CrtClassLoaderRegistry#
  • SAP Note: 894884 – Hot-deployment of KMC components – Clarification
  • KMC – Hot Deployment Checker: http://wiki.scn.sap.com/wiki/display/KMC/KMC+-+Hot+Deployment+Checker

In order to resolve hot-deployment you will need to proceed to restart the J2EE engine in order to clear the hot deployment and then subsequently check if KM is accessible.

KM: Performance is Slow

 

KM Performance Overview: Is it slow?

The first recommendation with any performance related issue is to check for visible errors or exceptions being thrown in the default trace error log files. With performance issues some core checks to assess include:

  • Have there been system changes recently e.g. upgrades which may have prompted this issue to begin occurring?
  • If so Post upgrade did you clear the portal caches/restart the portal service?
  • Is this issue occurring for all users/in all web browser platform types?Are customization’s/personalizations currently in place?

KM: Performance Specifics

The primary cause of performance impacts within the KMC is the activation of the AccessStatistic service on the KM repositories.

  • Check if the service is indeed activated in the configuration of the KM repository managers.

If so, we advise removing it wherever possible as it the recommendation in SAP Note 1025290.

After the configuration of these repository managers is updated with the removal of the AccessStatistic service a system restart will be required for the change to take effect.

After this, perform a retest to see if performance improves.

You can find additional information in the documentation outlined below:

KM: Tracing an Issue

If you are asked to collect trace info (Information) for a Knowledge Management (KM) WebDAV or a Portal Drive Scenario there are a few steps which you can follow.

SAP KBA: 2147813 – Trace Information for KM WebDAV or Portal Drive

KM: Component Monitor 

You can use the component monitor to identify wrongly configured objects of the following components of the KM platform.

· Filters

· Repository managers

· Repository services

· Global services

The status of an object is displayed in the form of a colored symbol. The color helps you to identify whether an object is wrongly configured. A message text helps you to find the error and correct the configuration of the object.

  • To call up the component monitor, choose System Administration > Monitoring > Knowledge Management > Component Monitor.

If a component has objects that are either wrongly configured or that couldn’t be started, a yellow or red symbol is already displayed in the tree view. Open the components affected, and read the error messages for any objects with errors. You correct errors by calling up the configuration of the object (for example, repository manager) and correcting the errors there.

 

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply