Starting JBOSS and IDM User App Automatically on SLES with JAVA Service Wrapper From Tanuki Software

Starting JBOSS and IDM User App Automatically on SLES with JAVA Service Wrapper From Tanuki Software

1) Pre-requisites

Novell IDM User Application is already installed and starts and stops properly using the original and scripts.

2) Installing Java Wrapper for Tanaki Software

You can download the "community" version for Linux here:

This version is free but does not work on 64Bits OS.

I used the WrappersimpleApp Integration method installation, you can find the documentation here:

The default JBOSS_HOME is /opt/novell/idm/jboss.

  1. Unpack the zip file in a source directory (/opt/wrapper for example)

  2. Copy bin/wrapper from source to JBOSS_HOME/bin

  3. Make it executable : “chmod +x wrapper”

  4. Copy src/bin/ from source to JBOSS_HOME/bin

  5. Rename the script to jboss (for example) and make it executable as well

  6. Then edit the script to reflect the name of the application:Extract of jboss script:
    # Application
    APP_LONG_NAME="JBoss Application Server"

    # Wrapper


  7. Copy the native library lib/ from source to JBOSS_HOME/lib

  8. Copy Jar file lib/wrapper.jar from source to JBOSS_HOME/lib

  9. Create the conf directory JBOSS_HOME/conf

  10. Copy the conf template src/conf/ from source to JBOSS_HOME/conf

  11. And rename it to wrapper.conf

  12. Create the wrapper log directory JBOSS_HOME/logs

3) Configure the Java Service wrapper to start IDMProv apps

Here is the final wrapper.conf configured to start IDMProv:
# Configuration files must begin with a line specifying the encoding
# of the the file.

# Wrapper License Properties (Ignored by Community Edition)
# Professional and Standard Editions of the Wrapper require a valid
# License Key to start. Licenses can be purchased or a trial license
# requested on the following pages:

# Include file problems can be debugged by removing the first '#'
# from the following line:

# The Wrapper will look for either of the following optional files for a
# valid License Key. License Key properties can optionally be included
# directly in this configuration file.
#include ../conf/wrapper-license.conf
#include ../conf/wrapper-license-%WRAPPER_HOST_NAME%.conf

# The following property will output information about which License Key(s)
# are being found, and can aid in resolving any licensing problems.

# Wrapper Localization
# Specify the locale which the Wrapper should use. By default the system
# locale is used.
#wrapper.lang=en_US # en_US or ja_JP

# Specify the location of the Wrapper's language resources. If these are
# missing, the Wrapper will default to the en_US locale.

# Wrapper Java Properties
# Java Application
# Locate the java binary on the system PATH:
# Specify a specific java binary:

# Tell the Wrapper to log the full generated Java command line.

# Java Main class. This class must implement the WrapperListener interface
# or guarantee that the WrapperManager class is initialized. Helper
# classes are provided to do this for you. See the Integration section
# of the documentation for details.

# Java Classpath (include wrapper.jar) Add class path elements as
# needed starting from 1

# Java Library Path (location of Wrapper.DLL or

# Java Bits. On applicable platforms, tells the JVM to run in 32 or 64-bit mode.

# Java Additional Parameters

# Initial Java Heap Size (in MB)

# Maximum Java Heap Size (in MB)

# Application parameters. Add parameters as needed starting from 1

# Wrapper Logging Properties
# Enables Debug output from the Wrapper.
# wrapper.debug=TRUE

# Format of output for the console. (See docs for formats)

# Log Level for console output. (See docs for log levels)

# Log file to use for wrapper output logging.

# Format of output for the log file. (See docs for formats)

# Log Level for log file output. (See docs for log levels)

# Maximum size that the log file will be allowed to grow to before
# the log is rolled. Size is specified in bytes. The default value
# of 0, disables log rolling. May abbreviate with the 'k' (kb) or
# 'm' (mb) suffix. For example: 10m = 10 megabytes.

# Maximum number of rolled log files which will be allowed before old
# files are deleted. The default value of 0 implies no limit.

# Log Level for sys/event log output. (See docs for log levels)

# Wrapper General Properties
# Allow for the use of non-contiguous numbered properties

# Title to use when running as a console
wrapper.console.title=JBoss Application Server

# Wrapper JVM Checks
# Detect DeadLocked Threads in the JVM. (Requires Standard Edition)

# Out Of Memory detection.
# (Simple match)
# (Only match text in stack traces if -XX:+PrintClassHistogram is being used.)
#wrapper.filter.trigger.1000=Exception in thread "*" java.lang.OutOfMemoryError
wrapper.filter.message.1000=The JVM has run out of memory.

# Wrapper Email Notifications. (Requires Professional Edition)
# Common Event Email settings.<SMTP_Host>[%WRAPPER_HOSTNAME%:%WRAPPER_NAME%:%WRAPPER_EVENT_NAME%] Event Notification<Sender email><Recipient email>

# Configure the log attached to event emails.

# Enable specific event emails.

# Specify custom mail content JVM was restarted.\n\nPlease check on its status.\n

# Wrapper Windows NT/2000/XP Service Properties
# WARNING - Do not modify any of these properties when an application
# using this configuration file has been installed as a service.
# Please uninstall the service before modifying this section. The
# service can then be reinstalled.

# Name of the service

# Display name of the service

# Description of the service

# Service dependencies. Add dependencies as needed starting from 1

# Mode in which the service is installed. AUTO_START, DELAY_START or DEMAND_START

# Allow the service to interact with the desktop.

4) Set the JBOSS daemon

Then you can set the jboss script to start automatically using the jboss command line:

“Jboss install”

5) Remarks

  • The "-b" option was not supported and replaced by :"

  • The "-c IDMProv" option was replaced by "-cIDMProv" because the space was not supported

Labels (1)


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
4 of 4
Last update:
‎2020-03-10 19:07
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.