cancel
Showing results for 
Search instead for 
Did you mean: 

Publish in SR

EdgarTabar
Participant
0 Kudos

Hi,

in my scenario: (third-party) SOAP --> PI 7.1 -->(SAP) ABAP Proxy

I'am ready and works (tested with the Test Configuration Tool).

Now I will test the scenario with SOAPUI. It is necessary to publish the webservice in the service registry?

Thanks

Accepted Solutions (1)

Accepted Solutions (1)

former_member184681
Active Contributor
0 Kudos

You can perform the cache refresh in transaction sxi_cache.

EdgarTabar
Participant
0 Kudos

In the transaction sxi_cache is all ok.

Is this the same like

http://<server>:<port>/CPACache/refresh?mode=full ?

Former Member
0 Kudos

Edgar,

CPA Cache is the Collaboration Profile Agreement Cache. You can refresh it. But the shortest way to do this for your scenario is to alter your communication channels with a dummy change e.g. in the description and activate it.

Regards,

Konrad

former_member184681
Active Contributor
0 Kudos

No, this is not exactly the same thing. See here for details:

http://wiki.sdn.sap.com/wiki/display/XI/SXI_CACHECommonErrors

Also make sure that all your objects are activated properly.

Greg

Answers (5)

Answers (5)

EdgarTabar
Participant
0 Kudos

Now it works!

I had a mistake in the comunication channel (sender)

In an asyn. scenario the quality of service is not best effort.

Now i changed it to exactly once and it works!

EdgarTabar
Participant
0 Kudos

But then I get the error message:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Aufruf eines Adapters

-->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>

<SAP:P1>Object ID 88ABE6A57E563B53AAB16484798D80A3 Software Component EDA02A7141AD11E1AD1EE5FC0A0A03CC</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Mapping program is not available in runtime cache: Object ID 88ABE6A57E563B53AAB16484798D80A3 Software Component EDA02A7141AD11E1AD1EE5FC0A0A03CC</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

The test with the payload works in the Test Configuration tool. There are no error messages.

Why is my mapping program not in the runtime cache? Can I refresh them? When yes, where?

Former Member
0 Kudos

Not neccessary for testing with SOAP UI.

Just click in your Sender Agreement and click on the menu tab of the Sender Agreement. Select display WSDL. There you will see the right address to load your WSDL into the SOAP UI testing tool.

former_member184681
Active Contributor
0 Kudos

Hi Edgar,

No, you don't have to publish your scenario in services registry to have it working or test it with SOAP UI. Just generate the wsdl file from the Sender Agreement and import it to SOAP UI and you're ready to test.

Hope you'll find this useful,

Greg

MichalKrawczyk
Active Contributor
0 Kudos

hi,

>>>Now I will test the scenario with SOAPUI. It is necessary to publish the webservice in the service registry?

no, you don't need to publish it there

Regards,

Michal Krawczyk