You can influence the behavior of Acquire when capturing Oracle data by putting suitable entries in an override script file. This file must be called APMconfgora and must be located in the metron home directory. It must have the ‘executable’ attribute set. If a file with this name is present in the metron home location, the Acquire Oracle scripts will attempt to run it after first setting values from the APMconfg file and from the ‘crontab’ entry that executes it.
This allows you to, carefully, change some of what Acquire does. There is no error checking for the contents of the APMconfgora file so you must take great care to use it correctly.
You are advised not to use this feature unless you are very sure of what you need to do and why. You are further strongly advised to open a call with Precisely Support to explain what you need or intend to do and obtain support in helping you do it.
In addition to overriding items already in the capture profile for an Oracle target, or setting specific environment variables of your choice, one specific override is also available.
This uses environment variables to set or override the Oracle wallet. See Using the Oracle Listener with Acquire for UNIX or Linux for more details on this facility.
In APMconfgora you can create and export environment variables of the form:
APMWALLET_<sid>_<databasename>=<walletentry>
<sid> is the Oracle SID
<databasename> is the Oracle database name
<walletentry> is the wallet entry to use to obtain the credentials to access this Oracle instance
The <sid> and <databasename> entries must EXACTLY match (including case) to override a wallet entry provided by the Control Center.
If <walletentry> is *NO then this will unset any wallet entry provided, even from Control Center, and force Acquire to make a bequeath connection to Oracle.
Example APMconfgora lines:
APMWALLET_PROD_Payroll=ProdPayWallet; export APMWALLET_PROD_Payroll
APMWALLET_TEST_Payroll=TestPayWallet; export APMWALLET_TEST_Payroll
APMWALLET_QA_Payroll=*NO; export APMWALLET_QA_Payroll