To Open the FrameWorX Server Location Settings:
Click on the FrameWorX button, shown below, in the Configure Server section of the ReportWorX Express ribbon.
FrameWorX Button
The FrameWorX Server Location window will appear, as shown below.
FrameWorX Server Location Window
The window allows you to configure settings for your default FrameWorX Server location with use by the following clients:
Default Server Location - .NET Clients
In the Default Server Location section, in the Primary Server/Cloud Connector text field, type the node name of the FrameWorX Server. Enter localhost to specify the local computer.
If you wish to enable redundancy, specify the Secondary FrameWorX Server location in the Secondary Server text field.. The secondary server will take over if the primary server becomes unavailable. (Leave this field empty to switch off redundancy.)
Click the More button if you wish to set additional properties.
More Options Within the .NET Clients Tab Properties
If you specified a Secondary default server same, for the optimal use of resources, you can put a check mark in the Enable Load Balancing check box. For a complete description of important load balancing information, refer to the Platform Services Configuration topic.
Also, if you specified a Secondary default server name, you can put a check mark in the Auto switch back to primary check box if you want the clients to automatically switch back to the primary server when the primary server becomes available again. If you leave this option unchecked, it will not automatically switch back to the primary server. Instead, you will have to switch it back manually when the server is available. (For instructions for manually switching over, refer to the Monitoring Redundancy Using MonitorWorX topic.) Enter a Heartbeat Rate (in seconds) in the text entry field. Enter a number of Allowed Missed Heartbeats (the number of signals lost in a row that should be considered as a connection failure) in the text entry field.
In the Transport section, select the Transport Protocol (choose either HTTP, HTTPS, WS HTTP or NET.TCP). Note that a proper Port number is selected for each protocol. If you change the port number here, you must also change it for the FrameWorX Server. This must be done manually.
For HTTP and HTTPS, you can decide whether you will Use REST API by clicking on the check box.
You can use the pulldown menu to select Client Authentication for your selected Transport Protocol (None, Integrated Windows Authentication, Client Certiificates).
For the selected transport protocols that support it (HTTPS, WS HTTP), if you select Client Certificates, you can decide to use the Select client certificate by pulldown menu to decide between Thumbprint, Subject Distinguished Name, or Issuer Distinguished Name. Once your selection has been made, you can enter the specific info in the text entry field below or click on the ellipsis [...] button to open the Windows Security window and select a certificate.
Click Save when you are done.
Restart all client applications for these settings to take effect.
Default Server Location - WebHMI Clients
In the Default Server Location section, in the Primary Server/Cloud Connector text field, type the node name of the FrameWorX Server. Enter localhost to specify the local computer.
If you wish to enable redundancy, specify the Secondary FrameWorX Server location in the Secondary Server text field. The secondary server will take over if the primary server becomes unavailable. (Leave this field empty to switch off redundancy.)
Click the More button if you wish to set additional properties. The remainder of the window will look like the following image.
More Options Within the WebHMI Clients Tab Properties
If you specified a Secondary default server same, for the optimal use of resources, you can put a check mark in the Enable Load Balancing check box. For a complete description of important load balancing information, refer to the Platform Services Configuration topic.
Also, if you specified a Secondary default server name, you can put a check mark in the Auto switch back to primary check box if you want the clients to automatically switch back to the primary server when the primary server becomes available again. If you leave this option unchecked, it will not automatically switch back to the primary server. Instead, you will have to switch it back manually when the server is available. (For instructions for manually switching over, refer to the Monitoring Redundancy Using MonitorWorX topic.) Note that Hearbeat parameters are common with .NET Clients.
In the Transport section, select the Transport Protocol (choose either HTTP, HTTPS, WS HTTP or NET.TCP). Note that a proper Port number is selected for each protocol. If you change the port number here, you must also change it for the FrameWorX Server. This must be done manually.
For HTTP and HTTPS, you can decide whether you will Use REST API by clicking on the check box.
You can use the pulldown menu to select Client Authentication for your selected Transport Protocol (None, Integrated Windows Authentication, Client Certiificates).
For the selected transport protocols that support it (HTTPS, WS HTTP), if you select Client Certificates, you can decide to use the Select client certificate by pulldown menu to decide between Thumbprint, Subject Distinguished Name, Issuer Distinguished Name, or User popup. Once your selection has been made, you can enter the specific info in the text entry field below or click on the ellipsis [...] button to open the Windows Security window and select a certificate.
Click Save when you are done.
Restart all client applications for these settings to take effect.
Default Server Location - Silverlight Clients
In the Default Server Location section, in the Primary Server/Cloud Connector text field, type the node name of the FrameWorX Server. Enter localhost to specify the local computer.
If you wish to enable redundancy, specify the Secondary FrameWorX Server location in the Secondary Server text field. The secondary server will take over if the primary server becomes unavailable. (Leave this field empty to switch off redundancy.)
Click the More button if you wish to set additional properties. The remainder of the window will look like the following image.
More Options Within the Silverlight Clients Tab Properties
If you specified a Secondary default server same, for the optimal use of resources, you can put a check mark in the Enable Load Balancing check box. For a complete description of important load balancing information, refer to the Platform Services Configuration topic. Enter a Heartbeat Rate (in seconds) in the text entry field. Enter a number of Allowed Missed Heartbeats (the number of signals lost in a row that should be considered as a connection failure) in the text entry field.
In the Transport section, select the Transport Protocol (choose either HTTP, HTTPS or NET.TCP). Note that a proper Port is selected for each protocol. If you change the port number here, you must also change it for the FrameWorX Server. This must be done manually.
You can use the pulldown menu to select Client Authentication for your selected Transport Protocol (None, Integrated Windows Authentication, Client Certiificates).
Click Save when you are done.
Restart all client applications for these settings to take effect.
Default Server Location - Mobile Clients
In the Default Server Location section, in the Primary Server/Cloud Connector text field, type the node name of the FrameWorX Server. Enter localhost to specify the local computer.
If you wish to enable redundancy, specify the Secondary FrameWorX Server location in the Secondary Server text field. The secondary server will take over if the primary server becomes unavailable. (Leave this field empty to switch off redundancy.)
Click the More button if you wish to set additional properties. The remainder of the window will look like the following image.
More Options Within the Mobile Clients Tab Properties
If you specified a Secondary default server same, for the optimal use of resources, you can put a check mark in the Enable Load Balancing check box. For a complete description of important load balancing information, refer to the Platform Services Configuration topic. Enter a Heartbeat Rate (in seconds) in the text entry field. Enter a number of Allowed Missed Heartbeats (the number of signals lost in a row that should be considered as a connection failure) in the text entry field.
In the Transport section, select the Transport Protocol (choose either HTTP or HTTPS). Note that a proper Port is selected for each protocol. If you change the port number here, you must also change it for the FrameWorX Server. This must be done manually.
Click Save when you are done.
Restart all client applications for these settings to take effect. Note that this configuration only applies to clients running MobileHMI on the Windows platform.
Default Server Location - Servers
In the Default Server Location section, in the Primary Server/Cloud Connector text field, type the node name of the FrameWorX Server. Enter localhost to specify the local computer.
If you wish to enable redundancy, specify the Secondary FrameWorX Server location in the Secondary Server text field.. The secondary server will take over if the primary server becomes unavailable. (Leave this field empty to switch off redundancy.)
Click the More button if you wish to set additional properties.
More Options Within the Mobile Clients Tab Properties
If you specified a Secondary default server same, for the optimal use of resources, you can put a check mark in the Enable Load Balancing check box. For a complete description of important load balancing information, refer to the Platform Services Configuration topic.
Also, if you specified a Secondary default server name, you can put a check mark in the Auto switch back to primary check box if you want the clients to automatically switch back to the primary server when the primary server becomes available again. If you leave this option unchecked, it will not automatically switch back to the primary server. Instead, you will have to switch it back manually when the server is available. (For instructions for manually switching over, refer to the Monitoring Redundancy Using MonitorWorX topic.) Enter a Heartbeat Rate (in seconds) in the text entry field. Enter a number of Allowed Missed Heartbeats (the number of signals lost in a row that should be considered as a connection failure) in the text entry field.
In the Transport section, select the Transport Protocol (choose either HTTP, HTTPS, WS HTTP or NET.TCP). Note that a proper Port number is selected for each protocol. If you change the port number here, you must also change it for the FrameWorX Server. This must be done manually.
For HTTP and HTTPS, you can decide whether you will Use REST API by clicking on the check box.
You can use the pulldown menu to select Client Authentication for your selected Transport Protocol (None, Integrated Windows Authentication, Client Certiificates).
For the selected transport protocols that support it (HTTPS, WS HTTP), if you select Client Certificates, you can decide to use the Select client certificate by pulldown menu to decide between Thumbprint, Subject Distinguished Name, or Issuer Distinguished Name. Once your selection has been made, you can enter the specific info in the text entry field below or click on the ellipsis [...] button to open the Windows Security window and select a certificate.
Click Save when you are done.
Restart all client applications for these settings to take effect.
See Also: