Business Connector monitoring in CCMS

How can I enable CCMS monitoring for Business Connecter. Im using 4.7.
/Teddy.

All relevant information is available at https://websmp201.sap-ag.de/sbc-download
Look at information under "CCMS Monitoring Package".
Cheers,
Sanjeev

Similar Messages

CCMS Agent for business Connector 4.7

HI,
I want to installed CCMSR agent on BusinessConnector 4.7 to maintain alerts. is it possible to install on Business Connector as it is not like XI. If anyone got any ideas please let me know.
Thanks,
Chander

I had installed SAPCCMSr on BUSiness Connector, but now I don't know what to monitor on the Business COnnector.
Thanks,
Chander

Sapccmsr register on Business Connector

Hi,
we want to monitor Business Connector 4.7 running on windows. so I download the OScol and sapccms agent and used the SAPNote 704349 used INSTALL WIN.SAR to install OScol and sapccmsr and then when I tried to register sapccmsr
I am having following error
C:\usr\sap\prfclog>sapccmsr.exe -R
Could not open the ICU common library.
   The following files must be in the path described by
   the environment variable "PATH":
   icuuc26.dll, icudt26l.dll, icuin26.dll [nlsui0.c 1405] pid = 1700
Terminating.
   You may set the environment variable NLSUI_7BIT_FALLBACK to run the program
   without the ICU libraries in an emergency mode. [nlsui0.c 1153] pid = 1700
thanks,
chander

Hi Chander,
I found this errror is relatived to Unicode sapccmsr agent.
Try to download the Non-Unicode sapccmsr agent which doesn't need additional
DLL files and setting any system variables.
SAP Note 914721 - CCMS agents and kernels: Patches 2006
Hope this helps,
Dolores

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

Business Process Monitoring with SAPCCMSR Agents

Hi
I have installed a SAPCCMSR Agent in a non-sap system to monitor log files.
This is the configuration about a particularly log file:
LOGFILE_TEMPLATE
DIRECTORY="E:\LOG"
FILENAME="senddata*.txt"
PATTERN_0="error"
VALUE_0=RED
MONITOR_NEWEST_FILES=1
In this folder every day, log are created (with name senddata-DD-MM-YYYY) and I would like to monitor only the last log produced to search for error.
When the agent run, it creates a monitor in rz20 with the name of the current log(for example senddata-08-09-2014).
Tomorrow when a new log will created, the monitor will change its name (for example in senddata-09-09-2014).
I also want use business process monitoring to create a monitor and assign the mte in rz20.
When I choose from a list which monitor assign, it give me the name of the ccms monitor that have the name valid for today(senddata-08-09-2014).
The problem is that tomorrow this MTE will change its name and will invalidate my monitor in bpm.
I tried to insert manually the value in bpm monitor like ...../senddata*/.... to see if dinamically, it will acquire the monitor with the name in rz20.
But this doesn't work.
Anyone have an idea on how monitor this?
Thanks very much & Best regards
Marco

Hi Mark,
When the agent run, it creates a monitor in rz20 with the name of the current log(for example senddata-08-09-2014).
"senddata-08-09-2014 " - Is this the name of your log file created on OS level everyday ?
If yes, then why not after every log switch after end of day, a file with name sendata replaces its old content with the contents of current logs ?
This "replacing" is scheduled to run every 5 mins from OS level(cron script) and it picks the name of the file using current date method ?
In this was you will have your monitor with same name.
Regards,
Divyanshu

Forwarding XML/EDI from SAP Business connector to EDI (cloverleaf)

Hello,
We are having issues setting SAP up to work with the business connector and our EDI system - cloverleaf.
For testing, we would like to:
1. Create an idoc in SAP and send it to the Busness Connector.
2. Have the busness connector send the doc via XML to our EDI system cloverleaf.
Currently, I have things setup like so:
SAP/ECC6:
SM59: RFC setup as type T and works fine.
WE20: Partner Type LS:
I have 2 message types setup (in outboard: I have "orders" and in Inbound I have the same).
in WE21: I have a cloverleaf (our EDI system) to run with the RFC destination I setup in SM59.
On the Business connector, I have the following under routing rules:
From SAP to the Business connector:
Sender: 8805
Reciver: 10000000008
Message Type: Orders
ACL Group: none
Package: default
Main Flow Services: wm.PartnerMgr.flows.88605.1000000008:ORDERS
Transport: ALE (R3/IDOC)
SAP destination: RD1 (our sid).
FOR my outgoing to our EDI system cloverleaf:
I am using the sender: * - Not sure if this should be SAP or the BC.
Reciver: * - Our EDI system. our EDI system is listening on port 49001.
Message Type: Orders
Under URL (not sure about this one)
I have http://reg2lxap0725:5555/MessagingSystem/receive/BcAdapter/BC
I am however stummped on how the URL shold look..
Now, when we test the above config... I recive the following results in WE02.
0000000000003024 25 03 Green Light: IDoc Successful Green LS/ /SAPBC ORDERS05 ORDERS Outbox CLOVERLEAF
For some reason, we also have an "inbound" that fails.
0000000000003025 25 56 Red Light: IDoc Has Errors KU/ /0000088605 ORDERS05 ORDERS Inbox SAPRD1
My main question is however around routing...
We are trying to send these to our EDI system which is listening on 49001.
I am not sure how they want us to setup the routing rules to pass this over to the right port..
I have also searched the documentation, and have not found any real step by step guides, so I may be missing a few things..
Any advice to point me to the right direction is greatly appriciated....
Thanks everyone,
Richard

Hello Prateek,
Thank you very much for your answer. The AdapterGuide was really helpfull.
Now the routing rule is associated to the correct Service (that was a the problem). So the rule started to process the XML files from the folder (the XML files disappeared immediately after I corrected the rule).
But now my problem is that on the SAP side there is no inbound IDOCs so it seems the trasmission may failed.
Moreover under "Routing"-->"Transactions" I don't see these entries with the the current date.
Our routing rule is simple: "wildcard" "wildcard" "wildcard" "ALE (R/3 IDOC)"--><OUR SAP SYSTEM>
The SAP connection is working as I can test under "SAP..." menu.
Is there any other way to monitor what had happened with these XML files? I'm sure the BC processed as the files are gone, but there is no IDOC in the destination SAP...
Thanks a lot!

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

SAP Business Connector MIME Services to SAP XI Transition

Today we are using the built in MIME services in Business Connector (pub.mime) to format a MIME message, and are then using https to post it to an external business partner by placing the data into the "mimeStream".
Is there a way to perform this same functionality in SAP XI?
Thanks
Peter

Hello Prateek,
Thank you very much for your answer. The AdapterGuide was really helpfull.
Now the routing rule is associated to the correct Service (that was a the problem). So the rule started to process the XML files from the folder (the XML files disappeared immediately after I corrected the rule).
But now my problem is that on the SAP side there is no inbound IDOCs so it seems the trasmission may failed.
Moreover under "Routing"-->"Transactions" I don't see these entries with the the current date.
Our routing rule is simple: "wildcard" "wildcard" "wildcard" "ALE (R/3 IDOC)"--><OUR SAP SYSTEM>
The SAP connection is working as I can test under "SAP..." menu.
Is there any other way to monitor what had happened with these XML files? I'm sure the BC processed as the files are gone, but there is no IDOC in the destination SAP...
Thanks a lot!

Business Connector 4.7

Hi,
I am SRM Consultant and not so specialized with XI or Business Connector.
I am working with a customer on SRM 4.0 / CCM 2.0 / Business Connector 4.7 ( standalone scenario ).
We need to have "contract catalogs" in our system ( CCM 2.0 )
So it is important that our contract data in SRM 4.0 will be changed into XML and send to CCM 2.0 Catalog.
This should be done by Business Connector 4.7
I know, that this works with XI - because there appears a flag " Distribute to Catalog" in SRM 4.0.
But how could this work with Business Connector?!
Would be glad, if someone could give me a hint.
Thanks and Regards,
J.H.

Hi,
I know that Business Connector is antiquated - but the customer works with that.
XI seems to be the future - but it is expensive too.
So - I´ve to find out how it works.
I think I will try to find an BAPI, which mapps the data into XML and send it to BC.
Can anybody tell me what is a "BAPI Driver". I found some of this and they all call up the Business Connector.
Best Regards
J.H.

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

PI 7 to SAP Business Connector Connectivity

Dear Gurus,
I have to connect our ECC 6.0 System to another ECC 6.0 System using B2B scenario. For B2B purposes we are using PI 7 while the other party is using SAP Business Connector (SAP BC) as it's front-end-tool for ERP-to-ERP connectivity. I am a Basis Consultant and I have been given the task of doing this connectivity. I have never worked on any business connector. Can anyone guide me in this? We do not have any PI Consultant
Also advice what infrastructure will be needed to complete this connectivity
Request you all gurus to kindly advise asap
Best Regards

Well, a PI consultant would be a better choice as you will have to learn some basics before you can implement your project. PI is not an easy system as business connector and it requires deeper skills and expertise on the tool, but with some effort, certainly you can do it yourself.
I do not have any experience on the administration of a dispatcher, so I cannot guide you on that subject. But after achieving the connectivity between the two dispatchers, the rest is the PI development task.
It seems that your scenario is not really a hard one. Play around with the tools(in PI) and try sample scenarios to get used to it. Here are some for your convenience:
And the PI (formerly called XI) library that covers almost everything is here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
With the help of the documentation and the sample scenario blogs, you will be able to develop your scenario. But gathering the required skill will take about a month or so, depending on your performance.
After learning the basics, you also need to work on monitoring, alert definitions, going live pratice etc. also which you can also find examples in the blogs. Furthermore, if the messages exchanged are to be changed before reaching the ERP on the PI side, you will also need some mapping practice. Here are two blogs which will teach you graphical mapping in PI:
/people/sravya.talanki2/blog/2005/08/16/message-mapping-simplified--part-i
/people/sravya.talanki2/blog/2005/12/08/message-mapping-simplified-150-part-ii
A B2B scenario can be partly auto-configured after definition of relevant integration scenario in the Integration Builder so it might be a good idea to learn it. I'm assuming you don't need any business processes(which automates A2A and B2B processes, for example a full order-to-cash scenario involving many systems and communications with business logic), so you will mostly need configuration instead of development. You also won't need any ABAP or Java skills in your case.
The content on SDN about PI is pretty rich so I don't think you will be short on examples and instructions. Just search when you need something, almost every aspect is covered by now.
Hope these are useful, feel free to ask anything you may need.
Regards,
Gökhan

SAP Business Connector send XML to SAP

Hello,
There is a BC which should read XML files from a specified folder and send them to SAP via RFC (in IDOC format).
The conection works between BC and SAP fine, gateways are registered and RFC destination has been maintained and tested in SAP.
How/where can I assign the "package" (which contains the folder with XMLs) with the SAP system (it is configured under "Adapters"-->"SAP ..." with correct listeners).
Is the assignment the "Routing rules" or the "Map"?
When should Business Connector start to read the specified folder? Does it start according to "scheduling tasks"?
Where can I monitor the procedures?
Thanks in advance!
Terence

Hello Prateek,
Thank you very much for your answer. The AdapterGuide was really helpfull.
Now the routing rule is associated to the correct Service (that was a the problem). So the rule started to process the XML files from the folder (the XML files disappeared immediately after I corrected the rule).
But now my problem is that on the SAP side there is no inbound IDOCs so it seems the trasmission may failed.
Moreover under "Routing"-->"Transactions" I don't see these entries with the the current date.
Our routing rule is simple: "wildcard" "wildcard" "wildcard" "ALE (R/3 IDOC)"--><OUR SAP SYSTEM>
The SAP connection is working as I can test under "SAP..." menu.
Is there any other way to monitor what had happened with these XML files? I'm sure the BC processed as the files are gone, but there is no IDOC in the destination SAP...
Thanks a lot!

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

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.

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 monitoring in CCMS

Similar Messages

Maybe you are looking for