Preparing a Production Environment

 

Preparing a Production Environment

The key to preparing a production environment is in the details. You most likely have already run through this exercise as you prepared or assisted in the preparation of the Development, Test, and UAT environment.  Make sure that any additional steps needed to be done (.NET Framework install, security adjustments, etc) are documented.

Below are some of the most common gotcha’s encountered when migrating environments.


AppServer

  • Ensure the web.config file is pointed to the appropriate Production Verivo Database
  • Ensure the web.config file is using the appropriate Production Database User credentials
  • Ensure the web.config has any debug keys commented out or turned OFF
  • Ensure the appropriate application plugins are located in the bin/plugins folder
  • Ensure the appropriate application plugins python files are located in the bin/plugins folder
    • Ensure that the python scripts are referencing the appropriate Production data sources
  • IIS
    • Ensure that all appropriate MIME types are added to the Application/Virtual Directory
    • Ensure that the Application/Virtual Directory is running under .NET Framework 4.0
    • Ensure that the appropriate Directory Security settings are turned on for the Application/Virtual Directory
  • Ensure that the Test page files are removed from the test folder on your AppServer.
  • Ensure that the AppServer has access to all application production data sources
  • Verivo Client OTA
    • Ensure that the IIS Application/Virtual Directory instance contains the appropriate MIME types
      • Blackberry
        • COD
        • JAD
      • Android
        • APK
      • iPhone Enterprise
        • IPA
    • Ensure that the appropriate Verivo client files are located in the Deploy directory of the Verivo AppServer
    • Ensure the web.config file has been updated with the appropriate keys to allow OTA to the customer specific Verivo Client
  • Verivo Client Download through Platform Application Store
    • Ensure the web.config file has been updated with the appropriate keys to allow redirection to the appropriate platform Application Store

Database Server

  • Production Database User
    • Ensure the appropriate permissions are set to the Verivo Database
      • Data Writer
      • Data Reader
      • Execute Stored Procedure
  • Configuration
    • Preparing to Export
      • Confirm if you need to bring over Mobile Users to the new environment
        • If not uncheck the Mobile User option
      • Confirm if the Verivo AppStudio Admin User is the same in the new environment
        • If not uncheck the Mobile User option
      • Always perform a full application export
        • Partial Exports are not handled as gracefully as expected
    • Preparing to Import
      • On the import details page confirm the Verivo Database version is appropriate
      • On the import details page confirm the Export Date is appropriate
      • Always perform a full application import
        • Partial Imports are not handled as gracefully as expected
    • Ensure Production Database User is set up as an Administrator
    • Ensure Datasources pointing to the appropriate Production endpoints
    • Ensure ‘Send scripts to iOS’ is turned OFF
    • Licensing
      • Ensure the appropriate application license key is set
      • Ensure the appropriate AppStudio Admin user key is set
    • Configuration Caching
      • Ensure ‘Cache Configuration on Client’ is turned ON
      • Ensure ‘Cache Configuration on Server’ is turned ON
    • Packaged Configuration
      • Ensure the Configuration Version value is set appropriately
        • If the value is the same as the Packaged Configuration export the client will not download new configuration
        • If the value is different from the Packaged Configuration export the client will download new configuration
          • On iOS the configuration download will adhere to the ‘Send scripts to iOS’ Application Property value
      • There is a known issue with Configuration Import where if this is the first time you have imported configuration to the Verivo Database and you immediately take a Packaged Configuration export that subsequent imports plus a Configuration Version value change will result in the iOS client to not work correctly
        • To ensure that this does not happen when you set up the Verivo Database that you either:
          • Perform a backup/restore from another environment
          • Import the configuration again after the initial import
    • User Provisioning
      • Ensure the appropriate Auto Enrollment Application Property setting is set
        • If Auto Enrollment is turned OFF ensure that all appropriate users are added and set to the appropriate application and workflow
    • Ensure Logging value is turned to the appropriate level
      • Errors Only is the recommendation

Client

  • Ensure the Application URL value is pointing to the Production Verivo AppServer
  • Ensure the Auth Type is set to the appropriate Production settings
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk