ADXSTUDIO CMS is completely integrated into Microsoft® Active Directory® for all user authentication and access control. ADXSTUDIO CMS uses Active Directory to store the hierarchy of the content.

The web console is a DHTML application that runs in Internet Explorer 6.  It is used for all administrative functions, including content publishing, user management, and all other applications.  The web console uses XML and gets the data to render the user interface from the web server via a web services model.

ADXSTUDIO CMS uses XML for all data storage and for mapping form fields to LDAP or SQL data storage (ie:  the fields in the user manager get mapped to LDAP attributes, and the fields in the log viewer get mapped to a SQL table).  ADXSTUDIO CMS has a substantial API that covers everything from ASP, ASP.NET, Javascript, XSLT libraries, SQL, and more.

The server components of ADXSTUDIO CMS are developed in C# and are compiled with COM interop.  This allows them to be used within ASP pages.  Because they are .NET applications, they can be called within ASP.NET applications by including the assembly in the 'references' and using the API natively with .NET.  It is important to note that ADXSTUDIO CMS is not just a COM object; ASP.NET applications use ADXSTUDIO CMS with native assemblies and do not require reverse-compatibility to be turned on.  ADXSTUDIO automatically senses the environment it is being run in (ASP or ASP.NET) and makes appropriate calls to the underlying infrastructure as appropriate.

ADXSTUDIO CMS 2006 supports all editions of Microsoft SQL Server 2000 and 2005 (except Mobile Edition). Please refer to the Microsoft website for a complete description of the various versions of SQL Server, including the free SQL 2005 Express Edition: http://www.microsoft.com/sql/editions/default.mspx

Most clients have a shared source control system such as Microsoft Visual SourceSafe or Team Foundation Server and have multiple developers working on each project.  These clients also desire to use an isolated development model where each developer has their own isolated development environment so they can work independently, yet cooperatively within their team.  In these scenarios, it is recommended that a shared development server be set up to host the ADXSTUDIO CMS development websites.  A separate website and application pool is set up for each developer on the shared development server.  Separate application pools allow each developer to use the remote debugging in .Net to trace and debug their own website without having any impact on other developers.  Each developer will check out the shared project within their source control system to the location of their personal website using a network share.  A custom URL is also used to host and browse each developer's website.  This allows for an isolated development model and allows for complete remote debugging of an ADXSTUDIO CMS website for each developer.  It is also typical to set up a shared website that is considered a stable development site.  When developers have completed their changes, they typically push their personal website to the stable development site for further integration testing.  Using this model, the development url is always stable and is typically used for entering content into the development site, and is also typically used by the project managers to review project deliverables.  This model also minimizes the ADXSTUDIO CMS licenses as only a single license is required for the development server.  It is also typical practice to use Microsoft Virtual Server 2005 R2 to virtualize the development environment.

Example:  Your website name is wireframeindustries.com and your development team consists of Bob, Sarah, and John.  You have separate development, testing, and production servers.