WSPUBLISH and SOAMANAGER

[Former Member]

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

[Former Member]

Hi,

As pointed out inprevious post, you need to setup connection between SOAMANAGER and SR.

>How could this happen? Since I had no problem with WSPUBLISH

SR setting is only configured in ERP thats why you are able to publish it using WSPUBLISH, since SOAMANAGER is running on Java stack you need to configure/maintain SR details here as well.

Regards,

gourav

[Former Member]

Hi,

thanks for the reply.

I have checked out the SAP Help ([Setting up the Connection to the Services Registry|http://help.sap.com/saphelp_nwpi71/helpdata/en/25/683fbe7e01407cb20995d10d71c895/frameset.htm]) as given in the previous post. But I could not follow the procedure due to the different user interfaces. For example, I could not find the "New" button which initiates the wizard for configuring a new connection. Instead, I only have buttons like "Append Row", "Insert Row". Besides, I could not configure other settings such as Authorization, Reverse Proxy mentioned in the SAP Help page.

So, I only did the setting till step 11 (including selecting CO_SERVICES_REGISTRY_FLAT_SI as the proxy class). After this, I tried to publish an enterprise service and got the error message "Access via 'NULL' object reference not possible." in the Web page. This time, I could not even see the publication log.

Then, I removed "CO_SERVICES_REGISTRY_FLAT_SI" entry from the proxy class column and gave it a second try. Now the situation is back to the original state as described in the first post.

Is this due to the difference in the version of the AS Java for the ECC? How can I check the version?

Thanks in advance.

Regards,

Joon Meng

Edited by: Joon Meng Goh on Sep 11, 2009 12:17 PM

Edited by: Joon Meng Goh on Sep 11, 2009 12:18 PM

[Former Member]

Hi,

The documentation in the link above is for a newer version, PI 7.1. This might be the reason for which you see a different interface and cannot follow the procedure.

I suppose you are using an earlier version of NetWeaver. Here is an earlier version of this procedure: [Setting Up the Connection to the Services Registry (for 7.0 EHP1)|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/25/683fbe7e01407cb20995d10d71c895/frameset.htm]

Hope this helps,

Rossen

p.s. If you work on 7.0 version, check this: [Publishing a Web Service|http://help.sap.com/saphelp_nw70/helpdata/en/44/cc8fd368c873dfe10000000a11466f/frameset.htm]

[Former Member]

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

[Former Member]

Hi Joon Meng,

While I am not an expert at this, here are two possible reasons for which the procedures might not work:

• The user account you use in SOA Manager is not allowed to perform every possible operation. If this is the case, you can try using an user account with more administrative privileges. Here is more info: [Authorizations|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/2b/07074155bcf26fe10000000a1550b0/frameset.htm]

• You are trying to perform procedures written for a particular product release on a different version of the product, either older or newer. Try finding which version you are using (for example, in SAP UI > System > Status), so that we can find which is the appropriate procedure.

Hope this helps,

Rossen

[Former Member]

Hi,

Have you done this: [Setting Up the Connection to the Services Registry|http://help.sap.com/saphelp_nwpi71/helpdata/en/25/683fbe7e01407cb20995d10d71c895/frameset.htm]

Hope this helps,

Rossen