Don't let some questions that are easy to solve ultimately evolve into big obstacles, which hinders your company's use of Web Services. BY WILLIAM OELLERMANN Recommendations: Visual Studio.NET, XML, WSDL, UDDI Whenevantly, the attitude of each company has the following attitude. Some companies believe that important technologies can solve current practical problems, which can be more conducive to their future development. Other companies have not taken action, but hold the attitude of watching and see if this new technology has suffered. Inevitably, these companies will have to play the role of followers so that they are likely to take some compromise during the design and implementation procedures, thereby shortening the adoption cycle. Although the importance of different technologies is different from a company, the delay may lose a valuable market share, or lose some opportunities, this loss is unrecivalent. Web Services is an appropriate example, some companies have put themselves in a follower. Considering that the current Web Services is not mature, this saying seems to be a bit anxious. But after all, there are a few meaningful Web Services now available, and people are constantly making efforts. In this article, I will tell why now use web services very important, focusing on the important difference between web applications and web services, and discuss two difficulties in the process of enterprises using Web Services. Then, I will scream a model, you can use it to overcome these difficulties, smartly useful web services for your business. First, I talked about the relevant background. The industry is invested in Web Services for nearly three years, but they seem to have no strong attraction. Indeed, many vendors build support for Web Services in their tools and application servers, but they are not clear who is using these Web Services. Even Microsoft has been tightened in the supply of .NET My Services. If Microsoft is not ready, how other people are ready to provide Web Services? Although it seems that it seems to lose motivation before Web Services starts, but in fact, they are only a long time to spread more than many people's expectations. Although Microsoft seems to have been out early in the announcement of Hailstorm (Aka My Services), it is taking steps to provide useful Web Services such as Mappoint.Net. Some companies take a look at the attitude towards the use of Web Services very slow, and they have made a mistake. Correctly understanding Web Services technology and market conditions can reflect that you can't afford to use Web Services. Figure 1. Development of the development of the Web application in the mid-1990s internet revolution made people's expectations of the use rate of technology, even a ridiculous extent. In six months, people can publish, develop, use, criticize, and abandon one technology. (Remember Push Technology?) The steady advancement of application technology, but quick advances not only contribute to the INTERNET revolution, but also provides an obvious way for a company to use Web. Since web applications become increasingly complex, they have turned from simple and static marketing sites to customers' interaction tools (see Figure 1). As businesses continue to improve their work in web applications, these applications develop from attracting users to improve the work efficiency of the company's internal staff.
Once the company is satisfied with the Web application used for internal web applications, they will only have a time problem with the cooperation between these programs for cooperation with partners. Although many people recognize that Web Services and web applications are different, they often ignore an important difference - meaningful web application can be an independent entity, and meaningful Web Services can't . This difference can lead to two factors, and some companies believe that these two factors will bring obstacles to the use of Web Services. The first factor is complexity - risk. Web Services is essentially more complicated than the Web site, not because of its technical specific complexity, but because Web Services must be combined with corporate key systems and processes. Any Web Services worthy of Web Services contains dynamic data and interaction with key systems. The role of Web Services is not equivalent to the "marketing brochure" site, and many companies are involved in the Web site. With Web Services, you really enters the web domain, and its complexity has brought higher risks to deploying Web Services. If your company provides a Web Service with a calculator, then other people develop a better service, making your service commercialization, just a time problem. Businesses will not provide more value for this web service, nor will they get more value from this web services, they will only benefit from Web Services that combine with their private data or processes; therefore exists Essential risks and complexity. This risk is similar to those related to providing web applications, but the strategy to mitigate these two risks is not necessary. Many companies are in the third region (DMZ) to isolate the Web system, which is not directly combined with important backend systems. Alternatively, they use a batch to periodically deliver the necessary data. Although this method is sometimes used for an application, it is unacceptable to meaningful Web Services. They need to interact with you cannot transfer to DMZ. If you create a web service in this way, you have to quenue it for other people. Like Web applications, we can securely provide Web Services and connect to internal systems, many companies need to update their independent security policies to keep synchronization with Web Services. The second factor is the cooperation of Web Services. With web applications, you can control the entire process and user experience. Only the client browser is you can't control, it is the smallest in any web application. In recent years, browsers have become a common component of almost all computers, which gives developers and designers a fairly consistent delivery tool to make the application's deployment easier. Instead, at least two devices should be used to participate in a Web Service. For web services, there is no browser type client. As an alternative, an intermediate party (application) manages interactions between web services and end users. Some web services may not contain end users, it is just a communication between two systems without any person. The application uses real Web Services This is not to say that you can't use a browser as a browser in a .asmx page in a .asmx page in Visual Studio .NET (VS.NET). However, a true Web Service is used by an application instead of being used by a browser.
Although you can build a normal Web Services user, even use Web Services, users through UDDI (Universal Discovery, Description, And Integration), and WSDL (Web Services Description Language), but no matter how key enterprise process is very fast Use Web Services in this way. Web Services is about integrated application procedures. If your purpose is to present any process directly to the end user on the web, you choose the wrong way. For many years, the web application has provided that function. These two factors make the way to use Web Services vary from the way to many people expect. Although the path to Web Services is different, this is not to say that you can't learn experience in the development of web applications; you only need to identify that these two roads will have different. By selecting one of the two methods used in the new technology mentioned earlier, you can manage these factors. Some companies are waiting for third-party suppliers to design detail, alleviate most (if not all) and the risk of providing Web Services. They know that Web Services needs to be secure, protect their information and assets, but they can not guarantee that they don't believe in Web Services security. Therefore, they choose to wait for a complete "Out-of-a-Box" solution. This approach enables enterprises to enter the obedience, because many components of the Web Services full lifecycle "standard" are still under development. As I mentioned earlier, this attitude may be very dangerous. The second factor may make a business decision not to provide Web Services, because no one requires it to do this, and it can't see competition. This attitude will also fall into the company, because most Web Services projects are not fully announced. Can't see Web Services because you don't see Web Services, think that you don't compete in Web Services that your customers are using. Enterprises with such an idea have turned these two factors into obstacles in the WEB Services process. Fortunately, some companies have realized that the complexity of Web Services - risks and cooperation are only small, not big obstacles. Below, I will tell a Web Services that you can implement today to ensure that you will not be able to lose. You can first provide Web Services to connect a completely different app. Because all existing middleware solutions, if you look at the first eye, you think Web Services is useless in your business, then look at it. Even small companies will have limitations in system access, and existing solutions cannot solve this problem, and Web Services will help. Recall your company to start combining web applications to your backend system. The backend system may be an online registration system that is connected to the primary customer data server, or a sending order to an e-commerce system for an execution system. You will always encounter a system, its owner or don't believe in your web application, require permission, or not to provide a good way to local API calls, you can only use a batch to accept or abandon the old data. This is a good opportunity to help Web Services to help the controlled permissions needed by both parties. The owner of the system has the opportunity to define an interface in the system, you don't have to get old data, or use an unstable, low-level agreement. The system for other applications requires Web Services also to mitigate the second factor - cooperation - provided the foundation. You initially decided to use Web Services to use existing needs of interaction, this interaction will bring you success.
You don't have to worry about the web service you build, your web service has lost motivation or your effort is unsuccessful. Control the sharing process You can control both sides of your procedure because your Web Services is provided and used inside. It not only reduces the overall risk of Web Services, but will give you an opportunity to satisfy your security options available in .NET Web Services, they have some Secure Sockets Layer certificates similar to the web application, Kerberos and Simple Object Access Protocol Headers. Figure 2. Entering Web Services Adoption Mode Some companies have adopted this approach to gradually transcend their limitations to implement and use Web Services (see Figure 2). In order to control complexity-risk and cooperation, companies need to extend their original Web Services to a single partner or limited partner. This allows you to further monitor and resolve any initial problems. It also allows you to help you collect demand or determine your original Web Services value as your main candidate. Partners should be a person who has established a stable relationship with it, you can trust them, provide full testing of services, they will not use possible (not necessarily related to security, but related to the process) "vulnerability ". After doing these preliminary efforts, your business will be more in hand when deploying Web Services to more suitable partners, don't worry about the two difficulties. In this method, UDDI and WSDL (VS.NET are automatically provided) may make more important contributions to your Web Services solution. So far, I have already described some of the cases of Web Services, and their number of users directly contacting each other is limited. Although WSDL helps to use a Web Service through vs.Net, your original efforts may have a fast build cycle, and you and your users can manually communicate all changes through communication and XML files. UDDI and WSDL are key to ensuring your Web Service implementation when you are ready to open your service to a large number of users. The problem that manually solves each new user will eventually lead to bottleneck problems between you and your potential users, it will hinder your Web Services' adoption rate. Once you have a large scale to deploy some web services to the determined partner, you will be prepared to open them. I mean is not an end user, because we have met them from a web application. You provide your web service to you may know or don't know, they need your web service. If you follow the previous steps, you should have confidence that you provide the Web Service to the system very small, the underlying frame supports it, and it is also important to have the reliability of the business process you present. Now you have publicly open your web service, you may think you have succeeded, but you just start. You have provided a Web Service, and its support system is limited. Even if you use a standard way to verify the user, you still have no automatic procedures to register new users. You may have already established an agreement with our partners, but you don't charge your Web Service (at least not based on it). You may also need to track the input Web Services requests and consider how you can manage your transactions or processes across multiple steps. These types of services are some additional features that can be used to create a powerful web service, but they are not necessarily necessary in the original Web Services I have told.
