Home > Kikonf compared to other MiddleWare Global Administration Software

Kikonf compared to other MiddleWare Global Administration Software

Providing facility management services for MiddleWare J2EE Applications can a be a Nightmare since:
  • Many Applications are involved.
  • Many 3rd party Software (*) must be configured and glued together to match one set of deployed MiddleWare Application criteria.
This complexity is also increased by the fact that Applications are generally sprayed on more than one environment.

In this context we generally find as many script layers as frontend or backend software that need to be configured.

It is in this area, that Kikonf brings significant value,
Kikonf provides a versatile central management system for all the incoming Applications.
Taking care of each environment and required resources for the whole dependant Software.

  • Oh my god another console (over my software console) !
    Kikonf is inspired from more then 10 years of work in critical J2EE Environments (mostly in banks and insurance companies, ISPs).
    And written by J2EE experts many times certified not only on J2EE Developement but also on the best typical Application servers of the market.
    This is why every Action plugin for Kikonf comes with the most typical parameters (even if it is easy to add new ones).

  • A blind shape cover over my software scripting layer !
    Definitly not !
    As J2EE experts we well know the strength of software native scripting langages (e.g.: jython is one of them).
    As a general rule all Action plugins are based on them.
    We definitly do not want to hide it or to obfuscate it.
    All Kikonf Action plugins are open (under the bsd licence), so you do not loose your skills using a black box, as it is easy to modify Action plugins, to promote them to your own version (by simple copy), or to eventually redistribute them or to sell them if you feel like it.
    Kikonf plugins can also be seen as a good educational ground for some scripting tricks you don't already know.

  • A central interface for the whole Application configuration.

  • This interface provide entries for what the users (*) need to see.

  • The security layer allows fine grain restriction levels, so you choose what you want to publish or not.

  • Users can interact with individual Actions : typically when delegating restricted administration actions to 3rd party users.

  • Actions can also be grouped together to represent a global operation : typically used by administrator.
    Hence this sole handy configuration file, garantees one application configuration contract for one environment (manageable for on fly backups/restores).

  • Actions can be self extracted/generated from your own existing software configuration.

  • Kikonf is directed ato what we do and what we need handling bunches of J2EE Applications in critical industrialized environments.

(*) Kikonf currently supports configurations for the following Software :
  • was : Support for WebSphere Application Server
  • wls : Support for WebLogic Server
  • tom : Support for Apache Tomcat
  • jbs : Support for JBoss
  • wmq : Support for WebSphere MQ
  • oss : Support for OpenSSL
  • jss : Support for Java Keytool
  • gsk : Support for GSKit

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 registred trademarks of International Business Machines Corporation.
  • "WebLogic Server" and "Java" are registred trademarks of Oracle and/or its affiliates.
  • "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