Configure Services as Clustered Services
To configure Talisma Server on a Cluster Server, the Talisma Job Service, Talisma Webform Sync Service, and Talisma Health Check Servicemust be configured as clustered services.
Talisma Job Service
To configure Talisma Job Service on the Secondary Cluster Node and set it to the Online state, perform the following steps:
-
Type the following command in the Open field in the Run dialog box:
"<Drive name>:\Program Files\Common Files\Talisma Shared\<Database name>\TlJobSvc.exe" -Service- Name="TlJobSvc_ SQLVirtualServerName_MainDatabaseName"
For example,
"<Drive name>:\Program Files\Common Files\Talisma Shared\<Database name>\TLJobSvc.exe" -Service-Name="tlJobSvc_VSQL_INST1_tlMain"
The Talisma Job Service is configured on the Secondary Cluster Node.
-
From the Services window, ensure that the service is set to the Manual mode. To do so, perform the following steps:
-
Type services.msc in the Open field of the Run dialog box. The Services window is displayed.
-
In the right pane, right-click Talisma Job Service and select Properties from the shortcut menu. The Properties dialog box is displayed.
-
Ensure that the value in the Startup type field is Manual.
-
-
Export the following Talisma Job Service registry keys from the Primary Cluster Node, and then import the same to the Secondary Cluster Node:
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Talisma Job Service
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<tlJobSvc_ SQLVirtualServerName>_<MainDatabaseName>
-
-
Open the Failover Cluster Manager on the Primary Cluster Node. For steps to open the Failover Cluster Manager, see Opening and Viewing the Failover Cluster Manager.
-
In the left pane, navigate to <Cluster Server Name>, Roles.
-
Right-click Roles and select Configure Role from the shortcut menu. The High Availability Wizard - Select Role window is displayed.
-
Select Generic Service. The High Availability Wizard - Select Service window is displayed.
-
In the New Resource Wizard, select tlJobSvc_<Name of the Virtual SQL Server>_<Name of the Virtual SQL Server Instance>_<Name of the Database>. For example, tlJobSvc_CRM9SQL_tlMain.
-
Click Next.
-
In the Client Access Point window, specify a name in the Name field. The name must be unique.
-
Select a network in the Networks column and specify the IP address in the Address column. The IP address must be unique and must belong to the range specified in the Networks column.
-
Click Next.
If applicable, specify details in the Select Storage and Replication Registry Settings windows.
The Confirmation window is displayed.
-
Click Next.
The Configure High Availability window is displayed and the process of configuring High Availability begins.
-
Click Next.
The Summary page is displayed. Click on the View Report button to view the report of the configuration.
-
Click Finish.
The Talisma Job Service is added as a Cluster Resource and is displayed in the right pane of the Failover Cluster Manager window. By default, the status of the Resource is Offline.
-
In the Failover Cluster Manager window, right-click Talisma Job Service and select Properties.
The Talisma Job Service Properties page is displayed.
-
In the General tab, perform the following steps:
-
Type Talisma Job Service in the Name and Service name field. Delete the value in the Startup parameters field.
-
Clear the selection of the Use Network Name for computer name option. By default, this option is selected.
-
-
In the Dependencies tab, add SQL Server, SQL Server Agent, and Cluster Disk 1 in the Resource column.
-
In the Advanced Policies tab, select the Run this resource in a separate Resource Monitor option.
-
Click OK in the Talisma Job Service Properties page.
The Failover Cluster Manager is displayed.
-
In the Failover Cluster Manager window, right-click Talisma Job Service and select Bring online from the shortcut menu.
The Service is set to the Online state.
Talisma Webform Sync Service
To configure Talisma Webform Sync Service on the Secondary Cluster Node and set it to the Online state, perform the following steps:
-
Move all Cluster Resources to the Secondary Cluster Node.
-
Type the following command in the Open field of the Run dialog box:
<Target Drive>:\<Talisma Server Target folder>\Binn\MainDBName\TlOfSyncU.exe” /Service /ServiceName:"SQLVirtualName_MainDatabaseName" /User:"DomainName\UserName" /Password:"password of user" /Database:"MainDatabaseName" /Server:"SQLVirtualName"
For example,
"J:\TalismaServer\Binn\INST1tlMain\TLOfSyncU.exe" /Service /ServiceName:"VSQL_INST1_tlMain" /User:"crmtest" /Password:"Testlab4" /Database:"tlMain" /Server:"VSQL"
The Talisma Webform Sync Service is configured on the Secondary Cluster Node.
-
Export the following Talisma Job Service registry keys from the Primary Cluster Node, and then import the same to the Secondary Cluster Node:
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Talisma Job Service
-
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\<tlJobSvc_ SQLVirtualServerName>_<MainDatabaseName>
-
-
From the Services window, ensure that the service is set to the Manual mode. To do so, perform the following steps:
-
Type services.msc in the Open field of the Run dialog box. The Services window is displayed.
-
In the right pane, right-click Talisma Webform Sync Service and select Properties from the shortcut menu. The Properties dialog box is displayed.
-
Ensure that the value in the Startup type field is Manual.
-
-
Open the Failover Cluster Manager on the Primary Cluster Node. For steps to open the Failover Cluster Manager, see Opening and Viewing the Failover Cluster Manager.
-
In the left pane, navigate to <Cluster Server Name>, Roles.
-
Right-click Roles and select Configure Role from the shortcut menu.
The High Availability Wizard - Select Role window is displayed.
-
Select Generic Service.
The High Availability Wizard - Select Service window is displayed.
-
Select <SQLVirtualServerName>_<MainDatabaseName>. For example, VSQL_tlmain.
-
In the Client Access Point window, specify a name in the Name field. The name must be unique.
-
Select a network in the Networks column and specify the IP address in the Address column. The IP address must be unique and must belong to the range specified in the Networks column.
-
Click Next. If applicable, specify details in the Select Storage and Replication Registry Settings windows.
The Confirmation window is displayed.
-
Click Next.
The Configure High Availability window is displayed and the process of configuring High Availability begins.
-
Click Next.
The Summary page is displayed. Click on the View Report button to view the report of the configuration.
-
Click Finish.
The Talisma Webform Sync Service is added as a Cluster Resource and is displayed in the right pane of the Failover Cluster Manager window. By default, the status of the Resource is Offline.
-
In the Failover Cluster Manager window, right-click Talisma Webform Sync Service and select Properties.
The Talisma Webform Sync Service Properties page is displayed.
-
In the General tab, perform the following steps:
-
Type Talisma Webform Sync Service in the Name and Service name fields.
-
Delete the value in the Startup parameters fields.
-
Clear the selection of Use Network Name for computer name option. By default, this option is selected.
-
-
In the Dependencies tab, add SQL Server, SQL Server Agent, and Cluster Disk 1 in the Resource column.
-
In the Advanced Policies tab, select the Run this resource in a separate Resource Monitor option.
-
In the Policies tab, set the policy as per the requirement.
-
Click OK in the Talisma Webform Sync Service Properties page.
The Failover Cluster Manager window is displayed.
-
Right-click Talisma Webform Service and select Bring online from the shortcut menu.
The Service is set to the Online state.
Talisma Health Check Service
To configure the Talisma Health Check Service on the Secondary Cluster Node and set it to the Online state, perform the following steps:
-
Type the following command in the Open field of the Run dialog box:
Talisma Shared Folder\ TLHealthCheckU.exe /Service /ServiceName:"tlHC_ SQLVirtualName_MainDatabaseName" /User:"DomainName\UserName" /Password:"password of user" /Database:"MainDatabaseName" /Server:"SQLVirtualName"
For example,
"<Drive name>:\ Program Files (x86)\Common Files\Talisma Shared\<Database name>\TLHealthCheckU.exe" /Service /ServiceName:"tlHC_VSQL_INST1_tlMain" /User:"crmtest" /Password:"Testlab4" /Database:"tlMain" /Server:"VSQL"
The Talisma Health Check Service is configured on the Secondary Cluster Node.
-
From the Services window, ensure that the service is set to the Manual mode. To do so, perform the following steps:
-
Type services.msc in the Open field of the Run dialog box: The Services window is displayed.
-
In the right pane, right-click Talisma Health Check Service and select Properties from the shortcut menu. The Properties dialog box is displayed.
-
Ensure that the value in the Startup type field is Manual.
-
-
Open the Failover Cluster Manager on the Primary Cluster Node. For steps to open the Failover Cluster Manager, see Opening and Viewing the Failover Cluster Manager.
-
In the left pane, navigate to <Cluster Server Name>, Roles.
-
Right-click Roles and select Configure Role from the shortcut menu.
The High Availability Wizard - Select Role window is displayed.
-
Select Generic Service.
The High Availability Wizard - Select Service window is displayed.
-
Select <tlHC_SQLVirtualName>_<MainDatabaseName>.
-
Click Next.
-
In the Client Access Point window, specify a name in the Name field. The name must be unique.
-
Select a network in the Networks column and specify the IP address in the Address column. The IP address must be unique and must belong to the range specified in the Networks column.
-
Click Next.
If applicable, specify details in the Select Storage and Replication Registry Settings windows.
The Confirmation window is displayed.
-
Click Next.
The Configure High Availability window is displayed and the process of configuring High Availability begins.
-
Click Next.
The Summary page is displayed. Click on the View Report button to view the report of the configuration.
-
Click Finish.
The Talisma Health Check Service is added as a Cluster Resource and is displayed in the right pane of the Failover Cluster Manager window. By default, the status of the Resource is Offline.
-
In the Failover Cluster Manager window, right-click <tlHC_SQLVirtualName>_<MainDatabaseName> and select Properties.
The <tlHC_SQLVirtualName>_<MainDatabaseName> window is displayed.
-
In the General tab, perform the following steps:
-
Type Talisma Health Check Service in the Name and Service name fields.
-
Delete the value in the Startup parameters field.
-
Clear the selection of the Use Network Name for computer name option. By default, this option is selected.
-
-
In the Dependencies tab, add SQL Server, SQL Server Agent, and Cluster Disk 1 in the Resource column.
-
In the Advanced Policies tab, select the Run this resource in a separate Resource Monitor option.
-
Click OK in the Talisma Health Check Service Properties page.
The Failover Cluster Manager is displayed.
-
In the Failover Cluster Manager, right-click Talisma Health Check Service and select Bring this resource online from the shortcut menu.
The Service is set to the Online state.