1. Administration Guide
  2. Pre-Provisioning

1 Pre-Provisioning

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. For Order Broker Cloud Service implementations, your Customer Success Manager (CSM) will be your main point of contact for these activities.

Note:

For more information about how Oracle Retail applications undergo pre-provisioning and provisioning phases, see the Oracle Retail Identify Management for OCI IAM Startup Guide.

Activate Your Service into a Cloud Account

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

On activation of your cloud account, you will have access to Oracle Cloud Infrastructure Console and the Identity and Access Management (OCI IAM) 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 MFA).

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

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:

Activation of your cloud service into a cloud account does NOT impact billing or the subscription service period—these details are connected to the subsequent environment delivery of the Order Broker Cloud Service.

Creating an Oracle Cloud Account

To start the setup, you'll click the Activate link provided in the e-mail received. Then the following steps are required:

  1. Provide the desired name for the Oracle Cloud Account.

    A best practice is to use a name which will encompass the scope of services to be managed in the account, such as a combination of your company name and "retail". For example, mystoresretail. After activation, you can adjust the displayed name for the cloud account.

  2. Provide your e-mail address as the customer administrator who receives the activation e-mail.

    The e-mail address must match the initial e-mail. If you would like a different contact to be used as the administrator, this can be managed after activation in coordination with your CSM.

  3. The activation success message will display, and you will receive a new welcome e-mail with access credentials.

Foot 1

Activating into an Existing Oracle Cloud Account

Activate your Retail cloud service within the Account Management section of your existing Oracle Cloud Account.

  1. Log in to your existing Oracle Cloud Account.

    Clicking the Activate link brings you to the login page.

  2. Within the Dashboard, click on the Account Management menu and then select the Activate tab.

    Available services to activate will be listed; you may need to select Show: Pending Activations.

  3. Click the Cloud Service Account Setup button to complete setup. This setup will enable you to select the current Oracle Cloud Account as the destination for the cloud service activation.

If you have any issues with the above, see the Frequently Asked Questions chapter.

Prepare Project Team

During this time, you will also be putting together your project plan for the deployment and go-live phases of your implementation. It is important to consider the following during this planning phase to prepare your project team for implementation:

  • OCI Identity & Access Management - As noted above, you will be using OCI IAM UI for user management for Order Broker. During the pre-provisioning timeframe, familiarize yourself with this solution and its features.

    https://docs.oracle.com/en-us/iaas/Content/Identity/home.htm

  • Project Team Training - Consider the training that the members of your team will need in order to make your implementation successful. This includes both your employees, as well as your systems integration partner. Suggested training topics to consider include Retail Integration Cloud Service configuration

  • Security Configurations - During this phase, you should designate a portion of your team to becoming familiar with OCI IAM and the roles, duties, and privileges for Order Broker. You can also start designing the roles that you will need for your users, and what duties will be assigned to your custom roles. For more details, please refer to Setting Up Data.


Footnote Legend

Footnote 1: Note: An Oracle Cloud Account is not the same as your My Oracle Support account. The Oracle Cloud Account exists within the OCI console and includes your identity domains for managing user access and identity.