Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql_54d_0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /var/www/html/wp-includes/wp-db.php on line 2056

Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql_54d_0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /var/www/html/wp-includes/wp-db.php on line 2056
1.3 Installation – Archibus Environment Configuration | RSC Knowledge Base
Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql_54d_0.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /var/www/html/wp-includes/wp-db.php on line 2056

1.3 Installation – Archibus Environment Configuration

This section contains details of Archibus application instances, servers, clients, and directory structure.  This Archibus configuration is specific for Zynga, but follows a standard RSC configuration pattern. 

Application Instances

To allow structured software development and exploration of new capabilities, the following Archibus application instances will be maintained:

Production Environment

This environment contains Zynga’s live data and drawings.  Changes to this environment require testing in the Development environment, and completion of the Change Request process.

Development Environment

This environment is a recent copy of the Production environment. It is used to by developers to build enhancements or fixes to the Archibus Application. Once Developers have completed enhancements, they are also tested in this environment.

Demo Environment

This environment contains a standard out-of-the-box instance of the Archibus Applications, with no Zynga data; all data in this environment is demonstration data created by Archibus to demonstrated Archibus capabilities.  This environment allows Zynga to explore other Archibus capabilities before setting them up in their own environments.


These environments are hosted on the following Windows VM Servers.  The servers are VMs running on VM Hosts physically located in Ntirety data centers as detailed below:

Server Name




Production server

Primary Node: 

Failover Node: 


Development server

Primary Node: 

Failover Node: 


Demo server


Primary Application Software

The following are the primary application software packages that run on each server type

Application Server

  • Tomcat – Application Server – Web Central runs inside Tomcat
  • IIS – SpaceView and MicroView run under IIS
  • Java JRE – Java Runtime Engine – Supports Tomcat
  • PHP – SpaceView and MicroView are written in PHP and need PHP to run
  • SQL Automation Engine – This is an RSC-proprietary Windows Service that interacts with the SQL Server Database to perform scheduled operations such as file imports and exports.  It is also used for updating Archibus calculations such as “update area totals” and “perform chargeback”.

Database Server

  • SQL Server Database (Standard Version) – Database Server Software
  • SQL Backup Master – Database Backup Software (Creates daily backups of the database)

Application Server File Structure

The locations of the ARCHIBUS files are described below.

  • D:\ CAFM
      • Backup – contains the full backup of databases of Production and Development
          • CRYSTAL_AUTO
          • DOWNLOADS
          • EXCHANGE
          • gnupg
          • Projects
          • Schema
          • SSL – Server SSL Certificates are installed here
          • Testing
    • APPS
      • AFM23
      • Agent_Ransack
      • CADNOW – floorplans publishing app
      • GnuPG
      • Inetpub\WWROOT – Root folder of the IIS Webserver
        • ARCHIVE
        • aspnet_client
        • maintenance
        • microview_tablet – Production MicroView Instance
        • microview_tablet_online – Production MicroView Instance
        • microview_tablet_online_dev – Development MicroView Instance
        • spaceview – Production SpaceView Instance
        • spaceview_dev – Development SpaceView Instance
        • spaceview_non_sso – Non-SSO SpaceView Instance
        • spaceview_test – Test SpaceView Instance
        • spaceview_workplace – Workplace SpaceView Instance
      • Java8 – Java is installed here
      • MViewFM_35 – Mview app
      • PHP – PHP is installed here
      • PHP Syncs
      • PHP Syncs Dev
      • PHP74
      • PortyQryV2
      • RSCSQLAUTO – RSC SQL Automation Engine
      • Shibboleth – Shibboleth is installed here; it is used to set up Web Central, SpaceView and MicroView as SAML Service Providers (SP)
      • SSO – SSO logs
      • Tomcat 9 8080\ – Apache Tomcat Production (SSO) instance of Web Central
      • Tomcat 9 8082\ – Apache Tomcat Production (NON SSO) instance of Web Central
      • Tomcat 9 8084\ – Apache Tomcat Development and Demo instance of Web Central
    • DOWNLOADS – Contains install files for all software on the server
    • FileShares – This is where drawings are stored and formatted floorplans published (note that the Development instance generally uses the same drawing files as Production)
      • Backups – contains the Archived exports and Development backups
          • Demo-HQ – contains DWGs (AutoCAD drawings connected to ARCHIBUS), enterprise-graphics (published floor files for Web Central in svg format) and maps (published drawing files for SpaceView and MicroView in gif format)
      • Development – contains DWGs, enterprise-graphics, and maps
      • Download – Archibus SmartClient Software 25_2
      • Production – contains DWGs, enterprise-graphics, maps and maps_old

Database Server Databases

Application data is stored as follows:






Production Database



Development Database



Demo Database

Access Permissions and Security

There are two ways to access the servers:  As a Server Administrator, and as an Application User.

Server Administrator Access

Server Administrators access the servers using Windows Remote Desktop.  The following security protections are in place to prevent unauthorized Access

  • RDP Access requires that the user be logged into RSC’s OpenVPN Virtual Private Network (RDP Login Ports are not available externally)
  • Logging into OpenVPN requires Two-Factor Authentication, in this case DUO on a mobile device linked to the user logging in
  • Only RSC Domain Administrators have accounts with permissions to log into the server

Application User Access

Application User access is through HTTPS-secured applications which also require SSO SAML Authentication (both SpaceView and WebCentral are set up as SAML Service Providers (SP).  Two Identity Providers can grant access to SpaceView and Web Central:

  • Zynga SSO SAML IdP – This is how Zynga users will be granted access to Web Central and SpaceView
  • RSC SSO SAML IdP – This is how RSC Administrators will be granted access to Web Central and SpaceView


There are two generic Administrator accounts within WebCentral that RSC Administrators will use:


Logon ID






In Production, Zynga CAFM Users Accounts within Archibus will be created using a SQL Automation Engine Sync.  Users will be created based on Employees, created by another Sync.  Which users will be able to log in will be determined by Archibus’s connection with the Zynga Single Sign On System, and by Administrators assigning these uses appropriate roles with limited Application access.

Client Environment

Browser Applications

Most client access will be through Web Browsers on their Desktops.  The following applications will be available via this mechanism:

  • Web Central – Archibus Packaged Web Application for users working full-time on Archibus.  This is the “heavy” and rich user interface that provides access to all data, but requires training to use.
  • SpaceView – A quick-access portal to user and space data

All these applications will be available only over TLS 1.2+ connections, and will require Zynga SAML SSO Authentication for access.

Windows Applications

One application needs to be installed directly on users’ desktops because of its need to integrate with other Windows desktop applications

  • Smart Client – This Windows application allows direct editing of Archibus data.  It also connects to either AutoCAD or Revit to allow drawings to be published to Archibus

Smartclient also users HTTPS for communications, will be available only over TLS 1.2+ connections, and will require Zynga SAML SSO Authentication for access.

Only Zynga data administrators and CAD users should need this application installed.  RSC can assist with installation and setup.

Was this helpful?

0 / 0

Leave a Reply 0

Your email address will not be published. Required fields are marked *