WSPUBLISH and SOAMANAGER

Hi,
I have published enterprise services from ECC successfully with WSPUBLISH. Now I want to try it out with SOAMANAGER. But when I publish an enterprise service in SOAMANAGER (Technical Configuration -> Publication Administration) with the following settings:
Service scope: All services
Publish Information: Service definitions and endpoints
[x] Force publications
And the publishing was failed and it returned the following messages:
Error retrieving Services Registry (SR) version information.
Error retrieving physical system from Services Registry
Exception raised during phyical system publication. Code .
How could this happen? Since I had no problem with WSPUBLISH.
Regards,
Joon Meng

Hi Rossen,
Thanks for the effort. I have checked the SAP Documentation for NetWeaver 7.0 EhP1 you mentioned
in the last post. But it is stil different from my SOAMANAGER. So I resort to the documentation
for NetWeaver 7.0, and I have found the following procedure:
Establishing a Connection Between the ABAP Back End and the Registry
1. Create a logical port for proxy class CO_ESREGISTRY_WSSI in transaction SOAMANAGER under Business Administration ® Web Services Administration ® Consumer Proxy.
2. Open the Call Parameters tab.
3. Enter the following in the http Destination field: http://<hostname>:<port>/ESRegistryWS/BasicAuthConfig?style=document
You can also enter an RFC destination in this field.
4. Call transaction WSPARAM.
5. In the first column, enter the name of the registry.
6. Enter any number in the Version field.
7. In the Logical Port field, choose the port you created before.
8. In the Primary field, select the value True if it is to deal with the standard registry.
To my surprise, even with this documentation, I could not proceed to step 2, because I could not
find the "Conumser Proxy" in step 1 and "Call Parameters" tab in step 2.
I wonder if there is much difference between publishing services with SOAMANAGER and WSPUBLISH.
If not, I think I should use WSPUBLISH in this case.
Regards,
Joon Meng

Similar Messages

SICF and SOAMANAGER for using enterprise services

Hi,
I need to publish enterprise services from my ERP backend to the Services Registry on my PI server.
According to the tutorial (https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2), I have to first activate the services in SICF and create endpoints for the corresponding services in SOAMANAGER.
I suppose, only after that I could publish the configured services in SR using WSPUBLISH, right?
Now, if let say I want to publish all enterprise services in my ERP backend, I have to select all the services in the WSPUBLISH, as stated in the instructions of the tutorial (http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/108ef7ba-8abd-2a10-f787-d5f29c5f1b88). But the problem is, do I need to configure every single enterprise services using SOAMANAGER? If not, only the service definitions would be published?
Hopefully someone could clear my doubts.
Thanks.
Regards,
Joon Meng

Hi Venu,
I could not see any nodes for end points in the SICF. So I manually created a service endpoint in SOAMANAGER and then published it to the Services Registry via WSPUBLISH. However, I was surprised to see two endpoints (one was created by me) in the Services Registry.
The service is "ECC_PURCHASEORDERCRTRC" and there are two endpoints for it in the Services Registry:
1. ECC_PURCHASEORDERCRTRC_Binding (created by me)
2. PurchaseOrderCreateRequestConfirmation_InSoapBinding
When I open the service in SOAMANAGER and navigate to the "Configuration" tab, I only see the endpoint from me (with "Manually Created" for Creation Type).
I wonder if the 2nd endpoint was created automatically during the service publishing?
Regards,
Joon Meng

Services created with WSADMIN and SOAMANAGER

Hello gurus!
Ihave a question about the WS created in the transaction SOAMANAGER. we have 5 webservices to operate our system, 4 of them were created with WSADMIN and one with SOAMANAGER. The problem is that in EPP we only can download the WSDL of the WS created in SOAMANAGER, and the other four cannot be found. Do we need to re-create them in SOAMANAGER in order to get them in EPP??
Regards IA

Hello,
For old Web service definitions, if you have created End Points using WSCONFIG, you do not need to recreate it in SOAMANAGER. In WSADMIN, once you place cursor on your service, you can download WSDL using WSDL icon in Application Tool bar.
Thanks,
Venu

SOAMANAGER - ECC 6.0

Hi
I am trying to test a web service using SOAMANAGERon ECC 6.0, using link on SDN http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-e64eeda1ff2&overridelayout=true
Configured SICF and SOAMANAGER, and i click on "Open WSDL document for selected binding" to get URL
Next step i click on "Open Web Service navigator for selected binding" and give the URL from step above
I receive the following message
Cannot download WSDL from http://lvdpe01.erp.intra:8000/sap/bc/srt/xip/sap/ecc_purchaseorder003qr/200/ecc_purchaseorder003qr/ecc_purchaseorder003qr_binding: Invalid Response Code: (404) Not Found. The request URL was:"http://lvdpe01.erp.intra:8000/sap/bc/srt/xip/sap/ecc_purchaseorder003qr/200/ecc_purchaseorder003qr/ecc_purchaseorder003qr_binding". Check, whether the URL is correct, and the Web Service that you are requesting is up and running.
Any help is much appreciated
Cheers
Edited by: Hasit Vaishnav on Sep 21, 2011 4:41 PM

Hi
I checked the port/host name via transaction SMICM > go to services> and HTTP is on 8000 and hot name is lvdpe01.erp.intra
Please can you explain a bit more on the third component "wsdl service hosted location "
Also just for info i am simualting this on ECC 6.0 and no PI involvement at the moment
cheers

SOAMANAGER: RFC connection uses 'anonymous' PSE?

Hi Everybody - We want to configure our ERP 6.04 system to consume an external web service. The web service will be accessed by an ABAP program (not by the end user). We want to use SSL and a service userid/password.
If the developer uses the supplied WSDL and tcodes SE80 and soamanager, the automatic configuration generates an RFC connection that does not contain userid and password and uses the SSL Client Standard PSE (SAPSSLC.pse). If the developer uses a manual configuration in soamanager in order to specify basic authentication in addition to SSL then the RFC connection will contain the userid/password, but it will also specify the 'anonymous' PSE (SAPSSLA.pse).
1. Does the above sound correct?
2. Are there any real issues with using the 'anonymous' PSE instead of the standard client PSE?
3. Will the 'anonymous' PSE present a problem when we go to QA and production (which will use CA signed certificates)?
4. Is there a way to specify SSL with userid/password and get the RFC connection to use the standard client PSE?
Thanks for your help - points awarded for helpful input.
Jeff

Hi Jeff,
Yes, you are right automatic LP generation can't change via change in RFC destination but manual LP can be changed via RFC destination.
See SAP help:http://help.sap.com/saphelp_nw70/helpdata/en/5b/2e423c0bcc4a7ee10000000a114084/content.htm and read point 3 and 4 carefully.
STANDARD = "Mutual Authentication"
Anonymous = "Only server Authentication"
Make sure you configured/activated correct security setting as per following document:
Configure ABAP AS: http://help.sap.com/saphelp_nw70/helpdata/en/65/6a563cef658a06e10000000a11405a/content.htm
Workaround I'll suggest that create another LP manually with exact settings you can see in automatic created LP and then change generated RFC destination (you can change manually generated LP's RFC destination).
To use standard client SSL you need to configure mutual trust between consumer and provider (I haven't configured it myself).
I'll investigate more and come back to you.
Regards,
Gourav

No result while creating a service consumer with Web Service Wizzard

Hi,
I've tried to create a service consumer with Web Service Wizzard in SE80 by using URL/HTTP Destination but nothing happens. After the popup with logondata for the WSDL I get the CRM start screen and nothing has been created in the given package.
technical details:
I use a CRM 5.0 system with SP15 (SAPKB70015).
I created the provider service at a 7.10 system with SP5 (SAPKB71005) via SPROXY, SOAMANAGER and WSPUBLISH and get the WSDL-URL from Service Registry.
The Service Registry of the 7.10 system serves as central Service Registry.
Has anybody an idea ?
Christoph

Guy,
Thanks for your reply.
This problem has been solved. Since I haven't turned on everything that to use transaction SOAMANAGER needs. After complete the switch-on works, the problem never happens again.
Thanks again.

Endpoints not being created

Hi All,
I am using Netweaver CE 7.1 and SAP EHP1 for Netweaver 7
I believe the endpoints would be created automatically whenever you cretae a proxy in SE80 for the service interface that you have created in ES Builder.
I created Service Interface with the associated Message types and the Data types and published the WSL file from ES builder..
In SE80, I got the interface that I created and created the proxy, added my code in the implementation class and then activated,
In service registry, I can see my Service Interface but with the status Modeled.
My question is, how can we create the endpoints, shouldn't this be created automatically.
In the Forums, all I see is transaction SOAMANAGER, WSPARAM,WSPUBLISH and so on which are obsolete.
Your help is much appreciated.
Cheers,
Sathya

Hi,
when you create Web Service definition with wizard, you have to define configuration of the Web Service in each client. This is done using transaction SOAMANAGER. In Business Administration tab, select Web Service adminstration and search for your web service. Then select the button Apply Selection. Now you can see the Configuration tab where you can create End Points. You can define multiple end points with separate security requirements to be consumed by different consumers.
Click on the option 'Option WSDL document for selected binding' to get WSDL.
http://help.sap.com/saphelp_nwpi711/helpdata/en/33/06820d9d174c2884576bd78ac5629d/frameset.htm
http://java.sun.com/developer/technicalArticles/WebServices/soa/
Thanks,

WSDL without endpoint in Services Registry

Hi,
I have successfully configured an enterprise service from ECC 6.0 by following this tutorial ([Configuration of Enterprise Services using SICF and SOAMANAGER|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/20b723f8-a422-2c10-aca5-fe64eeda1ff2&overridelayout=true]). After the configuration, I published the enterprise service to the Services Registry using WSPUBLISH.
However, when I tried to consume the service in Visual Composer, I got a connection error. Later, I discovered that it was due to the binding WSDL generated in SOAMANAGER in which the endpoint port was automatically set to 443 instead of 8001 (my http port). Luckily enough, I have found an identical problem posted to SDN forum ([soamanager referencing wrong port number in wsdl document |soamanager referencing wrong port number in wsdl document;). From there I learned that an SAPNOTE 1263112 must be uploaded to my ERP. Now, this problem is solved.
Nevertheless, after I have built a VC model that consumes the service, which is now found in the Services Registry, deployed and run it, I got this error message "Error in connection: Could not execute Web service, consult your administrator". To investigate the source of the problem, I copied the URL of the WSDL generated in SOAMANAGER from the link Open WSDL document for selected binding and created a logical destination in NWA for the direct consumption in VC. This time, the VC model worked!
This lead me to think that the problem lies in the binding WSDL in Services Registry. So, I checked the SR again and found that the URL for the binding WSDL in the "Endpoint" tab is different from the one in SOAMANAGER:
1. In SR
http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/binding/ws_policy/document?sap-client=800
2. In SOAMANAGER
http://myserver:8001/sap/bc/srt/wsdl/bndg_4AAD0B64E0BC0263E1008000C0A8A53D/wsdl11/allinone/ws_policy/document?sap-client=800
The binding WSDL in SR does not contain the endpoint. However, the endpoint is shown in the 2nd column "Target Address" of the endpoint table in "Endpoint" tab.
To summarize, I could not consume service that was configured in SOAMANAGER and subsequently published to SR. But, with the WSDL in SOAMANAGER, the service could be directly consumed.
Does anyone have idea about this problem?
Thanks in advance.
Regards,
Joon Meng

Hi,
Usually endpoint in SR is published as per SOAMANAGER (allinone/ws_policy/document?sap-client=800). Try to republish service again using "WSPUBLISH" with endpoint and chose "force publication" option.
You can also publish service using url directly from SR (goto "publish" tab).
Regards,
Gourav

SAP PI conceptual best practice for synchronous scenarios

Hi,
 Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
 We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document best practice guidelines for our internal development team to follow.
I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
 Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
 Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
 My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement. Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
 1) Use SAP PI Integration Directory. I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly. In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on. When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses. We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message. Extra work but seemingly for improved visibility of the process. I'm not suggesting this is the correct long term approach but states where we are currently.
 2) Use the Advanced Adapter Engine. I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support. I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc.
 3) Use the backend system's SOAP runtime and SOAMANAGER. Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system. [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.] The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable. My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review.
 Queries:
 I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
 I'm curious to understand SAPs intention with these options -
 - For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required?
 - Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
 - Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3? I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
 Thanks for any advice, it is much appreciated.
 Alan
Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

Hi Aaron,
I was hoping for a better more concrete answer to my questions.
I've had discussion with a number of experienced SAP developers and read many articles.
There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
- Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
- It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue. You can always turn on monitoring in SOAMANAGER to trace errors if need be.
- Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor. For example, we have some systems on Netweaver 7.0 and other on 7.1. As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
- We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment. Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
Hope these comments may be useful.
Alan

Adding field to repository structure leads to syntax error in webservice

Hello there,
I have added a field to a structure that is used as a parameter type in a customer function module which is part of a function group which is the endpoint of an enterprise service.
I would have expected the webservice where this structure is used to have been updated automatically. But no: When I check the service definition, I get an error message that the type is missing the new field. And sure enough, in the types tab of the service definition (in se80) the new field has not been added to the type (listed under "original types"! - which is kind of misleading, as obviously it is not identical to the repository type any longer).
I'm at a loss here - how can I update the service definition and publish a corrected wsdl file, which includes the added field in the type description? I have looked many places in se80 and soamanager and sproxy, but to no avail. Must I delete and re-create the entire enterprise service?
This is in SAP Netweaver 7.01 and no XI.
-- Sebastian
Edited by: Sebastian Millies on Jul 8, 2010 11:36 AM
unmarked as a question, because answered in [this thread|The specified item was not found.;. Sorry I saw this too late. Anyway, when using the "check" button, a dialog pops up asking whether the service should be updated. (This seemed not to happen when I was using the "check" context menu entry, by the way, but I cannot now exactly reproduce the condition).

Hi,
MAke sure there are no entries for application 03 in LBWQ, if you are using Queue delta update mode.
Make sure there are no entries for application 03 in Sm13, if you are using V3 unserialzied update mode.
You can do this by running collective run for applicaiton 03 in LBWE.
And also make sure there are no entries in RSA7 for DS 2LIS_03_BF.
Regards,
Anil Kumar Sharma .P

Web Service problem? Forbidden 403

Not sure why I'm getting this error when trying to run it in my ASP C# project.
The request failed with HTTP status 403: Forbidden.
Anyone have any insight on this? I'v

That seems to be the issues. I forgot to activate it in SCIF after it was created. It works now.
Now, can someone tell me what the difference is in creating a web service and SOAManager like this for a FM to import into say C# application versus just importing the RFC enabled FM into a project?
Reason I'm asking this question is that's how we were doing it before I found out this method to create a "actual" web service.
Before all we did was create the FM then made sure it's RFC enabled (seems like that needs to activated for WS also) then I would use the follow link to import it into my project:
http://******:8000/sap/bc/soap/wsdl?services=<< FM Name >>&sap-client=*

How to Consume Web Service?

Hi Experts,
I need to call a Function Module in the Exit.
In this Function Create to write the code to consume web service created by third party.
Then get the Data from there and uodate SAP
Can u plz help me with the Steps Involved in this?

Hi Mohsin,
Please chk this link once for consuming web services..
http://help.sap.com/saphelp_nw70/helpdata/en/bf/d005244e9d1d4d92b2fe7935556b4c/frameset.htm
http://help.sap.com/saphelp_nw04/Helpdata/EN/b4/6aae409567942ae10000000a155106/content.htm.
U shuld have authorizations for tcodes WSADMIN and SOAMANAGER for creating web services
Hope it will be useful..
Regards,
Lakshman.
Edited by: Lakshman N on Jan 13, 2009 12:06 PM

List service notifications web service

I'm not sure where to put this question - so I thought I would try here
We use service notifications. These are created through transaction IW51 and listed through IW58/IW59.
We have Microsoft Share Point as well.
The Share Point people are asking me - is there a web service or some existing SAP function to download the service notifications in XML so that they can load it into Share Point and produce some reports there.
I am not good yet at finding existing web services in SAP.
I searched through here: http://esworkplace.sap.com.
I also searched SDN and did a little debugging in IW58/IW59.
I also looked at SICF and SOAMANAGER.
I know how to create a web service and deploy it.
I have not been successful in finding existing SAP web services that may be there just not activated.
Any help on finding out where this might exist (if it does) - and also some help on how to find things like this in the future would be appreciated.
I get questions like this periodically from other groups asking if a web service already exists to download infromation from SAP and I haven't figured out how to find where they might exist.
Thanks.
Scott Overmeyer

You can retrieve the versions from the history option and re-generate it.

Where can I find customized rfc function?

Hi.
1.
I checked using wsadmin and soamanager, T-code wsadmin works forme.
What I'm considering is if I connect from remote side(exp: jco) , how can I find these methods?
2.
I create function via the se80, and can check in wsadmin, se 37.
Is it possible to create rfc enabled function in sap module area, and list in sap module area, such as normal functions in logistics, accounting module?
3.
I want to use this function to save record to database.
How can I write these script?
Is it possible to write script of function and table for me?
Thanks.

,.

Endpoints not found for service

hi
We are working on BPM Ce 7.2 where in we have uis in webdynpro java which calls a service from SR.
the service is workign fire from sr and soamanager.
however when we launch the application in portal it says that end point not found for that service.
We have checked Destination templates, system connections in nwa, and portal.
The same code is working fine in dev and wa workign fine in quality also until there was a ehp5 upgrade and refresh.
Has it to do anything with the upgrades and is there any other setting missing.
Any syggestions, please.
regards
Lavanya

Hello Varungulati,
I'm having the same issue, did you manage to solve this problem ?
Thanks,
Nadjia

WSPUBLISH and SOAMANAGER

Similar Messages

Maybe you are looking for