UDDI Development Guide under Windows.net
Mood
2002.02.28
Article Type: in-depth
Difficult Level: 5/9
Version: 2.03
It is still not possible to determine if the focus of the next debate is Windows.net, but many people try to see this trace from the nearest BBS and technology websites. Although Microsoft's lawyer is posted on many personal websites, it seems that the details about XP and Office XP have become simply tasteless. Many personal websites and BBSs no longer provide their Download and join, and even co-operated categories and activation are considered to be lagging and intake Class C. In addition to the 8IN1 XP burning skills, you can see more people in discussing the secrets about Windows.net, compared to what they prefer to exchange mutual installation and use skills, in fact, the frenzy is known as this century The best operating system is currently expressing the strange seismic hem. Whether you are nick in the 1990s Win98 Blue Sky White Cloud, respect for the smoothness and performance improvement of Win2000 Server last century is our minimum choice. Windows 2000 SP3 silently, so that this is the software that belongs to the last century has become the past, continue to wait for another cute and untrusted romantic revival, we are stubborn: this is a long-lasting version of Windows Almost all end versions of unsafe factors. A few patch showed high performance promotion is undoubtedly the backlight of the dead sheep. Between future phantom and true, we are more willing to choose the current security. We suspect that our position cannot change our understanding of security, so Windows 2000 must last. You can see that there is still a long way from the chaos to peace, and the WINDOWS.NET brings IIS6 and UDDI Service. Although some is a width, it is still very popular in it, it is very happy to fight a few mornings in the morning or afternoon. After all, this is another experience of another environment.
The following operation is set in such an environment: Windows.NET 3604 Server, Visual Studio.NET RTM, DOTNET UDDI SDK 2.0 Beta, MS SQL 2000 SP2, IE 6.0 2813. There are two machines, one installed with Windows.Net 3604, we call it Datacenter; one is Windows 2000 Adv Server, with Visual Studio.net and UDDI SDK, we call it vsdotnet.
And we will do the following:
1. Generate a WebServices on the VSDOTNET.
2. Register this WebService on the UDDI Server on the Datacenter.
3. We return to the VSDOTNET to verify this registration.
The entire process we can happen in a local area network, of course, inevitable is that we need to read some related online documents (will be listed in the last).
We have little discussions about what is UDDI, TMODELS, WSDL, and so on.
The first operation is the easiest, which can be a Hello's WebService, or a b = C WebServices, in fact UDDI does not mean that will eventually call this Webservices, and finally you will find I use asp.net A Hello World as an example, so this operation can almost jump, no longer said.
Finally, we need to record our links and prepared WSDL files (TMODEL), link is http: //vsdotnet/soap/uddi/registuddi.asmx? WSDL, but I want to name my name, reggistuddi is too easy to cause people Ambiguity Lenovo. The second operation is the process of registering UDDI, here we follow [Jan 01] suggestions, register with manual way. Programming will be for programming and a large number of operations, on the one hand, I think the space is limited. After the current topic, on the other hand, I want to blame Microsoft's current SDK's bad documentation, and there is no current document. Document description of components and APIs.
Windows.Net 3604 The default installation is not IIS and UDDI Services, you need to install separately in the control panel, the planned installation is to install MS SQL 2000 first, then install IIS 6, then install UDDI Services (you need Windows .NET has brought itself with DOTNET V1.0, and if the SQL 2000 is not installed, the UDDI installer automatically installs a streamlined SQL Server). After the installation is successful, the UDDI is registered into IIS, and the required data structure is installed in SQL 2000, and it will provide a Client side SDK, which is 1.76 in this Windows.net. After the installation is complete, type http: // datacenter / uddi, you will see an almost almost similar interface on the Microsoft website. I don't know if you do a phone thin program, from now you can see the UDDI process, the entire UDDI Services is a web service, which completes the operation and interaction of the UDDI database by the core DOT component, the user can pass the Client SDK To perform the need for interactive completion of the registration and query. In operation, it is like a phone thin application, you can query the phone thin, add an entry in the phone thin, modify a phone registration, delete and other operations. But we use manual way to do this. As for the specifications of the phone, the format of each phone is registered, the details of the query requirements are defined by the UDDI specification.
According to [Jan 01] or [See 01], we also list one of the same registration steps:
1. Add Providers
2. Add TMODEL
3. Add Service
4. Add binding
5. Add Instance
Compared to the registration steps described in [See 01]:
1. Add company (Business)
2. Add Contact Information (Contact)
3. Company classification
4. Add TMODEL
5. Defining services
The steps seem to, the same 5 step, I omitted that he is not necessary 2, 3, adds two steps necessary. This version of Add Service is a bit complicated, so I decided to use some pictures to explain these.
The first step Add providers is quite in [See 01] Add Business (now we can't judge the last unified statement, and the aunt is subject to the respective description), and the specific you can refer to the description in [SEE 01]. I ignored for add contact. Note that we need to use the right-click function, point my uddi to right click, we are called CCBOY
The second step Add TMODEL, this [see 01] is also very clear, it is ok, mainly to register our first operating WSDL. TMODEL in the same point is then right-click. We named Hello's third step Add Service, here and [see 01] have been some different. After add service, we need to continue the fourth step, here is some special. You need to click the Providers node and right click. We also named Hello
Step 4 Add Binding, click on our service to press the right button to add the appropriate option
Step 5 Add Instance, click on our name to press the right button, click on one window, use any of two ways, we will find the second step to increase the TMODEL-> Hello, select it to determine.
After completing these operations, we can see a tree picture:
This basically completed the first step-by-step WebService in the UDDI database of the Datacenter, we can select the Search's menu and find an entry we registered.
Last
