- Getting started
- System components and configuration
- BlackBerry AtHoc account requirements
- Install BlackBerry AtHoc
- Upgrade BlackBerry AtHoc
- Postinstallation or upgrade configuration
- Set antivirus file exclusions for database log and tempDB files
- IIS postinstallation checklist
- Application pool configuration tables
- Table 1: Application pool configuration
- Table 2: Application Pool - Web application associations for the AtHoc website - Enterprise configuration
- Table 3: AtHoc services application pool configuration
- Table 4: Application pools - web application association for AtHoc services web site
- IIS handler mappings
- Verification checklist
- Application pool configuration tables
- (Optional) Enable message termination
- (Optional) Enable and enforce the TLS 1.2 protocol
- (Optional) Configure the application server for Windows authentication
- (Optional) Configure client certificates on the application server
- (Optional) Set the SSL client certificate
- (Optional) Install certificates for cloud delivery services
- (Optional) Configure new access card formats for operator auto-login
- (Optional) Enable FIPS on each application server
- (Optional) Archive and MAS export service account requirements
- Configure .NET framework to use a web proxy
- (Optional) Restore the XML files for duplicated devices
- (Optional) Set up error pages for Self Service throttling
- (Optional) Set up error pages for Self Service throttling
- Advanced server configuration
- IIS 8.5 Security Technology Implementation Guide
- Server STIG
- IISW-SV-000103: Enable log file and Event Tracing windows
- IISW-SV-000107: Sufficient web server log records for location of web server events
- IISW-SV-000108: Sufficient web server log records for source of web server events
- IISW-SV-000110: Sufficient web server log records to establish the outcome of web server events
- IISW-SV-000111: Sufficient web server log records to establish identity
- IISW-SV-000112: Web server must use Event Tracing for Windows logging option
- IISW-SV-000120: Samples, examples, and tutuorials must be removed from production server
- IISW-SV-000124: Web server must have MIMEs that invoke OS shell programs disabled
- IISW-SV-000146: Web server must not impede ability to write log record content to an audit log
- IISW-SV-000153: Web server must maintain the confidentiality of controlled information during transmission
- IISW-SV-000154: Web server must maintain the confidentiality of controlled information during transmission
- Application STIG
- IISW-SI-000206: Enable log file and Event Tracing windows
- IISW-SI-000209: Sufficient website log records to establish identity
- IISW-SI-000210: Sufficient website log records to establish identity
- IISW-SI-000211: Website must use Event Tracing for Windows logging option
- IISW-SI-000214: Website must have MIMEs that invoke OS shell programs disabled
- IISW-SI-000228: Non-ASCII characters in URLs must be prohibited
- Server STIG
- Verifying BlackBerry AtHoc is operational
- Appendix A: Troubleshooting
- Appendix B: Organization duplicator object management
- BlackBerry AtHoc Customer Support Portal
- Legal notice
- BlackBerry Docs
- BlackBerry AtHoc
- BlackBerry AtHoc 7.9
- Installation and Configuration Guide
- Advanced server configuration
- Duplicate organizations across systems
Duplicate organizations across systems
Use the Organization Duplicator to make a copy of an organization on another server to set up a failover system, or to migrate to a new server. This tool is located on the application server.
Prerequisites:
- Two configured organizations on different database servers:
- Source server: The server location of the organization to be duplicated
- Target server: The server location where the organization is to be duplicated
- The source server should have configured users, alert templates, map layers, and other objects
Objects that are not duplicated:
- Global health monitors
- AtHocConnect organizations
- Incoming alerts
- Sent alerts
- User accounts
- Distribution lists (static only)
For detailed information about what is duplicated, see the "Organization Duplicator Object Management" section of this guide.
- Log in to the application server for the source system and navigate to the following directory:AtHocENS/ServerObjects/Tools/VPSDuplicator
- Run the Organization Duplicator tool as an administrator.
- Provide the source and target server information:
- Source:
- Database server: The source application server name. For example:DBSourceServer.mynetwork.com
- Username and Password of the ngad database.
- Target:
- Database server: The target application server name. For example:DBTargetServer.mynetwork.com
- Username and Password of the ngad database.
- ClickConnectto establish a connection and view the organizations that can be duplicated.
- Select the organizations to be duplicated. The Status column indicates whether the organization is ready to copy.
- Do one of the following:
- ClickCopy to Targetto copy the organizations to a new system.
- ClickNew on Sourceto create a new organization on the source system.
- ClickDuplicate on Sourceto copy an organization on the same system.
The message log indicates whether the duplication was successful.