Question

4
Replies
198
Views
 Veera Kishore Babu Swarna (VeeraKishoreS)
Wellcare
Integration Architect
Wellcare
US
VeeraKishoreS Member since 2016 3 posts
Wellcare
Posted: April 17, 2018
Last activity: June 19, 2018
Posted: 17 Apr 2018 14:34 EDT
Last activity: 19 Jun 2018 16:28 EDT
Closed
Solved

How to maintain Version Controlling in Pega for Services? This is to get backward compatibility

Hi All, We have requirement to maintain versioning for Pega services. This is to get the backward compatibility for the consumers of pega services.

Consumers should be able to call based on versions and not always the latest wsdl.

Thanks,

Veera Swarna

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 3 years ago
Posted: 17 Apr 2018 15:33 EDT
Akshay Sawai (AKSHAY)
Cognizant Technology Solutions
Lead System Architect
Cognizant Technology Solutions
CA

The service version is control via Service package's access group setting. If you keep separate service package name then you would be able to achieve it. However if you change service package name then your end point url will also change. Explore this option if this meets your requirement.
Posted: 3 years ago
Posted: 18 Apr 2018 9:26 EDT
Veera Kishore Babu Swarna (VeeraKishoreS)
Wellcare
Integration Architect
Wellcare
US

Hi, We already tried this option, but its not working the way how versioning works. If i just change the end point url to the existing request, its still going and hitting the old service package. Hence, its not giving the new elements added in the new version.


 


Thanks,


Veera Swarna
Posted: 3 years ago
Posted: 18 Apr 2018 14:50 EDT
Akshay Sawai (AKSHAY)
Cognizant Technology Solutions
Lead System Architect
Cognizant Technology Solutions
CA

If I understood it correctly then it seems to be cache issue. You can perform below steps to resolve cache issue.


  • Save Service package instance

  • Clear Rule cache from SMA

  • Delete Rule Extract Marker file (on each node) and restart your server

You can perform above steps and see if it helps.

Accepted Solution

Posted: 3 years ago
Posted: 4 May 2018 16:54 EDT
Veera Kishore Babu Swarna (VeeraKishoreS)
Wellcare
Integration Architect
Wellcare
US

Changing Service package name is changing many elements in the wsdl and this is not being treated versioning.


We should have a way where we can map the same service package to different access groups and this should change the url based on access group.


In that way we can achieve version controlling or backward compatibility which is not possible in Pega today.


We can close this thread.


Thanks,


Veera