This is a list of enterprise-integration points and other common application-server concerns that AMIT should check during deployments, upgrades, and cut-overs.
- Host Name:Is this a web application? What is the intended public CNAME(s)?
- Apache redirects to the public name.
- Shibboleth is configured to use that name.
- touchstone-dev was contacted to add the hostname to Touchstone.
- Apache's certificates are for the public hostname, and the request for the cert was sent with the hostname all lower case.
- vhosts are set correctly for both HTTP and HTTPS.
- Memory Settings: Production and Staging servers likely have more resources than Development and Test. Validate the memory settings for runtime environments like Java and PHP.
- RAdminD: Server Operations manages the operating systems with RAdminD, make sure all paths to AMIT installed components are excluded from the RAdminD system profile or that the component is managed by RAdmind.
- Runtimes
- Redundancy: For machines with a legacy of more than one runtime installed (multiple Java, multiple PHP), work with the development team to figure out which one to keep and eliminate the rest.
- Get an accurate list of which runtimes are being used (Java, PHP, Python) and in what context (web, feed script) and configure the runtime to work only in the ways that system uses it.
- Feeds: Is the system dependent on feeds from other systems? Validate they are working correctly.
- Backup: Is a backup mechinism in place and functioning properly? This is different depending on the hosting option.