1. Implementation Guide
  2. Getting Started

3 Getting Started

Once RDS is provisioned, the following APEX workspaces are available to use:

Table 3-1 APEX Workspaces

Workspace Name Source Cloud Service

MFCS

Merchandising Foundation Cloud Service

CECS

Customer Engagement Cloud Service

OBCS

Order Broker Clouds Service

XOCS

Xstore Office Cloud Service

Note:

These workspaces are available even if you have not subscribed to the associated cloud services, but they contain no database objects or replicated data.

You can access these workspaces by navigating to the workspace login page for your environment. The URL for this will be delivered to you after provisioning is complete, and follows the pattern:

https://<base URL>/<environment ID>/ords/

For example:

https://ocacs.ocs.oc-test.com/nryfhvvl5ka2su3imnq6/ords/

You are then able to log in to one of the workspaces listed above using the credentials that have been supplied to you.

APEX User Management

Once provisioned, each workspace comes with a single login. This user is the Workspace Administrator for that workspace.  In most cases, teams will need to create additional development users in these workspaces to facilitate the development of APEX applications and REST endpoints.  The Workspace Administrator account has the permissions to create additional users through the APEX UI. Use the workspace's Administration menu in the top right corner to access Manage Users and Groups. For full details, please refer to the APEX Administration Guide.


APEX Administration

Create the users needed by selecting the Create User button and filling in the form.


APEX Manage Users and Groups

The developer accounts created through this method have both an APEX account login as well as a database login. Upon initial creation, both share the same username and password. However, the account that is used to log into the APEX Workspace is the database account. This is important to understand, because if the user password is changed using the APEX UI, only the APEX account password is changed.  The database password is not affected, as noted on the UI screen here:


APEX Account Privileges

To aid in managing the database accounts, each RDS workspace comes configured with the RDS_PASSWORD_MGR database package containing two function that should be used to change the database passwords.

  • RDS_PASSWORD_MGR.change_password('oldPwd','newPwd'): The change_password function allows users to change their own database password.  It is callable by users with developer or higher privileges.

Example usage

BEGIN
    RDS_PASSWORD_MGR.CHANGE_PASSWORD('oldPassword', 'newPassword');
END;

  • RDS_PASSWORD_MGR.change_any_password('User', 'NewPwd'): The change_any_password function is available to the Workspace Administrator to reset anyone's password. A few things to note about this function:

    • Only developer or higher passwords can be reset

    • The user being reset must exist in the current workspace

    • The logged in Workspace Administrator cannot change their own password using this method. They must use the change_password function instead.

Example usage

BEGIN
    RDS_PASSWORD_MGR.CHANGE_ANY_PASSWORD('user','newPassword');
END;

Note:

In the current release of APEX in ADW, there is no support for externalizing the development users. As such, these users can not be managed in IDCS, OCI-IAM, or any other external user management system.  They must be managed as APEX users, as described above.