FrameWorX Server Location

To Open the FrameWorX Server Location Settings:

  1. Open the Workbench, then click on the Tools ribbon.

  2. Click on theFrameWorX Server Locationbutton, shown below, in the Tools section of the Tools ribbon.

FrameWorX Server Location Button

The FrameWorX Server Location window will appear within the Workbench.

FrameWorX Server Location Window

The window allows you to configure settings for your default FrameWorX Server location with use by the following clients:

For .NET Clients

Default Server Location - .NET Clients

  1. 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.

  2. 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.)

  3. 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 .NET Clients Tab Properties

  1. 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.

  2. 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.

  3. 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.

  4. If HTTP or HTTPS is selected, you can decide whether you will Use WebSockets by clicking on the checkbox.

  5. You can decide whether you will Use REST API by clicking on the check box.

  6. You can decide whether to 'Use Integrated Windows Authentication' for your selected Transport Protocol by clicking on the check box. Note that selection of the HTTPS transport protocol will enforce the use of integrated Windows Authentication.

  7. You can decide to 'Use Client Certificate (Subject Name or Thumbprint)', by clicking on the check box. If selected, you can enter the Subject Name or Thumbprint information in the text field below the check box.

  8. In the License Grace Period section, you can decide if you wish to Enable Grace Period. If selected, you can then set a Duration (in minutes) in the nearby text entry field.

  9. Click Save when you are done.

  10. Restart all client applications for these settings to take effect.

For WebHMI Clients

Default Server Location - WebHMI Clients

  1. 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.

  2. 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.)

  3. Click the Morebutton 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

  1. 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.

  2. 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.

  3. 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.

  4. If HTTP or HTTPS is selected, you can decide whether you will Use WebSockets by clicking on the checkbox.

  5. You can decide whether you will Use REST API by clicking on the check box.

  6. You can decide whether to 'Use Integrated Windows Authentication' for your selected Transport Protocol by clicking on the check box. Note that selection of the HTTP transport protocol for WebHMI Clients will restrict the use of integrated Windows Authentication and also that the selection of the HTTPS transport protocol will enforce the use of integrated Windows Authentication.

  7. You can decide to 'Use Client Certificate (common with .NET Clients)', by clicking on the check box. Note that if you had already selected the HTTP or HTTPS transport protocols, clicking this box will change the selected transport protocol to WS HTTP. The text entry field beneath the check box will remain greyed out for any transport protocol selection.

  8. Click Save when you are done.

  9. Restart all client applications for these settings to take effect.

For Mobile Clients

Default Server Location - Mobile Clients

  1. 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.

  2. 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.)

  3. Click the Morebutton 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

  1. 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.

  2. In the Transport section, select the Transport Protocol (choose either HTTP or HTTPS). 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.

  3. If HTTP or HTTPS is selected, you can decide whether you will Use WebSockets by clicking on the checkbox.

  4. You can decide whether you will Use REST API by clicking on the check box.

  5. Click Save when you are done.

  6. Restart all client applications for these settings to take effect. Note that this configuration only applies to Microsoft Windows 8 and Windows Phone 8 clients.

For Servers

Default Server Location - Servers

  1. 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.

  2. 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.)

  3. Click the Morebutton if you wish to set additional properties. The remainder of the window will look like the following image.

More Options Within the Server Tab Properties

  1. 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.

  2. 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.

  3. 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.

  4. If HTTP or HTTPS is selected, you can decide whether you will Use WebSockets by clicking on the checkbox.

  5. You can decide whether you will Use REST API by clicking on the check box.

  6. You can decide whether to 'Use Integrated Windows Authentication' for your selected Transport Protocol by clicking on the check box. Note that selection of the HTTPS transport protocol will enforce the use of integrated Windows Authentication.

  7. You can decide to 'Use Client Certificate (Subject Name or Thumbprint)', by clicking on the check box. If selected, you can enter the Subject Name or Thumbprint information in the text field below the check box.

  8. In the License Grace Period section, you can decide if you wish to Enable Grace Period. If selected, you can then set a Duration (in minutes) in the nearby text entry field.

  9. Click Save when you are done.

  10. Restart all client applications for these settings to take effect.

See Also:

Tools

Ribbon