In my solman system , DBACOCKPIT , "SLD System Import" tab is inactive

Dear All,
My SOLMAN system has SAP_BASIS 702 0012 and ST 710 0008
In DBACOCKPIT "SLD System Import" tab is inactive.
Please let me know if there is a way to make this tab active , and execute "SLD System Import" in DBA cockpit
Let me know in case you need more details
Thanks & Regards,
Sudhir

Hi Sudir,
No, you have not selected the dedicated system. Still you are in overview page.
It is saying active 53, inactive 5.
You select the system from the left panel. I am not sure where it is in your screen, But Try in SAP GUI as below
Thanks
Jansi

Similar Messages

How to Configure Business System in SLD (SAP-XI).

Hi all,
I am new to XI. I want to know the detail scenario of configuring Business system in SLD(System Landscape Directory) in SAP-XI.
Can , anyone help me on this...

hi suresh,
gothrogh this below liks ..........
http://help.sap.com/saphelp_nw04/helpdata/en/fe/39ae3d47afd652e10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/7b/d4653fd1d3b81ae10000000a114084/content.htm
http://wiki.sdn.sap.com/wiki/display/XI/WorkingwithSystemLandscapeDirectory+(SLD)
regards,
kesava

SAP PO Import tab

I config the system to have the import tab for all the PO (means domestic and international) and assign the declaration form when the material has commodity code. But now even though material has not a commodity code system is assigning a declaration form to it which i dont want it (if material does not have the commodity code system should not assign the declaration form in import tab to it. Any help be great.

Dear,
Check the Settings in OMGT trxn
Spro>MM>Purchasing>Foreign Trade/Customs>Control Foreign Trade Data in MM and SD Documents>Import Screens In Purchasing Document
Regards,
R.Brahmankar

SLD Export / import Technical and Business systems

Dear all,
I am new to SLD administration.
We have task to update the local SLD on the Production PI system PPI ( Target ) with the business systems ZEC, ZSC from the Production Master SLD on Production solution manager system
PSM ( source ) using Export/Import on the necessary technical and business systems.
Please confirm whether i am following correct steps :
Go to SLD Administration on PPI target system
ALL Instances
Instances by Class
Model
( which one of this option need to be selected , please let me know ?? )
Go to SLD Administration on PSM source system.
select Export button ->
Select business systems one by one and perform Export which will create .ZIP file
at local machine.
Go to SLD Administration on PPI target system
select Import button ->
Select Export ZIP file which created in previous steps from PSM and provide location from desktop
Start Import button ( only if you get Continue import option )
Please let me know if above procedure is correct for business systems
if yes then what need to be done for Technical system ??...do they require Export/import also ?
If yes when i go to technical system option i get Export option disabled...but same way when i go to
business systems option i get Export button enable and able to perform the export.
Do i need to only Export / Import business systems ?
Plese help me.
Regards,
RR

Manoj,
It seems entries are added manually .... should we remove and run Import for the same ...
or just try to overwrite .... in case of overwrite option ( as we have open OSS message ) SAP has suggested through OSS message that If you end up with problems when trying to overwrite, then the PPI SLD is broken and will have to be re-built because someone made a manual change to it and got the GUIDs out of synch with the master.
I do not understand if target system PPI SLD gets broken during overwriting operation as mentioned by SAP ... whats is the way / steps / procedure to Re-build SLD .
In rebuilt - process do i need to Import ( Export -> Export lines -> ALL ) the export backup created before start of this activity ? please let me know SLD rebuilt steps and about Remove - reimport issue.
Appreciate you time on this. thanks in advance.

** Is it possible to change the IP of the existing Technical System in SLD?

Hi Friends,
I want to do RFC to RFC scenario. When I try to import the RFC from the Business System, RFC is not imported. When I looked the corresponding technical system in the SLD, it is having the old IP address. That's why I am not able to import. So, is it possible to change the IP of the existing technical system in the SLD ?
Kindly reply.
Kind Regards,
Jegatheeswaran P

Reason being : We can associate n business syatems with one tech system with and we configure the scenarios via business systems which itself uses Tech system , if we will make changes in tech system later on it will affect the other scenarios also which are using the same tech system

Error while deleting the business system in SLD

HI
I am trying to delete the business system in SLD and encountering the following error .
if some one has any idea as to why is this error occuring
java.lang.NullPointerException at com.sap.sld.wd.businesssystem.BusinessSystem.removeXIIntegrationServer(BusinessSystem.java:497) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystem.removeXIIntegrationServer(InternalBusinessSystem.java:474) at com.sap.sld.wd.businesssystem.BusinessSystemMainView.RemoveOk(BusinessSystemMainView.java:450) at com.sap.sld.wd.businesssystem.wdp.InternalBusinessSystemMainView.wdInvokeEventHandler(InternalBusinessSystemMainView.java:477) at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87) at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361) at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330) at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:341) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:297) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:706) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:660) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:228) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Thanks
Nikhil

hi Nikhil,
Null pointer errors are difficult to correct as is
If you have imported the BS from some other system make sure the BS has been imported correctly without errors & any Tech systems attached to it exist.
sachin.

Technical systems in SLD not replicating in LMDB

Hello ,
I am installing new quality solution manger system (QSM) and trying to connect sandbox erp system to QSM .
Already configured SLD and sandbox is visible in it by RZ70 and configured synchronization connection between SLD and LMDb in solman_setup .
Currently on the QSM is available in the LMDB , what should I Do ?
Also for connecting diagnostic agent , In step select SLD it is configured but showing with 0 agents so in connecting diagnostic agents step , when trying to get agents nothing is found .

Hi,
I did not understand what is happening in the LMDB, you say that QSM is there...? What you should do in this case is to perform/finish the system preparation and basic configuration. Once these are finished, do the managed system configuration for the sand box. But before that, review its definition in the LMDB according to this wiki: Maintenance of Product in the System Landscape - SAP Solution Manager Setup - SCN Wiki.
In relation to the SMD agent not being available in the SLD, it's not necessary, it only matters that the agent is connected to the Solution Manager. Connecting it to SLD will enable it to connect it to the Solution Manager, but you can connect it directly to the Solman, skipping the SLD. The steps are described in KBA 1907909.
I recommend using the Java message server port to connect it, you can check the dev_ms file to ensure that the correct port is being used.
Best regards,
Daniel.

How to make an entry in transport tab of business system in SLD

Hi gurus,
In PI, in SLD we maintain Business systems. In this business sytem if we go to have a detail look there is a Transport tab.
What is this used for and how to make an entry here.
I'm a basis person and i'm configuring XI for the first time. Kindly help.
Regards,
Priya

1. Yes , you have to maintain target business system for the EACH BS in PROD system.
2. Normally we do have 2 different sld one is explictly for production system. another one is for dev and QA system. Once u done creating all the systems needed for the project. we will copy all business from the dev server to production server. So production server will have all BS from Dev and BS of production server.
3. i am not sure about this. i dont have particular docuemnts . normally we assign target business system in transport tab. and in Intergration Directory we will export the business system from DEV and and import the business system in production system.
Regards,
Balaji
Edited by: Balaji Pichaimuthu on May 19, 2010 9:06 AM

How to configure AS400 System in SLD

Hi,
Am in need to configure AS400 system into SLD. Driver and connection are done. Am in need to add the system into SLD.
do we need to add AS400 DB2 system as the third party system?

Prem,
It depends upon your client standards and SLD naming conventions. If there are mulitiple interfaces to this system, then I would create a 3rd party business system in SLD. After creating you need to assign the corresponding target system, so that when you transport it will take care. Once created you need to import it into your configuration and do your interfaces configuration accordingly.
Regards,
---Satish

SAP File System Access - SLD Naming Convention/Suggestions

I would like to access our ECC file system to pick up files we will use to create Idocs.
I'm wondering the best way to describe the file system access in the SLD.
I have a business system for the main client on the ECC system (BS_ED1CLNT010) for example but the OS isn't client specific.    I could use this as the Business System in the scenario and define a file adapter that connects to the unix server.
Any thoughts?

Maybe I didn't frame my question properly.
In the ECC system we have multiple clients (20,30,40, etc). If I am going to post an Idoc to a client in this system I need to define each as a business system in the SLD and import this to the Integration Directory.    So I would have BS_XXXCLNT010, BS_XXXCLNT020, etc, one for each client.   These all share the same Technical System.    If I want to post an Idoc to a client on the ECC system I have to define a Business System and interface to that and every client that will receive an Idoc. (as well as the ALE settings on the ECC)
Each of these reside on the same SAP server (sap00001 for example) and there is a directory (/public for example) on this server.     This isn't client specific.
I wish to pick up a file from the ECC file system and post a client on the ECC system (maybe different ones based on the data in the file).
I don't want to define the file adapter under BS_XXXCLNT020 since it isn't specifc to client 020 although that would work.
Do I create a new TS in the SLD as third party, stand alone java, and a BS for that?    TS_XXX_FILESYSTE (3rd party). BS_XXX_FILESYSTEM for the TS?
I'm really looking for clarity in the definition of the SLD.

SLD - Technical System Wizard - Select System: Only None (Standalone J2EE)

Hi, I want to connect to some RFC-Modules on a SAP/R3 System from my NetWeaver Web DynPro Application. Therefore I have to create JCO-Connections for the Models I created (MODELDATA_DEST and RFC_METADATA_DEST). For this I have to define the System I want these JCO-Connections to connect to in my SLD which I'm trying to do using the "Technical System Wizard". (SLD -> Technical Landscape -> New Technical System -> Web AS Java (because I'm developing a Java Application).
In the next screen I have to specifiy the location of my Server. I thought, that here, I have to define my SAP/R3 Server to which the JCO-Connections for my two models shall be connected. But the only option I can choose for "Web AS ABAP" (The ABAP System where my RFC-Modules are stored I guess) is "None (Standalone J2EE)".
Why is that? Or am I missing something? I thought I have to specify the SAP/R3 System containing the RFC-Modules here and not my local NetWeaver Server.
Thanks for your help
Thomas

Hi,
there seems to be a misunderstanding here. For JCO to work you need to set up the ABAP-System as a technical system in SLD, otherwise the Java-System is not able to determine information like Hostname and Portnumber for the RFC. Of course it's good to set up your WAS-Java in SLD as a technical system as well, but for the JCO the ABAP side is more important as far as I can see.
To have a clean start I suggest that you set up all involved technical systems in your SLD.
Regards,
Jörg

Pushing data from abap system to SLD

Hello,
I am pushing data from my abap system to SLD.
Job SAP_SLD_DATA_COLLECT is successfully finished but the job SAP_LMDB_LDB_0000000001. is not visible in sm37 in solman.
Hence technical system is not visible in LMDB.
Please guide me
Thanks and Regards,
Akshay

HI Akshay
I hope you had make sure that in SM61 you have assigned batch servers for the jobs.
Can you try to sync your LMDB with SLD once. There is option in LMDB to sync the data, Just see if you are getting the technical system details.
Also, please check the rfc destinatoin with ICM port if it is stable.
RFC LMDB_SyncDest<X> is using ICM Port 80<NR>
You can proceed as below
Please De-Activate the Sync Job in Solman_Setup -> System Preparation -> Prepare Landscape -> Set Up LMDB.
Execute transaction 'SM59'.
Locate the HTTP Destination -> 'LMDB_SyncDest<X>'.
Switch to Edit mode.
Change the Service No to 5<XX>00 where XX is the instance number.
Then makesure the Authorization and Connection test are working.
Then Re-Activate the synch job, via Solman_Setup -> System Preparation -> Prepare Landscape -> Set Up LMDB
Apart from that, can you check below note if it is applicable for you
1615263 - LMDB: Incremental Content Sync Job remains "Scheduled"
Regards
Rishav

The Business-System from SLD canu00B4t read

Hello,
during export from an configuration object folloging exception occure:
"The Business-System from SLD can´t read"
It seams all OK ...
Thanks in advance,
Frank

Did you change the name of the Business System in the past? Then you need to keep the old Business System name in the SLD, as during exporting and importing of configuration objects the history of the objects is checked as well.
Regards
Stefan

No Installed Products while adding Technical System in SLD!

Hello,
I am trying to add Technical Systems in SLD. when I was at the point to select the software components, I am not seeing any installed products on the left side.
I already gave the ABAP system details in the previous screens, in this wizard.
Why is it that I am not seeing any installed products.
Thanks
Srinivas

Hi Jazz,
Here are the errors I am getting.
Import finished with 72 errors
Errors:
CIM_ERR_FAILED: CIM qualifier Alias is currently not supported by this implementation
QUALIFIER.DECLARATION Alias
CIM_ERR_FAILED: CIM qualifier BitMap is currently not supported by this implementation
QUALIFIER.DECLARATION BitMap
CIM_ERR_FAILED: CIM qualifier BitValues is currently not supported by this implementation
QUALIFIER.DECLARATION BitValues
CIM_ERR_FAILED: CIM qualifier Composition is currently not supported by this implementation
QUALIFIER.DECLARATION Composition
CIM_ERR_FAILED: CIM qualifier Counter is currently not supported by this implementation
QUALIFIER.DECLARATION Counter
CIM_ERR_FAILED: CIM qualifier Delete is currently not supported by this implementation
QUALIFIER.DECLARATION Delete
CIM_ERR_FAILED: CIM qualifier Deprecated is currently not supported by this implementation
QUALIFIER.DECLARATION Deprecated
CIM_ERR_FAILED: CIM qualifier DN is currently not supported by this implementation
QUALIFIER.DECLARATION DN
CIM_ERR_FAILED: CIM qualifier Expensive is currently not supported by this implementation
QUALIFIER.DECLARATION Expensive
CIM_ERR_FAILED: CIM qualifier Experimental is currently not supported by this implementation
QUALIFIER.DECLARATION Experimental
CIM_ERR_FAILED: CIM qualifier Gauge is currently not supported by this implementation
QUALIFIER.DECLARATION Gauge
CIM_ERR_FAILED: CIM qualifier Ifdeleted is currently not supported by this implementation
QUALIFIER.DECLARATION Ifdeleted
CIM_ERR_FAILED: CIM qualifier In is currently not supported by this implementation
QUALIFIER.DECLARATION In
CIM_ERR_FAILED: CIM qualifier Invisible is currently not supported by this implementation
QUALIFIER.DECLARATION Invisible
CIM_ERR_FAILED: CIM qualifier Large is currently not supported by this implementation
QUALIFIER.DECLARATION Large
CIM_ERR_FAILED: CIM qualifier MaxValue is currently not supported by this implementation
QUALIFIER.DECLARATION MaxValue
CIM_ERR_FAILED: CIM qualifier MinLen is currently not supported by this implementation
QUALIFIER.DECLARATION MinLen
CIM_ERR_FAILED: CIM qualifier MinValue is currently not supported by this implementation
QUALIFIER.DECLARATION MinValue
CIM_ERR_FAILED: CIM qualifier Nonlocal is currently not supported by this implementation
QUALIFIER.DECLARATION Nonlocal
CIM_ERR_FAILED: CIM qualifier NonlocalType is currently not supported by this implementation
QUALIFIER.DECLARATION NonlocalType
CIM_ERR_FAILED: CIM qualifier NullValue is currently not supported by this implementation
QUALIFIER.DECLARATION NullValue
CIM_ERR_FAILED: CIM qualifier Octetstring is currently not supported by this implementation
QUALIFIER.DECLARATION Octetstring
CIM_ERR_FAILED: CIM qualifier Out is currently not supported by this implementation
QUALIFIER.DECLARATION Out
CIM_ERR_FAILED: CIM qualifier PropertyUsage is currently not supported by this implementation
QUALIFIER.DECLARATION PropertyUsage
CIM_ERR_FAILED: CIM qualifier Provider is currently not supported by this implementation
QUALIFIER.DECLARATION Provider
CIM_ERR_FAILED: CIM qualifier Read is currently not supported by this implementation
QUALIFIER.DECLARATION Read
CIM_ERR_FAILED: CIM qualifier Schema is currently not supported by this implementation
QUALIFIER.DECLARATION Schema
CIM_ERR_FAILED: CIM qualifier Source is currently not supported by this implementation
QUALIFIER.DECLARATION Source
CIM_ERR_FAILED: CIM qualifier SourceType is currently not supported by this implementation
QUALIFIER.DECLARATION SourceType
CIM_ERR_FAILED: CIM qualifier Static is currently not supported by this implementation
QUALIFIER.DECLARATION Static
CIM_ERR_FAILED: CIM qualifier Syntax is currently not supported by this implementation
QUALIFIER.DECLARATION Syntax
CIM_ERR_FAILED: CIM qualifier SyntaxType is currently not supported by this implementation
QUALIFIER.DECLARATION SyntaxType
CIM_ERR_FAILED: CIM qualifier Terminal is currently not supported by this implementation
QUALIFIER.DECLARATION Terminal
CIM_ERR_FAILED: CIM qualifier TriggerType is currently not supported by this implementation
QUALIFIER.DECLARATION TriggerType
CIM_ERR_FAILED: CIM qualifier UnknownValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnknownValues
CIM_ERR_FAILED: CIM qualifier UnsupportedValues is currently not supported by this implementation
QUALIFIER.DECLARATION UnsupportedValues
CIM_ERR_FAILED: CIM qualifier Write is currently not supported by this implementation
QUALIFIER.DECLARATION Write
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property ScheduledStartTime
CIM_Job
CIM_ERR_FAILED: Unknown qualifier Write found in property DeleteOnCompletion
CIM_JobSettingData
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_ConcreteJob: CIM_Job
CIM_ConcreteJob
CIM_ERR_FAILED: Unknown qualifier Write found in property EnabledDefault
CIM_EnabledLogicalElement
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_System
CIM_ERR_FAILED: Unknown qualifier Write found in property PrimaryOwnerName
CIM_Service
CIM_ERR_FAILED: Unknown qualifier Gauge found in property AvailableSpace
CIM_FileSystem
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property array PowerManagementCapabilities
CIM_ComputerSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property NumberOfUsers
CIM_OperatingSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property FileSize
CIM_LogicalFile
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property PowerManagementSupported
CIM_LogicalDevice
CIM_ERR_FAILED: No such override property in superclass CIM_System: EnabledState
CIM_ApplicationSystem
CIM_ERR_FAILED: Unknown qualifier Gauge found in property WorkingSetSize
CIM_Process
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_LogicalPort: CIM_LogicalDevice
CIM_LogicalPort
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_Processor: CIM_LogicalDevice
CIM_Processor
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkAdapter: CIM_LogicalDevice
CIM_NetworkAdapter
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class CIM_NetworkPort: CIM_LogicalPort
CIM_NetworkPort
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_OSProcess
CIM_OSProcess
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FRUIncludesProduct
CIM_FRUIncludesProduct
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_ProductParentChild
CIM_ProductParentChild
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_FileStorage
CIM_FileStorage
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class CIM_ProvidesServiceToElement
CIM_ProvidesServiceToElement
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_RunningOS does not exist.
CIM_RunningOS
CIM_ERR_FAILED: Unknown qualifier Composition found in class CIM_SystemDevice
CIM_SystemDevice
CIM_ERR_FAILED: Class CIM_OperatingSystem referenced by association CIM_BootOSFromFS does not exist.
CIM_BootOSFromFS
CIM_ERR_FAILED: Unknown qualifier Deprecated found in property CompiledBits
SAP_BCApplicationServer
CIM_ERR_FAILED: Unknown qualifier STATIC found in property AccSldModelVersion2
SAP_ACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterface: CIM_NetworkPort
SAP_ACENetworkInterface
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_JCODestination
SAP_JCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_MsgServJCODestination
SAP_MsgServJCODestination
CIM_ERR_FAILED: Unknown qualifier Deprecated found in class SAP_AppServJCODestination
SAP_AppServJCODestination
CIM_ERR_FAILED: Class SAP_ACENetworkInterface referenced by association SAP_ACENetworkToNetworkInterface does not exist.
SAP_ACENetworkToNetworkInterface
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_ACEAssociatedVirtualizationManager does not exist.
SAP_ACEAssociatedVirtualizationManager
CIM_ERR_FAILED: Class SAP_ACEEngine referenced by association SAP_HostedACEEngine does not exist.
SAP_HostedACEEngine
CIM_ERR_INVALID_SUPERCLASS: No such superclass for class SAP_ACENetworkInterfaceComponent: CIM_SystemDevice
SAP_ACENetworkInterfaceComponent

After BI 4.1 configuration in SOLMAN - error message "The systems you selected do not contain any software components currently supported by E2E Workload Analysis"

Hi All,
I'm trying configure E2E monitoring. I configured all necessary steps, I can see my BI 4.1 system in SLD, also in SOLMAN, all “lights” are green. But if I start Root Cause Analysis>> Ent-to End Analysis>> My system>> Workload Analysis, I see this error "The systems you selected do not contain any software components currently supported by E2E Workload Analysis".

It would be better if you can raise the question at Remote Supportability and Monitoring Tools
and or comment in the blog post How to generate and consume an E2E trace with BI4.x (for non-SolMan landscapes)
created by Toby Johnston
Do go through the note 1871260 - The systems you selected do not contain any software
components currently supported by E2E Workload analysis for SAP HANA
Hope they help.

In my solman system , DBACOCKPIT , "SLD System Import" tab is inactive

Similar Messages

Maybe you are looking for