Solution Manager 7.1 SLD working as SLD Runtime Backup?

[Former Member]

Hi,

I'm working on a landscape design, and I would like to have some critics and answers to my questions on the bottom of the topic.

This landscape have for each DEV, QAS and PRD:

- Application Server as ABAP

- Portal as Java

At this moment, DEV, QAS and PRD have it own isolated SLD.

This must support SAP NetWeaver Process Integration.

SLD Versions:

SLD DEV:

Namespace: sld/active
Model Version: 1.6.38
Content: SAP_CR 7.9 (produced 2012-03-06)

SLD QAS:

Namespace: sld/active
Model Version: 1.6.38
Content: SAP_CR 7.9 (produced 2012-03-06)

SLD PRD:

Namespace: sld/active
Model Version: 1.6.38
Content: SAP_CR 7.9 (produced 2012-03-06)

SLD SOLMAN:

Namespace: sld/active

Model Version: 1.6.41

Content: SAP_CR 10.12 (produced 04/01/2015)

Other Software Versions:

Application Server as ABAP: (SAP ECC SERVER) EHP 7 For SAP ERP 6.0

Portal as Java: (Enterprise Portal) SAP Netweaver 7.4

Solution Manager: Solution Manager 7.1

I have read the manual at:

I think my design follows the Unique path principle .

Questions:
1- Should this design work?

2- Can I use Solman local SLD as a backup from central SLD(PRD) and source of information to LMDB?

3- Can this design support Sap NetWeaver Process Integration?

4- Are my SLD's Versions compatibles with the design?

5- To have a bi-directional link between 2 SLD's they must be at the same version?

6- What can go wrong if I update all SLD's Versions to the latest?

7- Give me your opinion about this design.

8- Do I need to gather more information to do this?

Waiting for your help!

Thanks,

André Pinto

[mamartins · Accepted solution]

Hi Andre,

I have a similar landscape on my side.

All my DEV (ABAP, JAVA and DualStack) systems write to the DEV PI SLD.

All my QUA systems write to the QUA PI SLD.

All my PROD systems write to the PROD PI SLD.

Then the DEV PI SLD is configured to forward to QUA, and this one is forwarding to PROD and PROD is configured to forward to the SolMan SLD. This solution is valid with one drawback, you can't natively use the SOLMAN PI monitoring capabilities. But there is an alternative: http://service.sap.com/sap/support/notes/1631346

We choose this configuration because our PI SLD is very critical to us, and we don't want to mess with it.

You SLD versions are compatible but should be updated, because their versions are pretty old.

They should be on same version to communicate bi-directionally.

Do you already checked this blog: ?

Regards.

MM

[Former Member · Accepted solution]

Hi Manuel Martins,

Manuel Martins wrote:

Hi Andre,

I have a similar landscape on my side.

All my DEV (ABAP, JAVA and DualStack) systems write to the DEV PI SLD.

All my QUA systems write to the QUA PI SLD.

All my PROD systems write to the PROD PI SLD.

Then the DEV PI SLD is configured to forward to QUA, and this one is forwarding to PROD and PROD is configured to forward to the SolMan SLD. This solution is valid with one drawback, you can't natively use the SOLMAN PI monitoring capabilities. But there is an alternative: http://service.sap.com/sap/support/notes/1631346

Thank you for this Note, it was very informative and helpful!

 You SLD versions are compatible but should be updated, because their versions are pretty old.

I know it, and it will be updated!

They should be on same version to communicate bi-directionally.

Ok, i will make it updated to the same version.

Do you already checked this blog: SCN blogs and docs on SLD and LMDB?


Regards.
MM

Yes, I already checked it, and read some stuf from there, but before e start the changes i want to know for sure that what i'm doing is correct, so i dont make a mistake!

Thank you for your answer Manuel Martins