Technical Note 2173
Last Reviewed 09-Jul-2015
Reflection for the Web 2014 (All Editions)
Reflection for the Web 2011 (All Editions)
Reflection for the Web 2008 (All Editions)
Reflection Security Gateway 2014
WebSphere Application Server Express version 6.x or higher
This technical note provides steps and suggestions for installing Reflection for the Web on an IBM i (iSeries or AS/400) with IBM WebSphere Application Server Express 6.
Before You Begin
Before installing Reflection for the Web, we recommend that you have all of the latest Cumulative Fixes for your IBM i operating system as well as any Group Program Temporary Fixes (PTFs) for the following applications:
- WebSphere Application Server Express 6 Group Program Temporary Fixes (PTFs)
- Java Developer Kit 1.5 or higher for Reflection for the Web or Reflection Security Gateway
- Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files. For details, see Applying the JCE Unlimited Strength Jurisdiction Policy Files.
- IBM HTTP Server Group Program Temporary Fixes (PTFs)
Prepare the rweb.war File
Follow these steps to prepare the rweb.war file:
- Expand (Unzip) the Reflection for the Web installation files, and then copy the rweb.war file from the /nonautomated folder to a temporary folder on your PC.
- During download, the rweb.war file may be named rweb.war.zip. If so, rename rweb.war.zip to rweb.war.
Note: When renaming the file, you may receive an error stating that the file may become unstable. Click Yes to proceed.
- Using an FTP client, transfer the rweb.war file (using binary transfer type), to the following IFS directory on your AS/400.
By default, the full path is:
Verify that the QWAS[n] Subsystem is Started
Before proceeding, make a terminal session connection to your IBM i and use the WRKACTJOB command to verify that the QWAS[n] subsystem is started.
If QWAS6 is not started, refer to your WebSphere documentation for directions on starting the subsystem. QWAS6 must be started before you proceed.
Configure the iSeries Express Server
Follow the steps below to configure the iSeries Express Server for Reflection:
- Open the IBM WebSphere Application Server Express Administration Console and click IBM Web Administration for i. By default, this is accessed from http://<myserver>:2001.
- On the Application Servers tab, expand Applications and click Manage Installed Applications.
- On the Manage Installed Applications panel, click Install.
- On the Install New Application panel, browse to the rweb.war file. By default, this file is located in the /QIBM/UserData/WebSphere/AppServer/V6/Base/profiles/default/installableApps folder.
- Select the radio button for "Application is contained in a WAR file" and wait for the page to update.
- In the Context Root field, enter /rweb, and then click Next.
- Verify the application name is rweb.war. If you would like to have the JSPs compiled on application startup, rather than the first time the page is viewed, check the box for Pre-compile JSPs. (Note that this extends the time for the rweb application to start under Websphere the first time after install.)
- Click Next.
- Choose your Virtual Host or click Next to accept the defaults.
- Print the Summary page for your records, and then click Finish.
The new rweb.war application is installed and the Manage Installed Applications screen opens.
Note: It may take quite a while for the new rweb.war application to be created. The current state of the process is displayed in the upper-left corner of the window.
Update the web.xml Files
Reflection for the Web stores configuration information in the ReflectionData directory. You must create a ReflectionData directory, if one does not already exist, in a location that is accessible to Reflection for the Web (for example, /usr/local/ReflectionServer/ReflectionData). Ensure that rights are set so that Reflection for the Web can write to the ReflectionData directory.
Now, edit the web.xml file to specify the ReflectionData directory location:
- Navigate to the /usr/local directory and create a new directory named ReflectionData (if one does not already exist).
- There are two copies of the web.xml file, located in the following directories:
- Open each file, web.xml, in the text editor of your choice.
- In each web.xml file, locate the <parm-name>ReflectionData</parm-name> section and modify the file to specify the ReflectionData directory location. For example,
Starting Reflection for the Web
Once you have updated and saved both of the web.xml files, return to the Manage Installed Applications window and follow the steps below.
- Select the Application Server tab.
Check the serverís status. The status is displayed in the upper left corner. If the server is not running, click Start (the green arrow).
- Select Manage Installed Applications from the menu on the left.
- Select the rweb application you just installed and click Start. Verify that RWEB has been started and has a status of Ready.
Reflection is now installed. To access Reflection for the Web, open a browser and enter the URL, WAS port, and context root to your server.
Applying the JCE Unlimited Strength Jurisdiction Policy Files
Reflection Security Gateway 2014 R2 and Reflection for the Web 2014 R2 require the Java Cryptography Extension (JCE) Unlimited Strength Policy Files. "Unlimited strength" policy files contain no restrictions on cryptographic strengths, in contrast to the "strong" but limited cryptography policy files bundled in a JRE.
To apply the policy files:
- Download the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files from Oracle or IBM. Be sure to download the correct policy file updates for your version of Java:
- Uncompress and extract the downloaded file. The download includes a Readme.txt and two .jar files with the same names as the existing policy files.
- Locate the two existing policy files local_policy.jar and US_export_policy.jar in the following directory:
- UNIX: <java-home>/lib/security
- Windows: C:\Program Files\Java\jre<version>\lib\security
- Replace the existing policy files with the unlimited strength policy files you extracted.