Introduction

I maintain an application based on Remedy - Ars running a workflow application. The application is hosted on a Sun server using a local Sybase database. To monitor the server I wrote an Ars service to check the health status of Ars and the workflow application. The service was developed on Sun Solaris using a gcc compiler and a non free Remedy - Ars API. To monitor the server I'm using Moods as front-end and the service as data provider. The Moods application is using a graphic and a text based output device. The quality of information provided, combined with the easiness of using Moods, created a killer application with a strong request for additional installations. To minimize the installation requirements and maximize the support quality I decided to run the service on a Ultra Sparc 10 and only ship a generic Moods application for different kind of Unix and Windows environments. With using the service technology I do not need to port the data provider to different environments and was able to support environments with no Api support by the Remedy - Ars supplier.

the main goals of the libFreiburg 2.0 Project are:

• converting a shared library into a service
• a service is an executable, a service in a server
• one application can use multiple services
• different services communicate with a data-bus
• the data-bus is implemented as a shared/static library
• the service is available in local or remote mode
• if remote, the service is started by the inetd super-server
• if local, the service is started by the client
• the service can be created with any programming language
• the service can be accessed with any programming language
• to access a service no 'C' programming skills are required

prev: libFreiburg 2.0 - top: libFreiburg 2.0 - next: Installation

---