ShowTable of Contents
Known issues and limitations for this Lotus Expeditor 6.2.3 release listed on this page.
Lotus Expeditor Desktop Client
Title: The text of navigation bar in preference panel did not change to use large font
Problem abstract: Expeditor 6.2.3 on Windows does not dynamically inherit system font setting changes
Details: Not all aspects of the Expeditor 6.2.3 user interface will dynamically update their presentation based on changes to the system's font settings.
Resolving the Problem: This problem can be resolved by restarting Expeditor. All user interfaces will then reflect the new system font settings.
Title: Failed to install XPD client with Kazakh folder name
Problem abstract: Installing Expeditor 6.2.3 on Windows will fail if installation setup directory name is in Kazakh characters and installation is executed from setupwin32.exe.
Details: The installation will fail when installing from a Kazakh setup folder name on a Native Windows OS and running the setupwin32.exe. An example would be to create a setup folder name with Kazakh characters, copying the installation setup files to that location, then executing the setupwin32.exe from that location on a Kazakh Windows XP Operating System.
Resolving the Problem: This problem can be resolved by created an installation setup directory that has ASCII characters or by directly executing the Expeditor.msi instead of the setupwin32.exe file.
System JVM is needed to run applet in xulrunner based EB.
When using the embedded browser to view applet content with XULRunner, a standalone Java Virtual Machine is required.
Starting Expeditor 6.2.3, XULRunner Embedded Browser supports applet on Windows system. To run the applet, the Java Runtime Environment 6 update 15 (or higher) version is required. If the Java plugin is not installed, users may see a plugin alert, such as: "Click here to get the plugin." Users can either follow the link to install the JVM, or install manually. For manual steps, reference the section below.
Resolving the Problem:
Manual Installation Instructions
Go to the download page at java.com. ( http://java.com/en/download/index.jsp)
Click the Free Java Download button.
Click the Download Now button to start the online installation.
After the installation is complete, you must restart Expeditor
If you are on Linux Redhat and Ubuntu system, perform the following:
Open a console and change to /usr/lib/mozilla/plugins/ directory
Issue this command: ln -s /lib/i386/libnpjp2.so
If you are on Linux SLED 11 system, perform the following:
Open a console and change to /usr/lib/browser-plugins/ directory
Removing the old java plugin under it: rm -f javaplugin.so
Issue this command: ln -s /lib/i386/libnpjp2.so
To verify the right level of JVM is enabled for the embedded browser
Type about:plugins in the address bar of Integrate Browser
Find the information from Java Platform section
Title: [IE9/HTML5] Embedded browser with IE9 fail to show up the permission warming message.
Problem abstract: When using the embedded browser with Internet Explorer 9, HTML5 Geolocation feature does not work properly.
Details: When using Geolocation feature, Internet Explorer 9 standalone will prompt a security warning asking whether to accept the website "wants to track your physical location". But Embedded browser can not prompt such security warning, so that user cannot accept this security prompt and thus will not be able to use Geolocation. This is a Microsoft Internet Explorer 9's limitation which already has a documentation. http://blogs.msdn.com/b/jpsanders/archive/2011/05/09/you-cannot-use-geolocation-geo-location-in-an-ie-9-webbrowser-control.aspx
Resolving the Problem: Set the site as always allow via Internet Explorer 9 standalone.
Launch Internet Explorer 9 standalone, navigate to the website.
When prompt Geolocation security warning, select "Options for this site --> Always allow."
Then reopen the embedded browser, Geolocation feature will work properly.
Lotus Expeditor integrator
SPRs: TTHH8CV5UZ , MKAO8D89RL , MKAO8D79SP , BLIO8CUH24 , TTHH8D84CZ
Title: Native language support limitation in Expeditor integrator administration user interface (Dojo Framework limitation).
Problem abstract: The native language support by some Dojo 1.1 UI elements is limited.
Details: This is a limitation due to Dojo widget/parse not retaining required translation attribute 'tid' on content render time (e.g. The up-down list of More platform actions under Administer tab are not displayed correctly; under Configuration tab: Configure Dispatcher service - Inbound Routing not displayed correctly; under Monitor tab, NT for Monitor Adapters list; Some strings are not displayed on Start/Log-in page).
Resolving the Problem: If English language is used, the problem does not occur. Switch to English language setting in browser to avoid this display problem.
Title: Limitation in Expeditor integrator administration user interface (Microsoft Internet Explorer 7 limitation)
Expeditor integrator administration user interface has limited display capabilities when Microsoft Internet Explorer 7 is used.
When Internet Explorer 7 is used, some list views can not be displayed correctly (e.g. Integrator Bundle list under Administer tab, configure activity parameters under Configure tab, list with Application Control Flow details under Configure tab).
Resolving the Problem:
This problem can currently not be resolved. For users requiring special accessibility, Internet Explorer 8 and above are supported; there are limitations due to conflicts in Internet Explorer 7.
Title: Limitation in Expeditor integrator administration user interface (Microsoft Internet Explorer 8 and above limitation).
Expeditor integrator administration user interface has limited display capabilities when Microsoft Internet Explorer 8 and above are used.
When Internet Explorer 8 and above are used, limited text is displayed on the login page. After logging in, no content is displayed under any tab.
Resolving the Problem:
This problem can currently be resolved by using the Compatibility View of Internet Explorer 8 and above. In this Compatibility view the list with Application Control Flow details under Configure tab does not respond to the click event, so the Flow details can not be viewed on the Integrator UI. Details of the Internet Explorer Compatibility view can be found at this page: http://www.sevenforums.com/tutorials/1196-internet-explorer-compatibility-view-turn-off.html
SPRs: ZHHE8FJCYW , ZHHE8FJ4KF , KLIU8FJ4FA , FYBJ8FH9RB , FYBJ8FJ93E
Title: Configuration files for Expeditor integrator are limited to the English language.
Problem abstract: The Expeditor integrator displays the web UI in the Group1 languages, but all the input for configuration properties do NOT support other languages than English. This is a natural limitation as these properties are stored in configuration files of the product and these configuration files exist only in English.
Details: The Expeditor integrator displays the web UI in the Group1 languages, but all the input for configuration properties do NOT support other languages than English. This is a natural limitation as these properties are stored in configuration files of the product and these configuration files exist only in English.
This affects all properties that can be set using the Configuration Tool:
These are the application flows, which are stored in the /flowdefs folder.
These are the properties of the Expeditor integrator, which are all stored in the /config/XPDinteg.xml file.
They are belonging to the configuration files of the product beside all other Expeditor integrator configuration files in the /config folder and sub-folders and the configuration files inherited by the Lotus Expeditor product (e.g. files in /rcp/eclipse and its sub-folders). All these configuration files only support the English language.
Beside this, for certain properties like topic names only a certain character set.
These restrictions are driven by the underlying Eclipse and OSGi technology.
Resolving the Problem: This problem can currently not be resolved. Configuration parameters need to follow the naming guidelines and must be in English.
SPRs: BLIO8DAF8Z (), BLIO8F7E8F
Title: The language setting in browser is sometimes ignored by XPD integrator
Problem abstract: The Expeditor integrator UI is generally displayed using the language of the Web browser's locale, but some UI elements are configured through the underlaying Eclipse platform and, therefore, do use the locale setting of Eclipse. This can cause Expeditor integrator UI elements being displayed in different languages when the locale of Expeditor integrator's underlaying Eclipse does not match the browser's locale.
Details: The Expeditor integrator displays the Web UI in the Group1 languages according to the language setting of the browser with which the UI is accessed. The browser provides the locale to all Web UI related elements so that they can pick up the correct language. Due to the nature of the UI implementation, some UI elements are configurable through the Eclipse platform which has its own language setting retrieved from the OS or from given startup parameter.
The described problem is the case for values of the Monitor, Administer, Configure, Test tabs of the Expeditor integrator UI which are label value's configurable in Eclipse extension points. The extension points are processed while launching the runtime, and thus it takes the value from the system locale to determine which plugin_xx.properties file to get the value's of the labels from. If the locale is changed after launching the platform, it will not affect the properties file from which the extension point's label values are picked up.
Resolving the Problem: This problem can currently not be resolved. It is assumed that the case of different locales set for the platform and the browser will be very rarely the case since Expeditor integrator is installed in server environments where changing of locales is hardly the case.
SPRs : None
Title: Browsing local queues in Expeditor integrator containing a large number of messages with large payloads may lead to OutOfMemory error
Problem abstract: If a local queue in IBM Lotus Expeditor integrator/IBM micro broker contains a large number of messages with large payloads, e.g. around 4000 messages of size 10K each, and the JVM memory is set to 256m, an OutOfMemory issue may occur while trying to "browse" the messages using the Expeditor integrator UI > Monitor tab > Live view.
Details: If a local queue in IBM Lotus Expeditor integrator/IBM micro broker contains a large number of messages with large payloads, e.g. around 4000 messages of size 10K each, and the JVM memory is set to 256m, an OutOfMemory issue may occur while trying to "browse" the messages using the Expeditor integrator UI > Monitor tab > Live view. The same issue can occur if external tools like "HermesJMS" are used to browse the queues (http://www.hermesjms.com).
Resolution: None. This OutOfMemory issue can be avoided to some extent by increasing the JVM memory (Heapsize?). However, if the number of such large messages continues to increase, the OutOfMemory error may occur even after increasing the JVM memory and browsing the overloaded queues should be avoided in such cases.
SPRs : None
Title: Permission for Expeditor integrator clients to create dynamic queues.
Problem abstract: In certain production scenarios it is required that the Expeditor Integrator clients are not allowed to create queues dynamically. Clients should only be allowed to access the existing queues i.e. static queues.
Details: "Static queues" are those queues which are configured in the micro broker configuration section (Section_3) of the XPDinteg.xml. "Dynamic queues" can be created by any connected micro broker JMS or MQTT clients. I might be required that the clients are not allowed to create any dynamic queues.
Resolution: The following section of <messaging-service><core> in the Expeditor integrator configuration file XPDinteg.xml is used to allow / disallow the creation of dynamic queues by connected micro broker JMS or MQTT clients. If only static queues are allowed i.e. queues which are configured by Expeditor integrator, <dynamic-queue-creation> should be set to false. Changing this setting requires a platform reset.
<!-- INTERNAL Settings - Please, do only change if you know what you are doing! -->
Set to true to allow and false to disallow.
Note: Creation of Pub/Sub Topics by messaging clients can not be restricted. The clients can be granted pub/sub rights to specific topics using micro-acl.xml file.