After deployment, you can access the PEM web interface in your choice of browser. If the PEM server resides on a LOCAL host, navigate to:https://address_of_ark_server/pemhttps://address_of_remote_pem_server:port/pemIf you have registered the Ark console with a remote PEM server during deployment, use the PEM server credentials to connect.If you have deployed the PEM server locally (on the Ark host), the password associated with the Ark backing database will be used for the PEM server. Unless you have modified the password (either during deployment in the DB User New Password field, or after deployment in the console backing database), the Ark database superuser has the following connection credentials at deployment:name: postgrespassword: 0f42d1934a1a19f3d25d6288f2a3272c6143fc5dYou should change the password after deployment to a unique password (known only to trusted users). For details, see section 6.2.After authenticating with the server, the PEM web interface allows you to manage your monitored nodes (see Figure 2.13).When you launch an Ark cluster on a console that is registered with PEM, Ark will register each node of the cluster with the PEM server for monitoring. Each node of an Ark cluster, and the agent that resides on the node is displayed in a Group-level heading in the PEM web interface Browser tree control. The node name is:Ark-Cluster_cluster_nameWhere cluster_name is the name assigned to the cluster.Right click on the IP address of a cluster node, and provide the password specified when the cluster was provisioned to authenticate with the database and view the database objects that reside on the cluster in the tree control (see Figure 2.12).PEM documentation is available via the PEM web interface Help menu, or at the EnterpriseDB website at:If your Ark clusters are provisioned with private IP addresses, they may not be reachable from the PEM server. If this is the case, you will not be able to use the PEM Dashboard to remotely browse the database server. PEM agents running on the Ark cluster nodes will be able to report status to the PEM Server.For example, replica nodes created on OpenStack are not assigned public floating IP addresses, so you can't browse them remotely from the PEM Dashboard by default. You must manually assign a public IP address before being able to browse each node.