Application version management

[p_willems]

Hello,

After reading a lot of threats here I have a global picture of what is possible. I explain what I have and what I need wich is not working for me.

This is what I have: (Netweaver 7.0 SP15 - Java WebdynPro developments)

1. Created a Product and software component in the SLD (Say Prod X version 1.0)

2. Created a track in the Landscape Configurator (say ProdX10; only Development runtime system)

--> Did some developments, created activities, checked in and activated.

3.Created an anther Product and software component in the SLD (Say Prod X version 2.0)

4. Created a track in the Landscape Configurator (say ProdX20; only Development runtime system)

5. Create track connection (type Transport) between the created tracks (Source ProdX10 and target ProdX20)

What I want to realize is the following:

The source from track ProdX10 must be in track ProdX20 for continuing the developments in the new version.

The results till now:

--> Tracks are visible and worked. (Also visible in Developer Studio).

--> Can work on the created track

Problems (and what I want to happen:

--> How can I import the source from track ProdX10 to ProdX20. I never saw an option to import the source.

Maybe I do it totaly wrong, can somone advice.

Regards,

Patrick Willems

[Former Member · Accepted solution]

Patrick,

For transporting your (developed) code between the 2 tracks you can use "track connections".

There are 2 types: "repair" and "transport".

The first one (repair) transports your code after import in consolidation; the second one (transport) transports your code after the "Approve" action unther the approval tab of the CMS.

Hope this helps.

Regards,

Alain

[p_willems · Accepted solution]

Hi Alain,

If I understand you correctly, it's necessary to have a consolidation system defined in your track.

Till now I do not have that system.

If I configure that track ProdX10 en track ProdX20 has a consolidation system, the scenario I explained should work.

Regards,

Patrick Willems

[Former Member · Accepted solution]

Patrick,

You do not need a physical system for your consolidation, this is a phase in the CMS transport mechanism where a test server could be attached, as you can attach a physical server to you Test and Production phase too.

You could define tracks without any runtime systems if you want, but I don't have a partical requirement for that: it leads to more CMS administration.

To be able to transport your complete SCA file from track 1, you need to have it approved in the Approval phase.

From the history view of this phase you can than transport it to your track 2 manually (if you wish).

Personally, I would use the track connections.

Regards,

Alain

[p_willems · Accepted solution]

Alain,

I followed your suggestions and did the following:

Track ProdX10 already exists. (In SLD software component name PRODX10 with dependencies: SAP-JEE, SAP_BUILDT, and SAP_JTECHS).

In SLD created new product and software component version PRODX20 with dependencies: PRODX10.

Created new track: ProdX20. with only development runtime system checked.

Created new track connection between PRODX10 and PRODX20 with type transport.

On the assembly tab I clicked the button Forward from History, put in the Prod20X as target track and pressed the button forward. I imported the component in the development tab of track Prod20X. Also I imported the component in the consolidation tab. Till so far no problem.

But when I start SAP NETWEAVER DEVELOP STUDIO and import the development configuration, I don't see the source for the development components which are build in track ProdX10. I tried several times stopping and starting the developer studio, refresh, Re-Sync DCs and Synchronize DC projects without any luck. I can't see the developments.

What am I missing?

Regards,

Patrick

[Former Member · Accepted solution]

Patrick,

To have a newer version of your SCA's the name of the SCA's must be the exactly the same. Versioning of products and SCA's is done in the SLD with version numbers.

Please look at the following blog [https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5834] [original link is broken] [original link is broken] [original link is broken];.

I think this will help to solve your problem.

regards,

Alain

[p_willems · Accepted solution]

Hi Alain,

I tried your solution description but still no luck.

Created a product in the SLD with the same name, but a different version. That works.

In the CMS I created a track, track connection etc. Still ok.

In the track of the previous version I clicked the button forward from history, filled in the target track and pushed the button forward.

I could see the import in the development tab and inported the sca's. Till now no problem.

But when I go to the developer studio and inport the remote configuration, I don't see the source code.

Also on the DTR the source isn't there for the newly created track (workspace). Only the SC folder.

I think I forget something, but what?

In the blog of Guenter Schiele on point 6, he's talking about transport all sources from your old track to the new track. How is this done. By the transport connection?

Regards,

Patrick Willems

[Former Member · Accepted solution]

Hi Patrick,

As you added your develople SCA's to the track definition in the landscape configurator of the CMS, did you select "Source and Archive" for the package type of the SCA?

The transport mentioned in point 6 is either manually or through a track connection automatically.

Regrads,

Alain

[p_willems · Accepted solution]

Hi Alain,

I did not explicitly select it, it's automaticly selected. Also the check 'Developed' is automaticly checked.

So I think thats not the problem. Something else is, but what?

Regards,

Patrick Willems

[p_willems · Accepted solution]

Hello,

Can someone respond to my question earlier.

In the track definition in the landscape configurator of the CMS, I select "Source and Archive" for the package type of the SCA.

I still have no source code in SAP NETWEAVER DEVELOPER STUDIO.

Waht can I do to have the sources in my developer studio?

Warm regards,

Patrick Willems

[Former Member]

You must use CMS to move your developments to the Approval stage in the 1.0 track. Once Approved, they will appear in the import queue of the Development stage of the 2.0 track.