How Robot Connections Work for Multiple Instances

Pre-General Availability: 2024-09-02

How Robot Connections Work for Multiple Instances

You might have multiple instances of Oracle Integration and of the applications that your robots connect to. Learn how to optimize your workflow for each scenario.

Multiple Oracle Integration Instances

Factor to consider	More information
Building an automation solution in a development environment	You can build and test your robot in one or more lower Oracle Integration environments without impacting your production environment.
Deploying an automation solution to a higher environment	Use the built-in capabilities in a project to seamlessly deploy an automation solution, including robots and integrations, to a higher environment, such as a production environment. When you promote a solution to a higher environment, the values in the integration and robot connections are removed. For security reasons, Oracle Integration doesn't include sensitive data, such as passwords, in deployment packages. You likely need to provide different values for a higher environment, anyway. For example, the robot must work in a production instance, which might have a different URL and different credentials.
Updating an automation solution when a robot's credentials change	The password that a robot uses is sensitive information. Often, one person builds a robot and another person enters these credentials. When a robot's password changes, only the robot connection needs to be updated. You don't need to open or update the robot to make this change. If a robot has already been deployed to a production environment, you can update the password directly in the production environment.

Factor to consider

More information

Building an automation solution in a development environment

You can build and test your robot in one or more lower Oracle Integration environments without impacting your production environment.

Deploying an automation solution to a higher environment

Use the built-in capabilities in a project to seamlessly deploy an automation solution, including robots and integrations, to a higher environment, such as a production environment.

When you promote a solution to a higher environment, the values in the integration and robot connections are removed. For security reasons, Oracle Integration doesn't include sensitive data, such as passwords, in deployment packages. You likely need to provide different values for a higher environment, anyway. For example, the robot must work in a production instance, which might have a different URL and different credentials.

Updating an automation solution when a robot's credentials change

The password that a robot uses is sensitive information. Often, one person builds a robot and another person enters these credentials.

When a robot's password changes, only the robot connection needs to be updated. You don't need to open or update the robot to make this change.

If a robot has already been deployed to a production environment, you can update the password directly in the production environment.

Multiple Instances of the Application That a Robot Automates

Factor to consider	More information
Building and testing an automation solution against a development instance	While you're building and testing a robot and its integration, point to the development instance of the application. Identify any differences between the development and production instances of the application. These differences could impact the robot's behavior in production. For instance, sometimes new features are deployed to a development environment first.
Pointing to a higher environment after deployment to production	After you deploy an automation solution to a production environment of Oracle Integration, update the connections so that they point to the production instance of the application.

Factor to consider

More information

Building and testing an automation solution against a development instance

While you're building and testing a robot and its integration, point to the development instance of the application.

Identify any differences between the development and production instances of the application. These differences could impact the robot's behavior in production. For instance, sometimes new features are deployed to a development environment first.

Pointing to a higher environment after deployment to production

After you deploy an automation solution to a production environment of Oracle Integration, update the connections so that they point to the production instance of the application.