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
USDL Service Marketplace OS - FIWARE Forge Wiki

USDL Service Marketplace OS

From FIWARE Forge Wiki

Jump to: navigation, search

Contents

Brief Description

Internet based business networks require a marketplace, where you can offer and deal with services like goods and finally combine them to value added services. On the marketplace you can quickly find and book services and automated services, which enables you to attend an industry-ecosystem better than before.

The USDL service marketplace enables the Internet of Services to realize the following vision: Services become tradable goods which can get offered and acquired on internet based marketplaces. Beside automated internet services this also applies for services that are provided by individuals. Partner companies can combine existing services to new services whereby new business models will be incurred and the value added chain gets extended. USDL service marketplace as essential place to go for finding services and solutions Solutions of different partners can get combined Individual service offers are possible for any customer Service partners offer own and sub-arranged services simultaneously

File:Marketplace_1.png

The marketplace includes all functionalities for service trading including the topics on the following picture:

Programming artifacts

The marketplace is embedded in the TEXO tool chain. It covers a number of adjustable processes for the customer, intermediaries and vendors. The customer can identify his/her demand, search and match existing services on the market, browse catalogs, do pricing calculations (including VAT and tax handling), configure the service offering, request a final price, order the service, monitor the ordering and installation status, and finally give feedback. The intermediaries can do administration, service maintenance, control contracting and commisioning.

The vendors can display customer request, create special offers and bargaining, receive and process orders, update the status, and invoke billing. For FI-Ware the marketplace functionality will be reduced because the high-level architecture separates marketplace and shop functions at least conceptually. Therefore the interfaces for publishing offerings, registering shops, authentication, request for quotation and other marketplace functions will be wrapped by dedicated FI-Ware GE APIs.

Technologies used

The following technologies are used in the repository asset:

  • J2EE,
  • Jboss IDE, AS, Hibernate, Seam richfaces
  • ANTL
  • Apache
  • Hibernate
  • Spring
  • SSL and X.509 certificates
  • Postgres, MaxDB
  • OpenCSV
  • Linux (Ubuntu)

The relies on the Texo USDL repository and some functionality (probably not necessary for FI-Ware) relies on additional SAP products and TEXO partner contributions.

IPR

Open Source is in planning

Publicly available documentation

The marketplace was used and further developed in the projects TEXO, Premium Services.

For FI-Ware not all marketplace functionality is needed, because the functionality is split-up into marketplace and store functionality. The challenge is to refactor the system in the appropriate way.

Personal tools
Create a book