
Technical Notes |
|
To install Reflection for the Web 2011 on a UNIX or Linux machine, follow the steps in the Installation Guide. Use this technical note to manually install Reflection for the Web 2008 to a machine running UNIX or Linux when an automated installer is not available for your platform.
If you are installing Reflection for the Web 2011, please follow the instructions in the Reflection for the Web 2011 Installation Guide located here: http://support.attachmate.com/manuals/rweb2011.html.
This technical note includes information about installing and configuring Java SDK, Tomcat, and Reflection for the Web 2008 on a UNIX or Linux machine. This information in this note is organized into the following sections:
The instructions provided in this document apply to both UNIX and Linux systems; however, for ease of use, the term UNIX is used throughout this document.
This document assumes that you will install the Java SDK, Tomcat, and Reflection for the Web 2008 into the directories noted below. If any of these applications are installed in different locations, such as /opt, make the necessary path changes when following the steps provided in this document.
Note the following before you install Reflection for the Web 2008:
Attachmate Technical Support recommends that you review the Reflection for the Web 2008 Installation Guide, which is available with the product and online: http://support.attachmate.com/manuals/rweb2008.html
For additional Reflection for the Web resources, see Technical Note 1668.
If Java is already installed on your UNIX machine, skip to Installing and Configuring Tomcat. If Java is not yet installed, follow the steps below to obtain and install the correct version of Java.
To obtain and install Java for other UNIX systems, follow these steps:
/usr/javaJDK Self-Extracting Installation for Linux (64-bit): http://www.oracle.com/technetwork/java/javase/install-linux-64-self-extracting-142068.html
JDK Self-Extracting Binary Installation for Linux (32-bit): http://www.oracle.com/technetwork/java/javase/install-linux-self-extracting-138783.html
For example, for Linux and most UNIX platforms using the bash shell, the $PATH is updated as follows:
export PATH=/usr/java/jdk1.6.0/bin:$PATHFor Sun Solaris, use the following commands:
PATH=/usr/java/jdk1.6.0/bin:$PATHexport PATHjava -versionVersion information similar to the following should be displayed, confirming that you have installed the Java™ 2 Runtime Environment:
java version "1.6.0" Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0)Java HotSpot(TM) Client VM (build 1.4.2, mixed mode)Once Java is installed, follow the steps below to install and configure Tomcat, the servlet runner.
jar -xf /usr/local/tomcat.zip(Search for java.exe and enter the path to the directory above the /bin/ directory.) For example, the JAVA_HOME line in setenv.sh might read,
JAVA_HOME=/usr/java/j2sdk1.6.0Note the following:
chmod 755 *.shNote: The .sh files are in /user/local/jakarta-tomcat/bin.
If no other web server is configured on the machine where Tomcat was installed, skip to Installing and Configuring Reflection for the Web 2008.
If another web server was present on the UNIX machine when Tomcat was installed, you may need to modify Tomcat's HTTPS and HTTP port numbers to avoid interference with the other web server.
When choosing a new port, select ports above 1024 (available to non-root users). Follow the steps below to change the Tomcat port numbers.
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 443 --> <!-- https_connector_placeholder_begin --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="443" minProcessors="5" maxProcessors="75" enableLookups="false" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true">Change the default HTTPS port number from 443 to a port that is not already in use. For example, change the number from 443 to 8443, shown in red below. After editing, the entry should look like this:
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 --> <!-- https_connector_placeholder_begin --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8443" minProcessors="5" maxProcessors="75" enableLookups="false" acceptCount="100" debug="0" scheme="https" secure="true" useURIValidationHack="false" disableUploadTimeout="true"><!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 80 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="80" minProcessors="5" maxProcessors="75" enableLookups="false" redirectPort="443" acceptCount="100" debug="0" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true" /><!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8880 --> <Connector className="org.apache.coyote.tomcat4.CoyoteConnector" port="8880" minProcessors="5" maxProcessors="75" enableLookups="false" redirectPort="8443" acceptCount="100" debug="0" connectionTimeout="20000" useURIValidationHack="false" disableUploadTimeout="true" />Now that Java and Tomcat are installed, you are ready to install Reflection for the Web.
Follow these steps to install and configure Reflection for the Web 2008.
jar -xf /usr/local/jakarta-tomcat/webapps/rweb.warThis extracts the Reflection for the Web files and creates the Reflection for the Web directory structure.
<web-app> <context-param> <param-name>ReflectionData</param-name> <param-value>/usr/local/ReflectionData</param-value> </context-param> <context-param> <param-name>sslport</param-name> <param-value>8443</param-value> </context-param> |
Note: In Reflection for the Web 2008, the sslport parameter is located in the PropertyDS.xml file, which is located in the ReflectionData directory. To modify the port value, you must edit PropertyDS.xml.
If you do not plan to use HTTPS, skip to the next section, Starting Tomcat.
If you plan to use HTTPS to access the web server, you must use a server certificate.
You can configure Reflection to use either a self-signed certificate, or a Certificate Authority (CA) signed SSL server certificate. For information about Tomcat and CA-signed certificates, see Technical Note 1702.
Follow the steps below to start the Certificate Wizard, and then follow the Wizard instructions to create a self-signed certificate or to import a CA-signed certificate.
Note: This command must be run from the console that has a graphical UI or from a graphical user interface, such as Reflection X.
java -cp /usr/local/jakarta-tomcat/WRQUtilities/KeyToolsPro_jce1-2-1_1of2_signed.jar:/usr/local/jakarta-tomcat/WRQUtilities/CertWizard.jar runNote: On some systems, you may need to remove "run" from the command.
To start Tomcat:
./startup.shNote: There is no visible indication in the shell when startup.sh has successfully started Tomcat, and it may take a while before Tomcat is fully started and responsive on its listening ports. Use the ps or top command to see if it is running.
To start Reflection for the Web Administrative WebStation, open your web browser and enter the appropriate URL for your configuration into the Address field, replacing the <server name> and <port #> sections with your site specific information:
https://<server name>:<SSL port #>/rweb/AdminStart.htmlhttp://<server name>:<http port #>/rweb/AdminStart.htmlNote: By default, the administrative password is admin.
If you need to stop Tomcat, navigate to /usr/local/jakarta-tomcat/bin and enter:
./shutdown.shFor information about manually installing and configuring Reflection for the Web's security proxy server feature on UNIX systems that are not supported by the automated installation methods, see Technical Note 1812.
Note: Beginning in Reflection for the Web 2008, the security proxy server is not included in the Standard Edition.
To enable the optional metering feature in Reflection for the Web, see Technical Note 1824.
If you experience difficulties getting Tomcat to start, or getting Reflection for the Web 2008 to load, check the log files located at /jakarta-tomcat/logs.