Business connector on Virtual Server

Hi All,
I need a urgent help to know, if there are any disadvantages if we setup a Business connector environment in Virtual Server rather than a Physical server?
The situation is, currently I have business connector working on Physical server, for which a Warranty is reach end of life and no further support to the hardware is possible from the mother company.
Hence we have a plan of moving the Business connector in the physical server to a new virtual server provided by our infrastructure team as virtual servers are less costlier than physical server. Hence I would like to know how good to choose Virtual Server for business connector.
Also, do any one can suggest what is the best way of approach would be, to move the existing Business connector server operations to new hardware i.e. is it fine to do pure system copy and will it work? or else do I need to redo from installing the BC software and configuring it manually.
Thanks,
Bindu

Hi Bindu,
we are running all of our BC servers on VMWare images. Works perfectly. You are better off installing the BC from scratch and remember if you are installing it onto Windows XP or alike you should select the Windows 2000 compatibility mode both for installation as well as when running it. This will allow it to run just fine.
Be aware that BC 4.8 is due to be released soon and that will give you a supported, JVM updated version of BC for Windows and Linux. Currently all JVM versions are un-supported for previous BC versions.
If you use the same name and IP for your virtual server than what you had for the previous physical server you should not see any changes in your configs. Again, we have moved these from physical to virtual doing just that and it all worked well.
If you don't care about support at this point in time then you can also run the whole lot on a newer JVM, though if this is feasible or necessary is up to you.
Cheers
Kalle

Similar Messages

Business Connector 4.8

Hi there,
I am just about to install SAP Business Connector 4.8 on our Linux based
virtual machines. Every link I click on the portal for the download is directing
me to the options below which to my mind is windows based only.
I am missing something here? Shoudln't there be Linux/Unix versions as well??
Many thanks
Andy
ZIP
51042500_1
SAP Business Connector 4.8 Server and DEV STD ENCR WIN-32B
Info
116337
13.11.2012
ZIP
51042500_2
SAP Business Connector 4.8 Server and DEV STD ENCR WIN-64B
Info
117465
13.11.2012
ZIP
51042505_1
SAP Business Connector 4.8 Server and Dev Strong ENCR WIN32B
Info
116338
28.09.2012
ZIP
51042505_2
SAP Business Connector 4.8 Server and Dev Strong ENCR WIN64B
Info
117461
28.09.2012

I think BC 4.8 recognizes that automatically correctly.
If the button is not there anymore, you dont have to care about it.
Just give it a try...
CSY

SAP Business Connector on Windows XP

I've been trying to get the SAP Business Connector 4.7 to work on Windows XP professional but haven't been very successful. The business connector seems to install okay, but when I try to start the business connector through the server.bat file it generates the following errors:
(loglevel = 4)
Loading WmPartners package
00000E [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.EmailTransport:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.EmailTransport
00000F [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:saveMessage: [B2BSERV.0026.9106] No method saveMessage in class wm.PartnerMgr.xtn.admin
000010 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:view: [B2BSERV.0026.9106] No method view in class wm.PartnerMgr.xtn.admin
000011 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:saveRoutingRule: [B2BSERV.0026.9106] No method saveRoutingRule in class wm.PartnerMgr.gateway.admin
000012 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:convertWildCards: [B2BSERV.0026.9106] No method convertWildCards in class wm.PartnerMgr.gateway.admin
000013 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.B2B:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.B2B
000014 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:editStore: [B2BSERV.0026.9106] No method editStore in class wm.PartnerMgr.xtn.admin
000015 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.FTPTransport:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.FTPTransport
000016 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:invokeViewService: [B2BSERV.0026.9106] No method invokeViewService in class wm.PartnerMgr.xtn.admin
000017 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:viewMsgContent: [B2BSERV.0026.9106] No method viewMsgContent in class wm.PartnerMgr.xtn.admin
000018 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:updateTransports: [B2BSERV.0026.9106] No method updateTransports in class wm.PartnerMgr.gateway.admin
000019 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.admin:invokeService: [B2BSERV.0026.9106] No method invokeService in class wm.PartnerMgr.gateway.admin
00001A [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.xtn.admin:log: [B2BSERV.0026.9106] No method log in class wm.PartnerMgr.xtn.admin
00001B [B2BSERV.0028.0005] Loading SAP package
00001C [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.RFC:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.RFC
00001D [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.BAPI:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.BAPI
00001E [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.XML:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.XML
00001F [B2BSERV.0026.0002] Failure while loading service sap.bapi:encodeToFile: [B2BSERV.0026.9106] No method encodeToFile in class com.wm.pkg.sap.bapi.BusinessDocumentCoder
000020 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:bapi2rfc: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000021 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:rfc2bapi: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000022 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:bapi2ale: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000023 [B2BSERV.0026.0002] Failure while loading service sap.admin:listGatewayServices: [B2BSERV.0026.9106] No method listGatewayServices in class sap.admin
000024 [B2BSERV.0026.0002] Failure while loading service sap.bapi.Mapper:ale2bapi: [B2BSERV.0026.9104] Missing class sap.bapi.Mapper
000025 [B2BSERV.0026.0002] Failure while loading service wm.PartnerMgr.gateway.transport.ALE:startup: [B2BSERV.0026.9106] No method startup in class wm.PartnerMgr.gateway.transport.ALE
000026 [B2BSERV.0028.0005] Loading WmSamples package
000027 [B2BSERV.0028.0026] Warning: Deprecated service type (webtap) in service sample.webtap:logApp in package WmSamples
000028 [B2BSERV.0028.0005] Loading WmDB package
These errors don't stop the business connector from starting up, but the errors are not normal behaviour. When I try to start the business connector through a Windows service then I get the message "Could not start the SAP Business Connector Service on Local Computer. Error 126: The specified module could not be found".
I have a working business connector installation on a Windows 2000 server, and when I checked the error log of that installation I noticed that it had logged the same errors about the 'WmPartners' package. It on the other hand didn't have any problems loading the 'SAP' package.
I tried installing the business connector on two different systems with identical results. Has anybody been able to get the business connector to work on Windows XP?

HI,
I have no idea clearly about BC.. but ..
See the following links.. may be helpfull..
Business connector
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8609b90-0201-0010-c6bc-a41b611c6dac
SAP Business Connector on Windows XP
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/92e5bd90-0201-0010-b799-dfdc27f3100a
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a8424011-0d01-0010-e19d-e5bd8ca52244
If usefull .. points rewarded..
Regards
Chilla..

Business connector server on Virtual Server

Hi,
Currently our 4.6 release Business Connector servers running on Windows NT Operating system. We would like to upgrade them to BC release 4.7 on Windows 2000 operating system on Virtual servers.
Are there any known issues/disadvantages if we install Business connector servers on Virtual Server rather than a Physical server?
These virtual servers will be in the same domain as that of SAP systems. Host names of the upgraded Virtual servers will be same as the current production BC hosts.
Thanks,
Srini

Technical Data
These functions are:
Changed, new, deleted
For Release
   Software Component
·        Component: SAP Business Connector (external)
·        Release: 4.7
Assignment to Application Component
BC-MID-BUS (SAP Business Connector)
Country Setting
Valid for all countries
Use
The following information provides you with an overview of the new features in SAP BC Release 4.7: It also tells you about incompatible changes that you need to know about before performing an upgrade.
SAP BC 4.7 is based on Integration Server 4.6 from webMethods. However, the SAP BC elements in Integration Server 4.6 have been redeveloped (see below for details).
Features
Additional Functions in SAP BC Developer
As well as SAP BC Administrator GUI, you can now use SAP BC Developer to perform typical development tasks. You do not need administrator authorizations in SAP BC Developer to do this. For example, with SAP BC 4.7 you can use SAP Lookup to generate elements for the Developer. This enables you to gather information about function modules, structures (tables), BAPIs and IDocs in an SAP system, and then generate outbound maps or records for these objects directly.
SAP BC Developer contains a new menu, SAP, which contains the following functions:
·        Look up a function module and generate an outbound map
·        Look up a structure definition and generate a record.
·        Lookup a business object.
·        Look up an IDoc and creating a Record.
·        Browser for Function Maps.
In addition, the Developer now also supports the following actions:
·        Generate an SAP inbound map if you want an SAP system to run a service in SAP BC.
·        Generate an SAP outbound map to execute a function module in an SAP system.
·        Generate a record based on an SAP ABAP Dictionary structure.
·        Generate a record based on an SAP IDoc.
SAP BC Developer now also supports a proxy bypass list. This means that you no longer need to define whether a connection runs through a proxy; instead, the bypass list performs this task.
New Public Services on SAP BC Server
pub.string:gzip
Compresses the specified input string and generates a check total (optional). For measurements or for statistical purposes, the lengths of the zipped and unzipped strings are provided as output.
·        pub.string:ungzip
Decompresses a specified input string, which was compressed with pub.string:gzip, and verifies the check total (optional).
·        pub.string:numericParse
Analyzes a number in accordance with a given number pattern.
·        pub.math:randomLong
Generates a pseudo random number and sends its string representation in a pipeline variable. You can use this number as a universal identifier with an acceptable level of security, as long as it is used in non-distributed scenarios and for a small number of variables.
·        pub.file:head
Shows the start of a given file.
·        pub.file:tail
Shows the end of a given file.
·        pub.flow:sleep
Puts the current service into sleep mode for the specified period (in seconds).
Restructuring of the WmPartners Package
The WmPartners package in SAP BC Server has been completely restructured and now offers the following enhancements:
·        Improved status information in the messages displayed in the Transaction Store and the Audit Log. This solves a range of problems, such as incorrect status information being displayed by IDocs.
·        Improved search and sort options for transactions in the file system of the Message Store. In the Transactions menu, SAP BC Administrator GUI offers you a new option, Message Store Query Settings, which enables you to select and delete transactions. In Release 4.7, the Message Store can also be displayed on separate pages, which makes it easier to edit large numbers of transactions.
·        Improved search and sort options for Routing Rules. In the Routing Rules menu, SAP BC Administrator GUI offers you a new option, Routing Rule Filter Settings, which enables you to restrict the number of routing rules that are displayed, and to sort the display. The filter accepts all combinations of characters, and the placeholders '*' (string of characters) and '?' (one character). This makes it easier to sort and search for routing rules, especially if you need to process a large number of communication partners and message types.
·        Forwarding the "Confirm Event" tRFC (triggered by an SAP system) to the next receiver (for the following transports: B2B Service, ALE (R/3 IDoc), and XML (only if another SAP BC is the receiver)) and triggering "Confirm Event" from an external client. Both of these cases can be significant if the final receiver is an SAP system. In this case, "Confirm Event" removes the transaction ID from the ARFCRSTATE table, which can improve system performance significantly when a large number of tRFCs are being processed.
Support for Distributed Statistic Records (DSRs)
SAP BC has supported the generation of DSRs since Release 4.7 DSRs enable you to monitor the performance of each SAP system and its components. In this way, you can check how much system load is produced by each individual component, and how many resources are being used. This enables you to identify "performance leaks" and optimize system performance.
The DSR support integrated in SAP BC also allows you to measure the total retention period of a process in SAP BC. To evaluate the DSRs, you require additional SAP software, including specific versions of the SAP Solution Manager, and the RFC Library. The exact requirements are still being defined.
The details will be published in SAP Note 620418. You can find a link to this SAP Note on the SAP BC download page at http://service.sap.com/sbc-download.
SAP BC Server Core Enhancements
·        Reverse Invoke
The reverse invoke protocol has been enhanced and now allows you to forward more information, such as IP addresses.
If, for example, an application fails because a connection is broken, and other working connections exist, the connection is checked using a ping.
From now on, the internal server can open or reopen a defined number of connections, if necessary.
A document is generated for any exceptions on the internal server.
·        Email Listener
New Features in the Email Listener
¡        Reprocessing of invalid mails for IMAP Server
¡        Processed mails selected as "unread" if they have not been deleted.
You can also specify whether mails with exceptions are deleted or not.
·        Update Manager
The Update Manager manages fixes and patches for the upgrade of an SAP BC Server. Previously , the Update Manager allowed a fix to set other fixes as obsolete, using the updateVoidList field in the update.cnf file of the fix. An obsolete fix is not shown in classpath, but up to now the Update Manager has not been able to give a fix in classpath priority ahead of this other fix. The Update Manager has now been enhanced to support these fix priorities: The update.cnf file in the fix now contains an updatePrecedeList field.
Incompatible Changes
SAP BC Delivery Without JVM
The Windows Version of SAP BC 4.7 is no longer delivered with a Java Virtual Machine (JVM). The SAP BC 4.7 Installation Guide describes the JVMs that are supported.
See also
For more information, see the documentation on the SAP Business Connector, under
·        http://service.sap.com/connectors (SAP Business Connector ® SAP Business Connector in Detail ® Documentation).

Business Connector and sap router on same server?

Hello,
We are investigating currently in order to install "Business Connector" and "Sap router" on a same dedicated server.
I would like to know if it is possible or not recommended, etc... if there are some guidelines.
If someone has experience in this solution.
Many thanks for your help

I can't see a reason why not... any particular concerns?
Regards
Juan

WebMethods Integration Server Vs. SAP Business Connector 4.7 (BC)

Hi All
       We have to integrate non SAP systems and SAP systems for that we have 2 options
1)   SAP Business Connector 4.7 (BC)
2)   webMethods Integration Server
       which one will be better option for this kind of POC by considering all the issues like interaction with SAP RFC or IDocs, performance, load balancing, salability, maintenance, etc.
     please tell us pro's and cons of both to decide upon which is better option.
     Thanks in Advance
Thanks
Ninad

It is the same product, with different branding.
The only thing is that SAP consider the SAP BC end-of-maintenance, and suggest to use XI.
Regards,
Sandro

Com.wm.app.b2b.server.ServiceException with Business Connector

Hi Everybody,
I could need some help with the Business Connctor 4.8...
We just made an upgrade from SAP Business Connector 4.7 to 4.8. The new Business Connector also was moved to another server.
The installation was fine. In SM59 the RFC test works and also the MAPS are all in green status.The routing should also be fine.
I have the following problem when using the FM IDOC_INBOUND_ASYNCHRONOUS to send invoices to the customers I get the following error:
com.wm.app.b2b.server.ServiceException: com.wm.app.b2b.server.UnknownServiceException: [B2BSERV.0026.9201] Unknown service: wm.PartnerMgr.flows.MANDANT001.1STBP:INVOIC
I also created and imported the necessary certificates to communicate with our partner by https.
Please could you help? Is it a problem in the configuration or do I miss something with the certificates?
Thanks in advance!
Kind regards,
Lu Huynh

Hi Lu,
Yes that note was for SPA BC 4.7. I though it could provide you with some more insight.
Anyway, can you recheck whether the settings which you have done for IDoc in SAP BC. There might be some problem with them.
Also check this thread, it might be helpful (but i am not sure)
[B2BSERV.0026.9201] Unknown service: wm.PartnerMgr
One doubt the error message says Unknown service: wm.PartnerMgr.flows.MANDANT001.. IS the client 001?
Regards
Suraj

Business connector installation error

Dear community,
I am trying to install bc 4.8 x64 on win2008 R2 x64 std ed.server (in vmware).
When I run the installer (BCServer48_x64.exe or BCServerXpt48_x64) I get an error:
>business connector install could not find a java virtual machine to load
>you may need to reinstall a supported java virtual machine
As I understand it there is a sap jvm integrated, so separate jre install is not needed.
In any case I have also installed separate java :
>java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
but this does not change the error.
Win2008 R2 is supported according to pam and note 1094412.
I have tried using compatibility settings for win server 2003 but no change.
Any advice ?
Rgds, Eirikur.

It would have been helpful if you shared how to execute this fix.
Here by the way I fixed it:
First:
Make sure you have a JDK installed!
I used: JDK 6: sapjvm-6.1.043-ntamd64.zip
You can find it here: https://tools.netweaver.ondemand.com/ Press the Additional software tab.
Second:
Go to: http://java.com/en/download/help/path.xml
Here they will explain you how to edit the PATH for different OS. The Windows 7 fix works on Windows Server 2008 R2.
Third:
For windows Users:
When you have the Edit PATH screen open add the correct path that leads to your JDK.
For me it was: ";C:\Program Files\Java\sapjvm_6\bin" (Paste without the quotes but add a ; in front of your path)
Kind regards
Jérémy

Problem in sap business connector installation

Hi,
I have gone through installation guide ,but in it nothing was mentioned about c:\sapbc47\server\bin\runserver.bat file.Please help me to solve this problem.

7.5 Various problems on a 64bit architecture
At the time of writing (August 2002) no 64bit version of the Java Virtual Machine is yet available
for the following 64bit operating systems: AIX, HP-UX, Solaris. Therefore on these platforms the
32bit version of the JVM has to be used. This leads to the problem, that the 64bit version of the
native library libjmon.a (AIX), libjmon.sl (HP-UX) or libjmon.so (Solaris) cannot be loaded into the
process started by the JVM. (When starting monitoring, you'll see one of the following error
messages:
AIX: java.lang.UnsatisfiedLinkError
<sapbc>/packages/SAPMonitoring/code/libs/libjmon.a load ENOEXEC
on shared library(s)
<sapbc>/packages/SAPMonitoring/code/libs/libjmon.a
HP-UX: java.lang.UnsatisfiedLinkError:
<sapbc>/packages/SAPMonitoring/code/libs/libjmon.sl: specified
file is not a shared library, or a format error was detected
Solaris: java.lang.UnsatisfiedLinkError:
<sapbc>/packages/SAPMonitoring/code/libs/libjmon.so: ld.so.1:
/usr/j2se/bin/../bin/sparc/native_threads/java: fatal:
<sapbc>/packages/SAPMonitoring/code/libs/libjmon.so: wrong ELF
class: ELFCLASS64
This error should disappear, once you install a 64bit Java Virtual Machine. But until 64bit JVMs will
be available, the following workaround can be used:
From the Business Connector download page also download the zip file with the 32bit libraries for
your operating platform. From that extract the two files sapccmsr and libjmon.a/sl/so and copy them
to the directory <sapbc>/packages/SAPMonitoring/code/libs. (The sapccmsr also
interacts with the libjmon library and therefore must also be a 32bit version. The saposcol only
interacts with the operating system and therefore still has to be used in its 64bit version.)
After a restart to unload the old 64bit versions from the system, the error should be fixed.
Best Regards,
Mike

How do we Integratet SAP to Non-SAP Using Business Connector

Hi Experts,
I am new to SAP Business Connector !!
and what are the Forms ? for SAP Business Connector Related Postings ??
!! I have a requirement to integrate sap to non-sap with Business Connector !!
We need to Generate the SAP Data In xml Format ? and the Non-sap System can Understand Only XML Formated data.
Is there any way Business Connector Box can Pull the XML file from R/3 Application Server and store the file in the Business Connector Server. from that How do we Sent XML file to Non-sap. How do we Integrate ??
what transaction code will trigger this event ? I mean is ther any SAP Transaction Code to Integrate Business Connector?
For Eg. like in R/3 SD to FICO and MM Integration.
Please Give your Valuable Suggests..
Thanks .
Upender.

Hi,
It is not an issue, It will be a separate project :-).
The right forums for this,
Expert Forums » SAP NetWeaver » Process Integration
www.wmusers.com
Also go through the following links:
http://www.sapgenie.com/interfaces/businessconnector.htm
http://www.sapgenie.com/mysap/bus_connector.htm
/people/bla.suranyi/blog/2006/07/10/xi--sap-business-connector-integration-using-the-http-adapter
http://help.sap.com/saphelp_nw04/helpdata/en/6a/3f93404f673028e10000000a1550b0/frameset.htm
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
https://websmp104.sap-ag.de/connectors
Thanks and Regards,
Chandra Madapati

Problem establishing Business Connector 4.8 and R/3 connection

Hello,
I'm currently running a few SAP Business Connectors 4.7 servers for my company, all connected to SAP R/3 4.7 backend, and everything works fine.
I tried to setup the new BC 4.8, on a fresh Windows 2003 server, the install went fine, but when I try to make a new R/3 connection, with a working and existing RFC user (previously used by the former BC 4.7), I have the following error message :
Error : class com.sap.conn.jco.JCoRuntimeException
Message : Name or password is incorrect. Please re-enter on 192.168.0.4 sysnr 00
Service : sap.admin.server:getInfo
I don't understand because if I unplug the 4.8 server and plug back the 4.7 one with exactly SAME user/password and same R/3 connection properties, it works fine...
I precise I re-typed manually the login/passwords in both BCs to ensure it's not due to a typo error.
I have read that JCO has changed between 4.7 and 4.8 releases. Could it have an impact ? Also do I still need to install a librfc32.dll in my windows/system32 directory ?
Any clues ?
Thanks in advance for your help
P.
Edited by: Patrick TOURNEUR on Jul 21, 2008 6:40 PM

Hello,
just for your info, the JCo implementation has changed about this login function. BC 4.8 is using JCo 3, 4.7 used JCo 2.
I never understood the whole problem completely, but as you found out by yourself, you are safe if you enter the user/pwd in SAP only uppercase, and also in BC
SAP changed this user/login up/lowcase stuff at some time, which has caused many trouble in projects.
CSY

NULL Value in SAP Business Connector (BC47_CoreFix7 )

Dear All,
I am working with SAP Business Connector and some times i get NULL value in (PROXY SERVER) in Secure Proxy (HTTPS) so i need usualy to remove it manully and save the changes.
Would you plesae help me to solve this issue either to delete automatically or to have any idea to prevent getting this NULL value.
Thanks in advance..
Message was edited by: Hassan Hakeem

Dear,
i need the answer ASAP pleasssssssssssse.
Thanks..
Message was edited by: Hassan Hakeem

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

Flat File Transfer from SAP R/3 4.7 to SAP Business Connector 4.8

Hi Experts,
I have a requirement of transferring a flat file from my R/3 SAP 4.7 Box Application Server to the Business Connector 4.8 Box. I am new to SAP Business Connector and I am not to sure whether FTP works if I use a shell script in SAP R/3. Also, is there any way Business Connector Box can pull the file from R/3 Application Server and store the file in the Business Connector Server.
Any help will be appreciated!!!
Regards,
Subhhrangsu

Hi,
There are many ways thru which you can pass document to SAP BC:
You can HTTP, FTP, Email document to SAP BC.
SAP BC has predefined services for all of them.
For FTP document to SAP BC:
1 Initiate an FTP session on SAP BC Serveru2019s FTP listening port ( this can be found out from SAP BC administrator or from SAP BC homepage).
2 Point to the directory that contains the service to which you want to pass the XML
document.
Example cd \ns\Purchasing\SubmitOrder
3 Copy the XML document to this directory using the following command:
put XMLDoc.xml
Where XMLDoc.xml is the name of the file that you want to pass to SAP BC Server.
Example put PurchaseOrder.xml
Above code can be written in a batch file and you can schedule it to run at interval of minutes.
You can write java client program as well to upload file and map it to String variable of Flow service of SAP BC.
As Micheal said, you can look at sapbc/Developer/doc folder to look for more options.
Best Regards,
Divyesh

RFC function callls a SAP Business Connector Flow - only upper case

Hi everybody,
I wrote a function in SE37 which is calling a Flow in SAP Business Connector.
R/3 and SAP BC, both are Non Unicode systems.
The export parameter is TYPE makt-maktx.
The call to SAP BC works fine. Only all the text I can see in the pipeline of SAP BC is upper case.
I checked wether the domain of the makt-maktx allows case sensitive texts.
This is OK.
I have no idea how I can tell SAP BC to receive case sensitive texts.
I checked the forums. Seems nobody had such a problem.
Can somebyody help?
Best regards
Jochen
Hi to all,
it was not the JAVA Version, or a bug or whatelse.
I just ingnored while testing in SE37 that there is
a Flag [X] case sensitive - That's all!
Shame on me!
Greetings Joe
Message was edited by:
Jochen Seeliger

Hi Priya
Seeing the messages, it appears that server is down.
"java.net.ConnectException" occurs whenever you try to connect to a system which is not up and running.
cheers
Sameer
PS: Please award points if you find the answer useful

Business connector on Virtual Server

Similar Messages

Maybe you are looking for