Semantic Search Engine and Object Database Guidelines for Service Oriented Architecture Models

1.1. Project Background

Integration technologies are improved by using the Simple Object Access Protocol (SOAP) which is considered lightweight and is based on XML. This protocol is used for the exchange of information in a distributed systems environment. In addition, the Component Object Model (COM) which is from the Microsoft Windows family, is employed by the developers to re – use software components, and the Remote Method Invocation (Java RMI) enables the programmer to distribute the java technology – base to java technology based applications by invoking java objects from other java virtual machines.

In using the Enterprise Application Integration (EAI), which links the applications within a single organization, this process suffered from a lack of structure by using a point – to – point approach to link the processes. Creating architecture to reuse and integrate the classes will accelerate the development operation and reduce the cost. The guidelines work as a reference point for any companies to increase their productivity. The developers need to find the required object oriented models and integrate them to build the system easily and at a low cost. Creating a database structure which is considered one component of the system and connecting it with the search engine to facilitate the gathering of components will be a complete framework for service oriented architecture. Also, this structure is scalable to enable the developer to integrate the components from other organizations. The service oriented architecture will be used to build new systems by investing the service oriented business model and dividing the system into many partitions. Each partition is called a service. The structure enables the developers to combine one or more services to build their system. Sharing these services enables the software development companies to increase their productivity and build a large system in a short time at low cost. Finally, the information retrieval dilemma is that there are huge numbers of classes developed and to reuse these classes it is necessary to reorganize and restructure the retrieval operations to simplify access to these components. For the developers, it is a challenge to find a class which was built before hiring date and this problem also recurs with the massive amount of components especially when the documentation is very poor. Converting the system development inside the industry media into services is a big shift and it creates new perspectives for reusing these components as a business process model. There are two problems this research tries to solve. The first problem is how to create a search engine which should be semantic/ intelligent in order to retrieve the software components stored in the database. The second problem is how to store these software components in the database to facilitate the access operations which will lead to using the search engine to find the required software component.