Skip to end of metadata
Go to start of metadata
1 Purpose

The purpose of this page is to clarify the Content Management (CM) systems, and settings and fix some misconfigurations.

2 Overview

During incident solving process I came across many incidents, where the cause of the issue was a wrong CM setting in the system, and the issue was solved by making the CM system clean from errors.

In this document I will describe the possible misconfigurations and what to check when you see some errors in the Knowledge Managmement (KM) Monitoring.

3 KM Landscape 

Firstly you need to make sure, that you have only valid CM systems in KM configuration.

3.1 How to check what are your valid CM systems?

3.1.1 NW 7.3 and upwards:

Go to NetWeaver Administrator (NWA) (http://<portal url>:<port>/nwa -> Configuration -> Infrastructure -> System Information).

Here you can see how many instances and nodes you have in the system, and you have to set the CM systems according to it.

If you have an instance number ID xxxx and the instance have y nodes, then your CM systems are xxxx50, xxxx51, ..., xxxx5(y-1).

This means the followings:

  • if the instance has only 1 node, then the CM system is xxxx50.
  • if the instance has 5 nodes, then the CM Systems are as follows: xxxx50, xxxx51, xxxx52, xxxx53, xxxx54.

Here is an example:

You can see in NWA, that we have 1 instance in our system with ID 25911, which has 4 nodes.

In this case we have 4 CM systems: 2591150, 2591151, 2591152, 2591153.

 

Of course, you can have more instances, and these instances can have also 1 ore more nodes. In this case use the previous example for all the instances.

Then you will know, what are the valid CM systems in your landscape.

 

3.1.2 NW 7.0x, 7.1x, 7.2x:

Go to NWA (http://<portal url>:<port>/nwa -> System Management -> Configuration -> System Properties).

Here you can see the instances you have, and also how many servers you have for each instances.

In this case the server ID numbers of each instances will be the valid CM systems.

Here is an example:

In this case we have 1 instance in the system (ID 149697), and this instance has 2 server nodes (ID 14969750, 14969751).

So we have 2 valid CM systems in our landscape: 14969750 and 14969751.

3.2 How to check if you have only the valid CM systems in your landscape?

You can check in 2 places, if you have only valid CM systems, and if you have all the valid CM systems in your landscape.

  1. You can see the CM systems in the following location:

    Go to KM Monitor (http://<portal url>:<port>/irj/portal -> System Administration -> Monitoring -> Knowledge Management-> Component Monitor -> Services -> Scheduler) 

    Here is an example:



    As in our previous 7.3 NWA example, we had 1 instance with 4 server nodes, i.e. we had 4 CM systems: 2591150, 2591151, 2591152, 2591153.
     
  2. You can see and set the CM systems in the following location:

    Go to System Landscape definitions (http://<portal url>:<port>/irj/portal -> System Administration -> System Configuration -> Knowledge Management -> Content Management -> Global services -> System Landscape definitions -> Systems -> Content Management System).

    Here you can see the CM systems, that are set in your landscape.
    If you did a system copy, or changed your landscape, it can happen, that you can see here invalid CM systems (that doesn't exist in NWA), and also it can happen, that you cannot see some valid CM systems, that exists in NWA.
    You need to remove the non valid CM systems, and add the valid CM systems, that you can not find here, to have only the valid CM systems in your landscape.
    (! Note: you need to ensure first that no scheduler tasks are assigned to the invalid CM systems, before you delete it, otherwise you won't be able to delete it.
                 Please see section 4.1)

    Here is an example:

     
     

4 KM Monitor Errors

In KM Monitor you can see some errors, that is caused by misconfiguration of the CM system, and after fixing these, some other issues are also fixed, so it is necessary to fix these errors.
For KM Monitoring use the following location: System Administration -> Monitoring -> Knowledge Management -> Component Monitor 
Please check also the SAP Note
949450 - Knowledge Management Component Monitor 

4.1 No task to an invalid CM system

If a scheduler task is assigned to an invalid CM system, then this task won't run.

Please make sure, if you still have an invalid CM system, then there is no task assigned to it.
Go to KM Monitoring -> Services -> Scheduler, and check every invalid server nodes, if there are some tasks assigned to it.
If so, you can delete it in Scheduler Tasks (System Administration -> System Configuration -> Knowledge Management -> Content Management - Global Services -> Scheduler Tasks)
It is necessary to do it also e.g. before you want to delete the invalid CM system

Here is an example:

In our system we have some invalid CM systems, e.g. 703580753 is an invalid CM system, and one task is assigned to it, the DailySubscriptions:

Now we need to remove it from Scheduler Tasks:

We need to deselect the CM System that is selected, and then click on "Apply". The changes will take effect immediately.

4.2 One task to one CM system

If a scheduler task is assigned to more CM systems, then this task will not run correctly.

Assigning a task to multiple nodes actually increases the load as the nodes to not 'share' the load of the task. Instead, the task would be run multiple times simultaneously creating a greater load on the system. The load on each node the task is assigned to will be exactly the same as if it was only assigned to that specific node.

You need to make sure, that one scheduler task is assigned to only one valid CM system.

If you wish to spread the load across several nodes, there's no problem with that. If you have a clustered system, you can assign some tasks to one node and the other tasks to another node, or you can also assign all the scheduler tasks to one valid CM System. The important part is that no task is assigned to more than one CM system.

Please go to KM Monitoring -> Services -> Scheduler, and check every server node what tasks are assigned to them. If one task is assigned to more systems, you need to make changes.
You can also check and do the changes in Scheduler tasks (System Administration -> System Configuration -> Knowledge Management -> Content Management - Global Services -> Scheduler Tasks)

Here is an example:

After deselecting the CM systems, you need to make sure, that only one valid CM system is selected, then click on "Apply". The changes will take effect immediately.

4.3 All tasks to a CM system

In KM Monitoring -> Services -> Scheduler you can see the following errors:

"Configuration Error: No CM system assigned to this task"

You have to assign a valid CM system to every scheduler task, if you have a clustered system.
To do the changes you need to go to Scheduler tasks (System Administration -> System Configuration -> Knowledge Management -> Content Management - Global Services -> Scheduler Tasks).
Please refer to SAP Note 798633 - Tasks: Component Monitor shows startup failed. 

5 Clustered system setting

If you have a clustered system, you need to set it in System Landscape Service (System Administration -> System Configuration -> Knowledge Management -> Content Management - Global Services -> Show advanced Options -> System Landscape Service):

The "Active" parameter should be always seleted.
If you have a clustered system, the "Clustered Installation" option should be selected. 

6 Accessstatistic service - performance problems, lock issues

Please check the accessstatistic service in your system and remove it from the repository managers where you don't need it, as it can cause lock issues and performance problems.

Please refer to SAP Note 1025290 - CM Repository Service ' accessstatistic' 

7 Host parameter

Please also check, that the Host parameter is correct in the URL Generator Service.
The URL Generator service is found under : System Administration > System Configuration > KM > CM > Global services > URL Generator Service ( found under “Advanced Options”) (Please use FQDN - fully qualified domain name,  like http://<host>:<port> or https://<host>:<port> 
SAP Documentation:
https://help.sap.com/saphelp_nw73/helpdata/en/7d/236cfa17034a37a439dc392ec59eb0/frameset.htm
Knowledge Management (KM) -> Administering the KM System -> Basic Configuration for KM -> Wizard-Based Basic Configuration for KM -> Specify the Portal URL
Knowledge Management (KM) -> System Administration -> System Configuration -> KM Configuration -> Global Services -> URL Generator Service

 

If you make any changes, please restart the J2EE engine (if you have a clustered system, please restart the whole cluster).

Related Content

Related Documents

NW 7.0x - System Landscape Administration with SAP NetWeaver Administrator - Viewing System Properties
NW 7.3 - SAP NetWeaver Administrator - Working with System Information

NW 7.0x - Knowledge Management
NW 7.0x - Knowledge Management - Component Monitor
NW 7.0x - Knowledge Management - Scheduler Tasks
NW 7.0x - Knowledge Management - System Landscape Service 
NW 7.0x - Knowledge Management - System Landscape Definitions
NW 7.0x - Minimal Configuration for Knowledge Management 

NW 7.3 - Knowledge Management
NW 7.3 - Knowledge Management - Component Monitor
NW 7.3 - Knowledge Management - Scheduler Tasks
NW 7.3 - Knowledge Management - System Landscape Service 
NW 7.3 - Knowledge Management - System Landscape Definitions   

Related SAP Notes/KBAs

SAP Note 798633 - Tasks: Component Monitor shows startup failed

 SAP Note 949450 - Knowledge Management Component Monitor

__________________________________________________________________________________________________________

 

  • No labels