Show TOC

Procedure documentationManaging Non-SAP Product Descriptions

 

A non-SAP product in the system landscape is either developed by a customer ("customer product") or by a company other than SAP ("third-party product"). Non-SAP products often do not have an entry in the SAP software catalog and are therefore not part of the SAP CR content. They can be deployed in SAP runtimes, like AS ABAP or AS Java, or in non-SAP runtimes, like IBM WebSphere.

Products that were not developed by SAP but that are described in the SAP Software Catalog ("partner products") are not classified as non-SAP products, in this context.

Non-SAP product descriptions are created in the system landscape directory (SLD) and are synchronized to the landscape management database (LMDB), automatically.

Note Note

To register third-party systems in the SLD, see SAP Note 1781479Information published on SAP site and the guide Registering Third-Party Systems in the System Landscape Directory (SLD) at https://scn.sap.com/docs/DOC-22740Information published on SAP site.

End of the note.

Procedure

Creating New Non-SAP Product Descriptions
  1. Go to the home page of your SLD and select the CIM namespace that was selected as source for the SAP CR content in SAP Solution Manager. You can check the source in transaction SOLMAN_SETUP, under Start of the navigation path Mandatory Configuration Next navigation step Infrastructure Preparation Next navigation step Set Up Landscape Management Next navigation step LMDB Synchronization End of the navigation path.

  2. Choose Products.

  3. Choose New and follow the guided activity.

    • For later use in SAP Solution Manager, the product name must be unique. Do not create products with the same name, even if they have different vendors.

    • Enter the same value for the product vendor for all your products. Choose an internet domain that belongs to your company.

    • The product version must be unique for each product.

Deleting Non-SAP Product Descriptions

You can delete non-SAP product descriptions in the SLD. This deletion is propagated to the LMDB.

More Information

SAP Note 1774444Information published on SAP site.