IBM ITCAM Agent for SAP Applications, 7.1.1.1-TIV-ITM_SAP-IF0001 - United States  DOWNLOADABLE FILES

ABSTRACT
 This IFix resolves the APARs and defects listed in the "Problems Fixed" section below

DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2014.

All rights reserved.

Component: IBM(R) Tivoli(R) Composite Application Manager Agent for SAP
Applications, Version 7.1.1 Fix Pack 0001

Component ID: 5724B97SO

Fix: Interim Fix 0001, 7.1.1.1-TIV-ITM_SAP-IF0001

Date: 31 December 2014

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices

1.0 General description
========================

This interim fix resolves the APARs and defects listed in the
"Problems Fixed" section below.

2.0 Problems fixed in 7.1.1.1-TIV-ITM_SAP-IF0001
=====================================================
The following problems are addressed by this interim fix.

2.1 APARs
----------

APAR: IV63525
Abstract: CUSTOMER IS GETTING 0 ENTRIES FOR THE OUTPUT OF THE
FUNCTION MODULE /IBMMON/ITM_QOUT_GET_QUEUES.
Additional Information: The /IBMMON/ITM_QOUT_GET_QUEUES function
module stopped collecting the data even though the data was
present in the SAP system. Due to this, SYSID ‘+++’ was
displayed on the Tivoli Enterprise Portal. The function module
has been rectified for collecting the data from the SAP
systems having versions greater than 46C and SP level
SPKB46C39.

APAR: IV60733
Abstract: MPS CX_SY_CONVERSION_NO_NUMBER IN FUNCTION MODULE
IBMMON/ITM_FILE_SYSTEM
Additional Information: ABAP dump ‘Conversion Error –unable to
handle‘---‘ as a number ’ for the / IBMMON/ITM_FILE_SYSTEM
function module is gracefully handled towards File Systems
attribute group.

2.2 Defects
------------

Defect: 58382
Abstract: Exception condition "GWY_COMMUNICATION_FAILURE" raised.
Additional Information: "GWY_COMMUNICATION_FAILURE" has been
gracefully handled for the /IBMMON/ITM_GWY_CONNECTIONS
function module towards the Gateway Connections attribute
group.

Defect: 55733
Abstract: TEP Remote configuration of SAP Agent is not working on
non-windows after remote upgrade.
Additional Information: While getting the Config parameters from the
".cfg" file, the two parameters for gateway are removed from
the parameters that are being sent to the Tivoli Enterprise
Portal Configuration Panel. Also the ".cfg" file is updated
by removing those parameters. Then, reconfiguration of Agent
Instance with appserver and logon mode through Tivoli
Enterprise Portal is successful after remote upgradation to
711FP1 IF1.

Defect: 55366
Abstract: ABAP Dumps when Job Name is not present in SAP standard
table.
Additional Information: Exception handling was missing for the
scenario of the Job Name not being present in the SAP standard
table. The issue has been fixed by adding the required
exception handling for Workspace Integration engine background
jobs when Job is not present in SAP.

2.3 Enhancements
----------------

Enhancement: 67334
Abstract: Additional functionality to handle the MAI missing Alerts
in the Function Module /IBMMON/ITM_MAIALRT_INX.
Additional Information: Function module /IBMMON/ITM_MAIALRT_INX is
modified to fetch the MAI Alerts which are missed by ITM SAP
Agent as these MAI Alerts are inserted into table
/IBMMON/ITM_ALIX with some delay by SAP.
Note:
1) SAP system time and ITCAM SAP Agent machine time should be
in sync upto accuracy of seconds.
2) In order to have full collection of MAI Alerts, there is
an additional overlap time being added to the sampling time
frequency given by the ITCAM SAP Agent.
This additional overlap time is configurable parameter on
the SAP side
Please note -
a)By default the additional overlap time will be 1 min i.e.
60 seconds.
b)Maximum additional overlap time which can be configured
will be 5 mins i.e. 300 seconds.
c)If the user wants the additional overlap time greater than
1 min i.e. 60 seconds and less than or equal to 5mins i.e.
300 mins, then he should follow the below steps.

Please find below the steps to configure this additional
overlap time on SAP side:
• Go to transaction code SE16.
• Enter the table name as '/IBMMON/ITM_CNFG' and press 'F7'.
• Execute the database table '/IBMMON/ITM_CNFG' or press 'F8'.
• Add the additional overlap time parameter as ‘MAI_PERD_OV’
in the database field 'ITM Configuration Parameters' and
then add the additional overlap time in seconds in the
database field 'VALUE_INT' and save it.

2.4 Superseded fixes
---------------------
7.1.1-TIV-ITM_SAP-FP0001
7.1.1-TIV-ITM_SAP-IF0001

-------------------------

2.5 APARS, Defects and Enhancements included from superseded fixes
------------------------------------------------------------------
This section contains list of defects fixed / enhancements made in
previous releases. To get more details on these changes please refer
the README for that particular release.

--------------------------------
7.1.1-TIV-ITM_SAP-FP0001
--------------------------------

APAR: IV60177
Abstract: TEPS DISPLAYS ALERT TIMESTAMP AS UTC
Additional Information: MAI Alerts stored in the database table
'/IBMMON/ITM_ALIX' are in the UTC format.So while fetching
such MAI Alerts, conversion from UTC time zone to current
system time zone is required.

APAR: IV60254
Abstract: 'TRANSACTION PERFORMANCE' AND 'R/3 TRANSACTION PERFORMANCE'
MODULES ARE NOT SENDING DATA FOR HDC
Additional Information: Code has been changed in Transaction
performance logic which creates 'KSATRANS' file to display
historical data on TEP for Transaction performance.

APAR: IV60989
Abstract: EMPTY WORKSPACE FOR BUSINESS PROCESS MONITORING AND
SYSTEMMONITORING IN TEP
Additional Information: Code changes have been done to handle
exceptions for the SAP standard DSWP_BPM_SOLUTION_ID_CONVERT
function module and for the /IBMMON/ITM_MAIBP_MONITORING
MAI BPM function module.

APAR: IV61450
Abstract: REMOVE PERIOD START/END ATTRIBUTES OF XML MESSAGE LOGS
Additional Information: The attributes 'Period Start' and 'Period
End' are used by the agent internally and aren't helpful
to customer in anyway. In order to hide them from attribute
view, the 'USAGE' and 'COST' tags have been set to appropriate
values. Also, the queries that define the attribute view have
been modified to remove the 'Period Start' and 'Period End'
attributes.

APAR: IV59319
Abstract: SAP AGENT NOT PICKING UP ALERTS FROM SOLUTION MANAGER
Additional Information: This is DOC APAR and the third Party OS
command adapter should be configured and mail notification
should be enabled using appropriate steps.

Defect: 53372
Abstract: Unable to start SAP Agent when candlehome contains ‘SAP’
word.
Additional Information: Post install script ignores variables
containing 'SAP' keyword and they are not included in 'ksaenv'
file. When CANDLEHOME and JAVAHOME contained 'SAP' keyword,
they were ignored as well resulting in failure to start
ksaagent.

Defect: 49745
Abstract: Agent doesn't read syslog.idx file correctly
Additional Information: SAP agent read '<SID>_syslog.idx' incorrectly
leading to corrupt '.idx' file. This resulted in system log not
getting detected sometimes.
Note: This issue is reproducible only with multi instance SAP
system.

Defect: 47233
Abstract: Test connection utility is not working on windows as
designed for application server mode.
Additional Information: With the new NWRFC library, 'Gateway Host'
and 'Gateway service' are not required while creating a RFC
connection with the SAP server. So, these fields have been
removed from the agent configuration panel.

Defect: 45898
Abstract: R/3 action link of ‘Close Alert’ and ‘Close Alerts of the
same type’ are missing in ‘Alert Information’ view of CCMS
monitoring workspaces.
Additional Information: The workspace has been modified to create the
two missing links. Also, the code on the SAP side has been
fixed to correct the close alert mechanism.

Enhancement: 44620
Abstract: Netweaver RFC support added for SAP Agent common
layers.
Additional Information: Netweaver RFC v7.20 support has been added.
Communication with SAP system will now happen using the NWRFC
library instead of the Classic RFC library.

Enhancement: 44663
Abstract: Logging of SAP 'Component Version Id' and 'Interim Fix Id'
in the agent log file.
Additional Information: SAP 'Component Version Id' and 'Interim Fix
Id' are returned as additional parameters by the
'/IBMMON/ITM_FUNC_PARMS' function module and can be viewed in
the agent logs with minimum trace level enabled.

Enhancement: 45911
Abstract: Facilitate remote connection of type 'Internal Connection',
'Connections via ABAP driver' and 'TCP/IP' Connections defined
in SAP server.
Additional Information: This link has been provided from the 'Test
Connection' link in the 'Connection Monitoring' workspace to
check the status of a remote connection on demand.

Enhancement: 45973
Abstract: Facilitate single Unicode ITM file containing both BADI and
non-BADI objects.
Additional Information: Single ITM file has been provided to import
the SAP Agent transport on all supported SAP versions having
BADI or non-BADi implementation.

--------------------------------
7.1.1-TIV-ITM_SAP-IF0001
--------------------------------

APAR: IV53685
Abstract: TRANSPORT IMPORT FAILS FOR ITM_CONN_CHECK FUNCTION MODULE.
Additional Information: 711 GA transport fails with ABAP dump for the
/IBMMON/ITM_CONN_CHECK function module. Because of this, the
data is not collected and displayed on the Tivoli Enterprise
Portal for some attribute groups, and the dumps are generated
on SAP side.

APAR: IV52434
Abstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING
ADDSYSTEM.
Additional Information: Because of the missing slash in ATTRLIB
field name, the agent is configured incorrectly that hampers
the agent functionality and Historical Data Collection (HDC).
This problem occurs when the SAP agent instance is created by
using the tacmd Addsystem command, and the same instance is
reconfigured.

APAR: IV51184
Abstract: FUNCTION MODULE "/IBMMON/ITM_SYS_LOG" GENERATING ABAP
DUMP.
Additional Information: The "IBMMON/ITM_SYS_LOG" function module is
invoked every 10 minutes and it generates ABAP dumps.
"/IBMMON/ITM_SYS_LOG" function module was called with
"ITM_R3_LOG_RECORD" parameter. This parameter is not defined.
The Syslog information is available from INS and GRP subnodes,
however, problem occurs only while collecting the data for
:GRP subnode.

APAR: IV47613
Abstract: ABAP DUMPS DUE TO OVERFLOW IN /IBMMON/ITM_CCMS_ALERTS
(ALERT UNIQUE ID).
Additional Information: Added a new attribute named
'Extended Alert Unique Identifier' to hold bigger alert unique
identifier. The extended alert unique identifier attribute is
used to close an alert in the SAP system.

Defect: 43177
Abstract: Data is not coming for ‘ITM_USER_INFORMATION’ for ':Sys'
node.
Additional Information: The code considered only the 'INS' node.
Therefore, the user information link in the 'SYS' node did not
receive any data.

Defect: 43075
Abstract: 'No Applicable data' seen for CCMS Monitoring on ALL Grp
node along with 9911 alert in second call of agent in case of
CEN configured SAP.
Additional Information: When retrieving alerts for the first call of
the new CCMS design for GRP node in case of Central (CEN)
system, 'No Applicable Data' is displayed on the Tivoli
Enterprise Portal. The second call of the agent was
generating a 9911 alert.

Defect: 42393
Abstract: Argument column in "Lock Information" is showing invalid
data.
Additional Information: Lock argument of locked object shows string
'[][][][][][][]' on the Tivoli Enterprise Portal, when all
possible fields are responsible for locking that object.

Defect: 42317
Abstract : Delete transport unable to delete reference of agent BADI
class from MAI configured SAP system.
Additional Information: BADI delete transport must be able to
delete all relevant BADI classes and implementations from the
system where BADI is imported.

Defect: 40637
Abstract: Exception condition "ITM-NOT_FOUND" raised in case syslog
records are not found at SAP side.
Additional Information: If particular syslog details are not present
on the SAP system, then while accessing syslog details using
sys_detail link on the Tivoli Enterprise Portal, a "Exception
condition 'ITM-NOT FOUND' raised" short dump is generated on
the SAP side and a blank screen is displayed on the Tivoli
Enterprise Portal.

Defect: 39686
Abstract: Syslog causing ABAP dump for Group Sub Node.
Additional Information: For the logs and traces attribute group of
the GRP node, exceptions are raised.

Defect: 39681
Abstract: Data is missing for many columns of ITM_JOBS.
Additional Information: Data is not displayed for many columns of
ITM_Jobs.

Defect: 39007
Abstract: "No applicable Data" row should be seen on TEP for system
log under system name.
Additional Information: If there is no data for the "System Log"
workspace, then, "No applicable data" must be displayed in the
System Name column.

Defect: 38998
Abstract: Unable to interpret X as a number in function module
/IBMMON/ITM_HOSTS.
Additional Information: If the SAP system contains more than 9
application servers (RFC servers), the "Unable to interpret *
as a number" message is displayed in the /IBMMON/ITM_HOSTS
function module.

Defect: 38995
Abstract: Tivoli SAP agent causing dump in SAP on UNIX server.
Additional Information: If an exception occurred while reading job
log, the /IBMMON/ITM_JOB_LOG function module is terminated.

Defect: 38903
Abstract: IDOC Number not included in the Display item.
Additional Information: The "IDOC Number" is not available to use
as a display item in situations.

Defect: 38251
Abstract : Data is getting fetched for invalid sub-nodes.
Additional Information: Data must be returned only for the sub node
that is called; data must not be returned for other irrelevant
sub nodes. Call from the agent gives ITM_MGROUP or Origin node
as input to most of the function modules that contain the node
details.

Enhancement: 38724
Abstract: "Client" column is required for ITM_IDOC workspace to
differentiate the respective client's data.
Additional Information: Added a "Client" column in the
"IDOC Information" view of the "Data Transfer Information"
workspace. The “Client” column shows the client name for the
respective data of client.

3.0 Architecture and prerequisites
===================================
This Fix Pack is supported on all operating systems listed in the IBM
Tivoli Composite Application Manager Agent for SAP Applications
Installation and Configuration guide, Version 7.1.1 Fix Pack 1:
Link:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/sap/sap_landing_install.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/sap/sap_landing_install.html]

The following website contains the latest certification information:
Software Product Compatibility Reports (SPCR)
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]

You can also find system requirements for ITCAM for Applications V7.2.1
Fix Pack 1 at:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/prerequisites/apps7211_systemreqs.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/prerequisites/apps7211_systemreqs.html]

ITCAM for Applications 7.2.1.1 Knowledge Center:
http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/welcome_apps7211.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/welcome_apps7211.html]

3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:
- IBM(R) Tivoli(R) Composite Application Manager Agent for SAP
Applications, Version 7.1.1 Fix Pack 0001

7.1.1 Fix Pack 0001 ISO Part Number:
Physical Part Number: ITCAM Agent for SAP Applications CBHU9ML
Electronic Part Number: ITCAM Agent for SAP Applications CN0MJML

Customer need to download separately 7.1.1 Fix Pack 0001 GA ISO
image from Passport Advantage.

- IBM Tivoli Monitoring, Version 6.2.3 FP3

Because this fix is cumulative, it can be installed on any fix level
for this version, release, and modification level later than the
prerequisite.

4.0 Image directory contents
=============================
This fix image contains the following files:
- 7.1.1.1-TIV-ITM_SAP-IF0001.README - This README file
- 7.1.1.1-TIV-ITM_SAP-IF0001.tar - Fix archive .tar format
- 7.1.1.1-TIV-ITM_SAP-IF0001.zip - Fix archive .zip format

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX environment; use the .zip file if
you are working in a Windows environment.

5.0 Installation instructions
=============================

This fix can only be installed over an existing installation of
711 FP0001. Use the following steps to install this fix.

5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Upgrade
Prerequisites for this fix' must be installed when for upgrade.

- For the purpose of this README, the <CANDLEHOME> symbol is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

- Before installing this interim fix on UNIX systems, set the CANDLEHOME
environment variable to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this interim fix, be sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary
directory on the system that contains the agent to be updated.
For the purpose of this README, the <TEMP> symbol represents the
fully qualified path to this directory. Note: On Windows systems,
this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all supported
operating systems.

3. Use the "itmpatch" command to install the fix for the operating
system for that agent. For more information on the "itmpatch"
command, see section [6.2].

On UNIX systems, if the fix was expanded to
<TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:

> <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001/itmpatch -h <CANDLEHOME>
-i <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001/ksa_xxxxxx_tema_if0001.tar

where:
- xxxxxx corresponds to the value in the first column
returned by the ./cinfo -i command.

In the following example, the file is
"ksa_li6263_tema_if0001.tar".
> ./cinfo -i
[Monitoring Agent for Your Product]
[lx8266 Version: 07.11.01.01]

On Windows systems, if the fix was expanded to
<TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:

For Windows 32-bit
> <TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001\ksa_winnt_tema_if0001.cab

For Windows 64-bit
> <TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001\ksa_wix64_tema_if0001.cab

Note: if the itmpatch command gets this error:
"The application has failed to start because its side-by-side
configuration is incorrect. Please see the application event
log for more detail." it's necessary install the "visualstudio
redistribution package" before to run the itmpatch command.

For a 32bit architecture,
the name of this package is vcredist_x86.exe, available at
http://www.microsoft.com/en-us/download/details.aspx?id=5582 [http://www.microsoft.com/en-us/download/details.aspx?id=5582]

For a 64bit architecture,
the name of this package is vcredist_x64.exe,available at
http://www.microsoft.com/en-us/download/details.aspx?id=2092 [http://www.microsoft.com/en-us/download/details.aspx?id=2092]

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary
directory on the IBM Tivoli Enterprise Monitoring Server system.
For the purpose of this README, the <TEMP> symbol represents the
fully qualified path to this directory. Note: On Windows systems,
this path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
operating systems.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Command Reference.

On UNIX systems,
if the fix was expanded to <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001:
> $CANDLEHOME/bin/tacmd addBundles -n -i
<TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001

On Windows systems,
if the fix was expanded to <TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i
<TEMP>\7.1.1.1-TIV-ITM_SAP-IF0001

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. See Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. After "tacmd addBundles.." from step 3 above, control files
on the Tivoli Enterprise Monitoring Server and the
Tivoli Enterprise Portal Server must be updated.
These updates must be done manually.

a. Tivoli Enterprise Monitoring Server update
The sa_dd_07110101.xml and sa_dd.properties files must be
copied from the <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001
directory to the 071001000 version of the Tivoli Enterprise
Monitoring Services depot.

Two scripts are provided to make these copies and are
in the fix <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001 directory
after the expansion of the tar or zip file:

ksa_patchdepot.bat - Windows
ksa_patchdepot.sh - UNIX

From the <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001 directory,
run the appropriate script based on the operating system. The
script output contains details about the copies being made.

b. Tivoli Enterprise Portal Server update
Resource files must be copied from the
<TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001 directory to the
Tivoli Enterprise Monitoring Portal directory.

Two scripts are provided to make these copies and are
in the fix <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001 directory
after the expansion of the tar or zip file:

ksa_patch_resource_teps.bat - Windows
ksa_patch_resource_teps.sh - UNIX

From the <TEMP>/7.1.1.1-TIV-ITM_SAP-IF0001 directory,
run the appropriate script based on the operating system. The
script output contains details about the copies being made.

5. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM
Tivoli Monitoring Command Reference.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t sa
-n <Managed system name>
-v 07110101

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t sa
-n <Managed system name>
-v 07110101

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (sa), not three characters (ksa).
- The node (-n) for the "tacmd updateAgent" command is the
managed system name of the operating system (OS) agent to be
updated. The target node for the "tacmd updateAgent" command
is always an OS agent.

5.4 Agent support update
------------------------------
Use the following steps to update the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal
Desktop.
Note: If SDA feature is enable at the HUB TEMS, then below steps are
are not required. SDA will install only browser support and if
customer is using TEP Desktop then install the support manfully
as shown below.

This fix (7.1.1.1-TIV-ITM_SAP-IF0001) includes changes to the
agent support files that must be installed. If you installed these
updates, there are no additional installation steps. If you did not
install these updates, use the following steps to update the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, or
Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file
7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to the Tivoli
Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers,
or Tivoli Enterprise Portal Desktops.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Expand the archive file (ksa_tems_teps_tepd_if0001.tar or .zip)
that contains the updates for the Tivoli Enterprise Monitoring
Server, Tivoli Enterprise Portal Server, and Tivoli Enterprise
Portal Desktop using the "tar" command on UNIX systems or an
extract utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.

On UNIX systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.

Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.

1. Aquire a platform-specific pre-packaged JRE version
of the Application Support Installer (ASI). See IBM
Tivoli Monitoring Application Support Installer,
6.2-tiv-itm_asi-if0002 at
http://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]
for download and installation instructions.

2. Specify the '-j javahome' parameter with the path to
a 32-bit java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.

5. The next panel presented by the Application Support Installer
asks for the selection of Tivoli Monitoring components to which
you want to add application support. For this fix, check or
clear the check boxes as follows:

[checked | unchecked] - Tivoli Enterprise Monitoring Server (TEMS)
[checked | unchecked] - Tivoli Enterprise Portal Server (TEPS)
[checked | unchecked] - Tivoli Enterprise Desktop Client (TEPD)

Continue through the remaining GUI panels selecting SAP Agent
07.11.01.01 support to complete the installation.

6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it must
be restarted.

7. If the Tivoli Enterprise Monitoring Server being updated is remote
(not a Hub Tivoli Enterprise Monitoring Server) then restart the
Tivoli Enterprise Monitoring Server.

5.5 Installing SAP agent transport
------------------------------------
Note: From this fix onwards,a single ITM file has been provided for
importing SAP transport on all supported SAP versions having BADI or
non-BADI implementation.

This procedure installs the SAP transport into the SAP system. You
are not required to uninstall the previous transport before
installing this transport.

1. Go to the ABAP directory in the location where you expanded the
fix archive file.

2. Copy the transport files into the SAP environment as follows:

a. The following two sets of transport files are in the
ABAP directory of the SAP agent fix archive:

1) K711_00103U.ITM and R711_00103U.ITM in /ABAP directory.
These files are Unicode versions of the transport.

2) K711_00103_DELETE.ITM and R711_00103_DELETE.ITM
These transport files remove the ABAP code. Do not import
the DELETE transport unless you stop using the product
entirely and want to remove the transports from your SAP
systems.

b. Copy your transport files to the SAP Transport System data
directory as follows:

1) Copy the K711_00103U.ITM file to the cofiles directory.
2) Copy the R711_00103U.ITM file to the data directory.

3. Run the following command for non-BADI and BADI where:
SID Target SAP : system ID
PROFILE_NAME : Name of the tp profile file
nnn : Number for the target client where the agent is to run

tp addtobuffer ITMK711_00103U SID
pf=\usr\sap\trans\bin\PROFILE_NAME
tp import ITMK711_00103U SID client=nnn U16
pf=\usr\sap\trans\bin\PROFILE_NAME

Alternately, you can use the SAP STMS transaction to import the
transport requests. Ensure that the Import Transport Request Again
and the Overwrite Objects in Unconfirmed Repairs options are
checked on the Import Options tab of the Import Transport Request
window.

6.0 Additional installation information
========================================

6.1 Installation instructions for agent baroc file
------------------------------------------------------
This fix (7.1.1.1-TIV-ITM_SAP-IF0001) includes changes to the
agent baroc files that must be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If you have not installed the files, see the "IBM Tivoli
Monitoring, Version 6.2.2FP2: Installation and Setup Guide"
(ITM6.2.2FP2 Installation and Setup Guide.pdf) under
"Installing monitoring agent baroc files on the event server" in the
"Installing the IBM Tivoli Enterprise Console Event Synchronization"
section for more information.

6.2 Additional information on using the itmpatch command
---------------------------------------------------------
The itmpatch command has the following syntax.

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:

-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch

For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification,
where the fix is located. On Windows systems, this path must
include the drive letter.

6.3 Verifying the update
------------------------
1. To verify that the agent was updated correctly, use the tacmd
command to view the current version of the agent after the agent
is restarted. You are required to log in to a Tivoli Enterprise
Monitoring Server before viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory. The default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t sa

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t sa

Note:
- The component (-t) for the tacmd listSystems command is
specified as two characters (sa), not three characters (ksa).

When the agent update is successful, the agent version is
07.11.01.01

Note:
- The component (-t) for the tacmd listSystems command is
specified as two characters (sa), not three characters (ksa).

When the agent update is successful, the agent version is
07.11.01.01

After the agent is restarted, you can also use the GUI to verify
that the agent was successfully updated.

For the agent on Windows systems, the version number is
07.11.01.01
For the agent on UNIX systems, the version number is
07.11.01.01

2. To verify that the agent support files were updated correctly,
use the kincinfo command on Windows systems or the cinfo command
on Linux(R) or UNIX systems. The sample output below shows the
versions of the Tivoli Enterprise Portal Server, Tivoli Enterprise
Monitoring Server, or Tivoli Enterprise Portal Desktop systems
after this fix has been successfully applied.

Note:
- The date of the build displayed might not be accurate. This is
a known problem.

On Linux systems:
--------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%/bin/cinfo -i

Note: cinfo output may differ depending on ITM version.

*********** Fri Dec 5 10:14:10 IST 2014 ******************
User: root Groups: root bin daemon sys adm disk wheel pkcs11
Host name : IBMSAP1V9 Installer Lvl:06.23.03.00
CandleHome: /opt/ibm
***********************************************************
...Product inventory

ax IBM Tivoli Monitoring Shared Libraries
li6263 Version: 06.23.03.00

gs IBM GSKit Security Interface
li6243 Version: 07.40.43.00

jr Tivoli Enterprise-supplied JRE
li6263 Version: 06.12.00.00

sa IBM Tivoli Composite Application Manager Agent for SAP
Applications
li6263 Version: 07.11.01.01

ue Tivoli Enterprise Services User Interface Extensions
li6263 Version: 06.23.03.00

ui Tivoli Enterprise Services User Interface
li6263 Version: 06.23.03.00

7.0 Known problems and workarounds
===================================

Abstract: While configuring the agent instance on UNIX, more than 3
letters are accepted as instance ID.
Problem: Three letters are accepted as Instance ID while configuring
agent instance on UNIX. This can result in failure to connect
to the SAP system as the ".cfg" file for that instance will
be generated with a wrong name.
Workaround:
The user should make sure that only three lettered name is
entered as the instance ID while configuring an agent instance.

8.0 Additional product information
==================================

ABAP Transport Compatibility:
------------------------------
Each fix includes an updated agent executable
program (ksaagent or ksaagent.exe) and an updated ABAP transport.
Install both programs to obtain the highest level of support.

In some situations, you cannot install
a new transport immediately because of change control processes on the
mySAP systems. In these situations, sometimes you can run a new agent
executable with a prior version of the ABAP transport. This section
explains when it is possible to run a newer agent executable program
with an older version of an ABAP transport.

Note: The mySAP agent does not run correctly if not installed with
a compatible level of the transport.

Fix Level Delivered Transport Minimum Transport Level
----------- ------------------- -----------------------
FP0001-IF0001 ITMK711_00103U ITMK710_00103U
FP0001 ITMK711_00100U ITMK711_00100U
IF0001 ITMK711_00099U ITMK711_00098U
711 GA ITMK711_00098U ITMK711_00098U

9.0 Copyright and trademark information:
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.

10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.

INSTALLATION INSTRUCTIONS
Please refer to the 7.1.1.1-TIV-ITM_SAP-IF0001.README contained in the description section above for general installation instruction

DOWNLOAD PACKAGE
Please refer to the 7.1.1.1-TIV-ITM_SAP-IF0001.README contained in the description section above for general installation instructions

PROBLEMS SOLVED
IV63525; IV60733

Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] Fix Central Download Link 31 Dec 2014 English 89354240 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=7.1.1.1-TIV-ITM_SAP-IF0001&source=SAR] [ ]
PRODUCT ALIAS/SYNONYM
 7.1.1.1-TIV-ITM_SAP-IF0001

 [/support/docview.wss?uid=swg24039150&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039150&aid=2]Problems (APARS) fixed
IV63525, IV60733

Question:
SAP Agent suddenly crashed

Hello, my SAP Agent 7.1.1.1 crashed suddenly. I was able to restart it and since then it is working smoothly, but I would like to understand the root cause to avoid any reoccurrence.

Any idea ?

Answer:
Defect: 58382
Abstract: Exception condition "GWY_COMMUNICATION_FAILURE" raised.
Additional Information: "GWY_COMMUNICATION_FAILURE" has been
gracefully handled for the /IBMMON/ITM_GWY_CONNECTIONS
function module towards the Gateway Connections attribute
group.


IBM Datacap Rulerunner server stops after several aborted batches - United States Rulerunner hang stop abort TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 After several batches abort consecutively in Rulerunner, all threads shut down.

CAUSE
Rulerunner has a thread control feature that acts as a safety to prevent all pending batches from aborting. When it detects a certain number of consecutively aborted batches on a single thread, Rulerunner shuts down all threads. By default, the threshold is three batches, so shutdown occurs if four batches abort consecutively.

DIAGNOSING THE PROBLEM
With Rulerunner logging turned on, aborting batches will show in the rulerunnerX.log files (where X is the thread number. If there is a question as to whether a Rulerunner shutdown is being caused by this feature, check the rulerunnerX logs for each thread to see if there are four consecutive aborts followed by a shutdown.

RESOLVING THE PROBLEM
If there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.

x86 (32-bit) OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\Rulerunner\Misc (REG_DWORD) Restart
Individual processors [default: 1]

HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\Rulerunner\Misc (REG_DWORD) Restart
processor Attempts [default: 3]

x64 (64-bit) OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\Rulerunner\Misc
(REG_DWORD) Restart Individual processors [default: 1)

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\Rulerunner\Misc
(REG_DWORD) Restart processor Attempts [default: 3]

 * Restart Individual processors - 1 is on, 0 is off.
 * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort.

Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable Windows 8.1.0.3

Question:
Controlling stop and starting of Rulerunner Service

Hi

Datacap version 9.0.1

 Is there a way of issuing a controlled shutdown request so the thread has time to finish processing whichever tasks it is executing so that no batches are aborted due to the communication link error?

Answer:
If there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.

x86 (32-bit) OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\Rulerunner\Misc (REG_DWORD) Restart
Individual processors [default: 1]

HKEY_LOCAL_MACHINE\SOFTWARE\Datacap\Rulerunner\Misc (REG_DWORD) Restart
processor Attempts [default: 3]

x64 (64-bit) OS:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\Rulerunner\Misc
(REG_DWORD) Restart Individual processors [default: 1)

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Datacap\Rulerunner\Misc
(REG_DWORD) Restart processor Attempts [default: 3]

 * Restart Individual processors - 1 is on, 0 is off.
 * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort.


IBM Known limitation: You cannot add people to a matter request if there are more than 1000 people selected in the clipboard. - United States  PRODUCT DOCUMENTATION

ABSTRACT
 If you try to add people to a matter request when there are more than 1000 people in the clipboard, the following error will occur:
An unexpected error occurred.
Contact your system administrator.
ICWPA1001E

CONTENT
To work around the limitation, when you add people from the clipboard, add fewer than 1000 people at one time.

Question:
How to resolve "An unexpected error occurred. Contact your system administrator. ICWPA1001E"

When trying to add people to a matter request when there are more than 1000 people in the clipboard, the following error is reported:

An unexpected error occurred. Contact your system administrator. ICWPA1001E"

Answer: To work around the limitation, when you add people from the clipboard, add fewer than 1000 people at one time.


IBM Changes in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS - United States  TECHNOTE (FAQ)

QUESTION
 You have configured a WebSphere Application Server WebSphere MQ messaging provider connection factory without an Authentication Alias and do not programmatically supply user identifier information when creating a connection to a queue manager. You notice a change in the default behaviour between WebSphere Application Server versions regarding the user identifier flowed on the MQCONN to the target WebSphere MQ Queue Manager:

- When using WebSphere Application Server v7.0 and v8.0, no user identifier value (blank) is passed to the queue manager.

- When using WebSphere Application Server V8.5, a non-blank user identifier value is passed to the queue manager.

In the latter case, you receive the following exception when creating a connection to a queue manager:

JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')

Is this change in behaviour expected?

ANSWER
WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.
From the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ. This is true even if no user identifier has been specified, or a blank or null user identifier has been specified; for example by calling:

MQConnectionFactory.createConnection();

or:

MQConnectionFactory.createConnection(“”, “”);

or:

MQConnectionFactory.createConnection(null, null);

In the case where a null or blank user identifier has been specified, the WebSphere MQ V7.1 and later classes for JMS will query the value of the Java System Property user.name. The value of this property is flowed to the queue manager for authorization.

As a result, if the user identifier specified by the Java System Property user.name is not authorized to access the queue manager, the queue manager will return an exception to the WebSphere MQ classes for JMS with Reason Code MQRC_NOT_AUTHORIZED and the connection to the queue manager will not be established.

This change in behaviour could affect topologies that previously relied on the default behaviour in the WebSphere MQ V7.0.1 classes for JMS that flowed a blank user identifier when establishing a CLIENT mode transport connection. The expectation that a blank or null user identifier will be flowed by default, and that the user identifier that started the WebSphere MQ server-connection channel would be used by the queue manager when performing the authorization checks, is no longer valid from the WebSphere MQ V7.1 classes for JMS.

In the case outlined above, system administrators that are currently relying on the default behaviour of the WebSphere MQ V7.0.1 classes for JMS should review their configurations regarding the use of user identifiers and authorization. This might also help to improve security within their WebSphere MQ topology.

In summary, the change in behaviour will affect users of:

- The WebSphere MQ V7.1 and later classes for JMS.

- The WebSphere MQ V7.1 and later JCA Resource Adapter that includes the classes for JMS.

- Versions of WebSphere Application Server that include the WebSphere MQ V7.1 and later JCA Resource Adapter. Currently this is WebSphere Application Server V8.5.0.0 and later.

The com.ibm.mq.jms.ForceUserID Java System Property

A Java System Property called “com.ibm.mq.jms.ForceUserID” was introduced as part of APAR IZ49302 [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302] and included from WebSphere MQ V6.0.2.8 and WebSphere MQ V7.0.1.

The changes made as part of this APAR could be used to change the default behaviour in the WebSphere MQ V7.0.1 classes for JMS regarding the user identifier value flowed to the queue manager when creating a connection.

This property is no longer valid from WebSphere MQ V7.1. Setting this property will have no affect on the WebSphere MQ V7.1 classes for JMS and later.

Other Useful Resources

WebSphere MQ Documentation

The WebSphere MQ Documentation contains a section on planning user authorization which also includes a description on access control for clients. A link to this section in the WebSphere MQ V7.1 Documentation is as follows:

WebSphere MQ > Security > Planning for your security requirements >> Planning authorization [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/zs14070_.htm]

Technotes

A Technote is available that explains J2C Authentication Aliases and how they can be used to configure the user identifier flowed to a queue manager when creating a connection:

Enterprise applications, the WebSphere Application Server WebSphere MQ messaging provider connection factories and Authentication Aliases explained [http://www.ibm.com/support/docview.wss?uid=swg21580097]

Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server

Question: Why are we seeing MQRC_NOT_AUTHORIZED errors after upgrading Websphere from V7.0 to V8.5.5? https://www-01.ibm.com/support/docview.wss?uid=swg21662193

Answer:
WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.
From the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ.


IBM Specifying the profile path in the BPMConfig properties file for IBM Business Process Manager (BPM) - United States BPMConfig; profile; path; directory TECHNOTE (FAQ)

QUESTION
 How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command?

ANSWER
Note: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.

You can use the following property names:

 * For a Deployment Manager profile: bpm.dmgr.profilePath
 * For a Custom profile: bpm.de.node.#.profilePath

For example:
bpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile
bpm.de.node.1.profilePath=c:\\Program Files\\WebSphere\\profiles\\MyCustomProfile1

For Microsoft Windows, you can use double backslashes or forward slashes. For example:

bpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1

Note: If you are creating the profile makes sure a profilePath value does not exist. The parent directory of the profile path should exist and the user should have write privileges to create a new directory.

For example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory. Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory.

RELATED INFORMATION
 BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html]

Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5
PRODUCT ALIAS/SYNONYM
 BPM

Question:
Error when using profilePath parameter with BPMConfig to create a profile When creating a profile using the BPMConfig command and the -profilePath parameter to define a custom directory to store the profile data, the creation fails with the following error message if the directory already exists (even if it is empty):
com.ibm.bpm.config.BPMConfig.main(): The profile path <profile_path> must not exist.....

Answer: Note: If you are creating the profile makes sure a profilePath value does not exist.


IBM JMSListener AutoReconnect properties misconception - United States netcool; impact; netcool/impact; nci; jms; dsa; connectivity; reconnect; auto; autoreconnect; property; properties; listener; jmslistener; misconception; disinformation; misunderstanding; misinterpretation; error; fault; inaccuracy TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 There appears to be a common misconception regarding the application of the JMS DSA Listener properties for AutoReconnect

SYMPTOM
AutoReconnect fails

CAUSE
Properties for the JMSListener in the file:

$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props

have been set as:

impact.[JMSListenerName].jms.autoreconnect=true
impact.[JMSListenerName].jms.autoreconnect.pollinterval=[TimeValue]

RESOLVING THE PROBLEM
Properties for the JMSListener in the file:

$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props

Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:

impact.[JMSListenerName].autoreconnect=true
impact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]

Where [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit.

Question:
Netcool/Impact (all versions): JMSListener does not reconnect when JMS server is restarted

JMSListener does not reconnect when JMS server is restarted.
Created JMS datamodel to connect to JMS queue. Restart the JBOSS service on JBOSS server on which JMS queue exists Impact attempt to connect to JMS queue fails and it says connection could not be made. However, restart Impact process and click on test connection it gives connection OK message.

Have configured reconnect properties:

     impact.MyJMSListener.jms.autoreconnect=true
     impact.MyJMSListener.jms.autoreconnect.pollinterval=20000

Answer:
Properties for the JMSListener in the file:

$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props

Where [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:

impact.[JMSListenerName].autoreconnect=true
impact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]

Where [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit.


IBM No data in some workspaces for MySQL agent - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups.

SYMPTOM
Data does not get collected for the following views that show system and status variable related information:

View name Workspace name Navigator group name Statistics Statistics Availability Operations per second MySQL status data Availability Session status Agent Configuration Configuration Global status Global variables Server String properties Numeric properties Following exception is seen in the JDBC trace logs:

- JdbcConnection.executeFromList-new - java.sql.SQLException: The 'INFORMATION_SCHEMA.GLOBAL_STATUS' feature is disabled; see the documentation for 'show_compatibility_56'

The above error is seen for MySQL versions 5.7.9 and higher. For MySQL versions prior to 5.7.9, selecting from the INFORMATION_SCHEMA tables produces an empty result set with a deprecation warning.

Note: MySQL agent is packaged with ITCAM for Applications (IBM Tivoli Monitoring) and Application Performance Monitoring 8.1.x solutions.

CAUSE
Few tables in the INFORMATION_SCHEMA that are used by the agent to collect monitoring data are deprecated in the MySQL server versions 5.7.6 and above. Due to this deprecation these tables cannot be queried normally and cause an error when the agent tries to query these tables to get data.

More details about the MySQL INFORMATION_SCHEMA migration to performance_schema here:

https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html [https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html]

ENVIRONMENT
MySQL agent installed on MySQL Server versions 5.7.6 and above.

RESOLVING THE PROBLEM
Users wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA.

This variable can be set from the MySQL command prompt as:

set global show_compatibility_56=ON;

The default value of the variable 'show_compatibility_56' for MySQL server versions <=5.7.7 is ‘ON’ and for versions >=5.7.8 is ‘OFF’.

User can check the value of this variable by running the following command from the MySQL command prompt:

show global variables like "show_compatibility_56";

This variable can also be set in the MySQL server configuration file also called as Option file.

User needs to add the following line to the ‘my.cnf’ file (located at ‘<MySQL_Installation_Dir>/my.cnf’ for Windows and ‘/etc/my.cnf’ for UNIX/Linux):

show_compatibility_56=ON

The paths mentioned above are the default paths for the Option file. For more details on where your installation of MySQL server looks for the 'my.cnf' file, refer the URL:

https://dev.mysql.com/doc/refman/5.7/en/option-files.html [https://dev.mysql.com/doc/refman/5.7/en/option-files.html]

Note: Change in 'my.cnf' file will require a MySQL server re-start for the changes to take effect.

More details on the system variable 'show_compatibility_56' here:

https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56 [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56]

PRODUCT ALIAS/SYNONYM
 Monitoring agent for MySQL Sever

Question: No data in some workspaces for MySQL agent Why Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups?

Answer: Users wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA.


IBM ITCAM for SOA KD4SDMS database size grows - United States CAMSOAALL CAMSOADB CAMSOAPERF REQMETRICS RESPMETRICS kd4TrimDB2db TECHNOTE (FAQ)

QUESTION
 As the KD4SDMS grows unbounded, is there a way to regularly prune it?

ANSWER
Regarding the older release ITCAM for SOA 7.1.1, there is no a mechanism to automatically regularly prune the KD4SDMS database. The following Wiki page has been published on the topic:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables]

To keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above.

As for the newer ITCAM for SOA 7.2, there is a cleanup task that runs on the TEPS host where SDMS database is installed. It deletes REQMETRICS and RESPMETRICS table rows where SRTTIME (start of period) is more than 24 hours ago. So these two tables, which are responsible for most of KD4SDMS storage occupation, should not grow unbounded anymore.

NOTE: ITCAM for SOA 7.1.1 is Out-Of-Support since 2015 April 30.

Question: How to control SDMS database size? ITCAM for SOA 7.1.1 was installed about 3 years ago. I already know that SDMS database size may increase with no limit. Has anyone found a way to keep under control this behavior?

Answer: To keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above.


IBM Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed.  (CVE-2017-1341 ) - United States  SECURITY BULLETIN

SUMMARY
 MQOPEN call might succeed when it should have failed, when using generic profile authority matching for remotely defined MQ object.

VULNERABILITY DETAILS
CVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]
DESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.
CVSS Base Score: 3.7
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)

AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8

Maintenance levels 8.0.0.0 - 8.0.0.7

IBM MQ Appliance V8

Maintenance levels between 8.0.0.0 and 8.0.0.7

IBM MQ V9

Maintenance levels 9.0.0.0 - 9.0.0.1

IBM MQ V9 CD

IBM MQ 9.0.1 - 9.0.3

IBM MQ Appliance V9 CD

IBM MQ Appliance 9.0.1 - 9.0.3

REMEDIATION/FIXES
IBM MQ V8.0 & IBM MQ Appliance V8.0
Apply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]
Apply fix pack 8.0.0.8 for IBM MQ Appliance [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]
IBM MQ V9
Apply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]
IBM MQ V9 CD
Upgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]
IBM MQ Appliance V9 CD
Upgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]

WORKAROUNDS AND MITIGATIONS
None.

GET NOTIFIED ABOUT FUTURE SECURITY BULLETINS
 Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this.

REFERENCES
Complete CVSS v3 Guide [http://www.first.org/cvss/user-guide]
On-line Calculator v3 [http://www.first.org/cvss/calculator/3.0]

RELATED INFORMATION
IBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html]
IBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt]

CHANGE HISTORY
 30 Nov 2017: Initial version

*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin.

DISCLAIMER
According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.

Question: Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed (CVE-2017-1341) I need to understand details regarding Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed (CVE-2017-1341). Where can I find this information?

Answer:
CVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]
DESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.
CVSS Base Score: 3.7
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)


IBM Using Oracle JDBC driver specific properties through a datasource - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Properties directly supported by the Oracle JDBC driver that are not part of the JDBC specification cannot be used as a Custom Property in a datasource.

CAUSE
The Oracle JDBC driver has added support for a new Custom Property under connectionProperties..

RESOLVING THE PROBLEM
The method used with datasources is to set a Custom Property in the datasource as follows:

Name: connectionProperties
Value: propertyA=valueA;propertyB=valueB

For example, if you wish to set the property oracle.jdbc.V8Compatible=true, then you would specify the following.
Name: connectionProperties
Value: oracle.jdbc.V8Compatible=true

Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK

Question: How to set database specific custom properties in WebSphere Application Server? I am using Websphere Application Server (WAS) v8.5.x with Oracle 11.1 JDBC drivers and I want to set some oracle specific custom properties, when connecting to the database in Websphere Application Server. How to set such specific properties in Websphere Application Server?

Answer:
The method used with datasources is to set a Custom Property in the datasource as follows:

Name: connectionProperties
Value: propertyA=valueA;propertyB=valueB


IBM Tivoli Netcool/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States release notice; downloads; nco-p-nokia-nfmp; Probe for Nokia Network Functions Manager for Packet NEWS

ABSTRACT
 This new probe will be ready for downloading on July 20, 2017.

CONTENT

This probe is written to support Nokia Network Functions Manager for Packet release 17.3.

You can download the package you require from the IBM Passport Advantage website:

www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html]

Netcool/OMNIbus V8.1

If you are running Netcool/OMNIbus V8.1, a single package contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNL6HEN

The Netcool/OMNIbus V8.1 version of this probe supports the following Operating Systems:

AIX, Linux, Solaris and Windows.

Netcool/OMNIbus V7.4.0

If you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.

Part number Operating System CNL6DEN AIX CNL6EEN Linux CNL6FEN Solaris CNL6GEN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.

If, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:

https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]

Question:
What is the latest Alcatel 5620 SAM probe? We have the nco_p_alcatel_5620_sam_v13 probe, is there a newer version of the probe.
Does this probe support Release 14 of the 5620 SAM?

Answer:
You can download the package you require from the IBM Passport Advantage website:

www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html


IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States  TECHNOTE (FAQ)

QUESTION
 Which WebSphere DataPower virtual edition fix pack can I upgrade to and downgrade from?

CAUSE
Not all scrypt4 fix packs are compatible with the 5.0.0.0 OVA files that were released in November 2012 and March 2013. If you upgrade or downgrade with an incompatible fix pack, unexpected errors might occur.

ANSWER
 Use the following links to determine which fix packs are compatible with your virtual deployment.

 * 5.0.0.0 from 30 November 2012 (build 220750)
 * 5.0.0.0 from 29 March 2013 (build 227007)
 * 5.0.0.5
 * 5.0.0.6
 * 5.0.0.8 or later
 * 6.0.0.0 or later

5.0.0.0 from 30 November 2012 (build 220750)
When your virtual deployment is the OVA file from 30 November 2012, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.

Back to top

5.0.0.0 from 29 March 2013 (build 227007)
When your virtual deployment is the OVA file from 29 March 2013, you can install only the 5.0.0.0 fix pack and 5.0.0.8 or later fix packs from Fix Central. On Fix Central, the 5.0.0.5 and 5.0.0.6 fix packs are for the 5.0.0.0 OVA release from 30 November 2013.

Back to top

5.0.0.5
When your virtual deployment is 5.0.0.5, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.

Back to top

5.0.0.6
When your virtual deployment is 5.0.0.6, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013.

Back to top

5.0.0.8 or later
When your virtual deployment is 5.0.0.8 or later, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].

Note: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit.

Back to top

6.0.0.0 or later
When your virtual deployment is the 6.0.0.0 OVA file or a firmware upgrade through a 6.0.0.0 or later fix pack, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2].

Back to top

Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Service Gateway XG45 Virtual Edition VMware ESXi, VMware ESX 5.0.0, 6.0.0 Edition Independent

Question: How do I upgrade my virtual DataPower Appliance from 5.0 firmware to 6.0+ firmware? When attempting to upgrade my Virtual DataPower Appliance from 5.0.0.0 firmware version to 6.0+ firmware versions, I receive a failure message.

Answer: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit.


IBM Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit - United States WTX ITX Launcher On Success Delete On Failure Commit TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 IBM Transformation Extender (ITX) Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit.

SYMPTOM
Launcher fails to load a watch when On Success = Delete and On Failure = Commit are used.

CAUSE
This has been identified as a product defect under APAR PI64816

ENVIRONMENT
Using the IBM Transformation Extender (ITX) Launcher and 'On Success' is set to Delete and 'On Failure' is set to Commit.

DIAGNOSING THE PROBLEM
 The Compound system log reports the following Launcher FATAL error :

File Trigger FATAL Error : ValidateEKDirectories: Cannot find correct card index for watch #.

RESOLVING THE PROBLEM
Obtain patch for APAR PI64816.

Question:
Port number error starting 9.0 Launcher

I'm attempting to start up v9.0 for the first time with one .msl file on a Windows server and get the following error.  I also have v8.4 on this server and it starts fine.  I do not have v8.4 running when I attempt to start v9.0.

Cannot recognize if the system RecordChangeSystem.msl; has started. Reason: Server is unable to get the status of the system on port number 6,002.

I have the port range set to 7000/8000.  I've never seen this error before.

Any help?  Thanks.

Answer: Obtain patch for APAR PI64816.


IBM Datacap 9.0.1 FP1 - Readme doc - United States  PRODUCT README

ABSTRACT
 IBM Datacap 9.0.1 FP1 - Readme doc

CONTENT
About IBM Datacap 9.0.1 Feature Pack 1

Review this document for installation instructions and other important information before you install IBM® Datacap 9.0.1 Feature Pack 1, which cumulatively contains all feature pack updates since IBM Datacap Version 9.0.1 was released.

Upgrading to IBM Datacap 9.0.1 Feature Pack 1

From v9.0.1: use the Patch Installer from Fix Central

Installation Steps

Prerequisite:

· 1) Microsoft .NET Framework 4.6.1

· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe

· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013

· Run: vcredist_x86.exe

Install:

· 3) IBM Datacap 9.0.1.1

· Run: Update.exe

From v9.0.0.0, 9.0.0.1, 9.0.0.2 & 9.0.0.3: use the Full Installer from Passport Advantage

Installation Steps

Prerequisite:

· 1) Microsoft .NET Framework 4.6.1

· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe

· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013

· Run: vcredist_x86.exe

Install:

· 3) IBM Datacap 9.0.1.1

· Run: Setup.exe

Important

Updates are required only on Servers and thick client computers. No update is required for "thin client" computers. You must upgrade all thick clients and servers to the same IBM Datacap version and feature pack. Different versions of IBM Datacap are not compatible; therefore, you cannot connect an IBM Datacap client with a server that has a different IBM Datacap server version or feature pack installed. Operating Datacap Client or Datacap Web with an incompatible version of Datacap Server, or allowing different versions to access one database, can result in loss of data.

Once installed, this feature pack cannot be uninstalled. However, you can use "Uninstall or change a program" in Control Panel to uninstall the entire Datacap product.

The language you selected when installing Datacap 9.0.1 determined the language displayed in the InstallShield panels at that time, and also controls the language in which the InstallShield panels for this feature pack are displayed.

Alerts!

1) When running an update, the global ruleset DLLs are updated but the copies in each application are not updated.

As a result, new features and fixes are not applied to applications and customers might experience defects that have been fixed.

The global ruleset DLLs are in the Datacap\RRS folder. The application copies are in the application DCO rules folder.

Customers must manually update the ruleset DLLs in each application where they are installed.

2) When running an update, the master task configuration files are updated (Datacap\ProgramSet) but the setting in applications are not updated (in application DCO folder).

As a result, new features and fixes are not applied to applications and customers might experience problems that have been fixed.

The master task configuration is located in Datacap\ProgramSet. The application settings are in the application DCO folder.

Customers must manually update the task setting in each application where they are installed.

System requirements

Select the following link to see the hardware and software requirements for IBM Datacap.

http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html [http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html]

Search for ‘Datacap’, then select "Datacap "

Check the box ‘Show feature packs’ and select 9.0.1 for Feature Pack 1*.

New features added to IBM Datacap 9.0.1 Feature Pack 1

For a list of new features that were added to Datacap 9.0.1 in Feature Pack 1, see:
Highlights of IBM Datacap 9.0.1 Feature Pack 1 [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm].

http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm]

New Qualifications

IBM Datacap 9.0.1 Feature Pack 1 is qualified for use with:

· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;

See “Known Limitations” below for details)

· Oracle 12c (12.1.0.2.0)

· IBM Content Navigator 2.0.3 FP7

Issues fixed in IBM Datacap 9.0.1 Feature Pack 1

APAR Number Summary IO23893 Clicking on QA link in tmweb - Administrator fails with error "column named name already belongs to this datatable" if using admin database on SQL server IO24025 Can not import file which name contains '0x905C' such as "保険申告Updated.tif" IO24067 When customer use https + non-activeX to upload, some images will be corrupted frequently IO24082 Lineitem does not show up in Datacap Desktop Verify panel IO24102 Enhance IMail actions to use standard naming convention for ID's of pages created. IO24104 Using LLLDAP certain users are not able to login even when they are in the same group. LDAP is across multiple domains. IO24138 Couldn't create DC_P8 FileNet object error; action FNP8_SetURL () on 9.0 FP 3 and 9.0.1 IO24140 aindex.aspx does not update DATAFILE variable when a page is moved in batch view IO24141 DCDesktop Exception when performing a lookup query against an Oracle database IO24144 Batch aborts during ExcelWorkbookToImage with specific XLSX file IO24168 Page data is not generated when the page type is changed through batch structure in verify client of Datacap Navigator IO24169 when task has "-" and then change the batch status from hold to pending in edit job dialog, it will fail. IO24181 Unable to edit and enter values in multiple line edit box in tmweb Verifine panel IO24185 OCR_SR.RotateImageOCR_S () no longer compresses the TIFF image since applying 9.0 FP#2 was deployed IO24186 Thumbnail view of images is not activated in DcDesktop app until an image in batch tree view is clicked on IO24196 Setting a value to a custom column by main profile rule does not work. IO24199 Verify shortcut fails to show the batch list when the job name contains '( )' IO24205 System.OutOfMemory error returned by Datacap.Libraries.Convert.Outlook->OutlookMessageToImageAndAttachment () IO24213 Start bach panel non-overrideable validation not handled gracefully the second time around; Dc Desktop crashes IO24215 FNP8_CreateFolder () does not support / handle error in Italian IO24226 Page data failed to be shown in field details panel after running validation with some empty C nodes IO24227 CCO was not reloaded after running the rule so the re-OCR rule cannot take effect until relaunching the batch. IO24232 Main_Page no longer synch's up with custom data panel after switching from main_page to trailing page to main_page IO24249 Imprint.RedactParameters () converting color images to bitonal IO24249 Imprint.RedactByRegEx () only runs at Field level not at Page level but action help is slightly misleading IO24259 DcDesktop - certain columns in Job Monitor ONLY sort by Queue ID column IO24260 DSTUDIO: selecting ruleset "import files - all : Scan", returns message "The Document Hierarchy refers to some nonexistent Rules.". IO24282 MatchBarcodeBP throws an error in the rrs.log when processing non-barcode type pages. IO24289 tmweb fails to create setup file for a task if the app name begins with "AP" IO24381 SetNamePattern () with Convert.Unzip () is unable to resolve the naming pattern of the extracted image IO24384 Format and formatDescription are not supported in EDS IO24386 when the auto launch next batch is enabled, the page of the next verify page is not loaded. IO24387 Rescan status cannot be persisted after submitting if it is the only page in the batch IO24388 Split should not enabled on the page which is the only one in its parent document. IO24418 Images id are not numbered sequentially after fault with scanner occurs IO24427 Clicking on "Build Doc" button on custom panel generates exception error in DcDesktop App IO24439 Convert.ExcelWorkbookToImage () distorts the extracted tiff preventing GetBarcodeBP () from reading the barcode from the tiff image IO24447 rescanned page lost "ScanSrcPath" variable IO24461 Cannot paste value to a field if disable readonly on batch tree IO24470 After a job which jumped several tasks is edited via 'Edit Job' button, it could not be shown in Job Monitor IO24473 Batch is still in hold status even submitting it if session ever timeout. IO24475 Some Datacap css styles override ICN original ones, so impact ICN and other plugins. IO24477 image viewer error message does not conforming within image viewer. IO24486 Daeja ViewOne functionality of virtual as compared to Professional with DataCap
Known limitations in IBM Datacap 9.0.1 Feature Pack 1

Read this information to learn about known limitations in IBM Datacap 9.0.1 Feature Pack 1.

Component Summary TMWeb Scan Windows 10 supported with IBM Datacap 9.0.1 FP1 with the following known limitations:

1. TMweb's "IE Test" page may result in a dialog box titled “Accusoft Twain Pro7 common 9.0.013” with the message "picdll Load Library failed.”
2. When trying to perform a Web scan with a Physical Scanner connected (via twain drivers) , ie using Web Vscan configured with scancl.aspx, the message "picdll Load Library failed" may be displayed.

If any of these messages appear, TMWeb scanning will not be possible. Medical Claims When in MClaims Prof Red/Black FixupScan, clicking "Next LC" button will advance to the next page and display the data for it (Type and Status), but will keep the previous page selected as well, and changes to Status (from "Invalid Claim Type" to "New Claim") will not be saved.

Suggested workaround:
After clicking "Next LC" button, which will show previous page and current page selected in the Batch View display, then click the current page node in the Batch View display to properly select only the current page. After this one can continue to change the page Status and click "Next LC" button and repeat workaround for the next page. [/support/docview.wss?uid=swg27047895&aid=1] [/support/docview.wss?uid=swg27047895&aid=1]

Question:
Will Datacap support Windows 10, if so, which version is fully supported?

We want to if Datacap support windows 10, if so, which version supports it.

Please provide us official statement for the compatibility.

Answer:
IBM Datacap 9.0.1 Feature Pack 1 is qualified for use with:

· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;


IBM Configuring file content extraction tools for IBM Connections Search - United States stellent file content conversion extraction TECHNOTE (TROUBLESHOOTING)

PROBLEM
IBM Connections uses the Stellent (Oracle Outside In Technology) Export utility to extract text from documents of various types. The extracted text is added to the Search index allowing users to find documents based on the content.

When the Stellent utility is not configured correctly, file content will not be extracted or indexed. Therefore, search results within IBM Connections will not contain any matches on file content. For any content extraction issues, follow the steps in this tech note.

RESOLVING THE PROBLEM
 1 Stellent installation

Ensure that the following IBM Connections post-installation task has been carried out:
http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40 [http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40]

 2 Running the exporter in isolation from IBM Connections

To verify that the exporter is working correctly, you can run it on the command line in isolation from IBM Connections. To run the exporter executable on the command line, execute the following as the user that the Search WebSphere Application Server is running under:

1. Change directory to the Stellent binary location. For example:

 $ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport

2. Run the exporter command.
The exporter command has the following syntax:

 exporter inputpath=<path_to_input_file>
outputpath=<path_to_extracted_text_output>
outputid=FI_SEARCHTEXT

For example,
$ ./exporter inputpath=/root/translation.pdf \ outputpath=/root/testStellent.txt outputid=FI_SEARCHTEXT

If the text extraction worked successfully, you will see the following output:

Export complete

However, if you see a message like the one below, continue to step 3:

./exporter: error while loading shared libraries: libsc_ex.so: cannot open shared object file: No such file or directory

 3 Operating System Environment Variables

Ensure that the operating system environment variables LD_LIBRARY_PATH and PATH are set correctly in Section 1. Both variables should contain the Stellent installation directory. To get the current values of the environment variables, run the following commands as the user that the Search WebSphere Application Server is running under:

$ echo $LD_LIBRARY_PATH
$ echo $PATH

To verify that the Stellent exporter executable can be found through the PATH environment variable, run the following command:

$ which exporter

The output of this command should contain the full path to the exporter executable. For example:

/opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter

 4 WebSphere Environment

Using the WebSphere Application Server administration console, ensure that the WebSphere environment variable FILE_CONTENT_CONVERSION points to the exporter executable.

For example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter

 5 File Permissions

Ensure that the user that the Search WebSphere Application Server is running under has sufficient privileges. They should have read/write/execute permissions on the exporter executable and read/write permissions on the other files in the Stellent installation directory.

 6 Library compatibility

Verify that the libraries deployed with Stellent are compatible with your platform.

For example, on a 64 bit Linux system:
$ uname -a
Linux host1 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport
$ file libsc_ex.so
libsc_ex.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped

(Note that your Stellent installation may contain 32 bit libraries though you are running on 64 bit platform. This is not an issue, provided that the 32 bit compatible libraries are on the LD_LIBRARY_PATH or can be found on the shared library search path).

 7 Shared library dependencies

The Stellent exporter executable has a number of dependencies on both the shared libraries packaged with Stellent and on shared libraries installed on your system. To verify that all the required shared libraries can be found, use the 'ldd' command on the exporter executable as follows:

$ ldd -v exporter

Check the output of this command for any shared libraries marked as '=> not found'.

 Stellent shared library not found

If a Stellent shared library can't be found, then check that the setting of your LD_LIBRARY_PATH operating system environment variable contains the Stellent installation directory.

 System shared library not found

If a system shared library can't be found, then you are missing a prerequisite library.
NOTE: It is still possible to pick up libraries from locations other than those included in the LD_LIBRARY_PATH operating system environment variable, as long as they can be found elsewhere on the system's default search path.

In addition to libc.so.6, Stellent is dependent upon the following libraries:
libstdc++.so.5
libgcc_s.so.1

For Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5.

 *
 *

Question: DCS Document Conversion issue: java.util.MissingResourceException: Can't find resource for bundle  com.stellent.scd.ExportResources, key 127 DCS Document Conversion issue: java.util.MissingResourceException: Can't find resource for bundle com.stellent.scd.ExportResources, key 127

Answer:
In addition to libc.so.6, Stellent is dependent upon the following libraries:
libstdc++.so.5
libgcc_s.so.1

For Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5.


IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States IIB WMB FLASH (ALERT)

ABSTRACT
 IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux

CONTENT
IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to
CVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139

IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2

Remediation:

IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.

Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0

Question: Help with  IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux I need to understand details regarding Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux. Where can I find this information?

Answer:
IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to
CVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139

IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2


IBM Software maintenance strategy for CICS TS and its embedded components - United States Libery Java ; 5655S9700 R660 660 R600 600 HCI6600 R670 670 R700 700 HCI6700 5655-S97 5655S97 ; 5655Y0400 R680 680 R800 800 HCI6800 R690 690 R900 900 HCI6900 R700 700 R000 000 HCI7000 R710 710 R100 100 HCI7100 5655Y0401 5655-Y04 5655Y04 KIXINFO PRODUCT DOCUMENTATION

ABSTRACT
 CICS TS support is delivering the information in this document to help customers plan for updates to CICS Transaction Server for z/OS (CICS TS) and related software components such as WebSphere Liberty and CICS Explorer. Installing APAR fixes (PTFs) using Recommended Service Upgrades (RSUs) as early as possible can help avoid problems that could result in a service call, and as long as you test appropriately, help reduce risks to your business.

CONTENT

[/support/docview.wss?uid=swg27048530&aid=1]Embedded components in CICS TS [http://www-01.ibm.com/support/docview.wss?uid=swg27012749#delivering]
[/support/docview.wss?uid=swg27048530&aid=2]Update recommendations
[/support/docview.wss?uid=swg27048530&aid=3]Related information

Components in CICS TS

CICS TS provides the following embedded runtime components:

 * Equinox
   Equinox is an implementation of the OSGi core framework specification and is provided for both OSGi JVM servers and for Liberty JVM servers. Service for these components is provided when and if required.

 * Apache Axis2™
   Axis2 is an open source web services engine from the Apache Software Foundation and is used within CICS to provide the web service Java™ engine for the Axis2 JVM server environment. Service for this component is provided when and if required.

 * WebSphere Application Server Liberty Profile
   Liberty fix packs are provided on a regular basis through the CICS TS APAR delivery process and provide an update mechanism to keep the embedded CICS Liberty runtime synchronized with the fix packs provided by WebSphere Application Server. Keeping current helps you resolve problems faster for 2 reasons:  * Liberty APAR fixes (known as ifixes) can only be delivered on the latest Liberty fix pack that has been supplied by the CICS APAR process.
    * CICS APAR fixes can require other fixes such as WebSphere Liberty fix packs.

CICS Explorer and z/OS Explorer
The CICS Software Development Kit (SDK) for Java includes components from CICS for developing CICS Java applications. The CICS SDK for Servlet and JSP support includes Java Enterprise Edition (Java EE) and Liberty API libraries, and automatically installs required components such as WebSphere Developer Toolkit (WDT)." Service for these components is provided through the CICS Explorer fix pack process when and if required.
[/support/docview.wss?uid=swg27048530&aid=4] Back to Top

Update recommendations

Recommended Service Upgrade (RSU)
IBM recommends that you install all RSU [http://www-03.ibm.com/systems/z/os/zos/support/servicetest/] PTFs as preventive software maintenance for CICS TS. An RSU is a predefined collection of PTFs identified with a SOURCEID of RSUyymm, where yy indicates the last 2 digits of the year and mm indicates the month. [http://www-03.ibm.com/servers/eserver/zseries/zos/servicetst/]You can order an RSU [http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/]from ShopzSeries [https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp].

Equinox and Apache Axis2
There is unlikely to be much maintenance for Equinox and Axis2. Service for these components is provided when and if required, meaning it will be on a case by case basis and in most cases this will be to resolve service requests.

WebSphere Application Server Liberty Profile
Refer to Updating Liberty profile for CICS TS and z/OS Connect EE to latest version [http://www.ibm.com/support/docview.wss?uid=swg21993579] for a list of APARs you will need to update CICS TS and z/OS Connect Enterprise Edition (EE) to the latest version of WebSphere Application Server Liberty profile.

CICS Explorer
IBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4. For further details see Latest version of CICS Explorer and CICS Tools plug-ins for CICS Explorer [http://www.ibm.com/support/docview.wss?uid=swg21404312].

[/support/docview.wss?uid=swg27048530&aid=5] Back to Top

Related information:
 * Update Strategy for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27036014]

 * Fix list for IBM WebSphere Application Server Liberty [http://www.ibm.com/support/docview.wss?uid=swg27043863]

 * CICS TS embedded components [http://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.standards.doc/topics/supportedComponents.html]

 * Fixes by version for CICS products [http://www.ibm.com/support/docview.wss?uid=swg27008833]

[/support/docview.wss?uid=swg27048530&aid=6] Back to Top

PRODUCT ALIAS/SYNONYM
 CICS/TS CICS TS CICS Transaction Server

Question:
IZE0106E Connect failed with "Unsupported CICS release" after upgrading CICS TS V5.x Do I have to upgrade my CICS Explorer to the same release as CICS Transaction Server for z/OS (CICS TS)? I recently upgraded to a new release of CICS TS and now when I attempt to connect to CICS Explorer using a CMCI connection, I get message
IZE0106E Connect failed with "Unsupported CICS release" after upgrading
in CICS Explorer.

Answer: IBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4.