Skip to Content
author's profile photo Former Member
Former Member

Best practices on version mgmt / versioning strategy of enterprise services


Could anyone share with me at high level what the version strategy they have used for maintaining enterprise services on PI 7.1.

Is there any best practices document from SAP on versioning strategy of Enterprise services using SAP PI 7.1.

Basically, i want my enterprise service version to be maintained for existing consumers when a new consumer needs an enhancement to an existing service.

Thank you in advance for sharing experiences in this area.

Thanks & Regards,

Renjith John Andrews

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 20, 2011 at 10:24 AM

    Hi Renjith,

    I haven't personally come across any best practice (documented) guides on versioning enterprise services but what I can offer are some suggestions...Ther are partner co-innovations (with SAP Co-Innovation Lab) that work as a solid governance layer on top, see this very useful blog with references: [] [original link is broken];

    Ideally, you would want to manage an Enterprise Service Lifecycle through it's phases (broadly design-time, runtime & change management) with a proper impact (compatibility for current consumers) analysis.

    Suggestions in no particular order:

    - Factor into account the communication pattern (e.g. is it query-response, request-confirmation etc.) for the enterprise service to be version stepped. This will help with the impact analysis.

    - Business might be driving the change so they would need to specify whether the new requirements should be mandatory or optional (from a webservice parameter context).

    - Document potential impact to current consumers (e.g. additional mandataory request parameter would impact all curent consumers).

    - Consider business requirements like should the existing enterprise service version co-exist with the version stepped one or should the existing go through pre-defined lifecycyle stages of support (for a certain period) --> then deprecation --> then deprecation. Business may even decide that they should co-exist indefinitely.

    - Also consider things like, if the requirement is for an additional parameter, can current consumer compliance be maintained by making the parameter optional (backward compatibility).

    - You may or may not have noticed, when SAP version steps a service operation in the standard delivered Enterprise Services, they add a "_V1" to the current operation naming convention & it's added to the same Service Interface. That's also another way to go about it. However, I've noticed strange behaviour when I've tried this approach. It seems like the endpoints need to be deleted & re-created in SOAMANAGER before the new operation becomes visible in the WSDL. Possible current consumer impact during endpoint deletion & creation.

    - You can also look at the Release Transfer functionality in the SAP ESR for your requirements.

    Just some suggestions.

    Regards, Trevor

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Robert Warde

      Hi Robert,

      Thank you very much for your response and like you i am a bit perplexed as to why SAP doesn't have a "Best practices document out there" on versioning. Version management of neterprise services is a vey pertinent topic in the ESOA area.

      We have created our first set of versions in this release and come next release, my approach as i think now, would be a combination of namespace with versions and objects with versions(depends on how much of a functionality change comes in the new version).

      Thanks & Regards,

      Renjith John Andrews

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.