Implementing Oracle Wallet (Windows only)
You can store and manage Oracle database credentials using the Oracle Login Wallet (auto-login) instead of the Contenta Password Manager (dbpwdmgr.exe) utility. Oracle Wallet is supported for Contenta OCI binaries only. This documentation is intended for Oracle DBAs and Contenta Administrators.
RWS recommends that you follow the Oracle documentation for installing and setting up Oracle Wallet. Oracle Export (exp.exe) and import (imp.exe) utilities do not support Oracle Wallet; you must use Oracle Data Pump utilities to export and import databases. Contenta dbexport.pl and dbimport.pl utilities support Oracle Data Pump.
When Oracle Wallet is setup correctly, a particular schema credential (such as xyadmin or a given Contenta database) is connected to by logging into Oracle with an alias SID, leaving the username and password blank. Each schema is given its own SID alias in the client-side tnsnames.ora file, and these aliases are used to look up the appropriate schema and password in the local wallet.
For example, instead of logging in as S1000D/pswd@oraclesid.
- The login is converted by Contenta to
/@oraclesid_S1000D. - The tnsnames.ora file contains an alias from
oraclesid_S1000Dto the Oracle instance - The Oracle Login Wallet has a credential mapping
oraclesid_S1000DtoS1000Dandpswd.
The SID alias alone thus selects both the Oracle instance and the schema and password for login.
Any tools that need to perform SQL operations (such as xyadmin) that would normally require a -xyadminpwd argument but expect to get the password from the dbpwdmgr file, will instead expect a -xyadminsid argument, which is typically of the form oraclesid_xyadmin.
When executing any tool that requires the SID at the command line, be sure to specify the same value (such as oraclesid_S1000D) as the alias defined in the tnsname.ora file for the schema.
The Login Wallet must contain an entry for every Contenta database (Oracle schema) available under an Oracle instance; otherwise Contenta will fail to connect to the database.
If provided at the command line, database password options such as -pdmpwd or -xyadminpwd are ignored in Oracle Wallet mode for all database tools, except newdb.pl, dbimport.pl, and dumpobjs when executed with the -i option.
Database Name on the Contenta Login page or at the command line as dbname@oraclesid_dbname. The following Contenta tools can be accessed using Oracle Wallet.
- bin/builddb.exe
- bin/pcmadmin.exe
- bin/pcmsessions.exe
- bin/reap/blobread.exe
- bin/reap/checkblobs.exe
- bin/reap/dumpobj.exe
- bin/reap/editobj.exe
- bin/reap/fixblob.exe
- bin/reap/killobj.exe
- bin/reap/modversions.exe
- bin/reap/pcm_stats.exe
- bin/reap/reap_delete.exe
- bin/reap/pltrim.exe
- bin/reap/reap_report.exe
- bin/reap/showobj.exe
- bin/verilk.exe
- bin/support/bcp.exe
- bin/support/editmd.exe
- bin/support/update_project_views.exe
- bin/Upgrade_56/upgrade_56.exe
- bin/Upgrade_S1000D/upgrade_S1000D_59.exe
- bin/dbcopy.pl
- bin/dbexport.pl
- bin/dbimport.pl
- bin/dbrun.pl
- bin/dbstat.pl
- bin/dropdb.pl
- bin/listdb.pl
- bin/newdb.pl
- bin/pcm_compute_stats.pl
- bin/pcm_update_indexes.pl
- bin/ResetLinkendSequence.pl
- bin/setup_login_wallet.pl
- bin/support/validateprojlocks.pl
- encaps/Database.pm
- encaps/newdb.pm
- encaps/unicom.pm
- encaps/XyConfig.pm
The following section describes how to implement and use Oracle Wallet.