- Changing the Collection Security Framework setting to On in the
Magnify Console (under General Settings), displays a 404 - Resource
Not Found error in the Magnify Search page.
As a workaround, you
must navigate to the WebFOCUSxx\webapps\webfocus\search\jsp folder
and rename the magnifylogin.jsp_sample file to magnifylogin.jsp.
Once the file is renamed, restart the application server.
- Using FORMAT MAGNIFY
with TEXT fields that are larger than 32K in size generates a FOCSORT
error because the FOCSORT threshold (2GB) is reached.
As a workaround,
the TEXT field must be set as a Binary Large Object (BLOB) field (ACTUAL
and USAGE) so that it bypasses the FOCSORT and uses the FOCCACHE instead.
This technique writes the content out to disk in chunks as it is
processed and is delivered to Magnify as an incoming document.
- To enhance processing throughput and high availability failover,
indexing directly to disk can now be shared across a distributed
system managed by multiple application servers, which regulates
the delivery of incoming feeds and distributes searching in parallel.
This implementation must be used with the ENGINE feedtype set to
FULL. This architecture does not support dynamic partitioning. Instead,
a new Java Virtual Machine (JVM) instance is recommended. It is
also recommended to contact customer support, to ensure a proper
search architecture.
For more information, see the Magnify
Developer's Guide.
- When using Magnify search within a portal with Microsoft Internet
Explorer Version 11 with Compatibility View, the search results
may jump into a tabular view.
- The following query string parameters are no longer allowed
and accepted within Magnify URLs:
-
proxyreload
-
clearcache
-
collections
- The configuration and behavior of the Century Electronics demo
has changed from previous releases. Specifically, any changes made
to the collections file or style sheet file will be available after
the application server is restarted.
To configure and use the
Century Electronics demo, you will need to:
- Create a
backup copy of the original collections.xml file and collections_century.xml file.
- Delete the collections.xml file and rename the collections_century.xml file
to collections.xml.
- Remove all references to any combination of the following query
string parameters:
proxyreload=1
clearcache=1
collections=<any_value>
Note: To
apply changes directly to the collections file without restarting the
application server, use the Refresh Collections option in
the Magnify administration console.