Steps to enable OCI Container Engine for OKE Cluster Access from kubectl CLI

Steps to enable Oracle Cloud Infrastructure (OCI) Container Engine for Kubernetes (OKE)

cluster access from the kubectl CLI?

Setting Up Local Access to Clusters

To set up a kubeconfig file to enable access to a cluster using a local installation of kubectl and the

Kubernetes Dashboard:

Step 1: Generate an API signing key pair

Step 2: Upload the public key of the API signing key pair

Step 3: Install and configure the Oracle Cloud Infrastructure CLI

Step 4: Set up the kubeconfig file

Step 5: Verify that kubectl can access the cluster

Deploying the custom jar into the OIM placeholder library

Deploying the custom jar into the OIM placeholder library

The placeholder library is the file oracle.iam.ui.custom-dev-starter-pack.war. This file is available along with the other OIM application packages (EARs and WARs) at $OIM_ORACLE_HOME/server/apps folder.

Before doing any modification to this file, create a backup of it.

Using a ZIP tool, like 7-Zip, the steps are:

1.       Open the oracle.iam.ui.custom-dev-starter-pack.war

2.       Add the custom jar file to the 'WEB-INF/lib' folder. If the 'lib' folder does not exist, create it

3.       Save the oracle.iam.ui.custom-dev-starter-pack.war file.

4.       Copy the oracle.iam.ui.custom-dev-starter-pack.war file back to its original location under $OIM_ORACLE_HOME/server/apps

5.       Stop OIM managed server

6.       In WebLogic administration console, update the 'oracle.iam.ui.custom' library deployment and activate the changes

7.       Start OIM managed server.