× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Bryce,

You have several options. First, you do not need another NIC as a single NIC on IBM i can support mulitple IP's. That is one of the easiest approaches as that keep you out of the reverse proxy configs on Zend Core.

Another approach is to add the reverse proxy configs from the Zend Core Apache server to your WAS instance. This can be done, but is not easy and IBM can support you on this as this is both their servers.

Upgrade to Zend Server (no charge) and you go from two to one Apache server with no reverse proxy non-sense. Might be a more attractive method if consolidating the directives in a single Apache.



Regards,

Mike

mike.p@xxxxxxxx Cell: (408)679-1011 Office: (630)928-1476

Zend Server for IBM i avilable at http://www.zend.com/en/products/server/zend-server-5-new-ibmi


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Bryce Martin
Sent: Thursday, October 14, 2010 10:26 AM
To: web400@xxxxxxxxxxxx
Subject: [WEB400] Handling requests Websphere application server and php zendcore running on same machine.

Hello All,
We have an outward facing machine in our DMZ that has WAS and ZendCore
running. To access the WAS applications we have DNS for
http://webapps.ourdomain.com. For the PHP apps they go to
http://webapps.ourdomain.com:89.

This works fine internally. But externally port 89 is being blocked. It
appears to be the ISP blocking 89, but I wouldn't put it past our own
gurus. They sent us the firewall entry for our address and it looks wide
open, so I will give them the benefit of the doubt for now.

My quest goes beyond the network guys because I'm wondering if we can
handle this internally. How do you guys handle this situtation? We don't
have a spare NIC interface to tie the PHP server to, so that option is
out.

The problem is that a webpage that is served from the WAS is sent to the
client. On that page is a link to webapps.ourdomain.com:89/createpdf.php.
We need to return that pdf back tot he client but port 89 is being
blocked. My workaround was to move it to port 443 and set up ssl. Then
the link could go to https://webapps.ourdomain.com/createpdf.php and no
one would be blocking 443.

I toyed with the idea of a revers proxy server to handle the requests so
that we can keep the php server on port 89. I'm just not sure which path
would be best so I'd like to see how other people would do it.


Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777
--- This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us and destroy this message immediately. ---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.