Package com.oracle.database.selectai.agent

Interface Team

public interface Team
Contract for Select AI agent team lifecycle, orchestration, and definition management operations.

A team is a database-side resource managed by the DBMS_CLOUD_AI_AGENT PL/SQL package. Teams coordinate agents and can run multi-agent workflows using their configured members and attributes.

A Team instance can represent an existing database team or be configured for creation. The name-only SelectAIAgent.team(String) factory verifies that the team exists and loads its metadata and attributes before returning. SelectAIAgent.listTeams() also returns handles with loaded metadata and attributes. A handle configured for creation is obtained with SelectAIAgent.team(String, TeamAttributes, String, TeamStatus). A granted team owned by another user can be run by its qualified name via SelectAIAgent.runTeam(String, RunTeamRequest); that path does not create a Team handle or expose owner-only metadata.

A creation-configured handle retains its supplied attributes, description, and status without querying the database. Only such a handle can call create(); after creation succeeds, it becomes database-backed. enable(), disable(), drop(boolean), orchestration, state, and export operations require an existing database-side team. Existing teams can update individual attributes with setAttribute(String, String) or multiple attributes with setAttributes(TeamAttributes); both operations reload the typed attributes after the database update succeeds.

Before creation, getStatus() and getTeamAttributes() return the configured values. For a database-backed handle, each call to either method queries the database. getStatus() does not change the description returned by getDescription(). The description is supplied or loaded when the handle is initialized; getDescription() does not query the database. Methods such as describe() and getStateByConversationId(String) retrieve other database-side information.

Names and required Java arguments are checked locally. Loading metadata and executing team operations require database access; the database checks privileges and validates team attributes when they are submitted. Team execution and state-management payloads must conform to the formats accepted by the database package.

For a complete runnable example, see CreateTeamSample source. For an end-to-end example that creates the resources needed by a team, runs it, and continues the same database conversation, see AgentWorkflowSample source. For a supervisor agent coordinating separate worker-task mappings, see SupervisorTeamSample source.

Since:
1.1.0
See Also: