Informix

 View Only
  • 1.  Starting up InformixHQ

    Posted Tue December 05, 2023 11:48 PM

    Hi Family.

    In my usual concise manner (ahem!) I am asking for assistance.  Yes, I have the Starting the InformixHQ Server page open.

    I started to watch the video on how to start up InformixHQ but it was so blurry and muffled as to be effectively useless; I gave up about 5 minutes in.  However, I did manage to get the section on setting the password in informixhq-server.properties and set the password.  Since I could not make out how the narrator was starting java, I tried to use the script:

    informix@maxwell2l:/ifmx/ids.14.10.FC10/hq$ ./InformixHQ.ksh startserver
    WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.

    INFO: Please use list command to verify the process.

    Dec 05, 2023 7:04:31 PM org.glassfish.jersey.server.wadl.WadlFeature configure
    WARNING: JAXBContext implementation could not be found. WADL feature is disabled.

    UGH!  However, I do see that there is a Java server running: ps -e turned up:

    java -Dfile.encoding=utf-8 -jar informixhq-server.jar informixhq-server.properties

    So the server is running, FWIW.  Well, at least now I know what the narrator was typing in.  If all had worked out I would have been shown a port number and been able to access stuff via a browser.  (And yes, I have my server running.)

    What am I missing?  Let's see, I'm running IDS 14.10.FC10DE. As for Java:

    $ java --version
    openjdk 11.0.21 2023-10-17
    OpenJDK Runtime Environment (build 11.0.21+9-post-Ubuntu-0ubuntu122.04)
    OpenJDK 64-Bit Server VM (build 11.0.21+9-post-Ubuntu-0ubuntu122.04, mixed mode, sharing)

    So I think I'm in compliance well ahead of the Java requirement.

    So what am I missing? (Besides the screws everyone just silently responded ;-)

    OK, the log for this attempt starts at line 9.  I am pasting it here with the line numbers in the hope that it will mitigate the confusion caused by line-wrapping.

     9 2023-12-05 18:58:10 [main] INFO  com.informix.hq.server.JettyServer - Starting InformixHQ Server, version 2.3.1 (build number: 708, build date: 2023-03-07T13:32:27-0600)
     10 2023-12-05 18:58:10 [main] INFO  com.informix.hq.server.JettyServer - Reading properties file informixhq-server.properties
     11 2023-12-05 18:58:10 [main] INFO  com.informix.hq.server.JettyServer - InformixHQ configuration: {rest.session.timeout=3600000, alert.startNumberAlertSendThreads=4, alert.    scheduleConditionCheckInPast=false, hostname=, user.password.maxAge=0, user.password.requireNumber=true, user.password.requireLowerCase=true, httpPort=8080, user.password    .minLength=8, h2.encrypt.enable=false, user.password.requireUpperCase=true, initialAdminPassword=********, dataSource.IFX_ISOLATION_LEVEL=1, pool.connectionTimeout=5000,     httpsPort=-1, user.password.requireSpecialCharacterFromSet=, pool.minimumIdle=0, user.password.algorithm=SHA-256, redirectHTTPtoHTTPS=false, alert.email.debug=false, pool    .idleTimeout=60000, informix.connections.loadFile=, h2.encrypt.algorithm=AES, alert.numberConditionCheckThreads=4, pool.maximumPoolSize=3}
     12 2023-12-05 18:58:10 [main] INFO  com.informix.hq.server.h2.H2Schema - H2 schema version 33
     13 2023-12-05 18:58:10 [main] ERROR com.informix.hq.server.JettyServer - There are no users in the system. Attempt to create the initial admin user failed.
     14 2023-12-05 18:58:10 [main] ERROR com.informix.hq.server.JettyServer - The initial admin password is not a valid password. Password must be at least 8 characters and must     contain at least one lowercase character, one uppercase character, and one number.
     15 2023-12-05 19:04:29 [main] INFO  com.informix.hq.server.JettyServer - Starting InformixHQ Server, version 2.3.1 (build number: 708, build date: 2023-03-07T13:32:27-0600)
     16 2023-12-05 19:04:29 [main] INFO  com.informix.hq.server.JettyServer - Reading properties file informixhq-server.properties
     17 2023-12-05 19:04:29 [main] INFO  com.informix.hq.server.JettyServer - InformixHQ configuration: {rest.session.timeout=3600000, alert.startNumberAlertSendThreads=4, alert.    scheduleConditionCheckInPast=false, hostname=, user.password.maxAge=0, user.password.requireNumber=true, user.password.requireLowerCase=true, httpPort=8080, user.password    .minLength=8, h2.encrypt.enable=false, user.password.requireUpperCase=true, initialAdminPassword=********, dataSource.IFX_ISOLATION_LEVEL=1, pool.connectionTimeout=5000,     httpsPort=-1, user.password.requireSpecialCharacterFromSet=, pool.minimumIdle=0, user.password.algorithm=SHA-256, redirectHTTPtoHTTPS=false, alert.email.debug=false, pool    .idleTimeout=60000, informix.connections.loadFile=, h2.encrypt.algorithm=AES, alert.numberConditionCheckThreads=4, pool.maximumPoolSize=3}
     18 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.h2.H2Schema - H2 schema version 33
     19 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.JettyServer - Initial admin user created
     20 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.h2.H2AlertingIncidentsCache - Loaded 0 incidents from H2
     21 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.JettyServer - Loading package /package-builtin-sensors.json ...
     22 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.JettyServer - Loaded 30 sensors from package /package-builtin-sensors.json
     23 2023-12-05 19:04:30 [main] INFO  com.informix.hq.server.JettyServer - Loading package /package-builtin-reports.json ...
     24 2023-12-05 19:04:31 [main] INFO  com.informix.hq.server.JettyServer - Loaded 3 system reports from package /package-builtin-reports.json
     25 2023-12-05 19:04:31 [main] INFO  org.eclipse.jetty.util.log - Logging initialized @1393ms to org.eclipse.jetty.util.log.Slf4jLog
     26 2023-12-05 19:04:31 [main] INFO  com.informix.hq.server.JettyServer - Serving UI from JAR...
     27 2023-12-05 19:04:31 [main] INFO  com.informix.hq.server.JettyServer - Configuring server for HTTP on port 8080
     28 2023-12-05 19:04:31 [main] INFO  org.eclipse.jetty.server.Server - jetty-9.4.48.v20220622; built: 2022-06-21T20:42:25.880Z; git: 6b67c5719d1f4371b33655ff2d047d24e171e49a;     jvm 11.0.20.1+1-post-Ubuntu-0ubuntu122.04
     29 2023-12-05 19:04:31 [main] INFO  org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@4f94e148{/,jar:file:/home/ifmx-stuff/ids.14.10.FC    10/hq/informixhq-server.jar!/webapp/,AVAILABLE}
     30 2023-12-05 19:04:31 [main] INFO  org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@14bae047{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
     31 2023-12-05 19:04:31 [main] INFO  org.eclipse.jetty.server.Server - Started @2254ms
     32 2023-12-05 19:04:31 [main] INFO  com.informix.hq.server.jobs.RepositoryDataCleanupManager - Next runtime for data cleanup: 2023-12-06 00:00:00
     33 2023-12-05 19:04:31 [main] INFO  com.informix.hq.server.JettyServer - InformixHQ Server is started, up and running
    ~                                                                                                                          

    GADZOOKS! This is as incomprehensible as my Differential Geometry textbook!  Sorry about that.  But the "Add Attachment" does not seem to work in this Linux environment. (Maybe in Windows but that's no help.)

    Still, I do see some port info, though not something I can identify as a URL.

    Thanks for any diagnosis of what I'm missing.



    ------------------------------
    Jacob Salomon
    ---
    Nobody goes there anymore, it's too crowded.  --Attr: Yogi Berra
    ------------------------------


  • 2.  RE: Starting up InformixHQ

    Posted Wed December 06, 2023 12:43 AM
    Edited by Hedwig Fuchs Wed December 06, 2023 12:55 AM

    1) this HQ Version works with Java 11, But the supported version is still Java 8. Java 11 is throwing messages.
    HQ itself is working. The messages do not mean anything. Full support for Java 11 will come with HQ 3.0 (which will come with 14.10.FC11) 

    2) IBM FixCentral has a new HQ 2.3.4 which I recommend to use

    3) setup and start
    "InformixHQ Server is started, up and running" is the critical message.

    In $INFORMIXDIR/hq/informixhq-server-example.properties you can see what you can set up for HQServer,
    A must is:
    initialAdminPassword=mypassword
    this line can be deleted later, is only needed for the first start. But you should not forget it. 


    httpPort=12345
    Is the port which is used by HQServer

    The URL for the HQ user interface looks like: 

    http://xx.xx.xx.xx:12345/dashboard/groups/0

    start the HQServer with
    InformixHQ.ksh startserver propfile=<name of you properties file>



    ------------------------------
    Hedwig Fuchs
    ------------------------------



  • 3.  RE: Starting up InformixHQ

    Posted Wed December 06, 2023 11:26 AM

    Thank you, Hedwig.

    At the risk of displaying ignorance, I have to request a few points to be clarified.  It's a good bet I won't be the only beneficiary.

    • Java 11 is throwing messages. ... The messages do not mean anything.

    That's a lotta scary-looking text but I get the idea.  Until I get the next IDS release I'll have to put up with the scary messages. <Sad face>

    • IBM FixCentral has a new HQ 2.3.4 which I recommend to use

    From the log file I see I have HQ 2.3.1.  Rather than playing "Where's Waldo" on IBM's download site, please provide a URL where I can download  release 2.3.4.  Also, if I might hazard a minor feature request, howzabout a --version option to InformixHQ.ksh?

    • httpPort=12345  # Is the port which is used by HQServer

    The 12345 tells me you were just giving an example. In the two instances of httpPort showing up in the log file, the setting is httpPort=8080.

    • http://xx.xx.xx.xx:12345/dashboard/groups/0

    As with the port number 12345, the xx.xx stuff is obviously a template for the URL.  In my case the port number would, of course, be 8080, not the shown 12345.   But I need actual values for the xx items in this example.  I see nothing in the log that I could interpret as a URL.  What's supposed to go in there?  And I might hazard another feature request: In both the terminal output and the log, just tell me the blessed URL

    Again, Hedwig, thanks for the assurance that the messages are only scary, not a sign of danger.



    ------------------------------
    Jacob Salomon
    ---
    Nobody goes there anymore, it's too crowded.  --Attr: Yogi Berra
    ------------------------------



  • 4.  RE: Starting up InformixHQ

    IBM Champion
    Posted Wed December 06, 2023 11:37 AM

    Jacob:

    You posted:

    The 12345 tells me you were just giving an example. In the two instances of httpPort showing up in the log file, the setting is httpPort=8080.

    As with the port number 12345, the xx.xx stuff is obviously a template for the URL.  In my case the port number would, of course, be 8080, not the shown 12345.   But I need actual values for the xx items in this example. 

    The xx.xx.xx.xx would be your local host address since that is where the HQ service is running.

    In my case it would be http://10.0.0.23:8080

    Art



    ------------------------------
    Art S. Kagel, President and Principal Consultant
    ASK Database Management Corp.
    www.askdbmgt.com
    ------------------------------



  • 5.  RE: Starting up InformixHQ

    Posted Wed December 06, 2023 05:07 PM

    Take the path of least resistance my friend.  If IHQ wants Java 8, use Java 8.

    Ubuntu has a package:
    # apt-get install openjdk-8-jdk
    --OR--
    # apt-get install openjdk-8-jre

    You should be able to install multiple versions.
    Just set JAVA_HOME to point to the version your app needs,
    and add JAVA_HOME/bin to your PATH.

    So in the case of IHQ, if you start it as the 'informix' user,
    you would set in the informix user's environment:

    ....................cut here....................
    JAVA_HOME=/path/to/jdk_or_jre
    export JAVA_HOME
    PATH=$INFORMIXDIR/bin:$JAVA_HOME/jre/bin:$PATH
    export PATH
    ....................cut here....................

    Done!




  • 6.  RE: Starting up InformixHQ

    Posted Thu December 07, 2023 04:09 PM

    Hi Scott & family.

    I was able to get the sign-in screen by browsing to maxwell2l:8080 and sign in with username "admin" and the password I had set in the properties file. (Remember, I only have HQ 2.3.1, not 2.3.4)  This, without setting JAVA_HOME.  I'll leave myself with Java-11 and put up with the noisy messages until I can download the next release.  I am having password problems setting up the monitoring but I'll post about that in a separate thread.  (This thread is getting too long.)

    What I do want to clarify is exactly what JAVA_HOME should be set to, as per your suggestion.  Although it seems to have worked w/o that env variable, I suspect (incorrectly, perhaps) that things would work more smoothly if it were indeed set.  Now, Based on what I found in a stackoverflow post, I would set:

    export JAVA_HOME=/usr/lib/jvm/java-1.11.0-openjdk-amd64

    Is this correct?  This directory contains a few important-looking subdirs, like a lib directory holding a gazillion .so libraries. and jmod, holding many .jmod modules.  So it looks like a good candidate.

    Thank you, all who have responded.



    ------------------------------
    Jacob Salomon
    ---
    Nobody goes there anymore, it's too crowded.  --Attr: Yogi Berra
    ------------------------------



  • 7.  RE: Starting up InformixHQ

    Posted Thu December 07, 2023 05:41 PM

    Jacob,

    I think the reason things work without setting JAVA_HOME is that 
    Informix includes its own JRE.  It is installed under
    $INFORMIXDIR/extend/krakatoa/jre.  That directory gets added to
    the informix user's PATH.  Check $INFORMIXDIR/${INFORMIXSERVER}.ksh
    which is created when you first installed Informix.  The informix user 
    should be sourcing that file to set up the environment properly.  
    The InformixHQ.ksh script just uses the first version of 'java' it finds.

    Try `which java` to see what version of java the informix user is using.
    The Ubuntu package probably created a symlink in /usr/bin (to the real 
    installed java location) for the Java 11 version.  If /usr/bin appears 
    *BEFORE* $INFORMIXDIR/extend/krakatoa/jre/bin in the informix user's PATH, 
    that would explain the Java 11 errors you are seeing.

    Historically, to prevent "wrong JRE issues", most apps including Informix, 
    shipped with their own JRE.  This is why you have tons of versions of the 
    JRE installed on your system.  Informix 14.10 ships an older version of the
    IBM JRE for Java 8.  I seem to recall reading that newer Informix versions 
    were not going to ship with a JRE anymore.  The user will have to install
    their own JRE and then point informix to use that version.  This makes 
    more sense, you have fewer JREs installed, and when you need to do a 
    JRE security update, you do it in one place and all java apps benefit.

    If things work OK without setting JAVA_HOME, I wouldn't change anything.
    The main reason to set JAVA_HOME is to specify the specific version of 
    java you want to use.  If you do set JAVA_HOME, make sure to add 
    $JAVA_HOME/bin to your PATH ahead of any other versions of where java 
    might be installed on your system.

    As for what to set JAVA_HOME to, that depends on where java is installed
    on your system.  On a Debian system with openjdk-11-jdk installed, I see 
    /usr/lib/jvm/java-11-openjdk-amd64/bin/java, so you would set:

    JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
    export JAVA_HOME 
    PATH=$JAVA_HOME/bin:$PATH
    export PATH

    Try "dpkg -L openjdk-11-jre" to list the files Ubuntu installed on your system.

    scot