diff --git "a/train.jsonl" "b/train.jsonl" new file mode 100644--- /dev/null +++ "b/train.jsonl" @@ -0,0 +1,450 @@ +{"id": "TRAIN_Q000", "document": "IBM STREAMS 4.1.1.1 and 4.1.1.2 JOBS DO NOT INHERIT THE ENVIRONMENT VARIABLES SET IN .BASHRC, WHEN STREAMS IS RUN AS A SYSTEM SERVICE - United States FLASH (ALERT)\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 -i \n --application-ev =\n * \n \n\n\nRELATED INFORMATION\n APAR IT18432 [https://www-01.ibm.com/support/entdocview.wss?uid=swg1IT18432]", "question": "User environment variables no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2? \n\nHave 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\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", "answer": "To work around the issue, set environment variables that are needed by the application directly in the instance with: * \n \n * streamtool setproperty\n * -d -i \n --application-ev ="} +{"id": "TRAIN_Q001", "document": "IBM Exit() action within User Defined Function in Impact Policy Language - United States netcool; impact; netcool/impact; nci; ipl; policy; language; exit; exit(); function; user; defined; custom; udf; parser; action; set; global; variable; var; get; setglobalvar; getglobalvar; globalvar TECHNOTE (FAQ)\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]", "question": "Netcool/Impact (all versions): How is the Exit() action function expected to work with User Defined Functions? Netcool/Impact (all versions)\n\nUsing the Exit() action function within a User Defined Function in a Policy will not exit the Policy process.", "answer": "This is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call"} +{"id": "TRAIN_Q003", "document": "IBM Guide to properly setting up SSL within the IBM HTTP Server - United States ssl; handshake; secure socket layer; handshake failed; enable; ssl config; ssl setup; setup; IHS; crl; revocation; ssl; ssl; ssl; configure; config; config; config TECHNOTE (TROUBLESHOOTING)\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 \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n Listen 443\n \n SSLEnable\n SSLClientAuth None\n \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 \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n \n ServerName www.mycompany2.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n \n \n Listen 443\n \n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n \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 \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n \n ServerName www.mycompany2.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n \n \n \n ServerName www.mycompany3.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n \n \n Listen 443\n \n ServerName www.mycompany.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs\"\n DirectoryIndex index.html\n \n \n \n ServerName www.mycompany2.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany2\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs2\"\n DirectoryIndex index2.html\n \n \n \n ServerName www.mycompany3.com\n SSLEnable\n SSLClientAuth None\n SSLServerCert mycompany3\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n \n DocumentRoot \"c:/program files/ibm http server/htdocs3\"\n DirectoryIndex index3.html\n \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]", "question": "How to configure SSL mutual authentication in IBM HTTP Server? \n\nWe 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?\n\nThanks\n", "answer": "The 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"} +{"id": "TRAIN_Q005", "document": "IBM Support's Guide to Rules File Processing - United States rules; 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]", "question": "What happened to load.rules FAQ example? The load.rules maths function example rules file does not appear to be available anymore? ", "answer": "Netcool Technical Support Guide to rules file processing is provided as a collection of commonly used rules file techniques."} +{"id": "TRAIN_Q006", "document": "IBM Security Bulletin: IBM Tivoli Network Manager IP Edition is affected by an Apache CXF vulnerability (CVE-2017-3156) - United States 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.", "question": "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?", "answer": "CVEID: 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)"} +{"id": "TRAIN_Q007", "document": "IBM 2035 MQRC_NOT_AUTHORIZED Connecting to WebSphere MQ from WebSphere Application Server via CLIENT Bindings - United States 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", "question": "Why do I get an exception when calling MQ after migrating my BPM environment (2035 MQRC_NOT_AUTHORIZED) ? \n\nWe 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:\n\n [10/16/17 13:50:05:273 AST] 0000026d SystemOut O\n com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The\n security authentication was not valid that was supplied for QueueManager\n 'QM1' with connection mode 'Client' and host name 'MQ1(1414)'.\n Please check if the supplied username and password are correct on the\n QueueManager to which you are connecting.\n ...\n Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed\n with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').\n at\n com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.jav\n a:204)\n ... 162 more\n\nThe 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.", "answer": "Default 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)'"} +{"id": "TRAIN_Q008", "document": "IBM Rational Application Developer Support Policy for 64 bit technology - United States RSM; RSD; RSA; RAD; caspian64 bit; 64-bit; RAD 7 64 bit; RAD 7 OS; operating system; Rational Application Developer; X64; Windows 64 bit; supported OS; AMD; PMR #13878; 379; 000; 13878379000; 1263677; 64bit; 64 bit; 32 bit; 32bit; 32-bit; 64-bit; O/S; OS; requirements; system requirements; 8.0.3; 8.0; 7.5; v8.0.3; v7.5; v7.0; v8.0; v7.5.4; 803; windows 7; server; profile; websphere; test environment; create profile; button; greyed; Run Profile Management Tool ; disabled; IBM Software Development Kit; SDK; JRE; Program Files(x86); WAS; websphere application server; clearcase; scm; clearcase scm adapter; rational requisitepro; reqpro; heap size; jvm; max os x; os x; osx; mac TECHNOTE (FAQ)\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", "question": "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? ", "answer": "the Rational RequisitePro integration features/plugins are not supported or provided. These are only available as 32-bit eclipse plugins."} +{"id": "TRAIN_Q009", "document": "IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States ACCE; CE; Property; FEM TECHNOTE (FAQ)\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", "question": "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. ", "answer": "Follow 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"} +{"id": "TRAIN_Q010", "document": "IBM Starting WebSphere Application Server gives warning message - Could not lock User prefs - United States Websphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\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//logs/ 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.", "question": "managesdk.sh -listEnabledProfileAll fails with error: Couldn't get file lock. \n\nI am installing WebGUI FP13 and it is failing with the symptoms described in below technote.\n\nhttps://www-01.ibm.com/support/docview.wss?uid=swg21993160\n\nAs described in above technote when I run managesdk.sh script it fails with below errors.\n\n./managesdk.sh -listEnabledProfileAll\n\nSep 26, 2018 10:14:12 AM java.util.prefs.FileSystemPreferences syncWorld\n\nWARNING: Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\n\nPlease let me know what could be the issue?", "answer": "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.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file."} +{"id": "TRAIN_Q011", "document": "IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States TECHNOTE (TROUBLESHOOTING)\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]", "question": "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! ", "answer": "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."} +{"id": "TRAIN_Q012", "document": "IBM Insufficient ulimit Value Causes Native OutOfMemory - United States 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.", "question": "Are there any instructions for ulimit settings for WebSphere running on Linux? Are there any instructions for ulimit settings for WebSphere running on Linux? ", "answer": "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."} +{"id": "TRAIN_Q013", "document": "IBM Applying TIP 2.2 fix packs directly to a TIP 2.1 installation - United States TIPL2; TIPL2INST; tivoli Integrated portal; feature pack TECHNOTE (FAQ)\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--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]", "question": "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? ", "answer": "In order to apply TIP 2.2 fix packs, the target TIP installation must already be at TIPCore 2.2.0 or newer. TIP 2.1 installations must be upgraded to TIP 2.2 using the TIP 2.2.0.1 feature pack."} +{"id": "TRAIN_Q014", "document": "IBM Problems installing NMA agent (N4 agent) on Linux x86-64 - United States ITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)\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 /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\nci\n\n\n\n06\n\n22\n\n04\n\n000\n\n\nto \n\n\nci\n\n\n\n06\n\n30\n\n05\n\n000 \n\n \n\nThe same for other components in case they are also missing from your depot. \n\nThe dsc files are into /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", "question": "NMA agent installation failure \n\nHello, 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.\n\nIf I try to install the agent locally on the Linux machine, the list of available agents does not include NMA agent at all.\n\nIs there a solution to this problem?", "answer": "The 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."} +{"id": "TRAIN_Q015", "document": "IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States FLASH (ALERT)\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", "question": "Help with Action required for IIB V9 & WMB V8 Hypervisor Editions for security vulnerabilities in Red Hat Linux \n\nI 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.\n\nWhere can I find this information?", "answer": "WebSphere Message Broker Hypervisor Edition"} +{"id": "TRAIN_Q016", "document": "IBM Guidelines for setting ulimits (WebSphere Application Server) - United States ulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)\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 \n\n controls which users or groups will have these limits \n\n is either the string \"soft\" or \"hard\" limits.\nThe hyphen \"-\" can also be used which represents both soft and hard limits \n\n and 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 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]", "question": "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? ", "answer": "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."} +{"id": "TRAIN_Q017", "document": "IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States DSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION\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", "question": "Does Portal 6.1.x support Oracle 12c? \n\nWe 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?\n\nSpecifically, if Oracle 12c is not supported, what version of Oracle 11g is?", "answer": "Oracle 11gR2 V11.2.0.1 (including RAC)"} +{"id": "TRAIN_Q018", "document": "IBM Deletion of virtual portal fails with transaction timeout - United States virtual 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]", "question": "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?", "answer": "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: \n\n * the total and/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout"} +{"id": "TRAIN_Q019", "document": "IBM FAQ for IBM SPSS Statistics Subscription - United States 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].", "question": "i cannot enter SPSS statistics trial program \n\nI'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.\"\n\ni'm using Windows 7(32bit), and just want to know how can i resolve it.\n", "answer": "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"} +{"id": "TRAIN_Q020", "document": "IBM Rational Host Access Transformation Services 9.0 - United States service 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", "question": "HATS Plugin Download \n\nHi\n\nI have RDZ 9.0 and want to install the HATS plugin.\n\nI've downloaded from this link:\n\nhttp://www.ibm.com/developerworks/downloads/ws/whats/\n\nHATS 9.0.0.0 but it won't install because RDZ itself is not enough and it sais I need one of the following:\n\nIBM Rational Application Developer for WebSphere Software\n\nIBM Rational Software Architect for WebSphere Software\n\nIBM Rational Developer for i for SOA Construction\n\nIBM Rational Business Developer\n\nIBM Integration Developer\n\nwhich I don't have.\n\nWhere can I download the HATS version that is compatible with RDZ 9.0 and doesn't need anything else?", "answer": "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."} +{"id": "TRAIN_Q024", "document": "IBM SPSS Student Version and Graduate Pack Resources - United States SPSS 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", "question": "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: \n\nAuthorization failed.: You are not allowed to generate any more new licenses.\nEnd Of Transaction. \nNo additional authorizations are permitted on this code. \nWhat should I do?", "answer": "For installation & licensing issues on Student version and Graduate pack, contact your vendor."} +{"id": "TRAIN_Q026", "document": "IBM Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 - United States 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/reporting if you are using Tivoli Common Reporting 3.1 or\nlater with Jazz for Service Management and /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] [ ]", "question": "Where can I find the ITM VMware VI Agent Reports package for v 7.2? \n\nI 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:\n\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/W22ac5f3ebabf_4ff4_bd55_1a897c9a443e/page/Report%20Catalog\n", "answer": "Download 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"} +{"id": "TRAIN_Q027", "document": "IBM JDBC driver or database insufficiencies cause administration portlets to fail. - United States RT0002E; 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: /config/cells//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: /config/cells//nodes//variables.xml\n\nRELATED INFORMATION\n WebSphere Portal V8.0 detailed system requirements [http://www-01.ibm.com/support/docview.wss?uid=swg27007791]", "question": "Why are we not able to create new pages using the Manage Pages Portlet? We are using Portal 8.5 on Windows,\n\nFrom 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:\n\nEJPAS0017E: Unable to create PageName\n\nThe error in SystemOut.log shows:\n\n DefaultTransa E Message: Could not save object in repository.,\n Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\n com.ibm.workplace.wcm.services.repository.RepositoryException:\n Message: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\n ...\n \n Caused by: com.ibm.icm.da.DBAccessException:\n java.sql.SQLFeatureNotSupportedException: DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream\n at com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857)", "answer": "The JDBC driver does not meet WebSphere Portal v8's prerequisites."} +{"id": "TRAIN_Q028", "document": "IBM Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) - United States 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.", "question": "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). ", "answer": "CVEID: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)"} +{"id": "TRAIN_Q029", "document": "IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States dwc 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.", "question": "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.\n\nErrors seen are:\n\n AWSUI0833E The operation could not be completed. There has been a communication failure. \n The internal message is: AWSJCO005E WebSphere Application Server has given the following error: Error getting WsnNameService properties. \n\nWhat is the reason?", "answer": "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"} +{"id": "TRAIN_Q030", "document": "IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\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", "question": "Does DataPower support SHA-2? Is DataPower able to support SHA-2 ?", "answer": "Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred."} +{"id": "TRAIN_Q031", "document": "IBM Handling 302 redirect error message in a Web Application Firewall - United States HTTP; 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", "question": "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?", "answer": "To resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these \"302 Redirects\"."} +{"id": "TRAIN_Q033", "document": "IBM Automatically renew trusted credential - United States security; 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]", "question": "Scheduled reports fail after changing password Scheduled reports fail after changing password", "answer": "For IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.\nThe credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration."} +{"id": "TRAIN_Q034", "document": "IBM Tivoli Network Manager IP Edition 4.2.0 Fix Pack 3, 4.2.0-TIV-ITNMIP-FP0003 - United States 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] [ ]", "question": "ITNM 4.2 Fix Pack 3 link and build number?. ITNM 4.2 FP3 is available, if yes then where we can download?. ", "answer": "http://www.ibm.com/support/knowledgecenter/en/SSSHRK_4.2.0/itnm/ip/wip/relnotes/reference/nmip_rn.html?view=kc#relnotes__description"} +{"id": "TRAIN_Q037", "document": "IBM Tivoli Integrated portal enabling multiple logins using same user Id - United States TIPL2SEC 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.", "question": "How can multiple TDWC users logon into TDWC with same TWS user id? \n\nGiven 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:\n\nAnother user is currently logged in with the same user ID. Select from the following options:\n\n List item\n\nLog out the other user with the same user ID. You can recover changes made during the other user's session.\n\n List item\n\nReturn to the Login page and enter a different user ID.\n\nHow can multiple users logon without one user needing to logout?", "answer": "Only 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."} +{"id": "TRAIN_Q038", "document": "IBM How to Rollback From a Fix Pack or Interim Fix to an Earlier Build - United States uninstall; revert; downgrade; hotsite; HS; out; fixpack TECHNOTE (FAQ)\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 /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 /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 /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 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", "question": "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? ", "answer": "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 /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 /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 level, which will overwrite the files applied by fix pack or interim fix update. \n 7. Start the Cognos service."} +{"id": "TRAIN_Q039", "document": "IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States 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=
[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=
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\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]", "question": "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. ", "answer": "To avoid this problem, the generic JVM argument [http://www-01.ibm.com/support/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=
[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."} +{"id": "TRAIN_Q040", "document": "IBM Installation Manager does not work if symbolic links are used for Installation Manager of installed product locations - United States RN1.5; RN1.5.1; RN1.5.0.1; RN1.5.2; RN1.5.3; RN1.6; RN1.6.1; RN1.6.2; RN1.6.3; RN1.6.3.1; RN1.7; RN1.7.1; RN1.7.2; SRX; 1628092; RATLC02668456; IPL; Symlink TECHNOTE (TROUBLESHOOTING)\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.", "question": "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?", "answer": "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."} +{"id": "TRAIN_Q041", "document": "IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) - United States 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.", "question": "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?", "answer": "CVEID: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)"} +{"id": "TRAIN_Q042", "document": "IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States EJQAB0067E; 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 * /config/cells//clusters// for cluster \n * /config/cells//nodes//servers// 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]", "question": "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:\r\nCaused 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) ", "answer": "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\")."} +{"id": "TRAIN_Q043", "document": "IBM Pdcollect tool for ITM IBM i OS agent - United States ITM_TEMA_DIST_CONFIGURATION ITM_i5_Agent 5724C04 A4 OS/400 i5/OS IBMi IBM i pdcollect TECHNOTE (FAQ)\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/pdcollect.sh \n\nwhere 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.", "question": "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? ", "answer": "The pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information."} +{"id": "TRAIN_Q044", "document": "IBM SPSS Student Version and Graduate Pack Resources - United States SPSS 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", "question": "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? ", "answer": "For installation & licensing issues on Student version and Graduate pack, contact your vendor."} +{"id": "TRAIN_Q045", "document": "IBM Insufficient Access Error adding documents to FileNet Content Engine - United States FNRCE0001E; 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.", "question": "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. ", "answer": "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."} +{"id": "TRAIN_Q046", "document": "IBM IV67523 Move local data from CANDLEHOME to another file system - United States 6.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///tables/ATTRLIB -> /var/IBM/ITM/ATTRLIB/\n * \n * /opt/IBM/ITM/EIFLIB -> /var/IBM/ITM/EIFLIB\n * \n * /opt/IBM/ITM///tables/EIFLIB -> /var/IBM/ITM/EIFLIB/\n * \n * /opt/IBM/ITM/hist -> /var/IBM/ITM/hist\n * \n * /opt/IBM/ITM///hist -> /var/IBM/ITM/hist/\n * \n * /opt/IBM/ITM/psit -> /var/IBM/ITM/psit\n * \n * /opt/IBM/ITM///psit -> /var/IBM/ITM/psit/\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 * //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.", "question": "Does Linux KVM monitoring agent support CANDLEDATA function? Does Linux KVM monitoring agent in ITM support CANDLEDATA function? ", "answer": "The CANDLEDATA mechanism is available with ITM 6.30.05.00."} +{"id": "TRAIN_Q047", "document": "IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States SECURITY BULLETIN\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", "question": "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? ", "answer": "CVEID: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)"} +{"id": "TRAIN_Q048", "document": "IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States ACCE; CE; Property; FEM TECHNOTE (FAQ)\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", "question": "How to change the maximun string length for properties in ACCE \n\nHI 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\n\nPlease guide me", "answer": "Follow 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"} +{"id": "TRAIN_Q049", "document": "IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States 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.", "question": "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?", "answer": "· 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."} +{"id": "TRAIN_Q050", "document": "IBM Configuring access for HTTP and HTTPS in Jazz for Service Management - United States jazzsm11relnotes; jazzsm1101relnotes; jazzsm1102; jazzsm1103relnotes; relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; HTTP; HTTPS TECHNOTE (TROUBLESHOOTING)\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 theelement. The initial value of allelements isCONFIDENTIAL, meaning that secure access is always required. \n\n5. Change the setting toNONEto enable both HTTP and HTTPS requests. The element now reads:NONE. \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\n\nChangePasswdControllerServletConstraint\n\nChangePasswdControllerServlet\n/*\n\n\nRoles\nadministrator\noperator\nconfigurator\nmonitor\niscadmins\n\n\nNONE\n\n \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://:16310/ibm/console\nUse the HTTP port for logging in to the Dashboard Application Services Hub on the HTTP port .\nhttps://: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.", "question": "Does JazzSM 1.1.2.1 support HTTP access? Does JazzSM 1.1.2.1 support HTTP access? ", "answer": "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."} +{"id": "TRAIN_Q052", "document": "IBM Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) - United States 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.", "question": "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?", "answer": "CVEID: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)"} +{"id": "TRAIN_Q053", "document": "IBM Unable to add Centera Device in FileNet Content Engine - United States 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", "question": "P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider \n\nNew P8 CPE 5.2.1 install does not see the Centera Fixed Storage. The following error is returned:\n\nFNRCC0110E: 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)\n\nWhat is the cause?", "answer": "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."} +{"id": "TRAIN_Q054", "document": "IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States 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=
[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=
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\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]", "question": "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)?", "answer": "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.\""} +{"id": "TRAIN_Q055", "document": "IBM Unable to add Centera Device in FileNet Content Engine - United States 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", "question": "P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider \n\nNew P8 CPE 5.2.1 install does not see the Centera Fixed Storage. The following error is returned:\n\nFNRCC0110E: 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)\n\nHow do I fix this?", "answer": "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."} +{"id": "TRAIN_Q056", "document": "IBM Automated data collection capability provided by wpcollector tool - United States wpcollector 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 [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-.zip file in the [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]", "question": "What exactly is \"wpcollector\" in WebSphere Portal Server? I've been told to get wpcollector output? What exactly is this?", "answer": "Wpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support."} +{"id": "TRAIN_Q058", "document": "IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States 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", "question": "Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written", "answer": "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."} +{"id": "TRAIN_Q059", "document": "IBM Removing a failed install from the ITM i5/OS agent - United States i5 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", "question": "Uninstalling I5 OS agent failed \n\nI need to uninstall the I5OS agent before reinstalling a newer release of the same.\n\nCommand: DLTLICPGM LICPGM(5724C04)\n\nis anyway failing and I don't know how to proceed further. \n\nCan you please let me know the manual steps to uninstall the i5OS agent correctly ?", "answer": "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."} +{"id": "TRAIN_Q060", "document": "IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States TECHNOTE (FAQ)\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 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 ,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]", "question": "Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc \n\nInstalled an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc\n\nI get the following messages in the logs:-\n\n/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\"\n\nand from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log \"Unauthorized client connecting from ,rejecting\"\n\nWhat is the reason?", "answer": "One reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance"} +{"id": "TRAIN_Q062", "document": "IBM Minimum authorization required for SAP agent logon userid - United States authorization minimum IBMMON_AGENT profile settings agent userid SAP MySAP /IBMMON/AUTH TECHNOTE (FAQ)\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", "question": "SAP Agent user authorizations \n\nHello, 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 ?\n\nThanks", "answer": "By default, the MySAP agent uses the userid IBMMON_AGENT, that is created when ITM transport are imported in the SAP system, together with /IBMMON/AUTH role and profile.\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."} +{"id": "TRAIN_Q063", "document": "IBM Operational Decision Manager V8.5.1.2 Fix Pack - United States 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--FP002.zip, and extract its files. (Change 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--FP002.zip, and extract its files. (Change 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 /eclipse/tools. \n 2. Run the commandimcl updateAll -repositories WDC/updates,WDS/updates -acceptLicense.\n\n * Use the option -installDirectory 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", "question": "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", "answer": "This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2."} +{"id": "TRAIN_Q064", "document": "IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems - United States 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.", "question": "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 ? ", "answer": "Operating 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"} +{"id": "TRAIN_Q065", "document": "IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States verbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\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: \n\n * ex: -Xloggc:/tmp/gc.log \n\n-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc \n\n-XX:NumberOfGClogFiles= * Set the number of files to use when rotating logs, must be >= 1. The rotated log files will use the following naming scheme, .0, .1, ..., .n-1. \n\n-XX:GCLogFileSize=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]", "question": "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? ", "answer": "Add the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:/tmp/gc.log"} +{"id": "TRAIN_Q066", "document": "IBM Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002) - United States 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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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 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_lo_[instance]_kloagent_-.log shows \ntrace points similar to the following: \n\n- - - \n... \n...:kumpdcm2.c,195,\"KUMP_GetNextMember\") Directory 7F3B3401C380 \n/LFA_test_logs matched to pattern <^test_1.log$> \n...:kumpdcm2.c,211,\"KUMP_GetNextMember\") Directory handle \n7F3B3401C380 \nname /LFA_test_logs successfully matched 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 matched ^test_1.log$ \n...:kumpdcm2.c,330,\"KUMP_GetNextMemberDouble\") Directory \n7F3B3401C380 \n/LFA_test_logs member successfully matched 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 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 ... - .........,\nstatus 10 \" \nAdditional information: In the agent RAS1 log, the trace points \n\"*****Error: u_strFromUTF8 failed for string ..... - \n ..., status 10 \" 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 that results \nin this error is a file that should be monitored, then events\nwould be lost as the file is not monitored. The \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 _lo_[instance]_kloagent_-.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 \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 _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= \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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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 < >\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 _lo_[instance]_kloagent_-.log\ncontains trace points similar to the following: \n- - - \n... \n...:kum0dir.c,147,\"KUM0_stat_withMsgFlag\") *** Unable to obtain \nstatistics for file 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 \n70203_Base;msg='Tivoli [message]\\[message]' \n\nLog File Agent v6.3 and 6.3.0-TIV-ITM_LFA-IF0004\n \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_lo_[instance]_kloagent_-.log \ncontains trace points similar to the following: \n- - - \n... \n:kumpwfrm.c,261,\"KUMP_WaitFileReadyForMonitor\") *** \nUnable to open file local file , \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_lo_[instance]_kloagent_-.log\ncontains trace points similar to the following, where\n'test0420' is not the last or only directory to search: \n- - - \n... \n: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: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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-0.log\ncontains entries similar to the following: \n- - -\n... \n...:eventlog.cpp,1955,\"ModifyParameter\") Entry \n...:eventlog.cpp,1969,\"ModifyParameter\") Scanning for replaceable parameters. \n...:eventlog.cpp,2175,\"ModifyParameter\") No parameters to \nformat. \n\n...:eventlog.cpp,2185,\"ModifyParameter\") Scan results \n \n...:eventlog.cpp,2192,\"ModifyParameter\") Exit \n...:eventlog.cpp,1600,\"DisplayRecord\") Event Log Record: \n \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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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=>/LFA/49806/sotestout.txt >, \nUser= \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_lo_[instance]_kloagent_-.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.<.. \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_lo_[instance]_kloagent_-.log shows\ntrace points similar to the following: \n- - - \n... \n...:kumpfdp2.c,778,\"DoFileTailRestart\") Retrieved old monitor \nfilename 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 \n...:kumpfdp2.c,834,\"DoFileTailRestart\") Per TailRestartFromTop\nparameter, restarting file monitoring from beginning of file\n \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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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_lo_[instance]_kloagent_-.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 \n...:winlogquerylist.cpp,1145,\"writeEventDataToPipe\") \nNode <.fmt stanza> wrote event to pipe for event log , \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, =' 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_lo_[instance]_kloagent_-.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 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_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/_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 _lo__kloagent_.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_lo__kloagent_.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 to value 735 \n...:kumpfdp2.c,200,\"KUMP_ParseSingleRestartLine\") Error: parsed\nlocation file <735> creation modification \nsize with RecPtr 6000000000736F53 \n...:kumpfdp2.c,427,\"UpdateRestartFileBaseFunction\") Note: \nRequired fields missing from restart file \n...:kumpfdp2.c,173,\"KUMP_ParseSingleRestartLine\") Parsing \nRecPtr 6000000000736F53 <;> \n...:kumpfdp2.c,200,\"KUMP_ParseSingleRestartLine\") Error: parsed\nlocation file creation modification \n size with RecPtr 5FFFFFFFA0736F52Page 34 of 35 \n...:kumpfdp2.c,427,\"UpdateRestartFileBaseFunction\") Note: \nRequired fields missing from restart file \n \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_lo__kloagent_.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_lo__kloagent_.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_lo__kloagent_.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_lo__kloagent_.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 AttrName 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_lo__kloagent_.log contains\ntrace entries similar to the following: \n- - - \n... \n...:kumpwfrm.c,261,\"KUMP_WaitFileReadyForMonitor\") *** \nUnable to open file local file , Errno: 0,\nErrorText: No error, NO retry. Exiting \n...:kumpfdp5.c,231,\"CheckFileExistAndReady\") *** File \nC:/lo/43866/43866.log -- initial monitoring setup failed\n: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 _lo__kloagent_.log\ncontains trace entries similar to the following: \n- - - \n... \n...:kumprmfr.c,1015,\"KUMP_ReadMonitorFileUnicodeRecord\") \nSavedRec 51A6A58 14 \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_lo__kloagent_.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_lo__kloagent_.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_lo__kloagent_.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\nroot@mypia.tivlab.austin.ibm.com: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 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 \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 bundles must be removed from the\ndepot, using the \"tacmd removeBundles\" command. \nFor example: tacmd removeBundles -t lo -v 06300000\n\nOn UNIX systems, \nif the fix was expanded to /6.3.0-TIV-ITM_LFA-FP0002:\n> $CANDLEHOME/bin/tacmd addBundles -n \n-i /6.3.0-TIV-ITM_LFA-FP0002 \n\nOn Windows systems, \nif the fix was expanded to \\6.3.0-TIV-ITM_LFA-FP0002:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n \n-i \\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 \n-u \n-p \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 \n-v 06300200\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 \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 \n-u \n-p \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 \n-u \n-p \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_lo__kloagent_.log located in\n$CANDLEHOME/logs on UNIX systems and\n%CANDLE_HOME%\\tmaitm6\\logs on Windows systems:\n\n Component: ira\n Driver: agent_fac_63:201709131450/4769716.3 \n 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", "question": "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? ", "answer": "This fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC little-endian Log File agent."} +{"id": "TRAIN_Q067", "document": "IBM Rule Team Server/Decision Center is timing out while performing certain operations - United States 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-.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\nModify the timeout value that is associated with transactions (in seconds)\nilog.rules.teamserver.transaction.timeout\n600\n \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", "question": "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. ", "answer": "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-.ear\\teamserver.war\\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout."} +{"id": "TRAIN_Q068", "document": "IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States Datapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\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", "question": "Does DataPower support SHA-2? \n\nIs DataPower able to support SHA-2 (SHA256)?\n 1", "answer": "Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred."} +{"id": "TRAIN_Q069", "document": "IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States ssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ)\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.", "question": "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? ", "answer": "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."} +{"id": "TRAIN_Q070", "document": "IBM Search option for a reserved word or character in documents in Atlas - United States 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", "question": "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? ", "answer": "When 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\""} +{"id": "TRAIN_Q071", "document": "IBM Verify an IEM server upgrade is still in progress - United States 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.", "question": "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?", "answer": "It is important to allow the upgrade to complete when in this state, and not attempt to cancel or kill the upgrade process. To verify the upgrade is still active, check that the following process is still running: \n\nWindows: BESAdmin.exe \n\nLinux: BESAdmin"} +{"id": "TRAIN_Q072", "document": "IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States 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", "question": "Error: \"MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION\" occurs at portal startup \n\nWe are using Portal Server 8.5 and when starting the Portal server we see following error:\n\n0000005e MBeanStarter E com.ibm.wps.scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.ApplicationServerExtensions\n\nHow can we permanently resolve this error?", "answer": "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"} +{"id": "TRAIN_Q073", "document": "IBM An unexpected ruleset version is executed - United States 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", "question": "Latest deployed ruleset not executing in clustered environment \n\nWe 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.\n", "answer": "Possible 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"} +{"id": "TRAIN_Q075", "document": "IBM Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) - United States Sybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES\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 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 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 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/CNN25ML:\n> $CANDLEHOME/bin/tacmd addBundles -i /CNN25ML/WINDOWS/Deploy -t oy -f\n> $CANDLEHOME/bin/tacmd addBundles -i /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/CNN25ML:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\CNN25ML\\WINDOWS\\Deploy -t oy -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\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 \n-u \n-p \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 \n-v 062002000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 \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 \n-p INSTANCE=\"\"\n\nNote:\n- The 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 \n-u \n-p \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 \n-u \n-p \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:/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, ::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=\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/config/ directory.\n2.Open the coordinating file:\nFor single-instance agents: .ini \nFor multi-instance agents: _.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", "question": "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. ", "answer": "Component: 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"} +{"id": "TRAIN_Q076", "document": "IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States SECURITY BULLETIN\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.", "question": "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?", "answer": "CVEID: 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)"} +{"id": "TRAIN_Q080", "document": "IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States FLASH (ALERT)\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", "question": "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? ", "answer": "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable"} +{"id": "TRAIN_Q081", "document": "IBM Content Collector V4.0.1 Fix Pack 3 - United States 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", "question": "'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? ", "answer": "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."} +{"id": "TRAIN_Q082", "document": "IBM Security Network Protection firmware 5.3.1 release notes - United States release 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]", "question": "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?", "answer": "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."} +{"id": "TRAIN_Q083", "document": "IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States isolate this resource provider TECHNOTE (TROUBLESHOOTING)\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]", "question": "When click test connection, the older JDBC driver version shows in the SystemOut.log file \n\nWhen I click a test connection to a datasource, in the SystemOut.log file I can see the below information...\n\n [8/11/16 5:31:28:494 EDT] 00000088 DSConfigurati I DSRA8205I: JDBC driver name : Oracle JDBC driver \n [8/11/16 5:31:28:495 EDT] 00000088 DSConfigurati I DSRA8206I: JDBC driver version : 9.2.0.1.0 \n [8/11/16 5:31:28:496 EDT] 00000088 DSConfigurati I DSRA8025I: Successfully connected to DataSource. \n [8/11/16 5:31:28:608 EDT] 00000088 DSConfigurati I DSRA8203I: Database product name : Oracle \n [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\n\nWhere is WAS getting this information from?\n\nWe 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.\n\nThere is another older driver ojdbc14.jar\n\nWhen 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?\n\nIf 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.\n\nJDBC providers are pointed to ojdbc6.jar, but why it is showing a different JDBC driver version?", "answer": "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."} +{"id": "TRAIN_Q084", "document": "IBM Security Bulletin: IBM MQ clients connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it. (CVE-2018-1371) - United States SECURITY BULLETIN\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", "question": "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?\n", "answer": "CVEID: 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)"} +{"id": "TRAIN_Q085", "document": "IBM How to change Siebel connection settings using the siebel.properties file in WebSphere Adapter for Siebel eBusiness Applications - United States 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, \\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]", "question": "WebSphere Business Integration (WBI) Adapter for Siebel timeouts: unable to process large orders? \n\nI 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:\n\nOMRPC Request xxx on connection xxx was abandoned after 600133 ms because it timed out. (SBL-JCA-317)\n\nWhat should I do?", "answer": "Siebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.\nCreate a siebel.properties file and save it in the classpath of the adapter (For example, \\connectorModule) and restart the adapter and broker to pick up the settings to establish the required connections."} +{"id": "TRAIN_Q087", "document": "IBM Required gtk libraries for IBM Installation Manager on AIX - United States gtk; 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.(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_.tar to decompress the file.\n \n \n 3. Open the decompressed directory gtk2_bundle_ 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]", "question": "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? ", "answer": "To use the GUI, the gtk+ RPM and dependencies must be available on AIX. \n\n\nInstall this set of RPMs on AIX:"} +{"id": "TRAIN_Q089", "document": "IBM Security Bulletin: Multiple vulnerabilities in IBM® Java SDK affect WebSphere Application Server that ships with WebSphere Enterprise Service Bus (CVE-2015-2613, CVE-2015-2601, CVE-2015-4749, CVE-2015-2625, CVE-2015-1931) - United States SECURITY BULLETIN\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.", "question": "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. ", "answer": "CVEID: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)"} +{"id": "TRAIN_Q090", "document": "IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.13-TIV-ITM_SQL-IF0001 - United States ITM; SQL; ITCAM; Microsoft Applications DOWNLOADABLE FILES\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 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 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\\6.3.1.13-TIV-ITM_SQL-IF0001, the install command is:\n\nFor 32 bit Agent:\n> \\6.3.1.13-TIV-ITM_SQL-IF0001\\itmpatch -h \n-i \\6.3.1.13-TIV-ITM_SQL-IF0001\\KOQ_winnt_tema_if0001.cab\n\nFor 64 bit Agent:\n> \\6.3.1.13-TIV-ITM_SQL-IF0001\\itmpatch -h \n-i \\6.3.1.13-TIV-ITM_SQL-IF0001\\KOQ_wix64_tema_if0001.cab\n\nNote : Use \"itmpatch\" command from \\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 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 /6.3.1.13-TIV-ITM_SQL-IF0001:\n> $CANDLEHOME/bin/tacmd addBundles -n -i /6.3.1.13-TIV-ITM_SQL-IF0001\n\nOn Windows systems,\nif the fix was expanded to \\6.3.1.13-TIV-ITM_SQL-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i \\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 \n-u \n-p \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 -v 063113001\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 -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 \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 ] [-j ] \n\nOn Windows systems:\n> itmasi [-h ] [-j ] \n\nwhere:\n-h - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-j - 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 [-silent] \n[-r ] \n[-j ] \n\nOn Windows systems:\n> itmasi -h [-silent] \n[-r ] \n[-j ] \n\nwhere:\n-h - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r - 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 - 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 [OPTIONS]\n\nitmpatch -h \n-t { | }\n\nitmpatch -h \n-i { | }\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> /bin/itmpatch -h -t \n\n- To install the fix, use the \"-i\" option:\n> /bin/itmpatch -h -i \n\nwhere:\n is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n 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 \n-u \n-p \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 \n-u \n-p \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", "question": "Does ITCAM MSSQL agent support SQL Server 2017? Does MSSQL monitoring agent support SQL Server 2017?\nThe compatibility matrix only mentions SQL Server 2016:\nhttps://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=D67CBA30151E11E7B7E234686CAD92CE&osPlatforms=Windows&duComponentIds=S009&mandatoryCapIds=62|45", "answer": "Added support for SQL Server 2017 version."} +{"id": "TRAIN_Q091", "document": "IBM Unable to decrypt the FIPS key error when exporting keys from IBM Datacap Taskmaster Capture - United States dcskey gnk; dc_KTF.xml TECHNOTE (TROUBLESHOOTING)\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", "question": "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. ", "answer": "To 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"} +{"id": "TRAIN_Q092", "document": "IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States java.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", "question": "ClassCastException IlrStorePolicy$SerializedENamedElement incompatible with EStructuralFeature \n\nWe keep getting the following error when navigating in Decision Center on Websphere Application Server.\n\njava.lang.ClassCastException: ilog.rules.teamserver.web.IlrStorePolicy$SerializedENamedElement incompatible with org.eclipse.emf.ecore.EStructuralFeature\n\nDoes anyone know how we can avoid this error?\n", "answer": "WebSphere® 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."} +{"id": "TRAIN_Q093", "document": "IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States WMB IIB SECURITY BULLETIN\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", "question": "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? ", "answer": "CVEID: 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)"} +{"id": "TRAIN_Q097", "document": "IBM Too Many Open Files error message - United States wasrun; 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", "question": "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", "answer": "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. \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"} +{"id": "TRAIN_Q098", "document": "IBM Restoring missing xml files from backup in DASH - United States DASHL2; 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/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF \n\n3. Go to /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.", "question": "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? ", "answer": "1. Stop the DASH server \n\n2. Make a backup copy of the current xml files in the following directory: \n\n/profile/config/cells/JazzSMNode01Cell/applications/isc.ear/deployments/isc/isclite.war/WEB-INF \n\n3. Go to /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."} +{"id": "TRAIN_Q100", "document": "IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003) - United States DOWNLOADABLE FILES\n\nABSTRACT\n This Fix Pack addresses problems reported in IBM Tivoli Business Service Manager 6.1.1 \n\nDOWNLOAD DESCRIPTION\n\n\n\n*************************************************************\n* A change introduced by this Fix Pack is incomplete but will not \n* adversely affect existing function.\n*\n* Please refer to APAR(s) IV76788 for a description of the \n* problem(s) and corrective action(s). \n*\n* Evaluate this APAR for the potential impact in your environment.\n*\n* Please refer to APAR(s) IV79769 for a description of the \n* problem(s) and corrective action(s). \n*\n* Evaluate this APAR for the potential impact in your environment.\n*\n* A change introduced by this Fix Pack might negatively \n* affect existing product function.\n*\n* Please refer to APAR IV79769 for a description of the \n* problem and corrective action. See tech note for more details:\n* http://www-01.ibm.com/support/docview.wss?uid=swg24041505 [http://www-01.ibm.com/support/docview.wss?uid=swg21968610]\n*\n* Evaluate this APAR for the potential impact in your environment.\n*\n* Please refer to APAR(s) IV91142 for a description of the \n* problem(s) and corrective action(s). APAR IV71513 introduced in FP3\n* may affect performance in rare circumstances. \n*\n* Evaluate these APARs for the potential impact in your environment.\n*************************************************************\n\n\nIBM Tivoli Business Service Manager 6.1.1\nFix Pack Version 6.1.1-TIV-BSM-FP0003\n\n\nReadme file for: IBM Tivoli Business Service Manager\nProduct/Component Release: 6.1.1\nUpdate name: Fix Pack 3\nFix ID: 6.1.1-TIV-BSM-FP0003\nPublication Date: July 6, 2015\nLast modified date: July 3, 2015\nOnline version of the readme file:\nhttp://www.ibm.com/support/docview.wss?uid=swg24039742 [http://www.ibm.com/support/docview.wss?uid=swg24039742]\n\nAttention: You can always find the most current version of the readme file online.\n\n\nContents\n\n1.0 Files included in this Fix Pack\n2.0 Hardware and software requirements\n3.0 Installation information\n3.1 Dependencies\n3.2 Prerequisites\n3.3 Special considerations\n3.4 Superceded Fixes\n3.5 Extracting Fix Pack files\n3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX \n3.5.2 Extracting on Windows platforms\n3.5.3 Fix pack directories\n3.6 Maintenance upgrade strategy \n3.6.1 Example maintenance scenario\n3.7 Installation \n3.7.1 Installing the Fix Pack\n3.7.2 Discovery Library Toolkit\n3.8 TBSM agent\n3.9 Uninstalling the Fix Pack\n3.10 Recovering from a failed Fix Pack install\n3.11 Restoring failed DE upgrade from backup \n3.12 \"Service Level Objectives (SLO) Reporting\" function\n4.0 Additional information for TBSM Fix Pack 2 APARS\n4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS\n4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING \nON RADEVENTSTORE\n5.0 List of APARs\n5.1 TBSM 6.1.1 Fix Pack 3 APARS\n5.2 TBSM 6.1.1 Fix Pack 2 APARS\n5.3 TBSM 6.1.1 Fix Pack 1 APARS\n5.4 Tivoli Integrated Portal\n5.5 Jazz for Service Management (JazzSM)\n6.0 New support and features\n6.1 TBSM 6.1.1 Fixpack 3\n6.2 TBSM 6.1.1 Fixpack 2\n6.3 TBSM 6.1.1 Fixpack 1\n6.4 Additional Browser Support with Fixpack 3\n6.5 Additional Browser Support with Fixpack 2 \n6.6 eWAS Fixes and Upgrades \n6.7 OMNIbus 8.1\n6.8 DB2\n6.9 TADDM 7.3 Integration\n7.0 Known issues\n7.1 Some date options in TBSM Reports do not work\n7.2 Issues creating wire between Service Tree and Active \nEvent List (AEL)\n7.3 TBSM Agent Chart title differs from name in the \ndrop down list\n7.4 Minimize-restore does not restore to correct size for\nService Navigation->Data Fetchers on Internet Explorer(IE) 9\n7.5 Portlets covering content in a free form page \n7.6 Creation and deletion of Services and Templates that contain \nspecial characters\n7.7 WEBSERVICES SECURITY NOT FUNCTIONAL\n7.8 If using WEBSERVICES SECURITY (WSS) user authentication\n7.9 Microsoft Internet Explorer 11\n7.10 With certain Solaris installations the Event Summary portlet\nmay fail render\n7.11 TIP Portlet blank or does not load after TIP 2.2.0.15\ninstallation \n7.12 TIP chart portlet blank if TBSM Service Admin page is\nclosed and re-opened\n7.13 TBSM integration with ISM is no longer operational\n7.14 Java Security Warnings\n8.0 Copyright and trademark information\n\n\n=======================================================================\n1.0 Files included in this Fix Pack\n-------------------------------\n\nFix Pack 3 addresses the problems that have been reported in IBM®\nTivoli® Business Service Manager version 6.1.1. The following table\ncontains a list of files included in this Fix Pack and operating systems\nassociated with these files:\n\n+---------+----------------------------------------------------------------+\n| Platform| File |\n+---------+----------------------------------------------------------------+\n| AIX® | 6.1.1-TIV-BSM-FP0003-aix.tar |\n| | |\n+---------+----------------------------------------------------------------+\n| Linux® | 6.1.1-TIV-BSM-FP0003-linux.tar |\n| | |\n+---------+----------------------------------------------------------------+ \n| Solaris | 6.1.1-TIV-BSM-FP0003-solaris.tar |\n| | |\n+---------+----------------------------------------------------------------+\n| Windows®| 6.1.1.-TIV-BSM-FP0003-windows.zip |\n| | |\n+---------+----------------------------------------------------------------+\n| zLinux | 6.1.1-TIV-BSM-FP0003-zlinux.tar |\n| | |\n+--------------------------------------------------------------------------+\n|all platforms| 6.1.1-TIV-BSM-FP0003.README |\n+-------------+------------------------------------------------------------+\n|all platforms| 6.1.1-TIV-BSM-FP0003.README_Translated.zip | \n+-------------+------------------------------------------------------------+ \n\n\nNote: Whenever is used in the text of this readme, as part of the\nfilename of the Fix Pack package, it refers to, and can be\nsubstituted for one of the following operating systems:\n* Linux\n* Solaris\n* AIX\n* Windows\n* zLinux \n\nThe following files have been updated or replaced by this Fix Pack. \n\nAdded files on the Data Server:\nObjectServer_DS_config.ant\ntbsm_generic_ant_caller.bat\ntbsm_generic_ant_caller.sh\nTBSM_BusCompCreateShadows.js\nTBSM_BusCompPlaceAllCIsByIdentifier.js\nTBSM_BusCompShadowTechnologyGroups.js\nTBSM_ResEnrichReaderRecycle.js\nApplyPoliciesFor611FP3\nBSM_TemplateUpdates611FP0003.radsh\nsetJVMSettings.jy\nsetJVMSettings.bat\nsetJVMSettings.sh\nsmack-3.3.0.jar\nsmackx-3.3.0.jar\norg.apache.axis2-woden.jar\nipa-1.0-20120430.jar\nTDWHistory.xml \nFiles under tbsm/tools directory\n\nReplaced files on the Data Server:\nASQLStore.class\nBSM_Templates.radsh\nBSM_Templates_updatepropagation.radsh\nBSM_Templates_templates_only.radsh\nBSM_Templates_instances_only.radsh\ncanvasOpenURLActions.xml\ncollect_logs.ant\nfo_config.ant\nfo_data_config.ant\ntbsm_consistency.zip\nsetTraceLevel.jy\nscriptedAPIStartup.bsh\nMigrateUserActionscanvasDynamicSubMenuActions_X.xsl\nMigrateUserActionscanvasOpenURLActions_X.xsl\ntbsm_viewDefinitionFiles.lst\ntbsmDataImport.xml\nVisualRepresentationAttributes.xml\nav.jar\ntbsm-info.jar\nitmdataclient.jar\nmaintcli.jar\nncs.jar\ntbsm-jviews.jar\nncsagent.jar\nncsSoapClient.jar \nncChartComponent.jar\nnew-server.xml\nRAD_namevalidator.props \nTBSM_BusCompPlaceAllCIsByAttr.js\nTBSM_markerChangeProvider.ipl\nTBSM_ResEnrichMain.js\nTBSM_SLAUpdateServiceEvent.ipl\nTBSM_AV_GetColorForSeverity.ipl\nupdate-ear.py\nversioninfo.bat\nversioninfo\nverutil.jar\nFiles under tbsm/contrib/gistools\n\nReplaced Impact files on the Data Server: \nnciJmxClient.jar\nnci.jar\n\n\nIf you have made changes to the above mentioned files you will\nfind your copy of the file under:\n\n- Copy of scriptedAPIStartup.bsh (scriptedAPIStartup.bsh.orig)\ncan be found in the same directory as the original.\n- The copy of the files can be found in the following\ndirectory: \n[InstallDirectory]/\ntipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003/data\n\n\nIf Service Level Objectives (SLO) Reporting was previously deployed,\nthen the following policy files will also be overwritten by this Fix\nPack:\n\nTBSM_createBusinessCalendarDefn.js\nTBSM_createServiceDefinition.js\nTBSM_recordSLAMetric.js\nTBSM_serviceDowntimeBasedOnTBSMStatusChange.js\nTBSM_slaDefGlobalSettings.js\nTBSM_serviceDefinition.js\nTBSM_db2GetData.js\nTBSM_getDataFromTBSMAvailability.js\nTBSM_BusinessCalendar.js\n\n\n---\nAdded files on the Dashboard Server:\nObjectServer_DS_config.ant\ntbsm_generic_ant_caller.bat\ntbsm_generic_ant_caller.sh\nabout_icon22.png\nabout_thumb.png\nsetJVMSettings.jy\nsetJVMSettings.bat\nsetJVMSettings.sh\n\nReplaced files on the Dashboard Server:\ncanvasviewer_simple.html\ntbsm-jviews.jar\ntbsm-symbol-palette.jar\nrad_nodes_links.css\nLaunchTBSM.nova\nRAD_help_eclipse.props\nRAD_sla.props\nRAD_namevalidator.props\nserviceTreePortletView.jsp\nserviceNavigatorPortletView.jsp\nCreateDBPoller.jsp\nActionLoader.jsp\ndelete_template.jsp\nAbout.jsp\nesda_model.jsp\nactionLoader.jsp\nserviceViewerPortletView.jsp\nautopop_config.jsp\nChartInstanceChooser.jsp\nism_instances.jsp\ninstanceuserpreferences.jsp\nmain_ruleset_id_fields.jsp\nmain_ruleset_rules_list.jsp\nmain_rulesets_output.jsp\nmain_rulesets_rules.jsp\nmain_rulesets_sla.jsp\nserviceTreePortletEdit.jsp\nserviceViewerPortletEdit.jsp\ntaguserpreferences.jsp\nInstanceCustomizerWizard.jsp\nEventRawAttributeSelector.jsp\nTBSMCMPopup.jsp\nBIRTChartConfig.jsp\ncolumnProperties.jsp\ndependency_rule.jsp\nEditDBPollerFrames.jsp\nErrorMessageHandler.jsp\nmain_content.jsp\nmain_ruleset.jsp\nmain_rulesets_security.jsp\nmain_service.jsp\nmain_service_security.jsp\nmain_tabs.jsp\nmain_view.jsp\nServiceInstanceDependents.jsp\nLaunchDataBrowser.jsp\nrawattributeWizard/raw_event_table_fragment2.jsp\nRAD_AV_GetColorForSeverity.ipl\nradlabels*.properties\nncs.jar\nncsSoapClient.jar\nncChartComponent.jar\nav.jar\nitmdataclient.jar\nipa-1.0-20120430.jar\nitmdataclient.jar\nnci.jar\nnciClient.jar\nncCommon.jar\ntbsm-info.jar\nweb.xml\ncollect_logs.ant\nfo_config.ant\nfo_data_config.ant\nPolicies.jsp\nTypeBrowser.jsp\nimpactAdmin.properties\nROIEffReportIWidget.xml\nsetTraceLevel.jy\nversioninfo.bat\nversioninfo\nverutil.jar\nFiles under impactAdmin.war/scripts\nFiles under sla.war/dojo\nFiles under sla.war/audit/dojo\nFiles under twa.war/dojo\nRAD_dashboard_dataprovider.props\ntimeSeriesSearchDialog.jsp\ntimeSeriesPortletView.jsp\ntbsm-ltwd-server.jar\n\n\nReplaced Impact files on the Dashboard Server:\nnciClient.jar \nnciJmxClient.jar\nNCICLUSTER-EIC_configure.html\nTBSMCLUSTER-EIC_configure.html \nNCICLUSTER-new1twin.html\nTBSMCLUSTER-new1twin.html\nNCICLUSTER-newrwin.html\nTBSMCLUSTER-newrwin.html\n\n\nIf you have made changes to the above mentioned files you will\nfind your copy of the file under:\n- The copy of the files can be found in the following\ndirectory:\n[InstallDirectory]/\ntipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003/dash\n\n---\n\nAdded files associated with the Discovery Library Toolkit:\nremove_merged_resources.xml\nmigration/loadTaddmJars.bat \nmigration/migrateTaddmModel.bat \nmigration/loadTaddmJars.sh \nmigration/migrateTaddmModel.sh \nmigration/migrateClassFilters.xml \nmigration/etc/userPasswordPrompt.properties\ndb-checkupbeforecleanup.sql\n\nReplaced files associated with the Discovery Library Toolkit:\nscc_refreshnamingcommitchanges.sql \nscc_checkfordupsinstage.sql \nscc_processcreatecomponents.sql \nscc_remove_merged_resources.sql\nNamingRules.xml \ngenStep1SqlForTADDMFromOrm.xsl \ngenStep2SqlForTADDMFromOrm.xsl \ngenTheSQLTADDMFromOrm.xsl \nScrProducePostProcessingSql.xsl \nxmltoolkitsvc.properties \nASICLTools.jar\nsetdbshema.[sh|bat]\ncreateidmlbook.sql\ndb-cleanup.sql\n\n\n\nIf you have made changes to the above mentioned toolkit files you will\nfind your copy of the files under:\n[InstallDirectory]/tbsm/XMLtoolkit/log/install/maintenance/backup/611FP0003\n\n---\n\nTBSM agent packages are available for download from the TBSMAgent\ndirectory on the support download site. The TBSMAgent code was last\nupdated with TBSM 6.1.1 Fixpack 1\n\n\n=======================================================================\n\n2.0 Hardware and software requirements\n----------------------------------\n\nFor information about hardware and software requirements, see the\nTivoli Business Service Manager Installation Guide on the IBM\nTivoli Business Service Manager Information Center (at IBM Knowledge Center):\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/welcome.htm [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/welcome.htm]\n\nTo apply this Fix Pack you will need 3 GB of disk space. Please check\nthe amount of space you have before you install, as the installation\nwill fail if you run out of space.\n\n\n=======================================================================\n3.0 Installation information\n------------------------\n\n3.1 Dependencies\n\nThis Fixpack must be installed on each server(s) that is running \nthe TBSM data server or TBSM dashboard server.\n\nThis Fixpack requires IBM Tivoli Business Service Manager \nVersion 6.1.1 to be installed.\n\n3.2 Prerequisites\n-------------\n\nTivoli Integrated Portal 2.2.0.15 version 2 (v2) has been certified. It\ncan be installed after installing this fix pack.\n\nIBM strongly recommends updating to TIP FP 2.2.0.15 v2, if support is\nrequired for FF ESR 31 and IE11. If the TBSM data server and dashboard \nserver are installed on different machines, the TIP Fix Pack needs to be \ninstalled only on the dashboard server. In case of a TIP HA environment, \nthe HA nodes need to be disjoined first before upgrading to TIP FP.\n\nSee Fix Central for availability:\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]\n\nPost installation of TIP 2.2.0.15 v2 requires a re-start of the\nDashboard server and clearing of all user's browser cache!\n\n3.3 Special considerations\n----------------------\n\nConsider this information before you install the Fix Pack:\n1. You will be prompted during the installation to specify a backup\ndirectory name. The installer backs up DE at this location.\n\n2. This Fixpack does not backup the entire application. It only\nbacks up the files that it has updated/replaced. A backup copy of the\noriginal files can be retrieved from:\n[InstallDirectory]/tipv2/logs/tbsm/maintenance/backup/6.1.1.0/FP0003\n\n3. The TBSM and TIP processes or services may remain running but, will \nbe re-started during the Fix Pack install process. If the processes\nor services are manually stopped, prior to the Fix Pack install,\nplease make sure both the OMNIbus Object server and DB2 processes or\nservices remain running!\n\nNOTE: The installer will start/stop the TBSM and TIP services as\nneeded, during the install process.\n\nOn Linux/Unix: perform the following\n\n1. To stop the TBSM Data server issue the following command:\n\n$TIP_HOME/profiles/TBSMProfile/bin/stopServer.sh server1 \n-username -password \n\n2. To stop the TBSM Dashboard server, issue the following \ncommand:\n\n$TIP_HOME/profiles/TIPProfile/bin/stopServer.sh server1 \n-username -password \n\nBy default, username is tipadmin and password is the \ntipadmin password.\n\n3. To stop the TBSM Discovery Library Toolkit issue the \nfollowing command:\n\n$TBSM_HOME/XMLtoolkit/bin/tbsmrdr_stop.sh \n\nOn Windows:\n\n1. In the Start menu, click Settings -> Control Panel\n-> Administrative Tools -> Services.\n\nThe Services window opens. Depending on what services \nyou have installed, the available services are as follows: \n\nTivoli Business Service Manager - TBSMProfile_Port_17310. \nThis is the Data server. \nTivoli Integrated Portal - V2.2_TIPProfile_Port_16310.\nThis is the Dashboard server. \nTivoli BSM Discovery Library toolkit \nEIF probe \nThis service appears only if the EIF probe was installed \nas a Windows service. \n\n2. Right-click the service that you want to stop and click Stop.\n\n\n4. All non-vital programs should be closed prior to installation of \nthe Fixpack. \n\n\n3.4 Superceded Fixes\n----------------\n\n6.1.1.0-TIV-BSM-IF0001 is superceded by this Fix Pack.\n6.1.1.0-TIV-BSM-IF0002 is superceded by this Fix Pack.\n6.1.1.0-TIV-BSM-IF0003 is superceded by this Fix Pack.\n6.1.1.0-TIV-BSM-IF0004 is superceded by this Fix Pack.\n6.1.1-TIV-BSM-FP0001 is superceded by this Fix Pack.\n6.1.1-TIV-BSM-FP0002 is superceded by this Fix Pack.\n\n\n3.5 Extracting Fix Pack files\n-------------------------\n\n3.5.1 Extracting on Linux, Solaris, Linux for System z, and AIX \nplatforms\n\n1. Copy the file 6.1.1-TIV-BSM-FP0003-.tar to a temporary\nlocation on your TBSM Server.\n\n2. Unpack the file on each host where you need to install the Fix\nPack using these commands:\n\ntar -xvf 6.1.1-TIV-BSM-FP0003..tar\n\n\n3.5.2 Extracting on Windows platforms\n-------------------------------\n\n1. Copy the 6.1.1-TIV-BSM-FP0003-windows.zip file to a temporary\nlocation on your TBSM server host.\n\n2. Unzip the file on each server where you need to install the Fix Pack.\n\n\n3.5.3 Fix pack directories\n--------------------\n\nWhen you extract the file, these directories are created: \n\nTBSM -TBSM data server and dashboard server and TIP updates.\n\nDiscoveryLibrary -Discovery Library Toolkit updates\n\n/Reports\n\nSamples\n\n\n3.6 Maintenance upgrade strategy\n----------------------------\n\nBefore you install the Fix Pack, you need to plan how and when you will\nupgrade each TBSM server in your environment. \n\n\n3.6.1 Example maintenance scenario\n----------------------------\n\nIn this example, the maintenance is staged into two phases to\nreduce the time required for the TBSM maintenance window.\n\nIn this example environment, there are four servers: \n* primary data server\n* backup data server\n* two dashboard servers set up for load balancing called: dash1\nand dash2\n\nFollow this sequence:\n\nBefore you start the maintenance window: \n1. Upgrade backup data server\n2. Upgrade one dashboard server (for example dash2)\n3. Use the primary data server and dash1 for regular production\nactivities\n\nAfter you complete the upgrade the two secondary servers, start\nthe maintenance window down time for the production servers.\n1. Upgrade primary data server\n2. Upgrade dash1\n\nAfter you complete the upgrade for all the servers: \n1. Start primary data server\n2. Start backup data server\n3. Wait until TBSM completes the server synchronization.\n4. Start the dashboard servers. \n\n\n3.7 Installation\n------------\n\n\n3.7.1 Installing the Fix Pack\n-----------------------\n\n[Fix Pack] Refers to the directory where you extracted the Fix\nPack files from the zip/tar file.\n\nAttention: Install the Fix Pack with the same user that was\nused to install TBSM 6.1.1 GA\n\n\nNOTE: If you have deployed the Service Level Objectives (SLO) \nReporting Function, you must do the following before\ninstalling the Fix Pack:\n\n- Stop all Impact services that are running policies that\ncall the SLO functions to record data in the SLORPRT\ndatabase. If you have the service set to start at\nserver startup, then turn this option off before\ninstalling the fixpack, as the server is restarted\nduring the fixpack install.\n\nRunning the install without DE backup:\n\nIf you prefer to backup DE with your own procedures you can\nrun the install with the following parameter.\n\n-DNO_BACKUP=true\n\n(for Silent Install, uncomment the \"NO_BACKUP=true\" \nparm on the setupFP.rsp response file)\n\nIf you choose this method, you must backup DE before you install.\nAnd restore the original system using your backup/restore\nprocedures or utilities (if uninstalling the Fix Pack).\n\nFollow this procedure to install the Fix Pack:\n\n1. On the Tivoli Business Service Manager server host, change to the\n[Fix Pack]/TBSM directory where you extracted the files.\n2. Run the installation using one the following commands:\n* setup-windows.exe - Windows.\n* setup-.bin - other operating systems.\n\nInstallation command options:\n\nGUI mode No options, for example: \nWindows: setup-windows.exe\n\nor\n\nUNIX® : ./setup-.bin \n\nConsole mode\nUse the -i console option. \nFor example -\nWindows: setup-windows.exe -i console\n\nor \n\nUNIX® : ./setup-.bin -i console\n\nSilent Mode\n\na. Copy setupFP.rsp from the TBSM directory of the extracted\nFix Pack file ([Fix Pack]/TBSM) to a location it can be\nedited (/tmp).\nb. Update the file to match your environment.\nc. Confirm acceptance of license, by un-commenting this line\nand setting the parm to \"true\":\n#LICENSE_ACCEPTED=false\nd. Run:\n\nWindows: setup-windows.exe -f C:\\tmp\\setupFP.rsp\n\nor \n\nUNIX® :setup-.bin -f /tmp/setupFP.rsp\n\nNote: The response file needs to have a fully qualified\npath.\n\n3. During the install you will be asked to to verify\npath names to the TIP install.\n\n4. Restart both the Data and Dashboard processes/services\n\n5. After install is complete (and with the data server started), run\nthe script ApplyPoliciesFor611FP3, which can be found on the Data\nServer under $TBSM_HOME/bin. This script loads the new/updated\npolicies.\n\nNOTE: Do not run the ApplyPoliciesFor611FP3 on the secondary/\nbackup data server of a failover pair. This only needs to\nbe run on the primary data server.\n\nOn Windows:\n\nApplyPoliciesFor611FP3.bat \nFor example - ApplyPoliciesFor611FP3.bat tipadmin tipadmin\n\nOn Linux/Unix:\n\n./ApplyPoliciesFor611FP3 \nFor example - ./ApplyPoliciesFor611FP3 tipadmin tipadmin \n\nNOTE: Verify that the admin user id and password are\ncorrect otherwise, the script will fail at the last step.\n\nIf incorrect, rerun the script with a valid adminuser id\nand password.\n\n6. From the TBSM 6.1.1 Fix Pack 3 install media, copy these files\nonto the DB2 server (where the tbsmdb was initially installed,\nwhen TBSM was first setup).\n\nfrom: [Fix Pack]/TBSM/TBSMDBChecker\nto: [InstallDirectory]/tbsmdb/bin\n\nTBSM_Check_DB.bat\nTBSM_Check_DB.sh\ntbsmDatabaseChecker.xml\nTBSMDBChecker.props\n\nNOTE: The above action is only needed if you ever plan to use\nthe TBSM_Check_DB script, which will now suppress the\ndisplay of the requested user password.\n\n7. After installing this Fix Pack, end-users may need to clear their\nbrowser cache, close and re-open the browser; in order to avoid\nany issues on the client side.\n\n8. If the Impact \"Service Level Objectives (SLO) Reporting\"\nfunction was enabled, please refer to section 3.12 for additional\npost Fix Pack installation required actions.\n\n9. Please refer to section 4.0 \"Additional information for TBSM Fix Pack 3 APARS\"\nfor additional post install actions.\n\n\n3.7.2 Discovery Library Toolkit\n-------------------------\n\n1. Navigate to the DiscoveryLibrary directory.\n\n2. To install Fixpack 3, \n\nIf you are on a Windows operating system, run the following\ncommand from a prompt: \n\nsetup-dltoolkit-6.1.1-FP0003-windows_64.exe\n\nIf you are on a Unix operating system, run the following\ncommand from a prompt:\n\nsetup-dltoolkit-6.1.1-FP0003-_64.bin\n\nFor console mode, specify \"-i console\".\n\nNote: If the installer cannot find the TBSM 6.1.1 Discovery \nLibrary Toolkit, verify that the toolkit is installed and \nthat it was installed by the user that the fixpack is being \ninstalled with. If these are both okay, then set the environment\nvariable TBSM_TOOLKIT_BASE to the location of the toolkit and \nrestart the toolkit installer. For example: \nWindows:\nset TBSM_TOOLKIT_BASE=C:\\Program Files\\IBM\\tivoli\\tbsm\\XMLtoolkit\nUNIX:\nexport TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit\n\n3. The toolkit installer requires access to the database.\n\n\n4. Notes and Post-Install Considerations:\n\na) After installation is complete, you may remove\n[fixpack] to save space.\n\n5. Restart the toolkit.\n\n\n3.8 TBSM agent\n----------\n\nInstalling the TBSM agent (last updated with TBSM Fix Pack 1):\n\nThe following packages are available for download in the TBSMAgent\ndirectory on the support download site:\n\n* AIX: KR9_aix526CD-6.1.1-TIV-BSM-FP0001.tar.gz -AIX (64 bit) \n\n* Linux: KR9_lx8266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li x86_64R2.6(64 bit)\n\n* Solaris: KR9_sol286CD-6.1.1-TIV-BSM-FP0001.tar.gz -Solaris R8(64 bit)\n\n* Windows: KR9_wix64CD-6.1.1-TIV-BSM-FP0001.zip -(64 bit)\n\n* zLinux: KR9_ls3266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li S390R2.6(64 bit)\n\n\nTo install the updated TBSM agent (FP1), if not already installed:\n1. Download the appropriate agent code for your platform.\n2. Untar or unzip the file.\n3. Install the agent according to the directions in the TBSM\nInstallation Guide. This is a complete install package for the TBSM\nagent support and can be used for a fresh install of the agent.\n\nFor instructions on installing and configuring the TBSM agent, see:\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html]\n\n\n3.9 Uninstalling the Fix Pack\n-------------------------\n\nBefore uninstalling the FixPack all TBSM processes should be\nSTOPPED. The user must manually stop the TBSM processes, before \nthe uninstall of the FixPack (except for OMNIbus and DB2).\n\nAttention: Uninstall the Fix Pack with the same user that was used to\ninstall TBSM 6.1.1 GA.\n\nSilent mode and uninstall\n\n\nIf silent mode was used for the install, the uninstall will\ndefault to a silent uninstall and you must supply a response\nfile or the uninstall will fail.\n\nFor silent mode uninstalls, copy the setup_uninstall.rsp file\nfrom the Fix Pack image to the directory:\n\n/tbsm/_uninst/TBSM611_FP3\n\nand update the file with the correct information. Then launch\nthe installer specifying the file. For example:\n\nuninstall(.exe) -f /tmp/setup_uninstall.rsp\n\nNote: The response file needs to have a fully qualified path.\n\nOn the Tivoli Business Service Manager server system:\n\n1. Change to the directory: \n/tbsm/_uninst/TBSM611_FP3\n\n2. Run the uninstall command:\n\nUNIX: If you are on a Unix operating system, run the following\ncommand from a prompt.\n\n./uninstall\n\n\nWindows: If you are on a Windows operating system, run the following\ncommand from a prompt.\n\n.\\uninstall.exe\n\nFor console mode, specify \"-i console\"\n\n3. After the command has completed, run the following commands to clear\nthe server cache.\n\nLinux/AIX: /bin/clearClassCache.sh\n\nSolaris: java -Xshare:dump\n\nWindows: \\bin\\clearClassCache.bat\n\n\n\n4. Uninstall eWAS 7.0.0.35\n\nNOTE: On a \"Data server only\" environment, the TBSM 6.1.1 Fix\nPack 3 un-installer will not remove the upgraded eWAS\n7.0.0.35 Fix Pack it installed. If there are plans to, at\na future time, re-install TBSM 6.1.1 Fix Pack 3, it is\nnecessary to manually un-install eWAS 7.0.0.35. \n\nThese steps DO NOT apply to a \"Dashboard sever only\"\nenvironment or a \"Single server\" environment, where both the\nData and Dashboard are installed together.\n\nAgain, these steps are only needed on a \"Data server only\"\nenvironment. Failure to perform these actions, will prevent\nthe re-install of TBSM 6.1.1 Fix Pack 3!\n\na). Copy the uninstall-WASEmbeded.txt to a temporary location\nThe uninstall-WASEmbeded.txt file is located on:\n/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_WASFP/uninstall-WASEmbeded.txt\n\nFor example on Unix:\n/opt/IBM/tivoli/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_IAGLOBAL_COI_STEP_WASFP/uninstall-WASEmbeded.txt\n\nFor example on Windows:\nC:\\IBM\\tivoli\\tbsm\\_uninst\\TBSM611_FP3\\plan\\install\\MachinePlan_localhost\\00002_IAGLOBAL_COI_STEP_WASFP\\uninstall-WASEmbeded.txt\n\n\nOr from the TBSM 6.1.1 FP3 install media:\n6.1.1-TIV-BSM-FP0003-\\TBSM\\COI\\PackageSteps\\WASFP\\uninstall-WASEmbeded.txt\n\n\nb). Edit the uninstall-WASEmbeded.txt (on the temporary location)\n\nc). locate this line: -W product.location=\"@IAGLOBAL_WAS_HOME@\"\n\nd). Replace above line with: -W product.location=\"/tipv2\"\n\nWhere is the fully qualified directory where tipv2 located:\n\nfor example (Unix): -W product.location=\"/opt/IBM/tivoli/tipv2\"\n\nfor example (Windows): -W product.location=\"C:\\IBM\\tivoli\\tipv2\"\n\ne). Save the uninstall-WASEmbeded.txt file (on the temporary location)\n\nf). Execute the following command:\nOn Unix:\n/tipv2/WebSphereUpdateInstallerV7/update.sh -options /uninstall-WASEmbeded.txt -silent\n\nfor example: /opt/IBM/tivoli_root/tipv2/WebSphereUpdateInstallerV7/update.sh -options /tmp/uninstall-WASEmbeded.txt -silent\n\nOn Windows:\n/tipv2/WebSphereUpdateInstallerV7/update.exe -options /uninstall-WASEmbeded.txt -silent\n\nfor exampe: C:\\IBM\\tivoli\\tipv2\\WebSphereUpdateInstallerV7\\update.exe -options C:\\Temp\\uninstall-WASEmbeded.txt -silent\n\n5. Restart the Data Server and Dashboard Server.\n\n\n\nDiscovery Library Toolkit\n===================================================\n\nThe Toolkit portion of this fixpack cannot be uninstalled.\nA backup copy of the original files can be retrieved from:\n\n[InstallDirectory]/tbsm/\nXMLtoolkit/log/install/maintenance/backup/611FP0003\n\n\n\n3.10 Recovering from a failed Fix Pack install\n-----------------------------------------\n\nIf the install fails, try to uninstall in which case, it goes back to\nthe previous version. If there is no uninstall file under \n_uninst/TBSM611_FP3, then nothing really got installed and you can delete\nthe TBSM611_FP3 file and reinstall.\n\n\n3.11 Restoring failed DE upgrade from backup\n---------------------------------------\n\nTo recover a failed Deployment Engine upgrade in TBSM 6.1.1, see the\nTBSM Installation Guide at: \n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html]\n\n\n3.12 \"Service Level Objectives (SLO) Reporting\" function\n---------------------------------------------------\n\n\nThe information in this section applies only if you have deployed\nthe Impact Solution called \"Service Level Objectives (SLO)\nReporting\". The SLO function is enhanced by Fixpack 3 for:\n\n* Support of a time zone specification when creating the SLA\ndefinitions\n\n* Detection of active outages in the sample policy that reads\nfrom a TBSM Metric History database\n\n* Bug fixes and improved documentation\n\nFor this function, See the 'SLO Reporting' topic under Impact\n6.1.1 at the following url:\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html [http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/solution/imsg_slo_reporting_c.html]\n\nIf you have NOT deployed this solution, then you can skip this\nsection!\n\n\nAfter installing the Fixpack, but BEFORE restarting any SLO services:\n\n1) Update the SLORPRT database schema\n\na) You will need access to the machine where the SLORPRT\ndatabase was installed. If this database has not been\ninstalled, then the SLO solution has not been deployed\nand there is no need to continue this update to the\nschema.\n\nb) If necessary, copy files add_timezone.sql and\nupdate_views_timezone.sql from \n[InstallDirectory]/impact/add-ons/slo/db\nto a location accessible from the system you will use\nto update the database schema in the next step.\n\nc) Open a DB2 command window on a system with access to\nthe SLORPRT database and run the following commands:\n\ndb2 connect to SLORPRT user dbuser using dbpassword\n( replace dbuser and dbpassword with the\nuser/password specified in datasource\nSLOReportDatasource )\n\ndb2 -tvf /add_timezone.sql\n\ndb2 -tvf /update_views_timezone.sql\n\ndb2 connect reset\n\nWhere would be \n[InstallDirectory]/impact/add-ons/slo/db if on the \nsame machine as the Impact Data server, or the directory\nwhere you copied the files in step b if the SLORPRT\ndatabase is on a different machine\n\n\n2) Once the Fixpack is installed and the SLORPRT database\nschema has been updated, you should start any Impact\nservices configured for SLO processing. Remember to check\nthe option to start the service when the server starts,\nif that is how you originally configured the service.\n\n=======================================================================\n4.0 Additional information for TBSM Fix Pack 3 APARS:\n------------------------------------------------\n\nThe following APARs fixed in this service delivery require additional\naction by users. If your environment uses or is experiencing the\nsymptoms described, use the instructions provided to complete the fix.\n\n4.1 IV30875 - ERROR CTGBC0053E WHEN SELECTING SERVICE IN A CANVAS\nCustomers are now allowed to persist their log file settings \nwithout manually editing the server.xml file. Currently, customers\nuse the setTraceLevel script to set the maximum number of log files\nand the size of these of files using the following method:\n\n$TBSM_HOME/bin/setTraceLevel.sh data/dashboard -setTraceOutputToFile 30 40\n\nNow they will be able to persist these sizes by using the following\ncommand.\n\n$TBSM_HOME/bin/setTraceLevel.sh data/dashboard -setstartup\n\nBefore this change, the call would only persist changes to the trace\nlevel. Now it persists changes to the trace level as well as the log\nfile configurations.\n\n\n4.2 IV65545 - TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON\nRADEVENTSTORE\n\nThe following SQL statements needs to be run after FP install, against \nthe TBSM DB2 Database:\n\nCREATE INDEX RADEVENTSTORE_IDX1 ON TBSMBASE.RADEVENTSTORE(RADSERIAL) COLLECT STATISTICS\n\nThe above SQL statement can be found on the following file:\n\n./tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/AddRADEventStoreIndex.sql\n\nPlease provide the above file to the TBSM DB2 Database Administrator, \nalong with the following Notes:\n\nNotes: \n1) Use\ncat AddRADEventStoreIndex.sql | db2\nto run the SQL. The command must be run against all DB2 databases\nused for TBSM. The command does not require a server stop/start.\n\n2) The ; delimiter is not used in the AddRADEventStore.sql file\n- whether the delimiter is required or not depends on the\nconnection settings (-t option).\n\n3) Typical output from the SQL: cat AddRADEventStoreIndex.sql | db2\ndb2 => db2 => db2 => DB20000I The SQL command completed successfully.\ndb2 => db2 => DB20000I The SQL command completed successfully.\ndb2 => db2 => DB20000I The RUNSTATS command completed successfully.\n\n4) Typical output from the SQL (if the index already exists)\ndb2 => db2 => DB20000I The SQL command completed successfully.\ndb2 => db2 => SQL0605W The index was not created because an index\n\"TBSMBASE.RADEVENTSTORE_IDX\" with a matching definition already exists.\nSQLSTATE=01550\ndb2 => db2 => DB20000I The RUNSTATS command completed successfully.\n\n5) Other warning:\nSQL2314W Some statistics are in an inconsistent state. The newly\ncollected \"INDEX\" statistics are inconsistent with the existing \n\"TABLE\" statistics. SQLSTATE=01650\n\nTo address the message above, RUNSTATS Is Run after the index is\ncreated. \n\nAs well as the changes in the index there are 2 \nconfigurations changed required for this APAR\n\na) Increase the number of allowed connections for the TBSMDatabase \nData Source.\n\nThis can be done via the Impact GUI screen (Data Model) or via\nthe file tbsm\\etc\\TBSM_TBSMDatabase.ds\n\nIncrease the number from default 15 to 50 (or to limit \nrecommended by DB2 Admin)\n\nTBSMDatabase.DB2.MAXSQLCONNECTION=15\nto\nTBSMDatabase.DB2.MAXSQLCONNECTION=50\n\nIf changing via file, then a Data Server restart is required.\n\n\nb) Set the LOCKTIMEOUT in DB2 to 30 seconds. The default is -1, \nwhich mean no timeout - If you set this parameter to -1, lock \ntimeout detection is turned off. Setting to 30 seconds means \nsessions will only wait for 30 seconds for a lock. Again, this \nchange should be made in consultation with local DB2 \nAdministrator.\n\n\n=======================================================================\n5.0 List of APARs\n-------------\n\n5.1 TBSM 6.1.1 Fix Pack 3 APARs\n---------------------------\n\nThe following TBSM APARs are delivered with Fix Pack 3:\nIV60619 DATA SERVER RESTART REQUIRED TO GET A WORKING DATA FETCHER AFTER DELETION OF DEPENDENT RULE\nIV61278 RULE FILTER WITH 'NOT LIKE' ON SUMMARY FIELD MALFUNCTIONS\nIV64797 SETDBSCHEMA -F A COMMAND SHOULD ALSO RESET THE RESENRICHREADER SERVICE. : 611\nIV65695 FO_CONFIG SCRIPT DOES NOT CONFIGURE SET TBSM_B_IMPACTDB.DS DATA SOURCE PARAMETERS IN A FAILOVER ENVIRONMENT. : 611\nIV65825 XMLToolkit: Single Quotes not Encoded on IDML file generation: 611\nIV65947 ACCESSING CLOB DATATYPES IN TBSM DATABASE CAUSES DB2 ERROR, SQL0270N : 611\nIV65949 ACCESSING TBSM DATABASE VIEWS WITH IN TBSM CAUSES DB2 ERROR : 611\nIV65958 TBSM DATABASE QUERIES THAT USE MAX, MIN, DISTINCT, VIEWS CAUSES DB2 ERROR, SQL0243N : 611\nIV66535 TOOLKIT ISSUE RELATED TO STATEMENT RTERMINATION CHARACTERS: 611\nIV66950 TBSMEVENTREADER STOPS : THE REAL FIX FOR IV65545 IS TO FIX THE TXN CODE : 611\nIV71255 SELECT STATEMENTS USED FOR LOGGING PURPOSES IN DB-CLEANUP.SQL SCRIPT NEED TO BE COMMENTED OUT. : 611\nIV72005 IMPACT SLO FUNCTION\n\n5.2 TBSM 6.1.1 Fix Pack 2 APARs\n---------------------------\n\nIV62456 OOM DUE TO CIRCULAR REFERENCES\nIV62548 SAME SESSION CONTEXT USED FOR ALL RADSHELL SESSIONS, TRIGGERED FROM POLICIES\nIV60168 MODIFIED 'TBSM_NUMERICATTRIBUTEFUNCTIONS' POLICY DOESN'T GET EXPORTED\nIV56853 RADSHELL IMPORT FAILS DUE TO ORPHANED CHILD SERVICE\nIV63608 AFTER FIX FOR APAR IV32754 SEE SQLSTATE=42704 EXCEPTION FOR TBSMSCR.SCCP_COMPCLASS IN TOOLKIT LOGS\nIV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS\nIV65786 TBSM CIRCULAR REFERENCES ISSUE\nIV59886 TBSM DOES NOT RE-READ EVENT READER PROPS FILES AUTOMATICALLY WHEN YOU CONFIGURE/ENABLE EVENT ENRICHMENT\nIV61880 INFINITE LOOP IN DATA SERVER CAUSED BY MALFORMED OFFLINE TASK\nIV64950 DB2 ERROR DB2 SQL ERROR: SQLCODE=-805\nIV60750 NUMERICAL RULES NOT CALCULATED ON TBSM RESTART\nIV60961 CONCURRENTMODIFICATIONEXCEPTION THROWN WHEN YOU SELECT THE GUI FIND INSTANCE FUNCTION IN THE SERVICE AVILABILITY PORTLET\nIV61199 TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUPOUT CHANGES\nIV62273 CONCURRENTMODIFICATIONEXCEPTION ERRORS IN DASHBOARD LOG\nIV62294 NUMERIC AGGRIGATION RULE CHANGES NOT SAVED\nIV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT\nIV64933 [NetcoolTimeoutException] Log file exceptions when persisting ESDA instances\nIV65545 TBSMEVENTREADER STOPS BECAUSE EVENT PROCESSOR BLOCKING ON RADEVENTSTORE\nIV66210 NULLPOINTEREXCEPTION DISPLAYED ON SYSTEM STATUS ON FAILBACK\nIV65484 TBSM: DISPLAY NAME IN PERSISTENT SERVICE MODEL NOT BEING UPDATED\nIV68113 DELTA IMPORTS NOT WORKING FOR BUSINESS APPLICATIONS WITH IMPORTING FROM TADDM 7.3 TO TBSM 6.1.1 FP1\nIV60842 QUERY CONCATENATION PROBLEM WHEN THE PROPERTY 'DL_LIFECYCLESTATE_FILTER' IS ENABLED\nIV56450 NULL POINTER EXCEPTION AFTER CLICKING ON 'FIND INSTANCE'\nIV65991 DOCS ABOUT CONFIGURING FOR HTTP ACCESS INCORRECT\n\n\n\n5.3 TBSM 6.1.1 Fix Pack 1 APARs\n---------------------------\n\nThe following TBSM APARs are delivered with Fix Pack 1:\n\nIV21679 MODEL CLEANUP NEEDED AFTER ALIAS CHANGES\nIV30875 ERROR CTGBC0053E WHEN SELCTING SERVICE IN A CANVAS\nIV33717 ADVANCED THRESHOLD LOOKS CORRUPTED WHEN IT CONTAINS SINGLE SPACE CHARACTERS\nIV36878 Dont create rules with ' character'\nIV38053 MAINTENANCE SCHEDULE IS NOT WORKING\nIV38471 ADD LONGPARENTSERVICENAME TO THE TBSM REPORTING DATA MODEL.\nIV38574 SERVICE TREE COLUMNS DO NOT RESIZE TO FIT WHEN PORTLET RESIZES SMALLER.\nIV39167 NEED ABILITY TO LOGIN USING UID AND HAVE CN IN TIP BANNER\nIV39517 ESDA RULE DIALOG DOES NOT ALLOW PARENT TEMPLATE CHOICE\nIV39796 MAINTENANCE SCHEDULE WITH ADJACENT TIME WINDOWS CAUSING LOOP\nIV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER\nIV42657 SERVICE STATUS INCORRECT\nIV42941 COMPONENT COMPOSITES NAME TOO LONG IMPORTED FROM TADDM\nIV43098 SERVICE TREE REFRESH UPON CLICKING OR EXPANDING \nIV43165 INSTANCE PROPAGATION IN PLACE FOR SERVICES IMPORTED FROM TADDM BECAUSE OF RULE ON SCR_RETRIEVEDEPENDENTOBJECTSTEMPLATE\nIV43469 TBSM HANGS DURING AUTOPOP - DATA SERVER IN WAIT LOOP\nIV43804 VERSIONINFO ON A SPLIT SERVER, DATA SERVER IS INCOMPLETE\nIV43865 SERVICE INSTANCE CONTAINING CHINESE/NLS CHARS GENERATES ERROR TCTUI1003E\nIV44246 SOME INTERMEDIATE SERVICES MISSING EVENTS IN SERVICE DETAILS PORTLET\nIV44582 TBSM 6.1.0 CONCURRENTMODIFICATIONEXCEPTION MESSAGE DISPLAYED.\nIV45166 ITM POLICY DATA FETCHER CREATION - TBSM REMEMBERS ORIGINAL HOST DETAILS\nIV45386 THE COLOR OF MAXSEVERITYRAWEVENTS NOT CORRECTLY HANDLED.\nIV45868 THE SERVICE VIEWER DOES NOT LAUNCH ON ITALIAN CLIENT SYSTEMS\nIV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER\nIV46811 COMMA IN TEMPLATE NAME CAUSES ILOG.VIEWS EXCEPTION \nIV46876 UNABLE TO LAUNCH LEL FROM HTTP SERVER\nIV48813 ERROR POP UP WHEN SERVICE AVAILABILITY PAGE IS LAUNCHED \nIV49791 SECURITY ROLE IS NOT ACTED ON, WHEN ESDA INSTANCES ARE BELOW\nIV50625 CROSS-SITE SCRIPTING VULNERABILITY AT TBSM 6.1.0.1\nIV53791 EVENT COUNTS FOR PARENT SERVICES IS NOT ALWAYS UPDATED\nIV54197 TBSM DISCOVERY LIBRARY TOOLKIT REQUIRES UPDATES TO INTEGRATE WITH FUTURE TADDM RELEASES\nIV54587 TBSM AGENT - TEPS WORKSPACE TITLE DOES NOT MATCH WHAT IT SHOWS\nIV55756 TBSM 6.1.1 ESDA POPULATION CAUSES OUTOFMEMORY IN TBSM DATA\nIV56050 ERROR : JAVA.LANG.ERROR: JSFSECURITYPHASELISTENER - POSSIBLE\nIV56270 OUTOFMEMORY: USERPROFERENCESSTORE FOR CHILD RELATIONSHIP ATTRIBUTES IS NO\nIV57273 REQUEST ERROR IN BOTH VIEWS OF TBSM SERVICE INDICATORS\nIV59723 CROSS-SITE SCRIPTING VULNERABILITIES INVOLVING 3 JSPS\nIV61668 NETCOOLTIMEOUTEXCEPTION WHEN ESDA DISCOVERS TRIGGERS POLICY\n\n\n\nList of TBSM APARs that have updates to the documentation:\n\nIV54828 GET REQUESTS FROM DASH WIDGETS TO TBSM DATA SERVER\nThere is a new property (impact.dataproviderupdateprocessorintervalsecs), that\ndefines the interval at which the data provider fires status change updates.\n\nIV42339 CUSTOMER TRY SETTING THE PARM TO 'NULL' TURNS OUT THE DATASOURCE FILE WE SHIP FOR OUR OBJECT SERVER\nThe ObjectServer_DS.ObjectServer.FAILOVERPOLICY parm can be\nchanged (in the TBSM_HOME/etc/(TBSM or TBSM_B)_ObjectServer_DS.ds\nfile by either manually editing the file (as shown on the\nInstall Guide) or running this new command, with either of\nthe three listed values:\n\nWindows:\n\n%TBSM_HOME%\\bin\\tbsm_generic_ant_caller.bat ObjectServer_DS_config.ant \n\n\nUnix:\n\n$TBSM_HOME/bin/tbsm_generic_ant_caller.sh ObjectServer_DS_config.ant \n\nAvailable values:\n1. DISABLE - configure to only connect to Primary Object Server\n2. FAILOVER - configure FAILOVER back and forth between Object Servers but,\nonly if connection is lost. This is the Default (if NULL' is used)\n3. FAILBACK - configure to FAILBACK to Primary Object Server, as soon as it is available.\n\nIV46098 MULTIPLE TADDM MSS ASSOCIATED WITH RESOURCES WHEN TBSM IS CONFIGURED TO WORK WITH TADDM CONFIGURED FOR FAILOVER\n\n#\n# ---------------------------------------------------------------\n# (Optional) Specifies a alias for building MSS Id. By default,\n# the TADDM hostname is used. But in cases there TADDM is\n# configured in failover, objects imported from the Primary\n# TADDM and Backup TADDM will have different hostnames \n# used for building MSS. This will mean 2 MSS associated\n# with objects.\n# \n# When setting a string for the alias, use the primary taddm \n# hostname.\n#\nDL_AliasForMSS = PrimaryTaddmHostname\n#\n# Note: Launch in Context uses the MSS hostname to build the \n# sourceContactInfo value, which is used to contact the TADDM \n# server. For this reason, when TADDM is configured in Failover, \n# a front end server (load balancer) is required, to route Launch\n# In Context requests to the active server. This will ensure \n# requests are routed to the secondary TADDM server, when the \n# primary is down.\n\nIV65503 ESDA DOES NOT CLEAN OLD SERVICE IDENTIFICATION FIELDS\nThe property \"UseESDAIdentifiersOnly\" can be added, as an\nadditional parameter to the child Template, which will allow\nusers to select if they want previous event identifiers on a\nservice to be kept or erased with each invalidation. \n\nWhen set to \"true\", all previous event identifiers will be \nerased from TBSM memory model at each invalidation and the\nservice will only accept identifiers from ESDA policies or via\nSCR API. When set to \"false\", all event identifiers, old or\nnewly added will be preserved for the service. User must\nmanually delete event identifiers that they do not wish to\nkeep. This is TBSM's default behaviour. \n\nIV65786 TBSM CIRCULAR REFERENCES ISSUE\nThere will be two new properties added in TBSM_sla.props file\nthat governs the check:\n\nProperty name: impact.sla.servicetreedepthlimit\nDescription: When the data is imported from TADDM, a depth\nlimit check will be done to the corresponding service tree \nduring invalidation to ensure that the service tree has normal\nrelationship data. This property governs the depth limit for\nthe service tree. If the system detects a service tree with\ndepth level larger than the value set by this property, a \nwarning service instance will be created to warn the user to\nreview their data relationship.\n\nDefault value: 20\n\nProperty name: impact.sla.disableimportalldescendantslimitcheck\nDescription: When set to \"true\", the service tree depth limit\nwill not be checked during invalidation.\n\nDefault value: false\n\nIV62246 DATA SOURCE FAILOVER SETTINGS CLASH BETWEEN TBSM AND IMPACT\nThe APAR handles the issue of TBSM Failover settings for Data\nSources. Impact back-end java code handled whether or not\nfailover (or failback) is initiated in times of Data Source\nfailure. This back-end Impact code only uses the \nFAILOVERPOLICY settings in the .ds files\n\nThe APAR change has been in the TBSM interfaces to setting up\nData Source. There are 2 interfaces 1) GUI screen (as above)\nand 2 radshell (createDataSource and export functions). \n\n1) TBSM GUI: The TBSM GUI will now set the FAILOVERPOLICY\nsetting in the .ds file. When editing existing files, if\nno valid FAILOVERPOLICY exists, then the current\nDISABLEFAILOVER setting will be used to determine a new\nFAILOVERPOLICY setting, i.e. if no valid FAILOVERPOLICY\nexists, then if DISABLEFAILOVER is true, FAILOVERPOLICY \nwill be set to DISABLED. If DISABLEFAILOVER is false,\nFAILOVERPOLICY will be set to FAILOVER\n\nTake good note of the above. It means that existing data\nsources will have a new FAILOVERPOLICY set, when they are\nfirst saved via the GUI. Previously if FAILOVERPOLICY was\nnot valid, Impact assumed FAILOVER. But if you edit a data\nsource, and the data source has DISABLEFAILOVER = true,\nand no valid policy set, then the new value for\nFAILOVERPOLICY is DISABLED. This is correct behaviour, but\ndifferent to before. The best was to avoid any confusion,\nit to check each .ds file and ensure that a valid\nFAILOVERPOLICY is set. Do this either by editing the files\n(in which case a Data Server restart is required) or by\nopening each data source in the GUI. Not all Data Sources\nwill appear in the GUI (as some are built in). For these,\ncheck the files. If editing files, ensure no spaces at the\nend of settings. The only valid values for FAILOVERPOLICY\nare DISABLED, FAILOVER and FAILBACK.\n\n2) radshell: The Radshell interface also changes. The export()\nfunction will now export the failover policy, and the\ncreateDataSource takes a policy parameter (in place of the\nboolean disablefailover parameter), Also, the old\ncreateDataSource radshell function, will still work (for\nbackward compatibility with old exports). Note: Data Sources \nexported with IV62246 in place, will NOT work on old\nsystems-as the generated radshell command will contain a\npolicy string. \n\nThe following IMPACT APARs are delivered with Fix Pack 3:\n\nIV27869: related to PMR 15590,SGC,724 - For 6.1.1 Impact\n- The latest build should be installing version 2.2.0.2 of \nVMMObjectServerPlugin\nIV50058: IMPACT SERVER FAILS TO WORK PROPERLY WITH ANY SPACES IN CONFIGURABLE PROPS FILES\nIV58590: SNMPTRAPACTION FAILS ON 2ND TRAP WHEN PROCESSING MULTIPLES\nIV59481: UNABLE TO SEND HIBERNATIONS TO CLUSTER MEMBERS WHENEVER DIRECTSQL IS BEING USED\nIV59770: DATA ITEMS RETRIEVED FROM A DIRECTSQL'S SELECT ARE NOT ABLE TO BE UPDATED\nIV60438: IMPACT POLICY WIZARD (XML) FAILS WITH JAVA.LANG.NULLPOINTEREXCEPTION\nIV61538: MWM WINDOWS DO NOT ADJUST FOR DST\nIV61725: GETSCHEDULEMEMBER FUNCTION ISSUE\nIV63535: UNABLE TO PERFORM DECRYPTION OF INPUT VALUE - DATA SOURCE ACCOUNT GETTING LOCKED\nIV63942: SESSION.SENDCOMMAND IN A JS POLICY DOESN'T RETURNS ANY RESPONSE\nIV64075: NullPointerExceptions\nIV64837: IMPACT MWM WINDOW CREATED WITH WRONG END DATE\nIV65055: GET/SETGLOBALVARIABLES DO NOT WORK WITH ACTIVATE FUCNTION\nIV65179: LOCAL VARIABLES NOT RESTORED AFTER HIBERNATION\nIV66164: ADD RECURRING MW WINDOW\nIV67091: TBSM FAILOVER BACKUP NOT STARTED CORRECTLY IF STARTED TOO SOON\nIV67829: ITM/TEPS DATA DISPLAYED INCORRECTLY IN UI\nIV68383: DEBUG FLAG GENERATES MEMORY ISSUES WHEN NON OMNIBUS EVENTS ARE PROCESSED\nIV69164: POLICY USES HIBERNATION WILL NOT WAKE UP\nIV70836: COMMANDRESPONSE ERROR IN JS POLICY\nIV71157: ACTIVATE FUNCTION CALLED FROM WITHIN POLICY SUB-FUNCTION HAS NO EFFECT\nIV71513: EVENT IS NOT BEING PROCESSED CORRECTLY AFTER HIBERNATION\nIV73098: EVENTS OCCURING ONE HOUR BEFORE ONE TIME WINDOW GOING INTO MAINTENANCE\nIV73243: XSS ISSUE IN PROJECTNAME PARAMETER\n\nThe following IMPACT APARs are delivered with Fix Pack 2:\n\nIV18554: 511:EVAL FUNCTIONALITY HAS CHANGED FROM 4.1 TO 5.1.1\nIV23315: UPGRADE FROM IMPACT 5.1.1 TO IMPACT 6.x DISTRIBUTED [611]\nIV64152: SECONDARY NODE CAN'T BIND TO THE NAME SERVER\nIV61089: INSTALL FAILS AT STARTWAS STEP\nIV63137: IMPACT 6.1.1 REPLICATION FROM PRI TO SEC NOT WORKING\nIV62792: 1.2 GB WAS BEING FILLED BY BLANKS FROM LOGGER FUNCTION\nIV61956: DATA MODEL NOT SORTED IN ALPHABETICAL ORDER\nIV61746: IMPACT 611 FP1 INSTALL FAILS WHEN INSTALLING ON GA 611, WHICH HAS BEEN FIRST UPGRADED FROM IMPACT\nIV61399: NULL VALUE ON FIELD, DASH WIDGET SPINS TO MANY TIME MAKING DATA VEIW VERY SLOW TO VIEW.\nIV60005: DATA TYPE NOT SAVED CORRECTLY IF FEILD DELETED AND REMAINDER RE-ORDERED.\nIV60253: TEPS UIDP NOT CLEARING CACHE, CAUSING MEMORY LEAKS.\nIV58616: DIRECTSQL EXECUTE CAUSES EXCEPTION IN POLICY EXECUTION\nIV58511: EMAIL READER SERVICE DOES NOT HANDLE EMAILS THAT USE A NON-STANDARD CHARACTER SET\nIV53717: JMS MESSAGE LISTENER SERVICE NOT STOPPING PROPERLY\nIV56745: IMPACT IS UNABLE TO HANDLE EXCEPTIONS FROM A WEBSERVICES CALL\nIV56068: IMPACT THREADS INCREASING WHEN WEBSERVICES SECURITY IS ENABLED\nIV55989: HIDDEN/DELETED FIELDS NOT BEING REMOVED FORM OPERATOR VIEW\nIV50329: WEBSERVICES SECURITY NOT FUCTIONAL\nIV56541: CONFVMM4NCOS SCRIPT IN IMPACT 6.1 IS NOT WORKING AS EXPECTED\nIV47748: CAN'T LOAD WEBSERVICE LIBRARIES THAT HAVE JAVA OR JAVAX PACKAGES IN THEM\nIV55464: UNABLE TO CREATE A BUTTON ON JAZZ AFTER JAZZ FP2\nIV60923: USING THE DIRECTSQL APPROACH AND HAS IDENTIFIED THE NON-REFRESH OF THE SCHEMA ON USERNAME UPDATE IN THE DSA AS SECURITY RISK\nIV59920: NO MEANS OF ENCRYPTING IMPACT.OBJECTSERVER.SECUREPASSWORD THAT WILL ALLOW AUTHENTICATION TO AN OBJECT SERVER USING FIPS\n\nThe following IMPACT APARs are delivered with Fix Pack 1:\n\nIV11728: USING EVENTREADER PARSERESTRICTIONFILTER TO ALLOW THE USE OF GETDATE() \nIV21717: ONE TIME MAINTENANCE WINDOWS DO NOT ADJUST FOR DST\nIV22560: ANALYZE EVENT MAPPING TOOL FAILS AND HAMMERS CPU \nIV33973: JMS READER DOES NOT CONVERT ACTIVEMQMAPMESSAGE DATA FOR TRANSFER TO SECONDARY CLUSTER MEMBER\nIV34503: \"OPTIMIZE LIST\" OPTION DOESN'T REFLECT THE APPLIED CHANGES TOTHE LIST IN THE \"RESTRICT FIELDS\", WITHIN THE EVENTREADER\nIV35827: ERROR PRODUCED IN NETCOOL.LOG WHEN USING AN EVENTREADER WITH A BLANK FILTER VALUE\nIV35885: IMPACT NEEDS TO CHECK USER CREATED SERVICES, FOR WITH NAMES THAT END WITH A \"_SERVER\".\nIV35940: RETURNEVENT() FUNCTION WITHIN DATABASEEVENTREADER ADDED UNWANTED SINGLE QUOTES TO THE IDENTIFER FIELD IN THE SQL \"VIA\" STATEMENT\nIV36405: THE CONFVMM4LDAP COMMAND IS SHIPPED WITH IMPACT 6.1, BUT IS NOT DOCUMENTED\nIV36503: MWM CALENDAR: USING FORWARD BY ONE MONTH CAN LEAD TO NON-EXISTENT DATES BEING CREATED\nIV37040: USING \"NCI_COLLECT_LOGS\" UTILITY IN A GUI SERVER ONLY INSTALL DOES NOT WORK.\nIV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}\nIV37717: IMPACT 6.1 FP1 OPVIEW SOAP ERROR\nIV37759: INTERNAL DATATYPE STRING VALUE IS INTERPRETED AS AN INTEGER IF IT CONTAINS ONLY DIGITS\nIV38045: ORACLE DSA ERROR FOR COLUMN NAMES WITH \"DOUBLE-QUOTES\" AND \"NOT-ALL-CAPS\"\nIV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT\nIV38961: APPLICATION AND DATA NEEDS TO BE VALIDATED.\nIV39368: INCREASING CPU WHEN JABBERSERVICE\nIV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS\nIV41888: DISABLE THE HIBERNATION STORAGE\nIV42715: ERROR WHEN USING # IN IMPACT FILTER FROM DATATYPE DATAITEMS GUI WINDOW\nIV43030: IMPACT MISSED ENRICHING FEW EVENTS WHICH OCCURED SIMULTANIOUSLY\nIV43751: EVENTPROCESSOR IN A SECONDARY SERVER IS UN-ABLE TO CONTACT PRIMARY SERVER EVENTPROCESSOR.\nIV45068: ERROR TRYING TO CREATE SCHEDULE DATATYPE DATAITEM: ERROR MESSAGE: HTTP ERROR 500 INTERNAL SERVER ERROR\nIV45511: NEEDED 6.1.1 MWM OPVIEW POLICIES GET OVER-WRITTEN, AFTER MIGRATION FROM EITHER IMPACT 5.X OR 6.1, CAUSING MWM ISSUES\nIV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF \"ORPHANED\" FILES, CREATED FOR XINY DATATYPE\nIV45838: OBJECTSERVER CONNECTION DOES NOT RECOVER FROM BUSY PERIOD IF SELFMONITORING (DATASOURCE MONITORING) IS ENABLED\nIV46099: JMSREPLYTO WAS NOT ABLE TO SET CORRECT QUEUE.\nIV46493: ATTEMPTING TO USE DATATYPE FILTERS - \"SPECIAL\" CHARACTERS BEING CONVERTED TO HTML ENCODING THAT BREAKS OUTGOING SQL.\nIV46696: LIMITING THE NUMBER OF CONNECTIONS THAT IMPACT OPENS TO JMS\nIV46729: TOPOLOGY WIDGET KEEPS THE OLD LINKS BETWEEN NODES AND DOESN'T CLEAR IT, RESULTING IN AN INCORRECT RELATIONSHIP\nIV46799: FUNCTION IS NOT DEFINED BEFORE CALL\nIV47058: MWM POLICY SETS SUPPRESESCL FIELD TO 6 IMMEDIATELY AFTER SETTING TO 1.\nIV47799: SELECTING 2 KEY FIELDS IN DATA TYPE ON DEFAULTOBJECTSERVER DOESN'T WORK\nIV47904: EIC 'TEST SQL' FAILS DUE TO UNSCAPED CHARACTERS\nIV47988: SETTING THE WSSETDEFAULTPKGNAME VALUE GLOBALLY DOESN'T WORK WHEN THE WSINVOKE FUNCTION IS INSIDE A POLICY FUNCTION\nIV48113: SLOW RESPONSE ON THE POLICY PAGE WHEN ATTEMPTING TO OPEN A LARGE NUMBER OF POLICIES VIA THE GUI\nIV50464: JMS TIMEOUT CAUSES POLICY ASSIGNED TO OPERATORVIEW EXECUTE TWICE\nIV50932 MAINTENANCE WINDOW EVENT SHOWED STATUS 'NORMAL' - parent apar cancelled\nIV51062: DB2 DSA FAILS TO QUERY COLUMN NAMES WITH \"DOUBLE-QUOTES AND NOT-ALL-CAPS\"\nIV53483: CALLDBFUNCTION USAGE IN ORACLE DATABASE WITH FILTER 0=1\nIV53810: I10N - TRANSLATION ISSUE\nTranslation issues in XinY policy and in Browse and Cancel buttons have been fixed.\nIV53818: ISSUES WITH INTEGRATIONS ON 611\nWeb services related issues have been fixed.\nIV53822: FIXES FOR HA IN 611 FP1\nIssues related to Omnibus failover/failback have been fixed.\nIV53824: FIXES IN IMPACT SCRIPTS FOR 611 FP1\nIssues in Impact scripts nci_export, nci_import and nci_encryptpolicy have been fixed.\nIV53825: THIS APAR INCLUDES FIXES FOR DATA MODEL ISSUES IN 611 FP1\nIV53826: FIXES ISSUES IN 611 FP1 WITH POLICIES\nIV53827: THIS APAR FIXES SERVICES RELATED ISSUES IN 611 FP1\nIV53836: FIXES UI DATA PROVIDER ISSUES IN 611 FP1\nIV54939: A MISSING $IMPACT_HOME/LOGS/INSTALL/ DIRECTORY WILL RESULT IN THE NCI_CONFIGURATION_UTILITY PROBLEM\nIV55776: UI PROVIDER ENHANCEMENTS IN 611 FP1\nThis contains UI Provider enhancements where the user can show status and percentage in topology,\ntree, table, and list widgets\nIV55778: JABBER UPDATES IN 611 FP1\nThis contains Jabber Updates to use the smack library. \nIV55779: ADDITIONAL POLICY FUNCTIONS IN 611 FP1\nThis contains additional policy functions to escape special characters and filter malicious \ncontent in strings.\nIV55780: DSA ENHANCEMENTS IN 611 FP1\nDSA enhancements that alert the user when users switch between failover and\nfailback configuration. Improved handling of network timeouts.\nIV55781: SERVICEABILITY IMPROVEMENTS IN 611 FP1 \nServiceability improvements, which include improved error messages for\nGetHTTP and services.\n\n\nList of Impact APARs that are marked as updates to the documentation:\n\nIV20165: E-MAIL READER DELETES E-MAILS AFTER READING THEM\nThe email reader service reads incoming email, and runs\npolicies based on the contents of the email. To stop the\nemail reader from deleting emails after you read them, add the\nfollowing property to the .props file.\n.deleteonread=false\n\nWhere is the email reader service name.\nRestart the service.This only works for IMAP email servers.\n\nIV37369: OBJECT.PROTOTYPE.TOSTRING.CALL(OBJ) RETURNS {}\nIf a customer is using Object.prototype.toString.call(obj) in\na javascript policy, and wants to follow the javascript\nstandard, he can add the following property to\nNCI_server.props file - \n\nimpact.featureToStringAsSource.enabled=false\n\nWhen the property is set to false, the data follows the\nJavaScript standard and the data output by the Log function\nis not the same as in IPL. To make the output the same in\nJavaScript and IPL, make the value true but this does not \nfollow the javascript standard.\n\nIV38585: NCI_EXPORT NOT EXITING CLEANLY WHEN RUNNING ON A NON PRIMARY IMPACT\nNCI_EXPORT restriction: nci_export will not execute on the\nnon-primary member of a cluster.\n\nhttp://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/admin/imag_tools_c.html [http://www-01.ibm.com/support/knowledgecenter/SSSHYH_6.1.1.3/com.ibm.netcoolimpact.doc/admin/imag_tools_c.html] \n\nIV40158: ABILITY TO CHANGE NUMBER OF POLLING INTERVALS \nIn order to make the readEventBuffer store the events for a\nlonger interval, the number of intervals can be updated. The\ndefault number is 3.\n\nAdd the following property to the\n_.props. file \n(eg NCI_omnieventreader.props file)- \n\nimpact..numreaderbuffer=4\n\nThe default value for this property is 3.\n\nIV40179: ERROR MESSAGES FIRST APPEAR ON 6.1 AND 6.1.1 DURING STARTUP, DUE TO THE FACT THE\nNAMESERVER IS NOT INITIALISED YET\nWhen the Impact Server is started during the installation,\nthe following message is displayed in the netcool.log file:\n\nUnable to login to configured name servers host , port \n\nThe message occurs because the Name Server can take time to\ninitialize while Netcool/Impact starts. You can ignore this\nmessage. It is normal and it disappears when the Name Server\nserver is initialized.\n\nIV43157: ALL SERVERS IN A CLUSTER ARE REQUIRED TO USE THE SAME ADMIN UID AND PASSWORD\nIf you are configuring the Tivoli® Integrated Portal profile\nfor a cluster of servers, you must use the same user name and\npassword for all the servers in the cluster.\n\nIV44875: SET JREXEC TO LOG TO FILE IS NOT WORKING\nDocumentation has been updated on JRExec server logging.\n\nIV45481: NO DOCUMENTATION ON THE REQUIRED HTTP AUTHENTICATION FOR THE IMPACT 6.X WEBSERVICES\nDocumentation has been updated for Impact web services.\n\nIV45569: DOCUMENTATION NEEDED ...HOW TO HANDLE BUILD-UP OF \"ORPHANED\" FILES, CREATED FOR XINY DATATYPE\nA new policy has been added - XINY_DataType_PurgeData - to\nremove aged data items. More information can be found in the\nTroubleshooting Guide.\n\nIV46185: JAVACALL METHOD FAILS WITH JAVA.LANG.ILLEGALACCESSEXCEPTION-CANNOT ACCESS A MEMBER OF CLASS JAVA.UTIL.HASHTABLE$HASHITERATOR\nDocumentation has been updated for the NewJavaObject function.\n\nIV46512: THERE'S A NEED TO DOCUMENT THE FACT THAT ONE NEEDS TO RESTART IMPACT FOR JVM TO RELEASE ANY LOADED JAR FILES FOR WEBSERVICES\nDocumentation has been updated to specify the procedure of\nwhat to do when a user compiles a wsdl file using classes\nfrom a previously compiled file.\n\nIV47057: DATA TYPE QUERY CACHING RETURNING BAD DATA\nDocumentation on Data caching information has been updated.\n\nIV47454: INSTRUCTIONS ON HOW TO RUN UPGRADE PACAKAGE FOR IMPACT 6.1.1 ON CONSOLE OR SILENT MODE\nDocumentation on How to upgrade from Netcool/Impact 6.1 in\nconsole mode has been added.\n\nIV50673: INCORRECT/UNCLEAR DOCUMENTATION FOR HANDLING EXCEPTIONS\n\nIV50776: DURING UPGRADE WE WILL OVER WRITE ANY CUSTOMIZED MWM POLICIES WITH NEWER THE MWM DEFAULT POLICY'S VERSIONS\n\nIV51431: NEED TO DOCUMENT THAT DOT NOATION CAN NOT BE USED IN THE NAMING OF POLICIES, SERVICES, DATA TYPES, DATA SOURCES, AND PROJECTS.\nDocumentation has been updated to note that Dot notation \".\" \ncan not be used in the naming of POLICIES, SERVICES, DATA\nTYPES, DATA SOURCES, AND PROJECTS.\n\nIV52651: DATABASEREADER NOT WORKING PROPERLY WHEN USING GETUPDATES ON DATABASE TABLE'S TIMESTAMP FIELD\nDatabase event reader service\n\nAn additional property can be added to the NCI_XXX.props file\nin order to match the the date and time format of the\ntimestamp field in the external database. Where NCI is the\nname of the impact instance and XXX is the name of the\ndatabase event reader. \n\nAn example of this property is: \nimpact.XXX.formatpattern=dd-MMM-yy hh.mm.ss.SSS aaa\n\n\n5.4 Tivoli Integrated Portal\n------------------------\n\nThe Tivoli Integrated Portal 2.2.0.15 (version 2) should be installed\nafter installing this FixPack.\n\nThe following other components are updated with that version\nof TIP:\n\nDriver tip_2.2.0.15 (version 2)\n* This driver includes Java SDK version 1.6 SR16 Fix Pack 1\n* This driver includes eWAS 7.0.0.35\n* Browser support\nMicrosoft Internet Explorer version 10 & 11\nFirefox Extended Support Release (ESR) version 24 & 31\n\nSee Fix Central for availability:\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]\n\nNOTE: If TIP 2.2.0.15 (version 1) was previously installed, you may\nencounter the following issues. Please refer to the following\nTechnotes for resolution:\n\n- TIP Portlet blank or does not load after TIP 2.2.0.15\ninstallation:\nhttp://www.ibm.com/support/docview.wss?uid=swg21696426 [http://www.ibm.com/support/docview.wss?uid=swg21696426]\n\n\n- TIP chart portlet blank if TBSM Service Admin page is closed and\nre-opened:\nhttp://www.ibm.com/support/docview.wss?uid=swg21696424 [http://www.ibm.com/support/docview.wss?uid=swg21696424]\n\n\n\n5.5 Jazz for Service Management (JazzSM)\n------------------------------------\n\nIf JazzSM UI Services (DASH) is being used to visualize TBSM service model\ndata, then the latest JazzSM fix pack should be installed after installing this\nTBSM FixPack. See Fix Central for availability:\n\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Jazz+for+Service+Management&release=All&platform=All&function=all]\n\n\n\n=======================================================================\n6.0 New support and features\n------------------------\n\n6.1 TBSM 6.1.1 Fixpack 3\n--------------------\nFix Pack 3 includes the following enhancements:\n\n1) Template Editor: sort items in \"Rules\" table\n\nAdjusting the logic that handles the order of the rules displayed in\nthe table on the Rules tab. The following are the new rules each\nof the columns will adhere to:\n\nType column\n> use the same icon as the toolbar action that created the rule\n> tooltips describe the rule's type\n\nRule Name column\n> all rule names are now sorted A-Z \n> A-Z ordering maintained as rules are created and/or deleted \n> tooltips describe the rule's type; same as Type column\n> the display order will not be customer configurable\n\nRule Settings column\n> minor styling tweaks to assist readability\n\nThe above enhancement is specific to the TBSM console\n\n2) Tree Template datasets: enable use of internal status attributes in\n\"Tree Template Editor\"\n\nExtended the capability of the Tree Template datasets by allowing\nTBSM internal status attributes to be selected on the editor UI's\nTemplate Rule Mapping section.\n\nWhen Tree Template Viewed in TIP-based Service Tree\n\nWithout processing by the customization policy, these new status\nattributes will display as the standard TBSM status values: \n0.0, 3.0, or 5.0. \n\nThe above, enhances the TBSM Data Provider function and benefits\nthe DASH users.\n\n3) Datasets need a parameter to optionally exclude \"starting\" or\n\"container\" services.\n\nWith the addition of the Tree Template datasets in TBSM 6.1.1\nFixpack 1, we now have more situations where the administrator may\nwish to exclude the starting or container service from a view.\n\nThe above, enhances the TBSM Data Provider function and benefits\nthe DASH users.\n\n4) Support parameter to filter datasets in TBSM_Services datasource\nby template\n\nThe parameter would be available on the datasets in the \nTBSM_Services datasource, which includes the \"All_TBSM_Services\"\nand \"TBSM_Urgent_Services\" datasets\n\nThe above, enhances the TBSM Data Provider function and benefits\nthe DASH users.\n\n5) \"UrgentServices\" dataset added\n\nThis new dataset makes the service model data that was displayed\nin the legacy Urgent Services portlet available for display using\nthe List and Table widgets.\n\nThe above, enhances the TBSM Data Provider function and benefits\nthe DASH users.\n\n6) Managing Dataset Dynamic Updates\n\nAll datasets available from the TBSM UI Data Provider automatically\nsend updates when the content changes. This is the recommended usage\nof the TBSM datasets, but there may be scenarios where the user\nwould like to turn off the dynamic updating.\n\nThe above, enhances the TBSM Data Provider function and benefits\nthe DASH users.\n\nMore information can be found in the new \"Dynamic Updating and the\nTBSM UI Data Provider\" document on the TBSM Advanced Topics page at\nthe TBSM developersWorks site\n\n7) Tivoli Netcool/Impact provides new property to ascertain which Data\nProvider field is used, when retrieving ITM data from the REST\nService\n\n8) Enhancements to the Impact Solution called \n\"Service Level Objectives (SLO) Reporting\". The SLO function\nis enhanced by Fixpack 3 for:\n\n* Support of a time zone specification when creating the SLA\ndefinitions\n\n* Detection of active outages in the sample policy that reads from\na TBSM Metric History database\n\n* Bug fixes and improved documentation\n\n\nSee the Advanced Topics at the TBSM developerWorks site for new and\nupdated information:\n\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics] \n\n\n6.2 TBSM 6.1.1 Fixpack 2\n--------------------\n\n1) NUMERICAL RULES NOT CALCULATED ON TBSM RESTART\nNumerical Aggregation rules are triggered by a child metric rule\nchange, i.e. OverallAttribute. When the status of a child changes, the\nOverallAttribute metric rule's value will change and any Numerical \nAggregation rules, based on OverallAttribute, will be recalculated. \nWhen TBSM is restarted, only services which have related existing \nevents will have their status recalculated. Therefore not all Numerical\nAggregation rules (based on OverallAttribute) will be recalculated on \nTBSM restart, as some services will be green. \n\nThis may not be the desired outcome. On restart, it may be required\nthat all Numerical Aggregation rules are restarted. New functionality \nhas been provided for such a scenario, by forcing a bubble up of state \nnodes. The code can be triggered from a policy, for leaf nodes\nonly, or for all, as shown here: \n\nUSE_SHARED_SCOPE;\n\nType=\"StateModel\";\nFilter = \"RECALCSTATENODESLEAF\";\nlog(\"Recalc Leaf Node Only. Policy Start.\" );\nGetByFilter(Type, Filter, false); \nlog(\"Recalc Leaf Node Only. Policy Finish.\" );\n}\n\n\nUSE_SHARED_SCOPE;\n\nType=\"StateModel\";\nFilter = \"RECALCSTATENODESALL\";\nlog(\"Recalc All Nodes. Policy Start.\" );\nGetByFilter(Type, Filter, false); \nlog(\"Recalc All Nodes. Policy Finish.\" );\n}\n\nThe above policy code needs to be scheduled from Impact Services on\nstartup.\n\n\n\n2) TBSM SLAM EVENTS ONLY GENERATED IF THE RULE OUTPUT CHANGES\nIf a client wants SLAM event text for a Numerical rule, to update\n(even if it's value does not change), the following parm needs to be\nun-commented and set to \"true\"\n\n#If true then send SLAM events, even when the value of a Metric rule does NOT change.\n#Default is false.\n#Omnibus de-duplication will handle the rest.\n#impact.sla.sendslameventsformetricrulealways=true\n\n\n\n6.3 TBSM 6.1.1 Fixpack 1\n--------------------\n\n1) The BSM_Templates.radsh defines service templates for common TBSM services.\nIt was executed when you installed the TBSM GA release(not during the fixpack \ninstall). It's default template rules propagate child status to the parent \nservice based on child template changes. The script has been updated to set \nthe propagation type to instance propagation. When the child service status \nchanges, it will propagate the change to the parent service regardless of\nwhich child template rule caused the status change. See the Service \nConfiguration publication for more information about the aggregation rule \noption.\n\nTo update the rules with the instance propagation option in your current \ninstallation, you can invoke the \n$TBSM_HOME/install/BSM_Templates_updatepropation.radsh script.\n\nIf you re-execute the $TBSM_HOME/install/BSM_Templates.radsh script \nto re-create the templates, the rules will be configured with \nthe instance propagation option.\n\n\n2) The recommended version of JRE plugin is Sun JRE 1.7.0_51 or 1.8 for \nInternet Explorer and Firefox.\n\n3) Additional toolkit customization has been made. To pick up these\nchanges, run the following commands on the Data Server:\n\nWindows:\n\ncd %TBSM_HOME%\\install\ntype BSM_TemplateUpdates611FP0003.radsh | %TBSM_HOME%\\bin\\rad_radshell\n\nUNIX:\n\ncd $TBSM_HOME/install\ncat BSM_TemplateUpdates611FP0003.radsh | $TBSM_HOME/bin/rad_radshell\n\n4) As noted in the following Technote, When configuring pages in DASH \n(JazzSM) for TBSM datasets, it is often desirable to create them\nin a development environment and then later move them to\nproduction, perhaps via a test environment. With this Fix Pack and\nin conjunction with JazzSM 1.1 Fix Pack 2, there is no need to create\ntwo connections any longer.\n\nhttp://www.ibm.com/support/docview.wss?uid=swg21660077 [http://www.ibm.com/support/docview.wss?uid=swg21660077]\n\n5) TBSM 6.1.1 Fixpack 1 will support the use of a rich hover function in\nDASH (JazzSM). The TBSM UI data provider will now send the information\nneeded in order for a DASH user to configure a widget for rich hover \nsupport. To enable the rich hover in DASH you must:\n\nConfigure TBSM 6.1.1 to collect the registry information required to\nsupport the rich hover in TBSM 6.1.1. This configuration is documented\nat http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/customization/bsmc_oslc_config_dataserverconfg.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/customization/bsmc_oslc_config_dataserverconfg.html].\nThe rich hover option will not be available in DASH for widgets\nconfigured with a TBSM dataset if the oslcconfig has not been run.\n\nConfigure DASH (UI Services) for access to JazzSM Registry Services.\nConfiguration of the required property is described at \nhttp://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/dash_t_twl_uipreview_resource_reg.html [http://www.ibm.com/support/knowledgecenter/SSEKCU_1.1.0.3/com.ibm.psc.doc_1.1.0.3/tip_original/dash_t_twl_uipreview_resource_reg.html].\n\nNote that if enabled in DASH, rich hover will be shown for the same\nservices that support the rich hover in the TBSM 6.1.1 console. If \nconfigured for a widget, and there is no rich hover information, \nthen the flyover on the DASH widget will show nothing. Also note \nthat the DASH environment requires Single Sign On be configured \nbetween the various components required to gather the preview \ninformation (DASH, TADDM, ITM, etc.)\n\n6) TBSM 6.1.1 Fixpack 1 adds a new UI data provider data source that\nprovides new datasets corresponding to the customer's tree templates.\nThis allows the same data to be visualized in the legacy Service Tree\nas well as on a JazzSM/DASH page.\n\n\n6.4 Additional Browser Support with Fixpack 3\n\nNone!\n\n6.5 Additional Browser Support with Fixpack 2\n-----------------------------------------\n\nTBSM 6.1.1 supports FF ESR 10 and FF17 with Fix Pack 1 on TIP 2.2.0.11 (or below).\n\nThis Fix pack supports Internet Explorer 9(IE9) in \n\"Internet Explorer 9\" browser mode which is the default mode, not \nin \"Internet Explorer 9 Compatibility View\" browser mode.\nThe document mode is automatically set by TIP and should remain\n'IE7 standards'.\n\nIBM strongly recommends updating to TIP 2.2.0.15 version 2 (v2) if\nsupport is required for FF ESR 24/31 and/or IE10/11\n\nSee Fix Central for availability:\nhttp://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Integrated+Portal&release=2.2.0.15&platform=All&function=all]\n\n\n\n6.6 eWAS Fixes and Upgrades\n-----------------------\n\nPlease Note: The TBSM 6.1.1 Fix Pack will upgrade WebSphere (eWAS) on the Data\nserver automatically, to version 7.0 Fix Pack 35 (7.0.0.35) but, only if the Dashboard\nserver is not installed on that environment. If the Dashboard server is installed on the\nsame server (in the case of a single server environment), the eWAS will not be upgraded.\n\neWAS upgrade, on the TBSM Dashboard server and on \"Single server\" environments, will\ntake place when TIP 2.2.0.15 is applied.\n\nIf un-installing TBSM 6.1.1 Fix Pack, refer to section 3.9 \"Uninstalling the Fix Pack\"\nto manually remove eWAS 7.0.0.35 (on Data server only environments!).\n\n\n6.7 OMNIbus 8.1\n-----------\nTBSM 6.1.1 Fix Pack 1 supports the use of OMNIbus 8.1. But, please note that\nOMNIbus 8.1 is a separate install, requiring additional configuration changes to\nmake it work with TBSM. Refer to \"IBM Tivoli Netcool OMNIbus Considerations\" section\nof the \"Exploring TBSM\" Guide:\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_c_netcool_omnibus.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_c_netcool_omnibus.html]\n\nIf using OMNIbus 8.1, IBM recommends upgrading to the latest 8.1\nmaintenance level (at the moment, Fix Pack 2).\n\nIf using JazzSM/DASH to display TBSM resources, the Event Viewer and/or AEL may fail to display the appropriate\nTBSM events if (1) a Data Source is not setup to point to TBSM's OMNIbus and (2) the custom TBSM filters and views are\nnot defined to WebGUI. To setup the WebGUI views, it will be required to copy the following file from\nthe TBSM Dashboard server to a temporary location on the JazzSM server:\n\n/tipv2/profiles/TIPProfile/installedApps/TIPCell/isc.ear/sla.war/install/webtopcore/create_tbsm_views.xml\n\nIn addition to copying the file to the JazzSM server, it is necessary to execute the runwaapi command, to load filters/views\nthe WebGUI. On the JazzSM/DASH server, execute the following command:\n\n/netcool/omnibus_webgui/waapi/bin/runwaapi -file create_tbsm_views.xml -user -password \n\nPlease refer to the integration document found in \"Advanced Topics\"\nat the TBSM developerWorks site, for this and other topics:\n\nTBSM developerWorks Advanced Topics: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Business%20Service%20Manager1/page/Advanced%20Topics]\nIntegration document: https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=7d5ebce8-2dd8-449c-a58e-4676134e3eb8#fullpageWidgetId=Wea1cb2531f10_4ccd_99d7_6ab0334cb21f&file=c6d51b71-362e-44be-8aa2-650da0918ac7 [https://www.ibm.com/developerworks/community/groups/service/html/communityview?communityUuid=7d5ebce8-2dd8-449c-a58e-4676134e3eb8#fullpageWidgetId=Wea1cb2531f10_4ccd_99d7_6ab0334cb21f&file=c6d51b71-362e-44be-8aa2-650da0918ac7]\n\n\n6.8 DB2 \n---\nStarting with TBSM 6.1.1 Fix Pack 2, TBSM supports the use of DB2\nversion 10.5.3\n\n\n6.9 TADDM 7.3 Integration\n---------------------\nFor import of Business Applications from TADDM 7.3 to TBSM 6.1.1, the\nproperty com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility\nmust be set to \"true\" in collation.properties file (located under\ntaddm/dist/etc). This will be true by default for upgraded TADDM 7.3\nservers. It is false by default for fresh TADDM 7.3 installs. \n\nNote: TADDM restart is required after property modification.\n\nIf com.ibm.cdb.serviceinfrastructure.earlier.ver.compatibility is \nflipped from false to true, then all Business Applications need to be \nre-build, to regenerate backward compatible Business Applications. This \ncan be done by either waiting for scheduler to process all Grouping \nPatterns (and recreate new and old Business Applications) or by manually \nexecuting (all or selected) Grouping Patterns from TADDM UI (or command\nline).\n\n\n=======================================================================\n7.0 Known issues - \n------------\n\n7.1 Some date options in TBSM Reports do not work\n\nWhen specifying the date parameters for reports, some options \nlike \"last 30 days\" do not work. However, one can get this data\nfor the reports by selecting the Date Range and choosing the \ndates from the calendar. Below is a link to the TBSM reports in\nour Service Configuration guide which outlines how to run reports.\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/ServiceConfigurationGuide/bsmu_rept_view_reports.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/ServiceConfigurationGuide/bsmu_rept_view_reports.html]\n\n\n\n7.2 Issues creating wire between Service Tree and Active \nEvent List (AEL)\n\nIf the user creates a wire between the Service Tree and AEL\nwhen a page is first created, the wire does not work. The\nworkaround for this is to create a wire by editing the page\nafter the page has been created and saved. \n\n\n\n7.3 TBSM Agent Chart title differs from name in the \ndrop down list \n\nName displayed at the top of a TBSM Agent Chart differs from\nthe name of that chart in the drop down list. For eg,\nthe chart name in the drop down list is \"kr9_TBSM Service Status\" \nand the name shown at the top of the chart is \"Kr9:KR91003\". \nThe name at the top can be changed to display the same name \nas the drop down list by going to Preferences and changing \nthe chart name.\n\n\n\n7.4 Minimize-restore does not restore to correct size for\nService Navigation->Data/Data Fetchers on Internet Explorer(IE)9 \n\nIn the Service Navigation->Data/Data Fetchers portlet, after the \nminimize option has been exercised to minimize the portlet, the \nportlet is not resized correctly after using the 'restore' option.\nThe window resizes to a smaller size. This is an issue on\nInternet Explorer(IE) 9 but not on Firefox or on Internet \nExplorer(IE) 8. In order to go back to the original size, \nselect 'maximize' and 'restore'. \n\n\n\n7.5 Portlets covering content in a free form page\n\nWhen creating free form pages, the Service Viewer and Active Event \nList(AEL) portlets will always be on top of any content. This can \ninterfere with page layout and editing of portlet preferences. \nTo alleviate this issue, it is best to place these portlets \nonto the created page last to avoid having other content covered \nby them. If a page requires editing and contains Service Viewer \nor Active Event List portlets, it may be necessary to move \nthose portlets out of the way before editing preferences of \nother portlets.\n\n\n\n7.6 Creation and deletion of Services and Templates that contain\nspecial characters\n\nDue to new security additions the deletion of services and templates\nthat contain the characters '+', '&', '<','>','%',' \" ', is not\npermitted through the browser. Some of these characters are\npermitted on the creation of services, as services can still be\ncreated with these through auto population and importing. The \ndeletion of these services will now have to be carried out\nthrough the radshell command deleteServiceInstance. \n\nMore information on the command can be found here.\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/adminguide/bsma_shlr_service_delete.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.0/com.ibm.tivoli.itbsm.doc_6.1/adminguide/bsma_shlr_service_delete.html]\n\n\n\n\n7.7 WEBSERVICES SECURITY NOT FUNCTIONAL\nIf using WebService Security when making a WebService call,\n(callProps.EnableWSS=true), the jar file \ntipv2/plugin/org.apache.axis2.jar must be replaced by the jar\nfile tbsm/lib3p/org.apache.axis2-woden.jar and the newly replaced\nfile must be renamed to org.apache.axis2.jar.\n\nRestart is required.\n\n7.8 If using WEBSERVICES SECURITY (WSS) user authentication, then the\nimpact/dsa/wsdsa/wss/conf/wscb.properties needs to be altered to\nonly have one entry. If there is more than one entry in the file,\nonly the uid.1 and pwd.1 will be read\n\n7.9 Microsoft Internet Explorer 11.\nIE11 (supported only with TIP 2.2.0.15) may cause unexpected\nbehaviour in the Policy Editor, whereby the Policy List panel\ndisappears when the Project drop-down menu is selected. To\ncircumvent this, simply click on a different project in the Project\ndrop-down list and then click again on the desired project, to\nrestore the correct layout\n\n7.10 With certain Solaris installations the Event Summary portlet\n(Administration -> Service Administration -> Services) may fail to\nrender and cause an Out Of Memory (PermGen) exception (as seen in\nthe TIP trace log:\n\"java.lang.OutOfMemoryError: PermGen space exception\")\n\n\nSolution: \n1. Stop TBSM (kill the hung server if necessary).\n\n2. Goto the $TBSM_HOME/tipv2/profiles/TIPProfile/config/cells/TIPCell/nodes/TIPNode/servers/server1\ndirectory and make a backup of the server.xml file.\n\n3. Open the server.xml file for editing and in the jvmEntries xmi\ntag modify the genericJvmArguments attribute to read something\nlike this, where these two PermSize and MaxPermSize parms are\nbeing added (if other parms are already code, please preserve\nthose parms and just insert the two new ones): \n\ngenericJvmArguments=\" -XX:PermSize=256m -XX:MaxPermSize=512m -XX:+DisableExplicitGC\"\n\n4. Save the file and restart TBSM.\n\n\n7.11 TIP Portlet blank or does not load after TIP 2.2.0.15 installation\nRefer to the following Technote for resolution:\n\nhttp://www.ibm.com/support/docview.wss?uid=swg21696426 [http://www.ibm.com/support/docview.wss?uid=swg21696426]\n\nNOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)\n\n7.12 TIP chart portlet blank if TBSM Service Admin page is closed and \nre-opened\nRefer to the following Technote for resolution:\n\nhttp://www.ibm.com/support/docview.wss?uid=swg21696424 [http://www.ibm.com/support/docview.wss?uid=swg21696424]\n\nNOTE: The above issue is resolved also in TIP 2.2.0.15 (version 2)\n\n7.13 TBSM integration with ISM is no longer operational and will be\nremoved from the next TBSM version 6.1.1 Fix Pack. \nThis modification is due to changes in the supported versions of\nITCAM for Transaction / ISM.\n\n7.14 Java Security Warnings\nWith the ever changing security improvements to both the browsers\nJava Runtime Environment (JRE), clients are now more likely to see\nwarning messages about untrusted connections or invalid\ncertificates. To avoid those issues, clients can replace the IBM\nHTTP Server SSL certificate with an SSL certificate signed by a\nthird-party CA. For guidance on that task, refer to the following\nTechnote:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21424371 [http://www-01.ibm.com/support/docview.wss?uid=swg21424371]\n\n=======================================================================\n8.0 Copyright and trademark information\n\nhttp://www.ibm.com/legal/copytrade.shtml [http://www.ibm.com/legal/copytrade.shtml]\n\n8.1 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 may\nmake improvements and/or changes in the product(s) and/or the program(s)\ndescribed 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\nIntel®, Intel logo, Intel Inside®, Intel Inside logo, Intel® Centrino®,\nIntel Centrino logo, Celeron®, Intel Xeon®, Intel SpeedStep®, Itanium®,\nand Pentium® are trademarks or registered trademarks of Intel\nCorporation or its subsidiaries in the United States and other\ncountries.\n\nOther company, product, or service names may be trademarks or service\nmarks of others.\n\nPlease read THE IBM Tivoli Business Service Manager NOTICES AND\nINFORMATION in the file notices1.txt included in this Fix Pack before\nyou proceed with the download and installation of this Fix Pack. You can\nfind the additional notices file on the same web page as this Fix Pack.\n\n8.2 THIRD-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 certain\nsoftware code. The relevant terms and conditions, notices and other\ninformation are provided or referenced below. Please note that any\nnon-English version of the licenses below is unofficial and is provided\nto you for your convenience only. The English version of the licenses\nbelow, provided as part of the English version of this file, is the\nofficial version.\n\nNotwithstanding the terms and conditions of any other agreement you may\nhave with IBM or any of its related or affiliated entities (collectively\n\"IBM\"), the third party software code identified below are \"Excluded\nComponents\" and are subject to the following terms and conditions:\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 AND\nTHE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS\nFOR A PARTICULAR PURPOSE\n* IBM will not be liable to you or indemnify you for any claims related\nto the Excluded Components\n* IBM will not be liable for any direct, indirect, incidental, special,\nexemplary, punitive or consequential damages with respect to the\nExcluded Components.\n\n8.3 Apache Woden Distribution\n\n===============================================\n== NOTICE file corresponding to the section 4 d of ==\n== the Apache License, Version 2.0, ==\n== in this case for the Apache Woden distribution. ==\n===============================================\n\nThis product includes software developed by\nThe Apache Software Foundation (http://www.apache.org/ [http://www.apache.org/]).\n\nThis product also includes software developed by :\n\n- IBM Corporation (http://www.ibm.com [http://www.ibm.com/]),\nWSDL4J was the initial code contribution for the Apache Woden\nproject and some of the WSDL4J design and code has been reused.\n- The W3C Consortium (http://www.w3c.org [http://www.w3c.org/]),\nCommon W3C XML Schema and DTD files are packaged with Apache Woden.\n\nPlease read the different LICENSE files present in the root directory of\nthis distribution.\n\n===========================================================================\nApache License\nVersion 2.0, January 2004\nhttp://www.apache.org/licenses/ [http://www.apache.org/licenses/]\n\n\n===========================================================================\n\nWODEN SUBCOMPONENTS:\nFor any subcomponents included with the Woden source code that contain \nseparate copyright and license terms, their License information is appended \nbelow, in this file.\nFor any binary subcomponents redistributed with Woden under separate \nlicenses, their license files are included alongside those binary packages \nin the Woden release files (for example, alongside the dependant jar files\nin the /lib directory of the Woden zip file).\n\n===========================================================================\n\nFor the W3C schema and DTD files in the org.apache.woden.resolver package:\n\nW3C® SOFTWARE NOTICE AND LICENSE\nhttp://www.w3.org/Consortium/Legal/2002/copyright-software-20021231 [http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231]\nThis work (and included software, documentation such as READMEs, or other \nrelated items) is being provided by the copyright holders under the following \nlicense. By obtaining, using and/or copying this work, you (the licensee) agree \nthat you have read, understood, and will comply with the following terms and \nconditions.\n\nPermission to copy, modify, and distribute this software and its documentation, \nwith or without modification, for any purpose and without fee or royalty is \nhereby granted, provided that you include the following on ALL copies of the \nsoftware and documentation or portions thereof, including modifications:\n\nThe full text of this NOTICE in a location viewable to users of the \nredistributed or derivative work. \n\nAny pre-existing intellectual property disclaimers, notices, or terms and \nconditions. If none exist, the W3C Software Short Notice should be included \n(hypertext is preferred, text is permitted) within the body of any redistributed\nor derivative code.\n\nNotice of any changes or modifications to the files, including the date changes \nwere made. (We recommend you provide URIs to the location from which the code is \nderived.)\n\nTHIS SOFTWARE AND DOCUMENTATION IS PROVIDED \"AS IS,\" AND COPYRIGHT HOLDERS MAKE NO \nREPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, \nWARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE \nOF THE SOFTWARE OR DOCUMENTATION WILL NOT INFRINGE ANY THIRD PARTY PATENTS, \nCOPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.\n\nCOPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR \nCONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE SOFTWARE OR DOCUMENTATION.\n\nThe name and trademarks of copyright holders may NOT be used in advertising or \npublicity pertaining to the software without specific, written prior permission. \nTitle to copyright in this software and any associated documentation will at all \ntimes remain with copyright holders.\n____________________________________\n\nThis formulation of W3C's notice and license became active on December 31 2002. \nThis version removes the copyright ownership notice such that this license can \nbe used with materials other than those owned by the W3C, reflects that ERCIM is \nnow a host of the W3C, includes references to this specific dated version of the \nlicense, and removes the ambiguous grant of \"use\". Otherwise, this version is the \nsame as the previous version and is written so as to preserve the Free Software \nFoundation's assessment of GPL compatibility and OSI's certification under the \nOpen Source Definition. Please see our Copyright FAQ for common questions about \nusing materials from our site, including specific terms and conditions for packages \nlike libwww, Amaya, and Jigsaw. Other questions about this notice can be directed \nto site-policy@w3.org.\n\nJoseph Reagle \n\nLast revised $Id: copyright-software-20021231.html,v 1.11 2004/07/06 16:02:49 slesch Exp $ \n\n=========================================================================== \nFor license see the new SAX site at \nhttp://www.saxproject.org/ [http://www.saxproject.org/] for more up-to-date\nreleases and other information. Please change your bookmarks.\n\n\nSAX2 is Free!\n\nI hereby abandon any property rights to SAX 2.0 (the Simple API for\nXML), and release all of the SAX 2.0 source code, compiled code, and\ndocumentation contained in this distribution into the Public Domain.\nSAX comes with NO WARRANTY or guarantee of fitness for any\npurpose.\n\nDavid Megginson, david@megginson.com\n2000-05-05\n=======================================================================\n\n8.4 IBM obtained Smack V3.3.0 under the following license from Apache Software Foundation:\n\nApache License\nVersion 2.0, January 2004\nhttp://www.apache.org/licenses/ [http://www.apache.org/licenses/]\n\nPREREQUISITES\nIBM Tivoli Business Service Manager 6.1.1\n\nINSTALLATION INSTRUCTIONS\n\n3.7 Installation\n------------\n\n\n3.7.1 Installing the Fix Pack\n-----------------------\n\n[Fix Pack] Refers to the directory where you extracted the Fix\nPack files from the zip/tar file.\n\nAttention: Install the Fix Pack with the same user that was\nused to install TBSM 6.1.1 GA\n\n\nNOTE: If you have deployed the Service Level Objectives (SLO) \nReporting Function, you must do the following before\ninstalling the Fix Pack:\n\n- Stop all Impact services that are running policies that\ncall the SLO functions to record data in the SLORPRT\ndatabase. If you have the service set to start at\nserver startup, then turn this option off before\ninstalling the fixpack, as the server is restarted\nduring the fixpack install.\n\nRunning the install without DE backup:\n\nIf you prefer to backup DE with your own procedures you can\nrun the install with the following parameter.\n\n-DNO_BACKUP=true\n\n(for Silent Install, uncomment the \"NO_BACKUP=true\" \nparm on the setupFP.rsp response file)\n\nIf you choose this method, you must backup DE before you install.\nAnd restore the original system using your backup/restore\nprocedures or utilities (if uninstalling the Fix Pack).\n\nFollow this procedure to install the Fix Pack:\n\n1. On the Tivoli Business Service Manager server host, change to the\n[Fix Pack]/TBSM directory where you extracted the files.\n2. Run the installation using one the following commands:\n* setup-windows.exe - Windows.\n* setup-.bin - other operating systems.\n\nInstallation command options:\n\nGUI mode No options, for example: \nWindows: setup-windows.exe\n\nor\n\nUNIX® : ./setup-.bin \n\nConsole mode\nUse the -i console option. \nFor example -\nWindows: setup-windows.exe -i console\n\nor \n\nUNIX® : ./setup-.bin -i console\n\nSilent Mode\n\na. Copy setupFP.rsp from the TBSM directory of the extracted\nFix Pack file ([Fix Pack]/TBSM) to a location it can be\nedited (/tmp).\nb. Update the file to match your environment.\nc. Confirm acceptance of license, by un-commenting this line\nand setting the parm to \"true\":\n#LICENSE_ACCEPTED=false\nd. Run:\n\nWindows: setup-windows.exe -f C:\\tmp\\setupFP.rsp\n\nor \n\nUNIX® :setup-.bin -f /tmp/setupFP.rsp\n\nNote: The response file needs to have a fully qualified\npath.\n\n3. During the install you will be asked to to verify\npath names to the TIP install.\n\n4. Restart both the Data and Dashboard processes/services\n\n5. After install is complete (and with the data server started), run\nthe script ApplyPoliciesFor611FP3, which can be found on the Data\nServer under $TBSM_HOME/bin. This script loads the new/updated\npolicies.\n\nNOTE: Do not run the ApplyPoliciesFor611FP3 on the secondary/\nbackup data server of a failover pair. This only needs to\nbe run on the primary data server.\n\nOn Windows:\n\nApplyPoliciesFor611FP3.bat \nFor example - ApplyPoliciesFor611FP3.bat tipadmin tipadmin\n\nOn Linux/Unix:\n\n./ApplyPoliciesFor611FP3 \nFor example - ./ApplyPoliciesFor611FP3 tipadmin tipadmin \n\nNOTE: Verify that the admin user id and password are\ncorrect otherwise, the script will fail at the last step.\n\nIf incorrect, rerun the script with a valid adminuser id\nand password.\n\n6. From the TBSM 6.1.1 Fix Pack 3 install media, copy these files\nonto the DB2 server (where the tbsmdb was initially installed,\nwhen TBSM was first setup).\n\nfrom: [Fix Pack]/TBSM/TBSMDBChecker\nto: [InstallDirectory]/tbsmdb/bin\n\nTBSM_Check_DB.bat\nTBSM_Check_DB.sh\ntbsmDatabaseChecker.xml\nTBSMDBChecker.props\n\nNOTE: The above action is only needed if you ever plan to use\nthe TBSM_Check_DB script, which will now suppress the\ndisplay of the requested user password.\n\n7. After installing this Fix Pack, end-users may need to clear their\nbrowser cache, close and re-open the browser; in order to avoid\nany issues on the client side.\n\n8. If the Impact \"Service Level Objectives (SLO) Reporting\"\nfunction was enabled, please refer to section 3.12 for additional\npost Fix Pack installation required actions.\n\n9. Please refer to section 4.0 \"Additional information for TBSM Fix Pack 3 APARS\"\nfor additional post install actions.\n\n\n3.7.2 Discovery Library Toolkit\n-------------------------\n\n1. Navigate to the DiscoveryLibrary directory.\n\n2. To install Fixpack 3, \n\nIf you are on a Windows operating system, run the following\ncommand from a prompt: \n\nsetup-dltoolkit-6.1.1-FP0003-windows_64.exe\n\nIf you are on a Unix operating system, run the following\ncommand from a prompt:\n\nsetup-dltoolkit-6.1.1-FP0003-_64.bin\n\nFor console mode, specify \"-i console\".\n\nNote: If the installer cannot find the TBSM 6.1.1 Discovery \nLibrary Toolkit, verify that the toolkit is installed and \nthat it was installed by the user that the fixpack is being \ninstalled with. If these are both okay, then set the environment\nvariable TBSM_TOOLKIT_BASE to the location of the toolkit and \nrestart the toolkit installer. For example: \nWindows:\nset TBSM_TOOLKIT_BASE=C:\\Program Files\\IBM\\tivoli\\tbsm\\XMLtoolkit\nUNIX:\nexport TBSM_TOOLKIT_BASE=/opt/IBM/tivoli/tbsm/XMLtoolkit\n\n3. The toolkit installer requires access to the database.\n\n\n4. Notes and Post-Install Considerations:\n\na) After installation is complete, you may remove\n[fixpack] to save space.\n\n5. Restart the toolkit.\n\n\n3.8 TBSM agent\n----------\n\nInstalling the TBSM agent (last updated with TBSM Fix Pack 1):\n\nThe following packages are available for download in the TBSMAgent\ndirectory on the support download site:\n\n* AIX: KR9_aix526CD-6.1.1-TIV-BSM-FP0001.tar.gz -AIX (64 bit) \n\n* Linux: KR9_lx8266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li x86_64R2.6(64 bit)\n\n* Solaris: KR9_sol286CD-6.1.1-TIV-BSM-FP0001.tar.gz -Solaris R8(64 bit)\n\n* Windows: KR9_wix64CD-6.1.1-TIV-BSM-FP0001.zip -(64 bit)\n\n* zLinux: KR9_ls3266CD-6.1.1-TIV-BSM-FP0001.tar.gz -Li S390R2.6(64 bit)\n\n\nTo install the updated TBSM agent (FP1), if not already installed:\n1. Download the appropriate agent code for your platform.\n2. Untar or unzip the file.\n3. Install the agent according to the directions in the TBSM\nInstallation Guide. This is a complete install package for the TBSM\nagent support and can be used for a fresh install of the agent.\n\nFor instructions on installing and configuring the TBSM agent, see:\n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsni_agent_ic_install_config.html]\n\n\n3.9 Uninstalling the Fix Pack\n-------------------------\n\nBefore uninstalling the FixPack all TBSM processes should be\nSTOPPED. The user must manually stop the TBSM processes, before \nthe uninstall of the FixPack (except for OMNIbus and DB2).\n\nAttention: Uninstall the Fix Pack with the same user that was used to\ninstall TBSM 6.1.1 GA.\n\nSilent mode and uninstall\n\n\nIf silent mode was used for the install, the uninstall will\ndefault to a silent uninstall and you must supply a response\nfile or the uninstall will fail.\n\nFor silent mode uninstalls, copy the setup_uninstall.rsp file\nfrom the Fix Pack image to the directory:\n\n/tbsm/_uninst/TBSM611_FP3\n\nand update the file with the correct information. Then launch\nthe installer specifying the file. For example:\n\nuninstall(.exe) -f /tmp/setup_uninstall.rsp\n\nNote: The response file needs to have a fully qualified path.\n\nOn the Tivoli Business Service Manager server system:\n\n1. Change to the directory: \n/tbsm/_uninst/TBSM611_FP3\n\n2. Run the uninstall command:\n\nUNIX: If you are on a Unix operating system, run the following\ncommand from a prompt.\n\n./uninstall\n\n\nWindows: If you are on a Windows operating system, run the following\ncommand from a prompt.\n\n.\\uninstall.exe\n\nFor console mode, specify \"-i console\"\n\n3. After the command has completed, run the following commands to clear\nthe server cache.\n\nLinux/AIX: /bin/clearClassCache.sh\n\nSolaris: java -Xshare:dump\n\nWindows: \\bin\\clearClassCache.bat\n\n\n\n4. Uninstall eWAS 7.0.0.35\n\nNOTE: On a \"Data server only\" environment, the TBSM 6.1.1 Fix\nPack 3 un-installer will not remove the upgraded eWAS\n7.0.0.35 Fix Pack it installed. If there are plans to, at\na future time, re-install TBSM 6.1.1 Fix Pack 3, it is\nnecessary to manually un-install eWAS 7.0.0.35. \n\nThese steps DO NOT apply to a \"Dashboard sever only\"\nenvironment or a \"Single server\" environment, where both the\nData and Dashboard are installed together.\n\nAgain, these steps are only needed on a \"Data server only\"\nenvironment. Failure to perform these actions, will prevent\nthe re-install of TBSM 6.1.1 Fix Pack 3!\n\na). Copy the uninstall-WASEmbeded.txt to a temporary location\nThe uninstall-WASEmbeded.txt file is located on:\n/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_WASFP/uninstall-WASEmbeded.txt\n\nFor example on Unix:\n/opt/IBM/tivoli/tbsm/_uninst/TBSM611_FP3/plan/install/MachinePlan_localhost/00002_IAGLOBAL_COI_STEP_WASFP/uninstall-WASEmbeded.txt\n\nFor example on Windows:\nC:\\IBM\\tivoli\\tbsm\\_uninst\\TBSM611_FP3\\plan\\install\\MachinePlan_localhost\\00002_IAGLOBAL_COI_STEP_WASFP\\uninstall-WASEmbeded.txt\n\n\nOr from the TBSM 6.1.1 FP3 install media:\n6.1.1-TIV-BSM-FP0003-\\TBSM\\COI\\PackageSteps\\WASFP\\uninstall-WASEmbeded.txt\n\n\nb). Edit the uninstall-WASEmbeded.txt (on the temporary location)\n\nc). locate this line: -W product.location=\"@IAGLOBAL_WAS_HOME@\"\n\nd). Replace above line with: -W product.location=\"/tipv2\"\n\nWhere is the fully qualified directory where tipv2 located:\n\nfor example (Unix): -W product.location=\"/opt/IBM/tivoli/tipv2\"\n\nfor example (Windows): -W product.location=\"C:\\IBM\\tivoli\\tipv2\"\n\ne). Save the uninstall-WASEmbeded.txt file (on the temporary location)\n\nf). Execute the following command:\nOn Unix:\n/tipv2/WebSphereUpdateInstallerV7/update.sh -options /uninstall-WASEmbeded.txt -silent\n\nfor example: /opt/IBM/tivoli_root/tipv2/WebSphereUpdateInstallerV7/update.sh -options /tmp/uninstall-WASEmbeded.txt -silent\n\nOn Windows:\n/tipv2/WebSphereUpdateInstallerV7/update.exe -options /uninstall-WASEmbeded.txt -silent\n\nfor exampe: C:\\IBM\\tivoli\\tipv2\\WebSphereUpdateInstallerV7\\update.exe -options C:\\Temp\\uninstall-WASEmbeded.txt -silent\n\n5. Restart the Data Server and Dashboard Server.\n\n\n\nDiscovery Library Toolkit\n===================================================\n\nThe Toolkit portion of this fixpack cannot be uninstalled.\nA backup copy of the original files can be retrieved from:\n\n[InstallDirectory]/tbsm/\nXMLtoolkit/log/install/maintenance/backup/611FP0003\n\n\n\n3.10 Recovering from a failed Fix Pack install\n-----------------------------------------\n\nIf the install fails, try to uninstall in which case, it goes back to\nthe previous version. If there is no uninstall file under \n_uninst/TBSM611_FP3, then nothing really got installed and you can delete\nthe TBSM611_FP3 file and reinstall.\n\n\n3.11 Restoring failed DE upgrade from backup\n---------------------------------------\n\nTo recover a failed Deployment Engine upgrade in TBSM 6.1.1, see the\nTBSM Installation Guide at: \n\nhttp://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html [http://www.ibm.com/support/knowledgecenter/SSSPFK_6.1.1.3/com.ibm.tivoli.itbsm.doc/installguide/bsmi_upgrade_t_restore42.html]\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.1.1-TIV-BSM-FP0003-linux 06 Jul 2015 English 1422005148 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-linux&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-aix 06 Jul 2015 English 1501631388 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-aix&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-solaris 06 Jul 2015 English 1472222108 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-solaris&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-windows 06 Jul 2015 English 1437426779 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-windows&source=SAR] [ ] 6.1.1-TIV-BSM-FP0003-zlinux 06 Jul 2015 English 1418646428 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Business+Service+Manager&fixids=6.1.1-TIV-BSM-FP0003-zlinux&source=SAR] [ ] \n [/support/docview.wss?uid=swg24039742&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039742&aid=2]Problems (APARS) fixed\nIV60619 IV61278 IV64797 IV65695 IV65825 IV65947 IV65949 IV65958 IV66535 IV66950 IV71255 IV72005 IV62456 IV62548 IV60168 IV56853 IV63608 IV65503 IV65786 IV59886 , IV61880 IV64950 IV60750 IV60961 IV61199 IV62273 IV62294 IV62246 IV64933 IV65545 , IV66210 IV65484 IV68113 IV60842 IV56450 IV65991 IV21679 IV30875 IV33717 IV36878 , IV38053 IV38471 IV38574 IV39167 IV39517 IV39796 IV42339 IV42657 IV42941 IV43098 , IV43165 IV43469 IV43804 IV43865 IV44246 IV44582 IV45166 IV45386 IV45868 IV46098 , IV46811 IV46876 IV48813 IV49791 IV50625 IV53791 IV54197 IV54587 IV55756 IV56050 , IV56270 IV57273 IV59723 IV61668 , IV27869 IV50058 IV58590 IV59770 IV60438 IV61538 IV61725 IV63535 IV63942 IV64075 IV64837 IV65055 IV65179 IV66164 IV67091 IV67829 IV68383 IV69164 IV70836 IV71157 IV71513 IV73098 IV73243 IV18554 IV23315 IV64152 IV61089 IV63137 IV62792 IV61956 IV61746 IV61399 IV60005 IV60253 IV58616 IV58511 IV53717 IV56745 IV56068 IV55989 IV50329 IV56541 IV47748 IV55464 IV60923 IV11728 IV21717 IV22560 IV33973 IV34503 IV35827 IV35885 IV35940 IV36405 IV36503 IV37040 IV37369 IV37717 IV37759 IV38045 IV38585 IV38961 IV39368 IV40158 IV41888 IV42715 IV43030 IV43751 IV45068 IV45511 IV45569 IV45838 IV46099 IV46493 IV46696 IV46729 IV46799 IV47058 IV47799 IV47904 IV47988 IV48113 IV48113 IV50464 IV50932 IV51062 IV51098 IV51100 IV53483 IV53810 IV53818 IV53822 IV53824 IV53825 IV53826 IV53827 IV53836 IV54939 IV55776 IV55778 IV55779 IV55780 IV55781", "question": "Which version of TBSM support ITM 6.3? What is the TBSM version that is certified with ITM 6.3? ", "answer": "IBM Tivoli Business Service Manager 6.1.1\nFix Pack Version 6.1.1-TIV-BSM-FP0003"} +{"id": "TRAIN_Q101", "document": "IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States TECHNOTE (FAQ)\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 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 ,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]", "question": "Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc \n\nInstalled an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc\n\nI get the following messages in the logs:-\n\n/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\"\n\nand from the Guardium Appliance - via fileserver in the /log/opt-ibm-guardium-log/snif/snif.log \"Unauthorized client connecting from ,rejecting\"", "answer": "Uncheck the Approval box and the S-TAPs should start connecting ."} +{"id": "TRAIN_Q103", "document": "IBM Important Information about the WebSphere MQ Configuration Agent, Withdrawn from IBM OMEGAMON for Messaging on z/OS V7.5 - United States PRODUCT DOCUMENTATION\n\nABSTRACT\n Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ. It is stabilized in the previous V7.3 release, but MQ Configuration will be supported as long as V7.3 is in support. The components in V7.5 are the IBM MQ Monitoring Agent and the IBM Integration Bus Monitoring Agent, both of which have enhancements in V7.5 that address monitoring requirements you may have. You can upgrade your OMEGAMON for Messaging monitoring components to V7.5 while using the previous release of MQ Configuration. \n\nWhether or not you want to continue using MQ Configuration when you install and configure OMEGAMON for Messaging V7.5, there may be steps you need to take, so please review this document prior to installing and configuring V7.5. \n\nCONTENT\nFirst, please determine whether you have previously installed and configured the MQ Configuration component. If you have not done so previously, there is no need for you to consider the rest of this document. For this determination, please examine the following: \n\n\n· SMP/E: Are the FMIDs for MQ Configuration installed? The FMIDs are HKMC730 and HKCF730, or HKMC710 and HKCF710 if you are using the V7.1 level. \n· PARMGEN: In your PARMGEN configuration for each runtime environment, does the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), have the line for “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” selected for configuration in the environment? \n\nIf the answers are “yes” to both of the above questions, then you do need to continue with the following general steps, which are documented in detail below: \n\n1) Determine whether there are any users of MQ Configuration in your environment. There are many cases in which the MQ Configuration component is installed and configured in PARMGEN, but no one is actually using it. It is important to determine this in order to decide which step to take next.\n\n2) If you do not have users of MQ Configuration, or you want to remove it anyway, there may be steps required when you are installing and configuring OMEGAMON for Messaging V7.5 especially if you previously configured a shared agent address space for MQ monitoring (KMQ) and MQ configuration (KMC) agents. \n\n3) If you do have users of MQ Configuration and want to continue supporting that usage, you need to follow recommendations when you are installing and configuring OMEGAMON for Messaging V7.5 upgraded products.\n\n\nHere are the details:\n\n1) Suggested ways to determine whether there are any users of MQ Configuration:\n\na. In the Tivoli Enterprise Portal (TEP), using an administrator user ID, click Edit->Administer Users to check whether any users or groups have access to the Configuration navigator view. For users and/or groups that have been configured for TEP, check the Navigator Views tab to see if any of them have “Configuration” in their Assigned Views. If no one is allowed access to the Configuration navigator, then they are not using MQ Configuration feature. \n\nb. Another item to check in Administer Users is whether any user or group has the Permissions tab showing that View or Modify permission has been authorized for WebSphere MQ Configuration Authorities “Configure” authority. Some user or group should have permission to use this feature if it is used by anyone. \n\nc. Check whether there are configured names that reflect queue managers in your environment. Click on the Configuration navigator in the view drop-down list in the Navigator pane, then click on Defined View on the left. In the middle Defined Tree pane on the workspace, expand the various “+” items, and with the help of someone who knows MQ queue managers in your environment, see if any of the expanded items reflect queue managers actually in your environment. There will be default and example items shipped with the product, but you are looking for names reflecting MQ at your site. If there are no names that reflect queue managers in your environment, then no one is using MQ Configuration.\n\nd. If it appears that there is usage of MQ Configuration, it would still be good to check with MQ users at your site to see if they actually require it. Perhaps they have experimented with it but do not actually use it regularly. If the OMEGAMON feature for MQ Configuration is not absolutely required in your environment, the recommendation would be to review all the ways that the IBM MQ product offers to configure and administer MQ, some of which are new in recent releases. Also, remember that the OMEGAMON MQ Monitoring agent offers the Take Action facility to issue any MQSC configuration command if the user is authorized.\n\n\n2) If there are no users of MQ Configuration, or you want to remove it anyway: \n\na. If you use a Serverpac that contains the upgraded OMEGAMON for Messaging V7.5 components to install, the MQ Configuration FMIDs (HKMC730 and HKCF730) are not installed because they are not included in the Serverpac. However, depending on your previous configuration, the missing MQ Configuration component could cause unexpected results in your LPAR runtime environment (RTE), so check and act on the following items prior to installation and configuration of OMEGAMON for Messaging V7.5:\n\n1. If your Hub TEMS is configured on the z/OS platform and there are RKCF* DDNAME statements in your existing Hub TEMS started task JCL, update the TEMS started task JCL to remove those RKCF* DDNAME statements.\n\n2. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. For the MQ Monitoring agent to be the owner, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting, as depicted in the following example before and after settings:\n\nBefore (MQ Configuration owns the Agent address space called OMEGMQ):\nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===> \nKMC_AGT_STC OMEGMQ\nKMC_AGT_STC_OWNER “”\nKMQ_AGT_STC “”\nKMQ_AGT_STC_OWNER OMEGMQ\n\nAfter (MQ Monitoring owns the Agent address space called OMEGMQ): \nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===>\nKMQ_AGT_STC OMEGMQ\nKMQ_AGT_STC_OWNER “” \n\nTip: Please review the SMPE06 upgrade scenario [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2] in the OMEGAMON Shared Knowledge Center as part of deploying these changes. You can use the refreshed OMEGMQ OMEGAMON for Messaging – KMQ Agent-only address space in the RTE’s W/RKANSAMU dataset for refreshing the original shared address space in your system procedure library. The only delta would be the RKMCAPLA DDNAME, which can be staged for removal.\n\nb. If you install OMEGAMON for Messaging V7.5 as a CBPDO into an existing SMP/E CSI, the MQ Configuration FMIDs will remain installed, but since you are not using MQ Configuration, it is recommended you follow these steps:\n\n1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, make sure that the owner of that address space is the MQ Monitoring agent. See item a.2 above for more details.\n\n2. In the “Include Products in this PARMGEN RTE panel (KCIP@PGI)” (under step “1 KCIJPCFG Set-up/Refresh PARMGEN work environment” navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), deselect the line with “KMC OMEGAMON for Messaging – WebSphere MQ Configuration” so that it will be removed from the runtime environment (RTE) during reconfiguration/upgrade of the RTE. Follow one of the SMPEnn upgrade scenarios [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2] documented in the OMEGAMON Shared Knowledge Center. \n\nTip: Prior to upgrading the RTE, you also have the option to SMP/E delete the HKMC730 and HKCF730 FMIDs from the existing CSI. When you start the PARMGEN configuration phase of the upgrade, the inexistence of these deleted FMIDs is PARMGEN’s trigger to delete the product from the RTE upon reconfiguration following any of the SMPEnn upgrade scenarios (SMPE04 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe04_parmgenref.htm?pos=2], SMPE05 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe05_parmgenref.htm?pos=2] or SMPE06 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/parmgenref/smpe06_parmgenref.htm?pos=2]). \n\n\n3) If there are users of MQ Configuration, and you want to continue supporting that usage: \n\na. It is highly recommended that you install OMEGAMON for Messaging V7.5 as a CBPDO into the existing SMP/E CSI so that MQ Configuration remains available. If you do this, there are no other steps required, however, the following step is also highly recommended: \n\n1. If MQ Configuration (KMC) and MQ Monitoring (KMQ) agents are running in a shared agent address space, separate them into their own address spaces, since they will be running at different product levels. For this, the related PARMGEN LPAR RTE profile parameters for OMEGAMON for Messaging components may need adjusting to be like the following example in which MQ Configuration is running in an address space called OMEGMC and MQ Monitoring is running in an address space called OMEGMQ:\n\nISREDDE2 %RTE_PLIB_HILEV%.%RTE_NAME%.WCONFIG(%RTE_NAME%) \nCommand ===> \nKMC_AGT_STC OMEGMC\nKMC_AGT_STC_OWNER “”\nKMQ_AGT_STC OMEGMQ\nKMQ_AGT_STC_OWNER “”\n\nb. If you were to install OMEGAMON for Messaging V7.5 in a Serverpac, you would need to retain your old SMP/E CSI and maintain a separate PARMGEN runtime environment in order to use MQ Configuration separately. This may be acceptable to you if you already separate MQ Configuration from the rest of your monitoring infrastructure, with its own Hub TEMS, etc. In this case, for the configuration that will contain OMEGAMON for Messaging V7.5, please see item 2 above, steps a.1 and a.2 in case they would apply to that particular configuration.\n\nc. OMEGAMON for Messaging V7.5 application support does not include application support for the MQ Configuration component. If you need to re-install application support for MQ Configuration for any reason, you should use the latest V7.3 level of application support. For z/OS customers, that is available with DVD LCD7-3513-08 at the following link: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]\n\n\nFor more information about OMEGAMON for Messaging V7.5, please see this link to the product documentation:\nhttps://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html [https://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html]\n\nFor more information about OMEGAMON installation and configuration with PARMGEN, please see this link to the shared documentation:\nhttps://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2 [https://www.ibm.com/support/knowledgecenter/SSAUBV/com.ibm.omegamon_share.doc_6.3.0.2/shared_welcome/welcome.htm?pos=2] \n\n\nFor more information about recommended ways to configure IBM MQ, please see the following links:\nAdministering IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.adm.doc/q019950_.htm]\nConfiguring queue managers on z/OS [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019070_.htm]\nUsing IBM z/OSMF to automate IBM MQ [https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q019925_.htm]\nSupport continuous configuration deployments for IBM MQ with UrbanCode [https://www.ibm.com/developerworks/library/d-continuous-configuration-deployments-urbancode-mq-trs/index.html] \n\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2017/10/26", "question": "PARMGEN ABEND S013 in JOB KCIJPALO \n\nAfter installing IBM OMEGAMON for Messaging on z/OS 07.05.00, I receive the following ABEND after submitting PARMGEN Job KCIJPALO:\n\n JOB02175 IEC141I 013-18,IGG0191B,U600861X,KMCJPALR,RKPDIN,600D,ISMS01, 083\n 083 HSYS.S002.OMGNEW.TKANPAR(KMCPDICT)\n JOB02175 IEA995I SYMPTOM DUMP OUTPUT 085\n 085 SYSTEM COMPLETION CODE=013 REASON CODE=00000018\n 085 TIME=07.41.33 SEQ=00630 CPU=0000 ASID=004C\n 085 PSW AT TIME OF ERROR 075C1000 80E9E456 ILC 2 INTC 0D\n 085 NO ACTIVE MODULE FOUND\n 085 NAME=UNKNOWN\n 085 DATA AT PSW 00E9E450 - 4100302C 0A0D010D A7E5014B\n 085 AR/GR 0: 009FF028/00E9E760 1: 00000000/A4013000\n 085 2: 00000000/00081CB8 3: 00000000/00E9E734\n 085 4: 00000000/009B1410 5: 00000000/009B17A4\n 085 6: 00000000/009B174C 7: 00000000/009B17A4\n 085 8: 00000000/009B176C 9: 00000000/00000080\n 085 A: 00000000/00F20E10 B: 00000000/009B10FC\n 085 C: 00000000/00000008 D: 00000000/00000000\n 085 E: 00000000/80E9DCB4 F: 00000000/00000018\n 085 END OF SYMPTOM DUMP\n\nWhat is the cause of this?", "answer": "Starting with V7.5, IBM OMEGAMON for Messaging on z/OS no longer delivers the component called WebSphere MQ Configuration Agent, referred to as MQ Configuration in the rest of this document, because there are other recommended ways to configure IBM MQ."} +{"id": "TRAIN_Q104", "document": "IBM SCA destinations for IBM Business Process Manager (BPM), WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB) are not preserved when uninstalling and reinstalling a service module - United States SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a Service Component Architecture (SCA) module is uninstalled, by default, its associated destinations are removed, even if there are still messages in the destination queue. In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5 \nPRODUCT ALIAS/SYNONYM\n BPM\nWPS\nWESB", "question": "Updating SCA applications & internal SCA module queues \n\nWhen updating an existing SCA module using the ISC, I noticed that internal SCA queues (sca//...) on the SCA.SYSTEM bus) are deleted and recreated.\n\nDoes this mean that any messages that may still reside on these internal queues would be deleted on a module update? If so, when updating SCA modules in a production environment, should these internal queues be monitored to be empty before updating a SCA module (to prevent loosing messages)?", "answer": "To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations."} +{"id": "TRAIN_Q106", "document": "IBM Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) - United States SECURITY BULLETIN\n\nSUMMARY\n The Telemetry (MQXR) service can be configured to use SSL/TLS connections - the passphrase used to access the keystore is written to the file system in clear text in a properties file that is world readable. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]\nDESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.\nCVSS Base Score: 2.1\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] 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\nIBM WebSphere MQ 8.0 \n\n * 8.0.0.3 and earlier maintenance levels\n\n\nIBM WebSphere MQ 7.5 * 7.5.0.5 and earlier maintenance levels\n\n\nIBM WebSphere MQ 7.1 * 7.1.0.6 and earlier maintenance levels\n\nREMEDIATION/FIXES\nIBM WebSphere MQ 8.0 \n\nInstall fixpack 8.0.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg21969244] \nIBM WebSphere MQ 7.5 * Apply Interim fix IT09866 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+MQ&release=7.5.0.5&platform=All&function=aparId&apars=IT09866]\n\n\nIBM WebSphere MQ 7.1 * Install fixpack 7.1.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg21965293]\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] 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 01 February 2016: Original Copy 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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977183]", "question": "Help with Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) I need to understand details regarding Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012). Where can I find this information? ", "answer": "CVEID: CVE-2015-2012 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-2012]\nDESCRIPTION: IBM WebSphere MQ stores the MQXR keystore password in clear text in a world readable file.\nCVSS Base Score: 2.1\nCVSS Temporal Score: See http://xforce.iss.net/xforce/xfdb/103923 [http://xforce.iss.net/xforce/xfdb/103923] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L/AC:L/Au:N/C:P/I:N/A:N)"} +{"id": "TRAIN_Q107", "document": "IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code\n\n\nSetting the HTTP Session time-out from the Administrative Console \n1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management. \n\nIn the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box. \n\n\n2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level. \n\n\n3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level. \n\nAfter modifying these settings, save the master configuration. \n\nSetting HTTP Session time-out when application is packaged \n\nThe application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application. \n\nThis setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \n           \n *          60\n * \n *       \n\n \n\nWhere the \"session-timeout\" is an integer value for the desired session time-out in minutes. \nSetting HTTP Session time-out from the application code \n\nFinally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console. \n\nHTTP Session time-out Override Precedence Summary \n\nThe list below shows the precedence from which the final HTTP Session time-out is derived. \n\n1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&aid=1] Overrides all other settings RELATED INFORMATION\n A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "How to increase the HTTP Session time-out value for Workplace application on WebSphere Application Server? We would like to increase the HTTP Session time-out value for our Workplace application. Where are all the locations that this value is set and what are their precedence? ", "answer": "The HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code"} +{"id": "TRAIN_Q108", "document": "IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT). \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2\n\nREMEDIATION/FIXES\nSupportPac MS81: IBM WebSphere MQ Internet Pass-Thru\nUsers of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].\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 v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \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] ACKNOWLEDGEMENT\nReported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 11th June 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.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347]", "question": "Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) I need to understand details regarding Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000). Where can I find this information? ", "answer": "CVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)"} +{"id": "TRAIN_Q109", "document": "IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States IIB WMB FLASH (ALERT)\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\nCVE-2017-14746 CVE-2017-15085 CVE-2017-15086 CVE-2017-15087 CVE-2017-15275\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", "question": "Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux \n\nI 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.\nThis is related to CVE-ID:\nCVE-2017-14746\nCVE-2017-15085\nCVE-2017-15086\nCVE-2017-15087\nCVE-2017-15275\n\nWhere can I find this information?", "answer": "IBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable."} +{"id": "TRAIN_Q110", "document": "IBM Installing the Installation Manager on an NFS mounted disk - United States NFS; remote drive; mount drive ; 1308281 TECHNOTE (FAQ)\n\nQUESTION\n Can IBM® Installation Manager be installed on a UNIX® or Linux® NFS mounted disk? \n\nANSWER\nDo not install the IBM Installation Manager on an NFS mounted disk. \n\nOn AIX® for example, some of the JRE folders are not being deleted when the IBM Installation Manager uninstalls but is deleted after waiting for 10 minutes. This causes the JRE folder to not be uninstalled during an uninstall operation. Other UNIX and Linux operating systems have similar issues. \n\nOnly install the Installation Manager on a local disk.", "question": "Why does my install of the latest Installation Manager on a Linux Ingram Server not function? \n\nI've installed the latest Installation Manager on an Ingram Server that I mount to different Linux machines where I have installed WebSphere Application Server. I received the following error when trying to use the Installation Manager:\n\n 00:02.25 ERROR [main] org.eclipse.equinox.log.internal.\n ExtendedLogReaderServiceFactory safeLogged\n Application error\n java.lang.NoClassDefFoundError: org.eclipse.jface.dialogs.\n ProgressMonitorDialog\n at java.lang.ClassLoader.defineClassImpl(Native Method)\n at java.lang.ClassLoader.defineClass(ClassLoader.java:324)\n at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.\n defineClass(DefaultClassLoader.java:188)\n at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.\n defineClassHoldingLock(ClasspathManager.java:632)\n\nI have unmounted and remounted the drive but does not appear to resolve the issue.", "answer": "Only install the Installation Manager on a local disk."} +{"id": "TRAIN_Q111", "document": "IBM How to find details of Corrupted Object from the entries in db2diag.log? - United States TECHNOTE (FAQ)\n\nQUESTION\n How to find details of Corrupted Object from the entries in db2diag.log? \n\nANSWER\nWhen we have corruption in the database we may received following kind of entries in db2diag.log \nThese also notify object where we t where we have detected corruption in the Database.\n\nSample db2diag.log entry for Corruption.\n\n2016-05-04-03.13.05.261082-360 I3442A358 LEVEL: Error \nPID : 393470 TID : 1 PROC : db2pfchr 0 \nINSTANCE: db2inst1 NODE : 000 \nFUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers,probe:13 \nRETCODE : ZRC=0x86020001=-2046689279=SQLB_BADP \"page is bad\" \nDIA8400C A bad page was encountered. \n\n2016-05-04-03.13.05.264301-360 I3801A437 LEVEL: Error \nPID : 393470 TID : 1 PROC : db2pfchr 0 \nINSTANCE: db2inst1 NODE : 000 \nFUNCTION: DB2 UDB, buffer pool services, sqlbReadAndReleaseBuffers, \nprobe:13 \nDATA #1 : String, 158 bytes \nObj={pool:3;obj:21;type:0} State=x27 Parent={3;21}, EM=1120, PP0=1152 \nPage=51235 Cont=17 Offset=2848 BlkSize=15 \nsqlbReadAndReleaseBuffers error: num-pages=16\n\n\nBased on this information dumped in db2diag.log entry we can Identify {pool:3;obj:21;type:0} is the Object is corrupted.\n\ne.g. Obj={pool:3;obj:21;type:0}\n\nPool = Tablespace ID\nObj = Object ID\nType = Type of the Object\n\nIf Type is 0 its Table Object ,If its 1 then its Index. \n\nWe can find the Name of the Object using following query, to further backup the Definition for future reference.\n\ndb2 \"select char(tabname,20), char(tabschema,20) from syscat.tables where tableid= and tbspaceid=\"\n\nObj={pool:3;obj:21;type:0}\ndb2 \"select char(tabname,20), char(tabschema,20) from syscat.tables where tableid=21 and tbspaceid=3\"\n\nRELATED INFORMATION\n SYSCAT.TABLES catalog view [http://www.ibm.com/support/knowledgecenter/SSEPGG_10.1.0/com.ibm.db2.luw.sql.ref.doc/doc/r0001063.html?lang=en]", "question": "How to find details of Corrupted Object from the entries in db2diag.log? We have corruption in DB2 Database and got entries for corrupted Object in db2diag.log ,Need to find details of the Object using information dumped in db2diag.log ", "answer": "When we have corruption in the database we may received following kind of entries in db2diag.log \nThese also notify object where we t where we have detected corruption in the Database."} +{"id": "TRAIN_Q112", "document": "IBM JMSExceptions CWSIT0006E and CWSIA0241E on bus connect - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your application throws JMS exceptions CWSIT0006E and CWSIA0241E when trying to connect to a WebSphere Application Server (WAS) Service Integration Bus (SIBus). \n\nSYMPTOM\nApplication throws the following JMS exceptions in the stack trace while trying to connect to the SIBus: \n\nJMSException caught\njavax.jms.JMSException: CWSIA0241E: An exception was received during the call to the method\nJmsManagedConnectionFactoryImpl.createConnection:\ncom.ibm.websphere.sib.exception.SIResourceException: CWSIT0006E: It is not possible to contact\na messaging engine in bus YOURBUS..\nat\ncom.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:225)\nat\ncom.ibm.ws.sib.api.jms.impl.JmsManagedConnectionFactoryImpl.createConnection(JmsManagedConnectionFactoryImpl.java:148)\n\n\nCAUSE\nThis can be caused by a stopped messaging engine, a wrong or misspelled bus name (case-sensitive) in the connection factory settings or, the HA manager is not able to find the running messaging engine.\n\n\nRESOLVING THE PROBLEM\nThe error messages CWSIA0241E and CWSIT0006E indicate that when the connection was attempted, there were no running messaging engines available on the specified bus. To see why the messaging engines were not available, check the SystemOut.log for applicable messages. Examine the SystemOut.log file starting at the time period when the application experienced the problem and search backward. \n\n\nCheck for the CWSID0016I which indicates status of the Messaging Engine activity. You may see messages like this:\n\nSibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopping.\nSibMessage I [:] CWSID0016I: Messaging engine [mename]is in state Stopped.\n\nThe solution for this problem is to start the messaging engine.\n\nIf the messaging engine is running and you still see these errors at the application side, other possible reasons for this problem are:\n\n1) Check provider end points. The value for the provider endpoints should be in the format of host_name:port_number:BootstrapBasicMessaging.\n\nIn the JMS connection factory, you can define a list of provider endpoints that govern which servers the application will attempt to connect to. If you have defined these endpoints, ensure that the messaging engines for these servers have all started and that the port and transport chains defined in the endpoint list are correct. Also, ensure that the values for the Connection proximity (bus, cluster, host or server) and the Target groups and Target significance settings are appropriate. For example, if the Target significance value is Required and no suitable messaging engine could be located, then this would cause a connection failure. Please refer to the following links for how to set provider endpoints:\n\nDefault messaging provider queue connection factory [Settings] : [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSQueueConnectionFactory_DetailForm.html]\n\nDefault messaging provider topic connection factory [Settings]: [https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/SIBJMSTopicConnectionFactory_DetailForm.html]\n\nRestart the server after making the change.\n\n2) If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.\n\nTune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties. \n\n1)/properties : The properties declared under this location would be applicable to all the profiles in that installation.\n\n2)/properties : The properties declared here are applicable for all the servers on this profile\n\nIf a property is defined at both /properties and /properties, then the property defined at /properties would take precedence.\n\nAfter resetting the property you must restart the server.\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ Not Applicable Business Integration WebSphere Process Server Business Integration WebSphere Service Registry and Repository Business Integration IBM Business Process Manager Standard Business Integration WebSphere Enterprise Service Bus Business Integration WebSphere Partner Gateway Advanced Edition Configuration Business Integration WebSphere MQ Configuration \nPRODUCT ALIAS/SYNONYM\n WebSphere Application Server WAS SIB SIBUS SI BUS", "question": "WAS 8.5.x - Writing a JMS message to a remote queue takes a long time. How to write the message faster? \n\nWe are writing a jms message from a websphere cell (cellA) to a queue hosted by another websphere cell (cellB). Sometimes we noticed that writing a message is very slow. Usually when a local queue will be used the time to write this messages is about 8 ms, but if the queue is located on a other cell is took significant longer (about 3000ms+ ).\n\nOur findings: After enabling following trace \"=info: com.ibm.ws.sib.trm.=finest\" the problem is related to:\n- com.ibm.ws.cluster.selection.NoAvailableTargetExceptionImpl\n- WaitForWLMDat 3 (com.ibm.ws.sib.trm.wlm.client.WaitForWLMData) [:] Sleeping for 2999 ms \"\n\nBecause of the sleep time the writing to the queue is slowed down. How to prevent the sleeping time of 3 seconds, when writing a message to a remote queue?", "answer": "If your environment is heavily loaded, the HA manager might not be able to locate the running messaging engine within three seconds. In this case, check if there are any hung threads in the SystemOut.log, and resolve them if possible. Next, consider increasing the value of sib.trm.linger from three to give the HA manager more time to locate a messaging engine.\n\nTune the sib.trm.linger property value in the sib.properties file to set the messaging engine lookup delay so that the Work Load Manager (WLM) waits for a longer period of time before returning an error. Please refer to information below on how to set this property in the sib.properties. \n\n1)/properties : The properties declared under this location would be applicable to all the profiles in that installation.\n\n2)/properties : The properties declared here are applicable for all the servers on this profile\n\nIf a property is defined at both /properties and /properties, then the property defined at /properties would take precedence.\n\nAfter resetting the property you must restart the server."} +{"id": "TRAIN_Q113", "document": "IBM Configuring logging for Atlas Extensions in Atlas 6.0.3.3 - United States TECHNOTE (FAQ)\n\nQUESTION\n How do I configure logging for Atlas Extensions in Atlas 6.0.3.3? \n\nCAUSE\nAtlas Extensions log files are not being generated\n\nANSWER\nIn Atlas 6.0.3.3, the Atlas Extensions logging configuration has moved to log4j.properties file. \n\n 1. Navigate to /Atlas/Properties folder \n 2. Edit log4.properties file \n 3. Update the path Information for the following three properties 1. log4j.appender.MATTER_APPENDER.File=matter_adapter.log \n 2. log4j.appender.PERSON_APPENDER.File=person_adapter.log \n 3. log4j.appender.ORG_UNIT_APPENDER.File=org_unit_adapter.log\n \n \n 4. Save the file \n 5. Restart Atlas application server", "question": "How do I configure logging for Atlas Extensions in Atlas 6.0.3.3? How do I configure logging for Atlas Extensions in Atlas 6.0.3.3? ", "answer": "In Atlas 6.0.3.3, the Atlas Extensions logging configuration has moved to log4j.properties file. \n\n 1. Navigate to /Atlas/Properties folder \n 2. Edit log4.properties file \n 3. Update the path Information for the following three properties 1. log4j.appender.MATTER_APPENDER.File=matter_adapter.log \n 2. log4j.appender.PERSON_APPENDER.File=person_adapter.log \n 3. log4j.appender.ORG_UNIT_APPENDER.File=org_unit_adapter.log\n \n \n 4. Save the file \n 5. Restart Atlas application server"} +{"id": "TRAIN_Q114", "document": "IBM Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms ( CVE-2016-0394 ) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object on unix platforms, which exposes it to an unintended actor. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V9 IT14845 The APAR is available in Fix Pack 9.0.0.6 https://www-304.ibm.com/support/docview.wss?uid=swg24042598 [https://www-304.ibm.com/support/docview.wss?uid=swg24042598]\n\nWebSphere Message Broker V8 IT14845 The APAR is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] \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\nTo mitigate the problem with a current V8 or V9 fix pack installation on Unix platforms, you can run the following commands: \n\nfind /isadc -type d -exec chmod 755 {} \\;\nfind /isadc -type f -exec chmod 644 {} \\;\nfind /isadc -type f -name *.sh -print -exec chmod 755\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 28-Nov-2016 - Original version Published\n04-Apr-2017 - Removed v10 (distributed) from affected list, text change to explicitly mention 'on unix platforms' \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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21995532]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin: IIB & WMB upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) I need to understand details regarding Security Bulletin: IBM Integration Bus and WebSphere Message Broker, upon installation, set incorrect permissions for an object ( CVE-2016-0394 ) Where can I find this information? ", "answer": "CVEID: CVE-2016-0394 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0394]\nDESCRIPTION: IBM Integration Bus and WebSphere Message broker set incorrect permissions for an object, which could allow a local attacker to manipulate certain files. \nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/112643 [https://exchange.xforce.ibmcloud.com/vulnerabilities/112643] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)"} +{"id": "TRAIN_Q116", "document": "IBM Portal upgrades fail during ejbdeploy with 'Error is Platform not running' message - United States 7001eGA TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPortal upgrades fails during ejbdeploy with 'Error is Platform not running' message. This could happen for any v6.1.0.x , v7.0.0.x, or v8.0.0.x upgrade\n\nSYMPTOM\nIn the ConfigTrace.log, the following exception can be seen:\n==========================\n[wsadmin] ADMA5016I: Installation of wps started.\n[wsadmin] ADMA5058I: Application and module versions are validated with versions of deployment targets.\n[wsadmin] ADMA5018I: The EJBDeploy program is running on file /var/tmp/app5791171104868981175.ear.\n[wsadmin] Starting workbench.\n[wsadmin] EJB Deploy configuration directory: /opt/IBM/WebSphere/AppServer/profiles/dmgrProfile/ejbdeploy/configuration/\n[wsadmin] framework search path: /opt/IBM/WebSphere/AppServer/deploytool/itp/plugins\n[wsadmin] build: RAD753-I20090617_1116\n[wsadmin] An unexpected exception was thrown. Halting execution.\n[wsadmin] Shutting down workbench.\n[wsadmin] Error executing deployment: java.lang.IllegalStateException. Error is Platform not running.\n[wsadmin] java.lang.IllegalStateException: Platform not running\n[wsadmin] at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:374)\n[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)\n[wsadmin] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)\n[wsadmin] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)\n[wsadmin] at java.lang.reflect.Method.invoke(Method.java:597)\n[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BootLoaderLoader.run(BootLoaderLoader.java:487)\n[wsadmin] at com.ibm.etools.ejbdeploy.batch.impl.BatchDeploy.execute(BatchDeploy.java:106)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.execute(EJBDeploy.java:106)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.deploy(EJBDeploy.java:349)\n[wsadmin] at com.ibm.etools.ejbdeploy.EJBDeploy.main(EJBDeploy.java:311)\n[wsadmin] EJBDeploy level: @build@\n[wsadmin] ADMA5008E: The EJBDeploy program failed on file /var/tmp/app5791171104868981175.ear. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy\n[wsadmin] ADMA0063E: An error occurred during Enterprise JavaBeans (EJB) deployment. Exception: com.ibm.etools.ejbdeploy.EJBDeploymentException: Error executing EJBDeploy\n[wsadmin] ADMA5011I: The cleanup of the temp directory for application wps is complete.\n[wsadmin] ADMA5069E: The installation of application wps failed. This application was in the middle of a full update and therefore is uninstalled from the configuration session. Discard your current configuration session immediately to recover the application. Do not save changes to the WebSphere Application Server configuration repository. The application is not uninstalled from this repository. Until the current configuration session is discarded you do not see this application in the current session.\n[wsadmin] WASX7017E: Exception received while running file \"/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/work/was/curJaclScript.jacl\"; exception information: com.ibm.ws.scripting.ScriptingException: WASX7418E: Application update for wps failed: see previous messages for details.\n\n[wsadmin] WASX7341W: No \"save\" was performed before the interactive scripting session exited; configuration changes will not be saved.\n/opt/IBM/WebSphere/AppServer/profiles/wp_profile/ConfigEngine/config/includes/apply_PTF.xml:59: Java returned: 105\n==========================\n\nCAUSE\nThis exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed. \n\n\n\nRESOLVING THE PROBLEM\nTo resolve the problem, complete the following steps: \n\n\n1. Delete/Remove the contents of the following directory EXCEPT for the 'config.ini' file, if it exists (the paths are different depending on your backend WAS version):\n\nWebSphere Application Server v6.1.x: \n/deploytools/configuration\n\nWebSphere Application Server v7.0.x: \n/ejbdeploy/configuration\n/deploytool/itp/configuration\n\n\nWebSphere Application Server v8.0.x:\n/ejbdeploy/configuration\n/deploytool/itp/configuration\n\n\nCluster Environments: Do this for both the DMGR profile and the node profile.\n\nNote: The deploytools and ejbdeploy directories may not exist on all nodes. They are created when ejbdeploy is executed successfully for the first time. If it has never been executed successfully in your environment, then the directories will not be there.\n\n2. Re-attempt the WebSphere Portal upgrade.\n\n\n\n\n * \n *", "question": "Why does my upgrade to Portal 8001 CF14 fail with the following errors, ADMA5008E, ADMA0063E, ADMA5069E, WASX7017E? Why does my upgrade to Portal 8001 CF14 fail with the following errors, ADMA5008E, ADMA0063E, ADMA5069E, WASX7017E?", "answer": "This exception can happen during ejbdeploy after the WebSphere Application Server has been upgraded, and old OSGI cache remains for the ejbdeploy tool. The OSGI class of the ejbdeploy tool contains class information within the deploytool folder and can become stale if the content inside deploytool has changed."} +{"id": "TRAIN_Q117", "document": "IBM The affect of the auto-update feature for Oracle JDK 7 on IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation - United States NEWS\n\nABSTRACT\n The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8. \n\nCONTENT\nOn Windows operating systems, because the upgrade to Oracle JDK 8 is enabled by default, you might not be aware that the upgrade has occurred. This Oracle JDK 8 issue applies to the Mac OS as well.\n\n\n\nSYMPTOM\nYou might see one of the following messages in the log file on Windows and Mac OS machines that originate from the WebSphere Application Server Liberty Profile: \n\n * TRAS0033E: Runtime injection of detailed method trace failed for class with exception \n * CWWKC0044W: An exception occurred while scanning class and annotation data. \n\n\nRESOLUTION\nAs stated on the Java SE at a Glance [http://www.oracle.com/technetwork/java/javase/overview/index.html] page, Oracle is automatically migrating users with the auto-update feature enabled from Oracle JDK 7 to Oracle JDK 8. However, a number of IBM and third-party dependencies for IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation do not support Oracle JDK 8.\n\n\n\n\n * Windows operating systems\n If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8.\n \n \n 2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site.\n \n \n 3. Reinstall Oracle JDK 7.\n \n \n \n To disable the JDK auto-update feature on Windows operating systems, see the Change Automatic Update Settings [http://java.com/en/download/help/java_update.xml#adv] section of the Oracle Java Auto Update documentation.\n \n \n * Mac OS\n If you have already migrated to Oracle JDK 8, you need to revert to Oracle JDK 7 using the following steps: 1. Uninstall Oracle JDK 8. For more information, see the How do I uninstall Java 7 and later versions on my Mac? [https://www.java.com/en/download/help/mac_uninstall_java.xml] information on the Oracle web site.\n \n \n 2. Download the latest version of Oracle JDK 7 from the Java SE Downloads [http://www.oracle.com/technetwork/java/javase/downloads/index.html] tab of the Oracle web site. For more information, see JDK 7 Installation for Mac OS X [http://docs.oracle.com/javase/7/docs/webnotes/install/mac/mac-jdk.html].\n \n \n 3. Reinstall Oracle JDK 7. \n \n \n \n \n On the Mac OS operating system, you are explicitly asked if you want to update your Java version. Do not update the Java version to Java 8. To verify your Java version, see How do I update Java for my Mac? [https://www.java.com/en/download/help/mac_java_update.xml]\n\n \n\nCross reference information Segment Product Component Platform Version Edition Mobile- Speech and Enterprise Access IBM Worklight Security Mac OS X, Windows 6.2, 6.1, 6.0, 5.0.6, 5.0.5 Consumer, Enterprise Mobile- Speech and Enterprise Access IBM Mobile Foundation Security Mac OS X, Windows 6.0, 5.0.6, 5.0.5 Consumer, Enterprise", "question": "Should I upgrade to Oracle JDK 8 if I am using IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, or IBM MobileFirst Platform Foundation products? These is an upgrade available to replace Oracle JDK 7 with Oracle JDK 8. Does IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and the IBM MobileFirst Platform Foundation products support the use of Oracle JDK 8? ", "answer": "The IBM Mobile Foundation, IBM Worklight, IBM Worklight Foundation, and IBM MobileFirst Platform Foundation products support Oracle JDK 7, but do not support Oracle JDK 8."} +{"id": "TRAIN_Q118", "document": "IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Readme - stand-alone - United States WPWCMCF WPWCMCF02 7002CCF PRODUCT README\n\nABSTRACT\n IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix stand-alone installation instructions for all editions, including WebSphere Portal Express. \n\nCONTENT\n7.0.0.2: Readme for IBM WebSphere Portal 7.0.0.2 Combined Cumulative fix - stand-alone \n\n\nTable of Contents \n\n * About Combined Cumulative Fix #history \n * Space requirements \n * Cluster installation instructions [http://www.ibm.com/support/docview.wss?uid=swg27023911] \n * Steps for installing Combined Cumulative Fix \n * Steps for uninstalling Combined Cumulative Fix \n * #inst_clus#uninst_clusKnown issues \n * Change History \n * Additional information \n * Trademarks and service marks \n\n\n\n\n\n\n\n\nAbout Combined Cumulative Fix \n\nThese are the instructions on how to install a WebSphere Portal Combined Cumulative Fix. The Combined Cumulative Fix is a package of WebSphere Portal fixes and Web Content Manager Cumulative fixes. \n\nWhat's New \n\nAs of WebSphere Portal V7.0.0.2 Combined Cumulative Fix 26 (CF26), support has been added for syndicating to subscribers running WebSphere Portal V8.0.0.1 Combined Cumulative Fix 09 (CF09) or later. \n\nBack to top \n\n\n\n\n\n\nSpace requirements \n\nEnsure that enough disk space is available in the following directories: \n\nz/OS: 625 cylinders in the directory where you download the cumulative fix, 625 cylinders in the , 625 cylinders in and 1250 cylinders in your system temp directory. \n\nAll other platforms: 2 GB in the directory where you download the cumulative fix, 1 GB in , 1 GB in temporary disk space and 1 GB in your system temp directory, such as /tmp on Unix or Linux platforms or C:\\temp on the Microsoft Windows platform. \n\nBack to top \n\n\n\n\n\n\nSteps for installing Combined Cumulative Fix \n\nBEFORE YOU BEGIN:\nFamiliarize yourself with the Portal Upgrade Best Practices available from IBM Remote Technical Support for WebSphere Portal.\n\nPortal Upgrades: Best Practices for V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21452611] For instructions on how to validate your environment prior to the upgrade, see the instructions for running the Health Checker tool for WebSphere Portal at:\n\nHealth Checker tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] IMPORTANT: Certain security configurations can cause failures with the upgrade. Please check the following technote to see if this may apply to your environment.\n\nFix Pack 7.0.0.1 fails at action-import-defaultnodes-wp.filestore/base task. [http://www.ibm.com/support/docview.wss?uid=swg21496067] \n 1. Perform the following steps before installing Combined Cumulative fix:\n 1. Before you install this combined cumulative fix, check to see if the list of fixes already installed on your system is included in the list of fixes provided in this combined cumulative fix. If you have temporary, interim or cumulative fixes on your system that are not included in this Combined Cumulative Fix, then uninstall those fixes before installing this Combined Cumulative Fix and contact IBM Support for an updated version of that fix, or for more information. \n 2. If you are running an external Web server such as IBM HTTP server, stop the Web server. \n 3. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct. WebSphere Portal 7 introduced support for multiple profiles. If using multiple profiles, also verify that the information in each profile is correct. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7]. * Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file. \n * Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file. \n * Unix/Linux/Windows/IBM i Only: The WebSphere Portal Update Installer removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file: PWordDelete=false. \n * Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server. \n \n \n 4. Special considerations for multiple profiles or binary install or migration upgrade: 1. If you did a binary installation and created a WebSphere Portal profile later, or your Portal 7.0.0.x was migrated from 6.1.x, ensure that the PortalServer/wps.properties file correctly references the profile. The Portal Update Installer uses the wps.properties file to determine which profile is the primary profile to update. Failure to complete this step could result in an inoperable Portal server after the Combined Cumulative Fix installation completes. 1. Edit the /wps.properties file in a text editor \n 2. Add these two properties if they do not already exist:\n ProfileName=\n ProfileDirectory=\n \n Note: The ProfileDirectory property should use forward slash (/) instead of backslash (\\) on Windows.\n \n \n 2. If you have created multiple profiles. the Portal Update Installer will automatically upgrade all profiles. If you want to specify which profiles are updated, then complete the following steps: 1. Edit the /wps.properties file in a text editor \n 2. Add this property if it does not already exist:\n AutoUpdateMultipleProfiles=\n \n \n 3. If using Multiple Profiles, verify all your profiles are at the same level before starting upgrade.\n \n \n \n 5. Perform the following steps to download the Combined Cumulative Fix and the WebSphere Portal Update Installer: 1. Download the latest Combined Cumulative fix (e.g. 7.0.0.2-WP-WCM-Combined-CFPMnnnnn-CFnnn), and the latest WebSphere Portal Update Installer from http://www.ibm.com/support/docview.wss?uid=swg24027857 [http://www.ibm.com/support/docview.wss?uid=swg24027857]. \n 2. Create the PortalServer_root/update directory and extract the WebSphere Portal Update Installer file into this directory. \n 3. Create the PortalServer_root/update/fixes directory and extract the 7.0.0.2-WP-WCM-Combined-CFPMnnnnn-CFnnn.zip file into this directory, where n is the numbers associated with the version of the Combined Cumulative fix. Note for z/OS users: refer to Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670] for detailed descriptions of how to execute steps ii. and iii. above. \n \n \n \n \n \n\n\n2. Choose either the graphical user interface installation option or the command line installation option: \n\nNOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line). \n\nNOTE: If the installation fails, use the IBM Support Assistant [http://www.ibm.com/software/support/isa/] to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task. \n\n\nIf using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall=\"true\", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI. \n\nEnter the following command to launch the graphical user interface installation program: * Windows: PortalServer_root\\update> updatePortalWizard.bat Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh\n \n - OR -\n Perform the following steps to launch the installation program from the command line: 1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command. \n 2. Enter the following command to launch the installation program (NOTE: Enter the command on one line):\n \n * Windows: PortalServer_root\\update> updatePortal.bat -install\n -installDir \"\"\n -fix\n -fixDir \"\\update\\fixes\"\n -fixes < Cumulative fix > \n * Unix/Linux: PortalServer_root/update> ./updatePortal.sh -install\n -installDir \"\"\n -fix\n -fixDir \"/update/fixes\"\n -fixes < Cumulative fix > \n * IBM i: portal_server_root/update> updatePortal.sh -install\n -installDir \"\"\n -fix\n -fixDir \"/update/fixes\"\n -fixes < Cumulative fix > \n * z/OS: If the Health Checker Tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] has not been run then it needs to be run before installing the Combined Cumulative Fix. Execute the following commands to install the Combined Cumulative Fix: 1. From /bin directory:\n . ./setupCmdLine.sh \n 2. PortalServer_root/update> ./updatePortal.sh -install\n -installDir \"\"\n -fix\n -fixDir \"/update/fixes\"\n -fixes \n \n Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670]. Submit the JCLs, and then return here to continue.\n \n \n \n \n If you do not have any profiles at this point (because you are in the process of migration from WebSphere Portal 6.1 or Installing an additional node for a cluster or creating multiple profiles) no post installation steps are necessary and you can continue with the next steps that create the profiles as outlined by the according documentation.\n \n z/OS: If doing an upgrade as part of a migration from a previous version (eg. 6.x), run ./ConfigEngine.sh gather-migration-files command from the /ConfigEngine directory.\n \n z/OS: Run the following command: /PortalServer/bin/UpdateProfile.sh install CF skipPreCheckProfile\n \n All other platforms: To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].\n \n /PortalServer/bin/UpdateProfile.bat|.sh install CF\n \n This cumulative fix provides updates to OSGi bundles. After installing the cumulative fix, run \"/bin/osgiCfgInit.sh\" (for IBM i the command is just osgiCfgInit, for Microsoft Windows the command is osgiCfgInit.bat) to clear the caches and make the OSGi container pick up the updates to the modified OSGi bundles. Note that it is recommended to stop the portal server before running the osgiCfgInit command. \n * \n * \n\n3. Perform the following post installation steps: \n * If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps:\n 1. Regenerate the Web server plugin. \n 2. Copy the plugin-cfg.xml file to the Plugin directory. \n 3. Restart the Web server.\n \n \n Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to installing the Combined Cumulative fix. 1. To update the deployed remote rendering portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory \n * Log in to Portal as the Portal Administrator \n * Navigate to: Administration / Portlet Management / Web Modules \n * Find and select the remote rendering portlet web module \n * Click the Update Portlet Icon to the right of the selected portlet \n * Select the updated portlet WAR file located in: /PortalServer/wcm/prereq.wcm/installableApps \n * Click Next and Finish\n \n \n 2. To update the deployed PDM Doc List Portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory \n * Log in to Portal as the Portal Administrator \n * Navigate to: Administration / Portlet Management / Web Modules \n * Find and select the PDM Doc List Portlet web module \n * Click the Update Portlet Icon to the right of the selected portlet \n * Select the updated portlet WAR file located in: /PortalServer/wcm/prereq.wcm/installableApps \n * Click Next and Finish\n \n \n 3. Log out of Portal for changes to take effect.\n \n Clear the browser cache before using the updated Web Content Manager. Review the following documentation \"Configuration Changes and Options introduced in WP/WCM V7.0.0.1 and 7.0.0.2 Combined Cumulative Fixes\" [http://www.ibm.com/support/docview.wss?uid=swg27021250] to see if it applies to your environment.\n \n\n\n\n\n\nBack to top \n\n\n\n\n\n\nSteps for uninstalling Combined Cumulative Fix \n\nNOTE: Changing the server context root after upgrading is an unsupported uninstall path. To uninstall after changing the context root, you must first change the server context root back to the values of the previous version. \n\nNOTE: Configuring Portal Server from a stand-alone environment to a cluster environment after upgrading is an unsupported uninstall path. \n\n 1. Perform the following steps before you uninstall the Combined Cumulative Fix: 1. If you are running an external Web server such as IBM HTTP server, stop the Web server. \n 2. Verify that the information in the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_comp.properties files are correct. If using multiple profiles, also verify that the information in each profile is correct. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7]. * Enter a value for the PortalAdminPwd and WasPassword parameters in the wkplc.properties file. \n * Ensure that the DbUser (database user) and DbPassword (database password) parameters are defined correctly for all database domains in the wkplc_dbdomain.properties file. \n * If using a database other than the default, grant permissions to databases within the framework by setting the DbUser (database user) and DbPassword (database password) parameters in the wkplc_dbdomain.properties file. \n * Unix/Linux/Windows/IBM i Only: The WebSphere Portal Update Installer removes plain text passwords from the wkplc*.properties files. To keep these passwords in the properties files, include the following line in the wkplc.properties file: PWordDelete=false. \n * Ensure that the value of the XmlAccessPort property in wkplc_comp.properties matches the value of the port used for HTTP connections to the WebSphere Portal server. \n * WebSphere Portal 7 introduced support for multiple profiles. During the Combined Cumulative Fix uninstall the primary profile is downgraded first if one exists (The Update Installer also supports the update case for a binary only install without profiles). The primary profile is identified by two properties, ProfileDirectory and ProfileName. Ensure these properties are set before starting the downgrade process. \n * If using Multiple Profiles, verify all your profiles are at the same level before starting downgrade.\n \n \n \n \n \n 2. Choose either the graphical user interface uninstallation option or the command line uninstallation option:\n \n NOTE: Not all platforms can use the graphical user interface (IBM i and z/OS can only use command line).\n \n NOTE: If the uninstallation fails, use the IBM Support Assistant [http://www.ibm.com/software/support/isa/] to access support-related information and serviceability tools for problem determination. For IBM i, download ISA on a system other than IBM i. On the Support Assistant Welcome page, click Service. Then click the Create Portable Collector link to create a remotely collect the data from your IBM i system. Fix what is causing the problem and then rerun the installation task. \n \n \n If using the Universal PUI, (which does not include the bundled Java environment), run the following command, setupCmdLine.bat for Windows or . ./setupCmdLine.sh for Unix/Linux from the was_profile_root/bin directory to set up the Java environment for the graphical user interface installation program. When updating a Portal that does not have a profile because it was installed with isBinaryInstall=\"true\", then run setupCmdLine.bat|.sh from PortalServer_root/bin. z/OS users can not use the Universal PUI.\n * Enter the following command to launch the graphical user interface uninstallation program: * Windows: PortalServer_root\\update> updatePortalWizard.bat \n * Unix/Linux: PortalServer_root/update> ./updatePortalWizard.sh\n \n - OR -\n \n \n \n * Perform the following steps to launch the uninstallation program from the command line: 1. Stop any active application servers using the stopServer command. To see which application servers are active use the serverStatus command. \n 2. Enter the following command to launch the uninstallation program (NOTE: Enter the command on one line): * Windows: PortalServer_root\\update> updatePortal.bat -uninstall\n -installDir \"\"\n -fix\n -fixes < Cumulative fix > \n * Unix/Linux: PortalServer_root/update> ./updatePortal.sh -uninstall\n -installDir \"\"\n -fix\n -fixes < Cumulative fix > \n * IBM i: portal_server_root/update> updatePortal.sh -uninstall\n -installDir \"\"\n -fix\n -fixes < Cumulative fix > \n * z/OS: If the Health Checker Tool for WebSphere Portal V7.0 [http://www.ibm.com/support/docview.wss?uid=swg27020200] has not been run then it needs to be run before uninstalling the Combined Cumulative Fix. Execute the following commands to uninstall the Combined Cumulative Fix: 1. From /bin directory:\n . ./setupCmdLine.sh \n 2. PortalServer_root/update> ./updatePortal.sh -uninstall\n -installDir \"\"\n -fix\n -fixes \n \n Alternatively, the steps i. and ii. above can be executed via JCL. Customize the JCL samples from the following link: Installing interim fixes on WebSphere Portal Enable for z/OS using Portal Update Installer [http://www.ibm.com/support/docview.wss?uid=swg21326670]. Submit the JCLs, and then return here to continue.\n \n \n \n \n \n \n \n \n \n 3. Run the following command: * z/OS: /PortalServer/bin/UpdateProfile.sh uninstall CF skipPreCheckProfile \n * All other platforms: To downgrade a profile after an uninstall, the following command can be used to downgrade all profiles (including the primary profiles). See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].\n \n /PortalServer/bin/UpdateProfile.bat|.sh uninstall CF \n \n \n \n \n 4. If you are running an external Web server such as IBM HTTP server and you are using the WebSphere Application Server automatic generation and propagation of the plugin, then just restart the Web server. If you are not using the automatic generation and propagation, then perform the following steps: 1. Regenerate the Web server plugin. \n 2. Copy the plugin-cfg.xml file to the Plugin directory. \n 3. Restart the Web server.\n \n \n 5. If you previously customized any configuration files in the wp_profile_root/PortalServer/config directory, check to see if uninstalling the cumulative fix affected those files by restoring a version of the files that was saved when the cumulative fix was originally installed. If it did affect the files, you must perform the same customization on the restored version of each file. \n 6. Redeploy your customization, including JSPs, to the WCM portlets if you are using Web Content Manager and you customized the portlets prior to uninstalling the Combined Cumulative fix. 1. To update the deployed remote rendering portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory \n * Log in to Portal as the Portal Administrator \n * Navigate to: Administration / Portlet Management / Web Modules \n * Find and select the remote rendering portlet web module \n * Click the Update Portlet Icon to the right of the selected portlet \n * Select the updated portlet WAR file located in: /PortalServer/wcm/prereq.wcm/installableApps \n * Click Next and Finish\n \n \n 2. To update the deployed PDM Doc List Portlet: * Backup any files (e.g. custom JSPs) which have been copied to the deployed remote rendering portlet WAR directory \n * Log in to Portal as the Portal Administrator \n * Navigate to: Administration / Portlet Management / Web Modules \n * Find and select the PDM Doc List Portlet web module \n * Click the Update Portlet Icon to the right of the selected portlet \n * Select the updated portlet WAR file located in: /PortalServer/wcm/prereq.wcm/installableApps \n * Click Next and Finish\n \n \n 3. Log out of Portal for changes to take effect.\n \n \n 7. Clear the browser cache before using the updated Web Content Manager.\n\n\n\n\nBack to top \n\n\n\n\n\n\n\nKnown issues for latest Combined Cumulative Fix \n\n\nProblem: There may be browser / functional issues in themes and in WCM when running 7002 CF levels against Internet Explorer 11 or Microsoft Edge. \nSolution: It is recommended to run these browsers in compatibility mode as necessary. Also, note that some pieces of WCM functionality (exs. inability to close Workflow dialogs, Applet issues) may not work correctly with these browsers even in compatibility mode as they are not supported. \n\nProblem: Inline help may not appear correctly after CF29 update on zOS. \nSolution: From the /ConfigEngine directory, run task \n\n./ConfigEngine.sh expand-ear-wp.iehs.ear \n\nThen restart the Portal server. \n\n\nProblem: When using versions earlier than 'Java 6 update 45' or 'Java 7 update 51', a security pop-up dialog or error will be seen every time the WCM FileTransferApplet or Ephox EditLive editor is instantiated. \nSolution: It is recommended to upgrade the Java runtime environment level to either 'Java 6 update 45' or 'Java 7 update 51' or later. Please refer to the following URL: swg21663838 \n\n\nProblem: After you enter a number into the number element/component, and then save the content/component more than twice, you will notice that the number field gets populated with some dots, i.e. 123.456.78. If you then click on Save again, you will get the following error: \n'Enter a valid number. ( content/component name here)' \nSolution: The workaround is to remove the dots and save again. \n\n\nProblem: Page theme is changed to current Portal default theme when changing page content layout. \nSolution: The workaround would be to change the page theme back to \"Inherit Parent Theme\". A fix for this issue is scheduled to be included in a future Combined CF. \n\n\nProblem: After upgrading to a 7.0.0.2 Cumulative Fix and \"Portal 7.0.0.2\" theme has been set as the default portal theme, a user is unable to post to a blog or update a wiki using Microsoft Windows Internet Explorer. \nSolution: Perform the following steps to resolve the issue: 1. Navigate to Administration -> Manage Pages -> Contenet_Root -> Hidden pages. \n 2. Select \"Edit Page Properties\" for the hidden page named 'Web Content Management'. \n 3. On the 'Edit page: Web Content Management' page, extend 'Theme:' drop-down list and select \"-----Inherit Parent Theme-----\".\n\n\n\nProblem: WCM Authoring Search may not work after an upgrade to a 7.0.0.2 Cumulative Fix \nSolution: Perform the following steps to resolve the issue: 1. Edit the /PortalServer/jcr/lib/com/ibm/icm/icm.properties file in a text editor to verify all properties are correct. \n 2. Set jcr.textsearch.enabled=true \n 3. Change jcr.textsearch.indexdirectory to a corresponding location in the filesystem \n 4. Restart your Portal Server. \n 5. Create a new library or make changes in existing libraries\n\n\n\nProblem: When configuring Portal for use with a remote DB2 on z/OS database, the sample job provided for the database creation does not contain the statements required to create the storage groups. These take the form: \n\nCREATE STOGROUP group \nVOLUMES(' volume') \nVCAT category; \nCOMMIT; \n\nwhere, \ngroup is the name of the storage group for the database, \nvolume is the volume serial number of * to let SMS select the volume where the database will reside, \ncategory is the category name of the Integrated Catalog Facility. \n\nSolution: When using the EJPSCRDB sample job add the above statements for each storage group to the final version. These should be added at the beginning of \"Step 2\" of the sample job, just before the CREATE statements for the actual databases. \n\n\nProblem: Theme Policies are not supported by the Portal 7.0.0.2 theme. \nSolution: This is a known limitation. \n\n\nProblem: Client-side aggregation is not supported by the Portal 7.0.0.2 theme. \nSolution: This is a known limitation. \n\n\nProblem: The WebSphere Portal 7.0.0.2 theme does not support Sametime 8.5.1 \nSolution: This is a known limitation. \n\n\nProblem: Loading a page with the out of box default profile (Deferred) causes \"dojo is not defined\" error. \nSolution: Dojo is not available in view mode using the Deferred profile, which is the default out of box. Switch the page or theme to use the Full profile to access Dojo in view mode. For more information see URL: http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc [http://www.lotus.com/ldd/portalwiki.nsf/dx/Creating_the_module_profile_sdoc] \n\n\nProblem: The Portal 7.0.0.2 drag-and-drop framework does not support multi-selection and copying resources. \nSolution: This is a known limitation. This can be enabled by creating a custom drag and drop source and enabling these features. \n\n\nProblem: The deploy-7002-theme task fails \nSolution: The Portal 7.0.0.2 theme requires several artifacts from the \"Page Builder\" theme to exist on the server. If you have removed the theme or if you are coming from a migrated environment where the theme never existed, you will need to add the Page Builder theme back to the system before running the deploy-7002-theme task. Please see the \"Additional instructions for a migrated environment\" section at the following URL for more information http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc [http://www.lotus.com/ldd/portalwiki.nsf/dx/Installing_a_new_theme_sdoc] \n\n\nProblem: The Feedspace portlet in Portal 7.0.0.2 may show JavaScript issues. \nSolution: The Feedspace portlet needs to be redeployed to resolve this. Use the Portal administration area to update the the SyndicatedFeedPortlet.war. Use the PortalServer/bp/wp.bp.feedspace/installableApps/SyndicatedFeedPortlet.war to do this update. \n\n\nProblem: If a WCM cumulative fix is installed on a Websphere Portal 7.0.0.2 where the date of the install is later than the date on which the cumulative fix was packaged, then the update-wcm task will fail to overwrite the WCM war files from the base version. \nSolution: To workaround this problem, the war files from [PortalServer]\\wcm\\prereq.wcm\\installableApps have to be manually copied to [PortalServer]\\installableApps. Once this is done, the update-wcm task will execute successfully. \n\n\nProblem: Newly added WCM libraries might not be listed in the \"Web Content Libraries\" portlet on all nodes of the cluster due to an issue in cache replication. \nSolution: The workaround would be to restart nodes which have the stale library list. A fix for this issue is scheduled to be included in a future Combined CF. \n\n\nProblem: After uninstall of the combined cumulative fix, WPVersionInfo shows IBM WebSphere Portal Configuration Framework (CFGFW) at the upgraded version level. \nSolution: This is expected. The CFGFW version level shown after the uninstall of the combined cumulative fix remains at the upgraded level. There is no functional problem. \n\n\nProblem: If you plan to configure Computer Associates eTrust SiteMinder as your external security manager to handle authorization and authentication, the XML configuration interface may not be able to access WebSphere Portal through eTrust SiteMinder. \nSolution: To enable the XML configuration interface to access WebSphere Portal, use eTrust SiteMinder to define the configuration URL (/wps/config) as unprotected. Refer to the eTrust SiteMinder documentation for specific instructions. After the configuration URL is defined as unprotected, only WebSphere Portal enforces access control to this URL. Other resources such as the /wps/myportal URL are still protected by eTrust SiteMinder. If you already set up eTrust SiteMinder for external authorization and you want to use XMLConfiguration Interface (xmlaccess), make sure you have followed the procedure to allow for xmlaccess execution. \n\n\nProblem: If using the Firefox browser, portlets cannot be dragged to a page from the palette. It is necessary to click the + icon next to the portlet in the palette to add it to the page. \nSolution: This is documented as a known limitation. \n\n\nProblem: If an error is seen starting server \"WebSphere_Portal\" during the upgrade, a possible cause is that this server start is automatically enabled as part of the node reset state. \nThe error would appear similar to the following as part of the \"action-start-portal-server-standard\" task : \"ADMU3027E: An instance of the server may already be running: WebSphere_Portal\" \nSolution: Log into the WAS Admin Console. Under Application Servers-> WebSphere_Portal, ensure that the Monitoring Policy for \"Node restart state\" is set to Stopped for all WebSphere Portal servers that are part of the environment. \n\n\nFor a list of known issues for Previous WebSphere Portal 7.0.0.2 Combined Cumulative Fixes, see IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Previous Known Issues [http://www.ibm.com/support/docview.wss?uid=swg27023912]for details. \n\nBack to top \n\n\n\n\n\n\nAdditional information \nYou can find additional information on the WebSphere Portal support page [http://www-306.ibm.com/software/genservers/portal/support/]. \n\nBack to top \n\n\n\n\n\n\nTrademarks and service marks \nFor trademark attribution, visit the IBM Terms of Use [http://www.ibm.com/legal/us/] Web site. \n\nBack to top", "question": "Installation of Portal 7.0 CF fails with version mismatch \n\nInstallation of Portal 7.0 CF fails with message,\n\n\"Profile version is not the same as portal binary version before updating portal binary.\"", "answer": "To update a profile after an upgrade, the following command can be used to update profiles that are not included in AutoUpdateMultipleProfiles. All profiles that were not included in AutoUpdateMultipleProfiles need to be updated after the upgrade is done. All profiles must be at the same level for future upgrades to be applied. See the following link for multiple profiles Supporting multiple profiles: wp7 [http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Supporting_multiple_profiles_wp7].\n \n /PortalServer/bin/UpdateProfile.bat|.sh install CF"} +{"id": "TRAIN_Q120", "document": "IBM WebSphere DataPower M/T 9235 appliance might incorrectly report failure of both power supplies - United States TECHNOTE (FAQ)\n\nQUESTION\n The IBM WebSphere DataPower M/T 9235 appliance might incorrectly report the failure of both power supplies. This message is not reported on all appliances and can occur rarely in the field. \n\nANSWER\nThe following message would be present in the DataPower logs: \n\nSystem power supply #2 has failed.\n\nor logging event code: \n\n0x80400022 System power supply #2 \n\n\nThe problem can be confirmed by issuing the following commands on the appliance CLI:\n\nco \ntest hardware \nexit \n\nThe following output from the test hardware command confirms this problem: \n\n[failure] Power supply '1' has no AC input power, or is not present.\n[failure] Power supply '2' has no AC input power, or is not present.\n\nOther results in the test hardware command might also show incorrect values.\n\nThis problem does not affect the operation of the appliance other than the continuous reporting power supply failure message. \n\nTo confirm the power supplies are working normally you may check the LED status on the power supplies. If the LED's are green the power supplies are working normally.\n\n\nTo recover from the false errors perform a reboot of the appliance: \n\nFrom the WebGUI: \n\nControl Panel → System Control → In the “Shutdown” section choose “Reboot System” then click “Shutdown” \n\n \n\nFrom the CLI: \n\ntop \n\nshutdown reboot \n\ny \n\n\nThis problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages. In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged. The highly intermittent error rarely occurs again on the same appliance \n\nIf the issue reoccurs on the same appliance contact IBM DataPower support [http://www.ibm.com/support/docview.wss?uid=swg21236322] with the following information: \n\n1) How many times have you seen the issue on the same appliance? \n\n2) Gather the outputs for the following CLI commands:\nshow clock\nshow version\nshow ipmi\nshow sensors-other\nconfig\nservice show\ntest hardware", "question": "I am receiving AC power supply failures on my DataPower 9235 appliance. How can I resolve this? \n\nI am observing the following errors on my DataPower 9235 device:\n\n[failure] Power supply '1' has no AC input power, or is not present. [failure] Power supply '2' has no AC input power, or is not present.\n\nHow can this be resolved? ", "answer": "In most cases, a reboot of the appliance will reset the sensors and no additional errors are logged."} +{"id": "TRAIN_Q121", "document": "IBM Default number of threads for ncp_poller - United States Available threads for ncp_poller TECHNOTE (FAQ)\n\nQUESTION\n What are the number of threads assigned by default for ncp_poller? Is the same number of threads applicable for additional Pollers too? \n\nANSWER\nThere are 100 threads assigned for default Pollers in all three releases (v3.7, v3.8 & v3.9). \nThe additional poller is a new feature in v3.8 and higher versions, so additional Poller threads is not applicable for v3.7. But when you create additional pollers in v3.8/v3.9 same # of thread (i.e. 100) pool is assigned.\n\nIn v3.8, v3.9 - you can also increase the default 100 to a higher value by modifying and uncommenting the following line in $NCHOME/etc/precision/NcPollerSchema.cfg\n//update config.properties set BatchExtraThreads = 150;", "question": "ncp_poller failed with Out-of-memory in ITNM 3.9 FP4+IF1. What went wrong?. \n\nncp_poller is failed with out-fo-memory even if we have ITNM 3.9 FP4+IF1 latest FP\n\n2016-04-11T03:02:09: Fatal: F-RIV-002-014: [31869t] CRivError.cc(386) Out-of-memory - This process has run out of memory or exceeded the operating system memory limit for a 32 bit application - You must take action to reduce the amount of data this application is having to process new handler called\n\nHow to resolve this issue?.\n", "answer": "There are 100 threads assigned for default Pollers in all three releases (v3.7, v3.8 & v3.9). \nThe additional poller is a new feature in v3.8 and higher versions, so additional Poller threads is not applicable for v3.7. But when you create additional pollers in v3.8/v3.9 same # of thread (i.e. 100) pool is assigned.\n\nIn v3.8, v3.9 - you can also increase the default 100 to a higher value by modifying and uncommenting the following line in $NCHOME/etc/precision/NcPollerSchema.cfg\n//update config.properties set BatchExtraThreads = 150;"} +{"id": "TRAIN_Q122", "document": "IBM Some portal resources have been updated, however a long cache was set so the updates are not being served. - United States TECHNOTE (FAQ)\n\nQUESTION\nThe resolver uses the digest to cache some URLs like resource aggregator collections, and the digest remains the same between restarts. Resources like theme files are served from the browser or proxy cache (HTTP 304) and not loaded from the server.\n\n\nANSWER\nThe resolver uses the digest to cache some URLs like resource aggregator collections, and the digest remains the same between restarts. \nIn order to force a digest change (should some resources have changed and a long cache was set), you can set the \"digest.seed\" key in the WP ConfigService to any string value, which will be used in generating a new digest on server boot. This will force a digest change when you want a new one during a restart. \n\nChanging the digest setting generates different URLs, so the updated theme resources can be loaded from the server.", "question": "Why Theme Updates are not updated in the browser cache ? \n\nIf you change graphics in page header. Then packed the war file and update it via the Integrated Solutions Console. But the old graphic is still displayed until the user press Ctrl + F5 in Internet Explorer.", "answer": "Changing the digest setting generates different URLs, so the updated theme resources can be loaded from the server."} +{"id": "TRAIN_Q123", "document": "IBM SCA destinations for IBM Business Process Manager (BPM), WebSphere Process Server (WPS) and WebSphere Enterprise Service Bus (WESB) are not preserved when uninstalling and reinstalling a service module - United States SCA.RecycleDestinations; custom properties; SCA destinations; event sequencing; SCA modules; message queue TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a Service Component Architecture (SCA) module is uninstalled, by default, its associated destinations are removed, even if there are still messages in the destination queue. In some situations, such as when Event Sequencing is used, messages on the destinations must be preserved.\n\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Process Server AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.0.0.5 Business Integration WebSphere Enterprise Service Bus SCA AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows, z/OS 7.5, 7.0.0.5 \nPRODUCT ALIAS/SYNONYM\n BPM\nWPS\nWESB", "question": "Updating SCA applications & internal SCA module queues When updating an existing SCA module using the ISC, I noticed that internal SCA queues (sca//...) on the SCA.SYSTEM bus) are deleted and recreated. One can potentially loose messages on these queues. Is there a fix to the problem?", "answer": "To resolve this issue, use the SCA.recycleDestinations custom Java™ virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations."} +{"id": "TRAIN_Q124", "document": "IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States 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", "question": "Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written If you are trying to install Portal v8.5 on WAS 8.5.5.5 or less it may fail when running the manageprofiles.sh. You will get this exception; SEVERE\ncom.ibm.ws.profile.cli.WSProfileCLIAugmentProfileInvoker\nexecuteWSProfileAccordingToMode\n1\nINSTCONFFAILED: Profile augmentation failed. For more\ninformation, consult\n/opt/IBM/WebSphere/AppServer8/logs/manageprofiles/portal01_create.log.", "answer": "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."} +{"id": "TRAIN_Q125", "document": "IBM Diagnosing a java.lang.StackOverflowError - United States StackOverflow; overflowing; recursion; recursively; jit; JustInTime; Hot; Spot; WebSphere; Just-In-Time TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Stack Overflow exceptions can occur when a thread stack continues to grow in size until reaching the maximum limit. \n\nSYMPTOM\n A stack overflow can result from: \n\n * A deeply nested application \n * An infinite loop within an application \n * A problem in just-in-time (JIT) compiled code \n * Applications requiring a larger stack size, especially ones relying on XML, GUI, or java2D classes. \n * Native method calls\n\n\nStack overflow issues are frequently masked by Out of Memory exceptions. By resolving the memory constraints, the stack overflow can be resolved. \nCAUSE\nWhen a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java™ Virtual Machine (JVM) process, or the native stack size configured by the operating system. \nSome applications require stacks that are larger than the default size; for example, a graphics-intensive Java program can require a larger stack, which may require an increase in the stack size to avoid StackOverflow.\n\n\nDIAGNOSING THE PROBLEM\nLook for either Out of Memory messages or java.lang.StackOverflow in the server logs. The process may continue to run after either of these messages are seen. \n\n\nIf a crash did occur, a javacore should have generated on IBM SDK. You will either see the signal as SIGSEGV, SIGILL, SIGABRT, or SIGBUS. Usually the current thread will indicate the following\n\n\n\n\npending=java.lang.StackOverflowError \nRESOLVING THE PROBLEM\n \n\n\n\n\n[/support/docview.wss?uid=swg21162896&aid=1]Explanations and Solutions\n[/support/docview.wss?uid=swg21162896&aid=2]Detailed Configuration Options \n\n\n\n\n\n\n \n\nExplanations and Solutions \n\nInfinite Recursion \nIf an application is performing recursion, the maximum stack size can easily be reached and a Stack Overflow exception is thrown. The thread stack has a limited size and eventually its space will run out as the thread stack grows without bounds. \n\nSome traits of recursion: \n- Large thread stacks that appear to repeat \n- An infinite loop that continuously spawns off threads \n- Very large XML documents loaded into the Document Object Model (DOM) \n- JSP or servlets calling itself (usually by executing forward or include to itself) \n- Repeated calls in native functions \n\nIncreasing the thread stack size allows for larger thread stacks. However if the recursion continues to trigger a stack overflow, the next step is to identify what code is causing the recursion from javacores, thread dumps, or even system core files. \n\nA thread stack that indicates it's too large to display can be an indicator of stack overflow. This is especially true if the stack appears to repeat (such as recursive method calls). \n\nJIT/HotSpot Compiled Code \n\nThe JIT/HotSpot compiler (JIT) is designed to speed up the JVM execution times by compiling method calls. This can speed up execution time, but as more aggressive optimizations are used, this can inadvertently cause recursion, resulting in stack overflow or crash. The documents linked below explain how to debug JIT and HotSpot compiler issues: * JIT Problem Determination for IBM SDK 5.0 and 6.0 using -Xjit [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21294023] \n * Debugging HotSpot failures on the Solaris and HP-UX operating environment [http://www.ibm.com/support/docview.wss?rs=0&uid=swg21081179]\n\n\n\nDepleted Native Stack \nIt is almost guaranteed that a crash will occur if the native stack runs out of space. System cores can be used to identify long and possibly recursively looping native thread stacks. \n\nTo resolve, increase the native stack size (usually by adjusting the operating system limit for stack size) to accommodate the recursive native calls; however, identifying the recursive native calls will help determine the root cause of the stack overflow. \n\n\n\n\n[/support/docview.wss?uid=swg21162896&aid=3] Back to top \n\n[http://www.ibm.com/i/v14/rules/dotted_blue_rule_443.gif] \n\n \n\nDetailed Configuration Options \n\nAdjusting the Stack Sizes (Xss and Xmso) options \nIf this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources. \n\nFor every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow. \n\n * Maximum Thread Stack Size (-Xss)\n * \n * \n * \n * \n * -Xss \n * \n * \n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n * \n * \n * \n * there is no distinction between native and thread stack sizes\n * \n * only \n * \n * HP-UX\n * \n * \n * \n * -XX:MainThreadStackSize= \n * \n * \n * \n * \n * \n * \n * \n * Initial Thread Stack Size (-Xiss)\n * \n * This is only for distributed platforms (AIX, Linux, Windows)\n * \n * \n * \n * \n * \n * -Xiss \n * \n * \n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n * \n * Initial Native Stack Size (-Xmso)\n * \n * This is only for distributed platforms (AIX, Linux, Windows)\n * \n * \n * \n * \n * \n * \n * -Xmso \n * \n * \n * \n * nn[k|m|g|K|M|G]\n * \n * \n * \n * \n\n\n\nDefault Values \nThis is a chart of default sizes for the various stack size arguments. This is subject to change due to upgrades of the SDK. \n\n[/support/docview.wss?uid=swg21162896&aid=4]\nValue [/support/docview.wss?uid=swg21162896&aid=4]\nAIX [/support/docview.wss?uid=swg21162896&aid=4]\nLinux [/support/docview.wss?uid=swg21162896&aid=4]\nWindows [/support/docview.wss?uid=swg21162896&aid=4]\nSolaris [/support/docview.wss?uid=swg21162896&aid=4]\nHP-UX [/support/docview.wss?uid=swg21162896&aid=4]\nInitial Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]\n2KB [/support/docview.wss?uid=swg21162896&aid=4]\n2KB [/support/docview.wss?uid=swg21162896&aid=4]\n2KB [/support/docview.wss?uid=swg21162896&aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&aid=4]\nMaximum Thread Stack Size [/support/docview.wss?uid=swg21162896&aid=4]\n256KB (32-bit)\n512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]\n256KB (32-bit)\n512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]\n256KB (32-bit)\n512KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&aid=4]\nNot Adjustable [/support/docview.wss?uid=swg21162896&aid=4]\nNative Stack Size [/support/docview.wss?uid=swg21162896&aid=4]\n256KB [/support/docview.wss?uid=swg21162896&aid=4]\n256KB [/support/docview.wss?uid=swg21162896&aid=4]\n32KB (32-bit)\n256KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]\n512KB (32-bit)\n1024KB (64-bit) [/support/docview.wss?uid=swg21162896&aid=4]\n64KB (PA-RISC)\n1024KB (Itanium) [/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=4]\n[/support/docview.wss?uid=swg21162896&aid=5] Back to top \n\n\n\nExamples of Stack Overflow \n\nServer Logs \nThese logs may contain references to StackOverflow, alongside other messages. Thread stacks may accompany these messages, indicating if there is a recursive call. \n * SystemOut.log example\n \n * [3/14/15 3:14:15:926 CST] 31415926 BaseMap W CWOBJ0006W: An exception occurred:\n * \n * com.ibm.websphere.objectgrid.ObjectGridRuntimeException: java.lang.StackOverflowError\n * \n * <>\n * \n \n * \n * \n * \n * SystemErr.log example\n \n * [3/14/15 3:14:15:926 PST] 31415926 SystemErr R Caused by: java.lang.StackOverflowError\n * \n * at java.util.Hashtable.get(Hashtable.java:461)\n * \n * at com.ibm.ws.webcontainer.srt.SRTServletRequest.getParameter(SRTServletRequest.java:1257)\n * \n * at psdi.webclient.system.session.WebClientSession.applySkin(WebClientSession.java:295)\n * \n * at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1177)\n * \n * at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)\n * \n * at psdi.webclient.system.controller.AppInstance.render(AppInstance.java:1213)\n * \n * ...\n * \n \n * \n\nJavacore \n\nIn javacores, look for \"StackOverflowError\" in the thread name entry: 3XMTHREADINFO \"ORB.thread.pool : 19\" (TID:10167F78, sys_thread_t:E072BCE0, state:R, native ID:E06BEBA0) prio=5: pending=java.lang.StackOverflowError \nSystem Dump (processed with jextract and DTFJ Dump Analyzer) \n\nLook for this message near the end of a very large stack. This particular example had 1000 recursively called entries. Java stack frames dump is too long: \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "completeness report causes StackOverflowError in Decision Center \n\nWhen running the completeness report in Decision Center we sometimes get a StackOverflowError such as:\n\n ...\n Caused by: java.lang.StackOverflowError\n at ilog.rules.validation.solver.IlcIntScalProd.extract(IlcIntScalProd.java:89)\n at ilog.rules.validation.solver.IlcIntExpr.getPIntExp(IlcIntExpr.java:156)\n ...\n\n", "answer": "Adjusting the Stack Sizes (Xss and Xmso) options \nIf this does not work, you can adjust the stack sizes. Doubling the stack size is suggested as a first step; however, every thread that the JVM creates will consume memory. Be careful to not exhaust your physical and heap memory resources. \n\nFor every Java thread, there are two stacks that are utilized. One is for Java code for method calls, and the other is for native C code (on Solaris and HP-UX, only the native stack is utilized). These are adjustable and can be raised to provide more room on the stacks to prevent an overflow."} +{"id": "TRAIN_Q126", "document": "IBM Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM MQ could allow an authenticated user to potentially cause a denial of service by issuing an incorrect saved channel status inquiry. \n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]\nDESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.\nCVSS Base Score: 3.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ 9.0.2 Continuous Delivery \n\nIBM MQ Appliance 9.0.x Continuous Delivery \n\nIBM MQ 9.0 LTS \n\nIBM MQ 8.0 \n\nIBM MQ 8.0 Appliance\n\nREMEDIATION/FIXES\nIBM MQ 9.0.2 Continuous Delivery \n\nApply IBM MQ 9.0.3 Continuous Delivery release or later. \n\nIBM MQ Appliance 9.0.x Continuous Delivery \n\nApply continuous delivery update 9.0.3 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&release=9.0.2&platform=All&function=all] or later. \n\nIBM MQ 9.0 LTS \n\nApply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]. \n\nIBM MQ 8.0 \n\nApply Fix Pack 8.0.0.7 [http://www-01.ibm.com/support/docview.wss?uid=swg22005832]. \n\nIBM MQ Appliance 8.0 \n\nApply Fix Pack 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.5&platform=All&function=all].\n\nWORKAROUNDS AND MITIGATIONS\nIBM MQ Appliance; Affected Queue manager must be restarted. \n\nIBM MQ 9.0.2 CD : Restart the failed command server on the queue manager. \n\nIBM MQ 9.0 LTS : Restart the failed command server on the queue manager. \n\nIBM MQ 8.0 : Restart the failed command server on the queue manager.\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 09 Jan 2018: Updated\n06 Oct 2017: Updated at 9002 GA\n15 Jun 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.", "question": "Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) I need to understand details regarding Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236). Where can I find this information?\n", "answer": "CVEID:CVE-2017-1236 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1236]\nDESCRIPTION:IBM MQ could allow an authenticated user to potentially cause a denial of service by saving an incorrect channel status inquiry.\nCVSS Base Score: 3.1\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/124354 [https://exchange.xforce.ibmcloud.com/vulnerabilities/124354]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L)"} +{"id": "TRAIN_Q127", "document": "IBM How to troubleshoot the error \"Failed to process response headers\" - United States datapower; failed; parse; process; error; network; connection; persistent; headers; response headers; failed to process response headers; 7993; 7993; 7993; machine type 7993 TECHNOTE (FAQ)\n\nQUESTION\n What does this error mean?\n\nGeneral error that is always seen:\n[servicetype][error] wsgw(policyrule): tid(196761)[error][x.x.x.x]: Failed to process response headers\n\nSpecifically from a Web Service Gateway:\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[10.2.3.4]: Backside header failed to parse due to: Failed to process response headers\n[ws-proxy][error] wsgw(Proxy): tid(1234567)[error][10.2.3.4]: Failed to process response headers \n\nAdditional log information might be seen while at the debug log level.\n\n\nCAUSE\nWhen you read this error, keep in mind that it is thrown from a rule within a policy of a service. This error almost always means that the policy did not receive any data. If you increase the logging from error to debug, you should see network failures surrounding the response header error.\n\n\n\nIn almost every event, this error is caused by a connection failure.\nThe error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error.\n\n\nANSWER\nThe classic causes of this are either of these two: \n\n\n\n \n\nA slow response that causes the connection to timeout before receiving the response\nA failed connection attempt due to a closed persistent connection or some other connection issue that prevents the WebSphere® DataPower device® from connecting to the backend. For example, a reused connection would be attempted and found to already be closed out by something outside of DataPower®.\nAn example of this is explained here:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1 [http://www-01.ibm.com/support/docview.wss?uid=swg21417934&wv=1]\n\nThere are a broad range of network errors that can trigger this to error. A packet trace is the key to capture the problem and confirm what type of failure is the cause. A log with event subscription of \"all\" \"debug\" will also help correlate and confirm the packet trace data.\n\nIn some cases, a simple work around to try is to lower the DataPower persistent timeout or disable persistent connections. If this does not prevent the problem, then analysis of the packet trace and error report are required.", "question": "How precise is DataPower's backside persistent timeout value related to intermittent \"Failed to Process Response Headers\" error messages? \n\nI have a service on DataPower with a backside persistent timeout value set to 28 seconds. The actual backend device has a persistent timeout setting of 30 seconds.\n\nSince my service is configured with a lower persistent timeout value than 30 seconds, why am I still seeing the following error intermittently?\n\nWed June 25 2009 09:20:02 [0x80000001][xsltmsg][error] mpgw (MyGateway): tid(8675309)[error][9.x.x.x]: Failed to process response headers", "answer": "In almost every event, this error is caused by a connection failure.\nThe error is correct, the service did not receive any response headers or data. The key to help confirm this is to increase the log level to debug. This will allow you to see the network debug errors around the context of the service error."} +{"id": "TRAIN_Q128", "document": "IBM Content Collector Configuration Store is corrupted - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Content Collector Configuration Store Service cannot be started successfully due to database corruption. \n\nSYMPTOM\nCannot start the IBM Content Collector Configuration Store Service\n\n\nCAUSE\nTransaction log gets corrupted when IBM Content Collector server runs out of disk space. \n\nRESOLVING THE PROBLEM\n\n\n\n 1. Shutdown the IBM Content Collector Configuration Store Service if it is running. \n 2. Make a backup copy of all files under the following directory:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\n \n C:\\ProgramData may be hidden by default. Show hidden folders by changing the configuration in Folder and Search options > View tab > Hidden files and folders > Show hidden files, folders, and drives. \n 3. Free up disk space on the drive \n 4. Delete the following files:\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\*\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solmsg.out\n C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\solerror.out\n \n Important: \n Delete only the files under C:\\ProgramData\\IBM\\ContentCollector\\ConfigurationStore\\logs\\. \n Do not delete the folder itself.\n \n 5. If restoring the configuration store to a previously backed up copy is required, run afuConfigStoreTool -backup to restore the backup copy. See production documentation for more information on running this tool. Otherwise, proceed to the next step. \n 6. Restart IBM Content Collector services.\n \n\nRELATED INFORMATION\n IBM Content Collector Information Center [http://pic.dhe.ibm.com/infocenter/email/v4r0m0/index.jsp]", "question": "ICC Configuration Store Service is hung? ICC Configuration Store Service is hung and is not responding to start or stop commands. This was observed due to a potential issue with server running out of disk space. What is causing this? ", "answer": "Transaction log gets corrupted when IBM Content Collector server runs out of disk space."} +{"id": "TRAIN_Q129", "document": "IBM Identifying Indexing errors in Atlas database - United States TECHNOTE (FAQ)\n\nQUESTION\n How do I identify Indexing errors in Atlas database? \n\nCAUSE\nSometimes encrypted and password protected documents cause document indexing errors\n\nANSWER\n \n\n 1. Login to Atlas database as PSSAPL user \n 2. Run select * from ctx_user_index_errors; \n 3. Copy the value in the ERR_TEXTKEY Field \n 4. Run select * from documentlibrary where rowid=' '; \n 5. This will list the document which has the indexing error", "question": "How do I identify Indexing errors in Atlas database? How do I identify Indexing errors in Atlas database? ", "answer": "Login to Atlas database as PSSAPL user \n 2. Run select * from ctx_user_index_errors; \n 3. Copy the value in the ERR_TEXTKEY Field \n 4. Run select * from documentlibrary where rowid=' '; \n 5. This will list the document which has the indexing error"} +{"id": "TRAIN_Q130", "document": "IBM DataPower Gateways Firmware Support Lifecycle - United States datapower;support;lifecycle;support lifecycle;maintenance;firmware;release;releases;firmware releases;upgrade;upgrades;features;defect NEWS\n\nABSTRACT\nThis document provides information on the IBM DataPower Gateway Firmware Support Lifecycle.\n\nCONTENT\nIBM® DataPower® Gateway is a purpose-built gateway that provides security, traffic control, mediation and optimized access to a full range of mobile, web, application programming interface (API), service-oriented architecture (SOA), B2B and cloud workloads. It supports multi-cloud deployment and is available in Docker container, Linux application, VMware virtual machine and physical appliance form factors.\n\nIBM provides flexible support options to meet the needs of your business and minimize any business impact. The IBM DataPower Gateways end-of-service support policy applies differently between hardware and firmware.\n\nHardware \n\nDataPower physical appliance hardware is supported for a minimum of five years, starting at the General Availability of the new product. Beginning with the 8436 models, standard appliance service and support is available for five years from the end-of-marketing (EOM) date as described in the IBM Appliance Support Handbook [http://www.ibm.com/support/customercare/sas/f/applhandbook/home.html].\n\nFor end-of-service information on physical appliances, see IBM DataPower Gateways End of Service dates [http://www.ibm.com/support/docview.wss?uid=swg21317845]. \n\nFirmware \n\nBusinesses are building modernized digital platforms to drive innovation and disruption within the industry. IBM DataPower Gateways are a core component in these platforms and it needs to deliver new business functionality to keep pace with business innovation.\n\nEffective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:\n\n 1. CD release approximately once per quarter * Only the most recent CD release is supported at a given time.\n \n \n 2. Long Term Support (LTS) release every 12 months. * LTS releases are for customer seeking enhanced stability and do not wish to upgrade on the CD schedule, while CD releases are intended for customers seeking the latest features.\n * The first LTS release post 7.6 GA will be within two years. Subsequent LTS releases will occur every 12 months.\n * LTS releases will be supported for a minimum of 2 years.\n \n \n\nFirmware V7.6 and later have no extended support plan available for any release of DataPower Gateway. IBM will publish a notice of support discontinuance (end-of-service) for a LTS releases at least 12 months before the effective date.\n\nFirmware V7.5 and earlier will remain on the traditional IBM DataPower Gateway support model where they will be supported for a minimum of 2 years. There is no extended support plan available for any of these releases. IBM will publish a notice of support discontinuance (end-of-service) for releases at least 12 months before the effective date.\n\nNote: IBM DataPower Gateways customers can use the following table to track how long their version and release of a particular firmware level will be supported. By using the information in this table, customers can effectively plan their firmware investment without any gaps in support.\n\nRelease Support Model GA date End-of-service date Comment 7.7.0 \n7.7.1.0 \n7.7.1.1 \n7.7.1.2 CD 03/2018 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS218-018] \n06/08/2018 \n06/29/2018 \n07/27/2018 06/08/2018 \n06/29/2018 \n07/27/2018 \nPlanning Information 7.6.0 LTS 07/2017 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&letternum=ENUS217-265] Planning Information 7.5.0 \n7.5.1 \n7.5.2 Traditional 03/2016 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS216-024/index.html&lang=en&request_locale=en] \n06/2016 \n09/2016 04/30/2019 \n04/30/2019 \n04/30/2019 7.5.x Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS918-054/index.html&request_locale=nul] 7.2.0 Traditional 06/2015 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS215-108/index.html&lang=en&request_locale=en] 09/30/2018 7.2.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.1.0 Traditional 11/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS214-394/index.html&lang=en&request_locale=en] 09/30/2018 7.1.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS917-138/index.html&lang=en&request_locale=en] 7.0.0 Traditional 06/2014 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS214-117/index.html&lang=en&request_locale=en] 09/30/2017 7.0.0 Withdrawal Announcement [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/7/897/ENUS916-117/index.html&lang=en&request_locale=en] 6.0.2 (Common Criteria) Traditional 05/2015 6.0.1 Traditional 12/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/5/649/ENUSA13-1105/index.html&lang=en&request_locale=en] 06/19/2016 6.0.1 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 6.0.0 Traditional 06/2013 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/2/897/ENUS213-172/index.html&lang=en&request_locale=en] 06/19/2016 6.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21882726] 5.0.0 Traditional 06/2012 [http://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS112-064] 06/30/2015 5.0.0 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21677137] 4.0.2 Traditional 09/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS211-288/index.html&lang=en&request_locale=en] 11/30/2014 4.0.2 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21649637] 4.0.1 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 06/30/2014 4.0.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21642813] 4.0.0 Traditional 06/2011 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/1/897/ENUS211-141/index.html&lang=en&request_locale=en] 09/30/2013 4.0.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.2 Traditional 12/2010 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS211-284] 09/30/2013 3.8.2 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21612021] 3.8.1 Traditional 06/2010 [http://www-01.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/8/897/ENUS210-108/index.html&lang=en&request_locale=en] 12/31/2012 3.8.1 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.8.0 Traditional 11/2009 [https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS109-581] 09/30/2012 3.8.0 Withdrawal Announcement [http://www-01.ibm.com/support/docview.wss?uid=swg21511811] 3.7.3 Traditional 04/2009 12/31/2011 3.7.3 Withdrawal Announcement [http://www.ibm.com/support/docview.wss?uid=swg21457788] 1.0.0 Traditional 12/2008 12/31/2010 1.0.0 Announcement Archived 3.7.2 Traditional 12/2008 12/31/2010 3.7.2 Announcement Archived 3.7.1 Traditional 08/2008 08/31/2010 3.7.1 Announcement Archived 3.7.0 Traditional 07/2008 08/31/2010 3.7.0 Announcement Archived 3.6.1 Traditional 12/2007 12/31/2009 3.6.1 Announcement Archived 3.6.0 Traditional 10/2006 08/31/2009 3.6.0 Announcement Archived 3.5.1 Traditional 06/2006 02/28/2009 3.5.1 Announcement Archived \nNotes: \n\n * For information on current DataPower firmware versions, see Supported Firmware versions and recommended upgrade levels for IBM DataPower Gateways \".\n * Refer to the Contact Support [http://www.ibm.com/support/docview.wss?uid=swg21236322] page for how to reach IBM DataPower Gateways Support.\n * Customers are responsible for completing migration activities to currently supported levels before a release level reaches end-of-support.\n * Short duration support extensions are available on a case-by-case basis, for an additional fee, immediately following the end-of-support for a specific firmware level. Extensions would be for a very limited time period with limited terms and conditions. An extension is intended to provide support while customers complete their migration to a supported release.\n\n[https://www-prd-trops.events.ibm.com/sites/default/files/support/swg/swgtech.nsf/0/ec1cbaaf35990704852571f0006aa83d/Content/0.528A.jpg]", "question": "Upgrading to 7.7.x while using APIC v5 with DataPower? We currently have API Connect v5 with DataPower 7.2.x. Considering 7.2 is going out of support, we would like to upgrade to the most recent version(7.7) to stay up-to-date. Are there any known issues or conflicts with this setup? ", "answer": "Effective with DataPower Gateway firmware V7.6 [https://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=AN&subtype=CA&htmlfid=897/ENUS217-265&appname=USN], DataPower introduces a Continuous Delivery (CD) model to accelerate delivery of new capabilities and meet market needs. DataPower CD will consist of two releases:\n\n 1. CD release approximately once per quarter * Only the most recent CD release is supported at a given time.\n \n \n 2. Long Term Support (LTS) release every 12 months."} +{"id": "TRAIN_Q131", "document": "IBM How to override the directory location for IBM P8 Content Platform Engine (CPE) logs. - United States TECHNOTE (FAQ)\n\nQUESTION\n How to override the directory location for CPE logs. \n\nCPE logs include perflog_config.properties, p8_server_error.log, p8_server_trace.log, GCD folder, pesvr_system.log, pesvr_trace.log and pedata folders. In some instances, it will also include the INSO folder, CSSTemp folders and perf.log.\n\n\nANSWER\nAdd the system property 'user.dir' in the JVM argument to the application server.\nFor example, if you want to change the log location to 'c:\\logs'\nA. JBoss Application Server: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nB. Oracle WebLogic Server: * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nC. WebSphere Application Server: * \n * \n * \n * \n * \n * \n * \n * \n *", "question": "Is it possible to move all the P8 logs out of the default location? We are looking to move all the P8 logs out of the default FileNet folder in Websphere. The trace log can be moved easily; however, the error log and PE logs also need to be moved. ", "answer": "Add the system property 'user.dir' in the JVM argument to the application server."} +{"id": "TRAIN_Q132", "document": "IBM How to format server trace using ARSTFMT on Content Manager OnDemand 8.5.x.x and 9.0.x.x on Windows platform - United States server trace; ARSTFMT; Content Manager OnDemand TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Formatting CMOD V8.5.x.x and 9.0.x.x Server traces on Windows platform \n\nSYMPTOM\nCMOD Server trace output is unreadable\n\n\nCAUSE\nIn CMOD V8.5.0.0 and later, the trace file is written in binary. To convert the trace file from its binary format, use the ARSTFMT command found in the bin directory of your OnDemand server V8.5 and later installation.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\nOpen command prompt - navigate to the CMOD\\9.0\\bin directory and issue ARSTFMT as follows:\n\narstfmt -i C:\\Users\\IBM_ADMIN\\path\\to\\file -o C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt\n\n\n\n\nwhere the C:\\Users\\IBM_ADMIN\\path\\to\\file is the unreadable trace file and C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt is the name of the formatted trace file. \n\n \n\n\n\nRELATED INFORMATION\n Enable ODWEK tracing [http://www-01.ibm.com/support/docview.wss?uid=swg21240220]\nHow to enable trace in Content Manager OnDemand server [http://www-01.ibm.com/support/docview.wss?uid=swg21330810]", "question": "How can I format a trace for CMOD v9.0 on Windows? How can I format a CMOD trace on Windows?", "answer": "Open command prompt - navigate to the CMOD\\9.0\\bin directory and issue ARSTFMT as follows:\n\narstfmt -i C:\\Users\\IBM_ADMIN\\path\\to\\file -o C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt\n\n\n\n\nwhere the C:\\Users\\IBM_ADMIN\\path\\to\\file is the unreadable trace file and C:\\Users\\IBM_ADMIN\\path\\to\\file\\name.txt is the name of the formatted trace file."} +{"id": "TRAIN_Q134", "document": "IBM web server Plugin may need LD_LIBRARY_PATH when used with Apache 2.2 - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM web server Plug-in provides the connection between the web server tier and the IBM WebSphere Application Server (WAS) tier.\n\nWhen using Apache 2.2 web server on Linux operating systems, the IBM web server Plug-in may need to have the LD_LIBRARY_PATH environment variable set in a certain way, in order to be able to locate the IBM Global Security Kit (GSKit) libraries needed for SSL (HTTPS).\n\nWithout the GSKit libraries, the IBM web server Plug-in will be unable to initialize SSL, and will use only HTTP for connections to the WAS appservers. \n\nSYMPTOM\nDuring web server start-up, errors like the following will be logged into the Plug-in log file (http_plugin.log): \n\nERROR: lib_security: loadSecurityLibrary: Failed to load gsk library from /opt/IBM/WebSphere/Plugins/gsk8/gsk8_64\nERROR: ws_transport: transportInitializeSecurity: Unable to load security library\nERROR: ws_server: serverAddTransport: Failed to initialize security\nERROR: ws_server: serverAddTransport: HTTPS Transport is skipped\n\n\nRESOLVING THE PROBLEM\nTo resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit). \n\n \n\nFor example..... \n\nIf you installed the 32-bit Plug-in v7.0 and are using with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v7.0 and are using it with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_32/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v7.0 and are using it with a 64-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk7/gsk7_64/lib64/ \n\n \n\nIf you installed the 32-bit Plug-in v8.x and are using with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v8.x and are using it with a 32-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_32/lib/ \n\n \n\nIf you installed the 64-bit Plug-in v8.x and are using it with a 64-bit Apache 2.2, use this: \n\nexport LD_LIBRARY_PATH=/opt/IBM/WebSphere/Plugins/gsk8/gsk8_64/lib64/ \n\n \n\n \n\nPlease note that for Apache 2.2 on Linux, simply setting the LD_LIBRARY_PATH environment variable from the command line prior to starting the web server, MAY NOT WORK. In that case, you must set this variable as follows...\n\nFor SLES and SUSE Linux add the export command into the /usr/sbin/envvars file.\n\nFor RHEL Linux add the export command into the /etc/sysconfig/httpd file.\n\nBy adding the export command into the files shown above, it means that the environment variable will be set when the web server is started. That will enable the Plug-in to be able to locate the appropriate GSKit libraries and be able to initialize SSL transports. \n\n\n\nRELATED INFORMATION\n#Web server plug-in setupGSKitLibPath script contains in [http://www-01.ibm.com/support/docview.wss?uid=swg21441018]", "question": "Why Plug-in log file reports an error message after install & configure the WebSphere Plugin 8.5 version on a Apache 2.4 webserver. \n\nDuring web server start-up, errors like the following will be logged into the Plug-in log file (http_plugin.log):\n\nERROR: lib_security: loadSecurityLibrary: Failed to load gsk library from /opt/IBM/WebSphere/Plugins/gsk8/gsk8_64 ERROR: ws_transport: transportInitializeSecurity: Unable to load security library ERROR: ws_server: serverAddTransport: Failed to initialize security ERROR: ws_server: serverAddTransport: HTTPS Transport is skipped\n\nNote: This is an Apache 2.4 version on a Linux platform", "answer": "To resolve the problem, you must set the LD_LIBRARY_PATH environment variable to point to the library directory of the GSKit that comes with the IBM web server Plug-in. The precise directory location will depend of the version of Plug-in, and on the bit depth being used (32-bit or 64-bit)."} +{"id": "TRAIN_Q135", "document": "IBM NoClassDefFoundError running Java class selected from server plugin jar - United States wid; noclassdeffounderror; java; jar TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The visual snippet editor allows you to search and find methods in classes available only on a restricted basis at runtime. A runtime exception occurs when the Java™ snippet calls a method in a class found in one of the plugin JARs in the server's plugins directory. \n\nCAUSE\nSome of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code.\n\nDIAGNOSING THE PROBLEM\nA runtime exception is detected in the server log naming a class and method called from a visual snippet in the application.\n\nRESOLVING THE PROBLEM\nThe reason the method you selected in the snippet editor cannot be called in the JAR in the plugins directory is because of the architecture of the server. JARs in the plugins directory have a list that specifies what classes in the JAR can be called. This is called the exports list, and it is honored by the class loader the server uses. Classes not on the list are considered internal use only. Thus, not all classes in the server plugin JARs are available to be called by user code. \n\nYou can call any method when the JAR is in the server's library directorym because it is not being treated as a plugin and a different class loader is used, one which does not implement the exports list.\n\nThe snippet editor is not aware of this mechanism so it treats a plugin JAR the same as a regular Java JAR file. That is it allows you to select the (unavailable) class and method to call in your program. The resolution is to make sure that classes you call in plugin JARs appear on the exports list. \n\nFor example you may search for StringUtils and find the class org.apache.commons.lang.StringUtils in the WebSphere JAR plugin/com.ibm.ws.jpa.jar. This class is used internally by the plugin and it is not exported. In this case you must download the class you need directly from Apache and place the JAR in the server's classpath.", "question": "WAS runtime classpath does not match WAS Server Runtime library in RAD I've run into a classpath problem in WAS 8.0 for my web application. The problem is that it compiles fine i RAD but I get a NoClassDefFoundError in Runtime. ", "answer": "Some of the Java methods found in the JARs in the server's plugin directory are available to be called, but some of them are considered internal use only and an exception is thrown if you try to call them from user code."} +{"id": "TRAIN_Q136", "document": "IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.8-TIV-ITM_SQL-IF0001 - United States KOQ; OQ DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects listed in the \"Problems Fixed\" \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2016. \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.8\n\nComponent ID: 5724B96MO\n\nInterim Fix 0001, (6.3.1.8-TIV-ITM_SQL-IF0001)\n\nDate: March 30, 2016\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: IV79406\nAbstract: Duplicated entries of SQL Server on TADDM portal.\nAdditional Information: SQL Server instance discovered from ITM \nDLA and TADDM Sensor was not reconciling on TADDM \nand duplicates were seen. The reason for duplicates\nwas that the DLA naming rules were not matching \nwith the Sensors naming rules.\n\nAPAR: IV82234 \nAbstract: False databases are reported as Suspected.\nAdditional Information: The data collected for Database Detail is written\nin _DBD_PREV file. Due to improper file handling the \ncollector logs were written into this file which was causing collector \nlogs to be seen on the portal and triggering false alerts.\n\n2.2 DEFECTS:\n-----------------\nDEFECT: 138512\nAbstract: Improvement of table detail (KOQTBLD) algorithm.\nAdditional Information: The Table Detail information is now sorted \nbased on COLL_TBLD_SORTBY. \n\nDEFECT: 138519\nAbstract: Default instance of SQL Server is identified as 'MSSQLSERVER' \ninstead of hostname.\nAdditional Information: The default instance of SQL server used to get \nconfigured with hostname and not MSSQLSERVER. \nIn an environment, where there was default instance and \na named instance having same name as hostname had issues \nin configuration.\n\nDEFECT: 140838\nAbstract: Collector process crashes when collecting Statistics Summary\nattribute group.\nAdditional Information: There was an access violation exception as agent\nis trying to read from the memory that is already freed up.\n\n2.3 Superseded fixes\n--------------------\nNone\n\n2.4 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.8 \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.8 \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 for this version,\nrelease 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.8-TIV-ITM_SQL-IF0001.README - This is the README file\n- 6.3.1.8-TIV-ITM_SQL-IF0001.tar - Fix archive .tar format\n- 6.3.1.8-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.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.tar\n6.3.1.8-TIV-ITM_SQL-IF0001/koq_tems_teps_tepd_if0001.zip\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_winnt_tema_if0001.cab\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQ_wix64_tema_if0001.cab\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQWINNT.dsc\n6.3.1.8-TIV-ITM_SQL-IF0001/KOQWIX64.dsc\n6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd.properties\n6.3.1.8-TIV-ITM_SQL-IF0001/oq_dd_063108001.xml\n6.3.1.8-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 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.8-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 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\\6.3.1.8-TIV-ITM_SQL-IF0001, the install command is:\n\nFor 32 bit Agent:\n> \\6.3.1.8-TIV-ITM_SQL-IF0001\\itmpatch -h \n-i \\6.3.1.8-TIV-ITM_SQL-IF0001\\KOQ_winnt_tema_if0001.cab\n\nFor 64 bit Agent:\n> \\6.3.1.8-TIV-ITM_SQL-IF0001\\itmpatch -h \n-i \\6.3.1.8-TIV-ITM_SQL-IF0001\\KOQ_wix64_tema_if0001.cab\n\nNote : Use \"itmpatch\" command from \\6.3.1.8-TIV-ITM_SQL-IF0001\\ \ntemporary directory.\n\n5.3 Remote agent update\n-----------------------\n1. Transfer the appropriate archive file\n(6.3.1.8-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 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 /6.3.1.8-TIV-ITM_SQL-IF0001:\n> $CANDLEHOME/bin/tacmd addBundles -n -i /6.3.1.8-TIV-ITM_SQL-IF0001\n\nOn Windows systems,\nif the fix was expanded to \\6.3.1.8-TIV-ITM_SQL-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i \\6.3.1.8-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 \n-u \n-p \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 -v 063108001\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 -v 063108001\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 \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 Server, \nTivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file\n6.3.1.8-TIV-ITM_SQL-IF0001.tar or .zip) to the \nTivoli Enterprise Monitoring Servers, Tivoli Enterprise Portal Servers\nor 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 Server, \nTivoli Enterprise Portal Server, and Tivoli Enterprise Portal Desktop \nusing 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 ] [-j ] \n\nOn Windows systems:\n> itmasi [-h ] [-j ] \n\nwhere:\n-h - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-j - 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 [-silent] \n[-r ] \n[-j ] \n\nOn Windows systems:\n> itmasi -h [-silent] \n[-r ] \n[-j ] \n\nwhere:\n-h - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r - 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 - 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\nUnchecked - 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.08.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.8-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 [OPTIONS]\n\nitmpatch -h \n-t { | }\n\nitmpatch -h \n-i { | }\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> /bin/itmpatch -h -t \n\n- To install the fix, use the \"-i\" option:\n> /bin/itmpatch -h -i \n\nwhere:\n is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n 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 \n-u \n-p \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 \n-u \n-p \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.08.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.08.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************* Monday, March 21, 2016 6:18:11 PM *************\nUser : Administrator Group : NA\nHost Name : ESX1-SQL-T-9 Installer : Ver: 063004000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\nOQ TEMS App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.00 Build: 60071\n\nOQ TEPS App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.01 Build: 60711\n\nOQ TEPB App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.00 Build: 60071\n\nOQ TEPD App Support/Microsoft SQL Server Support\nWINNT Version: 06.31.08.01 Build: 60711\n\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.08.XX of product koq is currently installed.\nThe patch requires that you must have at least version\n06.31.08.XX of product installed to apply this patch.\nWorkaround: Use the itmpatch.exe provided in patch file \n6.3.1.8-TIV-ITM_SQL-XXXXXX.zip or \n6.3.1.8-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 process keeps on restarting.\nProblem: If the default instance is configured before patch upgrade then \nafter patch upgrade the collector process keeps on restarting \nWorkaround: In this patch, the name of default instance is changed from \nHOSTNAME to MSSQLSERVER (Defect 138519). Hence, the previously \nconfigured default instance with name as HOSTNAME will not \nwork properly. So, it is required to unconfigure default \ninstance (with name hostname) and configure it with name as \nMSSQLSERVER.\n\nFollowing are the steps to unconfigure and configure:\n1. Open Manage Tivoli Enterprise Monitoring Services \n(MTEMS) window. \n2. Right click on template row and go to \n\"Configure Using Defaults\".\n3. Select the default instance with name as HOSTNAME \nfrom 'Server To Monitor' list box and click on \">>\" button \nto unconfigure it.\n4. Select the instance with name 'MSSQLSERVER' in \n'Database Servers Available' list box and click on \"<<\" button\nto configure this instance.\n5. Set the configuration parameters and start the agent.\n\nAbstract: KOQ.SAVE registry is created for 631FP8 agent\nProblem: When a configured instance is un-configured or 631FP8 agent is \nuninstalled, the KOQ.SAVE registry is created.\nWorkaround: In case of upgrade to 6318IF1, manually delete the \nKOQ.SAVE registry. \n\n\n8.0 Additional product information\n==================================\nNone\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\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.8\n\nINSTALLATION INSTRUCTIONS\nPlease refer to the README contained in the '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] 6.3.1.8-TIV-ITM_SQL-IF0001 30-Mar-16 English 37159939 FC [http://www-933.ibm.com/support/fixcentral/swg/downloadFixes?product=ibm/Tivoli/Tivoli+Composite+Application+Manager+for+Microsoft+Applications&function=fixId&fixids=6.3.1.8-TIV-ITM_SQL-IF0001&includeRequisites=1&includeSupersedes=0&downloadMethod=http] [ ] \nPRODUCT ALIAS/SYNONYM\n SQL Agent \n\n [/support/docview.wss?uid=swg24041994&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24041994&aid=2]Problems (APARS) fixed\nIV79406, IV82234", "question": "Unexpected instance name for SQL Server agent after FP10 \n\nHello,\n\non a new server I have installed SQL Server agent 6.31 FP10 and then tried to create an instance. On the server we run a single instance of SQL Server (default instance) so I would expect it to be discovered with the server hostname as it was in the past. But the \"Configure Database Agents” pane discovers and shows one instance with name “MSSQLSERVER” instead of the machine hostname.\n\nThere are no errors in the OQ_LocalConfig.log file. Why does it happen ?", "answer": "Abstract: Default instance of SQL Server is identified as 'MSSQLSERVER' \ninstead of hostname.\nAdditional Information: The default instance of SQL server used to get \nconfigured with hostname and not MSSQLSERVER. \nIn an environment, where there was default instance and \na named instance having same name as hostname had issues \nin configuration."} +{"id": "TRAIN_Q137", "document": "IBM ERRORCODE=-4499, The application server rejected establishment of the connection. - United States -4499; JCC; SQL State = 08004; Error Code = -4; 499 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n \nAttempt to connect to a database using Type 4 JCC driver fails with the following exception:\n\njava.sql.SQLException: \n[jcc][t4][2057][11264][3.53.95] The application server rejected establishment of the connection. An attempt was made to access a database, , which was either not found or does \nnot support transactions. ERRORCODE=-4499, \nSQLSTATE=08004 DSRA0010E: SQL State = 08004, Error Code = -4,499 \n\n\n\nCAUSE\nUsing DCS DB alias or local alias name of the database in the connection string will cause this error.\n\nRESOLVING THE PROBLEM\n \n\nThe URL format for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity is:\n\n\n * \"jdbc:db2://: /\"; \n\n\nIn the Type 4 JDBC JCC driver connection string used, \n * If the connection is to a DB2 for Linux,Unix,Windows server, the database name should be the Target database name in the database server, it should not be the local alias name cataloged in the client. \n * If the connection is to a DB2 for z/OS server, database name is the DB2 location name that is defined during installation. All characters in the DB2 location name must be upper-case characters. The IBM Data Server Driver for JDBC and SQLJ does not convert lower-case characters in the database value to upper-case for IBM Data Server Driver for JDBC and SQLJ type 4 connectivity. \n * The location name can be found by executing the following SQL statement on the server: * SELECT CURRENT SERVER FROM SYSIBM.SYSDUMMY1;\n \n \n The target database name can also be found from the DCS directory on the client using the command: * db2 list dcs directory.\n \n \n\n\n\n[/support/docview.wss?uid=swg21443723&aid=1] [/support/docview.wss?uid=swg21443723&aid=1] \nFor further discussion on this topic, visit this developerWorks forum thread: \nhttps://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a [https://www.ibm.com/developerworks/community/forums/html/topic?id=1cd04237-a9dd-4061-9c38-f9043786691a] \nRELATED INFORMATION\n Type 4 JCC connection String: [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_r0052342.html]", "question": "What could cause a \"Connection refused\" to SQLDB/DB2 after some time? I have deployed an WAS Liberty/ JPA application. Everything is fine, and after a while (a day or 2), I get the connection refused exception: java.sql.SQLNonTransientException: [jcc][t4][2043][11550][4.14.103] Exception java.net.ConnectException: Error opening socket to server /XX.XXX.XXX.XXXon port 50,000 with message: Connection refused. ERRORCODE=-4499, SQLSTATE=08001 DSRA0010E: SQL State = 08001, Error Code = -4,499 \nAny idea what could cause this issue?", "answer": "Using DCS DB alias or local alias name of the database in the connection string will cause this error."} +{"id": "TRAIN_Q139", "document": "IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The MD5 “SLOTH” vulnerability on TLS 1.2 affects WebSphere Message Broker and IBM Integration Bus \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] 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:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V9, V10 \n\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\nFor users of ODBC SSL using the DataDirect drivers:\n\nYou might be vulnerable to SLOTH vulnerability, if you have not applied APAR IT09602 released in August 2015. (Please refer the bulletin at \nhttp://www.ibm.com/support/docview.wss?uid=swg21958955 [http://www.ibm.com/support/docview.wss?uid=swg21958955] for more details)\n\n\n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10 IT09602 The APAR is available in fix pack 10.0.0.2 and above. IBM Integration Bus V9 IT09602 The APAR is available in fix pack 9.0.0.5 and above. WebSphere Message Broker \n\nV8\nIT09602 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/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT09602]\n\nThe APAR is targeted to be available in fix pack 8.0.0.7. For unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \n\nYou should verify thst applying this fix does not cause any compatibility issues. The fix prevents the currently-practical SLOTH attack against the RSA-MD5 client authentication. IBM recommends that you avoid using ciphers which use an MD5 or SHA-1 signature hash. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\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] 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\nReported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \n\nCHANGE HISTORY\n 23 Jan 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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21977747]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Not Applicable AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WMB & IIB (CVE-2015-7575) I need to understand details regarding Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575). Where can I find this information? ", "answer": "CVEID: CVE-2015-7575 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7575]\nDESCRIPTION: The TLS protocol could allow weaker than expected security caused by a collision attack when using the MD5 hash function for signing a ServerKeyExchange message during a TLS handshake. An attacker could exploit this vulnerability using man-in-the-middle techniques to impersonate a TLS server and obtain credentials.\nCVSS Base Score: 7.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/109415 [https://exchange.xforce.ibmcloud.com/vulnerabilities/109415] 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:L/A:N)"} +{"id": "TRAIN_Q140", "document": "IBM .NET API error when installing IBM Content Collector (ICC) 4.0.1 - United States ICC; .NET API; CPE 5.2.1.2 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A .NET API error is thrown when attempting to install ICC 4.0.1. The error claims that either an incorrect version of the IBM FileNet P8 Content Processing Engine (CPE) .NET API 5.2.1.2 is installed or that it is missing some components. \n\nCAUSE\nA corrupt installation of the CPE 5.2.1.2.\n\nDIAGNOSING THE PROBLEM\n1. Check in \"Programs and features\"\n2. .NET API will not be listed there\n\nRESOLVING THE PROBLEM\nRe-installing the CPE 5.2.1.2 .NET API will solve this issue:\n\n\n\n\n1. Copy the software on a local disk.\n2. Start the re-installation of the .NET API.\n3. Select all sub-components of .NET framework 45 that were not listed before (select them all if unsure). \n\nDuring the next installation of ICC there are no further errors regarding missing components.", "question": "A .NET API error is thrown when attempting to install ICC 4.0.1 A .NET API error is thrown when attempting to install ICC 4.0.1. The error claims that either an incorrect version of the IBM FileNet P8 Content Processing Engine (CPE) .NET API 5.2.1.2 is installed or that it is missing some components. How do I fix this?", "answer": "Re-installing the CPE 5.2.1.2 .NET API will solve this issue:\n\n\n\n\n1. Copy the software on a local disk.\n2. Start the re-installation of the .NET API.\n3. Select all sub-components of .NET framework 45 that were not listed before (select them all if unsure). \n\nDuring the next installation of ICC there are no further errors regarding missing components."} +{"id": "TRAIN_Q141", "document": "IBM Using the \"reinitialize\" CLI command to reconfigure an appliance. - United States datapower; init; initialize; reinitialize; reinit; reset; factory settings; settings; 7993; 7993; 7993; machine type 7993 DPRecovery TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you need to reconfigure an IBM WebSphere DataPower SOA appliance you can use the \"reinitialize\" CLI command. \n\nRESOLVING THE PROBLEM\nNote: The appliance should NOT be initialized if sitation described in the technote exists - http://www-01.ibm.com/support/docview.wss?uid=swg21659259 [http://www-01.ibm.com/support/docview.wss?uid=swg21659259] - appliance gets into Fail-Safe mode. It may be necessary to return the appliance to IBM for repair.\nThe reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance.\n\nWhen the reinitialize command completes, your network IP configurations, user accounts and other configuration options, are no longer accessible. \n\nYou will only be able to connect to the appliance using the serial connection. \n\nYou will need to configure your Ethernet and all other settings again using the information in the product information center available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html].\n\nImportant points: \n\n * Make sure you have a working serial connection to the appliance. \n \n \n * The admin password will revert to the initial value of \"admin\" after the command executes.\n \n \n * A firmware image must be on the appliance prior to running the command. The firmware image used for the last upgrade of the device is removed from the file system automatically when the device reboots. Use DataPower's File Management WebGUI option to confirm you have an image or use these CLI commands:\n xi52# configure\n xi52# dir image:\n If an image file is not found, you will need to load a firmware image to the appliance into the image:/// directory. For example: you can use the WebGUI file management options or from the Control Panel, choose the System Control icon, the under Boot Image, choose the firmware file upload options.\n \n \n * Use the DataPower File Management to confirm you have sufficient file space. If you don't have sufficient file space, you can delete domains or other files to free up file space to allow the firmware image to be loaded to the appliance. \n \n \n * reinit is a CLI command available in the config-flash# mode, for example:\n \n xi52# configure terminal\n Global configuration mode \n xi52(config)# flash \n Flash configuration mode \n xi52(config-flash)#\n reinit \n \n Where represents a firmware image contained within the image:/// directory. This will be the firmware image which will be installed during the reinit process. For more CLI commands, refere to the following doc link:\n http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4 [http://pic.dhe.ibm.com/infocenter/wsdatap/v5r0m0/nav/4_4] \n \n \n * After the appliance reboots: * If the firmware image used was for V5 or newer, you will need to accept the license at first logon to the WebGui Configure the appliance per the instructions in the appliances configuration guide. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html]. \n \n \n\n\n\nThe command is documented in the information center. This and other documentation on the appliance is available from our library page [http://www.ibm.com/software/integration/datapower/library/index.html]. \n\nIf your appliance has the optional RAID (hard drives) reinitialize the RAID using the information in our RAID technote [http://www.ibm.com/support/docview.wss?uid=swg21358544]. \n\nIf your appliance has the optional HSM, reinitialize the HSM following the instructions in our HSM book or infocenter for your release of the product. These are available on our library page [http://www.ibm.com/software/integration/datapower/library/documentation/]. \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM DataPower Gateway Virtual Edition Business Integration IBM DataPower Gateways", "question": "How do I downgrade an IBM Gateway, DataPower, appliance to a lower major firmware release? I would like to know the proper, and supported, method to downgrade an appliance to prevent any issues or problems. ", "answer": "The reinit CLI command will allow you to reconfigure an IBM WebSphere DataPower SOA appliance. The reinit CLI command will allow you to delete (not erase) all existing configuration and data from an IBM WebSphere DataPower SOA appliance."} +{"id": "TRAIN_Q144", "document": "IBM Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]\nDESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Message Broker V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix WebSphere Message Broker V8 IT16698 The APAR is available in Fix Pack 8.0.0.8\nhttps://www-304.ibm.com/support/docview.wss?uid=swg24042925 [https://www-304.ibm.com/support/docview.wss?uid=swg24042925] \n\nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version/release/platform of the product. \nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\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\nCHANGE HISTORY\n 1 Dec 2016 - 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.\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin: The WebAdmin context for WMB V8 allows directory listings (CVE-2016-6080) \n\nI need to understand details regarding Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080). Where can I find this information?\n 0", "answer": "CVEID: CVE-2016-6080 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-6080]\nDESCRIPTION: The WebAdmin context for WebSphere Message Broker allows directory listings, which could disclose sensitive information to the attacker.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/117560 [https://exchange.xforce.ibmcloud.com/vulnerabilities/117560] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)"} +{"id": "TRAIN_Q145", "document": "IBM Generating Java diagnostic dumps for IBM Integration Bus - United States mqiinfo; java dumps; java core; core; force TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Use the procedures below to collect java diagnostics dumps from IBM Integration Bus (IIB).\n\nJava diagnostic dumps contain:\n- all Java threads running in a process (Java core or javacore files)\n- objects populating the heap space (Heap dump or heapdump files)\n- tracepoint information (Snap trace or snaptrace files)\n- internal system information (System dump)\n\nThese files can be used to diagnose problems such as lock conditions, loops, or memory allocation in Java code. \n\nGathering this information before calling IBM Support will help familiarize you with the troubleshooting process and save you time. \n\nRESOLVING THE PROBLEM\n\n\nJAVACORE DUMP INSTRUCTIONS\n\nNew javacore dump commands have been made available from IIB v10.0.0.9, onwards. \n- The new procedure uses the mqsichangeproperties command. \n- The old procedure uses a custom message flow, and is only applicable for operating systems that use the IBM JRE. \n\nNote: \nCollection of Java core dumps is an invasive activity and will impact the performance of the Integration Server process. \n\nJAVA DUMP COMMAND FOR IIB V10.0.0.9+\nUse this command to generate a Java dump on IIB v10.0.0.9+:\nmqsichangeproperties -e -o ComIbmInternalSupportManager/Java/JVM -n dump -v \n\nThe following dump types are supported:\n\nAll Platforms \n\n-v heap Produces a Java Heap dump \n\nIBM JRE Platforms (All platforms except HP and Solaris) -v core Produces a javacore -v system Produces a system dump -v all Produces a heapdump, javacore, and system dump \nDump files are output to $MQSI_WORKPATH/common/errors \n\nJAVA DUMP PROCEDURE FOR IIB PRIOR TO V10.0.0.9\nUse this procedure to create an IIB message flow that will trigger a Java dump for an Integration Server:\n\n1. Create a new message flow containing an Input node and a JavaCompute node.\n2. In the JavaCompute node, call the method 'com.ibm.jvm.Dump.JavaDump()'.\n3. Deploy your message flow to the target Integration Server.\n4. Recreate the conditions that necessitate the Java dump.\n5. Invoke your message flow by sending a message to the Input node.\n6. The dump files should be output to $MQSI_WORKPATH/common/errors.\n\nNote:\nThis procedure requires the use of the IBM JRE.\nTherefore, it is not suitable on Solaris or HP platforms which do not use the IBM JRE.\n\n\n\n\n\nRELATED INFORMATION\n Triggering a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.win.70.doc/diag/tools/javadump_trigger.html]\nEnabling a java dump [http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.lnx.70.doc/diag/tools/javadump_enable.html]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n WMB MB WebSphere Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI IIB", "question": "How can I obtain a Java thread dump against an execution group in IIB v10? \n\nThis Q&A is abstracted from a PMR\n\nHow can I obtain a Java thread dump against an execution group in IIB v10?\n", "answer": "Use this command to generate a Java dump on IIB v10.0.0.9+:\nmqsichangeproperties -e -o ComIbmInternalSupportManager/Java/JVM -n dump -v "} +{"id": "TRAIN_Q150", "document": "IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States 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", "question": "Error: \"MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION\" occurs at portal startup \n\nWe are using Portal Server 8.5 and when starting the Portal server we see following error:\n\n0000005e MBeanStarter E com.ibm.wps.scripting.server.MBeanStarter loadExtensions failed to load extension: key: ServerExt.applications / value: com.ibm.wps.scripting.server.ApplicationServerExtensions\n\nHow can we resolve this error without installing a fix?", "answer": "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."} +{"id": "TRAIN_Q151", "document": "IBM How to Proxy SSL request from DataPower to Remote Proxy Server? - United States Forward Proxy XMLFW MPGW CONNECT TUNNEL TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to configure an IBM WebSphere DataPower SOA Appliance Service to proxy an SSL request to a remote proxy server using the CONNECT method for SSL tunneling? \n\nCAUSE\nMany common forward proxy servers expect requests in different formats depending on if they are proxying non-SSL or SSL requests.\n\nFor example, a non-SSL request to be proxied may come in the form of GET hostname:port/URI.\n\nFor SSL requests to be proxied, remote proxy servers are commonly configured to tunnel the request from the client to the backend server.\n\nIn the SSL request scenario, remote proxy servers will typically expect a CONNECT request and then tunnel the SSL request from the client to the backend server.\n\nUsers configuring DataPower may need a way to implement this CONNECT method for SSL tunneling to a remote Proxy Server.\n\n\n\n\nRESOLVING THE PROBLEM\nNon-SSL Proxy requests will work using either:\n\na) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port\n\nb) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent\n\nSSL Proxy requests will work using the CONNECT method for SSL Tunneling when using a Multi-Protocol Gateway when configuring in a User Agent's HTTP Proxy Policy.\n\nThe XML Firewall service is not designed to use the CONNECT method for SSL Tunneling.", "question": "Does IBM DataPower Gateway Appliance support the HTTP CONNECT method? Does IBM DataPower Gateway Appliance support the HTTP CONNECT method for non-SSL proxy requests? ", "answer": "Non-SSL Proxy requests will work using either:\n\na) an XML Firewall when configuring in the HTTP Options tab, where the user can configure the Proxy Host and Port\n\nb) a Multi-Protocol Gateway when configuring an HTTP Proxy Policy in the User Agent"} +{"id": "TRAIN_Q152", "document": "IBM EIF probe not receiving itm events - United States om_tec.conf eif probe itm event clearing omnibus TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n ITM is sending events to EIF probe which is then forwarded to the OMNIbus Server. Client is observing that the clearing event is sent per the ITM trace/log but the event does not seem to be received into EIF or OMNIbus as the triggered event is still seen in OMNIbus.\n\n\n\nSYMPTOM\nSituation in ITM is no longer true but event is not cleared in OMNIbus.\n\n\nDIAGNOSING THE PROBLEM\nThe iptrace shows that the EIF probe on the OMNIbus side is resetting/closing() the TCP/IP connection after it receives the event and it never shows up in the EIF logs, so the event is just dropped.\n\nRESOLVING THE PROBLEM\nThe solution is to set the connection_mode in your om_tec.config on the ITM Server (TEMS) to use \n\n\nconnection_less \n\ninstead of \n\nconnection oriented.\n\nThat is, change this line in your om_tec.config\n\nConnectionMode=co\nto\nConnectionMode=connection_less\n\nYou will need to restart the EIF on your ITM. (tacmd refreshTECinfo -t eif)", "question": "EIF probe not receiving itm events Why is the event in the netcool isn't cleaned ? ", "answer": "The solution is to set the connection_mode in your om_tec.config on the ITM Server (TEMS) to use \n\n\nconnection_less \n\ninstead of \n\nconnection oriented."} +{"id": "TRAIN_Q154", "document": "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13) \n\nSupport for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \n\nNOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version). \nThe top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English. \nThe official MacOSX 10.13.1 version do not have this issue. So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple. \n\n \n\nB) Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra. \n\n \n\nC) Apple Macintosh OSX El Capitan (10.11) \n\nSupport for IBM SPSS Statistics 24. Please see the Release notes - IBM SPSS Statistics 24.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27047057] for known issues on Macintosh. \n\nFull documentation including installation material provided in different languages and manuals for release 24 can be found on IBM SPSS Statistics 24 Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg27047033] webpage. \n\n \n\nAlso, Support for IBM SPSS Statistics 23. Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391] \n\n \n\nD) Apple Macintosh OSX Yosemite (10.10) \n\nSupport for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n \n\nNote: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released. If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well. Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10. So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: \n\n**** \n\nIn some instances it can be necessary to re-install the legacy Apple Java 6 on 10.10 for the use of Statistics 22 FixPack 2 on this platform\n\nDownload and re-install Apple Java 6 \n\n- After you upgraded your Apple Mac OSX from a previous release to 10.10, Apple Java 6 may no longer exists on your upgraded system. If you then launch Statistics 22 which is an application that relies on Java 6, it can happen, the Mac OS pops up a dialog box stating Java 6 was requested, but none is present.\n- The Java dialog has a \"More Info\" button, which when clicked opens a browser to an Apple Tech Support page for Apple Java 2014-001. A download link is provided:\nhttp://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]\n- Click on the download link and a DMG containing the Java 6 installer is downloaded.\n- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6.\n\n******* \n\n \n\nE) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n*** \n\nNote: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22. Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. \n\n**** \n\nF) Apple Macintosh OSX Mountain Lion (10.8) \n\nSupport for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 \n\n**** \n\nG) Apple Macintosh OSX Lion (10.7) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nH) Apple Macintosh OSX Snow Leopard (10.6) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nOlder SPSS Statistics releases 18 and 19 and 20: \n\nPlease note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM. Please contact IBM Sales department to renew your contracts.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]", "question": "IBM SPSS Statistics Subscription Installer not supported on Mac OS version OS X 10.9.5 Attempted several times to install IBM SPSS statistics subscription installer. Followed online instructions to double click the blue and white statisticsSub_Installer and click open. The result a message installer not supported OS version. Attempted to turn off fire wall and install without success. Suggestions? ", "answer": "IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22."} +{"id": "TRAIN_Q155", "document": "IBM Case insensitive searches in IBM Content Navigator - United States ICN case sensitive TECHNOTE (FAQ)\n\nQUESTION\n How can a search field be enabled as case insensitive in IBM Content Navigator (ICN)? \n\nANSWER\nICN does not provide a feature to turn on or off case sensitive searches. All metadata searches in ICN are case sensitive by default. However, depending on the repository, case insensitive searches can be performed by doing the following:\n- For FileNet P8 repositories; set the Force Case Insensitive Search flag on the object store. \n- For Content Manager repositories; the administrator will firstly need to enable text search on metadata, then a text search will need to be done in ICN against the metadata by enclosing the metadata value in double quotes.\n\nAlternatively, a request filter can be written to change the case of a query to all upper or all lower case.", "question": "Is it possible to make where filter to case insensitive in My Inbox? Workplace OOTB feature - 'Tasks-->My Inbox--> Filter inbox based on field where' the filter is case sensitive. but our expected result is case insensitive. We have already checked 'Force case-insensitive search'. Our expectation it should return the same work items what ever we use 'TEST' or 'test'. ", "answer": "ICN does not provide a feature to turn on or off case sensitive searches. All metadata searches in ICN are case sensitive by default. However, depending on the repository, case insensitive searches can be performed by doing the following:\n- For FileNet P8 repositories; set the Force Case Insensitive Search flag on the object store. \n- For Content Manager repositories; the administrator will firstly need to enable text search on metadata, then a text search will need to be done in ICN against the metadata by enclosing the metadata value in double quotes.\n\nAlternatively, a request filter can be written to change the case of a query to all upper or all lower case."} +{"id": "TRAIN_Q158", "document": "IBM FileNet Workplace XT war and ear files are unusually small - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When creating the IBM FileNet Workplace XT archive files with either the Content Platform Engine Client Files installation or the IBM Case Manager's \"Deploy IBM FileNet Workplace XT\" configuration manager task , the resulting war and ear files are only a few kilobytes in size and contain the create_web_client_war.sh and create_web_client_ear.sh files.\n\n\n\nDIAGNOSING THE PROBLEM\nThe ceclient_install_log or warerr.log file will contain the following error:\n\nERROR:\n\"create_web_client_war.sh[5]: cd: .WorkplaceXT: [No such file or\ndirectory]\"\n\nWhen attempting to install the resulting archive file to IBM WebSphere Application Server, the following error is returned.\n\nIWAE0006E Archive is not a valid WAR File because the deployment descriptor can not be found (case sensitive): WEB-INF/web.xml \n\nRESOLVING THE PROBLEM\nThe create_web_client_war.sh script that creates the web_client.war file contains a change directory (CD) operating system command so the WorkplaceXT directory will be included in the archive. This CD command fails with a \"No such file or directory\" error. \n\nThis failure can be caused by the CDPATH operating system environment variable being set. The CDPATH environment variable is used to define the base directory to be used for the CD command. A side effect of setting the CDPATH is that CD commands in scripts may jump to unintended directories. \n\n \n\nFor example, the error below indicates that the operating system cannot find the WorkplaceXT directory off the root of the file system instead of the expected \"/IBM/FileNet/webclient/\" directory. \n\n \n\nERROR:\n\"create_web_client_war.sh[5]: cd: .WorkplaceXT: [No such file or\ndirectory] \n\n \n\nTo resolve this problem, unset the CDPATH operating system environment variable while creating the IBM FileNet Workplace XT war and ear files.", "question": "Why are my IBM FileNet Workplace XT war and ear files are unusually small? When creating the IBM FileNet Workplace XT archive files with either the Content Platform Engine Client Files installation or the IBM Case Manager's \"Deploy IBM FileNet Workplace XT\" configuration manager task , the resulting war and ear files are only a few kilobytes in size and contain the create_web_client_war.sh and create_web_client_ear.sh files. ", "answer": "This failure can be caused by the CDPATH operating system environment variable being set. The CDPATH environment variable is used to define the base directory to be used for the CD command. A side effect of setting the CDPATH is that CD commands in scripts may jump to unintended directories."} +{"id": "TRAIN_Q159", "document": "IBM The version of the IBM Content Search Services client embedded in the IBM FileNet Content Platform Engine is not compatible with the IBM FileNet Content Search Services server. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The version of the IBM FileNet Content Search Services client included in the IBM FileNet Content Platform Engine is not compatible with the IBM Content Search Services server. \n\nDIAGNOSING THE PROBLEM\nThe p8_server_error.log file from the IBM FileNet Content Platform Engine will have an error similar to the following:\n2017-03-22T13:13:07.102 1BCC84C0 CBR FNRCB0036W - WARN A problem\noccurred during a search using TextSearchServer\nId={B4FDE211-BE1A-44A1-B0CA-E50A75E4283A};\ndisplayName= xxxxxxxxx on attempt 1 of 1. An alternate text\nsearch server will be\ntried.\\ncom.filenet.api.exception.EngineRuntimeException: FNRCB0036E:\nCBR_TS_ACCESSING_TEXT_SEARCH_SERVER_FAILED: IBM Content Search Services\ncould not communicate with the server that runs on the\nxxxxxxxx:8191 host and port. The server is not\nstarted. Start the server. For information about starting the server,\nsee \"Starting or stopping IBM Content Search Services servers\" in the\nIBM FileNet P8 information center.\\n at\ncom.ibm.filenet.cse.cascade.CSECascadeBase.getTSS(CSECascadeBase.java:71\n)\\n at\n...\ncaused by\n...\nIQQG0205E The client [version: 5.2.0.2] is not compatible with the\nserver [version: 2.1.0.0-1.1-4140.FP4]. The client supports server\nversions [[5.2.0.2]]. The server supports client versions [[1.0.0.0,\n1.5.0.0, 1.5.0.1, 2.0.0.0, 2.1.0.0]].\n\n\nRESOLVING THE PROBLEM\nThe version of the IBM FileNet Content Search Services client files that are included in the IBM FileNet Content Platform Engine must match the version IBM FileNet Content Search Services server. Please check the readme files for your installed IBM FileNet Content Platform Engine and IBM FileNet Content Search Services fix packs as they will include fix pack requirements. \n\n \n\nFor example IBM Content Search Services 5.2.1.5 fix pack reports the following requirements. \n\n\nPrerequisites \n\nThis fix pack requires: \n\n * 5.2.1.0-P8CSS or any of the following\n 5.2.1.0-P8CSS-IF001 or 5.2.1.0-P8CSS-IF002 or 5.2.1.2-P8CSS-FP002 or 5.2.1.2-P8CSS-IF001 or 5.2.1.3-P8CSS-FP003 or 5.2.1.3-P8CSS-IF001 \n * 5.2.1.5-P8CPE-FP005", "question": "Why can't IBM FileNet Content Platform Engine successfully connect to IBM FileNet Content Search Services? \n\nWhy can't IBM FileNet Content Platform Engine successfully connect to IBM FileNet Content Search Services? I see the following error in my p8_server_error.log.\n\nIQQG0205E The client [version: 5.2.0.2] is not compatible with the server [version: 2.1.0.0-1.1-4140.FP4].", "answer": "The version of the IBM FileNet Content Search Services client files that are included in the IBM FileNet Content Platform Engine must match the version IBM FileNet Content Search Services server. Please check the readme files for your installed IBM FileNet Content Platform Engine and IBM FileNet Content Search Services fix packs as they will include fix pack requirements."} +{"id": "TRAIN_Q160", "document": "IBM PI19804: SQLCODE401 FROM DSNXOBFC FOR A SQL PROCEDURE WHEN USING INLIST IN IF STATEMENT - United States z/os A FIX IS AVAILABLE\nObtain the fix for this APAR.\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 * Sqlcode401 from dsnxobfc for a sql procedure when using inlist\n in if statement\n error will be received when coding something like this\n p1: begin\n decalre ws_types char(2) default 'SN';\n declare ws_typew char(2) default 'WS';\n \n if invar in (ws_types, ws_typew) then\n set outvar = 0;\n end if;\n \n Additional symptoms and search keywords\n SQLIN, SQLCODE401, SQLPROCEDURE, SQLSP, SQLSTOREDPROC\n \n \n \n \n \n\nLOCAL FIX\n * N/A\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All DB2 11 for z/OS users of a compiled SQL *\n * scalar function or native SQL procedure *\n * containing control statement with IN-LIST *\n * predicate which references SQL variables. *\n ****************************************************************\n * PROBLEM DESCRIPTION: SQLCODE -401 or unexpected ABEND0C4 *\n * or ABEND04E may occur for a CREATE *\n * PROCEDURE/FUNCTION statement that *\n * contains control statement with an *\n * IN-LIST predicate which references SQL *\n * variables. *\n * *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n The following examples help to illustrate the problem.\n \n Example#1. statement which issued SQLCODE -401 incorrectly.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN\n DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF PCTYPE IN (WC_CTYPE_PGMS, WC_CTYPE_PGMD) THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n Example#2. statement which issued ABEND0C4.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN\n DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF (CASE\n WHEN PCTYPE IN ('PGMS', 'PGMM', WC_CTYPE_PGMD, 'PGNN')\n THEN 'PGMM'\n ELSE 'PGMN'\n END\n ) = 'PGMM' THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n Example#3. statement which issued ABEND04E.\n CREATE PROCEDURE SYSADM.CTEST(\n IN PCTYPE CHAR(4),\n OUT PRC INTEGER)\n LANGUAGE SQL\n DETERMINISTIC\n MODIFIES SQL DATA\n DYNAMIC RESULT SETS 1\n DISABLE DEBUG MODE\n PTEST: BEGIN\n DECLARE WC_CTYPE_PGMS CHAR(4) DEFAULT 'PGMS';\n DECLARE WC_CTYPE_PGMD CHAR(4) DEFAULT 'PGMD';\n IF PCTYPE IN ('PGMS', 'PGMN', WC_CTYPE_PGMD, 'PGMG') THEN\n SET PRC = 0;\n END IF;\n RETURN;\n END PTEST?\n \n DB2 does not process the SQL variables in the IN-LIST predicate\n properly which can result in the incorrect SQLCODE or unexpected\n ABEND.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * DB2 has been modified correctly to process SQL variables in the\n IN-LIST predicate to avoid the problem.\n \n Additional keywords: SQLCODE401 SQLIN SQLCREATE SQLSP\n SQLSTOREDPROC SQLNATIVESQLPL SQLUDF\n SQLPROCEDURE\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI19804\n \n \n * REPORTED COMPONENT NAME\n DB2 OS/390 & Z/\n \n \n * REPORTED COMPONENT ID\n 5740XYR00\n \n \n * REPORTED RELEASE\n B10\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 2014-06-12\n \n \n * CLOSED DATE\n 2014-08-18\n \n \n * LAST MODIFIED DATE\n 2014-10-02\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 UI20622\n \n \n\nMODULES/MACROS\n * DSNXOP0\n \n \n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n DB2 OS/390 & Z/\n \n \n * FIXED COMPONENT ID\n 5740XYR00\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * RB10 PSY UI20622 [HTTPS://WWW14.SOFTWARE.IBM.COM/WEBAPP/SET2/ORDERMEDIA/SHOPCART?PTFS=UI20622]\n UP14/09/03 P F409\n \n \n\nFIX IS AVAILABLE\n * SELECT THE PTF APPROPRIATE FOR YOUR COMPONENT LEVEL. YOU WILL BE REQUIRED TO SIGN IN. DISTRIBUTION ON PHYSICAL MEDIA IS NOT AVAILABLE IN ALL COUNTRIES.", "question": "DSNT408I SQLCODE -401 creating stored procedure CIUSNTSR after upgrading to DB2 11 \n\nWhy would CIUSNTSR stored procedure creation fail with message DSNT408I and SQLCODE=-401? I am running CICS Interdependency Analyzer for z/OS (CICS IA) CIUDBCQ JCL when the failure occurs. This happened after I upgraded z/OS DB2 to V11.\n\nHere are the messages I receive:\n\n DSNT408I SQLCODE = -401, ERROR: THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE\n NOT COMPARABLE\n DSNT418I SQLSTATE = 42818 SQLSTATE RETURN CODE\n DSNT415I SQLERRP = DSNXOBFC SQL PROCEDURE DETECTING ERROR\n DSNT416I SQLERRD = 930 0 1 -1 0 0 SQL DIAGNOSTIC INFORMATION\n DSNT416I SQLERRD = X'000003A2' X'00000000' X'00000001' X'FFFFFFFF' X'00000000' X'00000000'\n SQL DIAGNOSTIC INFORMATION\n", "answer": "DB2 has been modified correctly to process SQL variables in the\n IN-LIST predicate to avoid the problem."} +{"id": "TRAIN_Q161", "document": "IBM MQJMS1068 error occurs when trying to create an XA connection from WebSphere Application Server to MQ - United States MQPRB MQPRB3189 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to create an XA connection to WebSphere® MQ from either WebSphere Application Server Version 7.x or Version 8.x with a connection factory that uses the Client Channel Definition Table (CCDT), the following error appears in the application server's SystemOut.log file: \n\n J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource . The exception which was received is javax.jms.JMSException: MQJMS1068: failed to obtain XAResource \n\n\n\nCAUSE\nThe reason why it is not possible to use the CCDT with XA connections is related to transaction recovery. \n\n If the application server stops while there are still active transactions, there is no way with the current implementation to ensure that it will connect to the same queue manager when it restarts. This can lead to in-doubt transactions being left dangling, and never resolved. \n\n It is hoped that this restriction will be resolved in future releases of WebSphere Application Server and WebSphere MQ.\n\nRESOLVING THE PROBLEM\nThe use of the Client Channel Definition Table (CCDT) with XA connections is not supported.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Java Message Service (JMS) Application Servers Runtimes for Java Technology Java SDK \nPRODUCT ALIAS/SYNONYM\n WMQ WASAS WAS", "question": "Problems making XA connection from WMQ to WAS using a CCDT \n\nWe have applications hosted on WAS 7.0.0.27. We have two hubs in Websphere MQ end. Hub1 queue manager and Hub2 queue manager.\n\nWe have 3 QCF's configured at WAS end as mentioned below\n\n jms/QM using a CCDT file pointing to a queue manager group.\n\n jms/QM01 using a direct connection to hub1 queue manager\n\n jms/QM02 using a direct connection to hub2 queue manager\n\nWe have 2 separate sync mdb listeners that connect using QCFs jms/QM01 and jms/QM02. We are using QCF jms/QM to put messages in MQ.\n\nWhile processing sync messages out listeners are going down.\n\nPlease advise.", "answer": "The use of the Client Channel Definition Table (CCDT) with XA connections is not supported."} +{"id": "TRAIN_Q162", "document": "IBM PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) - United States PI50993; PI50993; PI50993 DOWNLOADABLE FILES\n\nABSTRACT\n Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) \n\nDOWNLOAD DESCRIPTION\nPI50993 resolves the following problem:\n\nERROR DESCRIPTION:\nApache HTTPComponents vulnerabilities in WebSphere Application Server \nLOCAL FIX: \n\nPROBLEM SUMMARY:\nApache HTTPComponents vulnerabilities in WebSphere Application Server\n\nPROBLEM CONCLUSION:\nApache HTTPComponents vulnerabilities in WebSphere Application Server \n\nPREREQUISITES\nNone\n\nINSTALLATION INSTRUCTIONS\nPlease review the readme.txt for detailed installation instructions.\n\nURL LANGUAGE SIZE(Bytes) Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI50993/8.0.0.11/readme.txt] US English 2260 Readme [ftp://public.dhe.ibm.com/software/websphere/appserv/support/fixes/PI50993/8.5.5.7/readme.txt] US English 2296 \nDOWNLOAD PACKAGE\n\n\nKNOWN SIDE EFFECTS\nThere would be NoClassDefFoundError observed after applying the fix because the API in HTTPCore and HTTPClient libraries are no long visible to application. To resolve this error, application may need to be updated with HTTPCore and HTTPClient libraries bundled.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https://www.ibm.com/support/fixcentral/help?page=swfaqs] 8.5.5.6-WS-WASProd-IFPI50993 12-03-2015 US English 254093 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.5.5.6-WS-WASProd-IFPI50993&productid=WebSphere%20Application%20Server&brandid=5] 8.0.0.10-WS-WASProd-IFPI50993 12-03-2015 US English 253242 HTTP [http://www-933.ibm.com/eserver/support/fixes/fixcentral/swgquickorder?fixes=8.0.0.10-WS-WASProd-IFPI50993&productid=WebSphere%20Application%20Server&brandid=5] \nTECHNICAL SUPPORT\n Contact IBM Support using SR (http://www.ibm.com/software/support/probsub.html [http://www.ibm.com/software/support/probsub.html]), visit the WebSphere Application Server support web site (http://www.ibm.com/software/webservers/appserv/was/support/ [http://www.ibm.com/software/webservers/appserv/was/support/]), or contact 1-800-IBM-SERV (U.S. only). \n\n [/support/docview.wss?uid=swg24041394&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24041394&aid=2]Problems (APARS) fixed\nPI50993", "question": "Crash happened due to \"PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577)\" \n\nDetails of gpf crash events: A VerifyError was thrown due to \"Inaccessible class\" at offset 39(0x27) of the method executeInternal(Lorg/springframework/http/HttpHeaders;[B)Lorg/springfram ework/http/client/ClientHttpResponse of the above class org/springframework/http/client/HttpComponentsClientHttpRequest.\n\nLooking at method the bytecodes :\n\n31 invokespecial 15 org/apache/http/entity/ByteArrayEntity.([B)V 34 astore 4 36 aload3 37 aload 4 39 invokeinterface2 41 invokeinterface 16 org/apache/http/HttpEntityEnclosingRequest.setEntity(Lorg/apache/http/Ht tpEntity;)V\n\nThe above sequence of bytecodes indicates it created an instance of org/apache/http/entity/ByteArrayEntity, trying to cast it to type Lorg/apache/http/HttpEntity; which in turns led to the \"Inaccessible class\" VerifyError message.\n\nIt is clear that class org/apache/http/HttpEntity was not loaded at all:\n\n allclasses | grep org/apache/http/HttpEntity\n", "answer": "There would be NoClassDefFoundError observed after applying the fix because the API in HTTPCore and HTTPClient libraries are no long visible to application. To resolve this error, application may need to be updated with HTTPCore and HTTPClient libraries bundled."} +{"id": "TRAIN_Q163", "document": "IBM Content Navigator is not affected by the Apache Struts 2.x Vulnerability (CVE-2017-5638) - United States FLASH (ALERT)\n\nABSTRACT\n IBM Content Navigator is not vulnerable to the Apache Struts 2.x Vulnerability. \n\nCONTENT\nIBM Content Navigator in all editions and all platforms is NOT vulnerable to Apache Struts 2.x Vulnerability (CVE-2017-5638). \nIBM recommends that you review your entire environment and take appropriate mitigation and remediation action.\n\nChange History: March 17, 2017: original version published", "question": "Whether IBM Case Manager is using Apache Struts? Whether IBM Case Manager is using Apache Struts?", "answer": "IBM Content Navigator is not vulnerable to the Apache Struts 2.x Vulnerability."} +{"id": "TRAIN_Q165", "document": "IBM Learning more about EJBDeploy - United States EJB; EJBDeploy TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Learning more about EJBDeploy is the first step in the troubleshooting process. This document provides you with educational information that can help you learn more about this topic. \n\nRESOLVING THE PROBLEM\n \n\nTAB NAVIGATION\n * Learning more [http://www.ibm.com/support/docview.wss?uid=swg21994741]- selected tab,\n * Troubleshooting [http://www.ibm.com/support/docview.wss?uid=swg21994742]\n * Collect data [http://www.ibm.com/support/docview.wss?uid=swg21260603]\n\nGetting background information on EJBDeploy \n\n All Java Enterprise Edition (Java EE ) EJB applications go through an EJB deployment phase in which your application is customized to run in an application server. Typically, this is accomplished by a deployment tool that is specific to the application server. It generates code to allow your EJB to run within an EJB container. Some application server products' deployment tools alter the bytecode of your application classes rather than generating code ;however, the end result is similar. \n\nThe EJBDeploy Tool \n\nHistorically, EJB deployment in the Application Server product has been performed by the EJBDeploy tool, which is included with WebSphere® Application Server and packaged with the development tools for the WebSphere products. \nThe EJBDeploy tool inspects the external interfaces for your enterprise beans, generates wrapper code as .java files, and compiles the code using the javac compiler. The resulting .class files are packaged in your EJB module with your application code. For modules including and previous to EJB 2.1, the EJBDeploy tool must be invoked manually. \nPlease note that in WebSphere Application Server 8.5.5.x and below, the tool can only deploy Java EE applications compiled with a JDK level of 7 or below. To deploy JDK 8 compiled web applications, please upgrade to WebSphere Application Server V9.", "question": "Is Java 8 supported for EJBDeploy on WebSphere Application Server 8.5.5.9 or later? Is Java 8 supported for EJBDeploy on WebSphere Application Server 8.5.5.9 or later?", "answer": "Please note that in WebSphere Application Server 8.5.5.x and below, the tool can only deploy Java EE applications compiled with a JDK level of 7 or below. To deploy JDK 8 compiled web applications, please upgrade to WebSphere Application Server V9."} +{"id": "TRAIN_Q166", "document": "IBM MustGather: Sessions and session management problems in WebSphere Application Server - United States MustGather; MustGather; MustGather; httpsession; session; session manager; isa; collector; autopd; auto pd; MustGatherDocument TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with the IBM WebSphere Application Server sessions and session management component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data. \n\nRESOLVING THE PROBLEM\n\n\nCollecting data for problems with the IBM WebSphere Application Server sessions and session management component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data.\n\nTo improve the accuracy of complete data collection, IBM recommends you use the automated data collectors within IBM Support Assistant. Not only will the automated collector gather the equivalent of the manual process, it will also provide a secure file transfer of the collection to IBM.\n\nCOLLECTING DATA USING THE IBM SUPPORT ASSISTANT DATA COLLECTOR\n 1. \n 2. WebSphere Application Server V8.0.0.6\n 3. \n 4. (ISADC)\n 5. \n 6. ISADC\n 7. \n 8. Using the IBM Support Assistant Data Collector.\n 9. \n 10. \n 11. \n 12. Using the ISA Data Collector: * To run ISADC from command line, go to your app_server_root/bin directory and run isadc.[sh|bat]\n \n \n * To download, install and run ISADC locally:\n > Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server. [http://public.dhe.ibm.com/software/isa/isadc/?taxonomy=ApplicationServer] \n \n > > Select the option to collect from this or another system using a downloadable utility. Download and extract the zip file to your WAS_HOME directory. From a command line, run isadc.[sh|bat] or launch index.html to use the web interface.\n \n \n \n \n \n \n 13. To download and run ISADC in your browser: \n > Obtain the IBM Support Assistant Data collector online ISA Data Collector site for WebSphere Application Server. [http://public.dhe.ibm.com/software/isa/isadc/?taxonomy=ApplicationServer] \n \n > Select the option to collect from this system using the current browser and click Start Collection.\n \n \n \n 14. Select the Runtime > Session Management Problem collector and click Start.\n \n \n 15. Follow the prompts to automatically submit the collected data to IBM Support.\n\nCOLLECTING DATA MANUALLY\n \nSessions and Session Management specific MustGather information:\nThe first step in solving a problem with your HTTPSession in Application Server is to reproduce the problem with session tracing enabled. Adding debug code to the application simplifies the task of identifying the problem.\n\nInstructions for setting up the trace: \n\n 1. In the WebSphere Application Server administrative console, expand the Troubleshooting section and click Logs and Trace.\n \n \n 2. Click the link for your server.\n \n \n 3. Click Diagnostic Trace.\n \n \n 4. Make sure Enable Log is checked, Maximum File Size is 100MB, Historical Files is 10, and specify a File Name. You may have to select different values for Maximum File Size and Historical Files as per the frequency of the problem or as suggested by support team.\n \n \n 5. Click OK.\n \n \n 6. Click on Change Log Level Details.\n \n \n 7. In the text box for Trace Specification, enter the following string (type without spaces) depending on the method that you persist session data: * Trace strings for V7.0 and V8.0 releases * If you do not use any persistence:\n com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all\n \n \n * If you use database persistence:\n com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all:WAS.j2c=all:RRA=all\n \n \n * If you use memory-to-memory persistence:\n com.ibm.ws.session.*=all:com.ibm.ws.webcontainer.srt.*=all:com.ibm.ws.drs.*=all\n \n \n \n \n * Trace strings for V6.0 and V6.1 releases * If you do not use any persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all\n \n \n * If you use database persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all:WAS.j2c=all:RRA=all\n \n \n * If you use memory-to-memory persistence:\n com.ibm.ws.webcontainer.httpsession.*=all:com.ibm.ws.webcontainer.srt.*=all:com.ibm.ws.drs.*=all\n \n \n \n \n \n \n 8. Click apply and save your configuration.\n \n \n 9. Stop the Application Server.\n \n \n 10. Enable a plug-in trace by changing the LogLevel attribute from Error to Trace in the plugin-cfg.xml file. This file is located in the following directory:\n \n install_root/profiles/profile_name/config/cells/cell_name/nodes/\n web_server_node_name/servers/server_name\n \n \n For more information on capturing plug-in trace, refer MustGather document for plug-in [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21174894].\n \n 11. Stop the Web server.\n \n \n 12. Clear all logs for the Application Server: * trace.log \n * SystemOut.log \n * SystemErr.log\n \n \n \n \n 13. Start the Application Server.\n \n \n 14. Start the Web server.\n \n \n 15. Reproduce your problem. \n \n \n 16. Capture the cookie information from the browser by typing the following text in the address bar:\n javascript:document.cookie\n \n \n 17. Collect the following: * Trace file from the diagnostic trace.\n \n * All files in the following directory:\n install_root/profiles/profile_name/logs/server_name\n \n \n * All files in the following directory:\n install_root/profiles/profile_name/logs/ffdc\n \n \n * The server.xml file located in the following directory:\n install_root/profiles/profile_name/config/cells/cell_name/nodes/\n node_name/servers/server_name\n \n \n * The http_plugin.log file.\n \n \n * The sessionID that encountered the problem or was captured in step 16.\n \n \n * historyReport.html generated by running the tool genHistoryReport.bat or genHistoryReport.sh, located in the install_root/bin directory; historyreport.html is generated in the working directory of where the genHistoryReport tool is run.\n \n \n \n 18. Follow instructions to send diagnostic information to IBM support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852].\n\n\n\nFor a listing of all technotes, downloads, and educational materials specific to the Session and Sessions Management component, search the WebSphere Application Server support site [http://www.ibm.com/software/webservers/appserv/was/support/]. \n\nRelated information \nSubmitting information to IBM support [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21153852] \nSteps to getting support for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/support/appserver_support.html] \nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21145599] \nTroubleshooting guide for WebSphere Application Server [http://www.ibm.com/support/docview.wss?rs=180&uid=swg27005324] \nEXCHANGING DATA WITH IBM SUPPORT\nTo diagnose or identify a problem, it is sometimes necessary to provide Technical Support with data and information from your system. In addition, Technical Support might also need to provide you with tools or utilities to be used in problem determination. You can submit files using one of following methods to help speed problem diagnosis: \n\n * IBM Support Assistant (ISA) \n * Service Request (SR)\n * E-mail \n * FTP to the Enhanced Customer Data Repository (ECuRep)\n\n\n\n\nInstructions for exchanging information with IBM Support [http://www.ibm.com/support/docview.wss?uid=swg21153852]\n\nREAD FIRST AND RELATED MUSTGATHERS\nMustGather: Read first for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599]\n\n\n\n\n Classloader problem [http://www.ibm.com/support/docview.wss?uid=swg21196187] Dynamic Cache Problem [http://www.ibm.com/support/docview.wss?uid=swg21193837] JNDI Problem [http://www.ibm.com/support/docview.wss?uid=swg21143296] JTS Problem [http://www.ibm.com/support/docview.wss?uid=swg21153216] ORB Problem [http://www.ibm.com/support/docview.wss?uid=swg21157005] Scheduler Problem [http://www.ibm.com/support/docview.wss?uid=swg21220349] Workload Management Problem [http://www.ibm.com/support/docview.wss?uid=swg21052165] \n\nRELATED INFORMATION\n Recording your screen to share with IBM Support [https://www.ibm.com/developerworks/community/blogs/IBMElectronicSupport/entry/recording_your_screen_to_share_with_support?lang=en]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server - Express Java SDK AIX, HP-UX, Linux, Solaris, Windows Application Servers Runtimes for Java Technology Java SDK", "question": "Application code is overriding session timeout in WebSphere Application Server 7.0 How to check if application code is overriding session timeout? Is there a WebSphere trace that will show this information? ", "answer": "The first step in solving a problem with your HTTPSession in Application Server is to reproduce the problem with session tracing enabled. Adding debug code to the application simplifies the task of identifying the problem."} +{"id": "TRAIN_Q168", "document": "IBM Security Bulletin: Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-2961 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2961]\nDESCRIPTION: IBM Integration Bus uses the Apache Tomcat server for serving HTTP requests for the HTTPInput and SOAPInput nodes. A vulnerability exists where an unauthenticated, remote attacker can send a malformed HTTP POST request to the integration server HTTP listener. The attacker could use the information in the Java stack trace to identify the version of Apache Tomcat in use.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113806 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113806] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) \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 IT15188 The APAR is available in fix pack 10.0.0.5 IBM Integration Bus\n\n\nV9\n\nIT15188 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=IT15188 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15188]\n\nThe APAR is targeted to be available in fix pack 9.0.0.6 WebSphere Message Broker V8 IT15188 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/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15188 [http://www.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15188]\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. \nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp://www.ibm.com/support/docview.wss?uid=swg27006308 [http://www.ibm.com/support/docview.wss?uid=swg27006308]\n\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] CHANGE HISTORY\n 21-Jun-2016 - 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.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21986827]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker 8.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin: Integration server HTTP listener exposes stack trace in WMB & IIB (CVE-2016-2961) I need to understand details regarding Security Bulletin: Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus. Where can I find this information? ", "answer": "CVEID: CVE-2016-2961 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2961]\nDESCRIPTION: IBM Integration Bus uses the Apache Tomcat server for serving HTTP requests for the HTTPInput and SOAPInput nodes. A vulnerability exists where an unauthenticated, remote attacker can send a malformed HTTP POST request to the integration server HTTP listener. The attacker could use the information in the Java stack trace to identify the version of Apache Tomcat in use.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113806 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113806] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)"} +{"id": "TRAIN_Q170", "document": "IBM Flush Out Old Entries in the MQSeries Events Workspace - United States MQSeries Events workspace Current Events flush 5724K3500TR TECHNOTE (FAQ)\n\nQUESTION\n How can I flush out old entries in the MQ Series Events workspace for channels or queues that no longer exist? \n\nANSWER\nThe MQSeries Events workspace displays data from the Current Events attribute group. Since this data is stored in memory, stopping and restarting the MQ Monitoring agent will clear all the data in the Current Events table.", "question": "MQSeries Events correlation How are MQSeries Events cleared? ", "answer": "The MQSeries Events workspace displays data from the Current Events attribute group. Since this data is stored in memory, stopping and restarting the MQ Monitoring agent will clear all the data in the Current Events table."} +{"id": "TRAIN_Q171", "document": "IBM Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM DB2 is shipped as a component of WebSphere Remote Server. Information about security vulnerabilities affecting IBM DB2 has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nFor vulnerability details, see the security bulletin TLS padding vulnerability affects IBM DB2 LUW (CVE-2014-8730) [http://www.ibm.com/support/docview.wss?uid=swg21692618]. \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Remote Server V6.1, 6.2, 6.2.1, 7.0, 7.1, 7.1.1, 7.1.2, 8.5 IBM DB2 Workgroup Server Edition \nV9.1, 9.5, 9.7, 10.1, 10.5 GET 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] \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] CHANGE HISTORY\n 27 March 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.", "question": "Help with Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730) I need to understand details regarding Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730). Where can I find this information? ", "answer": "For vulnerability details, see the security bulletin TLS padding vulnerability affects IBM DB2 LUW (CVE-2014-8730)"} +{"id": "TRAIN_Q172", "document": "IBM StoredIQ support for TLS v1.2 - United States StoredIQ TLS secure SSL TECHNOTE (FAQ)\n\nQUESTION\n Does StoredIQ support TLS v1.2? \n\nCAUSE\nTLS 1.0 is being phased out and moving to 1.2\n\nANSWER\nYes, StoredIQ 7.6.0.5 and above support TLS 1.2. TLS 1.2 is supported both on Application Stack and Dataserver", "question": "Does StoredIQ support TLS v1.2? Does StoredIQ support TLS v1.2? ", "answer": "Yes, StoredIQ 7.6.0.5 and above support TLS 1.2. TLS 1.2 is supported both on Application Stack and Dataserver"} +{"id": "TRAIN_Q174", "document": "IBM WCM page and authoring portlet may not display after migration - United States WPv7000eGA; migrating; migrate; migration; V7.0; v7; WCM; out-of-box page; out of the box; page; authoring portlet; may not reach; cannot reach; cannot access; no access; exceptions; IWKAP0009E; Servlet not enabled TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAfter migrating to IBM WebSphere Portal V7.0, you may not be able to navigate to or display the Web Content Manager (WCM) out-of-box page or the authoring portlet. In addition, some related functions in the user interface might not work or might generate exceptions when accessed. Clicking buttons in the authoring portlet may generate the following error in the log: \n\n * \n * IWKAP0009E: Servlet not enabled\n * \n\n\nIf this occurs, you must re-enable these features manually after migration. \nCAUSE\nThe migration process can disable some new out-of-the-box features if the feature did not exist in the previous release or if it was updated. In particular, the Portal page required for the reserved authoring portlet is missing and the permissions on the AJAX proxy servlet are not set correctly.\n\n\nRESOLVING THE PROBLEM\nTo re-enable the affected features manually after migration, do the following: \n\n\n1. Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.\n\n2. Deploy the hidden Portal page on which the reserved authoring portlet is installed. \n\n\n3. Run the following task from the wp_profile_root / Config Engine directory. \n * Cluster note:\n * \n\n * Windows:\n * \n * \n * ConfigEngine.bat install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * U\n * NIX:\n * \n * ./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * i/S\n * y\n * stem\n * :\n * \n * ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n * \n * \n * z/OS \n * \n * :\n * \n * ./ConfigEngine.sh install-wcm-hidden-authoring-page -DWasPassword=\n * password\n \n\nNo restart of the Portal server is required. \n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management IBM Web Content Manager Migration AIX, IBM i, Linux, Solaris, Windows, z/OS 7.0, 6.1", "question": "Can not create a portal wcm syndicator-subscriber pair. The \"Subscribe Now\" window pops up but is blank or corrupted. Why? Can not create a portal wcm syndicator-subscriber pair. The \"Subscribe Now\" window pops up but is blank or corrupted.", "answer": "1. Make sure that the page on which the WCM authoring portlet is installed uses a theme with client-side rendering such as the Page Builder theme.\n\n2. Deploy the hidden Portal page on which the reserved authoring portlet is installed. \n\n\n3. Run the following task from the wp_profile_root / Config Engine directory."} +{"id": "TRAIN_Q178", "document": "IBM After restoring BigFix server database, ILMT/BFI/SUA server may not import all the data since the restore correctly - United States sequance number; resotre; database; missing data; gap TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n After you restore the BigFix database and run an import, new data is not displayed in BFI/SUA/LMT even after successful ETL imports. \n\nSYMPTOM\nNot all data reported already by endpoints to BigFix server are visible in LMT/BFI console. This may include scan results, capacity data, etc.\n\n\nCAUSE\nBFI/SUA/LMT is designed to import only newly created data. To achieve this, the data is marked with the so-called sequence number. The sequence number is incremented during every change, upload, scan, etc. Every import contains data starting from the sequence number reported during the last successful import to the current sequence number. \n\nWhen the database is restored, the sequence number is restored to the value from the time when the database backup was created. Because of that, it might happen that the sequence number after the restoration is lower than the sequence number reported during the last successful import. In such case, the first import after the database restoration does not include any data. After that import, the sequence number is updated and the next import contains new data. Depending on your scan settings, you might need to wait some time for the import that contains new data. \n\nWhen the database is restored, the sequence number is restored to the value from the time when the database backup was created.\n\nData for the period from the last successful import before the restoration of the database until the restoration is never imported (obviously, as the data was removed by restoring the DB) and needs to be re-generated by re-running the scans if needed. \n\nData from DB restoration time until first successful import is also by default not imported (causing a gap). To cover this gap you may follow the procedure described below.\n\n\n\nRESOLVING THE PROBLEM\nWarning: The following procedure will impact the length of the first import after the sequence is reset. After performing below steps ALL DATA from all endpoints available on BigFix server side will be imported (not only covering the problematic gap). For big environments the impact may be huge and it is better to re-run scans on selected endpoints instead.\n\n1) Ensure that the import is not running and stop the BFI/SUA/LMT server.\n2) To reset the sequence for all data sources and import all data, run the following query on the BFI/SUA/LMT database:\n\nDB2:\nUPDATE dbo.DATASOURCE_SEQUENCES set LAST_SEQUENCE = blob(x'0000000000000000');\n\nMSSQL:\nUPDATE dbo.datasource_sequences set last_sequence = 0x0000000000000000;\n\n3) Start the BFI/SUA/LMT. \n4) Run an import.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory", "question": "ILMT agent doesn`t show the hostname on inventory hardware Hello community: I have a problem with a host. I installed ILMT agent and i exec all the task (install scan,initiate scan,run capacity and upload results....) after that i not see the hostname at the ILMT webpage, i only recognized the host by the System ID. The Hypervisor is KVM. I do this tasks with many other host like that and i not found problems.I attached an image.\n\nCan you help me to manage this issue?\n\nThank you and Best regards.", "answer": "1) Ensure that the import is not running and stop the BFI/SUA/LMT server.\n2) To reset the sequence for all data sources and import all data, run the following query on the BFI/SUA/LMT database:\n\nDB2:\nUPDATE dbo.DATASOURCE_SEQUENCES set LAST_SEQUENCE = blob(x'0000000000000000');\n\nMSSQL:\nUPDATE dbo.datasource_sequences set last_sequence = 0x0000000000000000;\n\n3) Start the BFI/SUA/LMT. \n4) Run an import."} +{"id": "TRAIN_Q182", "document": "IBM Configuring the Tomcat Data Collector to run as a Windows service - United States ITCAM; J2EE; Tomcat; Windows; Service; CAMJ2ALL; CAMJ2INST; CAMJ2TCDC TECHNOTE (FAQ)\n\nQUESTION\n What is the correct procedure to configure the ITCAM for J2EE Data Collector for Tomcat to run as a Windows service? \n\nCAUSE\nThere is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC. This option does not work and will result in a failed configuration.\n\n\n\n[/support/docview.wss?uid=swg21961542&aid=1] [/support/docview.wss?uid=swg21961542&aid=1]\n\nThis option will be removed from the drop down menu for the Tomcat DC Configuration, according to APAR PI43783.\n\n\nANSWER\nTomcat on Windows platforms must be installed from a base distribution, that is extracting a .zip file named like apache-tomcat-7.0.62.zip, even though one plans to start Tomcat only as a Window Service, and not with a startup script. \n\n\nIf you install Tomcat from the Windows Service Installer (e.g. apache-tomcat-7.0.62.exe), rather than a base distribution, some of the command-line and startup scripts for launching Tomcat will not be included, and you won't be able to complete the following procedure.\n\n\n1- Configure the DC using the Normal Startup option.\n\n[/support/docview.wss?uid=swg21961542&aid=2] [/support/docview.wss?uid=swg21961542&aid=2]\n\nOn a supported Windows 64-bits platform with the YJ 7.1.1.0.0 installed in E:\\IBM\\ITM\\, and with a Tomcat 7 running a supported version of Sun HotSpot JRE , this will result in the following stanza being added into the \\bin\\catalina.bat file:\n\n\nREM -----Configurator of DC Begin----------\n\nset PATH=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\win64;%PATH%\nset JAVA_OPTS=-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\bcm-bootstrap.jar -Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ppe.probe-bootstrap.jar -Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ext\\tomcat\\tomcat.bcm.jar -agentlib:am_sun_16=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\dc.env.properties -Xloggc:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\gc.log -XX:-TraceClassLoading -XX:-TraceClassUnloading -Dcom.sun.management.jmxremote -Dsun.lang.ClassLoader.allowArraySyntax=true %JAVA_OPTS%\n\nREM -----Configurator of DC End----------\n\n\nYou might want to check at this point if the DC is correctly started when you start the Tomcat via the startup.bat script, even though you will start Tomcat as a Windows Service in the future.\n\n\n2- Right-click the Tomcat Service icon on the Windows taskbar and click Configure.\n\n3- When the Apache Tomcat properties window opens, click the Java™ tab.\n\n4- From the open catalina.bat file, copy the value for JAVA_OPTS, and paste it into the text box labelled Java Options (in the Apache Tomcat Properties window).\n\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\bcm-bootstrap.jar\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ppe.probe-bootstrap.jar\n-Xbootclasspath/p:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\itcamdc\\lib\\ext\\tomcat\\tomcat.bcm.jar\n-agentlib:am_sun_16=E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\dc.env.properties\n-Xloggc:E:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\runtime\\tomcat70.nc114017.romelab.it.ibm.com.Tomcat7\\gc.log\n-XX:-TraceClassLoading\n-XX:-TraceClassUnloading\n-Dcom.sun.management.jmxremote\n-Dsun.lang.ClassLoader.allowArraySyntax=true\n\n\n[/support/docview.wss?uid=swg21961542&aid=3]\n\n\n6- Add to the System Environment Variable PATH into the System Environment Variables the same value that was set for PATH into the catalina.bat:\n\n\\toolkit\\lib\\\n\nin our Windows 64-bits example:\n\nE:\\IBM\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\toolkit\\lib\\win64\n\nApart from small differences depending on the particular Windows distribution, this can basically be done from Control Panel-->Advanced System Settings-->Environment Variables-->Edit System Variable: Path\n\n\n[/support/docview.wss?uid=swg21961542&aid=4] [/support/docview.wss?uid=swg21961542&aid=4]\n\n\n7- Restart Windows.", "question": "ITCAM J2EE configuration problem with Tomcat as a Windows Service I want to configure ITCAM for J2EE 7.1.1.0.0 agent to monitor Tomcat 7.0 to be started as a service on Windows 2008 R2 64-bits.\n\nConfiguration fails with the following error message:\n\n2016-05-06 20:31:37.723+08:00\ncom.ibm.tivoli.itcam.install.j2ee.custompanel.ConfigProcessSectionPanel getActionErrorText [DEBUG_MIN]\nExit, return value = J2_EC_CONFIG_FAILED:Configuration failed.\nThe server is: \"Tomcat Application Server\"\nThe instance is: \"myTomcat\"\nThe trace log file is under the directory:\n\"C:\\tivoli\\ITM\\TMAITM6\\j2eedc\\7.1.1.0.0\\installer\\logs\"\n\nWhy is this failing?", "answer": "There is an option to specify the Tomcat Windows Service during GUI configuration of the ITCAM J2EE 7.1.1 agent/DC. This option does not work and will result in a failed configuration."} +{"id": "TRAIN_Q183", "document": "IBM StoredIQ Dataserver login page is not coming up in the browser - United States TECHNOTE (FAQ)\n\nQUESTION\n Why is the StoredIQ Dataserver login page not coming up in the browser? \n\nCAUSE\nThis is caused by missing or incorrect hostname in the /etc/hosts file. When you restart the apache service, you will see an error message - cannot reliably\ndetermine the fully qualified sever domain name\n\n\nANSWER\n \n\n 1. Login to the appliance as root \n 2. Edit the /etc/hosts file \n 3. Update the correct hostname and save changes \n 4. Restart the appliance", "question": "Why is the StoredIQ Dataserver login page not coming up in the browser? Why is the StoredIQ Dataserver login page not coming up in the browser? ", "answer": "This is caused by missing or incorrect hostname in the /etc/hosts file. When you restart the apache service, you will see an error message - cannot reliably\ndetermine the fully qualified sever domain name"} +{"id": "TRAIN_Q184", "document": "IBM When attempting to install a second Portal 8.5 instance on the same machine you receive the error, \"ERROR: Error executing the work flow. Step 'Basic Config' FAILED!\" - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIn this case, the customer had a business requirement that required installing 2 separate Portal installs on the same AIX machine. The first instance of Portal installed successfully. However, the second Portal instance failed during install with the following error....\n\nERROR: Error executing the work flow. Step 'Basic Config' FAILED!.\nCheck the logs for additional error messages.\n[/opt/wps85/scm/PortalServer/installer/wp.\nconfig/wizard/repository/repository_actions.xml:622]\n\nSYMPTOM\nThe IIM logs shows the following...\n[04/02/2015 17:29:30] PLPR0013I: Saving Console Enterprise Application\n[04/02/2015 17:29:30] PLPR0014I: Closing Console Enterprise Application\n[04/02/2015 17:29:48] PLPR0003I: Opening Console Enterprise Application\n- /opt/was85/base/scm/systemApps/isclite.ear\n[04/02/2015 17:30:01] PLPR0014I: Closing Console Enterprise Application\n\nStdErr: \n\n\nglobal\ncom.ibm.cic.agent.internal.core.IMLoggerImpl\ninfo\nReset current process umask from 022 to 022.\n\n\ncom.ibm.cic.common.logging.LogManager\norg.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory\n\nsafeLogged\n\nA problem occurred during the execution of the {0} file.\nERROR: Error executing the work flow. Step 'Basic Config' FAILED!.\nCheck the logs for additional error messages.\n[/opt/wps85/scm/PortalServer/installer/wp.config/wizard/repository/repos\nitory_actions.xml:622]\n\nA package has an issue that cannot be resolved by Installation Manager.\nIdentify the package that has the issue by looking at the installation\nhistory. In Installation Manager, click File > Installation History.\nIn console mode, enter S: View Installation History. Contact IBM\ncustomer support.\n\n/opt/wps85/scm/PortalServer/installer/wp.config/wizard/repository/r\nepository_actions.xml\n\n\n\n\n\nCAUSE\nIn this case, the problem was caused by the fact that the first Portal install was still running when the second Portal install was attempted\n\n\nENVIRONMENT\nPortal 8.5 \n\nAIX\n\n\nDIAGNOSING THE PROBLEM\nFurther review of the IIM logs earlier in the install sequence shows the following message.. \n\n\nERROR 06:32.98 Running processes have been detected that may\ninterfere with the current operation. Stop all WebSphere and related\nprocesses before continue.\n\n\nRESOLVING THE PROBLEM\nStop all WebSphere processes on the machine and attempt to install the second Portal instance again", "question": "I am trying to install Portal 8.5 on Windows and getting error, CRIMA1217E in the IIM logs While trying to install Portal 8.5 using IIM it fails and the following is in the IIM logs...\n\n 549 ERROR CRIMA1217E 01:01:00.16 A problem occurred during the\n execution of the\n C:\\IBM\\WebSphere\\PortalServer\\installer\\wp.config\\wizard\\repository\\repo\n sitory_actions.xml file.\n ERROR: Error executing the work flow. Step 'Basic\n Config' FAILED!. Check the logs for additional error messages.\n [C:\\IBM\\WebSphere\\PortalServer\\installer\\wp.config\\wizard\\repository\\rep\n ository_actions.xml:622]\n A package has an issue that cannot be resolved by\n Installation Manager.\n Identify the package that has the issue by looking at\n the installation history. In Installation Manager, click File >\n Installation History. In console mode, enter S: View Installation\n History. Contact IBM customer support.\n \n 550 ERROR 01:01:00.16 Creating WebSphere Portal Profile. This\n will take several minutes.\n", "answer": "Stop all WebSphere processes on the machine and attempt to install the second Portal instance again"} +{"id": "TRAIN_Q186", "document": "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13) \n\nSupport for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \n\nNOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version). \nThe top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English. \nThe official MacOSX 10.13.1 version do not have this issue. So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple. \n\n \n\nB) Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra. \n\n \n\nC) Apple Macintosh OSX El Capitan (10.11) \n\nSupport for IBM SPSS Statistics 24. Please see the Release notes - IBM SPSS Statistics 24.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27047057] for known issues on Macintosh. \n\nFull documentation including installation material provided in different languages and manuals for release 24 can be found on IBM SPSS Statistics 24 Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg27047033] webpage. \n\n \n\nAlso, Support for IBM SPSS Statistics 23. Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391] \n\n \n\nD) Apple Macintosh OSX Yosemite (10.10) \n\nSupport for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n \n\nNote: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released. If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well. Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10. So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: \n\n**** \n\nIn some instances it can be necessary to re-install the legacy Apple Java 6 on 10.10 for the use of Statistics 22 FixPack 2 on this platform\n\nDownload and re-install Apple Java 6 \n\n- After you upgraded your Apple Mac OSX from a previous release to 10.10, Apple Java 6 may no longer exists on your upgraded system. If you then launch Statistics 22 which is an application that relies on Java 6, it can happen, the Mac OS pops up a dialog box stating Java 6 was requested, but none is present.\n- The Java dialog has a \"More Info\" button, which when clicked opens a browser to an Apple Tech Support page for Apple Java 2014-001. A download link is provided:\nhttp://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]\n- Click on the download link and a DMG containing the Java 6 installer is downloaded.\n- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6.\n\n******* \n\n \n\nE) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n*** \n\nNote: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22. Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. \n\n**** \n\nF) Apple Macintosh OSX Mountain Lion (10.8) \n\nSupport for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 \n\n**** \n\nG) Apple Macintosh OSX Lion (10.7) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nH) Apple Macintosh OSX Snow Leopard (10.6) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nOlder SPSS Statistics releases 18 and 19 and 20: \n\nPlease note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM. Please contact IBM Sales department to renew your contracts.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]", "question": "IBM SPSS Statistics 25.0.0.1 MacOS 10.13 High Sierra. Will the german IBM SPSS statistics 25.0.0.1 on MAC be compatible with MAC OS High Sierra (10.13)?\n", "answer": "Support for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra."} +{"id": "TRAIN_Q187", "document": "IBM HTTP Session time-out settings and overwrite precedence rules - United States WebSphere http session management time-out wasrun precedence overwrite TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to set the HTTP Session time-out in various places on the IBM® WebSphere® Application Server Administrative Console. It is also possible to set HTTP Session time-out for the application packaging process. \n\nSince Session time-out can be set in multiple places, it is necessary to understand how the ultimate Session time-out for an application is determined. \n\nCAUSE\nApplication needs HTTP session time-out set.\n\nRESOLVING THE PROBLEM\nThe HTTP Session time-out can be set in the following places: \n\n * From the Administrative Console at the server, Enterprise application, and Web application levels \n * At the time when the application is packaged \n * In the application code\n\n\nSetting the HTTP Session time-out from the Administrative Console \n1. To set the HTTP Session time-out at the server level, navigate to Servers > Application Servers > Your Server > Web Container > Session Management. \n\nIn the Session time-out section of this window, you can select No time-out or Set time-out by clicking the appropriate radio button. If you choose to set the time-out, type the desired value in minutes in the box. \n\n\n2. To set the HTTP Session time-out at the Enterprise Application level, navigate to Applications > Enterprise Applications > Your Application > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level. \n\n\n3. To set the HTTP Session time-out at the Web Application level, navigate to Applications > Enterprise Applications > Your Application > Web Module > Your Web App.war > Session Management. \n\nCheck Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the Application Session to overwrite those values set at the parent levels, which in this case is the Server or Enterprise Application level. \n\nAfter modifying these settings, save the master configuration. \n\nSetting HTTP Session time-out when application is packaged \n\nThe application developer can also select to set the HTTP Session time-out parameter when the application is packaged. This value is stored in the web.xml file for the Web application. \n\nThis setting overrides any session time-outs defined from the Administrative Console. Alter this setting by repackaging the application with a new value, or by modifying the web.xml file. The entry in the web.xml will be as follows: \n           \n *          60\n * \n *       \n\n \n\nWhere the \"session-timeout\" is an integer value for the desired session time-out in minutes. \nSetting HTTP Session time-out from the application code \n\nFinally, the HTTP Session time-out can be set in the application code. The programmer can invoke the setMaxInactiveInterval() method on HttpSession object to set the time-out value as desired. This setting overrides any time-out defined in the application package or made from the Administrative Console. \n\nHTTP Session time-out Override Precedence Summary \n\nThe list below shows the precedence from which the final HTTP Session time-out is derived. \n\n1. Server Level [/support/docview.wss?uid=swg21163875&aid=1] Lowest level 2. Enterprise Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server Level if Override is selected 3. Web Application [/support/docview.wss?uid=swg21163875&aid=1] Overrides the Server and Enterprise Application settings if Override is selected 4. Application Level (web.xml) [/support/docview.wss?uid=swg21163875&aid=1] Overrides Server, Enterprise Application, and Web Application settings 5. Application Code [/support/docview.wss?uid=swg21163875&aid=1] Overrides all other settings RELATED INFORMATION\n A simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21659740]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "How to resolve coach service timeout or expired issue? Customer has followed http://www-01.ibm.com/support/docview.wss?uid=swg21633251 and http://www-01.ibm.com/support/docview.wss?uid=swg21601357 to set up long time session but customer still got error message: \"The service you are trying to run has expired.\" only when the user keep a coach session idle that over 30 minutes. How to resolve this issue? ", "answer": "Check Override in the Override Session Management section, then select to set the time-out and the time-out value. This sets the application session to overwrite those values set at the parent, which in this case is the Server level."} +{"id": "TRAIN_Q188", "document": "IBM Gathering detailed JazzSM Page and Widget information - United States DASHL2FAQ; Page; Widget; release; detailed; information TECHNOTE (FAQ)\n\nQUESTION\n How can I get detailed information about defined Pages and the Widgets on the Page? \n\nCAUSE\nPage and Widget release information that will be needed for PMR's\n\nANSWER\nThere are two options, display information about the Page and defined widgets and wires on the page, or show information about just the widgets. Both methods are explained below. \n\nIn the upper right portion of the displayed Page, right click on the icon followed by either the \"About\" or \"Edit Page\" on the pull down menu item as shown below. \n\n[/support/docview.wss?uid=swg21976068&aid=1]\n\nThe \"About\" selection will show the following information about the Page and Widgets widgets, wires defined on the Page:\n\n\"Console\", \"General\" information showing the DASH version, layout of the page and information about each of the defined widgets and wires on the page. Below is an example of the Widget information displayed:\n\n[/support/docview.wss?uid=swg21976068&aid=2] [/support/docview.wss?uid=swg21976068&aid=2]\n[/support/docview.wss?uid=swg21976068&aid=3] [/support/docview.wss?uid=swg21976068&aid=3]\n\nThe second option is to display only the information about a single widget. \n\nSelecting the \"Edit Page\" shown in the first screen shot above, you an then right click on the widgets, select \"About\" from the pulldown as shown below, \n\n\n[/support/docview.wss?uid=swg21976068&aid=4]\n\n[/support/docview.wss?uid=swg21976068&aid=5] [/support/docview.wss?uid=swg21976068&aid=5]", "question": "How can I get detailed JazzSM PAGE and Widget release information. How can I get detailed JazzSM PAGE and Widget release information.", "answer": "There are two options, display information about the Page and defined widgets and wires on the page, or show information about just the widgets."} +{"id": "TRAIN_Q189", "document": "IBM Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? - United States J2EE JBoss server Windows service LA2 fix TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? \n\nANSWER\nWhen you configure the JBoss Application Service to run as a Windows service, you will download the JBoss native connectors [http://jbossweb.jboss.org/downloads/jboss-native-2-0-10] and modify the service.bat file. \n\nThe JBoss service is not available to run as a Windows service when configured with the ITCAM for J2EE agent/DC because this involves changes to the JBoss native connector files and this is currently not supported. Additionally, there's no option to specify the Service name when configuring the JBoss server during the configuration steps. \n\nIf you are using JBoss AS 7.1 or JBoss EAP 6.1.0 or 6.2.0 or 6.3.0, then you will need the to use the latest patch first, [https://developer.ibm.com/answers/questions/208313/how-do-i-download-the-new-itcam-for-j2ee-711-la-if.html]then run the standalone.bat (or domain.bat) program from the command-line after successful configuration. \n\nNote: If you have a Tomcat server, then you will be able to use that server in a Service, the technote is here. [http://www.ibm.com/support/docview.wss?uid=swg21961542]\n\n \n\nPRODUCT ALIAS/SYNONYM\n ITCAM for J2EE", "question": "Is using a monitored JBoss server with ITCAM supported in a Windows Service? Is using a monitored JBoss server with ITCAM supported in a Windows Service? ", "answer": "The JBoss service is not available to run as a Windows service when configured with the ITCAM for J2EE agent/DC"} +{"id": "TRAIN_Q190", "document": "IBM Switching Business Process Choreographer Explorer back to using HTTP from HTTPS - United States DOWNLOADABLE FILES\n\nABSTRACT\n In Business Process Manager Advanced Version 8.0.1, the default protocol used by Business Process Choreographer Explorer was changed to use HTTPS. You can switch it back to HTTP. \n\nDOWNLOAD DESCRIPTION\nWhen Business Process Choreographer Explorer uses the default secure HTTPS protocol, any attempts to access Business Process Choreographer Explorer using HTTP are redirected to use HTTPS. If you need Business Process Choreographer Explorer to support insecure HTTP connections, you can use the unsecureExplorer.ant script to switch the protocol used from HTTPS to HTTP. \n\nAttention: It is not recommend to use the insecure HTTP protocol. Using HTTP for the Business Process Choreographer Explorer can open your organization to possible security problems.\n\nSwitching to HTTP\n\nIf you need to switch Business Process Choreographer Explorer from HTTPS to use HTTP, complete the following actions: \n\n 1. Download the unsecureExplorer.ant script file, which is attached near the bottom of this page.\n \n \n 2. If you previously switched Business Process Choreographer Explorer to use HTTP, but are performing this task again because you are installing an interim fix, fix pack, or refresh pack that updated Business Process Choreographer Explorer has reverted it back to the default HTTPS protocol, you must first delete the old (invalid) backup EAR file before running the script.\n \n * On Linux, UNIX-based and z/OS platforms, delete the install_root/ProcessChoreographer/internal/bpcexplorer_secure_backup.ear file. \n * On Microsoft Windows platforms, delete the\n install_root\\ProcessChoreographer\\internal\\bpcexplorer_secure_backup.ear file.\n \n \n \n \n 3. Run the script to patch the bpcexplorer.ear file. In a network deployment environment, you must run the script on the deployment manager. * On Linux, UNIX-based and z/OS platforms, enter the following command:\n install_root/ws_ant.sh -f unsecureExplorer.ant \n * On Windows platforms, enter the following command:\n install_root\\ws_ant.bat -f unsecureExplorer.ant\n Note: A backup copy of the original EAR file is created named bpcexplorer_secure_backup.ear.\n \n \n \n \n 4. Deploy the patched bpcexplorer.ear file by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For version 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414]. \n * For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449].\n \n \n \n \n\nRemember: In the future, if you install an interim fix, fix pack, or refresh pack that updates the Business Process Choreographer Explorer, it will revert to using the default secure HTTPS protocol. If that happens and you still need the Business Process Choreographer Explorer to use the HTTP protocol, you must complete these steps again to re-enable the HTTP protocol. \n\n\n\nSwitching back to HTTPS \n\nIf you need to switch Business Process Choreographer Explorer back from HTTP to HTTPS, complete the following actions: 1. Change to the directory where the backup EAR file is located. * On Linux, UNIX-based and z/OS platforms, its location is \n install_root/ProcessChoreographer/internal \n * On Windows platforms, its location is \n install_root\\ProcessChoreographer\\internal\n \n \n \n \n 2. In that directory, copy or rename the backup EAR file bpcexplorer_secure_backup.ear to bpcexplorer.ear and overwrite any existing copy.\n \n \n 3. Deploy the original HTTPS version by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For versions 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414]. \n * For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449].\n \n \n \n\nDownload file unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=2]unsecureExplorer.ant [/support/docview.wss?uid=swg24034421&aid=1]\n\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n BPM", "question": "Does anyone know how to disable HTTPS to HTTP redirection for BPC Explorer? \n\nIt appears that by default, BPC comes configured with https instead of http.\n\nIs there a way to configure BPC to use http instead or are there steps for configuring BPC to use http? Need to avoid accessing BPC explorer via https.", "answer": "1. Download the unsecureExplorer.ant script file, which is attached near the bottom of this page.\n \n \n 2. If you previously switched Business Process Choreographer Explorer to use HTTP, but are performing this task again because you are installing an interim fix, fix pack, or refresh pack that updated Business Process Choreographer Explorer has reverted it back to the default HTTPS protocol, you must first delete the old (invalid) backup EAR file before running the script.\n \n * On Linux, UNIX-based and z/OS platforms, delete the install_root/ProcessChoreographer/internal/bpcexplorer_secure_backup.ear file. \n * On Microsoft Windows platforms, delete the\n install_root\\ProcessChoreographer\\internal\\bpcexplorer_secure_backup.ear file.\n \n \n \n \n 3. Run the script to patch the bpcexplorer.ear file. In a network deployment environment, you must run the script on the deployment manager. * On Linux, UNIX-based and z/OS platforms, enter the following command:\n install_root/ws_ant.sh -f unsecureExplorer.ant \n * On Windows platforms, enter the following command:\n install_root\\ws_ant.bat -f unsecureExplorer.ant\n Note: A backup copy of the original EAR file is created named bpcexplorer_secure_backup.ear.\n \n \n \n \n 4. Deploy the patched bpcexplorer.ear file by updating the profile. For more information about updating profiles for an interim fix, see one of the following documents: * For version 8.0.1.x: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21608414]. \n * For version 8.5 and later: Profile update instructions for IBM Business Process Manager (BPM) interim fixes [http://www.ibm.com/support/docview.wss?uid=swg21637449]."} +{"id": "TRAIN_Q193", "document": "IBM New IBM License Metric Tool online Support experience! - United States NEWS\n\nABSTRACT\n IBM Security Support announced in October, 2017, that changes to your online IBM License Metric Tool (ILMT) Support experience were coming. See below for the text of the mailing to that was sent to Support customers. \n\nCONTENT\n\nDear IBM License Metric Tool Customer,\n\nIn addition to the recently announced LMT forum process [http://ibm.biz/ILMTforumAnnounce], we are excited to announce that we are launching a new online Support experience. Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017. \n\nThe move to this new online Support experience should be seamless for you. \n\n\n * As announced earlier this year, IBM dW Answers [https://developer.ibm.com/answers/index.html] should still be your first avenue to Support. \n * The e-mail and phone support channels offered to you today will remain unchanged. \n * Your bookmarks and existing access methods will automatically connect to the new online Support experience once you’ve selected your IBM Security product or you can use a new URL to reach the new online Support experience directly: https://www.ibm.com/mysupport [https://www.ibm.com/mysupport]. \n * Any existing PMRs will be automatically converted to “Cases” in the new experience. Simply choose “cases” from the Security product support landing page to see status or make updates. \n\n\nIf you are experiencing a problem with the portal (such as a login issue, etc.), we are here to help. You can submit your issue via our Support page [https://www.ibm.com/mysupport/s/] by clicking “Email IBM Support”, or by emailing spe@us.ibm.com. \n\nShould you have any questions, please send email to isssprt@us.ibm.com [isssprt@us.ibm.com?subject=Changes%20to%20your%20IBM%20Support%20experience]. [/support/docview.wss?uid=swg22009938&aid=1] IBM Security Support Team \n\nPRODUCT ALIAS/SYNONYM\n LMT", "question": "IBM Security announces a new online Support experience that is coming soon! What is happening online for IBM License Metric Tool customers? ", "answer": "In addition to the recently announced LMT forum process [http://ibm.biz/ILMTforumAnnounce], we are excited to announce that we are launching a new online Support experience. Most IBM Security products, including IBM License Metric Tool, will go live with this new technology at the end of October, 2017."} +{"id": "TRAIN_Q194", "document": "IBM Support's Guide to IBM CORBA probes - United States corba; visibroker; ibm corba; orb; ior; ior file; nonnative; probes; probe; corba-framework; dumpns; CORBA TECHNOTE (FAQ)\n\nQUESTION\n IBM CORBA probe : What happened to the visibroker patches? \n\nCAUSE\nVisibroker was replaced by the IBM CORBA integration\n\nANSWER\n \n\nThe Visibroker software is a third party product, and was replaced in 2012 by the IBM CORBA software. \n\n \n\nPlease review Support's Guide to IBM CORBA probes [attached] to understand the integration, alongside the probe's specific documentation.\n\nGENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=2]GENERIC_CORBA_SupportsGuide_20.pdf [/support/docview.wss?uid=swg21614208&aid=1]", "question": "Is there a support's guide to the CORBA Probes? Is there a support's guide to the IBM CORBA probes?", "answer": "GENERIC_CORBA_SupportsGuide_20.pdf"} +{"id": "TRAIN_Q195", "document": "IBM When importing a projects.csv file, the COORDINATOR column must be in the loginId:Role format. - United States PRODUCT DOCUMENTATION\n\nABSTRACT\n When you import a projects.csv file, if the COORDINATOR column is not in the loginId:Role format, the import will fail. \n\nCONTENT\nThe import fails with following error in the import logs:\n\n\n ERROR - FAILED: Create failed for Projects row 1: StringIndexOutOfBoundsException = null\n\nEnsure that the COORDINATOR column is in the loginId:Role format to prevent errors.", "question": "How to resolve \"StringIndexOutOfBoundsException = null\" \n\nWhen importing a projects.csv file, the import fails with following error in the import logs:\n\nERROR - FAILED: Create failed for Projects row 1: StringIndexOutOfBoundsException = null Ensure that the COORDINATOR column is in the loginId:Role format to prevent errors.", "answer": "Ensure that the COORDINATOR column is in the loginId:Role format to prevent errors."} +{"id": "TRAIN_Q198", "document": "IBM Security Bulletin: IBM API Connect is affected by Node.js tough-cookie module vulnerability to a denial of service (CVE-2016-1000232) - United States SECURITY BULLETIN\n\nSUMMARY\n API Connect has addressed the following vulnerability. \n\nNode.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources. \n\n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2016-1000232 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000232]\nDESCRIPTION:Node.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119038 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119038]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 \n\nAffected API Connect Affected Versions IBM API Connect 5.0.6.0-5.0.6.5 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0 REMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation / First Fix IBM API Connect\n\n5.0.0.0-5.0.6.5 5.0.6.6 LI79986 Addressed in IBM API Connect V5.0.6.6.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.5&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\n5.0.7.0-5.0.7.2 5.0.8.1 LI79986 Addressed in IBM API Connect V5.0.8.1.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] IBM API Connect\n\n5.0.8.0 5.0.8.1 LI79986 Addressed in IBM API Connect V5.0.8.1.\n\nFollow this link and find the \"APIConnect_Management\" package:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.0&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET 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 19 February 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.", "question": "Help with Security Bulletin: IBM API Connect is affected by Node.js tough-cookie module vulnerability to a denial of service (CVE-2016-1000232) I need to understand details regarding Security Bulletin: IBM API Connect is affected by Node.js tough-cookie module vulnerability to a denial of service (CVE-2016-1000232). Where can I find this information? ", "answer": "CVEID:CVE-2016-1000232 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000232]\nDESCRIPTION:Node.js tough-cookie module is vulnerable to a denial of service, caused by a regular expression error. By using a sufficiently large HTTP request Cookie header, a remote attacker could exploit this vulnerability to cause the application to consume an overly large amount of CPU resources.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/119038 [https://exchange.xforce.ibmcloud.com/vulnerabilities/119038]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 \n\nAffected API Connect Affected Versions IBM API Connect 5.0.6.0-5.0.6.5 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0"} +{"id": "TRAIN_Q199", "document": "IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]\n\nSee DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.\n\n\n[/support/docview.wss?uid=swg21397335&aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf] \n\nNote: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service. \n\nExample of a log entry: \n\n[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\" \n-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"\n-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"\n-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" \n-startType manual \n-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2] \n\nNotice: Some browsers are having trouble downloading this file and getting docview.wss instead. Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip). You can now access the utility. \nSee DeveloperWorks article for more information: \nThe Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html] \n\n\nSee TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services.", "question": "How to start PC DMgr as a Windows service? hi all. I just installed BPM 8.5.0.1 Process Center on a Windows 2008 R2 cloud server. The default BPM85 typical installation installs ProcessCenter Quickstart web page for starting the Dmgr and NodeMgr servers using the installation admin user . However, logout stops the services started by and attached to the admin user. I need to have this ProcessCenter (and Deployment Env Process SErvers) BPM85 DMgr / Node/ WASND started as a managed Windows managed service. I didn't see a Service Definition page to select run as Windows service. Can I possibly run BPMConfig -start dmgrprofile as a Windows service or is a profile update to my dmgr (hope not) needed to do this? ", "answer": "Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors."} +{"id": "TRAIN_Q201", "document": "IBM EJB WIMServiceHome cannot be found even after .ear file is installed successfully - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nThe ConfigEngine wp-add-property fails with the following error:\n\nCannot find EJB: ejb/com/ibm/websphere/wim/ejb/WIMServiceHome\n[wplc-add-property] javax.naming.ServiceUnavailableException: A communication failure occurred while attempting to obtain an initial context with the provider URL: \"corbaloc:iiop::\". \n\n\nCAUSE\nIn a cluster, the .ear file must be installed on the Deployment Manager (DMGR). For more information, refer to Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381]. If originally installed elsewhere, subsequent attempts to install it on the DMGR will appear to succeed but attempts to add properties (ConfigEngine task, wp-add-property) continue to fail with a \"Cannot find EJB\" message similar to the one above.\n\nENVIRONMENT\nClustered WebSphere Portal\n\nDIAGNOSING THE PROBLEM\n \n\n-- Confirm that any bootstrap address information in the URL is correct and that the target name server is running. A bootstrap address with no port specification defaults to port 2809. Possible causes other than an incorrect bootstrap address or unavailable name server include the network environment and workstation network configuration. [Root exception is org.omg.CORBA.TRANSIENT: java.net.UnknownHostException: :host=,port=9809 vmcid: IBM minor code: E02 completed: No]\n\n-- Check the results of the wp-la-install-ear file in the ConfigTrace.log to determine if the .ear file was already installed:\n\n\n * Command line arguments: ... wp-la-install-ear\n * \n * ...\n * \n * Target started: wp-la-install-ear\n * \n * \n * wp-la-install-ear:\n * \n * ...\n * \n * [wplc-create-ear]\n * \n * earfile=\"/prod/sys/Portal61/WebSphere/AppServer/systemApps/wim.ear/wimejb.jar\"\n * \n * [wplc-create-ear] null\n * [wsadmin] WASX7209I: Connected to process \"dmgr\" on node using SOAP connector; The type of process is: DeploymentManager \n [wsadmin] 'dmgr(cells//nodes//servers/dmgr|server.xml#Server_1)' \n [wsadmin] Enterprise application WIMSYSTEM already exists. \n ... \n * BUILD SUCCESSFUL\n\n\n-- Inspect the serverindex.xml files to confirm that the .ear file is installed on a non-DMGR node in the cluster: \n * \n * \n * \n * \n * ...\n * (contains no references to WIMSYSTEM.ear) \n \n * \n * WIMSYSTEM.ear/deployments/WIMSYSTEM\n\nRESOLVING THE PROBLEM\nYou must first uninstall the WIMSYSTEM enterprise application from the WebSphere_Portal server (using the WebSphere Administrative console). Then follow the steps in Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381] to install the .ear file on the DMGR.\n\nRELATED INFORMATION\n Incorrect providerURL causes wp-add-property failure [http://www.ibm.com/support/docview.wss?uid=swg21358381]", "question": "The config task wp-add-property is failing with \"Can not find EJB\" message while running on our Portal 8.5 cluster We are trying to perform the following steps on our Portal cluster...\n\nhttp://www.ibm.com/support/knowledgecenter/SSHRKX_8.5.0/mp/install/add_attributes.html\n\nWe successfully ran the wp-la-install-ear task but now when attempting to run the wp-add-property task we see the following error in the ConfigTrace.log....\n\n [wplc-add-property] [2016-10-11 15:57:32.065] Can not find EJB:\n ejb/com/ibm/websphere/wim/ejb/WIMServiceHome\n [wplc-add-property] javax.naming.NameNotFoundException: Context:\n dmgrCell01/nodes/dmgrNode01/servers/dmgr, name:\n ejb/com/ibm/websphere/wim/ejb/WIMServiceHome: First component in name\n websphere/wim/ejb/WIMServiceHome not found. [Root exception is\n org.omg.CosNaming.NamingContextPackage.NotFound:\n", "answer": "You must first uninstall the WIMSYSTEM enterprise application from the WebSphere_Portal server (using the WebSphere Administrative console). Then follow the steps in Document #1358381 [http://www.ibm.com/support/docview.wss?rs=899&uid=swg21358381] to install the .ear file on the DMGR."} +{"id": "TRAIN_Q202", "document": "IBM Finding if Table created as NOT LOGGED INITIALLY - United States TECHNOTE (FAQ)\n\nQUESTION\n How to find if Table was Created as NOT LOGGED INITIALLY? \n\nANSWER\nWe can use either of the following methods to Check if Table was created as 'Not Logged Initially'\n1)Using db2cat,\n\ndb2cat -db -n -s -t | grep \"Table not logged\"\nWhich can confirm if given table was created as NLI or not.\n\nSample Output \n----------------------\nConnecting to the Database.\nConnect to Database Successful.\nTable not logged : 0\n----------------------\nTable not Logged showing '0' represent Table was not created as NLI, if it returns '1' then that is table was created as NLI.\n\n2)Using db2look \nUsing db2look command to get DDL information on the table which would show you if \nthe table was created as \"NOT LOGGED INITIALLY\" \n\nExample: \ndb2look -d -t -e -o \n\nNOTE: Table Alter with ACTIVATE NOT LOGGED INITIALLY will not be listed in these above commands as it will activate NLI only for current Unit of work.\n\nNOTE:In DB2 V8 the LOG_ATTRIBUTE column in the SYSCAT.TABLES table was used to \ncheck if a table was created as NOT LOGGED INITIALLY.\nBut Starting from DB2 V9 this column is no longer being used and will always have a value of 0.\n\nRELATED INFORMATION\n NOT LOGGED INITIALLY [http://www.ibm.com/support/knowledgecenter/SSAE4W_7.1.0/com.ibm.etools.iseries.langref2.doc/rbafzmst484.htm]", "question": "How to find if Table was Created as NOT LOGGED INITIALLY? How to find if Table was Created as NOT LOGGED INITIALLY? ", "answer": "We can use either of the following methods to Check if Table was created as 'Not Logged Initially'\n1)Using db2cat,\n\ndb2cat -db -n -s -t | grep \"Table not logged\"\nWhich can confirm if given table was created as NLI or not.\n\nSample Output \n----------------------\nConnecting to the Database.\nConnect to Database Successful.\nTable not logged : 0\n----------------------\nTable not Logged showing '0' represent Table was not created as NLI, if it returns '1' then that is table was created as NLI.\n\n2)Using db2look \nUsing db2look command to get DDL information on the table which would show you if \nthe table was created as \"NOT LOGGED INITIALLY\" \n\nExample: \ndb2look -d -t -e -o "} +{"id": "TRAIN_Q203", "document": "IBM DataPower off-device logging: a configuration example - United States datapower; 7993; machine type 7993; logging; off device; off device logging; log target; off-device; syslog; debug log level; debug; log level TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote gives an example of how to enable off-device logging on an IBM® WebSphere® DataPower® appliance. This can be very helpful when a debug log level is needed to help isolate a problem or monitor behavior over a long period of time or can be used in production environment as DataPower only keeps a limited number of log files (the default is 3 files) in the file system in a rotational basis. \n\nCAUSE\nThe DataPower device has a finite amount of space to hold larger than average log files or long term logging needs in production environment. \n\nIt should be noted that if used while debugging at load or in a capacity issue, log events may be dropped. There is a prioritization of events within the device and client traffic always comes first. Log events dropped can be confirmed or counted from the Status>Log Targets menu in the WebGUI.\n\n\nRESOLVING THE PROBLEM\nConfigure a server daemon to listen and capture the DataPower devices events. First, this example shows how to create the log target sending events to a syslog destination. The other examples listed below will have their own strong points to be considered depending on the problem scenario. \n\n \n\nSyslog: \n\n* The syslog protocol operates over UDP which has no guarantee on packet delivery - a fast fire and forget method. \n\nTo create the new log target, go into the default domain: Objects > Log Targets \n\nConfigure the log target with settings as follows from the WebGUI: \n\n 1. Name the log target \n 2. Select Target Type of syslog \n 3. Fill in the Local Identifier with a descriptive string that may be used by a remote recipient to identify this specific log target \n 4. Enter the Remote Host Address and the Remote IP Port as in the screen shot wherex.x.x.x is the IP address of the remote syslog server that listens on port 514 \n 5. Take all other defaults\n\n\n\n[/support/docview.wss?uid=swg21269136&aid=1] [/support/docview.wss?uid=swg21269136&aid=1] \n\n \n\nUnder the Event Subscriptions tab, you can select all and debug as indicated here: \n\n\n[/support/docview.wss?uid=swg21269136&aid=2] [/support/docview.wss?uid=swg21269136&aid=2] \n\n * \n * 6. Generate log events in the DataPower by using some transactions, for example by saving the configuration from the WebGUI or running some test load into a domain.\n\n\nSyslog-ng, will simply work over the TCP protocol to ensure the packet is delivered to the destination. The same consideration should be applied to a device under high load in that a log event could be dropped if not able to be wrote out to the network within time. \n\n \n\nNFS:\nAll NFS limitations apply from file size and permission settings. This is a more common approach using an NFS static mount to capture a log target and can allow for slightly more reliable messages to be logged. The limiting factor again is the speed of the network and NFS server response time. \n\n \n\nFile type: \n\nUsing a file type log target with a backup method as seen here:\n[/support/docview.wss?uid=swg21269136&aid=3] [/support/docview.wss?uid=swg21269136&aid=3]\nThis will allow log events to quickly be written to a local file on the device's file system. Once the file reaches its set size a connection to the destination will upload the file from the device. This will upload with a unique time and date stamp on the uploaded file.\n\nThis is a useful method to capture sporadic problems. This is also useful for long running transactions that may span more than one file depending on device load.\n\n\nHTTP service:\nFinally a clever method that may be used in some senarios would be an HTTP service on the device.\nUsing an HTTP service configured in the following way,\n[/support/docview.wss?uid=swg21269136&aid=4] [/support/docview.wss?uid=swg21269136&aid=4] \n\nOnce the file type log is created in the logtemp:/// directory, a client browser or wget type client can easily retrieve the file from the device. \n\nThis is very useful when there is no local or accessible remote log storage location to the device, due to firewall or network restrictions. \n\nThis is also removing the limitation of the device dropping the log event should it not be able to write the log event to the network. \n\nEach of the above methods are very useful and work better in some scenarios than others depending on the network, load, problem, and information needed. This is intended to be a guide to help you decide which method would be best for your scenario.", "question": "Limitations of sylog-TCP log target using DataPower Gateways I am trying to configure a log target using type syslog-TCP. It seems that the payload is getting truncated when I try to record custom logs to it using log-action. How can I workaround it. ", "answer": "Configure a server daemon to listen and capture the DataPower devices events."} +{"id": "TRAIN_Q204", "document": "IBM Remote scanning freezes or stops with IBM Datacap Taskmaster Capture - United States hang scan ie8 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Remote scanning using scanner freezes or stops when using Internet Explorer 8 or later. \n\nSYMPTOM\nAdditional symptoms include: \n\n * The web page may crash and recover (close and quickly reopen). \n * The freeze may occur during or after scanning the first page.\n\n\nCAUSE\nInternet Explorer (IE) 8 and later includes its own version of Data Execution Prevention (DEP) which can cause the above symptoms and prevent scanning from running.\n\nENVIRONMENT\nInternet Explorer 8 and later\n\n\n\nRESOLVING THE PROBLEM\nTo disable DEP: \n\n 1. In the browser, open the Tools menu, and select Internet Options. \n 2. Select the Advanced tab. \n 3. Uncheck Enable memory protection to mitigate online attacks. \n 4. Close all windows, restart the browser and start scanning again.\n\n\nNote: If using Datacap 8.1, this issue has been fixed in 8.1 Fix Pack 1.", "question": "\"Internet Explorer has stopped working\" Hi,\n\nI am using scanning via web browser and I have my scanner connected to my computer. During the scanning process, Internet Explorer stops. This always happens. Has anyone encountered this yet? ", "answer": "Internet Explorer (IE) 8 and later includes its own version of Data Execution Prevention (DEP) which can cause the above symptoms and prevent scanning from running."} +{"id": "TRAIN_Q205", "document": "IBM The import task failed with \"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\" after patching BigFix/ILMT RedHat Linux server. - United States TECHNOTE (FAQ)\n\nQUESTION\n The import task failed with \"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\" after patching BigFix/ILMT RedHat Linux server. \n\nCAUSE\nTEMA version: 9.2.2.0-20151209-1636\nAfter patching BigFix/ILMT Redhat Linux server, the import task started to fail with the following error in the import log:\n\n[/support/docview.wss?uid=swg22004607&aid=1] [/support/docview.wss?uid=swg22004607&aid=1] \n\n\n\n\nThe following commands confirm the glibc library installed:\n\n\nrpm -qa | grep -i glibcd.\n\nglibc-2.12-1.192.el6.x86_64 \nglibc-headers-2.12-1.192.el6.x86_64 \ncompat-glibc-headers-2.5-46.2.x86_64 \ncompat-glibc-2.5-46.2.x86_64 \nglibc-devel-2.12-1.192.el6.x86_64 \nglibc-common-2.12-1.192.el6.x86_64 \nglibc-2.12-1.192.el6.i686 \n\n\nfind / -name glibc* \n/usr/share/man/overrides/ru/man7/glibc.7.gz /usr/share/man/man7/glibc.7.gz /usr/share/doc/glibc-2.12 /usr/share/doc/glibc-common-2.12 /usr/sbin/glibc_post_upgrade.x86_64 /usr/sbin/glibc_post_upgrade.i686 \n\nfind / -name getservbyname* \n/usr/share/man/man3p/getservbyname.3p.gz /usr/share/man/overrides/ru/man3/getservbyname.3.gz /usr/share/man/overrides/ru/man3/getservbyname_r.3.gz /usr/share/man/man3/getservbyname.3.gz /usr/share/man/man3/getservbyname_r.3.gz \n\nThe $PATH environment variable shows:\n\n\necho $PATH \n\n/usr/lib64/qt-3.3/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin \n\nEven re-installing the glibc 32-bit library rpm package again and rebooting the RedHat server as well, it won't resolve the issue.\n\nNote: same error will occur when modifying the datasource setting as well as described in the above technote link.\n\n\nANSWER\nThe problem is resolved after upgrading to ILMT 9.2.7 and the import task continues to work successfully. Most likely this is due to the ILMT 9.2.2 application expecting a specific version of glibc 32-bit library file and it won't work if a newer version is found after the patching the RedHat Linux server.\n\nRELATED INFORMATION\n#", "question": "INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException) Why the data import is failing with \"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\" after patching BigFix/ILMT RedHat Linux server ?", "answer": "Most likely this is due to the ILMT 9.2.2 application expecting a specific version of glibc 32-bit library file and it won't work if a newer version is found after the patching the RedHat Linux server."} +{"id": "TRAIN_Q206", "document": "IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM OS Images for Red Hat Linux Systems and AIX (CVE-2015-0410 and CVE-2014-6593) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition Version 6 and 7 that are used by IBM OS Images for Red Hat Linux Systems and AIX. These issues were disclosed as part of the IBM Java SDK updates in January 2015. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM OS Image for Red Hat Linux Systems 2.0.0.1 and earlier.\nIBM OS Image for AIX 2.0.0.1 and earlier.\n\nREMEDIATION/FIXES\nThe deployed Red Hat Linux-based and AIX virtual machines on IBM PureApplication Systems types are affected. The solution is to apply the following IBM PureApplication System fix to the deployed virtual machines.\n\nJava Update for Linux\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_Linux_2++&includeSupersedes=0]\n\nJava Update for AIX\nhttp://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0 [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=All&platform=All&function=fixId&fixids=+Java_Update_AIX_2++&includeSupersedes=0] \n\n\n\n 1. Import the fix into the Emergency Fix catalogue. \n 2. For deployed instances, apply this emergency fix on the VM. The IBM Java SDKwill be upgraded to IBM Java JDK 7.0 SR8 FP10 interim fix and IBM Java JDK 6.0 SR16 FP3 interim fix \n 3. Restart the deployed instance after the fix is applied.\n\n\nYou should verify applying this fix does not cause any compatibility issues. 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 v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \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\nNone \n\nCHANGE HISTORY\n 23 July 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.", "question": "Help with Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM OS Images for Red Hat Linux Systems and AIX (CVE-2015-0410 and CVE-2014-6593) I need to understand details regarding \"Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM OS Images for Red Hat Linux Systems and AIX (CVE-2015-0410 and CVE-2014-6593)\" Where can I find this information? ", "answer": "CVEID: CVE-2015-0410 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-0410]\nDESCRIPTION: An unspecified vulnerability related to the Security component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100151 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100151] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P) \n\nCVEID: CVE-2014-6593 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6593]\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/100153 [https://exchange.xforce.ibmcloud.com/vulnerabilities/100153] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:H/Au:N/C:P/I:P/A:N)"} +{"id": "TRAIN_Q207", "document": "IBM ITCAM Agent for WebSphere DataPower Applications: 7.1.0-TIV-ITM_WDP-FP0003 - United States DataPower; BN; KBN DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the enhancements listed in the \"Problems Fixed\"\nsection below. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2016.\n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager Agent for WebSphere DataPower Appliance\nVersion 7.1 Fix Pack 3\n\nComponent ID: 5724SOADP\n\nFix Pack: 3, 7.1.0-TIV-ITM_WDP-FP0003\n\nDate: Revised January 8, 2016\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\n1.0 General description\n=======================\nThis fix resolves the RFEs, APARs and defects listed in the \"Problems Fixed\"\nsection below. This fix also includes the superseded fixes listed in\nsection 2.6.\n\n2.0 Problems fixed\n==================\nThe following problems are addressed by this fix.\n\n2.1 APARs:\n----------\n\nN/A \n\n2.2 Defects\n--------------\n\nDefect: 61583\nAbstract: Increase java heap size and thread pool size.\nAdditional Information: In order to support monitoring more DPs per instance, we increased the maximum heap size from 512M to 1024M. And the thread pool size is changed from 5 to 10.\n\nTo enable the new maximum heap size, agent need to be restarted.\n\nTo enable the new thread pool size:\n1. Re-config the instances.\n2. Modify the agent's config file and restart the agent instances.\n--For UNIX/LINUX\nModify the file \"bn_.config\", change the item \"CDP_DP_THREAD_POOL_SIZE\" to \"10\".\n--For Windows\nModify the file \"KBNENV_\", change the item \"CDP_DP_THREAD_POOL_SIZE\" to \"10\".\n\n2.3 Enhancements:\n-----------------\nEnhancement: RFE: 68385 \nAbstract: AMEX - Additional DataPower monitoring capabilities to monitor new capabilities in V6/V7 of firmware\nAdditional Information: \nPriority 1- Link Aggregation - First available in V7 firmware. This is at the network layer. Can add monitoring for the network connections to ensure there are no failures in link aggregation.\nPriority 1- IMS Connect - Can monitor up/down connection monitoring in SNMP files.\nLower priority - On Demand Router - Load balancing for Websphere. Can add monitoring for the network connections and load balancing work its doing. \n\n4 new attribute groups were introduced in FP3.\n-IMS_Connect:\nIMSConnect, Domain, Requests, Responses, RequestErrors, ResponseErrors\n4 queries:\n--IMS Connect Status: Use the IMSConnect attributes to obtain information about IMS connect status on the monitored DataPower appliance.\n--IMS Connect Requests Top 10: Provides the top 10 requests IMS Connect.\n--IMS Connect Responses Top 10: Provides the top 10 responses IMS Connect.\n--IMS Connect Request Errors Top 10: Provides the top 10 request errors IMS Connect.\n--IMS Connect Response Errors Top 10: Provides the the top 10 response errors IMS Connect.\n\n-Link_Aggregation:\nIndex, Name, MgmtName, MTU, Mode, Status, Primary, Active, LACPHashPolicy, LACPDURate, LACPSelectionPolicy, LACPAggregatorID, LACPNumPorts, LACPActorKey, LACPPartnerKey, LACPPartnerMAC, MIIStatus\n3 queries:\n--Link Aggregation Status: Use the Link Aggregation Status attributes to obtain information about Link Aggregation Status on the monitored DataPower appliance.\n--Link Aggregation Status No-link: Provides all No-link status for Link Aggregation.\n--Link Aggregation MIIStatus No-link: Provides all No-link MIIStatus for Link Aggregation.\n\n-Link_Aggregation_Member_Status:\nAggregateIndex, AggregateName, MgmtName, MemberIndex, MemberName, AggregatorID\n1 query:\n--Link Aggregation Member Status: Use the Link Aggregation Member Status attributes to obtain information about Link Aggregation Member Status on the monitored DataPower appliance.\n\n-Load_Balancer:\nGroup, Domain, Server, Port, Health, Weight, AdminState\n3 queries:\n--Load Balancer Status: Use the Load Balancer Status attributes to obtain information about Load Balancer status on the monitored DataPower appliance.\n--Load Balancer Groups Down: Provides all Down status groups for Load Balancer.\n--Load Balancer Groups Softdown: Provides all Softdown status groups for Load Balancer. \n\nEnhancement: (internal) Remove the UE dependance\nAbstract: Remove the UE dependance\nAdditional Information: Details as below:\nax is upgraded to 06.30.04.00\ngs is upgraded to 08.00.50.20\njr is upgraded to 07.07.00.00\nui is upgraded to 06.30.04.00\n\n2.4 Superseded fixes\n-------------------------\nNone.\n\n\n2.5 APARs and defects included from superseded fixes\n----------------------------------------------------\nNone.\n\n\n3.0 Architecture and prerequisites\n=================================\nSupported operating systems are shown in the system requirements reports \nfor the DataPower agent. You can access these reports here:\n\n- Prerequisites topic in Knowledge Center:\nhttp://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/prerequisites/apps721_systemreqs.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1/com.ibm.itcama.doc_7.2.1/prerequisites/apps721_systemreqs.html]\n\n- Software Product Compatibility Reports (SPCR)\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--------------------------------\nThere is no prerequisite level for this fix.\n\nBecause this fix is cumulative, it can be installed on any fix level \nfor the version, release, and modification level above the prerequisite. \n\n\n4.0 Image directory contents\n============================\nPhysical Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CBNR3ML\nElectronic Part Number: ITCAM Apps Agent for WebSphere DataPower Appliance CN8KBML\n\n5.0 Installation instructions\n=============================\nWhen this fix pack image is downloaded from the IBM Software Support website, \nthese rules apply:\n* You can install the fix pack only locally on a system that hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases already. Similar to other \nupgrade software, you can install the fix pack image locally on a \ncomputer where the product software is not already installed.\n* You can populate agents to the depot.\n* You can deploy agents remotely to existing or new installations.\n\nWhen this fix pack image is downloaded from Passport Advantage, these rules \napply:\n* You can install the fix pack locally on a system that hosts a \nlicensed copy of IBM Tivoli Monitoring for Databases already.\n* You can install the fix pack locally on a system that does not host \na licensed copy of IBM Tivoli Monitoring for Databases already.\n* You can populate agents to the depot.\n* You can deploy agents remotely 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 upgrading.\n\n- For the purpose of this README, the symbol 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 customize the Extended Monitoring Agent for WebSphere DataPower Appliance \nbn.ini file on a UNIX system, back up this file before installing the fix. \nAfter this fix is installed, edit the latest bn.ini file and merge \nyour modifications into this bn.ini file.\n\n\n5.2 Local agent install and update (including silent installation)\n--------------------------------------------------------------\n1. Transfer the appropriate archive file to a \ntemporary directory on the system that contains the agent code to be \nupdated. For the purpose of this README, the symbol represents \nthe fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n2. Expand the archive file by using the tar command on UNIX systems or \nan unzip utility on Windows systems. This expansion creates a directory \nstructure that contains fixes for all supported platforms.\n\n3. Use the procedures in the \"IBM Tivoli Monitoring, Version 6.3 FP3\nInstallation and Setup Guide\" to install the agent.\n\n4. Use the procedures in the specific monitoring agent user's\nguide to complete the installation and configuration.\n\n\n5.3 Remote agent update and installation\n----------------------------------------\n1. Make sure that all potential targets of the remote deployment are\nrunning version 6.2.3 Fix Pack 4 or later of the OS monitoring \nagent.\n2. Transfer the appropriate archive file to \na temporary directory on the Tivoli Enterprise \nMonitoring Server system. For the purpose of this README, the \n symbol represents the fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n3. Expand the archive file by using the tar command on UNIX systems or an \nunzip utility on Windows systems. This expansion creates a directory structure\nthat contains fixes for all supported operating systems.\n\n4. To add the fix pack bundles to the remote deployment depot, use the\ntacmd addBundles command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\nabout the tacmd addBundles command, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: if the fix was expanded to \n/:\n> $CANDLEHOME/bin/tacmd addBundles -i //WINDOWS/Deploy -t bn -f\n> $CANDLEHOME/bin/tacmd addBundles -i //unix -t bn -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, for example, bn \nrepresents the Extended Monitoring Agent for WebSphere DataPower Appliance\n-f shows that the actions are complete and confirmation is not requested\n\nOn a Windows system: if the fix was expanded to \n/:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\\\WINDOWS\\Deploy -t bn -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\\\unix -t bn -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, for example, bn \nrepresents the Extended Monitoring Agent for WebSphere DataPower Appliance\n-f shows that the actions are complete and confirmation is not requested\n\n5. To login 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 about the\ntacmd login and updateAgent commands, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: \n> $CANDLEHOME/bin/tacmd login -s \n-u \n-p \n\n> $CANDLEHOME/bin/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be installed/update. Use this value as the target of the\ntacmd addsystem/updateAgent command. \n\n> $CANDLEHOME/bin/tacmd addsystem -t bn \n-n \n-p \n\n> $CANDLEHOME/bin/tacmd updateAgent -t bn\n-n \n-v 071003000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 installed/updated. Use this value as the target of the\ntacmd addsystem/updateAgent command. \n\n> $CANDLEHOME%\\bin\\tacmd addsystem -t BN \n-n \n-p \n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t BN\n-n \n-v 071003000\nNote:\n- The component (-t) for the updateAgent command is specified as \ntwo characters (bn), not three characters (kbn).\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- The component (-p) for the addsystem command is for agent's configuration info.\nHere is an example:\nINSTANCE=\"value\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PORT=\"162\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_SECURITY_LEVEL=\"authPriv\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_USER_NAME=\"admin\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PROTOCOL=\"SHA\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_AUTH_PASSWORD=\"value\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PROTOCOL=\"DES\"\nKQZ_SNMPEVENT.KQZ_SNMPEVENT_PRIV_PASSWORD=\"value\"\nDPS:.SOAP_HOST=\"value\"\nDPS:.DP_PORT=\"5550\"\nDPS:.DP_UID=\"admin\"\nDPS:.DP_PASSWORD=\"value\"\nDPS:.KBN_LOG_FILE=\"value\"\nDPC:.SNMP_VERSION=\"snmpV2\"\nDPC:.SNMP_HOST=\"value\"\nDPC:.SNMP_PORT=\"161\"\nDPC:.SNMP_COMMUNITY=\"public\" \n\n- The following error might occur with the updateAgent command on \nLinux and UNIX endpoints; however, the agent is successfully \nupdated. This error does not occur on Windows endpoints.\n\nKUICUA011I: Updating the bn agents.\nKUICUA015E: The updateAgent command did not complete because an\nerror occurred. Refer to the following error\nreturned from the server:\n\nThe monitoring server encountered an error while updating the\nmanaged system type.\n\nThe kuiras1.log file might provide more information about \nthis error. If you require further assistance to resolve the \nerror, contact IBM Software Support.\n\nA timeout occurred while waiting for an agent task to complete on\n{node name}.\n\nThe agent task did not complete within the configured \ntime out period.\n\nVerify that the target system is online. Increase the \ntime out value and try the operation again.\n\n\n\n5.4 Agent support update\n------------------------\nFix 7.1.0-TIV-ITM_WDP-FP0003 included changes to the agent\nsupport files that must be installed. If you installed these updates already, there are no additional installation\nsteps. Otherwise, use the following steps to update the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, or\nTivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file \nto the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli\nEnterprise Portal Servers, or Tivoli Enterprise Portal desktops. \n\n2. Expand the archive file by using the tar command on UNIX systems or an \nunzip utility on Windows systems. \n\n3. Use the procedures in the \"IBM Tivoli Monitoring, Version 6.3 FP3\nInstallation and Setup Guide.\"\n\n4. Use the procedures in the specific monitoring agent user's\nguide to complete the installation and configuration.\n\n5. If the Tivoli Enterprise Monitoring Server that is 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 Installation instructions for agent baroc file\n-----------------------------------------------------\nThere are no updates to the baroc files included in this fix or\nany of the superseded fixes. No additional installation steps are\nrequired.\n\n6.2 Additional information on new configuration item \"KBN_SOMA_PROTOCOL\"\n------------------------------------------------------------------------\nA new configuration item \"KBN_SOMA_PROTOCOL\" is introduced to support TLS.\nThe value should be SSL/TLSv1/TLSv1.1/TLSv1.2. The default value is \"TLSv1\". \nIf you want to support TLSv1.1/TLSv1.2, please change it manually.\n\n1. For Windows platform:\nThe new item \"KBN_SOMA_PROTOCOL\" is in KBNENV and KBNENV_.\n\na. Agent instance must be restarted to enable the new configuration change.\nb. The vaule of \"KBN_SOMA_PROTOCOL\" in KBNENV_ will be updated to \nthe same vaule of \"KBN_SOMA_PROTOCOL\" in KBNENV while the instance is re-configured.\n\n2. For Linux/Unix platform:\nThe new items \"KBN_SOMA_PROTOCOL\" is in bn.ini and bn_.config.\n\na. Agent instance must be restarted to enable the new configuration change.\nb. The vaule of \"KBN_SOMA_PROTOCOL\" in bn_.config will be updated to \nthe same vaule of \"KBN_SOMA_PROTOCOL\" in bn.ini while the instance is re-configured.\n\n6.3 Verifying the update\n----------------------------\n1. To verify that the agent was updated correctly, use the tacmd command\nto view the current version of the agent after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer before 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 \n-u \n-p \n> $CANDLEHOME/bin/tacmd listSystems -t or\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 \n-u \n-p \n> %CANDLE_HOME%\\bin\\tacmd listSystems -t bn\n\nNote: The component (-t) for the tacmd listSystems command is\nspecified as two characters (bn), not three characters (kbn).\n\nWhen the agent update is successful, the agent version is:\n07.10.03.00\n\nAfter the agent is restarted, you can also use the GUI to verify\nthat the agent was successfully updated.\n\nFor the agent on Windows systems, the version number is\n07.10.03.00.\nFor the agent on UNIX systems, the version number is\n07.10.03.00.\n\n2. To verify that the agent support files were updated correctly, use the\nkincinfo command on Windows systems or the cinfo command on\nLinux or UNIX systems. The sample output below shows the versions\nof the Tivoli Enterprise Portal Server, Tivoli Enterprise\nMonitoring Server, or Tivoli Enterprise Portal Desktop systems\nafter this fix has been successfully applied.\n\nNote: The date shown for the build might not be accurate. This\nis a 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\n*********** Fri Mar 18 13:23:02 CST 2011 ******************\nUser: root Groups: root bin daemon sys adm disk wheel\nHost name : myaixsys Installer Lvl:06.30.04.00\nCandleHome: /opt/IBM/ITM\n***********************************************************\n...Product inventory\n.\n.\n.\nMonitoring Agent for WebSphere DataPower Appliance update:\n\nbn ITCAM Agent for WebSphere DataPower Appliance\nlx8266 Version: 07.10.03.00\n\n\n.\n.\n.\nTivoli Enterprise Monitoring Server update:\n\nbn ITCAM Agent for WebSphere DataPower Appliance\ntms Version: 07.10.03.00\n\n.\n.\n.\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\n\nkincinfo output:\n\n*********** Wednesday, January 8, 2014 3:46:34 PM ***********\nUser : Administrator Group : NA\nHost Name : IBM-8B96EE78239 Installer : Ver: 063004000\nCandleHome : C:\\IBM\\ITM\nInstallitm : C:\\IBM\\ITM\\InstallITM\n*************************************************************\n...Product Inventory\n\n.\n.\n.\n[ Tivoli Enterprise Monitoring Server |\nTivoli Enterprise Portal Server and Tivoli Enterprise Portal Desktop] update:\nBN DataPower Agent Support\nWINNT Version: 07.10.03.00 Build: \n\nTivoli Enterprise Portal Server and Tivoli Enterprise Portal\nDesktop update:\n\n\nBN DataPower Agent Support\nWINNT Version: 07.10.03.00 Build: \n\n\nITCAM Agent for WebSphere DataPower Appliance update:\nBN ITCAM Agent for WebSphere DataPower Appliance\nWINNT Version: 07.10.03.00 Build: \n\nNote:\n\n- The date of the build that is shown might not be accurate. This\nproblem is known and is being addressed.\n- The kincinfo and cinfo command output examples in the sections\nthat follow show all components that you can update. If you install only \nsome of these components then only the components that you install are \nshown in the output of these commands.\n\n\n7.0 Known problems and workarounds\n==================================\nNone.\n\n8.0 Additional product information\n=================================\nNone.\n\n9.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 information\non the products and services currently available in your area. Any reference to an\nIBM product, program, or service is not intended to state or imply that only that\nIBM product, program, or service may be used. Any functionally equivalent product,\nprogram, or service that does not infringe any IBM intellectual property right may\nbe used instead. However, it is the user's responsibility to evaluate and verify\nthe operation of any non-IBM product, program, or service.\n\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:\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 or any other\ncountry where such provisions are inconsistent with 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 in\ncertain transactions, therefore, this statement may not apply to 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\nDOWNLOAD PACKAGE\n\n\n\nHOW CRITICAL IS THIS FIX?\nRFE:68385\n\n\n\nPROBLEMS SOLVED\nIntroduce new attribute groups:IMS_Connect, Link_Aggregation, Link_Aggregation_Member_Status and Load_Balancer.\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.1.0.0-TIV-ITM_WDP-FP0003 8 Jan 2016 English 1717046972 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=7.1.0.0-TIV-ITM_WDP-FP0003&source=SAR] [ ]", "question": "How to configure the Data Power Agent to communicate on TLSv1.2 ? APM agent for data power is not able to communicate with data power server when SSL is enabled. Since we are connecting to TLS version 1, where data power server supports only TLS 1.2. ", "answer": "A new configuration item \"KBN_SOMA_PROTOCOL\" is introduced to support TLS.\nThe value should be SSL/TLSv1/TLSv1.1/TLSv1.2. The default value is \"TLSv1\". \nIf you want to support TLSv1.1/TLSv1.2, please change it manually."} +{"id": "TRAIN_Q208", "document": "IBM Developer for z Systems and Rational Developer for z Systems Backward/Forward compatibility - United States RDz; compatible; backward; forward; IDz; Debug Tool: Debugger TECHNOTE (FAQ)\n\nQUESTION\n What levels of the IBM Developer for z Systems and Rational Developer for z Systems host and client are compatible? \n\nANSWER\nClient/Server Compatibility\n\n\n\nIn general, IBM Developer for z Systems, Rational Developer for z Systems and Rational Developer for System z follow a two level backward and forward compatibility tolerance for basic Client /Server functionality. \n\nIBM Developer for z Systems v14.1.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host and Rational Developer for z Systems v9.5.x client/host. \n\nIBM Developer for z Systems v14.0.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1.x client/host. \n\nRational Developer for z Systems v9.5.x host/client is compatible with IBM Developer for z Systems v14.1.x client/host, IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1.x, and v9.0.x client/host. \n\nRational Developer for System z v9.1.x host/client is compatible with IBM Developer for z Systems v14.0.x client/host, Rational Developer for z Systems v9.5.x client/host and Rational Developer for System z v9.1, v9.0.x, and v8.5.x client/host. \n\nRational Developer for System z v9.0.x host/client is compatible with versions v9.5.x, v9.1.x, v9.0.x, v8.5.x and v8.0.x client/host. \n\nRational Developer for System z v8.5.x host/client is compatible with versions v9.1, v9.0, v8.5, v8.0.x, and v7.6.x client/host. \n\nBasic Client/Server functionality includes: \n• Connecting to a z/OS System \n• Allocating z/OS Data sets \n• Creating a z/OS Project \n• Working with z/OS COBOL & Pl/I remote assets – edit, syntax check, submit, execute, debug and view the output \n• Basic CARMA functionality \n• Compatibility between service levels within a release is also supported (for example, using the v9.5 client to access a v9.5.1 server). \n\nAs an example, if you upgrade your Developer for z Systems host to 14.0.x, client versions v9.1.x, v9.5.x, v14.0 and v14.1.x are compatible with the 14.0.x server. \n\nLikewise, if you upgrade your Developer for z Systems client to 14.0.x, server versions v9.1.x, v9.5.x, v14.0.x and v14.1.x are compatible with the 14.0.x client. \n\nNote: Server enhancements that are client-dependent are not available to developers using earlier versions of the client. \n\nClient enhancements that are server-dependent are not available to developers accessing earlier versions of the server. \n\nFor Debugger, \n\n[/support/docview.wss?uid=swg21568844&aid=1] \nDeveloper for System z v9.0.1.x (host) \nDeveloper for System z v9.1.x (host) \nDeveloper for System z v9.5.x (host) \nDeveloper for z Systems v14.0.x (host) \nDeveloper for z Systems v14.1.x (host) \nDebug for z Systems v14.0.x (host) \nDebug for z Systems v14.1.x (host) Debug Tool v12 Debug Tool v13 \nDeveloper for System z v9.0.1.x (Client) X [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] [/support/docview.wss?uid=swg21568844&aid=1] X X \nDeveloper for System z v9.1.x (Client) X X X X X X X X X \nDeveloper for System z v9.5.x (Client) X X X X X X X [/support/docview.wss?uid=swg21568844&aid=1] X \nDeveloper for System z v14.0.x (Client) X(1) X(1) X X X X X X X \nDeveloper for System z v14.1.x (Client) X(1) X(1) X X X X X X X * (1) Launch configurations and JCL Generation not supported for these host versions.\n * \n * \n * \n * \n * \n * Workspace Data Compatibility\n * \n * \n * \n * \n * \n * \n *", "question": "Can I run different levels of the Rational Developer for z Systems host and client? I'd like to know if I can run different versions of the RDz client and host and if so what compatible or supported versions and releases?", "answer": "In general, IBM Developer for z Systems, Rational Developer for z Systems and Rational Developer for System z follow a two level backward and forward compatibility tolerance for basic Client /Server functionality."} +{"id": "TRAIN_Q209", "document": "IBM Reducing the size of Decision Warehouse trace when running scenario suites - United States TECHNOTE (FAQ)\n\nQUESTION\n When running a Decision Validation Service scenario suite in Rule Team Server can the optional trace be filtered to reduce its size ? \n\nANSWER\nIt is possible to customize the Decision Warehouse (DW) trace that is used by the Scenario Suite Provider (SSP) when a Decision Validation Service (DVS) scenario suite is executed in Rule Team Server. The customization can filter out information that is not necessary to keep in the DW. A sample implementation is provided that removes information about all the rules that are not fired, which helps keep the size of the trace small when there is a large number of rules in the ruleset and typically a much smaller number of rules actually fire. Also, only the DW persisted trace is smaller, the original larger trace is still used by DVS to perform the tests involved in the scenario suite. \n\nInstructions: \n\n 1. Unjar the attached jrules-ssptrace-src.jar to a local directory \n 2. Edit the file ./jrules-ssptrace/build.xml and modify the properties to reflect your environment setup ( in particular the jrules.home directory path, the sspInput and sspOutput file paths ) \n 3. Using a command line from the directory ./jrules-ssptrace execute: ant repackage-ssp \n 4. Deploy the customized SSP (available as the sspOutput file path) \n\n\njrules-ssptrace-src.jar [/support/docview.wss?uid=swg21438208&aid=2] [/support/docview.wss?uid=swg21438208&aid=1] \n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 8.5, 8.0.1, 8.0, 7.5", "question": "Out of memory error when executing simulation \n\nI am getting OutOfMemory error when running simulation from ODM 8.5.1 Decision Center.\n\nThe DVS Excel contains 50 scenarios and I am planning to submit a much larger number of scenario.\n\nI noted that each record of the EXECUTION_TRACES.FULL_EXECUTION_TRACE column of the Decision Server Decision Warehouse is several MB long.\n", "answer": "It is possible to customize the Decision Warehouse (DW) trace that is used by the Scenario Suite Provider (SSP) when a Decision Validation Service (DVS) scenario suite is executed in Rule Team Server. The customization can filter out information that is not necessary to keep in the DW. A sample implementation is provided that removes information about all the rules that are not fired, which helps keep the size of the trace small when there is a large number of rules in the ruleset and typically a much smaller number of rules actually fire."} +{"id": "TRAIN_Q210", "document": "IBM Wrap table column text in list tab - United States TPAEICD; wrap; table; col; length; line; feed TECHNOTE (FAQ)\n\nQUESTION\n How to wrap table column text in list tab? \n\nANSWER\nYou can wrap table column text according to number of characters by using property wraplength in the tablecol tag e.g.\n\n\n\nThis will wrap the text once it reaches 100 characters into a new line.\n\nRELATED INFORMATION\n How To Display More Characters of a Description Field [http://www-01.ibm.com/support/docview.wss?uid=swg21673316]", "question": "How to wrap table column text in list tab for a specific table? I would like to wrap the text of table column into new a line. ", "answer": "You can wrap table column text according to number of characters by using property wraplength in the tablecol tag"} +{"id": "TRAIN_Q212", "document": "IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on September 22 and 26, 2016 by the OpenSSL Project. OpenSSL is used by IBM MQ Advanced Message Security on the IBM i platform only. IBM MQ Advanced Message Security has addressed the applicable CVEs. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-2177 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2177]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the incorrect use of pointer arithmetic for heap-buffer boundary checks. By leveraging unexpected malloc behavior, a remote attacker could exploit this vulnerability to trigger an integer overflow and cause the application to crash.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113890 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H) \n\nCVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DSA implementation that allows the following of a non-constant time codepath for certain operations. An attacker could exploit this vulnerability using a cache-timing attack to recover the private DSA key.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8 \n\nMaintenance versions 8.0.0.0 through 8.0.0.5 are affected. \n\nIBM MQ V9 \n\n9.0.0.0 only\n\nREMEDIATION/FIXES\nIBM MQ V8 \n\nApply fixpack 8.0.0.6 [http://www-01.ibm.com/support/docview.wss?uid=swg21995100] \n\nIBM MQ V9 \n\nApply fixpack 9.0.0.1 [http://www-01.ibm.com/support/docview.wss?uid=swg27048059]\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 13 March 2017: Original version published\n24 May 2017: Details for 9.0.0.1 added \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\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg22000474]", "question": "Security Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2178) I need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2178). Where can I find this information?\n", "answer": "CVEID: CVE-2016-2178 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2178]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DSA implementation that allows the following of a non-constant time codepath for certain operations. An attacker could exploit this vulnerability using a cache-timing attack to recover the private DSA key.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/113889 [https://exchange.xforce.ibmcloud.com/vulnerabilities/113889] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)"} +{"id": "TRAIN_Q214", "document": "IBM Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM Dojo Toolkit is vulnerable to cross-site scripting and affects IBM Image Construction and Composition Tool. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]\n\nDESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99303 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99303] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Image Construction and Composition Tool v2.2.1.3 \nIBM Image Construction and Composition Tool v2.3.1.0 \nIBM Image Construction and Composition Tool v2.3.2.0\n\nREMEDIATION/FIXES\nThe solution is to apply the following IBM Image Construction and Composition Tool version fixes.\n\nUpgrade the IBM Image Construction and Composition Tool to the following fix levels or higher: \n\n\nFor IBM Image Construction and Composition Tool v2.2.1.3 * \n * \n * \n * \n * http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=1.1.0.5&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.2.1.3-28&includeSupersedes=0\n\n\nFor IBM Image Construction and Composition Tool v2.3.1.0 * \n * \n * \n * \n * http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.1.0-38&includeSupersedes=0\n\n\nFor IBM Image Construction and Composition Tool v2.3.2.0 * \n * \n * \n * http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=PureSystems&product=ibm/WebSphere/PureApplication+System&release=2.1.0.0&platform=All&function=fixId&fixids=ICCT_efix_Repository_2.3.2.0-12&includeSupersedes=0\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 v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \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\nNone \n\nCHANGE HISTORY\n 17 June 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.", "question": "Help with Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917) I need to understand details regarding \"Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917)\". Where can I find this information? ", "answer": "CVEID: CVE-2014-8917 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8917]\n\nDESCRIPTION: IBM Dojo Toolkit is vulnerable to cross-site scripting, caused by improper validation of user-supplied input.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/99303 [https://exchange.xforce.ibmcloud.com/vulnerabilities/99303] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:N/I:P/A:N)"} +{"id": "TRAIN_Q215", "document": "IBM Security Bulletin: A security vulnerability has been identified in IBM Tivoli Network Manager IP Edition shipped with WebSphere Application Server (CVE-2017-1194) - United States SECURITY BULLETIN\n\nSUMMARY\n WebSphere Application Server is shipped with IBM Tivoli Network Manager IP Edition. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nPlease consult the security bulletin Cross-site request forgery in WebSphere Application Server (CVE-2017-1194) [http://www-01.ibm.com/support/docview.wss?uid=swg22001226] for vulnerability details and information about fixes.\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Tivoli Network Manager 3.9, 4.1, 4.1.1 and 4.2\n\nREMEDIATION/FIXES\nRefer to the following security bulletins for vulnerability details and information about fixes addressed by WebSphere Application Server which is shipped with Network Manager IP Edition. \n\nPrincipal Product and Version(s) Affected Supporting Product and Version IBM Tivoli Network Manager 3.9 Fixpack 1 - Fixpack 5 Bundled the TIP version 2.1.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.1 Bundled the TIP version 2.2.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.1.1 FixPack 1 - Fixpack 2 Bundled the TIP version 2.2.0.x, which bundles IBM WebSphere version 7.0.0.x. IBM Tivoli Network Manager 4.2.0 - Fix Pack 1 - Fixpack 3. IBM Tivoli Network Manager 4.2 requires to install IBM Websphere Application Server Version 8.5.5.5 or later version separately. Users are recommended to apply IBM WebSphere version 8.5.5.5 Security Interim Fixes.. \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 4 May 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.", "question": "Is ITNM exposed to vulnerability CVE-2017-1194?. Is ITNM versions are affected by vulnerability CVE-2017-1194, because ITNM does shipped with WebSphere Application Server, where I can find the details?. ", "answer": "Please consult the security bulletin Cross-site request forgery in WebSphere Application Server (CVE-2017-1194) [http://www-01.ibm.com/support/docview.wss?uid=swg22001226] for vulnerability details and information about fixes."} +{"id": "TRAIN_Q216", "document": "IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805) - United States SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-7805 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805]\nDESCRIPTION:Network Security Services could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free in TLS 1.2 generating handshake hashes. By persuading a victim 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/132749 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132749]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.7\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.8 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=8.0.0.8]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply Continuous Delivery Release 9.0.4 [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~WebSphere&product=ibm/WebSphere/IBM+MQ+Appliance+M2000&function=textSearch&text=9.0.4]\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 12 December 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.", "question": "Help with Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805) I need to understand details regarding Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805). Where can I find this information?", "answer": "CVEID:CVE-2017-7805 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7805]\nDESCRIPTION:Network Security Services could allow a remote attacker to execute arbitrary code on the system, caused by a use-after-free in TLS 1.2 generating handshake hashes. By persuading a victim 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/132749 [https://exchange.xforce.ibmcloud.com/vulnerabilities/132749]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)"} +{"id": "TRAIN_Q217", "document": "IBM Locating ITM Workspace Application Support Files for z/OS Agents - United States AppSupport OMEGAMON application support 350 360 410 420 610 601 700 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote addresses the commonly asked question of where can workspace application support files be found for z/OS Agents. \n\nRESOLVING THE PROBLEM\nBefore you can view data collected by monitoring agents, you must install application support for the agents on the Tivoli Enterprise Portal Server and on the hub Tivoli Enterprise Monitoring Server. When you install application support on the Tivoli Enterprise Portal Server, you are installing the files required for presenting workspaces and online help for each monitoring agent. When you install application support on the hub monitoring server, you are installing the files required for product-provided situations, situation distributions, and other product-specific data. Installing application support on the hub monitoring server is also known as \"seeding\" the hub.\nMost z/OS-based agents provide application support files on CDs or DVDs, which are separate from the mainframe installation media. Distributed agents include their application support files in the distributed installation process. Each CD /DVD that contains application support files is listed below, with information about which products use the CD /DVD and where the CD / DVD can be found. The latest level in fulfillment is the CD /DVD on this list. Where possible, IBM provides both .zip and .tar formats, as well as .iso format, so that a physical CD / DVD can be created.\n\nPlease note that the IBM Tivoli Monitoring (ITM) media is separate from the workspace application support files which are included with products that run in the ITM environment. ITM can be obtained by ordering either 5724-C04 IBM Tivoli Monitoring through Passport Advantage or the no charge 5698-A79 IBM Tivoli Management Services on z/OS through Shop zSeries. Your IBM rep can ask Techline to configure and submit the order as well. 5698-A79 includes the server, engine, and configurator on z/OS. Workspace application support files may have their own fixpacks which are separate and distinct from any ITM fixpacks. Fixpacks can be found on the product support urls at: \nhttp://www-306.ibm.com/software/support/index_A_Z.html [http://www-306.ibm.com/software/support/index_A_Z.html].\n\nThe ITM Configuration Guide describes the application support installation process. It can be found online in the ITM information center at: https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/agent_support.htm [https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0/com.ibm.itm.doc_6.3/install/agent_support.htm]. A useful reference for this activity is a technote that lists all of the ITM product code. It can be found at:\nhttp://www.ibm.com/support/docview.wss?uid=swg21265222 [http://www-01.ibm.com/support/docview.wss?uid=swg21265222]. \n\n \n\nThe LCD7-5139-11 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-5139-11.zip] IBM Tivoli OMEGAMON Application Support Files for z/OS is the latest level available of the application support DVD for the OMEGAMON V5.5.0 products to be installed with IBM Tivoli Monitoring V6.3.0 Fix Pack 2 or higher. This DVD contains application support files for the following products: \n\n * IBM OMEGAMON XE on z/OS, version 5.5.0 \n * IBM OMEGAMON XE for CICS on z/OS, version 5.5.0 \n * IBM OMEGAMON XE for Networks, version 5.5.0 \n * IBM OMEGAMON XE for IMS on z/OS, version 5.5.0 \n * IBM OMEGAMON Dashboard Edition on z/OS, version 5.5.0 \n * IBM OMEGAMON XE for Storage on z/OS, version 5.4.0 \n * IBM OMEGAMON for JVM on z/OS, version 5.4.0 \n * IBM Tivoli OMEGAMON XE for DB2® Performance Expert on z/OS, version 5.4.0 \n * IBM Tivoli OMEGAMON XE for DB2® Performance Monitor on z/OS, version 5.4.0 \n * IBM DB2 Query Monitor, version 3.2.0 \n\nThe DVD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \nThe publications for the above products can be found at: [http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/index.jsp]http://www.ibm.com/support/knowledgecenter/SSAUBV/welcome [http://www-01.ibm.com/support/knowledgecenter/SSAUBV/welcome]\n\nThe language support DVD can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-5138-10.zip [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-5138-10.zip]\n\n\nThe LCD7-2600-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-2600-02.zip] IBM Tivoli OMEGAMON Data Files for z/OS is the latest level available of the application support DVD for the OMEGAMON XE for DB2 V5.4.0 product. This DVD contains application support files for the following products: \n\n * IBM Tivoli OMEGAMON XE for DB2® Performance Expert on z/OS, version 5.4.0 \n * IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, version 5.4.0 \n\nThe DVD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\nThe language support DVD for OMEGAMON XE for DB2® V5.4.0 can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD8-2746-00.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD8-2746-00.tar] \n\nThe LCD7-2600-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-2600-00.tar] IBM Tivoli OMEGAMON Data Files for z/OS is the latest level available of the application support DVD for the OMEGAMON XE for DB2 V5.1.0 product. This DVD contains application support files for the following products: \n\n * IBM Tivoli OMEGAMON XE for DB2® Performance Expert on z/OS, version 5.1.0 \n * IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, version 5.1.0 \n\nThe DVD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\nThe language support DVD for OMEGAMON XE for DB2® V5.1.0 can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-2597-00.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-2597-00.tar] \n\nThe LCD7-3580-09 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3580-09.tar] IBM Tivoli OMEGAMON Data Files for z/OS is the latest level available of the application support DVD for the OMEGAMON XE V4.2 products. This DVD contains application support files for the following products: \n\n * IBM Tivoli OMEGAMON XE for IMS ™ on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON XE for Storage on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON XE for CICS® on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON XE on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON XE for Mainframe Networks, version 4.2 \n * IBM Tivoli OMEGAMON for z/OS Management Suite, version 4.2 \n * IBM Tivoli OMEGAMON XE for DB2® Performance Expert on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, version 4.2 \n * IBM Tivoli OMEGAMON DE on z/OS, versions 3.1 and 4.2 (OMEGAVIEW II for the Enterprise component HKWO310), you will need to install the 4.2 support as 3.1 will not be displayed, the 3.1 support can be found on LCD7-0817-03 \n\nThe DVD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\nThe language pack DVD can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3583-05.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3583-04.tar] \n\n\nThe LCD7-3513-09 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3513-09.zip] IBM Tivoli OMEGAMON XE for Messaging V7.5.0 Data Files for z/OS DVD is the latest level available for application support. This DVD contains application support files for the following product: * IBM Tivoli OMEGAMON XE for Messaging, version 7.5.0 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. Publications for Tivoli OMEGAMON XE for Messaging V7.5.0 can be found at:\nhttp://www.ibm.com/support/knowledgecenter/SSRLD6_7.5.0/welcome_omxe_msg750.html?lang=en [http://www.ibm.com/support/knowledgecenter/SSRLD6_7.3.0/welcome_omxe_msg730.html?lang=en]\n\nThe language support DVD for Messaging V7.5.0 can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar]\n\nThe LCD7-3513-08 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3513-08.zip] IBM Tivoli OMEGAMON XE for Messaging V7.3.0 Data Files for z/OS DVD is the latest level available for application support. This DVD contains application support files for the following product: \n\n * IBM Tivoli OMEGAMON XE for Messaging, version 7.3.0 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. Publications for Tivoli OMEGAMON XE for Messaging V7.3.0 can be found at:\nhttp://www.ibm.com/support/knowledgecenter/SSRLD6_7.3.0/welcome_omxe_msg730.html?lang=en [http://www.ibm.com/support/knowledgecenter/SSRLD6_7.3.0/welcome_omxe_msg730.html?lang=en]\n\nThe language support DVD for Messaging V7.1.0 can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar]\n\nThe LCD7-3513-07 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3513-07.zip] IBM Tivoli OMEGAMON XE for Messaging V7.1.0 Data Files for z/OS DVD is the latest level available for application support. This DVD contains application support files for the following product: \n\n * IBM Tivoli OMEGAMON XE for Messaging, version 7.1.0 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. Publications for Tivoli OMEGAMON XE for Messaging V7.1.0 can be found at:\nhttp://www.ibm.com/support/knowledgecenter/SSRLD6_7.1.0/welcome_omxe_msg710.html?lang=en [https://www.ibm.com/support/knowledgecenter/en/SSRLD6_7.1.0/com.ibm.omegamon.mes_doc_7.1/welcome.htm]\n\nThe language support DVD for Messaging V7.1.0 can be found at the following url: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-3514-05.tar]\n\n[ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3957-00.zip]IBM Tivoli System Automation uses several different CD numbers for application support. Version 3.5.0 is the latest level available of the application support CD. All of the application support file CDs are listed below by version / release: \n\n * IBM Tivoli System Automation for z/OS V3.5.0 uses CD LCD7-5153-04 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-5153-04.zip] \n * IBM Tivoli System Automation for z/OS V3.4.0 uses CD LCD7-5153-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-5153-01.zip] \n * IBM Tivoli System Automation for z/OS V3.3.0 uses CD LCD7-3957-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3957-00.zip] \n * IBM Tivoli System Automation for z/OS V3.2.0 uses CD LCD7-1451-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1451-01.zip] \n * IBM Tivoli System Automation for z/OS V3.1.0 uses CD LCD7-1451-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1451-01.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \nThe language support CD can be found at: \nftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-5154-01.zip [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/langsupt/LCD7-5154-01.zip] \nThe publications for Tivoli System Automation for z/OS can be found at: \nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+System+Automation+for+zOS [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+System+Automation+for+zOS]. \n\n\nThe LCD7-1390-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1390-01.tar] IBM Tivoli NetView for z/OS Enterprise Management Agent Application Support DVD is the latest DVD available for application support for NetView for z/OS V5.4. This CD contains application support files for the following product: * IBM Tivoli NetView for z/OS V5.4.0 \n\nThe DVDs can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \nThe publications for Tivoli NetView for z/OS can be found at: \nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itnetviewforzos.doc/toc.xml [http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itnetviewforzos.doc/toc.xml]. \n\n\nThe [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-4912-00.tar] LCD7-4912-03 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-4912-03.zip] IBM Tivoli NetView for z/OS Enterprise Management Agent Application Support DVD is the latest DVD available for application support for NetView for z/OS V6.2. This CD contains application support files for the following product: * IBM Tivoli NetView for z/OS V6.2.0 \n\nThe DVDs can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \nThe publications for Tivoli NetView for z/OS can be found at: \nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.itnetviewforzos.doc/ic-homepage.html [http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?topic=/com.ibm.itnetviewforzos.doc/ic-homepage.html]. \nThe agent for IBM Tivoli OMEGAMON XE on z/VM and Linux 4.1.2 does not install onto z/VM but onto Linux on zSeries, so it is a non-z/OS agent and uses a different approach by providing application support files as part of the Linux on zSeries installation. The CD that provides the application support files is: \n\n * LCD7-0982-10 IBM Tivoli OMEGAMON XE on z/VM and Linux Tivoli Enterprise Portal Agent \n\nBecause the application support files are included with the agent installation media, they cannot be put on a general access URL. If you do not find this CD in your product package, contact IBM Software Support or your IBM sales representative to get replacement media. Publications for Tivoli OMEGAMON XE on z/VM and Linux can be found at:\nhttp://www.ibm.com/support/knowledgecenter [http://www.ibm.com/support/knowledgecenter].\n\n\nThe LCD7-0980-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-0980-00.tar] IBM Tivoli Web Access for Information Management Workspace Enablement is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Web Access for Information Management, version 1.3 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Web Access for Information Management can be found at:\nhttp://publib.boulder.ibm.com/tividd/td/IBMTivoliWebAccessforInformationManagement1.3.html [http://publib.boulder.ibm.com/tividd/td/IBMTivoliWebAccessforInformationManagement1.3.html]. \n\n\nThe LCD7-1937-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1937-01.zip] IBM Tivoli Decision Support for z/OS Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Decision Support for z/OS, version 1.8.1 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Decision Support for z/OS can be found at:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.tivoli.dszos.doc/toc.xml [http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.tivoli.dszos.doc/toc.xml]. \n\n\nThe LCD7-3735-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-06.zip] IBM Tivoli Advanced Catalog Management for z/OS Application Support is the latest level available of the application support CD and pertains to V2.6 of the product. LCD7-1920-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1920-00.tar] IBM Tivoli Advanced Catalog Management for z/OS Application Support is the level to use for V2.1 of the product. These application support file CDs are available as follows: \n\n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.6 uses CD LCD7-3735-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-06.zip] \n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.5 uses CD LCD7-3735-04-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-04-02.zip] \n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.4 uses CD LCD7-3735-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-02.zip] \n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.3 uses CD LCD7-3735-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-01.zip] \n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.2 uses CD LCD7-3735-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3735-00.zip] \n * IBM Tivoli Advanced Catalog Management for z/OS, version 2.1 uses CD LCD7-1920-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1920-00.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Advanced Catalog Management for z/OS can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Catalog+Management+for+zOS [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Catalog+Management+for+zOS]. \n\n\nThe LCD7-3578-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-06.zip] IBM Tivoli Advanced Audit for DFSMShsm Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.6 uses CD LCD7-3578-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-06.zip] \n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.5 uses CD LCD7-3578-05-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-05-01.zip] \n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.4 uses CD LCD7-3578-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-02.zip] \n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.3 uses CD LCD7-3578-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-01.zip] \n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.2 uses CD LCD7-3578-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3578-00.zip] \n * IBM Tivoli Advanced Audit for DFSMShsm, version 2.1 uses CD LCD7-1921-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1921-00.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Advanced Audit for DFSMShsm can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Audit+for+DFSMShsm [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Audit+for+DFSMShsm]. \n\n\nThe LCD7-3736-05 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3736-05.zip] IBM Tivoli Advanced Allocation Management for z/OS Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Advanced Allocation Management for z/OS, version 3.3 uses CD LCD7-3736-05 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3736-05.zip] \n * IBM Tivoli Advanced Allocation Management for z/OS, version 3.2 uses CD LCD7-3736-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3736-01.zip] \n * IBM Tivoli Advanced Allocation Management for z/OS, version 3.1 uses CD LCD7-3736-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3736-00.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Advanced Allocation Management for z/OS can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Allocation+Manager+for+zOS [http://publib.boulder.ibm.com/tividd/td/IBMTivoliAdvancedAllocationManagerforzOS3.1.html]\n\nThe LCD7-1922-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1922-00.tar] IBM Tivoli Allocation Optimizer for z/OS Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Allocation Optimizer for z/OS, version 2.1 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Allocation Optimizer for z/OS can be found at:\nhttp://publib.boulder.ibm.com/tividd/td/IBMTivoliAllocationOptimizerforzOS2.1.html [http://publib.boulder.ibm.com/tividd/td/IBMTivoliAllocationOptimizerforzOS2.1.html]. \n\n\nThe LCD7-3579-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-06.zip] IBM Tivoli Advanced Reporting and Management for DFSMShsm Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.6 uses CD LCD7-3579-06 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-06.zip] \n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.5 uses CD LCD7-3579-05-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-05-01.zip] \n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.4 uses CD LCD7-3579-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-02.zip] \n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.3 uses CD LCD7-3579-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-01.zip] \n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.2 uses CD LCD7-3579-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3579-00.zip] \n * IBM Tivoli Advanced Reporting for DFSMShsm, version 2.1 uses CD LCD7-1955-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-1955-00.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Advanced Reporting for DFSMShsm can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Reporting+for+DFSMShsm [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Reporting+for+DFSMShsm].\n\n\nThe LCD7-3504-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3504-01.zip] IBM Tivoli Tape Optimizer on z/OS Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Tape Optimizer on z/OS, version 2.2 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\n\nThe LCD7-3503-05 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-05.zip] IBM Tivoli Advanced Backup and Recovery for z/OS Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: * IBM Tivoli Advanced Backup and Recovery, version 2.4 uses CD LCD7-3503-05 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-05.zip] \n * IBM Tivoli Advanced Backup and Recovery, version 2.3 uses CD LCD7-3503-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-02.zip] \n * IBM Tivoli Advanced Backup and Recovery, version 2.2 uses CD LCD7-3503-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-01.zip] \n * IBM Tivoli Advanced Backup and Recovery, version 2.1 uses CD LCD7-3503-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-00.zip] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Advanced Backup and Recovery for z/OS can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Backup+and+Recovery+for+zOS [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Advanced+Backup+and+Recovery+for+zOS].\n\n\nThe LCD7-3505-04 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3505-04.tar] IBM Tivoli Automated Tape Allocation Manager Application Support is the latest level available of the application support CD. This CD contains application support files for the following product: \n\n * IBM Tivoli Automated Tape Allocation Manager, version 3.3 uses CD [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-00.zip] LCD7-3505-04 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3505-04.tar] \n * IBM Tivoli Automated Tape Allocation Manager, version 3.2 uses CD [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-00.zip] LCD7-3505-01 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3505-01.tar] \n * IBM Tivoli Automated Tape Allocation Manager, version 3.1 uses CD [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3503-00.zip] LCD7-3505-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3505-00.tar] \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Automated Tape Allocation Manager can be found at:\nhttp://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Automated+Tape+Allocation+Manager+for+zOS [http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Automated+Tape+Allocation+Manager+for+zOS].\n\n\n\nThe LCD7-0817-03 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-0817-03.tar] IBM Tivoli Monitoring Services on z/OS v6.1 350/360 Workspace Migration is the latest level available of the application support CD. This CD contains application support files for products that were originally developed on OMEGAMON Platform V350 or V360, rather than on the ITM level of the common components (Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server and client). These application support files enable the following products to run with the ITM level of the common components. Note: if you are running one of the V3.1.0 OMEGAMONs with the V360 level of platform and not the ITM level, you will need to use CD number LCD7-0764-02 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-0764-02.zip]. If you are running the V350 level of platform, which was packaged with the legacy level of products, the CDs contain both platform and product so are not available on a general access url. The current CD levels are LCD7-0617-02 for Windows and LCD7-0618-02 for Unix. If you do not find these CDs in your product package, contact IBM Software Support or your IBM sales representative to get replacement media. \n\n\n * IBM Tivoli OMEGAMON DE on z/OS V4.2.0 (OMEGAVIEW II for the Enterprise component) \n * IBM Tivoli OMEGAMON XE on z/OS, version 3.1 \n and previous versions of IBM Tivoli OMEGAMON XE on z/OS components \n * IBM Tivoli OMEGAMON XE on z/OS, version 2.2.1 (same FMIDs as Sysplex, version 2.2.0) \n * IBM Tivoli OMEGAMON XE for Sysplex, version 2.2.0 \n * IBM Tivoli OMEGAMON XE for Cryptographic Coprocessors, version 1.0.0 \n * IBM Tivoli OMEGAMON XE for OS/390 Unix System Services, version 2.2.0 \n * IBM Tivoli OMEGAMON XE for CICS on z/OS, version 3.1 \n and previous versions of IBM Tivoli OMEGAMON XE for CICS \n * IBM Tivoli OMEGAMON XE for CICS on z/OS, version 2.2.1 (same FMIDs as CICSPlex, version 2.2.0) \n * IBM Tivoli OMEGAMON XE for CICSPlex, version 2.2.0 \n * IBM Tivoli OMEGAMON XE for CICS, version 1.0.0 \n * IBM Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS, version 3.1 \n * IBM Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS, version 3.1 \n * IBM Tivoli OMEGAMON XE for DB2 on z/OS, version 4.0.0 (same FMIDs as DB2 on z/OS, version 3.0.0) \n * IBM Tivoli OMEGAMON XE for DB2 on z/OS, version 3.0.0 \n * IBM Tivoli OMEGAMON XE for IMS on z/OS, version 3.1 \n and previous versions of IBM Tivoli OMEGAMON XE for IMS \n * IBM Tivoli OMEGAMON XE for IMS on z/OS, version 2.2.1 (same FMIDs as IMSPlex, version 2.2.0) \n * IBM Tivoli OMEGAMON XE for IMSPlex, version 2.2.0 \n * IBM Tivoli OMEGAMON XE for IMS, version 1.0.0 \n * IBM Tivoli OMEGAMON XE for Mainframe Networks, version 3.1 \n and previous versions of IBM Tivoli OMEGAMON XE for Mainframe Networks \n * IBM Tivoli OMEGAMON XE for Mainframe Networks, version 2.1.0 (same FMIDs as Mainframe Networks, version 1.0.0) \n * IBM Tivoli OMEGAMON XE for Mainframe Networks, version 1.0.0 \n * IBM Tivoli OMEGAMON XE for Storage on z/OS, version 3.1 \n and previous versions of IBM Tivoli OMEGAMON XE for Storage \n * IBM Tivoli OMEGAMON XE for Storage on z/OS, version 2.1.0 (same FMIDs as Storage, version 1.0.0) \n * IBM Tivoli OMEGAMON XE for Storage on z/OS, version 1.0.0 \n * IBM Tivoli OMEGAMON XE for WebSphere Application Server on z/OS, version 1.3.1 (same FMIDs as WebSphere Application Server, version 1.3.0) \n * IBM Tivoli OMEGAMON XE for WebSphere Application Server on z/OS, version 1.3.0 \n * IBM Tivoli OMEGAMON XE for Websphere Business Integration, version 1.1.0 \n * IBM Tivoli Alert Adapter for OMEGACENTER Gateway, version 1.5.0 which is part of both: \n * IBM Tivoli AF/OPERATOR on z/OS, version 3.4.1 and \n * IBM Tivoli OMEGACENTER Gateway on z/OS, version 3.4.1 \n * IBM Tivoli Alert Adapter for AF/Remote, version 1.0.1 which is part of the IBM Tivoli AF/Remote product \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\nIndividual files for each of the products above as well as workspace application support files for some of distributed products can be found at: \nhttps://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=tmdl [https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=tmdl]. The publications for the above products can be found at:\nhttp://publib.boulder.ibm.com/tividd/td/tdprodlist.html [http://publib.boulder.ibm.com/tividd/td/tdprodlist.html]. \n\n\nThe LCD7-3959-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3959-00.tar] IBM Tivoli Composite Application Manager for Application Diagnostics is the latest level available of the application support CD for V7.1.0. This is the follow on product to IBM Tivoli Composite Application Manager for WebSphere version 6. This CD contains application support files for the following product: \n\n * IBM Tivoli Composite Application Manager for Application Diagnostics, version 7.1 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. The publications for Tivoli Automated Tape Allocation Manager can be found at:\nhttp://publib.boulder.ibm.com/tividd/td/IBMTivoliAutomatedTapeAllocationManagerforzOS3.1.html [http://publib.boulder.ibm.com/tividd/td/IBMTivoliAutomatedTapeAllocationManagerforzOS3.1.html]. \n\n \n\n\nIBM Tivoli Composite Application Manager for WebSphere version 6.0.1 or 6.1.0, uses a different approach for providing application support files. Catalog and attribute (.cat and .atr) files are provided with the z/OS agent FMID, and SQL files are provided on the distributed agent media. The CDs that provide the SQL files for version 6.0.1 are: \n\n * LCD7-0872-00 IBM Tivoli Enterprise Management Agent Version 6.0: Linux \n * LCD7-0815-00 IBM Tivoli Enterprise Management Agent Version 6.0: Windows \n * LCD7-0871-00 IBM Tivoli Enterprise Management Agent Version 6.0: Unix \n\nThe CD's that provide the SQL files for version 6.1.0 are: * LCD7-0872-01 IBM Tivoli Enterprise Management Agent Version 6.0: Linux \n * LCD7-0815-01 IBM Tivoli Enterprise Management Agent Version 6.0: Windows \n * LCD7-0871-01 IBM Tivoli Enterprise Management Agent Version 6.0: Unix \n\nBecause the SQL files are on distributed agent media these cannot be put on a general access url. If you do not find them in your product package please contact IBM support or your IBM sales representative to get replacement media. \nThe publications for Tivoli Composite Application Manager for WebSphere can be found at:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml [http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itcamwas.doc/toc.xml]. \n\n\nThe LCD7-2956-00 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-2956-00.tar] IBM Tivoli Composite Application Manager for SOA Application Support is the latest level available of the application support DVD for IBM Tivoli Composite Application Manager for SOA version 7.1.0. This DVD contains application support files for the following product: \n\n * IBM Tivoli Composite Application Manager for SOA, version 7.1 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]. \n\nIBM Tivoli Composite Application Manager for SOA version 6.0.0 or 6.0.1, uses a different approach for providing workspace application support files. Catalog and attribute (.cat and .atr) files and SQL files are all provided on the distributed agent media. The CDs that provide the application support files for version 6.0.0 are: * LCD7-0850-00 IBM Tivoli Composite Application Manager for SOA V6.0: Windows \n * LCD7-0952-00 IBM Tivoli Composite Application Manager for SOA V6.0: Linux \n * LCD7-0953-00 IBM Tivoli Composite Application Manager for SOA V6.0: IBM Monitoring - Application Support \n\nThe CD's that provide the application support files for version 6.1.0 are: * LCD7-0850-02 IBM Tivoli Composite Application Manager for SOA - Windows \n * LCD7-0952-02 IBM Tivoli Composite Application Manager for SOA - Linux on Intel and AMD 64 \n * LCD7-1367-01 IBM Tivoli Composite Application Manager for SOA - Linux on zSeries, Linux on pSeries, Linux on iSeries \n * LCD7-1368-01 IBM Tivoli Composite Application Manager for SOA - UNIX (Solaris and AIX) \n\nBecause the workspace application support files are on distributed agent media these cannot be put on a general access url. If you do not find them in your product package please contact IBM support or your IBM sales representative to get replacement media. \nThe publications for Tivoli Composite Application Manager for SOA can be found at:\nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itcamsoa.doc/toc.xml [http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/index.jsp?toc=/com.ibm.itcamsoa.doc/toc.xml]. \n\nIf you have any questions or to request physical media you can send an e-mail to tivzos@us.ibm.com.\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli OMEGAMON XE for CICS on z/OS All Versions Systems and Asset Management Tivoli OMEGAMON XE for IMS on z/OS 4.2.0, 4.1.0, 5.1.0 Systems and Asset Management Tivoli OMEGAMON XE for CICS Transaction Gateway on z/OS 4.2.0, 5.1.0, 5.3.0 Systems and Asset Management Tivoli OMEGAMON XE for Mainframe Networks 4.2.0, 5.1.0 Storage Management Tivoli OMEGAMON XE for Storage on z/OS 4.2.0, 5.1.0, 5.3.0 Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Expert on z/OS 4.2.0, 5.1.0, 5.2.0 Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Monitor on z/OS 5.1.0, 4.2.0, 5.2.0 Systems and Asset Management IBM OMEGAMON for CICS on z/OS z/OS 5.5.0 Systems and Asset Management IBM OMEGAMON for IMS on z/OS z/OS 5.5.0 Systems and Asset Management IBM OMEGAMON for JVM on z/OS z/OS 5.4.0 Systems and Asset Management IBM OMEGAMON for Messaging for z/OS z/OS 7.5.0 Systems and Asset Management IBM OMEGAMON for Networks on z/OS z/OS 5.5.0 Systems and Asset Management IBM OMEGAMON for z/OS z/OS 5.5.0 Systems and Asset Management IBM OMEGAMON Performance Management Suite for z/OS z/OS 5.5.0", "question": "Download link for application support for OMEGAMON for Messaging on z/OS V7.5 Where is download link for application support for IBM OMEGAMON for Messaging on z/OS V7.5.0 on ITM SLES zlinux servers? ", "answer": "The LCD7-3513-09 [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/LCD7-3513-09.zip] IBM Tivoli OMEGAMON XE for Messaging V7.5.0 Data Files for z/OS DVD is the latest level available for application support. This DVD contains application support files for the following product: * IBM Tivoli OMEGAMON XE for Messaging, version 7.5.0 \n\nThe CD can be found at the following url: ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/ [ftp://public.dhe.ibm.com/software/tivoli_support/misc/PandA/tools_agent/tools/appsupt/]."} +{"id": "TRAIN_Q219", "document": "IBM DB2 SQL error from Sterling B2B Integrator: SQLCODE: -1585, SQLSTATE: 54048 - United States STERLINGPRI TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This DB2 SQL error occurs with Sterling B2B Integrator: SQLCODE: -1585, SQLSTATE: 54048 \n\nSYMPTOM\ncom.sterlingcommerce.woodstock.profile.ProfileFinderException: listAllByEntityName: Finder Exception occurred: \n\nSQLState: 54048\nMessage: DB2 SQL error: SQLCODE: -1585, SQLSTATE: 54048, SQLERRMC: null\nVendor: -1585\n\n\nCAUSE\nThe DB2 instance did not have all 4 sizes of Temp tablespace defined.\nDBA had manually created the Temp tablespaces but only the 8k and 32k size.\n\n\nRESOLVING THE PROBLEM\nThe DB2 instance must have all 4 sizes of Temp tablespace created: 4k, 8k, 16k, and 32k. \n\nIn addition, these must be set as System Temp tablespaces, and not as User Temp tablespaces.\n\n \n\nHISTORICAL NUMBER\n PRI26178\nSCI94737", "question": "The configuration task database-transfer failed with DB2 SQL Error: SQLCODE=-1585, SQLSTATE=54048 While attempting to run the database-transfer task the following error is logged to the ConfigTrace.log:\naction-process-constraints: Fri Oct 10 13:20:34 CDT 2014 Target started: action-process-constraints [java] Executing java with empty input string [java] [10/10/14 13:20:35.877 CDT] Attempting to create a new Instance of com.ibm.db2.jcc.DB2Driver [java] [10/10/14 13:20:36.016 CDT] Instance of com.ibm.db2.jcc.DB2Driver created successfully [java] [10/10/14 13:20:36.016 CDT] Attempting to make connection using: jdbc:db2://:60500/:returnAlias=0; :: d2svc :: PASSWORD_REMOVED [java] [10/10/14 13:20:36.954 CDT] Connection successfully made [java] [10/10/14 13:20:37.073 CDT] ERROR: Error occurred gathering data from the source database [java] com.ibm.db2.jcc.am.SqlException: DB2 SQL Error: SQLCODE=-1585, SQLSTATE=54048, SQLERRMC=null, DRIVER=4.18.60 [java] at com.ibm.db2.jcc.am.kd.a(kd.java:752)", "answer": "The DB2 instance must have all 4 sizes of Temp tablespace created: 4k, 8k, 16k, and 32k. \n\nIn addition, these must be set as System Temp tablespaces, and not as User Temp tablespaces."} +{"id": "TRAIN_Q221", "document": "IBM What are the analyzer.db.updateMode parameter values for Case Foundation Case Analyzer? - United States performance TECHNOTE (FAQ)\n\nQUESTION\n What are the analyzer.db.updateMode parameter values for Case Foundation Case Analyzer? \n\nANSWER\nThe analyzer.db.updateMode parameter controls the JDBC update method used by Case Analyzer when updating tables in the Case Analyzer store SQL database. \n\nThe default value is CUSTOM_BATCH. That means that the JDBC driver will use the CUSTOM_BATCH update method for Case Analyzer queries. \n\nAnother possible value is BATCH. That means that the JDBC driver will use the BATCH update method for Case Analyzer queries. \n\nYou can set the BATCH value for the analyzer.db.updateMode parameter with the following query in the Case Analyzer store database: \n\n \n\n * UPDATE X_CAProperties SET PropValue='BATCH' \n WHERE PropName ='analyzer.db.updateMode' \n\n\nWhen to set the analyzer.db.updateMode = BATCH setting \n * IBM support may ask customer to set this setting to circumvent various performance-related symptoms and unexpected behavior. \n * In general, our experience is that the Microsoft JDBC drivers work better and are more stable with the analyzer.db.updateMode = BATCH setting.", "question": "Case Analyzer is not working \n\nCaseAnalyzer is not working, no latest audit log although service is running\n\nError in log:\n\n\"CAPublisher c2dce3b9 [Error] Unexpected exception occurred while processing task CAPublisher for store CASTORE.; Exception: com.microsoft.sqlserver.jdbc.SQLServerException: The query processor ran out of internal resources and could not produce a query plan. This is a rare event and only expected for extremely complex queries or queries that reference a very large number of tables or partitions. Please simplify the query. If you believe you have received this message in error, contact Customer Support Services for more information.\"", "answer": "You can set the BATCH value for the analyzer.db.updateMode parameter with the following query in the Case Analyzer store database: \n\n \n\n * UPDATE X_CAProperties SET PropValue='BATCH' \n WHERE PropName ='analyzer.db.updateMode'"} +{"id": "TRAIN_Q222", "document": "IBM Installing IBM Tivoli Directory Server Version 6.3 on RHEL 6 operating system - United States Tivoli Directory Server 6.3 on RHEL6; installing Tivoli Directory Server 6.3 on RHEL6 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes the points that you must consider when installing IBM Tivoli Directory Server Version 6.3 on Red Hat Enterprise Linux 6 (RHEL 6) operating system. \n\nRESOLVING THE PROBLEM\nFor a comprehensive list of the current recommended fix levels for IBM Tivoli Directory Server, see http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778 [http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778].\nUse this document to find the following information: \n\n * Prerequisites for installing Tivoli Directory Server 6.3 on RHEL 6 systems. \n * Instructions to install Tivoli Directory Server 6.3 and upgrade to Tivoli Directory Server 6.3 fix pack 10. \n * Known issues and their work around. \n\n\n * #RHEL6PREREQPREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM\n \n * #INSTALLUPGRADEFP10INSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10\n \n * #KIRHEL6KNOWN ISSUES AND THEIR WORK AROUND\n \n\nPREREQUISITE FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 ON RED HAT ENTERPRISE LINUX 6 (RHEL 6) OPERATING SYSTEM\n\n * The Korn shell (ksh) is required on Linux operating systems. \n * Before installing Tivoli Directory Server Version 6.3 client or server packages on RHEL 6, the following prerequisite packages must be present on the RHEL 6 system.\n You must upgrade the listed packages to the latest patch levels. See the Red Hat support site at http://rhn.redhat.com [http://rhn.redhat.com] for patches for Red Hat Enterprise Linux. You must install the following packages that are included with the Linux operating system. Red Hat Enterprise Linux (RHEL) Server 6 on x86-32 (x86/IA32) platform Red Hat Enterprise Linux (RHEL) Server 6 on x86-64 (AMD64/EM64T) platform Red Hat Enterprise Linux (RHEL) Server 6 on System z Red Hat Enterprise Linux (RHEL) Server 6 on POWER System (System i and System p) * compat-libstdc++-33 and its dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n * compat-libstdc++-33 and its dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n * compat-libstdc++-33 (install both 32 and 64-bit versions) and the dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n * compat-libstdc++-33 and its dependencies \n * gcc \n * gcc-c++ \n * glibc \n * glibc-common \n * glibc-devel \n * glibc-headers \n * libgcc\n \n \n * On RHEL 6, DB2 V9.7 FP4 is required for Tivoli Directory Server Version 6.3. To install DB2 V9.7 FP4 on RHEL6, the required minimum level of compat-libstdc++ is 1.3.1. On System z Linux, you must install the compat-libstdc++-33-3.2.3-47.3.s390x.rpm or higher version package before you install DB2.\n See the following DB2 websites for information about the DB2 prerequisites on RHEL 6. * https://www-304.ibm.com/support/docview.wss?uid=swg24031170 [https://www-304.ibm.com/support/docview.wss?uid=swg24031170] \n * https://www.ibm.com/developerworks/wikis/display/im/Red+Hat+Enterprise+Linux+%28RHEL%29+6+-+DB2+9.7 [https://www.ibm.com/developerworks/wikis/display/im/Red+Hat+Enterprise+Linux+%28RHEL%29+6+-+DB2+9.7]\n \n \n\n\n\n\n\n#ibm-contentBack to top\n\nINSTRUCTIONS FOR INSTALLING TIVOLI DIRECTORY SERVER VERSION 6.3 AND UPGRADING TO TIVOLI DIRECTORY SERVER VERSION 6.3 FIX PACK (FP) 10\n\n\nOn RHEL 6, you can install Tivoli Directory Server 6.3 using native operating system utilities only. To use Tivoli Directory Server 6.3 on RHEL 6, you must perform the following steps: 1. Install Tivoli Directory Server 6.3 General Availability (GA) version using native operating system utilities. \n 2. Upgrade DB2 V9.7 FP2 (provided with Tivoli Directory Server 6.3 GA ) to DB2 V9.7 FP4 level. \n 3. If you are using SSL or TLS enabled versions of TDS 6.3.0.10, you must install GSKit 8.0.14.14 or higher fix pack level. \n 4. Upgrade Tivoli Directory Server 6.3 GA to Tivoli Directory Server 6.3 FP 10 or higher fix pack level. See the following website for more information. * See the readme file for the required fix pack level at http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Directory+Server&release=All&platform=All&function=all [http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm~Tivoli&product=ibm/Tivoli/Tivoli+Directory+Server&release=All&platform=All&function=all]. \n * See http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778 [http://www-304.ibm.com/support/docview.wss?rs=767&uid=swg27009778] to obtain the latest fixes for IBM Tivoli Directory Server.\n \n \n\n\nNotes: * Tivoli Directory Server 6.3 installation using GUI installation program is not supported on RHEL 6. \n * Tivoli Directory Server 6.3 White pages installation using GUI installation program is not supported. \n * If you encounter an issue with the graphical user interface (GUI) tools such as the Instance Administration tool (idsxinst) and the Configuration tool (idsxcfg), use the appropriate command-line tool to complete the task.\n\n\nSupported Tivoli Directory Server Version 6.3 fix pack 10 components on RHEL 6 operating system: Operating system Supported 64-bit Directory server components Supported 32-bit Directory server components Supported DB2 levels Supported co-requisite software Red Hat Enterprise Linux (RHEL) Server 6 on x86-64 (AMD64/EM64T) Client\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Server 6 on x86-32 (x86/IA32) Not applicable Client\nServer\nProxy server\nWeb Administration tool V9.7 WSE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Server 6 on System z Client\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Server 6 on POWER System (System i and System p) Client\nServer\nProxy server\nWeb Administration tool Client V9.7 ESE FP4 * GSKit 8.0.14.14* \n * WebSphere Application Server 7.0.0.15 or higher fix pack version \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Desktop 6 on x86-64 Client Not applicable Not applicable * GSKit 8.0.14.14* \n * Java 1.6 SR9\n\nRed Hat Enterprise Linux (RHEL) Desktop 6 on x86-32 Not applicable Client Not applicable * GSKit 8.0.14.14* \n * Java 1.6 SR9\n\n\n*Note: You must upgrade the GSKit version to 8.0.14.22 or higher fix pack levels. The upgrade is required because of a known SSL/TLS related memory leak issue in GSKit version earlier than 8.0.14.22, which is fixed in GSKit 8.0.14.22 and higher fix pack levels. \n\nSupported browsers for Web Administration tool: * Mozilla Firefox 3.5.10\n\n\n\n\n\n#ibm-contentBack to top\n\nKNOWN ISSUES AND THEIR WORK AROUND\n\n\nOn RHEL6 systems, the following issues were found. The tech notes with identified issues and their work around are listed. * APARs: * The idsbulkload command fails on RHEL 6 with GLPBLK108E error message. See the APAR IO15265 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO15265 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO15265] for more information. \n * A return code, rc=-1, operations error is returned even after the ibmdirctl command starts ibmslapd on RHEL 6. See the APAR IO15910 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO15910 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO15910] for more information. \n * The Instance Administration tool (idsxinst) might throw an error when setting the LOCPATH environment variable with an invalid value. See the APAR IO16724 description at http://www-01.ibm.com/support/docview.wss?uid=swg1IO16724 [http://www-01.ibm.com/support/docview.wss?uid=swg1IO16724] for more information.\n \n \n * Tech notes: * Starting the ibmslapd or ibmdiradm process automatically using the inittab method on RHEL 6 does not work. See the tech note at http://www-01.ibm.com/support/docview.wss?uid=swg21588061 [http://www-01.ibm.com/support/docview.wss?uid=swg21588061] for more information.\n \n \n * Before installing DB2 V9.7, install compat-libstdc++ package on the system, if not present. If the required compat-libstdc++ package is not found on the system, DB2 exits installation with following error messages. * WARNING:\n * \n * Required minimum level of libstdc++ is 1.3.1\n * \n * Actual version of the library file detected : CXXABI_1.3\n * \n * Check the following web site for the up-to-date system requirements of IBM DB2 9.7\n * \n * http://www.ibm.com/software/data/db2/udb/sysreqs.html [http://www.ibm.com/software/data/db2/udb/sysreqs.html]\n * \n * http://www.software.ibm.com/data/db2/linux/validate [http://www.software.ibm.com/data/db2/linux/validate]\n * \n * Aborting the current installation ...\n * \n * Run installation with the option \"-f sysreq\" parameter to force the installation\n \n \n\n#ibm-contentBack to top", "question": "Composite Platform Installation Tool (CPIT) does not support IBM Tivoli Directory Server (ITDS) 6.3 on Red Hat Enterprise Linux \n\nWhen use the CPIT to install the FileNet P8 platform, the installation is not successful and the error occurs at ITDS installation, refer to the detailed error in cpit_install_stderr.txt:\n\nOUTPUT>========================================== OUTPUT>Setting Directories... OUTPUT>Mon Aug 11 08:20:00 SGT 2014 OUTPUT>/opt/IBM/cpit/decompressed/TDS/tdsV6.3/tds ERROR>./install_tds.bin: line 1956: warning: here-document at line 1956 delimited by end-of-file (wanted `/dev/null') OUTPUT>ERROR: /opt/IBM/ldap/V6.3/sbin/idsldif2db not found. TDS installation failed. Process completed with exit code: 1 ERROR in InvokeScripts-function - Terminate the remaining scripts. ***Aborting InvokeScripts-Install function.", "answer": "Tivoli Directory Server 6.3 installation using GUI installation program is not supported on RHEL 6."} +{"id": "TRAIN_Q223", "document": "IBM The off-line backup command could fail even when the database is quiesced on DB2 V10.1 and later. - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Offline-backup against the quiesced database failed with the error, SQL1035N.\nIt did not occur with V9.7. And it came to happen after migrating to V10.1 or later from V9.7. \n\nSYMPTOM\n \n\nThe following example shows this situation.\n\n1) In CLP 1 under the user having DBADM authority, execute quiesce database command on the database, sample.\n\n$ db2 connect to sample\n\nDatabase Connection Information\n\nDatabase server = DB2/AIX64 10.5.7\nSQL authorization ID = E105Q7A\nLocal database alias = SAMPLE\n\n\n$ db2 quiesce database immediate force connections\nDB20000I The QUIESCE DATABASE command completed successfully.\n$ db2 terminate\nDB20000I The TERMINATE command completed successfully.\n\n2) In CL 2 under the user having only connect privilege on sample database. \nRun the following shell repeating connect to sample.. \n\n$ cat connect.sh\n#!/bin/sh\ncount=0\nwhile [ $count -lt 1000 ]; do\ndb2 connect to $db\ncount=`expr $count + 1`\ndone \n\ndb2insth $ sh -x loop.sh\n+ count=0\n+ [ 0 -lt 1000 ]\n+ db2 connect to sample\nSQL20157N User with authorization ID \"USER1\" failed to attach to a\nquiesced instance, or connect to a quiesced database or a database in a\nquiesced instance which is in the following quiesce mode: \"QUIESCE DATABASE\"\nSQLSTATE=08004\n+ + expr 0 + 1\ncount=1\n+ [ 1 -lt 1000 ]\n+ db2 connect to sample\n\n\n* connect to sample continues to fail with the error, SQL20157N because the database, sample is quiesced.\n\n3) In CLP 1, execute the off-line backup command while executing the shell script under CLP2.\n\n$ db2 backup db sample\nSQL1035N The operation failed because the specified database cannot be\nconnected to in the mode requested. SQLSTATE=57019\n\n* The backup command failed. But this error does not happen on V9.7. \n\nFor avoiding the error in offline-backup, use quiesce instance command with restricted access option.\n\n\n\nCAUSE\nBecause of the code change in V10.1 GA, the off-line backup command could be blocked for short period of time while connect database command is executed.\n\n\n\nRESOLVING THE PROBLEM\n \n\nPlease use quiesce instance command with the \"restricted access\" option instead of the quiesce database command. \n\nOr please retry off-line backup command after getting SQL1035N error.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21980030]", "question": "SQL20157N happened in off-line backup against the quiesced database after migrating to V10.1 or V10.5 from V9.7. The customer spoladically got SQL20157N error in off-line backup command even when the database was quiesced. Why does this situation happen on V10.1 and V10.5 not on V9.7? ", "answer": "Because of the code change in V10.1 GA, the off-line backup command could be blocked for short period of time while connect database command is executed."} +{"id": "TRAIN_Q224", "document": "IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM WebSphere MQ Internet Pass-thru (MQIPT). \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4000 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4000]\nDESCRIPTION: The TLS protocol could allow a remote attacker to obtain sensitive information, caused by the failure to properly convey a DHE_EXPORT ciphersuite choice. An attacker could exploit this vulnerability using man-in-the-middle techniques to force a downgrade to 512-bit export-grade cipher. Successful exploitation could allow an attacker to recover the session key as well as modify the contents of the traffic. This vulnerability is commonly referred to as \"Logjam\".\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/103294 [https://exchange.xforce.ibmcloud.com/vulnerabilities/103294] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe affected ciphersuite is available in all versions of IBM WebSphere MQ Internet Pass-thru (MQIPT) prior to 2.1.0.2\n\nREMEDIATION/FIXES\nSupportPac MS81: IBM WebSphere MQ Internet Pass-Thru\nUsers of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2 [http://www.ibm.com/support/docview.wss?uid=swg24006386].\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 v2 Guide [http://www.first.org/cvss/v2/guide] \nOn-line Calculator v2 [http://nvd.nist.gov/CVSS-v2-Calculator] \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] ACKNOWLEDGEMENT\nReported to IBM by the WeakDH team at https://weakdh.org [https://weakdh.org] \n\nCHANGE HISTORY\n 11th June 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.\n\nRELATED INFORMATION\n A Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21962347]", "question": "Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) I need to understand details regarding Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000). What is the recommended fix?", "answer": "Users of IBM WebSphere MQ Internet Pass-Thru 2.1.0.1, 2.0 and older releases should first upgrade to IBM WebSphere MQ Internet Pass-Thru 2.1.0.2"} +{"id": "TRAIN_Q225", "document": "IBM Portal 7.0.0.1 migration may fail with error EJPPH0044E EJPPH0001E ADMC0009E while running upgrade-profile task. - United States upgrade-profile; migration; EJPPH0044E; EJPPH0001E; ADMC0009E; was.notification.timeout TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nOne may find the following in the configtrace.log file --- \n\n \nwps.dynamicui.transformationapp.webmod.xml to consolidated deployment \nscript \n[echo] Deploying consolidated web-app update script \n[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10056/wps/config/ \n\n[xmlaccess] EJPXB0004I: Writing output file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml \n[xmlaccess] EJPXB0002I: Reading input file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/config/work/consolida \ntedXMLAccess.xml \n[xmlaccess] EJPXB0019E: Server response indicates an error. For status \nand details of the XmlAccess error look at file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml. \n[xmlaccess] EJPXB0019E: Server response indicates an error. For status \nand details of the XmlAccess error look at file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/ConfigEngine/log/consolidatedXMLAc \ncessResult.xml. \n\n\nfrom the consolidatedXMLAccessResult.xml file, it fails at -- \n\n \n \n \ncom.ibm.wps.command.xml.XmlCommandException: EJPXA0043E: \nAn error occurred while creating or updating the resource. [web-app \ncom.ibm.wps.portlets.policystatus \nuid=com.ibm.workplace.policystatus.PolicyStatus] \ncom.ibm.wps.command.CommandFailedException: EJPPD0015E: \nPortlet application manager failed when user xmlaccess scripting user \nexecuted command UpdateWebApplication. \nWrappedException is: \ncom.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateException: EJPPH0044E: \nRedeployment of Web Module id in WAR file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta \ntus.war (application display name: PA_Policy_Status) didi not complete \nsuccessfully when invoking the WebSphere Application Server \nadministration interface. \ncom.ibm.wps.pe.mgr.exceptions.AppServerWarUpdateExceptio \nn: EJPPH0044E: Redeployment of Web Module id in WAR file \n/opt/IBM/WebSphere/APP/WP7/wp_profile/PortalServer/deployed/appPolicySta \ntus.war (application display name: PA_Policy_Status) didi not complete \nsuccessfully when invoking the WebSphere Application Server \nadministration interface. \ncom.ibm.wps.pe.mgr.exceptions.AppServerAdminListenerExce \nption: EJPPH0001E: Adding Notification Listener for MBean AppManagement \nfailed. (Application Name: PA_Policy_Status). \n\ncom.ibm.websphere.management.exception.ConnectorException: \nADMC0009E: The system failed to make the SOAP RPC call: \nqueryNames \n \n \n\n\nRESOLVING THE PROBLEM\nTo resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr. \nIf the property is not listed under custom properties, please add the above property.\n\nRe-run the upgrade-profile task to proceed with migration.", "question": "Why the Portal 7.0.0.2 - CF29 upgrade is failing ? Why the Portal 7.0.0.2 - CF29 upgrade is failing ?", "answer": "To resolve the issue increase the was.notification.timeout to 1200 (seconds) in WP DeploymentService either from WebSphere Admin Console or Dmgr. \nIf the property is not listed under custom properties, please add the above property.\n\nRe-run the upgrade-profile task to proceed with migration."} +{"id": "TRAIN_Q226", "document": "IBM Steps to disable RC4 SSL ciphers in Tivoli Integrated Portal - United States TIPL2SSL; TIPL2; TIPL2CONF; RC4; cipher; SSL TECHNOTE (FAQ)\n\nQUESTION\n What are the steps to disable RC4 ciphers from TIP? \n\nCAUSE\nSecurity scans may suggest disabling RC4 ciphers\n\nANSWER\nTo remove RC4 ciphers:\n\n\n 1. Log into the Websphere Application server and navigate to:\n SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP)\n \n \n 2. Select the *RC4* ciphers from the \"Selected ciphers\" list, and then click the \"< SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP)\n \n \n 2. Select the *RC4* ciphers from the \"Selected ciphers\" list, and then click the \"< Administering > Administering local WebSphere MQ objects > Performing local administration tasks using MQSC commands\nWebSphere MQ object names [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/fa11060_.htm]\n+ Case-sensitivity in MQSC commands\nMQSC commands, including their attributes, can be written in upper-case or lower-case. Object names in MQSC commands are folded to upper-case (that is, QUEUE and queue are not differentiated), unless the names are enclosed within single quotation marks. If quotation marks are not used, the object is processed with a name in upper-case. \n\nWhen specifying the SET command with the following value CLNTUSER(testuser) the string 'testuser' will be folded to upper-case resulting in the following value being actually used by runmqsc:\nCLNTUSER(TESTUSER)\nAnd in this case, there is no record for the user TESTUSER (the record is for 'testuser').\n\n\nANSWER\nNOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes. \n\nHowever, you MUST include the single quotes when specifying the value during an ACTION(REMOVE):\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)\n1 : set CHLAUTH(*) TYPE(USERMAP) CLNTUSER('testuser') ACTION(REMOVE)\nAMQ8877: WebSphere MQ channel authentication record set.\n\n\n++ Example of record with more attributes\n\nLet's examine the case when a record has more attributes, such as:\n\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(ADD)\nAMQ8877: WebSphere MQ channel authentication record set.\n\ndisplay CHLAUTH(MY.CHANNEL)\n9 : display CHLAUTH(MY.CHANNEL)\nAMQ8878: Display channel authentication record details.\nCHLAUTH(MY.CHANNEL) TYPE(USERMAP)\nDESCR( ) CUSTOM( )\nADDRESS(*) CLNTUSER(client_1)\nMCAUSER(user_1) USERSRC(MAP)\n\nYou want to delete the record and you try the following command which is based on the command that worked well for a simpler case. But this time, it fails:\n\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') ACTION(REMOVE)\nAMQ8884: Channel authentication record not found.\n\nYou try the original command that created the record, but changing the action to REMOVE:\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('client_1') USERSRC(MAP) MCAUSER('user_1') ADDRESS('*') ACTION(REMOVE)\nAMQ8885: Parameter not allowed for this action on a channel authentication record.\n\nThe attribute USERSRC is not a valid parameter for the REMOVE action (see table below).\nTherefore, by removing this attribute, then the following command worked successfully to remove the record:\nSET CHLAUTH(MY.CHANNEL) TYPE(USERMAP) CLNTUSER('mengano') ADDRESS('*') ACTION(REMOVE) \nAMQ8877: WebSphere MQ channel authentication record set.\n\nSee:\nWebSphere MQ 8.0.0 > IBM MQ > Reference > Administration reference > MQSC reference > The MQSC commands > \nSET CHLAUTH [http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q086630_.htm]\n.\n+ begin excerpt\n.\nUsage notes\nThe following table shows which parameters are valid for each value of ACTION:\n.\nAction \nParameter ADD or REMOVE REMOVEALL\nREPLACE\nCHLAUTH X X X \nTYPE X X X \nCMDSCOPE X X X \nACTION X X X \nADDRESS X X\nADDRLIST X X \nCHCKCLNT X \nCLNTUSER X X \nMCAUSER X \nQMNAME X X \nSSLCERTI X X \nSSLPEER X X \nUSERLIST X X \nUSERSRC X \nWARN X \nDESCR X \n.\n+ end excerpt\n\n\nAdditional Search Words: uppercase lowercase upper lower case\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ MQSeries", "question": "Why SET CHLAUTH ACTION(REMOVE) is not successful \n\nI have the following CHLAUTH records defined for channel BMMADMIN.SVRCONN:\n\n DIS CHLAUTH(BMM*) ALL\n 1 : DIS CHLAUTH(BMM*) ALL\n AMQ8878: Display channel authentication record details.\n CHLAUTH(BMMADMIN.SVRCONN) TYPE(USERMAP)\n DESCR(BTMA channel) CUSTOM( )\n ADDRESS(10.199.103.0) CLNTUSER(CHADVT3UTBMMPA$)\n MCAUSER(mqm) USERSRC(MAP)\n ALTDATE(2016-01-26) ALTTIME(20.38.12)\n AMQ8878: Display channel authentication record details.\n CHLAUTH(BMMADMIN.SVRCONN) TYPE(USERMAP)\n DESCR( ) CUSTOM( )\n ADDRESS( ) CLNTUSER(chadvt3utbm)\n MCAUSER(mqm) USERSRC(MAP)\n ALTDATE(2016-01-27) ALTTIME(18.03.44)\n\nI am attempting to remove the first of the two records above with this command, but receive the response \"record not found\":\n\n SET CHLAUTH(BMMADMIN.SVRCONN) TYPE(USERMAP) CLNTUSER('CHADVT3UTBMMPA$') ACTION(REMOVE)\n 3 : SET CHLAUTH(BMMADMIN.SVRCONN) TYPE(USERMAP) CLNTUSER('CHADVT3UTBMMPA$') ACTION(REMOVE)\n AMQ8884: Channel authentication record not found.\n\nHow do I fix this problem??\n", "answer": "you MUST include the single quotes when specifying the value during an ACTION(REMOVE):"} +{"id": "TRAIN_Q228", "document": "IBM SQL1763N error with Reason Code 11 while running \"Alter Tablespace\" command to reclaim unused storage space against DMS or automatic storage tablespaces. - United States SQL1763N; Alter Tablespace; reclaimable storage; DMS; Automatic storage table spaces; MON_GET_TABLESPACE; RECLAIMABLE_SPACE_ENABLED; SMS; DB2 Version 9.7; lower high water mark TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving SQL1763N error with Reason Code 11 while running \"Alter Tablespace\" command to reclaim unused storage space against DMS or automatic storage tablespaces. \n\nSYMPTOM\nFollowing reasons apply: \n\n * If the DMS or automatic storage tablespaces are not created in DB2 Version 9.7 or later, as the \"Reclaimable Storage\" is not available in tablespaces created in earlier versions(V9.1/V9.5) of the DB2 product. \n * Trying to alter a SMS tablespace as this feature is not supported on SMS tablespaces. \n\n\nExample testcase on a TEMPSPACE1 SMS tablespace. \n\n * \n * \n * DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL1763N Invalid ALTER TABLESPACE statement for table space \"TEMPSPACE1\" due to reason \"11\" SQLSTATE=429BC \n * \n \n\n\nDIAGNOSING THE PROBLEM\nMON_GET_TABLESPACE table function and RECLAIMABLE_SPACE_ENABLED monitor element can be used to identify whether the tablespace is enabled for reclaimable storage or not. Example: \ndb2 \"SELECT varchar(tbsp_name, 30) as tbsp_name, tbsp_type, RECLAIMABLE_SPACE_ENABLED FROM TABLE(MON_GET_TABLESPACE('',-2))\" \n\n \n\nSnippet of the output: \n\n \n\nTBSP_NAME TBSP_TYPE RECLAIMABLE_SPACE_ENABLED\n----------------- ----------- -------------------------\nSYSCATSPACE DMS 1\nTEMPSPACE1 SMS 0\nUSERSPACE1 DMS 1 \n\nIf the RECLAIMABLE_SPACE_ENABLED monitor element returns a value of 1, then the tablespace is enabled for reclaimable storage. Otherwise, it returns a value of 0.\n\n\n\nRESOLVING THE PROBLEM\nTo use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later. Example testcase on SYSCATSPACE DMS tablespace which has reclaimable storage enabled. \n\n \n\n * \n * \n * \n * \n * \n\n\nNote: \nTablespaces migrated from DB2 V9.1/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature. RELATED INFORMATION\n Reclaimable storage [http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0055392.html]", "question": "DB2 Non Reclaimable Storage . We have tablespaces defined under DB2 9.5 that apparently are not able\nto reclaim storage back to the OS, but does that mean DB2 cannot reuse\nthis space as well?", "answer": "To use the reclaimable storage feature, make sure to create the DMS or automatic storage tablespaces in DB2 Version 9.7 or later."} +{"id": "TRAIN_Q230", "document": "IBM Levels of JRE and GSkit bundled with IBM MQ - United States RELEASE NOTES\n\nABSTRACT\n This page gives you access to the details of the levels of JRE and GSKit included with various maintenance levels of IBM MQ, by version. \n\nCONTENT\n \n\nIBM MQ V9.0 Continuous Delivery GSKit Level JRE Level IBM Security Directory Server Client Level 9.0.5 (Windows, Linux, AIX) 8.0.50.88 8.0.5.10 6.4.0.14 9.0.4 (Windows, Linux, AIX) 8.0.50.82 8.0.4.11 6.4.0.12 9.0.3 (Windows, Linux) 8.0.50.78 8.0.4.5 6.4.0.11 9.0.2 (Windows, Linux) 8.0.50.77 8.0.3.20 6.4.0.11 9.0.1 (Windows, Linux) 8.0.50.70 8.0.3.12 6.4.0.9 \nIBM MQ V9.0 Long Term Support GSKit Level JRE Level IBM Security Directory Server Client Level 9.0.0.4 (Windows, Linux, AIX) 8.0.50.88 8.0.5.11 6.4.0.15 9.0.0.4 (Solaris) 8.0.50.88 8.0.5.10 6.4.0.15 9.0.0.4 (HP) 8.0.50.88 8.0.5.10 6.3.1.23 9.0.0.3 (Windows, Linux, AIX, Solaris ) 8.0.50.88 8.0.5.10 6.4.0.14 9.0.0.3 (HP) 8.0.50.88 8.0.5.5 6.3.1.22 9.0.0.2 (Windows, Linux, AIX, Solaris, HP) 8.0.50.77 8.0.4.10 6.4.0.12 9.0.0.1 (Windows, Linux, AIX) 8.0.50.77 8.0.4.1 6.4.0.11 9.0.0.1 (HP, Solaris) 8.0.50.77 8.0.4.5 6.4.0.11 9.0.0.0 (Solaris, Windows, Linux, AIX) 8.0.50.65 8.0.3.0 6.4.0.6 9.0.0.0 (HP) 8.0.50.65 8.0.2.14 6.3.1.15 \nIBM MQ V8.0 GSKit Level JRE Level IBM Security Directory Server Client Level 8.0.0.9 (Windows, Linux, AIX) 8.0.50.88 7.1 SR4 FP20 6.4.0.15 8.0.0.9 (Solaris) 8.0.50.88 7.0 SR10 FP20 6.4.0.15 8.0.0.9 (HP) 8.0.50.88 7.0 SR10 FP15 6.3.1.23 8.0.0.8 (Windows, Linux, AIX) 8.0.50.83 7.1 SR4 FP10 6.4.0.13 8.0.0.8 (Solaris, HP) 8.0.50.83 7.0 SR10 FP10 6.3.1.21 8.0.0.7 (Windows, Linux, AIX) 8.0.50.79 7.1 SR4 FP5 6.4.0.11 8.0.0.7 (Solaris, HP) 8.0.50.79 7.0 SR10 FP5 6.3.1.20 8.0.0.6 (Windows, Linux, AIX) 8.0.50.71 7.1 SR3 FP60 6.4.0.10 8.0.0.6 (Solaris) 8.0.50.71 7.0 SR9 FP60 6.4.0.10 8.0.0.6 (HP) 8.0.50.71 7.0 SR9 FP50 6.3.1.19 8.0.0.5 (Windows, Linux, AIX) 8.0.50.65 7.1 SR 3 FP 40 6.4.0.8 8.0.0.5 (Solaris) 8.0.50.65 7.0 SR 9 FP 40 6.4.0.8 8.0.0.5 (HP) 8.0.50.65 7.0 SR 9 FP 32 6.3.1.17 8.0.0.4 (Windows, Linux, AIX) 8.0.50.52 7.1 SR 3 FP 10 6.3.1.12 (6.4.0.4 Linux) 8.0.0.4 (Solaris, HP) 8.0.50.52 7 SR 9 FP 10 6.3.1.12 8.0.0.3 (Windows, Linux, AIX) 8.0.50.42 7.1 SR 3 6.3.1 8.0.0.3 (Solaris) 8.0.50.42 7 SR 9 6.3.1 8.0.0.3 (HP) 8.0.50.42 7 SR 8 6.3.1 8.0.0.2 (Windows, Linux, AIX) 8.0.50.34 7.1 SR 2 6.3.1 8.0.0.2 (Solaris, HP) 8.0.50.34 7 SR 8 6.3.1 8.0.0.1 (Solaris, Windows, Linux, AIX) 8.0.50.31 7 SR 7 FP 1 6.3.1 8.0.0.1 (HP) 8.0.50.31 7 SR 6 FP 1 6.3.1 8.0.0.0 (Solaris, Windows, Linux ,HP, AIX) 8.0.50.16 7 SR 6 6.3.1 \nIBM WebSphere MQ V7.5 GSKit Level JRE Level 7.5.0.8 (Windows, Linux, AIX, HP, Solaris) 8.0.50.79 6.0 SR16 FP45 7.5.0.7 (HP) 8.0.50.66 6.0 SR16 FP22 7.5.0.7 (Windows, Linux, AIX) 8.0.50.66 6.0 SR16 FP26 7.5.0.7 (Solaris) 8.0.50.66 6.0 SR16 FP25 7.5.0.6 (HP) 8.0.14.53 1.6 SR16 FP16 7.5.0.6 (Solaris, Windows, Linux, AIX) 8.0.14.53 1.6 SR16 FP20 7.5.0.5 (Solaris, Windows, Linux, HP, AIX) 8.0.14.48 1.6 SR 16 FP 3 Interim Fix 7.5.0.4 (Solaris, Windows, Linux, AIX) 8.0.14.43 1.6 SR 16 7.5.0.4 (HP) 8.0.14.43 1.6 SR 15 FP 1 7.5.0.3 (Solaris, Windows, Linux ,HP, AIX) 8.0.14.28 1.6 SR 15 7.5.0.2 (Solaris, Windows, Linux, AIX) 8.0.14.28 1.6 SR 13 FP 2 7.5.0.2 (HP) 8.0.14.28 1.6 SR 13 FP 1 7.5.0.1 (Solaris, Windows, Linux, HP, AIX) 8.0.14.26 1.6 SR 12 7.5.0.0 (Solaris, Windows, Linux, HP, AIX) 8.0.14.21 1.6 SR 10 FP 1 \nIBM WebSphere MQ V7.1 GSKit Level JRE Level 7.1.0.9 (Solaris, Windows, Linux, HP, AIX) 8.0.50.83 1.6 SR16 FP50 7.1.0.8 (Solaris, Windows, Linux, HP, AIX) 8.0.50.69 1.6 SR16 FP30 7.1.0.7 (Solaris, Windows, Linux, HP, AIX) 8.0.14.50 1.6 SR 16 FP 5 7.1.0.6 (Solaris, Windows, Linux, HP, AIX) 8.0.14.44 1.6 SR 16 FP 1 7.1.0.5 (Solaris, Windows, Linux, HP, AIX) 8.0.14.35 1.6 SR 15 FP 1 7.1.0.4 (Solaris, Windows, Linux, HP, AIX) 8.0.14.28 1.6 SR 14 7.1.0.3 (Solaris, Windows, Linux, AIX) 8.0.14.28 1.6 SR 13 FP 2 7.1.0.3 (HP) 8.0.14.28 1.6 SR 13 FP 1 7.1.0.2 (Solaris, Windows, Linux, HP, AIX) 8.0.14.22 1.6 SR 10 FP 1 7.1.0.1 (Solaris, Windows, Linux, HP, AIX) 8.0.14.14 1.6 SR 10 7.1.0.0 (Solaris, Windows, Linux, HP, AIX) 8.0.14.12 1.6 SR 9 FP 1 \nIBM WebSphere MQ V7.0.1 GSKit Level JRE Level 7.0.1.14 (Solaris, Windows, Linux, HP, AIX) 7.0.5.6, 8.0.14.53 1.5 SR 16 FP 14 7.0.1.13 (Solaris, Windows, Linux, HP, AIX) 7.0.5.6, 8.0.14.49 1.5 SR 16 FP 9 7.0.1.12 (Solaris, Windows, Linux, HP, AIX) 7.0.4.48, 8.0.14.34 1.5 SR 16 FP 4 7.0.1.11 (Solaris, Windows, Linux, HP, AIX) 7.0.4.45, 8.0.14.28 1.5 SR 16 FP 3 7.0.1.10 (Solaris, Windows, Linux, HP, AIX) 7.0.4.44, 8.0.14.26 1.5 SR 15 7.0.1.9 (Solaris, Windows, Linux, HP, AIX) 7.0.4.41, 8.0.14.22 1.5 SR 13 FP 1 7.0.1.8 (Solaris, Windows, Linux, HP, AIX) 7.0.4.38, 8.0.14.14 1.5 SR 13 7.0.1.7 (Solaris, Windows, Linux, HP, AIX) 7.0.4.33, 8.0.14.9 1.5 SR 12 FP 5 7.0.1.6 (Solaris, Windows, Linux, HP, AIX) 7.0.4.33, 8.0.14.9 1.5 SR 12 FP 4 7.0.1.5 (Solaris, Windows, Linux, HP, AIX) 7.0.4.29, 8.0.14.9 1.5 SR 12 FP 3 7.0.1.4 (Solaris, Windows, Linux, HP, AIX) 7.0.4.29, 8.0.14.7 1.5 SR 11 7.0.1.3 (Solaris, Windows, Linux, HP, AIX) 7.0.4.27 1.5 SR 11 7.0.1.2 (Solaris, Linux, HP, AIX) 7.0.4.27 1.5 SR 11 7.0.1.2 (Windows) 7.0.4.27 1.5 SR 5 7.0.1.1 (Solaris, Linux, HP, AIX) 7.0.4.23 1.5 SR 10 7.0.1.1 (Windows) 7.0.4.23 1.5 SR 5 7.0.1.0 (Solaris, Windows, Linux, HP, AIX) 7.0.4.23 1.5 SR 5 7.0.0.2 (Solaris, Windows, Linux, HP, AIX) 7.0.4.20 1.4.2 SR 12 7.0.0.1 (Solaris, Windows, Linux, HP, AIX) 7.0.4.20 1.4.2 SR 12 7.0.0.0 (Solaris, Windows, Linux, HP, AIX) 7.0.4.14 1.4.2 SR 12 \n\n\n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", "question": "Does IBM MQ Server installation include a Java Runtime Engine (JRE) and what is it used for? Does IBM MQ Server installation include a Java Runtime Engine (JRE)?", "answer": "This page gives you access to the details of the levels of JRE and GSKit included with various maintenance levels of IBM MQ, by version."} +{"id": "TRAIN_Q231", "document": "IBM Filter Analyzer and Filters comparing ObjectServer fields - United States netcool; impact; netcool/impact; nci; event; reader; eventreader; omnibus; omnibuseventreader; object; server; objectserver; field; fields; compare; contrast; comparison; use; filter; filters; filtering; analyse; analyze; analyser; analyzer; filteranalyser; filteranalyzer; rule; includes; unsupported; expression; include; including; support; supporting; supported; restriction; ExecutionException; Execution; Exception; consolidate; consolidatefilters; concurrent; expressions; expression TECHNOTE (FAQ)\n\nQUESTION\n The Filter Analyzer reports the error:\n\n\"rule includes an unsupported expression\"\n\nwhen comparing two ObjectServer fields against each other and/or a field against GetDate within an EventReader Filter\n\n\n\nCAUSE\nThis is a limitation in the functionality of the Filter Analyzer in Impact and can produce the log file message:\nWARN [EventFilter] Could not consolidate filters. Please check if the filter expressions are valid. java.util.concurrent.ExecutionException\n\n\n\n\nANSWER\nIn the EventReader properties file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[EventReaderName].props\n\nwhere [ImpactServerName] is the name of the ImpactServer (NCI by default) and [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader). Add the property:\n\nimpact.[EventReaderName].consolidatefilters=false\n\nwhere, again, [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader).\n\nOnce this property has been added to the file an ImpactServer restart is required to enable it.\n\nIn a Clustered environment one would have to stop the Secondary ImpactServer(s) first, then stop and restart the Primary ImpactServer and then restart the Secondary ImpactServer(s) to ensure that the property is not overwritten and is distributed to each ImpactServer in the Cluster.\n\nPlease note that this issue relates to the use of the Filter Analyzer and does not impinge upon the EventReader ability to parse the Filter.\n\nIf you are unable to see the Filter being applied in the outgoing SQL for the EventReader please read the TechNote \"EventReader Filters not applied to SQL select statement\" [link below].\n\n\nRELATED INFORMATION\n EventReader Filters not applied to SQL select statement [http://www-01.ibm.com/support/docview.wss?uid=swg21566480]", "question": "Netcool/Impact (all versions): OMNIbusEventReader Filter Analyzer error \"rule includes an unsupported expression\" Netcool/Impact (all versions): OMNIbusEventReader Filter Analyzer error \"rule includes an unsupported expression\"\n\nThis occurs when comparing two ObjectServer fields against each other in a Filter. ", "answer": "In the EventReader properties file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[EventReaderName].props\n\nwhere [ImpactServerName] is the name of the ImpactServer (NCI by default) and [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader). Add the property:\n\nimpact.[EventReaderName].consolidatefilters=false\n\nwhere, again, [EventReaderName] is the lower-case name of the EventReader (for example: omnibuseventreader).\n\nOnce this property has been added to the file an ImpactServer restart is required to enable it.\n\nIn a Clustered environment one would have to stop the Secondary ImpactServer(s) first, then stop and restart the Primary ImpactServer and then restart the Secondary ImpactServer(s) to ensure that the property is not overwritten and is distributed to each ImpactServer in the Cluster."} +{"id": "TRAIN_Q232", "document": "IBM Security Bulletin: MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affects IBM WebSphere Message Broker and IBM Integration Bus (CVE-2015-5011) - United States WMB IIB SECURITY BULLETIN\n\nSUMMARY\n MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affecting IBM WebSphere Message Broker and IBM Integration Bus \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-5011 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5011]\nDESCRIPTION: IBM Integration Bus could allow a local user to start and stop a service that they should not have access to.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/106403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/106403] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V9 \n\n WebSphere Message Broker V8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V9 PI28139 The APAR is available in fix pack 9.0.0.4 \nhttps://www-304.ibm.com/support/docview.wss?rs=849&uid=swg24040542 [https://www-304.ibm.com/support/docview.wss?rs=849&uid=swg24040542] WebSphere Message Broker\nV8 PI28139 The APAR is available in fix pack 8.0.0.6\nhttp://www-01.ibm.com/support/docview.wss?rs=849&uid=swg24040259 [http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg24040259] 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\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-03.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] CHANGE HISTORY\n 06-Oct-2015 - Original version Published/CVSS version changed to V3\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\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z/OS 9.0 \nPRODUCT ALIAS/SYNONYM\n WMB IIB", "question": "Help with Security Bulletin: MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affects WMB and IIB (CVE-2015-5011) I need to understand details regarding Security Bulletin: MQSISTOP/STARTMSGFLOW commands with unauthorized user succeed affects IBM WebSphere Message Broker and IBM Integration Bus (CVE-2015-5011). Where can I find this information? ", "answer": "CVEID: CVE-2015-5011 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-5011]\nDESCRIPTION: IBM Integration Bus could allow a local user to start and stop a service that they should not have access to.\nCVSS Base Score: 4\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/106403 [https://exchange.xforce.ibmcloud.com/vulnerabilities/106403] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N)"} +{"id": "TRAIN_Q233", "document": "IBM Security Bulletin: API Connect is affected by a cross-site scripting vulnerability \nCVE-2018-1382 - United States SECURITY BULLETIN\n\nSUMMARY\n API Connect has addressed the following vulnerability. \n\nIBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session. \n\n\n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2018-1382 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1382]\nDESCRIPTION:IBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session.\nCVSS Base Score: 5.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/138079 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138079]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected API Connect Affected Versions IBM API Connect 5.0.0.0-5.0.6.4 IBM API Connect 5.0.7.0-5.0.7.2 IBM API Connect 5.0.8.0-5.0.8.1 REMEDIATION/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation / First Fix IBM API Connect\n\n5.0.0.0-5.0.6.4 5.0.6.5 LI79885 Addressed in IBM API Connect V5.0.6.5.\n\nManagement Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.4&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] IBM API Connect\n\n5.0.7.0-5.0.7.2 5.0.8.2 LI79885 Addressed in IBM API Connect V5.0.8.2.\n\nManagement Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] IBM API Connect\n\n5.0.8.0-5.0.8.1 5.0.8.2 LI79885 Addressed in IBM API Connect V5.0.8.2.\n\nManagement Server and Developer Portal are impacted. \n\nFollow this link and find the \"APIConnect_Management\" and\n\"APIConnect-Portal\" packages:\n\nhttps://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.8.1&platform=All&function=all [https://www-945.ibm.com/support/fixcentral/swg/selectFixes?parent=ibm%7EWebSphere&product=ibm/WebSphere/IBM+API+Connect&release=5.0.7.0&platform=All&function=all] GET 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 30 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.", "question": "Help with Security Bulletin: API Connect is affected by a cross-site scripting vulnerability CVE-2018-1382 I need to understand details regarding Security Bulletin: API Connect is affected by a cross-site scripting vulnerability CVE-2018-1382. Where can I find this information? ", "answer": "CVEID:CVE-2018-1382 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1382]\nDESCRIPTION:IBM API Connect is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality, potentially leading to credentials disclosure within a trusted session.\nCVSS Base Score: 5.4\nCVSS Temporal Score: Seehttps://exchange.xforce.ibmcloud.com/vulnerabilities/138079 [https://exchange.xforce.ibmcloud.com/vulnerabilities/138079]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N)"} +{"id": "TRAIN_Q234", "document": "IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States wasservice; was service; wasservice command; websphere windows service; wasservice cmd; versiongap TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WASServiceCmd.exe is a front end for WASService.exe, which is shipped with WebSphere Application Server. WASService.exe is required in its default directory for adding, updating, and removing WebSphere Services in Windows.\n\nNotice: In WebSphere Application Server v8 and later, this utility is shipped with the product under the name of WASServiceHelper.bat in the bin directory.\nReference:\nUsing the WASServiceHelper utility to create Windows services for application servers\nhttps://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html [https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tins_wasservicecmd.html]\n\nSee DeveloperWorks article for detailed information: (Link at the bottom of this document) \n\nSYMPTOM\nCreating and removing a WebSphere service in Windows is confusing and error prone.\n\n\nCAUSE\nThis application takes several parameters which can be confusing to the user along with several long path strings leaving opportunities to setup incorrectly.\n\nENVIRONMENT\nWindows\n\nRESOLVING THE PROBLEM\n\n\n\n 1. Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line. \n \n \n 3. The WASServiceCmd utility prompts you to select specific options and settings from a list and then calls the WASService.exe command passing all selected parameters. This greatly reduces the time it takes to create a Windows service for WebSphere Application Server and reduces the opportunity for user errors.\n\n\n[/support/docview.wss?uid=swg21397335&aid=1] Flash demonstration [http://public.dhe.ibm.com/software/websphere/appserv/support/tutorials/wasservicecmd.swf] \n\nNote: This also creates an entry in the WASServiceCmd.log in the current directory which contains the actual WASService.exe command used to create the service. \n\nExample of a log entry: \n\n[Fri Aug 14 12:22:01 -0500 2009] WASService.exe -add \"Deployment Mgr01\" -serverName \"dmgr\" \n-profilePath \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\"\n-logRoot \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\"\n-logFile \"C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\Dmgr01\\logs\\dmgr\\WS_startdmgr.log\" -encodeParams -stopArgs \"-username vanno -password ****** \" \n-startType manual \n-restart false WASServicecmd.zip [/support/docview.wss?uid=swg21397335&aid=3] [/support/docview.wss?uid=swg21397335&aid=2] \n\nNotice: Some browsers are having trouble downloading this file and getting docview.wss instead. Download this file, then rename the file with a \".zip\" extension (for example, docview.zip or WASServiceCmd.zip). You can now access the utility. \nSee DeveloperWorks article for more information: \nThe Support Authority: Take the confusion (and errors) out of creating Windows services for WebSphere Application Server [http://www.ibm.com/developerworks/websphere/techjournal/1005_supauth/1005_supauth.html] \n\n\nSee TroubleShooting: WebSphere Application Server (Windows Services) problems for V6.0, V6.1 and V7.0 [http://www.ibm.com/support/docview.wss?uid=swg21232884] if you are still having a problem with Windows services.", "question": "How do I create a windows service for WebSphere Application Server version 7.0.X? Is there a tool that can help me create the windows service in an automated form? ", "answer": "Place the WASServiceCmd.exe utility in the following directory:\n \n install_root\\bin \n \n 2. Launch the command from the command line."} +{"id": "TRAIN_Q235", "document": "IBM Maximo fails to start with error BMXAA4087E - United States TPAESCCD; Maximo; start; BMXAA4087E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n BMXAA4087E - The MAXMESSAGE value for group login and key username could not be retrieved. \n\nSYMPTOM\n[ERROR] BMXAA6497E - A message for group login and key username could not be found.\ncom.ibm.db2.jcc.c.SqlException: No authorized routine named \"ISNULL\" of type \"FUNCTION\" having compatible arguments was found.\nat com.ibm.db2.jcc.c.fg.e(fg.java:1596)\nat com.ibm.db2.jcc.c.fg.a(fg.java:1206)\nat com.ibm.db2.jcc.b.gb.g(gb.java:140)\nat com.ibm.db2.jcc.b.gb.a(gb.java:39)\nat com.ibm.db2.jcc.b.w.a(w.java:34)\nat com.ibm.db2.jcc.b.vb.g(vb.java:139)\nat com.ibm.db2.jcc.c.fg.n(fg.java:1177)\nat com.ibm.db2.jcc.c.fg.a(fg.java:1832)\nat com.ibm.db2.jcc.c.fg.a(fg.java:473)\nat com.ibm.db2.jcc.c.fg.executeQuery(fg.java:457)\nat psdi.server.MXServer.getMessage(MXServer.java:5362)\nat psdi.server.MXServer.getMessages(MXServer.java:5538)\n\n\nENVIRONMENT\nIBM DB2 database\n\nDIAGNOSING THE PROBLEM\nConnect to database back end and check the result of this query :-\n\n\nselect propvalue from maximo.maxpropvalue where propname='mxe.db.format.nullvalue'; \n\nIf you are using DB2 database, the result should be 'COALESCE'.\n\n\nRESOLVING THE PROBLEM\nFor IBM DB2, the value is COALESCE, and you cannot change the default value. \n\nFor Oracle, the value is NVL, and you cannot change the default value.\nFor SQL Server, the value must be set to ISNULL.\n\nMake sure MXServer is stopped. Connect to database back end and update mxe.db.format.nullvalue by running following query :- \n\nupdate maximo.maxpropvalue set propvalue='COALESCE' where propname='mxe.db.format.nullvalue'; \n\nStart MXServer again.", "question": "Cannot start Maximo/SCCD with error BMXAA4087E - The MAXMESSAGE value for group login and key username could not be retrieved. Cannot start Maximo/SCCD with error BMXAA4087E - The MAXMESSAGE value for group login and key username could not be retrieved.", "answer": "For IBM DB2, the value is COALESCE, and you cannot change the default value. \n\nFor Oracle, the value is NVL, and you cannot change the default value.\nFor SQL Server, the value must be set to ISNULL.\n\nMake sure MXServer is stopped. Connect to database back end and update mxe.db.format.nullvalue by running following query :- \n\nupdate maximo.maxpropvalue set propvalue='COALESCE' where propname='mxe.db.format.nullvalue'; \n\nStart MXServer again."} +{"id": "TRAIN_Q236", "document": "IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States SPSS mac macintosh Apple Macintosh statistics OS supported version compatibility matrix leopard Snow Leopard Lion Mountain Lion 10.8 Mavericks 10.9 22 Yosemite 10.10 (Yosemite) el capitan 10.11 spss 24 Sierra 10.12 High Sierra 10.13 TECHNOTE (FAQ)\n\nQUESTION\n I would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions? \n\nANSWER\nPlease see the list below. It is strongly recommended to review the platform information on IBM Software Product Compatibility Reports [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.jsp]. The installation of IBM SPSS Statistics software on Apple Macintosh OSX operating systems requires an Intel processor. \n\nA) Apple Macintosh MacOS High Sierra (10.13) \n\nSupport for IBM SPSS Statistics 25 only. Please note that no other SPSS release will be officially supported on High Sierra, but older versions like SPSS Statistics 24 may run as well on High Sierra. \n\nNOTE: There's a known issue with some of the earlier release of Mac High Sierra system (13.0 and 13.1 beta version). \nThe top menu of SPSS 25 may disappear if the Mac OS system is set to Non-English. \nThe official MacOSX 10.13.1 version do not have this issue. So, if you encountert this issue you need to update your Mac OS version to latest official 10.13.1 build from Apple. \n\n \n\nB) Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra. \n\n \n\nC) Apple Macintosh OSX El Capitan (10.11) \n\nSupport for IBM SPSS Statistics 24. Please see the Release notes - IBM SPSS Statistics 24.0 [http://www-01.ibm.com/support/docview.wss?uid=swg27047057] for known issues on Macintosh. \n\nFull documentation including installation material provided in different languages and manuals for release 24 can be found on IBM SPSS Statistics 24 Documentation [http://www-01.ibm.com/support/docview.wss?uid=swg27047033] webpage. \n\n \n\nAlso, Support for IBM SPSS Statistics 23. Note: if you want to install on El Capitan, please refer to technote 1970391 [http://www-01.ibm.com/support/docview.wss?uid=swg21970391] \n\n \n\nD) Apple Macintosh OSX Yosemite (10.10) \n\nSupport for IBM SPSS Statistics 24, IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n \n\nNote: Mac OSX 10.10 (Yosemite) was released on Thursday, October 16th 2014 by Apple after Statistics 22 was released. If you like to use Statistics 22 on Yosemite you need to install Statistics 22 Fixpack 2 as well. Statistics 22 FixPack 2 and release Statistics 23 are fully tested on Yosemite OSX 10.10. So if you like to run Statistics 22 on Yosemite please install Statistics 22 FixPack 2 and also read the section below: \n\n**** \n\nIn some instances it can be necessary to re-install the legacy Apple Java 6 on 10.10 for the use of Statistics 22 FixPack 2 on this platform\n\nDownload and re-install Apple Java 6 \n\n- After you upgraded your Apple Mac OSX from a previous release to 10.10, Apple Java 6 may no longer exists on your upgraded system. If you then launch Statistics 22 which is an application that relies on Java 6, it can happen, the Mac OS pops up a dialog box stating Java 6 was requested, but none is present.\n- The Java dialog has a \"More Info\" button, which when clicked opens a browser to an Apple Tech Support page for Apple Java 2014-001. A download link is provided:\nhttp://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572]\n- Click on the download link and a DMG containing the Java 6 installer is downloaded.\n- Then you open the Java DMG, double click on the Java installer, follow the prompts and complete the installation of Java 6.\n\n******* \n\n \n\nE) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22 \n\n*** \n\nNote: IBM SPSS Statistics 22 was developed and released prior to Apple's release of OS X 10.9 (Mavericks). However, Statistics 22 can be installed on Mac OSX 10.9 if you install Apple Java SE 6 (1.6.0_65) on OS X 10.9 first before you install Statistics 22. Please see http://support.apple.com/kb/dl1572 [http://support.apple.com/kb/dl1572] for download. \n\n**** \n\nF) Apple Macintosh OSX Mountain Lion (10.8) \n\nSupport for IBM SPSS Statistics 22 and IBM SPSS Statistics 21 \n\n**** \n\nG) Apple Macintosh OSX Lion (10.7) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nH) Apple Macintosh OSX Snow Leopard (10.6) \n\nSupport for IBM SPSS Statistics 21 \n\n \n\nOlder SPSS Statistics releases 18 and 19 and 20: \n\nPlease note that SPSS Statistics releases 18, 19 and 20 are no longer supported by IBM. Please contact IBM Sales department to renew your contracts.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https://developer.ibm.com/answers/topics/statistics.html?smartspace=predictive-analytics]", "question": "Cannot Authorize SPSS 19 Installation on New Computer,Need to Authorize SPSS 19 on a New Computer I'm currently using SPSS 19 and need to install it on a new computer, however, it will not authorize. I've spoken to SPSS support by phone but they recommended checking here. I'm running on a Mac, OS X Sierra, for SPSS 19. Would someone please be able to assist?,I'm currently running SPSS 19 and need to install it on a new computer. When I try to authorize it, it fails. I've spoken to SPSS over the phone to no avail. I'm running OS X Sierra. Could anyone please help? ", "answer": "Apple Macintosh MacOS Sierra (10.12) \n\nSupport for IBM SPSS Statistics 25 and IBM SPSS Statistics 24 only. For release 24 It is also recommended to install the latest FixPack 2 for release 24 on Mac [http://www-01.ibm.com/support/docview.wss?uid=swg24043574]. [http://www-01.ibm.com/support/docview.wss?uid=swg24042675] \n\nNo older SPSS Statistics releases are supported on Sierra."} +{"id": "TRAIN_Q237", "document": "IBM Collect troubleshooting data for the IBM Business Process Manager products - United States install; mustgather; bpm; v7.5; collect; logs; troubleshooting; v8.5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You are having a problem with the IBM Business Process Manager (BPM) products. You would like to know what information you must collect (MustGather) so that the IBM Business Process Manager Support team can diagnose your problem. If you gather this documentation before contacting support, it will expedite the troubleshooting process and save you time. \n\nDIAGNOSING THE PROBLEM\nStart the problem analysis: \n\n * Review the SystemOut.log file at install_​​root​​/profiles/​​profile​​_​​name​​/​​logs​​/server​​_​​name and look for error messages that have been logged around the time stamp when the issue showed up. \n * Search the [http://www.ibm.com/software/htp/cics/tserver/support/]appropriate product support site from the following list for known problems using symptoms such as the message number and error codes: * IBM Business Process Manager Advanced [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Advanced] \n * IBM Business Process Manager Standard [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Standard] \n * IBM Business Process Manager Express [http://www.ibm.com/support/entry/portal/Overview/Software/WebSphere/IBM_Business_Process_Manager_Express] \n * IBM BPM Advanced Pattern for Red Hat Enterprise Linux Server [http://www.ibm.com/support/entry/portal/search_results?sn=spe&q=&filter=DC.Subject:SSV2LR]\n \n \n * Use theIBM Support Assistant [http://www.ibm.com/software/support/isa/]to search for known problems in the product documentation, forums, technotes, and so on. \n * Search the IBM dW Answers [https://developer.ibm.com/answers/topics/bpm/] or IBM Business Process Manager developerWorks community [http://www.ibm.com/developerworks/forums/forum.jspa?forumID=2382] pages for known problems. \n * If a fix is found that fits the symptoms, search Fix Central [http://www.ibm.com/support/fixcentral/] for the appropriate interim fix.\n\nRESOLVING THE PROBLEM\nCollect the following troubleshooting data if you need help from IBM Business Process Manager Support to resolve the problem. \n\n\n\nGENERAL DIAGNOSTIC INFORMATION\n\nEnvironment description: \n\n * IBM Business Process Manager product and version * In Business Process Manager V7.5.x, run the versionInfo -maintenancePackages command from the bin directory of your IBM Business Process Manager product installation and redirect the output to a file. \n * In Business Process Manager V8.x, run the versionInfo -fixpacks -ifixes command from the bin directory of your IBM Business Process Manager product installation and redirect the output to a file.\n \n \n * Operating system and version \n * Database vendor and version \n * Information about other involved software \n * Production / Test / QA environment \n * If you are running in a cluster, describe the topology that you have in place. If you have a topology diagram, provide it including host names, ports, and so on. \n * Is your IBM Business Process Manager product running in a virtual machine? If yes, provide more details on the software that you are using and its version.\n\n\nDetailed problem description: \nProvide a precise description of the issue and add every detail that might be related. \nThis could include: * Which symptoms do you see? \n * Which component or application is involved? \n * Do you see any error messages? \n * What is the time stamp when the problem occurs? \n * Did the current scenario work previously? If yes, what has been changed? \n * Is this issue reproducible at will? How often does this problem occur? Do you see any indicators on why this happens? \n * Provide screen shots if applicable (if an error message is not shown or if the specific error is not seen in the log files, and so on)\n\n\nAdditional details needed: \nProvide the complete log directories: * install​​_​​root/​​profiles/profile​​_​​name​​/​​logs​​/server​​_​​name \n * install_​​root/​​profiles/profile​​_​​name/​logs​​/ffdc\n\n\nProvide the configuration files: * TeamWorksConfiguration.running.xml file, which is located in the following locations: * Process Center profile:\n install_​​root/​​profiles/profile​​_​​name/config/cells/cell_name/nodes/\n node_name/servers/server_name/process-center \n * Process Server profile:\n install_​​root​​/​​profiles/profile​​_​​name/config/cells/cell_name/nodes/\n node_name/servers/server_name/process-server\n \n \n * The complete install_​​root/​​profiles/profile​​_​​name/configdirectory if requested by the support team.\n\n\nTest case: * Simplified and isolated test case without any custom dependencies and without access to external customer systems \n * *.twx export from IBM Process Designer \n * Project Interchange (PI) and enterprise archive (EAR) file from the involved Advanced Integration Services, if applicable \n * Exact, detailed steps to reproduce the problem, including timestamp of the problem occurrence.\n\n\nIf you have not provided it already, supply the business impact this issue is having on your company, including:​ * Any upcoming deadlines and dates​ \n * Any realized or potential effect on customers​\n\nCOMPONENT-SPECIFIC DIAGNOSTIC INFORMATION\n \n\n * Advanced Integration Service (AIS) [http://www.ibm.com/support/docview.wss?uid=swg21669894] [http://www.ibm.com/support/docview.wss?uid=swg21618716] \n * Application deployment [http://www.ibm.com/support/docview.wss?uid=swg21618716] \n * Application deployment (EAR file / Advanced content) [http://www.ibm.com/support/docview.wss?uid=swg21959495] \n * Business Process Choreographer (BPC) [http://www.ibm.com/support/docview.wss?uid=swg21270939] \n * Business Process Definition (BPD) [http://www.ibm.com/support/docview.wss?uid=swg21680148] \n * IBM Business Process Manager Advanced Pattern for AIX and Linux [http://www.ibm.com/support/docview.wss?uid=swg21642204] \n * IBM Business Process Manager document store [http://www.ibm.com/support/docview.wss?uid=swg21640607] (for IBM Business Process Manager V8.5.x) \n * IBM Business Process Manager on Cloud [http://www.ibm.com/support/docview.wss?uid=swg21664113] \n * Business Rules [http://www.ibm.com/support/docview.wss?uid=swg21663864] \n * Business Space [http://www.ibm.com/support/docview.wss?uid=swg21578516] \n * Coaches [http://www.ibm.com/support/docview.wss?uid=swg21666382] \n * Common Event Infrastructure (CEI) [http://www.ibm.com/support/docview.wss?uid=swg21670009] \n * Connection to Process Center [http://www.ibm.com/support/docview.wss?uid=swg21666261] \n * Data Map, Data Object and XML Serialization [http://www.ibm.com/support/docview.wss?uid=swg21664250] \n * Database [http://www.ibm.com/support/docview.wss?uid=swg21610455] \n * Dynamic Event Framework (DEF) [http://www.ibm.com/support/docview.wss?uid=swg21679783] \n * Installation and upgrade [http://www.ibm.com/support/docview.wss?uid=swg21506937] \n * Integration between IBM Business Process Manager (BPM) and IBM ILOG or IBM WebSphere Operational Decision Management [http://www.ibm.com/support/docview.wss?uid=swg21644787] \n * Message import and export (MQ and JMS related) [http://www.ibm.com/support/docview.wss?uid=swg21667053] \n * Migration [http://www.ibm.com/support/docview.wss?uid=swg21663802] \n * Out-of-memory, hangs, crashes [http://www.ibm.com/support/docview.wss?uid=swg21666135] \n * Performance [http://www.ibm.com/support/docview.wss?uid=swg21611603] \n * Performance Data Warehouse [http://www.ibm.com/support/docview.wss?uid=swg21609319] \n * Process Admin console [http://www.ibm.com/support/docview.wss?uid=swg21661316] \n * Process Designer [http://www.ibm.com/support/docview.wss?uid=swg21611598] \n * Process Inspector [http://www.ibm.com/support/docview.wss?uid=swg21666266] \n * Process Portal [http://www.ibm.com/support/docview.wss?uid=swg21656267] \n * REST API [http://www.ibm.com/support/docview.wss?uid=swg21666278] \n * Secure Sockets Layer (SSL), Java Secure Socket Extension (JSSE) or Java Cryptography Extensions (JCE) [http://www.ibm.com/support/docview.wss?uid=swg21162961] \n * Security [http://www.ibm.com/support/docview.wss?uid=swg21609418] \n * Service Component Architecture (SCA), Service Integration Bus (SIB) or Failed Event Manager (FEM) [http://www.ibm.com/support/docview.wss?uid=swg21669111] \n * Undercover Agent (UCA) [http://www.ibm.com/support/docview.wss?uid=swg21660915] \n * Web services [http://www.ibm.com/support/docview.wss?uid=swg21593461] \n \n\n\nNote: In the previous information, the install_root refers to the location in which you installed the product. The profile_name is the name of the profile that is specific to your configuration. The cell_name, node_name and server_name are the names of the cell, the node and the server that are specific to your configuration. \nAUTOMATIC DATA COLLECTION VIA THE BPM DATA COLLECTOR\n\nYou can also use the BPM Data Collector [http://www.ibm.com/support/docview.wss?uid=swg21641516] to automatically collect basic MustGather data like logs, version info and so on. Verify the created package if any requested information is missing prior to sending it to IBM Support for problem analysis.\nThis tool can be used with IBM Business Process Manager V8.0.1 Fix Pack 3 and with IBM Business Process Manager V8.5.x.\n\nRELATED INFORMATION\n Exchange data with IBM Technical Support [http://www.ibm.com/de/support/ecurep/index.html]\nBPM Advanced - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023005]\nBPM Standard - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023007]\nBPM Express - System requirements [http://www.ibm.com/support/docview.wss?uid=swg27023008]\nRecommended fixes for IBM BPM [http://www.ibm.com/support/docview.wss?uid=swg27022299]\nConfiguration file overview [http://www.ibm.com/support/docview.wss?uid=swg21439614]\nMustGather for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg21145599]\nTroubleshooting data: WebSphere Process Server [http://www.ibm.com/support/docview.wss?uid=swg21239895]\nTroubleshooting data: IBM Integration Designer [http://www.ibm.com/support/docview.wss?uid=swg21566742]\nTroubleshooting data: WebSphere ESB [http://www.ibm.com/support/docview.wss?uid=swg21268473]\nTroubleshooting data: WebSphere Lombardi Edition [http://www.ibm.com/support/docview.wss?uid=swg21440086]\nTroubleshooting data: IBM Business Monitor [http://www.ibm.com/support/docview.wss?uid=swg21498803]\nA Japanese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21620654]\nA simplified Chinese translation is available [http://www.ibm.com/support/docview.wss?uid=swg21634198]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Documentation AIX, Linux, Solaris, Windows 8.5.7, 8.5.6, 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Documentation Linux, Windows 8.5.7, 8.5.6, 8.5.5, 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM BPM Advanced Pattern on Red Hat Enterprise Linux Server Documentation Linux 8.5.0.1, 8.0.1, 8.0 Business Integration IBM Business Process Manager Advanced Pattern on AIX Documentation AIX 8.0.1 \nPRODUCT ALIAS/SYNONYM\n BPM", "question": "What is the best practice for working with BPM support When working with the BPM product set there are a lot of configuration files, logs and applications which can be exported for analysis by the support team. What are the best practices for working with the BPM support team? ", "answer": "Collect the following troubleshooting data if you need help from IBM Business Process Manager Support to resolve the problem."} +{"id": "TRAIN_Q239", "document": "IBM Security Bulletin:IBM Integration Bus is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client - United States IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere MQ V9.0 libraries are shipped in IBM Integration Bus and hence IBM Integration Bus is vulnerable to IBM WebSphere MQ JMS client deserialization RCE vulnerability.\n\n\n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2016-0360 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0360]\nDESCRIPTION: IBM Websphere MQ JMS client provides classes that deserialize objects from untrusted sources which could allow a malicious user to execute arbitrary Java code by adding vulnerable classes to the classpath. \nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111930 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111930] 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:H/A:H) \n\nPlease consult the security bulletin IBM WebSphere MQ JMS client deserialization RCE vulnerability [https://www-01.ibm.com/support/docview.wss?uid=swg21983457] for more details\n.\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V10.0.0.0 to V10.0.0.9, and V9.0.0.0 to V9.0.0.8\n\nREMEDIATION/FIXES\n \n\nProduct VRMF APAR Remediation/Fix IBM Integration Bus V10.0.0.0 to V10.0.0.9 IT21160 The APAR is available in fix pack 10.0.0.10\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043943 [http://www-01.ibm.com/support/docview.wss?uid=swg24043943] IBM Integration Bus V9.0.0.0 to V9.0.0.8 IT21160 The APAR is available in fix pack 9.0.0.9\nhttp://www-01.ibm.com/support/docview.wss?uid=swg24043947 [http://www-01.ibm.com/support/docview.wss?uid=swg24043947] \nRemediation for users of versions V9.0.0.7, V10.0.0.8 and above: \nIf MQ JMS is used, then you are applicable to this vulnerability. To get around this vulnerability, the following steps are required \n1. Apply the fix for IBM Integration Bus APAR IT21160 \n2. Specify the whiltelist classes as below \n\nmqsichangeproperties -e -o ComIbmJVMManager -n jvmSystemProperty -v \n\neg : mqsichangeproperties -e -o ComIbmJVMManager -n jvmSystemProperty -v \\ \"-Dcom.ibm.mq.jms.whitelist=com.ibm.broker.class1,com.ibm.broker.class2,com.ibm.broker.classn\\\" \n\nRemediation for users of versions prior to V10.0.0.8 and V9.0.0.7: \nYou will need to update MQ. Consult the security bulletin IBM WebSphere MQ JMS client deserialization RCE vulnerability [https://www-01.ibm.com/support/docview.wss?uid=swg21983457] for details. \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\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Matthias Kaiser of Code White (www.code-white.com) \n\nCHANGE HISTORY\n 29 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. \n\n\n\nPRODUCT ALIAS/SYNONYM\n IIB", "question": "Help with Security Bulletin: IIB is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client I need to understand details regarding Security Bulletin:IBM Integration Bus is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client (related to CVEID: CVE-2016-0360). Where can I find this information? ", "answer": "CVEID: CVE-2016-0360 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-0360]\nDESCRIPTION: IBM Websphere MQ JMS client provides classes that deserialize objects from untrusted sources which could allow a malicious user to execute arbitrary Java code by adding vulnerable classes to the classpath. \nCVSS Base Score: 8.1\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/111930 [https://exchange.xforce.ibmcloud.com/vulnerabilities/111930] 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:H/A:H)"} +{"id": "TRAIN_Q240", "document": "IBM CICS Transaction Server for z/OS 3.1 and 3.2 End of Support announcement - United States CICS TS 3.2 3.1 ; EOS; end of support; out of support; product lifecyle; end of lifecycle; withdrawal from support; withdrawn from support ; out of support; withdrawal announcement letter 5655M1500 R640 640 R400 400 HCI6400 R650 650 R500 500 HCI6500 5655-M15 5655M15; KIXINFO retention32 PRODUCT LIFECYCLE\n\nABSTRACT\n CICS Transaction Server for z/OS (CICS TS) V3.1 and V3.2 was withdrawn from support 31 December 2015. CICS TS Service Flow Feature V3.1 was also be withdrawn from support on the same date. This document contains a link to the Software service discontinuance announcement letter and product replacement information. \n\nCONTENT\nThe Software service discontinuance announcement letter that says CICS TS V3.1, CICS TS V3.2, and CICS TS Service Flow Feature V3.1 was withdrawn from support 31 December 2015 is 913-075 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS913-075]. \n\nThe following product replacement information is included in this announcement: \n\nProgram Program\nWithdrawn program number Replacement program number\n\nCICS TS V3.1 5655-M15 CICS TS V4.2 5655-S97\n\nCICS TS V3.2 5655-M15 CICS TS V4.2 5655-S97\n\nCICS TS Service CICS TS Service Flow\nFlow Feature V3.1 5655-M15 Feature V3.2 5655-M15\n\nNote: For additional information, refer to Software Announcement 211-080 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS211-080], dated April 05, 2011 . CICS TS V5.1 is also available and may be considered as a replacement product for CICS TS V3. For details, refer to Software Announcement 212-325 [http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&appname=gpateam&supplier=897&letternum=ENUS212-325], dated October 03, 2012 .\n\nSee the Announcement Letters for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21227090] if you are interested in upgrading to the latest release of CICS TS or any other CICS products.\n\nA fee based service extension for CICS TS for z/OS V3.1 or V3.2 might be available from IBM, if you need more time to upgrade. A service extension entitles you to continue to receive the level of support that you receive today using the same channels into IBM, including raising PMRs and APARs. If you would like to find out more about CICS service extensions, contact your local IBM Sales Representative: \n\n * US Customers, contact Customer Support Operations at 877-426-6006 option #2. If you give the support representative your customer number they can find your sales representative. \n \n \n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region.\n IBM directory of worldwide support contacts [http://www.ibm.com/planetwide/]\n \n \n\nFor more information about the availability of support extensions see IBM software support lifecycle policy [http://www.ibm.com/software/support/lifecycle/lc-policy.html] page. \nRELATED INFORMATION\n Announcement letters for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21227090]\nEnd of Service dates for CICS products [http://www.ibm.com/support/docview.wss?uid=swg21154953]\nCICS TS 4.1 and 4.2 End of Service dates [https://developer.ibm.com/answers/questions/182094/cics-transaction-server-for-zos-41-and-42-end-of-s.html]\n\n\n\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "question": "End of support date for CICS TS 3.2 change from 2016 to 2015 Did the end of support date for Transaction Server for z/OS (CICS TS) 3.2 change in June 2015? Earlier this year, the date was December 2016 now it appears to be December 2015! ", "answer": "The Software service discontinuance announcement letter that says CICS TS V3.1, CICS TS V3.2, and CICS TS Service Flow Feature V3.1 was withdrawn from support 31 December 2015 is 913-075"} +{"id": "TRAIN_Q241", "document": "IBM TroubleShooting: JavaServer Pages (JSP) problems - United States JSPs; TroubleShootingDocument; troublehooting TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Troubleshooting JSP problems for WebSphere® Application Server. This should help address common issues with this component before calling IBM support and save you time. \n\nRESOLVING THE PROBLEM\nThe following are some examples of common JSP problems and some basic information on how to resolve them: \n\n * java.io.FileNotFoundException: JSPG0036E: Failed to find resource\n If the browser displays a JSPG0036E: Failed to find resource message, the JSP processor cannot find the specified JSP page in the Web module, as shown below.\n \n java.io.FileNotFoundException: JSPG0036F: Failed to find /Tests/index.jsp\n at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.findWrapper (JSPExtensionProcessor.java:246)\n at com.ibm.ws.jsp.webcontainerext.JSPExtensionProcessor.handleRequest (JSPExtentionProcessor.java:228)\n ... \n Take following steps to verify URL being requested order to debug this exception:\n \n To determine the URL of the installed application, you need to use the administrative console to view the configuration of a number of items. The format of the URL is as follows:\n \n http://host:port/context_root/resource_name \n Finding :\n When a Web module is installed, a virtual host is associated with it. To find the virtual host using the WebSphere Application Server administrative console: 1. Select Applications > Application type > WebSphere Enterprise Applications.\n \n \n 2. Select the application name to open the details page.\n \n In the Web module Properties section, click Virtual hosts.\n \n \n 3. Note the virtual hosts that are used by the specified application Web module.\n \n \n To find the host and port numbers that are valid for the virtual host: 1. Select Environment > Virtual Hosts.\n \n \n 2. Choose the virtual host, and then under Additional Properties, click Host Aliases.\n \n \n 3. The list contains the host name and port combinations that can be used to access this virtual host. The host name column should contain values that are registered in a DNS server as a host name for the WebSphere Application Server. An asterisk (*) in the host column indicates that any name can be used. In this case, use the server host name.\n \n \n Finding \n The context root is the Web application root and is used to identify the application in the URI. To find the context root: 1. In the WebSphere Application Server administrative console, click Applications > Application type > WebSphere Enterprise Applications.\n \n \n 2. Select the target application, then under Detail Properties, click View Deployment Descriptor.\n \n \n 3. Review the tag for the specified Web module in the related deployment descriptor tag.\n \n \n Finding \n To find the initial file for the application (for example, index.jsp), you can look at the welcome file list in the Web deployment descriptor. As per J2EE specification, JSP files should reside under web module root or under sub directory other than META-INF and WEB-INF.\n \n For example: * Web module root :\n \n install_root\\profiles\\profile_name\\installedApps\\\\ \n \n \n In the preceding case, the index.jsp file should reside uner Web_module_root/Test directory. If not, than it explains this error message. \n \n * JSP not reloading\n If, after modifying and saving a JSP file, the change does not show up in the browser, you need to check the reload settings in the Web module configuration and the JSP runtime reload settings. For the JSPs, the Web container reloads a Web module only when the IBM extension reloadingEnabled in the ibm-web-ext.xmi file is set to true.\n \n The following is an example of web module reloading settings in the ibm-web-ext.xmi file:\n \n \n Location of the ibm-web-ext.xmi file :\n \n install_root\\profiles\\profile_name\\config\\cells\\cell_name\n \\applications\\\\deployments\\app_name\\\\WEB-INF\\ibm-web-ext.xmi \n Configuring JSP runtime reloading:\n You have the ability to modify the JSP processor behavior for different JSP stages (such as development, testing, or production environments). This done by configuring specific attributes in the IBM Web module extensions that affect the JSP runtime reload behavior.\n \n JSP files can be translated and compiled at runtime when the JSP file or its dependencies are modified. This is known as JSP reloading. JSP reloading is enabled through the reloadEnabled JSP engine parameter in the ibm-web-ext.xmi configuration file.\n \n The JSP engine settings are stored in the ibm-web.ext.xmi file, as shown \n \n \n \n * Encoding and internationalization issues\n Encoding and internationalization problems usually showup as garbage characters in Web pages and input from user interpreted incorrectly. Double Byte Character Set (DBCS) character processing is a common issue for encoding problems. DBCS is used for languages such a Chinese, Korean, and Japanese, where a single byte is not sufficient to represent all characters in the alphabet. Proper coding and configuration usually resolves these problems. For JSP pages, page encoding is the character encoding in which the file is encoded. For JSP pages in standard syntax, the page encoding is determined from the following sources: 1. The pageEncoding attribute of the page directive of the page \n 2. The charset value of the contentType attribute of the page directive\n \n \n If none of these is provided, ISO-8859-1 is used as the default page encoding.\n \n Page directive implementation in JSP code:\n \n \n \n <%@ page language=\"java\" contentType=\"text/html; charset=UTF-8\" pageEncoding=\"ISO-8859-15\" %>\n \n Receiving parameters\n \n \n

\n Your data is <%= request.getParameter(\"name\") %>\n

\n \n \n The pageEncoding and contentType attributes determine the page character encoding of only the file that physically contains the page directive. \n \n * java.lang.IllegalStateException\n This exception is thrown when attempt is made to modify HttpServletResponse object after it has been committed.\n \n If you have written something in the response buffer, you cannot forward a page:\n \n [7/8/05 20:36:25:694 ART] 0000004f ServletWrappe E SRVE0068E: Could not invoke the service() method on servlet TestServlet. Exception thrown : java.lang.IllegalStateException\n at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendRedirect(WebAppDispatcherContext.java:486)\n at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendRedirect(SRTServletResponse.java:810)\n ...\n [7/8/05 20:36:25:784 ART] 0000004f SRTServletRes W WARNING: Cannot set status. Response already committed. \n Calls to the following methods, after a committing response, will cause the java.lang.IllegalStateException error to occur: 1. setBufferSize(0) \n 2. reset() \n 3. resetBuffer() \n 4. sendError() \n 5. sendRedirect() \n 6. RequestDispatcher.forward() or performing jsp:forward\n \n \n Two other common variants of this exception are: \n java.lang.IllegalStateException: Header already sent \n One or more headers have been committed to the client, so you cannot set that header again. \n java.lang.IllegalStateException: OutputStream already obtained \n In case of JSP, the default output stream has always been created when the JSP has been translated to servlet. Creating and associating another output stream is the reason for this problem. The following piece of code will describe the reason for this error condition: \n try\n {\n lStream = pResponse.getOutputStream();\n lStream.write(lDocument);\n lStream.flush();\n }\n catch (java.io.IOException ioe)\n {\n logger.error(\"Exception writing ... to page output stream.\");\n }\n finally\n {\n try\n {\n if (lStream != null)\n {\n lStream.close();\n }\n }\n catch (java.io.IOException ioe)\n {\n logger.error(\"Exception closing page output stream.\");\n }\n } \n Two output streams cannot be associated with one JSP file. \n \n\nWhat to do next \nIf the preceding troubleshooting steps did not help solve your problem, see the MustGather [http://www.ibm.com/support/docview.wss?rs=180&uid=swg21255205] for JSP problems. \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "java.lang.IllegalStateException when I'm trying to stop a service in BPM Process Admin Console \n\nIn the Process Admin Console, under Monitoring > Process Monitor, when I try to stop a service, I get the following exception: java.lang.IllegalStateException: SRVE0199E: OutputStream already obtained\n\nWhat is causing this?", "answer": "java.lang.IllegalStateException\n This exception is thrown when attempt is made to modify HttpServletResponse object after it has been committed."} +{"id": "TRAIN_Q242", "document": "IBM After upgrading to 7.0.1.0 you get SSL error AMQ9716 - United States AMQ9716 7.0.1.0 SSL OCSP SSL TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You upgrade to WebSphere MQ 7.0.1.0 (or later) and have SSL enabled channels. After the upgrade you notice that in the Queue Manager error LOGs you see the following error message:\n\nAMQ9716: Remote SSL certificate revocation status check failed for channel '????'. \nThe channel does not start. \n\nSYMPTOM\nError AMQ9716\n\n\nCAUSE\nWith the release of WebSphere MQ V7.0.1.0 the use of OCSP certificate revocation checking was included. With this new feature, most likely your SSL certificates have a OCSP AuthorityInfoAccess (AIA) certificate extension embedded inside them. \n\n\nThis was ignored before V7.0.1.0. Now it is being used to verify the certificate. The most likely cause of the failure is that the system can not access the servers listed in the AIA. This then returns a UNKNOWN status when the check is done. The default action for MQ is to not allow the channel to start and the AMQ9716 to be reported when the UNKNOWN is returned.\n\n\nRESOLVING THE PROBLEM\nThe best thing to do in this case is to determine the cause of the UNKNOWN return code and fix it. \n\n\nThere are two possible methods to discover which OCSP AuthorityInfoAccess URL is embedded in a certificate. \n\nMethod 1.\nPlace the certificate on a Windows machine; ensure to use a file extension of \"crt\" and double-click it. View the detail extensions for the AIA. \n\n[/support/docview.wss?uid=swg21399255&aid=1]\n\nMethod 2\nUse IBM Key Management (gskit) GUI to view them. Issue the following command::\nIn Windows: strmqikm \nIn UNIX: gsk7ikm (MQ V7) or runmqckm (MQ V8)\n\nFrom the IBM Key Management window:\nSelect View/Edit for certificate\nView Details\nExtensions\nAuthorityInfoAccess\n\n[/support/docview.wss?uid=swg21399255&aid=2]\n\nThe first step would be to insure that connection to the URL in your certificate can be reached.\n\n\nWork-around:\nUse this only as a temporary fix until the root cause can be found.\nYou can do the following. It will still do OCSP checking and if REVOKED is returned then the channel will not start. A GOOD return code will allow the channel to start. If UNKNOWN is returned it will not stop the channel from starting and the AMQ9716 will not be reported.\n\nUNIX and Linux systems add the following to qm.ini\nSSL:\nOCSPAuthentication=OPTIONAL\n\nTo set for a Windows Queue Manager, run the following command:\namqmdain reg YourQMgrName -c add -s SSL -v OCSPAuthentication=OPTIONAL\n\nThe OCSPAuthentication setting is also applicable to clients and can also be set in the client ini file (e.g. mqclient.ini). Changes to the client OCSPAuthentication setting will take effect after the application is restarted.\n\nOn a queue manager, users will need to issue a REFRESH SECURITY TYPE(SSL) command (or the GUI/PCF equivalent) in order for the change in SSL settings to take effect.\n\nOCSP provides your SSL channels with additional security. Once the cause of the AMQ9716 error has been addressed then you are strongly recommended to re-enable OCSP enforcement\n\nRELATED INFORMATION\n OCSP Info [http://www.ibm.com/support/knowledgecenter/SSFKSJ_7.1.0/com.ibm.mq.doc/sy13000_.htm?lang=en]\n\n\n \n\nPRODUCT ALIAS/SYNONYM\n WMQ MQ", "question": "Getting Delay or AMQ9716: Remote SSL certificate revocation status check failed when trying to start a MQ SSL channel, why? Getting Delay or AMQ9716: Remote SSL certificate revocation status check failed when trying to start a MQ SSL channel, please help resolve this? The error can occur on the MQ server or also a MQ client application..\n\nAMQ9716: Remote SSL certificate revocation status check failed\n\nRemote SSL certificate revocation status check failed for channel '???'.\n\nEXPLANATION: WebSphere MQ failed to determine the revocation status of the remote SSL\ncertificate for one of the following reasons:\n\n(a) The channel was unable to contact any of the CRL servers or OCSP responders for the certificate.\n(b) None of the OCSP responders contacted knows the revocation status of the certificate.\n(c) An OCSP response was received, but the digital signature of the response could not be verified.", "answer": "With the release of WebSphere MQ V7.0.1.0 the use of OCSP certificate revocation checking was included. With this new feature, most likely your SSL certificates have a OCSP AuthorityInfoAccess (AIA) certificate extension embedded inside them. \n\n\nThis was ignored before V7.0.1.0. Now it is being used to verify the certificate. The most likely cause of the failure is that the system can not access the servers listed in the AIA. This then returns a UNKNOWN status when the check is done. The default action for MQ is to not allow the channel to start and the AMQ9716 to be reported when the UNKNOWN is returned."} +{"id": "TRAIN_Q243", "document": "IBM OMEGAMON XE MQ Monitoring Agent Issue the ALTER QLOCAL Command - United States ALTER QLOCAL command event TECHNOTE (FAQ)\n\nQUESTION\n We have the OMEGAMON XE for Messaging on zOS. The agent is configured to monitor all the queue managers (QMGRS) on the same lpar, however, we can see the agent sometimes issues the 'alter Qlocal' command on a QMGR. Why is the agent issuing this command? \n\nANSWER\nWhen a queue full event occurs, WebSphere MQ will disable the event. To ensure that subsequent queue full events will occur, the OMEGAMON XE for Messaging agent will re-enable the queue full event once it determines the queue is no longer full via an ALTER QL(qname) QDPMAXEV(ENABLED) command. Other than Take Action commands, this is the only ALTER command that the OMEGAMON XE for Messaging agent will issue.", "question": "We have the OMEGAMON XE for Messaging on zOS. The agent is configured to monitor all the queue managers (QMGRS) on the same lpar, however, we can see the agent sometimes issues the 'alter Qlocal' command on a QMGR We have the OMEGAMON XE for Messaging on zOS. The agent is configured to monitor all the queue managers (QMGRS) on the same lpar, however, we can see the agent sometimes issues the 'alter Qlocal' command on a QMGR. Why is the agent issuing this command?", "answer": "When a queue full event occurs, WebSphere MQ will disable the event. To ensure that subsequent queue full events will occur, the OMEGAMON XE for Messaging agent will re-enable the queue full event once it determines the queue is no longer full via an ALTER QL(qname) QDPMAXEV(ENABLED) command. Other than Take Action commands, this is the only ALTER command that the OMEGAMON XE for Messaging agent will issue."} +{"id": "TRAIN_Q244", "document": "IBM Security Bulletin: Multiple vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository Studio (CVE-2015-4872, CVE-2015-4911, CVE-2015-4893, CVE-2015-4803) - United States SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM® SDK Java™ Technology Edition that is shipped with IBM WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in October 2015. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4872 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4872]\n\nDESCRIPTION: An unspecified vulnerability related to the Security component has no confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107361 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107361] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:P/A:N)\n\nCVEID: CVE-2015-4911 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4911]\n\nDESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107360 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107360] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2015-4893 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4893]\n\nDESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107359 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107359] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nCVEID: CVE-2015-4803 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4803]\n\nDESCRIPTION: An unspecified vulnerability related to the JAXP component could allow a remote attacker to cause a denial of service.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107358 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107358] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:N/A:P)\n\nAFFECTED PRODUCTS AND VERSIONS\n WebSphere Service Registry and Repository Studio V8.5, V8.0, V7.5 and V7.0 are affected.\n\nREMEDIATION/FIXES\nNote regarding CVE-2015-4911\nThis was addressed by IBM in June 2008. As a reminder, users of Java 6 and above should\nrefer to the IBM XL XP-J documentation [https://www-01.ibm.com/support/knowledgecenter/api/content/nl/en-us/SSYKE2_7.0.0/com.ibm.java.win.70.doc/user/xml/xlxpj_reference.html] for the javax.xml.stream.supportDTD property\nfor information to help avoid this vulnerability.\n\nFor all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.0_IV79089_IV80119_IV80540_IV80888 [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm/WebSphere&product=ibm/WebSphere/WebSphere+Service+Registry+and+Repository&release=All&platform=All&function=fixId&fixids=8.5.6.0-WS-WSRR-Studio-MultiOS-IFIV79089_IV80119_IV80540_IV80888&includeRequisites=1&includeSupersedes=0&downloadMethod=ddp&source=fc] \n\n\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] \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 February 2016: 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.", "question": "Help with Security Bulletin: Multiple vulnerabilities identified in IBM Java SDK affect WSRR Studio (CVE-2015-4872) I need to understand details regarding Security Bulletin: Multiple vulnerabilities identified in IBM® Java SDK affect WebSphere Service Registry and Repository Studio (CVE-2015-4872). Where can I find this information? ", "answer": "CVEID: CVE-2015-4872 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-4872]\n\nDESCRIPTION: An unspecified vulnerability related to the Security component has no confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/107361 [https://exchange.xforce.ibmcloud.com/vulnerabilities/107361] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N/AC:L/Au:N/C:N/I:P/A:N)"} +{"id": "TRAIN_Q247", "document": "IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States FIXES ARE AVAILABLE\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 * If base entry and name in repository is different and\n clearCache functionality is used with clearEntity mode then\n virtual member manager (VMM) still looks in the cache and gets\n the entity from the cache instead of fetching it from the LDAP\n server.\n \n \n \n \n \n\nLOCAL FIX\n * test fix\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server V8.0 and V8.5 virtual member *\n * manager (VMM) *\n ****************************************************************\n * PROBLEM DESCRIPTION: Clear cache does not work if *\n * clearEntity *\n * mode is used. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n LDAP Clear cache functionality of VMM does not work when using\n clearEntity mode. Problems occur only if there is a different\n base entry used than the name in the repository entry.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * This APAR fixes the issue. It clears the cache properly even if\n base entry is different than name in repository.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.9. Please refer to the\n Recommended Updates 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 PI47826\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 800\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-08-28\n \n \n * CLOSED DATE\n 2015-12-09\n \n \n * LAST MODIFIED DATE\n 2015-12-09\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 * R800 PSY\n UP\n \n \n * R850 PSY\n UP", "question": "Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time? You are leveraging the reload() functionality as described in the blog post:\n https://www.ibm.com/developerworks/community/blogs/PortalL2Thoughts/entry/how_to_programatically_refresh_data_from_ldap64?lang=en\n\nto refresh the attribute cache after a change has been made to data within your LDAP. The purpose of this reload() is to update the data in real time on the Portal server. You discover that you are calling the reload(); however, the newly updated data is not immediately available to the application. How can this be fixed?\n", "answer": "This APAR fixes the issue. It clears the cache properly even if\n base entry is different than name in repository.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.9."} +{"id": "TRAIN_Q248", "document": "IBM WebSphere Message Broker Version 8.0 Readme - United States readme readme reademe readmes readmes; ReadmeDocument PRODUCT README\n\nABSTRACT\n This document contains the IBM WebSphere Message Broker Version 8.0.0.9 Readme \n\nCONTENT\nIBM WebSphere Message Broker Version 8.0 Readme\n\n\n\n\nReadme documentation for IBM WebSphere Message Broker Version 8.0.0.9 including the Runtime, Toolkit and Explorer components. \n\nReadme file for: IBM WebSphere Message Broker\nProduct/Component Release: 8.0\nUpdate Name: 8.0.0.9\n\nPublication date: 09 December 2011\nLast modified date: 30 June 2017 \n\nContents \n\n * Installation information: * Prior to installation \n * Installing \n * Essential information if you are migrating \n * Documentation \n * Support \n * Feature updates\n \n \n * Known problems and their workarounds (if any): * Installation \n * Platforms \n * Migration \n * WebSphere Message Broker Explorer \n * WebSphere Message Broker Toolkit \n * Web Services \n * Web UI \n * Nodes \n * WebSphere Adapter nodes \n * Graphical Data Mapper \n * Commands \n * Databases \n * Samples\n \n \n * Copyright and trademark information \n * Useful websites \n * Document change history\n\nInstallation information: Always use the latest version of this readme file, which is available in English only at:\nhttp://www.ibm.com/support/docview.wss?uid=swg27006917 [http://www.ibm.com/support/docview.wss?uid=swg27006917] \n\nTranslated readme files are available at:\nftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/ [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/] \n\nPrior to installation \n\nFor information about the tasks you must complete before you install the product, refer to the WebSphere Message Broker V8.0 documentationat: \n\nhttp://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html]\n\n\nCheck the WebSphere Message Broker system requirements to ensure that your installation platform is supported for the product edition that you are planning to install. The WebSphere Message Broker system requirements web page is available at:\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/ [http://www.ibm.com/software/integration/wbimessagebroker/requirements/] \n\nTwo editions of WebSphere Message Broker V8.0 are available on Windows: \n\n * WebSphere Message Broker V8.0 Windows x86 (32-bit Broker runtime component) WebSphere Message Broker V8.0 Windows x86-64 (64-bit Broker runtime component) \n\nThe 64-bit edition of WebSphere Message Broker is not supported on all 64-bit versions of the Windows Operating System. For more information, see the WebSphere Message Broker system requirements web page. Installing \n\nApplying service to z/OS \n\nIf you are applying service to z/OS, the Program Temporary Fix (PTF) packages must be downloaded as binary files, and then transferred to z/OS:\n1. Download the PTF packages as binary files from the WebSphere Message Broker Support Site at http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker [http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker] and save the files to your workstation.\n2. Allocate sequential datasets with the following attributes: \n\n * \n * \n * Record format . . . : FB \n * Record length . . . : 1024 \n * Block size . . . . : 6144 \n * 1st extent tracks . : 500 \n * Secondary tracks . : 50\n\n\nYou can use the following sample Job Control Language (JCL) to allocate these datasets: * \n * \n * INSERT A VALID JOBCARD HERE\n * //* \n * //ALLOCATE EXEC PGM=IEFBR14 \n * //SYSMOD1 DD DSN=YOUR HIGH LEVEL QUALIFIER (HLQ).PTF NUMBER.TRS, \n * // DISP=(NEW,CATLG,DELETE), \n * // UNIT=SYSDA, \n * // SPACE=(TRK,(500,50),RLSE), \n * // DSORG=PS, \n * // DCB=(RECFM=FB,LRECL=1024,BLKSIZE=6144) \n * //*\n\n3. Transfer the binary files from your local workstation to z/OS. File Transfer Protocol (FTP) can be used to transfer the files to the target z/OS as binary files by using the replace option, for example: put PTF NUMBER.TRS 'YOUR HLQ.PTF NUMBER.TRS' (replace\n4. Unpack the datasets using the TRSMAIN utility program. This utility is freely available at http://techsupport.services.ibm.com/390/trsmain.html [http://techsupport.services.ibm.com/390/trsmain.html]. \n\nYou can use the following sample JCL to unpack the datasets after the changes have been made, and a suitable job card added: \n\n * \n * \n * //* UNTERSE APAR \n * //***************************************************** \n * /UNPACK EXEC PGM=TRSMAIN,PARM='UNPACK' \n * //STEPLIB DD DISP=SHR,DSN=TERSE.LOADLIB \n * //SYSPRINT DD SYSOUT=* \n * //INFILE DD DSN=YOUR HLQ.PTF NUMBER.TRS, \n * // DISP=SHR \n * //OUTFILE DD DSN=YOUR HLQ.PTF NUMBER, \n * // DISP=(NEW,CATLG), \n * // SPACE=(TRK,(1000,100,)) \n * /*\n\n5. Apply the resulting files using System Modification Program/Extended(SMP/E) for z/OS RECEIVE and APPLY. \n\n\n\n\nEssential information if you are migrating If you are migrating from WebSphere Message Broker version 6.1 or version 7.0, refer to the online information center at http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp [http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp], which provides detailed information about how to migrate. \n\n\n\n\n\n\n\nDocumentation The online product documentation for WebSphere Message Broker V8.0 is available at: \nhttp://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html] \n\nAlways refer to the online product documentation for the latest information. The online product documentation contains newer information than the information center shipped with the Message Broker Toolkit. \n\nThe WebSphere Message Broker product documentation for V8.0.0.0 contains documentation for recording and viewing data. However, it does not contain information about replaying data. A PDF has been provided with the most up-to-date and comprehensive documentation about recording, viewing, and replaying data in V8.0.0.0. To download the PDF, see the technote at:\nwww.ibm.com/support/docview.wss?uid=swg21573603 [http://www.ibm.com/support/docview.wss?uid=swg21573603] \n\nThe WebSphere Message Broker product documentation for V8.0.0.1 contains up-to-date information about the web user interface. However, the following technotes contain additional information to supplement the topics in the product documentation: \n\n * For information about accessing the web user interface, see www.ibm.com/support/docview.wss?uid=swg21606634 [http://www.ibm.com/support/docview.wss?uid=swg21606634] For information about accessing data and resources in the web user interface, see www.ibm.com/support/docview.wss?uid=swg21606640 [http://www.ibm.com/support/docview.wss?uid=swg21606640] \n\nThe stand-alone information center is available for download at: \nftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_linux.tgz [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_linux.tgz] (Linux version) \nftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_win.zip [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_win.zip] (Windows version) \n\nRead the using_the_infocenter.html file that is included in the ibm_help folder in the wmb_help_linux.tgz and wmb_help_win.zip files. \n\n\n\n\n\n\nSupport Defects: This readme file might contain references to defect numbers. These numbers refer to internal IBM problem numbers; you might find these numbers useful when discussing problems with your IBM service representative. \n\nTechnotes: For current information about known problems and available fixes, see the WebSphere Message Broker support website at:\nhttp://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker [http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_Message_Broker] \n\nTo find information, click Troubleshoot. WebSphere Message Broker Technotes are displayed and can be ordered and searched. \n\nFor information about downloading WebSphere Message Broker Version V8.0 installation images from the Passport Advantage website, see the Download WebSphere Message Broker V8.0 from the Passport Advantage website download document, which is available at:\nhttp://www.ibm.com/support/docview.wss?uid=swg24030968 [http://www.ibm.com/support/docview.wss?uid=swg24030968] \n\nVersions: For the latest information about which particular versions of operating system and databases are supported by WebSphere Message Broker, consult the system requirements page at:\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/index.html [http://www.ibm.com/software/integration/wbimessagebroker/requirements/index.html] \n\n\n\n\n\n\n\nFeature updates Check periodically for updates to the WebSphere Message Broker Toolkit, including documentation updates in English and in other supported languages. Recommended fixes for WebSphere Message Broker can be found at: \nhttp://www.ibm.com/support/docview.wss?uid=swg27006041 [http://www.ibm.com/support/docview.wss?uid=swg27006041] \n\nDetails of what's new in Version 8.0 can be found at: \n\nhttp://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bb23110_.htm [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bb23110_.htm]\n\n\n\n\n\nTOP Known problems and their workarounds (if any): This section outlines the known problems and their workarounds (if any) of WebSphere Message Broker, by component. \n\n\n\n\n\n\nTOP Installation \n * Windows: Uninstallation executable program is not signed Symptoms: \n \n If you run the WebSphere Message Broker uninstallation program uninstaller.exe, and you are using Windows 7 or Windows Server 2008 R2, a dialogue might be displayed warning that the uninstallation file is unsigned. \n \n Solution: \n \n This warning can be safely ignored. Continue with the uninstallation process. \n \n \n \n * Windows: Attachment Manager Symptoms: \n \n If you are installing an IBM product by using an electronic image from IBM Passport Advantage, and you are using Windows XP Service Pack 2 or later, your Windows Security settings might cause Attachment Manager to block the content of the installer .zip file, causing your installation to fail. \n \n Solution: \n \n To work around this problem, complete the following steps: \n \n * \n * \n * \n * Properties\n * \n * \n * \n * General\n * \n * Unblock\n * \n \n \n For more information about Windows Attachment Manager, refer to the Microsoft Support site at: http://support.microsoft.com/kb/883260 [http://support.microsoft.com/kb/883260]\n \n * HP-UX: Runtime component supplied on a physical DVD The installation image for the WebSphere Message Broker V8.0 GA runtime component has exceeded the 700 MB limit recommended for a physical CD. For this reason, the installation image for the HP-UX platform is supplied on a physical DVD rather than a physical CD. The installation image for the WebSphere Message Broker V8.0 GA runtime component is also available from the Passport Advantage website. For information about downloading WebSphere Message Broker Version V8.0 installation images from the Passport Advantage website, see the Download WebSphere Message Broker V8.0 from the Passport Advantage website download document, which is available at:\n http://www.ibm.com/support/docview.wss?uid=swg24030968 [http://www.ibm.com/support/docview.wss?uid=swg24030968]\n \n \n \n * Installing using the fix pack installer Symptoms: \n \n The WebSphere Message Broker V8.0.0.0 GA runtime installer requires that you accept the license agreement.\n The fix pack installer requires either that you install on a system that already has WebSphere Message Broker V8.0 GA installed, or that you provide the original WebSphere Message Broker V8.0 GA license files. The WebSphere message Broker V8.0 GA license files can be from either an existing V8.0 runtime installation, or from the original V8.0 installation media. The location of the license files is required only when you are installing a WebSphere Message Broker V8.0 fix pack on a system on which an installation of WebSphere Message Broker V8.0 GA has not been detected. \n \n Solution: \n \n GUI or Console installations\n For a fix pack GUI or console installation where V8.0 does not already exist on the system, the installer will prompt you to provide the path to existing media licenses or an existing installation of V8.0.\n Where V8.0 is already installed on the system, you should not be prompted for existing licences, and the installation will progress as normal. \n \n Silent installations\n For silent installations (full media or fixpack) you must always accept the license, so for example \n \n \n For a full GA silent media installation\n Add the argument: -DLICENSE_ACCEPTED=TRUE to your silent command, or to the response file you have referenced\n For example on windows command line\n setup32.exe -i silent -DLICENSE_ACCEPTED=TRUE\n \n For a fix pack silent installation where V8.0 already exists on the system\n Add the argument: -DLICENSE_ACCEPTED=TRUE to your silent command, or to the silent response file you have referenced\n For example on windows command line\n 8.0.0-WS-MB-WINIA32-FP0001.exe -i silent -DLICENSE_ACCEPTED=TRUE\n \n For a fix pack silent installation where V8.0 does not already exist on the system\n Also add the argument: -DExternal_License_Path= to your silent command, or to the silent response file you have referenced\n For example on windows command line pointing at the original media in the D: drive\n 8.0.0-WS-MB-WINIA32-FP0001.exe -i silent -DLICENSE_ACCEPTED=TRUE -DExternal_License_Path=\"D:\\messagebroker_ia_runtime1\\license\n \n Note if pointing at an existing installation of V8.0.0.0 the path is subtly different\n For example on windows command line pointing at the original media in the D: drive\n 8.0.0-WS-MB-WINIA32-FP0001.exe -i silent -DLICENSE_ACCEPTED=TRUE -DExternal_License_Path=\"C:\\Program Files\\IBM\\MQSI\\8.0.0.0\\license\\8.0.0.0\"\n \n \n\n\n\n * Instructions for installing the WebSphere Message Broker runtime and ODBC Database Extender components with a non-root user ID Symptoms: \n \n In the information center topic \"Security on Linux and UNIX systems\" (bh26031), steps 3d) and 3e) for installing the runtime and ODBC Database Extender (IE02) components with a non-root user ID are incorrect. If you follow the steps described in the topic, the product will not install correctly. \n \n Solution: \n \n Replace steps 3d) and 3e) in the topic with the following new steps 3d) to 3i):\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 * /opt/ibm/mqsi and /opt/ibm/IE02 (for Linux) For example: SUDO mkdir /opt/ibm/mqsi\n SUDO mkdir /opt/ibm/IE02\n \n \n /opt/IBM/mqsi and /opt/IBM/IE02 (for UNIX and AIX). For example:\n SUDO mkdir /opt/IBM/mqsi\n SUDO mkdir /opt/IBM/IE02 \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\nTOP Platforms \n\nUbuntu WebSphere Message Broker is supported on Ubuntu, but only for development systems. Production systems should not be used to run WebSphere Message Broker on Ubuntu. \n\nFor more information, see the WebSphere Message Broker system requirements page. The WebSphere Message Broker system requirements web page is available at:\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/ [http://www.ibm.com/software/integration/wbimessagebroker/requirements/] \n\n\n * Unable to connect a node that has multiple output terminals to other nodes (116214) Symptoms \n \n When attempting to connect a node that has multiple output terminals to other nodes, a connection is not created. \n \n Solution \n \n To work around this problem, complete one of the following steps: \n \n * Set the following environment variable: GDK_NATIVE_WINDOWS=1 \n \n OR * Use a different window manager \n \n \n\nSolaris and HP-UX \n * Increase in bipbroker and DataFlowEngine memory footprint on Solaris and HP-UX platforms Symptoms \n \n When upgrading from 8.0.0.1 to 8.0.0.2, bipbroker and DataFlowEngine processes running on Solaris or HP platforms might consume an additional 204 MB of memory. This is caused by an increase in the default size of the ReservedCodeCacheSize parameter in the Java Virtual Machine (JVM) used by the broker processes. This area of memory is related to the just-in-time compilation of Java classes and was increased by the JVM supplier in response to an increase in bug reports from third party products failing due to exhaustion of space in the code cache. \n \n Solution \n \n Customers should use the default value for this parameter, but if this causes unnecessary resource contention, the default can be reverted to its former value by exporting the following environment variable in the broker's profile prior to starting the broker: \n \n * \n * \n \n \n\nAIX * DataFlowEngine abend on AIX when resolving hostname \n \n Symptoms\n The DataFlowEngine process running on AIX may terminate on startup or during a deploy with the following call stack in the abend/core file: \n calloc [] \n getaddrinfo [] \n Java_java_net_Inet6AddressImpl_lookupAllHostAddr \n \n Solution\n Apply AIX equivalent APAR fix for IV95824.\n Alternatively apply one of the following workarounds: \n 1) Specify hosts resolution order in /etc/netsvc.conf so that IPv4 is resolved first. For example: \n hosts=local4,bind4 \n 2) Export the following environment variable setting: \n IBM_JAVA_OPTIONS=-Djava.net.preferIPv4Stack=true \n \n \n\n\n\n\n\nTOP Migration \n * Brokers running fix pack 8.0.0.2 with new function capability enabled cannot participate in a multiple-broker global cache with brokers running 8.0.0.1. Symptom: \n \n After upgrading to fix pack 8.0.0.2, cache catalog servers fail to start. All cache components report BIP7190 warnings. \n \n Solution: \n \n In 8.0.0.2, by default, each WebSphere eXtreme Scale server participating in the global cache starts with a domain name that is derived by the broker.\n Previously in 8.0.0.1 the domain name for all servers in all embedded caches was an empty string. Servers in different domains cannot collaborate in the same grid.\n Therefore, for a cache that spans more than one broker, you must enable the new capability for these brokers at the same time. \n \n Enable the new capability by using the -f parameter on the mqsichangebroker command. \n \n Brokers running fix pack 8.0.0.2 without new functionality enabled can still collaborate in the same grid as brokers running 8.0.0.1.\n In this scenario, the servers running 8.0.0.2 will continue to use an empty string as the domain name, and will report a BIP7140 warning message to the system log with this information.\n \n \n\n\n\n\n\nTOP WebSphere Message Broker Explorer \n * Connecting to a queue manager requires a SHARECNV value that is greater than 0 To connect the WebSphere Message Broker Explorer to a queue manager to receive publications, the SHARECNV property on that queue manager's SVRCONN channel must have a value that is greater than 0. This value is required if you want to use the Broker Statistics or Broker Statistics Graph views in WebSphere Message Broker Explorer.\n \n \n\n\n\n\n\nTOP WebSphere Message Broker Toolkit \n * Reset the Broker Application Development perspective after migrating Symptom: \n \n After migrating the WebSphere Message Broker Toolkit and its resources to V8.0, items might be displayed in the WebSphere Message Broker Toolkit that are removed in V8.0; for example, previous toolkit options in menus. \n \n Solution: \n \n To resolve this problem, complete the following step: \n \n * \n * Window > Reset Perspective\n * \n \n \n After the perspective is reset, menus and views are updated for Version 8.0.\n \n * Migrating or importing resources to a WebSphere Message Broker Toolkit V8.0.0.0 or V8.0.0.1 workspace, might result in erroneous errors. Symptom: \n \n After migrating or importing WebSphere Message Broker Toolkit and its resources to V8.0.0.0 or V8.0.0.1, erroneous errors might be displayed in the Toolkit. \n \n Solution: \n \n With your V8.0.0.0 or V8.0.0.1 workspace open in the WebSphere Message Broker Toolkit, select Project > Clean... > Clean all projects. The erroneous error messages are removed.\n \n \n \n * Importing resources into a new workspace might require project clean Symptom: \n \n When you import resources into a new workspace, error messages might display after autobuild is complete. \n \n Solution: \n \n In the Broker Development view, select your projects and right-click Project > Clean to rebuild the projects. After the projects are cleaned, the error messages relating to the import are removed.\n \n \n \n * Specifying a new workspace with mqsicreatebar might require project clean Symptom: \n \n When you run the mqsicreatebar command and specify a new workspace, error messages might display. \n \n Solution: \n \n Use the -cleanBuild option when running the mqsicreatebar command to clean the projects.\n \n \n \n * DFDL topics in the WebSphere Message Broker Toolkit are displayed in US English only Symptom: \n \n When using the information center that is included in the WebSphere Message Broker Toolkit V8.0.0.0 GA, Data Format Description Language (DFDL) topics are displayed in US English only.\n These topics have the identifier \"dfxxxxx_\", where \"xxxxx\" is a five-digit number. \n \n Solution: \n \n This problem is fixed in WebSphere Message Broker version 8.0.0.1.\n \n Users of WebSphere Message Broker version 8.0.0.0 GA can view these topics, in a language other than US English, using the online product documentation. The online product documentation for WebSphere Message Broker V8.0 contains the latest translated documentation, and is available at: \n \n http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html]\n \n \n \n * Java, PHP, and Message Set projects having the same name can only belong to one Application or Library Symptom: \n \n If a customer has more than one application or library in their workspace which requires a Java, PHP, or Message Set projects having the same name, an error message similar to the following will appear:\n The project < Project Name > can not be a member of multiple applications or libraries.... \n \n Solution: \n \n Where an identical project is required in more than one application or library, a copy of the project should be made, and given a different name.\n \n \n \n * Documentation contains incorrect instructions for installing the WebSphere Message Broker Toolkit as a non-admin user Symptom: \n \n Non-admin user is not able to install Toolkit while following current installation documentation. \n \n Solution: \n \n This problem is fixed in WebSphere Message Broker version 8.0.0.1.\n \n Users of WebSphere Message Broker 8.0.0.0, who are installing Toolkit as a non-admin user, can refer to the online product documentation at [http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp]http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html], or \n \n \n * Step 5 of the WebSphere Message Broker Toolkit V8.0.0.0 installation documentation should be updated as follows: * \n * \n * On Windows run the following command: \\installToolkit.bat -nonAdmin On Linux run the following script: /installToolkit.sh -nonAdmin \n \n \n * Step 14 should be added to the WebSphere Message Broker Toolkit V8.0.0.0 installation documentation and read as follows: * \n * \n * On Windows run command: \\wmbt\\postconfig\\postInstall_admin.bat On Linux run script: /wmbt/postconfig/postInstall_admin.sh \n * \n \n \n * When using an application project and a subflow with a .msgflow extension it is possible to create a BAR file with a duplicate message flow if the sub-flows have been used incorrectly in the previous release. Symptom: \n \n This is caused when an External InputNode is added to the sub-flow; the resultant BAR file will contain two compiled message flows. One of the message flows will be the intended flow with the sub-flow embedded, the other message flow will be the extraneous sub-flow containing the ExternalInputNode without an appropriate ExternalOutput Node. \n \n When the BAR file is deployed both of the message flows will run. The sub-flow will incorrectly start a new thread and attempt to read data from the InputNode. \n \n Solution: \n \n Either : \n \n * \n * \n * \n \n \n \n * Launching the WebSphere Message Broker Toolkit from Installation Manager makes the toolkit use WebSphere MQ 7.0.1 Symptom: \n \n When an installation has completed, the user is provided the option to start the WebSphere Message Broker V8.0 Toolkit. When the toolkit opens, any broker which is running with a queue manager on WebSphere MQ version 7.1 or 7.5 will be reported as stopped, irrespective of whether the broker is running or not. A dialogue might be displayed warning the brokers can not be connected to. \n \n If a user tries to start one of the brokers which is stopped, an error message is displayed containing the following text: \n \n The queue manager '' is not running (MQ reason code 2059 while trying to connect) \n \n Check that: \n \n * \n * \n * \n \n If a user tries to start one of the brokers which is already started, a dialogue is displayed indicating that the broker can not be started as it is already running. Solution: \n \n Shut down the toolkit and re-open it using the toolkit installation and not by using Installation Manager.\n \n \n \n * A version of XULRunner which is not compatible with Eclipse 3.6 (upon which WebSphere Message Broker Toolkit is based) may cause the Linux toolkit to crash shortly after being launched. Symptom: \n \n Within a minute or so of launching the Linux toolkit, it crashes with the following error:\n JVM terminated - Exit code=160 \n \n Solution: \n \n Install a version of XULRunner which is compatible with Eclipse 3.6. \n \n Compatible versions of XULRunner are versions 1.8-3.6 and associated fix packs. \n \n Testing at IBM has been done using the following version, and this has been confirmed to resolve the issue:\n http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.19/runtimes/xulrunner-1.9.2.19.en-US.linux-i686.tar.bz2 [http://ftp.mozilla.org/pub/mozilla.org/xulrunner/releases/1.9.2.19/runtimes/xulrunner-1.9.2.19.en-US.linux-i686.tar.bz2] \n \n Expand the downloaded compressed file into a convenient directory ( e.g. /usr/lib/xulrunner_new) \n \n Add the following line to the eclipse.ini file under the mb install directory:\n -Dorg.eclipse.swt.browser.XULRunnerPath= ( e.g. -Dorg.eclipse.swt.browser.XULRunnerPath=/usr/lib/xulrunner_new)\n \n \n\n\n\n\n\nTOP Web Services \n * No known issues.\n\n\n\n\nTOP Web UI \n * Upload of WSDL on zOS in the Web UI is not supported On WebSphere Message Broker version 8.0.0.1 on zOS, you can not currently upload WSDL files using the Web UI for use in the Web Based Static Endpoint pattern.\n \n \n\n\n\n\n\nTOP Nodes * After applying fixpack containing APAR IT01950 error BIP2503 is received.\n\n * \n * Symptoms:\n * WebSphere Message Broker has been modified so that if ESQL containing a FOR statement which iterates over a SHARED ROW variable contains a PROPAGATE statement within the FOR block then any attempt to write to that shared variable will result in an exception BIP2503 \"Propagate with a SHARED variable lock held by FOR statement\" being thrown.\n \n The reason for this is that while iterating over a SHARED ROW variable a lock is held on the variable, this lock is also obtained when writing to the variable in downstream nodes and the exact timing of these operations could result in a deadlock occurring. It is not valid to modify the SHARED ROW variable being iterated over in downstream nodes as it may invalidate the loop therefore behavior has been changed to throw an exception instead of deadlocking.\n \n Solution: \n * This means that there may be some flows which were at risk of deadlocking which now throw an exception. The recommended action is to modify the flows so that they do not use the affected invalid pattern however if this is not possible the previous behavior can be restored by setting the environment variable MQSI_ALLOW_PROPAGATE_WITH_SHARED_LOCK_HELD=1 and restarting the Broker.\n\n\n\n\nTOP WebSphere Adapter nodes \n * Saving Enterprise Metadata Discovery (EMD) adapter connection information during iterative discovery Symptoms: \n \n During WebSphere Adapter for SAP Software Enterprise Metadata Discovery (EMD) iterative discovery, the Adapter Connection wizard Service Generation and Deployment Configuration panel is displayed and can be edited; however, any adapter system connection information that you enter is not saved in the adapter component. \n \n Solution: \n \n Use the WebSphere Adapters editor to change the adapter system connection information to ensure that subsequent EMD iterative discoveries preserve the adapter system connection information: \n \n * \n * \n * \n * Open With\n * \n * WebSphere Adapters editor\n * \n * \n * \n * \n * \n \n \n \n * Assured delivery option for JDEdwards is not supported Symptoms: \n \n The JDE inbound adapter fails to deploy if the assured delivery check box is selected in the adapter wizard. The following error is issued: \n \n An attempt to set the property 'AssuredOnceDelivery' on adapter component 'AssuredDeliveryMSApp.IBM WebSphere Adapter for JD Edwards EnterpriseOne' failed because the property is not supported. \n \n Solution: \n \n This functionality is not currently supported, and should not be used in message flow development.\n \n \n\n\n\n\n\nTOP Graphical Data Mapper \n * Using a graphical data map to map input data that is retrieved from a database uses the default database schema name specified for the configured JDBC connection identity Symptoms: \n \n Using a graphical data map to map input data that is retrieved from a database is dependent on the default schema name configuration of your database server. The broker does not currently provide a facility to override the database schema name to be used in the SQL statements issued against the database. Currently, the SQL statement issued by the map includes only the database and table name but not a schema name. As a result, your database server uses the default database schema name for the identity that the broker used to connect to it while running the map. The connection identity that the broker uses is configured in a broker JDBCProvider configurable service. The JDBCProvider configurable service used is selected by the data source name in the map. \n \n If the required database table is not available in this schema, the map execution fails with a broker error containing specific error codes for your database server. For example:\n BIP3947E: The map processing for QName '{maps}:RDB_Mapping' has failed, with the following details:\n '{Your specific database schema table access error message and codes}' \n \n Solution: \n \n This restriction is addressed in WebSphere Message Broker version 8.0.0.1, and later, through provision of the capability to optionally override the name of the database schema. For more information, see JDBCProviders configurable service [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an60170_.htm] property \"databaseSchemaNames\". \n \n Users of WebSphere Message Broker version 8.0 GA should ensure that the table being selected from the graphical data map is available in the schema that is set by your database server for the database connection identity that is configured in the JDBCProvider configurable service. This is particularly restrictive on z/OS.\n \n \n \n * Errors occur during runtime execution of newly created graphical data maps, that were converted from message map (.msgmap) files, or utilise certain extended capabilities such as submaps with multiple inputs, or xs: cast transforms Symptoms: \n \n The execution of a graphical data map created using WebSphere Message Broker Toolkit version 8.0.0.2 that is deployed to a WebSphere Message Broker Runtime version 8.0 or 8.0.0.1 fails. \n \n Example error messages: \n \n BIP2230E: Error detected whilst processing a message in node '' ComIbmMSLMappingNode: \n BIP3946E: The map script generation for QName '' has failed, with the following details: java.lang.RuntimeException: IXJXE0609E: [ERR 0548][ERR XPST0017] The function '' with parity '' is not in the in-scope function declarations. \n \n Solution: \n \n Update the WebSphere Message Broker runtime to version 8.0.0.2.\n \n \n \n * Errors are seen during runtime when using a complex Data Analysis generated GDM map. Symptoms: \n \n A JVM Out of Memory exception is seen at runtime when using a Data Analysis generated GDM Map \n \n When using complex XML structures more memory is required that the default JVM Heap size \n \n Solution: \n \n Use the mqsichangeproperties [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/an09143_.htm] command to increase the maximum heap size to greater than 256Mb. For example : mqsichangeproperties MB8BROKER -e default -o ComIbmJVMManager -n jvmMaxHeapSize -v 786432000\n \n \n\n\n\n\n\nTOP Commands \n * Calling mqsiprofile in a zsh shell exits the session (A63403) Symptoms: \n \n On UNIX systems that use Z shell (zsh) as the shell environment, a call to 'source {install path}/mqsiprofile' causes the shell to exit. Due to the default behavior of zsh, the mqsiprofile command checks an incorrect argument number to determine whether it is being sourced, or run directly. The mqsiprofile script then prints a warning message and calls exit, but zsh interprets this call as an instruction to exit the current shell. \n \n Solution: \n \n To work around this problem, complete the following step: \n \n * In the UNIX terminal, call 'unsetopt function_argzero', then call the mqsiprofile command again.\n \n \n \n * Documentation for mqsiapplybaroverride states support for -k and -y parameters Symptom: \n \n Information center topic an19545_ mqsiapplybaroverride describes parameters -k and -y for use with applications and libraries. Using these parameters with the command results in the following error:\n BIP1033E Invalid parameters \n \n Solution: \n \n These options are not supported with this command, and should not be used.\n \n \n \n * Error \"AMQ7027: Argument [QM Name] supplied to command [path]\\crtmqm.exe is invalid.\" is seen when running mqsicreatebroker to create a Domain aware HA Broker on the Windows platform Symptom: \n \n An AMQ7027 error message might be returned from mqsicreatebroker when creating an HA Broker on the Windows platform when using the new -B or -Q flags if the Queue Manager does not already exist. \n \n Solution: \n \n If a Queue Manager does not exist when creating an HA Broker on Windows using the new -B or -Q flags an attempt is made to create a Queue Manager. The mqsicreatebroker command run tries to pass the '-ar' flag to the create Queue Manager (crtmqm) command. \n \n However, this option is only available for V7.1.0.3 and V7.5.0.1 of MQ. MQ APAR IC85940 provided this function in the Fix Packs. \n \n There are two possible workarounds in this situation: \n \n * \n * \n * \n * \n \n \n\n\n\n\nTOP Databases \n * Dates inserted into a Microsoft SQLServer database using JDBC are 2 days out \n * \n Symptoms :\n After upgrading to WebSphere Message Broker 8.0.0.7 or above, or applying APAR IT03599 to an earlier Fix Pack installation, dates inserted into an SQLServer database using a JDBC connection either through a JavaCompute node or a mapping node are 2 days out.\n WebSphere Message Broker 8.0.0.7 and APAR IT03599 upgrade the level of Java used by the Broker to Java 1.7. Some versions of the Microsoft SQL JDBC driver do not support Java 1.7 and produce unexpected behaviour when used.\n \n Solution:\n Upgrade the version of the Microsoft SQL JDBC driver to a version which supports Java 1.7\n \n * User databases on z/OS Customers using user databases on z/OS require DB2 APAR PK99362.\n \n \n \n * Sybase globally coordinated ('XA') transactions Globally coordinated ('XA') transactions are not supported.\n \n \n \n * JDBC/XA globally coordinated ('XA') transactions JDBC/XA globally coordinated ('XA') transactions are supported on DB2 and Oracle (except Oracle RAC) on all broker platforms except HP-UX on Itanium and z/OS. \n \n ODBC XA and JDBC/XA can not be mixed on the same broker.\n \n \n \n * Informix globally coordinated ('XA') transactions Informix globally coordinated ('XA') transactions are not supported.\n \n \n \n * DB2 and Microsoft SQL Server support on Windows Server 2008 R2 and Windows 7 64-bit Only DB2 and Microsoft SQL Server are supported on Windows Server 2008 R2 and Windows 7 64-bit. Use the DB2 and Microsoft SQL Server system requirements pages to determine the correct versions of each product to use with your system. \n The DB2 system requirements web page is available at:\n http://www.ibm.com/software/data/db2/linux-unix-windows/sysreqs.html [http://www.ibm.com/software/data/db2/linux-unix-windows/sysreqs.html]\n \n \n \n * XA configuration using WebSphere MQ installation specific subdirectories of exits and exits64 directories is not supported When configuring a broker to use XA with a WebSphere MQ 7.1 or WebSphere MQ 7.5 queue manager as the transaction manager, users must include the appropriate switch file in the\n /exits and/or /exits64 directories. Users must not use the installation specific subdirectory of the exits and exits64 for the switch files.\n \n \n \n * The WebSphere Message Broker Information Center instructions for \"Connecting to a database from Linux and UNIX systems using the WebSphere Message Broker ODBC Database Extender\" are incorrect Symptoms: \n \n The Message Broker fails to connect correctly to a Database when attempting to use an ODBC Data Source on Linux and UNIX systems. \n \n Example error message \n \n BIP2393E: Database error: ODBC return code '-1' from data source ''ROUTING'' using ODBC driver manager ''/opt/ibm/IE02/2.0.0/lib/libodbcinterface.so''. \n \n BIP2322E: Database error: SQL State ''IM002''; Native Error Code '0'; Error Text ''[unixODBC][Driver Manager]Data source name not found, and no default driver specified''. \n \n BIP8040E: Unable to connect to the database. \n \n Solution: \n \n The following corrections to the identified sample help pages are needed to ensure the ODBC connection can be setup and run successfully. \n \n The following page: \n \n WebSphere Message Broker Version 8.0.0.1>Configuring brokers for test and production>Advanced configuration>Configuring for applications>Configuring databases>Enabling ODBC connections to the databases [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bk58060_.htm] \n \n \"Connecting to a database from Linux and UNIX systems using the WebSphere Message Broker ODBC Database Extender\" is incorrect. \n \n Step 8 starts with \"If you are using a DB2 ... on AIX\" indicating that if you are not using AIX, you can skip this step. You must complete step 8 for all Linux and UNIX platforms.\n \n \n\n\n\n\n\nTOP Samples \n * The WebSphere Message Broker Information Center instructions for the DatabaseInput Node sample are incorrect. Symptoms: \n \n When attempting to set up and run the WebSphere Message Broker Application sample the DatabaseInput Node does not run successfully, with either an error being displayed when loading or updating the database, or no message being retrieved from the broker flow when the database has been updated. \n \n Solution: \n \n The following corrections should be read in conjunction with the samples help pages. \n \n WebSphere Message Broker Version 8.0.0.1>Product overview>Samples>Application samples>DatabaseInput Node>Setting up the database>Setting up DB2 [http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.samples.dbinputnode.doc%2Fdoc%2Fcreate_db2.htm] \n \n Section: Setting up DB2 \n \n Step 3 requires an update to read: \n \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n \n \n WebSphere Message Broker Version 8.0.0.1>Product overview>Samples>Application samples>DatabaseInput Node>Running the DatabaseInput Node sample [http://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.samples.dbinputnode.doc/doc/create_db2.htm] Section: To run the DatabaseInput message flow: \n \n Steps 3, 4 and 7 require updating to read: \n \n * \n * \n * 4. Click Finish to add a row to the table. The result is displayed in the \"SQL Result\" view, which can be opened using the \"Show View\" Eclipse menu. \n * ... \n * 7. Verify that the message retrieved contains a customer structure. If no message is received, open the open the \"DatabaseInput Retrieve Failure.mbtest\" Flow Test to dequeue a possible failure explanation message.\n \n \n\n\n\n\nTOP Copyright and trademark information \nhttp://www.ibm.com/legal/copytrade.shtml [http://www.ibm.com/legal/copytrade.shtml] \n\nThis information was developed for products and services offered in the U.S.A. \n\nIBM may not offer the products, services, or features discussed in this information in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. \n\nIBM may have patents or pending patent applications covering subject matter described in this information. The furnishing of this information does not give you any license to these patents. You can send license inquiries, in writing, to: \n\n * IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. \n\nFor license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: * IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan \n\nThe following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. \n\nThis information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice. \n\nAny references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. \n\nIBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. \n\nLicensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: \n\n * IBM United Kingdom Laboratories, Mail Point 151, Hursley Park, Winchester, Hampshire, England SO21 2JN \n\nSuch information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Programming License Agreement, or any equivalent agreement between us. \n\nInformation concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and can not confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. \n\nThis information includes examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. \n\nCOPYRIGHT LICENSE: \n\nThis information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, can not guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. \n\nThe following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:\n\nDB2, developerWorks, IBM, Informix, Passport Advantage, WebSphere, z/OS.\n\nJava and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates in the United States, other countries, or both\n\nMicrosoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. \n\nUNIX is a registered trademark of The Open Group in the United States and other countries.\n\nLinux is a trademark of Linus Torvalds in the United States, other countries, or both.\n\nOther company, product or service names might be trademarks or service marks of others. \n\n\n\n\n\n\nTOP Useful websites WebSphere Message Broker product page\nhttp://www.ibm.com/software/integration/wbimessagebroker/ [http://www.ibm.com/software/integration/wbimessagebroker/] \n\nDB2 Fix Packs\nIf you have a current support contract, you can order DB2 fix packs on CD by calling DB2 support. Alternatively you can download DB2 fix packs from the web, however some fix pack files are large and therefore requesting CD versions can avoid lengthy downloads. \nDB2 support contact details, and DB2 fix pack downloads are available at:\nhttp://www.ibm.com/software/data/db2/udb/support.html [http://www.ibm.com/software/data/db2/udb/support.html] \n\nWebSphere MQ Fix Packs\nhttp://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ [http://www.ibm.com/support/entry/portal/Software/WebSphere/WebSphere_MQ] \n\nWebSphere Message Broker Fix Packs\nhttp://www.ibm.com/support/docview.wss?uid=swg27006041 [http://www.ibm.com/support/docview.wss?uid=swg27006041] \n\nWebSphere Message Broker Requirements\nhttp://www.ibm.com/software/integration/wbimessagebroker/requirements/ [http://www.ibm.com/software/integration/wbimessagebroker/requirements/] \n\nWebSphere Message Broker readme file\nhttp://www.ibm.com/support/docview.wss?uid=swg27006917 [http://www.ibm.com/support/docview.wss?uid=swg27006917] \n\nWebSphere Message Broker V8.0 Stand-alone information center\nFor Linux:\nftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_linux.tgz [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_linux.tgz]\nFor Windows:\nftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_win.zip [ftp://public.dhe.ibm.com/software/integration/wbibrokers/docs/V8.0/wmb_help_win.zip] \n\nWebSphere Message Broker V8.0 online product documentation \n\nhttp://www.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html [http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/mapfiles/help_home_msgbroker.html]\nIBM Centre for Java™ Technology Development Downloads\nhttp://www.ibm.com/developerworks/java/jdk/ [http://www.ibm.com/developerworks/java/jdk/] \n\nWeb Services Description Language (WSDL) Specification \nhttp://www.w3.org/TR/wsdl [http://www.w3.org/TR/wsdl] \n\nWebSphere Message Broker developerWorks Zone\nhttp://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.html [http://www.ibm.com/developerworks/websphere/zones/businessintegration/wmb.html] \n\n\n\n\n\n\n\nTOP Document change history * Product electronic availability: 9 December 2011 \n * Version 8.0.0.1: 15 August 2012 \n * Version 8.0.0.2: 27 March 2013 \n * Version 8.0.0.3: 23 Oct 2013 \n * Version 8.0.0.4: 31 March 2014 \n * Version 8.0.0.5: 17 February 2015 \n * Web update for this readme file: 15 August 2012 \n * Web update for this readme file: 5 October 2012\n - Added \"Instructions for installing the WebSphere Message Broker runtime and ODBC Database Extender components with a non-root user ID\" to Installation Section (English Readme only)\n\n\n(C) Copyright IBM Corporation 2013. All rights reserved. \n\n\nCOPYRIGHT DATE\n 2012 \n\nPRODUCT ALIAS/SYNONYM\n WMB MB WBIMB", "question": "MessageSet Project cannot be referenced in multiple Applications \n\nThe same MessageSet Project cannot be referenced in multiple Applications or Libraries in WMB V8.\n\nIs there any specific reason for having this restriction ?\n\nThanks.", "answer": "If a customer has more than one application or library in their workspace which requires a Java, PHP, or Message Set projects having the same name, an error message similar to the following will appear:\n The project < Project Name > can not be a member of multiple applications or libraries...."} +{"id": "TRAIN_Q250", "document": "IBM Cannot update a Notice Questionnaire Template or publish a Hold Notice - United States Oracle 11.2.0.4.0 Atlas Publish Questionnaire TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After attempting to update a Notice Questionnaire Template or Publish a Hold Notice using IBM Atlas, the changes are not reflected in the user interface after the action. \n\nSYMPTOM\nThis happens for any updates performed on all versions of Atlas running with Oracle 11.2.0.4.0\n\n\nCAUSE\nThis is caused by Oracle bug (17501296) in version 11.2.0.4 \n\nENVIRONMENT\nAll Platforms\n\nDIAGNOSING THE PROBLEM\nAfter updating a notice questionnaire template or publishing a Hold Notice, no visible change is noticed in the user interface. If the user tries to update using sqlplus, the following exception is thrown when the transaction is committed\nERROR at line 1:\nORA-00604: error occurred at recursive SQL level 1\nORA-06550: line 1, column 7:\nPLS-00306: wrong number or types of arguments in call to 'SYNCRN'\nORA-06550: line 1, column 7: PL/SQL: Statement ignored\n\nRESOLVING THE PROBLEM\nPlease contact Oracle support and apply the Patch:17501296", "question": "Why are the changes not reflected in the user interface when you update a Notice Questionnaire Template or Publish a Hold Notice using IBM Atlas? Why are the changes not reflected in the user interface when you.update a Notice Questionnaire Template or Publish a Hold Notice using IBM Atlas? ", "answer": "Please contact Oracle support and apply the Patch:17501296"} +{"id": "TRAIN_Q252", "document": "IBM An unexpected ruleset version is executed - United States 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", "question": "Latest deployed ruleset not executing in clustered environment \n\nWe 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. I can see the updated rules when I review the ruleset archive. It appears the parsed ruleset cache is not being updated. However, I turned off the asynchronous mode as recommended here but this has not resolved the issue. The lasted ruleset is being picked up if a restart the server or update a ruleset property.\n\nAnother interesting aspect is that when I invoke the decision service using a url the calls the application server directly from SOAPUI, the correct rule is executing. But if then go into the client application after this, the ruleapp executed from the service layer the is going through the http service is still returning the older version of the rules.\n", "answer": "Possible 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"} +{"id": "TRAIN_Q254", "document": "IBM Deletion of virtual portal fails with transaction timeout - United States virtual 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]", "question": "Why is my delete virtual portal timing out after 120 seconds? When deleting a virtual portal via the Portal Admin User Interface (UI), it fails to complete. Examination of the SystemOut.log shows the following message:\n\nWTRN0006W: Transaction 0000014BB8A229770000000161570720292692D3DEAA2109E6D66CBE4D063A1626DCF4E80000014BB8A229770000000161570720292692D3DEAA2109E6D66CBE4D063A1626DCF4E800000001 has timed out after 120 seconds.\n\n00000006 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 2,5,main]. The stack trace of this thread when the timeout occurred was: java.net.SocketInputStream.socketRead0(Native Method) java.net.SocketInputStream.read(SocketInputStream.java:140)\n....", "answer": "1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \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)"} +{"id": "TRAIN_Q255", "document": "IBM How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? - United States TECHNOTE (FAQ)\n\nQUESTION\n We are able to install Data Studio (DS) 4.1.2 successfully but unable to uninstall the \nexisting Data Studio 3.1.1. When uninstall Data Studio 3.1.1 from Control Panel, it \nraises an error message pop-up window and can not uninstall it. Here is the message:\n\n+-------------------------------------------------------------------------\n| Java Virtual Machine Launcher\n+-------------------------------------------------------------------------\n| X Could not find the main class: com.zerog.lax.LAX. Program will exit.\n+-------------------------------------------------------------------------\n\nHow can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error?\n\n\nCAUSE\nIt is an known behavior/limitation. \n\nANSWER\nIt may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine. \n\nHere is an workaround. Please try to uninstall all products including Install Manager \n(IM) then reinstall IM and Data Studio 4.1.2. Below are detailed steps:\n\n1. Use IM to uninstall as many packages as possible.\n\n2. Identify the packages that are still installed, and manually clean \nthem up.\n\nExample on Windows:\n- C:\\Program Files\\IBM\\{IBMIMShared | SDPShared}\n\n3. Delete IBM Installation Manager.\n\nExample on Windows:\n- Delete the IM install directory:\nC:\\Program Files\\IBM\\Installation Manager\\\n- Delete the AppData directory (IM Agent Data):\nWindows 7: C:\\ProgramData\\IBM\\Installation Manager\n- Delete the Windows registry (regedit) entry : \nHKEY_LOCAL_MACHINE\\SOFTWARE\\IBM\\Installation Manager\n- re-install IM\n\n4. Reinstall DS 4.1.2 and other products.\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following above.\nPlease contact your Sales Rep to submit a potential design change towards a future release.\nOr please open a ticket, Request For Enhancement at https://www.ibm.com/developerworks/rfe/ [https://www.ibm.com/developerworks/rfe/]", "question": "Unable to unistall Data Studio 3.1.1 on Windows We use Data Studio 3.1.1.0 with DB2 WSE V9.7 FP11 on Windows 2008. While trying to new version of Data Studio 4.1.2, we are able to install it successfully. But unable to uninstall the existing 3.1.1.0, getting the jvm error \"Could not find the main class\". Is it a bug or something?\n", "answer": "It may be happened where two versions Data Studio 3.1.1 and 4.1.2 installed machine."} +{"id": "TRAIN_Q256", "document": "IBM ITCAM Extended Agent for Oracle Database: 6.3.1-TIV-ITM_EXT-FP0002 - United States Oracle Extended Agent Fixpack 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\n(C) Copyright International Business Machines Corporation 2012, 2013.\n\n\n All rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager Extended Agent for Oracle Database,\nVersion 6.3.1\n\nComponent ID: 5724V09OR\n\nFix: Fix Pack 0002, 6.3.1-TIV-ITM_EXT-FP0002\n\nDate: 30 August, 2013\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 Notices\n\n1.0 General description\n=======================\nThis fix resolves the APARs and defects and provides the enhancements listed\nin the \"Problems Fixed\" section below. This fix also includes the superseded\nfixes listed in section 2.4. This fix pack contains only updates for the\nExtended Agent for Oracle Database.\n\nDownload the installer images from the Passport Advantage web page:\nhttp://www-306.ibm.com/software/howtobuy/passportadvantage/index.html [http://www-306.ibm.com/software/howtobuy/passportadvantage/index.html]\n\nPhysical Part Number: ITCAM Extended Agent for Oracle Database CBAQ2ML\nElectronic Part Number: ITCAM Extended Agent for Oracle Database CIL7KML\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\n2.0 Problems fixed\n==================\nThe following problems are addressed by this fix.\n\n2.1 APARS:\n----------\n\nAPAR : IV24938\nAbstract : WRONG PCT_FREE CALCULATION IN RDB_RECOVERY_FILE_DEST\nAdditional Information: The Oracle Database Extended agent displays a wrong\nvalue for Free Space(%) in the following workspace. The value\nthat is displayed is less then the real value. \n\nArchive Node -> Flash Recovery workspace -> \nFlash Recovery Space Usage view\n\nAPAR : IV26915\nAbstract : ORA-12504: TNS:LISTENER WAS NOT GIVEN\nAdditional Information: The Oracle Database Extended agent logs are\nwritten at a rapid pace and growing large very quickly.\nThe following error message repeats:\n\n\"ORA-12504: TNS:listener was not given\".\n\nAPAR : IV30446\nAbstract : ALERT LOG MESSAGE TEXT IS GARBLED\nAdditional Information: The Japanese part of the Oracle alert\nlog message is garbled in the Tivoli Enterprise Portal.\nThis garbled information might also occur in other multi-byte \ncharacter set (MBCS) locales, such as East Asian locales \nsuch as Simplified Chinese or Korean.\n\nAPAR : IV31219\nAbstract : RDB_SESSION_DETAILS WAREHOUSING ERROR 64\nAdditional Information: The historical data from the \nattribute group RDB_Session_Details table cannot be\nexported into the warehouse, because the value after UTF-8\nconversion has a length greater than the column ACTION defined\nwidth (32). Therefore, the row is not exported into\nwarehouse and the local historical data file size \nincreases continuously. This issue might also occur in other\nEast Asian locales such as Simplified Chinese or Korean.\n\nAPAR : IV36395\nAbstract : KRZCLIENT FILE HANDLE LEAK ON WINDOWS\nAdditional Information: \"Handle Count\" on Windows operating systems \nwhere the Oracle Extended Database agent is running is constantly \ngrowing. When the agent is restarted, the krzclient.exe process \nis using hundreds of file handles. The hundreds of file handles \nincreases to thousands of file handles in a few hours.\n\nAPAR : IV38555\nAbstract : KRZCLIENT CRASHES AT TOPSQL\nAdditional Information: The Oracle Extended Database agent krzclient\nprocess crashes and generates a core file when the process queries \nRDB Top SQL attribute groups.\n\n2.2 Defects\n-----------\n\n2.3 Enhancements: \n-----------------\n\nEnhancement: INTERNAL\nAbstract: User interface configuration improvements.\n\n- Simplifies the database connection configuration \nwith three connection types:\n- Basic: Oracle database server host name (or IP address),\nListener port, and Oracle database service\nname (or Oracle SID) must be specified.\n- TNS: only the TNS Alias must be specified or selected\nfrom the drop-down list that is discovered\nfrom the ORACLE_HOME/network/admin/tnsnames.ora file.\n- Advanced: only the Oracle connection string must be \nspecified to be compatible with an old\nversion of agent configuration.\n\n- Supports the following connection string format: \n\"//hostname:port/ORACLE_SID\".\n\n- At least one database connection must be added during\nthe GUI configuration.\n\nEnhancement: INTERNAL\nAbstract: New environment variables that you can use to \ncustomize the agent, such as KRZ_LISTENER_INCLUDE, \nKRZ_LISTENER_EXCLUDE, KRZ_TNS_INCLUDE, KRZ_TNS_EXCLUDE,\nKRZ_REDIRECT_TNS, KRZ_EVENT_LEVEL, and KRZ_SQL_PREFILTER.\n\n- Provides the option to control whether the agent monitors\nthe specific Listener name and Oracle net service end points.\nBoth including and excluding filters are provided \n(KRZ_LISTENER_INCLUDE,KRZ_LISTENER_EXCLUDE, \nKRZ_TNS_INCLUDE, KRZ_TNS_EXCLUDE).\n\n- Provides the option (KRZ_REDIRECT_TNS) to control whether\nto redirect the value of the predefined TNS_ADMIN environment\nvariable to the agent log directory to disable the Oracle \nsqlnet.log.\n\n- Provides the option (KRZ_EVENT_LEVEL) to control which \nlevel of agent event is sent. The level with a scope from high\nto low is MISC, INFO, WARN, or ERROR.\n\n- Provides the option (KRZ_SQL_PREFILTER) to control whether the\nagent combines the filter information in the SQL query that is\nsent to the Oracle database for the data processing.\n\n\nEnhancement: INTERNAL\nAbstract: Performance improvement for Top SQL monitoring.\n\nEnhancement: INTERNAL\nAbstract: Disk Space usage monitoring for Archive Destination\nwhen Archive destination is defined in the Oracle database as\nUSE_DB_RECOVERY_FILE_DEST instead of a real physical directory.\n\nEnhancement: \nAbstract: More SQL statement samples in the krzcussql.properties\ncustomized SQL template file for Oracle Jobs, Oracle Users, \nand Oracle Queues monitoring.\n\nA total of six sample SQL statements are in the default \ncustomized SQL template file. To ensure the sample customized\nSQL can be run successfully, the SELECT authority from \ncorresponding Oracle performance views must be granted to the\nOracle user of the agent in advance.\n\nSQL_ID: mytablespace\nSQL_TEXT: select * from dba_tables; \nOracle Views to be granted SELECT permission: dba_tables\n\nSQL_ID: mytest\nSQL_TEXT: SELECT SID, \nSQL_CHILD_NUMBER FROM v$session\nOracle Views to be granted SELECT permission: v$session\n\nSQL_ID: dba_objects\nSQL_TEXT: SELECT * FROM dba_objects where rownum<200; \nOracle Views to be granted SELECT permission: dba_objects\n\nSQL_ID: krz_jobs\nSQL_TEXT: SELECT JOB JOBID,\nLOG_USER LOGUSER,\nPRIV_USER PRIVUSER,\nSCHEMA_USER SCHEMAU,\nTO_CHAR(LAST_DATE, 'YYYYMMDDHH24MISS') LASTSUCCD,\nLAST_SEC LASTSUCCS,\nNEXT_SEC NEXTSEC,\nBROKEN JOBBROKEN,\nINTERVAL INTERVALFN,\nNVL(FAILURES,0) JOBFAILS,\n(SYSDATE - NEXT_DATE) * 1440 NEXTSTART FROM SYS.DBA_JOBS;\nOracle Views to be granted SELECT permission: SYS.DBA_JOBS\n\nSQL_ID: krz_users\nSQL_TEXT: SELECT USERNAME,\nUSER_ID USERID,\nACCOUNT_STATUS STATUS,\nLOCK_DATE LOCKDATE,\nEXPIRY_DATE EXPIRYDATE,\nDEFAULT_TABLESPACE DEFAULTTS,\nTEMPORARY_TABLESPACE TEMPTS,\nCREATED,\nPROFILE FROM SYS.DBA_USERS;\nOracle Views to be granted SELECT permission: SYS.DBA_USERS\n\nSQL_ID: krz_queues\nSQL_TEXT: SELECT NAME,\nQUEUE_TABLE QUEUETABLE,\nQID QUEUEID,\nQUEUE_TYPE TYPE,\nMAX_RETRIES MAXRETRY,\nRETRY_DELAY DELAY,\nENQUEUE_ENABLED ENQUEUE,\nDEQUEUE_ENABLED DEQUEUE FROM SYS.DBA_QUEUES;\nOracle Views to be granted SELECT permission: SYS.DBA_QUEUES\n\n2.4 Superseded fixes:\n---------------------\n6.3.1-TIV-ITM_KRZ-IF0001.\n6.3.1-TIV-ITM_KRZ-IF0002.\n6.3.1-TIV-ITM_EXT-FP0001.\n\n2.5 APARS and defects included from superseded fixes\n---------------------------------------------------- \n6.3.1-TIV-ITM_EXT-FP0001\n----------------------------------------------------\n\nAPAR : IV22637\nAbstract : AGENT CORE DUMP IF TNSPING IS NOT ACCESSABLE\nAdditional Information: A core dump occurs for the Oracle Database \nExtended agent if the agent is configured with KRZ_ORACLE_HOME but, \n$ORACLE_HOME/bin/tnsping file did not grant read+execute permission\nto the agent OS user.\n\nAPAR : IV14403\nAbstract : TABLESPACE PERCENT_FREE_TO_MAX CALCULATE WRONG\nAdditional Information: The Oracle Database Extended agent might calculate \nthe value of the Percent_Free_To_Max attribute incorrectly, because this value\nshould be greater than the value of the Percent_Free_To_Allocated attribute\nin case the Oracle tablespace is set with Autoextend ON and \nthe maximum file size of the data file is greater than the allocated size \nfor the current datafile.\n\n6.3.1-TIV-ITM_KRZ-IF0002\n----------------------------------------------------\n\nAPAR: IV08618\nAbstract : AGENT OCCUPY ORACLE SESSION MORE AND MORE\nAdditional Information: The Oracle Database Extended agent occupies the\nOracle sessions increasingly if the Oracle Database Extended agent user\ndoes not have all authorities in the krzgrant.sql file.\nThis increase is caused by the agent not disconnecting from the Oracle\ndatabase, with an error message of \"ORA-00942 Table or View does not\nexist,\" and the agent trying to reconnect to the Oracle database with a new\nsession in each interval.\n\nDefect: 167731\nAbstract: agent configure still load based version xml file.\nAdditional Information: A new rz_dd_063100002.xml file is\ninstalled in the itmhome\\config directory by this patch, \nwhere the base version of the rz_dd_063100000.xml file is installed.\n\nThe agent loads the configuration definition from the newly installed\nrz_dd_063100002.xml file instead of the base version file.\n\nDefect: 168694\nAbstract: cannot ignore Oracle Listener/Net Service definition.\nAdditional Information: A new KRZ_LOAD_ORACLE_NET environment variable \nis added so you can decide whether the Listener and Net Service End Points\nfrom the files below are required for monitoring.\n\nOn UNIX and Linux systems:\n$ORACLE_HOME/network/admin/listener.ora\n$ORACLE_HOME/network/admin/tnsnames.ora\n$TNS_ADMIN/network/admin/listener.ora\n$TNS_ADMIN/network/admin/tnsnames.ora\n\nOn Windows systems:\n%ORACLE_HOME%\\network\\admin\\listener.ora\n%ORACLE_HOME%\\network\\admin\\tnsnames.ora\n%TNS_ADMIN%\\network\\admin\\listener.ora\n%TNS_ADMIN%\\network\\admin\\tnsnames.ora \n\nIf this new variable is set to 'false', the agent\ndoes not load Listener or Net Service definitions from the files above,\neven if the agent is configured with ORACLE HOME directory.\n\nThe agent still loads Listener or Net Service definition if the agent\nis configured with a TNS PATH directory, which contains the\nlistener.ora or tnsnames.ora files.\n\nDefect: 168966\nAbstract: ASM disk/diskgroup display redundancy data.\nAdditional Information: In an Oracle RAC environment, if there is more\nthan one active ASM database instance, the agent queries back multiple\nrows for each disk or disk group in all active instances.\nIf there is a situation in monitoring the attributes such as \nKRZ_RDB_ASM_DISKGROUP.Free_Percent, there are\nduplicated alerts by this type of situation.\n\nThe agent queries back only one record for each disk or disk group, and \navoids the duplicated alert for the situation.\n\nThe following attribute groups are impacted by this fix:\n\nKRZ_RDB_ASM_DISKGROUP\nKRZ_RDB_ASM_DISK\nKRZ_ASM_DISK\nKRZ_ASM_DISKGROUP\n\nDefect: 168967\nAbstract: FreeToMax return negative value. \nAdditional Information: The agent gets a negative value or over 100% on the\nfollowing attributes because the Maximum file size of an Oracle\ndata file is less than the real data file size:\n\nKRZ_RDB_TABLESPACENORMAL_USAGE.Percentage_Free_To_Maximum\nKRZ_RDB_TABLESPACENORMAL_USAGE.Percentage_Allocated\nKRZ_RDB_TABLESPACETEMP_USAGE.Percentage_Allocated\n\nDefect: 172392\nAbstract: CANNOT MERGE CUSTOM SQL FOR BASETABLE \nAdditional Information: Use the KRZ_CUSTOM_SQLXML environment variable \nto specify a customized\nkrzsql_custom.xml file where the new SQLInfo is defined and the agent\nuses SQLInfo from the customized sql xml file instead of the \ndefault krzsql.xml file. There is a new BaseTable tag in\nthe SQLInfo from version 6.3.1 and the new definition of\nBaseTable cannot overwrite the default definition in the krzsql.xml file.\n\n\n\n\n\nIf you do not grant all tables and views to the Oracle Database Extended agent \nuser in the krzgrant.sql file, error messages are displayed about ORA-00942\nbecause the agent checks the Oracle authority on the QueryName element \nwhile the agent runs continuously.\n\nThe error message about ORA-00942 can be avoided by using a customized\nsql xml file and copying the SQLInfo definition from the default krzsql.xml \nfile and replacing the QueryName and GrantName with 'dual'.\n\n\n\n\n\nDefect: 172695\nAbstract: KRZCLIENT LOG FILE LOOP AND OVERWRITE FIRST ONE \nAdditional Information: The RAS1 log file for the \nkrzstart or krzclient processes loops between 01, 02, and 03. The\nfirst RAS1 log file is overwritten after the 3rd one \nis full. This action disenables you to see information, such as \nstart time during agent startup.\n\nAfter the application of the fix, in the following file examples\nthe RAS1 log message loops between the \n\"tivp56_rz_orcl_krzclient_4eef1fe8-02.log\" file and the \n\"tivp56_rz_orcl_krzclient_4eef1fe8-03.log\" file. The\n\"tivp56_rz_orcl_krzclient_4eef1fe8-01.log\" file\nis not overwritten.\n\n#cd /opt/IBM/ITM/logs && ls *krzclient*.log\ntivp56_rz_orcl_krzclient_4eef1fe8-01.log\ntivp56_rz_orcl_krzclient_4eef1fe8-03.log\ntivp56_rz_orcl_krzclient_4eef1fe8-02.log\n\n\n6.3.1-TIV-ITM_KRZ-IF0001\n----------------------------------------------------\nAPAR : IZ77624\nAbstract : AGENT GETS ERROR ORA-01722 INVALID NUMBER ORACLE EXTENDED AGENT\n6.3.0 ON DISTRIBUTED PLATFORM\nAdditional Information: The Oracle Database Extended agent returns no data\nto the Tivoli Enterprise Portal because of ORA-01722.\n\nAPAR : IZ83799\nAbstract : UNDO TABLESPACE %USED IS WRONG\nAdditional Information: The RDB_TablespaceNormal_Usage attribute group\nPCIUSED (% Used) attribute is incorrect for UNDO tablespace.\n\nAPAR : IZ84903\nAbstract : ITM RZ AGENT DOES NOT SUPPORT ORACLE 9I\nAdditional Information: The corrected prerequisite was republished\nin the information center, see the \"Supported applications\" section at \nhttp://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.4/oracledatabaseextendedagent.html [http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcama.doc_6.2.4/oracledatabaseextendedagent.html]\nNote: For Oracle Database Servers: Requires Version 10.1.0.1 or later.\n\nAPAR : IZ87013\nAbstract : DBCONNECTION IN SUBNODE NOT TRUNCATED\nAdditional Information: Subnode ID as part of the subnode name must not be\nlonger then 25 characters, because of IBM Tivoli Monitoring limitations.\nThe entire subnode ID is truncated instead of the DBConnection part\nbeing truncated.\nNote: Subnode ID format: DBConnection-AgentInstance-Hostname.\n\nThe following troubleshooting Technote was published:\nhttp://www-01.ibm.com/support/docview.wss?uid=swg21455513 [http://www-01.ibm.com/support/docview.wss?uid=swg21455513]\n\nAPAR : IZ92572\nAbstract : SITUATION DOES NOT FIRE WITH SCAN FILTER\nAdditional Information: The Oracle Database Extended agent gets an incorrect\nfilter operator of 'EQ' when a situation includes the SCAN filter with the 'NE'\noperator.\nThe wrong operator causes the agent not to get the required data from the\nOracle database, and situations cannot be fired even if there are matched\ndata rows for this situation.\n\nAPAR : IZ95428\nAbstract : KRZGRANT.SQL RETURNS ORA-01722 ERROR IN AN ORACLE ENVIRONMENT\nUSING A NON-STANDARD NLS_NUMERIC_CHARACHTERS STRING\nAdditional Information: Using a non-standard NLS_NUMERIC_CHARACTERS string\nin the Oracle environment causes the problem.\n\nAPAR : IZ95117\nAbstract : CANNOT MONITOR ORACLE TM LOCK\nAdditional Information: The agent can detect only the Transaction Lock\n(type=TX) and cannot detect the DML or Table Lock(type=TM) in the Oracle\ndatabase.\n\nAPAR : IZ95898\nAbstract : KRZCLIENT CORE DUMP AT ALERT LOG READING\nAdditional Information: krzclient causes a core dump if the alert log is archived\nand newly generated alert log is the same size as the previous one.\n\nDefect: 136835\nAbstract: RDB Alert Log Details attribute group Message Timestamp attribute\nshows an incorrect value for timestamp with timezone.\n\n2.6 Enhancements included from superseded fixes\n----------------------------------------------------\n6.3.1-TIV-ITM_EXT-FP0001\n----------------------------------------------------\n\nSelf-describing agent (SDA) application support installation is supported. \nTo take advantage of self-describing agent capability, your \nTivoli Management Services server components must be \nVersion 6.2.3 Fixpack 1 or later.\n\n6.3.1-TIV-ITM_KRZ-IF0002\n----------------------------------------------------\nEnhancement: RFE\nHeadline: Improve Oracle Database Extended Agent not to contact ORCL instance\n(SYS4472)\nID: 12585\nDescription: \nStop the behavior where the Oracle Extended Database agent tries to connect\nagainst the Oracle default instance \"ORCL\" every time when checking\nLISTENERs/TNS.\nThe Oracle Extended Database agent is hard-coded to try to connect against\nan Oracle Instance \"ORCL\" that does not exist on most systems.\nBy default, the agent tries to connect every 5 minutes. \nTherefore, the Oracle database creates \"connect error 12514\" Log Entries\neach time, which fills up the log files.\n\nAdditional Information: The Oracle Extended Database agent uses the tnsping Oracle\nutility tool in the ORACLE_HOME/bin path to verify the \nListener status if the agent is configured with KRZ_ORACLE_HOME. Or, the user\ncan use the new KRZ_DEFAULT_ORACLE_SERVICE_NAME environment variable to define\na valid service name for the Listener monitoring instead of the hard coded 'ORCL'.\n\nEnhancement: RFE\nHeadline: RDB Disk Space: Oracle Archive directory is not monitored\ncorrectly \nID: 13528\nDescription:\nOn SAP systems, the Oracle archive destination is defined as \nlog_archive_dest=/, which is not a \nvalid or existing directory. \"Not Available\" is displayed for % Free\nattribute within RDB Disk Space attribute group.\n\nEnhancement: RFE\nHeadline: Oracle RAC One Node Monitoring\nID: 13734\nDescription:\nOracle RAC One Node is a single instance database that is always online, \nand it is a new option since Oracle 11.2.0.1. The Oracle \nExtended Database agent is not able to monitor the RAC One Node correctly. \nThe agent displays Instance Status as \"INACTIVE\", and Instance Name as \"*\" \nwithin the RDB Active Instance attribute group in a RAC One Node \ncluster environment.\n\n6.3.1-TIV-ITM_KRZ-IF0001\n----------------------------------------------------\n\nEnhancement: MR0329054818\nAbstract: Add Host name, Instance name, and Database name to all Oracle\nattribute groups for the ITCAM Extended Agent for Oracle Database version\n6.3.\nAdditional Information: With this enhancement, the situation provides more\ndetailed information. The Oracle Database Extended agent also provides\nthis information in a combined string. \nThe IT administrator can set up the situation easily.\n\nThe following attribute groups were changed:\nKRZ_DATABASE_INFORMATION\nKRZ_AGENT_LISTENER\nKRZ_RDB_ALERT_LOG_SUMMARY\nKRZ_RDB_ALERT_LOG_DETAILS\nKRZ_RDB_TABLESPACE_OVERVIEW\nKRZ_RDB_TSFILE_METRIC\nKRZ_RDB_SEGMENT_ALLOCATION\nKRZ_RDB_TABLESPACETEMP_USAGE\nKRZ_RDB_TABLESPACENORMAL_USAGE\nKRZ_RDB_SEGMENT_STATISTICS\nKRZ_RDB_DATAFILE_IO\nKRZ_RDB_DATAFILE_OVERVIEW\nKRZ_RDB_DATAFILE_COUNT\nKRZ_RDB_TEMPFILE_OVERVIEW\nKRZ_RDB_OBJECTS\nKRZ_RDB_TABLES\nKRZ_RDB_TABLE_SIZE\nKRZ_RDB_TABLE_NUM_ROWS\nKRZ_RDB_INDEXES\nKRZ_RDB_INDEX_AVG_DATA_BLOCK\nKRZ_RDB_INDEX_SIZE\nKRZ_RDB_CLUSTERS\nKRZ_RDB_CLUSTER_AVG_BLKS\nKRZ_RDB_CLUSTER_SIZE\nKRZ_DATABASE_OVERVIEW\nKRZ_RDB_RESOURCE_LIMITATION\nKRZ_RDB_SYS_STATISTICS\nKRZ_RDB_SYS_METRIC_HISTORY\nKRZ_RDB_DBA_HIST_SYSMETRIC_SUMMARY\nKRZ_RDB_SYS_METRIC_GROWTH_PERCENT\nKRZ_RDB_SYS_METRIC\nKRZ_RDB_DATABASE_STATISTICS_SUMMARY\nKRZ_RDB_DISK_SPACE\nKRZ_RDB_PARAMETER\nKRZ_RDB_OPTION\nKRZ_RDB_SGA_OVERVIEW\nKRZ_RDB_SGA_DETAIL\nKRZ_RDB_SGA_SIZE\nKRZ_RDB_PGA_OVERVIEW\nKRZ_RDB_PGA_DETAIL\nKRZ_RDB_PGA_TARGET_ADVICE\nKRZ_RDB_DICTIONARY_CACHE_DETAIL\nKRZ_RDB_DICTIONARY_CACHE_RATIO\nKRZ_RDB_BUFFER_CACHE_DETAIL\nKRZ_RDB_BUFFER_CACHE_RATIO\nKRZ_RDB_LIBRARY_CACHE_DETAIL\nKRZ_RDB_LIBRARY_CACHE_RATIO\nKRZ_RDB_INSTANCES_ACTIVE_RATIO\nKRZ_RDB_ACTIVE_INSTANCE\nKRZ_RDB_INSTANCE_INFO\nKRZ_RDB_INTER_CONNECTIONS\nKRZ_RDB_GCS_CR_LATENCY\nKRZ_RDB_GCS_CUR_BLOCK\nKRZ_RDB_GCS_BLOCK_LOST\nKRZ_RDB_GCS_MEM\nKRZ_RDB_CACHE_FUSION_WRITE\nKRZ_RDB_GES_MEM\nKRZ_RDB_GES_ENQ_STAT\nKRZ_RDB_GES_LATENCY\nKRZ_RDB_GES_LOCK\nKRZ_RDB_MSG_STAT\nKRZ_RDB_SESSION_WAIT\nKRZ_RDB_DBA_EXTENTS\nKRZ_RDB_ASM_CLIENT\nKRZ_RDB_ASM_DISK\nKRZ_RDB_ASM_DISKGROUP\nKRZ_RDB_ASM_DISKIOSTAT\nKRZ_RDB_ASM_DISKGROUPIOSTAT\nKRZ_RDB_ASM_TEMPLATE\nKRZ_RDB_ARCHIVE_OVERVIEW\nKRZ_RDB_ARCHIVE_DEST\nKRZ_RDB_FLASH_RECOVERY_AREA_USAGE\nKRZ_RDB_FLASHBACK_DATABASE_LOG\nKRZ_RDB_FLASHBACK_DATABASE_LOGFILE\nKRZ_RDB_RECOVERY_FILE_DEST\nKRZ_RDB_SESSION_DETAILS\nKRZ_RDB_SESSION_SUMMARY\nKRZ_RDB_LOCK_STATISTICS\nKRZ_RDB_LOCK_DETAIL\nKRZ_RDB_LOCK_CONFLICT\nKRZ_RDB_LATCH_STATISTICS\nKRZ_RDB_LATCH_CHILDREN\nKRZ_RDB_ROLLBACK_SEGMENT_SUMMARY\nKRZ_RDB_ROLLBACK_SEGMENT_DETAIL\nKRZ_RDB_UNDO_STATISTICS\nKRZ_RDB_PROCESS_SUMMARY\nKRZ_RDB_PROCESS_DETAIL\nKRZ_RDB_BGPROCESS_STATS\nKRZ_RDB_TOP_SQL\nKRZ_RDB_DBA_HIST_SQL_PLAN\nKRZ_RDB_CUSTOMIZED_SQL_SUMMARY\nKRZ_RDB_CUSTOMIZED_SQL_DETAIL\nKRZ_ASM_ALERT_LOG_SUMMARY\nKRZ_ASM_ALERT_LOG_DETAILS\nKRZ_ASM_INSTANCE\nKRZ_ASM_PROCESS\nKRZ_ASM_CLIENT\nKRZ_ASM_BGPROCESS_STATS\nKRZ_ASM_DISK\nKRZ_ASM_DISKGROUP\nKRZ_ASM_FILEINFO\nKRZ_ASM_PARAMETER\nKRZ_ASM_TEMPLATE\nKRZ_ASM_DISKIOSTAT\nKRZ_ASM_DISKGROUPIOSTAT\nKRZ_ASM_OPERATION\nKRZ_DG_DATABASE_OVERVIEW\nKRZ_DG_STATS\nKRZ_DG_STATUS\nKRZ_DG_BGPROCESS_STATS\nKRZ_DG_ALERT_LOG_SUMMARY\nKRZ_DG_ALERT_LOG_DETAILS\nKRZ_DG_LOG\nKRZ_DG_LOGFILE\nKRZ_DG_STANDBY_LOG\nKRZ_DG_ARCHIVE_DEST_AND_STATUS\nKRZ_DG_PARAMETER\nKRZ_DG_DATAFILE\nKRZ_DG_ARCHIVE_DEST\nKRZ_DG_ARCHIVE_DEST_STATUS\nKRZ_DG_ARCHIVED_LOG\nKRZ_DG_LATEST_ARCHIVED_LOG\nKRZ_DG_ARCHIVE_GAP\nKRZ_DG_LOG_HISTORY\nKRZ_DG_LOG_HISTORY_STAT\nKRZ_DG_MANAGED_STANDBY\nKRZ_DG_RECOVERY_PROGRESS\nKRZ_DG_MANAGED_STANDBY_STAT\nKRZ_DG_LOGSTDBY_PROCESS\nKRZ_DG_LOGSTDBY_PROGRESS\nKRZ_DG_LOGSTDBY_STATE\nKRZ_DG_LOGSTDBY_STATS\nKRZ_DG_LOGSTDBY_STATISTICS\nKRZ_DG_LOGSTDBY_PROCESS_STAT\nKRZ_DG_CUSTOMIZED_SQL_SUMMARY\nKRZ_DG_CUSTOMIZED_SQL_DETAIL\n\nEnhancement: INTERNAL\nAbstract: Providing the option to control whether monitoring the listener\nand Oracle net-service.\nAdditional Information: Listener monitoring and net-service monitoring\nare started by default. If you do not want this \nmonitoring, you can turn off the related monitoring functions.\nThe KRZ_LISTENER_PING_INTERVAL and KRZ_TNS_PING_INTERVAL environment\nvariables control the interval. If the value is less than 1, the agent\nexits the thread and stops checking.\n\nEnhancement: INTERNAL\nAbstract: Adding the delta value for system level statistics data.\nAdditional Information: With this enhancement, you can monitor the delta\nchanged value for a specific metric.\n\nEnhancement: INTERNAL\nAbstract: Enhancement at subnode name. You can control how the subnode\nname is presented in IBM Tivoli Monitoring.\nAdditional Information: This enhancement also protected an existing\nproblem: \"pure event cannot fire when subnode name length is 32 characters\",\nwhich is a known APAR at ITM622FP4.\n\nPresent the subnode name as \n\"RZ:--:RDB\".\n\nThe KRZ_SUBNODE_INCLUDING_AGENTNAME environment variable controls whether \nthe agent instance name is added to the subnode name.\nThe default value is YES.\n\nThe KRZ_SUBNODE_INCLUDING_HOSTNAME environment variable controls whether \nthe host name is added to the subnode name.\nThe default value is YES.\n\nThe KRZ_MAX_SUBNODE_NAME_LENGTH environment variable controls the\nmaximum subnode name length. \nThe default value is 24.\n\n\n3.0 Architecture and prerequisites\n==================================\n\nThis fix is supported on all operating systems listed in \nthe IBM Tivoli Composite Application Manager Extended Agent for Oracle \nDatabase V6.3.1 Fixpack 2 User's Guide.\n\nThe following website contains the latest certification information:\nSoftware Product Compatibility Reports (SPCR)\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 Upgrade prerequisites for this fix\n-----------------------------\nThere is no prerequisite level for this fix.\n\nBecause this fix is cumulative, it can be installed on any fix level \nfor the version, release, and modification level above the prerequisite. \n\n\n4.0 Image directory contents\n============================\nPhysical Part Number: ITCAM Apps Ag for Oracle CBAQ2ML\nElectronic Part Number: ITCAM Apps Ag for Oracle CIL7KML\n\n5.0 Installation instructions \n=============================\n\nWhen this fix pack image is downloaded from the IBM Software Support website, \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 upgrading.\n\n- For the purpose of this README, the symbol 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 Extended Monitoring Agent for Oracle \nrz.ini file on a UNIX system, back up this file before installing the fix. \nAfter this fix is installed, edit the latest rz.ini file and merge \nyour modifications into this rz.ini file.\n\n\n5.2 Local agent install and update (including silent installation)\n--------------------------------------------------------------\n1. Transfer the appropriate archive file to a \ntemporary directory on the system that contains the agent code to be \nupdated. For the purpose of this README, the symbol represents \nthe fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n2. Expand the archive file by using the tar command on UNIX systems or \nan unzip utility on Windows systems. This expansion creates a directory \nstructure that contains fixes for all supported platforms.\n\n3. Use the procedures in the \"IBM Tivoli Monitoring, Version 6.2.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\n\n5.3 Remote agent update and installation\n----------------------------------------\n1. Make sure that all potential targets of the remote deployment are\nrunning version 6.2.2 Fix Pack 2 or later of the OS monitoring \nagent.\n2. Transfer the appropriate archive file to \na temporary directory on the Tivoli Enterprise \nMonitoring Server system. For the purpose of this README, the \n symbol represents the fully qualified path to this directory.\nNote: On Windows systems, this path includes the drive letter. \n\n3. Expand the archive file by using the tar command on UNIX systems or an \nunzip utility on Windows systems. This expansion creates a directory structure\nthat contains fixes for all supported operating systems.\n\n4. To add the fix pack bundles to the remote deployment depot, use the\ntacmd addBundles command found in $CANDLEHOME/bin on UNIX systems\nor in %CANDLE_HOME%\\bin on Windows systems. For more information\nabout the tacmd addBundles command, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: if the fix was expanded to \n/:\n> $CANDLEHOME/bin/tacmd addBundles -i //WINDOWS/Deploy -t rz -f\n> $CANDLEHOME/bin/tacmd addBundles -i //WIA64/Deploy -t rz -f\n> $CANDLEHOME/bin/tacmd addBundles -i //unix -t rz -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 rz \nrepresents the Extended Monitoring Agent for Oracle Database\n-f performs the actions without asking for confirmation\n\nOn a Windows system: if the fix was expanded to \n/:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\\\WINDOWS\\Deploy -t rz -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\\\WIA64\\Deploy -t rz -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i \\\\unix -t rz -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 rz \nrepresents the Extended Monitoring Agent for Oracle Database\n-f performs the actions without asking for confirmation\n\n5. To login 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 about the\ntacmd login and updateAgent commands, see the \"IBM Tivoli\nMonitoring Command Reference.\"\n\nOn a UNIX system: \n> $CANDLEHOME/bin/tacmd login -s \n-u \n-p \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 rz\n-n \n-v 063102000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 RZ\n-n \n-v 063102000\nNote:\n- The component (-t) for the updateAgent command is specified as \ntwo characters (rz), not three characters (krz).\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\n- The following error might occur with the updateAgent command on \nLinux and UNIX endpoints; however, the agent is successfully \nupdated. This error does not occur on Windows endpoints.\n\nKUICUA011I: Updating the rz agents.\nKUICUA015E: The updateAgent command did not complete because an\nerror occurred. Refer to the following error\nreturned from the server:\n\nThe monitoring server encountered an error while updating the\nmanaged system type.\n\nThe kuiras1.log file might provide more information about \nthis error. If you require further assistance to resolve the \nerror, contact IBM Software Support.\n\nA timeout occurred while waiting for an agent task to complete on\n{node name}.\n\nThe agent task did not complete within the configured \ntime out period.\n\nVerify that the target system is online. Increase the \ntime out value and try the operation again.\n\n\n\n5.4 Agent support update\n------------------------\nFix 6.3.1-TIV-ITM_EXT-FP0001 included changes to the agent\nsupport files that must be installed. If you have already\ninstalled these updates, there are no additional installation\nsteps. Otherwise, use the following steps to update the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, or\nTivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file \nto the 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 \"IBM Tivoli Monitoring, Version 6.2.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\n6.0 Additional installation information\n========================================\n\n6.1 Verifying the update\n------------------------\n1. To verify that the agent was updated correctly, use the tacmd command to \nview the current version of the agent. You are required to log in \nto a Tivoli Enterprise Monitoring Server before you view the agent\nversion. \n\nFor example:\nOn a UNIX system, where $CANDLEHOME is the IBM Tivoli Monitoring\ninstallation directory, the default location is '/opt/IBM/ITM'. \n\n> $CANDLEHOME/bin/tacmd login -s \n-u \n-p \n> $CANDLEHOME/bin/tacmd listSystems -t rz\n\nOn a Windows system, 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 \n-u \n-p \n> %CANDLE_HOME%\\bin\\tacmd listSystems -t RZ \n\nWhen the agent update is successful, the agent version is \n06.31.02.00\n\nNote:\nThe component (-t) for the tacmd listSystems command is specified \nas two characters (RZ), not three characters (KRZ).\n\n2. To verify that the agent support files were updated correctly, use \nthe kincinfo command on Windows systems or the cinfo command on Linux\nor UNIX systems to dump the component versions on each of the \nfollowing systems: Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring\nServer, and Tivoli Enterprise Portal desktop. \n\nNote: \nThe kincinfo and cinfo command output examples in the sections\nthat follow show all components that can be updated. If you do\nnot have all of these components installed, components that \nare not installed are not displayed in the output of these commands. \n\n\nSample output for the cinfo command on a UNIX or Linux systems\n--------------------------------------------------------------\nTo validate that all components are installed, run the\nfollowing command:\n\n./cinfo\n\nThis command provides four options on the CINFO menu shown in\nthe example that follows. Choose the option that meets your requirements.\n\n*********** Thu Aug 15 15:02:01 HKT 2013 ******************\nUser : root Group: root\nHost name : myaixsys Installer Lvl:06.22.02.00\nCandleHome: /opt/IBM/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) Show installed CD release versions\nX) Exit CINFO\n1\n\n*********** Thu Aug 15 15:02:01 HKT 2013 ******************\nUser : root Group: root bin daemon sys adm disk wheel\nHost name : myaixsys Installer Lvl:06.22.02.00\nCandleHome: /opt/IBM/ITM\n***********************************************************\n...Product inventory\n\n\nUnix/Linux: IBM Tivoli Enterprise Server Portal Server / IBM Tivoli \nEnterprise Portal Desktop, cinfo output:\n\nrz ITCAM Extended Agent for Oracle Database\nli6263 Version: 06.31.02.00\n\nUnix/Linux: Extended Agent for Oracle Database\n\n\nrz ITCAM Extended Agent for Oracle Database\nli6263 Version: 06.31.02.00\n\nSample output of the kincinfo command on a Windows System\n----------------------------------------------------------\nTo validate that all components have been installed, run \nthe following command:\n\nFor example:\n> %CANDLE_HOME%\\InstallITM\\kincinfo -i\n\n>kincinfo -i\n\nkincinfo output:\n\nWindows: Tivoli Enterprise Server Portal Server / Tivoli \nEnterprise Portal Desktop\n\nRZ ITCAM Extended Agent for Oracle Database\nWINNT Version: 06.31.02.00 Build: 201308012231\n\nRZ ITCAM Extended Agent for Oracle Database\nWINNT Version: 06.31.02.00 Build: 201308012231\n\nRZ ITCAM Extended Agent for Oracle Database\nWINNT Version: 06.31.02.00 Build: 201308012231\n\nRZ ITCAM Extended Agent for Oracle Database\nWINNT Version: 06.31.02.00 Build: 201308012231\n\nWindows: Extended Agent for Oracle Database:\n\nRZ ITCAM Extended Agent for Oracle Database\nWINNT Version: 06.31.02.00 Build: 201308012231 \n\n\n7.0 Known problems and workarounds\n==================================\n- Problem: Oracle agent unable to logon to oracle database, due to\ninvalid password, after remote deploying or remote \nconfiguring, on a windows x64 system.\ndefect: 119668\nWorkaround: Upgrade the Windows OS agent to version 6.22 fp2.\n\n- Problem: Oracle agent running processes not stopped, after removing\nthe oracle agent instance from the tivoli enterprise \nmonitoring services management window, on a UNIX system.\ndefect: 120864\nWorkaround: Stop the Oracle Database Extended agent instance before removing it.\n\n- Problem: A connection of oracle agent not displayed on TEP, if the \nconnection name is too long.\ndefect: 121337\nWorkaround: Assign a short name to the Oracle Database Extended agent instance and \nconnection in the instance to avoid truncating the unique name(connection \nname + krz instance name + host name).\n\n- Problem: Unable to remote deploy oracle agent to a windows IA64 \nsystem, if no WINNT platform bundle exists in the TEMS \nrepository.\ndefect: 122095\nWorkaround: Add the 3 Windows operating system bundles (WINNT, WIX64, WIA64) to\nThe Tivoli Enterprise Monitoring Server repository before remotely deploying \non a Windows IA64 system.\n\n- Problem: Alert logs is not displaying customized message ID.\n- Workaround: If you must monitor custom message IDs in Alert logs,\nmessage IDs must be specified in the \ninstalldir/config/_rz__msgid.properties file\nand you must restart the agent to display it in the portal.\n\n- Problem: default value for \"Last Execution Error Code\" is displaying as 0\nin workspace \"Customized SQLs->RDB Customized SQL Summary status\".\n- Workaround: The customized SQLs are not executed during agent startup\nby default. These SQLs are executed only if there is a situation or \nyou click \"Link to SQL Result\" in the workspace \"Customized SQLs ->\nRDB Customized SQL Summary Definition\".\n\n- Problem: agent environment variable or error trace level do not take\neffective.\n- Workaround: If you must edit an environment variable such as setting a new\nerror trace level, the new variable must be modified in both the \ninstalldir/config/rz.ini file and the installdir/config/rz_.config\nfile, and you must restart agent.\n\n- Problem: agent report ORA-00942 error message in the log files like\nfollowing. Oracle Database Server is 10.1.0.2.\nERROR at line 1:\nORA-00942: table or view does not exist\nORA-06512: at line 128\n- Workaround: Run the krzgrant.sql script in 6.3.1-TIV-ITM_KRZ-FP0001 to resolve\nthis error.\n\n- Problem: tacmd listsystems command does not display proper version\nfor offline agent's subnode.\nFor subnode e.g. RZ:HOSTNAME-INSTANCE-CONNECTION:RDB, version is\ndisplaying as 06.31.01.XX, Status is 'N'.\n- Workaround: Check the version from the root node of the agent to get the correct\nversion, for example, for INSTANCE:HOSTNAME:RZ, the version is displayed as \n06.31.01.00. \n\n- Problem: After upgrading to Fix Pack 2 and configuring the Oracle\nDatabase Extended agent silently, the agent cannot\nconnect to the database, which is specified by the\nKRZ_CONN_STR parameter in the silent configuration\nresponse file.\n- Workaround: The KRZ_CONN_TYPE parameter specifies the connection\ntype. The Advanced type is required to configure a\ndatabase connection with the KRZ_CONN_STR\nconnection string. For example:\n\nKRZ_CONN_STR.connection=//host:port/service\nKRZ_CONN_TYPE.connection=Advanced\n\nTo solve the problem, update the silent configuration\nresponse file to specify the KRZ_CONN_TYPE parameter and\nreconfigure the agent instance silently. For example:\n\n# cat /tmp/silent_config.txt\n############ PRIMARY TEMS CONFIGURATION ############\nCMSCONNECT=YES\nHOSTNAME=tivp055.cn.ibm.com\nNETWORKPROTOCOL=ip.pipe\nIPPIPEPORTNUMBER=1918\n############ Database connection config ############\nINSTANCE=inst1\nKRZ_CONN_USERID=tivoli\nKRZ_CONN_PASSWORD=password\nKRZ_INSTANT_CLIENT_LIBPATH=/opt/IBM/oci\nKRZ_DYNAMIC_LISTENER=FALSE\n###\nKRZ_CONN_STR.asm=//tivx010:1521/+ASM\nKRZ_CONN_USERID.asm=sys\nKRZ_CONN_PASSWORD.asm=oracle\nKRZ_CONN_MODE.asm=SYSDBA\nKRZ_CONN_TYPE.asm=Advanced\n\n# /opt/IBM/ITM/bin/itmcmd config -A -o inst1\n-p /tmp/silent_config.txt rz\n\n- Problem: The Oracle Database Extended agent reports the error\nmessage ORA-03135: connection lost contact and the\nsubnode that represents the monitored database\nconnection is still offline in the Tivoli Enterprise Portal\nafter the monitored database recovers to active status..\n- Workaround: The Oracle Database might disconnect all active connections\nand reject new connections under certain circumstances.\nAn example is when resources such as CPU are exhausted\nin the Oracle Server.\nTo solve the problem, ensure that the Oracle Database\nand Oracle Listener are open to the new connection and\nrestart the agent instance.\n\n- Problem: After you upgrade to V6.3.1 Fix Pack 2, the subnode ID\nis truncated from 25 characters to 24 characters. The\noriginal subnode with 25 characters changes to gray, and\nthe new subnode with 24 characters is displayed.\n- Workaround: This behavior is expected. In 6.3.1-TIV-ITM_KRZ-IF0001\nor later versions, the agent changed the maximum\nsubnode ID from 25 characters to 24 characters to avoid\nthe following problem, which is a known APAR for IBM\nTivoli Monitoring V6.2.2 Fix Pack 4: \"pure event cannot\nfire when subnode name length is equal to or greater\nthan 32 characters.\"\nTo avoid truncation of the subnode from 25 characters to\n24 characters, use one of the following two options:\n\nOption 1: Set the following variable to a value of 25 in\nthe agent environment variable files:\nKRZ_MAX_SUBNODE_ID_LENGTH=25. After you upgrade,\nthe default value is 24.\nNote:\n- On UNIX or Linux operating systems, the\nenvironment variable files include\ninstalldir/config/rz.ini and installdir/config/\nrz_instance.config.\n- On Windows operating systems, the environment\nvariable files include installdir\\TMAITM6\\\nKRZENV_instance (32-bit) or installdir\\\nTMAITM6_X64\\KRZENV_instance (64-bit).\n\nOption 2: Reduce the length of the database\nconnection name, agent instance name, or host name;\nor, see Changing default naming conventions for\ndatabase connections in the Installation and\nConfiguration Guide for the Oracle Database Extended\nagent for information.\n\n8.0 Additional product information\n==================================\nNone.\n\n\n9.0 Notices\n===========\nThis information was developed for products and services offered \nin the United States. IBM may not offer the products, services, or\nfeatures discussed in this document in other countries. Consult \nyour local IBM representative for information on the products and \nservices currently available in your area. Any reference to an \nIBM product, program, or service is not intended to state or imply \nthat only that IBM product, program, or service may be used. Any \nfunctionally equivalent product,program, or service that does not \ninfringe any IBM intellectual property right may be used instead. \nHowever, it is the user's responsibility to evaluate and verify\nthe operation of any non-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 or \nany other country where such provisions are inconsistent with 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 to you.\n\nTrademarks and service marks\n------------------------------------\nIBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business\nMachines Corp., registered in many jurisdictions worldwide. Other product and service names might be\ntrademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at\n\"Copyright and trademark information\" at www.ibm.com/legal/copytrade.shtml.\n\nLinux is a registered trademark of Linus Torvalds in the United States,\nother countries, or both.\n\nMicrosoft, Windows, Windows NT, and the Windows logo are trademarks of \nMicrosoft Corporation 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\nOther company, product, or service names may be trademarks or service \nmarks of others.\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] \nWhat is DD? [http://www6.software.ibm.com/dldirector/doc/DDfaq_en.html] 6.3.1-TIV-ITM_EXT-FP0002.README 30 Aug 2013 English 999999 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=6.3.1-TIV-ITM_EXT-FP0002&source=SAR ] [ ] DD \n [/support/docview.wss?uid=swg24035571&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24035571&aid=2]Problems (APARS) fixed\nIV38555, IV36395, IV31219, IV30446, IV26915, IV24938, IV22637, IV14403, IV08618, IZ95898, IZ95428, IZ95117, IZ92572, IZ87013, IZ84903, IZ83799, IZ77624", "question": "Error running krzgrant.sql script provided with 6.3.1.2-TIV-ITM_KRZ-IF0003.tar When running the krzgrant.sql script provided in the package - 6.3.1.2-TIV-ITM_KRZ-IF0003.tar get the following errors:\n\nERROR at line 1:\nORA-00942: table or view does not exist ORA-06512: at line 50 \n\nHow to correct this?", "answer": "Run the krzgrant.sql script in 6.3.1-TIV-ITM_KRZ-FP0001 to resolve\nthis error."} +{"id": "TRAIN_Q258", "document": "IBM How to delete a document hierarchy node in IBM Datacap Taskmaster Capture - United States dco document hierarchy node delete remove hide blank page TECHNOTE (FAQ)\n\nQUESTION\n How do I delete a document hierarchy node, such as a blank page, so that it no longer processes rules or appears in a batchview listing? \n\nCAUSE\nIt is sometimes desired to remove pages or documents from a batch, as they are no longer needed or to simplify processing for a Verify operator.\n\nANSWER\nThe DeleteChildType from the Validations library can be used by running it from the parent of the object to be deleted and specifying the specific child. \n\nFor example, to remove blank pages from a batch: \n\n 1. Create a special page type attached at the batch level called something like DeleteMe. \n 2. Use an action like BlankPagesIDBySize to identify the blank page: * BlankPagesIDBySize (1000,DeleteMe)\n \n \n 3. Create a rule with the action DeleteChildType(DeleteMe) and attach it at the batch level to have it remove all pages with page type DeleteMe.\n\n\nIf building a custom action, the DeleteChild API method is invoked from the parent object. \n\n * \n *", "question": "Hide a page in dotedit step I am working on datacap 8.1 version. I have 2 pages in a batch. Page 1 with status as 1, Page 2 with status as 20. Both are of same page type. In verification step (dotedit) I want to hide the page which is with status 20. I have given status 20 in ignored page status in web administrator for verify. But still when I navigate through pages in dotedit batch view the respective panel is loading. I am able to submit the batch even if I have one page in a batch with 20 as status.\n\nIs there any way to hide the page (we have multiple same type of pages in a batch) from dotedit based on the page status?", "answer": "The DeleteChildType from the Validations library can be used by running it from the parent of the object to be deleted and specifying the specific child. \n\nFor example, to remove blank pages from a batch: \n\n 1. Create a special page type attached at the batch level called something like DeleteMe. \n 2. Use an action like BlankPagesIDBySize to identify the blank page: * BlankPagesIDBySize (1000,DeleteMe)\n \n \n 3. Create a rule with the action DeleteChildType(DeleteMe) and attach it at the batch level to have it remove all pages with page type DeleteMe.\n\n\nIf building a custom action, the DeleteChild API method is invoked from the parent object."} +{"id": "TRAIN_Q259", "document": "IBM Purging the connection pool of a WebSphere Application Server data source using the data source MBean - United States was app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n During the testing or troubleshooting of an enterprise application, it may become necessary to purge the connection pool of a WebSphere Application Server data source of existing connections. \n\nSYMPTOM\nChanges to the application or environment may invalidate cached connections in the Connection Manager pool. Although these connections will eventually be discarded through the normal processing of the connection requests, it may be desirable to purge them all at once and allow the pool to refill with new, valid connections.\n\n\nRESOLVING THE PROBLEM\nWebSphere Application Server has an operation on the data source MBean that can be used to purge the connection pool. WebSphere Application Server MBean may be called via the wsadmin console, see the IBM Information Center topic \"Scripting the application serving environment (wsadmin)\" for more details. The operation name is: purgePoolContents. \n\nThe purgePoolContents operation has two options: \n\n 1. Normal: * This is the default option. \n * Existing in-flight transactions will be allowed to continue work. \n * Shared connection requests will be honored. \n * Free connections are cleaned up and destroyed. \n * In use connections (for example: connections in transactions) are cleaned up and destroyed when returned to the connection pool. \n * A close() call issued on any connection obtained prior to the purgePoolContents will be done synchronously (for example: wait for the jdbc driver to return before proceeding). \n * Requests for new connections (not handles to existing old connections) will be honored.\n \n \n \n \n 2. Immediate: * No new transactions will be allowed to start on any connections obtained prior to the purgePoolContents call. Instead, a StaleConnectionException is thrown. \n * No new handles will be handed out on any connections obtained prior to the purgePoolContents call. Instead, a StaleConnectionException is thrown. \n * Existing in-flight transactions will be allowed to continue work. Any new activities on a purged Connection will cause a StaleConnectionException or an XAER_FAIL exception (in the case of XA) \n * A close() call issued on any connection obtained prior to the purgePoolContents call will be done asynchronously (for example: no waiting for the jdbc driver to return) This is useful if the driver returns. \n * Due to the fact that close() does not wait, the number of connections will be decremented immediately in WebSphere Application Server. This might cause the total number of connections in WebSphere Application Server to be temporarily out of sync with the database total number of connections. \n * Requests for new connections (for example: not handles to existing old connections) will be honored.\n \n \n\n\nExamples of operations that can be executed on the data source MBean using the wasdmin console: 1. List all data sources:\n Using Jacl:\n $AdminControl queryNames *:type=DataSource,*\n \n Using Jython:\n AdminControl.queryNames(\"*:type=DataSource,*\")\n \n \n 2. Initialize a variable to specify a data source (this example uses Default Datasource, but any data source name listed in the output of above command can be used):\n Using Jacl:\n set name \"Default Datasource\"\n set ds [$AdminControl queryNames *:type=DataSource,name=$name,*] \n \n Using Jython:\n name = \"Default Datasource\"\n ds = AdminControl.queryNames(\"*:type=DataSource,name=\"+name+\",*\") \n \n \n 3. View the pool contents by invoking the showPoolContents operation of the data source MBean:\n Using Jacl:\n $AdminControl invoke $ds showPoolContents\n \n Using Jython:\n print AdminControl.invoke(ds, \"showPoolContents\")\n \n \n 4. View contents of all pools by invoking the showAllPoolContents operation of the data source MBean:\n Using Jacl:\n $AdminControl invoke $ds showAllPoolContents\n \n \n Using Jython:\n print AdminControl.invoke(ds, \"showAllPoolContents\")\n \n \n 5. Immediately purge the pool by invoking the purgePoolContents operation of the data source MBean with the immediate option:\n Using Jacl:\n $AdminControl invoke $ds purgePoolContents immediate\n \n \n Using Jython:\n AdminControl.invoke(ds, \"purgePoolContents\", \"immediate\")\n \n \n\nIf the purge operation is successful, no response will be observed. If the purge operation is not successful, the response will indicate a possible reason for failure. One common reason for failure is attempting to purge the contents of a connection pool which is not yet available (the connection pool is not created until a naming look-up of the associated datasource or connection factory occurs), resulting in an illegal state exception. \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK Application Servers WebSphere Application Server for z/OS Java SDK z/OS 8.0, 7.0, 6.1", "question": "Why does our Websphere application server hang when we apply Microsoft patch on our database server? We use SQL Server database for one of our inhouse applications. As part of our regular maintenance we install Microsoft SQL patching once every month.Our DBA restarts the database after the patch install.All applications reconnect to the datbase automatically once the database is up but the application that is running on WAS fails to reconnect to the daabase and the appserver becomes unresponsive.Test connection to database is working fine though. And also webserver is reaching out max clients. So we are restarting appservers and webservers everytime Microsoft SQL patching is installed.", "answer": "WebSphere Application Server has an operation on the data source MBean that can be used to purge the connection pool. WebSphere Application Server MBean may be called via the wsadmin console, see the IBM Information Center topic \"Scripting the application serving environment (wsadmin)\" for more details. The operation name is: purgePoolContents."} +{"id": "TRAIN_Q260", "document": "IBM BMT-IMP-0002 Failed to execute metadata request insufficient\ncapabilities\" - United States DQM; Import relational metadata capability TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User is unable to perform one or more of the following tasks:\n1. Run Metadata Wizard\n2. Import new metadata\n3. Modify Query Mode to Dynamic Query Mode for an existing package in Framework Manager project.\n\n\nSYMPTOM\nUser receives one of the following error messages: \n\n1. BMT-IMP-0002 Failed to execute metadata request insufficient capabilities \n\n2 BMT-IMP-0002 Failed to execute metadata request. insufficentCapabilities DPR-ERR-2082 An error has occurred. Please contact your administrator. The complete error has been logged by CAF with SecureErrorID... \n\n3. BMT-IMP-0002 Execution of task for metadata failed. InsufficientCapabilities...\n\n\nCAUSE\nOne possible reason is that the user does not have the required \"Import relational metadata\" capability.\n\n\nRESOLVING THE PROBLEM\nGrant user the required \"Import relational metadata\" capability. \n\n\nSteps:\n1. In Cognos Connection choose menu 'Launch > IBM Cognos Administration'.\n2. Select tab 'Security'\n3. Select 'Capabilities' on the left side.\n4. Click \"Actions\" > Set Properties beside \"'Import relational metadata'.\n5. Select the 'Permissions' tab.\n6. Add the required user, group or role to the capability granting them Read, Execute and Traverse permissions.\n\n\nRELATED INFORMATION\n Importing relational metadata to Framework Manager [http://ibmurl.hursley.ibm.com/3PJO]", "question": "Framework Manager data source error \n\nUsers receive the following error on selecting a data source from the list defined in IBM Cognos within Framework Manager 10.2.2 Fix Pack 5\n\nalt text\n\nThat error (BMT-IMP-0002 Failed to Execute Metadata request. CM-REQ-4342 An error occurred with the client. CAF-WRN-2082 An error has occurred.) prevents all users to add an existing data source via Framework Manager.\n\nHow can we fix this?", "answer": "Grant user the required \"Import relational metadata\" capability."} +{"id": "TRAIN_Q261", "document": "IBM Disabling WebSphere administrative security when admin console is not accessible - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WebSphere administrative secuirty needs to be disabled and the admin console is not accessible. \n\nCAUSE\nThis can be caused by several reasons eg... server will not start with security enabled, forgot administrative password, etc...\n\nRESOLVING THE PROBLEM\nWARNING: Please use this as the last resort and make sure the server is not in the middle of processing any transactions. \n\nTo disable security, please perform the following steps via wsadmin:\n\n\n 1. /bin/>wsadmin -conntype NONE \n 2. wsadmin>securityoff \n 3. wsadmin>exit \n 4. Restart the servers. \n 5. Enable the security from administrative console. \n 6. Once the needed corrections are made, you can re-enable security in the admin console and then restart WebSphere.\n\n\nNOTE: To restart the servers, you will first need to manually kill the java process since security is still enabled in the currently running process. \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server System Management/Repository", "question": "Cannot Start JazzSM Dash after ObjectServer as a User Repository \n\nUnable to see the User roles and Groups in WebSphere Admin Console. Added Repositories in the WebSphere Admin Console. It was added under Security.\n\nConsole Settings > Websphere Administrative Console > Security > Global Security > Federated Repositories\n\nAdded Object Server Repository\n\nServer was stopped. Tried to restart but unable to start the JazzSM Dash server\n\nWhy would the server not restart?\n", "answer": "This can be caused by several reasons eg... server will not start with security enabled, forgot administrative password, etc..."} +{"id": "TRAIN_Q262", "document": "IBM Scroll bar in search results resets to the top position in Internet Explorer V9, V10, and V11 - United States ICN; Content Navigator; preview; IE V11; Firefox; Chrome; Microsoft Edge; scroll bar TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n In IBM Content Navigator, the scroll bar in the search results resets to the top position when using Microsoft Internet Explorer V9, V10, and V11. This does not happen with Mozilla Firefox or Google Chrome. \n\nCAUSE\nThis is a Microsoft Internet Explorer issue which has been fixed in the Microsoft Edge browser. \n\nRESOLVING THE PROBLEM\nUpgrade to Microsoft Edge browser to address the issue.\n\nRELATED INFORMATION\n Microsoft Edge support [http://www.ibm.com/support/docview.wss?uid=swg21976776]", "question": "Scroll bar in search results resets to the top position in Internet Explorer In IBM Content Navigator, scroll bar in search results resets to the top position in Internet Explorer V9, V10, and V11. This does not happen with Mozilla Firefox or Google Chrome. ", "answer": "Upgrade to Microsoft Edge browser to address the issue."} +{"id": "TRAIN_Q263", "document": "IBM Tivoli Monitoring 6.3.0 Fix Pack 6 (6.3.0-TIV-ITM-FP0006) - United States DOWNLOADABLE FILES\n\nABSTRACT\n This is a cumulative fix pack for IBM Tivoli Monitoring version 6.3.0. \n\nDOWNLOAD DESCRIPTION\nThis is a cumulative fix pack for IBM Tivoli Monitoring version 6.3.0. This fixpack is available as both an upgrade and fresh install.\n\n\n\nThe upgrade install for this Fix pack consists of the following files:\n\n\n\nFix pack file name Description 6.3.0-TIV-ITM_TMV-Linuxx-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux x86, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Linuxx64-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux x86_64, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Linuxz-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Linux on System z, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Unix-FP0006.tar.gz Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for Unix, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Windows-FP0006.zip Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 32-bit Windows, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Windows64-FP0006.zip Contains the IBM Tivoli Monitoring base product components, Performance Analyzer, the Warehouse Proxy and Summarization and Pruning agents for 64-bit Windows, as well as application support for the base agents and a selected set of IBM Tivoli Monitoring 6.x based distributed monitoring agents. 6.3.0-TIV-ITM_TMV-Agents-FP0006.tar.gz Contains the IBM Tivoli Monitoring base agents. This includes the following: Agentless Monitor (multiplatforms), i5/OS agent, Windows OS agent, Linux OS agent, UNIX OS agent, UNIX Logs agent, IBM Tivoli Universal Agent. 6.3.0-TIV-ITM_TMV-Tools-FP0006.tar.gz Contains the IBM Tivoli Monitoring 5.1.2 Migration Toolkit, the Distributed Monitoring Upgrade Toolkit and the Tivoli Event Integration event synchronization component. 6.3.0-TIV-ITM_TMV-Agent-Reports-FP0006.tar.gz Contains the IBM Tivoli Monitoring OS Agents Reports. 6.3.0-TIV-ITM_TMV-ITPA-Common-FP0006 .tar.gz IBM Tivoli Performance Analyzer Reports and Domain Definitions Multiplatform, Multilingual. 6.3.0-TIV-ITM_TMV-LP-FP0006.tar.gz Contains the IBM Tivoli Monitoring Language Pack for all platforms. \nThe pristine install images can be downloaded from the IBM Passport Advantage® Online Website: \n\n\nNumber of eAssembly to download Number of part to download Title on Passport Advantage Contents CRYB4ML CN8CPEN IBM Tivoli Monitoring V6.3.0.6 Base, Windows (32 Bit env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support in English for base agents for 32-bit Windows operating systems CRYB4ML CN8CQEN IBM Tivoli Monitoring V6.3.0.6 Base, Windows (64 Bit env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Windows operating systems CRYB4ML CN8CREN IBM Tivoli Monitoring V6.3.0.6 Base, Unix, English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for UNIX operating systems CRYB4ML CN8CSEN IBM Tivoli Monitoring V6.3.0.6 Base, Linux (32 Bit Env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 32-bit Env. Linux operating systems CRYB4ML CN8CTEN IBM Tivoli Monitoring V6.3.0.6 Base, Linux (64 Bit Env.), English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Env. Linux operating systems CRYB4ML CN8CUEN IBM Tivoli Monitoring V6.3.0.6 Base, Linux on System z®, English Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for Linux on System z operating systems CRYB4ML CN8CVEN IBM Tivoli Monitoring V6.3.0.6 Tools, Multiplatform, English Tivoli Monitoring event synchronization component, Tivoli Enterprise Console® Event Definition Generator (TEDGEN) utility, and audit record DTDs CRYB4ML CN8CWML IBM Tivoli Monitoring V6.3.0.6 Language Support Language pack for Tivoli Monitoring server components, warehouse agents, OS agents, agentless OS agents, Tivoli Performance Analyzer agent for all operating systems and languages CRYB4ML CN8CXML IBM Tivoli Performance Analyzer V6.3.0.6: Reports and Domain Definitions Multiplatform, Multilingual Performance Analyzer domains and BIRT reports CRYB5ML CN8CYML IBM Tivoli Monitoring V6.3.0.6 Agents, Multiplatform, Multilingual Operating system agents (IBM i, Linux, UNIX, Windows) and Agentless OS agents (AIX, HP-UX, Linux, Solaris, Windows) CRYB5ML CN8CZML IBM Tivoli Monitoring V6.3.0.6 Agent Reports Operating system agent reports and reports installer \n\nThe following levelset PTFs represent the equivalent maintenance level for the corresponding z/OS components which can be ordered via ShopzSeries: \n\nUA79950 -- MGMT SERVER DS (Code) \nUA79951 -- MGMT SERVER DS (Data) \nUA79952 -- ITMS/ENGINE 1 of 2 \nUA79953 -- ITMS/ENGINE 2 of 2 \n\n\n\nCreated/Revised by Date of Creation/Update Summary of Changes MBK 2015/07/21 Document created DMH 2015/12/11 Fix Pack Published \n\nURL LANGUAGE SIZE(Bytes) Installation and Setup Guide [http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2//com.ibm.itm.doc_6.3fp2/install/itm_install.htm] English 999999999 \nDOWNLOAD PACKAGE\n\n\nFix Central\n\n Fix Central provides fixes and updates for your system's software, hardware, and operating system. An IBM registered ID is required to obtain the fixes, which allows us to update you on any critical issues with the fix. Privacy is always maintained. \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-FP0006 11 Dec 2015 English 999999999 FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ETivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.3.0-TIV-ITM-FP0006&source=fc] [ ] \n [/support/docview.wss?uid=swg24040390&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24040390&aid=2]Problems (APARS) fixed\nIV55651 IV60994 IV63092 IV63947 IV65928 IV65987 IV66557 IV66841 IV66911 IV67076 IV67172 IV67425 IV67488 IV67982 IV67984 IV68546 IV68792 IV69144 IV69246 IV69577 IV69631 IV69716 IV70115 IV70669 IV70848 IV71253 IV71318 IV71473 IV71612 IV71647 IV71746 IV71863 IV71904 IV71943 IV72089 IV72146 IV72203 IV72314 IV72474 IV72801 IV73322 IV73382 IV73766 IV73792 IV73932 IV73936 IV73939 IV74037 IV74060 IV74065 IV74120 IV74283 IV74467 IV74486 IV74529 IV74707 IV74718 IV74758 IV75054 IV75229 IV75556 IV75571 IV75592 IV75908 IV76074 IV76109 IV76801 IV77408 IV77439 IV77462 IV77775 IV78573 IV79364", "question": "Where can I get ITM 6.3.0 Fixpack 6 ? Is it available now ? Where can I get ITM 6.3.0 Fixpack 6 ? Is it available now ?", "answer": "6.3.0-TIV-ITM-FP0006 11 Dec 2015 English 999999999 FC [http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm%7ETivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.3.0-TIV-ITM-FP0006&source=fc]"} +{"id": "TRAIN_Q266", "document": "IBM WebSphere DataPower is not affected by the Bash vulnerabilities (CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278)\nFlash (Alert) - United States CVE-2014-6271 CVE-2014-7169 DataPower Bash FLASH (ALERT)\n\nABSTRACT\n DataPower is not vulnerable to the Bash vulnerabilities that have been referred to as “Bash Bug” or “Shellshock” and the two memory corruption vulnerabilities. \n\nCONTENT\nDataPower does not use Bash anywhere. Hence it is not impacted by any of the Bash vulnerabilities. \n\nIn particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278. \n\nIBM recommends that you review your entire environment to identify vulnerable releases of Bash and take appropriate mitigation and remediation actions.", "question": "Is DataPower affected by the bash environment variable vulnerability CVE-2014-6271 or CVE-2014-7169 Is DataPower affected by the recent vulnerability reported through CVE-2014-6271 or CVE-2014-7169?\n\nhttp://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-6271 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-7169", "answer": "In particular, DataPower in all editions and all platforms is NOT vulnerable to the Bash vulnerabilities: CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277, and CVE-2014-6278."} +{"id": "TRAIN_Q267", "document": "IBM ITCAM Agent for SAP Applications, 7.1.1.1-TIV-ITM_SAP-IF0001 - United States DOWNLOADABLE FILES\n\nABSTRACT\n This IFix resolves the APARs and defects listed in the \"Problems Fixed\" section below \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2014.\n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager Agent for SAP\nApplications, Version 7.1.1 Fix Pack 0001 \n\nComponent ID: 5724B97SO\n\nFix: Interim Fix 0001, 7.1.1.1-TIV-ITM_SAP-IF0001\n\nDate: 31 December 2014\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\n1.0 General description\n========================\n\nThis interim fix resolves the APARs and defects listed in the \n\"Problems Fixed\" section below.\n\n2.0 Problems fixed in 7.1.1.1-TIV-ITM_SAP-IF0001\n=====================================================\nThe following problems are addressed by this interim fix.\n\n2.1 APARs\n---------- \n\nAPAR: IV63525\nAbstract: CUSTOMER IS GETTING 0 ENTRIES FOR THE OUTPUT OF THE \nFUNCTION MODULE /IBMMON/ITM_QOUT_GET_QUEUES.\nAdditional Information: The /IBMMON/ITM_QOUT_GET_QUEUES function \nmodule stopped collecting the data even though the data was \npresent in the SAP system. Due to this, SYSID ‘+++’ was \ndisplayed on the Tivoli Enterprise Portal. The function module\nhas been rectified for collecting the data from the SAP \nsystems having versions greater than 46C and SP level \nSPKB46C39.\n\nAPAR: IV60733\nAbstract: MPS CX_SY_CONVERSION_NO_NUMBER IN FUNCTION MODULE\nIBMMON/ITM_FILE_SYSTEM\nAdditional Information: ABAP dump ‘Conversion Error –unable to \nhandle‘---‘ as a number ’ for the / IBMMON/ITM_FILE_SYSTEM\nfunction module is gracefully handled towards File Systems \nattribute group.\n\n2.2 Defects\n------------\n\nDefect: 58382 \nAbstract: Exception condition \"GWY_COMMUNICATION_FAILURE\" raised.\nAdditional Information: \"GWY_COMMUNICATION_FAILURE\" has been \ngracefully handled for the /IBMMON/ITM_GWY_CONNECTIONS \nfunction module towards the Gateway Connections attribute \ngroup.\n\nDefect: 55733\nAbstract: TEP Remote configuration of SAP Agent is not working on \nnon-windows after remote upgrade.\nAdditional Information: While getting the Config parameters from the\n\".cfg\" file, the two parameters for gateway are removed from \nthe parameters that are being sent to the Tivoli Enterprise \nPortal Configuration Panel. Also the \".cfg\" file is updated \nby removing those parameters. Then, reconfiguration of Agent \nInstance with appserver and logon mode through Tivoli \nEnterprise Portal is successful after remote upgradation to\n711FP1 IF1.\n\nDefect: 55366\nAbstract: ABAP Dumps when Job Name is not present in SAP standard\ntable.\nAdditional Information: Exception handling was missing for the\nscenario of the Job Name not being present in the SAP standard\ntable. The issue has been fixed by adding the required \nexception handling for Workspace Integration engine background\njobs when Job is not present in SAP.\n\n\n2.3 Enhancements\n----------------\n\nEnhancement: 67334\nAbstract: Additional functionality to handle the MAI missing Alerts \nin the Function Module /IBMMON/ITM_MAIALRT_INX. \nAdditional Information: Function module /IBMMON/ITM_MAIALRT_INX is \nmodified to fetch the MAI Alerts which are missed by ITM SAP\nAgent as these MAI Alerts are inserted into table \n/IBMMON/ITM_ALIX with some delay by SAP.\nNote: \n1) SAP system time and ITCAM SAP Agent machine time should be\nin sync upto accuracy of seconds.\n2) In order to have full collection of MAI Alerts, there is \nan additional overlap time being added to the sampling time \nfrequency given by the ITCAM SAP Agent.\nThis additional overlap time is configurable parameter on \nthe SAP side\nPlease note -\na)By default the additional overlap time will be 1 min i.e. \n60 seconds. \nb)Maximum additional overlap time which can be configured \nwill be 5 mins i.e. 300 seconds. \nc)If the user wants the additional overlap time greater than\n1 min i.e. 60 seconds and less than or equal to 5mins i.e.\n300 mins, then he should follow the below steps.\n\nPlease find below the steps to configure this additional \noverlap time on SAP side:\n• Go to transaction code SE16.\n• Enter the table name as '/IBMMON/ITM_CNFG' and press 'F7'.\n• Execute the database table '/IBMMON/ITM_CNFG' or press 'F8'.\n• Add the additional overlap time parameter as ‘MAI_PERD_OV’\nin the database field 'ITM Configuration Parameters' and \nthen add the additional overlap time in seconds in the \ndatabase field 'VALUE_INT' and save it.\n\n\n2.4 Superseded fixes\n---------------------\n7.1.1-TIV-ITM_SAP-FP0001\n7.1.1-TIV-ITM_SAP-IF0001\n\n-------------------------\n\n2.5 APARS, Defects and Enhancements included from superseded fixes\n------------------------------------------------------------------\nThis section contains list of defects fixed / enhancements made in \nprevious releases. To get more details on these changes please refer\nthe README for that particular release.\n\n--------------------------------\n7.1.1-TIV-ITM_SAP-FP0001\n--------------------------------\n\n\nAPAR: IV60177\nAbstract: TEPS DISPLAYS ALERT TIMESTAMP AS UTC \nAdditional Information: MAI Alerts stored in the database table\n'/IBMMON/ITM_ALIX' are in the UTC format.So while fetching \nsuch MAI Alerts, conversion from UTC time zone to current \nsystem time zone is required.\n\nAPAR: IV60254\nAbstract: 'TRANSACTION PERFORMANCE' AND 'R/3 TRANSACTION PERFORMANCE'\nMODULES ARE NOT SENDING DATA FOR HDC \nAdditional Information: Code has been changed in Transaction\nperformance logic which creates 'KSATRANS' file to display\nhistorical data on TEP for Transaction performance.\n\nAPAR: IV60989\nAbstract: EMPTY WORKSPACE FOR BUSINESS PROCESS MONITORING AND\nSYSTEMMONITORING IN TEP\nAdditional Information: Code changes have been done to handle\nexceptions for the SAP standard DSWP_BPM_SOLUTION_ID_CONVERT \nfunction module and for the /IBMMON/ITM_MAIBP_MONITORING \nMAI BPM function module.\n\nAPAR: IV61450\nAbstract: REMOVE PERIOD START/END ATTRIBUTES OF XML MESSAGE LOGS \nAdditional Information: The attributes 'Period Start' and 'Period\nEnd' are used by the agent internally and aren't helpful\nto customer in anyway. In order to hide them from attribute \nview, the 'USAGE' and 'COST' tags have been set to appropriate\nvalues. Also, the queries that define the attribute view have\nbeen modified to remove the 'Period Start' and 'Period End'\nattributes. \n\nAPAR: IV59319\nAbstract: SAP AGENT NOT PICKING UP ALERTS FROM SOLUTION MANAGER \nAdditional Information: This is DOC APAR and the third Party OS \ncommand adapter should be configured and mail notification \nshould be enabled using appropriate steps. \n\nDefect: 53372\nAbstract: Unable to start SAP Agent when candlehome contains ‘SAP’\nword.\nAdditional Information: Post install script ignores variables\ncontaining 'SAP' keyword and they are not included in 'ksaenv'\nfile. When CANDLEHOME and JAVAHOME contained 'SAP' keyword,\nthey were ignored as well resulting in failure to start \nksaagent.\n\nDefect: 49745\nAbstract: Agent doesn't read syslog.idx file correctly\nAdditional Information: SAP agent read '_syslog.idx' incorrectly\nleading to corrupt '.idx' file. This resulted in system log not\ngetting detected sometimes.\nNote: This issue is reproducible only with multi instance SAP\nsystem. \n\nDefect: 47233\nAbstract: Test connection utility is not working on windows as\ndesigned for application server mode.\nAdditional Information: With the new NWRFC library, 'Gateway Host' \nand 'Gateway service' are not required while creating a RFC\nconnection with the SAP server. So, these fields have been \nremoved from the agent configuration panel. \n\nDefect: 45898\nAbstract: R/3 action link of ‘Close Alert��� and ‘Close Alerts of the\nsame type’ are missing in ‘Alert Information’ view of CCMS\nmonitoring workspaces.\nAdditional Information: The workspace has been modified to create the\ntwo missing links. Also, the code on the SAP side has been \nfixed to correct the close alert mechanism. \n\nEnhancement: 44620\nAbstract: Netweaver RFC support added for SAP Agent common\nlayers.\nAdditional Information: Netweaver RFC v7.20 support has been added.\nCommunication with SAP system will now happen using the NWRFC\nlibrary instead of the Classic RFC library. \n\nEnhancement: 44663\nAbstract: Logging of SAP 'Component Version Id' and 'Interim Fix Id'\nin the agent log file.\nAdditional Information: SAP 'Component Version Id' and 'Interim Fix\nId' are returned as additional parameters by the \n'/IBMMON/ITM_FUNC_PARMS' function module and can be viewed in\nthe agent logs with minimum trace level enabled.\n\nEnhancement: 45911\nAbstract: Facilitate remote connection of type 'Internal Connection',\n'Connections via ABAP driver' and 'TCP/IP' Connections defined\nin SAP server.\nAdditional Information: This link has been provided from the 'Test\nConnection' link in the 'Connection Monitoring' workspace to \ncheck the status of a remote connection on demand.\n\nEnhancement: 45973\nAbstract: Facilitate single Unicode ITM file containing both BADI and\nnon-BADI objects. \nAdditional Information: Single ITM file has been provided to import\nthe SAP Agent transport on all supported SAP versions having \nBADI or non-BADi implementation.\n\n--------------------------------\n7.1.1-TIV-ITM_SAP-IF0001\n--------------------------------\n\nAPAR: IV53685\nAbstract: TRANSPORT IMPORT FAILS FOR ITM_CONN_CHECK FUNCTION MODULE.\nAdditional Information: 711 GA transport fails with ABAP dump for the\n/IBMMON/ITM_CONN_CHECK function module. Because of this, the \ndata is not collected and displayed on the Tivoli Enterprise\nPortal for some attribute groups, and the dumps are generated \non SAP side.\n\nAPAR: IV52434\nAbstract: ATTRLIB MISSING SLASH IF INSTANCE IS CREATED USING \nADDSYSTEM. \nAdditional Information: Because of the missing slash in ATTRLIB \nfield name, the agent is configured incorrectly that hampers \nthe agent functionality and Historical Data Collection (HDC). \nThis problem occurs when the SAP agent instance is created by \nusing the tacmd Addsystem command, and the same instance is \nreconfigured.\n\nAPAR: IV51184\nAbstract: FUNCTION MODULE \"/IBMMON/ITM_SYS_LOG\" GENERATING ABAP \nDUMP.\nAdditional Information: The \"IBMMON/ITM_SYS_LOG\" function module is \ninvoked every 10 minutes and it generates ABAP dumps.\n\"/IBMMON/ITM_SYS_LOG\" function module was called with \n\"ITM_R3_LOG_RECORD\" parameter. This parameter is not defined. \nThe Syslog information is available from INS and GRP subnodes,\nhowever, problem occurs only while collecting the data for \n:GRP subnode.\n\nAPAR: IV47613\nAbstract: ABAP DUMPS DUE TO OVERFLOW IN /IBMMON/ITM_CCMS_ALERTS \n(ALERT UNIQUE ID). \nAdditional Information: Added a new attribute named \n'Extended Alert Unique Identifier' to hold bigger alert unique \nidentifier. The extended alert unique identifier attribute is \nused to close an alert in the SAP system.\n\nDefect: 43177 \nAbstract: Data is not coming for ‘ITM_USER_INFORMATION’ for ':Sys' \nnode.\nAdditional Information: The code considered only the 'INS' node.\nTherefore, the user information link in the 'SYS' node did not\nreceive any data. \n\nDefect: 43075 \nAbstract: 'No Applicable data' seen for CCMS Monitoring on ALL Grp \nnode along with 9911 alert in second call of agent in case of \nCEN configured SAP.\nAdditional Information: When retrieving alerts for the first call of\nthe new CCMS design for GRP node in case of Central (CEN) \nsystem, 'No Applicable Data' is displayed on the Tivoli \nEnterprise Portal. The second call of the agent was \ngenerating a 9911 alert.\n\nDefect: 42393 \nAbstract: Argument column in \"Lock Information\" is showing invalid \ndata.\nAdditional Information: Lock argument of locked object shows string \n'[][][][][][][]' on the Tivoli Enterprise Portal, when all \npossible fields are responsible for locking that object. \n\nDefect: 42317\nAbstract : Delete transport unable to delete reference of agent BADI\nclass from MAI configured SAP system. \nAdditional Information: BADI delete transport must be able to \ndelete all relevant BADI classes and implementations from the \nsystem where BADI is imported.\n\nDefect: 40637 \nAbstract: Exception condition \"ITM-NOT_FOUND\" raised in case syslog\nrecords are not found at SAP side. \nAdditional Information: If particular syslog details are not present \non the SAP system, then while accessing syslog details using \nsys_detail link on the Tivoli Enterprise Portal, a \"Exception \ncondition 'ITM-NOT FOUND' raised\" short dump is generated on \nthe SAP side and a blank screen is displayed on the Tivoli \nEnterprise Portal.\n\nDefect: 39686 \nAbstract: Syslog causing ABAP dump for Group Sub Node. \nAdditional Information: For the logs and traces attribute group of \nthe GRP node, exceptions are raised. \n\nDefect: 39681 \nAbstract: Data is missing for many columns of ITM_JOBS. \nAdditional Information: Data is not displayed for many columns of \nITM_Jobs.\n\nDefect: 39007 \nAbstract: \"No applicable Data\" row should be seen on TEP for system \nlog under system name. \nAdditional Information: If there is no data for the \"System Log\" \nworkspace, then, \"No applicable data\" must be displayed in the \nSystem Name column. \n\nDefect: 38998 \nAbstract: Unable to interpret X as a number in function module\n/IBMMON/ITM_HOSTS. \nAdditional Information: If the SAP system contains more than 9 \napplication servers (RFC servers), the \"Unable to interpret * \nas a number\" message is displayed in the /IBMMON/ITM_HOSTS \nfunction module.\n\nDefect: 38995 \nAbstract: Tivoli SAP agent causing dump in SAP on UNIX server. \nAdditional Information: If an exception occurred while reading job \nlog, the /IBMMON/ITM_JOB_LOG function module is terminated. \n\nDefect: 38903 \nAbstract: IDOC Number not included in the Display item. \nAdditional Information: The \"IDOC Number\" is not available to use \nas a display item in situations. \n\nDefect: 38251 \nAbstract : Data is getting fetched for invalid sub-nodes.\nAdditional Information: Data must be returned only for the sub node \nthat is called; data must not be returned for other irrelevant\nsub nodes. Call from the agent gives ITM_MGROUP or Origin node \nas input to most of the function modules that contain the node \ndetails.\n\nEnhancement: 38724\nAbstract: \"Client\" column is required for ITM_IDOC workspace to \ndifferentiate the respective client's data. \nAdditional Information: Added a \"Client\" column in the \n\"IDOC Information\" view of the \"Data Transfer Information\" \nworkspace. The “Client” column shows the client name for the \nrespective data of client.\n\n\n3.0 Architecture and prerequisites\n===================================\nThis Fix Pack is supported on all operating systems listed in the IBM\nTivoli Composite Application Manager Agent for SAP Applications\nInstallation and Configuration guide, Version 7.1.1 Fix Pack 1:\nLink:\nhttp://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/sap/sap_landing_install.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/sap/sap_landing_install.html]\n\nThe following website contains the latest certification information:\nSoftware Product Compatibility Reports (SPCR)\nhttp://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html [http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html]\n\nYou can also find system requirements for ITCAM for Applications V7.2.1\nFix Pack 1 at:\nhttp://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/prerequisites/apps7211_systemreqs.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/prerequisites/apps7211_systemreqs.html]\n\nITCAM for Applications 7.2.1.1 Knowledge Center:\nhttp://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/welcome_apps7211.html [http://www-01.ibm.com/support/knowledgecenter/SS3JRN_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/welcome_apps7211.html]\n\n3.1 Prerequisites for this fix\n------------------------------\nThe prerequisite level for this fix is as follows:\n- IBM(R) Tivoli(R) Composite Application Manager Agent for SAP\nApplications, Version 7.1.1 Fix Pack 0001\n\n7.1.1 Fix Pack 0001 ISO Part Number:\nPhysical Part Number: ITCAM Agent for SAP Applications CBHU9ML\nElectronic Part Number: ITCAM Agent for SAP Applications CN0MJML \n\nCustomer need to download separately 7.1.1 Fix Pack 0001 GA ISO \nimage from Passport Advantage.\n\n\n- IBM Tivoli Monitoring, Version 6.2.3 FP3 \n\nBecause this fix is cumulative, it can be installed on any fix level\nfor this version, release, and modification level later than the\nprerequisite.\n\n\n4.0 Image directory contents\n=============================\nThis fix image contains the following files:\n- 7.1.1.1-TIV-ITM_SAP-IF0001.README - This README file\n- 7.1.1.1-TIV-ITM_SAP-IF0001.tar - Fix archive .tar format\n- 7.1.1.1-TIV-ITM_SAP-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 environment; use the .zip file if\nyou are working in a Windows environment.\n\n\n5.0 Installation instructions \n=============================\n\nThis fix can only be installed over an existing installation of\n711 FP0001. Use the following steps to install this fix.\n\n5.1 Before installing the fix \n-----------------------------\n- The prerequisites listed under section 3.1 entitled 'Upgrade \nPrerequisites for this fix' must be installed when for upgrade.\n\n- For the purpose of this README, the symbol 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 interim fix on UNIX systems, set the CANDLEHOME \nenvironment variable 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 interim fix, be 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(7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary\ndirectory on the system that contains the agent to be updated.\nFor the purpose of this README, the symbol represents the\nfully qualified path to this directory. Note: On Windows systems,\nthis 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 supported\noperating systems.\n\n3. Use the \"itmpatch\" command to install the fix for the operating\nsystem for that agent. For more information on the \"itmpatch\" \ncommand, see section [6.2]. \n\nOn UNIX systems, if the fix was expanded to \n/7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:\n\n> /7.1.1.1-TIV-ITM_SAP-IF0001/itmpatch -h \n-i /7.1.1.1-TIV-ITM_SAP-IF0001/ksa_xxxxxx_tema_if0001.tar\n\nwhere:\n- xxxxxx corresponds to the value in the first column \nreturned by the ./cinfo -i command. \n\nIn the following example, the file is \n\"ksa_li6263_tema_if0001.tar\".\n> ./cinfo -i\n[Monitoring Agent for Your Product]\n[lx8266 Version: 07.11.01.01] \n\nOn Windows systems, if the fix was expanded to \n\\7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:\n\nFor Windows 32-bit\n> \\7.1.1.1-TIV-ITM_SAP-IF0001\\itmpatch -h \n-i \\7.1.1.1-TIV-ITM_SAP-IF0001\\ksa_winnt_tema_if0001.cab\n\nFor Windows 64-bit \n> \\7.1.1.1-TIV-ITM_SAP-IF0001\\itmpatch -h \n-i \\7.1.1.1-TIV-ITM_SAP-IF0001\\ksa_wix64_tema_if0001.cab\n\nNote: if the itmpatch command gets this error:\n\"The application has failed to start because its side-by-side\nconfiguration is incorrect. Please see the application event\nlog for more detail.\" it's necessary install the \"visualstudio\nredistribution package\" before to run the itmpatch command.\n\nFor a 32bit architecture,\nthe name of this package is vcredist_x86.exe, available at\nhttp://www.microsoft.com/en-us/download/details.aspx?id=5582 [http://www.microsoft.com/en-us/download/details.aspx?id=5582]\n\nFor a 64bit architecture,\nthe name of this package is vcredist_x64.exe,available at \nhttp://www.microsoft.com/en-us/download/details.aspx?id=2092 [http://www.microsoft.com/en-us/download/details.aspx?id=2092]\n\n\n5.3 Remote agent update\n----------------------------\n1. Transfer the appropriate archive file \n(7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to a temporary\ndirectory on the IBM Tivoli Enterprise Monitoring Server system.\nFor the purpose of this README, the symbol represents the\nfully qualified path to this directory. Note: On Windows systems,\nthis 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 supported\noperating systems.\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 Command Reference.\n\nOn UNIX systems, \nif the fix was expanded to /7.1.1.1-TIV-ITM_SAP-IF0001:\n> $CANDLEHOME/bin/tacmd addBundles -n -i \n/7.1.1.1-TIV-ITM_SAP-IF0001 \n\nOn Windows systems, \nif the fix was expanded to \\7.1.1.1-TIV-ITM_SAP-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i \n\\7.1.1.1-TIV-ITM_SAP-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. 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. After \"tacmd addBundles..\" from step 3 above, control files\non the Tivoli Enterprise Monitoring Server and the\nTivoli Enterprise Portal Server must be updated.\nThese updates must be done manually.\n\na. Tivoli Enterprise Monitoring Server update\nThe sa_dd_07110101.xml and sa_dd.properties files must be\ncopied from the /7.1.1.1-TIV-ITM_SAP-IF0001\ndirectory to the 071001000 version of the Tivoli Enterprise\nMonitoring Services depot.\n\nTwo scripts are provided to make these copies and are \nin the fix /7.1.1.1-TIV-ITM_SAP-IF0001 directory\nafter the expansion of the tar or zip file:\n\nksa_patchdepot.bat - Windows\nksa_patchdepot.sh - UNIX\n\nFrom the /7.1.1.1-TIV-ITM_SAP-IF0001 directory,\nrun the appropriate script based on the operating system. The\nscript output contains details about the copies being made.\n\nb. Tivoli Enterprise Portal Server update\nResource files must be copied from the\n/7.1.1.1-TIV-ITM_SAP-IF0001 directory to the\nTivoli Enterprise Monitoring Portal directory.\n\nTwo scripts are provided to make these copies and are \nin the fix /7.1.1.1-TIV-ITM_SAP-IF0001 directory\nafter the expansion of the tar or zip file:\n\nksa_patch_resource_teps.bat - Windows\nksa_patch_resource_teps.sh - UNIX\n\nFrom the /7.1.1.1-TIV-ITM_SAP-IF0001 directory,\nrun the appropriate script based on the operating system. The \nscript output contains details about the copies being made.\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 \n\"tacmd login\" and \"tacmd updateAgent\" commands, see the IBM \nTivoli Monitoring Command Reference.\n\nOn UNIX systems: \n> $CANDLEHOME/bin/tacmd login -s \n-u \n-p \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 sa \n-n \n-v 07110101\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s \n-u \n-p \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 sa \n-n \n-v 07110101\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is \nspecified as two characters (sa), not three characters (ksa).\n- The node (-n) for the \"tacmd updateAgent\" command is the \nmanaged system name of the operating system (OS) agent to be \nupdated. The target node for the \"tacmd updateAgent\" command \nis always an OS agent.\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. \nNote: If SDA feature is enable at the HUB TEMS, then below steps are\nare not required. SDA will install only browser support and if\ncustomer is using TEP Desktop then install the support manfully\nas shown below.\n\nThis fix (7.1.1.1-TIV-ITM_SAP-IF0001) includes changes to the\nagent support files that must be installed. If you installed these\nupdates, there are no additional installation steps. If you did not\ninstall these updates, use the following steps to update the Tivoli\nEnterprise Monitoring Server, Tivoli Enterprise Portal Server, or\nTivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file\n7.1.1.1-TIV-ITM_SAP-IF0001.tar or .zip) to the Tivoli\nEnterprise Monitoring Servers, Tivoli Enterprise Portal Servers,\nor 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 (ksa_tems_teps_tepd_if0001.tar or .zip)\nthat contains the updates for the 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 directory\nstructure that includes a subdirectory called CD-ROM, with the\nnecessary updates.\n\n4. Use the Application Support Installer(ASI) GUI or the silent\ninstallation method to install the application support files. \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 ] [-j ] \n\nOn Windows systems:\n> itmasi [-h ] [-j ] \n\nWhen prompted by the Application Support Installer for the \ninstallable media directory, select the CD-ROM directory, not the\ncomponent directory. The installer can install updates for \nmultiple components at the same time.\n\nNote: For IBM Tivoli Monitoring Version 6.3 or above, one \nof the following additional steps must be performed.\n\n1. Aquire 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 32-bit java(r) 1.5 or java 1.6 installation when running \nthe itmasi.sh or itmasi.bat script described below. \n\n5. The next panel presented by the Application Support Installer \nasks for the selection of Tivoli Monitoring components to which \nyou want to add application support. For this fix, check or \nclear the check boxes as follows:\n\n[checked | unchecked] - Tivoli Enterprise Monitoring Server (TEMS)\n[checked | unchecked] - Tivoli Enterprise Portal Server (TEPS)\n[checked | unchecked] - Tivoli Enterprise Desktop Client (TEPD)\n\nContinue through the remaining GUI panels selecting SAP Agent\n07.11.01.01 support to complete the installation.\n\n6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise \nPortal Browser was running when the update was installed, it must\nbe restarted.\n\n7. If the Tivoli Enterprise Monitoring Server being updated is remote\n(not a Hub Tivoli Enterprise Monitoring Server) then restart the \nTivoli Enterprise Monitoring Server.\n\n5.5 Installing SAP agent transport\n------------------------------------\nNote: From this fix onwards,a single ITM file has been provided for\nimporting SAP transport on all supported SAP versions having BADI or\nnon-BADI implementation.\n\nThis procedure installs the SAP transport into the SAP system. You\nare not required to uninstall the previous transport before\ninstalling this transport.\n\n1. Go to the ABAP directory in the location where you expanded the\nfix archive file.\n\n2. Copy the transport files into the SAP environment as follows: \n\na. The following two sets of transport files are in the \nABAP directory of the SAP agent fix archive:\n\n1) K711_00103U.ITM and R711_00103U.ITM in /ABAP directory.\nThese files are Unicode versions of the transport. \n\n2) K711_00103_DELETE.ITM and R711_00103_DELETE.ITM\nThese transport files remove the ABAP code. Do not import\nthe DELETE transport unless you stop using the product \nentirely and want to remove the transports from your SAP\nsystems.\n\nb. Copy your transport files to the SAP Transport System data\ndirectory as follows:\n\n1) Copy the K711_00103U.ITM file to the cofiles directory.\n2) Copy the R711_00103U.ITM file to the data directory.\n\n3. Run the following command for non-BADI and BADI where:\nSID Target SAP : system ID\nPROFILE_NAME : Name of the tp profile file\nnnn : Number for the target client where the agent is to run\n\ntp addtobuffer ITMK711_00103U SID\npf=\\usr\\sap\\trans\\bin\\PROFILE_NAME\ntp import ITMK711_00103U SID client=nnn U16\npf=\\usr\\sap\\trans\\bin\\PROFILE_NAME\n\n\nAlternately, you can use the SAP STMS transaction to import the\ntransport requests. Ensure that the Import Transport Request Again \nand the Overwrite Objects in Unconfirmed Repairs options are \nchecked on the Import Options tab of the Import Transport Request\nwindow.\n\n\n6.0 Additional installation information\n========================================\n\n6.1 Installation instructions for agent baroc file\n------------------------------------------------------\nThis fix (7.1.1.1-TIV-ITM_SAP-IF0001) includes changes to the\nagent baroc files that must be reinstalled. If you have already\ninstalled these baroc files, there are no additional installation\nsteps. If you have not installed the files, see the \"IBM Tivoli\nMonitoring, Version 6.2.2FP2: Installation and Setup Guide\" \n(ITM6.2.2FP2 Installation and Setup Guide.pdf) under \n\"Installing monitoring agent baroc files on the event server\" in the\n\"Installing the IBM Tivoli Enterprise Console Event Synchronization\" \nsection for more information.\n\n6.2 Additional information on using the itmpatch command\n---------------------------------------------------------\nThe itmpatch command has the following syntax.\n\nUsage: itmpatch -h [OPTIONS]\n\nitmpatch -h \n-t { | }\n\nitmpatch -h \n-i { | }\n\nwhere:\n\n-h Specifies the IBM Tivoli Monitoring installation directory\n-i Specifies the path to the directory or patch file to be installed\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> /bin/itmpatch -h -t \n\n- To install the fix, use the \"-i\" option:\n> /bin/itmpatch -h -i \n\nwhere: \n is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n represents the fully qualified directory specification, \nwhere the fix is located. On Windows systems, this path must \ninclude the drive letter.\n\n6.3 Verifying the update\n------------------------\n1. To verify that the agent was updated correctly, use the tacmd\ncommand to view the current version of the agent after the agent\nis restarted. You are required to log in to a Tivoli Enterprise\nMonitoring Server before 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 \n-u \n-p \n> $CANDLEHOME/bin/tacmd listSystems -t sa\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 \n-u \n-p \n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t sa\n\nNote:\n- The component (-t) for the tacmd listSystems command is\nspecified as two characters (sa), not three characters (ksa).\n\nWhen the agent update is successful, the agent version is \n07.11.01.01\n\nNote:\n- The component (-t) for the tacmd listSystems command is\nspecified as two characters (sa), not three characters (ksa).\n\nWhen the agent update is successful, the agent version is \n07.11.01.01\n\nAfter the agent is restarted, you can also use the GUI to verify\nthat the agent was successfully updated.\n\nFor the agent on Windows systems, the version number is\n07.11.01.01\nFor the agent on UNIX systems, the version number is\n07.11.01.01\n\n2. To verify that the agent support files were updated correctly,\nuse the kincinfo command on Windows systems or the cinfo command\non Linux(R) or UNIX systems. The sample output below shows the\nversions of the Tivoli Enterprise Portal Server, Tivoli Enterprise\nMonitoring Server, or Tivoli Enterprise Portal Desktop systems \nafter this fix has been successfully applied.\n\nNote:\n- The date of the build displayed might not be accurate. This is\na known problem.\n\nOn Linux systems:\n--------------------\nTo validate that all components have been installed, run the\nfollowing command:\n\nFor example: \n> %CANDLE_HOME%/bin/cinfo -i\n\nNote: cinfo output may differ depending on ITM version.\n\n*********** Fri Dec 5 10:14:10 IST 2014 ******************\nUser: root Groups: root bin daemon sys adm disk wheel pkcs11\nHost name : IBMSAP1V9 Installer Lvl:06.23.03.00\nCandleHome: /opt/ibm\n***********************************************************\n...Product inventory\n\nax IBM Tivoli Monitoring Shared Libraries\nli6263 Version: 06.23.03.00\n\ngs IBM GSKit Security Interface\nli6243 Version: 07.40.43.00\n\njr Tivoli Enterprise-supplied JRE\nli6263 Version: 06.12.00.00\n\nsa IBM Tivoli Composite Application Manager Agent for SAP \nApplications\nli6263 Version: 07.11.01.01\n\nue Tivoli Enterprise Services User Interface Extensions\nli6263 Version: 06.23.03.00\n\nui Tivoli Enterprise Services User Interface\nli6263 Version: 06.23.03.00\n\n\n7.0 Known problems and workarounds\n===================================\n\nAbstract: While configuring the agent instance on UNIX, more than 3 \nletters are accepted as instance ID. \nProblem: Three letters are accepted as Instance ID while configuring \nagent instance on UNIX. This can result in failure to connect\nto the SAP system as the \".cfg\" file for that instance will\nbe generated with a wrong name.\nWorkaround:\nThe user should make sure that only three lettered name is \nentered as the instance ID while configuring an agent instance. \n\n\n8.0 Additional product information\n==================================\n\nABAP Transport Compatibility:\n------------------------------\nEach fix includes an updated agent executable\nprogram (ksaagent or ksaagent.exe) and an updated ABAP transport.\nInstall both programs to obtain the highest level of support.\n\nIn some situations, you cannot install\na new transport immediately because of change control processes on the\nmySAP systems. In these situations, sometimes you can run a new agent\nexecutable with a prior version of the ABAP transport. This section \nexplains when it is possible to run a newer agent executable program\nwith an older version of an ABAP transport.\n\nNote: The mySAP agent does not run correctly if not installed with\na compatible level of the transport.\n\nFix Level Delivered Transport Minimum Transport Level\n----------- ------------------- -----------------------\nFP0001-IF0001 ITMK711_00103U ITMK710_00103U\nFP0001 ITMK711_00100U ITMK711_00100U\nIF0001 ITMK711_00099U ITMK711_00098U\n711 GA ITMK711_00098U ITMK711_00098U\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\n\nINSTALLATION INSTRUCTIONS\nPlease refer to the 7.1.1.1-TIV-ITM_SAP-IF0001.README contained in the description section above for general installation instruction\n\nDOWNLOAD PACKAGE\nPlease refer to the 7.1.1.1-TIV-ITM_SAP-IF0001.README contained in the description section above for general installation instructions\n\n\nPROBLEMS SOLVED\nIV63525; IV60733\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] Fix Central Download Link 31 Dec 2014 English 89354240 FC [http://www.ibm.com/support/fixcentral/quickorder?product=ibm%2FTivoli%2FTivoli+Composite+Application+Manager+for+Applications&fixids=7.1.1.1-TIV-ITM_SAP-IF0001&source=SAR] [ ] \nPRODUCT ALIAS/SYNONYM\n 7.1.1.1-TIV-ITM_SAP-IF0001 \n\n [/support/docview.wss?uid=swg24039150&aid=1]Problems (APARS) fixed [/support/docview.wss?uid=swg24039150&aid=2]Problems (APARS) fixed\nIV63525, IV60733", "question": "SAP Agent suddenly crashed \n\nHello, my SAP Agent 7.1.1.1 crashed suddenly. I was able to restart it and since then it is working smoothly, but I would like to understand the root cause to avoid any reoccurrence. \n\nAny idea ?", "answer": "Defect: 58382 \nAbstract: Exception condition \"GWY_COMMUNICATION_FAILURE\" raised.\nAdditional Information: \"GWY_COMMUNICATION_FAILURE\" has been \ngracefully handled for the /IBMMON/ITM_GWY_CONNECTIONS \nfunction module towards the Gateway Connections attribute \ngroup."} +{"id": "TRAIN_Q269", "document": "IBM Datacap Rulerunner server stops after several aborted batches - United States Rulerunner hang stop abort TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After several batches abort consecutively in Rulerunner, all threads shut down. \n\nCAUSE\nRulerunner has a thread control feature that acts as a safety to prevent all pending batches from aborting. When it detects a certain number of consecutively aborted batches on a single thread, Rulerunner shuts down all threads. By default, the threshold is three batches, so shutdown occurs if four batches abort consecutively.\n\nDIAGNOSING THE PROBLEM\nWith Rulerunner logging turned on, aborting batches will show in the rulerunnerX.log files (where X is the thread number. If there is a question as to whether a Rulerunner shutdown is being caused by this feature, check the rulerunnerX logs for each thread to see if there are four consecutive aborts followed by a shutdown.\n\nRESOLVING THE PROBLEM\nIf there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.\n\n\nx86 (32-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nIndividual processors [default: 1] \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nprocessor Attempts [default: 3] \n\n \n\nx64 (64-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart Individual processors [default: 1) \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart processor Attempts [default: 3] \n\n \n\n * Restart Individual processors - 1 is on, 0 is off. \n * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable Windows 8.1.0.3", "question": "Controlling stop and starting of Rulerunner Service \n\nHi\n\nDatacap version 9.0.1\n\n Is there a way of issuing a controlled shutdown request so the thread has time to finish processing whichever tasks it is executing so that no batches are aborted due to the communication link error? ", "answer": "If there is a need to change this behavior due to situations where a large number of batches might legitimately abort, the threshold can be increased or the feature can be turned off through the following registry keys.\n\n\nx86 (32-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nIndividual processors [default: 1] \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\Rulerunner\\Misc (REG_DWORD) Restart\nprocessor Attempts [default: 3] \n\n \n\nx64 (64-bit) OS: \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart Individual processors [default: 1) \n\nHKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\Rulerunner\\Misc\n(REG_DWORD) Restart processor Attempts [default: 3] \n\n \n\n * Restart Individual processors - 1 is on, 0 is off. \n * Restart processor Attempts - Number of times Rulerunner will move to the next batch without shutting down the threads after a series of batches abort."} +{"id": "TRAIN_Q270", "document": "IBM Known limitation: You cannot add people to a matter request if there are more than 1000 people selected in the clipboard. - United States PRODUCT DOCUMENTATION\n\nABSTRACT\n If you try to add people to a matter request when there are more than 1000 people in the clipboard, the following error will occur:\nAn unexpected error occurred.\nContact your system administrator.\nICWPA1001E \n\nCONTENT\nTo work around the limitation, when you add people from the clipboard, add fewer than 1000 people at one time.", "question": "How to resolve \"An unexpected error occurred. Contact your system administrator. ICWPA1001E\" \n\nWhen trying to add people to a matter request when there are more than 1000 people in the clipboard, the following error is reported:\n\nAn unexpected error occurred. Contact your system administrator. ICWPA1001E\"", "answer": "To work around the limitation, when you add people from the clipboard, add fewer than 1000 people at one time."} +{"id": "TRAIN_Q272", "document": "IBM Changes in the default user identifier between WebSphere MQ V7.0.1 classes for JMS and WebSphere MQ V7.1 classes for JMS - United States TECHNOTE (FAQ)\n\nQUESTION\n You have configured a WebSphere Application Server WebSphere MQ messaging provider connection factory without an Authentication Alias and do not programmatically supply user identifier information when creating a connection to a queue manager. You notice a change in the default behaviour between WebSphere Application Server versions regarding the user identifier flowed on the MQCONN to the target WebSphere MQ Queue Manager:\n\n- When using WebSphere Application Server v7.0 and v8.0, no user identifier value (blank) is passed to the queue manager. \n\n- When using WebSphere Application Server V8.5, a non-blank user identifier value is passed to the queue manager. \n\nIn the latter case, you receive the following exception when creating a connection to a queue manager:\n\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED') \n\nIs this change in behaviour expected? \n\nANSWER\nWebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.\nFrom the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ. This is true even if no user identifier has been specified, or a blank or null user identifier has been specified; for example by calling:\n\nMQConnectionFactory.createConnection();\n\nor:\n\nMQConnectionFactory.createConnection(“”, “”);\n\nor:\n\nMQConnectionFactory.createConnection(null, null);\n\nIn the case where a null or blank user identifier has been specified, the WebSphere MQ V7.1 and later classes for JMS will query the value of the Java System Property user.name. The value of this property is flowed to the queue manager for authorization.\n\nAs a result, if the user identifier specified by the Java System Property user.name is not authorized to access the queue manager, the queue manager will return an exception to the WebSphere MQ classes for JMS with Reason Code MQRC_NOT_AUTHORIZED and the connection to the queue manager will not be established.\n\nThis change in behaviour could affect topologies that previously relied on the default behaviour in the WebSphere MQ V7.0.1 classes for JMS that flowed a blank user identifier when establishing a CLIENT mode transport connection. The expectation that a blank or null user identifier will be flowed by default, and that the user identifier that started the WebSphere MQ server-connection channel would be used by the queue manager when performing the authorization checks, is no longer valid from the WebSphere MQ V7.1 classes for JMS.\n\nIn the case outlined above, system administrators that are currently relying on the default behaviour of the WebSphere MQ V7.0.1 classes for JMS should review their configurations regarding the use of user identifiers and authorization. This might also help to improve security within their WebSphere MQ topology.\n\n\nIn summary, the change in behaviour will affect users of:\n\n- The WebSphere MQ V7.1 and later classes for JMS.\n\n- The WebSphere MQ V7.1 and later JCA Resource Adapter that includes the classes for JMS.\n\n- Versions of WebSphere Application Server that include the WebSphere MQ V7.1 and later JCA Resource Adapter. Currently this is WebSphere Application Server V8.5.0.0 and later.\n\n\nThe com.ibm.mq.jms.ForceUserID Java System Property\n\nA Java System Property called “com.ibm.mq.jms.ForceUserID” was introduced as part of APAR IZ49302 [http://www.ibm.com/support/docview.wss?uid=swg1IZ49302] and included from WebSphere MQ V6.0.2.8 and WebSphere MQ V7.0.1.\n\nThe changes made as part of this APAR could be used to change the default behaviour in the WebSphere MQ V7.0.1 classes for JMS regarding the user identifier value flowed to the queue manager when creating a connection.\n\nThis property is no longer valid from WebSphere MQ V7.1. Setting this property will have no affect on the WebSphere MQ V7.1 classes for JMS and later.\n\nOther Useful Resources\n\nWebSphere MQ Documentation\n\nThe WebSphere MQ Documentation contains a section on planning user authorization which also includes a description on access control for clients. A link to this section in the WebSphere MQ V7.1 Documentation is as follows:\n\nWebSphere MQ > Security > Planning for your security requirements >> Planning authorization [http://pic.dhe.ibm.com/infocenter/wmqv7/v7r1/topic/com.ibm.mq.doc/zs14070_.htm]\n\nTechnotes\n\nA Technote is available that explains J2C Authentication Aliases and how they can be used to configure the user identifier flowed to a queue manager when creating a connection: \n\nEnterprise applications, the WebSphere Application Server WebSphere MQ messaging provider connection factories and Authentication Aliases explained [http://www.ibm.com/support/docview.wss?uid=swg21580097]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server", "question": "Why are we seeing MQRC_NOT_AUTHORIZED errors after upgrading Websphere from V7.0 to V8.5.5? https://www-01.ibm.com/support/docview.wss?uid=swg21662193", "answer": "WebSphere MQ access control is based on user identifiers. There is a deliberate change in the default behaviour between the WebSphere MQ V7.0.1 classes for JMS and the WebSphere MQ V7.1 (and later) classes for JMS regarding the default user identifier flowed to the queue manager.\nFrom the WebSphere MQ V7.1 classes for JMS onwards, a non-blank user identifier is always flowed to the queue manager when creating a connection to WebSphere MQ."} +{"id": "TRAIN_Q274", "document": "IBM Specifying the profile path in the BPMConfig properties file for IBM Business Process Manager (BPM) - United States BPMConfig; profile; path; directory TECHNOTE (FAQ)\n\nQUESTION\n How do you specify the profile path in the configuration properties file for IBM Business Process Manager so you can use it with the BPMConfig command? \n\nANSWER\nNote: The information that is contained in this document has been moved to dW Answers at this location [https://developer.ibm.com/answers/questions/171346/how-do-you-specify-the-profile-path-with-bpmconfig.html]. The new format will allow you to ask questions of the community to better understand the information. This technote will be archived in 60 days. Please bookmark the new location.\n\nYou can use the following property names: \n\n * For a Deployment Manager profile: bpm.dmgr.profilePath \n * For a Custom profile: bpm.de.node.#.profilePath\n\n\nFor example: \nbpm.dmgr.profilePath=/usr/IBM/bpm85/profiles/DmgrProfile \nbpm.de.node.1.profilePath=c:\\\\Program Files\\\\WebSphere\\\\profiles\\\\MyCustomProfile1 \n\nFor Microsoft Windows, you can use double backslashes or forward slashes. For example: \n\nbpm.de.node.1.profilePath=c:/Program Files/WebSphere/profiles/MyCustomProfile1 \n\n \n\nNote: If you are creating the profile makes sure a profilePath value does not exist. The parent directory of the profile path should exist and the user should have write privileges to create a new directory. \n\n\nFor example, if you want to create a profile under the /usr/BPM850profiles/myProfile directory. Create the/usr/BPM850profiles directory, but do not create the /usr/BPM850profiles/myProfile directory.\n\nRELATED INFORMATION\n BPMConfig command: sample configuration properties file [http://www.ibm.com/support/knowledgecenter/SSFTDH_8.5.0/com.ibm.wbpm.imuc.doc/topics/samplecfgprops.html]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Installation / Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5 \nPRODUCT ALIAS/SYNONYM\n BPM", "question": "Error when using profilePath parameter with BPMConfig to create a profile When creating a profile using the BPMConfig command and the -profilePath parameter to define a custom directory to store the profile data, the creation fails with the following error message if the directory already exists (even if it is empty):\ncom.ibm.bpm.config.BPMConfig.main(): The profile path must not exist.....", "answer": "Note: If you are creating the profile makes sure a profilePath value does not exist."} +{"id": "TRAIN_Q276", "document": "IBM JMSListener AutoReconnect properties misconception - United States netcool; impact; netcool/impact; nci; jms; dsa; connectivity; reconnect; auto; autoreconnect; property; properties; listener; jmslistener; misconception; disinformation; misunderstanding; misinterpretation; error; fault; inaccuracy TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n There appears to be a common misconception regarding the application of the JMS DSA Listener properties for AutoReconnect\n\n\n\nSYMPTOM\nAutoReconnect fails\n\n\nCAUSE\nProperties for the JMSListener in the file: \n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props\n\nhave been set as:\n\nimpact.[JMSListenerName].jms.autoreconnect=true\nimpact.[JMSListenerName].jms.autoreconnect.pollinterval=[TimeValue]\n\n\n\n\nRESOLVING THE PROBLEM\nProperties for the JMSListener in the file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props\n\nWhere [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:\n\nimpact.[JMSListenerName].autoreconnect=true\nimpact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]\n\nWhere [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit.", "question": "Netcool/Impact (all versions): JMSListener does not reconnect when JMS server is restarted \n\nJMSListener does not reconnect when JMS server is restarted.\nCreated JMS datamodel to connect to JMS queue. Restart the JBOSS service on JBOSS server on which JMS queue exists Impact attempt to connect to JMS queue fails and it says connection could not be made. However, restart Impact process and click on test connection it gives connection OK message.\n\nHave configured reconnect properties:\n\n impact.MyJMSListener.jms.autoreconnect=true\n impact.MyJMSListener.jms.autoreconnect.pollinterval=20000\n\n", "answer": "Properties for the JMSListener in the file: \n\n\n$NCHOME/impact/etc/[ImpactServerName]_[JMSListenerName].props\n\nWhere [ImpactServerName] is the name of the ImpactServer (for example: NCI) and [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and the properties should be set as:\n\nimpact.[JMSListenerName].autoreconnect=true\nimpact.[JMSListenerName].autoreconnect.pollinterval=[TimeValue]\n\nWhere [JMSListenerName] is the name of the JMSListener Service (for example: MyJMSListener) and [TimeValue] is the desired polling interval value in milliseconds (for example: 30000 (equivalent to 30 seconds)). So, the properties are without the additional .jms bit."} +{"id": "TRAIN_Q277", "document": "IBM No data in some workspaces for MySQL agent - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups. \n\nSYMPTOM\nData does not get collected for the following views that show system and status variable related information: \n\nView name Workspace name Navigator group name Statistics Statistics Availability Operations per second MySQL status data Availability Session status Agent Configuration Configuration Global status Global variables Server String properties Numeric properties Following exception is seen in the JDBC trace logs: \n\n- JdbcConnection.executeFromList-new - java.sql.SQLException: The 'INFORMATION_SCHEMA.GLOBAL_STATUS' feature is disabled; see the documentation for 'show_compatibility_56' \n\nThe above error is seen for MySQL versions 5.7.9 and higher. For MySQL versions prior to 5.7.9, selecting from the INFORMATION_SCHEMA tables produces an empty result set with a deprecation warning. \n\n \n\nNote: MySQL agent is packaged with ITCAM for Applications (IBM Tivoli Monitoring) and Application Performance Monitoring 8.1.x solutions.\n\n\nCAUSE\nFew tables in the INFORMATION_SCHEMA that are used by the agent to collect monitoring data are deprecated in the MySQL server versions 5.7.6 and above. Due to this deprecation these tables cannot be queried normally and cause an error when the agent tries to query these tables to get data.\n\n\nMore details about the MySQL INFORMATION_SCHEMA migration to performance_schema here: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html [https://dev.mysql.com/doc/refman/5.7/en/performance-schema-variable-table-migration.html]\n\n\n\nENVIRONMENT\nMySQL agent installed on MySQL Server versions 5.7.6 and above.\n\n\n\nRESOLVING THE PROBLEM\nUsers wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA. \n\nThis variable can be set from the MySQL command prompt as: \n\nset global show_compatibility_56=ON; \n\n \n\nThe default value of the variable 'show_compatibility_56' for MySQL server versions <=5.7.7 is ‘ON’ and for versions >=5.7.8 is ‘OFF’. \n\n \n\nUser can check the value of this variable by running the following command from the MySQL command prompt: \n\nshow global variables like \"show_compatibility_56\"; \n\n \n\nThis variable can also be set in the MySQL server configuration file also called as Option file. \n\nUser needs to add the following line to the ‘my.cnf’ file (located at ‘/my.cnf’ for Windows and ‘/etc/my.cnf’ for UNIX/Linux): \n\nshow_compatibility_56=ON \n\n \n\nThe paths mentioned above are the default paths for the Option file. For more details on where your installation of MySQL server looks for the 'my.cnf' file, refer the URL: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/option-files.html [https://dev.mysql.com/doc/refman/5.7/en/option-files.html] \n\n \n\nNote: Change in 'my.cnf' file will require a MySQL server re-start for the changes to take effect. \n\n \n\nMore details on the system variable 'show_compatibility_56' here: \n\nhttps://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56 [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_show_compatibility_56]\n\n\n\nPRODUCT ALIAS/SYNONYM\n Monitoring agent for MySQL Sever", "question": "No data in some workspaces for MySQL agent Why Monitoring agent for MySQL when configured to monitor MySQL server versions 5.7.6 and above does not collect data for some of the attribute groups? ", "answer": "Users wanting to run the agent on MySQL server versions 5.7.6 and above should use the 'show_compatibility_56' [https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html] system variable which affects whether MySQL 5.6 compatibility is enabled with respect to how system and status variable information is provided by the INFORMATION_SCHEMA."} +{"id": "TRAIN_Q278", "document": "IBM ITCAM for SOA KD4SDMS database size grows - United States CAMSOAALL CAMSOADB CAMSOAPERF REQMETRICS RESPMETRICS kd4TrimDB2db TECHNOTE (FAQ)\n\nQUESTION\n As the KD4SDMS grows unbounded, is there a way to regularly prune it? \n\nANSWER\nRegarding the older release ITCAM for SOA 7.1.1, there is no a mechanism to automatically regularly prune the KD4SDMS database. The following Wiki page has been published on the topic:\nhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Composite+Application+Manager/page/Pruning+SDMS+Relationship+Metrics+Tables]\n\nTo keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above. \n\nAs for the newer ITCAM for SOA 7.2, there is a cleanup task that runs on the TEPS host where SDMS database is installed. It deletes REQMETRICS and RESPMETRICS table rows where SRTTIME (start of period) is more than 24 hours ago. So these two tables, which are responsible for most of KD4SDMS storage occupation, should not grow unbounded anymore.\n\nNOTE: ITCAM for SOA 7.1.1 is Out-Of-Support since 2015 April 30.", "question": "How to control SDMS database size? ITCAM for SOA 7.1.1 was installed about 3 years ago. I already know that SDMS database size may increase with no limit. Has anyone found a way to keep under control this behavior?", "answer": "To keep only the latest 24 hours every day (regular pruning), you can schedule a daily job to run the kd4TrimDB2db utility provided above."} +{"id": "TRAIN_Q279", "document": "IBM Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed. (CVE-2017-1341 ) - United States SECURITY BULLETIN\n\nSUMMARY\n MQOPEN call might succeed when it should have failed, when using generic profile authority matching for remotely defined MQ object. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]\nDESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8 \n\nMaintenance levels 8.0.0.0 - 8.0.0.7 \n\nIBM MQ Appliance V8 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.7 \n\nIBM MQ V9 \n\nMaintenance levels 9.0.0.0 - 9.0.0.1 \n\nIBM MQ V9 CD \n\nIBM MQ 9.0.1 - 9.0.3 \n\nIBM MQ Appliance V9 CD \n\nIBM MQ Appliance 9.0.1 - 9.0.3\n\nREMEDIATION/FIXES\nIBM MQ V8.0 & IBM MQ Appliance V8.0\nApply fix pack 8.0.0.8 [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]\nApply fix pack 8.0.0.8 for IBM MQ Appliance [http://www-01.ibm.com/support/docview.wss?uid=swg22010861&myns=swgws&mynp=OCSSFKSJ&mync=R&cm_sp=swgws-_-OCSSFKSJ-_-R]\nIBM MQ V9\nApply Fix Pack 9.0.0.2 [http://www-01.ibm.com/support/docview.wss?uid=swg24044038]\nIBM MQ V9 CD\nUpgrade to 9.0.4 [http://www-01.ibm.com/support/docview.wss?uid=swg24043348]\nIBM MQ Appliance V9 CD\nUpgrade to 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 30 Nov 2017: Initial 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.", "question": "Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed (CVE-2017-1341) I need to understand details regarding Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed (CVE-2017-1341). Where can I find this information?\n", "answer": "CVEID: CVE-2017-1341 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1341]\nDESCRIPTION: IBM WebSphere MQ could allow, under special circumstances, an unauthorized user to access an object which they should have been denied access.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/126456 [https://exchange.xforce.ibmcloud.com/vulnerabilities/126456] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N)"} +{"id": "TRAIN_Q280", "document": "IBM Using Oracle JDBC driver specific properties through a datasource - United States TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Properties directly supported by the Oracle JDBC driver that are not part of the JDBC specification cannot be used as a Custom Property in a datasource. \n\nCAUSE\nThe Oracle JDBC driver has added support for a new Custom Property under connectionProperties..\n\nRESOLVING THE PROBLEM\nThe method used with datasources is to set a Custom Property in the datasource as follows: \n\nName: connectionProperties \nValue: propertyA=valueA;propertyB=valueB\n\n\nFor example, if you wish to set the property oracle.jdbc.V8Compatible=true, then you would specify the following. \nName: connectionProperties \nValue: oracle.jdbc.V8Compatible=true\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK", "question": "How to set database specific custom properties in WebSphere Application Server? I am using Websphere Application Server (WAS) v8.5.x with Oracle 11.1 JDBC drivers and I want to set some oracle specific custom properties, when connecting to the database in Websphere Application Server. How to set such specific properties in Websphere Application Server? ", "answer": "The method used with datasources is to set a Custom Property in the datasource as follows: \n\nName: connectionProperties \nValue: propertyA=valueA;propertyB=valueB"} +{"id": "TRAIN_Q283", "document": "IBM Tivoli Netcool/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States release notice; downloads; nco-p-nokia-nfmp; Probe for Nokia Network Functions Manager for Packet NEWS\n\nABSTRACT\n This new probe will be ready for downloading on July 20, 2017. \n\nCONTENT\n \n\nThis probe is written to support Nokia Network Functions Manager for Packet release 17.3.\n\nYou can download the package you require from the IBM Passport Advantage website:\n\nwww-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html [http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html]\n\nNetcool/OMNIbus V8.1\n\nIf you are running Netcool/OMNIbus V8.1, a single package contains versions of the probe for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNL6HEN\n\nThe Netcool/OMNIbus V8.1 version of this probe supports the following Operating Systems:\n\nAIX, Linux, Solaris and Windows.\n\nNetcool/OMNIbus V7.4.0\n\nIf you are running Netcool/OMNIbus V7.4.0, a separate package is supplied for each Operating System. To obtain this new package, use the Find by part number field to search for the part number that corresponds to your Operating System as shown in the table below.\n\nPart number Operating System CNL6DEN AIX CNL6EEN Linux CNL6FEN Solaris CNL6GEN Windows Note: Some versions of some web browsers can introduce random characters into text copied from web pages to the clipboard. In such cases, if you copy and paste part numbers from this release notice into Passport Advantage search fields, the search engine might not return the correct result. If you are encountering problems locating packages in Passport Advantage, remove any characters generated by the copy-paste operation before searching, or manually enter the part numbers into the search field.\n\nIf, for any other reason, you cannot find installation packages in Passport Advantage, contact eCustomer care using the contact information on the following website:\n\nhttps://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html [https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare_emea.html]", "question": "What is the latest Alcatel 5620 SAM probe? We have the nco_p_alcatel_5620_sam_v13 probe, is there a newer version of the probe.\nDoes this probe support Release 14 of the 5620 SAM? ", "answer": "You can download the package you require from the IBM Passport Advantage website:\n\nwww-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/nokia_nfmp/wip/concept/nknfmp_intro.html"} +{"id": "TRAIN_Q285", "document": "IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States TECHNOTE (FAQ)\n\nQUESTION\n Which WebSphere DataPower virtual edition fix pack can I upgrade to and downgrade from? \n\nCAUSE\nNot all scrypt4 fix packs are compatible with the 5.0.0.0 OVA files that were released in November 2012 and March 2013. If you upgrade or downgrade with an incompatible fix pack, unexpected errors might occur.\n\nANSWER\n Use the following links to determine which fix packs are compatible with your virtual deployment.\n\n\n\n\n * 5.0.0.0 from 30 November 2012 (build 220750)\n * 5.0.0.0 from 29 March 2013 (build 227007)\n * 5.0.0.5\n * 5.0.0.6\n * 5.0.0.8 or later\n * 6.0.0.0 or later\n\n\n\n\n\n\n\n\n\n\n\n5.0.0.0 from 30 November 2012 (build 220750) \nWhen your virtual deployment is the OVA file from 30 November 2012, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.0 from 29 March 2013 (build 227007) \nWhen your virtual deployment is the OVA file from 29 March 2013, you can install only the 5.0.0.0 fix pack and 5.0.0.8 or later fix packs from Fix Central. On Fix Central, the 5.0.0.5 and 5.0.0.6 fix packs are for the 5.0.0.0 OVA release from 30 November 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.5 \nWhen your virtual deployment is 5.0.0.5, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.6 \nWhen your virtual deployment is 5.0.0.6, you can install any fix pack from Fix Central, except for the 5.0.0.0 fix pack. On Fix Central, the 5.0.0.0 fix pack is for the 5.0.0.0 OVA release from 29 March 2013. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n5.0.0.8 or later \nWhen your virtual deployment is 5.0.0.8 or later, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2]. \n\nNote: You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit. \n\nBack to top\n\n\n\n\n\n\n\n\n\n\n6.0.0.0 or later \nWhen your virtual deployment is the 6.0.0.0 OVA file or a firmware upgrade through a 6.0.0.0 or later fix pack, do not install any fix pack from Fix Cental that is earlier than the 5.0.0.8 fix pack. The 5.0.0.8 fix pack has critical fixes. For more information, see Critical Updates [http://www-01.ibm.com/support/docview.wss?uid=swg21390112#part2]. \n\nBack to top\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Service Gateway XG45 Virtual Edition VMware ESXi, VMware ESX 5.0.0, 6.0.0 Edition Independent", "question": "How do I upgrade my virtual DataPower Appliance from 5.0 firmware to 6.0+ firmware? When attempting to upgrade my Virtual DataPower Appliance from 5.0.0.0 firmware version to 6.0+ firmware versions, I receive a failure message. ", "answer": "You must install the 5.0.0.8 or later fix pack to upgrade to 6.0.0.0 or later. The 5.0.0.8 fix pack contains a required fix to allow the larger sized firmware image to fit."} +{"id": "TRAIN_Q286", "document": "IBM Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit - United States WTX ITX Launcher On Success Delete On Failure Commit TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Transformation Extender (ITX) Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit. \n\nSYMPTOM\nLauncher fails to load a watch when On Success = Delete and On Failure = Commit are used. \n\n\nCAUSE\nThis has been identified as a product defect under APAR PI64816\n\nENVIRONMENT\nUsing the IBM Transformation Extender (ITX) Launcher and 'On Success' is set to Delete and 'On Failure' is set to Commit.\n\nDIAGNOSING THE PROBLEM\n The Compound system log reports the following Launcher FATAL error :\n\nFile Trigger FATAL Error : ValidateEKDirectories: Cannot find correct card index for watch #.\n\n\n\nRESOLVING THE PROBLEM\nObtain patch for APAR PI64816.", "question": "Port number error starting 9.0 Launcher \n\nI'm attempting to start up v9.0 for the first time with one .msl file on a Windows server and get the following error. I also have v8.4 on this server and it starts fine. I do not have v8.4 running when I attempt to start v9.0.\n\nCannot recognize if the system RecordChangeSystem.msl; has started. Reason: Server is unable to get the status of the system on port number 6,002.\n\nI have the port range set to 7000/8000. I've never seen this error before.\n\nAny help? Thanks.", "answer": "Obtain patch for APAR PI64816."} +{"id": "TRAIN_Q287", "document": "IBM Datacap 9.0.1 FP1 - Readme doc - United States PRODUCT README\n\nABSTRACT\n IBM Datacap 9.0.1 FP1 - Readme doc \n\nCONTENT\nAbout IBM Datacap 9.0.1 Feature Pack 1 \n\nReview this document for installation instructions and other important information before you install IBM® Datacap 9.0.1 Feature Pack 1, which cumulatively contains all feature pack updates since IBM Datacap Version 9.0.1 was released. \n\n \n\nUpgrading to IBM Datacap 9.0.1 Feature Pack 1\n\n\nFrom v9.0.1: use the Patch Installer from Fix Central \n\nInstallation Steps \n\nPrerequisite: \n\n· 1) Microsoft .NET Framework 4.6.1 \n\n· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n· Run: vcredist_x86.exe \n\n \n\nInstall: \n\n· 3) IBM Datacap 9.0.1.1 \n\n· Run: Update.exe\n\n\nFrom v9.0.0.0, 9.0.0.1, 9.0.0.2 & 9.0.0.3: use the Full Installer from Passport Advantage \n\nInstallation Steps \n\nPrerequisite: \n\n· 1) Microsoft .NET Framework 4.6.1 \n\n· Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n· 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n· Run: vcredist_x86.exe \n\n \n\nInstall: \n\n· 3) IBM Datacap 9.0.1.1 \n\n· Run: Setup.exe \n\n \n\nImportant \n\nUpdates are required only on Servers and thick client computers. No update is required for \"thin client\" computers. You must upgrade all thick clients and servers to the same IBM Datacap version and feature pack. Different versions of IBM Datacap are not compatible; therefore, you cannot connect an IBM Datacap client with a server that has a different IBM Datacap server version or feature pack installed. Operating Datacap Client or Datacap Web with an incompatible version of Datacap Server, or allowing different versions to access one database, can result in loss of data. \n\nOnce installed, this feature pack cannot be uninstalled. However, you can use \"Uninstall or change a program\" in Control Panel to uninstall the entire Datacap product. \n\nThe language you selected when installing Datacap 9.0.1 determined the language displayed in the InstallShield panels at that time, and also controls the language in which the InstallShield panels for this feature pack are displayed. \n\n \n\nAlerts! \n\n1) When running an update, the global ruleset DLLs are updated but the copies in each application are not updated. \n\nAs a result, new features and fixes are not applied to applications and customers might experience defects that have been fixed. \n\nThe global ruleset DLLs are in the Datacap\\RRS folder. The application copies are in the application DCO rules folder. \n\nCustomers must manually update the ruleset DLLs in each application where they are installed. \n\n2) When running an update, the master task configuration files are updated (Datacap\\ProgramSet) but the setting in applications are not updated (in application DCO folder). \n\nAs a result, new features and fixes are not applied to applications and customers might experience problems that have been fixed. \n\nThe master task configuration is located in Datacap\\ProgramSet. The application settings are in the application DCO folder. \n\nCustomers must manually update the task setting in each application where they are installed. \n\n\nSystem requirements \n\nSelect the following link to see the hardware and software requirements for IBM Datacap. \n\nhttp://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html [http://www.ibm.com/software/reports/compatibility/clarity/softwareReqsForProduct.html] \n\n\nSearch for ‘Datacap’, then select \"Datacap \" \n\nCheck the box ‘Show feature packs’ and select 9.0.1 for Feature Pack 1*. \n\nNew features added to IBM Datacap 9.0.1 Feature Pack 1 \n\nFor a list of new features that were added to Datacap 9.0.1 in Feature Pack 1, see:\nHighlights of IBM Datacap 9.0.1 Feature Pack 1 [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm].\n\nhttp://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm [http://www.ibm.com/support/knowledgecenter/SSZRWV_9.0.1/com.ibm.datacaptoc.doc/dc_highlights_9011.htm]\n\n\nNew Qualifications \n\n \n\nIBM Datacap 9.0.1 Feature Pack 1 is qualified for use with: \n\n \n\n· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers; \n\nSee “Known Limitations” below for details) \n\n \n\n· Oracle 12c (12.1.0.2.0) \n\n \n\n· IBM Content Navigator 2.0.3 FP7 \n\n \n\nIssues fixed in IBM Datacap 9.0.1 Feature Pack 1 \n\n \n\nAPAR Number Summary IO23893 Clicking on QA link in tmweb - Administrator fails with error \"column named name already belongs to this datatable\" if using admin database on SQL server IO24025 Can not import file which name contains '0x905C' such as \"保険申告Updated.tif\" IO24067 When customer use https + non-activeX to upload, some images will be corrupted frequently IO24082 Lineitem does not show up in Datacap Desktop Verify panel IO24102 Enhance IMail actions to use standard naming convention for ID's of pages created. IO24104 Using LLLDAP certain users are not able to login even when they are in the same group. LDAP is across multiple domains. IO24138 Couldn't create DC_P8 FileNet object error; action FNP8_SetURL () on 9.0 FP 3 and 9.0.1 IO24140 aindex.aspx does not update DATAFILE variable when a page is moved in batch view IO24141 DCDesktop Exception when performing a lookup query against an Oracle database IO24144 Batch aborts during ExcelWorkbookToImage with specific XLSX file IO24168 Page data is not generated when the page type is changed through batch structure in verify client of Datacap Navigator IO24169 when task has \"-\" and then change the batch status from hold to pending in edit job dialog, it will fail. IO24181 Unable to edit and enter values in multiple line edit box in tmweb Verifine panel IO24185 OCR_SR.RotateImageOCR_S () no longer compresses the TIFF image since applying 9.0 FP#2 was deployed IO24186 Thumbnail view of images is not activated in DcDesktop app until an image in batch tree view is clicked on IO24196 Setting a value to a custom column by main profile rule does not work. IO24199 Verify shortcut fails to show the batch list when the job name contains '( )' IO24205 System.OutOfMemory error returned by Datacap.Libraries.Convert.Outlook->OutlookMessageToImageAndAttachment () IO24213 Start bach panel non-overrideable validation not handled gracefully the second time around; Dc Desktop crashes IO24215 FNP8_CreateFolder () does not support / handle error in Italian IO24226 Page data failed to be shown in field details panel after running validation with some empty C nodes IO24227 CCO was not reloaded after running the rule so the re-OCR rule cannot take effect until relaunching the batch. IO24232 Main_Page no longer synch's up with custom data panel after switching from main_page to trailing page to main_page IO24249 Imprint.RedactParameters () converting color images to bitonal IO24249 Imprint.RedactByRegEx () only runs at Field level not at Page level but action help is slightly misleading IO24259 DcDesktop - certain columns in Job Monitor ONLY sort by Queue ID column IO24260 DSTUDIO: selecting ruleset \"import files - all : Scan\", returns message \"The Document Hierarchy refers to some nonexistent Rules.\". IO24282 MatchBarcodeBP throws an error in the rrs.log when processing non-barcode type pages. IO24289 tmweb fails to create setup file for a task if the app name begins with \"AP\" IO24381 SetNamePattern () with Convert.Unzip () is unable to resolve the naming pattern of the extracted image IO24384 Format and formatDescription are not supported in EDS IO24386 when the auto launch next batch is enabled, the page of the next verify page is not loaded. IO24387 Rescan status cannot be persisted after submitting if it is the only page in the batch IO24388 Split should not enabled on the page which is the only one in its parent document. IO24418 Images id are not numbered sequentially after fault with scanner occurs IO24427 Clicking on \"Build Doc\" button on custom panel generates exception error in DcDesktop App IO24439 Convert.ExcelWorkbookToImage () distorts the extracted tiff preventing GetBarcodeBP () from reading the barcode from the tiff image IO24447 rescanned page lost \"ScanSrcPath\" variable IO24461 Cannot paste value to a field if disable readonly on batch tree IO24470 After a job which jumped several tasks is edited via 'Edit Job' button, it could not be shown in Job Monitor IO24473 Batch is still in hold status even submitting it if session ever timeout. IO24475 Some Datacap css styles override ICN original ones, so impact ICN and other plugins. IO24477 image viewer error message does not conforming within image viewer. IO24486 Daeja ViewOne functionality of virtual as compared to Professional with DataCap \nKnown limitations in IBM Datacap 9.0.1 Feature Pack 1 \n\nRead this information to learn about known limitations in IBM Datacap 9.0.1 Feature Pack 1. \n\n \n\n \n\nComponent Summary TMWeb Scan Windows 10 supported with IBM Datacap 9.0.1 FP1 with the following known limitations:\n\n1. TMweb's \"IE Test\" page may result in a dialog box titled “Accusoft Twain Pro7 common 9.0.013” with the message \"picdll Load Library failed.”\n2. When trying to perform a Web scan with a Physical Scanner connected (via twain drivers) , ie using Web Vscan configured with scancl.aspx, the message \"picdll Load Library failed\" may be displayed. \n\nIf any of these messages appear, TMWeb scanning will not be possible. Medical Claims When in MClaims Prof Red/Black FixupScan, clicking \"Next LC\" button will advance to the next page and display the data for it (Type and Status), but will keep the previous page selected as well, and changes to Status (from \"Invalid Claim Type\" to \"New Claim\") will not be saved.\n\nSuggested workaround: \nAfter clicking \"Next LC\" button, which will show previous page and current page selected in the Batch View display, then click the current page node in the Batch View display to properly select only the current page. After this one can continue to change the page Status and click \"Next LC\" button and repeat workaround for the next page. [/support/docview.wss?uid=swg27047895&aid=1] [/support/docview.wss?uid=swg27047895&aid=1]", "question": "Will Datacap support Windows 10, if so, which version is fully supported? \n\nWe want to if Datacap support windows 10, if so, which version supports it.\n\nPlease provide us official statement for the compatibility.", "answer": "IBM Datacap 9.0.1 Feature Pack 1 is qualified for use with: \n\n \n\n· Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;"} +{"id": "TRAIN_Q288", "document": "IBM Configuring file content extraction tools for IBM Connections Search - United States stellent file content conversion extraction TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nIBM Connections uses the Stellent (Oracle Outside In Technology) Export utility to extract text from documents of various types. The extracted text is added to the Search index allowing users to find documents based on the content. \n\nWhen the Stellent utility is not configured correctly, file content will not be extracted or indexed. Therefore, search results within IBM Connections will not contain any matches on file content. For any content extraction issues, follow the steps in this tech note. \n\n\nRESOLVING THE PROBLEM\n 1 Stellent installation \n\nEnsure that the following IBM Connections post-installation task has been carried out:\nhttp://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40 [http://www-10.lotus.com/ldd/lcwiki.nsf/dx/Copying_Search_conversion_tools_to_local_nodes_ic40]\n\n\n 2 Running the exporter in isolation from IBM Connections \n\nTo verify that the exporter is working correctly, you can run it on the command line in isolation from IBM Connections. To run the exporter executable on the command line, execute the following as the user that the Search WebSphere Application Server is running under: \n\n1. Change directory to the Stellent binary location. For example: \n\n $ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport\n\n2. Run the exporter command.\nThe exporter command has the following syntax: \n\n exporter inputpath=\noutputpath=\noutputid=FI_SEARCHTEXT\n\nFor example,\n$ ./exporter inputpath=/root/translation.pdf \\ outputpath=/root/testStellent.txt outputid=FI_SEARCHTEXT\n\nIf the text extraction worked successfully, you will see the following output: \n\nExport complete\n\nHowever, if you see a message like the one below, continue to step 3:\n\n./exporter: error while loading shared libraries: libsc_ex.so: cannot open shared object file: No such file or directory \n\n\n 3 Operating System Environment Variables \n\nEnsure that the operating system environment variables LD_LIBRARY_PATH and PATH are set correctly in Section 1. Both variables should contain the Stellent installation directory. To get the current values of the environment variables, run the following commands as the user that the Search WebSphere Application Server is running under:\n\n$ echo $LD_LIBRARY_PATH\n$ echo $PATH\n\nTo verify that the Stellent exporter executable can be found through the PATH environment variable, run the following command:\n\n$ which exporter\n\nThe output of this command should contain the full path to the exporter executable. For example:\n\n/opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter\n\n\n 4 WebSphere Environment \n\nUsing the WebSphere Application Server administration console, ensure that the WebSphere environment variable FILE_CONTENT_CONVERSION points to the exporter executable. \n\nFor example: /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport/exporter\n\n\n 5 File Permissions \n\nEnsure that the user that the Search WebSphere Application Server is running under has sufficient privileges. They should have read/write/execute permissions on the exporter executable and read/write permissions on the other files in the Stellent installation directory.\n\n\n 6 Library compatibility \n\nVerify that the libraries deployed with Stellent are compatible with your platform.\n\nFor example, on a 64 bit Linux system:\n$ uname -a\nLinux host1 2.6.18-308.11.1.el5 #1 SMP Fri Jun 15 15:41:53 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux\n\n$ cd /opt/IBM/Connections/data/local/search/stellent/dcs/oiexport\n$ file libsc_ex.so\nlibsc_ex.so: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped\n\n(Note that your Stellent installation may contain 32 bit libraries though you are running on 64 bit platform. This is not an issue, provided that the 32 bit compatible libraries are on the LD_LIBRARY_PATH or can be found on the shared library search path).\n\n\n 7 Shared library dependencies \n\nThe Stellent exporter executable has a number of dependencies on both the shared libraries packaged with Stellent and on shared libraries installed on your system. To verify that all the required shared libraries can be found, use the 'ldd' command on the exporter executable as follows:\n\n$ ldd -v exporter\n\nCheck the output of this command for any shared libraries marked as '=> not found'. \n\n Stellent shared library not found \n\nIf a Stellent shared library can't be found, then check that the setting of your LD_LIBRARY_PATH operating system environment variable contains the Stellent installation directory. \n\n System shared library not found \n\nIf a system shared library can't be found, then you are missing a prerequisite library.\nNOTE: It is still possible to pick up libraries from locations other than those included in the LD_LIBRARY_PATH operating system environment variable, as long as they can be found elsewhere on the system's default search path. \n\nIn addition to libc.so.6, Stellent is dependent upon the following libraries: \nlibstdc++.so.5\nlibgcc_s.so.1 \n\nFor Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5.\n\n\n\n\n * \n *", "question": "DCS Document Conversion issue: java.util.MissingResourceException: Can't find resource for bundle com.stellent.scd.ExportResources, key 127 DCS Document Conversion issue: java.util.MissingResourceException: Can't find resource for bundle com.stellent.scd.ExportResources, key 127 ", "answer": "In addition to libc.so.6, Stellent is dependent upon the following libraries: \nlibstdc++.so.5\nlibgcc_s.so.1 \n\nFor Red Hat Enterprise Linux 6.0 and later, it is possible that you are missing the package compat-libstdc++-33 . This package contains libstdc++.so.5."} +{"id": "TRAIN_Q291", "document": "IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States IIB WMB FLASH (ALERT)\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\nCVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139 \n\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\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0", "question": "Help with IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux I need to understand details regarding Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux. Where can I find this information? ", "answer": "IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to\nCVE-2017-12691 CVE-2017-12692 CVE-2017-12693 CVE-2017-12875 CVE-2017-12876 CVE-2017-12877 CVE-2017-13131 CVE-2017-13132 CVE-2017-13133 CVE-2017-13134 CVE-2017-13139 CVE-2017-13140 CVE-2017-13141 CVE-2017-13142 CVE-2017-13143 CVE-2017-13144 CVE-2017-13145 CVE-2017-13146 CVE-2017-13658 CVE-2017-13758 CVE-2017-13768 CVE-2017-13769 CVE-2017-14060 CVE-2017-14137 CVE-2017-14138 and CVE-2017-14139 \n\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"} +{"id": "TRAIN_Q294", "document": "IBM Software maintenance strategy for CICS TS and its embedded components - United States Libery Java ; 5655S9700 R660 660 R600 600 HCI6600 R670 670 R700 700 HCI6700 5655-S97 5655S97 ; 5655Y0400 R680 680 R800 800 HCI6800 R690 690 R900 900 HCI6900 R700 700 R000 000 HCI7000 R710 710 R100 100 HCI7100 5655Y0401 5655-Y04 5655Y04 KIXINFO PRODUCT DOCUMENTATION\n\nABSTRACT\n CICS TS support is delivering the information in this document to help customers plan for updates to CICS Transaction Server for z/OS (CICS TS) and related software components such as WebSphere Liberty and CICS Explorer. Installing APAR fixes (PTFs) using Recommended Service Upgrades (RSUs) as early as possible can help avoid problems that could result in a service call, and as long as you test appropriately, help reduce risks to your business. \n\nCONTENT\n\n\n\n[/support/docview.wss?uid=swg27048530&aid=1]Embedded components in CICS TS [http://www-01.ibm.com/support/docview.wss?uid=swg27012749#delivering]\n[/support/docview.wss?uid=swg27048530&aid=2]Update recommendations\n[/support/docview.wss?uid=swg27048530&aid=3]Related information \n\n\n\n\n\n\n\n\n\nComponents in CICS TS\n\nCICS TS provides the following embedded runtime components: \n\n * Equinox\n Equinox is an implementation of the OSGi core framework specification and is provided for both OSGi JVM servers and for Liberty JVM servers. Service for these components is provided when and if required.\n \n \n * Apache Axis2™ \n Axis2 is an open source web services engine from the Apache Software Foundation and is used within CICS to provide the web service Java™ engine for the Axis2 JVM server environment. Service for this component is provided when and if required.\n \n \n * WebSphere Application Server Liberty Profile\n Liberty fix packs are provided on a regular basis through the CICS TS APAR delivery process and provide an update mechanism to keep the embedded CICS Liberty runtime synchronized with the fix packs provided by WebSphere Application Server. Keeping current helps you resolve problems faster for 2 reasons: * Liberty APAR fixes (known as ifixes) can only be delivered on the latest Liberty fix pack that has been supplied by the CICS APAR process. \n * CICS APAR fixes can require other fixes such as WebSphere Liberty fix packs.\n \n \n \n\nCICS Explorer and z/OS Explorer\nThe CICS Software Development Kit (SDK) for Java includes components from CICS for developing CICS Java applications. The CICS SDK for Servlet and JSP support includes Java Enterprise Edition (Java EE) and Liberty API libraries, and automatically installs required components such as WebSphere Developer Toolkit (WDT).\" Service for these components is provided through the CICS Explorer fix pack process when and if required. \n[/support/docview.wss?uid=swg27048530&aid=4] Back to Top \n\n\nUpdate recommendations\n\nRecommended Service Upgrade (RSU) \nIBM recommends that you install all RSU [http://www-03.ibm.com/systems/z/os/zos/support/servicetest/] PTFs as preventive software maintenance for CICS TS. An RSU is a predefined collection of PTFs identified with a SOURCEID of RSUyymm, where yy indicates the last 2 digits of the year and mm indicates the month. [http://www-03.ibm.com/servers/eserver/zseries/zos/servicetst/]You can order an RSU [http://www-1.ibm.com/servers/eserver/zseries/zos/servicetst/]from ShopzSeries [https://www14.software.ibm.com/webapp/ShopzSeries/ShopzSeries.jsp].\n\n\nEquinox and Apache Axis2\nThere is unlikely to be much maintenance for Equinox and Axis2. Service for these components is provided when and if required, meaning it will be on a case by case basis and in most cases this will be to resolve service requests.\n\n\nWebSphere Application Server Liberty Profile\nRefer to Updating Liberty profile for CICS TS and z/OS Connect EE to latest version [http://www.ibm.com/support/docview.wss?uid=swg21993579] for a list of APARs you will need to update CICS TS and z/OS Connect Enterprise Edition (EE) to the latest version of WebSphere Application Server Liberty profile. \n\n\nCICS Explorer\nIBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4. For further details see Latest version of CICS Explorer and CICS Tools plug-ins for CICS Explorer [http://www.ibm.com/support/docview.wss?uid=swg21404312]. \n\n\n\n[/support/docview.wss?uid=swg27048530&aid=5] Back to Top \n\n\n\nRelated information: \n * Update Strategy for WebSphere Application Server [http://www.ibm.com/support/docview.wss?uid=swg27036014] \n \n * Fix list for IBM WebSphere Application Server Liberty [http://www.ibm.com/support/docview.wss?uid=swg27043863]\n \n * CICS TS embedded components [http://www.ibm.com/support/knowledgecenter/SSGMCP_5.3.0/com.ibm.cics.ts.standards.doc/topics/supportedComponents.html]\n \n * Fixes by version for CICS products [http://www.ibm.com/support/docview.wss?uid=swg27008833]\n\n\n[/support/docview.wss?uid=swg27048530&aid=6] Back to Top \n\n\nPRODUCT ALIAS/SYNONYM\n CICS/TS CICS TS CICS Transaction Server", "question": "IZE0106E Connect failed with \"Unsupported CICS release\" after upgrading CICS TS V5.x Do I have to upgrade my CICS Explorer to the same release as CICS Transaction Server for z/OS (CICS TS)? I recently upgraded to a new release of CICS TS and now when I attempt to connect to CICS Explorer using a CMCI connection, I get message \nIZE0106E Connect failed with \"Unsupported CICS release\" after upgrading \nin CICS Explorer. ", "answer": "IBM recommends that you upgrade to the latest release of CICS Explorer to obtain the most recent functionality and service. Old releases of CICS Explorer are not generally updated with new function, but new CICS Explorer releases are compatible with all earlier versions of CICS TS. Therefore, CICS Explorer V5.4 is compatible with CICS TS V4.1 through V5.4."} +{"id": "TRAIN_Q295", "document": "IBM How to determine if a TIP server is part of a HA cluster - United States TIPL2; TIPL2CONF; TIPL2HALB; Load balancing; high availability; Tivoli Integrated Portal; HA; TIP; HATool; modules; database TECHNOTE (FAQ)\n\nQUESTION\n What steps can be used to determine if a Tivoli Integrated Portal server is part of a High Availability server group? \n\nANSWER\nUse the HATool.{bat|sh} command located in the /profiles/TIPProfile/bin/ha directory. The usage for that command is:\nHATool.{bat|sh} modules \n\nIf this returns a list of modules, then HA is configured and the server is joined.\nIf this returns empty, then HA is configured, but server is disjoined.\nIf this throws Database Connection errors, then HA has never been configured on this server.\n\nSee the following technical note for complete details on High Availability/load balancing configuration:\n\nhttp://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tip.doc/ctip_config_ha_ovw.html [http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.tip.doc/ctip_config_ha_ovw.html]", "question": "Why are ITNM or Omnnibus WebGUI java applets fail to load with \"Missing Permissions manifest attribute in main jar\" Why are ITNM or Omnnibus WebGUI java applets fail to load with \"Missing Permissions manifest attribute in main jar\"", "answer": "Use the HATool.{bat|sh} command located in the /profiles/TIPProfile/bin/ha directory. The usage for that command is:\nHATool.{bat|sh} modules \n\nIf this returns a list of modules, then HA is configured and the server is joined.\nIf this returns empty, then HA is configured, but server is disjoined.\nIf this throws Database Connection errors, then HA has never been configured on this server."} +{"id": "TRAIN_Q296", "document": "IBM Steps to disable RC4 SSL ciphers in Tivoli Integrated Portal - United States TIPL2SSL; TIPL2; TIPL2CONF; RC4; cipher; SSL TECHNOTE (FAQ)\n\nQUESTION\n What are the steps to disable RC4 ciphers from TIP? \n\nCAUSE\nSecurity scans may suggest disabling RC4 ciphers\n\nANSWER\nTo remove RC4 ciphers:\n\n\n 1. Log into the Websphere Application server and navigate to:\n SSL certificate and key management > SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP)\n \n \n 2. Select the *RC4* ciphers from the \"Selected ciphers\" list, and then click the \"< SSL configurations > NodeDefaultSSLSettings > Quality of protection (QoP)\n \n \n 2. Select the *RC4* ciphers from the \"Selected ciphers\" list, and then click the \"<