Deployment for Internet Information Server (IIS)

Archibus uses its system architecture because this architecture is standard, provably secure, reliable, scalable and in use by the largest Web sites in the world.

IIS and Active Directory are the most common deployment environments among Archibus customers, and Archibus connects seamlessly with Windows client and server infrastructure.

Archibus supports Windows-Integrated Authentication as a standard deployment option. For instance, if your Web Central server is configured for Windows-style authentication, a "Use Windows authentication" checkbox appears as an option on the Sign In form. The Smart Client Web Services negotiates with the SSO server as to which built-in Windows authentication protocol (Kerberos or NTLM) to use. The Smart Client uses the network credentials of the current Windows user.

The Archibus Smart Client, Smart Client Extensions for Revit and AutoCAD are naive .net applications.

The Archibus Reservations Plugin for Microsoft Outlook is also a native .net application and operates right inside of Outlook. Users do not need to switch environments.

IIS sites can:

• Use IIS as the Web server, and it is the only piece of software that the rest of their enterprise and enterprise systems need to see or interact with.
• Use Active Directory and Window-native authentication unchanged with every part of Archibus, including Web Central, the Smart Client, and the Extensions
• Rely on Archibus business partners to install and maintain Archibus and any connector to the IIS infrastructure.

The connectors that Archibus uses are:

• a reverse proxy from IIS to connect to Archibus and its server via Apache JK, which is an industry-standard connector
• Web Services from environments like the Smart Client and the Archibus Plugin for Outlook
• Microsoft's own library for connecting to Exchange