ABAP to Java - JCo error

I followed all the instructions in Gregor's blog: /people/gregor.wolf3/blog/2004/08/26/setup-and-test-sap-java-connector-outbound-connection
This is based on the Example5.java that comes bundled with JCo software. I was able to start the server, I was able to successfully test my RFC destination, but when I actually run by ABAP program the return error is:
JCO.Server could not find server function 'JCOSERVER01'
I am running the java code on my local machine on eclipse. And in the console this is what I get after the call from the ABAP program:
Server JCOSERVER01 changed state from [ STOPPED ] to [ STARTED ]
Server JCOSERVER02 changed state from [ STOPPED ] to [ STARTED ]
Server JCOSERVER02 changed state from [ STARTED ] to [ STARTED LISTENING ]
Server JCOSERVER01 changed state from [ STARTED ] to [ STARTED LISTENING ]
Server JCOSERVER01 changed state from [ STARTED LISTENING ] to [ STARTED LISTENING BUSY ]
Exception in server JCOSERVER01:
com.sap.mw.jco.JCO$Exception: (120) JCO_: JCO.Server could not find server function 'JCOSERVER01'
com.sap.mw.jco.JCO$Exception: (120) JCO_: JCO.Server could not find server function 'JCOSERVER01'
     at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
     at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(MiddlewareRFC.java:1395)
     at com.sap.mw.jco.JCO$Server.listen(JCO.java:7067)
     at com.sap.mw.jco.JCO$Server.run(JCO.java:6996)
     at java.lang.Thread.run(Thread.java:534)
Server JCOSERVER01 changed state from [ STARTED LISTENING BUSY ] to [ STARTED LISTENING ]
Server JCOSERVER01 changed state from [ STARTED LISTENING ] to [ STARTED ]
Server JCOSERVER01 changed state from [ STARTED ] to [ STOPPED ]
Server JCOSERVER01 changed state from [ STOPPED ] to [ STARTED ]
Server JCOSERVER01 changed state from [ STARTED ] to [ STARTED LISTENING ]
Server JCOSERVER01 changed state from [ STARTED LISTENING ] to [ STARTED LISTENING BUSY ]
Pls help!
Thanks in adv
gs

Hi Prashil,
I am getting the error when I am testing using the test program from the blog.
Here it is:
DATA: REQUTEXT LIKE SY-LISEL,
      RESPTEXT LIKE SY-LISEL,
      ECHOTEXT LIKE SY-LISEL.
DATA: RFCDEST like rfcdes-rfcdest VALUE 'NONE'.
DATA: RFC_MESS(128).
REQUTEXT = 'HELLO WORLD'.
RFCDEST = 'Z_TEST_ABAP_TO_JCO'. "corresponds to the destination name defined in the SM59
CALL FUNCTION 'JCOSERVER01'
   DESTINATION RFCDEST
   EXPORTING
     REQUTEXT = REQUTEXT
   IMPORTING
     RESPTEXT = RESPTEXT
     ECHOTEXT = ECHOTEXT
   EXCEPTIONS
     SYSTEM_FAILURE        = 1 MESSAGE RFC_MESS
     COMMUNICATION_FAILURE = 2 MESSAGE RFC_MESS.
IF SY-SUBRC NE 0.
    WRITE: / 'Call STFC_CONNECTION         SY-SUBRC = ', SY-SUBRC.
    WRITE: / RFC_MESS.
ENDIF.
Also I have created and successfully tested the RFC destination: "Z_TEST_ABAP_TO_JCO" with the program id: "JCOSERVER01".
And "JCOSERVER01" is the name of one of the two servers started in the java program Example5.java.
Thanks
gs

Similar Messages

Java JCo Error

I have a J2EE servlet I wrote for use in EP 7.0 using JCO.createClient methods. The code works but every now and then there seems to be a connection issue with the backend R/3 system. This issue also appears to be occuring randomly and no speific event seems to cause the error. Has anyone run into something like this before, and can offer advice?

Hi Eric
Try to switch on SAP JCO trace, that will probably give you more information.
You can see how to do it in SAP Note 628962
Hope that helps
Peter

Java portal to bw hana sp08 JCO error

Dear Team
I am facing an issue after BW Hana migration.
Senario:1(BEFORE MIGRATION)
ORACLE DB/ BW NW 7.3+ JAVA PORTAL 7.01, EACH ON SINGLE STACK
HOSTNAME: xxxxx
DOMAIN: xxx.LOCAL
DATABASE: ORACLE11G
SYSTEM : ABAP + JAVA SEPARATE STACKS
PLATFORM: NW 7.3
JAVA 7.01
Senario 2
( MIGRATION ENTIRE ABAP STACK)
HDB/ BW NW 7.3
HOSTNAME: YYYYY
DOMAIN: xxxx.LOCAL
DATABASE: HDB SP08
SYSTEM : ABAP
PLATFORM: NW 7.3
Migrated only Abap stack and Java portal still runs with older database(oracle)in Older system(Xxxxx). I did the re-deployment on java portal with new HANA db configuration and it was success but.
When connecting Jco it is throwing error
Test Connection with Connector
Test Details:
The test consists of the following steps:
1. Retrieve the default alias of the system
2. Check the connection to the backend application using the connector defined in this system object
Results
Retrieval of default alias successful
Connection failed. Make sure that Single Sign-On is configured correctly
only the issue with Jco rest of all connectivity working fine, anybody face the same issue ?

Hi,
Issue got resolved .
OOPS N BUGS !!!: Java portal to bw hana JCO error / Connection failed. Make sure that Single Sign-On is configured corre…
Thanks
Yoonus

Short dump Error during VM container communication between ABAP and JAVA.

Hello All,
Can anybody please help with resolving the following issue:
Short dump is displayed, when I try to insert CRM product (type: material) in the document (opportunity). This CRM product was created in CRM directly.
When I try to insert ECC migrated material, everything works fine.
Here is the details of dump:
Short text
    Error during VM container communication between ABAP and JAVA
Information on where terminated
    Termination occurred in the ABAP program "SAPLPRC_INT" - in "GET_PRICING_PROCEDURE_INFO".
    The main program was "SAPMHTTP ". In the source code you have the termination point in line 100 of the (Include) program "LPRC_INTF35".
Thank you!

hi Willie,
     this is the dump, and i have used the t-code sm52 . the VMC is not active.
|Short Text                                                                                        |
|    Error during VM Container communication between ABAP and JAVA.                                |
|What happened?                                                                                    |
|    The current program had to be terminated because of an                                        |
|    error when installing the R/3 System.                                                         |
|    Error in the RFC layer.                                                                       |
|What can you do?                                                                                  |
|    Note which actions and entries caused the error to occur.                                     |
|                                                                                                  |
|    Consult your SAP administrator.                                                               |
|                                                                                                  |
|    Using transaction ST22 for ABAP dump analysis, you can view, manage,                          |
|    and retain termination messages for longer periods.                                           |
|Error analysis                                                                                    |
|    An error has occurred in the RFC layer during communication between                           |
|    JAVA and the ABAP stack. This prevents data from being passed correctly                       |
|    between the two stacks.                                                                       |
|                                                                                                  |
|    Message    = TH_VMC_SERV_NOT_ACTIVE                                                           |
|    Return code = -1007                                                                           |
|    Pointer    = "000007DD348F6138"                                                               |
|How to correct the error                                                                          |
|    Check whether the VMC is active on your application server. To do this,                       |
|    run transaction SM52. If the VMC is not active, contact your SAP                              |
|    administrator.                                                                                |
Regards
Charles

Error during VM container communication between ABAP and JAVA

Hello,
While creation of SC, I am getting error "Error during VM container communication between ABAP and JAVA"
Based on earlier responses in this forum, I checked following activity.
1. T Code - BBP_CND_CHECK_CUST
Result - IPC Pricing is Active and IPC is now running in VMC
2. Run Report - RSVMCRT_HEALTH_CHECK
Result - The Java component is deactivated
3. As per OSS note 854170, Profile parameters were existed as below
a) vmcj/enable - on
b) vmcj/option/maxJavaHeap = 200M
So, How to get Java component activated?
Thanks,
Rahul Mandale

Thanks Markus,
For SM53, I am getting resulets as " Java is not active on this application server - Message no. SVMCRT011"
Can you suggest, what I need to do for it? I can't use SRM Shopping cart because of it. thanks in advance, Rahul
and dev_w0 trace ....
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL           1
ACTIVE TRACE COMPONENTS      all, MJ
B
B Wed Aug 31 15:45:40 2011
B create_con (con_name=R/3)
B Loading DB library 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' ...
B Library 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' loaded
B Version of 'D:\usr\sap\CUS\DVEBMGS04\exe\dboraslib.dll' is "700.08", patchlevel (0.46)
B New connection 0 created
M sysno      04
M sid        CUS
M systemid   560 (PC with Windows NT)
M relno      7000
M patchlevel 0
M patchno    52
M intno      20050900
M make:      multithreaded, Unicode, optimized
M pid        456
M
M kernel runs with dp version 210000(ext=109000) (@(#) DPLIB-INT-VERSION-210000-UC)
M length of sys_adm_ext is 572 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 456) [dpxxdisp.c   1293]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm)          18304     (1408)
M DpShMCreate: sizeof(tm_adm)          3954072     (19672)
M DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
M DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
M DpShMCreate: sizeof(comm_adm)          528064     (1048)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)          0     (72)
M DpShMCreate: sizeof(vmc_adm)          0     (1452)
M DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
M DpShMCreate: sizeof(gw_adm)     48
M DpShMCreate: SHM_DP_ADM_KEY          (addr: 05C00040, size: 4613144)
M DpShMCreate: allocated sys_adm at 05C00040
M DpShMCreate: allocated wp_adm at 05C01E28
M DpShMCreate: allocated tm_adm_list at 05C065A8
M DpShMCreate: allocated tm_adm at 05C065D8
M DpShMCreate: allocated wp_ca_adm at 05FCBB70
M DpShMCreate: allocated appc_ca_adm at 05FD1930
M DpShMCreate: allocated comm_adm at 05FD3870
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 06054730
M DpShMCreate: allocated gw_adm at 06054770
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 060547A0
M DpShMCreate: allocated wall_adm at 060547A8
X EmInit: MmSetImplementation( 2 ).
X MM diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Wed Aug 31 15:45:41 2011
M ThInit: running on host crmsys
M
M Wed Aug 31 15:45:42 2011
M calling db_connect ...
C Prepending D:\usr\sap\CUS\DVEBMGS04\exe to Path.
C
C Wed Aug 31 15:45:47 2011
C Client NLS settings: AMERICAN_AMERICA.UTF8
C Logon as OPS$-user to get SAPSR3's password
C Connecting as /@CRM on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 UTF8                                                      1   0619F158   061A46F4   061A3F7C
C Attaching to DB Server CRM (con_hdl=0,svchp=061A3EC8,svrhp=061B5794)
C Starting user session (con_hdl=0,svchp=061A3EC8,srvhp=061B5794,usrhp=061CA558)
C
C Wed Aug 31 15:45:48 2011
C Now '/@CRM' is connected (con_hdl 0, nls_hdl 0).
C Got SAPSR3's password from OPS$-user
C Disconnecting from connection 0 ...
C Closing user session (con_hdl=0,svchp=061A3EC8,usrhp=061CA558)
C Now I'm disconnected from ORACLE
C Connecting as SAPSR3/<pwd>@CRM on connection 0 (nls_hdl 0) ... (dbsl 700 240106)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 UTF8                                                      1   0619F158   061A46F4   061A3F7C
C Starting user session (con_hdl=0,svchp=061A3EC8,srvhp=061B5794,usrhp=061CA558)
C Now 'SAPSR3/<pwd>@CRM' is connected (con_hdl 0, nls_hdl 0).
C Database NLS settings: AMERICAN_AMERICA.UTF8
C Database instance CRM is running on CRMSYS with ORACLE version 10.2.0.1.0 since 20110831
B
B Wed Aug 31 15:45:49 2011
B Connection 0 opened (DBSL handle 0)
B Wp Hdl ConName          ConId     ConState     TX PRM RCT TIM MAX OPT Date     Time   DBHost
B 000 000 R/3              000000000 ACTIVE       NO YES NO 000 255 255 20110831 154542 CRMSYS
M db_connect o.k.
M ICT: exclude compression: .zip,.cs,.rar,.arj,.z,.gz,.tar,.lzh,.cab,.hqx,.ace,.jar,.ear,.war,.css,.pdf,.js,.gzip,.uue,.bz2,.iso,.sda,.sar,.gif
I
I Wed Aug 31 15:46:12 2011
I MtxInit: 0 0 0
M SHM_PRES_BUF               (addr: 0A7C0040, size: 4400000)
M SHM_ROLL_AREA          (addr: 788A0040, size: 61440000)
M SHM_PAGING_AREA          (addr: 0AC00040, size: 32768000)
M SHM_ROLL_ADM               (addr: 0CB50040, size: 615040)
M SHM_PAGING_ADM          (addr: 0CBF0040, size: 525344)
M ThCreateNoBuffer          allocated 544152 bytes for 1000 entries at 0CC80040
M ThCreateNoBuffer          index size: 3000 elems
M ThCreateVBAdm          allocated 12160 bytes (50 server) at 0CD10040
X EmInit: MmSetImplementation( 2 ).
X MM diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation flat
X ES initialized.
B db_con_shm_ini: WP_ID = 0, WP_CNT = 13, CON_ID = -1
B dbtbxbuf: Buffer TABL (addr: 10E700C8, size: 30000000, end: 12B0C448)
B dbtbxbuf: Buffer TABLP (addr: 12B100C8, size: 10240000, end: 134D40C8)
B dbexpbuf: Buffer EIBUF (addr: 0FBA00D0, size: 4194304, end: 0FFA00D0)
B dbexpbuf: Buffer ESM   (addr: 134E00D0, size: 4194304, end: 138E00D0)
B dbexpbuf: Buffer CUA   (addr: 138F00D0, size: 3072000, end: 13BDE0D0)
B dbexpbuf: Buffer OTR   (addr: 13BE00D0, size: 4194304, end: 13FE00D0)
M rdisp/reinitialize_code_page -> 0
M icm/accept_remote_trace_level -> 0
M rdisp/no_hooks_for_sqlbreak -> 0
M CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
S
S Wed Aug 31 15:46:15 2011
S *** init spool environment
S initialize debug system
T Stack direction is downwards.
T debug control: prepare exclude for printer trace
T new memory block 1946AA80
S
S Wed Aug 31 15:46:16 2011
S spool kernel/ddic check: Ok
S using table TSP02FX for frontend printing
S 1 spool work process(es) found
S frontend print via spool service enabled
S printer list size is 150
S printer type list size is 50
S queue size (profile)   = 300
S hostspool list size = 3000
S option list size is 30
S      found processing queue enabled
S found spool memory service RSPO-RCLOCKS at 1D6D00A8
S doing lock recovery
S setting server cache root
S found spool memory service RSPO-SERVERCACHE at 1D6D0430
S    using messages for server info
S size of spec char cache entry: 297028 bytes (timeout 100 sec)
S size of open spool request entry: 2132 bytes
S immediate print option for implicitely closed spool requests is disabled
A
A Wed Aug 31 15:46:18 2011
A
A -PXA--
A PXA INITIALIZATION
A PXA: Fragment Size too small: 73 MB, reducing # of fragments
A System page size: 4kb, total admin_size: 5132kb, dir_size: 5076kb.
A Attached to PXA (address 688A0040, size 150000K)
A abap/pxa = shared protect gen_remote
A PXA INITIALIZATION FINISHED
A -PXA--
A
A
A Wed Aug 31 15:46:20 2011
A ABAP ShmAdm attached (addr=57A40000 leng=20955136 end=58E3C000)
A >> Shm MMADM area (addr=57EB5E58 leng=126176 end=57ED4B38)
A >> Shm MMDAT area (addr=57ED5000 leng=16150528 end=58E3C000)
A RFC Destination> destination crmsys_CUS_04 host crmsys system CUS systnr 4 (crmsys_CUS_04)
A
A Wed Aug 31 15:46:21 2011
A RFC Options> H=crmsys,S=04,d=2,
A RFC FRFC> fallback activ but this is not a central instance.
A
A RFC rfc/signon_error_log = -1
A RFC rfc/dump_connection_info = 0
A RFC rfc/dump_client_info = 0
A RFC rfc/cp_convert/ignore_error = 1
A RFC rfc/cp_convert/conversion_char = 23
A RFC rfc/wan_compress/threshold = 251
A RFC rfc/recorder_pcs not set, use defaule value: 2
A RFC rfc/delta_trc_level not set, use default value: 0
A RFC rfc/no_uuid_check not set, use default value: 0
A RFC rfc/bc_ignore_thcmaccp_retcode not set, use default value: 0
A RFC Method> initialize RemObjDriver for ABAP Objects
M ThrCreateShObjects          allocated 13730 bytes at 0FFB0040
N
N Wed Aug 31 15:46:22 2011
N SsfSapSecin: putenv(SECUDIR=D:\usr\sap\CUS\DVEBMGS04\sec): ok
N
N =================================================
N === SSF INITIALIZATION:
N ===...SSF Security Toolkit name SAPSECULIB .
N ===...SSF trace level is 0 .
N ===...SSF library is D:\usr\sap\CUS\DVEBMGS04\exe\sapsecu.dll .
N ===...SSF hash algorithm is SHA1 .
N ===...SSF symmetric encryption algorithm is DES-CBC .
N ===...sucessfully completed.
N =================================================
N
N Wed Aug 31 15:46:23 2011
N MskiInitLogonTicketCacheHandle: Logon Ticket cache pointer retrieved from shared memory.
N MskiInitLogonTicketCacheHandle: Workprocess runs with Logon Ticket cache.
M JrfcVmcRegisterNativesDriver o.k.
W =================================================
W === ipl_Init() called
B    dbtran INFO (init_connection '<DEFAULT>' [ORACLE:700.08]):
B     max_blocking_factor = 15, max_in_blocking_factor      =   5,
B     min_blocking_factor = 10, min_in_blocking_factor      =   5,
B     prefer_union_all    =   0, prefer_join                 =   0,
B     prefer_fix_blocking =   0, prefer_in_itab_opt          =   1,
B     convert AVG         =   0, alias table FUPD            =   0,
B     escape_as_literal   =   1, opt GE LE to BETWEEN        =   0,
B     select *            =0x0f, character encoding          = STD / <none>:-,
B     use_hints           = abap->1, dbif->0x1, upto->2147483647, rule_in->0,
B                           rule_fae->0, concat_fae->0, concat_fae_or->0
W
W Wed Aug 31 15:46:24 2011
W    ITS Plugin: Path dw_gui
W    ITS Plugin: Description ITS Plugin - ITS rendering DLL
W    ITS Plugin: sizeof(SAP_UC) 2
W    ITS Plugin: Release: 700, [7000.0.52.20050900]
W    ITS Plugin: Int.version, [32]
W    ITS Plugin: Feature set: [10]
W    ===... Calling itsp_Init in external dll ===>
W === ipl_Init() returns 0, ITSPE_OK: OK
W =================================================
E Enqueue Info: rdisp/wp_no_enq=1, rdisp/enqname=<empty>, assume crmsys_CUS_04
E Replication is disabled
E EnqCcInitialize: local lock table initialization o.k.
E EnqId_SuppressIpc: local EnqId initialization o.k.
E EnqCcInitialize: local enqueue client init o.k.
B
B Wed Aug 31 15:46:48 2011
B table logging switched off for all clients
M
M Wed Aug 31 15:47:55 2011
M SecAudit(RsauShmInit): WP attached to existing shared memory.
M SecAudit(RsauShmInit): addr of SCSA........... = 05BD0040
M SecAudit(RsauShmInit): addr of RSAUSHM........ = 05BD07A8
M SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = 05BD07E0
M SecAudit(RsauShmInit): addr of RSAUSLOTS...... = 05BD07EC
A
A Wed Aug 31 15:48:44 2011
A RFC FRFC> fallback on the central gateway crmsys sapgw04 activ
B
B Wed Aug 31 15:49:47 2011
B dbmyclu : info : my major identification is 3232288873, minor one 4.
B dbmyclu : info : Time Reference is 1.12.2001 00:00:00h GMT.
B dbmyclu : info : my initial uuid is D98FA690E8AA314D9B69930868792664.
B dbmyclu : info : current optimistic cluster level: 0
B dbmyclu : info : pessimistic reads set to 2.

More complex JCO Server examples (ABAP to Java)

JCo connections:
I found a couple of good documents for connecting from Java to ABAP. Whenever it comes to the other direction (ABAP to Java), information is somehow rare.
I had a look at the examples coming with the JCo lib, however I would like to find some more complex examples. Especially the transfer of larger result sets (obtained on the Java side) is interesting.
Does anybody know something like this? I have tried Google, but somehow always the same few articles showed up.
Any hints?

You can also use the JCO RFC Provider Service of the Web Application Server for your ABAP to Java calls.
The steps involved in that are
1. Configure destination in SM59 in SAP.
2. Create RFC Destination in Visual Admin.
3. Create a stateless session bean with JNDI name as the name of calling function module in SAP.
4. Add a business method public void processFunction(JCO.Funtion fn) which is called by the JCO RFC Provider Service. The name should be 'processFunction'.
5. Set library references in application-j2ee-engine.xml to type weak for the following
    a. com.sap.mw.jco.
    b. com.sap.tc.Logging (if you are using the logging api )
Here is the sample code for the EJB biz method
Business Method.
     public void processFunction(JCO.Function function) {
          try {
               // Get the import parameters for the function module
               JCO.ParameterList importList = function.getImportParameterList();
               logger.infoT("The value sent is" +
               (String)importList.getValue("USER_NAME"));
               // Set the export parameter value for the function module
               JCO.ParameterList export = function.getExportParameterList();
               export.setValue("From EJB", "RETURN");
               function.setExportParameterList(export);
          catch (java.lang.Exception e) {
               e.printStackTrace();

ABAP to Java Connector (JCo)

Hi All,
Currently this is what I have:
ABAP program uses OPEN SQL of course collect information from SAP database, then using NATIVE SQL goes thru DBCON to transfer information directly to another application (Non SAP system) database (not SAP database).
I just dont like this idea anymore since I was reading about the Java Connector.
So what I want to do is...Not sure feasible this is where I need your help on:
Remove all my NATIVE SQL statements, use JCo and rewrite those statements in Java language and communicate to the Non SAP application thru their API (their API is also Java base)
Will reward points.
Tim

hi,
you will find more info on.
http://www.sapgenie.com/faq/jco.htm
http://help.sap.com/saphelp_nw04/helpdata/en/47/80f671ee6e4b41b63c0fe46bd6e4f8/content.htm
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
http://searchsap.techtarget.com/tip/1,289483,sid21_gci854012,00.html
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-64134159551ecde70_glossary/S
for installing JCO zip file...
http://help.sap.com/saphelp_nw04/helpdata/en/47/80f671ee6e4b41b63c0fe46bd6e4f8/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/mysap4/mysap437.htm
You simply have to have a connection with SAP system and then you can call BAPI with which you can read / update the data in the SAP system.
Hope this info proves useful.
Regards,
Richa.

BI setup: WebAS ABAP Setting - Java to ABAP communication problem

Hello,
i've got a problem during intallation of BI in Netweaver 2004s. The Diagnostics & Support Desktop Tool reports errors in WebAS ABAP Settings. These errors are:
- "Web Template Validation failed due Java to ABAP communication problem (return code:ERSBOLAP018)" with the suggested solution "Check Connector Connection of System Object in Portal System Landscape". What does it mean?
- "Call ABAP->Java for function RSWR_RFC_SERVICE_TEST failed for destination <destination>" and "Call ABAP->Java for function RSRD_MAP_TO_PORTAL_USERS failed for destination <destination>" with suggested solution "Check the data of the destination in transaction SM59. Check that the target host is running and has registered a program id in the gateway." Run of transaction SM59 returns no errors.
Further i've take a look in the log 'dev_jrfc.trc' and there i found the errors:
- Exception thrown by application running in JCo Server
java.lang.RuntimeException: Bean RSRD_MAP_TO_PORTAL_USERS not found on host <host>
- Exception thrown by application running in JCo Server
java.lang.RuntimeException: Bean RSWR_RFC_SERVICE_TEST not found on host <host>
- Exception thrown by application running in JCo Server
java.lang.RuntimeException: Bean RSWR_PREEXECUTION_PROXY not found on host <host>
Can these errors be the cause of the WebAS ABAP Setting error displayed in the Diagnostics & Support Desktop Tool? How they can be solved?
Thanks for your help,
Martin

Hello Chetan,
thanks for your response. Maybe i've described my problem not clear enough. There is no problem of installation and usage of support & dektop tool, but of installation of BI. The support & dektop tool indicates the errors described above with no other hints. My questions is, if anybody knows, what is the cause of the errors and what i must do, to install BI correctly.
Cheers,
Martin

Call ABAP from Java

Can any one help me in calling an ABAP program from Java.
The version of SAP with me is 4.7.
Thanks in advance.
Regards ,
Nagaraju Donikena

To call ABAP from Java when I tried doing it from sample code given in help I was getting the following error. Can any one help in this regard.
Exception in thread "main" java.lang.ExceptionInInitializerError: JCO.classIniti
alize(): Could not load middleware layer 'com.sap.mw.jco.rfc.MiddlewareRFC'
JCO.nativeInit(): Could not initialize dynamic link library sapjcorfc [no sapjco
rfc in java.library.path]. java.library.path
        at com.sap.mw.jco.JCO.<clinit>(JCO.java:735)
        at TestConnect.<init>(TestConnect.java:8)
        at TestConnect.main(TestConnect.java:25)

Java system error: Server repository could not create function template

Hi, Our BI person is trying to publish/broadcast a query to the PRODCTION portal, she gets the below error message. I am
attaching the defaulttracelog file
"Java system error: Server repository could not create function template for RSRD_X_PRODUCE_PROXY caused by: com.sap.mw.jco.JCO$Exception: (103)"
<!LOGHEADER[START]/>
<!HELP[Manual modification of the header may cause parsing problem!]/>
<!LOGGINGVERSION[1.5.3.7185 - 630]/>
<!NAME[./log/defaultTrace.trc]/>
<!PATTERN[defaultTrace.trc]/>
<!FORMATTER[com.sap.tc.logging.ListFormatter]/>
<!ENCODING[UTF8]/>
<!FILESET[8, 20, 10485760]/>
<!PREVIOUSFILE[defaultTrace.7.trc]/>
<!NEXTFILE[defaultTrace.9.trc]/>
<!LOGHEADER[END]/>
#1.5 #002264F9350800600000022F000019C000048E9B91EF3AB3#1282698726384#com.sap.security.core.persistence#sap.com/irj#com.sap.security.core.persistence#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#/System/Security/Usermanagement#Java#An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". ##An exception was thrown in the UME/ABAP user management connector that was caused by unavailability of the RFC communication with the backend system: "". #1#Connect to SAP gateway failed
Connect_PM TYPE=A ASHOST=localhost SYSNR=00 GWHOST=localhost GWSERV=sapgw00 PCS=1
LOCATION    CPIC (TCP/IP) on local host with Unicode
ERROR       partner '127.0.0.1:sapgw00' not reached
TIME        Tue Aug 24 21:12:06 201
RELEASE     700
COMPONENT   NI (network interface)
VERSION     38
RC          -10
MODULE      nixxi.cpp
LINE        2823
DETAIL      NiPConnect2
SYSTEM CALL connect
ERRNO       10061
ERRNO TEXT WSAECONNREFUSED: Connection refused
COUNTER     56
#1.5 #002264F93508006000000230000019C000048E9B91EF47C8#1282698726384#com.sap.engine.services.monitor.mbeans.Monitor#sap.com/irj#com.sap.engine.services.monitor.mbeans.Monitor#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!#
#1.5 #002264F93508006000000231000019C000048E9B91EF4CD5#1282698726384#System.err#sap.com/irj#System.err#J2EE_GUEST#0##n/a##4dba6f30af8111df934c002264f93508#SAPEngine_Application_Thread[impl:3]_35##0#0#Error##Plain###com.sap.engine.services.jmx.exception.JmxSecurityException: Caller J2EE_GUEST not authorized, user J2EE_GUEST is not available from user management, reason: com.sap.security.api.NoSuchUserException:USER_AUTH_FAILED: User account for logonid "J2EE_GUEST" not found!
     at com.sap.engine.services.jmx.auth.UmeAuthorization.checkMBeanPermission(UmeAuthorization.java:63)
     at com.sap.engine.services.jmx.JmxServerFrame.checkMBeanPermission(JmxServerFrame.java:98)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.unregisterMBean(MBeanServerSecurityWrapper.java:395)
     at com.sap.engine.services.jmx.ClusterInterceptor.unregisterMBean(ClusterInterceptor.java:1327)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.unregisterMBean(MBeanServerInterceptorChain.java:258)
     at com.sap.engine.services.monitor.mbeans.Monitor.unregister(Monitor.java:106)
     at com.sap.engine.library.monitor.impl0.AbstractMonitorNode.remove(AbstractMonitorNode.java:154)
     at com.sap.engine.library.monitor.impl0.MonitorObjectFactory.uninstallMonitorNode(MonitorObjectFactory.java:483)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:595)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:581)
     at com.sap.engine.services.monitor.install.MonitorInstaller.uninstallMonitors(MonitorInstaller.java:568)
     at com.sap.engine.services.monitor.server.ApplicationLifeCycleImpl.applicationStopped(ApplicationLifeCycleImpl.java:52)
     at com.sap.engine.services.monitor.deployment.MonitorDeploymentContainer.commitStop(MonitorDeploymentContainer.java:630)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commonCommitFinished(StopTransaction.java:244)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitCommon(StopTransaction.java:290)
     at com.sap.engine.services.deploy.server.application.StopTransaction.commitLocal(StopTransaction.java:278)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesLocal(ApplicationTransaction.java:374)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:132)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesLocalAndWait(ParallelAdapter.java:250)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.stopApplicationLocalAndWait(DeployServiceImpl.java:4569)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.stopApplicationLocalAndWait(DeployCommunicatorImpl.java:628)
     at com.sap.portal.prt.sapj2ee.SAPJ2EEPortalRuntime$2.run(SAPJ2EEPortalRuntime.java:602)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.lang.ClassLoader$NativeLibrary.load(Native Method)
     at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1586)
     at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1482)
     at java.lang.Runtime.load0(Runtime.java:737)
     at java.lang.System.load(System.java:811)
     at com.sapportals.wcm.service.fsmount.FSMountService.loadDLL(FSMountService.java:736)
     at com.sapportals.wcm.service.fsmount.FSMountService.<clinit>(FSMountService.java:796)
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:219)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertGS(CmConfigurationProvider.java:637)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.convertServiceConfig(CmConfigurationProvider.java:601)
     at com.sapportals.wcm.repository.runtime.CmConfigurationProvider.readConfiguration(CmConfigurationProvider.java:205)
     at com.sapportals.wcm.crt.CrtSystemImpl.createComponentManager(CrtSystemImpl.java:108)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:202)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)
     at com.sap.engine.services.servlets_jsp.server.runtime.context.WebComponents.addServlet(WebComponents.java:139)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.loadServlets(ApplicationThreadInitializer.java:386)
     at com.sap.engine.services.servlets_jsp.server.container.ApplicationThreadInitializer.run(ApplicationThreadInitializer.java:110)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
#1.5 #002264F93508005C0000042300002CF00004939AAEE9AEB7#1288192475655#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#sap.com/irj#com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager#J2EE_GUEST#0##n/a##c7d00e00e1dc11dfa36d002264f93508#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###setting initial ACL on /reporting_backend/reports/System Administration/CM Store/cm.crawlcontent - com.sap.security.api.NoSuchRoleException: Role with uniqueName system_admin_role not found!
     at com.sap.security.core.imp.RoleFactory.getRoleByUniqueName(RoleFactory.java:1783)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getRoles(RPRepositoryManager.java:1474)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.syncReportResources(RPRepositoryManager.java:1334)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.initBackend(RPRepositoryManager.java:489)
     at com.sapportals.wcm.repository.manager.reporting.RPRepositoryManager.getResource(RPRepositoryManager.java:581)
     at com.sapportals.wcm.repository.RMAdapter.getResource(RMAdapter.java:228)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findResource(CmAdapter.java:1349)
     at com.sapportals.wcm.repository.runtime.CmAdapter.findManagerAndResource(CmAdapter.java:1322)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:979)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.service.reporting.ReportingService.localConfigure(ReportingService.java:294)
     at com.sapportals.wcm.service.reporting.ReportingService.startUpImpl(ReportingService.java:74)
     at com.sapportals.wcm.service.AbstractService.start(AbstractService.java:167)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.tryToStart(CrtThreadSafeComponentHandler.java:247)
     at com.sapportals.wcm.crt.CrtThreadSafeComponentHandler.handleLookup(CrtThreadSafeComponentHandler.java:109)
     at com.sapportals.wcm.crt.CrtComponentManager.lookup(CrtComponentManager.java:322)
     at com.sapportals.wcm.crt.CrtComponentManager.lookupChildComponent(CrtComponentManager.java:403)
     at com.sapportals.wcm.crt.CrtContainerManager.lookupComponent(CrtContainerManager.java:44)
     at com.sapportals.wcm.crt.CrtSystemImpl.lookupComponentByUri(CrtSystemImpl.java:131)
     at com.sapportals.wcm.crt.CrtComponentManager.startUp(CrtComponentManager.java:278)
     at com.sapportals.wcm.crt.CrtSystemImpl.startUpComponentManager(CrtSystemImpl.java:166)
     at com.sapportals.wcm.repository.runtime.CmSystem.startUp(CmSystem.java:227)
     at com.sapportals.wcm.repository.runtime.CmSystem.getInstance(CmSystem.java:164)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResourceImpl(CmAdapter.java:974)
     at com.sapportals.wcm.repository.runtime.CmAdapter.getResource(CmAdapter.java:192)
     at com.sapportals.wcm.portal.service.KMServiceImpl.afterInit(KMServiceImpl.java:249)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.__initServiceInstanceStep2(PortalServiceItem.java:877)
     at com.sapportals.portal.prt.core.broker.PortalServiceItem.startServices(PortalServiceItem.java:1118)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startLoadOnStartupServices(PortalAppBroker.java:1707)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.start(PortalAppBroker.java:1662)
     at com.sapportals.portal.prt.core.broker.PortalAppBroker.startNonCoreApplications(PortalAppBroker.java:1592)
     at com.sapportals.portal.prt.runtime.Portal.init(Portal.java:422)
     at com.sapportals.portal.prt.core.PortalCoreInitializer.coreInit(PortalCoreInitializer.java:54)
     at com.sapportals.portal.prt.dispatcher.PortalInitializer.<init>(PortalInitializer.java:129)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doSetupPortalInitializer.run(Dispatcher.java:161)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.initDispatcher(Dispatcher.java:361)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.access$000(Dispatcher.java:42)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$InitRunner.run(Dispatcher.java:114)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.init(Dispatcher.java:394)

Go to visual admin -> server -> services -> JCO RFC provider.
Check the RFC that connects to the BI Abap.
Its reporting the J2EE_GUEST user in the SAP with the system nr 00.
Is this BI java portal?
Is the java portal a addon to Abap or having seperate SID?
Check the connection definitions are correct and the gateway is running.

RSBOLAP 018 Java system error in BEx Web Application Designer

Hello,
while doing inside BEX Web Application Designer "validation of webtemplate" with
command "validate on server" I get following error message of WAD :
" Message RSBOLAP 018 description : Java system error : an Unknow Error occured during portal communication"
My procedure till now was ( please see results as screenshots in attachment) :
a) ckecking prerequisites for "Java template installer'" --> result "prerequisites.jng"
b) running "Java template installer" -> " result templateInstaller.jpg"
c) running Bex Web Application Designer as mentioned above results in error
message as mentioned above
d) running Diagnostic & Support Desktop Tool --> "result Diagnostic support desktop tool.jpg"
It says that something is wrong with "BI Mastersystem" because of failed connect to
message server.
Please advice me what I should do.
Thanks in advance
Regards,
Oscar

Hello
It is obvious that the connection between the ABAP and the Java is not working.
There should be a JCo RFC from the portal side to the ABAP stack set up and an RFC from the ABAP stack to the portal.
Check the entries of the table RSPOR_T_PORTAL
The RFC specified here should be the one mentioned above (ABAP - Java)
Check the name of the system should be SAP_BW
Is the parameter icm/host_name_full set on the ABAP stack with the domain name ?
Connect to the BI portal:
http://FQDN:5NN00/irj/portal
Navigate to system administration -> system configuration -> system landscape -> expand "portal content" -> systemlandscape -> SAP_BW
Right click on SAP_BW - Open - Object
Here you need to maintain these:
ITS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
ITS Host Name - FQDN_OF_BW_ABAP:port - You can use the value of icm/host_name_full parameter and retrieve port number from Tx SMICM - Services
ITS Path - /sap/bc/gui/sap/its/webgui
ITS Protocol - Select http
Logical System Name - BW ABAP Logical System Name - Tx SCC4 or BD54
Logon Method -SAPLOGONTICKET
Message server - BW ABAP FQDN
SAP Client - BW ABAP Client Number
SAP System ID (SID) - BW ABAP SID
Server Port - 39NN
Web AS Description - BW ABAP Logical System Name - Tx SCC4 or BD54
Web AS Host Name - FQDN_OF_BW_ABAP:port - icm/host_name_full and retrieve port number from Tx SMICM - Services
Web AS Path - /sap/bw/BEx
If everything is set properly then do a test connection.
Good Luck
RB

Java Communication error:Error while opening an RFC connection

Hi,
I am getting Java Communication error:Error while opening an RFC connection when i try to run a query from Bex analyser.
please let me know how to resolve this
Thanks
Bala Duvvuri

This error usually comes when the java stack is not upgraded.
when you upgrade yourABAP stack, simultaneously you have to upgrade the java stack also.
Please co-ordinate with your basis team to inform EP team to upgrade the java stack when basis team do ABAP stack upgrade.
Hope this would help you.

Error while deploying the aplication-jco error

Hello Experts,
i know   thousends of questions in jco error. I have followed that threads , still i am getting an error.
Plz help me out from that error.
My EP server is running on was 6.20,
and xi server is running on was 6.40.
what i have done:
I have downloaded fightslist application from sdn.
i have deployed that application to was 6.40.
i created one technical system for abap.
i configured sld.
i entered service name(sapms147 3600/tcp(this is ides(4.7) serversid and port)) in servicefile in was 6.40 machine.
when maintaing jco connections the following error has come:
com.sap.mw.jco.JCO$Exception: (102) RFC_ERROR_COMMUNICATION: Connect to message server host failed Connect_PM TYPE=B MSHOST=mlbpsap06 GROUP=PUBLIC R3NAME=I47 MSSERV=sapmsI47 PCS=1 LOCATION    CPIC (TCP/IP) on local host with Unicode ERROR       service 'sapmsI47' unknown TIME        Fri Dec 01 15:27:10 2006 RELEASE     640 COMPONENT   NI (network interface) VERSION     37 RC          -3 MODULE      ninti.c LINE        494 DETAIL      NiPGetServByName2: service 'sapmsI47' not found SYSTEM CALL getservbyname_r COUNTER     7
My doubts are:
1.where i have to enter service i.e which machine (6.40 or 4.7 machine).
2.while creating technicalsystem which product i have to choose).
3while creating jco connection
    whichone i have to choose either dictinory mata data or applicationdata.
    in message server connection which user id & password i have to give means 4.7 userid or xiserver userid & password.
Plz helpme out from this.
Thanks in advance.

Hello Sai,
NWDS is local means which machine i am using.
My EP 6.0 SP2 in 172....202 but it is reunning on was 6.20.(mlbpsap02)
and here was 6.40 ip is 172.....203 IP ,but XI is installed on this server)(mlbpsap03)
and R/3 ECC ip is 172......201.(mlbpsap01)
no sneak preview edition and all.
I have downloaded application(sample flight) in webdynpro.
and i configured sld in 203(cim test connection is successfull) ip.and also entered the service name(sapmsecc 3600/tcp).After entering the service name i restarted the server
and created technical system for abap (and here selectiong products ecc components are not there.)
in webdynpro content admin while maintaing jco , the above error is coming.
i am unable to find where the problem is
the main thing is ep is not in was 6.40
further what i do
and where i enter the host ip and aliases.

ABAP and JAVA sync issue

Hello,
We are having MI 7.0 at SPS15.Am trying to apply add to our system(we created SDA file from NWA as an addon).SDA addon getting deployed but its not getting sync between ABAP and Java stack even if is run reload sever time from NWA->Administrator->Mobile Infrastructure->Mobile Components.I can see add-on when i check from SDM but it cannot see when i search under Mobile component in NWA.Application logs shows below error.
#703543993#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##8e6d577024d511e1a299001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592001800000015000030100004B3E6C1311ED1#1323703575929#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##a19424a024d511e18ede001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_9##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBea                                                                                n#Plain####
#1.#001635730592000F00000016000030100004B3E6C662CEBE#1323703663073#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_ADMIN#47##n/a##d588777024d511e1c64a001635730592#SAPEngine_A                                                                                pplication_Thread[impl:3]_18##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerB                                                                                ean#Plain####
#1.#001635730592002000000015000030100004B3E6CDC2D7E4#1323703786809#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##1f482a9024d611e18dc1001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_29##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200260000000C000030100004B3E6D02A2DDA#1323703827137#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##37527e6024d611e1a43c001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_39##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#00163573059200350000000B000030100004B3E6D1150767#1323703842528#/Applications                                                                                #sap.com/tcwddispwda#com.sap.ip.mi.admin.wd.paramset.Details.Method-->wdDoModi                                                                                fyView()#J2EE_ADMIN#56##uwsvt729.merck.com_VZ1_12609950#J2EE_ADMIN#2e05832024d61                                                                                1e1b753001635730592#SAPEngine_Application_Thread[impl:3]_33##0#0#Error#1#com.sap                                                                                .ip.mi.admin.wd.paramset.Details#Plain###Specify all parameters#
#1.#00163573059200250000007C000030100004B3E6F8460AEE#1323704500063#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##c86ab33024d711e185b5001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_22##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592002F00000015000030100004B3E728C1AF02#1323705313486#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##ad1da59024d911e1a138001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_37##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
#1.#001635730592000F0000000000002A400004B3E754A629F8#1323706045836#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#J2E                                                                                E_GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[im                                                                                pl:3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsOrganizerAdapter#Plain###CMS o                                                                                rganizer proxy is waiting for requests#
#1.#001635730592000F0000000100002A400004B3E754A659EE#1323706045848#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#J2EE_                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl                                                                                :3]_26##0#0#Info#1#com.sap.cms.pcs.serverAPI.CmsManagerAdapter#Plain###CMS manag                                                                                er proxy is waiting for requests#
#1.#001635730592000F0000000200002A400004B3E754A6715D#1323706045854#/Applications                                                                                /CMS/PCS#sap.com/tcSLCMS~PCS#com.sap.cms.pcs.transport.proxy.CmsLogViewer#J2EE                                                                                GUEST#0##n/a##61feecc024db11e1b4cb001635730592#SAPEngineApplication_Thread[imp                                                                                l:3]_26##0#0#Info#1#com.sap.cms.pcs.transport.proxy.CmsLogViewer#Plain###CMS Log                                                                                Viewer is waiting for requests#
#1.#001635730592000F0000000300002A400004B3E754A67B77#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###CMS recovery servlet is wai                                                                                ting for requests#
#1.#001635730592000F0000000400002A400004B3E754A67CE5#1323706045857#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###start recovery#
#1.#001635730592000F0000000500002A400004B3E754AA7F91#1323706046120#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Import running in 0 queue(s). Start check if they are really running or                                                                                need recovery.#
#1.#001635730592000F0000000600002A400004B3E754AA8344#1323706046121#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Import running. Checked Items: 0; Recovered Items: 0; Re                                                                                covery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000700002A400004B3E754AAACBA#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###CMS recovery found 0 QueueItem(s) wi                                                                                th state Assembly running in 0 queue(s). Start check if they are really running                                                                                or need recovery.#
#1.#001635730592000F0000000800002A400004B3E754AAAEE5#1323706046132#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.pcs.QueueItemRecovery#J2EE_GUEST                                                                                #0#SAP J2EE Engine JTA Transaction : [0ffffffc069ffffff9e0008]#n/a##61feecc024db                                                                                11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0#Info#1#com.sap                                                                                .cms.recovery.pcs.QueueItemRecovery#Plain###Finished check and recovery for all                                                                                CMS QueueItems of state Assembly running. Checked Items: 0; Recovered Items: 0;                                                                                Recovery Failed Items: 0; Real running Items: 0#
#1.#001635730592000F0000000900002A400004B3E754AAB68F#1323706046134#/Applications                                                                                /CMS#sap.com/tcSLCMS~PCS#com.sap.cms.recovery.RecoveryServlet#J2EE_GUEST#0##n/                                                                                a##61feecc024db11e1b4cb001635730592#SAPEngine_Application_Thread[impl:3]_26##0#0                                                                                #Info#1#com.sap.cms.recovery.RecoveryServlet#Plain###finished recovery#
#1.#00163573059200140000000300002A400004B3E7AA40154F#1323707482010#/Applications                                                                                #sap.com/tcmobileadmin~ea#com.sap.ip.mi.ejb.mcd.MobileContainerBean.Method---:                                                                                Processfunction#J2EE_GUEST#0##n/a##b9c439d024de11e1a4ee001635730592#SAPEngine_Ap                                                                                plication_Thread[impl:3]_10##0#0#Error#1#com.sap.ip.mi.ejb.mcd.MobileContainerBe                                                                                an#Plain####
Thanks

Hi,
Tha ABAP stack consists of the Integration Server which in turn contains your Integration Engine and Business Process Engine.
The J2EE stack contains the Adapter Engine and your IR and ID run on the J2EE engine.
Ever wondered how and where the XI pipeline gets executed? It happens in the ABAP stack.
All messsages picked by the Adapter Framework running on the J2EE engine are passed to the Integration Engine, which does the routing. The mapping program again gets executed on the Java stack and the rest of the pipeline servies are executed again on the ABAP stack and so on.
Take a look at the XI overview doc to understand this better,
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a3d3c390-0201-0010-c490-bd85917138c8
Regards,
Bhavesh

Using JCO error Wrong repository version = 0 encountered.

Hi Guru,
We convert our existing Java Jco program to call RFC Sender adapter and XI should forward the request to RFC receiver adapter to our ECC.
We found that when we create client connection using gwhost, gwserv and tpname which is config in RFC sender adapter.
In our Java program throw error in the step of mRepository.getFunctionTemplate.
The error is "Wrong repository version = 0 encountered.".
It seems the program can not access function template from repository.
Anyone have this experience before, please advise
Thanks you.

It's working now.
For your knowledge, it seems it was something wrong inside the jrfc.jar.
The problem is not exactly the same but the solution is to apply OSS note 816491.

ABAP to Java - JCo error

Similar Messages

Maybe you are looking for