Next and the final step is to configure the Customer Portal application.
1
Deploy HyperServer DLL and uniGUI Runtime
Customer Portal runs on HyperServer and IIS. Deploy the latest HyperServer DLL to the production server and install the matching uniGUI Runtime.
Also ensure the SSL DLLs in the HyperServer folder are the most recent versions and update them if needed.
After replacing the HyperServer DLL, restart the application pool.
2
Edit CFG and enable Node zero
Edit the application's CFG file and assign values to related fields. Make sure to enable persistent node zero so Node zero will always be available (Node Timer runs only when Node id is Node zero).
app.cfg
We used the non-secure URL http://socket.fmsoft.net for external_server_url because the dedicated WebSockets server and other applications run on the same computer. If they are on different hosts or you require encryption, use https://socket.fmsoft.net instead.
Assigning a unique value to app_domain is optional but recommended to avoid conflicts if you later host multiple applications or clusters on the same dedicated server.
3
Recycle application pool
After saving CFG changes, recycle the application pool so the new configuration takes effect.
4
Upload and deploy the portal application
Upload the portal application using the HyperServer control panel. After uploading, recycle all Nodes to ensure Node zero runs the latest uploaded version.
5
Verify the portal
Call the customer portal at this URL to verify configuration:
https://prime.fmsoft.net/userv/mportal.dll
You should see the portal page and confirm that the WebSocket timer is running.
6
Confirm secure WebSocket connection
Checking the page source should show a secure connection established to "wss://socket.fmsoft.net" as expected.
clip0329
Adding Another Application
At this point it is easy to add more applications that will use the dedicated WebSockets server.
1
Prepare the ISAPI application
Take the compiled ISAPI DLL of the application you previously configured and tested (see Testing with an ISAPI Application). Copy that DLL to the production server and configure IIS to use the application as usual.
2
Configure ExternalServerToken and AppDomain
Ensure the configuration for the new application has the correct ExternalServerToken value.
If deploying the same application multiple times in different folders, assign a different AppDomain to each deployment (for example: chat).
clip0274
3
Deploy and run the ISAPI DLL
Copy the DLL into the folder of an existing ISAPI application (for example, demo) and call the DLL in a browser to run the application.
clip0332
You should be able to call and run the application in a browser window:
clip0331
You can see how easily an existing dedicated WebSockets server can be shared among multiple applications.
