SLD configuration in already existing Solman system

Hello,
We already have dedicated central SLD in our landscape but now we want to configure SLD in already existing SOLMAN and decommission the existing one.
Can anyone suggest how to configure SLD in already installed SOLMAN (may be high level step by step process)?
Thanks & Regards,
NK

Hi Nitin,
What will be the purpose of SLD of solution manager ?
eg. 1631346 - Solution Manager 7.1: SLD configuration for PI monitoring
You can add this SLD with a higher rank than the older SLD but lower than LMDB in solman_setup.
Refer:Step By Step Process to configure SLD, MOPZ & EWA in Solution Manager 7.1 SP 8
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/content.htm
Divyanshu

Similar Messages

  • SLD configuration for DXI / PXI technical systems

    Hello,
    we have a problem when transporting XI configuration objects from XI dev to XI prod. The transport objects arrive in XI prod, but the name of the business system (for the SAP backend system) is not converted from dev business system (T01CLNT010) to prod business system (P01CLNT01) although the transport target for T01CLNT010 business system was set correctly (we are using business system groups Dev and Prod). And the "related integration server" for T01CLNT010 was also set correctly to DXICLNT010.
    But then I noticed that the technical system for the DXI (XI Dev) is configured as follows:
    TMS Domain ("DOMAIN_PXI") and TMS Transport Group Name GROUP_PXI ("GROUP_PXI") have the same values as PXI. Is that correct ?? We are using file transport, not CMS.
    Another strange effect is that when I set the group in business system DXICLNT010 to Dev, that is also applied to business system PXICLNT010 ! Which is of course not what I want.
    I assume I have to associate DXICLNT010 to Dev and PXICLNT010 to Prod, same as for T01CLNT010 / P01CLNT010. Correct ? Or does the group in the XI business systems not matter ?
    Can anyone post an example of a working SLD configuration with two XI system dev and prod ? What values do I have to use in the XI technical and business systems, so that the transport will work ?
    CSY

    There's obviously something wrong in the SLD configuration for the exchange infrastructure systems. The error you're describing (one system pointing to another) usually occurs when one system is generated through homogeneous system copy of another system (was that your case?). I've seen that behaviour once and they corrected it by manually deleting the exchange infrastructure systems from SLD and creating them again from scratch.
    Anyway, I highly recommend you to get an expert NW Basis consultant to realize a check in it before you proceed any further.
    Aside of that, you're correct in your assumptions.
    Your config in SLD should be like:
    DEV_GROUP:
    - DXI
    - T01
    PRD_GROUP:
    - PXI
    - P01
    It's always 1 XI BS per group.
    Also, if you use separate SLDs for XI Dev and XI Prd, you have to make sure that this configuration is reflected in both SLDs. So, if you make it one SLD instance, you must generate a delta export zip file from the SLD where you did the configuration and import this zip file in the other SLD instance.
    If you use a central SLD, then it's not necessary.
    Regards,
    Henrique.

  • Trusted system entry already exists for system SOL

    Hi,
    Im trying to add a second trusted system with smt1 transaction but the thing is that i've already have an identical SID for another system so i get the "Trusted system entry already exists for system SOL" message.
    is there any way to solve this??
    thanks in advance.
    regards.

    In  SM59 - in the RFC in question - Press "Technical Settings" tab - then press "Yes" to Load Balancing - this will populate the "Target Host" field.
    Then make sure that you here enter the system data for the Target System (Default it will display the Host System data which you will need to replace)
    Then go back to SMT1 - Press the "Create" button - and in the Wizard you enter the RFC connection as before... Now it should work.
    Regards,
    Lars

  • SLD (CIM_ERR_ALREADY_EXISTS : INSTANCE ALREADY EXISTS )

    Hi All,
    While creating SLD at Step 6
    Select one or more Software product and then software component that are installed in this system
    I have selected below items
    Installed product                    Installed Component
    SAP Web AS 7.00 ;             SAP J2EE ENGINE 7.00
    I am getting an Error
    CIM_ERR_ALREADY_EXISTS-Instance already exists.
    Thanks in advance
    Arun

    See
    Re: CIM_ERR_ALREADY_EXISTS: Instance already exists: .........
    Regards,
    Slava

  • How many SLD's require for 2 solman system requirements?

    Scenario1:
    One solman system for entire landscape->One SLD is required.
    Is this SLD should be a seperate system or can be within solman?
    Scenario2:
    One solman system for DEV/QAS and other solman system for PRD.
    How many SLDs are required? Can we manage with single SLD?
    If two SLDs, Then both should be seperate systems. i.e, One SLD -> DEV/QAS Solman, Another SLD ->PRD Solman.
    If only one SLD, Then it should be seperate system or can be within solman?
    We do have EP in client enviroinment. Can we use SLD of EP?

    Hi,
    you can use one SLD for all your systems if you want. You can either use an existing one or the one which comes with Sol Man. That's up to you.
    Any scenario is possible.
    /cheers

  • SLD configuration to transport Third Party System ID Objects

    Hi expert,
    I have configured SLD group according to below link .
    Transport Targets and Groups in the SLD
    for PI and ECC system i have assigned transport target.
    we have third party system also defined in SLD there name is same in PI dev ,PI quality and PI production.
    how to proceed  to set transport target for third party system if name is same ?
    Thanks,
    Dipak Patil

    Hi Dipak
    If your third party system has the same name in all other environments, you do not need to set transport target. Then there won't be automatic translation of the Business System name during import to the other environments.
    Rgds
    Eng Swee

  • Create new interface design for configuration copying already existing

    Does anybody know how to do it?

    2. Since the IDOCs are already mapped to Interface A, will they be also processed to Interface B if I reuse them ??
    Interface A and Interface B will work as two different scenarios (Since Receiver Determination is reused.....you will have Message Branching......will see this in SXMB_MONI when you test the scenario(S))
    If you want to avoid any confusion then have conditions defined in Receiver Determination (if not considered then ask your business person to have a look into this approach).....this will avoid unnecessary execution of both the interfaces (A and B).
    Regards,
    Abhishek.

  • ChaRM migration to New Solman System

    Hi,
    We are planning to Migrate old Solman system ChaRM to new Solman ChaRM.
    Now how can I migrate RFCs & CDs to new Solman system ChaRM.
    Regards
    P K

    Hi PK
    There is no tool for moving the SLFN documents from one solman to the other. The only option to keep the already created tickets is to upgrade the the existing solman system to release 7.1.
    In SOlman 7.1 SM* transaction types are comming so during the upgrade we don´t make any changes to the old transaction types like SLFN, so the upgrade should not change your current configuration in solman 7.0 for incident management.
    You will not have any impact on Service Desk when using the old transaction type SLFN.
    So there can be only one recommendation for your situation:
    Perform an UPGRADE and please don't go for a fresh installation with data migration afterwards.
    There is no easy transfer of CRM document (as incidents, change requests, issues, top issues, ...) available.
    Advantages of the upgrade:
    - standard procedure
    - configuration and data is available after the upgrade
    The solman 7.1 is coming with new transaction types that you need to customizing  and it is not touching the old transaction types existing in solman 7.0.
    Please, take a look at this:
    http://scn.sap.com/docs/DOC-30133
    Also check below note which answers few FAQ's:
    1567003:  FAQ: ST710 Incident Management Frequently Asked
    Check below Wiki as well:
    http://wiki.sdn.sap.com/wiki/display/SAPITSM/Configuration+and+Administration+of+ITSM
    (all in one line)
    And select Configuration Guide - Application Incident Management
    Also check the External Service Desk Functionality.
    Please follow the path to the nodes listed below.
    SAP Solution Manager Implementation Guide
      SAP Solution Manager
        Capabilities (Optional)
          IT Service Management
            External Integration
                 Service Desk
                     External Service Desk
    Thanks
    Vikram

  • Excise invoice already exists  error in J1IS

    Hello
    Created the Subcontracting PO , and Issue the material to vendor ( mov type 541) with payment of duty, after this created the Excise invoice with T.code J1IS, system was generated the Excise entries in table J_1IEXCDTL and J_1IEXCHDR.
    After that we have reversed the excise entries, so now we got "R"Indicator in status field in above said table J_1IEXCDTL.
    Now system should allow me to create one more excise invoice with same Material document number but sytem was giving error message that "excise invoice already exists"
    Why system was allowing us to create new excise invoice?
    Regards
    sapman man

    hi
    you can't create another Excise document with same Material Doc.Because for this Material document already Excise document exit even though it is reversed.i think you have to delete Material document from J_1IEXCDTL and J_1IEXCHDR. then try to create new
    regds
    Rami

  • Java Add-In installation on a existing ABAP System (MSCS Cluster)

    Hi all
    we try to install a Java Add-In for a already existing ABAP System with
    SAPinst. The ABAP System is a NetWeaver2004s SR1 System in a MSCS Cluster.
    We have the Problem that we can´t choose the Installation Drive during
    the SAPInst Define Parameter Step during the "Central Services Instance (SCS) Java Add-In" Installation.
    But in the Installation Manual for
    NW2004s Java AS in Chapter 4.3.2 is stated:
    "Caution: You must install it on the same shared disk as the ASCS instance."
    If I run the Installation, the SCS will be installed on the local disk E:
    beside the Central Instance. But it need to be on the shared Disk P:
    beside the ASCS installation. How can I control this?
    Stefan

    obviously the network share saploc is existing in your system an pointing to a local device.
    Delete the local saploc share, install SCS instance, run MSCS first node, additional node, create the local share saploc again (don't forget to set permissions on the share, the default permission did only allow Read vor Everyone) and proceed with installation.
    There is a note in creation for this issue.
    peter

  • ORA- 31684 Object type already exists while import

    Hi All,
    I wrongly imported a user schema "AP_PD@SRV01" to user "A_IT@SRV02" (Instead of "AP_IT@SRV02").
    User AP_IT and Tablespaces are already exists and used remap option while import.
    remap_schema=AP_PD:A_IT (instead of mapping to user AP_IT, I misspelled as A_IT)
    remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
    After successful import to "A_IT@SRV02", I deleted the user "A_IT"
    SQL> DROP USER A_IT CASCADE;
    I restarted the import to the correct user schema .. i.e AP_IT@SRV02
    remap_schema=AP_PD:AP_IT remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
    and import was completed with the following errors
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"AP_IT" already exists
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
    ORA-31684: Object type PACKAGE:"AP_IT"."DBMS_NUMSYSTEM" already exists
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
    ORA-31684: Object type PACKAGE_BODY:"AP_IT"."DBMS_NUMSYSTEM" already exists
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 3 error(s) at 07:53:32
    My questions ...
    1.Can I assume that import was success as these objects were already exists.
    2.Does this effect in anyway to the end users if I ignore this errors assuming import was successful.
    3.If import is not a success then what should be my next step to import successfully.
    Thanks.

    Ven wrote:
    Hi All,
    I wrongly imported a user schema "AP_PD@SRV01" to user "A_IT@SRV02" (Instead of "AP_IT@SRV02").
    User AP_IT and Tablespaces are already exists and used remap option while import.
    remap_schema=AP_PD:A_IT (instead of mapping to user AP_IT, I misspelled as A_IT)
    remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
    After successful import to "A_IT@SRV02", I deleted the user "A_IT"
    SQL> DROP USER A_IT CASCADE;
    I restarted the import to the correct user schema .. i.e AP_IT@SRV02
    remap_schema=AP_PD:AP_IT remap_tablespace=AP_PD_DATA:AP_IT_DATA remap_tablespace=AP_PD_INDEX:AP_IT_INDEX
    and import was completed with the following errors
    Processing object type SCHEMA_EXPORT/USER
    ORA-31684: Object type USER:"AP_IT" already exists
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
    ORA-31684: Object type PACKAGE:"AP_IT"."DBMS_NUMSYSTEM" already exists
    Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
    ORA-31684: Object type PACKAGE_BODY:"AP_IT"."DBMS_NUMSYSTEM" already exists
    Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 3 error(s) at 07:53:32
    My questions ...
    1.Can I assume that import was success as these objects were already exists.
    2.Does this effect in anyway to the end users if I ignore this errors assuming import was successful.
    3.If import is not a success then what should be my next step to import successfully.
    Thanks.You mentioned AP_IT schema and tablespaces already exist before doing first import itself.
    Did you check the list of objects in AP_IT schema before performing import?
    The following error is just an informational message and can be ignored:
    ORA-31684: Object type USER:"AP_IT" already exists
    But, the other 2 errors which says that package +"AP_IT"."DBMS_NUMSYSTEM" already exists+ means you have package in AP_IT schema and it wasn't replaced from the dump you imported. If you need the package from the dumpfile, you can drop the package and can import PACKAGE alone.
    Hope this helps.
    Regards,
    Murali Mohan

  • ** 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

  • PROTOCOL.MSGID_EXISTING_INBOUND: Message already exists in called system

    Hello all,
    in our receiver system we get follow error:
    PROTOCOL.MSGID_EXISTING_INBOUND: Message already exists in called system
    The message is in status: message already processed.
    But sure we sent the message only once and the message aren't processed.
    The receiver system is a R/3 with a WAS 6.20 (Plug - In APPINT 200_620 PL 005).
    We trigger the message from our SAP XI 3.0 to R/3 via proxy.
    The proxy is follow configured:
    Transport Protocol: HTTP 1.0
    Message Protocol: XI 2.0
    Adapter Ingine: Integration Server
    Addressing Typ: HTTP Destination
    http Destination: D43CLNT002_HTTP
    Can anybody helps me ?
    Thanks

    Hello all,
    first Proxy from R/3 to SAP XI 3.0 works properly.
    In smq2 and sm58 aren't entries.
    The message are arrived the target system. But unfortunately with status:
    "Message already processed"
    In the error code on the target System SAP R/3:
      *<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>*
    *- <!--  Call Integration Server*
      -->
    - <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
      <SAP:Context />
      <SAP:Code p1="47BC9D365AC8451AE10000000AA001AA" p2="CENTRAL" p3="" p4="">PROTOCOL.MSGID_EXISTING_INBOUND</SAP:Code>
      <SAP:Text language="EN">Message ID 47BC9D365AC8451AE10000000AA001AA already exists in called system (pipeline CENTRAL)</SAP:Text>
      </SAP:ErrorHeader>
    In SAP XI the message was successfull processed to R/3.
    Thanks

  • Error creation of JCO connection: System Already Exist

    Hi Experts,
    We have created the SLD connection to the ECC6.0 from the Portal 7.0.
    Created one JCO connection using that SLD successfully for the Clinet 100.
    Now we required to create one more JCO Connection for client200 also. But it is giving the Error that
    System Already Exist.
    How can we resolve this. When we create the JCO connection for one client, con't we create one more JCO connection for the same system for the differt client or not?
    If so How do it?
    Regards

    I think you can add one more client in the existing connection. well, I am not sure about that even.
    nikhil

  • SLD Configuration to New Technical System is failed.

    When iam trying to create a new technical system in sld after selecting the product i got this error.Please help me on this iam new to Portal SLD.
    CIM_ERR_ALREADY_EXISTS: Instance already exists: SAP_InstalledProduct.CollectionID="24457af4-fdf7-e5f4-63ac-00f98079457a",ProductIdentifyingNumber="01200615320900001296",ProductName="SAP ERP",ProductVendor="sap.com",ProductVersion="2005",SystemID="STV.SystemNumber.0020620473.SystemHome.stravist"

    Hi,
    As per the error - the technical system already exists in the SLD. You could check in the list of existing technical systems if system STV already exists. If you want, use the same entry or else delete it first and try registering the system.
    Also, why are you recreating the system manually now? Was there a restore, system copy or any other activity?
    Manually creating the is not recommended. Auto register the system to SLD via RZ70 for ABAP or SLD Data supplier in Visual Admin for Java systems.
    Regards,
    Srikishan

Maybe you are looking for