I. Product Overview 1. The defects of the traditional two-storey software · Connection complex, management difficulties · A large number of information, and the total information private information coexistence · Various resource integration · Requirements Although, from development, maintenance, 100-150 exceeds When the client, each client is sold in non-linear growth, and the data is more than constant, the maintenance cost is significantly increased. Unlike problems with hardware upgrades. 2. Three-layer software architecture and middleware data resources and clients are separated by "Application Server", focusing on the application service request, not a data request. Program loading, startup, memory management ... High performance handling and shielding mismatched platform In three-level structure, the client's direct access to the data source is replaced by the application's request, the client access is the application, by The application queries and accesss the data. The third-level architecture requires the initial investment than the second-level architecture, but it has high long-term scalability. With the number of customers, the increase in the complexity of the application, the cost of development and maintenance is basically linear growth. .
Second, the software architecture 1.Websphere Administrator Server Administrative Console Administrative Database Administrative Server Stability: Application Server-> Administrative Server-> Nanny is managed. Safety: Safety authentication management of Web static resources and dynamic resources. Scalability: horizontal extension (servers) and vertical extensions (CPU increase, etc.). Integrated standards and openness. 2.Weblogic has only a daemon, all application servers, and Application Server is similar.
Third, the Java platform supports EJB: WebSphere support 1.1, WebLogic support 2.0, but does not really support 2.0, no support for host resource CMP types such as CICS, IMS, SAP, can participate in WLE EJB things in WLS, Web Gain provides a very weak EJB development environment without providing RMI / IIOP support. RMI / IIOP: EJB1.1 Optional, 2.0 must. WebLogic uses protocol T3, slow 4 letter than WebSphere
Fourth, performance 1. Dynamic content cache (WebSpherer is) 2. Vertical extension: The latter is reduced in the CPU 4, and the peak is reached at 12CPU. 3. Level extension: The session of the multi-server maintained, the former uses the database, the latter is transferred with multi-point transmission, and it is possible to lose the session when the crash is dead. 4. Data inventory: WebSphere's SQL uses pre-compiled, WebLogic insolete.
