Unigui trial notes (9)

Unigui execution programs can be deployed in three forms

1. ISAPI Mode

Deployed in IIS or Apache. The program is compiled in the DLL format. If you have not tried it, prepare a dedicated test later.

 

2. Standard execution file Mode

Compiling software into an independent EXE file, including web services and business content, is the simplest deployment method of unigui. The most important feature of this method is that code tracking can be performed. Similar to debugging of General EXE programs, debugging is very convenient in debug mode. After running EXE, you can directly open the page for testing. You can open the service monitoring page through the icon on the taskbar to monitor the running status of the service program, such:

 

3. Windows Service Mode

Compile the software into the service mode in windows and start it automatically. From the perspective of engineering documents, it is slightly different from general program engineering documents, which is not detailed here. In addition, a servicemodule is added to the project. the PAS file and the corresponding form file. This module defines some properties of Windows Service, including the name and dependency. I only modified the displayname attribute and used the default values for other properties.

Note: do not try to modify the file name and module class name. Otherwise, the system will not be able to recognize the file and the compilation will pass, but it will not be able to start when running, it is estimated that the internal code is dead.

Register a service in the same way as a general Windows service program. Use the command line to add the-install parameter, and use the-uninstall parameter for logout, as shown below:

Myserviceapp-install

Myserviceapp-uninstall

Start with the command line, as shown below:

Net start uniservicemodule

Uniservicemodule is the class name of the module.T

 

In practical application, I used two projects, one of which is the standard execution file mode, debug + Win32 for program debugging. The other project adopts the Windows service mode, release + win64, used for deployment and operation. In the case of a small number of clients (<5), the running effect is very good. I opened a 20 thousand-record table and displayed it on 50 pages by page, from the data acquisition to the first page of data display, the local area is about 3 ~ In the range of 4 seconds, the cloud server (bandwidth: 10 MB) is about 6 to 200 Kbyte/second when the file is actually detected ~ 7 seconds. It takes about 1 second to obtain the second page of data.

 

The most important thing is that this service program is deployed on many client terminals (300 ~ 500) the performance, according to the author, does not depend on the program, but on the server hardware conditions. We plan to use winrunner for a test in the near future to see the specific results, mainly including the performance of ISAPI and Windows service.

Unigui trial notes (9)