My Oracle Support Banner

Q & A On Elastic Search With Classic Message Store - Part 2 (Doc ID 2652146.1)

Last updated on MAY 08, 2020

Applies to:

Oracle Communications Messaging Server - Version 8.0.2 and later
Information in this document applies to any platform.

Goal

Question #1:  What is the isc log behavior? And what sort of controls are available to manage them?

The isc.log* files appear to behave like the ISS logs, rather than most of the Messaging logs:

$ ls -alrti isc*
  73827 -rw-r----- 1 <user> <group> 0 Mar 4 13:49 isc.log
  73826 -rw-r----- 1 <user> <group> 414 Mar 4 13:49 isc.log.1
  75296 -rw-r----- 1 <user> <group> 0 Mar 6 07:06 isc.log.0.lck
  75298 -rw-r----- 1 <user> <group> 414 Mar 6 07:06 isc.log.0

The current log is .0 and rotation involves renaming them.

Is that correct?

Where are the controls for how large they can get, how many it keeps, etc...?
 
Question #2:  What is the purpose of the -x switch on the deliver command?

The documentation says:

  -x : Enable isc callout in delivery, only valid in Cassandra store and isc installed

Is the part about "Cassandra" correct? Or is that a left-over from before Elastic and ISC were available with Classic store?

What happens if I use deliver to delivery a message with attachments and do not use -x?
 
Question #3:  If we had two backends sending to the same Elastic server and there happened to be DIFFERENT users on those two backends with the same UID, would it be possible for those users to search and get results about each other's mail?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.