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

Similar Messages

  • Error while executing template installer: Step 14 Maintain JCO Destinations

    Dear all:
    We are applying Template Installer to perform post installation for BI-JAVA in NW2004s SP09.
    Onto step 14: Maintain WebDynpro JCO Destinations, we faced the following Error message :
    Element 'SAPConfigLib.BW8.Unclassified.maintainJcoDestination':!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.BW8.Unclassified.maintainJcoDestination':Error during executing Java Reflection:Failed to delete JCO client connection 'WD_ALV_MODELDATA_DEST' on 'BW8.SystemHome.sap15\kin'
    Does anyone have any idea about it ?
    Thank you very much
    SF

    We are encountering the same issue in NW2004s SP 10. Szu-Fen, did you find a solution? If so, could you please post it here?
    Does anybody else have a hint how to resolve this?
    kind regards,
    Hartmut

  • Problem during Post Installation in PI 7.1

    Dear All,
    While doing post installation steps in PI 7.1 Server all the configurations are taking place in client 001 though we have done the client copy from 001 to 200. All the user id etc are getting created in client 001 only. I have changed the client id in RFC "I18NBackendConnection" and "UMEBackendConnection" in http://<host>:<hport>/nwa then also its taking 001 client only.
    Please guide me on how to do the configurations so that everything is done in 200 client.
    Regards,
    NJ

    Nishu,
              AYou could have resolved this isuue by running the client copy (SAP note - 1115280) before running the config wizard.
    You have rerun the
    client copy step - follow the SAP note 1115280 as is.
    and you will be fine... I think you may have to manually change the clients in the Java stack - Jco connection and RFC destination.
    regards,
    Arvind R

  • MI Post Installation Process missing template installer

    Hi All,
    I have installed MI Server (ABAP + JAVA Stacks) as a stand alone machine, also done the configuration steps <b>manually</b> for enabling mobile administrator in nwa. But getting issues while creating JCO's and unable to solve them, so I thought of doing it by <b>automation</b>. But when I want to execute the post installation template for MI, I don't find the scenario <b>MI Post Installation Process</b> in drop down box. Could anyone please help me in solving this issue. reward points are granted for valuable answers.
    Thanks and Regards,
    Kishore.

    Hi Mahwish,
    Have you tried to do it manually? Check if in your Visual Adminstrator -> Server -> Services -> JCO RFC Provider -> Runtime
    Check RFC Destinations MEMGMT_MOBILE_CONTAINER_SYNC
    Go to for MEMGMT_MOBILE_CONTAINER_SYNC
    http://help.sap.com/saphelp_nw2004s/helpdata/en/b0/9f9a4271c80a31e10000000a1550b0/frameset.htm
    Regards,
    Rogério

  • 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

  • R/3 Accessibility via JCo Destination

    Hello
    We have a WebDynpro application running in an SAP EP 7.0 SP15.
    We have metadata and modeldata JCo destinations defined for an R/3 backend system.
    The WebDynpro application is using the modeldata JCo destination to reach a BAPI in the R/3 backend system.
    As far as SSO access is configured for the modeldata JCo destination, it is required that the Portal user of the WebDynpro applications has an user defined in the R/3 system.
    We would need to find some solution so that the WebDynpro application can access the BAPI in spite the runtime Portal user does not exist in R/3 backend system (e.g. accessing R/3 system with another user, that could be hardcoded or mapped to the Portal user or whatever).
    Is that possible? If yes, how?
    Thanks a lot!
    Regards,
    Jon

    I think that perhaps you posted this question in the wrong Web Dynpro forum. This question appears to be Web Dynpro Java related and not Web Dynpro ABAP. Please confirm otherwise I will be moving this thread to the WDJ forum where it seems to belong.

  • In portal where we will create JCO destinations?

    HI Gurus,
    In portal where we will get the option or screen for creating JCO destinations....
    I guess its somemwhere in System Admin---->
    If anybody knows the path please share with me.......
    Thanks in Advance,
    Dharani

    Hi,
    Please check the below document for help
    configure ESS:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
    ESS/MSS Installation to R/3 4.7 Enterprise
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    Configuring The Business Package For Employee Self Service (ESS)-mySAP ERP 2004
    MSS - http://help.sap.com/saphelp_erp2004/helpdata/en/0a/8b3b40b1607a56e10000000a1550b0/frameset.htm
    help.sap.com - Configuration of Employee Self-Service (ESS)
    http://help.sap.com/saphelp_erp2005/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    help.sap.com - Technical Description and Configuration Information
    http://help.sap.com/saphelp_erp2005/helpdata/en/76/77594d165144a1a9bff9aae1e26b26/frameset.htm
    BP for ESS Document
    https://www2.iviewstudio.com/support_content/_17295/BP_ESS_05_P1.pdf
    General Settings for Self-Service Applications
    Configuring MSS on Portal 6.0
    Implementation and Configuration guide for ESS into Portal,Backend R/3 4.7C
    Thanks & regards
    Santosh
    Reward if helpful !!!

  • Getting error in creating JCo destination for WebDynpro

    Hi Guys,
    I am getting an error in creating JCo Destination under Web Dynpro Content Admin.I am deploying MSS on Netweaver portal SR1 and ecc 5.0.I am getting a message"An error has occurred: "Failed to process the request."Contact your System Admin.
    When I am seeing the details:
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322), 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
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
    Web Dynpro code generators of DC sap.com/tcwdtools:
    No information available
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87289.311
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    java.lang.NullPointerException
         at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.checkStatus(SystemLandscapeFactory.java:871)
         at com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.checkStatus(WDSystemLandscape.java:469)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateJCODestinations(NameDefinition.java:272)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.updateNavigation(NameDefinition.java:237)
         at com.sap.tc.webdynpro.tools.sld.NameDefinition.wdDoInit(NameDefinition.java:144)
         at com.sap.tc.webdynpro.tools.sld.wdp.InternalNameDefinition.wdDoInit(InternalNameDefinition.java:223)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.doInit(DelegatingView.java:61)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.view.View.initController(View.java:274)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:555)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bindRoot(ViewManager.java:422)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.init(ViewManager.java:130)
         at com.sap.tc.webdynpro.progmodel.view.InterfaceView.initController(InterfaceView.java:43)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.getView(ViewManager.java:540)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.bind(ViewManager.java:398)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.makeVisible(ViewManager.java:620)
         at com.sap.tc.webdynpro.progmodel.view.ViewManager.performNavigation(ViewManager.java:263)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.navigate(ClientApplication.java:737)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:350)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:635)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         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:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Please help me guys.
    Paritosh

    You should post your question to the Webdynpro forum:
    Web Dynpro Java

  • Creation of JCO Destinations for web dynpro

    Hi all,
    I read quite a lot of post concerning the subject but unfortunately I did not found a solution to my problem.
    My goal is to create JCO Destinations to make my web dynpro to connect to an R3 system.
    In order to realise this I followed these steps :
    - Launch visual admin and set http settings, rfc settings, and cim client settings. I click on CIM client test and the result is a success so I assume this part is correct.
    - In R3, I execute transaction smgw, go to remote gateway to get the gateway settings. I execute RZ70 and filled the parameters just checked. Then I activate and launch the data collect. I have no error message and everythings seemed to work fine.
    - In the sld (<host>:<port>/sld) I configured my server settings, the I go to data bridge, set update local sld to true and fill RFC gateway info with the same values as in my R3 system. Then I restarted the sld.
    - Finally I went to Web Dynpro content administrator to create my destinations and there I failed. After entering all settings (the message server appears in my technical landscape in SLD), when I click on finish I've got the following exception :
    [code]
    Failed to create new JCO client connection WD_FLIGHTLIST_RFC_METADATA_DEST:
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
    at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:140) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.createJCOClientConnection
    (SystemLandscapeFactory.java:286) at
    com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscape.createJCOClientConnection(WDSystemLandscape.java:107) at com.sap.tc.webdynpro.tools.sld.ButtonBar.onActionFinish
    (ButtonBar.java:224) at com.sap.tc.webdynpro.tools.sld.wdp.InternalButtonBar.wdInvokeEventHandler(InternalButtonBar.java:252) 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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:100) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:299) at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:641) at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59) at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154) at
    com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55) 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:385) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318) at
    com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:824) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37) at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71) 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:94) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162) Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for WD_FLIGHTLIST_RFC_METADATA_DEST at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:664) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247) at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221) at
    com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101) at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:138) ... 30 more Caused by: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:393) at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestinaton(JCOClientConnection.java:558) ... 35 more[/code]
    I tried to create a generic destination (no for the web dynpro tutorial) and failed again.
    I do not undestand what I did wrong.
    Does someone have an idea ?
    Thanks for reading this !
    Sylvain
    Message was edited by: Sylvain

    This thread helped me too because before reading it I didn't thought that I had to create a logon group "PUBLIC".
    Anyway I succed in creating 'WD_FLIGHTLIST_MODELDATA_DEST' and the test is ok. The problem was that in sld / technical system / web as abap, my Central Application Server host was wrong. It is not possible to change it so I just add a secondary server with the right host and select this one when creating the destination.
    The only pb remaining is now 'WD_FLIGHTLIST_RFC_METADATA_DEST'. I think the pb is my message server such this is the only difference between the two destinations
    Thanks for your help
    Message was edited by: Sylvain

  • Post-Installation Process Error (Template Base)

    Hi Experts,
    I try to run template base post-installation process in client 100, we never run post installation process in client 001 (Which is recommended before making the client copy), while doing template base post-installation process failed (got error) at PIPostInstallProcess step 7 u201CAdd Installed Product2u201D I move further and then it failed at step 19 (u201CConfigure the Role of the Integration Serviceu201D) and 20 (Register Queues) same process. It failed at number of process, so what I did I move to manual post-installation process but I stuck in the step were we need to import exchange_profile.xml because I can not see this file at sap\BX0\SYS\global, is this file being deleted by template base post-installation if yes then how to recover it?
    Without this file i can not complete the manual post installation process...:-(
    With Regards
    Sunil

    i think we do not need exchange_profile.xml file in 7.0 post-installation. ok i skip that step in post-installation now when i created LCRSAPRFC_BX0 in Visual Admin services->JCo RFCProvider and try to start it, it is throwing an Error.
    I am using user "PI_JCO_RFC" has respective role assign to it.
    I am not sure whether i am providing correct value to these filed or not
    Gateway Host
    Gateway Service
    Application server host
    System Number
    Client
    can somebody send me detail about these fields
    With Regards
    Sunil

  • No such JCO destination is defined in the SLD

    Hi All,
    Following JCo are not available in Portal 7.0 for MSS configuration.
    Already MSS Buss Pkg has been deployed in Portal.
    u2022     SAP_R3_SelfServiceGenericsFIN
    u2022     SAP_R3_SelfServiceGenerics_MetaDataFIN
    u2022     SAP_cProjects
    u2022     SAP_cProjects_MetaData
    Getting mention error for MSS application:
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCO destination name 'SAP_R3_SelfServiceGenerics_MetaDataFIN' in the SLD. No such JCO destination is defined in the SLD.
    Please suggest for resolution.
    Regards,
    SK

    You have to get this fixed through BASIS / Web Dynpro Content Administrator.
    Check under Content administrator -> Webdynpro whether all the JCO connections are working fine.
    Setting Up JCo Connections for MSS - http://help.sap.com/erp2005_ehp_04/helpdata/EN/ef/15d2060e344c2fbf22e526104c24bb/frameset.htm
    Once the ESS / MSS Business Packages are deployed, as a part of the post deployment steps JCO set up is to be completed
    Below JCO are to be set up for MSS -
    ●      General connections:
    ○       SAP_R3_SelfServiceGenerics
    ○       SAP_R3_SelfServiceGenerics_MetaData
    ●       Connections for the Team area:
    ○       SAP_R3_HumanResources
    ○       SAP_R3_HumanResources_MetaData
    ●      Connections for the Budget area:
    ○       SAP_R3_Financials
    ○       SAP_R3_Financials_MetaData
    ○       SAP_R3_SelfServiceGenericsFIN
    ○       SAP_R3_SelfServiceGenerics_MetaDataFIN
    Set up the following for branching to the details screen from Travel work items in the universal worklist:
    ○       SAP_R3_Travel
    ○       SAP_R3_Travel_MetaData
    ●      Connections for the Projects area:
    ○       SAP_cProjects
    ○       SAP_cProjects_MetaData

  • Problem in post installation of PI7.1

    Hi All expert  ,
    I facing problem in post installation of PI7.1 ,
    I have tried  to run net weaver initial setup with the help of configuration wizard we are facing given  following problem .
    During 60% of instatllation I have got error u201CChoose a password that is different from your last 5 passwordsu201D I  have changed it in ABAP side but still getting same error
    When I skip this step then second error
    : Choose a password that is different from your last 5 passwords 'PI_JCO_RFC'
    AI_RUNTIME_JCOSERVER
    RFC_ERROR_LOGON_FAILURE: Password logon no longer possible - too many failed attempts
    Is it any way to change all standard user(i.e. created during installation ) like PI*,  password in one shot in both ABAP side and  JAVA side .
    Regards,
    Amit

    Hi,
    that problem is resolved now m facing other problem during initial setup of configuration wizard .
    please see detail log .
    NetWeaver initial setup > PI UT initial setup > PI initial setup > Configure IntegrationServer > Initial setup of functional unit IntegrationServer > Initial setup of functional unit IntegrationServer > This wizard will execute Postinstall steps of technical configuration > Executing BAPI SXMB_SET_ROLE_TO_IS
    Executing BAPI SXMB_SET_ROLE_TO_IS
    Description
    No specified detailed description
    State
    START_ACTION
    Support Information
    Type of Action
    InvokeServiceDebug Events
    error message
    Error: Execution of Function SXMB_SET_ROLE_TO_IS ends with an error (cause:ONLY_ONE_CENTRAL_XMB:100, error code:092).
    error message
    Error: Execution of Function SXMB_SET_ROLE_TO_IS ends with an error (cause:ONLY_ONE_CENTRAL_XMB:100, error code:092).
    InvokeService:Executing BAPI SXMB_SET_ROLE_TO_IS
    Library: sap.com/tclmconfig~content
    SourcePath ./NetweaverProcess/PIJavaConstraint/PIJavaProcess/IntegrationServerRootProcess/IntegrationServerProcess/IntegrationServerProcess/SXMB_SET_ROLE_TO_IS/INVOKESERVICEBAPIIS
    Time 2009/07/31 at 14:30:47
    WSDL content/Netweaver/PI/IntegrationServer/service/BAPIConfiguringRoleOfIS.wsdl
    Destination parameters
    user : PISUPER
    password : % secure content %
    host : ctsgvcsapbl03
    sysnr : 10
    client : 001
    language : en
    function name: SXMB_SET_ROLE_TO_ISInput
    <Input>
    <NAME>EGAL</NAME>
    </Input>
    InvokeService- Result: Failed
    Exception Message:Execution of Function SXMB_SET_ROLE_TO_IS ends with an error (cause:ONLY_ONE_CENTRAL_XMB:100, error code:092).
    Exception Class:com.sap.tc.lm.ctc.metamodel.exception.ActionExecuteException
    Stacktrace
    com.sap.tc.lm.ctc.cul.serviceimpl.process.InvokeServiceControllerDefault.execute(InvokeServiceControllerDefault.java:171)
    error message
    Error: Execution of Function SXMB_SET_ROLE_TO_IS ends with an error (cause:ONLY_ONE_CENTRAL_XMB:100, error code:092).
    Regards,
    Amit

  • Failed to resolve JCO destination name

    I am using RFC model to post form data to backend. This is the error I got when I tried to run the application.
    <i>Failed to resolve JCO destination name 'MI2_APPLICATIONDATA' in the SLD. No such JCO destination is defined in the SLD</i>
    I have JCO destination configured in my SLD. I can see them in green when I go to Deployed Content --> System Defined Content. I was able to successfully test and ping them.
    One thing I observed is my application does not show up in the Deployed Content --> Local. Other earlier applications which I deployed before are showing up, but not the current one. I restarted J2EE server, rebuilt, redeployed. No luck !!

    Thats exactly the problem. I figured it out myself and thought of editing this thread. But you have replied by then. Thanks for the quick reply and awarded you the points you deserve.

  • 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

  • XI Post installation steps

    Hi,
    I'm trying to get XI going at a project.  The basis guys have installed the server but I have an idea none of the 'post installation steps' have been completed.
    The symptoms are that when I start the Integration Builder (SXMB_IFR) the Windows 'File Explorer' is started and not IE. The Integration Web page is not displayed.
    I quickly looked at the Configuration guide and I see none of the RFC destinations mentioned in the guide.
    Is this the reason for the problem ?.  I need to know exactly what totell the basis people to look at. They have never done an XI installation before so I'm almost sure they have not done these configuration steps.
    Thanks
    Andre

    Hi Andre,
    They should look at the intallation/configuration guides that SAP provides. These guides can be found at the service.sap.com and/or help.sap.com
    In a nutshell you have to make sure they have configured:
    SLD settings, these involves configuring RFC destinations, Maintain the SLD parameters in SLDAPICUST.
    Register, Starting up the queues. Configure the role of the integration server in trx SXMB_ADM or SXMB_ADMIN.
    Hope this helps.
    Cheers,
    Roberto
    Message was edited by: Roberto Viana

Maybe you are looking for