Advanced Deployment Options

4 Advanced Deployment Options

You can also use the individual deployment scripts for advanced deployment options.

New Installation and Deployment

The new installation and deployment flow is as follows:

Follow the instructions in section Database Deployment to deploy the TSAM Plus database.
Follow the instructions in section WebLogic Server Deployment to provision the WebLogic Server domain and deploy the TSAM Plus application.
Optionally, follow the instructions in the Enable and Disable Operations Assistant to enable Operations Assistant.

Upgrade from TSAM Plus 12.2.2.0.0

When upgrading from TSAM Plus 12.2.2.0.0:

TSAM Plus 12.2.2.0.0 RP07 or above must be applied to the existing TSAM Plus 12.2.2.0.0 installation.
TSAM Plus 22.1.0.0.0 RP001 or above is required for the TSAM Plus 22.1.0.0.0 installation.

The typical upgrade flow is as follows:

1. Follow the instructions in section Upgrade from TSAM Plus 12.2.2.0.0 Database to upgrade the TSAM Plus database.

2. Follow the instructions in section WebLogic Server Deployment to provision the WebLogic Server domain and deploy the TSAM Plus application.

3. Optionally, follow the instructions in chapter Enable and Disable Operations Assistant to enable Operations Assistant.

This section contains the following topics:

4.1 Database Deployment

This section contains the following topics:

Parent topic: Advanced Deployment Options

4.1.1 Provision a Database User

Oracle TSAM Plus Manager requires a dedicated Oracle database user.

The shell script TSAMDBUserProvision.sh is to be used by your database system administrator to create a dedicated database user with the required privileges.

Parent topic: Database Deployment

4.1.1.1 Usage

./TSAMDBUserProvision.sh -connStr <connection string> -adminUser <admin username> -user <new user> -tablespace <tablespace>\
 [-adb] [-walletDir <path to DB wallet>] [-dropUser] [-quota <quota limit>] [-enableAI] [-aiUser <new aiUser>] [-aiSourceMode <CLOUD|LOCAL>]

Table 4-1 Parameter List

Name	Description
`-connStr` <connection string>	DB connection string. If the connection string contains spaces or special characters like parentheses, enclose it in double quotes.
`-adminUser` <admin username>	The administrative user with privileges to create users.
`-aiSourceMode <CLOUD\|LOCAL>`	Optional. Specifies the AI source mode. The default value is CLOUD. LOCAL is supported only for non-ADB deployments.
`-user` <new user>	The name of the new database user to be created.
`-tablespace` <tablespace>	The tablespace for the new user.
`-adb`	(Optional) Flag to indicate Autonomous Database.
`-walletDir` <path to DB wallet>	(Optional) Path to the wallet directory.
`-dropUser`	(Optional) Drop the user if it already exists, then recreate.
`-quota` <quota limit>	(Optional) Quota for the user on the tablespace. Examples: 100M, 1G, UNLIMITED. Default is UNLIMITED if not provided.
`-enableAI`	(Optional) Flag to grant Select-AI related privileges (DBMS_CLOUD, DBMS_CLOUD_AI, etc.). This requires the Oracle TSAM Plus AI-based Operations Assistant feature.
`-enableAI -aiUser <new aiUser>`	Required when `-enableAI` is set. The database user used for TSAM Plus AI-based Operations Assistant. Note: Before running TSAMDBSchemaSetup.sh with `-enableAI`, set `AI_VECTORINDEX_SOURCE_MODE` in TSAMSetup.cfg. TSAMDBSchemaSetup.sh does not accept `-aiSourceMode` as a command-line parameter.
`-h or -help`	(Optional) Show help message.

Parent topic: Provision a Database User

4.1.1.2 Examples

To provision a database user on an on-prem Oracle database server:

./TSAMDBUserProvision.sh -connStr "hostname:1521/orclpdb1" -adminUser sys -user tsamuser1 -tablespace USERTABLESPACE -dropUser -quota 100G

To provision a database user on an Oracle Autonomous Database in Oracle Cloud:

./TSAMDBUserProvision.sh -connStr "(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1521)(host=adb.oraclecloud.com))(connect_data=(service_name=tsam22c.adb.oraclecloud.com))(security=(ssl_server_dn_match=yes)))"  -adminUser admin -user tsamuser1 -tablespace DATA -adb

To provision a database user on an Oracle Autonomous Database in Oracle Cloud with the AI feature enabled:

./TSAMDBUserProvision.sh -connStr "(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1521)(host=adb.oraclecloud.com))(connect_data=(service_name=tsam22c.adb.oraclecloud.com))(security=(ssl_server_dn_match=yes)))"  -adminUser admin -user tsamuser1 -tablespace DATA -adb -enableAI -aiUser tsamuser2

Parent topic: Provision a Database User

4.1.2 Set up Operations Assistant Knowledge Base

This step is only required if you want to use the AI-based Operations Assistant feature in Oracle TSAM Plus.

Oracle TSAM Plus Operations Assistant depends on the Oracle Tuxedo and Oracle TSAM Plus knowledge bases to achieve certain features.

Set AI_VECTORINDEX_SOURCE_MODE in TSAMSetup.cfg before running the AI deployment flow.

Use CLOUD to use the product-owned built-in documentation source. This is the default mode. Operators do not configure a document-source URL in TSAMSetup.cfg.

Use LOCAL to use Oracle DIRECTORY-backed sources on the database host. LOCAL is supported only when DB_IS_ADB=N in the current full-wrapper flow.

Parent topic: Database Deployment

4.1.2.1 Usage

For LOCAL mode, copy the source files to all three database-host directories:

/u02/tsam_ai/userdoc
/u02/tsam_ai/consoledoc
/u02/tsam_ai/followupdoc

To mirror the shipped CLOUD source, download the files from:

Parent topic: Set up Operations Assistant Knowledge Base

4.1.2.2 Example

CLOUD Example:

AI_VECTORINDEX_SOURCE_MODE="CLOUD"

LOCAL Example:

AI_VECTORINDEX_SOURCE_MODE="LOCAL"

Parent topic: Set up Operations Assistant Knowledge Base

4.1.3 Set up Database Schema

The shell script TSAMDBSchemaSetup.sh is to be used to create database assets for Oracle TSAM Plus Manager.

Parent topic: Database Deployment

4.1.3.1 Usage

./TSAMDBSchemaSetup.sh -connStr <connection string> -user <username> \  
  [-enablePartition] [-walletDir <dir>] \ 
  [-enableAI -aiUser <aiusername>]

Table 4-2 Parameter List

Name	Description
`-connStr` <connection string>	DB connection string. If the connection string contains spaces or special characters like parentheses, enclose it in double quotes.
`-user` <user name>	The name of the TSAM database user.
`-enablePartition`	(Optional) Flag to enable partitioning in database.
`-walletDir` <path to DB wallet>	(Optional) Path to the wallet directory.
`-enableAI`	Flag to enable AI setup (credentials, profile, agent, and metadata). You must configure the values in `TSAMSetup.cfg` file. Note: Before running TSAMDBSchemaSetup.sh with `-enableAI`, set `AI_VECTORINDEX_SOURCE_MODE` in TSAMSetup.cfg. TSAMDBSchemaSetup.sh does not accept `-aiSourceMode` as a command-line parameter.
`-aiUser <AI username>`	(Optional) The name of the TSAM database AI user when `-enableAI` is set. The target schema must own no tables, and `-aiUser` is required whenever `-enableAI` is used.
`-h or -help`	(Optional) Show help message.

Parent topic: Set up Database Schema

4.1.3.2 Examples

To set up database schema for an on-prem Oracle database server:

Use either a shell continuation character after -connStr or keep the connection descriptor on the same line. For example:

./TSAMDBSchemaSetup.sh -connStr "hostname:1521/orclpdb1" -user tsamuser1

To set up database schema for an Oracle Autonomous Database in Oracle Cloud, with partitioning enabled:

./TSAMDBSchemaSetup.sh -connStr "(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1521)(host=adb.oraclecloud.com))(connect_data=(service_name=tsam22c.adb.oraclecloud.com))(security=(ssl_server_dn_match=yes)))" -user tsamuser1 -enablePartition

To set up database schema for an Oracle Autonomous Database in Oracle Cloud, with AI feature enabled:

  ./TSAMDBSchemaSetup.sh -connStr "(description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1521)(host=adb.oraclecloud.com))(connect_data=(service_name=tsam22c.adb.oraclecloud.com))(security=(ssl_server_dn_match=yes)))" -user tsamuser1 -enableAI -aiUser tsamuser2

Note:

If the TSAMDBSchemaSetup.sh script fails, rerun TSAMDBUserProvision.sh with the -dropUser parameter to restart the database user provisioning process from scratch.

Parent topic: Set up Database Schema

4.1.4 Upgrade from TSAM Plus 12.2.2.0.0 Database

The TSAMDBSchemaUpgrade.sh script is used to perform an in-place upgrade of the TSAM Plus user schema in Oracle Database.

The Oracle Database version must be supported by TSAM Plus 22.1.0.0.0. If TSAM Plus 12.2.2.0.0 is running with an older Oracle Database version, upgrade Oracle Database to a version supported by TSAM Plus 22.1.0.0.0 before performing the TSAM Plus upgrade. See Prerequisites for details.

Parent topic: Database Deployment

4.1.4.1 Usages

./TSAMDBSchemaUpgrade.sh -connStr <connection string> -user \ 
 <username> [-walletDir <dir>] [-y]

Name	Description
`-connStr`	DB connection string. If the connection string contains spaces or special characters like parentheses, enclose it in double quotes.
`-user`	The existing TSAM Plus Manager 12.2.2 database schema owner.
`-walletDir`	(Optional) Path to the wallet directory.
`-y`	(Optional) Skip the upgrade confirmation prompt.
`-h or -help`	(Optional) Show help message.

Parent topic: Upgrade from TSAM Plus 12.2.2.0.0 Database

4.1.4.2 Examples

This example upgrades the TSAM Plus user schema testuser by connecting directly to the Oracle Database service orclpdb1 on localhost through port 1521.

./TSAMDBSchemaUpgrade.sh -connStr "localhost:1521/orclpdb1" -user testuser

This example upgrades the TSAM Plus user schema testuser using the connection service tsamdb_high and the Oracle Database wallet in /path/to/wallet. The -y option automatically confirms the upgrade without prompting for confirmation.

./TSAMDBSchemaUpgrade.sh -connStr "tsamdb_high" -user testuser -walletDir /path/to/wallet -y

Parent topic: Upgrade from TSAM Plus 12.2.2.0.0 Database

4.2 WebLogic Server Deployment

This section contains the following topics:

Parent topic: Advanced Deployment Options

4.2.1 Provision WebLogic Server Domain

Oracle TSAM Plus Manager is a web application running in a WebLogic Server domain. The shell script TSAMWLSProvision.sh is to be used to create a new WebLogic Server domain to host Oracle TSAM Plus Manager.

Parent topic: WebLogic Server Deployment

4.2.1.1 Usage

TLS is enabled by default. When TLS is enabled, specify -adminPort, -identityKeystore, -trustKeystore, and -privateKeyAlias. Use -disableTLS only for non-TLS domains.

./TSAMWLSProvision.sh [-WLSHome <path to WLS Home>] -domainLoc <path to domain> -port <Listen Port> -dataServerPort <DataServer Port> [-adminPort <Admin Port>] -adminUser <admin username> [-identityKeystore <path>] [-trustKeystore <path>] [-privateKeyAlias <alias>] [-disableTLS]

For example:

-port 8001 -dataServerPort 8002

The -dataServerPort argument is required. If it is not specified, the provisioning script exits with an error.

-WLSHome is optional; if omitted, the bundled WebLogic Server is used. -domainLoc, -port, -dataServerPort, and -adminUser are required. TLS is enabled by default. Unless -disableTLS is specified, -adminPort, -identityKeystore, -trustKeystore, and -privateKeyAlias are also required

Table 4-3 Parameter List

Name	Description
`-WLSHome` <path to WLS Home>	(Optional) ORACLE_HOME of WLS installation. If not set, uses the bundled WLS.
`-domainLoc` <path to domain>	Location for the new WLS domain.
`-port <Listen Port>`	[1-65535] Port number on which WebLogic Server listens for incoming connections
`-adminPort <Admin Port>`	Required when TLS is enabled. [1-65535] Port number for WebLogic administrative operations.
`-adminUser <new user>`	Admin user name of the new WLS domain.
`-dataServerPort <DataServer Port>`	Required. [1-65535] Port number for the TSAM DataServer channel used by LMS.
`-disableTLS`	(Optional) TLS disabled
`-identityKeystore` `<path>`	Required when TLS is enabled. Path to the identity keystore.
`-trustKeystore` `<path>`	Required when TLS is enabled. Path to the trust keystore.
`-privateKeyAlias <alias>`	Required when TLS is enabled. Alias for the private key in the identity keystore.
`-h or -help`	(Optional) Show help message.

Parent topic: Provision WebLogic Server Domain

4.2.1.2 Generate mTLS Keystores and Wallets

TSAM supports mTLS by default. For example, the hostnames (both the short name and the fully qualified domain name, or FQDN) of the machines running WebLogic Server (WLS) and Tuxedo should be included in the SANs. Otherwise, the mTLS connection will fail to be established. Therefore, the Subject Alternative Names (SANs) in the certificate must be configured correctly. Otherwise, the mTLS connection will fail to be established.

Use the commands below to create a CA, endpoint certificate, traditional JKS identity and trust stores, and an LMS wallet. Replace only the example values and enter a secure password when prompted.

OpenSSL 3.0 or later is required to generate the Java KeyStore (JKS) files and wallets described in the following steps.

Set the example environment variables

export HOST='tsam.example.com'
export CA_NAME='TLS-Example-Root-CA'
export SERVER_ALIAS='tsam-server'
export CLIENT_ALIAS='tsam-lms'
export APPDIR='/opt/example/tsam-app'
export SANS='DNS:tsam-tls,DNS:tsam-tls.example.com,DNS:*.example.com,IP:127.0.0.1'
export CA_SUBJ="/C=US/ST=CA/L=ExampleCity/O=Example/OU=Security/CN=$CA_NAME"
export SERVER_SUBJ="/C=US/ST=CA/L=ExampleCity/O=Example/OU=IT/CN=$HOST"
export CLIENT_SUBJ="/C=US/ST=CA/L=ExampleCity/O=Example/OU=LMS/CN=$CLIENT_ALIAS"

Generate the CA

openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:4096 -out tls-ca-key.pem
openssl req -x509 -new -sha256 -days 9000 -key tls-ca-key.pem -out tls-ca-cert.pem -subj "$CA_SUBJ" \
  -addext "basicConstraints=critical,CA:true,pathlen:0" \
  -addext "keyUsage=critical,keyCertSign,cRLSign"

Create the WebLogic server certificate

The SAN list must contain every hostname clients use to reach the TLS endpoint.

openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:4096 -out tls-server-key.pem
openssl req -new -sha256 -key tls-server-key.pem -out tls-server-csr.pem -subj "$SERVER_SUBJ" \
  -addext "subjectAltName=$SANS" \
  -addext "extendedKeyUsage=serverAuth,clientAuth"
openssl x509 -req -sha256 -days 9000 -copy_extensions copy \
  -in tls-server-csr.pem -CA tls-ca-cert.pem -CAkey tls-ca-key.pem \
  -CAcreateserial -out tls-server-cert.pem

Create the WebLogic identity and trust JKS files

The final WebLogic identity and trust stores are traditional JKS. The PKCS12 file below is only an intermediate import source for the private key pair.

openssl pkcs12 -export -out tls-server-source.p12 -inkey tls-server-key.pem -in tls-server-cert.pem -certfile tls-ca-cert.pem -name "$SERVER_ALIAS"
keytool -importkeystore -noprompt -srckeystore tls-server-source.p12 -srcstoretype PKCS12 -destkeystore tsam_tls_keystore.jks -deststoretype JKS -alias "$SERVER_ALIAS"
keytool -import -noprompt -trustcacerts -alias "$CA_NAME" -file tls-ca-cert.pem -keystore tsam_tls_truststore.jks -storetype JKS

Verify the WebLogic JKS Files

keytool -list -v -keystore tsam_tls_keystore.jks -storetype JKS
keytool -list -v -keystore tsam_tls_truststore.jks -storetype JKS
openssl verify -CAfile tls-ca-cert.pem tls-server-cert.pem

Parent topic: Provision WebLogic Server Domain

4.2.1.3 Configure mTLS Certificate on Oracle TSAM Plus Agent

Create the LMS client certificate, package it with the CA chain as an Oracle-compatible wallet, and place the wallet in the LMS application directory.

Create the LMS client certificate

openssl genpkey -algorithm RSA -pkeyopt rsa_keygen_bits:4096 -out tls-client-key.pem
openssl req -new -sha256 -key tls-client-key.pem -out tls-client-csr.pem -subj "$CLIENT_SUBJ" \
  -addext "extendedKeyUsage=clientAuth"
openssl x509 -req -sha256 -days 9000 -copy_extensions copy \
  -in tls-client-csr.pem -CA tls-ca-cert.pem -CAkey tls-ca-key.pem \
  -CAcreateserial -out tls-client-cert.pem

Package the LMS client key pair as a wallet

openssl pkcs12 -export -out ewallet.p12 -inkey tls-client-key.pem -in tls-client-cert.pem -certfile tls-ca-cert.pem -name "$CLIENT_ALIAS"
mkdir -p "$APPDIR/wallet.tsam-lms"
cp ewallet.p12 "$APPDIR/wallet.tsam-lms/ewallet.p12"

Configure LMS in UBBCONFIG

Add the LMS settings to the *SERVERS section. Set SEC_PRINCIPAL_LOCATION to the parent directory of wallet.tsam-lms. Enter the wallet password when prompted by tmloadcf.

LMS SRVGRP=LMSGRP SRVID=100 CLOPT="-A -- -l https://<example-host>:<example-port>/tsam"
    SEC_PRINCIPAL_NAME="$CLIENT_ALIAS"
    SEC_PRINCIPAL_LOCATION="<parent directory of wallet.tsam-lms>"
    SEC_PRINCIPAL_PASSVAR="PASSVAR"

Load and start the configuration
```
tmloadcf <UBBCONFIG>
# Start Tuxedo after the WebLogic domain is running
tmboot -y
```
Note:
Final WebLogic stores must report `Keystore type: JKS`. The LMS wallet remains PKCS12 because it is the Oracle wallet artifact. Keep private keys and passwords restricted.

Parent topic: Provision WebLogic Server Domain

4.2.1.4 Example

To create a WebLogic Server domain using the bundled WLS:

./TSAMWLSProvision.sh -domainLoc /u01/oracle/user_projects/domains/tsam_domain \
  -port 7002 -dataServerPort 7003 -adminPort 9002 -adminUser tsamops \
  -identityKeystore /home/oracle/ssl/identity.jks \
  -trustKeystore /home/oracle/ssl/trust.jks \
  -privateKeyAlias myserver

To create a WebLogic Server domain with TLS disabled:

./TSAMWLSProvision.sh -domainLoc /u01/app/tsamdom -port 8001 -dataServerPort 8002 -adminUser tsamops -disableTLS

Parent topic: Provision WebLogic Server Domain

4.2.1.5 Output

A new WebLogic Server domain is created. Start it by executing $TSAMDIR/bin/startup.sh -domainLoc <DOMAIN_HOME>, where <DOMAIN_HOME> is the same directory specified with TSAMWLSProvision.sh -domainLoc.

Parent topic: Provision WebLogic Server Domain

4.2.2 Deploy Oracle TSAM Plus Manager

The related DB users must be provisioned before the TSAM Plus ear file deployment.

The Oracle TSAM Plus Manager application is packaged in an EAR file tsam_22c.ear. Oracle TSAM Plus Manager uses a dedicated WebLogic Server data source to access the database. The JNDI name of the data source is jdbc/TSAM_db1. Also, when -enableAI is set, then another data source jdbc/TSAM_db2 is created. This option adds TSAM_DS2 (jdbc/TSAM_db2) with -createDataSource. It does not provision AI users, credentials, profiles, agents, or schemas, and -dbAIUser is required.

The shell script TSAMDeploy.sh can be used optionally to create the data source, and deploy the Oracle TSAM Plus Manager EAR file to a WebLogic server domain.

Ensure the WebLogic Server domain is up and running. If it is not running, execute $TSAMDIR/bin/startup.sh to start the WebLogic Server domain.

(Optional) Configures a WebLogic OpenID Connect (OIDC) identity asserter named oidc in myrealm and places it first in the authentication provider order if no provider with that name already exists. This option does not update an existing oidc provider. Before deployment, run TSAMOIDC_enable.sh -oidcPropertiesFile <file> to preprocess tsam_22c.ear. The properties file must define issuer, clientId, clientSecret, and redirectUrl; inactivityTimeout is optional. Deploy the modified EAR with -enableOIDC, and map the administrator and viewer principals to the corresponding application roles.

Note:

Protect the properties file and the modified EAR because they contain the client secret.

If you are upgrading from TSAM Plus 12.2.2.0.0, run TSAMDeploy.sh with the following choices:

Do not specify -enableAI or -dbAIUser.
Set -dbConnStr to the upgraded TSAM Plus Manager 22c database.
Set -dbUser to the TSAM Plus Manager database user.
Specify -createDataSource

Parent topic: WebLogic Server Deployment

4.2.2.1 Usage

./TSAMDeploy.sh -WLSHome <path to WLS Home> -WLSURL <WLS URL> -WLSAdminUser \
<admin username> [-WLSHostnameVerification] [-disableTLS] [-trustKeystore <path>] [-createDataSource] \
[-dbConnStr <DB connection string>] [-dbUser <DB user>] [-enableAI] [-dbAIUser <DB AIUser>] [-enableOIDC]\
[-EARFile <path to EAR file> [-domainLoc <path to domain>]]

Table 4-4 Parameter List

Name	Description
`-WLSHome` `<path to WLS Home>`	(Optional) `ORACLE_HOME` of WLS installation. If not set, then it uses the bundled WLS.
`-WLSURL <URL>`	Admin URL of the target WebLogic Server.
`-WLSAdminUser <username>`	Admin username of the WLS domain.
`-WLSHostnameVerification`	(Optional) Flag to enable hostname verification.
`-disableTLS`	(Optional) TLS disabled
`-trustKeystore <path>`	(Optional) Path to trust keystore.
`-createDataSource`	(Optional) Creates the Data Source
`-dbConnStr` <string>	(Optional) Database connection string. Required if creating a data source.
`-dbUser <username>`	(Optional) TSAM Plus Database username. Required if creating a data source.
`-enableAI`	(Optional) Enable AI feature for TSAM Plus.
`-dbAIUser <aiusername>`	(Optional).TSAM Plus Database AI username when creating AI Data Source. It is mandatory if you are creating a data source and `-enableAI` is set.
`-enableOIDC`	Preprocess tsam_22c.ear with TSAMOIDC_enable.sh -oidcPropertiesFile <file>, then deploy that EAR with TSAMDeploy.sh ... -enableOIDC. List issuer, clientId, clientSecret, and redirectUrl; document myrealm and administrator/viewer principal-to-role mappings; and restrict access to the properties file and EAR because clientSecret is embedded.
`-EARFile`	Optional unless deploying or redeploying the TSAM Plus Manager `EAR`. When `-EARFile` is set, `-domainLoc` is required.
`-domainLoc <path to domain>`	Required when `-EARFile` is set. Location of the target WebLogic domain.
`-h or -help`	(Optional) Show help message.

Parent topic: Deploy Oracle TSAM Plus Manager

4.2.2.2 Examples

To create a data source in the bundled WebLogic Server and deploy Oracle TSAM Plus, specify the -domainLoc parameter when using the -EARFile option.

To create a data source in the bundled WLS, and deploy the Oracle TSAM Plus When -EARFile is set, -domainLoc is required.

./TSAMDeploy.sh -WLSURL t3s://localhost:9002 -WLSAdminUser tsamops \    
    -trustKeystore /home/oracle/ssl/tsam-tls-truststore.jks \ 
    -createDataSource -domainLoc <domain_directory>  \ 
    -dbConnStr "jdbc:oracle:thin:@//dbhost:1521/ORCL" \
    -dbUser tsamuser1 -enableAI -dbAIUser tsamuser2 \ 
    -EARFile ${TSAMDIR}/deploy/tsam_22c.ear

EAR Only Deployment

./TSAMDeploy.sh -WLSURL t3s://localhost:9002 -WLSAdminUser tsamops \   
   -trustKeystore /u01/keystores/trust.jks \  
   -EARFile /workspace/tsam/tsam-adf-app/Mgr/target/tsam_22c.ear \  
   -domainLoc /u01/oracle/user_projects/domains/tsam_domain

To create Data Source only in the bundled WLS, without deploying Oracle TSAM Plus Manager EAR file:

./TSAMDeploy.sh -WLSURL t3s://localhost:9002 -WLSAdminUser tsamops \
    -trustKeystore /home/oracle/ssl/tsam-tls-truststore.jks \ 
    -createDataSource dbConnStr "jdbc:oracle:thin:@//dbhost:1521/ORCL" \
    -dbUser tsamuser1 -enableAI -dbAIUser tsamuser2 \
    -domainLoc <DOMAIN_HOME>

./TSAMDeploy.sh -WLSURL t3s://localhost:9002 \ 
    -WLSAdminUser tsamops -trustKeystore /u01/keystores/trust.jks \  
    -EARFile ${TSAMDIR}/deploy/tsam_22c.ear \ 
    -domainLoc <DOMAIN_HOME>

To deploy the Oracle TSAM Plus Manager EAR file to the bundled WLS, without creating a data source:

./TSAMDeploy.sh -WLSURL t3s://localhost:9002 \ 
    -WLSAdminUser tsamops -trustKeystore /u01/keystores/trust.jks \ 
    -EARFile /workspace/tsam/tsam-adfapp/Mgr/target/tsam_22c.ear \
    -domainLoc <DOMAIN_HOME>

Parent topic: Deploy Oracle TSAM Plus Manager

4.2.2.3 Output

The Oracle TSAM Plus Manager application is deployed to the WebLogic Server domain. You can access the Oracle TSAM Plus Console from a browser via https://<hostname>:<port>/tsam with username admin and the password you entered when prompted “Enter TSAM Plus admin password” during the execution of TSAMDBSchemaSetup.sh.

Note:

Use HTTPS when TLS is enabled and HTTP with -disableTLS.
<port> is the WebLogic console listen port, not the TSAM DataServer channel port

Parent topic: Deploy Oracle TSAM Plus Manager

4.2.3 Start and Shutdown WebLogic Server Domain

To start the WebLogic Server domain:

$TSAMDIR/bin/startup.sh -domainLoc <DOMAIN_HOME>

To shutdown the WebLogic Server domain:

 $TSAMDIR/bin/shutdown.sh -domainLoc <DOMAIN_HOME> -trustKeystore <path>

The -trustKeystore option is required. Hostname verification is disabled by default and is enabled only when -WLSHostnameVerification is specified.

Parent topic: WebLogic Server Deployment

4.3 Reset the password of the TSAM Plus Admin User

The TSAM_AdminPasswordReset.sh shell script is used to change or reset the password of the TSAM Plus Manager admin user.

Parent topic: Advanced Deployment Options

4.3.1 Usage

./TSAM_AdminPasswordReset.sh -connStr <connection string> -user <username> [-walletDir <dir>]

Table 4-5 Parameter List

Name	Description
`-connStr`	DB connection string. If the connection string contains spaces or special characters like parentheses, enclose it in double quotes.
`-user`	The name of the TSAM Plus database user, not the name of the TSAM Plus database AI user.
`-walletDir`	(Optional) Path to the wallet directory
-h or -help	(Optional) Show help message.

Parent topic: Reset the password of the TSAM Plus Admin User

4.3.2 Examples

To reset the TSAM Plus Manager admin user (username is admin) password in the tsamuser database schema on an Oracle Database server, run:

./TSAM_AdminPasswordReset.sh -connStr "localhost:1521/orclpdb1" -user tsamuser

Parent topic: Reset the password of the TSAM Plus Admin User