Browse Prior Art Database

Dynamic Service Architecture for Distributed Service Code Disclosure Number: IPCOM000238970D
Publication Date: 2014-Sep-29
Document File: 5 page(s) / 81K

Publishing Venue

The Prior Art Database


Disclosed are a method and process for automatically sending Domain Specific Language (DSL) service code, written by the software developer, to the services server from the application. This enables an application developer to build out services in an application during the coding phase, but have the service executed in the context of the server, rather than locally executing the service in the application.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 29% of the total text.

Page 01 of 5

Dynamic Service Architecture for Distributed Service Code

In this article, all numbered references refer to the figure below, representing the novel process for transparently sending Domain Specific Language (DSL) service code to the server from an application.

Figure: Components and process for transparently sending Domain Specific Language (DSL) service code to the server from an application

A software developer(3) developing an application (4) that relies on services (2) for its data source is dependent on the service provider (1) to create and register the services before the developer can build out the application to consume those services . In some cases, the service provider may have a suite of services exposed, but the software developer requires additional services in


Page 02 of 5

order to complete the application. In some cases, a service provider may grant the developer access to the server to create and deploy owned services, but the process involves the developer having access to the server and for the developer to manually update the server as required.

The problem addressed herein involves a method of automatically sending DSL service code, written by the software developer(3) to the services server (2) from the application (4), and therefore exposing a new service that is built out and maintained by the software developer (3) during the development phase of the application development lifecycle. This process no longer requires the service provider (1) to be involved during the Service creation phase. Once a service is fully completed, the service provider (1) can publish the new Service and make it available to everyone.

Current processes involve the software developer (3) to creating code and deploying that code to a remote server location, but only if the service provider (1) has granted the developer filesystem access to the server, and optionally allowed the developer to restart the server, for changes to take effect. If a server is running web services such as Axis*, then the developer can deploy a Java* Server Page (.jsp) to the server with the code required to build out the service. In both cases, the developer must send service code to the server and install that new service into the server.

The novel contribution is a method and process that enables a developer (3) to create a new service, or enhance and existing service (5), and then have the application (4) transparently transmit the service to the server's services (2). There, it is exposed as a service (6), enabling the application (4) to call that service as any other service that is exposed by the server. After the application and Service code have gone through many iterations and the developer (3) is satisfied with the service content (5), the service provider (1) approves that Service (8) and allows it to be published (9). At that point, other developers and client applications can consume it.

The novelty of the proposed solution is that the app...