Common Platform Basis: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
no edit summary
No edit summary
Line 1: Line 1:
Domain Content Mgt. System ([[DMS III|DCMS]]) integrates the following packages ¹ for the indicated  standard purposes and can be for key milestones in the to initialization of  your dominion (enterprise domain(s)):
'''ai-integration.biz''' Domain Content Mgt. System ([[DCMS-X]]) integrates the following packages ¹ for the parenthesized standard dominion purposes:
<br>
<br>
<table><tr><td width=400>
<table><tr><td width=400>
<ul>
<ul>
  <li> dojo (js,AJAX)
  <li> Eucalyptus (Open Souce Cloud Framework)
  <li> Drupal (Actions,Organic Groups,Workflow)
  <li> Drupal (the current stable core, our AOP framework service and our maintained (third pary) module set)
  <li> JBoss (Hibernate, Java, JMX, etc.)
  <li> JBoss (for all Java services)
  <li> Joomla (default Front End CMS)
  <li> NixOS (WFL/DCP is distributed as a derivative of this pure function Linux distro)
<li> LAMP (DCMS core, -E, -W, etc.)
  <li> SQL-Ledger ( used for Chart Of Accounts )
  <li> SQL-Ledger ( i18n COA )
<li> TYPO3 (Site Templating/Backend CMS)
<li> VirtueMart<br>&nbsp; ( carting, product catalog, and e-commerce/COA interface)
</ul>
</ul>
</td><td align=justify>
</td><td align=justify>
While we have used many, the RDBMSes we mainly use these days are MySQL, Postgres, and SQL Server, others as required. Note that some packages we use require  MySQL or Postgres and both are standard required components of our base platform service. SQL Server integration is performed on a case by case basis.<br><br>
We support the folllowing RDBMSes
Development environments contain simple db instances, production ones can use clustering, replication, etc.
 
*MySQL
*Oracle Express &sup1; or non-free Ora server.
*Postgres
*SQL Server &sup1;
 
&sup1; provided on a case by case basis
 
</td></tr></table>
</td></tr></table>
Our core platform services are made available in bindings for all of the above and our platform service setup will create a fully functional development prototype of a generic vertical for each distinct enterprise domain set or '[[dominion]]' using same. You can see this illustrated in our space with our 3 regular IPV4 domains.
Our core platform services are made available in bindings for all of the above and our platform service setup will create a fully functional development prototype of a generic vertical for each distinct enterprise domain set or '[[dominion]]' using same. You can see this illustrated in our space with our 3 regular IPV4 domains.

Navigation menu