Oracle® Retail Integration Cloud Service Oracle® Retail Integration Cloud Service Service Administrator Action List Release 19.1.000 F34817-01 |
|
![]() Previous |
![]() Next |
Once your environments are ready for you, the person designated as your service administrator will receive a welcome e-mail: one for each cloud service and each environment (stage, production, and so on).
Follow all instructions in the "Action Required: Access and Administer Production/Stage/Test Environment…" e-mail.
This environment access e-mail contains critical details required for you to access and administer your Cloud Service. You will receive on e-mail for each provisioned environment. Save these e-mails.
Log in to your Cloud Service. Use the Identity Management URL, username and temporary password provided in the environment access e-mail to verify access to your service. At your first login attempt, create a new password and make note of it because at this point you are the only one with access!
You will receive a separate e-mail for each provisioned environment, and the password for each environment is maintained separately. In addition, please note that you will not be able to access the Retail applications until you grant the appropriate application roles to your user
It is recommended that you save this e-mail for future reference, because at this point the service administrator is the only person with access.
Once you receive your welcome e-mail, it is recommended that you, as the system administrator, log into IDCS to verify your access and create a new password. You will also be assigned the application administrator group for each Retail Integration service in both your production and pre-production environments. Note that the group for pre-production will have an added extension (_PREPROD) in order to differentiate between the two. These should not be deleted.
It is also recommended that you add additional administrators in order to have a backup administrator and share in user management administration, as at this point no one else in your organization will have access to IDCS or the Retail Integration solutions. For assistance in creating users or adding them to groups, see the following documents:
Note: You may notice that there are a number of other user IDs set up in IDCS for Retail Integration (for example, bdi_admin, jos_admin). These users were seeded by the Oracle Cloud Operations team for use in Merchandising batch and integration processes. These users will be managed by the Oracle Cloud Operations team. |
Next, you should validate that you are able to access and successfully log into each of the Retail Integration Cloud Services for which you have been provisioned using the URLs provided in the e-mail, along with the username and password.
The welcome e-mail will also include your Customer Support Identifier (CSI). This should be registered with My Oracle Support (MOS), which you will use to log questions or issues about these services. Follow link in the e-mail or access support.oracle.com
to create a new account. If you already have a MOS account, remember to add your new CSI to your existing MOS account.
The first person to request access to a CSI will be checked by Oracle to ensure the domain of their e-mail address matches the domain associated with the CSI. Once approved, they will be made the Customer User Administrator of that CSI, and can approve others to use it. If someone else has already been made the administrator of that CSI, then the request will be e-mailed to him or her for approval. For more information on the Customer User Administrator, see MOS ID 1544004.2
.
Note: You will not be able to register your CSI number until your production environment has been provisioned. |
Before end users can access the Cloud Service application it is necessary to provision each user access to the system, and assign roles to each user to control what functionality will be available to them. The access provisioning is done using Oracle Identity Management (OIM). Instructions for end user account creation are documented in an Administration Guide, found in an online Documentation library at this location:
http://www.oracle.com/technetwork/documentation/oracle-retail-100266.html