Change SWCV in Technical System

[itabhishek9]

Hi SDNites,

I have got SWCV attached to the Technical system and the same has moved across the landscape. Can you tell me if I change the SWCV atatched to the Technical system now, will that create any problem for te existing developments.

If yes is the relatioship tightly coupled and cannot be modified once set up.

Regards,

Abhishek

[pvishnuvardan_reddy]

Hi Abhishek,

By changing SWCV, if you mean removing of SWCV attached to the TS, then I guess it will create inconsistency for the interface at runtime since ID part fetches values from SLD.

It's just like linking SWCV to the corresponding TS, if the link doesn't exist then it might create problems for the interface run.

Regards

Vishnu

[itabhishek9]

Thanks Vishnu for the response.

Yes I mean if I change SWCV attached in TS from X to Y, then what would be the impact.

Also as you have mentioned that ID refers to SLD. ID requires only Service Interfaces and Operation mpping from ESR which in turn is linked to SWCV. Also it is possible to include Service interfaces present in different SWCV. So my understanding is changing SWCV in TS should not cause the problem. But to be sure I need some more views.

Regards,

Abhishek

[pvishnuvardan_reddy]

Hi Abhishek,

Basically the change of SWCV mainly linked to ESR part since ESR objects are developed under it. If you can replicate the objects under the new SWCV, then there won't be any issue for ESR part concern.

Coming to ID part, since the ID objects are dependent on SI, Operation mapping, if you can assign the new SWCV to the corresponding TS, then there won't any issue with the ID part.

Please make sure that, all the environments are in sync about this setup.

Regards

Vishnu

[RaghuVamseedhar]

Abhishek,

AFAIK, there will be no impact changing underlying TS.

SAP PI ID is will take only business system (transport groups) from SLD.

[former_member184720]

>>> If you can replicate the objects under the new SWCV, then there won't be any issue for ESR part concern.

I suspect it should have impact even if we copy the objects to new SWCV as all the objects still be pointing to the older SWCV.

sender interface/ operation mapping & inbound interface all would be pointing to older SWCV and at runtime.

It's not just about interface name but also depends on SWCV ID as i believe at run time PI verifies this.

@Abhishek :

I agree with Vishnu that there could be some impact if your configuration objects are pointing to older SWCV.

You might want to remove SWCV reference in configuration object or regenerate them.