Electrolytic Tinplate And Tfs,Quality Tinplate Sheets,Tinplate Lacquered,Tinplate Strips CHANGZHOU AVEC PACKING TECHNOLOGY CO., LTD , https://www.avecintl.com
Based on this, this paper proposes the use of component coupling method to design application system architecture and implement technical solutions. The system applies the B/S three-tier structure, adopts the J2EE technical specification, and follows CORBA, COM and EJB component development standards. It is a technical package solution with prominent characteristics and fully applicable power marketing management information system.
1 system architecture design Component technology is essentially a software development tools and methods, its purpose is to achieve software reuse and function expansion. The use of component technology does not require the development and design of multiple application systems. Instead, it can analyze the core functions of a multi-mode system and rationalize software reuse, enabling the developed system to effectively support different application modes at the same time. Componentized programming methods inherit and develop object-oriented programming methods, applying object-oriented technology to system design, and enabling application systems to be built in a component-combined manner. Componentized programming approaches emphasize software reusability and high interoperability, focusing on component definition, construction, and assembly. Its reusability means that the provided functions can be used for multiple systems; interoperability means that the components from different sources can coordinate and communicate with each other to complete more complicated functions [2–4].
In order to build a high-level power marketing management information system, this paper proposes the idea of ​​building an application system with component coupling. The use of components to coordinate, call each other or independently operate, cooperate and complete the modular and systematic application functions, this component application method is also known as component coupling method. According to the different relations between components, they can be divided into tight coupling and loose coupling. This method can quickly design and develop components, implement components to be deployed organically to application servers, and improve the operating efficiency and performance of application systems. The features of this method are: programming language and development environment are independent; components have the characteristics of transparent location and transparent process; good scalability, high reusability, and can provide system-level public services; components can be tested individually and are easy to maintain. Establishing an application system by means of component coupling can not only shorten the development cycle of software products, improve the stability and reliability of the system, but also support the reuse of components and improve system scalability, which can not only reduce system maintenance costs, but also reduce system 2 Development costs.
1.1 System Architecture The multi-layer B/S structure application mode conforming to the Java 2 Enterprise Edition (J2EE) technical specification [3] is logically divided into four levels: the client layer, the Web service layer, the application service layer, and the database service layer. The client layer is mainly responsible for human-computer interaction; the Web service layer is mainly responsible for the centralized delegation and information distribution of access requests to the client layer via the HTTP and HTTPS protocols; the application service layer is mainly responsible for the centralized management of application logic, ie transaction processing and logic operation processing. And so on, the key response to the component calls of the CORBA/IIOP technology standard that implements mutual access to objects on the Internet can be divided into multiple according to the specific services they handle; the database service layer is mainly responsible for the storage and organization of data and the distribution of databases. Management, database synchronization and backup. Based on this guiding ideology, combined with the functional requirements of the power marketing management information system, an enterprise application system architecture as shown in Figure 1 was designed using the component coupling method. 
In Figure 1, the common components are abstracted functional objects, complete the transaction processing flow and data flow function partitioning, data mapping and other work, including report display, file system, report labels, dynamic graphics, data objects, transaction processing and other components; Dedicated components are abstracted power marketing management information system functional modules, complete business processing and report management, including industry expansion report equipment, electricity bills, power supply solutions, energy metering, electricity inspection, quality management, integrated services, charges Accounts and arrears such as liquidated damages and other components.
1.2 Application Server Deployment Architecture The application server architecture design is shown in Figure 2. 
In order to provide the required services of the application system and reduce the amount of code writing to the underlying architecture services, it is necessary to comply with certain standards and specifications in the architecture and implementation process, such as mature CORBA, COM/DCOM, JavaBean/EJB and other components. Standards, but also the system application components required to be organically deployed to the application server architecture. According to the component coupling method and the relationship between common components and special components required in the system application, it can be said that the relationship between the common component and the dedicated component must be tightly coupled, and the relationship between the dedicated components is loose coupling.
2 System Implementation Key Technologies 2.1 Component Coupling Technology Component-based software design and development process is currently one of the mainstream technologies for building software systems, allowing system developers to use greater flexibility and new methods to design and implement enterprise application systems. . The component coupling method is to use the components to coordinate with each other, call each other or operate independently, cooperate and complete modular and systematic application functions. According to the different relations between components, they can be divided into tight coupling and loose coupling.
a. Tightly coupled components are called tightly coupled with each other, such as the relationship between the database connection pool components and the execution of database operation components, transaction logic components and report generation components. The coupling relationship between components that are called and coordinated from the data flow is the tight coupling of components. Figure 3 shows the relationship between the three components. The working methods of these three kinds of components are as follows: 1 Database connection pool component: Complete the connection of the database with connection reuse. 2 Execute the SQL component: Connect to the database through the database connection pool component, complete the data logic processing, and return the processed result set to the XML generation component. 3XML generation component: read the report display format tag from the XML template library, generate HTML/XML pages in conjunction with the data sent from the SQL component, and return to the client display by the WebServer. 
b. The system functions of the loosely coupled components that operate independently from each other and complete the modular cooperation. This relationship is called loose coupling. In the realization of the functions, it is reflected in mutual cooperation to form a modular and systemic loose structure and close integration of functions. The relationship, for example, from the modular, system components on the coupling between the situation. The relationship between the three kinds of database operation components (executing SQL components, executing transaction processing components, execution data window components) and report page generation components (XML generation components, report dynamic generation components) is shown in FIG. 4 . 
Executing the SQL component, executing the transaction processing component, and executing the data window component are the functions of completing the database operation through the database connection pool component, but with different emphasis. Execute SQL components can complete the implementation of standard SQL statements, including the basic operations of Select, Delete, Insert, and Update on the database tables, can also complete the operation of the view and stored procedures; execution transaction processing components used to process transaction-based database Operation; the execution data window component is specifically used to execute the DataWindow of the adjuster application deployed on the application server and fed back to the report data in the processed OLTP database.
Any one of the three components can be coupled with the XML generation component to execute the report data operation function, and can also be coupled with the report dynamic generation component to complete the function of generating the user report. In addition, both the execution SQL component and the execution data window component can be combined with the execution transaction processing component in a manner that can be selected by the application system to jointly superimpose and complete the processing function of the service report or the transaction logic. Loose coupling of components is a collaborative relationship in which components are independent, can be replaced with each other, can be used by system applications, and can be superimposed.
2.2 Component Development Technology The development process for components can be divided into two main lines: server-side development and client-side development. Although server-side development of distributed communication protocols (such as CORBA, RMI) can sometimes be complicated, because the container provides most of the support for communication, state management, resource allocation, and thread management infrastructure code writing, it greatly simplifies Development of server components.
The main steps for server-side component development are:
a. Implementing component standard interfaces: Any interface required to implement a standard component model, enabling components to be based on the container's management capabilities.
b. Implement component-specific business interfaces: Implement any component-specific business interfaces and any supporting programs and utility classes that are supported.
c. Create a remote interface: Create a remote interface that defines all the specific component business interfaces.
d. Create a local interface: Create a local interface that defines a specific application method and finds a specific application method in the widget.
e. Compile the code: Compile the component implementation, the local interface, and the remote interface.
f. Configure the module or application deployment descriptor: The deployment descriptor required to configure the container/server is a J2EE deployment descriptor that defines the module's conformance, dependency deployment criteria.
g. Package component modules into J2EE applications and deploy them: Package standard J2EE deployment descriptors with one or more component JAR files into a J2EE application and deploy it to a J2EE-compliant application container server environment .
The client must use the correct component client interface method, and its development steps are:
a. Standard customer library verification: The correct component customer library must be built, including the correct versions of JNDI, EJB, customer RMI/IIOP, JMS, and JDBC core extension libraries.
b. Build Component Client Interface: Provides component clients with correctly compiled interfaces and specific stubs for specific components.
c. Customer Implementation: Implement component customers so that they can use any interface appropriately.
d. Client Code Compilation: Compile the component client code.
Then, you can debug and run the JZEE application client system in a specific J2EE application client container environment.
2.3 System Application Integration Integration The system application is based on the coupling of application service layer components, realizes the integration of PMMIS functions and integrates with GIS, DSS, Call-center and other system functions. The main issues that need to be paid attention to in the integration of PMMIS itself are the coordination and unification of communication between components and application layer. Using XML as a standard message representation and data conversion method between systems, J2EE enterprise application integration technology can be used to easily complete system application integration. The expansibility and compatibility of the B/S system architecture facilitate the seamless integration of multiple systems. The operation mode of PMMIS after integrating its own applications and other application systems can fully meet the operating mode of the enterprise information portal.
3 Conclusions The architecture and implementation technology based on the component coupling method discussed in this paper have been successfully applied to the actual construction of a power marketing management information system in a certain province and city. Practice has proved that designing and developing enterprise application systems based on component coupling technology can achieve the expected goals of the system, and has the following advantages: 1It helps developers to focus on the development and implementation process of the system design architecture, accelerate system software development efficiency, and improve system development quality; 2 Component coupling technology can reduce development costs, make large-scale software reuse possible, can not only improve system application efficiency, but also save the cost of system development and maintenance for power companies; 8 systems with high reliability, easy scalability and easy maintenance , And can achieve cross-platform, is conducive to the operation and expansion of the power company's application system, save the company's application system in the late investment; 4 can achieve seamless integration with GIS, DSS, Call-center and other systems, to achieve the integration of enterprise applications.
Introduction The use of advanced information technology to achieve networked service functions and the establishment of a power marketing management information system (PMMIS) adapted to market demand is the goal pursued by power supply companies to improve operational management efficiency, decision-making levels, and comprehensive corporate competitiveness. At present, the domestic electricity marketing management information system that has been put into operation generally has the following deficiencies: 1 It does not fully consider the characteristics of the electricity company's corporatization operation and electricity market, and still develops according to the traditional electricity consumption management mode; 2 It fails to properly resolve the system compatibility. Sexuality and scalability, for example, it is difficult to realize the organic integration of multiple power management information service modules, it is difficult to upgrade to integrated PMMIS, GIS, Call-center customer service support systems; 3 Failed to use power marketing analysis and auxiliary decision system The combination of electricity management information systems lacks the overall concept of electricity marketing. The traditional power management information systems mostly adopt a two-tier structure, and the development is extremely complicated. A lot of work must be done on both the server side and the client side, and code reuse and application performance are low. System applications under this model are difficult to integrate and it is difficult to reuse the functionality of existing systems [1]. Due to its poor compatibility and scalability, heavy maintenance workload, and system integration difficulties, it is no longer suitable for the development of power marketing management information systems.