Skip to Content
author's profile photo
Former Member

Messaging System requires J2EE enviroment

Jun 18, 2004 at 09:28 PM | 8 Views

Hi buddies,

Here's my system landscape.

I have a Java stand alone application on my local machine, which implements an outbound message interface. And I have an ABAP proxy class in XI system, which implements an inbound message interface.

I also have another XI system as integration server.

When I run Java application from my local machine, I always get a system fault message 'Messaging System requires J2EE enviroment'.

Does anyone have idea on this message? What is the messaging system it refers to (integration server?)?

Thanks in advance.

SAP Process Integration | SAP TechEd
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

4 Answers

  • author's profile photo
    Andrzej Filusz
    Jun 19, 2004 at 01:27 PM

    Hi!!!

    If I understood your scenario you well, you have something like that:

    [java stand alone app]>[SAP XI]>[another SAP XI with ABAP proxy objects]

    Now, could you tell me how your java stand alone app connects to SAP XI?

    You has written that your app implements an outbound message interface, so I suppose you are using java proxy, right?

    But your error message suggests me that there could be also JMS (Java Messaging Service). Is it true?

    Are you using JMS adapter in this scenario?

    Regards,

    Andrzej Filusz

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Stefan Grube
    Jun 24, 2004 at 01:16 PM

    Hi,

    you need to maintain following entry in the exchange profile:

    com.sap.aii.proxy.framework.connection.timeoutInMSec=-1

    If you use jpf.properties instead Exchange Profile, maintain the entry there.

    Regards

    Stefan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Jun 24, 2004 at 03:37 PM

      Thanks!!

      I checked the exchange profile setting, timeoutInMSec = -1. I ran the java application again. That error message is gone! So this problem should be resolved!

      But I got another error message, which is in German:

      ROUTING.NO_RECEIVER_CASE_BE:Es konnte kein Empfänger ermittelt werden (Verarbeitungstart: QoS = BE)

      .

      The machine translation is: It could no recipient ascertains become (processing start: QoS = BE).

      Any idea of this message?

      I already defined msg mapping and interface mapping. I also generated ABAP inbound proxy class and implemented the proxy method EXECUTE_SYNCHRONOUS. I tested the inbound proxy class, it's working fine.

  • author's profile photo
    Former Member
    Jun 24, 2004 at 10:12 PM

    Hello :

    I am not too sure if this is resolved here are the tips.

    You need to have jpf.registry in the work directory from where you are invoking your application and it should have

    the following line.

    com.sap.aii.proxy.framework.destination=http://<IS-HOST>:8000/sap/xi/engine/entry?action=execute&pipelineid=central

    Set Technical Id Properties to

    SAPTechnicalSystemIdentification=<SLD Java Stand alone technical system sytem>.SystemHome.<IS-Host name>

    Set dbconnect properties to

    hostname = <IS-HOST>

    systemNumber = <INSTANCE NUMBER>

    client = <IS-HOST CLIENT>

    user = <USER>

    password = <PWD>

    language = en

    I am sure you would have defined your system as JAVA Stand alone in SLD.

    Also make sure your class path refers to

    set classpath=.;C:\;C:\;C:\jdk1.3.1_09\src.jar;C:\jdk1.3.1_09\lib;C:\java\lib\aii_msg_runtime.jar;C:\java\lib\aii_msg_runtime.jar;C:\java\lib\aii_proxy_xirt.jar;C:\java\lib\aii_util_cimaccess.jar;C:\java\lib\aii_util_misc.jar;C:\java\lib\aii_util_rb.jar;C:\java\lib\aii_util_xml.jar;C:\java\lib\dbprofiles.jar;C:\java\lib\ejb20.jar;C:\java\lib\inqmyxml.jar;C:\java\lib\lcrclient.jar;C:\java\lib\logging.jar;C:\java\lib\sapjco.jar;C:\java\lib\SAPmdi.jar;C:\java\lib\messaging.jar;C:\java\lib\tc_sec_api.jar;C:\java\lib\tc_sec_core.jar;<path for outbound proxy classes>

    This works for us.

    Hope this helps.

    Thanks,

    Rajan Kidambi

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Jun 24, 2004 at 10:13 PM

    sorry i meant jpf.properties, not jpf.registry

    Thanks,

    Rajan Kidambi

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member
      Jun 29, 2004 at 03:13 PM

      Finally it works! The second message (German msg) that I got is just because I didn't create business scenario and receiver determination.

      Thanks!