Hi All,

There is a requirement where I need to set up a BPMon monitor over Purchase order created with a certain header status eg status "98". I tried to find a monitor in the PPT that details the list on monitors. Could not find it. Can this be done.

Regards,

Ashutosh

Hi expert,

I got another error in start instance phase. Could you please help me to fix this error?

TRACE      2013-08-28 10:13:48.85 [iaxxclib.cpp:161]

           CLib::load()

Opened sylib722.dll

TRACE      2013-08-28 10:13:48.085

exe dir is C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020

INFO       2013-08-28 10:13:48.101 [synxcpath.cpp:798]

           CSyPath::createFile() lib=syslib module=syslib

Creating file C:\Users\Administrator\AppData\Local\Temp\sapinst_exe.3016.1377656020\dev_sap_kernel_test_28_Aug_2013_10_13_48.

INFO       2013-08-28 10:13:48.101 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Users\Administrator\AppData\Local\Temp\sapinst_exe.3016.1377656020\dev_sap_kernel_test_28_Aug_2013_10_13_48.

TRACE      2013-08-28 10:13:48.101 [syxxclogbook.cpp:211]

           PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)

           lib=syslib module=syslib

Initialized SAP kernel tracing to file C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020\dev_sap_kernel

TRACE      2013-08-28 10:13:48.116 [iaxxclib.cpp:161]

           CLib::load()

Opened C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020/iaguieng722.dll

TRACE      2013-08-28 10:13:48.116 [syxxclogbook.cpp:211]

           PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)

           lib=syslib module=syslib

Initialized SAP kernel tracing to file dev_sap_kernel

TRACE      2013-08-28 10:13:48.148 [synxcuser.cpp:2143]

           CSyUserImpl::isExistingOnOS() lib=syslib module=syslib

existence check for user Administrator returned true.

TRACE      2013-08-28 10:13:48.148 [syxxccache.cpp:419]

           CSyAccountCache::addToCache(const IaPtr<CSyAccountImpl> account)

           lib=syslib module=syslib

inserted account (Administrator, S-1-5-21-2412049160-3397589599-1334480533-500, USER) into the accountcache.

TRACE      2013-08-28 10:13:48.148 [synxccuren.cpp:921]

           CSyCurrentProcessEnvironmentImpl::setEnvironmentVariable(const iastring & 'SAPINST_JRE_HOME', const iastring & 'C:/Users/ADMINI~1/AppData/Local/Temp/sapinst_exe.3016.1377656020/jre')

           lib=syslib module=syslib

Environment variable SAPINST_JRE_HOME set to value 'C:/Users/ADMINI~1/AppData/Local/Temp/sapinst_exe.3016.1377656020/jre'.

INFO       2013-08-28 10:13:49.520 [synxcpath.cpp:798]

           CSyPath::createFile() lib=syslib module=syslib

Creating file C:\Users\Administrator\AppData\Local\Temp\sapinst_exe.3016.1377656020\dev_sap_kernel_test_28_Aug_2013_10_13_49.

INFO       2013-08-28 10:13:49.520 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Users\Administrator\AppData\Local\Temp\sapinst_exe.3016.1377656020\dev_sap_kernel_test_28_Aug_2013_10_13_49.

TRACE      2013-08-28 10:13:49.708

MessageLib initialized successfully.

TRACE      2013-08-28 10:13:49.708

exe dir is C:/Users/ADMINI~1/AppData/Local/Temp/sapinst_exe.3016.1377656020

INFO       2013-08-28 10:13:49.723 [synxcpath.cpp:798]

           CSyPath::createFile() lib=syslib module=syslib

Creating file C:\Program Files\sapinst_instdir\x.

INFO       2013-08-28 10:13:49.723 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Program Files\sapinst_instdir\x.

TRACE      2013-08-28 10:13:49.739 [iaxxclib.cpp:161]

           CLib::load()

Opened C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020/iakdblib722.dll

TRACE      2013-08-28 10:13:49.739

SAPinst build information:

--------------------------

abi version : 722

make variant: 720_REL

build       : 1426667

compile time: Aug  1 2013 17:47:24

TRACE      2013-08-28 10:13:49.770

TRACE      2013-08-28 10:13:49.770

In case of a starting problems please check if the following assumptions are valid:

TRACE      2013-08-28 10:13:49.770

The installation was started from a directory which is writable to the SAPinst (and m_cwd ==  m_startfileDirectory )

TRACE      2013-08-28 10:13:49.770

The file control.xml is a valid "control.xml".

TRACE      2013-08-28 10:13:49.770

TRACE      2013-08-28 10:13:49.770

current working directory is C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS

INFO       2013-08-28 10:13:49.942 [synxcpath.cpp:798]

           CSyPath::createFile() lib=syslib module=syslib

Creating file C:\Program Files\sapinst_instdir\x.

INFO       2013-08-28 10:13:49.942 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Program Files\sapinst_instdir\x.

TRACE      2013-08-28 10:13:49.942 [syxxcfile.cpp:125]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/dev_sap_kernel, m_realNodeType: 2}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target file exists and (mode & ISyNode::EXISTING) ==> I will copy/move.

INFO       2013-08-28 10:13:49.942 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\dev_sap_kernel.

TRACE      2013-08-28 10:13:49.942 [syxxcnode.cpp:428]

           CSyNodeImpl::move(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS, ISyNode::CopyMoveMode_t 0x3)

           lib=syslib module=syslib

Moved C:/Users/Administrator/AppData/Local/Temp/sapinst_exe.3016.1377656020/dev_sap_kernel to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/dev_sap_kernel

TRACE      2013-08-28 10:13:49.942 [syxxcfile.cpp:125]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/dev_sap_kernel, m_realNodeType: 2}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target file exists and (mode & ISyNode::EXISTING) ==> I will copy/move.

INFO       2013-08-28 10:13:49.942 [synxcfile.cpp:368]

           CSyFileImpl::removeEx(ISyFSErrorHandler * pErrorHandler)

           lib=syslib module=syslib

Removed file C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\dev_sap_kernel.

TRACE      2013-08-28 10:13:49.942 [syxxcnode.cpp:428]

           CSyNodeImpl::move(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS, ISyNode::CopyMoveMode_t 0x3)

           lib=syslib module=syslib

Moved C:/Windows/System32/dev_sap_kernel to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/dev_sap_kernel

TRACE      2013-08-28 10:13:49.942 [syxxclogbook.cpp:211]

           PSyLogBook::initSAPKernelTracing(int traceLevel, const CSyPath & filePath)

           lib=syslib module=syslib

Initialized SAP kernel tracing to file C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\SYB\CENTRAL\AS\dev_sap_kernel

TRACE      2013-08-28 10:13:49.957

exe dir is C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020

TRACE      2013-08-28 10:13:49.957

exe dir is C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020

TRACE      2013-08-28 10:13:52.328

Running with toplevel file C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/toplevel.xml

TRACE      2013-08-28 10:13:52.344

Component version information: lmti_004_REL (CL 118967)

TRACE      2013-08-28 10:13:52.344 [syxxcfile.cpp:85]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst_dev.1.log, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

TRACE      2013-08-28 10:13:52.344 [syxxcnode.cpp:428]

           CSyNodeImpl::move(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst_dev.1.log, ISyNode::CopyMoveMode_t 0x3)

           lib=syslib module=syslib

Moved C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst_dev.log to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst_dev.1.log

TRACE      2013-08-28 10:13:52.360 [syxxcfile.cpp:85]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst.1.log, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

TRACE      2013-08-28 10:13:52.360 [syxxcnode.cpp:428]

           CSyNodeImpl::move(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst.1.log, ISyNode::CopyMoveMode_t 0x3)

           lib=syslib module=syslib

Moved C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst.log to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst.1.log

TRACE      2013-08-28 10:13:52.625

Using custom value info for property SAPINST_MESSAGE_CONSOLE_THRESHOLD.

TRACE      2013-08-28 10:13:52.625

Running with keydb file C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.xml

TRACE      2013-08-28 10:13:52.625

Running with dialog file C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/dialog.xml

TRACE      2013-08-28 10:13:52.796 [syxxcfile.cpp:85]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.2.xml, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

TRACE      2013-08-28 10:13:52.796 [synxcfile.cpp:470]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.2.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

           lib=syslib module=syslib

Copying file C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.xml to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.2.xml

INFO       2013-08-28 10:13:52.796 [synxcfile.cpp:670]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.2.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

           lib=syslib module=syslib

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/keydb.2.xml'.

TRACE      2013-08-28 10:13:52.999 [syxxcfile.cpp:85]

           CSyFileImpl::decideIfMoveCopyNode(const CopyMoveDestinationInfo & {m_nodeTypeForCombiCheck: ..., m_path: C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.1.xml, m_realNodeType: 8}, ISyNode::CopyMoveMode_t 0x3, PSyNodeInt &) const 

           lib=syslib module=syslib

Target node does not exist and (mode & ISyNode::MISSING) ==> I will copy/move.

TRACE      2013-08-28 10:13:52.999 [synxcfile.cpp:470]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.1.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

           lib=syslib module=syslib

Copying file C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.xml to C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.1.xml

INFO       2013-08-28 10:13:53.15 [synxcfile.cpp:670]

           CSyFileImpl::copy(const CSyPath & C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.1.xml, ISyNode::CopyMoveMode_t 0x3, ISyProgressObserver*) const 

           lib=syslib module=syslib

Copied file 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.xml' to 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/statistic.1.xml'.

TRACE      2013-08-28 10:13:53.93 [kdxxctaco.cpp:165]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

CKdbTableContainerImpl::syncToContainerFile start ...

TRACE      2013-08-28 10:13:53.93 [kdxxctaco.cpp:197]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

after creating out stream

TRACE      2013-08-28 10:13:53.93 [kdxxctaco.cpp:231]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

CKdbTableContainerImpl::syncToContainerFile stop ...

TRACE      2013-08-28 10:13:53.171 [kdxxctaco.cpp:165]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

CKdbTableContainerImpl::syncToContainerFile start ...

TRACE      2013-08-28 10:13:53.186 [kdxxctaco.cpp:197]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

after creating out stream

TRACE      2013-08-28 10:13:53.186 [kdxxctaco.cpp:231]

           CKdbTableContainerImpl::syncToContainerFile lib=iakdblib

CKdbTableContainerImpl::syncToContainerFile stop ...

TRACE      2013-08-28 10:13:53.389

SAPinst was started using commandline: C:\Users\ADMINI~1\AppData\Local\Temp\sapinst_exe.3016.1377656020\sapinst.exe SAPINST_CONTROL_URL=C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/control.xml SAPINST_CWD=C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS

TRACE      2013-08-28 10:13:53.389

SAPinst properties are :

SAPINST_CHECK_PACKAGES=false

SAPINST_CONTROL_URL=C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/control.xml

SAPINST_CWD=C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS

SAPINST_DIALOG_PORT=21212

SAPINST_DIALOG_URL=dialog.xml

SAPINST_EXE=SAPINST_EXE

SAPINST_JSLIB_TRACE=NW,NWUsers,OraCom,NWCTC,ClusterMgt,SystemIdentity,NetworkMgt

SAPINST_KEYDB_URL=keydb.xml

SAPINST_MESSAGE_CONSOLE_THRESHOLD=info

SAPINST_MESSAGE_URL=.

SAPINST_PACKAGES_URL=packages.xml

SAPINST_RESOURCE_URL=resourcepool.xml

SAPINST_SAVE_INPUT=true

SAPINST_SCAN_DEVICES=false

SAPINST_SKIP_DIALOGS=false

SAPINST_TOPLEVEL_URL=toplevel.xml

SAPINST_USE_ADVANCED_JS_HANDLING=true

SELFEXTRACTOR_EXECUTABLE_NAME=C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/SYB/CENTRAL/AS/sapinst.exe

regards

Hello Gurus

I need urgently configure my SLD in Solution Manager 7.0 EHP1. But I'm having problems to execute the step of SLD configuration

In this step it says: 'Open the administration interface in SLD, using the following URL: <http://<SLDHOST>:<SLDPORT>/sld>.' my hostname is sapslm, but I dont know which port I have to use

I've tried http://sapslm.ogmaster.local:8050/sld but received a 404 - page not found error

Below the full procedure:

All managed systems report their system data to an SLD. If there are several SLDs in the landscape, the system forwards the data to a central SLD.

Activities

Open the administration interface in SLD, using the following URL: <http://<SLDHOST>:<SLDPORT>/sld>.

Choose Administration -> Data Supplier.

Choose Add SLD.

Enter the URL of the SLD contained in SAP Solution Manager, using the following URL: <http://<SOLMANHOST>:<SOLMANPORT>>.

Enter an SLD administrator and a password (default user: J2EE_ADMIN).

Choose Save.

Once you save the system data of the managed systems, and the data from the source system has been transferred to the external SLD again, it is transferred to the (local) SLD of SAP Solution Manager.

Regards

With SAP Solution Manager 7.1, the Landscape Management Database (LMDB) has been introduced, changing the handling of landscape data. In the following, we have collected answers to frequently asked questions.

Add new questions as comment!

For detailed LMDB information, see the Documentation for System Landscape Management - LMDB

What is a ... Where can I find landscape descriptions? Why are there several repositories for landscape data: SLD, SMSY, and LMDB? What's better with the LMDB? How can I update outdated CR Content in the LMDB? How does data get into the LMDB? How does data get into SMSY when the LMDB replaces the local SLD in the SAP Solution Manager 7.1? What to do with data of systems that do not exist any longer? What to do if there are duplicate system entries in the LMDB? How do I connect the right SLD, can I change SLDs in between? If data supplier information is forwarded from a PI-SLD to the Solution Manager SLD, where must the latest CR content be installed? How do I set the rank for content synchronization between SLD and LMDB Which CIM model version does the LMDB need? Must the SLD have the same version Why do I not see some properties of my technical system? Why is there outdated data? Where do I report problems with the LMDB? How is LMDB data synchronized with the SAP Support Portal? Which background jobs are running for the LMDB? As long as NW7.31 PI SLD has all contents, can we simply swap LMDB sync from NW PI 7.11 SLD? Is there any risk removing the target of NW PI 7.11 SLD and add NW7.31 SLD? How can I get support to plan a company-wide SLD landscape? Where do I assign product instances to product systems? How can I ensure that data suppliers send correct data to the SLD?

Not found what you are looking for? Check out the SAP xSearch at http://service.sap.com/notes

What is a ...

technical system, product system, product instance, software component (version), logical component ...?
Click the links for defintions! See also the graphic here.

Where can I find landscape descriptions?

Landscape descriptions are collected at different locations for different purposes: in SLD, LMDB in SAP Solution Manager, Landscape Planner, SAP NetWeaver Landscape Virtualization Management, and SAP Infrastructure Management.
For more information, see Landscape Descriptions.

Why are there several repositories for landscape data: SLD, SMSY, and LMDB?

• The SLD is the target for self-registration of technical systems in the IP landscape. This technical systems information is provided for applications in non-productive and productive applications such as SAP NetWeaver Process Integration and WebDynpro (Java) based applications that need this information. Because of the productive use of the data it provides, often many SLD systems are used in customer landscapes (see SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape).
• The LMDB retrieves technical system information from the SLD as a basis for landscape data, to manage technical systems in monitoring and maintenance processes. It acts as a single source of truth in SAP Solution Manager. It provides a centralized UI approach to landscape verification functions and transaction SMSY.
  As of SAP Solution Manager 7.1 SP0-4, the LMDB manages information about technical systems, hosts.
  As of SP5, the LMDB also manages product system information.
• Transaction SMSY is the "old" system information storage, being replaced by the LMDB bit by bit.
  Up to SAP Solution Manager 7.1 SP4, SMSY is still used to manage product system information, but gets all technical systems information from the LMDB.
  As of SP5, SMSY is only used to manage project-related data (logical components and solutions); the required data (technical systems and product systems) ar edited and provided by the LMDB (see New in SP05: Product System Editor in the Landscape Management Database of SAP Solution Manager 7.1). 

What's better with the LMDB?

SAP Note 1679673 explains the most important differences between LMDB and SMSY.

How can I update outdated CR Content in the LMDB?

CIM model and CR Content are identical in System Landscape Directory (SLD) and LMDB. Every LMDB needs to be connected to an SLD system via full automatic synchronization. Together with all other data CIM model and CR Content are retrieved and updated from the SLD.

For details on CIM model and CR Content, see:

• SAP Note 669669
• SAP Note 1701770

More on System Landscape Directory -> How-to Handle Data in the SAP NetWeaver System Landscape Directory

How does data get into the LMDB?

The most important data source for the LMDB is the SLD – every LMDB needs to be connected to an SLD. All data contained in the SLD is retrieved by the LMDB via full, automatic synchronizationSome data is created in the LMDB, manually.#

1. CIM model and CR content (SAP software catalog) are synchronized from the SLD.
2. All technical systems with a data supplier are supposed to forward their system identity to an SLD. For 3rd-Party systems, this can be done by 'sldreg' data suppliers; details under System Landscape Directory -> Registering Third-Part Systems in the SLD.
   From the SLD, all data changes are forwarded to the LMDB.
3. If a technical system type doesn't have a data supplier (yet), its data can be created in the LMDB manually.
4. Systems that were manually created in transaction SMSY (because they once didn't have a data supplier, for example) can be migrated to the LMDB when you are updating to SAP Solution Manager 7.1. For more information, see SAP Help Portal: Migrate System Information from SMSY to LMDB.
5. Product system descriptions always must be created in the LMDB manually (as of SP5, previously in TA SMSY), based on the technical information provided by the SLD.

• SAP Help Portal: Integration of System Landscape Management Database (LMDB)
• SDN: More on System Landscape Directory-> Demo: The Full Automatic Sync Feature in the SLD of SAP NetWeaver 7.1.
• SAP Help Portal: Integration of System Landscape Management
• Planning Guide — System Landscape Directoryat http://scn.sap.com/docs/DOC-8042
• SAP Note 1669649

How does data get into SMSY when the LMDB replaces the local SLD in the SAP Solution Manager 7.1?

SMSY gets all technical (as of SAP Solution Manager 7.1 SP0) and product system information (as of SP5) from the LMDB. For older technical systems, that were registered in SAP Solution Manager 7.0 in SMSY manually, a migration process from SMSY to LMDB is available; for more information, see SAP Help Portal: Migrate System Information from SMSY to LMDB.

Product systems (until SP4) and logical components are still created in SMSY.

What to do with data of systems that do not exist any longer?

First of all: Do not simply delete technical system information in the LMDB. If a system becomes obsolete, delete it from the SLD, first, and deactivate the data supplier. The deletion is aut. synchronized with the LMDB and SMSY.

If, for some good reason, a technical system information was manually created in the LMDB, you also have to delete it manually. For more information, see the SAP Help Portal: Delete Technical System Information and Troubleshooting for the LMDB.

If a system was moved to a different server, this move can be handled in the SLD so that depending data (e.g. business systems) does not get lost but is updated.
For details on data maintenance in the SLD, see the SDN - More on System Landscape Directory -> How-to Manage House-Cleaning in the System Landscape Directory - Duplicate System Entries

What to do if there are duplicate system entries in the LMDB?

For different reasons, it can happen that the same system is registered more than once in the LMDB, with the same SID (e.g. ABC) but with different extended SIDs (e.g. ABC00001 and ABC00002) and maybe different hosts or installation numbers.

To find out how to clean up this situation, see SAP Note 1694004.

How do I connect the right SLD, can I change SLDs in between?

The SLD connection in SAP Solution Manager is set up in TA SOLMAN_SETUP -> System Preparation -> Prepare Landscape Description -> Select SLD and Set Up LMDB.

Connecting several SLDs to one SAP Solution Manager LMDB is not recommended. If you need to do so, you MUST make sure that any piece of information gets to the LMDB only via one SLD. Data on two or more SLDs must not overlap.

To ensure consistent CR content, you can only select one SLD as a CR source. For all other data (SIDs of tech. systems, business systems, host names, servers, etc.) you MUST install processes to fully separate the names (by naming conventions) and the data flow (by complete separation of SLD systems) to keep the unique-path-principle for data.

• SLD-LMDB Topology – Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP Solution Manager
• SLD and LMDB Topology: Replacing the Source SLD for the LMDB
• To keep SLD content available for SAP Solution Manager during SLD maintenance, you can switch between different SLDs that are in sync. For more information, see Switching between 2 SLD Systems in Sync with an LMDB or a 3rd SLD.

If data supplier information is forwarded from a PI-SLD to the Solution Manager SLD, where must the latest CR content be installed?

Ideally, the CR content is up-to-date in all SLDs. If you cannot make changes to your PI production system, you must at least update the SAP Solution Manager SLD. For the synchronization between SLD and LMDB it is important to have the latest CR content in the SLD that is used as CR source for the content synch (here, the Solution Manager SLD). The supplier data sent to the PI-SLD is forwarded in its original state and processed in the SAP Solution Manager SLD, hence, it does not matter for the LMDB if the CR content is outdated in the PI-SLD.

How do I set the rank for content synchronization between SLD and LMDB?

LMDB is acting as a single source of truth for landscape data in the SAP Solution Manager 7.1. It must always have a higher rank than the connected SLDs. Thereby, you avoid overwriting of manually edited data in the LMDB. For more information, see the SAP Help Portal: Connect LMDB to SLD.

Which CIM model version does the LMDB need? Must the SLD have the same version?

As a general rule, CIM model and CR content should not be older than three months compared to the latest version available at the SAP Service Marketplace. The SLD content updates are published every four to six weeks. If more than one SLD is connected to the LMDB, each connected SLD must contain at least the required CIM model version. But the model versions in multiple SLDs don't need to be identical. For more information, see the SAP Help Portal: Connect LMDB to SLD and SAP Note 1701770.

Why do I not see some properties of my technical system? Why is there outdated data?

Check if the full, automatic content synchronization is running under SAP Solution Manager Configuration (transaction solman_setup) -> System Preparation -> Prepare Landscape Description -> Set Up LMDB.

Check if the affected technical system is available in the SLD – if it is: Did you change the system information manually in the LMDB (you can see this on the Overview under Last Manual Change for the technical system)? Manual changes in the LMDB have a higher ranking than information from the SLD to avoid manual changes from being overwritten. But this also means that you need to update manually what you changed manually. If there is updated information from the SLD, it won't be written into the LMDB.

In such a case, when data is correct in the SLD, it can be helpful to use the SLD re-synchronization function in the LMDB. For more information, see the SAP Help Portal: Resynchronize Technical System Information from SLD and Troubleshooting for the LMDB.

Where do I report problems with the LMDB?

The component to create incidents is SV-SMG-LDB.

How is LMDB data synchronized with the SAP Support Portal?

See SAP Help Portal: Synchronize System Information with the SAP Support Portal.

Which background jobs are running for the LMDB?

Job	What it does
SAP_LMDB_LDB_*	Synchronization with SLD: In the SAP Solution Manager system, the name of the sync jobs between SLD and LMDB start with SAP_LMDB_LDB_* (e.g. SAP_LMDB_LDB_0000000001) and run under the SOLMAN_BTC system user. More at Connect LMDB to SLD.
SAP_LMDB_SMSY_SYNC SAP_LMDB_LCACHE_* DIAG_NOTIF_GUIDS_*	Jobs that initially fill the data stores in SAP Solution Manager: SAP_LMDB_SMSY_SYNC for consumer CL_LMDBS_NOTIFICATION (SMSY) SAP_LMDB_LCACHE_<domain id>_<namespace id> for consumer CL_LAPI_NOTIFICATION_CONSUMER (L-API cache) DIAG_NOTIF_GUIDS__<domain id>_<namespace id> for consumer CL_DIAGLS_LMDB_NOTIF_MANAGER (diagnostics) Valid until 7.1 SP7. See SAP Note 1592461.
SAP_LMDB_NOTIFY_LDB_*	Synchronization with SMSY and others: Between SMSY and SLD, there is no direct connection anymore. But all data in LMDB is automatically forwarded to SMSY by this notification job and by downstream sync jobs of individual consumers. Furthermore, this job updates other notification consumers, e.g. the Landscape API (L-API), diagnostics, and dual-stacks.
REFRESH_ADMIN_DATA_FROM_SUPPORT	Download SAP Service Marketplace information to SAP Solution Manager: Basic license data is regularly downloaded from the SAP Support Portal (aka 'OSS system') to SAP Solution Manager with this batch job. Parts of the downloaded information is stored in the LMDB. More in SAP Note 1490774.
LANDSCAPE FETCH job (daily) triggers report RSGET_SMSY (During solman_setup, is directly executed, once.)	Synchronization of LMDB and SAP Support Portal: LMDB data for all technical systems that are configured as 'active' is synchronized with the SAP Support Portal. For more information, see Synchronize System Information with the SAP Support Portal, which also explains how to trigger the job manually. See also SAP Note 993775. RFC Synchronization with ABAP systems:             The job gets data, directly by RFC, from ABAP systems where there READ RFC is available or maintained. For more information, see Manage RFC Connections for ABAP Technical Systems. In SAP Solution Manager, this data is stored in transaction SMSY. with Transport Management System (TMS): If the system is a domain controller for the Transport Management System (TMS), also transport landscape information is synchronized, which includes system names, clients, software components, and TMS-specific information for systems in the transport domain.This is required for Change Request Management (ChaRM). In SAP Solution Manager, this data is stored in transaction SMSY. You can find the LANDSCAPE FETCH job under solman_setup-> Basic Configuration -> Configure Automatically -> Schedule Solution Manager-> Background Jobs.
RLMDB_OSS_SYNC_CONF_AUTO_MIG	Synchronization from LMDB to SAP Support Portal: This report uploads LMDB system information to the SAP Support Portal. More in SAP Note 993775.
LMDB_VERIFICATION	LMDB Verification Checks for Product Systems:       The job is run when you trigger verification checks in the LMDB product system editor. For more information, see Execute Verification.

As long as NW7.31 PI SLD has all contents, can we simply swap LMDB sync from NW PI 7.11 SLD? Is there any risk removing the target of NW PI 7.11 SLD and add NW7.31 SLD?

See SLD and LMDB Topology: Replacing the Source SLD for the LMDB.

How can I get support to plan a company-wide SLD landscape?

For complex system landscapes an SLD planning workshop is recommended to define what the system landscape should look like. It can be followed-up by other services like a detailed migration plan, best practice recommendations for naming conventions, failover strategies, and maintenance or execution of the recommendations.

German-speaking customers still find the workshop as Strategischer SLD-Planungsworkshop in the ITTS Catalog.
In the future, SLD planning is part of a global SPM Service.

Where do I assign product instances to the product system?

When you maintain a product system, assign technical system + product instances to the product system - do NOT change the instances marked as installed on the technical system! Technical system information should always be sent by data supplier - do not change it manually.

How can I ensure that data suppliers send correct data to the SLD?

Check SAP Note 1842956 (Check Data Supplier Consistency for Technical System in LMDB).
If kernel or database data is missing, especially check if the SLD registration by sapstartsrv is active. See SAP Notes 1717846 (sapstartsrv SLD registration), 1824302 (Caption property of the SCS instance is incorrect in SLD), and 1715334 (SAPJVM version registered incorrectly in SLD).

Hi experts,

I have installed SAP Solution Manager 710 and applied SP08.~

Now, I am performing the configuration phase.

In system preparation, I have already done the following stepes

1-create Users

2-Check Installation

3-Implement SAP Note

All the above steps was successfully done.

I am stucked at Configure connectivity--> 4.4 Set Authorization Policy for Agents.

When I go to Agent Administration, it displays a page without agents.

Can you please help me to activate and view the installed agents so that I complete this step successfuly.

best regards

Ernesto Mandlate

Good Day All

Can anyone guide me on the following :

i want to configure my email notification so that when the notification Alert is raised and the email notification is sent to the recipient i want to include additional information in the body text of the email

i am aware that the badi BADI_BUILD_MESSAGE is define for this but im not sure if the information i want included can be perfmored with the badi

i am looking to include the specific error message per the IDOC as displayed in WE02 - highligted in green) (See pic1)

this message is a standard message with concacetanations of values stored in table EDIDS

Thank you

Dear all,

I installed a new 7.1 solman SP04 on a windows 2008 R2 Enterprise Edition 64bit with MS SQL 2008 R2.

After running the solman_setup on the System Preparation screen after I click NEXT it just hangs, stop responding, nothing happen, what could be the problem?

Check the screenshot for more details.

Best regards,
nelson chamba\

Hi, SolMan expert,

We tried to setup SolMan 7.1 internal BW for the first time according to all the possible SAP configuration documents we could find including those in many existing related threads. RSA1 datasource node Solution Manager 0SM_SMG_ROOT/0SM_SMG has only 12 active data sources. Most of them, for example 0SM_DSWPBI_PERF, didn't extract any data. Error message is "No data available in the source system for this selection".

Although many infoObject _TEXT or _ATTR datasources were activated, many are still missing, for example, 0BPARTNER_HIER. There are many activated infoCubes and DSOs, which have no downward data flow defined due to lack of corresponding active datasources.

Can anyone show us:

1.  How to find more SAP delivered data sources?

2.  Why didn't existing data source find data?

3.  Should all the BW extraction transformation process objects pre-exist and be defined with the downward and upward flows?

4. Whether we have to develop our own customized data source, transfer rules, update rules and etc.?

Thank you very much in advance!

Hong

Hello, I have solman 7.1  SP08  on hpux box . it has SAPJVM4.1   patch 16 and I want to upgrade to latest patch 33, I downloaded and unpacked it .  Oss notes say to use SUM to update  , So I have  latest version  of SUM .  When I run  SUM and get to the part where it wants either a stack configuration file n XML file or a manually prepared directory.  I select the manual  directory ,but what file (or directory ) do I point it to from the sapjvm 33 patch I  expanded?  Everyone I try gives me an error.

Hello!

I've configured VAR ServiceDesk in SolMan 7.01.

OSS-messages are successfully transfered to SAP and back.

Trying to configure now e-mail notification about message status change for reporter/processor.

Everything is done according to manual, except for the support team (we use two BP's with e-mail addresses provided):

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30bfb120-d4fa-2d10-7389-fadeee222b62?quicklink=index&overridelayout=true

TA SPPFCADM -> Application CRM_ORDER -> Define Action Profile and Actions -> Action Profile SLFN0001_ADVANCED -> made a Z-copy from action SLFN0001_ADVANCED_MAIL, parameters as in manual -> Save

TA SPPFCADM -> Application CRM_ORDER -> Condition Configuration -> for action profile SLFN0001_ADVANCED I've added recently created action -> created scheduling and starting conditions -> reaction on different statuses -> Save.

But when I create a message and change statuses in it - on "Actions" tab no Z-action appears that I've created.

No e-mail notification in SOST.

P.S. SCOT is configured.

What maybe the problem?

Thank you!

Hello experts!

Is there a Standard extension for "Сreate message" of Solution Manager. It is necessary to add a new field in this GUI window

Version is SM 7.1 SP8.

Thanks for information

Hi,

in my Change Request ZMCR I use the approval Procedure SMCR0001, but instead of the Change Manager Function which is normaly used for approval, I do use an own Z-BPFuction Called Change Coordinator ZDCR0011. Which is also configured in the Approval Procedure. Sadly, when I fill in the BP in the header of the Ticket and choose the approval Function, the BP is not copied into the approval assignment block. When I connfigure the procedure to use the Change Manager it is working.

Does anyone have any Idea, why it is not working with Z-Functions?

Thanks and Best Regards

Alex

As commented with friend Billy Warring  I open a discussion to share options to export data from LMDB from different ways to different goals.

That point start trough comments on Landscape Management Database (LMDB) – FAQ

I will collect all contributions in that discussion.

Thanks all for sharing ¡

Best regards,

Luis

Hi,

I am on Solman 7.1 SP8 on Windows Cluster VM environment. I am trying to setup Technical monitoring and Diagnostics.

The problems is with the Diagnostics agents:

1.

[Thread[SLD-AssocWatcher,1,main]              ] Error      [SLDQueryBuilder] SLD check connection failed

[EXCEPTION]

com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: HTTP response code: 503 Not Ready

** I have already Increased the parameters as per the section 'Scalability' in the Diagnostics Troubleshooting guide. Also, increased the number of concurrent registrations allowed from default value 10 and increased the number of threads.

2.

[EXCEPTION]

java.lang.ClassCastException: class com.sap.smd.api.ISMDAgentHandle_Stub:com.sap.smd.agent.loader.FileClassLoader@5f989f84

incompatible with interface javax.naming.Context:null

          at com.sap.smd.agent.connection.SMDConnectionTask.unbindAgent(SMDConnectionTask.java:1359)

          at com.sap.smd.agent.connection.SMDConnectionTask.internalAttemptConnection(SMDConnectionTask.java:724)

          at com.sap.smd.agent.connection.SMDConnectionTask$1.run(SMDConnectionTask.java:107)

          at com.sap.smd.agent.connection.P4JNDIContextHelper.executeInSecurityContext(P4JNDIContextHelper.java:148)

          at com.sap.smd.agent.connection.SMDConnectionTask.attemptConnection(SMDConnectionTask.java:102)

          at com.sap.smd.agent.connection.SMDConnectionTask.run(SMDConnectionTask.java:1271)

          at java.lang.Thread.run(Thread.java:679)

3.

com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is java.io.EOFException: End of stream is reached unexpectedly during input from Socket

The Agents keep on randomly shutting down with these errors.

I have tried with the smdsetup scripts.

I am using the 'On the Fly' scenario.

I do not find any solutions for these errors.

Regards,

Kaustubh.

Dear All

my current solma 7.0 on sp17 i want to update it please guid me...

my patch lave is

SAP_BASIS             700    0016    SAPKB70016

SAP_ABA                700    0016    SAPKA70016

PI_BASIS                 2006_1_700    0008    SAPKIPYM08

ST-PI                        2008_1_700    0004    SAPKITLRD4

SAP_BW                  700    0018    SAPKW70018

SAP_AP                   700    0014    SAPKNA7014

BBPCRM                  500    0012    SAPKU50012

BI_CONT                  703    0005    SAPKIBIIP5

CPRXRPM                400    0019    SAPK-40019INCPRXRPM

ST                            400    0017    SAPKITL427

ST-A/PI                     01L_CRM570    0000    -

ST-ICO                      150_700    0029    SAPK-1507TINSTPL

ST-SER                     700_2008_1    0005    SAPKITLOO5

please guide me

nainesh

9376998808

Hi All,

As I am generating EWA Report in every week.I am getting some issues regarding the same for Production Server.

As of now we are in the Kernel of 701 with patch level 196.Can anyone please help me out for the same.Screenshot is attached.

Please help me out as it is a production issue guys.

Kindly Suggest.

Many Thanks

Ajitabh

Hello gurus,

Recenlty I downloaded CCN 1652693 (ver.38)  through Solman_setup and when Clicked on the sap note assistant its directed to SNOTE screen.

when i checked the notes status , it shows Completely implemented ,Finished.Dont know why the status shows completed without executing impliment note from Snote.

Please guide how to impliment the note again with lastest related notes.Now i have downloaded all the Latest Notes using Sap note browser /F8 .But the status of Central Correction Notes is Completely implimented.

Thanks in advance..

regards

mathew

Dear,

    While doing the system preparation on solution manager 7.1 the below error message is popping up after the note is downloaded.We downloaded and implemented the note, but still its showing red.

Hello,

I just installed Solution Manager 7.1 on Linux and DB2. Though all the web-based transactions, like

solman_workcenter are not working.

1) I managed my local hosts file

2) I enabled all the /sap/bc services in transaction SICF

3) I googled, that it is necessary to setup the Solution Manager using the transaction solman_setup.

I tried to do it, but an IE window pops up prompting me to login (via popup). Afterwards, I am getting

the following error:

The URL which tried to open is:

http://<hostname>:8000/sap/bc/webdynpro/sap/wd_sise_main_app

I went again to SICF, but I don't have an entry, called sap under /sap/bc/webdynpro. And everything in

/sap/bc is activated anyway...

Please help me to correctly configure my Solution Manager :-)