Jay-Rajput/oci_data huggingface dataset:
Getting Started with IAM Identity Domains REST API


IAM identity domains REST API securely manage resources, including identities and configuration data. Support for OpenID Connect allows integration with compliant applications and identity domains. The OAuth2 service provides an API infrastructure for authorization that supports a range of token grant types that enable you to securely connect clients to services.

The identity domains REST API supports SCIM 2.0 compliant endpoints with standard SCIM 2.0 core schemas and Oracle schema extensions to:

Manage users, groups, and apps.

Perform identity functions, including password generation and reset.

Perform administrative tasks including bulk operations and job scheduling.

Configure settings for an identity domain including multifactor authentication, branding, and notification templates.

This guide contains the following sections:

Quick Start: Quickly get started with identity domains REST API in IAM by completing prerequisites, installing curl, and setting up authorization to manage your identity domain resources such as users, groups, and applications.
API Rate Limits: Understand the rate limiting for APIs for different identity domain types in IAM.
Endpoints Deprecation Notices: Learn about endpoints deprecation notices for identity domains in IAM.
Structuring Resource Requests: Learn the guidelines for building send requests in an identity domain in IAM.
Finding an Identity Domain URL: Find the Domain URL in the user interface and use it to access PaaS products that are integrated with identity domains in IAM.
Using cURL: Learn how to use cURL to access the REST APIs.
Managing Authorization Using the API: Learn how to use an OAuth client to access identity domains REST API. The identity domains REST API isn’t accessible using only an identity domain username and password. To access the identity domains REST API, you need an OAuth2 access token or an API key to use for authorization.
API Use Cases: Step through typical use cases using the IAM identity domain REST APIs.
Using Business Glossaries

Benefits of Using a Business Glossary
Owners of Business Glossaries
One Business Glossary Versus Multiple in an Organization
Data Flows

Design Concepts
Using the Designer Interface
Sending an Email

Using the Console
Using the API
Using the SDK
Volume Testing and Sending to Email Aliases
Shared IP or Dedicated IP
Reference
 information for the DevOps service including installation details for the Oracle Cloud Infrastructure DevOps plugin for Jenkins, build specification, and deployment specification.

DevOps Plugin for Jenkins
Build Specification
Command Specification
Deployment Specification
Build Runner Runtime Details
Shell Container Image Runtime Details
Using Oracle GraalVM in DevOps Build Pipelines
Glob Patterns



For more information click here https://docs.oracle.com/en-us/iaas/goldengate/doc/reference.html

For more information click here https://docs.oracle.com/en-us/iaas/disaster-recovery/doc/disaster-recovery-reference.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/devops/using/reference.htm

For more information click here https://docs.oracle.com/en-us/iaas/digital-assistant/doc/reference.html

For more information click here https://docs.oracle.com/en-us/iaas/database-migration/doc/reference.html
About Management Dashboard


Management Dashboard allows you to build performance monitoring, diagnosis and data analysis solutions on Oracle Cloud Infrastructure platform, infrastructure, and application resources. It has powerful data visualization options that gather real-time and historic data and display it in widgets.

The Management Dashboard visualization framework provides a quick insight into the health and performance of your resources. The visual representation of information in a dashboard makes the information easy to interpret and helps identify outliers, isolate issues and take corrective action.

Management Dashboard is available as part of the following Oracle Cloud Infrastructure Observability & Management services:

Application Performance Monitoring
Database Management
Logging Analytics
Management Agent
Operations Insights

For each Observability & Management service that it supports, Management Dashboard provides:

Oracle-defined dashboards, widgets, and filters that cover many common resource-monitoring scenarios.
Ability to create custom dashboards and widgets that meet your specific requirements.

As you work with Management Dashboard, here are some of the common terms that you will come across:

Dashboards: Data visualization tools that gather real-time data from the various tiers of an application or other monitored resource, and display it in widgets.
Widgets: Single data visualization for one type of resource, which allow you to display data in various presentation styles. The primary role of a widget is to display monitoring data in a form useful to you.
Filters: Data perspectives that can be applied to narrow down the results displayed in a single widget or multiple widgets.

The Management Dashboard documentation provides generic information regarding its features. For specific information on how to use dashboards for the Observability & Management services it supports, see service documentation:

Application Performance Monitoring Dashboards
Database Management Dashboards
Logging Analytics Dashboards
Management Agent Dashboards
Operations Insights Dashboards
Managing Migration Plans

Required IAM Policies
Recommendations for Using Multiple Migration Plans for a Migration Project
What to Do Next


After deploying your service and setting up users and groups, you need to complete some additional tasks in the Oracle Content Management web interface to get Oracle Content Management up and running.

Perform the followings tasks, as necessary, as described in Administering Oracle Content Management:

Set service defaults such as user quotas, link behavior, file type and size restrictions, and virus scan options.

Another important default to set is the default role given to new folder members.

You might want to perform some of the following tasks to get the most out of Oracle Content Management:
Apply branding and URLs to customize Oracle Content Management with your logo and other branding, and change the links that are available in the user menu to download apps, access help, and send feedback..
Enable email notifications to alert users when certain events occur, like when someone flags you, or when someone creates a public link for a file or folder.
Set the default time zone and language for the Oracle Content Management user interface.
Configure custom properties (metadata) so that users can quickly categorize files and folders with additional information.
Provide sign-in and get-started information to users to introduce your users to Oracle Content Management and let them know who to contact if they have questions.

Optionally, push the desktop app out to your users.

The desktop app keeps files and folders on your users' computers synchronized with the cloud. They can choose the folders in Oracle Content Management that they want to sync, including folders that are shared with them, so they always have access to the current versions of their content folders and assets. They can also add files and folders into their desktop folder, and they'll automatically be added to Oracle Content Management.

The desktop app also enables users to set notifications, letting them know when there's activity in conversations they participate in, and they can share files and folders, just like they do in the web interface.

To take your user experience even further, integrate Oracle Content Management with your other business applications, such as Oracle Process Cloud Service or custom applications.
Reference

Glossary
REST API
IP Address Allowlist



For more information click here https://docs.oracle.com/en-us/iaas/goldengate/doc/reference.html

For more information click here https://docs.oracle.com/en-us/iaas/disaster-recovery/doc/disaster-recovery-reference.html

For more information click here https://docs.oracle.com/en-us/iaas/Content/devops/using/reference.htm

For more information click here https://docs.oracle.com/en-us/iaas/digital-assistant/doc/reference.html

For more information click here https://docs.oracle.com/en-us/iaas/database-migration/doc/reference.html
Cloud Advisor settings


You can customize Cloud Advisor by postponing or dismissing recommendations and by customizing the logic that Cloud Advisor uses to make recommendations. Modify the recommendations based on your preferences and what works best for your workloads.

Cloud Advisor provides recommendations to help you maximize cost savings and improve the performance, security, and availability of your tenancy. However, you might want to customize recommendations for certain resources, postpone specific recommendations to review later, or dismiss recommendations entirely. Recommendation overrides and changes to recommendation overrides take effect the next time Cloud Advisor runs on your tenancy.

This section contains the following major topics:

Required IAM Policies
Profile Descriptions
Customizing Overrides
Profiles
Profile Levels
Scaling Node Pools

Using the Console
Using the API
Database Tools Policies


Create IAM policies to control who has access to the Database Tools Service and to control the type of access for each group of users.

If you are new to IAM policies, see Getting Started with Policies. See the Policy Reference for a complete list of policies in Oracle Cloud Infrastructure.

Topics:

Resource Types
For Oracle Database Connections
For MySQL Database Connections
Adding Authentication and Authorization to API Deployments


Find out how to add authentication and authorization functionality to API gateways with the API Gateway service.

You can control access to APIs you deploy to API gateways based on the API client sending a request, and define what it is that they are allowed to do. For the APIs you deploy, you'll typically provide:

Authentication functionality to determine an API client's identity. Is the API client really who they claim to be?
Authorization functionality to determine appropriate access for an API client, and grant the necessary permissions. What is the API client allowed to do?

You can add authentication and authorization functionality to API gateways to support:

HTTP Basic Authentication
API Key Authentication
OAuth Authentication and Authorization
Oracle Cloud Infrastructure Identity and Access Management (OCI IAM) with Identity Domains Authentication
Oracle Identity Cloud Service (IDCS) Authentication

You can add authentication and authorization functionality to an API gateway as follows:

You can have the API gateway pass a multi-argument or single-argument access token included in a request to an authorizer function deployed on OCI Functions to perform validation (see Passing Tokens to Authorizer Functions to Add Authentication and Authorization to API Deployments).
You can have the API gateway itself validate a JSON Web Token (JWT) included in the request with an identity provider (see Validating Tokens to Add Authentication and Authorization to API Deployments).

For convenience, these different types of authentication and authorization functionality are referred to as 'authentication servers'. You can set up multiple authentication servers for the same API deployment. The authentication servers you set up can be of the same type or a different type. Setting up multiple authentication servers for the same API deployment enables a request to be dynamically routed to the correct authentication server based on an element in the request. For more information, see Adding Multiple Authentication Servers to the same API Deployment
Known Issues for Data Integration

Success condition evaluation fails during running of a REST task
Changing an Identity Domain's Type


Upgrade an identity domain in IAM.

You can upgrade a domain by changing the domain type. Each identity domain type  is associated with a different set of features and object limits. For information to help you decide which domain type is appropriate for what you want to do, see IAM Identity Domain Types.

For more information for what validations to expect when changing domain types, see Changing your Identity Domain Type.

Console
CLI
API
Open the navigation menu and click Identity & Security. Under Identity, click Domains. Select the identity domain that you want to change. You might need to change the compartment to find the domain that you want.
Click Edit domain.
Under Domain type, click Change domains type.
Click the domain type to which you want to change.
Click Change domain type.
Click Save.
Access to Other VCNs: Peering

Important Implications of Peering
Troubleshoot
 Other Issues



For more information click here https://docs.oracle.com/en-us/iaas/goldengate/doc/troubleshoot.html
Creating a Migration Project

Creating a Simple Migration Project
Creating a Pipeline


Create a Data Science pipeline to run a task.

Ensure that you have created the necessary policies, authentication, and authorization for pipelines.

 Important



For proper operation of script steps, ensure that you have added the following rule to a dynamic group policy:

Copy
all {resource.type='datasciencepipelinerun', resource.compartment.id='<pipeline-run-compartment-ocid>'}

Before you begin:

Create a step artifact file.

Review the use of pipelines environment variables.

To store and manage pipeline logs, learn about logging.

Decide which conda environment you want to use. If you need a custom conda environment, create and publish one.

You can create pipelines by using the ADS SDK, OCI Console, or the OCI SDK.

Using ADS for creating pipelines can make developing the pipeline, the steps, and the dependencies easier. ADS supports reading and writing the pipeline to and from a YAML file. You can use ADS to view a visual representation of the pipeline. We recommend that you use ADS to create and manage pipeline using code.

Console
CLI
API
Use the Console to sign in to a tenancy with the necessary policies.
Open the navigation menu and click Analytics & AI. Under Machine Learning, click Data Science.
Select the compartment that contains the project that you want to use.

All projects in the compartment are listed.

Click the name of the project.

The project details page opens and lists the notebook sessions.

Under Resources, click Pipelines.
Click Create pipeline.
(Optional) Select a different compartment for the pipeline.
(Optional) Enter a name and description for the pipeline (limit of 255 characters). If you don't provide a name, a name is automatically generated.

For example, pipeline2022808222435.

Click Add pipeline steps to start defining the workflow for the pipeline.
In the Add pipeline step panel, select one of the following options, and then finish the pipeline creation:
From a Job
From a Script
 Expand All Expandable Areas
Troubleshooting DevOps

Deploying Applications to OKE
Vulnerability Audit Failure
Configuring Private Connection
Troubleshooting ADM


Use troubleshooting information to identify and address common issues that can occur while working with ADM.

 Tip

If the problem still persists or if the problem you're facing isn't listed, refer to the Getting Help section.
Connecting to a Windows Instance
 Using PowerShell
Configuration of a DB System


The configuration of a DB system is a collection of user, system, initialization, or service-specific variables that define the operation of a MySQL DB system. The configuration is linked to the shape you select for a DB system. MySQL HeatWave Service supports two types of configurations, default and custom configuration.

Overview of Configuration
Configuration Variables
Creating a Custom Configuration
Managing a Configuration
Viewing Configuration Details
Working with Virtual Nodes


Find out about virtual nodes, the differences between virtual nodes and managed nodes, and how to create virtual nodes using Container Engine for Kubernetes (OKE).

Virtual nodes provide a serverless Kubernetes experience, enabling you to run containerized applications at scale without the operational overhead of managing, scaling, upgrading, and troubleshooting the node infrastructure. Virtual nodes provide granular pod-level elasticity and pay-per-use pricing. As a result, you can scale deployments without taking into consideration the cluster's capacity, simplifying the execution of scalable workloads such as high-traffic web applications and data-processing jobs. You create virtual nodes by creating virtual node pools in enhanced clusters.

By contrast, managed nodes are OCI Compute instances running in your tenancy that you control and configure, with a shared operational responsibility. Container Engine for Kubernetes provisions and updates the Kubernetes software on managed nodes. For a detailed comparison of virtual nodes and managed nodes, see Comparing Virtual Nodes with Managed Nodes.

Virtual nodes provide you with the flexibility to satisfy application requirements. You can control the Kubernetes pod placement based on an availability needs, selecting the Compute processor shape, CPU, and memory most suited for an application. Hypervisor-level isolation for pods enables you to run any type of application on virtual nodes, including untrusted workloads.

Container Engine for Kubernetes with virtual nodes delivers seamless upgrades of Kubernetes clusters. The Kubernetes software is upgraded and security patches are applied while respecting application availability requirements.

Virtual nodes enable you to optimize the cost of running Kubernetes workloads. You pay for the exact compute resources consumed by each Kubernetes pod instead of paying for whole servers that might have unused capacity.
Overview of Full Stack Disaster Recovery


Learn about terminology, concepts, and benefits of Full Stack Disaster Recovery.

About Full Stack Disaster Recovery
Full Stack DR is an Oracle Cloud Infrastructure (OCI) disaster recovery orchestration and management service that provides comprehensive disaster recovery capabilities for all layers of an application stack, including infrastructure, middleware, database, and application.
Benefits of Full Stack Disaster Recovery
Full Stack DR provides multiple benefits in the area of business continuity.
Full Stack Disaster Recovery Terminology and Concepts
Before using Full Stack DR, familiarize yourself with the following key terms and concepts.
Governance

Goal
Roles
Implementation
Additional Considerations
Constraints and Blockers
Next Steps
Using Configurations


Learn how to use the configurations.

The Configuration page displays in each column the RFC No., scheduling details, RFC status, intermediate statuses, and customer update.

To create config RFC:

In the dashboard, click the hamburger menu ( three horizontal lines) at the top-left corner.
From the navigation pane, click Configurations.
In the Configurations page, click Initiate Config.
For Config Type, select Trace & Debug.
For Activity Name, select either of the following:
FRD Enable/Disable
FND Enable/Disable
For Activity Type, select Enable.
Select a Target.
For Summary, optionally enter a summary of this RFC.
Select Auto Disable Interval to schedule the disable activity time gap.
In the Activity Based Inputs section, enter the UserName.
If FND Enable/Disable is selected, enter Debug Log Module, and select Debug Log Level.
Select the Accept Risk check box.
Click Customer Note to add an action plan or any other relevant information you want included in the RFC.
Click Submit.

The Schedule Execution popup opens.

If you click Not Now, you will be returned to the listings in the Configurations page.
If you click Yes, the RFC will be scheduled for execution in 15 minutes.
If you click Pick Future, you will be taken to the scheduling Details page.
From the Configurations page, click the RFC from the listings.
In the Details page, click the Logs to view the logs.
To view the Activity Name Parameter, click the Information icon in the Activity Name text box.
Resource Discovery and Monitoring
 provides the following features:

Process-based auto-discovery and monitoring of state, CPU Utilization (%), Memory Utilization (%) of the following resource types:
Oracle Database
MySQL Database
Listener
WebLogic Server
Oracle HTTP Server
Apache Server
Tomcat
Metric history, Alarms, and Notifications using OCI monitoring platform
Monitor Top Processes (by CPU or Memory) or show Top Processes on-demand
Artifact Registry Concepts

Repository and Artifact Names in Artifact Registry
Immutable Artifacts in Artifact Registry
Artifact States in Artifact Registry
Identifying Artifacts with Secure Hash in Artifact Registry
Function Metrics

Overview of the OCI Functions Service Metrics
Prerequisites
Available Metrics: oci_faas
Using the Console
Using the API
Get an Oracle Cloud Account


The first step to get started with Oracle Cloud is to get an account.

Request and Manage Free Oracle Cloud Promotions
Buy an Oracle Cloud Subscription
Allowing Access to the Console from Your Network


Firewalls, proxy servers, and other devices that your network administrators use to control access to the internet can affect your ability to connect to the Console.

To allow network access to the Console, your network administrator must add the following URLs to the allowlist of your firewall or proxy server:

Copy
*.oracle.com
*.oraclecloud.com
*.oracleinfinity.io
oracle.112.2o7.net
consent.trustarc.com (Console cookie preferences)
 Note

Communication with the Console uses the standard TCP ports for HTTP (80) and HTTPS (443).
Renaming a Cloud Account and Tenancy


Learn about renaming a cloud account and tenancy.

 Important

This functionality is currently unavailable.
CEMLI API Specifications


Learn about the supported CEMLI API specifications.

The following CEMLI API specifications are supported:

CEMLI Execution API Specifications
CEMLI File API Specifications
CEMLI Metadata API Specifications
CEMLI Patch API Specifications
CEMLI Product API Specifications
CEMLI Service API Specifications
CEMLI User API Specifications
Oracle Maximum Availability Architecture in Oracle Cloud Infrastructure


Learn about Oracle Maximum Availability Architecture in OCI.

Oracle Maximum Availability Architecture (MAA) is a set of best practices developed by Oracle engineers over many years for the integrated use of Oracle High Availability, data protection, and disaster recovery technologies. The key goal of Oracle MAA is to meet recovery time objectives (RTO) and recovery point objectives (RPO) for Oracle databases and applications running on Oracle systems and database platforms using Oracle Cloud MAA.

See High Availability Overview and Best Practices for detailed information about the validated Oracle MAA benefits inherent to Autonomous Database and all Exadata cloud systems, and best practices to achieve minimal or zero application and database downtime across various cloud lifecycle operations.
Refreshing an Environment

Environment Refresh Requirements and Limitations
What's Copied During an Environment Refresh
Environment Refresh Duration
Environment Refresh Management Tasks