Package loading issue in Business Connector - Urgent Production deployment

Hi,
I created few additional flows in the Dev BC server and published them onto the Prod BC server. From Prod server, I tried installing them using Install Inbound release link. But nothing is happening after the link is clicked, i.e neither i get any error / warning message nor the new flows gets loaded into the existing package. Not sure why. As another attempt, I manually exported the zip file with all the new flows into the Prod server and retried installing the flows, but, with no result. I am not sure why this is happening.
Later, I observed that in the packages folder, there were sub-folders created for all the flows I wanted to import. Hence, as a final attempt, I tried recovering the package from Admin UI but unfortunately, now the package itself is not visible from the UI. All the original files, folders etc and new files / folders related to the newly created flows are still under the sapbc47/Server/packages/<My_Package> folder.
Can anyone suggest why the package is not visible in Package Management screen of the Admin UI while the related files are still in the file system.
Any valuable suggestions are highly appreciated. Cheers.
Prabhakar

Hi,
Restarting the Production server installed all the previously published packages from the QA server but the issue of on the fly package Publish - Subscribe still exists.
Any sugg are appreciated.
Cheers
Prabhakar

Similar Messages

  • Issue with Business connector to ECC

    Hi All,
    We are having issues when the orders from BC to vendors are failing.The chain is like this ECC idoc to BC conversion happens to xml and then sends to the vendors.We are getting a message saying like this
    com.wm.lang.flow.FlowException: [B2BCORE.0049.9010] Service 'sap2vendors:ORDERStoXML' invoking unknown service 'Failed HTTP Post' at '$default'. The service may have been renamed, moved or disabled.
    The whole problem is that some are failing and some are passing through.Thanks.

    Hi,
    When checked the server log.Got the below error.
    TransactionManager: Creating new Transaction 0A0D811E16654DCA1F7A0741
    000453  [B2BPCKG.0074.0002] TransactionManager: 0A0D811E16654DCA1F7A0741: State changed to Created
    000454  [B2BPCKG.0073.0032] Runtime: <-- Sender: 1000 Receiver: <number>
    MsgType: ORDERS Tid: 0A0D811E16654DCA1F7A0741
    000455  [B2BPCKG.0073.0037] Runtime: invoking Flow sap2vendors:receiveORDERS000<number>
    000456  [B2BPCKG.0073.0045] B2B Transport: --> OutboundProcess invoking sap2vendors:ORDERStoXML locally
    000457  [B2BCORE.0064.0014] Opening Socket https://<IPAddress>/invoke/CorporateExpress/receive  proxy=sparpxyapp.<hostname>:8080
    000458  [B2BPCKG.0073.0047] B2B Transport: --> OutboundProcess error: [B2BCORE.0049.9010] Service 'sap2vendors:ORDERStoXML' invoking unknown service 'Failed HTTP Post' at '$default'. The service may have been renamed, moved or disabled.
    000459  [B2BCORE.0077.0002] Unsupported email encoding  specified.  Defaulting to utf-8
    00045A  [B2BPCKG.0073.0039] Runtime: error in RR Flow sap2vendors:receiveORDERS<number>
    com.wm.app.b2b.server.ServiceException: com.wm.lang.flow.FlowException: [B2BCORE.0049.9010] Service 'sap2vendors:ORDERStoXML' invoking unknown service 'Failed HTTP Post' at '$default'. The service may have been renamed, moved or disabled.
    00045B  [B2BCORE.0077.0002] Unsupported email encoding  specified.  Defaulting to utf-8
    00045C  [B2BPCKG.0074.0006] TransactionManager: saved message body packages/WmPartners/pub/mailbox/<number>/ORDERS/0A0D811E16654DCA1F7A0741.values
    00045D  [B2BCORE.0077.0002] Unsupported email encoding  specified.  Defaulting to utf-8
    00045E  [B2BPCKG.0074.0002] TransactionManager: 0A0D811E16654DCA1F7A0741: State changed to Rolled back
    00045F  [B2BCORE.0077.0002] Unsupported email encoding  specified.  Defaulting to utf-8
    Edited by: Ambarish annapureddy on May 19, 2011 12:48 PM
    Edited by: Ambarish annapureddy on May 19, 2011 12:48 PM

  • Business Connector 4.7 connection issue with GB HMRC

    Inland Revenue have changed their URL's and SAP issued a new note 1614588 for this change.  As instructed in the note I installed the new package and now when we try to poll with Inland revenue we get a connection refused.
    I am not too familiar with the Business connector.  I have looked in the log but cannot find what URL it is trying to access.  I also noticed the package in the note is exactly the same size as the old one and the files included in the package are all modified in 2006. This implies to me that nothing was changed between the old package we had and the new one. I have raised this issue with SAP but have got no response yet.
    Any suggestions on how to investigate this connection refused issue?
    Thanks in advance
    Shamshudin

    I never found and anwser to this problem, I was forced to create an webclient and exchange an XML file. Which also only worked correctly if the content-type was equal to:
    ContentType = "application/x-sap.rfc; charset=UTF-8";
    Hope this helps someone.
    Mensaje editado por:
            Fabricio Martinez

  • Load balance business connectors

    Hi experts,
    We have 4 business connectors 4.7 version running on 5 different servers, Currently we are facing the problem of frequent restart on all of them. I would like to know is there any way we can load balance so that new Idoc processing request will go to the least used server. Also would like to know if increase in number of IDoc in flow will affect the performance of the business connectors.
    Regards,
    Suresh

    Hi,
    Please check the below from this article.
    https://social.technet.microsoft.com/Forums/exchange/en-US/749e64d6-9924-4150-bac0-ce4174896fb6/relaying-using-load-balancer?forum=exchange2010
    For those who still monitor this thread,
    The issue here is that the HLB is not configured to Use Source IP.  In the Netscaler world, this is configured on a device or load balancer level and is referred to as USIP.  (Use Source IP)  If Source IP is not configured, the HLB will pass
    the traffic to Exchange using the HLB's interface.  You can configure this IP as an allowed IP address on your relay connector, but this is a big security risk as previously stated because all traffic that is routed through the HLB has rights to relay.
    Concerning the network guy in PeterN22's post, open connections can be a problem and can cause port saturation if you are using an (*) as a wildcard on your RPC load balancing service.  I have had much better luck, across all my load balanced deployments
    (Citrix, Kemp, Cisco, etc.), when I use static port assignments on all load balanced services.  For example:
    SMTP - 25
    RPC - 59532
    OAB - 59533
    HTTPS - 443
    POP - 110
    etc.
    Exchange 2013 load balancing is now stateless and doesn't rely on Source IP, but this same issue with SMTP will occur if Source IP is not used.  I know this is a recap of some of the other posts, but hopefully the additional information is helpful for
    someone who may come across this post.

  • Data loading issue from BW Production to BW Sandbox

    Hello Guys,
           I am trying to load data from one info cube (Production) to another info cube (Sendbox) applying update rules for prototype model. I am not getting any error in monitoring window for Info Package. But what I see is '0 from 0 records' for long time. I have tested connection between two systems that looks O.K. There is data in Production Cube. This is first time I am loading data between two BW systems. I am not sure what could be wrong. Can some one please help me ASAP? Thanks a lot.
                 Export data source for that cube in production is created.
    Kate

    Hi Kate,
    The first thing you might want to check is the status of the extractor job in your Production system. The job name will be same as the request name BI_REQU*. So, in SM37 of Production system check for the extractor job <request number>  and check the status of the job. If it is running, it means that ur extraction is running still and you can wait for some more time or monitor the job closely in SM50 regarding it's progress.
    If it is in cancelled state, you need to check the job log or any short dumps for the error message.
    Regards,
    Sree

  • Load balancing for Business Package iviews

    Hello Gurus,
       we have installed SRM Business packages on our Portal system and accessing the SRM which has 2 application servers.How can we make the iviews to access any one of the application server as the link to ITS in iviews is static.What is the easiest and best approach to get them load balanced using Business Package iviews.
    Regards!

    Dear G,
    As I see your back-end system has 2 app servers... to cofigure the portal iViews to use both app servers you need to define that in the portal system object that is defined to connect to the backend system... You should look if the system object you use for connecting to srm is of the type: "SAP_R3_LoadBalancing"
    See also: http://help.sap.com/saphelp_nw70/helpdata/EN/1f/bddf3d48b05d5ae10000000a11405a/frameset.htm
    In addition because you are talking about ITS you could configure a WebDispatcher in front of your Backend SRM system...
    Good Luck,
    Benjamin Houttuin

  • Importing wmEDI Package in Business Connector

    Hi,
    Could anyone please tell me how to import wmEDI Package in Business Connector and where it is available?

    Hi,
      You will find the relevant informations in www.sapgenie.com and in sapnet.
    regards
    Aveek

  • Transport business connector service.......Urgent

    Hi Experts,
    The scenario is i am sending IDOC from SAP to SQL and SQL sends data for confirmation of Purchase order in SAP.
    For this i have 2 services in business connector. Things are working fine and i am at the stage of transporting the object to PRD.
    The problem is, I used an existing Package to create these 2 services.and for these services i created a

    HI,
    See the below links
    WAS - Business Connector
    business connector documentation
    SAP Business Connector
    Business connector
    Will Business Connector 4.6 be affected by new  Daylight savings changes
    Business connector
    More info on XI can be found at https://service.sap.com/xi
    and webAS on http://help.sap.com/saphelp_nw04/helpdata/en/f3/e20f3adfd0a706e10000000a114084/frameset.htm
    Check this also-
    http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/1bd5c2a85b11d6b28500508b5d5211/frameset.htm
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b4f3755a-0401-0010-b6b3-9b65bb7d4503
    Regards
    Chilla

  • Sap_ebp Package for Business Connector 4.7

    Hello together,
    can anybody tell me, where I can find the Sap_ebp Package for Business Connector 4.7 and SRM 4.0?!
    I have tried it with following Link
    http://service.sap.com/ocs-download
    but I could not find it there.
    BR
    Jutta

    Hi Jutta,
    it used to be here:
    http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000417060&
    but remember:
    "For SRM 4.0 (SRM SERVER 5.0), SAP does not recommend that you use the Business Connectors in connection with Supplier Relationship Management."
    quote from SAP note 856351
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • SAP Business Connector 4.8 and Webmethods EDI Package WmEDI

    Hello,
    we want to upgrade our SAP Business Connector to 4.8 and need to install the EDI package provided by Webmethods earlier.
    We now figured out, that the EDI package is not provided anymore for download in the SAP Service Marketplace.
    Any idea, how to get the EDI package (WmEDI)?
    Is it not free anymore?
    Kind Regards
    Tanja

    Hello Tanja,
    Go through these discussions..
    http://www.wmusers.com/forum/thread6212.html
    http://www.wmusers.com/forum/showthread.php?t=13377
    Thanks,
    Satya Kumar

  • 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 is going down frequently ....

    Hi,
    we are running business connector 4.7 and it was suddenly going something wrong, we did bounced business connector atleast 4 times in last 2 days. we are having issues when the outboundprocess is begin and it is not doing everytime but suddenly. we are unable to figure out anything from error logs as they are not really helpful.
    Please someone let us know ASAP as it is our production and we are in hurry to fixed it.
    Thanks,
    Chander

    Hi ravi,
    I am attaching Audit log and Server log.
    can u send me your email ID so that I can send you all log files.
    In Audit Log
    2007-06-14 06:19:23 CDT 2245x1tu5HhB13ky90DEralHij2G4xI=555587 3388474 pub.sap.idoc:transformHierarchyToFlat begin
    2007-06-14 06:19:24 CDT 2245x1tu5HhB13ky90DEralHij2G4xI=555587 3388474 pub.sap.idoc:transformHierarchyToFlat ok
    2007-06-14 06:19:24 CDT 2245x1tu5HhB13ky90DEralHij2G4xI=555587 3388474 pub.sap.transport.ALE:OutboundProcess begin
    2007-06-14 08:08:05 CDT -( Start )-
    2007-06-14 08:11:36 CDT Administrator 3675872 wm.server.event:startEventAgentPort begin
    2007-06-14 08:11:36 CDT Administrator 3675872 wm.server.event:startEventAgentPort ok
    Server log
    000000  -
      2007-06-14 00:03:03 CDT
    000000  [B2BSERV.0025.0001] Business Connector Server 4.7 Build 999 + CoreFix 7
    000001  [B2BSERV.0025.0006] License Manager started
    000002  [B2BSERV.0025.0008] State Manager started
    000003  [B2BSERV.0025.0010] Service Manager started
    000004  [B2BSERV.0025.0012] Cache Manager started
    000005  [B2BSERV.0025.0009] WIDL Service Manager started
    000006  [B2BSERV.0025.0004] Flow Service Manager started
    000007  [B2BSERV.0025.0002] Package Manager started
    000008  [B2BSERV.0025.0011] Package Replicator Manager started
    000009  [B2BSERV.0028.0001] Loading packages
    00000A  [B2BSERV.0028.0005] Loading WmRoot package
    00000B  [B2BSERV.0028.0005] Loading WmDB package
    00000C  [B2BSERV.0028.0005] Loading WmPublic package
    00000D  [B2BSERV.0028.0005] Loading WmSamples package
    00000E  [B2BSERV.0028.0005] Loading WmPartners package
    00000F  [B2BSERV.0028.0005] Loading SAP package
    000010  [B2BSERV.0028.0005] Loading XTNRepair package
    000011  [B2BSERV.0028.0005] Loading KwikTag package
    000012  [B2BSERV.0028.0005] Loading Default package
    000013  [B2BSERV.0028.0005] Loading Production package
    000014  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.event:startEventAgentPort)
    000015  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.email:init)
    000016  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.ftp:init)
    000017  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.http:init)
    000018  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.https:init)
    000019  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.smime:init)
    00001A  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.sock:init)
    00001B  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.sslsock:init)
    00001C  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.ns:syncToNamespace)
    00001D  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.remote:init)
    00001E  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.schedule:init)
    00001F  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.security.revInvoke:init)
    000020  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.tx:init)
    000021  [B2BCORE.0063.0011] Start
    000022  [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.soap:init)
    000023  [B2BSERV.0028.0012] WmDB: Startup service (wm.server.db:startup)
    000024  [B2BSERV.0028.0012] WmPublic: Startup service (pub.ldap:init)
    000025  [B2BSERV.0028.0012] WmPartners: Startup service (wm.PartnerMgr.gateway.admin:startup)
    000026  [B2BSERV.0028.0012] SAP: Startup service (sap.admin:startup)
    000027  [B2BSERV.0028.0012] SAP: Startup service (sap.admin.xslt:startup)
    000028  [B2BSERV.0028.0012] SAP: Startup service (sap.transport:ALEinit)
    000029  [B2BSERV.0028.0012] SAP: Startup service (sap.transport:BAPIinit)
    00002A  [B2BSERV.0028.0012] SAP: Startup service (sap.transport:RFCinit)
    00002B  [B2BSERV.0028.0012] SAP: Startup service (sap.transport:XMLinit)
    00002C  [B2BSERV.0028.0012] SAP: Startup service (sap.demo.idoc:registerDemoRoutings)
    00002D  [B2BSERV.0025.0005] Port Manager started
    00002E  [B2BSERV.0025.0013] Cache Sweeper started
    00002F  [B2BSERV.0025.0016] Config File Directory Saved
    000030  [B2BSERV.0014.0002] Initialization complete.
    000031  -
      2007-06-14 08:12:31 CDT

  • JCO Timeout for SAP Business Connector 4.7

    Environment :
      Windows 2000, SAP Business Connector (BC) 4.7
    General Description :
      SAP BC is used to invoke BAPI's in the SAP R/3 system.
    Issue :
      Some BAPI's are taking some time to return response depending on user load. Need to provide a timeout for RFC calls invoked by SAP BC using JCO.
      Following is the entry in the rfc trace log file when BC starts up ...
    000000  -
      2005-05-12 11:07:20 EDT
    000001  [B2B-SAP.0011.0001] [JNI-LAYER] RFC.nativeSetTraceLevel()                with rc = RFC_OK   leave, [SUCCESS]
    000002  [B2B-SAP.0002.0022] Log level set to 10
    000003  [B2B-SAP.0002.0025] Registered SAP package trace with core trace
    000004  [B2B-SAP.0002.0014] Starting SAP services
    000005  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.setProperty(jco.jdsr.comp_name, SAP BC server0023 5555)
    000006  [B2B-SAP.0003.0001] Loading native libraries
    000007  [B2B-SAP.0003.0002] JCO version: 2.1.4 (2004-10-20) sapjcorfc 2.1.4 (2004-10-20)
    000008  [B2B-SAP.0003.0004] jRFCLibrary info: 2.1.4 (2004-10-20)(C:\sapbc47\Server\packages\SAP\code\libs\sapjcorfc.dll)
    000009  [B2B-SAP.0003.0003] RfcLibrary version:
    This RFC library belongs to the SAP R/3 Release *** 640,0,41  *** MT-SL
    Versions of SAP internal libraries:
      dptr:    2
      ni  :   37
      cpic:    3
      rfc :    3
    00000A  [B2B-SAP.0011.0001] MiddlewareRFC.setProperty(jco.middleware.wait_for_request_time, 1)
    00000B  [B2B-SAP.0002.0016] Loaded SAP server configurations
    00000C  [B2B-SAP.0002.0015] SAP services started
    00000D  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setAbapDebug(false), current state false
    00000E  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setTrace(true), current state false
    00000F  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.setAbapDebug(false), current state false
    000010  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setMaxWaitTime(30000)
    000011  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setConnectionTimeout(600000)
    000012  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Pool.setTimeoutCheckPeriod(30000) on pool SERVER-300&USER_RFC&300&EN
    000013  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.PoolManager.addPool:
          name = SERVER-300&USER_RFC&300&EN,
          connection = USER_RFC|300|EN|AS=[11.12.7.296|00|]G0|,
          pool_size = 10,
          max_wait_time = 30000,
          pooled_connection_timeout = 600000,
          timeout_check_period = 30000
    000014  [B2B-SAP.0005.0003] Pool changed: SERVER-300&USER_RFC&300&EN containing 0 connection(s)
    007E72  [B2B-SAP.0006.0001] Executing invoke for ZBAPI_TEST_Service on SERVER-300
    007E73  [B2B-SAP.0011.0001] [JAV-LAYER] JCO.Client.execute (ZBAPI_TEST_Service) on handle [2]
    Questions :
       1) Is there a SAP BC configuration parameter for RFC execution timeout ??
       2) Any other way of enforcing the RFC time out ??
       3) If there is a way to set timeout on JCO.Client.execute method ??
    I really appreciate your help !!

    I have tried changes the connection timeout value but if doesnot affect the time RFC. Following is from SAP BC adapter  guide ..
    Delay (minutes) until an unused connection to a SAP
    System is timed out (default: 5)
    I think I need similar setting as that for RFC connection !!

  • 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

  • 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..

Maybe you are looking for