FatWire OverView.

FatWire is a Web Content Management owned by FatWire.


  • 1996: Established by Mark Fasciano, Ari Kahn and John Murcott
  • 2003: Acquired Open Market's Enterprise web content management assets including Content Server (originally from divine).
  • 2004: Launched Content Server 6.0 WCM Software
  • 2007: Yogesh Gupta was named President and CEO in August, acquired Infostoria in October, launched their strategy for Web Experience Management in November.
  • 2010: FatWire and EMC Corporation announced a partnership in which EMC will resell FatWire's products as their strategic Web Experience Management solution. In return FatWire acquired the rights to resell EMC's digital asset management software,
  • 2011: On June 21, 2011, Oracle announced that it has agreed to acquire FatWire Software.

Products are :

  • FatWire Content Server
  • FatWire TeamUp
  • FatWire Analytics
  • FatWire Engage
  • FatWire Community Server
  • FatWire Gadget Server
  • FatWire Mobility Server
  • FatWire Content Integration Platform

Comments

Post a Comment

Popular posts from this blog

Custom Circuit Breaker Policy for Mule 4

Image
  1.​ Introduction   This document is to show the details installation and configuration for custom circuit breaker policy.   Circuit Breaker monitors API calls. When everything is working as expected, it is in the state “closed”. When the number of fails, like timeout, bad request, backend api failure reaches a specified threshold, Circuit Breaker will stop processing further requests. We call it the open state. As a result, API clients will receive instant information that something went wrong without waiting for the timeout to come.   ​2.​ Detailed Policy Design   This policy implements the Circuit Breaker pattern by monitoring a configurable number of exceptions or errors returned from the target endpoint. When the number of consecutive failures crosses a threshold, the circuit breaker trips, and for the duration of a timeout period all attempts to invoke the API will fail immediately. After the timeout expires the circuit breaker allo...
Read more

Deciding which data model to use in FatWire

How you determine which type of data model should be used for a particular content? The basic asset model is a good choice when your data has the following characteristics:- 1)It is fixed, predictable: there will be no need to add attributes to the asset type. 2)It is homogenous: all assets of the same type have similar attributes. 3)It has a moderate number of attributes. You are limited by your database as to how many columns/attributes you can have in the asset type table for a basic asset. 4)You want to use the static publishing method predominantly. The flex model is the right choice when your data has the following characteristics: 1)It has lots of attributes. 2)It can be represented in a hierarchy in which assets inherit attribute values from parent assets. 3)You cannot predict what attributes might be necessary in the future. 4)Asset instances of the same type can vary widely. That is, not all assets of that type should have the same attributes. 5)Visitors browse you...
Read more