OMi-specific configuration

In addition to configuring the reverse proxy to work with OMi, you must configure OMi to work with the reverse proxy.

Note OMi must be configured only if application users are connected via a reverse proxy to OMi. If the reverse proxy is being used for data collectors only, skip the instructions in this section.

To configure OMi to work with the reverse proxy:

  1. Open Infrastructure Settings:

    Administration > Setup and Maintenance > Infrastructure Settings

    Alternatively, click Infrastructure Settings.

    Click Foundations and select the Platform Administration context from the drop-down box.

  2. In the Platform Administration - Host Configuration pane, verify the following parameters. These parameters are set automatically based on the OMi URL in the Connection Settings page of the OMi configuration wizard.

    • Default Virtual Gateway Server for Application Users URL and Default Virtual Gateway Server for Data Collectors URL. Verify that these parameters represent the URL of the machine (reverse proxy, load balancer, or other type of machine) used to access the gateway server.

      Example: http://my_reverse_proxy.example.com:80

      Local Virtual Gateway Server for Application Users URL and Local Virtual Gateway Server for Data Collectors URL (optional). If you must use more than one URL (the ones defined for the Default Virtual Server URLs, above) to access the gateway server machine, define a Local Server URL for each machine through which you want to access the gateway server machine.

      Example: http://my_specific_virtual_server.example.com:80.

      If the Local Virtual Services Server URL parameter is defined for a specific machine, this URL is used instead of the Default Virtual Services URL for the specifically-defined machine.

    • Direct Gateway Server for Application Users Server URL. Verify that this parameter represents the URL of the gateway server.

    • Direct Gateway Server for Data Collectors URL. Click the Edit button and delete the URL in the value field.

  3. In the Reverse Proxy Configuration pane, set the following parameters:

    • Enable Reverse Proxy. Set this parameter to true.

    • HTTP or HTTPS Reverse Proxy IPs Enter the internal IPs the reverse proxies or load balancers used to communicate with the gateway server machine.

      • If the IP address of the reverse proxy sending the HTTP/S request is included, the URL returned to the client is either the Default Virtual Server URL or the Local Virtual Server URL (when defined).

      • If no IP addresses are defined for this parameter (not recommended), OMi works in Generic Mode. This means that you will only be able to log into OMi using the Virtual URL and not directly to the gateway server.

      Note If your reverse proxy and OMi gateway servers are not in the same domain, you must add the IP of the reverse proxy to the HTTP or HTTPS Reverse Proxy IPs parameter. For more details, see LW-SSO configuration for multi-domain and nested domain installations.

      To find the internal IP of your reverse proxy or load balancer:

      • Log in to OMi through the reverse proxy or load balancer.

      • Open the log in the following location on the gateway server <OMi_HOME>/log/jboss/UserActions.servlets.log.

      • The IP that appears in the latest log-in line in this log is the reverse proxy or load balancer IP. The entry should have your user name.

  4. Increase the reverse proxy timeout.

  5. Restart the HPE OMi service on the OMi gateway and data processing servers.

Note Once you change the OMi base URL, it is assumed that the client is initiating HTTP or HTTPS sessions using the new base URL. You must therefore ensure that the HTTP or HTTPS channel from the client to the new URL is enabled.