Skip to content

Specialty Middleware

August 7, 2009

Several types of middleware provide for specific needs. Since they may not fit any of the categories above, this category was created to hold these special types. Four of these stand out, and even though there appear to be more types on the web, this thesis will cover only these.
The first is called multi-campus system middleware. This middleware uses the policies and relationships around common identifiers, search defaults, and directory configurations. People (applicant, student, alumni, faculty/staff, and retiree) are assigned permanent and unique identifiers. This means that no matter where the person goes within the system the same information will follow them. The middleware works with the database transparently. It controls the security (authentication of user), access, and privacy (only allow certain users to see sensitive information) of the database. It also consists of advance tools like desktop video, distributed computing systems, collaboration environments. Essentially, it makes many computing activities much simpler. One way is by removing the need for multiple passwords and the annoyance and security problems associated with them.
Another special middleware is called medical middleware. It covers enterprise issues such as security, directories, and authorization. It is a balance of institutional and medical enterprises. This middleware allows the sharing of data between institutions, medical centers, affiliated hospitals, state and Federal regulating and certifying bodies, organizations, insurance companies, medical researchers, etc. This middleware covers issues such as standards, common operational process and policies, etc. It manages the gateways to other computing systems (Peer Institutions, Corporate Collaborators, etc.) and assists with the performance of the enterprise system.
The third middleware is Ontology middleware. This middleware provides many services that allow users to easily employ and integrate ontological technologies into existing and future database systems. These services include accessing ontologies, ontology upgrading, query services, integration databases, etc. There are two major activities to be performed on an ontology system: development and management. The development activities performed are knowledge acquisition, editing, browsing, integration, merging, evaluation, implementation, etc. The management activities include configuration management, ontology evolution, ontology libraries, scheduling, and documentation, etc.
The fourth specialty middleware discussed in this thesis is called PDES (Parallel Discrete Event Simulation Systems) middleware. This is used to simulate extensive applications (telecommunication networks, transport grids, battlefield scenarios, etc.). The middleware is used to enhance the visualization system with specific views, and to manage requirements needed with the simulation. It provides an accurate picture of the system being monitored by showing specific values. These consist of the amount of time needed to advance the simulation by a single unit of time; percent of rolled back events for late arrivals and processing anti-messages; percent of events aborted; and memory usage.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: