Modified par file overwrites original one (Portal DC)

[Former Member]

Hi,

I'm trying to modify the masthead par file delivered by SAP using NWDI. I want to create it under our namespace so that it doesn't overwrite the original one but I don't see how to do it.

Here's what I've done so far: I created a Development Component of type "Enterprise Portal - Portal Application Standalone" and included the existing .par file. This DC is created with our own name prefix, and under a Software Component having our own vendor name. I changed the code, then DC Build, DC Deploy. Then when I access the portal I see the original masthead has been overwritten with my changes. It is always named com.sap.portal.navigation.masthead

Is there a way to change this name so that it doesn't clash with the original one? I've check in the portalapp.xml but it's not there, any idea?

Thanks,

Martin

[Former Member]

After some tests it appears that the .par file name must be changed before importing it using the New DC wizard. This solves the overwriting problem.

Martin

[luciano_leitedasilva]

Hi Martin,

I've changed the Mastead par file with successful, but using a local projet. I haven't any problem. Did you try create the new DC and ControlC and ControlV the code otherwise import the par file?

Regards,

Luciano

[Former Member]

Hi Luciano,

There is a step in the wizard to create the new Portal Project DC where we can either select to create it from an empty project or from an existing PAR file. I selected the second option, and browsed to select the masthead.par file. The project is then created and all the source files are copied automatically.

Now I'm wondering if I need to change the par file name <i>before</i> importing it, because it looks like after there is no way to change it. When a Portal project is not created as a DC, you can specify the par file name when you select "Upload PAR". But with a DC project we don't go through this step, we deploy directly on the J2EE server using <i>Development Component --> Deploy</i>. But just changing the file name might not be enough, there are surely other references to that name, like in the manifest files, so I don't think it's that simple. I will test it tomorrow when I'll have access to the system.

I'm also surprised to see that the portal doesn't support any vendor or namespace concept considering all the emphasis NWDI puts on this. Having the par files uniquely identified just by their file names is a little rudimentary. I guess there is still more integration work to be done with NWDI.

Martin