Farshad Mohajeri

Since you are using a secure URL (https) in your slave, you must copy SSL DDLs into master's folder as stated in our docs.

You can run your app either in Service Mode or in IIS mode. Both are acceptable. In service mode you can assign a global IP and open port 8077 to public -OR- run your Service app on port 80. In IIS mode you need to use the DLL version.

url=http://10.32.128.147:8077 global_url=https://gepweb01.mydomain.com.br/gepweb_d.dll The above url paramater is no longer valid. Here is the correct config: url=https://gepweb01.mydomain.com.br/gepweb_d.dll global_url= Since both URLs are the same you only need to assign the url parameter.

You can switch to Mode-2 gradually. You can start with one ServerNode and go on.

What are those doubts?

Delphi adds it to your project when you create a VCL form at design time.

I sent you a PM.

Does it work if you run the app directly?

Manual updated.

Hello, Actually, there is no window. We leave our subscribers free to choose the renewal date. One of the advantages of the uniGUI subscription.

Hi, Name of your program is uniTabControl. It is also name of one of our units. Change it to something else and it will compile.

Estimated release date: Next Monday (or sooner)

We are trying to make sure that this will happen! :) Mode-2 (UrlRedirect) adopts a simpler working principle compared with other two modes. Master Server's job is to redirect URL to one of the Slaves and once this happens all traffic goes to that slave server. The tricky part is to make sure that all URLs will point to the master server when a session is expired, terminated or restarted. Another thing is to make sure that a user can not directly start a session on a slave server.

We are still testing. The most tricky part is that all failed, timed out, restarted or naturally terminated sessions should be redirected back to the master server! Direct URL access should be disabled and re-routed to the master server! It is the part that we are still implementing & testing...!

Hello, There can be three recommendations for such situations: 1) Check Pool settings: http://www.unigui.com/doc/online_help/iis_7_0.htm 2) Set your Pool Identity to LOCALSYSTEM http://www.unigui.com/doc/online_help/using-a-different-account-for-.htm 3) Switch to HyperServer

We are trying to finish it!

I will try to find a workaround.

Users should be encouraged to connect to main URL only and not bookmark any sub-URL in the domain.

If the slave server is disabled and user tries connect to it then re-directing to main server will not work! That said, your concerns about load balancing remains valid.

Why do you want to prevent users from doing this?

Each ServerNode will be exposed to the global internet. There will be no difference between a regular uniGUI server and other ServerNodes. You can deploy them as ISAPI dlls, so IIS will add an additional security barrier.

Mode 3 (URL Redirect) is under test. We will publish it in next build.

Hello, Server Farm comes with three different operation modes. Pass Through Direct Url Redirect Mode 1) Pass Through (Implemented) In "Pass Through" mode all requests passes through the master HyperServer. This includes all file requests. Which means your master server can become quite busy when there is a momentary high load. In this mode each slave HyperServer instance communicates with its own Nodes privately. Slaves and related Nodes are isolated from the public access. It is the slowest mode, but the easiest for uniGUI developers to implement, manage and maintain. Mode 2) Direct (Not implemented) In this mode again all traffic is handled by the master HyperServer, but it will directly communicates with all Nodes from other HyperServer instances. This will improve performance, as the traffic are not relayed through the middle HyperServers. Mode 3) Url Redirect (Not implemented) In this mode each new session is redirected to one of the slave HyperServers. It will be done at URL level, so once the session is redirected, the master HyperServer will not handle the related traffic. For each slave HyperServer Node the traffic is handled directly by that HyperServer. This is the fastest operation mode, but this requires you to open all of your salves to the internet and assign them public URLs.

Have you enabled Pooling on your DB connections.

More questions: 1) Do you have a continuous Timer on your app? If yes what is the interval? 2) Do you have a single Database server for all of the sessions?