2 Pre-Provisioning Phase

Pre-provisioning is the period after contracts are signed, but before receiving your environments, where some key activities can occur related to your upcoming implementation. Your Customer Success Manager (CSM) will be your main point of contact and guidance for these activities.

Activate Your Service into a Cloud Account

You will receive an activation e-mail from Oracle in the initial stages of provisioning, often immediately after your subscription order is booked. You will need to activate your cloud service into a cloud account to begin the provisioning activities for your Oracle Retail Service(s). Promptly complete the activation steps to better enable on-time environment delivery.

Note:

See the Activation section in this document.

Note:

See the Welcome Email section in this document.

Activation of your cloud service into a cloud account is required to be completed prior to beginning Retail application installation provisioning activities. Activation into a cloud account does not impact billing or the subscription service period. Those details are connected to the subsequent environment delivery of the Retail cloud service.

On activation of your cloud account, you have access to Oracle Cloud Infrastructure Console. The Identity and Access Management (OCI IAM) UI is integrated into the OCI Console, and your default Identity Domain will be created. An identity domain is a container for managing users and roles, federating and provisioning of users, securing application integration through Oracle Single Sign-On (SSO) configuration, and OAuth administration. It represents a user population in Oracle Cloud Infrastructure and its associated configurations and security settings such as Multifactor Authentication (MFA).

To enhance security, the seeding of the "Security Policy for OCI Console" sign-on policy is nowin all tenancies. As soon as an identity domain or an Identity Cloud Service stripe has been seeded with the policy, it should activate it to enable multifactor authentication (MFA) for users with administrative privileges.

Note:

See IAM Multifactor authentication (MFA).

Your default identity domain is of the Oracle Apps type. Each identity domain type is associated with a different set of features and object limits.

Note:

See Identity Domain Types.

With CSM assistance, identify the individual who is the initial OCI IAM client Identity Domain Administrator; Oracle Retail Cloud Operations creates for them the OCI IAM Identity Domain Administrator profile.

The client Identity Domain Administrator can then configure the OCI IAM tenant's branding, emailing rules, and user groups as required.

Note:

See Understand Administrator Roles.

Oracle Retail Best Practice for Tenancy, Applications, and Identity Domains

Oracle Retail recommends that all retail applications use the same OCI IAM Domain. All retail application environments must reside within the same OCI IAM domain for Single Sign-On (SSO) to function across production and non-production environments.

If the customer requires separating the identity management for production and non-production environments, the tenancies, domains, and application environments must be organized such that all production (prod) applications are in the same identity domain and all non-production (stage, dev, and so on) applications are in the same identity domain.

For Oracle Retail enterprise integration, the server-to-server security credentials required to flow among the Oracle Retail Applications (for example, Merchandise Foundation Cloud Service to Planning), the applications must reside in the same tenancy.

Note:

As mentioned above, the activation of your cloud service into a cloud account does not impact billing or the subscription service period. Those details are connected to the subsequent environment delivery of the Oracle Retail Cloud Services.