WebMethods Middleware Development (1)

In the company by the Big Boss pulled over to do middleware development, before there is no big concept, but at that time the company did not have this aspect of the people, they are just to the company, can only bite the bullet.

Our project is a traditional material company, so it will have a lot of product information Ah, order quotes and other information needs to be synchronized in multiple systems, and we mainly do have about Salesforce integration.

The so-called middleware, which is a separate service program, is mainly responsible for the transmission of information between multiple systems, it can connect a number of different systems, even if their interfaces are different. To put it bluntly is to move the data of system a into system B. But then we certainly have questions, why do we need middleware, I can't do data transfer directly? At first I was also puzzled about this, especially in the development process encountered problems will inevitably complain, if let me directly do that many simple words. But in the presence of the principle of reasonableness, I slowly to its existence has a number of different views. When we do data integration, most of the time the objects are like databases, mainframe such systems, and such a system of external interaction ability is very poor, so if it needs to interact with the outside world so the cost of interaction is very large, especially the need to actively interact with the outside world is more impossible to achieve, then the middleware plays a role. What about the two flexible systems? In fact, most of the middleware application scenarios are in a number of big data systems, so there are a lot of network transmission problems, so there will be many similar to cache, data loss, large data transmission and so on. And if the source side and the target side of the direct interaction, the source side not only to do business data extraction, but also bear the direct interaction with target, which greatly increases the source pressure, but also easy to cause data loss and other issues. For example, a system needs to extract 10w data from 100 tables to sync to the B,c,d system, at which point a system needs to interact with b,c,d at the same time, so there will be blocking problems, And once a data in the 10w data such as the update failed or the target system is temporarily unresponsive, and so on, and so on, the synchronization operation may fail, which will affect other systems. So we also need to set a rollback or error exception in a system or even cache, and so on, a system synchronization we need so many operations, which is obviously unreasonable. In accordance with the principle of clear responsibility, the emergence of middleware has been a good solution to such problems. It can be seamlessly connected to multiple systems, and can be used to transfer data, such as subscription, and automatic sniffer target system and other functions, you can not worry about the loss of data, and it supports a variety of transport protocols, a variety of transmission text format and so on.

All right, so much, now formally introduce us to the use of multi-middleware webmethods. Webmethdos is Softwareag's multi-product, it has its own set of systems, including development tools Developer/designer, server configuration is, data interaction intermediary broker/um,b2b and other text interaction tranding Network, the big file transfer platform file Transfer, the System Management MWS, as well as the detailed log system, the authority system, but also has the report system and so on the function, simultaneously supports its own language and C#,java and so on, but can carry on the mobile development and so on. The latest update to 9.5 began with the cloud data synchronization and so on.

Next we begin to talk about the whole structure of webmethods and how to develop it.