#sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1
Many questions have created lately on forum Solution Manager surrounding the LMDB, MOPZ, SMSY, Product System and etc on SOLMAN 7.1. Therefore, I took the initiative and decided to write my first blog in my life so far, on how to assign Product System in SOLMAN 7.1 and how LMDB, SLD, SMSY and Landscape Verification work inter-related in SOLMAN7.1, to share with our fellow #sapadmin, as this is the important first step in order to proceed to utilize and operate most of the SOLMAN functionalities such as MOPZ, EWA, Diagnostics Configuration and etc. We can’t proceed further if stuck here.
http://wiki.sdn.sap.com/wiki/display/SMSETUP/Maintenance+of+Product+in+the+System+Landscape talk about product version and product instance information need to be maintained manually for all technical system running on Netweaver prior to 7.02 but the wiki didn’t provide any guide on how to assigned, get it visible and working.
LMDB technology was brought into SOLMAN 7.1, works inter-related with SMSY, SLD and even Landscape Verification step a leg in, which complicate the effort to maintain your company system landscape.
In our scenario, BJP is our BI-JAVA. We’ve fetched the system information to SLD, and entry appeared in SMSY once SLD has sync it with LMDB ( when periodic job SAP_LMDB_LDB_0000000001 completed, which runs on every 10 minutes)
In SMSY, if your perform a search, you’ll see BJP appears in Databases and Technical Systems but not Product Systems.
*BJP is used as example here.
Now we need to go assign Product System to BJP. Highlight BJP and right click -> change and below screen will prompt out. Click on “check” button and it’ll bring you to Technical System Editor.
You can change your landscape pattern here – either as HUB or SIDECAR.
As you can see, Product Versions and Product Systems tab is empty.
Next you need to go to Software and assigned Product Instances by clicking the Add button:
Navigate to “Proposals fitting to SCs” tab and add the correct product instance carefully, else it’ll lead to inconsistency and issues in MOPZ and Diagnostics configuration, when you don’t want to spend and waste time troubleshooting later.
Select the correct Product instance and click “Add”:
Next, go to “Proposals fitting to unassigned SCs” to check if there’s any software components, eg: Add-On and etc which doesn’t fit into the Product Instance Selected. Read the “Note” and “What to do” on how to fit those software components in.
What you’ll see when Product Instance is added:
Here, you need to ensure relevant software components has the “Product Assigned”
Save your entry and go back to the main screen, and product Version assigned.
How about “Product System”? We don’t find any feature to add in the product system. And there’s no information on any notes nor guides that talk about this explicitly. As product system is important to MOPZ and Diagnostic Configuration, we can’t proceed further without product system assigned for our Instance.
How about try our luck in Managed System Configuration?
When you click on “Display Product Systems”, it just bring you back to SMSY, and still we can’t find the feature to add “Product System”.
Don’t worry, trick to assign “Product System” is in Landscape Verification Tool. Click on “Goto Landscape Verification Tool” or go to transaction code LVSM. Click “Yes” for data synchronization and wait for it to complete, alternative, you can go to transaction code LVSM_LOAD to check the status.
Next, you need to manually create “Product System” as you won’t find “BJP” here:
Click “Add Product Systems”
*Please pay attention to the Product Selected, otherwise, you’ll have problem generate STACK XML for EHP upgrade and maintenance. Many questions had raised in Solution Manager Forum surrounding this topic.
Always select the base as main product, for example:
For ERP EHP1, 2 or 5, select Product SAP ERP
For NW7 EHP1, or 2, select Product SAP NETWEAVER
For SCM7 EHP1, select Product SAP SCM7 and etc………
Click Next and assign “BJP” as technical system.
Select the relevant Product Instance. Bear in mind that you can only select ONE Product Instance here! Otherwise you’ll hit into error and fails to save.
Next and Finish.
Remember to “SAVE” your configuration. Click the SAVE button.
You will see “BJP” now:
Go to SMSY and search for “BJP” and you’ll see Product Version is assigned and you are free to maintain additional Product Versions or Product Instance if relevant.
I hope this blog will help #sapadmin who encounters problem and unclear about SOLMAN7.1 Landscape Management technology. I’ve spent long hour and greased my elbow to get this working just for MOPZ usage for my upgrade. Previously, generate Stack XML in SOLMAN version<7.1 took me few minutes, but not longer simple in SOLMAN 7.1. To ensure a smooth operation in near future, i strongly advise your SOLMAN7.1 is patched to latest support packages, apply the master note and ensure system preparation, basic configuration are performed and completed successfully. Also, update your SAP CIM and SAP CR contents to latest level available, or at minimum 1.6.16 for CIM before SLD -> LMDB synchorization.
Refer to Note 669669 – Updating the SAP Component Repository in the SLD on how to update.