Re:Upgrading from Business Connector to Xi

Hi Guys,
Can anybody plz help me how to upgrade from business connector ti XI
Thanks in advance
Hari

Hi Hari,
If you are interested to get a free evaluation on the level of complexity of your BC projects and the amount of work required for the migration please contact us and we can perform this evaluation and estimation for you.
Our product BC2XI is the only BC to PI migration product which is [Netweaver content certified|http://www.sap.com/ecosystem/customers/directories/SoftwareISVSolutions.epx?context=21B87D61C0F646A22B2A6DB254A010CA8C9C141B7529F029910FE6FF9EEEC5A701BF20EED61AC07159D98BAA068EBE1B8C5C7665EA2226374E942CF1D2A49D202711A97F135182CC%7c681CA45EAFF1066138C1B9B28AACD541&response=shared] and the only product which you can actually see a demonstration of (go to [http://www.sisusoftware.com]). We hear about other products, but these don't seem to have any public availability (at least which one could see).
It is completely feasible to automate the migration of BC records, flows, flow elements, graphical maps, 100+ of the BC built-in functions, output templates, etc. it is just very, very complex
Cheers,
Kalle

Similar Messages

  • RFC Error while trying to access function module from business connector

    Hi,
    I am getting the following RFc exceptions in BC server when we invoke the service pub.sap.client:invoke fail as a flow step in Idoc_Status_Add(this service is calling a function module in sap namely ZYBC_IDOC_STATUS_ADD_FROM_BC which Adds status to Idoc (from Business Connector).But no trace of failures are recorded in sap side
    except 1: rfc_failure in BC trace files under monitoring.I need to know the root cause of these errors as the same services have run finely later and IDOCs were also processed successfully without any problem.
    com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: See RFC trace file or SAP system log for more details
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1217)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3684)
    at com.sap.mw.jco.JCO$Client.execute(JCO.java:3129)
    at com.wm.pkg.sap.rfc.SAPSession.invoke(SAPSession.java:437)
    at pub.sap.client.invoke(client.java:297)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    could anyone throw light on how this kind of error can be resolved and why it occured?
    Thanks.

    What does the RFC trace file and log say? Has there been any dump on the SAP server? Check the logs and transaction st22 in your SAP system to see if the RFC-module has dumped.
    My guess is the problem is in the RFC-module, I think you should start looking there.
    regards,
    Dionisios

  • Idoc outbound from business connector

    Hi,
    I'm  trying to map values to idoc from business connector(4.6). The flow is
    map
    transformhierarchytoflat
    ale outbound process.
    When I test the application, it's showing a null pointer exception . I have doubt in what all values should i give for control records ??
    Shall i create a new routing rule for this ?
    Any help or suggestion will be of great help .
    Thanks in advance.

    HI,
    You are getting the Null Pointer Exception due to missing of Values in any of the context variables or the fields from mapping on target side.
    Please check the data that you are passing may have any null values and whcih are not acceptable. Test the message mapping with test Tab.
    The Mandatory control records, such as Sender/ receiver Ports, Partner Profiles etc, you need to pass.
    Thanks
    Swarup

  • Send IDOC from Business Connector to SAP faster

    Hi Developer!
    I need to send a very lot of IDOC converted from XML files from the Business Connector to SAP. The XML files are in different directories pro business partner, but they have a same type (ISU_MSCONS).
    My problem, that the import take a lot of time. Only in every 3 seconds (IDOC creation time) gets (or works up?) the SAP one IDOC. I start diferent services pro partner at the same time to import the IDOCs, but I couldnt short the 3 second work time in the SAP. So you can count it easy, that in 1 minute I can import 20, in 1 hour 1200, in 1 day 28800 IDOCs instead of 100.000.
    It is really parallel import? Have anybody any idea to make the import more faster. I know (asked the SAP Administrator) so, one BC - SAP connection (Program_ID) has more pools (= threads) in the SAP at the same time.
    Thanks any help,
    Charlie

    Hi Satish,
    You can achieve this requirement
    1)If your external system going to support web service cals then send IDoc from External system as a web service, in PI use sender side SOAP and receiver side IDoc receiver channel  to  send IDoc.
    or
    2)Use proxy program ,implement the same ALE logic in PI.
      or
    3)Copy the Extenal IDoc message in to file folder as XML,then use file adapter to pick up this message and send it SAP using IDoc.
    Regards,
    raj

  • Error log on http request from business connector (BC)

    Hi all,
    We are sending http requests from our business connector to one client but the messages keep having log errors :
    server.log details :
    003C24  [B2BCORE.0064.0014] Opening Socket https://www.qab2b.xxx.com:443/invoke/wm.b2b.cxml:receiveCXML  proxy=10.28.38.27:80
    003C25  [B2BCORE.0038.0002] --> CONNECT www.qab2b.xxx.com:443 HTTP/1.0
    003C26  [B2BCORE.0038.0002] --> User-Agent: Mozilla/4.0 [en] (WinNT; I)
    003C27  [B2BCORE.0038.0002] --> Accept: image/gif, /
    003C28  [B2BCORE.0038.0002] --> Host: www.qab2b.xxx.com:443
    003C29  [B2BCORE.0038.0002] --> Proxy-Authorization: Basic YWJ1c2luZXNzY29ubmVjdG9yOmFidXNpbjA0
    003C2A  [B2BCORE.0038.0002] --> Authorization: Basic U0ZSQ2VnZXRlbDoyMDA3KkVBSV9TRlI=
    003C2B  [B2BCORE.0038.0002] > Content-type: multipart/mixed; boundary="--=_Part_0_1941981.1219399983635"
    003C2C  [B2BCORE.0038.0002] --> Message-ID: <7159395.1219399983666.JavaMail.SYSTEM@sw0030>
    003C2D  [B2BCORE.0038.0002] --> Mime-Version: 1.0
    003C2E  [B2BCORE.0040.0001] HTTP/1.1 200
    003C2F  [B2BCORE.0064.0017] Proxy Header <--Connection established
    003C30  [B2BCORE.0038.0002] --> POST /invoke/wm.b2b.cxml:receiveCXML HTTP/1.0
    003C31  [B2BCORE.0038.0002] --> User-Agent: Mozilla/4.0 [en] (WinNT; I)
    003C32  [B2BCORE.0038.0002] --> Accept: image/gif, /
    003C33  [B2BCORE.0038.0002] --> Host: www.qab2b.xxx.com:443
    003C34  [B2BCORE.0038.0002] --> Proxy-Authorization: Basic YWJ1c2luZXNzY29ubmVjdG9yOmFidXNpbjA0
    003C35  [B2BCORE.0038.0002] --> Authorization: Basic U0ZSQ2VnZXRlbDoyMDA3KkVBSV9TRlI=
    003C36  [B2BCORE.0038.0002] > Content-type: multipart/mixed; boundary="--=_Part_0_1941981.1219399983635"
    003C37  [B2BCORE.0038.0002] --> Message-ID: <7159395.1219399983666.JavaMail.SYSTEM@sw0030>
    003C38  [B2BCORE.0038.0002] --> Mime-Version: 1.0
    003C39  [B2BCORE.0038.0002] --> Content-Length: 188225
    003C3A  [B2BCORE.0040.0001] HTTP/1.0 200
    003C3B  [B2BCORE.0041.0001] ssnid=86087kPxFCsECcmXU5DHUAInKY9mEIIU-9355222; path=/;
    003C3C  [B2BCORE.0038.0002] <-- Set-Cookie: ssnid=86087kPxFCsECcmXU5DHUAInKY9mEIIU-9355222; path=/;
    003C3D  [B2BCORE.0038.0002] <-- Content-Type: multipart/mixed; boundary="----=_Part_0_1941981.1219399983635"
    003C3E  [B2BCORE.0038.0002] <-- Connection: Close
    003C3F  [B2BCORE.0038.0002] <-- Content-Length: 0
    003C40  [B2BCORE.0049.0008] Sequence : index=8 depth=3
    003C41  [B2BCORE.0049.0008] Sequence : index=6 depth=2
    003C42  [B2BCORE.0049.0008] Sequence : index=1 depth=3
    003C43  [B2BCORE.0049.0005] Invoke : index=1 depth=4
    003C44  [B2BCORE.0049.0008] Sequence : index=2 depth=3
    003C45  [B2BCORE.0049.0005] Invoke : index=1 depth=4
    003C46  [B2BCORE.0049.0008] Sequence : index=3 depth=3
    003C47  [B2BCORE.0049.0005] Invoke : index=1 depth=4
    003C48  [B2BSERV.0048.9999] Array index out of range: -1
    003C49  [B2BCORE.0049.0008] Sequence : index=4 depth=3
    003C4A  [B2BCORE.0050.0004] Copy failed: (Simple) No source data available: to=/returnedStatusCode(0), from=/returnHttp(0)/cXML(0)/Response(0)/Status(0)/@code(0)
    003C4B  [B2BCORE.0050.0004] Copy failed: (Simple) No source data available: to=/returnedMessage(0), from=/returnHttp(0)/cXML(0)/Response(0)/Status(0)/*body(0)
    003C4C  [B2BCORE.0050.0004] Copy failed: (Simple) No source data available: to=/returnedText(0), from=/returnHttp(0)/cXML(0)/Response(0)/Status(0)/@text(0)
    003C4D  [B2BCORE.0049.0008] Sequence : index=5 depth=3
    003C4E  [B2BCORE.0049.0008] Sequence : index=6 depth=3
    003C4F  [B2BCORE.0049.0008] Sequence : index=7 depth=2
    003C50  [B2BCORE.0049.0008] Sequence : index=2 depth=1
    003C51  [B2BSERV.0056.0003] Unable to send mail. Illegal address
    error java log on server>logs>error:
    2008-08-22 12:16:33 CEST java.lang.ArrayIndexOutOfBoundsException: Array index out of range: -1
         at com.wm.util.List.elementAt(List.java:101)
         at com.wm.lang.xml.token.BlockInputBuffer.getChar(BlockInputBuffer.java:59)
         at com.wm.lang.xml.TextNode.appendSqueezedText(TextNode.java:178)
         at com.wm.lang.xml.ElementNode.appendSqueezedText(ElementNode.java:333)
         at com.wm.lang.xml.ElementNode.getTextOfChildren(ElementNode.java:309)
         at com.wm.lang.xml.Document.getTextOfChildren(Document.java:542)
         at com.wm.app.b2b.services.DocumentToRecordService.recursiveCollect(DocumentToRecordService.java:661)
         at com.wm.app.b2b.services.DocumentToRecordService.bind(DocumentToRecordService.java:356)
         at pub.web.documentToRecord(web.java:667)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:693)
         at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
         at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
         at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
         at com.wm.lang.flow.FlowState.step(FlowState.java:430)
         at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
         at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:693)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:455)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:495)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:392)
         at wm.PartnerMgr.gateway.transport.B2B.OutboundProcess(B2B.java:157)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:693)
         at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
         at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
         at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
         at com.wm.lang.flow.FlowState.step(FlowState.java:430)
         at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
         at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:693)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:455)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:495)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:464)
         at wm.PartnerMgr.gateway.runtime.InboundProcess(runtime.java:423)
         at pub.sap.transport.RFC.InboundProcess(RFC.java:190)
         at java.lang.reflect.Method.invoke(Native Method)
         at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:693)
         at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:455)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:495)
         at com.wm.app.b2b.server.Service.doInvoke(Service.java:464)
         at com.wm.pkg.sap.rfc.Listener.handleRequest(Listener.java:286)
         at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:6022)
         at com.sap.mw.idoc.jco.JCoIDoc$Server.dispatchRequest(JCoIDoc.java:10120)
         at com.wm.pkg.sap.rfc.Listener.dispatchRequest(Listener.java:186)
         at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
         at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1070)
         at com.sap.mw.jco.JCO$Server.listen(JCO.java:5797)
         at com.sap.mw.jco.JCO$Server.run(JCO.java:5731)
         at com.wm.pkg.sap.rfc.Listener.run(Listener.java:101)
         at java.lang.Thread.run(Thread.java:479)
    Thanks for your support on this eai.
    Regards,
    Laurent.

    ok, I think we do not need the save/loadPipeline things, because you can debug the flow without that. I first thought you act as HTTP server, but you issue the client call in the flow itself.
    Looking at the logs more carefully, it shows for example:
    Copy failed: (Simple) No source data available: to=/returnedStatusCode(0), from=/returnHttp(0)/cXML(0)/Response(0)/Status(0)/@code(0)
    But you say have that input:
    <?xml version="1.0"?>
    <!DOCTYPE cXML SYSTEM "http://xml.cXML.org/schemas/cXML/1.2.011/cXML.dtd">
    <cXML version="1.2.011" payloadID="20080825171850716.18637uTQ9ExzheaK+H6b7O9oCAQWPzHA-9355222.8b3632def70da7220004d0b6" timestamp="2008-08-25T17:18:50-CEST">
    <Response>
    <Status code="500">No cXML document received from sender.</Status>
    </Response>
    </cXML>
    So we see that your mappings assumptions do not match the result structure.
    The other problem is that you get a status 500 and do not receive a cXML document, but that might be ok, depending on what parameters you pass to the other HTTP server. At least, you get a meaningful error message back from the server, meaning communication is ok.
    I suggest you first correct those "copy failed" issues and then check by single-stepping where exactly the flow fails and check that input again.
    By the way, when I feed the above cXML into recordToDocument, it works fine. Did you specify other input parameters besides "node" (e.g. recordName) ? And again, are you on Core Fix 8 ?
    CSY

  • Migration from Business Connector to XI

    Experts,
    when migrating from BCo to XI, what is the approach?
    What r the things that can be considered?
    How can we compare XI and BC?
    Any links should help me.
    Thanks,
    -Naveen.

    Hi,
    Have a look on:
    this SDN thread:
    How to move SAP BC config automatically to SAP XI?
    this SAP doc:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
    others found thanks to google:
    http://www.reply.it/upload/File/pdf_boxjolly/eng/CAPR05_sapXI_ENGLISH.pdf
    http://www.asug.com/client_files/Calendar/Upload/MigrateToXI%20ohio%20asug.ppt
    Moreover a session will be organized to the SAP tech:
    https://www.sdn.sap.com/irj/sdn/docs?rid=/webcontent/uuid/92e6dde6-0901-0010-f3a3-9ed771f90e71 [original link is broken]
    Hope this help you
    Mickael

  • Upgrading From Business Objects XI2 to XI3.0

    I can't seem to find the BusinessObjects Enterprise XI 3.0 Upgrade Guide.  Does anyone know where I can find it?

    Hi Shane,
    The upgrade guide is not directly on the product guides. You have to follow the link to the SAP service marketplace.
    Within the guide there are 3 options
    1) Install directly on top, only available for simple (single node) installations
    2) Install new and update CMS DB
    3) Install new and copy over objects.
    Regards
    Alan

  • Delta between Business Connector 4.8 and 4.7

    This seemed like the most logical place to put my post so here it goes..
    We are assessing our options for replacing/upgrading existing Business Connector installations that will shortly be out of support (OSS Note 571530).Whilst researching our options I have come across OSS Note 1094412 which describes a new version of 4.8 becoming available in July 2008.
    Information on BC4.8 is virtually non-existent on the web - can anyone provide me with details of the delta between 4.7 and 4.8, licensing structure, hardware requirements, support/maintenance strategy and ease of migration from 4.6/4.7 to 4.8?
    As an aside it is very interesting that SAP has chosen to provide BC 4.8, presumably to ensure BC can continue to runs on supported O/S' and Java environments, when SAP XI/PI is being touted as the de facto integrator for companies with a significant SAP presence. Maybe customers are not quite as keen to move on/remove their BC instances as SAP would hope...

    Hi Daniel,
    We have been on this topic for years (some vested interest through product development).
    What seems to have happened, from what we can gather, is that Netweaver XI/PI uptake hasn't happened as fast as initially hoped (SAP was looking at an intial end of life of Dec 2004 for BC).
    The case is quite simple. BC is free, easy to install and maintain. XI/PI, new product, takes a while to stabilize, much more feature rich, but at the same time more complex and less performing (and did I mention the license cost?).
    What we know about BC 4.8 and this is purely based on talking to people and reading about it, we have not seen / tested BC 4.8 ourselves - Mainly a platform upgrade, no significant changes. Most likely free as well (the original contract states that if SAP charges money for BC they have to pay extra to Webmethods / Software AG) accordingly. I would expect to see a few new built-in function and hopefully some hooks into standard SAP monitoring tools.
    I think you hit the nail on the head. We have seen customers panic and move to non-Netweaver platforms from BC to be on a supported solution (back when EOL was imminent before 4.8 was released). Why non-Netweaver? Because many customers use non-SAP Integration Products as well and they tend to drift to known solutions instead of trying to manage the risk of migrating to a unfamiliar product.
    I would not expect any major changes that would make migration to 4.8 hard. If there would be some major issues then that would signal some significant developments from SAP and that would be a strange thing at this point of the product lifecycle.
    End of life for BC 4.8 is in 2012 or thereabouts if I remember correctly, this was part of some note which was released/updated towards the end of last year.
    You might want to make some design calls if you continue developing your integration scenarios on BC. The best format to allow for an easy / relatively painfree migration to PI one day is by using BC graphical MAPS where possible, NOT XSL maps as wrongfully indicated in so many previous posts and articles. XSL is the hardest format to migrate to PI even though it might look superficially as a compatible format...
    Cheers
    Kalle

  • Business connector developer-Error message 'No IDOC found in input'

    Hi,
    Please note that this query is related to business connector developer not to XI.
    I have created a flow service based on an IDOC. When I tried to test the service from the business connector developer it gives me an error 'No idoc found in input'. I have done the setting based on the business connector configuration guide. The idoc also send to the port successfully.
    Can anyone guide me how to trigger the test from business connector developer for an idoc.
    Thanks
    Jim.
    Edited by: Jim Jose on Jul 13, 2011 5:58 PM

    Hi,
    Probably you would have created the routing today, with valid from todays date. But the order you are creating may be with start date in past and system is not able to find and valid routing for the day.
    I would suggest you to remove both the Basic "Start" and "End" and change the scheduling type to "Current date Scheduling", now enter. If system still not finding the routing, use the function "Read PP Master data".
    Regards,
    Prasobh

  • Problems Upgrading from BO XI to BO XI 3.0

    I attempted an upgrade from Business Objext XI (Crystal Enterprise Server) to XI 3.0. The install went fine until it got to the registering modules, which took hours and hours. It errored out that the CMS service was not running and could not continue. I looked at all the services and they are all disabled. The onlything running is the upgraded Tomcat Server.
    Looking in the Central Configuration Manager for XI 3.0 Tomcat is the only thing listed. No other services....where do I go from here?
    I reran the install and chose Repair, it ran through like it ran and got to Finish, but still nothing.
    Help, what do I do?
    Thanks,
    Mark W.

    That's XIR1, there is no upgrade option.
    The SIA in XI 3.0 replaced the other services and now runs everything as child propcesses so in the CCM you only see the SIA (Server Intelligence Agent)
    If it's missing you should be able to add it, and it should create the other processes for you when you do.
    There's questions as to whether or not 3.0 and XIR1 can be installed side by side, is that what you have done? or is it on another server?
    Since you are XIR1 you should install 3.0 on a clean server and then migrate via import wizard (in the program files BO group). If you get stuck then open an incident with support.
    Regards,
    Tim

  • Business  Connector and XI

    Dear Sir,
    Are there any preson change from Business Connector to use XI instead ?? Please kindly advise . how did you convert from BC  to XI
    Thank you and best regards,
    Vimol

    Hi Vimol,
    Check this "How to" guide, for the required information
    https://websmp205.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202&_OBJECT=011000358700005272252005E
    other How to guides,
    https://websmp101.sap-ag.de/~form/sapnet?_SHORTKEY=01200252310000071155&_SCENARIO=01100035870000000202
    have a look at this also...
    Re: Connectors and Xi...
    also,
    XI FAQ’/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    I hope this will help you.
    Regards,
    Saurabh...
    Reward with points if found helpful.

  • Business connector exceptions(java)

    Hi,
    I am getting java exceptions from Business connector server continously.Need to know the root cause of these errors and how they can be eliminated.
    The error i am getting is as below:
    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
               at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
               at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
               at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
               at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
               at pub.sap.client.createTID(client.java:373)
               at java.lang.reflect.Method.invoke(Native Method)
               at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
               at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
               at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
               at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
               at com.wm.lang.flow.FlowState.step(FlowState.java:430)
               at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
               at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
               at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
               at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
               at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
               at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
               at java.lang.Thread.run(Unknown Source)
    Any help on this regard would be highly appreciated.
    Thanks in advance.
    Regards,
    Priya.

    Hi Astrid,
    thanks for ur reply.
    i will chk that out and by the way the below is the full error log am getting and also there is some data loss in inbound messages to sap due to this error and IDOC exception.can u pls help on this issue
    Error being reported is:
    com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
    at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
    at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
    at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
    at pub.sap.client.createTID(client.java:373)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    and
    com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
    at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
    at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
    at pub.sap.client.sendIDoc(client.java:356)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
    at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
    at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
    at com.wm.lang.flow.FlowState.step(FlowState.java:430)
    at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
    at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
    at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
    at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
    at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
    at java.lang.Thread.run(Unknown Source)
    thanks in advance
    regards,
    priya.

  • Business Connector - Out of Memory error

    Hello,
    We have several services running from business connector and some which are called from SAP as remote function calls.  One error which keeps resurfacing is:
    java.lang.reflect.InvocationTargetException:OutOfMemoryError
    Can anyone tell me how to fix this?  At the moment we restart BC and move some log files and it seems to do the trick but we need to start being pro-active to minimise disruption to our clients.
    Any suggestions welcome.
    Thanks,
    Gill

    Hi,
    you should take care that you sweep regularly the SAP-transaction-log. There is a transaction 'sweepTransaction' which can be scheduled on a regurlar basis to get rid of old transactions.
    Another possible reason is that your service is consuming vast amounts of main memory, this could happen with very large objects, i.e. extremely big xml-files.
    Hope you find a solution.
    Regards, Astrid

  • Business Connector work with ECC 6.0 or have to switch over to PI - Upgrade

    Hi
    Client want the upgrade their current SAP system from 4.6C to ECC 6.0.
    Like to know if Business Connector would work with ECC 6.0 or they have to switch over to PI.
    Please Help
    Thanks

    i think BC will work ,
    chek the below thread for
    what are abaper tasks during upgrade to ECC 6.0
    what are abaper tasks during upgrade to ECC 6.0?
    pls reward points if helpfull
    regards
    kummari
    Edited by: kummari on Jul 4, 2008 8:05 AM
    Edited by: kummari on Jul 4, 2008 8:20 AM

  • Business Connector 4.8 :upgrade

    Dear all,
    I need to upgrade the SAP Business connector from version 4.7 to 4.8. I have already gone through the documents mentioned in service.sap.com/connectors, especially through the SAP BC migration guide. My concern is, customer does not wants to uninstall SAP BC 4.7 and proceed with 4.8, which is the normal procedure. They want to run both the versions together in the same server and once they are OK with 4.8, we can uninstall 4.7. The question is: Is it OK to run both the versions on same server? Is there any precaution I need to take before I install 4.8 in the same server where 4.7 is currently running? If it is OK, can I use the same transfer method which is described in migration guide to export and import the configurations?
    Thanks for your valueable comments.
    Rajeev

    If installation is possible, the ports can be configured to use different onces in each server...
    But as I said before, why compromising a productive box with experiments when running Business Connector is possible in a regular desktop for testing purposes.
    Thats my 2 cents
    Regards
    Juan

Maybe you are looking for