Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Problems starting JBOSS in Aleph 18

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    We are trying to start JBOSS on our Aleph 18 machine, but without success
    (JBOSS is for example used for SMSProxy, RESTful API, SOAP-interface).

    Resolution:
    With help from experts from Ex Libris problem was solved.

    The following steps have been performed:

    1) Check that Java 5 is installed.
    Correct output:
    >> java -version
    java version "1.5.0_10"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03)
    Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode)

    If Java 5 is not installed please follow the instruction in
    ftp://produser:Pr6gue@ftp.exlibris.co.il/product_patches/README.java5

    2) Change of Java-softlink
    OLD:
    /exlibris/aleph/a18_1/product/local/java -> /exlibris/product/j2sdk1.4.2_14/
    NEW:
    /exlibris/aleph/a18_1/product/local/java -> /exlibris/product/jdk1.5.0_10/

    So the link now points to Java 5.

    3) Creating file global.properties in $alephe_root/jboss_conf (in this case JBOSS is running on port 1895 as Copy number is 5 - if copy number is 1 you may use 1891)
    >> cd $alephe_root/jboss_conf
    >> cat global.properties
    server.name=localhost
    http.port=1895
    jndi.port=2895
    rmi.port=3895
    rmi.object.port=3995
    webservice.port=4895
    debug.port=5005
    server.pool.port=6895
    ajp.port=7895

    http.connectiontimeout=20000
    #sdk path
    java.home=/exlibris/aleph/a18_2/product/local/java

    4) Copying file global.properties from $alephe_root/jboss_conf/ to $aleph_dev/ng/aleph/home/profile/
    (File should exist in both directories)
    >>cp $alephe_root/jboss_conf/global.properties $aleph_dev/ng/aleph/home/profile

    5) Creating file main.properties (server address is 120.10.10.9 in this case, Aleph OPAC (Apache) is running on port 80, abc01 is the BIB library of the customer):
    >> cd $alephe_root/jboss_conf
    >> cat main.properties
    xservice.server.name=120.10.10.9
    xservice.server.port=80
    xservice.searchBase=abc01
    xservice.xsl.directory=/exlibris/aleph/u18_2/alephe/jboss_conf/xsl
    xservice.xsl.present2rss=present2rss.xsl

    Please note: if your server has something other than Listen [Port], such as Listen 80 in the above example in httpd.conf, please see KB 30496

    6) In order to activate global.properties and main.properties the following command needs to be performed:
    >> jbin
    >> set_globals.sh

    7) Stop and restart JBOSS:
    >> jbin
    >> ./jboss_shutdown.sh
    >> ./jboss_startup.sh
    Note: In Aleph v18 we recommend to use "jboss_shutdown.sh" and "jboss_startup.sh" to stop/restart JBOSS server instead of UTIL-W.
    There are known problems in UTIL-W in Aleph v18 that are fixed In Aleph v20.

    Now with this command we see JBOSS is running:
    >> ps -ef | grep "/a18_1/product/local/java/bin/java"

    A) Successfull test of SOAP-interface:
    We get an answer when we try to call up for example this WSDL-file:
    http://<server>:<port>/AlephWebServices/services/BorInfo?wsdl

    B) Sucessfull test of DLF-interface (RESTful API):
    >> cd /tmp
    >> wget "http://localhost:1895/rest-dlf/test"
    --11:07:26-- http://localhost:1895/rest-dlf/test
    => `test'
    Resolving localhost... 127.0.0.1
    Connecting to localhost[127.0.0.1]:1895... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: unspecified [application/xml]
    [ <=> ] 61 --.--K/s
    11:07:26 (595.70 KB/s) - `test' saved [61]

    >> more test
    <?xml version = "1.0" encoding = "UTF-8"?><status>OK</status>

    Note: If you still have problems using the RESTful API, please restart Apache server.


    • Article last edited: 10/8/2013