Interesting: Use SLI for host-based Web service integration

Hanging out on msdn, I accidentally saw something like this: screen logic integration.

SLI (screen logic Integration) is used to convert the character interface of the old UNIX green TerminalProgramIt is encapsulated into a web service so that these ancient business logic can be reused in the SOA architecture.

For example, in our company, the Business System is a UNIX-based terminal program, and some business logic is to input parameters and materials in some input boxes on the interface, or the computing result is displayed in a place on the screen. These business logic can be published through neon systems servicebuilder in the form of web services. the process is as follows:

1. Create a New neon systems servicebuilder project in vs to create an SLI solution. (Of course, you must install this first ).
2. The Wizard provides a recorder to record the input and output of your Telnet program, and to record all the input and output information on the screen.
3. In the recording result of the wizard, you can intuitively specify the input parameters, output results, and data types.
4. The Wizard generates the relevant object model and generates WebService.

What about the actual running time? I guess it is like this:
1. Web Services is called, and parameters are passed in. WebServices program calls the neon program.
2. The neon secretly connects to the unix host using the Telnet protocol, and calls the program on the unix host in the sequence of keys under the record.
3. the parameter is input by the program at the specified position.
4. the Host Program responds to the results. These results are originally displayed on the screen and are now obtained by Neon. Based on the specified location information, the system determines which fields are matched with the information, return to the Web Services program.
5. Web Services responds to the caller with the result object.

This is really useful.

On msdnArticleHere:
Http://www.microsoft.com/china/MSDN/library/KnowledgeBase/kb_0409.aspx