Apache config from PWS to Web Gateway

Question

Question

Scott Roth · Oct 26, 2023

#Web Gateway #Health Connect #InterSystems IRIS #InterSystems IRIS for Health

This is probably not the right place, but I don't know who I can reach out to... I am trying to configure an Apache/Web Gateway to our instance of IRIS so we are no longer using the built-in PWS. Can anyone point me in the right direction to configure Apache/Web Gateway to repoint

http://<server name>:52773/... to the https://<server name>/...

gateway so our users will not notice? How do I do this in Apache, do I need to modify httpd.conf or the ssl.conf file? What is the correct syntax...

This is what I tried to do in the httpd.conf file

<VirtualHost *:52773>
    ServerName int-lxiris-vd01.osumc.edu
    ServerAlias int-lxiris-vd01 int-lxiris-vd01.unix.osumc.edu
    Redirect permanent / https://int-lxiris-vd01.osumc.edu/
</VirtualHost>

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

Thanks

Scott Roth

Product version: IRIS 2023.1

Discussion (7)2

Log in or sign up to continue

Luis Angel Pére... · Oct 27, 2023

Maybe this article is helpful. is based on this document for LINUX and this other for Windows.

0 0

score 0 · Answer 1 · 2023-10-27T08:33:19-04:00

Scott Roth · Oct 27, 2023

Thanks, but I have already went through all of those steps.

0 0

score 0 · Answer 2 · 2023-11-09T02:14:21-05:00

Not sure if I understand where you are stuck. Looks like you are trying to proxy the PWS instead of avoiding it.
What the webgateway does and what intersystems recommends is using the webgateway which does not connect to the PWS on IRIS but to the superserver-port (default: port 1972).
The general configuration of the connection between Webgateway and IRIS is done via web-based management-interface of the webgateway. The articles Luis Angel is referring to include the configuration of which sorts or requests are linked to the Webgateway and forwarded to Iris (via superserver-port).
Hope this will help....

score 0 · Answer 3 · 2023-11-09T07:31:07-05:00

Since everyone on the team uses the URL that contains the port number of 52773, I was trying to make it possible for them not to have to update their bookmarks they already use. Seamless transition to encrypting the traffic between their web browser and the server.

score 0 · Answer 4 · 2023-11-09T08:13:49-05:00

The requests using port 52773 aren't even going to get to Apache, so you can't solve this problem by changing your Apache configuration. You would have to make your router forward traffic between your server and your other PCs on port 52773 to port 80 (for HTTP) or port 443 (HTTPS).

score 0 · Answer 5 · 2023-11-09T08:16:22-05:00

It is possible to setup Apache to listen for 52773 instead of 80, so why wouldn't calls to port 52773 go through Apache if it is configured to listen for port 52773?

score 0 · Answer 6 · 2023-11-09T08:18:24-05:00

My mistake, Scott, I thought you just had Apache running on its default ports and were trying to figure out how to make the other requests also go there.