Maintain Web Services in PI after refresh

[Former Member]

Hi All,

We just had a situation where in our mirror system had been refreshed from the production system. This had caused all the web services to point to production rather than the corresponding mirror. We were therefore wondering if there qas any way by which the WSDL's could be excluded from the refresh activities or if there was a table at the backend where all the WSDL URL;s will be maintained for every system.

Any suggestions on this front, will be highly appreciated.

Thanks.

[Former Member]

It depends on what is meant with the "refresh" activities:

1. If only the objects are transported, you can change the Adapter Metadata from both source and target. Open the communication channel metadata (the "Choose Metadata" button is right to the adapter type input help button), find the field that should not be modified on the transport and add the tag

<Flag>nonTransportable</Flag>

within the attribute. This should prevent the value from being overwritten.

2. There isn't any specific table for holding these attributes, and it is not recommended to manually change it on the database. If you need to perform a refresh on the whole server, including data tables, I would do the following:

a) Export all objects that should be maintained on the "mirror" system;

b) Perform the refresh from production;

c) import the objects again and replace with the objects that came from production system.

[Former Member]

Hi Lucas,

Thank you for your response.

If we consider your second option, in case of a total copy being made of the production environment into the mirror environment, do you think it is possible for web services specifically to be first exported and then reimported after refresh?

Could you or any one else please highlight on this.