Business connector java exceptions

Hi,
i am getting the below exceptions in BC server :
java.net.ConnectException: Operation timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at java.net.Socket.<init>(Unknown Source)
at com.wm.net.NetURLConnection.httpConnect(NetURLConnection.java:502)
at com.wm.net.NetURLConnection.connect(NetURLConnection.java:162)
at com.wm.net.HttpURLConnection.getOutputStream(HttpURLConnection.java:419)
at com.wm.net.HttpContext.getOutputStream(HttpContext.java:578)
at com.wm.net.HttpContext.getOutputStream(HttpContext.java:554)
at com.wm.net.HttpContext.post(HttpContext.java:338)
at pub.client.http(client.java:579)
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:466)
at com.wm.app.b2b.server.Service.doInvoke(Service.java:495)
at com.wm.app.b2b.server.Service.doInvoke(Service.java:464)
at com.wm.pkg.sap.rfc.Listener.handleRequest(Listener.java:340)
at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7238)
at com.sap.mw.idoc.jco.JCoIDoc$Server.dispatchRequest(JCoIDoc.java:10268)
at com.wm.pkg.sap.rfc.Listener.dispatchRequest(Listener.java:227)
at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1368)
at com.sap.mw.jco.JCO$Server.listen(JCO.java:6805)
at com.sap.mw.jco.JCO$Server.run(JCO.java:6734)
at com.wm.pkg.sap.rfc.Listener.run(Listener.java:117)
at java.lang.Thread.run(Unknown Source)
also,the error recorded in the audit log is a function module name which has been defined in BC as a function map and the sap system is calling business connector to execute a particular service which is pub:client:http.
inbound mapping has been done and when sap system calls BC to exceute this service,the above exceptions are raised.
need to know the root cause of these exceptions and how they can be rectified.
also,please clarify if the exceptions
at com.wm.net.NetURLConnection.httpConnect(NetURLConnection.java:502)
at com.wm.net.NetURLConnection.connect(NetURLConnection.java:162)
at com.wm.net.HttpURLConnection.getOutputStream(HttpURLConnection.java:419)
are occuring due to incorrect parameters in URL of http service or some other reason.
any help in this regard would be appreciated
thanks.

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

Similar Messages

Business connector exceptions(java)

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

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

JCO exceptions in business connector

hi..
i am getting the below JCO$ABAp exceptions in BC server.
can anyone pls clarify the root cause of these errors and possible solutions as to how they can be eliminated:
com.sap.mw.jco.JCO$AbapException: (126) INVALID_STATUS: INVALID_STATUS
     at com.wm.pkg.sap.rfc.SAPSession.invoke(SAPSession.java:463)
     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)
any inputs would be highly appreciated.
thanks
priya.

hii..
i am not handling sap side as such..just taking care of the business connector side.
i need to know if the resulting jco exceptions are due to services running in bc or sap function module side
thanks

JCO$Exception in business connector

hi,
i am getting the following JCO$exceptions in business connector production server.Also the message said is RFC internal error.I need to know the root cause of these exceptions and how they can be resolved either in business connector side or ABAP side.
2005-11-25 08:29:49 GMT com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
     at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
     at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
     at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
     at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
     at pub.sap.client.createTID(client.java:373)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
     at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
     at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
     at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
     at com.wm.lang.flow.FlowState.step(FlowState.java:430)
     at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
     at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
     at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
     at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
     at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
     at java.lang.Thread.run(Unknown Source)
Any help on this regard would be extremely useful and appreciated.
Thanks
Regards,
Ramya.

hii..
i am not handling sap side as such..just taking care of the business connector side.
i need to know if the resulting jco exceptions are due to services running in bc or sap function module side
thanks

Get Data from SAP over the Business Connector into a Java Programm

Hallo dear community,
i would like to receive data from the sap over the application business connector into a java programm. i work with the german book "SAP Business Connector 4.8 - Administration und Entwicklung".
Now i hand on the routing rule.
[Screenshot|http://h-2.abload.de/img/routingruleuyt9.png]
i don't know what i should configure here for receiving data, which i need for an java programm.
i will be very happy, when somebody got a tip or an source (tutorial) where i can find such a configuration :wink:

I think u r writing BDC for Uploading the data from excel flile to sap. for this is the code I am sending u can use then for Uploading data from excel to sap.
DATA: lv_filename TYPE rlgrap-filename.
FIELD-SYMBOLS : <fs>.
DATA : l_intern TYPE alsmex_tabline OCCURS 0 WITH HEADER LINE.
DATA : l_index TYPE i.
PARAMETERS : startcol TYPE i ,
      startrow TYPE i ,
      endcol TYPE i ,
      endrow TYPE i .
PARAMETERS: p_flnam LIKE rlgrap-filename.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_flnam.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
   program_name        = sy-repid
FIELD_NAME          = ' '
   IMPORTING
     file_name           = p_flnam .
MOVE p_flnam TO lv_filename.
Uploading the flat file from the desktop
START-OF-SELECTION.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
    EXPORTING
      filename                      = lv_filename
      i_begin_col                   = startcol
      i_begin_row                   = startrow
      i_end_col                     = endcol
      i_end_row                     = endrow
    TABLES
      intern                        = l_intern
EXCEPTIONS
INCONSISTENT_PARAMETERS       = 1
UPLOAD_OLE                    = 2
OTHERS                        = 3
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
SORT l_intern BY row col.
LOOP AT l_intern.
    MOVE l_intern-col TO l_index.
    ASSIGN COMPONENT l_index OF STRUCTURE itab TO <fs>.
    MOVE l_intern-value TO <fs>.
    AT END OF row.
      APPEND itab.
      CLEAR itab.
    ENDAT.
ENDLOOP.
I hope it will help u.
Regards
Nayan

Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.boots

When attempting to create a new Account in siebel integrated with OEDQ the following error occurs.
ERROR
Data Quality vendor-specific error: An error occurred when calling function 'sdq_init_connector ()' in connector ": "(-8) Exception!." Detailed error message: Exception thrown by Java: java.lang.UnsatisfiedLinkError: nio (Not found in com.ibm.oti.vm.bootstrap.library.path)(SBL-APS-00118)
STEPS
The issue can be reproduced at will with the following steps:
1) from EDQ director we have imported the EDQ_CDS,EDQ-REFERENCE DATA & EDQ_HISTORICAl DATA packages sucessfully.
2) Created dnd.param file in SIebel server SDQCOnnector folder.
3) Copied the libdnd.so file to siebsrvr lib directory(32 bit)
3) In dnd.param file we have mentioned the javalib file and instllation directory path(<Siebsrvr roo>/dnd/install)
4) Unzipped the EDQ-Siebel Connector files in dnd/install folder
5) Copied the dnd.properties file in dnd/install directory and modified it accordingly to point to installed EDQ instance.
6) Configured the Siebel components for EDQ integration.
7) Realtime EDQ jobs are running.
8) Create a new Account
Env details are
On : 8.2.2.14 [IP2014] version, Client Functionality
EDQ 11.1.1.7.4
IBM JDK 1.7 32 bit
Using Open UI
Any Champ have faced this issue and overcame it please let me know the resolution steps. your help is
Regards
Monoj Dey
9007554589

Hi Monoj,
A few questions:
- What OS is Siebel running on?
- What version of the Siebel connector are you using?
- Which libdnd.so file are you using?
- What's the contents of your dnd.parms file?
thanks,
Nick

Business connector and BAPI ,java code

Guy's
we are having development project based on <b>Business
connector and bapi</b> for sales order creation,we are
going for function module /TECCOM/SALESORDER_SIMULATE
for Availability request ,i am not aware of using business
connector and bapi before,they are going for some java code,now i have to create java code and use this particualr BAPI,pls if somebody already worked on such issue,then help me with some material which will guide
me and help me in finishing this task easily,
<b>mail me at [email protected]</b>

This is a very usefull link:
http://www.henrikfrank.dk/abapexamples/Java/

To run a java service in SAP business connector.

Hi,
I have created one java service in SAP business connector.When i run it, i get the error as " Service 'rfctest:validatedata' is not operational. To run this service, first recompile the Java source."
I have set the "path" variable,still i am getting the same error.
What should i do to solve this problem?

Hello,
when you call a BAPI from an external system via Business Connector, you will send a bXML document to BC (for example via HTTP). Refer to the SapbcSAPAdapterGuide for how to do that in detail, its good explained (see 4-25 and 7-3) there.
The explanation about sender/receiver is not correct. sender and receiver are the logical system names of the SAP backend system and the external system (check in transaction SALE of the SAP system).
Just send such document to BC, it will create the routing rule automatically. Then complete the routing rule (see 7-2) and activate it.
CSY

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

No SAP Option under Adapters in SAP business connector 4.7 Admin page

Hi Experts,
I have installed SAP BC 4.7 (both server and developer) and started the server (installation done with <sid>adm user). The problem I am facing is in configuration. There is no SAP option under Adapters because of which I am unable to configure ABAP stack here. Please help in resolving this.
Below are some logs:
sapqat01:ecqadm 52> java -jar /opt/sapbc47/Server/packages/SAP/code/jars/static/sapjco.jar -stdout
java.lang.ExceptionInInitializerError: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc. Not found in java.library.path [/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/CA/SharedComponents/lib:/usr/sap/ECQ/SYS/exe/run:/opt/sapbc47/Server/packages/SAP/code/jars/static:/oracle/client/10x_64/instantclient:/usr/lib]
        at com.sap.mw.jco.JCO.<clinit>(JCO.java:638)
        at java.lang.J9VMInternals.initializeImpl(Native Method)
        at java.lang.J9VMInternals.initialize(J9VMInternals.java:196)
        at java.lang.Class.forNameImpl(Native Method)
        at java.lang.Class.forName(Class.java:119)
        at com.sap.mw.jco.About.<init>(About.java:33)
        at com.sap.mw.jco.About.main(About.java:98)
SAP Java Connector (JCo)
Copyright (c) 2000-2003 SAP AG. All rights reserved.
Version Information
Java Runtime:
Operating System:    Linux 2.6.18-194.el5 for amd64
Java VM:             1.4.2 IBM Corporation
Java Codepage:       UTF8
Versions:
JCo API:             2.1.0 (2003-04-24)
JCo middleware:      Library not found
JCo library:         Library not found
RFC library:         Library not found
Paths:
JCo classes:         System-defined path
JCo library:         Library not found
RFC library:         System-defined path
Manifest
Manifest-Version: 1.0
Implementation-Version: 20030516 0830
Specification-Title: SAP Java Connector
Specification-Version: 2.1.0 (2003-04-24)
Implementation-Title: com.sap.mw.jco
Main-Class: com.sap.mw.jco.About
Created-By: Ant 1.4.1
Implementation-Vendor-Id: com.sap
Implementation-Vendor: SAP AG, Walldorf
Specification-Vendor: SAP AG, Walldorf
server.log file has the following error:
sapqat01:ecqadm 68> head -200 server.log
000000 [B2BSERV.0025.0001] Business Connector Server 4.7 (Standard Encryption) Build 999
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
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(StringTokenizer.java:280)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:759)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntries(PackageManager.java:713)
        at com.wm.app.b2b.server.PackageManager.processPackageManifest(PackageManager.java:564)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:361)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:327)
        at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:279)
        at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:180)
        at com.wm.app.b2b.server.Server.run(Server.java:183)
00000B [B2BSERV.0028.0005] Loading WmPublic package
00000C [B2BSERV.0028.0026] Warning: Deprecated service type (webtap) in service pub.webtap:getPage in package WmPublic
00000D [B2BSERV.0028.0005] Loading WmPartners package
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(StringTokenizer.java:280)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:759)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntries(PackageManager.java:713)
        at com.wm.app.b2b.server.PackageManager.processPackageManifest(PackageManager.java:564)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:361)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:327)
        at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:279)
        at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:180)
        at com.wm.app.b2b.server.Server.run(Server.java:183)
00000E [B2BSERV.0028.0005] Loading SAP package
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(StringTokenizer.java:280)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:759)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntries(PackageManager.java:713)
        at com.wm.app.b2b.server.PackageManager.processPackageManifest(PackageManager.java:564)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:361)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:327)
        at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:279)
        at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:180)
        at com.wm.app.b2b.server.Server.run(Server.java:183)
00000F [B2BSERV.0028.0005] Loading WmSamples package
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(StringTokenizer.java:280)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:759)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntries(PackageManager.java:713)
        at com.wm.app.b2b.server.PackageManager.processPackageManifest(PackageManager.java:564)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:361)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:327)
        at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:279)
        at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:180)
        at com.wm.app.b2b.server.Server.run(Server.java:183)
000010 [B2BSERV.0028.0005] Loading WmDB package
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(StringTokenizer.java:280)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:759)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntry(PackageManager.java:734)
        at com.wm.app.b2b.server.PackageManager.readAccessEntries(PackageManager.java:713)
        at com.wm.app.b2b.server.PackageManager.processPackageManifest(PackageManager.java:564)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:361)
        at com.wm.app.b2b.server.PackageManager.loadPackage(PackageManager.java:327)
        at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:279)
        at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:180)
        at com.wm.app.b2b.server.Server.run(Server.java:183)
000011 [B2BSERV.0028.0005] Loading Default package
000012 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.event:startEventAgentPort)
000013 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.email:init)
000014 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.ftp:init)
000015 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.http:init)
000016 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.https:init)
000017 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.smime:init)
000018 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.sock:init)
000019 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.net.sslsock:init)
00001A [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.ns:syncToNamespace)
00001B [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.remote:init)
00001C [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.schedule:init)
00001D [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.security.revInvoke:init)
00001E [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.tx:init)
00001F [B2BCORE.0063.0011] Start
000020 [B2BSERV.0028.0012] WmRoot: Startup service (wm.server.soap:init)
000021 [B2BSERV.0028.0012] WmPublic: Startup service (pub.ldap:init)
000022 [B2BSERV.0028.0012] WmPartners: Startup service (wm.PartnerMgr.gateway.admin:startup)
000023 [B2BPCKG.0074.0003] TransactionManager: init (entries=0, freeBlocks=0, maxFree=0, bytes=0, sync=true, file=packages/WmPartners/config/xtn.log)
000024 [B2BPCKG.0073.0005] Admin: WmPartners Startup ok
000025 [B2BSERV.0028.0012] SAP: Startup service (sap.admin:startup)
000026 [B2BSERV.0028.0013] Startup service exited with the following error: java.lang.reflect.InvocationTargetException: JCO.classInitialize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc. Not found in java.library.path [/opt/IBMJava2-amd64-142/jre/bin/j9vm:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin:/opt/IBMJava2-amd64-142/jre/bin/classic:/opt/sapbc47/Server/packages/WmWin32/code/libs:/opt/sapbc47/Server/packages/WmPartners/code/libs:/opt/sapbc47/Server/packages/SAP/code/libs:/opt/sapbc47/Server/lib:/opt/CA/SharedComponents/lib:/usr/sap/ECQ/SYS/exe/run:/oracle/client/10x_64/instantclient:/usr/lib]
000027 [B2BSERV.0028.0012] SAP: Startup service (sap.admin.xslt:startup)
000028 [B2BSERV.0028.0012] SAP: Startup service (sap.transport:ALEinit)
000029 [B2BSERV.0028.0013] Startup service exited with the following error: java.lang.reflect.InvocationTargetException: com.wm.pkg.sap.SAPConfig (initialization failure)
00002A [B2BSERV.0028.0012] SAP: Startup service (sap.transport:BAPIinit)
00002B [B2BSERV.0028.0012] SAP: Startup service (sap.transport:RFCinit)
00002C [B2BSERV.0028.0012] SAP: Startup service (sap.transport:XMLinit)
00002D [B2BSERV.0028.0012] SAP: Startup service (sap.demo.idoc:registerDemoRoutings)
00002E [B2BSERV.0028.0012] WmDB: Startup service (wm.server.db:startup)
00002F [B2BSERV.0025.0005] Port Manager started
000030 [B2BSERV.0025.0013] Cache Sweeper started
000031 [B2BSERV.0025.0016] Config File Directory Saved
000032 [B2BSERV.0014.0002] Initialization complete.
000033 -
2011-10-11 03:20:36 EDT
000034 [B2BSERV.0014.0005] Shutting down server. User requested.
000035 [B2BSERV.0028.0015] SAP: Shutdown service (sap.admin:shutdown)
000036 [B2BSERV.0028.0016] Shutdown service exited with the following error: java.lang.reflect.InvocationTargetException: com.wm.pkg.sap.SAPConfig (initialization failure)
000037 [B2BSERV.0028.0015] WmPartners: Shutdown service (wm.PartnerMgr.gateway.admin:shutdown)
000038 [B2BPCKG.0073.0001] Admin: WmPartners Shutdown
000039 [B2BSERV.0028.0015] WmPublic: Shutdown service (pub.ldap:shutdown)
00003A [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.http:shutdown)
00003B [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.https:shutdown)
00003C [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.ftp:shutdown)
00003D [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.email:shutdown)
00003E [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.tx:shutdown)
00003F [B2BCORE.0063.0013] Shutdown
000040 [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.schedule:shutdown)
000041 [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.remote:shutdown)
000042 [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.sock:shutdown)
000043 [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.net.sslsock:shutdown)
000044 [B2BSERV.0028.0015] WmRoot: Shutdown service (wm.server.security.revInvoke:shutdown)
000045 [B2BSERV.0014.0006] Server shutdown completed.
If anyone knows the solution, then please let me know. Your help is appreciated.
Best Regards,
Vikash Chandra
Edited by: Chandra Vikash on Oct 11, 2011 1:46 PM

Hello gaurav,
I have tried re-installing.
I am able to open the web-admin and also all the links except the ones in the adapters section.
I have checked the installation document, adapter guide for BC 4.8 but i couldnt find anything useful.
I was just wondering if it has got anything to do with the OS.
lemme know if you have come across anything like this.
thanks for the help.
Sreejith

Business Connector hangs

Dear all,
we have a problem with our business connector. It hangs from time to time so that we have to restart the service. Please have a look at the error logs. Are there other logs which could be helpful?
error.log
2009-01-23 00:00:38 GMT+01:00 ---( Start )---
2009-01-23 08:35:50 GMT+01:00 java.lang.NullPointerException
     at com.wm.util.coder.IDataCoderHash.get(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder._encode(IDataBinCoder.java(Compiled Code))
     at com.wm.util.coder.IDataBinCoder.encode(IDataBinCoder.java:193)
     at com.wm.data.IDataUtil.deepClone(IDataUtil.java:373)
     at com.wm.app.b2b.server.ServiceManager.handleError(ServiceManager.java:1155)
     at com.wm.app.b2b.server.ServiceManager.processError(ServiceManager.java:985)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:740)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:503)
     at com.wm.app.b2b.server.HTTPInvokeHandler.process(HTTPInvokeHandler.java:168)
     at com.wm.app.b2b.server.HTTPDispatch.run(HTTPDispatch.java:446)
     at com.wm.util.pool.PooledThread.run(PooledThread.java:109)
     at java.lang.Thread.run(Thread.java:498)
2009-01-23 09:15:13 GMT+01:00 ---( Start )---
2009-01-23 13:42:01 GMT+01:00 ---( Start )---
error.log from yesterday
2009-01-22 00:00:00 GMT+01:00 ---( Start )---
2009-01-22 16:54:10 GMT+01:00 ---( Start )---
Our BC v4.6 is running on a Win2000 Server.
Thanks in advance
Edited by: Kilian on Jan 23, 2009 3:12 PM

That looks very strange. Do you have the lastest service pack and core fix applied for 4.6 ? If not, I suggest to do that. If yes, normally you would open an OSS-Call. The problem is, BC 4.6 is not supported anymore then I would suggest you update to 4.8 or 4.7
It looks like a BC bug, because it is a null pointer exception inside a BC system method.
CSY

IDOC_ERROR_ILLEGAL_TYPE in business connector 4.7

Hi,
IDOCS are being sent from sap system to Business connector and conversion to xml is done through bc services
I am getting the following exceptions in business connector production server.I need to know the rootcauses of these exceptions and how they can be resolved
2005-11-25 08:15:40 GMT com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
     at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
     at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
     at pub.sap.client.sendIDoc(client.java:356)
     at java.lang.reflect.Method.invoke(Native Method)
     at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
     at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
     at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
     at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
     at com.wm.lang.flow.FlowState.step(FlowState.java:430)
     at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
     at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
     at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
     at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
     at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
     at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
     at java.lang.Thread.run(Unknown Source)
Regards,
priya.

I am with the same problem and it is apparently caused because the xml file is without encoding,

Business Connector related question

When I am in Business Connector and trying to right click on Trident package to Unlock it so I cab modify it and it gives me the following error:
Java.lang.NullPointer.Exception
When I click on more details I get Server Error occurred
Any ideas what is missing
or what can be done

Hi Chander,
I think all you need to do is the following.
1) Logon to the new development bussiness connector server via the administrative UI
2) From the admin screen on the left tab click under Packages -> Publishing
3) You will be taken to a screen the has available releases ...click on Add Subscribers
4) you window should have the following path Packages>Publishing>Add Subscriber
5) Choose a package. enter the following:
    Host Name: ( your production bus. connector server ip
    Host Port : ( your production bus. conn. server port ( default = 5555 )
    Transport : HTTP
    Remote user name: (your production bus conn user name )
    remote pw:              ( your production bus conn pw )
6) Click on add subscriber ( provided you have entered the correct un/pw and have acces to the server..you will get message that server is now subscriber to package
7) Click on return to publishing ( path should read Packages>publishing
8) Click on create release
9) under the package you set as a subscriber to production click on create release
10) enter package release information - click on create release at bottom of screen
11) return to publishing - path should read Packages>Publishing
12) you should now have a link send release to the right of your package
13) click on send release - from next screen click on your subscriber (production bus conn ).
thats it...

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 idoc error

hi,
i am getting these errors continously in bc server after restart of sap due to which there is data loss in the inbound messages to sap.outbound messages were processed every time sap was started.the errors are as follows:
com.sap.mw.idoc.IDoc$Exception: (3) IDOC_ERROR_ILLEGAL_TYPE: The document does not correspond to the associated repository.
at com.sap.mw.idoc.jco.JCoIDoc$JCoDocumentList.add(JCoIDoc.java:3095)
at com.wm.pkg.sap.rfc.SAPSession.sendIDoc(SAPSession.java:671)
at pub.sap.client.sendIDoc(client.java:356)
at java.lang.reflect.Method.invoke(Native Method)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
at com.wm.lang.flow.FlowState.step(FlowState.java:430)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
at java.lang.Thread.run(Unknown Source)
and am also getting rfc error as follows:
com.sap.mw.jco.JCO$Exception: (108) RFC_ERROR_INTERNAL: internal error
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeCreateTID(Native Method)
at com.sap.mw.jco.rfc.MiddlewareRFC$Client.createTID(MiddlewareRFC.java:1246)
at com.sap.mw.jco.JCO$Client.createTID(JCO.java:3903)
at com.wm.pkg.sap.rfc.SAPSession.createTID(SAPSession.java:768)
at pub.sap.client.createTID(client.java:373)
at java.lang.reflect.Method.invoke(Native Method)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:140)
at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:292)
at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:559)
at com.wm.lang.flow.FlowState.step(FlowState.java:430)
at com.wm.lang.flow.FlowState.invoke(FlowState.java:400)
at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1786)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:709)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:496)
at wm.server.net.EmailTransaction$RunService.write(EmailTransaction.java:1375)
at wm.server.net.EmailTransaction$RunService.run(EmailTransaction.java:1218)
at com.wm.util.pool.PooledThread.run(C:/NT/Perforce/basis/4.1.0-terra/module/core/source/com/wm/util/pool/PooledThread.java:103)
at java.lang.Thread.run(Unknown Source) .
please let me know rootcause of these errors and wat can be done to resolve it soon
thanks in advance,
regards,
priya.

Not sure if it will help, but have you tried to flush the structure cache? I think you will have problems if the structure of the IDoc has changed in the R/3 system and the Business Connector is not aware of the change.
BR,
Tony.

Business connector java exceptions

Similar Messages

Maybe you are looking for