<!doctype html>
<html>
 <head> 
  <title>Hardware Requirements</title> 
  <link rel="stylesheet" href="styles/site.css" type="text/css"> 
  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 
  <link rel="stylesheet" href="styles/icons.css" type="text/css">
  <script src="js/jquery.min.js"></script>
  <script src="tree/collapsibleTreeMenu.js"></script>
  <link href="tree/collapsibleTreeMenu.css" rel="stylesheet" type="text/css">
 </head> 
 <body class="theme-default aui-theme-default"> 
  <div id="page"> 
   <div id="main" class="aui-page-panel"> 
    <div id="main-header"> 
     <div id="breadcrumb-section"> 
      <ol id="breadcrumbs">  
       <li> <span><a href="Rhapsody-Integration-Engine-6.5_133160975.html">Rhapsody Integration Engine 6.5</a></span> </li> 
       <li> <span><a href="Installing-or-Upgrading-Rhapsody_133164145.html">Installing or Upgrading Rhapsody</a></span> </li> 
       <li> <span><a href="Pre-installation_133164186.html">Pre-installation</a></span> </li> 
       <li> <span><a href="System-Requirements_133164187.html">System Requirements</a></span> </li> 
      </ol> 
     </div> 
     <h1 id="title-heading" class="pagetitle"> <span id="title-text">Hardware Requirements</span> </h1> 
    </div> 
    <div id="content" class="view">  
     <div id="main-content" class="wiki-content group"> 
      <p>The Rhapsody organizationprovides a set of basic hardware specifications in order to give customers a general idea of the hardware requirements for deploying Rhapsody at their site.&nbsp;These specifications are not intended to replace formal, customized hardware recommendations created by Rhapsody's Professional Services Group (PSG) consultants.</p>
      <p>Rhapsody's hardware specifications are categorized according to site size and provide general recommendations based&nbsp;the estimated message load, the average size of the messages, a simple set of processing requirements and the number of days the messages need to be archived.</p>
      <p>The following table defines site size based on&nbsp;an average message size of 10kB and average message retention duration of 28 days:</p>
      <div class="table-wrap">
       <table class="wrapped confluenceTable">
        <tbody>
         <tr>
          <th class="confluenceTh"><p class="TableHeader">Site Size</p></th>
          <th class="confluenceTh"><p class="TableHeader">Messages <span style="color: rgb(0,0,0);">Received per </span>Day</p></th>
         </tr>
         <tr>
          <td class="confluenceTd"><p class="Tablecontent"><a href="#HardwareRequirements-SmallSite">Small</a></p></td>
          <td class="confluenceTd"><p class="Tablecontent">Less than 300,000</p></td>
         </tr>
         <tr>
          <td class="confluenceTd"><p class="Tablecontent"><a href="#HardwareRequirements-MediumSite">Medium</a></p></td>
          <td class="confluenceTd"><p class="Tablecontent">300,000 to 3,000,000</p></td>
         </tr>
         <tr>
          <td class="confluenceTd"><p class="Tablecontent"><a href="#HardwareRequirements-LargeSi">Large</a></p></td>
          <td class="confluenceTd"><p class="Tablecontent">Greater than 3,000,000</p></td>
         </tr>
        </tbody>
       </table>
      </div>
      <h2 id="HardwareRequirements-SmallSite">Small Site</h2>
      <h3 id="HardwareRequirements-SiteAssumptions">Site Assumptions</h3>
      <ul>
       <li>The site receives less than 300,000 messages per day.</li>
       <li>Each message requires mapping from one format to another and performs a simple table lookup before forwarding the message to another 10 systems.</li>
       <li>Peak load is about four times the sustained rate.</li>
      </ul>
      <h3 id="HardwareRequirements-MinimumHardwareRecommendations">Minimum Hardware Recommendations</h3>
      <ul>
       <li><em>Windows</em>® Server or Linux.</li>
       <li>64-bit Operating System.</li>
       <li>4 cores.</li>
       <li>8GB RAM and 2GB heap.</li>
       <li>40GB disk space for OS and Applications (RAID1).</li>
       <li>200GB disk space for data store (RAID1).</li>
      </ul>
      <h2 id="HardwareRequirements-MediumSite">Medium Site</h2>
      <h3 id="HardwareRequirements-SiteAssumptions.1">Site Assumptions</h3>
      <ul>
       <li>The site receives between 300,000 and 3,000,000 messages per day.</li>
       <li>Each message requires mapping from one format to another and performs a simple table lookup before forwarding the message to another 10 systems.</li>
       <li>Peak load is about four times the sustained rate.<span style="color: rgb(0,0,0);font-size: 16.0px;font-weight: bold;">&nbsp;</span></li>
      </ul>
      <h3 id="HardwareRequirements-MinimumHardwareRecommendations.1">Minimum Hardware Recommendations</h3>
      <ul>
       <li><em>Windows</em>® Server or Linux.</li>
       <li>64-bit Operating System.</li>
       <li>8 cores.</li>
       <li>8GB RAM and 4GB heap.</li>
       <li>40GB disk space for OS and Applications (RAID1).</li>
       <li>500GB disk space for data store (RAID10).</li>
      </ul>
      <h2 id="HardwareRequirements-LargeSite">Large Site</h2>
      <h3 id="HardwareRequirements-Assumptions">Assumptions</h3>
      <ul>
       <li>The site receives more than 3,000,000 messages per day.</li>
       <li>Each message requires mapping from one format to another and performs a simple table lookup before forwarding the message to another 10 systems.</li>
       <li>Peak load is about four times the sustained rate.</li>
      </ul>
      <h3 id="HardwareRequirements-MinimumHardwareRecommendations.2">Minimum Hardware Recommendations</h3>
      <ul>
       <li><em>Windows</em>® Server or Linux.</li>
       <li>64-bit Operating System.</li>
       <li>8 cores.</li>
       <li>16GB RAM and 8GB heap.</li>
       <li>40GB disk space for OS and Applications (RAID1).</li>
       <li>1TB disk space for data store (RAID10).</li>
      </ul>
      <p> </p> 
     </div> 
    </div> 
   </div>  
  </div>   
 </body>
</html>