8 Replies Latest reply on Feb 9, 2007 3:02 PM by John Kopera

    Solution Manager Landscape

      We are in the process of migrating from 3.2 to 4.0 and wanted to ask what landscape others have setup for solution Manager. At this time we have only a production Instance but I did hear on the COI call that SOny had a 3 Instance Landscape for solution Mananger.

      What have others implemented?

      Thanks in advance for any feedback.

        • 1. Solution Manager Landscape
          Raymond Smith



          << We are in the process of migrating from 3.2 to 4.0 and wanted to ask what landscape others have setup for solution Manager. At this time we have only a production Instance but I did hear on the COI call that SOny had a 3 Instance Landscape for solution Mananger.

          What have others implemented?

          Thanks in advance for any feedback.
          >>



          At Centex Homes, we have a sandbox for applying support packs and testing setup and configuration. Since there isn't a transport path for most of the work in Solution Manager, we did not see a need for a Dev, Test, Prod setup. This has worked well for us.

          • 2. Solution Manager Landscape

            Great thanks. We have decided to install a Development environment and seperate production environment as well. Our plans are to install Solution Mananger, SLD and Netweaver administrator on one system, does anyone have any experince with a similar environment?

            Thanks

            • 3. RE: Solution Manager Landscape
              Michael Niven

              Here at Agilent Technologies we had a 3.2 SolMan environment setup with a production landscape and a Dev/QA landscape for SAP 4.6. We are in the planning stages of an ECC 6.0 upgrade for the coming year. We decided to do a fresh install of SolMan 4.0 on a new system which included SolMan, SLD and NW Admin. We have decided to setup the current 4.6 production environment in the new SolMan 4.0 system and configure the new Dev/QA as they are brought online. We decided to split into two landscapes so that we will monitor them at different intervals. As the environment expands we will decide if we need to change or add landscapes. I try and provide information as things progress.

              • 4. RE: Solution Manager Landscape
                Rodney Schmisseur

                At Verizon we're implementing a two-tier SolMan landscape.  The 'DEV' SolMan box will support the CRM config for CHARM, Service Desk, etc., with access restricted to a handful of folks directly involved in implementing Solution Manager scenarios (support packs, set-up, etc.). 

                The 'PROD' SolMan box handles our project-specific implementation work (blueprint, configuration, etc.) and supports project-team wide access tied to the rest of the NW landscape

                • 5. RE: Solution Manager Landscape
                  David Moore

                  We currently use a single production instance of Solution Manager.  As we integrate more solman functionality into the competency center, we will evaluate whether it is worthwhile to expand our landscape.  In all likelihood we will just virtualize another server into our environment and create a DEV system for Solman sometime in the next few months.

                  • 6. RE: Solution Manager Landscape
                    David Moore

                    We currently use a single production instance of Solution Manager.  As we integrate more solman functionality into the competency center, we will evaluate whether it is worthwhile to expand our landscape.  In all likelihood we will just virtualize another server into our environment and create a DEV system for Solman sometime in the next few months.

                    • 7. RE: Solution Manager Landscape
                      Scott Enterline

                      To clarify - we use 2 systems for Sol Man. We have a sandbox/dev system and a production system. If you are planning to implement ChaRM or Service Desk a two system landscape is the best suggested by SAP.  Send me a note at vonkajay@yahoo.com and can explainin detail

                      ajay

                      • 8. RE:Solution Manager Landscape
                        John Kopera

                        Has the two-tier SolMan design worked well?  At MolsonCoors, we're looking to roll-out new SolMan functionality and are investigating the possibility of two instances Dev/Test for the bulk of functions, project development, document repository, etc., and a Prod environment for system monitoring, CHARM -- basically the reverse of Verizon.  How did you come to that design?  Anyone else have resources to leverage in desgining the SolMan landscape?  Thanks!