Test Connectivity to Essbase

After you deploy Oracle Essbase on Oracle Cloud Infrastructure, test your connectivity to Essbase by logging in to the Essbase web interface, Cube Designer, the Essbase command-line tool (CLI), and MaxL.

Note:

For Essbase login URLs, see Essbase, REST, and Smart View Client URLs.

Find the value of essbase_url of the Essbase instance, as described in Prepare to Work with an Essbase Stack Instance.
Start the Essbase stack, as described in Start the Essbase Stack.
In a browser, enter the value of essbase_url of the Essbase instance.
Log in as the initial Essbase service administrator, using the IAM or IDCS System Administrator User ID that you provided during stack deployment.

When you first log in, a pop-up message requests application permissions. Click Allow. This message should not appear again.

Find the value of essbase_url of the Essbase instance, as described in Prepare to Work with an Essbase Stack Instance.
Start the Essbase stack, as described in Start the Essbase Stack.
Follow the steps to set up Cube Designer, as described in Set up Cube Designer.
Log in as the initial Essbase service administrator, using the IAM or IDCS System Administrator User ID that you provided during stack deployment.

Find the public IP address of the Essbase instance, as described in Prepare to Work with an Essbase Stack Instance. For example, https://192.0.2.1/essbase.
Start the Essbase stack, as described in Start the Essbase Stack.
Follow the steps to set up CLI, as described in Download and Use the Command-Line Interface.
If you are connecting over VPN and you're using a load balancer, set a proxy. When proxies are needed, you must set them for each shell session. Example:
```
set HTTPS_PROXY=www-proxy-example.com:80
```
Change directories to the location where you downloaded the client. Example:
```
cd ../../temp/client/cli
```
Run the CLI shell, esscs.bat or esscs.sh, and log in as the initial Essbase service administrator, which is the IAM or IDCS System Administrator User ID that you provided during stack deployment.

In the following example, as the password is not entered, the administrator will be prompted to provide it next. The URL is the essbase_url from the job outputs resulting from the stack deployment.
```
esscs login -u admin1@example.com -url https://192.0.2.1/essbase
```
Any Identity Cloud Service users provisioned to work with Essbase can log in to CLI. The actions they can perform in CLI are determined by their roles and permissions. For details, see Understand Your Access Permissions in Essbase.

Find the public IP address of the Essbase instance, as described in Prepare to Work with an Essbase Stack Instance. For example, https://192.0.2.1/essbase.
Start the Essbase stack, as described in Start the Essbase Stack.
Follow the steps to set up MaxL, as described in Manage Essbase Using the MaxL Client.
Change directories to the location where you downloaded the client. Example:
```
cd ../../temp/client/maxl
```
Run the startMAXL batch or shell script. A command prompt opens, and the MaxL Client starts up.
Log in by providing your credentials and the Essbase URL in the MaxL login statement.

In the following example, the user logging in, admin1@example.com, is the initial Essbase service administrator, which is the IAM or IDCS System Administrator User ID that you provided during Essbase stack deployment. As the password is not entered in this example, the administrator will be prompted to provide it next. The URL is the essbase_url from the job outputs resulting from the Essbase deployment.
```
login admin1@example.com on "https://192.0.2.1/essbase";
```
Any Identity Cloud Service user provisioned to work with Essbase can log in to MaxL, as long as they are provisioned as a power user or administrator.