Version concepts - how do you handle versions?

[frank_wagner2]

Hello,

<br><br>

this questions is primarily for ISV, as customers may not have this problems...<br>

<br>

Background:

<br><br>

I have a software product that I now have to migrate to NWDI. I read a lot of documentation how to handle the release cycle but I never found a solutions for the problem that you have to consider SAPs J2EE Versions as base. <br>

For example: my application is a simple EJB App that will be migrated from standalone java to a J2EE integrated version. I'm currently developing on a J2EE 7.01 system, but app should be compatible with J2EE 7.00. So my SCs Version is 7.00 as it builds using J2EE 7.00 SCs.

<br><br>

So for at least next 5 years (I think SAP j2EE Release 7.00 is supported until 2015), I will have to maintain it after release so I will have a maintainance track for the SC Version 7.00 and every new feature has to be implemented via Support Packages (as SAP has done before the EHPs).

<br><br>

In parallel I have to provide a new version at least for release 7.10. Following the standard document this would be the "next" release of my product so I have to develop it in dev track. But in reality it is not really a new release of my product but just a "compatible with J2EE Server X" release. My release updates are the support packages...

<br><br>

So here comes the question:<br>

how do you handle the versions of your product? Do you have a own version number and just a separate track for every basis release? How do you reingrate the changes of a release to the different basis release versions?

For SAP'lers: how is this handled internally at SAP? I think some products just have a common code base (for example cannot imagine that you really develop a new release version for every EHP) and are only released as separate version because it is easier to define a stack if every component has the same basis release dependency.

<br>

Thanks,

Frank

[ErvinSzolke]

Hi Frank,

can you please close the thread if this answers your question?

Thank you!

Best Regards,

Ervin

[frank_wagner2]

Hello,

no solution found here but I will close the thread.

I now use a development configuration for each basis "release" compatible with.

Thanks,

Frank

[ErvinSzolke]

Hi,

I believe you'll welome the following two blogs:

JDI Software vs. JDI Content -- /people/marion.schlotte/blog/2005/10/25/jdi-software-vs-jdi-content

SAP Network Blog: How to Migrate Developed Software Components to a New Release in NWDI -- /people/guenter.schiele/blog/2007/02/12/how-to-migrate-developed-software-components-to-a-new-release-in-nwdi

Best Regards,

Ervin (http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29Home)

[Former Member]

Hi,

Firstly you have to decide on which application server you want to deploy your application , on 7.0 or on 710?

You just need to create a sofware component in the SLD defining your application and the dependent components for it.

Generally if am developing on 700 app server then i will need to add the SAP-JEE , SAP_BUILDT and SAP_JTECHS 700 release components as the dependent component list, this is bcoz i get the classes so that i can use in my component. If you want to use 710 then define SAP-JEE , SAP_BUILDT and SAP_JTECHS 710 components release.

Then create a track with your custom software component which you have created. Then import the DC in your NWDS then from here on you can follow normal development.

Secondly, Say your software component has to be deployed on the other system after x number of years. Then in for that particular system while defining the new software component you need to add this old component as the dependent component and then check-in this archive so that you can use the exsisitng classes.

Hope this helps you little.

Regards,

Vamshi.