Skip to main content

Setting up Novell User Application RBpM on Windows Server 2008 R2 as Windows Service

.. Gotcha.. the everything finally is up and running , now i have following things running in my enviornment.


1. Windows Server 2008 R2 (64-bit)
2. Novell Identity Manager 4.0.1
3. Novell User Application (RBpM) Modules / Jboss/ MySQL Community Edition 5.5
4. Novell User Application (Identity Reporting Module) Module
5. Novell EAS (Event Auditing Serivce) Suse Linux postGreSQL..

I wanted to setup the auto start of Jboss on the Windows Server 2008 R2 as Window Service and I ended up with the following setup:


Added %JBOSS_HOME% and %JAVA_HOME% as the System env variables. I had to stick to the JDK 1.6 /JRE x86 versions due to IDM reporting modules.


Good start wiht Option2 ( Use the JavaServiceWrapper by Tanuki.)
link# http://community.jboss.org/wiki/RunJBossAsAServiceOnWindows


and my wrapper.conf
===============================

wrapper.java.command=C:/Program Files (x86)/Java/jdk1.6.0_26/jre/bin/java

wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp

wrapper.java.classpath.1=%JBOSS_HOME%/lib/wrapper.jar
wrapper.java.classpath.2=C:/Program Files (x86)/Java/jdk1.6.0_26/jre/lib/tools.jar
wrapper.java.classpath.3=%JBOSS_HOME%/bin/run.jar
wrapper.java.classpath.4=%JBOSS_HOME%/lib/endorsed/xalan.jar

wrapper.java.library.path.1=%JBOSS_HOME%/lib

# these are the JAVA_OPTS
wrapper.java.additional.1=-server

# enviroment variables - define the ones that match your desired environment
wrapper.java.additional.1=-Dfile.encoding=UTF-8
wrapper.java.additional.2=-Dsun.jnu.encoding=UTF-8

# memory parameters - define the ones that match your desired environment
wrapper.java.additional.3=-XX:MaxPermSize=512m
wrapper.java.initmemory=512
wrapper.java.maxmemory=512


wrapper.app.parameter.1=org.jboss.Main
wrapper.app.parameter.2=-Djboss.service.binding.set=ports-01
wrapper.app.parameter.3=-c IDM -b 0.0.0.0

wrapper.logfile=%JBOSS_HOME%/server/IDM/log/wrapper-ROLLNUM.log
wrapper.logfile.rollmode=SIZE
wrapper.logfile.maxsize=10m

wrapper.ntservice.name=NovellUserAppJboss
wrapper.ntservice.displayname=NovellUserAppJboss

===============================


The windows service is running under Local System Account!

Comments

Popular posts from this blog

Experience writing a Java based DirXML Driver

Based on the customer project, I wrote a DirXML driver which provision users through Novell Identity Manager 3.5.1 to their company intranet portal ( A Plone System). The portal exposed the RESTful API interfaces. So I started looking first at the Novell SOAP driver to see if it fit our needs. But while reading the driver documentation i felt it required too much XSLT knowledge + more customization and testing on the driver. And again it used the Apache HttpClient, Which is more a HttpClient rather then it targets to any specific protocol implementation. So If you could build SOAP messages at your own so it would help you in transporting these message back and forth between IDM and Application. The Novell SOAP driver comes up with two built in configurations "SPML and DSML", but in my case none of them were suitable. I had always wished to write my own DirXML driver at my own, so I thought why not just take this opportunity to fulfill my wish and at the same time get s...

NetIQ IDM - JDBC statemens using policy builder

Few examples of using JDBC statements using dirxml policies On the Output policy: Handling matching policies with operation-data support: < rule > < description > [DB] Convert Query to DDL doc </ description > < comment name = "author" xml:space = "preserve" > Maqsood Ali Bhatti </ comment > < comment name = "version" xml:space = "preserve" > 5 </ comment > < comment name = "lastchanged" xml:space = "preserve" > Dec 20, 2017 </ comment > < conditions > < and > < if-operation mode = "case" op = "equal" > query </ if-operation > </ and > </ conditions > < actions > < do-append-xml-element expression = ".." name = "jdbc:statement" /> < do-append-xml-element expression = "../jdbc:statement[las...

Novell IdM 3.6 : Creating custom Subscriber PostProcessor Java extension for Delimited Text Driver Part 1

I had chance to write a custom PostProcessor extension for a Delimited Text Driver for Novell Identity Manager,  " t he PostProcessor extension should execute the code under another Windows Domain User account. So I decided to run the driver with Remote Loader Configuration, running the DirXML windows Service under another Windows Domain User Account. " Software and settings in my setup: * Novell Designer 3.0.1 (build  Jan 5, 2009) * Novell Identity Manager 3.6 / Windows Server 2003 R2 * Novell iManager 2.7.2 * Delimited Text Driver 3.6 ver 2.0 (imported configuration  file from Designer 3.0.1) * And the Delimited Text Driver was going to run on the remote server (Remote Loader),  * Java IDE was  (IntelliJIDEA) i started first with digging into documentation of the driver, and i came a cross this section: Using Java Interfaces to Customize File Processing: http://www.novell.com/documentation/idm36drivers/delimited/index.html?page=/documentation/idm36drivers/delimited/data/bkt...