WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Wed April 24, 2019 02:18 PM
    Edited by Alex Pennie Wed May 08, 2019 09:57 AM
    Hi all,

    Thanks so much for attending our session! We had some great questions asked during the webcast, if there are any remaining questions please add them here!

    ------------------------------
    Alasdair Nottingham
    IBM
    ------------------------------


  • 2.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Tue April 30, 2019 01:04 PM
    When I did the first development lab and configured security, it automatically created a p12 type certificate.  What is the keystore password?

    ------------------------------
    George Weaver
    IBM
    ------------------------------

    Original Message


  • 3.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Tue April 30, 2019 11:08 PM

    In the server directory there is a server.env file. In that server.env file there will be a line that has keystore_password=<some random string> the value after the = is the password. This gets generated when you run server create.

    If you look in the console.log you should see this message:

        [AUDIT ] CWPKI0820A: The default keystore has been created using the 'keystore_password' environment variable.

    which indicates this.



    ------------------------------
    Alasdair Nottingham
    IBM
    ------------------------------

    Original Message


  • 4.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Thu May 09, 2019 09:20 AM
    I am facing a class loader issue in 19.0.0.1 core : My JAAS and Application JAR's are loading by two different class loaders. Kindly advice how can i resolve. Below are my config in server.xml :

    <application id="Sample" location="/home0/was9/wlp/shahu/App.ear" name="Sha" type="ear" context-root="Sam" autoStart="true"><application id="BANCS" location="/home0/was9/wlp/shahu/App.ear" name="Sha" type="ear" autoStart="true">
    <classloader commonLibraryRef="Lib"/> </application>

    <library id="Lib"> <fileset dir="/home0/was9/wlp/usr/servers/shahu/apps/expanded/Sha.ear/APP-INF/lib" includes="*.*" scanInterval="5s"/> </library>

    <jaasLoginModule id="BFS" className="com.XXXX.LoginModule" controlFlag="REQUIRED" libraryRef="Lib"/>

    <jaasLoginContextEntry name="system.WEB_INBOUND" id="system.WEB_INBOUND"
    loginModuleRef="myCustom, hashtable, userNameAndPassword, certificate, token" />

    I kept my jaas.config and Login module JAR at /home0/was9/wlp/usr/servers/shahu/resources/security/jaas

    ------------------------------
    SHAHUL SHAIK
    ------------------------------

    Original Message


  • 5.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Thu May 09, 2019 11:23 AM
    Hi Alasdair,

    Is there any way to suppress the creation of messages.log? Running Liberty apps in a container I'd like to stream all logging to stdout/stderr

    With these entries in bootstrap.properties

    com.ibm.ws.logging.console.format=json

    com.ibm.ws.logging.console.log.level=info

    com.ibm.ws.logging.console.source=message,trace,accessLog,ffdc,audit

    and this in server.xml

     

    <logging maxFileSize="1" maxFiles="1"/>

     

    I should only see a 1MB messages.log

     

    In a VPOT last year it was suggested that com.ibm.ws.logging.message.file.name could be set to stdout but that causes the logging to go to a file called 'stdout.' traceFileName does allow stadout



    ------------------------------
    Joe Broz
    ------------------------------

    Original Message


  • 6.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Thu May 09, 2019 06:12 PM
    Add these lines to your bootstrap.properties

    com.ibm.ws.logging.message.format=json​
com.ibm.ws.logging.message.source=
    The first line says format messages.log as json. The second line says don't sent any loggable events to the messages.log. The net effect is no messages.log.

    This works for me on my systems and I spoke to our observability architect and while it wasn't originally intended to work we've agreed that it is a logical consequence of the external so we are going to add a regression test to make sure this continues to work.

    ------------------------------
    Alasdair Nottingham
    IBM
    ------------------------------

    Original Message


  • 7.  RE: Post event questions for WebSphere Liberty 19.0.0.1,2,3 Technical Overview, Update, and Q&A (Session 1 & 2)

    Posted Sun May 12, 2019 11:33 AM
    The other thing that you can do, if you want, is to avoid having a trace.log file if you are sending your trace to console as well.  So, to have no messages.log, no trace.log, and have both messages and trace go to console in JSON format, use the following in your bootstrap.properties:

                    com.ibm.ws.logging.trace.file.name=stdout
                    com.ibm.ws.logging.message.source=
                    com.ibm.ws.logging.message.format=json
                    com.ibm.ws.logging.console.source=message,trace
                    com.ibm.ws.logging.console.format=json

    Don




    Original Message


Related Content