With one tool automate the Configuration of APACHE, TOMCAT, JBOSS Application servers, and OTHERS (proprietary software) !


Whatever the trouble you're facing using Kikonf is: Contact us, no registration is needed.

From the simple Questions (mail object:Question) :
Kikonf understanding, field of exploitation, installing ...

To heavy complexe configurations across multiple servers (mail object:Scripting) :
We help you to realize powerful distributed scripting.
In order to manage and industrialize bunch of J2EE Application servers over heterogeneous software and plateforms.

We Help you to handle the tool.

Kikonf project has started in 2003.

Kikonf is a gathering of certified IT engineers (aka the ClockMakers), developing tools (Kikonf Action plugins),
for the industrialization of the management of J2EE MiddleWare Architectures, around an Universal Federating solution (the Kikonf core).

The J2EE MiddleWare area is a context where system Administrators, Integrators, developement Teams, project Managers, Architect Designers and decision Makers have to deal with rapid evolutions and swift changes,
concerning what MiddleWare Software is (or is not anymore), the Blue Print of the day, and how to glue them together.

Kikonf provides a unique platform to transversaly manage the shifting MiddleWare Software, in an integrated and long-lasting way.

Our team (working in this area), chooses to provide its skills (as plugins) around this Universal and Interoperable solution, which whatever the context may be, never changes.

This allows the sustainability of the whole entry points provided for all the previously quoted Actors, who keep the same interfaces (script layer, console and web interfaces (*)) over the contractual Architecture, whatever the undergound Software to manage is.

The Main difference between Kikonf and other solutions, is that it is thought from the ground, that means it starts by making it easy from the base scripter System engineer point of view.

Incorporating new Administrative plugins (Action plugins) for new software is as easy as glueing bricks together.
The plugin writing is thought for the most intuitive and to be the simplest (always into the Software genuine natural langage).
Afterwards, all the solutions (actual or future) naturally provided by Kikonf are automatically avalaible for the new incoming plugin.

This very clearness from the ground, impacts all aspects of Kikonf, making it strictly logical and intuitive from the view of all the other upper-layer Actors.
This brings Integrity from the System Adminisrtators to the high level GUI interface users and also eases communication between Actors.

The following is a list of the current categories provided for Kikonf. For a complete list of all plugins per category, please check here !

Kikonf currently supports configuration for the following Software :
  • apa : Support for Apache Http Server
  • tom : Support for Apache Tomcat
  • jbs : Support for JBoss
  • apa : Support for IBM Http Server
  • was : Support for WebSphere Application Server
  • wls : Support for WebLogic Server
  • wmq : Support for WebSphere MQ
  • oss : Support for OpenSSL
  • jss : Support for Java Keytool
  • gsk : Support for GSKit

  • 19/08/2010: Epicxml 4.5 alpha is finalised and plans are made for futur integration into Kikonf.

  • 02/11/2010: Kikonf 5.0 is released.

  • 25/12/2010: Kikonf plugins for Weblogic are released.

  • 25/01/2011: Apimenu 5.0 is released

  • 25/02/2011: Epicxml core is implemented into the Kikonf maintenance version.

    Epicxml supported by the kikupd commmand allows massive xml management for Standalone Actions and Custom Action files.
    Supported operation using picpaths are: select, delete, update and create.

  • 25/03/2011: Apimenu is implemented into the Kikonf maintenance version.

    Apimenu supported by the kikupd commmand allows automatic user interfaces for Standalone Actions and Custom Action files, and easy integration into your own menus.

  • 25/03/2011: Kikonf 5.1 released:

    Support of Kikonf plugins for Weblogic (added to the standard package).
    Support of massive xml management.
    Support of automatic user interface.

  • 25/10/2011: Kikonf 5.2 released:

    Support of Kikonf plugins for Java Keytool, OpenSSL and GSKit (added to the standard package).

  • 25/10/2011: Graphical Interface

    In addition to the already supported Command and Console Interfaces, more and more resources are getting involved to work on the Centralized Management Interface.

  • 05/10/2013: Back into business  

    After 2 years stop. We're back into business on Kikonf website.
    We've been working hard 2 years into higly stressed business production area stabelizing Kikonf.
    A lot of funny bugs have been walked away and many enhancements have been made to the code.
    Now kikonf is pretty mature for the production use.
    See changes-5.5.txt for changes (changes will no more appear into the home page but into a separated change_<version>.txt page).

Trademarks :
  • "WebSphere", "WebSphere Application Server", "WAS", "IBM MQ Series", "IBM WebSphere MQ", "WebSphere MQ", "IBM HTTP Server", "IHS", "GSKit", "Ikeyman" and "IBM Global Security Toolkit" are registered trademarks of International Business Machines Corporation.
  • "WebLogic Server" and "Java" are registered trademarks of Oracle and/or its affiliates.
  • "Apache Http Server" and "Tomcat" are trademarks of the Apache Software Foundation.
  • "Apache Tomcat" and "Tomcat" are trademarks of the Apache Software Foundation.
  • "JBoss" and "JBoss AS" are trademarks or registered trademarks of Red Hat.
  • "Openssl" is a trademark or registered trademark of the OpenSSL Software Foundation.
  • Other names may be trademarks of their respective owners.

Copyright © 2011 - Patrick Placidoux, Hélène Malamoud