EM Express can access one (1) CDB or one (1) PDB at a time. Each port has to be unique on a host. The main PL/SQL package for settings is DBMS_XDB_CONFIG. Non-administrative users can gain read-only access to EM Express through the EM_EXPRESS_BASIC role.
I ran the following command on the JAR instance on PADSTOW to see if EM Express was configured:
SELECT dbms_xdb_config.gethttpsport, dbms_xdb_config.gethttpport FROM dual;
The result was:
GETHTTPSPORT GETHTTPPORT ------------ ----------- 0 0
Thus, EM Express is not configured here.
I ran the following command on the JAR instance on PADSTOW to configure EM Express:
EXEC dbms_xdb_config.sethttpsport(5500)
The result was:
PL/SQL procedure successfully completed.
I ran the following command on the JAR instance on PADSTOW to see if EM Express was configured correctly:
SQL> SELECT dbms_xdb_config.gethttpsport, dbms_xdb_config.gethttpport FROM dual;
The result was:
GETHTTPSPORT GETHTTPPORT ------------ ----------- 5500 0
I was able to use HTTPS://PADSTOW.YAOCM.ID.AU:5500/EM to connect to the EM Express Console after igoring the security warnings. The following page appears:
I ran the following set of commands on the JAR instance on PADSTOW to:
SQL> ALTER SESSION SET container = jam0; Session altered. SQL> SQL> EXEC dbms_xdb_config.sethttpsport(5501) PL/SQL procedure successfully completed. SQL> SQL> CREATE USER douglas IDENTIFIED BY "&password."; User DOUGLAS created. SQL> SQL> GRANT em_express_basic, 2 CREATE SESSION 3 TO douglas; Grant succeeded.
I was able to use the url, HTTPS://PADSTOW.YAOCM.ID.AU:5501/EM, to connect to the EM Express Console for the JAM0 PDB after igoring the security warnings, and get the following screen: