Administrative Console in the IBM WebSphere Liberty Profile running on Raspberry Pi


Skill Level: Any Skill Level

Here you will learn step-by-step on how to install and configure the Administrative Console in the IBM WebSphere Liberty Profile.


Download the IBM WebSphere Liberty Profile

Operational System can be IBM AIX, other Unix-like, Windows or z/OS.


  1. Extract the IBM WebSphere Liberty Profile

    After to download the IBM WebSphere Liberty Profile, so-called WLP, from IBM’s site, just extract to some folder.

    You must not have root’s privilege to run the WLP.


    $ unzip
  2. Create an encrypted password for keyStore’s certificate

    This password is used by WLP in order to load the certificate over HTTPS instance. It is a must have for Administrative Console.

    The tool securityUtility is going to be used, with the parameter encode and –encoding=aes. At this time, AES cryptography is used.


    $ wlp/bin/securityUtility encode --encoding=aes igormonteirovieiraaa
    Result: "{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA=="
  3. Installing the adminCenter-1.0, an Administrative Console for IBMe WebSphere Liberty Profile

    The IBM WebSphere Liberty Profile comes with less features installed as possible, in order to be the most lightweight and secure Application Server in the market and for administrative’s purposes.

    In order to get Administrative Console, the correspondent package is adminCenter and must be installed through the following way:


    $ wlp/bin/installUtility install adminCenter-1.0
  4. Creating the server.xml for IBM WebSphere Liberty Profile

    At this time, the previous libraries were added to the filesystem and the WLP’s server.xml is bound to be created. A start is required to get these settings valid.


    $ wlp/bin/server start


    After this start, the server.xml was created underneath wlp/usr/servers/defaultServer/.

  5. Loading the Administrative Console

    Everytime either a module, library or plugin is installed through installUtility application, it must be pointed into server.xml.

    As best practice, better to stop the WLP before changing these parameters.


    $ wlp/bin/server stop


    To include the new features in the server.xml:


    $ vi wlp/usr/servers/defaultServer/server.xml




    <basicRegistry id="basic">
     <user name="admin" password="admin"/>
     <user name="nonadmin" password="nonadmin"/>
    <keyStore id="defaultKeyStore" password="{aes}ALdLTXUQf7HvUNqRxxFT4yDSMGMUw6Oe5TcawHZAK8LRGNlivTITq3km/Mc82t7EVA==" />
  6. Starting the Administrative Console wlp/bin/server start


    1. installUtility used to install:
      1. adminCenter-1.0
    2. server.xml configured with:
      1. adminCenter-1.0 as feature
      2. ssl-1.0 as feature
      3. administrative-role
      4. basicRegistry
      5. keyStore


    Starting the server:


    $ wlp/bin/server start

    The log is placed underneath wlp/usr/servers/defaultServer/logs/. There are two, console.log and messages.log. In case of error, ffdc will be created as well. Expected console.log:

    $ tail -f wlp/usr/servers/defaultServer/logsconsole.log 
    Launching defaultServer (WebSphere Application Server on Java HotSpot(TM) Client VM, version 1.8.0_65-b17 (en_US)
    [AUDIT ] CWWKE0001I: The server defaultServer has been launched.
    [AUDIT ] CWWKE0100I: This product is licensed for development, and limited production use. The full license terms can be viewed here:
    [AUDIT ] CWWKZ0058I: Monitoring dropins for applications. 
    [AUDIT ] CWWKF0012I: The server installed the following features: [jsp-2.3, ejbLite-3.2, managedBeans-1.0, servlet-3.1, jsf-2.2, beanValidation-1.1, ssl-1.0, jndi-1.0, appSecurity-2.0, jsonp-1.0, jdbc-4.1, jaxrs-2.0, restConnector-1.0, el-3.0, jaxrsClient-2.0, json-1.0, jpaContainer-2.1, adminCenter-1.0, cdi-1.2, distributedMap-1.0, webProfile-7.0, websocket-1.1, jpa-2.1].
    [AUDIT ] CWWKF0011I: The server defaultServer is ready to run a smarter planet.
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWWKT0016I: Web application available (default_host):
    [AUDIT ] CWPKI0803A: SSL certificate created in 31.868 seconds. SSL key file: /home/pi/wlp/usr/servers/defaultServer/resources/security/key.jks


  7. Accessing the Administrative Console of the IBM WebSphere Liberty Profile

    To specific an IP to the URL, the parameter host=”IP” must be inserted in the server.xml at the tag httpEndpoint. The server.xml‘s content must looks like:

     <httpEndpoint id="defaultHttpEndpoint" host=""
     httpsPort="9443" />

    A restart may be required in case of changing this IP.

    Use the URL http://localhost:9080/adminCenter/.

    IBM WebSphere Liberty Profile, Administrative Console


Deixe um comentário

Preencha os seus dados abaixo ou clique em um ícone para log in:

Logotipo do

Você está comentando utilizando sua conta Sair /  Alterar )

Foto do Google+

Você está comentando utilizando sua conta Google+. Sair /  Alterar )

Imagem do Twitter

Você está comentando utilizando sua conta Twitter. Sair /  Alterar )

Foto do Facebook

Você está comentando utilizando sua conta Facebook. Sair /  Alterar )

Conectando a %s