Oracle and Aurea List Manager (Windows)
It is mandatory to install Oracle Client Tools or Basic Client Software on the machine, which is going to be running Aurea List Manager before installing Aurea List Manager.
Once this is done, a user and password needs to be created to be used by Aurea List Manager. Aurea List Manager can now be installed.
Installing Oracle/Aurea List Manager Windows
- Install the Oracle Client Tools on the machine, which is going to be running Aurea List Manager
- Run the Configuration Assistant
- Select Local Net Service Name configuration and select Next.
- Select Add when asked what access you like to set up.
- Select Oracle9 database or service when asked what version of Oracle database to access.
- Enter the Service Name.
- Select TCP.
- Enter additional information as required by your network protocol.
- Perform a test of your connectivity.
- Select a Net Service Name.
- Open SQL*PLUS, and log on as system administrator.
- Enter the following lines:
create user username identified by password default tablespace users quota unlimited on users
grant connect, resource to usernameThe DBA (Database Administrator ) would need to know the standard permissions required for Oracle users. The previous is an example only. You may use any username or a different tablespace if desired.
Aurea List Manager can now be installed. Be sure to select the installer that matches the version of client tools installed from support.aurea.com
Changing the Character Set of your Oracle Instance
Oracle servers, by default, do not install with a character set that allows 8-bit ASCII characters to be represented correctly. Any high ASCII characters (greater than 127) are translated into other characters.
This can cause a problem any mail flowing through Aurea List Manager uses special accent
characters, such as ÿ or á. When this happens the Aurea List Manager server will give one of these errors
when starting it in the foreground:
Warning
Your database is not configured to store all data exactly as it was sent. This will cause some messages, especially those in foreign languages, to be incorrectly saved. It is recommended that you change your database configuration to ensure that this is not a problem.
Or,
Your database and/or client configuration will cause problems, as errors were generated when special characters (such as used by foreign languages) were sent and/or retrieved from the database. This will likely cause errors and should be corrected before continuing.
To solve this problem, the Oracle instance has to be created with an 8-bit ASCII character set. If there is no preference, we recommend you use: WE8ISO8859P1
This character set appears also to be the one used by Windows as its default, so if both client and server are set to use the same character set, there would be no need to worry about characters being translated.
However, if you choose a different character set, the data is translated into the client character set, which almost certainly causes problems. The client character set can be configured using an environmental variable called NLS_LANG.
The syntax of the variable is <language>_<country>.<char set>,
such as :
American_America.US8PC437.Setting the Environment Variable for Windows
- In the Control Panel, open System. Select the Advanced tab.
- Select Environment Variables
- In the System Properties for Environment Variables, assign
NLS_LANGtoAmerican_America.US8PC437.
Database Server Password Security
As the database password is saved unencrypted in a file lmcfg.txt, it is recommended to remove the password saved in this file and then specify that the password is provided on startup by altering this file.