Skip to Content
avatar image
Former Member

NWDI/JDI Planning

I want my company to start using the NWDI (JDI) environment. But I am a little confused on how to layout DTR, CMS, CBS and SLD for our environment. We are currently modifying Java programs in CRM 4.0 (Java Kernel 6.4) with out the use of JDI. We are going to start an EP on NW2004S project. So I have 3 instances for CRM (development, QA and production) and three instances for EP. I am going to install Solution Managers 4.0 also. So I am trying to understand how I should handle NWDI for when you have multiple sap products up and running. FYI we are only staff of 6 developers.

1) Where to install SLD and Name Server?

I am thinking I should install at least 2 solution managers one for testing upgrades and use in QA and Dev and one for Production. With Solution manager instances I was going to install SLD and name server. Does that sound like good or bad idea? I know you only need one SLD but how do you deal with upgrades?

2) How to handle the DTR, CMS and CBS? I am not really sure how plan for this correctly. Do I setup 2 CMS one for EP and one for CRM or should I only have 1. I am at a total lost for the DTR and CBS. I am trying to figure out how to layout instances for the DTR, CMS, CBS. Please assume we will not be heavy users of the java development envirorment.

Thanks for the help

Matthew Stroh

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • avatar image
    Former Member
    Jul 21, 2006 at 12:36 PM

    I have a pretty good idea on what I should do now thanks. The one thing I am curious how are most people handling the upgrade / support stacks of the NWDI if you only have one instance to work with? In our R/3 enviroment we try the upgrade / support stacks in our Sandbox enviroment before we even apply them to Dev, QA systems. I am guessing I will have a similiar issue with solution manager.

    Thanks the help Pascal.

    Matthew

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Good question... You can set up an NWDI/SM sandbox system of course. There's noone to hold you back 😉

      It'll be hard though to make this sandbox a 100% copy of your production NWDI. Think about all the SLD data for example...

  • avatar image
    Former Member
    Jul 21, 2006 at 07:28 AM

    Hi Matthew,

    1. You can install the SLD and associated Name Server on any NW2004/NW2004s Web AS. We have it running on our NWDI system.

    2. You need to install only 1(!) instance of NWDI, containing the three components (DTR, CBS, CMS). In case you've got a lot of developments going on (which is not happening in your case with only 6 developers) you can put the components on different Web AS's though for load distribution.

    The next thing you need to do is determine the products that you are going to develop: You should consider your Java developments for CRM 4.0 as products, which you define as such in the SLD's Software Catalog. Note that you do not need to put everything into one product.

    After this, you must figure out the software components (SC's) that build your products. This is also defined in the SLD.

    Once you've done all this, you can start working with NWDI:

    1. Create tracks for your software components and assign runtime systems to these tracks in the CMS Landscape Configurator.

    2. Check-in the base SCA's required for development into the tracks using CMS Transport Studio.

    3. Configure your NWDS for NWDI

    4. Import the Development Configuration(s) that have been created from the tracks using the Development Configurations perspective of NWDS.

    5. Start developing!

    In your case you need at least two tracks: One for your CRM developments with the CRM systems assigned as runtime systems and one for the EP developments with the EP systems assigned as runtime systems.

    You can have even more tracks though and these can use identical runtime systems.

    Some important notes about your SC's and tracks:

    1. You can put multiple SC's into one track.

    2. You should put SC's with a different release cycle into separate tracks, so define your release strategy for all your SC's!

    Kind regards,

    Pascal

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 21, 2006 at 02:46 PM

    I am going with 1 SLD and 1 NWDI. I am going to load SLD on solution manager because that will be my first NW2004s install. Then create another instance for NWDI. Right now it would be nice to run these in Virtual machines. I am think the upgrade process using a VM machine would be

    1) Shutdown the VM with NWDI Instance

    2) Make copy of the VM Machine

    3) Bring up the VM Machine and apply the upgrade. If you run into problems shutdown the VM and bring up the copy.

    There is probably a better way, but that is just one thought in my head.

    Matthew

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 19, 2007 at 08:15 PM

    is the below design possible for NWDI We are planning to install a single NWDI system supporting all the Java landscapes (Different Tracks). and want to deploy to runtime systems (EP,XI etc) through CMS is this possible ,since all the

    documents say that only three systems can be supported through CMS . our landscape is DEV-QAS-Preprod --Prod(EP,XI etc)

    Add comment
    10|10000 characters needed characters exceeded