Transport Portal component (par)

[julioalberto_martinezreal]

Hi

I have developted some DC of portal components. When i transport the DCs with NWDI from one system to other i can´t see the pars in second system portal. Must i deploy par files?

Doesn´t NWDI deploy portal component automaticlly??

Regards

Edited by: Julio Alberto Martinez Real on Sep 26, 2008 10:43 AM

[Former Member · Accepted solution]

Hi,

If it doesn't move to next environment , I think that you have to make sure:

Are there open build requests in the buildspace?

Are there open conflicts in the workspace?

Are there any broken DCs in the build compartment?

Are there any u201Cdirty DCsu201D in the build compartment?

Are there any problem DCs in the build compartment?

Are there any pending activities that are not yet completely activated?

Are there any build error in the component?

Please double check above mentioned items and then try.

Thanks

Krishna

[julioalberto_martinezreal · Accepted solution]

It move to next enviroment but the portal code isn´t deployed in portal.

[Former Member · Accepted solution]

Which DC type did you use? Portal Application Module? This DC type does not have a deployable result. You should use Portal Application Standalone instead.

[former_member615004 · Accepted solution]

Our experience is that this will not lead to the expected result, especially when trying to transport scheduler tasks via NWDI.

Recently we wrapped our scheduler tasks in an EAR archive (another development component referencing the PAR public part of the portal application) and transporting this component via the NWDI.

Using this strategy the scheduler tasks were updated ok along the track...

regards

Dirk

[former_member185029]

hi,

Please check if the runtime systems are configured for automatic deployment.

-Ashutosh

[julioalberto_martinezreal]

How can do it?

In the NWDI administration??

[former_member185029]

Hi,

Go to CMS -> Landscape Configurator- > Select your track -> Go to Runtime Systems tab, check if disable automatic deployment option is check.

-Ashutosh