Dynamic Web services Author: Atul Saini
In today's business environment, important information exists in many heterogeneous systems of enterprises.
It includes:
• Customer Relationship Management (CRM) system
• Financial accounting system
• Enterprise Resource Arrangement (ERP) System
• Web Servers
• Legacy system
This information must be accessed by multi-contacts, which typically evolve into internal isolation mechanisms. They pay attention to the needs of the product line and department rather than the customer, so that these systems still include strategic data.
Additional systems that contain important information usually need to be combined, so merchants are trying to find integration and business process management (BPM) solutions, which expands the life of previous investment and increase investment.
There are now several platforms to implement Web Services - the most famous sellers' J2EE application services and Microsoft's .NET Web Services can provide standard-based enterprises or cross-enterprises. Based on Web Services-based integration solution allows companies to reduce traditional high costs related to enterprise application integration, because Web Services solutions are industrial standards, unwanted knowledge that requires application and product owners. Because of this, many companies are willing to take WEB Services-based solutions for EAI and BPM.
EAI platform needs
Not all Web Services platforms can be used for EAI Out-of-the-Box. These problems include adding special needs in a potential platform to achieve distributed EAI and BPM solutions. The remaining part of this section will discuss this need, which is necessary for efficiency and scalability.
• Fully distributed, peer-to-peer network, event-based architecture
Real business processes are typical multi-application, multi-hardware, and multi-software distribution; they are also based on events because these processes are typically connected by a series of events. Therefore, a platform should be able to achieve the integration of business processes needed within an enterprise and cross-enterprises, which requires these processes on a fully distributed node. An effective EAI / BPM platform must require a peer-to-peer architecture, develop with software engine methods, emphasize its various security, control, dynamic access, and flexibility. The platform must be symmetrical, which means that software that is also based on an event infrastructure needs to be executed on all machines within the enterprise. Most EAI and BPM solutions control the business process through central systems, so that changes in application or increase new applications, they need to change in the central system. This topology is low in efficiency low, resulting in the presence of bottlenecks in a distributed system.
• Process routing transparent
An EAI infrastructure platform should provide full transparent information flow in different processes of the solution. In order to provide flexible change management capabilities without any programming, the information routing of each component within the system should not be considered.
• SERVICE-architecture-based flexibility
An EAI platform should ensure that it is easy to deploy, manage and change the participation process. This means a component-based architecture, in which the application is loined by rough components, they are bonded to each other by event-based messages, each service is potentially running during the separation process. This allows a quick deployment model to reduce the boot time of the implementation solution. This architecture provides support tools for rapidly modified processes, so analysts can change and instant deployment processes to meet the changes in business needs.
• Remote deployment, monitoring, and management
An EAI infrastructure platform should be able to provide methods for deployment, management, and monitoring on the network. It should also support real-time monitoring of data and events, which will significantly reduce the deployment of time and distributed business processes.
• Enterprise standard support
In order to reduce data exchange, messaging support, existing enterprise standards and BPM can dynamically reduce the entire cost of EAI infrastructure. It does not need to consider specific needs or specific knowledge in the deployment scheme, because the contents of the extended markup language (XML) and documentation are desired. Most merchants want to develop systems with messages, components, services, enterprise data, lightweight path access protocols (LDAP) path services, E-mail systems, and so on. So an EAI platform needs to ensure that these standards are easy to implement. Problems now of Web Services architecture
Although it is very interested in WEB Services for EAI, the current Web Services platform has some problems with the implementation EAI. These proliferated Web Services platforms (including J2EE application services and Microsoft .NET) are:
• Request / Reply semantic efficiency
The existing Web Services platform is a typical request / response semantic, each Web Services is connected by using a Simple Object Access Protocol (SOAP) request, then the module waits until the result is returned to the caller. The platform is based on voting vote and requires manual coding to get the output of Web Services, and passed it to different web services or applications in the workflow. The data stream within the Web Services lacks event bus, so that the WEB Services platform in the EAI solution is low in efficiency.
• Concentrate, unprecedable architecture
The current EAI solution needs to change the central system through the central system to control the business process, the application changes or new applications. Moreover, all data exchanges between applications require a central system, which will result in a bottleneck of distributed systems, and cause significant low efficiency and discomfort.
• Missing remote deployment, monitoring, and logs
Typical distributed systems There are many Services running on different machines across the network. If any of these Services service is invalid, other components on this system should be reminded. An EAI platform should provide Services constructing for such step-by-step monitoring, but also with remote tracking and log facilities. Another purpose of automatically deploying Web Services on remote nodes is to reduce maintenance and implementation. The existing central Web Services platform has no support for remote service deployment because the Internet's brakes do not provide infrastructure level support for deployment, resulting in an increase in the development and deployment of solutions.
Use the Services action platform
Now the Web Services infrastructure platform cannot resolve the core issues related to EAI and BPM, which is best to use the Web Services that uses event mode, namely the dynamic Web Services we mentioned. It is best to implement in a fully distributed situation, and the infrastructure of the event We call the Services Operating Platform (SOP). SOP facilitates distributed enterprise applications use visual tools to synthesize, deploy, and modify. A powerful SOP is that it provides a single overall platform for the company's EAI, B2B integration, B2B integration, BPM, cooperation, and general distributed computing.
Figure 1 shows the architecture of a typical SOP node. In a typical enterprise, each network node based on this architecture runs a Daemon, which is connected by the message bus, as shown in Figure 2. As can be seen from Figure 1, an SOP is provided as an event-based message, transparent process routing, remote monitoring tracking, log, timing arrangement, field, and availability, security, and remote deployment provide building support.
A SOP is a pure infrastructure platform that allows for any kind of software Services implementation, including Web Services. It is different from the existing Web Services implementation that it requires a fully distributed peer network using the infrastructure of the message, not a central request / response infrastructure. A SOP can provide these advantages to our customers.
• Services-based application synthesis deployment applications on SOP are composed of one or more Services (or components), each service runs freely in the process of separation. Services may be written in any language and communicate with each other through XML messages. This allows the structure to be flexible and easy to modify.
• Deploy and change during a speedy business process
Dynamic Web Services on SOP is rough Services, which is ideal for easy to change and replace, and Services implementations on SOP are obvious in Services distance between service. This makes it easy to modify or add fast modification of the speed of its business process. A SOP also supports the deployment of Services, allowing to change the business process for instant deployment through the network, compared to traditional solutions to reduce deployment fees.
• Error tolerance, measurable, reliability
SOP symmetrical network structure provides a high measurable platform, which does not have a single point of mistake, lacking the central system gives application developers directly route data between the required Services and define the network's topology selection The biggest flexibility.
• Component level security
A SOP gives an administrator which service is executed, where is executed, and ensure safety.
The SOP allows administrators to set any quantity security properties for each Services and provide the security settings of the tool configured on any network.
• Performed period monitoring, tracking and log
A SOP is monitoring, tracking, and logging support for execution period, and supports itself. All Services can be monitored by visualization tools. The tracking level can be dynamically changed on the deployed Services, and the debug log can be transferred in the software tool route in any node. These features greatly simplify the development, deployment, and debugging of distributed applications running in SOP.
• Support visualization process synthesis and change management tools
A SOP contains the application interface (API) to support the development of software tools, which allows for the rapid synthesis of distributed applications, builds the application designer's business process. This the same environment also allows you to monitor all Services on all distributed networks.
• Support enterprise standards
A SOP uses a standard Java Message Service (JMS) to exchange messages with standard XML, using XSLT data to be translated into Tifosi SOP and any other application or service format. A component resolves the development kit (SDK) allows users to connect to any existing components or services that use SOP. Other enterprise standards, such as Simple Mail Protocol (SMTP), and Simple Network Management Protocol (SNMP), enabling them to integrate with other enterprise systems.
• Services that supports generic purposes
A SOP also supports integration of components that are not implemented as specific Web services. A general purpose service can have any constant number of input and output ports, while a Web Service logically only one input and an output port. Under their integration efforts, General Services offers additional flexibility. Often, it is more likely to model the software service for a general purpose, not a specific Web Service.
in conclusion
Methods for EAI, BPM, and related enterprises have not fully metages these issues on potential infrastructure. SERVICE-based structure, implementation on fully distributed, peer-to-peer networks, event-driven systems, bringing the entire new level of versatility to enterprise platform space.
The SOP implements this way, expounds the need for BPM on applications and people's interaction level. It describes these needs in an enterprise or cross-enterprise, cross-domain (including domains that are different from traditional solution services). For all distributed calculations, in order to save time and money, in order to increase cross-sectoral processing efficiency, a SOP guarantee allows a company to establish a unified computational infrastructure.
About the Author
Eai Journal • April 2003 19atul Saini IS CEO
And Chief Technical
Office of Fiorano
Software. Through His
Leadership, The Company's
Flagship Product,
Fioranomq, HAS
Become a Leading
