The Infor LN HTML5 Workbench Administration Guide, Release 10.7.x, provides comprehensive administration information for Infor LN Workbench Applications based on HTML5 technology. This guide is intended for Infor LN system administrators responsible for setup and maintenance tasks, serving as a reference rather than a tutorial for learning about Infor LN Workbench itself. It explicitly states that it is not applicable to Silverlight-based Workbenches, directing users to the Infor LN Workbench Installation Guide (U9732 US) for information on those.
Function Description:
A Workbench, as described, provides an advanced user interface to the Infor Enterprise Server. These Workbenches are designed for seamless integration with Infor LN UI and the Infor Ming.le™ environment. Depending on their specific design, Workbenches can be initiated either as standard Infor LN sessions or incorporated into an Infor Ming.le Role-Based Home Page. The core function of the Workbench is to facilitate user interaction with the Enterprise Server through a modern web application interface. This web application communicates with relevant Business Data Exchange (BDE) and Dynamic Link Library (DLL) components within the Enterprise Server. The system architecture involves several key subsystems: the Enterprise Server itself, an LN UI Server (General Purpose) which is a Java-based web server running the LN UI web application, a dedicated Workbench Web Server (also a Java-based web server) running the web application part for one or more Workbenches, and the end user's Web Browser.
Important Technical Specifications:
The Workbench operates within a distributed environment, requiring specific configurations across its various components.
- Server Communication: Workbenches utilize TCP connections to the Enterprise Server, specifically on ports 11600 - 12300. It is crucial that these ports are accessible from the Workbench Web Server and are not blocked by network firewalls.
- Web Server Requirements: The Workbench Web Server can employ Tomcat, JBoss, or WebLogic web servers. For WebSphere application servers, specific configuration details are provided.
- DNS Domain Recommendation: For optimal performance and to avoid issues with client browser privacy settings, it is recommended to deploy both the LN UI Server (General Purpose) and the Workbench Web Server within the same DNS domain. If this is not feasible, client browsers must not block third-party cookies, which are blocked by default in Internet Explorer.
- Deployment Mechanism: Workbenches are deployed as web applications from "additional files" (e.g., .wbwar files) that must reside on the Enterprise Server. This deployment is initiated by an administrator using the Workbench Applications session (ttadv2570m100) and requires the LN UI to be operational on the workbench web server.
- Security: The configuration involves setting up user accounts with specific management and deployment privileges on the web servers (Tomcat, JBoss, WebSphere) and within the Infor LN UI. For WebSphere, SSL certificates (Base-64 encoded X.509 .cer files) are required for secure communication and must be imported into the SSL Truststore.
- Log Files: Workbench web applications generate log files containing message and logic events on the UI server side. These logs capture events with varying severity levels (ERROR, INFO, DEBUG). The log file names include the session code, version, release, and customer of the corresponding 3GL session (e.g.,
tdpur8360m000_B60_a_sy82.txt). The location of these log files depends on the web server used: ${catalina.base}/logs for Tomcat, ${jboss.server.log.dir} for JBoss, and ${java.io.tmpdir} for other web servers. The configuration of log messages (severity, directory, filename) is managed via a log4j.xml file, which is created during the initial deployment of each Workbench and located at C:\Infor\ese\lnui\config\workbenches\<workbench-name>.
Usage Features:
The guide outlines several key administrative tasks for setting up and managing Workbenches:
- Configuration of Workbench Web Server: This involves preparing the LN UI instance on the workbench web server to support Workbench deployments. This includes configuring the web server (Tomcat, JBoss, or WebSphere) itself, setting up the LN UI web application, and defining deployment URLs and base URLs on the Enterprise Server.
- User Account Management: Creating and verifying user accounts with appropriate management and deployment privileges on the web server (e.g.,
manager-script role for Tomcat, management user for JBoss).
- LN UI Instance Configuration: Configuring the workbench web server's LN UI with the correct deployment username, password, web server URL, port number, and web server username/password to enable deployment of web applications. For WebSphere, this also includes specifying server name, cell name, and node name.
- Deployment URL Configuration: Setting up the network location and credentials on the Enterprise Server for workbench deployment using the Workbench Deployment URLs session (ttaad7140m000). This includes specifying a deployment URL (e.g.,
https://nlbavwhtml5wb.infor.com:8445/webui/servlet/deploy), username, and password.
- Workbench Web Server Base URL Configuration: Defining the network location of the workbench web server where Workbenches are launched, using the Workbench Parameters (HTML-based) session (ttaad7131m000). This involves specifying a Workbench Web Server ID (e.g., WBWAR) and the base URL.
- Workbench Installation: This process involves deploying a Workbench on the Workbench Web Server.
- Deploying an Additional File: This step is performed for initial deployment or when an additional file has been updated. It involves selecting the workbench web server, choosing the additional file (with a
.wbwar extension), and initiating the deployment action from the Workbench Applications session (ttadv2570m100).
- Creating/Updating an Additional File: This is necessary when developing a new workbench or updating an existing one. It involves downloading the workbench web archive (
.war extension), using the Import Workbench Application session (ttadv2570m200) to specify package, VRC, and session details, and then importing the file. An option to overwrite existing files is available for updates.
- Client Tracing: For diagnostic purposes, client tracing can be activated in two ways:
- By pressing
<Shift><L> (capital letter 'L') in the browser, which captures messages and events in a trace file and provides a download button.
- By selecting
Options > Activate trace mode in the LN UI, which automatically captures events when the Workbench starts.
Maintenance Features:
The guide emphasizes troubleshooting and diagnostic capabilities to ensure smooth operation and resolve issues.
- Troubleshooting Deployment: The guide provides specific solutions for common deployment errors, such as "Failed to ping the server," "Failed to login," "URL http://... not correct (Not Found)," "URL http://... not correct (Couldn't connect to server)," "URL http://... not correct (Couldn't resolve the host name)," "URL http://... not correct (Unauthorized)," and "URL http://... not correct (Service Unavailable)." These solutions typically involve checking URL fields, port numbers, usernames, passwords, server operational status, and log files.
- Troubleshooting SSL Trust: For WebSphere, issues like "SSL Trust not, or incorrectly defined" are addressed by ensuring that SSL certificates are correctly imported into the SSL Truststore and that the uploaded certificate belongs to the correct web server.
- Troubleshooting Additional File Import: If a workbench application has already been imported, the solution is to update the additional file rather than attempting to create it again.
- Workbench Log File Analysis: Administrators can examine the Workbench log files, which contain message and logic events, to diagnose issues. The log files are stored in specific directories depending on the web server. The
log4j.xml file allows for configuration of log message severity and file location, aiding in detailed debugging.
- Diagnostic Information: The LN UI Administration Webapp provides access to "Infor LN UI Administration > Diagnostics > System Properties" for further diagnostic insights.
Need help?
To Next Page
General