Web Client

Configure the webplm.properties File

The following sections of the webplm.properties file can be configured. The file can be found in a .war file (in the web application WEB-INF directory).

Setting the compatibility mode (Internet Explorer 11)

To ensure that the Web Client is working with Internet Explorer 11, the compatibility mode is set in the configuration file webplm.properties:

axalant.web.ie_compatibility_mode=EmulateIE9

Possible values are:

EmulateIE9 (default)
EmulateIE8

If this is line is missing in the file webplm.properties, the compatiblity mode is defined by the general Compatibility settings in the Internet Explorer 11.

When starting the Web Client in the Internet Explorer the line <META http-equiv="X-UA-Compatible" content="IE=EmulateIE9" /> is added to the HTML code and will be interpreted by the Internet Explorer. The HTML pages of the Web Client will be rendered in "Internet Explorer 9" compatibility mode.

Any global settings in the Internet Explorer ( Tools -> Compatibility View settings -> checkbox "Display intranet sites in Compatibility View" ) will be ignored.

Firefox / Chrome
Opening the Web Client either in Firefox or Chrome the HTML page also shows the line <META http-equiv="X-UA-Compatible" content="IE=EmulateIE9" /> but this will be ignored.

Edge Browser
Nothing is added to the HTL pages when opening the Web Client.

Customize the Logo

In order to customize the header image and link, edit the properties.

Set the properties for headerLink and headerImage to add your logo and web address.

For example:

axalant.web.headerLink=http://www.oracle.com
axalant.web.headerImage=axalant/orc_logo.png

A customized logo needs to be added to the .war file.

Setting the Timeout Value

Agile e6 ships with a default timeout setting of 900 seconds (15 minutes) for an inactive Client. To better preserve end user work sessions, it is recommended to set this value to at least 3600 seconds (1 hour).

The timeout value is set in the file webplm.properties.

The following line controls the number of seconds for timeout:

axalant.web.sessionTimeout=900

Single Sign On

From Agile A9 to Agile e6

When the Single Sign On is activated for Agile A9 and Agile e6, the following configuration parameter has to be set to True to allow switching between Agile A9 to Agile e6. The User ID is passed on and therefore an additional login is not required.

axalant.web.enable.uid=[false|true]
True = activated
False = deactivated

By default this configuration parameter is set to False!

From Agile e6 to Different Clients

When Single Sign On is activated for Agile e6, the following configuration parameter has to be set to True to allow switching between different Agile e6 clients. An additional login is not required.

This can be used, e.g. for the Lightweight Reporting.

axalant.web.enable.ticket=[false|true]
True = activated
False = deactivated

By default this configuration parameter is set to False!

Enable Old URL Format

To enable the old URL format, the following configuration parameter has to be set to True.

axalant.web.enable.load=[false|true]
True = activated
False = deactivated

Configure the Default Sub-List Size

If the SDI mode of the client is switched off the size of the sub-list depends on the size of the mask if the width is set to 0. This does not apply to the Web client. It uses the default values as described below. These values can be adjusted accordingly.

To configure the size of a mask, the following lines need to be changed.

If the mask length is 0 the default value (here: 13) can be overwritten with the configuration file parameter:
axalant.web.sublist_width=<number of columns>

If the mask width is 0 the default value (here: 85) can be overwritten with the configuration file parameter:
axalant.web.sublist_height=<number of rows>

Change the Default Layout

Add parameter axalant.web.defaultRepositoryLayout=TOPWEB to the webplm.properties file.

Create a default TOPWEB.
The value of this default contains the DTV menu name with which the layout can be configured.

Create the menu selections for the different panes.

The following selection names are important:

Selection Name	Userexit	Parameter	Description
WEB-APP-INFO	web_app_cmd	OPEN-JSP jspaxalant/elements/infoHeader.jsp	Used for info pane. The parameter must be a JSP page. Default page is "/jspaxalant/elements/infoHeader.jsp"
WEB-APP-MENU	-	-	Used for the menu pane. Parameter is the name of the top menu.
WEB-APP-SHORTCUTS	-	-	Used for the toolbar.
WEB-APP-PANE-{id}	web_app_cmd		Userexit is used for different purposes, e.g. main pane, browser pane or message pane. For the Main pane, the parameter can be "SEARCH" to display the multiobject search form. For the message pane the parameter has to be MESSAGE. For the browser pane the parameter has to be EXPLORE.

Create the menu for the layout.
The name has to be the same as the value of the created default TOPWEB.

Add for each pane the corresponding selections.

TOPWEB Menu

Geometry Data

The geometry data can be applied for menu selections which start with WEB-APP-PANE.

Table Column	Description
Row	Has no influence on the layout.
Column	Different column numbers split the window vertically.
Length	Size of the ratio when the panes are split vertically.
Width	Size of the ratio when the panes are split horizontally.

Different options can be added to the Description (T_SELECTION.C_DESCRIP_[LANG]) field. Every entry has to be separated by a semicolon (;).

The options must start with a hash sign (#):

All language fields are filled at the same time.

Description Entry	Description
c=1	Pane is closeable
c=0	Pane is not closeable
s=1	Pane has a content stack (allows to move forward or backward in the main pane)
s=0	No content stack
a=1	Activated
a=0	Not activated

After updating the webplm.properties file the web application has to be stopped and started again so that the modifications become effective.