Dev. configuration not syncing with SLD

[Former Member]

Hello,

we are using NWDI 7.3 and have defined development configurations in CM Services. Currently we are going to upgrade our systems from NW 7.3 to NW 7.3 Ehp1, so we created new versions of our Software Components in SLD and defined 7.31 dependencies for them. Then we created a new development configuration with these new versions of Software Components. Since then we have a problem - when we update the dependencies of these new SCs in SLD and use "Check SCs" and "Update development configuration" functionality from the CM Services on our new track, it discovers the inconsistency between SLD and the development track and it looks like the development configuration is updated, but it is not - repeated check discovers the same inconsistencies. We have found a workaround - removing all SCs from our new development configuration and adding them back resolves the changed dependencies. But still, the development configuration can't be updated in the normal way.

Strange thing is that the old development configuration we used for 7.3 development doesn't suffer from this error - it is possible to update it through "Check SCs" and "Update development configuration" functionality.

Can you please advise on this problem?

Thank you and best regards,

Tomas Hansut

[ErvinSzolke]

Hello Tomas,

What dependencies did you define for 7.31 initially?

What dependencies did you add which were not updated during update development configuration ?

Can you send some step-by-step screenshots about how you proceed ?

@Pramod I am not sure this is about outdated SLD content therefore imho 669669 won't help here.

Thank you and Regards,

Ervin

[pramod_gopisetty1]

Hi Ervin,

Thanks for correcting.

I was thinking after CR content is updated the Track is not been updated.

I may be wrong.

Thanks,

Pramod

[Former Member]

Dear Ervin,

here is what we did:

1.    In SLD we created

a.    component COMMON 2.0 with build time dependencies:

Prerequisite Software Component Versions

FRAMEWORK EXTENSIONS 7.31, BPEM BASIS 7.31 , EP BUILD TOOL 7.31 , ENGINEAPI 7.31 , DI BUILD TOOL 7.31 , MMR SERVER 7.31 , ESMP BUILD TOOL 7.31 , BPEM FACADE 7.31 , MOIN BUILD TOOL 7.31 , EP RUNTIME 7.31 , SEA CORE 7.31 , DATA MAPPING 7.31 , SEA FACADE 7.31 , ESI - WSRM 7.31 , CU BASE JAVA 7.31  ,SEA UI 7.31  ,VOICE KIT VISUAL COMPOSER 7.31 , XI ADAPTER FRAMEWORK 7.31 , PORTAL BASIS API 7.31 , BPEM CONTENT 7.31 , COMPOSITION BUILD TOOL 7.31 , BPEM COLLABORATION 7.31 , VISUAL COMPOSER FRAMEWORK 7.31 , GUIDED PROCEDURES CORE 7.31 , WEB DYNPRO EXTENSIONS 7.31 , PORTAL BASIS 7.31 , ESCONF BUILD TOOL 7.31 , BRMS , BUILD TOOL 7.31 , SAP CAF 7.31 , JAVA FRAMEWORK OFFLINE 7.31 , ECM CORE COMPONENTS 7.31 , SERVICE COMPOSITION 7.31 , TEST_UTILS 1.0 of fs.sk , CAF MF 7.31 , BPEM METAMODEL BASIC LIB 7.31 , BPEM BUILDT 7.31 , VISUAL_PATTERN BUILD TOOL 7.31 , UWL COLL PROCESS ENGINE 7.31 , BRMS FACADE 7.31 , CU BASE WEB DYNPRO 7.31 , J2EE ENGINE FRAMEWORK 7.31 , WEB DYNPRO RUNTIME 7.31 , J2EE ENGINE SERVERCORE 7.31 , J2EE  ,ENGINE FACADE 7.31 , VC FREESTYLE KIT 7.31 , EP MODELING 7.31 , FORMS INFRASTRUCTURE 7.31

b.    component SECOND with build time dependencies:

Prerequisite Software Component Versions

DI BUILD TOOL 7.31 , COMMON 2.0 , ESCONF BUILD TOOL 7.31 , MOIN BUILD TOOL 7.31 , ENGINEAPI 7.31 , JAVA FRAMEWORK OFFLINE 7.31 , WEB DYNPRO RUNTIME 7.31 , COMPOSITION BUILD TOOL 7.31 , J2EE , ENGINE FACADE 7.31 , ESI - WSRM 7.31

2.    In CM services we created new Development configuration and we added above defined components. After “Check SC” everything is fine.

3.    Then in SLD we added an arbitrary dependency to COMMON 2.0 from 7.31

4.    In CM services: After “Check SC -> Repeat check” we are getting errors that Development configuration does not contain newly added dependency in COMMON and SECOND, so we “Update development configuration”. We are getting messages : “Software component updated successfully: Name COMMON 2.0, Software component updated successfully: Name SECOND ”. But after “Repeat check” the errors are still there. It does not help to repeat “Update development configuration”.

5.    Our workaround: In CM services: When we remove component SECOND from development configuration and then we “Check SC -> Repeat check” and “Update development configuration”, then it add new dependency to COMMON. Then we add component SECOND and everything is OK. However during the  next development this workaround will be still harder to execute.

Do you need more information?

Thank you and best regards,

Tomas Hansut

[ErvinSzolke]

Hello Tomas,

we attempted to reproduce this inhouse but so far we couldn't.

Could you please let me know:

- the version of component LM-CTS (go to http://<host>:<port>/nwa/sysinfo --> tab "Components" and copy-paste the whole line of LM-CTS.

- what dependencies have you define for SC 'TEST_UTILS 1.0 of fs.sk' ?

Thank you and Regards,

Ervin

[Former Member]

Dear Ervin,

we have 2 servers involved in this scenario. On the server where SLD is running, the line with version of LM-CTS component is following:

SAP AG

LM-CTS

sap.com

1000.7.30.3.0.20110522134400

The second server hosts DI and there we have this (different) version of LM-CTS component:

SAP AG

LM-CTS

sap.com

1000.7.30.4.0.20110801212600

The dependencies of SC TEST_UTILS 1.0 are:

JAVA FRAMEWORK OFFLINE 7.31

ENGINEAPI 7.31

DI BUILD TOOL 7.31

ESCONF BUILD TOOL 7.31

MOIN BUILD TOOL 7.31

WEB DYNPRO RUNTIME 7.31

ESI - WSRM 7.31

J2EE ENGINE FACADE 7.31

COMPOSITION BUILD TOOL 7.31

Thank you and best regards,

Tomas

[ErvinSzolke]

Hi Tomas,

could you please let me know whether this note helps?

#1714847 -- CM Services Add SC and Check SCs Help

It seems you have an older version of LM-CTS and raising it to >= 730 SP10 might help.

Thank you and Regards,

Ervin

[Former Member]

Dear Ervin,

if I read the note correctly, it is about having two active versions of software component in one development configuration. Well, that's not our case - we have some software components with multiple versions defined, but each of our development configurations contains max. one version of those software components. I hope I didn't miss anything else in that note.

Regarding raising version of LM-CTS - I will ask our admin for it, but it will probably take some time. I will let you know.

Thank you and best regards,

Tomas

[ErvinSzolke]

Hello Tomas,

ok, thank you for the feedback, please let me know once you raised the SP level of the LM-CTS.

Please also note that the SP stack cannot be inconsistent, so if you intend to raise the SP of LM-CTS to SP10 (or higher) then I strongly recommend you to raise the entire SP stack (i.e. all SCs that have release 7.30) to the same SP (in this example SP10). Else you might face major malfunctions.

Best Regards,

Ervin

[pramod_gopisetty1]

Hi Tomas,

I think when you are adding the 7.31 dependencies it is not able to recognize the components.

Before Upgrading you need to upgrade the CR Content, so that you can add the 7.31 dependencies.

1. Complete the post installation activities for SLD. Check your current CR Content and Model version.

2. Download the latest CR Content from Marketplace: service.sap.com/swdc->Download->Support Packages and Patches->Additional Components->SAP CR CONTENT->SAP CR CONTENT UP TO 2008->OS Ind->cimsap41508_0-10006428.zip (latest)

3. Logon to your SLD system with SLD Admin rights user ID

4. Goto Administration->CR Content->Import

5. Browse the cimsap41508_0-10006428.zip file and update CR Content.

6. Apply the CR delta package(s), based on your CR Content (step 1).

Please refer to note 669669 for further details on step 6.

Hope this helps.

Cheers-

Pramod

[Former Member]

Dear Pramod,

thank you for your answer. Our SLD Content is up to date.

Best regards,

Tomas Hansut