Server Nodes

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 3 Configuring the Client Application : Server Nodes

Server Nodes

When the client application Login screen is displayed, the Server field drop-down list will contain a list of TIBCO iProcess Objects Servers that the user can log into:

This list of servers is controlled using the ServerNodes record in the client application’s configuration file.

During the iProcess Workspace (Browser) installation process, you enter the information for one iProcess Objects Server. This section describes how to add additional entries to the ServerNodes record if you would like more than one server to appear in the Server field drop-down list.

To configure the server nodes for your installation:

1.

Open the appropriate config.xml file, depending on whether you are configuring the iProcess Client or a custom application. For information about the file’s location, see Configuration Files.

2.

Locate the ServerNodes record:

The first record should reflect the entries that were entered during the installation. The elements in this record can be modified if the information is no longer correct (for instance, the TCP port has changed for that server).

Placeholders have been provided for two additional iProcess Objects Servers.

3.

To configure additional servers, remove or move the appropriate comment delimiters from the “Server Two” or “Server Three” record, then enter the appropriate information in the following elements:

−

displayNodeName: The name that you would like displayed in the iProcess Workspace (Browser) Login to field drop-down list. This is the name the user would select when choosing a server to log into.

−

<ComputerName>: The name of the machine on which the TIBCO iProcess Objects Server is installed.

−

<IPAddress>: The IP address of the machine on which the TIBCO iProcess Objects Server is installed. You can enter the name of the host machine in this field, as long as that name resolves to the IP address of the machine where the iProcess Objects Server is running. Note, however, that this name must be able to be resolved by the machine on which the Action Processor is running.

Note that an IPv6 IP address can be used if the TIBCO iProcess Objects Server uses IPv6 addressing (an example IPv6 address is: he80::c531:b7a1:8922:ab12%13).

−

<TCPPort>: The TCP port number used by the TIBCO iProcess Objects Server. (The TCP port used by the server is specified using the iProcess Objects Server Configuration Utility in Windows systems (SWDIR\bin\SWEntObjSvCfg.exe), or by editing the iProcess Objects Server configuration file in UNIX systems ($SWDIR/seo/data/swentobjsv.cfg). For more information, see the TIBCO iProcess Objects Server Administrator’s Guide.)

−

<Name>: The name of the TIBCO iProcess Engine / iProcess Objects Server to which the user can log in. This is the “nodename” that is assigned to the iProcess Engine when it is installed.

−

<Director>: Specifies whether or not the previous entries actually describe a TIBCO iProcess Objects Director, which is used to connect the client to a server). Select “true” if the specifications are for a Director, or “false” if a TIBCO iProcess Objects Director is not being used.

−

UserPreferencePersistence - This element contains two attributes that are used to specify whether user data¹ is persisted locally or on the server, as well as obtained locally or from the server upon login. Server-side persistence allows users to move to different machines and/or browser types, and pick up user preferences specified from another machine and/or browser type. The user preference persistence attributes are:

persistOnServer - This attribute specifies whether or not to persist on the server, as follows:

If “false”:

−

All user data is stored on the client.

−

User data is not cached and is persisted client-side immediately.

If “true”:

−

All user data is stored on the server.

−

User data is cached and is not saved to the server until the user logs out or closes the browser window.

−

Options values (i.e., all settings on the Options dialog in the application) are stored on both the client and the server. This is required because the language setting is stored in the Options data and this is needed to set up the locale before login.

The first time server-side data is accessed for a given user, the user is given the option of initializing the server-side data with any data that has previously been persisted client side (if any client-side data exists). The user’s response to this question is persisted on the server and will not be asked again.

Default = “false” if attribute is absent.

maxDataSize - Sets the maximum number of bytes for the user preference data. This value needs to be set at or below the field size supported by the database used on the server, which is typically 256K (128K for double-byte character encoding).

If this value is too small, processing the data at the server will be inefficient; if it’s too large, the database will throw an exception when it attempts to parse the message containing user preference data.

Note that the character encoding used should be taken into consideration when determining the maximum data size.

Default = 32768 (32K) if attribute is absent

Minimum value = 10

Additional records can be added if you would like more than three servers to appear in the Server field drop-down list.

1

User data consists of the following: Adding, removing, or changing views (note that changes to views are persisted immediately, whereas all other user data are persisted upon logout or application closure); list filters; list sorts; column changes (either using the Column Selector, or done manually); auto-repeat toggle on the work item list; case history show seconds/microseconds setting.