Article

kuronen's picture
article
Reads:

7464

Score:
2.666665
2.7
3
 
Comments:

3

Using iManager 2.7 with Apache

Author Info

31 October 2007 - 8:52am
Submitted by: kuronen

(View Disclaimer)

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.

Environment

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


Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.




User Comments

ch1tsch1's picture

Doesn't work with SUSE 10.1 64-bit & Apache 2

Submitted by ch1tsch1 on 30 January 2008 - 2:24pm.

I tried this on SUSE 10.1 64-bit. It installs Apache2 by default. I tried replacing "httpd" with "apache2" in the commands listed. I get the following errors:

httpd2-prefork: Syntax error on line 177 of /etc/apache2/httpd.conf: Syntax error on line 102 of /etc/apache2/default-server.conf: Syntax error on line 2 of /etc/apache2/conf.d/mod_jk.conf: Cannot load /etc/opt/novell/tomcat5/jk/mod_jk.so into server: /etc/opt/novell/tomcat5/jk/mod_jk.so: wrong ELF class: ELFCLASS32
chi3iweb:/var/opt/novell/tomcat5 # cd ln -s /etc/opt/novell/tomcat5/jk/nps-Apache.conf /etc/

Looks like maybe it's trying to load a 32-bit library when I need a 64-bit? Any ideas?

bartman2000's picture

I couldn't get it to work on SLES 10 SP1.

Submitted by bartman2000 on 10 April 2008 - 5:34am.

I could not get this to work either on SLES 10 SP1 32bit. I ended up using proxy_ajp.

german_garcia_g's picture

mod_jk

Submitted by german_garcia_g on 3 August 2010 - 9:49am.

The problem is the version of mod_jk for 64 bits

i use
http://www.gossipcheck.com/mirrors/apache/tomcat/t...

you can remane to mod_jk.so and whit the command vi /etc/opt/novell/tomcat5/jk/mod_jk.conf change LoadModule jk_module whit the path to the new mod_jk

© 2013 Novell