+ All Categories
Home > Documents > Essbase on OCI Pre-Work - WordPress.com · 2020. 10. 7. · Build the Essbase Stack •Choose your...

Essbase on OCI Pre-Work - WordPress.com · 2020. 10. 7. · Build the Essbase Stack •Choose your...

Date post: 06-Feb-2021
Category:
Upload: others
View: 1 times
Download: 0 times
Share this document with a friend
69
Essbase on OCI Pre-Work
Transcript
  • Essbase on OCI Pre-Work

  • Generate SSH Key (for Windows)

    • https://phoenixnap.com/kb/generate-ssh-key-windows-10

    https://phoenixnap.com/kb/generate-ssh-key-windows-10

  • Create EssbaseAdmin User

    • Click on the OCI hamburger• Go to Identity -> Federation

  • Create EssbaseAdmin User

    • Click on OracleIdentityCloudService

  • Create EssbaseAdmin User

  • Create EssbaseAdmin User

    • Login

  • Create EssbaseAdmin User

  • Create EssbaseAdmin User

  • Create EssbaseAdmin User

  • Create EssbaseAdmin User

  • Login as EssbaseAdmin

    • Logout of the OCI console• Close the browser (to remove any cookies to your login)• Go to the email address of EssbaseAdmin to activate the account

  • Login as EssbaseAdmin

    • Give EssbaseAdmin a password• Note: avoid the use of exclamation

    points (!) in the password

  • Login as EssbaseAdmin

    • Go to cloud.oracle.com• Click on “View Accounts”• Choose “Sign in to Cloud”• Enter your tenancy name

  • Login as EssbaseAdmin

  • Login as EssbaseAdmin

  • Create Essbase Compartment

  • Create Essbase Compartment

  • Create Essbase Compartment

    • Copy the Compartment OCID to a text editor• Note: If you hover over the

    OCID, the option to copy the OCID shows

  • Create a Dynamic Group

  • Create a Dynamic Group

  • Create a Dynamic Group

    • Choose “Any of the following”• Choose “Compartment OCID” and paste the OCID you copied in the

    previous step

  • Create a Dynamic Group

  • Create Policies

  • Create Policies

    • Choose the Essbase compartment

  • Create Policies

  • Create Policies (1)

    • Enter verbatim in statement 1:

    Allow group Administrators to manage all-resources in compartment Essbase

  • Create Policies (2)

    • Enter verbatim in statement 1:

    Allow dynamic-group EssbaseDynGrp to manage all-resources in compartment Essbase

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

  • Create IDCS Application

    • Once you click ”Finish”, be sure to copy the Client ID and Client Secret to your text editor

  • Create IDCS Application

  • Create Vault and Key

  • Create Vault and Key

  • Create Vault and Key

    • Copy the Cryptographic Endpoint URL to your text editor• Be SURE you are copying the URL that includes “crypto”, not

    ”management”

  • Create Vault and Key

    • Copy the Crypto Endpoint to your text editor

  • Create Vault and Key

    • Once the vault has finished building (the icon will turn green), create a Vault Key

  • Create Vault and Key

  • Create Vault and Key

    • Copy the Key OCID and paste it into your text editor

  • Encrypt the Passwords

    • Convert the following to base64 using this link• Client Secret• EssbaseAdmin password• Password you plan to use as the ATP password

    https://www.base64encode.org/

  • Encrypt the Passwords

    • Invoke OCI CLI (Note: It may take a few seconds to start up)

  • Encrypt the Passwords

    • Encrypt the passwords and Client Secret using:oci kms crypto encrypt --endpoint CryptoEndpointURL --key-id EssKeyOCID --plaintext PasswordClientSecretAsBase64• Copy what is in quotes after ciphertext to your text editor

  • Encrypt the Passwords

    • You will do this multiple times (2-3 times depending on if you use the same password for EssbaseAdmin and ATP admin or not)

  • Build the Essbase Stack

    • Go to the OCI Marketplace

  • Build the Essbase Stack

    • Search for Essbase and choose the appropriate deployment

  • Build the Essbase Stack

    • Make sure you have chosen the correct compartment and click “Launch Stack”

  • Build the Essbase Stack

    • Give your stack a name

  • Build the Essbase Stack

  • Build the Essbase Stack

    • Choose your Availability Domain• Choose how many OCPUs you want (the VM.Standard2.2 is 2 OCPUs.

    2.4 would be 4 OCPUs)• Upload your SSH

    public key

  • Build the Essbase Stack

    • Enter EssbaseAdmin as the admin• Enter EssbaseAdmin’s encrypted password

  • Build the Essbase Stack

    • Enter the IDCS tenancy ID from the IDCS console URL

  • Build the Essbase Stack

    • Enter the Client ID and encrypted Client Secret• Enter EssbaseAdmin for the IDCS Essbase Admin User

  • Build the Essbase Stack

    • Choose if you want to use an existing ATP or DBCS database instance• Enter the database admin encrypted

    password (mine is the same asEssbaseAdmin’s password)• Choose the database type: BYOL or UCM

  • Build the Essbase Stack

    • Choose your options• If you want a public Essbase IP

    address, click the top box• Note: This will remove the Bastion

    host option

    • If you have an existing VCN, you can choose that option• Finally, choose if you want a Load

    Balancer

  • Build the Essbase Stack

  • Build the Essbase Stack

    • You can monitor the stack build

  • Build the Essbase Stack

    • At the end of the build, you will get your “Outputs”• These include your URLs• Note: The stack will continuing building for around 20 minutes

  • Build the Essbase Stack

    • Go back to the IDCS application and enter the URLs

  • Test the Essbase Build

    • Go to your URL and login with EssbaseAdmin• You will need to add access to the other users and groups in IDCS

    AND in the Essbase Security tab


Recommended