Skip to Content
0
Former Member
Jan 25, 2013 at 01:40 PM

SAPCC3.0 not registered in the SLD

33 Views

Hi all,

I've recently installed SAPCC3.0 SP07. During the installation process, I pointed to the SLD that my organization is using, where I had successfully added ABAP (ERP and CRM) an Java instances (CRM) a few days before. I entered the information in the installation process of both my CORE server (S05) and BART server (S06), but after completing the installation I cannot find anything in the SLD:

I've double-checked the configuration guide to ensure that all the parameters required in both CORE and BART servers are correct. Indeed, in the dispatcher log file I see the following:

2013-01-25 00:55:00.007 - [170.251.121.169*]dispatcher#1 - INFORM - [SCHED_SLEEPING] - Refresh scheduler will wake up on 1/25/13 1:00 AM.

2013-01-25 00:55:37.984 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Waiting instance bulkLoader#1 (Socket[addr=/170.251.121.169,port=56504,localport=2100]) is stoppe

d.

2013-01-25 00:56:47.402 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Waiting instance bulkLoader#1 (Socket[addr=/170.251.121.169,port=54349,localport=2100]) is stoppe

d.

2013-01-25 00:57:56.555 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Waiting instance bulkLoader#1 (Socket[addr=/170.251.121.169,port=29992,localport=2100]) is stoppe

d.

2013-01-25 00:59:05.585 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Waiting instance bulkLoader#1 (Socket[addr=/170.251.121.169,port=18275,localport=2100]) is stoppe

d.

2013-01-25 01:00:00.004 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Sending info to SLD.

2013-01-25 01:00:00.005 - [170.251.121.169*]dispatcher#1 - WARN - [tracing] - Unable to refresh instance bulkLoader#1

2013-01-25 01:00:00.005 - [170.251.121.169*]dispatcher#1 - INFORM - [SCHED_SLEEPING] - Refresh scheduler will wake up on 1/25/13 1:05 AM.

2013-01-25 01:00:00.220 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - SLD updated.

2013-01-25 01:00:00.220 - [170.251.121.169*]dispatcher#1 - INFORM - [SCHED_SLEEPING] - SLD Update scheduler will wake up on 1/26/13 1:00 AM.

I've also modified the config of the dispatched by means of the Admin+ Tool to trigger the update again and update the SLD CR as per note 669669; according to the log everything works fine, but I don't see the system in the SLD either:

2013-01-25 06:10:00.015 - [170.251.121.169*]dispatcher#1 - INFORM - [SCHED_SLEEPING] - Refresh scheduler will wake up on 1/25/13 6:15 AM.

2013-01-25 06:10:00.042 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - Sending info to SLD.

2013-01-25 06:10:00.339 - [170.251.121.169*]dispatcher#1 - INFORM - [tracing] - SLD updated.

2013-01-25 06:10:00.339 - [170.251.121.169*]dispatcher#1 - INFORM - [SCHED_SLEEPING] - SLD Update scheduler will wake up on 1/26/13 6:10 AM.

I'm checking the log file of the SLD server but I don't know if there is any filter component to look for. If I look for SAPCC3.0 in the SLD server I don't see any installed system either. Needlees to say that I cannot see it in SOLMAN either (SMSY analysis where used for Product SAPCC3.0 states that the product is not used).

I'm working with SOLMAN 7.1 SP04, and the SLD version is

SLD Version: 7.0209.20110628100657.0000
Build: 20110721 1556, Depot: //sdt/com.sap.lcr/NW702_09_REL, Changelist: 116098

Other data:

Model Version (sld/active): 1.6.34 SAP CR Content Version (sld/active): SAP_CR 8.9 (produced 01/07/2013) Namespace Model Version Classes Instances Associations Total Objects sld/active 1.6.34 1125 138691 352561 492377

Best regards. Raúl.