on 03-04-2014 5:24 PM
Hi All,
I am trying to configure notifications from NW to my local system.Anyhow RFC type 'G' (HTTP Connection to External Serv) is giving Error - ICM_HTTP_CONNECTION_REFUSED. I have configured the listener in my local machine.. I tried with httptrace & mambrane.
I tried with httptrace & mambrane one by one.. cann't not use both as it give error - port 8000 is already in use (So it is listening to port)..
Following are the steps I am trying:
2. Tcode – SMICM setting showing port for HTTP:
3. HTTP Trace running on my system:
4. After this I am trying to run RFC from NW server and it is giving – Error - ICM_HTTP_CONNECTION_REFUSE
5. I also tried with membrane – following is the setup for this.. (but not running both membrane and httptrace simultaneously, As I got error port # 8000 is in use )
6. RFC error Log in Tcode - SMICM:
Please check the steps and let me know what I am missing it setting up communication.
Regards,
Rajesh
Hi All,
I explored more on the notification and able to push notification from my ECC to NW server. Now message are in my NW queue but getting error out due to error.
1. Created a RFC in ECC - BEP_BGRFC_DEST and getting message in outbound queue with same name.
2. Created a RFC in NW- IWFND_ODATA_PUSH and it is receiving messages from ECC in inbound queue with same name.
3. In gateway messages are getting error out.. following are the error (/IWFND/ERROR_LOG):
Maybe gateway server is not finding the target system or something else...I have created the RFC for external system not sure where to assigned it.. Please assist me in fixing the error and let me the next step to follow..
Regards,
Rajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rajesh,
I am not sure about this specific error but in principle what you are trying to achieve might not be a good way to go productive. You are trying to push the gateway notifications out to the mobile devices here. The problem with this approach is a classical one and can only be resolved by some man in middle approach. Most fot he device vendors like Apple provide their own services like APNS which can be used by the man in the middles server to enable a push from backend systems to device applications.
You can use SAP Mobile Platform to achieve this.
But in case you can live with not immediate delivery of the notifications then I would suggest that you code your client to read the pending notifications from gateway everytime it starts. This will allow you to achieve similar use case but when the application is not running on device the notifications won't be pulled. If your client is a browser then its no use trying to push anyways.
Search of Notification/Subscriptions or look for the code in Flight Data Model on your gateway.
Cheers,
Vikas
Hi Rajesh,
Definitely if you want to enable Push notification for a mobile, you would have to use any of the available services of Apple APNS or Google's GCM for productive use as pointed out by .
Now for the testing purpose:
The error clearly says that the RFC destination is not found which means the format of the delivery address is not correct or the host/port maintained in the RFC destination does not correspond to the delivery address that's present in the subscription.
Secondly, The RFC destination should be able to ping the target server or in your case HTTP Trace/Membrane. Before doing connection test, start listening to the port in Membrane/HTTP Trace. You should be able to receive the ping. If not, then there's an issue.
Delivery address must have one of the following formats:
a) urn:sap-com:channel:<RFC destination>:<request URI>
b) http://<host>:<port>/...
c) https://<host>:<port>/...
In all cases an RFC destination must exist on Gateway either having a name <RFC destination> as in the option a)
or targeted to the <host>:<port> as in options b) and c).
Can you please verify above points?
Best regards,
Aakash
User | Count |
---|---|
77 | |
9 | |
9 | |
7 | |
6 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.