External Interfaces Design. The following external interfaces will be provided by the ESB: • Data Access: Supports messaging communications ( IEC 61968-100 standard); • Services Access: Exposes the services (i.e. orchestration services) as a web service; • Admin: Exposes the management of services and business processes as a web service. 2 Additional measures like two-factor authentication will be specified in deliverable D4.5. There are several integration patterns described in IEC 61968-100 [7] for implementing communications. The most basic ones, concern: • Synchronous request/reply, through web services or JMS queues; • Asynchronous request/reply, through web services (using callback) or JMS queues; • Publish/subscribe, through web services (using callback) or JMS topics3. Services Access and Admin interfaces’ provided methods are explained in Table 11 and Table 12. Method Parameters Response Description invokeService Service ID Call Parameter (Session Ticket) Service Response Calls a service with the provided parameter and returns the response. getServiceInfo Service ID (Session Ticket) Service Description Provides the description of a service. getServiceStatus Service ID (Session Ticket) Service Status Provides the status of a service. Table 12 Admin interface Method Parameters Response Description registerService Service Description (Session Ticket) Service ID Add a new service in the registry providing any relevant parameters. updateService Service ID Service Description (Session Ticket) Success Code Updates the details of an existing service in the registry. deleteService Service ID (Session Ticket) Success Code Deletes a service from the registry. getServiceList (Session Ticket) List of Service objects Returns the list of services. addRoute XML file (Session Ticket) Success Code Creates a specific routing design from/to an endpoint(s) and returns the route id or an error code. deleteRoute XML file (Session Ticket) Success Code Deletes a specific route. startRoute route ID (Session Ticket) Success Code Initiates a specific route. stopRoute route ID (Session Ticket) Success Code Stops a specific route. getRouteStatus route ID (Session Ticket) Route Status Provides the status of a specific route. addBusinessProcess XML file Business Process ID Save a business process in the repository. deleteBusinessProcess Business Process ID Success Code Deletes a business process from the repository. 3 Topics are used when the destination of a message is potentially more than one process, w...
External Interfaces Design. Table 25 presents the external interfaces and underlying methods provided by DAP. Interface Name Method Parameters Response Description Data Access retrieve Data Query Data Payload Retrieves a data set based on the data query. store Type, Data Payload Success Code Saves the provided data set. Visualisation Access retrieve Visualisation Identifier, Query Params Embeddable iframe Returns an interactive embeddable visualisation. Analytics Exec execute Process ID, Process Params Process Result Start execution of a calculation process. info Process ID Process Status Retrieves the information of a calculation process and its current status. Admin Access add Process Name, Process Description, Process Code, Process ID Stores calculation process code. delete Process ID Success Code Deletes a calculation process. list - List (ID, name, description ) Lists all stored calculation processes.
