Environment
Reflection for the Web 2011 (All Editions)
Reflection Security Gateway 2014
Situation
Resolution
Prerequisites
Beginning with Reflection for the Web 2011, Tomcat no longer ships as part of the manual install. Therefore a servlet container or application server is required to be preinstalled on the mainframe (such as Tomcat, WebSphere, or Dovetail's T:Z Quickstart for Tomcat, for example).
To install with WebSphere, see KB 7022220.
Replace Current Policy Files with Unlimited Strength Jurisdiction Policy Files
IBM's Java SDKs ship with limited jurisdiction policy files. If you use HTTPS or SSL, we strongly recommend that you replace the current policy files with unlimited strength jurisdiction policy files, which can be obtained from the following link. Locate and download the appropriate jurisdiction policy files for your environment to your workstation.
Unpack the ZIP file that you downloaded from IBM. To replace the files on the mainframe, local_policy.jar and US_export_policy.jar, transfer (in binary mode) the files from your workstation to the <java install directory>/jre/lib/security/ directory on the mainframe:
<java install directory>/jre/lib/security/local_policy.jar<java install directory>/jre/lib/security/US_export_policy.jarInstalling and Configuring the Management Server on the Mainframe
Since Java and the application server are already installed, you are ready to install the Reflection Management Server on the mainframe:
- Create an rweb directory under ../application_server_root/webapps/.
- Using an FTP client, transfer (in binary mode) the file following file located with the downloaded product files (or on the Reflection CD):
Reflection for the Web 2014 or Reflection Security Gateway 2014: \install_manual\components\rweb.war
Reflection for the Web 2011: \install\nonautomated\rweb.war
to the ../application_server_root /webapps/rweb directory on the Mainframe.
- Navigate to ../application_server_root /webapps and enter the following command to extract the Reflection files:
jar –xvf rweb.warThis command extracts the Reflection files and creates the Reflection directory structure.
- Using an FTP client, transfer (in binary mode) the web.xml file to your PC from the mainframe:
../application_server_root/webapps/rweb/WEB-INF/web.xml- Edit the web.xml file:
- Open the file web.xml in a text editor on your PC.
- In the web.xml file, replace the value for rwebdata_location_placeholder with /<PathTo>/ReflectionData (in our example, /u/ReflectionServer/ReflectionData). If the ReflectionData directory does not already exist, you must create it.
These values configure SSL to use the specified port. The resulting lines look like this:
<web-app><context-param><param-name>ReflectionData</param-name><param-value>/u/ReflectionServer/ReflectionData</param-value></context-param>- Save the file.
- Using an FTP client, transfer (in binary mode) the web.xml file from your PC to the mainframe directory below:
../application_server_root/webapps/rweb/WEB-INF/web.xmlNote: Permissions for the web.xml file should be set to 644.
Editing the PropertyDS.xml file
If you are using security, you will need to update the file, PropertyDS.xml, which is stored in the ../ReflectionData folder. Note: The file will be created once the application server is started.
- Using an FTP client, transfer (in binary mode) the PropertyDS.xml file to a temporary directory on your workstation.
- Open PropertyDS.xml in a text editor on your workstation.
- In the PropertyDS.xml file replace the value “443” with the value you are using for SSL (in our example, 8443).
Example:
<CORE_PROPERTY NAME="CS.HostPort"><STRING>8443</STRING></CORE_PROPERTY>- Using an FTP client, transfer the PropertyDS.xml file (in binary mode) to the ../ReflectionData directory.
Launching Reflection
Reflection opens by launching http://myhost.mycompany.com:port/rweb/AdminStart.html.
For example:
http://10.10.2.115:8081/rweb/AdminStart.htmlThe default password for Reflection Administrative WebStation is admin.