Technology characteristics

High level


Security

  • Runs as a spin-off module of Flex²B
    • Runs autonomous without Flex²B Cloud interface 
    • Is also embedded in the standard Flex²B Cloud interface
  • Connects to an internal MS SQL 2012 database
  • Secure tunnel through an https approach.
  • Secure through a JSON encryption, used by the framework to encrypt values and generation of checksums for validation and authentication purposes.
  • Double AES Encrypted authentication and authorisation by design.
  • Modern UX design using touch technology on dHtml (Html5), json data exchange by design
  • CSS for customer branding and UX customisation.
  • Multi device ready:
    • Modern browsers: Opera, Chrome, Firefox, Edge, Safari
    • Modern touch based interfaces (ie iOS, Android …)
  • Zero storage on device for securing information on consumer electronics (theft, loss, …).
  • User id, customer id, password secured environment.
    • When working in the Flex²B environment, users can reset, change, request password information
    • When working in the Claims spin off environment, it was intended to keep it simple and straight forward
  • Single user id and password to communicate to ERP systems 
    (plain user-id and password set up by SAP in the case of Flex²B-Dossier over a classic non secure http session)
  • https stream uploads of most popular graphical application intentions, upload and attached directly in the individual claim.
    • proof of claim
    • lower effort to check claim validity
    • easier and faster decision management
    • visualisation on claim
  • Protected against:
    • SQL injection
    • XML injection
    • Document as an argument attempt and fishing. 
  • Security docs stored local, out of the IIS reachable environment by application security on storage environment.
  • Flex²B typical document management (see also due diligence)
    • Stored as an hashed gid renamed document  


Communication

  • Towards master information
    • To retrieve delivery information on a claimed instance (stock unit number, aka pallet)
      • Via native connection to a DB
      • Via a web service call to an ERP
  • Posting information to an ERP (Flex²B acting as a client)
  • Receiving information from an ERP (Flex²B WS acting as a server)


SQL configuration

  • Attachment over a listener
  • Uses an embedded SQL user, to protect against undesired AD attacks.
  • Double AES embedded person and security information 
  • Separate Base database
  • Can run multiple F2BBase and F2BDB tenants 


Cloud environments

  • Flex²B and its components (ie Claims) run on
    • Customer hosted cloud
    • Softlayer Cloud
    • Microsoft Azure
    • Amazon WS
    • DA Cloud
  • IAAS
    • Any of the above
    • Might need a POC to see what the customer can provide to 
  • PAAS
    • When the possibility to connect to the backend ERP system is available and accessible over the public internet
  • SAAS
    • Through the ORYX cloud application
      • Need to connect to backend ERP systems and they need to be accessible and available over the public internet.

Technology inventory

  • Microsoft IIS
  • Microsoft SQL
  • Open architectures on
    • dHtml / html5
    • json
    • application encryptions
    • mime/graphics
  • Certificates for tunnelled security
  • Double AES encrypted sensitive data
  • DataFlex 18.x (upcoming 19.x)
  • Single Cloud application for browsers and touch based consumer devices (tablets…)
  • Stand alone or embedded in Flex²B 


Deployment and support

  • 1st level: in house at customer
  • 2nd level: regional consultant or Flex²B integrator
  • 3rd level: EU Team – Oryx
  • 4th level: escalation to ISVs, Cloud providers and/or ISPs


Additional

Flex²B and add-ons established communication channels over the years

  • EDI based communications using automated transport protocols or application
  • Web services
    • As a server
    • As a client
    • Soap 1.1 and soap 1.2
  • Json
    • Integrated in all Flex²B Cloud components
    • As a return mechanism on web services
  • API / REST (representational state transfer, structure defined, argument based)
    • As a client to connect to 3rd party suppliers (ie pre harvest applications)
  • Tailor made solutions
    • Intermediary information sources (ie BizTalk … ) 

Interesting white papers.

  • Using multi lingual benefits of Flex²B Cloud

Documentation, video & instruction channel.




Technical specifications

Flex²B and add-ons established communication channels over the years

  • EDI based communications using automated transport protocols or application
  • Web services
    • As a server
    • As a client
    • Soap 1.1 and soap 1.2
  • Json
    • Integrated in all Flex²B Cloud components
    • As a return mechanism on web services
  • API / REST (representational state transfer, structure defined, argument based)
    • As a client to connect to 3rd party suppliers (ie pre harvest applications)
  • Tailor made solutions
    • Intermediary information sources (ie BizTalk … ) 
    • EDI based connections