GRC
HR
SCM
CRM
BI


Blog

 

Register today for expert tips and a Live Q&A which covers the hardware, sizing, and landscaping considerations for GRC 10.0

by Allison Martin

June 15, 2011

Looking for more information on GRC 10.0? Check out the below tip from Kurt Hollis’s presentation on the types of hardware, sizing, and landscaping considerations you need to account for when deploying SAP BusinessObjects GRC 10.0. Make sure to Register Today for Kurt’s live Q&A session taking place tomorrow afternoon from 12:30 – 1:30pm Eastern time.

Hardware Platform Considerations for SAP BusinessObjects GRC Solutions
 

  • Follows the same platform considerations for all SAP NetWeaver- based systems
  • Refer to Product Availability Matrix (PAM) and release strategy
  • Can use a variety of hardware, operating systems, and databases:
    - IBM running AIX, i5/OS, or z/OS with DB2 database
    - HP with HP-UX with Oracle database
    - SUN with Solaris with Oracle database
    - SUSE or Red Hat Linux on a variety of hardware platforms
    - MS Windows Servers (64-bit OS) with MS SQL database
  • Large systems (with multiple application servers) are not normally required for SAP BusinessObjects GRC solutions
    - Suggest to pick a platform that SAP has a long support life cycle for and that your company is trained and confiden t in
  • Unicode and 64-bit only installation supported
  • Example: HP RX6600 IA64 server using two dual core CPUs and 16GB memory for Production system with Oracle database

Sizing for the SAP BusinessObjects GRC Solutions

  • Server size, CPU, and memory
    • ABAP Web Dynpro requires more memory then typical apps
      • 16GB memory minimum suggested for good performance
      • J2EE for Access Control and/or SAP Portal
        • 8GB memory minimum suggested
        • 2GB per J2EE server node
        • Several J2EE server nodes configured for Production
        • Use the sizing guide (Access Control only)
          • Sizing requirements are typically underestimated and result in performance issues later on
          • Database space – Initial 50-120GB plus yearly growth (see sizing)
          • May consider running both ABAP and Java stack (two separate instances) together on same server to reduce costs

Landscape Considerations for the GRC Applications

  • N+1 Landscape Strategy: Not recommended for GRC applications, applications are serving production landscape only, very limited development in this environment
  • Highly Available Possibility: Failover cluster not recommended for GRC applications, however, rapid recovery method to another server/site is recommended
  • Recommended Landscape Approach – three tier: Dev, QA, and PRD
  • Testing may be limited so a possible option is to dismiss the need for QA/Test systems
  • Minimum Landscap e Approach:
    Development and Production
    landscape. QA is optional in some
    cases.

Have your own questions on preparing your systems for GRC 10.0?

Join Deloitte's Kurt Hollis for a Q&A on technical issues and strategies for implementing and upgrading to 10.0  -- register now. Post your questions for Kurt and join the discussion during this one-hour Forum on Thursday, June 16 at 12:30pm EDT.

When you register you can also download  Kurt's GRC 2011 presentation "Lessons for Building Your SAP BusinessObjects GRC Solution Architecture." Review the information and tips in this detailed presentation, then follow the discussion on June 16, 12:30-1:30pm Easterm on Insider Learning Network.

An email has been sent to:






More from SAPinsider



COMMENTS

Please log in to post a comment.

No comments have been submitted on this article. Be the first to comment!


SAPinsider
FAQ