5 Enable and Disable Operations Assistant

Use the Operations Assistant lifecycle scripts to add the feature to an existing Oracle TSAM Plus installation, disable it without removing its resources, or re-enable a disabled installation.

Note:

Do not rerun TSAMSetup.sh against an existing installation. It is intended for a fresh or full-recreate deployment. Use TSAMEnableAI.sh and TSAMDisableAI.sh for lifecycle changes.

• Choose the Correct Operation
  
• Prerequisites
  
• Enable Operations Assistant
  
• Disable Operations Assistant and Preserve Its Resources
  
• Re-enable Operations Assistant
  

5.1 Choose the Correct Operation

Operation	Command	When to Use It
Install and Enable	TSAMEnableAI.sh	Operations Assistant has not been installed in this TSAM Plus environment. The command creates the AI-specific resources and enables the feature.
Resume Installation	TSAMEnableAI.sh -resume	The initial enable stopped after the AI database user was created. The command preserves that user and retries the remaining setup.
Disable and Preserve	TSAMDisableAI.sh	Temporarily stop new Operations Assistant requests while preserving the AI resources and chat history.
Re-enable Preserved Resources	TSAMEnableAI.sh -activateOnly	Operations Assistant was disabled with TSAMDisableAI.sh. The command validates the preserved resources and enables the feature again.

5.2 Prerequisites

This procedure requires Oracle TSAM Plus 22c RP001 or above. Apply the required rolling patch and complete its application and database upgrade before using the lifecycle scripts. The scripts do not upgrade or redeploy an older installation.

Follow these steps before enabling or re-enabling Operations Assistant:

1. Ensure SQL*Plus is available in PATH.
2. Ensure the existing WebLogic AdminServer is running.
3. Complete the database, network, wallet, and ACL prerequisites for the selected AI provider and knowledge source.
4. Configure the existing database and WebLogic connection values, AI provider, model, credentials, and vector source in $TSAMDIR/deploy/TSAMSetup.cfg.

Note:

TSAM_ENABLE_AI controls the fresh or full deployment wrapper only. The lifecycle scripts do not use this setting. Password values in TSAMSetup.cfg are not consumed; SQL*Plus and WebLogic prompt for passwords.

5.3 Enable Operations Assistant

Use this procedure when you enable the Operations Assistant for the first time in the existing TSAM Plus environment.

cd $TSAMDIR/deploy 
bash ./TSAMEnableAI.sh 

To use a configuration file in another directory:

bash ./TSAMEnableAI.sh -config /path/to/TSAMSetup.cfg 

The command validates the AI configuration before making changes. It then:

1. Places Operations Assistant in the disabled state.
2. Creates the AI database user without recreating the primary TSAM database user.
3. Adds the AI metadata and Select AI resources without rebuilding the core TSAM schema.
4. Creates the TSAM_DS2 WebLogic data source.
5. Validates the primary schema, AI schema, and AI data source.
6. Enables Operations Assistant after all checks succeed.

The command does not rebuild the WebLogic domain, redeploy the TSAM Plus EAR file, recreate the core TSAM schema, or delete existing chat data. If any setup step fails, Operations Assistant remains disabled.

Tip:

If the AI database user was created but a later setup step failed, correct the reported problem and run:

cd $TSAMDIR/deploy
  bash ./TSAMEnableAI.sh -resume

The command preserves the existing AI database user and retries the remaining setup and validation. If AI database user creation failed, correct the problem and run TSAMEnableAI.sh without -resume.

5.4 Disable Operations Assistant and Preserve Its Resources

Use the following command to disable the AI Operations Assistant feature.

cd $TSAMDIR/deploy 
bash ./TSAMDisableAI.sh 

The command preserves the AI database user, TSAM_DS2 data source, credentials, profiles, vector indexes, agent objects, grants, user settings, and chat history. New Operations Assistant requests are rejected while the feature is disabled. A request that is already running is not forcibly cancelled.

To use another configuration file:

bash ./TSAMDisableAI.sh -config /path/to/TSAMSetup.cfg 

5.5 Re-enable Operations Assistant

Use this procedure only after Operations Assistant was disabled with TSAMDisableAI.sh.

cd $TSAMDIR/deploy 
bash ./TSAMEnableAI.sh -activateOnly 

The command validates the preserved primary-schema resources, AI-schema resources, and the existing TSAM_DS2 data source before enabling the feature. It does not create or replace missing resources.

Note:

For a LOCAL installation, keep AI_VECTORINDEX_SOURCE_MODE=LOCAL in TSAMSetup.cfg. Use -resume, not -activateOnly, when recovering from an incomplete initial installation.