cancel
Showing results for 
Search instead for 
Did you mean: 

does NWDI actually work for end-to-end portal deployment?

Former Member
0 Kudos

I am looking into using NWDI for transporting portal content (iviews, roles etc) and portal code (par files).

Before doing that I would like to know what experts have to say about using NWDI for implementing portal transports. Has anyone used it in real-life? what works and what does not work when using NWDI with Portal?

According to SAP "NWDI is the strategic deployment tool for NW. A tight integration of the portal content development tools and NWDI is planned for a future release of NW".

One issue I see with the tool is that it requires a command line utility (sapmake_util) to convert EPA and PAR files to SDA and SCAs. That makes things difficult to manage as frequent deployments are needed. Can this conversion process be automated?

can NWDI be used to actually import portal content and par files into a target portal PCD? where in NWDI is the reference to the Portal target system?

thanks in advance for your comments and perspective.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello,

at the moment it is not possible to transport iviews over NWDI.

We are using NWDI for transporting WebDynpro objects. We had many problems to get our local development in the netweaver workplace into the track based NWDI.

Regards,

Alexander

Former Member
0 Kudos

Please look at this thread,

Points if helps

Former Member
0 Kudos

Hi,

I've asked some SAP consultants a year ago, and the recommendation then was that you can use it, but at the moment it was not recommened. I am not sure what has happened since, and there is need for an official SAP recommendation .

One of the problems is that the CBS (build server) doesn't have an understanding for portal applications and therefore you loose that extra functionality. So basically you can use NWDI for transporting the portal content ,but it will not have any understanding on what is being passed on.

The portal target system is defined in each NWDI track, where you enter connection properties for the SDM process (the SDM only understands .EAR,SDA and SCA files, and this is the reason why you need to repackage the par file in a SDA file). The repackaging can probably be very well automated using NWDS due to the fact that you can run executables from eclipse with the press of a key.

Regards

Dagfinn