Emdash and Endur/Findur Services Manager

The Environment Refresh process in emdash updates the Servers and Service Accounts that are allocated to the 'target' environment, replacing those that were stored in the 'source' database.

This is an important step to move from one Endur/Findur environment to another, and is performed in the 'Endur Refresh' step in the 'Environment Refresh - Endur' workflow, as below.


This point in the step is looking at some specific reference data in emdash, and comparing it to the Endur/Findur information in the Endur/Findur database.  It is then using the emdash reference data to replace Endur/Findur data.

Emdash Data

Service Allocations

We map Services to the environment - so we know what the Services are, which Server they are mapped onto, and what Service Account they will be executed under.


In the screen above, you can see that the Service called 'OpenLink_Endur_x64_001' is mapped to the server called 'acme-DEMO22-1'.  When the Endur/Findur windows service is installed on that server, it will run under the service account 'acme-DEMO22-1_1'.


As the screen above is an Allocation of a Service to an Environment, we can see more details about the Services themselves in Ref Data Manager - Services:


By applying a filter for the Service named 'OpenLink_Endur_x64_001' we can see a bit more detail about how the Service will be applied to Endur/Findur:

  • Service Name and Display Name are used when creating the Endur/Findur window service on the server;
  • Logical Name is used to match with a run site name in Endur.  It should be the same as the 'Server Node Name' in Endur/Findur's Service Manager screen (see below).
  • Service Type is used to signify that it is an Endur service.  This is not used to match anything within Endur itself and is only used internally within emdash.
  • Application User Name is also used as part of the process for installing and configuring the Endur/Findur windows service.  It is used to specify the Endur username/password fields as part of the Endur/Findur installation process
  • Service Code Bit signifies whether that run site should be running the x64 or x86 versions of Endur, and it will get the binaries lined up for the Windows Services accordingly.

So, it is really important that you look at the data set up in Services, and align with the data in Endur/Findur's Server Management screens as part of the emdash setup process.

Endur/Findur Data

Services Manager

As above, we use the Logical Name value in the Services reference data to match Server Node Name in Endur/Findur.


You can see that 'Appserver_x64_001' has been matched against the emdash Service ref data (via the Service Allocation) and we have replaced the OS Login Name and Host Name associated with the run site within Endur/Findur via the Environment Refresh Process.

Some customers will have up to 50 run sites mapped to an Endur/Findur environment.

However, they often don't have the number of run sites allocated to a smaller, test or development environment.

If this is the case, the emdash process will 'wipe out' the data associated with them - so it doesn't keep data from the Source environment in the Endur/Findur database.

Instead, it will replace the Server and User details with 'NA' as can be seen above.

Mapping Overview

Emdash_Service_Ref_Data-Endur_Runsite_Mapping.png(Click on the image above for a high resolution version)


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