You have three options to access an PPM server installation.
Those client components connect to PPM only using HTTP or HTTPS via load balancer. Different server components, for example, UMC, PPM Web or PPM server are resolved using different load balancer contexts.
You can access the PPM system using the load balancer base URL:
The following table shows the connection parameters for the different server components.
Component |
Server URL |
---|---|
UMC |
http://<cloud instance IP/FQDN>:4080/umc |
PPM Query API |
http://<cloud instance IP/FQDN>:4080/ppmserver/API_<client name>/… |
PPM Documentation |
http://<cloud instance IP/FQDN>:4080/ppm/html/help/ppm/en/overview/ index.htm |
PPM Online Help |
http://<cloud instance IP/FQDN>:4080/ppm/html/help/ppm/en/handling/ index.htm |
The IP address or fully qualified domain name (FQDN) is the unique entry point to gain access to a PPM system running in a cloud environment. This IP address is required to install PPM on a cloud instance (for details see chapter Installation).
All internal PPM components (for example, PPM registries, PPM servers, PPM Web, etc.) register with their internal host name at the Apache ZooKeeper. Other components that need access to those internal PPM components will request the proper address from the Apache ZooKeeper. Apache ZooKeeper centrally manages all relevant host name/IP configurations in the PPM system. Host name properties in all relevant settings files (for example, RMIServerURL) were removed and placed in the runnable ppm_core and can be changed using standard ARIS PPM Cloud Controller commands. It is not necessary to change multiple settings files to change the IP or host name of the PPM system.
After a change of host name or IP address issued in ARIS PPM Cloud Controller, all PPM components must be restarted.