You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Oracle Essbase][essbase] is a business analytics solution that uses a proven, flexible, best-in-class architecture for analysis, reporting, and collaboration. It delivers instant value and greater productivity for your business users, analysts, modelers, and decision-makers, across all lines of business within your organization. You can interact with Essbase, through a web or Microsoft Office interface, to analyze, model, collaborate, and report.
14
14
15
15
This Quick Start automates the deployment of Oracle Essbase on [Oracle Cloud Infrastructure (OCI)][oci]. It can also deploy additional stack components required – Autonomous Database, Load Balancer, Storage, Virtual Cloud Network (VCN) as part of the deployment.
16
16
17
-
For more details on deploying the Essbase stack on Oracle Cloud Infrastructure, please visit the [Administering Oracle Essbase](https://docs.oracle.com/en/database/other-databases/essbase/19.3/essad/index.html) guide.
17
+
For more details on deploying the Essbase stack on Oracle Cloud Infrastructure, please visit the [Administering Oracle Essbase](https://docs.oracle.com/en/database/other-databases/essbase/21/essad/index.html) guide.
18
18
19
19
### Default Topology
20
20
@@ -30,11 +30,11 @@ The above digram shows the full topology supported by the terraform scripts. In
30
30
31
31
## Before You Begin with Oracle Essbase
32
32
33
-
Refer to the [documentation](https://docs.oracle.com/en/database/other-databases/essbase/19.3/essad/you-begin-oracle-essbase.html) for the pre-requisite steps to using Essbase on OCI.
33
+
Refer to the [documentation](https://docs.oracle.com/en/database/other-databases/essbase/21/essad/you-begin-oracle-essbase.html) for the pre-requisite steps to using Essbase on OCI.
34
34
35
-
### Encrypt Values using KMS
35
+
### Create Secrets with OCI Vault
36
36
37
-
Oracle Cloud Infrastructure [Key Management (KMS)][kms] enables you to manage sensitive information when creating a stack. You are required to use KMS to encrypt credentials during provisioning by creating a key. Passwords chosen for Essbase administrator and Database must meet their respective password requirements.
37
+
Oracle Cloud Infrastructure [Vault][vault] enables you to manage sensitive information when creating a stack. You are required to store your credentials in the vault prior to provisioning the Essbase stack. Passwords chosen for Essbase administrator and Database must meet their respective password requirements.
38
38
39
39
### Create Dynamic Group
40
40
@@ -57,6 +57,7 @@ allow group group_name to manage buckets in compartment compartment_name
57
57
allow group group_name to manage objects in compartment compartment_name
58
58
allow group group_name to use vaults in compartment compartment_name
59
59
allow group group_name to use keys in compartment compartment_name
60
+
allow group group_name to use secrets in compartment compartment_name
60
61
```
61
62
62
63
Some policies may be optional, depending on expected use. For example, if you're not using a load balancer, you don't need a policy that allows management of load balancers.
@@ -73,6 +74,7 @@ allow dynamic-group group_name to manage autonomous-backups in compartment compa
73
74
allow dynamic-group group_name to read buckets in compartment compartment_name
74
75
allow dynamic-group group_name to manage objects in compartment compartment_name
75
76
allow dynamic-group group_name to use keys in compartment compartment_name
77
+
allow dynamic-group group_name to use secrets in compartment compartment_name
76
78
```
77
79
78
80
## Using the Terraform command line tool
@@ -97,7 +99,7 @@ terraform init
97
99
98
100
### Configure
99
101
100
-
Choose the Essbase image that corresponds to the desired[license](#License), by removing the `.disabled` extension on appropriate `essbase-<license>.auto.tfvars.disabled` file. Set the remaining [variables](./VARIABLES.md) needed to drive the stack creation. This can be done by creating the terraform.tfvars from the [template file](./terraform/terraform.tfvars.template), or using environment variables as described here.
102
+
By default, the Essbase image selected is the BYOL [license](#License). To use the UCM[license](#License), replace the `essbase.auto.tfvars` file with `essbase.auto.tfvars.ucm`. Set the remaining [variables](./VARIABLES.md) needed to drive the stack creation. This can be done by creating the terraform.tfvars from the [template file](./terraform/terraform.tfvars.template), or using environment variables as described here.
101
103
102
104
Let's make sure the plan looks good:
103
105
@@ -149,7 +151,7 @@ allow group group_name to manage orm-jobs in compartment compartment_name
149
151
150
152
## Post-Deployment Tasks
151
153
152
-
Refer to the [documentation](https://docs.oracle.com/en/database/other-databases/essbase/19.3/essad/complete-deployment-tasks.html) for a list of post-deployment tasks.
154
+
Refer to the [documentation](https://docs.oracle.com/en/database/other-databases/essbase/21/essad/complete-deployment-tasks.html) for a list of post-deployment tasks.
153
155
154
156
## License
155
157
@@ -171,8 +173,8 @@ The Oracle Essbase product requires an on-premises purchased license and active
171
173
172
174
If you have an issue or a question, please take a look at our [FAQs](./FAQs.md) or [open an issue](https://github.com/oracle-quickstart/oci-essbase/issues/new).
Copy file name to clipboardExpand all lines: VARIABLES.md
+8-14Lines changed: 8 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,12 +22,6 @@
22
22
| compartment_ocid | Y || The target compartment OCID in which all provisioned resources will be created. |
23
23
| stack_display_name | N || Display name prefix for all generated resources. If not specified, this will be automatically generated. |
24
24
25
-
## Vault Variables
26
-
| Name | Required | Default | Description |
27
-
| ---- | -------- | ------- | ----------- |
28
-
| kms_key_id | Y || The OCID for the encryption key used for the provided credentials. |
29
-
| kms_crypto_endpoint | Y || The crypto endpoint for the vault. |
30
-
31
25
## Notification Details
32
26
| Name | Required | Default | Description |
33
27
| ---- | -------- | ------- | ----------- |
@@ -73,7 +67,7 @@
73
67
| config_volume_size | N | 64 | Define the target size of the configuration volume, which stored the Essbase system data, such as logs. |
74
68
| temp_volume_size | N | 64 | Defined the target size of runtime temporary data. |
75
69
| essbase_admin_username | N | admin | The name of the Essbase system administrator. |
76
-
|essbase_admin_password_encrypted| Y || The password for the Essbase system administrator, encrypted with the provided vaule key. Use a password that starts with a letter, is between 8 and 30 characters long, contains at least one number, and, optionally, any number of the special characters (`$``#``_`). For example, `Ach1z0#d`. |
70
+
|essbase_admin_password_id| Y || The OCID for the vault secret that holds the password for the Essbase system administrator. Use a password that starts with a letter, is between 8 and 30 characters long, contains at least one number, and, optionally, any number of the special characters (`$``#``_`). For example, `Ach1z0#d`. |
77
71
| rcu_schema_prefix | N || Schema prefix to use when running RCU. A value with be automatically generated if not specified. |
78
72
| create_public_essbase_instance | N | false | Create the Essbase compute instance with a public IP address. |
79
73
| enable_essbase_monitoring | N | false | If enabled, the Essbase compute instance will emit telemetry data to the OCI Monitoring service. |
@@ -82,21 +76,21 @@
82
76
## Security Details
83
77
| Name | Required | Default | Description |
84
78
| ---- | -------- | ------- | ----------- |
85
-
|security_mode| N | idcs | Choose embedded LDAP or integration with Identity Cloud Service (IDCS). The use of embedded LDAP is not recommended for production workloads. |
86
-
| idcs_tenant | if `security_mode=idcs`|| The ID of your Identity Cloud Service instance, which typically has the format idcs-<guid>, and is part of the host name that you use to access Identity Cloud Service. |
87
-
| idcs_client_id | if `security_mode=idcs`|| The client ID for the IDCS application. |
88
-
|idcs_client_secret_encrypted| if `security_mode=idcs`|| The client secret for the IDCS application, encrypted with the provided vault key. |
89
-
| idcs_external_admin_username | if `security_mode=idcs`|| A user id to be registered as an Essbase administrator. This user must exist in the provided Identity Cloud Service instance. |
79
+
|identity_provider| N | idcs | Choose embedded LDAP or integration with Identity Cloud Service (IDCS). The use of embedded LDAP is not recommended for production workloads. |
80
+
| idcs_tenant | if `identity_provider=idcs`|| The ID of your Identity Cloud Service instance, which typically has the format idcs-<guid>, and is part of the host name that you use to access Identity Cloud Service. |
81
+
| idcs_client_id | if `identity_provider=idcs`|| The client ID for the IDCS application. |
82
+
|idcs_client_secret_id| if `identity_provider=idcs`|| The OCID for the vault secret that holds the client secret for the IDCS application. |
83
+
| idcs_external_admin_username | if `identity_provider=idcs`|| A user id to be registered as an Essbase administrator. This user must exist in the provided Identity Cloud Service instance. |
90
84
91
85
## Database Details
92
86
| Name | Required | Default | Description |
93
87
| ---- | -------- | ------- | ----------- |
94
88
| use_existing_db | N | false | Select this option to enable support of an existing database for the internal Essbase repository. |
95
89
| existing_db_type | N | Autonomous Database | Select which database you will use |
96
90
| existing_db_id | N || Target ATP database in which to create the Essbase schema. |
97
-
|db_admin_password_encrypted| if `existing_db_type=Autonomous Database`|| The password for the database administrator, encrypted with the provided vault key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$``#``_`). For example, `BEstr0ng_#12`. |
91
+
|db_admin_password_id| if `existing_db_type=Autonomous Database`|| The OCID for the vault secret that holds the password for the database administrator. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$``#``_`). For example, `BEstr0ng_#12`. |
98
92
| db_license_model | N | LICENSE_INCLUDED ||
99
93
| existing_oci_db_system_database_id | N || The database within the DB System in which to create the Essbase schema. |
100
94
| existing_oci_db_system_database_pdb_name | N || The name of the pdb in the target database. Required if not using the default pdb created during database provision. |
101
95
| oci_db_admin_username | N | SYS | The username for the database administrator. |
102
-
|oci_db_admin_password_encrypted| if `existing_db_type=OCI`|| The password for the database administrator, encrypted with the provided vault key. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$``#``_`). For example, `BEstr0ng_#12`. |
96
+
|oci_db_admin_password_id| if `existing_db_type=OCI`|| The OCID for the vault secret that holds the password for the database administrator. Use a password that starts with a letter, is between 12 and 30 characters long, contains at least one number, and at least one of the special characters (`$``#``_`). For example, `BEstr0ng_#12`. |
0 commit comments