performance from applications running in the Liberty profile of the IBM
WebSphere Application Server (WAS) on the IBM Power System S9xx and L922
systems recently made available from IBM
Before installing the Reflection for the Web or Reflection Security Gateway (hereinafter called Reflection) portlet, you must have the following installed and configured.
Prior to installing the portlet, you must obtain the RWebPA.war file, which you will use to install the Reflection portlet.
With Reflection installed and configured on your application server, you are ready to install the Reflection portlet to the WebSphere Portal Server.
There are multiple pages listing the portlets. You can use the Search tool to locate the RWeb portlet; select “Title starts with” or “Title contains” from the Searchby drop-down list, and enter rweb in the Search field. If RWeb portlet is not listed, you may have to logout and log back into the portal server for the portlet to be listed.
To launch a session automatically when the user opens the portal page, enter that specific session’s URL (which can be copied from the Session Manager on the Administrative WebStation) as the RWebURL value.
You can now add the Reflection portlet to any of the WebSphere portal pages.
The RWebPA.properties file contains the shared secret that the portlet uses to authenticate to the Reflection server. The shared secret needs to match what is configured on the Reflection server.
Replace sharedsecret (case sensitive) with the value you want to use to authenticate the portlet to the Reflection for the Web server.
If you run Reflection on a WebSphere Application Server (WAS), then you must enable “URL rewriting” on the WAS server.
If you run Reflection on another application server (not WAS), skip this section and proceed to Adding the Portlet to the WebSphere Portal (An Example).
Note: At this time, you can enable “URL rewriting” on the WAS at the server level only, not at the application level.
The following steps describe one way to add the Reflection portlet to a WebSphere portal page.
Follow these steps to ensure that the portlet works.
Before You Begin
Before installing Reflection for the Web or Reflection Security Gateway (hereinafter referred to as Reflection), you must have all of the following installed and configured on your host.
Installing Reflection for the Web
After the WebSphere Application Server has been properly installed and tested, follow the steps below to install Reflection.
Prepare the rweb.war File
Follow these steps to prepare the rweb.war file:
Reflection for the Web 2014 or 2011 or Reflection Security Gateway 2014: /install_manual/components/rweb.war
Reflection for the Web 2008: /nonautomated/rweb.war
Note: When renaming the file, you may receive an error stating that the file may become unstable. Click Yes to proceed.
Update the WebSphere Server Settings
Follow the steps below to update the WebSphere Server settings:
C:Temprweb.war –or– /u/local/rweb.war
The new rweb.war application is installed and the Administration Console screen opens. If you expand the Applications menu and select Enterprise Applications, the application state for rweb should be Stopped.
Click Save to update the master configuration.
Update the web.xml File
There are two copies of the web.xml file, located in the following directories:
– and –
Note: If this is a WebSphere Application Server Network Deployment, there is an additional web.xml that must be updated:
In both (or all three) files, locate the <param-name>ReflectionData</param-name> section and modify the file to include the data in red below, entering your path to ReflectionData (for example, C:ReflectionData or /u/local/ReflectionData), and substituting your own sslport value for 443. Note: If the ReflectionData directory does not already exist, you must manually create it.
Reflection stores configuration information in the ReflectionData directory. If this is a UNIX installation, ensure that rights are set so that Reflection can write to the ReflectionData directory.
Note: In Reflection, the sslport parameter is located in the PropertyDS.xml file, which is located in the ReflectionData folder. If you want to use a port other than default port 443; you must edit PropertyDS.xml after Reflection for the Web is started in WebSphere.
Once you have updated and saved both (or all three) of the web.xml files, return to the Administrative Console window and follow the steps below.
Reflection is now installed. To access Reflection, open a browser and enter the URL, WAS port, and context root to your server.
For example: http://rweb.atm.com:9080/rweb
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:
– Windows:C:Program FilesJavajre<version>libsecurity