Configuring Apache 1.3 to work with WebSphere 5 (Express)

I am trying to get my apache server to forward requests to websphere.  I have looked at all the config manuals/faqs and havn't come across this problem.

Environment:
Redhat Linux 7.3
Apache 1.3
WebSphere Express 5

I have done the following.

1.  Create a virtual host in websphere that listens on *:8082
2.  Installed my application in the websphere instance and assigned the *:8082 virtual host to all the modules
3.  Regenerate my websphere plugin
4.  Added these lines to my httpd.conf:
        LoadModule app_server_http_module /opt/IBM/WebSphere/Express502/Plugins/bin/mod_app_server_http_eapi.so
        WebSpherePluginConfig /opt/IBM/WebSphere/Express502/AppServer/config/cells/plugin-cfg.xml


Now when I start apache I get the following in the error_log:

[Mon Nov 10 15:29:10 2003] [notice] Initializing the WebSphere Plugin



The server never starts up and I cannot find an error message telling me what could be wrong.  I changed the LogLevel to 'debug' in the http conf and that doesn't see to add anything at all.

Please help me hunt down/solve this error.  Any and all help is much appreciated
Jim_McLeanAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kalosiCommented:
try to run this command

Linux:
strace -f /etc/init.d/apache start (or watherver start script are you using).

I don't know your OS, the strace command prints system calls the binary executes. This way we could gather usefull information.

Send please the last lines of the output, we should see the syscall that hangs and we can work further on that problem.

david
Jim_McLeanAuthor Commented:
I figured out my problem...  I only had 1 HTTP transport defined and this was used by the adminconsole virtual host.  I created an spare HTTP transport that wasn't used in any WAS virtual hosts and regenerated my plugin.  WAS now has a HTTP transport to communicate with Apache and it works fine now.  I wish IBM would have spelled out this a bit better in their documentation, but it works now.
Computer101Commented:
PAQed, with points refunded (500)

Computer101
E-E Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
skrraoCommented:
hi i am having the same problem, I have apache listening at port 8082 and I also have web sphere transport setup for 8082. The plugins are installed and I also updated plugin-cfg file. But still I cannot get apache to start. It does give any error message in the errlogs as well. I am not knowing how to proceed now.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Web Components

From novice to tech pro — start learning today.