NW-Release of Technical System SID of managed system - is unidentifiable!

Hi,
Does anyone encountered this issue before when generating stack file?
I am going to generate the stack file for SAP Enhancement Package 7 for SAP ERP 6.0 and SAP NetWeaver 7.4 
but during phase 2.2 it pops up the error "NW-Release of Technical System <SID of managed system>- is unidentifiable!"
I had read through note 1754904, but I could not found any SAP LiveCache under ERP system under SMSY.
Thanks and regards,
Shu Jie

Hi Shu Jie,
Please goto LMDB, then select technical system -> choose your system -> check the software field whether it has updated with the information of NW
if not, please make sure you added the system in SLD and SLD sync with LMDB.
please refer Landscape Management Database (LMDB) – FAQ and Troubleshooting for the LMDB - Managing System Landscape Information - SAP Library
Thanks
Jansi

Similar Messages

  • Technical Systems in Managed System Configuration greyed .

    Hi,
    I upgraded ST-SER to 701_2010_1 SP0 and in the process of upgrading
    this tool I had to also patch other components like ABAP,BASIS etc as
    pre-requisites for this.
    As this involved all the components to be patched, I
    executed the initial,Basic configuration in solman_setup and everything
    is fine.
    In Initial I executed only the read SLD and skipped the other steps as
    the other steps have been already executed after install of solution
    manager .
    In Basic Configuration I have executed all steps and everything has
    executed successfully.
    The problem is in Managed system configuration.
    I have the Wily Introscope Manager Console showing all the statistics
    of Agents and all Agents are attached.
    The problem I see is first thing is the technical setting in the
    Managed system diagnostics are greyed why is it ?
    Second is when I execute the Managed system Diagnostics configuration , the first step Wily host agent fails all other steps are okay.
    The error in this step is "No connection to any Wily Enterprise Manager"
    Appreciate any advise.
    Thanks,
    Misba

    Hello Diego,
    I started getting this error only after I upgraded the tools, even now the Wily is up and running and I can see the dashboard with all the live diagnostics graphs and statistics for ABAP & JAVA. All the steps have executed successfully except this one step. Even trusted RFC's are okay. This was an established system with all configurations.
    So I am surprised what I am missing.  Can you please explain to me more about how I can see " http://<ip>:<port>/SMD under "managed systems" ->Introscope Agent ".
    All Agents are attached and in Agent adminstration I can see all the Agents online.
    Thanks,
    Misba

  • Technical Systems Not appearing  in Managed Sytem Configuration

    Hi Experts,
    I am doing Solman_setup after upgrade.I am in Managed system configuration step.I have synchronized Abap and java systems through RZ70 and NWA respectively to Solamn Local SLD and hence they are also appearing in LMDB (technical system tab).However when I am opening Managed System Configuration page  no technical system (Abap or Java) is   found (except solman Abap and solman Java) technical system tab page (find the screen shot for ur convenience ).Can any one help me out to find the solution.
    Thanks
    Aditya Roushan

    Hi
    Please check the Synchronization job  between SLD and LMDB is running fine.
    Did you finish all the steps(SLD Setup) System Preparation?
    If the issue still exist please de actviate the SLD and recreate again
    Run the SLD and LMDB Sync job again after the recreation Step: SLD Setup
    Kind Regards,
    Phaneendra Kakani

  • Technical System (Application Server ABAP) - problem with data supplier

    My system had problems, I believe with the Data Supplier in LMDB
    there are errors
    How can I update / re-add in the SLD/LMDB data supplier?
    And how can you get it working correctly providers who do not receive the data (though the system sees them)

    Hi Michael,
    You can push an update from Solution Manager (the data supplier) to the SLD in transaction RZ70. There should be a button labeled "Start Data Collection and Job Scheduling". If your jobs are scheduled and everything is set up correctly, then starting your data collection will force an update ahead of schedule. (By default, the update is scheduled every 720 minutes -- i.e. 12 hours).
    On the Java side, you need to push via the Visual Administrator (when you're at NW 7.02, that changes in 7.3 to the NWA), but you didn't ask that.
    Typically, LMDB grabs an incremental update from SLD every 10 minutes or so. Check for a job called SAP_LMDB_LDB_0000000001. If your SLD-LMDB connection is not working properly, you may need to reset it. (SOLMAN_SETUP (as solman_admin or equivalent). Then system preparation -->5 Prepare Landscape). See SAP help on this Synchronization Between SLD and LMDB - SAP Solution Manager - SAP Library.
    Also, on the first screen you showed, System Landscape Technical System - Display, if you click Edit, then click on the advanced button, there is an option to Resynchronize Technical System from SLD. I haven't tried that, but that may actually be what you're looking for.
    I hope this helps!
    Best regards,
    --Tom

  • AS JAVA technical system not updated/registered in SLD

    Hi,
    We have setup the SLD bridge connection from our SLD with 7.0 SAP J2EE
    server which is our local SLD to SLD with 6.40 SAP J2EE server which is the master or central SLD. Actually we have this set up, that we have configured a local SLD for our Netweaver 2004s SR2 or Netweaver 7.0 system and connect it to the central SLD which is also a Netweaver system but of lower release, Netweaver 2004 SR1.
    Since Netweaver contains both ABAP and Java, I can see that our WAS ABAP technical system (of the SLD 7.0) was
    succesfully registered and updated on the central SLD 6.40 but I cannot
    register or update the WAS JAVA technical system (of the SLD 7.0) in the central SLD 6.40, but it can be updated in our local SLD which is then connected to the central SLD as mentioned.
    Since my update for the WAS ABAP was already working and its updated
    in the central SLD 6.40, what can we do to achieve the same result for the WAS
    JAVA? Because if it works with WAS ABAP, what is wrong then with WAS JAVA? What might be the cause or some other configurations to be made?
    Also can we synchronize the CIM updated with all the SLD? We want to
    see if we can just update the CIM content of SLD 6.40 and pushed this
    with the other SLD on the system e.g. SLD of 7.0.

    Hi,
    I think you should certain configurations for your system to be listed under SAp Java systems.
    1.Go to visual admin,c:\usr\sap\SID\JCxx\j2ee\admin
    run go.bat.
    Then go to services-----SLD Data supplier.
    go to Http settins under that,enter the details of central SLD you want to connect,
    hostname,http port,sld admin user and password.save it.
    go to CIM client settings,enter the same details there and save.
    Then check CIM client generation  test.it should be sucessfull.
    then trigger SLD data transfer at the top left corner.
    it also should be sucessfull.
    Then your system will be listed.
    2.may be you have to create a role called Lcr administrator with all Lcr* actions assigned to it.
    then this Lcr administrator role should be assigned to ur administrator user.
    hope this works.........
    reward points if helpful............

  • SMSY Technical System Delete and Clean-up

    I need to completely delete a SID from Solution Manager: SMSY technical system, projects, logical components,ChaRM, CCMS, tansport routes, SMD, SLD, etc. I am looking for clean-up documentation. Is there a document(s) which will describe a logical progression to remove an obsolete SID? Logically, removing CCMS and Wily monitoring can occur first. A manual delete of the technical system from the SLD next? Then delete projects and logical components? A good chronological order for steps like these would be very helpful. I'd like to avoid problems with workflow and system batch jobs.

    Hi Loenard,
    I don't think there is any job or program to do this. Best thing to do is if your system to be deleted is still running and is still sending data to solman SLD from RZ70 then disable this by removing the hostname data and save it. this isolates the system to be removed. next in SMSY, remove system from the product landscape from "logical components" list and then you can remove the system from product systems under "landscape components". here you may need reload the product landscape in solution landscape if it doesn't go away itself. if it gives issues then you can use the "where used" button and that tells you where it is still assigned and remove it from there.
    hope this helps

  • Technical System Not reporting to Master SLD

    Hi
    We have  multiple SLDs in our landscape for each landscape. We have a Central SLD in our Solutiion Manager systems. All the SLDs are configured to transfer the data to the master SLD through the Data Bride which reports everyday.
    One of the SLD reports only ABAP systems to the master SLD. I dont see any java systems reporting to the master SLD from. The other SLDs reports both ABAP and JAVA systems well. SO I am wondering what could be the reaon for not reporting only Java systems that to onlyfrom one SLD system.
    Mahesh Shetty

    Hi Mahesh,
    There is a lil difference. For a double stack target system, on the ABAP side, we maintain SLD connection details in RZ70, SLDAPICUST and RFCs LCRSAPRFC and SAPSLDAPI. Likewise, in Java side of the target system, the SLD Data Supplier entry in Visual admin needs to be maintained too. This will ensure the correct functioning of SLD for both ABAP and Java stack.
    Once the above configurations are maintained correctly, in SLD-> Technical systems-> dropdown WEB AS ABAP will have the ABAP entry and WEB AS java dropdown will have the Java entries.
    Rgds,
    Soujanya

  • Role import uses technical system id?

    Part of our portal content comes from BW - BEx applications are developed, and placed into a role on the BW side.  We were planning on importing the BW roles as worksets, followed by placing the worksets into a role that will fit into our portal navigation structure.
    Once thing that I noticed was that the system alias used to import the BW content uses the technical name of the remote system (XXX100, for example), instead of the system alias assigned to the system object from whence the content comes from.
    We were planning on exporting this content from our development portal, and importing it into each of the follow-on systems.  However, since each iView references a system based on the original technical system name, I'm left with these possible solutions:
    1. Leave the content as it, and just assign a technical system name as a system alias for the following on environments.  Very ugly, and confusing.
    2. Import the content, but manually change each iView to use the correct system alias.  Very time consuming, especially as the amount of content increases.  I could programatically alter the PCD to change the alias, but I would rather not do that since it's an extra step, and would involve some custom coding just to fix remote role imports.
    3. Import the roles in each follow on environment - also ugly, since I don't want to alter the content past development.  This would be circumventing our testing strategy, not to mention our change management processes.
    Ideally, I would like the content to be imported using the correct system alias (SAP_BW, for example).  Is there a way to do this, or am I just stuck?
    How are other people dealing with the importation of BW roles into the portal?

    Hi Ken,
    Are you sure about this? When you imported your roles from BI did you select the SAP_BW system alias or did you select a system alias XXX100?
    Also under your option 2 you can should be able to change the system property for all the iviews in one fell swoop by using the Multiple Property Replacement under Content Administration.
    Good luck,
    Bert

  • Error while creating Technical System

    Hi
    i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
    When i press next, It is throwing this error. Do anyone have any idea about this.
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
        at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
        at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
        at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        ... 27 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
    Web Dynpro Code Generation Infos
    sap.com/tcsldwd~main
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~landscape
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcsldwd~businesssystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~technicalsystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    sap.com/tcsldwd~softwarecatalog
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~namereservation
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    Detailed Error Information
    Detailed Exception Chain
    java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
         at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
         at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         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 in Advance
    Vijay Raheja

    HI Michal Krawczyk,
    Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
    It is asking me for :
    -URL of target SLD system, e.g. http://host:port/
    -User
    -Password.
    What should i give here. WHat will be port for R/3 system to which i want to connect.
    Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
    Thanks,
    Vijay Raheja

  • Doubt regarding creation of technical system.

    Hi i am doing interface between R3 and JDBC(third party)
    1)I  have created one technical system(type as web as abap) for R3 and one technical system(type as third party) for JDBC.
    2)but we usually download one software component in IR and we create namespace under downloaded software component(swc). we do create all objects for this interface is under this namespace.
    3)when we create technical system it will ask us install product, let us say we assign a prodocut called xyzr3 for Tecnical syste(TS r3), under this we have assigned a software componet(swc) called  xyzr3sw.
    4) when we create technical system for third party it will ask us to installed product, should i create new product for this technical system or do i need to assign a product xyzr3 witch is already created for R3 TS(tecnical system)?
    5)bcz we are using only one namespace for this interface whitch is created under xyzr3sw(sc of r3 ts, type as webase abap)
    6) let us say , we have created new product and swc for third party TS, any way we are not importing this sw component in IR, bcz we have imported xyzr3sw(sc of product, ts of r3), so do i need to assign same product xyzr3(witchi is creted for R3) , xyzrsw (swc created for R3) to ts (ts of type thired party)? bcz we are importing only one swc in IR to develop the interface(one name space)
    thanks,
    dhanush

    Hi Dhanush..
    4) when we create technical system for third party it will ask us to installed product, should i create new product for this technical system or do i need to assign a product xyzr3 witch is already created for R3 TS(tecnical system)?
    Yes. I think you should create new product here..
    6) let us say , we have created new product and swc for third party TS, any way we are not importing this sw component in IR, bcz we have imported xyzr3sw(sc of product, ts of r3), so do i need to assign same product xyzr3(witchi is creted for R3) , xyzrsw (swc created for R3) to ts (ts of type thired party)? bcz we are
    importing only one swc in IR to develop the interface(one name space)
    Yes. You do not need to import new software component version created for Third party.
    But I'll suggest here..since you want to use JDBC on the receiver side...you can just create Business Service ( where you do not have to specify technical details) and you can used as a receiving system. No need to create 3rd party here..
    Let me know if you need more details.
    Nilesh

  • Technical system for idoc

    i am doing a file2idoc scenario.i want to crete a technical system as web-as-abap.but we are having ecc6.0.here  we are having both abap & xi .here those are having  different host name.here in this scenario i am using idoc as receiver system.so will i use hostnbame of abap or xi in  technical system(web-as-abap)??

    Hi Michal,
    Thanks for reply.
    Regd Logical System, i did like this.
    T-Code: SALE
    Copied 'Logical System' name which is assigned for Client 800.
    and While creating SLD,
    Technical System: ( for Receiver IDOC)
    1.Web As ABAP
    2.Web AS ABAP Name (SID): FIC ( i don't know where to find SID , somebody asked me to give my R/3 System name.
    Note:Other guy told me like this to find SID, T-Code:SM51
    There will be name Seperated by 2 Underscores, the part next to 2nd underscore is SID. So, in my R/3 System, its like FIC_FIC_00, but when i tried to give 00 as SID, its not accepting, so i gave FIC)
    Installtion Number:    (i gave)
    Database hostname: FIC
    3. In next page Instance Number:00
    4. In next page Host Name: FIC and clicked Add
    5. Client: 800
    Logical System: T90CLNT090 ( which is from T-Code Sale)
    Business System:
    1. New_BS_IDOC
    2. Selected the Technical System created above.
    Still cannot find in "Adapter Specific Identifiers"
    <i>>>>you need to have logical system for your r3 business system (which you put in header mapping - sender service of the receiver agreement)</i>
    do i need to provide, receiver Buss System for Sender Service of Receiver Agreement?
    and i looked at weblog given, i am unable to find anything under T-Code IDX2, its empty..
    Any Sugg?

  • Business System and Technical System ??

    Hi Experts,
    Please tell, What is the Technical System and Business System. How many Technical and Busniess Systems do we have in XI ?
    Early responses are welcome.

    Hi,
    Business systems:
    Business systems are logical systems, which function as senders or receivers within PI. Business systems can be SAP systems or third-party systems.
    Depending on the associated technical system, the following types of business systems are defined in the SLD:
    Web AS ABAP:
    A business system, which is associated with a Web AS ABAP.
    A business system, which is associated with a Web AS ABAP, can play the role either of an application system or an integration server. An integration server is the central component of PI, which provides a framework for the exchange of information among various internal and external entities of a company. The integration server facilitates the interaction between the different operating systems and applications across internal and external networks.
    Web AS Java:
    A business system, which is associated with a Web AS Java.
    Standalone:
    A business system, which is associated with a standalone Java application.
    Third-party:
    A business system, which is associated with a third-party technical system.
    Technical systems:
    Technical systems are application systems that are installed in your system landscape. An example of an application system is a Customer Relationship Management (CRM) server. In the SLD, there are five types of technical systems:
    Web AS ABAP:
    Web AS ABAP technical systems, ranging from any SAP system to an APO server or CRM server, are based on the same Basis Component (BC), which includes the ABAP interpreter, ABAP Dictionary, ABAP Workbench, and so on. A dedicated database, which stores most of the data of the BC and the application components, is associated with the system.
    Web AS Java:
    Web AS Java systems consist of one or more instances and each instance is installed on a separate host. An instance itself consists of cluster nodes that can communicate with each other.
    Standalone Java:
    Standalone Java technical systems are standalone Java applications that are installed in a computer system from an administration perspective. They can also be installed as an operating system service or as a daemon.
    Third-Party:
    Third-party technical systems contain third-party software components and products.
    Regards,
    Prakasu

  • SLD Configuration - Technical System and Business System

    Hello,
    I have installed SAP Solution Manager with local SLD and i want to use this system as Central SLD for my System Landscape. Later on i have installed other SAP Products like ECC,BI,PI etc.
    Some of the systems i registered with previously defined SLD in Solution Manager, but some system i forgot to register with SLD during installation.
    I am not sure or aware what is the difference between SLD configuration during installation and after installation.
    If i have Register the System during installation will it register automatically with SLD or we have to do manually.
    If i have not register system during installation and later on i want to register particular system with SLD what is procedure for that.
    Can some one share knowledge on What is Technical Systems and Business System in SLD Configuration, i tried to do some activity for SLD Configuration but after seeing above both terms i was confused so for time being i stopped this activity.
    Looking forward for kind response.
    Best Regards,
    V.Singh

    Hello
    try to go through these
    http://help.sap.com/saphelp_nwesrce/helpdata/en/45/4208934d7f1193e10000000a1553f7/content.htm
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/652b1f46-0a01-0010-25ae-e7cb07b55414

  • How to create Technical System in SLD configuration?

    Howdy!
    Our R/3 system has not packed with proper plugin so I can not use T-code rz70 to transfer system info from R/3 to SLD.
    I try to create a technical system manually in SLD web UI.But in the last step of creation(ABAP based system),after I had choose the "installed product",which is SAP R/3 4.6c,"installed software component" didn't show on the right side panel as expected.
    Anybody can tell me how to slove this?
    Thanks indeed...

    There are a few notes on http://service.sap.com/notes that may help you with this!  Try note number 584654.
    What version is you kernel?
    I think it needs to be at least 6.30.
    J2EE Engine >= 6.30 on Windows and Unix platforms
    Web AS >=6.40 SP4
    Also try this Problem analysis guide:
    http://help.sap.com/saphelp_nw04/helpdata/en/71/7ffb3f6c78ee28e10000000a1550b0/frameset.htm

  • Regarding error in creating technical system of type WEB AS ABAP

    while creating technical system of WEB AS ABAP i have few doubts
    1) host name:(do we have to give sap system name or xi system name)
    and while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER  i.e xi3/sxi what ever it may be,so am facing very difficulty while creating communication channel and not able to select the integration engine under the ADAPTER ENGINE ,so please provide me suitable solution with screen shoits if possible ,it very urgent for me

    pls check this
    /people/michal.krawczyk2/blog/2005/03/10/registering-a-new-technical-system-in-sld--abap-based
    as per ur doubt
    1. <i>host name</i>:; sap system (can find under system status  info-->database of R/3)
    2. <i>SId is system status</i>->database>name (3) characters
    3.<i>while creating business system for this technical system am not able to find the option under RELATED INTEGRATION SERVER</i>--as fra as this info that is there when u follow the wizard of creating Business system , also did u select business system role as application system name then probly u can get the related server name ,make sure ur technical system is created well
    <i></i>

Maybe you are looking for