Automated Deployment into Multiple Production Systems 

Use

The SAP NetWeaver Development Infrastructure (NWDI) allows you to specify one production system per track. The procedure described below allows you to supply multiple production systems from one source track.

The figure shows the connection from one track in which the application is developed to multiple tracks for production systems.

Prerequisites

·        You use the NWDI in the development scenario Scenario “Developing Components with the NWDI“.

·        You have configured a track for the development of your software.

Procedure

...

       1.      Start with creating one track for every production system, in addition to the track you use for the development.

You can do this for every production system you want to supply or – to work uniformly – for all production systems together: In the latter case, do not specify a production system in the track, in which you develop.

                            a.      When creating these tracks, leave the URLs for DTR and CBS empty.

(For these additional tracks no DTR workspaces and no CBS buildspace are required, because no development takes place there.)

                            b.      Enter all software components of the track, in which you develop, as Required Software Components. Under Software Components for Development do not enter any SCs.

A dialog window appears to inform you of the fact that you must maintain the dependencies manually: Ignore this message since you do not develop and build in this track.

                            c.      On the Runtime Systems tab page, specify the address of the production system for the Production system.

 

       2.      Set the Track Connections of type Transport of the track in which you develop (source track) to all tracks for the production systems (target tracks).

During the Approval step in the development track all selected software components are transferred to all target tracks (including those for the production systems).

For technical reasons, a transfer between tracks is always done via the import queue for the development system of the target track, even though no development takes place in a track, that is, no workspaces and buildspaces are configured. In this case, the import into the development system consists of nothing but the transfer to the approval queue of the track. 

       3.      Now transfer the software version to your production systems by executing the following steps for each of the tracks created for a production system:

                            a.      Import into the target track all software components in the Transport Studio on the Development tab page.

The SC(s) are now available for the approval step.

                            b.      On the Approval tab page, choose Confirm for all objects you want to copy into the production system– usually these are all objects in the list.

The SC(s) are available for the import to the production system.

                            c.      On the Production tab page, choose Import for all objects you want to copy into the production system.

The new version is deployed into the production system.

Result

All connected production systems now have the same software version.