id
stringlengths 10
10
| document
stringlengths 304
140k
| question
stringlengths 61
1.77k
| answer
stringlengths 30
1.81k
|
|---|---|---|---|
TRAIN_Q000 | IBM STREAMS 4.1.1.1 and 4.1.1.2 JOBS DO NOT INHERIT THE ENVIRONMENT VARIABLES SET IN .BASHRC, WHEN STREAMS IS RUN AS A SYSTEM SERVICE - United States FLASH (ALERT)
ABSTRACT
In Streams 4.1.1.1 and 4.1.1.2 Streams jobs may not pick up the user enviroment from the streams user's .bashrc. This behavior is different from earlier releases. With these versions, when Streams is run as a system service, application environment variables must be set with streamtool.
CONTENT
Problem Description
When running Streams as a system service with Streams releases 4.1.1.1
or 4.1.1.2, toolkits and user applications that depend on the
user environment may have various errors.
For example the database toolkit might show the following error
if it does not pick up the ODBCINI environment variable:
* "An SQL operation failed. The SQL state is 08003, the SQL code
is 0 and the SQL message is [unixODBC][Driver
Manager]Connnection does not exist."
*
Problem Solution
To work around the issue, set environment variables that are needed by the application directly in the instance with: *
* streamtool setproperty
* -d <domain> -i <instance>
--application-ev <VARIABLE NAME>=<VARIABLE VALUE>
*
RELATED INFORMATION
APAR IT18432 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IT18432] | User environment variables no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2?
Have you found that after upgrade to Streams 4.1.1.1 or 4.1.1.2, that environment variables set in your .bashrc are no longer being set? For example ODBCINI is not set for the database toolkit and you get
An SQL operation failed. The SQL state is 08003, the SQL code
is 0 and the SQL message is [unixODBC][Driver
Manager]Connnection does not exist.
| To work around the issue, set environment variables that are needed by the application directly in the instance with: *
* streamtool setproperty
* -d <domain> -i <instance>
--application-ev <VARIABLE NAME>=<VARIABLE VALUE> |
TRAIN_Q001 | IBM Exit() action within User Defined Function in Impact Policy Language - United States netcool; impact; netcool/impact; nci; ipl; policy; language; exit; exit(); function; user; defined; custom; udf; parser; action; set; global; variable; var; get; setglobalvar; getglobalvar; globalvar TECHNOTE (FAQ)
QUESTION
and how to exit the Policy process from within a Custom Function
CAUSE
Using the Exit() parser function within a User Defined (or Custom) Function in Impact Policy Language (IPL) will not exit the Policy process, it will only exit the User Defined Function.
ANSWER
This is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call - for example:
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
* SetGlobalVar("ExitNow", 1);
*
* Exit();
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
* SetGlobalVar("ExitNow", 1);
*
* Exit();
*
*
*
*
*
*
*
*
*
*
* If(GetGlobalVar("ExitNow") == 1)
*
* {
Log(ID+WP+": Existing policy...");
* Exit
* ();
}
The above example ties in somewhat with the exampled configuration from the TechNote "Event Flagging with Go_NoGo checking" [ link below] and uses structured logging as covered in the TechNote "Structured logging in Policies" [ link below].
If the User Defined Function was nested within another User Defined Function one would have to exit each layer to return the Policy layer before the Exit() action would exit the Policy.
RELATED INFORMATION
Event Flagging with Go_NoGo checking [http://www-01.ibm.com/support/docview.wss?uid=swg21675015]
Structured Logging in Policies [http://www-01.ibm.com/support/docview.wss?uid=swg21596180] | Netcool/Impact (all versions): How is the Exit() action function expected to work with User Defined Functions? Netcool/Impact (all versions)
Using the Exit() action function within a User Defined Function in a Policy will not exit the Policy process. | This is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call |
TRAIN_Q003 | IBM Guide to properly setting up SSL within the IBM HTTP Server - United States ssl; handshake; secure socket layer; handshake failed; enable; ssl config; ssl setup; setup; IHS; crl; revocation; ssl; ssl; ssl; configure; config; config; config TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The following information can be used as a guide for setting up the Secure Sockets Layer (SSL) within the IBM HTTP Server. This document covers information on setting up SSL virtualhosts, creating keyfiles, certificates along with how to protect access to directories and URLs to specific ciphers. Also, included is documentation on how to trace and record SSL traffic between a client browser and the Web server.
RESOLVING THE PROBLEM
The following steps help guide you through the proper set up of SSL within the IBM HTTP Server:
1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements
2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake
3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)
4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)
5. Information that IBM WebSphere® Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server
1. Confirm that the Global Security Kit is installed and meets the minimum requirements
The Global Security Kit (GSKit) is a required component for the Secure Sockets Layer (SSL) enablement within the IBM HTTP Server. Therefore, it is important to confirm that a supported version of the Global Security Kit is installed prior to enabling SSL.
For a complete listing of IBM HTTP Server releases and corresponding Global Security Kit versions, click IBM HTTP Server: Global Security Kit (GSKit) supported versions [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21173214].
2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake
The iKeyman GUI, which is included within the IBM HTTP Server distribution, can be used to create a key database file (for example: key.kdb) needed to store personal server certificates required by the client browser during an SSL handshake.
For quick information on how to create a key database file and personal server certificates, refer to the technote IKEYMAN, How do I...? [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21006430]
More extensive information on using the iKeyman GUI to create key database files and certificates is located here: * For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fwelc_ikeymangui.html]
* For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fwelc_ikeymangui.html]
* For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.ihs.doc/ihs/welc_ikeymangui.html]
* For releases of IBM HTTP Server v9.0 [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.ihs.doc/ihs/welc_ikeymangui.html]
3. Enable SSL directives within the IBM HTTP Server's configuration file (httpd.conf)
1. Verify that the SSL modules are uncommented
* For Microsoft® Windows®:
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&aid=1]
* For UNIX® platforms:
LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&aid=2]
2. Create an SSL virtualhost stanza using the following examples and directives
If you are enabling one Web site for SSL, and the hostname is the same as the one already defined in the Global Scope for non-SSL (port 80), you can enable SSL as follows. This virtualhost uses the default hostname defined by the ServerName directive in the Global Scope and the IP address associated with it.
http://www.mycompany.com (non-SSL) 192.168.1.102 https://www.mycompany.com (SSL) 192.168.1.102
Example 1:
Listen 80
ServerName www.mycompany.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs"
DirectoryIndex index.html
Listen 443
<VirtualHost :443>
SSLEnable
SSLClientAuth None
</VirtualHost>
SSLDisable
KeyFile "c:/program files/ibm http server/key.kdb"
SSLV2Timeout 100
SSLV3Timeout 1000 [/support/docview.wss?uid=swg21179559&aid=3]
If you are enabling one Web site for SSL and the ServerName is different than the ServerName already defined in the Global Scope for non-SSL (port 80), you can enable SSL as follows. Both hostnames must be registered in DNS to a separate IP address, and both IP addresses must be configured on local network interface cards.
http://www.mycompany.com (non-SSL) 192.168.1.102 http://www.mycompany2.com (non-SSL) 192.168.1.103 https://www.mycompany2.com (SSL) 192.168.1.103
Example 2:
Listen 80
ServerName www.mycompany.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs"
DirectoryIndex index.html
<VirtualHost 192.168.1.103:80>
ServerName www.mycompany2.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs2">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs2"
DirectoryIndex index2.html
</VirtualHost>
Listen 443
<VirtualHost 192.168.1.103:443>
ServerName www.mycompany2.com
SSLEnable
SSLClientAuth None
<Directory "c:/Program Files/IBM HTTP Server/htdocs2">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs2"
DirectoryIndex index2.html
</VirtualHost>
SSLDisable
KeyFile "c:/program files/ibm http server/key.kdb"
SSLV2Timeout 100
SSLV3Timeout 1000
If you are enabling multiple Web sites for SSL, you can enable SSL as follows. All hostnames must be registered in DNS to a separate IP address. Also, all the IP addresses must be configured on a local network interface card. You must use the SSLServerCert directive to identify which personal server certificate in the key database file is passed to the client browser during the SSL handshake for each Web site. If the SSLServerCert directive is not defined, the IBM HTTP Server passes whatever certificate in the key database file is marked(*) as the "default key".
For more information on why different IP addresses are required when enabling multiple Web sites for SSL: IP-Based Virtual Hosting must be used if configuring multiple SSL Virtual Host [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21045922]http://www.mycompany.com (non-SSL) 192.168.1.102 https://www.mycompany.com (non-SSL) 192.168.1.102 http://www.mycompany2.com (non-SSL) 192.168.1.103 https://www.mycompany2.com (SSL) 192.168.1.103 http://www.mycompany3.com (non-SSL) 192.168.1.104 https://www.mycompany3.com (SSL) 192.168.1.104
Example 3:
Listen 80
ServerName www.mycompany.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs"
DirectoryIndex index.html
<VirtualHost 192.168.1.103:80>
ServerName www.mycompany2.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs2">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs2"
DirectoryIndex index2.html
</VirtualHost>
<VirtualHost 192.168.1.104:80>
ServerName www.mycompany3.com
<Directory "c:/Program Files/IBM HTTP Server/htdocs3">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs3"
DirectoryIndex index3.html
</VirtualHost>
Listen 443
<VirtualHost 192.168.1.102:443>
ServerName www.mycompany.com
SSLEnable
SSLClientAuth None
SSLServerCert mycompany
<Directory "c:/Program Files/IBM HTTP Server/htdocs">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs"
DirectoryIndex index.html
</VirtualHost>
<VirtualHost 192.168.1.103:443>
ServerName www.mycompany2.com
SSLEnable
SSLClientAuth None
SSLServerCert mycompany2
<Directory "c:/Program Files/IBM HTTP Server/htdocs2">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs2"
DirectoryIndex index2.html
</VirtualHost>
<VirtualHost 192.168.1.104:443>
ServerName www.mycompany3.com
SSLEnable
SSLClientAuth None
SSLServerCert mycompany3
<Directory "c:/Program Files/IBM HTTP Server/htdocs3">
Options Indexes
AllowOverride None
order allow,deny
allow from all
</Directory>
DocumentRoot "c:/program files/ibm http server/htdocs3"
DirectoryIndex index3.html
</VirtualHost>
SSLDisable
KeyFile "c:/program files/ibm http server/key.kdb"
SSLV2Timeout 100
SSLV3Timeout 1000
4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf).
* How to rewrite HTTP (port 80) requests to HTTPS (port 443)
The rewrite module (mod_rewrite.c) provided with the IBM HTTP Server can be used as an effective way to automatically rewrite all HTTP requests to HTTPS. For complete information click How to rewrite HTTP (port 80) requests to HTTPS (port 443) [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21114864].
* Logging SSL request information in the access log for IBM HTTP Server
The IBM HTTP Server implementation provides Secure Sockets Layer (SSL) environment variables that are configurable with the LogFormat directive in httpd.conf. For complete information click Logging SSL request information in the access log for IBM HTTP Server [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21176455].
* Enabling Certificate Revocation Lists (CRL) in the IBM HTTP Server
Certificate revocation provides the ability to revoke a client certificate given to the IBM HTTP Server by the browser when the key is compromised or when access permission to the key is revoked. CRL represents a database that contains a list of certificates revoked before their scheduled expiration date. For complete information: * For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html]
* For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSD28V_8.5.5/com.ibm.websphere.ihs.doc/ihs/cihs_crlinssl.html]
* For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html]
5. Information that IBM WebSphere Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server
* MustGather: SSL handshake and configuration problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141302]
* MustGather: CMS key database (.kdb) and certificate problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141303]
*
* Brief description of the SSL directives discussed in this document
*
Listen
*
*
*
*
* SSLEnable
*
*
*
*
* SSLClientAuth None
*
*
*
*
* SSLDisable
*
*
*
*
* KeyFile
*
*
*
*
* SSLV2Timeout
*
*
*
*
* SSLV3Timeout
*
*
*
*
* SSLServerCert
*
*
*
*
* SSLCipherSpec
*
*
*
*
* SSLCipherRequire
*
*
*
*
*
*
* For releases of IBM HTTP Server v7.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.0 [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.5 [http://www-01.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.ihs.doc/ihs/rihs_ssldirs.html] For releases of IBM HTTP Server v9.0 [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.ihs.doc/ihs/rihs_ssldirs.html] | How to configure SSL mutual authentication in IBM HTTP Server?
We are running IHS v7 and our application team has a specific webservice that they require SSL mutual authentication to be enabled for at the http server. Does anyone know how to set this up on IHS? Or any documentation?
Thanks
| The following steps help guide you through the proper set up of SSL within the IBM HTTP Server:
1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements
2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake
3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)
4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)
5. Information that IBM WebSphere® Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server |
TRAIN_Q005 | IBM Support's Guide to Rules File Processing - United States rules; rules file; array TECHNOTE (FAQ)
QUESTION
Support Guide : Are there any rules file examples?
ANSWER
The Netcool Technical Support Guide to rules file processing is provided as a collection of commonly used rules file techniques.
Please refer to the Netcool/OMNIbus Probe and Gateway Guide for general guidance to rules file processing.
RulesfileProcessing_SupportsGuide_30.pdf [/support/docview.wss?uid=swg21903536&aid=2]RulesfileProcessing_SupportsGuide_30.pdf [/support/docview.wss?uid=swg21903536&aid=1] | What happened to load.rules FAQ example? The load.rules maths function example rules file does not appear to be available anymore? | Netcool Technical Support Guide to rules file processing is provided as a collection of commonly used rules file techniques. |
TRAIN_Q006 | IBM Security Bulletin: IBM Tivoli Network Manager IP Edition is affected by an Apache CXF vulnerability (CVE-2017-3156) - United States SECURITY BULLETIN
SUMMARY
Vulnerability has been addressed in the Apache CXF component of Tivoli Network Manager IP Edition.
VULNERABILITY DETAILS
CVEID: CVE-2017-3156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3156]
DESCRIPTION: Apache CXF could provide weaker than expected security, caused by the failure to use the OAuth2 Hawk and JOSE MAC Validation code. A remote attacker could exploit this vulnerability using timing attacks to obtain sensitive information.
CVSS Base Score: 5.9
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/130249 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130249] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
Tivoli Network Manager IP Edition 4.1.1 (Huawei MTOSI Collector install)
Tivoli Network Manager IP Edition 4.2.0 (Huawei MTOSI Collector install)
REMEDIATION/FIXES
Product VRMF APAR Remediation/First Fix Tivoli Network Manager IP Edition 4.1.1 IV99816 Please call IBM service and reference APAR IV99816, to obtain a fix if needed for 4.1.1 release. Tivoli Network Manager IP Edition 4.2.0 IV99816 CXF 3.1.10 has been upgraded in 4.2 FixPack 3.
http://www-01.ibm.com/support/docview.wss?uid=swg24043575 [http://www-01.ibm.com/support/docview.wss?uid=swg24043575] 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
15 September 2017 : Original Version Published
*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. | Is ITNM exposed to Apache CXF vulnerability (CVE-2017-3156)? Is ITNM versions are affected by Apache CXF vulnerability (CVE-2017-3156), If yes then what are all the version will be affected and where I can find the details? | CVEID: CVE-2017-3156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3156]
DESCRIPTION: Apache CXF could provide weaker than expected security, caused by the failure to use the OAuth2 Hawk and JOSE MAC Validation code. A remote attacker could exploit this vulnerability using timing attacks to obtain sensitive information.
CVSS Base Score: 5.9
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/130249 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130249] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) |
TRAIN_Q007 | IBM 2035 MQRC_NOT_AUTHORIZED Connecting to WebSphere MQ from WebSphere Application Server via CLIENT Bindings - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This article covers the most common reasons why an application running in WebSphere Application Server receives a 2035 MQRC_NOT_AUTHORIZED error when connecting to MQ as a client over a network. Quick steps to work around the MQRC_NOT_AUTHORIZED errors during development are provided in the 'Resolving the problem' section, as well as considerations for implementing security in production environments. A summary is also provided of behavior for outbound scenarios with container-managed and component-managed security, as well as inbound behavior for listener ports and activiation specifications
SYMPTOM
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')
CAUSE
The two most likely reasons why the connection is refused by MQ are as follows:
1. The user identifier passed across the client connection from the application server to MQ is not known on the server where the MQ queue manager is running, is not authorised to connect to MQ, or is longer than 12 characters and has been truncated.
We discuss how this user identifier is obtained and passed over the connection in more detail below.
For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:
AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained.
For UNIX no entry in the MQ error logs would be seen by default.
See technote MQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 [http://www-01.ibm.com/support/docview.wss?rs=171&uid=swg21299319] for details of enabling error log entries on all platforms.
2. The user identifier passed across the client connection from the application server to MQ is a member of the 'mqm' group on the server hosting the MQ queue manager, and a Channel Authentication Record (CHLAUTH) exists that blocks administrative access to the queue manager. WebSphere MQ configures a CHLAUTH record by default in WebSphere MQ Version 7.1 and later that blocks all MQ admins from connecting as a client to the queue manager.
The following error in the MQ error logs would be seen for this scenario:
AMQ9777: Channel was blocked
See the Error logs on Windows, UNIX and Linux systems [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r5/topic/com.ibm.mq.tro.doc/q039560_.htm] section of the MQ Information Center for the location of the MQ error logs.
DIAGNOSING THE PROBLEM
To understand the cause of the MQRC_NOT_AUTHORIZED reason code, you need to understand what username (and password) is being used by MQ to authorise the application server.
Please note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections.
Password authentication is provided out of the box in IBM MQ V8.0. More details on the new IBM MQ V8.0 security features are available in this presentation [https://www.slideshare.net/MoragHughson/websphere-mq-v8-security-deep-dive].
For WebSphere MQ V7.5 and earlier, this means that while the understanding provided in this technote over how usernames/passwords are passed from the application server to MQ is helpful for development environments, solving the security requirements of production environments usually also requires one of the following approaches:
* Mutual SSL/TLS authentication.
MQ provides out-of-the-box features to authenticate a remotely attaching client using the digital certificate they provide for SSL/TLS transport security. For example by configuring an SSLPEER rule on the SVRCONN channel to match the Distinguished Name in the certificate of the WebSphere Application Server, and establishing trust in the issuer of that certificate.
* A custom, or 3rd party supplied, WebSphere MQ Security Exit
A security exit can be written for MQ that performs username and password authentication against a repository, such as the local operating system on the MQ server, or an LDAP repository.
When using a security exit for authentication it is important that SSL/TLS transport security is still configured, to ensure passwords are not sent in plain text.
MCA user ID (MCAUSER) configured on the Server Connection (SVRCONN) channel If an MCAUSER is configured on the SVRCONN channel that the application server is using to connect, and no security exit or mapping Channel Authentication Record is installed, then this overrides the username provided by the application server.
It is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL/TLS authentication exclusively for authentication.
Default behaviour when no credentials are supplied in the application server
If no credentials are supplied by the application on the createConnection call, and neither of the component managed or container managed security systems described below are configured, then WebSphere Application Server provides a blank username to MQ. This causes MQ to authorise the client based on the userid that the MQ listener is running under. In the majority of cases this is 'mqm' on UNIX/Linux systems and 'MUSR_MQADMIN' on Windows.
As these are administrative MQ users, they will be blocked by default in WebSphere MQ V7.1 and higher, with a AMQ9777 error logged in the error logs of the queue manager.
Container-managed security for outbound connections
The recommended way to configure the username and password passed to MQ by the application server for outbound connections, is to use container-managed security. Outbound connections are those created using a Connection Factory, rather than a Listener Port or Activation Specification.
Usernames of 12 characters or less are passed to MQ by the appliaction server. Usernames longer than 12 characters in length will be truncated, either during authorisation (on UNIX), or in the MQMD of messages that are sent.
Container-managed security means that the deployment descriptor, or EJB 3.0 annotations, of the application declare a resource reference with authentication type set to Container.
Then when the application looks up the Connection Factory in JNDI, it does so indirectly via the resource reference. For example an EJB 2.1 application would perform a JNDI lookup as follows, where "jms/MyResourceRef" has been declared as a resource reference in the deployment descriptor:
ConnectionFactory myCF = (ConnectionFactory)ctx.lookup("java:comp/env/jms/MyResourceRef")
An EJB 3.0 application might declare an annotated object property on the bean as follows:
@Resource(name = "jms/MyResourceRef",
authenticationType = AuthenticationType.CONTAINER)
private javax.jms.ConnectionFactory myCF;
When the application is deployed by an administrator, they bind this authentication alias to an actual Connection Factory that has been created in JNDI, and assign it a J2C authentication alias on deployment.
It is the username and password contained in this authentication alias that is then passed to MQ/JMS by the application server when the application connects. This approach puts the administrator in control of which username and password is used by each application, and prevents a different application from looking up the connection factory in JNDI directly to connect with the same username and password.
A default container-managed authentication alias can be supplied on the configuration panels in the administrative console for MQ connection factories. This default will only be used in the case that an application uses a resource reference configured for container-managed security, but the administrator has not bound it to an authentication alias during deployment. A screen shot is provided below:
[/support/docview.wss?uid=swg21636093&aid=1] [/support/docview.wss?uid=swg21636093&aid=1]
Default component-managed authentication alias for outbound connections
For cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default.
This default is called the "component-managed authentication alias" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin:
* JACL:
wsadmin>set cell [ $AdminConfig getid "/Cell:mycell" ]
mycell(cells/mycell|cell.xml#Cell_1)
wsadmin>$AdminTask listWMQConnectionFactories $cell
MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)
wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }
MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)
* Jython:
wsadmin>cell = AdminConfig.getid("/Cell:mycell")
wsadmin>AdminTask.listWMQConnectionFactories(cell)
'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'
wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', "-componentAuthAlias myalias")
'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'
Authentication alias for inbound MDB connections using an activation specification For inbound connections using an activation specification an authentication alias can be specified by the administrator when deploying the application, or a default authentication alias can be specified on the activation specification via the administrative console.
Authentication alias for inbound MDB connections using a listener port
For inbound connections using a listener port, the value specified in the "Container-managed authentication alias" setting of the connection factory (seen in the above screenshot) is used.
On zOS, first the "Container-managed authentication alias" is checked and used if set, then the "Component-managed authentication alias" is checked and used it set.
RESOLVING THE PROBLEM
The simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows:
1. Choose a user that you want WebSphere Application Server to be authenticated as. Typically the user chosen should have authority relevant to the context of the operations required by the application running in WebSphere Application Server and no more. For example, 'mqm' or other super user is not appropriate.
2. If this user is an MQ administrative user, then relax the Channel Authentication Record (CHLAUTH) security in MQ V7.1 or higher, so that administrative connections are not blocked on the SVRCONN channel you wish to use. An example MQSC command to do this for a SVRCONN channel called 'WAS.CLIENTS' is provided as follows:
SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY)
3. Configure the SVRCONN channel to set the MCA user ID (MCAUSER) to the user you have chosen. An example MQSC command to configure a SVRCONN channel to use 'myuser' as the MCA user ID is provided as follows:
ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')
The following additional considerations are important for production environments: For all production environments where transport security is required, SSL/TLS security must be configured between the application server and MQ.
In order to configure SSL/TLS transport security, you must establish the appropriate trust between the MQ queue manager and WebSphere Application Server. The application server, who initiates the SSL/TLS handshake, must always be configured to trust the certificate provided by the MQ queue manager . If the application server is configured to send a certificate to the MQ queue manager, then the queue manager must also be configured to trust it.
If trust is not correctly configured on both sides, you will encounter 2393 MQRC_SSL_INITIALIZATION_ERROR reason codes after enabling SSL/TLS on the connection.
If you do not have a security exit that performs username and password authentication, then you should configure mutual SSL/TLS authentication on your Server Connection channel to cause the queue manager to require a trusted certificate is provided by the application server. To do this you set "SSL Authentication" to "Required" in the MQ Explorer or SSLCAUTH(REQUIRED) via MQSC.
If you do have a security exit that performs username and password authentication installed in your MQ server, then configure your application to supply a username and password for validation by that security exit. The details of how to configure the username and password passed to MQ by the application server are described above in the "Diagnosing the problem" section.
All Server Connection channels that do not have SSL/TLS security applied should be disabled. Example MQSC commands to disable the SYSTEM.DEF.SVRCONN channel are provided as follows (these assume no user exists on the MQ server called 'NOAUTH'):
ALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH')
STOP CHL(SYSTEM.DEF.SVRCONN)
Details of how to configure the private certificate and trust of a MQ queue manager, and to enable SSL security on a Server Connection channel, see the following locations in the MQ information center:
* To configure the certificates and trust of the MQ queue manager see the following topic:
Configuring SSL on queue managers [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_ssl_channels.htm]
* To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:
Configuring SSL channels [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.explorer.doc/e_ssl_channels.htm]
Details of how you configure trust within WebSphere Application Server, and whether the application server sends a certificate to MQ for authentication, are in the following locations in the WebSphere Application Server information center: * To create or modify an SSL Configuration containing the appropriate SSL/TLS configuration for connecting to MQ, see the following topic:
SSL configurations [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]
Note that MQ requires you specify a matching Cipher Suite / Cipher Spec on both sides of the connection, as it checks the negotiated Cipher Suite matches the SSLCIPH setting on the channel after the handshake is complete. As a result the WebSphere Application Server SSL Configuration should be configured to contain only the Cipher Suite that matches the SSLCIPH setting on the Server Connection channel. See the following topic in the MQ information center for details of matching pairs:
CipherSuite and CipherSpec name mappings for connections to a WebSphere® MQ queue manager [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.msc.doc/xms_csecure_mapping_wmq.html]
* To enable SSL/TLS on a client connection, and choose which SSL Configuration to use, see the "Use SSL to secure communication with Websphere MQ", "Centrally managed" and "Specific configuration" sections of the following topics on Connection Factories and Activation Specifications
WebSphere MQ messaging provider connection factory settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pjcfm]
WebSphere MQ messaging provider activation specification settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pasm]
Cross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server for z/OS Java Messaging Service (JMS) z/OS, OS/390 8.5, 8.0, 7.0 Business Integration WebSphere Business Monitor AIX, HP-UX, Linux, Solaris, Windows, z/OS 7.5.1, 7.5, 7.0 Advanced, Basic Business Integration WebSphere Message Broker Environment AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0, 8.0, 7.0 Business Integration WebSphere MQ Clients AIX, HP-UX, IBM i, Linux, Windows 8.0, 7.5, 7.1, 7.0 | Why do I get an exception when calling MQ after migrating my BPM environment (2035 MQRC_NOT_AUTHORIZED) ?
We migrated our BPM environment from V8.0 to 8.5.7. When we attempt to call the MQ service we are getting the following exception:
[10/16/17 13:50:05:273 AST] 0000026d SystemOut O
com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The
security authentication was not valid that was supplied for QueueManager
'QM1' with connection mode 'Client' and host name 'MQ1(1414)'.
Please check if the supplied username and password are correct on the
QueueManager to which you are connecting.
...
Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed
with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
at
com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.jav
a:204)
... 162 more
The same MQ service is working fine in the old BPM environment. User name and password configured for the queue is correct. However, when we check the MQ logs, we observing the username is not used, instead the sys admin user seems to be used. | Default component-managed authentication alias for outbound connections
For cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default.
This default is called the "component-managed authentication alias" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin:
* JACL:
wsadmin>set cell [ $AdminConfig getid "/Cell:mycell" ]
mycell(cells/mycell|cell.xml#Cell_1)
wsadmin>$AdminTask listWMQConnectionFactories $cell
MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)
wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }
MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)
* Jython:
wsadmin>cell = AdminConfig.getid("/Cell:mycell")
wsadmin>AdminTask.listWMQConnectionFactories(cell)
'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'
wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', "-componentAuthAlias myalias")
'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)' |
TRAIN_Q008 | IBM Rational Application Developer Support Policy for 64 bit technology - United States RSM; RSD; RSA; RAD; caspian64 bit; 64-bit; RAD 7 64 bit; RAD 7 OS; operating system; Rational Application Developer; X64; Windows 64 bit; supported OS; AMD; PMR #13878; 379; 000; 13878379000; 1263677; 64bit; 64 bit; 32 bit; 32bit; 32-bit; 64-bit; O/S; OS; requirements; system requirements; 8.0.3; 8.0; 7.5; v8.0.3; v7.5; v7.0; v8.0; v7.5.4; 803; windows 7; server; profile; websphere; test environment; create profile; button; greyed; Run Profile Management Tool ; disabled; IBM Software Development Kit; SDK; JRE; Program Files(x86); WAS; websphere application server; clearcase; scm; clearcase scm adapter; rational requisitepro; reqpro; heap size; jvm; max os x; os x; osx; mac TECHNOTE (FAQ)
QUESTION
What is the support policy for using IBM Rational Application Developer for WebSphere Software, IBM Rational Software Architect, IBM Rational Software Modeler or IBM Rational Systems Developer version 7.x and 8.x with 64-bit operating systems for Microsoft Windows or Linux?
CAUSE
The 7.0.0.x, v7.5.x and v8.0 to 8.0.2 versions of these applications were not designed to take advantage of 64 bit computing and only use 32-bit technology.
ANSWER
The following IBM Rational Software version 7.x products are only supported on specified 64 bit operating systems running in 32 bit mode:
* Rational Application Developer for WebSphere Software
* Rational Software Architect
* Rational Software Modeler
* Rational Systems Developer
Similarly, Rational Application Developer (RAD) and Rational Software Architect (RSA) version 8.0 to 8.0.2 are only supported on specified 64 bit operating systems running in 32 bit mode. Rational Application Developer v8.0.3+ is available as a 64-bit application install on specified 64-bit operating systems, in addition to a 32-bit application install.
There is only one installation package. When installing RAD/RSA using IBM Installation Manager, on the Location page , if your operating system is 64-bit, then select 64-bit or 32-bit to install the product in the corresponding bit mode.
These products will be referred to generically as Rational Software Development Platform (RSDP) based products. For example, WebSphere Integration Developer v6.x/7.x is RSDP based.
Examples of some 64 bit Operating Systems:
* Microsoft Windows XP Professional x64 Edition (running on an AMD or Intel processor)
* Microsoft Windows 7 Professional 64-bit
* Red Hat Linux Enterprise Server 4+ running on x86-64 bit
* RAD 9.0 under 9.0.1 introduced support for Mac OS x - Lion 10.7 32 bit (with Oracle JDK for Mac OS X 7.0 Update 40) and Mountain Lion 10.8 - 32 bit. Likewise for RSA for WebSphere 9.0.0.1.
RAD 9.0.1.1 introduced support for 64-bit exploit on Mac OS x Mavericks 10.9 ( with Oracle JDK for Mac OS X 7.0 Update 71)
RSA 9.1.2 introduced support for 64-bit exploit on Mac OS X Yosemite 10.10 and OS X El Capitan 10.11 (with Oracle JDK 7.0 Update 75 for OS X)
Note: RSDP 32-bit JVM based products, do not require any additional or special set-up on a supported 64-bit operating system (O/S).
They run on the provided/supported 32-bit JVM for that RSDP product, as is.
Review the following documents for more details on the system requirements:
* (7014264) Rational Application Developer System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014264]
* (7014274) Rational Software Architect Family System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014274]
* (7014269) Rational Software Modeler System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014269]
The above items such as the Rational Application Developer System Requirements List cover latest versions and operating systems such as Windows Vista and Windows 7. Support is limited to 32 bit mode on 64 bit operating systems on all versions prior to Rational Application Developer 8.0.3. For more information consult:
Known problems and limitations to installing 64-bit Rational Application Developer [http://www.ibm.com/support/docview.wss?uid=swg21499482]
as referred to by the above Rational Application Developer System Requirements List. The following technote:
- Benefits, requirements, limitations, and known issues for Rational Software Architect products running as 64-bit applications starting from v8.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg27021665]
, especially Benefits, describes what is possible with a larger heap size with the 64-bit JVM.
In deciding if you want a 64-bit install of RAD/RSA, it is useful to know that the ClearCase SCM Adapter and the Rational RequisitePro integration features/plugins are not supported or provided. These are only available as 32-bit eclipse plugins.
If you have any further questions, contact IBM Support for Rational Application Developer, or the appropriate IBM RSDP product support team.
WebSphere Servers that are shipped with RSDP products:
The various WebSphere Application Server v6.x/7.x servers shipped with Rational Application Developer or Rational Software Architect {for WebSphere} prior to v8.0.4 are only provided as 32 bit editions. As of Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.4+, 64 bit editions of WebSphere Application Server v6.x/7.x servers are shipped in addition to the 32 bit editions.
The WebSphere Application Server v8.x (not beta) server shipped with Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.3+ is provided as one edition, and there is an installation option to install either the 32 bit or 64 bit JVM/JRE (IBM Software Development Kit (SDK)). Any 64 bit edition or 64-bit JVM requires a supported 64 bit operating system. This IBM Education Assistant Module/PDF : IBM WebSphere Application Server V8 Distributed platform installation [http://publib.boulder.ibm.com/infocenter/ieduasst/v1r1m0/topic/com.ibm.iea.was_v8/was/8.0/Installation/WASV8_dist_install.pdf] , demonstrates selecting a 32-bit or 64-bit SDK as part of a WAS v8.0 install using IBM Installation manager. If the WAS v8.0 installation is on a 32-bit operating system, this feature choice between IBM 32-bit SDK Java 6.0 or IBM 64-bit SDK Java 6.0 is not available and the installation will automatically default to the IBM 32-bit SDK Java 6.0.
The shipped WebSphere Portal Server v6.x/7.x servers are 32 bit or 64 bit editions. depending on whether you chose the IBM WebSphere Application Server Network Deployment, 32-bit or 64-bit server to install on.
Note: It is possible to work with any 64 bit remotely accessible or local stand-alone WebSphere Application Server v6.x/7.x/8.x. In Rational Application Developer 8.0.3+ be aware of the Info Center topic: Creating profiles for WebSphere Application Server on a 64-bit machine [Creating%20profiles%20for%20WebSphere%20Application%20Server%20on%20a%2064-bit%20machine] and see this APAR opened against RAD 8.5.1/8.5.5 : PI06339: A 64-bit install of the WebSphere Application Server Profile Management Tool may not launch on Windows 7. RELATED INFORMATION
Benefits for RSA v8.0.3 products running as 64-bit app [http://www.ibm.com/support/docview.wss?uid=swg27021665]
Internet Explorer v9+ required if using 64-bit Bit Mode [http://www.ibm.com/support/docview.wss?uid=swg21502701]
RAD 8.0.3+ IC: Creating profiles for WAS on a 64-bit ma [http://publib.boulder.ibm.com/infocenter/radhelp/v8/index.jsp?topic=/com.ibm.servertools.doc/topics/rbitmachine.html]
Rational ClearCase SCM adapter not available for 64-bit [http://www.ibm.com/support/docview.wss?uid=swg21502974]
Cannot install the Java Visual Editor in RAD 64 bit [http://www.ibm.com/support/docview.wss?uid=swg21499219]
RAD64bit Known problems to install or run [http://www.ibm.com/support/docview.wss?uid=swg21499482]
WAS V8.0 & V8.5 64-bit Install offer Program Files (x86 [https://developer.ibm.com/answers/questions/175210/why-does-was-v80-and-v85-offer-program-files-x86-a.html]
About SCM Adapter support on 64 Bit [http://www.ibm.com/support/docview.wss?uid=swg21460547]
Conversion of 32 bit to 64 bit WAS on the same machine [http://www.ibm.com/support/docview.wss?uid=swg21625930]
RAD901: Installing RAD for WebSphere Software [http://www-01.ibm.com/support/knowledgecenter/SSRTLW_9.0.1/com.ibm.rad.install.doc/topics/t_install_product.html]
RAD 9.0.x: new features and enhancements-9.0.1-new_OSup [http://www-01.ibm.com/support/docview.wss?uid=swg27038836#whatsnew_901_OSupdates]
RAD 9.0.1 System Requirements - O/S [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/osForProduct?deliverableId=1374678040873#osFamily-1]
RSA(4WS) 9.0.x: new features and enhancements [http://www.ibm.com/support/docview.wss?uid=swg27038488]
RSA 9.1.2: new features and enhancements - jdk [http://www-01.ibm.com/support/docview.wss?uid=swg27041555#whatsnew_912_JTE]
A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21504145]
Cross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Documentation Linux, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5, 7.0.0.6, 7.0.0.7, 7.0.0.8 Software Development Rational Software Modeler Documentation Windows, Linux 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Systems Developer Documentation Linux, Solaris, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Software Architect for WebSphere Software General Information Linux, Windows 7.5, 7.5.1, 7.5.2 | Is the Requisite Pro (ReqPro) feature/plugin supported with a 64-bit RAD/RSA(4WS) 851+ installation Is the Requisite Pro (ReqPro) feature/plugin supported with a 64-bit install of RAD/RSA(4WS) 851? | the Rational RequisitePro integration features/plugins are not supported or provided. These are only available as 32-bit eclipse plugins. |
TRAIN_Q009 | IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States ACCE; CE; Property; FEM TECHNOTE (FAQ)
QUESTION
With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class
1. Launch FEM
2. Expand the object store and document class tree. Right click on the document class and select "Properties"
3. Go to "Properties Definitions" tab, highlight the property definition and click "Edit"
4. Make the modification and click OK
5. Click OK again to save the change
How to perform the same operation with FileNet Content Engine - ACCE?
ANSWER
Follow the below steps to update the property definition properties on ACCE:
1. Launch ACCE
2. Expand the object stores folder and click the object store to open the Object store tab
3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab
4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify
5. ACCE will open that property definition in a new Properties tab
6. Modify the property definition as required
7. Go back to the Class Definition tab and click Save | Unable to locate the More tab of Document class - Property definition tab - property template configuration to update Is Required setting. Unable to locate the More tab of Document class - Property definition tab - property template configuration to update Is Required setting. Environment is running on Content Engine 5.2.0.3. | Follow the below steps to update the property definition properties on ACCE:
1. Launch ACCE
2. Expand the object stores folder and click the object store to open the Object store tab
3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab
4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify
5. ACCE will open that property definition in a new Properties tab
6. Modify the property definition as required
7. Go back to the Class Definition tab and click Save |
TRAIN_Q010 | IBM Starting WebSphere Application Server gives warning message - Could not lock User prefs - United States Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences.
SYMPTOM
The following message can be seen in the systemout.log:
[9/11/11 18:03:19:921 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences syncWorld Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
[9/11/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs. Unix error code 2.
CAUSE
The non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's "/etc/.java/.systemPrefs". This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log.
The root ID used to start Websphere Application Server can not find the Java system pref file.
DIAGNOSING THE PROBLEM
For non-root, you can confirm this issue by trying to start WebSphere using the "root" ID. Review the Websphere_Home/profiles/<profile_name>/logs/<failing server_name/systemout.log to verify that you no longer see the warning messages.
For root, verify if the /etc/.java/.systemPrefs exists
RESOLVING THE PROBLEM
For non-root :
Create a User_Home directory for this non-root user and restart WebSphere Application Server. If this does not resolve the issue use the following 2 suggestions below :
NOTE : The "dot" in front of the directories below represent that these are "hidden" directories. So the "dot" must be in front of the directory name to go into the directory or to access them.
1. Try giving 755 permission for /home/wasadmin/.java/.userPrefs
2. Add "-Djava.util.prefs.userRoot=/home/wasadmin/preps" as a SDK generic jvm argument
To set the argument on the SDK:
1. In the administrative console, click Servers > Server Types > WebSphere application servers , and select the server that you want to add the generic argument to..
2. Then, in the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine.
3. Specify -Djava.util.prefs.userRoot=/home/wasadmin/preps for the Generic JVM Arguments property, and click OK .
4. Click Save to save your changes.
5. Restart the application server.
For root : 1. Create a Java system pref directory
sudo mkdir -p /etc/.java/.systemPrefs
2. Restart the application server. | managesdk.sh -listEnabledProfileAll fails with error: Couldn't get file lock.
I am installing WebGUI FP13 and it is failing with the symptoms described in below technote.
https://www-01.ibm.com/support/docview.wss?uid=swg21993160
As described in above technote when I run managesdk.sh script it fails with below errors.
./managesdk.sh -listEnabledProfileAll
Sep 26, 2018 10:14:12 AM java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.
Please let me know what could be the issue? | The non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's "/etc/.java/.systemPrefs". This produces the aforementioned warning messages every 30 seconds in the profile_root/logs/server_name/systemout.log.
The root ID used to start Websphere Application Server can not find the Java system pref file. |
TRAIN_Q011 | IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
You have successfully installed an IBM SPSS Statistics product on a Mac computer. When you start the License Authorization Wizard (LAW) to enter the authorization code for licensing.
You receive the following message:
"Warning! You do not have the correct administrator privileges to license this product. Log in as administrator and try again, or contact your network administrator to correct this issue.
"
Once this message is displayed the only option available is "OK" to click on and you cannot enter your authorization code.
RESOLVING THE PROBLEM
Below is a picture of the warning:
[/support/docview.wss?uid=swg21966637&aid=1] [/support/docview.wss?uid=swg21966637&aid=1]
If you encounter this message, perform the following procedure:
1. If open, close the IBM SPSS Statistics product.
2. If open, close the License Authorization Wizard.
3. Open Finder.
4. Select the 'Go' menu.
5. Select the 'Utilities' menu.
6. Open the 'Terminal' program.
7. Type (copy/paste) the following command:
cd /Applications/IBM/SPSS/Statistics/
8.
9. Press Enter/Return.
10. Perform the procedure corresponding to the Statistics product version as described below:
Statistics Release 20 1. Type (copy/paste) the following command:
sudo chown -R root:admin 20
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
Statistics Release 21 1. Type (copy/paste) the following command:
sudo chown -R root:admin 21
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
Statistics Release 22 1. Type (copy/paste) the following command:
sudo chown -R root:admin 22
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
Statistics Release 23 1. Type (copy/paste) the following command:
sudo chown -R root:admin 23
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
Statistics Release 24 1. Type (copy/paste) the following command:
sudo chown -R root:admin 24
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
7.
8.
Statistics Release 25 1. Type (copy/paste) the following command:
sudo chown -R root:admin 25
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product.
To confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22)
cd /Applications/IBM/SPSS/Statistics/22/SPSSStatistics.app/Contents
then, type the following:
ls -l
(2) Press Enter/Return.
If you see some or all of subfolders shows a group ownership other than 'admin' (as displayed in Picture1), the procedure did not succeed. You will need to have your Mac IT support contact IBM SPSS Support for further assistance.
Picture1:
[/support/docview.wss?uid=swg21966637&aid=2] [/support/docview.wss?uid=swg21966637&aid=2]
Picture 2:
If you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.
[/support/docview.wss?uid=swg21966637&aid=3] [/support/docview.wss?uid=swg21966637&aid=3]
This behavior is also reported on the following product correction report (APAR): [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]
[https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]
https://www.ibm.com/support/entdocview.wss?uid=swg1PI41134 [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]
An IBM ID is required to access this material.
If needed, an IBM ID may be created at https://ibm.biz/ibm_web_id [https://ibm.biz/ibm_web_id]
RELATED INFORMATION
Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]
Need more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html] | Load SPSS 25 on a new computer I purchased SPSS 25 with a 12 month license on Jan 27. I loaded it and used it on my MacBook Pro. I now have a new MacBookPro. I was able to download the program but get a message that says I don't have a license. I do have the activation code. Can you please help me use this product on my new computer? Thanks! | Type (copy/paste) the following command:
sudo chown -R root:admin 20
2. Press Enter/Return.
3. Close Terminal.
4. Launch the License Authorization Wizard.
5. The warning message should no longer appear.
6. License your IBM SPSS Statistics product. |
TRAIN_Q012 | IBM Insufficient ulimit Value Causes Native OutOfMemory - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
An out of memory may be observed on a system running WebSphere Application Server on Linux or AIX that is due to ulimit restrictions on number of process/threads per user. Further investigation may reveal a "Failed to create a thread:" message within the generated javacore which would indicate a native out of memory issue has been encountered. The cause of the problem may be an insufficient ulimit setting. While this type of issue can occur on any level of Linux, or AIX, the issue is most likely to be seen in systems running multiple instances of WebSphere Application Server using one userid. The following will outline how to identify if a process ulimit is the culprit and what WebSphere Application Server Support recommends to fix the case.
SYMPTOM
An out of memory Dump Event such as:
"systhrow" (00040000) Detail "java/lang/OutOfMemoryError"
"Failed to create a thread: retVal -1073741830, errno 11" received
Note: This detailed message will appear only in javacores.
DIAGNOSING THE PROBLEM
When using WebSphere Application Server, ulimits can be set to fix or tune around a number of problems. For more on how to set a ulimit refer to the "Guidelines for setting ulimits [http://www-01.ibm.com/support/docview.wss?uid=swg21469413]" Technote which goes into detail on setting different ulimits on various operating systems and the difference between the soft and hard limit. This article is concerned particularly with the "-u" ulimit or "nproc" limit on Linux, the ulimit - r on AIX which affects the number of threads allowed for a single user process running WebSphere Application Server.
The AIX issue is less commonly seen as it limits then number of threads for a process but is seen in application servers with very large thread pools, This is becoming more common in 64bit addressing JVMs running complex applications. WebSphere Application support recommends setting the ulimit -r ulimited on AIX.
The nproc limit usually only counts processes on a server towards determining this number. Linux systems running WebSphere Application Server are a particular case. The nproc limit on Linux counts the number of threads within all processes that can exist for a given user. To determine the ulimit settings of a WebSphere Application Server process running on Linux refer to "How to determine the ulimit settings of a running WebSphere Application Server process on Linux [http://www-01.ibm.com/support/docview.wss?uid=swg21407889]".
User Limits (in bytes except for NOFILE and NPROC)
type soft limit hard limit RLIMIT_AS unlimited unlimited RLIMIT_CORE unlimited unlimited RLIMIT_CPU unlimited unlimited RLIMIT_DATA unlimited unlimited RLIMIT_FSIZE unlimited unlimited RLIMIT_LOCKS unlimited unlimited RLIMIT_MEMLOCK 65536 65536 RLIMIT_NOFILE 65536 65536 RLIMIT_NPROC 131072 131072
For most cases of older versions of Linux this value will be defaulted to around 2048. For out of the box Red Hat Enterprise Linux (RHEL) 6 the default value for nproc will be set to 1024. This low default setting for larger systems will not allow for enough threads in all processes.
WebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created.
By using this recommended value a sufficient number of threads in all processes will be allowed and will not be a limiting factor for the environment. Increasing the limit to the suggested value should have no negative impact. When the number of threads in all processes reaches the -u ulimit, an out of memory error message will be thrown. This issue can be avoided by increasing this limit. Be aware that if the number of threads/processes reaches the recommended number of 131072 or close, the issue may be deeper and continuing to increase the -u ulimit will only prove to be a temporary fix.
Once the ulimit is increased, the WebSphere Application Server will need to be restarted to use the
new setting. In the case of WebSphere Application Server ND, the nodeagent and the servers on the nodes will need to be restarted. | Are there any instructions for ulimit settings for WebSphere running on Linux? Are there any instructions for ulimit settings for WebSphere running on Linux? | WebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created. |
TRAIN_Q013 | IBM Applying TIP 2.2 fix packs directly to a TIP 2.1 installation - United States TIPL2; TIPL2INST; tivoli Integrated portal; feature pack TECHNOTE (FAQ)
QUESTION
Can Tivoli Integrated Portal 2.2 fix packs be applied directly to a TIP 2.1 installation?
ANSWER
In order to apply TIP 2.2 fix packs, the target TIP installation must already be at TIPCore 2.2.0 or newer. TIP 2.1 installations must be upgraded to TIP 2.2 using the TIP 2.2.0.1 feature pack. The TIP 2.2.0.1 feature pack can be acquired from IBM Fix Central [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=All&platform=All&function=all].
The following three items should be obtained from Fix Central:
* 2.2.0.1-TIV-TIP-<platform>-RP0001
* 2.2.0.1-TIV-TIP-FITSuit-RP0001vx
* 2201-fixpack-guide-PDF.pdf
To determine the installed TIPCore version, review the DE listIU command output. Details on the listIU command are included in the following technical note:
http://www-01.ibm.com/support/docview.wss?uid=swg21615989 [http://www-01.ibm.com/support/docview.wss?uid=swg21615989] | Can I apply a TIP 2.2 fix pack directly to a TIP 2.1 installation? Can I apply a TIP 2.2 fix pack directly to a TIP 2.1 installation? | In order to apply TIP 2.2 fix packs, the target TIP installation must already be at TIPCore 2.2.0 or newer. TIP 2.1 installations must be upgraded to TIP 2.2 using the TIP 2.2.0.1 feature pack. |
TRAIN_Q014 | IBM Problems installing NMA agent (N4 agent) on Linux x86-64 - United States ITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
The installation of NMA agent from package ITM for Virtual Environment V7.2.0.3 is failing with both remote or local installation on Linux x86-64.
SYMPTOM
1) The import of the whole bundle using command:
/opt/IBM/ITM/bin/tacmd addbundles -i <inst_media>/ITMfVE_Agents/unix
will fail with message:
Unable to find bundle prerequisite: ci 06.22.04.000 li6263
--
2) Even if you succeed in importing the bundle, the remote deploy of N4 agent on a Linux X86_64 fails because the installer recognizes the target node as a 64bit while the agent comes with a different architecture (li6263).
--
3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2.
The installer recognizes the target node as a 64bit platform and the agents are 32bit and so it does not show the expected list of agents.
CAUSE
The causes for the three scenarios depends on wrong prerequisite levels packaged into ITM for VE 7.2.0.3 for NMA agent, and on unexpected architecture recognized by the installer when trying to install the agent on the target node, if this one is a Linux x86-64.
RESOLVING THE PROBLEM
The issues should be corrected at Installer level, APAR IV84919 has been opened to fix them.
Anyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again.
Until then, you can bypass the issue with some manual steps.
---------------
1) If the import of agent bundle using command tacmd addbundles fails with message:
Unable to find bundle prerequisite: ci 06.22.04.000 li6263
this occurs because some agents, particularly N4 agent, have old prerequisites for shared components (ax, ui, gs,jr) that are not part of the ITM_for_VE bundle.
There is actually a workaround to correctly import the bundle in the depot, but it will not be of any help because remote installation of N4 agent will then fail due to the problem described in item number 2.
It can be anyway useful to know the workaround as it can be applied to other agents for which remote installation instead correctly works.
You must verify if the prerequisites mentioned in the error message are already present in your depot by using command tacmd viewdepot.
Beside of the one mentioned in the error message, you must be sure that also the other wanted prerequisites are already present in the depot.
N4 agent has the following prerequisites:
Product Code : n4
Deployable : True
Version : 062200000
Description : Monitoring Agent for Network Devices
Host Type : li6263
Host Version : li6263,lx8266
Prerequisites: ci:062204000 la:ipaddr05400 gs:074027000 jr:051201000
ui:062204000 ax:062204000
If all of them are already in the depot, then you can run the tamcd addbundles using flag "-n" (ignore prerequisites), this will allow to correctly import the agent bundle.
If you do not have the wanted prerequisite levels, you have two possible options:
a) retrieve and add them into depot from other ITM installation packages
b) modify the agent dsc files and change the level of the components required by the agent to match the level delivered with the bundle.
For example, ITM for Virtual Environment 7.2.0.3 delivers CI component at level 06.30.05.000, so if we consider N4 agent, you may need to change the file n4li6263.dsc in the rows:
<PrereqProdCode>ci</PrereqProdCode>
<PrereqVersion>
<Version>06</Version>
<Release>22</Release>
<Mod>04</Mod>
<Level>000</Level>
to
<PrereqProdCode>ci</PrereqProdCode>
<PrereqVersion>
<Version>06</Version>
<Release>30</Release>
<Mod>05</Mod>
<Level>000</Level>
The same for other components in case they are also missing from your depot.
The dsc files are into <installation_media>/ITMfVE_Agents/unix folder.
Repeat the tacmd addbundles command and it should now work fine.
As previously said, please consider that this scenario may occur also for agents different than N4, and the workaround is applicable also for them.
Of course the target dsc file name changes accordingly to the agent type and related architecture.
2) The above workaround can help in case the issue is only related to backleveled prerequisite packages.
Anyway, once you applied it, if the target node for the N4 agent is a Linux x86-64, you will anyway not be able to install it remotely.
The remote deploy of N4 agent on a Linux X86_64 fails because the installer recognizes the target node as a 64bit while the agent comes with a different architecture (li6263).
The quickest workaround in this case is to install the agent locally.
3) If you try to install the ITM for VE agents locally on a Linux x86_64, the usual installation procedure does not work for the same reason of point 2.
The installer recognizes the target node as a 64bit platform and the agents are 32bit.
So the installer menu will show no available agents to be installed.
You need to proceed as follow:
a) Run the local installation of N4 agent on target machine and proceed as usual when you are prompted with Installer initial questions.
b) Select Other operating systems when you are showed this panel
[/support/docview.wss?uid=swg21983839&aid=1] [/support/docview.wss?uid=swg21983839&aid=1]
c) Then select Linux Intel R2.6 R3.0 (32 bit)
[/support/docview.wss?uid=swg21983839&aid=2] [/support/docview.wss?uid=swg21983839&aid=2]
d) At this point you will see the list of agents that can be installed on the machine. Select the option for the n4 agent and installation will be completed successfully
[/support/docview.wss?uid=swg21983839&aid=3] [/support/docview.wss?uid=swg21983839&aid=3]
PRODUCT ALIAS/SYNONYM
IBM Tivoli Monitoring for Virtual Environments V7.2.0.3 | NMA agent installation failure
Hello, I'm trying to install the NMA agent from ITM for Virtual Environment package on a Linux x86-64. The preferred method would be remote install, but I'm not even able to perform tamcd addbundles as it complains about missing prerequisites.
If I try to install the agent locally on the Linux machine, the list of available agents does not include NMA agent at all.
Is there a solution to this problem? | The issues should be corrected at Installer level, APAR IV84919 has been opened to fix them.
Anyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again. |
TRAIN_Q015 | 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 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-2016-2126, CVE-2016-2125, CVE-2016-2123, CVE-2016-8866, CVE-2016-9556, CVE-2016-9559, and CVE-2016-9773.
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
PRODUCT ALIAS/SYNONYM
WMB HVE IIB HVE | Help with Action required for IIB V9 & WMB V8 Hypervisor Editions 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? | WebSphere Message Broker Hypervisor Edition |
TRAIN_Q016 | IBM Guidelines for setting ulimits (WebSphere Application Server) - United States ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server
SYMPTOM
Tuning ulimits correctly can overcome these errors:
* Too Many Open Files
* Could not lock User prefs. Unix Error Code 24.
* Truncated Core Dumps / Heap Dumps
RESOLVING THE PROBLEM
Is it possible to display the current ulimit settings? The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in.
How are ulimts set? Soft vs. Hard limits Soft limits are the current setting for a particular limit. They can be increased only to the current hard limit setting.
Hard limits are the maximum limit that can be configured. Any changes to these require root access.
Temporary Settings (for current session)
*
* ulimit -[H|S]limit_name limit_value
Temporary settings are set via the command line using the ulimit command. The limit_name must be present in the command (see the chart below). These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed.
This syntax can be used within shell scripts. Any processes spawned from these shell scripts will also have the temporary settings for the lifetime they are running.
By default, the soft limit will be changed (as changing the hard limit needs root access). Use -H (for hard limits) or -S (for soft limits) to change specific hard or soft limits.
NOTES:
On HP-UX, if you receive an error when setting a particular limit, and you have altered that particular hard limit, you may need to check and see if it had exceeded the kernel parameters. You can use kctune to check (and alter) these if necessary; check your HP-UX documentation for more information.
For Solaris, settings in the "/etc/system" configuration file also allow configuring of some kernel-wide limits.
Global Settings
[/support/docview.wss?uid=swg21469413&aid=1] Any changes to these global configuration limits files should be performed by your system administrator. Instructions on how to edit the files can be found on the manpage or in the commented section of the configuration file, as they can vary between versions of UNIX or Linux.
The format of the file, which differs slightly on versions of AIX and Linux, allows individual limits per users or groups, as well as set hard and soft limits. The limits defined in this configuration file are set globally.
Changes made to any limits file take effect after launching a new login shell (such as bash -l), or if the user logs out and logs back in to the system.
NOTES:
On Solaris and HP-UX, changes made to your shell's profile configuration (.profile or .login) should also take effect on the next login shell launched, or when your user logs back in using the specific shell.
For kernel-wide settings, which usually require a restart of the operating system to take effect, HP-UX has the kctune command, while Solaris has the /etc/system configuration file.
Specifics for each Operating System:
The most up-to-date information on the limits can be found in the man page for "ulimit".
AIX
Global settings are generally set in the file /etc/security/limits, although there may be different limit files for LPARs and WPARs.
Please note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or the limits file for further information.
Command Line limit_name * /etc/security/limits Description ulimit -c [value] core
core_hard Core file size in 512 byte blocks. ulimit -d [value]
(K bytes) data
data_hard Data segment size of processes in kilobytes. ulimit -f [value] fsize
fsize_hard File size limit in 512 byes blocks. ulimit -n [value] nofiles
nofiles_hard Max number of open files and/or sockets per process. ulimit -m [value]
(K bytes) rss
rss_hard The memory size of the process in kilobytes. ulimit -r [value] threads
threads_hard Max number of threads per process. ulimit -s [value]
(K bytes) stack
stack_hard The stack segment size in kilobytes. ulimit -t [value]
(seconds) cpu
cpu_hard Max per process CPU time (in seconds). ulimit -u [value] nproc
nproc_hard Specifies the limit of the number of processes per user. * Values are in 512 byte blocks unless otherwise specified, check your man page for further information
HP-UX
There is no global settings file on HP-UX. Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login).
There are similar kernel settings you can also set with kctune, such as "maxfiles_lim", but these kernel parameters do not normally need to be changed. Please refer to its man page for further information.
Please note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.
Command "ulimit" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks. ulimit -d [value] Data segment size of processes in 512 byte blocks. ulimit -f [value] File size limit in 512 byes blocks. ulimit -n [value] Max number of open files and/or sockets per process. ulimit -m [value] The memory size of the process in 512 byte blocks. ulimit -s [value] The stack segment size in 512 byte blocks. ulimit -t [value]
(seconds) Max per process CPU time (in seconds). * Values are in 512 byte blocks unless otherwise specified, check your man page for further information.
Linux
Global settings are set in the file /etc/security/limits.conf.
The format for setting each limit is as follows:
<domain> <type> <item> <value>
<domain> controls which users or groups will have these limits
<type> is either the string "soft" or "hard" limits.
The hyphen "-" can also be used which represents both soft and hard limits
<item> and <value> are shown in the table below. Most values can also use the string unlimited.
Please note that this table may not represent all ulimit items as they can vary between Linux variants. Consult the ulimit man page or the limits.conf file for further information.
Command Line limit_name /etc/security/limits.conf <item> Description ulimit -c [value] core Max core dump file size (KB) ulimit -d [value] data Max data size (KB) ulimit -f [value] fsize Max file size (KB) ulimit -l [value] memlock Max size of address space that can be locked into memory (KB) ulimit -n [value] nofile Max number of open files/sockets per process** ulimit -u [value] nproc Max number of processes for a single user ulimit -m [value] rss Max resident set size (KB) ulimit -s [value] stack The maximum stack size (KB) ulimit -t [value] cpu Max CPU time (minutes or seconds) ** There is a restriction that occurs on Red Hat Enterprise Linux that this value cannot be set to unlimited
Solaris
There is no global settings file specifically for ulimits on Solaris (however you can set kernel-wide settings in the /etc/system file). Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login).
Also depending on the shell used, the ulimit command is slightly different. See the man page for further information.
You can also set kernel wide settings for many of these ulimits in the /etc/system file.
For example, "set lim_fd_max = [value]" and "set rlim_fd_cur = [value]" are respectively the global hard and soft file descriptor limits. See the system OS's documentation for information on the /etc/system file.
Please note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.
Command Line limit_name *
(sh, ksh, bash) Command Line
(csh) Description ulimit -c [value] ulimit coredumpsize [value]
(K bytes) Core file size in 512 byte blocks. ulimit -d [value]
(K bytes) ulimit datasize [value]
(K bytes) Data segment size of processes in kilobytes. ulimit -f [value] ulimit filesize [value]
(K bytes) File size limit in 512 byes blocks. ulimit -n [value] ulimit descriptors [value] Max number of open files and/or sockets per process (plus 1) ulimit -s [value]
(K bytes) ulimit stacksize [value]
(K bytes) The stack segment size in kilobytes. ulimit -t [value]
(seconds) ulimit cputime [value]
(seconds) Max per process CPU time (in seconds). ulimit -v [value]
(K bytes) ulimit memorysize [value]
(K bytes) Maximum size of virtual memory (in kilobytes) * Values are in 512 byte blocks unless otherwise specified, check your man page for further information.
If I am experiencing Too Many Open Files (Unix Error Code 24), can I increase the number of file descriptors?
Yes you can through the ulimit -n [value] command. However these settings won't take effect until you restart your application server (and nodeagent), making sure you restart on the same command line where you executed "ulimit -n".
However, if you increase the value high enough and still run into these errors, you may want to check for a file descriptor leak (meaning a leak of opened files and/or sockets in your application code). The command lsof, offered on a variety of operating systems, can provide information on the quantity and types of file descriptors in use.
Further information can be found at this link: Too Many Open Files error message [http://www.ibm.com/support/docview.wss?uid=swg21067352]
On Linux, can I set the ulimit for the number of open files to unlimited? Certain versions of Red Hat Enterprise Linux do not allow this value to be set to unlimited due to a known issue in Red Hat Enterprise Linux 5 [https://bugzilla.redhat.com/show_bug.cgi?id=507159]. The limit must be set to an integer value no larger than 1048576. Other versions of Linux may not have this restriction. In the Information Center for WebSphere Application Server, there is a recommendation [http://www.ibm.com/support/knowledgecenter/en/SSAW57_8.0.0/com.ibm.websphere.nd.doc/info/ae/ae/tprf_tunelinux.html] of 8000.
If an attempt is made to set this ulimit to unlimited via the command line, an error will be displayed, and the old value will remain in place:
[root] # ulimit -n unlimited
bash: ulimit: open files: cannot modify limit: Operation not permitted
[/support/docview.wss?uid=swg21469413&aid=2] If you try to edit the /etc/security/limits.conf file to force unlimited for the number of open files, this will still be considered invalid and it will be reset to 0. This will prevent any new processes from spawning by that user or group. If this is the root user, the system will slowly die as new processes will be unable to generate. A recovery disc will be needed to reset the value.
On Red Hat Enterprise Linux 6, why are my settings for nproc (ulimit -u) not being honored. Red Hat Enterprise Linux 6 has introduced a configuration file, addressed in a bug report [https://bugzilla.redhat.com/show_bug.cgi?id=919793], ( /etc/security/limits.d/90-nproc.conf ) that overrides the nproc setting in the limits.conf. This file contains a line for nproc configured with a soft limit of 1024.
* soft nproc 1024
The rationale for this was to prevent fork bombs from occurring, To keep using the limits.conf for your nproc ulimit settings, you would need to comment this line out by making the first character on the line a hash/pound symbol.
#* soft nproc 1024
I am using an /etc/init.d script (or inittab) to start my application server and setting the global ulimit settings had no effect? The global settings for ulimit will not take effect if the init process starts the application server or nodeagent because it has yet to load the global settings. The global settings take effect once a login terminal session is started, or when a user logs in to the system, not when the init process spawns new processes based on init.d scripts. At startup, the operating system hasn't begun to load specific profiles up, even the root user. When you see individual services and processes starting, these are all child processes of the init process
This was previously documented for AIX 6.1 in the following Knowledge Center article entitled "telinit or init Command", under the Environments section. Here's the quoted section:
"A command that is executed by init from the /etc/inittab file uses init's ulimit values and not the default values as given in /etc/security/limits. The result is that a command that is successfully executed from the command line may not execute correctly when invoked by init. Any command that has specific ulimit requirements should include specific actions to set the ulimit values as required."
RELATED INFORMATION
Domino for Linux (see step 2) [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21377724]
AIX - IBM SDK 7.0 User Guide - Ulimits [http://publib.boulder.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.ibm.java.aix.70.doc%2Fuser%2Fulimits.html]
Linux - IBM SDK 7.0 User Guide - Ulimits [http://publib.boulder.ibm.com/infocenter/java7sdk/v7r0/index.jsp?topic=%2Fcom.ibm.java.lnx.70.doc%2Fuser%2Fulimits.html] | What can be done about "Too many open files" messages in the DASH systemOut? What can be done about "Too many open files" messages in the DASH systemOut log? | The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in. |
TRAIN_Q017 | IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States DSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION
ABSTRACT
IBM WebSphere Portal V6.1.0.5 and 6.1.5.2 hardware and software requirements on an AIX operating system. The hardware and software requirements reflect the versions of prerequisites and corequisites that were tested with WebSphere Portal V6.1.0.5 and 6.1.5.2.
CONTENT
TAB NAVIGATION
* AIX [http://www.ibm.com/support/docview.wss?uid=swg27019359]
* i5/OS [http://www.ibm.com/support/docview.wss?uid=swg27019362]
* Windows [http://www.ibm.com/support/docview.wss?uid=swg27019366]
IBM AIX
WebSphere Portal Server Version 6.1.0.5 and 6.1.5.2 (AIX)
This page describes the minimum product levels that need to be installed before opening a problem report with IBM WebSphere Portal Technical Support. The software versions and any maintenance levels listed on this page have been explicitly verified as working.
EARLIER LEVEL OF A LISTED SOFTWARE: Software versions at a lower level than those noted on this page are unsupported. LDAP software at an earlier level is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).
LATER LEVEL OF A LISTED SOFTWARE: Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are compatible with the tested versions. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).
UNLISTED SOFTWARE: Software not listed on this page at any level is unsupported. LDAP software not listed is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc_v6101/overview/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957] (#7012957 [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27012957]).
Operating systems
supported with 32-bit WebSphere Application Server and WebSphere Portal [/support/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system)
* AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system)
* AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (32-bit or 64-bit operating system)
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Operating systems
supported with 64-bit WebSphere Application Server and WebSphere Portal [/support/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system)
* AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system)
* AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (64-bit operating system)
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] AIX hardware requirements [/support/docview.wss?uid=swg27019359&aid=1] * IBM POWER family of processors
* Disk space requirements: * Minimum 2.5 GB free disk space for installation for WebSphere Portal
* Minimum 1.0 GB free disk space for installation for WebSphere Application Server
* Minimum 4 GB total disk space recommended for installation
* Physical memory: Under minimal load, WebSphere Portal can function with 2GB of RAM. However, 4GB is an optimal starting point for RAM in a production environment.
* CD-ROM drive
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Application Servers
The WebSphere-supplied Java SDK is required for both the run time and any remote Java clients. [/support/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server V7.0.0.11 with IBM SDK 1.6 SR12 (WebSphere Application Server product site) [http://www.ibm.com/software/webservers/appserv/was/]#1a#1b#1b
* WebSphere Application Server V6.1.0.31 with IBM SDK 1.5 SR7 (WebSphere Application Server product site) [http://www.ibm.com/software/webservers/appserv/was/]#1a#1b * Note: IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 6.1.x after that date with extended support, Java SDK V5 is no longer included
Refer to "Required WebSphere Interim Fixes for WebSphere Portal V6.1.0.5 and V6.1.5.2 [http://www.ibm.com/support/docview.wss?uid=swg24027476]" for the complete list of fixes required for WebSphere Application Server. [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Optional WebSphere Servers [/support/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server SCA feature pack 1.0.1.5
* WebSphere Application Server XML feature pack 1.0.0.5
* WebSphere Process Server V6.2.0.2*, 6.1.2.3, and 6.1.0.4 (all via Client Install option only with WAS 6.1x releases) *Refer to technote #1398123 for Process Server V6.2 Client installation [http://www.ibm.com/support/docview.wss?uid=swg21398123]
* WebSphere Virtual Enterprise (formerly "Extended Deployment") V6.1.1.1, 6.1.0.5 (WebSphere Extended Deployment product site [http://www.ibm.com/software/webservers/appserv/extend/])
JavaScript Library [/support/docview.wss?uid=swg27019359&aid=1] * Dojo V1.3.2 or 1.1.1
To take advantage of the support for Microsoft Internet Explorer V8.0 or to use the new features in 6.1.5.2 such as Mashups integration and the Page Builder Theme, you will need to use Dojo V1.3.2. Refer to the topic "Using a different Dojo version [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1/topic/com.ibm.wp.ent.doc_v615/admin/epc_use_prior_dojo.html]" for more information. [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Databases
[/support/docview.wss?uid=swg27019359&aid=1] * Derby V10.1 and 10.3
* IBM DB2 Universal Database (DB2 product site) [http://www.ibm.com/software/data/db2/9/] (also supports High Availability Disaster Recovery (HADR) Feature) * V9.7 FP1 for Linux, Unix, Windows
* V9.5 for Linux, Unix, Windows: Enterprise Server Edition 9.5 FP5, Express Edition 9.5 FP5, Workgroup Server Edition 9.5 FP5 (viper 2) (including HADR)
* V9.1 for Linux, Unix, Windows: Enterprise Server Edition 9.1 FP9, Express Edition 9.1 FP9, Workgroup Server Edition 9.1 FP9 (including HADR)
* V8.1 for Linux, Unix, Windows: Enterprise Server Edition 8.1 FP16, Express Edition 8.1 FP16, Workgroup Server Edition 8.1 FP16 (including HADR)
* IBM DB2 for z/OS V9.1 and V8.1, PUT level 0901 or later maintenance (DB2 for z/OS product site) [http://www.ibm.com/software/data/db2/zos/]#2 (also supports High Availability Disaster Recovery (HADR) Feature)
* WebSphere Information Integrator V8.2 FP4
* Oracle (Oracle Database product site) [http://www.oracle.com/database/index.html] (Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover#3a) * Standard/Enterprise V9.2.0.8, 10.1.0.5 Patch 4, 10.2.0.4 and 10.2.0.5 (patchset 8202632) (including RAC) (Supports Automatic Storage Management (ASM) Feature)
* Oracle 11gR2 V11.2.0.1 (including RAC)
* Oracle 11gR1 V11.1.0.7 (including RAC)
* Microsoft SQL Server (Microsoft product site) [http://www.microsoft.com] * Enterprise Edition 2008 SP1 [http://www.microsoft.com]
* Enterprise Edition 2005 SP3
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Java Database Connectivity (JDBC) Drivers [/support/docview.wss?uid=swg27019359&aid=1] * DataDirect Connect JDBC 4.0 (type 4) (DataDirect Connect JDBC product site [http://www.datadirect.com/products/jdbc/index.ssp])
* DB2 Driver for JDBC and SQLJ 3.1 (type 2/4)
* JCC JDBC driver level 3.58.90 or above to connect to DB2 for z/OS Note: Use the JDBC drivers provided with DB2 LUW V9.7 FP2 when the Portal is not also running on z/OS
* Derby embedded JDBC Driver
* Microsoft SQL Server JDBC Driver 1.2 or 2.0 (Microsoft SQL Server JDBC Driver site [http://msdn.microsoft.com/en-us/data/aa937724.aspx])
* Oracle 9i or 10g or 11g JDBC Driver Thin (type 4) (Oracle JDBC product site [http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html])
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Web servers
[/support/docview.wss?uid=swg27019359&aid=1] * Apache HTTP Server V2.0.5.9 (Apache Server product site) [http://httpd.apache.org/] (Apache Server 2.0.5.9 includes CERT Advisory CA-2002-17)
* Apache HTTP Server V2.2 (Apache Server product site) [http://httpd.apache.org/] (Apache 2.2.x is supported with WebSphere Application Server 7.0.#4a)#4a
* IBM HTTP Server for WAS V7.0 and 6.1 (IBM HTTP Server product site) (HTTP Server 7.0 is supported with WebSphere Application Server 7.0 only) [http://www.ibm.com/software/webservers/httpservers/]
* IBM HTTP Server for iSeries V7R1, V6R1 and V5R4 (IBM HTTP Server product site) [http://www-03.ibm.com/systems/i/software/http/index.html](HTTP Server for i5/OS is provided natively on System i5 and is not bundled with or installed by WebSphere Portal. For V5R4, supported group PTF is SF99114 level 13; for V6R1, supported group PTF is SF99115 level 1. For V5R4, the license program number is 5722DG1; for V6R1, the license program number is 5761DG1. Issue the GO LICPGM to display all the installed licensed programs. For WebSphere Application 6.1.0.21 on V6R1M0, apply SI35071. For WebSphere Application 7.0.0.1 on V6R1M0, apply SI35078)
* Microsoft Internet Information Services (IIS) V7.5 or 7.0 (only for WAS 7 environments) and 6.0 (Microsoft product site) [http://www.microsoft.com]
* IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http://www.lotus.com/products/product4.nsf/wdocs/dominohomepage]#4d(To use Lotus Domino Version 7.0 with WebSphere Application Server 6.1, you must install the Web Server plug-in for Lotus Domino Server Version 6 which is a part of the Web Server plug-in for WebSphere Application Server 6.1)
* Sun Java System Web Server 7 Update 8 or 6.1 SP12 (Sun product site) [http://www.sun.com/products/]
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Web browsers
(required for administration/configuration, sample program execution and launch pad. There is no restriction nor certification of Web browsers on clients that connect the server to display content) [/support/docview.wss?uid=swg27019359&aid=1] * 6.1.0.5: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http://www.microsoft.com]
* Firefox V3.6, 3.5, 3.0, 2.0, 1.5.0.7 (Firefox product site) [http://www.mozilla.org/]
* Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/]
* Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/]
Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http://www.ibm.com/support/docview.wss?uid=swg21320077]
* Opera 9.52 and higher [http://www.ibm.com/support/docview.wss?uid=swg21320077](Opera product site) [http://www.opera.com/products/]
Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http://www.ibm.com/support/docview.wss?uid=swg21318444]
*
* 6.1.5.2: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http://www.microsoft.com]
PageBuilder, Mashup Integration and Wiki/Blogs in V6.1.5.2 are not supported or functional when using Microsoft Internet Explorer V6.0.#6f
* Firefox V3.6, 3.5, 3.0 (Firefox product site) [http://www.mozilla.org/]
* Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/]
* Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/]
Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http://www.ibm.com/support/docview.wss?uid=swg21320077]#6a#6e
* Opera 9.52 and higher (Opera product site) [http://www.opera.com/products/]
Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http://www.ibm.com/support/docview.wss?uid=swg21318444]#6b
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] LDAP servers
[/support/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http://www.lotus.com/products/product4.nsf/wdocs/dominohomepage] For 7.0.2 and 7.0.1: Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup. Turkish users should use version 7.0.3 or later.#7a
* IBM Tivoli Directory Server 6.2, 6.1 and 6.0 (IBM Tivoli Directory Server product site) [http://www.ibm.com/software/tivoli/products/directory-server/] Add the fix for APAR IO02714 on applicable releases, available at IBM Support.#7b
* IBM z/OS Security Server 1.7 and 1.6 (IBM z/OS Security Server product site) [http://www.ibm.com/systems/z/advantages/security/index.html]
* IBM z/OS.e Security Server 1.7 and 1.6 (IBM z/OS Security Server product site)
* Novell eDirectory 8.8 or 8.7.3 (Novell eDirectory product site) [http://www.novell.com/products/edirectory/]
* Sun Java System Directory Server 7, 6.3, 6.1, and 6 (Sun product site) [http://www.sun.com/products/]
* Microsoft Active Directory 2008, including Lightweight Directory Server (AD LDS, previously referred to as "Application Mode" or ADAM)
* Windows Active Directory 2000 and 2003 including Application Mode
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Software for collaboration - Domino and Extended Products (optional) [/support/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1, 6.5.6 (IBM Lotus product site) [http://www.ibm.com/developerworks] Domino V8.5.2 also needs the fix applied for SPR DPOS895USS, contact Domino Technical Support for the fix.
* IBM Lotus Domino Document Manager V7 and 6.5.1
* IBM Lotus Sametime V8.5, 8.0.2, 8.0, 7.5.1 and 7.5 (IBM Lotus product site) [http://www.ibm.com/developerworks]
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Software for content management (optional) [/support/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Web Content Management V6.1.0.5 or 6.1.5.2 (IBM Lotus Web Content Management product site) [http://www.ibm.com/software/lotus/products/webcontentmanagement/]
* Ephox EditLive IBM LWCM OEM version 3.4.1.41 (which includes EditLive version 7.0.1.46.) (Ephox EditLive product site [http://www.ephox.com])
* IBM Lotus Quickr V8.5, 8.1.1 (IBM Lotus product site) [http://www.ibm.com/developerworks]
* 6.1.5.2: IBM Lotus FileNet P8 V4.5 (IBM Lotus product site) [http://www.ibm.com/developerworks]
* 6.1.5.2: IBM Content Manager V8.4 (IBM Content Manager product site) [http://www.ibm.com/software/data/cm/cmgr/]
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Supported Java Runtime Environments - Web Content Management authoring portlet [/support/docview.wss?uid=swg27019359&aid=1] * Java Runtime Environments (requires one) V1.6.x or 1.5.x (Sun product site) [http://www.sun.com/products/]
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] External Security software (optional) [/support/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli Access Manager V6.1 and 6.0 for trust association interceptor and enhanced trust association interceptor (support for Subject creation) (Tivoli Access Manager product site) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal.
* IBM Tivoli Access Manager V6.0 for Java Authorization Contract for Containers (JACC) (Tivoli Access Manager product site) [http://www.ibm.com/software/tivoli/products/access-mgr-e-bus/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal
* Computer Associates SiteMinder V6.0
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Software for portlet development [/support/docview.wss?uid=swg27019359&aid=1] * IBM Rational Application Developer V7.5 and 7.0.6 (plugin for UTE)
* IBM Portlet Factory V6.1.5, 6.1
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=2] [/support/docview.wss?uid=swg27019359&aid=3] [/support/docview.wss?uid=swg27019359&aid=3] Software for license management [/support/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli License Compliance Manager V2.3
[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=4] [/support/docview.wss?uid=swg27019359&aid=5] [/support/docview.wss?uid=swg27019359&aid=5]
Related information
[http://d02was006.southbury.ibm.com/support/dcf/preview.wss?host=d02dbs88.southbury.ibm.com&db=support/swg/swgdocs.nsf&unid=2D60E6429AA6F54285256FB00046AC9D&taxOC=SSCVS22&MD=2005/02/25%2008:02:00&sid=]Detailed system requirements [http://www.ibm.com/support/docview.wss?rs=688&uid=swg27007791]
WebSphere Portal Information Centers and more [http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html]
Support Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html]
See disclaimer.
Top of page
Disclaimer
IBM reserves the right to change specifications and other product information without prior notice. This publication could include technical inaccuracies or typographical errors. References herein to IBM products and services do not imply that IBM intends to make them available in other countries. IBM PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 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.
Top of page
ORIGINAL PUBLICATION DATE
2009/9/1 | Does Portal 6.1.x support Oracle 12c?
We are running Portal Server v6.1.0.6 and I need to know what the newest version of Oracle that is supported with the WPS 6.1.0.6?
Specifically, if Oracle 12c is not supported, what version of Oracle 11g is? | Oracle 11gR2 V11.2.0.1 (including RAC) |
TRAIN_Q018 | IBM Deletion of virtual portal fails with transaction timeout - United States virtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)
PROBLEM
Attempt to delete virtual portal via Virtual Portal Manager portlet fails with error:
EJPAH4000E: Failed to delete virtual portal
Attempts to delete the virtual portal using the ConfigEngine task "delete-virtual-portal" may fail as well.
CAUSE
With the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded:
* the total and/or maximum transaction lifetime timeout value(s) for the server
* the WCM component's transaction timeout
DIAGNOSING THE PROBLEM
SystemOut.log may show the following:
Example #1:
[9/10/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.
[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction
com.ibm.icm.ci.CDMTransactionException
at com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)
at com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)
at com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)
at com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)
....
Caused by: javax.transaction.RollbackException
at com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)
....
[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.
com.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.
at com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)
....
Caused by: javax.transaction.RollbackException
at com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)
....
Example #2:
[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.
[datestamp] 000000f4 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was:
java.net.SocketInputStream.socketRead0(Native Method)
java.net.SocketInputStream.read(SocketInputStream.java:150)
java.net.SocketInputStream.read(SocketInputStream.java:121)
com.ibm.db2.jcc.t4.x.b(x.java:208)
com.ibm.db2.jcc.t4.x.c(x.java:360)
com.ibm.db2.jcc.t4.x.c(x.java:473)
com.ibm.db2.jcc.t4.x.v(x.java:1241)
com.ibm.db2.jcc.t4.ab.a(ab.java:61)
com.ibm.db2.jcc.t4.p.a(p.java:50)
com.ibm.db2.jcc.t4.rb.b(rb.java:220)
com.ibm.db2.jcc.am.po.qc(po.java:3498)
com.ibm.db2.jcc.am.po.b(po.java:4461)
com.ibm.db2.jcc.am.po.ic(po.java:799)
com.ibm.db2.jcc.am.po.executeUpdate(po.java:777)
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)
com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)
com.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)
com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)
com.ibm.icm.ci.workspace.impl.PDeleteWorkspaceImpl.deleteWorkspace(PDeleteWorkspaceImpl.java:84) com.ibm.icm.ci.workspace.impl.WorkspaceService.deleteWorkspace(WorkspaceService.java:270) com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:808)
com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)
com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)
com.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)
com.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)
com.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)
....
RESOLVING THE PROBLEM
1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below.
2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider:
Name: wcm.transaction.timeout
Value: 600 (for example)
Note: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.
RELATED INFORMATION
#Transaction settings [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html]
PI04872 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI04872]
Setting Resource Environment Provider custom properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8] | Why does the transaction time out when I try to delete a virtual portal? Transaction timeout occurs when I try to delete a virtual portal. Managed pages is enabled. Why? | With the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded:
* the total and/or maximum transaction lifetime timeout value(s) for the server
* the WCM component's transaction timeout |
TRAIN_Q019 | IBM FAQ for IBM SPSS Statistics Subscription - United States TECHNOTE (FAQ)
QUESTION
FAQ for IBM SPSS Statistics Subscription
ANSWER
Q. How to I cancel the auto-renewal of my IBM SPSS Statistics Subscription?
A. Auto-renewal will be available a few days after your subscription starts. Please check back after a few days to change your subscription level. Changes to auto-renewal will take affect at the end of the month long subscription period.
Q. I have installed the Subscription and when I attempt to login all I get is a big white screen. How do I get my subscription started?
A. The most likely cause of this issue is installation of the 32bit IBM SPSS Statistics Subscription software on a 64bit machine. To fix the issue, please uninstall the 32bit and download and install the 64bit application from your Products & Services window on IBM.com. If you find that this does not resolve your issue, you have a new issue. Please open a Service Request using the Client Support Portal: http://ibm.biz/IBMClientSuccessPortal [http://ibm.biz/IBMClientSuccessPortal]. | i cannot enter SPSS statistics trial program
I've downloaded the 14-days trial of SPSS subscription for 32bit, windows. After opening the program I'm asked to login and after entering my username and password a blank page comes up. And there is no way to proceed from here. I already saw previous answers about SPSS trial Login error, and there is a link(https://ibm.box.com/s/huaafbjzabkyblh47n7g4l0o4gxp4zdy) to download the zip file of 'jxbrowser'. But i cannot enter the link, and the webpage says "probably the address was changed or deleted."
i'm using Windows 7(32bit), and just want to know how can i resolve it.
| The most likely cause of this issue is installation of the 32bit IBM SPSS Statistics Subscription software on a 64bit machine. To fix the issue, please uninstall the 32bit and download and install the 64bit application from your Products & Services window on IBM.com. If you find that this does not resolve your issue, you have a new issue. Please open a Service Request using the Client Support Portal: http://ibm.biz/IBMClientSuccessPortal |
TRAIN_Q020 | IBM Rational Host Access Transformation Services 9.0 - United States service release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES
ABSTRACT
IBM Rational Host Access Transformation Services 9.0 has been made generally available and contains fixes to version 9.0.
DOWNLOAD DESCRIPTION
Table of Contents Sections Description * What's new
This section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. * Impact assessment
This section provides information related to the impact of this release to allow you to assess how your environment may be affected. * Prerequisites
This section provides important information to review prior to the installation of this release. * Download package
This section provides the direct link to obtain the download package for installation in your environment. * Installation instructions
This section provides the installation instructions necessary to apply this release into your environment. * Known problems
This section contains a link to the known problems (open defects) identified at the time of this release. Supporting Documentation Document Description * Detailed System Requirements [http://www.ibm.com/support/docview.wss?uid=swg27011794]
Click to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions. * Information Center [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/index.jsp]
The information center provides you with user assistance for the product. You can view, browse, and search online information related to the product. You can also visit IBM Product information [http://www.ibm.com/support/publications/us/library/index.shtml#letter_R] page to browse for additional information centers. * Fix List [http://www.ibm.com/support/docview.wss?uid=swg27027491]
Click to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family. PREREQUISITES
IBM Installation Manager, Version 1.6.3.1 [http://www.ibm.com/support/docview.wss?uid=swg27025142] or later is required to install HATS 9.0.
INSTALLATION INSTRUCTIONS
For installation instructions, see Installing HATS [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/topic/com.ibm.hats.doc/doc/gsinstal.htm] in the Rational Host Access Transformation Services (HATS) V9.0 Information Center.
DOWNLOAD PACKAGE
Download options Access type Description Passport Advantage [https://www.ibm.com/software/howtobuy/softwareandservices/passportadvantage] Passport Advantage and Passport Advantage Express clients are required to sign in to download the software package. IBM OEM software [https://www.ibm.com/software/howtobuy/softwareandservices/oem] IBM Software Group OEM offerings are designed for partners who develop and sell business solutions with embedded or bundled IBM middleware software. Clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners must sign in to download the software package. HOW CRITICAL IS THIS FIX?
Impact Assessment Impact Description Recommended This release is a service release of Rational Host Access Transformation Services 9.0. It contains new features as well as fixes for client-reported and internally found defects. PROBLEMS SOLVED
Click the Fix List link in the table of contents above to review a list of the problems solved in this release.
KNOWN SIDE EFFECTS
The following defects were not resolved in this release.
APAR Description IC94113 [http://www.ibm.com/support/docview.wss?uid=swg1IC94113] DBCS characters behind DDS window border are garbled. IC94307 [http://www.ibm.com/support/docview.wss?uid=swg1IC94307] Rich client: Part of DBCS fixed character is damaged.
For up-to-date information about known issues and workarounds, see Rational Host Access Transformation Service 9.0 - Known issues and workarounds [http://www.ibm.com/support/docview.wss?uid=swg27038663].
CHANGE HISTORY
For what's new in HATS 9.0, see the Rational Host Access Transformation Services (HATS) V9.0 Information Center [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/index.jsp].
Back to top
TECHNICAL SUPPORT
TAB NAVIGATION
* General Support Information- selected tab,
* Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,
IBM Rational Software Support Communities
* Visit the IBM Support Portal [http://www.ibm.com/support/entry/portal/Overview/Software/Rational/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.
* Visit developerWorks [http://www.ibm.com/developerworks/rational/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http://www.ibm.com/developerworks/rfe/].
* Visit the Jazz Community [http://jazz.net/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress.
HELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:
Before you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions:
* What software versions were you running when the problem occurred?
* Do you have logs, traces, or messages that are related to the problem?
* Can you reproduce the problem? If so, what steps do you take to reproduce it?
* Is there a workaround for the problem? If so, be prepared to describe the workaround.
If you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http://www.ibm.com/software/support/exchangeinfo.html].
Follow IBM Rational Client Support on Twitter [http://twitter.com/rationalsupport] | Facebook [http://facebook.com/rationalsupport] | YouTube [http://www.youtube.com/ibmrationalsupport] | devWorks Blog [https://www.ibm.com/developerworks/mydeveloperworks/blogs/nfrsblog/?lang=en]
Back to top
[/support/docview.wss?uid=swg24035040&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24035040&aid=2]Problems (APARS) fixed
IC87102, IC87488, IC87959, IC88940, IC88981, IC89933, IC91191, IC91370, IC91420, IC92195 | HATS Plugin Download
Hi
I have RDZ 9.0 and want to install the HATS plugin.
I've downloaded from this link:
http://www.ibm.com/developerworks/downloads/ws/whats/
HATS 9.0.0.0 but it won't install because RDZ itself is not enough and it sais I need one of the following:
IBM Rational Application Developer for WebSphere Software
IBM Rational Software Architect for WebSphere Software
IBM Rational Developer for i for SOA Construction
IBM Rational Business Developer
IBM Integration Developer
which I don't have.
Where can I download the HATS version that is compatible with RDZ 9.0 and doesn't need anything else? | For installation instructions, see Installing HATS [http://pic.dhe.ibm.com/infocenter/hatshelp/v90/topic/com.ibm.hats.doc/doc/gsinstal.htm] in the Rational Host Access Transformation Services (HATS) V9.0 Information Center. |
TRAIN_Q024 | IBM SPSS Student Version and Graduate Pack Resources - United States SPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)
QUESTION
Where do I get support for IBM SPSS Student Version or Graduate Pack software?
ANSWER
Step 1:
For installation & licensing issues on Student version and Graduate pack, contact your vendor.
* Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ]
* On the Hub [http://onthehub.com/]
* StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx]
* JourneyEd [https://www.journeyed.com/contact]
* thinkEDU [https://thinkedu.desk.com/]
* Studica [http://www.studica.com/technical-support]
Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version | How do I transfer my SPSS 24 license key to a new computer? I need to transfer my SPSS 24 license key to a new computer. I was able to download IBM® SPSS® Statistics Standard GradPack 24 for Windows (12-Mo Rental) onto the new computer, but every time I put in the activation code, I am met with this error message:
Authorization failed.: You are not allowed to generate any more new licenses.
End Of Transaction.
No additional authorizations are permitted on this code.
What should I do? | For installation & licensing issues on Student version and Graduate pack, contact your vendor. |
TRAIN_Q026 | IBM Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 - United States DOWNLOADABLE FILES
ABSTRACT
This is an Interim Fix for IBM Tivoli Monitoring for Virtual Environments: VMware VI 7.2 Fix Pack 2 reports
DOWNLOAD DESCRIPTION
(C) Copyright International Business Machines Corporation 2015.
All rights reserved.
Component: IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI
Agent TCR Reports, Version 7.2 Fix Pack 2
Component ID: 5724L92AG
Interim Fix: 0001, 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001
Date: January 23, 2015
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
------------------
The following problems are addressed by this fix.
2.1 APARs
---------------
None.
2.2 Defects
-----------
Defect: 210286
Abstract: Update model for VM PARTITION
Additional information: For "Free_Space" and "Used_Space" attributes, the
default aggregation is defined not as AVG but as SUM. It usually
works as expected but if there were two entries which have same
"Timestamp", the "VM_PARTITION" attribute group's data is shown
with doubled values.
Defect: 212729
Abstract: Drill through feature is not working in VE 7.2 FP2 reports
Additional information: A few VMware VI reports are showing the following
message, when we try drill through by clicking on report chart:
RSV-CM-0005 Content Manager did not return an object for the
requested search path.
Defect: 212776
Abstract: Datacenter parameter/prompt is missing in a few VM reports
Additional information: The Datacenter parameter/prompt is missing in the
following VMware VI reports: VM Heat Chart, Bottom N VMs by
Resource Pool and Top N VMs By Resource Pool.
Defect: 212851
Abstract: Place Date range parameter after the Resource prompts
Additional information: A few VMware VI reports contain time selection over
resource selection. Therefore to make uniformity across the reports,
place Date range parameter after the resource prompts (like Data
Center and Cluster).
Defect: 212924
Abstract: Unsorted resources e.g.Cluster on parameter selection page
Additional information: Most of the VMware VI reports sometimes display
unsorted resources (viz. Data Center, Cluster, Host Servers, VMs
etc.) on parameter selection (aka prompt) page.
Defect: 212925
Abstract: Incorrect caption/label for Host Server resource parameter
Additional information: Incorrect caption/label for the resource parameter
e.g. In Network usage by VMs report, the "Host Server(s)" drop
down list title needs to be corrected as "Host Server" as user
can select only one host in this report.
2.3 Enhancements
------------------
Feature: 210245
Abstract: Enhance model to add SAMPLES.
Additional information: Add SAMPLES query item/column for each summarized
attribute group view (viz. Hourly, Daily, Weekly and Monthly)
in existing VMware VI Agent reports data model.
Feature: 213018
Abstract: RFE 60331: Require a new report for Cluster Utilization Details
Additional information: Require a new cluster level report like the Host
Server Utilization Details report, which is useful and included the
actual data points from the graph at the bottom of the report.
Defect: 213084
Abstract: Provide a choice to select date range or start & end week
Additional information: Provide a parameter choice (aka date filter option)
to either select date range or start and end week of the year in
the following VMware VI reports: Cluster Weekly Comparison and
Host Servers Weekly Comparison.
2.4 Superseded fixes
---------------------
None.
2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
None.
3.0 Architecture and prerequisites
----------------------------------
This fix is supported on all operating systems listed in the IBM Tivoli
Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning
User's Guide, version 7.2 Fix Pack 2. See chapter 9 for information on the Tivoli
Common Reporting.
The User's Guide is here:
http://www.ibm.com/support/knowledgecenter/SS9U76_7.2.0.2/com.ibm.tivoli.itmvs.doc_7.2.0.2/vedrcp72fp2_user.pdf [http://www.ibm.com/support/knowledgecenter/SS9U76_7.2.0.2/com.ibm.tivoli.itmvs.doc_7.2.0.2/vedrcp72fp2_user.pdf]
Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]
3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is defined in Chapter 9 of the IBM Tivoli
Monitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning
User's Guide, version 7.2 Fix Pack 2.
4.0 Image directory content
---------------------------
This fix image contains the following files:
- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.README - This README file
- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip - Fix archive .zip format.
The fix archive file contains the following directories and files,
which is the same as the format found in the reports directory
of the IBM Tivoli Monitoring for Virtual Environments V7.2 Fix Pack 2
Dashboards, Capacity Planner and Reports (TMVE), Multilingual media
as found on Passport Advantage:
- gui
- lib
- model
- reports
- scripts
- setup_aix.bin
- setup_hpux.bin
- setup_linux.bin
- setup_solaris.bin
- setup_windows.exe
- silent_installer.properties
- tcr_install.properties
Note that this Interim Fix is a complete replacement of these
files.
5.0 Installation instructions
-----------------------------
This fix can be installed over an existing installation or as
a new install. Expand the archive file,
7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip, and copy the files in any
location on the same computer where the Tivoli Common Reporting
server is installed.
Use the following procedure to import reports that are bundled by using
the report installer:
1. From the \7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 directory on the product file, run the
command appropriate for your operating system:
• setup_aix.bin (for AIX)
• setup_hpux.bin (for HP-UX)
• setup_linux.bin (for Linux)
• setup_solaris.bin (for Solaris)
• setup_windows.exe (for Windows)
The installer window opens.
2. Choose your language and click OK.
3. On the Welcome page click Next.
4. Specify the Tivoli Common Reporting installation directory, such as
<JazzSM_Home>/reporting if you are using Tivoli Common Reporting 3.1 or
later with Jazz for Service Management and <TIP_Home>/TCRComponents if
you are using Tivoli Common Reporting 2.1.1 with Tivoli Integrated Portal.
You can use the default folder or use the Browse button to provide the
path. Click Next.
5. Choose the reports you want to install. Click Next.
6. Enter the Tivoli Common Reporting user name and password. Click Next.
7. For each data source and data script, enter the data source configuration
information. Enter the following details for the selected cognos reports, and
then click Next:
• In the Enter the database username field, enter the administrator user name.
• In the Enter the user password field, enter the password.
• In the Choose the database type list, select the database type.
• In the Enter the database name field, enter the warehouse database name. For DB2
or Oracle, enter the database name. For MS SQL, enter the ODBC Data Source Name.
8. On the Data Script runDbScript Configuration page:
a. Click the JDBC User Credentials tab, and enter the Tivoli Data Warehouse database
user name and password to be used during the installation. Check the box to skip
defining the data source now.
b. Click the JDBC Database Credentials tab, and select database type. Edit the JDBC URL,
JDBC driver file names, and JDBC driver class for the selected database type and then
click Next.
• For DB2 database, required driver files are db2jcc.jar and db2jcc_license_cu.jar
(Note: JDBC credentials must have db2admin privileges.)
• For Oracle database, required driver file is oraclethin.jar
• For MS SQL Server database, required driver file is sqljdbc.jar
9. On the Report Installer Summary page, verify the reports to be installed, click Install,
and wait for the installer to finish.
10. The post-installation report is displayed. Check if the installation was successfully
finished and click Done.
Results:
Agent reports are now installed on your Tivoli Common Reporting server.
Alternatively, see Topic: Importing reports by using the report installer
in Chapter 17 of the IBM Tivoli Monitoring Administrator's Guide,
version 6.3 Fix Pack 2 for install instructions.
The Administrator's Guide is here:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/itm63fp2_admin.pdf [http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/itm63fp2_admin.pdf]
6.0 Additional installation information
---------------------------------------
None
7.0 Known problems and workarounds
----------------------------------
None
8.0 Additional product information
----------------------------------
None
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.
PREREQUISITES
IBM Tivoli Monitoring for Virtual Environments: VMware VI Agent, version 7.2 Fix Pack 2
INSTALLATION INSTRUCTIONS
Please refer to the full README contained in the Download Description section above for general installation instructions.
DOWNLOAD PACKAGE
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 23 Jan 2015 English 53552332 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/Tivoli&product=ibm/Tivoli/Tivoli+Monitoring+for+Virtual+Servers&release=All&platform=All&function=fixId&fixids=7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001&includeSupersedes=0] [ ] | Where can I find the ITM VMware VI Agent Reports package for v 7.2?
I am only able to find ver 6x reports. My initial search for the v7.2 reports took me to this link but it does not have v 7.2:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W22ac5f3ebabf_4ff4_bd55_1a897c9a443e/page/Report%20Catalog
| Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 23 Jan 2015 English 53552332 FC |
TRAIN_Q027 | IBM JDBC driver or database insufficiencies cause administration portlets to fail. - United States RT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING)
PROBLEM
You attempt to create a new page via the Manage Pages portlet or add a portlet to a page via the Edit Layout portlet and encounter an error.
SYMPTOM
SystemOut.log contains:
... DefaultTransa E Message: Could not save object in repository.,
Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager
com.ibm.workplace.wcm.services.repository.RepositoryException:
Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager
...
Caused by: com.ibm.icm.da.DBAccessException:
java.sql.SQLFeatureNotSupportedException:DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream
at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857)
The client browser displays:
EJPAS0017E ... Message: Could not save object in repository.,
Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a
function createItems of PLS data ...
or:
EJPAE0015E: Failed to add new portlets.
...
EJPEC0002E: The transaction has been set to rollback state...
CAUSE
The JDBC driver does not meet WebSphere Portal v8's prerequisites.
DIAGNOSING THE PROBLEM
Check SystemOut.log for the database server version and JDBC driver version:
DSRA8204I: Database product version : ...
InternalGener I DSRA8205I: JDBC driver name : ...
InternalGener I DSRA8206I: JDBC driver version : ...
Compare these to WebSphere Portal v8's prerequisites. Refer to the WebSphere Portal V8.0 detailed system requirements link below.
RESOLVING THE PROBLEM
If the database server and/or JDBC driver do not meet WebSphere Portal v8's prerequisites, upgrade or downgrade the component(s) to the appropriate supported level(s) and restart the Portal server(s).
If upgrading the JDBC driver requires replacing the .jar with another differently named .jar, other components in the system that referenced the older .jar may be affected. Pay special consideration to:
WAS Integrated Solutions Console > Environment > WebSphere Variables
VMM_JDBC_CLASSPATH
ORACLE_JDBC_DRIVER_PATH
These are stored in: <profile>/config/cells/<cell name>/variables.xml
Other WebSphere variables may also reference the older .jar, or these same variables may be set in different scopes, so check other variables and variables.xml files as well, such as: <profile>/config/cells/<cell name>/nodes/<node name>/variables.xml
RELATED INFORMATION
WebSphere Portal V8.0 detailed system requirements [http://www-01.ibm.com/support/docview.wss?uid=swg27007791] | Why are we not able to create new pages using the Manage Pages Portlet? We are using Portal 8.5 on Windows,
From WebSphere Portal Administration console. we go to ‘Manage Pages’- > Select ‘Content root’ item from table -> ‘New Page’ button, after entering the new page details and hitting OK we receive following error:
EJPAS0017E: Unable to create PageName
The error in SystemOut.log shows:
DefaultTransa E Message: Could not save object in repository.,
Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager
com.ibm.workplace.wcm.services.repository.RepositoryException:
Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager
...
Caused by: com.ibm.icm.da.DBAccessException:
java.sql.SQLFeatureNotSupportedException: DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream
at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857) | The JDBC driver does not meet WebSphere Portal v8's prerequisites. |
TRAIN_Q028 | IBM Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) - United States SECURITY BULLETIN
SUMMARY
The DiskFileItem class in Apache Commons Fileupload before version 1.3.3, used in IBM WebSphere MQ File Transfer Edition, specifically the Web Gateway component, could allow remote attackers to execute arbitrary code under the context of the current process, causing an undefined behavior.
VULNERABILITY DETAILS
CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]
DESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.
CVSS Base Score: 9.8
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM WebSphere MQ File Transfer Edition v7.0.0
IBM WebSphere MQ File Transfer Edition v7.0.1
IBM WebSphere MQ File Transfer Edition v7.0.2
IBM WebSphere MQ File Transfer Edition v7.0.3
IBM WebSphere MQ File Transfer Edition v7.0.4
REMEDIATION/FIXES
All affected product versions are already End of Support. Customers must contact IBM to obtain a fix for the affected release.
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
22 Dec 2017 Original 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. | Help with Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) I need to understand details regarding Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031). | CVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]
DESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.
CVSS Base Score: 9.8
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
TRAIN_Q029 | IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States dwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2)
SYMPTOM
Unable to connect to TWS 8.5.1 ,8.6 or 9.1/9.2 from DWC 9.3.
Check the WAS SystemOut.log for error :
SSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3,
but that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.
CAUSE
DWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect
RESOLVING THE PROBLEM
You can solve this problem by configuring your TWS engines to use TLS instead of SSL :
Backup and edit :
TWA_HOME/WAS/TWSProfile/config/cells/TWSNodeCell/security.xml
Find sslProtocol and change "SSL_TLS" to "TLS"
Find ssl.protocol and change value="SSL" to value="TLS"
Backup and edit :
TWA_HOME/WAS/TWSProfile/properties/ssl.client.props
Find com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS
Backup and edit :
TWA_HOME/WAS/TWSProfile/temp/ssl.client.props
Find com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS
Stop and restart WAS.
*Be aware that your Engines are now using TLS and so you must also reconfigure any DWC 9.2 or 9.1 installations that need to connect to those engines. You would change them to use TLS in the same way as above but also by the same changes in these copies of security.xml and ssl.client.props :
TWA_HOME/JazzSM/profile/config/cells/JazzSMNode01Cell/security.xml
TWA_HOME/JazzSM/profile/properties/ssl.client.props
TWA_HOME/JazzSM/profile/temp/ssl.client.props
Please consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted.
See technote 1689332. | TWS / DWC and WebSphere 8.5.5.4+ WebSphere for TWS & DWC were upgraded to 8.5.5.4 on most servers in a particular environment. However, any TWS servers that still had 8.5.5.2, could no longer be seen by the new DWC / WAS 8.5.5.4 servers. Those lower WAS version engines could not be added to the DWC.
Errors seen are:
AWSUI0833E The operation could not be completed. There has been a communication failure.
The internal message is: AWSJCO005E WebSphere Application Server has given the following error: Error getting WsnNameService properties.
What is the reason? | DWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect |
TRAIN_Q030 | IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)
QUESTION
When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain?
ANSWER
Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2 | Does DataPower support SHA-2? Is DataPower able to support SHA-2 ? | Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred. |
TRAIN_Q031 | IBM Handling 302 redirect error message in a Web Application Firewall - United States HTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:
Redirect and failed due to non idempotent request method. (RFC 2616 sec 10.3)
SYMPTOM
This technote pertains to the following errors.
Example 1: This example shows the service getting the following message: a Backside header failed to parse due to: Failed to establish a backside connection with a HTTP Redirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) message.
web-application-firewall (CookieEncrypt): Backside header failed to
parse due to: Failed to establish a backside connection
12:20:53 webapp-firewall warn 60452 10.176.3.97 HTTP Redirect from
'http://10.176.3.97:8080/cgi-bin/WebObjects.exe/IndvGate.woa/5/wo/2jHo28
QYOlhC2RZ1XQ15DE5OKo8/0.1.2.27.3.SecureSignOn.1' failed due to non
idempotent request method. (RFC 2616 sec 10.3)
Example 2: This example shows an HTTP response code 302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.
Wed May 21 2008 10:39:11 [mpgw][info] mpgw(ECP-MPGW):
tid(369602)[9.65.237.170]: HTTP response code 302 for
'http://9.65.237.170:8080/forum/ucplogin.php?mode=login'
Wed May 21 2008 10:39:11 [mpgw][warn] mpgw(ECP-MPGW):
tid(369602)[9.65.237.170]: HTTP Redirect from
'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' failed due to
non idempotent request method - RFC 2616 sec 10.3.
Wed May 21 2008 10:39:11 [mpgw][error] mpgw(ECP-MPGW):
tid(369602)[9.65.237.170]: Backside header failed to parse due to:
Failed to establish a backside connection
CAUSE
302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.
This is caused by the adherence to the HTTP RFC 2616 by the Datapower Appliance.
For additional information on the RFC you may see this page RFC2616 [http://www.w3.org/Protocols/rfc2616/rfc2616.html]
ENVIRONMENT
WebSphere DataPower XI50 and XS40
DIAGNOSING THE PROBLEM
Backside header failed to parse due to: Failed to establish a backside connection failed due to non idempotent request method. (RFC 2616 sec 10.3)
RESOLVING THE PROBLEM
To resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these "302 Redirects". Follow the steps outlined in the attached document that explain how to configure a web application firewall to handle the redirects using the attached ResetLocation.xsl stylesheet. With the specified edit for your environment, this file will handle most simple use cases and may also be edited to handle any additional requirements for your specific business solution.
sampleForRedirects.doc [/support/docview.wss?uid=swg21318593&aid=2] [/support/docview.wss?uid=swg21318593&aid=1]ResetLocation.xsl [/support/docview.wss?uid=swg21318593&aid=4] [/support/docview.wss?uid=swg21318593&aid=3]
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent Business Integration WebSphere DataPower SOA Appliances General Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent | Request fails with "non idempotent request method - RFC 2616 sec 10.3. " When a request is routed through DataPower and a redirect is done on a POST, the redirect will fail in DataPower and we can expect the following message to be logged in the error message: "non idempotent request method - RFC 2616 sec 10.3." How do I solve the problem? | To resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these "302 Redirects". |
TRAIN_Q033 | IBM Automatically renew trusted credential - United States security; trusted credentials SSO renew TECHNOTE (FAQ)
QUESTION
How do I choose the value to use for the Security > Authentication > Automatically renew trusted credential setting?
ANSWER
For IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.
The credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration.
* Primary namespace only (default setting): When you log on to the first namespace of your session, if you have trusted credentials for that account, the credentials are updated for the primary account only. All other credentials for other namespaces are not updated.
* Off: Credentials are not updated in any namespace.
* All namespaces: When you log on to the first namespace, your credentials are updated as described for "Primary namespace only". When you log on to additional namespaces, if your trusted credentials associated with the primary account contain logon information for that namespace, then those trusted credentials are updated. NOTE: Do not use the All namespaces option if users authenticate into secondary namespaces as different users.
A user's trusted credentials for a namespace will only be renewed once per day.
It is NOT possible to use SSO with the feature 'Automatically Renew Trusted Credentials' found in Cognos BI. The reason for this is due to the following:
"A trusted credential is special because the namespace credentials it stores must be usable at any time, not depending on any timestamp. This rules out SSO tickets like Kerberos tokens or SAP tokens as they will expire after a short time and will become unusable. A suitable trusted credential therefore usually is a pair consisting of a user name and a password. However, for SSO based authentication to IBM Cognos BI, there is no password available to the namespace that can be stored into the trusted credential. Therefore, this feature will only work for basic authentication, when the user provides a user name and password to the login screen." RELATED INFORMATION
Proven Practices: Securing the IBM Cognos 10 BI Environ [http://www.ibm.com/developerworks/data/library/cognos/security/cognos_bi_platform/page602.html]
Cognos Analytics 11 Equivalent Technote [http://www-01.ibm.com/support/docview.wss?uid=swg21998776] | Scheduled reports fail after changing password Scheduled reports fail after changing password | For IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.
The credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration. |
TRAIN_Q034 | IBM Tivoli Network Manager IP Edition 4.2.0 Fix Pack 3, 4.2.0-TIV-ITNMIP-FP0003 - United States DOWNLOADABLE FILES
ABSTRACT
This fix pack is a cumulative fix release and addresses several APARs and internally found issues since the release of Tivoli Network Manager IP Edition 4.2.0 Fix Pack 2.
DOWNLOAD DESCRIPTION
WHAT'S NEW: [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio]
http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__descriptio]n
Summary of the Enhancements included in this Fix Pack:
The following features and functions are introduced in Fix Pack 3.
Support for SLES 12.0
*
Support for DB2 version 11.1 *
Support for IBM zLinux Systems *
* Red Hat Enterprise zLinux Server 7.3 (s390x, 64 bit) SuSE zLinux Enterprise Server (SLES) 12.0 SP1(s390x,64 bit)
*
*
*
*
* https://www.ibm.com/software/passportadvantage/pao_customer.html
*
Offline geographical maps *
Custom geographical map layers *
Regional aggregation for geographical maps *
Before installing or upgrading Network Manager, refer to the Fix Pack Release notes:
http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html]
=====================================================================
Summary of fixes in V4.2.0 Fix Pack 3
=====================================================================
For details of an individual APAR, go to www.ibm.com/support [www.ibm.com/support] then enter the APAR name/# in "Search Support" then select search.
IV89573 EXPAT XML PARSER VULNERABILITIES IV90563 DELAY RCA REPROCESSING UPON SEEING CLEAR FOR ROOTCAUSE ALERT IV90626 CISCO WEBTOOLS SEND EMPTY EMAIL IV90807 SLOW PROCESSING IN STITCHER SWITCHFDBTOCONNECTIONS IV91086 THE DISCOVERY PROCESSES CANNOT BE STARTED FROM THE ITNM GUI WHEN ITNM IS INSTALLED IN A MASTER/SLAVE SETUP IV91094 IP Filtered view incorrectly skips links between non-matched interfaces IV91222 COLLAPSING A SUBGRAPH LEAVES THE NODES AN UNUSABLE DISTANCE FROM EACH OTHER. IV91592 TELLABS JAVA COLLECTOR TO DISPLAY CARD NAMES. IV91725 TIMER THREADS ARE NOT TIMELY GARBAGE COLLECTED IN THE STRUCTURE BROWSER TREE. IV92191 Huawei MPLSTelnet parse the recent 'display ip vpn-instance verbose' format incorrectly. This result in incorrect association of VPN Name and the respective interface IV92353 POLLER CORES STARTING SNMP POLICIES WITH ENTITIES IN SCOPE THAT HAVE NO IFNAME IV92982 RCA PLUGIN SGMENTATION FAULT OVER SMALLER NUMBER OF CHANGES IV93054 ITNM DEVICESTRUCTURE - INFERFACE EVENTS NOT INCLUDED IV93591 NO DATA BEING DISPLAYED ON TOP N PERFORMERS WIDGET IN THE NETWORK HEALTH DASHBOARD IV94005 DYNAMIC DISTINCT NETWORK VIEW CREATES EXTRA/DUPLICATE VIEWS. IV94658 LOCAL TYPE TOOLS FOR CONTEXT MENU IS NOT SUPPORTED BY ITNM 4.2
Known problems with V4.2.0 Fix Pack 3
http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html#relnotes__problems [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html#relnotes__problems] PREREQUISITES
Prerequisites and Installation Instructions
See http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html]
INSTALLATION INSTRUCTIONS
IBM TIVOLI NETWORK MANAGER IP EDITION V4.2.0 FIX PACK 3
=======================================================
Build 4.2.0.34
This document describes the known problems and APAR fixes for Network Manager V4.2.0 Fix Pack 3.
Copyright IBM Corporation 2017
1 WHAT'S NEW
See http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description]
2 INSTALLATION
See http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_installing.html]
3 POSTINSTALLATION AND CONFIGURATION
See http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_postinstallationtaskssummary.html [http://www.ibm.com/support/knowledgecenter/SSSHRK_4.2.0/itnm/ip/wip/install/task/nmip_ins_postinstallationtaskssummary.html]
4 KNOWN PROBLEMS AND LIMITATIONS
See http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__problems [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__problems]
5 SUMMARY OF APAR FIXES IN NETWORK MANAGER V4.2.0 FIX PACK 3
See http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__apar-fixes [http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__apar-fixes]
URL LANGUAGE SIZE(Bytes) 4.2.0_README_FP0003 [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0_README_FP0003&source=SAR] English 7178
DOWNLOAD PACKAGE
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 4.2.0-TIV-ITNMIP-AIX-FP0003 28 Apr 2017 Language Independent 3091689671 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-ITNMIP-Linux-FP0003 28 Apr 2017 Language Independent 3091689662 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-Linux-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-AIX-FP0003 28 Apr 2017 Language Independent 27899824 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-Linux-FP0003 28 Apr 2017 Language Independent 27899818 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-Linux-FP0003&source=SAR] [ ] | ITNM 4.2 Fix Pack 3 link and build number?. ITNM 4.2 FP3 is available, if yes then where we can download?. | http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description |
TRAIN_Q037 | IBM Tivoli Integrated portal enabling multiple logins using same user Id - United States TIPL2SEC tivoli integrated portal multiple logins TECHNOTE (FAQ)
QUESTION
How can I login to TIP from different machines using same user Id?
CAUSE
Need to login with multiple times with same user
ANSWER
Only TIP version 2.1 and higher support multiple logins using same user Id.
Follow below steps to configure Tivoli Integrated Portal to allow multiple users to log in using the same user Id and password.
1. Log in as an administrative user.
2. Navigate to:
tip_home_dir/profiles/TIPProfile/config/cells/TIPCell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF/
3. Edit consoleProperties.xml.
4. Locate the property with a id attribute of ENABLE.CONCURRENT.LOGIN and set its value to true.
5. Save the file and exit from the text editor.
6. Restart TIP server. | How can multiple TDWC users logon into TDWC with same TWS user id?
Given that one TDWC user is already accessing TDWC and a second TDWC user using the same logon id wants to logon to TDWC sees the following error:
Another user is currently logged in with the same user ID. Select from the following options:
List item
Log out the other user with the same user ID. You can recover changes made during the other user's session.
List item
Return to the Login page and enter a different user ID.
How can multiple users logon without one user needing to logout? | Only TIP version 2.1 and higher support multiple logins using same user Id.
Follow below steps to configure Tivoli Integrated Portal to allow multiple users to log in using the same user Id and password.
1. Log in as an administrative user.
2. Navigate to:
tip_home_dir/profiles/TIPProfile/config/cells/TIPCell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF/
3. Edit consoleProperties.xml.
4. Locate the property with a id attribute of ENABLE.CONCURRENT.LOGIN and set its value to true.
5. Save the file and exit from the text editor.
6. Restart TIP server. |
TRAIN_Q038 | IBM How to Rollback From a Fix Pack or Interim Fix to an Earlier Build - United States uninstall; revert; downgrade; hotsite; HS; out; fixpack TECHNOTE (FAQ)
QUESTION
There may be times when there is a need to remove a previously installed Fix Pack or Interim Fix (hotsite) and revert to the original installed version. This document describes how to roll back an installed Fix Pack or Interim Fix applied to Cognos BI.
ANSWER
Assuming create backup was selected, there will be a folder with the backup under the uninstall directory. Use these files to roll back. In version 10.2.1 FP1 and above there is no option to create a backup, instead backups are automatically created in the <cognos_install>/bkp directory.
Note that the backup directories only contain copies of all individual files that were modified by the fix pack or interim fix, not the entire contents of the original directory.
Care must also be taken when removing interim fixes to ensure that there weren't later interim fixes applied which also contain some of the same files. It is recommended that a full system and content store backup be performed before attempting.
Steps:
1. Stop the Cognos service and ensure that Cognos Configuration is not running.
2. When setting up the configuration of a newly installed Cognos BI environment, it is important to note that if you configure the new installation against the original content store, it is permanently upgraded to the new version and can no longer be used in the original environment. As a result, always create a backup of the content store prior to upgrading.
If a roll back to the original version is required, you can simply restore the backup. However, any work done after the content store has been upgraded (reports, models, security, etc...) to the new version will be lost, as all of this information is saved in the content store.
If you try to revert back to an earlier environment configured against the upgraded content store, you will get an error similar to the one below:
CM-CFG-5027 Unable to upgrade the content store to the to the version N that is compatible with this version of Content Manager. The current version of the content store is M.
3. Also, please refer to the notes on the fix pack which would include perquisites on Backup/Restore of content store and also other requirements.
4. For versions 8 - 10.2.1: In the <cognos_install>/uninstall/backup directory there will be a list of date stamped folders with the applied fix packs and/or interim fixes.
For versions 10.2.1 FP1 and above: This is stored in the <cognos_install>/bkp directory
5. Go into the folders and check the cmplst.txt file and check for the correct version to revert to.
6. Once the correct version is found, copy the contents of the whole folder and paste it at the <cognos_install> level, which will overwrite the files applied by fix pack or interim fix update.
7. Start the Cognos service.
HISTORICAL NUMBER
1028034 | We want to backout the Cognos component of Business Monitor to a previous version. What do we have to take care of? We want to backout the Cognos component of Business Monitor to a previous version. What do we have to take care of? | Stop the Cognos service and ensure that Cognos Configuration is not running.
2. When setting up the configuration of a newly installed Cognos BI environment, it is important to note that if you configure the new installation against the original content store, it is permanently upgraded to the new version and can no longer be used in the original environment. As a result, always create a backup of the content store prior to upgrading.
If a roll back to the original version is required, you can simply restore the backup. However, any work done after the content store has been upgraded (reports, models, security, etc...) to the new version will be lost, as all of this information is saved in the content store.
If you try to revert back to an earlier environment configured against the upgraded content store, you will get an error similar to the one below:
CM-CFG-5027 Unable to upgrade the content store to the to the version N that is compatible with this version of Content Manager. The current version of the content store is M.
3. Also, please refer to the notes on the fix pack which would include perquisites on Backup/Restore of content store and also other requirements.
4. For versions 8 - 10.2.1: In the <cognos_install>/uninstall/backup directory there will be a list of date stamped folders with the applied fix packs and/or interim fixes.
For versions 10.2.1 FP1 and above: This is stored in the <cognos_install>/bkp directory
5. Go into the folders and check the cmplst.txt file and check for the correct version to revert to.
6. Once the correct version is found, copy the contents of the whole folder and paste it at the <cognos_install> level, which will overwrite the files applied by fix pack or interim fix update.
7. Start the Cognos service. |
TRAIN_Q039 | IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States TECHNOTE (FAQ)
QUESTION
"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?"
CAUSE
*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack
ex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6.
The IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS)
See Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work.
"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits." ~IBM Java Development Team
If the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors/Locks. If these Class Pointers, Monitors/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http://www.ibm.com/developerworks/library/j-nativememory-linux/] will be thrown.
ANSWER
Why Use Compressed References?
Below the 4GB mark, the JVM does not have to perform any compression/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space.
Determining Address Location of Java Heap Memory
To verify if the Java heap has memory regions below the 4GB mark, check the "Object Memory" section in the javacore:
Convert the "start" address from the hex value to a GB value [http://ss64.com/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.
* [/support/docview.wss?uid=swg21660890&aid=1]
Setting the Preferred Heap Base with -Xgc:preferredHeapBase
Starting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV37797]).
NOTE: In IBM System z platforms (i.e. z/OS and z/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty
associated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below).
See related: IBM Knowledge Center - JVMJ9GC089W [https://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.messages/diag/appendixes/messages/j9gc/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory.
*
*
*
*
*
*
* This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.
Increase Maximum Heap Size to Force Heap Allocation Above the 4GB mark
Another way to ensure that the heap is allocated above the 4GB mark (Java 6.1.6.0 and Java 7.0.5.0 and later) is to set a maximum heap size equal to or greater than 4GB. For example -Xmx4G will ensure that the heap will have to be allocated above the 4GB mark. This will not work in earlier versions of the JVM since these earlier versions allowed the heap to straddle the 4GB mark, placing part of the memory above and some below (fixed as part of APAR IV37797) .
Further Investigation
If after setting -Xgc:preferredHeapBase=<address> or -Xmx4G a NOOM is still encountered (Java 6.1.6.0 and Java 7.0.5.0 and later), then further investigation is required at the application level. Look to decrease the size and usage of the applications Class Pointers and Monitors/Locks. Additionally, there are some WebSphere Application Server troubleshooting methods that may help reduce the native memory footprint. See: IBM Troubleshooting native memory issues [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21373312].
Reserving Low-Memory Space with -Xmcrs
If there is still free memory in the system when a Native OutOfMemory (NOOM) occurs, then the problem may be a shortage of memory in the low-memory region (under 4GB). Even if the Java heap is located above this boundary, other data associated with Java objects can be located in the low-memory region.
The OS memory allocator will deal out low-memory freely, thus memory resources in the lower boundary may run out. Later when the JVM tries to allocate memory for an artifact which is required to be allocated in low-memory (because the JVM has only reserved a 32bit pointer for it) it fails and throws an OutOfMemoryError.
Starting in Java 6.0.16.3, Java 6.1.8.3, Java 7.0.8.10, Java 7.1.2.10, there is a parameter -Xmcrs [http://www-01.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/xmcrs.html] which allows the JVM to increase the amount of low memory it reserves on startup. With this setting, as long as the low-memory usage by the JVM does not exceed the -Xmcrs value, NOOM in the lower boundary will be avoided.
To set this parameter, first decide what a reasonable value for your lower memory requirements may be. Reasonable value is unique to each environment so there is not a general recommendation.
* -Xmcrs<reasonable_value_for_lower_memory>
*
* NATIVEMEMINFO subcomponent dump routine
*
*
*
*
*
*
*
*
* [/support/docview.wss?uid=swg21660890&aid=2]
*
Disabling Compressed References with -Xnocompressedrefs As a last resort, if the native memory still can not be contained under the 4GB mark, you can set -Xnocompressedrefs [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/Xnocompressedrefs.html] as a generic JVM argument. [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] Using -Xnocompressedrefs will remove the use of compressed references and therefore remove the lower 4GB memory restriction on the Class Pointers and Monitors/Locks. This will however, result in a significant increase in Java heap memory requirements. It is not uncommon for 70% more heap space to be required. Due to the increased memory requirements it is strongly advised that the Java heap size is adjusted to a larger value and garbage collection is monitored and retuned as required.
Additionally, some benchmarks show a 10-20% relative throughput decrease when disabling compressed references: "Analysis shows that a 64-bit application without CR yields only 80-85% of 32-bit throughput but with CR yields 90-95%. Depending on application requirements, CR can improve performance up to 20% over standard 64-bit." See:ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf].
Before using -Xnocompressedrefs as a solution, first rule out the possibility of a native memory leak. Since using -Xnocompressedrefs will allow the the native memory to grow unbounded, a leak in native memory will lead to process size growth eventually leading to a process that needs to be paged out. The paging will incur performance overhead which will eventually lead to an unstable environment. Therefore careful consideration must be used when selecting -Xnocompressedrefs as a solution.
Memory Map Considerations
The below figure is a generalization of how the JVM handles addresses in each section of the memory map based on heap size and compressed references (CR). Please note that at each stage beyond having all of the Java memory contained below the 4GB mark, there will be performance consequences:
[/support/docview.wss?uid=swg21660890&aid=3]
No Compressed References Overhead using -Xnocompressedrefs
or
-Xmx > 25GB -increased memory footprint
-fewer/larger objects stored on heap leads to more frequent GC
-lower cache and translation look aside buffer (TLB) utilization [/support/docview.wss?uid=swg21660890&aid=4] Compressed References Overhead maximum heap address used by the Java JVM process is below 4GB none maximum heap address used by the Java JVM process is above 4GB but below 32GB compression/decompression of address pointers
Getting Assistance From IBM Support
If further assistance will be required from IBM WebSphere Support, please set the following -Xdump [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/tools/dumpagents_syntax.html] parameters in the generic JVM arguments [http://www-01.ibm.com/support/docview.wss?uid=swg21417365]:
*
*
*
Then restart the JVM and recreate the problem. Once the NOOM is encountered, process the resulting system core with jextract [http://www-01.ibm.com/support/docview.wss?uid=swg21577379]. Send the jextracted core file, heapdump, javacore, snap trace, systemOut.log, native_stderr.log, native_stdout.log and systemErr.log to IBM Support [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] for further analysis.
RELATED INFORMATION
Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]
AIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]
Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]
Compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]
IBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms] | How to remove the default -Xcompressedrefs from my WebSphere Application Server My understanding is that for performance reasons, the WebSphere Application server on 64bit JVMs is, by default, using compressed references (-Xcompressedrefs). Due to native OutOfMemory error, I would like to remove that default, so there is no such limitation imposed on my native memory size. | To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory. |
TRAIN_Q040 | IBM Installation Manager does not work if symbolic links are used for Installation Manager of installed product locations - United States RN1.5; RN1.5.1; RN1.5.0.1; RN1.5.2; RN1.5.3; RN1.6; RN1.6.1; RN1.6.2; RN1.6.3; RN1.6.3.1; RN1.7; RN1.7.1; RN1.7.2; SRX; 1628092; RATLC02668456; IPL; Symlink TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
You install IBM Installation Manager by using symbolic links at the root level for the agent data location or the installation location or for both locations and after a system change or system restart you cannot start Installation Manager or you cannot use Installation Manager to update or uninstall products.
CAUSE
When you install Installation Manager, the values for the agent data directory, the Installation Manager binaries, and the installation directories for products are stored internally as absolute paths with all the symbolic links resolved. If a symbolic link is used as part of the path for any of these directories or binaries, the symbolic link is replaced with its target value.
Similarly, when a product is installed with Installation Manager, the values for the installation location and shared resources directory are stored internally as absolute paths with all symbolic links resolved.
If the symbolic links change their values, the absolute path names for directories that are used by Installation Manager might change. When the Installation Manager starts, it will initialize itself using the data in the agent data location. However, the stored values for the paths to the agent data directory, Installation Manager binaries, or product installation locations do not point to the new locations. Installation Manager might fail to start, or might be unable to update or uninstall products that are installed.
RESOLVING THE PROBLEM
When choosing locations for the agent data directory, the Installation Manager binaries, shared resources directory, and the installation directories for products, do not use paths that include symbolic links.
If Installation Manager is using paths that no longer exist, create the old paths manually and mount the affected file systems at the original locations that are used by Installation Manager. Verify that the user IDs for Installation Manager have read access to each level of the recreated paths. | Is it recommended to use symbolic links when installing Omnibus 8.1 fixpacks? Is it recommended to use symbolic links when installing Omnibus 8.1 fixpacks? | You install IBM Installation Manager by using symbolic links at the root level for the agent data location or the installation location or for both locations and after a system change or system restart you cannot start Installation Manager or you cannot use Installation Manager to update or uninstall products. |
TRAIN_Q041 | IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) - United States SECURITY BULLETIN
SUMMARY
IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS).
VULNERABILITY DETAILS
CVEID:CVE-2017-5461 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5461]
DESCRIPTION:Mozilla Firefox could allow a remote attacker to execute arbitrary code on the system, caused by an out-of-bounds write during Base64 decoding operation in the Network Security Services (NSS) library. By persuading a user to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.
CVSS Base Score: 8.8
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125002 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125002]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ Appliance 8.0
Maintenance levels between 8.0.0.0 and 8.0.0.6
IBM MQ Appliance 9.0.x Continuous Delivery (CD) Release
Continuous delivery updates between 9.0.1 and 9.0.3
REMEDIATION/FIXES
IBM MQ Appliance 8.0
Apply fixpack 8.0.0.7 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=8.0.0.6&platform=All&function=all]
IBM MQ Appliance 9.0.x Continuous Delivery (CD) Release
Apply the ifix for APAR IT21888 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=9.0.3&platform=All&function=all]
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
24 Aug 2017 Updated to include IBM MQ Appliance 9.0.x CD release
14 Jul 2017 Original version published
*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. | Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) I need to understand details regarding Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461). Where can I find this information? | CVEID:CVE-2017-5461 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5461]
DESCRIPTION:Mozilla Firefox could allow a remote attacker to execute arbitrary code on the system, caused by an out-of-bounds write during Base64 decoding operation in the Network Security Services (NSS) library. By persuading a user to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.
CVSS Base Score: 8.8
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125002 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125002]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) |
TRAIN_Q042 | IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States EJQAB0067E; WSP0005E; LoginException; policy; theme; attribute; JCR TECHNOTE (TROUBLESHOOTING)
PROBLEM
Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions occur in the System* logs when accessing Portal pages after user authentication.
SYMPTOM
SystemOut.log shows:
[datestamp] 00000241 PolicyService E com.ibm.wps.policy.services.PolicyService getPolicy Exception calling storage api: com.ibm.portal.WpsException: EJQAB0067E: An error occurred while getting the policy root.
[datestamp] 00000241 PolicyManager E com.ibm.wps.policy.services.PolicyManagerServerSideImpl getPVSByPath throwing exception. PVS type not found for theme/SingleTopNav
SystemErr.log shows:
[datestamp] 00000241 SystemErr R javax.jcr.LoginException: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.
....
[datestamp] 00000241 SystemErr R Caused by: com.ibm.icm.da.DBAccessException: User id can not be null
[datestamp] 00000241 SystemErr R at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:177)
CAUSE
Authenticated user does not have the attribute defined in the backend user registry which matches the attribute defined in the store.puma_default.user.fbadefault.filter property in WP PumaStoreService Resource Environment Provider. Such attribute is used by JCR when querying for theme policy information.
DIAGNOSING THE PROBLEM
Collect the following:
* LDIF export of a sample user that hits this problem (if the backend user registry is LDAP) * If you cannot determine a specific user causing the error, you can use the following tracestring to confirm:
*=info:com.ibm.wps.policy.services.*=finest:com.ibm.wps.policy.commands.*=finest
Then look for the following line in trace.log: com.ibm.wps.policy.services.PolicyService PolicyService() ENTRY userid contructor: {DN of user}
* Resources.xml - can be found under * <wp_profile>/config/cells/<cellname>/clusters/<clustername>/ for cluster
* <wp_profile>/config/cells/<cellname>/nodes/<nodename>/servers/<portalservername>/ for standalone
Locate the WP PumaStoreService Resource Environment Provider in resources.xml and confirm if there is a defined property name for store.puma_default.user.fbadefault.filter. If not, then the default and active value for such property is "uid". If it does exist, then verify the attribute defined for the value. Then check the LDIF export for the user to confirm if such attribute is defined.
RESOLVING THE PROBLEM
Create/update the store.puma_default.user.fbadefault.filter custom property for the WP PumaStoreService Resource Environment Provider via the Integrated Solutions Console to an attribute that exists for all Portal users in the backend user registry (for example, "cn").
RELATED INFORMATION
#Puma Store Service [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Puma_Store_Service_wp8]
Setting service configuration properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8?OpenDocument&sa=true] | Non-admin users cannot access webDAV filestore. What is the likely reason? A non-admin user trying to access the webDAV filestore is unable to do so and they see the below exception in the portal logs:
Caused by: com.ibm.icm.da.DBAccessException: User id can not be null at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:159) at com.ibm.icm.da.portable.connection.ConnectionManager.logon(ConnectionManager.java:45) | Create/update the store.puma_default.user.fbadefault.filter custom property for the WP PumaStoreService Resource Environment Provider via the Integrated Solutions Console to an attribute that exists for all Portal users in the backend user registry (for example, "cn"). |
TRAIN_Q043 | IBM Pdcollect tool for ITM IBM i OS agent - United States ITM_TEMA_DIST_CONFIGURATION ITM_i5_Agent 5724C04 A4 OS/400 i5/OS IBMi IBM i pdcollect TECHNOTE (FAQ)
QUESTION
How do I collect logs and files for the IBM i OS agent?
ANSWER
The pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information.
Pdcollect is delivered in the IBM i OS agent beginning in ITM 6.23 FP5 and ITM 6.30 FP3. It is located in the following IFS directory:
/QIBM/ProdData/IBM/ITM/bin/pdcollect.sh
Pdcollect is also available as a downloadable file which is stored in an IFS directory chosen by the user. Download the following zip file to a local workstation and extract its contents. Follow the instructions in readme.txt for further information on installing the tool.
pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=2]pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=1]
The tool is executed by issuing the following shell script command in Qshell:
<directory>/pdcollect.sh
where <directory> is the IFS directory where the tool is stored.
You must execute pdcollect while running under a user profile that you use to run IBM Tivoli Monitoring to avoid problems with object authorities.
The output from the tool is a single compressed file that can be sent in binary form to IBM Support if requested. The output file is stored at the following location:
/tmp/ITM/pdcollect_ibmi.tar.Z
The output file is overwritten each time the tool is run. Copy or rename the output file after each invocation if more than one data collection is needed.
Instructions to view the data that has been collected is displayed in a message at the end of pdcollect processing.
The pdcollect tool for the IBM i OS agent does not collect information from the Tivoli Enterprise Monitoring Server (TEMS) or Tivoli Enterprise Portal Server (TEPS) systems. You may be asked to collect additional information from your TEMS or TEPS systems separately. | What is the equivalent of the .LG0 file for the OS agent - A4 - on i5 systems? What is the equivalent of the .LG0 file for the OS agent - A4 - on i5 systems? | The pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information. |
TRAIN_Q044 | IBM SPSS Student Version and Graduate Pack Resources - United States SPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)
QUESTION
Where do I get support for IBM SPSS Student Version or Graduate Pack software?
ANSWER
Step 1:
For installation & licensing issues on Student version and Graduate pack, contact your vendor.
* Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ]
* On the Hub [http://onthehub.com/]
* StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx]
* JourneyEd [https://www.journeyed.com/contact]
* thinkEDU [https://thinkedu.desk.com/]
* Studica [http://www.studica.com/technical-support]
Cross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version | Authorization code missing for SPSS 25? I purchased the IBM SPSS from Amazon, and I do not know where to locate the authorization code of license code/key. Can anyone help me? | For installation & licensing issues on Student version and Graduate pack, contact your vendor. |
TRAIN_Q045 | IBM Insufficient Access Error adding documents to FileNet Content Engine - United States FNRCE0001E; E_ACCESS_DENIED; unable to add document TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
User is getting a security error when attempting to add a document to a folder in an object store via FileNet Workplace XT or FileNet Enterprise Manager.
Security Error seen: The requester has insufficient access rights to perform the requested operation.
CAUSE
User does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents.
DIAGNOSING THE PROBLEM
* User has necessary rights to the document class, folders and object store but can't add document.
* User does not have necessary Create_Instance rights on the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes.
* Error seen in the P8_server_error.log:
YYYY-06-08T17:53:19.706Z 56005600 ENG FNRCE0001E - ERROR method name: checkUpdatePermissions principal name: username Global Transaction: true User Transaction: false Exception Info: The requester has insufficient access rights to perform the requested operation.
com.filenet.api.exception.EngineRuntimeException: FNRCE0001E: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation. failedBatchItem=0 errorStack={
RESOLVING THE PROBLEM
Steps to resolve issue:
1. Log in to FileNet Enterprise Manager.
2. Grant the user CREATE_INSTANCE rights to the Security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes.
3. Re-try adding the document. | Unable to add the document using content Navigator. We are getting the following error code. CIWEB1158. The user is unable to add the document using content Navigator. We are getting the following error code. CIWEB1158. | User does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents. |
TRAIN_Q046 | IBM IV67523 Move local data from CANDLEHOME to another file system - United States 6.30.05.00 CANDLEHOME CANDLEDATA itmCANDLEDATA.sh TECHNOTE (FAQ)
QUESTION
How do I move local data such as configuration files, log files, historical data, etc. from CANDLEHOME to a different file system?
CAUSE
Since its inception, IBM Tivoli Monitoring (ITM) has stored local data such as configuration files, log files, and historical data together with the installation files in CANDLEHOME. For example, ITM normally installs in a directory named /opt/IBM/ITM. Within that directory, it stores programs in subdirectory names like /opt/IBM/ITM/bin and /opt/IBM/ITM/classes. It also stores local data in subdirectory names like /opt/IBM/ITM/config and /opt/IBM/ITM/logs. This homogeneous design is a problem for installations that require an approach that keeps code in /opt and stores data in the /var file system.
ANSWER
Introduction
Under APAR IV67523, ITM added a new mechanism to move local data to a different file system. For example, data typically stored in /opt/IBM/ITM/config and /opt/IBM/ITM/logs can be redirected to /var/IBM/ITM/config and /var/IBM/ITM/logs. This new file system location is designated by the user at installation time, and it is referred to as CANDLEDATA. A conversion utility is provided to implement CANDLEDATA for existing installations.
The CANDLEDATA mechanism is available with ITM 6.30.05.00.
How CANDLEDATA Works
The CANDLEDATA mechanism is implemented primarily using symbolic links. This means most of the underlying code in ITM is unaware of CANDLEDATA. This also means the CANDLEDATA mechanism is limited to Linux and UNIX platforms.
The rest of this section shows examples of links where CANDLEHOME=/opt/IBM/ITM and CANDLEDATA=/var/IBM/ITM. You can define different locations for your own installation.
Base Directory Links
The following local data directories are always linked from CANDLEHOME to CANDLEDATA:
* /opt/IBM/ITM/InstallITM -> /var/IBM/ITM/InstallITM
*
* /opt/IBM/ITM/config -> /var/IBM/ITM/config
*
* /opt/IBM/ITM/kt1v3depot -> /var/IBM/ITM/kt1v3depot
*
* /opt/IBM/ITM/localconfig -> /var/IBM/ITM/localconfig
*
* /opt/IBM/ITM/logs -> /var/IBM/ITM/logs
*
* /opt/IBM/ITM/patchlogs -> /var/IBM/ITM/patchlogs
*
* /opt/IBM/ITM/tables -> /var/IBM/ITM/tables
*
* /opt/IBM/ITM/tmaitm6/agentdepot -> /var/IBM/ITM/tmaitm6/agentdepot
*
* /opt/IBM/ITM/tmp -> /var/IBM/ITM/tmp
These directories and links are automatically generated by ITM when the system is installed or converted to use CANDLEDATA.
General Agent Directory Links
In addition to the base set of directory links, most agents have general links for TEMA data:
* /opt/IBM/ITM/ATTRLIB -> /var/IBM/ITM/ATTRLIB
*
* /opt/IBM/ITM/<platform>/<pc>/tables/ATTRLIB -> /var/IBM/ITM/ATTRLIB/<pc>
*
* /opt/IBM/ITM/EIFLIB -> /var/IBM/ITM/EIFLIB
*
* /opt/IBM/ITM/<platform>/<pc>/tables/EIFLIB -> /var/IBM/ITM/EIFLIB/<pc>
*
* /opt/IBM/ITM/hist -> /var/IBM/ITM/hist
*
* /opt/IBM/ITM/<platform>/<pc>/hist -> /var/IBM/ITM/hist/<pc>
*
* /opt/IBM/ITM/psit -> /var/IBM/ITM/psit
*
* /opt/IBM/ITM/<platform>/<pc>/psit -> /var/IBM/ITM/psit/<pc>
These directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA.
Special Agent Directory Links
Some agents have links that are specific to that agent. For example, the LZ and UX agents create the following link for the Watchdog component to store local data:
* /opt/IBM/ITM/kca -> /var/IBM/ITM/kca
These directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA.
CANDLEDATA <-> CANDLEHOME Directory Links
The CANDLEHOME and CANDLEDATA directories also have cross references to each other:
* /opt/IBM/IBM/registry/CANDLEDATA -> /var/IBM/ITM
*
* /opt/IBM/ITM <- /var/IBM/ITM/CANDLEHOME
These links are all automatically generated by ITM when the system is installed or converted to use CANDLEDATA.
Configuration Variables exploited by CANDLEDATA
In addition to symbolic links, some individual components have special configuration settings to redirect agent-specific data to CANDLEDATA. ITM redirects data using the following configuration variables:
* CTIRA_SIT_PATH
*
* CANDLEHOME/
* <platform>/<pc>/psit
*
*
* KCA_IP_DIR
*
* CANDLEHOME/kca
*
*
* KCAWD_WRITE_DIR
*
* CANDLEHOME/kca
*
*
Notes: 1. While the variables point to CANDLEHOME/xxx, the directory links cause the local data to be written to the corresponding CANDLEDATA/xxx.
2. If you use configuration overrides that set these configuration variables, you'll need to review how those overrides work in an environment configured to use CANDLEDATA. In most cases, you'll want to remove your overrides.
Configuration Variables affected by CANDLEDATA
The symbolic links established by ITM for CANDLEDATA assume standard agent configuration. If you've modified any of the following, data will be continue to be redirected to the location you specified instead of the CANDLEDATA directory:
.
* ATTRLIB
*
* CTIRA_HIST_DIR
*
* EIFLIB
*
*
When converting an existing CANDLEHOME, ITM migrates any data in the original directories before linking them to CANDLEDATA. If you've modified any of the following, you must consider whether you need to change the setting and migrate the data manually:
. * CTIRA_SIT_FILE
*
*
By default, all of the following configuration variables direct data to /opt/IBM/ITM/localconfig. ITM migrates data from /opt/IBM/ITM/localconfig to /var/IBM/ITM/localconfig and then links the two. If you've modified any of these, you must consider whether you need to change the setting and migrate the data manually:
. * CTIRA_THRESHOLDS
*
* IRA_EVENT_EXPORT_SNMP_TRAP_CONFIG
*
*
* IRA_LOCALCONFIG_DIR
*
*
* IRA_PRIVATE_SITUATION_CONFIG
*
*
* IRA_SERVICE_INTERFACE_DEFAULT_PAGE
*
*
* IRA_SERVICE_INTERFACE_DIR
*
*
* KXX_FCP_SCRIPT_DEFINITIONS
Known Restrictions
1. The CANDLEDATA mechanism is available only for ITM on Linux and UNIX. ITM on Windows continues to keep local data under CANDLEHOME.
.
2. No facility is provided switch from a CANDLEHOME+CANDLEDATA implementation back to a unified CANDLEHOME implementation. To do this, you must uninstall and reinstall ITM.
.
3. No facility is provided to move CANDLEDATA from one directory to another. To do this, you must uninstall and reinstall ITM.
.
4. The CANDLEHOME and CANDLEDATA arrangement is a 1:1 relationship. * Only one CANDLEHOME can use a given CANDLEDATA. This means a given CANDLEDATA cannot be shared with multiple CANDLEHOMEs.
* A given CANDLEHOME can only use one CANDLEDATA. This means components cannot be split amongst multiple CANDLEDATAs.
.
5. The monitoring server and portal server cannot exploit CANDLEDATA. * The conversion utility will not convert an existing CANDLEHOME if it contains the monitoring server or portal server.
* The installer warns if CANDLEDATA is specified and the install image contains the monitoring server or portal server. However, the installer does not prevent monitoring server or portal server from being installed.
* ITM does not allow the monitoring server to start if CANDLEDATA is implemented.
* ITM does not allow the portal server to start if CANDLEDATA is implemented.
.
6. Not all agents have been verified to work with CANDLEDATA. Before using CANDLEDATA, check with the support group for each of the agents you intend to install.
.
7. System Monitor Agents (SMA) can exploit CANDLEDATA. However, the SMA installer does not create CANDLEDATA. These agents must be converted to use CANDLEDATA after they are installed.
.
8. The CANDLEDATA mechanism is intended only for current agents. If the agent media contains installer 6.30.00.00 or above, it should be ok to use with CANDLEDATA.
Some older or discontinued agents such as the Universal Agent (UM) and UNIX Logs agent (UL) cannot use CANDLEDATA reliably. ITM does not prevent older or discontinued agents from being installed into a new CANDLEHOME with CANDLEDATA implemented.
.
9. When CANDLEDATA is in use, ITM implements internal overrides for the following configuration variables: CTIRA_SIT_PATH, KCA_IP_DIR, and KCAWD_WRITE_DIR. * If you've already overridden any of these configuration variables, you must remove the overrides before converting a given component.
* If you've overridden these with CANDLEHOME/config/xx.environment, the conversion utility will detect and warn about them. Your overrides will win, so you must remove them.
* If you've overridden these with the old method of sourcing a script into CANDLEHOME/config/xx.ini, the conversion utility cannot detect them. However, the CANDLEDATA overrides will win.
.
10. The prerequisite scanner does not know about CANDLEDATA. It continues to assume everything is stored in CANDLEHOME. This means: * No space checking is performed for CANDLEDATA.
* Results are somewhat inflated for CANDLEHOME.
.
11. The conversion utility does not check for space when converting an existing new CANDLEHOME to use CANDLEDATA. Make sure there is enough space in CANDLEDATA before starting the conversion process.
Agents Verified with CANDLEDATA
The following agents have been verified to run properly when CANDLEDATA is implemented:
* LO
*
*
* LZ
*
*
* UD
*
*
* UX
*
*
For other agents, contact the corresponding support team.
Setting Up a New Local Installation with CANDLEDATA
For new installations, you can define the location for local data at installation time.
Local install (interactive):
*
* CANDLEDATA
*
* CANDLEHOME
*
*
*
* # ./install.sh
*
* INSTALL
*
*
* Enter the name of the IBM Tivoli Monitoring installation directory.
*
* [ default = /opt/IBM/ITM ]:
*
* "/opt/IBM/ITM" does not exist
*
* Try to create it [ 1-yes, 2-no; "1" is default ]?
*
* Creating directory "/opt/IBM/ITM"...
*
*
* Enter the name of the IBM Tivoli Monitoring local data directory.
*
* [ default = /opt/IBM/ITM ]: /var/IBM/ITM
*
* "/var/IBM/ITM" does not exist
*
* Try to create it [ 1-yes, 2-no; "1" is default ]?
*
* Creating directory "/var/IBM/ITM"...
*
* itmCANDLEDATA.sh: Installation directory "/opt/IBM/ITM" successfully converted to use data directory "/var/IBM/ITM".
*
*
*
* CANDLEDATA
*
*
*
*
* CANDLEDATA
*
* CANDLEHOME
*
* CANDLEDATA
*
* CANDLEHOME
*
* CANDLEHOME
*
Local install (silent):
*
* CANDLEDATA
*
* CANDLEDATA
*
*
*
* install.sh
[-l
* CANDLEDATA
* ]
*
Where: * -l
*
* CANDLEHOME
*
*
*
* CANDLEDATA
*
* install.sh
*
*
*
*
* CANDLEDATA
*
* CANDLEHOME
*
* CANDLEDATA
*
* install.sh
*
Starting an agent for the first time with CANDLEDATA
When you specify CANDLEDATA at install time, ITM establishes the base directory links. All agent-specific conversion is handled the first time a given agent is started. When this happens, an extra message is included in the agent start output: Here is an example:
# itmcmd agent start ux
Processing. Please wait...
itmCANDLEDATA.sh: Component ux successfully converted to use data directory "/var/IBM/ITM".
Starting Monitoring Agent for UNIX OS ...
Monitoring Agent for UNIX OS started
Converting an existing installation or new agents to use CANDLEDATA
For existing installations, ITM provides a utility to convert a CANDLEHOME to use CANDLEDATA. You can also use this utility to convert a newly installed agent before it is started. Under the covers, the installer runs this same utility.
itmCANDLEDATA.sh
[-b yes|no]
[-h CANDLEHOME]
[-l CANDLEDATA]
[-f no|yes]
[-p PC|*]
[-r no|yes]
Where:
*
* -b
*
* yes
*
* CANDLEDATA
*
* CANDLEHOME
*
* CANDLEHOME
*
* no
*
* CANDLEDATA
*
*
*
* -h
*
*
*
* -l
*
* CANDLEHOME
*
* CANDLEDATA
*
*
*
* -f
*
* no
*
* yes
*
*
*
* -p
*
* *
*
*
*
* -r
*
* no
*
* yes
*
If you set the CANDLEHOME or CANDLEDATA environment variables before launching the installer, then those values are used as though they had been passed with the command options. If both the command option is used and the environment variable is defined before the conversion utility is started, the command option takes precedence.
Example 1: Conversion of a typical CANDLEHOME can be performed with an incantation similar to this: *
* itmCANDLEDATA.sh -l /var/IBM/ITM -b yes -p "*" -r yes
Example 2: Conversion of a newly installed agent to a CANDLEHOME where CANDLEDATA is already implemented can be performed with an incantation similar to this: *
* itmCANDLEDATA.sh -b no -p "ux" -r yes
Using CANDLEDATA with Remote Deploy
You can define the location for local data remotely:
tacmd createnode (new installations):
*
* CANDLEDATA
*
* CANDLEDATA
*
*
*
* tacmd createnode ... -o ENV_CANDLEDATA=
* data_directory
* ...
*
*
*
* install.sh
*
* CANDLEDATA
*
*
tacmd executecommand + itmCANDLEDATA.sh (existing installations):
*
* CANDLEDATA
*
* tacmd updateagent
*
* CANDLEDATA
*
* tacmd executecommand
*
*
*
* tacmd executecommand ... -c "/opt/IBM/ITM/bin/itmCANDLEDATA.sh -l /var/IBM/ITM -p \"*\" -b yes -r yes > /tmp/itmCANDLEDATA_remote.log 2>&1 &"
*
*
*
*
* Launches the conversion utility on the agent (/opt/IBM/ITM/bin/itmCANDLEDATA.sh). Specifies the local data directory (-l /var/IBM/ITM). Specifies all agents are to be converted (-p \"*\"). Note that the quotes are escaped because the entire command string is quoted. Specifies the CANDLEDATA directory is to be built (-b yes). Specifies the agents are to be restarted (-r yes). Redirects STDOUT and STDERR to a log file (> /tmp/itmCANDLEDATA_remote.log 2>&1). Note that the standard -o/-e/-d/-v options for tacmd executecommand don't function properly because of the agent restart. Note also that /tmp is used instead of /opt/IBM/ITM/logs; the latter is moved during the conversion process and therefore must be inactive. Launches the command in the background (trailing &). tacmd executecommand waits for the commands to complete, and this is signaled by a communication from the agent. However, since the agent is restarted by the command, it will never reply to tacmd executecommand. Running the command in the background allows tacmd executecommand to complete normally.
Other Implications
The following general ITM utilities have been updated to run properly when CANDLEDATA is implemented:
* cinfo - The output heading indicates the location of CANDLEDATA if it implemented.
* itmcmd agent start - Agent configurations are automatically updated if CANDLEDATA is implemented. Also, the portal server is prevented from starting if CANDLEDATA is implemented.
* itmcmd server start - The monitoring server is prevented from starting if CANDLEDATA is implemented.
* secureMain - Permissions and ownership in CANDLEDATA are maintained just as in CANDLEHOME. If secureMain was run before CANDLEDATA is implemented, the conversion utility automatically runs secureMain again as part of the conversion process. However, if you run the conversion utility as a nonroot user (not recommended), you must run secureMain manually after conversion is complete.
* tacmd pdcollect and pdcollect - Data is gathered from CANDLEDATA just as from CANDLEHOME.
* uninstall.sh - Relevant data is removed from in CANDLEDATA just as from CANDLEHOME. For uninstall.sh REMOVE EVERYTHING, both the CANDLEHOME and CANDLEDATA directories are removed. | Does Linux KVM monitoring agent support CANDLEDATA function? Does Linux KVM monitoring agent in ITM support CANDLEDATA function? | The CANDLEDATA mechanism is available with ITM 6.30.05.00. |
TRAIN_Q047 | IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States SECURITY BULLETIN
SUMMARY
A comma separated file (CSV) download feature exists in IBM BPM and WLE and is available for anonymous users. An attacker can craft a URL that can trigger a download of attacker-supplied content under an attacker-supplied file name onto the victim's machine.
VULNERABILITY DETAILS
CVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]
DESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.
CVSS Base Score: 7.1
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L)
AFFECTED PRODUCTS AND VERSIONS
- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5
- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2
- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3
- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12
REMEDIATION/FIXES
Install IBM BPM or WLE interim fix JR57149 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR57149]as appropriate for your current version.
* IBM Business Process Manager Advanced [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR57149]
* IBM Business Process Manager Standard [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR57149]
* IBM Business Process Manager Express [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR57149]
* WebSphere Lombardi Edition [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=JR57149]
As IBM Business Process Manager V7.5 and WebSphere Lombardi Edition are out of general support, customers with a support extension contract can contact IBM support to request the fix. The fix disables the vulnerable URL and uses HTML5 features to trigger CSV download without server interaction.
For WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5
* Install Fix Pack 5 [http://www-01.ibm.com/support/docview.wss?uid=swg24034270] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V7.5.0.0 through V7.5.1.2: * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24031230], install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24036462] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V8.0.0.0 through V8.0.1.3 * Upgrade to minimal Refresh Pack 1 [http://www-01.ibm.com/support/docview.wss?uid=swg24033777], install Fix Pack 3 [http://www-01.ibm.com/support/docview.wss?uid=swg24037734] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V8.5.0.0 through V8.5.0.2 * Install Fix Pack 2 [http://www-01.ibm.com/support/docview.wss?uid=swg24040683] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V8.5.5.0 * Apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V8.5.6.0 through V8.5.6.0 CF2 * Install CF2 [http://www-01.ibm.com/support/docview.wss?uid=swg24041303] as required by iFix and then apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
For IBM BPM V8.5.7.0 through V8.5.7.0 CF 2016.12 * Install CF 2016.12 [https://www.ibm.com/support/docview.wss?uid=swg27048992] and then apply iFix JR57149 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]
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.
IMPORTANT NOTE
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
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]
ACKNOWLEDGEMENT
The vulnerability was reported to IBM by Nalla Muthu S and Prasath K
CHANGE HISTORY
24 Feb 2017: initial version published
*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.
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Solaris, Windows 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2 | Help with Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 Where can I find information for Security bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693? | CVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]
DESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.
CVSS Base Score: 7.1
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) |
TRAIN_Q048 | IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States ACCE; CE; Property; FEM TECHNOTE (FAQ)
QUESTION
With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class
1. Launch FEM
2. Expand the object store and document class tree. Right click on the document class and select "Properties"
3. Go to "Properties Definitions" tab, highlight the property definition and click "Edit"
4. Make the modification and click OK
5. Click OK again to save the change
How to perform the same operation with FileNet Content Engine - ACCE?
ANSWER
Follow the below steps to update the property definition properties on ACCE:
1. Launch ACCE
2. Expand the object stores folder and click the object store to open the Object store tab
3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab
4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify
5. ACCE will open that property definition in a new Properties tab
6. Modify the property definition as required
7. Go back to the Class Definition tab and click Save | How to change the maximun string length for properties in ACCE
HI I am trying to change the maximum string length in ACCE like we will do in FEM but in the more Tab I am not seeing the option
Please guide me | Follow the below steps to update the property definition properties on ACCE:
1. Launch ACCE
2. Expand the object stores folder and click the object store to open the Object store tab
3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab
4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify
5. ACCE will open that property definition in a new Properties tab
6. Modify the property definition as required
7. Go back to the Class Definition tab and click Save |
TRAIN_Q049 | IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States SECURITY BULLETIN
SUMMARY
There is a potential privilege escalation in WebSphere Application Server Admin Console.
VULNERABILITY DETAILS
CVEID: CVE-2017-1731 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1731]
DESCRIPTION: IBM WebSphere Application Server could provide weaker than expected security when using the Administrative Console. An authenticated remote attacker could exploit this vulnerability to possibly gain elevated privileges.
CVSS Base Score: 8.8
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134912 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134912] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)
AFFECTED PRODUCTS AND VERSIONS
This vulnerability affects the following versions and releases of IBM WebSphere Application Server:
* Version 9.0
* Version 8.5
* Version 8.0
* Version 7.0
REMEDIATION/FIXES
The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI89498 for each named product as soon as practical.
For WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition:
For V9.0.0.0 through 9.0.0.6:
· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24044155] [http://www-01.ibm.com/support/docview.wss?uid=swg24044154]
--OR--
· Apply Fix Pack 9.0.0.7 or later.
For V8.5.0.0 through 8.5.5.13:
· Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445]
--OR--
· Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018).
For V8.0.0.0 through 8.0.0.14:
· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512]
--OR--
· Apply Fix Pack 8.0.0.15 or later.
For V7.0.0.0 through 7.0.0.43:
· Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512] [http://www-01.ibm.com/support/docview.wss?uid=swg24044445] [http://www-01.ibm.com/support/docview.wss?uid=swg24043596] [http://www-01.ibm.com/support/docview.wss?uid=swg24042712] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394] [http://www-01.ibm.com/support/docview.wss?uid=swg24042513] [http://www-01.ibm.com/support/docview.wss?uid=swg24041604] [http://www-01.ibm.com/support/docview.wss?uid=swg24041394]
--OR--
· Apply Fix Pack 7.0.0.45 or later.
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.
IMPORTANT NOTE
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
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
29 January 2018: original document published
*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. | Help with Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WSRR (CVE-2017-1731) I need to understand details regarding Security Bulletin: Vulnerability identified in IBM WebSphere Application Server shipped with IBM WebSphere Service Registry and Repository (CVE-2017-1741). We are running WAS traditional V8.5. What is the recommended fix? | · Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI89498 [http://www-01.ibm.com/support/docview.wss?uid=swg24044512]
--OR--
· Apply Fix Pack 8.0.0.15 or later. |
TRAIN_Q050 | IBM Configuring access for HTTP and HTTPS in Jazz for Service Management - United States jazzsm11relnotes; jazzsm1101relnotes; jazzsm1102; jazzsm1103relnotes; relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; HTTP; HTTPS TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
By default, the Jazz™ for Service Management application server requires HTTPS access. You can set up the environment for both HTTP and HTTPS, however HTTP access is not supported.
CAUSE
For security reasons, HTTP access is disabled by default and is not supported.
RESOLVING THE PROBLEM
Before you begin
After installing Dashboard Application Services Hub and before beginning this procedure, log in to the console to ensure that it has connectivity and can start successfully.
About this task
Configuring for HTTP and HTTPS console access involves editing theweb.xmlfile of Web components. Use this procedure to identify and edit the appropriate Web XML files.
Important: These steps are provided for information purposes only, as setting up the environment for HTTP access is not supported.
Procedure
1. Change to the following directory:JazzSM_WAS_Profile/config/cells/JazzSMNode01Cell/applications.
2. From this location, locate theweb.xmlfiles in the following directories:
* For the Integrated Solutions Console web application archive:isc.ear/deployments/isc/isclite.war/WEB-INF
* For the Charts web application archive:isc.ear/deployments/isc/TIPChartPortlet.war/WEB-INF
* For the Dashboard Application Services Hub Change Password web application archive:isc.ear/deployments/isc/TIPChangePasswd.war/WEB-INF
3. Open one of the web.xmlfiles using a text editor. 4. Find the<transport-guarantee>element. The initial value of all<transport-guarantee>elements isCONFIDENTIAL, meaning that secure access is always required.
5. Change the setting toNONEto enable both HTTP and HTTPS requests. The element now reads:<transport-guarantee>NONE</transport-guarantee>.
6. Save the file, and then repeat these steps for the otherweb.xmldeployment files.
7. Stop and restart the server. [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.2.1/com.ibm.psc.doc/admin/psc_ctr_admin_restart_jazzsm_servers.html]
Example
The following example is a section of theweb.xmlfile forTIPChangePasswdwhere the transport-guarantee parameter is set toNONE:
<security-constraint>
<display-name>
ChangePasswdControllerServletConstraint</display-name>
<web-resource-collection>
<web-resource-name>ChangePasswdControllerServlet</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<auth-constraint>
<description>Roles</description>
<role-name>administrator</role-name>
<role-name>operator</role-name>
<role-name>configurator</role-name>
<role-name>monitor</role-name>
<role-name>iscadmins</role-name>
</auth-constraint>
<user-data-constraint>
<transport-guarantee>NONE</transport-guarantee>
</user-data-constraint>
</security-constraint>
What to do next
Users must now specify a different port, depending on the mode of access. The default port numbers are as follows:
http://<host_name>:16310/ibm/console
Use the HTTP port for logging in to the Dashboard Application Services Hub on the HTTP port .
https://<host_name>:16311/ibm/console
Use the HTTPS secure port for logging in to the Dashboard Application Services Hub.
Note:If you want to use single sign-on (SSO) then you must use the fully qualified domain name of the Dashboard Application Services Hub host. | Does JazzSM 1.1.2.1 support HTTP access? Does JazzSM 1.1.2.1 support HTTP access? | By default, the Jazz™ for Service Management application server requires HTTPS access. You can set up the environment for both HTTP and HTTPS, however HTTP access is not supported. |
TRAIN_Q052 | IBM Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) - United States SECURITY BULLETIN
SUMMARY
An IBM MQ application with authority to connect to a remote queue manager could send a malicious request that could cause undefined behaviour within the channel process servicing that connection, including a loss of service for other connections being serviced by the same channel process.
VULNERABILITY DETAILS
CVEID:CVE-2017-1557 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1557]
DESCRIPTION:IBM MQ could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests.
CVSS Base Score: 4.3
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/131547 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131547]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7
IBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS
IBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD
REMEDIATION/FIXES
IBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7
Apply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861]
IBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS
Apply fix pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]
IBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD
Apply IBM MQ 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
22 Dec 2017 - Original Published
*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. | Help with Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) I need to understand details regarding Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557). Where can I find this information? | CVEID:CVE-2017-1557 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1557]
DESCRIPTION:IBM MQ could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests.
CVSS Base Score: 4.3
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/131547 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131547]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) |
TRAIN_Q053 | IBM Unable to add Centera Device in FileNet Content Engine - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Errors received clicking "Test Connection" when configuring Centera Device in FileNet Enterprise Manager
SYMPTOM
After entering configuration information in FEM Fixed Content Device Wizard the following error is received:
File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $
The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).
Error in the p8_server_error.log:
2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.
com.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={
Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0
Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)
CAUSE
Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded.
ENVIRONMENT
IBM Websphere
DIAGNOSING THE PROBLEM
Following error is received when "Test Connection" is clicked:
File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $
The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).
RESOLVING THE PROBLEM
After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.
Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine
HISTORICAL NUMBER
41550
180
000 | P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider
New P8 CPE 5.2.1 install does not see the Centera Fixed Storage. The following error is returned:
FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. FPLibrary (Not found in java.library.path)
What is the cause? | Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. |
TRAIN_Q054 | IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States TECHNOTE (FAQ)
QUESTION
"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?"
CAUSE
*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack
ex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6.
The IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS)
See Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work.
"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits." ~IBM Java Development Team
If the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors/Locks. If these Class Pointers, Monitors/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http://www.ibm.com/developerworks/library/j-nativememory-linux/] will be thrown.
ANSWER
Why Use Compressed References?
Below the 4GB mark, the JVM does not have to perform any compression/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space.
Determining Address Location of Java Heap Memory
To verify if the Java heap has memory regions below the 4GB mark, check the "Object Memory" section in the javacore:
Convert the "start" address from the hex value to a GB value [http://ss64.com/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.
* [/support/docview.wss?uid=swg21660890&aid=1]
Setting the Preferred Heap Base with -Xgc:preferredHeapBase
Starting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http://www-01.ibm.com/support/docview.wss?uid=swg1IV37797]).
NOTE: In IBM System z platforms (i.e. z/OS and z/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty
associated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below).
See related: IBM Knowledge Center - JVMJ9GC089W [https://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.messages/diag/appendixes/messages/j9gc/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor/Lock memory.
*
*
*
*
*
*
* This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.
Increase Maximum Heap Size to Force Heap Allocation Above the 4GB mark
Another way to ensure that the heap is allocated above the 4GB mark (Java 6.1.6.0 and Java 7.0.5.0 and later) is to set a maximum heap size equal to or greater than 4GB. For example -Xmx4G will ensure that the heap will have to be allocated above the 4GB mark. This will not work in earlier versions of the JVM since these earlier versions allowed the heap to straddle the 4GB mark, placing part of the memory above and some below (fixed as part of APAR IV37797) .
Further Investigation
If after setting -Xgc:preferredHeapBase=<address> or -Xmx4G a NOOM is still encountered (Java 6.1.6.0 and Java 7.0.5.0 and later), then further investigation is required at the application level. Look to decrease the size and usage of the applications Class Pointers and Monitors/Locks. Additionally, there are some WebSphere Application Server troubleshooting methods that may help reduce the native memory footprint. See: IBM Troubleshooting native memory issues [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21373312].
Reserving Low-Memory Space with -Xmcrs
If there is still free memory in the system when a Native OutOfMemory (NOOM) occurs, then the problem may be a shortage of memory in the low-memory region (under 4GB). Even if the Java heap is located above this boundary, other data associated with Java objects can be located in the low-memory region.
The OS memory allocator will deal out low-memory freely, thus memory resources in the lower boundary may run out. Later when the JVM tries to allocate memory for an artifact which is required to be allocated in low-memory (because the JVM has only reserved a 32bit pointer for it) it fails and throws an OutOfMemoryError.
Starting in Java 6.0.16.3, Java 6.1.8.3, Java 7.0.8.10, Java 7.1.2.10, there is a parameter -Xmcrs [http://www-01.ibm.com/support/knowledgecenter/SSYKE2_6.0.0/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/xmcrs.html] which allows the JVM to increase the amount of low memory it reserves on startup. With this setting, as long as the low-memory usage by the JVM does not exceed the -Xmcrs value, NOOM in the lower boundary will be avoided.
To set this parameter, first decide what a reasonable value for your lower memory requirements may be. Reasonable value is unique to each environment so there is not a general recommendation.
* -Xmcrs<reasonable_value_for_lower_memory>
*
* NATIVEMEMINFO subcomponent dump routine
*
*
*
*
*
*
*
*
* [/support/docview.wss?uid=swg21660890&aid=2]
*
Disabling Compressed References with -Xnocompressedrefs As a last resort, if the native memory still can not be contained under the 4GB mark, you can set -Xnocompressedrefs [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/appendixes/cmdline/Xnocompressedrefs.html] as a generic JVM argument. [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] Using -Xnocompressedrefs will remove the use of compressed references and therefore remove the lower 4GB memory restriction on the Class Pointers and Monitors/Locks. This will however, result in a significant increase in Java heap memory requirements. It is not uncommon for 70% more heap space to be required. Due to the increased memory requirements it is strongly advised that the Java heap size is adjusted to a larger value and garbage collection is monitored and retuned as required.
Additionally, some benchmarks show a 10-20% relative throughput decrease when disabling compressed references: "Analysis shows that a 64-bit application without CR yields only 80-85% of 32-bit throughput but with CR yields 90-95%. Depending on application requirements, CR can improve performance up to 20% over standard 64-bit." See:ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf].
Before using -Xnocompressedrefs as a solution, first rule out the possibility of a native memory leak. Since using -Xnocompressedrefs will allow the the native memory to grow unbounded, a leak in native memory will lead to process size growth eventually leading to a process that needs to be paged out. The paging will incur performance overhead which will eventually lead to an unstable environment. Therefore careful consideration must be used when selecting -Xnocompressedrefs as a solution.
Memory Map Considerations
The below figure is a generalization of how the JVM handles addresses in each section of the memory map based on heap size and compressed references (CR). Please note that at each stage beyond having all of the Java memory contained below the 4GB mark, there will be performance consequences:
[/support/docview.wss?uid=swg21660890&aid=3]
No Compressed References Overhead using -Xnocompressedrefs
or
-Xmx > 25GB -increased memory footprint
-fewer/larger objects stored on heap leads to more frequent GC
-lower cache and translation look aside buffer (TLB) utilization [/support/docview.wss?uid=swg21660890&aid=4] Compressed References Overhead maximum heap address used by the Java JVM process is below 4GB none maximum heap address used by the Java JVM process is above 4GB but below 32GB compression/decompression of address pointers
Getting Assistance From IBM Support
If further assistance will be required from IBM WebSphere Support, please set the following -Xdump [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/tools/dumpagents_syntax.html] parameters in the generic JVM arguments [http://www-01.ibm.com/support/docview.wss?uid=swg21417365]:
*
*
*
Then restart the JVM and recreate the problem. Once the NOOM is encountered, process the resulting system core with jextract [http://www-01.ibm.com/support/docview.wss?uid=swg21577379]. Send the jextracted core file, heapdump, javacore, snap trace, systemOut.log, native_stderr.log, native_stdout.log and systemErr.log to IBM Support [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] for further analysis.
RELATED INFORMATION
Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]
AIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]
Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]
Compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]
IBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms] | I am running WebSphere App server on 64bit JVM with plenty of free system memory, how come I still get Native OutOfMemory errors (NOOM)? I am running WebSphere App server on 64bit JVM with plenty of free system memory, how come I still get Native OutOfMemory errors (NOOM)? | when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?"
CAUSE
*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack
ex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6.
The IBM JVM will automatically use compressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z/OS)
See Introducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work.
"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits." |
TRAIN_Q055 | IBM Unable to add Centera Device in FileNet Content Engine - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Errors received clicking "Test Connection" when configuring Centera Device in FileNet Enterprise Manager
SYMPTOM
After entering configuration information in FEM Fixed Content Device Wizard the following error is received:
File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $
The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).
Error in the p8_server_error.log:
2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.
com.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={
Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0
Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)
CAUSE
Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded.
ENVIRONMENT
IBM Websphere
DIAGNOSING THE PROBLEM
Following error is received when "Test Connection" is clicked:
File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $
The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).
RESOLVING THE PROBLEM
After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.
Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine
HISTORICAL NUMBER
41550
180
000 | P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider
New P8 CPE 5.2.1 install does not see the Centera Fixed Storage. The following error is returned:
FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. FPLibrary (Not found in java.library.path)
How do I fix this? | After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected. |
TRAIN_Q056 | IBM Automated data collection capability provided by wpcollector tool - United States wpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)
QUESTION
What are the benefits of the wpcollector tool? How do I use this tool?
ANSWER
Wpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support.
Wpcollector is delivered with WebSphere Portal beginning with the 7.0 release. If tracing is required for the problem scenario, you must manually enable traceStrings and recreate the problem PRIOR to running wpcollector.
To run wpcollector, please follow the steps, below:
* If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below:
* If using Microsoft Windows, Unix/Linux, or IBM i, run the following script from the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/PortalServer/bin/ directory to begin the collection: *
*
* Unix/Linux: wpcollector.sh
* i: wpcollector.sh
*
* Tip: To specify the option for collecting files for the Deployment Manager profile, use the "dmgr.root" parameter. For example:
* wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile
* If using IBM z/OS, proceed as follows [../reference/wpsdirstr.html%5C]: *
*
* In the Portal configuration panel, select Collect Diagnostics.
* Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS).
*
* Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.
* Locate the wp.mustgather-<timestamp>.zip file in the <wp_profile_root> [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/reference/wpsdirstr.dita]/filesForAutoPD/ directory and follow the instructions in "Exchanging information with IBM Technical Support for problem determination" [http://www-01.ibm.com/support/docview.wss?uid=swg21153852] to manually FTP the collection to IBM. If using z/OS, there may be additional z/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them.
* If tracing was requested and enabled, please follow the instructions provided by the L2 Support Engineer to disable tracing from the environment
RELATED INFORMATION
Data Collection and Symptom Analysis [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/trouble/tbl_apdt_over.dita?lang=en] | What exactly is "wpcollector" in WebSphere Portal Server? I've been told to get wpcollector output? What exactly is this? | Wpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support. |
TRAIN_Q058 | IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States FIXES ARE AVAILABLE
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]
SUBSCRIBE
You can track all active APARs for this component.
APAR STATUS
* CLOSED AS PROGRAM ERROR.
ERROR DESCRIPTION
* A PFBC file might fail to apply. Wsadmin will show an error
similar to this:
java.lang.Exception: java.lang.Exception: ADMG0660E:
Properties File Validation during command
applyConfigProperties failed. See Report file for details.
The report file will contain an error similar to this:
Error=java.lang.NullPointerException
at
com.ibm.websphere.management.configservice.ConfigServiceHelper.g
etConfigDataType(ConfigServiceHelper.java:235)
at
com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work
spaceHelper.java:563)
at
com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator
(WorkspaceHelper.java:584)
at
com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu
tes(ConfigServiceImpl.java:2102)
at
com.ibm.ws.management.commands.properties.resources.common.Apply
Properties.setProperties(ApplyProperties.java:240)
LOCAL FIX
PROBLEM SUMMARY
* ****************************************************************
* USERS AFFECTED: All users of IBM WebSphere Application *
* Server Property File Based Configuration *
****************************************************************
* PROBLEM DESCRIPTION: A Property File Based Configuration *
* (PFBC) file might fail to apply. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A recent (8.5.5.5) parser change introduced a problem where
types that have default values noted in the file and are not
Strings can be incorrectly processed. For example:
isolatedClassLoader=false #boolean,default(false)
might be incorrectly processed, and as a result, the file
might not apply.
PROBLEM CONCLUSION
* The parsing code is updated so the problem no longer occurs.
The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.6. Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]
TEMPORARY FIX
COMMENTS
APAR INFORMATION
* APAR NUMBER
PI37248
* REPORTED COMPONENT NAME
WEBS APP SERV N
* REPORTED COMPONENT ID
5724H8800
* REPORTED RELEASE
850
* STATUS
CLOSED PER
* PE
NoPE
* HIPER
NoHIPER
* SPECIAL ATTENTION
NoSpecatt / Xsystem
* SUBMITTED DATE
2015-03-18
* CLOSED DATE
2015-03-20
* LAST MODIFIED DATE
2015-03-24
* APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:
* APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:
FIX INFORMATION
* FIXED COMPONENT NAME
WEBS APP SERV N
* FIXED COMPONENT ID
5724H8800
APPLICABLE COMPONENT LEVELS
* R850 PSY
UP | Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written | The parsing code is updated so the problem no longer occurs.
The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.6. |
TRAIN_Q059 | IBM Removing a failed install from the ITM i5/OS agent - United States i5 removal TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
If an ITM i5/OS agent DLTLICPGM 5724C04 command fails then we have to remove the various parts of the agent that have been installed. This has to be done by hand because the DLTLICPGM 5724C04 command will fail as the unistall encounter some issues during uninstall. This technote will show how to do it.
SYMPTOM
RSTLICPGM command fails to install the ITM i5/OS agent.
DLTLICPGM 5724C04 command fails to uninstall the agent
CAUSE
RSTLICPGM/DLTLICPGM 5724C04 command failed to finish correctly and leaves the agent in an unknown state.
ENVIRONMENT
IBM i / i5/OS machines
DIAGNOSING THE PROBLEM
RSTLICPGM and DLTLICPGM 5724C04 fail for the i5 agent.
RESOLVING THE PROBLEM
To delete the ITM i5/OS agent do the following :-
First try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do
the following i5/OS commands :
DLTLIB QAUTOMON
DLTLIB QAUTOTMP
DLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.
start qsh
delete /QIBM/USERDATA/IBM/ITM and all sub directories in it.
delete /QIBM/PRODDATA/IBM/ITM and all sub directories in it.
Retry the RSTLICPGM commands specified in the user guide.
http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/osibmi/pcinstall_a4_ug.htm?lang=en [http://www-01.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/osibmi/pcinstall_a4_ug.htm?lang=en]
PRODUCT ALIAS/SYNONYM
ITM OS/400 agent
ITM i5/OS agent
ITM IBM i agent
5724C04 | Uninstalling I5 OS agent failed
I need to uninstall the I5OS agent before reinstalling a newer release of the same.
Command: DLTLICPGM LICPGM(5724C04)
is anyway failing and I don't know how to proceed further.
Can you please let me know the manual steps to uninstall the i5OS agent correctly ? | To delete the ITM i5/OS agent do the following :-
First try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do
the following i5/OS commands :
DLTLIB QAUTOMON
DLTLIB QAUTOTMP
DLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.
start qsh
delete /QIBM/USERDATA/IBM/ITM and all sub directories in it.
delete /QIBM/PRODDATA/IBM/ITM and all sub directories in it.
Retry the RSTLICPGM commands specified in the user guide. |
TRAIN_Q060 | IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States TECHNOTE (FAQ)
QUESTION
What can cause an STAP to fail to connect properly - I get the following messages in the logs:-
/tmp/guard_stap.stderr.txt on the DB Server :-
"Server <ip_addr> wasn't heard from for nn sec during this attempt (nnn sec total), closing and re-opening"
and from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log
"Unauthorized client connecting from <ip_addr> ,rejecting"
CAUSE
One reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance like this :-
[/support/docview.wss?uid=swg22009818&aid=1] [/support/docview.wss?uid=swg22009818&aid=1]
ANSWER
Uncheck the Approval box and the S-TAPs should start connecting .
[/support/docview.wss?uid=swg22009818&aid=2] [/support/docview.wss?uid=swg22009818&aid=2] | Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc
Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc
I get the following messages in the logs:-
/tmp/guard_stap.stderr.txt on the DB Server :- "Server wasn't heard from for nn sec during this attempt nnn sec total), closing and re-opening"
and from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log "Unauthorized client connecting from ,rejecting"
What is the reason? | One reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance |
TRAIN_Q062 | IBM Minimum authorization required for SAP agent logon userid - United States authorization minimum IBMMON_AGENT profile settings agent userid SAP MySAP /IBMMON/AUTH TECHNOTE (FAQ)
QUESTION
What are the minimum authorizations required for the userid used by the ITM MySAP agent to logon a SAP system?
ANSWER
By default, the MySAP agent uses the userid IBMMON_AGENT, that is created when ITM transport are imported in the SAP system, together with /IBMMON/AUTH role and profile.
If you don't want to use the default userid and profile, you need to create your own userid and provide it with a set of minimum required authorization settings.
Depending on the transport level, the required authorization may vary, but you can always refer to the values specified for the /IBMMON/AUTH profile available in the transport.
By looking at this profile, you can obtain the needed authorization information.
In example, for MySAP agent 6.2 IF16, those are the authorization defined for the /IBMMON/AUTH profile:
[/support/docview.wss?uid=swg21657458&aid=1] [/support/docview.wss?uid=swg21657458&aid=1]
You need to define your own userid providing the same set of authorization showed for the /IBMMON/AUTH profile to have mySAP agent performing successful data collection even using a non-default userid.
PRODUCT ALIAS/SYNONYM
IBM Tivoli Monitoring MySAP Agent 6.2 | SAP Agent user authorizations
Hello, I cannot use the default SAP user IBMMON_AGENT provided by the SAP Agent transport. Internal rules requires to create a new user respecting specific naming convention. I know how to do it but I don't know the authorization I need to assign to the new user. Where can I find them ?
Thanks | By default, the MySAP agent uses the userid IBMMON_AGENT, that is created when ITM transport are imported in the SAP system, together with /IBMMON/AUTH role and profile.
If you don't want to use the default userid and profile, you need to create your own userid and provide it with a set of minimum required authorization settings.
Depending on the transport level, the required authorization may vary, but you can always refer to the values specified for the /IBMMON/AUTH profile available in the transport.
By looking at this profile, you can obtain the needed authorization information. |
TRAIN_Q063 | IBM Operational Decision Manager V8.5.1.2 Fix Pack - United States DOWNLOADABLE FILES
ABSTRACT
This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2.
DOWNLOAD DESCRIPTION
This fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.5.1 can use this fix pack.
How to install the fix pack
If you are not installing both Operational Decision Manager components, skip the instructions regarding Decision Center or Decision Server.
1. For Decision Center, download 8.5.1-WS-ODM_DC-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.)
2. Extract the archive to a new folder, named WDC.
3. For Decision Server, Download 8.5.1-WS-ODM_DS-<OS>-FP002.zip, and extract its files. (Change <OS> to match your platform: AIX, HPUX, LINUX, OS400, SOLARIS, ZOS, or WIN32.)
4. Extract the archive to a new folder, named WDS.
Installing by using IBM Installation Manager: 1. Launch IBM Installation Manager.
2. In the toolbar menu, open File > Preferences and do the following:
3. Select repositories.
4. For Decision Center, click Add Repository.
5. Browse to the extracted folder WDC\updates.
6. Select the file repository.config.
7. For Decision Server, click Add Repository.
8. Browse to the extracted folder WDS\updates.
9. Select the file repository.config.
10. Make sure the repositories are selected in the Repositories list.
11. Click Apply to save your changes, and click OK to close the Repositories list.
12. Click Update to update your installation.
13. Follow the instructions in the installation manager to complete the installation.
Installing by using the Installation Manager command line: 1. Locate the imcl command under <IM installation>/eclipse/tools.
2. Run the commandimcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense.
* Use the option -installDirectory <install path of ODM 8.5.1> to update a specific installation.
* If you update only Decision Server or Decision Center, specify the repository accordingly.
Applying the fix pack
After you install the fix pack, you might have to do additional steps to apply the fix pack in your environment. To complete the update, see When and how to apply a modification or fix pack [http://www-01.ibm.com/support/docview.wss?uid=swg21665766].
Warning:
If you have installed interim fixes for Operational Decision Manager V8.5.1, you must uninstall the fixes before you can install this fix pack. You must also stop the Operational Decision Manager sample server for this installation. If you do not uninstall the fixes and stop the server, the installation of the fix pack fails. If you attempt to install the fix pack without uninstalling the interim fixes, the installer uninstalls the interim fixes before the installer fails. In this case, stop the sample server and restart the installation. INSTALLATION INSTRUCTIONS
Follow the instructions provided in the following resources:
DOWNLOAD PACKAGE
PROBLEMS SOLVED
Fix List for IBM Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg27023767]
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs]
What is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] ODM 8.5.1.0 AIX 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=AIX&function=all] [ ] DD ODM 8.5.1.0 HPUX 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=HPUX&function=all] [ ] DD ODM 8.5.1.0 Linux PPC 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+PPC&function=all] [ ] DD ODM 8.5.1.0 Linux x86 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+x86&function=all] [ ] DD ODM 8.5.1.0 Linux zSeries 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Linux+zSeries&function=all] [ ] DD ODM 8.5.1.0 OS/400 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=OS/400&function=all] [ ] DD ODM 8.5.1.0 Solaris 32-bit SPARC 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+32-bit,SPARC&function=all] [ ] DD ODM 8.5.1.0 Solaris 64-bit SPARC 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+64-bit,SPARC&function=all] [ ] DD ODM 8.5.1.0 Solaris 32-bit x86 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+32-bit,x86&function=all] [ ] DD ODM 8.5.1.0 Solaris 64-bit x86 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Solaris+64-bit,x86&function=all] [ ] DD ODM 8.5.1.0 Windows 30 Jan 2015 Language Independent 4000000000 FC [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.0&platform=Windows&function=all] [ ] DD
[/support/docview.wss?uid=swg24039235&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039235&aid=2]Problems (APARS) fixed
PI31830, PI31844, RS01612, RS01617, RS01630, RS01631, RS01635, RS01641, RS01645, RS01646, RS01653, RS01661, RS01664, RS01667, RS01668, RS01669, RS01670, RS01671, RS01680, RS01682, RS01683, RS01685, RS01686, RS01689, RS01690, RS01693, RS01694, RS01695, RS01697, RS01698, RS01700, RS01704, RS01707, RS01708, RS01709, RS01710, RS01711, RS01712, RS01714, RS01715, RS01716, RS01718, RS01720, RS01723, RS01725, RS01728, RS01733, RS01734, RS01735, RS01737, RS01743, RS01744, RS01748, RS01750, RS01751, RS01752, RS01754, RS01755, RS01760, RS01763, RS01768, RS01770, RS01774, RS01775, RS01779, RS01784, RS01790, RS01792, RS01793, RS01794, RS01795, RS01796, RS01798, RS01801, RS01804, RS01806, RS01809, RS01811, RS01813, RS01814, RS01817, RS01818, RS01819, RS01821, RS01824, RS01825, RS01827, RS01828, RS01831, RS01832, RS01850, RS01853, RS01854, RS01855, RS01856, RS01858, RS01859, RS01860, RS01862, RS01699 | How to get the ODM 8.5.1.2 fixpack of ODM 8.5.1.1? ODM 8.5.1.2 fixpack is not listed in Fix Central when installed platform ODM 8.5.1.1 is used: http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Operational+Decision+Management&release=8.5.1.1&platform=All&function=all | This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2. |
TRAIN_Q064 | IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems - United States RELEASE NOTES
ABSTRACT
IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems
CONTENT
WebSphere Application Server 8.5.5 announced IBM WebSphere SDK Java Technology Edition 8.0 as an option for Java.
* Liberty added support in fix pack 5
* WebSphere Application Server traditional added support for installing this SDK as an extension in 8.5.5.9 * In 8.5.5.11 and later, this SDK is available as an option on new installations.
* In 8.5.5.14 and later, it is planned that this SDK will be required for all new installations and all updates (fixpacks).
The following are the minimum supported OS levels for IBM WebSphere SDK Java Technology Edition 8.0 in WebSphere Application Server. Action Required:
*
*
* .0
*
Operating System minimums:
* AIX
* AIX 6.1 TL7
AIX 7.1 TL3
* HP-UX IA64
* HP-UX 11i v3 (11.31)
* IBM i
* IBM i V7R1
* Linux
* RedHat Enterprise Linux 6
RedHat Enterprise Linux 7
SLES 11.1 (SP1)
SLES 12
Ubuntu 12.04 LTS
Ubuntu 14.04 LTS
Ubuntu 16.04 LTS
* Windows
* Windows 7 service pack 1
Windows 8 (not Metro)
Windows Server 2012
Windows Server 2016
* Solaris
* Solaris 11
* z/OS
* z/OS 1.13
z/OS 2.1
z/OS 2.2
Component specific notes: * WebSphere Application Server installations between 8.5.5.11 and 8.5.5.14 require an explicit user selection to determine the default IBM WebSphere SDK Java Technology Edition on new installations.
* IBM HTTP Server and the Webserver Plug-in between 8.5.5.11 and 8.5.5.14 defaults to IBM WebSphere SDK Java Technology Edition 8.0. No explicit selection is required. These components do not use Java at runtime. | Support of RHEL 5.8 and Liberty 8.5.5.11 with JAVA 8.0 We are running RHEL 5.8 and 5.11 with Liberty 8.5.5.11 and want to run JAVA 8.0 . Is it Supported ? | Operating System minimums:
* AIX
* AIX 6.1 TL7
AIX 7.1 TL3
* HP-UX IA64
* HP-UX 11i v3 (11.31)
* IBM i
* IBM i V7R1
* Linux
* RedHat Enterprise Linux 6 |
TRAIN_Q065 | IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States verbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)
QUESTION
How can I write verbose gc output to a log file other than the native_stdout?
CAUSE
By default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.
ANSWER
WAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):
Solaris:
Add the following parameters to the generic JVM arguments:
-XX:+PrintGCDetails
-XX:+PrintGCDateStamps
-XX:+PrintHeapAtGC
-Xloggc:/tmp/gc.log
To enable log file rotation:
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10
-XX:GCLogFileSize=10M
notes:
-Xloggc:<fileName>
* ex: -Xloggc:/tmp/gc.log
-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc
-XX:NumberOfGClogFiles= <num_of_files> * Set the number of files to use when rotating logs, must be >= 1. The rotated log files will use the following naming scheme, <filename>.0, <filename>.1, ..., <filename>.n-1.
-XX:GCLogFileSize=<number>K (or M) * The size of the log file at which point the log will be rotated, must be >= 8K.
HP:
Add the following parameters to the generic JVM arguments:
-XX:+PrintGCDetails
-XX:+PrintGCDateStamps
-XX:+PrintHeapAtGC
-Xverbosegc:file= /tmp/gc_pid$$.vgc
To enable log file rotation:
-XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=10
-XX:GCLogFileSize=10M
note : $$ maps to the PID of the java process RELATED INFORMATION
6941923 : RFE: Handling large log files produced by lon [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6941923]
Enabling verbose garbage collection (verbosegc) in WebS [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21114927]
Where to set generic JVM arguments in WebSphere Applica [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365]
Verify Java SDK version shipped with IBM WebSphere Appl [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27005002]
HP-UX Java 6.0.18 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03119431/c03119431.pdf]
HP-UX Java 7.0.05 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03123467/c03123467.pdf]
Oracle - Java HotSpot VM Options [http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html] | For Solaris how to write verbose gc output to a log file other than the native_stdout? A customer asked why no gc logs generated even if they use the -Xverbosegc option. So How can I write verbose gc output to a log file other than the native_stdout for SunOS? | Add the following parameters to the generic JVM arguments:
-XX:+PrintGCDetails
-XX:+PrintGCDateStamps
-XX:+PrintHeapAtGC
-Xloggc:/tmp/gc.log |
TRAIN_Q066 | IBM Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002) - United States DOWNLOADABLE FILES
ABSTRACT
This fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC little-endian Log File agent. In addition, it resolves the APARs and defects listed below.
DOWNLOAD DESCRIPTION
(C) Copyright International Business Machines Corporation 2017.
All rights reserved.
Component: Tivoli® Log File Agent,
Version 6.3.0
Component ID: 5724C04LF
Fix Pack: 0002, 6.3.0-TIV-ITM_LFA-FP0002
Date: September 19, 2017
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 fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC
little-endian Log File agent. In addition, it resolves the APARs and
defects listed in the "Problems Fixed" section below and includes the
superseded fixes listed in section 2.4.
2.0 Problems fixed
============
The following problems are addressed by this fix.
2.1 APARs
-------------
APAR: IV96363
Abstract: AGENT CRASHES ON WINDOWS 2016 WHILE READING LOG
Additional information: The agent crashes when a second file close
attempt follows a successful close of the monitored log.
Any subsequent I/O operations, such as fseek, fgets, fclose,
etc, either on that thread or another thread using the same
file handle may result in a failure or a crash because the
file is no longer open or the handle is invalid. The failure
sometimes results in an fgetpos failure with "errno 9 'Bad
file descriptor'" and returns with a -1.
This has been seen more prevalently on Windows 2016 but
might occur on other platforms. This is related to IV60331.
On the agent system, with a minimum of the following trace:
"ERROR (UNIT:kumpfile ALL) (UNIT:kum0fdp0 ALL)" enabled, the
agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows trace points similar to the following:
- - -
...
...:kum0fdp0.c,76,"KUM0_FileClose") IOE 5619070 file handle
7C3AB428 File close successful
...:kum0fdp0.c,111,"KUM0_FileClose") SEptr 5613548 local file
D:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070
7C3AB428 closed unsuccessfully
...:kum0fdp0.c,82,"KUM0_FileClose") File close failed for IOE
@5619070, status code -1, errno 0 'No error'
...:kum0fdp0.c,111,"KUM0_FileClose") SEptr 5613548 local file
D:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070
7C3AB428 closed unsuccessfully
...
- - -
APAR: IV95005
Abstract: "DETECTED CODEPAGE CP943, USING CP932 INSTEAD TO MAP
BACKSLASH TO U+005C, NOT U+00A5 (YEN SYMBOL)" LOGGED ON
EVERY READ
Additional information: With a locale of Ja_JP (Shift-JIS) and
ERROR level trace, when the data is in the local code page,
the following message appears in agent RAS1 log for each
monitored event processed:
"Detected codepage CP943, using CP932 instead to map
backslash to U+005C, no U+00A5 (Yen symbol)".
This occurs on the agent system, with only ERROR trace
enabled. The agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
kum0nget.c,438,"TranslateStringToUTF8") Detected codepage
CP943, using CP932 instead to map backslash to U+005C, not
U+00A5 (Yen symbol)
...
- - -
APAR: IV93401
Abstract: USING REGEXLOGSOURCES TO MONITOR A REMOTE FILE FAILS
WITH FILE NOT FOUND
Additional information: Using RegexLogSources to monitor a remote
file fails with "*** Unable to obtain statistics for file
</LFA_test_logs/test_1.log> errno 2 'No such file or
directory". This occurs right after the file has been found
and matched. (Note: if the monitored file is also found
locally, it will succeed and monitor the local file.)
Using the same file in LogSources results in a match.
On the agent system, with a minimum of the following trace:
"ERROR (UNIT:kumpdcm2 ALL) (UNIT:kum0dir ALL)" enabled, the
agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:kumpdcm2.c,195,"KUMP_GetNextMember") Directory 7F3B3401C380
/LFA_test_logs matched <test_1.log> to pattern <^test_1.log$>
...:kumpdcm2.c,211,"KUMP_GetNextMember") Directory handle
7F3B3401C380
name /LFA_test_logs successfully matched <test_1.log> to pattern
<^test_1.log$>
...:kumpdcm2.c,217,"KUMP_GetNextMember") Exit: 0x0
...:kumpdcm2.c,301,"KUMP_GetNextMemberDouble") Retcode 0
Directory
/LFA_test_logs Member <test_1.log> matched ^test_1.log$
...:kumpdcm2.c,330,"KUMP_GetNextMemberDouble") Directory
7F3B3401C380
/LFA_test_logs member successfully matched <test_1.log> pattern
<^test_1.log$>
...:kumpdcm2.c,335,"KUMP_GetNextMemberDouble") Exit: 0x0
...:kum0dir.c,143,"KUM0_stat_withMsgFlag") *** Unable to obtain
statistics for file </LFA_test_logs/test_1.log> errno 2 'No such
file or directory'
...:kum0dir.c,192,"KUM0_stat_withMsgFlag") Unsuccessfully stat
file
/LFA_test_logs/test_1.log size=0 access time=0, modification
time=0,
creation time=0
...:kumpdcm2.c,481,"KUMP_DetermineCurrentMonitorFileNameStrict")
File
/LFA_test_logs/test_1.log skipped, stat failed -1
...
- - -
APAR: IV89574
Abstract: INVALID CHARACTERS SEEN IN THE TRACE "*****Error:
u_strFromUTF8 failed for string ... - <filename> .........,
status 10 <U_INVALID_CHAR_FOUND>"
Additional information: In the agent RAS1 log, the trace points
"*****Error: u_strFromUTF8 failed for string ..... -
<filename> ..., status 10 <U_INVALID_CHAR_FOUND>" and
"*****Error: uregex_setText failed..." contain garbled or
invalid characters. The garbled characters are not in the
events themselves.
Since these messages might occur when the agent is processing
a directory listing in order to determine the current file
to monitor as a result of a wildcard character in the
RegexLogSources parameter, if the <filename> that results
in this error is a file that should be monitored, then events
would be lost as the file is not monitored. The <filename>
is in the directory for RegexLogSources. The additional
invalid characters are not seen in the file listing on the
system.
This was discovered on Log File Agent V6.3 and later on
Windows, but also occurs on UNIX.
On the agent system, with a minimum of the following
trace enabled: "ERROR (UNIT:kum0regx ALL)", the agent RAS1
log <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows trace points similar to the following with some extra
characters added ".lnk":
-----
...:kum0regx.c,286,"KUM0_IsRegExPatternMatch")
*****Error: u_strFromUTF8 failed for string ä«ä¨äOäèäìäjäì -
änäfäîän .lnkÙl ÙsÙw pRegEx @4D05810 status 10 <U_INVALID_CHAR_FOUND>
---
APAR: IV79204
Abstract: LOGS RE-READ FROM THE BEGINNING WHEN DAYLIGHT SAVING
TIME (DST) ENDS
Additional information: On Windows systems, when daylight saving
time ends, log files might be re-read from the beginning
resulting in old events being re-sent. This only occurs
when time is set back.
The agent falsely detects that the configuration (.conf)
and format (.fmt) file have changed when the system is
configured to "Automatically adjust clock for Daylight
Saving time" and the file timestamps automatically change
triggering an agent reset. When NumEventsToCatchUp is set
to -1, this series of events causes the log file to be
re-read from the beginning. This was seen with IF0003 and
IF0004 when monitoring log files on Windows operating
systems, but not with the Windows Event log. This problem
did not occur on UNIX systems.
To resolve this issue you must install and use the Windows
WIX64 (x86-64 bit) agent or specify NumEventsToCatchUp=-2
in the configuration file as a work-around.
APAR: IV77403
Abstract: WINDOWS EVENT LOG EVENTS ARRIVED DELAYED WHEN
NUMEVENTSTOCATCHUP IS USED
Additional information: With a large input load (for example,
8004 events on each of 4 threads), Windows Event Log events
arrive with a significant delay when NumEventsToCatchUp=-1
is set in the conf file. The delay increases as the event
backlog grows. It can be in the order of 5 minutes depending
on CPU, etc. This is a result of the inherent overhead in
maintaing the position (bookmark) in the Windows Event Log
when NumEventsToCatchUp is set to -1 or n.
This is a follow-on to APAR IV63704.
APAR: IV76731
Abstract: UNABLE TO RENAME FILE WHICH IS BEING MONITORED BY ITM
LOG FILE AGENT
Additional information: On Windows systems, when the agent is
monitoring an application log, the log file cannot be
renamed because the file is open or in use. When new
records are added to the log, the agent opens the log,
reads the log and closes the log. However, when a large
volume of events are written to the log file, the log file
may remain open or in use due to operating system
efficiencies. As a result, an attempt to rename the log
file may fail. This problem occurs more prevently with the
WINNT 32-bit agent, when NumEventsToCatchUp is set to -1.
To minimize occurrence of this issue, use the Windows (WIX64)
x86-64 bit Log File agent.
APAR: IV60331
Abstract: RESETTING OF MULTIPLE CONF/FORMAT FILES CAUSES A CRASH
Additional information: Updating multiple configuration (.conf)
or format (.fmt) files, usually via a script or a situation
that runs frequently, and causes the agent to reset might
result in a core or crash. This also might be more likely
to occur with multiple subnodes to monitor a large number
of files, for example, 100 files. The root cause of the
crash is closing a file which is already closed or no longer
exists.
This has been seen, mainly on Linux, on agent start-up,
shutdown or reset as a result of configuration file changes.
The problem was originally discovered in Log File Agent
v6.2.3.1.
The <hostname>_lo_<#########>.log might contain information
similar to the following:
*** glibc detected *** /opt/IBM/ITM/lx8266/lo/bin/kloagent:
double free
or corruption (out): 0x00007f222d727030 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3c158760e6]
/lib64/libc.so.6[0x3c15878c13]
/lib64/libc.so.6(fclose+0x14d)[0x3c1586674d]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(kum_fclose+0x97)[0x7f222
42a68db]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseIOResources+
0x430)[0x7f2224275444]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseSourceResour
ce+0xae1)[0x7f22242799d1]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_FileServer+0x7114)[
0x7f2224250f30]
/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(+0xb9b56)[0x7f222427fb56
]
/lib64/libpthread.so.0[0x3c16007851]
/lib64/libc.so.6(clone+0x6d)[0x3c158e890d]
. . .
2.2 Defects
--------------
None.
2.3 Enhancements
----------------------
Enhancement: IV77403, IV76731
Abstract: Add Support for Windows x86-64 bit (WIX64) Agent
Additional Information: Support was added for Windows x86-64 bit
(WIX64) agent. This addresses APARs IV76731 and IV77403.
Enhancement: 216440
Abstract: Add Support for PowerPC little-endian (PPCLE)
Additional Information: Support was added for PowerPC little-endian.
2.4 Superseded fixes
-------------------------
6.3.0-TIV-ITM_LFA-FP0001
6.3.0-TIV-ITM_LFA-IF0005
6.3.0-TIV-ITM_LFA-IF0004
6.3.0-TIV-ITM_LFA-IF0003
6.3.0-TIV-ITM_LFA-IF0002
6.3.0-TIV-ITM_LFA-IF0001
2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.3.0-TIV-ITM_LFA-FP0001
------------------------
APAR: IV82875
Abstract: WINEVENTLOG REREAD FROM BEGINNING ON AGENT RESTART
Additional information: When monitoring Windows® Event Logs, the
event log is re-read from the beginning when the agent is
restarted, resulting in old events being sent. This occurs
on Microsoft Windows 2003 or 2008 systems with the following
settings in the agent configuration file:
- WINEVENTLOGS=<named event logs>
- NumEventsToCatchUp=-2
- UseNewEventLogAPI=n (must be set on Windows 2008 systems)
Note: NumEventsToCatchUp=-2 is not supported for Windows
Event logs.
Problem Determination: On the LO agent system, with a
minimum of the following trace specification:
KBB_RAS1: ERROR (UNIT:WinLogQuery ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:winlogqueryclass.cpp,2521,"WinLogQueryClass::
EventStartInit") WARNING: numEventsToCatchUp is -2 but
there aren't that many events. Starting with oldest instead
...
- - -
APAR: IV82170
Abstract: SOME EVENTS ARE NOT DETECTED WHEN BOTH MULTI-LINE AND
SINGLE-LINE FORMATS ARE USED
Additional information: When using a format file which contains
both multi-line and single line formats, some events might
not be detected and are discarded. In this case, the events
which were discarded were single lines of data which matched
the single line formats. The single lines were discarded
because the number of lines remaining to be processed was
less than or equal to (not greater than) the maximum number
of lines in the multi-line format.
This problem was discovered using errpt, but it can occur
with other pipes such as syslog, or with a monitored file.
It occurs on Log File Agent V6.3, up to Interim Fix 0005
and is platform independent.
Problem Determination: On the LO agent system, with a
minimum of the following trace specification:
KBB_RAS1: ERROR (UNIT:logmonitor ALL)(UNIT:kumrmfr ALL)(UNIT:kumpfile ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
all the lines are read into the buffer properly. Records
are processed until the ReadCount is equal to the
AttributeSetCount, and then the next "File Data Record" is
empty, even though more unprocessed data was still in the
buffer.
- - -
...
...:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRecord")
<0x1111746D0,0x2FF>
...
...:kumprmfr.c,454,"KUMP_ReadMonitorFileUnicodeRecord") Read
767 bytes :
Elapsed Time: 0.000425 sec CPU Time: 231 usec
...
...
...
...:kumprmfr.c,1112,"KUMP_ReadMonitorFileUnicodeRecord")
DlmRecordMode 0 ReadCount 5 DlmRecordDetected 0 PEptr @11103E450
ShutDownPending 0 AttributeSetCount 5 RecordSetWaitCount 0
FileMonitorFrequency 5
...
...:kumprmfr.c,1153,"KUMP_ReadMonitorFileUnicodeRecord")
File EOF switch set
...:kumprmfr.c,1182,"KUMP_ReadMonitorFileUnicodeRecord") Exit:
0x111941E8
...:kumpfile.c,594,"KUMP_FileServer") <0x1111941E8,0x0>
File Data Record:
...
- - -
APAR: IV81364
Abstract: PROCESS PRIORITY CLASS SETTINGS NOT REFLECTED OR SET
FOR LOG FILE AGENT PROCESS
Additional information: After configuring the Process Priority
class value, the agent process running on Red Hat Linux
does not set the corresponding priority or niceness value
for its process. The priority is set on the thread and not
the process (PID).
For example, after configuring the agent and setting the
ProcessPriorityClass in the configuration file or during
configuration to "D":
When the ps command is issued, the priority of the agent
process remains same:
# ps -eo priority,nice,comm,args,pid,time | grep kloagent
20 0 kloagent /opt/IBM/ITMfLFA/lx8266/lo/ 27424
00:00:00
Problem Determination: On the LO agent system, with a
minimum of the following trace specification:
KBB_RAS1= ERROR (UNIT:logmonitor ALL) (UNIT:Utilities ALL)
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:logmonitorqueryclass.cpp,479,"setProcessPriority") New*
conf file = /opt/IBM/ITM/config/test_lo.conf , fmt file =
/opt/IBM/ITM/config/test_lo.fmt in subnode NULL
...:logmonitorqueryclass.cpp,490,"setProcessPriority") New*
ProcessPriorityClass setting D found.
...:logmonitorqueryclass.cpp,532,"setProcessPriority") New*
set process priority value -5
...:utilities.cpp,517,"Utilities::setPriority") Active RAS1
Classes: EVERYT EVERYE EVERYU
...:utilities.cpp,517,"Utilities::setPriority") Entry
...:utilities.cpp,540,"Utilities::setPriority") Successfully
set process priority to fffffffb
...:utilities.cpp,554,"Utilities::setPriority") Exit: 0x0
...
- - -
Feature: 216423
Abstract: Add support for Linux PowerPC (lpp266)
Additional Information: The agent is now supported running on
Linux PowerPC Red Hat 7.1.
Feature: 216820
Abstract: Upgrade to Installer v6.2.3 FP0005
Additional Information: Upgrade to an Installer which contains
installer APAR IV67172 and provisional APAR IV65616 for
Red Hat Linux v7 support.
The following error might have been seen when running
install.sh:
================================================
ITM home directory "/opt/IBM/ITM" already exists.
OK to use it [ 1-yes, 2-no; "1" is default ]? 1
cut: fields and positions are numbered from 1
Try 'cut --help' for more information.
install.sh failure: KCI0766E could not find arch "" in a JRE version file.
================================================
6.3.0-TIV-ITM_LFA-IF0005
------------------------
APAR: IV78340
Abstract: EVENT ARRIVAL DELAYED DUE TO CPU THROTTLING
Additional information: After a system reboot which includes
automatic start-up of a Log File Agent instance, events
become increasingly delayed from minutes to as much as hours.
The root cause of the delay is the CPU throttling, which
occurs even when the Process maximum CPU percentage is
configured at 100%, the default which indicates no CPU
throttling, because at that point internally the maximum CPU
is reset to zero. This can occur with only a light flow rate
of events.
It was discovered on HP-UX and although, it is platform
independent, it may be more prevalent on HP-UX.
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1=ERROR (UNIT:kumpcpu ALL) (UNIT:kumpscan ALL)
(UNIT:kumpinit ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
...:kumpcpu.c,634,"KUMP_hpux_getcpucputime") cycles t 0
277079589 u 0 0 s 0 0 i 0 0 u 0 210142401 s 0 50284806 i 0
16652382
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 692698
second 0 277079589; first 0 0
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 692698
second 0 277079589; first 0 0
...:kumpcpu.c,486,"KUMP_GetCPUTimeDiff") cpu time diff 2003
second 0 277079589; first 0 276278019
...:kumpcpu.c,332,"KUMP_UpdateProcessTime") Process utilization
0.000000%; Changing the dampening wait from 0 milliseconds to 1
milliseconds
...
- - -
APAR: IV76119
Abstract: REMOVAL OF RC4 CIPHER FROM REMOTE MONITORING
Additional information: The arcfour (RC4) cipher algorithm, as used
in the TLS protocol and SSL protocol, could allow a remote
attacker to obtain sensitive information. Successful
exploitation could allow an attacker to retrieve sensitive
information. This vulnerability is commonly referred to as
"Bar Mitzvah Attack" (CVE-2015-2808). Support for the arcfour
cipher is being removed.
APAR: IV75776
Abstract: UNABLE TO OBTAIN MONITORED FILE STATISTICS ERROR WHEN FILE
NAME CONTAINS DOUBLE-BYTE CHARACTERS
Additional information: When monitoring a file which contains
Japanese or double-byte characters in the filename, the
message "Unable to obtain statistics for file < <filename> >
errno 2 'No such file or directory'" is written to the agent
log at approximately every poll interval cycle. However, the
file exists and is correctly monitored.
This occurs on Log File Agent version 6.3.0 and is platform
independent.
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1=ERROR (UNIT:kum0dir ALL)", the agent RAS1
log <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
...:kum0dir.c,147,"KUM0_stat_withMsgFlag") *** Unable to obtain
statistics for file <C:/temp/[filename].log> errno 2 'No such
file or directory'
...:kum0dir.c,167,"KUM0_stat_withMsgFlag") Unsuccessfully stat
file C:/temp/[filename].log size=0 access time=0, modification
time=0, creation time=0
...
- - -
APAR: IV75603
Abstract: BACKSLASH \ INCORRECTLY TRANSLATED ON WINDOWS WHEN SENT
TO EIF
Additional information: On Windows systems when the event is
translated back from UTF-8 to the native code page shift-JIS
(SJIS/943), in order to send the event to Event Integration
Facility (EIF), the backslash character is incorrectly
translated. The backslash character (0x5c) is translated to
UTF-8 0xC2A5, and when it is translated back to the native
code page, it is incorrectly translated to 0x1A which may
show as a blank space or unprintable character. As a result
of IV68698, code page 932 is used to translate the event to
UTF-8, however code page 943 is still being used to translate
the event from UTF-8 back to the native code page Shift-JIS.
Example:
Log File Agent v6.3 GA <cache file>
70203_Base;msg='Tivoli [message]\[message]'
Log File Agent v6.3 and 6.3.0-TIV-ITM_LFA-IF0004
<cache file>
70203_Base;msg='Tivoli [message] [message]'
APAR: IV75336
Abstract: LFA ASSOCIATED WITH LOG ANALYSIS IS DROPPING EVENTS
Additional information: The agent when associated with Log
Analysis is dropping events. When sending large amounts of
events to Event Integration Facility (EIF), the agent is
unable to keep up. The message "WARNING: <1000> events
already on queue, dropping the oldest one", where <1000>
is the default MaxEventQueueDepth value, is seen in the
agent RAS1 log.
APAR: IV74487
Abstract: ABLE TO MONITOR FILES GREATER THAN 2GB ON 32-BIT
LINUX
Additional information: When attempting to monitor files greater
than 2 gigabytes on a 32-bit Linux operating system, the
file is not monitored and is not displayed in the Monitored
File Workspace in the portal. A trace in the log shows
"File too large".
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1: ERROR (UNIT:kum0fdp0 ALL) (UNIT:kumpstdio
ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following:
- - -
...
<timestamp>:kumpwfrm.c,261,"KUMP_WaitFileReadyForMonitor") ***
Unable to open file local file <filename...>,
Errno: 27, ErrorText: File too large, NO retry. Exiting
...
- - -
APAR: IV74480
Abstract: COMPAREBYLASTUPDATE DOES NOT MONITOR THE MOST RECENT
REMOTE FILE ACROSS MULTIPLE DIRECTORIES
Additional information: When monitoring a remote log file using
regular expression meta characters (wildcard) in one directory
pattern of the path, and using the FileComparisonMode of
"CompareByLastUpdate", the most recent file from the most
recent directory is not monitored. Only the most recent
file in the first directory returned which matches the
pattern, is monitored.
CompareByLastUpdate should monitor the file with the most
recent last update timestamp across all the directories.
This occurs on Log File Agent version 6.3.0 and appears to
be platform independent. It does not occur for local files.
Problem Determination: With a minimum of the following trace
enabled: "KBB_RAS1: ERROR (UNIT:kum0sshlib ALL) (UNIT:kumpdcm ALL)",
the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace points similar to the following, where
'test0420' is not the last or only directory to search:
- - -
...
<timestamp>:kumpdcm2.c,214,"KUMP_GetNextMember") Directory
handle 7FF138015DA0 name /<...>/pm_20150424 could not find any
(more) members to match pattern <^.*\.log$>
...
...
<timestamp>:kum0sshlib.c,2184,"ssh_session_sftp_readdir")
Invalid data connInfo 7FF13800AE50 pDPAB 7FF138006640 ssh_ctx
7FF134007630 sftp_handle NULL buffer 7FF15C1DEE70 buflen 257
PEptr 7FF134004140
...
- - -
APAR: IV72073
Abstract: PATH TO MONITORED FILE NAME STARTS WITH DOUBLE SLASHES (//)
Additional information: Using the RegexLogSources option to
monitor a file which contains a regular expression meta
character in the first directory of the path, the resulting
monitored file name path starts with 2 forward slashes (//).
For example: RegexLogSources=/LFA_.*/ts_.*\.log , the File
Name field contains "//LFA_test/ts_01.log".
The extra starting slash is a cosmetic issue only and does
not cause any issues. The file is properly monitored.
The extra forward slash at the beginning of the path can
be seen on the portal in the File Name field in the Monitored
File Status on the Data Collection workspace or in the agent
logs.
The problem exists on Log File Agent v6.3.0 and v6.2.3.2.
This problem is platform independent.
However on Windows systems, if you specify the drive letter
preceding the path in the RegexLogSources option, the problem
does not occur.
Problem Determination:
On the the portal in the File Name field of the Data Collection
workspace, the File Name field contains, for example,
//LFA_test_logs/ts_01.log
With a minimum of the following trace enabled:
"KBB_RAS1: ERROR (UNIT:kumpdcm ALL)", the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains the double forward slashes:
- - -
...
...:kumpdcm2.c,279,"KUMP_GetNextMemberDouble") Directory /
Member
LFA_test_logs matched ^LFA_.*$; FilePathSpec2 NULL; and will
now use //LFA_test_logs
...:kumpdcm2.c,161,"KUMP_GetNextMember") Entry
...:kumpdir.c,139,"KUMP_OpenDir") Successfully opened
directory //LFA_test_logs 7F1748059310 7F1748059390
...:kumpdcm2.c,179,"KUMP_GetNextMember") Directory handle
7F1748059310 name //LFA_test_logs was successfully opened
...
- - -
APAR: IV71539
Abstract: %NNNN SYSTEM PARAMETERS NOT RESOLVED IN WINDOWS EVENT
LOG EVENTS
Additional information: On Windows 2003, the Log File Agent does
not resolve %nnnn system parameters in Windows Event Log
events. Windows Event Viewer is able to resolve the %nnnn to
the correct message. This problem might also be seen on
Windows 2008, when "UseNewEventLogAPI=N" is set in the agent
configuration file.
For example, the event is seen as:
DCOM got error "%1058" attempting to start the service
COMSysApp with arguments "" in order to run the server:
{7F19-11D2}
With a minimum of the following tracing enabled:
"KBB_RAS1: ERROR (UNIT:EventLog ALL)", the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-0<n>.log
contains entries similar to the following:
- - -
...
...:eventlog.cpp,1955,"ModifyParameter") Entry
...:eventlog.cpp,1969,"ModifyParameter") Scanning <DCOM
got error "%1058" attempting to start the service COMSysApp
with arguments "" in order to run the server:
{7F19-11D2} > for replaceable parameters.
...:eventlog.cpp,2175,"ModifyParameter") No parameters to
format.
...:eventlog.cpp,2185,"ModifyParameter") Scan results
<DCOM got error "%1058" attempting to start the service
COMSysApp with arguments "" in order to run the server:
{7F19-11D2} >
...:eventlog.cpp,2192,"ModifyParameter") Exit
...:eventlog.cpp,1600,"DisplayRecord") Event Log Record:
<DCOM got error "%1058" attempting to start the service
COMSysApp with
arguments "" in order to run the server:
{7F19-11D2}>
...:eventlog.cpp,1607,"DisplayRecord") Exit
...
- -
APAR: IV79219
Abstract: SHIP LIBKLOSSH-GSK8 LIBRARIES FOR z/LINUX 32-bit and
64-bit FOR REMOTE FILE PROCESSING.
Additional information: The libklossh-gsk8 library was not included
and shipped for ls3263, ls3266, hp11, and hp116 interps.
Defect 215184.
Defect: 215412
Abstract: Improve servicability of Windows File Notification
WaitForSingleObject trace message
6.3.0-TIV-ITM_LFA-IF0004
------------------------
APAR: IV68698
Abstract: WITH JAPANESE LOCALE, BACKSLASH CHARACTER IS WRONGLY
TRANSLATED WHEN INCLUDED IN TAKE ACTION COMMAND STRING
Additional information: When an event which is detected by the agent
is output from a situation using a Take Action command, by a
redirection, etc.; a single-byte backslash character ("\") is
displayed as a double-byte "middle point" character.
The character is correctly displayed in the portal indicating
that it is correctly read and translated by the agent when
read from the monitored log file.
The problem only occurs when the attribute containing
backslash is used in a Take Action command. When the
character is read from the monitored file, it is converted
from ibm-943_P15A-2003 to UTF-8 0xC2A5 - the UTF8
representation of backslash\yen). When the take action is
performed either at the agent or the monitoring server, the
agent translates the 0xC2A5 from UTF-8 to the native CP932
which results in the 0xFCFC character code.
The problem exists on the Log File Agent version 6.3.0
Interim Fix 0003 (6.3.0-TIV-ITM_LFA-IF0003) and earlier, with
Japanese locale. It can occur on Windows and UNIX® platforms.
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr ALL) (UNIT:task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
(54B982FE.000A-B30:kum0nget.c,411,"TranslateStringToUTF8") Entry
(54B982FE.000B-B30:kum0nget.c,419,"TranslateStringToUTF8")
Converting string buffer from ibm-943_P15A-2003 to UTF-8
...
(54B982FE.000F-B30:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRe
cord") <0x5FD6678,0x19>
+54B982FE.000F 00000000 2045206C 696E6461 C2A56C6D
6E6F61C2 .E.lmnoa..lmnoa. !!!!
+54B982FE.000F 00000010 A56C6D6E 6F61200D 0A
...
...
(54B982FE.00BE-F20:tasklibrary.cpp,1531,"ConvertCommandToLocal")
Converting UTF-8 command to codepage 932
...
(54B982FE.00DC-F20:tasklibrary.cpp,864,"executeTaskRequest")
Executing task cmd /c "echo lindaüülindaüülinda
>>c:\output.sit"
APAR: IV68574
Abstract: IN TAKEACTION, COMMAND OF MULTI-BYTE CHARACTERS WHICH HAVE 0XBA
OR 0XBB IS TRANSLATED TO LOCAL CODE PAGE INCORRECTLY.
Additional information: In takeAction processing, multi-byte
characters 0x82BA or 0x82BB in a command are translated to
local code page incorrectly. They are incorrectly replaced
with "[" and "]", respectively.
The problem exists on Log File Agent v6.3.0 Interim Fix 0003
(6.3.0-TIV-ITM_LFA-IF0003) and earlier releases and is
platform independent.
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:Logmonitor ALL) (UNIT:Kumprmfr ALL)
(UNIT:kum0nget ALL) (UNIT:Task ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains trace entries similar to the following:
- - -
...
...:kum0nget.c,419,"TranslateStringToUTF8") Converting string
buffer from ibm-943_P15A-2003 to UTF-8
...:kum0nget.c,482,"TranslateStringToUTF8") Buffersize 31158
bytes; Translated size 4 ; Copied 31158 characters readBuffer
1113EE3B0
...:kum0nget.c,498,"TranslateStringToUTF8") Exit: 0x113EE3B0
...:kum0nget.c,397,"KUM0_Fgets") Exit: 0x113EE3B0
...:kumprmfr.c,449,"KUMP_ReadMonitorFileUnicodeRecord")
<0x1113EE3B0,0x4> ?
+5492C8B8.000A 00000000 E3819D0A
... !!!!!!
...
<< The event is submitted to EIF - it still looks correct >>
(5492C8B8.005F-1B:logmonitorqueryclass.cpp,2433,"LogMonitorQuery
Class::setInstanceData") Submitting EIF event:
+5492C8B8.005F SOTEST_Event;C1='ã ';
E89 << hex character values>>
31D
...
...
...:tasklibrary.cpp,1225,"actionCallback") Received Take
action. Cmd=<print -r ' ã '>>/LFA/49806/sotestout.txt >,
User=<sysadmin>
...
...
...:tasklibrary.cpp,1531,"ConvertCommandToLocal") Converting
UTF-8 command to codepage 932
...:tasklibrary.cpp,1554,"ConvertCommandToLocal") Exit: 0x10F4BBF0
...
...
<< However when it is translated back from UTF-8 to codepage 943
it becomes incorrect:>>
...:tasklibrary.cpp,749,"executeTaskRequest") Entry
...:tasklibrary.cpp,791,"executeTaskRequest")
taskInfo.name = print
...:tasklibrary.cpp,841,"executeTaskRequest") Did
not find Task name 'print'. Going to run 'system' on the
request print -r ' ?]
'>>/LFA/49806/sotestout.txt .
...
- - -
APAR: IV68490
Abstract: ALL EVENTS ARE NOT DETECTED AND SENT AS EXPECTED WHEN
TRANSLATING FROM A MULTI-BYTE CODE PAGE
Additional information: All events are not matched and sent to the
event receiver. The events that are received might contain
garbled characters. Close examination of the agent log with
tracing enabled, shows that parts of the events or lines are
overwritten.
This only occurs when translating the data from a multi-byte
code page to UTF-8 and the conversion fails. The conversion
fails because the agent was unable to read all the bytes
required for a complete character into its buffer. This might
occur if a group of messages are sent or when a message
exceeds the maximum event size (EventMaxSize). Increasing the
EventMaxSize might produce different results.
The problem exists on the following Log File Agent versions:
- 6.3.0 interim fix 0003 and earlier
- 6.2.3.2 and later
- 6.2.2.4 Interim Fix 07 and later.
It is platform independent.
Problem Determination: With the following trace enabled for
the LO agent:
KBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all)
(UNIT:kumprmfr all)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log might
contain these error indicators:
"partial data", "RESIDUAL" , or "*****Error: u_strFromUTF8
failed for string".
Trace entries are similar to the following where the
translation buffer ends 0x1A and contains partial data.
- - -
...
...:kum0nget.c,411,"TranslateStringToUTF8") Entry
...:kum0nget.c,417,"TranslateStringToUTF8") translateBuffer
allocated 865 bytes at 43075E0
...:kum0nget.c,419,"TranslateStringToUTF8") Converting string
buffer from ibm-943_P15A-2003 to UTF-8
...:kum0nget.c,467,"TranslateStringToUTF8") Input buffer
43E31C3 of length 288 when translated into 43075E0 of
length 293 has partial data
...:kum0nget.c,469,"TranslateStringToUTF8") <0x43E31C3,0x120>
+... 00000000 23232323 3C323031 342F3132 2F303120
. . .
. . .
+... 00000100 3C313431 37343039 35343939 36383E20
<1417409549968>.
+... 00000110 3C424541 2D303030 3030303E 203CE383
<BEA-000000>.<..
+... 00000120 A1E38388 1A <---
..... !!
<< Note: When the failure occurs, the last three bytes of the
translated data are 0xEF 0xBF0 0xBD or the last byte is a 0x1A.>>
...:kum0nget.c,479,"TranslateStringToUTF8") Buffersize
865 bytes; Translated size 292; Copied 865 characters to
readBuffer 43E31C3 RESIDUAL 1 <----
!!!!!!!!!!
...
(...:kum0regx.c,286,"KUM0_IsRegExPatternMatch")
*****Error:u_strFromUTF8 failed for string
...
- - -
APAR: IV67737
Abstract: DUPLICATE EVENTS SENT BECAUSE LOG DETECTED AS SWITCHED OR
RE-CREATED
Additional information: After applying Log File Agent v6.3 IF0003
(6.3.0-TIV-ITM_LFA-IF0003) on AIX and Linux, with
NumEventsToCatchUp=-1 set in the conf file, the monitored log
is incorrectly detected as re-created or switched. The
monitored log is re-read from the beginning, resulting in
duplicate events.
This issue occurs on AIX, Linux. It does not exist on Windows
operating systems.
Problem Determination: With a minimum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:kumpfdp2 ALL) , the agent RAS1 log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
trace points similar to the following:
- - -
...
...:kumpfdp2.c,778,"DoFileTailRestart") Retrieved old monitor
filename </tmp/test_lfa.txt> creation time <1411741772> last
modification time <1411741772> size <699>
...
...:kumpfdp2.c,792,"DoFileTailRestart") Comparing creation
time <1411743260> last modification time <1411743260> size <758>
...:kumpfdp2.c,816,"DoFileTailRestart") Note: Monitorfile
/tmp/test_lfa.txt has been switched or re-created, updating
restart file
</opt/IBM/ITM/logs/LO_LFA01_LogfileEvents_LogfileEvents_tivoli85
.rst>
...:kumpfdp2.c,834,"DoFileTailRestart") Per TailRestartFromTop
parameter, restarting file monitoring from beginning of file
</tmp/test_lfa.txt>
...
- - -
The file, listed above, is detected as re-recreated based on the
file information returned by the operating system:
creation time modification time size
last <1411741772> <1411741772> <699>
current <1411743260> <1411743260 > <758>
APAR: IV67708
Abstract: WINDOWS EVENT LOG EVENTS WITH %N RESULTS IN A MESSAGE OF
"NONE"
Additional information: The event msg field or slot might contain
a value of "None", when a Windows event log message contains
a %n where n is a number in the event description field.
If the %n is not substituted, the Microsoft EvtFormatMessage
API returns ERROR_EVT_UNRESOLVED_VALUE_INSERT (15029) which
the agent treats as an error. As a result of the error, the
agent discards the event description and substitutes "None".
Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:WinLogQuery ALL), the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows
the "15029" error:
- - -
...
...:winlogqueryclass.cpp,932,"renderEvent") Rendering
message for event
...:winlogqueryclass.cpp,594,"renderEventString") Entry
...:winlogqueryclass.cpp,629,"renderEventString")
Retrieved metadata for provider MYEVENTSOURCE from hashmap
...:winlogqueryclass.cpp,676,"renderEventString")
EvtFormatMessage failed, error = 15029, evt handle = 0x00000002
...:winlogqueryclass.cpp,705,"renderEventString") Exit: 0x0
...
- - -
APAR: IV65900
Abstract: LOG FILE AGENT WINDOWS EVENT LOG EVENT ID NOT DETECTED
PROPERLY
Additional information: When the Windows Event log event ID is zero,
Log File Agent shows a random event ID.
Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1=ERROR (UNIT:WinLogQuery ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains the following trace point that shows an error
ocurred:
...:winlogqueryclass.cpp,799,"renderEvent") Error retrieving EventId
APAR: IV65500
Abstract: PROCESS PRIORITY NOT WORKING WITH SUBNODES
Additional information: The agent Process Priority Class setting
does not work with subnodes when it is enabled through the
autodiscovery option.
During the agent configuration, when the conf file and format
file are not specified and only the autodiscovery directory
and Process Priority Class are set, the Process Priority is not
set properly for the agent. It takes the default value.
APAR: IV64093
Abstract: EXCEPTION ACCESS VIOLATION WHEN EVENT EXCEEDS MAXIMUM
EVENT SIZE
Additional information: The kloagent process may terminate with an
Exception 0xC0000005 (ACCESS_VIOLATION), when the size of an
event exceeds the maximum event size (EventMaxSize) and is
truncated. The LO agent instance unexpectedly stops and goes
offline.
The crash occurs when the truncation occurs on a boundary
condition, and the event is truncated at a single quote and
has no ending semi-colon. It only occurs in the mapping of
the attribute slots to CustomSlots when sending events to IBM
Tivoli Monitoring from either a Windows event log or a file.
Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1= ERROR (UNIT:LogMonitorQuery ALL) (UNIT:WinLogQuery
ALL) (UNIT:kum0regx ALL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
contains the following trace points that show the size and
data of the incoming event:
...
...::winlogquerylist.cpp,1134,"writeEventDataToPipe")
Writing event of length ###### to pipe:
<contents of the log entry / event>
...:winlogquerylist.cpp,1145,"writeEventDataToPipe")
Node <.fmt stanza> wrote event to pipe for event log <logname>,
event size = XXXXX , bytes written = YYYYY
The following trace shows that the overall event exceeds
EventMaxSize and will be truncated. The '16384 bytes' is the
ventMaxSize the agent is using.
...
...:kum0regx.c,1152,"KUM0_PerformStringReplace")
Warning: Replacement string size ZZZZZ for attribute EIFEvent
larger than available buffer, only copied 16384 bytes to ....
The following trace points show the access violation:
...:logmonitorqueryclass.cpp,1812,"LogMonitorQueryClass:
:getSlotAttrAndValue") Entry
...:logmonitorqueryclass.cpp,1823,"LogMonitorQueryClass:
:getSlotAttrAndValue") No ; at end, <slotname>=' must be last
slot
...
...:kumpxtrt.c,51,"KUMP_PerformDataCallback")
***************************************************************
...:kumpxtrt.c,52,"KUMP_PerformDataCallback")
***** Data Callback Execution Exception Handler *****
...:kumpxtrt.c,56,"KUMP_PerformDataCallback")
***** Data Callback Function - EXCEPTION_ACCESS_VIOLATION *****
...:kumpxtrt.c,62,"KUMP_PerformDataCallback")
***************************************************************
...:kumpxtrt.c,65,"KUMP_PerformDataCallback") Exit: 0x0
Note: These entries might not be at the end of the log.
There will not be the corresponding exit trace point:
"LogMonitorQueryClass::getSlotAttrAndValue") Exit
See the APAR text for the .RAS file call stack information.
APAR: IV63704
Abstract: HEAVY WINDOWS EVENT LOG LOAD CAUSES DELAYS AND THE
APPEARANCE OF HANGS
Additional information: A heavy Windows event log throughput causes
delays in the events being displayed on the portal.
For example: when sending 1000 events per second per thread,
on 4 threads, the delay in seeing the events on the portal
might be as much as 30 minutes. The delay increases as the
PollInterval increases.
The agent might also appear to hang if too many duplicate
Windows Event log messages are received.
Problem Determination: With a mininum of the following trace
enabled for the LO agent:
KBB_RAS1: ERROR (UNIT: WinLogQueryList ALL) (UNIT:kum0nget ALL)
(UNIT:kumpfdp6 FLOW DETAIL)
the agent log
<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log
shows that the agent is continuing to monitor for incoming
events but no new events are received.
- - -
...
...:winlogquerylist.cpp,1143,"writeEventDataToPipe") Records
written to pipe n writeResult=1
< where n is the number of events written to pipe >
...
...
< And the following sequence repeatedly even though new events are
being sent. >
...:kumpfdp6.c,162,"WaitUntilNextSampleTime") >>>>>
WaitForSingleObject returned 258 for WaitFileHandle @78
...:kumpfdp6.c,233,"WaitUntilNextSampleTime") Exit: 0x1
...:kum0nget.c,122,"KUM0_Fgets") Entry
...:kum0nget.c,136,"KUM0_Fgets") read / actual BufferSize =
64146 / 192438, encoding = ibm-5348_P100-1997, convertToUTF8 = 1
...:kum0nget.c,308,"KUM0_Fgets") Using fgets() to get string
from file
...:kum0nget.c,355,"KUM0_Fgets") Pipe read returned no data
setting EOF
...:kum0nget.c,399,"KUM0_Fgets") Exit: 0x0
...
- - -
APAR: IV21752
Abstract: EIF: ERROR CODE 67 IS NOT HANDLED WHILE SENDING EVENTS
Additional information: If Error code 67 (Connection is broken) is
seen while sending events to the Event Integration Facility
(EIF) receiver, then the EIF sender ignores it and keeps
sending events forward, even though the events are not being
received by the EIF receiver.
This APAR is included in this fix for the Log File Agent on
Windows systems only. For UNIX/Linux systems, the fix is
included in IBM Tivoli Monitoring Shared Libraries (TEMA)
component of IBM Tivoli Monitoring version 6.2.3 Fix Pack 02
or later. You must install the Shared Libraries (ax) component
separately from the agent.
Enhancement: 212595
Abstract: Implement AESnnn-CTR ciphers for remote logs
6.3.0-TIV-ITM_LFA-IF0003
------------------------
APAR: IV60491
Abstract: SELINUX AUDIT LOG MESSAGES GENERATED WHEN USING IPV6 WITH
LOG AGENT
Additional information: On Log File Agent v6.3 and prior releases,
running the agent on a Security-Enhanced Linux (SELinux)
system using IPv6 with the SELinux security policy set to
"enforcing" generates audit messages. The messages in the
SELinux audit log /var/log/audit/audit.log are similar
to the following where <hostname> is the system the agent is
running on:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
type=AVC msg=audit(1389964628.602:213): avc: denied { write }
for pid=8121 comm="ifconfig" path="/opt/IBM/ITM/auditlogs/itm.
<hostname>_lz_audit.log" dev=dm-5 ino=4660
scontext=system_u:system_r: ifconfig_t:s0
tcontext=system_u:object_r:usr_t:s0 tclass=file
type=AVC msg=audit(1389964628.613:214): avc: denied { write }
for pid=8126 comm="ifconfig"
path="/opt/IBM/ITM/logs/<hostname>_lz_klzagent_52d92647-01.log"
dev=dm-5 ino=5066 scontext=system_u:system_r:ifconfig_t:s0
tcontext=system_u: object_r:usr_t:s0 tclass=file
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
APAR: IV60333
Abstract: EVENTS FROM WINDOWS EVENT LOG ARE INTERMITTENTLY NOT
DETECTED.
Additional information: Windows Event Log events are
intermittently not detected and sent. With the UnmatchLog
parameter specified, the event is also not saved in the
UnmatchLog file. In previous occurrences, the missing event
matches one of the format expressions and is sent. With
tracing set as described below, after the initial rendering
of the Windows Event Log event is seen in the agent log,
there are no occurrences of the event in the log.
This is more likely to occur when monitoring more than one
Windows Event Log (for example: Application, Security,
System, etc).
This problem occurs on Windows systems with Log File Agent
version 6.2.3.2 and 6.3.
APAR: IV59814
Abstract:BLANK ARCFOUR ALGORITHM CAUSES JAVA CORE WITH REMOTE LOG
FILE MONITORING
Additional information: The Log File Agent v6.3.0 might create Java®
cores when attempting to use the Remote Log File monitoring
feature which relies on SSH. The Java core is the result of a
blank("") arcfour algorithm name for the cipher.
The problem was initially seen on Linux, but is platform
independent.
With a minimum of KBB_RAS1: ERROR (UNIT:kex ALL), the agent
log <hostname>_lo_<instance>_kloagent_<timestamp>.log
ends with trace entries similar to the following:
- - -
...
(53444D90.04B8-40:kex.c,1880,"libssh2_kex_exchange") Entry
(53444D90.04B9-40:kex.c,1030,"kexinit") Entry
- - -
APAR: IV42315
Abstract: NUMEVENTSTOCATCHUP=-1 DOES NOT DETECT WHEN THE FILE HAS
BEEN REPLACED
Additional information: On restart of the Log FiLe agent, when the
configuration option NumEventsToCatchup is set to "-1", the
agent does not detect that a monitored file has been replaced
with a smaller file. The monitored file is not processed until
the file reaches the size maintained in the restart file. It
should result in the file being read from the beginning.
6.3.0-TIV-ITM_LFA-IF0002
------------------------
APAR: IV57736
Abstract: LOG FILE AGENT MAY CORE, CRASH ON HP-UX WHEN
NUMEVENTSTOCATCHUP IS USED.
Additional information: On HP-UX, when the configuration option
NumEventsToCatchUp is set to a value other than zero, the
agent might core. The problem occurs on Log File Agent v6.3.
The core might show the following:
Core was generated by ´kloagent'.
Program terminated with signal 11, Segmentation fault.
SEGV_MAPERR - Address not mapped to object
........
(gdb) where
#0 0xc000000010a30320:0 in UpdateRestartFileBaseFunction () at
kumpfdp2.c:427
#1 0xc000000010a32760:0 in UpdateRestartFileWithStats () at
kumpfdp2.c:553
#2 0xc000000010a3d970:0 in DoFileTailRestart () at
kumpfdp2.c:893
#3 0xc000000010a90af0:0 in KUMP_FileServer () at kumpfile.c:23
#4 0xc000000010b8eee0:0 in Task () at kumptask.c:35
#5 0xc0000000000fb140:0 in __pthread_bound_body+0x190 ()
from /usr/lib/hpux64/libpthread.so.1
........
With a minimum of "KBB_RAS1: ERROR (UNIT: kumpfdp2 ALL)
tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log ends with
trace entries similar to the following:
- - -
...
...:kumpfdp2.c,173,"KUMP_ParseSingleRestartLine") Parsing
RecPtr 6000000000736F4F <735>
...:kumpfdp2.c,1250,"KUMP_ParseNumericString") Unsuccessfully
parsed <NULL> to value 735
...:kumpfdp2.c,200,"KUMP_ParseSingleRestartLine") Error: parsed
location <NULL> file <735> creation <NULL> modification <NULL>
size <NULL> with RecPtr 6000000000736F53
...:kumpfdp2.c,427,"UpdateRestartFileBaseFunction") Note:
Required fields missing from restart file </opt/IBM/ITM/logs/L
O_default_LogfileEvents_hpia5.rst>
...:kumpfdp2.c,173,"KUMP_ParseSingleRestartLine") Parsing
RecPtr 6000000000736F53 <;>
...:kumpfdp2.c,200,"KUMP_ParseSingleRestartLine") Error: parsed
location <NULL> file <NULL> creation <NULL> modification
<NULL> size <NULL> with RecPtr 5FFFFFFFA0736F52Page 34 of 35
...:kumpfdp2.c,427,"UpdateRestartFileBaseFunction") Note:
Required fields missing from restart file
</opt/IBM/ITM/logs/LO_default_LogfileEvents_hpia5.rst>
- - -
APAR: IV56299
Abstract: A PERCENT SIGN (%) LITERAL IS NOT SUPPORTED IN FORMAT
STATEMENT
Additional information: When a percent sign (%) or a percent sign
(%) followed by a literal other than the valid variables of s,
t, n, is used in a FORMAT statement, it results in an "illegal
variable" message and an incorrect regular expression. As a
result, the record does not match as expected.
For example:
FORMAT 43866_Class10
43866_10 %s % %s*
. . .
or
FORMAT 43866_30
%t %s %MIDDLEWR: %s
. . .
With KBB_RAS1: ERROR, the the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
(5317981A.0002-12E0:lfaconfig.cpp,1042,"generateFormatFilter")
Format
for class 43866_Class10 contains illegal variable "%" in format
expression "43866_10 %s % %s*"
(5317981A.0003-12E0:lfaconfig.cpp,1045,"generateFormatFilter")
Variable
of type not recognized
...
- - -
This problem occurs on Log File Agent v6.3 and prior releases.
It is platform independent.
APAR: IV54710
Abstract: WINDOWS EVENT LOG NOT MONITORED ON SOME WINDOWS 2012
SYSTEMS AFTER INSTALLING 6.3.0-TIV-ITM_LFA-IF0001
Additional information: On some Windows 2012 systems, after
installing Log File Agent v6.3 interim fix 0001
(6.3.0-TIV-ITM_LFA-IF0001), Windows Event Log events are no
longer monitored. The Data Collection Status workspace shows
File Status: "231".
With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kum0fdp0.c,162,"KUM0_DynamicFileOpen")
fopen(\\.\pipe\KLO_gail_LogfileEvents_evl(System), rb) returned
NULL errno 231 'Unknown error'
...
- - -
APAR: IV53803
Abstract: TACMD ADDSYSTEM OF LO AGENT FAILS WITH
6.3.0-TIV-ITM_LFA-IF0001
Additional information: On Tivoli Enterprise Monitoring Server
v6.2.3 and beyond, when both the Log File Agent v6.3 (CIGM6ML)
and the interim fix (6.3.0-TIV-ITM_LFA-IF0001) are in the
depot, "tacmd AddSystem" fails because the interim fix
does not have a pre-requisite for LO version 06.30.00. The
agent is not pushed to the endpoint. This only occurs with
UNIX system targets.
APAR: IV53568
Abstract: ON WINDOWS FOR NUMEVENTSTOCATCHUP=-1 CREATES MULTIPLE
ENTRIES FOR EACH LOGS IN .RST AND MISSES EVENTS
Additional information: If NumEventsToCatchUp=-1, the restart (.rst)
file should be continuously updated. This file should contain
the name of each log being monitored along with the last
position read from the log. There should only be one line for
each monitored log file. However, instead of replacing the
line as it should, a new row is added. As a result, it is not
able to resume at the file position it was at when the agent
was stopped and events that occurred while the agent was
stopped are missed.
CPU performance issues might result from the excess processing
of the restart file.
APAR: IV52833
Abstract: SOME LOG LINES WRITTEN IN SEPARATE PIECES ARE INTERMITTENTLY
NOT SENT AS EVENTS
Additional information: On Windows® systems, some single lines
written to the monitored file in separate pieces are not sent
and do not appear in the UnmatchLog, if one was specified.
This might occur intermittently, when lines are written in
multiple parts, particularly on Windows systems.
With a minimum of KBB_RAS1: ERROR, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains a
trace entry similar to the following:
- - -
...:kum0mpbc.c,50,"KUM0_MoveStringPointerByChar")
***** Input string is NULL
- - -
APAR: IV52411
Abstract: MULTI-LINE *DISCARD* FORMAT FILTER INTERMITTENTLY ALLOWS
RECORDS TO ESCAPE FILTER AND SHOWS UP IN THE PORTAL.
Additional information: A multi-line *DISCARD* format filter
intermittently allows records to escape the filter and shows
up in the portal.
In addition, the handling of the end of the file (EOF) with
saved data from a previous read is not handled correctly.
This allows multi-line records which are split by EOF to
escape. The agent is not correctly retrying its read attempts
when it has a partial buffer and hits the EOF logic.
With a minimum of KBB_RAS1 with (UNIT:kum ALL) the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
. . .
(523B46FE.06DD-12:kum0regx.c,353,"KUM0_IsRegExPatternMatch")
Exit: 0x0
(523B46FE.06DE-12:kumpcapf.c,548,"KUMP_CheckAttributesPassFilter
s") Data <Sep 19 12:48:27 gisdev scsi: [ID 107833 kern.warning]
WARNING: /scsi_vhci/ssd@g600601602d301e0002f28a3e1ff9e111
(ssd63):
+523B46FE.06DE > AttrName <EIFEvent> failed MatchRegEx filter
1: <()^(.*Error for Command.*)\r?\n(.*)\r?\n(.*)\r?\n(.*)\r?\n
(.*asymmetric.*)()>
. . .
- - -
6.3.0-TIV-ITM_LFA-IF0001
------------------------
APAR: IV48040
Abstract: LOG FILE AGENT PROCESSING WINDOWS EVENT WHICH IS GREATER
THAN 64K CAUSES THE AGENT TO LOOP AND NOT PROCESS ANY MORE
EVENTS
Additional information: There were three issues found:
1)Event buffer size was limited to 64K. The event buffer
size is increased to 128K. A WARNING message is also issued
if an event exceeds the buffer size.
2)When the record is not processed because the buffer is too
small, the current event pointer is not incremented. On the
next pass, the same too-large event is read again, which
fails again and no more events are processed.
3)When numEventsToCatchUp is set to a value larger than the
number of records in the event log, the record number to read
is calculated incorrectly.
APAR: IV45784
Abstract: FILES CREATED AFTER KLO AGENT IS STARTED ARE NOT MONITORED
Additional information: On a Windows® system, if the monitored file
does not exist when the agent is started, the file is not
monitored after it is created. There might not be an entry for
the non-existent file in the Monitored File Status in the Data
Collection Status workspace.
The agent agent must be re-started to recognize the file or
the file must exist when the agent is started.
With a minimum of KBB_RAS1: ERROR, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kumpwfrm.c,261,"KUMP_WaitFileReadyForMonitor") ***
Unable to open file local file <filename>, Errno: 0,
ErrorText: No error, NO retry. Exiting
...:kumpfdp5.c,231,"CheckFileExistAndReady") *** File
C:/lo/43866/43866.log -- initial monitoring setup failed
<timestamp>:kumpfile.c,891,"KUMP_FileServer") >>>>> DP file
server ThreadID F04 ended for local file C:/lo/43866/43866.log
...
- - -
APAR: IV42745
Abstract: SOME LINES WRITTEN IN PIECES ARE UNMATCHED AND PARTIALLY
DISCARDED
Additional information: When a single line is written to the
monitored file in separate pieces, sometimes the line does
not match and is not sent as an event. This is because the
latter or subsequent piece of the line is written to the same
location in the internal read buffer and overwrites the
initial piece of the line. The resulting partial line does
not match the formats and is sent to the UnmatchLog, if one
was specified in the configuration file. This might occur
intermittently when lines are written in multiple parts,
particularly on Windows systems.
With a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL), the
agent log <hostname>_lo_<instance>_kloagent_<timestamp>.log
contains trace entries similar to the following:
- - -
...
...:kumprmfr.c,1015,"KUMP_ReadMonitorFileUnicodeRecord")
SavedRec 51A6A58 14 <job6 started: >
...
...:kumprmfr.c,412,"KUMP_ReadMonitorFileUnicodeRecord")
<0x51A6A58,0x56> 4+5187EED2.026F 00000000 362F362F
32303133 2036363A 3636200D 6/6/2013.66:66..
...
- - -
The second part of line is written to the same location in
the buffer, in the above example 0x51A6A58, overwriting the
first part of the line.
APAR: IV42699
Abstract: LAST MATCHING LINE OF LOG IS NOT IMMEDIATELY SENT AS A
MATCHING EVENT
Additional information: With record patterns that span multiple
lines (RECORDSET patterns), the last matching line of a
monitored file is not immediately sent as an event and it
does not show up in the UnmatchLog, if one was specified.
The amount of wait time till the event is actually sent is a
factor of the PollInterval.
With a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL)
(UNIT:kumpfdp ALL), the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following with the default
PollInterval of 5:
- - -
...
...:kumpfdp3.c,117,"OpenFileForMonitor") Assigned
RecordSetMaxWait = 5 seconds
...
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 1
MaxRecordSetWait limit 100
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 2
MaxRecordSetWait limit 100
...
...:kumprmfr.c,1090,"KUMP_ReadMonitorFileUnicodeRecord")
Waiting for RECORDSET end delimiter, RecordSetWaitCount 99
MaxRecordSetWait limit 100
...
- - -
APAR: IV41215
Abstract: BRACKET { IN FORMAT RESULTS IN LOAD METAFILE EXECUTION
EXCEPTION
Additional information: When an opening { bracket is used without a
closing bracket } in a FORMAT statement of the format file,
the agent log ends with a "Load Metafile Function -
EXCEPTION_ACCESS_VIOLATION" on agent start-up.
The agent process is still running but it is waiting for
initialization to complete successfully and is not monitoring.
The Data collection status Error Code is "No ERROR" but there
is no entry in the Monitored File Status for the monitored
file. This problem is platform independent.
With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...
...:kumplmet.c,204,"KUMP_LoadMetafile")
***************************************************************
...::kumplmet.c,205,"KUMP_LoadMetafile") ***** Load Metafile
Execution Exception Handler *****
...:kumplmet.c,209,"KUMP_LoadMetafile") ***** Load Metafile
Function - EXCEPTION_ACCESS_VIOLATION *****
...:kumplmet.c,215,"KUMP_LoadMetafile")
****************************************************************
...:logmonitorqueryclass.cpp,4031,"LogMonitorQueryClass:
:completReset") Table LogfileEvents still waiting for kum to
initialize after 30 seconds
...
- - -
APAR: IV39967
Abstract: RESTORED FILE IS NOT MONITORED AFTER CONF/FMT FILES
MODIFIED
Additional information: A restored log file is no longer monitored
and no new events are processed, when the sequence of all the
following events occur:
a) update the conf or fmt file to trigger reset processing,
b) remove the file, for example via un-mount, rename, delete,
move
c) wait for the 'File does not exist' status
d) restore the file.
The Data Collection workspace continues to show a File Status
of "FILE DOES NOT EXIST".
If the reset process (step a) is not triggered and only the
file is removed, the file is re-discovered properly. If only
the reset process (step a) is triggered, it also continues to
function properly.
Note: When the file is re-discovered after it is restored, it
is read from the beginning as a new file. This is not new
behavior with this APAR.
The root cause of this problem occurs on LFA v6.3, but the log
file is monitored when the file is restored.
APAR: IV37051
Abstract: EVENTS INTERMITTENTLY NOT MATCHED WHEN LINE WRITTEN IN
PIECES
Additional information: When an application writes only part of the
line and later writes the remainder of the line, the line
intermittently matches as an event with no changes to the fmt
file. This occurs more prevalently on Windows systems because
the operating system notifies the agent when the file has
changed. When the first part of the line is written, the agent
is notified but the partial line does not match any formats.
When the second part of the line is written, the agent is
notified again but the remainder of the line does not match
any formats. The two pieces of the line are treated as two
lines, neither of which match and both pieces are written as
two lines to the UnmatchLog, if one is configured.
Defect: 207998
Abstract: Agent does not continue to retry on remote log, when
RC -3, because errno is zero.
Additional information: When monitoring remote log files where the
connection breaks; for example, the remote system shuts down
or a network outage, the agent does not continually try
to re-establish the connection. The remote file is not
monitored. The Monitored File Status might not show a row
for the file.
With a minimum of "KBB_RAS1: ERROR tracing, the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:
- - -
...:session.c,243,"banner_send") Unable to send the banner
...:session.c,245,"banner_send") -3 - Error sending banner
to remote host
...:session.c,691,"session_startup") -3 - Error sending banner
to remote host
...:kum0sshlib.c,1227,"ssh_session_connect") Failed to
establish an SSH connection in 0 seconds for remote
[email protected]:22
/opt/IBM/ITM/logs/^mypia_ux_kuxagent_.*\.log$
mypia.ibm.com:22 socket 25 rc -3 errno 17 :
LIBSSH2_ERROR_BANNER_SEND
...
- - -
Defect: 206531
Abstract: Failed to load GSKit library
Additional information: When both GSKit version 7 and 8 are
installed on the same agent machine, either because of two
IBM Tivoli Monitoring installs, or some other product that
put a GSKit into the system /usr/lib directory, the wrong
version of the library is loaded and the GSKit
initialization fails. This problem has only been seen on
Linux®.
Defect: 205184
Abstract: Improve handling of files on re-mounted file systems
Defect: 204120
Abstract: Log agent crashes on Solaris due to mis-aligned integer
Additional information: Agent crashes in KUMP_DoDPdataToDCH when it
formats data from a buffer into integers and other formats,
due to a copy of an odd-aligned integer.
Defect: 203012
Abstract: LogSources wildcards match directories remote log -31 err
Additional information: If a LogSources specifies a remote directory
and not a remote file, the Monitored File Status shows "File
Status" OK, "File Type" of "REGULAR FILE", "PIPE" or
"UNKNOWN" and "Current File Size" 4096, but no files are
monitored.
Note: After the fix, when there are no wildcards in the
directory path, it may still show Status" OK, "File Type"
of "REGULAR FILE".
3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the Tivoli
Log File Agent User's Guide, version 6.3.0.
The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.
Please refer to the IBM Software Product Compatibility Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]
3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher
(6.2.2-TIV-ITM-FP0002)
This fix pack is a complete install image and as such, can be
installed on a pristine system. This fix is also cumulative, and can
be installed on any fix level for this version, release, and mod
level above the prerequisite.
For details, see the Troubleshooting Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Log%20File%20Agent [https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Log%20File%20Agent]
4.0 Image directory contents
===================
This fix image contains the following files:
- 6.30-TIV-ITM_LFA-FP0002.tar.gz
- 6.30-TIV-ITM_LFA-FP0002.README
5.0 Installation instructions
==================
5.1 Before installing the fix
-------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.
- For the purpose of this README, the symbol <CANDLEHOME> 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 fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
- NOTE: Before installing the LO x86-64 bit agent, you must
un-install the WINNT 32-bit version of the agent and the 32/64
bit compatibility package.
5.2 Local agent update
--------------------------
For installation instructions, see the Log File Agent User's Guide
v6.3.0:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/logfile/logfileagent_user.htm?lang=en [http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/logfile/logfileagent_user.htm?lang=en]
Note:
1. The PowerPC little-endian installation image is located in the
PPC_LE directory of the installation image. Invoke ./install.sh
from this directory.
2. On Windows systems, when the installation completes, the
Readme.txt displays "Welcome to IBM Tivoli Monitoring V6.2.3 Fix
Pack 5." This is the installer level and Readme and is not an
error.
5.3 Remote agent update
----------------------------
1. Transfer the archive file 6.3.0-TIV-ITM_LFA-FP0002.tar.gz to a
temporary directory on the IBM Tivoli Enterprise Monitoring
Server system. For the purpose of this README, the symbol <TEMP>
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 platforms.
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 Administrator's Guide.
Note:
1. The prerequisite Log File Agent bundles must also be in the
depot, to ensure successful completion of the remote agent update.
2. The 6.3.0-TIV-ITM_LFA-FP000<n> bundles must be removed from the
depot, using the "tacmd removeBundles" command.
For example: tacmd removeBundles -t lo -v 06300000<n>
On UNIX systems,
if the fix was expanded to <TEMP>/6.3.0-TIV-ITM_LFA-FP0002:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.3.0-TIV-ITM_LFA-FP0002
On Windows systems,
if the fix was expanded to <TEMP>\6.3.0-TIV-ITM_LFA-FP0002:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.3.0-TIV-ITM_LFA-FP0002
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. Please 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. 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 Administrator's Guide.
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 lo
-n <Managed system name>
-v 06300200
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 LO
-n <Managed system name>
-v 06300200
Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (LO), not three characters (KLO).
- 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.2 Agent support update
------------------------------
Fix pack 6.3.0-TIV-ITM_LFA-FP0001 included new certificates
in the agent support files which need to be installed. If you have
already installed these updates, there are no additional installation
steps. Otherwise, install the updates to the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server, or Tivoli
Enterprise Portal Desktop. For more information about installing
application support, see Installing and enabling application support
in the IBM Tivoli Monitoring Installation and Setup Guide.
6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or any
of the superseded fixes. No additional installation steps are
required.
6.2 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to 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 LO
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 LO
Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (LO), not three characters (KLO).
When the agent update is successful, the agent version is:
06.30.02.00.
After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.30.02.00.
2. To verify the agent you are running contains the updates from the
fix, see the following lines in the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log located in
$CANDLEHOME/logs on UNIX systems and
%CANDLE_HOME%\tmaitm6\logs on Windows systems:
<timestamp> Component: ira
<timestamp> Driver: agent_fac_63:201709131450/4769716.3
<timestamp> Timestamp: Sep 13 2017 ...
7.0 Known problems and workarounds
=========================
None.
8.0 Additional product information
======================
None.
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 [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.
PREREQUISITES
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher (6.2.2-TIV-ITM-FP0002).
As this fix is cumulative, it can be installed on any fix level for this version, release, and mod level above the prerequisite.
INSTALLATION INSTRUCTIONS
Please refer to the full README contained in the Download Description section above for general installation instructions.
DOWNLOAD PACKAGE
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.0-TIV-ITM_LFA-FP0002 25 Sep 2017 English 1796861216 FC [http://www.ibm.com/support/fixcentral/quickorder?fixids=6.3.0-TIV-ITM_LFA-FP0002&product=ibm/Tivoli/IBM Tivoli Monitoring&source=dbluesearch&platform=All] [ ]
PRODUCT ALIAS/SYNONYM
KLO
log adapter
[/support/docview.wss?uid=swg24043263&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24043263&aid=2]Problems (APARS) fixed
IV96363, IV95005, IV93401, IV89574, IV82875, IV82170, IV81364, IV79219, IV79204, IV78340, IV77403, IV76731, IV76119, IV75776, IV75603, IV75336, IV74487, IV74480, IV72073, IV71539, IV68698, IV68574, IV68490, IV67737, IV67708, IV65900, IV65500, IV64093, IV63704, IV60491, IV60331, IV60333, IV59814, IV57736, IV56299, IV54710, IV53803, IV53568, IV52833, IV52411, IV48040, IV45784, IV42745, IV42699, IV42315, IV41215, IV39967, IV37051, IV21752 | Is there a 64-bit agent Log File Agent available for Windows OS? Is there a 64-bit agent Log File Agent available for Windows OS? | This fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC little-endian Log File agent. |
TRAIN_Q067 | IBM Rule Team Server/Decision Center is timing out while performing certain operations - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
How to resolve "Transaction timed out after 601 seconds" error while performing certain operations in Rule Team Server (RTS)/Decision Center (DC)?
SYMPTOM
While generating ruleapps in RTS/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes):
On WebLogic:
Rule Team Server has encountered an unexpected error. The internal error message is: #{SelectionBean.asynchAction}: javax.faces.el.EvaluationException: java.lang.RuntimeException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057DF8C316E1C1224CD]'. No further JDBC access is allowed within this transaction.
...
On WebSphere:
TimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds.
TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 3,5,main]. The stack trace of this thread when the timeout occurred was:
ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046)
ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772)
ilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyParser.java:511)
...
CAUSE
The transaction timeout for RTS/DC is set to 10 minutes by default in the teamserver web module deployment descriptor (WEB-INF/web.xml), and application servers also have container level transaction timeouts that are configurable. If a transactional operation performed by RTS/DC takes longer than these timeouts to complete, the transaction is rolled back and the operation is not completed.
RESOLVING THE PROBLEM
If you perform time consuming operations in large repositories, you can increase the timeout value in the web.xml file of the RTS/DC EAR file (jrules-teamserver-<appserver>.ear\teamserver.war\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout.
You will find the property in the file web.xml defined as below:
...
<context-param>
<description>Modify the timeout value that is associated with transactions (in seconds)</description>
<param-name>ilog.rules.teamserver.transaction.timeout</param-name>
<param-value>600</param-value>
</context-param>
...
Another place to look for are application server specific transaction timeout configurations. For example, for WebSphere Application Server, check the "Maximum transaction timeout" and increase it as needed as described here [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html].
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 7.5 Enterprise Business Integration IBM Operational Decision Manager Platform Independent 8.0.1, 8.0 Enterprise | ODM 8.7 TeamServer users active authoring rules and they get kicked out - transaction timeout or session timeout? Some of my users are being kicked out of TeamServer while actively authoring rules. What value would be controlling this behavior? Session timeout is at it's default 30 minutes. Does transaction timeout come in to play here or is there a different setting that might be causing this. Thanks. | If you perform time consuming operations in large repositories, you can increase the timeout value in the web.xml file of the RTS/DC EAR file (jrules-teamserver-<appserver>.ear\teamserver.war\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout. |
TRAIN_Q068 | IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)
QUESTION
When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain?
ANSWER
Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2 | Does DataPower support SHA-2?
Is DataPower able to support SHA-2 (SHA256)?
1 | Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred. |
TRAIN_Q069 | IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States ssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ)
THIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):
English
QUESTION
Why would some outgoing SSL handshakes fail with firmware version 6.0 but not prior firmware versions?
CAUSE
Beginning in firmware version 6.0 and above, the default SSL settings have changed. The Crypto profiles now have TLSv1.2 and 1.1 which will be enabled by default. This affects the protocol version included in the Client Hello when DataPower is acting as the SSL client. If TLSv1.2 is not supported, the server still negotiates to the most secure supported protocol (e.g. TLSv1.1, TLSv1.0, SSLv3) if enabled.
Some legacy servers with non-compliant implementations of SSL may reject connection attempts when TLSv1.2 or TLSv1.1 are used. In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol.
The TLS versions 1.1 and 1.2 are part of the requirements for being compliant with NIST SP800-131a.
ANSWER
Upgrade the SSL server to a version compliant with the SSL/TLS specifications. If required you may disable TLSv1.2 and TLSv1.1 within the Crypto Profile to allow compatibility.
Within the domain simply navigate to the Objects> Crypto Configuration> Crypto Profile>
Then simply click on your specific profile to view the Options selection and see what SSL protocol versions are supported.
Any further questions or issues please feel free to contact DataPower support. A packet trace and error report would be the most helpful information in viewing the problem. | Why SSL handshake is failing after upgrading to 6.0 or above? After upgrading my datapower firmware to v6.0 or above, ssl handshake is failing, is there a reason for it? | Some legacy servers with non-compliant implementations of SSL may reject connection attempts when TLSv1.2 or TLSv1.1 are used. In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol. |
TRAIN_Q070 | IBM Search option for a reserved word or character in documents in Atlas - United States TECHNOTE (FAQ)
QUESTION
How do I search for a string which has reserved words or characters when searching in documents in Atlas?
CAUSE
There are specific options to use in oracle when you search for certain strings
ANSWER
When there is a "-" in a string you are searching for, you need to use "\" in front of the "-"
For example - "String1-String2" should be searched as "String1\-String2"
Please refer to the oracle documentation for Special Characters in Oracle Text Queries | How do I search for a string which has reserved words or characters when searching in documents in Atlas? How do I search for a string which has reserved words or characters when searching in documents in Atlas? | When there is a "-" in a string you are searching for, you need to use "\" in front of the "-"
For example - "String1-String2" should be searched as "String1\-String2" |
TRAIN_Q071 | IBM Verify an IEM server upgrade is still in progress - United States TECHNOTE (FAQ)
QUESTION
How can I tell if the IBM Endpoint Manager (BigFix) server database upgrade is progressing?
CAUSE
When upgrading a BigFix server, most of the time is usually spent upgrading the database. The installer launches the BESAdmin utility to complete this part of the upgrade, but does not provide detailed progress during this phase. For some long running upgrades, it may appear that the upgrade is hung or not progressing:
On Windows, the BESAdmin UI will indicate "Not Responding" if clicked on at this point.
On Linux, the message "Info: Configuring the database for the server component, please wait ... " is reported.
ANSWER
It is important to allow the upgrade to complete when in this state, and not attempt to cancel or kill the upgrade process. To verify the upgrade is still active, check that the following process is still running:
Windows: BESAdmin.exe
Linux: BESAdmin
CPU usage of BESAdmin may be minimal during times when the database is doing most of the work, so just the existence of the process is good confirmation. For additional confirmation, the BFEnterprise or BFENT database can be monitored for activity using SQL Server Profiler or the DB2 'CREATE EVENT MONITOR' statement to track SQL statement events. | Why does my upgrade to BigFix version 9.2.5 take a very long time? My upgrade to BigFix version 9.2.5 takes a very long time. What do I need to do? | It is important to allow the upgrade to complete when in this state, and not attempt to cancel or kill the upgrade process. To verify the upgrade is still active, check that the following process is still running:
Windows: BESAdmin.exe
Linux: BESAdmin |
TRAIN_Q072 | IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States A FIX IS AVAILABLE
Fixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]
SUBSCRIBE
You can track all active APARs for this component.
APAR STATUS
* CLOSED AS PROGRAM ERROR.
ERROR DESCRIPTION
* During Portal Start-Up following error is shown:
--------------------
0000005e MBeanStarter E com.ibm.wps.
scripting.server.MBeanStarter loadExtensions failed to load
extension:
key: ServerExt.applications / value:
com.ibm.wps.scripting.server.
ApplicationServerExtensions
LOCAL FIX
* 1) open the WAS admin console
2) navigate to Resources > Resource environment providers > WP
ScriptingService > Custom properties
3) you should see an entry with the name
"ServerExt.applications" and value
"com.ibm.wps.scripting.server.ApplicationServerExtensions"
4) delete this entry, save and restart the server.
PROBLEM SUMMARY
* A code fix for this issue is integrated into the WebSphere
Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal
8.5.0.0 available from Fix Central:
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent
=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al]
l&platform=All&function=aparId&apars=PI31198
PROBLEM CONCLUSION
* Added a task to remove the outdate resource environment
provider entry.
TEMPORARY FIX
COMMENTS
APAR INFORMATION
* APAR NUMBER
PI34677
* REPORTED COMPONENT NAME
WEBSPHERE PORTA
* REPORTED COMPONENT ID
5724E7600
* REPORTED RELEASE
850
* STATUS
CLOSED PER
* PE
NoPE
* HIPER
NoHIPER
* SPECIAL ATTENTION
NoSpecatt
* SUBMITTED DATE
2015-02-10
* CLOSED DATE
2015-03-10
* LAST MODIFIED DATE
2015-03-10
* APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:
* APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:
FIX INFORMATION
* FIXED COMPONENT NAME
WEBSPHERE PORTA
* FIXED COMPONENT ID
5724E7600
APPLICABLE COMPONENT LEVELS
* R850 PSY
UP | Error: "MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION" occurs at portal startup
We are using Portal Server 8.5 and when starting the Portal server we see following error:
0000005e MBeanStarter E com.ibm.wps.scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.ApplicationServerExtensions
How can we permanently resolve this error? | A code fix for this issue is integrated into the WebSphere
Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal
8.5.0.0 available from Fix Central:
http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent
=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al]
l&platform=All&function=aparId&apars=PI31198 |
TRAIN_Q073 | IBM An unexpected ruleset version is executed - United States TECHNOTE (FAQ)
QUESTION
Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?
What are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ?
CAUSE
Possible causes for unexpected versions to be executed are:
- the RES client requesting execution may be passing a wrong ruleset path
- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)
- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete
- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses
ANSWER
First validate that the RES components (the Execution Unit, the Management Console and the Client Application bundling the RES client library, which may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res/tpc_res_config.html].
The ruleset version that is executed depends first on the ruleset path that is requested. Specifying a ruleset path with no version ( such as /MyRuleApp/MyRuleset/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as /MyRuleApp/2.0/MyRuleset/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the requested ruleset path.
A common situation for an unexpected ruleset version to be executed is that of a hot deployment that is not successfully completed. The more frequent causes for the hot deployment not to happen as expected are:
* Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update through JMX. For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.config/config_ds_res_was8/tsk_was_map_admin_group.html]
* Version mismatch between the Execution Unit(s) and the Management Console: in order for the Management Console to detect the presence of execution units the versions of these components must match down to the fix level. For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the "About" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version. For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor
* Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that time. Note that there is no guarantee of which specific earlier version of the ruleset may be used since it is a factor of which versions are available in the deprecated ruleset cache and whether garbage collection has occurred. In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_forcing_sync_pars.html].
* Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See XU notification in a cluster over multiple cells [http://www-01.ibm.com/support/docview.wss?uid=swg21458245]. If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http://www-01.ibm.com/support/docview.wss?uid=swg21418646] can be useful.
* Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully
* Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_deploy_rlapp_ant.html] does not trigger a notification, so the update may only been seen after server restart.
* XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http://pic.dhe.ibm.com/infocenter/dmanager/v8r0/topic/com.ibm.wodm.dserver.rules.res.managing/topics/tsk_res_config_xu_mbean_jse.html]
* Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2SE mode hot deployment does not seem to work [http://www-01.ibm.com/support/docview.wss?uid=swg21585251]
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES / RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0 | Latest deployed ruleset not executing in clustered environment
We are using ODM 8.7.0.1 and are running into an issue in our clustered environment. After deploying an updated to the ruleapp, using "Replace RuleApp Version" versioning policy, the that the decision service is still executing the previous version of the business rules.
| Possible causes for unexpected versions to be executed are:
- the RES client requesting execution may be passing a wrong ruleset path
- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)
- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete
- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses |
TRAIN_Q075 | IBM Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) - United States Sybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES
ABSTRACT
This fix resolves the APARs and defects and provides the enhancements listed
in the "Problems Fixed" section below.
DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2018.
All rights reserved.
Component: IBM® Tivoli® Composite Application Manager for Applications 721 FP2:
Monitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)
Fix Pack: 0002
Component ID: 5724B96SO
Date: December 8, 2017
Table of 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 fix contains the APARs and defects that are specified in the "Problems
fixed" section.
2.0 Problems fixed
==================
The following problems are addressed by this fix.
2.1 APARs
----------
APAR :IV95149
Abstract :While installing Sybase agent "find / -name ASE-*" command takes too
long on system containing large disk and high volume mounts
Additional Information: While installing Sybase agent, prereqchecker invokes the SybaseVersion_plug.sh
script which executes the "find" command from root for finding Sybase server version.The "find /" command takes
a long time on systems with large disks, high volume of mounts.
2.2 Enhancements
----------------
RFE :86384
Abstract :Monitor availability of the Sybase backup Server, Job Server and
database job failures.
Additional Information: To monitor sybase backup server and job server status two new attributes were
added in existing attribute group Server Details.And to monitor failed job in database
two new attribute groups Job Details and Job Summary were added.
3.0 Architecture and prerequisites
===================================
This fix is supported on all operating systems listed in Compatibility report website.
For information about system requirements, go to the software product
compatibility reports website, and search for the ITCAM for Applications
product:
(http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]).
3.1 Prerequisites for this fix
-------------------------------
The minimum required version of IBM Tivoli Monitoring is V6.2.2 FP2
4.0 Image directory contents
==============================
Electronic Part Number: ITCAM Apps Ag for Sybase CNN25ML
The following folder structure of the image is created:
1. Sybase Agent Installer
-WINDOWS folder:
This folder contains the binary files for installing the 32-bit agent.
The folder also contains the Prereqchecker utility in the prereqchecker folder
for the Sybase agent.
- unix folder:
This folder contains the binary files for installing the 32-bit agent on Unix
platform. The folder also contains the Prereqchecker utility in the
prereqchecker folder for the Sybase agent.
This fix image contains the following files and directories:
AUTORUN.INF
[Deploy]
DeployLnk.sh
README.TXT
[unix]
notices
[WINDOWS]
install.sh
kcirunas.cfg
[license]
silent_install.txt
silent_config.txt
2. Sybase Support Installer
-WINDOWS folder:
This folder contains the Windows agent support files for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop
client, and Tivoli Enterprise Browser client.
- Unix folder:
This folder contains the non-Windows agent support files for the Tivoli
Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli
Enterprise Desktop client, and Tivoli Enterprise Browser client.
This fix image contains the following files and directories:
AUTORUN.INF
DeployLnk.sh
[WINDOWS]
README.TXT
[unix]
notices
install.sh
kcirunas.cfg
tmv630fp6-d5334a-201511302339.appsall.tar
[license]
silent_install.txt
silent_config.txt
Note:
If you are working in a UNIX environment, use install.sh file to install.
If you are working in a Windows environment, you can choose setup.exe
under directory [WINDOWS] or [WIA64] according your Windows platform.
5.0 Installation instructions
=============================
When this fix pack image is downloaded from the IBM Software Support Web site,
these rules apply:
* You can locally install the fix pack only on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases. Similar to other
upgrade software, the fix pack image also can be locally installed on a
computer where the product software is not already installed.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.
When this fix pack image is downloaded from Passport Advantage, these rules
apply:
* You can locally install the fix pack on a system that already hosts a
licensed copy of IBM Tivoli Monitoring for Databases.
* You can locally install the fix pack on a system that does not already host
a licensed copy of IBM Tivoli Monitoring for Databases.
* You can populate agents to the depot.
* You can remotely deploy agents to existing or new installations.
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 symbol <CANDLEHOME> 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.
- If you have customized the Monitoring Agent for Sybase Agent
oy.ini file on UNIX system, this file should be backed up before the fix
install. After this fix is installed, edit the latest oy.ini file and merge
your modifications into this oy.ini file.
5.2 Local agent install and update (including silent installation)
--------------------------------------------------------------
1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to a temporary
directory on the system that contains the agent code to be updated.
For the purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory.
Note: On Windows, this includes the drive letter.
2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.
3. Use the procedures in the "ITCAM for Applications, Version 7.2.1.2
Installation and Setup Guide" to install the agent.
4. Use the procedures in the specific database monitoring agent user's
guide to complete the installation and configuration.
5. After agent upgrade bitness of agent binary should be same as pre-upgrade on x86-64
bit windows. Agent do not support upgrade to 64 bit binary.
5.3 Remote agent update and installation
----------------------------------------
1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to
a temporary directory on the IBM Tivoli Enterprise
Monitoring Server system. For the purpose of this README, the
symbol <TEMP> represents the fully qualified path to this directory.
Note: On Windows, this includes the drive letter.
2. Expand the archive file using the tar command on UNIX systems or an
unzip utility on Windows systems. This creates a directory structure
that contains fixes for all of the supported operating systems.
3. To add the fix pack 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 Appendix A. Commands reference
of the "IBM Tivoli Monitoring Administrator's Guide."
On a UNIX system: if the fix was expanded to
<TEMP>/CNN25ML:
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/WINDOWS/Deploy -t oy -f
> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/unix -t oy -f
where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case or
represents the Monitoring Agent for Sybase Agent
-f performs the actions without asking for confirmation
On a Windows system: if the fix was expanded to
<TEMP>/CNN25ML:
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNN25ML\WINDOWS\Deploy -t oy -f
> %CANDLE_HOME%\bin\tacmd addBundles -i <TEMP>\CNN25ML\unix -t oy -f
where:
-i is the directory that contains the deployment bundles to be
added to the depot.
-t is the product code of the product to add, in this case oy
represents the Monitoring Agent for Sybase Agent
-f performs the actions without asking for confirmation
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 updateAgent commands, see Appendix A. Commands
reference of the "IBM Tivoli Monitoring Administrator's Guide."
On a UNIX system:
> $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 oy
-n <Managed system name>
-v 062002000
On a Windows system:
> %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 OY
-n <Managed system name>
-v 062002000
If there are not prior version koy agent on remote system .Then use
below tacmd addSystem command.
> %CANDLE_HOME%\bin\tacmd addSystem -t OY
-n <Managed system name>
-p INSTANCE="<Sybase instance name>"
Note:
- The <Sybase instance name> is the Sybase agent instance name to be monitored on
remote system.
- The component (-t) for the updateAgent command is specified as
two characters (oy), not three characters (koy).
- The node (-n) for the updateAgent command is the managed system
name of the operating system (OS) agent to be updated. The
target node for an updateAgent command is always an OS agent.
-Remote installation will fail if the MTEMS window is open on the agent machine.
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:
1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to
the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli
Enterprise Portal Servers or Tivoli Enterprise Portal desktops.
2. Expand the archive file using the tar command on UNIX systems or an
unzip utility on Windows systems.
3. Use the procedures in the "ITCAM for Applications, Version 7.2.1.2
Installation and Setup Guide."
4. Use the procedures in the specific database monitoring agent user's
guide to complete the installation and configuration.
5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a
Hub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise
Monitoring Server.
6.0 Additional installation information
=======================================
6.1 Verifying the update
-------------------------
1.To verify whether the agent is updated correctly, use the tacmd command to
view the current version of the agent after the agent is restarted. Ensure that
you log on to the Tivoli Enterprise Monitoring Server before you view 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 OY
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 OY
Note:
The component (-t) for the tacmd listSystems command is specified as two
characters (OY), not three characters (KOY).
When the agent is updated, the agent version is changed to 06.20.02.00.
After the agent is restarted, you can also use the GUI to verify whether the
agent was updated. For the agent on Windows systems, the version number is
06.20.02.00.
2.To verify whether the agent support files are updated correctly, use the
kincinfo command on Windows systems or the cinfo command on Linux or UNIX
systems.
On UNIX or Linux systems:
To validate that all components have been installed, run the following command:
$CANDLEHOME/bin/cinfo -i
Sample output for the cinfo command on a UNIX or Linux systems
----------------------------------------------------------
[root@HJS-SYB-1 bin]# ./cinfo
*********** Wed Nov 29 23:53:13 IST 2017 ******************
User: root Groups: root
Host name : HJS-SYB-1 Installer Lvl:06.30.06.00
CandleHome: /opt/IBM0611/ITM
***********************************************************
-- CINFO Menu --
1) Show products installed in this CandleHome
2) Show which products are currently running
3) Show configuration settings
4) Exit CINFO
1
*********** Wed Nov 29 23:53:15 IST 2017 ******************
User: root Groups: root
Host name : HJS-SYB-1 Installer Lvl:06.30.06.00
CandleHome: /opt/IBM0611/ITM
***********************************************************
...Product inventory
ax IBM Tivoli Monitoring Shared Libraries
lx8266 Version: 06.30.06.00
gs IBM GSKit Security Interface
lx8266 Version: 08.00.50.36
jr Tivoli Enterprise-supplied JRE
lx8266 Version: 07.09.01.00
oy Monitoring Agent for Sybase server
lx8266 Version: 06.20.02.00
ui Tivoli Enterprise Services User Interface
On Windows systems:
To validate that all components have been installed, run the following command:
%CANDLE_HOME%\bin\kincinfo –i
Sample output of the kincinfo command on a Windows System
----------------------------------------------------------
C:\IBM\ITM\BIN>kincinfo -i
********** Thursday, November 30, 2017 10:10:02 AM **********
User : Administrator Group : NA
Host Name : HJ-IBMIBM6737 Installer : Ver: 063006000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
IN Install INS/Windows Install Component
WINNT Version: 06.30.06.00 Build: 201511302132
IN TEMA(32-bit) INS/ITM 6.x Agent Install Component
WINNT Version: 06.30.06.00 Build: 201511302132
IN TEMA(64-bit) INS/ITM 6.x Agent Install Component Extensions
WINNT Version: 06.30.06.00 Build: 201511302132
AC KAC(64-bit) CMA/32/64 Bit Agent Compatibility Package
WIX64 Version: 06.30.06.00 Build: 201511302132
GL KGL(64-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
WIX64 Version: 06.30.06.00 Build: d5334a
GL KGL(32-bit) CMA/Tivoli Enterprise Monitoring Agent Framework
WINNT Version: 06.30.06.00 Build: d5334a
GS KGS(64-bit) GSK/IBM GSKit Security Interface
WIX64 Version: 08.00.50.36 Build: d5313a
GS KGS(32-bit) GSK/IBM GSKit Security Interface
WINNT Version: 08.00.50.36 Build: d5313a
JM KJM(32-bit) JVM/Embedded JVM
WINNT Version: 07.09.01.00 Build: 201506221629
NT KNT(32-bit) CMA/Monitoring Agent for Windows OS
WINNT Version: 06.30.00.00 Build: 30321
OY KOY(32-bit) CMA/Monitoring Agent for Sybase Server
WINNT Version: 06.20.02.00 Build: 72651
UE KUE(32-bit) CMA/Tivoli Enterprise Services User Interface Extensions
WINNT Version: 06.30.06.00 Build: d5334a
UI KUI(32-bit) CLI/Tivoli Enterprise Services User Interface
WINNT Version: 06.30.06.00 Build: 201511302132
7.0 Known problems and workarounds
==================================
Problem: Sybase agent configuration is not working using itmcmd manage
command from GUI on Solaris 11
Workaround:
For Solaris 11:
Run './itmcmd config -A oy' present at location:<CandleHome>/bin
Problem: Prereqchecker which is integrated with the installer fails on
windows platform.
Workaround:
For Windows:
Run on command prompt ‘prereq_checker.bat KOY’ present at location:
InstallerPath\Sybase_Agent_Installer\WINDOWS\prereqchecker
For Unix:
Run ‘./prereq_checker.sh KOY’ present at location:
InstallerPath\Sybase_Agent_Installer\unix\prereqchecker
Problem: Registry entries are not cleared when agent is uninstalled on 64 bit
windows platform.
Workaround: Delete registry entries manually from path:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Candle\KOY\610\
Problem: When running the verification step in the "itmcmd config -A oy"
function on a Solaris 10 system, the following output from the verification
program is produced: "user needs read authority to".
Workaround: Issue "ps -ef | grep koyagent" to locate the koyagent process and
issue "kill -9" for that process. Check the Navigator tree in the Tivoli
Enterprise Portal for an offline koyagent entry and clear the offline entry.
The Monitoring Agent for Sybase Server that was configured by "itmcmd config"
is unaffected by this problem.
Problem: When running multiple remote deploys and agent upgrades, a task
timeout occurs during either the remote deployment or the agent upgrade.
Workaround: Restart the OS Agent following the task timeout and before
performing the next remote deployment or agent upgrade.
Problem: If you are installing this fix into a depot on a Windows computer, and
WinZip(R) is used to extract this fix, text files in the depot might contain
CTRL-Ms. When this fix is remotely deployed to a UNIX machine from the Tivoli
Enterprise Monitoring Server or depot on Windows, the installation fails. The
CTRL-Ms are caused by extracting the fix using WinZip with "TAR file smart
CR/LF conversion" option enabled. This extraction causes WinZip to put CTRL-Ms
in text files when they are extracted on UNIX through remote deployment.
Workaround: If you are using WinZip for the fix installation for the Tivoli
Enterprise Monitoring Server on Windows, disable the default "TAR file smart
CR/LF conversion" option.
Problem: In the Tivoli Enterprise Portal, the instance name is displayed
instead of the host name in the Navigation tree.
For example the Navigation tree might look like this,
MySid
Sybase
Alert Log
...
instead of this,
MyHost
Sybase - MySid
Alert Log
...
The problem is that the length of the managed node name, <SID>:<HOSTNAME>:SYB,
exceeds the length supported by the portal. A possible cause is that the
fully-qualified host name is being used. If 'uname -n' on the Monitoring Agent
for Sybase Server computer returns a fully-qualified host name, then this host
name is the cause.
Workaround: Override the host name with an appropriate shorter name by adding
the following line to oy.config:
export COLL_HOSTNAME=<short name>
8.0 Additional product information
==================================
Steps for enabling SDA (Self-describing agent)
For Windows:
1.On the computer where the monitoring server is installed, in the Manage
Tivoli Enterprise Monitoring Services application, right-click the agent and
select Advanced→ Edit ENV file.
2.Edit the existing environment variable to: TEMA_SDA=Y.
For UNIX:
1.On the computer where the monitoring agent is installed, change to the
<Install_dir>/config/ directory.
2.Open the coordinating file:
For single-instance agents: <pc>.ini
For multi-instance agents: <pc>_<instance>.ini file
Where pc is the two-character product code.
3.Edit the existing environment variable to: TEMA_SDA=Y.
9.0 Copyright and trademark information
========================================
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions
worldwide. Other product and service names might be trademarks of IBM or other
companies. A current list of IBM trademarks is available on the Web at
"Copyright and trademark information" at ww.ibm.com/legal/copytrade.shtml.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of
Microsoft Corporation in the United States, other countries, or both. Java and
all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the
United States, other countries, or both. 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.
10.0 Notices
==================
This information was developed for products and services offered in the United
States. IBM may not offer the products, services, or features discussed in this
document in other countries. Consult your local IBM representative for
information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product,
program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
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 states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
INSTALLATION INSTRUCTIONS
Sybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.
URL LANGUAGE SIZE(Bytes) 6.2.0-TIV-ITM_SYB-FP0002 (CNN25ML) [https://w3-03.ibm.com/software/xl/download/ticket.wss] English 1722240862
DOWNLOAD PACKAGE
Sybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.
IBM Tivoli Composite Application Manager for Applications 721 FP2:
Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) (CNN25ML)
PRODUCT ALIAS/SYNONYM
OY
KOY
Sybase Agent
[/support/docview.wss?uid=swg24044440&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044440&aid=2]Problems (APARS) fixed
IV95149 | Where can I get Tivoli Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)? Where can I get Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)? I can't find this on Fix Central. | Component: IBM® Tivoli® Composite Application Manager for Applications 721 FP2:
Monitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)
Fix Pack: 0002
Component ID: 5724B96SO
Date: December 8, 2017 |
TRAIN_Q076 | IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States SECURITY BULLETIN
SUMMARY
IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate
VULNERABILITY DETAILS
CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]
DESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
All versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server
REMEDIATION/FIXES
For MQ 5.3
*
*
*
*
*
*
*
*
*
* https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all
*
For MQ 8
*
*
* here
*
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]
*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. | Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) I need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735). Where can I find this information? | CVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]
DESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) |
TRAIN_Q080 | 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 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-2011-5320 CVE-2017-15670 CVE-2017-15671 CVE-2017-15804
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
PRODUCT ALIAS/SYNONYM
WMB HVE IIB HVE | Help with Action required for IIB H.E. V9 and WMB H.E. V8 for security vulnerabilities in Red Hat Linux (CVE-2011-5320, CVE-2017-15670, CVE-2017-15671, CVE-2017-15804) 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? | IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable |
TRAIN_Q081 | IBM Content Collector V4.0.1 Fix Pack 3 - United States DOWNLOADABLE FILES
ABSTRACT
This document contains links to the download page for IBM Content Collector V4.0.1 Fix Pack 3
DOWNLOAD DESCRIPTION
IBM CONTENT COLLECTOR DOWNLOADS
* All versions [http://www.ibm.com/support/docview.wss?uid=swg27040223]
* Version 4.0.1 Fix Pack 3- selected tab,
Apply IBM Content Collector V4.0.1 Fix Pack 3 to upgrade from IBM Content Collector V4.0.1 to IBM Content Collector V4.0.1.3.
Below is the list of the problems that were fixed in this fix pack.
APAR Number APAR Abstract HE12445 [http://www.ibm.com/support/docview.wss?uid=swg1HE12445] ICC reporting "SOLID Table Error 13011: Table GENERIC_DATA does not exist" or "Connection switch, some session context may be lost" HE12488 [http://www.ibm.com/support/docview.wss?uid=swg1HE12488] SOME DOCUMENTS INTERMITTENTLY FAILED INDEXING WITH "COULD NOT BE PROCESSED AS A REGULAR EMAIL" ERROR. HE12491 [http://www.ibm.com/support/docview.wss?uid=swg1HE12491] IBM Content Collector cannot delete the entry from the Blacklist table in the solidDB HE12436 [http://www.ibm.com/support/docview.wss?uid=swg1HE12436] EXCEL FILES CANNOT BE INDEXED DUE TO 100% CPU CONSUMPTION task missing HE12490 [http://www.ibm.com/support/docview.wss?uid=swg1HE12490] Domino Template Enablement in IBM Content Collector setup tools causes an error when enable domino template. HE12513 [http://www.ibm.com/support/docview.wss?uid=swg1HE12513] TAG FILES REMAIN FOR ICC SOFTWARE COMPONENTS WHICH ARE NOT ACTUALLY INSTALLED. HE12526 [http://www.ibm.com/support/docview.wss?uid=swg1HE12526] EXPRESSION DOES NOT GET SAVED IN THE 'WS CALL WEB SERVICE' TASK HE12529 [http://www.ibm.com/support/docview.wss?uid=swg1HE12529] Mailbox randomly is skipped in the ICC cluster HE12537 [http://www.ibm.com/support/docview.wss?uid=swg1HE12537] CONTENT COLLECTOR INSTALLATION FAILS WITH ACCESS IS DENIED ERROR ON WASSERVICE.EXE FILE PREREQUISITES
IBM Content Collector V4.0.1 Fix Pack 3 can be used with the following IBM Content Collector version:
URL LANGUAGE SIZE(Bytes) Prerequisites for IBM Content Collector V4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27042658] English 1
INSTALLATION INSTRUCTIONS
Read the fix pack readme files for specific information about installing the fix pack packages.
URL LANGUAGE SIZE(Bytes) 4.0.1.3-IBM-ICC-FP003 [https://www-945.ibm.com/support/fixcentral/swg/downloadFixes?parent=Enterprise%2BContent%2BManagement&product=ibm/Information+Management/Content+Collector&release=All&platform=All&function=fixId&fixids=4.0.1.3-IBM-ICC-FP003&includeRequisites=1&includeSup] English 1
DOWNLOAD PACKAGE
The IBM Content Collector V4.0.1 Fix Pack 3 download package consists of the following files:
* 4.0.1.3-IBM-ICC-FP003.pdf: Readme file
* 4.0.1.3-IBM-ICC-Server-FP003.zip
* 4.0.1.3-IBM-ICC-OWA-FP003.zip
* 4.0.1.3-IBM-ICC-P8CSS-AIX-FP003.tar.gz
* 4.0.1.3-IBM-ICC-P8CSS-Linux-FP003.tar.gz
* 4.0.1.3-IBM-ICC-P8CSS-SOLARIS-FP003.tar.gz
* 4.0.1.3-IBM-ICC-P8CSS-WIN-FP003.zip
* 4.0.1.3-IBM-ICC-P8CSS-Linuxz-FP003.tar.gz
* 4.0.1.3-IBM-ICC-CM8Text-AIX-FP003.tar.gz
* 4.0.1.3-IBM-ICC-CM8Text-Linux-FP003.tar.gz
* 4.0.1.3-IBM-ICC-CM8Text-Solaris-FP003.tar.gz
* 4.0.1.3-IBM-ICC-CM8Text-WIN-FP003.zip
* 4.0.1.3-IBM-ICC-CM8Text-Linuxz-FP003.tar.gz
HOW CRITICAL IS THIS FIX?
This fix addresses vulnerabilities that are described in CVE-2016-0363 and CVE-2016-0376 which are disclosed as part of IBM Runtime Environment Java Technology Edition, Version 6 in April 2016.
For further information see the Readme File for IBM Content Collector V4.0.1 Fix Pack 3
[/support/docview.wss?uid=swg24042387&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042387&aid=2]Problems (APARS) fixed
HE12445 HE12488 HE12491 HE12436 HE12490 HE12513 HE12526 HE12529 HE12537 | 'Access is denied' install errors with ICC Installing ICC 4.0.1 and then FP2 gives the 'Access is denied' error on WASSERVICE.exe. How to resolve this? | Apply IBM Content Collector V4.0.1 Fix Pack 3 to upgrade from IBM Content Collector V4.0.1 to IBM Content Collector V4.0.1.3. |
TRAIN_Q082 | IBM Security Network Protection firmware 5.3.1 release notes - United States release notes; readme; firmware; xgs FIX README
ABSTRACT
IBM Security Network Protection Firmware Version 5.3.1 is a firmware update for the XGS NGIPS network protection platform. This release provides the following updates to IBM Security Network Protection Firmware Version 5.3.1.
CONTENT
Serviceability and support enhancements:
* You can now get additional information about your system through the command line within your "Tools" directory. We have added the Sysinfo command that will display system CPU, memory, and storage information in command line interface (CLI).
Note: A complete list of CLI commands are located in the Command-line interface [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/references/alps_command_line_interface.htm] section in the Knowledge Center.
* New to this release we have added a services mode within CLI. These commands will allow you to restart key services within the appliance. These services are listed below: * Packet processing
* Packet Capture
* Local Management Interface (LMI)
* License and Update (LUM)
* SiteProtector Communication
* You can now view and search logs from the command line using the "less" and "tail" commands from within logs mode. Log files found using the less command are System, Webserver, Updates and Analysis logs.
* With the admin-sftp account you can now retrieve Snapshots, Packet Captures, and support files. This account uses the same password as the admin account.
Note: More details on admin-sftp can be found in the Downloading files with an SFTP client [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/tasks/alps_downloading_sftp.htm]documentation on the Knowledge Center. [http://www.ibm.com/support/knowledgecenter/SSHLHV_5.3.1/com.ibm.alps.doc/tasks/alps_downloading_sftp.htm]
Response enhancement: * Forwarded events (Remote Syslog Alert Responses) will show the same details as the content sent to SiteProtector.
* Support for using the TCP protocol when creating Remote Syslog Alert Responses to prevent messages being truncated and improve delivery reliability over using UDP.
Network Access Policy enhancement: * You can now use the network access policy to control network access when the HTTP X-Forward-For (XFF) header is enabled. The network policy can use the XFF header along with the packet source to control network traffic.
IPS Policy enhancements: * You can now derive a new IPS object from an existing IPS object by right-clicking on an IPS object and left-clicking on Clone.
* When enabling network, transport-layer, and status events in a non-default IPS object, a warning message is shown. This will help to minimize what may be seen as a false negative.
Performance: * Inspection throughput increase for XGS 7100 up to 25Gbps, FPL5 (25Gbps) added.
Miscellaneous updates and implementation changes: * Top 10 URLs and URL categories widget in the Local Management Interface have been disabled by default. Given the limited popularity of this feature, coupled with the performance impact in certain situations, we disabled the feature by default. You can re-enable it by using the advanced parameter tune.url.topten.tracking=true.
* We have removed the MultiCast Domain Name System (mDNS), under some configurations it caused security risks within the appliance.
* Support for mutual certificate authentication for communication between the Network Security appliance and SiteProtector.
Known issues:
You can find a list of known issues for IBM Security Network Protection 5.3.1 in Technote 1715537: Known issues for IBM Security Network Protection version 5.3.1 [http://www.ibm.com/support/docview.wss?uid=swg21715537].
[/support/docview.wss?uid=swg21902778&aid=1] [https://ibm.biz/BdHdZx] [/support/docview.wss?uid=swg21902778&aid=2] [http://ibm.biz/InfraSecForumTechnote] [/support/docview.wss?uid=swg21902778&aid=3] [http://ibm.biz/SecSuptUTube] [/support/docview.wss?uid=swg21902778&aid=4] [http://ibm.biz/InfraSecFixes] [/support/docview.wss?uid=swg21902778&aid=5] [http://ibm.biz/FlexLicLogin] [/support/docview.wss?uid=swg21902778&aid=6] [http://ibm.biz/MyNotification] [/support/docview.wss?uid=swg21902778&aid=7] [http://ibm.biz/ContactSecSupport]
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903740] | XGS 5.3.0.6: Is there a way to replicate an inspection object under the same policy repository? Is there a way to replicate an inspection object under the same policy repository? | You can now derive a new IPS object from an existing IPS object by right-clicking on an IPS object and left-clicking on Clone. |
TRAIN_Q083 | IBM Use"isolate the resource provider" to establish data source connections using a different JDBC driver from the same database vendor - United States isolate this resource provider TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Customer has defined 3 Oracle JDBC Providers at cell, node and server
scope. Client have following configuration in websphere JDBC provider.
In Cell Scope - C:\jdbc\ojdbc5\ojdbc5.jar
In Node Scope - C:\jdbc\ojdbc6_g\ojdbc6_g.jar
In Server Scope- C:\jdbc\ojdbc6\ojdbc6.jar
In this case value of JDBC driver path in WebSphere variable is identical. Nornally, If JDBC provider configure at server level then server level driver will get load first. But in this case since all three drivers are from same vendor, So we can not control which driver is picking up. In this case
"C:\jdbc\ojdbc6\ojdbc6.jar" should be loaded first but instated, ojdbc5.jar was load first
[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass
oracle.jdbc.driver.OracleDriver
loader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9
source=file:/C:/jdbc/ojdbc5/ojdbc5.jar Exit
SYMPTOM
Due to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.
CAUSE
When multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded.
RESOLVING THE PROBLEM
In order to support the existence of multiple versions of the driver jars, the "Isolate this resource provider" configuration helps to ensure there are no conflicts. This needs to be configured on each JDBC Provider. You cannot isolate only one resource provider, all the provider configurations in different scopes will have to be configured with the "Isolate this resource provider" setting. In this scenario, the resource provider classes from different versions of the jars are not imported or accessed to verify if the isolation has indeed worked. In order to use the server-scoped resource provider the datasource using the server-scoped jdbc provider will have to be referenced from the application after isolating the resource providers and using a resource reference in the application.
Go to the JDBC Provider and enable "isolate the resource provider". When "Isolate this resource provider" is enabled, it ensures that only the jar that was specified in the classpath will be used for all the datasources under that particular JDBC provider.
Here are links to Knowledge Center articles which contain further information on the setting:
JDBC provider settings [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/udat_manjdbcprodet.html]
Considerations for isolated resource providers [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rdat_isolatedlimitations.html] | When click test connection, the older JDBC driver version shows in the SystemOut.log file
When I click a test connection to a datasource, in the SystemOut.log file I can see the below information...
[8/11/16 5:31:28:494 EDT] 00000088 DSConfigurati I DSRA8205I: JDBC driver name : Oracle JDBC driver
[8/11/16 5:31:28:495 EDT] 00000088 DSConfigurati I DSRA8206I: JDBC driver version : 9.2.0.1.0
[8/11/16 5:31:28:496 EDT] 00000088 DSConfigurati I DSRA8025I: Successfully connected to DataSource.
[8/11/16 5:31:28:608 EDT] 00000088 DSConfigurati I DSRA8203I: Database product name : Oracle
[8/11/16 5:31:28:608 EDT] 00000088 DSConfigurati I DSRA8204I: Database product version : Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, Automatic Storage Management, OLAP, Advanced Analytics
Where is WAS getting this information from?
We are using WAS ND v8.5.5.0. We are running Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production. The JDBC driver is ojdbc6.jar - Oracle 11.1.0.7.0-Production JDBC 4.0 compiled with JDK6.
There is another older driver ojdbc14.jar
When I do a test connection, I can see the JDBC Driver version is 9.2.0.1.0, but in the JDBC providers I have specified ojdbc6.jar. so it should show 11.1.0.7.0 but it is showing 9.2.0.1.0. why it is showing 9.2.0.1.0?
If we keep only ojdbc6.jar and do a test connection it is giving the correct JDBC Drivers version as it is same with ojdbc6.jar. But when we keep both ojdbc6.jar and ojdbc14.jar it is not giving the correct JDBC Driver version looks it is giving ojdbc14.jar version.
JDBC providers are pointed to ojdbc6.jar, but why it is showing a different JDBC driver version? | When multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded. |
TRAIN_Q084 | IBM Security Bulletin: IBM MQ clients connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it. (CVE-2018-1371) - United States SECURITY BULLETIN
SUMMARY
An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the queue manager's amqrmppa channel process, terminating it.
VULNERABILITY DETAILS
CVEID: CVE-2018-1371 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1371]
DESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.
CVSS Base Score: 6.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137771 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137771] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
AFFECTED PRODUCTS AND VERSIONS
IBM MQ V8.0
* Maintenance level 8.0.0.8
IBM MQ V9 LTS * Maintenance level 9.0.0.2
IBM MQ V9 CD * IBM MQ version 9.0.4
REMEDIATION/FIXES
IBM MQ V8.0
Apply FixPack 8.0.0.9 [http://www-01.ibm.com/support/docview.wss?uid=swg22015103]
IBM MQ V9 LTS * Apply FixPack 9.0.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24044508]
IBM MQ V9 CD * Upgrade to 9.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24043463]
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
01 Feb 2018: Original Version published
13 April 2018: Added 9.0.5, 9.0.0.3 and 8.0.0.9 FixPack details
*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.
Cross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers | Help with Security Bulletin: IBM MQ Clients connecting to an MQ Queue Manager can cause a SIGSEGV in the AMQRMPPA channel process terminating it (CVE-2018-1371) I need to understand details regarding Security Bulletin: IBM MQ Clients connecting to an MQ Queue Manager can cause a SIGSEGV in the AMQRMPPA channel process terminating it (CVE-2018-1371). Where can I find this information?
| CVEID: CVE-2018-1371 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1371]
DESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.
CVSS Base Score: 6.5
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137771 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137771] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) |
TRAIN_Q085 | IBM How to change Siebel connection settings using the siebel.properties file in WebSphere Adapter for Siebel eBusiness Applications - United States TECHNOTE (FAQ)
QUESTION
The Siebel connection of WebSphere Adapter for Siebel eBusiness Applications is established with the default settings. You may need to modify the connection settings, such as connection timeout, according to your product environment.
ANSWER
Siebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.
Create a siebel.properties file and save it in the classpath of the adapter (For example, <adapter project>\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections.
This is applicable for all supported brokers.
A detailed description of the Siebel.properties file is given below:
Siebel.properties File
The siebel.properties file, which is located in your classpath, can be used to provide default parameters for client applications connecting to Siebel applications using the Java Data Bean.
The table below shows the properties in the siebel.properties file.
[/support/docview.wss?uid=swg21366662&aid=1] [/support/docview.wss?uid=swg21366662&aid=1] [/support/docview.wss?uid=swg21366662&aid=1] Property Type Property Description Siebel Connection Manager Connection properties siebel.conmgr.txtimeout Indicates the transaction timeout (in milliseconds). Defaults to 600000 = 10 minutes. siebel.conmgr.poolsize Indicates the connection pool size. Connection pool maintains a set of connections to a specific server process. Defaults to 2. Max connection pool size is 500. siebel.conmgr.sesstimeout Indicates the transaction timeout (in seconds) on the client side. Defaults to 2700 = 45 minutes. siebel.conmgr.retry Indicates the number of open session retries. Defaults to 3. siebel.conmgr.jce
siebel.conmgr.virtualhosts Indicates the usage of Java Cryptography Extension. 1 for jce usage and 0 for no usage.
A listing of virtual servers representing a group of like servers that perform the same function, for example, call center functions.
An incoming login for the call center Virtual Server will try servers from the list in a round-robin fashion.
An example of such a list follows:
VirtualServer1=sid1:host:port,sid2:host:port...;VirtualServer2=...
where:
Virtual Servers = an assigned list of real Siebel Servers with host names and port numbers (of the local SCB). Siebel Generated code for JCA/JDB properties siebel.connection.string Specifies the Siebel connection string. siebel.user.name Specifies the user name to be used for logging in to Object Manager. siebel.user.password Specifies the password to be used for logging in to Object Manager. siebel.user.language Specifies the user's preferred language. siebel.user.encrypted Specifies whether the username and password is encrypted. siebel.jdb.classname Specifies the default JDB classname Java System Properties file.encoding Indicates the code page on the client side. For example, cp1252, utf8, unicodeBig, cp942. NOTE: Java System Properties are System Properties, not Siebel Properties.
The following is a sample siebel.properties file:
siebel.connection.string = siebel.tcpip.rsa.none://test.siebel.com/siebel/sseobjmgr_enu/test
siebel.conmgr.txtimeout = 3600
siebel.conmgr.poolsize = 5
siebel.conmgr.sesstimeout = 300000
siebel.properties [/support/docview.wss?uid=swg21366662&aid=3] [/support/docview.wss?uid=swg21366662&aid=2] | WebSphere Business Integration (WBI) Adapter for Siebel timeouts: unable to process large orders?
I receive the following error message when WebSphere Business Integration (WBI) Adapter for Siebel V2.6 tries to process an event in the event table for a large order:
OMRPC Request xxx on connection xxx was abandoned after 600133 ms because it timed out. (SBL-JCA-317)
What should I do? | Siebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.
Create a siebel.properties file and save it in the classpath of the adapter (For example, <adapter project>\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections. |
TRAIN_Q087 | IBM Required gtk libraries for IBM Installation Manager on AIX - United States gtk; motif TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
IBM Installation Manager requires gtk libraries to support the graphical user interface (GUI).
SYMPTOM
Installation Manager reports errors when the gtk libraries are not installed.
Examples of the reported errors:
* SWT library could not be loaded:
# ./install
00:00.92 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged
Could not load SWT library. Reasons:
/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
swt-pi-gtk (Not found in java.library.path)
/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
swt-pi-gtk (Not found in java.library.path)
/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)
java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
/root/Desktop/InstallationManager/configuration/org.eclipse.osgi/bundles/633/1/.cp/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
swt-pi-gtk (Not found in java.library.path)
/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)
/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)
at org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)
at java.lang.J9VMInternals.initializeImpl(Native Method)
...
The displayed failed to initialize. See the log /root/Desktop/InstallationManager/configuration/1361168761043.log for details.
* Segmentation error occurs when the gtk libraries are installed but are not at the required versions
Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=F0739208 Handler2=F05F5F1C
R0=D3D9FDCC R1=3013EEF0 R2=F077B69C R3=F0779450
R4=00000000 R5=00000000 R6=00000000 R7=00000000
R8=1220000F R9=1220000F R10=F0687A0C R11=000034E0
R12=03222C60 R13=30C7DD00 R14=31FAA028 R15=F05851EC
R16=00000007 R17=00000000 R18=F073B388 R19=30C7DD50
R20=32935C30 R21=31FAA040 R22=00000000 R23=30000BC8
R24=10010E04 R25=F05F7130 R26=30148364 R27=0000007E
R28=CFACCBB8 R29=F073AB7C R30=D3DC1410 R31=F0779430
IAR=D3DB63A8 LR=D3D9FDE8 MSR=0000D032 CTR=D3DE0E70
CR=22004084 FPSCR=82000000 XER=0000001B TID=00000000
MQ=00000000
FPR0 329d3fd000000110 (f: 272.000000, d: 6.943460e-65)
FPR1 41e0000000000000 (f: 0.000000, d: 2.147484e+09)
FPR2 c1e0000000000000 (f: 0.000000, d: -2.147484e+09)
FPR3 4330000001e00000 (f: 31457280.000000, d: 4.503600e+15)
FPR4 4330080000000000 (f: 0.000000, d: 4.512396e+15)
FPR5 4133851800000000 (f: 0.000000, d: 1.279256e+06)
FPR6 4133851800000000 (f: 0.000000, d: 1.279256e+06)
FPR7 4330080000138518 (f: 1279256.000000, d: 4.512396e+15)
FPR8 005f0031002e0034 (f: 3014708.000000, d: 6.897895e-307)
FPR9 002e0038002e0076 (f: 3014774.000000, d: 8.344265e-308)
FPR10 0032003000310033 (f: 3211315.000000, d: 1.001324e-307)
FPR11 0030003200320035 (f: 3276853.000000, d: 8.900720e-308)
FPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)
FPR13 4028000000000000 (f: 0.000000, d: 1.200000e+01)
FPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)
FPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)
Target=2_40_20110203_074623 (AIX 7.1)
CPU=ppc (8 logical CPUs) (0xc0000000 RAM)
----------- Stack Backtrace -----------
(0xD3D9F81C)
(0xD43D5E48)
(0xD43D8698)
(0xD43D1D38)
(0xD43D1B24)
(0xD3E4ABA0)
(0xD43D3058)
(0xD43D3200)
(0xD0F0ED18)
(0xD0F1536C)
(0xD0F19438)
(0xD2B1DF48)
(0xD2AE7780)
(0xD2AE7A30)
(0xD1516BAC)
(0xD2AE78E4)
(0xD2AE7E24)
(0xD2AEC6C4)
(0x100013C0)
(0xD04FCD88)
---------------------------------------
JVMDUMP006I Processing dump event "gpf", detail "" - please wait.
JVMDUMP032I JVM requested System dump using '/opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp' in response to an event
Note: "Enable full CORE dump" in smit is set to FALSE and as a result there will be limited threading information in core file.
JVMDUMP010I System dump written to /opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp
JVMDUMP032I JVM requested Java dump using '/opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt' in response to an event
JVMDUMP010I Java dump written to /opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt
JVMDUMP032I JVM requested Snap dump using '/opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc' in response to an event
JVMDUMP010I Snap dump written to /opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc
JVMDUMP013I Processed dump event "gpf", detail "".
Segmentation fault (core dumped)
CAUSE
Installation Manager is an Eclipse Rich Client Program application based on the open source project found at http://www.eclipse.org [http://www.eclipse.org]. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI. For Installation Manager, the GUI is the wizard mode of operation.
You can use Installation Manager without the gtk libraries. For information on console mode, command-line mode, or silent mode; see the Installation Manager Information Center [http://pic.dhe.ibm.com/infocenter/install/v1r6/topic/com.ibm.cic.agent.ui.doc/topics/c_modes.html]. Silent mode uses a response file and command-line mode is supported by all packages. For console mode, check your product documentation to verify that the product supports console mode.
RESOLVING THE PROBLEM
To use the GUI, the gtk+ RPM and dependencies must be available on AIX.
Install this set of RPMs on AIX:
atk-1.12.3-2.aix5.2.ppc.rpm
cairo-1.8.8-1.aix5.2.ppc.rpm
expat-2.0.1-1.aix5.2.ppc.rpm
fontconfig-2.4.2-1.aix5.2.ppc.rpm
freetype2-2.3.9-1.aix5.2.ppc.rpm
gettext-0.10.40-6.aix5.1.ppc.rpm
glib2-2.12.4-2.aix5.2.ppc.rpm
gtk2-2.10.6-4.aix5.2.ppc.rpm
libjpeg-6b-6.aix5.1.ppc.rpm
libpng-1.2.32-2.aix5.2.ppc.rpm
libtiff-3.8.2-1.aix5.2.ppc.rpm
pango-1.14.5-4.aix5.2.ppc.rpm
pixman-0.12.0-3.aix5.2.ppc.rpm
xcursor-1.1.7-3.aix5.2.ppc.rpm
xft-2.1.6-5.aix5.1.ppc.rpm
xrender-0.9.1-3.aix5.2.ppc.rpm
zlib-1.2.3-3.aix5.1.ppc.rpm
The installed RPMs must be of the minimum versions listed above.
To install the RPM versions specified above take the following steps:
1. Download the gtk2_bundle_v2.tar package [ftp://ftp.software.ibm.com/aix/freeSoftware/aixtoolbox/ezinstall/ppc/] (version 'v2') containing all the RPMs and the install script to a new directory.
2. Decompress the tar file.
You can use the command tar -xvf gtk2_bundle_<version>.tar to decompress the file.
3. Open the decompressed directory gtk2_bundle_<version> and run the install.sh script.
The script will check if the required RPMs are installed at the compatible level. If they are not, the script will prompt to install the compatible versions.
4. Verify the environment variable LIBPATH contains a path to the installed libraries.
For example LIBPATH=/opt/freeware/lib/
Note that if you download and install RPMs individually, we have found that the following libraries are incompatible: * glib2-2.14.6-2 and gtk2-2.10.6-5
RELATED INFORMATION
#Unreadable characters in the GUI when using X11 [http://www.ibm.com/support/docview.wss?uid=swg21661861] | Installation manager (IIM) fails to start on AIX, generates core file from GPF even though all GTK libs are installed. Trying to install DASH 3.1.3 on AIX but IIM won't start and instead creates a dump file with a GPF noted. We found a technical note with a list of the required libs for IIM on AIX and we have all of the latest versions of those libs. Why is the installer failing to start? | To use the GUI, the gtk+ RPM and dependencies must be available on AIX.
Install this set of RPMs on AIX: |
TRAIN_Q089 | IBM Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server that ships with WebSphere Enterprise Service Bus (CVE-2015-2613, CVE-2015-2601, CVE-2015-4749, CVE-2015-2625, CVE-2015-1931) - United States SECURITY BULLETIN
SUMMARY
There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Application Server that ships with WebSphere Enterprise Service Bus.
VULNERABILITY DETAILS
CVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]
DESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
CVEID:CVE-2015-2601 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2601]
DESCRIPTION:An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104733 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104733]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)
CVEID:CVE-2015-4749 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4749]
DESCRIPTION:An unspecified vulnerability related to the JNDI component could allow a remote attacker to cause a denial of service.
CVSS Base Score: 4.3
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104740 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104740]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:P)
CVEID:CVE-2015-2625 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2625]
DESCRIPTION:An unspecified vulnerability related to the JSSE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 2.6
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104743 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104743]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:H/Au:N/C:P/I:N/A:N)
CVEID:CVE-2015-1931 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1931]
DESCRIPTION:IBM Java Security Components store plain text data in memory dumps, which could allow a local attacker to obtain information to aid in further attacks against the system.
CVSS Base Score: 2.1
CVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/102967 [http://xforce.iss.net/xforce/xfdb/102967]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
WebSphere Enterprise Service Bus 6.2
WebSphere Enterprise Service Bus 7.0
WebSphere Enterprise Service Bus 7.5
REMEDIATION/FIXES
Please consult the security bulletin Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server July 2015 CPU [http://www-01.ibm.com/support/docview.wss?uid=swg21962931] for vulnerability details and information about fixes.
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 v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] 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
4th September 2015: Original version published
*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. | Help with Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Enterprise Service Bus (CVE-2015-2613) I would like to know details on how vulnerabilities in IBM Java SDK affect Websphere Application Server and in turn, Websphere Enterprise Service Bus product. | CVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]
DESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.
CVSS Base Score: 5
CVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N) |
TRAIN_Q090 | IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.13-TIV-ITM_SQL-IF0001 - United States ITM; SQL; ITCAM; Microsoft Applications DOWNLOADABLE FILES
ABSTRACT
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below
DOWNLOAD DESCRIPTION
Copyright International Business Machines Corporation 2018.
All rights reserved.
Component: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:
Microsoft(R) SQL Server Agent, Version 6.3.1.13
Component ID: 5724B96MO
Interim Fix 0001, (6.3.1.13-TIV-ITM_SQL-IF0001)
Date: May 14, 2018
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 Notices
1.0 General description
=======================
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below.
2.0 Problems fixed
==================
2.1 APARS:
-------------------
APAR: IJ00433
Abstract: The collector process is crashing while accessing invalid
parameter of the request.
Additional Information: Customized SQL query result attribute group
(KOQCSQLR) request uses 3 parameters & other attribute groups use 2
parameters. The memory for the third parameter was not handled properly.
And accessing this parameter by other attribute group would result
into crash.
APAR: IJ00815
Abstract: Device Detail attribute AUTOGROWTH behaviour not in sync
with SQL Server.
Additional Information: In case when data file autogrowth was disabled
and max-size was set to unlimited, then the incorrect values were
displayed for filegroup detail attribute(Max Growth Size) and device
detail attribute(Growth).
APAR: IJ01540
Abstract: False alerts are being generated as default value "Not
Collected" for "Database Space Pct Used" attribute is not correctly
converted before sending to TEPS.
Additional Information: Situations having default value
[ Not Collected (-1 ) ] in formula were not getting evaluated correctly
for some database detail attributes. However, the data was shown
correctly as ‘Not Collected’ on the portal.
APAR: IJ05451
Abstract: ITCAM SQL Server Agent's collector process crashes when using
SQL Server Native Client 10.0 or SQL Server Native Client 11.0 as
ODBC driver.
Additional Information: Collector was not able to handle all possible values
returned by ODBC when using SQL Server Native Client 10.0 and SQL Server
Native Client 11.0 causing it to crash.
2.2 DEFECTS:
-----------------
DEFECT: 170986
Abstract: Memory leak in Table Detail attribute group.
Additional Information: Memory leak observed in Table Detail attribute
group because incorrect de-allocation handling.
DEFECT: 170987
Abstract: Crash observed in Availability group details attribute group
and Table detail attribute group
Additional Information: Crash observed in Availability group details
attribute group and in Table detail attribute group for the wrong
usage of iterator after erase. Issue happened because an attempt to
increment the iterator was made after the iterator was deleted through
erase function.
DEFECT: 170993
Abstract: intial size > max size gives incorrect values
Additional Information: If a database was created with restricted growth
and then modifed the initial size of the database file to a value
greater than it's maxsize, then the value of maxsize was not updated
correctly (ideally in this case maxsize should become equal to initial
size). As a result, query to SQL Server returned false value for
maxsize due to which incorrect values were getting displayed on portal
for attributes in Database Detail, Device Detail and Filegroup Detail
attribute groups.
DEFECT: 170994
Abstract: Incorrect value displayed for Database Detail attributes
when autogrowth disabled and data freespace > drive freespace.
Additional Information: In cases when data file autogrowth was disabled
and data freespace was greater than device freespace then incorrect
value were seen for some attributes(Data Freespace , Aggregate Database
Freespace , Database Space pct used , Aggregate Database Freespace pct,
Database max growth size).
DEFECT: 171127
Abstract: Add tolerance support for SQL Server 2017.
Additional Information: Added support for SQL Server 2017 version.
DEFECT: 171244
Abstract: Spelling mistake in agent configuration panel.
Additional Information: Few spelling mistakes in agent configuration
panel were corrected.
DEFECT: 171318
Abstract: Usage of KOQ_ODBC_DRIVER variable in pre-req while making
sql server connection.
Additional Information: During pre-requisite check, the value of
‘Driver’ was hardcoded to ‘SQL Server‘. While later on, for collecting
data value for 'Driver’ was picked from ‘KOQ_ODBC_DRIVER’ variable.
Due to this, issue was seen during pre-requiste connection but later
on data was being collected successfully.
DEFECT: 171379
Abstract: High Severity vulnerabilities are resolved to avoid undefined
behaviour of the agent.
Additional Information: Removed the high severity errors in the code,
detected in CPPCheck tool.
DEFECT: 171785
Abstract: DBD_TEMP rename failed with error [32]
Additional Information: Renaming of DBD_TEMP to DBD_PREV files was
failing with Error 32 (The process cannot access the file because it
is being used by another process)because DBD_TEMP file handle was
taking time to close.
DEFECT: 171979
Abstract: Incorrect value is being sent when query is failed in SRV1
cursor.
Additional Information: Zero value was being sent when query fails in
SRV1 cursor which was incorrect. Zero is a meaningful value which does
not indicate failure.
DEFECT: 171981
Abstract: Not Collected value is frequently sent since database
detail collection is not getting completed in 45 seconds.
Additional Information: When database detail collection took more
than 45 seconds for collection, Not collected values were sent which
resulted into triggering of situation.
DEFECT: 172173
Abstract: Environment setting for COLL_DBCC_NO_LOCK was not taking
effect. Similar issue was seen with COLL_MONITOR_ALL_DATABASES.
Additional Information: Values were getting overwritten for above two
variables, hence queries were running without NoLock hint and monitoring
of all database setting was not working as expected.
DEFECT: 173699
Abstract: No data get collected for server summary attribute group.
Additional Information: SRV3,one of the pre-cursor of server summary
attribute group, was failing as its query was executed with (null)
option. Hence no data was collected for server summary attribute group.
DEFECT: 174076
Abstract: MSSQLQA: Sometime server detail data is not getting displayed
on portal.
Additional Information: SRV3, one of the pre-cursor of server summary
attribute group, was failing as its query was executed with (null)
option. Hence sometimes server detail data was not getting displayed
on portal.
DEFECT: 174077
Abstract: crypted SQL password in log file.
Additional Information: Encrypted password value in logfile is
replaced with fixed length string to avoid security breach.
DEFECT: 174420
Abstract: Last Statistics Query execution failing for table details
attribute group.
Additional Information: Due to query failure,table detail data was
collected only for the first time. From second collection onwards,
new data was not collected & portal always showed the data collected
during first collection.
DEFECT: 175117
Abstract: Table detail attribute group query was failing for syntax error
at where clause and returned null
Additional Information: The query which gets executed while include/exclude
databases is on, was containing two consecutive "where" and hence
was failing. This issue is seen with SQL Server 2014 and above versions.
DEFECT: 175120
Abstract: Data is not collected properly with the non default SQL
ODBC driver.
Additional Information: Due to incorrect size calculated for some
data types, either query’s result set processing was failing or the
data was getting truncated. As a result data was not getting collected
properly for some attributes.
2.3 Enhancements:
-----------------
RFE: 50594
Abstract: Support AlwaysOn feature for SQL developers edition.
Additional Information: Added support for SQL Server Developers
Edition's AlwaysOn feature.
2.4 Superseded fixes
--------------------
None
2.5 APARs and defects included from superseded fixes
----------------------------------------------------
None
3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Microsoft SQL Server agent prerequisites Document,
version 6.3.1 or from the following link:
http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1 [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=A54AA300920511E292EE9F030925FE1B&duComponent=Server_A5707A80920511E292EE9F030925FE1]
The following link is for the Tivoli operating system and application
support matrix. Please refer to this matrix for the latest
certification information.
http://www-969.ibm.com/software/reports/compatibility/clarity/index.html [http://www-969.ibm.com/software/reports/compatibility/clarity/index.html]
3.1 Prerequisites for this fix
------------------------------
The prerequisite level for this fix is as follows:
Local Agent Upgrade:
- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.13
Remote Agent Upgrade:
- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support
- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.13
- Monitoring Agent for Windows OS, Version V6.23 Fix Pack 3
As this fix is cumulative, it can be installed on any fix level
for this version, release and mod level above the prerequisite.
4.0 Image directory contents
============================
This fix image contains the following files:
- 6.3.1.13-TIV-ITM_SQL-IF0001.README - This is the README file
- 6.3.1.13-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format
- 6.3.1.13-TIV-ITM_SQL-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(R) environment; use the .zip file
if you are working in a Windows(R) environment.
The fix archive file contains the following files:
6.3.1.13-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar
6.3.1.13-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip
6.3.1.13-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab
6.3.1.13-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab
6.3.1.13-TIV-ITM_SQL-IF0001/KOQWINNT.dsc
6.3.1.13-TIV-ITM_SQL-IF0001/KOQWIX64.dsc
6.3.1.13-TIV-ITM_SQL-IF0001/oq_dd.properties
6.3.1.13-TIV-ITM_SQL-IF0001/oq_dd_063113001.xml
6.3.1.13-TIV-ITM_SQL-IF0001/itmpatch.exe
5.0 Installation instructions
=============================
This fix can only be installed over an existing installation.
Use the following steps to install this fix.
5.1 Before installing the fix
-----------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.
- With reference to this README, the symbol <CANDLEHOME> 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 fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Refer to section 7.0 entitled "Known problems and workarounds"
before installation.
- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.
5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(6.3.1.13-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory
on the system that contains the agent code to be updated. For
the purpose of this README, the symbol <TEMP> 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 platforms.
3. Use the "itmpatch" command to install the fix for that agent
platform. For more information on the "itmpatch" command, see
section 6.2.
On Windows systems, if the fix was expanded to
<TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001, the install command is:
For 32 bit Agent:
> <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001\KOQ_winnt_tema_if0001.cab
For 64 bit Agent:
> <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001\KOQ_wix64_tema_if0001.cab
Note : Use "itmpatch" command from <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001\
temporary directory.
5.3 Remote agent update
-----------------------
1. Transfer the appropriate archive file
(6.3.1.13-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of this README, the symbol <TEMP> 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 platforms.
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 Administrator's Guide.
On UNIX systems,
if the fix was expanded to <TEMP>/6.3.1.13-TIV-ITM_SQL-IF0001:
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.13-TIV-ITM_SQL-IF0001
On Windows systems,
if the fix was expanded to <TEMP>\6.3.1.13-TIV-ITM_SQL-IF0001:
> %CANDLE_HOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.1.13-TIV-ITM_SQL-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. Please 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. 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 "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 OQ -n <Managed system name> -v 063113001
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 OQ -n <Managed system name> -v 063113001
Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (oq), not three characters (koq).
- 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. To check if Remote Agent Update is SUCCESS/INPROGRESS/FAILED use the command
>tacmd getDeployStatus -g <transaction id>
where transaction id is the id provided after updateAgent command.
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.
1. Transfer the appropriate archive file
6.3.1.13-TIV-ITM_SQL-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 (koq_tems_teps_tepd_if0001.tar or .zip)
that contains the updates for 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) script to launch either
GUI installation or silent installation of the application
support files.
Note: For IBM Tivoli Monitoring Version 6.3 or above, one
of the following additional steps must be performed.
1. Acquire 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 java(r) 1.5 or java 1.6 installation when running
the itmasi.sh or itmasi.bat script described below.
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>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.
-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.
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.
Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.
Note: Agent support upgrade for IBM Tivoli Monitoring Version 6.3
or above on Linux, zLinux, Solaris and windows operating systems
requires the following files contained in interim fix
6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and
silent installation option of agent support upgrade.
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
- Solaris: setupSolaris.bin
- Windows: setupwin32.exe
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0002.README".
On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]
On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]
where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.
-r <response file> - Required. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and
modified as per your environment.
-j <JAVAHOME> - Optional. The fully-qualified path to the
"bin" directory where Java(R) is installed.
The location of Java on your system might
vary.
5. The next panel presented by the Application Support Installer
asks for the selection of which Tivoli Monitoring components
you want to add application support to.
For this fix, the check boxes should be set as follows:
Checked - Tivoli Enterprise Monitoring Server(TEMS)
Checked - Tivoli Enterprise Portal Server(TEPS)
Checked - Tivoli Enterprise Desktop Client(TEPD)
Continue through the remaining GUI panels selecting the
Microsoft SQL Server 06.31.13.01 support to complete the
installation.
Note: When support is installed using CLI or GUI for any of the
above Tivoli Monitoring components, they are restarted.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed, it
must be restarted.
6.0 Additional installation information
=======================================
Any existing Microsoft SQL Server Agent instances should be restarted
after the installation of this fix.
6.1 Installation instructions for agent baroc file
--------------------------------------------------
Fix (6.3.1.13-TIV-ITM_SQL-IF0001) includes changes to the agent
baroc files which need to be reinstalled. If you have already
installed these baroc files, there are no additional installation
steps. If not, refer to IBM Tivoli Monitoring, Installation
and Setup Guide under "Installing monitoring agent baroc files
on the event server" in "Installing the IBM Tivoli Enterprise
Console Event Synchronization" section for more information.
6.2 Additional information on using "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 must include the drive
letter.
6.3 Verifying the update
------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to 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 OQ
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 OQ
Note:
- The component (-t) for the tacmd "listSystems" command is
specified as two characters (OQ), not three characters (KOQ).
When the agent update is successful, the agent version is:
06.31.13.01.
After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.
For the agent on Windows systems, the version number is
06.31.13.01.
2. To verify the agent support files were updated correctly, use
the "kincinfo" command on Windows systems or the "cinfo" command
on Linux 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 displayed build date and installation date might not
be accurate. This is known problem.
On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:
./cinfo -i
On Windows systems:
-------------------
To validate that all components have been installed, run the
following command:
For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i
C:\Users\Administrator>kincinfo -i
*********** Thursday, May 10, 2018 04:36:22 PM ************
User : Administrator Group : NA
Host Name : HJS497-MSQL-T-1 Installer : Ver: 063007000
CandleHome : C:\IBM\ITM
Installitm : C:\IBM\ITM\InstallITM
*************************************************************
...Product Inventory
OQ TEMS App Support/Microsoft SQL Server Support
WICMS Version: 06.31.13.01 Build: 81136
OQ TEPS App Support/Microsoft SQL Server Support
WICMS Version: 06.31.13.01 Build: 81136
OQ TEPB App Support/Microsoft SQL Server Support
WICMS Version: 06.31.13.00 Build: 71541
OQ TEPD App Support/Microsoft SQL Server Support
WICMS Version: 06.31.13.01 Build: 81136
7.0 Known problems and workarounds
==================================
Abstract: itmpatch command fails during upgrade
Problem: When itmpatch command is executed, it fails while upgrading
agent fix pack. The following error message is
displayed:
Version 06.31.13.XX of product koq is currently installed.
The patch requires that you must have at least version
06.31.13.XX of product installed to apply this patch.
Workaround: Use the itmpatch.exe provided in patch file
6.3.1.13-TIV-ITM_SQL-XXXXXX.zip or
6.3.1.13-TIV-ITM_SQL-XXXXXX.tar file.
Abstract: English characters are getting displayed in Agent support
installer having Non-English language operating system.
Problem: In Non-English language operating system, when agent
support installer is executed it shows English characters.
Workaround: None
Abstract: Installing support for patch fails on ITM 6.3.0
Problem: When you try to install the support for this patch on ITM
6.3.0, the installation fails with following error:
The wizard cannot continue because of the following error:
could not load wizard specified in /wizard.inf (104)
Workaround: Use the pre-packaged binaries for itmasi available at:
http://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]
Abstract: Crash encountered in event viewer for koqagent.exe
Problem: Sometimes while stopping the koqagent process, the collection
process is not getting completed. When koqagent.exe stops, the
thread spawned by it gets terminated forcefully. Hence it's
causing a crash.
Workaround: None
Abstract: Application support installation fails on Non Windows OS.
Problem: While installing the application support on the machines
having Operating system other than windows, the support
installation using ASI fails if the temporary directory
where the patch files are extracted has spaces.
Workaround: Use the temporary directory without space.
Abstract: MSSQL Agent collector crashes.
Problem: Sometimes the job 'syspolicy_purge_history' fails and
the collector crashes.
Workaround: 1. Disable scheduling of system job 'syspolicy_purge_history'.
2. Disable detail trace logging.
Abstract: MSSQL Agent collector does not auto-restart.
Problem: When agent is configured with non admin user, it fails
to auto-restart if it needs to be.
Workaround: Restart the agent manually from MTEMS window.
8.0 Additional product information
==================================
None
9.0 Notices
===========
This information was developed for products and services offered in
the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services
currently available in your area. Any reference to an IBM product,
program, or service is not intended to state or imply that only that
IBM product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any
IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any
non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
The following paragraph does not apply to the United Kingdom
or any other country where such provisions are inconsistent
with local law:
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 states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply
to you.
Trademarks and service marks
----------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].
Microsoft, Windows, Windows NT, and the Windows logo are trademarks
of Microsoft Corporation in the United States, other countries, or
both.
Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. in the United States, other countries, or both.
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.
PREREQUISITES
ITCAMMA: Microsoft SQL Server Agent, Version 6.3.1.13
INSTALLATION INSTRUCTIONS
Please refer to the README contained in the Description section above for general installation instructions.
DOWNLOAD PACKAGE
HOW CRITICAL IS THIS FIX?
Recommended
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.3.1.13-TIV-ITM_SQL-IF0001 14 May 2018 English 38639539 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Microsoft+Applications&fixids=6.3.1.13-TIV-ITM_SQL-IF0001&source=SAR] [ ]
[/support/docview.wss?uid=swg24044840&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044840&aid=2]Problems (APARS) fixed
IJ00815, IJ00433, IJ01540 | Does ITCAM MSSQL agent support SQL Server 2017? Does MSSQL monitoring agent support SQL Server 2017?
The compatibility matrix only mentions SQL Server 2016:
https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=D67CBA30151E11E7B7E234686CAD92CE&osPlatforms=Windows&duComponentIds=S009&mandatoryCapIds=62|45 | Added support for SQL Server 2017 version. |
TRAIN_Q091 | IBM Unable to decrypt the FIPS key error when exporting keys from IBM Datacap Taskmaster Capture - United States dcskey gnk; dc_KTF.xml TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When attempting to generate and/or export keys using the dcskey command, you receive the error, "Keys couldn't be exported. Unable to decrypt the FIPS key"
CAUSE
Enabling the Use FIPS compliant algorithms for encryption, hashing and signing security policy can cause this error
RESOLVING THE PROBLEM
To allow the keys to be exported properly:
1. Select Local Security Policy under Administrative tools
2. Navigate to Local Policies - Security Options
3. Select System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing and be sure it is Disabled
4. Run dcskey e again to export the key | Keys couldn't be imported. Unable to encrypt the FIPS key On windows10 machine when I attempt to import the encryption key I am getting the error: "Keys couldn't be imported. Unable to encrypt the FIPS key". Because I cannot import the keys, I am unable to validate parameters. | To allow the keys to be exported properly:
1. Select Local Security Policy under Administrative tools
2. Navigate to Local Policies - Security Options
3. Select System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing and be sure it is Disabled
4. Run dcskey e again to export the key |
TRAIN_Q092 | IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States java.io.NotSerializableException SessionObjectSize counter PMI enabled disable serializable TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When PMI (Performance Monitoring Infrastructure) is enabled with SessionObjectSize counter enabled, getting NotSerializableException. The SystemOut.log shows something similar to:
[4/10/07 5:25:42:618 EDT] 00000091 SessionContex E Exception is: java.io.NotSerializableException: com.com1.dept.nls.model.someModel
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code))
...
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(CompiledCode))
at com.ibm.ws.webcontainer.httpsession.SessionContextMBeanAdapter.getSessionsInfo(SessionContextMBeanAdapter.java(Compiled Code))
at com.ibm.ws.webcontainer.httpsession.SessionTrackingPMIApplicationData$1.getRuntimeInfo(SessionTrackingPMIApplicationData.java(Inlined Compiled Code)) ...
at com.ibm.ws.pmi.server.modules.ServletSessionsModule$SessionObjSize.updateStatistic(ServletSessionsModule.java(Compiled Code))
at com.ibm.ws.pmi.server.data.SpdStatExternal.updateExternal(SpdStatExternal.java(Compiled Code))
at com.ibm.websphere.pmi.server.PmiAbstractModule.update(PmiAbstractModule.java(Compiled Code))
...
The error does not affect application functionality. Disabling SessionObjectSize counter makes the error stop occurring.
CAUSE
WebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.
RESOLVING THE PROBLEM
The application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface.
HISTORICAL NUMBER
53925
L6Q
000 | ClassCastException IlrStorePolicy$SerializedENamedElement incompatible with EStructuralFeature
We keep getting the following error when navigating in Decision Center on Websphere Application Server.
java.lang.ClassCastException: ilog.rules.teamserver.web.IlrStorePolicy$SerializedENamedElement incompatible with org.eclipse.emf.ecore.EStructuralFeature
Does anyone know how we can avoid this error?
| WebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.
RESOLVING THE PROBLEM
The application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface. |
TRAIN_Q093 | IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States WMB IIB SECURITY BULLETIN
SUMMARY
WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability.
VULNERABILITY DETAILS
CVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]
DESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V10.0 & V9.0
WebSphere Message Broker V8.0
REMEDIATION/FIXES
Product VRMF APAR Remediation/Fix IBM Integration Bus V10
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]
The APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]
The APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker
V8
IT15719 An interim fix is available from IBM Fix Central for all platforms.
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibms~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719]
The APAR is targeted to be available in fix pack 8.0.0.8
For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]
WORKAROUNDS AND MITIGATIONS
None known
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.
IMPORTANT NOTE
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
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] ACKNOWLEDGEMENT
None
CHANGE HISTORY
27 Oct 2016 - Original version Published
*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.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0
PRODUCT ALIAS/SYNONYM
WMB IIB | Help with Security Bulletin: WMB & IIB are affected by Open Source Tomcat vulnerability (CVE-2016-3092) I need to understand details regarding Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092). Where can I find this information? | CVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]
DESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.
CVSS Base Score: 5.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) |
TRAIN_Q097 | IBM Too Many Open Files error message - United States wasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
This technote explains how to debug the "Too many open files" error message on Microsoft Windows, AIX, Linux and Solaris operating systems.
SYMPTOM
The following messages could be displayed when the process has exhausted the file handle limit:
java.io.IOException: Too many open files
[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.
New sockets/file descriptors can not be opened after the limit has been reached.
CAUSE
System configuration limitation.
When the "Too Many Open Files" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.
RESOLVING THE PROBLEM
Determine Ulimits
On UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value.
Display the current soft limit:
ulimit -Sn
Display the current hard limit:
ulimit -Hn
Or capture a Javacore, the limit will be listed in that file under the name NOFILE:
kill -3 PID
Please see the following document if you would like more information on where you can edit ulimits:
Guidelines for setting ulimits (WebSphere Application Server)
http://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]
Operating Systems
Windows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http://technet.microsoft.com/en-us/sysinternals/bb896653]. This tool identifies the open handles/files associated with the Java™ process (but usually not sockets opened by the Winsock component) and determines which handles are still opened. These handles result in the "Too many open files" error message.
To display the handles, click on the Gear Icon [/support/docview.wss?uid=swg21067352&aid=1] in the toolbar (or press CTRL+ H to toggle the handles view). The icon will change to the icon for DLL files (so you can toggle it back to the DLL view).
It is important that you change the Refresh Rate. Select View > Update Speed, and change it to 5 seconds.
[/support/docview.wss?uid=swg21067352&aid=2] [/support/docview.wss?uid=swg21067352&aid=2]
There is also another Microsoft utility called Handle that you can download from the following URL:
https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx [https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx]
This tool is a command line version of Process Explorer. The URL above contains the usage instructions.
AIX
The commands lsof and procfiles are usually the best commands to determine what files and sockets are opened..
lsof
To determine if the number of open files is growing over a period of time, issue lsof to report the open files against a PID on a periodic basis. For example:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
This output does not give the actual file names to which the handles are open. It provides only the name of the file system (directory) in which they are contained. The lsof command indicates if the open file is associated with an open socket or a file. When it references a file, it identifies the file system and the inode, not the file name.
It is best to capture lsof several times to see the rate of growth in the file descriptors.
procfiles
The procfiles command does provide similar information, and also displays the full filenames loaded. It may not show sockets in use.
procfiles -n [PID] > procfiles.out
Other commands (to display filenames that are opened)
INODES and DF
df -kP filesystem_from_lsof | awk '{print $6}' | tail -1
>> Note the filesystem name
find filesystem_name -inum inode_from_lsof -print > filelist.out
>> Shows the actual file name
svmon
svmon -P PID -m | grep pers (for JFS)
svmon -P PID -m | grep clnt (for JFS2, NFS)
(this opens files in the format: filesystem_device:inode)
Use the same procedure as above for finding the actual file name.
Linux To determine if the number of open files is growing over a period of time, issue lsof to report the open files against a PID on a periodic basis. For example:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
The output will provide you with all of the open files for the specified PID. You will be able to determine which files are opened and which files are growing over time.
It is best to capture lsof several times to see the rate of growth in the file descriptors.
Alternately you can list the contents of the file descriptors as a list of symbolic links in the following directory, where you replace PID with the process ID. This is especially useful if you don't have access to the lsof command:
ls -al /proc/PID/fd
Solaris Run the following commands to monitor open file (socket) descriptors on Solaris:
pfiles
/usr/proc/bin/pfiles [ PID ] > pfiles.out
lsof
lsof -p [ PID ] > lsof.ou t
This will get one round of lsof output. If you want to determine if the number of open files is growing over time, you can issue the command with the -r option to capture multiple intervals:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
It is best to capture lsof several times to see the rate of growth in the file descriptors.
HP-UX
lsof
lsof -p [ PID ] > lsof.out
This will get one round of lsof output. If you want to determine if the number of open files is growing over time, you can issue the command with the -r option to capture multiple intervals:
lsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out
It is best to capture lsof several times to see the rate of growth in the file descriptors.
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK | Too many open files error cause Portal server out of service after a restart due to Hardware failure. After experienced a Hardware problem (OS shutdown totally), client start Portal Server and run for some time. Then they found the Portal out of service. The backend log shows lots of error related with Too Many Open Files | On UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file/socket usage. Additionally, file descriptor leaks can still occur even with a high value.
Display the current soft limit:
ulimit -Sn
Display the current hard limit:
ulimit -Hn
Or capture a Javacore, the limit will be listed in that file under the name NOFILE:
kill -3 PID |
TRAIN_Q098 | IBM Restoring missing xml files from backup in DASH - United States DASHL2; DASHL2FAQ; restore; backup; xml; WEB-INF TECHNOTE (FAQ)
QUESTION
How can I restore missing or corrupted xml files in the WEB-INF directory, (such as the navigation.xml, portletEntities.xml, etc.) from backup in Dashboard Application Service Hub (DASH) ?
CAUSE
Some of these files could have gotten corrupted.
ANSWER
DASH makes a backup copy of the WEB-INF configuration/custom xml files in the backups directory. These files are very useful if any of these files get corrupted.
Please follow below steps to restore files from the backups directory:
1. Stop the DASH server
2. Make a backup copy of the current xml files in the following directory:
<JazzSM_Home>/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF
3. Go to <JazzSM_Home>/profile/backups and find a backup file from a previous day/time that contains the missing xml files
Example: isc_stores_backup_1427324004938.zip
4. Unpack the zip file to a temporary location.
5. Restore these files in the WEB-INF directory from the backup.
6. Start DASH
7. Test if you can access the DASH Portal. | Restore JazzSM DASH login page to default images We've changed the JazzSM DASH login page images and want to restore them. What values do we use to revert those changes? | 1. Stop the DASH server
2. Make a backup copy of the current xml files in the following directory:
<JazzSM_Home>/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF
3. Go to <JazzSM_Home>/profile/backups and find a backup file from a previous day/time that contains the missing xml files
Example: isc_stores_backup_1427324004938.zip
4. Unpack the zip file to a temporary location.
5. Restore these files in the WEB-INF directory from the backup.
6. Start DASH
7. Test if you can access the DASH Portal. |
TRAIN_Q100 | IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003) - United States DOWNLOADABLE FILES
ABSTRACT
This Fix Pack addresses problems reported in IBM Tivoli Business Service Manager 6.1.1
DOWNLOAD DESCRIPTION
*************************************************************
* A change introduced by this Fix Pack is incomplete but will not
* adversely affect existing function.
*
* Please refer to APAR(s) IV76788 for a description of the
* problem(s) and corrective action(s).
*
* Evaluate this APAR for the potential impact in your environment.
*
* Please refer to APAR(s) IV79769 for a description of the
* problem(s) and corrective action(s).
*
* Evaluate this APAR for the potential impact in your environment.
*
* A change introduced by this Fix Pack might negatively
* affect existing product function.
*
* Please refer to APAR IV79769 for a description of the
* problem and corrective action. See tech note for more details:
* http://www-01.ibm.com/support/docview.wss?uid=swg24041505 [http://www-01.ibm.com/support/docview.wss?uid=swg21968610]
*
* Evaluate this APAR for the potential impact in your environment.
*
* Please refer to APAR(s) IV91142 for a description of the
* problem(s) and corrective action(s). APAR IV71513 introduced in FP3
* may affect performance in rare circumstances.
*
* Evaluate these APARs for the potential impact in your environment.
*************************************************************
IBM Tivoli Business Service Manager 6.1.1
Fix Pack Version 6.1.1-TIV-BSM-FP0003
Readme file for: IBM Tivoli Business Service Manager
Product/Component Release: 6.1.1
Update name: Fix Pack 3
Fix ID: 6.1.1-TIV-BSM-FP0003
Publication Date: July 6, 2015
Last modified date: July 3, 2015
Online version of the readme file:
http://www.ibm.com/support/docview.wss?uid=swg24039742 [http://www.ibm.com/support/docview.wss?uid=swg24039742]
Attention: You can always find the most current version of the readme file online.
Contents
1.0 Files included in this Fix Pack
2.0 Hardware and software requirements
3.0 Installation information
3.1 Dependencies
3.2 Prerequisites
3.3 Special considerations
3.4 Superceded Fixes
3.5 Extracting Fix Pack files
3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX
3.5.2 Extracting on Windows platforms
3.5.3 Fix pack directories
3.6 Maintenance upgrade strategy
3.6.1 Example maintenance scenario
3.7 Installation
3.7.1 Installing the Fix Pack
3.7.2 Discovery Library Toolkit
3.8 TBSM agent
3.9 Uninstalling the Fix Pack
3.10 Recovering from a failed Fix Pack install
3.11 Restoring failed DE upgrade from backup
3.12 "Service Level Objectives (SLO) Reporting" function
4.0 Additional information for TBSM Fix Pack 2 APARS
4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS
4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING
ON RADEVENTSTORE
5.0 List of APARs
5.1 TBSM 6.1.1 Fix Pack 3 APARS
5.2 TBSM 6.1.1 Fix Pack 2 APARS
5.3 TBSM 6.1.1 Fix Pack 1 APARS
5.4 Tivoli Integrated Portal
5.5 Jazz for Service Management (JazzSM)
6.0 New support and features
6.1 TBSM 6.1.1 Fixpack 3
6.2 TBSM 6.1.1 Fixpack 2
6.3 TBSM 6.1.1 Fixpack 1
6.4 Additional Browser Support with Fixpack 3
6.5 Additional Browser Support with Fixpack 2
6.6 eWAS Fixes and Upgrades
6.7 OMNIbus 8.1
6.8 DB2
6.9 TADDM 7.3 Integration
7.0 Known issues
7.1 Some date options in TBSM Reports do not work
7.2 Issues creating wire between Service Tree and Active
Event List (AEL)
7.3 TBSM Agent Chart title differs from name in the
drop down list
7.4 Minimize-restore does not restore to correct size for
Service Navigation->Data Fetchers on Internet Explorer(IE) 9
7.5 Portlets covering content in a free form page
7.6 Creation and deletion of Services and Templates that contain
special characters
7.7 WEBSERVICES SECURITY NOT FUNCTIONAL
7.8 If using WEBSERVICES SECURITY (WSS) user authentication
7.9 Microsoft Internet Explorer 11
7.10 With certain Solaris installations the Event Summary portlet
may fail render
7.11 TIP Portlet blank or does not load after TIP 2.2.0.15
installation
7.12 TIP chart portlet blank if TBSM Service Admin page is
closed and re-opened
7.13 TBSM integration with ISM is no longer operational
7.14 Java Security Warnings
8.0 Copyright and trademark information
=======================================================================
1.0 Files included in this Fix Pack
-------------------------------
Fix Pack 3 addresses the problems that have been reported in IBM®
Tivoli® Business Service Manager version 6.1.1. The following table
contains a list of files included in this Fix Pack and operating systems
associated with these files:
+---------+----------------------------------------------------------------+
| Platform| File |
+---------+----------------------------------------------------------------+
| AIX® | 6.1.1-TIV-BSM-FP0003-aix.tar |
| | |
+---------+----------------------------------------------------------------+
| Linux® | 6.1.1-TIV-BSM-FP0003-linux.tar |
| | |
+---------+----------------------------------------------------------------+
| Solaris | 6.1.1-TIV-BSM-FP0003-solaris.tar |
| | |
+---------+----------------------------------------------------------------+
| Windows®| 6.1.1.-TIV-BSM-FP0003-windows.zip |
| | |
+---------+----------------------------------------------------------------+
| zLinux | 6.1.1-TIV-BSM-FP0003-zlinux.tar |
| | |
+--------------------------------------------------------------------------+
|all platforms| 6.1.1-TIV-BSM-FP0003.README |
+-------------+------------------------------------------------------------+
|all platforms| 6.1.1-TIV-BSM-FP0003.README_Translated.zip |
+-------------+------------------------------------------------------------+
Note: Whenever <ARCH> is used in the text of this readme, as part of the
filename of the Fix Pack package, it refers to, and can be
substituted for one of the following operating systems:
* Linux
* Solaris
* AIX
* Windows
* zLinux
The following files have been updated or replaced by this Fix Pack.
Added files on the Data Server:
ObjectServer_DS_config.ant
tbsm_generic_ant_caller.bat
tbsm_generic_ant_caller.sh
TBSM_BusCompCreateShadows.js
TBSM_BusCompPlaceAllCIsByIdentifier.js
TBSM_BusCompShadowTechnologyGroups.js
TBSM_ResEnrichReaderRecycle.js
ApplyPoliciesFor611FP3
BSM_TemplateUpdates611FP0003.radsh
setJVMSettings.jy
setJVMSettings.bat
setJVMSettings.sh
smack-3.3.0.jar
smackx-3.3.0.jar
org.apache.axis2-woden.jar
ipa-1.0-20120430.jar
TDWHistory.xml
Files under tbsm/tools directory
Replaced files on the Data Server:
ASQLStore.class
BSM_Templates.radsh
BSM_Templates_updatepropagation.radsh
BSM_Templates_templates_only.radsh
BSM_Templates_instances_only.radsh
canvasOpenURLActions.xml
collect_logs.ant
fo_config.ant
fo_data_config.ant
tbsm_consistency.zip
setTraceLevel.jy
scriptedAPIStartup.bsh
MigrateUserActionscanvasDynamicSubMenuActions_X.xsl
MigrateUserActionscanvasOpenURLActions_X.xsl
tbsm_viewDefinitionFiles.lst
tbsmDataImport.xml
VisualRepresentationAttributes.xml
av.jar
tbsm-info.jar
itmdataclient.jar
maintcli.jar
ncs.jar
tbsm-jviews.jar
ncsagent.jar
ncsSoapClient.jar
ncChartComponent.jar
new-server.xml
RAD_namevalidator.props
TBSM_BusCompPlaceAllCIsByAttr.js
TBSM_markerChangeProvider.ipl
TBSM_ResEnrichMain.js
TBSM_SLAUpdateServiceEvent.ipl
TBSM_AV_GetColorForSeverity.ipl
update-ear.py
versioninfo.bat
versioninfo
verutil.jar
Files under tbsm/contrib/gistools
Replaced Impact files on the Data Server:
nciJmxClient.jar
nci.jar
If you have made changes to the above mentioned files you will
find your copy of the file under:
- Copy of scriptedAPIStartup.bsh (scriptedAPIStartup.bsh.orig)
can be found in the same directory as the original.
- The copy of the files can be found in the following
directory:
[InstallDirectory]/
tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003/data
If Service Level Objectives (SLO) Reporting was previously deployed,
then the following policy files will also be overwritten by this Fix
Pack:
TBSM_createBusinessCalendarDefn.js
TBSM_createServiceDefinition.js
TBSM_recordSLAMetric.js
TBSM_serviceDowntimeBasedOnTBSMStatusChange.js
TBSM_slaDefGlobalSettings.js
TBSM_serviceDefinition.js
TBSM_db2GetData.js
TBSM_getDataFromTBSMAvailability.js
TBSM_BusinessCalendar.js
---
Added files on the Dashboard Server:
ObjectServer_DS_config.ant
tbsm_generic_ant_caller.bat
tbsm_generic_ant_caller.sh
about_icon22.png
about_thumb.png
setJVMSettings.jy
setJVMSettings.bat
setJVMSettings.sh
Replaced files on the Dashboard Server:
canvasviewer_simple.html
tbsm-jviews.jar
tbsm-symbol-palette.jar
rad_nodes_links.css
LaunchTBSM.nova
RAD_help_eclipse.props
RAD_sla.props
RAD_namevalidator.props
serviceTreePortletView.jsp
serviceNavigatorPortletView.jsp
CreateDBPoller.jsp
ActionLoader.jsp
delete_template.jsp
About.jsp
esda_model.jsp
actionLoader.jsp
serviceViewerPortletView.jsp
autopop_config.jsp
ChartInstanceChooser.jsp
ism_instances.jsp
instanceuserpreferences.jsp
main_ruleset_id_fields.jsp
main_ruleset_rules_list.jsp
main_rulesets_output.jsp
main_rulesets_rules.jsp
main_rulesets_sla.jsp
serviceTreePortletEdit.jsp
serviceViewerPortletEdit.jsp
taguserpreferences.jsp
InstanceCustomizerWizard.jsp
EventRawAttributeSelector.jsp
TBSMCMPopup.jsp
BIRTChartConfig.jsp
columnProperties.jsp
dependency_rule.jsp
EditDBPollerFrames.jsp
ErrorMessageHandler.jsp
main_content.jsp
main_ruleset.jsp
main_rulesets_security.jsp
main_service.jsp
main_service_security.jsp
main_tabs.jsp
main_view.jsp
ServiceInstanceDependents.jsp
LaunchDataBrowser.jsp
rawattributeWizard/raw_event_table_fragment2.jsp
RAD_AV_GetColorForSeverity.ipl
radlabels*.properties
ncs.jar
ncsSoapClient.jar
ncChartComponent.jar
av.jar
itmdataclient.jar
ipa-1.0-20120430.jar
itmdataclient.jar
nci.jar
nciClient.jar
ncCommon.jar
tbsm-info.jar
web.xml
collect_logs.ant
fo_config.ant
fo_data_config.ant
Policies.jsp
TypeBrowser.jsp
impactAdmin.properties
ROIEffReportIWidget.xml
setTraceLevel.jy
versioninfo.bat
versioninfo
verutil.jar
Files under impactAdmin.war/scripts
Files under sla.war/dojo
Files under sla.war/audit/dojo
Files under twa.war/dojo
RAD_dashboard_dataprovider.props
timeSeriesSearchDialog.jsp
timeSeriesPortletView.jsp
tbsm-ltwd-server.jar
Replaced Impact files on the Dashboard Server:
nciClient.jar
nciJmxClient.jar
NCICLUSTER-EIC_configure.html
TBSMCLUSTER-EIC_configure.html
NCICLUSTER-new1twin.html
TBSMCLUSTER-new1twin.html
NCICLUSTER-newrwin.html
TBSMCLUSTER-newrwin.html
If you have made changes to the above mentioned files you will
find your copy of the file under:
- The copy of the files can be found in the following
directory:
[InstallDirectory]/
tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003/dash
---
Added files associated with the Discovery Library Toolkit:
remove_merged_resources.xml
migration/loadTaddmJars.bat
migration/migrateTaddmModel.bat
migration/loadTaddmJars.sh
migration/migrateTaddmModel.sh
migration/migrateClassFilters.xml
migration/etc/userPasswordPrompt.properties
db-checkupbeforecleanup.sql
Replaced files associated with the Discovery Library Toolkit:
scc_refreshnamingcommitchanges.sql
scc_checkfordupsinstage.sql
scc_processcreatecomponents.sql
scc_remove_merged_resources.sql
NamingRules.xml
genStep1SqlForTADDMFromOrm.xsl
genStep2SqlForTADDMFromOrm.xsl
genTheSQLTADDMFromOrm.xsl
ScrProducePostProcessingSql.xsl
xmltoolkitsvc.properties
ASICLTools.jar
setdbshema.[sh|bat]
createidmlbook.sql
db-cleanup.sql
If you have made changes to the above mentioned toolkit files you will
find your copy of the files under:
[InstallDirectory]/tbsm/XMLtoolkit/log/install/maintenance/backup/611FP0003
---
TBSM agent packages are available for download from the TBSMAgent
directory on the support download site. The TBSMAgent code was last
updated with TBSM 6.1.1 Fixpack 1
=======================================================================
2.0 Hardware and software requirements
----------------------------------
For information about hardware and software requirements, see the
Tivoli Business Service Manager Installation Guide on the IBM
Tivoli Business Service Manager Information Center (at IBM Knowledge Center):
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/welcome.htm [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/welcome.htm]
To apply this Fix Pack you will need 3 GB of disk space. Please check
the amount of space you have before you install, as the installation
will fail if you run out of space.
=======================================================================
3.0 Installation information
------------------------
3.1 Dependencies
This Fixpack must be installed on each server(s) that is running
the TBSM data server or TBSM dashboard server.
This Fixpack requires IBM Tivoli Business Service Manager
Version 6.1.1 to be installed.
3.2 Prerequisites
-------------
Tivoli Integrated Portal 2.2.0.15 version 2 (v2) has been certified. It
can be installed after installing this fix pack.
IBM strongly recommends updating to TIP FP 2.2.0.15 v2, if support is
required for FF ESR 31 and IE11. If the TBSM data server and dashboard
server are installed on different machines, the TIP Fix Pack needs to be
installed only on the dashboard server. In case of a TIP HA environment,
the HA nodes need to be disjoined first before upgrading to TIP FP.
See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]
Post installation of TIP 2.2.0.15 v2 requires a re-start of the
Dashboard server and clearing of all user's browser cache!
3.3 Special considerations
----------------------
Consider this information before you install the Fix Pack:
1. You will be prompted during the installation to specify a backup
directory name. The installer backs up DE at this location.
2. This Fixpack does not backup the entire application. It only
backs up the files that it has updated/replaced. A backup copy of the
original files can be retrieved from:
[InstallDirectory]/tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003
3. The TBSM and TIP processes or services may remain running but, will
be re-started during the Fix Pack install process. If the processes
or services are manually stopped, prior to the Fix Pack install,
please make sure both the OMNIbus Object server and DB2 processes or
services remain running!
NOTE: The installer will start/stop the TBSM and TIP services as
needed, during the install process.
On Linux/Unix: perform the following
1. To stop the TBSM Data server issue the following command:
$TIP_HOME/profiles/TBSMProfile/bin/stopServer.sh server1
-username <adminuser> -password <adminpassword>
2. To stop the TBSM Dashboard server, issue the following
command:
$TIP_HOME/profiles/TIPProfile/bin/stopServer.sh server1
-username <tipadminuser> -password <adminpassword>
By default, username is tipadmin and password is the
tipadmin password.
3. To stop the TBSM Discovery Library Toolkit issue the
following command:
$TBSM_HOME/XMLtoolkit/bin/tbsmrdr_stop.sh
On Windows:
1. In the Start menu, click Settings -> Control Panel
-> Administrative Tools -> Services.
The Services window opens. Depending on what services
you have installed, the available services are as follows:
Tivoli Business Service Manager - TBSMProfile_Port_17310.
This is the Data server.
Tivoli Integrated Portal - V2.2_TIPProfile_Port_16310.
This is the Dashboard server.
Tivoli BSM Discovery Library toolkit
EIF probe
This service appears only if the EIF probe was installed
as a Windows service.
2. Right-click the service that you want to stop and click Stop.
4. All non-vital programs should be closed prior to installation of
the Fixpack.
3.4 Superceded Fixes
----------------
6.1.1.0-TIV-BSM-IF0001 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0002 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0003 is superceded by this Fix Pack.
6.1.1.0-TIV-BSM-IF0004 is superceded by this Fix Pack.
6.1.1-TIV-BSM-FP0001 is superceded by this Fix Pack.
6.1.1-TIV-BSM-FP0002 is superceded by this Fix Pack.
3.5 Extracting Fix Pack files
-------------------------
3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX
platforms
1. Copy the file 6.1.1-TIV-BSM-FP0003-<ARCH>.tar to a temporary
location on your TBSM Server.
2. Unpack the file on each host where you need to install the Fix
Pack using these commands:
tar -xvf 6.1.1-TIV-BSM-FP0003.<ARCH>.tar
3.5.2 Extracting on Windows platforms
-------------------------------
1. Copy the 6.1.1-TIV-BSM-FP0003-windows.zip file to a temporary
location on your TBSM server host.
2. Unzip the file on each server where you need to install the Fix Pack.
3.5.3 Fix pack directories
--------------------
When you extract the file, these directories are created:
TBSM -TBSM data server and dashboard server and TIP updates.
DiscoveryLibrary -Discovery Library Toolkit updates
<ARCH>/Reports
Samples
3.6 Maintenance upgrade strategy
----------------------------
Before you install the Fix Pack, you need to plan how and when you will
upgrade each TBSM server in your environment.
3.6.1 Example maintenance scenario
----------------------------
In this example, the maintenance is staged into two phases to
reduce the time required for the TBSM maintenance window.
In this example environment, there are four servers:
* primary data server
* backup data server
* two dashboard servers set up for load balancing called: dash1
and dash2
Follow this sequence:
Before you start the maintenance window:
1. Upgrade backup data server
2. Upgrade one dashboard server (for example dash2)
3. Use the primary data server and dash1 for regular production
activities
After you complete the upgrade the two secondary servers, start
the maintenance window down time for the production servers.
1. Upgrade primary data server
2. Upgrade dash1
After you complete the upgrade for all the servers:
1. Start primary data server
2. Start backup data server
3. Wait until TBSM completes the server synchronization.
4. Start the dashboard servers.
3.7 Installation
------------
3.7.1 Installing the Fix Pack
-----------------------
[Fix Pack] Refers to the directory where you extracted the Fix
Pack files from the zip/tar file.
Attention: Install the Fix Pack with the same user that was
used to install TBSM 6.1.1 GA
NOTE: If you have deployed the Service Level Objectives (SLO)
Reporting Function, you must do the following before
installing the Fix Pack:
- Stop all Impact services that are running policies that
call the SLO functions to record data in the SLORPRT
database. If you have the service set to start at
server startup, then turn this option off before
installing the fixpack, as the server is restarted
during the fixpack install.
Running the install without DE backup:
If you prefer to backup DE with your own procedures you can
run the install with the following parameter.
-DNO_BACKUP=true
(for Silent Install, uncomment the "NO_BACKUP=true"
parm on the setupFP.rsp response file)
If you choose this method, you must backup DE before you install.
And restore the original system using your backup/restore
procedures or utilities (if uninstalling the Fix Pack).
Follow this procedure to install the Fix Pack:
1. On the Tivoli Business Service Manager server host, change to the
[Fix Pack]/TBSM directory where you extracted the files.
2. Run the installation using one the following commands:
* setup-windows.exe - Windows.
* setup-<unixplatform>.bin - other operating systems.
Installation command options:
GUI mode No options, for example:
Windows: setup-windows.exe
or
UNIX® : ./setup-<unixplatform>.bin
Console mode
Use the -i console option.
For example -
Windows: setup-windows.exe -i console
or
UNIX® : ./setup-<unixplatform>.bin -i console
Silent Mode
a. Copy setupFP.rsp from the TBSM directory of the extracted
Fix Pack file ([Fix Pack]/TBSM) to a location it can be
edited (/tmp).
b. Update the file to match your environment.
c. Confirm acceptance of license, by un-commenting this line
and setting the parm to "true":
#LICENSE_ACCEPTED=false
d. Run:
Windows: setup-windows.exe -f C:\tmp\setupFP.rsp
or
UNIX® :setup-<unixplatform>.bin -f /tmp/setupFP.rsp
Note: The response file needs to have a fully qualified
path.
3. During the install you will be asked to to verify
path names to the TIP install.
4. Restart both the Data and Dashboard processes/services
5. After install is complete (and with the data server started), run
the script ApplyPoliciesFor611FP3, which can be found on the Data
Server under $TBSM_HOME/bin. This script loads the new/updated
policies.
NOTE: Do not run the ApplyPoliciesFor611FP3 on the secondary/
backup data server of a failover pair. This only needs to
be run on the primary data server.
On Windows:
ApplyPoliciesFor611FP3.bat <adminuser> <adminpassword>
For example - ApplyPoliciesFor611FP3.bat tipadmin tipadmin
On Linux/Unix:
./ApplyPoliciesFor611FP3 <adminuser> <adminpassword>
For example - ./ApplyPoliciesFor611FP3 tipadmin tipadmin
NOTE: Verify that the admin user id and password are
correct otherwise, the script will fail at the last step.
If incorrect, rerun the script with a valid adminuser id
and password.
6. From the TBSM 6.1.1 Fix Pack 3 install media, copy these files
onto the DB2 server (where the tbsmdb was initially installed,
when TBSM was first setup).
from: [Fix Pack]/TBSM/TBSMDBChecker
to: [InstallDirectory]/tbsmdb/bin
TBSM_Check_DB.bat
TBSM_Check_DB.sh
tbsmDatabaseChecker.xml
TBSMDBChecker.props
NOTE: The above action is only needed if you ever plan to use
the TBSM_Check_DB script, which will now suppress the
display of the requested user password.
7. After installing this Fix Pack, end-users may need to clear their
browser cache, close and re-open the browser; in order to avoid
any issues on the client side.
8. If the Impact "Service Level Objectives (SLO) Reporting"
function was enabled, please refer to section 3.12 for additional
post Fix Pack installation required actions.
9. Please refer to section 4.0 "Additional information for TBSM Fix Pack 3 APARS"
for additional post install actions.
3.7.2 Discovery Library Toolkit
-------------------------
1. Navigate to the DiscoveryLibrary directory.
2. To install Fixpack 3,
If you are on a Windows operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.1-FP0003-windows_64.exe
If you are on a Unix operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.1-FP0003-<unixplatform>_64.bin
For console mode, specify "-i console".
Note: If the installer cannot find the TBSM 6.1.1 Discovery
Library Toolkit, verify that the toolkit is installed and
that it was installed by the user that the fixpack is being
installed with. If these are both okay, then set the environment
variable TBSM_TOOLKIT_BASE to the location of the toolkit and
restart the toolkit installer. For example:
Windows:
set TBSM_TOOLKIT_BASE=C:\Program Files\IBM\tivoli\tbsm\XMLtoolkit
UNIX:
export TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit
3. The toolkit installer requires access to the database.
4. Notes and Post-Install Considerations:
a) After installation is complete, you may remove
[fixpack] to save space.
5. Restart the toolkit.
3.8 TBSM agent
----------
Installing the TBSM agent (last updated with TBSM Fix Pack 1):
The following packages are available for download in the TBSMAgent
directory on the support download site:
* AIX: KR9_aix526CD-6.1.1-TIV-BSM-FP0001.tar.gz -AIX (64 bit)
* Linux: KR9_lx8266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li x86_64R2.6(64 bit)
* Solaris: KR9_sol286CD-6.1.1-TIV-BSM-FP0001.tar.gz -Solaris R8(64 bit)
* Windows: KR9_wix64CD-6.1.1-TIV-BSM-FP0001.zip -(64 bit)
* zLinux: KR9_ls3266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li S390R2.6(64 bit)
To install the updated TBSM agent (FP1), if not already installed:
1. Download the appropriate agent code for your platform.
2. Untar or unzip the file.
3. Install the agent according to the directions in the TBSM
Installation Guide. This is a complete install package for the TBSM
agent support and can be used for a fresh install of the agent.
For instructions on installing and configuring the TBSM agent, see:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html]
3.9 Uninstalling the Fix Pack
-------------------------
Before uninstalling the FixPack all TBSM processes should be
STOPPED. The user must manually stop the TBSM processes, before
the uninstall of the FixPack (except for OMNIbus and DB2).
Attention: Uninstall the Fix Pack with the same user that was used to
install TBSM 6.1.1 GA.
Silent mode and uninstall
If silent mode was used for the install, the uninstall will
default to a silent uninstall and you must supply a response
file or the uninstall will fail.
For silent mode uninstalls, copy the setup_uninstall.rsp file
from the Fix Pack image to the directory:
<installDir>/tbsm/_uninst/TBSM611_FP3
and update the file with the correct information. Then launch
the installer specifying the file. For example:
uninstall(.exe) -f /tmp/setup_uninstall.rsp
Note: The response file needs to have a fully qualified path.
On the Tivoli Business Service Manager server system:
1. Change to the directory:
<installDir>/tbsm/_uninst/TBSM611_FP3
2. Run the uninstall command:
UNIX: If you are on a Unix operating system, run the following
command from a prompt.
./uninstall
Windows: If you are on a Windows operating system, run the following
command from a prompt.
.\uninstall.exe
For console mode, specify "-i console"
3. After the command has completed, run the following commands to clear
the server cache.
Linux/AIX: <TIP_HOME>/bin/clearClassCache.sh
Solaris: java -Xshare:dump
Windows: <TIP_HOME>\bin\clearClassCache.bat
4. Uninstall eWAS 7.0.0.35
NOTE: On a "Data server only" environment, the TBSM 6.1.1 Fix
Pack 3 un-installer will not remove the upgraded eWAS
7.0.0.35 Fix Pack it installed. If there are plans to, at
a future time, re-install TBSM 6.1.1 Fix Pack 3, it is
necessary to manually un-install eWAS 7.0.0.35.
These steps DO NOT apply to a "Dashboard sever only"
environment or a "Single server" environment, where both the
Data and Dashboard are installed together.
Again, these steps are only needed on a "Data server only"
environment. Failure to perform these actions, will prevent
the re-install of TBSM 6.1.1 Fix Pack 3!
a). Copy the uninstall-WASEmbeded.txt to a temporary location
The uninstall-WASEmbeded.txt file is located on:
<installdir>/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_WASFP/uninstall-WASEmbeded.txt
For example on Unix:
/opt/IBM/tivoli/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_IAGLOBAL_COI_STEP_WASFP/uninstall-WASEmbeded.txt
For example on Windows:
C:\IBM\tivoli\tbsm\_uninst\TBSM611_FP3\plan\install\MachinePlan_localhost\00002_IAGLOBAL_COI_STEP_WASFP\uninstall-WASEmbeded.txt
Or from the TBSM 6.1.1 FP3 install media:
6.1.1-TIV-BSM-FP0003-<ARCH>\TBSM\COI\PackageSteps\WASFP\uninstall-WASEmbeded.txt
b). Edit the uninstall-WASEmbeded.txt (on the temporary location)
c). locate this line: -W product.location="@IAGLOBAL_WAS_HOME@"
d). Replace above line with: -W product.location="<installdir>/tipv2"
Where <installdir> is the fully qualified directory where tipv2 located:
for example (Unix): -W product.location="/opt/IBM/tivoli/tipv2"
for example (Windows): -W product.location="C:\IBM\tivoli\tipv2"
e). Save the uninstall-WASEmbeded.txt file (on the temporary location)
f). Execute the following command:
On Unix:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.sh -options <templocation>/uninstall-WASEmbeded.txt -silent
for example: /opt/IBM/tivoli_root/tipv2/WebSphereUpdateInstallerV7/update.sh -options /tmp/uninstall-WASEmbeded.txt -silent
On Windows:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.exe -options <templocation>/uninstall-WASEmbeded.txt -silent
for exampe: C:\IBM\tivoli\tipv2\WebSphereUpdateInstallerV7\update.exe -options C:\Temp\uninstall-WASEmbeded.txt -silent
5. Restart the Data Server and Dashboard Server.
Discovery Library Toolkit
===================================================
The Toolkit portion of this fixpack cannot be uninstalled.
A backup copy of the original files can be retrieved from:
[InstallDirectory]/tbsm/
XMLtoolkit/log/install/maintenance/backup/611FP0003
3.10 Recovering from a failed Fix Pack install
-----------------------------------------
If the install fails, try to uninstall in which case, it goes back to
the previous version. If there is no uninstall file under
_uninst/TBSM611_FP3, then nothing really got installed and you can delete
the TBSM611_FP3 file and reinstall.
3.11 Restoring failed DE upgrade from backup
---------------------------------------
To recover a failed Deployment Engine upgrade in TBSM 6.1.1, see the
TBSM Installation Guide at:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html]
3.12 "Service Level Objectives (SLO) Reporting" function
---------------------------------------------------
The information in this section applies only if you have deployed
the Impact Solution called "Service Level Objectives (SLO)
Reporting". The SLO function is enhanced by Fixpack 3 for:
* Support of a time zone specification when creating the SLA
definitions
* Detection of active outages in the sample policy that reads
from a TBSM Metric History database
* Bug fixes and improved documentation
For this function, See the 'SLO Reporting' topic under Impact
6.1.1 at the following url:
http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html [http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html]
If you have NOT deployed this solution, then you can skip this
section!
After installing the Fixpack, but BEFORE restarting any SLO services:
1) Update the SLORPRT database schema
a) You will need access to the machine where the SLORPRT
database was installed. If this database has not been
installed, then the SLO solution has not been deployed
and there is no need to continue this update to the
schema.
b) If necessary, copy files add_timezone.sql and
update_views_timezone.sql from
[InstallDirectory]/impact/add-ons/slo/db
to a location accessible from the system you will use
to update the database schema in the next step.
c) Open a DB2 command window on a system with access to
the SLORPRT database and run the following commands:
db2 connect to SLORPRT user dbuser using dbpassword
( replace dbuser and dbpassword with the
user/password specified in datasource
SLOReportDatasource )
db2 -tvf <slo_sql_dir>/add_timezone.sql
db2 -tvf <slo_sql_dir>/update_views_timezone.sql
db2 connect reset
Where <slo_sql_dir> would be
[InstallDirectory]/impact/add-ons/slo/db if on the
same machine as the Impact Data server, or the directory
where you copied the files in step b if the SLORPRT
database is on a different machine
2) Once the Fixpack is installed and the SLORPRT database
schema has been updated, you should start any Impact
services configured for SLO processing. Remember to check
the option to start the service when the server starts,
if that is how you originally configured the service.
=======================================================================
4.0 Additional information for TBSM Fix Pack 3 APARS:
------------------------------------------------
The following APARs fixed in this service delivery require additional
action by users. If your environment uses or is experiencing the
symptoms described, use the instructions provided to complete the fix.
4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS
Customers are now allowed to persist their log file settings
without manually editing the server.xml file. Currently, customers
use the setTraceLevel script to set the maximum number of log files
and the size of these of files using the following method:
$TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setTraceOutputToFile 30 40
Now they will be able to persist these sizes by using the following
command.
$TBSM_HOME/bin/setTraceLevel.sh <user> <pw> data/dashboard -setstartup
Before this change, the call would only persist changes to the trace
level. Now it persists changes to the trace level as well as the log
file configurations.
4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON
RADEVENTSTORE
The following SQL statements needs to be run after FP install, against
the TBSM DB2 Database:
CREATE INDEX RADEVENTSTORE_IDX1 ON TBSMBASE.RADEVENTSTORE(RADSERIAL) COLLECT STATISTICS
The above SQL statement can be found on the following file:
./tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/AddRADEventStoreIndex.sql
Please provide the above file to the TBSM DB2 Database Administrator,
along with the following Notes:
Notes:
1) Use
cat AddRADEventStoreIndex.sql | db2
to run the SQL. The command must be run against all DB2 databases
used for TBSM. The command does not require a server stop/start.
2) The ; delimiter is not used in the AddRADEventStore.sql file
- whether the delimiter is required or not depends on the
connection settings (-t option).
3) Typical output from the SQL: cat AddRADEventStoreIndex.sql | db2
db2 => db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => DB20000I The RUNSTATS command completed successfully.
4) Typical output from the SQL (if the index already exists)
db2 => db2 => DB20000I The SQL command completed successfully.
db2 => db2 => SQL0605W The index was not created because an index
"TBSMBASE.RADEVENTSTORE_IDX" with a matching definition already exists.
SQLSTATE=01550
db2 => db2 => DB20000I The RUNSTATS command completed successfully.
5) Other warning:
SQL2314W Some statistics are in an inconsistent state. The newly
collected "INDEX" statistics are inconsistent with the existing
"TABLE" statistics. SQLSTATE=01650
To address the message above, RUNSTATS Is Run after the index is
created.
As well as the changes in the index there are 2
configurations changed required for this APAR
a) Increase the number of allowed connections for the TBSMDatabase
Data Source.
This can be done via the Impact GUI screen (Data Model) or via
the file tbsm\etc\TBSM_TBSMDatabase.ds
Increase the number from default 15 to 50 (or to limit
recommended by DB2 Admin)
TBSMDatabase.DB2.MAXSQLCONNECTION=15
to
TBSMDatabase.DB2.MAXSQLCONNECTION=50
If changing via file, then a Data Server restart is required.
b) Set the LOCKTIMEOUT in DB2 to 30 seconds. The default is -1,
which mean no timeout - If you set this parameter to -1, lock
timeout detection is turned off. Setting to 30 seconds means
sessions will only wait for 30 seconds for a lock. Again, this
change should be made in consultation with local DB2
Administrator.
=======================================================================
5.0 List of APARs
-------------
5.1 TBSM 6.1.1 Fix Pack 3 APARs
---------------------------
The following TBSM APARs are delivered with Fix Pack 3:
IV60619 DATA SERVER RESTART REQUIRED TO GET A WORKING DATA FETCHER AFTER DELETION OF DEPENDENT RULE
IV61278 RULE FILTER WITH 'NOT LIKE' ON SUMMARY FIELD MALFUNCTIONS
IV64797 SETDBSCHEMA -F A COMMAND SHOULD ALSO RESET THE RESENRICHREADER SERVICE. : 611
IV65695 FO_CONFIG SCRIPT DOES NOT CONFIGURE SET TBSM_B_IMPACTDB.DS DATA SOURCE PARAMETERS IN A FAILOVER ENVIRONMENT. : 611
IV65825 XMLToolkit: Single Quotes not Encoded on IDML file generation: 611
IV65947 ACCESSING CLOB DATATYPES IN TBSM DATABASE CAUSES DB2 ERROR, SQL0270N : 611
IV65949 ACCESSING TBSM DATABASE VIEWS WITH IN TBSM CAUSES DB2 ERROR : 611
IV65958 TBSM DATABASE QUERIES THAT USE MAX, MIN, DISTINCT, VIEWS CAUSES DB2 ERROR, SQL0243N : 611
IV66535 TOOLKIT ISSUE RELATED TO STATEMENT RTERMINATION CHARACTERS: 611
IV66950 TBSMEVENTREADER STOPS : THE REAL FIX FOR IV65545 IS TO FIX THE TXN CODE : 611
IV71255 SELECT STATEMENTS USED FOR LOGGING PURPOSES IN DB-CLEANUP.SQL SCRIPT NEED TO BE COMMENTED OUT. : 611
IV72005 IMPACT SLO FUNCTION
5.2 TBSM 6.1.1 Fix Pack 2 APARs
---------------------------
IV62456 OOM DUE TO CIRCULAR REFERENCES
IV62548 SAME SESSION CONTEXT USED FOR ALL RADSHELL SESSIONS, TRIGGERED FROM POLICIES
IV60168 MODIFIED 'TBSM_NUMERICATTRIBUTEFUNCTIONS' POLICY DOESN'T GET EXPORTED
IV56853 RADSHELL IMPORT FAILS DUE TO ORPHANED CHILD SERVICE
IV63608 AFTER FIX FOR APAR IV32754 SEE SQLSTATE=42704 EXCEPTION FOR TBSMSCR.SCCP_COMPCLASS IN TOOLKIT LOGS
IV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS
IV65786 TBSM CIRCULAR REFERENCES ISSUE
IV59886 TBSM DOES NOT RE-READ EVENT READER PROPS FILES AUTOMATICALLY WHEN YOU CONFIGURE/ENABLE EVENT ENRICHMENT
IV61880 INFINITE LOOP IN DATA SERVER CAUSED BY MALFORMED OFFLINE TASK
IV64950 DB2 ERROR DB2 SQL ERROR: SQLCODE=-805
IV60750 NUMERICAL RULES NOT CALCULATED ON TBSM RESTART
IV60961 CONCURRENTMODIFICATIONEXCEPTION THROWN WHEN YOU SELECT THE GUI FIND INSTANCE FUNCTION IN THE SERVICE AVILABILITY PORTLET
IV61199 TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUPOUT CHANGES
IV62273 CONCURRENTMODIFICATIONEXCEPTION ERRORS IN DASHBOARD LOG
IV62294 NUMERIC AGGRIGATION RULE CHANGES NOT SAVED
IV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT
IV64933 [NetcoolTimeoutException] Log file exceptions when persisting ESDA instances
IV65545 TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON RADEVENTSTORE
IV66210 NULLPOINTEREXCEPTION DISPLAYED ON SYSTEM STATUS ON FAILBACK
IV65484 TBSM: DISPLAY NAME IN PERSISTENT SERVICE MODEL NOT BEING UPDATED
IV68113 DELTA IMPORTS NOT WORKING FOR BUSINESS APPLICATIONS WITH IMPORTING FROM TADDM 7.3 TO TBSM 6.1.1 FP1
IV60842 QUERY CONCATENATION PROBLEM WHEN THE PROPERTY 'DL_LIFECYCLESTATE_FILTER' IS ENABLED
IV56450 NULL POINTER EXCEPTION AFTER CLICKING ON 'FIND INSTANCE'
IV65991 DOCS ABOUT CONFIGURING FOR HTTP ACCESS INCORRECT
5.3 TBSM 6.1.1 Fix Pack 1 APARs
---------------------------
The following TBSM APARs are delivered with Fix Pack 1:
IV21679 MODEL CLEANUP NEEDED AFTER ALIAS CHANGES
IV30875 ERROR CTGBC0053E WHEN SELCTING SERVICE IN A CANVAS
IV33717 ADVANCED THRESHOLD LOOKS CORRUPTED WHEN IT CONTAINS SINGLE SPACE CHARACTERS
IV36878 Dont create rules with ' character'
IV38053 MAINTENANCE SCHEDULE IS NOT WORKING
IV38471 ADD LONGPARENTSERVICENAME TO THE TBSM REPORTING DATA MODEL.
IV38574 SERVICE TREE COLUMNS DO NOT RESIZE TO FIT WHEN PORTLET RESIZES SMALLER.
IV39167 NEED ABILITY TO LOGIN USING UID AND HAVE CN IN TIP BANNER
IV39517 ESDA RULE DIALOG DOES NOT ALLOW PARENT TEMPLATE CHOICE
IV39796 MAINTENANCE SCHEDULE WITH ADJACENT TIME WINDOWS CAUSING LOOP
IV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER
IV42657 SERVICE STATUS INCORRECT
IV42941 COMPONENT COMPOSITES NAME TOO LONG IMPORTED FROM TADDM
IV43098 SERVICE TREE REFRESH UPON CLICKING OR EXPANDING
IV43165 INSTANCE PROPAGATION IN PLACE FOR SERVICES IMPORTED FROM TADDM BECAUSE OF RULE ON SCR_RETRIEVEDEPENDENTOBJECTSTEMPLATE
IV43469 TBSM HANGS DURING AUTOPOP - DATA SERVER IN WAIT LOOP
IV43804 VERSIONINFO ON A SPLIT SERVER, DATA SERVER IS INCOMPLETE
IV43865 SERVICE INSTANCE CONTAINING CHINESE/NLS CHARS GENERATES ERROR TCTUI1003E
IV44246 SOME INTERMEDIATE SERVICES MISSING EVENTS IN SERVICE DETAILS PORTLET
IV44582 TBSM 6.1.0 CONCURRENTMODIFICATIONEXCEPTION MESSAGE DISPLAYED.
IV45166 ITM POLICY DATA FETCHER CREATION - TBSM REMEMBERS ORIGINAL HOST DETAILS
IV45386 THE COLOR OF MAXSEVERITYRAWEVENTS NOT CORRECTLY HANDLED.
IV45868 THE SERVICE VIEWER DOES NOT LAUNCH ON ITALIAN CLIENT SYSTEMS
IV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER
IV46811 COMMA IN TEMPLATE NAME CAUSES ILOG.VIEWS EXCEPTION
IV46876 UNABLE TO LAUNCH LEL FROM HTTP SERVER
IV48813 ERROR POP UP WHEN SERVICE AVAILABILITY PAGE IS LAUNCHED
IV49791 SECURITY ROLE IS NOT ACTED ON, WHEN ESDA INSTANCES ARE BELOW
IV50625 CROSS-SITE SCRIPTING VULNERABILITY AT TBSM 6.1.0.1
IV53791 EVENT COUNTS FOR PARENT SERVICES IS NOT ALWAYS UPDATED
IV54197 TBSM DISCOVERY LIBRARY TOOLKIT REQUIRES UPDATES TO INTEGRATE WITH FUTURE TADDM RELEASES
IV54587 TBSM AGENT - TEPS WORKSPACE TITLE DOES NOT MATCH WHAT IT SHOWS
IV55756 TBSM 6.1.1 ESDA POPULATION CAUSES OUTOFMEMORY IN TBSM DATA
IV56050 ERROR : JAVA.LANG.ERROR: JSFSECURITYPHASELISTENER - POSSIBLE
IV56270 OUTOFMEMORY: USERPROFERENCESSTORE FOR CHILD RELATIONSHIP ATTRIBUTES IS NO
IV57273 REQUEST ERROR IN BOTH VIEWS OF TBSM SERVICE INDICATORS
IV59723 CROSS-SITE SCRIPTING VULNERABILITIES INVOLVING 3 JSPS
IV61668 NETCOOLTIMEOUTEXCEPTION WHEN ESDA DISCOVERS TRIGGERS POLICY
List of TBSM APARs that have updates to the documentation:
IV54828 GET REQUESTS FROM DASH WIDGETS TO TBSM DATA SERVER
There is a new property (impact.dataproviderupdateprocessorintervalsecs), that
defines the interval at which the data provider fires status change updates.
IV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER
The ObjectServer_DS.ObjectServer.FAILOVERPOLICY parm can be
changed (in the TBSM_HOME/etc/(TBSM or TBSM_B)_ObjectServer_DS.ds
file by either manually editing the file (as shown on the
Install Guide) or running this new command, with either of
the three listed values:
Windows:
%TBSM_HOME%\bin\tbsm_generic_ant_caller.bat ObjectServer_DS_config.ant <parm>
Unix:
$TBSM_HOME/bin/tbsm_generic_ant_caller.sh ObjectServer_DS_config.ant <parm>
Available values:
1. DISABLE - configure to only connect to Primary Object Server
2. FAILOVER - configure FAILOVER back and forth between Object Servers but,
only if connection is lost. This is the Default (if NULL' is used)
3. FAILBACK - configure to FAILBACK to Primary Object Server, as soon as it is available.
IV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER
#
# ---------------------------------------------------------------
# (Optional) Specifies a alias for building MSS Id. By default,
# the TADDM hostname is used. But in cases there TADDM is
# configured in failover, objects imported from the Primary
# TADDM and Backup TADDM will have different hostnames
# used for building MSS. This will mean 2 MSS associated
# with objects.
#
# When setting a string for the alias, use the primary taddm
# hostname.
#
DL_AliasForMSS = PrimaryTaddmHostname
#
# Note: Launch in Context uses the MSS hostname to build the
# sourceContactInfo value, which is used to contact the TADDM
# server. For this reason, when TADDM is configured in Failover,
# a front end server (load balancer) is required, to route Launch
# In Context requests to the active server. This will ensure
# requests are routed to the secondary TADDM server, when the
# primary is down.
IV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS
The property "UseESDAIdentifiersOnly" can be added, as an
additional parameter to the child Template, which will allow
users to select if they want previous event identifiers on a
service to be kept or erased with each invalidation.
When set to "true", all previous event identifiers will be
erased from TBSM memory model at each invalidation and the
service will only accept identifiers from ESDA policies or via
SCR API. When set to "false", all event identifiers, old or
newly added will be preserved for the service. User must
manually delete event identifiers that they do not wish to
keep. This is TBSM's default behaviour.
IV65786 TBSM CIRCULAR REFERENCES ISSUE
There will be two new properties added in TBSM_sla.props file
that governs the check:
Property name: impact.sla.servicetreedepthlimit
Description: When the data is imported from TADDM, a depth
limit check will be done to the corresponding service tree
during invalidation to ensure that the service tree has normal
relationship data. This property governs the depth limit for
the service tree. If the system detects a service tree with
depth level larger than the value set by this property, a
warning service instance will be created to warn the user to
review their data relationship.
Default value: 20
Property name: impact.sla.disableimportalldescendantslimitcheck
Description: When set to "true", the service tree depth limit
will not be checked during invalidation.
Default value: false
IV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT
The APAR handles the issue of TBSM Failover settings for Data
Sources. Impact back-end java code handled whether or not
failover (or failback) is initiated in times of Data Source
failure. This back-end Impact code only uses the
FAILOVERPOLICY settings in the .ds files
The APAR change has been in the TBSM interfaces to setting up
Data Source. There are 2 interfaces 1) GUI screen (as above)
and 2 radshell (createDataSource and export functions).
1) TBSM GUI: The TBSM GUI will now set the FAILOVERPOLICY
setting in the .ds file. When editing existing files, if
no valid FAILOVERPOLICY exists, then the current
DISABLEFAILOVER setting will be used to determine a new
FAILOVERPOLICY setting, i.e. if no valid FAILOVERPOLICY
exists, then if DISABLEFAILOVER is true, FAILOVERPOLICY
will be set to DISABLED. If DISABLEFAILOVER is false,
FAILOVERPOLICY will be set to FAILOVER
Take good note of the above. It means that existing data
sources will have a new FAILOVERPOLICY set, when they are
first saved via the GUI. Previously if FAILOVERPOLICY was
not valid, Impact assumed FAILOVER. But if you edit a data
source, and the data source has DISABLEFAILOVER = true,
and no valid policy set, then the new value for
FAILOVERPOLICY is DISABLED. This is correct behaviour, but
different to before. The best was to avoid any confusion,
it to check each .ds file and ensure that a valid
FAILOVERPOLICY is set. Do this either by editing the files
(in which case a Data Server restart is required) or by
opening each data source in the GUI. Not all Data Sources
will appear in the GUI (as some are built in). For these,
check the files. If editing files, ensure no spaces at the
end of settings. The only valid values for FAILOVERPOLICY
are DISABLED, FAILOVER and FAILBACK.
2) radshell: The Radshell interface also changes. The export()
function will now export the failover policy, and the
createDataSource takes a policy parameter (in place of the
boolean disablefailover parameter), Also, the old
createDataSource radshell function, will still work (for
backward compatibility with old exports). Note: Data Sources
exported with IV62246 in place, will NOT work on old
systems-as the generated radshell command will contain a
policy string.
The following IMPACT APARs are delivered with Fix Pack 3:
IV27869: related to PMR 15590,SGC,724 - For 6.1.1 Impact
- The latest build should be installing version 2.2.0.2 of
VMMObjectServerPlugin
IV50058: IMPACT SERVER FAILS TO WORK PROPERLY WITH ANY SPACES IN CONFIGURABLE PROPS FILES
IV58590: SNMPTRAPACTION FAILS ON 2ND TRAP WHEN PROCESSING MULTIPLES
IV59481: UNABLE TO SEND HIBERNATIONS TO CLUSTER MEMBERS WHENEVER DIRECTSQL IS BEING USED
IV59770: DATA ITEMS RETRIEVED FROM A DIRECTSQL'S SELECT ARE NOT ABLE TO BE UPDATED
IV60438: IMPACT POLICY WIZARD (XML) FAILS WITH JAVA.LANG.NULLPOINTEREXCEPTION
IV61538: MWM WINDOWS DO NOT ADJUST FOR DST
IV61725: GETSCHEDULEMEMBER FUNCTION ISSUE
IV63535: UNABLE TO PERFORM DECRYPTION OF INPUT VALUE - DATA SOURCE ACCOUNT GETTING LOCKED
IV63942: SESSION.SENDCOMMAND IN A JS POLICY DOESN'T RETURNS ANY RESPONSE
IV64075: NullPointerExceptions
IV64837: IMPACT MWM WINDOW CREATED WITH WRONG END DATE
IV65055: GET/SETGLOBALVARIABLES DO NOT WORK WITH ACTIVATE FUCNTION
IV65179: LOCAL VARIABLES NOT RESTORED AFTER HIBERNATION
IV66164: ADD RECURRING MW WINDOW
IV67091: TBSM FAILOVER BACKUP NOT STARTED CORRECTLY IF STARTED TOO SOON
IV67829: ITM/TEPS DATA DISPLAYED INCORRECTLY IN UI
IV68383: DEBUG FLAG GENERATES MEMORY ISSUES WHEN NON OMNIBUS EVENTS ARE PROCESSED
IV69164: POLICY USES HIBERNATION WILL NOT WAKE UP
IV70836: COMMANDRESPONSE ERROR IN JS POLICY
IV71157: ACTIVATE FUNCTION CALLED FROM WITHIN POLICY SUB-FUNCTION HAS NO EFFECT
IV71513: EVENT IS NOT BEING PROCESSED CORRECTLY AFTER HIBERNATION
IV73098: EVENTS OCCURING ONE HOUR BEFORE ONE TIME WINDOW GOING INTO MAINTENANCE
IV73243: XSS ISSUE IN PROJECTNAME PARAMETER
The following IMPACT APARs are delivered with Fix Pack 2:
IV18554: 511:EVAL FUNCTIONALITY HAS CHANGED FROM 4.1 TO 5.1.1
IV23315: UPGRADE FROM IMPACT 5.1.1 TO IMPACT 6.x DISTRIBUTED [611]
IV64152: SECONDARY NODE CAN'T BIND TO THE NAME SERVER
IV61089: INSTALL FAILS AT STARTWAS STEP
IV63137: IMPACT 6.1.1 REPLICATION FROM PRI TO SEC NOT WORKING
IV62792: 1.2 GB WAS BEING FILLED BY BLANKS FROM LOGGER FUNCTION
IV61956: DATA MODEL NOT SORTED IN ALPHABETICAL ORDER
IV61746: IMPACT 611 FP1 INSTALL FAILS WHEN INSTALLING ON GA 611, WHICH HAS BEEN FIRST UPGRADED FROM IMPACT
IV61399: NULL VALUE ON FIELD, DASH WIDGET SPINS TO MANY TIME MAKING DATA VEIW VERY SLOW TO VIEW.
IV60005: DATA TYPE NOT SAVED CORRECTLY IF FEILD DELETED AND REMAINDER RE-ORDERED.
IV60253: TEPS UIDP NOT CLEARING CACHE, CAUSING MEMORY LEAKS.
IV58616: DIRECTSQL EXECUTE CAUSES EXCEPTION IN POLICY EXECUTION
IV58511: EMAIL READER SERVICE DOES NOT HANDLE EMAILS THAT USE A NON-STANDARD CHARACTER SET
IV53717: JMS MESSAGE LISTENER SERVICE NOT STOPPING PROPERLY
IV56745: IMPACT IS UNABLE TO HANDLE EXCEPTIONS FROM A WEBSERVICES CALL
IV56068: IMPACT THREADS INCREASING WHEN WEBSERVICES SECURITY IS ENABLED
IV55989: HIDDEN/DELETED FIELDS NOT BEING REMOVED FORM OPERATOR VIEW
IV50329: WEBSERVICES SECURITY NOT FUCTIONAL
IV56541: CONFVMM4NCOS SCRIPT IN IMPACT 6.1 IS NOT WORKING AS EXPECTED
IV47748: CAN'T LOAD WEBSERVICE LIBRARIES THAT HAVE JAVA OR JAVAX PACKAGES IN THEM
IV55464: UNABLE TO CREATE A BUTTON ON JAZZ AFTER JAZZ FP2
IV60923: USING THE DIRECTSQL APPROACH AND HAS IDENTIFIED THE NON-REFRESH OF THE SCHEMA ON USERNAME UPDATE IN THE DSA AS SECURITY RISK
IV59920: NO MEANS OF ENCRYPTING IMPACT.OBJECTSERVER.SECUREPASSWORD THAT WILL ALLOW AUTHENTICATION TO AN OBJECT SERVER USING FIPS
The following IMPACT APARs are delivered with Fix Pack 1:
IV11728: USING EVENTREADER PARSERESTRICTIONFILTER TO ALLOW THE USE OF GETDATE()
IV21717: ONE TIME MAINTENANCE WINDOWS DO NOT ADJUST FOR DST
IV22560: ANALYZE EVENT MAPPING TOOL FAILS AND HAMMERS CPU
IV33973: JMS READER DOES NOT CONVERT ACTIVEMQMAPMESSAGE DATA FOR TRANSFER TO SECONDARY CLUSTER MEMBER
IV34503: "OPTIMIZE LIST" OPTION DOESN'T REFLECT THE APPLIED CHANGES TOTHE LIST IN THE "RESTRICT FIELDS", WITHIN THE EVENTREADER
IV35827: ERROR PRODUCED IN NETCOOL.LOG WHEN USING AN EVENTREADER WITH A BLANK FILTER VALUE
IV35885: IMPACT NEEDS TO CHECK USER CREATED SERVICES, FOR WITH NAMES THAT END WITH A "_SERVER".
IV35940: RETURNEVENT() FUNCTION WITHIN DATABASEEVENTREADER ADDED UNWANTED SINGLE QUOTES TO THE IDENTIFER FIELD IN THE SQL "VIA" STATEMENT
IV36405: THE CONFVMM4LDAP COMMAND IS SHIPPED WITH IMPACT 6.1, BUT IS NOT DOCUMENTED
IV36503: MWM CALENDAR: USING FORWARD BY ONE MONTH CAN LEAD TO NON-EXISTENT DATES BEING CREATED
IV37040: USING "NCI_COLLECT_LOGS" UTILITY IN A GUI SERVER ONLY INSTALL DOES NOT WORK.
IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
IV37717: IMPACT 6.1 FP1 OPVIEW SOAP ERROR
IV37759: INTERNAL DATATYPE STRING VALUE IS INTERPRETED AS AN INTEGER IF IT CONTAINS ONLY DIGITS
IV38045: ORACLE DSA ERROR FOR COLUMN NAMES WITH "DOUBLE-QUOTES" AND "NOT-ALL-CAPS"
IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
IV38961: APPLICATION AND DATA NEEDS TO BE VALIDATED.
IV39368: INCREASING CPU WHEN JABBERSERVICE
IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
IV41888: DISABLE THE HIBERNATION STORAGE
IV42715: ERROR WHEN USING # IN IMPACT FILTER FROM DATATYPE DATAITEMS GUI WINDOW
IV43030: IMPACT MISSED ENRICHING FEW EVENTS WHICH OCCURED SIMULTANIOUSLY
IV43751: EVENTPROCESSOR IN A SECONDARY SERVER IS UN-ABLE TO CONTACT PRIMARY SERVER EVENTPROCESSOR.
IV45068: ERROR TRYING TO CREATE SCHEDULE DATATYPE DATAITEM: ERROR MESSAGE: HTTP ERROR 500 INTERNAL SERVER ERROR
IV45511: NEEDED 6.1.1 MWM OPVIEW POLICIES GET OVER-WRITTEN, AFTER MIGRATION FROM EITHER IMPACT 5.X OR 6.1, CAUSING MWM ISSUES
IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
IV45838: OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF SELFMONITORING (DATASOURCE MONITORING) IS ENABLED
IV46099: JMSREPLYTO WAS NOT ABLE TO SET CORRECT QUEUE.
IV46493: ATTEMPTING TO USE DATATYPE FILTERS - "SPECIAL" CHARACTERS BEING CONVERTED TO HTML ENCODING THAT BREAKS OUTGOING SQL.
IV46696: LIMITING THE NUMBER OF CONNECTIONS THAT IMPACT OPENS TO JMS
IV46729: TOPOLOGY WIDGET KEEPS THE OLD LINKS BETWEEN NODES AND DOESN'T CLEAR IT, RESULTING IN AN INCORRECT RELATIONSHIP
IV46799: FUNCTION <FUNCTIONNAME> IS NOT DEFINED BEFORE CALL
IV47058: MWM POLICY SETS SUPPRESESCL FIELD TO 6 IMMEDIATELY AFTER SETTING TO 1.
IV47799: SELECTING 2 KEY FIELDS IN DATA TYPE ON DEFAULTOBJECTSERVER DOESN'T WORK
IV47904: EIC 'TEST SQL' FAILS DUE TO UNSCAPED CHARACTERS
IV47988: SETTING THE WSSETDEFAULTPKGNAME VALUE GLOBALLY DOESN'T WORK WHEN THE WSINVOKE FUNCTION IS INSIDE A POLICY FUNCTION
IV48113: SLOW RESPONSE ON THE POLICY PAGE WHEN ATTEMPTING TO OPEN A LARGE NUMBER OF POLICIES VIA THE GUI
IV50464: JMS TIMEOUT CAUSES POLICY ASSIGNED TO OPERATORVIEW EXECUTE TWICE
IV50932 MAINTENANCE WINDOW EVENT SHOWED STATUS 'NORMAL' - parent apar cancelled
IV51062: DB2 DSA FAILS TO QUERY COLUMN NAMES WITH "DOUBLE-QUOTES AND NOT-ALL-CAPS"
IV53483: CALLDBFUNCTION USAGE IN ORACLE DATABASE WITH FILTER 0=1
IV53810: I10N - TRANSLATION ISSUE
Translation issues in XinY policy and in Browse and Cancel buttons have been fixed.
IV53818: ISSUES WITH INTEGRATIONS ON 611
Web services related issues have been fixed.
IV53822: FIXES FOR HA IN 611 FP1
Issues related to Omnibus failover/failback have been fixed.
IV53824: FIXES IN IMPACT SCRIPTS FOR 611 FP1
Issues in Impact scripts nci_export, nci_import and nci_encryptpolicy have been fixed.
IV53825: THIS APAR INCLUDES FIXES FOR DATA MODEL ISSUES IN 611 FP1
IV53826: FIXES ISSUES IN 611 FP1 WITH POLICIES
IV53827: THIS APAR FIXES SERVICES RELATED ISSUES IN 611 FP1
IV53836: FIXES UI DATA PROVIDER ISSUES IN 611 FP1
IV54939: A MISSING $IMPACT_HOME/LOGS/INSTALL/ DIRECTORY WILL RESULT IN THE NCI_CONFIGURATION_UTILITY PROBLEM
IV55776: UI PROVIDER ENHANCEMENTS IN 611 FP1
This contains UI Provider enhancements where the user can show status and percentage in topology,
tree, table, and list widgets
IV55778: JABBER UPDATES IN 611 FP1
This contains Jabber Updates to use the smack library.
IV55779: ADDITIONAL POLICY FUNCTIONS IN 611 FP1
This contains additional policy functions to escape special characters and filter malicious
content in strings.
IV55780: DSA ENHANCEMENTS IN 611 FP1
DSA enhancements that alert the user when users switch between failover and
failback configuration. Improved handling of network timeouts.
IV55781: SERVICEABILITY IMPROVEMENTS IN 611 FP1
Serviceability improvements, which include improved error messages for
GetHTTP and services.
List of Impact APARs that are marked as updates to the documentation:
IV20165: E-MAIL READER DELETES E-MAILS AFTER READING THEM
The email reader service reads incoming email, and runs
policies based on the contents of the email. To stop the
email reader from deleting emails after you read them, add the
following property to the <EmailReaderName>.props file.
<emailreadername>.deleteonread=false
Where <emailreadername> is the email reader service name.
Restart the service.This only works for IMAP email servers.
IV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}
If a customer is using Object.prototype.toString.call(obj) in
a javascript policy, and wants to follow the javascript
standard, he can add the following property to
NCI_server.props file -
impact.featureToStringAsSource.enabled=false
When the property is set to false, the data follows the
JavaScript standard and the data output by the Log function
is not the same as in IPL. To make the output the same in
JavaScript and IPL, make the value true but this does not
follow the javascript standard.
IV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT
NCI_EXPORT restriction: nci_export will not execute on the
non-primary member of a cluster.
http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/admin/imag_tools_c.html [http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/admin/imag_tools_c.html]
IV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS
In order to make the readEventBuffer store the events for a
longer interval, the number of intervals can be updated. The
default number is 3.
Add the following property to the
<CLUSTERNAME>_<readername>.props. file
(eg NCI_omnieventreader.props file)-
impact.<readername>.numreaderbuffer=4
The default value for this property is 3.
IV40179: ERROR MESSAGES FIRST APPEAR ON 6.1 AND 6.1.1 DURING STARTUP, DUE TO THE FACT THE
NAMESERVER IS NOT INITIALISED YET
When the Impact Server is started during the installation,
the following message is displayed in the netcool.log file:
Unable to login to configured name servers host , port
The message occurs because the Name Server can take time to
initialize while Netcool/Impact starts. You can ignore this
message. It is normal and it disappears when the Name Server
server is initialized.
IV43157: ALL SERVERS IN A CLUSTER ARE REQUIRED TO USE THE SAME ADMIN UID AND PASSWORD
If you are configuring the Tivoli® Integrated Portal profile
for a cluster of servers, you must use the same user name and
password for all the servers in the cluster.
IV44875: SET JREXEC TO LOG TO FILE IS NOT WORKING
Documentation has been updated on JRExec server logging.
IV45481: NO DOCUMENTATION ON THE REQUIRED HTTP AUTHENTICATION FOR THE IMPACT 6.X WEBSERVICES
Documentation has been updated for Impact web services.
IV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF "ORPHANED" FILES, CREATED FOR XINY DATATYPE
A new policy has been added - XINY_DataType_PurgeData - to
remove aged data items. More information can be found in the
Troubleshooting Guide.
IV46185: JAVACALL METHOD FAILS WITH JAVA.LANG.ILLEGALACCESSEXCEPTION-CANNOT ACCESS A MEMBER OF CLASS JAVA.UTIL.HASHTABLE$HASHITERATOR
Documentation has been updated for the NewJavaObject function.
IV46512: THERE'S A NEED TO DOCUMENT THE FACT THAT ONE NEEDS TO RESTART IMPACT FOR JVM TO RELEASE ANY LOADED JAR FILES FOR WEBSERVICES
Documentation has been updated to specify the procedure of
what to do when a user compiles a wsdl file using classes
from a previously compiled file.
IV47057: DATA TYPE QUERY CACHING RETURNING BAD DATA
Documentation on Data caching information has been updated.
IV47454: INSTRUCTIONS ON HOW TO RUN UPGRADE PACAKAGE FOR IMPACT 6.1.1 ON CONSOLE OR SILENT MODE
Documentation on How to upgrade from Netcool/Impact 6.1 in
console mode has been added.
IV50673: INCORRECT/UNCLEAR DOCUMENTATION FOR HANDLING EXCEPTIONS
IV50776: DURING UPGRADE WE WILL OVER WRITE ANY CUSTOMIZED MWM POLICIES WITH NEWER THE MWM DEFAULT POLICY'S VERSIONS
IV51431: NEED TO DOCUMENT THAT DOT NOATION CAN NOT BE USED IN THE NAMING OF POLICIES, SERVICES, DATA TYPES, DATA SOURCES, AND PROJECTS.
Documentation has been updated to note that Dot notation "."
can not be used in the naming of POLICIES, SERVICES, DATA
TYPES, DATA SOURCES, AND PROJECTS.
IV52651: DATABASEREADER NOT WORKING PROPERLY WHEN USING GETUPDATES ON DATABASE TABLE'S TIMESTAMP FIELD
Database event reader service
An additional property can be added to the NCI_XXX.props file
in order to match the the date and time format of the
timestamp field in the external database. Where NCI is the
name of the impact instance and XXX is the name of the
database event reader.
An example of this property is:
impact.XXX.formatpattern=dd-MMM-yy hh.mm.ss.SSS aaa
5.4 Tivoli Integrated Portal
------------------------
The Tivoli Integrated Portal 2.2.0.15 (version 2) should be installed
after installing this FixPack.
The following other components are updated with that version
of TIP:
Driver tip_2.2.0.15 (version 2)
* This driver includes Java SDK version 1.6 SR16 Fix Pack 1
* This driver includes eWAS 7.0.0.35
* Browser support
Microsoft Internet Explorer version 10 & 11
Firefox Extended Support Release (ESR) version 24 & 31
See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]
NOTE: If TIP 2.2.0.15 (version 1) was previously installed, you may
encounter the following issues. Please refer to the following
Technotes for resolution:
- TIP Portlet blank or does not load after TIP 2.2.0.15
installation:
http://www.ibm.com/support/docview.wss?uid=swg21696426 [http://www.ibm.com/support/docview.wss?uid=swg21696426]
- TIP chart portlet blank if TBSM Service Admin page is closed and
re-opened:
http://www.ibm.com/support/docview.wss?uid=swg21696424 [http://www.ibm.com/support/docview.wss?uid=swg21696424]
5.5 Jazz for Service Management (JazzSM)
------------------------------------
If JazzSM UI Services (DASH) is being used to visualize TBSM service model
data, then the latest JazzSM fix pack should be installed after installing this
TBSM FixPack. See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=all]
=======================================================================
6.0 New support and features
------------------------
6.1 TBSM 6.1.1 Fixpack 3
--------------------
Fix Pack 3 includes the following enhancements:
1) Template Editor: sort items in "Rules" table
Adjusting the logic that handles the order of the rules displayed in
the table on the Rules tab. The following are the new rules each
of the columns will adhere to:
Type column
> use the same icon as the toolbar action that created the rule
> tooltips describe the rule's type
Rule Name column
> all rule names are now sorted A-Z
> A-Z ordering maintained as rules are created and/or deleted
> tooltips describe the rule's type; same as Type column
> the display order will not be customer configurable
Rule Settings column
> minor styling tweaks to assist readability
The above enhancement is specific to the TBSM console
2) Tree Template datasets: enable use of internal status attributes in
"Tree Template Editor"
Extended the capability of the Tree Template datasets by allowing
TBSM internal status attributes to be selected on the editor UI's
Template Rule Mapping section.
When Tree Template Viewed in TIP-based Service Tree
Without processing by the customization policy, these new status
attributes will display as the standard TBSM status values:
0.0, 3.0, or 5.0.
The above, enhances the TBSM Data Provider function and benefits
the DASH users.
3) Datasets need a parameter to optionally exclude "starting" or
"container" services.
With the addition of the Tree Template datasets in TBSM 6.1.1
Fixpack 1, we now have more situations where the administrator may
wish to exclude the starting or container service from a view.
The above, enhances the TBSM Data Provider function and benefits
the DASH users.
4) Support parameter to filter datasets in TBSM_Services datasource
by template
The parameter would be available on the datasets in the
TBSM_Services datasource, which includes the "All_TBSM_Services"
and "TBSM_Urgent_Services" datasets
The above, enhances the TBSM Data Provider function and benefits
the DASH users.
5) "UrgentServices" dataset added
This new dataset makes the service model data that was displayed
in the legacy Urgent Services portlet available for display using
the List and Table widgets.
The above, enhances the TBSM Data Provider function and benefits
the DASH users.
6) Managing Dataset Dynamic Updates
All datasets available from the TBSM UI Data Provider automatically
send updates when the content changes. This is the recommended usage
of the TBSM datasets, but there may be scenarios where the user
would like to turn off the dynamic updating.
The above, enhances the TBSM Data Provider function and benefits
the DASH users.
More information can be found in the new "Dynamic Updating and the
TBSM UI Data Provider" document on the TBSM Advanced Topics page at
the TBSM developersWorks site
7) Tivoli Netcool/Impact provides new property to ascertain which Data
Provider field is used, when retrieving ITM data from the REST
Service
8) Enhancements to the Impact Solution called
"Service Level Objectives (SLO) Reporting". The SLO function
is enhanced by Fixpack 3 for:
* Support of a time zone specification when creating the SLA
definitions
* Detection of active outages in the sample policy that reads from
a TBSM Metric History database
* Bug fixes and improved documentation
See the Advanced Topics at the TBSM developerWorks site for new and
updated information:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics]
6.2 TBSM 6.1.1 Fixpack 2
--------------------
1) NUMERICAL RULES NOT CALCULATED ON TBSM RESTART
Numerical Aggregation rules are triggered by a child metric rule
change, i.e. OverallAttribute. When the status of a child changes, the
OverallAttribute metric rule's value will change and any Numerical
Aggregation rules, based on OverallAttribute, will be recalculated.
When TBSM is restarted, only services which have related existing
events will have their status recalculated. Therefore not all Numerical
Aggregation rules (based on OverallAttribute) will be recalculated on
TBSM restart, as some services will be green.
This may not be the desired outcome. On restart, it may be required
that all Numerical Aggregation rules are restarted. New functionality
has been provided for such a scenario, by forcing a bubble up of state
nodes. The code can be triggered from a policy, for leaf nodes
only, or for all, as shown here:
USE_SHARED_SCOPE;
Type="StateModel";
Filter = "RECALCSTATENODESLEAF";
log("Recalc Leaf Node Only. Policy Start." );
GetByFilter(Type, Filter, false);
log("Recalc Leaf Node Only. Policy Finish." );
}
USE_SHARED_SCOPE;
Type="StateModel";
Filter = "RECALCSTATENODESALL";
log("Recalc All Nodes. Policy Start." );
GetByFilter(Type, Filter, false);
log("Recalc All Nodes. Policy Finish." );
}
The above policy code needs to be scheduled from Impact Services on
startup.
2) TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUTPUT CHANGES
If a client wants SLAM event text for a Numerical rule, to update
(even if it's value does not change), the following parm needs to be
un-commented and set to "true"
#If true then send SLAM events, even when the value of a Metric rule does NOT change.
#Default is false.
#Omnibus de-duplication will handle the rest.
#impact.sla.sendslameventsformetricrulealways=true
6.3 TBSM 6.1.1 Fixpack 1
--------------------
1) The BSM_Templates.radsh defines service templates for common TBSM services.
It was executed when you installed the TBSM GA release(not during the fixpack
install). It's default template rules propagate child status to the parent
service based on child template changes. The script has been updated to set
the propagation type to instance propagation. When the child service status
changes, it will propagate the change to the parent service regardless of
which child template rule caused the status change. See the Service
Configuration publication for more information about the aggregation rule
option.
To update the rules with the instance propagation option in your current
installation, you can invoke the
$TBSM_HOME/install/BSM_Templates_updatepropation.radsh script.
If you re-execute the $TBSM_HOME/install/BSM_Templates.radsh script
to re-create the templates, the rules will be configured with
the instance propagation option.
2) The recommended version of JRE plugin is Sun JRE 1.7.0_51 or 1.8 for
Internet Explorer and Firefox.
3) Additional toolkit customization has been made. To pick up these
changes, run the following commands on the Data Server:
Windows:
cd %TBSM_HOME%\install
type BSM_TemplateUpdates611FP0003.radsh | %TBSM_HOME%\bin\rad_radshell
UNIX:
cd $TBSM_HOME/install
cat BSM_TemplateUpdates611FP0003.radsh | $TBSM_HOME/bin/rad_radshell
4) As noted in the following Technote, When configuring pages in DASH
(JazzSM) for TBSM datasets, it is often desirable to create them
in a development environment and then later move them to
production, perhaps via a test environment. With this Fix Pack and
in conjunction with JazzSM 1.1 Fix Pack 2, there is no need to create
two connections any longer.
http://www.ibm.com/support/docview.wss?uid=swg21660077 [http://www.ibm.com/support/docview.wss?uid=swg21660077]
5) TBSM 6.1.1 Fixpack 1 will support the use of a rich hover function in
DASH (JazzSM). The TBSM UI data provider will now send the information
needed in order for a DASH user to configure a widget for rich hover
support. To enable the rich hover in DASH you must:
Configure TBSM 6.1.1 to collect the registry information required to
support the rich hover in TBSM 6.1.1. This configuration is documented
at http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/customization/bsmc_oslc_config_dataserverconfg.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/customization/bsmc_oslc_config_dataserverconfg.html].
The rich hover option will not be available in DASH for widgets
configured with a TBSM dataset if the oslcconfig has not been run.
Configure DASH (UI Services) for access to JazzSM Registry Services.
Configuration of the required property is described at
http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/dash_t_twl_uipreview_resource_reg.html [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/dash_t_twl_uipreview_resource_reg.html].
Note that if enabled in DASH, rich hover will be shown for the same
services that support the rich hover in the TBSM 6.1.1 console. If
configured for a widget, and there is no rich hover information,
then the flyover on the DASH widget will show nothing. Also note
that the DASH environment requires Single Sign On be configured
between the various components required to gather the preview
information (DASH, TADDM, ITM, etc.)
6) TBSM 6.1.1 Fixpack 1 adds a new UI data provider data source that
provides new datasets corresponding to the customer's tree templates.
This allows the same data to be visualized in the legacy Service Tree
as well as on a JazzSM/DASH page.
6.4 Additional Browser Support with Fixpack 3
None!
6.5 Additional Browser Support with Fixpack 2
-----------------------------------------
TBSM 6.1.1 supports FF ESR 10 and FF17 with Fix Pack 1 on TIP 2.2.0.11 (or below).
This Fix pack supports Internet Explorer 9(IE9) in
"Internet Explorer 9" browser mode which is the default mode, not
in "Internet Explorer 9 Compatibility View" browser mode.
The document mode is automatically set by TIP and should remain
'IE7 standards'.
IBM strongly recommends updating to TIP 2.2.0.15 version 2 (v2) if
support is required for FF ESR 24/31 and/or IE10/11
See Fix Central for availability:
http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]
6.6 eWAS Fixes and Upgrades
-----------------------
Please Note: The TBSM 6.1.1 Fix Pack will upgrade WebSphere (eWAS) on the Data
server automatically, to version 7.0 Fix Pack 35 (7.0.0.35) but, only if the Dashboard
server is not installed on that environment. If the Dashboard server is installed on the
same server (in the case of a single server environment), the eWAS will not be upgraded.
eWAS upgrade, on the TBSM Dashboard server and on "Single server" environments, will
take place when TIP 2.2.0.15 is applied.
If un-installing TBSM 6.1.1 Fix Pack, refer to section 3.9 "Uninstalling the Fix Pack"
to manually remove eWAS 7.0.0.35 (on Data server only environments!).
6.7 OMNIbus 8.1
-----------
TBSM 6.1.1 Fix Pack 1 supports the use of OMNIbus 8.1. But, please note that
OMNIbus 8.1 is a separate install, requiring additional configuration changes to
make it work with TBSM. Refer to "IBM Tivoli Netcool OMNIbus Considerations" section
of the "Exploring TBSM" Guide:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_c_netcool_omnibus.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_c_netcool_omnibus.html]
If using OMNIbus 8.1, IBM recommends upgrading to the latest 8.1
maintenance level (at the moment, Fix Pack 2).
If using JazzSM/DASH to display TBSM resources, the Event Viewer and/or AEL may fail to display the appropriate
TBSM events if (1) a Data Source is not setup to point to TBSM's OMNIbus and (2) the custom TBSM filters and views are
not defined to WebGUI. To setup the WebGUI views, it will be required to copy the following file from
the TBSM Dashboard server to a temporary location on the JazzSM server:
<installdir>/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/webtopcore/create_tbsm_views.xml
In addition to copying the file to the JazzSM server, it is necessary to execute the runwaapi command, to load filters/views
the WebGUI. On the JazzSM/DASH server, execute the following command:
<installdir>/netcool/omnibus_webgui/waapi/bin/runwaapi -file create_tbsm_views.xml -user <admin> -password <password>
Please refer to the integration document found in "Advanced Topics"
at the TBSM developerWorks site, for this and other topics:
TBSM developerWorks Advanced Topics: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics]
Integration document: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=7d5ebce8-2dd8-449c-a58e-4676134e3eb8#fullpageWidgetId=Wea1cb2531f10_4ccd_99d7_6ab0334cb21f&file=c6d51b71-362e-44be-8aa2-650da0918ac7 [https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=7d5ebce8-2dd8-449c-a58e-4676134e3eb8#fullpageWidgetId=Wea1cb2531f10_4ccd_99d7_6ab0334cb21f&file=c6d51b71-362e-44be-8aa2-650da0918ac7]
6.8 DB2
---
Starting with TBSM 6.1.1 Fix Pack 2, TBSM supports the use of DB2
version 10.5.3
6.9 TADDM 7.3 Integration
---------------------
For import of Business Applications from TADDM 7.3 to TBSM 6.1.1, the
property com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility
must be set to "true" in collation.properties file (located under
taddm/dist/etc). This will be true by default for upgraded TADDM 7.3
servers. It is false by default for fresh TADDM 7.3 installs.
Note: TADDM restart is required after property modification.
If com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility is
flipped from false to true, then all Business Applications need to be
re-build, to regenerate backward compatible Business Applications. This
can be done by either waiting for scheduler to process all Grouping
Patterns (and recreate new and old Business Applications) or by manually
executing (all or selected) Grouping Patterns from TADDM UI (or command
line).
=======================================================================
7.0 Known issues -
------------
7.1 Some date options in TBSM Reports do not work
When specifying the date parameters for reports, some options
like "last 30 days" do not work. However, one can get this data
for the reports by selecting the Date Range and choosing the
dates from the calendar. Below is a link to the TBSM reports in
our Service Configuration guide which outlines how to run reports.
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/ServiceConfigurationGuide/bsmu_rept_view_reports.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/ServiceConfigurationGuide/bsmu_rept_view_reports.html]
7.2 Issues creating wire between Service Tree and Active
Event List (AEL)
If the user creates a wire between the Service Tree and AEL
when a page is first created, the wire does not work. The
workaround for this is to create a wire by editing the page
after the page has been created and saved.
7.3 TBSM Agent Chart title differs from name in the
drop down list
Name displayed at the top of a TBSM Agent Chart differs from
the name of that chart in the drop down list. For eg,
the chart name in the drop down list is "kr9_TBSM Service Status"
and the name shown at the top of the chart is "Kr9:KR91003".
The name at the top can be changed to display the same name
as the drop down list by going to Preferences and changing
the chart name.
7.4 Minimize-restore does not restore to correct size for
Service Navigation->Data/Data Fetchers on Internet Explorer(IE)9
In the Service Navigation->Data/Data Fetchers portlet, after the
minimize option has been exercised to minimize the portlet, the
portlet is not resized correctly after using the 'restore' option.
The window resizes to a smaller size. This is an issue on
Internet Explorer(IE) 9 but not on Firefox or on Internet
Explorer(IE) 8. In order to go back to the original size,
select 'maximize' and 'restore'.
7.5 Portlets covering content in a free form page
When creating free form pages, the Service Viewer and Active Event
List(AEL) portlets will always be on top of any content. This can
interfere with page layout and editing of portlet preferences.
To alleviate this issue, it is best to place these portlets
onto the created page last to avoid having other content covered
by them. If a page requires editing and contains Service Viewer
or Active Event List portlets, it may be necessary to move
those portlets out of the way before editing preferences of
other portlets.
7.6 Creation and deletion of Services and Templates that contain
special characters
Due to new security additions the deletion of services and templates
that contain the characters '+', '&', '<','>','%',' " ', is not
permitted through the browser. Some of these characters are
permitted on the creation of services, as services can still be
created with these through auto population and importing. The
deletion of these services will now have to be carried out
through the radshell command deleteServiceInstance.
More information on the command can be found here.
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/adminguide/bsma_shlr_service_delete.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/adminguide/bsma_shlr_service_delete.html]
7.7 WEBSERVICES SECURITY NOT FUNCTIONAL
If using WebService Security when making a WebService call,
(callProps.EnableWSS=true), the jar file
tipv2/plugin/org.apache.axis2.jar must be replaced by the jar
file tbsm/lib3p/org.apache.axis2-woden.jar and the newly replaced
file must be renamed to org.apache.axis2.jar.
Restart is required.
7.8 If using WEBSERVICES SECURITY (WSS) user authentication, then the
impact/dsa/wsdsa/wss/conf/wscb.properties needs to be altered to
only have one entry. If there is more than one entry in the file,
only the uid.1 and pwd.1 will be read
7.9 Microsoft Internet Explorer 11.
IE11 (supported only with TIP 2.2.0.15) may cause unexpected
behaviour in the Policy Editor, whereby the Policy List panel
disappears when the Project drop-down menu is selected. To
circumvent this, simply click on a different project in the Project
drop-down list and then click again on the desired project, to
restore the correct layout
7.10 With certain Solaris installations the Event Summary portlet
(Administration -> Service Administration -> Services) may fail to
render and cause an Out Of Memory (PermGen) exception (as seen in
the TIP trace log:
"java.lang.OutOfMemoryError: PermGen space exception")
Solution:
1. Stop TBSM (kill the hung server if necessary).
2. Goto the $TBSM_HOME/tipv2/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1
directory and make a backup of the server.xml file.
3. Open the server.xml file for editing and in the jvmEntries xmi
tag modify the genericJvmArguments attribute to read something
like this, where these two PermSize and MaxPermSize parms are
being added (if other parms are already code, please preserve
those parms and just insert the two new ones):
genericJvmArguments=" -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+DisableExplicitGC"
4. Save the file and restart TBSM.
7.11 TIP Portlet blank or does not load after TIP 2.2.0.15 installation
Refer to the following Technote for resolution:
http://www.ibm.com/support/docview.wss?uid=swg21696426 [http://www.ibm.com/support/docview.wss?uid=swg21696426]
NOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)
7.12 TIP chart portlet blank if TBSM Service Admin page is closed and
re-opened
Refer to the following Technote for resolution:
http://www.ibm.com/support/docview.wss?uid=swg21696424 [http://www.ibm.com/support/docview.wss?uid=swg21696424]
NOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)
7.13 TBSM integration with ISM is no longer operational and will be
removed from the next TBSM version 6.1.1 Fix Pack.
This modification is due to changes in the supported versions of
ITCAM for Transaction / ISM.
7.14 Java Security Warnings
With the ever changing security improvements to both the browsers
Java Runtime Environment (JRE), clients are now more likely to see
warning messages about untrusted connections or invalid
certificates. To avoid those issues, clients can replace the IBM
HTTP Server SSL certificate with an SSL certificate signed by a
third-party CA. For guidance on that task, refer to the following
Technote:
http://www-01.ibm.com/support/docview.wss?uid=swg21424371 [http://www-01.ibm.com/support/docview.wss?uid=swg21424371]
=======================================================================
8.0 Copyright and trademark information
http://www.ibm.com/legal/copytrade.shtml [http://www.ibm.com/legal/copytrade.shtml]
8.1 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.
Intel®, Intel logo, Intel Inside®, Intel Inside logo, Intel® Centrino®,
Intel Centrino logo, Celeron®, Intel Xeon®, Intel SpeedStep®, Itanium®,
and Pentium® are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other
countries.
Other company, product, or service names may be trademarks or service
marks of others.
Please read THE IBM Tivoli Business Service Manager NOTICES AND
INFORMATION in the file notices1.txt included in this Fix Pack before
you proceed with the download and installation of this Fix Pack. You can
find the additional notices file on the same web page as this Fix Pack.
8.2 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.
8.3 Apache Woden Distribution
===============================================
== NOTICE file corresponding to the section 4 d of ==
== the Apache License, Version 2.0, ==
== in this case for the Apache Woden distribution. ==
===============================================
This product includes software developed by
The Apache Software Foundation (http://www.apache.org/ [http://www.apache.org/]).
This product also includes software developed by :
- IBM Corporation (http://www.ibm.com [http://www.ibm.com/]),
WSDL4J was the initial code contribution for the Apache Woden
project and some of the WSDL4J design and code has been reused.
- The W3C Consortium (http://www.w3c.org [http://www.w3c.org/]),
Common W3C XML Schema and DTD files are packaged with Apache Woden.
Please read the different LICENSE files present in the root directory of
this distribution.
===========================================================================
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/ [http://www.apache.org/licenses/]
===========================================================================
WODEN SUBCOMPONENTS:
For any subcomponents included with the Woden source code that contain
separate copyright and license terms, their License information is appended
below, in this file.
For any binary subcomponents redistributed with Woden under separate
licenses, their license files are included alongside those binary packages
in the Woden release files (for example, alongside the dependant jar files
in the /lib directory of the Woden zip file).
===========================================================================
For the W3C schema and DTD files in the org.apache.woden.resolver package:
W3C® SOFTWARE NOTICE AND LICENSE
http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 [http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231]
This work (and included software, documentation such as READMEs, or other
related items) is being provided by the copyright holders under the following
license. By obtaining, using and/or copying this work, you (the licensee) agree
that you have read, understood, and will comply with the following terms and
conditions.
Permission to copy, modify, and distribute this software and its documentation,
with or without modification, for any purpose and without fee or royalty is
hereby granted, provided that you include the following on ALL copies of the
software and documentation or portions thereof, including modifications:
The full text of this NOTICE in a location viewable to users of the
redistributed or derivative work.
Any pre-existing intellectual property disclaimers, notices, or terms and
conditions. If none exist, the W3C Software Short Notice should be included
(hypertext is preferred, text is permitted) within the body of any redistributed
or derivative code.
Notice of any changes or modifications to the files, including the date changes
were made. (We recommend you provide URIs to the location from which the code is
derived.)
THIS SOFTWARE AND DOCUMENTATION IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE
OF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.
The name and trademarks of copyright holders may NOT be used in advertising or
publicity pertaining to the software without specific, written prior permission.
Title to copyright in this software and any associated documentation will at all
times remain with copyright holders.
____________________________________
This formulation of W3C's notice and license became active on December 31 2002.
This version removes the copyright ownership notice such that this license can
be used with materials other than those owned by the W3C, reflects that ERCIM is
now a host of the W3C, includes references to this specific dated version of the
license, and removes the ambiguous grant of "use". Otherwise, this version is the
same as the previous version and is written so as to preserve the Free Software
Foundation's assessment of GPL compatibility and OSI's certification under the
Open Source Definition. Please see our Copyright FAQ for common questions about
using materials from our site, including specific terms and conditions for packages
like libwww, Amaya, and Jigsaw. Other questions about this notice can be directed
to [email protected].
Joseph Reagle <[email protected]>
Last revised $Id: copyright-software-20021231.html,v 1.11 2004/07/06 16:02:49 slesch Exp $
===========================================================================
For license see the new SAX site at
http://www.saxproject.org/ [http://www.saxproject.org/] for more up-to-date
releases and other information. Please change your bookmarks.
SAX2 is Free!
I hereby abandon any property rights to SAX 2.0 (the Simple API for
XML), and release all of the SAX 2.0 source code, compiled code, and
documentation contained in this distribution into the Public Domain.
SAX comes with NO WARRANTY or guarantee of fitness for any
purpose.
David Megginson, [email protected]
2000-05-05
=======================================================================
8.4 IBM obtained Smack V3.3.0 under the following license from Apache Software Foundation:
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/ [http://www.apache.org/licenses/]
PREREQUISITES
IBM Tivoli Business Service Manager 6.1.1
INSTALLATION INSTRUCTIONS
3.7 Installation
------------
3.7.1 Installing the Fix Pack
-----------------------
[Fix Pack] Refers to the directory where you extracted the Fix
Pack files from the zip/tar file.
Attention: Install the Fix Pack with the same user that was
used to install TBSM 6.1.1 GA
NOTE: If you have deployed the Service Level Objectives (SLO)
Reporting Function, you must do the following before
installing the Fix Pack:
- Stop all Impact services that are running policies that
call the SLO functions to record data in the SLORPRT
database. If you have the service set to start at
server startup, then turn this option off before
installing the fixpack, as the server is restarted
during the fixpack install.
Running the install without DE backup:
If you prefer to backup DE with your own procedures you can
run the install with the following parameter.
-DNO_BACKUP=true
(for Silent Install, uncomment the "NO_BACKUP=true"
parm on the setupFP.rsp response file)
If you choose this method, you must backup DE before you install.
And restore the original system using your backup/restore
procedures or utilities (if uninstalling the Fix Pack).
Follow this procedure to install the Fix Pack:
1. On the Tivoli Business Service Manager server host, change to the
[Fix Pack]/TBSM directory where you extracted the files.
2. Run the installation using one the following commands:
* setup-windows.exe - Windows.
* setup-<unixplatform>.bin - other operating systems.
Installation command options:
GUI mode No options, for example:
Windows: setup-windows.exe
or
UNIX® : ./setup-<unixplatform>.bin
Console mode
Use the -i console option.
For example -
Windows: setup-windows.exe -i console
or
UNIX® : ./setup-<unixplatform>.bin -i console
Silent Mode
a. Copy setupFP.rsp from the TBSM directory of the extracted
Fix Pack file ([Fix Pack]/TBSM) to a location it can be
edited (/tmp).
b. Update the file to match your environment.
c. Confirm acceptance of license, by un-commenting this line
and setting the parm to "true":
#LICENSE_ACCEPTED=false
d. Run:
Windows: setup-windows.exe -f C:\tmp\setupFP.rsp
or
UNIX® :setup-<unixplatform>.bin -f /tmp/setupFP.rsp
Note: The response file needs to have a fully qualified
path.
3. During the install you will be asked to to verify
path names to the TIP install.
4. Restart both the Data and Dashboard processes/services
5. After install is complete (and with the data server started), run
the script ApplyPoliciesFor611FP3, which can be found on the Data
Server under $TBSM_HOME/bin. This script loads the new/updated
policies.
NOTE: Do not run the ApplyPoliciesFor611FP3 on the secondary/
backup data server of a failover pair. This only needs to
be run on the primary data server.
On Windows:
ApplyPoliciesFor611FP3.bat <adminuser> <adminpassword>
For example - ApplyPoliciesFor611FP3.bat tipadmin tipadmin
On Linux/Unix:
./ApplyPoliciesFor611FP3 <adminuser> <adminpassword>
For example - ./ApplyPoliciesFor611FP3 tipadmin tipadmin
NOTE: Verify that the admin user id and password are
correct otherwise, the script will fail at the last step.
If incorrect, rerun the script with a valid adminuser id
and password.
6. From the TBSM 6.1.1 Fix Pack 3 install media, copy these files
onto the DB2 server (where the tbsmdb was initially installed,
when TBSM was first setup).
from: [Fix Pack]/TBSM/TBSMDBChecker
to: [InstallDirectory]/tbsmdb/bin
TBSM_Check_DB.bat
TBSM_Check_DB.sh
tbsmDatabaseChecker.xml
TBSMDBChecker.props
NOTE: The above action is only needed if you ever plan to use
the TBSM_Check_DB script, which will now suppress the
display of the requested user password.
7. After installing this Fix Pack, end-users may need to clear their
browser cache, close and re-open the browser; in order to avoid
any issues on the client side.
8. If the Impact "Service Level Objectives (SLO) Reporting"
function was enabled, please refer to section 3.12 for additional
post Fix Pack installation required actions.
9. Please refer to section 4.0 "Additional information for TBSM Fix Pack 3 APARS"
for additional post install actions.
3.7.2 Discovery Library Toolkit
-------------------------
1. Navigate to the DiscoveryLibrary directory.
2. To install Fixpack 3,
If you are on a Windows operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.1-FP0003-windows_64.exe
If you are on a Unix operating system, run the following
command from a prompt:
setup-dltoolkit-6.1.1-FP0003-<unixplatform>_64.bin
For console mode, specify "-i console".
Note: If the installer cannot find the TBSM 6.1.1 Discovery
Library Toolkit, verify that the toolkit is installed and
that it was installed by the user that the fixpack is being
installed with. If these are both okay, then set the environment
variable TBSM_TOOLKIT_BASE to the location of the toolkit and
restart the toolkit installer. For example:
Windows:
set TBSM_TOOLKIT_BASE=C:\Program Files\IBM\tivoli\tbsm\XMLtoolkit
UNIX:
export TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit
3. The toolkit installer requires access to the database.
4. Notes and Post-Install Considerations:
a) After installation is complete, you may remove
[fixpack] to save space.
5. Restart the toolkit.
3.8 TBSM agent
----------
Installing the TBSM agent (last updated with TBSM Fix Pack 1):
The following packages are available for download in the TBSMAgent
directory on the support download site:
* AIX: KR9_aix526CD-6.1.1-TIV-BSM-FP0001.tar.gz -AIX (64 bit)
* Linux: KR9_lx8266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li x86_64R2.6(64 bit)
* Solaris: KR9_sol286CD-6.1.1-TIV-BSM-FP0001.tar.gz -Solaris R8(64 bit)
* Windows: KR9_wix64CD-6.1.1-TIV-BSM-FP0001.zip -(64 bit)
* zLinux: KR9_ls3266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li S390R2.6(64 bit)
To install the updated TBSM agent (FP1), if not already installed:
1. Download the appropriate agent code for your platform.
2. Untar or unzip the file.
3. Install the agent according to the directions in the TBSM
Installation Guide. This is a complete install package for the TBSM
agent support and can be used for a fresh install of the agent.
For instructions on installing and configuring the TBSM agent, see:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html]
3.9 Uninstalling the Fix Pack
-------------------------
Before uninstalling the FixPack all TBSM processes should be
STOPPED. The user must manually stop the TBSM processes, before
the uninstall of the FixPack (except for OMNIbus and DB2).
Attention: Uninstall the Fix Pack with the same user that was used to
install TBSM 6.1.1 GA.
Silent mode and uninstall
If silent mode was used for the install, the uninstall will
default to a silent uninstall and you must supply a response
file or the uninstall will fail.
For silent mode uninstalls, copy the setup_uninstall.rsp file
from the Fix Pack image to the directory:
<installDir>/tbsm/_uninst/TBSM611_FP3
and update the file with the correct information. Then launch
the installer specifying the file. For example:
uninstall(.exe) -f /tmp/setup_uninstall.rsp
Note: The response file needs to have a fully qualified path.
On the Tivoli Business Service Manager server system:
1. Change to the directory:
<installDir>/tbsm/_uninst/TBSM611_FP3
2. Run the uninstall command:
UNIX: If you are on a Unix operating system, run the following
command from a prompt.
./uninstall
Windows: If you are on a Windows operating system, run the following
command from a prompt.
.\uninstall.exe
For console mode, specify "-i console"
3. After the command has completed, run the following commands to clear
the server cache.
Linux/AIX: <TIP_HOME>/bin/clearClassCache.sh
Solaris: java -Xshare:dump
Windows: <TIP_HOME>\bin\clearClassCache.bat
4. Uninstall eWAS 7.0.0.35
NOTE: On a "Data server only" environment, the TBSM 6.1.1 Fix
Pack 3 un-installer will not remove the upgraded eWAS
7.0.0.35 Fix Pack it installed. If there are plans to, at
a future time, re-install TBSM 6.1.1 Fix Pack 3, it is
necessary to manually un-install eWAS 7.0.0.35.
These steps DO NOT apply to a "Dashboard sever only"
environment or a "Single server" environment, where both the
Data and Dashboard are installed together.
Again, these steps are only needed on a "Data server only"
environment. Failure to perform these actions, will prevent
the re-install of TBSM 6.1.1 Fix Pack 3!
a). Copy the uninstall-WASEmbeded.txt to a temporary location
The uninstall-WASEmbeded.txt file is located on:
<installdir>/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_WASFP/uninstall-WASEmbeded.txt
For example on Unix:
/opt/IBM/tivoli/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_IAGLOBAL_COI_STEP_WASFP/uninstall-WASEmbeded.txt
For example on Windows:
C:\IBM\tivoli\tbsm\_uninst\TBSM611_FP3\plan\install\MachinePlan_localhost\00002_IAGLOBAL_COI_STEP_WASFP\uninstall-WASEmbeded.txt
Or from the TBSM 6.1.1 FP3 install media:
6.1.1-TIV-BSM-FP0003-<ARCH>\TBSM\COI\PackageSteps\WASFP\uninstall-WASEmbeded.txt
b). Edit the uninstall-WASEmbeded.txt (on the temporary location)
c). locate this line: -W product.location="@IAGLOBAL_WAS_HOME@"
d). Replace above line with: -W product.location="<installdir>/tipv2"
Where <installdir> is the fully qualified directory where tipv2 located:
for example (Unix): -W product.location="/opt/IBM/tivoli/tipv2"
for example (Windows): -W product.location="C:\IBM\tivoli\tipv2"
e). Save the uninstall-WASEmbeded.txt file (on the temporary location)
f). Execute the following command:
On Unix:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.sh -options <templocation>/uninstall-WASEmbeded.txt -silent
for example: /opt/IBM/tivoli_root/tipv2/WebSphereUpdateInstallerV7/update.sh -options /tmp/uninstall-WASEmbeded.txt -silent
On Windows:
<installdir>/tipv2/WebSphereUpdateInstallerV7/update.exe -options <templocation>/uninstall-WASEmbeded.txt -silent
for exampe: C:\IBM\tivoli\tipv2\WebSphereUpdateInstallerV7\update.exe -options C:\Temp\uninstall-WASEmbeded.txt -silent
5. Restart the Data Server and Dashboard Server.
Discovery Library Toolkit
===================================================
The Toolkit portion of this fixpack cannot be uninstalled.
A backup copy of the original files can be retrieved from:
[InstallDirectory]/tbsm/
XMLtoolkit/log/install/maintenance/backup/611FP0003
3.10 Recovering from a failed Fix Pack install
-----------------------------------------
If the install fails, try to uninstall in which case, it goes back to
the previous version. If there is no uninstall file under
_uninst/TBSM611_FP3, then nothing really got installed and you can delete
the TBSM611_FP3 file and reinstall.
3.11 Restoring failed DE upgrade from backup
---------------------------------------
To recover a failed Deployment Engine upgrade in TBSM 6.1.1, see the
TBSM Installation Guide at:
http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html]
DOWNLOAD PACKAGE
Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 6.1.1-TIV-BSM-FP0003-linux 06 Jul 2015 English 1422005148 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-linux&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-aix 06 Jul 2015 English 1501631388 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-aix&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-solaris 06 Jul 2015 English 1472222108 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-solaris&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-windows 06 Jul 2015 English 1437426779 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-windows&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-zlinux 06 Jul 2015 English 1418646428 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-zlinux&source=SAR] [ ]
[/support/docview.wss?uid=swg24039742&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039742&aid=2]Problems (APARS) fixed
IV60619 IV61278 IV64797 IV65695 IV65825 IV65947 IV65949 IV65958 IV66535 IV66950 IV71255 IV72005 IV62456 IV62548 IV60168 IV56853 IV63608 IV65503 IV65786 IV59886 , IV61880 IV64950 IV60750 IV60961 IV61199 IV62273 IV62294 IV62246 IV64933 IV65545 , IV66210 IV65484 IV68113 IV60842 IV56450 IV65991 IV21679 IV30875 IV33717 IV36878 , IV38053 IV38471 IV38574 IV39167 IV39517 IV39796 IV42339 IV42657 IV42941 IV43098 , IV43165 IV43469 IV43804 IV43865 IV44246 IV44582 IV45166 IV45386 IV45868 IV46098 , IV46811 IV46876 IV48813 IV49791 IV50625 IV53791 IV54197 IV54587 IV55756 IV56050 , IV56270 IV57273 IV59723 IV61668 , IV27869 IV50058 IV58590 IV59770 IV60438 IV61538 IV61725 IV63535 IV63942 IV64075 IV64837 IV65055 IV65179 IV66164 IV67091 IV67829 IV68383 IV69164 IV70836 IV71157 IV71513 IV73098 IV73243 IV18554 IV23315 IV64152 IV61089 IV63137 IV62792 IV61956 IV61746 IV61399 IV60005 IV60253 IV58616 IV58511 IV53717 IV56745 IV56068 IV55989 IV50329 IV56541 IV47748 IV55464 IV60923 IV11728 IV21717 IV22560 IV33973 IV34503 IV35827 IV35885 IV35940 IV36405 IV36503 IV37040 IV37369 IV37717 IV37759 IV38045 IV38585 IV38961 IV39368 IV40158 IV41888 IV42715 IV43030 IV43751 IV45068 IV45511 IV45569 IV45838 IV46099 IV46493 IV46696 IV46729 IV46799 IV47058 IV47799 IV47904 IV47988 IV48113 IV48113 IV50464 IV50932 IV51062 IV51098 IV51100 IV53483 IV53810 IV53818 IV53822 IV53824 IV53825 IV53826 IV53827 IV53836 IV54939 IV55776 IV55778 IV55779 IV55780 IV55781 | Which version of TBSM support ITM 6.3? What is the TBSM version that is certified with ITM 6.3? | IBM Tivoli Business Service Manager 6.1.1
Fix Pack Version 6.1.1-TIV-BSM-FP0003 |
TRAIN_Q101 | IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States TECHNOTE (FAQ)
QUESTION
What can cause an STAP to fail to connect properly - I get the following messages in the logs:-
/tmp/guard_stap.stderr.txt on the DB Server :-
"Server <ip_addr> wasn't heard from for nn sec during this attempt (nnn sec total), closing and re-opening"
and from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log
"Unauthorized client connecting from <ip_addr> ,rejecting"
CAUSE
One reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance like this :-
[/support/docview.wss?uid=swg22009818&aid=1] [/support/docview.wss?uid=swg22009818&aid=1]
ANSWER
Uncheck the Approval box and the S-TAPs should start connecting .
[/support/docview.wss?uid=swg22009818&aid=2] [/support/docview.wss?uid=swg22009818&aid=2] | Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc
Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc
I get the following messages in the logs:-
/tmp/guard_stap.stderr.txt on the DB Server :- "Server wasn't heard from for nn sec during this attempt nnn sec total), closing and re-opening"
and from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log "Unauthorized client connecting from ,rejecting" | Uncheck the Approval box and the S-TAPs should start connecting . |
TRAIN_Q103 | IBM Important Information about the WebSphere MQ Configuration Agent, Withdrawn from IBM OMEGAMON for Messaging on z/OS V7.5 - United States PRODUCT DOCUMENTATION
ABSTRACT
Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ. It is stabilized in the previous V7.3 release, but MQ Configuration will be supported as long as V7.3 is in support. The components in V7.5 are the IBM MQ Monitoring Agent and the IBM Integration Bus Monitoring Agent, both of which have enhancements in V7.5 that address monitoring requirements you may have. You can upgrade your OMEGAMON for Messaging monitoring components to V7.5 while using the previous release of MQ Configuration.
Whether or not you want to continue using MQ Configuration when you install and configure OMEGAMON for Messaging V7.5, there may be steps you need to take, so please review this document prior to installing and configuring V7.5.
CONTENT
First, please determine whether you have previously installed and configured the MQ Configuration component. If you have not done so previously, there is no need for you to consider the rest of this document. For this determination, please examine the following:
· SMP/E: Are the FMIDs for MQ Configuration installed? The FMIDs are HKMC730 and HKCF730, or HKMC710 and HKCF710 if you are using the V7.1 level.
· PARMGEN: In your PARMGEN configuration for each runtime environment, does the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), have the line for “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” selected for configuration in the environment?
If the answers are “yes” to both of the above questions, then you do need to continue with the following general steps, which are documented in detail below:
1) Determine whether there are any users of MQ Configuration in your environment. There are many cases in which the MQ Configuration component is installed and configured in PARMGEN, but no one is actually using it. It is important to determine this in order to decide which step to take next.
2) If you do not have users of MQ Configuration, or you want to remove it anyway, there may be steps required when you are installing and configuring OMEGAMON for Messaging V7.5 especially if you previously configured a shared agent address space for MQ monitoring (KMQ) and MQ configuration (KMC) agents.
3) If you do have users of MQ Configuration and want to continue supporting that usage, you need to follow recommendations when you are installing and configuring OMEGAMON for Messaging V7.5 upgraded products.
Here are the details:
1) Suggested ways to determine whether there are any users of MQ Configuration:
a. In the Tivoli Enterprise Portal (TEP), using an administrator user ID, click Edit->Administer Users to check whether any users or groups have access to the Configuration navigator view. For users and/or groups that have been configured for TEP, check the Navigator Views tab to see if any of them have “Configuration” in their Assigned Views. If no one is allowed access to the Configuration navigator, then they are not using MQ Configuration feature.
b. Another item to check in Administer Users is whether any user or group has the Permissions tab showing that View or Modify permission has been authorized for WebSphere MQ Configuration Authorities “Configure” authority. Some user or group should have permission to use this feature if it is used by anyone.
c. Check whether there are configured names that reflect queue managers in your environment. Click on the Configuration navigator in the view drop-down list in the Navigator pane, then click on Defined View on the left. In the middle Defined Tree pane on the workspace, expand the various “+” items, and with the help of someone who knows MQ queue managers in your environment, see if any of the expanded items reflect queue managers actually in your environment. There will be default and example items shipped with the product, but you are looking for names reflecting MQ at your site. If there are no names that reflect queue managers in your environment, then no one is using MQ Configuration.
d. If it appears that there is usage of MQ Configuration, it would still be good to check with MQ users at your site to see if they actually require it. Perhaps they have experimented with it but do not actually use it regularly. If the OMEGAMON feature for MQ Configuration is not absolutely required in your environment, the recommendation would be to review all the ways that the IBM MQ product offers to configure and administer MQ, some of which are new in recent releases. Also, remember that the OMEGAMON MQ Monitoring agent offers the Take Action facility to issue any MQSC configuration command if the user is authorized.
2) If there are no users of MQ Configuration, or you want to remove it anyway:
a. If you use a Serverpac that contains the upgraded OMEGAMON for Messaging V7.5 components to install, the MQ Configuration FMIDs (HKMC730 and HKCF730) are not installed because they are not included in the Serverpac. However, depending on your previous configuration, the missing MQ Configuration component could cause unexpected results in your LPAR runtime environment (RTE), so check and act on the following items prior to installation and configuration of OMEGAMON for Messaging V7.5:
1. If your Hub TEMS is configured on the z/OS platform and there are RKCF* DDNAME statements in your existing Hub TEMS started task JCL, update the TEMS started task JCL to remove those RKCF* DDNAME statements.
2. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. For the MQ Monitoring agent to be the owner, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting, as depicted in the following example before and after settings:
Before (MQ Configuration owns the Agent address space called OMEGMQ):
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMC_AGT_STC OMEGMQ
KMC_AGT_STC_OWNER “”
KMQ_AGT_STC “”
KMQ_AGT_STC_OWNER OMEGMQ
After (MQ Monitoring owns the Agent address space called OMEGMQ):
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMQ_AGT_STC OMEGMQ
KMQ_AGT_STC_OWNER “”
Tip: Please review the SMPE06 upgrade scenario [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2] in the OMEGAMON Shared Knowledge Center as part of deploying these changes. You can use the refreshed OMEGMQ OMEGAMON for Messaging – KMQ Agent-only address space in the RTE’s W/RKANSAMU dataset for refreshing the original shared address space in your system procedure library. The only delta would be the RKMCAPLA DDNAME, which can be staged for removal.
b. If you install OMEGAMON for Messaging V7.5 as a CBPDO into an existing SMP/E CSI, the MQ Configuration FMIDs will remain installed, but since you are not using MQ Configuration, it is recommended you follow these steps:
1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. See item a.2 above for more details.
2. In the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), deselect the line with “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” so that it will be removed from the runtime environment (RTE) during reconfiguration/upgrade of the RTE. Follow one of the SMPEnn upgrade scenarios [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2] documented in the OMEGAMON Shared Knowledge Center.
Tip: Prior to upgrading the RTE, you also have the option to SMP/E delete the HKMC730 and HKCF730 FMIDs from the existing CSI. When you start the PARMGEN configuration phase of the upgrade, the inexistence of these deleted FMIDs is PARMGEN’s trigger to delete the product from the RTE upon reconfiguration following any of the SMPEnn upgrade scenarios (SMPE04 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2], SMPE05 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe05_parmgenref.htm?pos=2] or SMPE06 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2]).
3) If there are users of MQ Configuration, and you want to continue supporting that usage:
a. It is highly recommended that you install OMEGAMON for Messaging V7.5 as a CBPDO into the existing SMP/E CSI so that MQ Configuration remains available. If you do this, there are no other steps required, however, the following step is also highly recommended:
1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, separate them into their own address spaces, since they will be running at different product levels. For this, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting to be like the following example in which MQ Configuration is running in an address space called OMEGMC and MQ Monitoring is running in an address space called OMEGMQ:
ISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%)
Command ===>
KMC_AGT_STC OMEGMC
KMC_AGT_STC_OWNER “”
KMQ_AGT_STC OMEGMQ
KMQ_AGT_STC_OWNER “”
b. If you were to install OMEGAMON for Messaging V7.5 in a Serverpac, you would need to retain your old SMP/E CSI and maintain a separate PARMGEN runtime environment in order to use MQ Configuration separately. This may be acceptable to you if you already separate MQ Configuration from the rest of your monitoring infrastructure, with its own Hub TEMS, etc. In this case, for the configuration that will contain OMEGAMON for Messaging V7.5, please see item 2 above, steps a.1 and a.2 in case they would apply to that particular configuration.
c. OMEGAMON for Messaging V7.5 application support does not include application support for the MQ Configuration component. If you need to re-install application support for MQ Configuration for any reason, you should use the latest V7.3 level of application support. For z/OS customers, that is available with DVD LCD7-3513-08 at the following link: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]
For more information about OMEGAMON for Messaging V7.5, please see this link to the product documentation:
https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html [https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html]
For more information about OMEGAMON installation and configuration with PARMGEN, please see this link to the shared documentation:
https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2]
For more information about recommended ways to configure IBM MQ, please see the following links:
Administering IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.doc/q019950_.htm]
Configuring queue managers on z/OS [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019070_.htm]
Using IBM z/OSMF to automate IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019925_.htm]
Support continuous configuration deployments for IBM MQ with UrbanCode [https://www.ibm.com/developerworks/library/d-continuous-configuration-deployments-urbancode-mq-trs/index.html]
ORIGINAL PUBLICATION DATE
2017/10/26 | PARMGEN ABEND S013 in JOB KCIJPALO
After installing IBM OMEGAMON for Messaging on z/OS 07.05.00, I receive the following ABEND after submitting PARMGEN Job KCIJPALO:
JOB02175 IEC141I 013-18,IGG0191B,U600861X,KMCJPALR,RKPDIN,600D,ISMS01, 083
083 HSYS.S002.OMGNEW.TKANPAR(KMCPDICT)
JOB02175 IEA995I SYMPTOM DUMP OUTPUT 085
085 SYSTEM COMPLETION CODE=013 REASON CODE=00000018
085 TIME=07.41.33 SEQ=00630 CPU=0000 ASID=004C
085 PSW AT TIME OF ERROR 075C1000 80E9E456 ILC 2 INTC 0D
085 NO ACTIVE MODULE FOUND
085 NAME=UNKNOWN
085 DATA AT PSW 00E9E450 - 4100302C 0A0D010D A7E5014B
085 AR/GR 0: 009FF028/00E9E760 1: 00000000/A4013000
085 2: 00000000/00081CB8 3: 00000000/00E9E734
085 4: 00000000/009B1410 5: 00000000/009B17A4
085 6: 00000000/009B174C 7: 00000000/009B17A4
085 8: 00000000/009B176C 9: 00000000/00000080
085 A: 00000000/00F20E10 B: 00000000/009B10FC
085 C: 00000000/00000008 D: 00000000/00000000
085 E: 00000000/80E9DCB4 F: 00000000/00000018
085 END OF SYMPTOM DUMP
What is the cause of this? | Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ. |
TRAIN_Q104 | IBM SCA destinations for IBM Business Process Manager (BPM), WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB) are not preserved when uninstalling and reinstalling a service module - United States SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When a Service Component Architecture (SCA) module is uninstalled, by default, its associated destinations are removed, even if there are still messages in the destination queue. In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved.
RESOLVING THE PROBLEM
To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5
PRODUCT ALIAS/SYNONYM
BPM
WPS
WESB | Updating SCA applications & internal SCA module queues
When updating an existing SCA module using the ISC, I noticed that internal SCA queues (sca/<module>/...) on the SCA.SYSTEM bus) are deleted and recreated.
Does this mean that any messages that may still reside on these internal queues would be deleted on a module update? If so, when updating SCA modules in a production environment, should these internal queues be monitored to be empty before updating a SCA module (to prevent loosing messages)? | To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations. |
TRAIN_Q106 | IBM Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) - United States SECURITY BULLETIN
SUMMARY
The Telemetry (MQXR) service can be configured to use SSL/TLS connections - the passphrase used to access the keystore is written to the file system in clear text in a properties file that is world readable.
VULNERABILITY DETAILS
CVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]
DESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.
CVSS Base Score: 2.1
CVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM WebSphere MQ 8.0
* 8.0.0.3 and earlier maintenance levels
IBM WebSphere MQ 7.5 * 7.5.0.5 and earlier maintenance levels
IBM WebSphere MQ 7.1 * 7.1.0.6 and earlier maintenance levels
REMEDIATION/FIXES
IBM WebSphere MQ 8.0
Install fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244]
IBM WebSphere MQ 7.5 * Apply Interim fix IT09866 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5.0.5&platform=All&function=aparId&apars=IT09866]
IBM WebSphere MQ 7.1 * Install fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]
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
01 February 2016: Original Copy Published
*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.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977183] | Help with Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) I need to understand details regarding Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012). Where can I find this information? | CVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]
DESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.
CVSS Base Score: 2.1
CVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N) |
TRAIN_Q107 | IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process.
Since Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined.
CAUSE
Application needs HTTP session time-out set.
RESOLVING THE PROBLEM
The HTTP Session time-out can be set in the following places:
* From the Administrative Console at the server, Enterprise application, and Web application levels
* At the time when the application is packaged
* In the application code
Setting the HTTP Session time-out from the Administrative Console
1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management.
In the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box.
2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management.
Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level.
3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management.
Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level.
After modifying these settings, save the master configuration.
Setting HTTP Session time-out when application is packaged
The application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application.
This setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows:
<session-config>
* <session-timeout>60</session-timeout>
*
* </session-config>
Where the "session-timeout" is an integer value for the desired session time-out in minutes.
Setting HTTP Session time-out from the application code
Finally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console.
HTTP Session time-out Override Precedence Summary
The list below shows the precedence from which the final HTTP Session time-out is derived.
1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&aid=1] Overrides all other settings RELATED INFORMATION
A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK | How to increase the HTTP Session time-out value for Workplace application on WebSphere Application Server? We would like to increase the HTTP Session time-out value for our Workplace application. Where are all the locations that this value is set and what are their precedence? | The HTTP Session time-out can be set in the following places:
* From the Administrative Console at the server, Enterprise application, and Web application levels
* At the time when the application is packaged
* In the application code |
TRAIN_Q108 | IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN
SUMMARY
The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT).
VULNERABILITY DETAILS
CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]
DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as "Logjam".
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
AFFECTED PRODUCTS AND VERSIONS
The affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2
REMEDIATION/FIXES
SupportPac MS81: IBM WebSphere MQ Internet Pass-Thru
Users of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].
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 v2 Guide [http://www.first.org/cvss/v2/guide]
On-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator]
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] ACKNOWLEDGEMENT
Reported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org]
CHANGE HISTORY
11th June 2015: Original version published
*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.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347] | Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) I need to understand details regarding Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000). Where can I find this information? | CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]
DESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as "Logjam".
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) |
TRAIN_Q109 | 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-14746 CVE-2017-15085 CVE-2017-15086 CVE-2017-15087 CVE-2017-15275
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 | Help with Action required for 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.
This is related to CVE-ID:
CVE-2017-14746
CVE-2017-15085
CVE-2017-15086
CVE-2017-15087
CVE-2017-15275
Where can I find this information? | IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable. |
TRAIN_Q110 | IBM Installing the Installation Manager on an NFS mounted disk - United States NFS; remote drive; mount drive ; 1308281 TECHNOTE (FAQ)
QUESTION
Can IBM® Installation Manager be installed on a UNIX® or Linux® NFS mounted disk?
ANSWER
Do not install the IBM Installation Manager on an NFS mounted disk.
On AIX® for example, some of the JRE folders are not being deleted when the IBM Installation Manager uninstalls but is deleted after waiting for 10 minutes. This causes the JRE folder to not be uninstalled during an uninstall operation. Other UNIX and Linux operating systems have similar issues.
Only install the Installation Manager on a local disk. | Why does my install of the latest Installation Manager on a Linux Ingram Server not function?
I've installed the latest Installation Manager on an Ingram Server that I mount to different Linux machines where I have installed WebSphere Application Server. I received the following error when trying to use the Installation Manager:
00:02.25 ERROR [main] org.eclipse.equinox.log.internal.
ExtendedLogReaderServiceFactory safeLogged
Application error
java.lang.NoClassDefFoundError: org.eclipse.jface.dialogs.
ProgressMonitorDialog
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:324)
at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.
defineClass(DefaultClassLoader.java:188)
at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.
defineClassHoldingLock(ClasspathManager.java:632)
I have unmounted and remounted the drive but does not appear to resolve the issue. | Only install the Installation Manager on a local disk. |
TRAIN_Q111 | IBM How to find details of Corrupted Object from the entries in db2diag.log? - United States TECHNOTE (FAQ)
QUESTION
How to find details of Corrupted Object from the entries in db2diag.log?
ANSWER
When we have corruption in the database we may received following kind of entries in db2diag.log
These also notify object where we t where we have detected corruption in the Database.
Sample db2diag.log entry for Corruption.
2016-05-04-03.13.05.261082-360 I3442A358 LEVEL: Error
PID : 393470 TID : 1 PROC : db2pfchr 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,probe:13
RETCODE : ZRC=0x86020001=-2046689279=SQLB_BADP "page is bad"
DIA8400C A bad page was encountered.
2016-05-04-03.13.05.264301-360 I3801A437 LEVEL: Error
PID : 393470 TID : 1 PROC : db2pfchr 0
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,
probe:13
DATA #1 : String, 158 bytes
Obj={pool:3;obj:21;type:0} State=x27 Parent={3;21}, EM=1120, PP0=1152
Page=51235 Cont=17 Offset=2848 BlkSize=15
sqlbReadAndReleaseBuffers error: num-pages=16
Based on this information dumped in db2diag.log entry we can Identify {pool:3;obj:21;type:0} is the Object is corrupted.
e.g. Obj={pool:3;obj:21;type:0}
Pool = Tablespace ID
Obj = Object ID
Type = Type of the Object
If Type is 0 its Table Object ,If its 1 then its Index.
We can find the Name of the Object using following query, to further backup the Definition for future reference.
db2 "select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=<ObjectID> and tbspaceid=<Tablepace id>"
Obj={pool:3;obj:21;type:0}
db2 "select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=21 and tbspaceid=3"
RELATED INFORMATION
SYSCAT.TABLES catalog view [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001063.html?lang=en] | How to find details of Corrupted Object from the entries in db2diag.log? We have corruption in DB2 Database and got entries for corrupted Object in db2diag.log ,Need to find details of the Object using information dumped in db2diag.log | When we have corruption in the database we may received following kind of entries in db2diag.log
These also notify object where we t where we have detected corruption in the Database. |
TRAIN_Q112 | IBM JMSExceptions CWSIT0006E and CWSIA0241E on bus connect - United States TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Your application throws JMS exceptions CWSIT0006E and CWSIA0241E when trying to connect to a WebSphere Application Server (WAS) Service Integration Bus (SIBus).
SYMPTOM
Application throws the following JMS exceptions in the stack trace while trying to connect to the SIBus:
JMSException caught
javax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method
JmsManagedConnectionFactoryImpl.createConnection:
com.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact
a messaging engine in bus YOURBUS..
at
com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:225)
at
com.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:148)
CAUSE
This can be caused by a stopped messaging engine, a wrong or misspelled bus name (case-sensitive) in the connection factory settings or, the HA manager is not able to find the running messaging engine.
RESOLVING THE PROBLEM
The error messages CWSIA0241E and CWSIT0006E indicate that when the connection was attempted, there were no running messaging engines available on the specified bus. To see why the messaging engines were not available, check the SystemOut.log for applicable messages. Examine the SystemOut.log file starting at the time period when the application experienced the problem and search backward.
Check for the CWSID0016I which indicates status of the Messaging Engine activity. You may see messages like this:
SibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopping.
SibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopped.
The solution for this problem is to start the messaging engine.
If the messaging engine is running and you still see these errors at the application side, other possible reasons for this problem are:
1) Check provider end points. The value for the provider endpoints should be in the format of host_name:port_number:BootstrapBasicMessaging.
In the JMS connection factory, you can define a list of provider endpoints that govern which servers the application will attempt to connect to. If you have defined these endpoints, ensure that the messaging engines for these servers have all started and that the port and transport chains defined in the endpoint list are correct. Also, ensure that the values for the Connection proximity (bus, cluster, host or server) and the Target groups and Target significance settings are appropriate. For example, if the Target significance value is Required and no suitable messaging engine could be located, then this would cause a connection failure. Please refer to the following links for how to set provider endpoints:
Default messaging provider queue connection factory [Settings] : [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSQueueConnectionFactory_DetailForm.html]
Default messaging provider topic connection factory [Settings]: [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSTopicConnectionFactory_DetailForm.html]
Restart the server after making the change.
2) If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.
Tune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties.
1)<WAS_HOME>/properties : The properties declared under this location would be applicable to all the profiles in that installation.
2)<PROFILE_ROOT>/properties : The properties declared here are applicable for all the servers on this profile
If a property is defined at both <PROFILE_ROOT>/properties and <WAS_HOME>/properties, then the property defined at <PROFILE_ROOT>/properties would take precedence.
After resetting the property you must restart the server.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Not Applicable Business Integration WebSphere Process Server Business Integration WebSphere Service Registry and Repository Business Integration IBM Business Process Manager Standard Business Integration WebSphere Enterprise Service Bus Business Integration WebSphere Partner Gateway Advanced Edition Configuration Business Integration WebSphere MQ Configuration
PRODUCT ALIAS/SYNONYM
WebSphere Application Server WAS SIB SIBUS SI BUS | WAS 8.5.x - Writing a JMS message to a remote queue takes a long time. How to write the message faster?
We are writing a jms message from a websphere cell (cellA) to a queue hosted by another websphere cell (cellB). Sometimes we noticed that writing a message is very slow. Usually when a local queue will be used the time to write this messages is about 8 ms, but if the queue is located on a other cell is took significant longer (about 3000ms+ ).
Our findings: After enabling following trace "=info: com.ibm.ws.sib.trm.=finest" the problem is related to:
- com.ibm.ws.cluster.selection.NoAvailableTargetExceptionImpl
- WaitForWLMDat 3 (com.ibm.ws.sib.trm.wlm.client.WaitForWLMData) [:] Sleeping for 2999 ms "
Because of the sleep time the writing to the queue is slowed down. How to prevent the sleeping time of 3 seconds, when writing a message to a remote queue? | If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.
Tune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties.
1)<WAS_HOME>/properties : The properties declared under this location would be applicable to all the profiles in that installation.
2)<PROFILE_ROOT>/properties : The properties declared here are applicable for all the servers on this profile
If a property is defined at both <PROFILE_ROOT>/properties and <WAS_HOME>/properties, then the property defined at <PROFILE_ROOT>/properties would take precedence.
After resetting the property you must restart the server. |
TRAIN_Q113 | IBM Configuring logging for Atlas Extensions in Atlas 6.0.3.3 - United States TECHNOTE (FAQ)
QUESTION
How do I configure logging for Atlas Extensions in Atlas 6.0.3.3?
CAUSE
Atlas Extensions log files are not being generated
ANSWER
In Atlas 6.0.3.3, the Atlas Extensions logging configuration has moved to log4j.properties file.
1. Navigate to <Atlas_Install_folder>/Atlas/Properties folder
2. Edit log4.properties file
3. Update the path Information for the following three properties 1. log4j.appender.MATTER_APPENDER.File=matter_adapter.log
2. log4j.appender.PERSON_APPENDER.File=person_adapter.log
3. log4j.appender.ORG_UNIT_APPENDER.File=org_unit_adapter.log
4. Save the file
5. Restart Atlas application server | How do I configure logging for Atlas Extensions in Atlas 6.0.3.3? How do I configure logging for Atlas Extensions in Atlas 6.0.3.3? | In Atlas 6.0.3.3, the Atlas Extensions logging configuration has moved to log4j.properties file.
1. Navigate to <Atlas_Install_folder>/Atlas/Properties folder
2. Edit log4.properties file
3. Update the path Information for the following three properties 1. log4j.appender.MATTER_APPENDER.File=matter_adapter.log
2. log4j.appender.PERSON_APPENDER.File=person_adapter.log
3. log4j.appender.ORG_UNIT_APPENDER.File=org_unit_adapter.log
4. Save the file
5. Restart Atlas application server |
TRAIN_Q114 | IBM Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms ( CVE-2016-0394 ) - United States WMB IIB SECURITY BULLETIN
SUMMARY
IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor.
VULNERABILITY DETAILS
CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]
DESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)
AFFECTED PRODUCTS AND VERSIONS
IBM Integration Bus V9
WebSphere Message Broker V8
REMEDIATION/FIXES
Product VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]
WebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8
https://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925]
For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product.
The planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at :
http://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]
WORKAROUNDS AND MITIGATIONS
To mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands:
find <IIB install dir>/isadc -type d -exec chmod 755 {} \;
find <IIB install dir>/isadc -type f -exec chmod 644 {} \;
find <IIB install dir>/isadc -type f -name *.sh -print -exec chmod 755
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.
IMPORTANT NOTE
IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http://www.ibm.com/systems/z/solutions/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk.
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
28-Nov-2016 - Original version Published
04-Apr-2017 - Removed v10 (distributed) from affected list, text change to explicitly mention 'on unix platforms'
*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.
RELATED INFORMATION
A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21995532]
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0
PRODUCT ALIAS/SYNONYM
WMB IIB | Help with Security Bulletin: IIB & WMB upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) I need to understand details regarding Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) Where can I find this information? | CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]
DESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files.
CVSS Base Score: 4
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N) |
TRAIN_Q116 | IBM Portal upgrades fail during ejbdeploy with 'Error is Platform not running' message - United States 7001eGA TECHNOTE (TROUBLESHOOTING)
PROBLEM
Portal upgrades fails during ejbdeploy with 'Error is Platform not running' message. This could happen for any v6.1.0.x , v7.0.0.x, or v8.0.0.x upgrade
SYMPTOM
In the ConfigTrace.log, the following exception can be seen:
==========================
[wsadmin] ADMA5016I: Installation of wps started.
[wsadmin] ADMA5058I: Application and module versions are validated with versions of deployment targets.
[wsadmin] ADMA5018I: The EJBDeploy program is running on file /var/tmp/app5791171104868981175.ear.
[wsadmin] Starting workbench.
[wsadmin] EJB Deploy configuration directory: /opt/IBM/WebSphere/AppServer/profiles/dmgrProfile/ejbdeploy/configuration/
[wsadmin] framework search path: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins
[wsadmin] build: RAD753-I20090617_1116
[wsadmin] An unexpected exception was thrown. Halting execution.
[wsadmin] Shutting down workbench.
[wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running.
[wsadmin] java.lang.IllegalStateException: Platform not running
[wsadmin] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374)
[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[wsadmin] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[wsadmin] at java.lang.reflect.Method.invoke(Method.java:597)
[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:487)
[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:106)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:106)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:349)
[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:311)
[wsadmin] EJBDeploy level: @build@
[wsadmin] ADMA5008E: The EJBDeploy program failed on file /var/tmp/app5791171104868981175.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
[wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy
[wsadmin] ADMA5011I: The cleanup of the temp directory for application wps is complete.
[wsadmin] ADMA5069E: The installation of application wps failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.
[wsadmin] WASX7017E: Exception received while running file "/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/work/was/curJaclScript.jacl"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for wps failed: see previous messages for details.
[wsadmin] WASX7341W: No "save" was performed before the interactive scripting session exited; configuration changes will not be saved.
/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/includes/apply_PTF.xml:59: Java returned: 105
==========================
CAUSE
This exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed.
RESOLVING THE PROBLEM
To resolve the problem, complete the following steps:
1. Delete/Remove the contents of the following directory EXCEPT for the 'config.ini' file, if it exists (the paths are different depending on your backend WAS version):
WebSphere Application Server v6.1.x:
<profile root>/deploytools/configuration
WebSphere Application Server v7.0.x:
<profile root>/ejbdeploy/configuration
<AppServer root>/deploytool/itp/configuration
WebSphere Application Server v8.0.x:
<profile root>/ejbdeploy/configuration
<AppServer root>/deploytool/itp/configuration
Cluster Environments: Do this for both the DMGR profile and the node profile.
Note: The deploytools and ejbdeploy directories may not exist on all nodes. They are created when ejbdeploy is executed successfully for the first time. If it has never been executed successfully in your environment, then the directories will not be there.
2. Re-attempt the WebSphere Portal upgrade.
*
* | Why does my upgrade to Portal 8001 CF14 fail with the following errors, ADMA5008E, ADMA0063E, ADMA5069E, WASX7017E? Why does my upgrade to Portal 8001 CF14 fail with the following errors, ADMA5008E, ADMA0063E, ADMA5069E, WASX7017E? | This exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed. |
TRAIN_Q117 | IBM The affect of the auto-update feature for Oracle JDK 7 on IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation - United States NEWS
ABSTRACT
The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8.
CONTENT
On Windows operating systems, because the upgrade to Oracle JDK 8 is enabled by default, you might not be aware that the upgrade has occurred. This Oracle JDK 8 issue applies to the Mac OS as well.
SYMPTOM
You might see one of the following messages in the log file on Windows and Mac OS machines that originate from the WebSphere Application Server Liberty Profile:
* TRAS0033E: Runtime injection of detailed method trace failed for class <class name> with exception <exception name>
* CWWKC0044W: An exception occurred while scanning class and annotation data.
RESOLUTION
As stated on the Java SE at a Glance [http://www.oracle.com/technetwork/java/javase/overview/index.html] page, Oracle is automatically migrating users with the auto-update feature enabled from Oracle JDK 7 to Oracle JDK 8. However, a number of IBM and third-party dependencies for IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation do not support Oracle JDK 8.
* Windows operating systems
If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8.
2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site.
3. Reinstall Oracle JDK 7.
To disable the JDK auto-update feature on Windows operating systems, see the Change Automatic Update Settings [http://java.com/en/download/help/java_update.xml#adv] section of the Oracle Java Auto Update documentation.
* Mac OS
If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8. For more information, see the How do I uninstall Java 7 and later versions on my Mac? [https://www.java.com/en/download/help/mac_uninstall_java.xml] information on the Oracle web site.
2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site. For more information, see JDK 7 Installation for Mac OS X [http://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-jdk.html].
3. Reinstall Oracle JDK 7.
On the Mac OS operating system, you are explicitly asked if you want to update your Java version. Do not update the Java version to Java 8. To verify your Java version, see How do I update Java for my Mac? [https://www.java.com/en/download/help/mac_java_update.xml]
Cross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Worklight Security Mac OS X, Windows 6.2, 6.1, 6.0, 5.0.6, 5.0.5 Consumer, Enterprise Mobile- Speech and Enterprise Access IBM Mobile Foundation Security Mac OS X, Windows 6.0, 5.0.6, 5.0.5 Consumer, Enterprise | Should I upgrade to Oracle JDK 8 if I am using IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, or IBM MobileFirst Platform Foundation products? These is an upgrade available to replace Oracle JDK 7 with Oracle JDK 8. Does IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and the IBM MobileFirst Platform Foundation products support the use of Oracle JDK 8? | The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8. |
TRAIN_Q118 | IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Readme - stand-alone - United States WPWCMCF WPWCMCF02 7002CCF PRODUCT README
ABSTRACT
IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix stand-alone installation instructions for all editions, including WebSphere Portal Express.
CONTENT
7.0.0.2: Readme for IBM WebSphere Portal 7.0.0.2 Combined Cumulative fix - stand-alone
Table of Contents
* About Combined Cumulative Fix #history
* Space requirements
* Cluster installation instructions [http://www.ibm.com/support/docview.wss?uid=swg27023911]
* Steps for installing Combined Cumulative Fix
* Steps for uninstalling Combined Cumulative Fix
* #inst_clus#uninst_clusKnown issues
* Change History
* Additional information
* Trademarks and service marks
About Combined Cumulative Fix
These are the instructions on how to install a WebSphere Portal Combined Cumulative Fix. The Combined Cumulative Fix is a package of WebSphere Portal fixes and Web Content Manager Cumulative fixes.
What's New
As of WebSphere Portal V7.0.0.2 Combined Cumulative Fix 26 (CF26), support has been added for syndicating to subscribers running WebSphere Portal V8.0.0.1 Combined Cumulative Fix 09 (CF09) or later.
Back to top
Space requirements
Ensure that enough disk space is available in the following directories:
z/OS: 625 cylinders in the directory where you download the cumulative fix, 625 cylinders in the <Portal Configuration HFS>, 625 cylinders in <WebSphere Configuration HFS> and 1250 cylinders in your system temp directory.
All other platforms: 2 GB in the directory where you download the cumulative fix, 1 GB in <Portal_Install_Root>, 1 GB in <wp_profile_root> temporary disk space and 1 GB in your system temp directory, such as /tmp on Unix or Linux platforms or C:\temp on the Microsoft Windows platform.
Back to top
Steps for installing Combined Cumulative Fix
BEFORE YOU BEGIN:
Familiarize yourself with the Portal Upgrade Best Practices available from IBM Remote Technical Support for WebSphere Portal.
Portal Upgrades: Best Practices for V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21452611] For instructions on how to validate your environment prior to the upgrade, see the instructions for running the Health Checker tool for WebSphere Portal at:
Health Checker tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] IMPORTANT: Certain security configurations can cause failures with the upgrade. Please check the following technote to see if this may apply to your environment.
Fix Pack 7.0.0.1 fails at action-import-defaultnodes-wp.filestore/base task. [http://www.ibm.com/support/docview.wss?uid=swg21496067]
1. Perform the following steps before installing Combined Cumulative fix:
1. Before you install this combined cumulative fix, check to see if the list of fixes already installed on your system is included in the list of fixes provided in this combined cumulative fix. If you have temporary, interim or cumulative fixes on your system that are not included in this Combined Cumulative Fix, then uninstall those fixes before installing this Combined Cumulative Fix and contact IBM Support for an updated version of that fix, or for more information.
2. If you are running an external Web server such as IBM HTTP server, stop the Web server.
3. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct. WebSphere Portal 7 introduced support for multiple profiles. If using multiple profiles, also verify that the information in each profile is correct. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7]. * Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
* Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file.
* Unix/Linux/Windows/IBM i Only: The WebSphere Portal Update Installer removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file: PWordDelete=false.
* Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server.
4. Special considerations for multiple profiles or binary install or migration upgrade: 1. If you did a binary installation and created a WebSphere Portal profile later, or your Portal 7.0.0.x was migrated from 6.1.x, ensure that the PortalServer/wps.properties file correctly references the profile. The Portal Update Installer uses the wps.properties file to determine which profile is the primary profile to update. Failure to complete this step could result in an inoperable Portal server after the Combined Cumulative Fix installation completes. 1. Edit the <PortalServer root>/wps.properties file in a text editor
2. Add these two properties if they do not already exist:
ProfileName=<your profile name, e.g. wp_profile>
ProfileDirectory=<your profile directory, e.g. /opt/IBM/WebSphere/wp_profile>
Note: The ProfileDirectory property should use forward slash (/) instead of backslash (\) on Windows.
2. If you have created multiple profiles. the Portal Update Installer will automatically upgrade all profiles. If you want to specify which profiles are updated, then complete the following steps: 1. Edit the <PortalServer root>/wps.properties file in a text editor
2. Add this property if it does not already exist:
AutoUpdateMultipleProfiles=<comma separated list of profile names, e.g. wp_profile, wp_profile2, wp_profile3>
3. If using Multiple Profiles, verify all your profiles are at the same level before starting upgrade.
5. Perform the following steps to download the Combined Cumulative Fix and the WebSphere Portal Update Installer: 1. Download the latest Combined Cumulative fix (e.g. 7.0.0.2-WP-WCM-Combined-CFPMnnnnn-CFnnn), and the latest WebSphere Portal Update Installer from http://www.ibm.com/support/docview.wss?uid=swg24027857 [http://www.ibm.com/support/docview.wss?uid=swg24027857].
2. Create the PortalServer_root/update directory and extract the WebSphere Portal Update Installer file into this directory.
3. Create the PortalServer_root/update/fixes directory and extract the 7.0.0.2-WP-WCM-Combined-CFPMnnnnn-CFnnn.zip file into this directory, where n is the numbers associated with the version of the Combined Cumulative fix. Note for z/OS users: refer to Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670] for detailed descriptions of how to execute steps ii. and iii. above.
2. Choose either the graphical user interface installation option or the command line installation option:
NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).
NOTE: If the installation fails, use the IBM Support Assistant [http://www.ibm.com/software/support/isa/] to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.
If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.
Enter the following command to launch the graphical user interface installation program: * Windows: PortalServer_root\update> updatePortalWizard.bat Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh
- OR -
Perform the following steps to launch the installation program from the command line: 1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
2. Enter the following command to launch the installation program (NOTE: Enter the command on one line):
* Windows: PortalServer_root\update> updatePortal.bat -install
-installDir "<PortalServer_root>"
-fix
-fixDir "<PortalServer_root>\update\fixes"
-fixes < Cumulative fix >
* Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install
-installDir "<PortalServer_root>"
-fix
-fixDir "<PortalServer_root>/update/fixes"
-fixes < Cumulative fix >
* IBM i: portal_server_root/update> updatePortal.sh -install
-installDir "<portal_server_root>"
-fix
-fixDir "<portal_server_root>/update/fixes"
-fixes < Cumulative fix >
* z/OS: If the Health Checker Tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] has not been run then it needs to be run before installing the Combined Cumulative Fix. Execute the following commands to install the Combined Cumulative Fix: 1. From <was_profile_root>/bin directory:
. ./setupCmdLine.sh
2. PortalServer_root/update> ./updatePortal.sh -install
-installDir "<PortalServer_root>"
-fix
-fixDir "<PortalServer_root>/update/fixes"
-fixes <Cumulative fix>
Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670]. Submit the JCLs, and then return here to continue.
If you do not have any profiles at this point (because you are in the process of migration from WebSphere Portal 6.1 or Installing an additional node for a cluster or creating multiple profiles) no post installation steps are necessary and you can continue with the next steps that create the profiles as outlined by the according documentation.
z/OS: If doing an upgrade as part of a migration from a previous version (eg. 6.x), run ./ConfigEngine.sh gather-migration-files command from the <wp_profile_root>/ConfigEngine directory.
z/OS: Run the following command: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh install CF skipPreCheckProfile
All other platforms: To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].
<wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh install CF
This cumulative fix provides updates to OSGi bundles. After installing the cumulative fix, run "<profile location>/bin/osgiCfgInit.sh" (for IBM i the command is just osgiCfgInit, for Microsoft Windows the command is osgiCfgInit.bat) to clear the caches and make the OSGi container pick up the updates to the modified OSGi bundles. Note that it is recommended to stop the portal server before running the osgiCfgInit command.
*
*
3. Perform the following post installation steps:
* If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:
1. Regenerate the Web server plugin.
2. Copy the plugin-cfg.xml file to the Plugin directory.
3. Restart the Web server.
Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to installing the Combined Cumulative fix. 1. To update the deployed remote rendering portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
* Log in to Portal as the Portal Administrator
* Navigate to: Administration / Portlet Management / Web Modules
* Find and select the remote rendering portlet web module
* Click the Update Portlet Icon to the right of the selected portlet
* Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
* Click Next and Finish
2. To update the deployed PDM Doc List Portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
* Log in to Portal as the Portal Administrator
* Navigate to: Administration / Portlet Management / Web Modules
* Find and select the PDM Doc List Portlet web module
* Click the Update Portlet Icon to the right of the selected portlet
* Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
* Click Next and Finish
3. Log out of Portal for changes to take effect.
Clear the browser cache before using the updated Web Content Manager. Review the following documentation "Configuration Changes and Options introduced in WP/WCM V7.0.0.1 and 7.0.0.2 Combined Cumulative Fixes" [http://www.ibm.com/support/docview.wss?uid=swg27021250] to see if it applies to your environment.
Back to top
Steps for uninstalling Combined Cumulative Fix
NOTE: Changing the server context root after upgrading is an unsupported uninstall path. To uninstall after changing the context root, you must first change the server context root back to the values of the previous version.
NOTE: Configuring Portal Server from a stand-alone environment to a cluster environment after upgrading is an unsupported uninstall path.
1. Perform the following steps before you uninstall the Combined Cumulative Fix: 1. If you are running an external Web server such as IBM HTTP server, stop the Web server.
2. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct. If using multiple profiles, also verify that the information in each profile is correct. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7]. * Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file.
* Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file.
* If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database user) and DbPassword (database password) parameters in the wkplc_dbdomain.properties file.
* Unix/Linux/Windows/IBM i Only: The WebSphere Portal Update Installer removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file: PWordDelete=false.
* Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server.
* WebSphere Portal 7 introduced support for multiple profiles. During the Combined Cumulative Fix uninstall the primary profile is downgraded first if one exists (The Update Installer also supports the update case for a binary only install without profiles). The primary profile is identified by two properties, ProfileDirectory and ProfileName. Ensure these properties are set before starting the downgrade process.
* If using Multiple Profiles, verify all your profiles are at the same level before starting downgrade.
2. Choose either the graphical user interface uninstallation option or the command line uninstallation option:
NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).
NOTE: If the uninstallation fails, use the IBM Support Assistant [http://www.ibm.com/software/support/isa/] to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task.
If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall="true", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.
* Enter the following command to launch the graphical user interface uninstallation program: * Windows: PortalServer_root\update> updatePortalWizard.bat
* Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh
- OR -
* Perform the following steps to launch the uninstallation program from the command line: 1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command.
2. Enter the following command to launch the uninstallation program (NOTE: Enter the command on one line): * Windows: PortalServer_root\update> updatePortal.bat -uninstall
-installDir "<PortalServer_root>"
-fix
-fixes < Cumulative fix >
* Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall
-installDir "<PortalServer_root>"
-fix
-fixes < Cumulative fix >
* IBM i: portal_server_root/update> updatePortal.sh -uninstall
-installDir "<portal_server_root>"
-fix
-fixes < Cumulative fix >
* z/OS: If the Health Checker Tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] has not been run then it needs to be run before uninstalling the Combined Cumulative Fix. Execute the following commands to uninstall the Combined Cumulative Fix: 1. From <was_profile_root>/bin directory:
. ./setupCmdLine.sh
2. PortalServer_root/update> ./updatePortal.sh -uninstall
-installDir "<PortalServer_root>"
-fix
-fixes <Cumulative fix>
Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670]. Submit the JCLs, and then return here to continue.
3. Run the following command: * z/OS: <wp_profile_root>/PortalServer/bin/UpdateProfile.sh uninstall CF skipPreCheckProfile
* All other platforms: To downgrade a profile after an uninstall, the following command can be used to downgrade all profiles (including the primary profiles). See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].
<wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh uninstall CF
4. If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps: 1. Regenerate the Web server plugin.
2. Copy the plugin-cfg.xml file to the Plugin directory.
3. Restart the Web server.
5. If you previously customized any configuration files in the wp_profile_root/PortalServer/config directory, check to see if uninstalling the cumulative fix affected those files by restoring a version of the files that was saved when the cumulative fix was originally installed. If it did affect the files, you must perform the same customization on the restored version of each file.
6. Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to uninstalling the Combined Cumulative fix. 1. To update the deployed remote rendering portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
* Log in to Portal as the Portal Administrator
* Navigate to: Administration / Portlet Management / Web Modules
* Find and select the remote rendering portlet web module
* Click the Update Portlet Icon to the right of the selected portlet
* Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
* Click Next and Finish
2. To update the deployed PDM Doc List Portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory
* Log in to Portal as the Portal Administrator
* Navigate to: Administration / Portlet Management / Web Modules
* Find and select the PDM Doc List Portlet web module
* Click the Update Portlet Icon to the right of the selected portlet
* Select the updated portlet WAR file located in: <PortalServer_root>/PortalServer/wcm/prereq.wcm/installableApps
* Click Next and Finish
3. Log out of Portal for changes to take effect.
7. Clear the browser cache before using the updated Web Content Manager.
Back to top
Known issues for latest Combined Cumulative Fix
Problem: There may be browser / functional issues in themes and in WCM when running 7002 CF levels against Internet Explorer 11 or Microsoft Edge.
Solution: It is recommended to run these browsers in compatibility mode as necessary. Also, note that some pieces of WCM functionality (exs. inability to close Workflow dialogs, Applet issues) may not work correctly with these browsers even in compatibility mode as they are not supported.
Problem: Inline help may not appear correctly after CF29 update on zOS.
Solution: From the <wp_profile_root>/ConfigEngine directory, run task
./ConfigEngine.sh expand-ear-wp.iehs.ear
Then restart the Portal server.
Problem: When using versions earlier than 'Java 6 update 45' or 'Java 7 update 51', a security pop-up dialog or error will be seen every time the WCM FileTransferApplet or Ephox EditLive editor is instantiated.
Solution: It is recommended to upgrade the Java runtime environment level to either 'Java 6 update 45' or 'Java 7 update 51' or later. Please refer to the following URL: swg21663838
Problem: After you enter a number into the number element/component, and then save the content/component more than twice, you will notice that the number field gets populated with some dots, i.e. 123.456.78. If you then click on Save again, you will get the following error:
'Enter a valid number. ( content/component name here)'
Solution: The workaround is to remove the dots and save again.
Problem: Page theme is changed to current Portal default theme when changing page content layout.
Solution: The workaround would be to change the page theme back to "Inherit Parent Theme". A fix for this issue is scheduled to be included in a future Combined CF.
Problem: After upgrading to a 7.0.0.2 Cumulative Fix and "Portal 7.0.0.2" theme has been set as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer.
Solution: Perform the following steps to resolve the issue: 1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages.
2. Select "Edit Page Properties" for the hidden page named 'Web Content Management'.
3. On the 'Edit page: Web Content Management' page, extend 'Theme:' drop-down list and select "-----Inherit Parent Theme-----".
Problem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix
Solution: Perform the following steps to resolve the issue: 1. Edit the <wp_profile>/PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct.
2. Set jcr.textsearch.enabled=true
3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem
4. Restart your Portal Server.
5. Create a new library or make changes in existing libraries
Problem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form:
CREATE STOGROUP group
VOLUMES(' volume')
VCAT category;
COMMIT;
where,
group is the name of the storage group for the database,
volume is the volume serial number of * to let SMS select the volume where the database will reside,
category is the category name of the Integrated Catalog Facility.
Solution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of "Step 2" of the sample job, just before the CREATE statements for the actual databases.
Problem: Theme Policies are not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.
Problem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme.
Solution: This is a known limitation.
Problem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1
Solution: This is a known limitation.
Problem: Loading a page with the out of box default profile (Deferred) causes "dojo is not defined" error.
Solution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc [http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc]
Problem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources.
Solution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features.
Problem: The deploy-7002-theme task fails
Solution: The Portal 7.0.0.2 theme requires several artifacts from the "Page Builder" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the "Additional instructions for a migrated environment" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc [http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc]
Problem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues.
Solution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update.
Problem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version.
Solution: To workaround this problem, the war files from [PortalServer]\wcm\prereq.wcm\installableApps have to be manually copied to [PortalServer]\installableApps. Once this is done, the update-wcm task will execute successfully.
Problem: Newly added WCM libraries might not be listed in the "Web Content Libraries" portlet on all nodes of the cluster due to an issue in cache replication.
Solution: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF.
Problem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level.
Solution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem.
Problem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder.
Solution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution.
Problem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page.
Solution: This is documented as a known limitation.
Problem: If an error is seen starting server "WebSphere_Portal" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state.
The error would appear similar to the following as part of the "action-start-portal-server-standard" task : "ADMU3027E: An instance of the server may already be running: WebSphere_Portal"
Solution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for "Node restart state" is set to Stopped for all WebSphere Portal servers that are part of the environment.
For a list of known issues for Previous WebSphere Portal 7.0.0.2 Combined Cumulative Fixes, see IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Previous Known Issues [http://www.ibm.com/support/docview.wss?uid=swg27023912]for details.
Back to top
Additional information
You can find additional information on the WebSphere Portal support page [http://www-306.ibm.com/software/genservers/portal/support/].
Back to top
Trademarks and service marks
For trademark attribution, visit the IBM Terms of Use [http://www.ibm.com/legal/us/] Web site.
Back to top | Installation of Portal 7.0 CF fails with version mismatch
Installation of Portal 7.0 CF fails with message,
"Profile version is not the same as portal binary version before updating portal binary." | To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].
<wp_profile_root>/PortalServer/bin/UpdateProfile.bat|.sh install CF |
TRAIN_Q120 | IBM WebSphere DataPower M/T 9235 appliance might incorrectly report failure of both power supplies - United States TECHNOTE (FAQ)
QUESTION
The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field.
ANSWER
The following message would be present in the DataPower logs:
System power supply #2 has failed.
or logging event code:
0x80400022 System power supply #2
The problem can be confirmed by issuing the following commands on the appliance CLI:
co
test hardware
exit
The following output from the test hardware command confirms this problem:
[failure] Power supply '1' has no AC input power, or is not present.
[failure] Power supply '2' has no AC input power, or is not present.
Other results in the test hardware command might also show incorrect values.
This problem does not affect the operation of the appliance other than the continuous reporting power supply failure message.
To confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.
To recover from the false errors perform a reboot of the appliance:
From the WebGUI:
Control Panel → System Control → In the “Shutdown” section choose “Reboot System” then click “Shutdown”
From the CLI:
top
shutdown reboot
y
This problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance
If the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information:
1) How many times have you seen the issue on the same appliance?
2) Gather the outputs for the following CLI commands:
show clock
show version
show ipmi
show sensors-other
config
service show
test hardware | I am receiving AC power supply failures on my DataPower 9235 appliance. How can I resolve this?
I am observing the following errors on my DataPower 9235 device:
[failure] Power supply '1' has no AC input power, or is not present. [failure] Power supply '2' has no AC input power, or is not present.
How can this be resolved? | In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. |
TRAIN_Q121 | IBM Default number of threads for ncp_poller - United States Available threads for ncp_poller TECHNOTE (FAQ)
QUESTION
What are the number of threads assigned by default for ncp_poller? Is the same number of threads applicable for additional Pollers too?
ANSWER
There are 100 threads assigned for default Pollers in all three releases (v3.7, v3.8 & v3.9).
The additional poller is a new feature in v3.8 and higher versions, so additional Poller threads is not applicable for v3.7. But when you create additional pollers in v3.8/v3.9 same # of thread (i.e. 100) pool is assigned.
In v3.8, v3.9 - you can also increase the default 100 to a higher value by modifying and uncommenting the following line in $NCHOME/etc/precision/NcPollerSchema.cfg
//update config.properties set BatchExtraThreads = 150; | ncp_poller failed with Out-of-memory in ITNM 3.9 FP4+IF1. What went wrong?.
ncp_poller is failed with out-fo-memory even if we have ITNM 3.9 FP4+IF1 latest FP
2016-04-11T03:02:09: Fatal: F-RIV-002-014: [31869t] CRivError.cc(386) Out-of-memory - This process has run out of memory or exceeded the operating system memory limit for a 32 bit application - You must take action to reduce the amount of data this application is having to process new handler called
How to resolve this issue?.
| There are 100 threads assigned for default Pollers in all three releases (v3.7, v3.8 & v3.9).
The additional poller is a new feature in v3.8 and higher versions, so additional Poller threads is not applicable for v3.7. But when you create additional pollers in v3.8/v3.9 same # of thread (i.e. 100) pool is assigned.
In v3.8, v3.9 - you can also increase the default 100 to a higher value by modifying and uncommenting the following line in $NCHOME/etc/precision/NcPollerSchema.cfg
//update config.properties set BatchExtraThreads = 150; |
TRAIN_Q122 | IBM Some portal resources have been updated, however a long cache was set so the updates are not being served. - United States TECHNOTE (FAQ)
QUESTION
The resolver uses the digest to cache some URLs like resource aggregator collections, and the digest remains the same between restarts. Resources like theme files are served from the browser or proxy cache (HTTP 304) and not loaded from the server.
ANSWER
The resolver uses the digest to cache some URLs like resource aggregator collections, and the digest remains the same between restarts.
In order to force a digest change (should some resources have changed and a long cache was set), you can set the "digest.seed" key in the WP ConfigService to any string value, which will be used in generating a new digest on server boot. This will force a digest change when you want a new one during a restart.
Changing the digest setting generates different URLs, so the updated theme resources can be loaded from the server. | Why Theme Updates are not updated in the browser cache ?
If you change graphics in page header. Then packed the war file and update it via the Integrated Solutions Console. But the old graphic is still displayed until the user press Ctrl + F5 in Internet Explorer. | Changing the digest setting generates different URLs, so the updated theme resources can be loaded from the server. |
TRAIN_Q123 | IBM SCA destinations for IBM Business Process Manager (BPM), WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB) are not preserved when uninstalling and reinstalling a service module - United States SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
When a Service Component Architecture (SCA) module is uninstalled, by default, its associated destinations are removed, even if there are still messages in the destination queue. In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved.
RESOLVING THE PROBLEM
To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.
Cross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5
PRODUCT ALIAS/SYNONYM
BPM
WPS
WESB | Updating SCA applications & internal SCA module queues When updating an existing SCA module using the ISC, I noticed that internal SCA queues (sca/<module>/...) on the SCA.SYSTEM bus) are deleted and recreated. One can potentially loose messages on these queues. Is there a fix to the problem? | To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations. |
TRAIN_Q124 | IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States FIXES ARE AVAILABLE
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]
SUBSCRIBE
You can track all active APARs for this component.
APAR STATUS
* CLOSED AS PROGRAM ERROR.
ERROR DESCRIPTION
* A PFBC file might fail to apply. Wsadmin will show an error
similar to this:
java.lang.Exception: java.lang.Exception: ADMG0660E:
Properties File Validation during command
applyConfigProperties failed. See Report file for details.
The report file will contain an error similar to this:
Error=java.lang.NullPointerException
at
com.ibm.websphere.management.configservice.ConfigServiceHelper.g
etConfigDataType(ConfigServiceHelper.java:235)
at
com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work
spaceHelper.java:563)
at
com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator
(WorkspaceHelper.java:584)
at
com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu
tes(ConfigServiceImpl.java:2102)
at
com.ibm.ws.management.commands.properties.resources.common.Apply
Properties.setProperties(ApplyProperties.java:240)
LOCAL FIX
PROBLEM SUMMARY
* ****************************************************************
* USERS AFFECTED: All users of IBM WebSphere Application *
* Server Property File Based Configuration *
****************************************************************
* PROBLEM DESCRIPTION: A Property File Based Configuration *
* (PFBC) file might fail to apply. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A recent (8.5.5.5) parser change introduced a problem where
types that have default values noted in the file and are not
Strings can be incorrectly processed. For example:
isolatedClassLoader=false #boolean,default(false)
might be incorrectly processed, and as a result, the file
might not apply.
PROBLEM CONCLUSION
* The parsing code is updated so the problem no longer occurs.
The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.6. Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]
TEMPORARY FIX
COMMENTS
APAR INFORMATION
* APAR NUMBER
PI37248
* REPORTED COMPONENT NAME
WEBS APP SERV N
* REPORTED COMPONENT ID
5724H8800
* REPORTED RELEASE
850
* STATUS
CLOSED PER
* PE
NoPE
* HIPER
NoHIPER
* SPECIAL ATTENTION
NoSpecatt / Xsystem
* SUBMITTED DATE
2015-03-18
* CLOSED DATE
2015-03-20
* LAST MODIFIED DATE
2015-03-24
* APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:
* APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:
FIX INFORMATION
* FIXED COMPONENT NAME
WEBS APP SERV N
* FIXED COMPONENT ID
5724H8800
APPLICABLE COMPONENT LEVELS
* R850 PSY
UP | Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written If you are trying to install Portal v8.5 on WAS 8.5.5.5 or less it may fail when running the manageprofiles.sh. You will get this exception; SEVERE
com.ibm.ws.profile.cli.WSProfileCLIAugmentProfileInvoker
executeWSProfileAccordingToMode
1
INSTCONFFAILED: Profile augmentation failed. For more
information, consult
/opt/IBM/WebSphere/AppServer8/logs/manageprofiles/portal01_create.log. | The parsing code is updated so the problem no longer occurs.
The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.6. |
TRAIN_Q125 | IBM Diagnosing a java.lang.StackOverflowError - United States StackOverflow; overflowing; recursion; recursively; jit; JustInTime; Hot; Spot; WebSphere; Just-In-Time TECHNOTE (TROUBLESHOOTING)
PROBLEM(ABSTRACT)
Stack Overflow exceptions can occur when a thread stack continues to grow in size until reaching the maximum limit.
SYMPTOM
A stack overflow can result from:
* A deeply nested application
* An infinite loop within an application
* A problem in just-in-time (JIT) compiled code
* Applications requiring a larger stack size, especially ones relying on XML, GUI, or java2D classes.
* Native method calls
Stack overflow issues are frequently masked by Out of Memory exceptions. By resolving the memory constraints, the stack overflow can be resolved.
CAUSE
When a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java™ Virtual Machine (JVM) process, or the native stack size configured by the operating system.
Some applications require stacks that are larger than the default size; for example, a graphics-intensive Java program can require a larger stack, which may require an increase in the stack size to avoid StackOverflow.
DIAGNOSING THE PROBLEM
Look for either Out of Memory messages or java.lang.StackOverflow in the server logs. The process may continue to run after either of these messages are seen.
If a crash did occur, a javacore should have generated on IBM SDK. You will either see the signal as SIGSEGV, SIGILL, SIGABRT, or SIGBUS. Usually the current thread will indicate the following
pending=java.lang.StackOverflowError
RESOLVING THE PROBLEM
[/support/docview.wss?uid=swg21162896&aid=1]Explanations and Solutions
[/support/docview.wss?uid=swg21162896&aid=2]Detailed Configuration Options
Explanations and Solutions
Infinite Recursion
If an application is performing recursion, the maximum stack size can easily be reached and a Stack Overflow exception is thrown. The thread stack has a limited size and eventually its space will run out as the thread stack grows without bounds.
Some traits of recursion:
- Large thread stacks that appear to repeat
- An infinite loop that continuously spawns off threads
- Very large XML documents loaded into the Document Object Model (DOM)
- JSP or servlets calling itself (usually by executing forward or include to itself)
- Repeated calls in native functions
Increasing the thread stack size allows for larger thread stacks. However if the recursion continues to trigger a stack overflow, the next step is to identify what code is causing the recursion from javacores, thread dumps, or even system core files.
A thread stack that indicates it's too large to display can be an indicator of stack overflow. This is especially true if the stack appears to repeat (such as recursive method calls).
JIT/HotSpot Compiled Code
The JIT/HotSpot compiler (JIT) is designed to speed up the JVM execution times by compiling method calls. This can speed up execution time, but as more aggressive optimizations are used, this can inadvertently cause recursion, resulting in stack overflow or crash. The documents linked below explain how to debug JIT and HotSpot compiler issues: * JIT Problem Determination for IBM SDK 5.0 and 6.0 using -Xjit [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21294023]
* Debugging HotSpot failures on the Solaris and HP-UX operating environment [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21081179]
Depleted Native Stack
It is almost guaranteed that a crash will occur if the native stack runs out of space. System cores can be used to identify long and possibly recursively looping native thread stacks.
To resolve, increase the native stack size (usually by adjusting the operating system limit for stack size) to accommodate the recursive native calls; however, identifying the recursive native calls will help determine the root cause of the stack overflow.
[/support/docview.wss?uid=swg21162896&aid=3] Back to top
[http://www.ibm.com/i/v14/rules/dotted_blue_rule_443.gif]
Detailed Configuration Options
Adjusting the Stack Sizes (Xss and Xmso) options
If this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources.
For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow.
* Maximum Thread Stack Size (-Xss)
*
*
*
*
* -Xss<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
*
*
*
* there is no distinction between native and thread stack sizes
*
* only
*
* HP-UX
*
*
*
* -XX:MainThreadStackSize=<size>
*
*
*
*
*
*
*
* Initial Thread Stack Size (-Xiss)
*
* This is only for distributed platforms (AIX, Linux, Windows)
*
*
*
*
*
* -Xiss<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
*
* Initial Native Stack Size (-Xmso)
*
* This is only for distributed platforms (AIX, Linux, Windows)
*
*
*
*
*
*
* -Xmso<size>
*
* <size>
*
* nn[k|m|g|K|M|G]
*
*
*
*
Default Values
This is a chart of default sizes for the various stack size arguments. This is subject to change due to upgrades of the SDK.
[/support/docview.wss?uid=swg21162896&aid=4]
Value [/support/docview.wss?uid=swg21162896&aid=4]
AIX [/support/docview.wss?uid=swg21162896&aid=4]
Linux [/support/docview.wss?uid=swg21162896&aid=4]
Windows [/support/docview.wss?uid=swg21162896&aid=4]
Solaris [/support/docview.wss?uid=swg21162896&aid=4]
HP-UX [/support/docview.wss?uid=swg21162896&aid=4]
Initial Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
2KB [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Maximum Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
256KB (32-bit)
512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Not Adjustable [/support/docview.wss?uid=swg21162896&aid=4]
Native Stack Size [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
256KB [/support/docview.wss?uid=swg21162896&aid=4]
32KB (32-bit)
256KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
512KB (32-bit)
1024KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]
64KB (PA-RISC)
1024KB (Itanium) [/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=4]
[/support/docview.wss?uid=swg21162896&aid=5] Back to top
Examples of Stack Overflow
Server Logs
These logs may contain references to StackOverflow, alongside other messages. Thread stacks may accompany these messages, indicating if there is a recursive call.
* SystemOut.log example
* [3/14/15 3:14:15:926 CST] 31415926 BaseMap W CWOBJ0006W: An exception occurred:
*
* com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.lang.StackOverflowError
*
* <<Thread stack may follow this message>>
*
*
*
*
* SystemErr.log example
* [3/14/15 3:14:15:926 PST] 31415926 SystemErr R Caused by: java.lang.StackOverflowError
*
* at java.util.Hashtable.get(Hashtable.java:461)
*
* at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:1257)
*
* at psdi.webclient.system.session.WebClientSession.applySkin(WebClientSession.java:295)
*
* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1177)
*
* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)
*
* at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)
*
* ...
*
*
Javacore
In javacores, look for "StackOverflowError" in the thread name entry: 3XMTHREADINFO "ORB.thread.pool : 19" (TID:10167F78, sys_thread_t:E072BCE0, state:R, native ID:E06BEBA0) prio=5: pending=java.lang.StackOverflowError
System Dump (processed with jextract and DTFJ Dump Analyzer)
Look for this message near the end of a very large stack. This particular example had 1000 recursively called entries. Java stack frames dump is too long: <analyzererror>
Cross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK | completeness report causes StackOverflowError in Decision Center
When running the completeness report in Decision Center we sometimes get a StackOverflowError such as:
...
Caused by: java.lang.StackOverflowError
at ilog.rules.validation.solver.IlcIntScalProd.extract(IlcIntScalProd.java:89)
at ilog.rules.validation.solver.IlcIntExpr.getPIntExp(IlcIntExpr.java:156)
...
| Adjusting the Stack Sizes (Xss and Xmso) options
If this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources.
For every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow. |