WebNow on WebSphere - Product Documentation

WebNow on WebSphere - Product Documentation
WebNow on WebSphere
Installation and Setup Guide
Perceptive Content, Version: 7.0.x
Written by: Product Knowledge, R&D
Date: August 2015
© 2015 Lexmark International Technology, S.A. All rights reserved.
Lexmark is a trademark of Lexmark International Technology, S.A., or its subsidiaries, registered in the U.S. and/or
other countries. All other trademarks are the property of their respective owners. No part of this publication may be
reproduced, stored, or transmitted in any form without the prior written permission of Lexmark.
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Table of Contents
About WebNow Installation........................................................................................................................ 4
Install WebNow using WebSphere ............................................................................................................ 4
Download WebNow ............................................................................................................................... 4
Deploy WebNow .................................................................................................................................... 5
Configure the WebNow environment ..................................................................................................... 5
Set up WebNow in WebSphere Management Console......................................................................... 5
Set up WebNow as an enterprise application in WebSphere ................................................................ 6
Setting up SSL ....................................................................................................................................... 6
Install JRE on clients ................................................................................................................................. 6
Automatically install JRE from your intranet .......................................................................................... 7
Automatically install JRE........................................................................................................................ 8
Automatically install JRE through Enterprise Application Deployment .................................................. 8
Manually install JRE............................................................................................................................... 8
About WebNow Configuration ................................................................................................................... 9
Test WebNow ............................................................................................................................................ 9
About logging in through a business application ....................................................................................... 9
About viewing server settings .................................................................................................................... 9
Appendix: Web Configuration Files ........................................................................................................ 10
web.xml properties .................................................................................................................................. 10
WebNow.settings properties ................................................................................................................... 12
Index ........................................................................................................................................................... 19
Page 3 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
About WebNow Installation
WebNow is a thin-client product that runs on a web application server. For product technical
specifications and system requirements, refer to the Technical Specifications document for this product.
The following steps outline the high-level procedures required to install and configure WebNow.
1. Install and test Perceptive Content Server and at least one Perceptive Content Client. Do this
prior to installing the web application server. You use the Perceptive Content Management Console
to set up user authentication for WebNow users. For information on installing the Perceptive Content
Server and Client, refer to the Perceptive Content Installation Guide.
2. Download the WebNow installation zip file. The zip file contains the WebNow application files. You
can download the files from the Perceptive Software Customer Portal at
www.perceptivesoftware.com.
3. Install, start, and test your web application server.
4. Extract and deploy the appropriate webnow.war file for your web application server.
5. Edit the WebNow.settings file to configure the WebNow environment.
6. Install JRE on all client computers. See the Product Technical Specifications document for supported
JREs.
Install WebNow using WebSphere
In the WebNow installation instructions, environment variables represent the default installation path to a
product because the actual path can vary. For example, $WEBSPHERE_HOME represents the default
installation path to WebSphere. When you encounter an environment variable, replace the variable with
the default installation path to that product.
To install WebNow on WebSphere, complete the following steps.
•
Download WebNow.
•
Deploy WebNow.
•
Configure the WebNow environment.
•
Set up WebNow in WebSphere Management Console.
•
Set up WebNow as an enterprise application in WebSphere.
•
Set up SSL.
Download WebNow
Complete the following steps to download WebNow from the Perceptive Software website.
1. Go to www.perceptivesoftware.com and log in to the Customer Portal.
2. In the Product Downloads page, search for all downloadable items for the specific product and
version you want to use. These files may include a product installer, product documentation, or set of
supporting files.
3. Download the relevant files to a temporary directory on your computer.
Page 4 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Deploy WebNow
1. From the temporary directory where you downloaded the installation files, unzip the files.
The zip file contains WAR files for all web application servers. You can remove the WAR files that do
not apply to your web application server.
2. Move the websphere-webnow.war file to the [path]/${WEBSPHERE_HOME}/
/AppServer/installableApps/webnow/ directory. Create the webnow folder if it does not exist.
Note This directory is recommended, but not required. If you want to deploy the webspherewebnow.war file in another directory, move the file to the desired directory.
3. Extract the websphere-webnow.war file into the [path]/${WEBSPHERE_HOME}/AppServer
/installableApps/webnow/ directory.
After deploying the websphere-webnow.war file, you must make some changes to the
WebNow.settings configuration file.
Configure the WebNow environment
1. Open the webnow/WEB-INF directory.
2. Using a text editor, open the WebNow.settings file and configure the following parameters.
1. In host, enter the host name or IP address of the web application server.
2. In port, enter the port number of the Perceptive Content Server.
3. Save and close the WebNow.settings file.
4. If you are deploying WebSphere to multiple application servers, use a zip utility to zip the files back
into the websphere-webnow.war file.
5. Navigate to the [path]/${WEBSPHERE_HOME}/ \AppServer\installableApps\webnow directory
and select the websphere-webnow.war file, created by the WebNow Installation Wizard.
Note If you changed the default file location on the Destination Folder page during installation, the
websphere-webnow.war file is in the directory you specified.
6. Extract the file to the webnow directory.
Set up WebNow in WebSphere Management Console
1. Open the WebSphere Management Console.
2. In the First Steps window, click Start the Server if it is not already running and then click
Administrative Console.
3. In the Login dialog box, in the User ID box, type a user ID, and then click OK.
4. In the left pane, expand Applications, and click New Application.
5. In the right pane, under Install a New Application, click New Enterprise Application.
6. Under Path to the new application, select the Local file system option.
7. In the Full path box, type the location of the websphere-webnow.war file created during the
configuration of the WebNow environment, or click Choose File to locate the file, and click Next.
Page 5 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
8. Under How do you want to install the application? select the Fast Path option.
9. Expand Choose to generate default bindings and mappings, select the Generate Default
Bindings check box, and click Next.
10. On the Step 1: Select installation options page, click Next.
11. On the Step 2: Map modules to servers page, click Next.
12. On the Step 3: Map context roots for Web modules page, in the Context Root box, type
/webnow, and click Next.
13. On the Step 4: Summary page, review the summary, and click Finish.
14. The Installing page confirms that the WAR file installed.
15. Click Save directly to the master configuration.
Set up WebNow as an enterprise application in WebSphere
1. In the main Administrative Console, in the left pane, expand Applications, expand Application
Types, and click WebShere enterprise application.
2. In the right pane, under Enterprise Applications, click websphere-webnow.
3. Under WebNow Module Properties, click Session management.
4. Under General Properties, under Session tracking mechanism, click Enable Cookies
5. Under General Properties, clear the Restrict cookies to HTTPS sessions and Set session
cookies to HTTPOnly to help prevent cross-site scripting attacks check boxes.
6. Under Cookie maximum age, select Set maximum age, type 1800, and click OK.
Note You must set the Cookie maximum age value to a value that is greater than or equal to 60 times
the Session timeout value found in the Session Management General Properties window. The
Session timeout parameter displays in minutes and the Cookie maximum age parameter displays in
seconds. To ensure that the Cookie maximum age value is equal or greater than this amount, multiply
the Session timeout value by 60. For example, if the Session timeout value is 30, multiplying it by 60
equals 1800 (the Cookie maximum age value).
7. Under General Properties, select the Overwrite Session Management check box, and click OK.
8. Under Enterprise Applications, under Message(s), click Save.
9. To enable the WebNow application, under Enterprise Applications, select the webspherewebnow.war application check box, and click Start.
10. Restart the WebSphere service.
Setting up SSL
If you want to configure SSL to use with WebNow, you must do so on your WebSphere web application
server. SSL configuration cannot be completed within WebNow. For more information, refer to the
WebSphere Portal help documentation on the IBM website.
Install JRE on clients
WebNow is a Java-based application. Clients running WebNow require Java SE Runtime Environment
(JRE). Regardless of the web application server you use, the JRE must exist on every client computer
that accesses WebNow. The JRE provides the Java APIs, Java virtual machine, and other components
Page 6 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
needed to run applets and applications written in the Java programming language. Because the version
of JRE you need to install depends on the client's environment, refer to the Product Technical
Specifications document for JRE version information.
Before attempting to download JRE from the Oracle website or from an intranet site, make sure that the
user has access to the web or your intranet. Also, make sure that the user has permission to save the
JRE on the client computer. Use one of the following procedures to install JRE on your client computers.
The following sections describe four methods of installing JRE.
•
Automatically installing JRE from the internet – Use this method if there are network restrictions
around web access or limitations to downloading from the web. For this method, you download the
JRE from the Oracle website to a local intranet location, which is referenced by the web.xml file in
WebNow. The clients access the JRE from the intranet using this reference. When you want client
users to update the JRE, you must go to the Oracle website, download a new JRE, and then place it
in the same location on your intranet for the clients to access.
•
Automatically installing JRE using Internet Explorer – Automatic installation of JRE only occurs
when you are running Internet Explorer (IE) on Microsoft Windows. If you are using another operating
system or browser, choose a different installation option. For the automatic download to occur, the
user on the client computer must have access to the Oracle website.
•
Automatically installing JRE through Enterprise Application Deployment – You might want to
push the JRE out to all users at once. You can do this using SMS, Active Directory, or other similar
“push” software. This section does not describe how to use these types of software, but it provides
general information you use to push the software.
•
Manually installing JRE – If you do not want to install JRE automatically, you can install JRE
manually.
Note If you plan to use a 64-bit web browser, download the 64-bit JRE install package.
Automatically install JRE from your intranet
This JRE installation method is recommended if there are network restrictions around web access or
limitations to downloading from the web. For this method, you download the JRE from the Oracle website
to a local internet location, which is referenced by the web.xml file in WebNow. The clients access the
JRE from the intranet using this reference. When you want client users to update the JRE, you must go to
the Oracle website, download a new JRE, and then place it in the same location on your intranet for the
clients to access.
1. Download the JRE from http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Download the appropriate version for your operating system. For example, for 64-bit Windows,
download the JRE Windows x64 installer, (jre-7uXX-windows-x64.exe).
2. Place the downloaded file on an intranet web server or web application server. For ease of use, you
can place this file in the webnow installation directory.
3. Using Microsoft Windows Explorer, navigate to the WEB-INF folder that is installed with WebNow,
and then open the web.xml file. Modify the web.xml file as follows, where http://intranet_name points
to the location where you placed the JRE in step 2.
<context-param>
<param-name>java-plugin-codebase</param-name>
<param-value>http://intranet_name/jre-6u32-windowsi586.exe#Version=1,6,1,10</param-value>
Page 7 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
</context-param>
Note This is an example only. The version number and other data will differ based on your
environment. In a web browser, verify that the location is a valid URL. WebNow does not validate this
URL. Refer to the “web.xml parameters” section for more information.
4. Restart the web application server so the changes to the web.xml file take effect.
5. Launch WebNow from a client. If the correct version of JRE does not exist on the client, and the client
is running Internet Explorer on Microsoft Windows, WebNow attempts to install the JRE. Depending
on the Windows version and service packs installed, the security warning dialog box may appear.
6. During the JRE installation, we recommend that you select Typical. After the JRE installation
completes, WebNow automatically launches.
Automatically install JRE
The automatic installation of JRE occurs only when you are running Internet Explorer (IE) on Microsoft
Windows. If you are using another operating system or browser, choose a different installation option. For
the automatic download to occur, the user on the client computer must have access to the Oracle
website, http://www.oracle.com.
1. Launch WebNow from a client. If the correct version of JRE does not exist on the client, and the client
is running Internet Explorer on Microsoft Windows, WebNow attempts to download and install the
JRE. Depending on the Windows version and service packs installed, the security warning dialog box
may appear.
2. During the JRE installation, it is recommended that you select Typical. After the JRE installation
completes, WebNow launches.
Automatically install JRE through Enterprise Application Deployment
1. Download JRE from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Download
the appropriate version for your operating system. For example, for 64-bit Windows, download the
JRE Windows x64 installer, (jre-7uXX-windows-x64.exe).
2. After you download the JRE, incorporate the JRE installer with your company's application
deployment software. It is recommended that you install the JRE in "Silent" mode. The following links
describe the options for a silent or unattended installation.
For information on JRE silent installation, go to:
http://www.oracle.com/technetwork/java/javase/downloads/index.html.
Manually install JRE
If you do not want to install JRE automatically, you can install JRE manually.
When you install JRE manually, you must complete the installation for each WebNow client computer.
1. Download JRE from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Download
the appropriate version for your operating system. For example, for 64-bit Windows, download the
JRE Windows x64 installer, (jre-7uXX-windows-x64.exe).
2. Run the JRE installer and follow the installation instructions. During installation, it is recommended
that you select Typical. Depending on the Windows version and service packs installed, the security
warning dialog box may or may not appear.
Page 8 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
3. After the JRE installation completes, WebNow automatically launches.
About WebNow Configuration
Parameters in the WebNow.settings file allow you to configure your individual WebNow implementation
without shutting down the web application server.
You can configure WebNow to do any of the following actions.
•
Share web applications on the same web application server
•
Log in through your business application
•
Log in anonymously or using domain authentication
•
Open only specified file types
•
Apply a web client theme
Test WebNow
1. Start your web application server.
2. Open your Internet browser.
3. In the Address box, type the Error! Hyperlink reference not valid. name>:<port number>/webnow/,
where <server name> and <port number> are placeholders for the name of the computer and the port
number where you installed WebNow. The default port number for WebSphere is 9080.
About logging in through a business application
You can change the WebNow login method used when a business application, like PeopleSoft, calls
WebNow to display a document. In most instances, you do not want the user to enter login information
each time the business application displays a document within a browser session, which is the default
login method. Instead, you can set WebNow to request login information the first time it is called by the
business application. Subsequent calls do not require login information as long as they are made when
the business application browser window is still open.
For example, suppose that you have a business application browser window that uses WebNow links to
access WebNow documents. If you set session logging, your users do not have to log in each time they
access WebNow documents as long as the business application remains open.
About viewing server settings
The Server Settings feature available from the Help menu on the WebNow toolbar allows you to view
selected settings without accessing the server itself or the WebNow.settings file. Settings cannot be
modified in the Server Settings dialog box. Use the Copy to Clipboard function to copy the settings in the
Server Settings dialog box to the Windows Clipboard to simplify diagnosing server issues.
Page 9 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Appendix: Web Configuration Files
This section outlines the configuration files associated with WebNow. To apply the values configured for
the settings in your existing web.xml file to your new WebNow.settings file, you must manually change
the values in the WebNow.settings file using your backed up copy of the web.xml file from the previous
version.
web.xml properties
These are the properties and sample values for the web.xml file. You must restart the web application
server for changes to the web.xml file to take place.
Group
Property Name
Sample Value
Description
Context Properties
Java-plugin-codebase
JRE version 1.7.0_45
The java-plugin- codebase
determines the installation
directory from which you install
the JRE. By default, it installs
from Oracle's website.
However, we suggest you
change this setting to download
from your internal web server.
Doing so provides quicker
download times and avoids
network proxy issues.
<context- param><paramname>java-plugincodebase</paramname><paramvalue>http:// java.sun.com/
products/plugin/
autodl/jinstall-1_7_0_45windowsi586.cab#Version=
1,7,0,45</param- value>
For further information, see the
"Install JRE" section.
The combination of java-classid
and java- version determines
which JRE is downloaded (if not
already installed) and used by
WebNow. Both parameters
must be in sync.
Context properties
java-classid
JRE version 1.7.0_45
context- param><paramname>javaclassid</paramname><paramvalue>CAFEEFAC-00160000-0000ABCDEFFEDCBA</
param-value></ contextparam>
The java-plugin- codebase
determines the installation
directory from which you install
the JRE. By default, it installs
from Oracle's website.
However, we suggest you
change this setting to download
from your internal web server.
Doing so provides quicker
download times and avoids
network proxy issues.
For further information, see the
"Install JRE" section.
The combination of java-classid
and java- version determines
which JRE is downloaded (if not
already installed) and used by
WebNow. Both properties must
be in sync.
Page 10 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Property Name
Sample Value
Description
Context properties
java-version
JRE version 1.7.0_45
The java-plugin- codebase
determines the installation
directory from which you install
the JRE. By default, it installs
from Oracle's website.
However, it is recommended
that you change this setting to
download from your internal
web server. Doing so provides
quicker download times and
avoids network proxy issues.
<context- param><paramname>javaversion</paramname><paramvalue>1.6</ paramvalue></ context-param>
For further information, see the
"Install JRE" section.
The combination of java-classid
and java- version determines
which JRE is downloaded (if not
already installed) and used by
WebNow. Both properties must
be in sync.
Servlet and Servlet
mapping
servlet- name
com.imagenow.webno
w.rss
The web application server
uses this property. It should not
be changed.
Servlet and Servlet
mapping
servlet-class
com.imagenow.webno
w.rss
The web application server
uses this property. It should not
be changed.
Servlet and Servlet
mapping
url-pattern
/WebNowRSS
The web application server
uses this property. It should not
be changed.
MIME mapping
extension
doc
The file type WebNow opens
using the application specified
in the mime-mapping property.
For example: doc
ppt xls
MIME mapping
mime-type
application/msword
The application WebNow uses
to open files of the file type
specified in the extension
property. For example:
application/msword
application/vnd.ms- powerpoint
application/excel
Page 11 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
WebNow.settings properties
This section contains two tables that list the parameters for the WebNow.settings file. These settings
follow the order of the entries in the WebNow.settings file. The following table details the properties in
the [Servlet] and [Logging] sections of the file. These settings are not sent to the client.
Group
Setting
Options
Description
[Application
server settings]
host
123.456.78.90
The host name of the WebNow application server.
Can specify the host name or the IP address.
port
6000
The port number of the Perceptive Content Server.
By default, Perceptive Content utilizes port 6000.
form-presentationcache-timeout
1
native-support
TRUE
FALSE
When set to TRUE, you can view reports in
WebNow Explorer. The default is FALSE, which
enables you to view reports in their native
application.
When set to TRUE, the download size of WebNow
increases by 400k. If you are not using Adobe
Acrobat Reader documents, it is recommended that
you keep this set to FALSE.
native-doc-viewer
TRUE
FALSE
native-report-viewer
TRUE
FALSE
native-emailsupport
TRUE
load-balancingcookie-enabled
TRUE
load-balancingcookie-name
NLB_ID
FALSE
FALSE
Overrides the native-support setting. You can set
native-doc-viewer to TRUE so you can open
reports inside WebNow Explorer. This setting is
commented out by default.
Overrides the native-support is setting. You can set
native-report-viewer to TRUE so you can open
reports in their native application. This setting is
commented out by default.
Overrides the native-support setting. You can set
native-email-support to TRUE so you can email a
document as an attachment. This setting is
commented out by default.
Indicates whether WebNow inserts a persistent
cookie that devices can use to balance network
traffic.
If load-balancing-cookie-enabled is TRUE, this
setting indicates the name of the cookie.
The default is NLB_ID.
load-balancingcookie-lifetimeminutes
1440
Indicates the number of minutes the cookie is valid
before WebNow issues a new cookie.
The default is 1440.
Page 12 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Setting
Options
Description
ImageNow
Server
interaction
heartbeat
TRUE
Determines whether to send a heartbeat message
to the server at a regular interval to maintain the
session when no information is sent.
FALSE
By default, this property is set to FALSE. If set to
TRUE, the WebNow session will never timeout.
The recommended setting is FALSE.
Login settings
logontimeout
Any positive integer
The socket timeout for the logon process in
seconds. The default for this property is 30.
defaulttimeout
Any positive integer
The socket timeout for communications with the
Perceptive Content Server in seconds. The default
for this property is 30.
searchtimeout
Any positive integer
The socket timeout for when performing a Simple,
SQL, or Content search in seconds. The default for
this property is 30.
ermsearchtimeout
Any positive integer
The socket timeout for when performing an ERM
search in seconds. The default for this property is
30.
sso.key
Any valid string
When single sign-on is enabled, this setting
specifies the token WebNow uses with Perceptive
Content Server to indicate successful
authentication.
sso.method
Any valid string
Based on the provider, this setting specifies the
type of single sign on used.
Page 13 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
These settings follow the order of the entries in the WebNow.settings file. The following table details the
properties in the [WebNow] section of the file. These settings are sent to the client.
Group
Setting
Options
Description
Login settings
login-retryattempts
Any positive
integer
Specifies the number of unsuccessful login attempts
allowed.
Note If experiencing log-in issues with Tomcat web
application server, increase this value to 5 or 10.
anonymous
TRUE
FALSE
Whether or not to display the Anonymous logon
option in the logon screen.
When the value is TRUE, the anonymous check box
displays in the logon screen.
When the value is false, the anonymous check box is
hidden in the logon screen.
Your Perceptive Content Server must support
anonymous logon to use this option. The
anonymous.logon.enabled setting in the
inserver.ini must be set to TRUE if you want to use
anonymous logon.
sso
TRUE
Specifies whether single sign-on is enabled.
FALSE
Notes
To enable single sign-on for WebNow, you must also
configure the single sign-on settings in inow.ini on the
Perceptive Content Server.
When single sign-on is enabled, your single sign-on
provider supplies authentication information. Users
cannot log in to WebNow anonymously.
Client settings
animate
TRUE
FALSE
Determines whether to enable page animation. By
default, this property is set to TRUE.
If you operate in a Citrix environment or send full
screen image files over a network, setting this to
false will help with system performance.
domainauthentication
TRUE
FALSE
You can start WebNow, while logged in on a
Windows machine to an NT domain, and completely
bypass the log-in screen.
When the value is TRUE, domain authentication is
enabled. If you enable domain authentication, you
must enable the client validation setting and configure
your domain name in the inow.ini.
When the value is FALSE, domain authentication is
disabled. The default value is FALSE.
Page 14 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Client settings
(continued)
Setting
Options
Description
large-file-uploadsupport
TRUE
When set to TRUE, you can use streaming to upload
files up to the size specified in the max-uploadfilesize property.
FALSE
Note This setting is not supported when using the
JRun web application server.
When set to FALSE, file uploading is not streamed
and is limited by the amount of available RAM. If you
use JRun, you must set this property to FALSE. The
default value is FALSE.
max-uploadfilesize
Any number
between 1 and 255
Specifies the maximum file size WebNow allows you
to upload. Valid numbers range from 1 to 255 and
represent the maximum uploadable filesize in MB.
The default setting is 5, which would equate to a
maximum uploadable file size of 5 MB.
remembersession-enabled
TRUE
In WebNow, as long as you do not click Disconnect,
you remain connected unless your session times out
from inactivity. When remember-session-enabled is
set to true, you can log in during a session without
the need to provide login information each time you
connect. The default setting is false, which requires
you to enter your user name and password each time
you click a WebNow URL.
FALSE
Notes
The remember-session-enabled setting is not
supported if you are using Tomcat as your web
application server.
url-redirect-ondisconnect
URL
The URL to which users redirect after the current
WebNow session disconnects or times out.
co-branding
GIF, JPG, or PNG
file.
Displays a co-branded logo alongside of the WebNow
logo. You must place this logo file in the webnow
folder. If no file is provided, there is no co-branding.
The image height cannot exceed 62 pixels.
Page 15 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Setting
Options
Description
Client settings
render-forms-onclient
TRUE
Indicates whether the servlet sends form resources,
XSL presentations, and form data instances to the
applet to be rendered.
(continued)
FALSE
When this parameter is set to TRUE, the servlet
sends the form resources, XSL presentations, and
form data instances to the applet.
When this parameter is set to FALSE, the servlet
does not send the form resources, XSL
presentations, and form data instances to the applet.
Instead, the servlet performs XSLT processing in
place and then delivers the URL to the applet. The
default value for this parameter is FALSE. In most
cases, keep this parameter set to FALSE to reduce
load on the servlet.
Viewer settings
client-autotimeout
Any positive
integer
If client-autotimeout-enabled is set to TRUE, this
setting specifies the number of minutes WebNow
waits before timing out. The default is 30.
client-autotimeoutenabled
TRUE
When set to TRUE, WebNow automatically times out
based on the client-autotimeout value. The default is
FALSE.
client-autotimeoutwarning
Any positive
integer
If client-autotimeout-enabled is set to TRUE, this
setting specifies the number of seconds before
WebNow times out a warning message displays. The
minimum number of seconds you can specify is 10.
The default is 60.
global-max-openpages-enabled
TRUE
When set to true, this setting specifies that only a set
number of pages per document appear to the user.
The number of pages is set through global-maxopen-pages.
FALSE
FALSE
When set to FALSE, the user can change the number
of pages through WebNow Viewer.
User
configuration
settings
global-max-openpages
Any positive
integer
When global-max-open-pages-enabled is set to true,
this setting specifies the maximum number of pages
that can display for a document. If you experience
low memory, setting this property to a lower value
may resolve the issue.
text-extensions
File extensions
A comma separated list of the file types to open as
text within the Viewer window.
preferencesaving-allowed
TRUE
Whether or not to save the individual user
preferences specified in the Properties.ini file for
WebNow. If set to TRUE, users can save individual
WebNow preferences. If set to FALSE, they cannot.
The default is TRUE.
FALSE
Page 16 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Setting
Options
Description
Document title
bar
configuration
document-viewertitle
Any string followed
by zero or more of
the following
macros:
This optional setting changes the text in the
Document Viewer title bar. The string can contain any
literal text followed by macro replacement macros
shown. The % delimiters are required.
%Drawer%
%Folder%
The string in the settings file is the base string, and
the code appends the following string based on
viewer status:
%Tab%
Associated project information
%F3%
Workflow mode
%F4%
Version number (if in version control)
%F5%
Checked out
%DocType%
Example
All macros are
case sensitive.
document-viewer-title=Document - %DocType%
%FolderType%
This optional setting changes the text in the Folder
title bar. The string in the settings file is the base
string, and the code appends the following string
based on viewer status.
Folder title bar
configuration
folder-viewer-title
%FolderName%
Example
folder-viewer-title=Folder - %FolderType% %FolderName%
Client side
color themes
theme
Locale specific
disclaimers
disclaimer
Theme file
TRUE
FALSE
In WebNow, you can specify a web client theme to
use. The THEME file must exist in the WEB-INF
directory. Any number of THEME files can exist in
this directory, but only one theme can be specified in
this setting at one time.
Displays the value as disclaimer text in the bottom
portion of the login screen.
Notes
For special characters, such as ampersand (&),
quotes ("), less than (<), and greater than (>), use
HTML formatting codes.
For disclaimers in a language other than English,
define the settings below.
For alternate language support, complete these
settings. Supported languages are English, Spanish,
German, and French. Multiple disclaimers are
supported if you need to use more than one
language.
disclaimer_es
Disclaimer in Spanish.
disclaimer_fr
Disclaimer in French.
Page 17 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Group
Setting
Options
Description
disclaimer_de
Disclaimer in German.
disclaimer_pt_BR
Disclaimer in Brazilian Portuguese.
disclaimer_nl
Disclaimer in Dutch.
disclaimer_it
Disclaimer in Italian.
Environment
settings
clusteredenvironment
TRUE
AppletParams
image
Image filename
Specifies the static image to display during applet
startup. This setting is commented out by default.
centerimage
TRUE
Specifies whether to center the splash screen image.
This setting is commented out by default.
FALSE
FALSE
boxborder
TRUE
FALSE
Logging
log
Default is FALSE.
TRUE
FALSE
Specifies whether to apply a border around the
splash screen image. This setting is commented out
by default.
Specifies whether to log WebNow errors,
informational messages, and warning messages.
When the value is TRUE, logging is enabled. When
the value is FALSE, logging is disabled. The
recommended setting is TRUE. The default setting is
FALSE.
logdirectory
Directory path
Specifies the file directory in which WebNow will store
logged error and warning messages. This path must
exist.
log-transformerwarnings
TRUE
Specifies whether to log warning messages
associated with merging a form presentation with
form data. Set this property to TRUE when
developing a new form. The default is FALSE.
FALSE
Page 18 of 20
W e b N o w o n W i n d o ws f o r W e b S p h e r e I n s t a l l a t i o n G u i d e
Index
Business application
logging in ........................................................ 9
Enterprise Application ..................................... 6
Enterprise Application Deployment .................... 8
JRE
parameters ................................................... 10
WebNow Installation
about .............................................................. 4
on Windows using WebSphere ...................... 4
WebNow.settings ....................................... 4, 5, 9
installing .......................................................... 6
parameters ................................................... 12
SSL..................................................................... 6
WebSphere Management Console................ 4, 5
web.xml .......................................................... 7, 8
Page 19 of 20
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising