cancel
Showing results for 
Search instead for 
Did you mean: 

webservice consumption in abap not working

former_member474221
Participant
0 Kudos

hi

I create a inbound SI in ESR and then implemented in ECC client 200...then i created a webservice out of it using soamanager.

i wanted to test this webservice ...so in the same client I created a Consumer proxy class and a logical port this consumer proxy...

then i wrote the below code-

create object oref

exporting logical_port_name = 'LP_WS1'.

.....

TRY.

CALL METHOD oref->si_in_syn

EXPORTING

input = itab

IMPORTING

output = out

.

CATCH cx_ai_system_fault .

CATCH cx_ai_application_fault .

ENDTRY.

here after the class is called i get sy-subrc = 0 ....however output parameter OUT does not contain any values..

also i put a external breakpoint and als hardcoded breakpoint in the implemenetation and it did not stop there also

Accepted Solutions (1)

Accepted Solutions (1)

jitendra_it
Active Contributor
0 Kudos

Hi Hema,

First test wheather ur connection is working or not . Open the Logical port in SOAMANGER. then find its corresponding

RFC destination. Then open the RFC destination in SM59 , click on "Connection Test".

If ur connection is working properly then It might be possible that the data u r passing in input , will not return any values.

Many Thanks,

Jitendra

Edited by: jitu188 on Feb 23, 2012 7:21 PM

Former Member
0 Kudos

Hi Jitendra,

What can I do if SOAMANAGER is not creating the RFC destination? Please help me. I have no idea.

Thanks.

jitendra_it
Active Contributor
0 Kudos

Hi Fabian,

When we create logical port using SOAMANAGER, it creates a RFC destination which points to URL of sending system.

What can I do if SOAMANAGER is not creating the RFC destination?

Pls let us know about error u r getting during creation of logical port.

Former Member
0 Kudos

Jitendra,

Well, everything looks fine, I go to SOAMANAGER and I create the logical port for the service consumer. But, when I go back to SM59, I don't see any RFC created automaticaly.

If I go to test the service consumer through SE80, I can choose the logical port as you can see in the screen shoot.

But when I execute the test for the service consumer I get this error.

So I guess is because I don´t have the RFC destination. I don´t know why SOAMANAGER is not creating the RFC.

jitendra_it
Active Contributor
0 Kudos

Hi ,

Here string '050..' shows RFC destination.  Please search this string in SM59 and follow the steps that i have mentioned in previous posts.

Former Member
0 Kudos

Jitendra,

That is the problem, I go to the SM59 and I dont see that RFC destination.

jitendra_it
Active Contributor
0 Kudos

Hi ,

Are u able to see the RFC destination in SOAMANAGER ???

After creating the port, just enter proxy and click on display logical port and check.

Former Member
0 Kudos

Hi,

I do that but I don´t know where I can see the RFC destination in SOAMANAGER. I guess you are talking about the "Internal Identification" in the logical port in SOAMANAGER, right?

I don´t know if is usefull but I am in a network with a proxy server. Thanks for your help

Fabian.

jitendra_it
Active Contributor
0 Kudos

Hi ,

See the SOAMANAGER screen shot of system which is  running on ECC6.0 Ehp 4.0

Here you can see the RFC destination is under the field 'Http destination' under the 'Additional tab'

Former Member
0 Kudos

Hi,

I checked the SOAMANAGER screen of the logical port of my system which is running on ECC 7.31 Ehp 6.0, but I didn´t see that "HTTP Destination" anywhere. Do you know why could that be? I know it could be because we are using a newer version, but maybe you know something else I can do.

Thank you.

Former Member
0 Kudos

Hi Fabian,

This behaviour (i.e. auto creation of an RFC dest when a logical port is created) has been discontinued in newer versions. I can't remember from exactly what version (or what the reason was) but I recall mentioning it somehwere in this forum previously. It was a handy feature to "connection test" your logical port.

In the newer versions however, you should have a "Ping" option when creating your logical port through SOAMANAGER, you could maybe try that?

Also, I had some issues with the vague error messages while trying the ping before. I managed to resolving it by playing around with the hostname on the endpoint (seen in SOAMANAGER while creating an logical port). I just alternated between hostname and fully qualified hostname & somehow got it working - there seems to be some variation on how the hostname is resolved depending on which system you work on.

Regards, Trevor

Former Member
0 Kudos

Hi Trevor,

Thanks for your answer. I will try to fix my issue with your advice. I will keep writing if I find the answer.

Answers (0)