This article describes the Oracle Wallet Support feature in Data Express. If the wallet is properly configured, it allows the Data Express engine to connect the source and target databases without needing to specify the user name and password.

Wallet overview
Oracle Wallet is a container/repository that stores credentials such as certificates, certificate requests, and private keys. You can use this feature if you enable HTTPS. Oracle Wallets can be stored either on the file system or an LDAP Server (like OID).

Managing Wallets
You manage Oracle Wallets using Oracle Wallet Manager (OWM - java based application). OWM is executable in $ORACLE_HOME/bin .

Using OWM you can:

·         Create wallets

·         Create certificate requests

·         Import certificates to wallets

·         Upload wallets to a directory

Implementing Oracle Wallet in Data Express
There is a new parameter, Identify Externally, in the dxeconfig.cfg file that identifies the connection criteria. This parameter is at the end of the file in the section applicable to the Oracle Extension only.

The possible values are Y and N.  Default value is N.

·         If Identify Externally is set to yes (Y), Data Express will skip the reading of user name and password from method.rc. In this case, the connection to the database, instead of happening in the usual way (using the user and password specified during the “export” phase), will use the configured Wallet (if the Wallet has been configured properly). The system will connect to the database without needing explicit user name and password credentials.

·         If Identify Externally is set to No (N), the behavior of Data Express will remain unchanged and access continues to require a valid user name and password

The user interface will remain unchanged (and in case of use of wallet feature, the data specified as user and password are ignored by Data Express), and the only change needed, from the user perspective, is that in order to use the new feature, you must set the dxeconfig.cfg configuration file properly.

Here is a sample of the dxeconfig.cfg file:

* Data Express Configuration File

 

LogLevel:1

Always Drop Table:N

CSV Data Store:N

COBOL Masking:Y

Validate Target Table:Y

Validate Source Schema:N

Enable Logging:N

Hide Progress:N

 

* These entries are only applicable to the Oracle Extension.

 

Text Output:N

Data Separator:,

Fields Enclosed By:"

Identify Externally:Y

 

The dxeconfig file is not used for sampling. In order to use wallet management, you need to specify a –e parameter.

Use the following command to use identification via user and password:

Dxestart

Use the following command to use identification via wallet:

Dxestart -e