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: System Landscape Directory: Planning Guide
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