ShowTable of Contents
This section lists the currently configured limitations of the Expeditor integrator.
The message size is currently limited to 10 MByte
. This can be configured in the XPDinteg.xml
file, but should only be done with care. Many large messages can dramatically slow down the processing speed.
If the Lotus Expeditor micro broker bridge does not pick up messages carrying large files from the MQ back-end messaging server, the IBM MQ Server settings at the back-end are to be evaluated. The follwing properties should be adjusted in order to be able to transfer large files:
- Increase the Max. Message Length of the
- Queue Manager under menu Properties | Extended | Maximum Message Length
- ReqOutQx at the back-end under menu Properties | Extended | Maximum Message Length
- MQ Channel under menu Properties | Extended | Maximum Message Length
- Increase the Number of Log Files used by the MQ Queue Manager under menu Properties | Log | Log primary files / Log secondary files
The Message Load (in most cases the carried file) is also limited to 10 MByte
at the moment. Please, consider using the Expeditor integrator’s message splitting option to transfer larger files (see chapter Transfer of large files in multiple messages
Graphical User Interface
The Lotus Expeditor integrator Web Application based GUI is accessed with Web Browser. The recommended browser is Mozilla Firefox v2 and v3 (from http://www.mozilla.com
It is recommended for Microsoft® Internet Explorer (from http://www.microsoft.com
) to change the browser settings to:
Tools | Internet Options | Temporary files | Settings | Check for newer version available | select Every visit to the page
Script execution must be allowed and cookies should be enabled in the browser for correct presentation of the GUI.
Expeditor integrator is based on Eclipse RCP. For some functions which are use by the Expeditor integrator GUI, language settings are retrieved from the Eclipse environment settings. Browser language settings are ignored in this case. If the used browser for accessing Expeditor integrator is set to language A
but Expeditor integrator runtime (Eclipse RCP) uses language B
the basic GUI layout will show up in language A
and some called Expeditor functions will be displayed in language B
It is therefore recommended that Administrators use the local browser on the Expeditor integrator instance or make sure that their browser is set to the same language as the accessed integrator instance.
Operating system service support under Windows 2008
Installation and operation of Expeditor integrator as Windows 2008 system service is only working under the Administrator account and in non-console mode (no interaction with desktop, no OSGi console is displayed).
First Aid Guide
This is a little summary of steps that should be considered before contacting support.
Where to look first in case of Problems
Logging information is provided on component level as well as through the Custom Log Service and the Expeditor integrator Tivoli Monitor Service (iTMS). Basically, all application bundles write their log information to the standard OSGi Log Service. This logging information is kept in the Eclipse workspace
folder (see folder structure in chapter Expeditor integrator file and directory structure
). Furthermore, IBM Lotus Expeditor components do write log messages to independent log files. Please, refer to the following table for an overview of the available log files.
Table 51: Log information of the Expeditor integrator
Component and Description
|Log information (log file path / name)|
(e.g. size restricted by property)
OSGi Log Service
(standard Eclipse and OSGi logging)
|Information is logged in Eclipse log under <XPDINTEG_HOME>/workspace/logs|
Directory for log information from standard Eclipse and OSGi Core (OSGi Log Service)
The following properties can be edited in <XPDINTEG_HOME>/rcp/eclipse/plugins/com.ibm.rcp.base_<version><build>/config/pbuilder/rcpinstall.properties
Expeditor integrator default:
The above (default) setting generates a maximum of 6 log and trace files with a maximum size of 4MB for each file (circular logging/tracing). Changes of size and number of log and trace files can be adjusted with these parameters.
Expeditor integrator startup problems
e.g. due to config file parsing errors
Log file of max. 4kB size (wraps around when limit is reached)
|Custom Log Service||Log queue name is configured in XPDinteg.xml with parameters
MqEventQName and MqLogQJndi
|If bridged to messaging back-end, this may also be written to back-end XPDINTEG.LogQ or TEC console events.|
Logging is configured in the XPDinteg.xml file
MicrobrokerQueueDepth=40000, LogThreshold=1 (Error), MonitoringBundles, MonitoringStatus, MonitoringLogTopicList
(if the integrator Tivoli Mon Svc is used)
|consult the TEC and look for XPDINTEG_LOGEVENT and XPDINTEG_BUNDLEEVENT events||(parameters of Log Service apply)|
|TEC cache file
(stores events on disk when they cannot be sent to the event server)
|<XPDINTEG_HOME>/persistent/tec/tivoli.send.cache||Maximum size is 64KB for the Expeditor integrator v1.0.
If this is a requirement for future releases, a parameter could be provided that can be set in the XPDinteg.xml file.
|TEC log and trace files||<XPDINTEG_HOME>/persistent/tec/eif.log and
|TEC libraries do not provide options to limit the trace and log file size.
The Expeditor integrator v1.0 passes the log file names as parameters on to the used TEC libraries. Currently, there is no way to limit the size of these two files (even from XPDinteg).
It is recommended to turn the logging and tracing only on in defined environments by setting TecLogLevel=ALL and TecTraceLevel=ALL (in XPDinteg.xml) and OFF again under production conditions.
|Microbroker and –bridge
(log contain information about the broker, connection to the back-end and message handling)
|Log file under <XPDINTEG_HOME>\persistent\microbroker\XPDinteg_broker
Diagnostic information under
|-Location set with <persistence-directory>
-Size set with MicrobrokerLogSize in XPDinteg.xml
Transaction Service logs
(logs information about the status of transactions, errors and warnings)
|Log files under <XPDINTEG_HOME>/persistent/txlogdir\partnerlog
Set in in XPDinteg.xml
-TransactionLogDirectory=location of log files
-TransactionLogSize=file size limit in KB
Using the provided Maintenance tool for collecting log and trace data
is provided as a part of the com.ibm.rcp.integrator.tools-feature
. This can be used during maintenance for
- backing up and deleting log files
- ...deleting log files
- ...turning on/off MQJMS trace
The following files must exist as prerequisite
- XPDintegTools.jar by extracting the Expeditor integrator tools
- <XPDINTEG_HOME>/workspace folder (This folder only exists after Expeditor integrator was started at least ones after platform reset.).
Steps for using XPDintegMaint.bat
options should be used when Expeditor integrator is not running.)
1. Backup and delete the following log files:
These files are deleted together with *.lck
and trace files, e.g. <XPDINTEG_HOME>/trace.xml, <XPDINTEG_HOME>/trace.xml.1 and <XPDINTEG_HOME>/ffdc.xml. These trace files are not required for the maintenance logging.
2. Execute the following command from <XPDINTEG_HOME> to create and backup log files:
XPDintegMaint.bat -backupAndDeleteLogs <LOG_BACKUP_DIR>
3. Delete log files without creating back up. Run:
..to delete the following files:
Note: This option should be used with care because deleting any logs may cause losing valuable information for the support teams.
Turning MQJMS Trace On/Off in production environment
If messaging connection problems continue to exist, detailed logging and tracing can be used for further investigation (see Table_51)
The recommended method in production environments for turning MQJMS Tracing on or off without resetting the Expeditor integrator runtime is to manually update the <XPDINTEG_HOME>/workspace/.config/rcpinstall.properties
Follow these steps:
1. Turning on MQJMS trace:
- Stop Expeditor integrator
- Add the following two lines to the <XPDINTEG_HOME>/workspace/.config/rcpinstall.properties file:
- for e.g., add these lines for setting “C:/temp” as the <TRACE_DIR>:
- Start Expeditor integrator
- Start the micro broker trace tool:
- If this is the first time you have enabled tracing, you may need to unzip the XPDintegTools.zip file contained within the tools directory (<XPDINTEG_HOME>/tools).
- Additionally, configure the MBTrace.properties file prior to launching the batch file. Execute the MBtrace.bat (or MBTrace.sh on Linux). Details are provided in chapter Using the micro broker trace utility (MBtrace).
2. Turning off MQJMS trace:
- Stop Expeditor integrator
- Remove the following two lines above from <XPDINTEG_HOME>/workspace/.config/rcpinstall.properties file
- Re-start Expeditor integrator
3. After problem occurrence, execute the following commands in the OSGi console:
The dump threads command should be executed two more times. Ideally, execute the command thirty seconds after the previous command.
Clean up folders, messages and restart the Expeditor integrator
The following steps are required to manually reset the Expeditor integrator to its initial state:
- Delete content of @nowiki@34directory
- Delete content of <XPDINTEG_HOME>/persistent directory
- use a working version of the config\XPDinteg.xml file
- Run resetscript/XPDintegReset.bat (which includes the first two steps if the default directories are used)
- Start Expeditor integrator by either starting the service/daemon or manually running the XPDintegStart.bat/sh.
Please, refer to the installation and set-up description in the Installing and Configuring the IBM Lotus Expeditor integrator platform (see section Installing Expeditor integrator
Obtain an ISA Collection using the OSGi Console
The IBM Service Assistance (ISA) is provided as plug-in and can be used directly in the OSGi console of Lotus Expeditor integrator (see section Expeditor Integrator console commands
). Follow these steps to collect maintenance data for the IBM Support:
1. If not yet started, start IBM Lotus Expeditor integrator. If Expeditor integrator was started by the operating system service in non-Console mode, stop Expeditor integrator, switch to console mode and start it again (see chapter Starting, Stopping, Resetting Expeditor integrator
2. Run the following commands in the OSGi console:
If IBM Lotus Expeditor integrator un-installation procedure does NOT remove all files, it is highly recommended that Expeditor integrator administrators/users manually remove the files left on the file system after the un-installation has been completed.