Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 32 Next »

To get the Platform web interface hostname:

kubectl get service platform -n uepe -o jsonpath="{.metadata.annotations.external-dns\.alpha\.kubernetes\.io/hostname}"

If you wish to connect Usage Engine Private Edition from the legacy swing desktop, do note that after added the instance via Platform FQDN hostname in desktop launcher, you need to modify pico.rcp.platform.port property value to port 6790 at Configuration > Properties tab.

In this example, following assumptions has been made:

  1. PostgreSQL is used as the system database.

  2. Postgres admin username (postgres.adminUsername) value is set to the default PostgreSQL administrator.

  3. It is assumed that you have previously bootstrapped the postgresqlPassword secret key with a value equal to db_password which has configured in the terraform.tfvars. Please see https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/251560020/Usage+Engine+Private+Edition+Preparations+-+Azure+4.2#Bootstrapping-System-Credentials-%5BinlineExtension%5D section for an explanation on how to do this.

  4. The system database is automatically created during installation.

  5. jdbcPassword and mzownerPassword are randomly generated.

  6. postgresqlPassword / oraclePassword / saphanaPassword is not randomly generated and therefore you need to create them in secret as described in point 3.

  7. In case you are using database tool uepe-sys-db-tool.jar to create the system database manually, you need to ensure the credentials stated in point 5 and 6 are both included in the secret, please see https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/251560020/Usage+Engine+Private+Edition+Preparations+-+Azure+4.2#Bootstrapping-System-Credentials-%5BinlineExtension%5D for details.

  • No labels