Manage an Environment
After creating an environment and adding instances to it, you can manage its instances, as shown here:
Action | How To |
---|---|
Edit an environment's name and description |
In the Details tab, click Edit. Edit the details and click Save. |
Refresh a service instance's status |
In the Service Instances tab, mouse-over the instance, click Actions |
Check a service instance's response time | The Response Time provides information about the instance:
|
Edit a service instance's credentials | When your instance is set up for Basic authentication, mouse-over the Oracle Cloud Applications, Visual Builder, or Integration instance in the Service Instances tab, click Actions ![]() |
Renew a service instance's OAuth access | When your instance is set up for OAuth authentication, OAuth tokens (access and refresh) are cycled during regular use. A refresh token is used to obtain an access token whenever a user accesses the target instance. This refresh token is typically valid for seven days. (The token expiration time is set in the IDCS resource app and may be different based on your security requirements.) If the user authenticates with the target instance within the seven-day period, the active refresh token generates a new access token and a new refresh token. This cycle continues indefinitely as long as the refresh token stays valid. If the refresh token expires during extended periods of inactivity (say, when you're away on vacation), mouse-over the Oracle Cloud Applications, Visual Builder, or Integration instance in the Service Instances tab, click Actions ![]() Note: Service administrators can control the OAuth access or refresh token's expiration in the IDCS resource app. For example, to change this for your Oracle Cloud Applications instance, you'd look for theFusion Applications Cloud Service resource app under Oracle Cloud Services in your identity domain's resource app. See Edit High-Level Information for Oracle Applications.
|
Remove an instance from an environment |
In the Service Instances tab, mouse-over the instance, click Actions An instance can't be removed if it's associated with any workspace. If you try, an error message displays, listing the impacted users and the number of workspaces they have. You'll be instructed to ask those users to delete their workspaces. Once this has been done, you can go back and retry the Remove operation. Note: An IDCS resource cannot be removed from an environment if the instance is in another identity stripe. Nobody can remove an IDCS resource from a different identity stripe from an environment, but the project owner can still delete the entire environment. In addition, an IDCS resource from a second identity stripe cannot be added into the same environment. |
Delete an environment |
In the environments list, mouse-over the environment, click Actions Remember that the environment's instances won’t be deleted. An environment can't be deleted if it's associated with any workspaces. If you try, you'll see an error message listing the impacted users and the number of workspaces they have. You'll be instructed to ask those users to delete their workspaces. After they do that, you can go back and try to delete the environment again. Note: Project owners are the only project team members who can delete environments that were created in a different identity stripe. If a project member with the Developer role attempts this operation, they'll see an error message informing them that they can't delete an environment that has resources from another identity stripe. |