AgileEAS. NET platform development instance-smart upgrade and server deployment

Opening

The previous article describes how to switch between the distributed access service and the normal access mode. Next we will analyze how to achieve Remote Application Server deployment, and how to intelligently update the client, our specific implementation ideas

Path, which can be displayed in the following figure:

Next we will analyze the specific configuration process. In the future, we will analyze the specific implementation process and ideas of the smart client. This article will not cover it, but will introduce AgileEAS in the future. NET,

I will explain it in detail.

Outline

1. Configure the Application Deployment Server.

2. Package local client programs

Configure the Application Deployment Server

In general, the implementation of the smart client of an application is an Application Deployment Server. Relevant publishers use release tools to deploy the latest assembly or components to be updated on the server, then log on to the client

When the client communicates with the server, the client automatically checks whether the service needs to be updated. if the service needs to be updated, the client executes the Assembly update operation, AgileEAS. the idea of implementing the smart client on the NET platform is as follows:

The process is similar, but there are some changes in details. For example, if the client matches the Assembly list file on the server and determines the assembly to be updated, the client downloads the assembly, and after the Assembly is updated, start interface

You can restart the application after you click Update. However, it may be a little slow to download a large number of files during the first update, however, the subsequent process is very fast, because

During packaging, the Assembly itself is very small. The dll files of all applications are on the server. By downloading the Assembly from the server side to the local computer, the module can be accessed and called.

Subsequent non-first access:

The above is the specific Assembly update process. I do not know whether the statement is clear or clear. I hope you can leave a message to reply to this question.

Next, let's take a look at the specific configuration of the deployed server.

1. Find the EAS. AppServer Folder:

2. Related directory structure in the folder:

3. Click the "config" folder to view the functions and related content of the files in the folder:

4. Let's take a look at the configuration file information we need to modify. We just need to modify the "SmartClient. xml" file:

5. The prerequisite for using the above file configuration is that the distributed service has been installed; otherwise, the upgrade service configuration of the smart client cannot be completed. In this way, the configuration file of the server is modified. Let's take a look at it,

How to configure the specific assembly list file and update the Smart Client through the release tool provided by the platform.

6. Find the server deployment tool:

7. Find the following application in the folder:

8. The following page is displayed after running:

Since the specific functions of these different configuration items have been analyzed above, let's take a look at the specific steps of our application deployment:

9. First browse "initialize configuration file"

Click "Browse", select the "WebConfig. config" file under the config folder, and click "LOAD:

10. Configure assembly information:

11. Click "Configure assembly" and the following complex page appears. Let's parse the specific functions of this module.

12. Select the "SmartAssembly. config" file under the "config" directory and click "LOAD". The effect is as follows:

13. Click "Scan folder" to load all the Assembly files in the Assembly Folder:

14. Click "save" to synchronously write the list of scanned assemblies back to the "SmartAssembly. config" file:

Client Configuration

After the configuration of the server segment is described above, let's take a look at the client configuration and application packaging, configure related application configurations.

1. Copy the following assembly to the new folder "SmartClient". The following assembly is a required assembly for packaging the Smart Client:

This component is a required dll for the resource management platform.

2. modify the configuration file easeas.explorer.winclient.exe. config ":

Modify the address to the server you want to configure.

.

3. Make the necessary assembly we copied into an installer so that it can be conveniently deployed and applied. The following describes how to package the files and client programs we configured earlier.

4. Add the corresponding assembly or file to the package file:

5. Select "add assembly ":

6. Click "OK:

7. Add the "file" to add the configuration file:

8. Add the necessary resource management Platform Plug-in "EAS. explorer. res. dll file, which is a resource file of the resource management platform, such as a style image on the login page.

9. In this way, the core assembly inside the installation and deployment file of the core client is all included. Now we can start packaging. We can configure some packaging details and click Generate, to generate the installer

.

10. Click "properties". After the output file name is modified, click "OK ":

11. Select a project, right-click the project, and click "generate" or "regenerate ":

12. After the generate operation is executed, the following file is output.

We only use the MSI file and double-click it to run it. The installation prompt box is displayed. The installation is complete by default.

13. Find the Startup Program in the installation directory:

Run the eas.explorer.winclient.exe application in double-click mode. We will observe the changes in the Assembly file in this folder:

Enter the password "sa" or "1" and click "OK ":

If the following prompt appears:

Please package the Assembly during packaging, so you don't have to worry about the client. If you want to solve this problem, copy a dll Assembly from the downloaded assembly package to this directory:

Re-run the winclient.exe application and enter the following main interface:

This completes the update and interaction between the Smart Client and the application directly deployed on the server. The specific database access is completely completed through distributed communication.

In the above process, let's take a look at the assembly files downloaded when we access the resource management platform, from the Deployment Server:

In this way, the on-demand download method is used to reduce the difficulty of Application Deployment. by deploying a server for one-click release and multiple clients, you may be worried about concurrency and other stress issues, generally, the client

The version of the Assembly between the client and the server will be matched during login. If they are inconsistent, the version will be downloaded. Otherwise, the version will not be downloaded. Generally, this is not a problem.

Summary

In this way, we can complete the deployment and application of basic smart clients through the simple configuration above. When deploying the software environment for the customer, we only need to use the following installer for the customer:

Directly install the application to complete the specific communication service. The Administrator only needs to modify the configuration of the server segment, and the client does not need any configuration, but it may have a disadvantage, if the configuration on the server is incorrect,

All clients cannot complete access.

We have to make a trade-off about the specific quality. Different scenarios are different. Because of my limited level, there are still errors in understanding the system, or I have insufficient knowledge of the system platform, error. Please help

Point out, or you have better ideas and understanding about the current tool. Thank you!

Pharmacy system source code

 

Other articles

More articles about the AgileEAS. NET development platform are provided here.

1. official blog: AgileEAS. NET agile software development platform

3. What about AgileEAS. NET platform-document publishing?

4. Use Cases of the AgileEAS. NET platform tool for data prototype designer

5. More...

More communication

Official blog: http://www.smarteas.net/

Http://www.agilelab.cn/

If you have any questions about using the AgileEAS. NET development platform, use the following contact methods or communication methods.

1. Telephone-Email:

He gozhou: hegezhou_hot@163.com mobile phone: 18691480181 blog: http://www.cnblogs.com/hegezhou_hot/

2. QQ chat group:

308961614 Network Name: h.o. T