{"id":1838,"date":"2023-05-03T03:29:23","date_gmt":"2023-05-03T03:29:23","guid":{"rendered":"https:\/\/people.utm.my\/azhari\/?p=1838"},"modified":"2023-05-03T03:29:25","modified_gmt":"2023-05-03T03:29:25","slug":"overview-of-managing-applications-environments","status":"publish","type":"post","link":"https:\/\/people.utm.my\/azhari\/2023\/05\/03\/overview-of-managing-applications-environments\/","title":{"rendered":"Overview of Managing Applications Environments"},"content":{"rendered":"\n
\n

Applications Environment Management Concepts<\/h2>\n
\n

Here are some terms you may encounter when creating or managing an applications environment. Because the environments are running on Oracle Cloud Infrastructure, it is helpful to understand some basics about the features of OCI.<\/p>\n

\n
ENVIRONMENT TYPE or INSTANCE TYPE<\/dt>\n
The environment or instance type options will vary depending on the application.<\/dd>\n
Oracle Maymiser, offers INSTANCE TYPES and provides the instance type options of Maxymiser and Recommendations.<\/dd>\n
Some applications provide PRODUCTION and NON-PRODUCTION environment or instance types.<\/dd>\n
The PRODUCTION environment supports your day-to-day real-time business operations by authorized users.<\/dd>\n
Test and development environments are both NON-PRODUCTION environments. The test environment is typically used for staging before application deployment to production and for validation of maintenance updates before the same maintenance is applied to the production environment. Development environments (also referred to as Additional Test Environments or ATEs) are typically used as individual or collaborative development sandboxes for developing extensions (such as reporting, pages, and interfaces) or integrations with other applications. The number and types of environments allotted to your tenancy depend on your order.<\/dd>\n
REGION<\/dt>\n
\n

A region is where your environments are physically<\/em> hosted. This region is not the same as the geographical region that you selected on your subscription order.<\/p>\n<\/dd>\n

COMPARTMENT<\/dt>\n
\n

Compartments are a fundamental component of OCI for organizing and isolating your cloud resources. You can use them to logically separate resources for the purposes of measuring usage and billing, access (through the use of policies), and isolation (separating the resources for one project or business unit from another). For example, if you need to grant access to one group of users to your test environment and another group of users to your production environment, you can assign your test and production environments to different compartments. For more information, see Understanding Compartments<\/a>.<\/p>\n<\/dd>\n

IDENTITY AND ACCESS MANAGEMENT (IAM)<\/dt>\n
IAM<\/span> is the service that provides authentication and authorization for OCI resources. You interact with the IAM service when you create users, groups, and policies to manage your applications environments.<\/dd>\n
POLICY<\/dt>\n
OCI IAM<\/span> uses policies to specify who can access which resources. Access is granted at the group and compartment level, which means 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. For more information, see Getting Started with Policies<\/a>.<\/dd>\n
RESOURCE IDENTIFIERS or OCIDs<\/dt>\n
\n

Applications environment management supports environments as Oracle Cloud Infrastructure resources. Most types of resources have a unique, Oracle-assigned identifier called an Oracle Cloud ID (OCID). For information about the OCID format and other ways to identify your resources, see Resource Identifiers<\/a>.<\/p>\n<\/dd>\n<\/dl>\n<\/div>\n<\/article>\n

\n

Authentication and Authorization<\/h2>\n
\n
\n

Applications environment management uses the Oracle Cloud Infrastructure<\/span> IAM<\/span> service for authentication and authorization.<\/p>\n

An administrator in your organization needs to set up groups\u00a0<\/strong><\/p>\n<\/div>\n<\/div>\n<\/article>\n

and policies\u00a0<\/strong><\/p>\n

that control which users can access which services and resources. For example, to allow other users to manage applications environments you’ll need to create a group for these users and write a policy that grants the group access to the applications environments. If your organization will be using other OCI services, you’ll need to write policies specifically for those services.<\/p>\n