Life Cycle

Products reach the end of their life cycle for various reasons, such as:

  • Market demand.
  • Technological innovation.
  • Changes in direction in product development, or simply because products mature with time and are replaced with more high-functioning technology.

This evolution is just one more part of the complete product life cycle, and understands that when a product’s life cycle comes to an end, companies should analyze and examine the impact that this milestone may have on their organization. With this in mind, we’ve established the end-of-life (EOL) policy to help clients better manage their transition to new products or versions, as well as understanding the role that can play to help them migrate to alternative products, versions or technology.

Deister’s support life cycle guidelines provide predictable and consistent instructions about the availability of support during a product’s launch and life cycle. By knowing what types of support are available for the product, clients can take better advantage of their investment in technological innovation and plan their future in the tech environment strategically and successfully.

The end of the life cycle comes when no longer offers updates to resolve issues, patches, assistance or technical support for discontinued versions of the product.

Product Life Cycle / EOL Table


Life Cycle and Update Policy

Release Year Full Support  Transition Maintenance Discontinued Life Span Technological changes
1989 1995 1996 1997 January 1998 6+2  C
1996 2004 2005 2006 January 2007 8+2 Java 1.0, Servlet 2.2, JSP 1.1, NS3
2005  2014 2015  2016 January 2017 9+2 Java 1.5, Servlet 2.4, JSP 2.0, NS8, IE7
2015 2024(i) 2025 2026 January 2027 9+2 Java 1.8, NIO, Servlet 3.1, JSP2.3; EL3.0,
WebSocket 1.1, Firefox, IE11, Chrome, Safari

Estimated Support for the 2015 Product Line


Support is divided into three consecutive periods which determine the benefits offers for adopted products.


Full Support

Our products are fully supported with complete service, including:

      • Complete production support.
      • Major and minor updates.
      • Service Pack and issue resolution.


During this period, previously-offered benefits and features will be maintained and transition planning to a new available version may begin. During this phase, the company does not support the incorporation of new functionality or technological changes such as new browsers, operating systems or infrastructure (databases, Java JDK, Tomcat, etc.).

For reference, Axional 2005 includes support for Java JDK 1.7, Tomcat 5.5.35, Linux RH 6, RH7, CentOS 6 and browser support for CentOs7, and FF 37, Chrome 42, and MS IE 10 and 11.


If a client wishes to maintain an old product version, they will have some limited services available:

      • Complete production support.
      • Specific Service Packs.


When the product life cycle reaches the discontinuation phase, we recommend clients migrate to the new Axional product line. This migration may entail changes in licensing policy and system architecture.

If migration is not carried out, it may be possible to acquire Special Support Extension (SSE) so clients can maintain complete coverage before end of service and ensure their company is protected.

As such, continuous support will be available so that your company can keep functioning until you are able to migrate to the new Axional product line in such a way that service is not interrupted.

SSE, in these cases, does not involve fixes or updates, nor does it support new features.

Why Upgrade?

For companies, upgrading to the new Axional product line offers several advantages:

      • Exceptional performance.
      • Access to the latest application server technologies.
      • Greater security based on new role-based access control algorithms.
      • Support for latest-generation browsers.
      • New Business Intelligence solutions and OLAP engines.
      • Native support for the use of Informix Warehouse Accelerator (IWA).
      • Integration with the new Axional IB and Axional Studio product line.
      • Ability to obtain geofencing statistical data.
      • New business graphic creation functions.
      • Reliability and effectiveness.
      • Full integration and transparency.


      • The number and type of usage licenses can be better adjusted to the needs of your company.
      • The SaaS model lets you easily adapt to the fluctuations and flow of your business.
      • Purchased licenses that are no longer used become a thing of the past.
      • Software runs on an operating expenses (OPEX) model rather than a capital expenditure (CAPEX) model, so it’s easier to schedule around budgetary periods.

EOL (End-Of-Life) Policy

At we want to provide our clients as much information as possible so they can make the best decisions and plan their evolution towards a new product line that adapts to their company’s needs and makes them more competitive in the current market.

That’s why our products have an approximately 10-year life cycle, to make way for a new line of solutions more in touch with the technologies of the present moment.

End of Life (EOL)

Products reach the end of their life cycle for various reasons:

      • Technological innovation.
      • Market demand.
      • Discontinuation.

As a result, we’ve established an EOL policy to help clients better manage their transition and so that can help them migrate to new, updated product lines as part of their renewal path.

General policy guidelines are:

      • As a general rule, will alert clients to the date of end-of-life (EOL) for a product. This alert will also appear on the  blog.
      • When a product reaches EOL, all support services will become unavailable and the product will be obsolete and no longer catalogued.
      • After the EOL date, does not commit to developing, fixing or maintaining a product.
      • So long as the client is up-to-date with product maintenance, SSE (Special Support Extension) will be provided and must be adopted immediately after the product EOL. Please contact the administrator of your support account to adopt SSE before the EOL of your product so that we can assist you during the transition period.
      • If a client is not up-to-date with maintenance and wishes to adopt SSE at the end of a product’s EOL, they must pay retroactively for maintenance since the last adoption of service or, alternatively, since the date of product purchase.
      • If a client decides to make a change to new hardware during a product’s EOL Transition period, a new license for the new hardware will be required in accordance with the current licensing policy in effect. In addition, is not responsible for the functionality of applications until the client migrates to the current Axional product suite.

reserves the right to modify the present EOL policy for different product lines.
Any modification to product policy will be communicated to all clients and published in the support policy section for EOL products on the website.