Oracle® Collaboration Suite Release Notes Release 2 (9.0.4) for AIX Based Systems Part Number B12116-01 |
|
|
View PDF |
This chapter provides information about issues associated with Oracle Email. It contains the following sections:
Release 2 of the Oracle Collaboration Suite e-mail product ships with restricted use licenses for the Oracle9i Application Server 9.0.2.3 and the Oracle9i Database 9.2.0.3. Several enhancements have been made to all components of the mail solution to improve performance and functionality. New features include:
This section describes Oracle Email known issues.
The targetdn
attribute must be cataloged manually. If this attribute is not cataloged, the user rename operation fail
Workaround:
Enter the following command:
$ORACLE_HOME/ldap/bin/catalog.sh -connect infrastructure_connectstr -add \ -attr targetdn
Text index for e-mail body search is created with the Oracle Text BASIC_LEXER, which supports English and most western European languages that use white space delimited words. For other languages that are not supported by Oracle Text BASIC_LEXER, e-mail body search does not work.
Workaround:
SQL> alter table es_imt_msgbody add (cset VARCHAR2(20) default 'JAAUTO');
Supported lexers are:
es_mail
database user, drop the existing index es_ot_ix_search
file. This causes all previously indexed e-mails to be un-indexed.es_ot_ix_search
file with the lexer chosen in step 2. This causes all previously indexed e-mails to be re-indexed using the new lexer.esoratext
tablespace exists.es_mail
to recreate the index:
@ execute CTX_DDL.CREATE_PREFERENCE('my_lexer','LEXER_NAME'); Create charset filter preference @ execute CTX_DDL.CREATE_PREFERENCE('my_charset_preference','CHARSET_FILTER'); @ execute CTX_DDL.SET_ATTRIBUTE('my_charset_preference','charset','chosen_ charset'); chosen_char_set : Globalization support name of source character set. DROP INDEX es_ot_ix_search; CREATE INDEX es_ot_ix_search ON es_imt_msgbody(text) indextype IS ctxsys.context parameters ('DATASTORE es_search_dspref FILTER CTXSYS.CHARSET_FILTER SECTION GROUP es_search_sec_group STORAGE oratextstore LEXER my_lexer CHARSET COLUMN cset') ;
Limitations:
This section describes the known bugs for Oracle Email.
You need to configure the database listener to use extproc32
for external procedure agent callout.
To configure:
listener.ora
file, as follows:
Bug No. | Description |
---|---|
2990674 |
The IMAP sort command does not work correctly on profile folders. |
Multi-byte characters are sometimes not displayed properly. Oracle assigned bug number 2354956 to track this. If this problem occurs, do the following:
The following sections provide information about documentation errata.
The following sections provide information about documentation errata in he Oracle Email Migration Tool Guide.
Novell Client Version 4.81 or higher should be installed on the system where the Migration Tool is installed.
Microsoft Exchange 5.0 and Microsoft Exchange 5.5 does not support Public Alias Migration from this Version.
To check the mode in which the Outlook Client is installed:
/
) is present in a folder name, the Migration Tool replaces it with an underscore (_
) and prefixes the folder with Renamed_
.
For example, if the original folder is named Sales/March, the name becomes Renamed_Sales_March
.
ORACLE_HOME
can be any directory on the system from which the migration tool runs. It need not be a proper ORACLE installed ORACLE_HOME
setup.
Create a directory oes/migration
under the set ORACLE_HOME
.
Distribution lists are only created as SMTP distribution lists on Oracle. These can be converted to list server lists using the WebMail client administration pages.
Userlistgen
generates the users.xml
file for IMAP-based migration where the passwords are protected. This file is used by the Migration Tool for loading users.
userlistgen.sh
from $ORACLE_HOME/oes/migration/bin
.
./userlistgen.sh
The Migration Tool reads the following parameters from Standard input. To terminate, press ENTER twice.
For example:
sourceimapuserid=test1 sourceimappasswd=welcome1 targetimapuserid=test1 targetimapuserpasswd=welcome1 quota=50 sourceimapuserid=.....
When this is complete, the users.xml
file has to be copied to the required directory from where the Migration Tool will read it.
./userlistgen.sh file=<name>
The Migration Tool reads the file (in the users.xml
format supported by the Migration Tool) and the output file is generated in the same directory with the passwords in the users.xml
file protected.
For example: for input file:
<userlist> <user sourceimapuserid="test1" sourceimappasswd="welcome1" targetimapuserid="test1" targetimappasswd="welcome1" quota="10" /> </userlist>
The following sections provide information about documentation errata in the Oracle Email Application Developer's Guide.
Before a caller can access any of the directory components, the caller must authenticate with the LDAP directory using the oracle.mail.OESContext
class. Once authenticated, the instance of oracle.mail.OESContext
representing a trusted session must be passed to all of the directory APIs. There are two ways of authenticating: in the middle-tier ORACLE_HOME
and by providing the user credentials.
In this authentication model, the application must be deployed on a middle-tier host.
Modify the $ORACLE_HOME/oes/jazn/jazn-data.xml
file as follows:
$ORACLE_HOME/oes/jazn/jazn-data.xml
file.$ORACLE_HOME/oes/jazn/jazn-data.xml
</jazn-policy>
tag, add the following lines.
<grant> <grantee> <codesource> <url>file:%JARFILE_NAME%</url> </codesource> </grantee> <permissions> <permission> <class>oracle.security.jazn.JAZNPermission</class> <name>logon</name> </permission> </permissions> </grant>
where:
$ORACLE_HOME
is the Oracle home path in the middle-tier host.
%JARFILE_NAME%
is the absolute path of the application jar file.
Example authenticating as an application with the debug option turned off
OESContext oesctx = new OESContext(DirectoryConstants.DS_CALLERTYPE_APP, false); //Authenticate to the directory oesctx.authenticate(null, oracle_home); //oracle_home is the oracle home path on the middle tier host
In this authentication model , the application must provide Oracle Internet Directory super user credentials (credential of cn=orcladmin or cn=umadmin,cn=EmailServerContainer,cn=Products,
)
cn=OracleContext
Example authenticating as an application passing super user credentials with the debug option turned off
OESContext oesctx = new OESContext(DirectoryConstants.DS_CALLERTYPE_APP, false); //Authenticate to the directory oesctx.authenticate(username, password, ldaphost, ldapport); //username - super user dn, password - super user password, ldaphost - OID host name, ldapport - OID port number
To run these examples, the CLASSPATH
environment variable must include the following:
jndi.jar, ldap.jar, providerutil.jar, classes12.zip, $ORACLE_ HOME/jlib/repository.jar, $ORACLE_HOME/jlib/esldap.jar, $ORACLE_ HOME/jlib/escommon.jar, $ORACLE_HOME/jlib/ojmisc.jar, $ORACLE_ HOME/j2ee/home/jazn.jar
The $ORACLE_HOME/oes/jazn/jazn-data.xml
file must be edited as described above.
The following section provides information about documentation errata in the Oracle Email Administrator's Guide.