How to: |
Magnify requires an application server (for example, Tomcat or WebSphere) in order to read and write to index libraries. It can be installed on a Windows (64bit preferred) or Unix\Linux-based server, using the same language as the WebFOCUS Client.
Processing should be at least a dual-core machine, however, four CPUs are generally recommended. Moreover, a minimum of 8GB in memory is required, while 16GB is usually recommended. Depending on the size of the data, storage space should be anywhere between 250GB to 1TB or higher (it is usually estimated as three times the size of the expected data set).
Note: This all varies depending on the type of search-based application being proposed. Indexing frequency, volume of data, and concurrent usage affect how storage space and memory are allocated. Therefore, the use of a split-tier environment is recommended for a Magnify platform where the Reporting Server, Magnify, and each data source are each provided with their own dedicated resources. Magnify does scale in order to accommodate any environment.
The following are the prerequisites to configuring and using Magnify:
Note: For more information, see the WebFOCUS Security and Administration manual.
If the Application Server is running Java Runtime Environment (JRE) 1.5, the JAXBcomponent must be installed separately. For more information on installing the JAXBcomponent, see How to Add the JAXB Library to Your System or How to Add the JAXB Library to WebSphere. JRE 1.6 includes this component.
JAXB is part of the Oracle Distribution. As such, it resides in a special location in the path reserved for endorsed Java Standard files. The location of this file varies by application server. This section provides instructions to install the JAXB component into the JRE 1.6 classpath.
In addition, a Tomcat Server requires that you set a system property variable to point to the directory where the JAXB component resides.
https://jaxb.dev.java.net -console
The directory must be accessible to your WebSphere Application Server.
java -jar JAXB2_date.jar -console
where date is the release date of the jar file. For example, JAXB2_20091104.jar.
../tomcat/bin/catalina.sh
export JAVA_ENDORSED_DIRS=/path/jaxb-api.jar
Process Definition, Configuration information is displayed in the right pane, as shown in the following image.
java.endorsed.dirs
In the Value field, type:
/path/jaxb-ri-20070122/lib
In the Name field, type:
javax.xml.transform.TransformerFactory
In the Value field, type:
org.apache.xalan.xsltc.trax.TransformerFactorylmpl
WebFOCUS |