ebXML as an inter-enterprise solutions for data transmission a good ERP system, eliminating the difference between the issue of data. In addressing this question, we can refer to ebXML work practices. ebXML is a set of standardized specifications, it allows different scales, different geographical enterprise business communications through the Internet. Using ebXML, companies can use a standardized method to exchange business information and trade relations, with normal contact information terminology, definitions and register business processes.
In the process of using ebXML, the XML format for differences between enterprises through ebXML registry to remove. In the ebXML registry to different companies-one correspondence up the same information in different companies require access to data, when the company will need to convert the information to the request can identify the ebXML format.
3 blocks communication between the standardization of
Development of information system design for the data flow and data dictionary in the format of the final implementation is used due to the development of system development tools and system model-related. In practical applications, due to the internal data format, there is no uniform requirement, different ERP systems or different versions of the same ERP system, the internal exchange format is likely to be different, so that the system integration and bring some secondary development more difficult.
Although in a different language, there is also their own data exchange language, such as Ajax technology on the use of JSON as its data exchange standards. Ajax uses JavaScript as a scripting language, scripting languages and the lack of efficiency in the lower XML parser for XML allows Ajax to give up the choice of turning simple JSON, although the JSON data format and the use of XML than simple, JSON in JavaScript, however, focused on data exchange, lack of language compatibility, and JSON is not a standardized format, stability and security can not be a good guarantee, so there are still a lot of penetration problems.
A similar technology is ADO.Net uses XML as an intermediate format for data exchange, XML as a common format for data exchange provides the basis for cross-database. Because ADO technology is only as a cross-database data mode of operation designed for the unity of the meaning and interpretation of data is not necessary. Meanwhile, a new generation of database storage technology, XML has become a new database storage format, XML in Web applications, also played a pivotal role. In desktop applications, XML has become a very good data storage format. XML as a new generation of data storage standards, XML-oriented data storage and data presentation, as the next generation of web language XML is a success. However, in the semantic harmonization, XML does not make a corresponding provision can not serve as communication modules for data exchange language.
4 How to use ebXML to eliminate data gaps
Elimination of the exchange of information between the module format of the problem is not unified, mature ebXML seems to be a viable solution. Since the beginning of ebXML is to design a unified format for communication between different systems, as a system within a unified format for data exchange is also very appropriate.
In the system design, system design staff on the system as needed to make system design, data dictionary and data flow is an important part of the rational and efficient data flow is a good basis for information systems, information systems during the test run for changing needs of the user data may sometimes have to make some changes and improvement of how the changing demands to maintain the stability of the system design and development of information systems need to be considered a problem. Direct access to the data module in the system development mode, once a data stream needs to make changes to the module must be involved to make the corresponding changes. And the use of ebXML the data stream object-oriented package is a better solution.
In the implementation of ebXML, different systems of difference from the ebXML registry to eliminate the different meanings of the XML information through the Registry to find the definition of each other to achieve the conversion, for different data can also be used a similar approach to convert , we can join the ERP system and database, EDI translation layer between the ERP system as an intermediary to interact with the database, the system data flow between the modules can be defined in the EDI translation layer, all data-related definitions are stored in the EDI translation layer, ERP the various modules will no longer operate directly on the database in the system module when the request is only sent to the EDI translation layer data stream request, while the EDI translation layer will be based on the system design of pre-defined data stream format, obtained from the database and converted to XML format for messages returned to the ERP system
As for the external system data manipulation by the same EDI translation layer to eliminate differences in different ERP systems connected, the first EDI translation layer in each other's data flow and data dictionary to make the corresponding data interpretation, be each other's data flow and the corresponding up its own database. In the communication between different systems, if the need for external data, then sends the data to the EDI translation layer request, one's own EDI translation layer before the request will be forwarded to the requested party EDI translation layer, the other side of the EDI translation layer, after the receipt of By definition, respond to and deal with data formats, and then the requested data back to the sender of the EDI translation layer, one's own EDI translation layer then the data back to the ERP modules, so to complete the data processing. Namely, the global context, EDI translation layer also can be used as ebXML endpoint to be achieved; in the internal system, EDI translation layer is localized ebXML implementation. Therefore, the specific implementation, EDI translation layer does not conflict with ebXML, the two can very well together.
|
