KR20010105932A - A management system with connect function achieved systems exchange to internet - Google Patents

Abstract

The present invention and the system having a connector function that can be easily moved to the Web (WEB) environment while maintaining the client / server system built using the mainframe system and the middleware TP monitor that the user is currently using System and business that change the built 3-tier architecture to the N-tier architecture of the web environment to use all the functions provided by TP-Monitor. By providing a system that does not require any modification to the server application that provides the service, it minimizes the cost incurred by a company or a business operator to establish an Internet-based work environment, and processes the work through the Internet according to the work. Prevents various types of risks from No matter what system the data is on or where it is needed, the operators and users who operate the entire system are among the systems in the Internet environment that maximize the efficiency in running and improve the reliability of their use. Its feature is to provide an operating system with connector functionality for compatibility.

Description

A MANAGEMENT SYSTEM WITH CONNECT FUNCTION ACHIEVED SYSTEMS EXCHANGE TO INTERNET}

The present invention relates to an operating system having a connector function so that important systems on a network are compatible between the systems for constructing a single computing environment regardless of the type or database.

More specifically, it is easy to use as a web environment while maintaining the client / server system built using the mainframe system and the middleware TP-Monitor currently used by the user. Provided by TP-Monitor by changing system with mobile connector function and already built 3-tier architecture to N-tier architecture of web (WEB) environment Minimizes the cost incurred by companies or operators in building an Internet-based work environment by providing a system that requires no modifications to the server application that provides all the functions and server applications that provide business services. In order to prevent various types of risks that occur in the course of business through the Internet, This ensures that the end user's physical location or required data resides on the user's location, regardless of which system the user is on, and the operators and users who operate the entire system can maximize efficiency in implementation while at the same time The present invention relates to an operating system having a connector function for making compatibility between systems in an Internet environment to improve reliability.

In general, as the digital economy becomes the center of the new economy, companies that cannot adapt to the Internet-based online environment cannot maintain competitiveness, and in this rapidly changing market environment, many companies can handle their own line of work on Internet-based systems. The justification to switch should be recognized.

However, there is a huge investment in legacy systems that are in use today, and this cannot be abandoned, making it difficult to determine the transition to Internet-based systems.

In addition, as the number of Internet users increase and they are at the center of the economy, customers are demanding Internet-based work, but it is costly for companies to respond immediately to establish an Internet-based work environment. There are various types of risks that arise in the course of business through the Internet.

The Java Remote Client Service (JRS) product for incorporating the existing TOP END system into the web environment provides a Java API for use in various Java environments. It is executed in single-threaded form in the same way as the APIs provided in UNIX and NT systems, so if you want to write a TOP END client using servlets to request a service, the servlet basically The business critical applition structure located behind the web environment because the servlet is created in the form of a single thread model without using the multi-thread function supported by the This is a barrier to the scalability of Tuxedo's Jolt and TMAX's Web / T.

Therefore, in the WWW environment that is changing the world IT market, the existing middleware TP monitor products have provided their own solutions for the web (WEB) connection, but the enterprise (client / server) structure scalability, integrated management, distributed transaction processing, real-time load balancing, 24/7 processing, and heaters provided for business critical applications in the enterprise market. In terms of performance and cost, the products of middleware TP monitors are currently used in terms of performing tasks such as heterogeneous platform support and mainframe coexistence over the Internet and supporting customers. There is a problem that is not effective.

The present invention has been made to solve the problems of the prior art as described above has the following object.

The present invention is a client built using the mainframe system and middleware TP-Monitor that the user is currently using to form a single computing environment regardless of the type or database of important systems on the network. A system with a connector function that can easily move to a web environment while maintaining a client / server system, and a three-tier architecture that is already built, Provides a system that changes to N-tier architecture so that all the functions provided by TP-Monitor can be used and no modification to server application that provides business service is needed. By minimizing the costs incurred by companies or operators in establishing an Internet-based work environment, To prevent various types of risks incurred in the process of processing through the Internet, thereby allowing end users to run right where they are, regardless of the physical location of the user or the data they need. The purpose is to provide an operating system with a connector function that allows the operator and the user who operates the entire system to be compatible between systems in the Internet environment, which maximizes the efficiency in execution and improves the reliability of use.

1 is a system configuration diagram showing a state in which the present invention is built on the middleware,

2 is a system configuration diagram showing a state in which the present invention is built on a network service;

3 is an exemplary view showing an embodiment for security of the present invention;

Figure 4 is an exemplary view showing for explaining the process of the present invention.

<Description of the code | symbol about the principal part of drawing>

10: client or web browser

20: application server

20-1: Web Spear

23: Servlet Engine

25: J * Link

40: firewall

In order to achieve the object of the present invention described above, it will be described a preferred embodiment for embodying the present invention.

In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

The terms to be described below are terms set in consideration of functions in the present invention, which may vary depending on the intention or convention of the Internet operator and the programmer, and the definition thereof should be made based on the contents throughout the present specification.

Prior to the following description of the present invention, a connector for extending an application of a legacy system in use to an Internet-based environment to be compatible between systems in an Internet environment is referred to as "J * Link". It will be called.

In other words, the J * Link can extend middleware-based systems such as Tmax, TOP END, Tuxedo, CICS, and Entera and legacy systems that provide network services such as X.25 and TCP / IP to the Internet-based environment. This allows companies to provide Internet-based services while protecting what has been done.

The legacy system is a client / server or mainframe based system that does not support a web-based e-business system by itself, and the middleware is used by a user to transparently access system resources. It represents the software that binds the operating system, network, database, and applications together.

First, as shown in FIGS. 1 and 2, FIG. 1 is a system configuration diagram showing a state in which the present invention is built on a middleware, and FIG. 2 is a system configuration diagram showing a state in which the present invention is built on a network service. It is shown.

That is, the client 10, which is an environment in which a service can be requested through all kinds of web browsers that are generally used, the application server 20, which is a hardware node of a web server, and the application server. In the above, the system consists of TOP END, Tuxedo, Entera, which are various middleware 30 systems implemented by driving 20, and X.25 and TCP / IP, which is a league system 31 that provides network services. The application server 20 includes an HTTP server 21, a web sphere 20-1 formed of a JSP 22, a servlet engine 23, and Java Beans 24, and a J * Link 25. It provides additional functions for availability, scalability and performance every time, the HTTP server 21 to provide a Java virtual machine (JVM) to use the J * Link 25, the JSP (22) ) And the servlet engine 23 are dynamic dynamics of the Java. It is a standard specification for providing TTP contents (Dynamic http contents), the Java Beans (24) supports the business logic in the form of serialization of the Java program, the J * Link (25) is the Web sphere (20) -1) is installed between the middleware 30 system or the league system 31 to be extended to the Internet-based environment, so that companies can easily provide Internet-based services while protecting the existing ones. .

In addition, Figure 3 is an exemplary view showing an implementation for the security of the present invention, by installing a barrier 40 between the web sphere 20-1 and the J * Link 25 to block the leakage of information The Java instance 41 of the J * Link is located outside the firewall 40 so that only the J * Link Listener 42 and the J * Link Communicator 43 can communicate with each other.

In the present invention, the client 10 is a general web browser, such as MS's Explore and netscape, and the above indicates that it provides an environment for requesting services through all kinds of web browsers.

The application server 20 represents a hardware node of a generally used web server, and the application server represents a hardware node in which a web server (web server), a web application server, and a J * Link are mounted together. .

The web sphere (WebSphere, 20-1) is an example of a web application server, the software called the middleware on the Web basically provides a servlet engine, and each product has additional functions for availability, scalability, performance, etc. The J * Link 25 supports all Web applcation servers that provide a servlet engine. Examples thereof include IBM's WebSphere, BEA's WebLogic, and Silverstream.

The J * Link 25 can also operate in Jserv, Jrun, java Web Server, etc., which provides only a servlet engine.

The HTTP server 21 is generally called a web server, and in order to use J * Link, a JVM (javavirtual machine) must be provided, and most of the current products provide a JVM. As a kind of Apache web server, MS IIS, Netscape's Netscape server, and the like are included in the above WebSphere 20-1, but are actually different products.

The JSP 22 is an abbreviation of Java Server Page and is a standard specification for providing Java's dynamic http contents. The servlet of the servlet engine 23 is a standard specification for providing Java's dynamic http contents to a Java servlet. (24) supports business logic in the form of serializing Java programs.

MOM or RPC shown in the accompanying drawings calls the server application from the client of the middleware, TOP END, Tuxedo uses the MOM method, Entera uses the RPC method, the MOM (Message-Oriented Middleware) is the middleware service When calling a server application from a client as a calling method, a service is called in the form of a message. FML is a method of creating a message by defining a field with a buffer type used by Tuxede, and the RPC (Remote Procedure Call) is used in middleware. The following shows how to call a server application procedure directly from a client program when calling a service.

In addition, MHS (Message Handling service) represents a service that helps to call all the middleware using the MOM or RPC method in one way of the MOM method.

CICS of the system 30 is a transaction processing system provided by IBM that can be directly called using J * Link using a Communicstor, the network used is SNA LU6.2.

Among the systems 31, TCP / IP is one of the network protocols and is used when using a general client server environment, and is used to communicate with a UNIX system that does not use middleware.

X.25 of the system 31 is used as a network protocol when using an interface with a general mainframe or an external network, and is used to communicate with a mainframe that does not use middleware.

On the other hand, Figure 4 is an exemplary view showing to explain the process of the present invention, in the case of using the J * Link 25 to the system 30, 31 and Java applications (Java Application) Loading an application in a client, executing the application, loading the J * Link class, receiving an existing middleware connection, and receiving a service request; When the J * Link 25 is applied to the systems 30, 31 and Java Applet, a web page is requested, HTML pages and applet code in the web server are downloaded. Executing the applet code, executing the J * Link class, receiving a result from an existing middleware connection, and a service request; When the J * Link 25 is applied to the systems 30 and 31 and the Java Servlet, the servlet code is called, the servlet code in the server is executed, the J * Link class is loaded, and the existing Receiving middleware, requesting services, and receiving the results into an HTML page and sending the result to a client, the client browser displaying the HTML file; When the J * Link 25 is applied to the systems 30 and 31 and the Java server page (JSP), the JSP call, the web application server compiles the JSP into servlet code, and the server servlet code It executes by selecting from the steps of execution, loading the J * Link class, connecting to existing middleware, requesting service, receiving a result, creating an HTML page, and sending the result to the client.

It can be seen that the characteristics shown above are shown in Table 1 below for each usage.

TABLE 1

division Java application Java applet Java servlet JSP Response performance Seconds / milliseconds Seconds / milliseconds / minute Seconds / milliseconds Seconds / milliseconds Availability Very high Very high Very high Very high Transition Short, N-stem, 2 pcs Normal, N-stem, 2PC Normal, N-stem, 2PC Normal, N-stem, 2PC function Java Java Java / HTML Java / HTML Expandability Multiple nodes Multiple nodes Multiple nodes Multiple nodes Connectivity MW / Network MW / Network MW / Network MW / Network Execution Preinstall on Client Download at runtime Run on web server Run on web server flexibility usually Big Big Big Maintainability bad good good good Network load impact Large (at the time of installation) Large (download at run time) little little screen Java Java HTML

In the present invention, the J * Link is to be used to integrate the applications of the legacy system currently being used by companies in the Internet-based environment, and also do not re-develop server-side business applications that are already applied to the business. Instead, it can be reused in an Internet-based environment.

By using J * Link, people who develop programs related to business logic can develop programs without understanding the Internet infrastructure, and at the same time, reduce the cost and time in the development stage, web application server and TP. Interworking function of monitor and mainframe is made possible.

In addition, the J * Link operates independently of a network protocol and a web application server regardless of a system environment behind the client server environment or a mainframe environment.

Therefore, J * Link supports all web application servers that provide servlet engines such as IBM's Websphere, BEA's Weblogic, SilverStream, Oracle OAS, and can be used in various client server environments such as Tuxedo, TOP END, CICS, and Tmax. At the same time, it will support multiple network protocols, including X.25, TCP / IP, and SNA.

Without using the above J * Link, the most difficult thing when trying to change the existing system to the Internet infrastructure is the interface problem between the existing client server application and the web application. The service provided by the environment or the mainframe environment cannot be used in the Internet environment, causing various technical problems.

To solve this problem, the basic servlet engine is provided by a web application server, and the J * Link is a system integrating a Java environment and an existing system.

On the other hand, J * Link is designed in an object-oriented concept, and using Java and C / C ++ languages, methods for legacy environments (client server environment and mainframe environment) and interfaces support servlets and applets, Even in the environment using J * Link, various servlet functions such as multithreading can be used and the same API is always provided to developers regardless of the type of legacy system in which the service is performed.

Since the method of J * Link is provided in pure Java, there is no restriction on the Java development tool to be used, and the applications developed by J * Link can be controlled not only in the management function of the web application server but also in a web application. It provides independent J * Link configuration tools and management tools for easy management even when the server is unavailable, and J * Link automatically handles user sessions according to the number of transactions that are processing user sessions to handle large volumes of transactions. It has a session pool function that increases and decreases. This function can significantly reduce costs by improving system performance and reducing the number of user licenses of legacy middleware.

Another important feature is the ability to install firewalls between J * Link components without compromising system performance, providing complete protection of hackers and crackers from legacy applications and data on legacy systems.

The J * Link of the present invention described above can be used in various places and can take various forms.

It is to be understood, however, that the present invention is not limited to the specific forms referred to in the above description, but rather includes all modifications, equivalents and substitutions within the spirit and scope of the invention as defined by the appended claims. It should be understood to do.

As described above, the present invention uses a mainframe system and a middleware TP-Monitor, which are currently used by a user, to construct a single computing environment regardless of the type or database of important systems on the network. The system has a three-tier architecture and a built-in three-tier architecture that allows you to easily move to a web (WEB) environment while retaining the client / server system that was built. Changes to the N-tier architecture of the (WEB) environment make no modifications to the server application that provides the system and business services that make full use of the functionality provided by TP-Monitor. By providing a system so that it is not necessary, companies or operators can create an internet-based work environment. Has the effect of minimizing costs, and prevents various types of risks generated in the course of work through the Internet, depending on the business, and thus the end user's physical location or required data It is very useful to have the effect of being executed at the place where the user is, regardless of whether or not the user is in operation. It is obvious that the invention.

Claims (3)

Client 10, which is an environment in which a service can be requested through all kinds of web browsers, and an application server 20, which is a hardware node of a commonly used web server, and the application server 20. In the system consisting of TOP END, Tuxedo, Entera, which are various middleware 30 systems implemented by driving a C), and X.25 and TCP / IP, which is a league system 31 that provides network services, The application server 20 includes an HTTP server 21, a web sphere 20-1 formed of a JSP 22, a servlet engine 23, and Java Beans 24, and a J * Link 25. Each product offers additional features for availability, scalability and performance, The HTTP server 21 is to provide a Java virtual machine (JVM) to use the J * Link 25, the JSP 22 and the servlet engine 23 is the dynamic activity of the Java (Java) It is a standard specification for providing dynamic http contents, the Java Beans (24) supports the business logic in the form of serialization of the Java program, the J * Link (25) is the Web sphere (20-) 1) and installed between the middleware 30 system or the league system 31 to be extended to the Internet-based environment, so that companies can easily provide the Internet-based services while protecting the existing practice Operating system with a connector function to make the compatibility between systems in the Internet environment. The method of claim 1, The Java instance 41 of J * Link is installed in the firewall 40 to maintain security to prevent leakage of information by installing a firewall 40 between the web sphere 20-1 and the J * Link 25. Operating system having a connector function to make compatibility between the systems in the Internet environment, characterized in that the communication is made so that only the J * Link Listener (42) and J * Link Communicator (43) is located outside. The method of claim 1, (1) When the J * Link 25 is applied to the systems 30 and 31 and a Java application, the client loads the application and executes the application. A step in which the results are received by class loading, existing middleware connection, and service request; (2) When using the J * Link 25 in the system 30, 31, and Java Applet, a web page is required, and the HTML page and applet code in the web server are required. Downloading the applet code, executing the applet code, executing the J * Link class, and receiving the result by the existing middleware connection and service request; (3) When the J * Link 25 is applied to the systems 30 and 31 and the Java Servlet, the servlet code is called, the servlet code in the server is executed, and the J * Link class is used. Loading, receiving an existing middleware, requesting a service, and receiving the result, and converting the result into an HTML page to a client and displaying the HTML file in the client browser; (4) When the J * Link 25 is applied to the systems 30 and 31 and the Java server page (JSP), the JSP call, the web application server compiles the JSP into servlet code, and the server Executing the servlet code, loading the J * Link class, connecting to existing middleware, requesting a service, receiving a result, creating an HTML page, and sending the result to a client, the client browser displaying the result on a screen; Operating system having a connector function to make the compatibility between the systems in the Internet environment, characterized in that carried out by selecting.