SLD Design and advice

[Former Member]

Hi All,

We are planning on introducing PO to our landscape and before we implement it, I want to make sure I have a solid SLD configuration.

I will post a drawing but I will add context to it here.

PO is NW 7.4

NWDI is NW 7.31

SOLMAN is NW 7.1 SP10

ERP is ECC 6 EHP 5

The SLD will be hosted on a dedicated AS Java instance. Same NW version as PO, 7.4

We also have Charm in the Landscape.

My goal is have a design time and runtime SLD. I do not want to sync the 2 SLD's. Charm requires the LMDB to sync to both SLD's.

I confirmed this can work: see figure 2: http://scn.sap.com/community/it-management/alm/blog/2013/01/10/sld-lmdb-topology-connections-valid-a...

This figure only shows 1 SOLMAN LMDB, not 2. I wonder if it makes a difference. My drawing has 2 SOLMANS.

Also for redundency of the SLD. How should I go about it?

Have a look at the diagram, give me your feedback. Sorry I have no visio.

[Former Member]

Just want to finish up what i started,

I believe I found the model we will implement.

On page 45 of the SLD Planning guide it shows the following.

So my drawing now looks like this...again sorry no visio just mspaint.

[Former Member]

Hi Joshua,

have you successfully configured your SLD as per the plan in above screen shot or have you deviated from it ? if you have configured is it fit for purpose.

Regards

Raj

[Former Member]

Hi--

DO you know that you will face an issue when you will configure the transport tab for you P QA and Prod?

Since PI Must have the higher release you will end up stuck with Solamn later since you don't need to keep SolMan at the last release/Patch.

So PI Prod SLD much be the Master SLD while you are configuring the Sync bridges. Here is the path: PI SLD Design ->PI SLD Prod-> Solman SLD Prod -> SolMan SLD Test.

Cheers

F

[Former Member]

I'm under the understanding that, as of Solman 7.1, you do not need an SLD locally anymore.

Here are some statements pulled from the SLD Admin guide.

Release 7.1 of the SAP Solution Manager introduces the Landscape Management Database (LMDB). The LMDB is the central tool to handle landscape data in the SAP Solution Manager. The LMDB retrieves data from the SLD by full automatic synchronization, which works exactly as described above (see 3.3.2.1 Full Automatic Synchronization [page 20]). The content retrieved includes all SLD data (

CIM/CR Content, technical systems’ data, and manually created data such as business systems, manually created products, software components, etc.).

Note

: The use of the local SLD of the SAP Solution Manager 7.1 is optional. If you are not using SLD data productively in your landscape (typical applications making such use being SAP NetWeaver Process Integration or Web Dynpro Java based applications) and therefore no other SLD is available in the landscape, the local SLD of the SAP Solution Manager can be activated as a target for data suppliers. In that case, data suppliers address the SLD available on the SAP Solution Manager. This is then used as a source for the LMDB. (Using the Solution Manager SLD in such a case is part of the recommendations for SAP Solution Manager 7.0.)

[bxiv]

Good stuff to know SLD isn't a requirement, odd that is a recommended step in the setup though .  Something to consider with your design:

Setup SLD on SolMan and have your various SLD systems send updates to that SLD and point your LMDB only at itself thus providing a kind of choke point and less configuration in your solman_setup

-Or-

Setup Solman's LMDB to point to multiple SLDs pulling data, at which point you will need to manually control the prioities of the syncs or your landscape data within SolMan becomes inconsistent/strange.  If you or a co-worker forgets to set this up, you could have an SLD sync that changes data in the LMDB and invalidate some items or worse yet perhaps the LMDB syncs something to your SLD environment and creates inconsistencies in your central SLD.

Personal opinion I would leverage SolMan's SLD for the technical information you are looking for as majority of the SLD information isn't needed for a lot of your solman functionality.

[Former Member]

Billy,

You are correct, during solman_setup, you do need to connect to a SLD but it doesn't need to be local.

You can input a URL to a central SLD there and username/password to connect.

Now i'm told they want EWA also on top of CHARM and PO.

More design work

[Former Member]

[bxiv]

Figure 3 in the link you have shows 2 LMDBs; is your landscape for PI/SLD setup different from that?

Also SolMan 7.1 SP10 is really a Netweaver 7.02 stack, so keep that in mind as its SLD is not going to be like that of NWDI or PO.

In my landscape we don't have SLD talking directly to the LMDB (not even sure that is possible), SLDs and LMDB(s) will/can sync but the two technologies don't talk directly.  SolMan typically runs a job that syncs its SLD information to the LMDB.

[Former Member]

Thanks for replying Bill.

You are right, LMDB does not sync to SLD, It simply has a job that runs each 10 mins to fetch Data.

In my drawing, I represented that by the red arrows.

Also, In both SOLMAN's, I have no local SLD. So this cancels out the issue of NW 7.02 to the PO NW 7.4 SLD.

Personaly I see no isse with having an SLD on my SOLMAN's,

I want to seperate my dev/qa from my PRD. Hence the 2 SLD's, I do not want them syching either.

But because we are going to use CHARM, I need LMDB to be aware of both SLD's.

I've never configured 1 LMDB to pull data from 2 SLD's.

The document say's it can, but I can't find configuration anywhere.

[bxiv]

Part of Solman_setup is the creation of the SLD locally on the system it is step 6.1 of System Prep. so I'm not 100% sure how your SolMan is working properly without it (EWA and system readiness I would think this is flagged)?

I think the section you are looking for is this part of SolMan: