COTS application deployment and installation
Application package structure
After an application development is completed, it is a EAR package. If it is a simple web application, you only need to be one or more WAR packages. Each WAR Pack / Web-INF / SQLScripts, stores the application, the application needs to be created, and the data initialization script
EJB proxy mode
In the EJB proxy mode, all BLCs are deployed on the Application Server, and the client calls business logic as the EJB Client. This mode framework provides a business logical call service to the client as a pure business logic server, and does not provide a logical service.
Servlet call mode
The servlet call mode does not require Application Server, a complete deployment of the COTS application. This method can only support web clients
Joint mode
In the joint mode, BLC is deployed on Application Server, and only some of the necessary application frameworks are deployed on the Web Server. This mode supports different types of clients
Application installation
The application's EAR package or WAR package is first deployed by the application server, and then the super user will be in the system to enter the system (assuming in local operation): http: // localhost: 8088 / webapp / jsp / sys / install. System Automatically perform database-related initialization operations, after execution, the system automatically refreshes various caches of the application, and the application enters formal operation.
