Client/server application is obsolete. An HTML page does not have the power for your next generation application. XML and Web Services are here, and K-Plex has the tools and web services to help the software developer and end user to migrate, build, expand, and customize their web application for the next generation.

  • Overview - K-Plex provides the technology to software developers to quickly migrate, build, and expand their existing application to the next generation web base application using K-Plex core technology. K-Plex core technology of the Web Services software (PlexService) and the I-Pad client visual object development platform software(PlexWare).

  • PlexService - PlexService is based on SOAP Architecture and XML. The interface includes the Legacy Database Access to MS SQL Server, Oracle, and DB2. It also acts as an application server to K-Plex I-Pad client (PlexWare).

  • PlexService System Architecture - PlexService is a COM module. It has an external interface based on SOAP and includes a component of SOAP Listener. The SOAP Listener is an IIS ASP or ISAPI extension. The Client application sends the SOAP request to IIS web server. The SOAP request is intercepted by the SOAP Listener, and it invokes a function in the PlexService COM module. Click Here for the architecture drawing for PlexService.

  • PlexServiceCore - This module is mainly responsible for mapping between an external COM Interface and functions of PlexService. Also, it executes the Unifier Function to merge tables from databases and Control Function of Active Sharing Field. (In short, this module achieves Collaboration Function.)

  • PlexAccessor or Master DB Accessor - This module accesses a Legacy Database and creates in PlexService-specific XML format as the output results. MSXML is used to create and analyze XML in PlexService. OLE DB Native Interface is used to access database. Currently, databases that can be accessed through PlexAccessor are SQL Server 2000, Oracle 8i R8.1.6 or higher and DB2 UDB V7.1. PlexAccessor also provides a function to access PlexWare repository database. The Two Phase Commit Method is used in PlexAccessor as a mechanism of controlling transactions to handle multiple databases translucently. Because of this, PlexAccessor sends two Phase Commit Controlling Module to a new plug-in DB Accessor. These two modules are built in Master/Slave Configuration in PlexService. In this Master/Slave Configuration, PlexAccessor that operates as PlexService Module is called Master and DB Accessor that is developed as a new plug-in module is called Slave. This Master/Slave Configuration makes it possible to send two Phase Commit Controlling Module, though Transaction function (Commit/Rollback Function) is to be supported in Database that is connected to DB Accessor. Click Here to see the graphic representation of PlexAccessor architecture.

  • PlexTransformer - This module transforms data in PlexService-specific XML format to another XML format. This module allows you to receive data in the desired XML format. This module transforms data in PlexService-specific XML format to another XML format. This module allows you to receive data in the desired XML format. As mounted based on COM Technology, PlexAccessor and PlexTransformer are plug-in modules. Also, PlexAccessor (DB Accessor) or PlexTransformer with desired functions can be developed and added. Click Here to see the graphic representation of PlexTransformer architecture.

  • PlexWare - PlexWare is the I-Pad client platform for end-user and an application builder tool for software developers to build and customize their web applications. Its architecture is based on the IntelligentPad(I-Pad) Research for Object-Oriented Technology led by Professor Yuzru Tanaka of Electrical Engineering at National Hokkaido Universityof Japan.

    For more information about the IntelligentPad Research, please visit the IntelligentPad Consortium web site at http://pads.kplex.co.jp/english/index.html. PlexWare is composed of a set of visual objects called PlexKlips. These PlexKlips can migrate legacy applications into the web base application, and integrate with other information or data ( i.e., legacy applications, desktop applications, Web pages, and services). PlexWare also provides end user with an environment for customization and expansion.and, therefore, it is idea for migrating the legacy application to the Internet, bringing the desktop onto the Web, and combining the customization and integration into an Enterprise Integration Portal.

  • PlexWare Architecture - PlexWare runs on the Internet browser. It has a plug-in kernel that provides drag and drop operation and message communication to the PlexKlip (Klip) on the Internet browser. The current version of PlexWare provides an ActiveX Kernel for Microsoft Internet Explorer. Each Klip (Visual Object) is a special ActiveX in the COM dll module. Klip is a building block for the PlexWare Application. Klips are divided into four types as follows:

  • Klip for Data Access
  • Klip for Visualization (UI)
  • Klip for Logic
  • Klip as a part to develop Klip

    By combining the Klips together, it forms a PlexWare Component and Application. Here is the PlexWare internal structure.

Contact a K-Plex Representative



  Copyright © 2003-2019 K-Plex Inc. All rights reserved Contact K-Plex : Webmaster : Home