J2ME WMA wireless messaging api

Hi
Does anyone know if I can use the WMA from J2ME in my normal Java 1.4 SE version to encode and decode SMS messages that I have recieved from a cell phone via the serial port buy calling AT+ commands???
I am writing my own pdu sms message converter but there are too many aspects to cover I think...
Any help or insight will be much appreciated.
Thanks
Pug206Aid

I too looking for the same, my requirement is just recieving a sms from gsm mobile and feeding to the system. Can any one suggest what technology can be used for this, what should be real time environment.
Thanks in Adv..
Best Regards,
Sridhar G

Similar Messages

Sending SMS to server - Wireless Messaging API (WMA)

Hello :-)!
In general I want to create application for CLDC (with the use of MIDlet). (And maybe later to try the same with CDC). I want my application to create some data based on communication with the user of mobile phone and then to send little text file to the application on server computer.
I found that there exists such a thing as WMA - Wireless Messaging API. I downloaded examplary .jar & .jad files (with sources and documentation):
[http://www.forum.nokia.com/info/sw.nokia.com/id/9edb3299-e0f4-449d-a2fd-fa15ddbeed8b/MIDP_2_0_Wireless_Messaging_API_Example_v1_0.zip.html|http://www.forum.nokia.com/info/sw.nokia.com/id/9edb3299-e0f4-449d-a2fd-fa15ddbeed8b/MIDP_2_0_Wireless_Messaging_API_Example_v1_0.zip.html]
and copied those files to Sony Ericsson K750i. I installed the application, run it, it asked me whether I want to allow this application to receive SMS, I answered yes and... nothing else happened and the application exited. I run this application once more, it doesn't do anything at all and exits.
I tried to analyse the code but it didn't help me to notice what is wrong with the program.
In init() there is initialization of what and where will be sent (port number and message). (Function init is called in startApp so in my application I will need to call it in the other place in the code and I will take the content of the message from the other place that jar or jad files, as in this examplary application).StartApp() calls init(), it listens to incoming messages, creates commend, label etc. (Probably I need to erase from this example code responsible for listening to incoming messages so that this examplary application will work on my Sony Ericsson?).
CommandAction(c,d) sends text or binary message (depending on choice in the field cg.setSelectedIndex) or exits the application for "exit".
ItemStateChanged() changes from binary to text mode and vice versa.
SendBinaryMessage(connection,destAddress,Body) and sendTextMessage(...) send the message.
I don't know what are those "private static final String".>
Greetings:)!

{color:#000080}Learn to live with it, this is the specified behavior for SMS sending. Unless you can hack your phone's firmware, there's nothing you can do about it.
db{color}

Wireless Messaging API (WMA);

Hello, I am new to J2ME and I have two question regarding the Wireless Messaging API
1) In J2SE, I can find the J2SE api by going to google and searching for "java api"
However, I am having a difficult time finding the WMA api.
2)
When using the WMA api to send text message.
is there anyway to disable the warning message "Allow application WMA Demo to send text message to 778-xxx-xxxx?"
This message is very annoying.
Thank you for your help

{color:#000080}Learn to live with it, this is the specified behavior for SMS sending. Unless you can hack your phone's firmware, there's nothing you can do about it.
db{color}

Wireless Messaging API

Hi you all,
I am trying to send messages over GSM using the WMA API, but I am rather new to J2ME and I am struggling to understand a few things.
I have been searching and I found this code:
import javax.microedition.midlet.*;
import javax.microedition.lcdui.*;
import javax.microedition.io.*;
import javax.wireless.messaging.*;
public class SMSClient extends MIDlet {
    protected Display display;
    protected Displayable displayable;
    public SMSClient() {
     display = Display.getDisplay(this);
     displayable = new Form("SMS Client");
    public void startApp() {
     display.setCurrent(displayable);
     try {
         String address = "sms://+5550000:5432";
         String msg = "Hello";
         MessageConnection smsconn =
          (MessageConnection) Connector.open(address);
         TextMessage txtmessage =
          (TextMessage)smsconn.newMessage(
                      MessageConnection.TEXT_MESSAGE);
         txtmessage.setPayloadText(msg);
         smsconn.send(txtmessage);
     } catch (Exception e) {
         System.out.println(e.toString());
    public void pauseApp() {
    public void destroyApp(boolean unconditional) {
     display = null;
     displayable = null;
}Which allows me to send sms messages. What I am not undertsnding thought is this bit:
         String address = "sms://+5550000:5432";Don't I need to use any gateway to send the message???
Another issue I am having is about the above package:
import javax.microedition.midlet.*;which doesn't come included in the J2ME version I am using... But as far as I know that package is only used for GUI applications, I am wrong??
Thanks in advance.
MeTitus
Message was edited by:
Me_Titus

Hi deepspace...
I am developping for this module
http://www.imsys.se/products/modules.htm
and these are the packages that come with it:
com.dalsemi.onewire
com.dalsemi.onewire.adapter
com.dalsemi.onewire.container
com.dalsemi.onewire.utils
com.dalsemi.system
java.io
java.lang
java.net
java.util
javax.comm
javax.microedition.io
se.imsys.comm
se.imsys.net
se.imsys.ppp
se.imsys.protocol.http
se.imsys.system
se.imsys.utilThe code I am developping is not supposed to have any interface. Basically it will check messages from a pop server, and will send some of those messages to mobile phones, This device also has a gsm antenna...
I am really lost with this...
MeTitus

Run Wireless message API

Hi all,
I downloaded and installed J2ME toolkit and WMA packages.
Any one know how to develop simple example for sending sms message.
please post simple example and any additional requirements in step wise.
I will really appreciate.
Thanks,
Bala Datla

http://wireless.java.sun.com/midp/ttips/wma/

Wireless Messaging API simulator

hi,
does anybody know about simulator that can simulate sms
for testing the WMA?

hi,
http://java.sun.com/j2me/docs/wtk2.0_b2/SMSDemo.html
hope it's useful for u.

Wireless Messaging From Servlet

Can I send wireless messages from a servle using Wireless Messaging API ???
I have a little test (taken from http://jan.netcomp.monash.edu.au/internetdevices/wireless/wma.html).
There's a client that send messages, and a server that listens for incoming messages.
It work fine when I run the both under J2ME emulator, the client sends the messages ok and the server receive ok too.
Now I want to send the messages from a servlet. So I left the server unchanged and put the client code in the servlet but it doesn't works
The client's something like this
try
String address = "sms://+5550000:5432";
String msg = "Hello";
MessageConnection smsconn = (MessageConnection) Connector.open(address);
TextMessage txtmessage = (TextMessage)smsconn.newMessage(MessageConnection.TEXT_MESSAGE);
txtmessage.setPayloadText(msg);
smsconn.send(txtmessage);
catch (Exception e)
System.out.println(e.toString());
System.out.println (e.getMessage());
e.printStackTrace();
But running in the servlet, when opening the MessageConnection it throws an IOException "java.io.IOException: NYI".
Any Ideas??
Thanx

From a servlet I got it working (sends the messages ok from the servlet to the device listening).
I did it using the wma-tck.jar bundeled with Wireless Messaging API.
The servlet code to send the message's something like this.
String address = "sms://+5550000:5432"; //phone_number:port on wich the device is listening
String message = "MESSAGE";
MessageConnection conn = null;
Message mess = null;
conn = (new SMSConnector()).open(address);
mess = conn.newMessage("text");
((TextMessage)mess).setPayloadText(message);
mess.setAddress(address);
conn.send(mess);

JavaDoc for Wireless Messaging

Does anybody know where I can get the WMA (JSR-205) API JavaDoc? I looked in all the obvious places but could not find it. The WTK installed documentation just links to http://jcp.org/aboutJava/communityprocess/final/jsr205/ But this page only has a download for the specification (a PDF file). I tried going from java.sun.com --> J2ME --> APIs etc, but still ended up eventually at the JCP page above. Needless to say, this was an incredibly annoying experience.
Question: It's great having the WTK support wireless messaging, but how does someone write any code without the API JavaDoc?
Thanks,
yushen

I have exactly the same problem. I've now been trying
for 20 minutes to find the insert expletive here
javadocs for the JSR-205 API and I can't and it's
starting to wind me up a little bit. Why is the first
hit I get on google for the javadocs for some other
sucker looking for the same thing. Honestly people,
what would it take to include it in the WTK, like
20kb? And put a link that says JAVADOCS DOWNLOAD HERE
IDIOTS. thanks.Here you go - http://raud.ut.ee/~tec/static/api/WirelessMessagingAPI_JSR120/overview-tree.html
I know it's not JSR-205 but it's good enough.
Vaiden
Message was edited by:
Vaiden

Where can I find javax.wireless.messaging

Hello,
I am trying to fellow the tutorial ( http://developers.sun.com/mobility/midp/articles/wma/ ) about sending SMS. I think I need a package called javax.wireless.messaging. Do you know where I can find this?

The JSR is the source of the original proposal
[http://jcp.org/en/jsr/detail?id=120]
It is an API specification so you need the API and an actual implementation as well.
The above has a reference implementation. A "reference implementation" is intended to demonstrate that the API is sufficient. It isn't intended to be a production implementation and there might be problems with it.
Note that the API is not part of the Java API. Including 1.7
That above url via the "Final Release 2" suggests that Sun has a real implementation (alternative to the reference). Probably commercial. There might be other implementations as well.

Com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException in sap pi

Hi all,
I am working on SAP PI 7.3.1 SP09. Currently we have interfaces which uses 50200 port. I have created a http destination from nwa pointing to https://....url. So all of a sudden all the interfaces went to error state. After debugging i found that the port 50200 is replaced with 50201which is https port. After changing the port to initial value ie., 50200 all interfaces are working fine except the one which were pointing to https url and they are showing the following error description.
<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException</SAP:AdditionalText>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
The entire trace is as follows:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="T">Party normalization: sender</Trace>
<Trace level="3" type="T">Sender scheme external =</Trace>
<Trace level="3" type="T">Sender agency external =</Trace>
<Trace level="3" type="T">Sender party external =</Trace>
<Trace level="3" type="T">Sender party normalized =</Trace>
<Trace level="1" type="T">Determining the sender agreement</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>
<Trace level="2" type="T">Request Line = POST /sap/xi/engine/?type=entry HTTP/1.0</Trace>
<Trace level="2" type="T">Host = 10.66.14.150:50200</Trace>
<Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
<Trace level="1" type="T">Remote address = 10.66.10.160</Trace>
<Trace level="1" type="T">User = SFUSER</Trace>
<Trace level="1" type="T">Process ID: 760</Trace>
<Trace level="1" type="T">Work Process ID: 10</Trace>
<Trace level="1" type="T">Message ID = 53BEFE7146893BD5E10000000A420AA0</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">
<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
<Trace level="3" type="T">##### DG: 3</Trace>
<Trace level="3" type="T">##### TO: 3</Trace>
<Trace level="1" type="T">Hop engine name = is.02.devpipd1</Trace>
<Trace level="1" type="T">Hop engine type = IS</Trace>
<Trace level="1" type="T">Hop adapter name = XI</Trace>
<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>
- <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
<Trace level="3" type="T">No triggers found. OK.</Trace>
</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
<Trace level="1" type="Timestamp">2014-07-10T08:56:37Z INDIA</Trace>
<Trace level="1" type="T">ACL Check is performed</Trace>
<Trace level="1" type="T">XML validation is executed</Trace>
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">PLNAME = CENTRAL</Trace>
<Trace level="1" type="T">QOS = BE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>
<Trace level="3" type="T">Pipeline-Elements for pipeline SAP_CENTRAL</Trace>
<Trace level="3" type="T">0001 PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">0002 PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T">0003 PLSRV_INTERFACE_DETERMINATION</Trace>
<Trace level="3" type="T">0004 PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
<Trace level="3" type="T">0005 PLSRV_MAPPING_REQUEST</Trace>
<Trace level="3" type="T">0006 PLSRV_OUTBOUND_BINDING</Trace>
<Trace level="3" type="T">0007 PLSRV_VIRUS_SCAN_RQ_OUT</Trace>
<Trace level="3" type="T">0008 PLSRV_XML_VALIDATION_RQ_OUT</Trace>
<Trace level="3" type="T">0009 PLSRV_CALL_ADAPTER</Trace>
<Trace level="3" type="T">0010 PLSRV_VIRUS_SCAN_RS_INB</Trace>
<Trace level="3" type="T">0011 PLSRV_XML_VALIDATION_RS_INB</Trace>
<Trace level="3" type="T">0012 PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">0013 PLSRV_VIRUS_SCAN_RS_OUT</Trace>
<Trace level="3" type="T">0014 PLSRV_XML_VALIDATION_RS_OUT</Trace>
<Trace level="3" type="T">system-ID = PD1</Trace>
<Trace level="3" type="T">client = 001</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = SFUSER</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="2" type="T">Persisting original message</Trace>
<Trace level="3" type="T">Message-Version = 000</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_VALIDATION</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T" />
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">
<Trace level="3" type="T">Pipeline Service = PLSRV_XML_VALIDATION_RQ_INB</Trace>
<Trace level="3" type="T">Skip Inbound Validation =</Trace>
<Trace level="3" type="T">Skip Outbound Validation =</Trace>
<Trace level="3" type="T">Area = XML_VALIDATION_INB</Trace>
<Trace level="1" type="T">Reading sender agreement</Trace>
<Trace level="1" type="T">Message does not contain a sender agreement</Trace>
<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>
</Trace>
</Trace>
</Trace>
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA End of pipeline service processing PLSRVID= PLSRV_XML_VALIDATION_RQ_INB</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 001</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
<Trace level="3" type="Timestamp">2014-07-10T08:56:37Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
<Trace level="3" type="T

HI,
Thank you for your hint. Maybe I just forgot to mention one important fact. We have second SAP Netweaver PI 7.1 which is completely our system. The first one I mentioned in first message is the customer's one. The one we have extra is also connected to MAXIMO and GIS. Settings of this interface is completely same among one thing:
Patch level of XIAF:
1. customers SAP PI level is
Adapter Common Library Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:29:47+0000)
Adapter Application Version: 1.7.1007.20081105173106.0000, NW07_07_REL (2008-11-07T17:30:00+0000)
2. our SAP PI level is
Adapter Common Library Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:21+0000)
Adapter Application Version: 1.7.1008.20100215155230.0000, NW07_08_REL (2010-02-15T17:19:31+0000)
Both of them has Axis Version: Apache Axis version: 1.4 Built on Apr 22, 2006 (06:55:48 PDT)
Also important to mention is fact that same problem happened in our SAP PI, but we implemented last patch of XIAF and it has suddenly started to work. I have suspicion it is somehow connected to this patch. Btw. this patch contains a lot of notes regarding AXIS framework (i.e. 1435998, 1150375, 1048268), so obviously some bugs of the AXIS adapter has been resolved by this patch.
What do you think ?
Thanks

Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service. Can anyone please
help me.
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found

In my 2006 biztalk application I have exposed web service to receive SAP input. It was working fine. After I have modified something in orchestration in that application . I am getting following error while SAP try to consume my web service.
HI Arivazhagan K,
Could you give some explanation about what you modified? according the to error message, this is "resource is not found issue".
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

File to RFC Error com.sap.engine.interfaces.messaging.api.exception.Messagi

Hi ,
I am doing File to RFC Scenario.
My file get picked and I able to view the audit log under RWB message monitoring.
Here I am getting the error
u201CTransmitting the message to endpoint dest://XI_INTEGRATION_SERVER using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Error transmitting the message using HTTPTransmitter. Reason: java.net.MalformedURLException: unknown protocol: dest.
Can any one tell me what is the reason.
Regards, Navneet

Hi Prakasu,
I am using PI 7.1 version .
When I opened SMICM there I am finding the HTTP Port as 52000.and the BS at SLD are also using the same Port in URL..
And when i verified with the Basis they confirmed that Exchange profile is set correctly.
But My file adapter is still not able to send the data to IS.
Than I configured a scenario file to file without IR object and in this case data is coming to IS and it is succesfull also.
what is the reason that in this case file adapter not able to push the data to IS.
I used File adapter with NFS protocol.
regards,
navneet

SOAP Sender Error - com.sap.engine.interfaces.messaging.api.exception

Hi,
I am testing a SOAP Sender Channel using a SOAP Client and getting the following error. I have read almost all the posts related to errors in SOAP Channel and also have checked my URL which is correct. AS mentioned in many of the posts, my url goes like
https://<host>:<port>/XISOAPAdapter/MessageServlet?channel=:DEMO:SOAP_s_GETLIST&version=3.0&SenderService=DEMO&interface=si_os_GETLIST&interfaceNamespace=<namespace>
This is the error that I get when sending a message to the interface
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
   <SOAP:Body>
      <SOAP:Fault>
         <faultcode>SOAP:Server</faultcode>
         <faultstring>Server Error</faultstring>
         <detail>
            <s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">
               <context>XIAdapter</context>
               <code>ADAPTER.JAVA_EXCEPTION</code>
<text>com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIProxy:PARSE_APPLICATION_DATA:
     at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1041)
     at sun.reflect.GeneratedMethodAccessor1044_10001.invoke(Unknown Source)*
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:585)
            </s:SystemError>
         </detail>
      </SOAP:Fault>
   </SOAP:Body>
</SOAP:Envelope>
Has Anybody got this problem before? Is it any problem with the SOAP Adapter itself or with the data that is going in the message? If so, What is the possible solution for this?
Thanks,
Rashmi.

Hi Rashmi,
I also think your problem is data related.
Check the response in your SAP PI message monitor (SXMB_MONI) when you trigger a request using SoapUI. It sometimes provides a bit more detail. You design (data types, message types, service interfaces etc.) was done in SAP PI 7 then an Abap Proxy was generated from the service interface?
Sometimes there is an issue between the XSD data type declaration in SAP PI and the conversion to Abap data types that takes place when a proxy is generated from a PI Service Interface.
Check the data that you pass in your request, especially those like datetime fields. Maybe even change some of the data type definitions (like datetime) to a string (request & response) & then test through SoapUI & see if you still get the error. Then you can work out how to best resolve it.
Best Regards, Trevor

Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

Hi guys,
we are using PI 7.11.
With this release local processing on the advanced adapter engine is possible, when using integrated configurations.
This works fine.
Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.
I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.
Afterwards I treied to restart the message.
Following error occurs.
com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.
I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache
trying restart the failed message ends up in the error specified aboce.
Anyone faced the same issue already?
Kind regards
Jochen

HI Jochen,
I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.
To do a CPA Cache Refresh from the Adapter Engine:
To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:
http://<host>:<port>/CPACache/refresh?mode=delta|full
The Monitoring url is like this:
http://<host>:<port>/CPACache
Check this How-to Guide on Cache, it will be useful:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&overridelayout=true
Thanks
Dhwani

Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all

Hello,
I have an issue configuring a simple File Adapter Content Conversion, it will be great to give me some support as I'am new in the PO Environment.
Iam reading a flat file and trying to write into an XML in the same FTP server
I have a 1 to 1 Mapping as follows
And my Content Conversion at Sender side Looks like this
After running the configuration Iam getting following error message
Error: com.sap.engine.interfaces.messaging.api.exception.RetryControlException: Receiver Determination did not find any receivers at all
My System is the SAP Netweaver Process Intgration 7.4 single Java stack
Do you have any idea how to fix this issue?
Many thanks in advance
Khadim

Hi evrybody
I have enabled the tracing of ICO and have seen that my payload for the message mapping is ok,.
<ns:hartgeldbest_ERP_KT xmlns:ns="http://xxxxxx.de">
<Recordset>
<header>
     <gesellschaft>03</gesellschaft>
     <filiale>000</filiale>
     <satzart>11</satzart>
     <datum>00000000</datum>
     <kennzeichen>1</kennzeichen>
</header>
</Recordset>
</ns:hartgeldbest_ERP_KT>
The issue is on detrmining the RECEIVER in the Main-XML
<sap:Main xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sap="http://sap.com/xi/XI/Message/30" versionMajor="3"versionMinor="1" SOAP:mustUnderstand="1">
<sap:MessageClass>ApplicationMessage</sap:MessageClass>
<sap:ProcessingMode>asynchronous</sap:ProcessingMode>
<sap:MessageId>ae41678e-da87-11e3-cd0f-0000006831a2</sap:MessageId>
<sap:TimeSent>2014-05-13T10:16:43Z</sap:TimeSent>
<sap:Sender>
<sap:Party agency="http://sap.com/xi/XI" scheme="XIParty"/>
<sap:Service>CC_Hartgeldbest_File2Idoc</sap:Service>
</sap:Sender>
<sap:Receiver>
<sap:Party agency="" scheme=""/>
<sap:Service/>
</sap:Receiver>
<sap:Interface namespace="http://xxxxx.de">hartgeldbest_KT_async_out</sap:Interface>
</sap:Main>
Is it possible that the receiver is overwritten due to the Content Conversion? Because if I set my Message Protocol to "File" the receiver determination will work.
Any idea?
Thx
Khadim

J2ME WMA wireless messaging api

Similar Messages

Maybe you are looking for