Create Endur/Findur Environment Wizard

To streamline the process of creating new Endur/Findur environments, we have created the 'Endur/Findur Environment Wizard'.

This is accessible to emdash™ administrators on the home page:

Clicking on the button takes the admin user to the Wizard page, where they have some simple information to complete:

The information needed is:

  • Environment Name
    • What the environment will be called in emdash™.  
    • Entering the name of an existing environment will warn the user that the rebuild process will be rerun.  
    • This is useful in the event the job failed, or new Azure VMs need to be created.
  • Owner
    • Who will own the environment when it has been created.  This defaults to the user running the Wizard
  • Source Environment Name
    • If environments already exist in the emdash™ instance, you can select one
    • Selecting an environment will make the new one look the same in terms of applications that are allocated to it and their versions
    • If no environments already exist, you do not have to complete this field
  • Select or Specify Backup File
    • If you specify a source environment, a drop down list appears with the recent database backup files available.  Selecting one of these will use it to refresh the new environment
    • Alternately, you can specify a UNC Path to an Endur/Findur backup file which will be used instead
  • Database Server Name
    • If environments exist, you can select from a list of pre-configured database servers
    • Alternately, you can specify a new database server by clicking on 'Add database details' where you will have a pop-up to define the server, database type, and version of the database (e.g. <Server>\<Instance>, SQL Server, SQL 2012R2)
  • Database Technology and Version
    • Confirmation of the data associated with the database server selected
  • Environment Type
    • This is the categorisation within emdash™ - where it gets presented on the emdash™ home page
    • You can create new 'Types' by clicking on the 'Create New Environment Type' button
  • Authentication Type
    • This is the way in which users will connect to the Endur/Findur environment.  The options are:
      1. AD.  The default in 99% of cases would be single sign-on through the windows account
      2. SQL.  In some cases a separate application login is required.  This means that each user will have a database login created for them.
  • Fileshare
    • The root location of where the environment's fileshare will be created
  • Description
    • A description of the environment that will be presented on the emdash™ front page

A completed Environment Wizard form would look something like this:

Click on 'Run Environment Wizard' and a new emdash™ job will be kicked off that will:

  • Create the emdash™ reference data to describe the environment
  • Create the fileshare folder
  • Create the relevant AD Group in Active Directory
  • Create a shell database on the database server
  • Grant permissions to the AD Group to the fileshare folder
  • Create the directories needed in the fileshare folder
  • Create 2 new VMs from the Azure template (if Azure is configured)
  • Copy the Endur/Findur binaries onto the servers
  • Install and configure one Endur/Findur runsite on each VM
  • Install and configure the ECOM Spread Daemon on the VM
  • Refresh the database with the backup file selected
  • Run the emdash™ Environment Refresh processes against the database to configure it into a new environment
  • Assign all Endur/Findur system accounts to the database
  • Create the relevant config files for the environment
  • Create the shortcuts needed to access the environments, for system accounts and Active Directory users

The environment is now available, and can be managed by emdash™ users/admins as normal.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk