on 06-15-2009 11:29 AM
hello!
i publlished my RFC in a web service way.
I used the SOAMANAGER transaction as described in documentation , but when i try to use link "Open Web Service navigator for selected binding" page cannot open and i see follow error:
Service cannot be reached....
if i try to test web service from a soap client nothing appen and i have timeout error.
something missing??
thanks
alex
Hi,
The Web Service Navigator runs on a Netweaver J2EE stack.
If you use single stack abap system, you don't have a Web Service Navigator.
The good news is that, if you have a J2EE stack on an other system, you can use it.
If your web service is properly configured with SOAMANAGER, it is supposed to be possible to call it from any soap client program.
Regards,
Olivier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Olivier,
I join this message because I have similar problem.
We have 1 machine (single stack ERP6 NW SP17) + another machine (dual stack BI NW SP17 + Portal).
In the EntreprisePortal, we connected successfully the ABAP stack of BI and we face now the following open issues:
- SSO ERP (mach1) to Portal (mach2)
- transaction SOAMANAGER in ERP (mach 1)
- in SICF, we test the service /default_host/sap/public/bc/sicf_login_run and it does NOT WORK.
Is this all related to each other?
Regards,
Philippe
Edited by: Philippe Herau on Sep 18, 2009 6:55 PM
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
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.