cancel
Showing results for 
Search instead for 
Did you mean: 

Install NWDI as a separate instance - Need Advice

Former Member
0 Kudos

Hi All:

Myself setting up a 3 systems (Dev, Qlty & Prod) landscape in my current project.

Now I really want to understand and know the advantages and disadvantages of having NWDI as a separate instance rather than having it in Dev, Qlty (or Prod) Systems?

Why it is imp to have only in Dev system? Or how many DI instances do i need to have?

Thanks in advance,

MS

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Guys, tnx lot for both the inputs again. They gave me some clarity for sure.

Tnx,

MS

Former Member
0 Kudos

guys, any suggestions and references for my query..!

Former Member
0 Kudos

NWDI cannot exist in the same Java engine as your runtime engines.

Former Member
0 Kudos

... and you need only one NWDI installation.

Former Member
0 Kudos

Hi All:

Thanks for both the inputs. I'm very clear that we only need ONE instance of DI usually in DEV Server.

Now i'm not clear with Carlos statement, could you please elaborate your comments.

Tnx,

MS

Former Member
0 Kudos

Hi

The DI should be located in a separate server. Out of the three services provied by DI i.e, CMS, DTR and CBS, the CBS needs lot of memory. Because whenever a developer checks in the code, then the CBS service will build the project which eats lot of memory as well as CPU.Hence it is recommende to put the DI in a separate server.

However, being the Admin of NWDI its your call to put that in a separate machine depend on the load on your J2EE engine and the dev, Quality, Production server.

Hope this would be useful..

/Srikanth.

Former Member
0 Kudos

In addition, when you deploy to the runtime engine, the Java Server is sometimes restarted. If DI is installed on the runtime engine that is being restarted....