We use proprietary and third party's cookies to improve your experience and our services, identifying your Internet Browsing preferences on our website; develop analytic activities and display advertising based on your preferences. If you keep browsing, you accept its use. You can get more information on our Cookie Policy
Cookies Policy
Category:AppsFeature - FIWARE Forge Wiki

Category:AppsFeature

From FIWARE Forge Wiki

Jump to: navigation, search
This page has been generated, please do not change any content on this page, edit only the linked features on their wiki pages!

Contents

USDL Service Descriptions

Goal Description
FIWARE.Feature.Apps.USDL.BasicVocabulariesSpecification

As a provider, I would like to describe my services in uniform standard format, which is understood by many stores, marketplaces, and platform components.

The feature will provide basic description elements for services including general information, composition, simple pricing and service level agreements.


Service Repository

Goal Description
FIWARE.Feature.Apps.Repository.MaintainServiceDescription.UploadServiceDescription

Applications and end users should be able to upload a service description, or a resource to the repository.

The feature will provide basic functionality to upload a service description or a resource to the repository.


FIWARE.Feature.Apps.Repository.MaintainServiceDescription.RetrieveServiceDescription

Applications and end users should be able to retrieve a service description and any kind of resources from the repository.

The feature will provide basic functionality to retrieve a service description or a resource from the repository.


FIWARE.Feature.Apps.Repository.MaintainServiceDescription.ListServiceDescriptions

Applications and end users should be able to get a list of service description which are stored in a collection.

The feature will provide basic functionality to get a list of service descriptions from the repository.


Registry

Goal Description
FIWARE.Feature.Apps.Registry.RegisterProviderAndStore.CreateEntry

An application wants to register information about an entity.

The register must allow certain applications to publish information , such as store, provider, service endpoint, system configuration etc. for other components which need this information for proper function. For example:
  • a Store only appears on the marketplace if it is registered.
  • a provider must register to the system in order to make use of certain system fuctions.
  • A software component or service must be registered to be used in the overall business framework

etc.


FIWARE.Feature.Apps.Registry.GetProviderAndStoreInfo.ReadEntry

An application wants to find specific information about the business framework configuration

The register must allow certain applications to publish information , such as store, provider, service endpoint, system configuration etc. for other components which need this information for proper function.

This information can be retrieved by using a registry key and filtering patterns.


FIWARE.Feature.Apps.Registry.RegisterProviderAndStore.ModifyEntry

An application wants to modify information about an entity.

The register must allow certain applications to publish information , such as store, provider, service endpoint, system configuration etc. for other components which need this information for proper function. For example:
  • a Store only appears on the marketplace if it is registered.
  • a provider must register to the system in order to make use of certain system fuctions.
  • A software component or service must be registered to be used in the overall business framework

etc.

During run-time operation this information can and will change, for various reasons. For example a Service can be replaced by others or put on another machine, A provider changes its point of sale information, etc. In this case a registry entry already exists but must be changed. In many cases not only the whole entry can be changed but rather single properties, leaving the other properties in the entry untouched.


FIWARE.Feature.Apps.Registry.RegisterProviderAndStore.DeleteEntry

An application wants to de-register information about an entity.

The register must allow certain applications to retract information , because it is not longer valid. For example:
  • a Store shall not appear on the marketplace any longer.
  • a provider will not be provider any more.
  • A software component or serviceis no longer used in the overall business framework

etc.


Marketplace

Goal Description
FIWARE.Feature.Apps.Marketplace.ManageStoresAndOffers.BasicMarketplaceServices

As a user or provider I would like to upload and search/list services on the marketplace.

The feature will provide basic functionality for uploading and searching/listing of service offerings.


FIWARE.Feature.Apps.Marketplace.ServiceDiscovery.FulltextSearch

Applications and end users should be able to perform a full free text search for service offerings when using the marketplace, so that they can find the service offerings which fit to their requirements.

The feature will provide the functionality to search the marketplace for service offerings by user defined free text


FIWARE.Feature.Apps.Marketplace.ManageStoresAndOffers.StoreManagement

Applications and end users should be able to register and manage stores on the marketplace.

The feature will provide the functionality to register stores on the marketplace and to retrieve information about already registered stores. A store registration contains at least the basis URL to the Store API, as well as the ID of the User who registered the store on the marketplace


FIWARE.Feature.Apps.Marketplace.ManageStoresAndOffers.OfferingManagement

Applications (e.g. Stores) and end users should be able to create and manage their service offerings on the marketplace

The feature will provide the functionality to create new offerings on the marketplace and to retrieve information about already published offerings. A offering is always linked to a specific store and contains a link to a concrete USDL service description as well as a price plan.


FIWARE.Feature.Apps.Marketplace.ManageStoresAndOffers.UserManagement

Administrators should be able to create and manage users and their roles on the marketplace

The feature will provide the functionality to create new users on the marketplace and to retrieve information about already registered users.


FIWARE.Feature.Apps.Marketplace.ServiceComparison.CompareOfferings

Users want to have the possibility to compare offerings along multiple attributes

The feature will provide the functionality to compare offerings along multiple attributes.


FIWARE.Feature.Apps.Marketplace.PricingDecisionSupport.CreateMarketScenario

If you need further information about this component please ask SAP


Users want to have the possibility to create an abstract model of a market scenario

The feature will provide the functionality to create an abstract model of a market scenario including both the demand side (customers and their preferences) and the supply side (competitors and sold products and services) thereof.


FIWARE.Feature.Apps.Marketplace.PricingDecisionSupport.SimulatePriceLevels

If you need further information about this component please ask SAP


Users want to have the possibility to conduct simulations of alternative price levels in a modeled market scenario

The feature will provide the functionality to conduct simulations of alternative price levels in a modeled market scenario. Alternative price levels to be simulated can be selected in the form of a range of possible prices.


FIWARE.Feature.Apps.Marketplace.PricingDecisionSupport.ComparePriceLevels

If you need further information about this component please ask SAP


Users want to have the possibility evaluate how different price levels affect market and financial performances

The feature will provide the functionality to compare different price levels’ performances in terms of unit sales, revenues, market shares and profits. Tabular as well as graphical representation of the results will allow the user to readily assess which price level best fulfills his/her decision criteria.


FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.ReviewAndRating

We want to have the possibility to give ratings and reviews for services and stores.

The Review and Rating feature will provide the functionality to create and retrieve textual reviews and/or a star ratings for user-defined entities (e.g. service descriptions, offerings, stores).


FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.Recommendation

We want to have the possibility to give recommendations to users

The feature will provide basic recommendation functionality based on e.g. user ratings


FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarUsers

We want to have the possibility to find similar users for a users

This feature will return a list of users with similar interests for a given user. It may use various data sets as input for calculation (e.g. user order history items, user item ratings)


FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedSimilarItems

We want to have the possibility to give find similar items for a given item

The Get Similar Items feature will return a list of similar items for a given item.


FIWARE.Feature.Apps.Marketplace.RatingAndFeedback.RecommendedItemsForUser

We want to have the possibility to find recommended items for a user based on collaborative filtering system

Recommended items for a given user will be generated based on item ratings from similar users. This Feature depends on the Get Similar User Feature FIWARE.FEATURE.Apps.Marketplace.RecommendedSimilarUsers


Store

Goal Description
FIWARE.Feature.Apps.Store.SupportForBuyingAService

The store must allow to buy a service or application.

The store must be able to allow customers to buy applications, services or subscribe to pay per use services etc.


FIWARE.Feature.Apps.Store.SupportForBasicManagementOfOfferings

The store must provide users with a basic support for the management of their offerings

The store must offer the possibility to create, retrieve and search for offerings. Users must be able to manage their set of offerings. To do so, the store must provide an API.


FIWARE.Feature.Apps.Store.IntegrationWithMarketplace

The store must be integrated with the Marketplace.

The store must be registered in the Marketplace. This way, end users will be able to find offerings from different Stores in Marketplaces.


FIWARE.Feature.Apps.Store.IntegrationWithRepository

The store must be integrated with the Repository

The store must make use of Repositories. It must be able to handle USDL offerings as well. This implies that the store must be fully Linked-USDL compliant.


FIWARE.Feature.Apps.Store.ProvideAWebBasedGUI

The store must provide a Web based GUI

The store must provide its whole set of functionality through its own Web-based graphic user interface


FIWARE.Feature.Apps.Store.IntegrationWithRSS

The store must be integrated with the RSS GE.

The store must cooperate with the RSS GE in order to distribute the revenues originated during the charging process.


FIWARE.Feature.Apps.Store.SupportForChargingSinglePaymentServices

The store must be able to charge customers for services with single payment parts.

The Store must be able to charge customers that have acquired services with single payment parts.


FIWARE.Feature.Apps.Store.SupportForChargingSubscriptionServices

The store must be able to charge customers for services with subscription parts.

The Store must be able to charge customers that have acquired services with subscription parts.


FIWARE.Feature.Apps.Store.SupportForChargingPayPerUseServices

The store must be able to charge customers for services with pay per use parts.

The Store must be able to charge customers that have acquired services with pat per use parts.


FIWARE.Feature.Apps.Store.SupportForSocialFeatures
  1. REDIRECT FIWARE.Feature.Apps.Store.UserCentric&SocialFeatures.SupportForSocialFeatures

Business Elements & Business Models

Goal Description
FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ModelCreation

Allow business modelers to create a graphical representation of a business model

The web-based interface must provide a user-friendly, intuitive way to represent a business model, its elements (Activity, Actor, Group, VSE) and their connections (Driver, Relationship) graphically.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.XMLParsing

Allow parsing of JSON to XML and vice versa

The business modeler front-end client maintains all models in JSON format to allow for localstorage of the models and fast communication with the back-end. However all communication towards the other GE's is done through XML. A JSON to XML and vice versa parser/translator on the backend is therefore necessary.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.StorageAndRetrieval

Allow a business modeler to save and open a business model.

The BME must allow business modelers to store the business model as a file to their hard disk and subsequently open them.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UnitTestFrameworkChange

Easier creation and maintenance of unit tests

Swap Selenium to CasperJS as a unit testing framework


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.CanvasViewEnhancements

Allow business experts to have a more granular control on the business model presentation

Implement canvas zoom in and out functionality and present overlapping relationships with bridges


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.UndoAndRedo

Allow business experts to correct mistakes

Allow undoing and redoing of all user actions on the business model canvas


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendMediator

Decouple all 3rd party communication from the front-end client.

The backend mediator acts as a middleman between the business modeler front-end client(s) and the other GE's.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.BackendRESTservice

Create a RESTful interface on the backend to allow front-end clients to perform actions on resources

A REST interface should be created on the backend.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BMBCIntegrationPOC

Integration between the Business Modeler and Business Calculator GE's

Create a proof-of-concept to illustrate the integration between the Business Modeler and Business Calculator GE's


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.RSSIntegration

Allow (re)use of RSS models in the Business Modeler and Business Calculator GE's

Integrate the Business Modeler and Business Calculator GE's with the RSS GE


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.ParameterConfiguration

Allow a business modeler to configure the parameters of a business model.

The BME must allow business modelers to input and modify the parameters of the various business elements.


FIWARE.Feature.Apps.BEMES.MaintainBusinessElements&Models.BusinessModeler.RepositoryIntegration

Allow business modelers to publish their models to the Repository and retrieve them.

The BME must allow push-and-pull integration towards the Repository, using their service API.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.ECMN.ModelCreation

A web-based interface must provide a user-friendly, intuitive way to represent an ECMN model, its elements (equipment, drivers, aggregators, etc.) and their connections graphically.

Allow technical experts to create a graphical representation of equipment coupling modeling notation. ECMN is a novel visual language and specification language created within the Fi-Ware consortium.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.ECMN.ParameterConfiguration

It should be possible to set the parameters of the different elements in an ECMN model (equipment, drivers, connectors, etc.) in order to allow the modeler to calculate he results. This is also required to provide the business experts drawing the business models to have an impact on the separate sub models.

Allow a technical expert to configure the parameters of an ECMN model.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.ECMN.ModelCalculation

The ECMN calculator allows to calculate the outcome of an ECMN model when given its input values. These input values are gathered from the business modeling context and the ECMN calculator is called using the generic BusinessCalculator REST interface.

In order for the business model editor to calculate the full business model, it should execute the specific calculation modules for the modeled activities. The ModelCalculation module is a module which is capable of calculating the outcome of an activity when given the ECMN model together with the missing input to complete this model. It returns the required amounts of investments and equipment to accomplish this activity in the given business model context. Both input and output are completed by means of a REST interface and the generic XML data for this interface.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.Commenting

Add interaction between modelers in a remote manner

The commenting feature allows the user to comment in the model on changes and elements of others.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.RevenueModelCalculator

Allow the calculation of revenues from logical revenue models

The business calculator revenue model calculator enables the user to estimate revenues when presented with a predefined logical representation of the revenues, by means of a revenue model, together with the required information on costs, discounting and customers.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.RevenueModelWizard

Enable the technical expert to quickly construct a revenue model to be used in later calculation

The Revenue Model Wizard enables the technical expert to easily construct (by means of a wizard approach) a new revenue model. The revenue model is a novel specification and captures the way revenues can be modelled in a logical manner. The revenue model calculator is able to estimate revenues when presented with such model combined with information on costs and customers.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.TimedInput

Add a wizard for creating timed input information (e.g. adoption) and link them in the technical models

The Timed Input feature is linked into the editor in order to enable the user to construct the necessary input for the technical expert when constructing and analyzing technical models. The feature allows to add input that varies over time (e.g. number of customers, price erosion, etc.).


FIWARE.Feature.Apps.BEMES.BusinessCalculator.TimedOutput

Enable the technical expert to see timed information output for timed inputs

All output of the calculator should come, whenever possible, in a timed output format which enables the technical expert to inspect the outcomes of his models for a range of inputs or for changes in the input.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.OutputAnalysis

Enable the technical expert to investigate the technical model by means of advanced output windowing

The output analysis is an addition to the editor which enables the technical expert to inspect a technical model in an input-output relation and intermediate calculation steps interactively.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.CalculatorHub

Enable both a one point service, one unique REST interface and one instance for all calculators.

The calculator hub will redirect every incoming calculation call to the right calculator service based on the XML format.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.ModelRepository

Have one interface (REST) to retrieve all existing models for a given type and/or name

The model repository holds the models together with all related information on these models.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.BPMNCalculator

enable the user to calculate the costs for running (repeatedly) a given process in a set context.

The Business Process Modeling Notation Calculator is a calculator plugin with the ability to estimate the costs for running a given process in a set context when presented both the process in a (slimmed down version of) BPMN model file and all required information from the context


FIWARE.Feature.Apps.BEMES.BusinessCalculator.XPDLModelExtraction

Read an XPDL file and extract the interesting information for calculation purposes.

the XPDL Model extraction feature enables the calculator to read an XPDL file and extract only this information from there that is interesting in the case of a cost estimation. The subset of BPMN for which this XPDL model extraction will look is detailed in the calculator specifications.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.NetworkModelWizard

Enable the technical expert to detail how the network costs should be estimated.

the network model wizard enables the technical expert to detail the calculation steps to be used in network deployment cost estimation.


FIWARE.Feature.Apps.BEMES.BusinessCalculator.NetworkModelCalculator

provide a means for estimating network costs for a given network model and additional information

The Network Model Calculator enables the technical expert, the business modeler and other services to estimate the costs for installing a new network when presented with the logical high level description model and all required information such as the amount of customers, area size, etc.


Revenue Sharing

Goal Description
FIWARE.Feature.Apps.RSSS.CDRSDRLoading.CDRsReception

Revenue Sharing must support the reception of CDRs from external sources.

Revenue Sharing must support the reception of CDRs from external sources. CDRs must be submitted to the RSS GE in a file which contains a list of CDRs, according to a specified format, for a given period of time.


FIWARE.Feature.Apps.RSSS.CDRSDRLoading.CDRStorage

Revenue Sharing must store CDRs for later use.

CDRs are stored in a relational database for later use (revenue share calculation, reporting,etc.).


FIWARE.Feature.Apps.RSSS.RSCalculation.UserManagement

Revenue Sharing must support the definition of users and user roles

The feature will provide the capability to manage users allowed to use the system.


FIWARE.Feature.Apps.RSSS.RSCalculation.RSSModelManagement

Revenue Sharing must support the managment of revenue sharing models.

The feature will provide the capability to manage revenue sharing models. Each RSS model is mapped to an algorithm, which can be defined by the user. Just percentage algorithm is supported in release 0 but support for more complex algorithms will be added in the scope of FI-WARE.


FIWARE.Feature.Apps.RSSS.RSCalculation.RSSCalculation

Revenue Sharing must support the calculation of revenue shares.

Revenue Sharing must support the calculation of revenue shares for each developer based on stored CDRs and existing RSS models. This calculation is done periodically at preconfigured time intervals.


FIWARE.Feature.Apps.RSSS.RSCalculation.FlexibleRSSAlgorithms

Revenue Sharing must support a flexible way to define sharing algorithms so new ones can be easily added as required by the corresponding business models

The feature will provide the capability to flexibly define and use new Revenue Sharing models. Revenue Sharing models should support different calculation algorithms based on a mathematical function applied to a set of business parameters.


FIWARE.Feature.Apps.RSSS.RSCalculation.Reimbursement

Support reimbursement of amounts incorrectly charged to users

RSS should have the capability to reimburse incorrect charges upon customer complaints.


FIWARE.Feature.Apps.RSSS.PaymentGeneration.PaymentFileGeneration

Revenue Sharing must create a payment file, according to some agreed format.

Revenue Sharing must create a payment file, according to some agreed format. This file has to be sent to a payment broker to conduct actual payment to developers.


FIWARE.Feature.Apps.RSSS.ReportingCapabilities.AdditionalReports

Other reports about revenue sharing not shown in the Reports Feature.

RSS reports showing price interval detailed information, both in graphical and tabular format, about the revenues generated.


FIWARE.Feature.Apps.RSSS.ReportingCapabilities.Reports

Show detailed information about the revenue generated.

RSS reports show detailed information, both in graphical and tabular format, about the revenues generated split by application, developer, country etc. for a given period of time. Different type of reports will be available, such as top selling applications, transactions history and summary reports.


FIWARE.Feature.Apps.RSSS.MigrationToMySQL

The RSS database management system must be MySQL.

The feature covers the activities needed to perform the migration from the Oracle data base management system to MySQL in the settlement repository.


FIWARE.Feature.Apps.RSSS.ExpenditureManagement.BalanceAndAccumulated

Manage the expenses of a customer according the defined limit in a period of time.

This feature accumulates the different expenses incurred by a customer, giving the option to a provider of checking if this accumulated is over a limit and deny the operation in order to avoid fraud.


FIWARE.Feature.Apps.RSSS.ExpenditureManagement.ExpenditureLimits

Define and manage the expenses limits per customer and period of time.

This feature manages (creates, deletes, updates) the different expenses limit that providers will impose to their customers. These limits are used together with the balance and accumulated module in order to check if a new expense is allowed.


Composition Editor and Execution Engine

Goal Description
FIWARE.Feature.Apps.LightSemanticComposition.ModelComposition

BPMN Composition Editor enables business modelers to create service compositions using the BPMN 2.0 Graphical notation and execution semantics.

This GE provides support for service composition modeling, assuming BPMN 2.0 as graphical notation and execution semantics. Through the BPMN Composition Editor, business modelers can create or open composition models, modify them (edit) and manage them (save, delete). Composition models are stored within a Repository.

Composition edition also includes support for create/update/delete features for composition elements, such as service tasks, gateways (exclusive, parallel), flows and events (start, end).

Composition editor allows to select the composition itself or concrete composition elements.


FIWARE.Feature.Apps.LightSemanticComposition.PrepareDSLSemantics

Prepare specific languages DSL (or vocabularies) which provide concrete semantics.

In this GE approach, the business modelers describe composition models and their elements by annotating them with concepts taken from concrete domain specific languages DSL (or vocabularies) which provide concrete semantics. From operational point of view, it is common to use ontologies as DSL or vocabularies. The Light-weighted Semantic Mediator enables the business modeler to:
  • Register new DSL/Ontologies within it
  • Select a concrete DSL/Ontology for a given domain modeling context. Select a concrete DSL/Ontology concept within the domain ontology. These concepts are used to annotate and describe a composition model and their elements.


FIWARE.Feature.Apps.LightSemanticComposition.DescribeModelCompositionUsingDSL

Business modelers describes the composition model and its elements using semantic annotations.

The Light-weighted Semantic Mediator enables the business modeler to describe the composition model and its elements using semantic annotations.

In the scope of a composition task, the annotations constitute a description of the task. In other words, they describe the goal of the task. This goal will be used in the service matchmaking process to look for services whose semantic description will match it. A semantic task description is constituted by several annotations of certain type according to the semantic schema used to represent the goal (i.e MSM )

In the scope of the composition itself, the annotations constitute a description of the global composition requirements, preferences and contextual information.


FIWARE.Feature.Apps.LightSemanticComposition.DescribeServiceUsingDSL

Service Providers describes service using DSL/Semantics

Light-weighted Semantic-enabled Service Composition GE approach assumes that composable services are described using light semantics. Those semantic service descriptions are available within the Semantic Knowledge Base, and are provided by service providers. A service composition created by applying this GE approach is a service by its own, whereby the business modeler, acting as service provider, is required to provide this semantic description. Same applies to any other third party service intented to be composed by others.

The Light-weighted Semantic Mediator enables service providers to create semantic descriptions compliant to the semantic schema used by the complete GE solution. The concrete schema is left for the implementation, but it should be consistent along with all components that use it.

The schema includes links to the business oriented description stored in the Marketplace, and the technical description stored in the Repository.


FIWARE.Feature.Apps.LightSemanticComposition.BindTaskToService

Business modeler can discover and bind task to services that performs it.

One of the main jobs in service composition modeling is to bind every task the composition is divided out to a matching service that performs the task. A business modeler can conduct this task binding per task or for the whole composition. The Light-weighted Semantic Mediator enables the modeler to discover matching services based on task goal criteria, rank them according to preferences or non-functional requirements (NFR) and select one service, which is bound to the task. Those activities are typically performed by querying the Semantic Knowledge Base.


FIWARE.Feature.Apps.LightSemanticComposition.GenerateExecutableBPMNCompositionModel

Validate, generate, translate executable BPMN composition model

After binding task to service, next step in service composition modeling consists on filling the missing information that the composition model requires before being shipped for deployment and execution. Examples of missing information are:
  • Task binding technical description. For each BPMN 2.0 service task, a concrete task binding information has to be included, by inspecting the technical description (i.e. WSDL).
  • Data flow mapping, including IO mappings at task and composition level.

Once the service composition model has been completed with missing required executable information, the composition model is validated (BPMN 2.0 compliance validation) and serialized (for storage and deployment).

Optionally, the composition model can be translated from its original BPMN 2.0 format to another mappable format, such as BPEL 1.2/2.0 . This is required when the select target environment for execution is not BPMN 2.0 compatible.


FIWARE.Feature.Apps.LightSemanticComposition.DeployAndExecuteCompositionModel

The application can deploy and execute composition model

Full executable validated composition models can be deployed into the selected target Composition Execution environment, using the Composition Deployer. Once deployed, the service composition is enabled, being ready to received incoming requests from service consumers.

Similarly, deployed service compositions can be undeployed anytime.

During the execution time, deployed services can be enabled or disabled any time through the Composition Execution UI. Besides, running compositions (enabled) can be continuously monitored and monitoring data can be collected for given time frames.


FIWARE.Feature.Apps.ServiceMashup.MashupCreation.MashupFactory-Compose

Edit mashup

The editor contains a repository of categorized services and a work surface to combine the services.

Services can be added via drag & drop from the repository to the work surface. A short service description is given in the left corner. Services have input and output ports and can be connected via linking input and output ports. There is a type checker which allows to connect only correct data types, e.g. date with date. The configuration of certain services with configuration data, e.g. the web dialog is possible. The web dialog service supports to communicate with a user in a web browser and transfer the user data to other services. When the service is composed (i.e. all input ports are connected with an output port), the composition is saved by giving it a name. Debugging of a service by going step by step through the service is possible.


FIWARE.Feature.Apps.ServiceMashup.MashupCreation.MashupFactory-Install

Manage composed services

Mashups can be installed and managed, i.e. activate, stop, publish or remove services.

Status of a services can be watched and the period of activation can be defined.


FIWARE.Feature.Apps.ServiceMashup.MashupCreation.MashupFactory-Test

Test composed mashups

Composed services can be tried out by clicking Test. Services can be tested with the user account of the composer or with a dedicated user name to consume the service.

After login a list of services of this user is displayed and a service can be started via click on the link.


FIWARE.Feature.Apps.ServiceMashup.MashupCreation.GeoLocationSearch

Integrate services that allow to search for places nearby a given geo position

Extend the functionality of the available services by allowing to search for places of interest in a given radius around a given geo position.


FIWARE.Feature.Apps.ServiceComposition.CreateComposition

Creation of a Service Composition

Provides a graphical tool for the design of compositions. The tool is using [Ericsson Composition Editor] constructs and the created compositions and service descriptions are described in the Ericsson Composition format, using the building blocks described in the architecture:Start, Service Template, Condition, SSM Command, Goto, End. This composition type uses dynamic events for flow management and constraint resolution for late service binding.


FIWARE.Feature.Apps.ServiceComposition.CreateServiceDescription

Create a description to remotely access the different services w.r.t. their interface technology (SIP, WSDL, REST, RMI) within a composition.

Users have the possibility to create and edit component services. When creating a service description the user specifies what service type(s) this service is (e.g. SOAP, REST, SIP, etc). Then the user specifies values for the attributes that will be used when invoking the service (e.g. in case of a SOAP service the namespace, the port, the operation, the parameters passed to the operation, etc). The attributes to be specified could be either fixed or variable. Once a service is created it is stored in the local descriptions storage. Subsequently the user can browse and edit the description of component services that can be used in the composition.


FIWARE.Feature.Apps.ServiceComposition.ConstraintsEditor

Support for specifying service constraints.

Specification of constraints are used to decide runtime service selection (late binding) and event filtering. A global constraint can be specified in the skeleton start element, and is valid in the context of the composite service, for example all services used in that particular skeleton must be SIP services (syntax example: $(srv.type)='SIP'). A local constraint is to be specified within a service template. A constraint matches a service attribute against any SSM variable or literal value. To help user edit constraints a tab-completion feature matched against all potential service variables is provided.


FIWARE.Feature.Apps.ServiceComposition.ExecuteComposition

Execute a service composition.

Given a composition description (a skeleton) in the Ericsson Composition Format, the enabler can get such a composition as input and can enable and disable it from being triggered for execution. If enabled, runtime for the composed service is created and an API exposed to accept invocations as specified by the composition description. When invoked, the composed service will run the course of the specified control flow and will invoke on its turn all necessary component services to provide the specified invocation action.


FIWARE.Feature.Apps.ServiceComposition.ConstraintsResolutionAndDynamicBinding

Selecting the next service to execute is a combination of constraints resolution against the shared state of the composition engine, and the protocol steps of the active composition execution agent.

Protocol-level details related to the interaction with modules are left to the Composition Execution Agents (CEAs), which are responsible for enforcing composition decisions in the corresponding platform in a technology and protocol specific way. A shared state is used as means of mediating information between the application skeleton and the CEAs, thus coordinating the service execution. Based on what the triggering events was, the composition engine selects the matching skeleton and creates a new session. Then, at each step it selects a suitable service that matches all the constraints and serves it to the agent to execute.


FIWARE.Feature.Apps.ServiceComposition.ServiceCompositionCloudReady

The Service Composition enabler needs to be hosted in the cloud to provide flexible and scalable composed services.

The feature makes the Service Composition cloud ready and provides for some load balancing and multitenancy features.


FIWARE.Feature.Apps.ServiceComposition.ImportExportServiceDescriptionsAndSkeletons

Service descriptions and skeletons internal description should be converted from/to XML to be further exchanged between the local storage and the Repository.

In order to execute a composition the Service Composition enabler stores the service and skeleton descriptions in a local storage. These local storage needs to be read and wrote to in a specific manner.


FIWARE.Feature.Apps.ServiceComposition.IntegrationWithUSDLEditor

{{subst::FIWARE.Feature.Apps.ServiceComposition.IntegrationWithUSDLEditor}}

FIWARE.Feature.Apps.ServiceComposition.IntegrationWithRepository

A Repository is expected to hold the complete description of a composition, to be retrieved and reused by another party. Users should be able to import and export compositions in the Repository.

The Composition Editor needs to import full descriptions (both USDL and technical) of utilized component services and of the compositions themselves from the Repository. In this way compositions can be executed and further edited. It also needs to export created compositions and service descriptions into the repository.


FIWARE.Feature.Apps.ServiceComposition.IntegrationWithMarketplace

{{subst::FIWARE.Feature.Apps.ServiceComposition.IntegrationWithMarketplace}}

FIWARE.Feature.Apps.ServiceComposition.ContractFromStore

{{subst::FIWARE.Feature.Apps.ServiceComposition.ContractFromStore}}

FIWARE.Feature.Apps.ServiceComposition.PublishServiceToStore

{{subst::FIWARE.Feature.Apps.ServiceComposition.PublishServiceToStore}}

FIWARE.Feature.Apps.ServiceComposition.SupportForIdManagement

{{subst::FIWARE.Feature.Apps.ServiceComposition.SupportForIdManagement}}

FIWARE.Feature.Apps.ServiceComposition.SupportForOAuth2

{{subst::FIWARE.Feature.Apps.ServiceComposition.SupportForOAuth2}}

FIWARE.Feature.Apps.ApplicationMashup.WidgetOperatorDevelopmentEnvironment
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.DevSupport.WidgetOperatorDevelopmentEnvironment
FIWARE.Feature.Apps.ApplicationMashup.CreateUIOrientedServiceComposition

End users shall be able to compose Applications via composition of User Interface (UI) widgets using a composition editor without programming skills

End users can create new applications, also referred as mashups, by wiring UI components called widgets, searched and selected from a catalogue. Those widgets can communicate between themselves at runtime based on the Event-driven Widget communication mechanism supported by the Application Mashup. End users can also import mashups defined by other users as a whole, either from the catalogue or from a mashup description file in MDL. Imported mashups can be enhanced by adding new widgets from the catalogue that may be wired together with the widgets in the original mashup. Last but not least, the user can store the resulting composite application in the catalogue for reuse.


FIWARE.Feature.Apps.ApplicationMashup.SupportEventDrivenWidgetExecution

Application Mashup must support execution of event-driven widgets that asynchronously communicates with other widgets possibly executing in different execution environments (browsers, hosts, etc.) through a kind of Web-enabled pub/sub middleware.

Widgets in a mashup could need to asynchronously communicate with other widgets either in the same or in different execution environments, using a push communication model in the latter case.


FIWARE.Feature.Apps.ApplicationMashup.SupportPushCommunicationToClientWidgetsFromServers

Application and Services running at the backend should be able to push data to widgets running at client's browser

Certain applications may require that backend services be able to push data into widgets that are part of a mashup application running on a client browser. This requires both a html5 javascript pub/sub API in the client side, and the corresponding server side pub/sub API. It also requires a pub/sub middleware to be plugged in the Application Mashup (i.e. a plugin architecture in the Application Mashup)


FIWARE.Feature.Apps.ApplicationMashup.SupportForPiping

End users can operate (filter, aggregate, ...) with data from the backend services

The Application Mashup should give end users the possibility to adapt, filter, merge, sort,... data from the backend services to make use of it in their mashups.


FIWARE.Feature.Apps.ApplicationMashup.SupportForW3CWidgets
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForW3CWidgets
FIWARE.Feature.Apps.ApplicationMashup.SupportForOpenSocial
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.SupportForOpenSocial
FIWARE.Feature.Apps.ApplicationMashup.AllowHostingWidgetsInContainerApp
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInContainerApp
FIWARE.Feature.Apps.ApplicationMashup.AllowHostingWidgetsInWebBasedSystem
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.AlignmentWithStandardizationInitiativesAndProjects.AllowHostingWidgetsInWebBasedSystem
FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithNGSI-10QueryBrokerGE

Developers can easily make use of NGSI-10 systems when developing widgets/operator for the Application Mashup GE.

The Application Mashup GE will be integrated with the NGSI-10 GE of the Data chapter.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithDataChapterCEPGE

Developers can easily make use of CEP systems when developing widgets/operators for the Application Mashup GE.

The Application Mashup GE will be integrated with the Complex Event Processing GE of the Data chapter.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithDataChapterPubSubGE

Developers can easily make use of pub/sub systems when developing widgets/operators for the Application Mashup GE.

The Application Mashup GE will be integrated with the pub/sub GE of the Data chapter.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithDataChapterLocationGE

Developers can easily make use of location services when developing widgets/operators for the Application Mashup GE.

The Application Mashup GE will be integrated with the Location GE of the Data chapter.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithCloudChapterObjectStorage

Developers can easily make use of Object Storage services when developing widgets/operators for the Application Mashup GE.

The Application Mashup GE will be integrated with the Object Storage GE from the Cloud chapter


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithUSDLEditor

The Application Mashup will use USDL files created in the USDL Editor Tool

Publishing a mashup into the Marketplace needs a USDL file describing the offering. This USDL file is created with the USDL Tool. The Application Mashup will upload this file and will include the required technical information on it before having the application published.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithRepository

Users of the Application Mashup will get offerings from the Marketplace, retrieving them from the Repository. They will be able to publish their composed mashups on the Marketplace, and thus, storing them on the Repository.

The Application Mashup must be fully integrated with the Repository. It must use their APIs to store and retrieve offerings.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithMarketplace

Users of the Application Mashup will get offerings from the Marketplace. They will be able to publish their composed mashups on the Marketplace.

The Application Mashup must be fully integrated with the Marketplace. It must use their APIs to provide its users with the ability of publishing mashups, storing USDL, and retrieving offerings to have them installed in the local catalogue.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithStore

The Application Mashup must be integrated with the Store

The Application Mashup must offer the possibility to access the Store through its API to allow users, among other things, to place, retrieve and search offerings as well as make use of its social features, such as social rating and feedback.


FIWARE.Feature.Apps.ApplicationMashup.IntegrationWithIDManagementSystem
  1. REDIRECT FIWARE.Feature.Apps.ApplicationMashup.IDManagementSupport.IntegrationWithIDManagementSystem
FIWARE.Feature.Apps.ApplicationMashup.SupportForOAuth2

Authorisation of access to resources should support the OAuth2 protocol.

Every action the Application Mashup executes on behalf of the user needs to be authorized in a manner compatible with FIWARE platform. One of the supported authorization protocol should be OAuth2.


FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithUSDLEditor

Integrating a newly created composition into the business framework requires a USDL file describing the offering. The USDL description is created with the USDL editing tool and needs to be merged with the technical composition information for a complete description and further publishing.

The Light Semantic Composition will provide a tool to create a USDL file which will describe the composite service built.


FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithRepository

A Repository is expected to hold the complete description of a composition, to be retrieved and reused by another party. Users should be able to import and export compositions in the Repository.

The Light Semantic Composition will allows to manage (import/export) with the Repository, all the technical description (i.e. WSDL , WADL , etc) of services aggregated in the composition and the composition themselves.


FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.IntegrationWithMarketplace

Users need to find suitable services in the Marketplace to use in their compositions. They should also be able to publish they composition in the Marketplace and properly annotate for subsequent searches.

The Light Semantic Composition must be integrated with the Marketplace that is used to query and retrieve USDL service descriptions for those services matched to composition tasks through semantic matchmaking, thanks to links contained within their semantic descriptions.


FIWARE.Feature.Apps.LightSemanticComposition.IntegrationWithGEs.SupportForIdManagement

Authenticate and authorize users by means of the FIWARE ID Management System.

The user must be authenticated and authorized, allowing the Light Semantic Composition can interact with the rest of components.


Mediation

Goal Description
FIWARE.Feature.Apps.Mediation.AdvancedSemanticDataMediation

DataFlow Mediation based on semantic plugin and intersection

Advanced data mapping of elements in the I/O that ara not exactly matched.


FIWARE.Feature.Apps.Mediation.RunTimeProcessModelling

DataFlow Mediation based on semantic plugin and interseaction

Advanced data mapping of elements in the I/O that ara not exactly matched.


FIWARE.Feature.Apps.Mediation.BPMN20CompliantFileGeneration

Get a BPMN2.0 fully compliant file

Completing BPMN2.0 file


FIWARE.Feature.Apps.Mediation.BPEL1.2CompliantFileGeneration

Get a BPEL1.2 fully compliant file

Completing BPMN2.0 file


FIWARE.Feature.Apps.Mediation.ProtocolMediation.SOAP2REST

Allows to expose a REST Service with XML payload through SOAP protocol in order to enable a Compositor Editor supporting SOAP to compose REST Services

A REST service with XML payload will be exposed by the mediator via SOAP, as a document/literal wrapped SOAP service: the SOAP service exposed uses as payload for each operation the REST service corresponding operation payload, incapsulated in an element whose name is the one we have given to the SOAP operation (the payload is incapsulated in the SOAP Envelope).

The Mediator SOAP service can expose a custom WSDL imported through the WEB GUI. In the first release the Mediator allows to create a Mediation Service (as SOAP2REST) only through the Mediator GUI and it will not provide automatic WSDL generation. If a custom WSDL is provided and imported into the Mediation Service a client generation tool is provided by the Web GUI in order to create the client code


FIWARE.Feature.Apps.Mediation.ProtocolMediation.SOAP2POX

Allows to expose a POX Service (Plain Old XML) through SOAP protocol in order to enable a Compositor Editor supporting SOAP to compose POX Services

A POX service will be exposed by the mediator via SOAP. The SOAP service exposed uses as payload for each operation the POX service corresponding operation payload (incapsulated in the SOAP Envelope).

The Mediator SOAP service can expose a custom WSDL imported through the WEB GUI. In the first release the Mediator allows to create a Mediation Service only through the Mediator GUI and it will not provide automatic WSDL generation. If a custom WSDL is provided and imported into the Mediation Service a client generation tool is provided by the Web GUI in order to create the client code


FIWARE.Feature.Apps.Mediation.ProtocolMediation.TCP2HTTP

A client shold be able to call a service exposed via HTTP using TCP transport

Mediation task configuration that allows to call a service exposed via HTTP using TCP transport.


FIWARE.Feature.Apps.Mediation.ProtocolMediation.Security

Allows to manage the securiy issue base don WS-Security mechanism handling the authentication issue and managing WS-Security header. This mediation service requires the ws-security header in the SOAP request of the calling client, performs authentication, remove the WS-Security header and call the target service. It finally restore the WSA-Security header in the response.

ManagesWS-security authenctication


FIWARE.Feature.Apps.Mediation.UsageAndReliability.LoadBalancingEndpoints

It allows to load balance different endpoints based on various algorithms

A mediator task able to load balance different endpoints based on various algorithms


FIWARE.Feature.Apps.Mediation.UsageAndReliability.FailoverAEndpoints

It allows to configure different service endpoints in a failover configuration

A mediator task able to use different service endpoints in a failover configuration


FIWARE.Feature.Apps.Mediation.EventBrokering.Geofencing

A mediator service for managing a geofencing service and brokering geofencing events

The Geofencing service allows to set virtual perimeters (circular or polygonal) and to be notified when a specific device previously subscribed to the service enters or exits that perimeter. Moreover the service allows to send notifications to the subscribers when events are collected. This mediator allows to manage this kind of service and particularly:
  • add/remove subscribers
  • to collect positions from mobile devices
  • to set up virtual perimeters (circular and polygonal)
  • to dispatch geofencing events (enter geo-fence, exit geo-fence, tracking)


FIWARE.Feature.Apps.Mediation.TaskManagement.SplitAndAggregationPattern

A mediator service able to implement the split-aggregator pattern in order to manage the dispatching of a composite message and managing the replies. The message shall be split and each item has to be sent to the right receiver. In the same way the replies shall be aggregate in order to compose the whole response.

A mediator service able to implement the split-aggregator pattern in order to manage the dispatching of a composite message and managing the replies. The message shall be split and each item has to be sent to the right receiver. In the same way the replies shall be aggregate in order to compose the whole response.


FIWARE.Feature.Apps.Mediation.DataMediation.JSON

Support JSON message payloads

Handle services that use a JSON format in message payload representation


FIWARE.Feature.Apps.Mediation.EventBrokering.GeofencingSmartphoneClient

Geofencing mediator service clients for mobile devices

Implementation of Geofencing mediator service clients to run on mobile devices, in order to register/unregister to the localization service and to notify their position changes.


FIWARE.Feature.Apps.Mediation.Monitoring.SNMPMonitoringSupport

Monitoring Mediation GE with Simple Network Management Protocol (SNMP)

We expose mediation stats with Simple Network Management Protocol (SNMP).


FIWARE.Feature.Apps.Mediation.Performance.ImprovedMediationPerformance

Improve Mediation GE mediation performances

Improve Mediation GE internal performances in mediation processes


FIWARE.Feature.Apps.Mediation.ProtocolMediation.EnhancedRestfulSupport

Enhance the integration with REST services

Add to Mediation GE useful features to make REST services mediation easier and more powerful


FIWARE.Feature.Apps.Mediation.UsageAndReliability.PoliciesBasedThrottling

It allows to restrict the usage of a service through policies.

A mediator task able to restrict the usage of a target service based on source IP address or domain, the number of maximum concurrent connected clients and the rate of request in a time window


SLA Management

Goal Description
FIWARE.Feature.Apps.SLAManager.SLAModel

{{subst::FIWARE.Feature.Apps.SLAManager.SLAModel}}


(previous 200) (next 200)

Pages in category "AppsFeature"

The following 200 pages are in this category, out of 360 total.

F

F cont.

F cont.

(previous 200) (next 200)
Personal tools
Create a book