JDI for portal development

[Former Member]

Hi All!

I am currently configuring a JDI installation to use with the development of portal iviews.

The configuration went well, an I have tried making a new portal project (Using Scenario 2+).

Compiling the project also went well, but I have a question regarding the deployment of the par file.

The computer running the JDI, also has a portal installed, but do I still have to use the Export Par file/Quick par upload function, when I want to deploy the par file?

It seems a little waste, when we are already using the JDI to share the project, as well as making the central build?

I haven’t been able to find information regarding portal projects, and the use of JDI.

Is this not recommended?

Help is appreciated

Regards

Ronni Hostrup

[Former Member · Accepted solution]

Hi Ronni,

Yes ofcourse JDI is recommended for Portal development! This is true for all NetWeaver development.

The overhead for deploying to your 'local' portal is a small price to pay for the uniform way of deployment JDI offers. This way you (and your team) can switch from one environment to another without changing anything but the name of the J2EE Engine!

This might not be the answer you hoped for, but I hope it helps anyway

Regards, Jurjen.

[Former Member · Accepted solution]

Thanks for the answer.

Perhaps I should make myself a bit more concrete in my question.

We have a central server, which has the JDI And the Portal installed, we do not have any local J2ee engine.

When I make a new portal DC, and compile it, it works perfectly, and my teamate and I can share between us.

But how do we deploy it to the portal, so we can add it to an Iview?

I was under the impression that this would happen automatically as soon as the DC was checked in an activated.

But the only way I can make it work is by manually deploying it to the portal (or by using the Quick Par Upload inside NWDS)

And then it seems a bit overkill to make a central build and everything, when you deploy it manual anyways.

Am I using the JDI incorrectly or is there another way to do it?

Kind Regards

Ronni Hostrup

[former_member189311 · Accepted solution]

Hi Ronni,

no - you do not have to deploy the par file via the par upload utility of the NWDS portal plugin manually. The deployment (via SDM to the portal irj) is automatically started, after you imported the activity to the configured runtime system.

For me it worked fine.

Best regards,

Marion

[htammen · Accepted solution]

Hi Ronni,

when activating an activity a central build starts. This central build checks if your DC can be build in the central environment (buildspace) and starts the build process of DCs that depend on your DC, if any.

After the build of your DC it is stored in the central buildspace of CBS but it is <b><u>not</u></b> deployed.

This is done when you release your activity or a set of activities unless this option is deactivated in your track.

Regards

Helmut <u></u><u></u>