Release Notes
Release 1.0.5
E67907-03
August 2017
This document provides release notes for Oracle Communications Indexing and Search Service Release 1.0.5, consisting of the following sections:
The new features in this release of Indexing and Search Service are:
Indexing and Search Service User Can Manage Services By Using Solaris svcadm Commands
Searching Message Body with OR Terms No Longer Returns Extraneous Matches
Indexing and Search Service 1.0.5.29 provides new configuration parameters to improve bootstrapping large actions due to the overhead with merge operations. See the iss.indexsvc.segmentmerge.factor and iss.indexsvc.segmentmerge.factor.autoadjust.enabled parameters, and the topic on improving bootstrap performance for large accounts in Indexing and Search Service System Administrator's Guide, for more information.
You can optimize Indexing and Search Service 1.0.5.29 so that the jmqconsumer process scans the event backlog and marks the useless events to be skipped before submitting them to the indexSvc process. See the iss.jmqconsumer.useless.event.skip.enabled configuration parameter, and the topic on optimizing event backlog in Indexing and Search Service System Administrator's Guide, for more information.
Indexing and Search Service 1.0.5.29 provides the capability to automatically check the dIndex when the indexSvc process starts, and to automatically repair some issues that it finds. See the iss.indexsvc.periodic.autosync.checkstore.enabled and iss.indexsvc.periodic.autosync.checkstore.sync.enabled configuration parameters, and the topic on automatically checking and repairing dIndex problems in Indexing and Search Service System Administrator's Guide, for more information.
Starting with Indexing and Search Service 1.0.5.29, Java 8 is supported.
The isshttpd proxy in Indexing and Search Service 1.0.5.30 provides an API that enables non-Convergence clients, such as mobile clients, to search Indexing and Search Service. No additional configuration is necessary to be able to use this API.
The setup script in Indexing and Search Service 1.0.5.30 has been improved so that the Indexing and Search Service user ID (iss.user} can manage services through Oracle Solaris Service Management Facility (SMF).
Indexing and Search Service 1.0.5.30 has added the -T option for postpatch_restart and setup scripts to improve timeout situations.
Indexing and Search Service 1.0.5.30 has added additional output to the liststats option to display the following autobootstrap statistics:
Candidates reboot by age
Candidates from checkstore
Accounts bootstrapped
See the iss.store.reboot.age configuration parameter, and topic about the output of the liststats option in Indexing and Search Service System Administrator's Guide, for more information.
Indexing and Search Service 1.0.5.29 changes the contents of the index for an account to correct a problem where a message body search with OR terms was returning extraneous matches. These changes also remove most of the restrictions on the use of "body" and "text" terms in search queries.
With the changed index, the "body" and "text" terms are now part of the "content terms" kind, and so can be freely mixed in combinations with other content terms like "to," "from," "cc," and so on.
To be able to use this change, rebootstrap accounts to trigger a rebuild of the index:
Run the following command:
issadmin.sh --listbrief | grep 'separate (legacy)' |awk '{print $2}' &>
/var/tmp/rebootlist
Run the following command:
issadmin.sh --setautobootlist /var/tmp/rebootlist --reboot
Note:
If either autobootstrap or autosync are enabled, the process of rebootstrapping users, and rebuilding their indexes, happens automatically over time.After you rebootstrap accounts, the content index becomes larger, perhaps as much as double the original size, to support the previous Indexing and Search Service search capabilities. However, if your deployment does not use the attachment store (nor the Convergence attachment window view), you can reduce the size of the index to approximately the original size by using the iss.indexsvc.attachment.indexmode configuration parameter. The default value is full, which generates all attachment records along with the new "fullcontents" field. To reduce the index size, set this parameter to IMAPonly, and the indexing service generates only the new "fullcontents" field.
In Indexing and Search Service 1.0.5.30, when the --selectstate statelist command is specified with the --listbrief option, only users in the selected state are displayed
This section lists the fixed issues in this release of Indexing and Search Service.
Table 1 Fixes in Indexing and Search Service 1.0.5.29 and 1.0.5.30
| Bug Number | Customer SR | Notes |
|---|---|---|
|
25490517 |
3-14204991011 |
The setup script timeout is now configurable. See "-T Option for postpatch_restart and setup Scripts" for more information. |
|
25367495 |
3-14006074461 |
See "Indexing and Search Service User Can Manage Services By Using Solaris svcadm Commands" for more information. |
|
25178199 |
N/A |
Autoreboot candidates have been added to the liststats option. See "Additional Output for the liststats Option" for more information. |
|
24341871 |
3-13067221031 |
You can configure Indexing and Search Service to use a standby Indexing and Search Service server for autobootstrapping accounts. The bootstrap event on the standby server is delayed so that it only runs when the main Indexing and Search Service server is done bootstrapping the user. See the topic about replicating autobootstrap events to a standby server in Indexing and Search Service System Administrator's Guide for more information. |
|
22750583 |
3-14140106191, 3-12059238051 |
The checkIss command now gives time reporting on the tests that it is running. |
|
21505813 |
3-11090833741 |
The --listbrief option has been enhanced to filter on account state. |
|
17969121 |
3-8251849101, 3-10282967771 |
A problem as been corrected where search queries on a message body using OR terms was returning extraneous matches. See "Searching Message Body with OR Terms No Longer Returns Extraneous Matches" for more information. |
This section lists the known limitations in this release of Indexing and Search Service.
SR number: NA
Bug number: 18896930
When you run a patch upgrade on a configured patch, it fails.
Workaround:
When upgrading by using an Indexing and Search Service Automated Release Update (ARU) patch, you must run following commands:
commpkg upgrade IndexSearch_home/bin/setup -u IndexSearch_home/bin/setup
where IndexSearch_home specifies the installation location for the Indexing and Search Service software. The default is /opt/sun/comms/jiss.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Communications Indexing and Search Service Release Notes, Release 1.0.5
E67907-03
Copyright © 2017, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.