cancel
Showing results for 
Search instead for 
Did you mean: 

How to quickly test custom developments in SAP NetWeaver

Former Member
0 Kudos

Hi,

We are upgrading our NW 7.0 to version 7.4 and our eCommerce 7.02 to version 7.32. We are also using NDWI to make our custom developments and our deploys are made using converted .sda files. Those files are installed via command line by another team and sometimes it takes too long. We would like to know if there is a way for us to test any change/development made on the source code (for example on a .jsp file) without having to constantly send an .sda file for deployment.

Thanks in advance

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member198633
Contributor
0 Kudos

Hello Pedro,

In NWDS you can also go for a local build and direct deployment option, which completely bypasses NWDI. You just have to add the target AS Java system (eg: in NWDS' MMC perspective) to which you would like to deploy and NWDS will trigger direct deployment.

But this way you lose the benefits of NWDI, which is the ideal way to facilitate team development.

Best Regards,

Peter

Former Member
0 Kudos

Hi Peter,

And can we quickly deploy our changes in a remote NWDI managed by another team? Does we have to always send them the sda file with our code changes, our there's another method for us to directly deploy on that remote NWDI?

Thanks in advance,

Pedro

former_member198633
Contributor
0 Kudos

Hello Pedro,

To clarify, NWDI (NetWeaver Development Infrastructure (NWDI) - Java Development - SCN Wiki) is for team development. From NWDS tigger the (central) build and automatical deployment on the target system. In NWDS there is an option to deploy the target J2EE engine directly (this bypasses NWDI).

If you have 2 separate NWDI systems, the archives need to be exported and imported manually. There is no easier way than the manual export/import.

Best Regards,

Peter

Former Member
0 Kudos

Peter,

We only have 1 NWDI system, but this is a remote system managed by another team. Can we somehow develop on this remote system, see the changes we make, without having to always create the sda file and send it to be deployed by that team?

Best regards,
Pedro