Oracle Fusion AI Agent Studio: Agent Migration Process

In this blog we will understand the process of migrating AI Agents from one environment to the other in Fusion AI Agent Studio. This process was introduced starting with 26A release and helps us export/import individual AI agents as needed.

I've also covered some of the observations/shortcomings in this process based on my experience. Hope they help the readers.

The steps below describe the Export/Import process for an AI Agent starting from 26A.

Export AI Agent from the Source environment

1. In Source instance:

Navigate to Tools -> AI Agent Studio

Go to AI Agent Studio -> Agent Teams

2. From the Agent Teams tab, locate the agent team you want to export and click the download icon

 
3. While exporting an AI Agent, we need to enter below details:

Partner Name: <Company Name>

Description: Agent description

Partner Image: <Company Logo>

 

In the Preview section we can se how our agent would look like:

4. Once the export details are entered, verify details shown in Preview section and click Export to download the JSON file to your local system. 

5. In above example, the exported file would be 'BENEFITS_POLICY_ADVISOR.json'.

We can open the .JSON file and inspect if it exported all the desired details from the source environment:

Import AI Agent into the Target environment

1. Go to the target environment.

2. Navigate to AI Agent Studio -> Agent Teams

3. Click Import button.

 

4. Select the downloaded JSON file and click Open.

 

5. Once the AI Agent is imported, it can be found under Draft tab. The version of the imported agent gets reset to 1.

6. Use the Edit button to edit the imported agent team.

7. Publish the agent team after making the necessary configurations.

Export/Import Observations

Post-import manual steps (Official list mentioned by Oracle):

- Document tool: Upload and republish the document to ensure its content is correctly processed in the new environment.

- Email tool: Reconfigure the email tool to make sure necessary alerts are generated properly in the new environment.

- External REST tool: Reconfigure authentication settings for external REST API tools.

Additional observations based on my testing:

- This process exports and retains the LLM configuration/assignments for the agent. No reconfiguration needed in this case.

- It doesn't export Security configurations/role assignments for the agent. Needs manual reconfiguration/assignment upon import.

- It exports and retains the Questions (3 custom questions) as expected. No reconfiguration needed in this case.

- The Import process doesn't ask if you want to overwrite, in case the agent already exists. My existing agent version was 7 and upon reimporting it was reset to 1 in the Draft area.

- We need to mention Partner details (Name, agent description and even upload company Logo) during export.

This seems like a good way of branding as the agent shows company name and logo during export.

It’s a good feature that will help end users in identifying our own custom agents.

But I observed that the Company Name and Logo doesn’t appear anywhere upon import, or even after publishing the imported agent.

The branding information is not shown anywhere in AI Agent Studio or on the tiles in AI Chat section.

- Document tool loses the actual document - This is expected since Oracle has already published this behavior.

- All above points apply for Export/Import of a seeded agent as well as a fully custom agent (no difference in behavior).

- All above points apply for Export/Import of a Published agent as well as a Draft agent (no difference in behavior).

- Irrespective of the status of an agent in the source environment (Draft or Published) was, it goes in a Draft status in the target environment upon import.