Local Listener Web Browser Service

1. Expand the Local Listener node in the tree pane and then click the Web Browser node.
2. On the VersaLex tab in the content pane, specify parameter values as appropriate.

   See Local Listener Cleo VersaLex Web Browser Service reference for information about the parameters available.

3. Click Apply.

1. Expand the Local Listener node in the tree pane and then click the Web Browser node.
2. On the VersaLex tab in the content pane, specify parameter values as appropriate.

   See Local Listener VLPortal Web Browser Service reference for information about the parameters available.

3. Click Apply.

1. Expand the Local Listener node in the tree pane and then click the Web Browser node.
2. On VLPortal tab, click Web Page Catalog....
   The VLPortal Web Page Catalog dialog box appears.
3. The Web Pages table displays the list of current web pages. The Page ID field specifies a unique identifier for the page. The Language(s) field specifies the ISO 639-1 code(s) for the supported languages configured for this page. See Internationalizing your web portals for more information. Only one row can be selected at a time. From each row's right-click menu, you can:
   • Edit... the web page.  See Editing or creating a web page.
   • Remove the web page. If the page you attempt to remove is referenced within a current web portal, you are asked to confirm the removal. Note that the File Transfer History, Manual File Transfer, VersaLex Web Portal, and Web Portal Help pages cannot be removed.
   • View the web portals that reference this page through the Where Used... option.  See Viewing a web page cross reference.
4. Use New Page... to create a new web page from scratch. See Editing or creating a web page.
5. Use the Import… button to import new or modified language resource files to support languages other than English (provided by default with the VersaLex product). After you import a new resource file, it will be displayed in the read-only Language Resource Files field. See Internationalizing your web portals for further information.

When you select Edit... or Clone… from a row in the Web Portals table, or when the New Portal... button is selected from the VLPortaltab, the web portal editor is invoked.

Before discussing web portal editing, it is important to understand the default web portal configuration: the web portal provided for you by the VersaLex application. See About Default Portal Configuration.

1. The Portal ID designates a unique identifier for this portal. This is used as a reference "key" in the Associated web portal menu of an HTTP user host (see Local HTTP Users Configuration). 
2. The Title field allows you to specify a meaningful string, used primarily for organizing the portals. This value will not be displayed anywhere within the user portal experience.
3. The Images section allows you to customize the layout and design of the web portal framework.
   • The Logo defaults to img/defaultlogo.jpg. This image will be displayed in the upper left-hand corner of each web portal page. It can be changed to any customized image, for example, your company logo.
   • The Banner defaults to img/banner.jpg. This image will be displayed along the top of each web portal page. It can be changed to any customized image, for example, your company banner. A banner size of approximately 2000w by 84h pixels is recommended.
   • The Menu defaults to img/navpic.jpg. This image will be displayed just under the main menu, along the left border of each web portal page. It can be changed to any customized image.
   • Use Import... to import new graphic images that can subsequently be selected through the Logo, Banner, and Menu fields. All imported files are stored in webserver\VLPortal\img\ under the VersaLex home directory.
4. Set up the Navigation Menu table to establish the pages that should be included in the portal and the order in which they should be organized. Each row in the table represents a single web page. Only one row can be selected at a time. From each row's right-click menu, you can:
   • Move Up to move the page up in the menu list.
   • Move Down to move the page down in the menu list.
   • Insert Above... or Insert Below... to insert a new page above/below the current row. When this is selected, the following dialog will be displayed, allowing you to select a web page from the current web page catalog.  See Maintaining the VLPortal web page catalog.
     Note: The web page should be configured for all supported Language(s), otherwise the web page will not be displayed for those language-specific users. See Internationalizing your web portals.
   • Edit... to edit the selected page. See Editing or creating a web page.
   • Remove to remove the selected web page from the navigation menu. This does not remove the page from the web page catalog; it simply removes the page from this portal's navigation menu.  Note that all web portals must have at least one web page in their menu; therefore, the last page may not be removed. See Maintaining the VLPortal web page catalog.
   • View the web portals that reference the selected page through the "Where Used..." option.  See Viewing a web page cross reference.
5. Optional - Click Metadata to configure a metadata entry form for files the portal user uploads via the applet. See Configuring manual file transfer metadata.

To see how the fields specified on web portal editor map to an actual web portal layout, see the Sample web portal layout.

When you select Edit from a row in the Web Pages table in the VLPortal Web Page Catalog dialog box or in the Insert Page dialog box, or when you click New Page in the VLPortal Web Page Catalog dialog box, the web page editor is invoked.

Before discussing web page editing, it is important to understand the default web portal configuration: the web portal that is provided for you by the VersaLex application.  See About Default Portal Configuration.

The Manual File Transfer and File Transfer History pages are referred to as web portal base pages. Only the page title and language can be changed for these two base web pages.

1. In the Web Page Catalog dialog box, right-click the web page you want to edit and select Edit from the drop down menu.
   A edit confirmation dialog box appears.
2. In the confirmation dialog box, click Yes.
   The Edit Page dialog box appears.

   Note: This dialog box is limited in scope for base pages. You can only modify values in the Language and Title fields.
3. Select a value from the Language drop down menu.
   The Language drop-down list contains the ISO-639-1 codes associated with language files located in thewebserver\VLPortal\internationalization directory.
4. Enter a title for the base page in the Title field.
   The value you to specify is displayed in the portal navigation menu. It should be of a reasonable length for display within a browser, and it should be entered in the language associated with Language drop down menu. If more than one Language has been specified for a web page, deleting the Title text removes the value for the selected language. However, for the base pages, you must specify at least one language. See Internationalizing your web portals for more information.
5. Optional - Click Where Used to display a cross reference of the web portals. See Viewing a web page cross reference.

1. In the Web Page Catalog dialog box, right-click the web page you want to edit and select Edit from the drop down menu.
   A edit confirmation dialog box appears.
2. In the confirmation dialog box, click Yes.
   The Edit Page dialog box appears.

   Note: This dialog box is limited in scope for base pages. You can only modify values in the Language and Title fields.
3. Select a value from the Language drop down menu.
   The Language drop-down list contains the ISO-639-1 codes associated with language files located in thewebserver\VLPortal\internationalization directory.
4. Enter a title for the base page in the Title field.
   The value you to specify is displayed in the portal navigation menu. It should be of a reasonable length for display within a browser, and it should be entered in the language associated with Language drop down menu. If more than one Language has been specified for a web page, deleting the Title text removes the value for the selected language. However, for the base pages, you must specify at least one language. See Internationalizing your web portals for more information.
5. Select a page type. Choose one of the following:
   • Select Custom to modify your custom-built web page. These are pages that you have created within the VersaLexproduct. For information about custom pages, see About custom pages.
   • Select Link to insert a link directly to any web page that has been built outside of the VersaLex product. For information about link pages, see About link pages.
6. Optional - Click Where Used to display a cross reference of the web portals. See Viewing a web page cross reference.

When Where Used... is selected from a row in the Web Portals table, the following dialog is displayed. This dialog identifies the HTTP user hosts that are using this particular web portal. The dialog is used for reference only; no manipulation can be performed from here. For information about how to change a web portal reference for an HTTP user host, see Local HTTP Users Configuration.

When Where Used... is selected from a row in the Web Pages table of the VLPortal Web Page Catalog, or Where Used... is selected from the Navigation Menu table of the web portal editor, or the Where Used... button is clicked in the web page editor, the following dialog is displayed. This dialog identifies the web portals that are including this particular web page.  The dialog is used for reference only; no manipulation can be performed from here.  For information about how to change a web page reference for a web portal, see Editing, cloning, or creating a web portal.

1. From the Web Portal editor (Editing, cloning, or creating a web portal), click Metadata.
   The Edit Portal Metadata dialog box appears.
2. Enter information for the metadata file you want to create in the following fields:

   Filename

   Specify the name of the XML file to contain the user-supplied metadata that will accompany the uploaded files.

   Language

   Displays whatever alternative Label values have been supplied for the metadata items for the given language. See Internationalizing your web portals.

3. Add or edit metadata items from the Form Data list.
   If there are no existing metadata items in the Form Data list, click New Item to display the New Metadata Item dialog box.
   If there are metadata items in the Form Data list, right-click an item and select Edit to display the Edit Metadata Item dialog box.
   Note: The New Metadata Item and the Edit Metadata Item dialog boxes contain the same fields.
   1. Enter information about the metadata item in the dialog box.

      Label

      This label is displayed for this item in the selected language in the form the user is prompted to complete when uploading files. You select a language for the label and enter the label text.

      Choices

      Indicate the choices available to the user when they provide information about this item. If you provide choices, they are delimited by the ‘|’ symbol. If the user can enter freeform text for the input, leave this field blank.

      Element Identifier

      The XML attribute for this item's corresponding element in the generated file.

      Required

      Indicate whether or not a selection/input is mandatory for this metadata item.

   2. Click OK.
      Your changes are saved and the Edit Portal Metadata dialog box appears.
4. Optional - Right-click an existing metadata item and select one of the following from the menu:
   • Move Up and Move Down to change the order in which corresponding fields appear in the form the user is prompted to complete when uploading the file(s).
   • Edit to edit the metadata item
   • Remove to remove the selected metadata item.
5. Click OK to save your changes and return to the VLPortal tab.

1. Create a resource file for each language that you want to support. Use the VLPortal.properties file as a template for the desired language.  For example, if you want to add web portal Spanish language support (that has the ISO-639-1 language code of ‘es’), you would copy the VLPortal.properties file (from the webserver\VLPortal\internationalization directory) toVLPortal_es.properties.
2. Open this newly created properties file in a text editor and translate all the text after the ‘=’ character into the desired language for each property provided in this file. In our example, we are translating to Spanish. Do not add a space after the ‘=’ character. 

   Example:

   The original English translation:

   

   The same properties translated to Spanish:

   

   Note: Any lines preceded by one or more ‘#’ characters is a comment and is ignored by the VersaLex application. These lines are not required to be translated. 
3. Import the translated resource file(s) into the VersaLex application using the Import… button in the Maintaining the VLPortal web page catalog dialog.  
   Note: Do not copy the resource file(s) directly into the webserver\VLPortal\internationalization directory. In order for the resource file(s) to be properly registered in the VersaLex application, they must be imported. This applies to newly created resource files or modified resource file. In all cases, the files must be imported rather than directly copied.
4. For each web page listed in the VLPortal Web Page Catalog, add an entry for the newly configured language. Right-click each web page entry and select Edit….
   1. If a prompt appears showing the associated web portals and asking if you are sure you want to edit it, select Yes.
   2. From the Language drop-down selector in the upper-right corner, choose the newly imported language. 
   3. Add the page title content in the appropriate language and click OK.
   Note: At a minimum, the above steps should be performed for the four baseline standard web pages (that is, VersaLex Web Portal, Manual File Transfer, File Transfer History, and Web Portal Help). If any of these pages are missing a particular language variant, an asterisk (*) is displayed next to the language in theWeb Portals table in the VLPortal tab.

   See Configuring VLPortal Web Browser service.

5. Additionally, web portal users selecting this language will not be able to view the missing language variants. Further, if all the pages are missing, users will not be able to log into the web portal. When missing pages are encountered, a warning message is logged to the VersaLex console each time the web portal user logs in.
6. If it is necessary to remove a page for a specific language variant and it is not the only language configured for that page:
   1. Edit the desired page.
   2. Select the language variant from the list.
   3. Clear the Title text and click OK. 
      You are prompted to be sure you want to proceed. 
   4. Click Yes to complete the process.

1. Create a new HTML document from VLPortal_Help.html.  For example, if creating a Spanish language document, createVLPortal_Help_es.html. 
2. Open the new file in an HTML editor.
3. Translate all the text appropriately.
   If you want to update the screen images as well, use a screen capture application to capture images and name the images appropriately, for example, VLPortalLayout_es.bmp.
4. Within your HTML file, update all the image references to point to your newly created image files.
5. When finished editing your new HTML file, go to the VLPortal Web Page Catalog. Right-click on the VersaLex Web Page Helpentry and select Edit….
   1. If a prompt appears, showing the associated web portals and asking if you are sure you wish to edit it, click Yes.
   2. From the Language menu in the upper-right corner, choose the desired language. 
   3. Add the Title content in the appropriate language.
   See Editing or creating a web page and Maintaining the VLPortal web page catalog.
6. Import you new HTML file.
   Click Import, select the new file as your linked file, and click OK.
   Note: Do not copy HTML files directly into the webserver\VLPortal\html directory. In order for the HTML file to be properly registered in the VersaLex application, it must be imported. This applies to a newly created HTML file or a modified HTML file.  In all cases, the HTML files must be imported rather than directly copied.

1. Before your trading partners can access the web portal, you must first establish a mailbox for each partner under the local HTTP users (see Local HTTP Users Configuration), and provide your partners with the proper URL (for example,http(s)://VesraLexComputerIP:http(s)Port/VLPortalResourcePath). Once these steps are followed, your trading partners can access the web portal by entering the specified URL into their browser. They will be prompted for a login.
2. The User name and Password are those that were established within the trading partner's mailbox under the local HTTP user. 
3. To change a password, click Options. 

   A password can be changed if:

   • the username's mailbox is not defined as an LDAP Usergroup and/or the username’s password has expired or
   • the username's mailbox is defined as an LDAP Usergroup, the LDAP Server Directory Type is "Active Directory," the LDAP Server Security Mode is not set to "None," and the user's password has not already expired.
4. The user can choose from the list of available languages from the Language drop-down list and view the web portal in their preferred language based on the resource files that have been configured and imported into the Cleo Harmony, Cleo VLTrader, or Cleo LexiCom application (see Internationalizing Your Portal).
5. If the option to select a custom link was configured in the VLPortal tab, a link will be included on the login page. (See Configuring VLPortal Web Browser service.) The text describing this link can be customized by editing the VLPortalUI.CustomLink property in the language-specific VLPortal.properties file(s) stored in webserver\VLPortal\internationalization under the Cleo Harmony, Cleo VLTrader, or Cleo LexiCom home directory. 
6. If reCAPTCHA authentication was enabled on the VLPortal tab, a dialog similar to the one shown below will also be displayed when the number of configured failed login attempts has been exceeded, or the number of failed login attempts was set to zero. See Configuring VLPortal Web Browser service.     
7. After successfully logging in, the trading partner will be presented with the web portal home page in his desired language. The web portal associated with the user login is specified on the Local HTTP User Host: Host HTTP tab. See Configuring access for HTTP host users. The navigation within this portal is determined by the setup you established under the VLPortal tab. To understand the default (as-shipped) web portal configuration, see Configuring VLPortal Web Browser service. 

Cleo Dashboards and Cleo System Monitor are applications that are enabled from the Dashboards/Monitor tab in the Cleo VLNavigator application.

1. Expand the Local Listener node in the tree pane and then click the Web Browser node.
2. On the Dashboards/Monitor tab in the content pane, specify parameter values as appropriate.

   See Local Listener Dashboard and System Monitor web browser service reference for information about the parameters available.

3. Click Apply.
   Note: You must restart the Cleo Harmony or Cleo VLTrader service/daemon before you use Cleo Dashboards or Cleo System Monitor.

Cleo Unify application is enabled from the Cleo VLNavigator Unify tab. See Cleo VLNavigator.

1. Click Local Listener > Web Browser in the tree pane and then click the Unify tab.
2. Select the Unify Resource Path check box to enable access. The resource paths are not enabled by default. 
3. Specify the path to the Cleo Unify resources.
   The default value is /Unify. Cleo Unify is a web UI-only, and users must include this resource path in the URL when the application through a web browser. For example, http://VersaLexComputerIP:http(s)Port/Unify)
4. (Optional) Clear the Access via VLProxy check box. It is selected by default, but you can clear it to disable access through Cleo VLProxy.
5. Click Apply.

If you are running the Cleo Harmony, Cleo VLTrader, or Cleo LexiCom application on a Unix platform, you might need to adjust graphics- and font-related properties if the application is reporting related problems. Running in Headless mode eliminates any possible dependencies on X11 or XVFB. When Headless mode is enabled (the default for new installs), the other graphics and font settings cannot be changed. The corresponding XML property name is <Headlessmode>.

1. Click the Graphcis/Fonts tab.
2. Clear the Headless mode check box to enable edit mode for the other graphics and fonts settings.
3. Select the Mixed settings check box to enable the properties below.

   Use platform graphics

   Property name: <UsePlatformGraphics>

   Description: Indicates to use native graphics environment rather than the application’s virtual graphics environment

   Default value: True if Solaris or HP-UX and JRE 1.5; False otherwise

   Use X11 DISPLAY environment variable

   Property name: <NeedX11DisplayVariable>

   Description: If access to X-Window is needed for native graphics environment

   Default value: True

   Property name: <X11DisplayVariableValue>

   Description: X11 server number and screen number.  If an X11 server is not available, it may be necessary to run Xvfb.

   Default value: 0.0

   Include application fonts

   Property name: <IncludeApplicationFonts>

   Description: Includes webserver/AjaxSwing/lib/fonts in font path.  Can only be False if <IncludeJreFonts> is True

   Default value: True

   Include JRE fonts

   Property name: <IncludeJreFonts>

   Description: Includes jre/lib/fonts in font path.  Can only be False if <IncludeApplicationFonts> is True

   Default value: True

   Reverse order in font path

   Property name: <ReverseOrderInFontPath>

   Description: Reverses order of above directories in font path

   Default value: False

   Use application font properties

   Property name: <UseApplicationFontProperties>

   Description: Indicates to use application’s font properties rather than JRE’s

   Default value: True, if Linux. False otherwise

   Use platform font

   Property name: <UsePlatformFont>

   Description: Indicates to use native font rather than JRE’s

   Default value: True, if AIX. False otherwise

   Xvfb (X virtual frame buffer) is an X11 server that performs all graphical operations in memory (http://en.wikipedia.org/wiki/Xvfb). Xvfb implementations are available on Linux, Solaris, AIX, and HP-UX. If needed, perhaps the easiest way to activate Xvfb is to start an Xvfb process just prior to starting the Cleo Harmony, Cleo VLTrader, or Cleo LexiComapplication in the Harmonyd, VLTraderd, or LexiComd daemon script. The X11 server number and screen number are runtime parameters to Xvfb; the <X11DisplayVariableValue>

   above would need to be set to the same server and screen numbers.

   Note: If a native UI does not exist, you can use command line options to change any of the above settings.  For example:

   Harmonyc -p Local Listener\Web Browser –t <Service><IncludeApplicationFonts>False

   VLTraderc -p Local Listener\Web Browser –t <Service><IncludeApplicationFonts>False

   LexiComc -p Local Listener\Web Browser –t <Service><IncludeApplicationFonts>False

   • When Mixed settings is selected, the graphics and text settings can be a mixture of the VersaLex software's virtual environment and JVM runtime and operating system native environment.
   • When Application only settings is selected, all of the graphics and font settings shift to only those provided by the Cleo Harmony, Cleo VLTrader, or Cleo LexiCom software's virtual environment.
   • When Platform only settings is selected, all of the graphics and font settings shift to only those provided by the JVM runtime and operating system native environment. 

   For both Mixed settings and Platform only settings, if the Use X11 DISPLAY environment variable check box is selected, you should ensure the server and screen number are properly set.

1. Click the Advanced tab.
2. Specify values for the following properties as needed.

   Page Size

   Use this option to specify the number of nodes on a page.

   Changes to these settings in a web UI session are immediately applied to the session so that the optimal values can be determined - other active web UI sessions must explicitly refresh the tree (right-click in whitespace around tree).  To match previous versions of the VersaLex application when these settings were not configurable, set them as follows:

   Top Level

   Host Subfolders

   The number of nodes displayed per page for top level and host subfolders trees.

   Note: These settings apply to Cleo Harmony and Cleo VLTrader applications only

   Within Hosts

   The number of nodes displayed per page for the active and template hosts tree in the main window.

   Certificates

   The number of nodes displayed per page for the certificates tree in Administration > Certificates in the web UI or in Tools > Certificate Manager in the native UI.

   Session Timeouts - Harmony/VLNavigator

   These properties applies to the VersaLex and Cleo VLNavigator applications only.

   Initial startup

   The time allotted for launching a new web browser session. Default value: 120 seconds.

   Waiting for response

   The maximum time allowed waiting for server response to a browser request. Default value: 120 seconds.

   Abnormal exit detection

   The time allowed without a web UI ping before the session is shutdown by the server seconds. Default value: 60 seconds.

   Session Timeouts - VLPortal

   This property applies only to VLPortal.

   Inactivity Timeout

   The maximum time allowed while logged into the web portal without any user activity before the session is expired (default 600 seconds).  

   Note: If you have configured your portal users to use the applet, this value should be set large enough to cover the entire duration that a user may have an applet window active.

   Response Headers

   Additional response headers (primarily for required security headers) for the web UIs as a whole. Enter a new header on each line.

   Possible headers include:

   • X-XSS-Protection: 1; mode=block
   • X-Content-Type-Options: nosniff
   • Cache-Control: no-store
   • Content-Security-Policy: "script-src 'self'"

   If you specify X-Frame-Options, for those web UIs where IFrames are used (for example, Cleo Harmony and Cleo VLTrader), a value of DENY is automatically changed to SAMEORIGIN.

   If you specify Content-Security-Policy, for those web UIs where inline scripts are used(for example, Cleo Harmony and Cleo VLTrader), a script-src directive is added if not already present, and includes 'unsafe-inline'. If the directive already exists, 'unsafe-inline' is automatically inserted into directive.

   Debug Settings

   Append service debug to system debug file

   Select the check box to log debug information into the VersaLex system debug file.

   Create individual client debug files

   Select the check box to create a new HTML client debug file (stored in logs\ under the VersaLex home directory) for every JVM instance.

3. Click Apply.