All about Autoconfig in oracle application:

 adautocfg.sh >> Call adconfig.sh which further call adconfig.pl.

adtmplreport.sh>>

[applmgr3@ ~]$ cd $AD_TOP/bin

[applmgr3@1 bin]$ ls adtmplreport.sh

[applmgr3@ bin]$ adtmplreport.sh contextfile=$CONTEXT_FILE target=/u03/applmgr3/inst/apps/PROD_xxx/ora/10.1.3/Apache/Apache/conf/httpd.conf.

adclonectx.pl >>To retrieve the applications tier context file ( if it is lost or deleted accidentally) , execute the following command on the applications tier :

perl <COMMON_TOP>/clone/bin/adclonectx.pl retrieve

adbldxml.sh >>Creates the Applications context file, e.g. .xml

adchkcfg.sh >>script at $AD_TOP/bin. This script will run autoconfig in test mode and create the difference file which tells us what is going to change, when u actually run autoconfig.

This script is used for analysis purpose. It generates a report that shows differences between the original configuration files and the AutoConfig generated configuration files. 

Autoconfig will run in 3 phases.

1.INIT     – Instantiate the drivers and templates

2.SETUP   – Fill the templated with values from xml and create files

3.PROFILE  – Update the profile values in database.

Log/Files Location:

$INST_TOP/appl/admin >> context file location.

$INST_TOP/admin/log  >> autoconfig log file.

Restore a autoconfig :

Partially. Adconfig will create a restore script at $INST_TOP/admin/out/. This restore.sh will copy the backed up files before autoconfig run to its original locations. But the profile values updated in the database can’t be restored back.

Customization:

The way to do customization was to insert custom code between the BeginCustomization and End Customization blocks in the XML file.

It was difficult todocument and keep track of the customizations that were made. Now Oracle hascome up with a better way to manage and maintain customizations.

Create the custom directory in $PROD_TOP/admin/template

$AD_TOP/bin/adtmplreport.sh contextfile=/appl/admin/.xml

target=$FND_TOP/admin/template/appsweb.cfg

The above command would return "$FND_TOP/admin/template/forms_web_1012_cfg.tmp", means

the "appsweb.cfg" file was created from the source Autoconfig template $FND_TOP/admin/template/forms_web_1012_cfg.tmp.

Copy the "forms_web_1012_cfg.tmp" into custom directory created earlier  and then edit it to your requirements

Copy the template $FND_TOP/admin/template/forms_web_1012_cfg.tmp  to  $FND_TOP/admin/template/custom

Where to Find Your Tenancy's OCID:

Get the tenancy OCID from the Oracle Cloud Infrastructure Console on the Tenancy Details page:

1.Open the navigation menu, under Governance and Administration, go to Administration and click Tenancy Details.

2.The tenancy OCID is shown under Tenancy Information. Click Copy to copy it to your clipboard.

The tenancy OCID looks something like this (notice the word "tenancy" in it):

ocid1.tenancy.oc1..<unique_ID>

Identity and Access Management (IAM) in Oracle Cloud Infrastructure

IAM Service Components :

1.Resource:
A cloud object that your company's employees create and use when interacting with Oracle Cloud Infrastructure. Resources include compute instances, block storage volumes, virtual cloud networks (VCNs), subnets, and route tables.

2.User:
An individual employee or system that needs to manage or use your company's Oracle Cloud Infrastructure resources. Users might need to launch instances, manage remote disks, work with your virtual cloud network, and so on.

3.Group:
A collection of users who all need the same type of access to a particular set of resources
or compartment.

4.Compartment

5.Tenancy

6.Policy:
A document that specifies who can access which resources, and how. Access is granted at the group level and compartment level, which means that you can write a policy that gives a group a specific type of access within a specific compartment, or to the tenancy itself. If you give a group access to the tenancy, the group automatically gets the same type of access to all the compartments inside the tenancy.

7.Home Region:
The region where your IAM resources reside. All IAM resources are global and available across all regions, but the master set of definitions resides in a single region, the home region. You make changes to your IAM resources in your home region, and the changes are automatically propagated to all regions.