Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for Java Environments 4.1.

httpEndpoint considerations

If the default httpEndpoint is bound to a VIPA address, a shared port, or a specific host name, BMC AMI Ops Monitor for Java Environments is unable to identify the replying server. This issue causes functions to fail or acquire nonsensical data.

You can resolve the issue by adding an additional httpsEndpoint that is unique to the server and host.

Example

The following example adds port 8385 as a new httpsEndpoint.

<httpEndpoint id="adminHttpEndpoint" host="*" httpPort="-1" httpsPort="8385" />

Related topics

Enabling-features-in-the-server-xml-file

Configuring-the-audit-interceptor-for-z-OS-Connect-EE-servers

Configuring-the-authorization-interceptor-for-z-OS-Connect-EE-servers



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*