Unless you are using older versions of Linux, please search for more recent version of this article on Novell Cool Solutions

This tip explains how to use Novell iManager 2.7 with Apache. It applies to Linux RHEL* and can be used with other distributions, with a little extra thought.

With iManager 2.7, default access for Apache and mod_jk has been dropped. In practice, this means you’re going to have to access Tomcat port 8443 directly. So, this means problems for those who connect from behind firewalls and for those who seek maximum security for their identity vaults.

Luckily, the needed configuration files still exist in the installation; they just need a little editing and putting in place for Apache to read.

Here’s what you need to do:

1. Install iManager 2.7 normally.

2. Edit file /etc/opt/novell/tomcat5/jk/mod_jk.conf and replace all ‘tomcat4’ texts with ‘tomcat5’

3. Edit file /etc/opt/novell/tomcat5/jk/nps-Apache.conf and replace all ‘tomcat4’ texts with ‘tomcat5’

Next, you need to place the files so that Apache can use them:

4. Create symbolic links to apache config dir with shell commands:

  ln -s /etc/opt/novell/tomcat5/jk/mod_jk.conf /etc/httpd/conf.d/
  ln -s /etc/opt/novell/tomcat5/jk/nps-Apache.conf /etc/httpd/conf.d/

5. Restart Tomcat with this command: service novell-tomcat5 restart

6. Restart Apache with this command: service httpd restart

7. Make backup copies of the two configuration files so you do not need to repeat the procedure in case of reinstall.


This solution should work with nearly all Linuxes; it has been tested with RHEL4 / Centos4.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

By: kuronen
Oct 31, 2007
9:52 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow