XI Post Installation - SLD Connection

Hi, I'm following the XI 3.0 post-installation guide. In the step "Maintaining SLD Connection Parameters" I call transaction SLDAPICUST and try to insert a row as described in the guide.
The problem occurs in the password column which is not editable.
Am I missing something?
Thanks
Juan Manuel

Juan, I had the same problem. I was using the Java GUI 6.40R2 and the Password popup does not work. I switched to use the Windows GUI and the password popup came up, I entered the password and all is OK. I went back to the Java GUI and clicked on Password field and the popup is working now - go figure??

Similar Messages

  • Problem in XI after post installation.

    I have done the post installation for PI, everything was fine and sucessfull,
    but the problem is, in XI check list there is no objects found in the Integration Repository and Integration Directory with the URL  ( http:
    emsap008:50100\rep\start\index.asp ).
    Let me explain the problem which i faced.
    In the transaction SXMB_IFR --> Tool --> Import Design Objects Option, the result displaied is " There is no Objects found ". But as per the document i need to get               " PI7_0_BASIS_6.40_18_00.tpz ".
    Please clarify my doubt, ask me if my question is insuffecient.

    Hi Senthil !!
    Here is the guide with necessary steps
    http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
    /people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
    You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
    SAP Exchange Infrastructure Release 3.0 - Installation Guide
    SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
    Plus you can go through the following docs:
    SAP Exchange Infrastructure (XI) 3.0
    Troubleshooting Guide - SAP XI 3.0 and 2.0
    SAP XI Release 3.0 SPS11Configuration Guide
    Also you can have a look at the following thread, you will get some links in these threads too:
    Post installation of XI?
    XI INSTALLATION and POSTINSTALLATION
    XI Post Installation....Need help...
    XI Post Installation - Help
    XI Post Installation - SLD Connection
    refre this thread
    Post Installation of PI - PI template Installer not found
    <b>Pls rewards if useful</b>

  • Post installation for XI

    Hi All,
    I have installed ECC 6.0. I have added XI component also. Now i need to perform post installation steps for XI alone. i have downloaded the NW7 installation Guide MAXDB. is that enough? or should i need more documents....
    Also, i found out a document for post installation guide system landscape directory of SAP Netweaver 7.0....
    Which one should i follow?
    Please clarify....
    Thanks in advance,
    Madhukar

    Hi madhukar !!
    Is this what you are looking for:
    https://websmp103.sap-ag.de/~sapidb/011000358700001697502004E.PDF
    Also check this thread..
    Re: XI INSTALLATION and POSTINSTALLATION
    those describe din XI installation and configuration guides:
    http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
    http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
    check this thread for SLD configuration soon after XI installation
    SLD configuration
    Check this link also it has the procedure.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
    Here is the guide with necessary steps
    http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
    /people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
    You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
    SAP Exchange Infrastructure Release 3.0 - Installation Guide
    SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
    Plus you can go through the following docs:
    SAP Exchange Infrastructure (XI) 3.0
    Troubleshooting Guide - SAP XI 3.0 and 2.0
    SAP XI Release 3.0 SPS11Configuration Guide
    Also you can have a look at the following thread, you will get some links in these threads too:
    Post installation of XI?
    XI INSTALLATION and POSTINSTALLATION
    XI Post Installation....Need help...
    XI Post Installation - Help
    XI Post Installation - SLD Connection
    Post Installation of PI - PI template Installer not found
    Pls reward if useful

  • Hello installed xi and trying  2 do post installation but getting problem

    Hello,
              I installed SAP XI and trying to do the post installation...
              1)Created one client 100 and user XIUSER....with all rights like sap_all
              2)And created one more user XISUPER......only roles given...
              3)now I am trying with internet expositor
                  http://application server:java port/exchangeProfile
                     screen came user:xisuper
                                          p/w: 12345
                           BUT IS NOT GOING FORWRD....WHAT MIGHT BE THE PROBLEM..... TRY TO GIVE ME THE SUGGESTION....
    Regards,
    Sateesh.j

    Hi !!!
    Here is the guide with necessary steps
    http://help.sap.com/bp_bpmv130/Documentation/Installation/XI30InstallGuide.pdf
    /people/sravya.talanki2/blog/2006/11/15/post-installation-steps-for-activating-adobe-document-services-in-sap-xi-nw-2004s
    You will get the details of post installation activities for SAP XI in its installation guides itself. Have a look:
    SAP Exchange Infrastructure Release 3.0 - Installation Guide
    SAP Exchange Infrastructure 3.0 SR1 - Installation Guide
    Plus you can go through the following docs:
    SAP Exchange Infrastructure (XI) 3.0
    Troubleshooting Guide - SAP XI 3.0 and 2.0
    SAP XI Release 3.0 SPS11Configuration Guide
    Also you can have a look at the following thread, you will get some links in these threads too:
    Post installation of XI?
    XI INSTALLATION and POSTINSTALLATION
    XI Post Installation....Need help...
    XI Post Installation - Help
    XI Post Installation - SLD Connection
    refre this thread
    Post Installation of PI - PI template Installer not found
    just check also have you done this step ?
    This step is not covered by the PI template.
    You need these files The files SCM4003_00.ZIP and SCMBASIS4003_00.ZIP
    Further reference
    http://help.sap.com/saphelp_nw04s/helpdata/en/44/5755451622311ee10000000a155369/content.htm
    Another thing are the j2ee adapters and the adapter engine visible in the ID just check once. If not then go through these.
    1)Yeap you need the basis component imported first.
    2) Apply SAP Note 764176.
    3. /people/venugopalarao.immadisetty/blog/2007/03/15/adapter-engine-cannot-be-found-in-integration-directory
    <b>pls reward if useful</b>

  • Error in PI 7.0 not connect to go.bat & Post installation errors

    im completed installation of PI 7.0
    SYSTEM NAME : BIW7
    System ID   : BI7
    DB ID       : BIW
    Instance No : 04
    for post installation unable tp connect  go.bat
    im giving right password
    http://biw7:50400/ExchangeProfile   = it gives error 404 not found
    http://biw7:50400/sld   gives following error
    503   Service Unavailable
    Application cannot be started.
      Details:   com.sap.engine.services.deploy.container.ExceptionInfo: Naming error.

    For exchange profile, ur URL is incorrect. Try this
    http://biw7:50400/exchangeProfile
    Regards,
    Prateek

  • SLD port problem in Netweaver XI post installation configuration steps

    Hi All,
        Recently we changed the port number of the SAP server to 80.Every thing working fine.
    When ever we are configuring the XI that mean the post installation steps for Exchange Infrastructure it giving the errors in machine_technical_configuration  step.
    Error Message is:
    Element 'SAPConfigLib.NW5.Unclassified.addInstalledProduct':!BrokerImport.import_of_element_failed!!BrokerImport.Fehler!com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION:com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceWriter.writeElement!BrokerImport.LINE!157-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.86
    -:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
    -:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
    -:com.sap.tc.lm.ctc.cul.serviceimpl.importservice.CULConfigurationImport.importConfiguration.96
    -:com.sap.tc.lm.ctc.ccl.templateinstaller.StepExecuter.run.41
    Element 'SAPConfigLib.NW5.Unclassified.addInstalledProduct':Error during executing Java Reflection:IO error: Unable to open connection to host "mmsr18:50000". The host is down or unavailable..
    Is there any solution to solve this....
    Thanks & Regards,
    Vivek.

    hi
    check if the new port(80) is maintained in tcode- sldapicust
    Thx
    jonu

  • Error in the post installation steps of SLD .

    Hi
    We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
    This is detailed exception I got.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
    at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
    at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
    at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
    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:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    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)
    Please help me.
    Thanx & Regards,
    Naresh

    Hi Naresh,
    Can you let me know the service pack for the portal.
    Also try login in using administrator using the http://<localhost><port>/sld
    thanks
    Pankaj

  • Error in the post installation of SLD .

    Hi
           We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
    <b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!</b>
    This is detailed exception I got.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
         at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
         at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
         at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
         at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
         at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
         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:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         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)
    <b>
    Please help me.</b>
    T
    hanx & Regards,
    Naresh

    Hi Naresh
    Try logging off from the current window.
    and login again as "Administrator" .
    use http://portalhostname:50000/sld
    hope this helps
    Cheers !!!
    Satish Kumar.

  • Webdynpro error in Post installation steps of SLD

    Hi
    We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
    <b>com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!</b>
    This is detailed exception I got.
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
    at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
    at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
    at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
    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:420)
    at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
    at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
    at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
    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)
    Please help me.
    Thanx & Regards,
    Naresh

    Hey Aviad,
    Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
    1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
    components.
    2) Using the Archive remover tool which can be accessed from
    System Administration > Support > Portal Runtime > Administration
    Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
    3) Navigate to Content Administration > Portal content > Content
    Provided by SAP > Platform Add-Ons > Developer Content
    and remove all the contents below this folder.
    4) Restart the server
    After this you can deploy the SP9 business package using the SDM.
    Hope it helps,
    Roy

  • BI Post Installation /JCO Destinations

    Hi all,
    I am having some troubles getting the Netweaver BI functionalities to start running.
    We have just upgraded our BW System to Netweaver 2004s and installed an add-on Java Stack.
    Both the ABAP Stack and the Java Stack have the most current patch level.
    I followed the SLD post installation Guide and I think I did everything as described, including the prerequisites described in the SAP Notes 983156 and 917950.
    I do want to add that I am a functional consultant with quite a lot of experience in BW and BPS, but very little knowledge in Basis technology.  Our Basis collegues know only little about Java, so we are trying to work it out together.
    I imported the content though the SLD and created our ABAP System as a technical system in SLD.
    I then tried to use the post-BI installation wizard.  The following steps 1-9 are executed without problems: 
    1.     Create RFC Destinations in ABAP
    2.     Update Table RSPOR_T_PORTAL
    3.     Create RFC Destinations in Java
    4.     Create System Landscape Folder
    5.     Create BW System
    6.     Set System Alias
    7.     Add ACL
    8.     Set Master System
    9.     Download Engine Certificate
    I get following error message when trying to install step 10:
    Import ABAP Certificate to Engine Import not successful Element 'SAPConfigLib.C40.Unclassified.uploadAbapCertificate':!BrokerImport.import_of_element_failed!!BrokerImport.Fehler!com.sap.tc.lm.ctc.cul.cpi.exceptions.CPIBaseException: <Localization failed: ResourceBundle='com.sap.tc.lm.ctc.cul.cpi.CPIResourceBundle', ID='com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION', Arguments: []> : Can't find resource for bundle java.util.PropertyResourceBundle, key com.sap.tc.lm.ctc.cul.cpi.BaseException_BASE_EXCEPTION:com.sap.tc.lm.ctc.provider.javaServiceProvider.JavaServiceWriter.writeElement!BrokerImport.LINE!157-:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.86
    -:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
    -:com.sap.tc.lm.ctc.cul.broker.BrokerImport.importElement.128
    -:com.sap.tc.lm.ctc.cul.serviceimpl.importservice.CULConfigurationImport.importConfiguration.96
    -:com.sap.tc.lm.ctc.ccl.templateinstall er.StepExecuter.run.41
    Element 'SAPConfigLib.C40.Unclassified.uploadAbapCertificate':Error during executing Java Reflection:Remote call errored
    I also noticed that I cannot maintain the JCO destinations both in the web dynpro content administrator and in the transaction SPRO.
    In the web dynpro content administrator i see the buttons, but they are greyed out, in SPOR the "execute" button is missing.
    From what I read, I get a feeling that the symptoms might be connected, but I ran out of ideas what the problem could be.
    Does anybody have an idea?
    I would be very grateful if somebody could help.
    Regards,
    Omar

    Hi
    I am trying to install BI7.0 and as a part of it I was successful in installation part but when i am trying to check the prerequisite for the notes 983156, I was stuck at the point of bringing the system BI7.0 in to the sld, from the note I can infer that to bring the system in to sld we need to use rz70 and give the gateway details over there (host ,service) when I try to continue with the default values i was not successful to bring the system in to land scape can some one guide me for the steps to bring this system in to land scape.
    Any documents of ur previous installation would be appreciated.
    Regards
    Manikanth

  • POST Installation steps for SAP XI 7.0 SP06

    Hi Experts ,
    We are trying to install XI 7.0 SP06.We are suppose to carry out  post installation
    steps but we are not able to locate a proper post installation guide for the same.
    We have succesfully installed XI 3.0 earlier .However XI 7.0 post installation steps in the guide that we have "SAP NetWeaver 2004s SR1 ABAP+Java on Windows: Oracle" , are relatively less...
    Nevertheless, we have carried out the following steps
    5.21.1 Performing PI-Specific Steps for SLD Configuration
    Local and Central System Landscape Directory (SLD)
    Mapping Security Role to User
    1. Log on to the Visual Administrator of the J2EE engine of the SLD host.
    2. Choose Cluster® Server® Services® Security Provider.
    3. In the Runtime tab, choose Policy Configurations and then the column Components, and select the component
    sap.com/com.sap.lcr*sld.
    4. Switch to the Security Roles tab to display the assigned roles.
    5. Select role LcrInstanceWriterLD.
    The user SLDAPIUSER already exists with its security role LcrInstanceWriterLD.
    6. Switch to edit mode and add user PIAPPLUSER with the same role LcrInstanceWriterLD.
    Note
    For a central SLD, the user PIAPPLUSER must be created in the central SLD ABAP system first and be
    assigned to ABAP role SAP_XI_APPL_SERV_USER. The password must be same as in the XI Exchange
    Profile on the XI Integration Server.
    Note
    For information on the UME actions, see the Post-Installation Guide - SLD of SAP NetWeaver 2004s, section
    Configuring SLD Security, at service.sap.com/sld® Media Library.
    Maintaining SLD Connection Parameters (ABAP API)
    1. Log on to the SAP XI Integration Server System as user DDIC and call transaction SLDAPICUST. The screen
    Maintain SLD Access Data is displayed.
    2. Choose Display <-> Change and proceed as follows:
    a) Replace the existing SLDAPIUSER with PIAPPLUSER user.
    Note
    For a central SLD, make sure you use the user with security role LcrInstanceWriterLD.
    b) Make sure your entry is marked as Primary.
    Note
    Only the entry marked as Primary is active.
    c) Save your settings.
    April 10, 2006 PUBLIC 97
    Now we don't know wether the sld configuration is over or not ...or for that matter in RWB we see only J2se based adapter engine and  not J2ee based adapter engine...
    Kindly help

    Hi..
    Instaed doing this,please try out template based configuration which has been mentioned in the installation guide or else do as follows
    1.Login into NWA (netweaver administrator)
    as
    http://<host.<domain>.<com>:<port>/nwa
    2.Use J2ee_admin user id and password
    3.go to deploy and change
    4.select template based configuration for PI
    5.execute the template
    6.install it
    you can find the list of other templates which are clear and easy to do the post installation step..i found it useful ..
    Apart from these, as per sandro, you can check the data transfer in visual administrator or go the abap engine, transaction RZ70, press accept proposal button
    then execute button , check the data supply without any error
    Thanks
    Gopal
    (Avoid points if useful)

  • XI Post-Installation problem (403 Forbidden)

    Hi,
    currently i'm executing the post-installation of XI.
    At topic "Creating RFC Destinations in the ABAP Environment" especially creating the RFC-Destination "INTEGRATION_DIRECTORY_HMI" (SM59) I have a problem. After saving all necessary entries in various tabs, i get after executing "Test connection" the HTTP-Code 403 (forbidden).
    Following is the exact error i am getting:
      HEADER NAME                HEADER VALUE
    ~response_line               HTTP/1.1 403 Forbidden
    ~server_protocol             HTTP/1.1
    ~status_code                 403
    ~status_reason               Forbidden
    connection                   close
    set-cookie                   MYSAPSSO2=AjExMDAgAA9wb3J0YWw6WElJU1VTRVKIABNiYXNpY2F1dGhlbnRpY2F0aW9uAQAIWElJU1VTRVICAAMwM
    set-cookie                   JSESSIONID=(ximac_XID_00)ID9751150DB19780753031607883521End; Version=1; Path=/
    set-cookie                   saplb_*=(ximac_XID_00)9751150; Version=1; Path=/
    pragma                       no-cache
    cache-control                no-cache
    expires                      0
    content-type                 text/html
    content-length               1506
    server                       SAP J2EE Engine/6.40
    date                         Mon, 23 Sep 2002 08:37:06 GMT
      HTTP BODY
    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
    <html>
    <head>
         <title>Error Report</title>
    <style>
    td {font-family : Arial,
    Tahoma, Helvetica, sans-serif; font-size : 14px;}
    A:link
    A:visited
    A:active
    </style
    >
    </head>
    <body marginwidth="0" marginheight="0" leftmargin="0" topmar
    gin="0" rightmargin="0">
    <table width="100%" cellspacing="0" cellpaddin
    g="0" border="0" align="left" height="75">
    <tr bgcolor="#FFFFFF">
    <td align="left" colspan="2" height="48"><font face="Arial, Verdana, Hel
    vetica" size="4" color="#666666"><b>  403 &nbsp Forbidden</b><
    /font></td>
    </tr>
    <tr bgcolor="#3F73A3">
        <td height="23" width="8
    4"><img width=1 height=1 border=0 alt=""></td>
        <td height="23"><img
    width=1 height=1 border=0 alt=""></td>
        <td align="right" height="2
    3"><font face="Arial, Verdana, Helvetica" size="2" color="#FFFFFF"><b>SA
    P J2EE Engine/6.40 </b></font></td>
    </tr>
    <tr bgcolor="#9DCDFD">
        <td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></
    td>
    </tr>
    </table>
    <br><br><br><br><br><br>
    <p><font face="Arial, Ve
    rdana, Helvetica" size="3" color="#000000"><b>  You are not au
    thorized to view the requested resource.</b></font></p>
    <p><font face="
    Arial, Verdana, Helvetica" size="2" color="#000000"><table><tr><td valig
    n="top"><b> Details:</b></td><td valign="top"><PRE>No details avail
    able</PRE></font></td></tr></table></font></p>
    </body>
    </html>
      Time (ms)                             17,007
    I do not find the way to solve it....
    With regards
    Sunil

    Hi,
    Now i am getting another problem.
    While testing SLDCHECK i am getting exception while calling function LCR_LIST_BUSINESS_SYSTEMS.
    Please find the detail below.
    Testing the RFC connection to the SLD java client...
    RFC ping was successful
    SLD server access settings:
      host name:   XIMAC
      port number: 50000
      user       : XIAPPLUSER
    Use transaction SLDAPICUST if you wish to maintain the SLD server access data
    Launching the SLD GUI in a separate browser window...
    => Verify in the browser GUI that the SLD is in a healthy running state!
    Calling function LCR_LIST_BUSINESS_SYSTEMS
    Retrieving data from the SLD server...
    Function call returned exception code     3
    => Check whether the SLD is running!
    Summary: Connection to SLD does not work
    => Check SLD function and configurations
    Now checking access to the XI Profile
    any guess to solve this problem.
    with regards
    Sunil

  • SLD Connection IB: Can't find business systems: InternalEOAService

    Dear experts,
    I have connected my SLD properly to the IS. SLD_CHECK is successful. But I can not access the business systems from the integration builder. I get this message:
    ========================================================
    Access to object list of type "BusinessSystem" using the InternalEOAService BusinessSystemAccessor failed
    ========================================================
    What's wrong. Performed J2EE restart and SXI_CHACHE refresh.
    Can also not import configuration objects due to the fact that it thinks that certain business systems do not appear in the SLD. But they do....
    Please suggest?!?
    Kind regards.

    Forget about the SLDCHECK.  that is completely irrelevant here and only deals with the abap communciation.
    Your issue relates to the JAVA communication with the SLD.
    You need to successfully register the JAVA stack with the SLD.  In the Data Supplier, does this work for every page?  You are interested in the CIM Data tab...
    You may have to make alot of manual associations, but until you can register the other components, there's no point.
    Can you specify your version and whether or not the Template Installer was successful and whether you have checked the post installation tasks?
    Also check this note: https://service.sap.com/sap/support/notes/939592

  • Post installation steps for PI 7.0

    Hi,
    Can anybody send me the Post installation steps for PI 7.0?
    Thanks in advance..
    ~Kumar

    Hello,
    <br><br><br>
    We did PI Installation recently and version is 7.1
    <br><br><br>
    Steps are as under...
    <br><br><br>
    <br>1.     Basic PI installation</br>
    <br><br>2.     System checks after basic installation
    <br>a.     SM50
    <br>b.     SM21
    <br>c.     ST22
    <br>d.     SM12
    <br>e.     SM13
    <br>f.     SM37
    <br><br>3.     Unlock the 001 client for cross-client changes temporarily and set system timezone (STZAC)
    <br><br>4.     Change 001 client settings back to no changes allowed.
    <br><br>5.     Create BASIS team member accounts in ABAP Stack and assign SAP_ALL.
    <br><br>6.     Set directory permission for \usr\sap\trans directory on Transport Domain Controller system.
    <br><br>7.     Import profiles (RZ10)
    <br><br>8.     Add the 4 following entries in to the instance profile and restart instance(RZ10)
    <br>a.     DIR_TRANS =
    hostname.domain.ext\sapmnt\trans
    <br>b.     icm/host_name_full = hostname.domain.ext
    <br>c.     login/system_client = 100
    <br>d.     icm/server_port_0 = PROT=HTTP,PORT=5<sysno>00,TIMEOUT=1800,PROCTTIMEOUT=1800 {SAP Note 1107808}
    <br><br>9.     Configure TMS in transport domain controller{PI DEV} (STMS)
    <br>a.     Add virtual system
    <br>b.     STMS in newly installed system and configure proper transport domain
    <br>c.     In domain controller approve the new system (STMS -> SAP system -> Approve)
    <br><br>10.     Get maintenance certificate and SAP license from service marketplace and apply in to the new system {ABAP and JAVA} (slicense and NWA)
    <br><br>11.     Kernel Update JSPM
    <br>a.     JSPM update
    <br>b.     Kernel update
    <br>c.     BC-FES-IGS update
    <br><br>12.     Support pack installation ABAP
    <br>a.     SPAM update
    <br>b.     Support packs update
    <br><br>13.     Support pack installation JAVA
    <br>a.     Apply support pack stack
    <br>b.     Apply support pack patches
    <br>i.     After JVM installation Error occurs apply MS windows KB973544 {SAP Note 1367498}
    <br>c.     Restart JSPM and continue patch installation
    <br><br>14.     Client copy from client 001 to X00 using profile SAP_ALL
    <br><br>15.     Create logical system and assign it to new client (SALE)
    <br><br>16.     Change UME target in JAVA to client X00.
    <br>a.     Enter URL as http://hostname.domain.ext:port/nwa
    <br>b.     Management -> Infrastructure -> Destination
    <br>c.     Logon data TAB change client to X00
    <br>d.     Restart JAVA Instance
    <br><br>17.     Create following users
    <br>a.     PIAFUSER, PIRWBUSER, PIISUSER, PIDIRUSER, PIREPUSER and PIAPPLUSER on the target SLD and new system manually and assign role/group SAP_SLD_CONFIGURATOR to them. {SAP Note 1309239}
    <br>b.     PISUPER in new system and assign appropriate roles in ABAP and JAVA
    <br>c.     SLD_DS_<SID> and SLD_CL_<SID> on target SLD {Use source system master password}
    <br>d.     JCoRFC_<SID> in new system
    <br>e.     Sapadm user in new system
    <br><br>18.     Assign roles and groups to BASIS team on JAVA Stack
    <br><br>19.     Create PUBLIC logon group (SMLG)
    <br><br>20.     Configure SLD collector job as sapadm (RZ70)
    <br><br>21.     Run Configuration Wizard
    <br>a.     Enter URL as http://hostname.domain.ext:port/nwa
    <br>b.     Configuration management -> Scenarios -> Configuration Wizard
    <br>c.     Select Initial Configuration and click Start.
    <br><br>22.     Create the JCoRFC connection.
    <br>a.     Enter URL as http://hostname.domain.ext:port
    <br>b.     Web Dynpro -> Content administrator -> Maintain JCo destination
    <br>c.     Fill in information for the following 4 entries using client X00 and JCoRFC_<SID> as the user {Make sure you note the distinction between Metadata and Model destinations when you are creating the destination}
    <br>i.     WD_ALV_METADATA_DEST
    <br>ii.     WD_ALV_MODELDATA_DEST
    <br>iii.     WD_MODELDATA_DEST
    <br>iv.     WD_RFC_METADATA_DEST
    (Use dictionary Meta Data for the Metadata connections, use Application Data for the Model Data connections.)
    (Use the master password for EXQ)
    <br><br>23.     Repeat for the remaining 3 JCo RFC destinations. 
    <br><br>24.     Run PI Full Qualified Host Name Wizard {SAP Note: 1320707}{Make sure you check the host names for integration server and SLD}
    <br><br>25.     Create RFC destination in to ERP target system (SM59)
    <br>a.     Give Name PI_INTEGRATIONSERVER
    <br>b.     Connection type H
    <br>c.     In Technical settings TAB provide
    <br>i.     Target host = hostname.domain.ext
    <br>ii.     Path Prefix = /sap/xi/engine/?type=entry
    <br>iii.     User information is blank
    <br><br>26.     Setting SXMB_ADM ERP target system
    <br>a.     Open Integration engine configuration
    <br>b.     Goto -> Change Global Configuration Data
    <br>c.     Role of Business system = Application System {This is optional}
    <br>d.     Provide RFC destination name in Corresponding Integ. Server = dest://PI_INTEGRATIONSERVER
    <br><br>27.     Schedule Standard Jobs as SAPADM in client X00.
    <br><br>28.     SICF service to activate
    <br>a.     /default_host/sap/public/bc/pictograms
    <br>b.     /default_host/sap/public/bc/webicons
    <br>c.     /default_host/sap/public/bc/its/designs
    <br>d.     /default_host/sap/public/bc/workflow
    <br>e.     /default_host/sap/bc/ccms
    <br>f.     /default_host/sap/bc/webdynpro/sap/CTS_BROWSER
    <br>g.     /default_host/sap/bc/webflow
    <br>h.     /default_host/sap/bc/workflow
    <br>i.     /default_host/sap/bc/workflow_xml
    <br>j.     /default_host/sap/bc/xmb
    <br>k.     /default_host/sap/bc/ping
    <br>l.     /default_host/sap/xi/wsdl_sr
    <br>m.     /default_host/sap/xi/wsdl_url
    <br>n.     /sap/bc/webdynpro/sap/appl_soap_management
    <br><br>29.     Adjusting JNLP Heap size
    <br>a.     Open the Exchange profile through the link  u201Cadministrationu201D from the  web page of the Process Integration tools.
    <br>b.     Under the folder u201CIntegration Builderu201D click on the variable u201Ccom.sap.aii.ib.clientjnlp.j2se.maxheapsizeu201D
    <br>c.     Value = 1024
    <br>d.     Save the change and restart the J2EE instance of PI so that the new value can take effect.
    <br><br>30.     Create RFC destination for Advanced Adaptor Engine in sender ERP system(SM59)
    <br>a.     RFC Destination = AAE_<SID>
    <br>b.     Connection type = G
    <br>c.     Target Host = Host Name of AAE Server {PI Server}
    <br>d.     Service No. u2013 HTTP port number of AAE Server
    <br>e.     Path Prefix = /XISOAPAdepter/MessageServlet?ximessage=true
    <br>f.     Under Logon & Security use PIAPPLUSER with PI target systemsu2019 master password.
    <br><br>31.     Create RFC destination <SID>_ALE in ERP Source system with user ERQALEUSER {Make sure you have this user created in new installed system}
    <br><br>32.     Install External Driver Configuration in Process Integration 7.1 Using JSPM {SAP NOTE: 1138877}
    <br><br><br>
    Please let me know if I am missing anything there...
    <br><br><br>
    Cheers,
    <br>
    Yogesh

  • Compliance Calibrator Post Installation checks.

    Dear all, i'm trying to find some documentation regarding the CC post installation checks to ensure the system is installed fine. This is important because the installation is done by the customer themselves and I need to verify them before they should proceed to create or mitigate any rules in the system. Is there a checklist which i can refer to ?

    Peter,
    You'll find this to be quite a task - if i have understood you correctly. That is if you want to verify that installation has suceeded and that it is actually working correctly.
    Once you have gone through the post installation steps. That is, setting up the JCo Connections, SLD, Uploading the rules, usobt etc etc (This maybe creating the rules), Running the Full Sync for users/roles/profiles, analysis and management report background jobs and have not run into problems it is probably safe to say that everything has gone ok.
    What i would do after this is select a couple of sample users and execute some user analysis reports and use data in the backend R/3 to verify the reports.
    There isn't as far as i know a document which is able to <i>verify</i> the installation.
    Hope this helps,
    Cuneyt

Maybe you are looking for