Use Secure Shell (SSH) client software to connect to the Essbase instance deployed on Oracle Cloud Infrastructure to perform administrative tasks.
To access the private compute node, it depends on your environment. If your network configuration uses FastConnection or VPN with IPSec, you must provide the network setup that allows you to SSH to the private compute node.
You can log in securely to your Essbase instance from a remote host by using a secure shell (SSH) connection.
Before creating the Essbase instance on Oracle Cloud Infrastructure, generate at least one SSH key pair, and ensure that the private key is available on each host that you’ll use to access Essbase instances.
To connect to Essbase using SSH, you use the SSH private key, which is part of the key pair created as a prerequisite to deploying the stack. After you've created the stack, you have a few different IP addresses, depending on the network topology.
You can use any SSL utility, for example openSSL, to generate SSH keys and to log in to your Essbase instance.
If the Essbase compute node has an
essbase_node_public_ip address, you can access it directly with
ssh of the Essbase public IP using the following:
$ ssh -i <path_to_private_key> opc@<essbase_public_ip>
If you have deployed stack in a private subnet, the Essbase compute node will have a private IP only. In this case, you must create Bastion provided under Identity & Security. Use this Bastion to access the Essbase compute node. SSH commands can be copied from the Bastion session when you create the session.
(For 19c through 188.8.131.52.5) If you deployed a private subnet, the Essbase compute node has a private IP, but no public IP. In this case, you must use the public IP of the bastion host to access the Essbase compute node by proxy. Examples are provided in this topic. SSH syntax may vary, depending on your SSH client and operating system.
- In OCI Console > Identity & Security > Bastion.
- On Bastion page, click Create Bastion.
- Enter Bastion name.
- In Configure Networking, select the Target Virtual Cloud Network (VCN), the VCN in the relevant compartment – the VCN on which Essbase node is deployed.
- Select the Target Subnet on which Essbase node is deployed.
- Enter CIDR – IP or range of IPs from which access will be allowed.
- Click Create Bastion. Bastion is created.
- In OCI Console > Identity & Security > Bastion > click relevant created Bastion name link.
- Click Create Session.
- On the Create Session page, select session type value.
- Enter username.
- Enter computer instance to which you want to connect.
- Specify the SSH Key.
- In Advanced options, you can specify the IP to which you want to connect.
- Click Create Session. The session is created.
- Open the compute instance and enable Bastion Service toggle for the instance. Note by default, a Bastion session is available for three hours, and can be defined otherwise.
- Go to OCI Console > Identity & Security > Bastion.
- Select the relevant Bastion.
- Under Resources, click Sessions to view the Sessions page.
- On Sessions page, open drop-down menu to the right of the relevant created session, and click Copy SSH Command. You will use this command to ssh and log into the Essbase node.
- Replace ssh_key paths in the copied command. Edit the SSH command as follows: Replace
<privateKey>with the path to the private key (from the SSH key pair used to create the session).
Bastion Host SSH Tips (For 19c through 184.108.40.206.5)
Essbase doesn't have a public IP address when you deploy a private subnet using a bastion host. Use these guidelines to help you configure your system for SSH access to the Essbase compute node on Oracle Cloud
Infrastructure. These examples utilize a bash shell. Bash commands you enter are in
Change to the hidden directory,
.ssh, usually located in your user directory (check the documentation for your specific SSH client).
Modify (or create) the
configfile in the
.sshdirectory. Though the following example invokes the UNIX vi editor, you can use any text editor.
configfile, enter HostName and IdentityFile details for the bastion host. For HostName, provide the IP address of the bastion host, and for IdentityFile, provide the location of the private key that matches the public key you provided to Resource Manager during the Essbase deployment. Format:
Host bastion HostName <bastion_host_public_ip> IdentityFile <path_to_private_key>
Add to the config file an additional host entry for the private Essbase subnet. For HostName, provide the essbase_node_private_ip, and for IdentityFile, provide the location of the private key that matches the public key you provided to Resource Manager during the Essbase deployment. For ProxyCommand, set up SSH access for the opc user to access the bastion host by proxy. Example:
Host essbase HostName <essbase_node_private_ip> IdentityFile <path_to_private_key> ProxyCommand ssh opc@bastion -W %h:%p
Here is an example of a completed
Host bastion HostName 192.0.2.111 IdentityFile C:/temp/ids/my_key Host essbase HostName 10.0.1.2 IdentityFile C:/temp/ids/my_key ProxyCommand ssh opc@bastion -W %h:%p
configfile and exit the editor.
In your command window, log in over SSH to Essbase, by proxy of the bastion host, as the opc user.
Switch to user oracle to explore the Essbase compute and complete any administrative tasks.
sudo su oracle
Change to the home directory of the Essbase compute node on Oracle Cloud Infrastructure.
View the directories.
ls bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv tmp u01 usr var
Explore the Essbase directories. The applications are in the
appdirectory, and the file catalog is in the
cd /u01/data/essbase ls app catalog hybrid jagentId.id