Connection Information

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.

Connection Type

Configuring IIS as a load balancer – PB Docs 2022 – PowerBuilder Library

Configuring IIS as a load balancer – PB Docs 2022

Configuring IIS as a load balancer

This tutorial will walk you through configuring IIS as a load
balancer to direct client requests to a group of PowerServer Web APIs. You
will have to configure IIS to support sticky sessions.

Step 1: Follow the sections below to install IIS and configure IIS
as a reverse proxy server.

Step 2: Configure IIS as a proxy server and load balancer which
redirects requests to the PowerServer Web APIs group.

  1. Create a new website “proxyserver” which binds to port number
    8080. You can also use the existing Default Web Site (with port
    80).

  2. Set the application pool to “No managed code”.

    1. Select Application Pools in
      the Connections pane.

    2. Right click “proxyserver” in the list of application pools
      and then select Basic
      Settings
      .

    3. In the Edit Application
      Pool
      window, select No Managed
      Code
      from the .NET CLR
      version
      list box, and then click OK.

    cluster_2.png

  3. Set the cookie timeout value to a value equal to or greater than
    the session timeout value which is 3600 seconds (60 minutes) by
    default.

    cluster_11.png

    cluster_12.png

  4. Create a server farm that includes the group of PowerServer Web
    APIs.

    1. Right click Server Farms in
      the Connections pane, and then
      select Create Server Farm.

      The Server Farms node will
      not be available if “IIS Application Request Routing (ARR)” is not
      installed.

    2. In the Create Server Farm
      window, specify the server farm name and then click Next.

    3. Add the server instance by inputting the host name or IP
      address of PowerServer Web APIs, clicking Advanced settings to specify the port
      number of PowerServer Web APIs, and then clicking Add.

    4. Repeat the previous step to add the server instances one by
      one and then click Finish.

    5. Select Yes when asked
      whether to automatically create a URL rewrite rule.

    cluster_3.png

  5. Modify the URL rewrite rule.

    1. Select the server in the Connections pane and then double click
      URL Rewrite in the features view
      to open the feature.

      cluster_4.png

    2. Select the “ARR_PowerServerGroup_loadbalance” rule (this
      rule is automatically created when you create the server farm) and
      then click Edit from the
      Actions pane.

      cluster_5.png

    3. In the Edit Inbound Rule
      window, expand the Conditions
      block and then click Add. In the
      Add Condition dialog, input
      “{SERVER_PORT}” to the Condition
      input
      field and “8080” (port of “proxyserver” website)
      to the Pattern field, and click
      OK.

      cluster_6.png

    4. Click Apply for the changes
      to take effect.

      cluster_7.png

  6. Configure Server Affinity of
    the server farm to support sticky sessions.

    1. Select the “PowerServerGroup” server farm in the Connections pane, and then double click
      Server Affinity in the features
      view to open the feature.

      cluster_8.png

    2. Select the check box of Client
      affinity
      , keep the Cookie
      name
      as default “ARRAffinity”, and then click
      Apply.

      cluster_9.png


Document get from Powerbuilder help
Thank you for watching.
Was this article helpful?
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x