1. Enterprise Deployment Guide for Oracle Identity and Access Management in a Kubernetes Cluster
  2. Common Configuration and Management Procedures for an Enterprise Deployment

Part IV Common Configuration and Management Procedures for an Enterprise Deployment

There are a few typical configuration and management procedures that Oracle recommends for a regular enterprise deployment. Patching an enterprise deployment, configuring whole server migration and automatic server migration, performing scale out and scale in operations, troubleshooting issues are a few of the recommended procedures for an enterprise deployment.

This part of the guide contains the following chapters:

  • Common Configuration and Management Tasks for an Enterprise Deployment
    The configuration tasks include a few that are common to all enterprise deployments, such as verifying sizing information, performing backups and recoveries, and so on. Patching an enterprise deployment and cross wiring components are the other common tasks.
  • Using Whole Server Migration and Service Migration in an Enterprise Deployment
    The Oracle WebLogic Server migration framework supports Whole Server Migration and Service Migration. The following sections explain how these features can be used in an Oracle Fusion Middleware enterprise topology.
  • Centralized Monitoring Using Grafana and Prometheus
    When using Prometheus and Grafana, you can configure non-Kubernetes products to send their data to the console. This data is in addition to data from the Kubernetes components.
  • Centralized Log File Monitoring Using Elasticsearch and Kibana
    If you are using Elasticsearch and Kibana, you can configure Filebeat to send the log files to the centralized Elasticearch/Kibana console. Configure Filebeat on each of the hosts you want to send data from.
  • Scaling Procedures for an Enterprise Deployment
    The scaling procedures for an enterprise deployment include scale out and scale in. During a scale-out operation, you add Managed Servers to new nodes. You can remove these Managed Servers by performing a scale in operation.
  • Configuring Single Sign-On for an Enterprise Deployment
    You need to configure the Oracle HTTP Server WebGate in order to enable single sign-on with Oracle Access Manager.
  • Sanity Checks
    The sanity tests described in this chapter are over and above the normal tests detailed in the guide. They are designed to test the in-depth functionality of Oracle Access Management (OAM) and Oracle Identity Manager (OIM).
  • Troubleshooting
    You can troubleshoot the common issues that may arise with the Identity and Access Management enterprise deployment. The solutions provided for the common problems help you resolve them quickly.