ArchivesSpace Enterprise Server Setup

Follow

Enterprise Agreement (Atlas Hosted)

What is included in the basic server setup?

The Enterprise setup includes two permanent servers

  1. Production Server - maintained by Atlas
    • Staff and public sites are enabled
    • Database access
      • User accounts with read-only access to MySQL will be created as requested
      • Access will be restricted by IP address and each user will be unique

  2. Sandbox Server - accessible by site, maintained by Atlas
    • Staff and public sites are enabled
    • SSH access
      • Secure access to configure ArchivesSpace
    • Database access
      • User accounts with read/write access to MySQL will be created as requested
      • Access will be restricted by IP address and each user will be unique

How do we get started?

Atlas will create and configure a new server with the production settings, but it will initially be in a pre-production phase. Atlas will contact the site to coordinate LDAP and SSL certificate setup (if needed). The site will be provided all the details, with optional temporary write MySQL server access if needed for the migration. In most cases, the you will transfer the data to us and we will upload it for you. Once the data has been successfully migrated and tested, the server will be in production.

How do we connect to the servers?

Sites can use their preferred 3rd party tools to connect to the production server via MySQL and sandbox server via SSH or MySQL.

When is the sandbox server created?

Once the server is ready for production, we will make a copy of the server. We'll reconfigure this duplicate server to be the sandbox server by updating the DNS, permissions, etc.

What else do we need to know about the sandbox server?

  • The purpose of the sandbox server is to have a space for the site to work with ArchivesSpace in a development and test capacity.
  • If issues arise, Atlas will not troubleshoot the sandbox server, but we will create a fresh copy of the production server or roll back to a previous backup of the sandbox server (only two weeks worth of backups are stored).
  • Atlas will maintain the server by applying OS and ArchivesSpace updates as well as any security updates that are needed.
  • Atlas will coordinate any updates with the site.
  • If the site would like to get a fresh copy of the production server (whether it's that the sandbox server is having issues or fresh data/setup is desired), send in a request to Atlas and we will get a new one created.

How do we make plugin updates or other changes to the production server?

  • To make a request for a plugin update, send an email to service@atlas-sys.com or call 800-567-7401.
    • The request should include detailed documentation of the changes requested, including all files that need to be moved (include their location) as well as any other updates needed to complete the new setup.
  • Atlas will create an additional temporary server, called the staging server, by making a copy of the production server, then running updates to configure it for testing (DNS, IP, db password, etc.).
  • Atlas will follow the site provided documentation to update the staging server configuration.
  • Atlas will vet/test the plugins/changes on the staging server.
  • Atlas will notify the site when the process is complete and provide links to the web pages, which should be within one week of the request.
  • The site will use the links to test the staging server to confirm that the plugins/changes work as expected.
  • The site will notify Atlas when the testing is complete, which will be within two weeks of the staging server setup notification.
  • Atlas will work with the site to schedule a time to make the update live (during business hours), which will be within one week of the completion of testing.
  • Atlas will delete the staging server after the production server has been successfully updated (server should be up for no more than 1 month).

How do we request updates to ArchivesSpace on the production server?

  • To make a request for an ArchivesSpace update to the production server, send an email to service@atlas-sys.com or call 800-567-7401.
  • Atlas will create an additional temporary server, called the staging server, by making a copy of the production server, then running updates to configure it for testing (DNS, IP, db password, etc.).
  • Atlas will update the staging server to the latest version of ArchivesSpace.
  • Atlas will notify the site when the process is complete and provide links to the web pages, which should be within one week of the request.
  • The site will use the links to test the staging server to confirm that the update works as you expect
  • The site will notify Atlas when the testing is complete, which will be within two weeks of the staging server setup notification.
  • Atlas will work with the site to schedule a time to make the update live (during business hours) - within one week of the completion of testing.
  • Atlas will delete the staging server after the production server has been successfully updated (server should be up for no more than 1 month).

How do we request updates to ArchivesSpace on the sandbox server?

  • To make a request for an ArchivesSpace update to the sandbox server, send an email to service@atlas-sys.com or call 800-567-7401.
  • Atlas will work with the site to schedule a time to upgrade the server.
  • Things to consider:
    • Atlas can update the sandbox server in its existing state, but note that if changes have been made, the results would not be the same as for the production server.
      • If the sandbox server has been altered, the staging server process would be followed before updating the production server.
    • If requested, Atlas can create a new sandbox server that is a replica of the production server.
      • If this is done, this new sandbox server could be used instead of a staging server.
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.