Versionen im Vergleich

Schlüssel

  • Diese Zeile wurde hinzugefügt.
  • Diese Zeile wurde entfernt.
  • Formatierung wurde geändert.

...

You can have different UM Rest Proxy instances on different web servers, e.g. Intranet vs. Internet or different domains/tenants which all use different interfaces on the UM backend.

Typical configuration

Assuming you have the following setup:

  1. Outmost web server for www.yourwebsite.com on server A, running on https port 443

  2. Apache Tomcat with UM REST Proxy on same server A running on port 8080

  3. Apache Tomcat with Universal Messenger on server B running on port 8080

Outmost web server → UM REST Proxy on local Tomcat

On your outmost web server or load balancer which handles your website under www.yourwebsite.com add a Reverse Proxy configuration to handle all requests to /p/…

...

Codeblock
<Location /p/>
    SetEnv proxy-initial-not-pooled 1
    ProxyPass "http://your_restproxy_tomcat:12345localhost:8080/p/"
    ProxyPassReverse "http://your_restproxy_tomcat:12345localhost:8080/p/"
    RequestHeader set x-cmsbs-urlprefix "https://www.yourwebsite.com/p"
    RequestHeader unset x-cmsbs-restproxy-path 
    RequestHeader unset x-forwarded-host 
</Location>

UM REST Proxy on local Tomcat → Universal Messenger on server B

Assuming the UM REST Proxy will be deployed as /p on Tomcat the context file would look like this:

Codeblock
<Context path="/p" docBase="/opt/UM/cmsbs-restproxy.war">
    <Parameter name="cmsbs.resturl" value="http://server-b:8080/cmsbs/rest" />
...
</Context> 
Info

More configuration options including whitelist configuration: https://www.universal-messenger.de/knowledge-base/intern/doc-en/Administration/REST_proxy_configuration.html