Expeditor 6.2.2 Known Issues and Limitations

Added by Amanda J Bauman | Edited by IBM contributor

Zhe Wu on July 15, 2010 | Version 8

Abstract

No abstract provided.

Tags:

ShowTable of Contents

HideTable of Contents

1 Lotus Expeditor Desktop Client
- 1.1 Installing and Running Expeditor on non-English SUSE Linux Enterprise Desktop 10 systems
2 Embedded Browser

Known issues and limitations for this Lotus Expeditor 6.2.2 release listed on this page.

Lotus Expeditor Desktop Client

Installing and Running Expeditor on non-English SUSE Linux Enterprise Desktop 10 systems

SUSE Linux Enterprise Desktop 10 contains several system environment variables, one of which, LC_CTYPE, takes highest precedence by Java™ when determining the execution locale and character classifications. When setting SUSE Linux Enterprise Desktop 10 to run in non-English environments, such as Spanish, through the log-in panel, the contents of LC_CTYPE are not updated, but other locale related variables such as GDM_LANG and LANG are updated. To update the value of LC_CTYPE, the administrator should use the YaST2 Language Selection tool as follows:

1. After logging in as root, click Computer > Control Center.
2. In the left panel, under Groups, click System.
3. In the updated right panel, click Language.
4 .Choose the appropriate Primary language for the system.
5. Determine if you want to have the system use an English (US) keyboard layout and click Accept.

Note: If multiple languages are used on the same system, it might be more appropriate to not set the LC_CTYPE variable and to not use the YaST2 Language Selection tool, because LC_CTYPE inherits the value of LANG or LC_ALL. Also, if YaST is adapting the keyboard layout to English (US), you might need to unset LC_CTYPE in a command prompt and manually run the Expeditor installation script (setuplinux.sh) for the installation to occur in a non-English language.

Embedded Browser

SPR

#YGUO82H56Y
Title: Applet does not work in XULRunner based browser

Problem abstract: Applet does not work in XULRunner based browser on all platform by default

Details: Run applet in XULRunner based browser may cause an XPD crash on SLED system and Windows system. To
avoid the crash, the applet function is disabled by default in XULRunner based Browser.

Resolving the Problem: Applet still does not support on Windows and Mac platform. On Linux platform:
For RedHat system, user can resolve this problem by
1). adding a preference "com.ibm.rcp.dombrowser/enableApplet=true" into /opt/ibm/lotus/Expeditor/rcp/plugin_customization.ini file
2). installing a higher version java plugin into "/usr/lib/mozilla/plugins/" directory: For Sun JRE 1.5 or higher and IBM JRE1.6, change to /usr/lib/mozilla/plugins/ directory, issue this command: ln -s /plugin/i386/ns7/libjavaplugin_oji.so. And for IBM JRE 1.5, issue this command: ln -s /bin/libjavaplugin_oji.so

For SLED system, user can resolve this problem by
1). adding a preference "com.ibm.rcp.dombrowser/enableApplet=true" into /opt/ibm/lotus/Expeditor/rcp/plugin_customization.ini file
2). removing the old java plugin under "/usr/lib/browser-plugins/". For SLED10 SP3, the java plugin name is libjavaplugin_oji.so. And for SLED11, the name is javaplugin.so
3). installing a new higher version java plugin into same directory: For Sun JRE 1.5 or higher and IBM JRE1.6, change to /usr/lib/browser-plugins/ directory, issue this command: ln -s /plugin/i386/ns7/libjavaplugin_oji.so. And for IBM JRE 1.5, issue this command: ln -s /bin/libjavaplugin_oji.so

SPR

#CMSU8459T5
Title: Some plugin need to be installed manually for XULRunner based browser

Problem abstract: Some contents may not be rendered completely in XULRunner based browser due to plugins missing

Details: In XULRunner based browser, some page could not be rendered completely, if it require a plugin, while the plugin is not installed, e.g. plugin for flash, applet, pdf, etc.

Resolving the Problem: This problem can be resolved by installing the missing plugins manually. User can follow the following steps to install the plugins manually:
1). Search the plugin vendor website and download the plugin install packages
2). Install the plugins with its readme or guide
3). Administrator access is required during installation in some situations.
4). Restart the Expeditor client to active the plugin

For example: Install the Flash Player plugin
1). Download and install the Flash Player from: "http://get.adobe.com/flashplayer/"
2). Go through the install instructions, http://www.adobe.com/products/flashplayer/productinfo/instructions/

SPR

#SLDI85CAR5
Title: Sun Java plug-in crashes Expeditor on the first run when loading embedded browser on SLED10-SP3

Problem abstract: The default Sun Java plug-in on SLED10-SP3 crashes Expeditor on the first run when loading embedded browser.

Details: The default Sun Java plugin version is too low on SLED10SP3. Crash occurred when xulrunner registered the java plugin at starting time. The crash only occurs at the first time running embedded browser on SLED10-SP3.

Resolving the Problem: This problem can be resolved by restarting Expeditor after this first crash. Then Expeditor and browser will run properly.

SPR #

JYLU83KE6A
Title: Expeditor6.2.2 requires a Mozilla Firefox 3.5.x on SLED10-SP3

Problem abstract: When using SLED10 SP3, Expeditor6.2.2 requires a Mozilla Firefox 3.5.x browser installed on it

Details: Due to the low version of gtk2 library, the Expeditor's own xulrunner runtime can not be loaded on SLED10 SP3 system. Expeditor uses the Mozilla Firefox browser 3.5.x installed on it directly, which has installed by default. Users should not uninstall the Firefox browser that is installed, and should not remove the /usr/lib/firefox and /usr/lib/xulrunner1.9.1 directories. User can upgrade the Firefox browser to 3.5.x ,but should not upgrade it to 3.6.x, otherwise Expeditor will crash when opening a browser.

SPR #

PCAN86WUFM
Title: Can not open a new Embedded Browser window by using Applet on a Windows system with JRE 1.6.0.18 or later

Problem abstract: When Applet tries to open a new Embedded Browser window, there is no new Embedded Browser window opened.

Resolving the Problem: In JRE 1.6.0.18 and later, incompatible change inside next-generation Java Plug-in causes the problem. Users can disable it to solve the problem. Please follow below steps.
1). Click Start.
2). Click Control Panel.
3). Double click on Java Control Panel.
4). Click Advance tab in Java Control Panel.
5). Scroll to Java Plug-in entry.
6). Uncheck the check box for Enable next-generation Java Plug-in.
7). Click Ok and restart the system.

Install

Title: The unpack200.exe is broken in IBM JRE 6.0 SR6 and SR7

Problem abstract: XPD 6.2.2 plugins are compressed using pack200. When the product is installed, unpack200.exe is executed as part of the install and unpacking process. The install will fail if the unpack200.exe is broken.

Details: There is no issue installing the XPD 6.2.2 release using the included IBM JRE 6.0. This issue will only be seen if using an external JVM to install the XPD 6.2.2 product and if the external JVM is IBM JRE 6.0 SR6 or SR7.

Resolving the Problem: This problem can be resolved by using an IBM JRE 6.0 SR8 or later, or using an IBM JRE 6.0 SR4 or earlier

SPR #

BLIE868JL6
Title: In XPD 6.2.2 pack200 compression is not supported on inner jars

Problem abstract: XPD 6.2.2 supports the install of plugins which have been compressed using pack200. If a plugin includes an inner jar, and the inner jar is compressed using pack200, the install of the inner jar is not supported.

Details: The error that is reported is that the signature of the inner jar is not valid.

Resolving the Problem: This problem can be resolved by not using pack200 to compress inner jars.

Composite Applications

Title: Composite Applications: Title of category list not correctly displayed or displayed in Arabic only

Problem abstract: When connected to Portal 6.1.5, the category title in the Composite Application Catalog is displayed in Arabic only. In previous releases, it is displayed in English.

Details: The issue is with the Portal 6.1.5 serialization component.

Resolving the Problem: Please refer to the Portal 6.1.5 support web site for the iFix. http://www-01.ibm.com/support/docview.wss?uid=swg1PM07035.

Title: Unable to retrieve managed settings from a Portal server with TAM-SPNEGO authentication

Problem abstract: Unable to retrieve managed settings from a Portal server with TAM-SPNEGO authentication

Details: Due to a limitation with the WebSphere Portal policy service, environments using TAM-SPNEGO authentication will not be able to retrieve managed settings from a Portal server for use in the Lotus Notes/Expeditor client.

Resolving the Problem: Use an alternative supported authentication mechanism.

SPR

SAPL86RPX9
Title: Accessibility - Accessing Palette Entries when using JAWS. Unable to traverse to the categories and its components via tab key in the CAE palette.

Problem abstract: When traversing the Palette in CAE using a tab key, there is no visual or audible indication when reached to the palette's categories and its components.

Resolving the Problem: In order to select the right palette entry when using JAWS, you will first need to position your focus to the current palette. Then you need to hit [TAB] - this will put you in the palette. At this point you can use the arrow keys to traverse between the different palette categories and entries.

Native Launcher

SPR

SJOB84BE2P
Title: Work around for using QTP with Expeditor or Notes

Problem abstract: Expeditor does not start if HP Quick Test Professional 10.0 is installed.

Details: Install QTP. Select Java Addin during custom setup for QTP. Attempt to start Expeditor or Notes. The splash screen will appear but the client does not launch.

Resolving the Problem: There are 2 known methods that may allow Expeditor or Notes to launch. Only one of these should be required.

1) Go to Registry,
2) Determine the executable name by opening /framework/rcp/rcplauncher.properties on notes. Open /rcp/rcplauncher.properties on Expecitor. The eclipse.name= specifies the executable name. It is likely either notes2.exe or expeditor.exe.
2) Under "HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\JavaAgent\Modules", create a DWORD value. The name is the same as the executable name. The value is 0.
This will prevent QTP Java agent to be injected in the jvm.

1) Go to jvm.properties.
2) There are 2 possible locations for this property file. Just change both of them to be sure you get the one needed. Go to the and search for jvm.properties.
3) Using a text editor add the following line: env.unset.JAVA_TOOL_OPTIONS

Lotus Expeditor Server

defect:161626
Title: Unable to go back to parent pages in task history of a chain task

Problem abstract: The parent page link is corrupted if the task history is a chain task and the chain task includes a built-in chain task.

Details: When users navigate to a sub-task in a "run ISA" task (i.e. the nature is built-in chain task) which is included in a chain task in task history and then go back to parent page link, this link is corrupted.

Resolving the Problem: Users already can visit task history from top to bottom.

defect:161625
Title: A built-in chain task status is not updated when it is included in a chain task

Problem abstract: A built-in chain task status is not updated when it is included in a chain task and the chain task is succeeded.

Details: A built-in chain task (ex, run ISA) task status is not updated when it is included in a chain task and the chain task is succeeded. Each sub-task status of the built-in chain task (ex, run ISA) also shows success.

Resolving the Problem: Ignores this wrong status and check the parent chain task status or all of the sub-task status.

DB2 Everyplace Sync Server

Title: IBMDB2eServer can not be started in a cluster environment.

Problem abstract: IBMDB2eServer can not be started after performing server configuration, such as changing administrator password, database administrator password, create a cluster, or create a clone.

Details: The DB2 Everyplace Sync Server configurator will change configuration properties in database, but will not change the WebSphere Application Server configuration. However, IBMDB2eServer might encounter issue to start after configuration completed.

Resolving the Problem: Perform a full resynchronize for each node and restart the Deployment Manager and servers as the following steps.
1.login WebSphere Application Server administrator console.
2.Navigate to System Administration -> Nodes
3.check the Nodes hosting IBMDB2eServer
4.click Full Resynchronize
5.restart Deployment Manager and corresponding servers.

DB2 Everyplace Sync Server

Title: No shortcut to launch DB2 Everyplace Mobile Device Administration Center (MDAC) in windows platform.

Problem abstract: Expeditor Server configurator didn't create shortcut to launch DB2 Everyplace Mobile Device Administration Center (MDAC) in windows platform.

Details: The DB2 Everyplace Sync Server configurator remove the bundled legacy Install Shield to support new platforms in this release. This also cause some Install Shield features out. In windows platform, the configuration used to create a shortcut for launching DB2 Everyplace Mobile Device Administration Center (MDAC), and this will not be done in this release.

Resolving the Problem: Launch Mobile Device Administration Center by executing /Server/bin/dsyadmin.bat. This will be the same in Linux environment.