id
string | question
string | answer
string | is_impossible
bool | contexts
list |
|---|---|---|---|---|
TRAIN_Q000 | 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> | false | [
{
"filename": "swg21996508.txt",
"text": "Title: 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\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n 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. \n\nCONTENT\nProblem Description\nWhen running Streams as a system service with Streams releases 4.1.1.1\nor 4.1.1.2, toolkits and user applications that depend on the\nuser environment may have various errors.\nFor example the database toolkit might show the following error\nif it does not pick up the ODBCINI environment variable:\n\n\n\n * \"An SQL operation failed. The SQL state is 08003, the SQL code\n is 0 and the SQL message is [unixODBC][Driver\n Manager]Connnection does not exist.\"\n * \n\nProblem Solution \n\nTo work around the issue, set environment variables that are needed by the application directly in the instance with: * \n \n * streamtool setproperty\n * -d <domain> -i <instance>\n --application-ev <VARIABLE NAME>=<VARIABLE VALUE>\n * \n \n\n\nRELATED INFORMATION\n APAR IT18432 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IT18432]"
}
] |
TRAIN_Q001 | 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 | false | [
{
"filename": "swg21675316.txt",
"text": "Title: IBM Exit() action within User Defined Function in Impact Policy Language - United States\n\nText:\nnetcool; 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)\n\nQUESTION\n and how to exit the Policy process from within a Custom Function \n\nCAUSE\nUsing 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.\n\nANSWER\nThis 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: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * If(GetGlobalVar(\"ExitNow\") == 1)\n * \n * {\n Log(ID+WP+\": Existing policy...\");\n \n * Exit\n * ();\n }\n\n\nThe 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]. \n\nIf 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. \nRELATED INFORMATION\n Event Flagging with Go_NoGo checking [http://www-01.ibm.com/support/docview.wss?uid=swg21675015]\nStructured Logging in Policies [http://www-01.ibm.com/support/docview.wss?uid=swg21596180]"
}
] |
TRAIN_Q002 | Why are replies going to the DLQ with reason 2189 MQRC_CLUSTER_RESOLUTION_ERROR
I have changed my cluster receiver to match the IP address used and now I am seeing replies in my DLQ with 2189 MQRC_CLUSTER_RESOLUTION_ERROR. The reply queue is on a different cluster which this qmgr is a member of. The reply message uses replytoqmgr and queue name. The qmgr should see the replytoqmgr in the cluster and get the message over to the queue, but instead goes to dead letter queue. This queue manager is a repository to one cluster and a member of another. | - | true | [] |
TRAIN_Q003 | 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 | false | [
{
"filename": "swg21179559.txt",
"text": "Title: IBM Guide to properly setting up SSL within the IBM HTTP Server - United States\n\nText:\nssl; handshake; secure socket layer; handshake failed; enable; ssl config; ssl setup; setup; IHS; crl; revocation; ssl; ssl; ssl; configure; config; config; config TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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. \n\nRESOLVING THE PROBLEM\nThe following steps help guide you through the proper set up of SSL within the IBM HTTP Server: \n\n 1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements\n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n \n 3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 5. Information that IBM WebSphere® Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server\n\n\n\n\n\n\n 1. Confirm that the Global Security Kit is installed and meets the minimum requirements\n \n 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.\n \n 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].\n \n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n 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.\n \n 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] \n \n 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] \n * 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] \n * 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] \n * 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] \n \n \n \n \n 3. Enable SSL directives within the IBM HTTP Server's configuration file (httpd.conf)\n 1. Verify that the SSL modules are uncommented\n * For Microsoft® Windows®:\n \n \n LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&aid=1]\n \n \n * For UNIX® platforms:\n \n \n LoadModule ibm_ssl_module modules/mod_ibm_ssl.so [/support/docview.wss?uid=swg21179559&aid=2]\n \n \n \n \n 2. Create an SSL virtualhost stanza using the following examples and directives\n \n 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.\n \n http://www.mycompany.com (non-SSL) 192.168.1.102 https://www.mycompany.com (SSL) 192.168.1.102\n \n Example 1:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n Listen 443\n <VirtualHost :443>\n SSLEnable\n SSLClientAuth None\n </VirtualHost>\n \n SSLDisable\n KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 [/support/docview.wss?uid=swg21179559&aid=3]\n \n 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.\n \n 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\n \n Example 2:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n <VirtualHost 192.168.1.103:80>\n ServerName www.mycompany2.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n Listen 443\n <VirtualHost 192.168.1.103:443>\n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n SSLDisable\n KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n 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\".\n \n 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\n \n Example 3:\n \n Listen 80\n ServerName www.mycompany.com\n \n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n <VirtualHost 192.168.1.103:80>\n ServerName www.mycompany2.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.104:80>\n ServerName www.mycompany3.com\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs3\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n </VirtualHost>\n \n Listen 443\n <VirtualHost 192.168.1.102:443>\n ServerName www.mycompany.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.103:443>\n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany2\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs2\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n </VirtualHost>\n \n <VirtualHost 192.168.1.104:443>\n ServerName www.mycompany3.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany3\n <Directory \"c:/Program Files/IBM HTTP Server/htdocs3\">\n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n </Directory>\n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n </VirtualHost>\n \n SSLDisable\n KeyFile \"c:/program files/ibm http server/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n \n \n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf).\n \n * How to rewrite HTTP (port 80) requests to HTTPS (port 443)\n 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].\n \n \n * Logging SSL request information in the access log for IBM HTTP Server\n 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].\n \n \n * Enabling Certificate Revocation Lists (CRL) in the IBM HTTP Server\n 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] \n * 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] \n * 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]\n \n \n \n \n \n 5. Information that IBM WebSphere Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server\n * MustGather: SSL handshake and configuration problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141302]\n \n * MustGather: CMS key database (.kdb) and certificate problems [http://www.ibm.com/support/docview.wss?rs=177&context=SSEQTJ&uid=swg21141303]\n \n \n\n * \n * Brief description of the SSL directives discussed in this document\n * \n \n Listen\n * \n * \n * \n * \n * SSLEnable\n * \n * \n * \n * \n * SSLClientAuth None\n * \n * \n * \n * \n * SSLDisable\n * \n * \n * \n * \n * KeyFile\n * \n * \n * \n * \n * SSLV2Timeout\n * \n * \n * \n * \n * SSLV3Timeout\n * \n * \n * \n * \n * SSLServerCert\n * \n * \n * \n * \n * SSLCipherSpec\n * \n * \n * \n * \n * SSLCipherRequire\n * \n * \n * \n * \n * \n * \n * 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]"
}
] |
TRAIN_Q004 | Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux (CVE-2018-6551 CVE-2018-6485)
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-IDs:
CVE-2018-6551
CVE-2018-6485
Where can I find this information? | - | true | [] |
TRAIN_Q005 | 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. | false | [
{
"filename": "swg21903536.txt",
"text": "Title: IBM Support's Guide to Rules File Processing - United States\n\nText:\nrules; rules file; array TECHNOTE (FAQ)\n\nQUESTION\n Support Guide : Are there any rules file examples? \n\nANSWER\n \n\nThe Netcool Technical Support Guide to rules file processing is provided as a collection of commonly used rules file techniques. \n\nPlease refer to the Netcool/OMNIbus Probe and Gateway Guide for general guidance to rules file processing.\n\nRulesfileProcessing_SupportsGuide_30.pdf [/support/docview.wss?uid=swg21903536&aid=2]RulesfileProcessing_SupportsGuide_30.pdf [/support/docview.wss?uid=swg21903536&aid=1]"
}
] |
TRAIN_Q006 | 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) | false | [
{
"filename": "swg22008493.txt",
"text": "Title: IBM Security Bulletin: IBM Tivoli Network Manager IP Edition is affected by an Apache CXF vulnerability (CVE-2017-3156) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Vulnerability has been addressed in the Apache CXF component of Tivoli Network Manager IP Edition. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3156 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3156]\nDESCRIPTION: 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.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/130249 [https://exchange.xforce.ibmcloud.com/vulnerabilities/130249] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nTivoli Network Manager IP Edition 4.1.1 (Huawei MTOSI Collector install)\nTivoli Network Manager IP Edition 4.2.0 (Huawei MTOSI Collector install)\n\nREMEDIATION/FIXES\n \n\nProduct 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.\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043575 [http://www-01.ibm.com/support/docview.wss?uid=swg24043575] WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 15 September 2017 : Original Version Published \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q007 | 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)' | false | [
{
"filename": "swg21636093.txt",
"text": "Title: IBM 2035 MQRC_NOT_AUTHORIZED Connecting to WebSphere MQ from WebSphere Application Server via CLIENT Bindings - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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 \n\nSYMPTOM\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')\n\n\nCAUSE\nThe two most likely reasons why the connection is refused by MQ are as follows: \n\n 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.\n We discuss how this user identifier is obtained and passed over the connection in more detail below.\n For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:\n AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained.\n For UNIX no entry in the MQ error logs would be seen by default.\n 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. \n 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.\n The following error in the MQ error logs would be seen for this scenario:\n AMQ9777: Channel was blocked\n\nSee 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. \nDIAGNOSING THE PROBLEM\nTo 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. \n\nPlease note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections.\nPassword 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]. \n\nFor 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: \n\n * Mutual SSL/TLS authentication.\n 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. \n * A custom, or 3rd party supplied, WebSphere MQ Security Exit\n 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.\n 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.\n\n\nMCA 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. \n\nIt is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL/TLS authentication exclusively for authentication. \n\nDefault behaviour when no credentials are supplied in the application server \n\nIf 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. \n\nAs 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. \n\nContainer-managed security for outbound connections \n\nThe 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. \n\nUsernames 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. \n\nContainer-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. \n\nThen 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: \n\nConnectionFactory myCF = (ConnectionFactory)ctx.lookup(\"java:comp/env/jms/MyResourceRef\") \n\nAn EJB 3.0 application might declare an annotated object property on the bean as follows:\n@Resource(name = \"jms/MyResourceRef\", \nauthenticationType = AuthenticationType.CONTAINER)\nprivate javax.jms.ConnectionFactory myCF; \n\nWhen 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. \n\nIt 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. \n\nA 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:\n[/support/docview.wss?uid=swg21636093&aid=1] [/support/docview.wss?uid=swg21636093&aid=1] \n\nDefault component-managed authentication alias for outbound connections \n\nFor 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. \n\nThis 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: \n\n * JACL:\n wsadmin>set cell [ $AdminConfig getid \"/Cell:mycell\" ]\n \n mycell(cells/mycell|cell.xml#Cell_1)\n \n wsadmin>$AdminTask listWMQConnectionFactories $cell\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)\n \n wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }\n \n MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104) \n * Jython:\n wsadmin>cell = AdminConfig.getid(\"/Cell:mycell\")\n \n wsadmin>AdminTask.listWMQConnectionFactories(cell)\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n \n wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")\n \n 'MyCF(cells/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n\n\nAuthentication 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. \n\nAuthentication alias for inbound MDB connections using a listener port \n\nFor 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. \n\nOn 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.\n\n\nRESOLVING THE PROBLEM\nThe simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows: \n\n 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. \n 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:\n SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY) \n 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:\n ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')\n\n\nThe 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. \n\nIn 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. \n\nIf 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. \n\nIf 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. \n\nIf 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. \n\nAll 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'):\nALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH')\nSTOP CHL(SYSTEM.DEF.SVRCONN) \n\nDetails 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: \n\n * To configure the certificates and trust of the MQ queue manager see the following topic:\n 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] \n * To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:\n Configuring SSL channels [http://publib.boulder.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.explorer.doc/e_ssl_channels.htm]\n\n\nDetails 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:\n SSL configurations [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]\n 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:\n 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] \n * 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\n WebSphere MQ messaging provider connection factory settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pjcfm]\n WebSphere MQ messaging provider activation specification settings [http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-dist&topic=umj_pasm]\n\n \n\nCross 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"
}
] |
TRAIN_Q008 | 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. | false | [
{
"filename": "swg21263677.txt",
"text": "Title: IBM Rational Application Developer Support Policy for 64 bit technology - United States\n\nText:\nRSM; 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)\n\nQUESTION\n 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? \n\nCAUSE\nThe 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.\n\nANSWER\nThe following IBM Rational Software version 7.x products are only supported on specified 64 bit operating systems running in 32 bit mode: \n\n * Rational Application Developer for WebSphere Software \n * Rational Software Architect \n * Rational Software Modeler \n * Rational Systems Developer\n\n\nSimilarly, 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.\nThere 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. \n\n \n\nThese 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. \n\nExamples of some 64 bit Operating Systems: \n\n * Microsoft Windows XP Professional x64 Edition (running on an AMD or Intel processor) \n * Microsoft Windows 7 Professional 64-bit \n * Red Hat Linux Enterprise Server 4+ running on x86-64 bit \n * 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.\n 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)\n 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)\n\n\n\nNote: RSDP 32-bit JVM based products, do not require any additional or special set-up on a supported 64-bit operating system (O/S). \nThey run on the provided/supported 32-bit JVM for that RSDP product, as is. \n\nReview the following documents for more details on the system requirements: \n * (7014264) Rational Application Developer System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014264] \n * (7014274) Rational Software Architect Family System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014274] \n * (7014269) Rational Software Modeler System Requirements List [http://www.ibm.com/support/docview.wss?uid=swg27014269]\n \n\n\nThe 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: \nKnown problems and limitations to installing 64-bit Rational Application Developer [http://www.ibm.com/support/docview.wss?uid=swg21499482] \nas referred to by the above Rational Application Developer System Requirements List. The following technote: \n- 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] \n, especially Benefits, describes what is possible with a larger heap size with the 64-bit JVM. \n\nIn 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. \n\nIf you have any further questions, contact IBM Support for Rational Application Developer, or the appropriate IBM RSDP product support team. \n\n\nWebSphere Servers that are shipped with RSDP products: \n\nThe 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. \n\nThe 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. \n\nThe 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. \n\nNote: 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\n Benefits for RSA v8.0.3 products running as 64-bit app [http://www.ibm.com/support/docview.wss?uid=swg27021665]\nInternet Explorer v9+ required if using 64-bit Bit Mode [http://www.ibm.com/support/docview.wss?uid=swg21502701]\nRAD 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]\nRational ClearCase SCM adapter not available for 64-bit [http://www.ibm.com/support/docview.wss?uid=swg21502974]\nCannot install the Java Visual Editor in RAD 64 bit [http://www.ibm.com/support/docview.wss?uid=swg21499219]\nRAD64bit Known problems to install or run [http://www.ibm.com/support/docview.wss?uid=swg21499482]\nWAS 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]\nAbout SCM Adapter support on 64 Bit [http://www.ibm.com/support/docview.wss?uid=swg21460547]\nConversion of 32 bit to 64 bit WAS on the same machine [http://www.ibm.com/support/docview.wss?uid=swg21625930]\nRAD901: 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]\nRAD 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]\nRAD 9.0.1 System Requirements - O/S [http://www-969.ibm.com/software/reports/compatibility/clarity-reports/report/html/osForProduct?deliverableId=1374678040873#osFamily-1]\nRSA(4WS) 9.0.x: new features and enhancements [http://www.ibm.com/support/docview.wss?uid=swg27038488]\nRSA 9.1.2: new features and enhancements - jdk [http://www-01.ibm.com/support/docview.wss?uid=swg27041555#whatsnew_912_JTE]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21504145]\n\n\n \n\n\nCross 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"
}
] |
TRAIN_Q009 | 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 | false | [
{
"filename": "swg21696083.txt",
"text": "Title: IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States\n\nText:\nACCE; CE; Property; FEM TECHNOTE (FAQ)\n\nQUESTION\n With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class\n\n1. Launch FEM\n2. Expand the object store and document class tree. Right click on the document class and select \"Properties\"\n3. Go to \"Properties Definitions\" tab, highlight the property definition and click \"Edit\"\n4. Make the modification and click OK\n5. Click OK again to save the change\n\nHow to perform the same operation with FileNet Content Engine - ACCE? \n\nANSWER\nFollow the below steps to update the property definition properties on ACCE: \n\n\n\n\n 1. Launch ACCE \n 2. Expand the object stores folder and click the object store to open the Object store tab \n 3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab \n 4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify \n 5. ACCE will open that property definition in a new Properties tab \n 6. Modify the property definition as required \n 7. Go back to the Class Definition tab and click Save"
}
] |
TRAIN_Q010 | 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. | false | [
{
"filename": "swg21515420.txt",
"text": "Title: IBM Starting WebSphere Application Server gives warning message - Could not lock User prefs - United States\n\nText:\nWebsphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. \n\nSYMPTOM\nThe following message can be seen in the systemout.log: \n\n[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.\n[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.\n\n\nCAUSE\nThe 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.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file. \n\n\nDIAGNOSING THE PROBLEM\nFor 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. \n\n\nFor root, verify if the /etc/.java/.systemPrefs exists\n\n\nRESOLVING THE PROBLEM\nFor non-root : \n\nCreate 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 : \n\nNOTE : 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. \n\n1. Try giving 755 permission for /home/wasadmin/.java/.userPrefs \n\n2. Add \"-Djava.util.prefs.userRoot=/home/wasadmin/preps\" as a SDK generic jvm argument \n\n\nTo set the argument on the SDK: \n\n 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.. \n 2. Then, in the Server Infrastructure section, click Java and process management > Process definition > Java virtual machine. \n 3. Specify -Djava.util.prefs.userRoot=/home/wasadmin/preps for the Generic JVM Arguments property, and click OK . \n 4. Click Save to save your changes. \n 5. Restart the application server.\n\n\nFor root : 1. Create a Java system pref directory\n sudo mkdir -p /etc/.java/.systemPrefs \n 2. Restart the application server."
}
] |
TRAIN_Q011 | 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. | false | [
{
"filename": "swg21966637.txt",
"text": "Title: 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\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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.\n\nYou receive the following message:\n\n\n\"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.\n\n\"\n\nOnce this message is displayed the only option available is \"OK\" to click on and you cannot enter your authorization code. \n\nRESOLVING THE PROBLEM\nBelow is a picture of the warning: \n\n[/support/docview.wss?uid=swg21966637&aid=1] [/support/docview.wss?uid=swg21966637&aid=1]\n\nIf you encounter this message, perform the following procedure:\n\n\n 1. If open, close the IBM SPSS Statistics product. \n 2. If open, close the License Authorization Wizard. \n 3. Open Finder. \n 4. Select the 'Go' menu. \n 5. Select the 'Utilities' menu. \n 6. Open the 'Terminal' program. \n 7. Type (copy/paste) the following command:\n \n cd /Applications/IBM/SPSS/Statistics/ \n 8. \n 9. Press Enter/Return. \n 10. Perform the procedure corresponding to the Statistics product version as described below:\n\n\nStatistics Release 20 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 21 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 21\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 22 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 22\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\n\nStatistics Release 23 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 23\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 24 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 24\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product. \n 7. \n 8. \n\nStatistics Release 25 1. Type (copy/paste) the following command: \n \n sudo chown -R root:admin 25\n \n 2. Press Enter/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nTo confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22) \n\ncd /Applications/IBM/SPSS/Statistics/22/SPSSStatistics.app/Contents \n\nthen, type the following: \n\nls -l \n\n(2) Press Enter/Return. \n\n \n\nIf 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. \n\nPicture1:\n[/support/docview.wss?uid=swg21966637&aid=2] [/support/docview.wss?uid=swg21966637&aid=2]\n\nPicture 2: \n\nIf you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.\n[/support/docview.wss?uid=swg21966637&aid=3] [/support/docview.wss?uid=swg21966637&aid=3]\n\nThis behavior is also reported on the following product correction report (APAR): [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n[https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\nhttps://www.ibm.com/support/entdocview.wss?uid=swg1PI41134 [https://www-304.ibm.com/support/entdocview.wss?uid=swg1PI41134]\n\nAn IBM ID is required to access this material.\n\nIf needed, an IBM ID may be created at https://ibm.biz/ibm_web_id [https://ibm.biz/ibm_web_id]\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https://developer.ibm.com/answers/topics/spsslicensing.html]"
}
] |
TRAIN_Q012 | 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. | false | [
{
"filename": "swg21648497.txt",
"text": "Title: IBM Insufficient ulimit Value Causes Native OutOfMemory - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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. \n\nSYMPTOM\nAn out of memory Dump Event such as: \n\n\"systhrow\" (00040000) Detail \"java/lang/OutOfMemoryError\"\n\"Failed to create a thread: retVal -1073741830, errno 11\" received\n\nNote: This detailed message will appear only in javacores.\n\n\nDIAGNOSING THE PROBLEM\nWhen 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. \n\nThe 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.\n\nThe 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]\".\n\nUser Limits (in bytes except for NOFILE and NPROC) \n\ntype 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 \n\nFor 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. \n\nWebSphere 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. \n\nBy 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. \n\nOnce the ulimit is increased, the WebSphere Application Server will need to be restarted to use the \nnew setting. In the case of WebSphere Application Server ND, the nodeagent and the servers on the nodes will need to be restarted."
}
] |
TRAIN_Q013 | 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. | false | [
{
"filename": "swg21618719.txt",
"text": "Title: IBM Applying TIP 2.2 fix packs directly to a TIP 2.1 installation - United States\n\nText:\nTIPL2; TIPL2INST; tivoli Integrated portal; feature pack TECHNOTE (FAQ)\n\nQUESTION\n Can Tivoli Integrated Portal 2.2 fix packs be applied directly to a TIP 2.1 installation?\n\n\nANSWER\nIn 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]. \n\nThe following three items should be obtained from Fix Central: \n\n * 2.2.0.1-TIV-TIP-<platform>-RP0001 \n * 2.2.0.1-TIV-TIP-FITSuit-RP0001vx \n * 2201-fixpack-guide-PDF.pdf\n\n\n\nTo determine the installed TIPCore version, review the DE listIU command output. Details on the listIU command are included in the following technical note: \nhttp://www-01.ibm.com/support/docview.wss?uid=swg21615989 [http://www-01.ibm.com/support/docview.wss?uid=swg21615989]"
}
] |
TRAIN_Q014 | 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. | false | [
{
"filename": "swg21983839.txt",
"text": "Title: IBM Problems installing NMA agent (N4 agent) on Linux x86-64 - United States\n\nText:\nITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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. \n\nSYMPTOM\n1) The import of the whole bundle using command: \n\n/opt/IBM/ITM/bin/tacmd addbundles -i <inst_media>/ITMfVE_Agents/unix\n\nwill fail with message:\n\nUnable to find bundle prerequisite: ci 06.22.04.000 li6263\n\n--\n\n2) 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).\n\n--\n\n3) 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.\nThe 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.\n\n\nCAUSE\nThe 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.\n\n\nRESOLVING THE PROBLEM\nThe issues should be corrected at Installer level, APAR IV84919 has been opened to fix them. \n\nAnyway, since the correction involves the installation component, it will not be available until next release, when the Installation package will be built again. \n\nUntil then, you can bypass the issue with some manual steps. \n\n--------------- \n\n1) If the import of agent bundle using command tacmd addbundles fails with message: \n\nUnable to find bundle prerequisite: ci 06.22.04.000 li6263\n\nthis 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. \n\nThere 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. \n\nIt can be anyway useful to know the workaround as it can be applied to other agents for which remote installation instead correctly works.\n\nYou must verify if the prerequisites mentioned in the error message are already present in your depot by using command tacmd viewdepot.\nBeside of the one mentioned in the error message, you must be sure that also the other wanted prerequisites are already present in the depot.\n\nN4 agent has the following prerequisites:\n\nProduct Code : n4 \nDeployable : True \nVersion : 062200000 \nDescription : Monitoring Agent for Network Devices \nHost Type : li6263 \nHost Version : li6263,lx8266 \nPrerequisites: ci:062204000 la:ipaddr05400 gs:074027000 jr:051201000 \nui:062204000 ax:062204000\n\nIf 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.\n\nIf you do not have the wanted prerequisite levels, you have two possible options:\n\na) retrieve and add them into depot from other ITM installation packages\nb) modify the agent dsc files and change the level of the components required by the agent to match the level delivered with the bundle.\n\nFor 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:\n\n<PrereqProdCode>ci</PrereqProdCode>\n\n<PrereqVersion>\n\n<Version>06</Version>\n\n<Release>22</Release>\n\n<Mod>04</Mod>\n\n<Level>000</Level>\n\n\nto \n\n\n<PrereqProdCode>ci</PrereqProdCode>\n\n<PrereqVersion>\n\n<Version>06</Version>\n\n<Release>30</Release>\n\n<Mod>05</Mod>\n\n<Level>000</Level> \n\n \n\nThe same for other components in case they are also missing from your depot. \n\nThe dsc files are into <installation_media>/ITMfVE_Agents/unix folder. \n\nRepeat the tacmd addbundles command and it should now work fine. \n\nAs previously said, please consider that this scenario may occur also for agents different than N4, and the workaround is applicable also for them. \n\nOf course the target dsc file name changes accordingly to the agent type and related architecture. \n\n \n\n2) The above workaround can help in case the issue is only related to backleveled prerequisite packages. \n\nAnyway, 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.\nThe 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). \nThe quickest workaround in this case is to install the agent locally.\n\n3) 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. \nThe installer recognizes the target node as a 64bit platform and the agents are 32bit. \nSo the installer menu will show no available agents to be installed.\n\nYou need to proceed as follow:\n\na) Run the local installation of N4 agent on target machine and proceed as usual when you are prompted with Installer initial questions.\nb) Select Other operating systems when you are showed this panel\n\n[/support/docview.wss?uid=swg21983839&aid=1] [/support/docview.wss?uid=swg21983839&aid=1]\n\nc) Then select Linux Intel R2.6 R3.0 (32 bit)\n\n[/support/docview.wss?uid=swg21983839&aid=2] [/support/docview.wss?uid=swg21983839&aid=2]\n\nd) 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\n\n[/support/docview.wss?uid=swg21983839&aid=3] [/support/docview.wss?uid=swg21983839&aid=3]\n\n \n\nPRODUCT ALIAS/SYNONYM\n IBM Tivoli Monitoring for Virtual Environments V7.2.0.3"
}
] |
TRAIN_Q015 | 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 | false | [
{
"filename": "swg21998452.txt",
"text": "Title: 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\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n 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. \n\nCONTENT\nIBM 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. \n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation: \n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE"
}
] |
TRAIN_Q016 | 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. | false | [
{
"filename": "swg21469413.txt",
"text": "Title: IBM Guidelines for setting ulimits (WebSphere Application Server) - United States\n\nText:\nulimits; 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)\n\nPROBLEM(ABSTRACT)\n 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 \n\nSYMPTOM\nTuning ulimits correctly can overcome these errors: \n\n * Too Many Open Files \n * Could not lock User prefs. Unix Error Code 24. \n * Truncated Core Dumps / Heap Dumps\n\n\nRESOLVING THE PROBLEM\n \n\nIs 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.\n\n\n\n\nHow 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. \n\nHard limits are the maximum limit that can be configured. Any changes to these require root access. \n\n \n\nTemporary Settings (for current session) \n\n * \n * ulimit -[H|S]limit_name limit_value\n\n\nTemporary 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. \n\nThis 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. \n\nBy 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. \n\nNOTES: \n\nOn 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. \n\nFor Solaris, settings in the \"/etc/system\" configuration file also allow configuring of some kernel-wide limits. \n\n \n\nGlobal Settings \n\n[/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. \n\n \n\nThe 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. \n\n \n\nChanges 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. \n\n \n\nNOTES: \n\nOn 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. \n\nFor 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. \n\n \n\nSpecifics for each Operating System:\nThe most up-to-date information on the limits can be found in the man page for \"ulimit\".\n\n\n\nAIX \nGlobal settings are generally set in the file /etc/security/limits, although there may be different limit files for LPARs and WPARs. \n\n \n\nPlease 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.\n\n\n\nCommand Line limit_name * /etc/security/limits Description ulimit -c [value] core\ncore_hard Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) data\ndata_hard Data segment size of processes in kilobytes. ulimit -f [value] fsize\nfsize_hard File size limit in 512 byes blocks. ulimit -n [value] nofiles\nnofiles_hard Max number of open files and/or sockets per process. ulimit -m [value]\n(K bytes) rss\nrss_hard The memory size of the process in kilobytes. ulimit -r [value] threads\nthreads_hard Max number of threads per process. ulimit -s [value]\n(K bytes) stack\nstack_hard The stack segment size in kilobytes. ulimit -t [value]\n(seconds) cpu\ncpu_hard Max per process CPU time (in seconds). ulimit -u [value] nproc\nnproc_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 \n\n\nHP-UX \n\nThere 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). \n\nThere 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. \nPlease 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.\n\n\n\nCommand \"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]\n(seconds) Max per process CPU time (in seconds). * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\nLinux \nGlobal settings are set in the file /etc/security/limits.conf. \n\nThe format for setting each limit is as follows:\n<domain> <type> <item> <value> \n\n<domain> controls which users or groups will have these limits \n\n<type> is either the string \"soft\" or \"hard\" limits.\nThe hyphen \"-\" can also be used which represents both soft and hard limits \n\n<item> and <value> are shown in the table below. Most values can also use the string unlimited. \n\n \n\nPlease 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.\n\n\n\nCommand 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 \n\n\n\n\n\n\n\nSolaris \n\nThere 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). \n\nAlso depending on the shell used, the ulimit command is slightly different. See the man page for further information. \n\nYou can also set kernel wide settings for many of these ulimits in the /etc/system file. \nFor 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. \nPlease 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.\n\n\n\nCommand Line limit_name * \n(sh, ksh, bash) Command Line \n(csh) Description ulimit -c [value] ulimit coredumpsize [value]\n(K bytes) Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) ulimit datasize [value]\n(K bytes) Data segment size of processes in kilobytes. ulimit -f [value] ulimit filesize [value]\n(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]\n(K bytes) ulimit stacksize [value]\n(K bytes) The stack segment size in kilobytes. ulimit -t [value]\n(seconds) ulimit cputime [value]\n(seconds) Max per process CPU time (in seconds). ulimit -v [value]\n(K bytes) ulimit memorysize [value]\n(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. \n\n\n\n\nIf I am experiencing Too Many Open Files (Unix Error Code 24), can I increase the number of file descriptors? \nYes 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\". \n\nHowever, 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. \n\nFurther information can be found at this link: Too Many Open Files error message [http://www.ibm.com/support/docview.wss?uid=swg21067352] \n\n\nOn 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. \n\nIf 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:\n[root] # ulimit -n unlimited\nbash: ulimit: open files: cannot modify limit: Operation not permitted\n\n\n \n\n[/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. \n\n\n\n\nOn 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. \n\n* soft nproc 1024 \n\nThe 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. \n\n#* soft nproc 1024 \n \n\nI 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 \n\nThis 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: \n\n\"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.\"\n\nRELATED INFORMATION\n Domino for Linux (see step 2) [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21377724]\nAIX - 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]\nLinux - 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]"
}
] |
TRAIN_Q017 | 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) | false | [
{
"filename": "swg27019359.txt",
"text": "Title: IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States\n\nText:\nDSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION\n\nABSTRACT\n 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. \n\nCONTENT\n\n\n\nTAB NAVIGATION\n * AIX [http://www.ibm.com/support/docview.wss?uid=swg27019359]\n * i5/OS [http://www.ibm.com/support/docview.wss?uid=swg27019362]\n * Windows [http://www.ibm.com/support/docview.wss?uid=swg27019366]\n\nIBM AIX\n\n\n\n\nWebSphere Portal Server Version 6.1.0.5 and 6.1.5.2 (AIX) \n\nThis 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. \n\nEARLIER 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]). \n\nLATER 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]). \n\nUNLISTED 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]).\n\n\n\nOperating systems\nsupported 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) \n * 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) \n * 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)\n\n[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Operating systems\nsupported 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) \n * 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) \n * 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)\n\n[/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 \n * Disk space requirements: * Minimum 2.5 GB free disk space for installation for WebSphere Portal \n * Minimum 1.0 GB free disk space for installation for WebSphere Application Server \n * Minimum 4 GB total disk space recommended for installation \n \n \n * 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. \n * CD-ROM drive\n\n[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Application Servers\nThe 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 \n * 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\n \n \n\nRefer 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 \n * WebSphere Application Server XML feature pack 1.0.0.5 \n * 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] \n * 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/])\n\nJavaScript Library [/support/docview.wss?uid=swg27019359&aid=1] * Dojo V1.3.2 or 1.1.1\n\nTo 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\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[/support/docview.wss?uid=swg27019359&aid=1] * Derby V10.1 and 10.3 \n\n * 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 \n * 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) \n * 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) \n * 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)\n \n \n * 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) \n * WebSphere Information Integrator V8.2 FP4\n\n * 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) \n * Oracle 11gR2 V11.2.0.1 (including RAC) \n * Oracle 11gR1 V11.1.0.7 (including RAC)\n \n \n \n * Microsoft SQL Server (Microsoft product site) [http://www.microsoft.com] * Enterprise Edition 2008 SP1 [http://www.microsoft.com] \n * Enterprise Edition 2005 SP3\n \n \n\n[/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]) \n * DB2 Driver for JDBC and SQLJ 3.1 (type 2/4) \n * 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 \n * Derby embedded JDBC Driver \n * 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]) \n * 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])\n\n[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Web servers\n[/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) \n * 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 \n * 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/] \n * 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) \n * 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] \n * 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) \n * Sun Java System Web Server 7 Update 8 or 6.1 SP12 (Sun product site) [http://www.sun.com/products/] \n\n[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] Web browsers\n(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] \n * Firefox V3.6, 3.5, 3.0, 2.0, 1.5.0.7 (Firefox product site) [http://www.mozilla.org/] \n * Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/] \n 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]\n * Opera 9.52 and higher [http://www.ibm.com/support/docview.wss?uid=swg21320077](Opera product site) [http://www.opera.com/products/]\n 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]\n \n \n * \n * 6.1.5.2: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http://www.microsoft.com] \n PageBuilder, Mashup Integration and Wiki/Blogs in V6.1.5.2 are not supported or functional when using Microsoft Internet Explorer V6.0.#6f \n * Firefox V3.6, 3.5, 3.0 (Firefox product site) [http://www.mozilla.org/] \n * Apple Safari 3.2 and higher (Apple product site) [http://www.apple.com/safari/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http://www.apple.com/safari/]\n 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 \n * Opera 9.52 and higher (Opera product site) [http://www.opera.com/products/]\n 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\n \n \n\n[/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] [/support/docview.wss?uid=swg27019359&aid=1] LDAP servers\n[/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 \n * 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 \n * 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] \n * IBM z/OS.e Security Server 1.7 and 1.6 (IBM z/OS Security Server product site) \n * Novell eDirectory 8.8 or 8.7.3 (Novell eDirectory product site) [http://www.novell.com/products/edirectory/] \n * Sun Java System Directory Server 7, 6.3, 6.1, and 6 (Sun product site) [http://www.sun.com/products/] \n * Microsoft Active Directory 2008, including Lightweight Directory Server (AD LDS, previously referred to as \"Application Mode\" or ADAM) \n * Windows Active Directory 2000 and 2003 including Application Mode\n\n[/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. \n * IBM Lotus Domino Document Manager V7 and 6.5.1 \n * 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]\n\n[/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/] \n * 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]) \n * IBM Lotus Quickr V8.5, 8.1.1 (IBM Lotus product site) [http://www.ibm.com/developerworks] \n * 6.1.5.2: IBM Lotus FileNet P8 V4.5 (IBM Lotus product site) [http://www.ibm.com/developerworks] \n * 6.1.5.2: IBM Content Manager V8.4 (IBM Content Manager product site) [http://www.ibm.com/software/data/cm/cmgr/]\n\n[/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/]\n\n[/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. \n * 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 \n * Computer Associates SiteMinder V6.0\n\n[/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) \n * IBM Portlet Factory V6.1.5, 6.1\n\n[/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\n\n[/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] \n\nRelated information\n[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]\nWebSphere Portal Information Centers and more [http://www.ibm.com/developerworks/websphere/zones/portal/proddoc.html]\nSupport Statement [http://publib.boulder.ibm.com/infocenter/wpdoc/v6r1m0/topic/com.ibm.wp.ent.doc/overview/inst_req_supt.html] \n\nSee disclaimer. \n\nTop of page \n\nDisclaimer\nIBM 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. \n\nTop of page \n\n\n\n\nORIGINAL PUBLICATION DATE\n 2009/9/1"
}
] |
TRAIN_Q018 | 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 | false | [
{
"filename": "swg21611073.txt",
"text": "Title: IBM Deletion of virtual portal fails with transaction timeout - United States\n\nText:\nvirtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempt to delete virtual portal via Virtual Portal Manager portlet fails with error:\n\nEJPAH4000E: Failed to delete virtual portal \n\nAttempts to delete the virtual portal using the ConfigEngine task \"delete-virtual-portal\" may fail as well.\n\n\nCAUSE\nWith 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: \n\n * the total and/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may show the following: \n\nExample #1:\n\n[9/10/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.\n\n[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction\ncom.ibm.icm.ci.CDMTransactionException\nat com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)\nat com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)\nat com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n....\n\n[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n.... \n\nExample #2: \n\n[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.\n[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: \njava.net.SocketInputStream.socketRead0(Native Method)\njava.net.SocketInputStream.read(SocketInputStream.java:150)\njava.net.SocketInputStream.read(SocketInputStream.java:121)\ncom.ibm.db2.jcc.t4.x.b(x.java:208)\ncom.ibm.db2.jcc.t4.x.c(x.java:360)\ncom.ibm.db2.jcc.t4.x.c(x.java:473)\ncom.ibm.db2.jcc.t4.x.v(x.java:1241)\ncom.ibm.db2.jcc.t4.ab.a(ab.java:61)\ncom.ibm.db2.jcc.t4.p.a(p.java:50)\ncom.ibm.db2.jcc.t4.rb.b(rb.java:220)\ncom.ibm.db2.jcc.am.po.qc(po.java:3498)\ncom.ibm.db2.jcc.am.po.b(po.java:4461)\ncom.ibm.db2.jcc.am.po.ic(po.java:799)\ncom.ibm.db2.jcc.am.po.executeUpdate(po.java:777)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)\ncom.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)\ncom.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)\ncom.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)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)\ncom.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)\ncom.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)\ncom.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)\n....\n\n\nRESOLVING THE PROBLEM\n1. 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. \n\n2. 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: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example) \n\nNote: 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.\n\nRELATED INFORMATION\n#Transaction settings [http://pic.dhe.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.nd.doc/info/ae/ae/tjta_settlog.html]\nPI04872 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI04872]\nSetting Resource Environment Provider custom properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8]"
}
] |
TRAIN_Q019 | 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 | false | [
{
"filename": "swg22001418.txt",
"text": "Title: IBM FAQ for IBM SPSS Statistics Subscription - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n FAQ for IBM SPSS Statistics Subscription \n\nANSWER\nQ. How to I cancel the auto-renewal of my IBM SPSS Statistics Subscription? \nA. 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. \n\nQ. 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?\nA. 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]."
}
] |
TRAIN_Q020 | 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. | false | [
{
"filename": "swg24035040.txt",
"text": "Title: IBM Rational Host Access Transformation Services 9.0 - United States\n\nText:\nservice release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES\n\nABSTRACT\n IBM Rational Host Access Transformation Services 9.0 has been made generally available and contains fixes to version 9.0. \n\nDOWNLOAD DESCRIPTION\n \n\nTable of Contents Sections Description * What's new\n\nThis section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. * Impact assessment\n\nThis section provides information related to the impact of this release to allow you to assess how your environment may be affected. * Prerequisites\n\nThis section provides important information to review prior to the installation of this release. * Download package\n\nThis section provides the direct link to obtain the download package for installation in your environment. * Installation instructions\n\nThis section provides the installation instructions necessary to apply this release into your environment. * Known problems\n\nThis 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]\n\nClick 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]\n\nThe 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]\n\nClick 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\n 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.\n\nINSTALLATION INSTRUCTIONS\n 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.\n\nDOWNLOAD PACKAGE\n \n\nDownload 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?\n \n\nImpact 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\n Click the Fix List link in the table of contents above to review a list of the problems solved in this release.\n\nKNOWN SIDE EFFECTS\n The following defects were not resolved in this release. \n\nAPAR 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. \nFor 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]. \nCHANGE HISTORY\n 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]. \n\n \n\nBack to top\n\n\nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Resources [http://www.ibm.com/support/docview.wss?uid=swg27020747]- selected tab,\n\n\n\n\nIBM Rational Software Support Communities \n\n * 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.\n \n \n * 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/].\n \n \n * 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. \n\n\n\n\nHELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:\nBefore 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: \n\n * What software versions were you running when the problem occurred? \n * Do you have logs, traces, or messages that are related to the problem? \n * Can you reproduce the problem? If so, what steps do you take to reproduce it? \n * Is there a workaround for the problem? If so, be prepared to describe the workaround. \n\nIf 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]. \n\n \n\nFollow 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]\n\n\n\n\n Back to top \n\n [/support/docview.wss?uid=swg24035040&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24035040&aid=2]Problems (APARS) fixed\nIC87102, IC87488, IC87959, IC88940, IC88981, IC89933, IC91191, IC91370, IC91420, IC92195"
}
] |
TRAIN_Q021 | Help with Action required for Hypervisor Edition of IIB V9.0 and WMB V8.0 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? | - | true | [] |
TRAIN_Q022 | Why is an error seen while running run-svrssl-config?
Following error is seen while running run-svrssl-config ConfigEngine task:
action-run-pdjrte-config-zos-wp.ac.impl:
[validateHost] Validating hostname(s) in the following argument: tam001:7136:1,tam002:7136:2
[echo] Command to run is: java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ****** -appsvr_id myAppSvr -port 7223 -mode remote -policysvr
tam001:7135:1,tam002:7135:2 -authzsvr tam001:7136:1,tam002:7136:2 -cfg_file /opt/WebSphere/AppServer/tivoli/tam/PdPerm.properties -key_file /opt/WebSphere/AppServer/tivoli/tam/pdperm.ks
[java] Executing java with empty input string
[java] Exception in thread "main"
[java] [
[java] HPDMG0759W The user name already exists in the registry.
[java] ]
[java] at com.tivoli.pd.jutil.ob.a(ob.java:40)
[java] at com.tivoli.pd.jutil.ob.a(ob.java:66) | - | true | [] |
TRAIN_Q023 | Help with Action required for IIB H.E. V9 and 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-IDs:
CVE-2017-5715
CVE-2017-5753
CVE-2017-5754
Where can I find this information? | - | true | [] |
TRAIN_Q024 | 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. | false | [
{
"filename": "swg21592093.txt",
"text": "Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross 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"
}
] |
TRAIN_Q025 | We are experiencing issues after we cleared the /tmp/javasharedresources location and restarted the jvm.
We experienced an issue when we cleared the /tmp/javasharedresources location and restarted jvm. We found a behavior where our website is serving a blank page and also cache monitor is not reflecting the statistics.
Please help us to understand why we cannot clear the /tmp/javasharedresources ? | - | true | [] |
TRAIN_Q026 | 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 | false | [
{
"filename": "swg24039229.txt",
"text": "Title: IBM Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This is an Interim Fix for IBM Tivoli Monitoring for Virtual Environments: VMware VI 7.2 Fix Pack 2 reports \n\nDOWNLOAD DESCRIPTION\n(C) Copyright International Business Machines Corporation 2015. \n\n\n All rights reserved.\n\nComponent: IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI\nAgent TCR Reports, Version 7.2 Fix Pack 2\n\nComponent ID: 5724L92AG\n\nInterim Fix: 0001, 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001\n\nDate: January 23, 2015\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n\n1.0 General description\n-----------------------\n\nThis interim fix resolves the APARs and defects listed in the\n\"Problems Fixed\" section below. \n\n\n2.0 Problems fixed\n------------------\n\nThe following problems are addressed by this fix.\n\n2.1 APARs\n---------------\nNone.\n\n2.2 Defects\n-----------\nDefect: 210286\nAbstract: Update model for VM PARTITION\nAdditional information: For \"Free_Space\" and \"Used_Space\" attributes, the\ndefault aggregation is defined not as AVG but as SUM. It usually\nworks as expected but if there were two entries which have same\n\"Timestamp\", the \"VM_PARTITION\" attribute group's data is shown\nwith doubled values.\nDefect: 212729\nAbstract: Drill through feature is not working in VE 7.2 FP2 reports\nAdditional information: A few VMware VI reports are showing the following\nmessage, when we try drill through by clicking on report chart:\nRSV-CM-0005 Content Manager did not return an object for the\nrequested search path.\nDefect: 212776\nAbstract: Datacenter parameter/prompt is missing in a few VM reports\nAdditional information: The Datacenter parameter/prompt is missing in the\nfollowing VMware VI reports: VM Heat Chart, Bottom N VMs by\nResource Pool and Top N VMs By Resource Pool.\nDefect: 212851\nAbstract: Place Date range parameter after the Resource prompts\nAdditional information: A few VMware VI reports contain time selection over\nresource selection. Therefore to make uniformity across the reports,\nplace Date range parameter after the resource prompts (like Data\nCenter and Cluster).\nDefect: 212924\nAbstract: Unsorted resources e.g.Cluster on parameter selection page\nAdditional information: Most of the VMware VI reports sometimes display \nunsorted resources (viz. Data Center, Cluster, Host Servers, VMs\netc.) on parameter selection (aka prompt) page.\nDefect: 212925\nAbstract: Incorrect caption/label for Host Server resource parameter\nAdditional information: Incorrect caption/label for the resource parameter\ne.g. In Network usage by VMs report, the \"Host Server(s)\" drop\ndown list title needs to be corrected as \"Host Server\" as user\ncan select only one host in this report.\n\n2.3 Enhancements\n------------------\nFeature: 210245\nAbstract: Enhance model to add SAMPLES.\nAdditional information: Add SAMPLES query item/column for each summarized\nattribute group view (viz. Hourly, Daily, Weekly and Monthly)\nin existing VMware VI Agent reports data model.\nFeature: 213018\nAbstract: RFE 60331: Require a new report for Cluster Utilization Details\nAdditional information: Require a new cluster level report like the Host \nServer Utilization Details report, which is useful and included the\nactual data points from the graph at the bottom of the report.\nDefect: 213084\nAbstract: Provide a choice to select date range or start & end week\nAdditional information: Provide a parameter choice (aka date filter option)\nto either select date range or start and end week of the year in\nthe following VMware VI reports: Cluster Weekly Comparison and\nHost Servers Weekly Comparison.\n\n2.4 Superseded fixes\n---------------------\nNone.\n\n2.5 APARs and defects included from superseded fixes\n---------------------------------------------------------------\nNone.\n\n\n3.0 Architecture and prerequisites\n----------------------------------\n\nThis fix is supported on all operating systems listed in the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2. See chapter 9 for information on the Tivoli\nCommon Reporting.\n\nThe User's Guide is here:\n\nhttp://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]\n\nPlease refer to the IBM Software Product Compatability Reports (SPCR)\nfor the latest operating system certification information:\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html] \n\n3.1 Prerequisites for this fix\n------------------------------\n\nThe prerequisite level for this fix is defined in Chapter 9 of the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2.\n\n\n4.0 Image directory content\n---------------------------\n\nThis fix image contains the following files:\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.README - This README file\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip - Fix archive .zip format.\n\nThe fix archive file contains the following directories and files,\nwhich is the same as the format found in the reports directory\nof the IBM Tivoli Monitoring for Virtual Environments V7.2 Fix Pack 2\nDashboards, Capacity Planner and Reports (TMVE), Multilingual media \nas found on Passport Advantage:\n- gui\n- lib\n- model\n- reports\n- scripts\n- setup_aix.bin\n- setup_hpux.bin\n- setup_linux.bin\n- setup_solaris.bin\n- setup_windows.exe\n- silent_installer.properties\n- tcr_install.properties\n\nNote that this Interim Fix is a complete replacement of these\nfiles.\n\n5.0 Installation instructions\n-----------------------------\nThis fix can be installed over an existing installation or as\na new install. Expand the archive file, \n7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip, and copy the files in any\nlocation on the same computer where the Tivoli Common Reporting \nserver is installed.\n\nUse the following procedure to import reports that are bundled by using\nthe report installer:\n1. From the \\7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 directory on the product file, run the \ncommand appropriate for your operating system:\n• setup_aix.bin (for AIX)\n• setup_hpux.bin (for HP-UX)\n• setup_linux.bin (for Linux)\n• setup_solaris.bin (for Solaris)\n• setup_windows.exe (for Windows)\nThe installer window opens.\n2. Choose your language and click OK.\n3. On the Welcome page click Next.\n4. Specify the Tivoli Common Reporting installation directory, such as\n<JazzSM_Home>/reporting if you are using Tivoli Common Reporting 3.1 or\nlater with Jazz for Service Management and <TIP_Home>/TCRComponents if\nyou are using Tivoli Common Reporting 2.1.1 with Tivoli Integrated Portal.\nYou can use the default folder or use the Browse button to provide the\npath. Click Next.\n5. Choose the reports you want to install. Click Next.\n6. Enter the Tivoli Common Reporting user name and password. Click Next.\n7. For each data source and data script, enter the data source configuration \ninformation. Enter the following details for the selected cognos reports, and \nthen click Next:\n• In the Enter the database username field, enter the administrator user name.\n• In the Enter the user password field, enter the password.\n• In the Choose the database type list, select the database type.\n• In the Enter the database name field, enter the warehouse database name. For DB2\nor Oracle, enter the database name. For MS SQL, enter the ODBC Data Source Name.\n8. On the Data Script runDbScript Configuration page:\na. Click the JDBC User Credentials tab, and enter the Tivoli Data Warehouse database \nuser name and password to be used during the installation. Check the box to skip \ndefining the data source now.\nb. Click the JDBC Database Credentials tab, and select database type. Edit the JDBC URL, \nJDBC driver file names, and JDBC driver class for the selected database type and then \nclick Next.\n• For DB2 database, required driver files are db2jcc.jar and db2jcc_license_cu.jar \n(Note: JDBC credentials must have db2admin privileges.)\n• For Oracle database, required driver file is oraclethin.jar\n• For MS SQL Server database, required driver file is sqljdbc.jar\n9. On the Report Installer Summary page, verify the reports to be installed, click Install, \nand wait for the installer to finish.\n10. The post-installation report is displayed. Check if the installation was successfully \nfinished and click Done.\n\nResults:\nAgent reports are now installed on your Tivoli Common Reporting server.\n\nAlternatively, see Topic: Importing reports by using the report installer \nin Chapter 17 of the IBM Tivoli Monitoring Administrator's Guide, \nversion 6.3 Fix Pack 2 for install instructions.\n\nThe Administrator's Guide is here:\n\nhttp://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]\n\n\n6.0 Additional installation information\n---------------------------------------\nNone\n\n\n7.0 Known problems and workarounds\n----------------------------------\nNone\n\n\n8.0 Additional product information\n----------------------------------\nNone \n\n\n9.0 Copyright and trademark information\n---------------------------------- \nA current list of IBM trademarks is available on the Web at \"Copyright\nand trademark information\" at www.ibm.com/legal/copytrade.shtml.\n\n\n10.0 Notices\n-------\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION\n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,\nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\nSome jurisdictions do not allow disclaimer of express or implied\nwarranties in certain transactions, therefore, this statement may not\napply to you.\n\nThis information could include technical inaccuracies or typographical\nerrors. Changes are periodically made to the information herein; these\nchanges will be incorporated in new editions of the publication. IBM\nmay make improvements and/or changes in the product(s) and/or the\nprogram(s) described in this publication at any time without notice.\n\nMicrosoft, Windows, and Windows Server are trademarks of Microsoft\nCorporation in the United States, other countries, or both. \n\nJava and all Java-based trademarks and logos are trademarks or\nregistered trademarks of Oracle and/or its affiliates. \n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.\n\nThird-Party License Terms and Conditions, Notices and Information\n-----------------------------------------------------------------\nThe license agreement for this product refers you to this file for\ndetails concerning terms and conditions applicable to third party\nsoftware code included in this product, and for certain notices and\nother information IBM must provide to you under its license to\ncertain software code. The relevant terms and conditions, notices and\nother information are provided or referenced below. Please note that\nany non-English version of the licenses below is unofficial and is\nprovided to you for your convenience only. The English version of the\nlicenses below, provided as part of the English version of this file,\nis the official version.\n\nNotwithstanding the terms and conditions of any other agreement you\nmay have with IBM or any of its related or affiliated entities\n(collectively \"IBM\"), the third party software code identified below\nare \"Excluded Components\" and are subject to the following terms and\nconditions:\n\n- the Excluded Components are provided on an \"AS IS\" basis\n- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND\nCONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT\nNOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE\nAND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND\nFITNESS FOR A PARTICULAR PURPOSE\n- IBM will not be liable to you or indemnify you for any claims\nrelated to the Excluded Components\n- IBM will not be liable for any direct, indirect, incidental,\nspecial, exemplary, punitive or consequential damages with respect\nto the Excluded Components. \n\nPREREQUISITES\nIBM Tivoli Monitoring for Virtual Environments: VMware VI Agent, version 7.2 Fix Pack 2\n\nINSTALLATION INSTRUCTIONS\nPlease refer to the full README contained in the Download Description section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat 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] [ ]"
}
] |
TRAIN_Q027 | 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. | false | [
{
"filename": "swg21611699.txt",
"text": "Title: IBM JDBC driver or database insufficiencies cause administration portlets to fail. - United States\n\nText:\nRT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nYou 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.\n\nSYMPTOM\nSystemOut.log contains:\n... DefaultTransa E Message: Could not save object in repository., \nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\ncom.ibm.workplace.wcm.services.repository.RepositoryException: \nMessage: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\n...\nCaused by: com.ibm.icm.da.DBAccessException:\njava.sql.SQLFeatureNotSupportedException:DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream\nat com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857) \n\n \n\nThe client browser displays: \n\n\nEJPAS0017E ... Message: Could not save object in repository.,\nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a\nfunction createItems of PLS data ...\n\nor:\n\nEJPAE0015E: Failed to add new portlets.\n...\nEJPEC0002E: The transaction has been set to rollback state...\n\n\nCAUSE\nThe JDBC driver does not meet WebSphere Portal v8's prerequisites.\n\n\nDIAGNOSING THE PROBLEM\nCheck SystemOut.log for the database server version and JDBC driver version: \n\n\nDSRA8204I: Database product version : ...\nInternalGener I DSRA8205I: JDBC driver name : ...\nInternalGener I DSRA8206I: JDBC driver version : ...\n\nCompare these to WebSphere Portal v8's prerequisites. Refer to the WebSphere Portal V8.0 detailed system requirements link below.\n\n\nRESOLVING THE PROBLEM\nIf 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). \n\n \n\nIf 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: \n\n\nWAS Integrated Solutions Console > Environment > WebSphere Variables\nVMM_JDBC_CLASSPATH\nORACLE_JDBC_DRIVER_PATH\n\nThese are stored in: <profile>/config/cells/<cell name>/variables.xml\n\nOther 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\n\nRELATED INFORMATION\n WebSphere Portal V8.0 detailed system requirements [http://www-01.ibm.com/support/docview.wss?uid=swg27007791]"
}
] |
TRAIN_Q028 | 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) | false | [
{
"filename": "swg22011689.txt",
"text": "Title: IBM Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n 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. \n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2016-1000031 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: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.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/117957 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM WebSphere MQ File Transfer Edition v7.0.0 \n\nIBM WebSphere MQ File Transfer Edition v7.0.1 \n\nIBM WebSphere MQ File Transfer Edition v7.0.2 \n\nIBM WebSphere MQ File Transfer Edition v7.0.3 \n\nIBM WebSphere MQ File Transfer Edition v7.0.4\n\nREMEDIATION/FIXES\nAll affected product versions are already End of Support. Customers must contact IBM to obtain a fix for the affected release.\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 22 Dec 2017 Original Version \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q029 | 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 | false | [
{
"filename": "swg21964202.txt",
"text": "Title: IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States\n\nText:\ndwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2) \n\nSYMPTOM\nUnable to connect to TWS 8.5.1 ,8.6 or 9.1/9.2 from DWC 9.3. \n\nCheck the WAS SystemOut.log for error :\n\nSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3, \nbut 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.\n\n\nCAUSE\nDWC 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\n\n\nRESOLVING THE PROBLEM\nYou can solve this problem by configuring your TWS engines to use TLS instead of SSL :\n\n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/config/cells/TWSNodeCell/security.xml \n\nFind sslProtocol and change \"SSL_TLS\" to \"TLS\" \n\nFind ssl.protocol and change value=\"SSL\" to value=\"TLS\" \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/properties/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nBackup and edit : \n\nTWA_HOME/WAS/TWSProfile/temp/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nStop and restart WAS. \n\n*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 : \n\nTWA_HOME/JazzSM/profile/config/cells/JazzSMNode01Cell/security.xml \n\nTWA_HOME/JazzSM/profile/properties/ssl.client.props \n\nTWA_HOME/JazzSM/profile/temp/ssl.client.props \n\nPlease consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted. \n\nSee technote 1689332."
}
] |
TRAIN_Q030 | 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. | false | [
{
"filename": "swg21406783.txt",
"text": "Title: 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\n\nText:\nDatapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n 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.\n\n\n \n\nCross 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"
}
] |
TRAIN_Q031 | 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". | false | [
{
"filename": "swg21318593.txt",
"text": "Title: IBM Handling 302 redirect error message in a Web Application Firewall - United States\n\nText:\nHTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:\n\nRedirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) \n\nSYMPTOM\nThis technote pertains to the following errors. \n\nExample 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.\n\nweb-application-firewall (CookieEncrypt): Backside header failed to \nparse due to: Failed to establish a backside connection \n12:20:53 webapp-firewall warn 60452 10.176.3.97 HTTP Redirect from \n'http://10.176.3.97:8080/cgi-bin/WebObjects.exe/IndvGate.woa/5/wo/2jHo28 \nQYOlhC2RZ1XQ15DE5OKo8/0.1.2.27.3.SecureSignOn.1' failed due to non \nidempotent request method. (RFC 2616 sec 10.3)\n\nExample 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.\n\nWed May 21 2008 10:39:11 [mpgw][info] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP response code 302 for \n'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' \nWed May 21 2008 10:39:11 [mpgw][warn] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP Redirect from \n'http://9.65.237.170:8080/forum/ucplogin.php?mode=login' failed due to\nnon idempotent request method - RFC 2616 sec 10.3. \nWed May 21 2008 10:39:11 [mpgw][error] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: Backside header failed to parse due to: \nFailed to establish a backside connection\n\n\nCAUSE\n302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.\n\nThis is caused by the adherence to the HTTP RFC 2616 by the Datapower Appliance. \nFor additional information on the RFC you may see this page RFC2616 [http://www.w3.org/Protocols/rfc2616/rfc2616.html]\n\n\nENVIRONMENT\nWebSphere DataPower XI50 and XS40\n\n\n\nDIAGNOSING THE PROBLEM\nBackside header failed to parse due to: Failed to establish a backside connection failed due to non idempotent request method. (RFC 2616 sec 10.3)\n\n\n\nRESOLVING THE PROBLEM\nTo 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.\n\nsampleForRedirects.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]\n\n\n\nCross 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"
}
] |
TRAIN_Q032 | WCM User can not access authorized content with this exception in SystemOut.log: com.ibm.icm.jcr.access.AccessDeniedException
WCM User can not access authorized content with this exception in SystemOut.log: com.ibm.icm.jcr.access.AccessDeniedException | - | true | [] |
TRAIN_Q033 | 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. | false | [
{
"filename": "swg21591076.txt",
"text": "Title: IBM Automatically renew trusted credential - United States\n\nText:\nsecurity; trusted credentials SSO renew TECHNOTE (FAQ)\n\nQUESTION\n How do I choose the value to use for the Security > Authentication > Automatically renew trusted credential setting? \n\nANSWER\nFor 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.\nThe credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration.\n\n\n * 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.\n \n * Off: Credentials are not updated in any namespace.\n \n * 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.\n\n\nA user's trusted credentials for a namespace will only be renewed once per day. \n\nIt 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: \n\n\"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\n Proven Practices: Securing the IBM Cognos 10 BI Environ [http://www.ibm.com/developerworks/data/library/cognos/security/cognos_bi_platform/page602.html]\nCognos Analytics 11 Equivalent Technote [http://www-01.ibm.com/support/docview.wss?uid=swg21998776]"
}
] |
TRAIN_Q034 | 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 | false | [
{
"filename": "swg24043575.txt",
"text": "Title: IBM Tivoli Network Manager IP Edition 4.2.0 Fix Pack 3, 4.2.0-TIV-ITNMIP-FP0003 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n 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. \n\nDOWNLOAD DESCRIPTION\nWHAT'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]\n\n\nhttp://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\n\nSummary of the Enhancements included in this Fix Pack:\nThe following features and functions are introduced in Fix Pack 3.\n\nSupport for SLES 12.0 \n\n * \n\n\nSupport for DB2 version 11.1 * \n\n\nSupport for IBM zLinux Systems * \n * Red Hat Enterprise zLinux Server 7.3 (s390x, 64 bit) SuSE zLinux Enterprise Server (SLES) 12.0 SP1(s390x,64 bit) \n * \n * \n * \n * \n * https://www.ibm.com/software/passportadvantage/pao_customer.html\n * \n\n\nOffline geographical maps * \n\n\nCustom geographical map layers * \n\n\nRegional aggregation for geographical maps * \n\n\nBefore installing or upgrading Network Manager, refer to the Fix Pack Release notes: \nhttp://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] \n\n\n===================================================================== \nSummary of fixes in V4.2.0 Fix Pack 3 \n===================================================================== \nFor 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. \n\n\nIV89573 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 \n\n\n\nKnown problems with V4.2.0 Fix Pack 3 \nhttp://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\nPrerequisites and Installation Instructions \n\nSee 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]\n\nINSTALLATION INSTRUCTIONS\nIBM TIVOLI NETWORK MANAGER IP EDITION V4.2.0 FIX PACK 3\n=======================================================\n\nBuild 4.2.0.34\nThis document describes the known problems and APAR fixes for Network Manager V4.2.0 Fix Pack 3.\n\nCopyright IBM Corporation 2017\n\n\n1 WHAT'S NEW\nSee 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]\n\n2 INSTALLATION\nSee 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]\n\n3 POSTINSTALLATION AND CONFIGURATION\nSee 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]\n\n4 KNOWN PROBLEMS AND LIMITATIONS\nSee 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]\n\n5 SUMMARY OF APAR FIXES IN NETWORK MANAGER V4.2.0 FIX PACK 3\nSee 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]\n\nURL 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 \nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat 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] [ ]"
}
] |
TRAIN_Q035 | DataPower remote log targets, tracking efficieny
How can I track the efficiency of my log target (remote endpoint)? | - | true | [] |
TRAIN_Q036 | Why are not seeing data for our APMV8 AIX OS agent on AIX 7.1.x?
We are not seeing any data for our APMV8 AIX OS agent in the APM/UI. | - | true | [] |
TRAIN_Q037 | 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. | false | [
{
"filename": "swg21576245.txt",
"text": "Title: IBM Tivoli Integrated portal enabling multiple logins using same user Id - United States\n\nText:\nTIPL2SEC tivoli integrated portal multiple logins TECHNOTE (FAQ)\n\nQUESTION\n How can I login to TIP from different machines using same user Id? \n\nCAUSE\nNeed to login with multiple times with same user\n\nANSWER\nOnly TIP version 2.1 and higher support multiple logins using same user Id. \n\nFollow below steps to configure Tivoli Integrated Portal to allow multiple users to log in using the same user Id and password. \n\n1. Log in as an administrative user. \n\n2. Navigate to: \n\ntip_home_dir/profiles/TIPProfile/config/cells/TIPCell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF/ \n\n3. Edit consoleProperties.xml. \n\n4. Locate the property with a id attribute of ENABLE.CONCURRENT.LOGIN and set its value to true. \n\n5. Save the file and exit from the text editor. \n\n6. Restart TIP server."
}
] |
TRAIN_Q038 | 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. | false | [
{
"filename": "swg21341204.txt",
"text": "Title: IBM How to Rollback From a Fix Pack or Interim Fix to an Earlier Build - United States\n\nText:\nuninstall; revert; downgrade; hotsite; HS; out; fixpack TECHNOTE (FAQ)\n\nQUESTION\n 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. \n\nANSWER\nAssuming 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.\nNote 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.\n\nCare 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.\n\nSteps: \n\n\n\n 1. Stop the Cognos service and ensure that Cognos Configuration is not running. \n 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.\n 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.\n 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:\n 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. \n 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. \n 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. \n For versions 10.2.1 FP1 and above: This is stored in the <cognos_install>/bkp directory \n 5. Go into the folders and check the cmplst.txt file and check for the correct version to revert to. \n 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. \n 7. Start the Cognos service.\n\n \n\nHISTORICAL NUMBER\n 1028034"
}
] |
TRAIN_Q039 | 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. | false | [
{
"filename": "swg21660890.txt",
"text": "Title: IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n \"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?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe 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) \n\nSee 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. \n\n\"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 \n\nIf 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. \nANSWER\nWhy Use Compressed References? \n\nBelow 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. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert 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.\n\n\n\n * [/support/docview.wss?uid=swg21660890&aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase \n\nStarting 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]). \n\n\n\nNOTE: 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 \nassociated 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). \nSee 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. \n\n * \n * \n * \n * \n * \n * \n * This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.\n\n\nIncrease Maximum Heap Size to Force Heap Allocation Above the 4GB mark \n\nAnother 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) . \n\n \n\nFurther Investigation \n\nIf 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].\n\nReserving Low-Memory Space with -Xmcrs\n\nIf 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.\n\nThe 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.\n\nStarting 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.\n\nTo 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.\n\n\n * -Xmcrs<reasonable_value_for_lower_memory>\n\n * \n * NATIVEMEMINFO subcomponent dump routine\n * \n * \n * \n * \n * \n * \n * \n * \n * [/support/docview.wss?uid=swg21660890&aid=2]\n * \n\n\nDisabling 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.\n\nAdditionally, 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].\n\nBefore 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.\n\n\nMemory Map Considerations \n\nThe 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: \n\n\n\n[/support/docview.wss?uid=swg21660890&aid=3] \n\nNo Compressed References Overhead using -Xnocompressedrefs \nor\n-Xmx > 25GB -increased memory footprint\n-fewer/larger objects stored on heap leads to more frequent GC\n-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 \n\n\nGetting Assistance From IBM Support \nIf 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]: \n * \n * \n * \n\n\nThen 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. \nRELATED INFORMATION\n Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]\nAIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]\nIntroducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]\nCompressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]\nIBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms]"
}
] |
TRAIN_Q040 | 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. | false | [
{
"filename": "swg21628092.txt",
"text": "Title: IBM Installation Manager does not work if symbolic links are used for Installation Manager of installed product locations - United States\n\nText:\nRN1.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)\n\nPROBLEM(ABSTRACT)\n 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. \n\nCAUSE\nWhen 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.\nSimilarly, 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. \n\nIf 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.\n\n\nRESOLVING THE PROBLEM\nWhen 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. \n\n\nIf 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."
}
] |
TRAIN_Q041 | 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) | false | [
{
"filename": "swg22005055.txt",
"text": "Title: IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-5461 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5461]\nDESCRIPTION: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.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/125002 [https://exchange.xforce.ibmcloud.com/vulnerabilities/125002]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance 8.0 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.6\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nContinuous delivery updates between 9.0.1 and 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ Appliance 8.0 \n\nApply 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]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply 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]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 24 Aug 2017 Updated to include IBM MQ Appliance 9.0.x CD release\n14 Jul 2017 Original version published \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q042 | 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"). | false | [
{
"filename": "swg21664629.txt",
"text": "Title: IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States\n\nText:\nEJQAB0067E; WSP0005E; LoginException; policy; theme; attribute; JCR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPolicy (EJQAB0067E) and JCR Login (WSP0005E) exceptions occur in the System* logs when accessing Portal pages after user authentication.\n\nSYMPTOM\nSystemOut.log shows:\n\n[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. \n[datestamp] 00000241 PolicyManager E com.ibm.wps.policy.services.PolicyManagerServerSideImpl getPVSByPath throwing exception. PVS type not found for theme/SingleTopNav\n\nSystemErr.log shows:\n\n[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.\n....\n[datestamp] 00000241 SystemErr R Caused by: com.ibm.icm.da.DBAccessException: User id can not be null\n[datestamp] 00000241 SystemErr R at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:177)\n\n\nCAUSE\nAuthenticated 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.\n\nDIAGNOSING THE PROBLEM\nCollect the following: \n\n * 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:\n \n *=info:com.ibm.wps.policy.services.*=finest:com.ibm.wps.policy.commands.*=finest\n \n Then look for the following line in trace.log: com.ibm.wps.policy.services.PolicyService PolicyService() ENTRY userid contructor: {DN of user} \n \n \n * Resources.xml - can be found under * <wp_profile>/config/cells/<cellname>/clusters/<clustername>/ for cluster \n * <wp_profile>/config/cells/<cellname>/nodes/<nodename>/servers/<portalservername>/ for standalone\n \n \n\nLocate 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. \nRESOLVING THE PROBLEM\nCreate/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\").\n\nRELATED INFORMATION\n#Puma Store Service [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Puma_Store_Service_wp8]\nSetting service configuration properties [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Setting_service_configuration_properties_wp8?OpenDocument&sa=true]"
}
] |
TRAIN_Q043 | 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. | false | [
{
"filename": "swg21657023.txt",
"text": "Title: IBM Pdcollect tool for ITM IBM i OS agent - United States\n\nText:\nITM_TEMA_DIST_CONFIGURATION ITM_i5_Agent 5724C04 A4 OS/400 i5/OS IBMi IBM i pdcollect TECHNOTE (FAQ)\n\nQUESTION\n How do I collect logs and files for the IBM i OS agent? \n\nANSWER\nThe 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. \n\nPdcollect 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: \n\n\n/QIBM/ProdData/IBM/ITM/bin/pdcollect.sh\n\n\nPdcollect 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. \n\n pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=2]pdcollect_ibmi_1.4.zip [/support/docview.wss?uid=swg21657023&aid=1] \n\n The tool is executed by issuing the following shell script command in Qshell:\n\n<directory>/pdcollect.sh \n\nwhere <directory> is the IFS directory where the tool is stored. \n\nYou must execute pdcollect while running under a user profile that you use to run IBM Tivoli Monitoring to avoid problems with object authorities. \n\nThe 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: \n\n /tmp/ITM/pdcollect_ibmi.tar.Z \n\nThe 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. \n\nInstructions to view the data that has been collected is displayed in a message at the end of pdcollect processing. \n\nThe 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."
}
] |
TRAIN_Q044 | 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. | false | [
{
"filename": "swg21592093.txt",
"text": "Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http://www.hearne.software/Software/SPSS-Grad-Packs-for-Students-by-IBM/FAQ] \n * On the Hub [http://onthehub.com/] \n * StudentDiscounts.com [http://studentdiscounts.com/contact-us.aspx] \n * JourneyEd [https://www.journeyed.com/contact] \n * thinkEDU [https://thinkedu.desk.com/] \n * Studica [http://www.studica.com/technical-support]\n\n\n\n\n\nCross 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"
}
] |
TRAIN_Q045 | 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. | false | [
{
"filename": "swg21598974.txt",
"text": "Title: IBM Insufficient Access Error adding documents to FileNet Content Engine - United States\n\nText:\nFNRCE0001E; E_ACCESS_DENIED; unable to add document TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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.\n\n\nSecurity Error seen: The requester has insufficient access rights to perform the requested operation. \n\nCAUSE\nUser does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents.\n\nDIAGNOSING THE PROBLEM\n\n\n\n * User has necessary rights to the document class, folders and object store but can't add document. \n * User does not have necessary Create_Instance rights on the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n * Error seen in the P8_server_error.log:\n \n 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.\n com.filenet.api.exception.EngineRuntimeException: FNRCE0001E: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation. failedBatchItem=0 errorStack={\n \n\nRESOLVING THE PROBLEM\nSteps to resolve issue: \n\n 1. Log in to FileNet Enterprise Manager. \n 2. Grant the user CREATE_INSTANCE rights to the Security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n 3. Re-try adding the document."
}
] |
TRAIN_Q046 | 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. | false | [
{
"filename": "swg21695194.txt",
"text": "Title: IBM IV67523 Move local data from CANDLEHOME to another file system - United States\n\nText:\n6.30.05.00 CANDLEHOME CANDLEDATA itmCANDLEDATA.sh TECHNOTE (FAQ)\n\nQUESTION\n How do I move local data such as configuration files, log files, historical data, etc. from CANDLEHOME to a different file system? \n\nCAUSE\nSince 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.\n\nANSWER\nIntroduction \n\nUnder 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. \n\nThe CANDLEDATA mechanism is available with ITM 6.30.05.00. \n\n \n\n\n\n\n\n\nHow CANDLEDATA Works \n\nThe 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. \n\nThe 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. \n\n \n\nBase Directory Links \n\nThe following local data directories are always linked from CANDLEHOME to CANDLEDATA:\n\n\n * /opt/IBM/ITM/InstallITM -> /var/IBM/ITM/InstallITM\n * \n * /opt/IBM/ITM/config -> /var/IBM/ITM/config\n * \n * /opt/IBM/ITM/kt1v3depot -> /var/IBM/ITM/kt1v3depot\n * \n * /opt/IBM/ITM/localconfig -> /var/IBM/ITM/localconfig\n * \n * /opt/IBM/ITM/logs -> /var/IBM/ITM/logs\n * \n * /opt/IBM/ITM/patchlogs -> /var/IBM/ITM/patchlogs\n * \n * /opt/IBM/ITM/tables -> /var/IBM/ITM/tables\n * \n * /opt/IBM/ITM/tmaitm6/agentdepot -> /var/IBM/ITM/tmaitm6/agentdepot\n * \n * /opt/IBM/ITM/tmp -> /var/IBM/ITM/tmp\n\nThese directories and links are automatically generated by ITM when the system is installed or converted to use CANDLEDATA. \n\n \n\nGeneral Agent Directory Links \n\nIn addition to the base set of directory links, most agents have general links for TEMA data:\n\n\n * /opt/IBM/ITM/ATTRLIB -> /var/IBM/ITM/ATTRLIB\n * \n * /opt/IBM/ITM/<platform>/<pc>/tables/ATTRLIB -> /var/IBM/ITM/ATTRLIB/<pc>\n * \n * /opt/IBM/ITM/EIFLIB -> /var/IBM/ITM/EIFLIB\n * \n * /opt/IBM/ITM/<platform>/<pc>/tables/EIFLIB -> /var/IBM/ITM/EIFLIB/<pc>\n * \n * /opt/IBM/ITM/hist -> /var/IBM/ITM/hist\n * \n * /opt/IBM/ITM/<platform>/<pc>/hist -> /var/IBM/ITM/hist/<pc>\n * \n * /opt/IBM/ITM/psit -> /var/IBM/ITM/psit\n * \n * /opt/IBM/ITM/<platform>/<pc>/psit -> /var/IBM/ITM/psit/<pc>\n\n\nThese directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA. \n\nSpecial Agent Directory Links \n\nSome 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:\n\n\n * /opt/IBM/ITM/kca -> /var/IBM/ITM/kca\n\n\nThese directories and links are automatically generated by ITM when the agent is converted to use CANDLEDATA. \n\nCANDLEDATA <-> CANDLEHOME Directory Links \n\nThe CANDLEHOME and CANDLEDATA directories also have cross references to each other:\n\n\n * /opt/IBM/IBM/registry/CANDLEDATA -> /var/IBM/ITM\n * \n * /opt/IBM/ITM <- /var/IBM/ITM/CANDLEHOME\n\n\nThese links are all automatically generated by ITM when the system is installed or converted to use CANDLEDATA. \n\nConfiguration Variables exploited by CANDLEDATA \n\nIn 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:\n\n\n * CTIRA_SIT_PATH\n * \n * CANDLEHOME/\n * <platform>/<pc>/psit\n * \n * \n * KCA_IP_DIR\n * \n * CANDLEHOME/kca\n * \n * \n * KCAWD_WRITE_DIR \n * \n * CANDLEHOME/kca\n * \n * \n\nNotes: 1. While the variables point to CANDLEHOME/xxx, the directory links cause the local data to be written to the corresponding CANDLEDATA/xxx. \n 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.\n\n\nConfiguration Variables affected by CANDLEDATA\nThe 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:\n. \n\n * ATTRLIB\n * \n * CTIRA_HIST_DIR\n * \n * EIFLIB\n * \n * \n\nWhen 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: \n. * CTIRA_SIT_FILE\n * \n * \n\nBy 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: \n. * CTIRA_THRESHOLDS \n * \n * IRA_EVENT_EXPORT_SNMP_TRAP_CONFIG\n * \n * \n * IRA_LOCALCONFIG_DIR\n * \n * \n * IRA_PRIVATE_SITUATION_CONFIG\n * \n * \n * IRA_SERVICE_INTERFACE_DEFAULT_PAGE\n * \n * \n * IRA_SERVICE_INTERFACE_DIR\n * \n * \n * KXX_FCP_SCRIPT_DEFINITIONS \n\n\n\n\n\nKnown Restrictions\n\n\n 1. The CANDLEDATA mechanism is available only for ITM on Linux and UNIX. ITM on Windows continues to keep local data under CANDLEHOME. \n . \n 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.\n . \n 3. No facility is provided to move CANDLEDATA from one directory to another. To do this, you must uninstall and reinstall ITM.\n . \n 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. \n * A given CANDLEHOME can only use one CANDLEDATA. This means components cannot be split amongst multiple CANDLEDATAs.\n .\n \n \n 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. \n * 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. \n * ITM does not allow the monitoring server to start if CANDLEDATA is implemented. \n * ITM does not allow the portal server to start if CANDLEDATA is implemented.\n .\n \n \n 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.\n . \n 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.\n . \n 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. \n \n 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. \n . \n 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. \n * 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. \n * 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.\n .\n \n \n 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. \n * Results are somewhat inflated for CANDLEHOME.\n .\n \n \n 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. \n\n\n\n\n\n\n\nAgents Verified with CANDLEDATA\n\nThe following agents have been verified to run properly when CANDLEDATA is implemented:\n\n\n * LO\n * \n * \n * LZ\n * \n * \n * UD\n * \n * \n * UX\n * \n * \n\nFor other agents, contact the corresponding support team. \n\n\n\n\n\n\nSetting Up a New Local Installation with CANDLEDATA\n\nFor new installations, you can define the location for local data at installation time.\n\nLocal install (interactive):\n\n\n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * \n * \n * # ./install.sh\n * \n * INSTALL\n * \n * \n * Enter the name of the IBM Tivoli Monitoring installation directory.\n * \n * [ default = /opt/IBM/ITM ]:\n * \n * \"/opt/IBM/ITM\" does not exist\n * \n * Try to create it [ 1-yes, 2-no; \"1\" is default ]?\n * \n * Creating directory \"/opt/IBM/ITM\"...\n * \n * \n * Enter the name of the IBM Tivoli Monitoring local data directory.\n * \n * [ default = /opt/IBM/ITM ]: /var/IBM/ITM\n * \n * \"/var/IBM/ITM\" does not exist\n * \n * Try to create it [ 1-yes, 2-no; \"1\" is default ]?\n * \n * Creating directory \"/var/IBM/ITM\"...\n * \n * itmCANDLEDATA.sh: Installation directory \"/opt/IBM/ITM\" successfully converted to use data directory \"/var/IBM/ITM\".\n * \n * \n * \n * CANDLEDATA\n * \n * \n * \n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEHOME\n * \n\n\nLocal install (silent): \n * \n * CANDLEDATA\n * \n * CANDLEDATA\n * \n * \n * \n * install.sh \n [-l \n * CANDLEDATA\n * ] \n * \n Where: * -l\n * \n * CANDLEHOME\n * \n \n \n * \n * \n * CANDLEDATA\n * \n * install.sh\n * \n * \n * \n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * install.sh\n * \n\n\n\n\n\n\n\nStarting an agent for the first time with CANDLEDATA \n\nWhen 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:\n\n# itmcmd agent start ux\nProcessing. Please wait...\nitmCANDLEDATA.sh: Component ux successfully converted to use data directory \"/var/IBM/ITM\".\nStarting Monitoring Agent for UNIX OS ...\nMonitoring Agent for UNIX OS started \n\n \n\n\n\n\n\n\nConverting an existing installation or new agents to use CANDLEDATA \n\nFor 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. \n\nitmCANDLEDATA.sh\n[-b yes|no] \n[-h CANDLEHOME] \n[-l CANDLEDATA] \n[-f no|yes] \n[-p PC|*]\n[-r no|yes] \n\nWhere: \n\n * \n * -b\n * \n * yes\n * \n * CANDLEDATA\n * \n * CANDLEHOME\n * \n * CANDLEHOME\n * \n * no\n * \n * CANDLEDATA\n * \n * \n * \n * -h\n * \n * \n * \n * -l\n * \n * CANDLEHOME\n * \n * CANDLEDATA\n * \n * \n * \n * -f\n * \n * no\n * \n * yes\n * \n * \n * \n * -p\n * \n * *\n * \n * \n * \n * -r\n * \n * no\n * \n * yes\n * \n\n\nIf 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. \n\nExample 1: Conversion of a typical CANDLEHOME can be performed with an incantation similar to this: * \n * itmCANDLEDATA.sh -l /var/IBM/ITM -b yes -p \"*\" -r yes\n\n\nExample 2: Conversion of a newly installed agent to a CANDLEHOME where CANDLEDATA is already implemented can be performed with an incantation similar to this: * \n * itmCANDLEDATA.sh -b no -p \"ux\" -r yes\n\n\n\n\n\n\n\nUsing CANDLEDATA with Remote Deploy\n\nYou can define the location for local data remotely:\n\ntacmd createnode (new installations):\n\n\n * \n * CANDLEDATA\n * \n * CANDLEDATA\n * \n * \n * \n * tacmd createnode ... -o ENV_CANDLEDATA=\n * data_directory\n * ...\n * \n * \n * \n * install.sh\n * \n * CANDLEDATA\n * \n * \n\ntacmd executecommand + itmCANDLEDATA.sh (existing installations): \n * \n * CANDLEDATA\n * \n * tacmd updateagent\n * \n * CANDLEDATA\n * \n * tacmd executecommand\n * \n * \n * \n * tacmd executecommand ... -c \"/opt/IBM/ITM/bin/itmCANDLEDATA.sh -l /var/IBM/ITM -p \\\"*\\\" -b yes -r yes > /tmp/itmCANDLEDATA_remote.log 2>&1 &\"\n * \n * \n * \n * \n * 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. \n\n\n\n\n\n\nOther Implications \n\nThe following general ITM utilities have been updated to run properly when CANDLEDATA is implemented: \n\n * cinfo - The output heading indicates the location of CANDLEDATA if it implemented. \n * itmcmd agent start - Agent configurations are automatically updated if CANDLEDATA is implemented. Also, the portal server is prevented from starting if CANDLEDATA is implemented. \n * itmcmd server start - The monitoring server is prevented from starting if CANDLEDATA is implemented. \n * 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. \n * tacmd pdcollect and pdcollect - Data is gathered from CANDLEDATA just as from CANDLEHOME. \n * 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."
}
] |
TRAIN_Q047 | 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) | false | [
{
"filename": "swg21998655.txt",
"text": "Title: IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n 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. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-9693 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION: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.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119517 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5\n- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2\n- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3\n- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12\n\nREMEDIATION/FIXES\nInstall IBM BPM or WLE interim fix JR57149 [http://www-01.ibm.com/support/docview.wss?uid=swg1JR57149]as appropriate for your current version. \n\n\n * 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] \n * 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] \n * 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] \n * 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]\n\n\nAs 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. \n\nFor WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5 \n\n * 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] \n\nFor 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]\n\n\nFor 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]\n\n\nFor 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]\n\n\nFor IBM BPM V8.5.5.0 * Apply iFix JR57149 [https://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor 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]\n\n\nFor 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]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n 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. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Nalla Muthu S and Prasath K \n\nCHANGE HISTORY\n 24 Feb 2017: initial version published \n\n*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. \n\nDISCLAIMER\nAccording 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.\n\n \n\n\nCross 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"
}
] |
TRAIN_Q048 | 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 | false | [
{
"filename": "swg21696083.txt",
"text": "Title: IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States\n\nText:\nACCE; CE; Property; FEM TECHNOTE (FAQ)\n\nQUESTION\n With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class\n\n1. Launch FEM\n2. Expand the object store and document class tree. Right click on the document class and select \"Properties\"\n3. Go to \"Properties Definitions\" tab, highlight the property definition and click \"Edit\"\n4. Make the modification and click OK\n5. Click OK again to save the change\n\nHow to perform the same operation with FileNet Content Engine - ACCE? \n\nANSWER\nFollow the below steps to update the property definition properties on ACCE: \n\n\n\n\n 1. Launch ACCE \n 2. Expand the object stores folder and click the object store to open the Object store tab \n 3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab \n 4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify \n 5. ACCE will open that property definition in a new Properties tab \n 6. Modify the property definition as required \n 7. Go back to the Class Definition tab and click Save"
}
] |
TRAIN_Q049 | 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. | false | [
{
"filename": "swg22012345.txt",
"text": "Title: IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential privilege escalation in WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1731 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1731]\nDESCRIPTION: 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.\nCVSS Base Score: 8.8\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/134912 [https://exchange.xforce.ibmcloud.com/vulnerabilities/134912] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION/FIXES\n The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI89498 for each named product as soon as practical.\n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition: \n\nFor V9.0.0.0 through 9.0.0.6: \n· 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]\n--OR-- \n· Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.13: \n· 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]\n--OR-- \n· Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018). \n\nFor V8.0.0.0 through 8.0.0.14: \n· 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] \n--OR-- \n· Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n· 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]\n--OR-- \n· Apply Fix Pack 7.0.0.45 or later. \n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n 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. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 29 January 2018: original document published \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q050 | 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. | false | [
{
"filename": "swg21974566.txt",
"text": "Title: IBM Configuring access for HTTP and HTTPS in Jazz for Service Management - United States\n\nText:\njazzsm11relnotes; jazzsm1101relnotes; jazzsm1102; jazzsm1103relnotes; relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; HTTP; HTTPS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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. \n\nCAUSE\nFor security reasons, HTTP access is disabled by default and is not supported. \n\nRESOLVING THE PROBLEM\nBefore you begin\n\n\nAfter 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. \n\nAbout this task \n\nConfiguring 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. \n\nImportant: These steps are provided for information purposes only, as setting up the environment for HTTP access is not supported. \n\nProcedure \n\n1. Change to the following directory:JazzSM_WAS_Profile/config/cells/JazzSMNode01Cell/applications. \n\n2. From this location, locate theweb.xmlfiles in the following directories: \n\n * For the Integrated Solutions Console web application archive:isc.ear/deployments/isc/isclite.war/WEB-INF \n * For the Charts web application archive:isc.ear/deployments/isc/TIPChartPortlet.war/WEB-INF \n * For the Dashboard Application Services Hub Change Password web application archive:isc.ear/deployments/isc/TIPChangePasswd.war/WEB-INF\n\n\n3. 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. \n\n5. Change the setting toNONEto enable both HTTP and HTTPS requests. The element now reads:<transport-guarantee>NONE</transport-guarantee>. \n\n6. Save the file, and then repeat these steps for the otherweb.xmldeployment files. \n\n7. 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] \n\nExample \n\nThe following example is a section of theweb.xmlfile forTIPChangePasswdwhere the transport-guarantee parameter is set toNONE:\n<security-constraint>\n<display-name>\nChangePasswdControllerServletConstraint</display-name>\n<web-resource-collection>\n<web-resource-name>ChangePasswdControllerServlet</web-resource-name>\n<url-pattern>/*</url-pattern>\n</web-resource-collection>\n<auth-constraint>\n<description>Roles</description>\n<role-name>administrator</role-name>\n<role-name>operator</role-name>\n<role-name>configurator</role-name>\n<role-name>monitor</role-name>\n<role-name>iscadmins</role-name>\n</auth-constraint>\n<user-data-constraint>\n<transport-guarantee>NONE</transport-guarantee>\n</user-data-constraint>\n</security-constraint> \n\nWhat to do next \n\nUsers must now specify a different port, depending on the mode of access. The default port numbers are as follows:\nhttp://<host_name>:16310/ibm/console\nUse the HTTP port for logging in to the Dashboard Application Services Hub on the HTTP port .\nhttps://<host_name>:16311/ibm/console\nUse the HTTPS secure port for logging in to the Dashboard Application Services Hub. \n\nNote: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."
}
] |
TRAIN_Q051 | Where can I find a description of the key differences between releases of DB2 ?
I am planning an upgrade to the latest release of DB2 and I am looking for the main differences with the previous release. I my case, more specifically between version 10.5 and version 11.1. Where can I find information on this ? | - | true | [] |
TRAIN_Q052 | 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) | false | [
{
"filename": "swg22004378.txt",
"text": "Title: IBM Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n 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. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-1557 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1557]\nDESCRIPTION: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.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/131547 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131547]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD\n\nREMEDIATION/FIXES\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nApply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861] \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS \n\nApply fix pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038] \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD \n\nApply IBM MQ 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 22 Dec 2017 - Original Published \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q053 | 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. | false | [
{
"filename": "swg21502037.txt",
"text": "Title: IBM Unable to add Centera Device in FileNet Content Engine - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log: \n\n\n2011-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.\ncom.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={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)\n\n\nCAUSE\nChanges 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. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000"
}
] |
TRAIN_Q054 | 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." | false | [
{
"filename": "swg21660890.txt",
"text": "Title: IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n \"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?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe 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) \n\nSee 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. \n\n\"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 \n\nIf 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. \nANSWER\nWhy Use Compressed References? \n\nBelow 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. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert 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.\n\n\n\n * [/support/docview.wss?uid=swg21660890&aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase \n\nStarting 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]). \n\n\n\nNOTE: 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 \nassociated 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). \nSee 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. \n\n * \n * \n * \n * \n * \n * \n * This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.\n\n\nIncrease Maximum Heap Size to Force Heap Allocation Above the 4GB mark \n\nAnother 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) . \n\n \n\nFurther Investigation \n\nIf 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].\n\nReserving Low-Memory Space with -Xmcrs\n\nIf 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.\n\nThe 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.\n\nStarting 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.\n\nTo 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.\n\n\n * -Xmcrs<reasonable_value_for_lower_memory>\n\n * \n * NATIVEMEMINFO subcomponent dump routine\n * \n * \n * \n * \n * \n * \n * \n * \n * [/support/docview.wss?uid=swg21660890&aid=2]\n * \n\n\nDisabling 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.\n\nAdditionally, 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].\n\nBefore 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.\n\n\nMemory Map Considerations \n\nThe 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: \n\n\n\n[/support/docview.wss?uid=swg21660890&aid=3] \n\nNo Compressed References Overhead using -Xnocompressedrefs \nor\n-Xmx > 25GB -increased memory footprint\n-fewer/larger objects stored on heap leads to more frequent GC\n-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 \n\n\nGetting Assistance From IBM Support \nIf 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]: \n * \n * \n * \n\n\nThen 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. \nRELATED INFORMATION\n Linux/Windows - Thanks for the memory [http://www.ibm.com/developerworks/library/j-nativememory-linux/]\nAIX - Thanks for the Memory [http://www.ibm.com/developerworks/library/j-nativememory-aix/]\nIntroducing WebSphere Compressed Reference Technology [ftp://public.dhe.ibm.com/software/webserver/appserv/was/WAS_V7_64-bit_performance.pdf]\nCompressed references [http://publib.boulder.ibm.com/infocenter/javasdk/v6r0/topic/com.ibm.java.doc.diagnostics.60/diag/understanding/mm_compressed_references.html]\nIBM Java Compressed References and Native OOMs [https://www.ibm.com/developerworks/community/blogs/kevgrig/entry/ibm_java_compressed_references_and_native_ooms]"
}
] |
TRAIN_Q055 | 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. | false | [
{
"filename": "swg21502037.txt",
"text": "Title: IBM Unable to add Centera Device in FileNet Content Engine - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log: \n\n\n2011-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.\ncom.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={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)\n\n\nCAUSE\nChanges 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. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000"
}
] |
TRAIN_Q056 | 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. | false | [
{
"filename": "swg21445430.txt",
"text": "Title: IBM Automated data collection capability provided by wpcollector tool - United States\n\nText:\nwpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)\n\nQUESTION\n What are the benefits of the wpcollector tool? How do I use this tool? \n\nANSWER\nWpcollector 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. \n\nWpcollector 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. \n\nTo run wpcollector, please follow the steps, below:\n\n\n\n * 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: \n \n\n\n * 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: * \n * \n * Unix/Linux: wpcollector.sh \n * i: wpcollector.sh \n * \n * Tip: To specify the option for collecting files for the Deployment Manager profile, use the \"dmgr.root\" parameter. For example: \n * wpcollector.bat -Ddmgr.root=/opt/IBM/WebSphere/profiles/dmgr_profile\n \n \n * If using IBM z/OS, proceed as follows [../reference/wpsdirstr.html%5C]: * \n * \n * In the Portal configuration panel, select Collect Diagnostics. \n * Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS). \n * \n * 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.\n \n \n * 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. \n \n\n\n * If tracing was requested and enabled, please follow the instructions provided by the L2 Support Engineer to disable tracing from the environment\n\nRELATED INFORMATION\n Data Collection and Symptom Analysis [http://www-01.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/trouble/tbl_apdt_over.dita?lang=en]"
}
] |
TRAIN_Q057 | Help with an insufficient authorization check for project actions in IBM Business Process Manager (CVE-2014-4844)
I need to understand details regarding an insufficient authorization check for project actions in IBM Business Process Manager (CVE-2014-4844). Where can I find this information? | - | true | [] |
TRAIN_Q058 | 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. | false | [
{
"filename": "swg1PI37248.txt",
"text": "Title: IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States\n\nText:\n FIXES ARE AVAILABLE\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http://www-01.ibm.com/support/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http://www-01.ibm.com/support/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http://www-01.ibm.com/support/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http://www-01.ibm.com/support/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http://www-01.ibm.com/support/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http://www-01.ibm.com/support/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24042746]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http://www-01.ibm.com/support/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http://www-01.ibm.com/support/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http://www-01.ibm.com/support/docview.wss?uid=swg24044479]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http://www-01.ibm.com/support/docview.wss?uid=swg24044734]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A PFBC file might fail to apply. Wsadmin will show an error\n similar to this:\n \n java.lang.Exception: java.lang.Exception: ADMG0660E:\n Properties File Validation during command\n applyConfigProperties failed. See Report file for details.\n \n The report file will contain an error similar to this:\n Error=java.lang.NullPointerException\n at\n com.ibm.websphere.management.configservice.ConfigServiceHelper.g\n etConfigDataType(ConfigServiceHelper.java:235)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work\n spaceHelper.java:563)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator\n (WorkspaceHelper.java:584)\n at\n com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu\n tes(ConfigServiceImpl.java:2102)\n at\n com.ibm.ws.management.commands.properties.resources.common.Apply\n Properties.setProperties(ApplyProperties.java:240)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Property File Based Configuration *\n ****************************************************************\n * PROBLEM DESCRIPTION: A Property File Based Configuration *\n * (PFBC) file might fail to apply. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A recent (8.5.5.5) parser change introduced a problem where\n types that have default values noted in the file and are not\n Strings can be incorrectly processed. For example:\n isolatedClassLoader=false #boolean,default(false)\n might be incorrectly processed, and as a result, the file\n might not apply.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6. Please refer to the Recommended Updates\n page for delivery information:\n http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI37248\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt / Xsystem\n \n \n * SUBMITTED DATE\n 2015-03-18\n \n \n * CLOSED DATE\n 2015-03-20\n \n \n * LAST MODIFIED DATE\n 2015-03-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBS APP SERV N\n \n \n * FIXED COMPONENT ID\n 5724H8800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"
}
] |
TRAIN_Q059 | 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. | false | [
{
"filename": "swg21377984.txt",
"text": "Title: IBM Removing a failed install from the ITM i5/OS agent - United States\n\nText:\ni5 removal TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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. \n\nSYMPTOM\nRSTLICPGM command fails to install the ITM i5/OS agent. \n\nDLTLICPGM 5724C04 command fails to uninstall the agent\n\n\nCAUSE\nRSTLICPGM/DLTLICPGM 5724C04 command failed to finish correctly and leaves the agent in an unknown state.\n\n\nENVIRONMENT\nIBM i / i5/OS machines\n\n\n\nDIAGNOSING THE PROBLEM\nRSTLICPGM and DLTLICPGM 5724C04 fail for the i5 agent.\n\n\n\nRESOLVING THE PROBLEM\n \n\n To delete the ITM i5/OS agent do the following :- \n\nFirst try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do \nthe following i5/OS commands : \n\nDLTLIB QAUTOMON \nDLTLIB QAUTOTMP \nDLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.\n\nstart qsh \ndelete /QIBM/USERDATA/IBM/ITM and all sub directories in it. \ndelete /QIBM/PRODDATA/IBM/ITM and all sub directories in it. \n\nRetry the RSTLICPGM commands specified in the user guide. \nhttp://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]\n\n\n\nPRODUCT ALIAS/SYNONYM\n ITM OS/400 agent\nITM i5/OS agent\nITM IBM i agent\n5724C04"
}
] |
TRAIN_Q060 | 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 | false | [
{
"filename": "swg22009818.txt",
"text": "Title: 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\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What can cause an STAP to fail to connect properly - I get the following messages in the logs:-\n\n/tmp/guard_stap.stderr.txt on the DB Server :-\n\"Server <ip_addr> wasn't heard from for nn sec during this attempt (nnn sec total), closing and re-opening\"\n\nand from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log\n\"Unauthorized client connecting from <ip_addr> ,rejecting\"\n\n\nCAUSE\nOne 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 :- \n[/support/docview.wss?uid=swg22009818&aid=1] [/support/docview.wss?uid=swg22009818&aid=1]\n\n\n\n\n\nANSWER\nUncheck the Approval box and the S-TAPs should start connecting . \n\n\n[/support/docview.wss?uid=swg22009818&aid=2] [/support/docview.wss?uid=swg22009818&aid=2]"
}
] |
TRAIN_Q061 | Getting hung threads, sometimes followed by OutOfMemory error
Our application is hanging, we see lots of hung threads in the SystemOut.log, occasionally followed by OutOfMemory error. | - | true | [] |
TRAIN_Q062 | 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. | false | [
{
"filename": "swg21657458.txt",
"text": "Title: IBM Minimum authorization required for SAP agent logon userid - United States\n\nText:\nauthorization minimum IBMMON_AGENT profile settings agent userid SAP MySAP /IBMMON/AUTH TECHNOTE (FAQ)\n\nQUESTION\n What are the minimum authorizations required for the userid used by the ITM MySAP agent to logon a SAP system? \n\nANSWER\nBy 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.\nIf 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.\nDepending 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.\nBy looking at this profile, you can obtain the needed authorization information.\nIn example, for MySAP agent 6.2 IF16, those are the authorization defined for the /IBMMON/AUTH profile: \n\n\n[/support/docview.wss?uid=swg21657458&aid=1] [/support/docview.wss?uid=swg21657458&aid=1]\n\nYou 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.\n\n \n\nPRODUCT ALIAS/SYNONYM\n IBM Tivoli Monitoring MySAP Agent 6.2"
}
] |
TRAIN_Q063 | 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. | false | [
{
"filename": "swg24039235.txt",
"text": "Title: IBM Operational Decision Manager V8.5.1.2 Fix Pack - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.5.1 can use this fix pack.\n\n\nHow to install the fix pack\nIf you are not installing both Operational Decision Manager components, skip the instructions regarding Decision Center or Decision Server.\n\n\n 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.) \n 2. Extract the archive to a new folder, named WDC. \n 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.) \n 4. Extract the archive to a new folder, named WDS.\n\n\nInstalling by using IBM Installation Manager: 1. Launch IBM Installation Manager. \n 2. In the toolbar menu, open File > Preferences and do the following: \n 3. Select repositories. \n 4. For Decision Center, click Add Repository. \n 5. Browse to the extracted folder WDC\\updates. \n 6. Select the file repository.config. \n 7. For Decision Server, click Add Repository. \n 8. Browse to the extracted folder WDS\\updates. \n 9. Select the file repository.config. \n 10. Make sure the repositories are selected in the Repositories list. \n 11. Click Apply to save your changes, and click OK to close the Repositories list. \n 12. Click Update to update your installation. \n 13. Follow the instructions in the installation manager to complete the installation.\n\n\nInstalling by using the Installation Manager command line: 1. Locate the imcl command under <IM installation>/eclipse/tools. \n 2. Run the commandimcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense.\n\n * Use the option -installDirectory <install path of ODM 8.5.1> to update a specific installation. \n * If you update only Decision Server or Decision Center, specify the repository accordingly.\n\n\nApplying the fix pack \nAfter 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]. \n\nWarning: \nIf 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\nFollow the instructions provided in the following resources:\n\nDOWNLOAD PACKAGE\n\n\n\nPROBLEMS SOLVED\nFix List for IBM Operational Decision Manager [http://www.ibm.com/support/docview.wss?uid=swg27023767]\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] \nWhat 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 \n [/support/docview.wss?uid=swg24039235&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039235&aid=2]Problems (APARS) fixed\nPI31830, 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"
}
] |
TRAIN_Q064 | 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 | false | [
{
"filename": "swg27045339.txt",
"text": "Title: IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems - United States\n\nText:\n RELEASE NOTES\n\nABSTRACT\n IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems \n\nCONTENT\nWebSphere Application Server 8.5.5 announced IBM WebSphere SDK Java Technology Edition 8.0 as an option for Java. \n\n\n\n\n * Liberty added support in fix pack 5 \n * 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. \n * In 8.5.5.14 and later, it is planned that this SDK will be required for all new installations and all updates (fixpacks).\n \n \n\nThe following are the minimum supported OS levels for IBM WebSphere SDK Java Technology Edition 8.0 in WebSphere Application Server. Action Required:\n\n * \n * \n * .0\n * \n\n\nOperating System minimums: \n\n * AIX\n * AIX 6.1 TL7 \n AIX 7.1 TL3 \n * HP-UX IA64\n * HP-UX 11i v3 (11.31) \n * IBM i\n * IBM i V7R1 \n * Linux\n * RedHat Enterprise Linux 6 \n RedHat Enterprise Linux 7 \n SLES 11.1 (SP1) \n SLES 12 \n Ubuntu 12.04 LTS \n Ubuntu 14.04 LTS \n Ubuntu 16.04 LTS \n * Windows\n * Windows 7 service pack 1 \n Windows 8 (not Metro) \n Windows Server 2012 \n Windows Server 2016 \n * Solaris \n * Solaris 11 \n * z/OS\n * z/OS 1.13 \n z/OS 2.1 \n z/OS 2.2 \n\n\n\nComponent 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. \n * 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."
}
] |
TRAIN_Q065 | 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 | false | [
{
"filename": "swg21636533.txt",
"text": "Title: IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States\n\nText:\nverbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\n\nQUESTION\n How can I write verbose gc output to a log file other than the native_stdout? \n\nCAUSE\nBy default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.\n\nANSWER\n \n\nWAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:/tmp/gc.log\n\nTo enable log file rotation:\n-XX:+UseGCLogFileRotation\n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M\n\n\nnotes:\n-Xloggc:<fileName> \n\n * ex: -Xloggc:/tmp/gc.log \n\n-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc \n\n-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. \n\n-XX:GCLogFileSize=<number>K (or M) * The size of the log file at which point the log will be rotated, must be >= 8K. \n\n\nHP: \nAdd the following parameters to the generic JVM arguments: \n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xverbosegc:file= /tmp/gc_pid$$.vgc \n\nTo enable log file rotation: \n-XX:+UseGCLogFileRotation \n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M \n\nnote : $$ maps to the PID of the java process RELATED INFORMATION\n 6941923 : RFE: Handling large log files produced by lon [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6941923]\nEnabling verbose garbage collection (verbosegc) in WebS [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21114927]\nWhere to set generic JVM arguments in WebSphere Applica [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21417365]\nVerify Java SDK version shipped with IBM WebSphere Appl [http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg27005002]\nHP-UX Java 6.0.18 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03119431/c03119431.pdf]\nHP-UX Java 7.0.05 - Handling large GC log files [http://h20000.www2.hp.com/bc/docs/support/SupportManual/c03123467/c03123467.pdf]\nOracle - Java HotSpot VM Options [http://www.oracle.com/technetwork/java/javase/tech/vmoptions-jsp-140102.html]"
}
] |
TRAIN_Q066 | 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. | false | [
{
"filename": "swg24043263.txt",
"text": "Title: IBM Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002) - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n 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. \n\nDOWNLOAD DESCRIPTION\n\n\n\n(C) Copyright International Business Machines Corporation 2017.\nAll rights reserved.\n\nComponent: Tivoli® Log File Agent,\nVersion 6.3.0\n\nComponent ID: 5724C04LF\n\nFix Pack: 0002, 6.3.0-TIV-ITM_LFA-FP0002\n\nDate: September 19, 2017\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n\n1.0 General description\n===============\nThis fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC \nlittle-endian Log File agent. In addition, it resolves the APARs and \ndefects listed in the \"Problems Fixed\" section below and includes the\nsuperseded fixes listed in section 2.4.\n\n\n2.0 Problems fixed\n============\nThe following problems are addressed by this fix.\n\n2.1 APARs\n-------------\n\nAPAR: IV96363\nAbstract: AGENT CRASHES ON WINDOWS 2016 WHILE READING LOG\nAdditional information: The agent crashes when a second file close\nattempt follows a successful close of the monitored log.\nAny subsequent I/O operations, such as fseek, fgets, fclose,\netc, either on that thread or another thread using the same\nfile handle may result in a failure or a crash because the\nfile is no longer open or the handle is invalid. The failure\nsometimes results in an fgetpos failure with \"errno 9 'Bad\nfile descriptor'\" and returns with a -1.\n\nThis has been seen more prevalently on Windows 2016 but \nmight occur on other platforms. This is related to IV60331.\n\nOn the agent system, with a minimum of the following trace:\n\"ERROR (UNIT:kumpfile ALL) (UNIT:kum0fdp0 ALL)\" enabled, the\nagent RAS1 log\n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log\nshows trace points similar to the following: \n- - - \n... \n...:kum0fdp0.c,76,\"KUM0_FileClose\") IOE 5619070 file handle\n7C3AB428 File close successful\n...:kum0fdp0.c,111,\"KUM0_FileClose\") SEptr 5613548 local file \nD:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070 \n7C3AB428 closed unsuccessfully\n...:kum0fdp0.c,82,\"KUM0_FileClose\") File close failed for IOE \n@5619070, status code -1, errno 0 'No error'\n...:kum0fdp0.c,111,\"KUM0_FileClose\") SEptr 5613548 local file \nD:/Log/WAS/AppSrv01/nodeagent/SystemOut.log IOptr 5619070 \n7C3AB428 closed unsuccessfully \n... \n- - - \n\nAPAR: IV95005\nAbstract: \"DETECTED CODEPAGE CP943, USING CP932 INSTEAD TO MAP \nBACKSLASH TO U+005C, NOT U+00A5 (YEN SYMBOL)\" LOGGED ON\nEVERY READ\nAdditional information: With a locale of Ja_JP (Shift-JIS) and\nERROR level trace, when the data is in the local code page,\nthe following message appears in agent RAS1 log for each\nmonitored event processed: \n\"Detected codepage CP943, using CP932 instead to map\nbackslash to U+005C, no U+00A5 (Yen symbol)\". \n\nThis occurs on the agent system, with only ERROR trace\nenabled. The agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains trace points similar to the following:\n- - - \n... \nkum0nget.c,438,\"TranslateStringToUTF8\") Detected codepage \nCP943, using CP932 instead to map backslash to U+005C, not \nU+00A5 (Yen symbol) \n... \n- - - \n\nAPAR: IV93401\nAbstract: USING REGEXLOGSOURCES TO MONITOR A REMOTE FILE FAILS\nWITH FILE NOT FOUND \nAdditional information: Using RegexLogSources to monitor a remote\nfile fails with \"*** Unable to obtain statistics for file \n</LFA_test_logs/test_1.log> errno 2 'No such file or\ndirectory\". This occurs right after the file has been found\nand matched. (Note: if the monitored file is also found\nlocally, it will succeed and monitor the local file.) \nUsing the same file in LogSources results in a match. \n\nOn the agent system, with a minimum of the following trace:\n\"ERROR (UNIT:kumpdcm2 ALL) (UNIT:kum0dir ALL)\" enabled, the\nagent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows \ntrace points similar to the following: \n\n- - - \n... \n...:kumpdcm2.c,195,\"KUMP_GetNextMember\") Directory 7F3B3401C380 \n/LFA_test_logs matched <test_1.log> to pattern <^test_1.log$> \n...:kumpdcm2.c,211,\"KUMP_GetNextMember\") Directory handle \n7F3B3401C380 \nname /LFA_test_logs successfully matched <test_1.log> to pattern \n<^test_1.log$> \n...:kumpdcm2.c,217,\"KUMP_GetNextMember\") Exit: 0x0 \n...:kumpdcm2.c,301,\"KUMP_GetNextMemberDouble\") Retcode 0 \nDirectory \n/LFA_test_logs Member <test_1.log> matched ^test_1.log$ \n...:kumpdcm2.c,330,\"KUMP_GetNextMemberDouble\") Directory \n7F3B3401C380 \n/LFA_test_logs member successfully matched <test_1.log> pattern \n<^test_1.log$> \n...:kumpdcm2.c,335,\"KUMP_GetNextMemberDouble\") Exit: 0x0 \n...:kum0dir.c,143,\"KUM0_stat_withMsgFlag\") *** Unable to obtain \nstatistics for file </LFA_test_logs/test_1.log> errno 2 'No such \nfile or directory' \n...:kum0dir.c,192,\"KUM0_stat_withMsgFlag\") Unsuccessfully stat \nfile \n/LFA_test_logs/test_1.log size=0 access time=0, modification \ntime=0, \ncreation time=0 \n...:kumpdcm2.c,481,\"KUMP_DetermineCurrentMonitorFileNameStrict\") \nFile \n/LFA_test_logs/test_1.log skipped, stat failed -1 \n... \n- - - \n\nAPAR: IV89574\nAbstract: INVALID CHARACTERS SEEN IN THE TRACE \"*****Error: \nu_strFromUTF8 failed for string ... - <filename> .........,\nstatus 10 <U_INVALID_CHAR_FOUND>\" \nAdditional information: In the agent RAS1 log, the trace points \n\"*****Error: u_strFromUTF8 failed for string ..... - \n<filename> ..., status 10 <U_INVALID_CHAR_FOUND>\" and \n\"*****Error: uregex_setText failed...\" contain garbled or \ninvalid characters. The garbled characters are not in the\nevents themselves. \n\nSince these messages might occur when the agent is processing\na directory listing in order to determine the current file\nto monitor as a result of a wildcard character in the \nRegexLogSources parameter, if the <filename> that results \nin this error is a file that should be monitored, then events\nwould be lost as the file is not monitored. The <filename> \nis in the directory for RegexLogSources. The additional \ninvalid characters are not seen in the file listing on the\nsystem. \n\nThis was discovered on Log File Agent V6.3 and later on \nWindows, but also occurs on UNIX. \n\nOn the agent system, with a minimum of the following \ntrace enabled: \"ERROR (UNIT:kum0regx ALL)\", the agent RAS1\nlog <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log\nshows trace points similar to the following with some extra\ncharacters added \".lnk\": \n----- \n...:kum0regx.c,286,\"KUM0_IsRegExPatternMatch\") \n*****Error: u_strFromUTF8 failed for string ä«ä¨äOäèäìäjäì - \nänäfäîän .lnkÙl ÙsÙw pRegEx @4D05810 status 10 <U_INVALID_CHAR_FOUND> \n--- \n\nAPAR: IV79204\nAbstract: LOGS RE-READ FROM THE BEGINNING WHEN DAYLIGHT SAVING\nTIME (DST) ENDS\nAdditional information: On Windows systems, when daylight saving\ntime ends, log files might be re-read from the beginning\nresulting in old events being re-sent. This only occurs \nwhen time is set back. \n\nThe agent falsely detects that the configuration (.conf) \nand format (.fmt) file have changed when the system is\nconfigured to \"Automatically adjust clock for Daylight \nSaving time\" and the file timestamps automatically change \ntriggering an agent reset. When NumEventsToCatchUp is set\nto -1, this series of events causes the log file to be\nre-read from the beginning. This was seen with IF0003 and\nIF0004 when monitoring log files on Windows operating \nsystems, but not with the Windows Event log. This problem\ndid not occur on UNIX systems. \n\nTo resolve this issue you must install and use the Windows\nWIX64 (x86-64 bit) agent or specify NumEventsToCatchUp=-2\nin the configuration file as a work-around. \n\nAPAR: IV77403\nAbstract: WINDOWS EVENT LOG EVENTS ARRIVED DELAYED WHEN \nNUMEVENTSTOCATCHUP IS USED \nAdditional information: With a large input load (for example,\n8004 events on each of 4 threads), Windows Event Log events\narrive with a significant delay when NumEventsToCatchUp=-1\nis set in the conf file. The delay increases as the event\nbacklog grows. It can be in the order of 5 minutes depending\non CPU, etc. This is a result of the inherent overhead in\nmaintaing the position (bookmark) in the Windows Event Log\nwhen NumEventsToCatchUp is set to -1 or n. \n\nThis is a follow-on to APAR IV63704. \n\nAPAR: IV76731\nAbstract: UNABLE TO RENAME FILE WHICH IS BEING MONITORED BY ITM\nLOG FILE AGENT \nAdditional information: On Windows systems, when the agent is\nmonitoring an application log, the log file cannot be \nrenamed because the file is open or in use. When new\nrecords are added to the log, the agent opens the log, \nreads the log and closes the log. However, when a large\nvolume of events are written to the log file, the log file\nmay remain open or in use due to operating system\nefficiencies. As a result, an attempt to rename the log \nfile may fail. This problem occurs more prevently with the\nWINNT 32-bit agent, when NumEventsToCatchUp is set to -1.\n\nTo minimize occurrence of this issue, use the Windows (WIX64) \nx86-64 bit Log File agent. \n\nAPAR: IV60331\nAbstract: RESETTING OF MULTIPLE CONF/FORMAT FILES CAUSES A CRASH\nAdditional information: Updating multiple configuration (.conf) \nor format (.fmt) files, usually via a script or a situation \nthat runs frequently, and causes the agent to reset might \nresult in a core or crash. This also might be more likely \nto occur with multiple subnodes to monitor a large number\nof files, for example, 100 files. The root cause of the\ncrash is closing a file which is already closed or no longer\nexists. \n\nThis has been seen, mainly on Linux, on agent start-up,\nshutdown or reset as a result of configuration file changes. \nThe problem was originally discovered in Log File Agent \nv6.2.3.1.\n\nThe <hostname>_lo_<#########>.log might contain information\nsimilar to the following: \n\n*** glibc detected *** /opt/IBM/ITM/lx8266/lo/bin/kloagent: \ndouble free \nor corruption (out): 0x00007f222d727030 *** \n======= Backtrace: ========= \n/lib64/libc.so.6[0x3c158760e6] \n/lib64/libc.so.6[0x3c15878c13] \n/lib64/libc.so.6(fclose+0x14d)[0x3c1586674d] \n/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(kum_fclose+0x97)[0x7f222 \n42a68db] \n/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseIOResources+ \n0x430)[0x7f2224275444] \n/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_ReleaseSourceResour \nce+0xae1)[0x7f22242799d1] \n/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(KUMP_FileServer+0x7114)[ \n0x7f2224250f30] \n/opt/IBM/ITM/lx8266/lo/lib/libkloudp.so(+0xb9b56)[0x7f222427fb56 \n] \n/lib64/libpthread.so.0[0x3c16007851] \n/lib64/libc.so.6(clone+0x6d)[0x3c158e890d] \n. . . \n\n2.2 Defects\n--------------\nNone.\n\n2.3 Enhancements \n----------------------\nEnhancement: IV77403, IV76731\nAbstract: Add Support for Windows x86-64 bit (WIX64) Agent\nAdditional Information: Support was added for Windows x86-64 bit\n(WIX64) agent. This addresses APARs IV76731 and IV77403.\n\nEnhancement: 216440\nAbstract: Add Support for PowerPC little-endian (PPCLE)\nAdditional Information: Support was added for PowerPC little-endian.\n\n2.4 Superseded fixes\n-------------------------\n6.3.0-TIV-ITM_LFA-FP0001\n6.3.0-TIV-ITM_LFA-IF0005\n6.3.0-TIV-ITM_LFA-IF0004\n6.3.0-TIV-ITM_LFA-IF0003\n6.3.0-TIV-ITM_LFA-IF0002\n6.3.0-TIV-ITM_LFA-IF0001\n\n2.4 APARs and defects included from superseded fixes\n---------------------------------------------------------------\n\n6.3.0-TIV-ITM_LFA-FP0001\n------------------------ \nAPAR: IV82875\nAbstract: WINEVENTLOG REREAD FROM BEGINNING ON AGENT RESTART \nAdditional information: When monitoring Windows® Event Logs, the\nevent log is re-read from the beginning when the agent is\nrestarted, resulting in old events being sent. This occurs \non Microsoft Windows 2003 or 2008 systems with the following\nsettings in the agent configuration file: \n- WINEVENTLOGS=<named event logs> \n- NumEventsToCatchUp=-2 \n- UseNewEventLogAPI=n (must be set on Windows 2008 systems) \n\nNote: NumEventsToCatchUp=-2 is not supported for Windows\nEvent logs. \n\nProblem Determination: On the LO agent system, with a \nminimum of the following trace specification:\nKBB_RAS1: ERROR (UNIT:WinLogQuery ALL) \nthe agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows \ntrace points similar to the following: \n- - - \n... \n...:winlogqueryclass.cpp,2521,\"WinLogQueryClass::\nEventStartInit\") WARNING: numEventsToCatchUp is -2 but\nthere aren't that many events. Starting with oldest instead \n... \n- - - \n\nAPAR: IV82170\nAbstract: SOME EVENTS ARE NOT DETECTED WHEN BOTH MULTI-LINE AND\nSINGLE-LINE FORMATS ARE USED \nAdditional information: When using a format file which contains\nboth multi-line and single line formats, some events might\nnot be detected and are discarded. In this case, the events\nwhich were discarded were single lines of data which matched\nthe single line formats. The single lines were discarded\nbecause the number of lines remaining to be processed was\nless than or equal to (not greater than) the maximum number\nof lines in the multi-line format. \n\nThis problem was discovered using errpt, but it can occur\nwith other pipes such as syslog, or with a monitored file. \nIt occurs on Log File Agent V6.3, up to Interim Fix 0005 \nand is platform independent.\n\nProblem Determination: On the LO agent system, with a \nminimum of the following trace specification: \nKBB_RAS1: ERROR (UNIT:logmonitor ALL)(UNIT:kumrmfr ALL)(UNIT:kumpfile ALL) \nthe agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows \nall the lines are read into the buffer properly. Records\nare processed until the ReadCount is equal to the \nAttributeSetCount, and then the next \"File Data Record\" is \nempty, even though more unprocessed data was still in the\nbuffer. \n- - -\n... \n...:kumprmfr.c,449,\"KUMP_ReadMonitorFileUnicodeRecord\") \n<0x1111746D0,0x2FF> \n... \n...:kumprmfr.c,454,\"KUMP_ReadMonitorFileUnicodeRecord\") Read \n767 bytes : \nElapsed Time: 0.000425 sec CPU Time: 231 usec \n... \n... \n... \n...:kumprmfr.c,1112,\"KUMP_ReadMonitorFileUnicodeRecord\") \nDlmRecordMode 0 ReadCount 5 DlmRecordDetected 0 PEptr @11103E450\nShutDownPending 0 AttributeSetCount 5 RecordSetWaitCount 0 \nFileMonitorFrequency 5 \n... \n...:kumprmfr.c,1153,\"KUMP_ReadMonitorFileUnicodeRecord\") \nFile EOF switch set \n...:kumprmfr.c,1182,\"KUMP_ReadMonitorFileUnicodeRecord\") Exit: \n0x111941E8 \n...:kumpfile.c,594,\"KUMP_FileServer\") <0x1111941E8,0x0> \nFile Data Record: \n... \n- - -\n\nAPAR: IV81364 \nAbstract: PROCESS PRIORITY CLASS SETTINGS NOT REFLECTED OR SET\nFOR LOG FILE AGENT PROCESS\nAdditional information: After configuring the Process Priority\nclass value, the agent process running on Red Hat Linux\ndoes not set the corresponding priority or niceness value\nfor its process. The priority is set on the thread and not\nthe process (PID).\n\nFor example, after configuring the agent and setting the \nProcessPriorityClass in the configuration file or during \nconfiguration to \"D\": \n\nWhen the ps command is issued, the priority of the agent\nprocess remains same: \n# ps -eo priority,nice,comm,args,pid,time | grep kloagent \n20 0 kloagent /opt/IBM/ITMfLFA/lx8266/lo/ 27424 \n00:00:00 \n\nProblem Determination: On the LO agent system, with a \nminimum of the following trace specification: \nKBB_RAS1= ERROR (UNIT:logmonitor ALL) (UNIT:Utilities ALL)\nthe agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows \ntrace points similar to the following: \n- - -\n...\n...:logmonitorqueryclass.cpp,479,\"setProcessPriority\") New*\nconf file = /opt/IBM/ITM/config/test_lo.conf , fmt file = \n/opt/IBM/ITM/config/test_lo.fmt in subnode NULL \n...:logmonitorqueryclass.cpp,490,\"setProcessPriority\") New* \nProcessPriorityClass setting D found. \n...:logmonitorqueryclass.cpp,532,\"setProcessPriority\") New* \nset process priority value -5 \n...:utilities.cpp,517,\"Utilities::setPriority\") Active RAS1 \nClasses: EVERYT EVERYE EVERYU \n...:utilities.cpp,517,\"Utilities::setPriority\") Entry \n...:utilities.cpp,540,\"Utilities::setPriority\") Successfully\nset process priority to fffffffb \n...:utilities.cpp,554,\"Utilities::setPriority\") Exit: 0x0 \n... \n- - -\n\nFeature: 216423 \nAbstract: Add support for Linux PowerPC (lpp266) \nAdditional Information: The agent is now supported running on \nLinux PowerPC Red Hat 7.1.\n\nFeature: 216820\nAbstract: Upgrade to Installer v6.2.3 FP0005\nAdditional Information: Upgrade to an Installer which contains\ninstaller APAR IV67172 and provisional APAR IV65616 for \nRed Hat Linux v7 support.\n\nThe following error might have been seen when running\ninstall.sh:\n================================================ \nITM home directory \"/opt/IBM/ITM\" already exists.\nOK to use it [ 1-yes, 2-no; \"1\" is default ]? 1\ncut: fields and positions are numbered from 1\nTry 'cut --help' for more information.\ninstall.sh failure: KCI0766E could not find arch \"\" in a JRE version file.\n================================================ \n\n6.3.0-TIV-ITM_LFA-IF0005\n------------------------ \nAPAR: IV78340\nAbstract: EVENT ARRIVAL DELAYED DUE TO CPU THROTTLING\nAdditional information: After a system reboot which includes\nautomatic start-up of a Log File Agent instance, events\nbecome increasingly delayed from minutes to as much as hours.\nThe root cause of the delay is the CPU throttling, which\noccurs even when the Process maximum CPU percentage is\nconfigured at 100%, the default which indicates no CPU\nthrottling, because at that point internally the maximum CPU\nis reset to zero. This can occur with only a light flow rate\nof events. \n\nIt was discovered on HP-UX and although, it is platform\nindependent, it may be more prevalent on HP-UX. \n\nProblem Determination: With a minimum of the following trace\nenabled: \"KBB_RAS1=ERROR (UNIT:kumpcpu ALL) (UNIT:kumpscan ALL) \n(UNIT:kumpinit ALL)\", the agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains trace points similar to the following: \n- - - \n... \n...:kumpcpu.c,634,\"KUMP_hpux_getcpucputime\") cycles t 0 \n277079589 u 0 0 s 0 0 i 0 0 u 0 210142401 s 0 50284806 i 0 \n16652382 \n...:kumpcpu.c,486,\"KUMP_GetCPUTimeDiff\") cpu time diff 692698 \nsecond 0 277079589; first 0 0 \n...:kumpcpu.c,486,\"KUMP_GetCPUTimeDiff\") cpu time diff 692698 \nsecond 0 277079589; first 0 0 \n...:kumpcpu.c,486,\"KUMP_GetCPUTimeDiff\") cpu time diff 2003 \nsecond 0 277079589; first 0 276278019 \n...:kumpcpu.c,332,\"KUMP_UpdateProcessTime\") Process utilization\n0.000000%; Changing the dampening wait from 0 milliseconds to 1\nmilliseconds \n... \n- - - \n\nAPAR: IV76119\nAbstract: REMOVAL OF RC4 CIPHER FROM REMOTE MONITORING\nAdditional information: The arcfour (RC4) cipher algorithm, as used\nin the TLS protocol and SSL protocol, could allow a remote\nattacker to obtain sensitive information. Successful\nexploitation could allow an attacker to retrieve sensitive\ninformation. This vulnerability is commonly referred to as\n\"Bar Mitzvah Attack\" (CVE-2015-2808). Support for the arcfour\ncipher is being removed. \n\nAPAR: IV75776\nAbstract: UNABLE TO OBTAIN MONITORED FILE STATISTICS ERROR WHEN FILE\nNAME CONTAINS DOUBLE-BYTE CHARACTERS \nAdditional information: When monitoring a file which contains\nJapanese or double-byte characters in the filename, the\nmessage \"Unable to obtain statistics for file < <filename> >\nerrno 2 'No such file or directory'\" is written to the agent\nlog at approximately every poll interval cycle. However, the\nfile exists and is correctly monitored. \n\nThis occurs on Log File Agent version 6.3.0 and is platform\nindependent.\n\nProblem Determination: With a minimum of the following trace\nenabled: \"KBB_RAS1=ERROR (UNIT:kum0dir ALL)\", the agent RAS1\nlog <hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log\ncontains trace points similar to the following: \n- - - \n... \n...:kum0dir.c,147,\"KUM0_stat_withMsgFlag\") *** Unable to obtain \nstatistics for file <C:/temp/[filename].log> errno 2 'No such \nfile or directory' \n...:kum0dir.c,167,\"KUM0_stat_withMsgFlag\") Unsuccessfully stat \nfile C:/temp/[filename].log size=0 access time=0, modification \ntime=0, creation time=0 \n... \n- - - \n\nAPAR: IV75603\nAbstract: BACKSLASH \\ INCORRECTLY TRANSLATED ON WINDOWS WHEN SENT\nTO EIF\nAdditional information: On Windows systems when the event is\ntranslated back from UTF-8 to the native code page shift-JIS\n(SJIS/943), in order to send the event to Event Integration\nFacility (EIF), the backslash character is incorrectly\ntranslated. The backslash character (0x5c) is translated to\nUTF-8 0xC2A5, and when it is translated back to the native\ncode page, it is incorrectly translated to 0x1A which may\nshow as a blank space or unprintable character. As a result\nof IV68698, code page 932 is used to translate the event to\nUTF-8, however code page 943 is still being used to translate\nthe event from UTF-8 back to the native code page Shift-JIS.\n\nExample: \nLog File Agent v6.3 GA <cache file> \n70203_Base;msg='Tivoli [message]\\[message]' \n\nLog File Agent v6.3 and 6.3.0-TIV-ITM_LFA-IF0004\n<cache file> \n70203_Base;msg='Tivoli [message] [message]' \n\nAPAR: IV75336\nAbstract: LFA ASSOCIATED WITH LOG ANALYSIS IS DROPPING EVENTS\nAdditional information: The agent when associated with Log\nAnalysis is dropping events. When sending large amounts of\nevents to Event Integration Facility (EIF), the agent is\nunable to keep up. The message \"WARNING: <1000> events\nalready on queue, dropping the oldest one\", where <1000>\nis the default MaxEventQueueDepth value, is seen in the \nagent RAS1 log.\n\nAPAR: IV74487\nAbstract: ABLE TO MONITOR FILES GREATER THAN 2GB ON 32-BIT\nLINUX\nAdditional information: When attempting to monitor files greater\nthan 2 gigabytes on a 32-bit Linux operating system, the\nfile is not monitored and is not displayed in the Monitored\nFile Workspace in the portal. A trace in the log shows\n\"File too large\". \n\nProblem Determination: With a minimum of the following trace\nenabled: \"KBB_RAS1: ERROR (UNIT:kum0fdp0 ALL) (UNIT:kumpstdio\nALL)\", the agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains trace points similar to the following: \n- - - \n... \n<timestamp>:kumpwfrm.c,261,\"KUMP_WaitFileReadyForMonitor\") *** \nUnable to open file local file <filename...>, \nErrno: 27, ErrorText: File too large, NO retry. Exiting \n... \n- - - \n\nAPAR: IV74480\nAbstract: COMPAREBYLASTUPDATE DOES NOT MONITOR THE MOST RECENT\nREMOTE FILE ACROSS MULTIPLE DIRECTORIES \nAdditional information: When monitoring a remote log file using\nregular expression meta characters (wildcard) in one directory\npattern of the path, and using the FileComparisonMode of\n\"CompareByLastUpdate\", the most recent file from the most \nrecent directory is not monitored. Only the most recent \nfile in the first directory returned which matches the\npattern, is monitored. \n\nCompareByLastUpdate should monitor the file with the most \nrecent last update timestamp across all the directories. \n\nThis occurs on Log File Agent version 6.3.0 and appears to\nbe platform independent. It does not occur for local files. \n\nProblem Determination: With a minimum of the following trace\nenabled: \"KBB_RAS1: ERROR (UNIT:kum0sshlib ALL) (UNIT:kumpdcm ALL)\", \nthe agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log\ncontains trace points similar to the following, where\n'test0420' is not the last or only directory to search: \n- - - \n... \n<timestamp>:kumpdcm2.c,214,\"KUMP_GetNextMember\") Directory \nhandle 7FF138015DA0 name /<...>/pm_20150424 could not find any \n(more) members to match pattern <^.*\\.log$> \n... \n... \n<timestamp>:kum0sshlib.c,2184,\"ssh_session_sftp_readdir\") \nInvalid data connInfo 7FF13800AE50 pDPAB 7FF138006640 ssh_ctx \n7FF134007630 sftp_handle NULL buffer 7FF15C1DEE70 buflen 257 \nPEptr 7FF134004140 \n... \n- - - \n\nAPAR: IV72073 \nAbstract: PATH TO MONITORED FILE NAME STARTS WITH DOUBLE SLASHES (//)\nAdditional information: Using the RegexLogSources option to\nmonitor a file which contains a regular expression meta \ncharacter in the first directory of the path, the resulting\nmonitored file name path starts with 2 forward slashes (//). \nFor example: RegexLogSources=/LFA_.*/ts_.*\\.log , the File\nName field contains \"//LFA_test/ts_01.log\". \n\nThe extra starting slash is a cosmetic issue only and does\nnot cause any issues. The file is properly monitored. \nThe extra forward slash at the beginning of the path can\nbe seen on the portal in the File Name field in the Monitored\nFile Status on the Data Collection workspace or in the agent\nlogs. \n\nThe problem exists on Log File Agent v6.3.0 and v6.2.3.2. \nThis problem is platform independent. \nHowever on Windows systems, if you specify the drive letter \npreceding the path in the RegexLogSources option, the problem \ndoes not occur. \n\nProblem Determination: \nOn the the portal in the File Name field of the Data Collection \nworkspace, the File Name field contains, for example, \n//LFA_test_logs/ts_01.log \n\nWith a minimum of the following trace enabled: \n\"KBB_RAS1: ERROR (UNIT:kumpdcm ALL)\", the agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log\ncontains the double forward slashes: \n- - -\n... \n...:kumpdcm2.c,279,\"KUMP_GetNextMemberDouble\") Directory / \nMember \nLFA_test_logs matched ^LFA_.*$; FilePathSpec2 NULL; and will \nnow use //LFA_test_logs \n...:kumpdcm2.c,161,\"KUMP_GetNextMember\") Entry \n...:kumpdir.c,139,\"KUMP_OpenDir\") Successfully opened \ndirectory //LFA_test_logs 7F1748059310 7F1748059390 \n...:kumpdcm2.c,179,\"KUMP_GetNextMember\") Directory handle \n7F1748059310 name //LFA_test_logs was successfully opened \n... \n- - -\n\nAPAR: IV71539 \nAbstract: %NNNN SYSTEM PARAMETERS NOT RESOLVED IN WINDOWS EVENT\nLOG EVENTS \nAdditional information: On Windows 2003, the Log File Agent does\nnot resolve %nnnn system parameters in Windows Event Log\nevents. Windows Event Viewer is able to resolve the %nnnn to\nthe correct message. This problem might also be seen on\nWindows 2008, when \"UseNewEventLogAPI=N\" is set in the agent\nconfiguration file. \n\nFor example, the event is seen as: \nDCOM got error \"%1058\" attempting to start the service \nCOMSysApp with arguments \"\" in order to run the server: \n{7F19-11D2} \n\nWith a minimum of the following tracing enabled: \n\"KBB_RAS1: ERROR (UNIT:EventLog ALL)\", the agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-0<n>.log\ncontains entries similar to the following: \n- - -\n... \n...:eventlog.cpp,1955,\"ModifyParameter\") Entry \n...:eventlog.cpp,1969,\"ModifyParameter\") Scanning <DCOM \ngot error \"%1058\" attempting to start the service COMSysApp\nwith arguments \"\" in order to run the server: \n{7F19-11D2} > for replaceable parameters. \n...:eventlog.cpp,2175,\"ModifyParameter\") No parameters to \nformat. \n\n...:eventlog.cpp,2185,\"ModifyParameter\") Scan results \n<DCOM got error \"%1058\" attempting to start the service \nCOMSysApp with arguments \"\" in order to run the server: \n{7F19-11D2} > \n...:eventlog.cpp,2192,\"ModifyParameter\") Exit \n...:eventlog.cpp,1600,\"DisplayRecord\") Event Log Record: \n<DCOM got error \"%1058\" attempting to start the service \nCOMSysApp with \narguments \"\" in order to run the server: \n{7F19-11D2}> \n...:eventlog.cpp,1607,\"DisplayRecord\") Exit \n... \n- - \n\nAPAR: IV79219\nAbstract: SHIP LIBKLOSSH-GSK8 LIBRARIES FOR z/LINUX 32-bit and \n64-bit FOR REMOTE FILE PROCESSING. \nAdditional information: The libklossh-gsk8 library was not included\nand shipped for ls3263, ls3266, hp11, and hp116 interps.\nDefect 215184.\n\nDefect: 215412\nAbstract: Improve servicability of Windows File Notification \nWaitForSingleObject trace message\n\n6.3.0-TIV-ITM_LFA-IF0004\n------------------------ \nAPAR: IV68698\nAbstract: WITH JAPANESE LOCALE, BACKSLASH CHARACTER IS WRONGLY\nTRANSLATED WHEN INCLUDED IN TAKE ACTION COMMAND STRING\nAdditional information: When an event which is detected by the agent\nis output from a situation using a Take Action command, by a \nredirection, etc.; a single-byte backslash character (\"\\\") is\ndisplayed as a double-byte \"middle point\" character. \n\nThe character is correctly displayed in the portal indicating \nthat it is correctly read and translated by the agent when\nread from the monitored log file. \n\nThe problem only occurs when the attribute containing \nbackslash is used in a Take Action command. When the\ncharacter is read from the monitored file, it is converted \nfrom ibm-943_P15A-2003 to UTF-8 0xC2A5 - the UTF8\nrepresentation of backslash\\yen). When the take action is \nperformed either at the agent or the monitoring server, the\nagent translates the 0xC2A5 from UTF-8 to the native CP932\nwhich results in the 0xFCFC character code. \n\nThe problem exists on the Log File Agent version 6.3.0\nInterim Fix 0003 (6.3.0-TIV-ITM_LFA-IF0003) and earlier, with\nJapanese locale. It can occur on Windows and UNIX® platforms.\n\nProblem Determination: With the following trace enabled for \nthe LO agent: \nKBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all) \n(UNIT:kumprmfr ALL) (UNIT:task ALL)\nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains trace entries similar to the following: \n- - - \n... \n(54B982FE.000A-B30:kum0nget.c,411,\"TranslateStringToUTF8\") Entry\n(54B982FE.000B-B30:kum0nget.c,419,\"TranslateStringToUTF8\") \nConverting string buffer from ibm-943_P15A-2003 to UTF-8 \n... \n(54B982FE.000F-B30:kumprmfr.c,449,\"KUMP_ReadMonitorFileUnicodeRe\ncord\") <0x5FD6678,0x19> \n+54B982FE.000F 00000000 2045206C 696E6461 C2A56C6D \n6E6F61C2 .E.lmnoa..lmnoa. !!!! \n+54B982FE.000F 00000010 A56C6D6E 6F61200D 0A \n... \n... \n(54B982FE.00BE-F20:tasklibrary.cpp,1531,\"ConvertCommandToLocal\")\nConverting UTF-8 command to codepage 932 \n... \n(54B982FE.00DC-F20:tasklibrary.cpp,864,\"executeTaskRequest\") \nExecuting task cmd /c \"echo lindaüülindaüülinda \n>>c:\\output.sit\" \n\nAPAR: IV68574\nAbstract: IN TAKEACTION, COMMAND OF MULTI-BYTE CHARACTERS WHICH HAVE 0XBA \nOR 0XBB IS TRANSLATED TO LOCAL CODE PAGE INCORRECTLY. \nAdditional information: In takeAction processing, multi-byte\ncharacters 0x82BA or 0x82BB in a command are translated to\nlocal code page incorrectly. They are incorrectly replaced \nwith \"[\" and \"]\", respectively. \n\nThe problem exists on Log File Agent v6.3.0 Interim Fix 0003 \n(6.3.0-TIV-ITM_LFA-IF0003) and earlier releases and is \nplatform independent. \n\nProblem Determination: With the following trace enabled for\nthe LO agent: \nKBB_RAS1= ERROR (UNIT:Logmonitor ALL) (UNIT:Kumprmfr ALL) \n(UNIT:kum0nget ALL) (UNIT:Task ALL) \nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains trace entries similar to the following: \n- - - \n... \n...:kum0nget.c,419,\"TranslateStringToUTF8\") Converting string\nbuffer from ibm-943_P15A-2003 to UTF-8 \n...:kum0nget.c,482,\"TranslateStringToUTF8\") Buffersize 31158\nbytes; Translated size 4 ; Copied 31158 characters readBuffer\n1113EE3B0 \n...:kum0nget.c,498,\"TranslateStringToUTF8\") Exit: 0x113EE3B0 \n...:kum0nget.c,397,\"KUM0_Fgets\") Exit: 0x113EE3B0 \n...:kumprmfr.c,449,\"KUMP_ReadMonitorFileUnicodeRecord\") \n<0x1113EE3B0,0x4> ? \n+5492C8B8.000A 00000000 E3819D0A \n... !!!!!! \n... \n<< The event is submitted to EIF - it still looks correct >> \n(5492C8B8.005F-1B:logmonitorqueryclass.cpp,2433,\"LogMonitorQuery\nClass::setInstanceData\") Submitting EIF event: \n+5492C8B8.005F SOTEST_Event;C1='ã '; \nE89 << hex character values>> \n31D \n... \n... \n...:tasklibrary.cpp,1225,\"actionCallback\") Received Take \naction. Cmd=<print -r ' ã '>>/LFA/49806/sotestout.txt >, \nUser=<sysadmin> \n... \n... \n...:tasklibrary.cpp,1531,\"ConvertCommandToLocal\") Converting\nUTF-8 command to codepage 932 \n...:tasklibrary.cpp,1554,\"ConvertCommandToLocal\") Exit: 0x10F4BBF0\n... \n... \n<< However when it is translated back from UTF-8 to codepage 943\nit becomes incorrect:>> \n...:tasklibrary.cpp,749,\"executeTaskRequest\") Entry \n...:tasklibrary.cpp,791,\"executeTaskRequest\") \ntaskInfo.name = print \n...:tasklibrary.cpp,841,\"executeTaskRequest\") Did \nnot find Task name 'print'. Going to run 'system' on the \nrequest print -r ' ?] \n'>>/LFA/49806/sotestout.txt . \n...\n- - -\n\nAPAR: IV68490\nAbstract: ALL EVENTS ARE NOT DETECTED AND SENT AS EXPECTED WHEN \nTRANSLATING FROM A MULTI-BYTE CODE PAGE \nAdditional information: All events are not matched and sent to the \nevent receiver. The events that are received might contain\ngarbled characters. Close examination of the agent log with\ntracing enabled, shows that parts of the events or lines are\noverwritten. \n\nThis only occurs when translating the data from a multi-byte \ncode page to UTF-8 and the conversion fails. The conversion \nfails because the agent was unable to read all the bytes \nrequired for a complete character into its buffer. This might \noccur if a group of messages are sent or when a message \nexceeds the maximum event size (EventMaxSize). Increasing the\nEventMaxSize might produce different results. \n\nThe problem exists on the following Log File Agent versions: \n- 6.3.0 interim fix 0003 and earlier \n- 6.2.3.2 and later \n- 6.2.2.4 Interim Fix 07 and later. \nIt is platform independent. \n\nProblem Determination: With the following trace enabled for\nthe LO agent: \nKBB_RAS1= ERROR (UNIT:logmonitor all)(UNIT:kum0nget all) \n(UNIT:kumprmfr all) \nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log might \ncontain these error indicators: \n\"partial data\", \"RESIDUAL\" , or \"*****Error: u_strFromUTF8 \nfailed for string\". \n\nTrace entries are similar to the following where the \ntranslation buffer ends 0x1A and contains partial data. \n- - -\n... \n...:kum0nget.c,411,\"TranslateStringToUTF8\") Entry \n...:kum0nget.c,417,\"TranslateStringToUTF8\") translateBuffer \nallocated 865 bytes at 43075E0 \n...:kum0nget.c,419,\"TranslateStringToUTF8\") Converting string\nbuffer from ibm-943_P15A-2003 to UTF-8 \n...:kum0nget.c,467,\"TranslateStringToUTF8\") Input buffer \n43E31C3 of length 288 when translated into 43075E0 of \nlength 293 has partial data \n...:kum0nget.c,469,\"TranslateStringToUTF8\") <0x43E31C3,0x120> \n+... 00000000 23232323 3C323031 342F3132 2F303120 \n. . . \n. . . \n+... 00000100 3C313431 37343039 35343939 36383E20 \n<1417409549968>. \n+... 00000110 3C424541 2D303030 3030303E 203CE383 \n<BEA-000000>.<.. \n+... 00000120 A1E38388 1A <--- \n..... !! \n\n<< Note: When the failure occurs, the last three bytes of the \ntranslated data are 0xEF 0xBF0 0xBD or the last byte is a 0x1A.>>\n\n...:kum0nget.c,479,\"TranslateStringToUTF8\") Buffersize \n865 bytes; Translated size 292; Copied 865 characters to \nreadBuffer 43E31C3 RESIDUAL 1 <---- \n!!!!!!!!!! \n... \n(...:kum0regx.c,286,\"KUM0_IsRegExPatternMatch\") \n*****Error:u_strFromUTF8 failed for string \n... \n- - -\n\nAPAR: IV67737\nAbstract: DUPLICATE EVENTS SENT BECAUSE LOG DETECTED AS SWITCHED OR \nRE-CREATED \nAdditional information: After applying Log File Agent v6.3 IF0003 \n(6.3.0-TIV-ITM_LFA-IF0003) on AIX and Linux, with \nNumEventsToCatchUp=-1 set in the conf file, the monitored log \nis incorrectly detected as re-created or switched. The\nmonitored log is re-read from the beginning, resulting in\nduplicate events. \n\nThis issue occurs on AIX, Linux. It does not exist on Windows \noperating systems.\n\nProblem Determination: With a minimum of the following trace\nenabled for the LO agent: \nKBB_RAS1= ERROR (UNIT:kumpfdp2 ALL) , the agent RAS1 log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows\ntrace points similar to the following: \n- - - \n... \n...:kumpfdp2.c,778,\"DoFileTailRestart\") Retrieved old monitor \nfilename </tmp/test_lfa.txt> creation time <1411741772> last \nmodification time <1411741772> size <699> \n... \n...:kumpfdp2.c,792,\"DoFileTailRestart\") Comparing creation \ntime <1411743260> last modification time <1411743260> size <758>\n...:kumpfdp2.c,816,\"DoFileTailRestart\") Note: Monitorfile \n/tmp/test_lfa.txt has been switched or re-created, updating \nrestart file \n</opt/IBM/ITM/logs/LO_LFA01_LogfileEvents_LogfileEvents_tivoli85\n.rst> \n...:kumpfdp2.c,834,\"DoFileTailRestart\") Per TailRestartFromTop\nparameter, restarting file monitoring from beginning of file\n</tmp/test_lfa.txt> \n... \n- - - \n\nThe file, listed above, is detected as re-recreated based on the\nfile information returned by the operating system: \ncreation time modification time size \nlast <1411741772> <1411741772> <699> \ncurrent <1411743260> <1411743260 > <758> \n\nAPAR: IV67708\nAbstract: WINDOWS EVENT LOG EVENTS WITH %N RESULTS IN A MESSAGE OF \n\"NONE\" \nAdditional information: The event msg field or slot might contain \na value of \"None\", when a Windows event log message contains\na %n where n is a number in the event description field. \nIf the %n is not substituted, the Microsoft EvtFormatMessage\nAPI returns ERROR_EVT_UNRESOLVED_VALUE_INSERT (15029) which\nthe agent treats as an error. As a result of the error, the \nagent discards the event description and substitutes \"None\".\n\nProblem Determination: With a mininum of the following trace\nenabled for the LO agent: \nKBB_RAS1= ERROR (UNIT:WinLogQuery ALL), the agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log shows\nthe \"15029\" error: \n- - - \n... \n...:winlogqueryclass.cpp,932,\"renderEvent\") Rendering \nmessage for event \n...:winlogqueryclass.cpp,594,\"renderEventString\") Entry \n...:winlogqueryclass.cpp,629,\"renderEventString\") \nRetrieved metadata for provider MYEVENTSOURCE from hashmap \n...:winlogqueryclass.cpp,676,\"renderEventString\") \nEvtFormatMessage failed, error = 15029, evt handle = 0x00000002 \n...:winlogqueryclass.cpp,705,\"renderEventString\") Exit: 0x0 \n... \n- - - \n\nAPAR: IV65900\nAbstract: LOG FILE AGENT WINDOWS EVENT LOG EVENT ID NOT DETECTED\nPROPERLY \nAdditional information: When the Windows Event log event ID is zero,\nLog File Agent shows a random event ID. \n\nProblem Determination: With a mininum of the following trace\nenabled for the LO agent: \nKBB_RAS1=ERROR (UNIT:WinLogQuery ALL) \nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains the following trace point that shows an error\nocurred:\n...:winlogqueryclass.cpp,799,\"renderEvent\") Error retrieving EventId\n\nAPAR: IV65500\nAbstract: PROCESS PRIORITY NOT WORKING WITH SUBNODES \nAdditional information: The agent Process Priority Class setting\ndoes not work with subnodes when it is enabled through the \nautodiscovery option. \n\nDuring the agent configuration, when the conf file and format\nfile are not specified and only the autodiscovery directory \nand Process Priority Class are set, the Process Priority is not\nset properly for the agent. It takes the default value. \n\nAPAR: IV64093\nAbstract: EXCEPTION ACCESS VIOLATION WHEN EVENT EXCEEDS MAXIMUM \nEVENT SIZE \nAdditional information: The kloagent process may terminate with an \nException 0xC0000005 (ACCESS_VIOLATION), when the size of an\nevent exceeds the maximum event size (EventMaxSize) and is\ntruncated. The LO agent instance unexpectedly stops and goes\noffline. \n\nThe crash occurs when the truncation occurs on a boundary \ncondition, and the event is truncated at a single quote and \nhas no ending semi-colon. It only occurs in the mapping of \nthe attribute slots to CustomSlots when sending events to IBM\nTivoli Monitoring from either a Windows event log or a file.\n\nProblem Determination: With a mininum of the following trace\nenabled for the LO agent: \nKBB_RAS1= ERROR (UNIT:LogMonitorQuery ALL) (UNIT:WinLogQuery \nALL) (UNIT:kum0regx ALL) \nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \ncontains the following trace points that show the size and\ndata of the incoming event:\n... \n...::winlogquerylist.cpp,1134,\"writeEventDataToPipe\") \nWriting event of length ###### to pipe: \n<contents of the log entry / event> \n...:winlogquerylist.cpp,1145,\"writeEventDataToPipe\") \nNode <.fmt stanza> wrote event to pipe for event log <logname>, \nevent size = XXXXX , bytes written = YYYYY \n\nThe following trace shows that the overall event exceeds\nEventMaxSize and will be truncated. The '16384 bytes' is the \nventMaxSize the agent is using.\n... \n...:kum0regx.c,1152,\"KUM0_PerformStringReplace\") \nWarning: Replacement string size ZZZZZ for attribute EIFEvent\nlarger than available buffer, only copied 16384 bytes to .... \n\nThe following trace points show the access violation:\n...:logmonitorqueryclass.cpp,1812,\"LogMonitorQueryClass: \n:getSlotAttrAndValue\") Entry \n...:logmonitorqueryclass.cpp,1823,\"LogMonitorQueryClass: \n:getSlotAttrAndValue\") No ; at end, <slotname>=' must be last \nslot \n... \n...:kumpxtrt.c,51,\"KUMP_PerformDataCallback\") \n*************************************************************** \n...:kumpxtrt.c,52,\"KUMP_PerformDataCallback\") \n***** Data Callback Execution Exception Handler ***** \n...:kumpxtrt.c,56,\"KUMP_PerformDataCallback\") \n***** Data Callback Function - EXCEPTION_ACCESS_VIOLATION ***** \n...:kumpxtrt.c,62,\"KUMP_PerformDataCallback\") \n*************************************************************** \n...:kumpxtrt.c,65,\"KUMP_PerformDataCallback\") Exit: 0x0 \n\nNote: These entries might not be at the end of the log. \nThere will not be the corresponding exit trace point: \n\"LogMonitorQueryClass::getSlotAttrAndValue\") Exit \n\nSee the APAR text for the .RAS file call stack information.\n\nAPAR: IV63704\nAbstract: HEAVY WINDOWS EVENT LOG LOAD CAUSES DELAYS AND THE\nAPPEARANCE OF HANGS \nAdditional information: A heavy Windows event log throughput causes\ndelays in the events being displayed on the portal. \nFor example: when sending 1000 events per second per thread,\non 4 threads, the delay in seeing the events on the portal\nmight be as much as 30 minutes. The delay increases as the\nPollInterval increases. \n\nThe agent might also appear to hang if too many duplicate\nWindows Event log messages are received. \n\nProblem Determination: With a mininum of the following trace\nenabled for the LO agent: \nKBB_RAS1: ERROR (UNIT: WinLogQueryList ALL) (UNIT:kum0nget ALL) \n(UNIT:kumpfdp6 FLOW DETAIL) \nthe agent log \n<hostname>_lo_[instance]_kloagent_<timestamp>-<nn>.log \nshows that the agent is continuing to monitor for incoming\nevents but no new events are received. \n- - - \n... \n...:winlogquerylist.cpp,1143,\"writeEventDataToPipe\") Records \nwritten to pipe n writeResult=1 \n< where n is the number of events written to pipe > \n... \n... \n< And the following sequence repeatedly even though new events are\nbeing sent. > \n...:kumpfdp6.c,162,\"WaitUntilNextSampleTime\") >>>>> \nWaitForSingleObject returned 258 for WaitFileHandle @78 \n...:kumpfdp6.c,233,\"WaitUntilNextSampleTime\") Exit: 0x1 \n...:kum0nget.c,122,\"KUM0_Fgets\") Entry \n...:kum0nget.c,136,\"KUM0_Fgets\") read / actual BufferSize = \n64146 / 192438, encoding = ibm-5348_P100-1997, convertToUTF8 = 1 \n...:kum0nget.c,308,\"KUM0_Fgets\") Using fgets() to get string \nfrom file \n...:kum0nget.c,355,\"KUM0_Fgets\") Pipe read returned no data \nsetting EOF \n...:kum0nget.c,399,\"KUM0_Fgets\") Exit: 0x0 \n...\n- - - \n\nAPAR: IV21752\nAbstract: EIF: ERROR CODE 67 IS NOT HANDLED WHILE SENDING EVENTS \nAdditional information: If Error code 67 (Connection is broken) is\nseen while sending events to the Event Integration Facility\n(EIF) receiver, then the EIF sender ignores it and keeps \nsending events forward, even though the events are not being\nreceived by the EIF receiver. \n\nThis APAR is included in this fix for the Log File Agent on\nWindows systems only. For UNIX/Linux systems, the fix is\nincluded in IBM Tivoli Monitoring Shared Libraries (TEMA)\ncomponent of IBM Tivoli Monitoring version 6.2.3 Fix Pack 02\nor later. You must install the Shared Libraries (ax) component \nseparately from the agent.\n\nEnhancement: 212595 \nAbstract: Implement AESnnn-CTR ciphers for remote logs\n\n6.3.0-TIV-ITM_LFA-IF0003\n------------------------ \nAPAR: IV60491\nAbstract: SELINUX AUDIT LOG MESSAGES GENERATED WHEN USING IPV6 WITH\nLOG AGENT \nAdditional information: On Log File Agent v6.3 and prior releases, \nrunning the agent on a Security-Enhanced Linux (SELinux)\nsystem using IPv6 with the SELinux security policy set to\n\"enforcing\" generates audit messages. The messages in the\nSELinux audit log /var/log/audit/audit.log are similar\nto the following where <hostname> is the system the agent is\nrunning on: \n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ntype=AVC msg=audit(1389964628.602:213): avc: denied { write } \nfor pid=8121 comm=\"ifconfig\" path=\"/opt/IBM/ITM/auditlogs/itm. \n<hostname>_lz_audit.log\" dev=dm-5 ino=4660 \nscontext=system_u:system_r: ifconfig_t:s0 \ntcontext=system_u:object_r:usr_t:s0 tclass=file \ntype=AVC msg=audit(1389964628.613:214): avc: denied { write } \nfor pid=8126 comm=\"ifconfig\" \npath=\"/opt/IBM/ITM/logs/<hostname>_lz_klzagent_52d92647-01.log\" \ndev=dm-5 ino=5066 scontext=system_u:system_r:ifconfig_t:s0 \ntcontext=system_u: object_r:usr_t:s0 tclass=file \n- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \n\nAPAR: IV60333\nAbstract: EVENTS FROM WINDOWS EVENT LOG ARE INTERMITTENTLY NOT\nDETECTED.\nAdditional information: Windows Event Log events are\nintermittently not detected and sent. With the UnmatchLog\nparameter specified, the event is also not saved in the\nUnmatchLog file. In previous occurrences, the missing event\nmatches one of the format expressions and is sent. With\ntracing set as described below, after the initial rendering\nof the Windows Event Log event is seen in the agent log,\nthere are no occurrences of the event in the log. \n\nThis is more likely to occur when monitoring more than one\nWindows Event Log (for example: Application, Security, \nSystem, etc). \n\nThis problem occurs on Windows systems with Log File Agent \nversion 6.2.3.2 and 6.3. \n\nAPAR: IV59814\nAbstract:BLANK ARCFOUR ALGORITHM CAUSES JAVA CORE WITH REMOTE LOG\nFILE MONITORING \nAdditional information: The Log File Agent v6.3.0 might create Java®\ncores when attempting to use the Remote Log File monitoring\nfeature which relies on SSH. The Java core is the result of a\nblank(\"\") arcfour algorithm name for the cipher. \nThe problem was initially seen on Linux, but is platform\nindependent.\n\nWith a minimum of KBB_RAS1: ERROR (UNIT:kex ALL), the agent\nlog <hostname>_lo_<instance>_kloagent_<timestamp>.log \nends with trace entries similar to the following: \n- - - \n... \n(53444D90.04B8-40:kex.c,1880,\"libssh2_kex_exchange\") Entry\n(53444D90.04B9-40:kex.c,1030,\"kexinit\") Entry \n- - - \n\nAPAR: IV42315\nAbstract: NUMEVENTSTOCATCHUP=-1 DOES NOT DETECT WHEN THE FILE HAS\nBEEN REPLACED \nAdditional information: On restart of the Log FiLe agent, when the\nconfiguration option NumEventsToCatchup is set to \"-1\", the\nagent does not detect that a monitored file has been replaced\nwith a smaller file. The monitored file is not processed until\nthe file reaches the size maintained in the restart file. It\nshould result in the file being read from the beginning. \n\n6.3.0-TIV-ITM_LFA-IF0002\n------------------------ \nAPAR: IV57736\nAbstract: LOG FILE AGENT MAY CORE, CRASH ON HP-UX WHEN \nNUMEVENTSTOCATCHUP IS USED. \nAdditional information: On HP-UX, when the configuration option\nNumEventsToCatchUp is set to a value other than zero, the\nagent might core. The problem occurs on Log File Agent v6.3. \n\nThe core might show the following: \nCore was generated by ´kloagent'. \nProgram terminated with signal 11, Segmentation fault. \nSEGV_MAPERR - Address not mapped to object \n........ \n(gdb) where \n#0 0xc000000010a30320:0 in UpdateRestartFileBaseFunction () at\nkumpfdp2.c:427 \n#1 0xc000000010a32760:0 in UpdateRestartFileWithStats () at \nkumpfdp2.c:553 \n#2 0xc000000010a3d970:0 in DoFileTailRestart () at \nkumpfdp2.c:893 \n#3 0xc000000010a90af0:0 in KUMP_FileServer () at kumpfile.c:23\n#4 0xc000000010b8eee0:0 in Task () at kumptask.c:35 \n#5 0xc0000000000fb140:0 in __pthread_bound_body+0x190 () \nfrom /usr/lib/hpux64/libpthread.so.1 \n........ \n\nWith a minimum of \"KBB_RAS1: ERROR (UNIT: kumpfdp2 ALL) \ntracing, the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log ends with \ntrace entries similar to the following: \n- - - \n... \n...:kumpfdp2.c,173,\"KUMP_ParseSingleRestartLine\") Parsing \nRecPtr 6000000000736F4F <735> \n...:kumpfdp2.c,1250,\"KUMP_ParseNumericString\") Unsuccessfully \nparsed <NULL> to value 735 \n...:kumpfdp2.c,200,\"KUMP_ParseSingleRestartLine\") Error: parsed\nlocation <NULL> file <735> creation <NULL> modification <NULL> \nsize <NULL> with RecPtr 6000000000736F53 \n...:kumpfdp2.c,427,\"UpdateRestartFileBaseFunction\") Note: \nRequired fields missing from restart file </opt/IBM/ITM/logs/L \nO_default_LogfileEvents_hpia5.rst> \n...:kumpfdp2.c,173,\"KUMP_ParseSingleRestartLine\") Parsing \nRecPtr 6000000000736F53 <;> \n...:kumpfdp2.c,200,\"KUMP_ParseSingleRestartLine\") Error: parsed\nlocation <NULL> file <NULL> creation <NULL> modification \n<NULL> size <NULL> with RecPtr 5FFFFFFFA0736F52Page 34 of 35 \n...:kumpfdp2.c,427,\"UpdateRestartFileBaseFunction\") Note: \nRequired fields missing from restart file \n</opt/IBM/ITM/logs/LO_default_LogfileEvents_hpia5.rst> \n- - - \n\nAPAR: IV56299\nAbstract: A PERCENT SIGN (%) LITERAL IS NOT SUPPORTED IN FORMAT\nSTATEMENT\nAdditional information: When a percent sign (%) or a percent sign\n(%) followed by a literal other than the valid variables of s,\nt, n, is used in a FORMAT statement, it results in an \"illegal\nvariable\" message and an incorrect regular expression. As a\nresult, the record does not match as expected. \n\nFor example: \nFORMAT 43866_Class10 \n43866_10 %s % %s* \n. . .\n\nor \n\nFORMAT 43866_30 \n%t %s %MIDDLEWR: %s \n. . .\n\nWith KBB_RAS1: ERROR, the the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains\ntrace entries similar to the following: \n- - - \n... \n(5317981A.0002-12E0:lfaconfig.cpp,1042,\"generateFormatFilter\") \nFormat \nfor class 43866_Class10 contains illegal variable \"%\" in format\nexpression \"43866_10 %s % %s*\" \n(5317981A.0003-12E0:lfaconfig.cpp,1045,\"generateFormatFilter\") \nVariable \nof type not recognized \n... \n- - - \n\nThis problem occurs on Log File Agent v6.3 and prior releases.\nIt is platform independent. \n\nAPAR: IV54710\nAbstract: WINDOWS EVENT LOG NOT MONITORED ON SOME WINDOWS 2012\nSYSTEMS AFTER INSTALLING 6.3.0-TIV-ITM_LFA-IF0001 \nAdditional information: On some Windows 2012 systems, after\ninstalling Log File Agent v6.3 interim fix 0001\n(6.3.0-TIV-ITM_LFA-IF0001), Windows Event Log events are no\nlonger monitored. The Data Collection Status workspace shows\nFile Status: \"231\". \n\nWith a minimum of \"KBB_RAS1: ERROR tracing, the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains\ntrace entries similar to the following: \n- - - \n... \n...:kum0fdp0.c,162,\"KUM0_DynamicFileOpen\") \nfopen(\\\\.\\pipe\\KLO_gail_LogfileEvents_evl(System), rb) returned\nNULL errno 231 'Unknown error' \n... \n- - - \n\nAPAR: IV53803\nAbstract: TACMD ADDSYSTEM OF LO AGENT FAILS WITH\n6.3.0-TIV-ITM_LFA-IF0001 \nAdditional information: On Tivoli Enterprise Monitoring Server \nv6.2.3 and beyond, when both the Log File Agent v6.3 (CIGM6ML)\nand the interim fix (6.3.0-TIV-ITM_LFA-IF0001) are in the\ndepot, \"tacmd AddSystem\" fails because the interim fix \ndoes not have a pre-requisite for LO version 06.30.00. The\nagent is not pushed to the endpoint. This only occurs with\nUNIX system targets.\n\nAPAR: IV53568\nAbstract: ON WINDOWS FOR NUMEVENTSTOCATCHUP=-1 CREATES MULTIPLE\nENTRIES FOR EACH LOGS IN .RST AND MISSES EVENTS \nAdditional information: If NumEventsToCatchUp=-1, the restart (.rst)\nfile should be continuously updated. This file should contain\nthe name of each log being monitored along with the last \nposition read from the log. There should only be one line for \neach monitored log file. However, instead of replacing the\nline as it should, a new row is added. As a result, it is not\nable to resume at the file position it was at when the agent\nwas stopped and events that occurred while the agent was\nstopped are missed.\n\nCPU performance issues might result from the excess processing \nof the restart file. \n\nAPAR: IV52833\nAbstract: SOME LOG LINES WRITTEN IN SEPARATE PIECES ARE INTERMITTENTLY\nNOT SENT AS EVENTS\nAdditional information: On Windows® systems, some single lines\nwritten to the monitored file in separate pieces are not sent\nand do not appear in the UnmatchLog, if one was specified.\nThis might occur intermittently, when lines are written in\nmultiple parts, particularly on Windows systems. \n\nWith a minimum of KBB_RAS1: ERROR, the agent log\n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains a\ntrace entry similar to the following: \n- - - \n...:kum0mpbc.c,50,\"KUM0_MoveStringPointerByChar\") \n***** Input string is NULL\n- - - \n\nAPAR: IV52411\nAbstract: MULTI-LINE *DISCARD* FORMAT FILTER INTERMITTENTLY ALLOWS \nRECORDS TO ESCAPE FILTER AND SHOWS UP IN THE PORTAL. \nAdditional information: A multi-line *DISCARD* format filter\nintermittently allows records to escape the filter and shows\nup in the portal.\n\nIn addition, the handling of the end of the file (EOF) with\nsaved data from a previous read is not handled correctly. \nThis allows multi-line records which are split by EOF to \nescape. The agent is not correctly retrying its read attempts\nwhen it has a partial buffer and hits the EOF logic. \n\nWith a minimum of KBB_RAS1 with (UNIT:kum ALL) the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains \ntrace entries similar to the following:\n- - - \n. . . \n(523B46FE.06DD-12:kum0regx.c,353,\"KUM0_IsRegExPatternMatch\") \nExit: 0x0 \n(523B46FE.06DE-12:kumpcapf.c,548,\"KUMP_CheckAttributesPassFilter \ns\") Data <Sep 19 12:48:27 gisdev scsi: [ID 107833 kern.warning] \nWARNING: /scsi_vhci/ssd@g600601602d301e0002f28a3e1ff9e111 \n(ssd63):\n+523B46FE.06DE > AttrName <EIFEvent> failed MatchRegEx filter \n1: <()^(.*Error for Command.*)\\r?\\n(.*)\\r?\\n(.*)\\r?\\n(.*)\\r?\\n\n(.*asymmetric.*)()> \n. . . \n- - - \n\n6.3.0-TIV-ITM_LFA-IF0001\n------------------------\nAPAR: IV48040\nAbstract: LOG FILE AGENT PROCESSING WINDOWS EVENT WHICH IS GREATER\nTHAN 64K CAUSES THE AGENT TO LOOP AND NOT PROCESS ANY MORE\nEVENTS \nAdditional information: There were three issues found: \n1)Event buffer size was limited to 64K. The event buffer\nsize is increased to 128K. A WARNING message is also issued\nif an event exceeds the buffer size. \n\n2)When the record is not processed because the buffer is too \nsmall, the current event pointer is not incremented. On the \nnext pass, the same too-large event is read again, which\nfails again and no more events are processed.\n\n3)When numEventsToCatchUp is set to a value larger than the \nnumber of records in the event log, the record number to read\nis calculated incorrectly.\n\nAPAR: IV45784 \nAbstract: FILES CREATED AFTER KLO AGENT IS STARTED ARE NOT MONITORED\nAdditional information: On a Windows® system, if the monitored file\ndoes not exist when the agent is started, the file is not\nmonitored after it is created. There might not be an entry for\nthe non-existent file in the Monitored File Status in the Data\nCollection Status workspace. \n\nThe agent agent must be re-started to recognize the file or\nthe file must exist when the agent is started. \n\nWith a minimum of KBB_RAS1: ERROR, the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains\ntrace entries similar to the following: \n- - - \n... \n...:kumpwfrm.c,261,\"KUMP_WaitFileReadyForMonitor\") *** \nUnable to open file local file <filename>, Errno: 0,\nErrorText: No error, NO retry. Exiting \n...:kumpfdp5.c,231,\"CheckFileExistAndReady\") *** File \nC:/lo/43866/43866.log -- initial monitoring setup failed\n<timestamp>:kumpfile.c,891,\"KUMP_FileServer\") >>>>> DP file\nserver ThreadID F04 ended for local file C:/lo/43866/43866.log\n... \n- - - \n\nAPAR: IV42745\nAbstract: SOME LINES WRITTEN IN PIECES ARE UNMATCHED AND PARTIALLY\nDISCARDED \nAdditional information: When a single line is written to the\nmonitored file in separate pieces, sometimes the line does\nnot match and is not sent as an event. This is because the\nlatter or subsequent piece of the line is written to the same\nlocation in the internal read buffer and overwrites the\ninitial piece of the line. The resulting partial line does\nnot match the formats and is sent to the UnmatchLog, if one\nwas specified in the configuration file. This might occur\nintermittently when lines are written in multiple parts,\nparticularly on Windows systems. \n\nWith a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL), the\nagent log <hostname>_lo_<instance>_kloagent_<timestamp>.log\ncontains trace entries similar to the following: \n- - - \n... \n...:kumprmfr.c,1015,\"KUMP_ReadMonitorFileUnicodeRecord\") \nSavedRec 51A6A58 14 <job6 started: > \n... \n...:kumprmfr.c,412,\"KUMP_ReadMonitorFileUnicodeRecord\") \n<0x51A6A58,0x56> 4+5187EED2.026F 00000000 362F362F \n32303133 2036363A 3636200D 6/6/2013.66:66.. \n... \n- - - \nThe second part of line is written to the same location in\nthe buffer, in the above example 0x51A6A58, overwriting the\nfirst part of the line. \n\nAPAR: IV42699\nAbstract: LAST MATCHING LINE OF LOG IS NOT IMMEDIATELY SENT AS A\nMATCHING EVENT \nAdditional information: With record patterns that span multiple\nlines (RECORDSET patterns), the last matching line of a\nmonitored file is not immediately sent as an event and it\ndoes not show up in the UnmatchLog, if one was specified.\nThe amount of wait time till the event is actually sent is a\nfactor of the PollInterval. \n\nWith a minimum of KBB_RAS1: ERROR (UNIT:kumprmfr ALL) \n(UNIT:kumpfdp ALL), the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains \ntrace entries similar to the following with the default \nPollInterval of 5: \n- - - \n... \n...:kumpfdp3.c,117,\"OpenFileForMonitor\") Assigned \nRecordSetMaxWait = 5 seconds \n... \n...:kumprmfr.c,1090,\"KUMP_ReadMonitorFileUnicodeRecord\")\nWaiting for RECORDSET end delimiter, RecordSetWaitCount 1 \nMaxRecordSetWait limit 100 \n...:kumprmfr.c,1090,\"KUMP_ReadMonitorFileUnicodeRecord\")\nWaiting for RECORDSET end delimiter, RecordSetWaitCount 2 \nMaxRecordSetWait limit 100 \n... \n...:kumprmfr.c,1090,\"KUMP_ReadMonitorFileUnicodeRecord\")\nWaiting for RECORDSET end delimiter, RecordSetWaitCount 99 \nMaxRecordSetWait limit 100 \n... \n- - - \n\nAPAR: IV41215\nAbstract: BRACKET { IN FORMAT RESULTS IN LOAD METAFILE EXECUTION\nEXCEPTION\nAdditional information: When an opening { bracket is used without a\nclosing bracket } in a FORMAT statement of the format file,\nthe agent log ends with a \"Load Metafile Function - \nEXCEPTION_ACCESS_VIOLATION\" on agent start-up. \nThe agent process is still running but it is waiting for \ninitialization to complete successfully and is not monitoring. \nThe Data collection status Error Code is \"No ERROR\" but there\nis no entry in the Monitored File Status for the monitored\nfile. This problem is platform independent. \n\nWith a minimum of \"KBB_RAS1: ERROR tracing, the agent log\n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains \ntrace entries similar to the following: \n- - - \n... \n...:kumplmet.c,204,\"KUMP_LoadMetafile\") \n*************************************************************** \n...::kumplmet.c,205,\"KUMP_LoadMetafile\") ***** Load Metafile \nExecution Exception Handler ***** \n...:kumplmet.c,209,\"KUMP_LoadMetafile\") ***** Load Metafile \nFunction - EXCEPTION_ACCESS_VIOLATION ***** \n...:kumplmet.c,215,\"KUMP_LoadMetafile\") \n****************************************************************\n...:logmonitorqueryclass.cpp,4031,\"LogMonitorQueryClass: \n:completReset\") Table LogfileEvents still waiting for kum to \ninitialize after 30 seconds \n... \n- - - \n\nAPAR: IV39967\nAbstract: RESTORED FILE IS NOT MONITORED AFTER CONF/FMT FILES\nMODIFIED\nAdditional information: A restored log file is no longer monitored\nand no new events are processed, when the sequence of all the\nfollowing events occur: \na) update the conf or fmt file to trigger reset processing, \nb) remove the file, for example via un-mount, rename, delete, \nmove \nc) wait for the 'File does not exist' status \nd) restore the file. \nThe Data Collection workspace continues to show a File Status \nof \"FILE DOES NOT EXIST\". \n\nIf the reset process (step a) is not triggered and only the\nfile is removed, the file is re-discovered properly. If only\nthe reset process (step a) is triggered, it also continues to \nfunction properly. \nNote: When the file is re-discovered after it is restored, it \nis read from the beginning as a new file. This is not new \nbehavior with this APAR. \n\nThe root cause of this problem occurs on LFA v6.3, but the log \nfile is monitored when the file is restored. \n\nAPAR: IV37051\nAbstract: EVENTS INTERMITTENTLY NOT MATCHED WHEN LINE WRITTEN IN\nPIECES\nAdditional information: When an application writes only part of the\nline and later writes the remainder of the line, the line\nintermittently matches as an event with no changes to the fmt\nfile. This occurs more prevalently on Windows systems because\nthe operating system notifies the agent when the file has\nchanged. When the first part of the line is written, the agent\nis notified but the partial line does not match any formats.\nWhen the second part of the line is written, the agent is\nnotified again but the remainder of the line does not match\nany formats. The two pieces of the line are treated as two\nlines, neither of which match and both pieces are written as\ntwo lines to the UnmatchLog, if one is configured. \n\nDefect: 207998\nAbstract: Agent does not continue to retry on remote log, when \nRC -3, because errno is zero.\nAdditional information: When monitoring remote log files where the\nconnection breaks; for example, the remote system shuts down\nor a network outage, the agent does not continually try\nto re-establish the connection. The remote file is not\nmonitored. The Monitored File Status might not show a row\nfor the file.\n\nWith a minimum of \"KBB_RAS1: ERROR tracing, the agent log\n<hostname>_lo_<instance>_kloagent_<timestamp>.log contains\ntrace entries similar to the following: \n- - - \n...:session.c,243,\"banner_send\") Unable to send the banner\n...:session.c,245,\"banner_send\") -3 - Error sending banner\nto remote host\n...:session.c,691,\"session_startup\") -3 - Error sending banner\nto remote host\n...:kum0sshlib.c,1227,\"ssh_session_connect\") Failed to\nestablish an SSH connection in 0 seconds for remote\[email protected]:22 \n/opt/IBM/ITM/logs/^mypia_ux_kuxagent_.*\\.log$\nmypia.ibm.com:22 socket 25 rc -3 errno 17 : \nLIBSSH2_ERROR_BANNER_SEND\n...\n- - - \n\nDefect: 206531\nAbstract: Failed to load GSKit library\nAdditional information: When both GSKit version 7 and 8 are \ninstalled on the same agent machine, either because of two\nIBM Tivoli Monitoring installs, or some other product that\nput a GSKit into the system /usr/lib directory, the wrong\nversion of the library is loaded and the GSKit \ninitialization fails. This problem has only been seen on\nLinux®.\n\nDefect: 205184\nAbstract: Improve handling of files on re-mounted file systems\n\nDefect: 204120\nAbstract: Log agent crashes on Solaris due to mis-aligned integer\nAdditional information: Agent crashes in KUMP_DoDPdataToDCH when it\nformats data from a buffer into integers and other formats,\ndue to a copy of an odd-aligned integer. \n\nDefect: 203012\nAbstract: LogSources wildcards match directories remote log -31 err\nAdditional information: If a LogSources specifies a remote directory\nand not a remote file, the Monitored File Status shows \"File\nStatus\" OK, \"File Type\" of \"REGULAR FILE\", \"PIPE\" or\n\"UNKNOWN\" and \"Current File Size\" 4096, but no files are\nmonitored.\n\nNote: After the fix, when there are no wildcards in the\ndirectory path, it may still show Status\" OK, \"File Type\"\nof \"REGULAR FILE\".\n\n\n3.0 Architecture and prerequisites\n======================\nThis fix is supported on all operating systems listed in the Tivoli\nLog File Agent User's Guide, version 6.3.0.\n\nThe following link is for the Tivoli operating system and application\nsupport matrix. Please refer to this matrix for the latest \ncertification information.\nPlease refer to the IBM Software Product Compatibility Reports (SPCR)\nfor the latest operating system certification information:\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]\n\n3.1 Prerequisites for this fix\n--------------------------------\nThe prerequisite level for this fix is as follows:\n- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher\n(6.2.2-TIV-ITM-FP0002)\n\nThis fix pack is a complete install image and as such, can be \ninstalled on a pristine system. This fix is also cumulative, and can \nbe installed on any fix level for this version, release, and mod \nlevel above the prerequisite. \n\nFor details, see the Troubleshooting Wiki:\nhttps://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]\n\n4.0 Image directory contents\n===================\nThis fix image contains the following files:\n\n- 6.30-TIV-ITM_LFA-FP0002.tar.gz\n- 6.30-TIV-ITM_LFA-FP0002.README\n\n5.0 Installation instructions \n==================\n\n5.1 Before installing the fix \n-------------------------------\n- The prerequisites listed under section 3.1 entitled 'Prerequisites\nfor this fix' must be installed before this fix can be installed.\n\n- For the purpose of this README, the symbol <CANDLEHOME> is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\IBM\\ITM'\non Windows systems.\n\n- Before installing this fix on UNIX systems, set the environment \nvariable CANDLEHOME to the IBM Tivoli Monitoring installation\ndirectory.\n\nFor example: \n> CANDLEHOME=/opt/IBM/ITM\n> export CANDLEHOME \n\n- Because there is no uninstall utility for this fix, make sure to\nperform a backup of your environment before installing this fix.\n\n- NOTE: Before installing the LO x86-64 bit agent, you must\nun-install the WINNT 32-bit version of the agent and the 32/64 \nbit compatibility package.\n\n\n5.2 Local agent update\n--------------------------\nFor installation instructions, see the Log File Agent User's Guide\nv6.3.0: \nhttp://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]\n\nNote: \n1. The PowerPC little-endian installation image is located in the\nPPC_LE directory of the installation image. Invoke ./install.sh\nfrom this directory.\n\n2. On Windows systems, when the installation completes, the \nReadme.txt displays \"Welcome to IBM Tivoli Monitoring V6.2.3 Fix\nPack 5.\" This is the installer level and Readme and is not an \nerror.\n\n5.3 Remote agent update\n----------------------------\n1. Transfer the archive file 6.3.0-TIV-ITM_LFA-FP0002.tar.gz to a\ntemporary directory on the IBM Tivoli Enterprise Monitoring \nServer system. For the purpose of this README, the symbol <TEMP>\nrepresents the fully qualified path to this directory. Note: On\nWindows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems or\nan extract utility on Windows systems. This step creates a directory\nstructure that contains fixes for all of the supported platforms.\n\n3. To add the agent fix bundles into the remote deploy depot, use\nthe \"tacmd addBundles\" command found in $CANDLEHOME/bin on UNIX\nsystems or in %CANDLE_HOME%\\bin on Windows systems. For more\ninformation on the \"tacmd addBundles\" command, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nNote: \n1. The prerequisite Log File Agent bundles must also be in the\ndepot, to ensure successful completion of the remote agent update.\n2. The 6.3.0-TIV-ITM_LFA-FP000<n> bundles must be removed from the\ndepot, using the \"tacmd removeBundles\" command. \nFor example: tacmd removeBundles -t lo -v 06300000<n>\n\nOn UNIX systems, \nif the fix was expanded to <TEMP>/6.3.0-TIV-ITM_LFA-FP0002:\n> $CANDLEHOME/bin/tacmd addBundles -n \n-i <TEMP>/6.3.0-TIV-ITM_LFA-FP0002 \n\nOn Windows systems, \nif the fix was expanded to <TEMP>\\6.3.0-TIV-ITM_LFA-FP0002:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n \n-i <TEMP>\\6.3.0-TIV-ITM_LFA-FP0002 \n\nwhere:\n-n indicates that prerequisite bundles are not automatically\nadded. The -n parameter must be used because the fix \ndirectory does not contain any prerequisites that the fix\nmight require. Please see Section 3.1 for the prerequisites\nfor this fix.\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n\n4. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following \"tacmd\" commands. For more information on the \n\"tacmd login\" and \"tacmd updateAgent\" commands, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nOn UNIX systems: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> $CANDLEHOME/bin/tacmd updateAgent -t lo \n-n <Managed system name>\n-v 06300200\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t LO \n-n <Managed system name> \n-v 06300200\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is\nspecified as two characters (LO), not three characters (KLO).\n- The node (-n) for the \"tacmd updateAgent\" command is the managed\nsystem name of the operating system (OS) agent to be updated.\nThe target node for the \"tacmd updateAgent\" command is always\nan OS agent.\n\n5.2 Agent support update\n------------------------------\nFix pack 6.3.0-TIV-ITM_LFA-FP0001 included new certificates \nin the agent support files which need to be installed. If you have\nalready installed these updates, there are no additional installation \nsteps. Otherwise, install the updates to the Tivoli Enterprise\nMonitoring Server, Tivoli Enterprise Portal Server, or Tivoli\nEnterprise Portal Desktop. For more information about installing \napplication support, see Installing and enabling application support\nin the IBM Tivoli Monitoring Installation and Setup Guide.\n\n6.0 Additional installation information\n========================\n\n6.1 Installation instructions for agent baroc file\n-----------------------------------------------------\nThere are no updates to the baroc files included in this fix or any\nof the superseded fixes. No additional installation steps are\nrequired.\n\n6.2 Verifying the update\n----------------------------\n1. To verify the agent was updated correctly, use the \"tacmd\" command\nto view the agent's current version after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer prior to viewing the agent version. \n\nFor example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring\ninstallation directory, the default location is '/opt/IBM/ITM'. \n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems -t LO\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'. \n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t LO \n\nNote: The component (-t) for the \"tacmd listSystems\" command is\nspecified as two characters (LO), not three characters (KLO).\n\nWhen the agent update is successful, the agent version is: \n06.30.02.00.\n\nAfter the agent is restarted, you can also use the GUI to verify\nthe agent was successfully updated.\n\nFor the agent on Windows systems, the version number is \n06.30.02.00. \n\n2. To verify the agent you are running contains the updates from the\nfix, see the following lines in the agent log \n<hostname>_lo_<instance>_kloagent_<timestamp>.log located in\n$CANDLEHOME/logs on UNIX systems and\n%CANDLE_HOME%\\tmaitm6\\logs on Windows systems:\n\n<timestamp> Component: ira\n<timestamp> Driver: agent_fac_63:201709131450/4769716.3 \n<timestamp> Timestamp: Sep 13 2017 ...\n\n\n7.0 Known problems and workarounds\n=========================\nNone.\n\n\n8.0 Additional product information\n======================\nNone.\n\n\n9.0 Copyright and trademark information\n================================== \nA current list of IBM trademarks is available on the Web at \"Copyright\nand trademark information\" at www.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].\n\n\n10.0 Notices\n=======\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION\n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,\nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\nSome jurisdictions do not allow disclaimer of express or implied\nwarranties in certain transactions, therefore, this statement may not\napply to you.\n\nThis information could include technical inaccuracies or typographical\nerrors. Changes are periodically made to the information herein; these\nchanges will be incorporated in new editions of the publication. IBM\nmay make improvements and/or changes in the product(s) and/or the\nprogram(s) described in this publication at any time without notice.\n\nMicrosoft, Windows, and Windows Server are trademarks of Microsoft\nCorporation in the United States, other countries, or both. \n\nJava and all Java-based trademarks and logos are trademarks or\nregistered trademarks of Oracle and/or its affiliates. \n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.\n\nThird-Party License Terms and Conditions, Notices and Information\n-----------------------------------------------------------------\nThe license agreement for this product refers you to this file for\ndetails concerning terms and conditions applicable to third party\nsoftware code included in this product, and for certain notices and\nother information IBM must provide to you under its license to\ncertain software code. The relevant terms and conditions, notices and\nother information are provided or referenced below. Please note that\nany non-English version of the licenses below is unofficial and is\nprovided to you for your convenience only. The English version of the\nlicenses below, provided as part of the English version of this file,\nis the official version.\n\nNotwithstanding the terms and conditions of any other agreement you\nmay have with IBM or any of its related or affiliated entities\n(collectively \"IBM\"), the third party software code identified below\nare \"Excluded Components\" and are subject to the following terms and\nconditions:\n\n- the Excluded Components are provided on an \"AS IS\" basis\n- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND\nCONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT\nNOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE\nAND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND\nFITNESS FOR A PARTICULAR PURPOSE\n- IBM will not be liable to you or indemnify you for any claims\nrelated to the Excluded Components\n- IBM will not be liable for any direct, indirect, incidental,\nspecial, exemplary, punitive or consequential damages with respect\nto the Excluded Components. \n\nPREREQUISITES\n The prerequisite level for this fix is as follows: \n\n\n- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher (6.2.2-TIV-ITM-FP0002).\n\nAs this fix is cumulative, it can be installed on any fix level for this version, release, and mod level above the prerequisite. \n\nINSTALLATION INSTRUCTIONS\nPlease refer to the full README contained in the Download Description section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat 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] [ ] \nPRODUCT ALIAS/SYNONYM\n KLO\nlog adapter \n\n [/support/docview.wss?uid=swg24043263&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24043263&aid=2]Problems (APARS) fixed\nIV96363, 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"
}
] |
TRAIN_Q067 | 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. | false | [
{
"filename": "swg21451229.txt",
"text": "Title: IBM Rule Team Server/Decision Center is timing out while performing certain operations - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to resolve \"Transaction timed out after 601 seconds\" error while performing certain operations in Rule Team Server (RTS)/Decision Center (DC)? \n\nSYMPTOM\nWhile generating ruleapps in RTS/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes): \n\nOn WebLogic: \n\nRule 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. \n\n... \n\n \n\nOn WebSphere: \nTimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds.\nTimeoutManage 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: \nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyParser.java:511)\n...\n\n\nCAUSE\nThe 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.\n\n\n\nRESOLVING THE PROBLEM\nIf 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. \n\n\nYou will find the property in the file web.xml defined as below:\n...\n<context-param>\n<description>Modify the timeout value that is associated with transactions (in seconds)</description>\n<param-name>ilog.rules.teamserver.transaction.timeout</param-name>\n<param-value>600</param-value>\n</context-param> \n... \n\nAnother 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].\n\n\n\n\n\n\n\nCross 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"
}
] |
TRAIN_Q068 | 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. | false | [
{
"filename": "swg21406783.txt",
"text": "Title: 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\n\nText:\nDatapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n 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.\n\n\n \n\nCross 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"
}
] |
TRAIN_Q069 | 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. | false | [
{
"filename": "swg21632275.txt",
"text": "Title: IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States\n\nText:\nssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nQUESTION\n Why would some outgoing SSL handshakes fail with firmware version 6.0 but not prior firmware versions? \n\nCAUSE\nBeginning 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. \n\nSome 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.\n\nThe TLS versions 1.1 and 1.2 are part of the requirements for being compliant with NIST SP800-131a.\n\n\n\nANSWER\nUpgrade 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. \n\n\nWithin the domain simply navigate to the Objects> Crypto Configuration> Crypto Profile>\nThen simply click on your specific profile to view the Options selection and see what SSL protocol versions are supported.\n\nAny 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."
}
] |
TRAIN_Q070 | 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" | false | [
{
"filename": "swg21982451.txt",
"text": "Title: IBM Search option for a reserved word or character in documents in Atlas - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I search for a string which has reserved words or characters when searching in documents in Atlas? \n\nCAUSE\nThere are specific options to use in oracle when you search for certain strings\n\nANSWER\nWhen there is a \"-\" in a string you are searching for, you need to use \"\\\" in front of the \"-\" \n\nFor example - \"String1-String2\" should be searched as \"String1\\-String2\" \n\nPlease refer to the oracle documentation for Special Characters in Oracle Text Queries"
}
] |
TRAIN_Q071 | 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 | false | [
{
"filename": "swg21962862.txt",
"text": "Title: IBM Verify an IEM server upgrade is still in progress - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I tell if the IBM Endpoint Manager (BigFix) server database upgrade is progressing? \n\nCAUSE\nWhen 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: \n\nOn Windows, the BESAdmin UI will indicate \"Not Responding\" if clicked on at this point. \n\nOn Linux, the message \"Info: Configuring the database for the server component, please wait ... \" is reported.\n\n\nANSWER\nIt 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: \n\nWindows: BESAdmin.exe \n\nLinux: BESAdmin \n\nCPU 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."
}
] |
TRAIN_Q072 | 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 | false | [
{
"filename": "swg1PI34677.txt",
"text": "Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States\n\nText:\n A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http://www-01.ibm.com/support/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications / value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions\n \n \n \n \n \n\nLOCAL FIX\n * 1) open the WAS admin console\n 2) navigate to Resources > Resource environment providers > WP\n ScriptingService > Custom properties\n 3) you should see an entry with the name\n \"ServerExt.applications\" and value\n \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"\n 4) delete this entry, save and restart the server.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 05 (PI31198 [http://www-01.ibm.com/support/docview.wss?uid=swg1PI31198]) for Portal\n 8.5.0.0 available from Fix Central:\n \n http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent\n =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]\n l&platform=All&function=aparId&apars=PI31198\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added a task to remove the outdate resource environment\n provider entry.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI34677\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-02-10\n \n \n * CLOSED DATE\n 2015-03-10\n \n \n * LAST MODIFIED DATE\n 2015-03-10\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * FIXED COMPONENT ID\n 5724E7600\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"
}
] |
TRAIN_Q073 | 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 | false | [
{
"filename": "swg21598779.txt",
"text": "Title: IBM An unexpected ruleset version is executed - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?\nWhat are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ? \n\nCAUSE\nPossible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses\n\n\nANSWER\nFirst 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]. \n\nThe 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. \n\n \n\nA 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: \n\n * 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] \n * 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 \n * 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]. \n * 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. \n * Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully \n * 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. \n * 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] \n * 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] \n\n \n\n\nCross 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"
}
] |
TRAIN_Q074 | Is there a way to not use cache inside a HttpRequest node?
Is there a way in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) to not use cache inside a HttpRequest node? | - | true | [] |
TRAIN_Q075 | 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 | false | [
{
"filename": "swg24044440.txt",
"text": "Title: 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\n\nText:\nSybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects and provides the enhancements listed \nin the \"Problems Fixed\" section below. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2018.\n\n\nAll rights reserved.\n\nComponent: IBM® Tivoli® Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase® Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)\n\nFix Pack: 0002\nComponent ID: 5724B96SO\nDate: December 8, 2017\n\nTable of contents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n1.0 General description\n=======================\nThis fix contains the APARs and defects that are specified in the \"Problems \nfixed\" section. \n\n2.0 Problems fixed\n==================\nThe following problems are addressed by this fix.\n\n2.1 APARs \n----------\nAPAR :IV95149 \nAbstract :While installing Sybase agent \"find / -name ASE-*\" command takes too \nlong on system containing large disk and high volume mounts\nAdditional Information: While installing Sybase agent, prereqchecker invokes the SybaseVersion_plug.sh \nscript which executes the \"find\" command from root for finding Sybase server version.The \"find /\" command takes\na long time on systems with large disks, high volume of mounts. \n\n2.2 Enhancements \n----------------\nRFE :86384 \nAbstract :Monitor availability of the Sybase backup Server, Job Server and \ndatabase job failures. \nAdditional Information: To monitor sybase backup server and job server status two new attributes were \nadded in existing attribute group Server Details.And to monitor failed job in database \ntwo new attribute groups Job Details and Job Summary were added.\n\n\n3.0 Architecture and prerequisites\n===================================\nThis fix is supported on all operating systems listed in Compatibility report website.\nFor information about system requirements, go to the software product\ncompatibility reports website, and search for the ITCAM for Applications\nproduct:\n(http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]).\n\n3.1 Prerequisites for this fix\n-------------------------------\nThe minimum required version of IBM Tivoli Monitoring is V6.2.2 FP2\n\n\n4.0 Image directory contents\n==============================\nElectronic Part Number: ITCAM Apps Ag for Sybase CNN25ML\n\nThe following folder structure of the image is created:\n\n1. Sybase Agent Installer\n-WINDOWS folder: \nThis folder contains the binary files for installing the 32-bit agent.\nThe folder also contains the Prereqchecker utility in the prereqchecker folder\nfor the Sybase agent.\n\n- unix folder:\nThis folder contains the binary files for installing the 32-bit agent on Unix\nplatform. The folder also contains the Prereqchecker utility in the\nprereqchecker folder for the Sybase agent.\n\nThis fix image contains the following files and directories:\nAUTORUN.INF \n[Deploy] \nDeployLnk.sh\nREADME.TXT \n[unix] \nnotices\n[WINDOWS] \ninstall.sh \nkcirunas.cfg\n[license] \nsilent_install.txt \nsilent_config.txt\n\n2. Sybase Support Installer\n-WINDOWS folder: \nThis folder contains the Windows agent support files for the Tivoli Enterprise\nMonitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop\nclient, and Tivoli Enterprise Browser client.\n\n- Unix folder:\nThis folder contains the non-Windows agent support files for the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli\nEnterprise Desktop client, and Tivoli Enterprise Browser client.\n\nThis fix image contains the following files and directories:\nAUTORUN.INF \nDeployLnk.sh \n[WINDOWS] \nREADME.TXT \n[unix] \nnotices\ninstall.sh \nkcirunas.cfg \ntmv630fp6-d5334a-201511302339.appsall.tar\n[license] \nsilent_install.txt \nsilent_config.txt\n\nNote: \nIf you are working in a UNIX environment, use install.sh file to install. \nIf you are working in a Windows environment, you can choose setup.exe \nunder directory [WINDOWS] or [WIA64] according your Windows platform.\n\n\n5.0 Installation instructions\n=============================\n\nWhen this fix pack image is downloaded from the IBM Software Support Web site, \nthese rules apply:\n* You can locally install the fix pack only on a system that already hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases. Similar to other \nupgrade software, the fix pack image also can be locally installed on a \ncomputer where the product software is not already installed.\n* You can populate agents to the depot.\n* You can remotely deploy agents to existing or new installations.\n\nWhen this fix pack image is downloaded from Passport Advantage, these rules \napply:\n* You can locally install the fix pack on a system that already hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases.\n* You can locally install the fix pack on a system that does not already host \na licensed copy of IBM Tivoli Monitoring for Databases.\n* You can populate agents to the depot.\n* You can remotely deploy agents to existing or new installations.\n\n\n5.1 Before installing the fix\n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Upgrade prerequisites \nfor this fix' must be installed when for upgrade.\n\n- For the purpose of this README, the symbol <CANDLEHOME> is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\ibm\\itm'\non Windows systems.\n\n- If you have customized the Monitoring Agent for Sybase Agent \noy.ini file on UNIX system, this file should be backed up before the fix \ninstall. After this fix is installed, edit the latest oy.ini file and merge \nyour modifications into this oy.ini file.\n\n\n5.2 Local agent install and update (including silent installation)\n--------------------------------------------------------------\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to a temporary \ndirectory on the system that contains the agent code to be updated. \nFor the purpose of this README, the symbol <TEMP> represents the fully \nqualified path to this directory.\nNote: On Windows, this includes the drive letter. \n\n2. Expand the archive file using the tar command on UNIX systems or \nan unzip utility on Windows systems. This creates a directory \nstructure that contains fixes for all of the supported platforms.\n\n3. Use the procedures in the \"ITCAM for Applications, Version 7.2.1.2 \nInstallation and Setup Guide\" to install the agent.\n\n4. Use the procedures in the specific database monitoring agent user's\nguide to complete the installation and configuration.\n\n5. After agent upgrade bitness of agent binary should be same as pre-upgrade on x86-64 \nbit windows. Agent do not support upgrade to 64 bit binary.\n\n\n5.3 Remote agent update and installation\n----------------------------------------\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to \na temporary directory on the IBM Tivoli Enterprise \nMonitoring Server system. For the purpose of this README, the \nsymbol <TEMP> represents the fully qualified path to this directory.\nNote: On Windows, this includes the drive letter. \n\n2. Expand the archive file using the tar command on UNIX systems or an \nunzip utility on Windows systems. This creates a directory structure\nthat contains fixes for all of the supported operating systems.\n\n3. To add the fix pack bundles into the remote deploy depot, use the\ntacmd addBundles command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\non the tacmd addBundles command, see Appendix A. Commands reference\nof the \"IBM Tivoli Monitoring Administrator's Guide.\"\n\nOn a UNIX system: if the fix was expanded to \n<TEMP>/CNN25ML:\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/WINDOWS/Deploy -t oy -f\n> $CANDLEHOME/bin/tacmd addBundles -i <TEMP>/CNN25ML/unix -t oy -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot.\n-t is the product code of the product to add, in this case or \nrepresents the Monitoring Agent for Sybase Agent\n-f performs the actions without asking for confirmation\n\nOn a Windows system: if the fix was expanded to \n<TEMP>/CNN25ML:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\CNN25ML\\WINDOWS\\Deploy -t oy -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\CNN25ML\\unix -t oy -f \n\nwhere:\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n-t is the product code of the product to add, in this case oy \nrepresents the Monitoring Agent for Sybase Agent\n-f performs the actions without asking for confirmation\n\n5. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following tacmd commands. For more information on the\ntacmd login and updateAgent commands, see Appendix A. Commands\nreference of the \"IBM Tivoli Monitoring Administrator's Guide.\"\n\nOn a UNIX system: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> $CANDLEHOME/bin/tacmd updateAgent -t oy \n-n <Managed system name>\n-v 062002000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%/bin/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t OY \n-n <Managed system name>\n-v 062002000\n\nIf there are not prior version koy agent on remote system .Then use \nbelow tacmd addSystem command.\n\n> %CANDLE_HOME%\\bin\\tacmd addSystem -t OY \n-n <Managed system name> \n-p INSTANCE=\"<Sybase instance name>\"\n\nNote:\n- The <Sybase instance name> is the Sybase agent instance name to be monitored on \nremote system.\n- The component (-t) for the updateAgent command is specified as \ntwo characters (oy), not three characters (koy).\n- The node (-n) for the updateAgent command is the managed system\nname of the operating system (OS) agent to be updated. The \ntarget node for an updateAgent command is always an OS agent.\n-Remote installation will fail if the MTEMS window is open on the agent machine.\n\n5.4 Agent support update\n------------------------\nUse the following steps to update the Tivoli Enterprise Monitoring \nServer, Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal\nDesktop:\n\n1. Transfer the appropriate archive file (CNN25ML.tar.gz or .iso) to \nthe IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli\nEnterprise Portal Servers or Tivoli Enterprise Portal desktops. \n\n2. Expand the archive file using the tar command on UNIX systems or an \nunzip utility on Windows systems. \n\n3. Use the procedures in the \"ITCAM for Applications, Version 7.2.1.2\nInstallation and Setup Guide.\"\n\n4. Use the procedures in the specific database monitoring agent user's\nguide to complete the installation and configuration.\n\n5. If the Tivoli Enterprise Monitoring Server being updated is remote (not a \nHub Tivoli Enterprise Monitoring Server) then restart the Tivoli Enterprise \nMonitoring Server.\n\n\n\n6.0 Additional installation information\n=======================================\n6.1 Verifying the update\n-------------------------\n1.To verify whether the agent is updated correctly, use the tacmd command to\nview the current version of the agent after the agent is restarted. Ensure that\nyou log on to the Tivoli Enterprise Monitoring Server before you view the agent\nversion.\nFor example,\n\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation\ndirectory, the default location is /opt/IBM/ITM.\n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t OY\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring\ninstallation directory, the default location is C:\\IBM\\ITM.\n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t OY\n\nNote:\nThe component (-t) for the tacmd listSystems command is specified as two\ncharacters (OY), not three characters (KOY).\n\nWhen the agent is updated, the agent version is changed to 06.20.02.00.\nAfter the agent is restarted, you can also use the GUI to verify whether the\nagent was updated. For the agent on Windows systems, the version number is\n06.20.02.00.\n\n2.To verify whether the agent support files are updated correctly, use the\nkincinfo command on Windows systems or the cinfo command on Linux or UNIX\nsystems.\n\nOn UNIX or Linux systems:\nTo validate that all components have been installed, run the following command:\n$CANDLEHOME/bin/cinfo -i\n\nSample output for the cinfo command on a UNIX or Linux systems\n----------------------------------------------------------\n[root@HJS-SYB-1 bin]# ./cinfo\n\n*********** Wed Nov 29 23:53:13 IST 2017 ******************\nUser: root Groups: root\nHost name : HJS-SYB-1 Installer Lvl:06.30.06.00\nCandleHome: /opt/IBM0611/ITM\n***********************************************************\n\n-- CINFO Menu --\n1) Show products installed in this CandleHome\n2) Show which products are currently running\n3) Show configuration settings\n4) Exit CINFO\n1\n\n*********** Wed Nov 29 23:53:15 IST 2017 ******************\nUser: root Groups: root\nHost name : HJS-SYB-1 Installer Lvl:06.30.06.00\nCandleHome: /opt/IBM0611/ITM\n***********************************************************\n...Product inventory\n\nax IBM Tivoli Monitoring Shared Libraries\nlx8266 Version: 06.30.06.00\n\ngs IBM GSKit Security Interface\nlx8266 Version: 08.00.50.36\n\njr Tivoli Enterprise-supplied JRE\nlx8266 Version: 07.09.01.00\n\noy Monitoring Agent for Sybase server\nlx8266 Version: 06.20.02.00\n\nui Tivoli Enterprise Services User Interface\n\nOn Windows systems:\nTo validate that all components have been installed, run the following command:\n%CANDLE_HOME%\\bin\\kincinfo –i\n\nSample output of the kincinfo command on a Windows System\n----------------------------------------------------------\nC:\\IBM\\ITM\\BIN>kincinfo -i\n********** Thursday, November 30, 2017 10:10:02 AM **********\nUser : Administrator Group : NA\nHost Name : HJ-IBMIBM6737 Installer : Ver: 063006000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\n\nIN Install INS/Windows Install Component\nWINNT Version: 06.30.06.00 Build: 201511302132\n\nIN TEMA(32-bit) INS/ITM 6.x Agent Install Component\nWINNT Version: 06.30.06.00 Build: 201511302132\n\nIN TEMA(64-bit) INS/ITM 6.x Agent Install Component Extensions\nWINNT Version: 06.30.06.00 Build: 201511302132\n\nAC KAC(64-bit) CMA/32/64 Bit Agent Compatibility Package\nWIX64 Version: 06.30.06.00 Build: 201511302132\n\nGL KGL(64-bit) CMA/Tivoli Enterprise Monitoring Agent Framework\nWIX64 Version: 06.30.06.00 Build: d5334a\n\nGL KGL(32-bit) CMA/Tivoli Enterprise Monitoring Agent Framework\nWINNT Version: 06.30.06.00 Build: d5334a\n\nGS KGS(64-bit) GSK/IBM GSKit Security Interface\nWIX64 Version: 08.00.50.36 Build: d5313a\n\nGS KGS(32-bit) GSK/IBM GSKit Security Interface\nWINNT Version: 08.00.50.36 Build: d5313a\n\nJM KJM(32-bit) JVM/Embedded JVM\nWINNT Version: 07.09.01.00 Build: 201506221629\n\nNT KNT(32-bit) CMA/Monitoring Agent for Windows OS\nWINNT Version: 06.30.00.00 Build: 30321\n\nOY KOY(32-bit) CMA/Monitoring Agent for Sybase Server\nWINNT Version: 06.20.02.00 Build: 72651\n\nUE KUE(32-bit) CMA/Tivoli Enterprise Services User Interface Extensions\nWINNT Version: 06.30.06.00 Build: d5334a\n\nUI KUI(32-bit) CLI/Tivoli Enterprise Services User Interface\nWINNT Version: 06.30.06.00 Build: 201511302132\n\n\n7.0 Known problems and workarounds\n==================================\nProblem: Sybase agent configuration is not working using itmcmd manage \ncommand from GUI on Solaris 11\nWorkaround:\nFor Solaris 11:\nRun './itmcmd config -A oy' present at location:<CandleHome>/bin\n\nProblem: Prereqchecker which is integrated with the installer fails on \nwindows platform.\nWorkaround: \nFor Windows:\nRun on command prompt ‘prereq_checker.bat KOY’ present at location:\nInstallerPath\\Sybase_Agent_Installer\\WINDOWS\\prereqchecker\n\nFor Unix:\nRun ‘./prereq_checker.sh KOY’ present at location:\nInstallerPath\\Sybase_Agent_Installer\\unix\\prereqchecker\n\nProblem: Registry entries are not cleared when agent is uninstalled on 64 bit\nwindows platform.\nWorkaround: Delete registry entries manually from path:\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Candle\\KOY\\610\\\n\nProblem: When running the verification step in the \"itmcmd config -A oy\"\nfunction on a Solaris 10 system, the following output from the verification\nprogram is produced: \"user needs read authority to\".\nWorkaround: Issue \"ps -ef | grep koyagent\" to locate the koyagent process and\nissue \"kill -9\" for that process. Check the Navigator tree in the Tivoli\nEnterprise Portal for an offline koyagent entry and clear the offline entry.\nThe Monitoring Agent for Sybase Server that was configured by \"itmcmd config\" \nis unaffected by this problem. \n\nProblem: When running multiple remote deploys and agent upgrades, a task\ntimeout occurs during either the remote deployment or the agent upgrade. \nWorkaround: Restart the OS Agent following the task timeout and before\nperforming the next remote deployment or agent upgrade.\n\nProblem: If you are installing this fix into a depot on a Windows computer, and\nWinZip(R) is used to extract this fix, text files in the depot might contain\nCTRL-Ms. When this fix is remotely deployed to a UNIX machine from the Tivoli\nEnterprise Monitoring Server or depot on Windows, the installation fails. The\nCTRL-Ms are caused by extracting the fix using WinZip with \"TAR file smart\nCR/LF conversion\" option enabled. This extraction causes WinZip to put CTRL-Ms\nin text files when they are extracted on UNIX through remote deployment. \nWorkaround: If you are using WinZip for the fix installation for the Tivoli\nEnterprise Monitoring Server on Windows, disable the default \"TAR file smart\nCR/LF conversion\" option. \n\nProblem: In the Tivoli Enterprise Portal, the instance name is displayed\ninstead of the host name in the Navigation tree. \nFor example the Navigation tree might look like this,\nMySid\nSybase\nAlert Log\n...\ninstead of this,\nMyHost\nSybase - MySid\nAlert Log\n...\n\nThe problem is that the length of the managed node name, <SID>:<HOSTNAME>:SYB,\nexceeds the length supported by the portal. A possible cause is that the\nfully-qualified host name is being used. If 'uname -n' on the Monitoring Agent\nfor Sybase Server computer returns a fully-qualified host name, then this host\nname is the cause. \nWorkaround: Override the host name with an appropriate shorter name by adding\nthe following line to oy.config: \nexport COLL_HOSTNAME=<short name>\n\n\n8.0 Additional product information \n==================================\nSteps for enabling SDA (Self-describing agent)\nFor Windows:\n1.On the computer where the monitoring server is installed, in the Manage\nTivoli Enterprise Monitoring Services application, right-click the agent and \nselect Advanced→ Edit ENV file.\n2.Edit the existing environment variable to: TEMA_SDA=Y.\n\nFor UNIX:\n1.On the computer where the monitoring agent is installed, change to the\n<Install_dir>/config/ directory.\n2.Open the coordinating file:\nFor single-instance agents: <pc>.ini \nFor multi-instance agents: <pc>_<instance>.ini file \nWhere pc is the two-character product code.\n3.Edit the existing environment variable to: TEMA_SDA=Y.\n\n\n9.0 Copyright and trademark information \n========================================\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of\nInternational Business Machines Corp., registered in many jurisdictions\nworldwide. Other product and service names might be trademarks of IBM or other\ncompanies. A current list of IBM trademarks is available on the Web at\n\"Copyright and trademark information\" at ww.ibm.com/legal/copytrade.shtml.\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks of\nMicrosoft Corporation in the United States, other countries, or both. Java and\nall Java-based trademarks are trademarks of Sun Microsystems, Inc. in the\nUnited States, other countries, or both. UNIX is a registered trademark of The\nOpen Group in the United States and other countries. Linux is a registered\ntrademark of Linus Torvalds in the United States, other countries, or both.\nOther company, product, or service names may be trademarks or service marks of \nothers.\n\n\n10.0 Notices\n==================\nThis information was developed for products and services offered in the United\nStates. IBM may not offer the products, services, or features discussed in this\ndocument in other countries. Consult your local IBM representative for\ninformation on the products and services currently available in your area. Any\nreference to an IBM product, program, or service is not intended to state or\nimply that only that IBM product, program, or service may be used. Any\nfunctionally equivalent product, program, or service that does not infringe any\nIBM intellectual property right may be used instead. However, it is the user's\nresponsibility to evaluate and verify the operation of any non-IBM product,\nprogram, or service.\nIBM may have patents or pending patent applications covering subject matter\ndescribed in this document. The furnishing of this document does not grant you\nany license to these patents. You can send license inquiries, in writing, to:\nIBM Director of Licensing\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\nThe following paragraph does not apply to the United Kingdom or any other\ncountry where such provisions are inconsistent with local law:\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \"AS IS\"\nWITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR\nFITNESS FOR A PARTICULAR PURPOSE.\nSome states do not allow disclaimer of express or implied warranties in certain\ntransactions, therefore, this statement may not apply to you.\n\nINSTALLATION INSTRUCTIONS\nSybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.\n\n\nURL LANGUAGE SIZE(Bytes) 6.2.0-TIV-ITM_SYB-FP0002 (CNN25ML) [https://w3-03.ibm.com/software/xl/download/ticket.wss] English 1722240862 \nDOWNLOAD PACKAGE\nSybase Server Agent 620 FP2 installer can be downloaded from IBM passport advantage using part number CNN25ML.\n\nIBM Tivoli Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) (CNN25ML) \n\n\n\nPRODUCT ALIAS/SYNONYM\n OY\nKOY\nSybase Agent \n\n [/support/docview.wss?uid=swg24044440&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044440&aid=2]Problems (APARS) fixed\nIV95149"
}
] |
TRAIN_Q076 | 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) | false | [
{
"filename": "swg22014367.txt",
"text": "Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n 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 \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: 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.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/131047 [https://exchange.xforce.ibmcloud.com/vulnerabilities/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION/FIXES\nFor MQ 5.3 \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * 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\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q077 | Why is the test suite execution failing from Decision Center?
When executing a test suite from Decision Center the run may fail with an error message similar to:
XU client error.
GBRXU0448E: Plugin error.
Unable to retrieve the engine manager.
The parsing of the ruleset failed Problem occurred loading translation: Error when translating parameter "inputParameter": Cannot translate class "sample.InputParameter".
What can be causing this error? | - | true | [] |
TRAIN_Q078 | Daylight Saving Time changes effect on CICS TS
How does the Daylight Saving Time (DST) time change affect CICS Transaction Server for z/OS and z/VSE (CICS TS)? I would like to know when DST begins and ends in my country, and if there are any actions that I will need to take for CICS when the time changes. | - | true | [] |
TRAIN_Q079 | How can I force the Websphere 6.1 JVM to pick only a specific jdbc jar?
We are running WAS 6.1. We have multiple jvms in a cell and only one of them needs to use a new version of the DB2 client. We have an application deployed onto this jvm and this application needs to use two different version of DB2 jdbc jars. One part of the application is configured to use the old jars and the other part needs to use the new jars. Is there a way to configure the jvm such that the second part of the application always picks up the latest jars? | - | true | [] |
TRAIN_Q080 | 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 | false | [
{
"filename": "swg22010832.txt",
"text": "Title: 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\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n 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 \n\nCONTENT\nIBM 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\nRemediation: \n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB HVE IIB HVE"
}
] |
TRAIN_Q081 | '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. | false | [
{
"filename": "swg24042387.txt",
"text": "Title: IBM Content Collector V4.0.1 Fix Pack 3 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This document contains links to the download page for IBM Content Collector V4.0.1 Fix Pack 3 \n\nDOWNLOAD DESCRIPTION\n \n\nIBM CONTENT COLLECTOR DOWNLOADS\n * All versions [http://www.ibm.com/support/docview.wss?uid=swg27040223] \n * Version 4.0.1 Fix Pack 3- selected tab, \n\n\nApply 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. \n\nBelow is the list of the problems that were fixed in this fix pack.\n\n\nAPAR 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\nIBM Content Collector V4.0.1 Fix Pack 3 can be used with the following IBM Content Collector version: \n\nURL LANGUAGE SIZE(Bytes) Prerequisites for IBM Content Collector V4.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27042658] English 1 \nINSTALLATION INSTRUCTIONS\nRead the fix pack readme files for specific information about installing the fix pack packages.\n\nURL 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 \nDOWNLOAD PACKAGE\nThe IBM Content Collector V4.0.1 Fix Pack 3 download package consists of the following files: \n\n * 4.0.1.3-IBM-ICC-FP003.pdf: Readme file \n * 4.0.1.3-IBM-ICC-Server-FP003.zip \n * 4.0.1.3-IBM-ICC-OWA-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-SOLARIS-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-Linuxz-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Solaris-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-CM8Text-Linuxz-FP003.tar.gz\n\nHOW CRITICAL IS THIS FIX?\nThis 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. \n\nFor further information see the Readme File for IBM Content Collector V4.0.1 Fix Pack 3\n\n\n\n [/support/docview.wss?uid=swg24042387&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24042387&aid=2]Problems (APARS) fixed\nHE12445 HE12488 HE12491 HE12436 HE12490 HE12513 HE12526 HE12529 HE12537"
}
] |
TRAIN_Q082 | 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. | false | [
{
"filename": "swg21902778.txt",
"text": "Title: IBM Security Network Protection firmware 5.3.1 release notes - United States\n\nText:\nrelease notes; readme; firmware; xgs FIX README\n\nABSTRACT\n 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. \n\nCONTENT\nServiceability and support enhancements: \n\n * 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).\n 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.\n \n * 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 \n * Packet Capture \n * Local Management Interface (LMI) \n * License and Update (LUM) \n * SiteProtector Communication\n \n \n \n * 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. \n \n * 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. \n 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]\n\n\nResponse enhancement: * Forwarded events (Remote Syslog Alert Responses) will show the same details as the content sent to SiteProtector. \n * Support for using the TCP protocol when creating Remote Syslog Alert Responses to prevent messages being truncated and improve delivery reliability over using UDP.\n\n\nNetwork 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.\n\n\nIPS 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.\n \n * 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.\n\n\nPerformance: * Inspection throughput increase for XGS 7100 up to 25Gbps, FPL5 (25Gbps) added.\n\n\nMiscellaneous 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. \n \n * We have removed the MultiCast Domain Name System (mDNS), under some configurations it caused security risks within the appliance.\n \n * Support for mutual certificate authentication for communication between the Network Security appliance and SiteProtector.\n\n\nKnown issues: \nYou 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]. \n\n\n\n\n[/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] \nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21903740]"
}
] |
TRAIN_Q083 | 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. | false | [
{
"filename": "swg21634612.txt",
"text": "Title: IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States\n\nText:\nisolate this resource provider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer has defined 3 Oracle JDBC Providers at cell, node and server\nscope. Client have following configuration in websphere JDBC provider. \n\nIn Cell Scope - C:\\jdbc\\ojdbc5\\ojdbc5.jar \n\nIn Node Scope - C:\\jdbc\\ojdbc6_g\\ojdbc6_g.jar \n\nIn Server Scope- C:\\jdbc\\ojdbc6\\ojdbc6.jar \n\nIn 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 \n\"C:\\jdbc\\ojdbc6\\ojdbc6.jar\" should be loaded first but instated, ojdbc5.jar was load first\n\n[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass \n\noracle.jdbc.driver.OracleDriver \n\nloader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9 \n\nsource=file:/C:/jdbc/ojdbc5/ojdbc5.jar Exit \n\n\n\n\n\n\nSYMPTOM\nDue to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.\n\n\nCAUSE\nWhen 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. \n\nRESOLVING THE PROBLEM\n 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. \n\n\nGo 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. \n\n \n\nHere are links to Knowledge Center articles which contain further information on the setting: \n\n\nJDBC provider settings [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/udat_manjdbcprodet.html]\n\nConsiderations for isolated resource providers [https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.0/com.ibm.websphere.nd.multiplatform.doc/ae/rdat_isolatedlimitations.html]"
}
] |
TRAIN_Q084 | 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) | false | [
{
"filename": "swg22012983.txt",
"text": "Title: 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\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the queue manager's amqrmppa channel process, terminating it. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2018-1371 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1371]\nDESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/137771 [https://exchange.xforce.ibmcloud.com/vulnerabilities/137771] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8.0 \n\n * Maintenance level 8.0.0.8\n\n\nIBM MQ V9 LTS * Maintenance level 9.0.0.2\n\n\nIBM MQ V9 CD * IBM MQ version 9.0.4\n\nREMEDIATION/FIXES\nIBM MQ V8.0 \n\nApply FixPack 8.0.0.9 [http://www-01.ibm.com/support/docview.wss?uid=swg22015103] \nIBM MQ V9 LTS * Apply FixPack 9.0.0.3 [http://www-01.ibm.com/support/docview.wss?uid=swg24044508]\n\n\nIBM MQ V9 CD * Upgrade to 9.0.5 [http://www-01.ibm.com/support/docview.wss?uid=swg24043463]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] \n\nCHANGE HISTORY\n 01 Feb 2018: Original Version published\n13 April 2018: Added 9.0.5, 9.0.0.3 and 8.0.0.9 FixPack details \n\n*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. \n\nDISCLAIMER\nAccording 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. \n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers"
}
] |
TRAIN_Q085 | 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. | false | [
{
"filename": "swg21366662.txt",
"text": "Title: IBM How to change Siebel connection settings using the siebel.properties file in WebSphere Adapter for Siebel eBusiness Applications - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n 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. \n\nANSWER\nSiebel 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.\nCreate 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.\n\nThis is applicable for all supported brokers.\n\nA detailed description of the Siebel.properties file is given below:\n\nSiebel.properties File \n\nThe 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. \n\nThe table below shows the properties in the siebel.properties file. \n\n[/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\n\n\n\nsiebel.conmgr.virtualhosts Indicates the usage of Java Cryptography Extension. 1 for jce usage and 0 for no usage.\n\nA listing of virtual servers representing a group of like servers that perform the same function, for example, call center functions.\n\nAn incoming login for the call center Virtual Server will try servers from the list in a round-robin fashion.\n\nAn example of such a list follows:\n\nVirtualServer1=sid1:host:port,sid2:host:port...;VirtualServer2=...\n\nwhere:\n\nVirtual 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. \n\nThe following is a sample siebel.properties file: \n\nsiebel.connection.string = siebel.tcpip.rsa.none://test.siebel.com/siebel/sseobjmgr_enu/test \n\nsiebel.conmgr.txtimeout = 3600 \n\nsiebel.conmgr.poolsize = 5 \n\nsiebel.conmgr.sesstimeout = 300000 \n\nsiebel.properties [/support/docview.wss?uid=swg21366662&aid=3] [/support/docview.wss?uid=swg21366662&aid=2]"
}
] |
TRAIN_Q086 | I can't find the JDBC driver for my DB2.
I am running BPM 8.0.1 with DB2 10.1.0.
Reading this technote:
http://www-01.ibm.com/support/docview.wss
"Use the JDBC driver of your database product instead of the JDBC delivered with IBM Business Process Manager (BPM)"I am trying to download the latest JDBC driver from the following technote:
http://www-01.ibm.com/support/docview.wss
It looks like the link for the JDBC driver download for DB2 10.1.0 is greyed out. Where can I download this driver? | - | true | [] |
TRAIN_Q087 | 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: | false | [
{
"filename": "swg21631478.txt",
"text": "Title: IBM Required gtk libraries for IBM Installation Manager on AIX - United States\n\nText:\ngtk; motif TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Installation Manager requires gtk libraries to support the graphical user interface (GUI). \n\nSYMPTOM\nInstallation Manager reports errors when the gtk libraries are not installed. \n\nExamples of the reported errors:\n\n\n * SWT library could not be loaded:\n\n\n\n# ./install\n00:00.92 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged\nCould not load SWT library. Reasons:\n/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.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n/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.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n/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.)\nswt-pi-gtk (Not found in java.library.path)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n/root/.swt/lib/aix/ppc/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)\nat org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)\nat java.lang.J9VMInternals.initializeImpl(Native Method)\n...\nThe displayed failed to initialize. See the log /root/Desktop/InstallationManager/configuration/1361168761043.log for details. \n * Segmentation error occurs when the gtk libraries are installed but are not at the required versions\n\n\n\nUnhandled exception\nType=Segmentation error vmState=0x00040000\nJ9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033\nHandler1=F0739208 Handler2=F05F5F1C\nR0=D3D9FDCC R1=3013EEF0 R2=F077B69C R3=F0779450\nR4=00000000 R5=00000000 R6=00000000 R7=00000000\nR8=1220000F R9=1220000F R10=F0687A0C R11=000034E0\nR12=03222C60 R13=30C7DD00 R14=31FAA028 R15=F05851EC\nR16=00000007 R17=00000000 R18=F073B388 R19=30C7DD50\nR20=32935C30 R21=31FAA040 R22=00000000 R23=30000BC8\nR24=10010E04 R25=F05F7130 R26=30148364 R27=0000007E\nR28=CFACCBB8 R29=F073AB7C R30=D3DC1410 R31=F0779430\nIAR=D3DB63A8 LR=D3D9FDE8 MSR=0000D032 CTR=D3DE0E70\nCR=22004084 FPSCR=82000000 XER=0000001B TID=00000000\nMQ=00000000\nFPR0 329d3fd000000110 (f: 272.000000, d: 6.943460e-65)\nFPR1 41e0000000000000 (f: 0.000000, d: 2.147484e+09)\nFPR2 c1e0000000000000 (f: 0.000000, d: -2.147484e+09)\nFPR3 4330000001e00000 (f: 31457280.000000, d: 4.503600e+15)\nFPR4 4330080000000000 (f: 0.000000, d: 4.512396e+15)\nFPR5 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR6 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR7 4330080000138518 (f: 1279256.000000, d: 4.512396e+15)\nFPR8 005f0031002e0034 (f: 3014708.000000, d: 6.897895e-307)\nFPR9 002e0038002e0076 (f: 3014774.000000, d: 8.344265e-308)\nFPR10 0032003000310033 (f: 3211315.000000, d: 1.001324e-307)\nFPR11 0030003200320035 (f: 3276853.000000, d: 8.900720e-308)\nFPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)\nFPR13 4028000000000000 (f: 0.000000, d: 1.200000e+01)\nFPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nTarget=2_40_20110203_074623 (AIX 7.1)\nCPU=ppc (8 logical CPUs) (0xc0000000 RAM)\n----------- Stack Backtrace -----------\n(0xD3D9F81C)\n(0xD43D5E48)\n(0xD43D8698)\n(0xD43D1D38)\n(0xD43D1B24)\n(0xD3E4ABA0)\n(0xD43D3058)\n(0xD43D3200)\n(0xD0F0ED18)\n(0xD0F1536C)\n(0xD0F19438)\n(0xD2B1DF48)\n(0xD2AE7780)\n(0xD2AE7A30)\n(0xD1516BAC)\n(0xD2AE78E4)\n(0xD2AE7E24)\n(0xD2AEC6C4)\n(0x100013C0)\n(0xD04FCD88)\n---------------------------------------\nJVMDUMP006I Processing dump event \"gpf\", detail \"\" - please wait.\nJVMDUMP032I JVM requested System dump using '/opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp' in response to an event\nNote: \"Enable full CORE dump\" in smit is set to FALSE and as a result there will be limited threading information in core file.\nJVMDUMP010I System dump written to /opt/IBM/InstallationManager/eclipse/core.YYYY0318.095945.7798784.0001.dmp\nJVMDUMP032I JVM requested Java dump using '/opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt' in response to an event\nJVMDUMP010I Java dump written to /opt/IBM/InstallationManager/eclipse/javacore.YYYY0318.095945.7798784.0002.txt\nJVMDUMP032I JVM requested Snap dump using '/opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc' in response to an event\nJVMDUMP010I Snap dump written to /opt/IBM/InstallationManager/eclipse/Snap.YYYY0318.095945.7798784.0003.trc\nJVMDUMP013I Processed dump event \"gpf\", detail \"\".\nSegmentation fault (core dumped)\n\nCAUSE\nInstallation 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. \n\nYou 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.\n\n\nRESOLVING THE PROBLEM\nTo use the GUI, the gtk+ RPM and dependencies must be available on AIX. \n\n\nInstall this set of RPMs on AIX:\n\n\natk-1.12.3-2.aix5.2.ppc.rpm\ncairo-1.8.8-1.aix5.2.ppc.rpm\nexpat-2.0.1-1.aix5.2.ppc.rpm\nfontconfig-2.4.2-1.aix5.2.ppc.rpm\nfreetype2-2.3.9-1.aix5.2.ppc.rpm\ngettext-0.10.40-6.aix5.1.ppc.rpm\nglib2-2.12.4-2.aix5.2.ppc.rpm\ngtk2-2.10.6-4.aix5.2.ppc.rpm\nlibjpeg-6b-6.aix5.1.ppc.rpm\nlibpng-1.2.32-2.aix5.2.ppc.rpm\nlibtiff-3.8.2-1.aix5.2.ppc.rpm\npango-1.14.5-4.aix5.2.ppc.rpm\npixman-0.12.0-3.aix5.2.ppc.rpm\nxcursor-1.1.7-3.aix5.2.ppc.rpm\nxft-2.1.6-5.aix5.1.ppc.rpm\nxrender-0.9.1-3.aix5.2.ppc.rpm\nzlib-1.2.3-3.aix5.1.ppc.rpm\n\nThe installed RPMs must be of the minimum versions listed above.\n\nTo install the RPM versions specified above take the following steps: \n\n\n 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. \n \n \n 2. Decompress the tar file. \n You can use the command tar -xvf gtk2_bundle_<version>.tar to decompress the file.\n \n \n 3. Open the decompressed directory gtk2_bundle_<version> and run the install.sh script.\n \n 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.\n \n \n 4. Verify the environment variable LIBPATH contains a path to the installed libraries. \n For example LIBPATH=/opt/freeware/lib/\n\n\nNote 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 \n\nRELATED INFORMATION\n#Unreadable characters in the GUI when using X11 [http://www.ibm.com/support/docview.wss?uid=swg21661861]"
}
] |
TRAIN_Q088 | Help with Action required for SOA Policy Gateway Pattern For Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235)
I need to understand details regarding "Action required for SOA Policy Gateway Pattern For Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235)". This vulnerability that has been referred to as “GHOST”.
Where can I find this information? | - | true | [] |
TRAIN_Q089 | 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) | false | [
{
"filename": "swg21965955.txt",
"text": "Title: 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\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n 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. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2015-2613 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2613]\nDESCRIPTION:An unspecified vulnerability and Java SE Embedded related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104734 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104734]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)\n\nCVEID:CVE-2015-2601 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2601]\nDESCRIPTION:An unspecified vulnerability related to the JCE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104733 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104733]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:P/I:N/A:N)\nCVEID:CVE-2015-4749 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4749]\nDESCRIPTION:An unspecified vulnerability related to the JNDI component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104740 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104740]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:N/A:P)\n\nCVEID:CVE-2015-2625 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2625]\nDESCRIPTION:An unspecified vulnerability related to the JSSE component could allow a remote attacker to obtain sensitive information.\nCVSS Base Score: 2.6\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/104743 [https://exchange.xforce.ibmcloud.com/vulnerabilities/104743]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:N/A:N)\n\nCVEID:CVE-2015-1931 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1931]\nDESCRIPTION: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.\nCVSS Base Score: 2.1\nCVSS Temporal Score: Seehttp://xforce.iss.net/xforce/xfdb/102967 [http://xforce.iss.net/xforce/xfdb/102967]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Enterprise Service Bus 6.2\nWebSphere Enterprise Service Bus 7.0\nWebSphere Enterprise Service Bus 7.5\n\nREMEDIATION/FIXES\nPlease 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.\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/PSIRT] CHANGE HISTORY\n 4th September 2015: Original version published \n\n*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. \n\nDISCLAIMER\nAccording 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."
}
] |
TRAIN_Q090 | 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. | false | [
{
"filename": "swg24044840.txt",
"text": "Title: IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.13-TIV-ITM_SQL-IF0001 - United States\n\nText:\nITM; SQL; ITCAM; Microsoft Applications DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2018. \n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:\nMicrosoft(R) SQL Server Agent, Version 6.3.1.13\n\nComponent ID: 5724B96MO\n\nInterim Fix 0001, (6.3.1.13-TIV-ITM_SQL-IF0001)\n\nDate: May 14, 2018\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Notices\n\n\n1.0 General description\n=======================\nThis fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below. \n\n2.0 Problems fixed\n==================\n2.1 APARS:\n-------------------\nAPAR: IJ00433\nAbstract: The collector process is crashing while accessing invalid\nparameter of the request. \nAdditional Information: Customized SQL query result attribute group\n(KOQCSQLR) request uses 3 parameters & other attribute groups use 2\nparameters. The memory for the third parameter was not handled properly.\nAnd accessing this parameter by other attribute group would result\ninto crash.\n\nAPAR: IJ00815\nAbstract: Device Detail attribute AUTOGROWTH behaviour not in sync\nwith SQL Server. \nAdditional Information: In case when data file autogrowth was disabled\nand max-size was set to unlimited, then the incorrect values were\ndisplayed for filegroup detail attribute(Max Growth Size) and device\ndetail attribute(Growth).\n\nAPAR: IJ01540\nAbstract: False alerts are being generated as default value \"Not\nCollected\" for \"Database Space Pct Used\" attribute is not correctly\nconverted before sending to TEPS.\nAdditional Information: Situations having default value\n[ Not Collected (-1 ) ] in formula were not getting evaluated correctly\nfor some database detail attributes. However, the data was shown\ncorrectly as ‘Not Collected’ on the portal.\n\nAPAR: IJ05451 \nAbstract: ITCAM SQL Server Agent's collector process crashes when using\nSQL Server Native Client 10.0 or SQL Server Native Client 11.0 as\nODBC driver.\nAdditional Information: Collector was not able to handle all possible values\nreturned by ODBC when using SQL Server Native Client 10.0 and SQL Server\nNative Client 11.0 causing it to crash.\n\n2.2 DEFECTS:\n-----------------\nDEFECT: 170986\nAbstract: Memory leak in Table Detail attribute group. \nAdditional Information: Memory leak observed in Table Detail attribute\ngroup because incorrect de-allocation handling. \n\nDEFECT: 170987\nAbstract: Crash observed in Availability group details attribute group\nand Table detail attribute group\nAdditional Information: Crash observed in Availability group details\nattribute group and in Table detail attribute group for the wrong\nusage of iterator after erase. Issue happened because an attempt to\nincrement the iterator was made after the iterator was deleted through\nerase function. \n\nDEFECT: 170993\nAbstract: intial size > max size gives incorrect values\nAdditional Information: If a database was created with restricted growth\nand then modifed the initial size of the database file to a value\ngreater than it's maxsize, then the value of maxsize was not updated\ncorrectly (ideally in this case maxsize should become equal to initial\nsize). As a result, query to SQL Server returned false value for\nmaxsize due to which incorrect values were getting displayed on portal\nfor attributes in Database Detail, Device Detail and Filegroup Detail\nattribute groups.\n\nDEFECT: 170994\nAbstract: Incorrect value displayed for Database Detail attributes\nwhen autogrowth disabled and data freespace > drive freespace.\nAdditional Information: In cases when data file autogrowth was disabled\nand data freespace was greater than device freespace then incorrect\nvalue were seen for some attributes(Data Freespace , Aggregate Database\nFreespace , Database Space pct used , Aggregate Database Freespace pct,\nDatabase max growth size). \n\nDEFECT: 171127\nAbstract: Add tolerance support for SQL Server 2017.\nAdditional Information: Added support for SQL Server 2017 version.\n\nDEFECT: 171244\nAbstract: Spelling mistake in agent configuration panel.\nAdditional Information: Few spelling mistakes in agent configuration\npanel were corrected.\n\nDEFECT: 171318\nAbstract: Usage of KOQ_ODBC_DRIVER variable in pre-req while making\nsql server connection.\nAdditional Information: During pre-requisite check, the value of\n‘Driver’ was hardcoded to ‘SQL Server‘. While later on, for collecting\ndata value for 'Driver’ was picked from ‘KOQ_ODBC_DRIVER’ variable.\nDue to this, issue was seen during pre-requiste connection but later\non data was being collected successfully.\n\nDEFECT: 171379\nAbstract: High Severity vulnerabilities are resolved to avoid undefined\nbehaviour of the agent.\nAdditional Information: Removed the high severity errors in the code,\ndetected in CPPCheck tool.\n\nDEFECT: 171785\nAbstract: DBD_TEMP rename failed with error [32]\nAdditional Information: Renaming of DBD_TEMP to DBD_PREV files was\nfailing with Error 32 (The process cannot access the file because it\nis being used by another process)because DBD_TEMP file handle was\ntaking time to close. \n\nDEFECT: 171979\nAbstract: Incorrect value is being sent when query is failed in SRV1\ncursor.\nAdditional Information: Zero value was being sent when query fails in\nSRV1 cursor which was incorrect. Zero is a meaningful value which does\nnot indicate failure.\n\nDEFECT: 171981\nAbstract: Not Collected value is frequently sent since database\ndetail collection is not getting completed in 45 seconds.\nAdditional Information: When database detail collection took more\nthan 45 seconds for collection, Not collected values were sent which\nresulted into triggering of situation.\n\nDEFECT: 172173\nAbstract: Environment setting for COLL_DBCC_NO_LOCK was not taking\neffect. Similar issue was seen with COLL_MONITOR_ALL_DATABASES.\nAdditional Information: Values were getting overwritten for above two\nvariables, hence queries were running without NoLock hint and monitoring\nof all database setting was not working as expected.\n\nDEFECT: 173699\nAbstract: No data get collected for server summary attribute group.\nAdditional Information: SRV3,one of the pre-cursor of server summary\nattribute group, was failing as its query was executed with (null)\noption. Hence no data was collected for server summary attribute group.\n\nDEFECT: 174076\nAbstract: MSSQLQA: Sometime server detail data is not getting displayed\non portal.\nAdditional Information: SRV3, one of the pre-cursor of server summary\nattribute group, was failing as its query was executed with (null)\noption. Hence sometimes server detail data was not getting displayed\non portal.\n\nDEFECT: 174077\nAbstract: crypted SQL password in log file.\nAdditional Information: Encrypted password value in logfile is \nreplaced with fixed length string to avoid security breach.\n\nDEFECT: 174420\nAbstract: Last Statistics Query execution failing for table details\nattribute group.\nAdditional Information: Due to query failure,table detail data was\ncollected only for the first time. From second collection onwards,\nnew data was not collected & portal always showed the data collected\nduring first collection.\n\nDEFECT: 175117\nAbstract: Table detail attribute group query was failing for syntax error\nat where clause and returned null\nAdditional Information: The query which gets executed while include/exclude\ndatabases is on, was containing two consecutive \"where\" and hence \nwas failing. This issue is seen with SQL Server 2014 and above versions. \n\nDEFECT: 175120\nAbstract: Data is not collected properly with the non default SQL\nODBC driver.\nAdditional Information: Due to incorrect size calculated for some\ndata types, either query’s result set processing was failing or the\ndata was getting truncated. As a result data was not getting collected\nproperly for some attributes.\n\n2.3 Enhancements:\n-----------------\nRFE: 50594\nAbstract: Support AlwaysOn feature for SQL developers edition.\nAdditional Information: Added support for SQL Server Developers\nEdition's AlwaysOn feature.\n\n2.4 Superseded fixes\n--------------------\nNone\n\n2.5 APARs and defects included from superseded fixes\n----------------------------------------------------\nNone\n\n3.0 Architecture and prerequisites\n==================================\nThis fix is supported on all operating systems listed in the \nIBM Tivoli Monitoring: Microsoft SQL Server agent prerequisites Document,\nversion 6.3.1 or from the following link:\nhttp://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]\n\n\nThe following link is for the Tivoli operating system and application\nsupport matrix. Please refer to this matrix for the latest \ncertification information.\n\nhttp://www-969.ibm.com/software/reports/compatibility/clarity/index.html [http://www-969.ibm.com/software/reports/compatibility/clarity/index.html]\n\n3.1 Prerequisites for this fix\n------------------------------\nThe prerequisite level for this fix is as follows:\n\nLocal Agent Upgrade: \n- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.13 \n\nRemote Agent Upgrade:\n- IBM Tivoli Monitoring, Version V6.23 Fix Pack 3 with OS Support\n- ITCAMMA: Monitoring Agent for Microsoft SQL Server, Version 6.3.1.13 \n- Monitoring Agent for Windows OS, Version V6.23 Fix Pack 3\n\nAs this fix is cumulative, it can be installed on any fix level\nfor this version, release and mod level above the prerequisite.\n\n\n4.0 Image directory contents\n============================\nThis fix image contains the following files:\n\n- 6.3.1.13-TIV-ITM_SQL-IF0001.README - This is the README file\n- 6.3.1.13-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format\n- 6.3.1.13-TIV-ITM_SQL-IF0001.zip - Fix archive .zip format\n\nNote: The .tar and .zip files are identical in content. Use the .tar\nfile if you are working in a UNIX(R) environment; use the .zip file\nif you are working in a Windows(R) environment.\n\nThe fix archive file contains the following files:\n6.3.1.13-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar\n6.3.1.13-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip\n6.3.1.13-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab\n6.3.1.13-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab\n6.3.1.13-TIV-ITM_SQL-IF0001/KOQWINNT.dsc\n6.3.1.13-TIV-ITM_SQL-IF0001/KOQWIX64.dsc\n6.3.1.13-TIV-ITM_SQL-IF0001/oq_dd.properties\n6.3.1.13-TIV-ITM_SQL-IF0001/oq_dd_063113001.xml\n6.3.1.13-TIV-ITM_SQL-IF0001/itmpatch.exe\n\n\n5.0 Installation instructions\n=============================\nThis fix can only be installed over an existing installation. \nUse the following steps to install this fix.\n\n5.1 Before installing the fix\n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Prerequisites\nfor this fix' must be installed before this fix can be installed.\n\n- With reference to this README, the symbol <CANDLEHOME> is the\nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\\IBM\\ITM'\non Windows systems.\n\nBefore installing this fix on UNIX systems, set the environment\nvariable CANDLEHOME to the IBM Tivoli Monitoring installation\ndirectory.\n\nFor example:\n> CANDLEHOME=/opt/IBM/ITM\n> export CANDLEHOME\n\n- Refer to section 7.0 entitled \"Known problems and workarounds\"\nbefore installation.\n\n- Because there is no uninstall utility for this fix, make sure to\nperform a backup of your environment before installing this fix.\n\n5.2 Local agent update\n----------------------\n1. Transfer the appropriate archive file\n(6.3.1.13-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory\non the system that contains the agent code to be updated. For\nthe purpose of this README, the symbol <TEMP> represents the\nfully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the \nsupported platforms.\n\n3. Use the \"itmpatch\" command to install the fix for that agent\nplatform. For more information on the \"itmpatch\" command, see\nsection 6.2.\n\nOn Windows systems, if the fix was expanded to\n<TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001, the install command is:\n\nFor 32 bit Agent:\n> <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\\itmpatch -h <CANDLEHOME>\n-i <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\\KOQ_winnt_tema_if0001.cab\n\nFor 64 bit Agent:\n> <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\\itmpatch -h <CANDLEHOME> \n-i <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\\KOQ_wix64_tema_if0001.cab\n\nNote : Use \"itmpatch\" command from <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\\ \ntemporary directory.\n\n5.3 Remote agent update\n-----------------------\n1. Transfer the appropriate archive file\n(6.3.1.13-TIV-ITM_SQL-IF0001.tar or .zip) to a temporary directory\non the IBM Tivoli Enterprise Monitoring Server system. For the\npurpose of this README, the symbol <TEMP> represents the fully\nqualified path to this directory.\nNote: On Windows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a \ndirectory structure that contains fixes for all of the \nsupported platforms.\n\n3. To add the agent fix bundles into the remote deploy depot, use\nthe \"tacmd addBundles\" command found in $CANDLEHOME/bin on UNIX\nsystems or in %CANDLE_HOME%\\bin on Windows systems. For more\ninformation on the \"tacmd addBundles\" command, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nOn UNIX systems,\nif the fix was expanded to <TEMP>/6.3.1.13-TIV-ITM_SQL-IF0001:\n> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.1.13-TIV-ITM_SQL-IF0001\n\nOn Windows systems,\nif the fix was expanded to <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i <TEMP>\\6.3.1.13-TIV-ITM_SQL-IF0001\n\nwhere:\n-n indicates that prerequisite bundles are not automatically\nadded. The -n parameter must be used because the fix \ndirectory does not contain any prerequisites that the fix\nmight require. Please see Section 3.1 for the prerequisites\nfor this fix.\n-i is the directory that contains the deployment bundles to \nbe added to the depot. \n\n4. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following \"tacmd\" commands. For more information on the\n\"tacmd login\" and \"tacmd updateAgent\" commands, see \"IBM Tivoli \nMonitoring Command Reference\".\n\nOn UNIX systems: \n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser>\n-p <password>\n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> $CANDLEHOME/bin/tacmd updateAgent -t OQ -n <Managed system name> -v 063113001\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser>\n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t OQ -n <Managed system name> -v 063113001\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is \nspecified as two characters (oq), not three characters (koq).\n- The node (-n) for the \"tacmd updateAgent\" command is the\nmanaged system name of the operating system (OS) agent to be\nupdated.\nThe target node for the \"tacmd updateAgent\" command is always\nan OS agent.\n\n5. To check if Remote Agent Update is SUCCESS/INPROGRESS/FAILED use the command \n>tacmd getDeployStatus -g <transaction id>\n\nwhere transaction id is the id provided after updateAgent command.\n\n5.4 Agent support update\n------------------------\nUse the following steps to update the Tivoli Enterprise Monitoring\nServer, Tivoli Enterprise Portal Server, or Tivoli Enterprise\nPortal Desktop.\n\n1. Transfer the appropriate archive file\n6.3.1.13-TIV-ITM_SQL-IF0001.tar or .zip) to the Tivoli \nEnterprise Monitoring Servers, Tivoli Enterprise Portal\nServers, or Tivoli Enterprise Portal Desktops.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems\nor an extract utility on Windows systems. This step creates a \ndirectory structure that contains fixes for all of the supported\nplatforms.\n\n3. Expand the archive file (koq_tems_teps_tepd_if0001.tar or .zip)\nthat contains the updates for Tivoli Enterprise Monitoring\nServer, Tivoli Enterprise Portal Server, and Tivoli Enterprise\nPortal Desktop using the \"tar\" command on UNIX systems or an \nextract utility on Windows systems. This step creates a \ndirectory structure that includes a subdirectory called CD-ROM,\nwith the necessary updates.\n\n4. Use the Application Support Installer(ASI) script to launch either \nGUI installation or silent installation of the application \nsupport files. \n\nNote: For IBM Tivoli Monitoring Version 6.3 or above, one\nof the following additional steps must be performed.\n\n1. Acquire a platform-specific pre-packaged JRE version \nof the Application Support Installer (ASI). See IBM \nTivoli Monitoring Application Support Installer, \n6.2-TIV-ITM_ASI-IF0002 at \nhttp://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]\nfor download and installation instructions.\n\n2. Specify the '-j javahome' parameter with the path to \na java(r) 1.5 or java 1.6 installation when running \nthe itmasi.sh or itmasi.bat script described below. \n\nGUI installation option\n------------------------\nThe GUI can be started by using one of the following commands\nfrom within the CD-ROM directory where setup.jar is located.\n\nOn UNIX systems:\n> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>] \n\nOn Windows systems:\n> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>] \n\nwhere:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-j <JAVAHOME> - Optional. The fully-qualified path to the\n\"bin\" directory where Java(R) is installed.\nThe location of Java on your system might\nvary.\n\nWhen prompted by the Application Support Installer for the \ninstallable media directory, select the CD-ROM directory, not\nthe component directory. The installer can install updates for \nmultiple components at the same time.\n\nSilent installation option\n--------------------------\nTo use the silent installation option, use one of the following\ncommands from within the CD-ROM directory where setup.jar is \nlocated. \n\nNote: Agent support upgrade for IBM Tivoli Monitoring Version 6.3 \nor above on Linux, zLinux, Solaris and windows operating systems \nrequires the following files contained in interim fix \n6.2-TIV-ITM_ASI-IF0002. This is applicable to both GUI and \nsilent installation option of agent support upgrade.\n- Linux: setupLinux.bin\n- zLinux: setupLinux390.bin\n- Solaris: setupSolaris.bin\n- Windows: setupwin32.exe\n\nFollow the installation instructions contained in the\n\"6.2-TIV-ITM_ASI-IF0002.README\".\n\nOn UNIX systems:\n> ./itmasi.sh -h <CANDLEHOME>[-silent] \n[-r <response file>] \n[-j <JAVAHOME>] \n\nOn Windows systems:\n> itmasi -h <CANDLEHOME> [-silent] \n[-r <response file>] \n[-j <JAVAHOME>] \n\nwhere:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r <response file> - Required. Customized response file name.\nThe default response file \"response.txt\" in\nthe CD-ROM directory can be copied and\nmodified as per your environment.\n\n-j <JAVAHOME> - Optional. The fully-qualified path to the\n\"bin\" directory where Java(R) is installed.\nThe location of Java on your system might\nvary.\n\n5. The next panel presented by the Application Support Installer \nasks for the selection of which Tivoli Monitoring components\nyou want to add application support to.\nFor this fix, the check boxes should be set as follows:\n\nChecked - Tivoli Enterprise Monitoring Server(TEMS)\nChecked - Tivoli Enterprise Portal Server(TEPS)\nChecked - Tivoli Enterprise Desktop Client(TEPD)\n\nContinue through the remaining GUI panels selecting the\nMicrosoft SQL Server 06.31.13.01 support to complete the\ninstallation.\n\nNote: When support is installed using CLI or GUI for any of the\nabove Tivoli Monitoring components, they are restarted. \n\n\n6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise\nPortal Browser was running when the update was installed, it\nmust be restarted.\n\n\n6.0 Additional installation information\n=======================================\nAny existing Microsoft SQL Server Agent instances should be restarted\nafter the installation of this fix.\n\n6.1 Installation instructions for agent baroc file\n--------------------------------------------------\nFix (6.3.1.13-TIV-ITM_SQL-IF0001) includes changes to the agent\nbaroc files which need to be reinstalled. If you have already\ninstalled these baroc files, there are no additional installation\nsteps. If not, refer to IBM Tivoli Monitoring, Installation\nand Setup Guide under \"Installing monitoring agent baroc files\non the event server\" in \"Installing the IBM Tivoli Enterprise\nConsole Event Synchronization\" section for more information.\n\n6.2 Additional information on using \"itmpatch\" command\n----------------------------------------------------\nThe \"itmpatch\" command has the following syntax.\n\nUsage: itmpatch -h <installation home> [OPTIONS]\n\nitmpatch -h <installation home>\n-t { <patch_file_directory> | <patch_file> }\n\nitmpatch -h <installation home>\n-i { <patch_file_directory> | <patch_file> }\n\nwhere:\n-h Specifies the IBM Tivoli Monitoring installation directory\n-i Specifies the path to the directory or patch file to be \ninstalled\n-t Generates a report of the actions to be taken by the patch\n\nFor example, on UNIX systems:\n- To preview the fix installation, use the \"-t\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>\n\n- To install the fix, use the \"-i\" option:\n> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>\n\nwhere:\n<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n<TEMP> represents the fully qualified directory specification where\nthe fix is located. On Windows systems, this must include the drive\nletter.\n\n6.3 Verifying the update\n------------------------\n1. To verify the agent was updated correctly, use the \"tacmd\" command\nto view the agent's current version after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer prior to viewing the agent version.\n\nFor example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli \nMonitoring installation directory, the default location\nis '/opt/IBM/ITM'.\n\n> $CANDLEHOME/bin/tacmd login -s <server>\n-u <itmuser>\n-p <password>\n> $CANDLEHOME/bin/tacmd listSystems -t OQ\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'.\n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t OQ \n\nNote:\n- The component (-t) for the tacmd \"listSystems\" command is \nspecified as two characters (OQ), not three characters (KOQ).\n\nWhen the agent update is successful, the agent version is:\n06.31.13.01.\n\nAfter the agent is restarted, you can also use the GUI to verify\nthe agent was successfully updated.\nFor the agent on Windows systems, the version number is \n06.31.13.01.\n\n2. To verify the agent support files were updated correctly, use \nthe \"kincinfo\" command on Windows systems or the \"cinfo\" command\non Linux or UNIX systems. The sample output below shows the \nversions of the Tivoli Enterprise Portal Server, Tivoli \nEnterprise Monitoring Server, or Tivoli Enterprise Portal\nDesktop systems after this fix has been successfully applied.\n\nNote: The displayed build date and installation date might not \nbe accurate. This is known problem.\n\nOn UNIX or Linux systems:\n-------------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\n./cinfo -i\n\nOn Windows systems:\n-------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\nFor example:\n> %CANDLE_HOME%\\InstallITM\\kincinfo -i\n\nC:\\Users\\Administrator>kincinfo -i\n*********** Thursday, May 10, 2018 04:36:22 PM ************\nUser : Administrator Group : NA\nHost Name : HJS497-MSQL-T-1 Installer : Ver: 063007000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\nOQ TEMS App Support/Microsoft SQL Server Support\nWICMS Version: 06.31.13.01 Build: 81136\n\nOQ TEPS App Support/Microsoft SQL Server Support\nWICMS Version: 06.31.13.01 Build: 81136\n\nOQ TEPB App Support/Microsoft SQL Server Support\nWICMS Version: 06.31.13.00 Build: 71541\n\nOQ TEPD App Support/Microsoft SQL Server Support\nWICMS Version: 06.31.13.01 Build: 81136\n\n\n7.0 Known problems and workarounds\n==================================\nAbstract: itmpatch command fails during upgrade\nProblem: When itmpatch command is executed, it fails while upgrading\nagent fix pack. The following error message is \ndisplayed: \n\nVersion 06.31.13.XX of product koq is currently installed.\nThe patch requires that you must have at least version\n06.31.13.XX of product installed to apply this patch.\nWorkaround: Use the itmpatch.exe provided in patch file \n6.3.1.13-TIV-ITM_SQL-XXXXXX.zip or \n6.3.1.13-TIV-ITM_SQL-XXXXXX.tar file.\n\nAbstract: English characters are getting displayed in Agent support \ninstaller having Non-English language operating system.\nProblem: In Non-English language operating system, when agent \nsupport installer is executed it shows English characters.\nWorkaround: None\n\nAbstract: Installing support for patch fails on ITM 6.3.0\nProblem: When you try to install the support for this patch on ITM\n6.3.0, the installation fails with following error:\nThe wizard cannot continue because of the following error: \ncould not load wizard specified in /wizard.inf (104)\nWorkaround: Use the pre-packaged binaries for itmasi available at:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24034924 [http://www-01.ibm.com/support/docview.wss?uid=swg24034924]\n\nAbstract: Crash encountered in event viewer for koqagent.exe\nProblem: Sometimes while stopping the koqagent process, the collection\nprocess is not getting completed. When koqagent.exe stops, the\nthread spawned by it gets terminated forcefully. Hence it's\ncausing a crash.\nWorkaround: None\n\nAbstract: Application support installation fails on Non Windows OS.\nProblem: While installing the application support on the machines\nhaving Operating system other than windows, the support\ninstallation using ASI fails if the temporary directory \nwhere the patch files are extracted has spaces.\nWorkaround: Use the temporary directory without space.\n\nAbstract: MSSQL Agent collector crashes.\nProblem: Sometimes the job 'syspolicy_purge_history' fails and \nthe collector crashes.\nWorkaround: 1. Disable scheduling of system job 'syspolicy_purge_history'.\n2. Disable detail trace logging.\n\nAbstract: MSSQL Agent collector does not auto-restart.\nProblem: When agent is configured with non admin user, it fails\nto auto-restart if it needs to be.\nWorkaround: Restart the agent manually from MTEMS window.\n\n8.0 Additional product information\n==================================\nNone\n\n\n\n9.0 Notices\n===========\nThis information was developed for products and services offered in \nthe United States. IBM may not offer the products, services, or \nfeatures discussed in this document in other countries. Consult your\nlocal IBM representative for information on the products and services\ncurrently available in your area. Any reference to an IBM product, \nprogram, or service is not intended to state or imply that only that\nIBM product, program, or service may be used. Any functionally \nequivalent product, program, or service that does not infringe any \nIBM intellectual property right may be used instead. However, it is \nthe user's responsibility to evaluate and verify the operation of any\nnon-IBM product, program, or service.\n\nIBM may have patents or pending patent applications covering subject\nmatter described in this document. The furnishing of this document \ndoes not grant you any license to these patents. You can send license\ninquiries, in writing, to:\n\nIBM Director of Licensing\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\n\nThe following paragraph does not apply to the United Kingdom \nor any other country where such provisions are inconsistent \nwith local law:\n\nINTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \n\"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, \nINCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF \nNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.\n\nSome states do not allow disclaimer of express or implied warranties\nin certain transactions, therefore, this statement may not apply \nto you.\n\nTrademarks and service marks\n----------------------------\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks\nof International Business Machines Corp., registered in many\njurisdictions worldwide. Other product and service names might be\ntrademarks of IBM or other companies. A current list of IBM trademarks \nis available on the Web at \"Copyright and trademark information\" at \nwww.ibm.com/legal/copytrade.shtml [www.ibm.com/legal/copytrade.shtml].\n\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks\nof Microsoft Corporation in the United States, other countries, or \nboth.\n\nJava and all Java-based trademarks are trademarks of Sun Microsystems, \nInc. in the United States, other countries, or both.\n\nUNIX is a registered trademark of The Open Group in the United States \nand other countries.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.\n\nPREREQUISITES\nITCAMMA: Microsoft SQL Server Agent, Version 6.3.1.13\n\nINSTALLATION INSTRUCTIONS\nPlease refer to the README contained in the Description section above for general installation instructions.\n\nDOWNLOAD PACKAGE\n\n\n\nHOW CRITICAL IS THIS FIX?\nRecommended\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat 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] [ ] \n [/support/docview.wss?uid=swg24044840&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24044840&aid=2]Problems (APARS) fixed\nIJ00815, IJ00433, IJ01540"
}
] |
TRAIN_Q091 | 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 | false | [
{
"filename": "swg21648986.txt",
"text": "Title: IBM Unable to decrypt the FIPS key error when exporting keys from IBM Datacap Taskmaster Capture - United States\n\nText:\ndcskey gnk; dc_KTF.xml TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n 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\" \n\nCAUSE\nEnabling the Use FIPS compliant algorithms for encryption, hashing and signing security policy can cause this error\n\nRESOLVING THE PROBLEM\nTo allow the keys to be exported properly: \n\n 1. Select Local Security Policy under Administrative tools \n 2. Navigate to Local Policies - Security Options \n 3. Select System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing and be sure it is Disabled \n 4. Run dcskey e again to export the key"
}
] |
TRAIN_Q092 | 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. | false | [
{
"filename": "swg21268440.txt",
"text": "Title: IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States\n\nText:\njava.io.NotSerializableException SessionObjectSize counter PMI enabled disable serializable TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When PMI (Performance Monitoring Infrastructure) is enabled with SessionObjectSize counter enabled, getting NotSerializableException. The SystemOut.log shows something similar to:\n\n[4/10/07 5:25:42:618 EDT] 00000091 SessionContex E Exception is: java.io.NotSerializableException: com.com1.dept.nls.model.someModel \nat java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code)) \n... \nat java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(CompiledCode)) \nat com.ibm.ws.webcontainer.httpsession.SessionContextMBeanAdapter.getSessionsInfo(SessionContextMBeanAdapter.java(Compiled Code)) \nat com.ibm.ws.webcontainer.httpsession.SessionTrackingPMIApplicationData$1.getRuntimeInfo(SessionTrackingPMIApplicationData.java(Inlined Compiled Code)) ... \nat com.ibm.ws.pmi.server.modules.ServletSessionsModule$SessionObjSize.updateStatistic(ServletSessionsModule.java(Compiled Code)) \nat com.ibm.ws.pmi.server.data.SpdStatExternal.updateExternal(SpdStatExternal.java(Compiled Code)) \nat com.ibm.websphere.pmi.server.PmiAbstractModule.update(PmiAbstractModule.java(Compiled Code)) \n...\n\nThe error does not affect application functionality. Disabling SessionObjectSize counter makes the error stop occurring. \n\nCAUSE\nWebSphere® Application Server Session Manager throws NotSerializableException when it tries to serialize non-serializable SessionData from the application before sending it to PMI.\n\nRESOLVING THE PROBLEM\nThe application needs to ensure there is no session object that is not serializable. The object needs to implement java™.io.Serializable interface.\n\n \n\nHISTORICAL NUMBER\n 53925\nL6Q\n000"
}
] |
TRAIN_Q093 | 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) | false | [
{
"filename": "swg21993043.txt",
"text": "Title: IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-3092 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: 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.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/114336 [https://exchange.xforce.ibmcloud.com/vulnerabilities/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V10.0 & V9.0 \n\nWebSphere Message Broker V8.0 \n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://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]\n\nThe APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://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]\n\nThe APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker\nV8\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp://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]\n\nThe APAR is targeted to be available in fix pack 8.0.0.8 \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?rs=849&uid=swg27006308 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nNone known\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http://www-01.ibm.com/software/support/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n 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. \n\nREFERENCES\nComplete CVSS v3 Guide [http://www.first.org/cvss/user-guide] \nOn-line Calculator v3 [http://www.first.org/cvss/calculator/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http://www.ibm.com/security/secure-engineering/bulletins.html] \nIBM Product Security Incident Response Blog [http://www.ibm.com/blogs/psirt] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 27 Oct 2016 - Original version Published\n\n\n*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. \n\nDISCLAIMER\nAccording 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.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB"
}
] |
TRAIN_Q094 | Test MDB with Multiline message.
Hi, I need to test my MDB injecting a multiline message into my Local WAS server. I have tried the WAS Integrated Universal Client and SIBExplorer. But the only accept on line mesage. How can I inject a multiline message into my Local WAS?
I have tryid to config HermeJMS but without success. | - | true | [] |
TRAIN_Q095 | When will WebSphere Application Server v7.0 and v8.0 be end of support (EOS)?
Has an End of Support (EOS) date been announced for WebSphere Application Server v7.0 and 8.0? | - | true | [] |
TRAIN_Q096 | How to fnd out more about performance problems in WebSphere Application Server which are in relationship with DB2? (Analyze long running sql-queries)
I want to analyze a WAS/DB2 performance problem and want to investigate the root-cause of the issue. In my WAS SystemOut.log file I noticed a lot of hanging threads that hang in java.net.SocketInputStream.socketRead0(). For example:
"WebContainer : 0" at java/net/SocketInputStream.socketRead0() at java/net/SocketInputStream.read() at com.xyz.methodABC() ...
This indicates that the server still waits for result-sets from the database. So how to find out more about such db-performance-issues? | - | true | [] |
TRAIN_Q097 | 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 | false | [
{
"filename": "swg21067352.txt",
"text": "Title: IBM Too Many Open Files error message - United States\n\nText:\nwasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3/14/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen 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.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn 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. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp://www.IBM.com/support/docview.wss?rs=180&uid=swg21469413 [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows 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. \n\nTo 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). \n\nIt is important that you change the Refresh Rate. Select View > Update Speed, and change it to 5 seconds. \n\n[/support/docview.wss?uid=swg21067352&aid=2] [/support/docview.wss?uid=swg21067352&aid=2] \n\nThere is also another Microsoft utility called Handle that you can download from the following URL: \nhttps://technet.microsoft.com/en-us/sysinternals/bb896655.aspx [https://technet.microsoft.com/en-us/sysinternals/bb896655.aspx] \n\nThis tool is a command line version of Process Explorer. The URL above contains the usage instructions. \n\n\nAIX \nThe commands lsof and procfiles are usually the best commands to determine what files and sockets are opened.. \n\nlsof \nTo 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: \n\nlsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out \n\nThis 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. \n\nIt is best to capture lsof several times to see the rate of growth in the file descriptors. \n\nprocfiles \nThe procfiles command does provide similar information, and also displays the full filenames loaded. It may not show sockets in use. \n\nprocfiles -n [PID] > procfiles.out \n\n\nOther commands (to display filenames that are opened) \n\nINODES and DF \ndf -kP filesystem_from_lsof | awk '{print $6}' | tail -1 \n>> Note the filesystem name \nfind filesystem_name -inum inode_from_lsof -print > filelist.out \n>> Shows the actual file name \n\nsvmon \nsvmon -P PID -m | grep pers (for JFS) \nsvmon -P PID -m | grep clnt (for JFS2, NFS) \n(this opens files in the format: filesystem_device:inode) \n\nUse the same procedure as above for finding the actual file name. \n\n\nLinux 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: \n\nlsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out \n\nThe 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. \n\nIt is best to capture lsof several times to see the rate of growth in the file descriptors. \n\n\nAlternately 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: \n\nls -al /proc/PID/fd \n\n\nSolaris Run the following commands to monitor open file (socket) descriptors on Solaris: \n\npfiles \n/usr/proc/bin/pfiles [ PID ] > pfiles.out \n\nlsof \nlsof -p [ PID ] > lsof.ou t \n\nThis 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: \nlsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out \n\nIt is best to capture lsof several times to see the rate of growth in the file descriptors. \n\nHP-UX \nlsof \nlsof -p [ PID ] > lsof.out \n\nThis 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: \nlsof -p [PID] -r [interval in seconds, 1800 for 30 minutes] > lsof.out \n\nIt is best to capture lsof several times to see the rate of growth in the file descriptors. \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"
}
] |
TRAIN_Q098 | 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. | false | [
{
"filename": "swg21902654.txt",
"text": "Title: IBM Restoring missing xml files from backup in DASH - United States\n\nText:\nDASHL2; DASHL2FAQ; restore; backup; xml; WEB-INF TECHNOTE (FAQ)\n\nQUESTION\n 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) ? \n\nCAUSE\nSome of these files could have gotten corrupted. \n\nANSWER\nDASH 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. \n\nPlease follow below steps to restore files from the backups directory: \n\n1. Stop the DASH server \n\n2. Make a backup copy of the current xml files in the following directory: \n\n<JazzSM_Home>/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF \n\n3. Go to <JazzSM_Home>/profile/backups and find a backup file from a previous day/time that contains the missing xml files \n\nExample: isc_stores_backup_1427324004938.zip \n\n4. Unpack the zip file to a temporary location. \n\n5. Restore these files in the WEB-INF directory from the backup. \n\n6. Start DASH \n\n7. Test if you can access the DASH Portal."
}
] |
TRAIN_Q099 | Migrating a Rule Project to JRules v7.0 and v7.1
How do I migrate a rule project to JRules v7.0 and v7.1? | - | true | [] |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.