SAP Landscape

Currently we are working on Entire SAP landscape using single SAN storage where database of DEV,QAS and production will be stored. Whether the SAN should be used for all databases or it should be for production database only?

This is something only the hardware vendor can tell you. "Usually" you do a sizing using Quicksizer (http://service.sap.com/quicksizer) and your chosen hardware vendor will suggest the best matching hardware for you (machines + SAN).
You can put all instances on one SAN technically, keep in mind that the performance of the production may be impacted if someone is doing things on the other two systems. However, there are SAN systems, that can do I/O class priorization, we don´t know if you SAN can do that. Check with your vendor.
Markus

Similar Messages

Importance of quality box in sap landscape.

Hi All,
Can anyone explain about why generally all the companies using the QUALITY BOX in the SAP LANDSCAPE, Anyway we are already testing with the DEVELOPMENT BOX, so we can transfer directly from DEV to PRD na.....Why the need of QTY there. This question i got in the previous interview...
Thanks in Advance..

Hi,
We need real time production objects for the proper testing, so we have to copy the data from production to other systems that we can't do for the DEV box due to the customiztion involved in DEV box because of the above reason we Use quality sytems for the testing purpose.
Will copy the data from Production to QAS and will use the same real time data for the testing inorder to avoid any issues in PRD box from the customization part.
Hope the above information will helps you to understand the testing environment.
-Srini

Best practise for SAP landscape and copyback procedures

Can i get help on bestpractise for SAP landscape design and copy back procedures .

Hi. GO to http://help.sap.com/bp/initial/index.htm
There you find all about BP.
Regards, Award if helpful

Best practice SAP landscape

Hello all,
I would like to know if there is some kind of best practice regarding SAP landscape in a big company.
For example is it recommended to have in the landscape a SAP Quality Assurance System open for customizing (transaction SCC4) so that quick customizing tests are performed at any moment, instead of customizing in Development system and then transports in QaS. (this can be very frustrating because for solving and testing an issue it's possible that numerous customizing tasks and reset of customzing is neccessary) ?
How SAP compliant would this solution be?
Thank you very much for your help!
Daniel Nicula

Hmmm, I do not know exactly if the question can be posed here in GRC related threads.
But it seemed to me that it is somehow connected.
Anyway, I agree with you that final customizing should be done in DEV and then transported in QAS.
What i am not sure is if it is against SAP recommendations to have a QAS opened for customizing and try all the solutions for an issue. And in the end when you are sure of what you want to do and to obtain, then you do the customizing also in DEV and follow the normal transport route.
Which can be the risks in case you have a QAS opened for customizing?
Thank you.

Change in Active Directory Domain where a SAP landscape is installed

Dear fellow forum members,
the IT team of one of our customers is planning a change in their Microsoft Active Domain forest in their LAN: as their SAP ERP systems are all domain installations, they have asked me, as their BASIS consultant, if this activity could harm in any way their SAP landscape.
The SAP ERP Systems are domain installations on two Windows Server 2008 R2 64 bit hosts.
This is the activity they plan to do is to replace an old Windows Server 2003 domain controller with a Windows Server 2012 domain controller. These are the steps they will do:
1) Add the new Windows Server 2012 domain controller to the forest;
2) Move the main roles from the old Windows Server 2003 domain controller to the new 2012 one, following the procedure recommended by Microsoft;
3) Remove the old Windows 2003 R2 domain controller from the forest.
During all the procedure, their current Windows Server 2008 domain controller will remain active and functional. At the end of the procedure, the domain will then be updated to a Windows Server 2008 structure, from the actual 2003.
I can't see any problem in this procedure: at least one domain controller will always remain active so the SAP users <sid>adm and SAPService<SID> will be able to authenticate on the domain with no interruptions. Also the SAP hosts won't change name, FQDN, IP address or configuration.
But I'm not a Microsoft AD expert and this procedure can't be tested beforehand, because all the SAP systems belong to the same domain obviously.
I've searched through the SAP knowledge base and I can't find any note or document that is relevant to this activity.
I've also opened a ticket to SAP, but they basically replied that the Active Directory is a matter for the Microsoft consultants, not SAP. They also recommended I post my question on the forum so here I am.
So I'd like to ask you if you foresee any problems with this procedure, and if you can recommend preparation activities or any other kind of precautions.
Thanks, kind regards.
M

Hi Marcello,
I can tell you that the Network Operations group at my organization have upgraded the domain controllers a few times (Windows 2000 -> Windows 2003, then Windows 2003 -> Windows 2012), and other than some warning about potential disruptions during the maintenance window, they didn't otherwise even include the SAP Basis group in the discussion! So, it happened, we did nothing special for SAP to prepare (nor afterwards), and basically we didn't even notice. It made no difference to SAP. Other aspects of network/domain functionality, especially our Exchange email server, experienced more disruption than SAP did.
So, in conclusion, I think that your IT team can proceed, and other than keeping an eye on things and testing basic things, like network communication, afterwards, there isn't much you need to do. Your main concern is that there always be a functioning domain controller (and DNS server). Do they have a rollback plan if things go south for them?
Regards,
Matt

Agile Development in an SAP Landscape

My team is looking to shift from a 'regular', waterfall-type development methodology which delivers 2 large functional releases per year to a more flexible, nimble project based approach based on Agile Development methodologies.
The goal is to be able to treat each project independently from a resource and scheduling perspective - so multiple projects could be underway at any one time but each one potentially running on a different time line. Of course, life-cycle support for the production environment would be on-going at the same time.
The problem we face is defining an SAP system landscape that supports this approach and that allows for the management of the inevitable conflicts that will arise when different projects require changes to the same development object.
I'm interested to hear feedback from anyone who has implemented an Agile Development approach within an SAP environment ( successfully or not ! ) as well as ideas for what a possible Agile SAP landscape could look like.
Thanks
Tim

Our team has been adopting some agile practices and have seen some great benefits. We have not embraced one methodology entirely (XP, Scrum, etc.). We're taking bits and pieces that make sense in our environment and adopting them incrementally.
Here's an example of some of the things that we're doing:
1. Chunking out development tasks. Basically working with the requirements or functionality that we know and not waiting until every possible scenario is clearly (or not so clearly) defined. We try to get stakeholders (business users and BPx's) looking at our programs and prototypes often to ensure that we're on the right track. This chunking out of tasks has been a benefit in that it is easier to manage (from a manager and developer perspective) and it gives us clearly definable goals for what we're shooting for in a fixed time frame (1 week). We talk individually every day (short spinarounds) to ensure that we're on track and identify any potential risks.
2. Modeling of requirements. This proves extremely valuable to our developers, functional folks, and business users. This usually involves grabbing a couple of folks and whiteboarding ideas to ensure that everybody has a clear understanding of what is going on. I will admit that this we certainly don't do it as much as we should, but it's something that we're working on doing as much as we can.
3. Frequent builds/migration. We currently transport released changes to test every 30 minutes in the ABAP stack. This allows us as developers to move on to the next task and allows our testers a quicker turnaround of bug fixes and new functionality. We move production code twice a week. For the JAVA side, we do a "JIT" build/deployment. As fixes need to be migrated, we check in/build and deploy. Since the NWDI is still new to us, we haven't done much investigation on automating this process, but I imagine that we will do so in the future.
One of the challenges that we ran into was thinking that the code was the only thing that matters (which you might get from some agile camps). Just because you're modeling and documenting (just enough documentation), does not mean that you're not "agile". You don't throw out design and analysis just so you can sit down and write code to have something to show somebody. The collaboration and clarity that agile practices provide is one of the keys to making it successful.
We started implementing some of these practices in the development group about 8 months ago and since then we've seen some interest/adoption in our project management group and functional teams. I would imagine that we'll continue to pick and choose practices that work for us...try some out, see what happens, adapt, evolve, etc. So far so good in my opinion. From a managment perspective, it really has made it easy to know what people are working on and how productive we can be as a group. From a developer's perspective, it makes development easier and more fun when you have a clear target in front of you and you can throw out ideas in a modeling session. From the end user perspective, they seem to like that we can roll out production ready functionality in an incremental way so they don't have to wait 6 months to get something that they can see and use. From my limited experience, it seems to be a much better way to develop applications.

Why the public IP is used in SAP Landscape

Hi All,
I need information about public IP is used in SAP landscape.
I searched in google and sap forums, but it gives how to public IP change in SAP system.
It didn't give reason.
Can you help in this.
Regards,
jhansi.
Edited by: gajula jhansi on Mar 29, 2011 9:18 AM
Edited by: gajula jhansi on Mar 29, 2011 9:22 AM

Hi,
The public ip is used in sap router configuration, so to configure sap router we have to give ip address.
Thanks
Srikanth

Sap landscape issue

hi all,
         just went thru the rules and regulation posted by juan...nice..
my query
          1)in sap landscape what is the number of clients we should be having in DEV QAS and PRD system.
                          a)as i am able to understand if we have DEV server installed we will automatically acessing 000,001,066
                          b)if we have QAS server installed we will automatically acessing 000,001,066
                          c)if we have PRD server installed we will automatically acessing 000,001,066
                                   Then why do we say that we should have only one client in PRD server.
                                                                                or we can say excluding 000,001,066 only one
please clear my confusion on this..
regards
keith

hi keith,
            first you need to understand the SAP landscape clearly , If you are having DEVELOPMENT ,QUALITY and PRODUCTION system i.e three system landscape, all three will have 000,001,066 client in that. now it depends how your system goes about , being DEVELOPMENT system you must have one test client, one copy of master client(000) assume 111 where all your development work will undergo.
          same is the case with your QUALITY server also.
but when it comes to PRODUCTION you should have only one client(as shyam also mentioned) where production activites should take place.
to read more about this-see these helpful links
http://www.sap-img.com/general/what-is-sap--landscape.htm
cheers -
ashish singh

How many NWDI's in your SAP Landscape

Hi SAPpers,
we have a reasonable size SAP landscape and our developers do a lot of WebDynPro developments for Portal.
We are now beginning to integrate CE with NWDI too, but that's a separate story.
My point is, in our SAP Landscape we have ONE NWDI installed.
We've just had basically a system down for NWDI for the last 10 days and it has shown us what a single point of failure NWDI is, because, as we have only one NWDI, if it is down, Developers cannot work, and transports cannot be completed.
Therefore, my question,
What does everyone else do about this ?
Should we have a second NWDI, as a warm standby, where, if we lose the main NWDI we then configure the tracks in the standby NWDI and get the Developers to work against that one while we fix the primary NWDI ?
Is there any guidance from SAP on how many NWDI's to have in a SAP Landscape to stop the NWDI becoming a single point of failure ?
Others, please be aware of the risks and consequence of only one NWDI in a SAP Landscape.
Thanks and regards,
Petr.

Hi Pascal,
thank you for your reply.
High availability of NWDI would not help the problem that recently happened to us, NWDI for various reasons stopped working.
Hence we need to think about some kind of warm standby NWDI which could be bought up in emergencies, have all tracks configured in probably 12 hours - for ESS etc and then become active while the main NWDI is being repaired.
NWDI is indeed a single point of failure on its own.
Kind regards,
Petr.

Transporting a Crystal Report to a different SAP landscape

I have developed a Crystal Report in our development SAP landscape. I have published it and am able to view it in Infoview. I would now like to transport that report to our test SAP landscape. How do I transport my Crystal Report? I have looked in the SAP Integration Kit Users Guide, Installation Guide and the Admininistration Guide with no luck. I have also searched the Knowledge Base. Any help would be greatly appreciated. Thanks.

Hi Dennis,
in case you saved the report to the BW system via the SAP menus in the CR Designer then you can use the standard transport mechnism from the SAP system
Ingo

Solution Manager 7.1 Integration into SAP Landscape

Hi All
I have a few questions for all the SAP Solution Manager experts out there and for anyone that would like to take a stab at these questions. An organization would like to implement a 3 system landscape for the following SAP Applications; SAP ERP, SAP CRM, SAP SRM, SAP Portal, SAP XI, SAP BI (SAP BW and SAP BOBJ) as well as SAP Solution Manager. They want to use all the functionality that is available in Solution Manager. The questions that I pose is as follows;
     1. How many Solution Manager systems must one implement? A 3 system landscape or will a 2 system landscape suffice? Bearing in mind that    functionality such as CHARM will be implemented.
     2. Where will the productive SLD reside? How would this SLD connect to the Solution Manager Systems?
     3. To which Solution Manager System will all the diagnostic agents connect to?
Your expert input would gladly be appreciated and points awarded accordingly.
Regards
Deen

Hi Deena,
I good approach would be to use a two system landscape.
Where - all sandbox and development systems are connected to develpoment solman.
and - all other systems, like quality, pre-prod, and prod are connected to production solman.
For CHARM, this is sufficient. Keep the hardware specs on the higher side of production solman.
You should use a separate SLD instance on your solution manager. WHY, incase you need to update the SP level, as SLD needs to be on the highest level, outage from SOLMAN or PI would be avoided.
You can also use, SLD of Solution manager, SYNC you dev sld with prod sld - uni directional sync - eg for stack generation.
SLD connect to your solution manager during solman_setup basic configuration and preparation of your landscape through LMDB.
Check.
SLD and LMDB Topology: Replacing the Source SLD for the LMDB
https://help.sap.com/saphelp_sm71_sp05/helpdata/en/a5/971735dd184f5c8d943c6cf423d13a/content.htm
Connect diagnostic agents to your producitve solution manager.
For more please reply back.
Good Luck !!
Regards,
Divyanshu

SAP Landscape for ECC,EP,BW,XI, DMS and TREX

Hi all,
I am in the role of SAP Basis Consultant for an IT organisation. One of their client require to install SAP ECC ( FI-CO,MM,PS,HR,REM,PM), EP, BW, XI, DMS and TREX. Their plan is to use ECC 6.0 ( Netweaver 7.0 SR2) with EP 7.0 and all others are latest version. The Dev setup in WIndows-Oracle and production will be AIX-Oralce. In the Dev setup, install all the components in separate servers and in production it is to be combined as follows ERP+ SRM(later) in one server, EPXI in another server, BW in one server and DMSTREX in last one.
Here my doubt is, this installation plan will have any issue?.
Second, the data export from DEV ( windowsoracle) Production ( unix-AIXoracle) will have any issue?
Please reply with details. As the project is in the planning phase.
regards,
Siby Syriac.P

Hi Siby,
If your client need such a broad installation (SAP ECC ( FI-CO,MM,PS,HR,REM,PM), EP, BW, XI, DMS and TREX), I'm sure that they hired a Senior Project Manager together with a team of senior consultants in each of the areas to look after the implementation. Also i presume they have look into hardware requirements to ensure the landscape will deliver the adecuate performance to the target amount of concurrent users.
As far as i can see from the 10 lines you wrote, I can't see a QA environment been considered... which I think is a mistake (thats only my own opinion). I can't see any issues having DEV runnning Windows and PRD running AIX (As long that youre confortable working in both environments). About the installation plan is very difficult to tell by your 10 lines but I'll try avoid having two big systems in the same box as ECC and SRM.
Thats my 2 cents
Regards
Juan

Removing risks and violations in existing SAP Landscape

There is a landscape where SAP ECC is already installed and we are planning to install AC 5.3. As the roles are already there in ECC Dev system, so we will perform the risk analysis in Dev and once free of risks, move the role to Production.
I would like to know, from where to start in already existing sap roles structure to free up them from risks. Do we need to provide the business process roles to indiviual BP Owners like FI roles to FI team and same for others to clear the risks and violations. Once completed from them, run them in RAR to found any risk violations remaining. If still found, follow the same process till all the roles and clean and can be moved to production.
Do we need to start from transaction level?
Any help appreciated.
Regards,
Sanjay

Sanjay,
there are various ways to achieve that and many replies are already there (pls search similar threads)
well small summary will be
1. customize standard rules per your org requirement
2. role are already existing, hence i expect they were create business wise
3. run analysis on all the role and have a report in your hand
4. discuss with various security leads of each buisness, which risk wish to be removed and which one to be mitigated
5. once done with cleaning of role, it's time you run analysis on users and mitigate or clean...........
hope it helps
regards,
Surpreet

Technical system definitions on multiple SLD servers in a SAP landscape

Hi,
If we want to migrate an SAP SLD server from Solution manager application to ECC application(s). In this process solution manager's SLD server data will be migrated into multiple servers at ECC environment(say for example, we define one SLD server for all development systems and one for Production systems).
Is it required to have all technical systems of SLD servers to be same? (I mean do we have to have all the technical systems defined on Dev SLD server to be available even at PRD SLD server?)
Thanks in advance for all responses.
NetWeaver admin.

Hi,
Yes. If you configured some technical system which reports data to your DEV SLD. And you want same data should be replicated to PRD SLD then you can configure data bridge between DEV SLD and PRD SLD. Then your DEV SLD will replicates its data to PRD SLD.
In order to configure data bridge, you can check below link:
http://help.sap.com/saphelp_nwesrce/helpdata/en/43/da21ba13660aa5e10000000a1553f6/content.htm
Thanks
Sunny

Can Solution Manager manage all the security for all of our SAP Landscape?

Hello Solman gurus - We're looking at Solution Manager once again. I had installed it for incident management back several years ago during our original go-live - and it fell by the wayside after go-live. My question is related to the latest and greatest version - can it actually to the administration of security roles, profiles, etc. of all of our SAP systems from within Solution Manager?
Much thanks, Ken Little

Sound like Central User Administration to me.....

SAP Landscape

Similar Messages

Maybe you are looking for