[{"id":"TRAIN_Q000","question":"User environment variables no longer getting picked up after upgrade to 4.1.1.1 or 4.1.1.2?\n\n\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 =","is_impossible":false,"contexts":[{"filename":"swg21996508.txt","text":"Title: IBM STREAMS 4.1.1.1 and 4.1.1.2 JOBS DO NOT INHERIT THE ENVIRONMENT VARIABLES SET IN .BASHRC, WHEN STREAMS IS RUN AS A SYSTEM SERVICE - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n In Streams 4.1.1.1 and 4.1.1.2 Streams jobs may not pick up the user enviroment from the streams user's .bashrc. This behavior is different from earlier releases. With these versions, when Streams is run as a system service, application environment variables must be set with streamtool. \n\nCONTENT\nProblem Description\nWhen running Streams as a system service with Streams releases 4.1.1.1\nor 4.1.1.2, toolkits and user applications that depend on the\nuser environment may have various errors.\nFor example the database toolkit might show the following error\nif it does not pick up the ODBCINI environment variable:\n\n\n\n * \"An SQL operation failed. The SQL state is 08003, the SQL code\n is 0 and the SQL message is [unixODBC][Driver\n Manager]Connnection does not exist.\"\n * \n\nProblem Solution \n\nTo work around the issue, set environment variables that are needed by the application directly in the instance with: * \n \n * streamtool setproperty\n * -d -i \n --application-ev =\n * \n \n\n\nRELATED INFORMATION\n APAR IT18432 [https:\/\/www-01.ibm.com\/support\/entdocview.wss?uid=swg1IT18432]"}]},{"id":"TRAIN_Q001","question":"Netcool\/Impact (all versions): How is the Exit() action function expected to work with User Defined Functions?\n\nNetcool\/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","is_impossible":false,"contexts":[{"filename":"swg21675316.txt","text":"Title: IBM Exit() action within User Defined Function in Impact Policy Language - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; ipl; policy; language; exit; exit(); function; user; defined; custom; udf; parser; action; set; global; variable; var; get; setglobalvar; getglobalvar; globalvar TECHNOTE (FAQ)\n\nQUESTION\n and how to exit the Policy process from within a Custom Function \n\nCAUSE\nUsing the Exit() parser function within a User Defined (or Custom) Function in Impact Policy Language (IPL) will not exit the Policy process, it will only exit the User Defined Function.\n\nANSWER\nThis is because the Exit() parser function in IPL is designed to exit the immediate scope. To carry the action outside of the User Defined Function to the Policy level one would have to set a variable that is then tested immediately after the User Defined Function call - for example: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * SetGlobalVar(\"ExitNow\", 1);\n * \n * Exit();\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * If(GetGlobalVar(\"ExitNow\") == 1)\n * \n * {\n Log(ID+WP+\": Existing policy...\");\n \n * Exit\n * ();\n }\n\n\nThe above example ties in somewhat with the exampled configuration from the TechNote \"Event Flagging with Go_NoGo checking\" [ link below] and uses structured logging as covered in the TechNote \"Structured logging in Policies\" [ link below]. \n\nIf the User Defined Function was nested within another User Defined Function one would have to exit each layer to return the Policy layer before the Exit() action would exit the Policy. \nRELATED INFORMATION\n Event Flagging with Go_NoGo checking [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21675015]\nStructured Logging in Policies [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21596180]"}]},{"id":"TRAIN_Q002","question":"Why are replies going to the DLQ with reason 2189 MQRC_CLUSTER_RESOLUTION_ERROR\n\nI have changed my cluster receiver to match the IP address used and now I am seeing replies in my DLQ with 2189 MQRC_CLUSTER_RESOLUTION_ERROR. The reply queue is on a different cluster which this qmgr is a member of. The reply message uses replytoqmgr and queue name. The qmgr should see the replytoqmgr in the cluster and get the message over to the queue, but instead goes to dead letter queue. This queue manager is a repository to one cluster and a member of another. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q003","question":"How to configure SSL mutual authentication in IBM HTTP Server?\n\n\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\u00ae Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server","is_impossible":false,"contexts":[{"filename":"swg21179559.txt","text":"Title: IBM Guide to properly setting up SSL within the IBM HTTP Server - United States\n\nText:\nssl; handshake; secure socket layer; handshake failed; enable; ssl config; ssl setup; setup; IHS; crl; revocation; ssl; ssl; ssl; configure; config; config; config TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The following information can be used as a guide for setting up the Secure Sockets Layer (SSL) within the IBM HTTP Server. This document covers information on setting up SSL virtualhosts, creating keyfiles, certificates along with how to protect access to directories and URLs to specific ciphers. Also, included is documentation on how to trace and record SSL traffic between a client browser and the Web server. \n\nRESOLVING THE PROBLEM\nThe following steps help guide you through the proper set up of SSL within the IBM HTTP Server: \n\n 1. Confirm that the Global Security Kit (GSKit) is installed and meets the minimum requirements\n \n \n 2. Create a key database file and certificates needed to authenticate the Web server during an SSL handshake\n \n \n 3. Enable SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf)\n \n \n 5. Information that IBM WebSphere\u00ae 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\u00ae Windows\u00ae:\n \n \n LoadModule ibm_ssl_module modules\/mod_ibm_ssl.so [\/support\/docview.wss?uid=swg21179559&aid=1]\n \n \n * For UNIX\u00ae 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 <\/Directory>\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 <\/VirtualHost>\n \n SSLDisable\n KeyFile \"c:\/program files\/ibm http server\/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 [\/support\/docview.wss?uid=swg21179559&aid=3]\n \n If you are enabling one Web site for SSL and the ServerName is different than the ServerName already defined in the Global Scope for non-SSL (port 80), you can enable SSL as follows. Both hostnames must be registered in DNS to a separate IP address, and both IP addresses must be configured on local network interface cards.\n \n http:\/\/www.mycompany.com (non-SSL) 192.168.1.102 http:\/\/www.mycompany2.com (non-SSL) 192.168.1.103 https:\/\/www.mycompany2.com (SSL) 192.168.1.103\n \n Example 2:\n \n Listen 80\n ServerName www.mycompany.com\n \n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n <\/Directory>\n \n DocumentRoot \"c:\/program files\/ibm http server\/htdocs\"\n DirectoryIndex index.html\n \n \n ServerName www.mycompany2.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs2\"\n DirectoryIndex index2.html\n <\/VirtualHost>\n \n Listen 443\n \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 <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs2\"\n DirectoryIndex index2.html\n <\/VirtualHost>\n \n SSLDisable\n KeyFile \"c:\/program files\/ibm http server\/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n If you are enabling multiple Web sites for SSL, you can enable SSL as follows. All hostnames must be registered in DNS to a separate IP address. Also, all the IP addresses must be configured on a local network interface card. You must use the SSLServerCert directive to identify which personal server certificate in the key database file is passed to the client browser during the SSL handshake for each Web site. If the SSLServerCert directive is not defined, the IBM HTTP Server passes whatever certificate in the key database file is marked(*) as the \"default key\".\n \n For more information on why different IP addresses are required when enabling multiple Web sites for SSL: IP-Based Virtual Hosting must be used if configuring multiple SSL Virtual Host [http:\/\/www.ibm.com\/support\/docview.wss?rs=177&context=SSEQTJ&uid=swg21045922]http:\/\/www.mycompany.com (non-SSL) 192.168.1.102 https:\/\/www.mycompany.com (non-SSL) 192.168.1.102 http:\/\/www.mycompany2.com (non-SSL) 192.168.1.103 https:\/\/www.mycompany2.com (SSL) 192.168.1.103 http:\/\/www.mycompany3.com (non-SSL) 192.168.1.104 https:\/\/www.mycompany3.com (SSL) 192.168.1.104\n \n Example 3:\n \n Listen 80\n ServerName www.mycompany.com\n \n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n <\/Directory>\n \n DocumentRoot \"c:\/program files\/ibm http server\/htdocs\"\n DirectoryIndex index.html\n \n \n ServerName www.mycompany2.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs2\"\n DirectoryIndex index2.html\n <\/VirtualHost>\n \n \n ServerName www.mycompany3.com\n \n Options Indexes\n AllowOverride None\n order allow,deny\n allow from all\n <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs3\"\n DirectoryIndex index3.html\n <\/VirtualHost>\n \n Listen 443\n \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 <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs\"\n DirectoryIndex index.html\n <\/VirtualHost>\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 <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs2\"\n DirectoryIndex index2.html\n <\/VirtualHost>\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 <\/Directory>\n DocumentRoot \"c:\/program files\/ibm http server\/htdocs3\"\n DirectoryIndex index3.html\n <\/VirtualHost>\n \n SSLDisable\n KeyFile \"c:\/program files\/ibm http server\/key.kdb\"\n SSLV2Timeout 100\n SSLV3Timeout 1000 \n \n \n \n \n 4. Other considerations when enabling SSL directives within the IBM HTTP Server configuration file (httpd.conf).\n \n * How to rewrite HTTP (port 80) requests to HTTPS (port 443)\n The rewrite module (mod_rewrite.c) provided with the IBM HTTP Server can be used as an effective way to automatically rewrite all HTTP requests to HTTPS. For complete information click How to rewrite HTTP (port 80) requests to HTTPS (port 443) [http:\/\/www.ibm.com\/support\/docview.wss?rs=177&context=SSEQTJ&uid=swg21114864].\n \n \n * Logging SSL request information in the access log for IBM HTTP Server\n The IBM HTTP Server implementation provides Secure Sockets Layer (SSL) environment variables that are configurable with the LogFormat directive in httpd.conf. For complete information click Logging SSL request information in the access log for IBM HTTP Server [http:\/\/www.ibm.com\/support\/docview.wss?rs=177&context=SSEQTJ&uid=swg21176455].\n \n \n * Enabling Certificate Revocation Lists (CRL) in the IBM HTTP Server\n Certificate revocation provides the ability to revoke a client certificate given to the IBM HTTP Server by the browser when the key is compromised or when access permission to the key is revoked. CRL represents a database that contains a list of certificates revoked before their scheduled expiration date. For complete information: * For releases of IBM HTTP Server v7.0 [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html] \n * For releases of IBM HTTP Server v8.5 [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSD28V_8.5.5\/com.ibm.websphere.ihs.doc\/ihs\/cihs_crlinssl.html] \n * For releases of IBM HTTP Server v8.0 [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Fcihs_crlinssl.html]\n \n \n \n \n \n 5. Information that IBM WebSphere Support needs to debug SSL configuration and certificate issues related to the IBM HTTP Server\n * MustGather: SSL handshake and configuration problems [http:\/\/www.ibm.com\/support\/docview.wss?rs=177&context=SSEQTJ&uid=swg21141302]\n \n * MustGather: CMS key database (.kdb) and certificate problems [http:\/\/www.ibm.com\/support\/docview.wss?rs=177&context=SSEQTJ&uid=swg21141303]\n \n \n\n * \n * Brief description of the SSL directives discussed in this document\n * \n \n Listen\n * \n * \n * \n * \n * SSLEnable\n * \n * \n * \n * \n * SSLClientAuth None\n * \n * \n * \n * \n * SSLDisable\n * \n * \n * \n * \n * KeyFile\n * \n * \n * \n * \n * SSLV2Timeout\n * \n * \n * \n * \n * SSLV3Timeout\n * \n * \n * \n * \n * SSLServerCert\n * \n * \n * \n * \n * SSLCipherSpec\n * \n * \n * \n * \n * SSLCipherRequire\n * \n * \n * \n * \n * \n * \n * For releases of IBM HTTP Server v7.0 [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.0 [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_ssldirs.html] For releases of IBM HTTP Server v8.5 [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSAW57_8.5.5\/com.ibm.websphere.ihs.doc\/ihs\/rihs_ssldirs.html] For releases of IBM HTTP Server v9.0 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_9.0.0\/com.ibm.websphere.ihs.doc\/ihs\/rihs_ssldirs.html]"}]},{"id":"TRAIN_Q004","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux (CVE-2018-6551 CVE-2018-6485)\n\n\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-IDs:\nCVE-2018-6551\nCVE-2018-6485\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q005","question":"What happened to load.rules FAQ example?\n\nThe 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.","is_impossible":false,"contexts":[{"filename":"swg21903536.txt","text":"Title: IBM Support's Guide to Rules File Processing - United States\n\nText:\nrules; rules file; array TECHNOTE (FAQ)\n\nQUESTION\n Support Guide : Are there any rules file examples? \n\nANSWER\n \n\nThe Netcool Technical Support Guide to rules file processing is provided as a collection of commonly used rules file techniques. \n\nPlease refer to the Netcool\/OMNIbus Probe and Gateway Guide for general guidance to rules file processing.\n\nRulesfileProcessing_SupportsGuide_30.pdf [\/support\/docview.wss?uid=swg21903536&aid=2]RulesfileProcessing_SupportsGuide_30.pdf [\/support\/docview.wss?uid=swg21903536&aid=1]"}]},{"id":"TRAIN_Q006","question":"Is ITNM exposed to Apache CXF vulnerability (CVE-2017-3156)?\n\nIs 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)","is_impossible":false,"contexts":[{"filename":"swg22008493.txt","text":"Title: IBM Security Bulletin: IBM Tivoli Network Manager IP Edition is affected by an Apache CXF vulnerability (CVE-2017-3156) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Vulnerability has been addressed in the Apache CXF component of Tivoli Network Manager IP Edition. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3156 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3156]\nDESCRIPTION: Apache CXF could provide weaker than expected security, caused by the failure to use the OAuth2 Hawk and JOSE MAC Validation code. A remote attacker could exploit this vulnerability using timing attacks to obtain sensitive information.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/130249 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/130249] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:U\/C:H\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nTivoli Network Manager IP Edition 4.1.1 (Huawei MTOSI Collector install)\nTivoli Network Manager IP Edition 4.2.0 (Huawei MTOSI Collector install)\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/First Fix Tivoli Network Manager IP Edition 4.1.1 IV99816 Please call IBM service and reference APAR IV99816, to obtain a fix if needed for 4.1.1 release. Tivoli Network Manager IP Edition 4.2.0 IV99816 CXF 3.1.10 has been upgraded in 4.2 FixPack 3.\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043575 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043575] WORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nCHANGE HISTORY\n 15 September 2017 : Original Version Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"TRAIN_Q007","question":"Why do I get an exception when calling MQ after migrating my BPM environment (2035 MQRC_NOT_AUTHORIZED) ?\n\n\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)'","is_impossible":false,"contexts":[{"filename":"swg21636093.txt","text":"Title: IBM 2035 MQRC_NOT_AUTHORIZED Connecting to WebSphere MQ from WebSphere Application Server via CLIENT Bindings - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This article covers the most common reasons why an application running in WebSphere Application Server receives a 2035 MQRC_NOT_AUTHORIZED error when connecting to MQ as a client over a network. Quick steps to work around the MQRC_NOT_AUTHORIZED errors during development are provided in the 'Resolving the problem' section, as well as considerations for implementing security in production environments. A summary is also provided of behavior for outbound scenarios with container-managed and component-managed security, as well as inbound behavior for listener ports and activiation specifications \n\nSYMPTOM\nJMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED')\n\n\nCAUSE\nThe two most likely reasons why the connection is refused by MQ are as follows: \n\n 1. The user identifier passed across the client connection from the application server to MQ is not known on the server where the MQ queue manager is running, is not authorised to connect to MQ, or is longer than 12 characters and has been truncated.\n We discuss how this user identifier is obtained and passed over the connection in more detail below.\n For queue managers running on Windows, the following error might be seen in the MQ error logs for this scenario:\n AMQ8075: Authorization failed because the SID for entity 'wasuser' cannot be obtained.\n For UNIX no entry in the MQ error logs would be seen by default.\n See technote MQS_REPORT_NOAUTH environment variable can be used to better diagnose return code 2035 [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=171&uid=swg21299319] for details of enabling error log entries on all platforms. \n 2. The user identifier passed across the client connection from the application server to MQ is a member of the 'mqm' group on the server hosting the MQ queue manager, and a Channel Authentication Record (CHLAUTH) exists that blocks administrative access to the queue manager. WebSphere MQ configures a CHLAUTH record by default in WebSphere MQ Version 7.1 and later that blocks all MQ admins from connecting as a client to the queue manager.\n The following error in the MQ error logs would be seen for this scenario:\n AMQ9777: Channel was blocked\n\nSee the Error logs on Windows, UNIX and Linux systems [http:\/\/pic.dhe.ibm.com\/infocenter\/wmqv7\/v7r5\/topic\/com.ibm.mq.tro.doc\/q039560_.htm] section of the MQ Information Center for the location of the MQ error logs. \nDIAGNOSING THE PROBLEM\nTo understand the cause of the MQRC_NOT_AUTHORIZED reason code, you need to understand what username (and password) is being used by MQ to authorise the application server. \n\nPlease note that WebSphere MQ V7.5 and earlier does not provide any out-of-the box password authentication system for client connections.\nPassword authentication is provided out of the box in IBM MQ V8.0. More details on the new IBM MQ V8.0 security features are available in this presentation [https:\/\/www.slideshare.net\/MoragHughson\/websphere-mq-v8-security-deep-dive]. \n\nFor WebSphere MQ V7.5 and earlier, this means that while the understanding provided in this technote over how usernames\/passwords are passed from the application server to MQ is helpful for development environments, solving the security requirements of production environments usually also requires one of the following approaches: \n\n * Mutual SSL\/TLS authentication.\n MQ provides out-of-the-box features to authenticate a remotely attaching client using the digital certificate they provide for SSL\/TLS transport security. For example by configuring an SSLPEER rule on the SVRCONN channel to match the Distinguished Name in the certificate of the WebSphere Application Server, and establishing trust in the issuer of that certificate. \n * A custom, or 3rd party supplied, WebSphere MQ Security Exit\n A security exit can be written for MQ that performs username and password authentication against a repository, such as the local operating system on the MQ server, or an LDAP repository.\n When using a security exit for authentication it is important that SSL\/TLS transport security is still configured, to ensure passwords are not sent in plain text.\n\n\nMCA user ID (MCAUSER) configured on the Server Connection (SVRCONN) channel If an MCAUSER is configured on the SVRCONN channel that the application server is using to connect, and no security exit or mapping Channel Authentication Record is installed, then this overrides the username provided by the application server. \n\nIt is common practice for many customers to set an MCAUSER on every SVRCONN channel, and use mutual SSL\/TLS authentication exclusively for authentication. \n\nDefault behaviour when no credentials are supplied in the application server \n\nIf no credentials are supplied by the application on the createConnection call, and neither of the component managed or container managed security systems described below are configured, then WebSphere Application Server provides a blank username to MQ. This causes MQ to authorise the client based on the userid that the MQ listener is running under. In the majority of cases this is 'mqm' on UNIX\/Linux systems and 'MUSR_MQADMIN' on Windows. \n\nAs these are administrative MQ users, they will be blocked by default in WebSphere MQ V7.1 and higher, with a AMQ9777 error logged in the error logs of the queue manager. \n\nContainer-managed security for outbound connections \n\nThe recommended way to configure the username and password passed to MQ by the application server for outbound connections, is to use container-managed security. Outbound connections are those created using a Connection Factory, rather than a Listener Port or Activation Specification. \n\nUsernames of 12 characters or less are passed to MQ by the appliaction server. Usernames longer than 12 characters in length will be truncated, either during authorisation (on UNIX), or in the MQMD of messages that are sent. \n\nContainer-managed security means that the deployment descriptor, or EJB 3.0 annotations, of the application declare a resource reference with authentication type set to Container. \n\nThen when the application looks up the Connection Factory in JNDI, it does so indirectly via the resource reference. For example an EJB 2.1 application would perform a JNDI lookup as follows, where \"jms\/MyResourceRef\" has been declared as a resource reference in the deployment descriptor: \n\nConnectionFactory myCF = (ConnectionFactory)ctx.lookup(\"java:comp\/env\/jms\/MyResourceRef\") \n\nAn EJB 3.0 application might declare an annotated object property on the bean as follows:\n@Resource(name = \"jms\/MyResourceRef\", \nauthenticationType = AuthenticationType.CONTAINER)\nprivate javax.jms.ConnectionFactory myCF; \n\nWhen the application is deployed by an administrator, they bind this authentication alias to an actual Connection Factory that has been created in JNDI, and assign it a J2C authentication alias on deployment. \n\nIt is the username and password contained in this authentication alias that is then passed to MQ\/JMS by the application server when the application connects. This approach puts the administrator in control of which username and password is used by each application, and prevents a different application from looking up the connection factory in JNDI directly to connect with the same username and password. \n\nA default container-managed authentication alias can be supplied on the configuration panels in the administrative console for MQ connection factories. This default will only be used in the case that an application uses a resource reference configured for container-managed security, but the administrator has not bound it to an authentication alias during deployment. A screen shot is provided below:\n[\/support\/docview.wss?uid=swg21636093&aid=1] [\/support\/docview.wss?uid=swg21636093&aid=1] \n\nDefault component-managed authentication alias for outbound connections \n\nFor cases where it is impractical to change the application to use container-managed security, or to change it to supply a username and password directly on the createConnection call, it is possible to supply a default. \n\nThis default is called the \"component-managed authentication alias\" and cannot be configured via the administrative console (since WebSphere Application Server Version 7.0 when it was removed from the panels MQ connection factories). The below scripting samples show how to configure it using wsadmin: \n\n * JACL:\n wsadmin>set cell [ $AdminConfig getid \"\/Cell:mycell\" ]\n \n mycell(cells\/mycell|cell.xml#Cell_1)\n \n wsadmin>$AdminTask listWMQConnectionFactories $cell\n \n MyCF(cells\/mycell|resources.xml#MQConnectionFactory_1247500675104)\n \n wsadmin>$AdminTask modifyWMQConnectionFactory MyCF(cells\/mycell|resources.xml#MQConnectionFactory_1247500675104) { -componentAuthAlias myalias }\n \n MyCF(cells\/mycell|resources.xml#MQConnectionFactory_1247500675104) \n * Jython:\n wsadmin>cell = AdminConfig.getid(\"\/Cell:mycell\")\n \n wsadmin>AdminTask.listWMQConnectionFactories(cell)\n \n 'MyCF(cells\/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n \n wsadmin>AdminTask.modifyWMQConnectionFactory('MyCF(cells\/mycell|resos urces.xml#MQConnectionFactory_1247500675104)', \"-componentAuthAlias myalias\")\n \n 'MyCF(cells\/mycell|resources.xml#MQConnectionFactory_1247500675104)'\n\n\nAuthentication alias for inbound MDB connections using an activation specification For inbound connections using an activation specification an authentication alias can be specified by the administrator when deploying the application, or a default authentication alias can be specified on the activation specification via the administrative console. \n\nAuthentication alias for inbound MDB connections using a listener port \n\nFor inbound connections using a listener port, the value specified in the \"Container-managed authentication alias\" setting of the connection factory (seen in the above screenshot) is used. \n\nOn zOS, first the \"Container-managed authentication alias\" is checked and used if set, then the \"Component-managed authentication alias\" is checked and used it set.\n\n\nRESOLVING THE PROBLEM\nThe simplest steps to resolve the 2035 MQRC_NOT_AUTHORIZED errors in a development environment, where full transport security is not required, are as follows: \n\n 1. Choose a user that you want WebSphere Application Server to be authenticated as. Typically the user chosen should have authority relevant to the context of the operations required by the application running in WebSphere Application Server and no more. For example, 'mqm' or other super user is not appropriate. \n 2. If this user is an MQ administrative user, then relax the Channel Authentication Record (CHLAUTH) security in MQ V7.1 or higher, so that administrative connections are not blocked on the SVRCONN channel you wish to use. An example MQSC command to do this for a SVRCONN channel called 'WAS.CLIENTS' is provided as follows:\n SET CHLAUTH('WAS.CLIENTS') TYPE(BLOCKUSER) USERLIST(ALLOWANY) \n 3. Configure the SVRCONN channel to set the MCA user ID (MCAUSER) to the user you have chosen. An example MQSC command to configure a SVRCONN channel to use 'myuser' as the MCA user ID is provided as follows:\n ALTER CHL('WAS.CLIENTS') CHLTYPE(SVRCONN) MCAUSER('myuser')\n\n\nThe following additional considerations are important for production environments: For all production environments where transport security is required, SSL\/TLS security must be configured between the application server and MQ. \n\nIn order to configure SSL\/TLS transport security, you must establish the appropriate trust between the MQ queue manager and WebSphere Application Server. The application server, who initiates the SSL\/TLS handshake, must always be configured to trust the certificate provided by the MQ queue manager . If the application server is configured to send a certificate to the MQ queue manager, then the queue manager must also be configured to trust it. \n\nIf trust is not correctly configured on both sides, you will encounter 2393 MQRC_SSL_INITIALIZATION_ERROR reason codes after enabling SSL\/TLS on the connection. \n\nIf you do not have a security exit that performs username and password authentication, then you should configure mutual SSL\/TLS authentication on your Server Connection channel to cause the queue manager to require a trusted certificate is provided by the application server. To do this you set \"SSL Authentication\" to \"Required\" in the MQ Explorer or SSLCAUTH(REQUIRED) via MQSC. \n\nIf you do have a security exit that performs username and password authentication installed in your MQ server, then configure your application to supply a username and password for validation by that security exit. The details of how to configure the username and password passed to MQ by the application server are described above in the \"Diagnosing the problem\" section. \n\nAll Server Connection channels that do not have SSL\/TLS security applied should be disabled. Example MQSC commands to disable the SYSTEM.DEF.SVRCONN channel are provided as follows (these assume no user exists on the MQ server called 'NOAUTH'):\nALTER CHL(SYSTEM.DEF.SVRCONN) CHLTYPE(SVRCONN) MCAUSER('NOAUTH')\nSTOP CHL(SYSTEM.DEF.SVRCONN) \n\nDetails of how to configure the private certificate and trust of a MQ queue manager, and to enable SSL security on a Server Connection channel, see the following locations in the MQ information center: \n\n * To configure the certificates and trust of the MQ queue manager see the following topic:\n Configuring SSL on queue managers [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r1\/index.jsp?topic=%2Fcom.ibm.mq.explorer.doc%2Fe_ssl_channels.htm] \n * To configure the Server Connection channel, used by applications running in the application server to connect to MQ, see the following topic:\n Configuring SSL channels [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r1\/topic\/com.ibm.mq.explorer.doc\/e_ssl_channels.htm]\n\n\nDetails of how you configure trust within WebSphere Application Server, and whether the application server sends a certificate to MQ for authentication, are in the following locations in the WebSphere Application Server information center: * To create or modify an SSL Configuration containing the appropriate SSL\/TLS configuration for connecting to MQ, see the following topic:\n SSL configurations [http:\/\/www14.software.ibm.com\/webapp\/wsbroker\/redirect?version=phil&product=was-base-dist&topic=csec_sslconfigs]\n Note that MQ requires you specify a matching Cipher Suite \/ Cipher Spec on both sides of the connection, as it checks the negotiated Cipher Suite matches the SSLCIPH setting on the channel after the handshake is complete. As a result the WebSphere Application Server SSL Configuration should be configured to contain only the Cipher Suite that matches the SSLCIPH setting on the Server Connection channel. See the following topic in the MQ information center for details of matching pairs:\n CipherSuite and CipherSpec name mappings for connections to a WebSphere\u00ae 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"}]},{"id":"TRAIN_Q008","question":"Is the Requisite Pro (ReqPro) feature\/plugin supported with a 64-bit RAD\/RSA(4WS) 851+ installation\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21263677.txt","text":"Title: IBM Rational Application Developer Support Policy for 64 bit technology - United States\n\nText:\nRSM; RSD; RSA; RAD; caspian64 bit; 64-bit; RAD 7 64 bit; RAD 7 OS; operating system; Rational Application Developer; X64; Windows 64 bit; supported OS; AMD; PMR #13878; 379; 000; 13878379000; 1263677; 64bit; 64 bit; 32 bit; 32bit; 32-bit; 64-bit; O\/S; OS; requirements; system requirements; 8.0.3; 8.0; 7.5; v8.0.3; v7.5; v7.0; v8.0; v7.5.4; 803; windows 7; server; profile; websphere; test environment; create profile; button; greyed; Run Profile Management Tool ; disabled; IBM Software Development Kit; SDK; JRE; Program Files(x86); WAS; websphere application server; clearcase; scm; clearcase scm adapter; rational requisitepro; reqpro; heap size; jvm; max os x; os x; osx; mac TECHNOTE (FAQ)\n\nQUESTION\n What is the support policy for using IBM Rational Application Developer for WebSphere Software, IBM Rational Software Architect, IBM Rational Software Modeler or IBM Rational Systems Developer version 7.x and 8.x with 64-bit operating systems for Microsoft Windows or Linux? \n\nCAUSE\nThe 7.0.0.x, v7.5.x and v8.0 to 8.0.2 versions of these applications were not designed to take advantage of 64 bit computing and only use 32-bit technology.\n\nANSWER\nThe following IBM Rational Software version 7.x products are only supported on specified 64 bit operating systems running in 32 bit mode: \n\n * Rational Application Developer for WebSphere Software \n * Rational Software Architect \n * Rational Software Modeler \n * Rational Systems Developer\n\n\nSimilarly, Rational Application Developer (RAD) and Rational Software Architect (RSA) version 8.0 to 8.0.2 are only supported on specified 64 bit operating systems running in 32 bit mode. Rational Application Developer v8.0.3+ is available as a 64-bit application install on specified 64-bit operating systems, in addition to a 32-bit application install.\nThere is only one installation package. When installing RAD\/RSA using IBM Installation Manager, on the Location page , if your operating system is 64-bit, then select 64-bit or 32-bit to install the product in the corresponding bit mode. \n\n \n\nThese products will be referred to generically as Rational Software Development Platform (RSDP) based products. For example, WebSphere Integration Developer v6.x\/7.x is RSDP based. \n\nExamples of some 64 bit Operating Systems: \n\n * Microsoft Windows XP Professional x64 Edition (running on an AMD or Intel processor) \n * Microsoft Windows 7 Professional 64-bit \n * Red Hat Linux Enterprise Server 4+ running on x86-64 bit \n * RAD 9.0 under 9.0.1 introduced support for Mac OS x - Lion 10.7 32 bit (with Oracle JDK for Mac OS X 7.0 Update 40) and Mountain Lion 10.8 - 32 bit. Likewise for RSA for WebSphere 9.0.0.1.\n RAD 9.0.1.1 introduced support for 64-bit exploit on Mac OS x Mavericks 10.9 ( with Oracle JDK for Mac OS X 7.0 Update 71)\n RSA 9.1.2 introduced support for 64-bit exploit on Mac OS X Yosemite 10.10 and OS X El Capitan 10.11 (with Oracle JDK 7.0 Update 75 for OS X)\n\n\n\nNote: RSDP 32-bit JVM based products, do not require any additional or special set-up on a supported 64-bit operating system (O\/S). \nThey run on the provided\/supported 32-bit JVM for that RSDP product, as is. \n\nReview the following documents for more details on the system requirements: \n * (7014264) Rational Application Developer System Requirements List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27014264] \n * (7014274) Rational Software Architect Family System Requirements List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27014274] \n * (7014269) Rational Software Modeler System Requirements List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27014269]\n \n\n\nThe above items such as the Rational Application Developer System Requirements List cover latest versions and operating systems such as Windows Vista and Windows 7. Support is limited to 32 bit mode on 64 bit operating systems on all versions prior to Rational Application Developer 8.0.3. For more information consult: \nKnown problems and limitations to installing 64-bit Rational Application Developer [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21499482] \nas referred to by the above Rational Application Developer System Requirements List. The following technote: \n- Benefits, requirements, limitations, and known issues for Rational Software Architect products running as 64-bit applications starting from v8.0.3 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27021665] \n, especially Benefits, describes what is possible with a larger heap size with the 64-bit JVM. \n\nIn deciding if you want a 64-bit install of RAD\/RSA, it is useful to know that the ClearCase SCM Adapter and the Rational RequisitePro integration features\/plugins are not supported or provided. These are only available as 32-bit eclipse plugins. \n\nIf you have any further questions, contact IBM Support for Rational Application Developer, or the appropriate IBM RSDP product support team. \n\n\nWebSphere Servers that are shipped with RSDP products: \n\nThe various WebSphere Application Server v6.x\/7.x servers shipped with Rational Application Developer or Rational Software Architect {for WebSphere} prior to v8.0.4 are only provided as 32 bit editions. As of Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.4+, 64 bit editions of WebSphere Application Server v6.x\/7.x servers are shipped in addition to the 32 bit editions. \n\nThe WebSphere Application Server v8.x (not beta) server shipped with Rational Application Developer or Rational Software Architect {for WebSphere} v8.0.3+ is provided as one edition, and there is an installation option to install either the 32 bit or 64 bit JVM\/JRE (IBM Software Development Kit (SDK)). Any 64 bit edition or 64-bit JVM requires a supported 64 bit operating system. This IBM Education Assistant Module\/PDF : IBM WebSphere Application Server V8 Distributed platform installation [http:\/\/publib.boulder.ibm.com\/infocenter\/ieduasst\/v1r1m0\/topic\/com.ibm.iea.was_v8\/was\/8.0\/Installation\/WASV8_dist_install.pdf] , demonstrates selecting a 32-bit or 64-bit SDK as part of a WAS v8.0 install using IBM Installation manager. If the WAS v8.0 installation is on a 32-bit operating system, this feature choice between IBM 32-bit SDK Java 6.0 or IBM 64-bit SDK Java 6.0 is not available and the installation will automatically default to the IBM 32-bit SDK Java 6.0. \n\nThe shipped WebSphere Portal Server v6.x\/7.x servers are 32 bit or 64 bit editions. depending on whether you chose the IBM WebSphere Application Server Network Deployment, 32-bit or 64-bit server to install on. \n\nNote: It is possible to work with any 64 bit remotely accessible or local stand-alone WebSphere Application Server v6.x\/7.x\/8.x. In Rational Application Developer 8.0.3+ be aware of the Info Center topic: Creating profiles for WebSphere Application Server on a 64-bit machine [Creating%20profiles%20for%20WebSphere%20Application%20Server%20on%20a%2064-bit%20machine] and see this APAR opened against RAD 8.5.1\/8.5.5 : PI06339: A 64-bit install of the WebSphere Application Server Profile Management Tool may not launch on Windows 7. RELATED INFORMATION\n Benefits for RSA v8.0.3 products running as 64-bit app [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27021665]\nInternet Explorer v9+ required if using 64-bit Bit Mode [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21502701]\nRAD 8.0.3+ IC: Creating profiles for WAS on a 64-bit ma [http:\/\/publib.boulder.ibm.com\/infocenter\/radhelp\/v8\/index.jsp?topic=\/com.ibm.servertools.doc\/topics\/rbitmachine.html]\nRational ClearCase SCM adapter not available for 64-bit [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21502974]\nCannot install the Java Visual Editor in RAD 64 bit [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21499219]\nRAD64bit Known problems to install or run [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21499482]\nWAS V8.0 & V8.5 64-bit Install offer Program Files (x86 [https:\/\/developer.ibm.com\/answers\/questions\/175210\/why-does-was-v80-and-v85-offer-program-files-x86-a.html]\nAbout SCM Adapter support on 64 Bit [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21460547]\nConversion of 32 bit to 64 bit WAS on the same machine [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21625930]\nRAD901: Installing RAD for WebSphere Software [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSRTLW_9.0.1\/com.ibm.rad.install.doc\/topics\/t_install_product.html]\nRAD 9.0.x: new features and enhancements-9.0.1-new_OSup [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27038836#whatsnew_901_OSupdates]\nRAD 9.0.1 System Requirements - O\/S [http:\/\/www-969.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/osForProduct?deliverableId=1374678040873#osFamily-1]\nRSA(4WS) 9.0.x: new features and enhancements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038488]\nRSA 9.1.2: new features and enhancements - jdk [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27041555#whatsnew_912_JTE]\nA simplified Chinese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21504145]\n\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Software Architect Documentation Linux, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5, 7.0.0.6, 7.0.0.7, 7.0.0.8 Software Development Rational Software Modeler Documentation Windows, Linux 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Systems Developer Documentation Linux, Solaris, Windows 7.0, 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4 Software Development Rational Software Architect for WebSphere Software General Information Linux, Windows 7.5, 7.5.1, 7.5.2"}]},{"id":"TRAIN_Q009","question":"Unable to locate the More tab of Document class - Property definition tab - property template configuration to update Is Required setting.\n\nUnable 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","is_impossible":false,"contexts":[{"filename":"swg21696083.txt","text":"Title: IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States\n\nText:\nACCE; CE; Property; FEM TECHNOTE (FAQ)\n\nQUESTION\n With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class\n\n1. Launch FEM\n2. Expand the object store and document class tree. Right click on the document class and select \"Properties\"\n3. Go to \"Properties Definitions\" tab, highlight the property definition and click \"Edit\"\n4. Make the modification and click OK\n5. Click OK again to save the change\n\nHow to perform the same operation with FileNet Content Engine - ACCE? \n\nANSWER\nFollow the below steps to update the property definition properties on ACCE: \n\n\n\n\n 1. Launch ACCE \n 2. Expand the object stores folder and click the object store to open the Object store tab \n 3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab \n 4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify \n 5. ACCE will open that property definition in a new Properties tab \n 6. Modify the property definition as required \n 7. Go back to the Class Definition tab and click Save"}]},{"id":"TRAIN_Q010","question":"managesdk.sh -listEnabledProfileAll fails with error: Couldn't get file lock.\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21515420.txt","text":"Title: IBM Starting WebSphere Application Server gives warning message - Could not lock User prefs - United States\n\nText:\nWebsphere; startup; FileSystemPreferences; user prefs; prefs; Could not lock User prefs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Warning message issued during the non-root or root startup of WebSphere stating that it can not lock the user or system preferences. \n\nSYMPTOM\nThe following message can be seen in the systemout.log: \n\n[9\/11\/11 18:03:19:921 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences syncWorld Couldn't flush user prefs: java.util.prefs.BackingStoreException: Couldn't get file lock.\n[9\/11\/11 18:03:49:929 EDT] 00000001 prefs W java.util.prefs.FileSystemPreferences checkLockFile0ErrorCode Could not lock User prefs. Unix error code 2.\n\n\nCAUSE\nThe non-root ID that is being used to start WebSphere Application Server does not have a user_home directory. Therefore this non-root ID is unable to access the root user's \"\/etc\/.java\/.systemPrefs\". This produces the aforementioned warning messages every 30 seconds in the profile_root\/logs\/server_name\/systemout.log.\n\nThe root ID used to start Websphere Application Server can not find the Java system pref file. \n\n\nDIAGNOSING THE PROBLEM\nFor non-root, you can confirm this issue by trying to start WebSphere using the \"root\" ID. Review the Websphere_Home\/profiles\/\/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."}]},{"id":"TRAIN_Q011","question":"Load SPSS 25 on a new computer\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21966637.txt","text":"Title: IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You have successfully installed an IBM SPSS Statistics product on a Mac computer. When you start the License Authorization Wizard (LAW) to enter the authorization code for licensing.\n\nYou receive the following message:\n\n\n\"Warning! You do not have the correct administrator privileges to license this product. Log in as administrator and try again, or contact your network administrator to correct this issue.\n\n\"\n\nOnce this message is displayed the only option available is \"OK\" to click on and you cannot enter your authorization code. \n\nRESOLVING THE PROBLEM\nBelow is a picture of the warning: \n\n[\/support\/docview.wss?uid=swg21966637&aid=1] [\/support\/docview.wss?uid=swg21966637&aid=1]\n\nIf you encounter this message, perform the following procedure:\n\n\n 1. If open, close the IBM SPSS Statistics product. \n 2. If open, close the License Authorization Wizard. \n 3. Open Finder. \n 4. Select the 'Go' menu. \n 5. Select the 'Utilities' menu. \n 6. Open the 'Terminal' program. \n 7. Type (copy\/paste) the following command:\n \n cd \/Applications\/IBM\/SPSS\/Statistics\/ \n 8. \n 9. Press Enter\/Return. \n 10. Perform the procedure corresponding to the Statistics product version as described below:\n\n\nStatistics Release 20 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 21 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 21\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 22 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 22\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\n\nStatistics Release 23 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 23\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 24 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 24\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product. \n 7. \n 8. \n\nStatistics Release 25 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 25\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nTo confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22) \n\ncd \/Applications\/IBM\/SPSS\/Statistics\/22\/SPSSStatistics.app\/Contents \n\nthen, type the following: \n\nls -l \n\n(2) Press Enter\/Return. \n\n \n\nIf you see some or all of subfolders shows a group ownership other than 'admin' (as displayed in Picture1), the procedure did not succeed. You will need to have your Mac IT support contact IBM SPSS Support for further assistance. \n\nPicture1:\n[\/support\/docview.wss?uid=swg21966637&aid=2] [\/support\/docview.wss?uid=swg21966637&aid=2]\n\nPicture 2: \n\nIf you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.\n[\/support\/docview.wss?uid=swg21966637&aid=3] [\/support\/docview.wss?uid=swg21966637&aid=3]\n\nThis behavior is also reported on the following product correction report (APAR): [https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\n[https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\nhttps:\/\/www.ibm.com\/support\/entdocview.wss?uid=swg1PI41134 [https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\n\nAn IBM ID is required to access this material.\n\nIf needed, an IBM ID may be created at https:\/\/ibm.biz\/ibm_web_id [https:\/\/ibm.biz\/ibm_web_id]\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/spsslicensing.html]"}]},{"id":"TRAIN_Q012","question":"Are there any instructions for ulimit settings for WebSphere running on Linux?\n\nAre 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.","is_impossible":false,"contexts":[{"filename":"swg21648497.txt","text":"Title: IBM Insufficient ulimit Value Causes Native OutOfMemory - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n An out of memory may be observed on a system running WebSphere Application Server on Linux or AIX that is due to ulimit restrictions on number of process\/threads per user. Further investigation may reveal a \"Failed to create a thread:\" message within the generated javacore which would indicate a native out of memory issue has been encountered. The cause of the problem may be an insufficient ulimit setting. While this type of issue can occur on any level of Linux, or AIX, the issue is most likely to be seen in systems running multiple instances of WebSphere Application Server using one userid. The following will outline how to identify if a process ulimit is the culprit and what WebSphere Application Server Support recommends to fix the case. \n\nSYMPTOM\nAn out of memory Dump Event such as: \n\n\"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\"\n\"Failed to create a thread: retVal -1073741830, errno 11\" received\n\nNote: This detailed message will appear only in javacores.\n\n\nDIAGNOSING THE PROBLEM\nWhen using WebSphere Application Server, ulimits can be set to fix or tune around a number of problems. For more on how to set a ulimit refer to the \"Guidelines for setting ulimits [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21469413]\" Technote which goes into detail on setting different ulimits on various operating systems and the difference between the soft and hard limit. This article is concerned particularly with the \"-u\" ulimit or \"nproc\" limit on Linux, the ulimit - r on AIX which affects the number of threads allowed for a single user process running WebSphere Application Server. \n\nThe AIX issue is less commonly seen as it limits then number of threads for a process but is seen in application servers with very large thread pools, This is becoming more common in 64bit addressing JVMs running complex applications. WebSphere Application support recommends setting the ulimit -r ulimited on AIX.\n\nThe nproc limit usually only counts processes on a server towards determining this number. Linux systems running WebSphere Application Server are a particular case. The nproc limit on Linux counts the number of threads within all processes that can exist for a given user. To determine the ulimit settings of a WebSphere Application Server process running on Linux refer to \"How to determine the ulimit settings of a running WebSphere Application Server process on Linux [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21407889]\".\n\nUser Limits (in bytes except for NOFILE and NPROC) \n\ntype soft limit hard limit RLIMIT_AS unlimited unlimited RLIMIT_CORE unlimited unlimited RLIMIT_CPU unlimited unlimited RLIMIT_DATA unlimited unlimited RLIMIT_FSIZE unlimited unlimited RLIMIT_LOCKS unlimited unlimited RLIMIT_MEMLOCK 65536 65536 RLIMIT_NOFILE 65536 65536 RLIMIT_NPROC 131072 131072 \n\nFor most cases of older versions of Linux this value will be defaulted to around 2048. For out of the box Red Hat Enterprise Linux (RHEL) 6 the default value for nproc will be set to 1024. This low default setting for larger systems will not allow for enough threads in all processes. \n\nWebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created. \n\nBy using this recommended value a sufficient number of threads in all processes will be allowed and will not be a limiting factor for the environment. Increasing the limit to the suggested value should have no negative impact. When the number of threads in all processes reaches the -u ulimit, an out of memory error message will be thrown. This issue can be avoided by increasing this limit. Be aware that if the number of threads\/processes reaches the recommended number of 131072 or close, the issue may be deeper and continuing to increase the -u ulimit will only prove to be a temporary fix. \n\nOnce the ulimit is increased, the WebSphere Application Server will need to be restarted to use the \nnew setting. In the case of WebSphere Application Server ND, the nodeagent and the servers on the nodes will need to be restarted."}]},{"id":"TRAIN_Q013","question":"Can I apply a TIP 2.2 fix pack directly to a TIP 2.1 installation?\n\nCan 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.","is_impossible":false,"contexts":[{"filename":"swg21618719.txt","text":"Title: IBM Applying TIP 2.2 fix packs directly to a TIP 2.1 installation - United States\n\nText:\nTIPL2; TIPL2INST; tivoli Integrated portal; feature pack TECHNOTE (FAQ)\n\nQUESTION\n Can Tivoli Integrated Portal 2.2 fix packs be applied directly to a TIP 2.1 installation?\n\n\nANSWER\nIn order to apply TIP 2.2 fix packs, the target TIP installation must already be at TIPCore 2.2.0 or newer. TIP 2.1 installations must be upgraded to TIP 2.2 using the TIP 2.2.0.1 feature pack. The TIP 2.2.0.1 feature pack can be acquired from IBM Fix Central [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~Tivoli&product=ibm\/Tivoli\/Tivoli+Integrated+Portal&release=All&platform=All&function=all]. \n\nThe following three items should be obtained from Fix Central: \n\n * 2.2.0.1-TIV-TIP--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]"}]},{"id":"TRAIN_Q014","question":"NMA agent installation failure\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21983839.txt","text":"Title: IBM Problems installing NMA agent (N4 agent) on Linux x86-64 - United States\n\nText:\nITM Virtual environments install NMA N4 unable find bundle prerequisites CI addbundles TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The installation of NMA agent from package ITM for Virtual Environment V7.2.0.3 is failing with both remote or local installation on Linux x86-64. \n\nSYMPTOM\n1) The import of the whole bundle using command: \n\n\/opt\/IBM\/ITM\/bin\/tacmd addbundles -i \/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<\/PrereqProdCode>\n\n\n\n06<\/Version>\n\n22<\/Release>\n\n04<\/Mod>\n\n000<\/Level>\n\n\nto \n\n\nci<\/PrereqProdCode>\n\n\n\n06<\/Version>\n\n30<\/Release>\n\n05<\/Mod>\n\n000<\/Level> \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"}]},{"id":"TRAIN_Q015","question":"Help with Action required for IIB V9 & WMB V8 Hypervisor Editions for security vulnerabilities in Red Hat Linux\n\n\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","is_impossible":false,"contexts":[{"filename":"swg21998452.txt","text":"Title: IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux. \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-2126, CVE-2016-2125, CVE-2016-2123, CVE-2016-8866, CVE-2016-9556, CVE-2016-9559, and CVE-2016-9773. \n\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with Red Hat Enterprise Linux (RHEL) Server 6.2.\n\nRemediation: \n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 \nPRODUCT ALIAS\/SYNONYM\n WMB HVE IIB HVE"}]},{"id":"TRAIN_Q016","question":"What can be done about \"Too many open files\" messages in the DASH systemOut?\n\nWhat 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.","is_impossible":false,"contexts":[{"filename":"swg21469413.txt","text":"Title: IBM Guidelines for setting ulimits (WebSphere Application Server) - United States\n\nText:\nulimits; linux; unix; aix; openfiles; opensockets; sockets; socket; files; ulimit-n; limits.conf; configuration; security; etc; root; init; crontask; cron; nodeagent; dmgr; appserver; server; applicationserver; application; nofile; unlimited; 8000; 8192 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes various ways to set ulimit values on UNIX and Linux operating systems as well as information that pertains to WebSphere Application Server \n\nSYMPTOM\nTuning ulimits correctly can overcome these errors: \n\n * Too Many Open Files \n * Could not lock User prefs. Unix Error Code 24. \n * Truncated Core Dumps \/ Heap Dumps\n\n\nRESOLVING THE PROBLEM\n \n\nIs it possible to display the current ulimit settings? The command ulimit -Xa will display all current settings that are set for the current login session, where X represents the hard (H) or soft (S) limits to be displayed. By default, if no value is supplied for X, soft limits will be displayed. However if a process is already running, it may have a different ulimit configurations than the current shell that you run the ulimit -a command in.\n\n\n\n\nHow are ulimts set? Soft vs. Hard limits Soft limits are the current setting for a particular limit. They can be increased only to the current hard limit setting. \n\nHard limits are the maximum limit that can be configured. Any changes to these require root access. \n\n \n\nTemporary Settings (for current session) \n\n * \n * ulimit -[H|S]limit_name limit_value\n\n\nTemporary settings are set via the command line using the ulimit command. The limit_name must be present in the command (see the chart below). These settings are only temporary for the current session and will be lost once the session is over or the terminal window is closed. \n\nThis syntax can be used within shell scripts. Any processes spawned from these shell scripts will also have the temporary settings for the lifetime they are running. \n\nBy default, the soft limit will be changed (as changing the hard limit needs root access). Use -H (for hard limits) or -S (for soft limits) to change specific hard or soft limits. \n\nNOTES: \n\nOn HP-UX, if you receive an error when setting a particular limit, and you have altered that particular hard limit, you may need to check and see if it had exceeded the kernel parameters. You can use kctune to check (and alter) these if necessary; check your HP-UX documentation for more information. \n\nFor Solaris, settings in the \"\/etc\/system\" configuration file also allow configuring of some kernel-wide limits. \n\n \n\nGlobal Settings \n\n[\/support\/docview.wss?uid=swg21469413&aid=1] Any changes to these global configuration limits files should be performed by your system administrator. Instructions on how to edit the files can be found on the manpage or in the commented section of the configuration file, as they can vary between versions of UNIX or Linux. \n\n \n\nThe format of the file, which differs slightly on versions of AIX and Linux, allows individual limits per users or groups, as well as set hard and soft limits. The limits defined in this configuration file are set globally. \n\n \n\nChanges made to any limits file take effect after launching a new login shell (such as bash -l), or if the user logs out and logs back in to the system. \n\n \n\nNOTES: \n\nOn Solaris and HP-UX, changes made to your shell's profile configuration (.profile or .login) should also take effect on the next login shell launched, or when your user logs back in using the specific shell. \n\nFor kernel-wide settings, which usually require a restart of the operating system to take effect, HP-UX has the kctune command, while Solaris has the \/etc\/system configuration file. \n\n \n\nSpecifics for each Operating System:\nThe most up-to-date information on the limits can be found in the man page for \"ulimit\".\n\n\n\nAIX \nGlobal settings are generally set in the file \/etc\/security\/limits, although there may be different limit files for LPARs and WPARs. \n\n \n\nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or the limits file for further information.\n\n\n\nCommand Line limit_name * \/etc\/security\/limits Description ulimit -c [value] core\ncore_hard Core file size in 512 byte blocks. ulimit -d [value]\n(K bytes) data\ndata_hard Data segment size of processes in kilobytes. ulimit -f [value] fsize\nfsize_hard File size limit in 512 byes blocks. ulimit -n [value] nofiles\nnofiles_hard Max number of open files and\/or sockets per process. ulimit -m [value]\n(K bytes) rss\nrss_hard The memory size of the process in kilobytes. ulimit -r [value] threads\nthreads_hard Max number of threads per process. ulimit -s [value]\n(K bytes) stack\nstack_hard The stack segment size in kilobytes. ulimit -t [value]\n(seconds) cpu\ncpu_hard Max per process CPU time (in seconds). ulimit -u [value] nproc\nnproc_hard Specifies the limit of the number of processes per user. * Values are in 512 byte blocks unless otherwise specified, check your man page for further information \n\n\nHP-UX \n\nThere is no global settings file on HP-UX. Instead, you would need to issue the specific ulimit command in your shell's (or user's) profile configuration (like .profile or .login). \n\nThere are similar kernel settings you can also set with kctune, such as \"maxfiles_lim\", but these kernel parameters do not normally need to be changed. Please refer to its man page for further information. \nPlease note that this table may not represent all ulimit items as they can vary between operating system versions. Consult the ulimit man page or your OS documentation for further information.\n\n\n\nCommand \"ulimit\" limit_name* Description ulimit -c [value] Core file size in 512 byte blocks. ulimit -d [value] Data segment size of processes in 512 byte blocks. ulimit -f [value] File size limit in 512 byes blocks. ulimit -n [value] Max number of open files and\/or sockets per process. ulimit -m [value] The memory size of the process in 512 byte blocks. ulimit -s [value] The stack segment size in 512 byte blocks. ulimit -t [value]\n(seconds) Max per process CPU time (in seconds). * Values are in 512 byte blocks unless otherwise specified, check your man page for further information. \n\n\nLinux \nGlobal settings are set in the file \/etc\/security\/limits.conf. \n\nThe format for setting each limit is as follows:\n \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]"}]},{"id":"TRAIN_Q017","question":"Does Portal 6.1.x support Oracle 12c?\n\n\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)","is_impossible":false,"contexts":[{"filename":"swg27019359.txt","text":"Title: IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States\n\nText:\nDSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION\n\nABSTRACT\n IBM WebSphere Portal V6.1.0.5 and 6.1.5.2 hardware and software requirements on an AIX operating system. The hardware and software requirements reflect the versions of prerequisites and corequisites that were tested with WebSphere Portal V6.1.0.5 and 6.1.5.2. \n\nCONTENT\n\n\n\nTAB NAVIGATION\n * AIX [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019359]\n * i5\/OS [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019362]\n * Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019366]\n\nIBM AIX\n\n\n\n\nWebSphere Portal Server Version 6.1.0.5 and 6.1.5.2 (AIX) \n\nThis page describes the minimum product levels that need to be installed before opening a problem report with IBM WebSphere Portal Technical Support. The software versions and any maintenance levels listed on this page have been explicitly verified as working. \n\nEARLIER LEVEL OF A LISTED SOFTWARE: Software versions at a lower level than those noted on this page are unsupported. LDAP software at an earlier level is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]). \n\nLATER LEVEL OF A LISTED SOFTWARE: Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are compatible with the tested versions. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]). \n\nUNLISTED SOFTWARE: Software not listed on this page at any level is unsupported. LDAP software not listed is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]).\n\n\n\nOperating systems\nsupported with 32-bit WebSphere Application Server and WebSphere Portal [\/support\/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (32-bit or 64-bit operating system)\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Operating systems\nsupported with 64-bit WebSphere Application Server and WebSphere Portal [\/support\/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (64-bit operating system)\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] AIX hardware requirements [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM POWER family of processors \n * Disk space requirements: * Minimum 2.5 GB free disk space for installation for WebSphere Portal \n * Minimum 1.0 GB free disk space for installation for WebSphere Application Server \n * Minimum 4 GB total disk space recommended for installation \n \n \n * Physical memory: Under minimal load, WebSphere Portal can function with 2GB of RAM. However, 4GB is an optimal starting point for RAM in a production environment. \n * CD-ROM drive\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Application Servers\nThe WebSphere-supplied Java SDK is required for both the run time and any remote Java clients. [\/support\/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server V7.0.0.11 with IBM SDK 1.6 SR12 (WebSphere Application Server product site) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/]#1a#1b#1b \n * WebSphere Application Server V6.1.0.31 with IBM SDK 1.5 SR7 (WebSphere Application Server product site) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/]#1a#1b * Note: IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 6.1.x after that date with extended support, Java SDK V5 is no longer included\n \n \n\nRefer to \"Required WebSphere Interim Fixes for WebSphere Portal V6.1.0.5 and V6.1.5.2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24027476]\" for the complete list of fixes required for WebSphere Application Server. [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Optional WebSphere Servers [\/support\/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server SCA feature pack 1.0.1.5 \n * WebSphere Application Server XML feature pack 1.0.0.5 \n * WebSphere Process Server V6.2.0.2*, 6.1.2.3, and 6.1.0.4 (all via Client Install option only with WAS 6.1x releases) *Refer to technote #1398123 for Process Server V6.2 Client installation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21398123] \n * WebSphere Virtual Enterprise (formerly \"Extended Deployment\") V6.1.1.1, 6.1.0.5 (WebSphere Extended Deployment product site [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/])\n\nJavaScript Library [\/support\/docview.wss?uid=swg27019359&aid=1] * Dojo V1.3.2 or 1.1.1\n\nTo take advantage of the support for Microsoft Internet Explorer V8.0 or to use the new features in 6.1.5.2 such as Mashups integration and the Page Builder Theme, you will need to use Dojo V1.3.2. Refer to the topic \"Using a different Dojo version [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1\/topic\/com.ibm.wp.ent.doc_v615\/admin\/epc_use_prior_dojo.html]\" for more information. [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Databases\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] * Derby V10.1 and 10.3 \n\n * IBM DB2 Universal Database (DB2 product site) [http:\/\/www.ibm.com\/software\/data\/db2\/9\/] (also supports High Availability Disaster Recovery (HADR) Feature) * V9.7 FP1 for Linux, Unix, Windows \n * V9.5 for Linux, Unix, Windows: Enterprise Server Edition 9.5 FP5, Express Edition 9.5 FP5, Workgroup Server Edition 9.5 FP5 (viper 2) (including HADR) \n * V9.1 for Linux, Unix, Windows: Enterprise Server Edition 9.1 FP9, Express Edition 9.1 FP9, Workgroup Server Edition 9.1 FP9 (including HADR) \n * V8.1 for Linux, Unix, Windows: Enterprise Server Edition 8.1 FP16, Express Edition 8.1 FP16, Workgroup Server Edition 8.1 FP16 (including HADR)\n \n \n * IBM DB2 for z\/OS V9.1 and V8.1, PUT level 0901 or later maintenance (DB2 for z\/OS product site) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/]#2 (also supports High Availability Disaster Recovery (HADR) Feature) \n * WebSphere Information Integrator V8.2 FP4\n\n * Oracle (Oracle Database product site) [http:\/\/www.oracle.com\/database\/index.html] (Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover#3a) * Standard\/Enterprise V9.2.0.8, 10.1.0.5 Patch 4, 10.2.0.4 and 10.2.0.5 (patchset 8202632) (including RAC) (Supports Automatic Storage Management (ASM) Feature) \n * Oracle 11gR2 V11.2.0.1 (including RAC) \n * Oracle 11gR1 V11.1.0.7 (including RAC)\n \n \n \n * Microsoft SQL Server (Microsoft product site) [http:\/\/www.microsoft.com] * Enterprise Edition 2008 SP1 [http:\/\/www.microsoft.com] \n * Enterprise Edition 2005 SP3\n \n \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Java Database Connectivity (JDBC) Drivers [\/support\/docview.wss?uid=swg27019359&aid=1] * DataDirect Connect JDBC 4.0 (type 4) (DataDirect Connect JDBC product site [http:\/\/www.datadirect.com\/products\/jdbc\/index.ssp]) \n * DB2 Driver for JDBC and SQLJ 3.1 (type 2\/4) \n * JCC JDBC driver level 3.58.90 or above to connect to DB2 for z\/OS Note: Use the JDBC drivers provided with DB2 LUW V9.7 FP2 when the Portal is not also running on z\/OS \n * Derby embedded JDBC Driver \n * Microsoft SQL Server JDBC Driver 1.2 or 2.0 (Microsoft SQL Server JDBC Driver site [http:\/\/msdn.microsoft.com\/en-us\/data\/aa937724.aspx]) \n * Oracle 9i or 10g or 11g JDBC Driver Thin (type 4) (Oracle JDBC product site [http:\/\/www.oracle.com\/technology\/software\/tech\/java\/sqlj_jdbc\/index.html])\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Web servers\n[\/support\/docview.wss?uid=swg27019359&aid=1] * Apache HTTP Server V2.0.5.9 (Apache Server product site) [http:\/\/httpd.apache.org\/] (Apache Server 2.0.5.9 includes CERT Advisory CA-2002-17) \n * Apache HTTP Server V2.2 (Apache Server product site) [http:\/\/httpd.apache.org\/] (Apache 2.2.x is supported with WebSphere Application Server 7.0.#4a)#4a \n * IBM HTTP Server for WAS V7.0 and 6.1 (IBM HTTP Server product site) (HTTP Server 7.0 is supported with WebSphere Application Server 7.0 only) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] \n * IBM HTTP Server for iSeries V7R1, V6R1 and V5R4 (IBM HTTP Server product site) [http:\/\/www-03.ibm.com\/systems\/i\/software\/http\/index.html](HTTP Server for i5\/OS is provided natively on System i5 and is not bundled with or installed by WebSphere Portal. For V5R4, supported group PTF is SF99114 level 13; for V6R1, supported group PTF is SF99115 level 1. For V5R4, the license program number is 5722DG1; for V6R1, the license program number is 5761DG1. Issue the GO LICPGM to display all the installed licensed programs. For WebSphere Application 6.1.0.21 on V6R1M0, apply SI35071. For WebSphere Application 7.0.0.1 on V6R1M0, apply SI35078) \n * Microsoft Internet Information Services (IIS) V7.5 or 7.0 (only for WAS 7 environments) and 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http:\/\/www.lotus.com\/products\/product4.nsf\/wdocs\/dominohomepage]#4d(To use Lotus Domino Version 7.0 with WebSphere Application Server 6.1, you must install the Web Server plug-in for Lotus Domino Server Version 6 which is a part of the Web Server plug-in for WebSphere Application Server 6.1) \n * Sun Java System Web Server 7 Update 8 or 6.1 SP12 (Sun product site) [http:\/\/www.sun.com\/products\/] \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Web browsers\n(required for administration\/configuration, sample program execution and launch pad. There is no restriction nor certification of Web browsers on clients that connect the server to display content) [\/support\/docview.wss?uid=swg27019359&aid=1] * 6.1.0.5: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n * Firefox V3.6, 3.5, 3.0, 2.0, 1.5.0.7 (Firefox product site) [http:\/\/www.mozilla.org\/] \n * Apple Safari 3.2 and higher (Apple product site) [http:\/\/www.apple.com\/safari\/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http:\/\/www.apple.com\/safari\/] \n Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077]\n * Opera 9.52 and higher [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077](Opera product site) [http:\/\/www.opera.com\/products\/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21318444]\n \n \n * \n * 6.1.5.2: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n PageBuilder, Mashup Integration and Wiki\/Blogs in V6.1.5.2 are not supported or functional when using Microsoft Internet Explorer V6.0.#6f \n * Firefox V3.6, 3.5, 3.0 (Firefox product site) [http:\/\/www.mozilla.org\/] \n * Apple Safari 3.2 and higher (Apple product site) [http:\/\/www.apple.com\/safari\/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http:\/\/www.apple.com\/safari\/]\n Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077]#6a#6e \n * Opera 9.52 and higher (Opera product site) [http:\/\/www.opera.com\/products\/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21318444]#6b\n \n \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] LDAP servers\n[\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http:\/\/www.lotus.com\/products\/product4.nsf\/wdocs\/dominohomepage] For 7.0.2 and 7.0.1: Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup. Turkish users should use version 7.0.3 or later.#7a \n * IBM Tivoli Directory Server 6.2, 6.1 and 6.0 (IBM Tivoli Directory Server product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] Add the fix for APAR IO02714 on applicable releases, available at IBM Support.#7b \n * IBM z\/OS Security Server 1.7 and 1.6 (IBM z\/OS Security Server product site) [http:\/\/www.ibm.com\/systems\/z\/advantages\/security\/index.html] \n * IBM z\/OS.e Security Server 1.7 and 1.6 (IBM z\/OS Security Server product site) \n * Novell eDirectory 8.8 or 8.7.3 (Novell eDirectory product site) [http:\/\/www.novell.com\/products\/edirectory\/] \n * Sun Java System Directory Server 7, 6.3, 6.1, and 6 (Sun product site) [http:\/\/www.sun.com\/products\/] \n * Microsoft Active Directory 2008, including Lightweight Directory Server (AD LDS, previously referred to as \"Application Mode\" or ADAM) \n * Windows Active Directory 2000 and 2003 including Application Mode\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for collaboration - Domino and Extended Products (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1, 6.5.6 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] Domino V8.5.2 also needs the fix applied for SPR DPOS895USS, contact Domino Technical Support for the fix. \n * IBM Lotus Domino Document Manager V7 and 6.5.1 \n * IBM Lotus Sametime V8.5, 8.0.2, 8.0, 7.5.1 and 7.5 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for content management (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Web Content Management V6.1.0.5 or 6.1.5.2 (IBM Lotus Web Content Management product site) [http:\/\/www.ibm.com\/software\/lotus\/products\/webcontentmanagement\/] \n * Ephox EditLive IBM LWCM OEM version 3.4.1.41 (which includes EditLive version 7.0.1.46.) (Ephox EditLive product site [http:\/\/www.ephox.com]) \n * IBM Lotus Quickr V8.5, 8.1.1 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] \n * 6.1.5.2: IBM Lotus FileNet P8 V4.5 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] \n * 6.1.5.2: IBM Content Manager V8.4 (IBM Content Manager product site) [http:\/\/www.ibm.com\/software\/data\/cm\/cmgr\/]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Supported Java Runtime Environments - Web Content Management authoring portlet [\/support\/docview.wss?uid=swg27019359&aid=1] * Java Runtime Environments (requires one) V1.6.x or 1.5.x (Sun product site) [http:\/\/www.sun.com\/products\/]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] External Security software (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli Access Manager V6.1 and 6.0 for trust association interceptor and enhanced trust association interceptor (support for Subject creation) (Tivoli Access Manager product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal. \n * IBM Tivoli Access Manager V6.0 for Java Authorization Contract for Containers (JACC) (Tivoli Access Manager product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal \n * Computer Associates SiteMinder V6.0\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for portlet development [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Rational Application Developer V7.5 and 7.0.6 (plugin for UTE) \n * IBM Portlet Factory V6.1.5, 6.1\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=2] [\/support\/docview.wss?uid=swg27019359&aid=3] [\/support\/docview.wss?uid=swg27019359&aid=3] Software for license management [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli License Compliance Manager V2.3\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=4] [\/support\/docview.wss?uid=swg27019359&aid=5] [\/support\/docview.wss?uid=swg27019359&aid=5] \n\nRelated information\n[http:\/\/d02was006.southbury.ibm.com\/support\/dcf\/preview.wss?host=d02dbs88.southbury.ibm.com&db=support\/swg\/swgdocs.nsf&unid=2D60E6429AA6F54285256FB00046AC9D&taxOC=SSCVS22&MD=2005\/02\/25%2008:02:00&sid=]Detailed system requirements [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27007791]\nWebSphere Portal Information Centers and more [http:\/\/www.ibm.com\/developerworks\/websphere\/zones\/portal\/proddoc.html]\nSupport Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc\/overview\/inst_req_supt.html] \n\nSee disclaimer. \n\nTop of page \n\nDisclaimer\nIBM reserves the right to change specifications and other product information without prior notice. This publication could include technical inaccuracies or typographical errors. References herein to IBM products and services do not imply that IBM intends to make them available in other countries. IBM PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. \n\nTop of page \n\n\n\n\nORIGINAL PUBLICATION DATE\n 2009\/9\/1"}]},{"id":"TRAIN_Q018","question":"Why does the transaction time out when I try to delete a virtual portal?\n\nTransaction 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","is_impossible":false,"contexts":[{"filename":"swg21611073.txt","text":"Title: IBM Deletion of virtual portal fails with transaction timeout - United States\n\nText:\nvirtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempt to delete virtual portal via Virtual Portal Manager portlet fails with error:\n\nEJPAH4000E: Failed to delete virtual portal \n\nAttempts to delete the virtual portal using the ConfigEngine task \"delete-virtual-portal\" may fail as well.\n\n\nCAUSE\nWith the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded: \n\n * the total and\/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may show the following: \n\nExample #1:\n\n[9\/10\/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.\n\n[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction\ncom.ibm.icm.ci.CDMTransactionException\nat com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)\nat com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)\nat com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n....\n\n[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n.... \n\nExample #2: \n\n[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.\n[datestamp] 000000f4 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was: \njava.net.SocketInputStream.socketRead0(Native Method)\njava.net.SocketInputStream.read(SocketInputStream.java:150)\njava.net.SocketInputStream.read(SocketInputStream.java:121)\ncom.ibm.db2.jcc.t4.x.b(x.java:208)\ncom.ibm.db2.jcc.t4.x.c(x.java:360)\ncom.ibm.db2.jcc.t4.x.c(x.java:473)\ncom.ibm.db2.jcc.t4.x.v(x.java:1241)\ncom.ibm.db2.jcc.t4.ab.a(ab.java:61)\ncom.ibm.db2.jcc.t4.p.a(p.java:50)\ncom.ibm.db2.jcc.t4.rb.b(rb.java:220)\ncom.ibm.db2.jcc.am.po.qc(po.java:3498)\ncom.ibm.db2.jcc.am.po.b(po.java:4461)\ncom.ibm.db2.jcc.am.po.ic(po.java:799)\ncom.ibm.db2.jcc.am.po.executeUpdate(po.java:777)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)\ncom.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)\ncom.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)\ncom.ibm.icm.ci.workspace.impl.PDeleteWorkspaceImpl.deleteWorkspace(PDeleteWorkspaceImpl.java:84) com.ibm.icm.ci.workspace.impl.WorkspaceService.deleteWorkspace(WorkspaceService.java:270) com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:808)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)\ncom.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)\ncom.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)\ncom.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)\n....\n\n\nRESOLVING THE PROBLEM\n1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \n\n2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example) \n\nNote: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.\n\nRELATED INFORMATION\n#Transaction settings [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.doc\/info\/ae\/ae\/tjta_settlog.html]\nPI04872 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI04872]\nSetting Resource Environment Provider custom properties [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Setting_service_configuration_properties_wp8]"}]},{"id":"TRAIN_Q019","question":"i cannot enter SPSS statistics trial program\n\n\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","is_impossible":false,"contexts":[{"filename":"swg22001418.txt","text":"Title: IBM FAQ for IBM SPSS Statistics Subscription - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n FAQ for IBM SPSS Statistics Subscription \n\nANSWER\nQ. How to I cancel the auto-renewal of my IBM SPSS Statistics Subscription? \nA. Auto-renewal will be available a few days after your subscription starts. Please check back after a few days to change your subscription level. Changes to auto-renewal will take affect at the end of the month long subscription period. \n\nQ. I have installed the Subscription and when I attempt to login all I get is a big white screen. How do I get my subscription started?\nA. The most likely cause of this issue is installation of the 32bit IBM SPSS Statistics Subscription software on a 64bit machine. To fix the issue, please uninstall the 32bit and download and install the 64bit application from your Products & Services window on IBM.com. If you find that this does not resolve your issue, you have a new issue. Please open a Service Request using the Client Support Portal: http:\/\/ibm.biz\/IBMClientSuccessPortal [http:\/\/ibm.biz\/IBMClientSuccessPortal]."}]},{"id":"TRAIN_Q020","question":"HATS Plugin Download\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg24035040.txt","text":"Title: IBM Rational Host Access Transformation Services 9.0 - United States\n\nText:\nservice release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES\n\nABSTRACT\n IBM Rational Host Access Transformation Services 9.0 has been made generally available and contains fixes to version 9.0. \n\nDOWNLOAD DESCRIPTION\n \n\nTable of Contents Sections Description * What's new\n\nThis section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable. * Impact assessment\n\nThis section provides information related to the impact of this release to allow you to assess how your environment may be affected. * Prerequisites\n\nThis section provides important information to review prior to the installation of this release. * Download package\n\nThis section provides the direct link to obtain the download package for installation in your environment. * Installation instructions\n\nThis section provides the installation instructions necessary to apply this release into your environment. * Known problems\n\nThis section contains a link to the known problems (open defects) identified at the time of this release. Supporting Documentation Document Description * Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27011794]\n\nClick to review the detailed system requirements information for a complete list of hardware requirements, supported operating systems, prerequisites and optional supported software, with component-level details and operating system restrictions. * Information Center [http:\/\/pic.dhe.ibm.com\/infocenter\/hatshelp\/v90\/index.jsp]\n\nThe information center provides you with user assistance for the product. You can view, browse, and search online information related to the product. You can also visit IBM Product information [http:\/\/www.ibm.com\/support\/publications\/us\/library\/index.shtml#letter_R] page to browse for additional information centers. * Fix List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27027491]\n\nClick to review a complete list of the defects (APARs) resolved in this release including a list of resolved defects for the entire version family. PREREQUISITES\n IBM Installation Manager, Version 1.6.3.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27025142] or later is required to install HATS 9.0.\n\nINSTALLATION INSTRUCTIONS\n For installation instructions, see Installing HATS [http:\/\/pic.dhe.ibm.com\/infocenter\/hatshelp\/v90\/topic\/com.ibm.hats.doc\/doc\/gsinstal.htm] in the Rational Host Access Transformation Services (HATS) V9.0 Information Center.\n\nDOWNLOAD PACKAGE\n \n\nDownload options Access type Description Passport Advantage [https:\/\/www.ibm.com\/software\/howtobuy\/softwareandservices\/passportadvantage] Passport Advantage and Passport Advantage Express clients are required to sign in to download the software package. IBM OEM software [https:\/\/www.ibm.com\/software\/howtobuy\/softwareandservices\/oem] IBM Software Group OEM offerings are designed for partners who develop and sell business solutions with embedded or bundled IBM middleware software. Clients with Flexible Contract Type (FCT) license purchases and IBM Business Partners must sign in to download the software package. HOW CRITICAL IS THIS FIX?\n \n\nImpact Assessment Impact Description Recommended This release is a service release of Rational Host Access Transformation Services 9.0. It contains new features as well as fixes for client-reported and internally found defects. PROBLEMS SOLVED\n Click the Fix List link in the table of contents above to review a list of the problems solved in this release.\n\nKNOWN SIDE EFFECTS\n The following defects were not resolved in this release. \n\nAPAR Description IC94113 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IC94113] DBCS characters behind DDS window border are garbled. IC94307 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IC94307] Rich client: Part of DBCS fixed character is damaged. \nFor up-to-date information about known issues and workarounds, see Rational Host Access Transformation Service 9.0 - Known issues and workarounds [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038663]. \nCHANGE HISTORY\n For what's new in HATS 9.0, see the Rational Host Access Transformation Services (HATS) V9.0 Information Center [http:\/\/pic.dhe.ibm.com\/infocenter\/hatshelp\/v90\/index.jsp]. \n\n \n\nBack to top\n\n\nTECHNICAL SUPPORT\n \n\nTAB NAVIGATION\n * General Support Information- selected tab,\n * Support Resources [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27020747]- selected tab,\n\n\n\n\nIBM Rational Software Support Communities \n\n * Visit the IBM Support Portal [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Rational\/product] to configure your support portal experience and review FAQs, lists of known problems, fixes, and a wealth of important support information.\n \n \n * Visit developerWorks [http:\/\/www.ibm.com\/developerworks\/rational\/] to access an online collection of tutorials, sample code, standards, forums and other resources provided by experts at IBM to assist software developers using Rational tools including access to the IBM RFE Community [http:\/\/www.ibm.com\/developerworks\/rfe\/].\n \n \n * Visit the Jazz Community [http:\/\/jazz.net\/] if you use a Rational product created using the Jazz platform to interact directly with the Jazz development team and other community members, download product trials and betas and track developement progress. \n\n\n\n\nHELPFUL HINTS FOR OBTAINING TECHNICAL ASSISTANCE:\nBefore you contact IBM Rational Software Support, gather the background information that you need to describe the problem. When you describe a problem to an IBM software support specialist, be as specific as possible and include all relevant background information so that the specialist can help you solve the problem efficiently. To save time, know the answers to these questions: \n\n * What software versions were you running when the problem occurred? \n * Do you have logs, traces, or messages that are related to the problem? \n * Can you reproduce the problem? If so, what steps do you take to reproduce it? \n * Is there a workaround for the problem? If so, be prepared to describe the workaround. \n\nIf you have helpful information to diagnose or identify the problem on your system, you can provide this data by following the instructions to exchange information with IBM Technical Support [http:\/\/www.ibm.com\/software\/support\/exchangeinfo.html]. \n\n \n\nFollow IBM Rational Client Support on Twitter [http:\/\/twitter.com\/rationalsupport] | Facebook [http:\/\/facebook.com\/rationalsupport] | YouTube [http:\/\/www.youtube.com\/ibmrationalsupport] | devWorks Blog [https:\/\/www.ibm.com\/developerworks\/mydeveloperworks\/blogs\/nfrsblog\/?lang=en]\n\n\n\n\n Back to top \n\n [\/support\/docview.wss?uid=swg24035040&aid=1]Problems (APARS) fixed [\/support\/docview.wss?uid=swg24035040&aid=2]Problems (APARS) fixed\nIC87102, IC87488, IC87959, IC88940, IC88981, IC89933, IC91191, IC91370, IC91420, IC92195"}]},{"id":"TRAIN_Q021","question":"Help with Action required for Hypervisor Edition of IIB V9.0 and WMB V8.0 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. Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q022","question":"Why is an error seen while running run-svrssl-config?\n\nFollowing error is seen while running run-svrssl-config ConfigEngine task:\n action-run-pdjrte-config-zos-wp.ac.impl: \n [validateHost] Validating hostname(s) in the following argument: tam001:7136:1,tam002:7136:2\n [echo] Command to run is: java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ****** -appsvr_id myAppSvr -port 7223 -mode remote -policysvr\n tam001:7135:1,tam002:7135:2 -authzsvr tam001:7136:1,tam002:7136:2 -cfg_file \/opt\/WebSphere\/AppServer\/tivoli\/tam\/PdPerm.properties -key_file \/opt\/WebSphere\/AppServer\/tivoli\/tam\/pdperm.ks\n [java] Executing java with empty input string\n [java] Exception in thread \"main\"\n [java] [\n [java] HPDMG0759W The user name already exists in the registry.\n [java] ]\n [java] at com.tivoli.pd.jutil.ob.a(ob.java:40)\n [java] at com.tivoli.pd.jutil.ob.a(ob.java:66)","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q023","question":"Help with Action required for IIB H.E. V9 and WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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\nThis is related to CVE-IDs:\nCVE-2017-5715\nCVE-2017-5753\nCVE-2017-5754\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q024","question":"How do I transfer my SPSS 24 license key to a new computer?\n\nI need to transfer my SPSS 24 license key to a new computer. I was able to download IBM\u00ae SPSS\u00ae 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.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q025","question":"We are experiencing issues after we cleared the \/tmp\/javasharedresources location and restarted the jvm.\n\n\n\nWe experienced an issue when we cleared the \/tmp\/javasharedresources location and restarted jvm. We found a behavior where our website is serving a blank page and also cache monitor is not reflecting the statistics.\n\nPlease help us to understand why we cannot clear the \/tmp\/javasharedresources ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q026","question":"Where can I find the ITM VMware VI Agent Reports package for v 7.2?\n\n\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","is_impossible":false,"contexts":[{"filename":"swg24039229.txt","text":"Title: IBM Monitoring for Virtual Environments: VMware VI 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This is an Interim Fix for IBM Tivoli Monitoring for Virtual Environments: VMware VI 7.2 Fix Pack 2 reports \n\nDOWNLOAD DESCRIPTION\n(C) Copyright International Business Machines Corporation 2015. \n\n\n All rights reserved.\n\nComponent: IBM(R) Tivoli(R) Monitoring for Virtual Environments: VMware VI\nAgent TCR Reports, Version 7.2 Fix Pack 2\n\nComponent ID: 5724L92AG\n\nInterim Fix: 0001, 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001\n\nDate: January 23, 2015\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Copyright and trademark information\n10.0 Notices\n\n\n1.0 General description\n-----------------------\n\nThis interim fix resolves the APARs and defects listed in the\n\"Problems Fixed\" section below. \n\n\n2.0 Problems fixed\n------------------\n\nThe following problems are addressed by this fix.\n\n2.1 APARs\n---------------\nNone.\n\n2.2 Defects\n-----------\nDefect: 210286\nAbstract: Update model for VM PARTITION\nAdditional information: For \"Free_Space\" and \"Used_Space\" attributes, the\ndefault aggregation is defined not as AVG but as SUM. It usually\nworks as expected but if there were two entries which have same\n\"Timestamp\", the \"VM_PARTITION\" attribute group's data is shown\nwith doubled values.\nDefect: 212729\nAbstract: Drill through feature is not working in VE 7.2 FP2 reports\nAdditional information: A few VMware VI reports are showing the following\nmessage, when we try drill through by clicking on report chart:\nRSV-CM-0005 Content Manager did not return an object for the\nrequested search path.\nDefect: 212776\nAbstract: Datacenter parameter\/prompt is missing in a few VM reports\nAdditional information: The Datacenter parameter\/prompt is missing in the\nfollowing VMware VI reports: VM Heat Chart, Bottom N VMs by\nResource Pool and Top N VMs By Resource Pool.\nDefect: 212851\nAbstract: Place Date range parameter after the Resource prompts\nAdditional information: A few VMware VI reports contain time selection over\nresource selection. Therefore to make uniformity across the reports,\nplace Date range parameter after the resource prompts (like Data\nCenter and Cluster).\nDefect: 212924\nAbstract: Unsorted resources e.g.Cluster on parameter selection page\nAdditional information: Most of the VMware VI reports sometimes display \nunsorted resources (viz. Data Center, Cluster, Host Servers, VMs\netc.) on parameter selection (aka prompt) page.\nDefect: 212925\nAbstract: Incorrect caption\/label for Host Server resource parameter\nAdditional information: Incorrect caption\/label for the resource parameter\ne.g. In Network usage by VMs report, the \"Host Server(s)\" drop\ndown list title needs to be corrected as \"Host Server\" as user\ncan select only one host in this report.\n\n2.3 Enhancements\n------------------\nFeature: 210245\nAbstract: Enhance model to add SAMPLES.\nAdditional information: Add SAMPLES query item\/column for each summarized\nattribute group view (viz. Hourly, Daily, Weekly and Monthly)\nin existing VMware VI Agent reports data model.\nFeature: 213018\nAbstract: RFE 60331: Require a new report for Cluster Utilization Details\nAdditional information: Require a new cluster level report like the Host \nServer Utilization Details report, which is useful and included the\nactual data points from the graph at the bottom of the report.\nDefect: 213084\nAbstract: Provide a choice to select date range or start & end week\nAdditional information: Provide a parameter choice (aka date filter option)\nto either select date range or start and end week of the year in\nthe following VMware VI reports: Cluster Weekly Comparison and\nHost Servers Weekly Comparison.\n\n2.4 Superseded fixes\n---------------------\nNone.\n\n2.5 APARs and defects included from superseded fixes\n---------------------------------------------------------------\nNone.\n\n\n3.0 Architecture and prerequisites\n----------------------------------\n\nThis fix is supported on all operating systems listed in the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2. See chapter 9 for information on the Tivoli\nCommon Reporting.\n\nThe User's Guide is here:\n\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SS9U76_7.2.0.2\/com.ibm.tivoli.itmvs.doc_7.2.0.2\/vedrcp72fp2_user.pdf [http:\/\/www.ibm.com\/support\/knowledgecenter\/SS9U76_7.2.0.2\/com.ibm.tivoli.itmvs.doc_7.2.0.2\/vedrcp72fp2_user.pdf]\n\nPlease refer to the IBM Software Product Compatability Reports (SPCR)\nfor the latest operating system certification information:\nhttp:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity\/index.html [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity\/index.html] \n\n3.1 Prerequisites for this fix\n------------------------------\n\nThe prerequisite level for this fix is defined in Chapter 9 of the IBM Tivoli\nMonitoring for Virtual Environments: Dashboard, Reporting, and Capacity Planning\nUser's Guide, version 7.2 Fix Pack 2.\n\n\n4.0 Image directory content\n---------------------------\n\nThis fix image contains the following files:\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.README - This README file\n- 7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip - Fix archive .zip format.\n\nThe fix archive file contains the following directories and files,\nwhich is the same as the format found in the reports directory\nof the IBM Tivoli Monitoring for Virtual Environments V7.2 Fix Pack 2\nDashboards, Capacity Planner and Reports (TMVE), Multilingual media \nas found on Passport Advantage:\n- gui\n- lib\n- model\n- reports\n- scripts\n- setup_aix.bin\n- setup_hpux.bin\n- setup_linux.bin\n- setup_solaris.bin\n- setup_windows.exe\n- silent_installer.properties\n- tcr_install.properties\n\nNote that this Interim Fix is a complete replacement of these\nfiles.\n\n5.0 Installation instructions\n-----------------------------\nThis fix can be installed over an existing installation or as\na new install. Expand the archive file, \n7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001.zip, and copy the files in any\nlocation on the same computer where the Tivoli Common Reporting \nserver is installed.\n\nUse the following procedure to import reports that are bundled by using\nthe report installer:\n1. From the \\7.2.0.2-TIV-ITM_VMWVI_RPT-IF0001 directory on the product file, run the \ncommand appropriate for your operating system:\n\u2022 setup_aix.bin (for AIX)\n\u2022 setup_hpux.bin (for HP-UX)\n\u2022 setup_linux.bin (for Linux)\n\u2022 setup_solaris.bin (for Solaris)\n\u2022 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\u2022 In the Enter the database username field, enter the administrator user name.\n\u2022 In the Enter the user password field, enter the password.\n\u2022 In the Choose the database type list, select the database type.\n\u2022 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\u2022 For DB2 database, required driver files are db2jcc.jar and db2jcc_license_cu.jar \n(Note: JDBC credentials must have db2admin privileges.)\n\u2022 For Oracle database, required driver file is oraclethin.jar\n\u2022 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] [ ]"}]},{"id":"TRAIN_Q027","question":"Why are we not able to create new pages using the Manage Pages Portlet?\n\nWe are using Portal 8.5 on Windows,\n\nFrom WebSphere Portal Administration console. we go to \u2018Manage Pages\u2019- > Select \u2018Content root\u2019 item from table -> \u2018New Page\u2019 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.","is_impossible":false,"contexts":[{"filename":"swg21611699.txt","text":"Title: IBM JDBC driver or database insufficiencies cause administration portlets to fail. - United States\n\nText:\nRT0002E; JDBC; database; driver; RepositoryException; PLS; EJPAS0017E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nYou attempt to create a new page via the Manage Pages portlet or add a portlet to a page via the Edit Layout portlet and encounter an error.\n\nSYMPTOM\nSystemOut.log contains:\n... DefaultTransa E Message: Could not save object in repository., \nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\ncom.ibm.workplace.wcm.services.repository.RepositoryException: \nMessage: Could not save object in repository., Cause: javax.jcr.RepositoryException: RT0002E: Error while calling a function createItems of PLS data manager\n...\nCaused by: com.ibm.icm.da.DBAccessException:\njava.sql.SQLFeatureNotSupportedException:DSRA1300E: Feature is not implemented: PreparedStatement.setBinaryStream\nat com.ibm.icm.da.portable.data.WideTableData.changeItems(WideTableData.java:857) \n\n \n\nThe client browser displays: \n\n\nEJPAS0017E ... Message: Could not save object in repository.,\nCause: javax.jcr.RepositoryException: RT0002E: Error while calling a\nfunction createItems of PLS data ...\n\nor:\n\nEJPAE0015E: Failed to add new portlets.\n...\nEJPEC0002E: The transaction has been set to rollback state...\n\n\nCAUSE\nThe JDBC driver does not meet WebSphere Portal v8's prerequisites.\n\n\nDIAGNOSING THE PROBLEM\nCheck SystemOut.log for the database server version and JDBC driver version: \n\n\nDSRA8204I: Database product version : ...\nInternalGener I DSRA8205I: JDBC driver name : ...\nInternalGener I DSRA8206I: JDBC driver version : ...\n\nCompare these to WebSphere Portal v8's prerequisites. Refer to the WebSphere Portal V8.0 detailed system requirements link below.\n\n\nRESOLVING THE PROBLEM\nIf the database server and\/or JDBC driver do not meet WebSphere Portal v8's prerequisites, upgrade or downgrade the component(s) to the appropriate supported level(s) and restart the Portal server(s). \n\n \n\nIf upgrading the JDBC driver requires replacing the .jar with another differently named .jar, other components in the system that referenced the older .jar may be affected. Pay special consideration to: \n\n\nWAS Integrated Solutions Console > Environment > WebSphere Variables\nVMM_JDBC_CLASSPATH\nORACLE_JDBC_DRIVER_PATH\n\nThese are stored in: \/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]"}]},{"id":"TRAIN_Q028","question":"Help with Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22011689.txt","text":"Title: IBM Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The DiskFileItem class in Apache Commons Fileupload before version 1.3.3, used in IBM WebSphere MQ File Transfer Edition, specifically the Web Gateway component, could allow remote attackers to execute arbitrary code under the context of the current process, causing an undefined behavior. \n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2016-1000031 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION:Apache Commons FileUpload, used in IBM WebSphere MQ File Transfer Edition, could allow deserialization of untrusted data in the DiskFileItem class of the FileUpload library. A remote attacker could exploit this vulnerability to execute arbitrary code under the context of the current process.\nCVSS Base Score: 9.8\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/117957 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/117957]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:N\/S:U\/C:H\/I:H\/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM WebSphere MQ File Transfer Edition v7.0.0 \n\nIBM WebSphere MQ File Transfer Edition v7.0.1 \n\nIBM WebSphere MQ File Transfer Edition v7.0.2 \n\nIBM WebSphere MQ File Transfer Edition v7.0.3 \n\nIBM WebSphere MQ File Transfer Edition v7.0.4\n\nREMEDIATION\/FIXES\nAll affected product versions are already End of Support. Customers must contact IBM to obtain a fix for the affected release.\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nCHANGE HISTORY\n 22 Dec 2017 Original Version \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"TRAIN_Q029","question":"TWS \/ DWC and WebSphere 8.5.5.4+\n\nWebSphere 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","is_impossible":false,"contexts":[{"filename":"swg21964202.txt","text":"Title: IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States\n\nText:\ndwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2) \n\nSYMPTOM\nUnable to connect to TWS 8.5.1 ,8.6 or 9.1\/9.2 from DWC 9.3. \n\nCheck the WAS SystemOut.log for error :\n\nSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3, \nbut that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.\n\n\nCAUSE\nDWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect\n\n\nRESOLVING THE PROBLEM\nYou can solve this problem by configuring your TWS engines to use TLS instead of SSL :\n\n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/config\/cells\/TWSNodeCell\/security.xml \n\nFind sslProtocol and change \"SSL_TLS\" to \"TLS\" \n\nFind ssl.protocol and change value=\"SSL\" to value=\"TLS\" \n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/properties\/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/temp\/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nStop and restart WAS. \n\n*Be aware that your Engines are now using TLS and so you must also reconfigure any DWC 9.2 or 9.1 installations that need to connect to those engines. You would change them to use TLS in the same way as above but also by the same changes in these copies of security.xml and ssl.client.props : \n\nTWA_HOME\/JazzSM\/profile\/config\/cells\/JazzSMNode01Cell\/security.xml \n\nTWA_HOME\/JazzSM\/profile\/properties\/ssl.client.props \n\nTWA_HOME\/JazzSM\/profile\/temp\/ssl.client.props \n\nPlease consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted. \n\nSee technote 1689332."}]},{"id":"TRAIN_Q030","question":"Does DataPower support SHA-2?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21406783.txt","text":"Title: IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States\n\nText:\nDatapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2"}]},{"id":"TRAIN_Q031","question":"Request fails with \"non idempotent request method - RFC 2616 sec 10.3. \"\n\nWhen 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\".","is_impossible":false,"contexts":[{"filename":"swg21318593.txt","text":"Title: IBM Handling 302 redirect error message in a Web Application Firewall - United States\n\nText:\nHTTP; Redirect; 302; non idempotent TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DataPower is preventing POST based HTTP redirect in accordance with RFC and displays this as part of the error in the logs:\n\nRedirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) \n\nSYMPTOM\nThis technote pertains to the following errors. \n\nExample 1: This example shows the service getting the following message: a Backside header failed to parse due to: Failed to establish a backside connection with a HTTP Redirect and failed due to non idempotent request method. (RFC 2616 sec 10.3) message.\n\nweb-application-firewall (CookieEncrypt): Backside header failed to \nparse due to: Failed to establish a backside connection \n12:20:53 webapp-firewall warn 60452 10.176.3.97 HTTP Redirect from \n'http:\/\/10.176.3.97:8080\/cgi-bin\/WebObjects.exe\/IndvGate.woa\/5\/wo\/2jHo28 \nQYOlhC2RZ1XQ15DE5OKo8\/0.1.2.27.3.SecureSignOn.1' failed due to non \nidempotent request method. (RFC 2616 sec 10.3)\n\nExample 2: This example shows an HTTP response code 302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.\n\nWed May 21 2008 10:39:11 [mpgw][info] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP response code 302 for \n'http:\/\/9.65.237.170:8080\/forum\/ucplogin.php?mode=login' \nWed May 21 2008 10:39:11 [mpgw][warn] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: HTTP Redirect from \n'http:\/\/9.65.237.170:8080\/forum\/ucplogin.php?mode=login' failed due to\nnon idempotent request method - RFC 2616 sec 10.3. \nWed May 21 2008 10:39:11 [mpgw][error] mpgw(ECP-MPGW): \ntid(369602)[9.65.237.170]: Backside header failed to parse due to: \nFailed to establish a backside connection\n\n\nCAUSE\n302,HTTP Redirect and failed due to non idempotent request method - RFC 2616 sec 10.3 message.\n\nThis is caused by the adherence to the HTTP RFC 2616 by the Datapower Appliance. \nFor additional information on the RFC you may see this page RFC2616 [http:\/\/www.w3.org\/Protocols\/rfc2616\/rfc2616.html]\n\n\nENVIRONMENT\nWebSphere DataPower XI50 and XS40\n\n\n\nDIAGNOSING THE PROBLEM\nBackside header failed to parse due to: Failed to establish a backside connection failed due to non idempotent request method. (RFC 2616 sec 10.3)\n\n\n\nRESOLVING THE PROBLEM\nTo resolve the issue, the IBM WebSphere DataPower SOA appliance web application firewall can be configured to handle these \"302 Redirects\". Follow the steps outlined in the attached document that explain how to configure a web application firewall to handle the redirects using the attached ResetLocation.xsl stylesheet. With the specified edit for your environment, this file will handle most simple use cases and may also be edited to handle any additional requirements for your specific business solution.\n\nsampleForRedirects.doc [\/support\/docview.wss?uid=swg21318593&aid=2] [\/support\/docview.wss?uid=swg21318593&aid=1]ResetLocation.xsl [\/support\/docview.wss?uid=swg21318593&aid=4] [\/support\/docview.wss?uid=swg21318593&aid=3]\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower XML Security Gateway XS40 Not Applicable Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent Business Integration WebSphere DataPower SOA Appliances General Firmware 4.0.1, 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent"}]},{"id":"TRAIN_Q032","question":"WCM User can not access authorized content with this exception in SystemOut.log: com.ibm.icm.jcr.access.AccessDeniedException\n\nWCM User can not access authorized content with this exception in SystemOut.log: com.ibm.icm.jcr.access.AccessDeniedException","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q033","question":"Scheduled reports fail after changing password\n\nScheduled 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.","is_impossible":false,"contexts":[{"filename":"swg21591076.txt","text":"Title: IBM Automatically renew trusted credential - United States\n\nText:\nsecurity; trusted credentials SSO renew TECHNOTE (FAQ)\n\nQUESTION\n How do I choose the value to use for the Security > Authentication > Automatically renew trusted credential setting? \n\nANSWER\nFor IBM Cognos Business Intelligence(BI) deployments that do not implement a single sign-on (SSO) solution, stored credentials used for running scheduled activities can be automatically updated. When a user logs into the IBM Cognos BI application with a user name and password, the trusted credential used to run schedules when not logged in will be refreshed as well. This removes the burden from the end user of having to remember to manually refresh their trusted credentials and may eliminate failed activities caused by changed or expired user credentials.\nThe credential refresh behaviour is controlled by the Security > Authentication > Automatically renew trusted credential setting in Cognos Configuration.\n\n\n * Primary namespace only (default setting): When you log on to the first namespace of your session, if you have trusted credentials for that account, the credentials are updated for the primary account only. All other credentials for other namespaces are not updated.\n \n * Off: Credentials are not updated in any namespace.\n \n * All namespaces: When you log on to the first namespace, your credentials are updated as described for \"Primary namespace only\". When you log on to additional namespaces, if your trusted credentials associated with the primary account contain logon information for that namespace, then those trusted credentials are updated. NOTE: Do not use the All namespaces option if users authenticate into secondary namespaces as different users.\n\n\nA user's trusted credentials for a namespace will only be renewed once per day. \n\nIt is NOT possible to use SSO with the feature 'Automatically Renew Trusted Credentials' found in Cognos BI. The reason for this is due to the following: \n\n\"A trusted credential is special because the namespace credentials it stores must be usable at any time, not depending on any timestamp. This rules out SSO tickets like Kerberos tokens or SAP tokens as they will expire after a short time and will become unusable. A suitable trusted credential therefore usually is a pair consisting of a user name and a password. However, for SSO based authentication to IBM Cognos BI, there is no password available to the namespace that can be stored into the trusted credential. Therefore, this feature will only work for basic authentication, when the user provides a user name and password to the login screen.\" RELATED INFORMATION\n Proven Practices: Securing the IBM Cognos 10 BI Environ [http:\/\/www.ibm.com\/developerworks\/data\/library\/cognos\/security\/cognos_bi_platform\/page602.html]\nCognos Analytics 11 Equivalent Technote [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21998776]"}]},{"id":"TRAIN_Q034","question":"ITNM 4.2 Fix Pack 3 link and build number?.\n\nITNM 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","is_impossible":false,"contexts":[{"filename":"swg24043575.txt","text":"Title: IBM Tivoli Network Manager IP Edition 4.2.0 Fix Pack 3, 4.2.0-TIV-ITNMIP-FP0003 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This fix pack is a cumulative fix release and addresses several APARs and internally found issues since the release of Tivoli Network Manager IP Edition 4.2.0 Fix Pack 2. \n\nDOWNLOAD DESCRIPTION\nWHAT'S NEW: [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__descriptio]\n\n\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__descriptio [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__descriptio]n\n\nSummary of the Enhancements included in this Fix Pack:\nThe following features and functions are introduced in Fix Pack 3.\n\nSupport for SLES 12.0 \n\n * \n\n\nSupport for DB2 version 11.1 * \n\n\nSupport for IBM zLinux Systems * \n * Red Hat Enterprise zLinux Server 7.3 (s390x, 64 bit) SuSE zLinux Enterprise Server (SLES) 12.0 SP1(s390x,64 bit) \n * \n * \n * \n * \n * https:\/\/www.ibm.com\/software\/passportadvantage\/pao_customer.html\n * \n\n\nOffline geographical maps * \n\n\nCustom geographical map layers * \n\n\nRegional aggregation for geographical maps * \n\n\nBefore installing or upgrading Network Manager, refer to the Fix Pack Release notes: \nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html] \n\n\n===================================================================== \nSummary of fixes in V4.2.0 Fix Pack 3 \n===================================================================== \nFor details of an individual APAR, go to www.ibm.com\/support [www.ibm.com\/support] then enter the APAR name\/# in \"Search Support\" then select search. \n\n\nIV89573 EXPAT XML PARSER VULNERABILITIES IV90563 DELAY RCA REPROCESSING UPON SEEING CLEAR FOR ROOTCAUSE ALERT IV90626 CISCO WEBTOOLS SEND EMPTY EMAIL IV90807 SLOW PROCESSING IN STITCHER SWITCHFDBTOCONNECTIONS IV91086 THE DISCOVERY PROCESSES CANNOT BE STARTED FROM THE ITNM GUI WHEN ITNM IS INSTALLED IN A MASTER\/SLAVE SETUP IV91094 IP Filtered view incorrectly skips links between non-matched interfaces IV91222 COLLAPSING A SUBGRAPH LEAVES THE NODES AN UNUSABLE DISTANCE FROM EACH OTHER. IV91592 TELLABS JAVA COLLECTOR TO DISPLAY CARD NAMES. IV91725 TIMER THREADS ARE NOT TIMELY GARBAGE COLLECTED IN THE STRUCTURE BROWSER TREE. IV92191 Huawei MPLSTelnet parse the recent 'display ip vpn-instance verbose' format incorrectly. This result in incorrect association of VPN Name and the respective interface IV92353 POLLER CORES STARTING SNMP POLICIES WITH ENTITIES IN SCOPE THAT HAVE NO IFNAME IV92982 RCA PLUGIN SGMENTATION FAULT OVER SMALLER NUMBER OF CHANGES IV93054 ITNM DEVICESTRUCTURE - INFERFACE EVENTS NOT INCLUDED IV93591 NO DATA BEING DISPLAYED ON TOP N PERFORMERS WIDGET IN THE NETWORK HEALTH DASHBOARD IV94005 DYNAMIC DISTINCT NETWORK VIEW CREATES EXTRA\/DUPLICATE VIEWS. IV94658 LOCAL TYPE TOOLS FOR CONTEXT MENU IS NOT SUPPORTED BY ITNM 4.2 \n\n\n\nKnown problems with V4.2.0 Fix Pack 3 \nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html#relnotes__problems [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html#relnotes__problems] PREREQUISITES\nPrerequisites and Installation Instructions \n\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_installing.html [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_installing.html]\n\nINSTALLATION INSTRUCTIONS\nIBM TIVOLI NETWORK MANAGER IP EDITION V4.2.0 FIX PACK 3\n=======================================================\n\nBuild 4.2.0.34\nThis document describes the known problems and APAR fixes for Network Manager V4.2.0 Fix Pack 3.\n\nCopyright IBM Corporation 2017\n\n\n1 WHAT'S NEW\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__description [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__description]\n\n2 INSTALLATION\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_installing.html [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_installing.html]\n\n3 POSTINSTALLATION AND CONFIGURATION\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_postinstallationtaskssummary.html [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/install\/task\/nmip_ins_postinstallationtaskssummary.html]\n\n4 KNOWN PROBLEMS AND LIMITATIONS\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__problems [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__problems]\n\n5 SUMMARY OF APAR FIXES IN NETWORK MANAGER V4.2.0 FIX PACK 3\nSee http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__apar-fixes [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSSHRK_4.2.0\/itnm\/ip\/wip\/relnotes\/reference\/nmip_rn.html?view=kc#relnotes__apar-fixes]\n\nURL LANGUAGE SIZE(Bytes) 4.2.0_README_FP0003 [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0_README_FP0003&source=SAR] English 7178 \nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https:\/\/www.ibm.com\/support\/fixcentral\/help?page=swfaqs] 4.2.0-TIV-ITNMIP-AIX-FP0003 28 Apr 2017 Language Independent 3091689671 FC [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-ITNMIP-Linux-FP0003 28 Apr 2017 Language Independent 3091689662 FC [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-ITNMIP-Linux-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-AIX-FP0003 28 Apr 2017 Language Independent 27899824 FC [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-AIX-FP0003&source=SAR] [ ] 4.2.0-TIV-NOIHD-Linux-FP0003 28 Apr 2017 Language Independent 27899818 FC [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FTivoli%2FTivoli+Network+Manager+IP+Edition&fixids=4.2.0-TIV-NOIHD-Linux-FP0003&source=SAR] [ ]"}]},{"id":"TRAIN_Q035","question":"DataPower remote log targets, tracking efficieny\n\nHow can I track the efficiency of my log target (remote endpoint)? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q036","question":"Why are not seeing data for our APMV8 AIX OS agent on AIX 7.1.x?\n\nWe are not seeing any data for our APMV8 AIX OS agent in the APM\/UI. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q037","question":"How can multiple TDWC users logon into TDWC with same TWS user id?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21576245.txt","text":"Title: IBM Tivoli Integrated portal enabling multiple logins using same user Id - United States\n\nText:\nTIPL2SEC tivoli integrated portal multiple logins TECHNOTE (FAQ)\n\nQUESTION\n How can I login to TIP from different machines using same user Id? \n\nCAUSE\nNeed to login with multiple times with same user\n\nANSWER\nOnly TIP version 2.1 and higher support multiple logins using same user Id. \n\nFollow below steps to configure Tivoli Integrated Portal to allow multiple users to log in using the same user Id and password. \n\n1. Log in as an administrative user. \n\n2. Navigate to: \n\ntip_home_dir\/profiles\/TIPProfile\/config\/cells\/TIPCell\/applications\/isc.ear\/deployments\/isc\/isclite.war\/WEB-INF\/ \n\n3. Edit consoleProperties.xml. \n\n4. Locate the property with a id attribute of ENABLE.CONCURRENT.LOGIN and set its value to true. \n\n5. Save the file and exit from the text editor. \n\n6. Restart TIP server."}]},{"id":"TRAIN_Q038","question":"We want to backout the Cognos component of Business Monitor to a previous version. What do we have to take care of?\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21341204.txt","text":"Title: IBM How to Rollback From a Fix Pack or Interim Fix to an Earlier Build - United States\n\nText:\nuninstall; revert; downgrade; hotsite; HS; out; fixpack TECHNOTE (FAQ)\n\nQUESTION\n There may be times when there is a need to remove a previously installed Fix Pack or Interim Fix (hotsite) and revert to the original installed version. This document describes how to roll back an installed Fix Pack or Interim Fix applied to Cognos BI. \n\nANSWER\nAssuming create backup was selected, there will be a folder with the backup under the uninstall directory. Use these files to roll back. In version 10.2.1 FP1 and above there is no option to create a backup, instead backups are automatically created in the \/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"}]},{"id":"TRAIN_Q039","question":"How to remove the default -Xcompressedrefs from my WebSphere Application Server\n\nMy 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.","is_impossible":false,"contexts":[{"filename":"swg21660890.txt","text":"Title: IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n \"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/understanding\/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z\/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work. \n\n\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor\/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\" ~IBM Java Development Team \n\nIf the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors\/Locks. If these Class Pointers, Monitors\/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http:\/\/www.ibm.com\/developerworks\/library\/j-nativememory-linux\/] will be thrown. \nANSWER\nWhy Use Compressed References? \n\nBelow the 4GB mark, the JVM does not have to perform any compression\/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors\/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert the \"start\" address from the hex value to a GB value [http:\/\/ss64.com\/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.\n\n\n\n * [\/support\/docview.wss?uid=swg21660890&aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase \n\nStarting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IV37797]). \n\n\n\nNOTE: In IBM System z platforms (i.e. z\/OS and z\/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty \nassociated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below). \nSee related: IBM Knowledge Center - JVMJ9GC089W [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSYKE2_7.0.0\/com.ibm.java.messages\/diag\/appendixes\/messages\/j9gc\/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=
[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]"}]},{"id":"TRAIN_Q040","question":"Is it recommended to use symbolic links when installing Omnibus 8.1 fixpacks?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21628092.txt","text":"Title: IBM Installation Manager does not work if symbolic links are used for Installation Manager of installed product locations - United States\n\nText:\nRN1.5; RN1.5.1; RN1.5.0.1; RN1.5.2; RN1.5.3; RN1.6; RN1.6.1; RN1.6.2; RN1.6.3; RN1.6.3.1; RN1.7; RN1.7.1; RN1.7.2; SRX; 1628092; RATLC02668456; IPL; Symlink TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You install IBM Installation Manager by using symbolic links at the root level for the agent data location or the installation location or for both locations and after a system change or system restart you cannot start Installation Manager or you cannot use Installation Manager to update or uninstall products. \n\nCAUSE\nWhen you install Installation Manager, the values for the agent data directory, the Installation Manager binaries, and the installation directories for products are stored internally as absolute paths with all the symbolic links resolved. If a symbolic link is used as part of the path for any of these directories or binaries, the symbolic link is replaced with its target value.\nSimilarly, when a product is installed with Installation Manager, the values for the installation location and shared resources directory are stored internally as absolute paths with all symbolic links resolved. \n\nIf the symbolic links change their values, the absolute path names for directories that are used by Installation Manager might change. When the Installation Manager starts, it will initialize itself using the data in the agent data location. However, the stored values for the paths to the agent data directory, Installation Manager binaries, or product installation locations do not point to the new locations. Installation Manager might fail to start, or might be unable to update or uninstall products that are installed.\n\n\nRESOLVING THE PROBLEM\nWhen choosing locations for the agent data directory, the Installation Manager binaries, shared resources directory, and the installation directories for products, do not use paths that include symbolic links. \n\n\nIf Installation Manager is using paths that no longer exist, create the old paths manually and mount the affected file systems at the original locations that are used by Installation Manager. Verify that the user IDs for Installation Manager have read access to each level of the recreated paths."}]},{"id":"TRAIN_Q041","question":"Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22005055.txt","text":"Title: IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-5461) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-5461 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-5461]\nDESCRIPTION:Mozilla Firefox could allow a remote attacker to execute arbitrary code on the system, caused by an out-of-bounds write during Base64 decoding operation in the Network Security Services (NSS) library. By persuading a user to visit a specially-crafted website, a remote attacker could exploit this vulnerability using unknown attack vectors to execute arbitrary code on the vulnerable system or cause a denial of service.\nCVSS Base Score: 8.8\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125002 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125002]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:U\/C:H\/I:H\/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ Appliance 8.0 \n\nMaintenance levels between 8.0.0.0 and 8.0.0.6\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nContinuous delivery updates between 9.0.1 and 9.0.3\n\nREMEDIATION\/FIXES\nIBM MQ Appliance 8.0 \n\nApply fixpack 8.0.0.7 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+MQ+Appliance+M2000&release=8.0.0.6&platform=All&function=all]\nIBM MQ Appliance 9.0.x Continuous Delivery (CD) Release \n\nApply the ifix for APAR IT21888 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+MQ+Appliance+M2000&release=9.0.3&platform=All&function=all]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nCHANGE HISTORY\n 24 Aug 2017 Updated to include IBM MQ Appliance 9.0.x CD release\n14 Jul 2017 Original version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"TRAIN_Q042","question":"Non-admin users cannot access webDAV filestore. What is the likely reason?\n\nA 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\").","is_impossible":false,"contexts":[{"filename":"swg21664629.txt","text":"Title: IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States\n\nText:\nEJQAB0067E; WSP0005E; LoginException; policy; theme; attribute; JCR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPolicy (EJQAB0067E) and JCR Login (WSP0005E) exceptions occur in the System* logs when accessing Portal pages after user authentication.\n\nSYMPTOM\nSystemOut.log shows:\n\n[datestamp] 00000241 PolicyService E com.ibm.wps.policy.services.PolicyService getPolicy Exception calling storage api: com.ibm.portal.WpsException: EJQAB0067E: An error occurred while getting the policy root. \n[datestamp] 00000241 PolicyManager E com.ibm.wps.policy.services.PolicyManagerServerSideImpl getPVSByPath throwing exception. PVS type not found for theme\/SingleTopNav\n\nSystemErr.log shows:\n\n[datestamp] 00000241 SystemErr R javax.jcr.LoginException: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.\n....\n[datestamp] 00000241 SystemErr R Caused by: com.ibm.icm.da.DBAccessException: User id can not be null\n[datestamp] 00000241 SystemErr R at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:177)\n\n\nCAUSE\nAuthenticated user does not have the attribute defined in the backend user registry which matches the attribute defined in the store.puma_default.user.fbadefault.filter property in WP PumaStoreService Resource Environment Provider. Such attribute is used by JCR when querying for theme policy information.\n\nDIAGNOSING THE PROBLEM\nCollect the following: \n\n * LDIF export of a sample user that hits this problem (if the backend user registry is LDAP) * If you cannot determine a specific user causing the error, you can use the following tracestring to confirm:\n \n *=info:com.ibm.wps.policy.services.*=finest:com.ibm.wps.policy.commands.*=finest\n \n Then look for the following line in trace.log: com.ibm.wps.policy.services.PolicyService PolicyService() ENTRY userid contructor: {DN of user} \n \n \n * Resources.xml - can be found under * \/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]"}]},{"id":"TRAIN_Q043","question":"What is the equivalent of the .LG0 file for the OS agent - A4 - on i5 systems?\n\nWhat 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.","is_impossible":false,"contexts":[{"filename":"swg21657023.txt","text":"Title: IBM Pdcollect tool for ITM IBM i OS agent - United States\n\nText:\nITM_TEMA_DIST_CONFIGURATION ITM_i5_Agent 5724C04 A4 OS\/400 i5\/OS IBMi IBM i pdcollect TECHNOTE (FAQ)\n\nQUESTION\n How do I collect logs and files for the IBM i OS agent? \n\nANSWER\nThe pdcollect tool for the IBM i OS agent allows you to easily and quickly collect the most commonly used information from an IBM i system for IBM Support to investigate a problem. The tool gathers log files, configuration information, version information, job information, message queue information, and basic system information. \n\nPdcollect is delivered in the IBM i OS agent beginning in ITM 6.23 FP5 and ITM 6.30 FP3. It is located in the following IFS directory: \n\n\n\/QIBM\/ProdData\/IBM\/ITM\/bin\/pdcollect.sh\n\n\nPdcollect is also available as a downloadable file which is stored in an IFS directory chosen by the user. Download the following zip file to a local workstation and extract its contents. Follow the instructions in readme.txt for further information on installing the tool. \n\n pdcollect_ibmi_1.4.zip [\/support\/docview.wss?uid=swg21657023&aid=2]pdcollect_ibmi_1.4.zip [\/support\/docview.wss?uid=swg21657023&aid=1] \n\n The tool is executed by issuing the following shell script command in Qshell:\n\n\/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."}]},{"id":"TRAIN_Q044","question":"Authorization code missing for SPSS 25?\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q045","question":"Unable to add the document using content Navigator. We are getting the following error code. CIWEB1158.\n\nThe 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.","is_impossible":false,"contexts":[{"filename":"swg21598974.txt","text":"Title: IBM Insufficient Access Error adding documents to FileNet Content Engine - United States\n\nText:\nFNRCE0001E; E_ACCESS_DENIED; unable to add document TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n User is getting a security error when attempting to add a document to a folder in an object store via FileNet Workplace XT or FileNet Enterprise Manager.\n\n\nSecurity Error seen: The requester has insufficient access rights to perform the requested operation. \n\nCAUSE\nUser does not have Create_Instance right on the security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes and cannot create these objects when adding documents.\n\nDIAGNOSING THE PROBLEM\n\n\n\n * User has necessary rights to the document class, folders and object store but can't add document. \n * User does not have necessary Create_Instance rights on the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n * Error seen in the P8_server_error.log:\n \n YYYY-06-08T17:53:19.706Z 56005600 ENG FNRCE0001E - ERROR method name: checkUpdatePermissions principal name: username Global Transaction: true User Transaction: false Exception Info: The requester has insufficient access rights to perform the requested operation.\n com.filenet.api.exception.EngineRuntimeException: FNRCE0001E: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation. failedBatchItem=0 errorStack={\n \n\nRESOLVING THE PROBLEM\nSteps to resolve issue: \n\n 1. Log in to FileNet Enterprise Manager. \n 2. Grant the user CREATE_INSTANCE rights to the Security permission of the ReferentialContainmentRelationship and DynamicReferentialContainmentRelationship classes. \n 3. Re-try adding the document."}]},{"id":"TRAIN_Q046","question":"Does Linux KVM monitoring agent support CANDLEDATA function?\n\nDoes Linux KVM monitoring agent in ITM support CANDLEDATA function? ","answer":"The CANDLEDATA mechanism is available with ITM 6.30.05.00.","is_impossible":false,"contexts":[{"filename":"swg21695194.txt","text":"Title: IBM IV67523 Move local data from CANDLEHOME to another file system - United States\n\nText:\n6.30.05.00 CANDLEHOME CANDLEDATA itmCANDLEDATA.sh TECHNOTE (FAQ)\n\nQUESTION\n How do I move local data such as configuration files, log files, historical data, etc. from CANDLEHOME to a different file system? \n\nCAUSE\nSince its inception, IBM Tivoli Monitoring (ITM) has stored local data such as configuration files, log files, and historical data together with the installation files in CANDLEHOME. For example, ITM normally installs in a directory named \/opt\/IBM\/ITM. Within that directory, it stores programs in subdirectory names like \/opt\/IBM\/ITM\/bin and \/opt\/IBM\/ITM\/classes. It also stores local data in subdirectory names like \/opt\/IBM\/ITM\/config and \/opt\/IBM\/ITM\/logs. This homogeneous design is a problem for installations that require an approach that keeps code in \/opt and stores data in the \/var file system.\n\nANSWER\nIntroduction \n\nUnder APAR IV67523, ITM added a new mechanism to move local data to a different file system. For example, data typically stored in \/opt\/IBM\/ITM\/config and \/opt\/IBM\/ITM\/logs can be redirected to \/var\/IBM\/ITM\/config and \/var\/IBM\/ITM\/logs. This new file system location is designated by the user at installation time, and it is referred to as CANDLEDATA. A conversion utility is provided to implement CANDLEDATA for existing installations. \n\nThe CANDLEDATA mechanism is available with ITM 6.30.05.00. \n\n \n\n\n\n\n\n\nHow CANDLEDATA Works \n\nThe CANDLEDATA mechanism is implemented primarily using symbolic links. This means most of the underlying code in ITM is unaware of CANDLEDATA. This also means the CANDLEDATA mechanism is limited to Linux and UNIX platforms. \n\nThe rest of this section shows examples of links where CANDLEHOME=\/opt\/IBM\/ITM and CANDLEDATA=\/var\/IBM\/ITM. You can define different locations for your own installation. \n\n \n\nBase Directory Links \n\nThe following local data directories are always linked from CANDLEHOME to CANDLEDATA:\n\n\n * \/opt\/IBM\/ITM\/InstallITM -> \/var\/IBM\/ITM\/InstallITM\n * \n * \/opt\/IBM\/ITM\/config -> \/var\/IBM\/ITM\/config\n * \n * \/opt\/IBM\/ITM\/kt1v3depot -> \/var\/IBM\/ITM\/kt1v3depot\n * \n * \/opt\/IBM\/ITM\/localconfig -> \/var\/IBM\/ITM\/localconfig\n * \n * \/opt\/IBM\/ITM\/logs -> \/var\/IBM\/ITM\/logs\n * \n * \/opt\/IBM\/ITM\/patchlogs -> \/var\/IBM\/ITM\/patchlogs\n * \n * \/opt\/IBM\/ITM\/tables -> \/var\/IBM\/ITM\/tables\n * \n * \/opt\/IBM\/ITM\/tmaitm6\/agentdepot -> \/var\/IBM\/ITM\/tmaitm6\/agentdepot\n * \n * \/opt\/IBM\/ITM\/tmp -> \/var\/IBM\/ITM\/tmp\n\nThese directories and links are automatically generated by ITM when the system is installed or converted to use CANDLEDATA. \n\n \n\nGeneral Agent Directory Links \n\nIn addition to the base set of directory links, most agents have general links for TEMA data:\n\n\n * \/opt\/IBM\/ITM\/ATTRLIB -> \/var\/IBM\/ITM\/ATTRLIB\n * \n * \/opt\/IBM\/ITM\/\/\/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."}]},{"id":"TRAIN_Q047","question":"Help with Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693\n\nWhere 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)","is_impossible":false,"contexts":[{"filename":"swg21998655.txt","text":"Title: IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A comma separated file (CSV) download feature exists in IBM BPM and WLE and is available for anonymous users. An attacker can craft a URL that can trigger a download of attacker-supplied content under an attacker-supplied file name onto the victim's machine. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-9693 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/119517 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:C\/C:L\/I:L\/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5\n- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2\n- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3\n- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12\n\nREMEDIATION\/FIXES\nInstall IBM BPM or WLE interim fix JR57149 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1JR57149]as appropriate for your current version. \n\n\n * IBM Business Process Manager Advanced [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Standard [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Express [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR57149] \n * WebSphere Lombardi Edition [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=JR57149]\n\n\nAs IBM Business Process Manager V7.5 and WebSphere Lombardi Edition are out of general support, customers with a support extension contract can contact IBM support to request the fix. The fix disables the vulnerable URL and uses HTML5 features to trigger CSV download without server interaction. \n\nFor WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5 \n\n * Install Fix Pack 5 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034270] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149] \n\nFor IBM BPM V7.5.0.0 through V7.5.1.2: * Upgrade to minimal Refresh Pack 1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24031230], install Fix Pack 2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036462] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.0.0.0 through V8.0.1.3 * Upgrade to minimal Refresh Pack 1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033777], install Fix Pack 3 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037734] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.0.0 through V8.5.0.2 * Install Fix Pack 2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040683] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.5.0 * Apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.6.0 through V8.5.6.0 CF2 * Install CF2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041303] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.7.0 through V8.5.7.0 CF 2016.12 * Install CF 2016.12 [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg27048992] and then apply iFix JR57149 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http:\/\/www.ibm.com\/systems\/z\/solutions\/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Nalla Muthu S and Prasath K \n\nCHANGE HISTORY\n 24 Feb 2017: initial version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Solaris, Windows 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2"}]},{"id":"TRAIN_Q048","question":"How to change the maximun string length for properties in ACCE\n\n\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","is_impossible":false,"contexts":[{"filename":"swg21696083.txt","text":"Title: IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States\n\nText:\nACCE; CE; Property; FEM TECHNOTE (FAQ)\n\nQUESTION\n With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class\n\n1. Launch FEM\n2. Expand the object store and document class tree. Right click on the document class and select \"Properties\"\n3. Go to \"Properties Definitions\" tab, highlight the property definition and click \"Edit\"\n4. Make the modification and click OK\n5. Click OK again to save the change\n\nHow to perform the same operation with FileNet Content Engine - ACCE? \n\nANSWER\nFollow the below steps to update the property definition properties on ACCE: \n\n\n\n\n 1. Launch ACCE \n 2. Expand the object stores folder and click the object store to open the Object store tab \n 3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab \n 4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify \n 5. ACCE will open that property definition in a new Properties tab \n 6. Modify the property definition as required \n 7. Go back to the Class Definition tab and click Save"}]},{"id":"TRAIN_Q049","question":"Help with Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WSRR (CVE-2017-1731)\n\nI 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":"\u00b7 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\u00b7 Apply Fix Pack 8.0.0.15 or later.","is_impossible":false,"contexts":[{"filename":"swg22012345.txt","text":"Title: IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential privilege escalation in WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1731 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1731]\nDESCRIPTION: IBM WebSphere Application Server could provide weaker than expected security when using the Administrative Console. An authenticated remote attacker could exploit this vulnerability to possibly gain elevated privileges.\nCVSS Base Score: 8.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134912 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134912] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:H\/I:H\/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION\/FIXES\n The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI89498 for each named product as soon as practical.\n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition: \n\nFor V9.0.0.0 through 9.0.0.6: \n\u00b7 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\u00b7 Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.13: \n\u00b7 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\u00b7 Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018). \n\nFor V8.0.0.0 through 8.0.0.14: \n\u00b7 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\u00b7 Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n\u00b7 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\u00b7 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."}]},{"id":"TRAIN_Q050","question":"Does JazzSM 1.1.2.1 support HTTP access?\n\nDoes JazzSM 1.1.2.1 support HTTP access? ","answer":"By default, the Jazz\u2122 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.","is_impossible":false,"contexts":[{"filename":"swg21974566.txt","text":"Title: IBM Configuring access for HTTP and HTTPS in Jazz for Service Management - United States\n\nText:\njazzsm11relnotes; jazzsm1101relnotes; jazzsm1102; jazzsm1103relnotes; relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; HTTP; HTTPS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n By default, the Jazz\u2122 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<\/transport-guarantee>. \n\n6. Save the file, and then repeat these steps for the otherweb.xmldeployment files. \n\n7. Stop and restart the server. [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.2.1\/com.ibm.psc.doc\/admin\/psc_ctr_admin_restart_jazzsm_servers.html] \n\nExample \n\nThe following example is a section of theweb.xmlfile forTIPChangePasswdwhere the transport-guarantee parameter is set toNONE:\n\n\nChangePasswdControllerServletConstraint<\/display-name>\n\nChangePasswdControllerServlet<\/web-resource-name>\n\/*<\/url-pattern>\n<\/web-resource-collection>\n\nRoles<\/description>\nadministrator<\/role-name>\noperator<\/role-name>\nconfigurator<\/role-name>\nmonitor<\/role-name>\niscadmins<\/role-name>\n<\/auth-constraint>\n\nNONE<\/transport-guarantee>\n<\/user-data-constraint>\n<\/security-constraint> \n\nWhat to do next \n\nUsers must now specify a different port, depending on the mode of access. The default port numbers are as follows:\nhttp:\/\/: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."}]},{"id":"TRAIN_Q051","question":"Where can I find a description of the key differences between releases of DB2 ?\n\nI am planning an upgrade to the latest release of DB2 and I am looking for the main differences with the previous release. I my case, more specifically between version 10.5 and version 11.1. Where can I find information on this ? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q052","question":"Help with Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22004378.txt","text":"Title: IBM Security Bulletin: IBM MQ is affected by a potential denial of service to channel processes (CVE-2017-1557) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n An IBM MQ application with authority to connect to a remote queue manager could send a malicious request that could cause undefined behaviour within the channel process servicing that connection, including a loss of service for other connections being serviced by the same channel process. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-1557 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1557]\nDESCRIPTION:IBM MQ could allow an authenticated user with authority to send a specially crafted request that could cause a channel process to cease processing further requests.\nCVSS Base Score: 4.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131547 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131547]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:N\/I:N\/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD\n\nREMEDIATION\/FIXES\nIBM MQ and IBM MQ Appliance v8.0.0.0 to v8.0.0.7 \n\nApply fix pack 8.0.0.8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22010861] \n\nIBM MQ v9.0.0.0 LTS to v9.0.0.1 LTS \n\nApply fix pack 9.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044038] \n\nIBM MQ and IBM MQ Appliance v9.0.1 CD to v9.0.3 CD \n\nApply IBM MQ 9.0.4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043348]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nCHANGE HISTORY\n 22 Dec 2017 - Original Published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"TRAIN_Q053","question":"P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21502037.txt","text":"Title: IBM Unable to add Centera Device in FileNet Content Engine - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log: \n\n\n2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.\ncom.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)\n\n\nCAUSE\nChanges made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000"}]},{"id":"TRAIN_Q054","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)?\n\nI 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.\"","is_impossible":false,"contexts":[{"filename":"swg21660890.txt","text":"Title: IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n \"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/understanding\/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z\/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work. \n\n\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor\/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\" ~IBM Java Development Team \n\nIf the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors\/Locks. If these Class Pointers, Monitors\/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http:\/\/www.ibm.com\/developerworks\/library\/j-nativememory-linux\/] will be thrown. \nANSWER\nWhy Use Compressed References? \n\nBelow the 4GB mark, the JVM does not have to perform any compression\/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors\/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert the \"start\" address from the hex value to a GB value [http:\/\/ss64.com\/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.\n\n\n\n * [\/support\/docview.wss?uid=swg21660890&aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase \n\nStarting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IV37797]). \n\n\n\nNOTE: In IBM System z platforms (i.e. z\/OS and z\/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty \nassociated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below). \nSee related: IBM Knowledge Center - JVMJ9GC089W [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSYKE2_7.0.0\/com.ibm.java.messages\/diag\/appendixes\/messages\/j9gc\/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=
[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]"}]},{"id":"TRAIN_Q055","question":"P8 CPE 5.2.1 error: FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21502037.txt","text":"Title: IBM Unable to add Centera Device in FileNet Content Engine - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Errors received clicking \"Test Connection\" when configuring Centera Device in FileNet Enterprise Manager \n\nSYMPTOM\nAfter entering configuration information in FEM Fixed Content Device Wizard the following error is received: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). \n\n \n\nError in the p8_server_error.log: \n\n\n2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.\ncom.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0\n\nCaused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)\n\n\nCAUSE\nChanges made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. \n\n\nENVIRONMENT\nIBM Websphere\n\n\n\nDIAGNOSING THE PROBLEM\nFollowing error is received when \"Test Connection\" is clicked: \n\nFile = .\\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ \n\n \n\nThe [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).\n\n\nRESOLVING THE PROBLEM\nAfter making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine \nHISTORICAL NUMBER\n 41550\n180\n000"}]},{"id":"TRAIN_Q056","question":"What exactly is \"wpcollector\" in WebSphere Portal Server?\n\nI'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.","is_impossible":false,"contexts":[{"filename":"swg21445430.txt","text":"Title: IBM Automated data collection capability provided by wpcollector tool - United States\n\nText:\nwpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)\n\nQUESTION\n What are the benefits of the wpcollector tool? How do I use this tool? \n\nANSWER\nWpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support. \n\nWpcollector is delivered with WebSphere Portal beginning with the 7.0 release. If tracing is required for the problem scenario, you must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. \n\nTo run wpcollector, please follow the steps, below:\n\n\n\n * If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below: \n \n\n\n * If using Microsoft Windows, Unix\/Linux, or IBM i, run the following script from the [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]"}]},{"id":"TRAIN_Q057","question":"Help with an insufficient authorization check for project actions in IBM Business Process Manager (CVE-2014-4844)\n\nI need to understand details regarding an insufficient authorization check for project actions in IBM Business Process Manager (CVE-2014-4844). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q058","question":"Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written\n\nPortal 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.","is_impossible":false,"contexts":[{"filename":"swg1PI37248.txt","text":"Title: IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States\n\nText:\n FIXES ARE AVAILABLE\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042746]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044479]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044734]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A PFBC file might fail to apply. Wsadmin will show an error\n similar to this:\n \n java.lang.Exception: java.lang.Exception: ADMG0660E:\n Properties File Validation during command\n applyConfigProperties failed. See Report file for details.\n \n The report file will contain an error similar to this:\n Error=java.lang.NullPointerException\n at\n com.ibm.websphere.management.configservice.ConfigServiceHelper.g\n etConfigDataType(ConfigServiceHelper.java:235)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work\n spaceHelper.java:563)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator\n (WorkspaceHelper.java:584)\n at\n com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu\n tes(ConfigServiceImpl.java:2102)\n at\n com.ibm.ws.management.commands.properties.resources.common.Apply\n Properties.setProperties(ApplyProperties.java:240)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Property File Based Configuration *\n ****************************************************************\n * PROBLEM DESCRIPTION: A Property File Based Configuration *\n * (PFBC) file might fail to apply. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A recent (8.5.5.5) parser change introduced a problem where\n types that have default values noted in the file and are not\n Strings can be incorrectly processed. For example:\n isolatedClassLoader=false #boolean,default(false)\n might be incorrectly processed, and as a result, the file\n might not apply.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6. Please refer to the Recommended Updates\n page for delivery information:\n http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980 [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI37248\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt \/ Xsystem\n \n \n * SUBMITTED DATE\n 2015-03-18\n \n \n * CLOSED DATE\n 2015-03-20\n \n \n * LAST MODIFIED DATE\n 2015-03-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBS APP SERV N\n \n \n * FIXED COMPONENT ID\n 5724H8800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"}]},{"id":"TRAIN_Q059","question":"Uninstalling I5 OS agent failed\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21377984.txt","text":"Title: IBM Removing a failed install from the ITM i5\/OS agent - United States\n\nText:\ni5 removal TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If an ITM i5\/OS agent DLTLICPGM 5724C04 command fails then we have to remove the various parts of the agent that have been installed. This has to be done by hand because the DLTLICPGM 5724C04 command will fail as the unistall encounter some issues during uninstall. This technote will show how to do it. \n\nSYMPTOM\nRSTLICPGM command fails to install the ITM i5\/OS agent. \n\nDLTLICPGM 5724C04 command fails to uninstall the agent\n\n\nCAUSE\nRSTLICPGM\/DLTLICPGM 5724C04 command failed to finish correctly and leaves the agent in an unknown state.\n\n\nENVIRONMENT\nIBM i \/ i5\/OS machines\n\n\n\nDIAGNOSING THE PROBLEM\nRSTLICPGM and DLTLICPGM 5724C04 fail for the i5 agent.\n\n\n\nRESOLVING THE PROBLEM\n \n\n To delete the ITM i5\/OS agent do the following :- \n\nFirst try DLTLICPGM 5724C04 for the Tivoli agent. If that does not work then do \nthe following i5\/OS commands : \n\nDLTLIB QAUTOMON \nDLTLIB QAUTOTMP \nDLTUSRPRF QAUTOMON and choose to remove all objects owned by this user.\n\nstart qsh \ndelete \/QIBM\/USERDATA\/IBM\/ITM and all sub directories in it. \ndelete \/QIBM\/PRODDATA\/IBM\/ITM and all sub directories in it. \n\nRetry the RSTLICPGM commands specified in the user guide. \nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0\/com.ibm.itm.doc_6.3\/osibmi\/pcinstall_a4_ug.htm?lang=en [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0\/com.ibm.itm.doc_6.3\/osibmi\/pcinstall_a4_ug.htm?lang=en]\n\n\n\nPRODUCT ALIAS\/SYNONYM\n ITM OS\/400 agent\nITM i5\/OS agent\nITM IBM i agent\n5724C04"}]},{"id":"TRAIN_Q060","question":"Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc\n\n\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","is_impossible":false,"contexts":[{"filename":"swg22009818.txt","text":"Title: IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What can cause an STAP to fail to connect properly - I get the following messages in the logs:-\n\n\/tmp\/guard_stap.stderr.txt on the DB Server :-\n\"Server 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]"}]},{"id":"TRAIN_Q061","question":"Getting hung threads, sometimes followed by OutOfMemory error\n\nOur application is hanging, we see lots of hung threads in the SystemOut.log, occasionally followed by OutOfMemory error. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q062","question":"SAP Agent user authorizations\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21657458.txt","text":"Title: IBM Minimum authorization required for SAP agent logon userid - United States\n\nText:\nauthorization minimum IBMMON_AGENT profile settings agent userid SAP MySAP \/IBMMON\/AUTH TECHNOTE (FAQ)\n\nQUESTION\n What are the minimum authorizations required for the userid used by the ITM MySAP agent to logon a SAP system? \n\nANSWER\nBy default, the MySAP agent uses the userid IBMMON_AGENT, that is created when ITM transport are imported in the SAP system, together with \/IBMMON\/AUTH role and profile.\nIf you don't want to use the default userid and profile, you need to create your own userid and provide it with a set of minimum required authorization settings.\nDepending on the transport level, the required authorization may vary, but you can always refer to the values specified for the \/IBMMON\/AUTH profile available in the transport.\nBy looking at this profile, you can obtain the needed authorization information.\nIn example, for MySAP agent 6.2 IF16, those are the authorization defined for the \/IBMMON\/AUTH profile: \n\n\n[\/support\/docview.wss?uid=swg21657458&aid=1] [\/support\/docview.wss?uid=swg21657458&aid=1]\n\nYou need to define your own userid providing the same set of authorization showed for the \/IBMMON\/AUTH profile to have mySAP agent performing successful data collection even using a non-default userid.\n\n \n\nPRODUCT ALIAS\/SYNONYM\n IBM Tivoli Monitoring MySAP Agent 6.2"}]},{"id":"TRAIN_Q063","question":"How to get the ODM 8.5.1.2 fixpack of ODM 8.5.1.1?\n\nODM 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.","is_impossible":false,"contexts":[{"filename":"swg24039235.txt","text":"Title: IBM Operational Decision Manager V8.5.1.2 Fix Pack - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This cumulative fix pack updates Operational Decision Manager V8.5.1 and V8.5.1.1 to V8.5.1.2. \n\nDOWNLOAD DESCRIPTION\nThis fix pack is entitled. Only customers who have purchased Operational Decision Manager V8.5.1 can use this fix pack.\n\n\nHow to install the fix pack\nIf you are not installing both Operational Decision Manager components, skip the instructions regarding Decision Center or Decision Server.\n\n\n 1. For Decision Center, download 8.5.1-WS-ODM_DC--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"}]},{"id":"TRAIN_Q064","question":"Support of RHEL 5.8 and Liberty 8.5.5.11 with JAVA 8.0\n\nWe 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","is_impossible":false,"contexts":[{"filename":"swg27045339.txt","text":"Title: IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems - United States\n\nText:\n RELEASE NOTES\n\nABSTRACT\n IBM WebSphere SDK Java Technology Edition 8.0 Minimum Supported Operating Systems \n\nCONTENT\nWebSphere Application Server 8.5.5 announced IBM WebSphere SDK Java Technology Edition 8.0 as an option for Java. \n\n\n\n\n * Liberty added support in fix pack 5 \n * WebSphere Application Server traditional added support for installing this SDK as an extension in 8.5.5.9 * In 8.5.5.11 and later, this SDK is available as an option on new installations. \n * In 8.5.5.14 and later, it is planned that this SDK will be required for all new installations and all updates (fixpacks).\n \n \n\nThe following are the minimum supported OS levels for IBM WebSphere SDK Java Technology Edition 8.0 in WebSphere Application Server. Action Required:\n\n * \n * \n * .0\n * \n\n\nOperating System minimums: \n\n * AIX\n * AIX 6.1 TL7 \n AIX 7.1 TL3 \n * HP-UX IA64\n * HP-UX 11i v3 (11.31) \n * IBM i\n * IBM i V7R1 \n * Linux\n * RedHat Enterprise Linux 6 \n RedHat Enterprise Linux 7 \n SLES 11.1 (SP1) \n SLES 12 \n Ubuntu 12.04 LTS \n Ubuntu 14.04 LTS \n Ubuntu 16.04 LTS \n * Windows\n * Windows 7 service pack 1 \n Windows 8 (not Metro) \n Windows Server 2012 \n Windows Server 2016 \n * Solaris \n * Solaris 11 \n * z\/OS\n * z\/OS 1.13 \n z\/OS 2.1 \n z\/OS 2.2 \n\n\n\nComponent specific notes: * WebSphere Application Server installations between 8.5.5.11 and 8.5.5.14 require an explicit user selection to determine the default IBM WebSphere SDK Java Technology Edition on new installations. \n * IBM HTTP Server and the Webserver Plug-in between 8.5.5.11 and 8.5.5.14 defaults to IBM WebSphere SDK Java Technology Edition 8.0. No explicit selection is required. These components do not use Java at runtime."}]},{"id":"TRAIN_Q065","question":"For Solaris how to write verbose gc output to a log file other than the native_stdout?\n\nA 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","is_impossible":false,"contexts":[{"filename":"swg21636533.txt","text":"Title: IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States\n\nText:\nverbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\n\nQUESTION\n How can I write verbose gc output to a log file other than the native_stdout? \n\nCAUSE\nBy default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.\n\nANSWER\n \n\nWAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:\/tmp\/gc.log\n\nTo enable log file rotation:\n-XX:+UseGCLogFileRotation\n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M\n\n\nnotes:\n-Xloggc: \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]"}]},{"id":"TRAIN_Q066","question":"Is there a 64-bit agent Log File Agent available for Windows OS?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg24043263.txt","text":"Title: IBM Tivoli Log File Agent, Version 6.3.0 Fix Pack 02 (6.3.0-TIV-ITM_LFA-FP0002) - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This fix pack adds support for a Windows x86-64 bit (WIX64) and PowerPC little-endian Log File agent. In addition, it resolves the APARs and defects listed below. \n\nDOWNLOAD DESCRIPTION\n\n\n\n(C) Copyright International Business Machines Corporation 2017.\nAll rights reserved.\n\nComponent: Tivoli\u00ae 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<\/LFA_test_logs\/test_1.log> errno 2 'No such file or\ndirectory\". This occurs right after the file has been found\nand matched. (Note: if the monitored file is also found\nlocally, it will succeed and monitor the local file.) \nUsing the same file in LogSources results in a match. \n\nOn the agent system, with a minimum of the following trace:\n\"ERROR (UNIT:kumpdcm2 ALL) (UNIT:kum0dir ALL)\" enabled, the\nagent RAS1 log \n_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 <\/LFA_test_logs\/test_1.log> errno 2 'No such \nfile or directory' \n...:kum0dir.c,192,\"KUM0_stat_withMsgFlag\") Unsuccessfully stat \nfile \n\/LFA_test_logs\/test_1.log size=0 access time=0, modification \ntime=0, \ncreation time=0 \n...:kumpdcm2.c,481,\"KUMP_DetermineCurrentMonitorFileNameStrict\") \nFile \n\/LFA_test_logs\/test_1.log skipped, stat failed -1 \n... \n- - - \n\nAPAR: IV89574\nAbstract: INVALID CHARACTERS SEEN IN THE TRACE \"*****Error: \nu_strFromUTF8 failed for string ... - .........,\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 \u00e4\u00ab\u00e4\u00a8\u00e4O\u00e4\u00e8\u00e4\u00ec\u00e4j\u00e4\u00ec - \n\u00e4n\u00e4f\u00e4\u00ee\u00e4n .lnk\u00d9l \u00d9s\u00d9w 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\u00ae 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\u00ae 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\u00fc\u00fclinda\u00fc\u00fclinda \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='\u00e3 '; \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 <\/tmp\/test_lfa.txt> creation time <1411741772> last \nmodification time <1411741772> size <699> \n... \n...:kumpfdp2.c,792,\"DoFileTailRestart\") Comparing creation \ntime <1411743260> last modification time <1411743260> size <758>\n...:kumpfdp2.c,816,\"DoFileTailRestart\") Note: Monitorfile \n\/tmp\/test_lfa.txt has been switched or re-created, updating \nrestart file \n<\/opt\/IBM\/ITM\/logs\/LO_LFA01_LogfileEvents_LogfileEvents_tivoli85\n.rst> \n...:kumpfdp2.c,834,\"DoFileTailRestart\") Per TailRestartFromTop\nparameter, restarting file monitoring from beginning of file\n<\/tmp\/test_lfa.txt> \n... \n- - - \n\nThe file, listed above, is detected as re-recreated based on the\nfile information returned by the operating system: \ncreation time modification time size \nlast <1411741772> <1411741772> <699> \ncurrent <1411743260> <1411743260 > <758> \n\nAPAR: IV67708\nAbstract: WINDOWS EVENT LOG EVENTS WITH %N RESULTS IN A MESSAGE OF \n\"NONE\" \nAdditional information: The event msg field or slot might contain \na value of \"None\", when a Windows event log message contains\na %n where n is a number in the event description field. \nIf the %n is not substituted, the Microsoft EvtFormatMessage\nAPI returns ERROR_EVT_UNRESOLVED_VALUE_INSERT (15029) which\nthe agent treats as an error. As a result of the error, the \nagent discards the event description and substitutes \"None\".\n\nProblem Determination: With a mininum of the following trace\nenabled for the LO agent: \nKBB_RAS1= ERROR (UNIT:WinLogQuery ALL), the agent log \n_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\u00ae\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 \u00b4kloagent'. \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 <\/opt\/IBM\/ITM\/logs\/L \nO_default_LogfileEvents_hpia5.rst> \n...:kumpfdp2.c,173,\"KUMP_ParseSingleRestartLine\") Parsing \nRecPtr 6000000000736F53 <;> \n...:kumpfdp2.c,200,\"KUMP_ParseSingleRestartLine\") Error: parsed\nlocation file creation modification \n size with RecPtr 5FFFFFFFA0736F52Page 34 of 35 \n...:kumpfdp2.c,427,\"UpdateRestartFileBaseFunction\") Note: \nRequired fields missing from restart file \n<\/opt\/IBM\/ITM\/logs\/LO_default_LogfileEvents_hpia5.rst> \n- - - \n\nAPAR: IV56299\nAbstract: A PERCENT SIGN (%) LITERAL IS NOT SUPPORTED IN FORMAT\nSTATEMENT\nAdditional information: When a percent sign (%) or a percent sign\n(%) followed by a literal other than the valid variables of s,\nt, n, is used in a FORMAT statement, it results in an \"illegal\nvariable\" message and an incorrect regular expression. As a\nresult, the record does not match as expected. \n\nFor example: \nFORMAT 43866_Class10 \n43866_10 %s % %s* \n. . .\n\nor \n\nFORMAT 43866_30 \n%t %s %MIDDLEWR: %s \n. . .\n\nWith KBB_RAS1: ERROR, the the agent log \n_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\u00ae 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\u00ae 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\u00ae.\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"}]},{"id":"TRAIN_Q067","question":"ODM 8.7 TeamServer users active authoring rules and they get kicked out - transaction timeout or session timeout?\n\nSome 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.","is_impossible":false,"contexts":[{"filename":"swg21451229.txt","text":"Title: IBM Rule Team Server\/Decision Center is timing out while performing certain operations - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to resolve \"Transaction timed out after 601 seconds\" error while performing certain operations in Rule Team Server (RTS)\/Decision Center (DC)? \n\nSYMPTOM\nWhile generating ruleapps in RTS\/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes): \n\nOn WebLogic: \n\nRule Team Server has encountered an unexpected error. The internal error message is: #{SelectionBean.asynchAction}: javax.faces.el.EvaluationException: java.lang.RuntimeException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057DF8C316E1C1224CD]'. No further JDBC access is allowed within this transaction. \n\n... \n\n \n\nOn WebSphere: \nTimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds.\nTimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 3,5,main]. The stack trace of this thread when the timeout occurred was: \nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyParser.java:511)\n...\n\n\nCAUSE\nThe transaction timeout for RTS\/DC is set to 10 minutes by default in the teamserver web module deployment descriptor (WEB-INF\/web.xml), and application servers also have container level transaction timeouts that are configurable. If a transactional operation performed by RTS\/DC takes longer than these timeouts to complete, the transaction is rolled back and the operation is not completed.\n\n\n\nRESOLVING THE PROBLEM\nIf you perform time consuming operations in large repositories, you can increase the timeout value in the web.xml file of the RTS\/DC EAR file (jrules-teamserver-.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)<\/description>\nilog.rules.teamserver.transaction.timeout<\/param-name>\n600<\/param-value>\n<\/context-param> \n... \n\nAnother place to look for are application server specific transaction timeout configurations. For example, for WebSphere Application Server, check the \"Maximum transaction timeout\" and increase it as needed as described here [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.doc\/info\/ae\/ae\/tjta_settlog.html].\n\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 7.5 Enterprise Business Integration IBM Operational Decision Manager Platform Independent 8.0.1, 8.0 Enterprise"}]},{"id":"TRAIN_Q068","question":"Does DataPower support SHA-2?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21406783.txt","text":"Title: IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States\n\nText:\nDatapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2"}]},{"id":"TRAIN_Q069","question":"Why SSL handshake is failing after upgrading to 6.0 or above?\n\nAfter 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.","is_impossible":false,"contexts":[{"filename":"swg21632275.txt","text":"Title: IBM DataPower firmware version 6.0 will enable TLS v1.2 or v1.1 by default - United States\n\nText:\nssl tsl client hello handshake fail failed version 6.0 TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nQUESTION\n Why would some outgoing SSL handshakes fail with firmware version 6.0 but not prior firmware versions? \n\nCAUSE\nBeginning in firmware version 6.0 and above, the default SSL settings have changed. The Crypto profiles now have TLSv1.2 and 1.1 which will be enabled by default. This affects the protocol version included in the Client Hello when DataPower is acting as the SSL client. If TLSv1.2 is not supported, the server still negotiates to the most secure supported protocol (e.g. TLSv1.1, TLSv1.0, SSLv3) if enabled. \n\nSome legacy servers with non-compliant implementations of SSL may reject connection attempts when TLSv1.2 or TLSv1.1 are used. In these cases, the handshake fails without properly negotiating to a mutually agreeable protocol.\n\nThe TLS versions 1.1 and 1.2 are part of the requirements for being compliant with NIST SP800-131a.\n\n\n\nANSWER\nUpgrade the SSL server to a version compliant with the SSL\/TLS specifications. If required you may disable TLSv1.2 and TLSv1.1 within the Crypto Profile to allow compatibility. \n\n\nWithin the domain simply navigate to the Objects> Crypto Configuration> Crypto Profile>\nThen simply click on your specific profile to view the Options selection and see what SSL protocol versions are supported.\n\nAny further questions or issues please feel free to contact DataPower support. A packet trace and error report would be the most helpful information in viewing the problem."}]},{"id":"TRAIN_Q070","question":"How do I search for a string which has reserved words or characters when searching in documents in Atlas?\n\nHow 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\"","is_impossible":false,"contexts":[{"filename":"swg21982451.txt","text":"Title: IBM Search option for a reserved word or character in documents in Atlas - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I search for a string which has reserved words or characters when searching in documents in Atlas? \n\nCAUSE\nThere are specific options to use in oracle when you search for certain strings\n\nANSWER\nWhen there is a \"-\" in a string you are searching for, you need to use \"\\\" in front of the \"-\" \n\nFor example - \"String1-String2\" should be searched as \"String1\\-String2\" \n\nPlease refer to the oracle documentation for Special Characters in Oracle Text Queries"}]},{"id":"TRAIN_Q071","question":"Why does my upgrade to BigFix version 9.2.5 take a very long time?\n\nMy 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","is_impossible":false,"contexts":[{"filename":"swg21962862.txt","text":"Title: IBM Verify an IEM server upgrade is still in progress - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I tell if the IBM Endpoint Manager (BigFix) server database upgrade is progressing? \n\nCAUSE\nWhen upgrading a BigFix server, most of the time is usually spent upgrading the database. The installer launches the BESAdmin utility to complete this part of the upgrade, but does not provide detailed progress during this phase. For some long running upgrades, it may appear that the upgrade is hung or not progressing: \n\nOn Windows, the BESAdmin UI will indicate \"Not Responding\" if clicked on at this point. \n\nOn Linux, the message \"Info: Configuring the database for the server component, please wait ... \" is reported.\n\n\nANSWER\nIt is important to allow the upgrade to complete when in this state, and not attempt to cancel or kill the upgrade process. To verify the upgrade is still active, check that the following process is still running: \n\nWindows: BESAdmin.exe \n\nLinux: BESAdmin \n\nCPU usage of BESAdmin may be minimal during times when the database is doing most of the work, so just the existence of the process is good confirmation. For additional confirmation, the BFEnterprise or BFENT database can be monitored for activity using SQL Server Profiler or the DB2 'CREATE EVENT MONITOR' statement to track SQL statement events."}]},{"id":"TRAIN_Q072","question":"Error: \"MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION\" occurs at portal startup\n\n\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","is_impossible":false,"contexts":[{"filename":"swg1PI34677.txt","text":"Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States\n\nText:\n A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications \/ value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions\n \n \n \n \n \n\nLOCAL FIX\n * 1) open the WAS admin console\n 2) navigate to Resources > Resource environment providers > WP\n ScriptingService > Custom properties\n 3) you should see an entry with the name\n \"ServerExt.applications\" and value\n \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"\n 4) delete this entry, save and restart the server.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 05 (PI31198 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI31198]) for Portal\n 8.5.0.0 available from Fix Central:\n \n http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent\n =ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al]\n l&platform=All&function=aparId&apars=PI31198\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added a task to remove the outdate resource environment\n provider entry.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI34677\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-02-10\n \n \n * CLOSED DATE\n 2015-03-10\n \n \n * LAST MODIFIED DATE\n 2015-03-10\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * FIXED COMPONENT ID\n 5724E7600\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"}]},{"id":"TRAIN_Q073","question":"Latest deployed ruleset not executing in clustered environment\n\n\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","is_impossible":false,"contexts":[{"filename":"swg21598779.txt","text":"Title: IBM An unexpected ruleset version is executed - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?\nWhat are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ? \n\nCAUSE\nPossible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses\n\n\nANSWER\nFirst validate that the RES components (the Execution Unit, the Management Console and the Client Application bundling the RES client library, which may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.config\/config_ds_res\/tpc_res_config.html]. \n\nThe ruleset version that is executed depends first on the ruleset path that is requested. Specifying a ruleset path with no version ( such as \/MyRuleApp\/MyRuleset\/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as \/MyRuleApp\/2.0\/MyRuleset\/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the requested ruleset path. \n\n \n\nA common situation for an unexpected ruleset version to be executed is that of a hot deployment that is not successfully completed. The more frequent causes for the hot deployment not to happen as expected are: \n\n * Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update through JMX. For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.config\/config_ds_res_was8\/tsk_was_map_admin_group.html] \n * Version mismatch between the Execution Unit(s) and the Management Console: in order for the Management Console to detect the presence of execution units the versions of these components must match down to the fix level. For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the \"About\" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version. For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor \n * Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that time. Note that there is no guarantee of which specific earlier version of the ruleset may be used since it is a factor of which versions are available in the deprecated ruleset cache and whether garbage collection has occurred. In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_forcing_sync_pars.html]. \n * Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See XU notification in a cluster over multiple cells [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21458245]. If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21418646] can be useful. \n * Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully \n * Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_deploy_rlapp_ant.html] does not trigger a notification, so the update may only been seen after server restart. \n * XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_xu_mbean_jse.html] \n * Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2SE mode hot deployment does not seem to work [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21585251] \n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES \/ RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0"}]},{"id":"TRAIN_Q074","question":"Is there a way to not use cache inside a HttpRequest node?\n\nIs there a way in IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) to not use cache inside a HttpRequest node? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q075","question":"Where can I get Tivoli Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)?\n\nWhere 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\u00ae Tivoli\u00ae Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase\u00ae Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002)\n\nFix Pack: 0002\nComponent ID: 5724B96SO\nDate: December 8, 2017","is_impossible":false,"contexts":[{"filename":"swg24044440.txt","text":"Title: IBM Tivoli Composite Application Manager for Applications 721 FP2: Monitoring Agent for Sybase Server 620 FP2 (6.2.0-TIV-ITM_SYB-FP0002) - United States\n\nText:\nSybase Agent; OY; KOY; 5724B96SO; ITM; ITCAM DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects and provides the enhancements listed \nin the \"Problems Fixed\" section below. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2018.\n\n\nAll rights reserved.\n\nComponent: IBM\u00ae Tivoli\u00ae Composite Application Manager for Applications 721 FP2: \nMonitoring Agent for Sybase\u00ae 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 \u2013i\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 \u2018prereq_checker.bat KOY\u2019 present at location:\nInstallerPath\\Sybase_Agent_Installer\\WINDOWS\\prereqchecker\n\nFor Unix:\nRun \u2018.\/prereq_checker.sh KOY\u2019 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\u2192 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"}]},{"id":"TRAIN_Q076","question":"Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22014367.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:U\/C:L\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION\/FIXES\nFor MQ 5.3 \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"TRAIN_Q077","question":"Why is the test suite execution failing from Decision Center?\n\nWhen executing a test suite from Decision Center the run may fail with an error message similar to:\n XU client error.\n GBRXU0448E: Plugin error.\n Unable to retrieve the engine manager.\n The parsing of the ruleset failed Problem occurred loading translation: Error when translating parameter \"inputParameter\": Cannot translate class \"sample.InputParameter\".\n\nWhat can be causing this error? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q078","question":"Daylight Saving Time changes effect on CICS TS\n\nHow does the Daylight Saving Time (DST) time change affect CICS Transaction Server for z\/OS and z\/VSE (CICS TS)? I would like to know when DST begins and ends in my country, and if there are any actions that I will need to take for CICS when the time changes. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q079","question":"How can I force the Websphere 6.1 JVM to pick only a specific jdbc jar?\n\nWe are running WAS 6.1. We have multiple jvms in a cell and only one of them needs to use a new version of the DB2 client. We have an application deployed onto this jvm and this application needs to use two different version of DB2 jdbc jars. One part of the application is configured to use the old jars and the other part needs to use the new jars. Is there a way to configure the jvm such that the second part of the application always picks up the latest jars? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q080","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)\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. 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","is_impossible":false,"contexts":[{"filename":"swg22010832.txt","text":"Title: IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2011-5320 CVE-2017-15670 CVE-2017-15671 CVE-2017-15804\nRemediation: \n\nIBM strongly recommends that you contact Red Hat to obtain and install fixes for Red Hat Enterprise Linux (RHEL) Server 6.2, as applicable\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker Hypervisor Edition Linux 8.0 \nPRODUCT ALIAS\/SYNONYM\n WMB HVE IIB HVE"}]},{"id":"TRAIN_Q081","question":"'Access is denied' install errors with ICC\n\nInstalling 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.","is_impossible":false,"contexts":[{"filename":"swg24042387.txt","text":"Title: IBM Content Collector V4.0.1 Fix Pack 3 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This document contains links to the download page for IBM Content Collector V4.0.1 Fix Pack 3 \n\nDOWNLOAD DESCRIPTION\n \n\nIBM CONTENT COLLECTOR DOWNLOADS\n * All versions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27040223] \n * Version 4.0.1 Fix Pack 3- selected tab, \n\n\nApply IBM Content Collector V4.0.1 Fix Pack 3 to upgrade from IBM Content Collector V4.0.1 to IBM Content Collector V4.0.1.3. \n\nBelow is the list of the problems that were fixed in this fix pack.\n\n\nAPAR Number APAR Abstract HE12445 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12445] ICC reporting \"SOLID Table Error 13011: Table GENERIC_DATA does not exist\" or \"Connection switch, some session context may be lost\" HE12488 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12488] SOME DOCUMENTS INTERMITTENTLY FAILED INDEXING WITH \"COULD NOT BE PROCESSED AS A REGULAR EMAIL\" ERROR. HE12491 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12491] IBM Content Collector cannot delete the entry from the Blacklist table in the solidDB HE12436 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12436] EXCEL FILES CANNOT BE INDEXED DUE TO 100% CPU CONSUMPTION task missing HE12490 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12490] Domino Template Enablement in IBM Content Collector setup tools causes an error when enable domino template. HE12513 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12513] TAG FILES REMAIN FOR ICC SOFTWARE COMPONENTS WHICH ARE NOT ACTUALLY INSTALLED. HE12526 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12526] EXPRESSION DOES NOT GET SAVED IN THE 'WS CALL WEB SERVICE' TASK HE12529 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12529] Mailbox randomly is skipped in the ICC cluster HE12537 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1HE12537] CONTENT COLLECTOR INSTALLATION FAILS WITH ACCESS IS DENIED ERROR ON WASSERVICE.EXE FILE PREREQUISITES\nIBM Content Collector V4.0.1 Fix Pack 3 can be used with the following IBM Content Collector version: \n\nURL LANGUAGE SIZE(Bytes) Prerequisites for IBM Content Collector V4.0.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27042658] English 1 \nINSTALLATION INSTRUCTIONS\nRead the fix pack readme files for specific information about installing the fix pack packages.\n\nURL LANGUAGE SIZE(Bytes) 4.0.1.3-IBM-ICC-FP003 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=Enterprise%2BContent%2BManagement&product=ibm\/Information+Management\/Content+Collector&release=All&platform=All&function=fixId&fixids=4.0.1.3-IBM-ICC-FP003&includeRequisites=1&includeSup] English 1 \nDOWNLOAD PACKAGE\nThe IBM Content Collector V4.0.1 Fix Pack 3 download package consists of the following files: \n\n * 4.0.1.3-IBM-ICC-FP003.pdf: Readme file \n * 4.0.1.3-IBM-ICC-Server-FP003.zip \n * 4.0.1.3-IBM-ICC-OWA-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-SOLARIS-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-P8CSS-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-P8CSS-Linuxz-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-AIX-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Linux-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-Solaris-FP003.tar.gz \n * 4.0.1.3-IBM-ICC-CM8Text-WIN-FP003.zip \n * 4.0.1.3-IBM-ICC-CM8Text-Linuxz-FP003.tar.gz\n\nHOW CRITICAL IS THIS FIX?\nThis fix addresses vulnerabilities that are described in CVE-2016-0363 and CVE-2016-0376 which are disclosed as part of IBM Runtime Environment Java Technology Edition, Version 6 in April 2016. \n\nFor further information see the Readme File for IBM Content Collector V4.0.1 Fix Pack 3\n\n\n\n [\/support\/docview.wss?uid=swg24042387&aid=1]Problems (APARS) fixed [\/support\/docview.wss?uid=swg24042387&aid=2]Problems (APARS) fixed\nHE12445 HE12488 HE12491 HE12436 HE12490 HE12513 HE12526 HE12529 HE12537"}]},{"id":"TRAIN_Q082","question":"XGS 5.3.0.6: Is there a way to replicate an inspection object under the same policy repository?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21902778.txt","text":"Title: IBM Security Network Protection firmware 5.3.1 release notes - United States\n\nText:\nrelease notes; readme; firmware; xgs FIX README\n\nABSTRACT\n IBM Security Network Protection Firmware Version 5.3.1 is a firmware update for the XGS NGIPS network protection platform. This release provides the following updates to IBM Security Network Protection Firmware Version 5.3.1. \n\nCONTENT\nServiceability and support enhancements: \n\n * You can now get additional information about your system through the command line within your \"Tools\" directory. We have added the Sysinfo command that will display system CPU, memory, and storage information in command line interface (CLI).\n Note: A complete list of CLI commands are located in the Command-line interface [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSHLHV_5.3.1\/com.ibm.alps.doc\/references\/alps_command_line_interface.htm] section in the Knowledge Center.\n \n * New to this release we have added a services mode within CLI. These commands will allow you to restart key services within the appliance. These services are listed below: * Packet processing \n * Packet Capture \n * Local Management Interface (LMI) \n * License and Update (LUM) \n * SiteProtector Communication\n \n \n \n * You can now view and search logs from the command line using the \"less\" and \"tail\" commands from within logs mode. Log files found using the less command are System, Webserver, Updates and Analysis logs. \n \n * With the admin-sftp account you can now retrieve Snapshots, Packet Captures, and support files. This account uses the same password as the admin account. \n Note: More details on admin-sftp can be found in the Downloading files with an SFTP client [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSHLHV_5.3.1\/com.ibm.alps.doc\/tasks\/alps_downloading_sftp.htm]documentation on the Knowledge Center. [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSHLHV_5.3.1\/com.ibm.alps.doc\/tasks\/alps_downloading_sftp.htm]\n\n\nResponse enhancement: * Forwarded events (Remote Syslog Alert Responses) will show the same details as the content sent to SiteProtector. \n * Support for using the TCP protocol when creating Remote Syslog Alert Responses to prevent messages being truncated and improve delivery reliability over using UDP.\n\n\nNetwork Access Policy enhancement: * You can now use the network access policy to control network access when the HTTP X-Forward-For (XFF) header is enabled. The network policy can use the XFF header along with the packet source to control network traffic.\n\n\nIPS Policy enhancements: * You can now derive a new IPS object from an existing IPS object by right-clicking on an IPS object and left-clicking on Clone.\n \n * When enabling network, transport-layer, and status events in a non-default IPS object, a warning message is shown. This will help to minimize what may be seen as a false negative.\n\n\nPerformance: * Inspection throughput increase for XGS 7100 up to 25Gbps, FPL5 (25Gbps) added.\n\n\nMiscellaneous updates and implementation changes: * Top 10 URLs and URL categories widget in the Local Management Interface have been disabled by default. Given the limited popularity of this feature, coupled with the performance impact in certain situations, we disabled the feature by default. You can re-enable it by using the advanced parameter tune.url.topten.tracking=true. \n \n * We have removed the MultiCast Domain Name System (mDNS), under some configurations it caused security risks within the appliance.\n \n * Support for mutual certificate authentication for communication between the Network Security appliance and SiteProtector.\n\n\nKnown issues: \nYou can find a list of known issues for IBM Security Network Protection 5.3.1 in Technote 1715537: Known issues for IBM Security Network Protection version 5.3.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21715537]. \n\n\n\n\n[\/support\/docview.wss?uid=swg21902778&aid=1] [https:\/\/ibm.biz\/BdHdZx] [\/support\/docview.wss?uid=swg21902778&aid=2] [http:\/\/ibm.biz\/InfraSecForumTechnote] [\/support\/docview.wss?uid=swg21902778&aid=3] [http:\/\/ibm.biz\/SecSuptUTube] [\/support\/docview.wss?uid=swg21902778&aid=4] [http:\/\/ibm.biz\/InfraSecFixes] [\/support\/docview.wss?uid=swg21902778&aid=5] [http:\/\/ibm.biz\/FlexLicLogin] [\/support\/docview.wss?uid=swg21902778&aid=6] [http:\/\/ibm.biz\/MyNotification] [\/support\/docview.wss?uid=swg21902778&aid=7] [http:\/\/ibm.biz\/ContactSecSupport] \nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21903740]"}]},{"id":"TRAIN_Q083","question":"When click test connection, the older JDBC driver version shows in the SystemOut.log file\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21634612.txt","text":"Title: IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States\n\nText:\nisolate this resource provider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer has defined 3 Oracle JDBC Providers at cell, node and server\nscope. Client have following configuration in websphere JDBC provider. \n\nIn Cell Scope - C:\\jdbc\\ojdbc5\\ojdbc5.jar \n\nIn Node Scope - C:\\jdbc\\ojdbc6_g\\ojdbc6_g.jar \n\nIn Server Scope- C:\\jdbc\\ojdbc6\\ojdbc6.jar \n\nIn this case value of JDBC driver path in WebSphere variable is identical. Nornally, If JDBC provider configure at server level then server level driver will get load first. But in this case since all three drivers are from same vendor, So we can not control which driver is picking up. In this case \n\"C:\\jdbc\\ojdbc6\\ojdbc6.jar\" should be loaded first but instated, ojdbc5.jar was load first\n\n[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass \n\noracle.jdbc.driver.OracleDriver \n\nloader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9 \n\nsource=file:\/C:\/jdbc\/ojdbc5\/ojdbc5.jar Exit \n\n\n\n\n\n\nSYMPTOM\nDue to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.\n\n\nCAUSE\nWhen multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded. \n\nRESOLVING THE PROBLEM\n In order to support the existence of multiple versions of the driver jars, the \"Isolate this resource provider\" configuration helps to ensure there are no conflicts. This needs to be configured on each JDBC Provider. You cannot isolate only one resource provider, all the provider configurations in different scopes will have to be configured with the \"Isolate this resource provider\" setting. In this scenario, the resource provider classes from different versions of the jars are not imported or accessed to verify if the isolation has indeed worked. In order to use the server-scoped resource provider the datasource using the server-scoped jdbc provider will have to be referenced from the application after isolating the resource providers and using a resource reference in the application. \n\n\nGo to the JDBC Provider and enable \"isolate the resource provider\". When \"Isolate this resource provider\" is enabled, it ensures that only the jar that was specified in the classpath will be used for all the datasources under that particular JDBC provider. \n\n \n\nHere are links to Knowledge Center articles which contain further information on the setting: \n\n\nJDBC provider settings [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_9.0.0\/com.ibm.websphere.nd.multiplatform.doc\/ae\/udat_manjdbcprodet.html]\n\nConsiderations for isolated resource providers [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_9.0.0\/com.ibm.websphere.nd.multiplatform.doc\/ae\/rdat_isolatedlimitations.html]"}]},{"id":"TRAIN_Q084","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)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22012983.txt","text":"Title: IBM Security Bulletin: IBM MQ clients connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it. (CVE-2018-1371) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the queue manager's amqrmppa channel process, terminating it. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2018-1371 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-1371]\nDESCRIPTION: An IBM MQ client connecting to an MQ queue manager can cause a SIGSEGV in the amqrmppa channel process terminating it.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137771 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137771] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:N\/I:N\/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V8.0 \n\n * Maintenance level 8.0.0.8\n\n\nIBM MQ V9 LTS * Maintenance level 9.0.0.2\n\n\nIBM MQ V9 CD * IBM MQ version 9.0.4\n\nREMEDIATION\/FIXES\nIBM MQ V8.0 \n\nApply FixPack 8.0.0.9 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22015103] \nIBM MQ V9 LTS * Apply FixPack 9.0.0.3 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044508]\n\n\nIBM MQ V9 CD * Upgrade to 9.0.5 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043463]\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nCHANGE HISTORY\n 01 Feb 2018: Original Version published\n13 April 2018: Added 9.0.5, 9.0.0.3 and 8.0.0.9 FixPack details \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY. \n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers"}]},{"id":"TRAIN_Q085","question":"WebSphere Business Integration (WBI) Adapter for Siebel timeouts: unable to process large orders?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21366662.txt","text":"Title: IBM How to change Siebel connection settings using the siebel.properties file in WebSphere Adapter for Siebel eBusiness Applications - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n The Siebel connection of WebSphere Adapter for Siebel eBusiness Applications is established with the default settings. You may need to modify the connection settings, such as connection timeout, according to your product environment. \n\nANSWER\nSiebel adapter uses the Siebel API (Java Data Bean) to interact with the Siebel server. The Siebel API also provides a way to configure the connection settings on the client side.\nCreate a siebel.properties file and save it in the classpath of the adapter (For example, \\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]"}]},{"id":"TRAIN_Q086","question":"I can't find the JDBC driver for my DB2.\n\nI am running BPM 8.0.1 with DB2 10.1.0.\n\n \n\nReading this technote:\nhttp:\/\/www-01.ibm.com\/support\/docview.wss\n\n\"Use the JDBC driver of your database product instead of the JDBC delivered with IBM Business Process Manager (BPM)\"I am trying to download the latest JDBC driver from the following technote:\n\nhttp:\/\/www-01.ibm.com\/support\/docview.wss\n\nIt looks like the link for the JDBC driver download for DB2 10.1.0 is greyed out. Where can I download this driver?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q087","question":"Installation manager (IIM) fails to start on AIX, generates core file from GPF even though all GTK libs are installed.\n\nTrying 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:","is_impossible":false,"contexts":[{"filename":"swg21631478.txt","text":"Title: IBM Required gtk libraries for IBM Installation Manager on AIX - United States\n\nText:\ngtk; motif TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Installation Manager requires gtk libraries to support the graphical user interface (GUI). \n\nSYMPTOM\nInstallation Manager reports errors when the gtk libraries are not installed. \n\nExamples of the reported errors:\n\n\n * SWT library could not be loaded:\n\n\n\n# .\/install\n00:00.92 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged\nCould not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)\nat org.eclipse.swt.internal.gtk.OS.(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]"}]},{"id":"TRAIN_Q088","question":"Help with Action required for SOA Policy Gateway Pattern For Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235)\n\nI need to understand details regarding \"Action required for SOA Policy Gateway Pattern For Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235)\". This vulnerability that has been referred to as \u201cGHOST\u201d. \nWhere can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q089","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affect WebSphere Enterprise Service Bus (CVE-2015-2613)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21965955.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM\u00ae Java SDK affect WebSphere Application Server that ships with WebSphere Enterprise Service Bus (CVE-2015-2613, CVE-2015-2601, CVE-2015-4749, CVE-2015-2625, CVE-2015-1931) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 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\u00ae 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."}]},{"id":"TRAIN_Q090","question":"Does ITCAM MSSQL agent support SQL Server 2017?\n\nDoes 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.","is_impossible":false,"contexts":[{"filename":"swg24044840.txt","text":"Title: IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.13-TIV-ITM_SQL-IF0001 - United States\n\nText:\nITM; SQL; ITCAM; Microsoft Applications DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2018. \n\n\nAll rights reserved.\n\nComponent: IBM(R) Tivoli(R) Composite Application Manager for Microsoft(R) Applications:\nMicrosoft(R) SQL Server Agent, Version 6.3.1.13\n\nComponent ID: 5724B96MO\n\nInterim Fix 0001, (6.3.1.13-TIV-ITM_SQL-IF0001)\n\nDate: May 14, 2018\n\nContents:\n\n1.0 General description\n2.0 Problems fixed\n3.0 Architecture and prerequisites\n4.0 Image directory contents\n5.0 Installation instructions\n6.0 Additional installation information\n7.0 Known problems and workarounds\n8.0 Additional product information\n9.0 Notices\n\n\n1.0 General description\n=======================\nThis fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below. \n\n2.0 Problems fixed\n==================\n2.1 APARS:\n-------------------\nAPAR: IJ00433\nAbstract: The collector process is crashing while accessing invalid\nparameter of the request. \nAdditional Information: Customized SQL query result attribute group\n(KOQCSQLR) request uses 3 parameters & other attribute groups use 2\nparameters. The memory for the third parameter was not handled properly.\nAnd accessing this parameter by other attribute group would result\ninto crash.\n\nAPAR: IJ00815\nAbstract: Device Detail attribute AUTOGROWTH behaviour not in sync\nwith SQL Server. \nAdditional Information: In case when data file autogrowth was disabled\nand max-size was set to unlimited, then the incorrect values were\ndisplayed for filegroup detail attribute(Max Growth Size) and device\ndetail attribute(Growth).\n\nAPAR: IJ01540\nAbstract: False alerts are being generated as default value \"Not\nCollected\" for \"Database Space Pct Used\" attribute is not correctly\nconverted before sending to TEPS.\nAdditional Information: Situations having default value\n[ Not Collected (-1 ) ] in formula were not getting evaluated correctly\nfor some database detail attributes. However, the data was shown\ncorrectly as \u2018Not Collected\u2019 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\u2018Driver\u2019 was hardcoded to \u2018SQL Server\u2018. While later on, for collecting\ndata value for 'Driver\u2019 was picked from \u2018KOQ_ODBC_DRIVER\u2019 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\u2019s 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"}]},{"id":"TRAIN_Q091","question":"Keys couldn't be imported. Unable to encrypt the FIPS key\n\nOn 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","is_impossible":false,"contexts":[{"filename":"swg21648986.txt","text":"Title: IBM Unable to decrypt the FIPS key error when exporting keys from IBM Datacap Taskmaster Capture - United States\n\nText:\ndcskey gnk; dc_KTF.xml TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to generate and\/or export keys using the dcskey command, you receive the error, \"Keys couldn't be exported. Unable to decrypt the FIPS key\" \n\nCAUSE\nEnabling the Use FIPS compliant algorithms for encryption, hashing and signing security policy can cause this error\n\nRESOLVING THE PROBLEM\nTo allow the keys to be exported properly: \n\n 1. Select Local Security Policy under Administrative tools \n 2. Navigate to Local Policies - Security Options \n 3. Select System Cryptography: Use FIPS compliant algorithms for encryption, hashing and signing and be sure it is Disabled \n 4. Run dcskey e again to export the key"}]},{"id":"TRAIN_Q092","question":"ClassCastException IlrStorePolicy$SerializedENamedElement incompatible with EStructuralFeature\n\n\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\u00ae 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\u2122.io.Serializable interface.","is_impossible":false,"contexts":[{"filename":"swg21268440.txt","text":"Title: IBM Getting java.io.NotSerializableException when SessionObjectSize counter is enabled - United States\n\nText:\njava.io.NotSerializableException SessionObjectSize counter PMI enabled disable serializable TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When PMI (Performance Monitoring Infrastructure) is enabled with SessionObjectSize counter enabled, getting NotSerializableException. The SystemOut.log shows something similar to:\n\n[4\/10\/07 5:25:42:618 EDT] 00000091 SessionContex E Exception is: java.io.NotSerializableException: com.com1.dept.nls.model.someModel \nat java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java(Compiled Code)) \n... \nat java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java(CompiledCode)) \nat com.ibm.ws.webcontainer.httpsession.SessionContextMBeanAdapter.getSessionsInfo(SessionContextMBeanAdapter.java(Compiled Code)) \nat com.ibm.ws.webcontainer.httpsession.SessionTrackingPMIApplicationData$1.getRuntimeInfo(SessionTrackingPMIApplicationData.java(Inlined Compiled Code)) ... \nat com.ibm.ws.pmi.server.modules.ServletSessionsModule$SessionObjSize.updateStatistic(ServletSessionsModule.java(Compiled Code)) \nat com.ibm.ws.pmi.server.data.SpdStatExternal.updateExternal(SpdStatExternal.java(Compiled Code)) \nat com.ibm.websphere.pmi.server.PmiAbstractModule.update(PmiAbstractModule.java(Compiled Code)) \n...\n\nThe error does not affect application functionality. Disabling SessionObjectSize counter makes the error stop occurring. \n\nCAUSE\nWebSphere\u00ae 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\u2122.io.Serializable interface.\n\n \n\nHISTORICAL NUMBER\n 53925\nL6Q\n000"}]},{"id":"TRAIN_Q093","question":"Help with Security Bulletin: WMB & IIB are affected by Open Source Tomcat vulnerability (CVE-2016-3092)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21993043.txt","text":"Title: IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by Open Source Tomcat vulnerability (CVE-2016-3092) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by Open Source Apache Tomcat vulnerability. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-3092 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-3092]\nDESCRIPTION: Apache Tomcat is vulnerable to a denial of service, caused by an error in the Apache Commons FileUpload component. By sending file upload requests, an attacker could exploit this vulnerability to cause the server to become unresponsive.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/114336 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/114336] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:N\/S:U\/C:N\/I:N\/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n IBM Integration Bus V10.0 & V9.0 \n\nWebSphere Message Broker V8.0 \n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 10.0.0.7 IBM Integration Bus V9\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 9.0.0.7 WebSphere Message Broker\nV8\nIT15719 An interim fix is available from IBM Fix Central for all platforms.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibms~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibms~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT15719]\n\nThe APAR is targeted to be available in fix pack 8.0.0.8 \nFor unsupported versions of the product, IBM recommends upgrading to a fixed, supported version\/release\/platform of the product. \n\nThe planned maintenance release dates for WebSphere Message Broker and IBM Integration Bus are available at : \nhttp:\/\/www.ibm.com\/support\/docview.wss?rs=849&uid=swg27006308 [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=849&uid=swg27006308]\n\nWORKAROUNDS AND MITIGATIONS\nNone known\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http:\/\/www.ibm.com\/systems\/z\/solutions\/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] RELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 27 Oct 2016 - Original version Published\n\n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Message Broker AIX, HP-UX, Linux, Solaris, Windows 8.0 \nPRODUCT ALIAS\/SYNONYM\n WMB IIB"}]},{"id":"TRAIN_Q094","question":"Test MDB with Multiline message.\n\n\n\nHi, I need to test my MDB injecting a multiline message into my Local WAS server. I have tried the WAS Integrated Universal Client and SIBExplorer. But the only accept on line mesage. How can I inject a multiline message into my Local WAS?\n\nI have tryid to config HermeJMS but without success.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q095","question":"When will WebSphere Application Server v7.0 and v8.0 be end of support (EOS)?\n\nHas an End of Support (EOS) date been announced for WebSphere Application Server v7.0 and 8.0? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q096","question":"How to fnd out more about performance problems in WebSphere Application Server which are in relationship with DB2? (Analyze long running sql-queries)\n\nI want to analyze a WAS\/DB2 performance problem and want to investigate the root-cause of the issue. In my WAS SystemOut.log file I noticed a lot of hanging threads that hang in java.net.SocketInputStream.socketRead0(). For example:\n\n\"WebContainer : 0\" at java\/net\/SocketInputStream.socketRead0() at java\/net\/SocketInputStream.read() at com.xyz.methodABC() ...\nThis indicates that the server still waits for result-sets from the database. So how to find out more about such db-performance-issues?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q097","question":"Too many open files error cause Portal server out of service after a restart due to Hardware failure.\n\nAfter 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","is_impossible":false,"contexts":[{"filename":"swg21067352.txt","text":"Title: IBM Too Many Open Files error message - United States\n\nText:\nwasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3\/14\/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets\/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file\/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp:\/\/www.IBM.com\/support\/docview.wss?rs=180&uid=swg21469413 [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb896653]. This tool identifies the open handles\/files associated with the Java\u2122 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"}]},{"id":"TRAIN_Q098","question":"Restore JazzSM DASH login page to default images\n\nWe'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.","is_impossible":false,"contexts":[{"filename":"swg21902654.txt","text":"Title: IBM Restoring missing xml files from backup in DASH - United States\n\nText:\nDASHL2; DASHL2FAQ; restore; backup; xml; WEB-INF TECHNOTE (FAQ)\n\nQUESTION\n How can I restore missing or corrupted xml files in the WEB-INF directory, (such as the navigation.xml, portletEntities.xml, etc.) from backup in Dashboard Application Service Hub (DASH) ? \n\nCAUSE\nSome of these files could have gotten corrupted. \n\nANSWER\nDASH makes a backup copy of the WEB-INF configuration\/custom xml files in the backups directory. These files are very useful if any of these files get corrupted. \n\nPlease follow below steps to restore files from the backups directory: \n\n1. Stop the DASH server \n\n2. Make a backup copy of the current xml files in the following directory: \n\n\/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_Q099","question":"Migrating a Rule Project to JRules v7.0 and v7.1\n\nHow do I migrate a rule project to JRules v7.0 and v7.1? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q100","question":"Which version of TBSM support ITM 6.3?\n\nWhat 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","is_impossible":false,"contexts":[{"filename":"swg24039742.txt","text":"Title: IBM Tivoli Business Service Manager V6.1.1 Fix Pack 3(6.1.1-TIV-BSM-FP0003) - United States\n\nText:\n 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\u00ae\nTivoli\u00ae 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\u00ae | 6.1.1-TIV-BSM-FP0003-aix.tar |\n| | |\n+---------+----------------------------------------------------------------+\n| Linux\u00ae | 6.1.1-TIV-BSM-FP0003-linux.tar |\n| | |\n+---------+----------------------------------------------------------------+ \n| Solaris | 6.1.1-TIV-BSM-FP0003-solaris.tar |\n| | |\n+---------+----------------------------------------------------------------+\n| Windows\u00ae| 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\u00ae : .\/setup-.bin \n\nConsole mode\nUse the -i console option. \nFor example -\nWindows: setup-windows.exe -i console\n\nor \n\nUNIX\u00ae : .\/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\u00ae :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\u00ae 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\u00ae, Windows, and Windows Server are trademarks of Microsoft\nCorporation in the United States, other countries, or both.\n\nIntel\u00ae, Intel logo, Intel Inside\u00ae, Intel Inside logo, Intel\u00ae Centrino\u00ae,\nIntel Centrino logo, Celeron\u00ae, Intel Xeon\u00ae, Intel SpeedStep\u00ae, Itanium\u00ae,\nand Pentium\u00ae 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\u00ae 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\u00ae : .\/setup-.bin \n\nConsole mode\nUse the -i console option. \nFor example -\nWindows: setup-windows.exe -i console\n\nor \n\nUNIX\u00ae : .\/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\u00ae :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"}]},{"id":"TRAIN_Q101","question":"Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc\n\n\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 .","is_impossible":false,"contexts":[{"filename":"swg22009818.txt","text":"Title: IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What can cause an STAP to fail to connect properly - I get the following messages in the logs:-\n\n\/tmp\/guard_stap.stderr.txt on the DB Server :-\n\"Server 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]"}]},{"id":"TRAIN_Q102","question":"How to run BPMProcessInstancesCleanup script faster\n\n\n\nBPMProcessInstancesCleanup deletes only 15-60 completed instances per minute. How do we make it delete instances faster. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q103","question":"PARMGEN ABEND S013 in JOB KCIJPALO\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg27050456.txt","text":"Title: IBM Important Information about the WebSphere MQ Configuration Agent, Withdrawn from IBM OMEGAMON for Messaging on z\/OS V7.5 - United States\n\nText:\n 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\u00b7 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\u00b7 PARMGEN: In your PARMGEN configuration for each runtime environment, does the \u201cInclude Products in this PARMGEN RTE panel (KCIP@PGI)\u201d (under step \u201c1 KCIJPCFG Set-up\/Refresh PARMGEN work environment\u201d navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), have the line for \u201cKMC OMEGAMON for Messaging \u2013 WebSphere MQ Configuration\u201d selected for configuration in the environment? \n\nIf the answers are \u201cyes\u201d 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 \u201cConfiguration\u201d 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 \u201cConfigure\u201d 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 \u201c+\u201d 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 \u201c\u201d\nKMQ_AGT_STC \u201c\u201d\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 \u201c\u201d \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 \u2013 KMQ Agent-only address space in the RTE\u2019s 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 \u201cInclude Products in this PARMGEN RTE panel (KCIP@PGI)\u201d (under step \u201c1 KCIJPCFG Set-up\/Refresh PARMGEN work environment\u201d navigation from the PARAMETER GENERATOR (PARMGEN) WORKFLOW - PRIMARY OPTION MENU), deselect the line with \u201cKMC OMEGAMON for Messaging \u2013 WebSphere MQ Configuration\u201d 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\u2019s 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 \u201c\u201d\nKMQ_AGT_STC OMEGMQ\nKMQ_AGT_STC_OWNER \u201c\u201d\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"}]},{"id":"TRAIN_Q104","question":"Updating SCA applications & internal SCA module queues\n\n\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\u2122 virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.","is_impossible":false,"contexts":[{"filename":"swg21639375.txt","text":"Title: 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\n\nText:\nSCA.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\u2122 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"}]},{"id":"TRAIN_Q105","question":"JD Edwards Adapter supported in BPM 8.5.6?\n\nHi experts, I have a question about the support for the JD Edwards Adapter in BPM 8.5.6, because the Infocenter for BPM 8.5.6 doesn't have a detailed explanation for this adapter unlike infocenter for BPM 8.5.5, I just wondering if it's only an oversight in Infocenter.\n\n\nI am asking this because I have a BPM opportunity for a client that uses JD Edwards and I want to be sure that this adapter can be used.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q106","question":"Help with Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21968399.txt","text":"Title: IBM Security Bulletin: IBM WebSphere MQ MQXR insecure passwords (CVE-2015-2012) - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q107","question":"How to increase the HTTP Session time-out value for Workplace application on WebSphere Application Server?\n\nWe 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","is_impossible":false,"contexts":[{"filename":"swg21163875.txt","text":"Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\u00ae WebSphere\u00ae 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 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \n * \u00a0 \u00a0 \u00a0 \u00a0 \u00a060<\/session-timeout>\n * \n * \u00a0 \u00a0 \u00a0 <\/session-config>\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"}]},{"id":"TRAIN_Q108","question":"Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21959745.txt","text":"Title: IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q109","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg22011696.txt","text":"Title: IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States\n\nText:\nIIB 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"}]},{"id":"TRAIN_Q110","question":"Why does my install of the latest Installation Manager on a Linux Ingram Server not function?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21308281.txt","text":"Title: IBM Installing the Installation Manager on an NFS mounted disk - United States\n\nText:\nNFS; remote drive; mount drive ; 1308281 TECHNOTE (FAQ)\n\nQUESTION\n Can IBM\u00ae Installation Manager be installed on a UNIX\u00ae or Linux\u00ae NFS mounted disk? \n\nANSWER\nDo not install the IBM Installation Manager on an NFS mounted disk. \n\nOn AIX\u00ae 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."}]},{"id":"TRAIN_Q111","question":"How to find details of Corrupted Object from the entries in db2diag.log?\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21983129.txt","text":"Title: IBM How to find details of Corrupted Object from the entries in db2diag.log? - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q112","question":"WAS 8.5.x - Writing a JMS message to a remote queue takes a long time. How to write the message faster?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21624731.txt","text":"Title: IBM JMSExceptions CWSIT0006E and CWSIA0241E on bus connect - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q113","question":"How do I configure logging for Atlas Extensions in Atlas 6.0.3.3?\n\nHow 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","is_impossible":false,"contexts":[{"filename":"swg21981881.txt","text":"Title: IBM Configuring logging for Atlas Extensions in Atlas 6.0.3.3 - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q114","question":"Help with Security Bulletin: IIB & WMB upon installation, set incorrect permissions for an object ( CVE-2016-0394 )\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21985013.txt","text":"Title: 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\n\nText:\nWMB 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"}]},{"id":"TRAIN_Q115","question":"AIX APARs required when installing\/upgrading to IIB 10.0\/10.0.0.1\n\nThe system requirements for IBM Integration Bus 10.0 on AIX states that I need to be running the following AIX APARs:\n\nFor AIX 6.1 TL9 plus APARS IV65761 & IV68449For AIX 7.1 TL3 plus APARS IV65758 & IV67977\n\nSystem requirements for IBM Integration Bus 10.0http:\/\/www-969.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProductdeliverableId=1376392102308&osPlatform=AIX# !\n\nHow can I get access to these apars?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q116","question":"Why does my upgrade to Portal 8001 CF14 fail with the following errors, ADMA5008E, ADMA0063E, ADMA5069E, WASX7017E?\n\nWhy 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.","is_impossible":false,"contexts":[{"filename":"swg21426787.txt","text":"Title: IBM Portal upgrades fail during ejbdeploy with 'Error is Platform not running' message - United States\n\nText:\n7001eGA 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 *"}]},{"id":"TRAIN_Q117","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?\n\nThese 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.","is_impossible":false,"contexts":[{"filename":"swg21695094.txt","text":"Title: 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\n\nText:\n 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"}]},{"id":"TRAIN_Q118","question":"Installation of Portal 7.0 CF fails with version mismatch\n\n\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","is_impossible":false,"contexts":[{"filename":"swg27023910.txt","text":"Title: IBM WebSphere Portal 7.0.0.2 Combined Cumulative Fix Readme - stand-alone - United States\n\nText:\nWPWCMCF 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"}]},{"id":"TRAIN_Q119","question":"How do I change from shared to unshared connection?\n\nin WAS, how do I change from shared to unshared connection. I am seeing connections max out and take a long time to release.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q120","question":"I am receiving AC power supply failures on my DataPower 9235 appliance. How can I resolve this?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21512291.txt","text":"Title: IBM WebSphere DataPower M\/T 9235 appliance might incorrectly report failure of both power supplies - United States\n\nText:\n 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 \u2192 System Control \u2192 In the \u201cShutdown\u201d section choose \u201cReboot System\u201d then click \u201cShutdown\u201d \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"}]},{"id":"TRAIN_Q121","question":"ncp_poller failed with Out-of-memory in ITNM 3.9 FP4+IF1. What went wrong?.\n\n\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;","is_impossible":false,"contexts":[{"filename":"swg21514810.txt","text":"Title: IBM Default number of threads for ncp_poller - United States\n\nText:\nAvailable 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;"}]},{"id":"TRAIN_Q122","question":"Why Theme Updates are not updated in the browser cache ?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21647572.txt","text":"Title: IBM Some portal resources have been updated, however a long cache was set so the updates are not being served. - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q123","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. 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\u2122 virtual machine (JVM) property for the module. Set the property to false to preserve SCA destinations.","is_impossible":false,"contexts":[{"filename":"swg21639375.txt","text":"Title: 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\n\nText:\nSCA.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\u2122 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"}]},{"id":"TRAIN_Q124","question":"Portal v8.5 install fails with INSTCONFFAILED - No Portral logs are written\n\nIf 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.","is_impossible":false,"contexts":[{"filename":"swg1PI37248.txt","text":"Title: IBM PI37248: A PROPERTY FILE BASED CONFIGURATION (PFBC) FILE MIGHT FAIL TO AP PLY. - United States\n\nText:\n FIXES ARE AVAILABLE\n8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040035]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040425]\n8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040533]\n8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041178]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041590]\n8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041819]\n8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042150]\n8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043005]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042746]\n8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043844]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044096]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044479]\n8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044734]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * A PFBC file might fail to apply. Wsadmin will show an error\n similar to this:\n \n java.lang.Exception: java.lang.Exception: ADMG0660E:\n Properties File Validation during command\n applyConfigProperties failed. See Report file for details.\n \n The report file will contain an error similar to this:\n Error=java.lang.NullPointerException\n at\n com.ibm.websphere.management.configservice.ConfigServiceHelper.g\n etConfigDataType(ConfigServiceHelper.java:235)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getType(Work\n spaceHelper.java:563)\n at\n com.ibm.ws.management.configservice.WorkspaceHelper.getDelegator\n (WorkspaceHelper.java:584)\n at\n com.ibm.ws.management.configservice.ConfigServiceImpl.getAttribu\n tes(ConfigServiceImpl.java:2102)\n at\n com.ibm.ws.management.commands.properties.resources.common.Apply\n Properties.setProperties(ApplyProperties.java:240)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Property File Based Configuration *\n ****************************************************************\n * PROBLEM DESCRIPTION: A Property File Based Configuration *\n * (PFBC) file might fail to apply. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n A recent (8.5.5.5) parser change introduced a problem where\n types that have default values noted in the file and are not\n Strings can be incorrectly processed. For example:\n isolatedClassLoader=false #boolean,default(false)\n might be incorrectly processed, and as a result, the file\n might not apply.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The parsing code is updated so the problem no longer occurs.\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.6. Please refer to the Recommended Updates\n page for delivery information:\n http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980 [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980]\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI37248\n \n \n * REPORTED COMPONENT NAME\n WEBS APP SERV N\n \n \n * REPORTED COMPONENT ID\n 5724H8800\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt \/ Xsystem\n \n \n * SUBMITTED DATE\n 2015-03-18\n \n \n * CLOSED DATE\n 2015-03-20\n \n \n * LAST MODIFIED DATE\n 2015-03-24\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBS APP SERV N\n \n \n * FIXED COMPONENT ID\n 5724H8800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"}]},{"id":"TRAIN_Q125","question":"completeness report causes StackOverflowError in Decision Center\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21162896.txt","text":"Title: IBM Diagnosing a java.lang.StackOverflowError - United States\n\nText:\nStackOverflow; 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\u2122 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"}]},{"id":"TRAIN_Q126","question":"Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22003510.txt","text":"Title: IBM Security Bulletin: Incorrect saved channel status enquiry could cause denial of service for IBM MQ (CVE-2017-1236) - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q127","question":"How precise is DataPower's backside persistent timeout value related to intermittent \"Failed to Process Response Headers\" error messages?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21292808.txt","text":"Title: IBM How to troubleshoot the error \"Failed to process response headers\" - United States\n\nText:\ndatapower; 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\u00ae DataPower device\u00ae 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\u00ae.\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."}]},{"id":"TRAIN_Q128","question":"ICC Configuration Store Service is hung?\n\nICC 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.","is_impossible":false,"contexts":[{"filename":"swg21680391.txt","text":"Title: IBM Content Collector Configuration Store is corrupted - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q129","question":"How do I identify Indexing errors in Atlas database?\n\nHow 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","is_impossible":false,"contexts":[{"filename":"swg21982458.txt","text":"Title: IBM Identifying Indexing errors in Atlas database - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q130","question":"Upgrading to 7.7.x while using APIC v5 with DataPower?\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21246298.txt","text":"Title: IBM DataPower Gateways Firmware Support Lifecycle - United States\n\nText:\ndatapower;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\u00ae DataPower\u00ae 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]"}]},{"id":"TRAIN_Q131","question":"Is it possible to move all the P8 logs out of the default location?\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21994039.txt","text":"Title: IBM How to override the directory location for IBM P8 Content Platform Engine (CPE) logs. - United States\n\nText:\n 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 *"}]},{"id":"TRAIN_Q132","question":"How can I format a trace for CMOD v9.0 on Windows?\n\nHow 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.","is_impossible":false,"contexts":[{"filename":"swg21661918.txt","text":"Title: 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\n\nText:\nserver 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]"}]},{"id":"TRAIN_Q133","question":"DFHXS1201 when using ATS after applying RSU1412 to CICS TS 5.2 or 5.1\n\nWhy would I start receiving signon error DFHXS1201 after applying the PTFs in Recommended Service Update RSU1412 to CICS Transaction Server for z\/OS (CICS TS) V5.2 or V5.1? The terminal is autoinstalled, then automatically signed on by CA Top Secret using Automated Terminal Signon (ATS). This is the error message I receive: \nDFHXS1201 The password supplied in the verification request for userid userid was invalid. This occurred in transaction CSGM when userid userid was signed on at netname netname.\nThe only difference in a region without the maintenance is that the last message seen is the DFHSN1100 indicating that the terminal was successfully signed on. In the region with the error, there is an extra XS0601 trace entry for INQUIRE PASSWORD that is failing, which causes the sign-on to fail and prevents the automation from running.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q134","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\n\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).","is_impossible":false,"contexts":[{"filename":"swg21600618.txt","text":"Title: IBM web server Plugin may need LD_LIBRARY_PATH when used with Apache 2.2 - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q135","question":"WAS runtime classpath does not match WAS Server Runtime library in RAD\n\n 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.","is_impossible":false,"contexts":[{"filename":"swg21497604.txt","text":"Title: IBM NoClassDefFoundError running Java class selected from server plugin jar - United States\n\nText:\nwid; 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\u2122 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."}]},{"id":"TRAIN_Q136","question":"Unexpected instance name for SQL Server agent after FP10\n\n\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\u201d pane discovers and shows one instance with name \u201cMSSQLSERVER\u201d 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.","is_impossible":false,"contexts":[{"filename":"swg24041994.txt","text":"Title: IBM ITCAM for Microsoft (R) App : SQL Server 6.3.1.8-TIV-ITM_SQL-IF0001 - United States\n\nText:\nKOQ; 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"}]},{"id":"TRAIN_Q137","question":"What could cause a \"Connection refused\" to SQLDB\/DB2 after some time?\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21443723.txt","text":"Title: IBM ERRORCODE=-4499, The application server rejected establishment of the connection. - United States\n\nText:\n-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]"}]},{"id":"TRAIN_Q138","question":"can Datacap support to Arabic language?\n\ncan Datacap support to Arabic language?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q139","question":"Help with Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WMB & IIB (CVE-2015-7575)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21975233.txt","text":"Title: IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects WebSphere Message Broker and IBM Integration Bus (CVE-2015-7575) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n The MD5 \u201cSLOTH\u201d 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"}]},{"id":"TRAIN_Q140","question":"A .NET API error is thrown when attempting to install ICC 4.0.1\n\nA .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.","is_impossible":false,"contexts":[{"filename":"swg21971485.txt","text":"Title: IBM .NET API error when installing IBM Content Collector (ICC) 4.0.1 - United States\n\nText:\nICC; .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."}]},{"id":"TRAIN_Q141","question":"How do I downgrade an IBM Gateway, DataPower, appliance to a lower major firmware release?\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21244384.txt","text":"Title: IBM Using the \"reinitialize\" CLI command to reconfigure an appliance. - United States\n\nText:\ndatapower; 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"}]},{"id":"TRAIN_Q142","question":"DataPower upgrade Loading firmware failed: Insufficient flash space available.\n\nI am trying to upgrade my M\/T 9235 DataPower Gateway Appliance and am receiving the message(s) similar to:\nError performing that action! Could not install firmware image. Loading firmware failed: Preserve user modified data failed: Insufficient flash space available System will NOT reboot. \nOR\n\"Loading firmware failed: Insufficient flash space available.\"\nHow can I resolve this? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q143","question":"I do not have an authorization code to license my copy of SPSS, where can I get one?\n\nEither I was never given an authorization code or I have lost mine and need to get one, can you help me get one? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q144","question":"Help with Security Bulletin: The WebAdmin context for WMB V8 allows directory listings (CVE-2016-6080)\n\n\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)","is_impossible":false,"contexts":[{"filename":"swg21995004.txt","text":"Title: IBM Security Bulletin: The WebAdmin context for WebSphere Message Broker Version 8 allows directory listings (CVE-2016-6080) - United States\n\nText:\nWMB 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"}]},{"id":"TRAIN_Q145","question":"How can I obtain a Java thread dump against an execution group in IIB v10?\n\n\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 ","is_impossible":false,"contexts":[{"filename":"swg21618139.txt","text":"Title: IBM Generating Java diagnostic dumps for IBM Integration Bus - United States\n\nText:\nmqiinfo; 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"}]},{"id":"TRAIN_Q146","question":"Why am I seeing native out of memory issues on a 64-bit system?\n\nI have a 64-bit Java installed on my Portal server. On occasion I'm seeing the Portal server processID disappear across any one of my servers running in the clusters. Portal restarts no problem and runs fine, but the processID disappears. \nLogs aren't showing any errors. Did see the following in a javacore or two that was generated: \"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\" Failed to create a thread: retVal -1073741830, errno 11. reporting\nWhy is this happening? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q147","question":"We specify the sslProtocol for an Execution Group via \"-n sslProtocol -v TLS\" as per following: mqsichangeproperties \"-o HTTPSConnector\" \"-n sslProtocol -v TLS\"\n\nDoes WMB support TLS v1.1 protocol or TLS v1.2?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q148","question":"Help with Action required for Hypervisor Editions of IIB V9 & WMB 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. Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q149","question":"How do I correct a BIP3701E: INVALID_CHARACTER_ERR I'm getting on deploy?\n\nReceiving a\nBIP3701E: A Java exception was thrown whilst calling the Java JNI method ''AdminAgentThread_getDeployMessage''. The Java exception was ''org.w3c.dom.DOMException: INVALID_CHARACTER_ERR: An invalid or illegal XML character is specified. ''\non deploy. What is wrong? The knowledge center just states I need to correct the error. What is the invalid character?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q150","question":"Error: \"MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION\" occurs at portal startup\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg1PI34677.txt","text":"Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States\n\nText:\n A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications \/ value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions\n \n \n \n \n \n\nLOCAL FIX\n * 1) open the WAS admin console\n 2) navigate to Resources > Resource environment providers > WP\n ScriptingService > Custom properties\n 3) you should see an entry with the name\n \"ServerExt.applications\" and value\n \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"\n 4) delete this entry, save and restart the server.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 05 (PI31198 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI31198]) for Portal\n 8.5.0.0 available from Fix Central:\n \n http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent\n =ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al]\n l&platform=All&function=aparId&apars=PI31198\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added a task to remove the outdate resource environment\n provider entry.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI34677\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-02-10\n \n \n * CLOSED DATE\n 2015-03-10\n \n \n * LAST MODIFIED DATE\n 2015-03-10\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * FIXED COMPONENT ID\n 5724E7600\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"}]},{"id":"TRAIN_Q151","question":"Does IBM DataPower Gateway Appliance support the HTTP CONNECT method?\n\nDoes 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","is_impossible":false,"contexts":[{"filename":"swg21612222.txt","text":"Title: IBM How to Proxy SSL request from DataPower to Remote Proxy Server? - United States\n\nText:\nForward 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."}]},{"id":"TRAIN_Q152","question":"EIF probe not receiving itm events\n\nWhy 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.","is_impossible":false,"contexts":[{"filename":"swg21978641.txt","text":"Title: IBM EIF probe not receiving itm events - United States\n\nText:\nom_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)"}]},{"id":"TRAIN_Q153","question":"What version of ITCAM for MQ agent supports MQ v9.1?\n\n\n\nI will be looking at MQ v9.1 that has recently become GA. What version of the ITCAM MQ monitoring agent supports this version of MQ?\n\nI have v7.30 FP2 of the WebSphere MQ Monitoring Agent for AIX, LINUX and Windows. Do you think that version support MQ v9.1?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q154","question":"IBM SPSS Statistics Subscription Installer not supported on Mac OS version OS X 10.9.5\n\nAttempted 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.","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q155","question":"Is it possible to make where filter to case insensitive in My Inbox?\n\nWorkplace 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.","is_impossible":false,"contexts":[{"filename":"swg21987296.txt","text":"Title: IBM Case insensitive searches in IBM Content Navigator - United States\n\nText:\nICN 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."}]},{"id":"TRAIN_Q156","question":"TLS protocol with ITCAM for Datapower\n\nWe have a DataPower appliance with TLS security protocol enabled. Can we configure ITCAM for DataPower appliance v7.1 to specifically use the TLS protocol v1.2 (not v1.0)?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q157","question":"Help with Security Bulletin: IBM WebSphere MQ 7.0.1 potential denial of service (CVE-2015-2013)\n\nI need to understand details regarding Security Bulletin: IBM WebSphere MQ 7.0.1 potential denial of service (CVE-2015-2013). Where can I find this information?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q158","question":"Why are my IBM FileNet Workplace XT war and ear files are unusually small?\n\nWhen 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.","is_impossible":false,"contexts":[{"filename":"swg22002443.txt","text":"Title: IBM FileNet Workplace XT war and ear files are unusually small - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q159","question":"Why can't IBM FileNet Content Platform Engine successfully connect to IBM FileNet Content Search Services?\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg22002444.txt","text":"Title: 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\n\nText:\n 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"}]},{"id":"TRAIN_Q160","question":"DSNT408I SQLCODE -401 creating stored procedure CIUSNTSR after upgrading to DB2 11\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg1PI19804.txt","text":"Title: IBM PI19804: SQLCODE401 FROM DSNXOBFC FOR A SQL PROCEDURE WHEN USING INLIST IN IF STATEMENT - United States\n\nText:\nz\/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."}]},{"id":"TRAIN_Q161","question":"Problems making XA connection from WMQ to WAS using a CCDT\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21249798.txt","text":"Title: IBM MQJMS1068 error occurs when trying to create an XA connection from WebSphere Application Server to MQ - United States\n\nText:\nMQPRB MQPRB3189 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to create an XA connection to WebSphere\u00ae 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"}]},{"id":"TRAIN_Q162","question":"Crash happened due to \"PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577)\"\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg24041394.txt","text":"Title: IBM PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) - United States\n\nText:\nPI50993; 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"}]},{"id":"TRAIN_Q163","question":"Whether IBM Case Manager is using Apache Struts?\n\nWhether IBM Case Manager is using Apache Struts?","answer":"IBM Content Navigator is not vulnerable to the Apache Struts 2.x Vulnerability.","is_impossible":false,"contexts":[{"filename":"swg22000563.txt","text":"Title: IBM Content Navigator is not affected by the Apache Struts 2.x Vulnerability (CVE-2017-5638) - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q164","question":"Rulerunner Sleep For:\n\n\n\nI have configured Rulerunner to sleep for 3 seconds between tasks but it continues to use the default setting of 10 seconds.\n\nAny ideas on why my setting of 3 seconds is not being used?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q165","question":"Is Java 8 supported for EJBDeploy on WebSphere Application Server 8.5.5.9 or later?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21994741.txt","text":"Title: IBM Learning more about EJBDeploy - United States\n\nText:\nEJB; 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\u00ae 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."}]},{"id":"TRAIN_Q166","question":"Application code is overriding session timeout in WebSphere Application Server 7.0\n\nHow 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.","is_impossible":false,"contexts":[{"filename":"swg21192604.txt","text":"Title: IBM MustGather: Sessions and session management problems in WebSphere Application Server - United States\n\nText:\nMustGather; 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"}]},{"id":"TRAIN_Q167","question":"ITCAM for J2EE 7.11 part numbers\n\nWhat are the names, part numbers, sizes and posting dates for ITCAM for J2EE v7.1.1.0 installation images on all supported platforms?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q168","question":"Help with Security Bulletin: Integration server HTTP listener exposes stack trace in WMB & IIB (CVE-2016-2961)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21985017.txt","text":"Title: IBM Security Bulletin: Integration server HTTP listener exposes stack trace in WebSphere Message Broker and IBM Integration Bus - United States\n\nText:\nWMB 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"}]},{"id":"TRAIN_Q169","question":"What is right trace for investigate the \"CWTKE0021W: The expired people assignment (staff query result) cannot be refreshed\" in SystemOut.log\n\nHello, after upgrading from Websphere Process Server 7 to Business Process Manager Advanced - Process Server 8.5.6 we are seeing many CWTKE0021W in the SystemOut.log on two different test environments. We use Standalone LDAP repository.\nAccording to very brief (none) description at http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SS9KLH_8.5.6\/com.ibm.wbpm.ref.doc\/CWTKE0021W.html there should be further info in SystemOut.log (some exception I suppose) but in our case there is not - the logs are clear, the CWTKE0021W is only information. AFAIK we are not aware of any problems with our staff queries, so far it is only disturbing message in the logs but we want to get rid of them before we hit production with 8.5.6.\nI found the http:\/\/www-01.ibm.com\/support\/docview.wss but I guess that is not our case, we dont see any timeout messages in the logs.\nI wanted to enable the trace but Im not sure what trace string to use, there are many trace code packages which I consider as candidates (com.ibm.task., com.ibm.bpe.staff., com.ibm.bpe.query.*) but those enviroments are heavily used so I dont want to blindly enable all as I need to make smallest performance impact as possible.\nPlease could you advice with right trace string to use (or other means for resolving the problem without the traces) ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q170","question":"MQSeries Events correlation\n\nHow 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.","is_impossible":false,"contexts":[{"filename":"swg21391724.txt","text":"Title: IBM Flush Out Old Entries in the MQSeries Events Workspace - United States\n\nText:\nMQSeries 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."}]},{"id":"TRAIN_Q171","question":"Help with Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21700633.txt","text":"Title: IBM Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2014-8730) - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q172","question":"Does StoredIQ support TLS v1.2?\n\nDoes 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","is_impossible":false,"contexts":[{"filename":"swg21998312.txt","text":"Title: IBM StoredIQ support for TLS v1.2 - United States\n\nText:\nStoredIQ 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"}]},{"id":"TRAIN_Q173","question":"How to use the LIKE operator, wildcard and special characters in your IBM FileNet Content Platform Engine Sweep's Filter Expression?\n\nHow to use the LIKE operator, wildcard and special characters in your IBM FileNet Content Platform Engine Sweep's Filter Expression? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q174","question":"Can not create a portal wcm syndicator-subscriber pair. The \"Subscribe Now\" window pops up but is blank or corrupted. Why?\n\nCan 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.","is_impossible":false,"contexts":[{"filename":"swg21445801.txt","text":"Title: IBM WCM page and authoring portlet may not display after migration - United States\n\nText:\nWPv7000eGA; 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"}]},{"id":"TRAIN_Q175","question":"Clustering Decision Validation Services\n\nHow can we cluster Decision Validation Services (DVS)? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q176","question":"JD Edwards Adapter supported in BPM 8.5.6?\n\nHi experts, I have a question about the support for the JD Edwards Adapter in BPM 8.5.6: which is the most current version of JD Edwards supported in this Adapter ?\n\nI am asking this because I have a BPM opportunity for a client that uses JD Edwards and I want to be sure that this adapter can be used.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q177","question":"Help with installing the latest version of Portal 8.5 on AIX\n\nWe are planning to install the latest WebSphere Portal 8.5x on AIX 7.0 with DB2 Where can I find the step by step installation procedure?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q178","question":"ILMT agent doesn`t show the hostname on inventory hardware\n\nHello 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.","is_impossible":false,"contexts":[{"filename":"swg21977398.txt","text":"Title: IBM After restoring BigFix server database, ILMT\/BFI\/SUA server may not import all the data since the restore correctly - United States\n\nText:\nsequance 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"}]},{"id":"TRAIN_Q179","question":"What is the difference between the software available in Passport Advantage and Fix Central?\n\nIs it possible to get IIB General Availability (GA) code from somewhere else or is it only available on Passport Advantage?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q180","question":"How to download IBM MQ ?\n\nHow and where to download IBM MQ V8 or IBM Websphere MQ V7.1 or 7.5 for production environment ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q181","question":"Problem with EJB WebService and empty beans.xml in META-INF directory\n\nWhen using a EJB WebService (EAR file attached) with a empty beans.xml file in the META-INF directory (my intent is to use CDI), the project can be deployed correctly, but when the EJB WebService is called, I get the following error message:\n[24\/04\/14 21:33:34:913 CEST] 0000003b id= com.ibm.ws.webbeans.WebBeansInitializer E An error occured while starting application context path : [\/SampleEJBWebService] [24\/04\/14 21:33:35:028 CEST] 0000003b id= com.ibm.ws.logging.internal.impl.IncidentImpl I FFDC1015I: An FFDC Incident has been created: \"java.lang.NullPointerException com.ibm.ws.webcontainer.osgi.VirtualHost startWebApp\" at ffdc_14.04.24_21.33.34.0.log\nWhen I remove the beans.xml file, everything works fine without any problems.\nNow my question is: Are there any workarounds available?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q182","question":"ITCAM J2EE configuration problem with Tomcat as a Windows Service\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21961542.txt","text":"Title: IBM Configuring the Tomcat Data Collector to run as a Windows service - United States\n\nText:\nITCAM; 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\u2122 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."}]},{"id":"TRAIN_Q183","question":"Why is the StoredIQ Dataserver login page not coming up in the browser?\n\nWhy 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","is_impossible":false,"contexts":[{"filename":"swg22001607.txt","text":"Title: IBM StoredIQ Dataserver login page is not coming up in the browser - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q184","question":"I am trying to install Portal 8.5 on Windows and getting error, CRIMA1217E in the IIM logs\n\nWhile 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","is_impossible":false,"contexts":[{"filename":"swg21701478.txt","text":"Title: 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\n\nText:\n 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: <\/message>\n<\/entry>\n\nglobal<\/logger>\ncom.ibm.cic.agent.internal.core.IMLoggerImpl<\/class>\ninfo<\/method>\nReset current process umask from 022 to 022.<\/message>\n<\/entry>\n\ncom.ibm.cic.common.logging.LogManager<\/logger>\norg.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory\n<\/class>\nsafeLogged<\/method>\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.<\/key>\n\n\/opt\/wps85\/scm\/PortalServer\/installer\/wp.config\/wizard\/repository\/r\nepository_actions.xml<\/arg>\n<\/message>\n<\/entry>\n<\/log>\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"}]},{"id":"TRAIN_Q185","question":"After increasing the number of mq clients connections to over 10k, FDCs with probe id XC035040 are logged and no further client connections can be established.\n\nWhy are FDCs reporting probe id XC035040 after adding 1000 mq client connections to the mq server ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q186","question":"IBM SPSS Statistics 25.0.0.1 MacOS 10.13 High Sierra.\n\nWill 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.","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q187","question":"How to resolve coach service timeout or expired issue?\n\nCustomer 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.","is_impossible":false,"contexts":[{"filename":"swg21163875.txt","text":"Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\u00ae WebSphere\u00ae 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 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \n * \u00a0 \u00a0 \u00a0 \u00a0 \u00a060<\/session-timeout>\n * \n * \u00a0 \u00a0 \u00a0 <\/session-config>\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"}]},{"id":"TRAIN_Q188","question":"How can I get detailed JazzSM PAGE and Widget release information.\n\nHow 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.","is_impossible":false,"contexts":[{"filename":"swg21976068.txt","text":"Title: IBM Gathering detailed JazzSM Page and Widget information - United States\n\nText:\nDASHL2FAQ; 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]"}]},{"id":"TRAIN_Q189","question":"Is using a monitored JBoss server with ITCAM supported in a Windows Service?\n\nIs 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","is_impossible":false,"contexts":[{"filename":"swg21967756.txt","text":"Title: IBM Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? - United States\n\nText:\nJ2EE 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"}]},{"id":"TRAIN_Q190","question":"Does anyone know how to disable HTTPS to HTTP redirection for BPC Explorer?\n\n\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].","is_impossible":false,"contexts":[{"filename":"swg24034421.txt","text":"Title: IBM Switching Business Process Choreographer Explorer back to using HTTP from HTTPS - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q191","question":"Help with Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WebSphere Remote Server (CVE-2014-8917)\n\nI need to understand details regarding Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WebSphere Remote Server (CVE-2014-8917). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q192","question":"What are the recommended configuration settings (best practices) for a TSAMP controlled DB2 HA \/ HADR cluster?\n\nWhen using TSAMP to control a DB2 shared disk or HADR cluster, what are the best practices that would allow for greatest reliability & stability?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q193","question":"IBM Security announces a new online Support experience that is coming soon!\n\nWhat 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.","is_impossible":false,"contexts":[{"filename":"swg22009938.txt","text":"Title: IBM New IBM License Metric Tool online Support experience! - United States\n\nText:\n 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\u2019ve 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 \u201cCases\u201d in the new experience. Simply choose \u201ccases\u201d 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 \u201cEmail IBM Support\u201d, 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"}]},{"id":"TRAIN_Q194","question":"Is there a support's guide to the CORBA Probes?\n\nIs there a support's guide to the IBM CORBA probes?","answer":"GENERIC_CORBA_SupportsGuide_20.pdf","is_impossible":false,"contexts":[{"filename":"swg21614208.txt","text":"Title: IBM Support's Guide to IBM CORBA probes - United States\n\nText:\ncorba; 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]"}]},{"id":"TRAIN_Q195","question":"How to resolve \"StringIndexOutOfBoundsException = null\"\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg27046676.txt","text":"Title: IBM When importing a projects.csv file, the COORDINATOR column must be in the loginId:Role format. - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q196","question":"Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735)\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735). What is th efix for MQ 8?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q197","question":"Out of memory exception when copying large tables in RSO\n\nWe need to import an Excel table with 23,000 lines into an ODM Decision Table. We've tried using Excel (Rule Solutions for Office) but the Copy fails with an error message GBOC0014E indicating a System.OutOfMemoryException. Is this expected? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q198","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)\n\nI 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","is_impossible":false,"contexts":[{"filename":"swg22013088.txt","text":"Title: 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\n\nText:\n 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."}]},{"id":"TRAIN_Q199","question":"How to start PC DMgr as a Windows service?\n\n 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.","is_impossible":false,"contexts":[{"filename":"swg21397335.txt","text":"Title: IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States\n\nText:\nwasservice; 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."}]},{"id":"TRAIN_Q200","question":"How do I configure WebSphere Portal with OpenLDAP?\n\nHow do I configure WebSphere Portal with OpenLDAP?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q201","question":"The config task wp-add-property is failing with \"Can not find EJB\" message while running on our Portal 8.5 cluster\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21365841.txt","text":"Title: IBM EJB WIMServiceHome cannot be found even after .ear file is installed successfully - United States\n\nText:\n 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<\/deployedApplcations>\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]"}]},{"id":"TRAIN_Q202","question":"How to find if Table was Created as NOT LOGGED INITIALLY?\n\nHow 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 ","is_impossible":false,"contexts":[{"filename":"swg21984463.txt","text":"Title: IBM Finding if Table created as NOT LOGGED INITIALLY - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q203","question":"Limitations of sylog-TCP log target using DataPower Gateways\n\nI 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.","is_impossible":false,"contexts":[{"filename":"swg21269136.txt","text":"Title: IBM DataPower off-device logging: a configuration example - United States\n\nText:\ndatapower; 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\u00ae WebSphere\u00ae DataPower\u00ae 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."}]},{"id":"TRAIN_Q204","question":"\"Internet Explorer has stopped working\"\n\n 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.","is_impossible":false,"contexts":[{"filename":"swg21500151.txt","text":"Title: IBM Remote scanning freezes or stops with IBM Datacap Taskmaster Capture - United States\n\nText:\nhang 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."}]},{"id":"TRAIN_Q205","question":"INFO: Upload replication check failed with error: getservbyname_r failed (Java::JavaLang::RuntimeException)\n\nWhy 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.","is_impossible":false,"contexts":[{"filename":"swg22004607.txt","text":"Title: 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\n\nText:\n 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#"}]},{"id":"TRAIN_Q206","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)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21962588.txt","text":"Title: 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\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 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."}]},{"id":"TRAIN_Q207","question":"How to configure the Data Power Agent to communicate on TLSv1.2 ?\n\nAPM 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.","is_impossible":false,"contexts":[{"filename":"swg24041563.txt","text":"Title: IBM ITCAM Agent for WebSphere DataPower Applications: 7.1.0-TIV-ITM_WDP-FP0003 - United States\n\nText:\nDataPower; 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] [ ]"}]},{"id":"TRAIN_Q208","question":"Can I run different levels of the Rational Developer for z Systems host and client?\n\nI'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.","is_impossible":false,"contexts":[{"filename":"swg21568844.txt","text":"Title: IBM Developer for z Systems and Rational Developer for z Systems Backward\/Forward compatibility - United States\n\nText:\nRDz; 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\u2022 Connecting to a z\/OS System \n\u2022 Allocating z\/OS Data sets \n\u2022 Creating a z\/OS Project \n\u2022 Working with z\/OS COBOL & Pl\/I remote assets \u2013 edit, syntax check, submit, execute, debug and view the output \n\u2022 Basic CARMA functionality \n\u2022 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 *"}]},{"id":"TRAIN_Q209","question":"Out of memory error when executing simulation\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21438208.txt","text":"Title: IBM Reducing the size of Decision Warehouse trace when running scenario suites - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q210","question":"How to wrap table column text in list tab for a specific table?\n\nI 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","is_impossible":false,"contexts":[{"filename":"swg22007765.txt","text":"Title: IBM Wrap table column text in list tab - United States\n\nText:\nTPAEICD; 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]"}]},{"id":"TRAIN_Q211","question":"How can I resolve issues with CLI copy command using SCP\/SFTP on DataPower?\n\nI'm running into some issues while running DataPower CLI COPY command using SCP\/SFTP. It throws an error saying \n\"% Copy: File not found \"\neven though the files are in place. What steps should I take in order to resolve this issue? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q212","question":"Security Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2178)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21999724.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q213","question":"Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735)\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q214","question":"Help with Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21959709.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in IBM Dojo Toolkit affect IBM Image Construction and Composition Tool (CVE-2014-8917) - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q215","question":"Is ITNM exposed to vulnerability CVE-2017-1194?.\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg22002975.txt","text":"Title: 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\n\nText:\n 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."}]},{"id":"TRAIN_Q216","question":"Help with Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22009842.txt","text":"Title: IBM Security Bulletin: IBM MQ Appliance is affected by a Network Security Services (NSS) vulnerability (CVE-2017-7805) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in Network Security Services (NSS). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-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."}]},{"id":"TRAIN_Q217","question":"Download link for application support for OMEGAMON for Messaging on z\/OS V7.5\n\nWhere 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\/].","is_impossible":false,"contexts":[{"filename":"swg21255545.txt","text":"Title: IBM Locating ITM Workspace Application Support Files for z\/OS Agents - United States\n\nText:\nAppSupport 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\u00ae Performance Expert on z\/OS, version 5.4.0 \n * IBM Tivoli OMEGAMON XE for DB2\u00ae 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\u00ae 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\u00ae 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\u00ae 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\u00ae 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 \u2122 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\u00ae 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\u00ae 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"}]},{"id":"TRAIN_Q218","question":"DFHXS1201 password invalid after TSS7110E password expired with RSU1412 applied to CICS TS 5.1 or 5.2\n\nWhy can't I successfully change my expired password using CICS transaction CESN? I receive CA Top Secret message \"TSS7110E Password Has Expired. New Password Missing\" followed by CICS message DFHXS1201 applid The password supplied in the verification request for userid userid was invalid.' I'm typing in valid passwords but I still can't get logged onto CICS.\n\nI started having problems after applying RSU1412 to CICS Transaction Server for z\/OS (CICS TS) V5.1or V5.2. Fixing PTFs for CICS TS V5.1 (or V5.2) APARs PI21866 and PI33454 have been installed. CA Top Secret fixes RO78438. and RO78976 along with TR79619 and TR79620 have also been installed for recent problems.\n\nIn the CICS auxtrace, I can see the system authorization facility (SAF) response returned:\n\n XS FE04 XSSB *EXC* FUNCTION(INQUIRE_PASSWORD_DATA) RESPONSE(EXCEPTION) \n REASON(INVALID_PASSWORD) SAF_RESPONSE(8) SAF_REASON(0) \n ESM_RESPONSE(8) ESM_REASON(0) METHOD_USED(FULL)\n TASK-00199 KE_NUM-0039 TCB-RO \/009FA9E8 RET-943EBDA8 \nThis is the complete CICS message is:\nDFHXS1201 applid The password supplied in the verification request for userid userid was invalid. This occurred in transaction CESN when userid userid was signed on at netname netname.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q219","question":"The configuration task database-transfer failed with DB2 SQL Error: SQLCODE=-1585, SQLSTATE=54048\n\nWhile 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.","is_impossible":false,"contexts":[{"filename":"swg21529563.txt","text":"Title: IBM DB2 SQL error from Sterling B2B Integrator: SQLCODE: -1585, SQLSTATE: 54048 - United States\n\nText:\nSTERLINGPRI 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"}]},{"id":"TRAIN_Q220","question":"\"Cannot retrieve execution traces on your server\" message in DVS test suite execution results page\n\nThe test suite is successful and returns the test results specified in the Excel scenario file, but the message \"Cannot retrieve execution traces on server \" shows in the results page, and the additional trace information requested in the run page is not available.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q221","question":"Case Analyzer is not working\n\n\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'","is_impossible":false,"contexts":[{"filename":"swg22004617.txt","text":"Title: IBM What are the analyzer.db.updateMode parameter values for Case Foundation Case Analyzer? - United States\n\nText:\nperformance 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."}]},{"id":"TRAIN_Q222","question":"Composite Platform Installation Tool (CPIT) does not support IBM Tivoli Directory Server (ITDS) 6.3 on Red Hat Enterprise Linux\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21599258.txt","text":"Title: IBM Installing IBM Tivoli Directory Server Version 6.3 on RHEL 6 operating system - United States\n\nText:\nTivoli 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"}]},{"id":"TRAIN_Q223","question":"SQL20157N happened in off-line backup against the quiesced database after migrating to V10.1 or V10.5 from V9.7.\n\nThe 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.","is_impossible":false,"contexts":[{"filename":"swg21979667.txt","text":"Title: IBM The off-line backup command could fail even when the database is quiesced on DB2 V10.1 and later. - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q224","question":"Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000)\n\nI 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","is_impossible":false,"contexts":[{"filename":"swg21959745.txt","text":"Title: IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Internet Passthru (CVE-2015-4000) - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q225","question":"Why the Portal 7.0.0.2 - CF29 upgrade is failing ?\n\nWhy 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.","is_impossible":false,"contexts":[{"filename":"swg21569953.txt","text":"Title: IBM Portal 7.0.0.1 migration may fail with error EJPPH0044E EJPPH0001E ADMC0009E while running upgrade-profile task. - United States\n\nText:\nupgrade-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]<\/message> \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.<\/message> \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.<\/message> \ncom.ibm.wps.pe.mgr.exceptions.AppServerAdminListenerExce \nption: EJPPH0001E: Adding Notification Listener for MBean AppManagement \nfailed. (Application Name: PA_Policy_Status).<\/message> \n\ncom.ibm.websphere.management.exception.ConnectorException: \nADMC0009E: The system failed to make the SOAP RPC call: \nqueryNames<\/message> \n<\/status> \n<\/request> \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."}]},{"id":"TRAIN_Q226","question":"Can I disable RC4 cyphers in TIP?\n\nHow can one disable the RC4 cypers in Tivoli Integrated Portal?","answer":"To 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"}]},{"id":"TRAIN_Q228","question":"DB2 Non Reclaimable Storage .\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21438047.txt","text":"Title: 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\n\nText:\nSQL1763N; 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]"}]},{"id":"TRAIN_Q229","question":"automatically rotate log files for IHS and Plug-in\n\nHow to configure IBM HTTP Server (IHS), and IBM web server Plug-in, to automatically rotate the log files?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q230","question":"Does IBM MQ Server installation include a Java Runtime Engine (JRE) and what is it used for?\n\nDoes 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.","is_impossible":false,"contexts":[{"filename":"swg27038676.txt","text":"Title: IBM Levels of JRE and GSkit bundled with IBM MQ - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q231","question":"Netcool\/Impact (all versions): OMNIbusEventReader Filter Analyzer error \"rule includes an unsupported expression\"\n\nNetcool\/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.","is_impossible":false,"contexts":[{"filename":"swg21675858.txt","text":"Title: IBM Filter Analyzer and Filters comparing ObjectServer fields - United States\n\nText:\nnetcool; 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]"}]},{"id":"TRAIN_Q232","question":"Help with Security Bulletin: MQSISTOP\/STARTMSGFLOW commands with unauthorized user succeed affects WMB and IIB (CVE-2015-5011)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg21967265.txt","text":"Title: IBM Security Bulletin: MQSISTOP\/STARTMSGFLOW commands with unauthorized user succeed affects IBM WebSphere Message Broker and IBM Integration Bus (CVE-2015-5011) - United States\n\nText:\nWMB 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"}]},{"id":"TRAIN_Q233","question":"Help with Security Bulletin: API Connect is affected by a cross-site scripting vulnerability CVE-2018-1382\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22013054.txt","text":"Title: IBM Security Bulletin: API Connect is affected by a cross-site scripting vulnerability \nCVE-2018-1382 - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q234","question":"How do I create a windows service for WebSphere Application Server version 7.0.X?\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21397335.txt","text":"Title: IBM Using WASServiceCmd to create Windows services for WebSphere Application Servers - United States\n\nText:\nwasservice; 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."}]},{"id":"TRAIN_Q235","question":"Cannot start Maximo\/SCCD with error BMXAA4087E - The MAXMESSAGE value for group login and key username could not be retrieved.\n\nCannot 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.","is_impossible":false,"contexts":[{"filename":"swg21959714.txt","text":"Title: IBM Maximo fails to start with error BMXAA4087E - United States\n\nText:\nTPAESCCD; 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."}]},{"id":"TRAIN_Q236","question":"Cannot Authorize SPSS 19 Installation on New Computer,Need to Authorize SPSS 19 on a New Computer\n\nI'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.","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q237","question":"What is the best practice for working with BPM support\n\nWhen 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.","is_impossible":false,"contexts":[{"filename":"swg21569731.txt","text":"Title: IBM Collect troubleshooting data for the IBM Business Process Manager products - United States\n\nText:\ninstall; 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_\u200b\u200broot\u200b\u200b\/profiles\/\u200b\u200bprofile\u200b\u200b_\u200b\u200bname\u200b\u200b\/\u200b\u200blogs\u200b\u200b\/server\u200b\u200b_\u200b\u200bname 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\u200b\u200b_\u200b\u200broot\/\u200b\u200bprofiles\/profile\u200b\u200b_\u200b\u200bname\u200b\u200b\/\u200b\u200blogs\u200b\u200b\/server\u200b\u200b_\u200b\u200bname \n * install_\u200b\u200broot\/\u200b\u200bprofiles\/profile\u200b\u200b_\u200b\u200bname\/\u200blogs\u200b\u200b\/ffdc\n\n\nProvide the configuration files: * TeamWorksConfiguration.running.xml file, which is located in the following locations: * Process Center profile:\n install_\u200b\u200broot\/\u200b\u200bprofiles\/profile\u200b\u200b_\u200b\u200bname\/config\/cells\/cell_name\/nodes\/\n node_name\/servers\/server_name\/process-center \n * Process Server profile:\n install_\u200b\u200broot\u200b\u200b\/\u200b\u200bprofiles\/profile\u200b\u200b_\u200b\u200bname\/config\/cells\/cell_name\/nodes\/\n node_name\/servers\/server_name\/process-server\n \n \n * The complete install_\u200b\u200broot\/\u200b\u200bprofiles\/profile\u200b\u200b_\u200b\u200bname\/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:\u200b * Any upcoming deadlines and dates\u200b \n * Any realized or potential effect on customers\u200b\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"}]},{"id":"TRAIN_Q238","question":"Help with Security Bulletin: IIB is affected by Web UI security vulnerability (CVE-2017-1694)\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by Web UI security vulnerability (CVE-2017-1694). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q239","question":"Help with Security Bulletin: IIB is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22008829.txt","text":"Title: IBM Security Bulletin:IBM Integration Bus is affected by deserialization RCE vulnerability in IBM WebSphere JMS Client - United States\n\nText:\nIIB 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"}]},{"id":"TRAIN_Q240","question":"End of support date for CICS TS 3.2 change from 2016 to 2015\n\nDid 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","is_impossible":false,"contexts":[{"filename":"swg21635057.txt","text":"Title: IBM CICS Transaction Server for z\/OS 3.1 and 3.2 End of Support announcement - United States\n\nText:\nCICS 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"}]},{"id":"TRAIN_Q241","question":"java.lang.IllegalStateException when I'm trying to stop a service in BPM Process Admin Console\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21282614.txt","text":"Title: IBM TroubleShooting: JavaServer Pages (JSP) problems - United States\n\nText:\nJSPs; TroubleShootingDocument; troublehooting TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Troubleshooting JSP problems for WebSphere\u00ae 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<\/TITLE>\n <\/HEAD>\n <BODY>\n <H1>\n Your data is <%= request.getParameter(\"name\") %>\n <\/H1>\n <\/BODY>\n <\/HTML> \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"}]},{"id":"TRAIN_Q242","question":"Getting Delay or AMQ9716: Remote SSL certificate revocation status check failed when trying to start a MQ SSL channel, why?\n\nGetting 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.","is_impossible":false,"contexts":[{"filename":"swg21399255.txt","text":"Title: IBM After upgrading to 7.0.1.0 you get SSL error AMQ9716 - United States\n\nText:\nAMQ9716 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"}]},{"id":"TRAIN_Q243","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\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21512416.txt","text":"Title: IBM OMEGAMON XE MQ Monitoring Agent Issue the ALTER QLOCAL Command - United States\n\nText:\nALTER 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."}]},{"id":"TRAIN_Q244","question":"Help with Security Bulletin: Multiple vulnerabilities identified in IBM Java SDK affect WSRR Studio (CVE-2015-4872)\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities identified in IBM\u00ae 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)","is_impossible":false,"contexts":[{"filename":"swg21971058.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository Studio (CVE-2015-4872, CVE-2015-4911, CVE-2015-4893, CVE-2015-4803) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 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."}]},{"id":"TRAIN_Q245","question":"WebSphere Adapter for JDBC receives DB2 SQL Error: SQLCODE=-104\n\nWebSphere Adapter for JDBC throws an exception when executing a retrieveAll operation against a z\/OS mainframe DB2 database.\nThe following error message is seen when WebSphere Adapter for JDBC executes a retrieveAll operation against a z\/OS mainframe DB2 database: Body: javax.resource.ResourceException: DB2 SQL Error: SQLCODE=-104, \nSQLSTATE=42601, SQLERRMC=SNAPSHOT;MODE, DRIVER=3.57.82DSRA0010E: SQL \nState = 42601, Error Code = -104 \nHow should I resolve this issue? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q246","question":"Help with Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2015-2808)\n\nI need to understand details regarding Security Bulletin: Security vulnerabilities have been identified in IBM DB2 shipped with WebSphere Remote Server (CVE-2015-2808). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q247","question":"Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time?\n\nYou 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.","is_impossible":false,"contexts":[{"filename":"swg1PI47826.txt","text":"Title: IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q248","question":"MessageSet Project cannot be referenced in multiple Applications\n\n\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....","is_impossible":false,"contexts":[{"filename":"swg27023600.txt","text":"Title: IBM WebSphere Message Broker Version 8.0 Readme - United States\n\nText:\nreadme 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=<path to licenses> 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: <disk1 image>\\installToolkit.bat -nonAdmin On Linux run the following script: <disk1 image>\/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: <WMBT80_Home>\\wmbt\\postconfig\\postInstall_admin.bat On Linux run script: <WMBT80_Home>\/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 '<QueueManager>' 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=<location of unzipped download> ( 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:<type> 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 '<node label>' ComIbmMSLMappingNode: <flow name>\n BIP3946E: The map script generation for QName '<map routine name>' has failed, with the following details: java.lang.RuntimeException: IXJXE0609E: [ERR 0548][ERR XPST0017] The function '<function name>' with parity '<n>' 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 <MQ_DATA_PATH>\/exits and\/or <MQ_DATA_PATH>\/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\u2122 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"}]},{"id":"TRAIN_Q249","question":"Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Telemetry (CVE-2015-4000)\n\nI need to understand details regarding Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM WebSphere MQ Telemetry (CVE-2015-4000). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q250","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?\n\nWhy 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","is_impossible":false,"contexts":[{"filename":"swg21664126.txt","text":"Title: IBM Cannot update a Notice Questionnaire Template or publish a Hold Notice - United States\n\nText:\nOracle 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"}]},{"id":"TRAIN_Q251","question":"Security Bulletin: Weak Cipher available in IBM API Connect (CVE-2015-2808)\n\nI need to understand details regarding Security Bulletin: Weak Cipher available in IBM API Connect (CVE-2015-2808). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q252","question":"Latest deployed ruleset not executing in clustered environment\n\n\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","is_impossible":false,"contexts":[{"filename":"swg21598779.txt","text":"Title: IBM An unexpected ruleset version is executed - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is Rule Execution Server (RES) not executing the expected version of a ruleset ?\nWhat are the possible causes after a hot deployment for Rule Execution Server not to use the updated ruleset ? \n\nCAUSE\nPossible causes for unexpected versions to be executed are: \n- the RES client requesting execution may be passing a wrong ruleset path\n- a hot deploy notification was not sent by the RES console, or not received by all the Execution Units (XU)\n- the ruleset parsing policy may be delaying the use of a ruleset version until its parsing is complete\n- the updated ruleset cannot be parsed successfully and RES falls back on an earlier active version that parses\n\n\nANSWER\nFirst validate that the RES components (the Execution Unit, the Management Console and the Client Application bundling the RES client library, which may be HTDS, MTDS, the SSP or a custom application) have been installed properly as per the documentation, see Configuring Rule Execution Server [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.config\/config_ds_res\/tpc_res_config.html]. \n\nThe ruleset version that is executed depends first on the ruleset path that is requested. Specifying a ruleset path with no version ( such as \/MyRuleApp\/MyRuleset\/ ) is interpreted as a request to execute the highest version of the ruleset, as opposed to a version specific ruleset path ( such as \/MyRuleApp\/2.0\/MyRuleset\/1.0 ). Validate that the executed ruleset path is indeed unexpected considering the requested ruleset path. \n\n \n\nA common situation for an unexpected ruleset version to be executed is that of a hot deployment that is not successfully completed. The more frequent causes for the hot deployment not to happen as expected are: \n\n * Permission issue: the user publishing the ruleset update must have sufficient administrative rights ( Monitor role in WebSphere Application Server ) in order for the deployment to notify all the Execution Units of the ruleset update through JMX. For example on WebSphere Application Server see Mapping the resAdministrators group to the Monitor role [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.config\/config_ds_res_was8\/tsk_was_map_admin_group.html] \n * Version mismatch between the Execution Unit(s) and the Management Console: in order for the Management Console to detect the presence of execution units the versions of these components must match down to the fix level. For example 7.1.1.4 Management Console would not interact properly with a 7.1.1.3 Execution Unit. The version of the RES console is displayed in the \"About\" link (top right corner). The version of the Execution Unit can be seen in the resource adapter ra.xml file where a resourceadapter-version tag shows the version. For example with the WebSphere Application Server this can seen through: Resources > Resource adapters > XU > Deployment Descriptor \n * Asynchronous ruleset parsing is used : in this mode, while an updated ruleset is being parsed, an earlier version of the ruleset can be used for executions that are requested at that time. Note that there is no guarantee of which specific earlier version of the ruleset may be used since it is a factor of which versions are available in the deprecated ruleset cache and whether garbage collection has occurred. In order to remove any uncertainty on the version that can be executed, it is possible to either turn off the asynchronous mode [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_asynchron_turnoff.html], or force synchronous parsing in asynchronous mode [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_forcing_sync_pars.html]. \n * Notification scope is limited to one cell : by design the RES notification mechanism only works within one WebSphere Application Server Cell ( or one JBoss domain, or one Weblogic domain ), so a Management Console may only notify Execution Units that are running on servers in the same cell as the RES Console. See XU notification in a cluster over multiple cells [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21458245]. If you need to implement notifications to several cells at once, the document Ruleset updates and programmatic notification of RES eXecution Unit [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21418646] can be useful. \n * Parsing failure of an updated ruleset : leading the XU to fall back on an earlier active version that parses successfully \n * Ruleset update was only written to persistence: writing directly to RES persistence with the ant tasks res-write-db or res-write-file [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_deploy_rlapp_ant.html] does not trigger a notification, so the update may only been seen after server restart. \n * XU MBean is not activated in Java SE mode : See Activating the XU MBean in Java SE [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r0\/topic\/com.ibm.wodm.dserver.rules.res.managing\/topics\/tsk_res_config_xu_mbean_jse.html] \n * Multiple Java SE Execution Units are deployed in the same JVM: See Rule Execution Server J2SE mode hot deployment does not seem to work [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21585251] \n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Modules:Execution Server (BRES \/ RES) Platform Independent 7.1.1, 7.1, 7.0.3, 7.0.2, 7.0.1, 7.0"}]},{"id":"TRAIN_Q253","question":"What TLS cipherspecs\/ciphersuites are supported when connecting from Oracle Java (non-IBM JRE) to MQ queue manager?\n\nWhat TLS cipherspecs\/ciphersuites are supported when connecting from Oracle Java (non-IBM JRE) to MQ queue manager?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q254","question":"Why is my delete virtual portal timing out after 120 seconds?\n\nWhen 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)","is_impossible":false,"contexts":[{"filename":"swg21611073.txt","text":"Title: IBM Deletion of virtual portal fails with transaction timeout - United States\n\nText:\nvirtual portal; timeout; delete; portlet; EJPAH4000E; EJPEB0804E; rollbackexception; admin; WTRN0006W TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAttempt to delete virtual portal via Virtual Portal Manager portlet fails with error:\n\nEJPAH4000E: Failed to delete virtual portal \n\nAttempts to delete the virtual portal using the ConfigEngine task \"delete-virtual-portal\" may fail as well.\n\n\nCAUSE\nWith the introduction of Managed Pages in WebSphere Portal 8.0, virtual portal deletions require more transaction time when removing from the system. This increased transaction time can lead to an error situation if either of the following timeouts is exceeded: \n\n * the total and\/or maximum transaction lifetime timeout value(s) for the server \n * the WCM component's transaction timeout\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may show the following: \n\nExample #1:\n\n[9\/10\/12 10:08:43:757 AMT] 0000001a TimeoutManage I WTRN0006W: Transaction 00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000139B080F02D0000000236122A9CB64A65E5C73B006CE4605EA6BEA57CC3F6A1783B00000001 has timed out after 120 seconds.\n\n[datestamp] 00000055 JTATransactio E RT0025E: Failed to save user transaction\ncom.ibm.icm.ci.CDMTransactionException\nat com.ibm.icm.ci.JCRUserTransaction.commit(JCRUserTransaction.java:189)\nat com.ibm.icm.ci.JTATransaction.commit(JTATransaction.java:166)\nat com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:804)\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n....\n\n[datestamp] 00000055 DeleteVPComma E com.ibm.wps.command.vp.DeleteVPCommand AbstractCommand.throwCommandException EJPEB0804E: DeleteVPCommand: An exception in the data backend occurred.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJPFB0002E: Exception occurred.\nat com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:348)\n....\nCaused by: javax.transaction.RollbackException\nat com.ibm.tx.jta.impl.TransactionImpl.stage3CommitProcessing(TransactionImpl.java:1254)\n.... \n\nExample #2: \n\n[datestamp] 000000f4 TimeoutManage I WTRN0006W: Transaction PA_MageVirtualPortals#MgeVirtualPortals.war#ManageVirtualPortals 00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000143FA0D566200000001680EB7144589A0582D368B51A9A958DDACFF4F62EA89D95C00000001 has timed out after 120 seconds.\n[datestamp] 000000f4 TimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 8,5,main]. The stack trace of this thread when the timeout occurred was: \njava.net.SocketInputStream.socketRead0(Native Method)\njava.net.SocketInputStream.read(SocketInputStream.java:150)\njava.net.SocketInputStream.read(SocketInputStream.java:121)\ncom.ibm.db2.jcc.t4.x.b(x.java:208)\ncom.ibm.db2.jcc.t4.x.c(x.java:360)\ncom.ibm.db2.jcc.t4.x.c(x.java:473)\ncom.ibm.db2.jcc.t4.x.v(x.java:1241)\ncom.ibm.db2.jcc.t4.ab.a(ab.java:61)\ncom.ibm.db2.jcc.t4.p.a(p.java:50)\ncom.ibm.db2.jcc.t4.rb.b(rb.java:220)\ncom.ibm.db2.jcc.am.po.qc(po.java:3498)\ncom.ibm.db2.jcc.am.po.b(po.java:4461)\ncom.ibm.db2.jcc.am.po.ic(po.java:799)\ncom.ibm.db2.jcc.am.po.executeUpdate(po.java:777)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecuteUpdate(WSJdbcPreparedStatement.java:1187)\ncom.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.executeUpdate(WSJdbcPreparedStatement.java:804)\ncom.ibm.icm.da.portable.common.sql.PPreparedStatement.executeUpdate(PPreparedStatement.java:83) com.ibm.icm.da.portable.data.DeleteWorkspace.deleteWideTableData(DeleteWorkspace.java:359)\ncom.ibm.icm.da.portable.data.DeleteWorkspace.deleteWorkspace(DeleteWorkspace.java:130) com.ibm.icm.da.portable.data.DataManager.deleteWorkspace(DataManager.java:700)\ncom.ibm.icm.ci.workspace.impl.PDeleteWorkspaceImpl.deleteWorkspace(PDeleteWorkspaceImpl.java:84) com.ibm.icm.ci.workspace.impl.WorkspaceService.deleteWorkspace(WorkspaceService.java:270) com.ibm.icm.jcr.RepositoryImpl.deleteWorkspace(RepositoryImpl.java:808)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:336)\ncom.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler$2.run(JcrWorkspaceVirtualPortalHandler.java:324) com.ibm.wps.ac.impl.UnrestrictedAccessImpl.run(UnrestrictedAccessImpl.java:84)\ncom.ibm.wps.command.ac.ExecuteUnrestrictedCommand.execute(ExecuteUnrestrictedCommand.java:90) com.ibm.wps.wcm.vpmapping.JcrWorkspaceVirtualPortalHandler.onVirtualPortalDeleted(JcrWorkspaceVirtualPortalHandler.java:345)\ncom.ibm.wps.command.vp.VirtualPortalHandlerImpl.onVirtualPortalDeleted(VirtualPortalHandlerImpl.java:396)\ncom.ibm.wps.command.vp.DeleteVPCommand.execute(DeleteVPCommand.java:178 com.ibm.wps.portlets.managevirtualportals.actions.DoDeleteVirtualPortalAction.deleteVirtualPortal(DoDeleteVirtualPortalAction.java:151)\n....\n\n\nRESOLVING THE PROBLEM\n1. Increase the total transaction lifetime timeout and maximum transaction timeout values (for example, to 600 seconds or greater) using the instructions in the Related information section below. \n\n2. If the problem persists after addressing the change in suggestion #1 and the error in SystemOut.log shows that the timeout still occurs after 120 seconds (as opposed to the increased value that you just set), then update to Cumulative Fix (CF) 9 or later to get the fix for APAR PI04872 and then add (or update if already exists) the following custom property to the WCM_WCMConfigService Resource Environment Provider: \n\nName: wcm.transaction.timeout \n\nValue: 600 (for example) \n\nNote: There is not a target value for a transaction timeouts that applies to every customer environment. The goal should be to find a value that allows the virtual portal deletion to succeed but does not introduce significant delay in being alerted for other transaction timeouts.\n\nRELATED INFORMATION\n#Transaction settings [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.doc\/info\/ae\/ae\/tjta_settlog.html]\nPI04872 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI04872]\nSetting Resource Environment Provider custom properties [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Setting_service_configuration_properties_wp8]"}]},{"id":"TRAIN_Q255","question":"Unable to unistall Data Studio 3.1.1 on Windows\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21991414.txt","text":"Title: IBM How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? - United States\n\nText:\n 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\/]"}]},{"id":"TRAIN_Q256","question":"Error running krzgrant.sql script provided with 6.3.1.2-TIV-ITM_KRZ-IF0003.tar\n\nWhen 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.","is_impossible":false,"contexts":[{"filename":"swg24035571.txt","text":"Title: IBM ITCAM Extended Agent for Oracle Database: 6.3.1-TIV-ITM_EXT-FP0002 - United States\n\nText:\nOracle 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<SQLInfo ID=\n...\n<\/SQLText>\n<BaseTable QueryName=\"SampleTable1\" GrantName=\"SampleTable1\"\/>\n<\/SQL>\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<SQLInfo ID=\n...\n<\/SQLText>\n<BaseTable QueryName=\"dual\" GrantName=\"dual\"\/>\n<\/SQL>\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=<directory>\/<file prefix>, 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:<database connection name>-<agent instance name>-<host name>: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 <CANDLEHOME> 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 <TEMP> 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<TEMP> 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<TEMP>\/<PARTNUMBER>:\n> $CANDLEHOME\/bin\/tacmd addBundles -i <TEMP>\/<PARTNUMBER>\/WINDOWS\/Deploy -t rz -f\n> $CANDLEHOME\/bin\/tacmd addBundles -i <TEMP>\/<PARTNUMBER>\/WIA64\/Deploy -t rz -f\n> $CANDLEHOME\/bin\/tacmd addBundles -i <TEMP>\/<PARTNUMBER>\/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<TEMP>\/<PARTNUMBER>:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\<PARTNUMBER>\\WINDOWS\\Deploy -t rz -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\<PARTNUMBER>\\WIA64\\Deploy -t rz -f\n> %CANDLE_HOME%\\bin\\tacmd addBundles -i <TEMP>\\<PARTNUMBER>\\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 <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME\/bin\/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> $CANDLEHOME\/bin\/tacmd updateAgent -t rz\n-n <Managed system name>\n-v 063102000\n\nOn a Windows system:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\/bin\/tacmd listSystems\n\nThe output shows the managed system name for the OS agent on the \nremote system to be updated. Use this value as the target of the\ntacmd updateAgent command. \n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t RZ\n-n <Managed system name>\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 <server>\n-u <itmuser> \n-p <password>\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 <server>\n-u <itmuser> \n-p <password>\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\/<host>_rz_<inst>_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_<instance>.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"}]},{"id":"TRAIN_Q257","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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\nThis is related to CVEID:\nCVE-2017-15277\nCVE-2017-15281\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q258","question":"Hide a page in dotedit step\n\n 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.","is_impossible":false,"contexts":[{"filename":"swg21509510.txt","text":"Title: IBM How to delete a document hierarchy node in IBM Datacap Taskmaster Capture - United States\n\nText:\ndco 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 *"}]},{"id":"TRAIN_Q259","question":"Why does our Websphere application server hang when we apply Microsoft patch on our database server?\n\nWe 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.","is_impossible":false,"contexts":[{"filename":"swg21220832.txt","text":"Title: IBM Purging the connection pool of a WebSphere Application Server data source using the data source MBean - United States\n\nText:\nwas 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"}]},{"id":"TRAIN_Q260","question":"Framework Manager data source error\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21624136.txt","text":"Title: IBM BMT-IMP-0002 Failed to execute metadata request insufficient\ncapabilities\" - United States\n\nText:\nDQM; 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]"}]},{"id":"TRAIN_Q261","question":"Cannot Start JazzSM Dash after ObjectServer as a User Repository\n\n\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...","is_impossible":false,"contexts":[{"filename":"swg21405302.txt","text":"Title: IBM Disabling WebSphere administrative security when admin console is not accessible - United States\n\nText:\n 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. <WAS_INSTALL_DIR>\/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"}]},{"id":"TRAIN_Q262","question":"Scroll bar in search results resets to the top position in Internet Explorer\n\nIn 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.","is_impossible":false,"contexts":[{"filename":"swg21981877.txt","text":"Title: IBM Scroll bar in search results resets to the top position in Internet Explorer V9, V10, and V11 - United States\n\nText:\nICN; 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]"}]},{"id":"TRAIN_Q263","question":"Where can I get ITM 6.3.0 Fixpack 6 ? Is it available now ?\n\nWhere 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]","is_impossible":false,"contexts":[{"filename":"swg24040390.txt","text":"Title: IBM Tivoli Monitoring 6.3.0 Fix Pack 6 (6.3.0-TIV-ITM-FP0006) - United States\n\nText:\n 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\u00ae 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\u00ae, 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\u00ae 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"}]},{"id":"TRAIN_Q264","question":"Why are data source connections to Microsoft SQL Server failing after upgrading WebSphere Application Server?\n\n\n\nWebSphere Application Server v7 and Java SDK were updated to Fix Pack v7.0.0.37. Afterward, all data source connections to Microsoft SQL Server failed. \n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q265","question":"Help with Security Bulletin: Multiple vulnerabilities in OpenSSL affect WMB and IIB\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in OpenSSL affect WebSphere Message Broker and IBM Integration Bus. Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q266","question":"Is DataPower affected by the bash environment variable vulnerability CVE-2014-6271 or CVE-2014-7169\n\nIs 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.","is_impossible":false,"contexts":[{"filename":"swg21685435.txt","text":"Title: 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\n\nText:\nCVE-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 \u201cBash Bug\u201d or \u201cShellshock\u201d 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."}]},{"id":"TRAIN_Q267","question":"SAP Agent suddenly crashed\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg24039150.txt","text":"Title: IBM ITCAM Agent for SAP Applications, 7.1.1.1-TIV-ITM_SAP-IF0001 - United States\n\nText:\n 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 \u2018+++\u2019 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 \u2018Conversion Error \u2013unable to \nhandle\u2018---\u2018 as a number \u2019 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\u2022 Go to transaction code SE16.\n\u2022 Enter the table name as '\/IBMMON\/ITM_CNFG' and press 'F7'.\n\u2022 Execute the database table '\/IBMMON\/ITM_CNFG' or press 'F8'.\n\u2022 Add the additional overlap time parameter as \u2018MAI_PERD_OV\u2019\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 \u2018SAP\u2019\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 '<SID>_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 \u2018Close Alert\u2019 and \u2018Close Alerts of the\nsame type\u2019 are missing in \u2018Alert Information\u2019 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 \u2018ITM_USER_INFORMATION\u2019 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 \u201cClient\u201d 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 <CANDLEHOME> 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 <TEMP> 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<TEMP>\/7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:\n\n> <TEMP>\/7.1.1.1-TIV-ITM_SAP-IF0001\/itmpatch -h <CANDLEHOME> \n-i <TEMP>\/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<TEMP>\\7.1.1.1-TIV-ITM_SAP-IF0001, the install command is:\n\nFor Windows 32-bit\n> <TEMP>\\7.1.1.1-TIV-ITM_SAP-IF0001\\itmpatch -h <CANDLEHOME> \n-i <TEMP>\\7.1.1.1-TIV-ITM_SAP-IF0001\\ksa_winnt_tema_if0001.cab\n\nFor Windows 64-bit \n> <TEMP>\\7.1.1.1-TIV-ITM_SAP-IF0001\\itmpatch -h <CANDLEHOME> \n-i <TEMP>\\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 <TEMP> 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 <TEMP>\/7.1.1.1-TIV-ITM_SAP-IF0001:\n> $CANDLEHOME\/bin\/tacmd addBundles -n -i \n<TEMP>\/7.1.1.1-TIV-ITM_SAP-IF0001 \n\nOn Windows systems, \nif the fix was expanded to <TEMP>\\7.1.1.1-TIV-ITM_SAP-IF0001:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i \n<TEMP>\\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 <TEMP>\/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 <TEMP>\/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 <TEMP>\/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<TEMP>\/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 <TEMP>\/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 <TEMP>\/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 <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME\/bin\/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> $CANDLEHOME\/bin\/tacmd updateAgent -t sa \n-n <Managed system name>\n-v 07110101\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t sa \n-n <Managed system name> \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 <CANDLEHOME>] [-j <JAVAHOME>] \n\nOn Windows systems:\n> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>] \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 <installation home> [OPTIONS]\n\nitmpatch -h <installation home>\n-t { <patch_file_directory> | <patch_file> }\n\nitmpatch -h <installation home>\n-i { <patch_file_directory> | <patch_file> }\n\nwhere:\n\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> <CANDLEHOME>\/bin\/itmpatch -h <CANDLEHOME> -t <TEMP>\n\n- To install the fix, use the \"-i\" option:\n> <CANDLEHOME>\/bin\/itmpatch -h <CANDLEHOME> -i <TEMP>\n\nwhere: \n<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring \ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n<TEMP> represents the fully qualified directory specification, \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 <server>\n-u <itmuser>\n-p <password>\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 <server>\n-u <itmuser>\n-p <password>\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"}]},{"id":"TRAIN_Q268","question":"Why can't I install the NOI Impact extensions that come with Impact fixpack 7.1.0.7?\n\n\n\nI downloaded this package: 7.1.0-TIV-NCI-LINUX-FP0007.zip.\nThere are repositories for Impact and the extensions. I updated Impact 7.1.0.4. successfully to 7.1.0.7 but the extensions did not get applied.\n\nI went back into Installation Manager and tried to perform an update using only the extensions repository and received the following message\n\n\"Update Packages\nNo updates or fixes were found for the packages that are installed in\nthe selected locations. ...\" alt text\n\nthis is what is installed:\nIBM\u00ae Installation Manager : 1.8.6 :\nimpact.gui_server_7.1.0.20160915_1412 IBM Tivoli Netcool\/Impact GUI Server : 7.1.0.7 :\nimpact.server_7.1.0.20160915_1412 : IBM Tivoli Netcool\/Impact Server : 7.1.0.7 :\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q269","question":"Controlling stop and starting of Rulerunner Service\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21964407.txt","text":"Title: IBM Datacap Rulerunner server stops after several aborted batches - United States\n\nText:\nRulerunner 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"}]},{"id":"TRAIN_Q270","question":"How to resolve \"An unexpected error occurred. Contact your system administrator. ICWPA1001E\"\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg27046675.txt","text":"Title: IBM Known limitation: You cannot add people to a matter request if there are more than 1000 people selected in the clipboard. - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q271","question":"Why am I seeing a java.lang.StackOverflowError in Portal?\n\nMy Portal process pid \/ java.exe is suddenly disappearing. Reviewing the SystemOut.log files around the time it disppears, I am seeing the following:\n\n[datetime] 000007c1 ServletWrappe E\ncom.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0014E: [....]\n\nnested exception is\njava.lang.StackOverflowError\nat\norg.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherS ervlet.java:837)\nHow do I prevent this?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q272","question":"Why are we seeing MQRC_NOT_AUTHORIZED errors after upgrading Websphere from V7.0 to V8.5.5?\n\nhttps:\/\/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.","is_impossible":false,"contexts":[{"filename":"swg21662193.txt","text":"Title: 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\n\nText:\n 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(\u201c\u201d, \u201c\u201d);\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 \u201ccom.ibm.mq.jms.ForceUserID\u201d 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"}]},{"id":"TRAIN_Q273","question":"Why are the icons greyed \/ grayed out for a library in the WCM Library Admin Portlet?\n\nUsually this is seen when an attempt to delete the library via the delete trash-can icon and the delete fails\/hangs. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q274","question":"Error when using profilePath parameter with BPMConfig to create a profile\n\nWhen 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 <profile_path> must not exist.....","answer":"Note: If you are creating the profile makes sure a profilePath value does not exist.","is_impossible":false,"contexts":[{"filename":"swg21649807.txt","text":"Title: IBM Specifying the profile path in the BPMConfig properties file for IBM Business Process Manager (BPM) - United States\n\nText:\nBPMConfig; 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"}]},{"id":"TRAIN_Q275","question":"Upgrade of IBM Integration Designer fails\n\nI tried upgrading IID from 7.5.1.0 to 7.5.1.2 using the online repository via an Internet connection. An error is thrown in Installation Manager and the upgrade fails:\nCRIMC1029E: failed to add module com.ibm.ram.rich.core_7.2.2.v20100224_0426 in warehouse C:\\Program Files (x86)\\IBM\\WebSphere\\AppServer-Shared Error renewable download \n...\nHow do I solve this issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q276","question":"Netcool\/Impact (all versions): JMSListener does not reconnect when JMS server is restarted\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21567091.txt","text":"Title: IBM JMSListener AutoReconnect properties misconception - United States\n\nText:\nnetcool; 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."}]},{"id":"TRAIN_Q277","question":"No data in some workspaces for MySQL agent\n\nWhy 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.","is_impossible":false,"contexts":[{"filename":"swg22008622.txt","text":"Title: IBM No data in some workspaces for MySQL agent - United States\n\nText:\n 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 \u2018ON\u2019 and for versions >=5.7.8 is \u2018OFF\u2019. \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 \u2018my.cnf\u2019 file (located at \u2018<MySQL_Installation_Dir>\/my.cnf\u2019 for Windows and \u2018\/etc\/my.cnf\u2019 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"}]},{"id":"TRAIN_Q278","question":"How to control SDMS database size?\n\nITCAM 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.","is_impossible":false,"contexts":[{"filename":"swg21959281.txt","text":"Title: IBM ITCAM for SOA KD4SDMS database size grows - United States\n\nText:\nCAMSOAALL 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."}]},{"id":"TRAIN_Q279","question":"Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed (CVE-2017-1341)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22005400.txt","text":"Title: IBM Security Bulletin: IBM MQ and IBM MQ Appliance MQOPEN call might succeed when it should have failed. (CVE-2017-1341 ) - United States\n\nText:\n 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."}]},{"id":"TRAIN_Q280","question":"How to set database specific custom properties in WebSphere Application Server?\n\nI 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","is_impossible":false,"contexts":[{"filename":"swg21197705.txt","text":"Title: IBM Using Oracle JDBC driver specific properties through a datasource - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q281","question":"Does ITCAM MSSQL agent support SQL Server 2017?\n\nDoes MSSQL monitoring agent support SQL Server 2017?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q282","question":"Security Bulletin: Non-configured connections could cause denial of service in IBM WebSphere MQ Internet Pass-Thru (CVE-2017-1118)\n\nI need to understand details regarding Security Bulletin: Non-configured connections could cause denial of service in IBM WebSphere MQ Internet Pass-Thru (CVE-2017-1118). Where can I find this information?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q283","question":"What is the latest Alcatel 5620 SAM probe?\n\nWe 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","is_impossible":false,"contexts":[{"filename":"swg22005197.txt","text":"Title: IBM Tivoli Netcool\/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States\n\nText:\nrelease 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]"}]},{"id":"TRAIN_Q284","question":"Improve performance of rule execution and Rule Execution Server (RES) for ODM and JRules\n\nHow do I improve rule execution and RES performance when working with ODM or WebSphere ILOG JRules?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q285","question":"How do I upgrade my virtual DataPower Appliance from 5.0 firmware to 6.0+ firmware?\n\nWhen 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.","is_impossible":false,"contexts":[{"filename":"swg21638268.txt","text":"Title: IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States\n\nText:\n 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"}]},{"id":"TRAIN_Q286","question":"Port number error starting 9.0 Launcher\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21986219.txt","text":"Title: IBM Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit - United States\n\nText:\nWTX 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."}]},{"id":"TRAIN_Q287","question":"Will Datacap support Windows 10, if so, which version is fully supported?\n\n\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\u00b7 Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers;","is_impossible":false,"contexts":[{"filename":"swg27047895.txt","text":"Title: IBM Datacap 9.0.1 FP1 - Readme doc - United States\n\nText:\n 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\u00ae 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\u00b7 1) Microsoft .NET Framework 4.6.1 \n\n\u00b7 Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n\u00b7 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n\u00b7 Run: vcredist_x86.exe \n\n \n\nInstall: \n\n\u00b7 3) IBM Datacap 9.0.1.1 \n\n\u00b7 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\u00b7 1) Microsoft .NET Framework 4.6.1 \n\n\u00b7 Run: NDP461-KB3102436-x86-x64-AllOS-ENU.exe \n\n \n\n\u00b7 2) Microsoft Visual C++ Redistributable Packages for Visual Studio 2013 \n\n\u00b7 Run: vcredist_x86.exe \n\n \n\nInstall: \n\n\u00b7 3) IBM Datacap 9.0.1.1 \n\n\u00b7 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 \u2018Datacap\u2019, then select \"Datacap \" \n\nCheck the box \u2018Show feature packs\u2019 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\u00b7 Microsoft Windows 10 (except for TMWeb Scanning with Twain drivers; \n\nSee \u201cKnown Limitations\u201d below for details) \n\n \n\n\u00b7 Oracle 12c (12.1.0.2.0) \n\n \n\n\u00b7 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 \"\u4fdd\u967a\u7533\u544aUpdated.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 \u201cAccusoft Twain Pro7 common 9.0.013\u201d with the message \"picdll Load Library failed.\u201d\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]"}]},{"id":"TRAIN_Q288","question":"DCS Document Conversion issue: java.util.MissingResourceException: Can't find resource for bundle com.stellent.scd.ExportResources, key 127\n\nDCS 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.","is_impossible":false,"contexts":[{"filename":"swg21613001.txt","text":"Title: IBM Configuring file content extraction tools for IBM Connections Search - United States\n\nText:\nstellent 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=<path_to_input_file>\noutputpath=<path_to_extracted_text_output>\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 *"}]},{"id":"TRAIN_Q289","question":"Why does the other instance of my multi-instance qmgr seem to hang after a failover?\n\nWhy does the other instance of my multi-instance qmgr seem to hang after a failover?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q290","question":"Hey, how can I transfer my spss 24 licence from my old macbook to the new one?\n\n\n\nI made the backup from my laptop to my new one, but SPSS doesnt allow me to start, because of the licence! Also I tried the SPSS Licence wizard on the new macbook, but it is not possible to fill in my licence\n\nI didn't find a option to deactivate the licence on the previous macbook.. how can I solve this problem?\n\nI would be grateful for some help!\n\nCheers","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q291","question":"Help with 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. 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","is_impossible":false,"contexts":[{"filename":"swg22009436.txt","text":"Title: IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States\n\nText:\nIIB 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"}]},{"id":"TRAIN_Q292","question":"Cannot access Decision Center or Rule Execution Server console (ODM)\n\nAfter installing Decision Center and Decision Server, I try to access the Decision Center and Rule Execution Server (RES) consoles, and get a 'Page not found' error ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q293","question":"Is WebSphere Portal affected by the June 2015 leap second?\n\nIs WebSphere Portal affected by the leap second that will be inserted at the end of June 2015?\nReference: http:\/\/en.wikipedia.org\/wiki\/Leap_second","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q294","question":"IZE0106E Connect failed with \"Unsupported CICS release\" after upgrading CICS TS V5.x\n\nDo 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.","is_impossible":false,"contexts":[{"filename":"swg27048530.txt","text":"Title: IBM Software maintenance strategy for CICS TS and its embedded components - United States\n\nText:\nLibery 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\u2122 \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\u2122 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"}]},{"id":"TRAIN_Q295","question":"Why are ITNM or Omnnibus WebGUI java applets fail to load with \"Missing Permissions manifest attribute in main jar\"\n\nWhy 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 <TIP HOME>\/profiles\/TIPProfile\/bin\/ha directory. The usage for that command is:\nHATool.{bat|sh} modules <db2 username> <db2 password>\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.","is_impossible":false,"contexts":[{"filename":"swg21499307.txt","text":"Title: IBM How to determine if a TIP server is part of a HA cluster - United States\n\nText:\nTIPL2; 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 <TIP HOME>\/profiles\/TIPProfile\/bin\/ha directory. The usage for that command is:\nHATool.{bat|sh} modules <db2 username> <db2 password>\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]"}]},{"id":"TRAIN_Q296","question":"Is it possible to controle which ciphers are available in Tivoli Integrated Portal?\n\nIs it possible to controle which ciphers are available in Tivoli Integrated Portal? ","answer":"To 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 \"<<Remove\" button.\n \n \n 3. Click the \"Apply\" button, and then the \"Save (to the master configuration)\" link.\n \n \n 4. Restart TIP.","is_impossible":false,"contexts":[{"filename":"swg21690163.txt","text":"Title: IBM Steps to disable RC4 SSL ciphers in Tivoli Integrated Portal - United States\n\nText:\nTIPL2SSL; 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 \"<<Remove\" button.\n \n \n 3. Click the \"Apply\" button, and then the \"Save (to the master configuration)\" link.\n \n \n 4. Restart TIP."}]},{"id":"TRAIN_Q297","question":"What action is required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235)?\n\nIBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server requires customer action for the GNU C library (glibc) vulnerability that has been referred to as \"GHOST\". What action is required? ","answer":"IBM strongly recommends that you should contact Red Hat to obtain fixes and install fixes for Red Hat Enterprise Linux (RHEL).","is_impossible":false,"contexts":[{"filename":"swg21695676.txt","text":"Title: IBM Action required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the GNU C library (glibc) vulnerability (CVE-2015-0235) - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server requires customer action for the GNU C library (glibc) vulnerability that has been referred to as \"GHOST\". \n\nCONTENT\nIBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server ships with Red Hat Enterprise Linux (RHEL) that is vulnerable to the GNU C library (glibc) vulnerability (CVE-2015-0235).\n\nRemediation:\nIBM strongly recommends that you should contact Red Hat to obtain fixes and install fixes for Red Hat Enterprise Linux (RHEL).\n\nChange History:\nJanuary 29, 2015: Original version published\n\nRELATED INFORMATION\n Red Hat Customer Portal - GHOST vulnerability [https:\/\/access.redhat.com\/articles\/1332213]\nA Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21696879]"}]},{"id":"TRAIN_Q298","question":"Can I see the exact number of PVU used in our VM environment\n\nHi,\n\nHappy new year!\n\nCan I see the exact number of PVU used in our VM environment, if yes, how to check? I want to be sure that we are using correct number of PVU we have license for.\n\nWe have installed Datastage on a windows 2016 standard server with 2 processor and 2 cores per processor assigned to this virtual server. The blade server that is used by this datastage server has 2 processors, 6 cores each.\n\nAfter configuring ILMT for the first time, the metric reports showed 120 PVU per core, so a total of 480 full capacity. Then we defined VM manager, and now reports show a PVU total of 840 full capacity and 480 sub capacity.","answer":"pvu_full_capacity.csv - PVU full capacity license metric results \n * pvu_sub_capacity.csv - PVU subcapacity license metric results","is_impossible":false,"contexts":[{"filename":"swg21688543.txt","text":"Title: IBM Correct understanding of CSV version of PVU reports - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What files are in the audit snapshot generated by IBM License Metric Tool or IBM BigFix Inventory version 9.x, and what is the correct interpretation of the values in the CSV report files? \n\nCAUSE\nThe licensing reports in CSV format can be misinterpreted by some customers.\n\nANSWER\nAudit snapshot is a record of PVU and RVU MAPC utilization in your enterprise over a period of time. It contains the following files: \n\n * audit_trail.csv \u2013 all user actions that influence the final results of the licensing reports, for example, software classification actions, uploads and imports of the PVU table, software catalog, and charge units as well as changes to the VM managers. \n * data_conditions.txt \u2013 conditions that were used during the generation of the audit snapshot, including the reporting period and filters applied on the reports as well as general information about the time when the snapshot was generated, version of the PVU table and software catalog, status of the import, aggregation, and recalculation. \n * part_numbers.csv - part numbers that are listed in the software catalog for all software products that are included in any of the CSV report files. \n * pvu_full_capacity.csv - PVU full capacity license metric results \n * pvu_sub_capacity.csv - PVU subcapacity license metric results \n * rvu_full_capacity.csv - RVU full capacity license metric results \n * rvu_sub_capacity.csv - RVU subcapacity license metric results \n * bundling_definitions.csv - list of IBM software regardless of its license type and utilization together with details of the computers on which the software is installed \n * readme.txt - a link to this document (technote) \n * checksums.txt, signature.rsa, and pub_key.pem - files used by IBM auditors to verify the authenticity and correctness of the audit snapshot.\n\n\n\nWhy some product instances are not listed in the CSV reports? \n\nCSV reports with information about PVU and RVU MAPC utilization (pvu_full_capacity.csv, pvu_sub_capacity.csv, rvu_full_capacity.csv, and rvu_sub_capacity.csv) list only software instances that were discovered during the license peak value time. If an instance was installed in your environment during the reporting period of the current audit snapshot but was not discovered during the license peak value time, the instance is not listed in the CSV reports. \n\nExample: \nThree instances of DB2 are installed. The reporting period is set to one month and DB2 license utilization is as follows: \n\u00b7 Instance 1 uses the maximum of 100 PVUs, \n\u00b7 Instance 2 uses the maximum of 300 PVUs, \n\u00b7 Instance 3 uses the maximum of 500 PVUs. \n\nThe license peak value occurs when the sum of PVU values for all instances is the highest and equals 800 PVUs (300 PVUs for instance 2 + 500 PVUs for instance 3). The peak occurs during the period that is marked with a red square (it is the license peak value time). The peak usage for instance 1 is outside of the red square. It means that this instance was installed in the environment during the current reporting period but was not discovered during the license peak value time. This instance is not listed in the CSV report. \n\n[\/support\/docview.wss?uid=swg21688543&aid=1] [\/support\/docview.wss?uid=swg21688543&aid=1] \n\n\nWhy some values from the CSV report do not relate back to what is displayed on the user interface? \n\nWhen all values from column M (Physical Server PVU Subcapacity) for a particular product are added, the obtained value is greater that the value that is displayed in the user interface. It happens due to the way that data is presented in CSV reports and on the user interface. \n\nThe All IBM Metrics and IBM PVU subcapacity reports are multilevel, and consist of the following levels:\n1. First level: a list of all products\n[\/support\/docview.wss?uid=swg21688543&aid=2] [\/support\/docview.wss?uid=swg21688543&aid=2] \n\n\n2. Second level: when you click a product name, you go to information about the physical server on which the product is installed.\n[\/support\/docview.wss?uid=swg21688543&aid=3] [\/support\/docview.wss?uid=swg21688543&aid=3] \n\n \n\n3. Third level: when you click the server name, you go to a list of virtual machines that run on this server and have the product installed. \n[\/support\/docview.wss?uid=swg21688543&aid=4] [\/support\/docview.wss?uid=swg21688543&aid=4] \n\n\nThe audit snapshot is not multilevel. However, it has to present the same information that the report that is available in the user interface. Below is an excerpt from the audit snapshot that corresponds to the report that was presented on the screen shots above (some columns are hidden in the snapshot to simplify it).\n\n[\/support\/docview.wss?uid=swg21688543&aid=5] [\/support\/docview.wss?uid=swg21688543&aid=5] \n\n \n\nWhen values in column M are added, PVU consumption equals 480 PVUs. However, these values should not be added because they all refer to a single server (TLM_VM_423\u2026) on which the four VMs run, not an individual VM that is listed in column P (Computer). \n\nThe value in column M is repeated due to the way data needs to be presented in a CSV file. If you want to relate back the value from column M in the audit snapshot to the user interface report, it is the value that you can see in the column PVU Subcapacity Limit on the second level of the report. The value in column L relates back to the column CPU Core Subcapacity on the second level of the report. \n\n \n[\/support\/docview.wss?uid=swg21688543&aid=6] [\/support\/docview.wss?uid=swg21688543&aid=6] \n\n\nPVU and RVU MAPC subcapacity license terms specify license consumption only on the physical server level. PVU and RVU MAPC values cannot be calculated and presented on the virtual machine or LPAR level, and such data is not provided by License Metric Tool or BigFix Inventory. For more information about virtualization capacity license counting rules that are used for PVU and RVU MAPC calculation, see: \nhttp:\/\/www-01.ibm.com\/software\/passportadvantage\/Counting_Software_licenses_using_specific_virtualization_technologies.html [http:\/\/www-01.ibm.com\/software\/passportadvantage\/Counting_Software_licenses_using_specific_virtualization_technologies.html]\n\nRELATED INFORMATION\n Understanding CSV files with metric utilization [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SS8JFY_9.2.0\/com.ibm.lmt.doc\/Inventory\/softinv\/c_understanding_csv.html]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Inventory"}]},{"id":"TRAIN_Q299","question":"Installing fixpacks with Installation Manager - when did it change from using updateInstaller, starting in which version of WebSphere\n\nI was using updateInstaller to install fixpacks, and there was a separate fixpack for WebSphere and separate for the JDK, independent of each other. Now I understand that with Installation Manager there is a single package containing both the WebSphere App server fixpack as well as the JDK. When did this occur, starting with which version of WebSphere ? ","answer":"Starting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.","is_impossible":false,"contexts":[{"filename":"swg21138332.txt","text":"Title: IBM Java SDK Upgrade Policy for the IBM WebSphere Application Server - United States\n\nText:\nupgrade policy TECHNOTE (FAQ)\n\nQUESTION\n What is the Java\u2122 SDK upgrade policy for the IBM\u00ae WebSphere\u00ae Application Server? \n\nCAUSE\nUpdating to the latest compatible Java SDK could help you resolve problems more quickly.\n\nANSWER\nThe IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version. \n\nList of WebSphere Application Server fix packs and the corresponding Java SDK versions [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27005002]\n\nPolicy Summary by WebSphere Application Server release:\n\nWebSphere Application Server V8.0, V8.5, V8.5.5\nStarting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.\n\nWebSphere Application Server V7.0\nAny V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.1\nAny V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.0\nAny V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.1\nAny V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.0\nAny V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.\n\n\n\nDetails of Java SDK Upgrade Policy\n\nWebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:\n\n\n * Matching Java SDK service releases to Application Server releases and fix packs\n \n \n * Delivering updates and fixes associated with the Java SDK on any given Application Server release.\n\n\nIn an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information. \n\nIn some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data. \n\nThere are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process: \n 1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.\n \n \n 2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.\n \n \n 3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.\n \n\n\nThese factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle. \n\nJava SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy. \n\nWebSphere Application Server Support details: \nhttp:\/\/www.ibm.com\/software\/webservers\/appserv\/support.html [http:\/\/www.ibm.com\/software\/webservers\/appserv\/support.html] \n\nIdentifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk. \n\nImportant: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION\n Verify Java SDK version shipped with WebSphere fix pack [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27005002]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"}]},{"id":"TRAIN_Q300","question":"How to access the 2nd portal profile?\n\n Hello,\n\nI created a second WebSphere portal profile (wp_profile2) under C:\\IBM\\WebSphere as part of setting up multi-profile environment on windows using WebSphere Portal 8.0.0.1 CF04\/WAS 8.0.0.10. I started the WebSphere_Portal under this profile successfully and am trying to access this new portal profile from a web browser using http:\/\/<host>:port\/wps\/myportal. I tried all the ports listed in SystemOut log but none of them seem to work and the one that appears to work is writing below error in logs and is showing a blank page:\n\n \n\n[11\/10\/15 9:45:13:374 PST] 00000044 SystemOut O javax.servlet.jsp.JspException: com.ibm.portal.resolver.exceptions.LocalizedIOException: RT7507E: Unable to initialize Repository: Default.\n[11\/10\/15 9:45:13:374 PST] 00000044 SystemOut O at com.ibm.wps.engine.templates.themes.Default.render(Default.java:237)\n[11\/10\/15 9:45:13:374 PST] 00000044 SystemOut O at com.ibm.wps.engine.templates.ThemeTemplate.render(ThemeT\n\n \n\nDoes anyone have any idea of how to fix the above issues and get the portal access working?\n\nAppreciate your help regarding this.\n\n \n\nThank you. ","answer":"Remove the copy so that the only file in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm is icm.properties","is_impossible":false,"contexts":[{"filename":"swg21606716.txt","text":"Title: IBM Message RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2 - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nMessage RT7507E: Unable to initialize Repository: Default occurs in SystemOut.log after successful database transfer from Derby to DB2\n\nSYMPTOM\nYou may see this stacktrace in SystemOut.log after successfully completing the database transfer from Derby to DB2\n\n[6\/25\/12 16:10:19:213 CEST] 0000002e InitServlet E INI8504E:One or more initialization step failed. Please check the server log for details.\ncom.ibm.icm.jcr.RepositoryExistsException: RT7507E: Unable to initialize Repository: Default.\nat com.ibm.icm.jcr.RepositoryFactory.init(RepositoryFactory.java:218)\nat com.ibm.icm.jcr.RepositoryFactory.getRepository(RepositoryFactory.java:479)\nat com.ibm.icm.jcr.servlet.InitServlet.init(InitServlet.java:56)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:336)\nat com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.init(ServletWrapperImpl.java:168)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.loadOnStartupCheck(ServletWrapper.java:1341)\nat com.ibm.ws.webcontainer.webapp.WebApp.doLoadOnStartupActions(WebApp.java:588)\nat com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinally(WebApp.java:559)\nat com.ibm.ws.webcontainer.webapp.WebAppImpl.initialize(WebAppImpl.java:421)\nat com.ibm.ws.webcontainer.webapp.WebGroupImpl.addWebApplication(WebGroupImpl.java:88)\nat com.ibm.ws.webcontainer.VirtualHostImpl.addWebApplication(VirtualHostImpl.java:169)\nat com.ibm.ws.webcontainer.WSWebContainer.addWebApp(WSWebContainer.java:749)\nat com.ibm.ws.webcontainer.WSWebContainer.addWebApplication(WSWebContainer.java:634)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:422)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:714)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1160)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1369)\nat com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:638)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:967)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:766)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:2153)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:445)\nat com.ibm.ws.runtime.component.CompositionUnitImpl.start(CompositionUnitImpl.java:123)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.start(CompositionUnitMgrImpl.java:388)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl.access$500(CompositionUnitMgrImpl.java:116)\nat com.ibm.ws.runtime.component.CompositionUnitMgrImpl$CUInitializer.run(CompositionUnitMgrImpl.java:994)\nat com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:349)\nat com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1659)\n\n\n\n\n\nCAUSE\nRoot cause was having another copy of icm.properties in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm, in this case by making a backup copy in the same directory with name icm-copy.properties\n\nRESOLVING THE PROBLEM\nRemove the copy so that the only file in .\\wp_profile\\PortalServer\\jcr\\lib\\com\\ibm\\icm is icm.properties\n\nRELATED INFORMATION\n Fiddler [http:\/\/www.fiddlertool.com]\nPlug-in MustGather [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21174894]\nWebSphere Portal tracing [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/WebSphere_Portal_runtime_logs_wp7]\nIHS Rewrite rules (mod_rewrite Apache module) [http:\/\/publib.boulder.ibm.com\/infocenter\/wasinfo\/fep\/index.jsp?topic=%2Fcom.ibm.websphere.ihs.doc%2Finfo%2Fihs%2Fihs%2Frihs_apachemods.html]"}]},{"id":"TRAIN_Q301","question":"How do you switch on the indexing of sparse file in StoredIQ?\n\nBy default these are skipped - does anyone know where to switch them on on the dataserver? ","answer":"SSH into the Data Server(s) and enter the following command at the prompt; \n\n\npsql -U dfuser dfdata -c \"insert into adminknobs (name,value,description,valuetype,use) VALUES ('read_sparse_files','1','Read sprase data objects','int','1')\"\n\nIt should return the following;\n\nINSERT 0 1\n\nif so, enter the following command and wait for the UI to come back up;\n\nservice siqinit restart","is_impossible":false,"contexts":[{"filename":"swg21692240.txt","text":"Title: IBM How do I process Sparse data objects Identified in the Audit - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I turn on sparse data object processing \n\nANSWER\nAfter harvesting a volume, the audit may show \"skipped - cannot \naccess data object\", with a sparse data object message recorded in the details section. \n\nTo correct this problem, ensure that no jobs are running. SSH into the Data Server(s) and enter the following command at the prompt; \n\n\npsql -U dfuser dfdata -c \"insert into adminknobs (name,value,description,valuetype,use) VALUES ('read_sparse_files','1','Read sprase data objects','int','1')\"\n\nIt should return the following;\n\nINSERT 0 1\n\nif so, enter the following command and wait for the UI to come back up;\n\nservice siqinit restart\n\nYou can now run harvests as normal and sparse data objects will be processed. If your are using a policy which backs up the original files and just leaves a sparse file viewable that when accessed, will pull the original file forward, you may run into space issues. This is because SIQ will be accessing every sparse file, so the sparse files' size on disk will grow to the same size as the original file."}]},{"id":"TRAIN_Q302","question":"Help with Security Bulletin: Multiple Vulnerabilities identified in IBM Java SDK affect WSRR and WSRR Studio\n\n\n\nI need to understand details regarding Security Bulletin: Multiple Vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio.\n\nThis is related to CVEID:\nCVE-2018-2633\nCVE-2018-2603\nCVE-2018-2579\nCVE-2018-2602\n\nWhere can I find this information?","answer":"CVEID:CVE-2018-2633 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H)","is_impossible":false,"contexts":[{"filename":"swg22013955.txt","text":"Title: IBM Security Bulletin: Multiple Vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 6 used by WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in January 2018.\n\nThese issues are also addressed by WebSphere Application Server Network Deployment shipped with WebSphere Service Registry and Repository. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2018-2633 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H) \nCVEID:CVE-2018-2603 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2603]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137855 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137855]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\nCVEID:CVE-2018-2579 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2579]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.\nCVSS Base Score: 3.7\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137833 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137833]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\nCVEID:CVE-2018-2602 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2602]\nDESCRIPTION:An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.\nCVSS Base Score: 4.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137854 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137854]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:R\/S:U\/C:L\/I:L\/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Service Registry and Repository V8.5 and V8.0 and WebSphere Service Registry and Repository Studio V8.5 are affected.\n\nREMEDIATION\/FIXES\nFor all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.1_IJ04332 [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-Studio-MultiOS-IFIJ04332]\n\nFor WebSphere Service Registry and Repository the issues are addressed by WebSphere Application Server.\n\n\n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server V8.0 \nRefer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with WebSphere Service Registry and Repository: \n\nSecurity Bulletin: Multiple Vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server January 2018 CPU [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22013818] 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 14 March 2018: 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."}]},{"id":"TRAIN_Q303","question":"Error #2070\n\nI purchased the SPSS grad pack and put one of the licenses on one computer and another on this one. This computer crashed and I was forced to reformat the hard drive. Subsequently, I lost SPSS in the process. After reinstalling the program, when I attempted to open a data set I received this error:\nError #2070 The application is unable to communicate properly with the license server. The license server may be down, or there may be other network-related communication or DNS issues interfering. This command is not executed. Specific symptom number: 3. WHat is causing this?","answer":"The above error can be caused by invalid values entered during the licensing phase of installing SPSS Statistics\/Modeler or the client machine cannot reach the Sentinel License Manager host using the machine Hostname.","is_impossible":false,"contexts":[{"filename":"swg21480755.txt","text":"Title: IBM Error # 2070. The license server is down. Specific symptom number: 3 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n We have network installations of IBM SPSS Statistics\/Modeler. When the application is launched, the following errors are reported:\n\n\"The current license does not permit this job to continue.\"\n\nfollowed by...\n\n\"Error # 2070\nThe license server is down. Please check to see that the license server is running or ask your local SPSS coordinator to check the license server.\nThis command is not executed.\nSpecific symptom number: 3.\"\n\nThe Safenet Sentinel License Manager has been licensed and confirmed to be running. \nWhat is the problem? \n\nCAUSE\nThe above error can be caused by invalid values entered during the licensing phase of installing SPSS Statistics\/Modeler or the client machine cannot reach the Sentinel License Manager host using the machine Hostname.\n\nANSWER\nPlease do the following to verify:\n\n1. Navigate to the IBM SPSS Statistics\/Modeler directory and open \"spssprod.inf\", using any text editor. \n\n - By default, SPSS Statistics would store this file in: C:\\Program Files\\IBM\\SPSS\\Statistics\\xx\\ \n\n - By default, SPSS Modeler would store this file in: C:\\Program Files\\IBM\\SPSS\\Modeler\\xx.x\\bin\\\n\n2. Verify the \"DaemonHost\" value matches the Hostname or IP Address of the machine where the Safenet Sentinel License Manager is installed. \n\n - E.g. DaemonHost=MyLicenseServer or DaemonHost=127.0.0.1\n\nIf the DaemonHost value specifies redundant license servers, please do the following if you are using SPSS Statistics 22 (or earlier) or SPSS Modeler 16.0 (or earlier):\n\n\n a). Remove all license servers from the \"DaemonHost\" line and save the file.\n\nb). Create a system environment variable, called LSHOST, on each SPSS client with your redundant license servers as its value. Separate each redundant license server with a colon, e.g.\n==========================\nVariable: LSHOST\nValue: server1:server2:server3\n========================== \n\n\n\nIf the \"DaemonHost\" value is accurate and you are using a Hostname value, you have a name resolution problem. Error # 2070, Symptom number 3 typically means the SPSS client cannot connect to the name resolution database or the name resolution database does not contain a record for the machine where the SPSS Sentinel License Manager resides. To verify, please do the following:\n\n1. Run lswhere.exe (which is located in the SPSS directory, see above) from the problematic SPSS Client machine and take note of the displayed output. The following is an example of the output: \n\n\n==========================\nSentinel LM 8.x.x Search Tool For License Servers\nCopyright (C) 20xx Rainbow Technologies, Inc.\n\nServer Address : xxx.xxx.xxx.xxx\nServer Name : Machine_A\n========================== \n\n\nIf the Safenet Sentinel License Manager machine is not listed or you encounter the error, \"Error[17]: Probably no servers are running on this subnet.\", please add the following system environment variable to the IBM SPSS Statistics\/Modeler client and run lswhere.exe again: \n\n\n==========================\nVariable: LSHOST\nValue: Name or IP address of the License Manager machine \n========================== \n\n\nFor information about defining environment variables, see the Network License Administrator's Guide. If using the LSHOST environment variable does not render the Safenet Sentinel License Manager machine, try using LSFORCEHOST instead.\n\n2. When you see the Safenet Sentinel License Manager machine name and corresponding IP address listed in the lswhere output, ping the displayed Server Name from a command line, e.g.\n\n\n==========================\nping Machine_A\n========================== \n\n\nAn example of the resulting output is as follows:\n==========================\nUnknown host Machine_A\n========================== \n\n\nIf the ping command is unable to resolve the Server Name, you have a name resolution problem and must address it (with help from your IT Administrator\/Help Desk team) before IBM SPSS Statistics\/Modeler can acquire a license from the Sentinel License Manager.\n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/modeler\/?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/spsslicensing.html]\nA simplified Chinese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21641554]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Statistics Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Platform Independent Not Applicable Business Analytics SPSS Amos Windows Not Applicable Business Analytics SPSS SamplePower Platform Independent Not Applicable \nHISTORICAL NUMBER\n 51910"}]},{"id":"TRAIN_Q304","question":"In FileNet Workplace XT .csv files open as a text file instead of using MS Excel\n\nThe .csv file was created through WorkplaceXT and it only can be opened as the text file instead of the Excel file, and the mime type is text\/csv, not application\/vnd.ms-excel. However, when creating the same .csv document through ACCE, the mime Type is \"application\/vnd.ms-excel\" shown under the Properties tab and Content Element tab.","answer":"Add a section to Web.xml mapping the extension to the mime type: \n\n * \n * <mime-mapping>\n <extension>csv<\/extension>\n <mime-type>application\/vnd.ms-excel<\/mime-type>\n <\/mime-mapping>","is_impossible":false,"contexts":[{"filename":"swg21972681.txt","text":"Title: IBM In FileNet Workplace XT .csv files open as a text file instead of using MS Excel - United States\n\nText:\nMime type TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nPROBLEM(ABSTRACT)\n The .csv file was created through WorkplaceXT and it only can be opened as the text file instead of the Excel file \n\nSYMPTOM\nThe .csv file can be opened as the Excel from ACCE and outside of WorkplaceXT but not from inside of the WorkplaceXT\n\n\nCAUSE\nMime Type was not set correctly when creating the .csv documents via WorkplaceXT\n\nDIAGNOSING THE PROBLEM\nWhen creating a .csv document through ACCE, the mime Type is \"application\/vnd.ms-excel\" shown under the Properties tab and Content Element tab. \n\n * When adding a .csv document through WorkplaceXT, the mime Type shows \"text\/csv\" from the Properties tab and Content Element tab in ACCE. \n * Verify if the .csv document with the mime Type \"application\/vnd.ms-excel\" is opened as Excel file in WorkplaceXT\n\nRESOLVING THE PROBLEM\nAdd a section to Web.xml mapping the extension to the mime type: \n\n * \n * <mime-mapping>\n <extension>csv<\/extension>\n <mime-type>application\/vnd.ms-excel<\/mime-type>\n <\/mime-mapping>"}]},{"id":"TRAIN_Q305","question":"Need help accessing my SPSS access code?\n\nI downloaded SPSS GradPack (Standard) 25 6 Months for my Mac. The IBM SPSS Statistics 24 licensing page pops up for me to enter the code. I enter the code provided and then hit next, and it tells me the code is too short to be valid? What code do I use then? I need this resolved fast, my first assignment is due soon. I was only given a 16-digit access code, not a 20-digit?\n\n\n\nThis dW Answers question is about an IBM document with the Title:\nSPSS Student Version and Graduate Pack Resources","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q306","question":"Hey, how can I transfer my spss 24 licence from my old macbook to the new one?\n\n\n\nI made the backup from my laptop to my new one, but SPSS doesnt allow me to start, because of the licence! Also I tried the SPSS Licence wizard on the new macbook, but it is not possible to fill in my licence\n\nI didn't find a option to deactivate the licence on the previous macbook.. how can I solve this problem?\n","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.","is_impossible":false,"contexts":[{"filename":"swg21966637.txt","text":"Title: IBM Getting a warning message 'You do not have the correct administrator privileges' when attempting to license a SPSS Statistics product on Mac OS. - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You have successfully installed an IBM SPSS Statistics product on a Mac computer. When you start the License Authorization Wizard (LAW) to enter the authorization code for licensing.\n\nYou receive the following message:\n\n\n\"Warning! You do not have the correct administrator privileges to license this product. Log in as administrator and try again, or contact your network administrator to correct this issue.\n\n\"\n\nOnce this message is displayed the only option available is \"OK\" to click on and you cannot enter your authorization code. \n\nRESOLVING THE PROBLEM\nBelow is a picture of the warning: \n\n[\/support\/docview.wss?uid=swg21966637&aid=1] [\/support\/docview.wss?uid=swg21966637&aid=1]\n\nIf you encounter this message, perform the following procedure:\n\n\n 1. If open, close the IBM SPSS Statistics product. \n 2. If open, close the License Authorization Wizard. \n 3. Open Finder. \n 4. Select the 'Go' menu. \n 5. Select the 'Utilities' menu. \n 6. Open the 'Terminal' program. \n 7. Type (copy\/paste) the following command:\n \n cd \/Applications\/IBM\/SPSS\/Statistics\/ \n 8. \n 9. Press Enter\/Return. \n 10. Perform the procedure corresponding to the Statistics product version as described below:\n\n\nStatistics Release 20 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 20\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 21 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 21\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 22 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 22\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\n\nStatistics Release 23 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 23\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nStatistics Release 24 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 24\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product. \n 7. \n 8. \n\nStatistics Release 25 1. Type (copy\/paste) the following command: \n \n sudo chown -R root:admin 25\n \n 2. Press Enter\/Return. \n 3. Close Terminal. \n 4. Launch the License Authorization Wizard. \n 5. The warning message should no longer appear. \n 6. License your IBM SPSS Statistics product.\n\n\nTo confirm the changes have been made (1) In the Terminal window change directory to below path (example for release 22) \n\ncd \/Applications\/IBM\/SPSS\/Statistics\/22\/SPSSStatistics.app\/Contents \n\nthen, type the following: \n\nls -l \n\n(2) Press Enter\/Return. \n\n \n\nIf you see some or all of subfolders shows a group ownership other than 'admin' (as displayed in Picture1), the procedure did not succeed. You will need to have your Mac IT support contact IBM SPSS Support for further assistance. \n\nPicture1:\n[\/support\/docview.wss?uid=swg21966637&aid=2] [\/support\/docview.wss?uid=swg21966637&aid=2]\n\nPicture 2: \n\nIf you see some or all of subfolders shows a group ownership of 'admin' (as displayed in Picture2), the procedure was successful.\n[\/support\/docview.wss?uid=swg21966637&aid=3] [\/support\/docview.wss?uid=swg21966637&aid=3]\n\nThis behavior is also reported on the following product correction report (APAR): [https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\n[https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\nhttps:\/\/www.ibm.com\/support\/entdocview.wss?uid=swg1PI41134 [https:\/\/www-304.ibm.com\/support\/entdocview.wss?uid=swg1PI41134]\n\nAn IBM ID is required to access this material.\n\nIf needed, an IBM ID may be created at https:\/\/ibm.biz\/ibm_web_id [https:\/\/ibm.biz\/ibm_web_id]\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]\nNeed more help? Our Licensing forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/spsslicensing.html]"}]},{"id":"TRAIN_Q307","question":"Product upgrade installed a second instance of the DE, causing upgrade failure.\n\nThe Deployment Engine should only have one instance installed on a server with IBM products installed. In this case, a second DE was installed, which caused the failure of the Product upgrade. Error: Wrong Deployment Engine.\n\nProduct install failed. You will get a message similar to this: You are updating an instance of (Product name) that was installed using the Tivoli Deployment Engine (DE) located at \"\/home\/nc_admin\/.acsi_FQDN\". However you are now using the DE located at \"\/home\/nc_admin\/.acsi_HOSTNAME\".\n\nWhen the DE is installed as non-root ( in this case nc_admin ), it will install the DE in the user home directory, in this case \/home\/nc_admin, and use the FQDN in the name: \/home\/nc_admin\/.acsi_FQDN","answer":"There are two options to fix this problem. \n\n1) Make sure the current upgrade is using the same version of JVM as the original install. \n\n2) Removing the newly created DE, which shouldn't have been created, then creating a link to the existing DE is the best work around in this case. The Product upgrade will see the link and add the information to the valid DE install.","is_impossible":false,"contexts":[{"filename":"swg21967589.txt","text":"Title: IBM Product upgrade installed a second instance of the DE, causing upgrade failure. - United States\n\nText:\nDEL2INST; Tivoli; Deployment; Engine; FQDN; Duplicate; acsi TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Deployment Engine should only have one instance installed on a server with IBM products installed. In this case, a second DE was installed, which caused the failure of the Product upgrade.\nError: Wrong Deployment Engine. \n\nSYMPTOM\nProduct install failed. You will get a message similar to this:\nYou are updating an instance of <Product name> that was installed using \nthe Tivoli Deployment Engine (DE) located at \"\/home\/nc_admin\/.acsi_<Fully Qualified hostname>\". \nHowever you are now using the DE located at \"\/home\/nc_admin\/.acsi_<hostname>\". \n\n\nWhen the DE is installed as non-root ( in this case nc_admin ), it will install the DE in the user home directory, in this case \/home\/nc_admin, and use the FQDN in the name: \/home\/nc_admin\/.acsi_<Fully Qualified hostname> \n\n\nCAUSE\nBecause the two Product installs used different versions of JVM, the underlying Java is using \"hostname\" for one version of JVM, and \"Fully Qualified hostname\" for the other. The DE normally uses the FQDN appended to the \"acsi_\" string to create the DE directory:\n\nFor example, if the Product is being installed as user \"nc_admin\" and the entry in \/etc\/hosts is this:\n\nx.xx.xxx.xx server_name.corporation.net server_name\n\nThe hostname is \"server_name\"\nFully Qualified hostname (FQDN) is \"server_name.corporation.net\"\n\n\nENVIRONMENT\nUpgrading existing product that uses the Deployment Engine on a UNIX server\n\n\n\nDIAGNOSING THE PROBLEM\nOutput similar to this when the Product install fails: \n\nthe Tivoli Deployment Engine (DE) located at \"\/home\/nc_admin\/.acsi_<Fully qualified hostname>\". \nHowever you are now using the DE located at \"<User_home>\/nc_admin\/.acsi_<hostname>\"\n\n\nRESOLVING THE PROBLEM\nThere are two options to fix this problem. \n\n1) Make sure the current upgrade is using the same version of JVM as the original install. \n\n2) Removing the newly created DE, which shouldn't have been created, then creating a link to the existing DE is the best work around in this case. The Product upgrade will see the link and add the information to the valid DE install. \n\n*IMPORTANT NOTE: The Product install failure message will tell you what instance of the DE is valid, please refer to the error message in the \"Symptom\" section above. \n\n At this point there will be the following in the DE_HOME directory: \n\n .acsi_<FQDN> ( Valid DE installation ) \n\n .acsi_<userid> ( link to .acsi_<FQDN> ) \n\n .acsi_<hostname> ( Invalid DE directory created by the failed Product upgrade ) \n\n This can be confirmed by referring to the Product install error. \n\n Removing the invalid DE and creating softlink: \n\n - Backup the original DE installation directory: <DE_HOME>\/.acsi_<FQDN> \n\n - Move the new invalid DE directory to a backup directory: <DE_HOME>\/.acsi_<hostname> \n\n - Create a soft link to the \"good\" DE install \n\n cd <DE_HOME> \n\n ln -s <DE_HOME>\/.acsi_<FQDN> .acsi_<hostname> \n\n - Confirm the link was created successfully, it should look like this: \n> ls -lart \nlrwxrwxrwx 1 nc_admin ncoadmin <date> .acsi_<hostname> -> <DE_HOME>\/.acsi_<FQDN> \n\n \n3) Retry the product install. You will need to confirm there is no required cleanup before retrying the Product upgrade."}]},{"id":"TRAIN_Q308","question":"Datacap Navigator Verify\n\nWhen i run a Batch for Verification in Datacap Navigator.. Fields are not getting displayed .. same fields can be seen in tmweb. How do I access the client log in Internet Explorer?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q309","question":"How do I resolve CSQX620E System SSL error function 'gsk_secure_socket_init' RC=440?\n\nWhen trying to establish an SSL\/TLS connection from a queue manager running on a Unix server to a queue manager running on z\/OS, I am getting the following error message:\nCSQX620E CSQXRESP System SSL error,\n \nchannel ????\n \nconnection (ipaddr)\n \nfunction 'gsk_secure_socket_init' RC=440\n\nI can successfully connect from the mainframe to the Unix server.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q310","question":"What may be the cause of unclosed MQ object connections on DataPower?\n\nHow can I resolve open MQ object connections that did not close out on DataPower?","answer":"Change the cache timeout on the IBM WebSphere DataPower MQ manager (mq-qm) object. You can start using a value of 60 seconds as the suggestion. The best practice is to use a value which should be less than the KeepAlive Timeout of the MQ Queue Manager (qmgr).","is_impossible":false,"contexts":[{"filename":"swg21380213.txt","text":"Title: IBM WebSphere DataPower SOA Appliance MQ Manager Object's connections are not closed as expected. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n IBM WebSphere DataPower SOA appliance MQ Manager Object's connections are not closed as expected. This can happen when the mq-qm object uses the default value which is an empty string. \n\nCAUSE\nDataPower MQ manager object's idle connection is not closed when using default cache timeout.\n\nANSWER\nChange the cache timeout on the IBM WebSphere DataPower MQ manager (mq-qm) object. You can start using a value of 60 seconds as the suggestion. The best practice is to use a value which should be less than the KeepAlive Timeout of the MQ Queue Manager (qmgr)."}]},{"id":"TRAIN_Q311","question":"S878 abends during CICS startup after applying PTF for OA45950\n\nAfter applying the PTF for z\/OS APAR OA45950, why am I suddenly receiving many S878 abends when I bring up my CICS regions? No CICS system or application software changes were made. \nThe PTF numbers for APAR OA45950 for the various MVS releases are:\nRelease C10 : UA75818 available 15\/02\/25 (F502 ) \nRelease D10 : UA75819 available 15\/02\/25 (F502 ) \nRelease 210 : UA75838 available 15\/02\/25 (F502 ) ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q312","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593)\n\nI need to understand details regarding \"Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (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)","is_impossible":false,"contexts":[{"filename":"swg21962370.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition Version 6 and 7 that are used by IBM Image Construction and Composition Tool. 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 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: \n\n * For IBM Image Construction and Composition Tool v2.2.1.3 * IBM Image Construction and Composition Tool v2.2.1.3 Build 28\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 [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 For IBM Image Construction and Composition Tool v2.3.1.0 * IBM Image Construction and Composition Tool v2.3.1.0 Build 38\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 [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 For IBM Image Construction and Composition Tool v2.3.2.0 * IBM Image Construction and Composition Tool v2.3.2.0 Build 12\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 [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 \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 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 21 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."}]},{"id":"TRAIN_Q313","question":"Why am I seeing a java.lang.StackOverflowError in Portal?\n\nMy Portal process pid \/ java.exe is suddenly disappearing. Reviewing the SystemOut.log files around the time it disppears, I am seeing the following:\n\n[datetime] 000007c1 ServletWrappe E\ncom.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0014E: [....]\n\nnested exception is\njava.lang.StackOverflowError\nat\norg.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherS ervlet.java:837)\n\nWhat is causing this?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q314","question":"how to Configure the server to only accept strong encryption protocols such as TLS1.1?\n\nhow to Configure the server to only accept strong encryption protocols such as TLS1.1?","answer":"For all releases and versions of Apache based IBM HTTP Server, IBM recommends disabling SSLv3: \n\n\nAdd the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains \"SSLEnable\":\n\n# Disable SSLv3 for CVE-2014-3566\n# SSLv2 is disabled in V8R0 and later by default, and in typical V7\n# and earlier configurations disabled implicitly when SSLv3 ciphers \n# are configured with SSLCipherSpec.\nSSLProtocolDisable SSLv3 SSLv2\n\nStop and restart IHS for the changes to take affect.","is_impossible":false,"contexts":[{"filename":"swg21687172.txt","text":"Title: IBM Security Bulletin: Vulnerability in SSLv3 affects IBM HTTP Server (CVE-2014-3566) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled by default in the Apache based IBM HTTP Server. \n\nVULNERABILITY DETAILS\nCVE ID: CVE-2014-3566 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566]\nDESCRIPTION: IBM HTTP Server could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plain text of encrypted connections. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013] 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\nThis vulnerability affects all versions and releases of IBM HTTP Server (IHS) component in all editions of WebSphere Application Server and bundling products.\n\n\nREMEDIATION\/FIXES\nThere is no separate interim fix for the PI27904 APAR that is associated with this issue, but the interim fix for APAR PI31516 (TLS Padding Vulnerability CVE-2014-8730 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21692502]) includes the update for APAR PI27904. APAR PI27904 update disables SSLv3 by default for IHS 7.0 and newer, and adds the 'SSLProtocolEnable' directive into IHS 7.0. \n\nThe update for PI27904 will be included in fix packs 7.0.0.37, 8.0.0.10 and 8.5.5.4. \n\n\nWORKAROUNDS AND MITIGATIONS\nFor all releases and versions of Apache based IBM HTTP Server, IBM recommends disabling SSLv3: \n\n\nAdd the following directive to the httpd.conf file to disable SSLv3 and SSLv2 for each context that contains \"SSLEnable\":\n\n# Disable SSLv3 for CVE-2014-3566\n# SSLv2 is disabled in V8R0 and later by default, and in typical V7\n# and earlier configurations disabled implicitly when SSLv3 ciphers \n# are configured with SSLCipherSpec.\nSSLProtocolDisable SSLv3 SSLv2\n\nStop and restart IHS for the changes to take affect.\n\nNote: \n\n * If you start IHS with the -f command line argument, or you use the \"Include\" directive to include alternate configuration files, you may need to search those filenames for SSLEnable.\n\n * If you configure SSL with SSLEnable in the global (non-virtualhost) scope, you will need to move SSLEnable into a virtualhost scope to add SSLProtocolDisable\n\n\nIBM recommends that you review your entire environment to identify other areas that enable SSLv3 protocol and take appropriate mitigation (such as disabling SSLv3) and remediation actions. 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\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 v2 Guide [http:\/\/www.first.org\/cvss\/v2\/guide] \nOn-line Calculator v2 [http:\/\/nvd.nist.gov\/CVSS-v2-Calculator] \nHTTPS advisor fails when SSLv3 is disabled on backend servers [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21691795] TLS Padding vulnerability CVE-2014-8730 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21692502]\n\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 October 2014: original document published\n03 November 2014: added extra notes \n02 December 2014: added link to reference section\n28 January 2015: added links to CVE-2014-8730 \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."}]},{"id":"TRAIN_Q315","question":"Can CMS certificates be created with a keysize greater than 1024?\n\nWe are trying to determine if a keysize can be greater than 1024. Any insight would be appreciated. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q316","question":"Datapower WebGUI down due to an expired or invalid certificate\n\nThe Datapower WebGUI is down due to an expired or invalid certificate. How can the WebGUI access be restored? ","answer":"The following commands will reset the RBM's, ACL's, WebGUI and SSH services to the default settings. \n\nNote: If the ssh is working, you may omit any commands with the ssh. \n\n \n\nconfig \n\nweb-mgmt \n\nno ssl \n\nexit \n\nwrite mem \n\ny \n\nno web-mgmt \n\nno ssh \n\nrbm \n\nreset \n\nexit \n\nacl web-mgmt \n\nreset \n\nexit \n\nacl ssh \n\nreset \n\nexit \n\nwrite mem (key step to remove the current settings) \n\ny \n\nweb-mgmt <ip to listen on or 0.0.0.0 for all> <port to use default is9090> \n\nssh <ip to listen on or 0.0.0.0 for all> <port to use default is22> \n\nwrite mem \n\ny","is_impossible":false,"contexts":[{"filename":"swg21498634.txt","text":"Title: IBM Unable to connect using network services: WebGUI or ssh after upgrading WebSphere DataPower firmware - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why can't I access the Web managment or ssh after upgrading firmware? \n\nCAUSE\nThis can occur if you are using a custom certificate or authentication for the management services and any of the associated certificates are expired. Expired certificates are removed at upgrade time.\n\nANSWER\nThe first step is to verify that the network is functioning correctly using these commands: \n\nshow int \n\nshow int mode \n\nshow route \n\n \n\nThose commands will show if there is any network activity as well as the ethernet link speed. \n\nOnce the network is confirmed, the quickest way to recover the web management and ssh services is to delete and recreate them with the default settings using the serial console. \n\nThe following commands will reset the RBM's, ACL's, WebGUI and SSH services to the default settings. \n\nNote: If the ssh is working, you may omit any commands with the ssh. \n\n \n\nconfig \n\nweb-mgmt \n\nno ssl \n\nexit \n\nwrite mem \n\ny \n\nno web-mgmt \n\nno ssh \n\nrbm \n\nreset \n\nexit \n\nacl web-mgmt \n\nreset \n\nexit \n\nacl ssh \n\nreset \n\nexit \n\nwrite mem (key step to remove the current settings) \n\ny \n\nweb-mgmt <ip to listen on or 0.0.0.0 for all> <port to use default is9090> \n\nssh <ip to listen on or 0.0.0.0 for all> <port to use default is22> \n\nwrite mem \n\ny \n\n \n\nOnce complete, test the service and confirm you can now access the appliance. Then you may work to configure any custom certificates or authentication settings desired. \n\nIf this does not resolve the issue Contact DataPower Support [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21236322]\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower B2B Appliance XB60 4.0.2, 4.0.1, 5.0.0, 6.0.0 All Editions Business Integration WebSphere DataPower SOA Appliances Firmware 4.0.2, 4.0.1, 5.0.0, 6.0.0, 6.0.1 Edition Independent Business Integration WebSphere DataPower XML Security Gateway XS40 Firmware 4.0.2, 4.0.1, 5.0.0, 6.0.0 All Editions"}]},{"id":"TRAIN_Q317","question":"How to resolve DataPower firmware loading error % Loading firmware failed: Internal receive API error (3)?\n\nMessage % Loading firmware failed: Internal receive API error (3) was observed during firmware update. How do you resolve this issue? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q318","question":"fixlets do not appear in console bigfix\n\n\n\nWork with ILTM 9.2.7 \/ 9.5.4.38. In the bigfix console the fixlets do not appear, under the tree: Sites-> IBM License Reporting (ILTM) v9 -> Fixlets and Task.\n\nAttached image. Do you have any ideas?\n\nGreetings and thank you BigFix","answer":"Check with the firewall\/proxy\/IPS\/network admin and ask them to check the logs for dropped packets or downloads and to adjust the rules to allow the BES Support site content through. \n 2. Try turning off Internet Explorer Enhanced Security Configuration [https:\/\/blogs.technet.microsoft.com\/chenley\/2011\/03\/10\/how-to-turn-off-internet-explorer-enhanced-security-configuration\/] for Administrators to see if this resolves the issue.","is_impossible":false,"contexts":[{"filename":"swg21974546.txt","text":"Title: IBM BigFix Server unable to gather site content from sync.bigfix.com (error: Unexpected HTTP response: 404) - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Identifying a block between the BigFix Server and IBM BigFix's sync.bigfix.com content servers. \n\nSYMPTOM\nError messages similar to the following in the BESRelay.log on the BigFix server: \n\n * \n * \n * http:\/\/sync.bigfix.com\/cgi-bin\/bfgather\/bessupport?Time=1452540085:\n * \n * \n * \n * \n * Error messages similar to the following in the GatherDB.log on the BigFix server:\n Mon, 11 Jan 2016 14:43:22 -0500 -- Unexpected exception during gather of site BES Support: Unexpected HTTP response: 404\n\n\nNote: If the BES Support cannot gather for the first time the entire console is empty of its UI elements. \nCAUSE\n \n\n 1. There is most likely an Intrusion Prevention System (IPS) between the BigFix server and our content sites at sync.bigfix.com that is dropping the download because it is detecting something in the download (one of the sites files) as being malicious. If you do not have an IPS between the BigFix server and the sync.bigfix.com servers; it may be the firewall or proxy appliance that is causing the issue. \n 2. Another cause might be that Internet Explorer Enhanced Security Configuration is enabled for Administrators on the BigFix Windows server machine.\n\nRESOLVING THE PROBLEM\n \n\n 1. Check with the firewall\/proxy\/IPS\/network admin and ask them to check the logs for dropped packets or downloads and to adjust the rules to allow the BES Support site content through. \n 2. Try turning off Internet Explorer Enhanced Security Configuration [https:\/\/blogs.technet.microsoft.com\/chenley\/2011\/03\/10\/how-to-turn-off-internet-explorer-enhanced-security-configuration\/] for Administrators to see if this resolves the issue."}]},{"id":"TRAIN_Q319","question":"Why does my login fail when I use the ltpa-usrnm attribute?\n\nYou use a Domino server as your LDAP, and the login attribute you want to use is ltpa-usrnm. This is acceptable, as the login attribute can be set accordingly in the wimconfig.xml. When the search string is built for the login, it is in the form, cn=username, o=orgname.\n\nThis cause the following exception to the returned:\n\n[3\/30\/16 9:56:03:453 CDT] 000000f7 exception E com.ibm.ws.wim.adapter.ldap.LdapConnection getAttributes CWWIM4520E The 'javax.naming.InvalidNameException: \"CN=username\/O=orgname\": [LDAP: error code 34 - Invalid DN Syntax]; remaining name '\"CN=username\/O=orgname'\"; ","answer":"You need to set a custom property using the following\n command\n \n $AdminTask configureAdminWIMUserRegistry {-customProperties\n {\"com.ibm.ws.wim.registry.allowDNPrincipalNameAsLiteral\n =true\"} }\n \n When this property is set, VMM determines whether the login\n name ends with a baseEntry. If the login name does not end\n with a baseEntry it is not treated as a DN and the login is\n successful.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.4 and 8.5.0.1.","is_impossible":false,"contexts":[{"filename":"swg1PM66670.txt","text":"Title: IBM PM66670: WHEN LOGIN ATTRIBUTE VALUE HAS \"=\" SIGN IN IT, INVALIDUNIQUENAME EXCEPTION IS THROWN. - United States\n\nText:\n FIXES ARE AVAILABLE\n8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033190]\n8.5.0.1: WebSphere Application Server V8.5 Fix Pack 1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033606]\n8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033754]\n8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034672]\n8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034673]\n8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035457]\n8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036729]\n8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037574]\n8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039242]\n8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040425]\n8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041590]\n8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042746]\n8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044096]\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 * UniqueName formation was incorrect which leads to login failure\n with 6\/5\/12 9:53:35:968 EDT] 00000087 UserRegistryI E\n SECJ0363E: Cannot create credential for the user tw=admin\n because of the following exception\n com.ibm.websphere.wim.exception.InvalidUniqueNameException:\n CWWIM0515E The 'tw=admin' entity is not in the scope of the\n 'defined' realm.\n at\n com.ibm.ws.wim.RepositoryManager.getRepositoryIndexByUniqueName(\n RepositoryManager.java:333)\n at\n com.ibm.ws.wim.RepositoryManager.getRepositoryID(RepositoryManag\n er.java:279)\n at\n com.ibm.ws.wim.ProfileManager.retrieveEntityFromRepository(Profi\n leManager.java:2800)\n at\n com.ibm.ws.wim.ProfileManager.retrieveEntity(ProfileManager.java\n :2916)\n at\n com.ibm.ws.wim.ProfileManager.getImpl(ProfileManager.java:1614)\n at\n com.ibm.ws.wim.ProfileManager.genericProfileManagerMethod(Profil\n eManager.java:364)\n at\n com.ibm.ws.wim.ProfileManager.get(ProfileManager.java:417)\n at\n com.ibm.websphere.wim.ServiceProvider.get(ServiceProvider.java:3\n 66)\n at\n com.ibm.ws.wim.registry.util.BridgeUtils.getEntityByIdentifier(B\n ridgeUtils.java:622)\n at\n com.ibm.ws.wim.registry.util.UniqueIdBridge.getUniqueUserId(Uniq\n ueIdBridge.java:202)\n at\n com.ibm.ws.wim.registry.WIMUserRegistry$6.run(WIMUserRegistry.ja\n va:568)\n at\n com.ibm.ws.security.auth.ContextManagerImpl.runAs(ContextManager\n Impl.java:5445)\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server *\n ****************************************************************\n * PROBLEM DESCRIPTION: Virtual member manager (VMM) throws *\n * InvalidUniqueNameException when the *\n * login attribute value contains an *\n * equal sign \"=\". *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n VMM throws InvalidUniqueNameException when the login attribute\n value contains a \"=\". When an equal sign \"=\" is encountered in\n the login name for example 'tw=admin', VMM treats this as a\n distinguished name (DN) and hence the login fails.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * You need to set a custom property using the following\n command\n \n $AdminTask configureAdminWIMUserRegistry {-customProperties\n {\"com.ibm.ws.wim.registry.allowDNPrincipalNameAsLiteral\n =true\"} }\n \n When this property is set, VMM determines whether the login\n name ends with a baseEntry. If the login name does not end\n with a baseEntry it is not treated as a DN and the login is\n successful.\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.4 and 8.5.0.1. 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 PM66670\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\n \n \n * SUBMITTED DATE\n 2012-06-13\n \n \n * CLOSED DATE\n 2012-07-13\n \n \n * LAST MODIFIED DATE\n 2012-07-13\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"}]},{"id":"TRAIN_Q320","question":"Command Line and Silent configuration for ITCAM J2EE 7.1.1 agent\n\nI am seeing unexpected behaviors when using Command Line (interactive or silent) configuration for J2EE DC when trying to enable MS or TT features. These do not seem to work. Are these configuration methods supported? ","answer":"Supported methods are GUI and silent configuration. \n\nAlso, silent configuration fully works both on UNIX and Windows platforms only at level 7.1.1.0.4.\nBefore this maintenance level there were issues and limitations with Managing Server and Transaction Tracking integration. \n\n \n\nSupport Command Line configuration for J2EE DC will possibly be added in some future patch via Request For Enhancement.","is_impossible":false,"contexts":[{"filename":"swg21902438.txt","text":"Title: IBM Command Line configuration for J2EE Data Collector - United States\n\nText:\nITCAM; J2EE; CLI; configurator; CAMJ2ALL; CAMJ2INST TECHNOTE (FAQ)\n\nQUESTION\n Command Line configuration for J2EE DC is not working as expected when trying to enable MS or TT features. \n\nCAUSE\nInteractive CLI configuration is not supported with ITCAM J2EE 7.1.1, including last available level 7.1.1.0.4.\n\nANSWER\nSupported methods are GUI and silent configuration. \n\nAlso, silent configuration fully works both on UNIX and Windows platforms only at level 7.1.1.0.4.\nBefore this maintenance level there were issues and limitations with Managing Server and Transaction Tracking integration. \n\n \n\nSupport Command Line configuration for J2EE DC will possibly be added in some future patch via Request For Enhancement."}]},{"id":"TRAIN_Q321","question":"Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect (CVE-2017-10115, CVE-2017-10116). Where can I find this information?","answer":"CVEID: CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876] 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:N\/A:N) \n\nCVEID: CVE-2017-10116 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H)","is_impossible":false,"contexts":[{"filename":"swg22008382.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 used by IBM API Connect. \n\nThese issues were disclosed as part of the IBM Java SDK updates in July 2017. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876] 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:N\/A:N) \n\nCVEID: CVE-2017-10116 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.7.2\n\nREMEDIATION\/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation\/First Fix IBM API Connect \n\nV5.0.0.0 - 5.0.6.3 5.0.6.4 LI79805 Addressed in IBM API Connect V5.0.6.4.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+API+Connect&release=5.0.6.3&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\nV5.0.7.0 - 5.0.7.2 5.0.8.0 LI79805 Addressed in IBM API Connect V5.0.8.0.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps:\/\/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 [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] \nIBM Java SDK July 2017 Security Bulletin [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22007002] \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 18 September 2017: 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."}]},{"id":"TRAIN_Q322","question":"EIF probe not receiving itm events\n\nEIF probe not receiving itm events\nWhy is the event in the netcool isn't cleaned ? ","answer":"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(<RST>) the TCP\/IP connection after it receives the event and it never shows up in the EIF logs, so the event is just dropped.","is_impossible":false,"contexts":[{"filename":"swg21978641.txt","text":"Title: IBM EIF probe not receiving itm events - United States\n\nText:\nom_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(<RST>) 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)"}]},{"id":"TRAIN_Q323","question":"How to adjust font and padding of rows in the Web GUI Event Viewer of Netcool\n\nYou would like to change the font and padding of event rows.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q324","question":"Help with Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Business Monitor (CVE-2015-0138)\n\nI need to understand details regarding Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Business Monitor (CVE-2015-0138). Where can I find this information? ","answer":"CVEID: CVE-2015-0138 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0138]\n\nDESCRIPTION: A vulnerability in various IBM SSL\/TLS implementations could allow a remote attacker to downgrade the security of certain SSL\/TLS connections. An IBM SSL\/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS\/SSL traffic between vulnerable clients and servers. \nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:N\/I:P\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21700865.txt","text":"Title: IBM Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with IBM Business Monitor (CVE-2015-0138) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n WebSphere Application Server is shipped as a component of IBM Business Monitor. Information about a security vulnerability affecting WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0138 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0138]\n\nDESCRIPTION: A vulnerability in various IBM SSL\/TLS implementations could allow a remote attacker to downgrade the security of certain SSL\/TLS connections. An IBM SSL\/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS\/SSL traffic between vulnerable clients and servers. \nThis vulnerability is also known as the FREAK attack.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691] 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\nThe following products are affected: \n\n * WebSphere Business Monitor V7.0.0.x \n * IBM Business Monitor V7.5.x \n * IBM Business Monitor V8.0.1.x \n * IBM Business Monitor V8.5.5.0 \n * IBM Business Monitor V8.5.6.0\n\nREMEDIATION\/FIXES\nTo remediate this issue, refer to Security Bulletin: Vulnerability with RSA Export Keys may affect IBM WebSphere Application Server (CVE-2015-0138) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21698613]\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 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\nCVE-2015-0138 was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA \n\nCHANGE HISTORY\n 2015-03-30: 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. \n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21701544]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Business Monitor Security AIX, Linux, Linux zSeries, Solaris, Windows 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0"}]},{"id":"TRAIN_Q325","question":"While attempting to upgrade Portal\/WCM 7.0x to CF28 it fails with prerequisite errors.\n\nThe upgrade fails and displays the following message...\n\"A product prerequisite relationship was not satisified. The fix PI10705 is not supported on any of these products.\nPlease fix the problem or de-select the invalid efix from the list and try again.\" ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q326","question":"Is Re-naming the WebSphere Portal installation directory and cell name for an existing clustered installation possible?\n\nQuestion: Is re-naming the WebSphere Portal installation directory and cell name for an existing clustered installation possible? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q327","question":"Help with Security Bulletin: IIB is affected by an Apache Tomcat related vulnerability (CVE-2017-7674)\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by an Apache Tomcat related vulnerability (CVE-2017-7674). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q328","question":"Rules view statistics shows no statistics\n\n\n\nWe converted the single RulesMgrSvr in a cluster and added a second RulesMgrSvr member on another node.\n\nThe rules console on the first node works fine.\n\nOn the second member view statistics fails, no statistics or error messages are shown","answer":"It is possible to deploy several Rule Execution Server (RES) Console in the same cluster, however there are some administrative interactions from RES components to RES console that may not work due to the presence of more than one RES management stack within the same administrative scope.","is_impossible":false,"contexts":[{"filename":"swg21449103.txt","text":"Title: IBM Limitations when deploying more than one Rule Execution Server console - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n It is possible to deploy several Rule Execution Server (RES) Console in the same cluster, however there are some administrative interactions from RES components to RES console that may not work due to the presence of more than one RES management stack within the same administrative scope. \n\nSYMPTOM\nWhen a RES component makes an attempt to interact with a RES Console management stack (through a JMX invocation) the following exception may occur if more than one RES Console is deployed within an administrative cell: \n\n...\njava.lang.IllegalStateException \nat ilog.rules.res.mbean.util.IlrSingleMBeanInvocationHandler.invoke(Unknown Source)\n...\n\nNote: a similar exception can be seen when no RES Console is found so the first thing to verify is that a RES Console is completely deployed and that it passes the diagnostic properly before considering the issue in this present note.\n\n\nCAUSE\nThe scope of the management API (JMX) is typically that of the Cell (WebSphere), Domain (Weblogic) or Partition(JBoss). RES components that interact directly with the RES Console management stack normally expect to find exactly one RES Console within the this management scope : an error can arise from not finding a RES Console management stack, as well as finding more than one.\n\n\nRESOLVING THE PROBLEM\nCertain use cases are supported that involve deploying more than one RES console in a cluster, most notably for situations where a active\/passive fail over is needed, see the following document for more information: Clustering Rule Execution Server (RES) management console [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21426014] \n\n\nHowever there is a number of limitations that one can face when several RES consoles are deployed within the same administrative cell, such as : \n\n 1. The use of the API ilog.rules.session.IlrManagementSession (reference [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/index.jsp?topic=\/com.ibm.websphere.ilog.jrules.doc\/html\/api\/html\/ilog\/rules\/res\/session\/IlrManagementSession.html]) may fail with a java.lang.IllegalStateException as per the symptom above. In this situation, the only option is to deploy a single RES Console per cell. \n 2. With JRules 6.x deploying RSM in a cell where more than one RES console is deployed can lead to java.lang.IllegalStateException as per the symptom above when attempting to add an SSP through the RSM console. \n 3. With JRules 7.x DVS scenario suite executions initiated from Rule Studio to be run on a remote Java EE server in a cell where more than one RES console is deployed may fail with java.lang.IllegalStateException as per the symptom above. \n 4. The use of interceptors (i.e. IlrSessionInterceptor implementations) may fail with a java.lang.IllegalStateException or an error message such as ilog.rules.res.session.interceptor.IlrSessionInterceptorException: Unable to find RuleApp \/myruleapp\/myruleset for use by the interceptor. In this situation, the only option is to deploy a single RES Console per cell.\n\n\nFor situations 2. and 3. note that DVS and RSM are normally deployed in a non-production environment since they support the testing process of the rules prior to their deployment to production. So in practice it is not necessary to deploy multiple RES console instances for fail over purpose when in a testing environment. The recommendation is then to set up RES console and SSP in a testing cell that is separate from the production cell. In this testing cell, only one instance of RES console should be installed. RELATED INFORMATION\n#Setting up multipe XUs in one cell [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21400807]\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 Enterprise"}]},{"id":"TRAIN_Q329","question":"CICS VR FRLOG option that logs changes to VSAM datasets\n\nIs the information about the NONE option for FRLOG in the CICS VSAM Recovery for z\/OS (CICS VR) documentation correct? If it is not, what information is logged when NONE is specified?\n\nI am working on a POC for the Classic change data capture (CDC) for VSAM. In order for Classic CDC to capture changes from a VSAM file, it has to be altered to have a FRLOG option.\n\nAccording to the CICS VR documentation, FRLOG has NULL, NONE, REDO, UNDO, and ALL options. By default I would think FRLOG(ALL) option will give everything in the log. However when using this option, customer cannot run their batch update job after the alter. The file cannot be opened by the batch job. We were told by Classic team to use the FRLOG=NONE option and this option actually worked. I am really confused because according to the manual NONE option will not log any changes. Here is the paragraph from the manual:","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q330","question":"How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width?\n\nHow do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator v2.0.3, to fit content by height or width? ","answer":"The same parameter-value pair mentioned above can be added in the Additional Settings section of the Daeja ViewONE panel, of the admin desktop. Add the parameter-value pair to the Additional Settings section of \n\n * the Professional tab for modifying the behaviour of the Daeja Professional viewer \n * the Virtual tab for modifying the behaviour of the Daeja Virtual viewer.\n\n\nClick New in the Additional Settings section to add the parameter-value pair. Save the changes and they should get picked up when the viewer is re-launched.","is_impossible":false,"contexts":[{"filename":"swg21674924.txt","text":"Title: IBM How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? - United States\n\nText:\nfit by height; fit by width; fit; default fit; Daeja viewer; FileNet viewer; Daeja; scale TECHNOTE (FAQ)\n\nQUESTION\n How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? \n\nANSWER\nIn Content Navigator v2.0.2 \n\nIn the ..navigator.war\/applets\/filenetViewer_properties.jsp file, set the value of the parameter 'scale' as follows \n\nTo fit content by width, specify - scale: \"ftow\",\nTo fit content by height, specify - scale: \"ftoh\",\n\nHere's another way to modify the behaviour: \n\n * make the same changes above to the filenetViewer_properties.jsp under ECMClient\\configure\\explodedformat\\navigator\\applets folder. \n * Rebuild and redeploy the ear file. \n * Restart the application server\n\n\nSave the changes and they should get picked up when the viewer is re-launched. \n\nIn Content Navigator v2.0.3 \n\nThe same parameter-value pair mentioned above can be added in the Additional Settings section of the Daeja ViewONE panel, of the admin desktop. Add the parameter-value pair to the Additional Settings section of \n\n * the Professional tab for modifying the behaviour of the Daeja Professional viewer \n * the Virtual tab for modifying the behaviour of the Daeja Virtual viewer.\n\n\nClick New in the Additional Settings section to add the parameter-value pair. Save the changes and they should get picked up when the viewer is re-launched."}]},{"id":"TRAIN_Q331","question":"mirandabarby\n\nI have purchased a grad pack of SPSS. How do I enter the authorisation code to activate\/license ","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q332","question":"Why isn't my LTPA token auto-renewing in Chrome?\n\nAfter using Maximo 7.6.0.8 from Chrome for a while (an hour?) my session became \"dead\". I could type in the \"Find Navigation Item\" box in the sidenav, but clicking on the selections went nowhere. Clicking on Sign Out didn't work, either. But there were loads of these errors in the logs for me. What's going wrong?\n\n\n\nThis dW Answers question is about an IBM document with the Title:\nSECJ0371W Warning Message Additional Information","answer":"When using single sign-on (SSO), the Security Cache will refresh from the LTPA Token. If your LTPA Token is also expired, then the user will be asked to re-login. Also, the cache timeout period is reset every time that entry is hit. So, if the entry is hit 9 minutes into the 10 minute timeout period, the clock is reset at that time. So, instead of timing out in another minute, it is now reset for another 10 minutes, then if it's hit again in that time, it will get extended again. \n\nWhen using Local operating system for authentication, the user will be asked to login when the session times out, not the security cache.","is_impossible":false,"contexts":[{"filename":"swg21078845.txt","text":"Title: IBM Security Cache, LTPA Token, and Session Time Outs - United States\n\nText:\nsession; cache; logout; login; timeout; time out; LTPA TECHNOTE (FAQ)\n\nQUESTION\n What happens when the Security Cache, LTPA Token timeout, and session time out? \n\nANSWER\nQuestion 1 \nWhat happens when the Security Cache times out? Will the user be asked to re-login?\n\nAnswer 1 \nNo. When using single sign-on (SSO), the Security Cache will refresh from the LTPA Token. If your LTPA Token is also expired, then the user will be asked to re-login. Also, the cache timeout period is reset every time that entry is hit. So, if the entry is hit 9 minutes into the 10 minute timeout period, the clock is reset at that time. So, instead of timing out in another minute, it is now reset for another 10 minutes, then if it's hit again in that time, it will get extended again. \n\nWhen using Local operating system for authentication, the user will be asked to login when the session times out, not the security cache. \n\nIn V6.1, the Federated Repository has it's own cache settings. See the link under Related Information. \n\nQuestion 2 \n\n 1. Using a browser, we accessed a secured application, we provided the UserID (UserA) and a valid PW (Password1). A token was created. So far everything is working fine. \n \n 2. You manually changed the password for UserA in the LTPA (LDAP or custom registry) from Password1 to Password2. \n 3. Using a new browser we accessed the application providing UserA and the new password (Password2) a token was created and again everything is working as expected. \n \n 4. Using a another new browser we accessed the application providing UserA and the old password (Password1). You were surprised to notice that a token was created and UserA was able to access the application. \n\n\nAnswer 2 \nThe old password takes up to 1.5 times the security cache to disappear. It will also expire at the end of the LTPA token timeout. \n\nIn IBM WebSphere Application Server V5.0.2 and later, you can purge a user from the security cache using an MBean interface. See the Related Information at the end of this article. \n\n\nQuestion 3 \nI want to force my users to re-login after a set \"inactivity timeout\" period. How is WebSphere Application Server supposed to work with regard to session timeouts and LTPA timeout. Answer 3 \nSee the answer to this question in item 9 of the following developerWorks article:\nhttp:\/\/www.ibm.com\/developerworks\/websphere\/techjournal\/1003_botzum\/1003_botzum.html [http:\/\/www.ibm.com\/developerworks\/websphere\/techjournal\/1003_botzum\/1003_botzum.html]\n\n\nQuestion 4 \nIf this is the case, can we expire or delete the LTPAToken cookie when the session expires? If so, what mechanism should we use? \n\nAnswer 4\nYou can manually perform a form-based logout (as described in the Information Center) to request that the LTPAToken cookie be destroyed in the web browser, but within WebSphere Application Server, there is no functionality to automatically perform the form-based logout when the session times out. This would have to be performed programmatically.\n\nRELATED INFORMATION\n Federated Repository cache settings [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSAW57_8.5.5\/com.ibm.websphere.nd.doc\/ae\/uwim_ldapperfsettings.html]\nAuthentication cache settings [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSAW57_8.5.5\/com.ibm.websphere.nd.doc\/ae\/usec_sec_domains_cache.html]"}]},{"id":"TRAIN_Q333","question":"javax.xml.bind.UnmarshalException org.xml.sax.SAXParseException: The reference to entity must end with the ; delimiter.\n\n\n\nAfter an upgrade from JRules to ODM we are receiving errors because of an ampersand in our data. This used to work before.\n\nCaused by: javax.xml.bind.UnmarshalException\n- with linked exception: [org.xml.sax.SAXParseException: The reference to entity \"NIGHT\" must end with the ; delimiter.","answer":"The value of the parameter is the XML data corresponding to your input parameter XSD, either passed in a CDATA section or by escaping the XML special characters (replacing <, >, \", ' and & with <, >, ", ' and &).","is_impossible":false,"contexts":[{"filename":"swg21498780.txt","text":"Title: IBM Format of XML-type ruleset parameters in SOAP messages with MTDS - United States\n\nText:\nXSD; schema; SOAP; web service TECHNOTE (FAQ)\n\nQUESTION\n How to format the value of an XML-type ruleset parameter in the SOAP request to a Monitored Transparent Decision Service (MTDS) ? \n\nCAUSE\nAs mentioned in the documentation for MTDS, XML parameters are represented by a String in the WSDL file.\n\nANSWER\nThe value of the parameter is the XML data corresponding to your input parameter XSD, either passed in a CDATA section or by escaping the XML special characters (replacing <, >, \", ' and & with <, >, ", ' and &). \n\nFor more information on transparent decision services, refer to section \"Rule Execution Server > Introducing Rule Execution Server > Rule Execution Server basics > Transparent decision services and rule execution\" of the JRules V7.1 documentation [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/index.jsp?topic=\/com.ibm.websphere.ilog.jrules.doc\/Content\/Business_Rules\/Documentation\/_pubskel\/JRules\/ps_JRules_Global926.html].\n\nRELATED INFORMATION\n JRules V7.0 doc on transparent decision services [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r0m3\/topic\/com.ibm.websphere.ilog.jrules.doc\/Content\/Business_Rules\/Documentation\/_pubskel\/JRules\/ps_JRules_Global801.html]\nWODM V7.5 doc on transparent decision services [http:\/\/publib.boulder.ibm.com\/infocenter\/dmanager\/v7r5\/topic\/com.ibm.dserver.res\/Content\/Business_Rules\/_pubskel\/Infocenter_Primary\/ps_DS_Rule_Execution_Server1460.html]\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, 7.5"}]},{"id":"TRAIN_Q334","question":"Datetime export to FileNet\n\n Hi there\n\n \n\nI created an application in Datacap that export to FileNet a Datetime field. In FEM I have a property type of Datetime. I'm using the following to send value to FileNet:\n\nFNP8_SetProperty (\"DataEmissao,@DATE(dd\/MM\/yyyy)+@STRING( )+@TIME(HH:MM),Datetime\")\n\n \n\nThe export works fine, but if I check the Datetime property in FEM I can see that the TIME was stored wrong, exactly 3 hours less.\n\ne.g:\n\nCurrent Datetime is: 19\/08\/2013 18:10\n\nValue stored in FEM: 19\/08\/2013 15:10\n\n \n\nCan someone help me? What I'm doing wrong?\n\n \n\nThank's ","answer":"Modify the date\/time value into proper GMT\/UTC format of YYYY-MM-DDTHH:MM[:SS] and then add a time offset to account for the GMT time difference, e.g. YYYY-MM-DDTHH:MM:SS-HH:MM, prior to export to FileNet P8. \n\n\nThe action IsFieldDateWithReformat from the Validations library can be called with a parameter of \"s\" (no quotation marks) to format a local date\/time value to UTC; a GMT offset can be appended to a UTC value with any standard action such as rrSet from the rrunner library.","is_impossible":false,"contexts":[{"filename":"swg21572905.txt","text":"Title: IBM Exported dates to IBM FileNet Content Engine are one day off in IBM Datacap Taskmaster Capture - United States\n\nText:\nFileNet P8; FNP8; Export; yesterday; GMT; UTC TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Dates exported to IBM FileNet P8 Content Engine show yesterday's date when viewed by an IBM FileNet Content Engine client \n\nCAUSE\nIBM FileNet Content Engine stores all time stamps using UTC format. If a date is passed into IBM FileNet Content Engine with no time component then the time defaults to midnight UTC, which may indicate the prior date when converted back into local time.\nTaskmaster does not convert or handle dates in GMT\/UTC and thus any date values must be formatted by the application rules prior to export to IBM FileNet Content Engine\n\n\nRESOLVING THE PROBLEM\nModify the date\/time value into proper GMT\/UTC format of YYYY-MM-DDTHH:MM[:SS] and then add a time offset to account for the GMT time difference, e.g. YYYY-MM-DDTHH:MM:SS-HH:MM, prior to export to FileNet P8. \n\n\nThe action IsFieldDateWithReformat from the Validations library can be called with a parameter of \"s\" (no quotation marks) to format a local date\/time value to UTC; a GMT offset can be appended to a UTC value with any standard action such as rrSet from the rrunner library.\n\nExample 1: \n\nDescription Field Value (Case A) Field Value (Case B) Data captured 05\/31\/2012 15:00 05\/31\/2012 IsFieldDateWithReformat(s) 2012-05-31T15:00:00 2012-05-31T00:00:00 rrSet(@F+-07:00,@F) 2012-05-31T15:00:00-07:00 2012-03-15T00:00:00-07:00 Here the initial field value is first transformed to UTC. The rrSet action is called to append the GMT offset \"-07:00\" to the field value. \n\nExample 2: Description Field Value (Case A) Field Value (Case B) Data captured 05\/31\/2012 15:00 05\/31\/2012 IsFieldDateWithReformat(s) 2012-05-31T15:00:00 2012-05-31T00:00:00 rrSet(@F+@CHR(43)+07:00,@F) 2012-05-31T15:00:00+07:00 2012-03-15T00:00:00+07:00 Here the initial field value is first transformed to UTC. The rrSet action is called to append the GMT offset \"+07:00\" to the field value, @CHR is used to avoid conflict with the concatenation operator. \n\nNote: IBM FileNet Content Engine may have a back end setting for Daylight Savings Time (DST), thus modifying the GMT offset to account for DST may not be necessary. \n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet P8 Platform Content Engine Windows, AIX, HP-UX, Linux, Solaris 5.2, 5.1, 5.0, 4.5, 4.2, 4.1"}]},{"id":"TRAIN_Q335","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux (CVE-2018-6405)\n\n\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-2018-6405\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q336","question":"Why does silent install abort indicating files are locked?\n\nSilent installs can fail reporting that there are locked files under the ITM installation directory on Windows platform. Why does this happen?\n\nExample:\n\nC:\\IBM\\ITM\\InstallITM\\\nAbort IBM Tivoli Monitoring 20160203 1832.log\n\n02-03-2016 18:37:10: File C:\\IBM\\ITM\\TMAITM6\\deploy.jar is locked.\n02-03-2016 18:37:10: File C:\\IBM\\ITM\\TMAITM6\\deploy.jar could not be renamed, errors may occur.\n02-03-2016 18:37:17: Directory C:\\IBM\\ITM has locked files.\n02-03-2016 18:37:17: Correct and launch setup again.\n02-03-2016 18:37:17: Directory C:\\IBM\\ITM has locked files, unable to continue.\n02-03-2016 18:37:17: SEVERE: ERROR - Install aborted. ","answer":"A limitation for remote deployment and silent installations indicates:\nA silent installation terminates if product files are locked. This behavior ensures that the installer does not overwrite product files that are currently running. The best practice is to shut down all components, including monitoring servers, portal server, and portal clients before you perform any product upgrade. This limitation only affects silent installations. Installations through the installation wizard is not affected.","is_impossible":false,"contexts":[{"filename":"swg21882989.txt","text":"Title: IBM Locked files encountered during Windows agent silent installation - United States\n\nText:\nlocked files; silent; remote; installation; Windows TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A silent installation of the Windows NT agent aborts due to locked files. \n\nSYMPTOM\nThe Customer's AbortIBMTivoliMonitoring yyyymmdd hhmm.log (for example AbortIBMTivoliMonitoring20150409 1014.log) shows the following messages & errors. \n\n4-9-2015 10:15:22 CheckLockedFiles - Search directory C:\\IBM\\ITM for locked files.\n4-9-2015 10:15:22 CheckLockedFiles - File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\ISSetup.dll is locked.\n4-9-2015 10:15:22 File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\ISSetup.dll could not be renamed, errors may occur.\n4-9-2015 10:15:22 CheckLockedFiles - File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\setup.exe is locked.\n4-9-2015 10:15:22 File C:\\IBM\\ITM\\InstSpbs\\WINDOWS\\setup.exe could not be renamed, errors may occur.\n4-9-2015 10:15:22 CheckLockedFiles - Directory C:\\IBM\\ITM has locked files.\n4-9-2015 10:15:22 CheckedLockedFiles - silent install processing\n4-9-2015 10:15:22 CheckedLockedFiles - Check[C:\\IBM\\ITM\\InstSpbs\\silent_winos622_64bit_prod.txt] for Locked Files=continue\n4-9-2015 10:15:22 CheckLockedFiles - Locked files not present.\n4-9-2015 10:15:22 CheckLockedFiles - Directory C:\\IBM\\ITM - return TRUE\n4-9-2015 10:15:22 Directory C:\\IBM\\ITM has locked files.\n4-9-2015 10:15:22 Correct and launch setup again.\n4-9-2015 10:15:22 Directory C:\\IBM\\ITM has locked files, unable to continue.\n4-9-2015 10:15:22 SEVERE: ERROR - Install aborted.\n\n\nCAUSE\nA limitation for remote deployment and silent installations indicates:\nA silent installation terminates if product files are locked. This behavior ensures that the installer does not overwrite product files that are currently running. The best practice is to shut down all components, including monitoring servers, portal server, and portal clients before you perform any product upgrade. This limitation only affects silent installations. Installations through the installation wizard is not affected.\n\n\nENVIRONMENT\nAny Windows version \n\nAny ITM component installed silently\n\n\nDIAGNOSING THE PROBLEM\nLook in <ITMHOME>\\InstallITM for a file name with syntax similar to: \nAbortIBMTivoliMonitoring<DATE TIME>.log\n\nFor example:\nAbortIBMTivoliMonitoring20150409 1014.log\n\n\n\nRESOLVING THE PROBLEM\nWorkaround: Use the following method to resolve the problem:\n1. Search the installation log for instances of the CheckLockedFiles string. Locked files are listed at these places. Locked files are files that might need to be upgraded during an installation, and because they are in use (locked) the silent install terminates.\n\n\n2. Identify the process that is locking the files.\n\n\n3. Stop the process.\n\n\n4. Prevent file locking by modifying the response file for installation file. This step is required when a silent installation has terminated. \n\na. Open the response file in a text editor. In many cases, the file in which you make this modification is named silent.txt. On Windows, the file to modify is the NT_Silent_Install.txt file that is located on the monitoring server.\nb. Add the following line to the [INSTALLATION SECTION] area of your silent install response file:\nLocked Files=continue\nIf you apply any other value or assign no value for this parameter, silent installations fail when locked files exist.\nc. If Locked Files=continue is used in a silent install or remote deploy, the computer MUST be rebooted before ITM is brought up or another install is run. This is mandatory or the <ITMHOME> directory could become corrupt. If the <ITMHOME> directory becomes corrupt, all of ITM will have to be uninstalled and reinstalled.\n\n\n5. Run the silent installation again."}]},{"id":"TRAIN_Q337","question":"Why does the other instance of my multi-instance qmgr seem to hang after a failover?\n\nQueue manager will not start after failover.","answer":"Rename the file amqalchk.fil, which is found under mq\\qmgrs\\qmgrname\\ on the shared drive (to something like amqalchk.fil_OLD); then restart the queue manager.","is_impossible":false,"contexts":[{"filename":"swg21192546.txt","text":"Title: IBM Failover to secondary node under MSCS and the queue manager will not start - United States\n\nText:\nHL083112 mqlpgrlg ZX000001 ExecCtrlrMain lpiRC_LOG_NOT_AVAILABLE mscs TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You attempt to failover from the primary to secondary node under MSCS. Your WebSphere MQ queue manager fails to come up on the secondary node, and errors are generated. \n\nSYMPTOM\nThe sequence seen in the FDC files show:\n\n\nProbe Id :- HL083112 \nComponent :- mqlpgrlg \nProcess Name :- D:\\Programs\\MQSeries\\bin\\amqzxma0.exe \nMajor Errorcode :- hrcE_MQLO_UNEXPECTED_OS_ERROR \nMQM Function Stack\nkpiStartup\napiStartup\nalmPerformReDoPass\nhlgScanLogBegin\nmqlpgrlg\nxcsFFST\n\n\nProbe Id :- ZX000001\nComponent :- ExecCtrlrMain \nProcess Name :- D:\\Programs\\MQSeries\\bin\\amqzxma0.exe \nMajor Errorcode :- xecF_E_UNEXPECTED_RC \nMinor Errorcode :- lpiRC_LOG_NOT_AVAILABLE \nProbe Description :- AMQ6118: An internal WebSphere MQ error has occurred \n(7017) \nArith1 :- 28695 7017 \nMQM Function Stack\nxcsFFST\n\n\nCAUSE\nThis is caused by a logger failure at restart due to missing or damaged logs.\n\n\nRESOLVING THE PROBLEM\nRename the file amqalchk.fil, which is found under mq\\qmgrs\\qmgrname\\ on the shared drive (to something like amqalchk.fil_OLD); then restart the queue manager.\n\n\n\nPRODUCT ALIAS\/SYNONYM\n WMQ \/ MQ"}]},{"id":"TRAIN_Q338","question":"VScan not working after migrating Datacap Application from 8.1 to 9.0.1\n\nI have recently migrated one datacap application developed in Datacap 8.1 to Datacap 9.0.1. I followed the complete instruction provided in the link \n\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSZRWV_9.0.1\/com.ibm.dc.develop.doc\/dcadv001.htm\n\n \n\nAfter migration, when I tried to execute the application using Datacap Desktop. I got errors that \"This batch has no data to process. Aborting\" and \"Unable to run queue\". I am attaching the screenshots of error. I am also attaching the DStudio rule's screenshot.\n\nI have verified and configured all the required settings.\n\nPlease guide if someone has faced the similar issue and resolved it.\n","answer":"The \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity).","is_impossible":false,"contexts":[{"filename":"swg21967312.txt","text":"Title: IBM Error when launching Scan task from Datacap Desktop. - United States\n\nText:\nDesktop; No data; Scan; VScan TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving the following error message when attempting to launch up Scan task from Datacap Desktop:\n\"This batch has no data to process. Aborting.\" \n\nThen followed by this error: \n\"Unable to run queue.\" \n\nDIAGNOSING THE PROBLEM\nThe panel for TravelDocs contained a value with all upper-case letter [eg. TRAVELDOCS], which caused the error to occur when attempting to launch the Scan task from Datacap Desktop\n\nRESOLVING THE PROBLEM\nThe \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity). \n\nLogon to TMWeb client. \n\nGo to Administrator tab \n\nSelect the VScan task from the Workflow. \n\nClick Setup under Program. \n\nThen change the value of the Panel to match what is in Datacap Studio. For example \"TRAVELDOCS\" to \"TravelDocs\" \n\nClick Save\n\n[\/support\/docview.wss?uid=swg21967312&aid=1] [\/support\/docview.wss?uid=swg21967312&aid=1]\n\n[\/support\/docview.wss?uid=swg21967312&aid=2] [\/support\/docview.wss?uid=swg21967312&aid=2]\n[\/support\/docview.wss?uid=swg21967312&aid=3] [\/support\/docview.wss?uid=swg21967312&aid=3]"}]},{"id":"TRAIN_Q339","question":"Why I get pop-up message of \"undefined\" when accessing TCR 3.1.2.1 in IE 11?\n\nWhen I access Tivoli Common Reporting -> Launch -> Administration, will get repeated message window with content of \"underfined\". This happened only with IE11 and TCR 3.1.2.1 ","answer":"To resolve this issue, access the following Tivoli Common Reporting dispatcher link: \n\nhttps:\/\/JazzSM_hostname:port\/tarf\/servlet\/dispatch","is_impossible":false,"contexts":[{"filename":"swg21974757.txt","text":"Title: IBM Cognos Report Studio in Tivoli Common Reporting Version 3.1 and later fix packs fail to launch on Internet Explorer Version 11 - United States\n\nText:\njazzsm11relnotes; jazzsm1101relnotes; jazzsm1102relnotes; jazzsm1103relnotes; jazzsm1110relnotes; jazzsm1120relnotes; jazzsm1121relnotes; jazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM\u00ae Cognos\u00ae Report Studio in Tivoli\u00ae Common Reporting Version 3.1 and later fix packs fail to launch on Internet Explorer Version 11 \n\nCAUSE\nIBM Jazz for Service Management includes the Dashboard Application Services Hub service and the Tivoli Common Reporting service.\nDashboard Application Services Hub supports Internet Explorer v11 in full mode because bundled libraries like Dojo only support Internet Explorer v11 in full mode.\nWhereas, the bundled version of Cognos Business Intelligence v10.2.2 within Tivoli Common Reporting supports Internet Explorer v11 in compatibility mode.\nWhen launching Tivoli Common Reporting from Dashboard Application Services Hub, because of browser mode compatibility issues, Cognos Report Studio functionalities do not work as expected.\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, access the following Tivoli Common Reporting dispatcher link: \n\nhttps:\/\/JazzSM_hostname:port\/tarf\/servlet\/dispatch \n\n\nFor example: \nhttps:\/\/JazzSM_hostname:16311\/tarf\/servlet\/dispatch"}]},{"id":"TRAIN_Q340","question":"Why is an error seen while running run-svrssl-config?\n\n\n\nFollowing error is seen while running run-svrssl-config ConfigEngine task:\n\n action-run-pdjrte-config-zos-wp.ac.impl: \n [validateHost] Validating hostname(s) in the following argument: tam001:7136:1,tam002:7136:2\n [echo] Command to run is: java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ****** -appsvr_id myAppSvr -port 7223 -mode remote -policysvr\n tam001:7135:1,tam002:7135:2 -authzsvr tam001:7136:1,tam002:7136:2 -cfg_file \/opt\/WebSphere\/AppServer\/tivoli\/tam\/PdPerm.properties -key_file \/opt\/WebSphere\/AppServer\/tivoli\/tam\/pdperm.ks\n [java] Executing java with empty input string\n [java] Exception in thread \"main\"\n [java] [\n [java] HPDMG0759W The user name already exists in the registry.\n [java] ]\n [java] at com.tivoli.pd.jutil.ob.a(ob.java:40)\n [java] at com.tivoli.pd.jutil.ob.a(ob.java:66)\n","answer":"To avoid the error, do one of the following steps before executing the run-svrssl-config task:\n\na) Use a unique value for wp.ac.impl.PDServerName\n\nor\n\nb) Run the following command manually from a command prompt on the portal server to remove the appsvr_id value from Tivoli Access Manager's repository: \n\njava com.tivoli.pd.jcfg.SvrSslCfg -action unconfig-admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre\/PdPerm.properties -key_file","is_impossible":false,"contexts":[{"filename":"swg21319595.txt","text":"Title: IBM HPDMG0759W error when creating the AMJRTE properties file - United States\n\nText:\nTAM; run-svrssl-config; svrssl; HPDMG0759W; AMJRTE TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhen executing the \"run-svrssl-config\" task via the ConfigEngine to create the AMJRTE properties file, you receive the following error:\n\nCommand to run is: java com.tivoli.pd.jcfg.SvrSslCfg -action config -admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre\/PdPerm.properties -key_file C:\\IBM\\WebSphere\\AppServer\\java\\jre\/lib\/security\/pdperm.ks\n[java] Exception in thread \"main\" \n[java] [\n[java] HPDMG0759W The user name already exists in the registry.\n[java] ]\n[java] at com.tivoli.pd.jutil.bo.a(bo.java:98)\n\n\nENVIRONMENT\nConfiguring WebSphere\u00ae Portal 6.1 with Tivoli\u00ae Access Manager 6.0\n\nDIAGNOSING THE PROBLEM\n \n\nThe user name referenced in the error message refers to the appsvr id used in the SvrSslCfg command. The value for this user name is set via the following parameter in wkplc_comp.properties:\n\nwp.ac.impl.PDServerName\n\n\nRESOLVING THE PROBLEM\n \n\nTo avoid the error, do one of the following steps before executing the run-svrssl-config task:\n\na) Use a unique value for wp.ac.impl.PDServerName\n\nor\n\nb) Run the following command manually from a command prompt on the portal server to remove the appsvr_id value from Tivoli Access Manager's repository: \n\njava com.tivoli.pd.jcfg.SvrSslCfg -action unconfig-admin_id sec_master -admin_pwd ****** -appsvr_id myserverid -port 7223 -mode remote -policysvr <hostname>:7135:1 -authzsvr <hostname>:7136:1 -cfg_file C:\\IBM\\WebSphere\\AppServer\\java\\jre\/PdPerm.properties -key_file\n\n\nRELATED INFORMATION\n#Creating the AMJRTE properties file [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/index.jsp?topic=\/com.ibm.wp.ent.doc\/security\/cfg_tam_auth.html]\n\n\n\n\n * \n *"}]},{"id":"TRAIN_Q341","question":"How to check IBM Java ORB build version in WebSphere Application Server?\n\nJust a simple question: How to check IBM Java ORB build version in WebSphere Application Server? ","answer":"<washome>\/java\/bin\/java -Xbootclasspath\/p:<washome>\/java\/jre\/lib\/ext\/ibmorb.jar com.ibm.rmi.util.Version","is_impossible":false,"contexts":[{"filename":"swg21157005.txt","text":"Title: IBM MustGather: Object Request Broker (ORB) problems with WebSphere Application Server - United States\n\nText:\nMustGather; MustGather; MustGather; ORB; Object Request Broker; ISA; collector; autopd; auto pd; MustGatherDocument TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Collecting data for problems with the IBM WebSphere Application Server Object Request Broker 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\nTAB NAVIGATION\n * Learning more [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21245077]\n * Troubleshooting [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21237101]\n * Collecting data- selected tab,\n\nCollecting data for problems with the IBM WebSphere Application Server Object Request Broker component. Gathering this MustGather information before calling IBM support will help you understand the problem and save time analyzing the data..\n\nCOLLECTING DATA MANUALLY\n\nObject Request Broker specific MustGather information 1. Where does the problem occur? Between what components?\n \n \n 2. What is your topology?\n \n \n 3. What are the symptoms noticed?\n \n \n 4. How do you recover from this problem?\n \n \n 5. What are the hostnames of the Client and the Application Servers?\n \n \n 6. How often does this problem occur?\n \n \n 7. Is there a firewall installed between the failing components?\n \n \n 8. Can you successfully ping the server from the remote client? Can you ping the client from the remote server?\n \n \n 9. Has this problem always occurred or has it just started to occur? If it just started, what changes were made?\n \n \n 10. Clear out the logs in the install_root\/logs directory, then recreate the problem.\n \n \n 11. Collect the following files: * The newly created logs.\n \n \n * Answers to the preceding questions.\n \n \n * For releases of WebSphere Application Server versions 5.0 and 6.0 * collector.[sh\/bat] output\n \n \n \n \n * Any additional information you think might relate (topology, symptoms, and so on) to IBM.\n \n Note: Additional ORB, Security, or WLM traces might be required.\n \n \n\n \n\nAdditional MustGather information for ORB interoperability problems \n\n 1. What third-party ORB are you trying to use?\n \n \n 2. What version is the third-party ORB using?\n \n \n 3. What language is the third-party ORB using? (C++ or Java)\n \n \n 4. What platform is the third-party ORB running on?\n \n \n 5. What platform is WebSphere Application Server running on?\n \n \n 6. Does the problem or error occur consistently or randomly?\n \n \n 7. Is the problem reproducible? If so, what are the steps?\n \n \n 8. Is WebSphere Application Server being used as the server or client to the third-party ORB?\n \n \n 9. Has this worked before, or is this a new configuration?\n \n \n 10. Have you tried using the approach recommended in the CORBA Interop samples?\n \n \n 11. Where was the Interface Definition Language (IDL) compiled (what tool was used)?\n \n Note: See the WebSphere Application Server detailed system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006921] for the information related to the third party ORB Supported\/Tested, then select WebSphere Version > Server Type > Search on third-party ORB in Software Requirements List.\n\n \n\nA collector output is required for the WebSphere Application Server support team to troubleshoot an ORB issue. By providing the collector output, your configuration can be reviewed to help get a better understanding of your topology and settings. \n\n\n * Detailed instructions on how to run the collector program can be found at the following link:\n\n\nhttps:\/\/www.ibm.com\/support\/knowledgecenter\/SSEQTP_8.5.5\/com.ibm.websphere.nd.doc\/ae\/ttrb_runct.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEQTP_8.5.5\/com.ibm.websphere.nd.doc\/ae\/ttrb_runct.html] \n\nMake sure you do not run the collector program from within the WebSphere Application Server product installation root directory. This will lead to an error. Make a working directory where you can start the collector program. \n\nOnce you have run the collector program from the dmgr, upload the collector.jar file that is created. \n\nIf specific ORB traces have been requested by the Application Server support team, use the following instructions:\n\nNOTE: In most cases, support is going to need a matching client and server side trace to troubleshoot the issue. In some cases, they may even need traces from the nodeagent.\n\n\n\n * WebSphere Application Server V6.1, V7.0, V8.0, and V8.5 ORB trace instructions \n You can review the following video that walks you through setting up the ORB trace in the Administrative Console. It goes through each step listed below to make sure the ORB trace is enabled correctly. \n \n \n 1. From the Administrative Console, select Servers > Application Servers > server_name > Change Log Details Levels.\n \n \n 2. Remove any previous entries in the text field type the following:\n \n *=info:ORBRas=all\n \n \n 3. Apply and save changes.\n \n \n 4. Select Servers > Application Servers > server_name > Diagnostic Trace Service.\n \n \n 5. Change the Maximum Number of Historical Files to 10 and maximum file size to 50mb\n \n \n 6. Apply and save changes.\n \n \n 7. Enabling Comm Trace:\n \n Application Server\n From the Administrative Console, Select Servers > Application Servers > server_name > Container Services > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.\n \n Node Agent\n From the Administrative Console, select System Administration >Node Agent > nodeagent > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.\n \n Deployment Manager\n From the Administrative Console, Select System Administration > Deployment Manager > ORB Service. Select the Orb Tracing check box to enable Comm Tracing.\n \n NOTE: You will need to do a server restart for the Comm Tracing to be captured in the trace.log file. You can also leave the Orb Tracing check box checked permanently in case you run into another ORB issue in the future. That way, you don't have to do another server restart for the trace to be captured. Leaving the Orb Tracing check box checked won't log any data to a trace log unless you have the ORBRas=all trace string enabled (Step 2 above). This means it won't cause any performance issues or affect anything else in the server. \n 8. Apply and save changes.\n \n \n 9. Restart the sever and recreate the problem\n \n \n 10. Collect the following data:\n \n profile_root\/logs\/server_name\/trace.log\n \n * \n * profile_root\n * \/logs\/ffdc folder\n \n * \n \n * NOTE: \n * \n * date\n * \n * time\n * \n * \n \n \n * Stand Alone Java Client ORB Trace Instructions 1. Start the client program with the \"-D\" arguments to specify the trace settings\n \n -Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true -Dcom.ibm.CORBA.Debug.Output=client.log\n \n \n 2. The ORB trace output is captured in the path pointed by com.ibm.CORBA.Debug.Output.\n \n If the com.ibm.CORBA.Debug.Output parameter is not specified, the ORB trace output is captured in a unique trace file named orbtrc.<timestamp>.txt in the current directory of execution.\n \n \n 3. Collect the following file:\n \n orbtrc.<timestamp>.txt \n \n \n \n \n \n * J2EE Client Trace Instructions 1. Start the launchClient script with the following arguments to enable the trace:\n \n install_root\/bin\/launchClient.sh <ear_file> -JVMOptions=\"-Dcom.ibm.CORBA.Debug=true -Dcom.ibm.CORBA.CommTrace=true\" -CCtrace=ORBRas=all -CCtracefile=orbtrace.txt -CCtraceMode=basic\n \n \n Note: For Windows installations, use launchClient.bat instead of launchClient.sh\n \n 2. The ORB trace output is captured in a unique trace file named orbtrace.txt in the current directory of execution.\n \n \n 3. Collect the following file:\n \n orbtrace.txt\n \n \n \n * How to check IBM\u00ae Java\u2122 ORB build version in WebSphere\u00ae Application Server.\n\n * <washome>\/java\/bin\/java -Xbootclasspath\/p:<washome>\/java\/jre\/lib\/ext\/ibmorb.jar com.ibm.rmi.util.Version\n \n * Follow instructions to send diagnostic information to IBM support [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21153852] [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg21153852]\n \n\n\n\nFor a listing of all technotes, downloads, and educational materials specific to the ORB component, search the WebSphere Application Server support site [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server]. \n\nRelated information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21153852] \nSubmitting information to IBM support [http:\/\/www.ibm.com\/support\/docview.wss?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?uid=swg21145599] \nTroubleshooting guide for WebSphere Application Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27005324] \n\n\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 * 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] Security Problem [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21470063] JNDI Problem [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21143296] JTS Problem [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21153216] Session Management Problem [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21192604] 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 Runtimes for Java Technology Java SDK AIX, HP-UX, Linux, Solaris, Windows 8.0, 7.1, 7.0, 6.1, 6.0.2, 6.0 Application Servers WebSphere Application Server Object Request Broker (ORB) AIX, HP-UX, Linux, Solaris, Windows 9.0, 8.5.5, 8.5, 8.0, 7.0, 6.1 Base, Network Deployment"}]},{"id":"TRAIN_Q342","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\n \n\n- com.ibm.ws.cluster.selection.NoAvailableTargetExceptionImpl\n \n\n- WaitForWLMDat 3 (com.ibm.ws.sib.trm.wlm.client.WaitForWLMData) [:] Sleeping for 2999 ms \"\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":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q343","question":"Help with Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2017-1681)\n\nI need to understand details regarding Security Bulletin: A security vulnerability has been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2017-1681). Is WAS Liberty affected?","answer":"This vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Liberty","is_impossible":false,"contexts":[{"filename":"swg22010419.txt","text":"Title: IBM Security Bulletin: Information disclosure in WebSphere Application Server (CVE-2017-1681) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential information disclosure vulnerability in WebSphere Application Server. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1681 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1681]\nDESCRIPTION: IBM WebSphere Application Server (IBM Liberty for Java for Bluemix 3.15) could allow a local attacker to obtain sensitive information, caused by improper handling of application requests, which could allow unauthorized access to read a file. IBM X-Force ID: 134003.\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134003 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134003] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:L\/PR:N\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Liberty \n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION\/FIXES\nThe recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI88642 for each named product as soon as practical.\n\nFor WebSphere Application Server Liberty with fixpack levels prior to 17.0.0.3: \n\u00b7 Upgrade to minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044506] [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]\n--OR-- \n\u00b7 Apply Liberty Fix Pack 17.0.0.3 or later. \n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition: \n\nFor V9.0.0.0 through 9.0.0.6: \n\u00b7 Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI88642 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044506] [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\u00b7 Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.12: \n\u00b7 Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI88642 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044506] \n--OR-- \n\u00b7 Apply Fix Pack 8.5.5.13 or later. \n\nFor V8.0.0.0 through 8.0.0.14: \n\u00b7 Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044506] [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\u00b7 Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n\u00b7 Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI88642 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044506] [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\u00b7 Apply Fix Pack 7.0.0.45 or later. \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] \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\n08 February 2018: updated CVSS score, changed from 5.3 to 4.0 \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=swg22013132]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition Application Servers WebSphere Application Server Liberty Core"}]},{"id":"TRAIN_Q344","question":"BPEDB tablespace issues and how to address them\n\nThe size of the tables in BPEDB grows over a period of time. Thousands of process instances were created, due to an unexpected error. We went ahead and terminated the instances and deleted them from BPC Explorer. The size of the BPEDB grew from 1GIG to 11GIG. However, even after terminating the instances, the size of BPEDB did not decrease. How do we reduce the size of the BPEDB? Will the size increase if more instances are created ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q345","question":"Where can I find information on security issues addressed in WAS fix pack 8.5.5.6?\n\nI am planning to upgrade to WAS fix pack 8.5.5.6 and would like to know what security vulnerabilities, if any, are addressed in this fix pack. ","answer":"Cross reference list for security vulnerabilites fixed in IBM WebSphere Application Server 8.5.5.6, IBM WebSphere Application Server Hypervisor 8.5.5.6 and IBM WebSphere Application Server Liberty Profile 8.5.5.6.","is_impossible":false,"contexts":[{"filename":"swg21959083.txt","text":"Title: IBM Security Bulletin: Multiple Security Vulnerabilities fixed in IBM WebSphere Application Server 8.5.5.6 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Cross reference list for security vulnerabilites fixed in IBM WebSphere Application Server 8.5.5.6, IBM WebSphere Application Server Hypervisor 8.5.5.6 and IBM WebSphere Application Server Liberty Profile 8.5.5.6. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0226 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0226]\nDESCRIPTION: Apache WSS4J could allow a remote attacker to obtain sensitive information, caused by Bleichenbacher's attack on XML Encryption. By sending a specially-crafted message, an attacker could exploit this vulnerability to decrypt the key and obtain sensitive information.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100836 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100836] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:P\/I:N\/A:N) \nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: \n\nVersion 8.5 Liberty Profile \n\nRemediation\/Fixes: The recommended solution is to apply the Interim Fix, Fix Pack, or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403], Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI36866, as noted below:\n\nFor IBM WebSphere Application Server Liberty profile: \n\nFor V8.5.5.2 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI36866 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040191]\n\nWorkaround(s): None known \nMitigation(s): None known \n\nCVE ID: CVE-2015-1885 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1885] (APAR PI33202 and PI36211) \n\nDESCRIPTION: WebSphere Application Server Full Profile and Liberty Profile could allow a remote attacker to gain elevated privileges on the system when OAuth grant type of password is used. \n\nCVSS: \nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101255 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101255] for the current score\nCVSS Environmental Score*: Undefined\nCVSS String: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile and Liberty Profile Version 8.0 Version 7.0 \n\nRemediation\/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix, Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI36211 for Full Profile and PI33202 for Liberty Profile, as noted below: \n\nFor IBM WebSphere Application Server \n\nFor V8.5.0.0 through 8.5.5.5 Full Profile: Apply Interim Fix PI36211 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 6 (8.5.5.6), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)\/installableApps directory.\n\n\nFor V8.5.0.0 through 8.5.5.4 Liberty Profile: Apply Interim Fix PI33202 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039594] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039594] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403]\n-- OR Apply Fix Pack 5 (8.5.5.5), or later.\n\nFor V8.0.0.0 through 8.0.0.10: Apply Interim Fix PI36211 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 11 (8.0.0.11), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)\/installableApps directory.\n\nFor V7.0.0.0 through 7.0.0.37: Apply Interim Fix PI36211 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039602]\n-- OR Apply Fix Pack 39 (7.0.0.39), or later. After the fix pack is installed, the fix will not be active until the installed OAuth ear, WebSphereOauth20SP.ear, is updated from the (WAS_HOME)\/installableApps directory.\n\nWorkaround(s): None known \nMitigation(s): None known \n\nCVEID: CVE-2015-0250 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0250]\nDESCRIPTION: Apache Batik could allow a remote attacker to obtain sensitive information. By persuading a victim to open a specially-crafted SVG file, an attacker could exploit this vulnerability to reveal files and obtain sensitive information.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101614 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101614] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:N\/A:N) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile Version 8 Version 7 Version 6.1\n\nRemediation\/Fixes: The recommended solution is to apply the Interim Fix, Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403], Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI39768 or PI49437, as noted below:\n\nFor IBM WebSphere Application Server Full profile and IBM WebSphere Application Server Hypervisor Edition\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI39768 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040442]\n\nFor V8.0.0.0 through 8.0.0.10: Apply Fix Pack 11 (8.0.0.11), or later. [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI39768 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040442] \n\nFor V7.0.0.0 through 7.0.0.37: Apply Fix Pack 39 (7.0.0.39), or later. [https:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg21693757]\n-- OR Apply Interim Fix PI49437 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041163] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040442]\n\nFor V6.1.0.0 through 6.1.0.47: Apply Fix Pack 47 (6.1.0.47), or later and then apply Interim Fix PI49437 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041163]\n\n\nWorkaround(s): None known \nMitigation(s): None known \n\n\nCVEID: CVE-2015-1927 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1927]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to gain elevated privileges on the system, caused by an application not having the correct serveServletsbyClassname setting. By a developer not setting the correct property, an attacker could exploit this vulnerability to gain unauthorized access.\nCVSS Base Score: 6.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102872 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102872] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:P\/A:P) \n\n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile and Liberty Profile Version 8 Version 7\n\nRemediation\/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403], Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI31622, as noted below:\n\nPlease Note:This APAR has changed the default value of the WebContainer custom property com.ibm.ws.webcontainer.disallowServeServletsByClassname from false to true so that no security threat could occur. Prior to this change, it was up to the developer to remember to change the custom property to true before deploying into production. \n\n\nProperty Name: com.ibm.ws.webcontainer.disallowServeServletsByClassname \nDescription: If set to true, disallows the use of serveServletsByClassnameEnabled at the application server level, overriding any setting of serveServletsByClassnameEnabled at the application level. This property affects all applications. \nValues: true(default)\/false\n\nIf you need to change the value please refer to the the following technote for instructions on enabling WebContainer custom properties: \n\nFull Profile: http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21284395 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21284395]\nLiberty Profile: http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21597753 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21597753]\n\nFor IBM WebSphere Application Server Full profile, IBM WebSphere Application Server Liberty Profile and IBM WebSphere Application Server Hypervisor Edition\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI31622 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040348]\n\nFor V8.0.0.0 through 8.0.0.10: Apply Fix Pack 11 (8.0.0.11), or later. [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI31622 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040348] \n\nFor V7.0.0.0 through 7.0.0.37: Apply Fix Pack 39 (7.0.0.39), or later. [https:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg21693757]\n-- OR Apply Interim Fix PI31622 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040348]\n\nWorkaround(s): Set the custom property com.ibm.ws.webcontainer.disallowServeServletsByClassName to true\nMitigation(s): None known \n\nCVEID: CVE-2015-1936 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1936]\nDESCRIPTION: IBM WebSphere Application Server Administrative console could allow a remote authenticated attacker to hijack a user's session when Security is not enabled. An attacker could exploit this vulnerability using the JSESSIONID parameter to gain access to another user's session.\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/103108 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/103108] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:S\/C:P\/I:N\/A:N) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 Full Profile Version 8 \n\nRemediation\/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403], Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI37230, as noted below:\n\n\nFor IBM WebSphere Application Server and IBM WebSphere Application Server Hypervisor Edition:\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI37230 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040347]\n\nFor V8.0.0.0 through 8.0.0.11: Apply Fix Pack 12 (8.0.0.12), or later. [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21693751]\n-- OR Apply Interim Fix PI37230 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040347]\n\nWorkaround(s): None known \nMitigation(s): None known \n\nCVEID: CVE-2015-1946 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1946]\nDESCRIPTION: IBM WebSphere Application Server 8.5 and IBM WebSphere Virtual Enterprise 7.0 could allow a local attacker to gain elevated privileges on the system cause by the user roles not being handled properly.\nCVSS Base Score: 4.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/103201 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/103201] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L\/AC:M\/Au:S\/C:P\/I:P\/A:P) \n\nAFFECTED VERSIONS: The following IBM WebSphere Application Server Versions are affected: Version 8.5 IBM WebSphere Application Server Version 7.0 IBM WebSphere Virtual Enterprise on WebSphere Application Server Version 7 and Version 8\n\nRemediation\/Fixes: The recommended solution is to apply the Fix Pack or PTF for each named product as soon as practical. \n\nFix: \nApply an Interim Fix [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039403], Fix Pack or PTF [https:\/\/www-304.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980] containing this APAR PI35180, as noted below:\n\nFor IBM WebSphere Application Server\n\nFor V8.5.0.0 through 8.5.5.5: Apply Fix Pack 6 (8.5.5.6), or later. \n-- OR Apply Interim Fix PI35180 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040235]\n\nFor IBM WebSphere Virtual Enterprise using WebSphere Application Server V7.0 and V8.0: Apply WebSphere Virtual Enterprise Fix Pack 6 (7.0.0.6) or later. \n\nWorkaround(s): None known \nMitigation(s): None known \n\nOther APARs shipped with 8.5.5.6 are included in the security bulletins below:\nPI33012 Security Bulletin for Dojo Toolkit Vulnerability [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21697284]\nPI36563 Security Bulletin for RSA Export Keys for WebSphere Application Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21698613]\nPI36563 Security Bulletin for RC4 Stream Cipher for WebSphere Application Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21701503]\nPI38302 Security Bulletin for Management Port for WebSphere Application Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21883573]\nPI36417 Security Bulletin for RSA Export Keys for IBM HTTP Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21698959] \nPI34229 Security Bulletin for RC4 Stream Cipher for IBM HTTP Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21701072] \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 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 26 June 2015: original document published\n29 June 2015: fix serveservlets custom property name and add workaround\n30 June 2015: fix serveservlets custom property\n16 July 2015: added additional links to ifixes\n13 August 2015: added additonal link to ifixes\n2 September 2015: updated fix pack dates and level\n13 November 2015: updated interim fix PI39768 with PI49437 \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 Application Servers WebSphere Application Server Hypervisor Edition Application Servers WebSphere Virtual Enterprise"}]},{"id":"TRAIN_Q346","question":"Cannot open module in exclusive edit - (no such file or directory)\n\nI have a module, that I can open normally, but when I try to open it in Exclusive Edit it tells me that \"no such file or directory\" How do I solve this?","answer":"This defect is resolved in IBM Rational DOORS Version 9.4.0.1","is_impossible":false,"contexts":[{"filename":"swg21511831.txt","text":"Title: IBM DOORS module fails to open in exclusive edit mode results in error \"unable to open module ...no such file or directory\" - United States\n\nText:\nmissing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to open a module exclusive edit in IBM Rational DOORS result in the error \"DOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\". \n\nSYMPTOM\nA module with a large number of sections is used mostly in shareable edit mode. \n\nYou can open the module Read-only , or Shareable-Edit; but not in exclusive edit. \n\nSteps to reproduce: \n\n 1. Login to DOORS\n \n \n 2. Click the Project, or folder, icon that contains the module\n \n \n 3. Click the module icon in the DOORS Explorer window\n \n \n 4. Click File > Open> Exclusive Edit (Ctrl + E)\n \n\n\nExpected result: The module should open in Exclusive edit mode. \n\nActual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode. If you attempt to check the database integrity for issue the module is not flagged for any problems. \n\nThe full error message is as follows:\n\nDOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\"\nC:\\Program Files (x86)\\IBM\\Rational\\DOORS\\9.5\\data\\v6data\\20\\m00000021.mod\\current.ver\\s1000005.dtc\n\n\nimage \n\n[\/support\/docview.wss?uid=swg21511831&aid=1] [\/support\/docview.wss?uid=swg21511831&aid=1]\n\nCAUSE\n This issue has been identified as a product defect under APAR PM50525 [http:\/\/ibm.com\/support\/docview.wss?uid=swg1PM31236].\n\n\n\nRESOLVING THE PROBLEM\nThis error indicates that a user session file is corrupted on the database server. \n\nThis defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27036720#9401] \n\n \n\nWORKAROUND: \n\nthe following options can be used to correct this problem: \n\n * Retrieve the missing file from system backup and insert it into the module current.ver directory\n \n The advantage of inserting the missing session file is you do not need to restart the database server.\n\nWarning these two option should only be performed by Rational Support. Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database. Send the session.ixc file to support for repair\n\nFrom the module directory listed in the error message provide support the file session.ixc\nChoosing to have support repair the session index file requires you to have all users log out \nand shut down the DOORS database server until the repaired file is returned and inserted \nto replace the existing data file for the module.\n\nCreate a replacement session file \nFrom the module directory listed in the error message provide support the file session.ixc\nAdjacent session files will be required in order to to create the replacement. \nYour support engineer will identify these files from the session index file.\nNo work can be performed in the effected module until the replacement session file is restored\nfor the effected module. \n\n\nNote: Generally the repair is only required for one user session file. However in circumstances where DOORS reports a missing session file for a module- the event that caused this may have effected session files for other users connected to the module. For this situation you may need to perform a successive repair to the index file."}]},{"id":"TRAIN_Q347","question":"When DataPower 7.5.2.x is acting as an SFTP client, what Key Exchange and Mac Algorithms are offered in the SSH handshake?\n\nBy default which algorithms are offered by DataPower on firmware 7.5.2? ","answer":"Default KEX algorithms * curve25519-sha256@libssh.org\n * \n * ecdh-sha2-nistp256\n * \n * ecdh-sha2-nistp384\n * \n * ecdh-sha2-nistp521\n * \n * diffie-hellman-group-exchange-sha256\n * \n * diffie-hellman-group14-sha1\n \n Default MAC algorithms * umac-64-etm@openssh.com\n * \n * umac-128-etm@openssh.com\n * \n * hmac-sha2-256-etm@openssh.com\n * \n * hmac-sha2-512-etm@openssh.com\n * \n * hmac-sha1-etm@openssh.com\n * \n * umac-64@openssh.com\n * \n * umac-128@openssh.com\n * \n * hmac-sha2-256\n * \n * hmac-sha2-512\n * \n * hmac-sha1","is_impossible":false,"contexts":[{"filename":"swg21974106.txt","text":"Title: IBM Late breaking updates to DataPower 7.5 documentation - United States\n\nText:\n NEWS\n\nABSTRACT\n \n\nThe version 7.5 documentation for IBM DataPower Gateway is not the latest available information. This document covers late breaking updates that are not in IBM Knowledge Center.\n\nLast updated, October 2017.\n\n\n\nCONTENT\nThe late breaking updates in this document apply to DataPower Gateway version 7.5 documentation. \n\n\n\n\n\n\n\nTo access specific updates, click the appropriate link: * Upgrade\n * \n * Installation\n * \n * GatewayScript\n * \n * File management\n * \n * Monitors\n\nTo view the change history of this document, see Change history\n\n\nThe corrections in the following sections apply to DataPower Gateway version 7.5 in IBM Knowledge Center.\n\n\n\n\n\n\n\n\n\n\nUpgrade * \n * Disabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices. \n * \n * \n * enable-legacy-kex yes\n * \n * The enable-legacy-kex command for the SSH server profile in available in 7.5.2.0. The enable-legacy-kex command for the SSH client profile is available in 7.5.2.7. \n * \n * \n * Default cipher suites * chacha20-poly1305@openssh.com (CHACHA20-POLY1305_AT_OPENSSH.COM)\n * \n * aes128-ctr (AES128-CTR)\n * \n * aes192-ctr (AES192-CTR)\n * \n * aes256-ctr (AES256-CTR)\n * \n * aes128-gcm@openssh.com (AES128-GCM_AT_OPENSSH.COM)\n * \n * aes256-gcm@openssh.com (AES256-GCM_AT_OPENSSH.COM)\n * \n * arcfour256 (ARCFOUR256)\n * \n * arcfour128 (ARCFOUR128)\n * \n * aes128-cbc (AES128-CBC)\n * \n * 3des-cbc (3DES-CBC)\n * \n * blowfish-cbc (BLOWFISH-CBC)\n * \n * cast128-cbc (CAST128-CBC)\n * \n * aes192-cbc (AES192-CBC)\n * \n * aes256-cbc (AES256-CBC)\n * \n * arcfour (ARCFOUR)\n * \n * rijndael-cbc@lysator.liu.se (RIJNDAEL-CBC_AT_LYSATOR.LIU.SE)\n \n Default KEX algorithms * curve25519-sha256@libssh.org\n * \n * ecdh-sha2-nistp256\n * \n * ecdh-sha2-nistp384\n * \n * ecdh-sha2-nistp521\n * \n * diffie-hellman-group-exchange-sha256\n * \n * diffie-hellman-group14-sha1\n \n Default MAC algorithms * umac-64-etm@openssh.com\n * \n * umac-128-etm@openssh.com\n * \n * hmac-sha2-256-etm@openssh.com\n * \n * hmac-sha2-512-etm@openssh.com\n * \n * hmac-sha1-etm@openssh.com\n * \n * umac-64@openssh.com\n * \n * umac-128@openssh.com\n * \n * hmac-sha2-256\n * \n * hmac-sha2-512\n * \n * hmac-sha1\n \n \n * \n * \n * The SSH client always initiates the banner exchange. During the SSH2 banner exchange, use CR+LF termination for the banner. The SSH client ignores any message from the SSH server until the banner exchange. \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nInstallation * \n * show other-sensors\n * \n * show sensors-other\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nGatewayScript * \n * clear gatewayscript-cache path\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nFile management * \n * isamwebroot local policyframework \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nMonitors * \n * type\n * \n * block\n * \n * shape\n * \n * type command\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\nChange history \nLast modified: 30 October 2017. * 30 October 2017: Added information about nonexisting block keyword for Message Filter Action type command. \n * 19 October 2017: Added information about which directories you can create and remove subdirectories. \n * 19 July 2016: Added data about the wrong command troubleshooting command in the installation documentation. \n * 17 June 2016: Added data about the undocumented Global command. \n * 22 March 2016: Created for 7.5.\n\nBack to top"}]},{"id":"TRAIN_Q348","question":"Why does DSM error log have errors for SQLCODE=-206 errors reported for ISAS core warehouse database?\n\nDSM error log have errors for SQLCODE=-206 errors reported for ISAS core warehouse database. How do Isolve the problem?","answer":"Run the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_9.7.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command","is_impossible":false,"contexts":[{"filename":"swg21983739.txt","text":"Title: IBM Data Server Manager (DSM) showing SQLCODE=-206 \"<name> is not valid in the context where it is used.\" - United States\n\nText:\nSQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it\nis used.\" error \n\nSYMPTOM\nThe symptoms can vary depending on each installation. \n\nMost common scenario, DSM shows Data Pending status for the monitored database.\n\n\nCAUSE\nWhen you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.\nMeaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level. \n\n\n\nDIAGNOSING THE PROBLEM\nOne way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database: \n\ndb2 \"select versionnumber from sysibm.sysversions order by 1 desc\" \n\nIf the results is showing a lower level than the ones DSM supports, that means your environment\nis not supported, and you are getting the SQLCODE=-206 error.\n\nTo verify what are the DB2 levels supported by DSM, please refer to the links below:\n- System requirements for IBM Data Server Manager, version 1.1.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27045176]\n- System requirements for IBM Data Server Manager, version 2.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27048115]\n\n\n\nRESOLVING THE PROBLEM\nRun the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_9.7.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command"}]},{"id":"TRAIN_Q349","question":"Help with Security Bulletin: Persistent cross-site scripting vulnerability in Process Admin Console affecting IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) CVE-2015-0156\n\nI need to understand details regarding Security Bulletin: Persistent cross-site scripting vulnerability in Process Admin Console affecting IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) CVE-2015-0156). Where can I find this information? ","answer":"CVEID:CVE-2015-0156 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0156]\n\nDESCRIPTION:IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100792 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100792]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:N\/I:P\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21697120.txt","text":"Title: IBM Security Bulletin: Persistent cross-site scripting vulnerability in Process Admin Console affecting IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) CVE-2015-0156 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2015-0156 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0156]\n\nDESCRIPTION:IBM Business Process Manager is vulnerable to stored cross-site scripting, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100792 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100792]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:N\/I:P\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\n * IBM Business Process Manager Standard V7.5.x, 8.0.x, 8.5.x \n * IBM Business Process Manager Express V7.5.x, 8.0.x, 8.5.x \n * IBM Business Process Manager Advanced V7.5.x, 8.0.x, 8.5.x \n * WebSphere Lombardi Edition 7.2.x\n\n\nIf you are using an earlier unsupported version, IBM strongly recommends to upgrade. REMEDIATION\/FIXES\nInstall the interim fix for APAR JR52420 as appropriate for your current IBM Business Process Manager or IT06812 for your current WebSphere Lombardi Edition environment. \n\n * IBM Business Process Manager Express [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR52420] \n * IBM Business Process Manager Standard [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR52420] \n * IBM Business Process Manager Advanced [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR52420] \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=IT06812]\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 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 2015-05-13 - 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 Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.6, 8.5.5, 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 Express Security Linux, Linux zSeries, Windows 8.5.6, 8.5.5, 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 AIX, HP-UX, Linux, Linux zSeries, Linux\/x86, Platform Independent, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2"}]},{"id":"TRAIN_Q350","question":"Missing option to fill in attributes when trying to deploy a pattern\n\nI tried to deploy a pattern and I have some parameters to modify at deployment time. But I can't see my parts\/attributes in the Component Attribute List. ","answer":"To show missing component attributes for configuration, lock any one of the attributes, such as the name attribute. This action causes the other component attributes to be displayed for configuration.","is_impossible":false,"contexts":[{"filename":"swg27044407.txt","text":"Title: IBM PureApplication System Release Note: Some component attributes are not available to configure during pattern deployment - United States\n\nText:\nv2001rlsnotes RELEASE NOTES\n\nABSTRACT\n Some component attributes are not available to configure during pattern deployment \n\nCONTENT\nProblem: If your virtual system pattern includes a component (such as an image, software component or script package) that has a data dependency on another component, but does not have any locked attributes, then the attributes for the component with the data dependency are not presented for configuration during pattern deployment.\n\nResolution: To show missing component attributes for configuration, lock any one of the attributes, such as the name attribute. This action causes the other component attributes to be displayed for configuration."}]},{"id":"TRAIN_Q351","question":"How to set session time out period for a single user in DASH?\n\nHow to set session time out period for a single user in DASH?","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","is_impossible":false,"contexts":[{"filename":"swg21163875.txt","text":"Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\u00ae WebSphere\u00ae 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 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-config> \n * \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-timeout>60<\/session-timeout>\n * \n * \u00a0 \u00a0 \u00a0 <\/session-config>\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"}]},{"id":"TRAIN_Q352","question":"How to Create an Application with the the Websphere Adapter for Flat File using Hex05 delimeter?\n\nHow to Create an Application with the the Websphere Adapter for Flat File using Hex05 delimeter? ","answer":"The only complete solution at this time is to not process unicode characters that are not valid in XML. This can be done by not importing data fields that might contain such characters or by purging such characters from the incoming data source.","is_impossible":false,"contexts":[{"filename":"swg21425772.txt","text":"Title: IBM \"An invalid XML character\" error is thrown when handling data originating from a WebSphere Adapter - United States\n\nText:\nUnicode invalid character 0x0 xml serialize serialization XSLT XLS error TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n WeBSphere Adapter is unable to process data from a source containing unicode data due to a serialization error in the broker indicating that \"An invalid XML character (Unicode: 0x0) was found in the element content\". \n\nSYMPTOM\nWhen processing data using a broker that originates from a WebSphere JCA Adapter, you encounter an exception of the following form: \n\nSource = java.lang.RuntimeException caught trying to serialize BO BusinessObject: F4211BeginDoc@382a382a (F4211FSBeginDoc=F4211FSBeginDoc@67e667e6) probeid = 214 Stack Dump = java.lang.RuntimeException: An invalid XML character (Unicode: 0x0) was found in the element content:\n\nThis error occurs while you are performing data transformations within your broker, either for an XSLT or to enable monitoring or tracing of the data stream, and results in a flow failure.\n\n\nCAUSE\nThe problem occurs when the source data contains unicode data which is not allowed in XML. In the above example, this is the unicode character 0x0, but there are a number of other unicode characters that can cause the same result. The problem does not occur in the WebSphere Adapter itself because the WebSphere Adapters are entirely capable of handling full unicode data. Rather, the problem happens in some brokers which fail to properly serialize the incoming data into a valid XML object.\n\n\nRESOLVING THE PROBLEM\nThe only complete solution at this time is to not process unicode characters that are not valid in XML. This can be done by not importing data fields that might contain such characters or by purging such characters from the incoming data source. It is not sufficient to do filtering in the BO maps since the broker can still run into problems prior to this Java\u2122 mapping. \n\n\nIf handling of fields containing these unicode characters is essential to your use case, it will be necessary to open a PMR with your broker's support team (rather than the WebSphere Adapter team) to determine if there are any alternatives available.\n\n \n\nHISTORICAL NUMBER\n 75349\n344\n000"}]},{"id":"TRAIN_Q353","question":"CQWEB can\\'t retrieve repository dropdown list options in RedHat Linux, how to deal with it ?\n\nI setup a cq demo env in redhat linux with oracle database, CQ 7.1.2, LRKS 8.1.3, Linux CQ client can login CQ as the following picture 1, but CQWEB login page can't retrieve the repository dropdown list options as the following picture 2. I used cqreg to register CQ database:\n\ncqreg add_dbset -v ORACLE -s 192.168.0.84 -d ESBDB -u cqadmin -p cqadmin -dbset CQ_DEMO_ORACLE -co LOB_TYPE=CLOB -force\n\n How do I deal with it? ","answer":"Run cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user. \n\n\n\nAlso make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again.","is_impossible":false,"contexts":[{"filename":"swg21320206.txt","text":"Title: IBM ERROR: Default DB path is not set, when adding database set on RHEL 5 - United States\n\nText:\n1320206; ClearQuest; Command Line Tools; CQ; cqreg; add_dbset; initialize; CQ_DATABASES; CQDB_rgys; registry; db set; db_set; Default DB path is not set; Use cqreg initialize first; linux; RHEL; RHEL5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains why the error, \"Default DB path is not set\", occurs when adding a connection with IBM\u00ae Rational\u00ae ClearQuest\u00ae on RedHat Enterprise Linux\u00ae (RHEL) 5. \n\nSYMPTOM\nWhen running the command cqreg add_dbset, this error occurs:\n\n\"Default DB path is not set\"\n\"Default version is 7.0.0\"\n\/opt\/rational\/clearquest\/CQDB_rgys\/cqdb_registry\/7.0.0 does not exist. Use cqreg initialize first. \n\nCAUSE\nNormally, at the end of a ClearQuest installation on UNIX\u00ae based platforms, the cqreg initialize command runs automatically. The command creates the registry structure for database sets. During the installation, the command did not run successfully.\n\nDIAGNOSING THE PROBLEM\nVerify that the CQDB_rgys directory exists, as defined in the installation options. The following is the default registry location: \n\n\n\/opt\/rational\/clearquest\/CQDB_rgys\/cqdb_registry\/\n\nIf not present, then the cqreg initialize command was not successful.\n\n\nRESOLVING THE PROBLEM\nRun cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user. \n\n\n\nAlso make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again."}]},{"id":"TRAIN_Q354","question":"CICS Transaction Server and CICS Tools compatibility with z\/OS 1.13\n\nI am using CICS Transaction Server for z\/OS (CICS TS) and several CICS Tools and I would like to know if they are compatible with z\/OS V1.13?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q355","question":"What does the message \"ERROR: Records trailing spring space set to 512 is too small...\" mean?\n\nWhat does the message \"ERROR: Records trailing spring space set to 512 is too small...\" mean? ","answer":"This error can occur when a query includes multiple aggregates against varchar or nvarchar columns. As the query is being processed the system allocates memory for each row of the result set. This includes each of the GROUP BY columns and each of the aggregates. For queries doing aggregates on variable length columns, the total length of the record will vary during the process.","is_impossible":false,"contexts":[{"filename":"swg21567862.txt","text":"Title: IBM PureData Systems for Analytics - nzsql error, Records trailing spring space set to 512 is too small - United States\n\nText:\nnetezza PDA TECHNOTE (FAQ)\n\nQUESTION\n What does the message \"ERROR: Records trailing spring space set to 512 is too small...\" mean? \n\nANSWER\nThe following error may appear in the pg.log file: \n\nERROR: Records trailing spring space set to 512 is too small : Bump it up using the environment variable NZ_SPRINGFIELD_SIZE \n\nThis error can occur when a query includes multiple aggregates against varchar or nvarchar columns. As the query is being processed the system allocates memory for each row of the result set. This includes each of the GROUP BY columns and each of the aggregates. For queries doing aggregates on variable length columns, the total length of the record will vary during the process. For example, if the current min value is \"Boston\" and the new min value is \"Albuquerque\" space for the new min value needs to increase. \n\nThe NZ_SPRINGFIELD_SIZE is an extra pseudo-column that is tacked onto each row. It does not contain any data. It is a filler that starts out at NZ_SPRINGFIELD_SIZE and then dynamically shrinks and expands as needed to keep each of the aggregate rows at a fixed length. There is a single springfield in each grouping record that has to shrink and grow to offset the combined changes in width of the running values for all min\/max aggregates. \n\nTo avoid this error message, increase the value for this parameter as follows: \n\n1. nzstop\n2. export NZ_SPRINGFIELD_SIZE=1024\n3. nzstart \n\nYou can confirm that the environment variable took effect by running the command \"nzsystem showregistry\". The output should contain the following: \"system.maxSpringFieldSize = 1024\". \n\nUnfortunately, the setting for NZ_SPRINGFIELD_SIZE will revert to its default value the next time the database is stopped and started without the NZ_SPRINGFIELD_SIZE environment variable being set. To ensure that the setting persists after every database restart, do the following:\n1. Add the following line to the \/nz\/data\/config\/system.cfg file. (Create the file if it does not exist.) \n\nsystem.maxSpringFieldSize = 1024\n2. nzstop\n3. nzstart \n\nIf 1024 does not work, try higher values. Setting the limit may take a little trial and error. Increasing this value should not have a noticeable impact on other system performance. \n\n \n\nNote: \"By default 512 bytes is allocated to each row taking part in aggregations. By increasing this value by 512 we allocate over 30MB more memory for every 1 000 000 rows participating in aggregations. This is for one query, there might be other queries in the system which do aggregations as well. The more memory that is allocated for NZ_SPRINGFIELD_SIZE (for each row) the less memory left for other processes. Having said this, it is not uncommon to see NZ_SPRINGFIELD_SIZE set to 8192 without consequence but care must be taken and one must still be aware of how increasing NZ_SPRINGFIELD_SIZE will impact resources, thus increase it wisely. \" \n\n \n\nHISTORICAL NUMBER\n NZ755310"}]},{"id":"TRAIN_Q356","question":"What can be done about \"Too many open files\" messages in the DASH systemOut?\n\nWhat can be done about \"Too many open files\" messages in the DASH systemOut log on a system running Linux? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q357","question":"DataPower support for SHA-2\n\nDoes DataPower support the SHA-256 cryptographic hash function?","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.","is_impossible":false,"contexts":[{"filename":"swg21406783.txt","text":"Title: IBM When a Certificate Authority (CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate the signature of CA on certificate. - United States\n\nText:\nDatapower DP valcred SHA2 SHA-2 SHA-256 certificate trust CA TECHNOTE (FAQ)\n\nQUESTION\n When a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), can IBM Websphere DataPower SOA Appliance validate the certificate and trust chain? \n\nANSWER\n Yes, if a Certificate Authority(CA) signs a certificate using SHA2(SHA-256), IBM Websphere DataPower SOA Appliance can validate CA's signature on the certificate while building trust chain from the DataPower ValCred.\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower SOA Appliances General Firmware 3.8.1, 3.8, 3.7.3, 3.7.2"}]},{"id":"TRAIN_Q358","question":"Cannot create syndication pair between Virtual Portals with a different user repository than Base Portal\n\nSteps:\r\nI have two different user repositories one to manage my base portal and Virtual Portals. (p.e: For Base Portal I use ITDS, and for VPs I use AD) with differents admin users each.\r\nThen I created two VPs using the AD repository, and my VPs admin user on the credential vault.\r\nTried to create a syndication relationship , that is failing with the error:\r\n\"Could not communicate with the target URL. Please check that the Syndicator URL details are entered correctly, and that the credential slot user exists on the target server.\" ","answer":"The Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.","is_impossible":false,"contexts":[{"filename":"swg21681464.txt","text":"Title: IBM Syndicating to VP with exclusive realms does not work. - United States\n\nText:\nsyndication; realm; vp; admin user; getPortalAdministrator TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\n \n\nSyndication from base Portal to Virtual Portal with different realms does not work:-\n\n1) Create 2 different realms with different base entries and map one realm ( with base entry e.g DC=org1,DC=test) to base Portal.\n\n2) Create a Virtual portal and map it to another realm ( with base entry e.g DC=org2,DC=test).\n\n3) Attempt to carry out syndication from Base Portal to Virtual Portal.\n\n4) The syndication fails with below exception:\n\n[datetime] 0000007f PackageGenera I createIceProjectItemRemoves():: p_items length = 0 \n[datetime] 0000008b ResponseBL I Performing response for sender: 1abc2a07-e70a-4804-8e09-b7b897eef534\n[datetime] 000000a1 SubscriberTas E Unexpected exception thrown while updating subscription: [IceId: <1abc2a07-e70a-4804-8e09-b7b897eef534> Current State: <ICE-INITIAL>], exception: com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST\n[...]\nat com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator(UserManagementServiceImpl.java:1678)\n[...]\n\n\nCAUSE\n\nThe Admin user exists on Base Portal but not the Realm which is configured to Virtual Portal.\n\nThe Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() does not have access to the Virtual Portal.\n\n\nRESOLVING THE PROBLEM\n \n\nThe Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.\n\nRELATED INFORMATION\n Realm Support [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/xpDocViewer.xsp?lookupName=IBM%20WebSphere%20Portal%208%20Product%20Documentation&documentId=3B264D090122D90D85257B26000692C6&action=openDocument&rev=true&mode=original&content=pdcontent]"}]},{"id":"TRAIN_Q359","question":"Help with Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects IBM MQ Appliance (CVE-2015-7575)\n\nI need to understand details regarding Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects IBM MQ Appliance (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)","is_impossible":false,"contexts":[{"filename":"swg21974599.txt","text":"Title: IBM Security Bulletin: Vulnerability in MD5 Signature and Hash Algorithm affects IBM MQ Appliance (CVE-2015-7575) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The MD5 \u201cSLOTH\u201d vulnerability on TLS 1.2 affects IBM MQ Appliance \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 MQ Appliance M2000\n\nREMEDIATION\/FIXES\nApply the ifix for APAR IT13296 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/IBM%20MQ%20Appliance%20M2000&fixids=8.0.0.4-IBM-MQ-Appliance-M2000-IT13223&function=fixId&parent=ibm\/WebSphere].\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] ACKNOWLEDGEMENT\nReported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \n\nCHANGE HISTORY\n 26 January 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 IBMMQ"}]},{"id":"TRAIN_Q360","question":"Is it possible to monitor Memory\/LPAR metrics using ITM HMC agent?\n\nI understand the ITM AIX Premium agent captures these metrics but like to know if it is possible to monitor Memory\/LPAR metrics using ITM HMC agent? ","answer":"6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n---------------------------------\nFeature: 208626\nAbstract: LPAR Memory Attributes\nAdditional information: The following new attributes are added in\nthe Server LPARs attribute group:\n\nCurrent_Memory - The current amount of memory, in megabytes,\nconfigured for the LPAR.\nWarehouse name: CM0\nRunning_Memory - The amount of memory, in megabytes, varied on-line\nby the LPAR.\nWarehouse name: RM\n\nIn order to display these new attributes in the Tivoli Enterprise\nPortal, use the Query Editor and select Server LPARs_V9 under\nKPH SERVER LPARS.","is_impossible":false,"contexts":[{"filename":"swg24042283.txt","text":"Title: IBM Tivoli Monitoring: HMC Base Agent 6.2.2.3-TIV-ITM_HMC_BASE-IF0004 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This fix resolves the APARs listed in the APAR Number(s) section below, and adds enhancement feature 215857 to add hardware events. \n\nDOWNLOAD DESCRIPTION\nCopyright International Business Machines Corporation 2015. \nAll rights reserved.\n\n\nComponent: IBM(R) Tivoli(R) Monitoring: HMC Base Agent,\nVersion 6.2.2.3\n\nComponent ID: 5724C04HB\n\nInterim Fix 0004, 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\n\nDate: October 20, 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===============\nThis fix resolves the APARs and defects listed in the \"Problems Fixed\"\nsection below.\n\n\n2.0 Problems fixed\n============\nThe following problems are addressed by this fix.\n\n2.1 APARs\n---------------\n\nAPAR: IV67769\nAbstract: APPLICATION SUPPORT MISMATCH WARNING MESSAGE\nAdditional information: After installing interim fix\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003, the Tivoli Enterprise\nPortal might display a warning indicator that states\nApplication Support Mismatch and shows HMC Base Servers\nwith Client Version 06220302 and Server Version 06220303. \n\n2.3 Enhancements\n------------------\nFeature: 215857\nAbstract: New Hardware Events Attribute Group\nAdditional information: Add a new attribute group to collect \nhardware events from the Hardware Management\nConsole (HMC).\n\nAttribute group name: Hardware Events\nTable name : KPHHDWEVNTS\nWarehouse table name: KPH_HARDWARE_EVENTS or KPHHDWEVNTS\n\nAttribute descriptions:\n\nProblem_No - The problem number of the event.\nReference_Code - The reference code for the event.\nFirst_Report_Time - The first time when the event was reported.\nPMH_No - The IBM hardware support PMR number that\nwas created if the call home was successful.\nFirmware_Fix - The Firmware Fix for the event.\nService_Event_Text - The description of the service event.\nApproval_State - The event approval state, either approved or\nunapproved.\nDuplicated_Count - The number of times the event has occurred.\nSeverity - The event severity.\nSystem_MTMS - The machine type\/model of the server\nreporting the event.\nEnclosure_MTMS - The machine type\/model of the enclosure\nsystem reporting the event.\nCreated_Time - The time the event was created.\nEvent_Time - The time the event was reported.\nCall_Home_Intended - Defines if call home was intended for this\nevent, either true or false.\nAnalyzing_MTMS - The machine type\/model of the analyzing system.\nReference_Code_Extent - The extent of reference code.\nSystem_Ref_code - The system reference code.\n\n2.4 Superseded fixes\n---------------------\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003\n6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n6.2.2.3-TIV-ITM_HMC_BASE-IF0001\n\n2.5 APARs and defects included from superseded fixes\n---------------------------------------------------------------\n\n6.2.2.3-TIV-ITM_HMC_BASE-IF0003\n---------------------------------\nAPAR: IV60709\nAbstract: NO CPU DATA WHEN HMC TIME ZONE IS SET TO BST\nAdditional information: If the Hardware Management Console (HMC)\ntime zone is set to BST, data might not be collected.\nThe data provider might use the incorrect time zone\nbecause BST can represent more than one time zone, for\nexample, British Summer Time and Bangladesh Standard\nTime. When the data provider sends the commands to the\nHMC to collect the CPU data, the start and stop times of\nthe commands might not be correct and might not receive\nany data. Also, data might be collected, but for the\nwrong time frame. \n\n6.2.2.3-TIV-ITM_HMC_BASE-IF0002\n---------------------------------\nFeature: 208626\nAbstract: LPAR Memory Attributes\nAdditional information: The following new attributes are added in\nthe Server LPARs attribute group:\n\nCurrent_Memory - The current amount of memory, in megabytes,\nconfigured for the LPAR.\nWarehouse name: CM0\nRunning_Memory - The amount of memory, in megabytes, varied on-line\nby the LPAR.\nWarehouse name: RM\n\nIn order to display these new attributes in the Tivoli Enterprise\nPortal, use the Query Editor and select Server LPARs_V9 under\nKPH SERVER LPARS.\n\n6.2.2.3-TIV-ITM_HMC_BASE-IF0001\n---------------------------------\n\nAPAR: IV47101\nAbstract: NO CPU DATA DUE TO TIME OUTS ON HMC SSH CALLS\nAdditional information: In large environments, where there are more\nthan 150 LPARs on a server, the CPU Units used and CPU\nUsed Pct might display \"Not Collected.\" The\nkph_data_provider_<instance>_0.log displays the\nfollowing message: \n--\nSEVERE: SSHCommandExecutor.call: Timed out while waiting\nfor `lslparutil -m \"<server>\" -r \"lpar\" -s s -F\n'lpar_id|time|time_cycles |\nentitled_cycles|capped_cycles|uncapped_cycles| idle_cycles'\n--\n\nAPAR: IV50134\nAbstract: NO CPU DATA WHEN HMC TIME SET TO GMT FORMAT\nAdditional information: If the HMC time zone is set to a GMT format,\nfor example, GMT-08:00, CPU data might not be collected\nbecause the data provider does not recognize the GMT\nformat and will default to using the local time zone. \nWhen the data provider sends the commands to the HMC to\ncollect the CPU data, the start and stop times of the\ncommands might not be correct and might not receive any\ndata. It is also possible that data will be collected,\nbut for the wrong time frame.\n\nAPAR: IV50135\nAbstract: NO DATA IN MEMORY AND PAGING SPACE VIEW\nAdditional information: The System workspace might not display any\ndata in the Memory and Paging Space views. This can\nhappen when the HMC commands:\n---\nmonhmc -r swap -n 0\nmonhmc -r mem -n 0\n---\nreturn data in M bytes instead of k bytes:\n---\nSwap: 1992M total, 0M used, 1992M free, 2853M cached \nMem: 24336M total, 4534M used, 19801M free, 480M buffers\n---\n\nAPAR: IV50686\nAbstract: NO CPU DATA IN NON-ENGLISH LOCALE\nAdditional information: When the agent runs in a non-English locale,\nattributes \"CPU Units Used\" and \"CPU Used Pct\" might\ndisplay as \"Not Collected\" due to a Java problem. The\nkph_data_provider_0.log will have a message similar to\nthis: \n---\nWARNING: \nManagementConsoleInventoryItemBuilder$BasicDataCommand.\nprocessResult: An error occurred while parsing the N2 date\nfield \"Fri Sep 27 11:35:31 JST 2013\". Continuing. \n---\n\n2.2 Defects\n---------------\nDefect: 207939\nAbstract: Java CPCI - deadlock due to bad lock usage in some versions\nof Java runtime\nAdditional information: Classloading and resource loading might get\nlocks in the wrong order, due to Java APAR IZ96933, \ncausing the data provider to stop collecting data. This\nfix prevents the problem no matter what version of Java is\nrunning.\n\nDefect: 208541\nAbstract: Add log messages to show data sent to kphagent\nAdditional information: At log level of FINEST, show the contents of\nthe rows of data sent from the data provider to the \nkphagent process.\n\n\n3.0 Architecture and prerequisites\n======================\nThis fix is supported on all operating systems listed in the\nIBM Tivoli Monitoring: HMC Base Agent User's Guide, version 6.2.2.3.\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--------------------------------\nThe prerequisite level for this fix is as follows:\n\nIBM Tivoli Monitoring: HMC Base Agent, Version 6.2.2 Interim\nFeature 3, which is available from PassPort Advantage under the\nfollowing eAssembly:\n\nIBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, English\n(CIH93EN) (Both agent and support files are included in this one\npackage)\nIBM Tivoli Monitoring for System p V6.2.2 Interim Feature 3, Language\nSupport, Multiplatform, Multilingual (CIH94ML)\n\nFor details, see the Troubleshooting Wiki:\n\nhttps:\/\/www.ibm.com\/developerworks\/mydeveloperworks\/wikis\/home?lang=en#\/wiki\/Tivoli%20Monitoring\/page\/System%20P%20Agents [https:\/\/www.ibm.com\/developerworks\/mydeveloperworks\/wikis\/home?lang=en#\/wiki\/Tivoli%20Monitoring\/page\/System%20P%20Agents]\n\nAs this fix is cumulative, it can be installed on any fix level for\nthis version, release, and mod level above the prerequisite.\n\n\n4.0 Image directory contents\n===================\nThis fix image contains the following files:\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.README - This README file\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar - Fix archive .tar format\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004.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 if \nyou are working in a Windows(R) environment. \n\nThe fix archive file contains the following files:\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\/kphaix526.dsc\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\/kph_aix526_tema_if0004.tar\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\/ph_dd.properties\n- 6.2.2.3-TIV-ITM_HMC_BASE-IF0004\/ph_dd_062203004.xml\n- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004\/kpk_tems_teps_tepd_if0004.tar\n- 6.2.2.2-TIV-ITM_HMC_BASE-IF0004\/kpk_tems_teps_tepd_if0004.zip\n\n\n5.0 Installation instructions \n==================\nThis fix can only be installed over an existing installation. Use\nthe 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- For the purpose of this README, the symbol <CANDLEHOME> is the \nIBM Tivoli Monitoring installation directory. The default value\nfor CANDLEHOME is '\/opt\/IBM\/ITM' on UNIX systems and 'C:\\IBM\\ITM'\non Windows systems.\n\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- 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.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary\ndirectory on the system that contains the agent code to be\nupdated. For the purpose of this README, the symbol <TEMP>\nrepresents the fully qualified path to this directory. Note: On\nWindows systems, this path includes the drive letter.\n\n2. Expand the archive file using the \"tar\" command on UNIX systems or \nan extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the supported\nplatforms.\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<TEMP>\/6.2.2.3-TIV-ITM_HMC_BASE-IF0004, the install command is:\n\n> itmpatch -h <CANDLEHOME> \n-i <TEMP>\/6.2.2.3-TIV-ITM_HMC_BASE-IF0004\/kph_aix526_tema_if0004.tar\n\n5.3 Remote agent update\n----------------------------\n1. Transfer the appropriate archive file\n(6.2.2.3-TIV-ITM_HMC_BASE-IF0004.tar or .zip) to a temporary\ndirectory on the IBM Tivoli Enterprise Monitoring Server system.\nFor the purpose of this README, the symbol <TEMP> 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 or \nan extract utility on Windows systems. This step creates a\ndirectory structure that contains fixes for all of the supported\nplatforms.\n\n3. To add the agent fix bundles into the remote deploy depot, use the\n\"tacmd 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 the IBM Tivoli Monitoring\nAdministrator's Guide.\n\nOn UNIX systems, \nif the fix was expanded to <TEMP>\/6.2.2.3-TIV-ITM_HMC_BASE-IF0004:\n> $CANDLEHOME\/bin\/tacmd addBundles -n -i <TEMP>\/6.2.2.3-TIV-ITM_HMC_BASE-IF0004\n\nOn Windows systems, \nif the fix was expanded to <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004:\n> %CANDLE_HOME%\\bin\\tacmd addBundles -n -i <TEMP>\\6.2.2.3-TIV-ITM_HMC_BASE-IF0004\n\nwhere:\n-n indicates that prerequisite bundles are not automatically\nadded. The -n parameter must be used because the fix \ndirectory does not contain any prerequisites that the fix\nmight require. Please see Section 3.1 for the prerequisites\nfor this fix.\n-i is the directory that contains the deployment bundles to be\nadded to the depot. \n\n4. To log in to the Tivoli Enterprise Monitoring server, and deploy\nthe fix to the appropriate nodes where the agent is running, use\nthe following \"tacmd\" commands. For more information on the\n\"tacmd login\" and \"tacmd updateAgent\" commands, see the IBM Tivoli\nMonitoring Administrator's Guide.\n\nOn UNIX systems: \n> $CANDLEHOME\/bin\/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> $CANDLEHOME\/bin\/tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> $CANDLEHOME\/bin\/tacmd updateAgent -t ph\n-n <Managed system name>\n-v 062203004\n\nOn Windows systems:\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems\n\nThe output shows the Managed System Name for the OS agent on the\nremote system to be updated. Use this value as the target of the\n\"tacmd updateAgent\" command.\n\n> %CANDLE_HOME%\\bin\\tacmd updateAgent -t PH \n-n <Managed system name> \n-v 062203004\n\nNote:\n- The component (-t) for the \"tacmd updateAgent\" command is\nspecified as two characters (PH), not three characters (KPH).\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.4 Agent support update\n------------------------------\n\nThis fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the agent\nsupport files which need to be installed. Use the following steps to\nupdate the Tivoli Enterprise Monitoring Server, Tivoli Enterprise\nPortal Server, or Tivoli Enterprise Portal Desktop.\n\n1. Transfer the appropriate archive file\n(6.2.2.2-TIV-ITM_HMC_BASE-IF0004.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 (kph_tems_teps_tepd_if0004.tar or .zip)\nthat contains the updates for Tivoli Enterprise Monitoring Server,\nTivoli Enterprise Portal Server, and Tivoli Enterprise Portal\nDesktop using the \"tar\" command on UNIX systems or an extract\nutility 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\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-if0003 at\n\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034924 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034924]\n\nfor download and installation instructions.\n\n-- OR --\n\n2. Specify the '-j javahome' parameter with the path to\na Java(r) 1.5 or java 1.6 installation when running\nthe itmasi.sh or itmasi.bat script described below.\n\nGUI installation option\n------------------------\nThe GUI can be started by using one of the following commands\nfrom within the CD-ROM directory where setup.jar is located.\n\nOn UNIX systems:\n> .\/itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]\n\nOn Windows systems:\n> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]\n\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\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: Using the silent installation option for Linux and zLinux\noperating systems requires the following files contained in\ninterim fix 6.2-TIV-ITM_ASI-IF0001:\n- Linux: setupLinux.bin\n- zLinux: setupLinux390.bin\nFollow the installation instructions contained in the\n\"6.2-TIV-ITM_ASI-IF0001.README\".\n\nOn UNIX systems:\n> .\/itmasi.sh -h <CANDLEHOME>[-silent]\n[-r <response file>]\n[-j <JAVAHOME>]\n\nOn Windows systems:\n> itmasi -h <CANDLEHOME> [-silent]\n[-r <response file>]\n[-j <JAVAHOME>]\n\nwhere:\n-h <CANDLEHOME> - Required. The path to the IBM Tivoli\nMonitoring installation directory.\n\n-r <response file> - Optional. Customized response file name.\nThe default response file \"response.txt\" in\nthe CD-ROM directory can be copied and modified\nfor your environment. Do not update \"response.txt\".\n\n-j <JAVAHOME> - Optional. The fully-qualified path to the \"bin\"\ndirectory where Java(R) is installed. The\nlocation of Java on your system might vary.\n\n5. The next panel presented by the Application Support Installer asks\nfor the selection of which Tivoli Monitoring components you want\nto add application support to. For this fix, check or clear the\ncheck boxes 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 HMC Base\n06.22.03.04 support to complete the installation.\n\n6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise Portal\nBrowser was running when the update was installed, it must be\nrestarted.\n\n\n6.0 Additional installation information\n========================\n\nFor additional troubleshooting installation information, see the\nitmpatch.log in the patchlogs directory in <CANDLEHOME>.\n\n6.1 Installation instructions for agent baroc file\n-----------------------------------------------------\nThis fix 6.2.2.2-TIV-ITM_HMC_BASE-IF0004 includes changes to the\nagent baroc files that must be installed. Refer to IBM Tivoli\nMonitoring Installation and Setup Guide under \"Installing monitoring\nagent baroc files on the event server\" in \"Installing the IBM Tivoli\nEnterprise Console Event Synchronization\" section for more\ninformation.\n\n6.2 Additional information on using \"itmpatch\" command\n--------------------------------------------------------------\nThe \"itmpatch\" command has the following syntax:\n\nUsage: itmpatch -h <installation home> [OPTIONS]\n\nitmpatch -h <installation home>\n-t { <patch_file_directory> | <patch_file> }\n\nitmpatch -h <installation home>\n-i { <patch_file_directory> | <patch_file> }\n\nwhere:\n-h Specifies the IBM Tivoli Monitoring installation directory\n-i Specifies the path to the directory or patch file to be installed\n-t Generates a report of the actions to be taken by the patch\n\n\nFor example, on UNIX systems:\n- To preview the fix installation, use the \"-t\" option:\n> <CANDLEHOME>\/bin\/itmpatch -h <CANDLEHOME> -t <TEMP>\n\n- To install the fix, use the \"-i\" option:\n> <CANDLEHOME>\/bin\/itmpatch -h <CANDLEHOME> -i <TEMP>\n\nwhere:\n<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring\ninstallation directory. On Windows systems, this path must include\nthe drive letter.\n<TEMP> represents the fully qualified directory specification where\nthe fix is located. On Windows systems, this must include the drive\nletter.\n\n6.3 Verifying the update\n----------------------------\n\n1. To verify the agent was updated correctly, use the \"tacmd\" command\nto view the agent's current version after the agent is restarted.\nYou are required to log in to a Tivoli Enterprise Monitoring\nServer prior to viewing the agent version.\n\nFor example:\nOn UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring\ninstallation directory, the default location is '\/opt\/IBM\/ITM'. \n\n> $CANDLEHOME\/bin\/tacmd login -s <server>\n-u <itmuser> \n-p <password>\n> $CANDLEHOME\/bin\/tacmd listSystems -t PH\n\nOn Windows systems, where %CANDLE_HOME% is the IBM Tivoli\nMonitoring installation directory, the default location\nis 'C:\\IBM\\ITM'. \n\n> %CANDLE_HOME%\\bin\\tacmd login -s <server>\n-u <itmuser> \n-p <password>\n\n> %CANDLE_HOME%\\bin\\tacmd listSystems -t PH \n\nNote: The component (-t) for the \"tacmd listSystems\" command is\nspecified as two characters (PH), not three characters (KPH).\n\nWhen the agent update is successful, the agent version is:\n06.22.03.04.\n\n2. To verify the agent support files were updated correctly, use the\n\"kincinfo\" 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 displayed date of 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*********** Thu Oct 7 13:57:24 CST 2015 ******************\nUser: root Groups: system bin sys security cron audit lp\nHost name : <hostname> Installer Lvl:06.30.02.00\nCandleHome: \/opt\/IBM\/ITM\n***********************************************************\n...Product inventory\n.\n.\n.\nph Monitoring Agent for HMC Base\ntms Version: 06.22.03.04\ntps Version: 06.22.03.04\ntpw Version: 06.22.03.00\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{Add your sample output here}\n*********** Thu Oct 7 16:03:55 Eastern Standard Time 2015 **********\nUser : Administrator Group : NA\nHost Name : <hostname> Installer: Ver: 062204000\nCandleHome: C:\\IBM\\ITM\nInstallitm: C:\\IBM\\ITM\\InstallITM\n*********************************************************************\n.\n.\n.\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n\nPH Monitoring Agent for HMC Base Support\nWINNT Version: 06.22.03.04 Build: 201510070000\n.\n.\n.\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 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\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: HMC Base Agent, Version 6.2.2 Interim Feature 3\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.2.2.3-TIV-ITM_HMC_BASE-IF0004 18 May 2016 English 35850104 FC [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?fixids=6.2.2.3-TIV-ITM_HMC_BASE-IF0004&product=ibm%2FTivoli%2FIBM+Tivoli+Monitoring&source=dbluesearch&platform=All] [ ] \nPRODUCT ALIAS\/SYNONYM\n HMC Agent\nMonitoring Agent for System P\nSystem P Agent \n\n [\/support\/docview.wss?uid=swg24042283&aid=1]Problems (APARS) fixed [\/support\/docview.wss?uid=swg24042283&aid=2]Problems (APARS) fixed\nIV47101, IV50134, IV50135, IV50686, IV60709, IV67769"}]},{"id":"TRAIN_Q361","question":"Is MQ V7.0.1 is going out of support?\n\nWhen is the last date of support?","answer":"Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015","is_impossible":false,"contexts":[{"filename":"swg21674407.txt","text":"Title: IBM Announcement: End of Support for WebSphere MQ and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 and WebSphere MQ Telemetry V7.0.1 - United States\n\nText:\n NEWS\n\nABSTRACT\n IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z\/OS V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition for z\/OS V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1. \n\nCONTENT\n\n\nTAB NAVIGATION\n * WebSphere MQ and File Transfer Edition V7.0.1 and V7.0.0 \u2022 MQ Telemetry V7.0.1 selected tab\n\nTAB NAVIGATION\n * What were the end of support dates for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1?\n * Do these announcements affect WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, or WebSphere MQ Hypervisor Edition V7.0.1?\n * What replacement products are available?\n * How do I check which version I am currently running?\n * Is any information available to help me upgrade to a later version?\n * How do I purchase a support extension for my current version?\n * When a WebSphere MQ server product goes out of support, does the client and file transfer agent also go out of support?\n * Are these products still supported when they are bundled with another IBM product?\n * Is the WebSphere MQ V7.0 Resource Adapter supported in WebSphere Application Server?\n * Is documentation still available for these products?\n * How do I obtain installation images for these products if I still need them?\n * Is there an IBM MQ V9.0 or MQ V8.0 trial version available for download?\n\n\n\n[\/support\/docview.wss?uid=swg21674407&aid=1]\n\n\n\n\nWHAT ARE THE END OF SUPPORT DATES FOR WEBSPHERE MQ V7.0.1 AND V7.0.0, WEBSPHERE MQ FILE TRANSFER EDITION V7.0.1 AND V7.0.0, AND WEBSPHERE MQ TELEMETRY V7.0.1?\n\n * \n * Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5\/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z\/OS V7.0.1 25 Sep 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-248] 30 Sep 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-150] z\/OS WebSphere MQ V7.0.0 16 Jun 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-068] 30 Apr 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5\/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z\/OS V7.0.0 27 Jun 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-067] 30 Sep 2011 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS910-014] z\/OS WebSphere MQ File Transfer Edition V7.0.1 05 Jun 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-118] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z\/OS V7.0.1 12 Jun 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-119] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z\/OS WebSphere MQ File Transfer Edition V7.0.0 05 Dec 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-331] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z\/OS V7.0.0 12 Dec 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-339] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z\/OS WebSphere MQ Telemetry V7.0.1 27 Aug 2010 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-201] 30 Sep 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] Linux (x86-64), Windows (x86) \n * \n * Review lifecycle dates for all IBM MQ and WebSphere MQ products [http:\/\/www.ibm.com\/software\/support\/lifecycleapp\/PLCSearch.wss?q=%28+%22IBM+MQ%22+OR+%22WebSphere+MQ%22+%29+AND+NOT+%28+Tivoli+OR+Adapter+OR+Broker+OR+Integrator+OR+Workflow+OR+%22Low+Latency+Messaging%22+%29]\n \n End of support information for WebSphere MQ V7.5 and WebSphere MQ Hypervisor Edition V7.5 [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg21996472]\n \n End of support information for WebSphere MQ V7.1, WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, and WebSphere MQ Hypervisor Edition V7.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg21980668]\n \n \n * Back to top\n\n\n\n\nDO THESE ANNOUNCEMENTS AFFECT WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4, V7.0.3 AND V7.0.2, WEBSPHERE MQ ADVANCED MESSAGE SECURITY V7.0.1, OR WEBSPHERE MQ HYPERVISOR EDITION V7.0.1?\n\n * IBM has subsequently announced the end of support for these products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21980668] on all platforms including z\/OS:\n * \n * Lifecycle dates for WebSphere MQ V7.0 products [http:\/\/www.ibm.com\/software\/support\/lifecycleapp\/PLCSearch.wss?q=%28%22WebSphere+MQ+%22+AND+%227.0%22%29+OR+%28%22WebSphere+MQ+File+Transfer+Edition+%22+AND+%28%227.0.4%22+OR+%227.0.3%22+OR+%227.0.2%22%29%29+OR+%28%22WebSphere+MQ+Advanced+Message+Security+%22+AND+%227.0.1%22%29] \n * \n * Back to top\n\n\n\n\nWHAT REPLACEMENT PRODUCTS ARE AVAILABLE?\n\n * Replacements for WebSphere MQ V7.0.1 and V7.0.0 include IBM MQ or IBM MQ Advanced V9.0 and V8.0. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 Apri 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * Replacements for WebSphere MQ for z\/OS V7.0.1 and V7.0.0 include IBM MQ, IBM MQ Advanced, or IBM MQ Value Unit Edition for z\/OS V9.0 and V8.0.0.\n * Replacements for WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 include IBM MQ Advanced V9.0 and V8.0. WebSphere MQ Advanced V7.5 is also available (except on IBM i), but its end of support date is 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117]. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ and replace the former File Transfer Edition and Advanced Message Security products.\n * Replacements for WebSphere MQ File Transfer Edition for z\/OS V7.0.1 and V7.0.0 include IBM MQ Advanced for z\/OS V9.0 and V8.0.0. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ for z\/OS and replace the former File Transfer Edition for z\/OS and Advanced Message Security for z\/OS products.\n * The replacement for WebSphere MQ Telemetry V7.0.1 is IBM MQ or IBM MQ Advanced V9.0 or V8.0, all of which include Telemetry as a component of the MQ product. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * \n * \n * Back to top\n\n\n\n\nHOW DO I CHECK WHICH VERSION I AM CURRENTLY RUNNING?\n\n * Follow these general instructions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21621707] or the IBM MQ Knowledge Center instructions [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.ref.adm.doc\/q083280_.htm] to display your IBM MQ or WebSphere MQ version on all platforms except for z\/OS with the command: dspmqver\n * On z\/OS, look for message CSQY000I [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.ref.doc\/csq_y.htm] in the MSTR joblog to determine your version.\n * Follow the IBM MQ Knowledge Center instructions [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.wmqfte.doc\/display_ver_cmd.htm] to display your Managed File Transfer or WebSphere MQ File Transfer Edition version with the command: fteDisplayVersion\n * WebSphere MQ Telemetry V7.0.1 only runs on WebSphere MQ V7.0.1 (fix pack 7.0.1.3 and later) on Linux (x86-64) and Windows (x86). Although there is no command to display the WebSphere MQ Telemetry version, if your WebSphere MQ version is V7.0.1 and you have a WebSphere MQ Telemetry service and channels [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.tt.doc\/tt_intro.htm] configured, then you are running WebSphere MQ Telemetry V7.0.1.\n * \n * Back to top\n\n\n \n[\/support\/docview.wss?uid=swg21674407&aid=2]\n\n \n\n\n\n\nIS ANY INFORMATION AVAILABLE TO HELP ME UPGRADE TO A LATER VERSION?\n\n * The IBM MQ and WebSphere MQ Migration Guide [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/aimsupport\/entry\/websphere_mq_ibm_mq_migration_guide] is available to view online or download:\n * IBM MQ and WebSphere MQ Migration Guide [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/aimsupport\/resource\/MQ_migration\/WMQ_Migration.pdf] \n * \n * The IBM Knowledge Center also includes information to assist you in migrating to a supported version of IBM MQ or WebSphere MQ:\n * Migrating and upgrading to IBM MQ V9.0 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.mig.doc\/q006180_.htm] Migrating and upgrading to IBM MQ V8.0 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.mig.doc\/q006180_.htm] Migrating and upgrading to WebSphere MQ V7.5 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.5.0\/com.ibm.mq.mig.doc\/q006180_.htm] \n * \n * The following WebSphere Support Technical Exchange presentations may be helpful if you are considering running multiple MQ installations on your system:\n * Webcast replay: WebSphere MQ Multi-Version - First Steps [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024276] Webcast replay: WebSphere MQ Multi-Version - Environment Considerations and Management [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024340] \n * \n * Back to top\n\n\n\n\nHOW DO I PURCHASE A SUPPORT EXTENSION FOR MY CURRENT VERSION?\n\n * Support extensions are available for an additional fee. To purchase extended support for WebSphere MQ or any of the other products, please contact your local IBM sales representative.\n * US Customers should contact Customer Support Operations at 1-877-426-6006, option #2. If you provide your IBM customer number, they can quickly find your sales representative.\n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region:\n * \n * IBM Directory of Worldwide Contacts [http:\/\/www.ibm.com\/planetwide\/] \n * \n * Back to top\n\n\n\n\nWHEN AN WEBSPHERE MQ SERVER PRODUCT GOES OUT OF SUPPORT, DOES THE CLIENT AND FILE TRANSFER AGENT ALSO GO OUT OF SUPPORT?\n\n * Yes. WebSphere MQ V7.0 clients and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 agents go out of support at the same time as the server.\n * \n * Back to top\n\n\n [\/support\/docview.wss?uid=swg21674407&aid=3] \n\n\n\n\nARE THESE PRODUCTS STILL SUPPORTED WHEN THEY ARE BUNDLED WITH ANOTHER IBM PRODUCT?\n\n * Yes, support is available for all bundled components until the IBM product that includes them is withdrawn from support. However, they are only supported when used by the bundling IBM product. Unrelated usage is not supported.\n * \n * Find the end of support date for your IBM software product [http:\/\/www.ibm.com\/software\/support\/lifecycle\/index_a_z.html] \n * \n * Back to top\n\n\n\n\nIS THE WEBSPHERE MQ V7.0 RESOURCE ADAPTER SUPPORTED IN WEBSPHERE APPLICATION SERVER?\n\n * Yes, the WebSphere MQ V7.0 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0] shipped with WebSphere Application Server V8.0 and V7.0 is supported through 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-143], when both of those versions of WebSphere Application Server end support, or longer if you purchase a WebSphere Application Server support extension.\n \n * Similarly, the WebSphere MQ V7.1 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0_0] shipped with WebSphere Application Server V8.5.x is supported as long as that version of WebSphere Application Server remains in support, or longer if you purchase a WebSphere Application Server support extension.\n \n * However, if you manually install your own copy of the WebSphere MQ V7.x Resource Adapter in WebSphere Application Server or any third-party Java EE server, it will go out of support with the corresponding WebSphere MQ server version.\n \n * The IBM MQ V8.0 and V9.0 Resource Adapters cannot be installed in WebSphere Application Server V8.5.x, V8.0 and V7.0 because those versions support JMS 1.1 while the IBM MQ Resource Adapters implement JMS 2.0. WebSphere Application Server V9.0 ships with the IBM MQ V9.0 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0_0_0] and includes full support for JMS 2.0. The version of MQ Resource Adapter you use must be supported by your Java EE server but does not need to match the version of the queue managers to which you wish to connect.\n \n * Back to top\n\n \n\n\n\n\nIS DOCUMENTATION STILL AVAILABLE FOR THESE PRODUCTS?\n\n * Yes. Online documentation is available in the IBM Knowledge Center, while downloadable Information Center installations and PDF versions of the manuals are available from the MQ Library page.\n * \n * WebSphere MQ V7.0.1 Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.helphome.v70.doc\/WelcomePagev7r0.htm] WebSphere MQ V7.0.1 library of downloadable documentation [http:\/\/www.ibm.com\/software\/integration\/wmq\/library\/library701.html] WebSphere MQ V7.0.0 library of downloadable documentation [http:\/\/www.ibm.com\/software\/integration\/wmq\/library\/library700.html] WebSphere MQ File Transfer Edition V7.0.4 Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEP7X_7.0.4\/welcome\/WelcomePagev7r0.html] WebSphere MQ Telemetry V7.0.1 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.tt.doc\/tt_intro.htm] \n * \n * Back to top\n\n\n\n\nHOW DO I OBTAIN INSTALLATION IMAGES FOR THESE PRODUCTS IF I STILL NEED THEM?\n\n * Installation images for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1 are no longer available from Passport Advantage [https:\/\/www.ibm.com\/software\/passportadvantage\/pao_customer.html]. Contact IBM if you have an urgent business need for these installation images.\n * \n * Back to top\n\n\n \n[\/support\/docview.wss?uid=swg21674407&aid=4]\n\n \n\n\n\n\nIS THERE AN IBM MQ V9.0 OR MQ V8.0 TRIAL VERSION AVAILABLE FOR DOWNLOAD?\n\n * You can obtain a full-featured trial version of IBM MQ to evaluate for 90 days:\n * \n * Try IBM MQ now [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/preLogin.do?pkgid=&S_SRCID=ESD-WSMQ-EVAL&source=ESD-WSMQ-EVAL&S_TACT=109J84RW&S_CMP=web_ibm_ws_appint_ct_wmq-ov&S_PKG=CR9H9ML&s=&id=2009-08-28+03%3A34%3A46.648052R&fam=&cat=&l=English+International&m=download&ibm-continue=Continue] \n * \n * Back to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ File Transfer Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z\/OS 7.0.1, 7.0 All Editions Business Integration WebSphere MQ Telemetry Not Applicable Linux, Windows Business Integration IBM MQ \nPRODUCT ALIAS\/SYNONYM\n WebSphere MQ WMQ"}]},{"id":"TRAIN_Q362","question":"Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Image Construction and CompositionTool. (CVE-2015-4000)\n\nI need to understand details regarding \"Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Image Construction and CompositionTool. (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)","is_impossible":false,"contexts":[{"filename":"swg21964501.txt","text":"Title: IBM Security Bulletin: Vulnerability in Diffie-Hellman ciphers affects IBM Image Construction and CompositionTool. (CVE-2015-4000) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The Logjam Attack on TLS connections using the Diffie-Hellman (DH) key exchange protocol affects IBM Image Construction and Composition Tool. \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\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:\n\n\u00b7 For IBM Image Construction and Composition Tool v2.2.1.3\n\u00b7 IBM Image Construction and Composition Tool v2.2.1.3 Build 32\n\nhttp:\/\/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-32&includeSupersedes=0 [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-32&includeSupersedes=0]\n\n\n\u00b7 For IBM Image Construction and Composition Tool v2.3.1.0\n\u00b7 IBM Image Construction and Composition Tool v2.3.1.0 Build 43\n\nhttp:\/\/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-43&includeSupersedes=0 [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-43&includeSupersedes=0]\n\n\n\u00b7 For IBM Image Construction and Composition Tool v2.3.2.0\n\u00b7 IBM Image Construction and Composition Tool v2.3.2.0 Build 16\n\nhttp:\/\/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-16&includeSupersedes=0 [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-16&includeSupersedes=0]\n\n\nYou should verify applying this configuration change does not cause any compatibility issues. If you change the default setting after applying the fix, you will expose yourself to the attack described above. IBM recommends that you review your entire environment to identify other areas where you have enabled the Diffie-Hellman key-exchange protocol used in TLS and take appropriate mitigation and remediation actions.\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 18 August 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."}]},{"id":"TRAIN_Q363","question":"Where can I find information on the Integration Bus Healthcare Pack?\n\nWhere can I find information about the Integration Bus Healthcare Pack V4.0? ","answer":"Release notes file for: IBM Integration Bus Healthcare Pack\nProduct Release: 4.0\nUpdate name: 4.0.0.0\nVersions and fix packs:\n* V4.0.0.0 (electronic availability: 25 June 2015)\nDocument first published: 25 June 2015\nDocument last modified: 25 June 2015","is_impossible":false,"contexts":[{"filename":"swg27046040.txt","text":"Title: IBM Integration Bus Healthcare Pack V4.0 release notes - United States\n\nText:\n RELEASE NOTES\n\nABSTRACT\n This document contains the release notes for IBM Integration Bus Healthcare Pack V4.0, including the tooling and runtime components. \n\nCONTENT\nRelease notes file for: IBM Integration Bus Healthcare Pack\nProduct Release: 4.0\nUpdate name: 4.0.0.0\nVersions and fix packs:\n* V4.0.0.0 (electronic availability: 25 June 2015)\nDocument first published: 25 June 2015\nDocument last modified: 25 June 2015\n\n\n\n\nContents \n\n * Download location \n * Installation information: * Prior to installation \n * Installing \n * Documentation \n * Support \n * Feature updates\n \n \n * Additional information \n * Known problems and their workarounds (if any): * Installation \n * IBM Integration Toolkit\n \n \n * Copyright and trademark information \n * Useful websites\n\n\n\n\n\nDownload location Download IBM Integration Bus Healthcare Pack V4.0 using the following instructions:\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040117 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040117] \n\n\nInstallation information \n\nAlways use the latest version of this release notes 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 release notes files are available at: \nftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/healthcare\/V4.0\/ [ftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/healthcare\/V4.0\/] \n\n\nPrior to installation \n\nFor information about the tasks you must complete before you install the product, refer to the IBM Integration Bus Healthcare Pack product documentation at:\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00090.htm [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00090.htm]\n\nInstalling \n\nInstallation information is available in the IBM Integration Bus Healthcare Pack product documentation at:\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00090.htm [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00090.htm] \n\n\n\n\n\n\n\nDocumentation The online product documentation for IBM Integration Bus Healthcare Pack is available at: \nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00000.htm [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00000.htm] \n\nAlways refer to the online product documentation for the latest information. \n\nThe stand-alone product documentation is available for download at: \nftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/healthcare\/V4.0\/iib_healthcare_help.zip [ftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/healthcare\/V4.0\/iib_healthcare_help.zip] (Windows and Linux (x86-64) version)\n\nRead the How to add the Healthcare plug-in to a help system.txt file that is included in the iib_healthcare_help.zip file. \n\n\n\n\n\n\n\nSupport Defects: This release notes 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 IBM Integration Bus 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] \nTo find information, click Troubleshooting documentation. IBM Integration Bus and IBM Integration Bus Healthcare Pack Technotes are displayed and can be ordered and searched. \n\nFor information about downloading IBM Integration Bus Healthcare Pack V4.0 installation images from the Passport Advantage website, see the Accessing the Installer topic in the IBM Integration Bus product documentation, which is available at:\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha03080.htm [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha03080.htm] \n\nVersions: For the latest information about which particular versions of operating systems are supported by IBM Integration Bus Healthcare Pack, see 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 toolkit, including documentation updates in English and in other supported languages. Recommended fixes for IBM Integration Bus Healthcare Pack can be found at: \nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006041 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006041] \n\n\n\n\n\n\nTOP Additional information \nKnown problems and their workarounds (if any): This section outlines the known problems and their workarounds (if any) of the IBM Integration Bus Healthcare Pack, by component. \n\n\n\n\n\n\nTOP Installation \n * Installation of IBM Integration Bus Healthcare Pack V4.0.0.0 on computers that have a previous version installed is not supported To install IBM Integration Bus Healthcare Pack V4.0.0.0 you must first remove any existing installations of the IBM Integration Bus Healthcare Pack or IBM WebSphere Message Broker Connectivity Pack for Healthcare.\n \n \n\n\n\n\n\nTOP IBM Integration Toolkit \n * HL7\u00ae FHIR\u00ae Draft Standard for Trial Use The HL7\u00ae FHIR\u00ae standard is used in the Healthcare: FHIR transformation pattern. The standard is a Draft Standard for Trial Use (DSTU), rather than a full normative specification.\n \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 * \n * \n * \n * \n * \n * \n * \n * \n * \n\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: * \n * \n * \n * \n * \n * \n * \n\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 Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites 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 * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\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 cannot 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, cannot 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\nAIX, developerWorks, IBM, Passport Advantage, WebSphere.\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 IBM Integration Bus product page\nhttp:\/\/www.ibm.com\/software\/products\/us\/en\/ibm-integration-bus\/ [http:\/\/www.ibm.com\/software\/products\/us\/en\/ibm-integration-bus] \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\nIBM Integration Bus Fix Packs\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006041 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006041] \n\nIBM Integration Bus Requirements\nhttp:\/\/www.ibm.com\/software\/integration\/wbimessagebroker\/requirements\/ [http:\/\/www.ibm.com\/software\/integration\/wbimessagebroker\/requirements\/] \n\nIBM Integration Bus release notes and readme files\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006917 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006917] \n\nIBM Integration Bus V10.0 stand-alone product documentation\nFor Linux:\nftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/V10.0\/ib_help_linux.tgz [ftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/V10.0\/ib_help_linux.tgz]\nFor Windows:\nftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/V10.0\/ib_help_win.zip [ftp:\/\/public.dhe.ibm.com\/software\/integration\/integrationbus\/docs\/V10.0\/ib_help_win.zip] \n\nIBM Integration Bus Healthcare Pack V4.0 online product documentation\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00000.htm [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSMKHH_10.0.0\/com.ibm.healthcare.doc\/ha00000.htm] \n\nIBM Centre for Java\u2122 Technology Development Downloads\nhttp:\/\/www.ibm.com\/developerworks\/java\/jdk\/ [http:\/\/www.ibm.com\/developerworks\/java\/jdk\/] \n\nIBM Integration Bus developerWorks Zone\nhttp:\/\/www.ibm.com\/developerworks\/websphere\/zones\/businessintegration\/wmb.html [http:\/\/www.ibm.com\/developerworks\/websphere\/zones\/businessintegration\/wmb.html] \n\nIBM Messaging blog\nhttps:\/\/www.ibm.com\/developerworks\/mydeveloperworks\/blogs\/c565c720-fe84-4f63- 873f-607d87787327 [https:\/\/www.ibm.com\/developerworks\/mydeveloperworks\/blogs\/c565c720-fe84-4f63-873f-607d87787327] \n\n\n\n\n\n\n\nTOP (C) Copyright IBM Corporation 2015. All rights reserved. \n\n\nCOPYRIGHT DATE\n 2015 \n\nORIGINAL PUBLICATION DATE\n 2015\/6\/25 \n\nPRODUCT ALIAS\/SYNONYM\n IIB IBMIB"}]},{"id":"TRAIN_Q364","question":"Receiving an error when trying to create a profile after applying WAS V8.0.0.10 (or later fixpack) to BPM V8.0.1.3 which uses MS SQL Server database\n\n\n\nAfter applying IBM WebSphere Application Server (WAS) V8.0.0.10 (or later fixpack) in IBM Business Process Manager (BPM) V8.0.1.3, I receive the following error when trying to create the profile:\n\ncom.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: \"Only SSLv3 was enabled while com.ibm.jsse2.disableSSLv3 is set to true\". RC = 300","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q365","question":"Help with Security Bulletin: Multiple vulnerabilities in Node.js affect IBM API Connect (CVE-2017-1000381, CVE-2017-11499)\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in Node.js affect IBM API Connect (CVE-2017-1000381, CVE-2017-11499). Where can I find this information?","answer":"CVEID:CVE-2017-1000381 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1000381]\nDESCRIPTION:c-ares could allow a remote attacker to obtain sensitive information, caused by an out-of-bounds read in the ares_parse_naptr_reply() function when parsing NAPTR responses. By sending specially crafted DNS response packet, an attacker could exploit this vulnerability to read memory outside of the given input buffer and cause a denial of service.\nCVSS Base Score: 6.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128625 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128625]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:L)\n\nCVEID:CVE-2017-11499 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-11499]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by a flaw related to constant HashTable seeds. A remote attacker could exploit this vulnerability to flood the hash and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/129465 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/129465]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:H)","is_impossible":false,"contexts":[{"filename":"swg22009964.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in Node.js affect IBM API Connect (CVE-2017-1000381, CVE-2017-11499) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM API Connect has addressed Node.js vulnerabilities involving access to sensitive information and potential denial of service. \n\nVULNERABILITY DETAILS\n\nCVEID:CVE-2017-1000381 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1000381]\nDESCRIPTION:c-ares could allow a remote attacker to obtain sensitive information, caused by an out-of-bounds read in the ares_parse_naptr_reply() function when parsing NAPTR responses. By sending specially crafted DNS response packet, an attacker could exploit this vulnerability to read memory outside of the given input buffer and cause a denial of service.\nCVSS Base Score: 6.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128625 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128625]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:L)\n\nCVEID:CVE-2017-11499 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-11499]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by a flaw related to constant HashTable seeds. A remote attacker could exploit this vulnerability to flood the hash and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/129465 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/129465]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:H) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\nAffected IBM API Management 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 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 LI79821 Addressed in IBM API Connect V5.0.6.5.\n\nManagement Server is impacted.\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.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.1 LI79821 Addressed in IBM API Connect V5.0.8.1.\n\nManagement Server and Developer Portal are impacted.\n\nFollow this link and find the \"APIConnect_Management\" package and\n\"APIConnect-Portal\" 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 LI79821 Addressed in IBM API Connect V5.0.8.1.\n\nManagement Server and Developer Portal are impacted. \n\nFollow this link and find the \"APIConnect_Management\" package and\n\"APIConnect-Portal\" 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] 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 06 December 2017: 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."}]},{"id":"TRAIN_Q366","question":"How do to restore corrupted Object server DB using data from Backup Object server in Linux?\n\nError: E-REG-002-025: Region 'table_store', from directory '\/opt\/IBM\/tivoli\/netcool\/omnibus\/db\/NCOMS\/', has been recovered in a corrupt state: Extent statistics mismatch Error: E-OBX-102-020: Failed to start the storage system. (-490:Extent statistics mismatch) ","answer":"1. Create a temporary directory\n\nmkdir \/tmp\/backup \n\n2. Use nco_sql to obtain a backup\n\n.\/nco_sql -server NCOMS \nPassword: \n1> alter system backup '\/tmp\/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that \/tmp\/backup contains *.tab files.\n\n4. Compressed \/tmp\/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.","is_impossible":false,"contexts":[{"filename":"swg21631606.txt","text":"Title: IBM Create backup of the ObjectServer database - United States\n\nText:\nMustGather; objectserver; backup TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Steps to create a backup of the ObjectServer database for troubleshooting. \n\nRESOLVING THE PROBLEM\nProvide the following information: \n\n[\/support\/docview.wss?uid=swg21631606&aid=1][\/support\/docview.wss?uid=swg21631606&aid=2]\n\n1. Create a temporary directory\n\nmkdir \/tmp\/backup \n\n2. Use nco_sql to obtain a backup\n\n.\/nco_sql -server NCOMS \nPassword: \n1> alter system backup '\/tmp\/backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that \/tmp\/backup contains *.tab files.\n\n4. Compressed \/tmp\/backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so.\n\n[\/support\/docview.wss?uid=swg21631606&aid=3]\n\n1. Create a temporary directory\n\nmkdir c:\\tmp\\backup \n\n2. Use nco_sql to obtain a backup\n\nisql -S NCOMS -U root \nPassword: \n1> alter system backup 'c:\\tmp\\backup'; \n2> go \n(0 rows affected) \n1> quit \n\n3. Verify that c:\\tmp\\backup contains *.tab files.\n\n4. Compressed c:\\tmp\\backup\n\n5. Copy of ObjectServers properties file (i.e. NCOMS.props)\n\n6. If you can provide the root password, do so."}]},{"id":"TRAIN_Q367","question":"1040ez 9.0 Application\n\n Hi\n\nI have downloaded sample Datacap 9 applications (1040ez, Express, Survey) using below link and copied in my local system C:\\Datacap and added reference in Datacap.xml file.\n\nIBM Datacap 9.0 and IBM Datacap 9.0.1 DDK sample applications\n\nBut i'm unable to login Datacap Studio & Tmweb.net . (I tried to with re generating encryption keys but no luck).\n\nCan anyone let me know the reason, anything I missed in configuration ?\n\nMy Datacap version in Local Machine\n\nIBM Datacap 9.0.0.3\n\nBuild: v 9.0.0.72\n\nThanks","answer":"If this is a new server where Datacap has never been run and encryption has not been set up at all, follow the instructions at Exporting encryption keys [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSZRWV_9.0.1\/com.ibm.dc.install.doc\/dcain011_copyto_cs1.htm].\n\n\nIf this is an existing server or a new server where the previous steps have been completed, distribute the dc_ktf.xml file to the client folder for all clients that will be used following the instructions at Importing encryption keys to Datacap computers","is_impossible":false,"contexts":[{"filename":"swg21968549.txt","text":"Title: IBM Couldn't validate parameters error logging in with IBM Datacap - United States\n\nText:\nlogin connect couldnt validate parameters TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Users are unable to log in with any client to any application. The Taskmaster Server (tms) log shows:\n\nConnect couldn't validate parameters \n\nSYMPTOM\nThis is most commonly seen on a new installed Taskmaster Server. Users attempting to login will receive a message stating that they cannot connect to the admin database.\n\n\nCAUSE\nEncryption is not yet fully set up, so FIPS key information cannot be located.\n\nRESOLVING THE PROBLEM\nIf this is a new server where Datacap has never been run and encryption has not been set up at all, follow the instructions at Exporting encryption keys [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSZRWV_9.0.1\/com.ibm.dc.install.doc\/dcain011_copyto_cs1.htm].\n\n\nIf this is an existing server or a new server where the previous steps have been completed, distribute the dc_ktf.xml file to the client folder for all clients that will be used following the instructions at Importing encryption keys to Datacap computers [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSZRWV_9.0.1\/com.ibm.dc.install.doc\/dcain010_copyto_wtminstall1.htm].\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable Windows 8.1.0"}]},{"id":"TRAIN_Q368","question":"Does ITCAM for MQ monitoring agent (kmq) use SYSTEM.MQXR.COMMAND.QUEUE causing Unknown Object Name [2085] event?\n\n\n\nUsing the ITCAM MQ Monitoring agent, we have a situation that generates alerts when a 2085 event (object unknown) occurs. We have recently seen alerts for the queue SYSTEM.MQXR.COMMAND.QUEUE\nWe found following technote:\nUnknown Object Name [2085], SYSTEM.MQXR.COMMAND.QUEUE\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21681687\n\nThis technote does not mention Tivoli monitoring product, and only mentions monitoring products such as Nastel and InfraRed360.\nDoes Tivoli monitoring agent for WebSphere MQ use the SYSTEM.MQXR.COMMAND.QUEUE? We are try to find out which application is causing the 2085 event.","answer":"Use the runmqsc display connection command to find the process id (PID) and application name. \n\nUsing the above example of the queue Q1, this is the complete command to invoke under runmqsc: \n\n\ndisplay conn(*) where(objname eq Q1) all","is_impossible":false,"contexts":[{"filename":"swg21318303.txt","text":"Title: IBM Identify the application that has a WMQ queue opened - United States\n\nText:\nIdentify application program connected queue TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your WebSphere MQ queue manager will not stop if there are applications that still have a queue opened. Your goal is to allow a graceful stop of the queue manager, also called controlled (or quiesced) shutdown. \n\nFor example, the following runmqsc command for the queue Q1 shows that there is an application currently that has opened a queue, but it does not provide application name, or process id number (PID). The value for OPPROCS indicates 1 application has opened the queue for output (for doing a PUT).\n\ndisplay qstatus(Q1)\n1 : display qstatus(Q1)\nAMQ8450: Display queue status details.\nQUEUE(Q1) TYPE(QUEUE)\nCURDEPTH(0) IPPROCS(0)\nLGETDATE( ) LGETTIME( )\nLPUTDATE( ) LPUTTIME( )\nMEDIALOG( ) MONQ(OFF)\nMSGAGE( ) OPPROCS(1)\nQTIME( , ) UNCOM(NO)\n\nYou want to determine the name of the application that currently has a queue open, \n\nRESOLVING THE PROBLEM\nUse the runmqsc display connection command to find the process id (PID) and application name. \n\nUsing the above example of the queue Q1, this is the complete command to invoke under runmqsc: \n\n\ndisplay conn(*) where(objname eq Q1) all\n\nExample output:\n\nAMQ8276: Display Connection details.\nCONN(ACBDC64820001B01)\nEXTCONN(414D5143514D5F414E47454C494C4C4F)\nTYPE(CONN)\nPID(7364)TID(1)\nAPPLTAG(WebSphere MQ\\bin\\amqsput.exe)APPLTYPE(USER)\nASTATE(NONE) CHANNEL( )\nCONNAME( ) CONNOPTS(MQCNO_SHARED_BINDING)\nUSERID(x) UOWLOG( )\nUOWSTDA( ) UOWSTTI( )\nUOWLOGDA( ) UOWLOGTI( )\nURTYPE(QMGR)\nEXTURID(XA_FORMATID[00000000] XA_GTRID[] XA_BQUAL[])\nQMURID(0.0) UOWSTATE(NONE)\n\nThe following fields are of interest:\nPID(7364) => Process id\nAPPLTAG(WebSphere MQ\\bin\\amqsput.exe) => name of the application\nUSERID(x) => Userid that has invoked the application\n\n\nFor UNIX users:\n\nOne of the main purposes for the above technique is to eventually kill the process that is connected to the queue manager. \n\na) One option is to use the STOP CONN command under runmqsc. Using the above example, the corresponding command would be:\nSTOP CONN(ACBDC64820001B01)\n\nb) The following SupportPac can be used to identify the applications and kill them if desired:\n\nMS6B: WebSphere MQ Connection Management Utility [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg24017810]\nThis SupportPac is Category 4 (which means that the IBM MQ Support team does not support it)\n\n \n\nPRODUCT ALIAS\/SYNONYM\n WMQ MQ"}]},{"id":"TRAIN_Q369","question":"Security Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2177)\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect IBM WebSphere MQ Advanced Message Security (CVE-2016-2177). Where can I find this information?\n","answer":"CVEID: 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)","is_impossible":false,"contexts":[{"filename":"swg21999724.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect IBM MQ Advanced Message Security (CVE-2016-2177, CVE-2016-2178) - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q370","question":"Error 7002 SPSS 25 for Linux License invalid\n\n I have SPSS 25 on my linux computer but when I try to use it, is simply says error 7002. I have already checked the time and date and tried a new authorization code but it still won't work (student license). The specific symptom number of the error is 12. Can you help me?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q371","question":"Can my system run MQ V8.0?\n\nWhere are the system requirements listed, and are there any significant changes? ","answer":"This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement.","is_impossible":false,"contexts":[{"filename":"swg27041395.txt","text":"Title: IBM System Requirements for WebSphere MQ V8.0 - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n This document contains system requirements for WebSphere MQ V8.0 and a note about IBM WebSphere MQ Advanced entitlement. \n\nCONTENT\nIBM has provided customers with a Software Product Compatibility Reports (SPCR) tool where you can locate and find complete lists of supported operating systems, system requirements, prerequisites, and optional supported software for WebSphere MQ 8.0. \n\nRHEL Compatible OS. Defect support is available for Linux environments that are fully compatible - both source and binary - with Red Hat Enterprise Linux V6. Unless stated otherwise, WebSphere MQ has not been specifically tested in such compatible environments. WebSphere MQ Support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the linux environment itself. If issues arise that are related to the compatible linux environment, the user may need to contact the linux environment vendor for support, or the issue may need to be recreated inside an environment tested by IBM in order to receive WebSphere MQ support. \n\nVirtualization. Defect support is available for virtualization environments where they relate to releases of this platform already supported by WebSphere MQ. Unless stated elsewhere in the system requirements WebSphere MQ has not been specifically tested in virtualization environments. \n\nWebSphere MQ support is therefore unable to assist in issues related to configuration and setup, or issues that are directly related to the virtualization environment itself. \n\nPlease also refer to:\nWebSphere MQ's support position on Virtualization, low-level hardware, file systems on networks and high availability. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21392025]\n\n\nThe SPCR tool links to information about the minimum product levels that must be installed before opening a problem report with IBM WebSphere MQ Technical Support. The software versions and any maintenance levels listed in the tool have been explicitly verified as working.\n\n\nSupported System Requirements: \nThe links below are located in the SPCR tool and go directly to the supported operating systems, prerequisites, system requirements, and optional supported software for the specific operating system. \n\n\nWebSphere MQ 8.0\n\nBy Operating System\nAIX [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=AIX]\nHP [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=HP]\nIBM i [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=IBM%20i]\nLinux [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Linux]\n4690 (Managed File Transfer Agent Only) [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Other]\nSolaris [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Solaris]\nWindows [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=Windows]\nz\/OS [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1350550241693&osPlatform=z\/OS]\n\nBy Component\nMQ Advanced Message Security [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568DDB101AEF11E38F7D228059AF1569]\nMQ Client [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_569814401AEF11E38F7D228059AF1569]\nMQ Explorer [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Desktop_56A6BA401AEF11E38F7D228059AF1569]\nMQ Managed File Transfer Agent [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_56910F601AEF11E38F7D228059AF1569]\nMQ Managed File Transfer Service [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568AA6C01AEF11E38F7D228059AF1569]\nMQ Queue Manager [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568C06501AEF11E38F7D228059AF1569]\nMQ Resource Adapter [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Miscellaneous_5685EBD01AEF11E38F7D228059AF1569]\nMQ Telemetry Server [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProductByComponent?deliverableId=1350550241693&duComponent=Server_568CF0B01AEF11E38F7D228059AF1569]\n\nSPCR tool available for all software products:\nThe generic link to the IBM Software Product Compatibility Reports (SPCR) tool is below. You can access the tool for any product and obtain the supported operating systems, system requirements, and optional supported software for your product version. \n\nClick the link below to reach the front page of SPCR:\nDetailed system requirements for a specific product in SPCR [http:\/\/publib.boulder.ibm.com\/infocenter\/prodguid\/v1r0\/clarity\/softwareReqsForProduct.html]\n\nThen choose the following options to obtain the supported operating systems, system requirements, and optional supported software for your product version.\n\n1. Select the desired product.\n2. Select the desired version.\n3. Select your operating system.\n\n----------------------------------------------------------------------------------------------------------------\nIBM WebSphere MQ Advanced entitlement\n\nIBM WebSphere MQ Advanced and IBM WebSphere MQ Advanced Idle Standby grants entitlement to the following components: \n\n * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n\nIBM WebSphere MQ Advanced for Developers grants entitlement to the following components: * IBM WebSphere MQ \n * IBM WebSphere Advanced Message Security \n * IBM WebSphere Managed File Transfer Service \n * IBM WebSphere MQ Telemetry \n * IBM WebSphere Managed File Transfer Managed Endpoint\n\n----------------------------------------------------------------------------------------------------------------"}]},{"id":"TRAIN_Q372","question":"How to fix error CRIMA1217E when upgrade JAZZ from 1.1.0 to 1.1.3 failed?\n\nHow to fix problem when upgrade JAZZ from 1.1.0 to 1.1.3 failed? ","answer":"The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: .\/JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.3.0\/com.ibm.psc.doc\/ref\/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"","is_impossible":false,"contexts":[{"filename":"swg21985946.txt","text":"Title: IBM Upgrading to Jazz for Service Management Version 1.1.3.0 using Installation Manager results in a permission denied error - United States\n\nText:\njazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When upgrading Jazz for Service Management to Version 1.1.3.0 using Installation Manager, the installation fails with the following error:\n\nCannot run program \"\/space\/IBM\/JazzSM\/ui\/bin\/wrapper.sh\" (in directory \"\/space\/IBM\/JazzSM\/ui\/bin\"): error=13, Permission denied [\/space\/IBM\/JazzSM\/install\/tip\/tipWrapp\nerInstall.xml:215] \n\nCAUSE\nDuring the upgrade process the non-root user does not have the correct permissions to run the shell script. This is due to the following:\n1. Jazz for Service Management is installed as a non-root user\n2. Installation Manager is installed in user mode through root user\n\n\nRESOLVING THE PROBLEM\nThe upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: .\/JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.3.0\/com.ibm.psc.doc\/ref\/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"\n\nFor example (showing default installation paths): .\/JazzSMgrpModeUpgrade.sh \"\/home\/root\/IBM\/InstallManager\/\" \"\/opt\/IBM\/JazzSM\/\" \"\/opt\/Download\/dash_upgrade_rsp.xml\"\n\n\nFor IM GUI mode installation, provide the 2 mandatory arguments; IM_Install_Location and JazzSM_Install_Location. \nThis argument combination invokes Installation Manager in GUI mode and lead you through the rest of the upgrade process.\n\nFor IM Silent installation, provide all 3 arguments; IM_Install_Location , JazzSM_Install_Location, and Response_file_with_absolute_Path.\nThis argument combination invokes Installation Manager in silent mode to upgrade JazzSM.\n\nJazzSMgrpModeUpgrade.sh [\/support\/docview.wss?uid=swg21985946&aid=2]JazzSMgrpModeUpgrade.sh [\/support\/docview.wss?uid=swg21985946&aid=1]"}]},{"id":"TRAIN_Q373","question":"RecognizePageFieldsICR_C aborts with Page Type change\n\n\n\nI have an DeveloperWorks application that runs: Survey. In the application PageID Task there is a function that sets the Page Type to ReliefForm (based on a barcode)\n\nDoes anyone know why when I change the SetPageType to set another name, the RecognizePageFieldsICR_C in the Profiler Task aborts? If I put the name back the action runs fine.\n","answer":"In Datacap Studio, set the c_cr variable to USA prior to the call to recognition as follow:\n\nSaveAsCurrentObjVariable(\"c_cr\", \"USA\")\nRecognizeFieldICR_C","is_impossible":false,"contexts":[{"filename":"swg21654520.txt","text":"Title: IBM Datacap Taskmaster Capture ICR error code 12 - United States\n\nText:\nRecognizeFieldICR_C; Recostar; 12 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When performing field level ICR recognition using the action RecognizeFieldICR_C (), the batch aborts with error code 12. \n\nSYMPTOM\nFrom log file:\n\nExecuting 'RecognizeFieldEx' from 'Datacap.Recognition.Recostar.ICRCWrapperClass'. Parameter : <FieldName>\nRecognition return status: 12(Not defined (not used))\n\n\nCAUSE\nThe c_cr variable for ICR_C recognition is not set for the engine.\n\nRESOLVING THE PROBLEM\nIn Datacap Studio, set the c_cr variable to USA prior to the call to recognition as follow:\n\nSaveAsCurrentObjVariable(\"c_cr\", \"USA\")\nRecognizeFieldICR_C"}]},{"id":"TRAIN_Q374","question":"About implementation and specification in a File entry of type Logical under Component\n\nI use Rhapsody for C++ and want to add a .c\/.h file combo.\n\nI know I can easily do this by adding 2 File entries under the Component level: one being Implementation type and the other Specification. Then add the appropriate code in the respective Text Elements.\n\nAlternatively I can do the equivalent by having a single File entry of type Logical that will generate 2 files (and change the CG:ImplementationExternsion property changed to .c).\n\nHowever when the type is set to Logical, I don't know where to place the code for the Implementation and the code for the Specification so that they end up each in the right file. Right now, whatever I put in the Text Element ends up in both files.\n\nDoes anyone know how I can indicate Rhapsody that \"this code is the implementation (.c)\" and \"this code is the specification (.h)\"?\n\n---\n\nRhapsody 8.0.5 for C++ on Windows","answer":"In some cases, you want to import legacy source files into Rhapsody models as external elements. For those externally imported elements (classes and files), Rhapsody doesn't generate code, hence you can preserve legacy code as part of your existing model. However, by default, Rhapsody excludes those external elements from the build even though you turn CG::File::AddToMakefile [File::AddToMakefile] property on.","is_impossible":false,"contexts":[{"filename":"swg21621937.txt","text":"Title: IBM How to include Rational Rhapsody external source files into configuration MakeFile - United States\n\nText:\nexternal; AddToMakefile; build; make; File element; MakeFile; external object; external objects; make file TECHNOTE (FAQ)\n\nQUESTION\n How can you configure the default setting of IBM Rational Rhapsody Developer Edition for C++ (RiC++) in order to include external source files into MakeFile? \n\nCAUSE\nIn some cases, you want to import legacy source files into Rhapsody models as external elements. For those externally imported elements (classes and files), Rhapsody doesn't generate code, hence you can preserve legacy code as part of your existing model. However, by default, Rhapsody excludes those external elements from the build even though you turn CG::File::AddToMakefile [File::AddToMakefile] property on.\n\nANSWER\nFor general information regarding code generation for external elements, see \"Code generation for external elements [http:\/\/pic.dhe.ibm.com\/infocenter\/rhaphlp\/v8\/index.jsp?topic=%2Fcom.ibm.rhp.uml.diagrams.doc%2Ftopics%2Frhp_r_dm_cd_genrtion_extnl_elmts.html]\" topic in Rhapsody Info Center. This technote will provide 3 solutions to allow the inclusion of external elements into the build. \n\n\nSolution 1 - Use Component File element \n\n * \n * \n * Add source file to the build\n * \n\n\nSolution 2 - Use File\/Class element \n\n * \n * \n * \n * \n * Note:\n * \n * \n * \n * \n * Add a Class\/File element to map the external source code into the model. Set property CG::Class::UseAsExternal as \"checked\" for the added element. Set property CG::File::AddToMakefile [File::AddToMakefile] as \"checked\". Set the path to the external file in property CG::Class:FileName to make Rhapsody aware the location of the external source code. The path info would be used in MakeFile generated by Rhapsody.\n \n Note: Both absolute and relative path are supported. Right click the model element, from context menu, click Add New > SourceArtifact.\n \n Note: In order to include this external model element into MakeFile, SourceArtifact is required for the external model element. To enable the display of SourceArtifact, make sure Top Menu > View > Browser Display Options > Show Source Artifacts is checked.\n Make sure the type of added SourceArtifact is set either \"Logical\" or \"Implementation\" (DO NOT choose \"Specification\"). \n Rename SourceArtifact with the name of the external source code (e.g. rename the element to \"hoo\", if the external file name is \"hoo.cpp\"). Click [Elements] tab of the SourceArtifact to make sure the model element is correctly mapped in SourceArtifact. In case of Class, the mapping will be done automatically. For File, manually add its parent element to [Elements] tab as below:\n \n [\/support\/docview.wss?uid=swg21621937&aid=1]\n \n IMPORTANT: You might occasionally find the behavior of File is not consistent with Class. This is because File element is designed to be used as external element only, and not supposed to be built from Rhapsody. You are encouraged to use external Class element in RiC++ model to avoid any confusion you might experience. Generate MakeFile to make sure the external source file (e.g. hoo.obj) file is being added in the build.\n \n\nSolution 3 - Use Additional Sources setting \n\n * \n * \n * [Additional Sources]\n * \n * [Settings]\n * \n * \n \n Note: \n * \n\n\nRELATED INFORMATION\n#Code generation for external elements [http:\/\/pic.dhe.ibm.com\/infocenter\/rhaphlp\/v8\/index.jsp?topic=%2Fcom.ibm.rhp.uml.diagrams.doc%2Ftopics%2Frhp_r_dm_cd_genrtion_extnl_elmts.html]\nAdd source file to the biuld [http:\/\/pic.dhe.ibm.com\/infocenter\/rhaphlp\/v8\/topic\/com.ibm.rhp.uml.diagrams.doc\/topics\/rhp_t_dm_adding_source_files_build.html?resultof=%22%61%64%64%22%20%22%73%6f%75%72%63%65%22%20%22%73%6f%75%72%63%22%20%22%66%69%6c%65%22%20%22%62%75%69%6c%64%22%20]"}]},{"id":"TRAIN_Q375","question":"Where can I find more information about GNU C library (glibc) vulnerability affects IBM DataPower Gateway appliances (CVE-2015-0235)?\n\nI need to understand details regarding GNU C library (glibc) vulnerability affects IBM DataPower Gateway appliances (CVE-2015-0235). ","answer":"CVEID: [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0235]CVE-2015-0235 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0235]\n\n\nDESCRIPTION:The gethostbyname functions of the GNU C Library (glibc) are vulnerable to a buffer overflow. By sending a specially crafted, but valid hostname argument, a remote attacker could overflow a buffer and execute arbitrary code on the system with the privileges of the targeted process or cause the process to crash. This issue is being referred to as the \"Ghost\" vulnerability.\n\n\nCVSS Base Score: 7.6\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100386 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100386]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:H\/Au:N\/C:C\/I:C\/A:C)","is_impossible":false,"contexts":[{"filename":"swg21696640.txt","text":"Title: IBM Security Bulletin: GNU C library (glibc) vulnerability affects IBM DataPower Gateway appliances (CVE-2015-0235) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n GNU C library (glibc) vulnerability that has been referred to as GHOST affects IBM DataPower Gateway appliances. \n\nVULNERABILITY DETAILS\nCVEID: [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0235]CVE-2015-0235 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0235]\n\n\nDESCRIPTION:The gethostbyname functions of the GNU C Library (glibc) are vulnerable to a buffer overflow. By sending a specially crafted, but valid hostname argument, a remote attacker could overflow a buffer and execute arbitrary code on the system with the privileges of the targeted process or cause the process to crash. This issue is being referred to as the \"Ghost\" vulnerability.\n\n\nCVSS Base Score: 7.6\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100386 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/100386]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:H\/Au:N\/C:C\/I:C\/A:C)\n\nAFFECTED PRODUCTS AND VERSIONS\nAll DataPower versions through 6.0.0.11, 6.0.1.7, 7.0.0.4, 7.1.0.2\n\nREMEDIATION\/FIXES\nFix is available in versions 6.0.0.12, 6.0.1.8, 7.0.0.5, 7.1.0.3. Refer to APAR IT06941 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IT06941] for URLs to download the fix. Customers using DataPower firmware version 5.0.x, contact customer support.\n\nIBM recommends that you review your entire environment to identify vulnerable releases of glibc including your Operating Systems and take appropriate mitigation and remediation actions. Please contact your Operating System provider for more information.\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\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 10 Feb 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."}]},{"id":"TRAIN_Q376","question":"Help with Security Bulletin: Vulnerability in Apache Commons FileUpload affects WSRR (CVE-2016-1000031)\n\nI need to understand details regarding Security Bulletin: Vulnerability in Apache Commons FileUpload affects IBM WebSphere Service Registry and Repository (CVE-2016-1000031). Where can I find this information?","answer":"CVEID: CVE-2016-1000031 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in certain products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in 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: See https:\/\/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)","is_impossible":false,"contexts":[{"filename":"swg22010680.txt","text":"Title: IBM Security Bulletin: Vulnerability in Apache Commons FileUpload affects IBM WebSphere Service Registry and Repository (CVE-2016-1000031) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Vulnerability in Apache Commons FileUpload affects IBM WebSphere Service Registry and Repository (CVE-2016-1000031) \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-1000031 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-1000031]\nDESCRIPTION: Apache Commons FileUpload, as used in certain products, could allow a remote attacker to execute arbitrary code on the system, caused by deserialization of untrusted data in 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: See https:\/\/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\nWebSphere Service Registry and Repository V8.5\nWebSphere Service Registry and Repository V8.0\n\nFor unsupported versions IBM recommends upgrading to a fixed, supported version of the product\n\nREMEDIATION\/FIXES\nTo remediate CVE-2016-1000031 you need to apply fixes for both IBM WebSphere Application Server and IBM WebSphere Service Registry and Repository.\n\nFor WebSphere Application Server updates refer to this bulletin:\nSecurity Bulletin: Security vulnerability in Apache Commons FileUpload used by WebSphere Application Server (CVE-2016-1000031) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22011428]\n\nFor WebSphere Service Registry and Repository, this vulnerability has been fixed under APAR IJ01131. Fixes containing IJ01131 have been published and are available from Fix Central.\n\nFor WSRR V8.5 \n\n * Apply V8.5.6.1_IJ01131 [https:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-MultiOS-IFIJ01131]\n \n\nFor WSRR V8.0 * Apply [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+Service+Registry+and+Repository&function=fixId&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085]V8.0.0.3_IV65487_IV79085_IV87422_IV87429_IV89477_IJ01131 [https:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.0.0.3-WS-WSRR-MultiOS-IFIV65487_IV79085_IV87422_IV87429_IV89477_IJ01131]\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 04 January 2018: 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."}]},{"id":"TRAIN_Q377","question":"Help with Security Bulletin: Vulnerability in system log on IBM MQ Appliance WebGUI (CVE-2017-1591)\n\nI need to understand details regarding Security Bulletin: Vulnerability in system log on IBM MQ Appliance WebGUI (CVE-2017-1591). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q378","question":"Help with Security Bulletin: A vulnerability in the GSKit component of IBM MQ Appliance (CVE-2016-0201)\n\nI need to understand details regarding Security Bulletin: A vulnerability in the GSKit component of IBM MQ Appliance (CVE-2016-0201). Where can I find this information? ","answer":"CVEID: CVE-2016-0201 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-0201]\nDESCRIPTION: IBM GSKit could allow a remote attacker to obtain sensitive information, caused by a MD5 collision. An attacker could exploit this vulnerability to obtain authentication credentials.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109310 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109310] 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)","is_impossible":false,"contexts":[{"filename":"swg21974598.txt","text":"Title: IBM Security Bulletin: A vulnerability in the GSKit component of IBM MQ Appliance (CVE-2016-0201) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A vulnerability has been addressed in the GSKit component of IBM MQ Appliance \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0201 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-0201]\nDESCRIPTION: IBM GSKit could allow a remote attacker to obtain sensitive information, caused by a MD5 collision. An attacker could exploit this vulnerability to obtain authentication credentials.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109310 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109310] 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\nIBM MQ Appliance M2000\n\nREMEDIATION\/FIXES\nApply the ifix for APAR IT13023 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/IBM%20MQ%20Appliance%20M2000&fixids=8.0.0.4-IBM-MQ-Appliance-M2000-IT13223&function=fixId&parent=ibm\/WebSphere].\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] IBM WebSphere MQ (CVE-2016-0201) http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21974466 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21974466] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 26 January 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 IBMMQ"}]},{"id":"TRAIN_Q379","question":"Why the tick boxes in 'Subscibed Events' table remain ticked after saving the page\n\nWhen editing a widget and try to unsubscribe the event subscription for 'dataRefresh' events, the checkbox\/tick for \"dataRferesh\" is still selected, even after saving the page. ","answer":"This has been identified as a product defect under APAR IV83442","is_impossible":false,"contexts":[{"filename":"swg21984540.txt","text":"Title: IBM Can't disable DASH TimeSet and dataRefresh in Events configuration - United States\n\nText:\nDASHL2; timeSet; dataRefresh; Events; WIdgets.; Pages TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Any Widget added to a Page after the initial \"Save\" or \"Save and Exit\" will not retain the Events settings when trying to disable the TimeSet and dataRefresh Events in the Edit -> Events pull down configuration window. \n\nSYMPTOM\nTimeSet and dataRefresh Events can't be disabled after any \"Save\" for previous added Widgets on a Page.\n\n\nCAUSE\nThis has been identified as a product defect under APAR IV83442\n\nENVIRONMENT\nAny DASH version, this was a problem since DASH 3.1.0\n\nDIAGNOSING THE PROBLEM\nCreate a Page in DASH, add Widgets then save and exit. Access the Page again, edit the page to add another Widget, Edit the Events in the new Widget then unselect the TimeSet and dataRefresh options. Save the changes.\n\n\nEdit the new Page:\n\n[\/support\/docview.wss?uid=swg21984540&aid=1]\n\nUnselect the TimeSet and dataRefresh options.\n\n[\/support\/docview.wss?uid=swg21984540&aid=2]\n\nAfter a \"save\" or \"save and exit\" you will see that they are enabled again. \n\n\n[\/support\/docview.wss?uid=swg21984540&aid=3]\n\n\nRESOLVING THE PROBLEM\nCurrently, the only workaround is to Place and configure the Events for all widgets wanted on the page before doing first \"Save\" or \"Save and Exit\". All widgets will retain values for subscribed events such as 'dataRefresh' and 'timeSet' \n\nTo use 'dataRefresh' and 'timeSet' properties of subscribed events for any widgets which are added after first \"Save\" or \"Save and Exit\", DASH support will need to be contacted. \n\nNote: This issue is with the widgets which are placed on the page after first \"Save\" or \"Save & Exit\""}]},{"id":"TRAIN_Q380","question":"How do I view Custodian Notes in Atlas Preservation Plan?\n\nHow do I view Custodian Notes in Atlas Preservation Plan? ","answer":"When you click on the Notes tab in a Preservation Plan it only lists the Plan Notes. Click the \"Show Custodian Notes\" button which lists the custodian notes. If you would like to go back to Plan Notes, click the \"Show Plan Notes\" button","is_impossible":false,"contexts":[{"filename":"swg21981880.txt","text":"Title: IBM Viewing Custodian Notes in Atlas Preservation Plan - United States\n\nText:\nAtlas Notes Preservation Plan TECHNOTE (FAQ)\n\nQUESTION\n How do I view Custodian Notes in Atlas Preservation Plan? \n\nCAUSE\nWhen you click on the Notes tab in a Preservation Plan, you see a blank page without any notes listed\n\nANSWER\nWhen you click on the Notes tab in a Preservation Plan it only lists the Plan Notes. Click the \"Show Custodian Notes\" button which lists the custodian notes. If you would like to go back to Plan Notes, click the \"Show Plan Notes\" button"}]},{"id":"TRAIN_Q381","question":"'Use Authorization Group' in user registry\n\nDefined prefix & suffix at 'Static Group' under 'Use Authorization Group' in API Connect manager user registry setting. Error returns when tested. How can I address this?\nError:\n \nLDAP test connection failed. The certification passed but the group authorization failed.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q382","question":"Where to download SPSS Statistics 24.0 Fix Pack 2\n\n\n\nI found the pack from following link: https:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043574\n\nBut where should I download it?","answer":"Log in as a local administrator. \n 2. Download the Fix Pack to a temporary location on your hard drive. \n 3. Ensure that no versions of Statistics are running. \n 4. Run the Statistics 24.0.0.2 Fix Pack executable.\n Note: you must use \"Run as Administrator\" by first right-clicking on the executable. \n 5. Statistics 24.0.0.2 is ready to run. Use the Help -> About menu to verify that 24.0.0.2 is now the installed version.","is_impossible":false,"contexts":[{"filename":"swg24043574.txt","text":"Title: IBM SPSS Statistics 24.0 Fix Pack 2 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This Fix Pack will upgrade your SPSS Statistics 24.0 installation to SPSS Statistics 24.0 FP2 (24.0.0.2) \n\nDOWNLOAD DESCRIPTION\nThis Fix Pack provides important product corrections for SPSS Statistics 24.0.\n\n\nIssues Corrected and Release Note(s): Fix List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27049686]\n\nNOTE: The 24.0.0.2 Fix Pack contains all Interim Fixes made available for 24.0.0.0, as well as other corrected issues, and can be installed over any of the earlier Interim Fixes with no conflict.\n\nPREREQUISITES\nThis Fix Pack is language independent but can only be installed over existing client and server installations of IBM SPSS Statistics 24.0.0.0\n\nINSTALLATION INSTRUCTIONS\n \nInstallation Windows \n\n 1. Log in as a local administrator. \n 2. Download the Fix Pack to a temporary location on your hard drive. \n 3. Ensure that no versions of Statistics are running. \n 4. Run the Statistics 24.0.0.2 Fix Pack executable.\n Note: you must use \"Run as Administrator\" by first right-clicking on the executable. \n 5. Statistics 24.0.0.2 is ready to run. Use the Help -> About menu to verify that 24.0.0.2 is now the installed version.\n\n\nGuidelines for unattended\/pushed installations for Windows-based clients: NOTE: This Fix Pack may require the machine to be rebooted to complete the installation. Please be aware that \"pushing\" the installation in unattended, silent mode may therefore force an unexpected machine reboot on a user, and schedule such installations accordingly. \n\nThe SPSS Statistics 24.0.0.2 for Windows Fix Pack obeys the same rules documented in the Site and Network License Administrator's Guides regarding \"Extracting the Contents of a Downloaded Installer file\" and \"Pushing an Installation to Windows Computers\". \n\nIn this case: \n\n 1. Download the appropriate installer file to a temporary location on your hard drive. \n 2. Open a command window as the local Administrator account and change directory to the temporary download location. \n 3. Extract the \"SPSSStatistics24.0.0.2Patch.msi\" and locale-specific .mst file into a specified location from the downloaded FixPack installer file, \"24.0-IM-S24STATC-<OS>-FP002.exe\",using the documented \"\/b\" switch: 24.0-IM-S24STATC-<OS>-FP002.exe \/b\"c:\\Stats24002FixPack\" (where <OS> is your operating system) \n 4. You can then copy the two extracted files to a network share for easier distribution. \n 5. Install the patch: \n \n msiexec \/i \"c:\\Stats24002FixPack\\SPSS_Statistics_24002_<OS>_Patch.msi\" \/qn \/L*V \"%temp%\\SPSSStatistics24002PatchLog.txt\" PYTHON_EXISTS=\"1\" TRANSFORMS=\"c:\\Stats24002FixPack\\1033.mst\"\n \n (where <OS> is the same operating system specification as in step 3)\n\n\nInstallation Mac \n\n 1. Download and save the Statistics 24.0.0.2 Fix Pack to your local hard drive. \n 2. Ensure that no versions of Statistics are running. \n 3. Execute the Statistics 24.0.0.2 Fix Pack installer from the downloaded .dmg file. \n 4. Statistics 24.0.0.2 is ready to run. Use the About Statistics 24 menu to verify that 24.0.0.2 is the installed version.\n\n\nIBM SPSS Statistics 24 release is supported on Apple Macintosh OS X 10.10.x (Yosemite) through macOS 10.12.x (Sierra) \n\nGuidelines for unattended\/pushed installations for Macintosh-based clients: \n\nIBM SPSS Statistics 24 FixPack 2 for Mac OS X has a silent (push) installer. To install this FixPack on Mac systems, do the following: \n\n 1. Open the 24.0-IM-S24STATC-Mac-Silent-FP002.dmg disk image and copy the two files to your desktop (or any writable location). \n 2. Open a Terminal window and change directories to the location of the patch installer and installer.properties file. \n 3. Edit the installer.properties file to suit your needs. The USER_INSTALL_DIR parameter must be defined. For example, if the current SPSS Statistics 24 install is in the default \/Applications\/IBM\/SPSS\/Statistics\/24, USER_INSTALL_DIR would be:\n USER_INSTALL_DIR=\/Applications\/IBM\/SPSS\/Statistics\/24 \n 4. Uncomment and modify other parameters as needed. \n 5. To execute the installer, use the following command:\n \n .\/SPSS_Statistics_Installer_Silent.bin -f installer.properties\n\n\nInstallation Linux 1. Download the Fix Pack to a temporary location on your hard drive. \n 2. Ensure that no versions of Statistics are running. \n 3. Open a terminal window and execute the 24.0-IM-S24STATC-Linux8664-FP002.bin executable file as the \u2018root\u2019 user. \n 4. Statistics 24.0.0.2 is ready to run. Use the Help -> About menu to verify that 24.0.0.2 is the installed version.\n\n\nGuidelines for unattended\/pushed installations for Linux-based clients: The SPSS Statistics 24.0.0.2 for Linux Fix Pack obeys the same rules documented in the Site and Network License Administrator's Guides regarding \"Running a Silent Installation on Mac and Linux Computers\". \n\nNote: Please contact IBM SPSS Technical Support to obtain the appropriate installer.properties file for the Linux platform. \n\nSPSS Statistics Server - 24.0 FP2 Installation Instructions \n\nInstallation Windows \n\n 1. Log in as a local administrator. \n 2. Download the Fix Pack contents to a temporary location. \n 3. Ensure that the same version of Statistics Server is not running, as multiple versions can be installed on the server. \n 4. Run the Statistics Server 24.0.02 Fix Pack executable. \n Note: you must use \"Run as Administrator\" by first right-clicking on the executable. \n 5. SPSS Statistics Server 24.0.0.2 is ready to run. Check the service name or add\/remove programs, or launch statisticsb and run the SHOW VERSION command to verify 24.0.0.2 as the installed version.\n\n\nInstallation UNIX\/Linux Note: On UNIX and Linux, the Statistics Server upgrade is now a true incremental upgrade and not a complete, fresh installation. Installing the Fix Pack for the appropriate platform should be similar to the instructions for installing your server given in the SPSS Statistics Server Installation Instructions. It is suggested to copy off the spssdxcfg.ini prior to the installation on the UNIX \/ Linux server as the installation may remove the R section in spssdxcfg.ini and may require manual updating after FP2 installation \n\n 1. Download the Fix Pack to a directory on the server machine. \n 2. Shut down Statistics Server prior to applying the Fix Pack. \n 3. You need to ensure the ownership and permissions for the \/bin, \/lib and \/common subdirectories of the Statistics installation directory. For example, if you installed as root, to change the ownership and permissions, go to Statistics installation directory and run the following commands at the UNIX prompt: \n \n chown -R root:root bin lib commonchmod -R 777 bin lib common \n 4. When running SPSS Statistics Server with internal authentication, a regular user can be the owner of these directories. Refer to the SPSS Statistics Server Administrator\u2019s Guide for more information. \n 5. The Fix Pack can be installed silently using the installer.properties file that comes with the 24.0 release (on the DVD): .\/<installer_name> -f installer.properties where <installer_name> is the installer .bin file that you ftp'ed to the server. \n 6. You can also execute the installer directly to launch a graphical version of the installer. (Note: You will need an X Window System to do so): .\/<installer_name>\n Note for graphical installer: You should change the default installer directory for the patch in the Install Wizard to point it to the directory on the server where Statistics Server 24.0 is installed. \n 7. Start the Statistics Server after the Fix Pack installation is complete. \n 8. Run .\/statisticsb and enter SHOW VERSION. The response should indicate 24.00.00.02\n\nDOWNLOAD PACKAGE\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] All packages 9 May 2017 Language Independent 1 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=all] [ ] IBM SPSS Statistics Server 24.0 zLinux Fix Pack 2 9 May 2017 Language Independent 642988 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATS-zLinux-FP002&includeRequisites=1&includeSupersedes=0&download] [ ] IBM SPSS Statistics Server 24.0 pLinux Fix Pack 2 9 May 2017 Language Independent 672373 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATS-pLinux-FP002&includeRequisites=1&includeSupersedes=0&download] [ ] IBM SPSS Statistics Server 24.0 Linux64 Fix Pack 2 9 May 2017 Language Independent 649871 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATS-Linux8664-FP002&includeRequisites=1&includeSupersedes=0&downl] [ ] IBM SPSS Statistics Server 24.0 Win64 Fix Pack 2 9 May 2017 Language Independent 519152 FC [https:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.0&platform=All&function=fixId&fixids=24.0-IM-S24STATS-WIN64-FP001&includeRequisites=1&includeSupersedes=0&downloadM] [ ] IBM SPSS Statistics Server 24.0 AIX Fix Pack 2 9 May 2017 Language Independent 726149 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATS-AIX-FP002&includeRequisites=1&includeSupersedes=0&downloadMet] [ ] IBM SPSS Statistics Client 24.0 Win64 Fix Pack 2 9 May 2017 Language Independent 732557 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATC-WIN64-FP002&includeRequisites=1&includeSupersedes=0&downloadM] [ ] IBM SPSS Statistics Client 24.0 Win32 Fix Pack 2 9 May 2017 Language Independent 706642 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATC-WIN32-FP002&includeRequisites=1&includeSupersedes=0&downloadM] [ ] IBM SPSS Statistics Client 24.0 Mac Fix Pack 2 9 May 2017 Language Independent 565780 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATC-Mac-FP002&includeRequisites=1&includeSupersedes=0&downloadMet] [ ] IBM SPSS Statistics Client 24.0 Mac Silent Fix Pac 9 May 2017 Language Independent 516867 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATC-Mac-Silent-FP002&includeRequisites=1&includeSupersedes=0&down] [ ] IBM SPSS Statistics Client 24.0 Linux64 Fix Pack 2 9 May 2017 Language Independent 651522 FC [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=SPSS&product=ibm\/Information+Management\/SPSS+Statistics&release=24.0.0.1&platform=All&function=fixId&fixids=24.0-IM-S24STATC-Linux8664-FP002&includeRequisites=1&includeSupersedes=0&downl] [ ]"}]},{"id":"TRAIN_Q383","question":"What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed?\n\nWhat could cause problems if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed in CMOD v9.0?","answer":"Issuing the arssyscr -I (instance name) -r command will trigger arssockd to check for the ARSDBBUNDT (RDF tables), which do not exist.","is_impossible":false,"contexts":[{"filename":"swg21672402.txt","text":"Title: IBM What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed? - United States\n\nText:\narssyscr; Report Distribution TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Running arssyscr -I instance_name -r during upgrade without RDF installed or enabled can lead to errors during load. \n\nSYMPTOM\nYou will see errors similar to (depending on database brand) \nDB Error: ORA-00942: table or view does not exist -- SQLSTATE=, SQLCODE=942, File=arsrddb.c, \nLine=951 in your systemlog\n\n\nCAUSE\nIssuing the arssyscr -I (instance name) -r command will trigger arssockd to check for the ARSDBBUNDT (RDF tables), which do not exist. \n\nDIAGNOSING THE PROBLEM\nYou will see the \"table or view does not exist\" errors in your Systemlog\n\nRESOLVING THE PROBLEM\nYou will need to rename the Report Distribution tables and delete the Application, Application Group and Folders by performing the steps below:\n\nYou are going to want to change the Report Distribution table name: \n\nThis test is done on DB2, but It should be the same for (Oracle or SQL \nServer). \nThat is [2] and [3], to rename to object name, you need to log on your \ndatabase command session: \n\n\n[1] Shutdown arssockd \n\n[2] Rename the Application Group name \n\nc:\\>db2 \"select agid, name, agid_name from arsag where name = 'System \nReport Distribution'\" \nAGID NAME \nAGID_NAME \n----------- ------------------------------------------------------------ \n--------- \n5007 System Report Distribution \nSR \n1 record(s) selected. \n\n\nc:\\>db2 \"update arsag set name = 'System Report Distribution DELETE' \nWHERE name = 'System Report Distribution'\" \nDB20000I The SQL command completed successfully. \n\n\n[3] Rename the Folder name \n\nc:\\>db2 \"select name from arsfol where name like 'System Report \nDistribution%'\" \nNAME \n------------------------------------------------------------ \nSystem Report Distribution - Bundles \nSystem Report Distribution - Deliveries \nSystem Report Distribution - Reports \n3 record(s) selected. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Bundles \nDELETE' where name = 'System Report Distribution - Bundles'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - \nDeliveries DELETE' where name = 'System Report Distribution - \nDeliveries'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Reports \nDELETE' where name = 'System Report Distribution - Reports'\" \nDB20000I The SQL command completed successfully. \n\n[3] Start up arssockd \n\n[4] Use the Admin GUI to delete the RD Application group, Applications, \nand Folders"}]},{"id":"TRAIN_Q384","question":"Where do I find list of all document formats indexable and supported by ICC Content Search Services Support (CSSS)?\n\nWhere do I find list of all document formats indexable and supported by ICC Content Search Services Support (CSSS)? ","answer":"Content Search Services uses Oracle Outside In Technology for text conversion. The Indexable document types depend on the version of the Oracle product that is used in Content Search Services in Content Platform Engine. The CSS V5.2.1 uses Outside In V8.4.1\n\nYou can reference this link to check what document types CSS\/Outside In supports: \n\n\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSNW2F_5.2.1\/com.ibm.p8.ce.admin.tasks.doc\/cbr\/csscbr_indexable_documenttype.htm?lang=en","is_impossible":false,"contexts":[{"filename":"swg21978407.txt","text":"Title: IBM File Formats for IBM Content Collector (ICC) Content Search Services Support - United States\n\nText:\nicc; css; csss TECHNOTE (FAQ)\n\nQUESTION\n How do I find list of all document formats supported by ICC Content Search Services Support (CSSS)? \n\nANSWER\nContent Search Services uses Oracle Outside In Technology for text conversion. The Indexable document types depend on the version of the Oracle product that is used in Content Search Services in Content Platform Engine. The CSS V5.2.1 uses Outside In V8.4.1\n\nYou can reference this link to check what document types CSS\/Outside In supports: \n\n\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSNW2F_5.2.1\/com.ibm.p8.ce.admin.tasks.doc\/cbr\/csscbr_indexable_documenttype.htm?lang=en [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSNW2F_5.2.1\/com.ibm.p8.ce.admin.tasks.doc\/cbr\/csscbr_indexable_documenttype.htm?lang=en]"}]},{"id":"TRAIN_Q385","question":"Where in the WAS admin console can I set the java nursery sizes? (-Xmns256M -Xmnx256M)\n\nSo, when GC=GENCON the HEAP gets split up into a nursery and tenured HEAP space. Can I ,in the Admin console, set the nursery size?? In the console, if I go here: A. WAS 8.X where to set these:\n\nServers => Application servers => server_name Now find the \"System Infrastructure\" section -> Java and Process Management -> (Lower right ) -> Process definition -> (Additional Properties section) -> Java Virtual Machine (Right hand side)\nB. Now in the Configuration window I only see the general MIN\/MAX HEAP JVM settings. (These are the (-Xmos756M (Min) -Xmox1024M (Max)) tenured heap settings settings.\n\nShows near bottom I only see: Inital heap size (MIN) Maximum Heap size (MAX)\nHowever, I need to also set the nursery (-Xmns256M -Xmnx256M). How\/where can this get set in the WAS admin console? (I'd rather not try and go hacking through the server.xml file...) I know in WAS 6.1 and 7.X we used to add these java parms in the \"generic JVM arguments\" section or directly into the ..\\WebSphere\\AppServer\\bin\\startServer.bat . However, it looks like some some WAS editions and versions do NOT have the \"Generic JVM arguments\" section on the JVM page. What can you do in this case?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q386","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593)\n\nI need to understand details regarding \"Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593).\" Where can I find information regarding CVE-2014-6593?","answer":"CVEID: 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)","is_impossible":false,"contexts":[{"filename":"swg21962370.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2015-0410 and CVE-2014-6593) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition Version 6 and 7 that are used by IBM Image Construction and Composition Tool. 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 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: \n\n * For IBM Image Construction and Composition Tool v2.2.1.3 * IBM Image Construction and Composition Tool v2.2.1.3 Build 28\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 [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 For IBM Image Construction and Composition Tool v2.3.1.0 * IBM Image Construction and Composition Tool v2.3.1.0 Build 38\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 [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 For IBM Image Construction and Composition Tool v2.3.2.0 * IBM Image Construction and Composition Tool v2.3.2.0 Build 12\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 [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 \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 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 21 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."}]},{"id":"TRAIN_Q387","question":"Why may I receive: Dump Event \"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\" \"Failed to create thread: retVal -1073741830, errno 12\" ?\n\nWhy may I receive: Dump Event \"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\" \"Failed to create thread: retVal -1073741830, errno 12\" ?","answer":"\"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.","is_impossible":false,"contexts":[{"filename":"swg21660890.txt","text":"Title: IBM Using -Xgc:preferredHeapBase with -Xcompressedrefs - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n \"Why does the JVM report a native out-of-memory (NOOM) when using compressed references? I am using a 64bit JVM and I clearly have plenty of memory left. How can I resolve this problem?\" \n\nCAUSE\n \n\n*In this note, please refer to Java Versioning: Java Version.Release.ServiceRelease.FixPack \nex: Java 7.1.4.6 is the same as Java 7.1 SR4 FP6 is the same as Java 7 R1 SR4 FP6. \nThe IBM JVM will automatically use compressed references [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/understanding\/mm_compressed_references.html]when using a maximum heap size less than 25GB. This automated behavior was introduced in Java 6.1.5.0 and Java 7.0.4.0*. Compressed references (CR) decreases the size of Java objects making better use of available memory space. This better use of space results in improved JVM performance. *(Java 7.0.1.1 and later uses compressed references by default on z\/OS) \n\nSee Introducing WebSphere Compressed Reference Technology [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf] for detailed information on how Compressed References work. \n\n\"When using compressed references, the size of the field used in the Java object for the Class Pointer and the Monitor\/Lock is 32 bits instead of the 64bits that would be available in non-compressed mode. Because we are using 32 bits to store the location of these, and they are located in native (non-Java heap) memory, they must be allocated in the first 4GB of the address space - the maximum range we can address with the 32 bits.\" ~IBM Java Development Team \n\nIf the Java heap itself is small (-Xmx), the JVM may allocate it in the lower 4GB of address space along with the Class Pointers and Monitors\/Locks. If these Class Pointers, Monitors\/Locks and Java heap (if included) cannot fit in the lower 4GB, a native out of memory (NOOM) [http:\/\/www.ibm.com\/developerworks\/library\/j-nativememory-linux\/] will be thrown. \nANSWER\nWhy Use Compressed References? \n\nBelow the 4GB mark, the JVM does not have to perform any compression\/decompression of the address pointer at runtime. Therefore, the best performance will be attained if the Class Pointers, Monitors\/Locks and Java heap can all be contained comfortably within the lowest 4GB of the address space. \n\n \n\nDetermining Address Location of Java Heap Memory \n\nTo verify if the Java heap has memory regions below the 4GB mark, check the \"Object Memory\" section in the javacore:\n\nConvert the \"start\" address from the hex value to a GB value [http:\/\/ss64.com\/convert.html]. In the example below, 0x000000000F010000=0.23GB which is below the the 4GB (0x0000000100000000) mark.\n\n\n\n * [\/support\/docview.wss?uid=swg21660890&aid=1]\n\n\nSetting the Preferred Heap Base with -Xgc:preferredHeapBase \n\nStarting with Java 6.1.6.0 and Java 7.0.5.0, and later, the JVM will determine if the Java heap will fit comfortably in the lower 4GB. If it is too large, the JVM will automatically allocate the Java heap above the 4GB mark (APAR IV37797 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IV37797]). \n\n\n\nNOTE: In IBM System z platforms (i.e. z\/OS and z\/Linux), automatic shift of the heap above the 4GB address space does NOT occur because on these platforms, there is an additional performance penalty \nassociated with higher shift values. To resolve Native OOM issues due to a shortage of heap memory in the lower region on z platforms, use -Xnocompressedrefs (see below). \nSee related: IBM Knowledge Center - JVMJ9GC089W [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSYKE2_7.0.0\/com.ibm.java.messages\/diag\/appendixes\/messages\/j9gc\/message_jvmj9gc089.html] However, in earlier Java 6.1 and Java 7.0 versions (earlier than Java 6.1.6.0 and Java 7.0.5.0), if the Java heap can not fit in the lower 4GB, a NOOM will occur. To avoid this problem, the generic JVM argument [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21417365] -Xgc:preferredHeapBase=<address> [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/understanding\/mm_compressed_references.html] can be used to ensure the Java heap is allocated above the 4GB address space. This will leave more room for the Class Pointer and Monitor\/Lock memory. \n\n * \n * \n * \n * \n * \n * \n * This will locate the Java heap starting at the 4GB mark thus leaving the lower 4GB for the other processes.\n\n\nIncrease Maximum Heap Size to Force Heap Allocation Above the 4GB mark \n\nAnother way to ensure that the heap is allocated above the 4GB mark (Java 6.1.6.0 and Java 7.0.5.0 and later) is to set a maximum heap size equal to or greater than 4GB. For example -Xmx4G will ensure that the heap will have to be allocated above the 4GB mark. This will not work in earlier versions of the JVM since these earlier versions allowed the heap to straddle the 4GB mark, placing part of the memory above and some below (fixed as part of APAR IV37797) . \n\n \n\nFurther Investigation \n\nIf after setting -Xgc:preferredHeapBase=<address> or -Xmx4G a NOOM is still encountered (Java 6.1.6.0 and Java 7.0.5.0 and later), then further investigation is required at the application level. Look to decrease the size and usage of the applications Class Pointers and Monitors\/Locks. Additionally, there are some WebSphere Application Server troubleshooting methods that may help reduce the native memory footprint. See: IBM Troubleshooting native memory issues [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=180&uid=swg21373312].\n\nReserving Low-Memory Space with -Xmcrs\n\nIf there is still free memory in the system when a Native OutOfMemory (NOOM) occurs, then the problem may be a shortage of memory in the low-memory region (under 4GB). Even if the Java heap is located above this boundary, other data associated with Java objects can be located in the low-memory region.\n\nThe OS memory allocator will deal out low-memory freely, thus memory resources in the lower boundary may run out. Later when the JVM tries to allocate memory for an artifact which is required to be allocated in low-memory (because the JVM has only reserved a 32bit pointer for it) it fails and throws an OutOfMemoryError.\n\nStarting in Java 6.0.16.3, Java 6.1.8.3, Java 7.0.8.10, Java 7.1.2.10, there is a parameter -Xmcrs [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSYKE2_6.0.0\/com.ibm.java.doc.diagnostics.60\/diag\/appendixes\/cmdline\/xmcrs.html] which allows the JVM to increase the amount of low memory it reserves on startup. With this setting, as long as the low-memory usage by the JVM does not exceed the -Xmcrs value, NOOM in the lower boundary will be avoided.\n\nTo set this parameter, first decide what a reasonable value for your lower memory requirements may be. Reasonable value is unique to each environment so there is not a general recommendation.\n\n\n * -Xmcrs<reasonable_value_for_lower_memory>\n\n * \n * NATIVEMEMINFO subcomponent dump routine\n * \n * \n * \n * \n * \n * \n * \n * \n * [\/support\/docview.wss?uid=swg21660890&aid=2]\n * \n\n\nDisabling Compressed References with -Xnocompressedrefs As a last resort, if the native memory still can not be contained under the 4GB mark, you can set -Xnocompressedrefs [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/appendixes\/cmdline\/Xnocompressedrefs.html] as a generic JVM argument. [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21417365] Using -Xnocompressedrefs will remove the use of compressed references and therefore remove the lower 4GB memory restriction on the Class Pointers and Monitors\/Locks. This will however, result in a significant increase in Java heap memory requirements. It is not uncommon for 70% more heap space to be required. Due to the increased memory requirements it is strongly advised that the Java heap size is adjusted to a larger value and garbage collection is monitored and retuned as required.\n\nAdditionally, some benchmarks show a 10-20% relative throughput decrease when disabling compressed references: \"Analysis shows that a 64-bit application without CR yields only 80-85% of 32-bit throughput but with CR yields 90-95%. Depending on application requirements, CR can improve performance up to 20% over standard 64-bit.\" See:ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf].\n\nBefore using -Xnocompressedrefs as a solution, first rule out the possibility of a native memory leak. Since using -Xnocompressedrefs will allow the the native memory to grow unbounded, a leak in native memory will lead to process size growth eventually leading to a process that needs to be paged out. The paging will incur performance overhead which will eventually lead to an unstable environment. Therefore careful consideration must be used when selecting -Xnocompressedrefs as a solution.\n\n\nMemory Map Considerations \n\nThe below figure is a generalization of how the JVM handles addresses in each section of the memory map based on heap size and compressed references (CR). Please note that at each stage beyond having all of the Java memory contained below the 4GB mark, there will be performance consequences: \n\n\n\n[\/support\/docview.wss?uid=swg21660890&aid=3] \n\nNo Compressed References Overhead using -Xnocompressedrefs \nor\n-Xmx > 25GB -increased memory footprint\n-fewer\/larger objects stored on heap leads to more frequent GC\n-lower cache and translation look aside buffer (TLB) utilization [\/support\/docview.wss?uid=swg21660890&aid=4] Compressed References Overhead maximum heap address used by the Java JVM process is below 4GB none maximum heap address used by the Java JVM process is above 4GB but below 32GB compression\/decompression of address pointers \n\n\nGetting Assistance From IBM Support \nIf further assistance will be required from IBM WebSphere Support, please set the following -Xdump [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/tools\/dumpagents_syntax.html] parameters in the generic JVM arguments [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21417365]: \n * \n * \n * \n\n\nThen restart the JVM and recreate the problem. Once the NOOM is encountered, process the resulting system core with jextract [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21577379]. Send the jextracted core file, heapdump, javacore, snap trace, systemOut.log, native_stderr.log, native_stdout.log and systemErr.log to IBM Support [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21153852] for further analysis. \nRELATED INFORMATION\n Linux\/Windows - Thanks for the memory [http:\/\/www.ibm.com\/developerworks\/library\/j-nativememory-linux\/]\nAIX - Thanks for the Memory [http:\/\/www.ibm.com\/developerworks\/library\/j-nativememory-aix\/]\nIntroducing WebSphere Compressed Reference Technology [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf]\nCompressed references [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/v6r0\/topic\/com.ibm.java.doc.diagnostics.60\/diag\/understanding\/mm_compressed_references.html]\nIBM Java Compressed References and Native OOMs [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/kevgrig\/entry\/ibm_java_compressed_references_and_native_ooms]"}]},{"id":"TRAIN_Q388","question":"How to set database specific custom properties in WebSphere Application Server?\n\nI am using Websphere Application Server (WAS) v8.5.x with Oracle 11.1 JDBC drivers and I want to set some oracle specific properties, when connecting to the database in Websphere Application Server. (specifically: defaultRowPrefetch). How to set such specific properties in Websphere Application Server?","answer":"The way to set this connection property is as follows:. \n\n\n\n\nYou cannot set defaultRowPrefetch as a JVM property. It would have to be named \noracle.jdbc.defaultRowPrefetch for that to work. You can only use this property \nby loading it into a Properties object in the code and then calling \ngetConnection with the Properties object.","is_impossible":false,"contexts":[{"filename":"swg21417765.txt","text":"Title: IBM Configuring defaultRowPrefetch for an Oracle JDBC driver - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The setting defaultRowPrefetch is used to help increase the performance of queries to Oracle databases and we sometimes find customers who want to enable this feature for Oracle database connections to increase the prefetched rows. \n\nOracle JDBC drivers have a feature built in as an extension that allows you to set the number of rows that are prefetched while the full result set is being formulated. This is to reduce the number of trips back and forth to the database. \n\n\nSYMPTOM\nIf defaultRowPrefetch is set as a custom property on the datasource, this will not work as the defaultRowPrefetch is not a datasource property but a property on the connection itself .\n\n\nCAUSE\ndefaultRowPrefetch is a property of the connection and not of the datasource\n\nENVIRONMENT\nWebSphere Application Server using an Oracle JDBC driver\n\nDIAGNOSING THE PROBLEM\nCustomer sets this property and does not see it work. This may result in longer times to getting the full result set and more round trips to the database.\n\nRESOLVING THE PROBLEM\nThe Oracle defaultRowPrefetch can be set in an attempt to speed up queries to a database that return multiple rows. But, it cannot be set as a custom property in a datasource. Please see below:\n\nThe way to set this connection property is as follows:. \n\n\n\n\nYou cannot set defaultRowPrefetch as a JVM property. It would have to be named \noracle.jdbc.defaultRowPrefetch for that to work. You can only use this property \nby loading it into a Properties object in the code and then calling \ngetConnection with the Properties object."}]},{"id":"TRAIN_Q389","question":"What are the supported Macintosh Operating System versions for IBM SPSS Statistics 19, 20, 21, 22 and 23?\n\nI would like to know what are the supported Macintosh Operating system versions for IBM SPSS Statistics versions 18, 19, 20, 21, 22 and 23? ","answer":"Please 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.","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q390","question":"Netcool\/Impact (all versions): DataType incorrect on Secondary\n\n\n\nThe DataType is not being correctly replicated across the ImpactServer Cluster. The .type file of the Secondary ImpactServer configuration is truncated with the error message:\n\nError 500: Mark invalid","answer":"\"a new property is added to increase the file size limit:\n\n\n\n * \n\n\nAdd the property to $NCHOME\/impact\/etc\/<SERVERNAME>_server.props file \nwhere size limit can be 8192, 16384, 32768, etc.. \" \n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact.","is_impossible":false,"contexts":[{"filename":"swg21598417.txt","text":"Title: IBM DataType incorrect on Secondary - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; data; type; datatype; .type; replication; cluster; sync; error; 500; mark; invalid TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The DataType is not being correctly replicated across the ImpactServer Cluster \n\nSYMPTOM\nThe .type file of the Secondary ImpactServer configuration is truncated with the error message: \n\n * \n * \n\n\nCAUSE\nAPAR \"IZ81446: IMPACT 511 CLUSTER UNABLE TO REPLICATE DATATYPES WITH USERPARMETERS VALUES IN EXCESS OF 16,000 CHARACTERS.\" [link below] \n\n\n\n\n\nRESOLVING THE PROBLEM\nAdditional comments associated with APAR IZ81446 release notes: \n\n\n\"a new property is added to increase the file size limit:\n\n\n\n * \n\n\nAdd the property to $NCHOME\/impact\/etc\/<SERVERNAME>_server.props file \nwhere size limit can be 8192, 16384, 32768, etc.. \" \n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact. \n\nThe APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter. \n\nThe character length includes the whole USERPARAMETERS property name as well as the definition. \n\nFor example one would add the property: \n\n * \n\n\nto the files: \n\n * \n * \n * \n\n\nwhere one wished to allow the replication of a DataType between two ImpactServers called NCI1 and NCI2 in a Cluster where the USERPARMETERS property line were 20,000 characters long. \nRELATED INFORMATION\n APAR IZ81446 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IZ81446]"}]},{"id":"TRAIN_Q391","question":"Can an update query be run against the C&DS repository to update job results?\n\nWe have jobs set up in SPSS Deployment Manager. We would like to do a mass change of the location set up on the location set on the location tab.","answer":"The job data is stored as metadata. There is no query or batch process that can be run to do a mass update to change the location of your results tab. The recommendation is to work with your IT administrator to clean up your file system, point your file system to a new location or manually update all of your jobs","is_impossible":false,"contexts":[{"filename":"swg21983638.txt","text":"Title: IBM Can an update query be run against the C&DS repository to update job results? - United States\n\nText:\nmass change query update results TECHNOTE (FAQ)\n\nQUESTION\n We have jobs set up in SPSS Deployment Manager. We would like to do a mass change of the location set up on the location set on the location tab. \n\nCAUSE\nCurrently all results are written to a specific file system and the server is full. We would like to change the location the results of the output. \n\nANSWER\nThe job data is stored as metadata. There is no query or batch process that can be run to do a mass update to change the location of your results tab. The recommendation is to work with your IT administrator to clean up your file system, point your file system to a new location or manually update all of your jobs\n\nRELATED INFORMATION\n Need more help? Our C&DS forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/collaboration.html?smartspace=predictive-analytics]"}]},{"id":"TRAIN_Q392","question":"KD4SoapHeaderV2 in WebServices messages\n\nThe following header appears in the WebServices messages after configuring ITCAM for SOA DC:\n\n<soapenv:Header> <KD4NS:KD4SoapHeaderV2 xmlns:KD4NS=\"www.ibm.com\/KD4Soap\" >AFIAAgAkYzViZmRmOTUtYmY3Mi0zNGY1LWExNDItNTNlMGI3MzUxNmRmACRjYTdmZTQwYi1 mNDFlLTMxNzUtYjExYi04MzY1MmMyMTliNjUABA==<\/KD4NS:KD4SoapHeaderV2> <\/soapenv:Header>\nIs it possible to remove the KD4SoapHeaderV2 header appearing in the WebServices messages after that ITCAM for SOA monitoring has been enabled?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q393","question":"How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width?\n\nHow do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? ","answer":"In Content Navigator v2.0.2 \n\nIn the ..navigator.war\/applets\/filenetViewer_properties.jsp file, set the value of the parameter 'scale' as follows \n\nTo fit content by width, specify - scale: \"ftow\",\nTo fit content by height, specify - scale: \"ftoh\",\n\nHere's another way to modify the behaviour: \n\n * make the same changes above to the filenetViewer_properties.jsp under ECMClient\\configure\\explodedformat\\navigator\\applets folder. \n * Rebuild and redeploy the ear file. \n * Restart the application server\n\n\nSave the changes and they should get picked up when the viewer is re-launched. \n\nIn Content Navigator v2.0.3 \n\nThe same parameter-value pair mentioned above can be added in the Additional Settings section of the Daeja ViewONE panel, of the admin desktop. Add the parameter-value pair to the Additional Settings section of \n\n * the Professional tab for modifying the behaviour of the Daeja Professional viewer \n * the Virtual tab for modifying the behaviour of the Daeja Virtual viewer.\n\n\nClick New in the Additional Settings section to add the parameter-value pair. Save the changes and they should get picked up when the viewer is re-launched.","is_impossible":false,"contexts":[{"filename":"swg21674924.txt","text":"Title: IBM How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? - United States\n\nText:\nfit by height; fit by width; fit; default fit; Daeja viewer; FileNet viewer; Daeja; scale TECHNOTE (FAQ)\n\nQUESTION\n How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? \n\nANSWER\nIn Content Navigator v2.0.2 \n\nIn the ..navigator.war\/applets\/filenetViewer_properties.jsp file, set the value of the parameter 'scale' as follows \n\nTo fit content by width, specify - scale: \"ftow\",\nTo fit content by height, specify - scale: \"ftoh\",\n\nHere's another way to modify the behaviour: \n\n * make the same changes above to the filenetViewer_properties.jsp under ECMClient\\configure\\explodedformat\\navigator\\applets folder. \n * Rebuild and redeploy the ear file. \n * Restart the application server\n\n\nSave the changes and they should get picked up when the viewer is re-launched. \n\nIn Content Navigator v2.0.3 \n\nThe same parameter-value pair mentioned above can be added in the Additional Settings section of the Daeja ViewONE panel, of the admin desktop. Add the parameter-value pair to the Additional Settings section of \n\n * the Professional tab for modifying the behaviour of the Daeja Professional viewer \n * the Virtual tab for modifying the behaviour of the Daeja Virtual viewer.\n\n\nClick New in the Additional Settings section to add the parameter-value pair. Save the changes and they should get picked up when the viewer is re-launched."}]},{"id":"TRAIN_Q394","question":"Why does DSM error log have errors for SQLCODE=-206 errors reported for ISAS core warehouse database?\n\nWhy does DSM error log have errors for SQLCODE=-206 errors reported for ISAS core warehouse database? ","answer":"When you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.","is_impossible":false,"contexts":[{"filename":"swg21983739.txt","text":"Title: IBM Data Server Manager (DSM) showing SQLCODE=-206 \"<name> is not valid in the context where it is used.\" - United States\n\nText:\nSQLCODE 206 -206 SQL0206 SQL0206N DSM incompatible db2level fixpack fix pack db2iupdt TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Data Server Manager log files are full of SQLCODE=-206 \"<name> is not valid in the context where it\nis used.\" error \n\nSYMPTOM\nThe symptoms can vary depending on each installation. \n\nMost common scenario, DSM shows Data Pending status for the monitored database.\n\n\nCAUSE\nWhen you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release. \n\nBut that command does not necessarily update the database system catalog to support the new fix pack that you have installed.\nMeaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level. \n\n\n\nDIAGNOSING THE PROBLEM\nOne way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database: \n\ndb2 \"select versionnumber from sysibm.sysversions order by 1 desc\" \n\nIf the results is showing a lower level than the ones DSM supports, that means your environment\nis not supported, and you are getting the SQLCODE=-206 error.\n\nTo verify what are the DB2 levels supported by DSM, please refer to the links below:\n- System requirements for IBM Data Server Manager, version 1.1.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27045176]\n- System requirements for IBM Data Server Manager, version 2.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27048115]\n\n\n\nRESOLVING THE PROBLEM\nRun the db2updvnn command according to the db2level of your monitored database: \n\n- For DB2 V9.7 run db2updv97 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_9.7.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.1 run db2updv10 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V10.5 run db2updv105 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command\n- For DB2 V11.1 run db2updv111 [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_11.1.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0054449.html] command"}]},{"id":"TRAIN_Q395","question":"Does ITCAM for HTTP Server 7.1 FP4 work with IBM HTTP Server (IHS) 8.5.5.10 on AIX 7.2.x ?\n\nDoes ITCAM for HTTP Server 7.1 FP4 work with IBM HTTP Server (IHS) 8.5.5.10 on AIX 7.2.x ? ","answer":"IBM HTTP Server 8.5.5.9 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.","is_impossible":false,"contexts":[{"filename":"swg27036410.txt","text":"Title: IBM Fix list for IBM HTTP Server Version 8.5 - United States\n\nText:\nFix list Fixlist List of Updates list of defects maintenance refresh pack cumulative fix fix pack fixpack service pack FixListDocument PRODUCT DOCUMENTATION\n\nABSTRACT\nIBM HTTP Server provides periodic fixes for release 8.5. The following is a complete listing of fixes for Version 8.5 with the most recent fix at the top.\n\nCONTENT\n \n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1F4.gif] Back to all versions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27006973] \n\n\nFix Pack 14 (8.5.5.14) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.5D6.gif] Fix Pack 13 (8.5.5.13) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.804.gif] Fix Pack 12 (8.5.5.12) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.9DA.gif] Fix Pack 11 (8.5.5.11) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.B56.gif] Fix Pack 10 (8.5.5.10) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.CD2.gif] Fix Pack 9 (8.5.5.9) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.E48.gif] Fix Pack 8 (8.5.5.8) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.FBE.gif] Fix Pack 7 (8.5.5.7) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1134.gif] Fix Pack 6 (8.5.5.6) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.12AA.gif] Fix Pack 5 (8.5.5.5) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1420.gif] Fix Pack 4 (8.5.5.4) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1596.gif] Fix Pack 3 (8.5.5.3) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.16F8.gif] Fix Pack 2 (8.5.5.2) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.185A.gif] Fix Pack 1 (8.5.5.1) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.19D0.gif] Refresh Pack (8.5.5) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1B46.gif] Fix Pack 2 (8.5.0.2) [https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.1CBC.gif] Fix Pack 1 (8.5.0.1) \n\n\nFix Pack 14 (8.5.5.14) Fix release date: 20 August 2018\nLast modified: 20 August 2018\nStatus: Recommended\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.2186.gif]Download Fix Pack 14 [http:\/\/www.ibm.com\/support\/docview.wss?uid=ibm10719839]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PH01159 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PH01159]\/ UI57810. Back to Top APAR Description PI90598 CVE-2017-12613 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22013598 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22013598] PI94222 Multiple vulnerabilities in GSKit bundled with IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22015347 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22015347] PI95670 Multiple vulnerabilities in IBM HTTP Server (CVE-2017-15710, CVE-2017-15715,CVE-2018-1301)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22015344 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22015344] PI91075 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI91075] Add environment variable to record \"SSLVersion\" failure PI91351 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI91351] Add toleration for TLS certificate extension InhibitAnyPolicy marked as non-critical PI91850 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI91850] MVSDS does not list member contents when using relative generation number to create a member list with PDS\/PDSE GDG (z\/OS only) PI91975 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI91975] The 'Header unset Content-Type' directive does not unset the Content-Type response header. PI92017 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI92017] Include CGI program name when writing stderr to the error log when using mod_cgi PI92053 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI92053] Let child processes avoid graceful shutdown if ECONNREFUSED, ECONNABORTED, ECONNRESET occur during client accept(). PI92092 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI92092] FSUM6245 seen when upgrading IHS to a new fix pack and using an intermediate symbolic link (z\/OS only) PI92407 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI92407] Log startup message for low 64-bit MEMLIMIT PI93212 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI93212] Throttle SSL0600E error messages PI93624 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI93624] Increase default LDAPSharedCacheSize PI94050 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI94050] High CPU\/Hang with IHS mod_auth_basic LDAP PI94539 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI94539] mod_proxy_http does not allow headers larger than 8K bytes. PI95610 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI95610] Namespace collision when mod_ibm_ssl.so is loaded alongside libodr.so. PI95964 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI95964] Add mod_cgi directive to allow users to configure timeouts for CGI applications. PI95983 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI95983] Allow Content-Type to be edited via the Header directive. PI96321 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI96321] Update embedded LDAP SDK to 6.4.x PI97314 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI97314] Add mod_backtrace for Windows \nNote: If the original installation was performed at 8.5.5.11 or earlier, fixpack 8.5.5.14 and later will replace the embedded IBM Java 6 with IBM Java 8.\n\nNote: IBM HTTP Server 8.5.5.14 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.34.\n\nFix Pack 13 (8.5.5.13) Fix release date: 05 February 2018\nLast modified: 05 February 2018\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.2186.gif]Download Fix Pack 13 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24044479]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI93091 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI93091] \/ UI53558. Back to Top APAR Description PI82481 CVE-2017-7679 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22005280 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22005280] PI87445 CVE-2017-9798 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22009782 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22009782] PI87663 CVE-2017-12618 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22009782 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22009782] PI83257 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI83257] Reduce memory usage from long mod_rewrite configurations. PI83350 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI83350] Add jobname and job id to SMF 103 records for IBM HTTP Server (z\/OS only) PI84868 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI84868] Disable the 3DES cipher by default in IBM HTTP Server. PI85478 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI85478] Disable symmetric offload by default when IHS is configured to use a crypto card. PI85561 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI85561] SSL Fallback Protection related errors with SSLProxyEngine ON PI85702 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI85702] SAFRunAs %%CERTIF%% asks for basic auth credentials PI85804 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI85804] Improve password failure error messages in authnz_saf PI88232 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI88232] Allow the server to handle requests with obsolete folds containing only spaces and\/or tabs after PI73984. PI88356 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI88356] Default ciphers with SSLFIPSEnable are System SSL defaults instead of IHS defaults. PI88550 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI88550] Allow IHS instance on z\/OS to swing to an alternate read-only directory. PI88553 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI88553] Print an error message that includes the errno and errno2 values if fail to find a specified saf-group. PI90141 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI90141] IBM HTTP Server may hang at startup on z\/Linux running on z14 hardware - upgrade GSKit to 8.0.50.84 PI90834 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI90834] abendoc4 in apr_pstrcat using saf-change-pw handler (z\/OS only) \nNote: IBM HTTP Server 8.5.5.13 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.34.\n\nFix Pack 12 (8.5.5.12) Fix release date: 21 July 2017\nLast modified: 21 July 2017\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.42FC.gif]Download Fix Pack 12 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24043844]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI84253 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI84253] \/ UI48698. Back to Top APAR Description PI73984 CVE-2016-8743 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21996847 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21996847] PI82260 CVE-2017-3167 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg22005280 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg22005280] PI82263 CVE-2017-7668 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg22005280 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg22005280] PI69182 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI69182] IBM HTTP Server SSL cipher defaults may be displayed incorrectly on z\/OS PI70947 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI70947] Newlines are consumed when an MVSDS dataset's content type is not set to text\/* or application\/x-javascript. PI72027 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI72027] IHS rewrite rule on IPV6 does not redirect correctly. PI72350 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI72350] Fix potential crash in mod_mem_cache in IHS 8.5 and earlier. PI72989 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI72989] Hangs related to mod_backtrace and mod_whatkilledus during a crash. PI73027 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI73027] Crash with combination of mod_net_trace loaded and 'EnableSendfile ON' in httpd.conf. PI73043 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI73043] Upgrade bundled GSKit security library PI73661 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI73661] Session ID Daemon (sidd) memory leak PI73819 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI73819] Allow an extended syntax for the SSLCipherSpec directive on z\/OS (z\/OS only) PI74119 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI74119] Delayed closure of keepalive connections during graceful process termination on z\/OS. (z\/OS only) PI74200 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI74200] Connection resets under heavy load when connecting to IHS on z\/OS. (z\/OS only) PI75341 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI75341] \/server-status doesn't display client IP until first request is read PI76757 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI76757] Allow SSL handshake transcripts to be enabled or disabled PI76874 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI76874] Further enhancements to PI50937 high cpu avoidance PI76918 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI76918] 'Permission denied' errors after maintenance upgrade of IBM HTTP Server on z\/OS (z\/OS only) PI77304 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI77304] VersionInfo shows Java 6 after install of IBM HTTP Server 8.5.5.11 with Java 8.0 PI78442 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI78442] Some sequences of server-side includes mixing '#include virtual=' and '#include file=' result in a HTTP 400 error. PI78767 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI78767] HttpProtocolOptions does not get merged from global to virtualhost scope in 8.5 and earlier. PI78967 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI78967] Allow CEEDUMPS to be requested with kill -USR2 (z\/OS only) PI80187 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI80187] Redirect functionality not working as expected for MVSDS requests (z\/OS only) PI80356 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI80356] Upgrade bundled GSKit security library PI80447 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI80447] Disable MMAP for static files by default on z\/OS (z\/OS only) PI81360 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI81360] Allow SSL_\/TLS_ prefixes to be used interchangeably for cipher long names PI81589 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI81589] Use ECHDE_RSA ciphers by default under TLS1.2 in IBM HTTP Server 8.0 and 8.5 PI81602 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI81602] Issues with updating SAF password when using Firefox or Chrome (z\/OS only) \nNote: IBM HTTP Server 8.5.5.12 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.32, plus some of the security fixes from 2.2.33.\n\nFix Pack 11 (8.5.5.11) Fix release date: 23 December 2016\nLast modified: 23 December 2016\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.7338.gif]Download Fix Pack 11 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24043005]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI73335 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI73335] \/ UI43131. Back to Top APAR Description PI65855 CVE-2016-5387 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21988019 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21988019] PI66849 CVE-2012-0876, CVE-2012-1148, CVE-2016-4472\nexpat vulnerability fixes for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21988026 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21988026] PI66153 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI66153] XML datasets with no XML extension cause error under mod_mvsds (z\/OS only) PI66183 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI66183] When MFA is configured, SAFRunAs fails with a permission error (z\/OS only) PI66695 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI66695] mod_reqtimeout can cause 'java.io.IOException: Async IO operation failed' PI66787 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI66787] Session cache daemon (sidd) memory leak PI66931 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI66931] Upgrade bundled GSKit security library to resolve TLS > 1.2 negotiation intolerance. PI67595 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI67595] AuthSAFExpiration and AuthSAFReenter do not work when using a 401 errordocument (z\/OS only) PI68001 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI68001] Add ability for the MVS stop command to do a graceful shutdown of the server (z\/OS only) PI68803 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI68803] IHS on Z\/OS CPU usage increases in release 8.5.5.5 or beyond (z\/OS only) PI70024 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI70024] Lower message severity to Info for cache return error when connection is aborted for the IBM HTTP Server error logging PI70372 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI70372] mod_mvsds serves a plain text file as an html page if it contains any string starting with a '<' and ending with a '>'. PI70496 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI70496] Startup failures when 'SSLEnable' is specified globally instead of within a VirtualHost. PI70829 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI70829] Provide additional message information for IBM HTTP Server TLS handshakes PI71340 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI71340] Update ikeyman\/gskcmd wrappers for IBM HTTP Server 8.5.5 and 9.0 with embedded Java 8. \nNote: IBM HTTP Server 8.5.5.11 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.\n\nFix Pack 10 (8.5.5.10) Fix release date: 15 August 2016\nLast modified: 15 August 2016\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/0.921A.gif]Download Fix Pack 10 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24042150]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI66501 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI66501] \/ UI39727. Back to Top APAR Description PI63098 CVE-2016-0718 for IBM HTTP Server (Distributed only)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21988026 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21988026] PI53754 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI53754] Using MVSDS to retrieve a GDG(0) always returns the same file, even after a new generation is created. (z\/OS only) PI54415 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI54415] Requests with CONTENT-LENGTH: 0 and any LimitRequestBody may result in a 413 error PI54757 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI54757] Delay allocating an IHS thread until data is available on a new inbound TCP connection. PI54808 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI54808] RewriteRule sees un-decoded characters in URL when mod_authnz_saf loaded (z\/OS only) PI56034 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI56034] No equivalent functionality for DGW ALWAYSWELCOME directive in IHS on z\/OS. PI57543 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI57543] Allow one address space per rotatelogs process to be conserved. (z\/OS only) PI57596 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI57596] CRIHS0001I may contain garbage information or not pick up HTTPS port. (z\/OS only) PI57657 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI57657] INSTCONFPARTIALSUCCESS when the IBM HTTP Server installer cannot determine a local hostname. PI58218 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI58218] IBM HTTP Server 'mod_cache' fixes. PI59374 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI59374] Certificate expiration reporting for IBM HTTP Server. PI59561 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI59561] Add pre\/post password hooks to mod_authnz_saf. (z\/OS only) PI60207 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI60207] Upgrade bundled GSKit security library to 8.0.50.61 (Distributed only) PI60251 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI60251] mod_mvsds writes content as binary instead of text\/plain. (z\/OS only) PI60784 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI60784] IBM HTTP Server directives SSLCipherBan and SSLCipherRequire may crash when GSKit tracing is enabled. (Distributed only) PI62663 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI62663] Some Server Side Includes (SSI) may not be translated as expected (z\/OS only) PI63482 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI63482] Add a private header with password change information for 401 response. PI63682 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI63682] IHS mod_status displays many 'NULL' strings in request column. PI64346 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI64346] SetEnvIf may be skipped with SAF auth enabled (z\/OS only) PI64628 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI64628] IBM HTTP Server on Z\/OS is deleting the wrong IPC message queue (z\/OS only) \nNote: IBM HTTP Server 8.5.5.10 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.\n\nFix Pack 9 (8.5.5.9) Fix release date: 18 March 2016\nLast modified: 18 March 2016\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/1.81E.gif]Download Fix Pack 9 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24041819]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI58575 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI58575] \/ UI35897. Back to Top APAR Description PI52395 CVE-2015-7420 for IBM HTTP Server (GSKit upgrade)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21974507 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21974507] PI54962 CVE-2016-0201 for IBM HTTP Server (GSKit upgrade)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21974507 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21974507] PI40885 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI40885] The 'SAFRunAs' directive implicitly requires access to the \"OMVSAPPL\" class in some RACF configurations (z\/OS only)\n{The initial fix was in 8.5.5.7, but was not effective until additional updates in this fixpack.} PI47828 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI47828] IBM HTTP Server on z\/OS fails to start with CC=0137 and ABENDU4093 RC00000281 (z\/OS only) PI48695 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI48695] DGW compatibility for CGI query strings and syntax in server-side includes. (z\/OS only) PI49165 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI49165] Add new request time logging formats PI49473 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI49473] IBM HTTP Server mod_filter is unable to process pages with error response codes returned from WebSphere Plugin PI49718 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI49718] Improve error_log reporting for 'SSLProxyEngine' handshake errors PI49791 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI49791] Add the IfFile directive to allow processing directives based on file existance. PI50376 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI50376] DGW compatibility for DOCUMENT_* CGI variables. (z\/OS only) PI50397 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI50397] No error log entries for 'SAFRunAs %%CERTIF_REQ%%' failures. (z\/OS only) PI50514 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI50514] SSL session ID cache daemon (SIDD) creates unnecessary entries PI50937 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI50937] Alleviate looping between SSL and GSKit (IBM Global Security Kit) PI51185 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI51185] Enhancements allowing use of SAFRunAsEarly for certificate switching PI52299 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI52299] TLS_FALLBACK_SCSV support for IBM HTTP Server \nNote: IBM HTTP Server 8.5.5.9 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.\n\nFix Pack 8 (8.5.5.8) Fix release date: 11 December 2015\nLast modified: 11 December 2015\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/1.260A.gif]Download Fix Pack 8 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24041178]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI52859 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI52859] \/ UI33171. Back to Top APAR Description PI45005 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI45005] Use of SAFRunAs %%CLIENT%% can result in ICH408I messages to be issued against the HTTP Server userid PI45562 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI45562] Add a message to indicate the IBM HTTP Server is ready PI45740 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI45740] Encoding error on RewriteRule PI46559 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI46559] The setupadm script on Linux fails to use an existing group without the -create parameter PI46616 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI46616] Allow RewriteRule to use colon (':') in header names and values PI46868 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI46868] REXX CGI'S may display as text in the browser PI47198 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI47198] IHS caching partial response for chunked responses PI47605 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI47605] Support -t -DDUMP_SSL_CONFIG and -t -DDUMP_SSL_CIPHERS on Microsoft Windows PI47642 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI47642] Honor a global LogLevel specified after a virtual host definition that does not explicitly set LogLevel \nNote: IBM HTTP Server 8.5.5.8 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.\n\nFix Pack 7 (8.5.5.7) Fix release date: 11 September 2015\nLast modified: 11 September 2015\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/1.3AAC.gif]Download Fix Pack 7 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040533]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI47832 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI47832] \/ UI30752. Back to Top APAR Description PI39833 CVE-2015-1829 for IBM HTTP Server on Windows\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21959081 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21959081] PI42928 CVE-2015-3183 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21963361 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21963361] PI44793 CVE-2015-4947 for IBM HTTP Server Administration Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21965419 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21965419] PI44809 CVE-2015-1788 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21963362 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21963362] PI45596 CVE-2015-1283 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21964428 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21964428] PI38322 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI38322] Allow mod_cache to ignore an 'Authorization' HTTP request header PI38562 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI38562] CGI resources are briefly unavailable just after a restart PI38828 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI38828] Enable unified config dump PI38835 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI38835] IBM HTTP Server cannot log time-to-first-byte (TTFB) PI39439 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI39439] DGW-style SSL environment variables are not set PI40952 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI40952] Preserve quoting in SSLServerCert directive \nNote: IBM HTTP Server 8.5.5.7 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.31.\n\nFix Pack 6 (8.5.5.6) Fix release date: 26 June 2015\nLast modified: 26 June 2015\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/2.512.gif]Download Fix Pack 6 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040035]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI43067 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI43067] \/ UI28569. Back to Top APAR Description PI36417 CVE-2015-0138 for IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21698959 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21698959] PI34229 Disable RC4-based TLS ciphers by default in IBM HTTP Server.\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21701072 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21701072] PI32452 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI32452] Userid on 'require saf-user' statement doesn't work when specified as lower case (z\/OS only) PI32841 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI32841] Some cipher names and keysizes are not logged when using %(SSL_CIPHER)e in LogFormat for access log. PI33039 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI33039] EDC5170I error happens when running CGI script in Apache server with WLM enabled on z\/OS PI33527 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI33527] SSLOCSPEnable directive always enables OCSP (Online Certificate Status Protocol) even if value is 'OFF'. PI34017 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI34017] HTTP error 413 on static files results in a duplicate error message. PI35073 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI35073] IBM HTTP Server always supplies its own HTTP 'DATE' header to responses generated by the WebSphere webserver plug-in. PI35219 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI35219] ABEND0C1 when running install_ihs on z\/OS PI35519 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI35519] cgiparse incorrectly handles POST request bodies on z\/OS PI39284 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI39284] Error continues to appear in HAPALLO2 JCL after PI25264 (z\/OS only) \nNote: IBM HTTP Server 8.5.5.6 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.29.\n\nFix Pack 5 (8.5.5.5) Fix release date: 13 March 2015\nLast modified: 13 March 2015\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/2.1D4A.gif]Download Fix Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24039425]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI36674 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI36674] \/ UI25968. Back to Top APAR Description PI31516 CVE-2014-8730: Enable strict CBC padding checks on TLS connections\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21697368 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21697368] PI28735 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI28735] ErrorDocument redirection for status code 414 (Request URI too long) does not work PI30041 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI30041] mod_deflate_z gives no indication if hardware offload was used (z\/OS only) PI30093 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI30093] Allow SSLProtocolDisable, SSLProtocolEnable, and SSLAttributeSet in the IBM HTTP Server configuration global PI30323 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI30323] Add support for dual-mode ECDSA\/RSA SSL virtual hosts PI31566 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI31566] Allow IBM HTTP Server RLimit* directives to reduce hard limits PI31802 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI31802] APR_POLLSET_ADD failure - ERRNO2=0X76650000 (z\/OS only) \nNote: IBM HTTP Server 8.5.5.5 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.29.\n\nFix Pack 4 (8.5.5.4) Fix release date: 08 December 2014\nLast modified: 08 December 2014\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/2.2EE8.gif]Download Fix Pack 4 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24038539]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI30622 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI30622] \/ UI23545. Back to Top APAR Description PI22070 Multiple Apache web server vulnerabilities:\nCVE-2014-0118 (mod_deflate), CVE-2014-0226 (mod_status), CVE-2014-0231 (mod_cgid), CVE-2013-5704 (core)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21690185 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21690185] PI27904 IBM HTTP Server should disable weak SSL protocols and ciphers by default PI19013 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI19013] Missing version.signature file after the installation of Apache HTTP Server -FMID HHAP85P\n(z\/OS only) PI19580 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI19580] mod_reqtimeout: Potential for unexpected timeouts in IBM HTTP Server 8.5.5 on z\/OS when using RequestReadTimeout (z\/OS only) PI19581 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI19581] IBM HTTP Server modules specified without a path don't load PI21655 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI21655] mod_mvsds: 404 returned when attempting to browse a member of a PDS dataset using MVSDS (z\/OS only) PI23005 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI23005] Allow logging of time taken during SSL handshake PI24257 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI24257] 'Header edit* ...' directive not accepted by IBM HTTP Server PI24424 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI24424] Add support for zEnterprise Data Compression (zEDC) offload for IBM HTTP Server. (z\/OS only) PI24782 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI24782] mod_smf module only writes smf type 103 subtype 14 records when debug is turned on. (z\/OS only) PI24990 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI24990] Add mpmstats info to console. (z\/OS only) PI25124 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI25124] Install of PTF UI20159 does not update product files 14\/09\/19 PTF PECHANGE (z\/OS only) PI25264 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI25264] Error appears in HAPALLO2 JCL (z\/OS only) PI25783 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI25783] Fatal getpwuid() error at IBM HTTP Server startup (z\/OS only) PI26507 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI26507] mod_proxy on z\/OS doesn't try IPV4 addresses on systems where IPV6 connections fail (z\/OS only) PI26894 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI26894] Increase security libraries to resolve high CPU loop on 64bit Microsoft Windows\n(GSKit upgrade to 8.0.50.34) \nNote: IBM HTTP Server 8.5.5.4 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.29.\n\nFix Pack 3 (8.5.5.3) Fix release date: 18 August 2014\nLast modified: 18 August 2014\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/3.134.gif]Download Fix Pack 3 \n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI21538 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI21538] \/ UI20159. Back to Top APAR Description PI13028 CVE-2014-0098: mod_log_config - Potential denial of service vulnerability\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249] PI17025 CVE-2014-0963: IBM HTTP Server high CPU utilization with SSL (includes GSKit upgrade)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249] PI19700 CVE-2014-0076: Local side-channel attack on ECDSA (GSKit upgrade)\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21681249] PI13422 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI13422] Memory leak in GSKit 8.0.50 (GSKit upgrade) PI13949 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI13949] MVSDS request does not release shared ENQ (z\/OS only) PI14451 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI14451] IHS with SSLFIPSENABLE reports error code 53817451 at startup (z\/OS only) PI15344 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI15344] IBM HTTP Server caching issues PI16599 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI16599] Authentication failure gives LDAP error for non-LDAP configurations PI17434 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI17434] SSLCACHE may fail due to SSLCACHEPORTFILENAME value being in use (z\/OS only) \nNote: IBM HTTP Server 8.5.5.3 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.27.\n\nFix Pack 2 (8.5.5.2) Fix release date: 28 April 2014\nLast modified: 28 April 2014\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/3.144E.gif]Download Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037250]\n\nThis fixpack is delivered for IBM Ported Tools on z\/OS using APAR\/PTF: PI15962 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI15962] \/ UI17041. Back to Top APAR Description PI05309 CVE-2013-6329: SSL session resumption vulnerability. (GSKit upgrade).\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554] PI09345 CVE-2013-6438: Potential Denial of Sevice in mod_dav for IBM HTTP Server.\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554] PI09443 CVE-2013-6747: GSKit Certificate Chain Vulnerability. (GSKit upgrade).\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21669554] PM94008 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM94008] Timed-out ldap bind and search failures on reused connections are not retried. PM94143 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM94143] Use of SAFRunAs results in ICH408I messages to be issued against the HTTP Server userid (z\/OS only) PM94602 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM94602] ProxyRemote fails to work with SSL requests PM96039 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM96039] AcceptEx disablement notice should not appear in Microsoft Windows Event Viewer PM97650 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM97650] IBM HTTP Server does not send SIGTERM to fastCGI application PI04922 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI04922] IBM HTTP Server scaling\/processing threads limited on 64-bit Microsoft Windows. PI06366 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI06366] IBM HTTP Server thread creation failures when scaling up from default configuration on RHEL6 PI07665 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI07665] IBM HTTP server 8.5 (Apache) on z\/OS needs support of cgiparse and cgiutils from IHS 5.3 Domino Go Web Server. PI08502 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI08502] Potential heap corruption under load for IBM HTTP Server with SSL enabled. (GSKit upgrade). PI08715 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PI08715] Potential mod_proxy crashes under load PI09344 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PI09344] Missing version.signature file for 31-bit IBM HTTP Server on z\/OS breaks 8.5.5 post-update process. \nNote: IBM HTTP Server 8.5.5.2 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.26.\n\nFix Pack 1 (8.5.5.1) Fix release date: 11 November 2013\nLast modified: 11 November 2013\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/3.2EF8.gif]Download Fix Pack 1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035935] Back to Top APAR Description PM87808 CVE-2013-1862: mod_rewrite vulnerability\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21651880 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21651880] PM89996 CVE-2013-1896: mod_dav vulnerability\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21651880 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21651880] PM84215 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM84215] mod_mpmstats may report incorrect values during startup or shutdown PM87247 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM87247] Additional certificate attributes are needed as fields accessible to the SSLClientAuthRequire directive PM89422 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM89422] IHS WebDAV requests slow on Windows PM91704 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM91704] Add mod_smf module for IBM HTTP Server (z\/OS only) PM92105 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM92105] wlm enclave support fails on a child process without a unique jobname (z\/OS only) \nNote: IBM HTTP Server 8.5.5.1 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.25.\n\nRefresh Pack (8.5.5) Fix release date: 14 June 2013\nLast modified: 14 June 2013\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/3.401C.gif]Download Refresh Pack 8.5.5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034969] Back to Top APAR Description PM85211 CVE-2013-0169: TLS Vulnerability (The fix upgrades the bundled GSKit security library) \nhttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/81902 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/81902] \nNote: IBM HTTP Server 8.5.5 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.24.\n\nFix Pack 2 (8.5.0.2) Fix release date: 15 April 2013\nLast modified: 15 April 2013\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/3.479A.gif]Download Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034672] Back to Top APAR Description PM76110 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM76110] CVE-2012-4557: mod_proxy_ajp incorrectly marks backend WAS CE server down PM80058 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM80058] CVE-2012-3499\/CVE-2012-4558: Potential exposure in several IBM HTTP Server optional modules\nhttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/82359 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/82359]\nhttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/82360 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/82360] PM68347 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM68347] Z\/OS IHS config for versions prior to 8.5 may not migrate as expected to 8.5 PM69188 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM69188] Installation of IBM HTTP Server V8.5 completes with a warning. Failure occurs because the system's hostname is not set. PM70591 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM70591] IHS on Microsoft Windows startup failure with SSLv3Timeout or SSLv2Timeout in vhost: 'master_main: create child process failed.' PM70994 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM70994] SSLFakeBasicAuth depends on LoadModule order PM71102 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM71102] <Location> settings don't affect some mod_negotiation generated content PM73304 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM73304] Add mod_ssl's SSLProxyCheckPeerCN to IBM HTTP Server PM75876 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM75876] The 'Header' directive can't set a header only if the header is absent, even when using 'EDIT' mode or relying on other modules. PM77980 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM77980] IBM HTTP Server should not add the Server: header by default PM78087 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM78087] IBM HTTP Server high memory use when many hundreds of RewriteCond %{REQUEST_URI} PM78144 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM78144] IBM HTTP Server large logformats cannot be correctly logged by piped loggers PM78434 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM78434] Provide end-to-end timeouts for SSL handshakes PM79015 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM79015] mod_disk_cache on Windows gives error: '(OS 5) Access is denied: disk_cache: Rename tempfile to datafile failed' PM80235 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM80235] NIST SP800-131a support for IBM HTTP Server PM80260 [http:\/\/www.ibm.com\/support\/docview.wss?uid=isg1PM80260] apr_pollset_add failure -errno2=0X11780494, or growing CPU usage on the listener thread in IHS child processes (z\/OS only) \nNote: IBM HTTP Server 8.5.0.2 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.24.\n\nFix Pack 1 (8.5.0.1) Fix release date: 29 October 2012\nLast modified: 29 October 2012\nStatus: Superseded\n\n[https:\/\/www-prd-trops.events.ibm.com\/sites\/default\/files\/support\/swg\/swgdocs.nsf\/0\/88423a02b4f66c1385257a99006a3c24\/Content\/4.19D4.gif]Download Fix Pack 1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24033606] Back to Top APAR Description PM66218 Upgrade bundled GSKit security library\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21614265 [http:\/\/www-01.ibm.com\/support\/docview.wss?&uid=swg21614265] PM66470 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM66470] CVE-2012-2687: mod_negotiation - potential information disclosure on compromised site. PM72915 TLS compression should be disabled by default in IBM HTTP Server\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21611881 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21611881] PM62011 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM62011] mod_log_config: The wrong cookie can be logged PM63634 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM63634] admin.passwd file was reset after installing fixpack PM68007 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM68007] Non-root IBM HTTP Server install fails if primary group has no name PM71612 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PM71612] Additional non-serviceable files added for IBM HTTP Server \nNote: IBM HTTP Server 8.5.0.1 contains all applicable security fixes in Apache HTTP Server versions up through 2.2.23."}]},{"id":"TRAIN_Q396","question":"Can I obtain latest version WorkPlace(AE)'s source code?\n\nCan I obtain latest version WorkPlace's source code? ","answer":"The IBM FileNet P8 Workplace Source Code is distributed under an IBM Source Code License. You must review and accept the terms of the license when you download the source. The license text is attached to this technote for your convenience.","is_impossible":false,"contexts":[{"filename":"swg21327685.txt","text":"Title: IBM Obtaining FileNet Workplace Source Code - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I obtain source code for IBM FileNet P8 Workplace? \n\nCAUSE\nn\/a\n\nANSWER\nOBTAINING IBM FILENET P8 WORKPLACE SOURCE CODE \n\n\n_______________________________________________________\n\nThe IBM FileNet P8 Workplace Source Code is distributed under an IBM Source Code License. You must review and accept the terms of the license when you download the source. The license text is attached to this technote for your convenience.\n\nDIRECTIONS\n\n1. Complete the questionnaire below and answer all questions.\n2. Review the attached license. You will agree to this license when you download the software.\n3. Open a support ticket PMR, copy your answers to the questionnaire to the PMR, and ask L2 to open a CRM to review and approve the request.\n4. Upon review and approval by L3, L2 will be sent instructions where the customer may download the source.\n\n\nQUESTIONNAIRE\n\n1.) Name: _____________________________________\n\n2.) Company Name: ______________________________\n\nICN (IBM Customer Number, 7 digits): __________________________\n\n3.) How would you describe the type of users for whom you are building your application? \n[ ] Business Analyst \n[ ] Administrator,\n[ ] Business User,\n[ ] General User, \n[ ] Other ______________________________________.\n\n4.) Please describe how Workplace will be used in your organization.\n_______________________________________________________________________________________\n\n_______________________________________________________________________________________\n\n_______________________________________________________________________________________\n\n_______________________________________________________________________________________\n\n5.) Why do you want to customize Workplace?\n[ ] Current user interface is too difficult to use\n[ ] Desire to simplify\/reduce existing functionality for your end users\n[ ] Desire to change the look and feel to match corporate identity\n[ ] Require different functionality based on organizational roles\n[ ] The following functionality is not available in Workplace:\n__________________________________________________________\n\n6.) If you plan on reusing Workplace UI components to build a custom application, which components will you reuse or modify?\n[ ] Add\/Check In Wizards \n[ ] Property Page\n[ ] Security Page\n[ ] Search Page\n[ ] Search Results\n[ ] List View\n[ ] Select Object\n[ ] Publish Page\n[ ] In Box List View\n[ ] Public In Box List View\n[ ] eforms\n[ ] Form Policies\n[ ] Entry Templates\n[ ] Other __________________________________\n\n7.) If you are planning to roll out Workplace as is but require minor customization, what are you planning to customize? \n[ ] Wizards \n[ ] Property Pages\n[ ] Search Page\n[ ] Search Operators\n[ ] Search Results \n[ ] Actions \n[ ] List view\n[ ] Login Behavior\n[ ] Color schemes\n[ ] Logos\/Images\n[ ] Java Viewer\n[ ] Other _____________________________\n\n7.) Have you evaluated IBM Content Navigator as a replacement for the AE Workplace UI? [ ] Yes [ ] No \n\n8.) There may be other options for building custom applications. Would you like to be contacted to further discuss? [ ] Yes [ ] No \n\nAdditional Comments? (Optional)\n\n_______________________________________________________________________________________\n\n_______________________________________________________________________________________\n\n_______________________________________________________________________________________\n\n______________________________________________________________________________________\n\nLA_en.rtf [\/support\/docview.wss?uid=swg21327685&aid=2] [\/support\/docview.wss?uid=swg21327685&aid=1]"}]},{"id":"TRAIN_Q397","question":"Will Web GUI for Netcool\/OMNIbus Be Affected by the Up Coming Leap Second?\n\nAs Januaray 01 2017, a Leap Second will be added to adjust the time. We would like to know if this one second adjustment will have an affect on WebGUI for Netcool\/OMNIbus. ","answer":"The addition of Leap Second has no impact to WebGUI functionality. Therefore, preventive maintenance is not necessary.","is_impossible":false,"contexts":[{"filename":"swg21700534.txt","text":"Title: IBM Impact of the addition of Leap Second time on WebGUI - United States\n\nText:\nadjust; timezone; tz TECHNOTE (FAQ)\n\nQUESTION\n What is the impact of the addition of Leap Second on WebGUI? \n\nCAUSE\nEvery few years, a one-second adjustment is added to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time.\n\nANSWER\nThe addition of Leap Second has no impact to WebGUI functionality. Therefore, preventive maintenance is not necessary."}]},{"id":"TRAIN_Q398","question":"Cannot create syndication pair between Virtual Portals with a different user repository than Base Portal\n\n\nSteps:\n\nI have two different user repositories one to manage my base portal and Virtual Portals. (p.e: For Base Portal I use ITDS, and for VPs I use AD) with differents admin users each.\n\nThen I created two VPs using the AD repository, and my VPs admin user on the credential vault.\n\nTried to create a syndication relationship , that is failing with the error:\n\n\"Could not communicate with the target URL. Please check that the Syndicator URL details are entered correctly, and that the credential slot user exists on the target server.\"","answer":"The Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.","is_impossible":false,"contexts":[{"filename":"swg21681464.txt","text":"Title: IBM Syndicating to VP with exclusive realms does not work. - United States\n\nText:\nsyndication; realm; vp; admin user; getPortalAdministrator TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\n \n\nSyndication from base Portal to Virtual Portal with different realms does not work:-\n\n1) Create 2 different realms with different base entries and map one realm ( with base entry e.g DC=org1,DC=test) to base Portal.\n\n2) Create a Virtual portal and map it to another realm ( with base entry e.g DC=org2,DC=test).\n\n3) Attempt to carry out syndication from Base Portal to Virtual Portal.\n\n4) The syndication fails with below exception:\n\n[datetime] 0000007f PackageGenera I createIceProjectItemRemoves():: p_items length = 0 \n[datetime] 0000008b ResponseBL I Performing response for sender: 1abc2a07-e70a-4804-8e09-b7b897eef534\n[datetime] 000000a1 SubscriberTas E Unexpected exception thrown while updating subscription: [IceId: <1abc2a07-e70a-4804-8e09-b7b897eef534> Current State: <ICE-INITIAL>], exception: com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST com.presence.connect.wmmcomms.exception.MemberNotFoundException: Message: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST, Cause: com.ibm.wps.um.exceptions.impl.MemberNotFoundExceptionImpl: com.ibm.portal.WpsException: EJPSG0002E: Requested Member does not exist.uid=wpsadmin,cn=users,DC=XYZ,DC=TEST\n[...]\nat com.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator(UserManagementServiceImpl.java:1678)\n[...]\n\n\nCAUSE\n\nThe Admin user exists on Base Portal but not the Realm which is configured to Virtual Portal.\n\nThe Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() does not have access to the Virtual Portal.\n\n\nRESOLVING THE PROBLEM\n \n\nThe Admin user has to be made visible on both base and virtual Portals if you wish to syndicate between the two.\n\nWhen syndicating to Virtual Portals, the Administrator User who is listed as the Domain Admin retrieved with:\ncom.presence.connect.wmmcomms.UserManagementServiceImpl.getPortalAdministrator() should have access to the Virtual Portal.\n\nRELATED INFORMATION\n Realm Support [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/xpDocViewer.xsp?lookupName=IBM%20WebSphere%20Portal%208%20Product%20Documentation&documentId=3B264D090122D90D85257B26000692C6&action=openDocument&rev=true&mode=original&content=pdcontent]"}]},{"id":"TRAIN_Q399","question":"Business Rules with Message Broker\n\n I want to know if there is a way to use a business rule approach with Message Broker. Because I want to take advantage about benefits for using it, like if they(rules) are not embedded in code, they can be reused and shared, even though application is retired.\n\nI have heard about some rules engine like Drools. Is it possible to do this merge with Message Broker or this has its own rules engine? Where can I go to search for information about this?","answer":"This SupportPac provides a node to execute the J2SE rule execution server (RES) of WebSphere Operational Decision Management inside the WebSphere Message Broker JVM.","is_impossible":false,"contexts":[{"filename":"swg24032010.txt","text":"Title: IBM IAM9: Message Broker \u2013 WebSphere Decision Service Node - United States\n\nText:\niam9; JRules; Decision Management; Rule Engine; ILog DOWNLOADABLE FILES\n\nABSTRACT\n This SupportPac provides a node to execute the J2SE rule execution server (RES) of WebSphere Operational Decision Management inside the WebSphere Message Broker JVM. \n\nDOWNLOAD DESCRIPTION\nThis SupportPac provides a WebSphere Decision Service Node in WebSphere Message Broker to run a J2SE runtime business rules engine that can process rules based on the business content from messages within message broker flows. The runtime rules engine can come from the WebSphere Operational Decision Management (WODM). The node receives a input message, extracts the rule set parameter and then runs the rule engine. The result is sent to the output terminal and can be used for complex routing and decision making. \n\nThe SupportPac makes existing custom integrations between WebSphere Message Broker and WebSphere Operational Decision Management simpler to implement.\n\nThe SupportPac is delivered as a User Defined Node added to the Message Broker Toolkit palette. \n\u2022 WebSphere Message Broker v7, v8, v9 with IAM9 node v1 SupportPac with ODM v7, v7.5 and v8.\n\u2022 WebSphere Message Broker v7, v8, v9 with IAM9 node v2 SupportPac with ODM V8.0.1 and 8.5.\n\nPossible Uses\nDecision Service node can be used for:\n\u2022 Complex flow decisions by rule.\n\u2022 Content based routing by rule.\n\nNew in this Release\n\u2022 Provide a node implementation for all ODM releases currently available.\n\u2022 Change the user interface and input to look similar to the decision service node of IBM Integration Bus (formerly known as WebSphere Message Broker) v9.\n\u2022 Enable Decision Warehouse.\n\u2022 Provide Local Environment Structure to set rule set path and rule set parameters.\n\nDetails\nAuthor: Jochen Benke, IT Specialist, Software Services for WebSphere (ISSW)\nCategory: 2\nReleased: 27Mar12 \nLast updated: 28Aug13\nCurrent SupportPac Version: 2.0\n\u00bbPlease note that the version number shown in the right-hand pane is the version of the WebSphere MQ or WebSphere MB product that this SupportPac applies to. The date is the last web page refresh. \n\nTo view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage. [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=171&uid=swg27007205]\n\nPREREQUISITES\nWebSphere Message Broker V7.0 or later\nWebSphere ILOG BRMS V7.1 or later\nWebSphere Operational Decision Management V7.5 or later\n\nINSTALLATION INSTRUCTIONS\nSee Node documentation below.\n\nURL LANGUAGE SIZE(Bytes) iam9.pdf [ftp:\/\/public.dhe.ibm.com\/software\/integration\/support\/supportpacs\/individual\/iam9.pdf] US English 789266 \nDOWNLOAD PACKAGE\n\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options iam9.zip 28 Aug 2013 US English 546661 HTTPS [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/preLogin.do?source=swg-mbwdsn] \nTECHNICAL SUPPORT\n Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels. \n\nYou may submit a question using the 'rate this page' below but a response is not guaranteed.\n\nPlease read the license information contained within the zip file of this SupportPac to determine if you want to use it. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Not Applicable 8.5, 8.0.1, 8.0, 7.5 Business Integration WebSphere ILOG JRules Not Applicable 7.1"}]},{"id":"TRAIN_Q400","question":"Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235)\n\nI need to understand details regarding Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235). Where can I find this information?\n","answer":"CVEID: CVE-2017-1235 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1235]\nDESCRIPTION: IBM MQ could allow an authenticated user to cause a premature termination of a client application thread, which could potentially cause denial of service.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/123914 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/123914] 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)","is_impossible":false,"contexts":[{"filename":"swg22005415.txt","text":"Title: IBM Security Bulletin: IBM MQ termination of a client application causes denial of service (CVE-2017-1235) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Termination during an MQGET call of a client application running on a channel with SHARECNV=1, could cause a SIGSEGV and termination of the channel agent process. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1235 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1235]\nDESCRIPTION: IBM MQ could allow an authenticated user to cause a premature termination of a client application thread, which could potentially cause denial of service.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/123914 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/123914] 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 V8.0 \n\nIBM MQ V8.0.0.6 and earlier maintenance levels. \n\nIBM MQ V9.0 Long Term Support Release \n\nIBM MQ V9.0.0.1 and earlier maintenance levels. \n\nIBM MQ V9.0 Continuous Delivery Release \n\nIBM MQ Continuous delivery update 9.0.3 and earlier maintenance levels.\n\nREMEDIATION\/FIXES\nIBM MQ V8.0 \n\nApply 8.0.0.7 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0.0.7&platform=All&function=all&useReleaseAsTarget=true] maintenance level. \n\nIBM MQ V9.0 Long Term Support Release \n\nApply 9.0.0.2 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=9.0.0.2&platform=All&function=all&useReleaseAsTarget=true] maintenance level. \n\nIBM MQ V9.0 Continuous Delivery Release \n\nApply continuous delivery update 9.0.4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043348] 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\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."}]},{"id":"TRAIN_Q401","question":"How do I tell when there are mismatched MQ jars in my application server?\n\nMismatched jar files can cause strange and unpredictable errors when using the MQ JMS classes from a .war file. ","answer":"If your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.","is_impossible":false,"contexts":[{"filename":"swg21681142.txt","text":"Title: IBM Solving IBM MQ Java code version mismatches using the mqjavalist.sh script - United States\n\nText:\nWebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Java\u2122 SE applications and Java EE application servers such as WebSphere Application Server do not use a consistent set of MQ Java archives, applications can fail in unpredictable ways. If WebSphere Application Server notices a mismatch, it issues this message: \"MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.\" \n\nENVIRONMENT\nThe mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions. Although the mqjavalist.sh script does not run on Windows systems, it is possible to zip up a directory structure on Windows in order to examine it with mqjavalist.sh on a different system. To use the mqjavalist.sh script, download it from the bottom of this page, copy it to the target system, and make the script executable. Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example:\n\n\n\n 1. Preparing to run mqjavalist.sh\n 2. \n 3. sh> chmod +x mqjavalist.sh \n sh> PATH=$PATH:\/opt\/java7\/bin \n \n\n\n\n\nDIAGNOSING THE PROBLEM\nIBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages. For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications. Java SE and Java EE applications must use a consistent set of MQ jar files at the same maintenance level, or else they might experience a wide variety of problems including intermittent errors, performance problems, and other failures.\n\nIt is common to find multiple versions of the MQ jar files in the Java CLASSPATH, or invalidly bundled in Java applications (.ear, .war, and .jar files). Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.\n\n\n\n * Syntax\n * Examples\n * WebSphere Application Server\n * Sample output\n * Resolving problems\n * Download\n\n\n\nSYNTAX\n\n 1. mqjavalist.sh -? | -h \n 2. \n 3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ...\n 4. \n 5. \n 6. \n 7. -?:\n 8. \n 9. \n 10. -h:\n 11. \n 12. \n 13. -v:\n 14. \n 15. \n 16. -r:\n 17. \n 18. \n 19. -f File\u200b:\n 20. \n 21. \n 22. -d Directory:\n 23. \n 24. \n 25. \n 26. \n 27. \n 28. The mqjavalist.sh script can take several minutes to complete, depending on the number of Java archives to search and whether you perform a recursive examination of archive files. While running, the script regularly prints its status and the percentage of work completed.\n\n\nBack to top\n\n\n\nEXAMPLES\n\n 1. Search for MQ files under \/usr\/IBM\/WebSphere and save the results to the file mqlist.txt:\n \n mqjavalist.sh -f mqlist.txt -d \/usr\/IBM\/WebSphere\n 2. \n 3. \n 4. Perform a recursive search of archives under \/opt\/IBM:\n \n mqjavalist.sh -r -d \/opt\/IBM\n 5. \n 6. \n 7. Recursively search archive files under the \/opt\/IBM\/IIB and \/opt\/mqm directories and enable verbose output to ~\/output.txt:\n \n mqjavalist.sh -vrf ~\/output.txt -d \/opt\/IBM\/IIB -d \/opt\/mqm\n 8. \n\n\nBack to top\n\n\n\nWEBSPHERE APPLICATION SERVER\n\nWebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location. Except as noted below, the copies of the MQ jar files should match the versions listed on this page [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089]. Any copies of the MQ jar files other than those listed below might represent a problem: \n\n\n 1. WebSphere Application Server V8.5.5, V8.5 and V8.0\n 2. \n 3. \n\n\n\n 1. WebSphere Application Server V7.0\n 2. \n 3. \n 4. \n 5. \n 6. If you created a WebSphere Application Server V7.0 profile before applying fix pack 7.0.0.1 or later, you must update the profile to use the correct MQ Resource Adapter path [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_7.0.0\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/tmj_wmqra_restoredefault.html]. Otherwise, the application servers in that profile will use the old MQ Resource Adapter jars under the profile installedConnectors\/wmq.jmsra.rar directory rather than the MQ jars in the main installedConnectors\/wmq.jmsra.rar directory, which are kept up to date by WebSphere Application Server fix packs.\n\n\n 1. WebSphere Application Server V6.1\n 2. \n 3. \n\n\n\nBack to top\n\n\n\nSAMPLE OUTPUT\n\n 1. sh> \n 2. .\/mqjavalist.sh -r -f mqlist.txt -d \/opt\/IBM\/WebSphere\/AppServer\n 3. \n 4. Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d \/opt\/IBM\/WebSphere\/AppServer\n \n mqjavalist.sh: Searching directory \/opt\/IBM\/WebSphere\/AppServer\n mqjavalist.sh: 2180 possible Java archives found\n 1. Found 80 MQ classes in classes.jar in WMQHTTP.war in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/Dmgr01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:56 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/Dmgr01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear\n 2. Found 80 MQ classes in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/installedApps\/aemtux1Cell01\/WMQHTTP_war.ear\/WMQHTTP.war\/WEB-INF\/lib\/classes.jar:\n root root 156845 2013-09-25 18:02 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/installedApps\/aemtux1Cell01\/WMQHTTP_war.ear\/WMQHTTP.war\/WEB-INF\/lib\/classes.jar\n 3. Found 80 MQ classes in classes.jar in WMQHTTP.war in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:57 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear\n 4. Found com.ibm.mq.commonservices.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 5. Found com.ibm.mq.connector.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 6. Found com.ibm.mq.headers.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 \/wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 7. Found com.ibm.mq.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 8. Found com.ibm.mq.jmqi.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 9. Found com.ibm.mq.jmqi.local.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 10. Found com.ibm.mq.jmqi.remote.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 11. Found com.ibm.mq.jmqi.system.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 12. Found com.ibm.mq.jms.admin.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Common Client API\/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 13. Found com.ibm.mq.pcf.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 14. Found com.ibm.mqjms.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Client Common Facade\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 15. Found dhbcore.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n 16. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.jar:\n root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 17. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.commonservices.jar:\n root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 18. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.remote.jar:\n root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 19. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jar:\n root root 448745 2012-10-15 12:56 com.ibm.mq.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 20. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jms.admin.jar:\n root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar\n Implementation-Title: JMS Common Client API\/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 21. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mqjms.jar:\n root root 352254 Aug 01 11:49 com.ibm.mqjms.jar\n Implementation-Title: JMS Common Client facade\n Implementation-Version: 7.0.1.5 - k701-105-110419\n Implementation-Vendor: IBM Corporation\n 22. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.connector.jar:\n root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 23. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.headers.jar:\n root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 24. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.local.jar:\n root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 25. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.system.jar:\n root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 26. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.pcf.jar:\n root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 27. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/dhbcore.jar:\n root root 2011835 2012-10-15 12:56 dhbcore.jar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n mqjavalist.sh: 27 jar files with MQ code found in \/opt\/IBM\/WebSphere\/AppServer\n \n mqjavalist.sh: 27 total jar files with MQ code found\n mqjavalist.sh: Results saved to mqlist.txt\n \n \n \n 5. \n 6. Back to top\n\nRESOLVING THE PROBLEM\n\nReview the output from mqjavalist.sh to determine where copies of the MQ jar files have been found. Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime. If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it.\n\nIn the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter. They all show an implementation version of 7.1.0.0 - k000-L111005.1 except for #21, com.ibm.mqjms.jar, which shows an implementation version of 7.0.1.5 - k701-105-110419. Because the jar file versions are not in sync, MQ JMS will not function as expected.\n\nIn cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server. Entry #14 in the mqjavalist.sh output shows the com.ibm.mqjms.jar file with an implementation version of 7.1.0.0 - k000-L111005.1, which is what we need. Use the jar program to extract the com.ibm.mqjms.jar file from the wmq.jmsra.rar archive, then copy it over the back-level version of the jar. Use chown and chmod to ensure the permissions on the file are correct.\n\nIn other cases, you might find that the classpath for the application server, or for your Java SE application, is picking up extra copies of the MQ jar files. Eliminating unnecessary classpath entries can resolve the problem.\n\nIf your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.\n\nBack to top\n\n\nAdditional Keywords: \ntroubleshoot troubleshooting trouble shoot classloader classpath configuration scripts\n\n\n\nDOWNLOAD\n 1. \n 2. mqjavalist.sh [\/support\/docview.wss?uid=swg21681142&aid=2]mqjavalist.sh\n\n\n\n\nDISCLAIMER: All source code and\/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Back to top"}]},{"id":"TRAIN_Q402","question":"Why am I getting StaleConnectionException on WebSphere side while Oracle is throwing 'OALL8 is in an inconsistent state'?\n\n\n\nIn the WebSphere Application Server SystemOut.log file we see this message:\n\n ConnectionEve A J2CA0056I: TheConnection Manager received a fatal connection error from the Resource Adapter for resource jdbc\/<data source name>. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: OALL8 is in an inconsistent state:java.sql.SQLException: OALL8 is in an inconsistent state.\n\nHow can this be resolved?","answer":"In WebSphere Application Server, the StaleConnectionException is issued when the database vendor issues an exception indicating that a connection currently in the connection pool is no longer valid.","is_impossible":false,"contexts":[{"filename":"swg21063645.txt","text":"Title: IBM Demystifying the WebSphere StaleConnectionException - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n What is the StaleConnectionException, why is it issued by WebSphere Application Server, and what should be done about it? \n\nRESOLVING THE PROBLEM\nIn WebSphere Application Server, the StaleConnectionException is issued when the database vendor issues an exception indicating that a connection currently in the connection pool is no longer valid. This can happen for many reasons, including: \n\n * The application tries to get a connection and fails, as when the database is not started.\n \n \n * A connection is no longer usable due to a database failure. When an application tries to use a connection it has previously obtained, the connection is no longer valid. In this case, all connections currently in use by an application can get this error when they try to use the connection.\n \n \n * The application using the connection has already called close() and then tries to use the connection again.\n \n \n * The application tries to use a JDBC\u2122 resource, such as a statement, obtained on a now-stale connection.\n\n\nWhen the StaleConnectionException is issued, the behavior is determined by the Purge Policy setting for the connection pool. If the Purge Policy is set to EntirePool, the entire pool is flushed. But if the Purge Policy is set to FailingConnectionOnly, only the connection that caused the StaleConnectionException is purged from the pool. \n\nAn application can recover from bad connections by explicitly catching the StaleConnectionException and getting a new connection from the pool. Numerous exceptions issued by DB2, Oracle, DataDirect (for connecting to SQLServer), Sybase, and Informix are currently mapped to the StaleConnectionException, which makes recovery easier for the application programmer. The following pseudocode provides an example of how to recover from a StaleConnectionException: \n\n\/\/get a userTransaction\njavax.transaction.UserTransaction tran = getSessionContext().getUserTransaction();\n\/\/retry indicates whether to retry or not\n\/\/numOfRetries states how many retries have\n\/\/ been attempted\nboolean retry = false;\nint numOfRetries = 0;\njava.sql.Connection conn = null;\njava.sql.Statement stmt = null;\ndo {\ntry {\n\/\/begin a transaction\ntran.begin();\n\/\/Assumes that a datasource has already been obtained\n\/\/from JNDI\nconn = ds.getConnection();\nconn.setAutoCommit(false);\nstmt = conn.createStatement();\nstmt.execute(\"INSERT INTO EMPLOYEES VALUES\n(0101, 'Bill', 'R', 'Smith')\");\ntran.commit();\nretry = false;\n} catch(java.sql.SQLException sqlX)\n{\n\/\/ If the error indicates the connection is stale, then\n\/\/ rollback and retry the action\nif (com.ibm.websphere.rsadapter.WSCallHelper\n.getDataStoreHelper(ds)\n.isConnectionError(sqlX))\n{\ntry {\ntran.rollback();\n} catch (java.lang.Exception e) {\n\/\/deal with exception\n\/\/in most cases, this can be ignored\n}\nif (numOfRetries < 2) {\nretry = true;\nnumOfRetries++;\n} else {\nretry = false;\n}\n}\nelse\n{\n\/\/deal with other database exception\nretry = false\n}\n} finally {\n\/\/always cleanup JDBC resources\ntry {\nif(stmt != null) stmt.close();\n} catch (java.sql.SQLException sqle) {\n\/\/usually can ignore\n}\ntry {\nif(conn != null) conn.close();\n} catch (java.sql.SQLException sqle) {\n\/\/usually can ignore\n}\n}\n} while (retry) ; \n\nFurther details about WebSphere Connection Pooling are located in the WebSphere Application Server Knowledge Center article Connection pooling [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_8.5.5\/com.ibm.websphere.nd.doc\/ae\/cdat_conpool.html]\n\nKnowledge Center article Exceptions pertaining to data access [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_8.5.5\/com.ibm.websphere.nd.doc\/ae\/cdat_daexcp.html] contains details on the StaleConnectionException error\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"}]},{"id":"TRAIN_Q403","question":"Help with Security Bulletin: IBM PureApplication System is affected by a security vulnerability. (CVE-2015-1890)\n\nI need to understand details regarding \"Security Bulletin: IBM PureApplication System is affected by a security vulnerability (CVE-2015-1890)\". Where can I find this information? ","answer":"CVEID: CVE-2015-1890 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1890] \n\nDESCRIPTION: IBM General Parallel File System could allow someone who has access to a snap file generated by the gpfs.snap tool (\/usr\/lpp\/mmfs\/bin\/gpfs.snap) to read the private keys of certificates used by GPFS for daemon communications via the TLS protocol.\nCVSS Base Score: 3.5\nCVSS Temporal Score: See [https:\/\/exchange.xforce.ibmcloud.com\/]https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101382 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101382] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21964025.txt","text":"Title: IBM Security Bulletin: IBM PureApplication System is affected by a security vulnerability. (CVE-2015-1890) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A security vulnerability have been identified in the General Parallel File System gpfs.snap service tool that affects IBM PureApplication System. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1890 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1890] \n\nDESCRIPTION: IBM General Parallel File System could allow someone who has access to a snap file generated by the gpfs.snap tool (\/usr\/lpp\/mmfs\/bin\/gpfs.snap) to read the private keys of certificates used by GPFS for daemon communications via the TLS protocol.\nCVSS Base Score: 3.5\nCVSS Temporal Score: See [https:\/\/exchange.xforce.ibmcloud.com\/]https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101382 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101382] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:P\/I:N\/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects IBM PureApplication Server and the GPFS pattern type included in: \n\n * \n * \n * \n\nREMEDIATION\/FIXES\nThe solution is to upgrade the IBM PureApplication System to the following fix levels and update deployments that implement the GPFS pattern type using the GPFS Pattern Interim Fix: \nIBM PureApplication System V2.1 \n\n * \n * GPFS Pattern Interim Fix is located at: http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.1.0&includeSupersedes=0] \n\n\n\nIBM PureApplication System V2.0 * \n * GPFS Pattern Interim Fix is located at: http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&includeSupersedes=0 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=update-gpfs-1.2.0.0_1.2.0.1_and_1.2.0.2&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] \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\nNone \n\nCHANGE HISTORY\n 10 August 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."}]},{"id":"TRAIN_Q404","question":"Why do I get \"error: The admin task reported the following: null\" if uploading a DataPower scrypt3 firmware image file WAS 8.x DataPower Appliance Manager?\n\nHow can I manage a set of DataPower appliances that shall run v7 firmware images by using WebSphere Application Server 8.x DataPower Appliance Manager?I get \"error: The admin task reported the following: null\" if uploading a DataPower scrypt3, while scrypt2 works fine.","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q405","question":"How do I define JMS objects for MQ?\n\nWhere and how do I defined JMS objects used by an MQ JMS application? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q406","question":"Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect ( CVE-2016-5548). Where can I find this information? ","answer":"CVEID: CVE-2016-5548 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-5548]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120864 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120864] 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:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22006126.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 used by IBM API Connect. \n\nThese issues were disclosed as part of the IBM Java SDK updates in January 2017 and April 2017. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-5546 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-5546]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component has no confidentiality impact, high integrity impact, and no availability impact.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120869 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120869] 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:H\/A:N) \n\nCVEID: CVE-2016-5548 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-5548]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120864 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120864] 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:N\/A:N) \n\nCVEID: CVE-2016-5549 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-5549]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 6.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120863 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120863] 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:N\/A:N) \n\nCVEID: CVE-2016-5547 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-5547]\nDESCRIPTION: An unspecified vulnerability related to the Libraries component could allow a remote attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120871 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120871] 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\nCVEID: CVE-2016-2183 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DES\/3DES cipher, used as a part of the SSL\/TLS protocol. By capturing large amounts of encrypted traffic between the SSL\/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/116337 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\nCVEID: CVE-2017-3511 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3511]\nDESCRIPTION: An unspecified vulnerability related to the Java SE JCE component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.7\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/124890 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/124890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.7.2\n\nREMEDIATION\/FIXES\n \n\nAffected Product Addressed in VRMF APAR Remediation\/First Fix IBM API Connect \n\nV5.0.0.0 - 5.0.6.2 5.0.6.3 LI79749 Addressed in IBM API Connect V5.0.6.3.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps:\/\/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 [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\nV5.0.7.0 - 5.0.7.2 5.0.8.0 LI79749 Addressed in IBM API Connect V5.0.8.0.\n\nFollow this link and find the \"APIConnect_Management\" and \"apiconnect-collective-controller\" packages:\n\nhttps:\/\/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 [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] \nIBM Java SDK January 2017 Security Bulletin [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21997194] \nIBM Java SDK April 2017 Security Bulletin [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22002169] \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 11 September 2017: 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."}]},{"id":"TRAIN_Q407","question":"Help with Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WSRR \n\nI need to understand details regarding Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2017-1583, CVE-2011-4343). What products are affected?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q408","question":"Help with Fix Pack 6 for WMB V8\n\nWhere can I find more information about WebSphere Message Broker (WMB) Fix Pack 6?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q409","question":"OpenSSL Heartbleed (CVE-2014-0160) vulnerability and IBM Support Assistant ISA\n\n Ref. IBM Product Security Incident Response Team - https:\/\/www-304.ibm.com\/connections\/blogs\/PSIRT\/entry\/openssl_heartbleed_cve_2014_0160?lang=en_us\n\nAny statements we can share regarding OpenSSL usage in ISA (v4, v5)since it's neither listed here in NOT affected by this vulnerability? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q410","question":"how to disable clickjacking at ICN?\n\nWe need to secure IBM Content navigator 2.0.3 Fixpack (FileNet P8 5.2.1 FP5, OS AIX 7.1) on our Production environment against malicious activity in the following ways:\n\nDisable clickjacking i.e. it was observed that the server didn't return an X-Frame-Options header. The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q411","question":"Support for Domino 9.0.1 with ICC?\n\nIs Domino v9.0.1 and FP's supported for ICC?","answer":"Starting with IBM Content Collector 4.0.1 Fix Pack 6, IBM Lotus Domino\/Notes 9.0.1 FP7,FP8 are supported\n\nStarting with IBM Content Collector 4.0.1 Fix Pack 4, IBM Lotus Domino\/Notes 9.0.1 FP6 is supported \n\n Starting with IBM Content Collector 4.0.1 Fix Pack 2, IBM Lotus Domino\/Notes 9.0.1 FP4, FP5, Mozilla Firefox 35 and Microsoft Edge are supported. IBM Content Collector supports the latest fix packs of the server and client software.","is_impossible":false,"contexts":[{"filename":"swg27042658.txt","text":"Title: IBM Prerequisites for IBM Content Collector Version 4.0.1 - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n This document details the system requirements for IBM Content Collector Version 4.0.1. \n\nCONTENT\n \n\nAlways up-to-date system requirement reports can be dynamically generated by using the Software Product Compatibility Reports (SPCR) tool [http:\/\/www-969.ibm.com\/software\/reports\/compatibility\/clarity\/index.html]. \n\nFrom the Content Collector product tabs below you can select detailed system requirement reports for different contexts (by Operating System, by component). Note that clicking a link will always generate a new, up-to-date report.\n\nImportant:\nBecause 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 forward compatible.\n\nAlways check for the latest IBM Content Collector security bulletins in the IBM Support Portal and make sure to have the required fixes applied.\n\nPRODUCT REQUIREMENTS FOR IBM CONTENT COLLECTOR\n * All versions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27040212] \n * Version 4.0.1- selected tab, \n\n * HARDWARE REQUIREMENTS\n \n * Content Collector server\n * Client workstations\n * SOFTWARE PREREQUISITES\n \n * Operating system and software\n * Web application server\n * COLLECTION SOURCE SYSTEMS\n \n * Lotus Domino\n * Microsoft Exchange\n * SMTP email\n * Microsoft SharePoint\n * IBM Connections\n * File system\n\n * ARCHIVE SYSTEMS\n \n * IBM Content Manager\n * IBM FileNet P8\n * LEGACY RESTORE\n \n * Legacy restore\n * RETENTION POLICY DISTRIBUTION SUPPORT\n \n * Retention Policy Distribution Support\n * OPTIONAL SOFTWARE\n \n * Optional software\n\n\n\n\n\nIBM CONTENT COLLECTOR PRODUCTS\n * Content Collector for Email\n\n * Content Collector for File Systems\n\n * Content Collector for IBM Connections\n\n * Content Collector for Microsoft SharePoint\n\n\n\n\n\nLegend \n\nx86 Intel 32-bit processors, including IBM System x, eServer xSeries, and BladeCenter servers X86-64 64-bit AMD Opteron (AMD64) and Intel Xeon (EM64T) processors, including IBM System x and BladeCenter servers \n\nHARDWARE REQUIREMENTS\nIBM CONTENT COLLECTOR SERVER\nThe following table contains the minimum and the recommended hardware requirements for the server where IBM Content Collector is installed.\n\n \n\nHardware requirements Minimum Recommended Processor 2 dual-core processors\nx86 or x86-64 2 six-core processors\nx86 or x86-64 Processor speed 2.5 GHz > 3 GHz System memory (RAM) 4 GB 8 GB Hard disk Hard drive with sufficient capacity 2 enterprise class hard drives with 10000 RPM or better Disk space For IBM Content Collector program package, prerequisite software, temporary data, and log information 150 GB > 150 GB For each IBM Content Collector server that is intended to run an SMTP Receiver instance 750 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive documents from SMTP email systems, this storage must be on a fast NAS device and shared between all Content Collector servers. 1 TB redundant storage For IBM Connections archiving 10 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive IBM Connections documents, this storage must be on a fast NAS device and shared between all Content Collector servers. > 10 GB Supported virtualization environments for IBM Content Collector are VMware ESX and ESXi 4, 5, and 5.1 and Microsoft HyperV Server 2008, 2008 R2, and 2012.\n\nBack to top\n\nCLIENT WORKSTATIONS\nThe hardware capacity of connected client workstations must be sufficient to run the supported client applications:\n\n * Lotus Notes or Lotus iNotes\n * Microsoft Outlook or Outlook Web App\n\nIn addition, the minimum hardware requirements for mobile support are contained in the following form(OWA Extension mobile support on iPhone and iPad, iNotes Extension mobile support on iPad only) starting with IBM Content Collector 4.0.1 Fix Pack 2 \n\n \n\nHardware iOS Capacity iPad mini 9.x 16GB iPad with Retina 9.x 16GB iPhone 6 9.x 16GB For more information, see the client software documentation.\n\nBack to top\n\n\n\nSOFTWARE PREREQUISITES\nPREREQUISITES FOR THE IBM CONTENT COLLECTOR SERVER\nThe following section describes the operating system and other software that is required on the system where IBM Content Collector Server is installed.\n\nOPERATING SYSTEM\nIBM Content Collector can be installed on servers with one of the following operating systems:\n\nOperating systems Editions Architectures Fixes Windows Server 2008 * Standard Edition \n * Enterprise Edition\n\n * 32-bit (x86) \n * 64-bit (x86-64)\n\nService Pack 2 Windows Server 2008 R2 * Standard Edition \n * Enterprise Edition\n\n * 64-bit (x86-64)\n\nService Pack 1 Windows Server 2012 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] Windows Server 2012 R2 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] Windows Server 2016 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] IBM Content Collector does not support Server Core and Nano server installations. Note that if IBM Content Collector is installed on Windows Server 2012 R2, you can use only IBM Content Manager Enterprise Edition V8.5 as an IBM Content Manager target repository.\n\n\nREQUIRED SOFTWARE\nThe following software must be installed on the server where IBM Content Collector is installed.\nImportant: \n\n * On a 64-bit operating system, IBM Content Collector Server runs in 32-bit compatibility mode. Therefore, IBM Content Collector Server requires the 32-bit version of all software prerequisites. \n * For performance reasons, do not colocate the IBM Content Collector Server and the archive system on one server in a production environment. This setup can be used for testing or demonstration purposes, but it is not officially supported.\n\nSoftware Required for which scenarios Notes DB2 Information Integrator for Content Required for IBM Content Manager V8.4 repositories See IBM Content Manager. IBM Content Manager V8 API Required for IBM Content Manager V8.5 repositories See IBM Content Manager. FileNet Content Engine .NET and Java clients Required for IBM FileNet P8 repositories See IBM FileNet P8. IBM FileNet IDM Desktop 4.0.x Required for IBM FileNet Image Services repositories [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft .NET Framework 4.0 or 4.5 Always required When using Microsoft .NET version 4.5 on a Windows Server 2008 or Windows Server 2008 R2 operating system, Microsoft .NET Framework 4.5.1 is required. Lotus Domino 8.5.0 server with the latest fix pack \nLotus Domino 8.5.3 FP6 server\nLotus Domino 8.5.4 server\nIBM Domino 9.0 or 9.0.1 FP2 server\nIBM Domino 9.0.1 FP4 server\nIBM Domino 9.0.1 FP5 server\nIBM Domino 9.0.1 FP6 server\nIBM Domino 9.0.1 FP7 server\nIBM Domino 9.0.1 FP8 server Required if you want to archive Lotus Notes documents The Lotus Domino server provides a Lotus Notes API for processing Lotus Notes documents. Microsoft Outlook 2007 Service Pack 3 (or later)\nMicrosoft Outlook 2010 Service Pack 1 (or later)\nMicrosoft Outlook 2013\nMicrosoft Outlook 2016 Required if you want to archive email from Microsoft Exchange servers The Microsoft Outlook client provides the Messaging API (MAPI) for email processing. Microsoft Windows DST update KB 955839 [http:\/\/support.microsoft.com\/kb\/955839] Always required [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft Windows Server 2008 R2 SP1 hotfix KB 2732673 [http:\/\/support.microsoft.com\/kb\/2732673]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2728738 [http:\/\/support.microsoft.com\/kb\/2728738]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2831013 [http:\/\/support.microsoft.com\/kb\/2831013]\nMicrosoft Windows Server 2008 R2 hotfix KB 2831154 [http:\/\/support.microsoft.com\/kb\/2831154] Required if the File System Connector is used [\/support\/docview.wss?uid=swg27042658&aid=1] Back to top\n\nWEB SERVER APPLICATIONS\nIBM WEBSPHERE APPLICATION SERVER\nIBM Content Collector requires IBM WebSphere Application Server to run the Configuration Web Service and to perform search and restore operations. Typically, there is no need to check for compatible versions because IBM Content Collector comes with an embedded version of WebSphere Application Server Version 8.0.\n\nHowever, you can deploy some of the IBM Content Collector web applications to an external web application server. IBM Content Collector supports the base edition of IBM WebSphere Application Server for AIX, Linux, and Windows. The Network Deployment edition is not supported. Always install the latest fix pack. The following versions are supported: \n\n * 8.0.0.13 \n * 8.5\n\nIf you use an external web application server, make sure that the following prerequisites that are required for IBM Content Collector Server are also installed on the separate web application server: \n\n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package \n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update \n * Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package \n\nHow to get: \n\nYou can purchase IBM WebSphere Application Server from the following website: WebSphere Application Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024129]\n\nIBM CONTENT COLLECTOR WEB APPLICATION BROWSERS\nThe IBM Content Collector web applications support the following browsers: \n\nBrowsers Versions Mozilla Firefox * 14 \n * 17 or 24 Extended Support Release (ESR) \n * 24 \n * 28 \n * 31 Extended Support Release (ESR) \n * 32 \n * 33 \n * 34 \n * 35\n\nMicrosoft Internet Explorer * 8 \n * 9 \n * 10 \n * 11\n\nMicrosoft Edge * 20\n\nChrome * 60\n\nMicrosoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2. \n\nHow to get: \n\nYou can obtain Mozilla Firefox from www.mozilla.com [http:\/\/www.mozilla.com] and Microsoft Internet Explorer from www.microsoft.com [http:\/\/www.microsoft.com].\n\nBack to top\n\n\n\nCOLLECTION SOURCE SYSTEMS\nLOTUS DOMINO\nSERVER AND CLIENTS\nThe following table describes the supported versions of Lotus Domino for Domino mail servers and the supported versions of Lotus Notes for Notes mail clients:\n\nServer software Client software Other software requirements Notes * Lotus Domino 8.5.0 \n * Lotus Domino 8.5.1 \n * Lotus Domino 8.5.2 \n * Lotus Domino 8.5.3 FP6 \n * Domino 9.0 \n * Domino 9.0.1 FP2 \n * Domino 9.0.1 FP4 \n * Domino 9.0.1 FP5 \n * Domino 9.0.1 FP6 \n * Domino 9.0.1 FP7 \n * Domino 9.0.1 FP8\n\n * Lotus Notes 8.5.0 \n * Lotus Notes 8.5.1 \n * Lotus Notes 8.5.2 \n * Lotus Notes 8.5.3 FP6 \n * Notes 9.0 (along with the Browser plug-in) \n * Notes 9.0.1 (along with the Browser plug-in) \n * Notes 9.0.1 FP2 \n * Notes 9.0.1 FP4 \n * Notes 9.0.1 FP5 \n * Notes 9.0.1 FP6 \n * Notes 9.0.1 FP7 \n * Notes 9.0.1 FP8\n\n * Windows 7 Service Pack 1 (32-bit and 64-bit) \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Mac OS X 10.8.x (32-bit and 64-bit) \n * Mac OS X 10.9.x (32-bit and 64-bit) \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Mozilla Firefox 14 \n * Mozilla Firefox 17 or 24 Extended Support Release (ESR) \n * Mozilla Firefox 24 \n * Mozilla Firefox 28 \n * Mozilla Firefox 31 Extended Support Release (ESR) \n * Mozilla Firefox 32 \n * Mozilla Firefox 33 \n * Mozilla Firefox 34 \n * Mozilla Firefox 35 \n * Microsoft Internet Explorer 8 \n * Microsoft Internet Explorer 9 \n * Microsoft Internet Explorer 10 \n * Microsoft Internet Explorer 11 \n * Microsoft Edge\n\nOn Mac OS X, Lotus Notes R8.5.1 Fix Pack 2 or higher is required.\n\nOffline repositories, collecting additional archiving information, and automatic document retrieval is not supported for Lotus Notes clients on Mac OS.\n\nThe Notes 9.0 Browser plug-in provides these Content Collector functions: * Interactive restore \n * Settings \n * Help\n\n * Lotus iNotes 8.5.0 \n * Lotus iNotes 8.5.1 \n * Lotus iNotes 8.5.2 \n * Lotus iNotes 8.5.3 FP6 \n * iNotes 9.0 \n * iNotes 9.0.1 FP2 \n * iNotes 9.0.1 FP4 \n * iNotes 9.0.1 FP5 \n * iNotes 9.0.1 FP6 \n * iNotes 9.0.1 FP7 \n * iNotes 9.0.1 FP8\n\niNotes must have been configured when the Domino server was initially configured. Starting with IBM Content Collector 4.0.1 Fix Pack 6, IBM Lotus Domino\/Notes 9.0.1 FP7,FP8 are supported\n\nStarting with IBM Content Collector 4.0.1 Fix Pack 4, IBM Lotus Domino\/Notes 9.0.1 FP6 is supported \n\n Starting with IBM Content Collector 4.0.1 Fix Pack 2, IBM Lotus Domino\/Notes 9.0.1 FP4, FP5, Mozilla Firefox 35 and Microsoft Edge are supported. IBM Content Collector supports the latest fix packs of the server and client software. \n\nWindows 10 is supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nIf you want to use the IBM Content Collector Offline Repository in Notes, the following packages are required on the workstation that runs the Notes client, depending on the version of IBM Content Collector that was used to enable the Domino template: \n\nContent Collector version used to enable Domino template Required package on client workstation IBM Content Collector 2.2 (or earlier) Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update [http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=26347] IBM Content Collector 3.0, 4.0, or 4.0.1 Microsoft Visual C++ 2010 Redistributable Package [http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en] To use IBM Content Collector Search, Lotus Notes R8.5.1 or later with standard configuration is required. Basic configuration is not supported. \n\nIf you want to use IBM Content Collector Search in Notes against a database without an index, the following packages are required on the workstation that runs the Notes client:\n\n * Microsoft Visual C++ 2010 Redistributable Package [http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en]\n * Microsoft Security Advisory: Insecure library loading could allow remote code execution [http:\/\/support.microsoft.com\/kb\/2533623] \n\n\n\nHow to get: \n\nYou can purchase Domino from the following website: IBM Domino [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24033984]\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running a Lotus Notes client on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenDesktop 7.0 Domino\/Notes 9.0\nCitrix XenDesktop 7.5 or later Application installed on server Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to server Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to client Lotus Domino\/Lotus Notes 8.5.1 or \nDomino\/Notes 9.0 Basic\nCitrix XenApp 6.5 Hosted application in your datacenter Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later Local Access App Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later Microsoft Application Virtualization applications (App-V) Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later For the virtualization method application streamed to client, the following restriction applies:\n\n * Automatic client document retrieval does not work in the standard configuration of Notes client version 8.5, 8.5.3, or 9.\n\n \n\n\nBack to top\n\nMICROSOFT EXCHANGE\nSERVER\nThe following table describes the supported versions of Microsoft Exchange Server:\n\nServer software Notes * Microsoft Exchange Server 2007 Standard and Enterprise Edition with Service Pack 3 Update Rollup 11 \n * Microsoft Exchange Server 2010 Standard and Enterprise Edition with Service Pack 2 Update Rollup 4 or Service Pack 3 \n * Microsoft Exchange Server 2013 Standard and Enterprise Edition with Service Pack 1 (KB2860242 [http:\/\/support.microsoft.com\/kb\/2860242]) \n * Microsoft Exchange Server 2016 Standard and Enterprise Edition \n\nYou must not install Microsoft Exchange Server on the IBM Content Collector server. How to get:\nYou can purchase Microsoft Exchange Server from www.microsoft.com [http:\/\/www.microsoft.com].\n\nOUTLOOK EXTENSION\nBefore you add the IBM Content Collector Outlook Extension to a client workstation, ensure that the required software is installed on that workstation: \n\nOperating system Client application Other software requirements Notes * Windows 7 Professional Service Pack 1 \n * Windows 7 Ultimate Service Pack 1 \n * Windows 7 Enterprise Service Pack 1 \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Microsoft Outlook 2007 Service Pack 3 \n * Microsoft Outlook 2010 Service Pack 2 \n * Microsoft Outlook 2013 \n * Microsoft Outlook 2016\n\n * .NET Framework 4.5 (or later)\n\nYou can install the IBM Content Collector Outlook Extension irrespective of the language in which Outlook is installed.\n\nAn Outlook logon profile containing the parameters for the connection to the Exchange server must exist.\n\nThere are different Outlook extension installable to be used with 32-Bit and 64-Bit versions of Microsoft Outlook * Mozilla Firefox 14, 17 or 24 ESR, 24, 28, 31 ESR, 32, 33, 34, or 35 \n * Microsoft Internet Explorer 8, 9, 10, or 11 \n * Microsoft Edge \n * Chrome 60\n\nMicrosoft Outlook 64 Bit version is supported starting with IBM Content Collector 4.0.1 Fix Pack 8 with Outlook Extension (64-bit) installable.\n\nWindows 10, Microsoft Edge and Microsoft Outlook 2016 are supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nChrome browser is supported starting with IBM Content Collector 4.0.1 Fix Pack 6\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running Outlook Extension on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Microsoft Outlook 2010\nCitrix XenDesktop 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop 7.6 or later Hosted application in your datacenter Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later Local Access App Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later Microsoft Application Virtualization applications (App-V) Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later \n\n\nOUTLOOK WEB APP (OWA)\n Outlook Web App (OWA) Extension\n\nTo install the IBM Content Collector Outlook Web App Extension on the Exchange server, the following requirements must be met: \n\nExchange Server version (required) Other software requirements Notes * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2 \n * Microsoft Exchange Server 2013 SP1 \n * Microsoft Exchange Server 2016 \n\n.NET Framework 4.5 Full Profile (or later) The OWA Extension must be installed on the Exchange Server that has the Client Access Server (CAS) role. Outlook Web App (OWA) Service\n\nApart from the Outlook Web App Extension that is installed on the Exchange server, the Outlook Web App Service is installed on top of a Microsoft Internet Information Service (IIS) Server. The following table lists the operating system and other requirements for the OWA Service.\n\n \n\nExchange Server version Operating system for the Outlook Web App Service (required) Other software requirements * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * Windows Server 2008 Service Pack 2 \n * Windows Server 2008 R2 Service Pack 1\n\n * Microsoft IIS Server 6 or 7 \n * .NET Framework 4.5\n\n * Microsoft Exchange Server 2013 SP1\n\n * Windows Server 2008 R2 Service Pack 1 \n * Windows Server 2012 R2\n\n * Microsoft IIS Server 7.5 (or later)\n\n * Microsoft Exchange Server 2016 \n\n * Windows Server 2012 \n * Windows Server 2012 R2\n\n * .NET Framework 4.5.2\n\nIn the Internet Information Service (IIS) Manager: \n\n * Set the Web Service Extension ASP.NET V4.5 to Allowed. \n * Set the identity of the application pool where the OWA service resides to NetworkService. \n * Set the .NET Framework version to v4.5 \n * Disable the forms authentication method for the OWA Service (afuowa) after the installation. IBM Content Collector OWA Service does not support forms authentication in Microsoft IIS 7.0. \n\n\nHow to get: \n\nYou can purchase Microsoft IIS Server and .NET Framework from www.microsoft.com [http:\/\/www.microsoft.com].\n\n\nOutlook Web App (OWA) client \n\nTo be able to use the Outlook Web App functions, clients require the following software on their workstations: \n\n \n\nExchange Server version Software prerequisites for OWA clients * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * .NET Framework 2.0 (or later) \n * Microsoft Internet Explorer 8, 9, or 10\n\n * Microsoft Exchange Server 2013 SP1\n\n * Microsoft Internet Explorer 9, 10 or 11 \n * Google Chrome 13 \n * Microsoft Edge\n\n * Microsoft Exchange Server 2016 \n\n * Microsoft Internet Explorer 10 or 11 \n * Microsoft Edge\n\nThe following restrictions apply: \n\n * IBM Content Collector OWA support does not work with if the option \"Use the blind and low vision experience\" in the OWA settings is used. \n * IBM Content Collector OWA support works only with OWA Premium Mode. \n * IBM Content Collector OWA support on Exchange 2010 supports only the Internet Explorer browser and not Apple Safari, Mozilla Firefox, and so on although Microsoft OWA 2010 supports other browsers. \n * IBM Content Collector OWA support on Exchange 2013 supports the Google Chrome browser in Apple Mac OS X 10.9.x (32-bit and 64-bit) \n * Microsoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2 \n * IBM Content Collector OWA support on Exchange 2016 is supported starting from IBM Content Collector 4.0.1 Fix Pack 3 Back to top\n \n \n \n \n \n\nSMTP EMAIL\nIBM Content Collector can archive SMTP\/MIME email. The source mail system requires a specific setup to send all SMTP\/MIME email to be processed to IBM Content Collector. \nIn addition to SMTP forwarding for Microsoft Exchange and Lotus Domino, the respective setup has been tested for these mail systems:\n\n\n\nMail system Notes Microsoft Exchange Online See technote 1648828 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21648828] for information about how to set up journal forwarding from Microsoft Exchange Online to IBM Content Collector. Google Mail for Business See technote 1648572 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21648572] for information about archiving email from Google Mail for Business with IBM Content Collector. \nBack to top\n\nMICROSOFT SHAREPOINT\nThe following table describes the supported versions of Microsoft SharePoint: \n\n \n\nMicrosoft SharePoint Notes Microsoft SharePoint Server 2010 with Service Pack 2 (Standard or Enterprise edition) [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft SharePoint Foundation 2010 with Service Pack 2 Microsoft SharePoint Server 2013 with Service Pack 1 (Standard or Enterprise edition) Only functionality that is also provided by Microsoft SharePoint 2010 is supported. Microsoft SharePoint Foundation 2013 with Service Pack 1 Microsoft SharePoint Server 2016 (Standard and Enterprise edition) Only functionality that is also provided by older Microsoft SharePoint servers is supported. \nMicrosoft SharePoint Foundation edition is no longer available in the SharePoint Server 2016 release. As an alternative end users can use 180 days trial for Standard or Enterprise edition.\n\nHow to get:\nYou can purchase Microsoft SharePoint from www.microsoft.com [http:\/\/www.microsoft.com].\n\nBack to top\n\nIBM CONNECTIONS\n\nThe following table describes the supported versions of IBM Connections: \n\n \n\nIBM Connections IBM Connections 4.5 Documents from IBM Connections can be archived in the following archive systems: \n\n * IBM Content Manager Enterprise Edition (all supported versions) \n * IBM FileNet P8 Content Engine 5.1 or later with IBM Content Search Services\n\nHow to get: \n\nYou can purchase IBM Connections from the following website: IBM Connections [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034473].\n\nBack to top\n\nFILE SYSTEM SUPPORT\nThe following table describes supported file systems. \n\nFile system Notes NTFS V3.1\n\nDepending on the repository capabilities, the maximum supported file size is up to 30 GB.\n\nIBM Content Collector supports Microsoft SMB Protocol versions 1.0, 2.0 and 3.0 for Windows file server ReFS (Windows 2012) Novell Netware V6.5 SP 8 Novell Open Enterprise Server 2 SP3\nNovell Open Enterprise Server 11 Samba V3.3 Services for NFS for Windows 2008, 2008 R2, 2012, 2016 Windows Server 2016 is supported as File System collection source starting with IBM Content Collector 4.0.1 Fix Pack 8\n\nRestriction: If IBM Content Collector is installed on Windows 2008 and you are archiving from Novell file servers, Novell Client 2 SP1 IR 6 or later must be installed. \n\nThe File System Repository Connector also allows for archiving to cloud file systems. \n\n\nBack to top\n\n\n\nARCHIVE SERVERS\nIBM CONTENT MANAGER\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the connector that is required on the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required connector on IBM Content Collector Server Notes IBM Content Manager Enterprise Edition V8.4.2 Fix Pack 3 and V8.4.3 Fix Pack 3\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27036382]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3. Use the Setup Type Connector.\n\nSupport for IBM Content Manager V8.4 on Linux requires a Linux 32-bit system on an Intel platform or Linux for System z. For details, see the technote Content Manager Enterprise Edition Version 8.4 support for 32-bit \/ 64-bit for Linux\/UNIX\/Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21293849].\n\nImportant: For IBM Content Manager Enterprise Edition V8.4.3, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 on AIX, text search requires IBM Content Collector Text Search Support V4.0.\n\nImportant: For IBM Content Manager Enterprise Edition V8.5, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5 Fix Pack 4\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5 Fix Pack 4. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 Fix Pack 4 on AIX, text search requires IBM Content Collector Text Search Support V4.0. IBM Content Manager for z\/OS Version V8.4.2, V8.4.3, and V8.4.3 Fix Pack 1\n * z\/OS\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3, V8.4.3, or V8.4.3 Fix Pack 1. Use the Setup Type Connector.\n\nIBM Content Manager for z\/OS can be used as a repository for files and Microsoft SharePoint documents. Email documents are supported starting with V8.4.3 Fix Pack 1. Text search is not supported. IBM Content Manager for z\/OS V8.5 * z\/OS\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nText search is not supported. How to get:\nYou can purchase IBM Content Manager from the following websites:\n\n\n * Content Manager Enterprise Edition [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035460]\n * Content Manager for z\/OS [http:\/\/www.ibm.com\/software\/products\/us\/en\/conmanzos]\n\nTEXT-SEARCH FUNCTION\nTo enable the text-search function (full-text search) for a Content Manager archive system, the IBM Content Collector indexer for text search must be installed. While IBM Content Collector supports archiving to Content Manager archive systems with DB2 databases or Oracle databases, the text-search function is not supported for archive systems with Oracle databases.\n\n The indexer for text search requires IBM Content Manager Enterprise Edition and the following software:\n\nNet Search Extender\nThe required version depends on the version of DB2 that is used by IBM Content Manager. Additional Net Search Extender e-fixes (required) Notes AIX Power 6.1 and 7.1 IBM Net Search Extender 9.1 for DB2 V9.1 Fix Pack 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24024133] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] IBM Net Search Extender and the required fix packs and e-fixes must be installed on the IBM Content Manager server. Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.5 for DB2 V9.5 Fix Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24025481] Windows\n\nIC58821\nIP22989 Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.7 for DB2 V9.7 Fix Pack 4 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029745] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.1 for DB2 V10.1 Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24033997] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.5 for DB2 10.5 Fixpack 6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040522] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 How to get: \n\nYou can download IBM Content Manager fix packs and Net Search Extender e-fixes from the following websites:\n\n * Content Manager fix packs [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27009038]\n * Net Search Extender e-fixes [ftp:\/\/public.dhe.ibm.com\/ps\/products\/db2extenders\/fixes]\n\nBack to top\n\nIBM FILENET P8\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the FileNet APIs that are required for the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required APIs on IBM Content Collector Server Notes IBM FileNet P8 Content Engine 5.0.0.1, 5.1 Fix Pack 2, 5.2, or 5.2.1 \n\nFor the required level of the database management system, see the IBM FileNet P8 system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27013654]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the FileNet P8 Content Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the FileNet P8 Content Engine Client installer. [\/support\/docview.wss?uid=swg27042658&aid=1] Important: For IBM FileNet P8 Content Engine 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. IBM Content Foundation V5.2 or V5.2.1 \n\nFor the required level of the database management system, see the IBM Content Foundation system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038265]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the IBM Content Foundation Content Platform Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the IBM Content Foundation Content Platform Engine installer. [\/support\/docview.wss?uid=swg27042658&aid=1] Important: For IBM Content Foundation V5.2.0, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. IBM FileNet Image Services 4.1.2 or 4.2 * AIX \n * HP-UX \n * Solaris \n * Windows\n\nIBM FileNet IDM Desktop IBM FileNet Image Services can only be used as a repository for files. It is not suitable for email. Text search and retrieving archived content through stub links is not supported. If you use IBM FileNet P8 with IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported.\n\nImportant: The fix pack level of the Content Engine of IBM Content Collector Server must match the fix pack level of the Content Engine server for both the .NET Clients and the Java Clients components.\n\nHow to get: \n\nYou can purchase FileNet P8 from the following websites:\n\n\n * FileNet Content Manager [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034227]\n * Content Foundation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034868]\n * FileNet Image Services [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24020652]\n\nTEXT-SEARCH FUNCTION\nThe text-search function (full-text search) for FileNet archive systems with IBM Legacy Content Search Engine requires Autonomy IDOL K2. With IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported\n\nTo use the text-search function (full-text search) for FileNet archive systems with IBM Content Search Services, IBM Content Collector Content Search Services Support must be installed on the Content Search Services server. If the Content Search Services server runs on AIX, Linux, or Solaris, ensure that Java 1.6 is installed. \n\nContent Search Services Support requires the following FileNet P8 components: \n\n\nFileNet P8 components Required on which server Operating system Notes IBM FileNet P8 Content Engine 5.1 Fix Pack 3 with IF001 or later, or 5.2 Fix Pack 2 with IF001 or later, or 5.2.1\nIBM Content Foundation V5.2 or V5.2.1 FileNet P8 Content Engine server * AIX \n * Linux \n * Solaris \n * Windows\n\nInterim Fixes are available on Fix Central [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=FileNet+Product+Family&product=ibm\/Information+Management\/FileNet+Content+Engine&release=5.1.0.0&platform=All&function=all].\n\nThe FileNet P8 Content Engine server must be configured to use Content Search Services. IBM FileNet P8 Content Search Engine Client 5.1 Fix Pack 2 or Content Search Engine Client 5.2 Content Search Services server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe client component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. IBM FileNet P8 Content Search Services 5.1 with IF005 or later, or 5.2 with IF002 or later, or 5.2.1\n\nFor details about the supported operating systems, see the IBM FileNet P8 system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27013654]. Content Search Services server * AIX \n * Linux \n * Windows\n\nInterim Fixes are available on Fix Central [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=FileNet+Product+Family&product=ibm\/Information+Management\/FileNet+Content+Search+Services&release=5.1.0.0&platform=All&function=all].\n\nImportant: For IBM FileNet P8 Content Search Services 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. Java Clients (Other Applications) 5.1 Fix Pack 2 or 5.2 * Content Search Services server \n * IBM Content Collector server\n\n * AIX \n * Linux \n * Solaris \n * Windows\n\nThe Java Clients component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. .NET Clients 5.1 Fix Pack 2 or 5.2 IBM Content Collector server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe .NET Clients component is provided through the FileNet P8 Content Engine installer. \nThe text-search function (full-text search) for IBM Content Foundation requires the Content Search Services component. Back to top\n\n\n\nLEGACY RESTORE\n\nLegacy restore provides access to documents that were archived with IBM CommonStore for Lotus Domino or IBM CommonStore for Exchange Server. Legacy restore supports the same archive systems as the CommonStore products and has the same system requirements to connect to these archive systems as the CommonStore products:\n\nSystem requirements for IBM CommonStore for Lotus Domino [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27010342]\nSystem requirements for IBM CommonStore for Exchange Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27010343]\n\nIn addition, Legacy Restore also supports the archive systems IBM Content Manager Enterprise Edition V8.5 and IBM Content Manager for z\/OS V8.5. \n\nThere are some limitations when using IBM Content Collector Legacy Restore instead of the CommonStore products, including the following restrictions: \n\n * IBM Content Collector Legacy Restore provides read-only access to documents, but no write access. \n * For documents that are stored in Content Manager OnDemand or Content Manager for z\/OS, search is not supported. \n * For multi-part document model item types in Content Manager 8, only the first part can be previewed.\n\nIBM Content Collector Legacy Restore supports the same operating systems as IBM Content Collector Server. \n\nBack to top\n\n\n\n\n\n\nRETENTION POLICY DISTRIBUTION SUPPORT\nTo use IBM Content Collector Retention Policy Distribution Support, you must install IBM Atlas Policy Suite, which is the client interface in Global Retention Policy and Schedule Management for managing document retention schedules.\n\nThe following table describes the supported versions of IBM Atlas Policy Suite:\n\n\n\nIBM Atlas Policy Suite IBM Atlas Policy Suite 6.0.3 How to get: \n\nYou can purchase IBM Atlas Policy Suite from the following website: IBM Atlas Policy Suite [https:\/\/www.ibm.com\/support\/entdocview.wss?uid=swg24036335]. \n\nBack to top\n\n\n\n\n\n\nOPTIONAL SOFTWARE\nThe following table describes the software that is required if you want to use optional functions of IBM Content Collector:\n\nFunction Software Use IBM eDiscovery Manager to search and collect archived documents IBM eDiscovery Manager V2.2.1 or V2.2 Fix Pack 4 Use IBM Content Classification to classify documents IBM Content Classification V8.8 Declare records against documents in a FileNet P8 archive system IBM Enterprise Records V5.1.1, V5.1.2, or V5.2 Fix Pack 1 Access documents in an archive system IBM FileNet Workplace XT V1.1.5 Fix Pack 1 or Fix Pack 2\nIBM Content Navigator V2.0, V2.0.1, V2.0.2, V2.0.3, V3.0 or V3.0.1 How to get: \n\nYou can purchase these products from the following websites:\n\n * IBM eDiscovery Manager [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035931]\n * IBM Content Classification [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029115]\n * IBM Enterprise Records [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035858]\n * IBM Content Navigator [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034327]\n\nBack to top\n\n\n\nIBM CONTENT COLLECTOR PRODUCT REPORTS\nCONTENT COLLECTOR FOR EMAIL\nREQUIREMENTS\nBY PLATFORM\n * Mac OS [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Mac OS]\n\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Windows]\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1385722855736]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862A48C058E511E3A11D923472D26C14]\n * Legacy Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8626C65058E511E3A11D923472D26C14]\n * Notes Client Extension [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862AE50058E511E3A11D923472D26C14]\n\n * Outlook Extension [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862BA85058E511E3A11D923472D26C14]\n * Outlook Web App Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862789A058E511E3A11D923472D26C14]\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862825E058E511E3A11D923472D26C14]\n\n * SharePoint Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8628E93058E511E3A11D923472D26C14]\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8629857058E511E3A11D923472D26C14]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR FILE SYSTEMS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6D064B0C7E811E4A93F4F818B63D91A]\n\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C89C80C7E811E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C9D500C7E811E4A93F4F818B63D91A]\n\n\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR IBM CONNECTIONS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE258D0C7ED11E4A93F4F818B63D91A]\n\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE035F0C7ED11E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE1BC90C7ED11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n \n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR MICROSOFT SHAREPOINT\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3176240C7EB11E4A93F4F818B63D91A]\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3151850C7EB11E4A93F4F818B63D91A]\n\n * SharePoint Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E315DBA0C7EB11E4A93F4F818B63D91A]\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3169EF0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top"}]},{"id":"TRAIN_Q412","question":"Can't delete BPD instances in Process Designer\n\nI'm not sure what is wrong with some BPD instances.\nWhen an instance is Active, but seems to not be able determine the next activity, I can't delete that instance in the Process Designer.\nEvery time I try to delete or terminate the instance, this message appears \"Delete BPD Instances (0%)\", but it get stuck there and nothing happens.\n\nI checked the Event Monitor, and there are few Jobs scheduled there... All show the same message: Notify BPD xxxxx of notification. Is this a tip what could be going wrong?\n\n\nWhat is the possible solution to this issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q413","question":"VScan not working after migrating Datacap Application from 8.1 to 9.0.1\n\n\n\nHello,\n\nI have recently migrated one datacap application developed in Datacap 8.1 to Datacap 9.0.1. I followed the complete instruction provided in the link \n\nhttp:\/\/www.ibm.com\/support\/knowledgecenter\/SSZRWV_9.0.1\/com.ibm.dc.develop.doc\/dcadv001.htm\n\n \n\nAfter migration, when I tried to execute the application using Datacap Desktop. I got errors that \"This batch has no data to process. Aborting\" and \"Unable to run queue\". I am attaching the screenshots of error. I am also attaching the DStudio rule's screenshot.\n\nI have verified and configured all the required settings.\n\nPlease guide if someone has faced the similar issue and resolved it.\n\nThanks.\n","answer":"The \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity).","is_impossible":false,"contexts":[{"filename":"swg21967312.txt","text":"Title: IBM Error when launching Scan task from Datacap Desktop. - United States\n\nText:\nDesktop; No data; Scan; VScan TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Receiving the following error message when attempting to launch up Scan task from Datacap Desktop:\n\"This batch has no data to process. Aborting.\" \n\nThen followed by this error: \n\"Unable to run queue.\" \n\nDIAGNOSING THE PROBLEM\nThe panel for TravelDocs contained a value with all upper-case letter [eg. TRAVELDOCS], which caused the error to occur when attempting to launch the Scan task from Datacap Desktop\n\nRESOLVING THE PROBLEM\nThe \"Bind DCO type to panel\" for Datacap Desktop is case-sensitive. Be sure the DCO name matches as it appears in Datacap Studio (both the spelling and case-sensitivity). \n\nLogon to TMWeb client. \n\nGo to Administrator tab \n\nSelect the VScan task from the Workflow. \n\nClick Setup under Program. \n\nThen change the value of the Panel to match what is in Datacap Studio. For example \"TRAVELDOCS\" to \"TravelDocs\" \n\nClick Save\n\n[\/support\/docview.wss?uid=swg21967312&aid=1] [\/support\/docview.wss?uid=swg21967312&aid=1]\n\n[\/support\/docview.wss?uid=swg21967312&aid=2] [\/support\/docview.wss?uid=swg21967312&aid=2]\n[\/support\/docview.wss?uid=swg21967312&aid=3] [\/support\/docview.wss?uid=swg21967312&aid=3]"}]},{"id":"TRAIN_Q414","question":"Is MQ V7.0 is going out of support?\n\nIs Websphere MQ V7.0 is going out of support?","answer":"IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z\/OS V7.0.1 and V7.0.0,","is_impossible":false,"contexts":[{"filename":"swg21674407.txt","text":"Title: IBM Announcement: End of Support for WebSphere MQ and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 and WebSphere MQ Telemetry V7.0.1 - United States\n\nText:\n NEWS\n\nABSTRACT\n IBM has withdrawn support for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ for z\/OS V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition for z\/OS V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1. \n\nCONTENT\n\n\nTAB NAVIGATION\n * WebSphere MQ and File Transfer Edition V7.0.1 and V7.0.0 \u2022 MQ Telemetry V7.0.1 selected tab\n\nTAB NAVIGATION\n * What were the end of support dates for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1?\n * Do these announcements affect WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, or WebSphere MQ Hypervisor Edition V7.0.1?\n * What replacement products are available?\n * How do I check which version I am currently running?\n * Is any information available to help me upgrade to a later version?\n * How do I purchase a support extension for my current version?\n * When a WebSphere MQ server product goes out of support, does the client and file transfer agent also go out of support?\n * Are these products still supported when they are bundled with another IBM product?\n * Is the WebSphere MQ V7.0 Resource Adapter supported in WebSphere Application Server?\n * Is documentation still available for these products?\n * How do I obtain installation images for these products if I still need them?\n * Is there an IBM MQ V9.0 or MQ V8.0 trial version available for download?\n\n\n\n[\/support\/docview.wss?uid=swg21674407&aid=1]\n\n\n\n\nWHAT ARE THE END OF SUPPORT DATES FOR WEBSPHERE MQ V7.0.1 AND V7.0.0, WEBSPHERE MQ FILE TRANSFER EDITION V7.0.1 AND V7.0.0, AND WEBSPHERE MQ TELEMETRY V7.0.1?\n\n * \n * Product Version Release Date End of Support Platforms WebSphere MQ V7.0.1 28 Aug 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-245] 30 Apr 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5\/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z\/OS V7.0.1 25 Sep 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-248] 30 Sep 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-150] z\/OS WebSphere MQ V7.0.0 16 Jun 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-068] 30 Apr 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] AIX, HP-UX (Itanium), HP-UX (PA-RISC), i5\/OS, Linux (POWER), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Solaris (x86-64), Windows (x86) WebSphere MQ for z\/OS V7.0.0 27 Jun 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-067] 30 Sep 2011 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS910-014] z\/OS WebSphere MQ File Transfer Edition V7.0.1 05 Jun 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-118] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Linux (x86-64), Linux (zSeries 64-bit), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z\/OS V7.0.1 12 Jun 2009 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS209-119] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z\/OS WebSphere MQ File Transfer Edition V7.0.0 05 Dec 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-331] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-158] AIX, HP-UX (Itanium), Linux (x86), Solaris (SPARC), Windows (x86) WebSphere MQ File Transfer Edition for z\/OS V7.0.0 12 Dec 2008 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS208-339] 30 Sep 2014 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS913-149] z\/OS WebSphere MQ Telemetry V7.0.1 27 Aug 2010 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS210-201] 30 Sep 2015 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS914-067] Linux (x86-64), Windows (x86) \n * \n * Review lifecycle dates for all IBM MQ and WebSphere MQ products [http:\/\/www.ibm.com\/software\/support\/lifecycleapp\/PLCSearch.wss?q=%28+%22IBM+MQ%22+OR+%22WebSphere+MQ%22+%29+AND+NOT+%28+Tivoli+OR+Adapter+OR+Broker+OR+Integrator+OR+Workflow+OR+%22Low+Latency+Messaging%22+%29]\n \n End of support information for WebSphere MQ V7.5 and WebSphere MQ Hypervisor Edition V7.5 [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg21996472]\n \n End of support information for WebSphere MQ V7.1, WebSphere MQ File Transfer Edition V7.0.4, V7.0.3 and V7.0.2, WebSphere MQ Advanced Message Security V7.0.1, and WebSphere MQ Hypervisor Edition V7.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg21980668]\n \n \n * Back to top\n\n\n\n\nDO THESE ANNOUNCEMENTS AFFECT WEBSPHERE MQ FILE TRANSFER EDITION V7.0.4, V7.0.3 AND V7.0.2, WEBSPHERE MQ ADVANCED MESSAGE SECURITY V7.0.1, OR WEBSPHERE MQ HYPERVISOR EDITION V7.0.1?\n\n * IBM has subsequently announced the end of support for these products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21980668] on all platforms including z\/OS:\n * \n * Lifecycle dates for WebSphere MQ V7.0 products [http:\/\/www.ibm.com\/software\/support\/lifecycleapp\/PLCSearch.wss?q=%28%22WebSphere+MQ+%22+AND+%227.0%22%29+OR+%28%22WebSphere+MQ+File+Transfer+Edition+%22+AND+%28%227.0.4%22+OR+%227.0.3%22+OR+%227.0.2%22%29%29+OR+%28%22WebSphere+MQ+Advanced+Message+Security+%22+AND+%227.0.1%22%29] \n * \n * Back to top\n\n\n\n\nWHAT REPLACEMENT PRODUCTS ARE AVAILABLE?\n\n * Replacements for WebSphere MQ V7.0.1 and V7.0.0 include IBM MQ or IBM MQ Advanced V9.0 and V8.0. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 Apri 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * Replacements for WebSphere MQ for z\/OS V7.0.1 and V7.0.0 include IBM MQ, IBM MQ Advanced, or IBM MQ Value Unit Edition for z\/OS V9.0 and V8.0.0.\n * Replacements for WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 include IBM MQ Advanced V9.0 and V8.0. WebSphere MQ Advanced V7.5 is also available (except on IBM i), but its end of support date is 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117]. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ and replace the former File Transfer Edition and Advanced Message Security products.\n * Replacements for WebSphere MQ File Transfer Edition for z\/OS V7.0.1 and V7.0.0 include IBM MQ Advanced for z\/OS V9.0 and V8.0.0. The Advanced license allows use of the Managed File Transfer and Advanced Message Security components which are now built into MQ for z\/OS and replace the former File Transfer Edition for z\/OS and Advanced Message Security for z\/OS products.\n * The replacement for WebSphere MQ Telemetry V7.0.1 is IBM MQ or IBM MQ Advanced V9.0 or V8.0, all of which include Telemetry as a component of the MQ product. WebSphere MQ or WebSphere MQ Advanced V7.5 are also available (except on IBM i), but their end of support date is 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-117].\n * \n * \n * Back to top\n\n\n\n\nHOW DO I CHECK WHICH VERSION I AM CURRENTLY RUNNING?\n\n * Follow these general instructions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21621707] or the IBM MQ Knowledge Center instructions [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.ref.adm.doc\/q083280_.htm] to display your IBM MQ or WebSphere MQ version on all platforms except for z\/OS with the command: dspmqver\n * On z\/OS, look for message CSQY000I [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.ref.doc\/csq_y.htm] in the MSTR joblog to determine your version.\n * Follow the IBM MQ Knowledge Center instructions [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.wmqfte.doc\/display_ver_cmd.htm] to display your Managed File Transfer or WebSphere MQ File Transfer Edition version with the command: fteDisplayVersion\n * WebSphere MQ Telemetry V7.0.1 only runs on WebSphere MQ V7.0.1 (fix pack 7.0.1.3 and later) on Linux (x86-64) and Windows (x86). Although there is no command to display the WebSphere MQ Telemetry version, if your WebSphere MQ version is V7.0.1 and you have a WebSphere MQ Telemetry service and channels [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.tt.doc\/tt_intro.htm] configured, then you are running WebSphere MQ Telemetry V7.0.1.\n * \n * Back to top\n\n\n \n[\/support\/docview.wss?uid=swg21674407&aid=2]\n\n \n\n\n\n\nIS ANY INFORMATION AVAILABLE TO HELP ME UPGRADE TO A LATER VERSION?\n\n * The IBM MQ and WebSphere MQ Migration Guide [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/aimsupport\/entry\/websphere_mq_ibm_mq_migration_guide] is available to view online or download:\n * IBM MQ and WebSphere MQ Migration Guide [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/aimsupport\/resource\/MQ_migration\/WMQ_Migration.pdf] \n * \n * The IBM Knowledge Center also includes information to assist you in migrating to a supported version of IBM MQ or WebSphere MQ:\n * Migrating and upgrading to IBM MQ V9.0 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.mig.doc\/q006180_.htm] Migrating and upgrading to IBM MQ V8.0 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.mig.doc\/q006180_.htm] Migrating and upgrading to WebSphere MQ V7.5 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.5.0\/com.ibm.mq.mig.doc\/q006180_.htm] \n * \n * The following WebSphere Support Technical Exchange presentations may be helpful if you are considering running multiple MQ installations on your system:\n * Webcast replay: WebSphere MQ Multi-Version - First Steps [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024276] Webcast replay: WebSphere MQ Multi-Version - Environment Considerations and Management [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024340] \n * \n * Back to top\n\n\n\n\nHOW DO I PURCHASE A SUPPORT EXTENSION FOR MY CURRENT VERSION?\n\n * Support extensions are available for an additional fee. To purchase extended support for WebSphere MQ or any of the other products, please contact your local IBM sales representative.\n * US Customers should contact Customer Support Operations at 1-877-426-6006, option #2. If you provide your IBM customer number, they can quickly find your sales representative.\n * Customers in other geographies should refer to the IBM directory of worldwide support contacts to find sales contact numbers in your region:\n * \n * IBM Directory of Worldwide Contacts [http:\/\/www.ibm.com\/planetwide\/] \n * \n * Back to top\n\n\n\n\nWHEN AN WEBSPHERE MQ SERVER PRODUCT GOES OUT OF SUPPORT, DOES THE CLIENT AND FILE TRANSFER AGENT ALSO GO OUT OF SUPPORT?\n\n * Yes. WebSphere MQ V7.0 clients and WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0 agents go out of support at the same time as the server.\n * \n * Back to top\n\n\n [\/support\/docview.wss?uid=swg21674407&aid=3] \n\n\n\n\nARE THESE PRODUCTS STILL SUPPORTED WHEN THEY ARE BUNDLED WITH ANOTHER IBM PRODUCT?\n\n * Yes, support is available for all bundled components until the IBM product that includes them is withdrawn from support. However, they are only supported when used by the bundling IBM product. Unrelated usage is not supported.\n * \n * Find the end of support date for your IBM software product [http:\/\/www.ibm.com\/software\/support\/lifecycle\/index_a_z.html] \n * \n * Back to top\n\n\n\n\nIS THE WEBSPHERE MQ V7.0 RESOURCE ADAPTER SUPPORTED IN WEBSPHERE APPLICATION SERVER?\n\n * Yes, the WebSphere MQ V7.0 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0] shipped with WebSphere Application Server V8.0 and V7.0 is supported through 30 April 2018 [https:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?subtype=ca&infotype=an&appname=iSource&supplier=897&letternum=ENUS916-143], when both of those versions of WebSphere Application Server end support, or longer if you purchase a WebSphere Application Server support extension.\n \n * Similarly, the WebSphere MQ V7.1 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0_0] shipped with WebSphere Application Server V8.5.x is supported as long as that version of WebSphere Application Server remains in support, or longer if you purchase a WebSphere Application Server support extension.\n \n * However, if you manually install your own copy of the WebSphere MQ V7.x Resource Adapter in WebSphere Application Server or any third-party Java EE server, it will go out of support with the corresponding WebSphere MQ server version.\n \n * The IBM MQ V8.0 and V9.0 Resource Adapters cannot be installed in WebSphere Application Server V8.5.x, V8.0 and V7.0 because those versions support JMS 1.1 while the IBM MQ Resource Adapters implement JMS 2.0. WebSphere Application Server V9.0 ships with the IBM MQ V9.0 Resource Adapter [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089#7dotx_0_0_0] and includes full support for JMS 2.0. The version of MQ Resource Adapter you use must be supported by your Java EE server but does not need to match the version of the queue managers to which you wish to connect.\n \n * Back to top\n\n \n\n\n\n\nIS DOCUMENTATION STILL AVAILABLE FOR THESE PRODUCTS?\n\n * Yes. Online documentation is available in the IBM Knowledge Center, while downloadable Information Center installations and PDF versions of the manuals are available from the MQ Library page.\n * \n * WebSphere MQ V7.0.1 Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.helphome.v70.doc\/WelcomePagev7r0.htm] WebSphere MQ V7.0.1 library of downloadable documentation [http:\/\/www.ibm.com\/software\/integration\/wmq\/library\/library701.html] WebSphere MQ V7.0.0 library of downloadable documentation [http:\/\/www.ibm.com\/software\/integration\/wmq\/library\/library700.html] WebSphere MQ File Transfer Edition V7.0.4 Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEP7X_7.0.4\/welcome\/WelcomePagev7r0.html] WebSphere MQ Telemetry V7.0.1 [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.tt.doc\/tt_intro.htm] \n * \n * Back to top\n\n\n\n\nHOW DO I OBTAIN INSTALLATION IMAGES FOR THESE PRODUCTS IF I STILL NEED THEM?\n\n * Installation images for WebSphere MQ V7.0.1 and V7.0.0, WebSphere MQ File Transfer Edition V7.0.1 and V7.0.0, and WebSphere MQ Telemetry V7.0.1 are no longer available from Passport Advantage [https:\/\/www.ibm.com\/software\/passportadvantage\/pao_customer.html]. Contact IBM if you have an urgent business need for these installation images.\n * \n * Back to top\n\n\n \n[\/support\/docview.wss?uid=swg21674407&aid=4]\n\n \n\n\n\n\nIS THERE AN IBM MQ V9.0 OR MQ V8.0 TRIAL VERSION AVAILABLE FOR DOWNLOAD?\n\n * You can obtain a full-featured trial version of IBM MQ to evaluate for 90 days:\n * \n * Try IBM MQ now [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/preLogin.do?pkgid=&S_SRCID=ESD-WSMQ-EVAL&source=ESD-WSMQ-EVAL&S_TACT=109J84RW&S_CMP=web_ibm_ws_appint_ct_wmq-ov&S_PKG=CR9H9ML&s=&id=2009-08-28+03%3A34%3A46.648052R&fam=&cat=&l=English+International&m=download&ibm-continue=Continue] \n * \n * Back to top\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ File Transfer Edition Not Applicable AIX, HP-UX, Linux, Solaris, Windows, z\/OS 7.0.1, 7.0 All Editions Business Integration WebSphere MQ Telemetry Not Applicable Linux, Windows Business Integration IBM MQ \nPRODUCT ALIAS\/SYNONYM\n WebSphere MQ WMQ"}]},{"id":"TRAIN_Q415","question":"Unable to login to FileNet Workplace XT 1.1.5.x. Getting error, Problem initializing encryption\/decryption with keyID.\n\n\n\nWe are having issue while trying to login Workplace XT. Getting the error message below as soon as I hit after giving credentials.\n\nError Message: com.filenet.wcm.api.EncryptionException: Problem initializing encryption\/decryption with keyId 7d3f93e3, size 256 bits. java.home=\/opt\/IBM\/WebSphere\/AppServer\/java\/jre. Cause: java.security. InvalidKeyException: Illegal key size or default parameters\n\nIBM WAS 8.5.5.9 Workplace XT 1.1.5","answer":"This behavior occurs if Workplace XT is configured to use Maximum strength keys (>128bit) during installation.","is_impossible":false,"contexts":[{"filename":"swg21501900.txt","text":"Title: IBM Unable to log on to FileNet WorkplaceXT receive an AE SecurityCheckFilter error - United States\n\nText:\nAE SecurityCheckFilter; JSSE; unlimited strength TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Unable to log on to FileNet WorkplaceXT - AE SecurityCheckFilter error \n\nSYMPTOM\nWhen attempting to log on to FileNet WorkplaceXT deployed on an IBM WebSphere Application Server, the following error is displayed : \n\nException Message: [Filter AE SecurityCheckFilter]: filter is unavailable. \nFilter AE SecurityCheckFilter: filter is unavailable. \n\n\nDIAGNOSING THE PROBLEM\nSystemOut.log may contain the following exception : \n\n\nProblem initializing encryption\/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\\AppServer\\java\\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters\ncom.filenet.wcm.api.EncryptionException: Problem initializing encryption\/decryption with keyId abcd1234, size 256 bits. java.home=<<WAS_home>>\\AppServer\\java\\jre. Cause: java.security.InvalidKeyException: Illegal key size or default parameters\nat com.filenet.wcm.api.impl.CryptoHelper.getCipher(CryptoHelper.java:93)\nat com.filenet.wcm.api.impl.CryptoHelper.doEncryptOrDecrypt(CryptoHelper.java:104)\nat com.filenet.wcm.api.impl.SessionImpl.getTokenSymmetric(SessionImpl.java:771)\nat com.filenet.wcm.api.impl.SessionImpl.getToken(SessionImpl.java:741)\nat com.filenet.ae.toolkit.server.util.credentials.UserTokenUtil.getUserToken(UserTokenUtil.java:131)\nat com.filenet.ae.toolkit.server.servlet.filter.SecurityCheckFilter.doFilter(SecurityCheckFilter.java:51)\n....\n\n\n\nRESOLVING THE PROBLEM\nThis behavior occurs if Workplace XT is configured to use Maximum strength keys (>128bit) during installation. In this case, the JRE used by the J2EE Application server, for example <<WAS_home>>\\AppServer\\java\\jre should contain unlimited strength policy files, otherwise it will be unable to encrypt \/ decrypt user tokens. \n\n \n\n * One option is to install the JSSE unlimited strength jar files for the JRE used by the J2EE Application Server. For IBM JREs, more info can be found at \n \n https:\/\/www.ibm.com\/developerworks\/java\/jdk\/security\/ [https:\/\/www.ibm.com\/developerworks\/java\/jdk\/security\/] \n \n \n * Another option is to regenerate the encryption keys using 128bit encryption which doesn't require the unlimited strength policy .jar files. Please refer to the P8 Infocenter for usage information on the com.filenet.wcm.api.util.MakeCryptoKeys utility."}]},{"id":"TRAIN_Q416","question":"Why are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality?\n\nWhy are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality? ","answer":"The documentation references a MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED and a MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE parameter that is supposed to be under the VIRTUAL_INTERVIEW_CONFIGURATION component.These component parameters are not automatically added as part of the database upgrade scripts.","is_impossible":false,"contexts":[{"filename":"swg21984301.txt","text":"Title: IBM Component parameters missing for Enable Hold and Virtual Interview Multiple Response functionality - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why are the component parameters missing for the Enable Hold and Virtual Interview Multiple Response functionality? \n\nCAUSE\n \n\nThe documentation references a MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED and a MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE parameter that is supposed to be under the VIRTUAL_INTERVIEW_CONFIGURATION component.These component parameters are not automatically added as part of the database upgrade scripts.\n\n\nANSWER\nTo enable the Enable Hold and Virtual Interview Multiple Response functionality you can manually create the component parameters. To do this go to the Admin > Components screen. \n\n 1. Search for the VIRTUAL_INTERVIEW_CONFIGURATION component. \n 2. Click on \"Edit\". \n 3. Click on \"Add Parameter\". \n 4. Set the new parameter with the name \"MULTIPLE_RESPONSES_FOR_HOLD_VI_ALLOWED\" and a value of \"True\" or \"False\" depending on your use of the functionality. \n 5. Click on \"Add Parameter\" again. \n 6. Set the new parameter with the name \"MULTIPLE_RESPONSES_INTERVIEW_AUTO_COMPLETE\" and a value of \"True\" or \"False\" depending on your use of the functionality. \n 7. Click on \"Save and Close\"."}]},{"id":"TRAIN_Q417","question":"What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed?\n\nWhat will I see if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed in CMOD v9.0?","answer":"You will see the \"table or view does not exist\" errors in your Systemlog","is_impossible":false,"contexts":[{"filename":"swg21672402.txt","text":"Title: IBM What happens if I run arssyscr -I instance_name -r without having Report Distribution enabled or installed? - United States\n\nText:\narssyscr; Report Distribution TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Running arssyscr -I instance_name -r during upgrade without RDF installed or enabled can lead to errors during load. \n\nSYMPTOM\nYou will see errors similar to (depending on database brand) \nDB Error: ORA-00942: table or view does not exist -- SQLSTATE=, SQLCODE=942, File=arsrddb.c, \nLine=951 in your systemlog\n\n\nCAUSE\nIssuing the arssyscr -I (instance name) -r command will trigger arssockd to check for the ARSDBBUNDT (RDF tables), which do not exist. \n\nDIAGNOSING THE PROBLEM\nYou will see the \"table or view does not exist\" errors in your Systemlog\n\nRESOLVING THE PROBLEM\nYou will need to rename the Report Distribution tables and delete the Application, Application Group and Folders by performing the steps below:\n\nYou are going to want to change the Report Distribution table name: \n\nThis test is done on DB2, but It should be the same for (Oracle or SQL \nServer). \nThat is [2] and [3], to rename to object name, you need to log on your \ndatabase command session: \n\n\n[1] Shutdown arssockd \n\n[2] Rename the Application Group name \n\nc:\\>db2 \"select agid, name, agid_name from arsag where name = 'System \nReport Distribution'\" \nAGID NAME \nAGID_NAME \n----------- ------------------------------------------------------------ \n--------- \n5007 System Report Distribution \nSR \n1 record(s) selected. \n\n\nc:\\>db2 \"update arsag set name = 'System Report Distribution DELETE' \nWHERE name = 'System Report Distribution'\" \nDB20000I The SQL command completed successfully. \n\n\n[3] Rename the Folder name \n\nc:\\>db2 \"select name from arsfol where name like 'System Report \nDistribution%'\" \nNAME \n------------------------------------------------------------ \nSystem Report Distribution - Bundles \nSystem Report Distribution - Deliveries \nSystem Report Distribution - Reports \n3 record(s) selected. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Bundles \nDELETE' where name = 'System Report Distribution - Bundles'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - \nDeliveries DELETE' where name = 'System Report Distribution - \nDeliveries'\" \nDB20000I The SQL command completed successfully. \n\nc:\\>db2 \"update arsfol set name = 'System Report Distribution - Reports \nDELETE' where name = 'System Report Distribution - Reports'\" \nDB20000I The SQL command completed successfully. \n\n[3] Start up arssockd \n\n[4] Use the Admin GUI to delete the RD Application group, Applications, \nand Folders"}]},{"id":"TRAIN_Q418","question":"Request for Sample working RUN() Function for ITX\n\n\n\nHi Guys,\n\n \n\nAnyone can share your simple RUN() function to trigger another map for ITX?\n\nAppreciate if some example can be shared!\n\n \n\nThanks in advance!!\n\nCheers!","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q419","question":"Does double the number of instances equal double through put in IIB \/ WMB?\n\nIf I double the number of instances of an IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) flow should I get double the through put?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q420","question":"How can I investigate hangs in MQ or in applications?\n\nAre there any tools to help get to the bottom of hangs? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q421","question":"Authorization code issue\n\nlike many of the other questions posted on here ... I'm having trouble authenticating my SPSS authorization code. Then there is an issue getting a license code back from the IBM proxy server to complete my download. Please help. ","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q422","question":"Help with Security Bulletin: Vulnerability in SSLv3 affects IID and WID (CVE-2014-3566)\n\nI need to understand details regarding Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer and WebSphere Integration Developer (CVE-2014-3566). Where can I find this information? ","answer":"CVE-ID: CVE-2014-3566 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: IBM Integration Designer and WebSphere Integration Developer could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21689914.txt","text":"Title: IBM Security Bulletin: Vulnerability in SSLv3 affects IBM Integration Designer and WebSphere Integration Developer (CVE-2014-3566) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled in IBM Integration Designer and WebSphere Integration Developer. \n\nVULNERABILITY DETAILS\nCVE-ID: CVE-2014-3566 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: IBM Integration Designer and WebSphere Integration Developer could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.\n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013] 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\nThis vulnerability affects some versions and releases of IBM Integration Designer and WebSphere Integration Developer.\n\nREMEDIATION\/FIXES\nIBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues.\n\nNote that other related products are also affected by this vulnerability. In the context of applying fixes, you will also want to update Installation Manager to version 1.8 or later.\n\nTo fully mitigate the POODLE vulnerability for server side components, an additional fix for IBM Integration Designer and WebSphere Integration Developer is required (JR51720): \n\n * WebSphere Integration Developer V7.5.1.2 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Integration+Designer&release=7.5.1.2&platform=All&function=aparId&apars=JR51720] \n * IBM Integration Designer V8.0.1.3 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Integration+Designer&release=8.0.1.3&platform=All&function=aparId&apars=JR51720] \n * IBM Integration Designer V8.5.5.0 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Integration+Designer&release=8.5.5&platform=All&function=aparId&apars=JR51720]\n\nWORKAROUNDS AND MITIGATIONS\nCustomers who cannot or do not want to install the fix recommended in the \"Remediation\/Fixes\" section of this security bulletin can disable the use of SSLv3 using manual configuration as described in \"Workarounds and Mitigations\" under the \"Client configuration files\" section in the following bulletin: Security Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21687173]\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] \nSecurity Bulletin: Vulnerability in SSLv3 affects IBM WebSphere Application Server (CVE-2014-3566) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21687173] \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 2014-11-14- 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\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere Integration Developer Security Linux, Windows 7.0.0.5, 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2, 6.1.2"}]},{"id":"TRAIN_Q423","question":"Report stuck in current queue\n\n\n\nWe have one report that has been showing in the admin current\nactivities status tab for 20+ days and we have had 2 full re-starts\nsince then. Also it appears we have interactive jobs staying around as well for past days and days.\n\nHow can we clean this up ?","answer":"Dropping the NC* tables that use this script: \n\nSteps:\n1. Stop the Cognos Service\n2. Take a physical backup of the Content Store or Notification database\n3. Select the appropriate folder for your content store or notification database type under <install>\/configuration\/schemas\/delivery\/<dbtype>\/ \n4. Run NC_DROP_<dbtype>.sql against the content store or notification database \n4. Restart Cognos Services. \n\nShould dropping the NC* tables not resolve the issue, then restore the content or notification store from the last backup version.","is_impossible":false,"contexts":[{"filename":"swg21371279.txt","text":"Title: IBM Scheduled Cognos BI reports are stuck in Pending state - United States\n\nText:\ndeployment TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Schedules Cognos Business Intelligience reports are not running. Scheduled reports are stuck in \"Pending\" state forever. \n\n- Renewing credentials does not resolve the issue. After credentials are renewed, user still receives the same error indicating that the credentials are invalid.\n\n- Enabling the \"Run as the Owner\" option does not resolve the issue \n\nSYMPTOM\nThe provided credentials are invalid.\nCNC-SEC-3403 The user account information is invalid, or it is missing in Content Manager. \nCAM-AAA-0102 Unable to authenticate. The user must select a namespace.\n...\nYour session has expired.\nSelect a namespace for authentication\n\n\nCAUSE\nContent Store corrupted.\n\nRESOLVING THE PROBLEM\nDropping the NC* tables that use this script: \n\nSteps:\n1. Stop the Cognos Service\n2. Take a physical backup of the Content Store or Notification database\n3. Select the appropriate folder for your content store or notification database type under <install>\/configuration\/schemas\/delivery\/<dbtype>\/ \n4. Run NC_DROP_<dbtype>.sql against the content store or notification database \n4. Restart Cognos Services. \n\nShould dropping the NC* tables not resolve the issue, then restore the content or notification store from the last backup version.\n\nRELATED INFORMATION\n Cognos Analytics Equivalent [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22001203]"}]},{"id":"TRAIN_Q424","question":"Unable to unistall Data Studio 3.1.1 on Windows\n\n\nWe 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\". How we can delete it?\n","answer":"Please try to uninstall all products including Install Manager \n(IM) then reinstall IM and Data Studio 4.1.2.","is_impossible":false,"contexts":[{"filename":"swg21991414.txt","text":"Title: IBM How can uninstall Data Studio 3.1.1 where Control Panel uninstall process gets an error? - United States\n\nText:\n 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\/]"}]},{"id":"TRAIN_Q425","question":"Upgrading the feature level to 8 for a VOB and ACLs\n\n We have upgraded to Clearcase version 8.0.1.3 ( on Windows 2008 Server) \nHow to upgrade the feature level of a single VOB from 5 to 8 ?","answer":"Execute the following two commands: \n\n 1. cleartool chflevel -replica <new feature level> replica:<replica name>@\\<vob tag>\n \n \n 2. cleartool chflevel -family <new feature level> vob:\\<vob tag>","is_impossible":false,"contexts":[{"filename":"swg21150579.txt","text":"Title: IBM Raise the feature level of a single VOB without increasing the feature level for other VOBs on the server - United States\n\nText:\nfeature level; chflevel; unreplicated; non-replicated; base; clearcase; 1150579; feature levels; replicated VOB TECHNOTE (FAQ)\n\nQUESTION\n How can you increase the feature level of a single non-replicated IBM Rational ClearCase VOB without increasing the feature level for the other VOBs on the server? \n\nANSWER\n \n\nExecute the following two commands: \n\n 1. cleartool chflevel -replica <new feature level> replica:<replica name>@\\<vob tag>\n \n \n 2. cleartool chflevel -family <new feature level> vob:\\<vob tag>\n\n\n\nNotes: * These commands are used for replicated VOB as well; however, there are special considerations that need to be taken when changing the feature level of a VOB that is replicated. Review the MultiSite Administrator's Guide under the topic of Feature levels [http:\/\/publib.boulder.ibm.com\/infocenter\/cchelp\/v7r0m1\/index.jsp?topic=\/com.ibm.rational.clearcase.cc_ms_admin.doc\/c_feature_levels.htm]for more details.\n \n * If a VOB is used in a UCM environment, the PVOB and all Component VOBs must be at the same feature level in order to utilize the features of that level.\n\n\nExample: \n\n 1. Open a command prompt and set into a view\n \n \n 2. Mount and change directory into the VOB tag\n \n \n 3. Describe the VOB to show current feature level\n \n > cleartool describe -long vob:.\n versioned object base \"\/vobstore\/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 2\n VOB storage host:pathname \"host1:\/vobstore\/test_vob.vbs\"\n VOB storage global pathname \"\/net\/host1\/vobstore\/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com\/jdoe\n group ibm.com\/group1\n Additional groups:\n group ibm.com\/other\n VOB holds objects from the following views:\n Attributes:\n FeatureLevel = 2 \n \n \n 4. Determine the replica name (by default is original)\n \n > cleartool lsreplica\n For VOB replica \"\/vobstore\/test_vob\":\n 23-Mar.09:36 jdoe replica \"original\"\n \n \n 5. Change the feature level. * Step 1:\n > cleartool chflevel -replica 3 replica:original@\/vobstore\/test_vob\n Replica feature level raised to 3.\n \n \n * Step 2:\n > cleartool chflevel -family 3 vob:\/vobstore\/test_vob\n cleartool: Warning: Raising the VOB family feature level may make it impossible to move this VOB to servers running an earlier revision of ClearCase and to create MultiSite replicas of this VOB on such servers.\n Raise VOB family feature level? [no] y\n VOB family feature level raised to 3.\n \n \n \n \n 6. Describe the VOB to show new feature level:\n \n > cleartool describe -long vob:.\n versioned object base \"\/vobstore\/test_vob\"\n created 23-Mar-01.09:36:29 by John Doe (jdoe.group1@host1)\n VOB family feature level: 3\n VOB storage host:pathname \"host1:\/vobstore\/test_vob.vbs\"\n VOB storage global pathname \"\/net\/host1\/vobstore\/test_vob.vbs\"\n database schema version: 53\n VOB ownership:\n owner ibm.com\/jdoe\n group ibm.com\/user\n Additional groups:\n group ibm.com\/other\n VOB holds object from the following views:\n Attributes:\n FeatureLevel = 3 \n\n\nReview the ClearCase Command Reference Guide on the topic of chflevel (cleartool man chflevel) for more information. \n\n \n\n\n\n\n\nRELATED INFORMATION\n#About Feature Levels and ClearCase [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21119269]"}]},{"id":"TRAIN_Q426","question":"Help with Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747)\n\nI need to understand details regarding Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747). Where can I find this information? ","answer":"CVEID: CVE-2017-1747 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1747]\nDESCRIPTION: A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/135520 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/135520] 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:H)","is_impossible":false,"contexts":[{"filename":"swg22012992.txt","text":"Title: IBM Security Bulletin: IBM MQ Clients can send a specially crafted message that could cause a channel to SIGSEGV. (CVE-2017-1747) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1747 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1747]\nDESCRIPTION: A specially crafted message could cause a denial of service in an IBM MQ application consuming messages that the application needs to perform data conversion on.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/135520 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/135520] 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:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V9 LTS\nMaintenance levels 9.0.0.0 - 9.0.0.2 \n\nIBM MQ V9 CD\nMaintenance levels 9.0.0 - 9.0.4\n\nREMEDIATION\/FIXES\nIBM MQ V9 LTS\nApply FixPack 9.0.0.3 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044508] \n\nIBM MQ V9 CD\nUpgrade to IBM MQ version 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 28 March 2018: Original Version published\n29 March 2018: Correction to bulletin to remove HPE Nonstop as affected platform. \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 IBM MQ Business Integration IBM MQ Advanced Business Integration IBM MQ Advanced for Developers"}]},{"id":"TRAIN_Q427","question":"Setting session timeouts and precedence\n\nWhat are the different ways to set the session timeout values. What takes more 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","is_impossible":false,"contexts":[{"filename":"swg21163875.txt","text":"Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\u00ae WebSphere\u00ae 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 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-config> \n * \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-timeout>60<\/session-timeout>\n * \n * \u00a0 \u00a0 \u00a0 <\/session-config>\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"}]},{"id":"TRAIN_Q428","question":"ITMv6 issue: Cognos reports run for an extended period, sometimes never finishes\n\nITMv6 issue: Cognos reports run for an extended period, sometimes never finishes\n\n","answer":"TCR 2.1\/2.1.1 server provides a default setting for heap size, a minimum size (xms) of 512MB and a maximum size (xmx) of 1024MB.","is_impossible":false,"contexts":[{"filename":"swg21585678.txt","text":"Title: IBM Increasing Java Heap Memory in IBM Tivoli Common Reporting 2.1\/2.1.1 - United States\n\nText:\nTCR - Tivoli Common Reporting TECHNOTE (FAQ)\n\nQUESTION\n How to increase Java heap memory size in IBM Tivoli Common Reporting (TCR) 2.1\/2.1.1 versions? \n\nCAUSE\nRunning a large scale report with Default java heap settings might result in OutOfMemory error\n\nANSWER\nTCR 2.1\/2.1.1 server provides a default setting for heap size, a minimum size (xms) of 512MB and a maximum size (xmx) of 1024MB. \n\nIn order to change the heap memory size, execute the following command:\n<INST>\/tipv2\/bin\/wsadmin.sh[.bat] -user <USERNAME> -password <PASSWORD> -f <INST>\/tipv2\/profiles\/TIPProfile\/bin\/changeMem.py --xms <MINVALUE> --xmx <MAXVALUE>\n\nwhere <INST> is the TCR Installation folder like \/opt\/IBM\/tivoli\n<MINVALUE> can be 1024 and <MAXVALUE> can be 1843 (1GB and 1.8GB respectively)\n\nNOTE: In order to avoid OutOfMemory error, it is recommended to be within the 2GB limit (for 32 bit architectures - maximum memory can be 2^32)\nFor 64-bit JVM, the maximum heap value can be upto 50% of the available physical memory. Reason being maximum memory will be 2^64 which is 16 exabytes which is a very huge number! \n1 exabyte = 1024*1024*1024 Gigabyte!\nPlease refer to the links provided in the 'Related Infomation' section to learn more on the Java sizing and heap information.\n\nTo test the JVM's maximum heap memory support, please follow the below test:\na) Open command line \/ shell script and navigate to <INST>\/tipv2\/java\/jre\/bin folder\nb) Execute this command: java -Xmx1843m hello\n- if java accepts this 1.8GB setting, then it will throw the \"class not found\" error for hello\n- if java does not accept this value, then it gives the \"Initialization error\" and \"Failed to instantiate heap\" message!\n- You can try to increase the value of Xmx and see where it breaks\n- For 32-bit JVM, it is not advised to set this value beyond 1843m but for 64-bit JVM, value can be upto 50% of the available physical memory.\n\nAfter setting the new values, restart the TCR server for the changes to take effect.\n\nRELATED INFORMATION\n Sizing the Java Heap [http:\/\/publib.boulder.ibm.com\/infocenter\/javasdk\/tools\/index.jsp?topic=%2Fcom.ibm.java.doc.igaa%2F_1vg000139b8b453-11951f1e7ff-8000_1001.html]\nJava code to Java Heap [http:\/\/www.ibm.com\/developerworks\/java\/library\/j-codetoheap\/index.html]"}]},{"id":"TRAIN_Q429","question":"Does Portal 7.0.0.2 CF20 support upgrading the DB2 JDBC Driver from 4.11.77 to 4.18.60?\n\nDoes Portal 7.0.0.2 CF20 support upgrading the DB2 JDBC Driver from 4.11.77 to 4.18.60?","answer":"IBM DB2 Universal JDBC Provider (XA) from DB2 z\/OS (type 4) Version and future fix packs All Applicable AIX OS Requires APAR PK93123 for DB2 on z\/OS V8.1 and V9.1. You can obtain the fix from DB2 on z\/OS support or IBMLINK.","is_impossible":false,"contexts":[{"filename":"swg27020885.txt","text":"Title: IBM WebSphere Portal V7.0.0.2 hardware and software requirements - United States\n\nText:\nDSRdoc; DSR; WPv7002eGA; hardware; software; requirements; portal 7.0.0.2; V7.0.0.2; 7002eGA PRODUCT DOCUMENTATION\n\nABSTRACT\n WebSphere Portal V7.0.0.2 hardware and software requirements for Server, Enable and Extend editions, as well as Lotus Web Content Management V7.0.0.2, on supported Linux platforms and distributions. \n\nCONTENT\n\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 Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019552] (#7019552 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27019552]). \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 Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019552] (#7019552 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27019552]). \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 Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 7.0.0.2 in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019552] (#7019552 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27019552]). \n\n\nWEBSPHERE PORTAL SERVER, ENABLE, EXTEND AND LOTUS WEB CONTENT MANAGEMENT 7.0.0.2\nTAB NAVIGATION\n * AIX - selected tab, \n * IBM i \n * Linux \n * Solaris \n * Windows \n\nTAB NAVIGATION\n * AIX \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable AIX OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable AIX OS A CD\/DVD drive is required.\n\nMemory All Applicable AIX OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor All Applicable AIX OS IBM POWER family of processors\n\n Back to top \n\nOperating Systems Operating System Attributes Notes AIX Platform listing of supported OS AIX 5.3 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System Technology and service release level requirements:\n * Technology level 12 or later\n * Service release 1 or later\n\nFor example: (5300-07-01)\n\nWebSphere Application Server requirements depending on operating system bit:\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nAIX 6.1 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System Technology and service release level requirements: \n\n * Technology level 5 or later. \n * Service release 2 or later. \n\nFor example: 6100-04-02 \n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS \n * 64-bit JDK\/WebSphere Application Server on 64-bit OS \n\nAIX 7.1 POWER System and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit: * 32-bit JDK\/WebSphere Application Server on 64-bit OS \n * 64-bit JDK\/WebSphere Application Server on 64-bit OS \n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm\/WebSphere]\n\n [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029137]\n\n1. IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 7.0.x after that date with extended support, Java SDK V5 is no longer included. It is recommended that you upgrade to IBM Java SDK V6.\n\n2. IBM Java SDK V6 will reach end of service in Apr 2018. If you continue to use WebSphere Application Server 7.0.x after that date with extended support, Java SDK V6 is no longer included.\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/xml\/index.html] All Applicable AIX OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/cea\/] All Applicable AIX OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/sca\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extremescale\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_eXtreme_Scale] All Applicable AIX OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/virtualenterprise\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Virtual_Enterprise] All Applicable AIX OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/IBM_Connections] All Applicable AIX OS Lotus Connections 2.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable AIX OS Lotus Connections 3.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable AIX OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable AIX OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable AIX OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable AIX OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable AIX OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable AIX OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/standard\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable AIX OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable AIX OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-enterprise.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5\/OS 6.1 and future fix packs All Applicable AIX OS DB2 for i5\/OS 7.1 and future fix packs All Applicable AIX OS DB2 for i5\/OS V5R4 and future fix packs All Applicable AIX OS DB2 for z\/OS 9.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable AIX OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z\/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z\/OS 10.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable AIX OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable AIX OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z\/OS 8.1 and future fix packs All Applicable AIX OS WebSphere Portal 7.0 works with DB2 for z\/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-workgroup.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable AIX OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable AIX OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable AIX OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable AIX OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable AIX OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable AIX OS See Note #3 Identity Management IBM z\/OS.e Security Server 1.6 and future fix packs All Applicable AIX OS IBM z\/OS.e Security Server 1.7 and future fix packs All Applicable AIX OS IBM z\/OS Security Server 1.6 and future fix packs All Applicable AIX OS IBM z\/OS Security Server 1.7 and future fix packs All Applicable AIX OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Microsoft Active Directory 2003 and future fix packs All Applicable AIX OS Microsoft Active Directory 2008 and future fix packs All Applicable AIX OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable AIX OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable AIX OS Novell eDirectory 8.7.3 and future fix packs All Applicable AIX OS Novell eDirectory 8.8 and future fix packs All Applicable AIX OS Sun Java System Directory Server 6.1 and future fix packs All Applicable AIX OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable AIX OS Sun Java System Directory Server 7.0 and future fix packs All Applicable AIX OS Tivoli Directory Server 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable AIX OS Tivoli Directory Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable AIX OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable AIX OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable AIX OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK\/JRE\/JDK 6.0 Update 17 and future fix packs All Applicable AIX OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable AIX OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable AIX OS DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 and future fix packs All Applicable AIX OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 IBM Application Connectivity to DB2 for z\/OS Feature Version and future fix packs All Applicable AIX OS IBM DB2 Universal JDBC Provider (XA) from DB2 z\/OS (type 4) Version and future fix packs All Applicable AIX OS Requires APAR PK93123 for DB2 on z\/OS V8.1 and V9.1. You can obtain the fix from DB2 on z\/OS support or IBMLINK. IBM Toolbox for Java\/JTOpen JDBC Driver 6.0 and future fix packs All Applicable AIX OS Check for the latest jt400.jar file at:http:\/\/sourceforge.net\/projects\/jt400\/files\/ [http:\/\/sourceforge.net\/projects\/jt400\/files\/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable AIX OS Microsoft SQL Server JDBC Driver 3.0 All Applicable AIX OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable AIX OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable AIX OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-metric-tool\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMLicenseMetricTool.html] All Applicable AIX OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-integrator\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryIntegrator.html] All Applicable AIX OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable AIX OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wps\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Process_Server] All Applicable AIX OS Security CA SiteMinder 6.0 and future fix packs All Applicable AIX OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable AIX OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable AIX OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/index.html] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable AIX OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/] (support) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/support\/] All Applicable AIX OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable AIX OS IBM PR\/SM any version and future fix packs All Applicable AIX OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable AIX OS WPAR: Product installed in System Workload Partition AIX 6.1 and future fix packs AIX 5.3 POWER System,\nAIX 6.1 POWER System Refer to the following technote for installation instructions: \n\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21426713 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21426713] \n\nWPAR: Product installed in System Workload Partition AIX 7.1 and future fix packs AIX 7.1 POWER System Web Browsers Apple Safari 4.0 and future fix packs All Applicable AIX OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable AIX OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable AIX OS Internet Explorer 6.0 SP2 on Windows XP SP1\/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable AIX OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable AIX OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable AIX OS Refer to the IE9 Support statement for more information:\n\n http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable AIX OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable AIX OS See Note #1 Opera 10.0 and future fix packs All Applicable AIX OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable AIX OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable AIX OS Apache HTTP Server 2.2 and future fix packs All Applicable AIX OS IBM HTTP Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable AIX OS IBM HTTP Server 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable AIX OS IBM HTTP Server for i5\/OS Any and future fix packs All Applicable AIX OS IBM HTTP Server for i5\/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z\/OS Any and future fix packs All Applicable AIX OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable AIX OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable AIX OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable AIX OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable AIX OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable AIX OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable AIX OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * IBM i \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable IBM i OS Minimum 5.0 GB free disk space with 6 disk arms (cache is desired) for installation for WebSphere Portal\n\nMedia Drive All Applicable IBM i OS A CD\/DVD drive is required.\n\nMemory All Applicable IBM i OS Physical memory: 8 GB minimum\nProduction environments and environments featuring multiple profiles will require more memory.\nNote: The amount of memory assigned to the *INTERACT pool should be set at a minimum of well over 1 GB and a maximum of 100%. If the *INTERACT pool cannot be given enough memory, then the database tasks have to be started with SBMJOB so that they run in the *BASE pool.\n\nProcessor All Applicable IBM i OS Recent System i5 and eServer i5 models with at least 3800 CPW\nSystem i model 820 with processor feature 2395\n\n Back to top \n\nOperating Systems Operating System Attributes Notes IBM i Platform listing of supported OS IBM i 5.4 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 IBM i 6.1 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 IBM i 7.1 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm\/WebSphere]\n\n [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/xml\/index.html] All Applicable IBM i OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/cea\/] All Applicable IBM i OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/sca\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extremescale\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_eXtreme_Scale] All Applicable IBM i OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/virtualenterprise\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Virtual_Enterprise] All Applicable IBM i OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/IBM_Connections] All Applicable IBM i OS Lotus Connections 2.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable IBM i OS Lotus Connections 3.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable IBM i OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable IBM i OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable IBM i OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable IBM i OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable IBM i OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable IBM i OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/standard\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable IBM i OS Requires hot fix BMUY-87SL83\n\nDatabases DB2 for i5\/OS 6.1 and future fix packs All Applicable IBM i OS DB2 for i5\/OS 7.1 and future fix packs All Applicable IBM i OS DB2 for i5\/OS V5R4 and future fix packs All Applicable IBM i OS DB2 for z\/OS 10.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable IBM i OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable IBM i OS Identity Management IBM Tivoli Directory Server for iSeries V5R4 and future fix packs All Applicable IBM i OS IBM Tivoli Directory Server for iSeries V6R1 and future fix packs All Applicable IBM i OS IBM Tivoli Directory Server for iSeries V7R1 and future fix packs All Applicable IBM i OS IBM z\/OS.e Security Server 1.6 and future fix packs All Applicable IBM i OS IBM z\/OS.e Security Server 1.7 and future fix packs All Applicable IBM i OS IBM z\/OS Security Server 1.6 and future fix packs All Applicable IBM i OS IBM z\/OS Security Server 1.7 and future fix packs All Applicable IBM i OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Microsoft Active Directory 2003 and future fix packs All Applicable IBM i OS Microsoft Active Directory 2008 and future fix packs All Applicable IBM i OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable IBM i OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable IBM i OS Novell eDirectory 8.7.3 and future fix packs All Applicable IBM i OS Novell eDirectory 8.8 and future fix packs All Applicable IBM i OS Sun Java System Directory Server 6.1 and future fix packs All Applicable IBM i OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable IBM i OS Sun Java System Directory Server 7.0 and future fix packs All Applicable IBM i OS Tivoli Directory Server 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable IBM i OS Tivoli Directory Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable IBM i OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable IBM i OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable IBM i OS J2SE 6.0 32-bit for IBM i V5R4\nProduct 5722JV1, option 11 with latest Java group PTF applied\nJ2SE 6.0 32-bit for IBM i V6R1\nProduct 5761JV1, option 11 with latest Java group PTF applied\nJ2SE 6.0 64-bit for IBM i V6R1\nProduct 5761JV1, option 12 with latest Java group PTF applied\n\nSun Java SDK\/JRE\/JDK 6.0 Update 17 and future fix packs All Applicable IBM i OS Java Developer Kit 6.0 64-bit for IBM i V5R4\nProduct 5722JV1, option 10 with latest Java group PTF applied \nJava Developer Kit 6.0 64-bit for IBM i V6R1\nProduct 5761JV1, option 10 with latest Java group PTF applied JDBC Drivers IBM Toolbox for Java\/JTOpen JDBC Driver 6.0 and future fix packs All Applicable IBM i OS Check for the latest jt400.jar file at:http:\/\/sourceforge.net\/projects\/jt400\/files\/ [http:\/\/sourceforge.net\/projects\/jt400\/files\/] Microsoft SQL Server JDBC Driver 3.0 All Applicable IBM i OS Miscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-metric-tool\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMLicenseMetricTool.html] All Applicable IBM i OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-integrator\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryIntegrator.html] All Applicable IBM i OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable IBM i OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wps\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Process_Server] All Applicable IBM i OS Security CA SiteMinder 6.0 and future fix packs All Applicable IBM i OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable IBM i OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable IBM i OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/index.html] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable IBM i OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/] (support) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/support\/] All Applicable IBM i OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable IBM i OS IBM PR\/SM any version and future fix packs All Applicable IBM i OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable IBM i OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable IBM i OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable IBM i OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable IBM i OS Internet Explorer 6.0 SP2 on Windows XP SP1\/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable IBM i OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable IBM i OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable IBM i OS Refer to the IE9 Support statement for more information:\n\n http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable IBM i OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable IBM i OS See Note #1 Opera 10.0 and future fix packs All Applicable IBM i OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable IBM i OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable IBM i OS Apache HTTP Server 2.2 and future fix packs All Applicable IBM i OS IBM HTTP Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable IBM i OS IBM HTTP Server 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable IBM i OS IBM HTTP Server for i5\/OS Any and future fix packs All Applicable IBM i OS IBM HTTP Server for i5\/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z\/OS Any and future fix packs All Applicable IBM i OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable IBM i OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable IBM i OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable IBM i OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable IBM i OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable IBM i OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable IBM i OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Red Hat Enterprise Linux (RHEL) \n * Red Hat Enterprise Linux (RHEL) Server \n * Red Hat Enterprise Linux (RHEL) Workstation \n * SUSE Linux Enterprise Desktop (SLED) \n * SUSE Linux Enterprise Server (SLES) \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Linux OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Linux OS A CD\/DVD drive is required.\n\nMemory All Applicable Linux OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor Red Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES x86-32,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES x86-64,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 Desktop x86-32,\nRed Hat Enterprise Linux (RHEL) 4 Update 6 WS x86-32,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-32,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-64,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Desktop editions x86-32,\nRed Hat Enterprise Linux (RHEL) Server 6 x86-32,\nRed Hat Enterprise Linux (RHEL) Server 6 x86-64,\nRed Hat Enterprise Linux (RHEL) Workstation 6 x86-32,\nRed Hat Enterprise Linux (RHEL) Workstation 6 x86-64,\nSUSE Linux Enterprise Desktop (SLED) 10.0 SP2 x86-32,\nSUSE Linux Enterprise Desktop (SLED) 11.0 x86-32,\nSUSE Linux Enterprise Server (SLES) 10 SP2 x86-32,\nSUSE Linux Enterprise Server (SLES) 10 SP2 x86-64,\nSUSE Linux Enterprise Server (SLES) 11 x86-32,\nSUSE Linux Enterprise Server (SLES) 11 x86-64,\nSUSE Linux Enterprise Server (SLES) 9 SP4 x86-32,\nSUSE Linux Enterprise Server (SLES) 9 SP4 x86-64 Processor: CPU speeds of late-model, mid-range to high-end servers are recommended (32-bit or 64-bit support). Pentium 800 MHz or equivalent at a minimum. Production environments should consider the Pentium 4 processor at 1.4 GHz or higher. AMD Opteron, Intel EM64T\n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES POWER System,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform POWER System,\nRed Hat Enterprise Linux (RHEL) Server 6 POWER System,\nSUSE Linux Enterprise Server (SLES) 10 SP2 POWER System,\nSUSE Linux Enterprise Server (SLES) 11 POWER System,\nSUSE Linux Enterprise Server (SLES) 9 SP4 POWER System IBM System i (iSeries) IBM System p (pSeries), IBM OpenPower, or IBM BladeCenter.\nSystem p includes IBM system product lines System i5 models that support LPAR (64-bit support only) with minimum of 450 CPW in Linux Partition, System p models that support Linux (64-bit support only), BladeCenter JS20, and OpenPower that are based on IBM System p architecture technology and run the same Linux distributions from Red Hat and Novell SUSE.\n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES System z,\nRed Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform System z,\nRed Hat Enterprise Linux (RHEL) Server 6 System z,\nSUSE Linux Enterprise Server (SLES) 10 SP2 System z,\nSUSE Linux Enterprise Server (SLES) 11 System z,\nSUSE Linux Enterprise Server (SLES) 9 SP4 System z System z processors\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Linux Platform listing of supported OS Red Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS \n * 64-bit JDK\/WebSphere Application Server on 64-bit OS \n\nRed Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 Red Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 Red Hat Enterprise Linux (RHEL) 4 Update 6 AS\/ES x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Red Hat Enterprise Linux (RHEL) 4 Update 6 Desktop x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) 4 Update 6 WS x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 Red Hat Enterprise Linux (RHEL) 5 Update 2 Advanced Platform x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Red Hat Enterprise Linux (RHEL) 5 Update 2 Desktop editions x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 Red Hat Enterprise Linux (RHEL) Server 6 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System WebSphere Application Server requirements depending on operating system bit:\n\n\u2022 32-bit JDK\/WebSphere Application Server on 64-bit OS\n\u2022 64-bit JDK\/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Server 6 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z WebSphere Application Server requirements depending on operating system bit:\n\n\u2022 64-bit JDK\/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Server 6 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 WebSphere Application Server requirements depending on operating system bit:\n\n\u2022 32-bit JDK\/WebSphere Application Server on 32-bit OS Red Hat Enterprise Linux (RHEL) Server 6 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 WebSphere Application Server requirements depending on operating system bit:\n\n\u2022 32-bit JDK\/WebSphere Application Server on 64-bit OS\n\u2022 64-bit JDK\/WebSphere Application Server on 64-bit OS Red Hat Enterprise Linux (RHEL) Workstation 6 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 WebSphere Application Server requirements depending on operating system bit:\n\n\u2022 32-bit JDK\/WebSphere Application Server on 32-bit OS Red Hat Enterprise Linux (RHEL) Workstation 6 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #8 SUSE Linux Enterprise Desktop (SLED) 10.0 SP2 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 SUSE Linux Enterprise Desktop (SLED) 11.0 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #2 SUSE Linux Enterprise Server (SLES) 10 SP2 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 SUSE Linux Enterprise Server (SLES) 10 SP2 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 SUSE Linux Enterprise Server (SLES) 10 SP2 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 SUSE Linux Enterprise Server (SLES) 10 SP2 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #6 SUSE Linux Enterprise Server (SLES) 11 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #6 SUSE Linux Enterprise Server (SLES) 11 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z WebSphere Application Server requirements depending on operating system bit:\n\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nSUSE Linux Enterprise Server (SLES) 11 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 SUSE Linux Enterprise Server (SLES) 11 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 SUSE Linux Enterprise Server (SLES) 9 SP4 POWER System and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: POWER System See Note #7 SUSE Linux Enterprise Server (SLES) 9 SP4 System z and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: System z See Note #8 SUSE Linux Enterprise Server (SLES) 9 SP4 x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #5 SUSE Linux Enterprise Server (SLES) 9 SP4 x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #7 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm\/WebSphere]\n\n [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/xml\/index.html] All Applicable Linux OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/cea\/] All Applicable Linux OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/sca\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extremescale\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_eXtreme_Scale] All Applicable Linux OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/virtualenterprise\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Virtual_Enterprise] All Applicable Linux OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/IBM_Connections] All Applicable Linux OS Lotus Connections 2.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Linux OS Lotus Connections 3.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Linux OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Linux OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Linux OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Linux OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Linux OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Linux OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/standard\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Linux OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Linux OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-enterprise.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5\/OS 6.1 and future fix packs All Applicable Linux OS DB2 for i5\/OS 7.1 and future fix packs All Applicable Linux OS DB2 for i5\/OS V5R4 and future fix packs All Applicable Linux OS DB2 for z\/OS 9.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Linux OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z\/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z\/OS 10.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Linux OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Linux OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z\/OS 8.1 and future fix packs All Applicable Linux OS WebSphere Portal 7.0 works with DB2 for z\/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-workgroup.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Linux OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Linux OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Linux OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Linux OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Linux OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Linux OS See Note #3 Identity Management IBM z\/OS.e Security Server 1.6 and future fix packs All Applicable Linux OS IBM z\/OS.e Security Server 1.7 and future fix packs All Applicable Linux OS IBM z\/OS Security Server 1.6 and future fix packs All Applicable Linux OS IBM z\/OS Security Server 1.7 and future fix packs All Applicable Linux OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Microsoft Active Directory 2003 and future fix packs All Applicable Linux OS Microsoft Active Directory 2008 and future fix packs All Applicable Linux OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Linux OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Linux OS Novell eDirectory 8.7.3 and future fix packs All Applicable Linux OS Novell eDirectory 8.8 and future fix packs All Applicable Linux OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Linux OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Linux OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Linux OS Tivoli Directory Server 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Linux OS Tivoli Directory Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Linux OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Linux OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Linux OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK\/JRE\/JDK 6.0 Update 17 and future fix packs All Applicable Linux OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Linux OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Linux OS DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 and future fix packs All Applicable Linux OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 IBM Application Connectivity to DB2 for z\/OS Feature Version and future fix packs All Applicable Linux OS IBM DB2 Universal JDBC Provider (XA) from DB2 z\/OS (type 4) Version and future fix packs All Applicable Linux OS Requires APAR PK93123 for DB2 on z\/OS V8.1 and V9.1. You can obtain the fix from DB2 on z\/OS support or IBMLINK. IBM Toolbox for Java\/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Linux OS Check for the latest jt400.jar file at:http:\/\/sourceforge.net\/projects\/jt400\/files\/ [http:\/\/sourceforge.net\/projects\/jt400\/files\/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Linux OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Linux OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Linux OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Linux OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-metric-tool\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMLicenseMetricTool.html] All Applicable Linux OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-integrator\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryIntegrator.html] All Applicable Linux OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Linux OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wps\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Process_Server] All Applicable Linux OS Security CA SiteMinder 6.0 and future fix packs All Applicable Linux OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Linux OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Linux OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/index.html] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Linux OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/] (support) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/support\/] All Applicable Linux OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version and future fix packs All Applicable Linux OS IBM PR\/SM any version and future fix packs All Applicable Linux OS KVM in SUSE Linux Enterprise Server (SLES) 11 SUSE Linux Enterprise Server (SLES) 11 POWER System,\nSUSE Linux Enterprise Server (SLES) 11 System z,\nSUSE Linux Enterprise Server (SLES) 11 x86-32,\nSUSE Linux Enterprise Server (SLES) 11 x86-64 Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Linux OS VMware ESX 4.0 and future releases, mod levels and fix packs All Applicable Linux OS VMware ESXi 4.0 and future releases, mod levels and fix packs All Applicable Linux OS z\/VM 6.1 and future fix packs (overview) [http:\/\/www.vm.ibm.com\/] All Applicable Linux OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Linux OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Linux OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Linux OS Internet Explorer 6.0 SP2 on Windows XP SP1\/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Linux OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Linux OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Linux OS Refer to the IE9 Support statement for more information:\n\n http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Linux OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Linux OS See Note #1 Opera 10.0 and future fix packs All Applicable Linux OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Linux OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Linux OS Apache HTTP Server 2.2 and future fix packs All Applicable Linux OS IBM HTTP Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Linux OS IBM HTTP Server 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Linux OS IBM HTTP Server for i5\/OS Any and future fix packs All Applicable Linux OS IBM HTTP Server for i5\/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z\/OS Any and future fix packs All Applicable Linux OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Linux OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Linux OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Linux OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Linux OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Linux OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Linux OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Solaris \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n * Processor \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Solaris OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Solaris OS A CD\/DVD drive is required.\n\nMemory All Applicable Solaris OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\nProcessor Solaris 10 x86-64 AMD Opteron (64 bit kernel support only); Intel EM64T (64 bit kernel support only) \n\n Back to top \n\nOperating Systems Operating System Attributes Notes Solaris Platform listing of supported OS Solaris 10 SPARC and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: SPARC WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/Application Server on 64-bit OS\n * 64-bit JDK\/Application Server on 64-bit OS\n\nSolaris 10 x86-64 and future OS fix packs Bitness: 64 Bit Exploit\nHardware platform: x86-64 See Note #8 Solaris 9 SPARC and future OS fix packs Bitness: 32 Bit\nHardware platform: SPARC WebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS \n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm\/WebSphere]\n\n [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/xml\/index.html] All Applicable Solaris OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/cea\/] All Applicable Solaris OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/sca\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extremescale\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_eXtreme_Scale] All Applicable Solaris OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/virtualenterprise\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Virtual_Enterprise] All Applicable Solaris OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/IBM_Connections] All Applicable Solaris OS Lotus Connections 2.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Solaris OS Lotus Connections 3.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Solaris OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Solaris OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Solaris OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Solaris OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Solaris OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Solaris OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/standard\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Solaris OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Solaris OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-enterprise.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5\/OS 6.1 and future fix packs All Applicable Solaris OS DB2 for i5\/OS 7.1 and future fix packs All Applicable Solaris OS DB2 for i5\/OS V5R4 and future fix packs All Applicable Solaris OS DB2 for z\/OS 9.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Solaris OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z\/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z\/OS 10.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Solaris OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Solaris OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z\/OS 8.1 and future fix packs All Applicable Solaris OS WebSphere Portal 7.0 works with DB2 for z\/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-workgroup.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Solaris OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Solaris OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Solaris OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Solaris OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Solaris OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Solaris OS See Note #3 Identity Management IBM z\/OS.e Security Server 1.6 and future fix packs All Applicable Solaris OS IBM z\/OS.e Security Server 1.7 and future fix packs All Applicable Solaris OS IBM z\/OS Security Server 1.6 and future fix packs All Applicable Solaris OS IBM z\/OS Security Server 1.7 and future fix packs All Applicable Solaris OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Microsoft Active Directory 2003 and future fix packs All Applicable Solaris OS Microsoft Active Directory 2008 and future fix packs All Applicable Solaris OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Solaris OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Solaris OS Novell eDirectory 8.7.3 and future fix packs All Applicable Solaris OS Novell eDirectory 8.8 and future fix packs All Applicable Solaris OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Solaris OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Solaris OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Solaris OS Tivoli Directory Server 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Solaris OS Tivoli Directory Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Solaris OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Solaris OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Solaris OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK\/JRE\/JDK 6.0 Update 17 and future fix packs All Applicable Solaris OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Solaris OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Solaris OS DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 and future fix packs All Applicable Solaris OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 IBM Application Connectivity to DB2 for z\/OS Feature Version and future fix packs All Applicable Solaris OS IBM DB2 Universal JDBC Provider (XA) from DB2 z\/OS (type 4) Version and future fix packs All Applicable Solaris OS Requires APAR PK93123 for DB2 on z\/OS V8.1 and V9.1. You can obtain the fix from DB2 on z\/OS support or IBMLINK. IBM Toolbox for Java\/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Solaris OS Check for the latest jt400.jar file at:http:\/\/sourceforge.net\/projects\/jt400\/files\/ [http:\/\/sourceforge.net\/projects\/jt400\/files\/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Solaris OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Solaris OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Solaris OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Solaris OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-metric-tool\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMLicenseMetricTool.html] All Applicable Solaris OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-integrator\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryIntegrator.html] All Applicable Solaris OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Solaris OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wps\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Process_Server] All Applicable Solaris OS Security CA SiteMinder 6.0 and future fix packs All Applicable Solaris OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Solaris OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Solaris OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/index.html] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Solaris OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/] (support) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/support\/] All Applicable Solaris OS Virtualization IBM PR\/SM any version and future fix packs All Applicable Solaris OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Solaris OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Solaris OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Solaris OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Solaris OS Internet Explorer 6.0 SP2 on Windows XP SP1\/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Solaris OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Solaris OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Solaris OS Refer to the IE9 Support statement for more information:\n\n http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Solaris OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Solaris OS See Note #1 Opera 10.0 and future fix packs All Applicable Solaris OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Solaris OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Solaris OS Apache HTTP Server 2.2 and future fix packs All Applicable Solaris OS IBM HTTP Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Solaris OS IBM HTTP Server 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Solaris OS IBM HTTP Server for i5\/OS Any and future fix packs All Applicable Solaris OS IBM HTTP Server for i5\/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z\/OS Any and future fix packs All Applicable Solaris OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Solaris OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Solaris OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Solaris OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Solaris OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Solaris OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Solaris OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nTAB NAVIGATION\n * Windows 7 \n * Windows Server 2003 \n * Windows Server 2008 \n * Windows Vista \n * Windows XP \n\n\n\n\nOUTLINE\n * Hardware Requirements * Disk Space \n * Media Drive \n * Memory \n \n \n * Software Requirements * Operating System \n * Application Servers \n \n \n * Optional Supported Software * Application Servers \n * Collaboration \n * Databases \n * Identity Management \n * Java Technology \n * JDBC Drivers \n * Miscellaneous \n * Process Server \n * Security \n * Tools \n * Virtualization \n * Web Browsers \n * WebDAV Client \n * Web Servers \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Disk Space All Applicable Windows OS Minimum 2.5 GB free disk space for installation for WebSphere Portal\nMinimum 1.4 GB free disk space for installation for WebSphere Application Server\nMinimum 4 GB total disk space recommended for installation\n\nMedia Drive All Applicable Windows OS A CD\/DVD drive is required.\n\nMemory All Applicable Windows OS Physical memory requirements and recommendations for WebSphere Portal:\n\n * Under minimal load, WebSphere Portal can function with 2GB of RAM and a remote database.\n * In a production environment, 4GB is an optimal starting point for RAM.\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Windows Platform listing of supported OS Windows 7 Enterprise x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n\nWindows 7 Enterprise x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nWindows 7 Professional x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n\nWindows 7 Professional x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Support for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nWindows Server 2003 R2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 Base Level Service: SP2\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n\nWindows Server 2003 R2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Base Level Service: SP2\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nWindows Server 2003 SP2 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2003 SP2 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2003 SP2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2003 SP2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 R2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Datacenter Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Datacenter Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Enterprise Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Enterprise Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Server 2008 SP2 Standard Edition x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 See Note #4 Windows Server 2008 SP2 Standard Edition x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 See Note #6 Windows Vista Enterprise x86-32 Bitness: 32 Bit\nHardware platform: x86-32 Supported for developer platform only\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n\nWindows Vista Enterprise x86-64 Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\nWindows XP SP2 Professional x86-32 and future OS fix packs Bitness: 32 Bit\nHardware platform: x86-32 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n\nWindows XP SP2 Professional x86-64 and future OS fix packs Bitness: 32 Bit, 64 Bit Exploit\nHardware platform: x86-64 Supported for developer platform only.\n\nWebSphere Application Server requirements depending on operating system bit:\n\n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n\n Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers WebSphere Application Server 7.0.0.19 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS Download mandatory APAR PM52049 for WebSphere Application server 7.0.0.19 from this site -\n\n Fix Central Link for PM52049 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFix?product=ibm\/WebSphere\/WebSphere+Application+Server&fixids=7.0.0.19-WS-WAS-IFPM52049&source=dbluesearch&function=fixId&parent=ibm\/WebSphere]\n\n [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029137]\n\n Back to top \n\nOptional Supported Software Group Product Applicable OS Notes Application Servers WebSphere Application Server Feature Pack for XML 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/xml\/index.html] All Applicable Windows OS WebSphere Application Server V7 Feature Pack for Communications Enabled Applications 1.0.0.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/cea\/] All Applicable Windows OS WebSphere Application Server V7 Feature Pack for Service Component Architecture 1.0.1.7 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/featurepacks\/sca\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS WebSphere eXtreme Scale 7.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extremescale\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_eXtreme_Scale] All Applicable Windows OS Requires version 7.1.0.0 WebSphere Virtual Enterprise 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/virtualenterprise\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Virtual_Enterprise] All Applicable Windows OS Requires fix pack version 6.1.1.2 Collaboration IBM Connections 3.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/IBM_Connections] All Applicable Windows OS Lotus Connections 2.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Windows OS Lotus Connections 3.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/connections\/index.html] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Connections] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Quickr for Domino 8.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Windows OS Lotus Quickr for Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_Domino] All Applicable Windows OS Lotus Quickr for WebSphere Portal 8.1.1 Feature Packs and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Windows OS Lotus Quickr for WebSphere Portal 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/quickr\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Lotus\/Lotus_Quickr_for_WebSphere_Portal] All Applicable Windows OS Lotus Sametime Entry 8.0 and future mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Windows OS IBM Lotus Sametime Entry 8.0.2 requires hot fix BMUY-87SL83 \n\nLotus Sametime Entry 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/entry\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Windows OS Requires hot fix BMUY-87SL83\n\nLotus Sametime Standard 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/sametime\/standard\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/sametime\/support.html] All Applicable Windows OS Requires hot fix BMUY-87SL83\n\nDatabases Apache Derby 10.3 and future fix packs All Applicable Windows OS Not supported in a production environment.\n\nDB2 9 for Linux, UNIX and Windows 9.1.0.9 and future fix packs All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Enterprise Server Edition 9.7.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-enterprise.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\n Database parameter 'cur_commit' must be set to 'DISABLED' for database of WebSphere Portal 7\n\nDB2 for i5\/OS 6.1 and future fix packs All Applicable Windows OS DB2 for i5\/OS 7.1 and future fix packs All Applicable Windows OS DB2 for i5\/OS V5R4 and future fix packs All Applicable Windows OS DB2 for z\/OS 9.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Windows OS High Availability Disaster Recovery (HADR) Feature is supported.\n\n WebSphere Portal 7.0 works with DB2 for z\/OS V9.1 - PUT level 0912.\n\n The following are required:\n\n * APAR PK75093 or later\n * APAR PK92163:\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK92163]\n * APAR PK68265\n\nDB2 for z\/OS 10.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2zos\/] All Applicable Windows OS DB2 pureScale Feature for Enterprise Server Edition 9.8.0.3 and future fix packs All Applicable Windows OS Requires 7.0.0.1 CF007 or higher.\n\n Refer to the steps documented here: http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Configuring_WebSphere_Portal_V7.0.0.1_with_DB2_pureScale?open]\n\nDB2 Universal Database for z\/OS 8.1 and future fix packs All Applicable Windows OS WebSphere Portal 7.0 works with DB2 for z\/OS V8.1 - PUT level 0912 or later service level.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nDB2 Workgroup Server Edition 9.5.0.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/data\/db2\/linux-unix-windows\/edition-workgroup.html] (support) [http:\/\/www.ibm.com\/software\/data\/db2\/support\/db2_9\/] All Applicable Windows OS Includes Workgroup Server, Enterprise Server, and Express Server editions.\n\n High Availability Disaster Recovery (HADR) Feature is supported.\n\nMicrosoft SQL Server Enterprise Edition 2005 SP2 and future fix packs All Applicable Windows OS Microsoft SQL Server Enterprise Edition 2008 and future fix packs All Applicable Windows OS Microsoft SQL Server Enterprise Edition 2008 R2 All Applicable Windows OS Oracle Database 10g Enterprise Edition Release 1 10.1.0.5 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Enterprise Edition Release 2 10.2.0.4 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Standard Edition Release 1 10.1.0.5 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 10g Standard Edition Release 2 10.2.0.4 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.6 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 1 11.1.0.7 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Enterprise Edition Release 2 11.2.0.2 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.6 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 1 11.1.0.7 and future fix packs All Applicable Windows OS See Note #3 Oracle Database 11g Standard Edition Release 2 11.2.0.2 and future fix packs All Applicable Windows OS See Note #3 Identity Management IBM z\/OS.e Security Server 1.6 and future fix packs All Applicable Windows OS IBM z\/OS.e Security Server 1.7 and future fix packs All Applicable Windows OS IBM z\/OS Security Server 1.6 and future fix packs All Applicable Windows OS IBM z\/OS Security Server 1.7 and future fix packs All Applicable Windows OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Microsoft Active Directory 2003 and future fix packs All Applicable Windows OS Microsoft Active Directory 2008 and future fix packs All Applicable Windows OS Microsoft Active Directory Application Mode (ADAM) 2003 and future fix packs All Applicable Windows OS Microsoft AD LDS(Lightweight Directory Services) Windows 2008 and future fix packs All Applicable Windows OS Novell eDirectory 8.7.3 and future fix packs All Applicable Windows OS Novell eDirectory 8.8 and future fix packs All Applicable Windows OS Sun Java System Directory Server 6.1 and future fix packs All Applicable Windows OS Service Pack 10 or later is required. Sun Java System Directory Server 6.3 and future fix packs All Applicable Windows OS Sun Java System Directory Server 7.0 and future fix packs All Applicable Windows OS Tivoli Directory Server 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Windows OS Tivoli Directory Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Windows OS Fix pack 4 or later is required. Tivoli Directory Server 6.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryServer.html] All Applicable Windows OS Java Technology IBM Runtime Environment, Java Technology Edition 6.0 and future mod levels and fix packs All Applicable Windows OS Requirements:\n\n * Java version included or recommended by WebSphere Application Server 7.0.0.19.\n\nSun Java SDK\/JRE\/JDK 6.0 Update 17 and future fix packs All Applicable Windows OS Supported Java runtime environments 1.5.x or 1.6.x (requires one) for the Web Content Management authoring portlet\n\nJDBC Drivers Apache Derby 10.3 JDBC 4.0 and future fix packs All Applicable Windows OS Derby is a non-production environment. V10.3.3.1 or later is required. DataDirect Connect for JDBC 4.0 (type 4) and future fix packs All Applicable Windows OS DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 and future fix packs All Applicable Windows OS DB2 9.5 and DB2 9.7 require DB2 Driver for JDBC and SQLJ (type 2\/4) 4.0 IBM Application Connectivity to DB2 for z\/OS Feature Version and future fix packs All Applicable Windows OS IBM DB2 Universal JDBC Provider (XA) from DB2 z\/OS (type 4) Version and future fix packs All Applicable Windows OS Requires APAR PK93123 for DB2 on z\/OS V8.1 and V9.1. You can obtain the fix from DB2 on z\/OS support or IBMLINK. IBM Toolbox for Java\/JTOpen JDBC Driver 6.0 and future fix packs All Applicable Windows OS Check for the latest jt400.jar file at:http:\/\/sourceforge.net\/projects\/jt400\/files\/ [http:\/\/sourceforge.net\/projects\/jt400\/files\/] Microsoft SQL Server JDBC Driver 2.0 and future fix packs All Applicable Windows OS Microsoft SQL Server JDBC Driver 3.0 All Applicable Windows OS Oracle JDBC Driver (XA) 10g Any and future fix packs All Applicable Windows OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nOracle JDBC Driver (XA) 11g 11.2.0.2 and future fix packs All Applicable Windows OS Oracle 11g JDBC Driver Thin (type 4) (11.2.0.2 or higher)\n\n Requires the ojdbc6.jar file.\n\nMiscellaneous IBM License Metric Tool 7.2.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-metric-tool\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMLicenseMetricTool.html] All Applicable Windows OS Tivoli Directory Integrator 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-integrator\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMDirectoryIntegrator.html] All Applicable Windows OS Tivoli License Compliance Manager 2.3 Fixpack 1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Windows OS Process Server WebSphere Process Server 7.0.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wps\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Process_Server] All Applicable Windows OS Security CA SiteMinder 6.0 and future fix packs All Applicable Windows OS Tivoli Access Manager for e-business 6.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Windows OS Tivoli Access Manager for e-business 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliAccessManagerfore-business.html] All Applicable Windows OS Tools Rational Application Developer for WebSphere Software 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/index.html] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Windows OS WebSphere Portlet Factory 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/] (support) [http:\/\/www.ibm.com\/software\/genservers\/portletfactory\/support\/] All Applicable Windows OS Virtualization IBM PR\/SM any version and future fix packs All Applicable Windows OS Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 and future fix packs All Applicable Windows OS VMware ESX 4.0 and future releases, mod levels and fix packs All Applicable Windows OS VMware ESXi 4.0 and future releases, mod levels and fix packs All Applicable Windows OS Web Browsers Apple Safari 4.0 and future fix packs All Applicable Windows OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nGoogle Chrome 8 and future releases, mod levels and fix packs All Applicable Windows OS Refer to the following link for Known limitations when using Google Chrome and Apple Safari Web browsers with WebSphere Portal V7.0.x:\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at\n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 6.0 SP2 and future fix packs All Applicable Windows OS Internet Explorer 6.0 SP2 on Windows XP SP1\/SP2 and Windows 2000 SP4 and Windows 2003. Support for Microsoft Internet Explorer v6.0 is deprecated in this release and due to its limited capabilities many WebSphere Portal features do not function or render correctly, including Client-Side Aggregation (CSA), Page Builder, Mashup integration, Wikis and Blogs. Some legacy pages and themes can be successfully rendered by Microsoft Internet Explorer v6.0, but use of this Web browser is not recommended.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 7.0 and future fix packs All Applicable Windows OS Internet Explorer 7.0 is supported on all versions of Windows that are supported by WebSphere Portal.\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMicrosoft Internet Explorer 8.0 and future fix packs All Applicable Windows OS See Note #1 Microsoft Internet Explorer 9.0 and future fix packs All Applicable Windows OS Refer to the IE9 Support statement for more information:\n\n http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21496054]\n\n For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n\nMozilla Firefox 3.0 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 3.5 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 3.6 and future fix packs All Applicable Windows OS See Note #1 Mozilla Firefox 4.0 and future releases, mod levels and fix packs All Applicable Windows OS See Note #1 Opera 10.0 and future fix packs All Applicable Windows OS See Note #1 WebDAV Client davfs2 1.4.6 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nJSCAPE AnyClient 2.2 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nSRT WebDrive 9.1 All Applicable Windows OS Refer to the technote for version information and limitations -\n\n Recommended WebDAV clients for accessing IBM WebShpere Portal version 7.0.0.2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27023805]\n\nWeb Servers Apache HTTP Server 2.0.59 and future fix packs All Applicable Windows OS Apache HTTP Server 2.2 and future fix packs All Applicable Windows OS IBM HTTP Server 6.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Windows OS IBM HTTP Server 7.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_HTTP_Server] All Applicable Windows OS IBM HTTP Server for i5\/OS Any and future fix packs All Applicable Windows OS IBM HTTP Server for i5\/OS versions V5R4, V6R1 and V7R1\n\nIBM HTTP Server for z\/OS Any and future fix packs All Applicable Windows OS Lotus Domino 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.0.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.0.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5.1 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Lotus Domino 8.5.2 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/lotus\/products\/domino\/] (support) [http:\/\/www.ibm.com\/software\/lotus\/support\/domino\/support.html] All Applicable Windows OS Microsoft Internet Information Services 6.0 and future fix packs All Applicable Windows OS Microsoft Internet Information Services 7.0 and future fix packs All Applicable Windows OS Microsoft Internet Information Services 7.5 and future fix packs All Applicable Windows OS Supported as Web server plugins when hosted on the Windows Server 2008 R2 edition. Sun Java System Web Server 6.1 SP10 and future fix packs All Applicable Windows OS Sun Java System Web Server 6.1 Service pack 10 or later is required.\n\nSun Java System Web Server 7.0 Update 8 and future fix packs All Applicable Windows OS Sun Java System Web Server 7.0 Update 8 or later is required.\n\n Back to top \n\n\n\n\nNOTES\n * Note #1: For more information on Web browser support with WebSphere Portal, refer to \"WebSphere Portal Support Statement Addendum - Web browsers\" at \n \n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27016293]\n \n \n * Note #2: Development Platform Only\n WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n \n \n * Note #3: Includes Support for Oracle RAC.\n \n \n * Note #4: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n \n \n * Note #5: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK\/WebSphere Application Server on 32-bit OS\n \n \n * Note #6: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n \n \n * Note #7: WebSphere Application Server requirements depending on operating system bit:\n \n * 32-bit JDK\/WebSphere Application Server on 64-bit OS\n * 64-bit JDK\/WebSphere Application Server on 64-bit OS\n \n \n * Note #8: WebSphere Application Server requirements depending on operating system bit:\n \n * 64-bit JDK\/WebSphere Application Server on 64-bit OS"}]},{"id":"TRAIN_Q430","question":"DASH 3.1.2.1 to 3.1.3.0 taking long time\n\nDASH 3.1.2.1 to 3.1.3.0 taking long time. How to fix this?","answer":"The upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process.","is_impossible":false,"contexts":[{"filename":"swg21985946.txt","text":"Title: IBM Upgrading to Jazz for Service Management Version 1.1.3.0 using Installation Manager results in a permission denied error - United States\n\nText:\njazzsm1130relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When upgrading Jazz for Service Management to Version 1.1.3.0 using Installation Manager, the installation fails with the following error:\n\nCannot run program \"\/space\/IBM\/JazzSM\/ui\/bin\/wrapper.sh\" (in directory \"\/space\/IBM\/JazzSM\/ui\/bin\"): error=13, Permission denied [\/space\/IBM\/JazzSM\/install\/tip\/tipWrapp\nerInstall.xml:215] \n\nCAUSE\nDuring the upgrade process the non-root user does not have the correct permissions to run the shell script. This is due to the following:\n1. Jazz for Service Management is installed as a non-root user\n2. Installation Manager is installed in user mode through root user\n\n\nRESOLVING THE PROBLEM\nThe upgrade must be initiated by using the attached script, which gives the non-root user (who originally installed this Jazz for Service Management instance) the correct permissions for the upgrade process. \n\n\nThe script takes two mandatory arguments and one optional argument.\n\nUsage: .\/JazzSMgrpModeUpgrade.sh \"IM_Install_Location\" \n\"JazzSM_Install_Location [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.3.0\/com.ibm.psc.doc\/ref\/psc_r_pathnames.html]\"\"[Response_file_with_absolute_Path]\"\n\nFor example (showing default installation paths): .\/JazzSMgrpModeUpgrade.sh \"\/home\/root\/IBM\/InstallManager\/\" \"\/opt\/IBM\/JazzSM\/\" \"\/opt\/Download\/dash_upgrade_rsp.xml\"\n\n\nFor IM GUI mode installation, provide the 2 mandatory arguments; IM_Install_Location and JazzSM_Install_Location. \nThis argument combination invokes Installation Manager in GUI mode and lead you through the rest of the upgrade process.\n\nFor IM Silent installation, provide all 3 arguments; IM_Install_Location , JazzSM_Install_Location, and Response_file_with_absolute_Path.\nThis argument combination invokes Installation Manager in silent mode to upgrade JazzSM.\n\nJazzSMgrpModeUpgrade.sh [\/support\/docview.wss?uid=swg21985946&aid=2]JazzSMgrpModeUpgrade.sh [\/support\/docview.wss?uid=swg21985946&aid=1]"}]},{"id":"TRAIN_Q431","question":"Install path under \"Program Files\"\n\nMy path for the OS agent is e:\\Program Files\\IBM. Is there any issues or underlying problems if I install under \"Program Files\"? Just want to make sure no issues with a \"space\" in the install path. ","answer":"Getting the below error when you try to install ITM on Window OS \n\n\"D:\\Program Files\\IBM\\ITM\" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.","is_impossible":false,"contexts":[{"filename":"swg21961222.txt","text":"Title: IBM Trouble installing ITM on Windows OS - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Getting the below error when you try to install ITM on Window OS \n\n\"D:\\Program Files\\IBM\\ITM\" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces. \n\nSYMPTOM\nWhen you try to install ITM on \" C:\\Program Files\\IBM\\ITM\" it woks fine but when we try to install it on \"D:\\Program Files\\IBM\\ITM\" we get the below error:\n\n\n\"D:\\Program Files\\IBM\\ITM\" includes blanks. Due to your system settings the installation path cannot include blanks, please specify location with no spaces.\n\nIf you take out the spaces and use D:\\ProgramFiles\\IBM\\ITM, the install will continue. \n\n\nRESOLVING THE PROBLEM\n \n\nCouple of ways to fix this... \n\n \n\n1. Remove the space in the directory path and install the ITM on a directory without spaces. \n\nExample : D:\\IBM\\ITM \n\n \n\n2. Check the NTFS 8.3 name creation and enable the 8.3 naming creation to install the ITM on a directory path with spaces.\n\ncheck the value on the below registry location \n\n\nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\FileSystem\\NtfsDisable8dot3NameCreation\n\nIn case NtfsDisable8dot3NameCreation is set to (2), this means the following: NTFS sets the 8.3 naming convention creation on a per volume basis.\n\nYou can check the 8.3 name creation using this command for the volumes that are impacted.\n\nFor example, if the %TEMP% folder is located on c:\\, but you are installing on d:\\, then you should run these commands: \n\n\nfsutil 8dot3name query c:\nfsutil 8dot3name query d:\n\nYou will get an output like this:\nThe volume state is: 0 (8dot3 name creation is enabled).\nThe registry state is: 2 (Per volume setting - the default). \n\n\nValue and Meaning\n\n0 NTFS creates short file names. This setting enables applications that cannot process long file names and computers that use different code pages to find the files.\n1 NTFS does not create short file names. Although this setting increases file performance, applications that cannot process long file names, and computers that use different code pages, might not be able to find the files.\n2 NTFS sets the 8.3 naming convention creation on a per volume basis.\n3 NTFS disables 8dot3 name creation on all volumes except the system volume. \n\n \n\nmore detail... \n\n\nhttps:\/\/technet.microsoft.com\/en-us\/library\/cc959352.aspx [https:\/\/technet.microsoft.com\/en-us\/library\/cc959352.aspx]"}]},{"id":"TRAIN_Q432","question":"Maintenance Manager login with LDAP\n\n I\"m trying to set up NENU to run on a 9.0.1 application. I've created the application and configured the ruleset but it will not connect to the application.\n\nIn the Knowledge base it says that if using LDAP to leave the UserID, Password and Station ID blank.\n\nI have tried this in multiple configuration but it simply will not connect and says the Userid and Password are invalid.\n\nAnyone have expedite on how to connect using LDAP?\n\nHere is the error message when using a userid\n\nRunning SetupOpenApplication Action...\n16:07:24.569 (47) t:1C90 p:53A7028 !!! ERROR !!!: Cannot login to application:'APPLICATIONAME', server:'tms', admin:'tmadmin', engine:'tmengine', user name:'ntprod\\svc_datacap_tst', station:'btcedcswd212v'. Error message from aTM:'Login name and\/or password invalid.\nPlease try again.'\n16:07:24.569 (0) t:1C90 p:53A7028 Running SetupDisconnectAll Action...\n\nIf I remove the username, password and station, the error message is the same except the userID has xxx.com\\svc_datacap_tst as the userid which is incorrect. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q433","question":"Optim license\n\n\n\nWe bought Optim 11.3, Test data management and data masking module....\n\nI wonder how to get a Optim license? \n","answer":"See the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.\n\nOptim license key technote.doc [\/support\/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc","is_impossible":false,"contexts":[{"filename":"swg21973794.txt","text":"Title: IBM Optim, Optim Connect, ODM, and Optim zOS licensing - United States\n\nText:\nlicense key; password; fix pack; enable; license file; Open Data Manager; ODM; entitle TECHNOTE (FAQ)\n\nQUESTION\n Are license keys still required for Optim Distributed, Optim Connect, ODM, and Optim zOS products? \n\nANSWER\nSee the attached document for a full explanation of which license keys might be required, how to request them if they are, and how to self-entitle your Optim product if they are not.\n\nOptim license key technote.doc [\/support\/docview.wss?uid=swg21973794&aid=2]Optim license key technote.doc [\/support\/docview.wss?uid=swg21973794&aid=1]"}]},{"id":"TRAIN_Q434","question":"DataPower upgrade \"extracting firmware firmware parsing error\" \"Error while processing Action ... \"\n\nI am trying to upgrade my DataPower Gateway Appliance and am receiving the message(s) similar to:\n\"extracting firmware firmware parsing error\"\nOR\n\"Error while processing Action ... Validate boot image failed \"Validation Failed\"\nHow can I resolve this? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q435","question":"Why does WebSphere Portal take over 30 minutes to start up and show hung thread message on thread server.startup?\n\nWhy does WebSphere Portal take over 30 minutes to start up and show hung thread message on thread server.startup?\nExample message from SystemOut.log:\n[3\/3\/15 5:58:47:293 EST] 00000019 ThreadMonitor W WSVR0605W: Thread \"server.startup : 1\" (00000015) has been active for 692705 milliseconds and may be hung. There is\/are 1 thread(s) in total in the server that may be hung. at java.io.UnixFileSystem.getBooleanAttributes0(Native Method) at \n....\norg.eclipse.jst.j2ee.commonarchivecore.internal.strategy.DirectoryArchiveLoadStrategyImpl.addDirectory(DirectoryArchiveLoadStrategyImpl.java:31) ..... ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q436","question":"Can you delete temporary data that is generated by IBM Business Process Manager?\n\nIn the OS temporary directories, there are many files generated for BPM. These files are created on the following operations:\ncreate TWX snapshot for export\naccess a managed asset during process execution\ncreate offline install package\nThe following temporary directories are used for storing temp files:Operating system temporary directory:\/tmp (Linux)c:\\windows\\temp (Windows)\n\nHow can these files be cleaned up?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q437","question":"Is WAS TE v7.0.0.41 available for RAD?\n\nIs WebSphere Application Server 7.0 Test Environment Extension (WTE) v 7.0.0.41 available for Rational Application Developer for WebSphere Software (RAD) ? ","answer":"This download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:\n\n\n * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41.","is_impossible":false,"contexts":[{"filename":"swg24042177.txt","text":"Title: IBM WebSphere Application Server 7.0 Test Environment Extension 7.0.0.41 - United States\n\nText:\nifix; interim fix; i-fix; fix; patch; update; fixes; upgrade DOWNLOADABLE FILES\n\nABSTRACT\n IBM WebSphere Application Server 7 Fix Pack 41 (7.0.0.41) is available as an installed test environment extension \n\nDOWNLOAD DESCRIPTION\nThis download includes the following update to the WebSphere Application Server v7.0 Test Environment extension included with Rational Software Delivery Platform products:\n\n\n * IBM WebSphere Application Server Version 7 Fix Pack 41 also known as version 7.0.0.41. For more information, see the WebSphere Application Server readme [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27004980#ver70]. \n * WebSphere Application Server Feature Pack for Web 2.0 1.0.1.1 \n * WebSphere Application Server Feature Pack for Mobile 1.1.0.1 (Note: This feature pack is available only when installing with version 8.0 or newer.) \n * WebSphere Application Server Feature Pack for Communications Enabled Applications 1.0.0.13 \n * WebSphere Application Server Feature Pack for Service Component Architecture 1.0.1.17 \n * WebSphere Application Server Feature Pack for XML 1.0.0.15 \n * WebSphere Application Server Feature Pack for OSGi Applications and Java Persistence API (JPA) 2.0 v1.0.0.9 (Note: This feature pack is available only when installing with version 8.0 or newer.) \n * WebSphere Application Server Feature Pack for Modern Batch 1.0.0.5 (Note: This feature pack is available only when installing with version 8.0 or newer.)\n\n\nFor more information on feature packs for WebSphere Application Server, see http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27008534&wv=1#was70 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27008534&wv=1#was70]. PREREQUISITES\nYou must have the WebSphere Application Server 7.0 Test Environment extension installed.\n\nYou need up to 5.18 GB of disk space to install the fix pack. To download and extract the compressed installation files, you need an additional 6 GB of disk space.\n\nINSTALLATION INSTRUCTIONS\nImportant: By default, you do not need to download the compressed files that contain the update; the update is downloaded and installed by IBM Installation Manager directly from the IBM update repository.\n\nFor instructions on installing this update using Installation Manager, see the topic Updating Installed Product Packages in the information center for your product and version: \n\n * Rational Application Developer for WebSphere Software, version 8.5.x [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSRTLW_8.5.5\/com.ibm.rad.install.doc\/topics\/t_update.html] \n * Rational Application Developer for WebSphere Software, version 9.0.x [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSRTLW_9.0.0\/com.ibm.rad.install.doc\/topics\/t_update.html] \n * Rational Application Developer for WebSphere Software, version 9.1.x [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSRTLW_9.1.0\/com.ibm.rad.install.doc\/topics\/t_update.html] \n\n\nTo download and install the update from the compressed files, complete the following steps: \n 1. Download the update files from Fix Central by following the link listed in the download table below\n 2. Extract the compressed files in an appropriate directory. For example, choose to extract to C:\\temp\\update\n 3. Add the update's repository location in IBM Installation Manager: 1. Start IBM Installation Manager.\n 2. On the Start page of Installation Manager, click File > Preferences, and then click Repositories. The Repositories page opens.\n 3. On the Repositories page, click Add Repository.\n 4. In the Add repository window, browse to or enter the file path to the diskTag.inf file, which is located in the disk1 sub-directory in the directory where you extracted the compressed files and then click OK. For example, enter C:\\temp\\updates\\disk1\\diskTag.inf.\n 5. Click OK to close the Preference page.\n \n \n 4. Install the update as described in the the topic \"Updating Installed Product Packages\" in the information center for your product and version\n\nDOWNLOAD PACKAGE\nYou can download the fix pack from Fix Central using either Download Director, HTTP or FTP. \n\n 1. Click the link in the table that follows to access Fix Central. \n 2. On the Select Fixes page, select Fix pack : 9.1.1.2-Rational-RAD-groupfixpack (IBM Rational Application Developer for WebSphere Software Version 9.5.0.2) \n 3. Expand section Show contained fixes. \n 4. From the list of contained fixed, select one of the following options:\n\n * (For 64-bit) 7.0.0.41-Rational-WAS70_64-fixzippack (WebSphere Application Server 70 64bit Extension version 7.0.0.41 update pack) \n * (For 32-bit) 7.0.0.41-Rational-WAS70-fixzippack (WebSphere Application Server 70 Extension version 7.0.0.41 update pack \n 1. Click Continue and follow the prompts to download the update.\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.0.0.41-Rational-WAS70-fixzippack 6 May 2016 English 1 FC [https:\/\/ibm.biz\/Bd48Av] [ ] \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"}]},{"id":"TRAIN_Q438","question":"During action in Rhapsody Statechart\n\n\n\nHi Folks,\n\n \n\nI am developing a statechart in Rhapsody and I have a question.\n\nI could not see in Rhapsody where I can insert an action that must occur during the whole time the state is active.\n\nI can only see : Actions on Entry and Actions on Exit.\n\nWhere is During Action?","answer":"Some of UML features such as deferred event and do-activity are not natively supported today.","is_impossible":false,"contexts":[{"filename":"swg27040251.txt","text":"Title: IBM Differences between Rational Rhapsody 8.0 Statecharts and UML 2.4.1 Behavior State Machine - United States\n\nText:\nRestriction; Restrictions; Limitation; Limitations; drawing; graphical; graph; difference; diferences; gap; deffer; feature; features; concept; concepts; error; errors WHITE PAPER\n\nABSTRACT\n This is a white paper that explains the differences between IBM Rational Rhapsody 8.0.x Statecharts and UML 2.4.1 Behavior State Machine. \n\nCONTENT\n \n\nAuthors: Shinji Kanai, Moria Abadi\n\n\nOMG UML and IBM Rational Rhapsody have been evolving in parallel, and some differences were created and expanded over time. Not all graphical notations that are defined in UML specification are supported by Rhapsody. There are certain patterns of transitions you cannot draw due to restrictions imposed deliberately, but not necessarily limited by UML specification. Some of UML features such as deferred event and do-activity are not natively supported today. This document covers such gaps that are found between UML specification and Rhapsody implementation, aiming to help you design statechart more effectively and enable easier interchange of statecharts among UML-based modeling tools.\n\n\n\n\nDisclaimer This documentation is created based on differences that are found between Rhapsody 8.0.x Statechart and OMG UML 2.4.1 Superstructure Specification (UML spec). The content is believed to be accurate at the time of publication. Use this documentation at your own risk as it might contain some incompleteness and imprecision.\n\n\n\nTable: Graphical Notations and Naming comparison \n\nUML2.4.1 Concept: Behavior state machine element or capability as it is named in OMG UML 2.4.1 Superstructure Spec. Section in spec: The section describing the element in UML spec. In Rhapsody: The corresponding name and graphical notation of UML concept that is used in Rhapsody. Note: Additional comments to help understand the specific concept better. \n[\/support\/docview.wss?uid=swg27040251&aid=1] UML2.4.1 Concept Section in spec In Rhapsody Note 1. Entry Point\n[\/support\/docview.wss?uid=swg27040251&aid=2] 15.3.1 EnterExitPoint\n[\/support\/docview.wss?uid=swg27040251&aid=3] (*) Visualization using a rectangular symbol is not supported\n(*) Not supported for composite states (See NO. 36). 2. Exit Point\n[\/support\/docview.wss?uid=swg27040251&aid=4] 15.3.1 EnterExitPoint\n[\/support\/docview.wss?uid=swg27040251&aid=5] (*) Visualization using a rectangular symbol is not supported\n(*) Not supported for composite states, only for submachine states 3. Final State\n[\/support\/docview.wss?uid=swg27040251&aid=6] 15.3.2 Termination State\n[\/support\/docview.wss?uid=swg27040251&aid=7] [\/support\/docview.wss?uid=swg27040251&aid=1] 4. Initial Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=8] 15.3.8 Default Connector\n[\/support\/docview.wss?uid=swg27040251&aid=9] [\/support\/docview.wss?uid=swg27040251&aid=1] 5. Deep History Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=10] 15.3.8 History Connector\n\n[\/support\/docview.wss?uid=swg27040251&aid=11] [\/support\/docview.wss?uid=swg27040251&aid=1] 6. Shallow History Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=12] 15.3.8 Shallow History Connector\n[\/support\/docview.wss?uid=swg27040251&aid=13] (*) Code Generation is supported in v8.0.6. See technote 1668548 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21668548] for more information. 7. Join Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=14] 15.3.8 Join Sync Bar\n[\/support\/docview.wss?uid=swg27040251&aid=15] [\/support\/docview.wss?uid=swg27040251&aid=1] 8. Fork Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=16] 15.3.8 Fork Sync Bar\n[\/support\/docview.wss?uid=swg27040251&aid=17] [\/support\/docview.wss?uid=swg27040251&aid=1] 9. Junction Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=18] 15.3.8 Junction Connector\n[\/support\/docview.wss?uid=swg27040251&aid=19] (*) Used only for merge. Only one outgoing transition is permitted 10. Static Conditional Branch\n[\/support\/docview.wss?uid=swg27040251&aid=20] 15.3.8 Condition Connector\n[\/support\/docview.wss?uid=swg27040251&aid=21] (*) Only one incoming transition is allowed.\n(*) Realized by way of the condition connector. 11. Terminate Pseudostate\n[\/support\/docview.wss?uid=swg27040251&aid=22] 15.3.8 termination Connector\n[\/support\/docview.wss?uid=swg27040251&aid=23] [\/support\/docview.wss?uid=swg27040251&aid=1] 12. State List\n[\/support\/docview.wss?uid=swg27040251&aid=24] 15.3.8 [\/support\/docview.wss?uid=swg27040251&aid=25] (*) This is an additional representation for transition from the junction having a history as target. the regular representation can be used instead. 13. Region\n[\/support\/docview.wss?uid=swg27040251&aid=26] 15.3.10 Region\n[\/support\/docview.wss?uid=swg27040251&aid=27] [\/support\/docview.wss?uid=swg27040251&aid=1] 14. Simple State\n[\/support\/docview.wss?uid=swg27040251&aid=28] 15.3.11 Simple State\n[\/support\/docview.wss?uid=swg27040251&aid=29] [\/support\/docview.wss?uid=swg27040251&aid=1] 15. Composite State\n[\/support\/docview.wss?uid=swg27040251&aid=30] 15.3.11 Composite State\n[\/support\/docview.wss?uid=swg27040251&aid=31] [\/support\/docview.wss?uid=swg27040251&aid=1] 16. Submachine State\n[\/support\/docview.wss?uid=swg27040251&aid=32] 15.3.11 Sub-statechart\n[\/support\/docview.wss?uid=swg27040251&aid=33] [\/support\/docview.wss?uid=swg27040251&aid=1] 17. Entry Behavior\n[\/support\/docview.wss?uid=swg27040251&aid=34] 15.3.11 Action on Entry\n[\/support\/docview.wss?uid=swg27040251&aid=35] [\/support\/docview.wss?uid=swg27040251&aid=1] 18. Exit behavior\n[\/support\/docview.wss?uid=swg27040251&aid=36] 15.3.11 Action on Exit\n[\/support\/docview.wss?uid=swg27040251&aid=37] [\/support\/docview.wss?uid=swg27040251&aid=1] 19. Behavior in state (do-activity)\n[\/support\/docview.wss?uid=swg27040251&aid=38] 15.3.11 [\/support\/docview.wss?uid=swg27040251&aid=39] (*) Can be implemented using entry and exit actions. See appendix (*2) for additional information. 20. Deferred events\n[\/support\/docview.wss?uid=swg27040251&aid=40] 15.3.11 [\/support\/docview.wss?uid=swg27040251&aid=41] (*) Can be modeled by customizing the framework. See appendix (*3) for additional information. 21. State Redefinition 15.3.11 State Redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its inherited states. 22. State Machine extension 15.3.12 State machine extension (*) through class inheritance 23. Time event\n[\/support\/docview.wss?uid=swg27040251&aid=42] 15.3.13 Time event\n[\/support\/docview.wss?uid=swg27040251&aid=43] (*) First option tm(<expression>), where<expression> is the number of time units. Second option Accept time event. 24. Transition 15.3.14 Transition (*) A transition cannot be associated with more than one trigger. Separate transitions for each trigger need to be used.\n(*) See appendix (*4) for the list of known transaction patterns that are forbidden by Rhapsody. 25. Internal transition\n[\/support\/docview.wss?uid=swg27040251&aid=44] 15.3.14 Reaction in state\n[\/support\/docview.wss?uid=swg27040251&aid=45] [\/support\/docview.wss?uid=swg27040251&aid=1] 26. Completion transition 15.3.14 Null transition [\/support\/docview.wss?uid=swg27040251&aid=1] 27. Completion event 15.3.14 Null event [\/support\/docview.wss?uid=swg27040251&aid=1] 28. Transition redefinition 15.3.14 Transition redefinition (*) Class inheritance causes inheritance of statecharts. the inherited statechart can redefine its transitions, except the source state and the trigger. 29. Signal receipt\n[\/support\/docview.wss?uid=swg27040251&aid=46] 15.3.14 Accept Event Action\n[\/support\/docview.wss?uid=swg27040251&aid=47] [\/support\/docview.wss?uid=swg27040251&aid=1] 30. Signal sending\n[\/support\/docview.wss?uid=swg27040251&aid=48] 15.3.14 Send Action\n[\/support\/docview.wss?uid=swg27040251&aid=49] [\/support\/docview.wss?uid=swg27040251&aid=1] 31. Action sequence notation\n[\/support\/docview.wss?uid=swg27040251&aid=50] 15.3.14 [\/support\/docview.wss?uid=swg27040251&aid=51] [\/support\/docview.wss?uid=swg27040251&aid=1] 32. Local transition\n[\/support\/docview.wss?uid=swg27040251&aid=52] 15.3.15 [\/support\/docview.wss?uid=swg27040251&aid=53] [\/support\/docview.wss?uid=swg27040251&aid=1] 33. Choice Pseudostate\/Dynamic Conditional Branch\n[\/support\/docview.wss?uid=swg27040251&aid=54] 15.3.8 [\/support\/docview.wss?uid=swg27040251&aid=55] (*) Can be simulated for example by using an additional state with guarded outgoing null transitions. See attachment (*1) in appendix. 34. Final Notation\n[\/support\/docview.wss?uid=swg27040251&aid=56] 15.3.8 [\/support\/docview.wss?uid=swg27040251&aid=57] (*) {final} means that the state cannot be redefined (such as, extended). 35. Entry\/Exit Point as part of submachine state graph\n[\/support\/docview.wss?uid=swg27040251&aid=58] 15.3.11 [\/support\/docview.wss?uid=swg27040251&aid=59] [\/support\/docview.wss?uid=swg27040251&aid=1] 36. Entry\/Exit Point on composite state\n[\/support\/docview.wss?uid=swg27040251&aid=60] 15.3.8 [\/support\/docview.wss?uid=swg27040251&aid=61] [\/support\/docview.wss?uid=swg27040251&aid=1] 37. \"Bracket\" Entry\/Exit Point notation \n[\/support\/docview.wss?uid=swg27040251&aid=62] 15.3.1 [\/support\/docview.wss?uid=swg27040251&aid=63] [\/support\/docview.wss?uid=swg27040251&aid=1] 38. Referenced\/Reused submachine state\n[\/support\/docview.wss?uid=swg27040251&aid=64] 15.3.11 [\/support\/docview.wss?uid=swg27040251&aid=65] (*) Creation of submachine is supported, but cannot be reused\/referenced elsewhere. 39. Multiple triggers for a transition\n[\/support\/docview.wss?uid=swg27040251&aid=66] 15.3.14 [\/support\/docview.wss?uid=swg27040251&aid=67] [\/support\/docview.wss?uid=swg27040251&aid=1] 40. Extended Notation\n[\/support\/docview.wss?uid=swg27040251&aid=68] 15.3.11 [\/support\/docview.wss?uid=swg27040251&aid=69] (*) Similar effect is achievable but need to extend a whole class containing a state machine using generalization. \n\nAppendix: \n\n\nDisclaimer All source code or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.\n\n\n#tbc \n\n#tbc \n(*1) Dynamic Conditional Branch \n\nDynamicBranch74orHigher.zip [\/support\/docview.wss?uid=swg27040251&aid=71]DynamicBranch74orHigher.zip [\/support\/docview.wss?uid=swg27040251&aid=70] \n\n#tbc \n(*2) \nthere is a risk that is involved to support an execution of an action that is being performed while the owning object is in a certain state. For example, there is a state \"WaitForInput\" with Do Action reading an input from the console in the background. Now an event comes to trigger a transition - a need arose to interrupt the operation of reading the input - but there is no generic way to do such things for all operations unless the action is being performed in a different thread and kill this thread. this solution seems risky for embedded systems and considered inefficient. \n\n#tbc \n(*3) \nRhapsody does not support deferred events, but there is an easy way to catch an event, which is not consumed, and process it according to your need. OMReactive class contains handleNotConsumed() virtual function, which can be overridden in your reactive class. This function is always called when event is not consumed. \n\n\n(*4)Transactional Restrictions - List of known transaction patterns that are forbidden by Rhapsody \n\n\n\nMultiple outgoing transitions from Exit Point [\/support\/docview.wss?uid=swg27040251&aid=72] Transition to Condition Connector from Entry\/Exit Point having multiple incoming transitions [\/support\/docview.wss?uid=swg27040251&aid=73] [\/support\/docview.wss?uid=swg27040251&aid=73]\n[\/support\/docview.wss?uid=swg27040251&aid=74] [\/support\/docview.wss?uid=swg27040251&aid=74] Direct transition from Junction to Condition Connector [\/support\/docview.wss?uid=swg27040251&aid=75] Indirect transition from Junction to Condition Connector by way of Entry\/Exit Point [\/support\/docview.wss?uid=swg27040251&aid=76] Direct transition from Join Bar to Junction [\/support\/docview.wss?uid=swg27040251&aid=77] Direct transition from Junction to Fork Bar [\/support\/docview.wss?uid=swg27040251&aid=78] Multiple incoming transition to Condition Connector [\/support\/docview.wss?uid=swg27040251&aid=79] Set a trigger on a transition that is originated from Exit Point [\/support\/docview.wss?uid=swg27040251&aid=80] \nRELATED INFORMATION\n UML 2.4.1 Superstructure [http:\/\/www.omg.org\/spec\/UML\/2.4.1\/Superstructure\/PDF\/]\nEnhancement for Do Activity [http:\/\/www.ibm.com\/developerworks\/rfe\/execute?use_case=viewRfe&CR_ID=8817]\nEnhancement for Dynamic Condition Connector [http:\/\/www.ibm.com\/developerworks\/rfe\/execute?use_case=viewRfe&CR_ID=7832]\nEnhancement for Shallow History Connector [http:\/\/www.ibm.com\/developerworks\/rfe\/execute?use_case=viewRfe&CR_ID=5916]\nEnhancement Deferred Event [http:\/\/www.ibm.com\/developerworks\/rfe\/execute?use_case=viewRfe&CR_ID=12691]"}]},{"id":"TRAIN_Q439","question":"Stored Procedure in WTX\n\n\n\nHi All,\n\nCan anyone please share the example\/steps\/document link on how to call Stored Procedure in Input Card of a Map? The Stored Procedure will return multiple rows and columns and we need to map those rows in Output as well. Please enlighten if someone has worked on this?","answer":"SYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX \/ ITX Oracle adapter.","is_impossible":false,"contexts":[{"filename":"swg21982008.txt","text":"Title: IBM Transformation Extender Oracle adapter does not support SYS_REFCURSOR return type in an Oracle stored procedure \/ function - United States\n\nText:\nOracle Adapter Unsupported datatype SYS_REFCURSOR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When using the IBM WebSphere Transformation Extender (WTX) \/ IBM Transformation Extender (ITX) Oracle adapter to call a stored procedure \/ function with a REF_SYSCURSOR return type, a failure of \"Unsupported datatype returned is being treated as text\" occurs. \n\nSYMPTOM\nThe Oracle database adapter log (.dbl) reports the following error:\n\nUnsupported datatype returned is being treated as text.\n\n\nCAUSE\nSYS_REFCURSOR is not a valid datatype as a return from an Oracle stored procedure call using the WTX \/ ITX Oracle adapter.\n\nENVIRONMENT\nIBM WebSphere TX \/ IBM TX Oracle adapter on any valid execution platform\n\nDIAGNOSING THE PROBLEM\nLASTERRORMSG() reports 'Failed to execute the SQL statement' and the database adapter log reports 'Unsupported datatype returned is being treated as text.'\n\nRESOLVING THE PROBLEM\nRedesign the Stored Procedure to NOT return a SYS_REFCURSOR datatype."}]},{"id":"TRAIN_Q440","question":"SCM check analyses showing as not reported in the SCA user interface\n\n\nSCM check analyses showing as <not reported> the SCA user interface.\n\nCheck analyses in the SCA interface are showing as in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.\n\nHow do I solve this issue?","answer":"To resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted.","is_impossible":false,"contexts":[{"filename":"swg21983904.txt","text":"Title: IBM SCM check analyses are showing as <not activated> the SCA user interface - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The reason why your check analyses are no longer showing activated and returning data in the SCA user interface. \n\nSYMPTOM\nCheck analyses in the SCA interface are showing as <not activated> in the SCA user interface where at one point they were activated and returning data. Now they are not activated and not returning data.\n\n\nCAUSE\nThe operator who activated the analysis has been deleted. The audit trail cleaner tool was run and it removed the operator and de-activated the analysis.\n\nRESOLVING THE PROBLEM\nTo resolve the issue, have an active operator reactivate the check analyses and then run a new import in SCA. As a best practice, it is recommended that you have an operator account dedicated to activating the SCM check analyses in your deployment. This account should never be deleted.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Security IBM BigFix Compliance"}]},{"id":"TRAIN_Q441","question":"How to serve static images from our HTTP Server instead of WebSphere 8.5 application?\n\nHow to serve static images from our HTTP Server instead of WebSphere 8.5 application?","answer":"If you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled=\"true\" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application.","is_impossible":false,"contexts":[{"filename":"swg21508890.txt","text":"Title: IBM How to serve static files from both IBM HTTP Server and an application in WebSphere Application Server - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I configure IBM HTTP Server (IHS), and the IBM web server Plug-in, and my web application running in WebSphere Application Server (WAS), to serve some of my static files (JPG, GIF, CSS, JS, etc) from the IHS web server, but serve other static files from my web app running in WAS? \n\nCAUSE\nThe \"fileServingEnabled\" property in the ibm-web-ext.xmi file in the web application, is like an ON \/ OFF switch.\nA setting of fileServingEnabled=\"true\" means that ALL static files will be served from the web application in WAS only. In this case, the plug-in config will use a wildcard with the application context-root like \"\/myapp\/*\". That way every URL starting with \/myapp\/* will be routed to the application in WAS.\n\nOn the other hand, fileServingEnabled=\"false\" means NO static files will be served from the application in WAS. In this case, a wildcard will NOT be used in the plugin-cfg.xml file. Instead, there will be several URI entries matching the URL-Patterns from <servlet-mappings> in the web.xml, like \"\/myapp\/servlet1\" and \"\/myapp\/index.jsp\". Requests for dynamic content matching the URI entries in the Plug-in config, will be routed to the application in WAS. But everything else (static content) will be handled by the IHS web server itself.\n\n\nANSWER\nIf you want to serve any static files (JPG, GIF, CSS, JS, etc) from your web application in WAS, you must use fileServingEnabled=\"true\" in the ibm-web-ext.xmi file. That will cause the plug-in to use a wildcard entry for the context-root of your web application. For example, if the context-root is \"myapp\", then there will be a URI entry for \"\/myapp\/*\" in the plug-in config, and everything starting with \"myapp\" will be routed to the application in WAS. \n\n\nNow, if you also want to be able to serve some of the static files from the IHS web server itself, you will need to do a trick using RewriteRule in the IHS config. Here is how the trick works:\n\n1) Create a subdirectory called \"static\" under the IHS DocumentRoot directory. And put the static files that you want IHS to serve into that directory. For example in the IHS document root directory (HTTPServer\/htdocs\/) create a subdirectory called \"static\". Something like this:\n\/usr\/IBM\/HTTPServer\/htdocs\/static\/\n\n2) In your web application, you will reference those files using relative references like \"static\/picture.jpg\", or \"static\/mystyles.css\".\n\nThose relative references will be interpreted as URLs like this:\n\/myapp\/static\/picture.jpg\n\/myapp\/static\/mystyles.css\n\nKeep in mind that there really is NOT any \"static\" subdirectory in the application. But that is ok.\n\n3) Now, in the IHS config, you must use RewriteCond and RewriteRule to watch for these references, and redirect to get them from IHS. For example, look at these directives...\n\n<ifModule mod_rewrite.c>\nRewriteEngine on\nRewriteRule ^\/myapp\/static\/(.*) \/static\/$1 [PT]\n<\/ifModule>\n\nIt means, if the URI begins with \/myapp\/static\/* then IHS will rewrite it to just \/static\/* and \"pass-through\". Since \/static\/* does NOT match anything in the Plug-in config, the request will be handled by IHS, and the file will be served from the static directory under IHS DocumentRoot.\n\nTo the user looking at the URL in the browser they will see this:\n\/hostname\/myapp\/static\/picture.jpg\n\nBut, the file will really be served by IHS from here:\n\/hostname\/static\/picture.jpg\n\nHere is another example:\n\nIf you just want to match and serve *.gif files from IHS, use:\n\nRewriteCond %{REQUEST_URI} \\.(gif)$ [NC]\nRewriteRule ^\/myapp\/(.*) \/static\/$1 [PT]\n\nIf you just want to match and serve *.gif, *.css and *.js files from IHS, use:\n\nRewriteCond %{REQUEST_URI} \\.(gif|css|js)$ [NC]\nRewriteRule ^\/myapp\/(.*) \/static\/$1 [PT]\n\nWhich assumes the files themselves are placed in [IHS_DOC_ROOT]\/static\/.\n\n4) For the static files in the application, you will need to put them in some other directory that is NOT called \"static\", for example \"images\/sunset.jpg\" would be a directory and file in the myapp application. This URL request, would be handled by the Plug-in and sent to the application in WAS:\nhostname\/myapp\/images\/sunset.jpg\n\n\nSo, by using the trick described above, some static files will be served from IHS, like:\n\/hostname\/myapp\/static\/picture.jpg\n\nBut other static files will be served from the web application running in WAS, like:\n\/hostname\/myapp\/images\/sunset.jpg"}]},{"id":"TRAIN_Q442","question":"Help with Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000)\n\nI need to understand details regarding Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000). This vulnerability is commonly referred to as \"Logjam\". 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)","is_impossible":false,"contexts":[{"filename":"swg21959412.txt","text":"Title: IBM Security Bulletin: Vulnerability with Diffie-Hellman ciphers may affect IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5 (CVE-2015-4000) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The LogJam Attack on Diffie-Hellman ciphers (CVE-2015-4000) may affect some configurations of IBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server 2.5. \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\nIBM SOA Policy Gateway Pattern for Red Hat Enterprise Linux Server version 2.5\n\nREMEDIATION\/FIXES\nNone\n\nWORKAROUNDS AND MITIGATIONS\nCustomers should follow the mitigation advice contained in the WebSphere Application Server security bulletin, located at http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21957980 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21957980] .\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] ACKNOWLEDGEMENT\nReported to IBM by The WeakDH team at https:\/\/weakdh.org [https:\/\/weakdh.org] \n\nCHANGE HISTORY\n 08 June 2015: 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."}]},{"id":"TRAIN_Q443","question":"How to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform?\n\nHow to get debug information when the IBM Content Navigator Installer is failing on the Unix Platform? ","answer":"To capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:\nexport LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell. \n\nThen run the installer. The output that is produced should help debug the installer. \nIf you would like to redirect output to a file:\n1. Set LAX_DEBUG=file as per the instruction above. \n2. Run your installer. \n3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install.","is_impossible":false,"contexts":[{"filename":"swg21980147.txt","text":"Title: IBM How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling? - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How to get debug information when the IBM Content Navigator Installer on the Unix Platform is failling?\n\n\nANSWER\nTo capture the debug output from the UNIX command line, enter one of the following (based on what shell you are using) at the command line prior to executing the installer:\nexport LAX_DEBUG=true or setenv LAX_DEBUG true or LAX_DEBUG=true or set LAX_DEBUG or whatever would be appropriate for the Unix shell. \n\nThen run the installer. The output that is produced should help debug the installer. \nIf you would like to redirect output to a file:\n1. Set LAX_DEBUG=file as per the instruction above. \n2. Run your installer. \n3. Once the install is complete a file labeled jx.log will be generated in the same directory as your installer. This file will contain the entire debug output generated by the install."}]},{"id":"TRAIN_Q444","question":"Licence authorised in SPSS 22, however, same error code of missing license appears\n\nI had SPSS 22 that worked fine until the license ended. It was renewed and when I tried to re-enter the license number it was authorised, however, there was still an error code of missing license and so I can work with my SPSS.\n\nThis is the error code:\n\n Error # 7001 There is no license for IBM SPSS Statistics. This could be due to a missing license file or no more network licenses available. For detailed information about this problem, run the 'showlic' utility found in the product installation directory. Execution of this command stops. Specific symptom number: 18\n\nI would appreciate your help! ","answer":"No, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly.","is_impossible":false,"contexts":[{"filename":"swg21477587.txt","text":"Title: IBM Will current versions of IBM SPSS Statistics or AMOS for Windows run on a Macintosh operating system? - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n I have a Macintosh computer with Intel processor. I am wondering if I can install an IBM SPSS Statistics for Windows or IBM SPSS AMOS for Windows releases on this Mac with emulation or dual-booting software such as Boot Camp, Parallels, Virtual PC, Rosetta? \n\nANSWER\nNo, installing IBM SPSS Statistics and AMOS for Windows releases on a Macintosh operating system or hardware using any dual booting or emulation software is not supported and cannot run properly. \n\nIBM SPSS Statistics is available for Macintosh operating system as a single release. IBM SPSS AMOS is available only for Microsoft Windows operating system.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]"}]},{"id":"TRAIN_Q445","question":"Why does IBM Datacap 8.1 appear to hang\n\nWhy does IBM Datacap 8.1 appear to hang, requiring a restart of all components http:\/\/ow.ly\/yhjCg #ibmecm","answer":"The cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query. \n\nTMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.","is_impossible":false,"contexts":[{"filename":"swg21666402.txt","text":"Title: IBM Why does IBM Datacap 8.1 appear to hang, requiring a restart of all components? - United States\n\nText:\nhang; non responsive; timeout; Admin retry; Engine retry TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Why does IBM Datacap appear to hang, requiring a restart of all components? \n\nSYMPTOM\nThe Datacap system appears to become non-responsive, requiring a restart of all components to get it working again.\n\n\nCAUSE\nThe cause is due to a malformed SQL query string. From the client perspective, it was reported to occur during logon via TMWeb, and Thick Client. Another case was from a user that was doing a Thick Client query. \n\nTMServer has an feature where it will retry any command that results in error, based on the settings in the registry. The settings reflect the number of retries to do and the time interval to wait. The default settings have a duration of 16 minutes, which gives the appearance that the TMServer has hung.\n\n\nDIAGNOSING THE PROBLEM\nCollect and examine the TMServer log. Look for multiple instances (6-12) of an ADO error, indicating a bad query was executed. This information can be used to identify the user that is causing the problem\n\n\n\nRESOLVING THE PROBLEM\nWhile bad queries should be avoided, the following will allow TMServer to respond faster, should a bad query happen: \n\n1. Stop all Datacap applications, then stop the TMServer. \n\n2. Change the following registry entries on the TMServer box:\n\n\n * \n * \n * HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Datacap\\TMS\\InterThread (REG_SZ) Engine retries \n * \n * \n * \n * HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) Admin retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) ADO retries HKEY_LOCAL_MACHINE\\SOFTWARE\\Datacap\\TMS\\InterThread (REG_SZ) Engine retries \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\n3. Restart the TMServer, then start the Datacap applications in reverse order. \n\nPlease Note: Since these are considered tuning parameters, you will need to test to see what settings work best for your system. \n\nNote: for Datacap 9.x, the registry entry name is singular, as in 'Admin retry' or 'Engine retry'."}]},{"id":"TRAIN_Q446","question":"Is DataPower affected by the bash environment variable vulnerability CVE-2014-6271 or CVE-2014-7169\n\nIs DataPower affected by the recent vulnerability reported through CVE-2014-6271 or 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.","is_impossible":false,"contexts":[{"filename":"swg21685435.txt","text":"Title: 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\n\nText:\nCVE-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 \u201cBash Bug\u201d or \u201cShellshock\u201d 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."}]},{"id":"TRAIN_Q447","question":"ITCAM Agent for DataPower in TEP view, no data in the \"HTTP Mean Transaction Times - Top 10\" workspace.\n\nWIth ITCAM Agent for DataPower in TEP view, there is no data in the \"HTTP Mean Transaction Times - Top 10\" workspace. The problem is that while the KBN agent is displaying some data in the TEP, in the \"DataPower Appliances\" view, there is no data in the \"HTTP Mean Transaction Times - Top 10\" workspace. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q448","question":"export XML results in ASE\n\n\n\nHello everyone, you all know that ASD gives the possibility to export results in XML with File --> Export --> Scan Results as XML (Legacy...) Is there any chance to have the same XML using ASE 9035 ???","answer":"The answer to the question is 'no'. \nIn AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML.","is_impossible":false,"contexts":[{"filename":"swg21649798.txt","text":"Title: IBM How to Export the Scan Results (Detailed Security Issues) into XML format in AppScan Enterprise - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Is there a way to Export the Scan Results (Detailed Security Issues) into XML format in IBM Security AppScan Enterprise? \n\nANSWER\nThe answer to the question is 'no'. \nIn AppScan Enterprise Console, there are functions, Export to XML and Export detailed Security issues to PDF, but there is no function Export detailed Security issues to XML. \n\nWe strongly suggest to submit an enhancement request (RFE) for the AppScan Enterprise products as described in How to submit enhancement requests for IBM Security products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21682719]. The requests there are submitted directly to the AppScan management team."}]},{"id":"TRAIN_Q449","question":"How do I identify people in scope across Matters in Atlas?\n\nHow do I identify people in scope across Matters in Atlas? ","answer":"REP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views.","is_impossible":false,"contexts":[{"filename":"swg21983912.txt","text":"Title: IBM Identifying people in scope across Matters in Atlas - United States\n\nText:\nAtlas People in Scope Views TECHNOTE (FAQ)\n\nQUESTION\n How do I identify people in scope across Matters in Atlas? \n\nCAUSE\nQuery to identify people in scope across matters in Atlas\n\nANSWER\nREP_PEOPLE_INSCOPE_VW view has information about people in scope. You can create a query by joining the view with REP_MATTER_VW, REP_REQUEST_VW, REP_NOTICES_VW and REP_PERSON_VW views. \n\nPlease refer to reporting views documentation at the following link for more details about Matter related views\n\nhttps:\/\/www.ibm.com\/support\/knowledgecenter\/SS5JP8_6.0.3\/com.ibm.aps.use.doc\/apsrv0044.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SS5JP8_6.0.3\/com.ibm.aps.use.doc\/apsrv0044.html]l"}]},{"id":"TRAIN_Q450","question":"MQRC_NOT_AUTHORIZED after migrating from Websphere V7.0 to V8.5.5\n\nAfter migration from WAS 7 TO WAS 8.5.5.3 ,WAS is unable to communicate with MQ and we see the following errors in the SystemOut.log: \n \ncom.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'XXXQM' with connection mode 'Client' and host name 'ipaddress(port)'. \nPlease check if the supplied username and password are correct on the QueueManager to which you are connecting. at com.ibm.msg.client.wmq.common.internal.Reason .reasonToException(Reason.j ava:516) \n..... \nCaused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED'). at com.ibm.msg.client.wmq.common.internal.Reason.createException (Reason.java:204)\n \n What is causing this?","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.","is_impossible":false,"contexts":[{"filename":"swg21662193.txt","text":"Title: 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\n\nText:\n 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(\u201c\u201d, \u201c\u201d);\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 \u201ccom.ibm.mq.jms.ForceUserID\u201d 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"}]},{"id":"TRAIN_Q451","question":"How to connect ICC to P8 using SSL?\n\nIn the ICC Configuration Manager, http has been changed to https in the P8 URL. But validating the connection to P8 fails. ","answer":"ICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.","is_impossible":false,"contexts":[{"filename":"swg21979016.txt","text":"Title: IBM Configure IBM Content Collector to use SSL to communicate with IBM FileNet P8. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I configure IBM Content Collector (ICC) to use SSL to communicate with IBM FileNet P8 for all components? \n\nCAUSE\nICC communicates with P8 in several different components. Depending on the API used for the various components, P8 certificates need to be installed in multiple places.\n\nANSWER\nDo the following steps to install P8 certificates. Depending on your business requirements, you may not use all of the components so some steps may not be necessary. \n\n * First obtain a P8 server certificate by accessing the P8 Content Engine ping page using this URL: https:\/\/<ce_server>:<ssl_port>\/FileNet\/Engine \n \n From the browser, view the certificate and copy it to a file. Use it for later steps. \n Do not use the MTOM page as it may not produce the same certificate that ICC requires. \n \n \n \n \n * Perform this step if you are going to run ICC Initial Configuration to create new document classes in P8 object store. * To import the certificate, issue the following command, whereICCInstallDiris the directory of your Content Collector installation andP8CertificatFileis the certificate for the FileNet P8 server: \"ICCInstallDir\\java\\jre\\bin\\keytool.exe\" -import -file P8CertificateFile\n -keystore \"ICCInstallDir\\java\\jre\\lib\\security\\cacerts\" -alias afup8 \n \n \n * At the password prompt, enter the password for the JRE keystore. (The default password is changeit.) \n * Enterywhen asked whether to trust the certificate. \n * Run ICC Initial Configuration and you should then be able to validate the connection with P8 using SSL.\n \n \n\n * Perform this step if you are going to run task route archiving to P8: * Add the P8 certificate into the Windows Trusted Root Certificate Authorities via the Microsoft Management Console. \n * For more details instructions, refer to this document:\n http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21610358 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21610358]\n \n \n\n * Perform this step if you are going to retrieve, restore, or search for documents from P8: * Start ikeyman from ICC-install-directory\\AFUWeb\\ewasfor the ICC embedded web application server. \n * In the ikeyman utility, select Key Database File>Open, and select PKCS12as key database type. \n * In theLocationfield, specify theWAShome\\profiles\\profile name\\config\\cells\\cell name\\nodes\\node name\\trust.p12file.\n ReplaceWAShome,profile name,cell name, andnode namewith the proper values of your web application server installation. \n * Click OK. \n * When prompted for a password, enter the password. ClickOK. The default password is WebAS. \n * Under theSigner certificateslist, clickAddto add the P8 certificate. \n * Exit ikeyman utility and restart IBM Content Collector Web Application service. \n * For more details instructions, refer to this document: http:\/\/www.ibm.com\/support\/knowledgecenter\/SSAE9L_4.0.1\/com.ibm.content.collector.doc_kc\/installing\/t_afu_establish_trust_relationship.dita?lang=en [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSAE9L_4.0.1\/com.ibm.content.collector.doc_kc\/installing\/t_afu_establish_trust_relationship.dita?lang=en]"}]},{"id":"TRAIN_Q452","question":"Cannot start the IBM Content Collector Configuration Store Service\n\nHow to resolve when the IBM Content Collector Configuration Store Service cannot be started? ","answer":"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.","is_impossible":false,"contexts":[{"filename":"swg21680391.txt","text":"Title: IBM Content Collector Configuration Store is corrupted - United States\n\nText:\n 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]"}]},{"id":"TRAIN_Q453","question":"ICO's Roadmap of supporting next OpenStack versions\n\n\n\nHello,\n\nICO 2.5.0.2 is compatible with OpenStack kilo, is there a plan making it work with OpenStack Liberty\/Mitika ?\n\nWould you share any information or link about the roadmap, please?\n\nThanks in advance.","answer":"The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).","is_impossible":false,"contexts":[{"filename":"swg2C1000132.txt","text":"Title: IBM Cloud Orchestrator (ICO) continues to be a strategic solution for IBM - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n Cloud Orchestrator (ICO) continues to be a strategic solution for IBM \n\nCONTENT\nIBM Cloud Orchestrator continues to be a strategic solution for IBM in Hybrid Cloud management and will continue to be actively developed. Future IBM Cloud Orchestrator releases will enable management of external OpenStack environments which are compliant with the RefStack certification, providing more choices and flexibility to clients to select their preferred OpenStack vendor. The current release of IBM Cloud Orchestrator will continue to bundle IBM Cloud Manager with OpenStack (ICMO), while future IBM Cloud Orchestrator releases will no longer bundle ICMO, as it has been announced that ICMO is at the end of market (see reference document below).\nIBM Cloud Orchestrator (ICO) and IBM Cloud Manager with OpenStack (ICMO) will continue to be supported until Sept 2020.\n\nReference: ICMO End of Market announcement:\nhttp:\/\/www-01.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/2\/897\/ENUS916-062\/index.html&lang=en&request_locale=en [http:\/\/www-01.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/2\/897\/ENUS916-062\/index.html&lang=en&request_locale=en]"}]},{"id":"TRAIN_Q454","question":"Column Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256\n\nColumn Analysis on Informix database using odbc connector fails with error SQLSTATE = HY000: Native Error Code = -256","answer":"To resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit.","is_impossible":false,"contexts":[{"filename":"swg21591143.txt","text":"Title: IBM Information Server Informix Wire Protocol driver error \"Transaction not available\" from ODBC Connector Stage - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When using the ODBC Connector Stage to access data in an Informix database, receive the following error:\n\nMessage: ODBC_Connector_0: ODBC function \"SQLPrepare\" reported: SQLSTATE = HY000: Native Error Code = -95: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Unexpected Network Error.\nODBC function \"SQLPrepare\" reported: SQLSTATE = HY000: Native Error Code = -256: Msg = [IBM(DataDirect OEM)][ODBC Informix Wire Protocol driver][Informix]Transaction not available. (CC_OdbcDBStatement::dbsPrepare, file CC_OdbcDBStatement.cpp, line 347)\n\n\nRESOLVING THE PROBLEM\nTo resolve the above error, set the Transaction handling>Isolation Level from none to Auto-Commit."}]},{"id":"TRAIN_Q455","question":"How can I query the Derby database in Portal via SQL statements?\n\nI have a Portal system I just installed. I have not yet run database-transfer to copy the data from the Derby database to a DB2, Oracle, or SQL Server database. I don't wish to transfer to an external database and I have a need to run a SQL query against a table or two in the Derby database to troubleshoot an issue. \r\nHow can I perform this action? ","answer":"In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals.","is_impossible":false,"contexts":[{"filename":"swg21381009.txt","text":"Title: IBM Using dblook and ij to work with the embedded Apache Derby in WebSphere Portal - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM WebSphere Portal 6.1 uses an embedded version of Apache Derby out of the box. However, there is no longer a graphical tool such as CloudView (as with Cloudscape 5.x). In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals. \n\nRESOLVING THE PROBLEM\n\nBefore proceeding with the following, it is strongly recommended that you back up your Derby database. Make a copy of <wp_profile>\/PortalServer\/derby\/wpsdb to a backup directory. Since the version of Derby used in WebSphere Portal is embedded, you must stop the Portal server before you can access the database although you can always work on the backup copy.\n\nNOTE: For simplicity, we will omit the extension of the utilities. You should add \".sh\" or \".bat' depending on the platform.\n\nThere are three primary utility tools that are installed with WebSphere 6.1, \"dblook\", \"ij\", and \"sysinfo\", under the <was_root>\/AppServer\/derby\/bin\/embedded directory. The sysinfo utility generates information about the operating system, the Java version and classpath, and the Derby driver files and version information.\n\ndblook utility\nThe dblook utility is used to view the database structure (in DDL - Data Definition Language) for a specific database. \n\nThe usage is dblook -d <databaseURL> [options], where databaseURL is in the \"jdbc:derby:<database>\" format. The <database> should be given as a full path, such as C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb. \n\nCommonly used options include: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Examples:\n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -t user_desc -verbose -o C:\\temp\\user_desc.sql\n * \n * \n\n\nij utility \nThe ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes (when advised by IBM Support). \n\nTo start ij, simply open a command prompt or terminal window, change the directory and enter the command. You should then see the ij shell with prompt \"ij>\". \n\nThe following are some common commands that you may use when reviewing data in the Portal database. * \n * ij> connect 'jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb';\n * \n * \n * \n * \n * ij> show connections;\n * \n * \n * CONNECTION0* - jdbc:derby:C:\\ibm\\websphere\\wp_profile\\portalserver\\derby\\wpsdb \n * = current connection \n ij> driver \"org.apache.derby.jdbc.EmbeddedDriver'; \n * \n * \n * \n * ij> set schema=release;\n * \n * \n * \n * \n * ij> select * from user_desc where oid=1000;\n * \n * \n * \n * \n * ij> run 'myquery.sql';\n * \n * \n * \n * \n * \n * \n * ij> CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE('RELEASE','USER_DESC','USER_DESC.SQL',';','|',NULL);\n * \n * \n * \n * \n * ij> \n * CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY('SELECT * FROM RELEASE.USER_DESC','user_desc_query.sqlL',null,'|',NULL);\n * \n * \n\nRELATED INFORMATION\n Derby utility from Apache [http:\/\/docs.oracle.com\/javadb\/10.3.3.0\/getstart\/cgsusingtoolsutils.html]\nDerby SQL references from Apache [http:\/\/db.apache.org\/derby\/docs\/10.1\/ref\/crefsqlj23296.html]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z\/OS 7.0, 6.1"}]},{"id":"TRAIN_Q456","question":"zonecfg error while starting nodeagent and dmgr\n\n\n\nI saw zonecfg error while starting nodeagent and dmgr in solaris server\n\nMy env is Oracle Solaris 11.2 SPARC, and WAS is 8558, jave 1.7. [1\/22\/16 21:31:18:379 AEDT] 00000001 SystemOut O java.lang.Exception: command \/usr\/sbin\/zonecfg failed with 1 at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.executeCommand(SolarisHypervisor.java:357) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor.access$100 (SolarisHypervisor.java:30) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.processZoneCfg(SolarisHypervisor.java:570) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor$Zone.(SolarisHypervisor.java:461) at com.ibm.ws.xd.agent.hypervisor.SolarisHypervisor ..... Is that normal behavior and what's the exactly meaning of the error?","answer":"When WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions.","is_impossible":false,"contexts":[{"filename":"swg21626683.txt","text":"Title: IBM Exceptions starting WAS 8.5 as non root user on Solaris - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You notice the exceptions below at start up. \n\nSYMPTOM\nException: command \/usr\/sbin\/zonecfg failed with 1\nand \nFFDC Exception:java.lang.Exception SourceId:com.ibm.ws.xd.vv.nodedetect.NetworkInterfaceUtil.getMacAddresses ProbeId:2\njava.lang.Exception: dlopen() returned error; rc=128\n\n\nCAUSE\nWhen WebSphere Application Server is run as a non-root user it will not be able to run native commands. This limited access causes the exceptions.\n\nRESOLVING THE PROBLEM\nTo resolve the problem, run WebSphere Application Server under a root user. If the environment is not virtualized, that is if Solaris zones are not being used then the errors can be ignored as these will only occur at start up and will not affect a non-virtualized environment"}]},{"id":"TRAIN_Q457","question":"What is the correct number of datasource connections for Portal?\n\nWhat is the best way to figure out how to configure the maximum number of datasource connections for my Portal server? What factors are involved that I need watch out for? ","answer":"When tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system. \n\nEach Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1. \n\nHowever, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1","is_impossible":false,"contexts":[{"filename":"swg21509634.txt","text":"Title: IBM How to set an appropriate number of Portal Datasource connections in WebSphere Portal - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\nFor a given maximum number of Portal WebContainer threads set, what should I set my maximum Portal datasource connections to? \n\nANSWER\nWhen tuning WebSphere Portal at version 6.0 and beyond, one of the concerns that arises is how should one tune the maximum number of Portal datasources. Portal can and does make heavy internal use of datasources, so miscalculating this (maximum) value can have a significant impact on system behavior. Out of the box, the default maximum setting is 50. This may or may not be sufficient for any given system. \n\nEach Portal request may make any number of database (DB) requests ranging for none to several.. Further, customized portlets and PPR (Parallel Portlet Rendering) may cause several concurrent DB requests. By default, the maximum number of WebContainer threads is also set to 50. Therefore the ratio between the maximum number of Portal datasource connections to the maximum number of Portal WebContainer threads is 1:1. Support has found that this ratio is often too low for the best performance. In the past, there have been recommendations of this ratio as high as of 2:1 or even 2.5:1. \n\nHowever, these values caused concern in large deployments where the TOTAL number of maximum datasource connections might start to place a strain on backend resources. Recent analysis suggests that these ratio values may be safely reduced to 1.25: 1 for all Portal datasource, with the exception of the jcrDB when WCM is used extensively. In this case, we recommend a ratio of 1.5:1 \n\n----------------------------------------------------------------------------------------------------------------- \n\nFor example, if your system's \n\nMaximum number of WebContainer threads is 100 \n\nthen you should set your \n\nMaximum number of Portal datasource connections to 125 \n\nfor each Portal datasource. \n\n----------------------------------------------------------------------------------------------------------------- \n\nIf during Runtime, you should find that your running out of Portal Datasource connections, you may go ahead and increase the ratio up to 2:1. Please be aware of how this might impact your backend resources and be sure to scale your database accordingly. \n\n------------------------------------------------------------------------------------------------------------------ \n\nTo find the number of WebContainer threads that are running in any particular Portal server, use the WebSphere Application Server Admin Console and go to the following location: \n\nServers ---> Application Servers --> WebSphere_Portal (your server) --> Thread Pools --> WebContainer \n\n \n\nTo find the Data Source setting for your Portal datasources, use the WebSphere Application Server Admin Console to go to the following location: \n\nResources ---> Data Sources ---> wpdbDB (for example) --> Connection pools \n\n--------------------------------------------------------------------------------------------------------------------"}]},{"id":"TRAIN_Q458","question":"Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task\n\n Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task","answer":"Please make the following change in the WAS Admin Console...\nApplications > WebSphere enterprise applications >\nJavaContentRepository > Target specific application status > Check the\nbox for the WebSphere_Portal server > Click Enable Auto Start > Save\nchanges > restart Portal\n\nAfter making this change please attempt the CF upgrade again.","is_impossible":false,"contexts":[{"filename":"swg21691034.txt","text":"Title: IBM Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task - United States\n\nText:\nupgrade; TASK001X; import-nodes; 404 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhile attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task.\n\nSYMPTOM\nThe ConfigTrace.log shows the following...\n\nimport-nodes:\n\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\n\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\nat org.apache.tools.ant.Task.perform(Task.java:364)\n\nat org.apache.tools.ant.Target.execute(Target.java:341)\n\nat org.apache.tools.ant.Target.performTasks(Target.java:369)\n\nat\norg.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)\n\nat\norg.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe\nckExecutor.java:37)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n\n... 75 more\n\n\nCAUSE\nThe customer had previously disabled the autostart on several applications to improve the Portal startup time\n\nENVIRONMENT\nPortal 8.0.0.1\nWindows\n\nDIAGNOSING THE PROBLEM\nfrom ConfigTrace.log...\n\nWed Nov 19 16:49:42 CST 2014\nTarget started: import-nodes\n\nimport-nodes:\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n... 75 more\n\nFrom here I reviewed the SystemOut.log at the same timestamp and see\nthe following...\n\n[11\/19\/14 16:49:43:804 CST] 00000042 filter E\ncom.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter\nSRVE8109W: Uncaught exception thrown by filter Extensible Filter:\njava.io.FileNotFoundException: SRVE0190E: File not found:\n\/jcr\/remotetask\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(\nDefaultExtensionProcessor.java:893)\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(D\nefaultExtensionProcessor.java:874)\n\nBoth of these messages seems to indicate a problem with the WCM\nstartup. This code is contained in the following\napplication....JavaContentRepository.ear.\n\nLooking at your last Portal startup I saw this below which occurs\nduring the wcm application startup....\n\n[11\/19\/14 15:57:54:566 CST] 00000009 ApplicationMg A WSVR0200I:\nStarting application: wcm\n\n....\n\n[11\/19\/14 16:00:36:812 CST] 00000005 TimeoutManage I WTRN0006W:\nTransaction\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000001 has timed out after 120 seconds.\n[11\/19\/14 16:00:36:831 CST] 00000005 TimeoutManage I WTRN0124I: When\nthe timeout occurred the thread with which the transaction is, or was\nmost recently, associated was Thread[server.startup : 0,5,main]. The\nstack trace of this thread when the timeout occurred was:\njava.lang.Thread.blockedOn(Thread.java:1076)\nsun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)\nsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce\nssorImpl.java:37)\njava.lang.reflect.Method.invoke(Method.java:611)\n\nKnowing this I further reviewed the SystemOut.log to see where the JCR\nweb module gets loaded during startup....it should begin like this...\n\nSRVE0169I: Loading Web Module: JCRContentRepository.\n\nYour startup does not have this. This prompted me to review the\ndeployment.xml from the JavaContentRepository application directory at\nthis location...\n\nPortal8\/wp_profile\/config\/cells\/C001389391Cell\/applications\/JavaContentR\nepository.ear\/deployments\/JavaContentRepository\/deployment.xml\n\nThe contents show the following...\n\n<targetMappings xmi:id=\"DeploymentTargetMapping_1335003370698\"\nenable=\"false\" target=\"ServerTarget_1335003370698\"\/>\n\nThe enable=false means that you have this application set to not\nautostart. Because of this it is not starting during Portal startup\nand therefore is not available when the config task attempts to\ncommunicate with it during the upgrade...and therefore causes the\nproblem.\n\nRESOLVING THE PROBLEM\nPlease make the following change in the WAS Admin Console...\nApplications > WebSphere enterprise applications >\nJavaContentRepository > Target specific application status > Check the\nbox for the WebSphere_Portal server > Click Enable Auto Start > Save\nchanges > restart Portal\n\nAfter making this change please attempt the CF upgrade again."}]},{"id":"TRAIN_Q459","question":"Help with Security Bulletin: IIB is affected by Open Source Apache Tomcat Vulnerabilities (CVE-2017-12617,CVE-2017-12615)\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by Open Source Apache Tomcat Vulnerabilities (CVE-2017-12617,CVE-2017-12615). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q460","question":"How do I transfer my SPSS 24 license key to a new computer?\n\nI need to transfer my SPSS 24 license key to a new computer. I was able to download IBM\u00ae SPSS\u00ae 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?\n\n\n\nThis dW Answers question is about an IBM document with the Title: \nSPSS Student Version and Graduate Pack Resources","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q461","question":"How can I configure TIP to clear the ARGUS cache without having to do a system restart?\n\nArgus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The \"cacheTime\" variable in the configFile.xml configuration file controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors. ","answer":"To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1.","is_impossible":false,"contexts":[{"filename":"swg21657452.txt","text":"Title: IBM Tivoli Integrated Portal hangs because of Argus java.lang.OutOfMemory. - United States\n\nText:\ncacheTime; config.xml; Argus; TIP cache; TIPL2CONF; TIPL2PERF TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Argus stores it's role authorizations in memory cache, and is not cleaned out unless the TIP is restarted. The \"cacheTime\" variable controls this, which is set to -1 by default. If the number of TIP roles is high, it can cause Java OOM errors. \n\nSYMPTOM\nTIP hangs. SystemOut.log file shows Java.lang.OutOfMemoryError: \n\n[10\/2\/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[\/secure\/isclite\/tiles\/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)\n\n\nCAUSE\nBy default, the ARGUS cache will not get cleaned up unless the TIP server is restarted. This normally will give the system good runtime performance. However, in cases where a large number of user\/role mappings are defined, the system may run into Java memory issues causing Java OutOfMemory outages.\n\nThe cacheTime we are talking about here is Argus cache. The is used for the way the role authorizations are stored in memory by Argus and nothing related to LDAP or SSO. The Argus cache time by default we ship with in TIP is -1 which means the cache will not get cleaned up till we re-start the server. \n\nError from the <TIP_HOME>\/profiles\/TIPProfile\/logs\/server1\/SystemOut.log\n\n[10\/2\/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[\/secure\/isclite\/tiles\/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method)\n\n\nENVIRONMENT\nall environments\n\n\n\nDIAGNOSING THE PROBLEM\nJava heapdump files will be created in the <TIP_HOME>\/profiles\/TIPProfile directory. \n\nheapdump.20131022.144244.20034001.phd \n\nThe Systemout.log will have have errors similar to this: \n\n\n[10\/2\/13 9:27:54:838 CDT] 0000002a webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: \n[Servlet Error]-[\/secure\/isclite\/tiles\/nop.jsp]: java.lang.OutOfMemoryError: Java heap space at java.lang.Object.clone(Native Method) \n\n\nUsing the memory heap dump analysis shows that Argus is the problem, specifically the instance shown inside the red line in the output of the Java memory analyzer below: \n\n \n\n[\/support\/docview.wss?uid=swg21657452&aid=1] [\/support\/docview.wss?uid=swg21657452&aid=1]\n\nYou can also check the cacheTime variable in the <TIP_HOME>\/profiles\/TIPProfile\/config\/cells\/TIPCell\/commonauthz\/config.xml file to confirm if it's set to \"-1\", which means the Argus cache will not get cleaned up unless the TIP server is restarted.\n\n\nRESOLVING THE PROBLEM\nThe cacheTime value in config.xml is in milliseconds. TIP is shipped with the initial value of -1, which means the Argus cache will not be cleared out unless TIP restart. To resolve this issue you need to configure 'cacheTime' to non -1 value. Initially we suggest setting the value to 1200000, which is 20 minutes. After the change you will have to restart the TIP server, normally server1. \n\nNOTE: The cacheTime variable was added in TIP version 2.2.0.0."}]},{"id":"TRAIN_Q462","question":"Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283)\n\nI need to understand details regarding Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues (CVE-2017-1283). Where can I find this information?","answer":"CVEID: CVE-2017-1283 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1283]\nDESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125144 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125144] 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)","is_impossible":false,"contexts":[{"filename":"swg22003852.txt","text":"Title: IBM Security Bulletin: IBM MQ and IBM MQ Appliance Shared memory leak caused by MQ applications using dynamic queues. (CVE-2017-1283) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Shared memory leak caused by MQ applications using dynamic queues. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1283 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1283]\nDESCRIPTION: IBM WebSphere MQ could allow an authenticated user to cause a shared memory leak by MQ applications using dynamic queues, which can lead to lack of resources for other MQ applications.\nCVSS Base Score: 3.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125144 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125144] 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 V8\nIBM MQ 8.0.0.0 - 8.0.0.6 maintenance levels\nIBM MQ Appliance V8\nIBM MQ Appliance 8.0.0.0 - 8.0.0.6 maintenance levels\nIBM MQ V9\nIBM MQ 9.0.0.0 - 9.0.0.1 maintenance levels\nIBM MQ V9 CD\nIBM MQ 9.0.1 - 9.0.3 releases\nIBM MQ Appliance V9 CD\nIBM MQ Appliance 9.0.1 - 9.0.3\n\nREMEDIATION\/FIXES\nIBM MQ V8 \n\nApply Fix Pack 8.0.0.7 [https:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22005832]\nIBM MQ Appliance V8\nApply Fix Pack 8.0.0.7 for MQ Appliance [https:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22005832]\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 IBM MQ 9.0.4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043348]\nIBM MQ Appliance V9 CD\nUpgrade to IBM MQ Appliance 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 14 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."}]},{"id":"TRAIN_Q463","question":"Can Portal prevent the usage of simultaneous logins with the same userID?\n\nIs it possible for WebSphere Portal to limit the usage of a userID to one authenticated session as a time? In other words, prevent authenticating to Portal as \"user1\" from one browser and then simultaneously authenticating to Portal again as \"user1\" from another browser? ","answer":"WebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported. \n\n\"ConcurrentModificationException\" and other errors may be logged.\n\nMost of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.\n\nIt may be possible to prevent multiple logins by writing custom \"tracking code.\" Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.\n\nIf you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):\n\n-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.\n\n-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility. \n\n-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a \"force simultaneous login\" option in the login user interface.\n\nFor load testing, use unique user ids or virtual users.","is_impossible":false,"contexts":[{"filename":"swg21227799.txt","text":"Title: IBM Multiple logins using the same user ID - United States\n\nText:\nConcurrentModificationException; log in; login; multiple; userid; multiple login TECHNOTE (FAQ)\n\nQUESTION\n \"ConcurrentModificationException\" and other errors may occur if the same user id is logged in to IBM WebSphere Portal multiple times.\n\n\nANSWER\nWebSphere Portal has no built-in mechanism or configuration setting to limit the number of times a user id may log in. Unexpected behavior may occur if the same id is logged in more than once and this is not supported. \n\n\"ConcurrentModificationException\" and other errors may be logged.\n\nMost of the related issues were resolved in WebSphere Portal 5.1. However, you may still encounter exceptions or side-effects if you access the Portal in multiple browser windows using the same user id, whether or not the authentication requests take place on separate physical hosts.\n\nIt may be possible to prevent multiple logins by writing custom \"tracking code.\" Contact IBM Services for assistance to undertake such a project. WebSphere Portal Development does not have any sample code.\n\nIf you wish to write your own code, some of the issues to be aware of are (this is not an inclusive list):\n\n-- Multiple logins may take place on different nodes in a cluster. This means some cluster-wide mechanism would have to be in place to keep track of the logged-in users. Look at the WebSphere Application Server DistributedMap interface.\n\n-- There should be a fail-safe way to track user logout (explicit logout and session timeout). Using a session listener might be a possibility. \n\n-- If a user closes the browser without logging out, that user must wait for a session timeout before logging in again. Otherwise, there should be a \"force simultaneous login\" option in the login user interface.\n\nFor load testing, use unique user ids or virtual users.\n\nRELATED INFORMATION\n Portal 6.1\/7.0: Authentication Filters [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1\/index.jsp?topic=\/com.ibm.wp.ent.doc_v615\/admin\/adauthflt.html]\nPortal 6.1: Custom Login Portlet [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg21358508]\nRestricting Multiple Sessions [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Restricting_Multiple_Sessions_in_WebSphere_Portal]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products General AIX, HP-UX, Linux, Solaris, Windows 7.0, 6.1.5, 6.1, 6.0, 5.1"}]},{"id":"TRAIN_Q464","question":"Why is SAP agent user getting locked for V7.1.1 FP1?\n\nWe have ITCAM agent for SAP, V 7.1.1 FP1 IF1. Every few weeks, the agent user appears to be getting locked because it starts using wrong password, and SAP basis team has to unlock it, and then it starts to work again. Is there a solution for this problem?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q465","question":"Why do I get a nullPointerException from the default portal theme? EJCBD0021E\n\n\n\nI can see the following nullPointerException in the logs:\n\nEJCBD0021E: The URI [dav:fs-type1\/themes\/Portal8.0\/theme.html] and parameters [['themeURI'=['dav:fs-type1\/themes\/Portal8.0\/theme.html'], 'mime-type'=['text\/html']]] could not be processed: [EJCBD0021E: The URI [dav:fs-type1\/themes\/Portal8.0\/nls\/theme_en.html] and parameters [['themeURI'=['dav:fs-type1\/themes\/Portal8.0\/theme.html'], 'mime-type'=['text\/html']]] could not be processed: [EJCBD0019E: The data source identified by the URI [co:head] and parameters []] could not be processed: [java.lang.NullPointerException]]]\n\nAdditional review of the logs shows the entry:\n\nCaused by: java.lang.NullPointerException at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 481) at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 502) at com.ibm.wps.resolver.impl.ExtensionTracker.(ExtensionTracker.java: 518) at com.ibm.wps.resolver.resource.BlackWhiteListFactoryOnExtensionRegistry.< init>(BlackWhiteListFactoryOnExtensionRegistry.java:226) ... 136 more","answer":"the temporary directory for extension points has become corrupted. This can happen after a server is upgraded.","is_impossible":false,"contexts":[{"filename":"swg21459952.txt","text":"Title: IBM WebSphere Portal startup fails with EJCBC0002E: The service [<serviceName>] could not be located. - United States\n\nText:\nEJCBC0002E; EJPFD0016E; extensionregistry; CORFriendlySelectionServiceHome TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhen starting the WebSphere_Portal server, startup throws an exception: EJCBC0002E: The service could not be located. \n\nSYMPTOM\nIn the SystemOut.log, the following exception can be seen at the time the wps.ear application is started:\n===========================\n[1\/13\/11 11:00:56:875 EST] 00000015 Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.\ncom.ibm.portal.resolver.exceptions.LocalizedIOException: EJCBC0002E: The service [com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome] could not be located.\nat com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:201)\nat com.ibm.portal.resolver.helper.eclipse.Platform.createInstance(Platform.java:128)\nat com.ibm.wps.resolver.friendly.service.PortalFriendlySelectionBootstrapService.init(PortalFriendlySelectionBootstrapService.java:197)\nat com.ibm.wps.services.Service.init(Service.java:107)\nat com.ibm.wps.services.Service.init(Service.java:83)\nat com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:363)\n===========================\n\nThe service name in this case is \"com.ibm.wps.resolver.friendly.CORFriendlySelectionServiceHome\", but the name could vary. \n\nYou may also see warnings for various applications like this:\n\n===========================\n[1\/13\/11 11:00:54:250 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.skinlistprovider) not available for Extension: com.ibm.wps.engine.standardSkinListProvider\n[1\/13\/11 11:00:54:252 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.model.themelistprovider) not available for Extension: com.ibm.wps.engine.standardThemeListProvider\n[1\/13\/11 11:00:54:269 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.ContentNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AIContentNodeLinkGenerator\n[1\/13\/11 11:00:54:278 EST] 00000015 RegistryResol W CWXRS0023W: Extension Point (com.ibm.portal.resolver.model.NavigationNodeLinkGenerator) not available for Extension: com.ibm.wps.ai.rest.AINavigationNodeLinkGenerator\n===========================\n\n\nCAUSE\nThese messages indicate that the the temporary directory for extension points has become corrupted. This can happen after a server is upgraded.\n\n\nRESOLVING THE PROBLEM\nTo resolve this problem, you can do the following: \n\n\n1. Stop the WebSphere_Portal server\n\n2. Delete the contents of the following directory:\n\n<wp_profile root>\/temp\/<node name>\/WebSphere_Portal\/_extensionregistry \n\n3. Start the WebSphere_Portal server."}]},{"id":"TRAIN_Q466","question":"What happens if I lost my seed and salt value?\n\nIn ISDS, what happens if I lost my seed and salt value?\n\n\n\nThis dW Answers question is about an IBM document with the Title:\nOpen Mic Webcast: Configuring SDS 8.0.1 Virtual Appliance with a remote DB2 database - Tuesday, 17 Jan 2017 [presentation slides are attached; includes link to replay]","answer":"There is NO way to recover the seed value used during the instance creation if it has been lost. The only workaround is to create a new instance with a new encryption seed value and then use the db2ldif and ldif2db utilities to export and import data respectively. These utilities can be supplied with the new encryption seed and the salt value of the new instance. Thus the data would be preserved(alongwith the passwords) on this new instance.","is_impossible":false,"contexts":[{"filename":"swg21244655.txt","text":"Title: IBM Seed value used during the instance creation is lost : Recovery procedure - United States\n\nText:\nseed lost; idsgendirksf; Encryption Seed Value; key stash file TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Generating key stash file if the seed value which was used at the time of instance creation has been lost then there is no way to recover this seed value. \n\nRESOLVING THE PROBLEM\n \n\nThere is NO way to recover the seed value used during the instance creation if it has been lost. The only workaround is to create a new instance with a new encryption seed value and then use the db2ldif and ldif2db utilities to export and import data respectively. These utilities can be supplied with the new encryption seed and the salt value of the new instance. Thus the data would be preserved(alongwith the passwords) on this new instance.\n\nHere are the steps to follow:\n\n1. Set up a new instance says \"newinst\".\n\n$> idsicrt -I newinst -e thisismyencryptionseed -l (\/home\/newinst) -n\n\n$> idscfgdb -I newinst -w ldap -a newinst -t newinst -l (\/home\/newinst) -n\n\n$> idscfgsuf -s \"o=ibm,c=us\" -I newinst -n\n\n$> idsdnpw -u cn=root -p root -I newinst -n\n\n2. Note the encryption seed - \"thisismyencryptionseed\". Let us call this new_encryptionseed\n\n3. Once this new instance is setup note down the salt value generated by the new server instance by searching for \"cn=crypto,cn=localhost\".\n\n$> ldapsearch -D <administrator DN> -w <administrator password> -b \"cn=crypto,cn=localhost\" -s base objectclass=* ibm-slapdCryptoSalt\n\nLet us call this value: new_saltvalue\n\n4. Lets assume that the instance name with the forgotten encryption seed is \"oldinst\"\n\n5. Use the db2ldif utility on the instance with the forgotten encryptionseed, oldinst with the following options -\n\n$> db2ldif -o outputfile -I oldinst -k new_encryptionseed -t new_saltvalue\n\n6. Once this step is successfully completed the entire data from \"oldinst\" would be dumped in outputfile.\n\n7. Use the utilities like ldif2db to re-load all the data into the new server instance.\n\n\n\n\n\n\n\nHISTORICAL NUMBER"}]},{"id":"TRAIN_Q467","question":"How can we change the password for LDAP bind user?\n\nWe need to change our LDAP bind user due to security requirement. Is there any documentation for the procedure? ","answer":"The Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and\/or password. This procedure applies to FileNet Content Engine 4.x and above.","is_impossible":false,"contexts":[{"filename":"swg21442694.txt","text":"Title: IBM Procedure to change the username and\/or password for the FileNet Content Engine Directory Service Account, including the bootstrap user - United States\n\nText:\nchange; user; password; fem; directory service; bootstrapconfig; bootstrap user TECHNOTE (FAQ)\n\nQUESTION\n How do you change the user and\/or password for Directory Service Account used by the Content Engine? \n\nANSWER\nThe Directory Service user account and password are normally used in two product components: FileNet Enterprise Manager (FEM), and the application server. A coordinated update procedure should be followed when there is a need to change the user account and\/or password. This procedure applies to FileNet Content Engine 4.x and above. \n\n * \n * Note: \n * \n * \n\n\nIf the same user account is also used as the CE Bootstrap user, the corresponding user in the BootstrapConfig.properties needs to change as well. For changing the GCD admin user\/password in BootstrapConfig.properties specifically, refer to this documentation: \nhttp:\/\/publib.boulder.ibm.com\/infocenter\/p8docs\/v4r5m1\/index.jsp?topic=\/com.ibm.p8.doc\/admin\/security\/sec_how_change_bootstrap_pwd.htm [http:\/\/publib.boulder.ibm.com\/infocenter\/p8docs\/v4r5m1\/index.jsp?topic=\/com.ibm.p8.doc\/admin\/security\/sec_how_change_bootstrap_pwd.htm] \n\n\n1. Launch FEM and the application server's administrative console. \na. Login to FEM using the Directory Service account. \nb. Login to the application server administrative console with an administrator account. \n\nImportant: Do not close above two applications until you have completed step 5 below. \n\n\n2. Make LDAP account changes: \na. Change the password for an existing account on the LDAP server - Using LDAP interface, change the password for the CE Directory Service account. \nOR \nb. Create a new user account on the LDAP server for the CE Directory Service account. \n\n\n3. Add new user (if applicable), to FEM \nIf the bind user is also the CE admin user, then the bind user will need to be added to all the existing objects in the P8 domain. Please read Update object store with new users and groups [http:\/\/publib.boulder.ibm.com\/infocenter\/p8docs\/v4r5m1\/index.jsp?topic=\/com.ibm.p8.doc\/admin\/security\/sec_how_update_os.htm] for instructions \n\n\n4. Change Directory Configuration bind user in FEM \nUsing FEM (step 1a above), go to Domain properties > Directory Configuration > Select Directory Configuration > click on the Modify button > General Tab: \na. Modify the Directory Service User with new user's full distinguish name (DN) \nb. Click on Change password check box > change to a new password > click OK. \n\nAt this point you will be presented a dialog box with following message: \n\u201cThese changes require the application server to be restarted. Please restart the application server to incorporate these changes\u201d \n\nclick OK > click OK \n\nImportant: Do not restart the application server until you have completed step 5 below. \n\n\n5. Change the user in the application server's directory configuration \n\n- For Websphere, in the WebSphere Administrative Console, go to Global Security > click on Configure under User Account Repository > Modify Bind Distinguished Name (DN) > Modify Bind Password > click OK and Save changes \n\n- For WebLogic go to Security Realms > myrealm > Providers > ldap provider and click on \"Provider Specific\" tab in WebLogic Admin Console. Change \"Principal\" and \"Credential\". \n\n- For JBoss go to <JBoss Home>\\server\\<CE Server>\\conf directory and edit \"login-config.xml\". \nFind \"FileNet\" application-policy and in login module change bindDN\/bindCredential. \n\n\n6. Changing the CE Bootstrap user \n\nFor CE 4.5.x and above: \na. In the Configure Bootstrap Properties task, set the Bootstrap Operation property to Modify Existing. \nb. Confirm that the Bootstrapped EAR file property contains the path to the bootstrap file you need to edit. \nc. Change the Bootstrap user password. Use Configuration Manager's features to save and run the task. \nd. Run Configuration Manager's Deploy Application. \n\nFor CE 4.0: \nNote: This step is needed only if the GCD user name is the same as the Directory Service account. Note that the example below is for a Windows environment. \n\n- For WebSphere \na. Open command prompt window, go to folder where EAR file reside (it differs depending on CE version). For example, in CE 4.5.1, go to \"<CE Home> \\ tools \\ configure \\ profiles \\ <profile> \\ ear\" \nb. Backup Engine-ws.ear \nc. Execute the command below: \n\njava \u2013jar \u201cc:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar\u201d \u2013e Engine-ws.ear --username <username> --password <password> \n\nd. Since the Engine-ws.ear file has been deployed in the WebSphere's installedApps path, the Bootstrap file need to be copied to the path manually. Extract the props.jar file from the ear file by utility such as Winzip, copy the props.jar file to theinstalledApps location - \u201c<WebSphere Home>\\ AppServer\\ profiles \\ <profile name> \\ InstalledApps \\<serverNodecell> \\ FileNetEngine.ear \\ APP-INF \\ lib \\\" \n\nNote that an alternative to copying the props.jar file is to uninstall and re-install the updated ear file in WebSphere. \n\n- For WebLogic \na. Open command prompt window, go to folder - \"<WebLogic home> \\ user_projects \\ domains \\ <domain> \\ servers \" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava \u2013jar \u201cc:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar\u201d \u2013e Engine-wl.ear --username <username> --password <password> \n\n- For JBoss \na. Open command prompt window, go to folder - \"<JBoss Home> \\ server \\ <server> \\ deploy \\\" \nb. Backup FileNetEngine.ear \nc. Execute the command below: \n\njava \u2013jar \u201cc:\\program files\\FileNet\\ContentEngine\\lib\\BootStrapConfig.jar\u201d \u2013e Engine-jb.ear --username <username> --password <password> \n\n\n7. Remove cached files in the application server \n- Close FileNet Enterprise Manager (Step 1a) \n- Close Administrative Console (Step 1b) \n- Stop the application server \n- Remove the cached FileNetEngine directory in the application server. \nFor example, the default windows path on Websphere 6.0 is \n\"C:\\program files\\Websphere\\AppServer\\profiles\\<profile name>\\temp\\<server node>\\ \n<server>\\FileNetEngine\" \n\n\n8. Restart the application server, and login to FEM using the new user and password. \n\n\n9. Troubleshooting \n\nIf CE fails to start due to mistakes in the above procedures, you may not be able to redo the change through these procedures because FEM will fail to run. \nIn this case, you can do the following: \n\n- Back out the change made to the GCD database in step 3 by deleting the latest row in the FNGCD table. \n- Back out the change made to the application server in step 4 by redoing the procedure with the previous user. \n- Back out the change made to the BootstrapConfig.properties file's GCD user by using the backup EAR file \n- Restart the application server, and login to FEM using the previous user."}]},{"id":"TRAIN_Q468","question":"How can I alleviate performance problems with the octigate database?\n\nITCAM-related question: How can I alleviate performance problems with the octigate database?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q469","question":"Help with Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WSRR \n\nI need to understand details regarding Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository ( CVE-2011-4343). Where can I find this information? ","answer":"CVEID: CVE-2011-4343 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2011-4343] \nDESCRIPTION: Apache MyFaces could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability using specially crafted parameters to inject EL expressions into input fields mapped as view parameters and obtain sensitive information. \nCVSS Base Score: 5 \nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132287 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132287] for the current score \nCVSS Environmental Score*: Undefined \nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22010993.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server shipped with Jazz for Service Management (CVE-2017-1583, CVE-2011-4343) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are two potential information disclosure vulnerabilities that affects the Java Server Faces (JSF) component used by WebSphere Application Server. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1583 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1583]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper error handling by MyFaces in JSF.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132342 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132342] 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\n\nCVEID: CVE-2011-4343 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2011-4343] \nDESCRIPTION: Apache MyFaces could allow a remote attacker to obtain sensitive information. An attacker could exploit this vulnerability using specially crafted parameters to inject EL expressions into input fields mapped as view parameters and obtain sensitive information. \nCVSS Base Score: 5 \nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132287 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/132287] for the current score \nCVSS Environmental Score*: Undefined \nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:P\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nJazz for Service Management version 1.1.0 - 1.1.3\n\nREMEDIATION\/FIXES\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version Affected Supporting Product Security Bulletin Jazz for Service Management version 1.1.0 - 1.1.3 Websphere Application Server Full Profile 8.5.5 Security Bulletin: Multiple vulnerabilities affect Java Server Faces (JSF) used by WebSphere Application Server (CVE-2017-1583, CVE-2011-4343) [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22008707] WORKAROUNDS AND MITIGATIONS\nPlease refer to WAS iFix\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 27-November-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."}]},{"id":"TRAIN_Q470","question":"Does Logout button get disabled in ICM for SSO with Tivoli Access Manager ?\n\nDoes Logout button get disabled in ICM for SSO with Tivoli Access Manager ? ","answer":"IBM Content Navigator disables the Log Out option under SSO environments. However, under some SSO environments or desktop load scenarios, such as SPNEGO\/Kerberos on a WebLogic Application Server, IBM Content Navigator enables the Log Out option.\n\n\n\n\nIf the Log Out option is enabled but does not work correctly in your SSO environment, you can remove the Log Out option by customizing the banner user session context menu that is used by your desktop configuration.","is_impossible":false,"contexts":[{"filename":"swg27042940.txt","text":"Title: IBM Content Navigator known issue: In a SPNEGO\/Kerberos Single sign-on environment, IBM Content Navigator the Log Out option is enabled - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n In a SPNEGO\/Kerberos single sign-on (SSO) environment, your IBM Content Navigator session shows the Log Out option as enabled when you select the drop-down menu on the user name. However, the option should be disabled. \n\nCONTENT\nIBM Content Navigator disables the Log Out option under SSO environments. However, under some SSO environments or desktop load scenarios, such as SPNEGO\/Kerberos on a WebLogic Application Server, IBM Content Navigator enables the Log Out option.\n\n\n\n\nIf the Log Out option is enabled but does not work correctly in your SSO environment, you can remove the Log Out option by customizing the banner user session context menu that is used by your desktop configuration. \n\nTo remove the Log Out option: \n\n 1. In the administration tool, select Menus. \n 2. Enter \"User\" in the Name contains filter field. \n 3. Select the Default banner user session context menu and click Copy. \n 4. Enter a name for the new menu such as \"Banner user session context menu - no Log Out option\". \n 5. Remove the Log Out from the Selected list. \n 6. Save the new menu. \n 7. Open the Desktops configuration, then open your desktop configuration. \n 8. Select the Menus tab and scroll to the Feature Context Menus section. \n 9. Select the new menu that you created for the Banner user session context menu menu type. \n 10. Save your desktop. \n\n\nThe change to the menus takes effect when the modified desktop is reloaded. \n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Case Manager AIX, Linux, Linux on System z, Windows 5.2.1.0"}]},{"id":"TRAIN_Q471","question":"Why can't I search groups after upgrading to WebSphere Application Server 8.5.5.10?\n\nWhy can't I search groups after upgrading to WebSphere Application Server 8.5.5.10?","answer":"PI69518 resolves the following problem:\n\nERROR DESCRIPTION: \nAfter upgrade to 8.5.5.10, there are cases when group \nsearch fails from \"Users and Groups\" -> \"Administrative \nGroups\" panel. When it happens in GUI, the same issue \nhappens with AdminTask listRegistryGroups command.","is_impossible":false,"contexts":[{"filename":"swg24042833.txt","text":"Title: IBM PI69518:group search fails with a classcast exception after upgrade to 8.5.5.10 - United States\n\nText:\nPI69518; PI69518; PI69518 DOWNLOADABLE FILES\n\nABSTRACT\n group search fails with a classcast exception after upgrade to 8.5.5.10 \n\nDOWNLOAD DESCRIPTION\nPI69518 resolves the following problem:\n\nERROR DESCRIPTION: \nAfter upgrade to 8.5.5.10, there are cases when group \nsearch fails from \"Users and Groups\" -> \"Administrative \nGroups\" panel. When it happens in GUI, the same issue \nhappens with AdminTask listRegistryGroups command. \n\nSeeing the following in systemout.log: \n[9\/20\/16 15:37:21:077 EDT] 00000076 GroupDetailAc W \nlistRegistryGroups: Command not successful: \njava.lang.ClassCastException: javax.management.ObjectName \nincompatible \nwith javax.management.AttributeList \n\n************************************************** \n\nIn traces we see stack: \n\n[9\/20\/16 15:36:05:658 EDT] 00000076 SecurityRealm 3 exception \ncaught \njava.lang.ClassCastException: \njavax.management.ObjectName incompatible with \njavax.management.AttributeList \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.getLD \nAPProps(SecurityRealmProvider.java:1420) \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.getLD \nAPList(SecurityRealmProvider.java:1363) \nat \ncom.ibm.ws.security.admintask.securityDomain.SecurityRealmProvid\ner.listR \negistryGroups(SecurityRealmProvider.java:402) \nat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) \nat \nsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor\nImpl.jav \na:95) \nat \nsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod\nAccessor \nImpl.java:56) \nat java.lang.reflect.Method.invoke(Method.java:620) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleCommand\nProvider \n.executeReal(SimpleCommandProvider.java:156) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleCommand\nProvider \n.execute(SimpleCommandProvider.java:142) \nat \ncom.ibm.websphere.management.cmdframework.provider.SimpleAdminCo\nmmand.ex \necute(SimpleAdminCommand.java:57) \n\nLOCAL FIX: \nnone \n\nPROBLEM SUMMARY\n\nUSERS AFFECTED:\nAll users of IBM WebSphere Application\nServer\n\nPROBLEM DESCRIPTION:\njava.lang.ClassCastException when\ngroup search is performed.\n\nRECOMMENDATION:\nNone\n\nThere was a bug in the code that uses a registry object that\nmay not contain necessary attributes for the group search and\ncauses ClassCastException.\n\nPROBLEM CONCLUSION: \nThe bug was fixed in the code to correct the exception. \n\nThe fix for this APAR is currently targeted for inclusion in \nfix pack 8.5.5.11. Please refer to the Recommended Updates \npage for delivery information: \nhttp:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980 [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980]\n\nPREREQUISITES\nNone\n\nINSTALLATION INSTRUCTIONS\nPlease review the readme.txt for detailed installation instructions.\n\nURL LANGUAGE SIZE(Bytes) V85 Readme [ftp:\/\/public.dhe.ibm.com\/software\/websphere\/appserv\/support\/fixes\/PI69518\/8.5.5.10\/readme.txt] US English 6584 \nDOWNLOAD PACKAGE\n\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.10-WS-WAS-IFPI69518 09-28-2016 US English 276737 HTTP [http:\/\/www-933.ibm.com\/eserver\/support\/fixes\/fixcentral\/swgquickorder?fixes=8.5.5.10-WS-WAS-IFPI69518&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=swg24042833&aid=1]Problems (APARS) fixed [\/support\/docview.wss?uid=swg24042833&aid=2]Problems (APARS) fixed\nPI69518"}]},{"id":"TRAIN_Q472","question":"The Ping Probe will not start with SetUID configured\n\nThe Netcool OMNIbus Ping Probe will not start with SetUID configured. What should I check? ","answer":"To enable non-root user to start the probe, you need to change the owner to root and permissions to setuid. And AIX ignores the LIBPATH setting when program runs as setuid root, so you also need to put either a copy of the required libraries, or a symbolic link to the required libraries in one of the trusted paths like \/lib or \/usr\/lib.","is_impossible":false,"contexts":[{"filename":"swg21499280.txt","text":"Title: IBM Unable to start Ping Probe by non-root user on AIX - United States\n\nText:\nPing probe; non root; start; permissions TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Ping probe fails to start when the probe is installed and started by non-root user. \n\nSYMPTOM\nThe following error is seen in the probe's log: \n\nError: E-P_P-002-038: Could not change euid: Operation not permitted\nError: E-P_P-002-017: IPv4 socket failed: specified action does not have access permission of the file\nError: E-P_P-002-037: This program can only be run by root, or it must be setuid root.\n\n\nCAUSE\nPing probe needs permissions which allow it to run as root and the LIBPATH setting should be changed.\n\n\nENVIRONMENT\nAIX\n\n\n\nRESOLVING THE PROBLEM\nTo enable non-root user to start the probe, you need to change the owner to root and permissions to setuid. And AIX ignores the LIBPATH setting when program runs as setuid root, so you also need to put either a copy of the required libraries, or a symbolic link to the required libraries in one of the trusted paths like \/lib or \/usr\/lib. \n\n\n1. Change the owner to root and permissions to setuid.\ne.g\n# cd $OMNIHOME\/probes\/aix5\/\n# chown root:root nco_p_ping\n# chmod +s nco_p_poing\n\n2. Put a symbolic link to the required libraries.\ne.g\n# cd \/usr\/lib\n\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libgsk*\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libPa_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libnetcool_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libslclient_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libOpl_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libsybct_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libsybcs_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libsybtcl_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libsybcomn_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libtre.a\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libsybintl_r.so\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libicuuc40.a\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libicui18n40.a\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libicudata40.a\n\n\nNote:\nThe required libraries can be seen by the following command:\n# dump -H $NCHOME\/omnibus\/platform\/aix5\/nco_p_ping\n\nNote:\nIf there are newer modules of the required libraries, it's better to create a symbolic link to the newer module.\ne.g\nRun\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libicui18n40.1.a\nrather than,\n# ln -s \/opt\/IBM\/netcool\/platform\/aix5\/lib\/libicui18n40.a\n\nBut, please note that it would be better to create the symbolic links again whenever after you apply Fix pack for OMNibus core.\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Netcool\/OMNIbus Ping AIX All Versions"}]},{"id":"TRAIN_Q473","question":"Why Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?\n\nSummarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table. What's the fix?\n","answer":"Update the invalid data with a valid UTF-8 character string.","is_impossible":false,"contexts":[{"filename":"swg21684365.txt","text":"Title: IBM SqlException with message \"Caught java.io.CharConversionException.\" and ERRORCODE=-4220 - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When an application uses the IBM Data Server Driver for JDBC and SQLJ (also known as the JCC driver) and is connected to a database with code set UTF-8 (code page 1208), it throws an\nSqlException with message including \"Caught java.io.CharConversionException\" and ERRORCODE=-4220 if the data in a character column that it queries contains a sequence of bytes that is not a valid UTF-8 string. \n\nSYMPTOM\nAn exception is thrown similar to this: \n\n com.ibm.db2.jcc.am.SqlException: [jcc][t4][1065][12306][XXX.XXX.XXX] Caught java.io.CharConversionException. See attached Throwable for details. ERRORCODE=-4220, SQLSTATE=null\n[...]\nCaused by: java.nio.charset.MalformedInputException: Input length = XXX\n[...]\nCaused by: sun.io.MalformedInputException\nat sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:XXX)\n[...]\n\n\n\nCAUSE\nThe JCC driver throws the exception when data in a character column that it queries is not a valid string in the database code page.\n\nThe invalid data could have been input to the database in the following ways:\n\n\n * By running an SQL statement which writes byte values to the database. For example: INSERT INTO tab1 VALUES (X'C3')\n\n * By running the IMPORT or LOAD commands for files which contain character data that is not in the code page of the client machine, so the appropriate code page conversion was not done. To make sure that the the appropriate code page conversion is done when running IMPORT or LOAD, specify the code page of the input file by including the \"codepage=x\" file type modifier (specifying the code page in place of x).\n\nDIAGNOSING THE PROBLEM\nYou can use the HEX function to find out what are the byte values in a character column. \n\nFor example, to find out the byte values in column COL1 in table TAB1, run: \nSELECT HEX(col1) FROM tab1\n\n\nRESOLVING THE PROBLEM\nUpdate the invalid data with a valid UTF-8 character string. \n\n\nAlternatively, for JCC driver versions that support it you can set the JCC configuration property db2.jcc.charsetDecoderEncoder=3 so that instead of throwing an exception the JCC driver returns the Unicode REPLACEMENT CHARACTER (U+FFFD) in place of a sequence of bytes that is not a valid UTF-8 string. \nThe JCC configuration property db2.jcc.charsetDecoderEncoder is supported in versions of the JCC driver that come with DB2 LUW 9.5 Fix Pack 8 and later (APAR IC74896), DB2 LUW 9.7 Fix Pack 5 and later (APAR IC74895), and all DB2 LUW releases from DB2 10.1 onwards.\n\nFor example, suppose you have a Java program MyApp.java that executes an SQL query of a database column that contains a sequence of bytes that is not a valid string.\nWhen you run:\njava MyApp\nit throws an exception. But when you run:\njava -Ddb2.jcc.charsetDecoderEncoder=3 MyApp\nit returns the string with any invalid sequence of bytes replaced by the Unicode REPLACEMENT CHARACTER. \n\nThe Unicode REPLACEMENT CHARACTER often appears like this \n(a diamond with a question mark inside it) : [\/support\/docview.wss?uid=swg21684365&aid=1]\n\nRELATED INFORMATION\n APAR IC78495 [https:\/\/www-01.ibm.com\/support\/entdocview.wss?uid=swg1IC74895]\nAPAR IC74896 [https:\/\/www-01.ibm.com\/support\/entdocview.wss?uid=swg1IC74896]\nMaking the setting for IBM Data Studio [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21612346]\nMaking the setting for IBM Content Collector [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSAE9L_4.0.0\/com.ibm.content.collector.doc_kc\/troubleshooting\/ts_afu_java_throws_exception.dita]\nUDF to identify invalid data in a UTF-8 character colum [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21608985]\nHow invalid data can get into a UTF-8 character column [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21412846]\nLOAD command [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0008305.html]\nIMPORT command [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0008304.html]\nHEX function [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.sql.ref.doc\/doc\/r0000811.html]"}]},{"id":"TRAIN_Q474","question":"CICS Transaction Server for z\/OS 4.1 and 4.2 End of Service dates\n\nWhen will CICS Transaction Server for z\/OS (CICS TS) V4.1 and V4.2 be withdrawn from support? I need to make sure that I upgrade to a newer release before the end of support (EOS) date. I would like to know what product replacement information is in the announcement letter. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q475","question":"How can I fix blank pull down \"Console Settings\" menu after successful install of JazzSM 1.2.1.1 and WebSphere 8.5.5.9?\n\nWebSphere version 8.5.5.9 didn't include jar files that were available in previous releases of WebSphere that are required by DASH for various tasks.","answer":"The missing jar files are included in DASH 3.1.2.1 Cumulative Patch 5, which you can download from this site: \n\n\nhttp:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~Tivoli\u220fuct=ibm\/Tivoli\/Jazz+for+Service+Management&release=1.1&platform=All&function=all [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~Tivoli&product=ibm\/Tivoli\/Jazz+for+Service+Management&release=1.1&platform=All&function=all]","is_impossible":false,"contexts":[{"filename":"swg21981870.txt","text":"Title: IBM Missing Icon pulldown options in DASH main menu after 3.1.2.1 Install - United States\n\nText:\nDASHL2; Console Settings; missing.; icons; WAS 8.5.5.9; DASH 3.1.2.1; Cumulative patch 5; CP5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After fresh install of WAS 8.5.5.9 with JazzSM 1.1.2.1\/DASH 3.1.2.1, the \"Console Settings\" is missing entries and other expected icons are missing from the DASH main page. \n\nSYMPTOM\nAfter successful installation of JazzSM 1.1.2.1\/DASH 3.1.2.1 with WebSphere 8.5.5.9, some of the icons in the main DASH window are missing on the left.\n\n\nCAUSE\nIt was recently discovered that some .jar files were not included in WebSphere 8.5.5.9, that were available in previous WebSphere releases, and are required for several functions in DASH.\n\nENVIRONMENT\nJazzSM 1.1.2.1 \/ DASH 3.1.2.1 WAS 8.5.5.9\n\nDIAGNOSING THE PROBLEM\nAfter you login to DASH and select \"Console Settings\", the displayed window, which should have several lines, is blank:\n\n\n[\/support\/docview.wss?uid=swg21981870&aid=1]\n\nAlso, in this case there wasn't any icons in the upper left portion of the main DASH window.\n\n\nRESOLVING THE PROBLEM\nThe missing jar files are included in DASH 3.1.2.1 Cumulative Patch 5, which you can download from this site: \n\n\nhttp:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~Tivoli\u220fuct=ibm\/Tivoli\/Jazz+for+Service+Management&release=1.1&platform=All&function=all [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~Tivoli&product=ibm\/Tivoli\/Jazz+for+Service+Management&release=1.1&platform=All&function=all] \n\n[\/support\/docview.wss?uid=swg21981870&aid=2] [\/support\/docview.wss?uid=swg21981870&aid=2]\nIf you have any questions as to whether DASH 3.1.2.1 Cumulative Patch 5 has been installed, please run this command:\n\n<JazzSM_HOME>\/ui\/bin\/consolecli Version if patch 5 has been installed, it will have output showing the patch number shown in the red square in the screen shot:\n\n[\/support\/docview.wss?uid=swg21981870&aid=3] [\/support\/docview.wss?uid=swg21981870&aid=3]\n\nIf installing on a UNIX server, you will see several of these messages, they indicate that the jar files are not currently on the server, but the Patch install will finish successfully.\ncp: \n\/opt\/IBM\/JazzSM\/ui\/..\/profile\/installedApps\/JazzSMNode01Cell\/\/isc.ear\/TI \nPChangePasswd.war\/js\/ibm\/tivoli\/tip\/changepasswd\/nls\/iw\/messages.js: No \nsuch file or directory \n.\n.\nPatch 201603301212 successfully installed."}]},{"id":"TRAIN_Q476","question":"How to turn on event debug to troubleshoot Impact Event Processing stopping ?\n\nImpact support has requested a set of recreate logs with event logging turned on. What are the steps to do this?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q477","question":"On 30th June, could the Leap Second cause Linux to freeze and impact my MQ?\n\nOn 30th June, could the Leap Second cause Linux to freeze and impact my MQ? ","answer":"In the past, the addition of leap seconds caused some systems running older Linux kernels to fail. IBM MQ and WebSphere MQ queue managers running on these systems generated repeated FDC files showing Probe Id XY348010 or XC272003 from xcsCreateThread, with error code xecP_E_NO_RESOURCE. Other FDCs are also possible.","is_impossible":false,"contexts":[{"filename":"swg21602521.txt","text":"Title: IBM Leap Second bug in older Linux kernels may affect IBM MQ and WebSphere MQ - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n Leap seconds are a periodic one-second adjustment of Coordinated Universal Time (UTC) required to keep a system's time of day close to the mean solar time.\n\nA leap second is scheduled for 31 December 2016 at 23h 59m 60s UTC.\n\nIn the past, the addition of leap seconds caused some systems running older Linux kernels to fail. IBM MQ and WebSphere MQ queue managers running on these systems generated repeated FDC files showing Probe Id XY348010 or XC272003 from xcsCreateThread, with error code xecP_E_NO_RESOURCE. Other FDCs are also possible. \n\nCONTENT\nOn 31 December 2016, the Network Time Protocol (NTP) daemon will schedule a leap second [http:\/\/en.wikipedia.org\/wiki\/Leap_second] to occur at midnight, making the final minute of the day 61 seconds long. Prior leap second insertions, including the 30 June 2016 leap second, caused some Linux systems to exhibit unexplained high CPU usage.\n\n\nIBM MQ and WebSphere MQ use the Native POSIX Thread Library (NPTL) which relies on futuxes (\"fast userspace mutexes\") for synchronization between threads. Futexes can exhibit high CPU spins after leap seconds on Linux kernel versions 2.6.22 through 3.5-rc7, inclusive, although some Linux distributions shipped patches for kernels in this range:\n\n\n * \n * Leap Second to be added on December 31st 2016\n * \n * \n * \n * General information on Leap Second 2016\n * \n * Fixes and workarounds to avoid issues caused by Leap Second 2015\n * \n * \n * \n * Addition of leap second causes spuriously high CPU usage and futex lockups\n\n\n\nContact your Linux vendor to check the status of other distributions, or check the Linux kernel version using \"uname -r\" and confirm that your system is older than 2.6.22 or running 3.5 or later. \n\nIf you encounter this problem, the following workaround may resolve the high CPU usage. As root, run: \n * date -s \"$(LC_ALL=C date)\"\n\n \n\nPRODUCT ALIAS\/SYNONYM\n IBM MQ WMQ WebSphere MQ MQSeries"}]},{"id":"TRAIN_Q478","question":"How to define shared libraries for ODM ruleApps on WAS traditional?\n\nWhat is the proper way to define a shared lib for RuleApps without giving up the isolated mode of the XU resource adapter? Is it \"works as designed\" that isolating of the XU prevents the resource adapter from seeing shared lib classes from other classloaders? ","answer":"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.","is_impossible":false,"contexts":[{"filename":"swg21634612.txt","text":"Title: IBM Use\"isolate the resource provider\" to establish data source connections using a different JDBC driver from the same database vendor - United States\n\nText:\nisolate this resource provider TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customer has defined 3 Oracle JDBC Providers at cell, node and server\nscope. Client have following configuration in websphere JDBC provider. \n\nIn Cell Scope - C:\\jdbc\\ojdbc5\\ojdbc5.jar \n\nIn Node Scope - C:\\jdbc\\ojdbc6_g\\ojdbc6_g.jar \n\nIn Server Scope- C:\\jdbc\\ojdbc6\\ojdbc6.jar \n\nIn this case value of JDBC driver path in WebSphere variable is identical. Nornally, If JDBC provider configure at server level then server level driver will get load first. But in this case since all three drivers are from same vendor, So we can not control which driver is picking up. In this case \n\"C:\\jdbc\\ojdbc6\\ojdbc6.jar\" should be loaded first but instated, ojdbc5.jar was load first\n\n[13. 4. 5 12:05:15:625 KST] 00000023 CompoundClass < loadClass \n\noracle.jdbc.driver.OracleDriver \n\nloader=com.ibm.ws.bootstrap.ExtClassLoader@5dc95dc9 \n\nsource=file:\/C:\/jdbc\/ojdbc5\/ojdbc5.jar Exit \n\n\n\n\n\n\nSYMPTOM\nDue to multiple JDBC drivers from the same vendor were configured in different scopes, the wrong driver class was loaded.\n\n\nCAUSE\nWhen multiple versions of the JDBC driver are configured in WebSphere Application Server, irrespective of the scopes, there is a possibility of a collision of the classes and we cannot predict from which version of the driver jar the class got loaded. \n\nRESOLVING THE PROBLEM\n In order to support the existence of multiple versions of the driver jars, the \"Isolate this resource provider\" configuration helps to ensure there are no conflicts. This needs to be configured on each JDBC Provider. You cannot isolate only one resource provider, all the provider configurations in different scopes will have to be configured with the \"Isolate this resource provider\" setting. In this scenario, the resource provider classes from different versions of the jars are not imported or accessed to verify if the isolation has indeed worked. In order to use the server-scoped resource provider the datasource using the server-scoped jdbc provider will have to be referenced from the application after isolating the resource providers and using a resource reference in the application. \n\n\nGo to the JDBC Provider and enable \"isolate the resource provider\". When \"Isolate this resource provider\" is enabled, it ensures that only the jar that was specified in the classpath will be used for all the datasources under that particular JDBC provider. \n\n \n\nHere are links to Knowledge Center articles which contain further information on the setting: \n\n\nJDBC provider settings [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_9.0.0\/com.ibm.websphere.nd.multiplatform.doc\/ae\/udat_manjdbcprodet.html]\n\nConsiderations for isolated resource providers [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_9.0.0\/com.ibm.websphere.nd.multiplatform.doc\/ae\/rdat_isolatedlimitations.html]"}]},{"id":"TRAIN_Q479","question":"Why cant I load and AEL when using IE 11 JRE 8\n\nApplication Blocked by Java Security\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q480","question":"Whether IBM Case Manager is using Apache Struts?\n\nWhether IBM Case Manager is using Apache Struts? If yes, could you let us know which version? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q481","question":"Connection pooling parameters (unusedTimeout, agedTimeout) won't work as expected on bpm 8.5.5 and oracle 11g RAC\n\nWe have set the connection pooling parameters to unusedTimeout=300, agedTimeout=600, minConnections=0 and reapTimeout=180 seconds for all pools. Our expectation is that maximum after 13 minutes any connection shall be renewed (8 minutes for unused ones). However we observe connections issued by CMNuser and PSuser that last for days\/weeks. Did anyone face a similar issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q482","question":"Is there a limit to the number of items that can be listed within an \"in\" list as part of a where clause?\n\nIs there a limit to the number of items that can be listed within an \"in\" list as part of a where clause? ","answer":"The short answer is no limit.\n\n\nBy default we create a virtual table for any \"in list\" with more than 5 values.\n\nThe only limitation with large \"in list\" statements would be the memory needed to compile the query. If the query is too complex, you can potentially run out of memory, but that will not affect other sessions since this happens inside the postgres process assigned to that session. The parameter that is responsible for this behaviour is inlist_threshold and it is safe to increase this value to 100, but not more.","is_impossible":false,"contexts":[{"filename":"swg21698950.txt","text":"Title: IBM Is there a limit to the number of items that can be listed within an \"in\" list as part of a where clause? - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Is there a limit to the number of items that can be listed within an \"in\" list as part of a where clause? \n\nCAUSE\nEvery time the query optimizer finds a \"(NOT) IN\" statement in the query, a decision must be made:\nOption A: Evaluate the condition sequentially for every member of the IN-list, or \nOption B: create a temporal virtual table from this list and use JOIN logic for evaluation. \n\nIf the amount of members in the IN-list is smaller than the value of INLIST_THRESHOLD, then option A is used. \nIf the amount of members in the IN-list is equal or bigger than the value of INLIST_THRESHOLD, then option B is used.\n\n\nENVIRONMENT\nAny IBM PureData System for Analytics with any NPS Release\n\n\n\nRESOLVING THE PROBLEM\nThe short answer is no limit.\n\n\nBy default we create a virtual table for any \"in list\" with more than 5 values.\n\nThe only limitation with large \"in list\" statements would be the memory needed to compile the query. If the query is too complex, you can potentially run out of memory, but that will not affect other sessions since this happens inside the postgres process assigned to that session. The parameter that is responsible for this behaviour is inlist_threshold and it is safe to increase this value to 100, but not more.\n\nshow inlist_threshold;\n\nset inlist_threshold=<value>;\n\n \n\nPRODUCT ALIAS\/SYNONYM\n pda netezza"}]},{"id":"TRAIN_Q483","question":"How do I tell when there are mismatched MQ jars in my application server?\n\nMismatched jar files can cause strange and unpredictable errors when using the MQ JMS classes. ","answer":"Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.","is_impossible":false,"contexts":[{"filename":"swg21681142.txt","text":"Title: IBM Solving IBM MQ Java code version mismatches using the mqjavalist.sh script - United States\n\nText:\nWebSphere MQ WMQ TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Java\u2122 SE applications and Java EE application servers such as WebSphere Application Server do not use a consistent set of MQ Java archives, applications can fail in unpredictable ways. If WebSphere Application Server notices a mismatch, it issues this message: \"MQJCA1008 The WebSphere MQ classes for JMS were found in the class path but were not the correct version. This error can occur if the application server finds an earlier version of the WebSphere MQ classes for JMS in the class path. The error can also occur if you do not configure WebSphere Application Server to use the correct version of the WebSphere MQ classes for JMS.\" \n\nENVIRONMENT\nThe mqjavalist.sh script runs on Linux and UNIX systems and can identify Java archives and classes from MQ V5.3 and later versions. Although the mqjavalist.sh script does not run on Windows systems, it is possible to zip up a directory structure on Windows in order to examine it with mqjavalist.sh on a different system. To use the mqjavalist.sh script, download it from the bottom of this page, copy it to the target system, and make the script executable. Make sure that either the unzip command or the Java jar command is available in your PATH before running mqjavalist.sh. For example:\n\n\n\n 1. Preparing to run mqjavalist.sh\n 2. \n 3. sh> chmod +x mqjavalist.sh \n sh> PATH=$PATH:\/opt\/java7\/bin \n \n\n\n\n\nDIAGNOSING THE PROBLEM\nIBM MQ ships a number of Java archives (jar files) that applications use to connect to MQ and work with messages. For Java EE environments, MQ provides a Resource Adapter called wmq.jmsra.rar which contains the jar files required by JMS applications. Java SE and Java EE applications must use a consistent set of MQ jar files at the same maintenance level, or else they might experience a wide variety of problems including intermittent errors, performance problems, and other failures.\n\nIt is common to find multiple versions of the MQ jar files in the Java CLASSPATH, or invalidly bundled in Java applications (.ear, .war, and .jar files). Finding and eliminating duplicate copies of the MQ jar files can be a difficult task, but the mqjavalist.sh script simplifies that task on Linux and UNIX systems.\n\n\n\n * Syntax\n * Examples\n * WebSphere Application Server\n * Sample output\n * Resolving problems\n * Download\n\n\n\nSYNTAX\n\n 1. mqjavalist.sh -? | -h \n 2. \n 3. mqjavalist.sh [-v] [-r] [-f File] -d Directory ...\n 4. \n 5. \n 6. \n 7. -?:\n 8. \n 9. \n 10. -h:\n 11. \n 12. \n 13. -v:\n 14. \n 15. \n 16. -r:\n 17. \n 18. \n 19. -f File\u200b:\n 20. \n 21. \n 22. -d Directory:\n 23. \n 24. \n 25. \n 26. \n 27. \n 28. The mqjavalist.sh script can take several minutes to complete, depending on the number of Java archives to search and whether you perform a recursive examination of archive files. While running, the script regularly prints its status and the percentage of work completed.\n\n\nBack to top\n\n\n\nEXAMPLES\n\n 1. Search for MQ files under \/usr\/IBM\/WebSphere and save the results to the file mqlist.txt:\n \n mqjavalist.sh -f mqlist.txt -d \/usr\/IBM\/WebSphere\n 2. \n 3. \n 4. Perform a recursive search of archives under \/opt\/IBM:\n \n mqjavalist.sh -r -d \/opt\/IBM\n 5. \n 6. \n 7. Recursively search archive files under the \/opt\/IBM\/IIB and \/opt\/mqm directories and enable verbose output to ~\/output.txt:\n \n mqjavalist.sh -vrf ~\/output.txt -d \/opt\/IBM\/IIB -d \/opt\/mqm\n 8. \n\n\nBack to top\n\n\n\nWEBSPHERE APPLICATION SERVER\n\nWebSphere Application Server and other IBM products built on WebSphere Application Server normally show the MQ jar files in more than one location. Except as noted below, the copies of the MQ jar files should match the versions listed on this page [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg21248089]. Any copies of the MQ jar files other than those listed below might represent a problem: \n\n\n 1. WebSphere Application Server V8.5.5, V8.5 and V8.0\n 2. \n 3. \n\n\n\n 1. WebSphere Application Server V7.0\n 2. \n 3. \n 4. \n 5. \n 6. If you created a WebSphere Application Server V7.0 profile before applying fix pack 7.0.0.1 or later, you must update the profile to use the correct MQ Resource Adapter path [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSAW57_7.0.0\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/tmj_wmqra_restoredefault.html]. Otherwise, the application servers in that profile will use the old MQ Resource Adapter jars under the profile installedConnectors\/wmq.jmsra.rar directory rather than the MQ jars in the main installedConnectors\/wmq.jmsra.rar directory, which are kept up to date by WebSphere Application Server fix packs.\n\n\n 1. WebSphere Application Server V6.1\n 2. \n 3. \n\n\n\nBack to top\n\n\n\nSAMPLE OUTPUT\n\n 1. sh> \n 2. .\/mqjavalist.sh -r -f mqlist.txt -d \/opt\/IBM\/WebSphere\/AppServer\n 3. \n 4. Running mqjavalist.sh V1.4 on SUSE Linux Enterprise Server 10 (ppc) with arguments: -r -f mqlist.txt -d \/opt\/IBM\/WebSphere\/AppServer\n \n mqjavalist.sh: Searching directory \/opt\/IBM\/WebSphere\/AppServer\n mqjavalist.sh: 2180 possible Java archives found\n 1. Found 80 MQ classes in classes.jar in WMQHTTP.war in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/Dmgr01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:56 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/Dmgr01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear\n 2. Found 80 MQ classes in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/installedApps\/aemtux1Cell01\/WMQHTTP_war.ear\/WMQHTTP.war\/WEB-INF\/lib\/classes.jar:\n root root 156845 2013-09-25 18:02 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/installedApps\/aemtux1Cell01\/WMQHTTP_war.ear\/WMQHTTP.war\/WEB-INF\/lib\/classes.jar\n 3. Found 80 MQ classes in classes.jar in WMQHTTP.war in \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear:\n root root 145600 2014-07-16 13:57 \/opt\/IBM\/WebSphere\/AppServer\/profiles\/AppSrv01\/config\/cells\/aemtux1Cell01\/applications\/WMQHTTP_war.ear\/WMQHTTP_war.ear\n 4. Found com.ibm.mq.commonservices.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 5. Found com.ibm.mq.connector.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 6. Found com.ibm.mq.headers.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 \/wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 7. Found com.ibm.mq.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 8. Found com.ibm.mq.jmqi.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 9. Found com.ibm.mq.jmqi.local.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 10. Found com.ibm.mq.jmqi.remote.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 11. Found com.ibm.mq.jmqi.system.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 12. Found com.ibm.mq.jms.admin.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Common Client API\/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 13. Found com.ibm.mq.pcf.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 14. Found com.ibm.mqjms.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Title: JMS Client Common Facade\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 15. Found dhbcore.jar in \/opt\/IBM\/WebSphere\/AppServer\/lib\/WMQ\/ra\/wmq.jmsra.rar:\n root root 7885592 2012-10-15 12:56 wmq.jmsra.rar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n 16. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.jar:\n root root 1115668 2012-10-15 12:56 com.ibm.mq.jmqi.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 17. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.commonservices.jar:\n root root 728387 2012-10-15 12:56 com.ibm.mq.commonservices.jar\n Implementation-Title: WebSphere MQ Common Service\n Implementation-Version: ${version.number} - ${build.level}\n Implementation-Vendor: IBM Corporation\n 18. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.remote.jar:\n root root 546407 2012-10-15 12:56 com.ibm.mq.jmqi.remote.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 19. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jar:\n root root 448745 2012-10-15 12:56 com.ibm.mq.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 20. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jms.admin.jar:\n root root 358016 2012-10-15 12:56 com.ibm.mq.jms.admin.jar\n Implementation-Title: JMS Common Client API\/SPI\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 21. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mqjms.jar:\n root root 352254 Aug 01 11:49 com.ibm.mqjms.jar\n Implementation-Title: JMS Common Client facade\n Implementation-Version: 7.0.1.5 - k701-105-110419\n Implementation-Vendor: IBM Corporation\n 22. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.connector.jar:\n root root 339396 2012-10-15 12:56 com.ibm.mq.connector.jar\n Implementation-Title: WebSphere MQ J2EE Connector Architecture\n Implementation-Version: 7.1.0.0-k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 23. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.headers.jar:\n root root 338572 2012-10-15 12:56 com.ibm.mq.headers.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 24. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.local.jar:\n root root 224747 2012-10-15 12:56 com.ibm.mq.jmqi.local.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 25. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.jmqi.system.jar:\n root root 209738 2012-10-15 12:56 com.ibm.mq.jmqi.system.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 26. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/com.ibm.mq.pcf.jar:\n root root 125200 2012-10-15 12:56 com.ibm.mq.pcf.jar\n Implementation-Title: WebSphere MQ classes for Java\n Implementation-Version: 7.1.0.0 - k000-L111005.1\n Implementation-Vendor: IBM Corporation\n 27. Found \/opt\/IBM\/WebSphere\/AppServer\/installedConnectors\/wmq.jmsra.rar\/dhbcore.jar:\n root root 2011835 2012-10-15 12:56 dhbcore.jar\n Implementation-Version: \"DH610-GOLD\"\n Implementation-Title: \"Webscale Distribution Hub Core\"\n Implementation-Vendor: \"IBM Corporation\"\n mqjavalist.sh: 27 jar files with MQ code found in \/opt\/IBM\/WebSphere\/AppServer\n \n mqjavalist.sh: 27 total jar files with MQ code found\n mqjavalist.sh: Results saved to mqlist.txt\n \n \n \n 5. \n 6. Back to top\n\nRESOLVING THE PROBLEM\n\nReview the output from mqjavalist.sh to determine where copies of the MQ jar files have been found. Not all duplicates represent a problem, unless they are being loaded by your Java SE application or Java EE application server at runtime. If the com.ibm.mq.commonservices.jar file shows an implementation version of ${version.number} - ${build.level} just ignore it.\n\nIn the sample output above, entries #16 through #27 represent the jar files for the installed MQ Resource Adapter. They all show an implementation version of 7.1.0.0 - k000-L111005.1 except for #21, com.ibm.mqjms.jar, which shows an implementation version of 7.0.1.5 - k701-105-110419. Because the jar file versions are not in sync, MQ JMS will not function as expected.\n\nIn cases like this, the wmq.jmsra.rar file should contain a copy of the MQ jar at the right level for the application server. Entry #14 in the mqjavalist.sh output shows the com.ibm.mqjms.jar file with an implementation version of 7.1.0.0 - k000-L111005.1, which is what we need. Use the jar program to extract the com.ibm.mqjms.jar file from the wmq.jmsra.rar archive, then copy it over the back-level version of the jar. Use chown and chmod to ensure the permissions on the file are correct.\n\nIn other cases, you might find that the classpath for the application server, or for your Java SE application, is picking up extra copies of the MQ jar files. Eliminating unnecessary classpath entries can resolve the problem.\n\nIf your Java EE application (.ear or .war) bundles a copy of any MQ jar files, you should remove them and rely on the ones from the installed MQ Resource Adapter instead.\n\nBack to top\n\n\nAdditional Keywords: \ntroubleshoot troubleshooting trouble shoot classloader classpath configuration scripts\n\n\n\nDOWNLOAD\n 1. \n 2. mqjavalist.sh [\/support\/docview.wss?uid=swg21681142&aid=2]mqjavalist.sh\n\n\n\n\nDISCLAIMER: All source code and\/or binaries attached to this document are referred to here as \"the Program\". IBM is not providing program services of any kind for the Program. IBM is providing the Program on an \"AS IS\" basis without warranty of any kind. IBM WILL NOT BE LIABLE FOR ANY ACTUAL, DIRECT, SPECIAL, INCIDENTAL, OR INDIRECT DAMAGES OR FOR ANY ECONOMIC CONSEQUENTIAL DAMAGES (INCLUDING LOST PROFITS OR SAVINGS), EVEN IF IBM, OR ITS RESELLER, HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Back to top"}]},{"id":"TRAIN_Q484","question":"Stale \/ old content on one cluster node but content up-to-date on other nodes.Why?\n\nStale \/ old content on one cluster node but content up-to-date on other nodes. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q485","question":"Security Bulletin: XXE injection vulnerability in IBM API Connect (CVE-2017-1322)\n\nI need to understand details regarding Security Bulletin: XXE injection vulnerability in IBM API Connect (CVE-2017-1322). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q486","question":"Why Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?\n\nWhy Summarization and pruning are failing with SQL Error Code = -4220 on AIX_LPAR table?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q487","question":"Security Bulletin: API Connect Portal is affected by multiple Drupal vulnerabilities\n\nI need to understand details regarding Security Bulletin: API Connect Portal is affected by multiple Drupal vulnerabilities (CVE-2017-6924, CVE-2017-6923, CVE-2015-7875, CVE-2017-6925). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q488","question":"Does DB2 DBMS implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures?\n\n\n\nV-58159 - SV-72589r1_rule says \"The DBMS must implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures.\" \nDoes DB2 UDB version 8 implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures?","answer":"DB2 uses encryption modules which are FIPS 140-2 certified.","is_impossible":false,"contexts":[{"filename":"swg21237078.txt","text":"Title: IBM DB2 UDB Version 8, v10.5 compliance with FIPS 140-2 standard - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Is DB2 v8, v10.5 compliant to FIPS 140-2 ?. \n\nANSWER\n\nIs DB2 v10.5 compliant with FIPS 140-2?\n\nQ: Is DB2 vulnerable to the problem described below?\n\nV-58165 DBMS main in the middle attack [https:\/\/www.stigviewer.com\/stig\/database_security_requirements_guide\/2015-06-23\/finding\/V-58165]\n\n\"One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective. \"\n\nA: No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above. DB2 uses encryption modules which are FIPS 140-2 certified.\n\nDB2 v8.x compliancy to FIPS 140-2\n\nDB2 v8.x went out of support in April 2009.\n\nWhat is ICC?\n\nICC (IBM Crypto for C) is a set of libraries from Tivoli\u00ae for performing encryption. As of DB2\u00ae Universal Database\u2122 (DB2 UDB) Version 8 fixpak 7 (equivalent to DB2 UDB Version 8.2), DB2 is using ICC on most platforms.\n\nCustomers who need to operate in an environment that is compliant with FIPS 140-2 federal standard should take into account the releases of ICC that are shipped by DB2 on different platforms and the compliance status of those releases with FIPS 140.2.\n\nFollowing is a list of platforms on which DB2 is using ICC for encryption of data flowing between clients and servers:\n\nDB2 V8 Fixpak 7 through DB2 Fixpak 11: \nICC Version 1.2.2 on platforms:\nAIX 32 bit\nHP-UX PA-RISC 32 bit\nICC Version 1.2.1 on platforms: \nAIX 64 bit\nHP-UX PA-RISC 64 bit\nHP-UX IA64\nLinux x86, Linux x86-64, Linux IA64\nLinux for zSeries\nLinux for POWER\nWindows x86 and IA64\nSolaris SPARC 64 bit\nICC Version 1.3.9 on platforms:\nSolaris x86-64 (DB2 V8.2 GA)\n\nDB2 V8 Fixpak 12 and later: \nICC Version 1.4.1 on platforms \nAIX\nHP-UX PA-RISC\nLinux x86 and x86-64\nLinux for zSeries\nLinux for POWER\nWindows x86 and x86-64\nSolaris SPARC\nICC Version 1.3.9 on platforms \nHP-UX IA64\nLinux IA64\nWindows IA64\n\nSummary of known problems encountered in ICC 1.2.1\/1.2.2:\nThere are a number of issues with DB2 and the ICC encryption libraries at levels prior to 1.3.9. The known problems are: \n\n\n 1. Severe performance problems where processes seem to hang, or take several minutes to run. \n 2. A bug in ICC code causes it to communicate with the OpenSSL EGD (Entropy Gathering Daemon) which under certain circumstances could hang \n 3. ICC symbols have not been namespaced and DB2 can end up with symbol collisions with OpenSSL code. This can also happen when multiple versions of ICC are used within the same process.\n\n\nDB2 Version 8 Fixpak 12 and later incorporates IBM Crypto for C (ICC) version 1.3.9 or 1.4.1 cryptographic module which fixes these problems. \n\n \n\nNote: The latest status of ICC conformance with FIPS 140-2 standard can be obtained by referring to http:\/\/www.ibm.com\/security\/standards\/st_evaluations.shtml [http:\/\/www.ibm.com\/security\/standards\/st_evaluations.shtml]\n\nRELATED INFORMATION\n FIPS PUB 140-2 [http:\/\/csrc.nist.gov\/publications\/fips\/fips140-2\/fips1402.pdf]"}]},{"id":"TRAIN_Q489","question":"Recurrent RES StaleConnectionException\n\nHow to prevent rule execution failing because of recurrent StaleConnectionException on ODM 8.8 Rule Execution Server? ","answer":"Configure the WebSphere Application Server data source connection pool [http:\/\/publib.boulder.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException : \n\n * Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout \n * Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout","is_impossible":false,"contexts":[{"filename":"swg21496354.txt","text":"Title: IBM JRules or ODM module fails to access database with StaleConnectionException - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n JRules and ODM modules such as Rule Execution Server (RES) and Rule Team Server (RTS) \/ Decision Center (DC) may fail to access their data source with the following type of exception present in the log:\n\ncom.ibm.websphere.ce.cm.StaleConnectionException: Io exception: Connection timed out \n\nSYMPTOM\nThe problem may occur when a JRules or ODM module accesses its data source after a period of database access inactivity. For example: \n\n * The first user accessing a RTS \/ DC server that remained idle overnight experiences a failure upon logging and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred at that time. \n * After a RES server has been processing execution requests normally for some time, an attempt to deploy a ruleset update fails and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred upon an attempt to invalidate a ruleset or to retrieve its definition.\n\n\nCAUSE\nThe underlying network connection for a data source is no longer valid although the data source itself remains considered active from the WebSphere Application Server data source connection pool management perspective. An attempt by a JRules module to try and access its data base through one such data source connection provided by the Application Server may then fail. \nThe network connection of a data source may become invalid for a number of reasons, one typical example is that a firewall between the Application Server and the Database has a policy to discard network connections that remain idle for some time.\n\n\nENVIRONMENT\nThe exception com.ibm.websphere.ce.cm.StaleConnectionException is specific to WebSphere Application Server environments. But a similar issue can be experienced with Weblogic, see: Rule Execution Server on WebLogic unable to load ruleset after period of inactivity [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21615801]\n\n\n\nRESOLVING THE PROBLEM\nConfigure the WebSphere Application Server data source connection pool [http:\/\/publib.boulder.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException : \n\n * Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout \n * Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout\n\n\nThe document Troubleshooting stale connection problems [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21247168#SCETroubleshooting] provides further information. RELATED INFORMATION\n#RES unable to load ruleset after period of inactivity [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21615801]\nTroubleshooting stale connection problems [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21247168#SCETroubleshooting]\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 Enterprise"}]},{"id":"TRAIN_Q490","question":"TWS \/ DWC and WebSphere 8.5.5.4+\n\nWebSphere 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. ","answer":"You can solve this problem by configuring your TWS engines to use TLS instead of SSL :","is_impossible":false,"contexts":[{"filename":"swg21964202.txt","text":"Title: IBM How Connect TDWC 9.3 to TWS Engine lower level release - United States\n\nText:\ndwc 93; connect; SSL ; TLS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n DWC 9.3 users cannot connect to TWS Engine lower level releases (8.5.1 until 9.2) \n\nSYMPTOM\nUnable to connect to TWS 8.5.1 ,8.6 or 9.1\/9.2 from DWC 9.3. \n\nCheck the WAS SystemOut.log for error :\n\nSSL0080E: javax.net.ssl.SSLHandshakeException - The client and server could not negotiate the desired level of security. Reason: Server chose SSLv3, \nbut that protocol version is not enabled or not supported by the client. javax.net.ssl.SSLHandshakeException: Server chose SSLv3, but that protocol version is not enabled or not supported by the client.\n\n\nCAUSE\nDWC 9.3 is packaged with WAS 8.5.5.4 and due to known vulnerabilities has SSLV3 disabled. However TWS 9.2 and earlier versions use SSLv3 by default and so the DWC 9.3 cannot connect\n\n\nRESOLVING THE PROBLEM\nYou can solve this problem by configuring your TWS engines to use TLS instead of SSL :\n\n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/config\/cells\/TWSNodeCell\/security.xml \n\nFind sslProtocol and change \"SSL_TLS\" to \"TLS\" \n\nFind ssl.protocol and change value=\"SSL\" to value=\"TLS\" \n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/properties\/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nBackup and edit : \n\nTWA_HOME\/WAS\/TWSProfile\/temp\/ssl.client.props \n\nFind com.ibm.ssl.protocol=SSL and change to com.ibm.ssl.protocol=TLS \n\nStop and restart WAS. \n\n*Be aware that your Engines are now using TLS and so you must also reconfigure any DWC 9.2 or 9.1 installations that need to connect to those engines. You would change them to use TLS in the same way as above but also by the same changes in these copies of security.xml and ssl.client.props : \n\nTWA_HOME\/JazzSM\/profile\/config\/cells\/JazzSMNode01Cell\/security.xml \n\nTWA_HOME\/JazzSM\/profile\/properties\/ssl.client.props \n\nTWA_HOME\/JazzSM\/profile\/temp\/ssl.client.props \n\nPlease consider that since you configure with TLS the WAS of TWS Engine also the Dynamic Agent can be impacted. \n\nSee technote 1689332."}]},{"id":"TRAIN_Q491","question":"Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089)\n\nI need to understand details regarding Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089).","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q492","question":"Help with Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942)\n\nI need to understand details regarding Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942). Where can I find this information? ","answer":"CVEID: CVE-2015-4943 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4943]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)\nCVEID: CVE-2015-4941 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4941]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514] 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-4942 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4942]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)","is_impossible":false,"contexts":[{"filename":"swg21972012.txt","text":"Title: IBM Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A number of malformed MQTT client flows could be issued by a malicious user to cause the MQXR service to abend and require manual restart. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4943 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4943]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)\nCVEID: CVE-2015-4941 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4941]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514] 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-4942 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4942]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515] 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\nIBM WebSphere MQ 8.0 \n\n - IBM WebSphere MQ 8.0.0.3 and earlier maintenance levels \n\nIBM WebSphere MQ 7.5 \n\n - IBM WebSphere MQ 7.5.0.5 and earlier maintenance levels \n\nIBM WebSphere MQ 7.1 \n\n - IBM WebSphere MQ 7.1.0.6 and earlier maintenance levels\n\nREMEDIATION\/FIXES\nWebSphere MQ 8.0 \n\n - Apply fixpack 8.0.0.4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21969244] \n\nWebSphere MQ 7.5 \n\n - Apply interim ifix 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\nWebSphere MQ 7.1 \n\n - Apply fixpack 7.1.0.7 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21965293]\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\nReported to IBM by Codenomicon at http:\/\/www.codenomicon.com\/ [http:\/\/www.codenomicon.com\/] \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. \n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21977182]"}]},{"id":"TRAIN_Q493","question":"Help with Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server, which is shipped with, or a required product for, IBM Tivoli Network Manager IP Edition (CVE-2017-1741).\n\nI need to understand details regarding Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server, which is shipped with, or a required product for, IBM Tivoli Network Manager IP Edition (CVE-2017-1741) Where can I find this information? ","answer":"CVEID: CVE-2017-1741 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1741]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper handling of Administrative Console panel fields. When exploited an attacker could read files on the file system.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134931 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134931] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:L\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22012342.txt","text":"Title: IBM Security Bulletin: Information disclosure in WebSphere Application Server Admin Console (CVE-2017-1741) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential information disclosure in the WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1741 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1741]\nDESCRIPTION: IBM WebSphere Application Server could allow a remote attacker to obtain sensitive information caused by improper handling of Administrative Console panel fields. When exploited an attacker could read files on the file system.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134931 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134931] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\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 PI90042 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\u00b7 Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI90042 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044616] [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\u00b7 Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.13: \n\u00b7 Upgrade to minimal fix pack levels as required by interim fixes and then apply Interim Fix PI90042 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044616] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044445] \n--OR-- \n\u00b7 Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018). \n\nFor V8.0.0.0 through 8.0.0.14: \n\u00b7 Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI90042 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044616] [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\u00b7 Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n\u00b7 Upgrade to a minimal fix pack levels as required by interim fix and then apply Interim Fix PI90042 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044616] [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\u00b7 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 06 March 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. \n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22014402]"}]},{"id":"TRAIN_Q494","question":"Why do we observe the transaction rollback errors J2CA0024E and DSRA0080E with Oracle 12c and how can we fix it?\n\n\n\nWe are using BPM Advanced v8.5.6 in connection with the Oracle JDBC Driver 12.1.0.1.0. We observe many database transaction rollback exceptions:\n\n J2CA0024E: Method rollback, within transaction branch ID <null> of resource pool jdbc\/BPEDB, caught com.ibm.ws.exception.WsException: DSRA0080E: An exception was received by the Data Store Adapter. See original exception message: Could not rollback with auto-commit set on. with SQL State : 99999 SQL Code : 17274\n\nDue to the technote \"Advanced database support for IBM BPM Standard, IBM BPM Advanced, and IBM Business Monitor on distributed platforms\" this is a supported configuration.\n\nWhy do we observe these errors and how can we fix it?","answer":"To use Oracle 12c with IBM Business Monitor V8.5.5, a new JVM property must be defined. Add the following JVM property to the Monitor server JVM:\n\noracle.jdbc.autoCommitSpecCompliant=false","is_impossible":false,"contexts":[{"filename":"swg21690673.txt","text":"Title: IBM Upgrading default JDBC drivers to Oracle 12c requires the definition of an additional JVM property in IBM Business Monitor - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n In IBM Business Monitor V8.5.5, the Monitor server fails if the default JDBC driver included in the product is upgraded to an Oracle 12c JDBC driver. \n\nRESOLVING THE PROBLEM\nTo use Oracle 12c with IBM Business Monitor V8.5.5, a new JVM property must be defined. Add the following JVM property to the Monitor server JVM:\n\noracle.jdbc.autoCommitSpecCompliant=false"}]},{"id":"TRAIN_Q495","question":"Is there a way to separate the application logging from WebSphere Application Server logging?\n\n\n\nCurrently the WebSphere error logs as well as the application error logs are printed in same file. The same case with system out logs. Our goal is to separate the application system error and out logs from WebSphere system logs.\n\nIf we are use log4j in the application for separating the logs what is the best way to do this?","answer":"In WAS V8.5, we added the application name to log and trace records stored using HPEL (High Performance Extensible Logging). Since HPEL lets you format and filter your log content after it has been persisted to the HPEL log\/trace repository, this lets you decide if you want to see your application content on its own (helpful for uncluttered debug of an application), or together with the application server log\/trace content (helpful to see impact of server on applications, and vice versa).","is_impossible":false,"contexts":[{"filename":"swg21995397.txt","text":"Title: IBM Troubleshoot: Logging Problems in IBM WebSphere Application Server - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Trace analysis information for the logging component in the WebSphere\u00ae Application Server. \n\nSYMPTOM\nDoes not display.\n\n\nRESOLVING THE PROBLEM\n \n\nThis document contains troubleshooting information for logging problems in the WebSphere\u00ae Application Server. This can help address common issues with this component before calling IBM support and save you time.\n\nTAB NAVIGATION\n * \n * \n * Troubleshoot- selected tab,\n * \n * Collect data [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21321060]\n\nOverview \nYou will find common questions in this section that may help resolve your logging problems.\n\n1. How do I use JCL with WebSphere\u00ae Application Server?\n\nFor information on how to use JCL, see The Support Authority: Using Jakarta Commons Logging (JCL) with WebSphere Application Server [https:\/\/www.ibm.com\/developerworks\/websphere\/techjournal\/0901_supauth\/0901_supauth.html]\n\n2. What are IBM recommendations regarding SLF4J and Logback? \n\nIn general, we recommend that customers use JUL when possible\/practical (as mentioned in The Support Authority: A developer's guide to WebSphere Application Server logging [http:\/\/www.ibm.com\/developerworks\/websphere\/techjournal\/0802_supauth\/0802_supauth.html]). JUL provides a good, ubiquitous logging infrastructure, which is suitable for most applications, and integrates with WebSphere Application Server log and trace. Using JUL directly also avoids extra log\/trace API \"hops\" that are introduced by using other log\/trace frameworks that map to JUL. The WAS logs are generated using JUL Handlers connected to the root JUL Logger.\n\nIn case you don't want to use JUL, or you have code that is already instrumented with another logging package, SLF4J or Logback can be helpful. For example, you may have code already written with Log4J. Log4J log\/trace is not routed to WAS log\/trace files, and Log4J loggers don't show up in the WAS tree of loggers you can control from the admin console. Further, trace spec settings you make in WAS do not control Log4J logger settings. This is where SLF4J or Logback can come in handy, as you can use them to intercept Log4J calls and forward them to the logging implementation of your choice. In order to integrate well with WAS logs\/trace, we would recommend you bind your SLF4J\/Logback API to map your log\/trace content to JUL -- this will give you the ability to see your logs\/trace in the WAS log\/trace files, and enable you to have easy admin console control over all of your loggers.\n\n3. How can I get WAS logs to go to syslog or the Windows EventLog?\n\nThere are a number of places that users have asked to be able to direct logs to in the past. Most notably, a number of customers have asked for the ability to send logs to syslog.\n\nWebSphere Application Server sends all of its logs to java.util.logging (JUL), and customers can customize what happens to the log\/trace events by way of using JUL Handlers. Once content is sent to JUL, it can be handled in a variety of flexible ways:\n\n1) By default, we store the content in our log files, such as SystemOut.log, trace.log, or the newer log and trace repositories of the High Performance Extensible Logging framework we added in WebSphere Application Server V8.0. We also send the log content over JMX notifications, which allows for remote access.\n\n2) If customers want to send content to places like SMTP, syslog, event log, or a few other places, they can use SLF4J to route WAS logs to Log4J, and use the corresponding Log4J Appenders. In this configuration, WAS logging routes to java.util.logging, SLF4J's Handler routes the request to Log4J, and Log4J can be configured to write log records to a syslog Appender. \n\n3) If users want to do something even more custom, they can write their own JUL Handlers and plug them into WebSphere Application Server. \n\n4. I am unable to turn on WebSphere Application Server trace. The trace state sets to *=off?\n\nThe systemOut.log shows: \n\n\n\n[5\/26\/15 14:10:44:746 EDT] 000000d9 ManagerAdmin I TRAS0018I: The trace state has changed. The new trace state is *=off. \nThe problem is related to the below two JVM arguments: \n\n-Djava.util.logging.configureByLoggingPropertiesFile=TRUE\n-Djava.util.logging.config.file=<path>\/logging.properties \nVerify if the above 2 JVM arguments are configured. If yes, temporary disable it so WAS trace can be enabled. \n\n5. The WebSphere Application Server logging has stopped, what may have caused this? \n\nThe user might have disabled the trace by setting trace output to none. \n\nSetting runtime trace output to none impacts the JVM logs. To do that, the runtime trace spec will be set to *=off, which means to turn off all log levels. If customers just want to disable the trace for debug information only, we recommend setting the runtime trace spec, accordingly, instead of setting runtime trace output to none. For example, set to *=info, which is the default. \n\nVerify if the commons-logging.jar and commons-logging.properties exist in the JVM classpath. If yes, suggest to remove it and put them inside the application (with parent_last setting) or put them in the isolated shared library. \n\n6. How can I separate my logs into separate files for each application? \n\nIn WAS V8.5, we added the application name to log and trace records stored using HPEL (High Performance Extensible Logging). Since HPEL lets you format and filter your log content after it has been persisted to the HPEL log\/trace repository, this lets you decide if you want to see your application content on its own (helpful for uncluttered debug of an application), or together with the application server log\/trace content (helpful to see impact of server on applications, and vice versa). \n\nFor example, if you had 3 applications called app1, app2, and app3, you could create app specific logs as follows: WAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app1 > app1.log\nWAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app2 > app2.log\nWAS_INSTALL_ROOT\\bin> logViewer -includeExtensions appName=app3 > app3.log \nor see everything in one file as follows: \n\nWAS_INSTALL_ROOT\\bin> logViewer > all.log \n7. How can I add my own java.util.logging.Handler to WAS? \n\nTo create a Handler you need to extend the java.util.logging.Handler class as follows (this example also shows how to filter for only the most severe messages): \n\nimport java.util.logging.Handler;\nimport java.util.logging.Level;\nimport java.util.logging.LogRecord;\npublic class MyHandler extends Handler {\npublic void close() {\n}\npublic void flush() {\n}\npublic void publish(LogRecord record) {\nif (record.getLevel().intValue() >= Level.SEVERE.intValue()) {\n\/\/ do something...\n}\n}\n}\nIn your application you can add that Handler to the root logger as follows:\nimport java.util.logging.Handler;\nimport java.util.logging.Logger;\n...\nHandler myHandler = new MyHandler();\nLogger logger = Logger.getLogger(\"\");\nlogger.addHandler(myHandler);\n... \n8. Why can't I set my own log levels using the Logger setLevel method? \n\nThe application server can run in two modes. \n\nBy default, the logger levels are managed, and we expect any changes to logger levels to be done only through wsadmin or through the admin console. When the trace spec update is applied, we explicitly set each logger to the level specified in the trace spec -- we do not leave any named loggers at level set to null. So, while you can change a logger's level using the setLevel method, that change only lasts until you apply your next trace spec update from wsadmin or the admin console. Basically, changes you make via logger.setLevel are temporary at best, and do not apply automatically to children since the children won't have a null level. \n\nAlternately, you can have the server to be configured by the JRE's logging.properties file by setting the java.util.logging.configureByLoggingPropertiesFile property. In this mode, the application server will not touch the logger levels -- you cannot update the levels through the admin console, nor through wsadmin. See Java virtual machine custom properties [http:\/\/www14.software.ibm.com\/webapp\/wsbroker\/redirect?version=matt&product=was-base-dist&topic=xrun_jvm] for more information on this setting. In this mode, you can specify anything you would normally specify in your logging.properties file. Be careful not to use a console handler though, as that will lead to an infinite loop, since we take data sent to System.out, turn it into LogRecords, and send it to the root logger. \n9. How can I get java.util.logging to initialize from a jre\/bin\/logging.properties file in the application server? \n\nYou can do this via system property: java.util.logging.configureByLoggingPropertiesFile=true\n\nNote that if you do set up your server in this mode, we will not manage your logger levels via the admin console.\n\nNote also that we will ignore any console handler entries found in the logging.properties file, since we route System.out to the root logger, which would mean that a console handler would cause an infinite recursion. \n\nIf you do use this system property, and you want to change logger levels, you have two choices:\n\n\n * \n * 2) Set the Logger levels programatically using the Logger.setLevel method\n \n\n10. How can I get the full logger name from log and trace records? \n\nThe full logger name can be handy to know for enabling trace. How you get to it depends on what log and trace mode you use: \n\nBasic log and trace mode: \n\nThe basic log format (not to be confused with basic log and trace mode), which is the default format for SystemOut.log \/ SystemErr.log \/ trace.log has a truncated version of the logger name: \n\n[4\/14\/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857 \nThere is no way to get the full logger name from basic formatted logs. You need to switch to advanced format for your logs\/trace if you want to see the full logger name. Once in advanced format, log contents appear as follows: \n\n[4\/14\/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]\nhello fine 54857 \nHPEL log and trace mode: \n\nYou can use the HPEL LogViewer command line tool to output the log\/trace content in either basic or advanced format. \n\n> logviewer -format basic \n\n....\n[4\/14\/11 9:41:45:218 EDT] 00000021 QuickLogTest W hello fine 54857\n.... \n> logviewer -format advanced \n\n....\n[4\/14\/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4]\nhello fine 54857\n... \n11. How can I write HPEL content to a database? \n\nIf you want to write to a Database, any of the following options will work: \n\n1) Write your own log handler (that writes to a database) and plug it into JSR47. (see the Java doc for java.util.logging.Handler) \n\n2) Write an HPEL reading Java application to read the content from an HPEL log repository and write it to a database \n\n3) Write an HPEL reading Java application to read the content from an HPEL log repository and write it out in .csv format, then just use the common database commands to load the .csv content into the database. \n\n12. How do you tune HPEL for optimal performance in tWAS? \n\nIn the server.xml, jvmEntries element: \n- Ensure debugMode is set to false \n- Ensure RAS JMX notifications are disabled by including -Dcom.ibm.ejs.ras.disablerasnotifications=true in genericJvmArguments \n- Ensure -Xquickstart is not in the list of genericJvmArguments \n\n<jvmEntries xmi:id=\"JavaVirtualMachine_1183122130078\" verboseModeClass=\"false\" verboseModeGarbageCollection=\"false\" verboseModeJNI=\"false\" runHProf=\"false\" hprofArguments=\"\" debugMode=\"false\" debugArgs=\"-Dcom.ibm.ws.classloader.j9enabled=true -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=7777\" genericJvmArguments=\"-Dcom.ibm.ejs.ras.disablerasnotifications=true\"> \nIn hpelModel.xml: \n- Ensure textLog is disabled. \n\n<hpelTextLog xmi:id=\"HPELTextLog_1\" enabled=\"false\" dataDirectory=\"${SERVER_LOG_ROOT}\"\/> \n13. How can I tell who is writing to System.err \/ System.out ? \n\nAdd the following to your genericJvmArgument s : \n\n-Xtrace:print=mt,trigger=method{com\/ibm\/ejs\/ras\/System*.*,jstacktrace} \n14. How can I identify what code is writing to System.out.println? \n\nAdd the following to your genericJvmArguments and restart the server to see a stack trace for each call to System.out.println: \n\n-Xtrace:print=mt,trigger=method{java\/io\/PrintStream.println,jstacktrace} \nA snippet of the stack trace for a sample application, which calls System.out.println(), with the above JVM argument set, which identifies that the Hello.printHello (Hello.java:15) writes to System.out. \n\n03:41:01.245*0x3277900 mt.0 > java\/io\/PrintStream.println(Ljava\/lang\/String;)V Bytecode method, This = 7fffff49f98\n03:41:01.247 0x3277900 j9trc_aux.0 - jstacktrace:\n03:41:01.248 0x3277900 j9trc_aux.1 - [1] java.io.PrintStream.println (PrintStream.java:829)\n03:41:01.248 0x3277900 j9trc_aux.1 - [2] com.ibm.jvm.io.ConsolePrintStream.println (ConsolePrintStream.java:311)\n03:41:01.250 0x3277900 j9trc_aux.1 - [3] Hello.printHello (Hello.java:15)\n03:41:01.251 0x3277900 j9trc_aux.1 - [4] Hello.main (Hello.java:9)Hello World\n03:41:01.253 0x3277900 mt.6 < java\/io\/PrintStream.println(Ljava\/lang\/String;)V Bytecode method \n15. How can I see who called a particular method? \n\nAdd the following to your genericJvmArguments: \n\n-Xtrace:print=mt,trigger=method{java\/util\/logging\/Logger.setLevel,jstacktrace} \n16. What are the .owner files for in the log directory? \n\nThe server creates a .owner file for each of the log files. The file content indicates which cell\/node\/server is the rightful user of the similarly named log file. This is used as a sort of locking mechanism to make sure that users don't improperly configure their systems. If two or more servers are configured to use the same log directory and file name, we can detect it using the .owner file and we will print a warning in the log file. \n\nFor more information, see Java virtual machine (JVM) log settings [http:\/\/www14.software.ibm.com\/webapp\/wsbroker\/redirect?version=phil&product=was-nd-dist&topic=JVMLogs_description] \n\n17. How can I correlate information from thread stacks in the javacore with information in my SystemOut.log file? \n\nThere are a few ways to correlate content in WAS logs\/trace with content in javacore thread dumps: \n\nBest option, if you are using WebSphere Application Server 8.0 \/ 8.5: \n\nApplies to: \nWAS 8.0.0.4 and above running with Java 626 SR4 and above \nWAS 8.5.0.2 and above running with Java 7 SR3 and above or Java 626 SR4 and above \n\nIn recent releases, we have made it possible to have the thread id used in the WebSphere Application Server log\/trace match with the thread id used in javacores. In WAS 8.0.0.4 and above, you can use a system property to make the thread id in the logs\/trace match the Java thread id. In WAS 8.5.0.2 and above, the thread id used in the logs\/trace matches with the Java thread id by default. For more information, see PM60913: Introduce ability to use Java Thread ID in Logs instead of LogRecord Thread ID [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PM60913] and JVM log interpretation [http:\/\/www14.software.ibm.com\/webapp\/wsbroker\/redirect?version=phil&product=was-nd-dist&topic=rtrb_readmsglogs] \n\nAnother option if you are using High Performance Extensible Logging (HPEL) \/ Binary Logging: \n\nApplies to: \nFull profile WAS 8.0.0.0 and above \nLiberty profile WAS 8.5.5.0 and above \n\nFull Profile: \nUse the HPEL logViewer command to output the logs in advanced format so you can see the full thread name: \n> logViewer -format advanced (basic is the default format) \n\nLiberty Profile: \nUse the binaryLog command line tool to output the logs in advanced format so you can see the full thread name: \n> binaryLog view --format=advanced \n\nYou will get output that looks like the following: \n\n[4\/14\/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4] \nThe javacore contains the same thread name: \n\n3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java\/lang\/Thread:0x02517CE0, state:R, prio=5\n3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)\n3XMTHREADINFO3 Java callstack:\n4XESTACKTRACE at com\/ibm\/io\/async\/AsyncLibrary.aio_getioev2(Native Method) \nAnother option if you are using Advanced format for your SystemOut.log \/ trace.log: \n\nApplies to: \nAll currently supported WebSphere Application Server releases. \n\nChange your log\/trace format to Advanced. The Advanced format contains the full thread name, as does the javacore. \n\nAdvanced format Log: \n\n[4\/14\/11 9:41:45:218 EDT] 00000021 W UOW= source=com.ibm.somelogger.QuickLogTest org= prod= component= thread=[WebContainer : 4] \nThe javacore contains the same thread name: \n\n3XMTHREADINFO \"WebContainer : 4\" J9VMThread:0x1578D700, j9thread_t:0x150D0D04, java\/lang\/Thread:0x02517CE0, state:R, prio=5\n3XMTHREADINFO1 (native thread ID:0x15B0, native priority:0x5, native policy:UNKNOWN)\n3XMTHREADINFO3 Java callstack:\n4XESTACKTRACE at com\/ibm\/io\/async\/AsyncLibrary.aio_getioev2(Native Method) \nWhat to do next \nIf the preceding troubleshooting did not help solve your problem, see the Mustgather [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21321060]for logging problems to continue investigation."}]},{"id":"TRAIN_Q496","question":"Why am I getting an SSL Key Exception (RSA premaster secret error) when trying to create a syndication pair?\n\n\n\nWhen trying to create the syndication pair for a virtual portal, I am getting the following exception:\n\n\"IWKWC0016E: The remote service can not be retrieved. Either the URL you entered is incorrect, the server you indicated does not contain IBM Web Content Manager or the web service has been incorrectly configured and could not be located. Check the log for more details https:\/\/1.23.456.789 <-- your ip address or hostname will be shown here\n\n\/wps\/wcm\/vpname\/basicauth\/SyndicationServlet?reqlocale=en_US& javax.net.ssl.SSLKeyException: RSA premaster secret error\"","answer":"The default restricted policy file has a 2048 key size limit. If the RSA key size exceeds this limit then this error is expected.","is_impossible":false,"contexts":[{"filename":"swg21663373.txt","text":"Title: IBM SSLKeyException: RSA premaster secret error Caused by InvalidKeyException - United States\n\nText:\nJDBC JCC SSL SSLKeyException .InvalidKeyException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n My java application using the Data Server Driver for JDBC (JCC) is failing to establish SSL connection with following error:\n\nSSLKeyException: RSA premaster secret error. Caused by: java.security.InvalidKeyException: Illegal key size or default parameters. \n\nSYMPTOM\njavax.net.ssl.SSLKeyException: RSA premaster secret error. Caused by: java.security.InvalidKeyException: Illegal key size or default parameters \n\n\nCAUSE\nThe default restricted policy file has a 2048 key size limit. If the RSA key size exceeds this limit then this error is expected.\n\nRESOLVING THE PROBLEM\nThis issue can be resolved by upgrading to the unrestricted policy files, replacing the security policy files with the IBM unlimited cryptography files. Replace the local_policy.jar with the Unrestricted JCE policy File. [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/reg\/pick.do?source=jcesdk&lang=en_US]"}]},{"id":"TRAIN_Q497","question":"Login to DASH returned \"Page cannot be displayed\" error\n\nLogin to DASH returned \"Page cannot be displayed\" error","answer":"Run the log collector program:\n\n\n 1. Change the directory to <JazzSM Home>\/ui\/bin \n 2. Run the following command:\n \n .\/consoleLogCollector.sh or .bat\n \n Send us the console_logs.zip file located in <JazzSM Home>\/ui directory\n\n\nand attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. Please also provide the DASH version info:\n<JazzSM Home>\/ui\/bin\/consolecli.sh Version\n\nUpload the resulting output file to the PMR","is_impossible":false,"contexts":[{"filename":"swg21632844.txt","text":"Title: IBM Enabling tracing for the DASH service in Jazz for Service Management - United States\n\nText:\nDASHL2; DASHL2FAQ; DASHL2MUSTG; enable tracing TECHNOTE (FAQ)\n\nQUESTION\n What is the procedure to enable trace logging to troubleshoot DASH runtime issues\/errors? \n\nCAUSE\nYou can use trace logging to assist in monitoring system performance and diagnosing problems. Since trace logs can be quite verbose and include many unrelated errors, resetting the logs and then reproducing the problem issue can reduce the time required for log analysis for specific issues.\n\nANSWER\nSteps to enable tracing: \n\n\nEnable trace logging. \n\n 1. Log into the DASH. After logging in navigate to Console Settings [\/support\/docview.wss?uid=swg21632844&aid=1] > Websphere Administrative Console. \n 2. Navigate to Troubleshooting -> Logs & Trace \n 3. Click on the Server1 -> Select Diagnostic Trace Service. Increase the Maximum Number of Historical Files from 1 to 10. \n 4. Click Apply, then select Change Log Detail Levels. \n 5. Click on Runtime tab to enable tracing for the DASH process that is currently running. Enabling tracing from the Runtime tab will keep tracing active until the next time the DASH server process is stopped. To make tracing persistent even after stopping and restarting the DASH server process click the Configuration tab instead. \n 6. Clear the trace string in the Groups box and replace it with the following:\n \n *=info: com.ibm.isc.*=all: com.ibm.isclite.*=all: com.ibm.iscportal.*=all: com.ibm.isclite.service.datastore.consoleproperties.*=INFO\n \n For the Connection manager (data provider related issues) you will want to enable all for the following components:\n \n *=info: com.ibm.isclite.rest.*=all:com.ibm.tivoli.conmgr.*=all \n 7. Click on the Apply button. \n 8. If you enabled tracing from the Configuration tab in step 4, then click the \"Save\" link that appears at the top of the page. (\"Save to master configuration\")\n\n\nOnce tracing is enabled, reproduce the DASH runtime issue. Note the time that the issue was reproduced so that the issue can be easily correlated with the trace log entries. \n\nRun the log collector program:\n\n\n 1. Change the directory to <JazzSM Home>\/ui\/bin \n 2. Run the following command:\n \n .\/consoleLogCollector.sh or .bat\n \n Send us the console_logs.zip file located in <JazzSM Home>\/ui directory\n\n\nand attach them to the associated Problem Management Record (PMR). Please include the time the issue was reproduced in the PMR update. Please also provide the DASH version info:\n<JazzSM Home>\/ui\/bin\/consolecli.sh Version\n\nUpload the resulting output file to the PMR"}]},{"id":"TRAIN_Q498","question":"How do I reduce the amount of CPU being consumed by Just In Time (JIT) compilation?\n\nMy Portal system is experiencing period bursts of high CPU. After reviewing some data, I've determined the primarily culprit behind these CPU bursts are Just In Time (JIT) compilation threads, similar to the following:\n\n 3XMTHREADINFO \"JIT Compilation Thread-0\" \n J9VMThread:0x0000000040004F00, j9thread_t:0x0000010010122040, \n java\/lang\/Thread:0x00000007011CAA58, state:CW, prio=10 \n 3XMJAVALTHREAD (java\/lang\/Thread getId:0x4, isDaemon:true) \n 3XMTHREADINFO1 (native thread ID:0x39100EF, native priority:0xB, native policy:UNKNOWN) \nWhy is this happening and how can I reduce the amount of CPU that JIT is using?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q499","question":"Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804)\n\nI need to understand details regarding Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804). Where can I find this information?","answer":"CVEID:CVE-2017-8804 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-8804]\nDESCRIPTION:glibc is vulnerable to a denial of service, caused by improper handling of buffer deserialization in the xdr_bytes and xdr_string functions. By sending a specially-crafted UDP packet, a remote attacker could exploit this vulnerability to cause virtual memory allocation, or memory consumption on the system.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125760 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125760]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:H)","is_impossible":false,"contexts":[{"filename":"swg22009796.txt","text":"Title: IBM Security Bulletin: IBM MQ Appliance is affected by a GNU C library (glibc) vulnerability (CVE-2017-8804) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM MQ Appliance has addressed a vulnerability in GNU C library (glibc). \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-8804 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-8804]\nDESCRIPTION:glibc is vulnerable to a denial of service, caused by improper handling of buffer deserialization in the xdr_bytes and xdr_string functions. By sending a specially-crafted UDP packet, a remote attacker could exploit this vulnerability to cause virtual memory allocation, or memory consumption on the system.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125760 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125760]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: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 04 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."}]},{"id":"TRAIN_Q500","question":"Where is latest information on fix packs for Cast Iron?\n\nWhere can I find more information on the fix packs and downloads available for the various releases of Cast Iron? ","answer":"Following are links to more information about the latest fix packs available on Fix Central for these versions:","is_impossible":false,"contexts":[{"filename":"swg21631488.txt","text":"Title: IBM WebSphere Cast Iron Cloud integration fix packs are available - United States\n\nText:\n NEWS\n\nABSTRACT\n Fix packs for WebSphere Cast Iron Cloud integration are now available for download. \n\nCONTENT\nFollowing are links to more information about the latest fix packs available on Fix Central for these versions: \n\n * 7.5.2.0 (App Connect Professional). See this forum Q&A [https:\/\/developer.ibm.com\/answers\/questions\/303457\/what-is-ibm-app-connect-professional\/] for more information. And see App Connect Professional builds and iFix details. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21998280] \n * 7.5.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21972013] \n * 7.5.0.0 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21963355] \n * 7.0.0.2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21686987] \n * 7.0.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21678176] \n * 7.0.0.0 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21656428] \n * 6.4.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21647655] \n * 6.4.0.0 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21641628] \n * 6.3.0.2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21650993] \n * 6.3.0.1 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21625115] \n * 6.3.0.0 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21619941]"}]},{"id":"TRAIN_Q501","question":"Is there a way to force the Tivoli Integrated Portal (TIP) fix pack installer to use a different temp location?\n\nIs there a way to force the Tivoli Integrated Portal (TIP) fix pack installer to use a different temp location? ","answer":"There is no option available to override \/tmp.","is_impossible":false,"contexts":[{"filename":"swg21655808.txt","text":"Title: IBM Specifying an alternative to \"\/tmp\" for Tivoli Integrated Portal installs - United States\n\nText:\nTIPL2; TIPL2INST; tmp; temp directory; folder; Tivoli Integrated Portal; installation; fix pack TECHNOTE (FAQ)\n\nQUESTION\n Is there a way to configure the TIP installer to use an alternate directory if the installation user ID has insufficient access rights to \"\/tmp\"? \n\nANSWER\nTIP L3 has examined the TIP installer and found that \/tmp is hard coded in both the TIP and Websphere installers. There is no option available to override \/tmp. To pursue a change to the TIP installer to accommodate an alternate tmp location, please submit an enhancement request via the RFE site here:\n\nhttp:\/\/www.ibm.com\/developerworks\/rfe\/?BRAND_ID=90 [http:\/\/www.ibm.com\/developerworks\/rfe\/?BRAND_ID=90]"}]},{"id":"TRAIN_Q502","question":"Wy can we not insert a table in ckeditor after upgrading Portal 8.5 to CF06?\n\nWe are using the default rich text ckeditor in Portal WCM 8.5. Since upgrading to Portal 8.5 CF04 we are however unable to insert HTML tables using the menu option, \"Insert Table\". \r\n\r\nAfter setting values and clicking OK we get following error:\r\n Uncaught TypeError: Cannot read property 'undefined' of undefined getValue \r\n @ full.js:2CKEDITOR.dialog.validate.regex \r\n @ ckeditor.js:570l @ table.js?t=E9ND:5(anonymous function) \r\n @ ckeditor.js:528CKEDITOR.dialog.A \r\n @ ckeditor.js:528(anonymous function) \r\n @ ckeditor.js:528d @ ckeditor.js:43CKEDITOR.event.CKEDITOR.event.fire \r\n @ ckeditor.js:44CKEDITOR.tools.extend.okButton.CKEDITOR.tools.extend.onClick\r\n @ ckeditor.js:549(anonymous function) @ ckeditor.js:492d \r\n @ ckeditor.js:43CKEDITOR.event.CKEDITOR.event.fire \r\n @ ckeditor.js:44CKEDITOR.ui.dialog.button.CKEDITOR.tools.extend.click \r\n @ ckeditor.js:491(anonymous function) \r\n @ ckeditor.js:483d @ ckeditor.js:43CKEDITOR.event.CKEDITOR.event.fire ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q503","question":"Can I remove the write permissions for \"other\" in ..\/ibm\/common\/acsi?\n\nCan I remove \"write\" permission for \"other\" for all the sub-directories and files under the following directory,\n\n \/usr\/ibm\/common\/acsi \n \/var\/ibm\/common\/acsi \n\nWill it cause any problem? ","answer":"Remove world writable permissions from DE directories. This will not impact functionality.","is_impossible":false,"contexts":[{"filename":"swg21512729.txt","text":"Title: IBM Can we remove world-writable permissions - global write permission - United States\n\nText:\nWorld writeable TECHNOTE (FAQ)\n\nQUESTION\n Setup a recurring process to remove world-writable from the files and directories: chmod o-w. We are not planning to delete any files. Would this impact functionality ? \n\nANSWER\nThe question is whether or not it is safe to remove world-writable for these files and directories. Some of them are dynamic and will be re-created with world-writable after reboot. For these we would like to remove world-writable on a recurring basis. \n\n\/export\/opt\/IBM\/tivoli\/tip\/derby\/TTSS Directory-Only \/export\/opt\/IBM\/tivoli\/tip\/derby\/TTSS\/log Directory-Only \/export\/opt\/IBM\/tivoli\/tip\/derby\/TTSS\/seg0 Directory-Only \/opt\/tivoli\/cit\/bin\/etc Directory-Only \/opt\/tivoli\/cit\/bin\/etc\/wscanhw Directory-Only \/opt\/tivoli\/cit\/cache_data Directory-Only \/tmp\/javasharedresources Directory-Only \/usr\/ibm\/common\/acsi\/logs Directory-Only \/usr\/ibm\/tivoli\/common\/CIT\/logs Directory-Only \/var\/.com.zerog.registry.xml File \/var\/ibm\/common\/acsi\/resourceBundleLocation Directory-Only \/usr\/ibm\/common\/acsi\/repos\/persistSVCRepos Directory-Only \/usr\/ibm\/common\/acsi\/repos\/persistSVCRepos\/* File \/usr\/ibm\/tivoli Directory-Only \/usr\/ibm\/tivoli\/common Directory-Only \/usr\/ibm\/tivoli\/common\/CIT Directory-Only \nAnswer: \n\nDB2 is OK confirmed by DB2 support \n# Revoke world-writable from recurring DB2 log files \n\/bin\/chmod o-w \n\/export\/opt\/IBM\/home\/tklmdb2\/sqllib\/db2dump\/stmmlog\/stmm.*.log \n\/bin\/chmod o-w \n\/opt\/IBM\/home\/tklmdb2\/tklmdb2\/NODE0000\/TKLMDB\/.SQLCRT.FLG \n\/bin\/chmod o-w \n\/opt\/IBM\/home\/tklmdb2\/tklmdb2\/NODE0000\/TKLMDB\/*\/.SQLCRT.FLG \n\nTested removing world-writable permissions on DB2 and it is OK. \n\nNone of these files are TKLM specific. \n\nSome of these directories do not belong to TIP. \n\nCIT Files TKLM V2 doesn't have them: \n\/opt\/tivoli\/cit\/bin\/etc Directory-Only \n\/opt\/tivoli\/cit\/bin\/etc\/wscanhw Directory-Only \n\/opt\/tivoli\/cit\/cache_data Directory-Only \n\/usr\/ibm\/tivoli Directory-Only \n\/usr\/ibm\/tivoli\/common Directory-Only \n\/usr\/ibm\/tivoli\/common\/CIT Directory-Only \n\/usr\/ibm\/tivoli\/common\/CIT\/logs Directory-Only \n\nChanged the permissions on those files. Everything looked OK: create a master keystore. create an LTO device. create a key, backup and restore, and apply a fixpack. \n\nNon-DE \n\/tmp\/javasharedresources Directory-Only \n\/var\/.com.zerog.registry.xml File Can be deleted \nDE related files \n\/usr\/ibm\/common\/acsi\/logs Directory-Only \n\/var\/ibm\/common\/acsi\/resourceBundleLocation Directory-Only \n\/usr\/ibm\/common\/acsi\/repos\/persistSVCRepos Directory-Only \n\/usr\/ibm\/common\/acsi\/repos\/persistSVCRepos\/* File \n** Remove world writable permissions from DE directories. This will not impact functionality. \n\nIt is OK to change the global write permission on above directories and files."}]},{"id":"TRAIN_Q504","question":"OMNIBUS nco_p_mttrapd : Malformed traps\n\nHow can you determine why the MTTrapd [SNMP] probe drops traps? ","answer":"Traps can be dropped during high loading, so ensure that the traps are being dropped from specific devices under normal load. \n\nUse snoop, tcpdump or Wireshark to capture the traps that are being dropped on the probe servers port, as defined in the property file.","is_impossible":false,"contexts":[{"filename":"swg21468340.txt","text":"Title: IBM MTTrapd [SNMP] probe drops traps from specific devices - United States\n\nText:\nnco_p_mttrapd; snmp; snmp traps; traps; dropped; drop; dropping; malformed; TCP TECHNOTE (FAQ)\n\nQUESTION\n MMTrapd probe : Why are SNMP traps dropped from specific devices? \n\nCAUSE\nSNMP packets can be dropped for a number of reasons, including overloading, malformed packets, malformed traps\/informs and incorrectly configured\/non-compliant MIBS.\n\nANSWER\nTraps can be dropped during high loading, so ensure that the traps are being dropped from specific devices under normal load. \n\nUse snoop, tcpdump or Wireshark to capture the traps that are being dropped on the probe servers port, as defined in the property file. \n\ne.g.\nPort : 162\n\n\nLoad the PCAP file into the Wireshark GUI and review the trap[s] visually. \n\n\nFor traps to be processed they must have enterprise-oid and uptime, otherwise they will be dropped during probe processing by the NET-SNMP libraries.\n\nTry setting Protocol to 'ALL' in case the trap is being sent as TCP|UDP.\n\nFor SNMPv3 trap and inform processing please refer to the available online FAQ's and supplementary documentation [see related information].\n\nSNMPv3 traps require a unique creatruser entry for each device in the mttrapd.conf file, with the user definition including the devices unique engined-id. Whilst SNMPv3 INFORMs can be sent without an engine-id and a single createuser entry in the ConfPath's mttrapd.conf file.\n\nIf the trap appears to be RFC compliant, and MTTrapd probe is correctly configured, please send the PCAP file of the trap along with the probes debug log and property file to IBM Tivoli Netcool support for further analysis.\n\nIMPORTANT: You should ensure that the latest MTTrapd probe and Netcool\/OMNIbus fix pack is installed before contacting IBM Tivoli Netcool support, and that the problem persists with the latest product.\n\nRELATED INFORMATION\n#Capturing TCP data [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21569745]\nSupport's Guide to the SNMP [MTTrapd] probe [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21607690]\nSNMPv3 trap reception [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21626348]"}]},{"id":"TRAIN_Q505","question":"How do I transfer my SPSS 24 license key to a new computer?\n\nI need to transfer my SPSS 24 license key to a new computer. I was able to download IBM\u00ae SPSS\u00ae 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.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"TRAIN_Q506","question":"Help with Security Bulletin: Vulnerability identified in IBM WebSphere Application Server shipped with IBM WSRR (CVE-2017-1743)\n\nI need to understand details regarding Security Bulletin: Vulnerability identified in IBM WebSphere Application Server shipped with IBM WebSphere Service Registry and Repository (CVE-2017-1743). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q507","question":"Why are the users unable to login to Web GUI 8.1 after I modify timeout to 2147483647 in security.xml file ?\n\n\n\nI followed the Web GUI 8.1 reference guide here to switching off the session timeout\n\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSSHTQ_8.1.0\/com.ibm.netcool_OMNIbus.doc_8.1.0\/webtop\/wip\/task\/web_adm_settimeout.html\n\nAfter I edited \/config\/cells\/JazzSMNode01Cell\/security.xml file, modified timeout setting to 2147483647, users are not able to login anymore.","answer":"1. On DASH server, navigate to <JazzSM Home>\/profile\/config\/cells\/JazzSMNode01Cell\/applications\/isc.ear\/deployments\/isc\/isclite.war\/WEB-INF \n\n \n2. Take a backup of consoleProperties.xml \n\n \n3. Open consoleProperties.xml in edit-mode. \n\n \n4. Search for \"LTPAFIX\" and change the value from \"true\" to \"false\". \n\n\nExample: \n\nBefore \n===== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"true\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\nAfter \n==== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"false\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\n5. Save the file. \n\n \n6. Restart DASH server.","is_impossible":false,"contexts":[{"filename":"swg21690658.txt","text":"Title: IBM Setting a big session time-out value in DASH causes session lock-out - United States\n\nText:\nDASHL2; session; time-out; timeout; cannot login; locked out ; 2147483647; security.xml TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Using a big value (2147483647) for the session timeout setting in DASH, to achieve the maximum time between timeouts, is causing users to be locked out completely. \n\nSYMPTOM\nAfter entering the user ID and password in the login page, and then pressing the \"continue\" button,\nthe login page does not change, stuck at \"processing\" and then returns to the login page again.\" \n\nAll users get essentially locked out completely from DASH sessions.\n\n\nCAUSE\nIn order to maximize the time between session timeouts, the customer is setting the timeout parameter in the security.xml file to 2147483647.\n\nThis timeout parameter used in the security.xml file is a WAS setting, but DASH is using a javascript call (settimeout), which causes a condition that prevents a login, if the timeout value is really big. \n\n\nNote: 2147483647 is the maximum positive value for a 32-bit signed binary integer in computing.\n\n\nRESOLVING THE PROBLEM\nThis condition that prevents logins can be averted by setting the custom property LTPAFIX in the consoleProperties.xml to \"false\". \n\n\nPlease follow this steps: \n\n1. On DASH server, navigate to <JazzSM Home>\/profile\/config\/cells\/JazzSMNode01Cell\/applications\/isc.ear\/deployments\/isc\/isclite.war\/WEB-INF \n\n \n2. Take a backup of consoleProperties.xml \n\n \n3. Open consoleProperties.xml in edit-mode. \n\n \n4. Search for \"LTPAFIX\" and change the value from \"true\" to \"false\". \n\n\nExample: \n\nBefore \n===== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"true\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\nAfter \n==== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"false\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\n5. Save the file. \n\n \n6. Restart DASH server."}]},{"id":"TRAIN_Q508","question":"BPM v8012 is compatible with oracle 12c or 11.2.0.4?\n\nDoes anyone know if BPM v8012 is compatible with Oracle 12c or 11.2.0.4? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q509","question":"How do I resolve this error Cannot load module librfccm.o, when trying to start the SAP monitoring agent?\n\nThe ITCAM SAP agent won't start, I'm getting this errorDependent module librfccm.o could not be loaded. 0509-022 Cannot load module librfccm.o.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q510","question":"Support of RHEL 5.8 and Liberty 8.5.5.5 with JAVA 8.0\n\nWe are running RHEL 5.8 and 5.11 with Liberty 8.5.5.5 and want to run JAVA 8.0 . Is it Supported ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q511","question":"Security Bulletin: Vulnerabilities in SSL affect IBM DataPower Gateways (CVE-2015-0289)\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in SSL affect IBM DataPower Gateways (CVE-2015-0289). Where can I find this information? ","answer":"CVEID: CVE-2015-0289 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101669 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101669] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)","is_impossible":false,"contexts":[{"filename":"swg21902172.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in SSL affect IBM DataPower Gateways (CVE-2015-0287, CVE-2015-0289, CVE-2015-0292, and CVE-2015-0293) - United States\n\nText:\ndatapower; CVE-2015-0287; CVE-2015-0289; CVE-2015-0292; CVE-2015-0293 SECURITY BULLETIN\n\nSUMMARY\n OpenSSL vulnerabilities were disclosed on March 19, 2015 by the OpenSSL Project. IBM DataPower Gateway has addressed the corresponding applicable CVEs. \n\n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0287 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0287]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by an error related to the reuse of a structure in ASN.1 parsing. An attacker could exploit this vulnerability using an invalid write to corrupt memory and execute arbitrary code on the system.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101668 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101668] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:P\/I:P\/A:P) \n\nCVEID: CVE-2015-0289 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0289]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service, caused by the failure to properly handle missing outer ContentInfo by the PKCS#7 parsing code. An attacker could exploit this vulnerability using a malformed ASN.1-encoded PKCS#7 blob to trigger a NULL pointer dereference.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101669 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101669] 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-0292 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0292]\nDESCRIPTION: OpenSSL could allow a remote attacker to execute arbitrary code on the system, caused by an error when processing base64 encoded data. An attacker could exploit this vulnerability using specially-crafted base 64 data to corrupt memory and execute arbitrary code on the system and cause a denial of service.\nCVSS Base Score: 7.5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101670 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101670] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:P\/I:P\/A:P) \n\nCVEID: CVE-2015-0293 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0293]\nDESCRIPTION: OpenSSL is vulnerable to a denial of service. By sending a specially-crafted SSLv2 CLIENT-MASTER-KEY message, a remote attacker could exploit this vulnerability to trigger an assertion.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101671 [https:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/101671] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P) \n\n\nNote that the following vulnerabilities disclosed on the same day do not impact DataPower appliances:\nCVEID: CVE-2015-0291 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0291]\nCVEID: CVE-2015-0207 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0207]\nCVEID: CVE-2015-0208 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0208]\nCVEID: CVE-2015-0209 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0209]\nCVEID: CVE-2015-0285 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0285]\nCVEID: CVE-2015-0286 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0286]\nCVEID: CVE-2015-0288 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0288]\nCVEID: CVE-2015-0290 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0290]\nCVEID: CVE-2015-1787 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1787]\n\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM DataPower Gateway appliances all versions through 6.0.0.13, 6.0.1.9, 7.0.0.6, and 7.1.0.4\n\nREMEDIATION\/FIXES\nFix is available in versions 6.0.0.14, 6.0.1.10, 7.0.0.7. Refer to APAR IT07854 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IT07854] for [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IT03868] URLs to download the fix.\n\nThis bulletin will be updated when a fix is made available for DataPower 7.1.x version. \n\nFor customers on DataPower 5.x versions, IBM recommends upgrading to a fixed, supported version of the product\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] OpenSSL Project vulnerability website [http:\/\/www.openssl.org\/news\/vulnerabilities.html] OpenSSL Advisory on above listed CVEs [https:\/\/www.openssl.org\/news\/secadv_20150319.txt]\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] ACKNOWLEDGEMENT\nNone \n\nCHANGE HISTORY\n 15 May 2015: Updated status on 7.1.x\n30 April 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."}]},{"id":"TRAIN_Q512","question":"Installing RAA plugin in RDz\n\n Hi,\n\nI'm trying to install the RAA plugin in RDz.\n\nBut the installation manager mentions that it is not compatibble with an other package, in casu the IBM CICS Explorer SDK. But I would like to install both, is this not possible? ","answer":"Follow the steps below to install RAAi:\n\n\n 1. Find the jar files by opening the RAAiInstallRepository.zip file and looking in thepluginsfolder for these two files: * com.ibm.dmh.raai_*.jar \n * com.ibm.raa.integrate.doc_*.jar\n \n \n \n \n 2. Find thedropinssubdirectory. 1. Right click on the properties to find the shortcut used to start RDz. \n 2. Look at theTargetproperty to see where eclipse.exe resides\n For example: C:\\Program Files\\IBM\\SDP\n \n \n \n \n 3. Create a dropinssubdirectory if one does not exist. \n \n \n 4. Copy the two jar files above to thedropinssubdirectory. \n \n \n 5. Restart RDz (Run as administrator)\n \n \n 6. Verify you have an Asset Analyzerentry in the left pane after RDz restarts by clicking on Window > Preferencesfrom the menu.","is_impossible":false,"contexts":[{"filename":"swg21651101.txt","text":"Title: IBM Installing Rational Asset Analyzer Plug-in on Rational Developer for z\/OS results in error CRIMA1071E - United States\n\nText:\nRAA; RAAi; Rdz; CRIMA1071E; 41580 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to install IBM Rational Asset Analyzer (RAA) Plug-in (RAAi) for IBM Rational Developer for System z (RDz) results in the error CRIMA1071E. \n\nSYMPTOM\nYou may receive a message similar to the following when installing RAAi in a RDz V9.0 environment: \n\nIBM Rational\u00ae Asset Analyzer Plug-in for IBM Rational Developer for System z\u00ae 6.1.0.0 cannot be installed into any package group.\n\nCRIMA1071E: The installation package 'IBM Rational\u00ae Asset Analyzer Plug-in for IBM Rational Developer for System z\u00ae' requires components supplied by other packages.\nThe required components might be supplied by the following installation packages:\nPackage: Rational\u00ae Developer for System z 7.6\n\n\nCAUSE\nThe RAAi installation program does not yet support RDz 9.0.\n\n\nRESOLVING THE PROBLEM\nInstall RAAi 6.1 into RDz 9.0 by manually copying the plug-in jar files to the Eclipsedropinsfolder. \n\n\nFollow the steps below to install RAAi:\n\n\n 1. Find the jar files by opening the RAAiInstallRepository.zip file and looking in thepluginsfolder for these two files: * com.ibm.dmh.raai_*.jar \n * com.ibm.raa.integrate.doc_*.jar\n \n \n \n \n 2. Find thedropinssubdirectory. 1. Right click on the properties to find the shortcut used to start RDz. \n 2. Look at theTargetproperty to see where eclipse.exe resides\n For example: C:\\Program Files\\IBM\\SDP\n \n \n \n \n 3. Create a dropinssubdirectory if one does not exist. \n \n \n 4. Copy the two jar files above to thedropinssubdirectory. \n \n \n 5. Restart RDz (Run as administrator)\n \n \n 6. Verify you have an Asset Analyzerentry in the left pane after RDz restarts by clicking on Window > Preferencesfrom the menu.\n\n\nIf you later wish to delete this copy of RAAi 6.1, simply remove the two plug-in jar files that you previously copied into the dropins subdirectory. \n\n\nCross reference information Segment Product Component Platform Version Edition Software Development Rational Asset Analyzer for System z"}]},{"id":"TRAIN_Q513","question":"Help with Security Bulletin: WMB and IIB are affected by denial of service vulnerability (CVE-2014-8901)\n\nI need to understand details regarding Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by denial of service vulnerability (CVE-2014-8901). Where can I find this information? ","answer":"CVEID: CVE-2014-8901 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-8901]\nDESCRIPTION: IBM XML4J and XML4C libraries contain a denial of service vulnerability when loading specially crafted content. This causes the CPU to consume 100% of available resources and creates serious performance degradation to the system.\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99110 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99110] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:S\/C:N\/I:N\/A:P)","is_impossible":false,"contexts":[{"filename":"swg21697458.txt","text":"Title: IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by denial of service vulnerability (CVE-2014-8901) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n WebSphere Message Broker and IBM Integration Bus are affected by denial of service vulnerability. Pattern matching while validating a specially crafted XML document causes XML4C to consume 100% CPU \n\nVULNERABILITY DETAILS\nCVEID: CVE-2014-8901 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-8901]\nDESCRIPTION: IBM XML4J and XML4C libraries contain a denial of service vulnerability when loading specially crafted content. This causes the CPU to consume 100% of available resources and creates serious performance degradation to the system.\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99110 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99110] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:S\/C:N\/I:N\/A:P) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Message Broker V8 \n\nIBM Integration Bus V9 and V10 \n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10 IT07064 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=IT07064 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07064]\n\nThe APAR is targeted to be available in fix pack 10.0.0.4 IBM Integration Bus V9 IT07064 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=IT07064 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07064]\n\nThe APAR is targeted to be available in fix pack 9.0.0.6 WebSphere Message Broker\nV8\nIT07064 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=IT07064 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07064] \n\nThe APAR is targeted to be available in fix pack 8.0.0.7 \nTo mitigate the vulnerability, after an interim fix or fixpack containing IT07064 is applied you must set the following environment variable to disable the use of regular expressions by the MRM parser before starting the broker or integration node: \n\n\n * MQSI_DISABLE_REGEX_IN_XML4C=yes \n\n\n\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?uid=swg27006308 [http:\/\/www.ibm.com\/support\/docview.wss?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 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 29-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. \n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21978064]\n\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"}]},{"id":"TRAIN_Q514","question":"Why is WAS sending duplicate requests though our Portal application user clicks submit button only once?\n\nIs there any setting in WAS,Portal or IHS that can help prevent duplicate requests?","answer":"ServerIOTimeoutRetry can be used to decrease the number of retries after ServerIOTimeout has fired.","is_impossible":false,"contexts":[{"filename":"swg21318463.txt","text":"Title: IBM Recommended values for web server plug-in config - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n In the web server plug-in, what do the LoadBalanceWeight, MaxConnections, ConnectTimeout, ServerIOTimeout, RetryInterval, IgnoreAffinityRequests, and GetDWLMTable options mean and what are the recommended settings for these options?\n\nWhat affect does Session Affinity have?\n\nHow are connections handled during plug-in fail-over?\n\nWhat is the effect of using more than one web server child process? \n\nANSWER\nTo understand how load balancing works in the web server plug-in, see Understanding IBM HTTP Server plug-in Load Balancing in a clustered environment [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21219567].\n\nTo understand how fail-over works in the web server plug-in, see Understanding HTTP plug-in failover in a clustered environment [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21219808].\n\n\nLoadBalanceWeight is a starting \"weight\". The value is dynamically changed by the plug-in during runtime. The \"weight\" of a server (or clone) is lowered each time a request is assigned to that clone. When all weights for all servers drop to 0 or below, the plug-in has to readjust all of the weights so that they are above 0. Using a starting value of only 2 (default), means that the weights will get to 0 very quickly and the plug-in will constantly be readjusting the weights. Therefore, It is recommended to start with a higher LoadBalanceWeight. The IBM WebSphere Application Server administrative console will allow a value up to 20 for this. However, it is certainly possible to manually edit the plugin-cfg.xml file and specify some other value for LoadBalanceWeight that is higher than 20.\n\nNote: At runtime, the LoadBalanceWeight of each appserver in a cluster are normalized by their highest common factor. For example, 100, 90, 80 have a common factor of 10. So, these configured weights would be divided by 10 at runtime, resulting in actual starting weights of only 10, 9, 8. Setting all clones to the same starting LoadBalanceWeight (for example: 20, 20, 20) will result in an actual starting weight of only 1 for each, because of normalization. So, it is recommended to set the weight of at least one of the clones to be off by a value of 1. For example, if there are 3 clones, you might choose the starting LoadBalanceWeights to be: 20, 20, 19. After normalization the weights will be unchanged.\nRecommended values = all clones the same, except one clone off by one (for example: 20, 20, 19)\n\n\nMaxConnections is used to gauge when a server is \"starting to become overwhelmed\". It is not used to determine when to fail-over (mark the server \"down\"). When a request is sent from the plug-in to the WAS appserver, it is called a \"PendingRequest\", until the response comes back. If the application running in WebSphere Application Server is handling requests quickly, each request will only be PENDING for a very short time. So, under ideal conditions, MaxConnections is not needed and therefore the default is (-1) meaning unlimited. However, sometimes an application may start to become overwhelmed and the application may not be able to handle the requests as quickly. Consequently Pending Requests start to build up. MaxConnections can be used to put a limit on the number of PENDING requests per server. When the MaxConnections limit is reached, the plug-in will stop sending requests to that appserver, but it is not marked down. The optimal value for MaxConnections will depend on how quickly the application and appserver respond to each request. If normal responses are returned in less than one second, it may be appropriate to set a low value for MaxConnections, like 20 or so. However, if it normally takes several seconds to get a response from the application, then it would be prudent to use a higher value for MaxConnections, like 100. Please note that if the MaxConnections limit has been reached the plug-in will not send ANY more requests to that server until responses come back for the current PENDING requests, and the pendingRequests count drops back down below the MaxConnections limit.\nRecommended value = 20 - 100 depending on application response times\n\n*Best Practices: with MaxConnections=\"-1\" use LogLevel=\"Stats\" to monitor the pendingRequests numbers in the plug-in log, under normal conditions. Then, choose a value for MaxConnections that is significantly higher than the highest number shown in the log. This method will help you to determine a MaxConnections value that is right for your specific environment.\n\n\nConnectTimeout means \"how long should the plug-in wait when trying to open a socket to the Application Server\"? If there are streams already open and available to the Application Server, the plug-in will use one of those. However, sometimes the plug-in needs to open a new stream to the Application Server. That should not take very long, so the value for ConnectTimeout should be very small. A ConnectTimeout value of 0 means never time-out. In that case, the time-out is left up to the OS TCP layer, which is NOT ideal. It is much better to specify a small positive number (like 5 seconds).\nRecommended value = 5\n\n\nServerIOTimeout means \"how long should the plug-in wait for a response from the application\". After the socket is opened, the plug-in sends the request to the Application Server. The application processes the request and a response is sent back to the client, through the plug-in. How long should that take? What is reasonable, based on the application? There is no single correct answer here. It depends on the application. If the application is very quick to respond, then you can use a lower value for ServerIOTimeout. However, if the application requires more time to process the request (maybe to retrieve data from a database), then you should use a higher number for ServerIOTimeout. Using a value of 0 means that the plug-in will NOT time-out the request. This is often NOT ideal. A positive value means that the plug-in will NOT mark the appserver down after a ServerIOTimeout pops. So, if you want the plug-in to continue sending requests to the timed-out appserver, use a positive value. On the other hand, a negative value means that the plug-in WILL mark the appserver down after a ServerIOTimeout pops. So, if you want the plug-in to immediately mark the appserver down and fail-over to another appserver in the same cluster, use a negative value.\nRecommended value = -900 (that is negative 900)\n\nNote: The ability to use a negative ServerIOTimeout value was introduced in plug-in apar PK72097 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK72097].\n\n*Best Practices: use traces to determine the amount of time it takes for your application to respond to requests under normal conditions. Be sure to include the longest running requests that take the most time to respond. Then choose a value for ServerIOTimeout that is much larger (2X or 3X or more) than the longest response time. This method will ensure that your ServerIOTimeout is high enough to allow adequate time for the application to respond normally. Make it a negative value so that if the ServerIOTimeout pops, the plug-in will immediately mark the server down, and retry the request to a different appserver.\n\n\nServerIOTimeoutRetry can be used to decrease the number of retries after ServerIOTimeout has fired. By default, the Plug-in will try a request equal to the number of members in the cluster. For example, if the cluster has four members, and there is a ServerIOTimeout, the Plug-in will try it a second time. If the retry fails with ServerIOTimeout fired, then it will try a third time, and a fourth time if needed. But after four attempts, the Plug-in will give up and stop retrying. If you want to override this default behavior and reduce the number of retries after ServerIOTimeout, you can set ServerIOTimeoutRetry to a value that is less than the number of members in the cluster.\nRecommended value = -1 (this is the default)\n\nNote: This property was introduced by Plug-in apar PM70559 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PM70559].\n\n\nRetryInterval is the time that the plug-in will wait before trying again to use an appserver that was marked down. The optimal value for RetryInterval depends on the number of appservers in the cluster, and the value used for ServerIOTimeout. You can use the following formula to determine the maximum RetryInterval value for your plug-in config:\n\n(number of appservers in cluster - 1) x (absolute ServerIOTimeout) - 1\n\nFor example, if there are two appservers in the cluster, and the value of ServerIOTimeout is -900, then the maximum RetryInterval setting would be:\n(2 - 1) x (900) - 1 = 899 seconds or less\n\nAnother example, if there are four appservers in the cluster, and the value of ServerIOTimeout is -900, then the maximum RetryInterval setting would be:\n(4 - 1) x (900) -1 = 2699 seconds or less\n\nWarning: Setting RetryInterval to a value higher than the recommended maximum, based on the formula above, can lead to an undesirable situation where all of the appservers in the cluster may be marked down simultaneously resulting in all requests temporarily failing.\nRecommended value = 60 (this is the default)\n\n\nAffinity requests are requests that contain a session cookie (ie. JSESSIONID). The session cookie is set by the Session Manager in WAS to ensure that all subsequent requests from the same client return to the same app server in the cluster. The session cookie contains the clone ID (or partition ID) of that specific app server. The web server Plug-in will look for the session cookie and use the clone ID to send the request to that specific WAS app server. An affinity request is not load balanced.\n\nIn the plug-in config there is a property called IgnoreAffinityRequests. This property determines if affinity requests will affect the load balance weights, or not. The default value for IgnoreAffinityRequests is True, which means that affinity requests will not have any affect on the load balance weights. This is best for environments where there are no, or few, affinity requests. On the other hand, for an environment with a lot of affinity requests, it may be better to set IgnoreAffinityRequests to False so that the load balance weights will accurately reflect the effect of having a lot of affinity requests.\n\n\nFail-over occurs when the plug-in marks a cluster member appserver (or clone) as \"down\", and then sends the pending requests to other members of the same cluster. This can happen if the plug-in is unable to open a new connection to the appserver within the ConnectTimeout. Or fail-over can happen if the plug-in has already sent the request to the appserver, but does not receive a response from the application within ServerIOTimeout. When the plug-in marks a cluster member appserver \"down\", it will handle the PENDING requests in one of two ways: Prior to plug-in apar PM12112 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PM12112], the plug-in would send all of the pending requests to the very next appserver in the cluster. However, after plug-in apar PM12112 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PM12112], the plug-in will randomly send the pending requests to any of the available appservers in the cluster. While the appserver is marked \"down\" the plug-in will no longer send any requests to it. After RetryInterval the plug-in will check to see if that appserver can be used successfully again. If so, the \"down\" flag will be removed and the appserver will be used again.\n\nNote: By default, the number of attempts to handle a request is limited by the number of appservers in the cluster. For example, if there are only two appservers in the cluster, and the request fails once, the plug-in will only attempt that request one more time (total of two attempts). Or another example, if there are five appservers in the same cluster, and the request fails once, then the plug-in will attempt to retry that same request up to four more times (total of five attempts). That number includes retries sent to the same appserver (session affinity), or attempts sent to different appservers (fail-over).\n\nUpdate: The plug-in apar PM70559 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PM70559] introduced a new setting called \"ServerIOTimeoutRetry\" that can be used to control the number of retries due to ServerIOTimeout.\n\n\nIf Memory-to-Memory (M2M) session replication is enabled in WebSphere Application Server, then the GetDWLMTable setting in the plug-in config must be changed to \"true\". Memory-to-Memory replication uses partition IDs rather than clone IDs. This can lead to broken session affinity if GetDWLMTable is set to false (which is the default). So it is very important to set GetDWLMTable=\"true\" whenever using M2M in WebSphere Application Server.\nRecommendation = GetDWLMTable=\"true\" whenever M2M is used in WebSphere Application Server.\n\n\nEach web server child process loads a separate instance of the web server plug-in. And multiple running instances of the web server plug-in do not share information with each other. For example if the IBM HTTP Server web server is configured to start 3 child processes (StartServers 3), then there will be 3 instances of the web server plug-in running (one for each IBM HTTP Server child process). The dynamically changing LoadBalanceWeight of each cluster member is not shared between the plug-in instances. So, in one instance of the plug-in \"member1\" might be considered UP with a weight of 5, when in another instance of the plug-in \"member1\" might be considered DOWN and unusable. This can result in possibly different behaviors depending on which child process \/ plug-in instance handles each incoming request. For this reason it is recommended that you should configure the web server to use only a few web server child processes with many threads on each. See Tuning IBM HTTP Server to maximize the number of client connections to WebSphere Application Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21167658].\n\nIf you choose to use more than one web server child process, keep in mind that the plug-in settings are handled on a per instance basis. For example, MaxConnections means the number of pending requests that will be allowed on that server, for each plug-in instance. If MaxConnections = 20, and there are 3 web server child processes (3 plug-in instances), then each instance will allow 20 pending connections to that Application Server for a total of 60 pending connections.\n\n\nRelated information\n[http:\/\/g01zciwas003.ahe.pok.ibm.com\/support\/dcf\/preview.wss?host=g01zcidbs003.ahe.pok.ibm.com&db=support\/swg\/swgtech.nsf&unid=E3B7487DDFB64D2C852574C00071DA95&taxOC=SSCC2GP&MD=2011\/05\/11%2011:05:12&sid=#]Understanding plug-in Load Balancing [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21219567]\nUnderstanding plug-in Fail-over [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21219808]\nTuning IBM HTTP Server processes and threads [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21167658]\nweb server plug-in configuration [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21450051]\nModifying plug-in properties from the WebSphere Application Server administrative console [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21460889]\nHow do the properties ServerIOTimeout and PostBufferSize affect plug-in behavior? [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21408884]"}]},{"id":"TRAIN_Q515","question":"SPSS will not start on Mac\n\n\n\nI downloaded SPSS about 3 weeks ago. On the day when I downloaded it, it was working fine. Last week, I tried starting SPSS but it did not start. I tried reinstalling it, it still would not open. I've updated JAVA (thought this would be a problem), it slowly opened the program but then now that I have reinstalled it and entered in my code, I've used up my code and I have no authorization. But just now, I started SPSS and the same problem is happening. The IBM SPSS name screen appears but nothing happens.\n\n SPSS would not start.\n\n Even if it does start, I have licensing problems.\n","answer":"Delete the following file: com.ibm.spss.plist on your Macintosh to dramatically reduce the opening and closing of the Statistics software.","is_impossible":false,"contexts":[{"filename":"swg21651225.txt","text":"Title: IBM Performance issue on Mac OS X Launching and Closing SPSS Statistics 21 or 22. - United States\n\nText:\nMac OS X; Performance; open; close; exit; launch; 10.6.x 10.7.x 10.8.x 10.9.x TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n With SPSS Statistics 21 or 22 software installed on Mac OS X. \nThe software was running normally, but for what ever reason, the program might fail or close improperly by using Force Quit several times. \n\nCAUSE\nThis has been identified as a product defect under APAR PM90266\n\nENVIRONMENT\nThis technote applies with any Mac OS X compatible with Statistics 21 or 22, Not version 23. \n\n- IBM SPSS Statistics 21 release is supported on Apple Macintosh 10.6 (Snow Leopard), 10.7 (Lion), and 10.8 (Mountain Lion) with Intel processor. \n\n- IBM SPSS Statistics 22 release is supported on Apple Macintosh 10.7 (Lion), and 10.8 (Mountain Lion) with Intel processor. \nNote: IBM SPSS Statistics 22 for Macintosh (Mavericks, OSX 10.9 Operating System) is not officially supported until Statistics 22 FixPack 1 is released. \n\n\nNote: Windows computers see \nTechnote 1652535\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21652535 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21652535]\n\nNote: For Statistics 23.0 Windows or Mac OS X, refer to technote: 1640411\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21640411 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21640411]\n\n\nDIAGNOSING THE PROBLEM\nOne or more of the following symptoms might occur that this resolution can solve. \n\n(1) Statistics takes an abnormally longer time to start and close than when the software was initially installed. \n\n(2) Very slow response and performance with using the software. \n\n(3) The 'Data Editor' menu no longer appears under the Main menu bar.\n\n\nRESOLVING THE PROBLEM\nDelete the following file: com.ibm.spss.plist on your Macintosh to dramatically reduce the opening and closing of the Statistics software. \n\n- You can delete it by opening the Finder and locate the Library\/Preferences folder: \/Library\/Preferences\/com.ibm.spss.plist\n(1) Restart your Mac.\n(2) Open 'Finder'.\n(3) Select the 'Home' (house) icon (folder) in the left-hand pane.\n(4) Select the 'Go' menu at top of screen.\n(5) Press the 'Option' key. The list of menu options will now include 'Library'.\n(6) Select the 'Library' menu option.\n(7) Open the 'Preferences' folder.\n(8) Rename the com.ibm.spss.plist object to old_com.ibm.spss.plist \n\n\n- Another option is to use the Terminal application and do the following:\nrm -fR ~\/Library\/Preferences\/com.ibm.spss.plist \n\n \n\nFinish and test your changes by doing the following: \n\n(9) Launch Statistics\n(10) Work with the program a bit.\n(11) Close the software (It should be quicker, do not force quit)\n(12) Re-launch Statistics\n(13) Work with the program a bit.\n(14) Close the software (do not force quit)\n(15) Launch the software \n\n\nNOTE: When you launch Statistics for the first time, it will take a little longer than subsequent launches, until you reboot your computer again. This is related to Java initialization routines. \n\n\n- FYI: Additionally, if you are using Mac OSX Mavericks 10.9.x, you need to stop the process that protects this file and restores it (it is deleted):\n\nSince OSX 10.9.x Mavericks a cached copy of your \"plist\" file is stored that uses a background process: CFPREFSD\nDeleting the \"plist\" file and restarting SPSS Statistics does not create a new copy of these files.\nRather, Mavericks restore its cached copy. \nOnly by stopping the \"cfprefsd\" process and starting SPSS Statistics, will it generate a new \"plist\" preference file and default toolbar.\n\nWhen you go to Finder - Applications - Utilities and open Activity Monitor on the 10.9.x computer you see that there is a CFPREFSD process visible for root user and for the current logged in user.\nYou need to stop the CFPREFSD process for the current user. Do so in the Terminal application by running the following command:\n\nkillall -u {CURRENT_USER} cfprefsd\n\nWhere {CURRENT_USER} is replaced with the person's user ID. One can get the user ID by typing \"whoami\" at a Terminal prompt. \n\nShould removing these files and running the program does not resolve the issue, you might need to remove all of them and reinstall the program.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]"}]},{"id":"TRAIN_Q516","question":"RecognizePageFieldsICR_C aborts with Page Type change\n\n I have an DeveloperWorks application that runs: Survey. In the application PageID Task there is a function that sets the Page Type to ReliefForm (based on a barcode)\n\nDoes anyone know why when I change the SetPageType to set another name, the RecognizePageFieldsICR_C in the Profiler Task aborts? If I put the name back the action runs fine. ","answer":"In Datacap Studio, set the c_cr variable to USA prior to the call to recognition as follow:\n\nSaveAsCurrentObjVariable(\"c_cr\", \"USA\")\nRecognizeFieldICR_C","is_impossible":false,"contexts":[{"filename":"swg21654520.txt","text":"Title: IBM Datacap Taskmaster Capture ICR error code 12 - United States\n\nText:\nRecognizeFieldICR_C; Recostar; 12 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When performing field level ICR recognition using the action RecognizeFieldICR_C (), the batch aborts with error code 12. \n\nSYMPTOM\nFrom log file:\n\nExecuting 'RecognizeFieldEx' from 'Datacap.Recognition.Recostar.ICRCWrapperClass'. Parameter : <FieldName>\nRecognition return status: 12(Not defined (not used))\n\n\nCAUSE\nThe c_cr variable for ICR_C recognition is not set for the engine.\n\nRESOLVING THE PROBLEM\nIn Datacap Studio, set the c_cr variable to USA prior to the call to recognition as follow:\n\nSaveAsCurrentObjVariable(\"c_cr\", \"USA\")\nRecognizeFieldICR_C"}]},{"id":"TRAIN_Q517","question":"Installed an STAP on a DB Server but it does not show up on my Appliance in S-TAP Control etc\n\n\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\nHow do I correct the problem?","answer":"Uncheck the Approval box and the S-TAPs should start connecting .","is_impossible":false,"contexts":[{"filename":"swg22009818.txt","text":"Title: IBM Guardium STAP does not connect properly and does not show in the S-TAP Control - I see some specific errors in some log files. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What can cause an STAP to fail to connect properly - I get the following messages in the logs:-\n\n\/tmp\/guard_stap.stderr.txt on the DB Server :-\n\"Server <ip_addr> wasn't heard from for nn sec during this attempt (nnn sec total), closing and re-opening\"\n\nand from the Guardium Appliance - via fileserver in the \/log\/opt-ibm-guardium-log\/snif\/snif.log\n\"Unauthorized client connecting from <ip_addr> ,rejecting\"\n\n\nCAUSE\nOne reason for these errors could be that the S-TAP Approval Needed is checked in the S-TAP Certification screen on the Appliance like this :- \n[\/support\/docview.wss?uid=swg22009818&aid=1] [\/support\/docview.wss?uid=swg22009818&aid=1]\n\n\n\n\n\nANSWER\nUncheck the Approval box and the S-TAPs should start connecting . \n\n\n[\/support\/docview.wss?uid=swg22009818&aid=2] [\/support\/docview.wss?uid=swg22009818&aid=2]"}]},{"id":"TRAIN_Q518","question":"Help with Security Bulletin: IBM WebSphere MQ is affected by a vulnerability in GSKit (CVE-2014-0076)\n\nI need to understand details regarding Security Bulletin: IBM WebSphere MQ is affected by a vulnerability in GSKit (CVE-2014-0076). Where can I find this information? ","answer":"CVE-ID: CVE-2014-0076 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-0076]\nDESCRIPTION: An attacker running a program on the same machine as where the victim is running a program could use CPU timing information to discover key information about certain kinds of binary type Elliptic Curves used in Digital signatures during signing operations. Although GSKit only generates Prime type Elliptic Curves, externally generated keys may be imported in GSKit.\nFrom WebSphere MQ version 7.1, GSKit version 8.0 is integrated with WebSphere MQ. For WebSphere MQ 7.0.1, GSKit version 7 or version 8 was installed separately.\n\nCVSS Base Score: 2.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/91990 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/91990]\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:L\/AC:L\/Au:N\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21688949.txt","text":"Title: IBM Security Bulletin: IBM WebSphere MQ is affected by a vulnerability in GSKit (CVE-2014-0076) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A vulnerability in GSKit, which is included in IBM WebSphere MQ, can potentially allow key information about certain kinds of binary type Elliptic Curves used in Digital signatures during signing operations. \n\nVULNERABILITY DETAILS\nCVE-ID: CVE-2014-0076 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-0076]\nDESCRIPTION: An attacker running a program on the same machine as where the victim is running a program could use CPU timing information to discover key information about certain kinds of binary type Elliptic Curves used in Digital signatures during signing operations. Although GSKit only generates Prime type Elliptic Curves, externally generated keys may be imported in GSKit.\nFrom WebSphere MQ version 7.1, GSKit version 8.0 is integrated with WebSphere MQ. For WebSphere MQ 7.0.1, GSKit version 7 or version 8 was installed separately.\n\nCVSS Base Score: 2.1\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/91990 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/91990]\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, including all maintenance levels. \n\nIBM WebSphere MQ 7.5, including all maintenance levels. \n\nIBM WebSphere MQ 7.1, including all maintenance levels. \n\nIBM WebSphere MQ 7.0.1, maintenance levels from 7.0.1.4 onwards, using GSKit version 8.0.\n\nREMEDIATION\/FIXES\nIBM strongly recommends that Elliptic Curve CipherSpecs are not used. These CipherSpecs have names starting with 'EC'. \n\nA summary of MQ CipherSpecs and protocols can be found in the IBM Knowledge Center Specifying CipherSpecs [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.sec.doc\/q014260_.htm] topic.\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 03 November 2014: 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=swg21689211]"}]},{"id":"TRAIN_Q519","question":"Help with Security Bulletin: Cross-site scripting vulnerabilities in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) error handling (CVE-2015-0193)\n\nI need to understand details regarding Security Bulletin: Cross-site scripting vulnerabilities in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) error handling (CVE-2015-0193). Where can I find this information? ","answer":"CVEID:CVE-2015-0193 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0193]\nDESCRIPTION:IBM Business Proccess Manager is vulnerable to cross-site scripting, caused by improper neutralization of user-supplied input in some error situations. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101009 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101009]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:N\/I:P\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21697944.txt","text":"Title: IBM Security Bulletin: Cross-site scripting vulnerabilities in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) error handling (CVE-2015-0193) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM Business Proccess Manager is vulnerable to cross-site scripting, caused by improper neutralization of user-supplied input in some error situations. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2015-0193 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0193]\nDESCRIPTION:IBM Business Proccess Manager is vulnerable to cross-site scripting, caused by improper neutralization of user-supplied input in some error situations. A remote attacker could exploit this vulnerability using a specially-crafted URL to execute script in a victim's Web browser within the security context of the hosting Web site, once the URL is clicked. An attacker could use this vulnerability to steal the victim's cookie-based authentication credentials.\nCVSS Base Score: 3.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101009 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/101009]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:S\/C:N\/I:P\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\n \n\n * IBM Business Process Manager Standard V7.5.x.x through 8.5.5.0 \n * IBM Business Process Manager Express V7.5.x.x through 8.5.5.0 \n * IBM Business Process Manager Advanced V7.5.x.x through 8.5.5.0 \n * WebSphere Lombardi Edition 7.2\n\n\nIf you are using an older unsupported version, IBM strongly recommends to upgrade. REMEDIATION\/FIXES\nInstall the interim fix for APAR JR52626 as appropriate for your current IBM Business Process Manager or WebSphere Lombardi Edition version. \n\n * IBM Business Process Manager Express [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR52626] \n * IBM Business Process Manager Standard [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR52626] \n * IBM Business Process Manager Advanced [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR52626] \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=JR52626]\n\nWORKAROUNDS AND MITIGATIONS\nAs a pre-caution, advise users not to click links in email.\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 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 2015-05-27 - initial version published\n2015-10-07 - updated version numbers \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 Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5, 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 Express Security Linux, Linux zSeries, Windows 8.5.5, 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, Linux zSeries, Linux\/x86, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2"}]},{"id":"TRAIN_Q520","question":"OCR Results for Bold fonts\n\n\n\nHi all,\n\nI am having issue with extracting front that are bold, big front. May I know if Datacap have limitation on capturing metadata with big, bold front such as title of the document. I am using RecognizePageOCR_A for extraction of meta data and every other words were being extracted fine except those that are big. The attachment are the sample of front that could not be captured.","answer":"Do one of the following as appropriate for the situation. \n\n * Verify that the newest recognition engine is being used. Currently this is done using the RecognizePageOCR_S action from the ocr_sr library. \n * Increase the height limit for the action using SetMaxCharacterHeightTMM(x) where x represents the height in pixels. Default depends on the DPI, but for 300 DPI is 64. \n * Reduce the height of the word in pixels. This may be done either by making the word smaller, or by reducing the number of pixels per inch for the tiff.","is_impossible":false,"contexts":[{"filename":"swg21620875.txt","text":"Title: IBM Recognition gives Word too tall error with IBM Datacap Taskmaster Capture - United States\n\nText:\nrecognition OCR OCR_A OCR_S TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When performing recognition on an image, recognition fails. The RRS log entry shows:\n\nWord too tall, removed. \n\nCAUSE\nThis error can occur when the height of the word in pixels exceeds the configured limit. It can also occur when the recognition engine cannot identify the boundaries of the word.\n\nRESOLVING THE PROBLEM\nDo one of the following as appropriate for the situation. \n\n * Verify that the newest recognition engine is being used. Currently this is done using the RecognizePageOCR_S action from the ocr_sr library. \n * Increase the height limit for the action using SetMaxCharacterHeightTMM(x) where x represents the height in pixels. Default depends on the DPI, but for 300 DPI is 64. \n * Reduce the height of the word in pixels. This may be done either by making the word smaller, or by reducing the number of pixels per inch for the tiff."}]},{"id":"TRAIN_Q521","question":"Cannot open module in exclusive edit - (no such file or directory)\n\n Hello.\n\nI have a module, that I can open normally, but when I try to open it in Exclusive Edit it tells me that \"no such file or directory\"\n\nWhat does this mean?","answer":"This error indicates that a user session file is corrupted on the database server. \n\nThis defect is resolved in IBM Rational DOORS Version 9.4.0.1","is_impossible":false,"contexts":[{"filename":"swg21511831.txt","text":"Title: IBM DOORS module fails to open in exclusive edit mode results in error \"unable to open module ...no such file or directory\" - United States\n\nText:\nmissing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to open a module exclusive edit in IBM Rational DOORS result in the error \"DOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\". \n\nSYMPTOM\nA module with a large number of sections is used mostly in shareable edit mode. \n\nYou can open the module Read-only , or Shareable-Edit; but not in exclusive edit. \n\nSteps to reproduce: \n\n 1. Login to DOORS\n \n \n 2. Click the Project, or folder, icon that contains the module\n \n \n 3. Click the module icon in the DOORS Explorer window\n \n \n 4. Click File > Open> Exclusive Edit (Ctrl + E)\n \n\n\nExpected result: The module should open in Exclusive edit mode. \n\nActual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode. If you attempt to check the database integrity for issue the module is not flagged for any problems. \n\nThe full error message is as follows:\n\nDOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\"\nC:\\Program Files (x86)\\IBM\\Rational\\DOORS\\9.5\\data\\v6data\\20\\m00000021.mod\\current.ver\\s1000005.dtc\n\n\nimage \n\n[\/support\/docview.wss?uid=swg21511831&aid=1] [\/support\/docview.wss?uid=swg21511831&aid=1]\n\nCAUSE\n This issue has been identified as a product defect under APAR PM50525 [http:\/\/ibm.com\/support\/docview.wss?uid=swg1PM31236].\n\n\n\nRESOLVING THE PROBLEM\nThis error indicates that a user session file is corrupted on the database server. \n\nThis defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27036720#9401] \n\n \n\nWORKAROUND: \n\nthe following options can be used to correct this problem: \n\n * Retrieve the missing file from system backup and insert it into the module current.ver directory\n \n The advantage of inserting the missing session file is you do not need to restart the database server.\n\nWarning these two option should only be performed by Rational Support. Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database. Send the session.ixc file to support for repair\n\nFrom the module directory listed in the error message provide support the file session.ixc\nChoosing to have support repair the session index file requires you to have all users log out \nand shut down the DOORS database server until the repaired file is returned and inserted \nto replace the existing data file for the module.\n\nCreate a replacement session file \nFrom the module directory listed in the error message provide support the file session.ixc\nAdjacent session files will be required in order to to create the replacement. \nYour support engineer will identify these files from the session index file.\nNo work can be performed in the effected module until the replacement session file is restored\nfor the effected module. \n\n\nNote: Generally the repair is only required for one user session file. However in circumstances where DOORS reports a missing session file for a module- the event that caused this may have effected session files for other users connected to the module. For this situation you may need to perform a successive repair to the index file."}]},{"id":"TRAIN_Q522","question":"Can IBM Content Navigator be installed on Windows and be deployed to an Application Server that is running on a Unix Platform?\n\nCan IBM Content Navigator be installed on Windows and be deployed to an Application Server that is running on a Unix Platform? ","answer":"This is not a supported configuration.","is_impossible":false,"contexts":[{"filename":"swg21980148.txt","text":"Title: IBM Can IBM Content Navigator be installed on Windows and be deployed to an Application Server that is running on a Unix Platform. - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Can IBM Content Navigator be installed on Windows and be deployed to an Application Server that is running on a Unix Platform. \n\nANSWER\nThis is not a supported configuration."}]},{"id":"TRAIN_Q523","question":"If we need to log client ip, if the FELB is enabled, does it still need enable x-forwarder-for?\n\nIf we need to log client ip, if the FELB is enabled, does it still need enable x-forwarder-for?","answer":"This is a known limitation in the current implementation of haproxy ( FELB ), especially with the layer 7 where SSL termination is handled.\nNotice that forwarding a client IP address to a backend works when the FELB is setup to use non-SSL configuration.","is_impossible":false,"contexts":[{"filename":"swg21971127.txt","text":"Title: IBM Client IP address missing from the X-Forwarded-For header - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is the Front End Load Balancer ( FELB ) not forwarding a client IP address to a backend? \n\nANSWER\nThis is a known limitation in the current implementation of haproxy ( FELB ), especially with the layer 7 where SSL termination is handled.\nNotice that forwarding a client IP address to a backend works when the FELB is setup to use non-SSL configuration."}]},{"id":"TRAIN_Q524","question":"I have an issues with V701 SCSQAUTH\/SCSQANLE and MQ V8, my batch jobs receiving an ABEND (ABN=102-00000000).\n\nI have an issues with V701 SCSQAUTH\/SCSQANLE and MQ V8, my batch jobs receiving an ABEND (ABN=102-00000000). ","answer":"Correct the STEPLIB for the batch job to point to the V7.1.0 libraries.","is_impossible":false,"contexts":[{"filename":"swg21647026.txt","text":"Title: IBM Batch job fails with ABEND 102 REASON 00000000 \nDUMP TITLE=CSQ1,ABN=102-00000000 ... Mismatch code levels - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Your WebSphere MQ (WMQ) batch job abends with an abend 102 - 00000000\nABEND102 ABENDS102 S102 \n\nCAUSE\nOne reason for Abend 102-00000000 - \n\nMismatch in code levels between WMQ MSTR (Queue Manager) and the batch job\n\nThe S102 is occurring as the batch job is running with V701 libraries (for example, SCSQAUTH dataset which contains CSQBSRV, CSQBCON etc) against a V710 queue manager. In order to run against a V710 queue manager the V710 libraries need to be used by the batch job. \nIn order to connect to a V710 queue manager the application needs to run with a V710 SCSQAUTH. The V710 SCSQAUTH will allow an application to connect to both a V710 or a V701 queue manager. \nThis is documented in the Information Center (section 'z\/OS: Planning for migration from WebSphere MQ version 7.0.1 to WebSphere MQ version 7. [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r1\/index.jsp?topic=%2Fcom.ibm.mq.doc%2Fmi77108_.htm]1'; \n\n\n * \n\n\nPer ' Application migration and interoperation [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r1\/index.jsp?topic=%2Fcom.ibm.mq.doc%2Fmi23001_.htm]' topic, WebSphere MQ does not support connecting server applications loading libraries from the earlier level to connect to a later level of queue manager. On z\/OS the STEPLIB must reference the target libraries for the queue manager. \n\nDIAGNOSING THE PROBLEM\nIn IPCS you can view level of CSQBSRV in the batch job address space. \n\nSTORAGE ---------------------------------- \nCommand ===> \nAddress: \n294D8210 DD2DD220 DD0CB6C7 D70BDAF8 DAF8D77B | ..K....GP..8.8P# | \n294D8220 D748D748 A7F4000E C3E2D8C2 E2D9E540 | P.P.x4..CSQBSRV \n294D8230 F2F0F1F2 F1F1F2F7 E4D2F8F3 F7F7F440 | 20121127UK83774| . \nPTF UK83774is for Release ... 010 (V7.0.1) \n\n\nRESOLVING THE PROBLEM\nCorrect the STEPLIB for the batch job to point to the V7.1.0 libraries.\n\n\n\nHISTORICAL NUMBER\n 04659 79L 000\n47552 077 724 \n\nPRODUCT ALIAS\/SYNONYM\n wmq mq"}]},{"id":"TRAIN_Q525","question":"Can I change the ITCAM J2EE Agent Monitoring Level via the TEPS in version 7.1.1?\n\n\n\nIn the 7.1 version of the J2EE agent I could use the Agent Configuration to change the Monitoring Level for the agent- https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SS3JRN_7.2.0\/com.ibm.itcamfapps_ad.doc_72\/J2EE_agent_tema_install_guide\/step10.html\n\nSo how can I change the Monitoring Level in the 7.1.1 agent?\n","answer":"In the older release of the J2EE agent (v6.2 FP6), there was an option to specify the Monitoring Level, Sampling Rate and other parameters (threshold values, time intervals, etc..) during the configuration phase of the agent itself. This is now not possible in the new J2EE agent v7.1.1.0.0 configuration panels as these options are not available anymore. \n\nThe default values for the Monitoring Level and the Sampling Rate are L1 and 2% respectively. If you want to change these default values permanently, then please make these changes.\n\nIn the $ITM_HOME\/config (Unix) dir or %ITM_HOME%\\TMAITM6 (Windows), you will find the <hostname>_yj.xml file. Make a copy of this file, then stop the agent and make changes to the parameters (see screenshot below) in the file. Save file, restart the agent. The new values will now be accepted in the agent. If you are deploying a new Weblogic application, stop the agent, modify the <hostname>_yj_<wls_instance>.xml file then restart the agent again.","is_impossible":false,"contexts":[{"filename":"swg21700308.txt","text":"Title: IBM Modifying the default Monitoring Level and Sampling Rate in the J2EE v7.1.1.0.0 agent. - United States\n\nText:\nJ2EE TEMA Monitoring Level Sampling Rate xml files CAMADALL CAMJ2INST DC WebLogic TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n How do I modify the default Monitoring Level and Sampling Rate in the new J2EE v7.1.1.0.0 agent? \n\nANSWER\nIn the older release of the J2EE agent (v6.2 FP6), there was an option to specify the Monitoring Level, Sampling Rate and other parameters (threshold values, time intervals, etc..) during the configuration phase of the agent itself. This is now not possible in the new J2EE agent v7.1.1.0.0 configuration panels as these options are not available anymore. \n\nThe default values for the Monitoring Level and the Sampling Rate are L1 and 2% respectively. If you want to change these default values permanently, then please make these changes.\n\nIn the $ITM_HOME\/config (Unix) dir or %ITM_HOME%\\TMAITM6 (Windows), you will find the <hostname>_yj.xml file. Make a copy of this file, then stop the agent and make changes to the parameters (see screenshot below) in the file. Save file, restart the agent. The new values will now be accepted in the agent. If you are deploying a new Weblogic application, stop the agent, modify the <hostname>_yj_<wls_instance>.xml file then restart the agent again.\n\n[\/support\/docview.wss?uid=swg21700308&aid=1] [\/support\/docview.wss?uid=swg21700308&aid=1]\n\n \n\nPRODUCT ALIAS\/SYNONYM\n ITCAM ITCAM for J2EE DC JBoss WebLogic"}]},{"id":"TRAIN_Q526","question":"Reporting in Rhapsody\n\n\n\nHello All,\n\nI can't find the reports plus in my Rhapsody v8.1.2 x64\n\nanybody knows the reason.","answer":"Rational Rhapsody ReporterPlus N N N N N N N N N N N N Y Y WindRiver Workbench 3.3 integration N N N N N N N N N N N N N N Visual Basic for Applications (VBA) N N N N N N N N N N NA NA NA NA Tornado IDE integration N N N N NA NA NA NA NA NA NA NA NA NA [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] N \u2013 not available","is_impossible":false,"contexts":[{"filename":"swg27038779.txt","text":"Title: IBM Availability of features in the 64-bit version of Rational Rhapsody (8.0.3 and later) - United States\n\nText:\nrhapsody; windows 64-bit PRODUCT DOCUMENTATION\n\nABSTRACT\n This table presents information on the availability of features in the 64-bit version of Rational Rhapsody. Features not listed here have been available in the 64-bit version since it was first released. \n\nCONTENT\n \n\n[\/support\/docview.wss?uid=swg27038779&aid=1] 803 804 805 806 81 811 812 8121 813 814 815 82 821 83 Rational Rhapsody Architect for Software N N N N N N N N N N N N Y Y Reverse engineering - for languages other than Ada N N N N N N N N N N Y Y Y Y Roundtripping - for languages other than Ada \u2013 component level N N N N N N N N N N Y Y Y Y Roundtripping - for languages other than Ada \u2013 individual classes N N N N N N N N N N N Y Y Y Code-centric mode (without code-generation) N N N N N N N N N N N N N Y Action language N N N N N N N N N N N N N N SCC-based configuration management tool integrations: [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] * \n\nN N N N N N N N N N N N N N * \n\nN N N N N N N N N N N N N N * \n\nN N N N N N N N N N N N N N * \n\nN N N N N N N N N N N N N N Rational Team Concert direct integration (RTC actions within Rhapsody) NA NA NA NA NA NA NA NA NA NA NA Y Y Y Rational System Architect import N N N N N N N N N N N N N N Webify (web-enabling a model) N N N N N N N N N N N N N N TeamCenter integration N N N N N N N N N N N N NA NA Rational DOORS integration (via internal interface, not Gateway) NA NA NA NA NA NA NA NA NA NA NA NA NA NA Rational Rhapsody ReporterPlus N N N N N N N N N N N N Y Y WindRiver Workbench 3.3 integration N N N N N N N N N N N N N N Visual Basic for Applications (VBA) N N N N N N N N N N NA NA NA NA Tornado IDE integration N N N N NA NA NA NA NA NA NA NA NA NA [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] N \u2013 not available\nY \u2013 available\nNA \u2013 not available in 32-bit version either [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1] [\/support\/docview.wss?uid=swg27038779&aid=1]"}]},{"id":"TRAIN_Q527","question":"Why is my MQ Java \/ JMS application getting 2035 NOT_AUTHORIZED error after upgrade of MQ?\n\nWhy is my MQ Java \/ JMS application getting 2035 NOT_AUTHORIZED error after upgrade of MQ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q528","question":"We have configured a new LDAP server in Atlas but why does authentication work for only some users ?\n\nWe have configured a new LDAP server in Atlas but why does authentication work for only some users ? ","answer":"Make sure the user who failed to login exists in Atlas and is active. If not , create the corresponding user manually or use HR Loader to import those users who are part of the new LDAP server.","is_impossible":false,"contexts":[{"filename":"swg21976589.txt","text":"Title: IBM LDAP allows authentication for only some users in Atlas. - United States\n\nText:\natlas; pss TECHNOTE (FAQ)\n\nQUESTION\n We have configured a new LDAP server in Atlas but why does authentication work for only some users ? \n\nCAUSE\nAtlas login fails with \"Authentication failed: Unknown user (or) password\"\n\nANSWER\nMake sure the user who failed to login exists in Atlas and is active. If not , create the corresponding user manually or use HR Loader to import those users who are part of the new LDAP server."}]},{"id":"TRAIN_Q529","question":"Help with Security Bulletin: Vulnerabilities in IBM SDK for Node.js affect IBM Business Process Manager Configuration Editor\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in IBM SDK for Node.js affect IBM Business Process Manager Configuration Editor (CVE-2014-3569, CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-8275, CVE-2015-0204, CVE-2015-0205, CVE-2015-0206). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q530","question":"How to find out more details about ORB \/ corba minor-codes?\n\nI get some orb-exceptions in my EJBs and I want to find out more about the thrown ORB-minor-codes. For example:\n\n\"vmcid: IBM minor code: E86 completed: Maybe\"\n\nWhere can I find more information about this minor code: E86?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q531","question":"Is there Self-Describing Agent Support for ITCAM AD 7.1 Agent?\n\nDoes ITCAM for AD 7.1 (YN) agent for WAS support SDA (Self-Describing-Agent) feature? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q532","question":"Does Tivoli Monitoring NetApp monitoring agent support OCUM environments?\n\nDoes Tivoli Monitoring NetApp monitoring agent support OCUM environments?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q533","question":"Help with Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4941)\n\nHelp with Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4941)","answer":"CVEID: CVE-2015-4941 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4941]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)","is_impossible":false,"contexts":[{"filename":"swg21972012.txt","text":"Title: IBM Security Bulletin: Malformed client flows abend MQTT channel (CVE-2015-4943, CVE-2015-4941, CVE-2015-4942) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A number of malformed MQTT client flows could be issued by a malicious user to cause the MQXR service to abend and require manual restart. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-4943 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4943]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104516] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:N\/C:N\/I:N\/A:P)\nCVEID: CVE-2015-4941 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4941]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service due to incorrect handling of abbreviated TLS handshake.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104514] 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-4942 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-4942]\nDESCRIPTION: IBM WebSphere MQ could allow a remote attacker to crash the MQXR service using a sequence of connect and disconnects which will have to be restarted.\nCVSS Base Score: 5\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/104515] 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\nIBM WebSphere MQ 8.0 \n\n - IBM WebSphere MQ 8.0.0.3 and earlier maintenance levels \n\nIBM WebSphere MQ 7.5 \n\n - IBM WebSphere MQ 7.5.0.5 and earlier maintenance levels \n\nIBM WebSphere MQ 7.1 \n\n - IBM WebSphere MQ 7.1.0.6 and earlier maintenance levels\n\nREMEDIATION\/FIXES\nWebSphere MQ 8.0 \n\n - Apply fixpack 8.0.0.4 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21969244] \n\nWebSphere MQ 7.5 \n\n - Apply interim ifix 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\nWebSphere MQ 7.1 \n\n - Apply fixpack 7.1.0.7 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21965293]\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\nReported to IBM by Codenomicon at http:\/\/www.codenomicon.com\/ [http:\/\/www.codenomicon.com\/] \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. \n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21977182]"}]},{"id":"TRAIN_Q534","question":"Can you upgrade directly from Firmware Version 6 to Firmware Version 7 for IBM DataPower Gateway?\n\nCan you upgrade directly from Firmware Version 6 to Firmware Version 7 for IBM DataPower Gateway or is there an interim step\/pre-requisite? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q535","question":"SYSIBMADM.DBCFG IS AN UNDEFINED NAME error message on z\/OS ODM Event Server\n\nOn Z\/OS, Events runtime may trace the following exception into system logs when DB2 is used as the runtime repository: com.ibm.websphere.ce.cm.StaleConnectionException: SYSIBMADM.DBCFG IS AN UNDEFINED NAME. SQLCODE=-204, SQLSTATE=42704, DRIVER=3.65.102 ","answer":"This error message can be safely ignored.","is_impossible":false,"contexts":[{"filename":"swg21690184.txt","text":"Title: IBM Ignorable SYSIBMADM.DBCFG IS AN UNDEFINED NAME error message - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n On Z\/OS, Events runtime may trace the following exception into system logs when DB2 is used as the runtime repository:\ncom.ibm.websphere.ce.cm.StaleConnectionException: SYSIBMADM.DBCFG IS AN UNDEFINED NAME. SQLCODE=-204, SQLSTATE=42704, DRIVER=3.65.102 \n\nSYMPTOM\ncom.ibm.websphere.ce.cm.StaleConnectionException: SYSIBMADM.DBCFG IS AN UNDEFINED NAME. SQLCODE=-204, SQLSTATE=42704, DRIVER=3.65.102 is logged.\n\n\nCAUSE\nDB2 SYSIBMADM.DBCFG table view does not exist on Z\/OS.\n\nRESOLVING THE PROBLEM\nThis error message can be safely ignored."}]},{"id":"TRAIN_Q536","question":"Why do we see database errors \"caused by com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001,...\" in SystemOut.log?\n\nWhy do we see database errors \"caused by com.ibm.db2.jcc.am.SqlDataException: DB2 SQL Error: SQLCODE=-302, SQLSTATE=22001,...\" in SystemOut.log?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q537","question":"Netcool\/Impact 6.1.0: How to change the HSQLDB password?\n\nNetcool\/Impact 6.1.0: How to change the HSQLDB password?","answer":"SET PASSWORD\n * \n * \n * SET PASSWORD <password>;\n * \n * \n * Changes the password of the currently connected user.","is_impossible":false,"contexts":[{"filename":"swg21967958.txt","text":"Title: IBM Change HSQLDB password - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; hsql; database; data; base; db; hsqldb; pass; word; password; pw; sa; system; admin; systemadmin; security; sec; authentication; auth; vulnerable; vulnerability; change; alter; update TECHNOTE (FAQ)\n\nQUESTION\n The default password does not fulfil corporate security requirements. \n\nCAUSE\nThe default password is blank\n\nANSWER\nLooking into guides for this third party software shows HSQLDB command line capability as being: \n\n * \n * SET PASSWORD\n * \n * \n * SET PASSWORD <password>;\n * \n * \n * Changes the password of the currently connected user. Password must be double quoted. Empty password can be set using \"\".\n\n\nAn example of changing the password in HSQLDB as above by connecting to the database: \n\n * \n * \n * \n * \n * \n\n\nand issuing the command: \n\n * \n\n\nquitting: \n\n * \n\n\nand logging back in with the new password: \n\n * \n * \n * \n * \n * \n\n\nThe above example login uses the default ImpactServer name (NCI) and HSQLDB port number (5435). The default password is blank. \n\nOne will have to edit the HSQLDB DataSource to enable it to connect to the database with the new password. \n\nA) One method is by encrypting the password and editing the HSQLDB DataSource to allow DSA connection. Use nci_crypt to encrypt the password - for example: \n\n * \n * \n * \n\n\nedit the file: \n\n * \n\n\nto alter the property: \n\n * \n\n\nfrom the default value of {aes}9C71E0F544E705326E2B5CBDFC54CE46 to the new encrypted password value - for example: \n\n * \n\n\nThis requires an ImpactServer restart to enable. \n\nB) An alternate method is to edit the DataSource via the normal Impact configuration GUI and provide the new password there. This alternate method has the advantage that one does not need to perform the encryption oneself, nor does one need to manually edit the configuration file and nor does one need to perform an ImpactServer restart to read up the new configuration into the memory resident database that is the ImpactServer."}]},{"id":"TRAIN_Q538","question":"Is ITCAM Data Collector for WebSphere 7.2.0.0.14 available?\n\nIs ITCAM Data Collector for WebSphere 7.2.0.0.14 available? ","answer":"7.2.0.0.14 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0014&includeSupersedes=0&source=fc] March 9, 2017","is_impossible":false,"contexts":[{"filename":"swg21653030.txt","text":"Title: IBM ITCAM Data Collector for WebSphere V7.2 fixes - United States\n\nText:\n FIX README\n\nABSTRACT\n IBM Tivoli Composite Application Manager Data Collector for WebSphere V7.2 fixes \n\nCONTENT\nInstallation Instructions \nRefer to the README file located in Fix Central for additional information \n\n\n\nDownload \nWhat is Fix Central? [http:\/\/www.ibm.com\/support\/fixcentral\/help?page=swfaqs] RELEASE DATE APAR numbers 7.2.0.0.15 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0015&includeSupersedes=0&source=fc] April 17, 2018 PI12540 PI66965 PI70320 PI72648 PI78728 PI78731 PI79097 PI81694 PI83644 PI83841 PI84543 PI86304 PI86589 PI87809 PI87994 PI88830 PI91448 PI92916 PI92459 PI93985 PI94733 PI94742 PI95349 PI95968 7.2.0.0.14 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0014&includeSupersedes=0&source=fc] March 9, 2017 IV85603 PI05433 PI67994 PI52132 PI52407 PI71243 PI22174 PI71124 PI22832 IV88814 IV88264 IV84761 IV84209 7.2.0.0.13 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0013&includeSupersedes=0&source=fc] May 6, 2016 PI48106 PI53964 PI41634 PI53691 PI52367 PI51119 PI57148 PI59839 PI42952 PI39907 PI42603 7.2.0.0.12 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0012&includeSupersedes=0&source=fc] Jan 6, 2016 PI30133 PI35027 PI35893 PI34945 PI39525 PI43321 PI48106 PI53964 PI41634 PI53691 7.2.0.0.11 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0011&includeSupersedes=0&source=fc] Apr 21, 2015 PI11450 PI16745 PI18682 PI21062 PI24319 PI25035 PI25663 PI27187 PI33891 PI34061 PI35680 PI36215 PI37162 PM70256 PM74078 PM75193 PM75581 PM87883 PM93570 IV47342 IV69645 7.2.0.0.10 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0010&includeSupersedes=0&source=fc] Oct 8, 2014 PM98778 PI06311 PI07084 PI22743 PI08200 PM88373 PM99070 PM94101 IV47342 PI06761 PI08473 PI08257 7.2.0.0.9 This is Limited Availability Interim Fix. Please contact Customer Support to obtain this fix . 7.2.0.0.8 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0008&includeSupersedes=0&source=fc] Oct 18, 2013 PM93570 7.2.0.0.7 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0007&includeSupersedes=0&source=fc] Oct 18, 2013 7.2.0.0.6 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0006&includeSupersedes=0&source=fc] Oct 18, 2013 PM88373 7.2.0.0.5 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0005&includeSupersedes=0&source=fc] Oct 18, 2013 7.2.0.0.4 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0004&includeSupersedes=0&source=fc] Oct 18, 2013 PM81890 PM79101 PM80120 PM88932 PM76203 7.2.0.0.3 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0003&includeSupersedes=0&source=fc] Oct 17, 2013 PM82318 7.2.0.0.2 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAM_DC-IF0002&includeSupersedes=0&source=fc] Oct 17, 2013 PM77662"}]},{"id":"TRAIN_Q539","question":"Why is Installation Manager hanging during install. The install screen just clocks forever with no errors.\n\nI am trying to Install Installation Manager 1.6.1 (64 bit) on RHEL 6.6.\n\nOur System Admin Has confirmed that all required RPMs are installed . Taken few javacores and they show following thread as hung :\n\n3XMTHREADINFO \"main\" J9VMThread:0x00007F4C500AD000, j9thread_t:0x00007F4C50053B60, java\/lang\/Thread:0x00007F4C2A1E4410, state:CW, prio=63XMTHREADINFO1 (native thread ID:0x2BFB, native priority:0x6, native policy:UNKNOWN)3XMTHREADINFO2 (native stack address range from:0x00007F4C56D40000, to:0x00007F4C57741000, size:0xA01000)3XMTHREADINFO3 Java callstack:4XESTACKTRACE at org\/eclipse\/swt\/internal\/gtk\/OS._gtk_enumerate_printers(Native Method)4XESTACKTRACE at\n...\nESTACKTRACE at com\/ibm\/cic\/common\/ui\/internal\/views\/AbstractCicWizardView.setWizard(AbstractCicWizardView.java:666)\n\nHow do I resolve the problem ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q540","question":"CR is not inserted for textarea using IE\n\nWe are using IBM Case Manager 5.2.1.4 and IBM Content Navigator 2.0.3.7. Using Properties View Designer of Case Builder, we tried to input CR (\"Enter\") on the text area, but CR is not inserted. This issue occurs only on IE, not on Firefox or Chrome. ","answer":"PJ44413 (IBM Case Manager users) When using Internet Explorer v11, the carriage return does not start a new line in a text area. \nWith this fix, the new line is created.","is_impossible":false,"contexts":[{"filename":"swg27049061.txt","text":"Title: IBM Fix list for IBM Content Navigator Version 3.0.0 - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n The following table contains the complete listing of fixes for Version 3.0.0. \n\nCONTENT\nAPARs fixed in IBM Content Navigator Version 3.0.0 \n\nAPAR Description IO24490 (IBM FileNet P8 users) When EDS is used to hide workflow properties in the in-basket filter, moving the input focus through each visible workflow property field with the tab key causes a null script error when the next field is hidden. This also causes the input focus to stop moving to the next visible field.\nWith this fix, the tab key moves the input focus through each of the visible fields. IO24492 (IBM Content Navigator for Microsoft Office users) When the LTPA token times out, the SSO Kerberos does not recover.\nWith this fix, the user connection is reestablished. IO24514 (IBM Content Manager users) Child attribute values are not exported with the other attributes. [https:\/\/cmdtsweb4.usca.ibm.com:9449\/jazz\/resource\/itemName\/com.ibm.team.workitem.WorkItem\/84947] \nWith this fix, the child attributes and the values are exported. IO24539 (IBM FileNet P8 users) When criteria are entered into the workflow in-basket filter, pressing the Enter key does not close the filter dropdown and apply the filter criteria.\nWith this fix, the Enter works as expected. IO24544 (IBM CMIS for Content Manager users) Administrators must restart CMIS after modifying the Content Manager data model for users to see the changes.\nWith this fix, the Content Manager configuration cache is cleared and the data model changes now appear. IO24653 (IBM Content Navigator for Microsoft Office users) Users are unable to select a different document class when adding an email from Outlook.\nWith this fix, users can change the document model class. IO24710 (IBM FileNet P8 users) When users attempt to download documents with the Download All action and the user does not have permission to open all of the documents, the user receives an error.\nWith this fix, the user receives a friendly error message that the user does not have sufficient permissions. IO24711 (IBM FileNet P8 users) After editing the properties of multiple documents or folders that have an entry template, the reference to the entry template is lost after changes are saved.\nWith this fix, the entry template information is retained. IO24745 (IBM FileNet P8 users) The annotateEdit HTML parameter is set to true but annotation editing remains enabled.\nWith this fix, the annotateEdit parameter disables annotation editing. IO24752 (IBM Content Navigator for Microsoft Office users) When the locale is set to a RTL orientation, some choice lists remain set to LTR.\nWith this fix, the choice list option orientation is set correctly. IO24757 (IBM CMIS for Content Manager users) When files of 0 byte length are encountered, the document id is not retrieved.\nWith this fix, the document id, cmis:contentStreamId, is available in the response metadata when using IBM Content Manager Search API. IO24759 (IBM Content Navigator users) When using the sample feature, the \u2018Get Next\u2019 button does not work.\nWith this fix, the \u2018Get Next\u2019 button retrieves the next document. IO24765 (IBM FileNet P8 users) When a search returns more than the maximum count of items, the count displays as 0.\nWith this fix, the message will reflect that the maximum count was exceeded. IO24777 (IBM CMIS for FileNet users) [https:\/\/cmdtsweb4.usca.ibm.com:9449\/jazz\/resource\/itemName\/com.ibm.team.workitem.WorkItem\/84806]CMIS logs an error that parsing runtime descriptor failed.\nWith this fix, the error is no longer logged. IO24779 (IBM Content Manager users) Users are unable to select the role when adding users or groups to a search, teamspace, or entry template role in a repository configuration.\nWith this fix, the role can be selected. IO24784 (IBM Content Navigator users) Themes can not be saved. \nWith this fix, themes can be saved. IO24789 (IBM Content Navigator users) New inheritance security is not set to include document access rights for Owner, Author and Reader.\nWith this fix, the default document access rights are corrected. IO24790 (IBM Content Manager users) Users are unable to retrieve a worklist containing a very large number of work items. \nWith this fix, the worklist will display the list of work items. IO24791 (IBM Content Navigator users) Some TIFF images compressed in JPEG only shows a partial image preview.\nWith this fix, the complete image can be previewed. IO24803 (IBM Content Manager OnDemand users) Users can not sort a field containing a mapping in the OnDemand application group. \nWith this fix, the column can be sorted. IO24804 (IBM FileNet P8 users) For documents with replication mapping set as inbound only, all annotations appear to save without any error message but only the first annotation is saved with the content.\nWith this fix, the annotations are saved correctly. IO24807 (IBM Content Navigator users) The default desktop load fails if there are references to menu actions in a disabled plug-in.\nWith this fix, the default desktop will load and ignore the references to the disabled plugin. IO24808 (IBM FileNet P8 users) Text searches with a phrase containing a reserved word like \"and\" generates the wrong query.\nWith this fix, the query is generated correctly. IO24813 (IBM Content Manager uses) Some annotations created using other clients are not correctly displayed in the Daeja Virtual Viewer.\nWith this fix, the annotations are displayed correctly. IO24821 (IBM CMIS for FileNet users) The CMIS documentation for the allowedRepositories configuration property should have values separated by spaces.\nWith this fix, the documentation is corrected. IO24822 (IBM Content Navigator for Microsoft Office users) The Send file as link action removes custom subject.\nWith this fix, the custom subject setting is used. IO24825 (IBM Content Navigator users) The Move to folder action in the context menu is not working from within a teamspace when over 400 teamspaces exist.\nWith this fix, the action performs as expected. IO24826 (IBM Content Manager users) The work item list is not updated with the current owner after the work item owner has been changed and the item has been processed to the next step.\nWith this fix, the work item list is updated. IO24830 (IBM Content Navigator users) After viewing a document with the applet viewer, an error is found in the log: SRVE0190E: File not found: \/applets\/DropDown.gif\nWith this fix, the error does not occur. IO24831 (IBM Content Navigator users) Download All action should download all parts as a zip file when multiple documents are selected. IO24836 (IBM Content Navigator users) If the session expired login dialog is cancelled, the user is not logged out and the session is not expired.\nWith this fix, the user session is expired when Cancel is selected. IO24846 (IBM Content Navigator users) Change language and locale settings dialog do not display. \nWith this fix, the settings dialog appears. IO24847 (IBM Content Navigator for Microsoft Office users) After adding columns to the results list and the user selects to sort, the original list of columns is displayed.\nWith this fix, the updated list of columns is displayed for the sorted results. IO24861 (IBM Content Navigator for Microsoft Office users) When using drag-and-drop to add documents to a teamspace with multiple entry templates defined, if the user selects a different template there is an error message about folder selection.\nWith this fix, the folder selection is not lost so the error message does not appear. IO24865 (IBM Content Manager users) When a user tries to view the next or previous document in the list from the Daeja ViewONE Virtual viewer with the Properties pane open, the viewer hangs.\nWith this fix, the issue is resolved. IO24869 (IBM Image Service users) Users are unable to view federated annotations from Image Services.\nWith this fix, users can view the federated annotations. IO24871 (IBM Content Navigator users) The version of the document added to the Favorites list is not the same version opened.\nWith this fix, the same version that was added to the list is the same one opened. IO24880 (IBM Content Navigator users) When adding a document by clicking Add Document Using Entry Template, the repository root folder is automatically selected in the Save in field, and an error message is displayed if the logged in user does not have permission to save the document under the root folder.\nWith this fix, the repository root folder is not automatically selected. IO24883 (IBM Content Manager users) Some TIFF files can not be viewed when using the Content Manager applet viewer.\nWith this fix, the documents can be viewed. IO24884 (IBM Content Navigator for Microsoft Office users) When the results list is displaying the contents of a folder , users can not refresh the results.\nWith this fix, the folder contents can be refreshed. IO24886 (IBM Content Navigator for Microsoft Office users) For Content Manager user, if the name property is a string:ext type, the name does not appear. \nWith this fix, the name property is used for the document title. IO24909 (IBM Content Navigator users) When a multi-line value is first displayed in an entry template property layout text area field, the complete value is not displayed. The text area field does not resize to display the full value until the input focus enters the text area field.\nWith this fix, the text area displays the value as expected. IO24944 (IBM Content Manager users) Navigator does not allow a user to change the class of a document with content to another class if the user does not have permission to add content to the target class. IBM Content Manager does not require the permission to add content to the target class.\nWith this fix, the user can change the class. IO24949 IBM Content Manager OnDemand users) Decimal numbers are not sorted properly when the server is set to a locale that uses a comma to indicate the decimal place, i.e., French.\nWith this fix, decimal numbers are sorted properly. IO24952 (IBM Content Navigator users) In a load balanced environment, if the client IP address for a request changes for an active session, the application executes an invalid DNS look up for each request after the client IP address change which can add a significant delay to the time it takes to process each request.\nWith this fix, the invalid DNS look up is not executed. IO24953 (IBM Content Navigator for Microsoft Office users) When uploading a document, the user can manipulate the upload path and save documents in a restricted folder.\nWith this fix, the user to limited to folders they have permissions for. IO24965 (IBM FileNet P8 users) Sometimes adding the related child document fails.\nWith this fix, the child document provides an error that document import failed. IO24972 (IBM Content Manager users) When using a layout and a dependent property is linked to a foreign key, the dependent property is not displaying the default foreign key values when the parent property value changes.\nWith this fix, the foreign key default choices are updated properly as the user changes the parent property value. IO24973 (IBM Content Navigator users) When using the Paste action from the context menu to paste the password into the Password field, the login button is not enabled. \nWith this fix, the Paste action enables the Add button. IO24985 (IBM Content Navigator for Microsoft Office users) Users can not install on Windows 10 if .Net 4.6.2 is already installed.\nWith this fix, users can install on Windows 10. PJ44290 (IBM Collaboration Services users) When the document name is renamed with an extension, the first content element is not displayed as expected. Instead the user is prompted to download the content element as a document with the same extension. \nWith this fix, the content is downloaded with the correct extension. PJ44413 (IBM Case Manager users) When using Internet Explorer v11, the carriage return does not start a new line in a text area. \nWith this fix, the new line is created. PJ44420 (IBM CMIS for FileNet users) With CMIS v1.1, the \"query\" and \"unfiled\" links are throwing an error.\nWith this fix, the links do not cause an error."}]},{"id":"TRAIN_Q541","question":"Cognos Workspace Advanced Users are unable to see features. Why?\n\n\n\nCertain Workspace Advanced users cannot open Report Studio. This happens with certain custom roles.\n\nEnvironment: IBM Cognos 10.2.2.x","answer":"Based on the following steps the group or role will only have access to either Cognos Workspace (Business Insight) or Cognos Workspace Advanced (Business Insight Advanced). Even though the Role receives Traverse and Execute permissions for the Report Studio capability it will not be able to open Report Studio (this is only possible if you have Traverse and Execute permissions for the Professional User Interface Profile).","is_impossible":false,"contexts":[{"filename":"swg21593254.txt","text":"Title: IBM How to create a custom group\/role for Cognos Workspace and\/or Cognos Workspace Advanced - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document will explain the steps necessary to create a group or role within the Cognos Namespace that can be used to assign only rights for Cognos Workspace Advanced and\/or Cognos Workspace (or as they were formerly known in 10.1.1 \/ 10.1 Business Insight Advanced and\/or Business Insight.). \n\nCAUSE\nIBM Cognos Licensing might require a Group of Users to be able to only access Cognos Workspace or Cognos Workspace Advanced (Business Insight or Business Insight Advanced).\n\nENVIRONMENT\nIBM Cognos Installation with Cognos Workspace (Business Insight) and Cognos Workspace Advanced (Business Insight Advanced).\n\nRESOLVING THE PROBLEM\nBased on the following steps the group or role will only have access to either Cognos Workspace (Business Insight) or Cognos Workspace Advanced (Business Insight Advanced). Even though the Role receives Traverse and Execute permissions for the Report Studio capability it will not be able to open Report Studio (this is only possible if you have Traverse and Execute permissions for the Professional User Interface Profile).\n\n\n\n\n\nFirst create your group or role in the Cognos Namespace: \n\n1. Launch IBM Cognos Administration \n\n2. Select the Security Tab \n\n3. Choose Users, Groups and Roles \n\n4. Click on the Cognos namespace. \n\n5. Click \"New Role\" or \"New Group\" \n\nThen you will have to apply the following settings:\nR=Read\nT=Traverse\nW=Write\nX=Execute \n\nPermissions on Capabilities [Cognos Administration->Capabilities]:\nCognos Viewer: TX\nRun With Options: TX\nCollaborate: TX\nExecutive Dashboard: TX\nExecutive Dahsboard -> Use Advanced Dashboard Features: TX (10.2.x and Up)\nExecutive Dahsboard -> Use Interactive Dashboard Features: TX (10.2.x and Up)\nReport Studio: TX\nScheduling: TX\nWatch Rules: TX\n\nReport Studio Profiles: TX [This is \"set properties\" directly on Security Tab->User Interface Profiles]\nExpress: TX [This is below User Interface Profiles]\n\nPermissions:\nPublic Folders: RTWX\nExpress Authors (on itself): RTX [Replace this with your Group located in Cognos Administration->Security tab->Users,Groups,Roles->Cognos-><your Express Group>]\n\nTo remove the Group\/Role access to Cognos Workspace (Business Insight) do the following access:\nCognos Administration->Security Tab->Capabilities->Executive Dashboards (Cognos Workspace\/Business Insight)->Set Properties \nYour group\/role then receives deny on Traverse and Execute. \n\nTo remove the Group\/Role access to Cognos Workspace Advanced (Business Insight Advanced) do the following:\nCognos Administration->User Interface Profiles->Drop Down Symbol next to Express->Set Properties\nSelect your group and change Traverse and Execute to Deny.\n\nYou can create unique Groups\/Roles to cater to every requirement separately."}]},{"id":"TRAIN_Q542","question":"Where to find the recommended fixes for WebSphere and Portal ?\n\nWhere to find the recommended fixes for WebSphere and Portal ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q543","question":"RHEL7.2: CF servers crashed when db2cluster -cm -list -alert command issued\n\nEnvironment: DB2 11.1 GA \/ RHEL7.2\n\nWhenever I execute \"db2cluster -cm -list -alert\", 0x80090030 logged in db2diag.log on member nodes. Finally CF servers become STOPPED status with high probability.\n\n 2016-09-12-15.51.35.731323+540 I362836576E602 LEVEL: Severe \n PID : 22991 TID : 70366596624816 PROC : db2sysc 0 \n INSTANCE: db2inst1 NODE : 000 DB : SAMPLE\n HOSTNAME: pscale00.ibm.com \n EDUID : 112 EDUNAME: db2LLMn2 (SAMPLE) 0 \n FUNCTION: DB2 UDB, RAS\/PD component, pdLogCaPrintf, probe:876 \n DATA #1 : <preformatted> \n NotifyConn_t.wait (PsGetNotification:) failed: 0x80090030 \n DATA #1 : <preformatted> \n If a CF return code is displayed above and you wish to get \n more information then please run the following command: \n \n db2diag -cfrc <CF_errcode> ","answer":"Add the following setting to file \/etc\/systemd\/logind.conf\nRemoveIPC=no","is_impossible":false,"contexts":[{"filename":"swg21681093.txt","text":"Title: IBM Known Issues for DB2 on Linux - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What are known issues on Linux platforms related to DB2\u00ae database products ? \n\nANSWER\nKnown Issues with DB2 on Linux \n\n[\/support\/docview.wss?uid=swg21681093&aid=1]\nBug ID [\/support\/docview.wss?uid=swg21681093&aid=2]Description\nLinux Flavor [\/support\/docview.wss?uid=swg21681093&aid=3]\nComments 1076574 DB2's 'db2syc' process exhibits memory leak. Redhat v6 DB2 'db2sysc' process will see memory leak. Eventually, RAM and swap will be 100% consumed. The machine will be non-responsive. This memory is released when DB2 engine is stopped with 'db2stop'.\n\nThis is a RedHat Linux issue and is discussed here:https:\/\/access.redhat.com\/support\/cases\/01054560\/ [https:\/\/access.redhat.com\/support\/cases\/01054560\/] \n\nThis problem is already fixed by RedHat. The detailed description of all the Redhat Linux versions affected by this bug and fix details are available at:https:\/\/rhn.redhat.com\/errata\/RHBA-2014-0470.html [https:\/\/rhn.redhat.com\/errata\/RHBA-2014-0470.html] 1042807 32-bit applications running on 64-bit platforms where issuing msgrcv with -ve message type hangs with error: \nerror: msgrcv: No message of the desired type. Redhat v7\nkernel-3.10.0-54.0.1.e17.x86_64 32-bit application does not work on RHEL 7.0 with 64-bit DB2 engine. When the sample programs under sqllib\/samples\/c\/ like inattach.c or dbinfo.c is compiled by bldapp with BITWIDTH=32, it hangs in sqlorqueInternal.\n\nThis is a RedHat Linux issue and is discussed here:\nhttps:\/\/access.redhat.com\/solutions\/1202773 [https:\/\/access.redhat.com\/solutions\/1202773]\n\nThis problem will be fixed by RedHat in v7.1 1264533 DB2 Panic, due to removed IPC resources. Redhat v7.2 The problem is caused by logind removing IPC resources owned by user when this user logs off. The bug is described here:\nhttps:\/\/bugzilla.redhat.com\/show_bug.cgi?id=1264533 [https:\/\/bugzilla.redhat.com\/show_bug.cgi?id=1264533]\n\nLocal Fix:\nAdd the following setting to file \/etc\/systemd\/logind.conf\nRemoveIPC=no 948149 db2dart reports incorrect container tag for container which resides on XFS SLES 12 This problem exists for XFS and only if container is opened in Direct IO mode. In reality the container tag is not corrupted but result buffer will return empty after pread call, which did not report any errors. More information here:\nhttps:\/\/bugzilla.linux.ibm.com\/show_bug.cgi?id=131069 [https:\/\/bugzilla.linux.ibm.com\/show_bug.cgi?id=131069] \n\nThe problem is fixed in \nkernel-default-3.12.32-33.1.x86_64.rpm\n\n1165277 db2 local connections may hang in semop function Redhat\/CentOS v6.6. The problem is caused by a IPC bug, first seen in kernel kernel 2.6.32-434.el6. More information here: https:\/\/bugzilla.linux.ibm.com\/show_bug.cgi?id=119049 [https:\/\/bugzilla.linux.ibm.com\/show_bug.cgi?id=119049]\n\nFixed in https:\/\/rhn.redhat.com\/errata\/RHSA-2015-1272.html [https:\/\/rhn.redhat.com\/errata\/RHSA-2015-1272.html]\n\nLocal Fix:\nConfigure local clients' connections through TCP\/IP loopback."}]},{"id":"TRAIN_Q544","question":"Unable to login to TEP with TEPS LDAP authentication\n\nTEPS LDAP has been configured correctly. User id can be searched successfully in eWAS.\n\nThe login appears to be attempting to authenticate with the HUB TEMS rather than going through Websphere to contact the LDAP server.","answer":"remove the TEPS variable 'KFW_AUTHORIZATION_USE_EWAS' from the KFWENV, then restart the TEPS and verify that all users can log in.","is_impossible":false,"contexts":[{"filename":"swg21688718.txt","text":"Title: IBM TEP Login is failing for some LDAP users - United States\n\nText:\nKFW_AUTHORIZATION_USE_EWAS; TEPS; Login ; LDAP ADO; status 1021 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The TEPS is configured to use LDAP (e.g. Microsoft Active Directory ) for user authentication.\nSome LDAP user are able to login successfully, but some users are not able to login, why? \n\nSYMPTOM\nFor some users that try to log into the TEPS, the following error is seen: \n\n\"KFWITM393E User ID or password is invalid\" \n\n \n\nThe TEPS logs shows the error:\nKFW1002I Starting Service: 'Startup Complete v2.0' (Thursday, August 28, 2014, 3:12:36 PM-{252C}ctserver.cpp,520, \"CTServer::startServerDll\") KFW1003I Started Service: 'Startup Complete \nv2.0' (Thursday, August 28, 2014, 3:12:36 PM-{4D4}ctserver.cpp,975, \n\"CTServer::runORB\") KFW1020I ********* Waiting for requests. Startup complete ********* \n(Thursday, August 28, 2014, 3:13:30 PM-{51C}kdssqrun.c,964,\"CreatePath\") Create Path Error. status 1021 path NCS: \n\n\nCAUSE\nThe TEPS variable 'KFW_AUTHORIZATION_USE_EWAS' \n\n\nRESOLVING THE PROBLEM\nPlease remove the TEPS variable 'KFW_AUTHORIZATION_USE_EWAS' from the KFWENV, then restart the TEPS and verify that all users can log in.\n\n\n\nPRODUCT ALIAS\/SYNONYM\n ITM\nMonitoring"}]},{"id":"TRAIN_Q545","question":"Netcool\/Impact 6.1.0: SelfMonitoring events are being incorrectly cleared by OMNIbus GenericClear Automation\n\nNetcool\/Impact 6.1.0: SelfMonitoring events are being incorrectly cleared by OMNIbus GenericClear Automation\n\nWhen there are multiple SelfMonitoring events reporting stopped Impact Services and one of those Impact Services is restarted the resolution event is used by the OMNIbus GenericClear (and DeleteClears) Automations to delete ALL the events. ","answer":"The easy solution at this time is to upgrade to Fix Pack 1 or higher. One could go to the extremes of creating a PolicyActivator, polling at a higher rate than the GenericClear Automation, to run a Policy to pick-up these events, pull out the Service name from the Summary field and append it to the Agent field of the events so that the GenericClear Automation can uniquely identify and correlate Problem and Resolution events.","is_impossible":false,"contexts":[{"filename":"swg21579319.txt","text":"Title: IBM SelfMonitoring events incorrectly cleared - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; 610; self; monitoring; selfmonitoring; service; event; events; problem; resolution; clear; clears; generic; genericclear; delete; deleteclears; automation; object; server; objectserver; objserv; nco; omnibus TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n All SelfMonitoring Service problem (Service stopped) events are cleared by GenericClear if any single resolution (Service started) event is created \n\nSYMPTOM\nA Service is stopped and a SelfMonitoring (problem) event is sent to the ObjectServer. \n\nAnother Service is stopped and that too creates a SelfMonitoring (problem) event in the ObjectServer.\n\nThe second Service is then restarted and SelfMonitoring sends a resolution (Service started) events to the ObjectServer and this results in BOTH Service stopped events being set to Severity 0.\n\n\n\nCAUSE\nSelfMonitoring Service events do not include any details of the Service in question in the fields used by the GenericClear Automation in the ObjectServer to uniquely identify and correlate Problem and Resolution events - so any single SelfMonitoring Service Resolution event will correlate with ALL SelfMonitoring Service Problem events and set the Severity to 0 for the DeleteClears Automation to mop up. \n\n\n\n\n\nDIAGNOSING THE PROBLEM\nSelfMonitoring Service events for known stopped Services are vanishing when they shouldn't. \n\n\n\n\n\nRESOLVING THE PROBLEM\nThe easy solution at this time is to upgrade to Fix Pack 1 or higher. One could go to the extremes of creating a PolicyActivator, polling at a higher rate than the GenericClear Automation, to run a Policy to pick-up these events, pull out the Service name from the Summary field and append it to the Agent field of the events so that the GenericClear Automation can uniquely identify and correlate Problem and Resolution events. \n\n\nThis problem is recorded by APAR IV13297 \"ALERTKEY VALUE FOR SELFMONITORING (SERVICE) EVENTS DOES NOT INCLUDE SERVICE DETAILS, SO GENERICCLEAR CLEARS ALL SUCH EVENTS.\" [link below] and is fixed in IBM Tivoli Netcool\/Impact V6.1.0 Fix Pack 1 (6.1.0-TIV-NCI-FP0001) [link below] and above.\n\n\nRELATED INFORMATION\n APAR IV13297 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IV13297]\n6.1.0-TIV-NCI-FP0001 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24031658]"}]},{"id":"TRAIN_Q546","question":"Does @LocalNodeAlias=\"\" will affect ITNM failover health check events?.\n\nCustomization in nco_p_monitor.rules with @LocalNodeAlias=\"empty\", after that both Primary and Backup started health check fail event, how to resolve that. ","answer":"The value for m_Domain is taken from the value for Node (@Node) in alerts.status for the health check event. If you have altered the inserted value for @Node, either by modifying the nco_p_ncpmonitor.rules file or by some other method such as an Automation or Impact policy, then the resulting update for state.domains will fail. Ensure that the rules governing the modification of @Node allow for the value of @Node to remain unchanged for health check events.","is_impossible":false,"contexts":[{"filename":"swg21424808.txt","text":"Title: IBM Health Check events Node and Domain and their interactions. - United States\n\nText:\nHealthCheck failed events; nco_p_ncpmonitor.rules; VirtualDomain TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n HealthCheck failed events are being received, nco_p_ncpmonitor.rules has been customized. \n\nSYMPTOM\nAlthough both the Primary and Backup domains are up and (according to their mutual VirtualDomain processes) are healthy, each is sending Health Check Failed events for the other domain.\n\n\nCAUSE\nThis document only applies to those installations where the nco_p_ncpmonitor.rules file has been edited to modify the inserted value for @Node in alerts.status or where @Node is being modified for health check events by some other external process. \n\nEach ITNM Gateway (ncp_ncogate) in the Primary and Backup domain retrieves health check events from alerts.status and constructs an update into the state.domains table in the VirtualDomain process. Please review the documentation in the 'Related Information' section below for more information on the Health Check process.\n\n\nDIAGNOSING THE PROBLEM\nWhen you run the ncp_ncogate process in debug you can see the update that the gateway makes in state.domains. The value for m_Domain should be the same as the Domain name for the Primary or the Backup domain. It should not be the name of the Virtual domain. \n\n\nProcessHealthCheck sent:update state.domains set m_HealthStatus=1 where m_Domain='ITNM';\n\n\nRESOLVING THE PROBLEM\nThe value for m_Domain is taken from the value for Node (@Node) in alerts.status for the health check event. If you have altered the inserted value for @Node, either by modifying the nco_p_ncpmonitor.rules file or by some other method such as an Automation or Impact policy, then the resulting update for state.domains will fail. Ensure that the rules governing the modification of @Node allow for the value of @Node to remain unchanged for health check events.\n\nRELATED INFORMATION\n#failover [http:\/\/publib.boulder.ibm.com\/infocenter\/tivihelp\/v8r1\/topic\/com.ibm.networkmanagerip.doc_3.8\/itnm\/ip\/wip\/install\/concept\/nmip_ins_failoverop.html]"}]},{"id":"TRAIN_Q547","question":"Do I need to manually apply SDA function for ITCAM for SOA 7.2 FP1 ifix 5?\n\nThe SDA function for ITCAM for SOA 7.2 FP1 ifix 5 works for TEMS but IS NOT coded to work for TEPS. User is required to manually apply the support files on TEPS for this version (ifix 5).\n\ndoes this need a manual apply for TEPS only for SOA 7.2, FP1 and ifix 5 ?\" ","answer":"User has to manually apply SOA 7.2 FP1 ifix 5 support files on TEPS.","is_impossible":false,"contexts":[{"filename":"swg21968518.txt","text":"Title: IBM SDA does not work for TEPS support files on ITCAM for SOA 7.2 FP1 ifix 5 - United States\n\nText:\nSDA TEPS \"support files\" SOA 7.2 FP1 ifix 5 TECHNOTE (FAQ)\n\nQUESTION\n Why is my product support not being updated on TEPS (It's updated on TEMS) - from 7.2.0.1-TIV-ITCAMSOA-AIX-IF0005.tar. \n\nCAUSE\n SOA includes an SDA package for the TEMS but not for TEPS.\n\nANSWER\nBasically, it is working as it is coded for this version. \n\n User has to manually apply SOA 7.2 FP1 ifix 5 support files on TEPS. \n\n Doc Apar IV77933 is created to provide this information. \n\n \n\nNOTE: \nAll version of ITCAM for SOA 7.2 requires to apply support files manually on TEPS. \nNone of the 7.2 installers include SDA support for TEPS. It is not limited to 7.2.0.1-TIV-ITCAMSOA-IF0005."}]},{"id":"TRAIN_Q548","question":"Why does the user receive Notice Sender Execution Failed Alert after upgrading to Atlas 6.0.3.3?\n\nWhy does the user receive Notice Sender Execution Failed Alert after upgrading to Atlas 6.0.3.3? ","answer":"The error message is \"java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01628: max # extents (32765) reached for rollback\" and is caused by MATTERPERFORMER_TEXT","is_impossible":false,"contexts":[{"filename":"swg21982857.txt","text":"Title: IBM User receiving Notice Sender Execution Failed Alert after upgrading to Atlas 6.0.3.3 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why does the user receive Notice Sender Execution Failed Alert after upgrading to Atlas 6.0.3.3? \n\nCAUSE\nThe error message is \"java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1 ORA-01628: max # extents (32765) reached for rollback\" and is caused by MATTERPERFORMER_TEXT\n\nANSWER\n \n\n 1. Backup Atlas Database \n 2. Using sqlplus login to Atlas Database using PSSAPL user \n 3. Run the Following commands in SQL prompt \n 4. EXEC ddl_util.drop_index('MATTERPERFORMER_TEXT'); \n 5. EXEC ddl_util.drop_ctx_pref('MatterPerformer_Pref10G'); \n 6. commit;"}]},{"id":"TRAIN_Q549","question":"What does the end-file-message mean while doing a launchpad.sh in the MS\"\n\nI am getting an end-file-message means while doing a launchpad.sh in the MS. How do I solve the problem?","answer":"Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries.","is_impossible":false,"contexts":[{"filename":"swg21985630.txt","text":"Title: IBM Using launchpad.sh or silent_MS_linux.bin results in end-of-file message. - United States\n\nText:\nITCAM compat-libstdc++ libstdc++ libraries silent_MS_linux.bin launchpad.sh errors TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nPROBLEM(ABSTRACT)\n Using the DC or MS 'launchpad.sh' script results in the following error message:\n.\/setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `\/dev\/null') \n\nSYMPTOM\nThe following error is seen running when doing either 'launchpad.sh' or 'silent_MS_linux.bin': \n\n Initializing InstallShield Wizard........ \nLaunching InstallShield Wizard........ \n\n.\/setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `\/dev\/null') \n\nThe installer is unable to run in graphical mode. Try running the \ninstaller with the -console for -silent flag.\n\n\nCAUSE\nMissing Linux system libraries.\n\n\nENVIRONMENT\nLinux - RHEL6.x and RHEL7.x 64-bit versions.\n\n\n\nRESOLVING THE PROBLEM\nThis error messag is seen because of some missing Linux libraries. Usually what's missing are the compat-libstdc++ or libstdc++ libraries. Usually the 32-bit version is missing. Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries. \n\n\n[\/support\/docview.wss?uid=swg21985630&aid=1] [\/support\/docview.wss?uid=swg21985630&aid=1]\n[\/support\/docview.wss?uid=swg21985630&aid=2] [\/support\/docview.wss?uid=swg21985630&aid=2]\n\n \n\nPRODUCT ALIAS\/SYNONYM\n ITCAM4AD ITCAMfAD ITCAM for App Diagnostics"}]},{"id":"TRAIN_Q550","question":"ITNM is vulnerable to CVE-2017-3523 ?\n\nCustomer would like to know if ITNM versions is vulnerable to CVE-2017-5638? If yes then where we can find the details?. ","answer":"Refer to the following security bulletins for vulnerability details and information about fixes addressed by Oracle MySQL which is shipped with IBM Tivoli Network Manager IP Edition.","is_impossible":false,"contexts":[{"filename":"swg22004767.txt","text":"Title: IBM Security Bulletin: Security vulnerability has been identified in Oracle MySQL shipped with IBM Tivoli Network Manager IP Edition (CVE-2017-3523) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Oracle MySQL is shipped with IBM Tivoli Network Manager IP Edition. Information about a security vulnerability affecting Oracle MySQL has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nRefer to the security bulletin listed in the Remediation\/Fixes section\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Tivoli Network Manager 3.9\n\nREMEDIATION\/FIXES\nRefer to the following security bulletins for vulnerability details and information about fixes addressed by Oracle MySQL which is shipped with IBM Tivoli Network Manager IP Edition. \n\nAffected Product and Version(s) Product and Version shipped as a component Affected Supporting Product Security Bulletin IBM Tivoli Network Manager 3.9 IBM Tivoli Network Manager 3.9 shipped with MySQL Connector 5.6 Oracle Critical Patch Update Advisory - April 2017 [http:\/\/www.oracle.com\/technetwork\/security-advisory\/cpuapr2017-3236618.html] 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 15 June 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."}]},{"id":"TRAIN_Q551","question":"Why am I getting StaleConnectionException on WebSphere side while Oracle is throwing 'OALL8 is in an inconsistent state'?\n\nIn the WebSphere Application Server SystemOut.log file we see this message:\n\nConnectionEve A J2CA0056I: TheConnection Manager received a fatal connection error from the Resource Adapter for resource jdbc\/<data source name>. The exception which was received is com.ibm.websphere.ce.cm.StaleConnectionException: OALL8 is in an inconsistent state:java.sql.SQLException: OALL8 is in an inconsistent state.\nHow can this be resolved?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q552","question":"How to export key from SSL certificate in IBM HTTP Server 7; getting restricted policy error\n\n\n\nWe're trying to export our IHS 7 SSL key to PKCS12 format so we can use it on our Load Balancer, but it fails with some policy error:\n\n $\/usr\/IBM\/HTTPServer\/bin\/gsk7cmd -cert -export -db \/usr\/IBM\/HTTPServer\/ssl\/key.kdb -pw #### -label \"domain1\" -type cms -target \/tmp\/domain1.p12 -target_type PKCS12 -target_pw ####\n \n The command cannot complete because your JRE is using restricted policy files.\n\nSame error happens in Ikeyman tool. Any ideas?","answer":"To resolve the problem, select either option: \n\n * Download and install a later Java 32-bit x86 AMD\/Intel Java SDK from [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=180&uid=swg24023707]the WebSphere Support web site [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24028881] to the IBM HTTP Server java and plug-ins java folder.\n \n \n * Download and install the files from the Unrestricted JCE policy files [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/preLogin.do?source=jcesdk] site.","is_impossible":false,"contexts":[{"filename":"swg21395327.txt","text":"Title: IBM The Key Management Utility bundled with IBM HTTP Server V7.0 32-bit, and the WebSphere Application Server Web server plug-in 32-bit V7.0, displays an error when creating a PKCS12 keystore file - United States\n\nText:\np12; pkcs12; ikeyman; v7.0; Plugin; Plug-in; JCE policy file TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Java version \"1.6.0\" new install with IBM HTTP Server V7.0 and the Web server plug-in V7.0 contains restricted policy files. \n\nSYMPTOM\nAn error message displays when performing the following steps: \n\n 1. Start the Key Management Utility.\n \n \n 2. Select Key Database File > New. For Key database type, select PKCS12 and then click OK.\n \n [\/support\/docview.wss?uid=swg21395327&aid=1]\n \n \n 3. Enter a new password and click OK.\n\n\nThe following error message is displayed: \n\nThe command cannot complete because your JRE is using restricted policy files. \nCAUSE\nRestricted JCE Policy files\n\n\nRESOLVING THE PROBLEM\nTo resolve the problem, select either option: \n\n * Download and install a later Java 32-bit x86 AMD\/Intel Java SDK from [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=180&uid=swg24023707]the WebSphere Support web site [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24028881] to the IBM HTTP Server java and plug-ins java folder.\n \n \n * Download and install the files from the Unrestricted JCE policy files [https:\/\/www14.software.ibm.com\/webapp\/iwm\/web\/preLogin.do?source=jcesdk] site. \n \n After downloading the unrestricted JCE policy files, follow the instructions below to replace the restricted JCE policy files with the unrestricted JCE policy files.\n\n\nInstructions: \n1. Rename and move the restricted JCE Policy files indicated below from the <ihsinst>\/java\/jre\/lib\/security\/ directory to a directory that is outside the JDK class path, extdirs, or bootclasspath. \n\nlocal_policy.jar \nUS_export_policy.jar \n\n2. Next, place the unrestricted JCE policy files in the <ihsinst>\/java\/jre\/lib\/security\/ directory. They should be named local_policy.jar and US_export_policy.jar \n\n3. Finally, restart the ikeyman utility to pick up the unrestricted JCE policy files now located in the security directory \n\nVery Important Note: You will be offered two options to download. See screen shot below. The correct Unrestricted JCE policy files will depend on the JAVA SR version. This can be verified, Run java -version command from the <ihsinst>\/java\/jre\/bin directory. The output will display the Java SR version. \nFor example: Java 1.6..0 version with SR12 \n[\/support\/docview.wss?uid=swg21395327&aid=2] [\/support\/docview.wss?uid=swg21395327&aid=2] \n\n[\/support\/docview.wss?uid=swg21395327&aid=3] [\/support\/docview.wss?uid=swg21395327&aid=3] \n\nReplacing the wrong Unrestricted JCE policy files, when retry to manage a PKCS12 keystore file the ikeyman utility will fail to open.the keystore file reporting the following error. \n\n[\/support\/docview.wss?uid=swg21395327&aid=4] \n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server IBM HTTP Server Windows 7.0.0.5, 7.0.0.3, 7.0.0.1, 7.0"}]},{"id":"TRAIN_Q553","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2014-3566 and CVE-2014-6457)\n\nI need to understand details regarding \"Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2014-3566 and CVE-2014-6457) .\" Where can I find this information? ","answer":"CVEID: CVE-2014-6457 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-6457]\n\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\n\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97148 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97148] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:H\/Au:N\/C:P\/I:P\/A:N) \n\nCVE-ID: CVE-2014-3566 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21903249.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java SDK affect IBM Image Construction and Composition Tool (CVE-2014-3566 and CVE-2014-6457) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 6 that is used by IBM PureApplication System. This also includes a fix for the Padding Oracle On Downgraded Legacy Encryption (POODLE) SSLv3 vulnerability (CVE-2014-3566). These were disclosed as part of the IBM Java SDK updates in October 2014. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2014-6457 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-6457]\n\nDESCRIPTION: An unspecified vulnerability related to the JSSE component has partial confidentiality impact, partial integrity impact, and no availability impact.\n\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97148 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97148] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:H\/Au:N\/C:P\/I:P\/A:N) \n\nCVE-ID: CVE-2014-3566 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-3566]\n\nDESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/97013] 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\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\uf0b7 For\uf020IBM Image Construction and Composition Tool v2.2.1.3 \n\n * \n\n\n\uf0b7 For IBM Image Construction and Composition Tool v2.3.1.0 * \n\n\n\uf0b7 For\uf020IBM Image Construction and Composition Tool v2.3.2.0 * \n\n\n\nIBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 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 15 May 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."}]},{"id":"TRAIN_Q554","question":"DB2 Non Reclaimable Storage .\n\nWe have tablespaces defined under DB2 9.5 that apparently are not able\nto reclaim storage back to the OS. \nIs there a conversion available without reloading the tables?","answer":"Tablespaces migrated from DB2 V9.1\/V9.5 to V9.7 won't get upgraded directly to use the reclaimable storage feature.","is_impossible":false,"contexts":[{"filename":"swg21438047.txt","text":"Title: 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\n\nText:\nSQL1763N; 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]"}]},{"id":"TRAIN_Q555","question":"SPSS free trial not working on MAC - gets stuck in when it should be launching and goes nowhere\n\n\n\nI downloaded the SPSS software on my mac running Yosemite 10.10.5. The trial was activated by IBM, they sent me several emails stating this.\n\nSo I tried to launch the app and get stuck here alt text There is no progress after an hour; and I tried to launch several times, it never gets out of this screen.\n","answer":"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:","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q556","question":"Does DB2 DBMS implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures?\n\nDoes DB2 DBMS implement NIST FIPS 140-2 validated cryptographic modules to provision digital signatures? If so, how can we utilize it?","answer":"No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above. DB2 uses encryption modules which are FIPS 140-2 certified.","is_impossible":false,"contexts":[{"filename":"swg21237078.txt","text":"Title: IBM DB2 UDB Version 8, v10.5 compliance with FIPS 140-2 standard - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Is DB2 v8, v10.5 compliant to FIPS 140-2 ?. \n\nANSWER\n\nIs DB2 v10.5 compliant with FIPS 140-2?\n\nQ: Is DB2 vulnerable to the problem described below?\n\nV-58165 DBMS main in the middle attack [https:\/\/www.stigviewer.com\/stig\/database_security_requirements_guide\/2015-06-23\/finding\/V-58165]\n\n\"One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers based on patterns in identifiers already known. The preferred technique for thwarting guesses at Session IDs is the generation of unique session identifiers using a FIPS 140-2 approved random number generator. However, it is recognized that available DBMS products do not all implement the preferred technique yet may have other protections against session hijacking. Therefore, other techniques are acceptable, provided they are demonstrated to be effective. \"\n\nA: No because DB2 does not use session ids for authentication and thus not vulnerable to the attack described above. DB2 uses encryption modules which are FIPS 140-2 certified.\n\nDB2 v8.x compliancy to FIPS 140-2\n\nDB2 v8.x went out of support in April 2009.\n\nWhat is ICC?\n\nICC (IBM Crypto for C) is a set of libraries from Tivoli\u00ae for performing encryption. As of DB2\u00ae Universal Database\u2122 (DB2 UDB) Version 8 fixpak 7 (equivalent to DB2 UDB Version 8.2), DB2 is using ICC on most platforms.\n\nCustomers who need to operate in an environment that is compliant with FIPS 140-2 federal standard should take into account the releases of ICC that are shipped by DB2 on different platforms and the compliance status of those releases with FIPS 140.2.\n\nFollowing is a list of platforms on which DB2 is using ICC for encryption of data flowing between clients and servers:\n\nDB2 V8 Fixpak 7 through DB2 Fixpak 11: \nICC Version 1.2.2 on platforms:\nAIX 32 bit\nHP-UX PA-RISC 32 bit\nICC Version 1.2.1 on platforms: \nAIX 64 bit\nHP-UX PA-RISC 64 bit\nHP-UX IA64\nLinux x86, Linux x86-64, Linux IA64\nLinux for zSeries\nLinux for POWER\nWindows x86 and IA64\nSolaris SPARC 64 bit\nICC Version 1.3.9 on platforms:\nSolaris x86-64 (DB2 V8.2 GA)\n\nDB2 V8 Fixpak 12 and later: \nICC Version 1.4.1 on platforms \nAIX\nHP-UX PA-RISC\nLinux x86 and x86-64\nLinux for zSeries\nLinux for POWER\nWindows x86 and x86-64\nSolaris SPARC\nICC Version 1.3.9 on platforms \nHP-UX IA64\nLinux IA64\nWindows IA64\n\nSummary of known problems encountered in ICC 1.2.1\/1.2.2:\nThere are a number of issues with DB2 and the ICC encryption libraries at levels prior to 1.3.9. The known problems are: \n\n\n 1. Severe performance problems where processes seem to hang, or take several minutes to run. \n 2. A bug in ICC code causes it to communicate with the OpenSSL EGD (Entropy Gathering Daemon) which under certain circumstances could hang \n 3. ICC symbols have not been namespaced and DB2 can end up with symbol collisions with OpenSSL code. This can also happen when multiple versions of ICC are used within the same process.\n\n\nDB2 Version 8 Fixpak 12 and later incorporates IBM Crypto for C (ICC) version 1.3.9 or 1.4.1 cryptographic module which fixes these problems. \n\n \n\nNote: The latest status of ICC conformance with FIPS 140-2 standard can be obtained by referring to http:\/\/www.ibm.com\/security\/standards\/st_evaluations.shtml [http:\/\/www.ibm.com\/security\/standards\/st_evaluations.shtml]\n\nRELATED INFORMATION\n FIPS PUB 140-2 [http:\/\/csrc.nist.gov\/publications\/fips\/fips140-2\/fips1402.pdf]"}]},{"id":"TRAIN_Q557","question":"How do I resolve a performance issue with my applicaiton running on a DB2 client as a result of low level segement calls issued by DB2?\n\nCurrently experiencing a performance issue with an application running on a DB2 client, the stack traces reveals that multiple segment() calls are being issued by DB2 and they are failing. What can be done to resolve this issue? ","answer":"The solution is to issue the following command at the DB2 client:\n\ndb2trc alloc\n\nThis will then create the necessary IPC resources, and prevent the semget() calls from failing (since the semget() call now has IPC resources that it can use). The potential performance problem will thus be avoided.\n\nThe failed semget() operations are more of a concern for Solaris Operating Environment, Linux\u00ae, HP-UX and AIX\u00ae operating systems, in terms of performance implications. Windows\u00ae will not have this problem due to its specific architecture.\n\nThe db2trc alloc command should be invoked every time the client is restarted, and therefore it is recommended to add this command to a startup script.","is_impossible":false,"contexts":[{"filename":"swg21209523.txt","text":"Title: IBM Application running on a DB2 client performs poorly due to low level semget calls issued by DB2 - United States\n\nText:\ndb2trc alloc; semget TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document provides troubleshooting information for the situation where an application running on a remote DB2 client performs poorly. In particular, it describes a scenario where performance is poor because of failed semget() calls to the operating system.\n\n\nCAUSE\nDB2\u00ae Universal Database\u2122 (DB2 UDB) has an internal trace facility called \"db2trc\". This trace facility acquires Inter Process Communication (IPC) resources (both semaphore and shared memory). Even though a DB2 trace is not turned on, it may issue semget() calls to the operating system. These calls will fail, though, since no IPC resources were acquired.\n\nRESOLVING THE PROBLEM\nThe trace facility has an \"alloc\" option that can allocate necessary IPC resources. When you issue db2start, internal functions equivalent to command db2trc alloc are automatically issued, and when you issue db2stop, the trace segment will be removed if no one is using it.\n\nSince a DB2 client does not necessarily have the ability to perform the db2start command, no IPC's will be automatically allocated for the trace facility, and hence the problem.\n\nThe solution is to issue the following command at the DB2 client:\n\ndb2trc alloc\n\nThis will then create the necessary IPC resources, and prevent the semget() calls from failing (since the semget() call now has IPC resources that it can use). The potential performance problem will thus be avoided.\n\nThe failed semget() operations are more of a concern for Solaris Operating Environment, Linux\u00ae, HP-UX and AIX\u00ae operating systems, in terms of performance implications. Windows\u00ae will not have this problem due to its specific architecture.\n\nThe db2trc alloc command should be invoked every time the client is restarted, and therefore it is recommended to add this command to a startup script.\n\nNote: To determine if the application is issuing semget() calls, the best course of action would be to take a \"truss\". Please read your operating system manuals on how to perform and read a truss.\n\nRELATED INFORMATION\n IC85712 (AIX) [http:\/\/www-01.ibm.com\/support\/docview.wss?crawler=1&uid=swg1IC85712]\nFP5: db2trc command has been improved for clients (Linu [http:\/\/publib.boulder.ibm.com\/infocenter\/db2luw\/v9r7\/topic\/com.ibm.db2.luw.wn.doc\/doc\/c0059466.html]\nv10.5 IT17501 [https:\/\/www-01.ibm.com\/support\/entdocview.wss?uid=swg1IT17501]\nv11.1 IT17518 [https:\/\/www-01.ibm.com\/support\/entdocview.wss?uid=swg1IT17518]"}]},{"id":"TRAIN_Q558","question":"Could UCD import template from ipas?\n\nI am trying to import a template from ipas, UCD seems to be able to retrieve the pattern name after some hints. But I am getting the following Error after clicking the Save button on the import template page:\n\n(WeaverError) handshake alert: handshake_failure (original=handshake alert: handshake_failure, original backtrace=org\/jruby\/ext\/openssl\/SSLSocket.java:170:in\nconnect' file:\/media\/udeploy\/server\/lib\/weaver.jar!\/gems\/httpclient-2.2.7\/lib\/httpclient\/session.rb:300:in\nssl_connect')\n\nUCD is version 6.0.1.3.484576 IPAS is 4.0.0.3-20140404055836 \/ 20140404-0551-458","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q559","question":"Help with Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920)\n\nI need to understand details regarding \"Security Bulletin: Security Vulnerability in IBM PureApplication System (CVE-2015-1920)\". Where can I find this information? ","answer":"CVEID: CVE-2015-1920 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C)","is_impossible":false,"contexts":[{"filename":"swg21964873.txt","text":"Title: IBM Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM PureApplication System contains IBM WebSphere Application Server, which has a security vulnerability that could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1920 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C) \n\nPlease consult the security bulletin: Security Vulnerability in IBM WebSphere Application Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21883573]for additional vulnerability details and information\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V2.1\nIBM PureApplication System V2.0\nIBM PureApplication System V1.1 \n\nREMEDIATION\/FIXES\nThe solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1\n\u00b7 Web Application Pattern Type V2.0.4.2\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc]\n\n\u00b7 Web Application Pattern Type V1.0.4.2\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f]\n\nIBM PureApplication System V2.0 \nThe solution is to upgrade to IBM PureApplication System V2.0.0.1 Interim Fix 5\n\nIBM PureApplication System V1.1 and earlier:\nContact IBM customer support for upgrade options.\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 19 August 2015: Original Version Published\n11 September 2015 Updated for IBM PureApplication System v2.0 \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."}]},{"id":"TRAIN_Q560","question":"What are the known issues with WILY software and WAS or BPM?\n\n\n\nWhat are the known issues with WILY software and WAS or BPM?","answer":"If you are using CA Wily Introscope to monitor performance in the same environment with IBM Business Process Manager, you might receive messages that a user session has expired. Before you can continue working on IBM BPM, you must log out and log in again.","is_impossible":false,"contexts":[{"filename":"swg21966881.txt","text":"Title: IBM Business Process Manager users receive errors that session has expired - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n If you are using CA Wily Introscope to monitor performance in the same environment with IBM Business Process Manager, you might receive messages that a user session has expired. Before you can continue working on IBM BPM, you must log out and log in again. \n\nCAUSE\nWebSphere Application Server has session security integration enabled by default. Enabling this feature guards against the possibility of session data being hijacked by another user. \nThe Wily Introscope agent might try to access an active user session to monitoring purposes. Because Wily does not have the same authenticated user, the session security integration feature prevents Wily from accessing that user session. \n\nBy having a custom property named InvalidateOnUnauthorizedSessionRequestException set to true, the session manager will invalidate the active user session. This causes the \"session expired\" messages for the IBM BPM user. (The default value for InvalidateOnUnauthorizedSessionRequestException is false.)\n\n\nDIAGNOSING THE PROBLEM\nTo verify you have this problem, you can turn on tracing for the Web container, the session, security, and IBM BPM using these tracing strings: \n\n\n*=info:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:com.ibm.ws.session.*=all:com.ibm.ws.security.*=all:com.ibm.websphere.security.*=all:com.ibm.websphere.wim.*=all:com.ibm.wsspi.wim.*=all:com.ibm.ws.wim.*=all:WLE.*=all \n\nYou might see entries in the stack trace similar to the following lines:\n\nat com.wily.introscope.agent.servlethelper.ServletRequestHelper.getSession(ServletRequestHelper.java:286)\nat com.wily.introscope.agent.servlethelper.ServletRequestHelper.get(ServletRequestHelper.java:513)\nat com.wily.introscope.agent.trace.hc2.HttpServletLazyMapProvider.get(HttpServletLazyMapProvider.java:63)\nat com.wily.util.adt.LazyMap.get(LazyMap.java:182)\nat com.wily.introscope.agent.trace.hc2.HttpServletLazyMap.putAllParameters(HttpServletLazyMap.java:191)\nat com.wily.introscope.agent.trace.hc2.HttpServletTracer.IInvocationDataParameterCallback_addParameters(HttpServletTracer.java:782)\nat com.wily.introscope.agent.trace.InvocationData.addParameterCallbacks(InvocationData.java:3486)\nat com.wily.introscope.agent.feature.VirtualStackFeatureHelper.fillComponentParams(VirtualStackFeatureHelper.java:157)\nat com.wily.introscope.agent.feature.VirtualStackFeatureHelper.getTransanctionSnapShotFromInvocationData(VirtualStackFeatureHelper.java:235)\nat com.wily.introscope.agent.feature.VirtualStackFeatureHelper.getTransactionSnapshotFromStack(VirtualStackFeatureHelper.java:75)\nat com.wily.introscope.agent.feature.StallFeatureBase.reportStall(StallFeatureBase.java:50)\nat com.wily.introscope.agent.feature.StallCheckBehaviorCorrect.ITimestampedRunnable_execute(StallCheckBehaviorCorrect.java:61)\nat com.wily.util.heartbeat.IntervalHeartbeat$BehaviorNode.execute(IntervalHeartbeat.java:972)\nat com.wily.util.heartbeat.IntervalHeartbeat.executeNextBehaviorAndCalculateSleepTime(IntervalHeartbeat.java:491)\nat com.wily.util.heartbeat.IntervalHeartbeat.access$2(IntervalHeartbeat.java:445)\nat com.wily.util.heartbeat.IntervalHeartbeat$HeartbeatRunnable.run(IntervalHeartbeat.java:668)\nat java.lang.Thread.run(Thread.java:784)\n\n\n\nRESOLVING THE PROBLEM\nTo prevent the sessions from expiring, choose one of the following options: \n\n * Stop the Wily agent. \n * Remove the custom property InvalidateOnUnauthorizedSessionRequestException=true by completing the following steps: 1. Log in to the administrative console. \n \n 2. Click server_name > Session Manager > Custom properties. \n \n 3. Select the InvalidateOnUnauthorizedSessionRequestException property, which is set to true, and delete it.\n The purpose of this setting in BPM default configuration is to \"gracefully\" terminate existing sessions and create new sessions in shared browser scenarios. With this setting removed, you may see temporary exceptions in cases two users share the same browser instance and try to switch identity without closing the browser in between. \n \n 4. Click Apply and then save the master configuration. \n \n 5. Restart the servers. \n \n \n * Disable specific Wily configurations that reuse the session IDs from existing users.\n\nRELATED INFORMATION\n CA Technologies: Session killed by agent heartbeat [http:\/\/www.ca.com\/us\/support\/ca-support-online\/product-content\/knowledgebase-articles\/tec1314663.aspx]\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard AIX, Linux, Solaris, Windows 8.5.7.CF201706, 8.5.7.CF201703, 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 Business Integration IBM Business Process Manager Express Linux, Windows 8.5.7.CF201706, 8.5.7.CF201703, 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 \nPRODUCT ALIAS\/SYNONYM\n BPM"}]},{"id":"TRAIN_Q561","question":"I am getting an error when attempting to apply CF09 on Portal 8001 on a secondary cluster node\n\nThe ConfigTrace.log shows the following....\n\n [wsadmin] com.ibm.websphere.management.exception.AdminException:\n ADMA5026E: No valid target is specified in ObjectName\n WebSphere:cell=<cellname>,node=<nodename>,server=webserver1 for\n module ilwwcm-authoring.war+WEB-INF\/web.xml.\n [wsadmin] ADMA5026E: No valid target is specified in ObjectName\n WebSphere:cell=<cellname>,node=<nodename>,server=webserver1 for\n module ilwwcm-authoring.war+WEB-INF\/web.xml.\n","answer":"If using a remote Dmgr, be sure it is started prior to attempting the upgrade. \n\n2. If using a local Dmgr and Installation Manager requires you to stop it prior to attempting the upgrade, follow these steps:\na. Verify the Dmgr profile name by navigating to the Dmgr's AppServer\/bin folder and execute this command:\n\n.\/manageprofiles.sh|bat -listProfiles\n\nb. Pass in the correct Dmgr profile name according to the installation option you are using:\n\nhttp:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/xpDocViewer.xsp?lookupName=Readme+8.0.0.1#action=openDocument&res_title=Upgrade_instructions_for_WebSphere_Portal_and_Web_Content_Manager_V8.0.0.1_clustered_servers_8001&content=pdcontent","is_impossible":false,"contexts":[{"filename":"swg21632223.txt","text":"Title: IBM Fix pack 8001 installlation fails - ADMA5026E: no valid target is specified in ObjectName - United States\n\nText:\nportal fix pack fixpack 8001 8.0.0.1 install installation fail fails failure ADMA5026E WCMD0003E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nDuring the 8001 fix pack installation, ConfigEngine executes a wsadmin script which tries to read the server definition for any vertical cluster members added to the node. If the Dmgr was not running during the upgrade, it may fail.\n\nSYMPTOM\nIn ConfigTrace, the process is not connecting to the Dmgr:\n========================================\nFri Mar 22 21:19:10 GMT 2013\nTarget started: action-set-managed-node-flag\n\naction-set-managed-node-flag:\n[echo] Is this a Managed Node ? true\nTarget finished: action-set-managed-node-flag\nFri Mar 22 21:19:11 GMT 2013\nTarget started: action-set-conntype-property\n\naction-set-conntype-property:\n[echo] wsadminConnType set to: NONE\nTarget finished: action-set-conntype-property\n========================================\n\n\nThe wsadminConnType should be set to SOAP in a cluster. Further in the ConfigTrace, we see this error:\n\n\n========================================\n\n[wsadmin] WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.\n[wsadmin] AppName wps_scheduler\n[wsadmin] Ear File \/opt\/IBM\/WebSphere\/PortalServer\/installer\/wp.ear\/installableApps\/wps_scheduler.ear\n[wsadmin] Install Options -update -appname \"wps_scheduler\" -deployejb.classpath {\/opt\/IBM\/WebSphere\/PortalServer\/base\/wp.base\/shared\/app\/wp.base.jar}\n[wsadmin] Getting tasks for: wps_scheduler\n\n[wsadmin] ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=MyCell,node=MyNode,server=webserver1 for module wp.scheduler.ejb.jar+META-INF\/ejb-jar.xml.\n[wsadmin] com.ibm.websphere.management.exception.AdminException: ADMA5026E: No valid target is specified in ObjectName WebSphere:cell=MyCell,node=MyNode,server=webserver1 for module wp.scheduler.ejb.jar+META-INF\/ejb-jar.xml.\n[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServerNames(ConfigRepoHelper.java:2270)\n[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getAddRemoveServerNames(ConfigRepoHelper.java:2175)\n[wsadmin] at com.ibm.ws.management.application.task.ConfigRepoHelper.getServerNames(ConfigRepoHelper.java:2048)\n[wsadmin] at com.ibm.ws.management.application.AppAssociation.getServerNames(AppAssociation.java:1451)\n========================================\n\n\nIn Installation Manager native logs, you may see the following error if an incorrect Dmgr profile name is passed in:\n\n========================================\ncheck-if-ok-to-start-dmgr:\n\niim-start-dmgr:\n[exec] WCMD0003E: The specified profile \"Dmgr01\" cannot be found.\nIf a default profile exists and you wish to use it, the -profileName\nparameter is not required.\n[exec] Result: 1\n[exec] Current profile - wp_profile\n========================================\n\nCAUSE\nThe Dmgr is not started during the upgrade, so the installation process cannot connect to it.\n\n\n\nRESOLVING THE PROBLEM\n1. If using a remote Dmgr, be sure it is started prior to attempting the upgrade. \n\n2. If using a local Dmgr and Installation Manager requires you to stop it prior to attempting the upgrade, follow these steps:\na. Verify the Dmgr profile name by navigating to the Dmgr's AppServer\/bin folder and execute this command:\n\n.\/manageprofiles.sh|bat -listProfiles\n\nb. Pass in the correct Dmgr profile name according to the installation option you are using:\n\nhttp:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/xpDocViewer.xsp?lookupName=Readme+8.0.0.1#action=openDocument&res_title=Upgrade_instructions_for_WebSphere_Portal_and_Web_Content_Manager_V8.0.0.1_clustered_servers_8001&content=pdcontent [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/xpDocViewer.xsp?lookupName=Readme+8.0.0.1#action=openDocument&res_title=Upgrade_instructions_for_WebSphere_Portal_and_Web_Content_Manager_V8.0.0.1_clustered_servers_8001&content=pdcontent]\n\n\n\n\n * \n *"}]},{"id":"TRAIN_Q562","question":"Does Portal 6.1.x support Oracle 11g?\n\n\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, What version of Oracle 11g is?","answer":"Oracle 11gR2 V11.2.0.1 (including RAC)","is_impossible":false,"contexts":[{"filename":"swg27019359.txt","text":"Title: IBM WebSphere Portal V6.1.0.5 and V6.1.5.2 hardware and software requirements - AIX - United States\n\nText:\nDSRdoc; SystemRequirementsDocument; prereq; coreq; installation prerequisites; 6105eGA 6152eGA V6105 V6.1.0.5 6.1.0.5 6105 6152 PRODUCT DOCUMENTATION\n\nABSTRACT\n IBM WebSphere Portal V6.1.0.5 and 6.1.5.2 hardware and software requirements on an AIX operating system. The hardware and software requirements reflect the versions of prerequisites and corequisites that were tested with WebSphere Portal V6.1.0.5 and 6.1.5.2. \n\nCONTENT\n\n\n\nTAB NAVIGATION\n * AIX [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019359]\n * i5\/OS [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019362]\n * Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019366]\n\nIBM AIX\n\n\n\n\nWebSphere Portal Server Version 6.1.0.5 and 6.1.5.2 (AIX) \n\nThis page describes the minimum product levels that need to be installed before opening a problem report with IBM WebSphere Portal Technical Support. The software versions and any maintenance levels listed on this page have been explicitly verified as working. \n\nEARLIER LEVEL OF A LISTED SOFTWARE: Software versions at a lower level than those noted on this page are unsupported. LDAP software at an earlier level is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]). \n\nLATER LEVEL OF A LISTED SOFTWARE: Because other products frequently ship fixes, updates, and new releases, testing every configuration is not possible. In general, you can install and run with updates to supported products if those updates are compatible with the tested versions. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]). \n\nUNLISTED SOFTWARE: Software not listed on this page at any level is unsupported. LDAP software not listed is considered untested and best effort support only. For more details and exceptions, refer to the WebSphere Portal 6.1.x Support Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc_v6101\/overview\/inst_req_supt.html]. Also see the listing of software explicitly not supported for use with WebSphere Portal 6.1.x in WebSphere Portal Support Statement Addendum - Unsupported Products [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957] (#7012957 [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27012957]).\n\n\n\nOperating systems\nsupported with 32-bit WebSphere Application Server and WebSphere Portal [\/support\/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (32-bit or 64-bit operating system)\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Operating systems\nsupported with 64-bit WebSphere Application Server and WebSphere Portal [\/support\/docview.wss?uid=swg27019359&aid=1] * AIX Version 7 Release 1 (64-bit operating system) \n * AIX Version 6 Release 1 Technology level 0 Service release 4 (6100-00-04), or with higher Technology or Service release level (64-bit operating system) \n * AIX 5L Version 5 Release 3 Technology level 7 Service release 1 (5300-07-01), or with higher Technology or Service release level (64-bit operating system)\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] AIX hardware requirements [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM POWER family of processors \n * Disk space requirements: * Minimum 2.5 GB free disk space for installation for WebSphere Portal \n * Minimum 1.0 GB free disk space for installation for WebSphere Application Server \n * Minimum 4 GB total disk space recommended for installation \n \n \n * Physical memory: Under minimal load, WebSphere Portal can function with 2GB of RAM. However, 4GB is an optimal starting point for RAM in a production environment. \n * CD-ROM drive\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Application Servers\nThe WebSphere-supplied Java SDK is required for both the run time and any remote Java clients. [\/support\/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server V7.0.0.11 with IBM SDK 1.6 SR12 (WebSphere Application Server product site) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/]#1a#1b#1b \n * WebSphere Application Server V6.1.0.31 with IBM SDK 1.5 SR7 (WebSphere Application Server product site) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/]#1a#1b * Note: IBM Java SDK V5 reached end of service in 2015. If you continue to use WebSphere Application Server 6.1.x after that date with extended support, Java SDK V5 is no longer included\n \n \n\nRefer to \"Required WebSphere Interim Fixes for WebSphere Portal V6.1.0.5 and V6.1.5.2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24027476]\" for the complete list of fixes required for WebSphere Application Server. [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Optional WebSphere Servers [\/support\/docview.wss?uid=swg27019359&aid=1] * WebSphere Application Server SCA feature pack 1.0.1.5 \n * WebSphere Application Server XML feature pack 1.0.0.5 \n * WebSphere Process Server V6.2.0.2*, 6.1.2.3, and 6.1.0.4 (all via Client Install option only with WAS 6.1x releases) *Refer to technote #1398123 for Process Server V6.2 Client installation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21398123] \n * WebSphere Virtual Enterprise (formerly \"Extended Deployment\") V6.1.1.1, 6.1.0.5 (WebSphere Extended Deployment product site [http:\/\/www.ibm.com\/software\/webservers\/appserv\/extend\/])\n\nJavaScript Library [\/support\/docview.wss?uid=swg27019359&aid=1] * Dojo V1.3.2 or 1.1.1\n\nTo take advantage of the support for Microsoft Internet Explorer V8.0 or to use the new features in 6.1.5.2 such as Mashups integration and the Page Builder Theme, you will need to use Dojo V1.3.2. Refer to the topic \"Using a different Dojo version [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1\/topic\/com.ibm.wp.ent.doc_v615\/admin\/epc_use_prior_dojo.html]\" for more information. [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Databases\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] * Derby V10.1 and 10.3 \n\n * IBM DB2 Universal Database (DB2 product site) [http:\/\/www.ibm.com\/software\/data\/db2\/9\/] (also supports High Availability Disaster Recovery (HADR) Feature) * V9.7 FP1 for Linux, Unix, Windows \n * V9.5 for Linux, Unix, Windows: Enterprise Server Edition 9.5 FP5, Express Edition 9.5 FP5, Workgroup Server Edition 9.5 FP5 (viper 2) (including HADR) \n * V9.1 for Linux, Unix, Windows: Enterprise Server Edition 9.1 FP9, Express Edition 9.1 FP9, Workgroup Server Edition 9.1 FP9 (including HADR) \n * V8.1 for Linux, Unix, Windows: Enterprise Server Edition 8.1 FP16, Express Edition 8.1 FP16, Workgroup Server Edition 8.1 FP16 (including HADR)\n \n \n * IBM DB2 for z\/OS V9.1 and V8.1, PUT level 0901 or later maintenance (DB2 for z\/OS product site) [http:\/\/www.ibm.com\/software\/data\/db2\/zos\/]#2 (also supports High Availability Disaster Recovery (HADR) Feature) \n * WebSphere Information Integrator V8.2 FP4\n\n * Oracle (Oracle Database product site) [http:\/\/www.oracle.com\/database\/index.html] (Oracle Database clustering using RAC on all supported Oracle levels. Supports connect time failover#3a) * Standard\/Enterprise V9.2.0.8, 10.1.0.5 Patch 4, 10.2.0.4 and 10.2.0.5 (patchset 8202632) (including RAC) (Supports Automatic Storage Management (ASM) Feature) \n * Oracle 11gR2 V11.2.0.1 (including RAC) \n * Oracle 11gR1 V11.1.0.7 (including RAC)\n \n \n \n * Microsoft SQL Server (Microsoft product site) [http:\/\/www.microsoft.com] * Enterprise Edition 2008 SP1 [http:\/\/www.microsoft.com] \n * Enterprise Edition 2005 SP3\n \n \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Java Database Connectivity (JDBC) Drivers [\/support\/docview.wss?uid=swg27019359&aid=1] * DataDirect Connect JDBC 4.0 (type 4) (DataDirect Connect JDBC product site [http:\/\/www.datadirect.com\/products\/jdbc\/index.ssp]) \n * DB2 Driver for JDBC and SQLJ 3.1 (type 2\/4) \n * JCC JDBC driver level 3.58.90 or above to connect to DB2 for z\/OS Note: Use the JDBC drivers provided with DB2 LUW V9.7 FP2 when the Portal is not also running on z\/OS \n * Derby embedded JDBC Driver \n * Microsoft SQL Server JDBC Driver 1.2 or 2.0 (Microsoft SQL Server JDBC Driver site [http:\/\/msdn.microsoft.com\/en-us\/data\/aa937724.aspx]) \n * Oracle 9i or 10g or 11g JDBC Driver Thin (type 4) (Oracle JDBC product site [http:\/\/www.oracle.com\/technology\/software\/tech\/java\/sqlj_jdbc\/index.html])\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Web servers\n[\/support\/docview.wss?uid=swg27019359&aid=1] * Apache HTTP Server V2.0.5.9 (Apache Server product site) [http:\/\/httpd.apache.org\/] (Apache Server 2.0.5.9 includes CERT Advisory CA-2002-17) \n * Apache HTTP Server V2.2 (Apache Server product site) [http:\/\/httpd.apache.org\/] (Apache 2.2.x is supported with WebSphere Application Server 7.0.#4a)#4a \n * IBM HTTP Server for WAS V7.0 and 6.1 (IBM HTTP Server product site) (HTTP Server 7.0 is supported with WebSphere Application Server 7.0 only) [http:\/\/www.ibm.com\/software\/webservers\/httpservers\/] \n * IBM HTTP Server for iSeries V7R1, V6R1 and V5R4 (IBM HTTP Server product site) [http:\/\/www-03.ibm.com\/systems\/i\/software\/http\/index.html](HTTP Server for i5\/OS is provided natively on System i5 and is not bundled with or installed by WebSphere Portal. For V5R4, supported group PTF is SF99114 level 13; for V6R1, supported group PTF is SF99115 level 1. For V5R4, the license program number is 5722DG1; for V6R1, the license program number is 5761DG1. Issue the GO LICPGM to display all the installed licensed programs. For WebSphere Application 6.1.0.21 on V6R1M0, apply SI35071. For WebSphere Application 7.0.0.1 on V6R1M0, apply SI35078) \n * Microsoft Internet Information Services (IIS) V7.5 or 7.0 (only for WAS 7 environments) and 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http:\/\/www.lotus.com\/products\/product4.nsf\/wdocs\/dominohomepage]#4d(To use Lotus Domino Version 7.0 with WebSphere Application Server 6.1, you must install the Web Server plug-in for Lotus Domino Server Version 6 which is a part of the Web Server plug-in for WebSphere Application Server 6.1) \n * Sun Java System Web Server 7 Update 8 or 6.1 SP12 (Sun product site) [http:\/\/www.sun.com\/products\/] \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Web browsers\n(required for administration\/configuration, sample program execution and launch pad. There is no restriction nor certification of Web browsers on clients that connect the server to display content) [\/support\/docview.wss?uid=swg27019359&aid=1] * 6.1.0.5: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n * Firefox V3.6, 3.5, 3.0, 2.0, 1.5.0.7 (Firefox product site) [http:\/\/www.mozilla.org\/] \n * Apple Safari 3.2 and higher (Apple product site) [http:\/\/www.apple.com\/safari\/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http:\/\/www.apple.com\/safari\/] \n Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077]\n * Opera 9.52 and higher [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077](Opera product site) [http:\/\/www.opera.com\/products\/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21318444]\n \n \n * \n * 6.1.5.2: * Microsoft Internet Explorer 8.0, 7.0, 6.0 (Microsoft product site) [http:\/\/www.microsoft.com] \n PageBuilder, Mashup Integration and Wiki\/Blogs in V6.1.5.2 are not supported or functional when using Microsoft Internet Explorer V6.0.#6f \n * Firefox V3.6, 3.5, 3.0 (Firefox product site) [http:\/\/www.mozilla.org\/] \n * Apple Safari 3.2 and higher (Apple product site) [http:\/\/www.apple.com\/safari\/] \n * Apple Safari 4.0, 4.0.5 (Apple product site) [http:\/\/www.apple.com\/safari\/]\n Safari is not supported for use with the Common Mail portlet. For additional information, see Limitations on Safari Web browser. Mashup Integration not supported with Safari for Windows. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21320077]#6a#6e \n * Opera 9.52 and higher (Opera product site) [http:\/\/www.opera.com\/products\/]\n Drag and Drop functionality of administering portlets and pages is not supported with Opera. Opera is not supported for use with the Common Mail portlet or the Domino and Extended Products Portlets. For additional information, see Limitations on Opera Web browser. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21318444]#6b\n \n \n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] LDAP servers\n[\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1 (Lotus Domino product site) [http:\/\/www.lotus.com\/products\/product4.nsf\/wdocs\/dominohomepage] For 7.0.2 and 7.0.1: Apply SPR KLIN6LRTHJ to be able to return Groups and Users by direct lookup. Turkish users should use version 7.0.3 or later.#7a \n * IBM Tivoli Directory Server 6.2, 6.1 and 6.0 (IBM Tivoli Directory Server product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/directory-server\/] Add the fix for APAR IO02714 on applicable releases, available at IBM Support.#7b \n * IBM z\/OS Security Server 1.7 and 1.6 (IBM z\/OS Security Server product site) [http:\/\/www.ibm.com\/systems\/z\/advantages\/security\/index.html] \n * IBM z\/OS.e Security Server 1.7 and 1.6 (IBM z\/OS Security Server product site) \n * Novell eDirectory 8.8 or 8.7.3 (Novell eDirectory product site) [http:\/\/www.novell.com\/products\/edirectory\/] \n * Sun Java System Directory Server 7, 6.3, 6.1, and 6 (Sun product site) [http:\/\/www.sun.com\/products\/] \n * Microsoft Active Directory 2008, including Lightweight Directory Server (AD LDS, previously referred to as \"Application Mode\" or ADAM) \n * Windows Active Directory 2000 and 2003 including Application Mode\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for collaboration - Domino and Extended Products (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Domino Enterprise Server V8.5.2, 8.5.1, 8.5, 8.0.2, 8.0.1, 8.0 and V7.0.3, 7.0.2, 7.0.1, 6.5.6 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] Domino V8.5.2 also needs the fix applied for SPR DPOS895USS, contact Domino Technical Support for the fix. \n * IBM Lotus Domino Document Manager V7 and 6.5.1 \n * IBM Lotus Sametime V8.5, 8.0.2, 8.0, 7.5.1 and 7.5 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for content management (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Lotus Web Content Management V6.1.0.5 or 6.1.5.2 (IBM Lotus Web Content Management product site) [http:\/\/www.ibm.com\/software\/lotus\/products\/webcontentmanagement\/] \n * Ephox EditLive IBM LWCM OEM version 3.4.1.41 (which includes EditLive version 7.0.1.46.) (Ephox EditLive product site [http:\/\/www.ephox.com]) \n * IBM Lotus Quickr V8.5, 8.1.1 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] \n * 6.1.5.2: IBM Lotus FileNet P8 V4.5 (IBM Lotus product site) [http:\/\/www.ibm.com\/developerworks] \n * 6.1.5.2: IBM Content Manager V8.4 (IBM Content Manager product site) [http:\/\/www.ibm.com\/software\/data\/cm\/cmgr\/]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Supported Java Runtime Environments - Web Content Management authoring portlet [\/support\/docview.wss?uid=swg27019359&aid=1] * Java Runtime Environments (requires one) V1.6.x or 1.5.x (Sun product site) [http:\/\/www.sun.com\/products\/]\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] External Security software (optional) [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli Access Manager V6.1 and 6.0 for trust association interceptor and enhanced trust association interceptor (support for Subject creation) (Tivoli Access Manager product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal. \n * IBM Tivoli Access Manager V6.0 for Java Authorization Contract for Containers (JACC) (Tivoli Access Manager product site) [http:\/\/www.ibm.com\/software\/tivoli\/products\/access-mgr-e-bus\/] When using Tivoli Access Manager 6.0 for authorization or integrated user provisioning with WebSphere Portal, the Tivoli Access Manager AMJRTE component must be at the Version 5.1 fix pack 2 level or later. This version of AMJRTE component is automatically installed with WebSphere Application Server Version 5.1.1 or later, but must still be configured to work with WebSphere Portal \n * Computer Associates SiteMinder V6.0\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=1] Software for portlet development [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Rational Application Developer V7.5 and 7.0.6 (plugin for UTE) \n * IBM Portlet Factory V6.1.5, 6.1\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=2] [\/support\/docview.wss?uid=swg27019359&aid=3] [\/support\/docview.wss?uid=swg27019359&aid=3] Software for license management [\/support\/docview.wss?uid=swg27019359&aid=1] * IBM Tivoli License Compliance Manager V2.3\n\n[\/support\/docview.wss?uid=swg27019359&aid=1] [\/support\/docview.wss?uid=swg27019359&aid=4] [\/support\/docview.wss?uid=swg27019359&aid=5] [\/support\/docview.wss?uid=swg27019359&aid=5] \n\nRelated information\n[http:\/\/d02was006.southbury.ibm.com\/support\/dcf\/preview.wss?host=d02dbs88.southbury.ibm.com&db=support\/swg\/swgdocs.nsf&unid=2D60E6429AA6F54285256FB00046AC9D&taxOC=SSCVS22&MD=2005\/02\/25%2008:02:00&sid=]Detailed system requirements [http:\/\/www.ibm.com\/support\/docview.wss?rs=688&uid=swg27007791]\nWebSphere Portal Information Centers and more [http:\/\/www.ibm.com\/developerworks\/websphere\/zones\/portal\/proddoc.html]\nSupport Statement [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.ent.doc\/overview\/inst_req_supt.html] \n\nSee disclaimer. \n\nTop of page \n\nDisclaimer\nIBM reserves the right to change specifications and other product information without prior notice. This publication could include technical inaccuracies or typographical errors. References herein to IBM products and services do not imply that IBM intends to make them available in other countries. IBM PROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. \n\nTop of page \n\n\n\n\nORIGINAL PUBLICATION DATE\n 2009\/9\/1"}]},{"id":"TRAIN_Q563","question":"CICS VR V4.2 or V5.x affected by the June 2015 Leap Second\n\nAre there any problems, pre or post actions or other maintenance required before or after adding the June 2015 Leap second for CICS VSAM Recovery for z\/OS (CICS VR) 4.2, 5.1 or 5.2? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q564","question":"Why SET CHLAUTH ACTION(REMOVE) is not successful\n\n\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\nMay I know the reason?\n","answer":"NOTICE that the userid mentioned in the CLNTUSER field of the output of the DISPLAY CHLAUTH command is NOT surrounded by single quotes.","is_impossible":false,"contexts":[{"filename":"swg21577138.txt","text":"Title: IBM MQ 7.1 and later: How to remove a channel authentication record (CHLAUTH) - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n You have added a channel authentication record into a WebSphere MQ 7.1 or later queue manager:\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL) ACTION(ADD)\nAMQ8877: WebSphere MQ channel authentication record set.\n\nThen you display it:\n\nDISPLAY CHLAUTH(*) TYPE(USERMAP)\n1 : DISPLAY CHLAUTH(*) TYPE(USERMAP)\nAMQ8878: Display channel authentication record details.\nCHLAUTH(*) TYPE(USERMAP)\nCLNTUSER(testuser) USERSRC(CHANNEL)\n\nNow you want to remove it and you try executing the following runmqsc command which you constructed using copy and paste from the above output:\n\nDELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)\n3 : DELETE CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) USERSRC(CHANNEL)\n\nYou get the following error:\n\nAMQ8405: Syntax error detected at or near end of command segment below:-\nDELETE CHLAUTH\n\nThe DELETE CHLAUTH does not exist and after consulting the MQ 7.1 Information Center you read that you have to use the SET CHLAUTH command with the argument ACTION(REMOVE). You try now:\n\nSET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)\n19 : SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER(testuser) ACTION(REMOVE)\n\nBut you get the following error:\n\nAMQ8884: Channel authentication record not found.\n\nYou specified the attribute CLNTUSER(testuser) as it was shown in the output of the DISPLAY CHLAUTH(*), thus, you think the record should be found. You want to know what is the problem?\n\n\nCAUSE\nSee the following section of the MQ 7.1 documentation:\nWebSphere MQ > 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"}]},{"id":"TRAIN_Q565","question":"Does ODM 8.5.1 support MQ 9.0?\n\n\n\nDoes ODM 8.5.1 support MQ 9.0 where ODM Rule Execution Server is running on WAS 8.5.0.2 (embedded with ODM)?\n\nNo MQ version is specified in ODM 8.5.1 System Requirements.","answer":"WebSphere MQ V7.0, V7.1, V7.5, V8.0 and V9.0 queue managers and clients inter operate with queue managers and clients from any previous level of the WebSphere MQ or MQSeries products.","is_impossible":false,"contexts":[{"filename":"swg21312967.txt","text":"Title: IBM MQ 7.x, MQ 8.0 and MQ 9.0 compatibility with previous versions - including usage of CCDT files, JMS .bindings, SSL\/TLS - United States\n\nText:\ncompatibility; compatible TECHNOTE (FAQ)\n\nQUESTION\n Are WebSphere MQ (WMQ) V7.0, V7.1, V7.5 and V8.0 compatible with previous versions?\nCan an MQ 8.0 client use a CCDT created with a previous version?\nCan an MQ 7.0 client use a CCDT created with a newer version?\nCan a JMS .bindings file created in 7.1 be used with 8.0?\nCan a JMS .bindings file created in 8.0 be using with 7.1?\nCan an older MQ client using an old SSL protocol still work with MQ 9.0?\n\n\nANSWER\n\nCompatibility statement:\n\nWebSphere MQ V7.0, V7.1, V7.5, V8.0 and V9.0 queue managers and clients inter operate with queue managers and clients from any previous level of the WebSphere MQ or MQSeries products.\n\nThis means that ... \n\n * A 7.0, 7.1, 7.5, 8.0 and 9.0 client can connect to all queue managers, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0 \n * A 7.0, 7.1, 7.5, 8.0 and 9.0 queue manager can interact with all clients, non-version 7, as well as version 7.0, 7.1, 7.5, 8.0 and 9.0\n\n\nNote: If your V7.x, V8.0 or V9.0 client connects to an MQ 6.0 or earlier queue manager, or use a server-connection channel with the attribute SHARECNV = 0 (which treats the connection as being MQ 6.0), then you cannot use V7 features, and structures in your client application. \n\n\nMQ Client V6 and V7\/V8\/V9 compatibility \n\nThe new features which are available for a version 7.x, 8.0 or 9.0 client connected to a version 6.0 queue manager are: \n- Weighted selection on CLNTCONN channels. \n- Reconnecting via a previously used channel. \n- Maximum message length increased on MQSERVER environment variable. \n\nThe new feature which is available for a version 6.0 client connected to a version 7.x, 8.0 or 9.0 queue manager is: \n- Instance limits on SVRCONN channels. \n\n\nCaveat \n\nThe compatibility statement refers to: \nVersion.Release \n\n... such as: \nA 7.0 client is compatible with a 7.5 queue manager. \n\nThis statement does not extend to a more granular specification: \nVersion.Release.Maintenance.FixPack (V.R.M.F) \n\nIf there are known problems at a given V.R.M.F (such as 7.0.0.0), then an upgrade to a more recent fix pack for the same Version.Release will be necessary (such as 7.0.1.11). Notice that the upgrade is within the same Version.Release (7.0) and a migration to a newer Version.Release is not forced. \n\n\n+ Compatibility of MQ clients and CCDT files \n\nNewer versions of the MQ clients (such as 8.0) know how to handle CCDT files that were created\/edited by older queue managers (such as 6.0) \n\nOlder MQ clients (such as 6.0) do NOT know how to handle CCDT files that were created\/edited by newer queue managers (such as 8.0). That is, older clients do not know what are the new attributes (if any) introduced in newer MQ versions. \n\nBased on the above, if you have a mix of versions of MQ clients that use a common CCDT file, then this CCDT file should be edited from a queue manager at the LOWEST (OLDEST) version. For example, if you are using MQ 6.0, 7.0, 7.1, 7.5, 8.0 and 9.0 clients that use a CCDT file, then the CCDT file must be maintained by the MQ queue manager at version 6.0 \n- However, the newer MQ clients (8.0) when using the CCDT created with 5.3 will NOT be able to fully exploit newer features, even when connecting to an 8.0 queue manager because the CCDT will not show the new attributes for those new features. \n\nMQ CCDT created version Compatible MQ client versions \n\n6.0 6.0 7.0 7.1 7.5 8.0 9.0 \n7.0 7.0 7.1 7.5 8.0 9.0 \n7.1 7.1 7.5 8.0 9.0 \n7.5 7.1 7.5 8.0 9.0 \n8.0 8.0 9.0 \n9.0 8.0 9.0 \n\nNotes: \n- There was no change in the MQCD length between 7.1 and 7.5. Therefore the CCDT created on 7.5 can be used on 7.1. \n- There was no change in the MQCD length between 8.0 and 9.0. Therefore the CCDT created on 9.0 can be used on 8.0. \n- Unless documented otherwise, CCDTs created on higher level maintenance releases (for example 8.0.0.3) are compatible with lower level (for this example: 8.0.0.0) MQ clients running the same MQ version and release. \n\nUpdate on July 2016: \nThere are 2 APARs that allow OLDER MQ clients to use NEWER CCDT files! \nThese APARs relax the restriction by allowing newer CCDTs to be used on older clients but with the caveat that the older client cannot make use of any of the newer channel attributes. These attributes will assume their default values when the CCDT is negotiated with the queue manager. \n. \nFor Java\/JMS client applications: \nIT10863: WEBSPHERE MQ CLASSES FOR JAVA\/JMS APPLICATIONS CAN NOT USE CCDT FILES GENERATED ON A NEWER LEVEL QUEUE MANAGER [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IT10863] \nVersion Maintenance Level \nv7.0 7.0.1.14 \nv7.1 7.1.0.8 \nv7.5 7.5.0.6 \nv8.0 8.0.0.3 \n\nFor C based (and non-Java\/JMS) client applications: \nIT11547: WEBSPHERE MQ CLIENT APPLICATIONS CANNOT USE CCDT FILES GENERATED ON A NEWER LEVEL QUEUE MANAGER [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IT11547]. \nThis applies to C based and non-Java\/JMS applications. \nVersion Maintenance Level \nv7.1 7.1.0.8 \nv7.5 7.5.0.7 \nv8.0 8.0.0.3 \n\n\n+ Compatibility of MQ clients and JMS .bindings files \n\n- A JMS .bindings file that was created at an older version (such as 7.1) than the MQ JMS client (such as 8.0) will be used without version related errors by the client. \n\n- A JMS .bindings file that was created at a newer version (such as 8.0) than the MQ JMS client (such as 7.1), will be used without version related errors by the client. If there are any new attributes in the JMS administered objects that the older client cannot read, they are ignored. \n\n\n+ Compatibility of SSL\/TLS cipher specifications \n\nThere have been changes in recent fix packs related to the compatibility of SSL\/TLS cipher specifications. For example, if you have a MQ Client at 7.1.0.1 connecting to a MQ 8.0.0.1 queue manager using an older SSL cipher specification, after applying Fix Pack MQ 8.0.0.2 to the queue manager, the connectivity may be broken because the queue manager indicates that the older SSL cipher spec is now deprecated. \n\nFor more details on the compatibility of SSL\/TLS cipher specifications, see the following blog entry: \n\nSSL and TLS Cipher Specification Deprecations for the MQ Product [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/aimsupport\/entry\/ssl_and_tls_cipher_specification_deprecations_for_the_mq_product?lang=en] \nMiguel A. Rodriguez \nMay 2016 \nDue to the recent security vulnerabilities (for example, POODLE Attack), the latest MQ product Fix Packs come with stricter, default security requirements that affect the use of the compromised Secure Socket Layer (SSL) and Weak Transport Level Security (TLS) Cipher Specifications. Since these Cipher Specification deprecations are disabled in MQ Fix Packs by default, review the article for the changes separated by MQ versions and Fix Pack levels. RELATED INFORMATION\n WebSphere MQ V7.1 Announcement Letter - PDF [http:\/\/www.ibm.com\/common\/ssi\/rep_ca\/8\/897\/ENUS208-068\/ENUS208068.PDF]\nWebSphere MQ V7.1 Announcement Letter - Web [http:\/\/www.ibm.com\/common\/ssi\/cgi-bin\/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS211-395]\nWMQ Doc: Coexistence compatibility interoperability [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.5.0\/com.ibm.mq.mig.doc\/q006320_.htm?lang=en]\n\n\n \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ \nPRODUCT ALIAS\/SYNONYM\n WMQ MQ"}]},{"id":"TRAIN_Q566","question":"When required, upgrade the IBM Installation Manager rather than install a new copy.\n\nDuring the installation of WebSphere Process Server (WPS) Fix Pack, or IBM Business Process Manager (BPM) Fix Pack, there may be requirement to use a newer version of IBM Installation Manager.\nWhat is the right method to meet this requirement?","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q567","question":"Why the Editor for Messages logon page does not work?\n\n\n\nWe have Editor for Messages installed on a Windows server. Users are accessing the web UI from a terminal server session that has been replaced recently. Users cannot login anymore from the new environment.\n\nThe fails as follows : the Editor for Messages logon page loads but when the user wants to validate their user\/password by clicking on the \"login\" button, nothing occurs.","answer":"Editor for Messages supports Microsoft Internet Explorer only. Mozilla Firefox and Google Chrome are not supported.\n\nSupported IE versions: \nIE 6, IE 7, IE 8, IE 9 (compatibility view), IE 10(Compatibility view), IE 11(Compatibility view)","is_impossible":false,"contexts":[{"filename":"swg21678261.txt","text":"Title: IBM Web Browser Versions Supported by PathWAI Editor for Messages - United States\n\nText:\nWeb Browser Internet Explorer Editor for Messages 5724K3700 5724K3700TR TECHNOTE (FAQ)\n\nQUESTION\n Which web browser versions are supported by Editor for Messages? \n\nANSWER\nEditor for Messages supports Microsoft Internet Explorer only. Mozilla Firefox and Google Chrome are not supported.\n\nSupported IE versions: \nIE 6, IE 7, IE 8, IE 9 (compatibility view), IE 10(Compatibility view), IE 11(Compatibility view)\n\nNote:\nThere are known issues which cause functions not to work correctly with IE 9 or above. For example, the check boxes for queue filters at the right side do not work correctly, and the open queue messages dialog shows in minimum small size. As a workaround, IE compatibility view is recommended. The following explains how to enable it.\n\n1. Enter the URL to connect with Editor for Messages Web Server. In my case, 9.123.109.109 is the server IP. \n[\/support\/docview.wss?uid=swg21678261&aid=1] [\/support\/docview.wss?uid=swg21678261&aid=1]\nScreenshot 1\n\n2. Right click on the menu Tools \u2013> Compatibility View. From now on, all views from this site will be displayed in IE compatibility view. You may also add the IP to the compatibility view setting (see screenshot 2) by selecting Tools -> Compatibility View Settings, then it will open following dialog. Now, input the server IP address to add and click \u2018close\u2019 to save.\n\n[\/support\/docview.wss?uid=swg21678261&aid=2]\nScreenshot 2\n\nAfter this, you do not need to select the compatibility view every time when IE is launched. IE will open the site automatically in compatibility view."}]},{"id":"TRAIN_Q568","question":"How does Session timeout work in WebSphere Portal? and How do I change the timeout behavior?\n\n\n\nHow does Session timeout work in WebSphere Portal V6.1.0.1?","answer":"In V6.1.0.1, when the session expires, you are redirected to the page specified in the redirect.logout.url property. \n\n\nIn Portal 6.1.0.1 with APAR PK78213 installed or in V6.1.0.2 and later, you are not redirected to the login page. Instead, the ErrorSessionTimeOut.jsp displays:","is_impossible":false,"contexts":[{"filename":"swg21419230.txt","text":"Title: IBM WebSphere Portal inactive session time out and redirect - United States\n\nText:\nredirect; session; time out; session time out; redirect.logout.url; redirect logout TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nA redirect to a specific page in IBM WebSphere Portal does not always occur when an inactive session times out or the inactive session time out does not appear to occur at all. \n\nDIAGNOSING THE PROBLEM\nYou set the following properties in the WP_ConfigService and notice different behavior when the session times out (depending on your version of WebSphere Portal): \n\n * \n * redirect.logout = true\n * \n * redirect.logout.url = <Fully Qualified URL>\n\n\nThe session inactivity time out is 30 minutes but this value does not affect this issue. \nRESOLVING THE PROBLEM\nIn V6.1.0.1, when the session expires, you are redirected to the page specified in the redirect.logout.url property. \n\n\nIn Portal 6.1.0.1 with APAR PK78213 installed or in V6.1.0.2 and later, you are not redirected to the login page. Instead, the ErrorSessionTimeOut.jsp displays: \n\n[\/support\/docview.wss?uid=swg21419230&aid=1] [\/support\/docview.wss?uid=swg21419230&aid=1]\n\nBy design, the ErrorSessionTimeOut.jsp always displays when the session times out if a logout URL is configured.\n\nOn systems running V6.1.0.1, install APAR PK78213 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PK78213] to maintain consistency across all 6.1 platforms. \n\nTo redirect to the login page (or any other page) when the session expires, use one of the following methods:\n\n\n * \n * \n * \n * \"Configuring authentication filters\"\n * \n * New security APIs in WebSphere Portal\n * \n * \n * \n * \n * \n * \n\n\nNOTES \n\n1. This document discusses redirect behavior on session timeout. An \"explicit\" logout (by selecting or clicking the logout link) is always expected to cause a redirect to the URL specified in redirect.logout.url. \n\n2. The inactive session timeout may not work at all in a single node cluster or a cluster with \"failover\" nodes in which only 1 node is up at a time (for example, when using Portal Express). Either add a second node or set the value for Distributed Sessions from \"Memory-to-memory \nreplication\" to None in the WebSphere Application Server Integrated Solutions Console, path: Servers > Server Types > Websphere application servers > WebSphere_Portal > session management > Distributed environment settings. RELATED INFORMATION\n APAR PK78213 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PK78213]\nConfiguring authentication filters [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1\/topic\/com.ibm.wp.ent.doc_v6101\/admin\/adauthflt.html]\nNew security APIs in WebSphere Portal [http:\/\/www.ibm.com\/developerworks\/websphere\/library\/techarticles\/0905_buchwald\/0905_buchwald.html]\nPeer-to-peer topology [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=\/com.ibm.websphere.nd.doc\/info\/ae\/ae\/cprs_m2m_p2p_default.html]"}]},{"id":"TRAIN_Q569","question":"Authorization failed.: The Authorization Code entered is not for this product\/version.\n\nIf you have multiple Authorization Codes, please check you have entered the correct one. ","answer":"Please check that your authorization code matches the version and software product you are trying to license. The product and version of the authorization code must match that of the installed product. For assistance with your authorization codes, please visit the Predictive Analytics Community Get Help page https:\/\/developer.ibm.com\/predictiveanalytics\/get-help\/ [https:\/\/developer.ibm.com\/predictiveanalytics\/get-help\/], for direct links to the License Key Center and information about your Support options.","is_impossible":false,"contexts":[{"filename":"swg21486143.txt","text":"Title: IBM Error message: 'authorization failed' and 'authorization code entered is not for this product\/version' when attempting to license IBM SPSS Statistics or Modeler\/ - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When attempting to license an SPSS product, I am getting the following error message.\n\nAuthorization in progress ... (xxxxxxxxxxxxxxxxxxxx)\nAuthorization failed.: The authorization code entered is not for this product\/version. If you have multiple Authorization Codes, please check you have entered the correct one.\n***End Of Transaction.***\nOne or more codes failed.\nClick \"Next\" to license authorization via e-mail.\n\nWhat can I do to correct this problem? \n\nCAUSE\nThe authorization code product and\/or version does not match that of your installed product.\n\nRESOLVING THE PROBLEM\nPlease check that your authorization code matches the version and software product you are trying to license. The product and version of the authorization code must match that of the installed product. For assistance with your authorization codes, please visit the Predictive Analytics Community Get Help page https:\/\/developer.ibm.com\/predictiveanalytics\/get-help\/ [https:\/\/developer.ibm.com\/predictiveanalytics\/get-help\/], for direct links to the License Key Center and information about your Support options. \n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Visualization Designer Platform Independent 1.0.3, 1.0.2, 1.0 \nHISTORICAL NUMBER\n 93088"}]},{"id":"TRAIN_Q570","question":"What files require modification when updating, upgrading, moving, or migrating a System Monitor MSSQL database in IBM Enterprise Content Management System Monitor 5.2 ?\n\nWhat files require modification when updating, upgrading, moving, or migrating a System Monitor MSSQL database in IBM Enterprise Content Management System Monitor 5.2? ","answer":"The files are:\n$CENIT_ROOT\/cala_rex\/cfg\/cala_rex_finca.cfg\n\n$CENIT_ROOT\/cala_rex\/cfg\/cala_rex_srv.cfg\n\n$CENIT_ROOT\/.prodinfo\/FSM_SERVER.settings\n\n$CENIT_ROOT\/eventserver\/cfg\/db-cfg.xml\n\n$CENIT_ROOT\/gui\/cfg\/db-cfg.xml\n\n$CENIT_ROOT\/initdb\/cfg\/db-cfg.xml","is_impossible":false,"contexts":[{"filename":"swg22002442.txt","text":"Title: IBM Files requiring modification when updating, upgrading, moving, or migrating a System Monitor MSSQL database in IBM Enterprise Content Management System Monitor 5.2 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What files require modification when updating, upgrading, moving, or migrating a System Monitor MSSQL database in IBM Enterprise Content Management System Monitor 5.2 \n\nANSWER\nThe files are:\n$CENIT_ROOT\/cala_rex\/cfg\/cala_rex_finca.cfg\n\n$CENIT_ROOT\/cala_rex\/cfg\/cala_rex_srv.cfg\n\n$CENIT_ROOT\/.prodinfo\/FSM_SERVER.settings\n\n$CENIT_ROOT\/eventserver\/cfg\/db-cfg.xml\n\n$CENIT_ROOT\/gui\/cfg\/db-cfg.xml\n\n$CENIT_ROOT\/initdb\/cfg\/db-cfg.xml\n\n\n\nThere is a chance that a monitor could be configured to check the status of the monitor's database server, in which case the MSSQL database server name is also defined in this file:\n\n$CENIT_ROOT\/cala\/misc\/cmdtab_merged.ctb.\n\n\nPlease note: If the port, user, or password changes, these must also be reflected in the above files."}]},{"id":"TRAIN_Q571","question":"DcDesktop Verification batch panel\n\n Hi\n\nWhat is the purpose of page type drop down list in Verification batch panel?\n\nWhere can this be used?\n\nCan this be disabled or made invisible?\n\nThanks in advance. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q572","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM WebSphere MQ (CVE-2016-0475)\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM WebSphere MQ (CVE-2016-0475). Where can I find this information? ","answer":"CVEID: CVE-2016-0475 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-0475]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE Java SE Embedded and Jrockit related to the Libraries component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109946 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109946] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:P\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21976896.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM WebSphere MQ (CVE-2016-0475, CVE-2015-7575, CVE-2016-0448) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae Runtime Environment Java\u2122 Technology Edition that is used by IBM WebSphere MQ. These issues were disclosed as part of the IBM Java SDK updates in January 2016 and include the vulnerability commonly referred to as \u201cSLOTH\u201d. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-0448 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-0448]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE and Java SE Embedded related to the JMX component could allow a remote attacker to obtain sensitive information resulting in a partial confidentiality impact using unknown attack vectors.\nCVSS Base Score: 4\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109949 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109949] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:S\/C:P\/I:N\/A:N)\n\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\nCVEID: CVE-2016-0475 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-0475]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE Java SE Embedded and Jrockit related to the Libraries component has partial confidentiality impact, partial integrity impact, and no availability impact.\nCVSS Base Score: 5.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109946 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/109946] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:P\/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM JRE 7, Java Technology Edition, Version 7 provided by IBM WebSphere MQ 8.0.0.4 and earlier on all platforms (except IBM i and z\/OS) \n\nIBM JRE 6, Java Technology Edition, Version 6 provided by IBM WebSphere MQ 7.5.0.5, IBM WebSphere MQ 7.1.0.7 and earlier on all platforms (except IBM i and z\/OS)\n\nREMEDIATION\/FIXES\nIBM WebSphere MQ 8.0 \n\nHP-UX \n\nApply fix pack 8.0.0.5 when available, in the interim apply ifix IV81649 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649] \n\nAIX, Linux, Solaris & Windows \n\nApply fix pack 8.0.0.5 when available, in the interim apply ifix IT13492 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0&platform=All&function=aparId&apars=IT13492] \n\n \n\nIBM WebSphere MQ 7.5 \n\nHP-UX \n\nApply fix pack 7.5.0.7 when available, in the interim apply ifix IV81649 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=7.5&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649] \n\nAIX, Linux, Solaris & Windows \n\nApply fix pack 7.5.0.6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21975660] \n\n \n\nIBM WebSphere MQ 7.1 \n\nHP-UX \n\nApply fix pack 7.1.0.8 when available, in the interim apply ifix IV81649 [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=7.5&platform=HPUX+64-bit,+IA64&function=aparId&apars=IV81649] \n\nAIX, Linux, Solaris & Windows \n\nApply fix pack 7.1.0.8 when available, in the interim apply ifix IT13492 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=7.1&platform=All&function=all&source=fc]\n\nWORKAROUNDS AND MITIGATIONS\nFor CVE-2015-7575: \n\nUsers of Java 7 and later can address the issue by updating the ..\/jre\/lib\/security\/java.security file as follows (both steps are required): \n\n\u00b7 Add MD5 to the jdk.certpath.disabledAlgorithms property - for example jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024, MD5 \n\n\u00b7 Add MD5withRSA to the jdk.tls.disabledAlgorithms property - for example jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768, MD5withRSA \n\nJava 6 requires code changes in the JSSE component in addition to the java.security file modifications, so upgrading the JRE is the only solution.\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 v2 Guide [http:\/\/www.first.org\/cvss\/v2\/guide] \nOn-line Calculator v2 [http:\/\/nvd.nist.gov\/CVSS-v2-Calculator] \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] IBM Java SDK Security Bulletin [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21974193] ACKNOWLEDGEMENT\nCVE-2015-7575 was reported to IBM by Karthikeyan Bhargavan at INRIA in Paris, France \n\nCHANGE HISTORY\n 22 April 2016: Original version published\n29 April 2016: Altered CVE-2015-7575 scoring\n2 June 2016: Further correction to CVE-2015-7575 scoring \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=swg21982284]"}]},{"id":"TRAIN_Q573","question":"Why dbheap memory keeps increasing when I am running select count(*) for each table in my BLU database?\n\n\n\nI am running DB2 V11.1. It is a BLU database size of about 70T, most of the tables are column organized. I run select count(*) for each table, and finally got out of memory for dbheap. My question is:\n\n How to release the data in dbheap.\n","answer":"This memory allocation is persistent\/cached until the database deactivates or the table is dropped.","is_impossible":false,"contexts":[{"filename":"swg21986534.txt","text":"Title: IBM Newly accessed tables result in increasing of dbheap - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Newly accessed tables result in increasing of dbheap \n\nSYMPTOM\nFrom output of command \"db2pd -db <db name> -mempools\" you can find LogSz\/PhySz of the memory pool named \"dbh\" keeps on increasing.\n\n\nCAUSE\nThis is expected result. Every newly accessed table loads the tcb and has associated allocations for data, index, lob, compression dictionaries if applicable. This memory allocation is persistent\/cached until the database deactivates or the table is dropped.\n\nDIAGNOSING THE PROBLEM\nCollect \"db2pd -db showdb -memblocks 2 sort -alldbp\", you will find most of the the newly memory allocations are from File 1601762203 LOC 1025 and LOC 1015: \n\nDay 1:\n\nAll memory consumers in Database memory set:\nPoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File \n2 dbh 2502313088 51.03 59601 7.42 1025 1601762203\n2 dbh 1906996352 38.89 59601 7.42 1015 1601762203\n2 dbh 325096960 6.63 169321 21.08 2225 1235116617\n2 dbh 37055232 0.76 159296 19.84 3159 1235116617\n\nDay 2:\n\nAll memory consumers in Database memory set:\nPoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File \n2 dbh 2642441600 50.76 63266 7.16 1025 1601762203\n2 dbh 2027344256 38.95 63266 7.16 1015 1601762203\n2 dbh 356836992 6.86 185844 21.03 2225 1235116617\n2 dbh 40057088 0.77 174834 19.78 3159 1235116617\n\nNote, for different versions, LOC might be different, above LOC only applies to V9.7FP11.\n\nCollect \"db2pd -d showdb -tcbstats -alldbp\", you will see the number of tcb entries also keeps on increasing.\n\n\n\n\n\nRESOLVING THE PROBLEM\nThis is the expected result, once all tables in the database are accessed for at least one time, the memory increasing will stop."}]},{"id":"TRAIN_Q574","question":"Help with Security Bulletin: WMB and IIB are affected by information disclosure vulnerability (CVE-2017-1126)\n\nI need to understand details regarding Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by information disclosure vulnerability (CVE-2017-1126). Where can I find this information? ","answer":"CVEID: CVE-2017-1126 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1126]\nDESCRIPTION: IBM Integration Bus and WebSphere Message Broker could allow an unauthorized user to obtain sensitive information about software versions, which could lead to further attacks.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/121341 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/121341] 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)","is_impossible":false,"contexts":[{"filename":"swg22008470.txt","text":"Title: IBM Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by information disclosure vulnerability (CVE-2017-1126) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus and WebSphere Message Broker have addressed the vulnerability that would allow an unauthorized user to obtain sensitive information about software versions, and which could lead to further attacks. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-1126 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1126]\nDESCRIPTION: IBM Integration Bus and WebSphere Message Broker could allow an unauthorized user to obtain sensitive information about software versions, which could lead to further attacks.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/121341 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/121341] 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 Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9 \n\n WebSphere Message Broker V8.0.0.0 - V8.0.0.8\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10.0.0.0-V10.0.0.9 IT18731\/\nIT21161 The APARs are 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-V9.0.0.8 IT18731\/\nIT21161 The APARs are 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] WebSphere Message Broker V8.0.0.0 -V8.0.0.8 IT18731\/\nIT21161 APAR IT18731 is available in fix pack 8.0.0.9 http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043806 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043806]\n\nFor a fix for APAR IT21161, please contact IBM support. \nWebsphere Message Broker V8 is no longer in full support; IBM recommends upgrading to a fixed, supported version\/release\/platform of the product. If you are an extended support customer and require a fix, this is available only for the latest fixpack (8.0.0.9). To obtain the fix contact IBM support. \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 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\nRELATED INFORMATION\n# \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"}]},{"id":"TRAIN_Q575","question":"Why dbheap memory keeps increasing when I am running select count(*) for each table in my BLU database?\n\n\n\nI am running DB2 V11.1. It is a BLU database size of about 70T, most of the tables are column organized. I run select count(*) for each table, and finally got out of memory for dbheap. My questionn is:\n\n What data is stored in the dbheap ?\n\n ","answer":"This is expected result. Every newly accessed table loads the tcb and has associated allocations for data, index, lob, compression dictionaries if applicable. This memory allocation is persistent\/cached until the database deactivates or the table is dropped.","is_impossible":false,"contexts":[{"filename":"swg21986534.txt","text":"Title: IBM Newly accessed tables result in increasing of dbheap - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Newly accessed tables result in increasing of dbheap \n\nSYMPTOM\nFrom output of command \"db2pd -db <db name> -mempools\" you can find LogSz\/PhySz of the memory pool named \"dbh\" keeps on increasing.\n\n\nCAUSE\nThis is expected result. Every newly accessed table loads the tcb and has associated allocations for data, index, lob, compression dictionaries if applicable. This memory allocation is persistent\/cached until the database deactivates or the table is dropped.\n\nDIAGNOSING THE PROBLEM\nCollect \"db2pd -db showdb -memblocks 2 sort -alldbp\", you will find most of the the newly memory allocations are from File 1601762203 LOC 1025 and LOC 1015: \n\nDay 1:\n\nAll memory consumers in Database memory set:\nPoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File \n2 dbh 2502313088 51.03 59601 7.42 1025 1601762203\n2 dbh 1906996352 38.89 59601 7.42 1015 1601762203\n2 dbh 325096960 6.63 169321 21.08 2225 1235116617\n2 dbh 37055232 0.76 159296 19.84 3159 1235116617\n\nDay 2:\n\nAll memory consumers in Database memory set:\nPoolID PoolName TotalSize(Bytes) %Bytes TotalCount %Count LOC File \n2 dbh 2642441600 50.76 63266 7.16 1025 1601762203\n2 dbh 2027344256 38.95 63266 7.16 1015 1601762203\n2 dbh 356836992 6.86 185844 21.03 2225 1235116617\n2 dbh 40057088 0.77 174834 19.78 3159 1235116617\n\nNote, for different versions, LOC might be different, above LOC only applies to V9.7FP11.\n\nCollect \"db2pd -d showdb -tcbstats -alldbp\", you will see the number of tcb entries also keeps on increasing.\n\n\n\n\n\nRESOLVING THE PROBLEM\nThis is the expected result, once all tables in the database are accessed for at least one time, the memory increasing will stop."}]},{"id":"TRAIN_Q576","question":"JD Edwards Adapter supported in BPM 8.5.6?\n\n\n\nHi experts, I have a question about the support for the JD Edwards Adapter in BPM 8.5.6, because the Infocenter for BPM 8.5.6 doesn't have a detailed explanation for this adapter unlike infocenter for BPM 8.5.5, I just wondering which is the most current version of JD Edwards supported in this Adapter ?","answer":"Supported JD Edwards versions * EnterpriseOne Tools 8.97, 8.98 ( JD Edwards Adapter Inbound, Outbound operations) \n * EnterpriseOne Tools 9.1 ( JD Edwards Adapter from Version 7.5.0.2 onwards) \n * EnterpriseOne Tools 9.1.4 ( JD Edwards Adapter from Version 7.5.0.5_IF06 onwards)","is_impossible":false,"contexts":[{"filename":"swg27021012.txt","text":"Title: IBM WebSphere Adapter for JD Edwards, Version 7.5 system requirements - United States\n\nText:\nDSRDoc; DetailedSystemRequirementsDocument PRODUCT DOCUMENTATION\n\nABSTRACT\n This techdoc lists the system requirements for IBM WebSphere Adapter for JD Edwards, version 7.5. \n\nCONTENT\nThe information provided here describes the minimum product levels you need installed before opening a problem report with the WebSphere Adapters support team. Because other products frequently ship fixes, updates, and new releases, it is not possible to test every configuration. In general, you can install and run updates to supported products if those updates are compatible with later versions. This statement does not apply to enterprise information system (EIS) product versions and their dependencies. Specific cases where this statement is not applicable are indicated where relevant. \n\nSupported JD Edwards versions * EnterpriseOne Tools 8.97, 8.98 ( JD Edwards Adapter Inbound, Outbound operations) \n * EnterpriseOne Tools 9.1 ( JD Edwards Adapter from Version 7.5.0.2 onwards) \n * EnterpriseOne Tools 9.1.4 ( JD Edwards Adapter from Version 7.5.0.5_IF06 onwards)\n\nNote : For v9.1.4,the JDE user login password and security password should be same. Otherwise, there may be a chance of hitting the login issues while using the real time events and XML list query\n\nNote: The adapter is compatible with any version of JD Edwards EnterpriseOne that works with the supported versions of EnterpriseOne Tools.\nEnterpriseOne Tools 8.9 SP1, 8.9 SP2, 8.93, 8.94, 8.95, 8.96 are supported only for application design, development, and testing; there is no support for production use. Those versions are deprecated because Oracle does not support them. Supported databases All databases supported by the products listed in the Software requirements section. \n\nHARDWARE \/ SOFTWARE REQUIREMENTS\nTAB NAVIGATION\n * AIX - selected tab, \n * HP \n * IBM i \n * Linux \n * Solaris \n * Windows \n\nTAB NAVIGATION\n * AIX \n\n\n\n\nOUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable AIX OS DVD\/CD-ROM Drive\n\nMemory All Applicable AIX OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor All Applicable AIX OS IBM POWER family of processors\n\nSystem z All Applicable AIX OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes AIX Platform listing of supported OS AIX 5.3 TL7 POWER System Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System AIX 5.3 TL9 POWER System Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System AIX 6.1 TL1 POWER System Bitness: 64 Bit Tolerate, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System AIX 6.1 TL2 POWER System Bitness: 64 Bit Tolerate, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System AIX 6.1 TL4 POWER System Bitness: 64 Bit Tolerate, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System AIX 7.1 POWER System Bitness: 64 Bit Tolerate, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable AIX OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable AIX OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable AIX OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable AIX OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable AIX OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable AIX OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable AIX OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable AIX OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable AIX OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable AIX OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable AIX OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable AIX OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable AIX OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable AIX OS Virtualization IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version All Applicable AIX OS See Note #2 IBM PowerVM Hypervisor (LPAR, DPAR, Micro-Partition) any supported version All Applicable AIX OS See Note #2 WPAR: Product installed in System Workload Partition AIX 6.1 AIX 6.1 TL1 POWER System Specifically AIX 6.1 TL4 SP2 or higher\n\nWPAR: Product installed in System Workload Partition AIX 6.1 AIX 6.1 TL1 POWER System Added on 8\/17: In Alignment with WPS 7.x support statement\n\nWPAR: Product installed in System Workload Partition AIX 7.1 All Applicable AIX OS Back to top \n\n\n\n\nTAB NAVIGATION\n * HP-UX \n\n\n\n\nOUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable HP OS DVD\/CD-ROM Drive\n\nMemory All Applicable HP OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor All Applicable HP OS Intel Itanium 2 processor\n\nSystem z All Applicable HP OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes HP Platform listing of supported OS HP-UX 11i v2 IA64 Bitness: 64 Bit Exploit\nDeployment Role: Server\nHardware platform: IA64 HP-UX 11i v2 PA-RISC Bitness: 64 Bit Tolerate\nDeployment Role: Server\nHardware platform: PA-RISC HP-UX 11i v3 IA64 Bitness: 64 Bit Exploit\nDeployment Role: Server\nHardware platform: IA64 HP-UX 11i v3 PA-RISC Bitness: 64 Bit Tolerate\nDeployment Role: Server\nHardware platform: PA-RISC Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable HP OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable HP OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable HP OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable HP OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable HP OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable HP OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable HP OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable HP OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable HP OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable HP OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable HP OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable HP OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable HP OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable HP OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable HP OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable HP OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable HP OS Virtualization WPAR: Product installed in System Workload Partition AIX 7.1 All Applicable HP OS Back to top \n\n\n\n\nTAB NAVIGATION\n * IBM i \n\n\n\n\nOUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable IBM i OS DVD\/CD-ROM Drive\n\nMemory All Applicable IBM i OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor All Applicable IBM i OS Any system from the IBM POWER5 family of processors or later; one processing unit or more\n\nSystem z All Applicable IBM i OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes IBM i Platform listing of supported OS IBM i 5.4 POWER System Bitness: 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System IBM i 6.1 POWER System Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System IBM i 7.1 POWER System Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: POWER System Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable IBM i OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable IBM i OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable IBM i OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable IBM i OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable IBM i OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable IBM i OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable IBM i OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable IBM i OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable IBM i OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable IBM i OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable IBM i OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable IBM i OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable IBM i OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable IBM i OS Virtualization WPAR: Product installed in System Workload Partition AIX 7.1 All Applicable IBM i OS Back to top \n\n\n\n\nTAB NAVIGATION\n * Red Hat Enterprise Linux (RHEL) \n\n\n\n\nOUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable Linux OS DVD\/CD-ROM Drive\n\nMemory All Applicable Linux OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor Red Hat Enterprise Linux (RHEL) 5.0 Update 6 Advanced Platform x86-64 Intel Pentium at 3GHz for single core system, 2.4GHz for dual cores or more; Intel EM64T or AMD opteron.\n\nSystem z All Applicable Linux OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Linux Platform listing of supported OS Red Hat Enterprise Linux (RHEL) 4.0 Update 6 AS\/ES x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Red Hat Enterprise Linux (RHEL) 5.0 Update 1 Advanced Platform x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Linux OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Linux OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Linux OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Linux OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Linux OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Linux OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Linux OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Linux OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Linux OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Linux OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Linux OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Linux OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Linux OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Linux OS Virtualization IBM PR\/SM any version All Applicable Linux OS Adapters will provide support in alignment with WPS support statement\n\nIBM PR\/SM any version All Applicable Linux OS See Note #2 Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 All Applicable Linux OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 All Applicable Linux OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.5 All Applicable Linux OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.5 All Applicable Linux OS VMware ESX 4.0 Red Hat Enterprise Linux (RHEL) 4.0 Update 6 AS\/ES x86-32,\nRed Hat Enterprise Linux (RHEL) 5.0 Update 1 Advanced Platform x86-64 Adapters will provide support in alignment with WPS support statement\n\nVMware ESX 4.0 All Applicable Linux OS Applicable to Linux on x86-32 and x86-64\n\nVMware ESXi 4.0 All Applicable Linux OS Applicable to Linux on x86-32 and x86-64\n\nVMware ESXi 4.0 Red Hat Enterprise Linux (RHEL) 4.0 Update 6 AS\/ES x86-32,\nRed Hat Enterprise Linux (RHEL) 5.0 Update 1 Advanced Platform x86-64 Adapters will provide support in alignment with WPS support statement\n\nWPAR: Product installed in System Workload Partition AIX 7.1 All Applicable Linux OS z\/VM 6.1 (overview) [http:\/\/www.vm.ibm.com\/] All Applicable Linux OS z\/VM 6.1 (overview) [http:\/\/www.vm.ibm.com\/] All Applicable Linux OS See Note #2 Back to top \n\n\n\n\nTAB NAVIGATION\n * Solaris \n\n\n\n\nOUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable Solaris OS DVD\/CD-ROM Drive\n\nMemory All Applicable Solaris OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor All Applicable Solaris OS Sun Solaris operating environment compatible SPARC at 440Mhz or later\n\nSystem z All Applicable Solaris OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Solaris Platform listing of supported OS Solaris 10 SPARC Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: SPARC Solaris 9 SPARC Bitness: 64 Bit Tolerate, 32 Bit\nDeployment Role: Server\nHardware platform: SPARC Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Solaris OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Solaris OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Solaris OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Solaris OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Solaris OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Solaris OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Solaris OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Solaris OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Solaris OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Solaris OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Solaris OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Solaris OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Solaris OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Solaris OS Virtualization WPAR: Product installed in System Workload Partition AIX 7.1 All Applicable Solaris OS Back to top \n\n\n\n\nTAB NAVIGATION\n * Windows Server 2003 \n * Windows Server 2008 \n * Windows 7* \n\n\n\n\nNote*: The Support for Windows 7 has been added under release v7.5.0.2 OUTLINE\n * Hardware Requirements * Media Drive \n * Memory \n * Processor \n * System z \n \n \n * Software Requirements * Operating System \n * Application Servers \n * Connectors \n * Development Tools \n \n \n * Optional Supported Software * License Use Management \n * Support Assistant \n * Virtualization \n \n \n\n\n\n\nHardware Requirements Group Applicable OS Notes Media Drive All Applicable Windows OS DVD\/CD-ROM Drive\n\nMemory All Applicable Windows OS Minimum 1GB physical memory; 2GB recommended\n\nProcessor All Applicable Windows OS Intel Pentium at 3GHz for single core system, 2.4GHz for dual cores or more; Intel EM64T or AMD opteron.\n\nSystem z All Applicable Windows OS System z processor\n\n Back to top \n\nOperating Systems Operating System Attributes Notes Windows Platform listing of supported OS Windows Server 2003 R2 SP2 Datacenter Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 R2 SP2 Enterprise Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 R2 SP2 Standard Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 SP1 Datacenter Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 SP1 Enterprise Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 SP1 Standard Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 SP2 Datacenter Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2003 SP2 Enterprise Edition x86-32 Bitness: 32 Bit\nDeployment Role: Server\nHardware platform: x86-32 Windows Server 2008 Datacenter Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows Server 2008 Enterprise Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows Server 2008 R2 Datacenter Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows Server 2008 R2 Enterprise Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows Server 2008 R2 Standard Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows Server 2008 Standard Edition x86-64 Bitness: 64 Bit Tolerate, 32 Bit, 64 Bit Exploit\nDeployment Role: Server\nHardware platform: x86-64 Windows 7 Enterprise x86-32 Bitness: 32 Bit\nDeployment Role: Desktop\nHardware platform: x86-32 Windows 7 Enterprise x86-64 Bitness: 64 Bit Tolerate\nDeployment Role: Desktop\nHardware platform: x86-64 Windows 7 Professional x86-32 Bitness: 32 Bit\nDeployment Role: Desktop\nHardware platform: x86-32 Windows 7 Professional x86-64 Bitness: 64 Bit Tolerate\nDeployment Role: Desktop\nHardware platform: x86-64 Windows 7 Ultimate x86-32 Bitness: 32 Bit\nDeployment Role: Desktop\nHardware platform: x86-32 Windows 7 Ultimate x86-64 Bitness: 64 Bit Tolerate\nDeployment Role: Desktop\nHardware platform: x86-64 Back to top \n\nSoftware Requirements Group Product Applicable OS Notes Application Servers IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Windows OS See Note #1 IBM Business Process Manager Advanced 7.5 and future releases, mod levels and fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced] All Applicable Windows OS See Note #3 WebSphere Application Server 7.0.0.17 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS See Note #1 WebSphere Application Server 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS See Note #1 WebSphere Application Server for z\/OS 8.0 (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/zos_os390\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS See Note #1 WebSphere Application Server Network Deployment 8.0 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/webservers\/appserv\/was\/network\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Application_Server] All Applicable Windows OS See Note #1 Connectors WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Windows OS See Note #1 WebSphere Enterprise Service Bus 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/wsesb\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/WebSphere_Enterprise_Service_Bus] All Applicable Windows OS See Note #3 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Windows OS See Note #1 WebSphere Enterprise Service Bus for z\/OS 7.5 and future fix packs All Applicable Windows OS See Note #3 Development Tools IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Windows OS See Note #1 IBM Integration Designer 7.5 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/integration\/integration-designer\/] (support) [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Integration_Designer] All Applicable Windows OS See Note #3 Rational Application Developer for WebSphere Software 8.0.3 and future fix packs (overview) [http:\/\/www.ibm.com\/software\/products\/us\/en\/application] (support) [http:\/\/www.ibm.com\/software\/awdtools\/developer\/application\/support\/index.html] All Applicable Windows OS Back to top \n\nOptional Supported Software Group Product Applicable OS Notes License Use Management Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Windows OS Tivoli License Compliance Manager 2.3 (overview) [http:\/\/www.ibm.com\/software\/tivoli\/products\/license-mgr\/] (support) [http:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliLicenseManager.html] All Applicable Windows OS Support Assistant IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Windows OS IBM Support Assistant 4.1 (overview) [http:\/\/www-306.ibm.com\/software\/support\/isa\/] (support) [http:\/\/www.ibm.com\/software\/awdtools\/isa\/support\/] All Applicable Windows OS Virtualization Red Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 All Applicable Windows OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.4 All Applicable Windows OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.5 All Applicable Windows OS In Alignment with WPS 7.x support statement\n\nRed Hat KVM as delivered with Red Hat Enterprise Linux (RHEL) 5.5 All Applicable Windows OS VMware ESX 4.0 All Applicable Windows OS Adapters will provide support in alignment with WPS support statement\n\nVMware ESX 4.0 All Applicable Windows OS Applicable to Linux on x86-32 and x86-64\n\nVMware ESXi 4.0 All Applicable Windows OS Applicable to Linux on x86-32 and x86-64\n\nVMware ESXi 4.0 All Applicable Windows OS Adapters will provide support in alignment with WPS support statement\n\nWPAR: Product installed in System Workload Partition AIX 7.1 All Applicable Windows OS Back to top \n\n\n\n\nNOTES\n * Note #1: For tooling purposes, the adapter code can be obtained from the Rational Application Developer product.\n For runtime purposes, a stand-alone adapter PID must be purchased for use on WebSphere Application Server. To obtain a stand-alone adapter PID, go to Passport Advantage [http:\/\/www.ibm.com\/software\/passportadvantage] and use Product ID (PID) Code 5724-T75.\n \n This adapter is supported only for development and unit testing on the operating systems supported by the tooling products. This adapter is supported only for deployment and production on the operating systems supported by the runtime server products. To ensure compatibility, always consult the system requirements supported by these complementary products.\n \n \n * Note #2: Adapters will provide support in alignment with WPS support statement\n \n \n * Note #3: This adapter is supported only for development and unit testing on the operating systems supported by the tooling products. This adapter is supported only for deployment and production on the operating systems supported by the runtime server products. To ensure compatibility, always consult the system requirements supported by these complementary products."}]},{"id":"TRAIN_Q577","question":"My SystemOut.log is overfilled by messages SECJ0371W (LTPA token expired). I am sick and tired of them. Can I disable them?\n\nMy SystemOut.log is overfilled by messages SECJ0371W (LTPA token expired). I am sick and tired of them. Can I disable them? ","answer":"A security custom property will be used to disable the logging\n of the SECJ0371W message. Setting this property to true will\n disable future logging of the message.\n com.ibm.websphere.security.ltpa.disableSECJ0371W=true","is_impossible":false,"contexts":[{"filename":"swg1PI54477.txt","text":"Title: IBM PI54477: ADD ABILITY TO DISABLE LOGGING OF SECJ0371W EXPIRED LTPA TOKEN MESSAGES - United States\n\nText:\n FIXES ARE AVAILABLE\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 * SECJ0371W messages fill the logs and the customer does not find\n them useful. They would like to turn off the logging of these\n messages.\n \n WL3SEC\n \n \n \n \n \n\nLOCAL FIX\n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server V8.0 and higher. *\n ****************************************************************\n * PROBLEM DESCRIPTION: Users would like to be able to disable *\n * SECJ0371W messages *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n SECJ0371W messages log every event of an LTPA token\n expiration. LTPA token expirations are expected under normal\n circumstances. Although at times these messages can alert\n customers to unexpected conditions. For instance a client\n continues to send an expired token repeatedly.\n The customer is requesting the ability to disable the logging\n of the SECJ0371W message.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * A security custom property will be used to disable the logging\n of the SECJ0371W message. Setting this property to true will\n disable future logging of the message.\n com.ibm.websphere.security.ltpa.disableSECJ0371W=true\n \n The fix for this APAR is currently targeted for inclusion in\n fix packs 8.0.0.13 and 8.5.5.10. 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 PI54477\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-12-18\n \n \n * CLOSED DATE\n 2016-02-24\n \n \n * LAST MODIFIED DATE\n 2016-07-12\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"}]},{"id":"TRAIN_Q578","question":"Does IBM DataPower Gateway Appliance support the HTTP CONNECT method?\n\nDoes IBM DataPower Gateway Appliance support the HTTP CONNECT method?\n","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\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.","is_impossible":false,"contexts":[{"filename":"swg21612222.txt","text":"Title: IBM How to Proxy SSL request from DataPower to Remote Proxy Server? - United States\n\nText:\nForward 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."}]},{"id":"TRAIN_Q579","question":"Trouble downloading SPSS Statistics free trial\n\nI am trying to download the free trial version of SPSS Statistics version 24. I'm a graduate student and want to try it out on my Mac OS X 10.9.5 laptop. However, when I get to the \"confirm\" part, it keeps showing me an error message saying \"can't save profile.\" How do you go about fixing this and getting it installed? Thanks! ","answer":"E) Apple Macintosh OSC Mavericks (10.9) \n\nSupport for IBM SPSS Statistics 23 and IBM SPSS Statistics 22","is_impossible":false,"contexts":[{"filename":"swg21507587.txt","text":"Title: IBM What are the supported Apple Macintosh Operating System Versions for IBM SPSS Statistics? - United States\n\nText:\nSPSS 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]"}]},{"id":"TRAIN_Q580","question":"WebSphere MQ Hypervisor Edition requires customer action for the GNU C library (glibc) vulnerabilities (CVE-2015-1472 & CVE-2013-7423)\n\nWebSphere MQ Hypervisor Edition requires customer action for the GNU C library (glibc) vulnerabilities (CVE-2015-1472 & CVE-2013-7423)\nWhere can I find additional information on what action is required? ","answer":"IBM strongly recommends that you should contact Red Hat to obtain fixes and install fixes for Red Hat Enterprise Linux (RHEL).","is_impossible":false,"contexts":[{"filename":"swg21902248.txt","text":"Title: IBM Action required for IBM WebSphere MQ Hypervisor Edition for RedHat Enterprise Linux Server for the GNU C library (glibc) vulnerabilities (CVE-2015-1472 & CVE-2013-7423) - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n WebSphere MQ Hypervisor Edition requires customer action for the GNU C library (glibc) vulnerabilities (CVE-2015-1472 & CVE-2013-7423) \n\nCONTENT\nWebSphere MQ Hypervisor Edition Versions 7.0.1 and 7.5 ship with Red Hat Enterprise Linux (RHEL) that is vulnerable to GNU C library (glibc) vulnerabilities (CVE-2015-1472 & CVE-2013-7423). \n\nRemediation\/Fixes \n\n IBM strongly recommends that you should contact Red Hat to obtain fixes and install fixes for Red Hat Enterprise Linux (RHEL). \n\nRELATED INFORMATION\n Red Hat vulnerabilities by CVE name [https:\/\/access.redhat.com\/security\/cve\/]\nA Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21903158]"}]},{"id":"TRAIN_Q581","question":"OOM exception thrown when trying to configure an ITCAM for WAS 7.2 Data Collector\n\nI am trying to configure an ITCAM for WAS 7.2.0.0.x DC using config.sh, but getting OOM exceptions, as following:\n\n.\/config.sh\n\nLog file name: \/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/data\/config-trace.log.\n\nList of TCP\/IP interfaces discovered:\n\n 1. ...\n Enter a number [default is: 1]:\n 1\n JVMDUMP039I Processing dump event \"systhrow\", detail \"java\/lang\/OutOfMemoryError\" at 2017\/08\/22 12:27:03 - please wait.\n....\n java.lang.OutOfMemoryError: java.lang.OutOfMemoryError: Java heap space\n\nLooking at the javacore.txt files, I can see that this is the command throwing an OOM\n\n1CICMDLINE \/opt\/IBM\/ITM\/JRE\/aix526\/bin\/java -classpath \/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/bin\/jython\/jython.jar:\/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/bin\/lib\/installbundle.jar -Xms256m -Xmx256m -Dpython.path=\/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/bin\/lib:\/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/bin\/lib org.python.util.jython \/opt\/IBM\/ITM\/dchome\/7.2.0.0.10\/bin\/config.py\n\nHow could I solve this?","answer":"The Java heap settings are set in the config.sh script in the JAVA_OPTS line. For AIX, the default settings are way too low. \n\nPlease do these changes to get it to work: \n\nMake a backup of the config.sh file, then edit it. \n\nSearch for the following line JAVA_OPTS in the config.sh file:[\/support\/docview.wss?uid=swg21959444&aid=1] [\/support\/docview.wss?uid=swg21959444&aid=1] \n\nChange the JAVA_OPTS=\"-Xms256m -Xmx256m\" to a higher value like this: \n\nJAVA_OPTS=\"-Xms512m -Xms512m\" \n\nSave file, restart the config again and see if it works now without any Out of Java heap messages.","is_impossible":false,"contexts":[{"filename":"swg21959444.txt","text":"Title: IBM Configuration of the ITCAM agent on AIX leads to Java heap errors. - United States\n\nText:\nJAVA_OPTS CAMADALL CAMADINST java heap java.lang.OutOfMemoryError CFG5045E TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nPROBLEM(ABSTRACT)\n Configuration of the ITCAM agent on AIX leads to Java heap errors. \n\nSYMPTOM\nDuring configuration of the YN agent, you will see these errors: \n\njava.lang.OutOfMemoryError: Java heap space\nat org.python.core.PyException.tracebackHere(PyException.java:158)\nat org.python.core.PyException.tracebackHere(PyException.java:145)\nat org.python.core.PyTableCode.call(PyTableCode.java:169)\nat org.python.core.PyBaseCode.call(PyBaseCode.java:301)\nat org.python.core.PyBaseCode.call(PyBaseCode.java:141)\nat org.python.core.PyFunction.__call__(PyFunction.java:327)\nat org.python.core.PyFunction.__call__(PyFunction.java:322)\nat org.python.core.PyInstance.ifindfunction(PyInstance.java:168)\nat org.python.core.PyInstance.__findattr_ex__(PyInstance.java:148)\nat org.python.core.PyObject.__findattr__(PyObject.java:863)\nat org.python.core.PyInstance.invoke_ex(PyInstance.java:328)\n\njava.lang.OutOfMemoryError: java.lang.OutOfMemoryError: Java heap space\nCFG5045E The configuration process is being terminated due to errors listed above.\n\n\nCAUSE\nLow heap settings in the JAVA_OPTS parameter.\n\n\nENVIRONMENT\nAIX - Distributed\n\n\n\nRESOLVING THE PROBLEM\nThe Java heap settings are set in the config.sh script in the JAVA_OPTS line. For AIX, the default settings are way too low. \n\nPlease do these changes to get it to work: \n\nMake a backup of the config.sh file, then edit it. \n\nSearch for the following line JAVA_OPTS in the config.sh file:[\/support\/docview.wss?uid=swg21959444&aid=1] [\/support\/docview.wss?uid=swg21959444&aid=1] \n\nChange the JAVA_OPTS=\"-Xms256m -Xmx256m\" to a higher value like this: \n\nJAVA_OPTS=\"-Xms512m -Xms512m\" \n\nSave file, restart the config again and see if it works now without any Out of Java heap messages.\n\n \n\nPRODUCT ALIAS\/SYNONYM\n ITCAMfAD ITCAM4AD ITCAM for App Diagnostics"}]},{"id":"TRAIN_Q582","question":"Problems downloading SPSS Statistics Premium Grad Pack v.24- Mac\n\nPurchased SPSS Statistics Premium Grad Pack v.24. for Mac from THINKedu.com. Have tried a dozen times to download it but fails. Tried using wifi, direct ethernet connection, Firefox, Safari, and Chrome incognito, with no other programs running in background. Have purchased previous versions from another vendor multiple times without an issue. THINKedu would not offer additional support, directing me to contact IBM instead. IBM Software Support @ (919) 864-3512 said \"there is no phone support for students for SPSS\" and directed me to ask a question here instead. Saw a suggestion for an installer on another post; seems to lead to a trial version- is that the best idea? ","answer":"If you are looking for a free trial version of SPSS Statistics, go here: Free Trial Version","is_impossible":false,"contexts":[{"filename":"swg24041224.txt","text":"Title: IBM Downloading IBM SPSS Statistics 24 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n Downloading IBM SPSS Statistics 24 \n\nDOWNLOAD DESCRIPTION\nIBM\u00ae SPSS\u00ae Statistics is the world\u2019s leading statistical software used to solve business and research problems by means of ad-hoc analysis, hypothesis testing, and predictive analytics. Organizations use IBM SPSS Statistics to understand data, analyze trends, forecast and plan to validate assumptions and drive accurate conclusions. \n\nIf you are looking for a free trial version of SPSS Statistics, go here: Free Trial Version [http:\/\/www.ibm.com\/analytics\/us\/en\/technology\/predictive-analytics\/#ibm-spss-stats-modeler-trials]\n\nDetailed information on getting started, managing your account, downloading and installing, and licensing is available here: GetSPSS [http:\/\/www.ibm.com\/software\/analytics\/spss\/support\/get_spss.html]\n\nComplete documentation for IBM SPSS Statistics 24.0 is available here: IBM SPSS Statistics 24 Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSLVMB_24.0.0]\n\nPDF versions of the installation instructions and manuals are also available here: IBM SPSS Statistics 24 Documentation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27047033]\n\n\nTo download a product, go to the IBM Passport Advantage\u00ae Web Site [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/sdma\/SDMA?PO=DOWNLOAD_FIND_BY_PART_NUMBER] and then:\n\n\n 1. Do one of the following:\n If you are a returning customer, sign in.\n If you are a new customer, register. \n 2. If the Software download & media access window appears, click I agree. \n 3. In the Find downloads & media window, click Download finder. \n 4. Under Download finder, select the download you want, and click Continue. \n 5. Under Select criteria, select a language and one or more platforms. \n 6. Under Download options, select the options you want, and click Continue. \n 7. Under Review \u201cCurrent version\u201d downloads, expand Current version and under Description, select the download you want, expand it and select the items you want. \n 8. If applicable, under Select optional downloads, expand and select the items you want. \n 9. Under Review downloading specifics, update the Download method or the Download location, if you want, and then click I agree, and click Download now. \n 10. In the Initial Setup dialog, change the Default download location, if you want. \n 11. If you are prompted, click OK to create the directory where you want the downloaded items to be stored. \n 12. Click OK to begin the download.\n\n\nUse the plus sign icon to expand the files in the download of your choice in order to avoid downloading unnecessary files. \n\nWhen the download has finished, Download complete appears in the Download Director dialog. The required and optional parts for each product are listed and described in detail. There is an option to download each licensed eAssembly. Each eAssembly contains all of the required and optional downloads needed for a particular product and platform combination.\n\nDownloading and assembling the product\n1. Download all of the parts that you need, both required and optional.\n2. Unpack each of the parts into a single temporary directory on your system. \n3. Follow the installation instructions provided in the download to install the product. \n\nFor assistance with all questions on generating and accessing authorization codes, including how to enable additional add-on modules that you purchase, go to:\nhttp:\/\/public.dhe.ibm.com\/software\/analytics\/spss\/licensing\/Auth_Codes_092910_2.html [http:\/\/public.dhe.ibm.com\/software\/analytics\/spss\/licensing\/Auth_Codes_092910_2.html]\n\nAny customer with an active support contract can seek activation assistance by logging a support request online or by phone via links available at www.ibm.com\/planetwide.\n\nDownload Options\nYou can download entire eAssemblies or individual eImages. The eAssemblies contain all required and optional eImages for each download package. This section lists the eAssemblies. The complete list of eAssemblies and associated eImages is provided below.\n\nIBM SPSS Statistics 24.0 Desktop\nMultilingual\nWindows: CRZ0ZML\nMac OS: CRZ10ML\nLinux: CRZ11ML\n\nFor Windows, there are 32-bit and 64-bit versions of the product eImage. You only need the one that is appropriate for your computer.\n\n\nIBM SPSS Statistics Developer\nMultilingual\nWindows: CRZ1AML\nMac OS: CRZ1BML\nLinux: CRZ1CML\n\nFor Windows, there are 32-bit and 64-bit versions of the product eImage. You only need the one that is appropriate for your computer.\n\nIBM SPSS Desktop and Developer Documentation\nMultilingual\nAll platforms: CRZ0WML\nThe installation instructions and manuals for IBM SPSS Statistics Desktop and Developer. This includes installation instructions for all supported platforms for single user installation, site license installation and administration, network license (concurrent license) installation and administration, and data access pack installation (for database access).\n\nInstallation instructions for all platforms and all languages are contained in a single eImage. Manuals in PDF form are available in separate eImages for each language.\n\nIBM SPSS Statistics Data Drivers\nMultilingual\nAll platforms: CRZ0XML\nDrivers to support various data sources in IBM SPSS Statistics Desktop, Developer, and Server. \n\nNote: This eAssembly also contains \u201cIBM SPSS Statistics Data File Drivers\u201d. The Statistics data file drivers allow you to read SPSS Statistics (.sav) data files in applications that support Open Database Connectivity (ODBC) or Java Database Connectivity (JDBC). This is optional. Only download it if you need it.\n\nIBM SPSS Statistics Concurrent User Licensing Server \nMultilingual\nAll platforms: CRZ0YEN\nLicense managers and hardware keys for IBM SPSS Statistics Desktop and Developer. \n\nYou will need this if you purchased software that requires a hardware key, or you are an SPSS administrator at a site that purchased concurrent licenses. If you are not aware of either of those conditions, then you don\u2019t need it.\n\nIf you are an SPSS administrator at a site that purchased concurrent licenses, download the Sentinel License Manager corresponding to the operating system of the computer where you plan to install it. \n\nIBM SPSS Statistics Server\nEnglish\nWindows: CRZ15ML\nLinux for System z: CRZ16ML\nLinux: CRZ18ML\nLinux for System p LE: CRZ17ML\nAIX: CRZ19ML\n\nIBM SPSS Statistics Server is available only in English.\n\nYou need to download the correct eImage for your server computer\u2019s operating system. \n\nIBM SPSS Visualization Designer 1.0.3 \nEnglish\nWindows: CRCQ9EN\n\nIBM SPSS SamplePower 3.0.1\nEnglish\nWindows: CRNK7EN\nA desktop application that helps you to find the best sample size for your research.\n\nComplete list of all eAssemblies and eImages\nThe following table list all the parts available for IBM SPSS Statistics 24.0.\n\n\n\n\nParts and Platform Part Number Category IBM SPSS Statistics Desktop 24.0 Documentation Multilingual eAssembly CRZ0WML IBM SPSS Statistics Client\/Developer Installation Documentation 24.0 Multilingual CN99SML Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 English CN99HEN Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 French CN99IFR Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 German CN99JDE Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Italian CN99KIT Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Japanese CN99LJA Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Russian CN99MRU Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Chinese-simplified CN99FSC Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Spanish CN99NES Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Chinese-traditional CN99GTC Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Korean CN99PKO Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Polish CN99QPL Documentation IBM SPSS Statistics Client\/Developer Documentation 24.0 Portuguese Brazilian CN99RBP Documentation \nIBM SPSS Statistics Data Drivers 24.0 Multilingual Multiplatform eAssembly CRZ0XML IBM SPSS Statistics Data File Drivers 24.0 Multiplatform Multilingual CN9ADML Optional IBM SPSS Data Access Pack 7.1.1 Multiplatform English CN8IUEN Optional IBM SPSS Statistics - Integration Plug-In for Microsoft .NET 32-bit 24.0 for Microsoft Windows CN98XML Optional IBM SPSS Statistics - Integration Plug-In for Microsoft .NET 64-bit 24.0 for Microsoft Windows CN98YML Optional \nIBM SPSS Statistics Concurrent User Licensing Server 24.0 English Multiplatform eAssembly CRZ0YEN IBM SPSS Concurrent Licensing Tools 9.6 - License Manager 64-bit AIX English CN997EN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Linux x86-64 English CN998EN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Microsoft Windows English CN99AEN Required IBM SPSS Concurrent Licensing Tools 9.6 - License Manager Mac English CN99BEN Required IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Microsoft Windows English CN99CEN Optional IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Linux x86-64 English CN99DEN Optional IBM SPSS Concurrent Licensing Tools 9.6 - Hardware Key Mac English CN99EEN Optional \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Microsoft Windows Multilingual eAssembly CRZ0ZML IBM SPSS Statistics Client 32-bit 24.0 Microsoft Windows Multilingual CN98SML Required IBM SPSS Statistics Client 64-bit 24.0 Microsoft Windows Multilingual CN98TML Required IBM SPSS Statistics Client 24.0 Microsoft Windows Multilingual (ISO Version) CNA15ML Optional IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Mac OS Multilingual eAssembly CRZ10ML IBM SPSS Statistics Client 24.0 Mac OS Multilingual CN98UML Required IBM SPSS Statistics Client 24.0 Mac OS Silent Multilingual CN98VML Required IBM SPSS Statistics Client 24.0 Mac OS Multilingual (ISO Version) CNA16ML Optional \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Linux x86-64 Multilingual eAssembly CRZ11ML IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual CN98WML Required IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual (ISO version) CNA17ML Optional \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Microsoft Windows Multilingual eAssembly CRZ12ML IBM SPSS Statistics Client 32-bit 24.0 Microsoft Windows Multilingual CN98SML Required IBM SPSS Statistics Client 64-bit 24.0 Microsoft Windows Multilingual CN98TML Required IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Mac OS Multilingual eAssembly CRZ13ML IBM SPSS Statistics Client 24.0 Mac OS Multilingual CN98UML Required IBM SPSS Statistics Client 24.0 Mac OS Silent Multilingual CN98VML Required \nIBM SPSS Statistics Desktop 24.0 for Base and all Modules Academic Linux x86-64 Multilingual eAssembly CRZ14ML IBM SPSS Statistics Client 24.0 Linux x86-64 Multilingual CN98WML Required \nIBM SPSS Statistics Server 24.0 Microsoft Windows Multilingual eAssembly CRZ15ML IBM SPSS Statistics Server 24.0 Microsoft Windows Multilingual CN99TML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation \nIBM SPSS Statistics Server 24.0 Linux on System z Multilingual eAssembly CRZ16ML IBM SPSS Statistics Server 24.0 Linux on System z Multilingual CN99UML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation \nIBM SPSS Statistics Server 24.0 Linux x86-64 Multilingual eAssembly CRZ18ML IBM SPSS Statistics Server 24.0 Linux x86-64 Multilingual CN99WML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation \nIBM SPSS Statistics Server 24.0 AIX Multilingual eAssembly CRZ19ML IBM SPSS Statistics Server 24.0 AIX Multilingual CN99XML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation \nIBM SPSS Statistics Server 24.0 Linux on System p LE Multilingual eAssembly CRZ17ML IBM SPSS Statistics Server 24.0 Linux on System p LE Multilingual CN99VML Required IBM SPSS Statistics Server Documentation 24.0 English CN99YEN Documentation \nIBM SPSS Statistics Developer 24.0 Microsoft Windows Multilingual eAssembly CRZ1AML IBM SPSS Statistics Developer 32-bit 24.0 Microsoft Windows Multilingual CN99ZML Required IBM SPSS Statistics Developer 64-bit 24.0 Microsoft Windows Multilingual CN9A0ML Required IBM SPSS Statistics Diagnostic Utility 24.0 Microsoft Windows Multilingual CN98ZML Recommended \nIBM SPSS Statistics Developer 24.0 Mac OS Multilingual eAssembly CRZ1BML IBM SPSS Statistics Developer 24.0 Mac OS Multilingual CN9A1ML Required IBM SPSS Statistics Developer 24.0 Mac OS Silent Multilingual CN9A2ML Required \nIBM SPSS Statistics Developer 24.0 Linux x86-64 Multilingual eAssembly CRZ1CML IBM SPSS Statistics Developer 24.0 Linux x86-64 Multilingual CN9A3ML Required \nIBM SPSS Statistics Desktop Integrated Student Edition 24.0 Multiplatform English eAssembly CRZ1MEN IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Microsoft Windows English CN994EN Required IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Mac OS English CN995EN Required IBM SPSS Statistics Desktop Integrated Student Edition 24.0 Multiplatform English (ISO Version) CN996EN Required \nIBM SPSS Visualization Designer 1.0.3 Microsoft Windows English eAssembly CRCQ9EN IBM SPSS Visualization Designer 1.0.3 License Instructions English CI20GEN Required IBM SPSS Visualization Designer 1.0.3 Microsoft Windows Installer English CZN4JEN Required IBM SPSS Visualization Designer Documentation 1.0.3 Microsoft Windows English CZN4KEN Documentation \nIBM SPSS SamplePower 3.0.1 Microsoft Windows English eAssembly CRNK7EN IBM SPSS SamplePower 3.0.1 Microsoft Windows English CIP6XEN Required IBM SPSS SamplePower Documentation 3.0 Microsoft Windows English CZN4IEN Documentation \nIBM SPSS Statistics 24.0 Collaboration and Deployment Services 8.0 Multiplatforms Multilingual eAssembly CRZ0VML IBM SPSS Statistics 24.0 Collaboration and Deployment Services Adapter 8.0 Multiplatforms Multilingual CN9ACML Optional IBM SPSS Collaboration and Deployment Services Deployment Manager 8.0 Microsoft Windows Multilingual CN9D6ML Optional"}]},{"id":"TRAIN_Q583","question":"Why does the ITCAM for AD Managing GUI install fail with an end-of-file message?\n\nI am trying to install the ITCAM for AD Managing server and I am seeing the following error when doing either 'launchpad.sh' or 'silent_MS_linux.bin': Initializing InstallShield Wizard........ Launching InstallShield Wizard........\n\n.\/setup_MS_lin.bin: line 1926: warning: here-document at line 1926 delimited by end-of-file (wanted `\/dev\/null')\n\nThe installer is unable to run in graphical mode. Try running the installer with the -console for -silent flag.","answer":"CAUSE\nMissing Linux system libraries.","is_impossible":false,"contexts":[{"filename":"swg21985630.txt","text":"Title: IBM Using launchpad.sh or silent_MS_linux.bin results in end-of-file message. - United States\n\nText:\nITCAM compat-libstdc++ libstdc++ libraries silent_MS_linux.bin launchpad.sh errors TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nPROBLEM(ABSTRACT)\n Using the DC or MS 'launchpad.sh' script results in the following error message:\n.\/setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `\/dev\/null') \n\nSYMPTOM\nThe following error is seen running when doing either 'launchpad.sh' or 'silent_MS_linux.bin': \n\n Initializing InstallShield Wizard........ \nLaunching InstallShield Wizard........ \n\n.\/setup_MS_lin.bin: line 1926: warning: here-document at line 1926 \ndelimited by end-of-file (wanted `\/dev\/null') \n\nThe installer is unable to run in graphical mode. Try running the \ninstaller with the -console for -silent flag.\n\n\nCAUSE\nMissing Linux system libraries.\n\n\nENVIRONMENT\nLinux - RHEL6.x and RHEL7.x 64-bit versions.\n\n\n\nRESOLVING THE PROBLEM\nThis error messag is seen because of some missing Linux libraries. Usually what's missing are the compat-libstdc++ or libstdc++ libraries. Usually the 32-bit version is missing. Use the commands shown below to verify you have them installed, otherwise contact your Linux system administrator and installt these required libraries. \n\n\n[\/support\/docview.wss?uid=swg21985630&aid=1] [\/support\/docview.wss?uid=swg21985630&aid=1]\n[\/support\/docview.wss?uid=swg21985630&aid=2] [\/support\/docview.wss?uid=swg21985630&aid=2]\n\n \n\nPRODUCT ALIAS\/SYNONYM\n ITCAM4AD ITCAMfAD ITCAM for App Diagnostics"}]},{"id":"TRAIN_Q584","question":"Help with Security Bulletin: Vulnerability identified in IBM WebSphere Application Server shipped with WSRR (CVE-2017-1741)\n\nI 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 V9.0.0.0. What is the recommended fix?","answer":"\u00b7 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\u00b7 Apply Fix Pack 8.0.0.15 or later.","is_impossible":false,"contexts":[{"filename":"swg22012345.txt","text":"Title: IBM Security Bulletin: Potential Privilege Escalation in WebSphere Application Server Admin Console (CVE-2017-1731) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There is a potential privilege escalation in WebSphere Application Server Admin Console. \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1731 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1731]\nDESCRIPTION: IBM WebSphere Application Server could provide weaker than expected security when using the Administrative Console. An authenticated remote attacker could exploit this vulnerability to possibly gain elevated privileges.\nCVSS Base Score: 8.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134912 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134912] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:L\/UI:N\/S:U\/C:H\/I:H\/A:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nThis vulnerability affects the following versions and releases of IBM WebSphere Application Server: \n\n * Version 9.0 \n * Version 8.5 \n * Version 8.0 \n * Version 7.0\n\nREMEDIATION\/FIXES\n The recommended solution is to apply the interim fix, Fix Pack or PTF containing APARs PI89498 for each named product as soon as practical.\n\nFor WebSphere Application Server traditional and WebSphere Application Server Hypervisor Edition: \n\nFor V9.0.0.0 through 9.0.0.6: \n\u00b7 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\u00b7 Apply Fix Pack 9.0.0.7 or later. \n\nFor V8.5.0.0 through 8.5.5.13: \n\u00b7 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\u00b7 Apply Fix Pack 8.5.5.14 or later (targeted availability 3Q2018). \n\nFor V8.0.0.0 through 8.0.0.14: \n\u00b7 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\u00b7 Apply Fix Pack 8.0.0.15 or later. \n\nFor V7.0.0.0 through 7.0.0.43: \n\u00b7 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\u00b7 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."}]},{"id":"TRAIN_Q585","question":"Minimum Size of QR Code for Datacap to identify correctly\n\nWhat is the recommended minimum size of the barcode for the Datacap to identify it properly.","answer":"To optimize barcode recognition: \n\n * The width of the thinnest bar (called the X-dimension) must be at least one pixel, and two pixels are recommended for best results. At 200 DPI this means each bar must be at least .01 inch. Generally this translates to about 4 to 5 characters per inch. \n * The X-dimension or width of the narrowest black bar and white space between bars must be at least 20 mils (1\/50 inch, 1\/2 mm). When scanned perfectly at 200 DPI this would result in 4 pixels, and at 300 DPI 6 pixels. \n * For Code 39 symbols: a 20 mil X-dimension results in a density of approximately 3.6 characters per inch. Optimally the height should be at least 1\/4 inch or 15% of the width, whichever is greater, though this is not an absolute requirement. The minimum quiet zone (white space before and after the bar code) specified by the standard is 1\/5 inch.","is_impossible":false,"contexts":[{"filename":"swg21500300.txt","text":"Title: IBM Optimizing barcode recognition with IBM Datacap - United States\n\nText:\nbar code barcode recognition optimization patch code patchcode TECHNOTE (FAQ)\n\nQUESTION\n What can be done to give the best results with barcode recognition? \n\nCAUSE\nDuring printing, the ink can bleed or spread out over the white area, and then, during scanning, additional spreading of black may occur. As a result, the white spaces end up disappearing and the bars blend into each other. This can be seen by looking at the scanned image at high magnification. The barcode must meet the specifications after accounting for this.\n\nANSWER\nTo optimize barcode recognition: \n\n * The width of the thinnest bar (called the X-dimension) must be at least one pixel, and two pixels are recommended for best results. At 200 DPI this means each bar must be at least .01 inch. Generally this translates to about 4 to 5 characters per inch. \n * The X-dimension or width of the narrowest black bar and white space between bars must be at least 20 mils (1\/50 inch, 1\/2 mm). When scanned perfectly at 200 DPI this would result in 4 pixels, and at 300 DPI 6 pixels. \n * For Code 39 symbols: a 20 mil X-dimension results in a density of approximately 3.6 characters per inch. Optimally the height should be at least 1\/4 inch or 15% of the width, whichever is greater, though this is not an absolute requirement. The minimum quiet zone (white space before and after the bar code) specified by the standard is 1\/5 inch. \n * Scanning can sometimes introduce white or black stripes on the image running in the scanning direction, typically vertical stripes if the paper is scanned in Portrait orientation. Bar codes printed in normal horizontal orientation cannot be read reliably when this occurs. It is advisable to print barcodes perpendicular to the direction of scanning. If the barcode must be printed horizontally on a page, scanning in landscape orientation will make the barcode more robust in the presence of common scanner issues. \n * By default, Datacap only accepts barcode images with 71% confidence or higher. To modify it to accept low confidence barcodes also, add the following action to run prior to barcode detection: * SetMinimumConfidenceBP(1) - This is equivalent to 11% confidence. Each increment increases the required confidence 10% and higher values can be used if false barcodes are detected. A value of 4 is usually sufficient for this purpose.\n \n \n * Barcode recognition has an internal barcode enhancement capability. To maintain high performance, this feature is turned off by default. If low quality barcodes are being received, it may be desired to turn on barcode enhancement, despite the performance hit. To do this, add the following action to run prior to barcode detection: * rrSet(1,@P.bp_enhance)\n \n \n * Performing Datacap's regular image enhancement (ImageFix) prior to running any barcode recognition action is not recommended. ImageFix is designed to optimize text recognition and can actually degrade the barcode. There are some rare exceptions, and if it is necessary to use image enhancement prior to barcode recognition, pay close attention to the configuration settings, especially vertical line removal and despeckle. To ensure image processing is not interfering with barcode recognition, test with the ImageFix() action removed.\n\n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture Not Applicable 8.1.0"}]},{"id":"TRAIN_Q586","question":"How to enable the snippet results cache in the Netezza Platform Software releases?\n\nHow to enable the snippet results cache in the Netezza Platform Software releases? ","answer":"To enable the feature on a session level and test the snippet results cache behavior, you must pause the NPS system, set the variable, and resume the system, as follows: \n\nnzsystem pause -force\nnzsystem set -arg system.srcMode=1 -force\nnzsystem resume\n\nThis setting remains in effect until the database is restarted. You can add the definition to the system.cfg file to keep the setting in effect after the Netezza software restarts:\n\n\n 1. Log in to the Netezza system as the nz user account.\n \n 2. With any text editor, open the \/nz\/data\/config\/system.cfg file. \n \n 3. Look for a system.srcMode definition in the file to make sure that one is not already present and\/or commented out. If you find an entry, make sure that system.srcMode=1 is set and not commented out with a # character. If you cannot find an entry, add system.srcMode=1 to the file. \n \n 4. Save and close the system.cfg file.\n \n 5. Stop and restart the NPS software using the nzstop and then the nzstart commands.","is_impossible":false,"contexts":[{"filename":"swg21960526.txt","text":"Title: IBM How to enable the snippet results cache in the Netezza Platform Software releases - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The snippet results cache feature is disabled by default in some NPS releases. Review this topic to learn how to enable the feature if your queries could benefit from it. \n\nCAUSE\nStarting with the June 2015 fix packs for NPS 7.1.0.6 and 7.2.0.5, and the NPS 7.2.1 release, the snippet results cache is disabled by default because it was optimized for specific workloads. Starting in the March fix packs 7.1.0.9, 7.2.0.8, and 7.2.1.2, the feature is enabled by default because it is optimized for most workloads. \n\nENVIRONMENT\nNetezza Platform Software releases 7.1.0.6 through 7.1.0.8-P1, 7.2.0.5 through 7.2.0.7-P1 and 7.2.1 through 7.2.1.1-P1\n\nDIAGNOSING THE PROBLEM\nQueries that take advantage of the snippet results cache have longer runtimes after upgrades from any 7.x release to a release listed in the Environment section.\n\nRESOLVING THE PROBLEM\nThe snippet results cache is a query optimization feature added in NPS release 7.1 that can help to improve the performance of small queries. The feature was enabled by default for the NPS 7.1 releases up to 7.1.0.6 and for 7.2 releases up to 7.2.0.5.\n\n\nThe snippet results cache saves the intermediate results of snippets and can reuse them rather than incur the processing time to recompute them when needed. The cache can help to improve the performance of small queries. \n\nHowever, in environments where queries run against tables that constantly change with TRUNCATE, load, updates, and\/or rollback operations, caching may not be a good match if cached snippet results are frequently invalidated before they can be reused. \n\nIf you upgrade from any 7.x release to a release listed in the Environment section and detect a change in query performance for queries that take advantage of the snippet results cache, you can re-enable the feature.\n\nTo enable the feature on a session level and test the snippet results cache behavior, you must pause the NPS system, set the variable, and resume the system, as follows: \n\nnzsystem pause -force\nnzsystem set -arg system.srcMode=1 -force\nnzsystem resume\n\nThis setting remains in effect until the database is restarted. You can add the definition to the system.cfg file to keep the setting in effect after the Netezza software restarts:\n\n\n 1. Log in to the Netezza system as the nz user account.\n \n 2. With any text editor, open the \/nz\/data\/config\/system.cfg file. \n \n 3. Look for a system.srcMode definition in the file to make sure that one is not already present and\/or commented out. If you find an entry, make sure that system.srcMode=1 is set and not commented out with a # character. If you cannot find an entry, add system.srcMode=1 to the file. \n \n 4. Save and close the system.cfg file.\n \n 5. Stop and restart the NPS software using the nzstop and then the nzstart commands."}]},{"id":"TRAIN_Q587","question":"Why can't I connect to HTTPS server using Installation Manager 1.7.2?\n\n\n\nWhen using IBM Installation Manager 1.7.2 to connect to a HTTPS server, I get the following message:\n\nThe following repositories are not connected: https:\/\/www.ibm.com\/software\/repositorymanager\/service\/com.ibm. websphere.ND.v85\/8.5.5.2.\n\nWhen I try to hit the URL, I get a 404 error.","answer":"IBM Installation Manager has added support for the TLS protocol in versions 1.8 and 1.7.4. Versions of the Installation Manager that are 1.7.3.1 or older, require SSL security protocol to connect to a HTTPS server. \nTo resolve the issue, update IBM Installation Manager to version 1.7.4, 1.8 or newer.","is_impossible":false,"contexts":[{"filename":"swg21688071.txt","text":"Title: IBM Installation Manager 1.7.3.1 or older cannot connect to HTTPS servers that have SSL security protocol disabled - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When using IBM Installation Manager to connect to a HTTPS server, if the server has SSL disabled, versions of IBM Installation Manager older than 1.8 will not be able to connect to it \n\nRESOLVING THE PROBLEM\nIBM Installation Manager has added support for the TLS protocol in versions 1.8 and 1.7.4. Versions of the Installation Manager that are 1.7.3.1 or older, require SSL security protocol to connect to a HTTPS server. \nTo resolve the issue, update IBM Installation Manager to version 1.7.4, 1.8 or newer.\n\nRELATED INFORMATION\n Installation Manager and Packaging Utility downloads [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27025142]"}]},{"id":"TRAIN_Q588","question":"Why may I receive: Dump Event \"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\" \"Failed to create a thread: retVal -1073741830, errno 11\" ?\n\nWhy may I receive: Dump Event \"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\" \"Failed to create a thread: retVal -1073741830, errno 11\" ?","answer":"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.","is_impossible":false,"contexts":[{"filename":"swg21648497.txt","text":"Title: IBM Insufficient ulimit Value Causes Native OutOfMemory - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n An out of memory may be observed on a system running WebSphere Application Server on Linux or AIX that is due to ulimit restrictions on number of process\/threads per user. Further investigation may reveal a \"Failed to create a thread:\" message within the generated javacore which would indicate a native out of memory issue has been encountered. The cause of the problem may be an insufficient ulimit setting. While this type of issue can occur on any level of Linux, or AIX, the issue is most likely to be seen in systems running multiple instances of WebSphere Application Server using one userid. The following will outline how to identify if a process ulimit is the culprit and what WebSphere Application Server Support recommends to fix the case. \n\nSYMPTOM\nAn out of memory Dump Event such as: \n\n\"systhrow\" (00040000) Detail \"java\/lang\/OutOfMemoryError\"\n\"Failed to create a thread: retVal -1073741830, errno 11\" received\n\nNote: This detailed message will appear only in javacores.\n\n\nDIAGNOSING THE PROBLEM\nWhen using WebSphere Application Server, ulimits can be set to fix or tune around a number of problems. For more on how to set a ulimit refer to the \"Guidelines for setting ulimits [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21469413]\" Technote which goes into detail on setting different ulimits on various operating systems and the difference between the soft and hard limit. This article is concerned particularly with the \"-u\" ulimit or \"nproc\" limit on Linux, the ulimit - r on AIX which affects the number of threads allowed for a single user process running WebSphere Application Server. \n\nThe AIX issue is less commonly seen as it limits then number of threads for a process but is seen in application servers with very large thread pools, This is becoming more common in 64bit addressing JVMs running complex applications. WebSphere Application support recommends setting the ulimit -r ulimited on AIX.\n\nThe nproc limit usually only counts processes on a server towards determining this number. Linux systems running WebSphere Application Server are a particular case. The nproc limit on Linux counts the number of threads within all processes that can exist for a given user. To determine the ulimit settings of a WebSphere Application Server process running on Linux refer to \"How to determine the ulimit settings of a running WebSphere Application Server process on Linux [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21407889]\".\n\nUser Limits (in bytes except for NOFILE and NPROC) \n\ntype soft limit hard limit RLIMIT_AS unlimited unlimited RLIMIT_CORE unlimited unlimited RLIMIT_CPU unlimited unlimited RLIMIT_DATA unlimited unlimited RLIMIT_FSIZE unlimited unlimited RLIMIT_LOCKS unlimited unlimited RLIMIT_MEMLOCK 65536 65536 RLIMIT_NOFILE 65536 65536 RLIMIT_NPROC 131072 131072 \n\nFor most cases of older versions of Linux this value will be defaulted to around 2048. For out of the box Red Hat Enterprise Linux (RHEL) 6 the default value for nproc will be set to 1024. This low default setting for larger systems will not allow for enough threads in all processes. \n\nWebSphere Application Server Support recommends setting the ulimit -u or nproc to a value of 131072 when running on Linux to safely account for all the forked threads within processes that could be created. \n\nBy using this recommended value a sufficient number of threads in all processes will be allowed and will not be a limiting factor for the environment. Increasing the limit to the suggested value should have no negative impact. When the number of threads in all processes reaches the -u ulimit, an out of memory error message will be thrown. This issue can be avoided by increasing this limit. Be aware that if the number of threads\/processes reaches the recommended number of 131072 or close, the issue may be deeper and continuing to increase the -u ulimit will only prove to be a temporary fix. \n\nOnce the ulimit is increased, the WebSphere Application Server will need to be restarted to use the \nnew setting. In the case of WebSphere Application Server ND, the nodeagent and the servers on the nodes will need to be restarted."}]},{"id":"TRAIN_Q589","question":"How to have IBM HTTP Server re-direct an application URL from HTTPS to HTTP?\n\nWe have an application which uses SSL, but we need to make this http only. We disabled all the SSL, but many clients URLs are still pointing to https. So we need a HTTP Server redirect to change these URLs from https to http. Is this possible? ","answer":"First, make sure the LoadModule line for mod_rewrite is uncommented in the httpd.conf\n\nLoadModule rewrite_module modules\/mod_rewrite.so\n\nNext, add the following to the global scope or any port 80 VirtualHost stanzas defined within the httpd.conf configuration file.\n\nRewriteEngine on\nRewriteCond %{SERVER_PORT} =80\nRewriteRule ^(.*) https:\/\/%{SERVER_NAME}%{REQUEST_URI} [R,L]\n\nFinally, restart the IBM HTTP Server after making the preceding changes","is_impossible":false,"contexts":[{"filename":"swg21114864.txt","text":"Title: IBM Rewriting HTTP (port 80) requests to HTTPS (port 443) - United States\n\nText:\nrewrite; ssl; plugin; dynamic; static; rules; IHS; WAS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The rewrite module (mod_rewrite.c) provided with the IBM\u00ae HTTP Server can be used as an effective way to automatically rewrite all HTTP requests to HTTPS. \n\nRESOLVING THE PROBLEM\nThe rewrite module (mod_rewrite.c) can be used to automatically rewrite all HTTP (port 80) requests to HTTPS (port 443). This provides an effective way to ensure that all traffic to and from the IBM HTTP Server is encrypted over the Secure Sockets Layer (SSL) without having to use individual redirects or hard-coded HTTPS links. \nNote: The web server should already be configured to handle HTTPS requests successfully\nbefore attempting to implement the following suggestions. For assistance with setting up SSL in the IBM HTTP Server, visit SSL guide [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21179559]\n\nFirst, make sure the LoadModule line for mod_rewrite is uncommented in the httpd.conf\n\nLoadModule rewrite_module modules\/mod_rewrite.so\n\nNext, add the following to the global scope or any port 80 VirtualHost stanzas defined within the httpd.conf configuration file.\n\nRewriteEngine on\nRewriteCond %{SERVER_PORT} =80\nRewriteRule ^(.*) https:\/\/%{SERVER_NAME}%{REQUEST_URI} [R,L]\n\nFinally, restart the IBM HTTP Server after making the preceding changes\n\nImportant: If using HTTP authentication, make sure it is only configured for your SSL virtual host. If it also applies to your port 80 requests, the authentication challenge can pre-empt the rewrite, resulting in user IDs and passwords being sent over an unencrypted session.\n\nIt is also recommended that you configure your port 80 virtual host with a different document root and so on, from your SSL virtual host. This is to be sure that even if your rewrite fails, sensitive information cannot be served from that virtual host over unencrypted sessions.\n\nRELATED INFORMATION\n Module mod_rewrite..URL Rewriting Engine [http:\/\/httpd.apache.org\/docs\/mod\/mod_rewrite.html]"}]},{"id":"TRAIN_Q590","question":"Why is RPT script for secure application failing during RRT agent playback with URL Unavailable ?\n\n\n\nIn the ITCAM for Transactions, Robotic Response Time agent (t6) - the Rational Performance Tester (RPT) scripts playback is failing for specific secure applications (ones that use https). The scripts which invoke the http URLs work fine.\n\nThe TEP workspace Robotic Response Time -> Playback Status->Robotic Script Verification Point Failures shows following Event Types for the RPT Script when it fails:\n\n Script Type Event Type\n \n Rational Performance Tester HTTP Return Code\n Rational Performance Tester Content Failure\n Rational Performance Tester URL Unavailable Failure\n\nWhat could be causing the https URLs to fail, and how to resolve this?\n","answer":"SSL (Secure Sockets Layer) and TLS (Transport Layer Security) are transport layer protocols. Ciphers implement security by providing the encryption mechanism. \n\nTLS is the new protocol. SSL protocol got up to version 3.0. In effect, TLS 1.0 is SSL 3.1. Currently, TLS versions include TLS 1.1 and 1.2. Each new version adds new features and modifies internal details. \n\nWhether the RRT agent supports TLS1.1\/1.2 depends on whether the underlying JRE supports TLS 1.1\/1.2. The JRE that supports the RRT agent and the JRE that supports RPT workbench must both support the same version of TLS and the same ciphers.","is_impossible":false,"contexts":[{"filename":"swg21960133.txt","text":"Title: IBM Does the RRT agent support TLS 1.1\/1.2 and 256-bit ciphers? - United States\n\nText:\n256-bit ciphers; Strong Encryption; TLS 1.1; TLS 1.2; SSL; Generic Failure; Cannot support; RPT; RRT; T6; 71RRT-RPTPLAN; 71RRT-RPTINS; 71RRT-RPTCONF; 71RRT-RPTPLAY; 71RRT-RPTWV; 71RRT-RPTTS TECHNOTE (FAQ)\n\nQUESTION\n What do you need to do to configure the Robotic Response Time (RRT) agent to support TLS 1.1\/1.2 and 256-bit ciphers? \n\nCAUSE\nSupport for TLS 1.1\/1.2 and 256-bit ciphers is determined by the underlying JRE (Java Runtime Environment). Consequently, in order to support TLS 1.1\/1.2 and 256-bit ciphers, patch the RPT workbench JRE, and patch the RRT agent JRE. Both JREs must support the same level of TLS.\n\nANSWER\n \n\nSSL (Secure Sockets Layer) and TLS (Transport Layer Security) are transport layer protocols. Ciphers implement security by providing the encryption mechanism. \n\nTLS is the new protocol. SSL protocol got up to version 3.0. In effect, TLS 1.0 is SSL 3.1. Currently, TLS versions include TLS 1.1 and 1.2. Each new version adds new features and modifies internal details. \n\nWhether the RRT agent supports TLS1.1\/1.2 depends on whether the underlying JRE supports TLS 1.1\/1.2. The JRE that supports the RRT agent and the JRE that supports RPT workbench must both support the same version of TLS and the same ciphers. \n\nFor example, RRT 7.3 FP01 supports RPT 8.3.0.3, but RPT 8.3.0.3 does not support TLS1.1\/1.2. Consequently, RRT 7.3 FP01 also does not support TLS 1.1\/1.2.\n\nIn comparison, RRT 7.4 with IF21 or IF24 (7.4.0.0-TIV-CAMRT-IF0021 or 7.4.0.0-TIV-CAMRT-IF0024) can support RPT 8.3 and RPT 8.6 since RPT 8.6 supports TLS1.1 \/1.2, and the IBM Java 7 included with RRT 7.4 also supports TLS 1.1\/1.2. \n\nHowever, when a script uses TLS 1.2\/1,2, some ciphers may not be supported. To verify whether certain cipher suites are supported, visit the IBM Java Knowledge Center:\n\nIBM Java Cipher Suite Information\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSYKE2_7.0.0\/com.ibm.java.security.component.70.doc\/security-component\/jsse2Docs\/ciphersuites.html?lang=en [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSYKE2_7.0.0\/com.ibm.java.security.component.70.doc\/security-component\/jsse2Docs\/ciphersuites.html?lang=en]\n\n\nDo You Need to Patch Java?\n\nFirst, determine whether your script uses 256-bit ciphers. In RPT workbench, open the script in Test Editor mode. In the left panel, drill down through the Server Access Configurations. Select SSL.\n\n[\/support\/docview.wss?uid=swg21960133&aid=1]\n\nIn the right panel, examine the available ciphers that display. If the list contains 256-bit ciphers, you need to support Strong Encryption in RPT and the RRT agent. The name identifies the encryption level. For example, SSL_DHE_RSA_WITH_AES_256_CBC_SHA is a 256-bit cipher. The presence of 256 in the cipher name means that the cipher supports 256-bit encryption. \n\n[\/support\/docview.wss?uid=swg21960133&aid=2] [\/support\/docview.wss?uid=swg21960133&aid=2]\n\nCipher Naming Conventions\n\nIn RPT workbench, the cipher name always begins with \"SSL\" to simplify naming conventions. If the script uses TLS as the protocol in the test, then the cipher is a TLS cipher.\n\n[\/support\/docview.wss?uid=swg21960133&aid=3] [\/support\/docview.wss?uid=swg21960133&aid=3]\n\nPlayback Symptoms\n\nCheck whether your script playbacks indicate that the RRT JRE needs to be patched to support Strong Encryption. Strong Encryption adds 256-bit ciphers.\n\n1) The Playback Status workspace shows that playbacks are complete, but the Verification Failures workspace shows:\n\nEvent Type: Generic Failure\n\nViolated Value: java.lang.RuntimeException occurred in IBM Registration. Message: java.io.FileNotFoundException: \/tmp\/RPTTEMP.A1E4CC464D3DD067D\n\nAdditional Details: none\n\n2) The trace-robotic log includes messages like the following:\n\n[2015-05-05T22:10:58.487-04:00] - MIN - <playback-hostname> - PlaybackThreadPoolWorker-1169 - com.ibm.tivoli.transperf.playback.rpt.RPTPlaybackService.processStatusEvent() - Sending RT VP event: i=|0|, statusEvent=|SimTestStatusEvent Values: monitorName=|<script-name>|,URL=|<monitored-url>|,eventType=|com.ibm.rational.test.lt.HTTPPageVerdict|,eventId=|516.b32|,parentEventId=|516.b27|,ownerId=|A1E4ED99F22F68E2FD5CB86461633031|,text=|Error occurred during connection to server '<server-url>'. Explanation message: 'Cannot support SSL_DHE_RSA_WITH_AES_256_CBC_SHA with currently installed providers'. Since this request is the primary request for the current page all secondary requests will be skipped and the next page will be attempted.|,name=|Primary Request verdict|,actualValue=||,expectedValue=|null|,eventVerdict=|3|,eventReason=|2|,eventDesc=|null||\n\nPatching JREs to Support TLS 1.1\/1,2\n\nBy default, RPT workbench is configured with restricted or limited strength ciphers. To use less restricted encryption algorithms, you need to download and apply the unlimited jurisdiction policy files (local_policy.jar and US_export_policy.jar). \n\nSee Enabling Strong encryption greater than 128 bit key lengths in Rational Performance Tester\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg21245273 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21245273]\n\nUse the following instructions to patch the JRE that the RRT agent uses.\n\nNote: Backup the jar files that these steps replace -- before you replace these files.\n\n1) Go to the IBM developerWorks Java Technology Security page for JRE 6 security information. \nSee https:\/\/www.ibm.com\/developerworks\/java\/jdk\/security\/ [https:\/\/www.ibm.com\/developerworks\/java\/jdk\/security\/]\n\n2) Click on the \"Java SE 6\" link. \n\n3) Click on the \"IBM SDK Policy files\".\n\n4) On the Sign in page, enter your developerWorks IBM ID and password.\n\n5) After successfully logging in, select Files for Java 5.0 SR16, Java 6 SR13, Java 6 SR5 (J9 VM2.6), Java 7 SR4, and all later releases. Click on Continue.\n\n6) Scroll down to the License portion of the resulting page and click on the View license link to see the licensing terms for the download.\n\n7) If the licensing terms are acceptable, check I agree and click on the I confirm link. If the terms are not acceptable, you are not able to enable strong encryption, and you should click I cancel.\n\n8) Click on the Download now link to download the unrestricted.zip file.\n\n9) Extract the local_policy.jar and US_export_policy.jar files from the unrestricted.zip archive.\n\n10) Log onto the RRT agent host, and stop the RRT agent.\n\n11) Backup the local_policy.jar and US_export_policy.jar files in the <ITM_HOME>\/tmaitm6\/java60\/jre\/lib\/security and <ITM_HOME>\/tmaitm6\/java70\/jre\/lib\/security directories on the RRT agent host.\n\n12) Place those two files in the <ITM_HOME>\/tmaitm6\/java60\/jre\/lib\/security and <ITM_HOME>\/tmaitm6\/java70\/jre\/lib\/security directories on the RRT agent host. Replace the existing files with the same names. Verify that the file permissions are the same as the files you replaced.\n\n13) Restart the RRT agent.\n\n14) Try to playback the RPT script again. Does the script playback successfully, without error? \n\nRELATED INFORMATION\n Security information for JRE 6 [https:\/\/www.ibm.com\/developerworks\/java\/jdk\/security\/]\nEnabling Stong encryption greater than 128 bit key leng [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21245273 ]\n\n\n\n\nHISTORICAL NUMBER\n 34602.082.000 \n\nPRODUCT ALIAS\/SYNONYM\n ITCAMfT\nT7.4"}]},{"id":"TRAIN_Q591","question":"Is IIBv9x affected by vulnerability CVE-2016-6304?\n\n\n\nThis Q&A is abstracted from a PMR\n\nI would like to know if IIBv9x is affected by vulnerability CVE-2016-6304. There was a report that Open SSL vulnerabilities were included in IIB but I could not find anything regarding specifically for CVE-2016-6304 vulnerability for IIB. Can you please confirm?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q592","question":"Do the Bash Bug vulnerabilities affect WebSphere MQ Hypervisor?\n\nDo the Bourne Again Shell (Bash) vulnerabilities known as Bash Bugs or Shellshock affect WebSphere MQ Hypervisor and if so, what action is required to address this situation?","answer":"IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server ship with Red Hat Enterprise Linux (RHEL) that is vulnerable to CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277 and CVE-2014-6278 Bash vulnerabilities.","is_impossible":false,"contexts":[{"filename":"swg21685666.txt","text":"Title: IBM Action required for IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server for the Bash vulnerabilities (CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277 and CVE-2014-2014-6278) - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n IBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server requires customer action for the Bash vulnerabilities that have been referred to as \"Bash Bug\" or \"Shellshock\" and the two memory corruption vulnerabilities. \n\nCONTENT\nIBM WebSphere MQ Hypervisor Edition for Red Hat Enterprise Linux Server ship with Red Hat Enterprise Linux (RHEL) that is vulnerable to CVE-2014-6271, CVE-2014-7169, CVE-2014-7186, CVE-2014-7187, CVE-2014-6277 and CVE-2014-6278 Bash vulnerabilities. \n\nRemediation: \n\nIBM strongly recommends that you should contact Red Hat to obtain fixes and install fixes for Red Hat Enterprise Linux (RHEL). \n\n \n\nChange History: \n\nSeptember 29, 2014: Original version published.\n\nRELATED INFORMATION\n A Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21685764]"}]},{"id":"TRAIN_Q593","question":"How can I query the Derby database in Portal via SQL statements?\n\n\n\nI have a Portal system I just installed. I have not yet run database-transfer to copy the data from the Derby database to a DB2, Oracle, or SQL Server database. I don't wish to transfer to an external database and I have a need to run a SQL query against a table or two in the Derby database to troubleshoot an issue.\n\nHow can I perform this action?","answer":"The ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes","is_impossible":false,"contexts":[{"filename":"swg21381009.txt","text":"Title: IBM Using dblook and ij to work with the embedded Apache Derby in WebSphere Portal - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM WebSphere Portal 6.1 uses an embedded version of Apache Derby out of the box. However, there is no longer a graphical tool such as CloudView (as with Cloudscape 5.x). In order to obtain the data and structure of the WebSphere Portal database, dblook and ij utilities can be used to accomplish such goals. \n\nRESOLVING THE PROBLEM\n\nBefore proceeding with the following, it is strongly recommended that you back up your Derby database. Make a copy of <wp_profile>\/PortalServer\/derby\/wpsdb to a backup directory. Since the version of Derby used in WebSphere Portal is embedded, you must stop the Portal server before you can access the database although you can always work on the backup copy.\n\nNOTE: For simplicity, we will omit the extension of the utilities. You should add \".sh\" or \".bat' depending on the platform.\n\nThere are three primary utility tools that are installed with WebSphere 6.1, \"dblook\", \"ij\", and \"sysinfo\", under the <was_root>\/AppServer\/derby\/bin\/embedded directory. The sysinfo utility generates information about the operating system, the Java version and classpath, and the Derby driver files and version information.\n\ndblook utility\nThe dblook utility is used to view the database structure (in DDL - Data Definition Language) for a specific database. \n\nThe usage is dblook -d <databaseURL> [options], where databaseURL is in the \"jdbc:derby:<database>\" format. The <database> should be given as a full path, such as C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb. \n\nCommonly used options include: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Examples:\n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -o C:\\temp\\wpsdb_ddl.sql\n * \n * \n * \n * \n * dblook -d jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\PortalServer\\wpsdb -z release -t user_desc -verbose -o C:\\temp\\user_desc.sql\n * \n * \n\n\nij utility \nThe ij utility is a command line SQL processor. It can be used to run DDL for creating database, tables, indexes, and so on. In a WebSphere Portal environment, it would typically be used for exporting data or making simple changes (when advised by IBM Support). \n\nTo start ij, simply open a command prompt or terminal window, change the directory and enter the command. You should then see the ij shell with prompt \"ij>\". \n\nThe following are some common commands that you may use when reviewing data in the Portal database. * \n * ij> connect 'jdbc:derby:C:\\IBM\\WebSphere\\wp_profile\\derby\\wpsdb';\n * \n * \n * \n * \n * ij> show connections;\n * \n * \n * CONNECTION0* - jdbc:derby:C:\\ibm\\websphere\\wp_profile\\portalserver\\derby\\wpsdb \n * = current connection \n ij> driver \"org.apache.derby.jdbc.EmbeddedDriver'; \n * \n * \n * \n * ij> set schema=release;\n * \n * \n * \n * \n * ij> select * from user_desc where oid=1000;\n * \n * \n * \n * \n * ij> run 'myquery.sql';\n * \n * \n * \n * \n * \n * \n * ij> CALL SYSCS_UTIL.SYSCS_EXPORT_TABLE('RELEASE','USER_DESC','USER_DESC.SQL',';','|',NULL);\n * \n * \n * \n * \n * ij> \n * CALL SYSCS_UTIL.SYSCS_EXPORT_QUERY('SELECT * FROM RELEASE.USER_DESC','user_desc_query.sqlL',null,'|',NULL);\n * \n * \n\nRELATED INFORMATION\n Derby utility from Apache [http:\/\/docs.oracle.com\/javadb\/10.3.3.0\/getstart\/cgsusingtoolsutils.html]\nDerby SQL references from Apache [http:\/\/db.apache.org\/derby\/docs\/10.1\/ref\/crefsqlj23296.html]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Organizational Productivity- Portals & Collaboration WebSphere Portal End of Support Products AIX, HP-UX, IBM i, Linux, Solaris, Windows, z\/OS 7.0, 6.1"}]},{"id":"TRAIN_Q594","question":"In WebSphere MQ, why am I getting AMQ9776, AMQ9777 Channel was blocked errors?\n\nIn WebSphere MQ, why am I getting AMQ9776, AMQ9777 Channel was blocked errors ","answer":"-","is_impossible":true,"contexts":[]},{"id":"TRAIN_Q595","question":"How can I configure a DataPower MQ client to use mutual authentication with SSL?\n\nI am looking to setup a DataPower MQ Client to use SSL in mutual authentication mode with a Remote WebSphere MQ Manager. ","answer":"The following three steps are necessary to make sure that the SSL configurations for the Remote MQ Server is correctly working. Refer to IBM WebSphere MQ product manuals to configure MQ environment to work in SSL mutual authentication mode.\n\n\n 1. Configure WebSphere MQ Queue Manager (Remote MQ Server) to use SSL authentication (SSLCAUTH as \"required\") using URL: http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm]. \n 2. Configure WebSphere MQ Client to use SSL authentication. \n 3. Verify that WebSphere MQ Client can PUT\/GET message(s) using application programs such as amqsputc and amqsgetc with MQ Queue Manager in SSL mutual authentication mode.","is_impossible":false,"contexts":[{"filename":"swg21260155.txt","text":"Title: IBM Configuring DataPower MQ client to use SSL in mutual authentication mode - United States\n\nText:\ndatapower; mq; websphere mq; ssl; mutual authentication mode; mq manager; 7993; 7993; 7993; machine type 7993 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The WebSphere DataPower MQ Client can be configured to use SSL in mutual authentication mode with a Remote WebSphere MQ Manager. This step-by-step technote guides DataPower Appliance users on how to configure DataPower MQ Manager Object to use SSL in mutual authentication mode. This technote assumes that MQ queue manager is configured with key database and its associted password file for using SSL connection with other MQ clients. If it is not configured yet, it has to be done first using the URL: http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm] \n\nRESOLVING THE PROBLEM\nIn order to use this technote, you should have a working knowledge of how to setup and administer MQ Server in Windows, AIX, Solaris, HP-UX, or Linux environment. You should also have an understanding of how to configure DataPower MQ Manager Object that connects to remote WebSphere MQ Queue Manager (qmgr). This technote focuses on configuring DataPower MQ Client to use SSL in mutual authentication mode with Firmware Releases 3.8.2 and later fixpacks. Follow these steps to configure DataPower MQ Manager Object (mq-qm object) to access WebSphere MQ Queue Manager (Remote MQ Server) in SSL mutual authentication mode.\nWebSphere MQ configuration prerequisites\n\nThe following three steps are necessary to make sure that the SSL configurations for the Remote MQ Server is correctly working. Refer to IBM WebSphere MQ product manuals to configure MQ environment to work in SSL mutual authentication mode.\n\n\n 1. Configure WebSphere MQ Queue Manager (Remote MQ Server) to use SSL authentication (SSLCAUTH as \"required\") using URL: http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.explorer.doc\/e_ssl.htm]. \n 2. Configure WebSphere MQ Client to use SSL authentication. \n 3. Verify that WebSphere MQ Client can PUT\/GET message(s) using application programs such as amqsputc and amqsgetc with MQ Queue Manager in SSL mutual authentication mode.\n \n\n\nGenerate self signed key\/certificate \n 1. Generate the self signed key\/certificate pair using the \"crypto tool\" from the DataPower device. \n 2. Download the two files to your local machine. For the sake of illustration purpose, the names of the key and certificate files are defined as \"dpmqclient-privkey.pem\" and \"dpmqclient-sscert.pem\" respectively. \n 3. Assuming that openssl tool (www.openssl.org [http:\/\/www.openssl.org]) is installed in the local machine. With openssl tool, you can use the following command to create a \"pkcs12\" type key from the above key\/certificate pair which are of PEM type. This step is necessary as MQ key database will not import key\/certificate files created as PEM.\n \n openssl pkcs12 -export -out dpmqclient-key.p12-in dpmqclient-sscert.pem-inkey dpmqclient-privkey.pem-name ibmwebspheremqadmin\n \n Note the value associated with \"-name\" parameter. IBM WebSphereMQ client required a friendly label as \"ibmwebspheremq<userid>\" of the MQ client user. In this example, the user name is being used as \"admin\". This user must be used in the DataPower MQ Queue Manager object and it must also be an authorized user for both the DataPower MQ instance as well as for the remote WebSphere MQ Server. Please refer to Pages G58-62 in the 3.6.0-WebGui Guide for various fields as described in MQ Queue Manager configuration screen. Also note the following two fields with appropriate values which are required for the MQ Queue Manager object to connect the remote WebSphere MQ Server in SSL mode. \n\n * SSL Key Repository: The key database file name \n SSL Cipher Specification: TRIPLE_DES_SHA_US \n \n\nTo import a personal certificate using \"iKeycmd\" GUI, use the following commands in your host machine where the WebSphere MQ Server\/Client is running. \n * UNIX\n * \n * \n * gsk7cmd -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms \n * \n * \n * Windows\n * \n * \n * runmqckm -cert -import -file filename -pw password -type pkcs12 -target filename -target_pw password -target_type cms \n * \n * \n * \n * \n * -file \n * filenam \n * \n * \n * -pw \n * password\n * \n * \n * -type \n * pkcs12 \n * \n * \n * -target \n * filename\n * \n * \n * -target_pw \n * password\n * \n * \n * -target_type \n * cms\n * \n\n\n\nGenerate the new password file \n\nFollow these steps to generate the new password file. \n 1. Start the iKeyman GUI using either the gsk7ikm command (on UNIX) or the strmqikm command (on Windows). \n 2. From the Key Database File menu, click Open. The Open window displays. \n 3. Click Key database type and select CMS (Certificate Management System). \n 4. Click Browse to navigate to the directory that contains the key database files. \n 5. Select the key database file in which you want to save the certificate, for example key.kdb. \n 6. Click Open. The Password Prompt window displays. \n 7. Type the password you set when you created the key database and click OK. \n 8. The name of your key database file displays in the File Name field. The Personal Certificates menu will display both \"ibmwebspheremq<qmgr>\" and \"ibmwebspheremq<user>\" labels. \n 9. In the WebSphere MQ Certificate key database, there is one certificate assigned to the queue manager or client. The certificate's Friendly Name attribute contains the string ibmwebspheremq followed in lower case by the queue manager name or the client logon ID. This Friendly Name value becomes the label of the certificate in the GSKit key database. Refer to Alter the Friendly Name (Label) of pkcs12 certificates for importing into GSKit [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21225160] if you want to alter the Friendly Name (Label) of pkcs12 certificates that are part of WebSphere MQ Certificate key database. Refer to \"Migrating SSL Security Certificates in WebSphere MQ for Windows\" [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/topic\/com.ibm.mq.csqzas.doc\/sy12430_.htm?resultof=%22%6d%71%22%20%22%66%69%78%22%20%22%6d%69%67%72%61%74%65%64%22%20%22%6d%69%67%72%61%74%22%20%22%63%65%72%74%69%66%69%63%61%74%65%73%22%20%22%63%65%72%74%69%66%22%20] if you want to fix the migrated certificates from the WebSphere MQ V5.3 version to later version. [http:\/\/publib.boulder.ibm.com\/infocenter\/wmqv7\/v7r0\/index.jsp?topic=\/com.ibm.mq.csqzao.doc\/mi10240_.htm] \n 10. From the key database File menu, click Stash Password. This will create the new password file as \"key.sth\". Select OK and close the key database File. \n 11. Upload the \"key.kdb\" and \"key.sth\" files to \"cert:\" directory of the DataPower box. Configure the MQ client object in the DataPower box to use this key database as shown in the screen shot above to connect in SSL mutual authentication mode with the MQ Manager. The following screen shot shows the \"key.kdb\" and \"key.sth\" files are located in the \"cert:\" directory of the application domain.[\/support\/docview.wss?uid=swg21260155&aid=1] [\/support\/docview.wss?uid=swg21260155&aid=1] This screen shot below shows that mq-qm object is using the \"key.kdb\" file located in the \"cert:\" directory with the associated cipher specification as \"TRIPLE_DES_SHA_US\". Note that SSL Proxy Profile field is \"(none)\" as this configuration is using key repository method for SSL connection.[\/support\/docview.wss?uid=swg21260155&aid=2] [\/support\/docview.wss?uid=swg21260155&aid=2] \n 12. Refresh the SSL security attribute of the MQ Manager to use this key database and password files from the host machine running MQ Server.\n \n Runmqsc <MQ Manager>\n Refresh security type(ssl)\n End\n \n 13. Test your application to PUT\/GET MQ message(s) using DataPower MQ client with the new configuration.\n\nNote: DataPower 3.8 and later firmware provides a separate method for the mq-qm object to use SSL in mutual authentication mode. This method uses DataPower SSL Proxy Profile that includes Crypto profile with Identification Credential. For more details, refer to DataPower InfoCenter on how to create SSL Proxy Profile: \nhttps:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.1.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.1.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html] (Fixpack V7.1.0.x) \nhttps:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.2.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.2.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html] (Fixpack V7.2.0.x) \nhttps:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.5.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SS9H2Y_7.5.0\/com.ibm.dp.doc\/mq_securingwithansslproxyprofileobject.html] (Fixpack V7.5.0.x) \n\nNote: The generation of key database can be done using IBM Key Management Tool which comes with MQ Product. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Not Applicable Firmware 3.8.2, 3.8.1, 3.8, 3.7.3 Edition Independent"}]},{"id":"TRAIN_Q596","question":"Why is ITCAM MQ agent shutting down often?\n\n\n\nWe have an MQ agent instance that keeps shutting down randomly.\nBelow is the version of agent:\nmq WebSphere MQ Monitoring Agent lx8263 Version: 07.30.01.00","answer":"Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options \nWhat is Fix Central(FC)? [https:\/\/www.ibm.com\/support\/fixcentral\/help?page=swfaqs] 7.3.0-TIV-XEforMsg-FP0002 9 Dec 2016 English 1 FC","is_impossible":false,"contexts":[{"filename":"swg24043057.txt","text":"Title: IBM ITCAM Agents for WebSphere Messaging Version 7.3.0 Fix Pack 02 (7.3.0-TIV-XEforMsg-FP0002) - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This is the second fix pack after ITCAM Agents for WebSphere Messaging Version 7.3.0 GA \n\nDOWNLOAD DESCRIPTION\n This fix pack fixes the APARs of previous product versions.\n\n\n This fix pack provides support for IBM MQ V9 and several other enhancements(See readme).\n\nPREREQUISITES\nThe following software installed in your environment is compatible with this fix pack.\nSupported WebSphere MQ\n* WebSphere MQ 7.1\n* WebSphere MQ 7.5\n* IBM MQ 8.0\n* IBM MQ 9.0\n\nSupported IBM broker products:\n* WebSphere Message Broker 8.0\n* IBM Integration Bus 9.0\n* IBM Integration Bus 10.0\n\nSupported IBM Tivoli Monitoring\n* IBM Tivoli Monitoring 6.3.0 fix pack 2 or later \n\nINSTALLATION INSTRUCTIONS\nRefer to the Readme file on Fix Central\n\nDOWNLOAD PACKAGE\n \n\n * 1. For distributed systems, download the following installation images from Passport Advantage [http:\/\/www-306.ibm.com\/software\/howtobuy\/passportadvantage\/index.html]. \n Description Part number IBM Tivoli Composite Application Manager Agents for WebSphere Messaging V7.3.0 FP02 CNFL0EN \n \n * 2. For z\/OS systems, install the following PTFs to bring your system to an equivalent level to this fix pack: FMID Maintenance level HKCF730 UA83334 HKMC730 UA83330 HKMQ730 UA83394 HKQI730 UA83372 \n * 3. For the z\/OS customer who has no agents running on distributed systems, download IBM Tivoli OMEGAMON XE for Messaging V7.3.0 Application Support Files for z\/OS from the following website: Platform File to download Linux or Unix LCD7-3513-08.tar [ftp:\/\/public.dhe.ibm.com\/software\/tivoli_support\/misc\/PandA\/tools_agent\/tools\/appsupt\/LCD7-3513-08.tar] Windows LCD7-3513-08.zip [ftp:\/\/public.dhe.ibm.com\/software\/tivoli_support\/misc\/PandA\/tools_agent\/tools\/appsupt\/LCD7-3513-08.zip] \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] 7.3.0-TIV-XEforMsg-FP0002 9 Dec 2016 English 1 FC [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=Tivoli%20Composite%20Application%20Manager&product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.3.0-TIV-XEforMsg-FP0002&inclu] [ ] \n [\/support\/docview.wss?uid=swg24043057&aid=1]Problems (APARS) fixed [\/support\/docview.wss?uid=swg24043057&aid=2]Problems (APARS) fixed\nIV88312, IV83641, IV83002, IV82721, IV82535, IV80959, IV79995, IV79961, IV77813, IV77658, IV77411, IV88948, IV79978, IV90769, OA50555, OA51407, IV84483"}]},{"id":"TRAIN_Q597","question":"How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width?\n\nHow do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator v2.0.2, to fit content by height or width? ","answer":"In the ..navigator.war\/applets\/filenetViewer_properties.jsp file, set the value of the parameter 'scale' as follows \n\nTo fit content by width, specify - scale: \"ftow\",\nTo fit content by height, specify - scale: \"ftoh\",\n\nHere's another way to modify the behaviour: \n\n * make the same changes above to the filenetViewer_properties.jsp under ECMClient\\configure\\explodedformat\\navigator\\applets folder. \n * Rebuild and redeploy the ear file. \n * Restart the application server\n\n\nSave the changes and they should get picked up when the viewer is re-launched.","is_impossible":false,"contexts":[{"filename":"swg21674924.txt","text":"Title: IBM How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? - United States\n\nText:\nfit by height; fit by width; fit; default fit; Daeja viewer; FileNet viewer; Daeja; scale TECHNOTE (FAQ)\n\nQUESTION\n How do I change the default 'fit content by' behaviour of Daeja viewer in IBM Content Navigator, to fit content by height or width? \n\nANSWER\nIn Content Navigator v2.0.2 \n\nIn the ..navigator.war\/applets\/filenetViewer_properties.jsp file, set the value of the parameter 'scale' as follows \n\nTo fit content by width, specify - scale: \"ftow\",\nTo fit content by height, specify - scale: \"ftoh\",\n\nHere's another way to modify the behaviour: \n\n * make the same changes above to the filenetViewer_properties.jsp under ECMClient\\configure\\explodedformat\\navigator\\applets folder. \n * Rebuild and redeploy the ear file. \n * Restart the application server\n\n\nSave the changes and they should get picked up when the viewer is re-launched. \n\nIn Content Navigator v2.0.3 \n\nThe same parameter-value pair mentioned above can be added in the Additional Settings section of the Daeja ViewONE panel, of the admin desktop. Add the parameter-value pair to the Additional Settings section of \n\n * the Professional tab for modifying the behaviour of the Daeja Professional viewer \n * the Virtual tab for modifying the behaviour of the Daeja Virtual viewer.\n\n\nClick New in the Additional Settings section to add the parameter-value pair. Save the changes and they should get picked up when the viewer is re-launched."}]},{"id":"TRAIN_Q598","question":"Is Internet Explorer 11 supported by Lombardi 7.2.XX\n\n We are using Lombardi 7.2.0.5 version. We are planning to upgrade Internet Explorer to IE 11 version.\n\nIs IE 11 supported? Are there any known issues? ","answer":"The following table provides direct links to the detailed system requirements information for the specified release and operating system for the IBM Business Process Manager Standard product.\n\n\nTAB NAVIGATION\n * Version 8.5.7- selected tab,\n * Version 8.5.6\n * Version 8.5.5\n * Version 8.5\n * Version 8.0.1\n * Version 8.0\n * Version 7.5.1\n * Version 7.5","is_impossible":false,"contexts":[{"filename":"swg27023007.txt","text":"Title: IBM Business Process Manager Standard detailed system requirements - United States\n\nText:\nDSREntry; SystemRequirementsDocument; prereq; coreq; installation prerequisites; DSRdoc DETAILED SYSTEM REQUIREMENTS\n\nABSTRACT\n This document provides access to the detailed system requirements information on the supported releases of IBM Business Process Manager Standard. \n\nCONTENT\nThe detailed system requirements information is available through the Software Product Compatibility Reports [https:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity\/softwareReqsForProduct.html] web site. This web site provides you with the ability to dynamically generate operating system, prerequisite, server virtualization environment, translation, end of service, and detailed system requirements reports for your specific product, release, and operating system. \n\n\nThe following table provides direct links to the detailed system requirements information for the specified release and operating system for the IBM Business Process Manager Standard product.\n\n\nTAB NAVIGATION\n * Version 8.5.7- selected tab,\n * Version 8.5.6\n * Version 8.5.5\n * Version 8.5\n * Version 8.0.1\n * Version 8.0\n * Version 7.5.1\n * Version 7.5\n\nIBM Business Process Manager Standard Version 8.5.7 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1399304491114&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1399304491114&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1399304491114&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1399304491114&osPlatform=Windows]\n\nNotes: \n\n * Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1399304491114]\n\nIBM Business Process Manager Standard Version 8.5.6 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1379596967826&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1379596967826&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1379596967826&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1379596967826&osPlatform=Windows]\n\n\nNotes: \n\n * Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1379596967826]\n\nIBM Business Process Manager Standard Version 8.5.5 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1362573579419&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1362573579419&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1362573579419&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1362573579419&osPlatform=Windows]\n\n\nNotes: \n\n * Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1362573579419]\n\nIBM Business Process Manager Standard Version 8.5 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1333099842423&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1333099842423&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1333099842423&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1333099842423&osPlatform=Windows]\n\n\nNotes: \n\n * The Microsoft Internet Explorer Version 8.0 browser is deprecated in this release. You can use this browser with the IBM Business Process Manager products. However, the use of the Tab and Table Coach views, the new dashboards, and the associated Dashboard Toolkit, are not supported. For these functions, it is advised that you use one of the other supported browser versions including Microsoft Internet Explorer Versions 9 and 10.\n * Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1333099842423]\n\nIBM Business Process Manager Standard Version 8.0.1 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1313410528495&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1313410528495&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1313410528495&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1313410528495&osPlatform=Windows]\n\n\nNote: Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1313410528495].\n\nIBM Business Process Manager Standard Version 8.0 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1301659482241&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1301659482241&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1301659482241&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1301659482241&osPlatform=Windows]\n\n\nNote: Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1301659482241].\n\nIBM Business Process Manager Standard Version 7.5.1 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1282724539433&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1282724539433&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1282724539433&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1282724539433&osPlatform=Windows]\n\n\nNote: Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1282724539433].\n\nIBM Business Process Manager Standard Version 7.5 is supported on the following operating systems:\n\n * AIX [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1284157761205&osPlatform=AIX]\n * Linux [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1284157761205&osPlatform=Linux]\n * Solaris [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1284157761205&osPlatform=Solaris]\n * Windows [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1284157761205&osPlatform=Windows]\n\n\nNote: Server virtualization environment information is available in this report [http:\/\/pic.dhe.ibm.com\/infocenter\/prodguid\/v1r0\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1284157761205&].\n\n\nNote: Your entitlement to support, if any, is dependent upon your license and\/or maintenance agreements for IBM Business Process Manager Standard and is limited to your use of the relevant prerequisite with a supported IBM Business Process Manager Standard product.\n\n\nRELATED INFORMATION\n IBM Business Process Manager Tools & Add-Ons [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27023009]\nIBM Integration Designer detailed system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27022441]\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2011\/10\/4 \n\nPRODUCT ALIAS\/SYNONYM\n BPM"}]},{"id":"TRAIN_Q599","question":"ICC configuration manager error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.\n\nWhen saving changes in ICC configuration manager, an \"Application Error\" window pops up.\n\nError:\n\nA severe error occurred.\n\nProblem:\n\nException has been thrown by the target of an invocation.\n\nSolution:\n\nContact IBM Software Support with this error message (see Details).\n\nClick on the Details button and the following stack trace is reported:\n\nDetails\n\nSystem.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)\n\n.....\n\n.....\n\nSystem.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.\n\nat System.Security.Cryptography.MD5CryptoServiceProvider..ctor()\n\nWhat is causing this?","answer":"Incompatible Windows security policy.","is_impossible":false,"contexts":[{"filename":"swg21991690.txt","text":"Title: IBM Application Error in IBM Content Collector Configuration Manager when saving a task route - United States\n\nText:\nicc; fips; md5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n An application error is reported in the IBM Content Collector (ICC) configuration manager when you try to save a task route or other settings. \n\nSYMPTOM\nThe pop up window shows the following message: \n\n * \n * Error: \n * \n A severe error occurred.\n \n \n * Problem:\n * \n Exception has been thrown by the target of an invocation.\n \n \n * Solution:\n * \n Contact IBM Software Support with this error message (see Details).\n\n\nClick on the Details button and the following stack trace is reported: \n\n * Details\n * System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.\n at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)\n at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)\n .....\n .....\n System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.\n at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()\n\n\nCAUSE\nIncompatible Windows security policy.\n\nDIAGNOSING THE PROBLEM\nScroll down to the bottom of the detail section and verify that the following error is seen: \n\n * \n * \n * \n * \n * \n * System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.\n at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()\n\nRESOLVING THE PROBLEM\nTo resolve the problem, go to the following: \n\n * Navigate to Control Panel > Administrative Tools > Local Security Policy > Security Settings > Local Policy > Security Options. \n * In security option, select and double click on System Cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing \n * Check if the option is enabled. If it is enabled, disable this option and try to save the changes in ICC configuration manager again.\n\n\nIf problem persists after disabling the option, contact IBM support for further assistance."}]},{"id":"DEV_Q000","question":"Web GUI 8.1 FP7 requires DASH 3.1.2.1 or later\n\n\n\nYou wanted to install Web GUI 8.1 FP7, but your DASH version does not meet the required version.\n\nIM 1.8 displayed the following:\n\n ERROR: The installed IBM Dashboard Application Services Hub version is 3.1.0.3, but requires version 3.1.2.1 or later.\n\n","answer":"Version 1.1.3.0 is a full refresh of Jazz for Service Management Version 1.1 Base with Modification 3.","is_impossible":false,"contexts":[{"filename":"swg24042191.txt","text":"Title: IBM Download Jazz for Service Management Version 1.1.3.0 - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n You can download Jazz for Service Management from the Passport Advantage web site by using the electronic image part numbers that are provided in this document. \n\nDOWNLOAD DESCRIPTION\n\n\nJazz\u2122 for Service Management brings together the Open Services for Lifecycle Collaboration (OSLC) community's open specifications for linking data and other shared integration services; including dashboard and reporting services. Jazz for Service Management underpins client defined management scenarios such as cloud; performance monitoring; and IT service management.\n\nJazz for Service Management has a number of integration services: Dashboard Services provided by IBM\u00ae Dashboard Application Services Hub and Reporting Services.\n\nFor more information about Jazz for Service Management; see the Jazz for Service Management documentation [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.3.0\/com.ibm.psc.doc\/psc_ic-homepage.html].\n\nVersion 1.1.3.0 is a full refresh of Jazz for Service Management Version 1.1 Base with Modification 3. \n\n\n\nDOWNLOADING JAZZ FOR SERVICE MANAGEMENT ELECTRONIC IMAGES\nYou can download images by using the IBM Download Director applet or HTTP. If possible choose Download Director; because it automatically verifies the completeness of each image that it processes.\n\nTip: If you use Download Director to download the software; then you can also use it to extract the contents of all the compressed files that you downloaded in the session.\n\n\n 1. Before you start the installation; check the Jazz for Service Management Technotes [http:\/\/www.ibm.com\/support\/search.wss?q=jazzsm1130relnotes] for late breaking issues or updated installation instructions.\n 2. Determine the set of platform-specific images to download for the installation scenario or integration services to install; as summarized in the following table. Scenario Images Full installation; all integration services and middleware * Jazz\u2122 for Service Management 1.1.3.0\n * IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0\n * IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9\n * IBM\u00ae DB2\u00ae Enterprise Server Edition 10.5\n \n Custom installation; Dashboard Application Services Hub * Jazz\u2122 for Service Management 1.1.3.0\n * IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9; optional if already installed\n * IBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements; for high availability environment only\n * IBM\u00ae DB2\u00ae Enterprise Server Edition 10.5; for high availability environment only\n \n Custom installation; Reporting Services * Jazz\u2122 for Service Management 1.1.3.0\n * IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0\n * IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9; optional if already installed\n * IBM\u00ae DB2\u00ae Enterprise Server Edition 10.5; optional if already installed\n \n \n 3. Create one or more of the following temporary directories in the same file system: * JazzSM_Image_Home directory; which refers to the directory that will contain the extracted contents of the Jazz for Service Management platform-specific image.\n * Image_Imgs_Home directory; which refers to the directory that will contain the extracted contents of platform-specific images for middleware. Tip: You only create this directory if you intend to install IBM DB2\u00ae; IBM WebSphere\u00ae Application Server.\n \n \n \n \n 4. Navigate to the IBM Passport Advantage web site [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm]. \n Note: You require an IBM Customer ID to sign in and continue.\n 5. Select the Find by part number search option under Download finder options.\n 6. Search for each downloadable image by part number; as outlined in the relevant Operating_System tab in this download document.\n 7. Select and download only the images for your platform that you need.\n 8. Extract the downloaded images into directories that you created in step 3. \n \n Important: If you have downloaded the middleware and you want to perform a full installation; ensure that your Install_Imgs_Home directory is set up as follows:\n |-ESE (Windows) [extracted DB2 installation image on Windows] \n |-ese (UNIX) [extracted DB2 installation image on AIX; Linux; or Linux for System z] \n |-WASRepository [extracted WebSphere Application Server installation image]\n |-TCRCognos [extracted Tivoli Common Reporting Cognos\u00ae installation image] This directory structure is not required for a custom installation; for example; installing a subset of integration services by using the launchpad custom workflow or IBM Installation Manager GUI.\n \n \n 9. To perform a full installation; download the Quick Start image with a part number of CNC1MML. It contains quick start guides for these installation scenarios. * CNC1MML_JazzSM_lang_code.pdf - Quick start guide for the full installation scenario; to install all Jazz for Service Management integration services; IBM DB2\u00ae; and IBM WebSphere\u00ae Application Server on a single server for evaluation and development purposes. \n \n \n 10. If you want to perform a custom installation; for example; install only a subset of Jazz for Service Management integration services or use existing supported installations of WebSphere Application Server or DB2; see Custom installation scenario [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEKCU_1.1.3.0\/com.ibm.psc.doc\/install\/psc_c_install_advanced_opt.html] in the Jazz for Service Management documentation.\n\n\n\nTAB NAVIGATION\n * AIX\u00ae\n * Linux\n * Linux on System z\u00ae\n * Windows\n\n\n\nSee Jazz for Service Management Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038732] for the AIX operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1NML Jazz for Service Management 1.1.3.0 for AIX\u00ae; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0\n\nCNC1SML IBM Tivoli Common Reporting 3.1.3.0 for AIX\u00ae; 64-bit; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Reporting Services and Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC1YML IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9 for Jazz for Service Management for AIX\u00ae; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3TML IBM\u00ae DB2\u00ae Enterprise Server Edition V10.5 for AIX\u00ae Multilingual CIPH4ML IBM\u00ae DB2\u00ae 10.5 Enterprise Server Edition - Restricted Use Quick Start and Activation Multiplatform Multilingual CIWM8ML IBM\u00ae DB2\u00ae 10.5 National Language Pack for AIX\u00ae Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038732] for the Linux operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1PML Jazz for Service Management 1.1.3.0 for Linux\u00ae; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 18.2; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1TML IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0 for Linux\u00ae; 64-bit; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC1ZML IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9 for Jazz for Service Management for Linux\u00ae; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIXV0ML IBM\u00ae DB2\u00ae Enterprise Server Edition V10.5 for Linux\u00ae on AMD64 and Intel\u00ae EM64T systems (x64) Multilingual CIPH4ML IBM\u00ae DB2\u00ae 10.5 Enterprise Server Edition - Restricted Use Quick Start and Activation Multiplatform Multilingual CIWM5ML IBM\u00ae DB2\u00ae 10.5 National Language Pack for Linux\u00ae on AMD64 and Intel\u00ae EM64T systems (x64) Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038732] for the Linux on System z operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1QML Jazz for Service Management 1.1.3.0 for Linux\u00ae on System z\u00ae; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration service: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1UML IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0 for Linux\u00ae on System z\u00ae; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC20ML IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9 for Jazz for Service Management for Linux\u00ae on System z\u00ae; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3SML IBM\u00ae DB2\u00ae Enterprise Server Edition V10.5 for Linux\u00ae on System z\u00ae Multilingual CIWM7ML IBM\u00ae DB2\u00ae 10.5; National Language Pack V10.5 for Linux\u00ae on System z\u00ae Multilingual Back to top\n\nSee Jazz for Service Management Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038732] for the Windows operating systems on which Jazz for Service Management is supported.\n\nDownloadable images with part numbers\n\nYou can download electronic images for Jazz for Service Management and its database and application server middleware. Refer to the following sections for details about the images that are required and optional.\n\n * Required software\n * Optional software\n\nRequired software Part number\n\nDescription\n\nCNC1RML Jazz for Service Management 1.1.3.0 for Windows; 64-bit; Multilingual\n\nContains the Jazz for Service Management launchpad; IBM Installation Manager Version 1.8.4.1; IBM Prerequisite Scanner Version 1.2.0.18; IBM Tivoli Directory Integrator Identity Edition Version 7.1.1.5; and the Installation Manager software packages for following integration services: IBM Dashboard Application Services Hub Version 3.1.3.0.\n\nCNC1VML IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0 for Windows; Multilingual\n\nContains the base installation image.\n\nOptional software Download the following supplemental software under the following conditions:\n\n * If you want to install Jazz for Service Management and its database and application server middleware on a single server for evaluation and development purposes; also referred to as a full installation.\n * If you do not have an existing supported version of WebSphere Application Server.\n * If you do not have an existing supported version of DB2 Enterprise Server Edition and you want to install Tivoli Common Reporting or Dashboard Application Services Hub in a high-availability environment.\n * If you want to set up Dashboard Application Services Hub in a high-availability environment.\n * If you want to model business data views of your data by using Framework Manager.\n\nOptional WebSphere Application Server software Part number\n\nDescription\n\nCNC21ML IBM\u00ae WebSphere\u00ae Application Server 8.5.5.9 for Jazz for Service Management for Windows; 64-bit; Multilingual\n\n \n\nContains WebSphere Application Server Version 8.5.5.9 and IBM WebSphere SDK for Java Technology Edition 7.0.8.0\n\nCI6X0ML\nCI6X1ML\nCI6X2ML\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (1 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (2 of 3) for Multiplatform; Multilingual\nIBM\u00ae WebSphere\u00ae Application Server V8.5 Supplements (3 of 3) for Multiplatform; Multilingual\n\n\nContains supplemental WebSphere Application Server software; including IBM HTTP Server and IBM HTTP Server plug-in for IBM WebSphere Application Server.\n\nImportant: Download only if you want to set up Dashboard Application Services Hub in a high-availability environment. You must download all 3 images and extract them to the same location.\n\nOptional DB2 software Part number\n\nDescription\n\nCIW3YML IBM\u00ae DB2\u00ae Enterprise Server Edition V10.5 for Windows on AMD64 and EM64T systems (x64) Multilingual CIPH4ML IBM\u00ae DB2\u00ae 10.5 Enterprise Server Edition Restricted Use Quick Start Guide and Activation Optional Tivoli Common Reporting 3.1.2.0 software Part number\n\nDescription\n\nCNC1WML IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0 IBM\u00ae Cognos\u00ae Framework Manager for Windows; Multilingual\n\nCNC1XML IBM\u00ae Tivoli\u00ae Common Reporting 3.1.3.0 IBM\u00ae Cognos\u00ae Cube Designer for Windows; Multilingual\n\nBack to top\n\nConnect; learn; and share with the Jazz for Service Management Community Jazz for Service Management has an active community that can provide you with additional resources. Browse and contribute to the forums and the blog. Review the wiki on topics such as best practices. You can also learn more about upcoming releases; provide feedback; or suggest enhancements.\nSee the Jazz for Service Management community [https:\/\/www.ibm.com\/developerworks\/servicemanagement\/jazzsm\/index.html] on Service Management Connect."}]},{"id":"DEV_Q001","question":"What can be done about \"Too many open files\" messages in the DASH systemOut?\n\nWhat can be done about \"Too many open files\" messages in the DASH systemOut log on an AIX box?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q002","question":"Unable to open profile from P8 Content Engine Configuration manager (CMUI) on Redhat Linux 7.2, getting GPF and javacore dump.\n\n\n\nLaunch configmgr then try to open an existing profile. Once I click ok on the dialog box to\n\"Verify your application server setting before proceeding...\" Configuration manager would crash and GPF. I can see the javacore.txt and dmp file created.\nThe javacore.txt contains the following:\n\n0SECTION TITLE subcomponent dump routine NULL =============================== 1TICHARSET UTF-8 1TISIGINFO Dump Event \"gpf\" (00002000) received 1TIDATETIME Date: 2016\/05\/05 at 04:53:30 1TIFILENAME Javacore filename: \/opt\/IBM\/FileNet\/ContentEngine\/tools\/configure\/javacore.20160505.045330.25035.0002.txt 1TIREQFLAGS Request Flags: 0x81 (exclusive+preempt) 1TIPREPSTATE Prep State: 0x100 (trace_disabled) 1TIPREPINFO Exclusive VM access not taken: data may not be consistent across javacore sections NULL ------------------------------------------------------------------------ 0SECTION GPINFO subcomponent dump routine NULL ================================ 2XHOSLEVEL OS Level : Linux 3.10.0-327.13.1.el7.x86_64 2XHCPUS Processors - 3XHCPUARCH Architecture : x86 3XHNUMCPUS How Many : 1 3XHNUMASUP NUMA is either not supported or has been disabled by user NULL\n1XHEXCPCODE J9Generic_Signal_Number: 00000004 1XHEXCPCODE Signal_Number: 0000000B 1XHEXCPCODE Error_Value: 00000000 1XHEXCPCODE Signal_Code: 00000080 1XHEXCPCODE Handler1: F72A2E6A 1XHEXCPCODE Handler2: F724D00A 1XHEXCPCODE InaccessibleAddress: 00000000 NULL\n1XHEXCPMODULE Module: \/lib\/libcairo.so.2 1XHEXCPMODULE Module_base_address: D55FC000\n\nThis is a Redhat Linux 7.2 environment with Content Platform Engine CPE 5.2.1.4.","answer":"Install the missing libraries \"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit. Please contact RedHat to obtain the missing libraries.","is_impossible":false,"contexts":[{"filename":"swg21978390.txt","text":"Title: IBM Unable to open a profile in FileNet Content Engine Configuration Manager User Interface (CMUI) on Redhat Linux 7.x - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Unable to open a profile in FileNet Content Engine Configuration Manager User Interface (CMUI) on Redhat Linux 7.x. \n\nSYMPTOM\nCMUI will javacore with the following in the javacore.txt \n\n1XHEXCPCODE J9Generic_Signal_Number: 00000004\n1XHEXCPCODE Signal_Number: 0000000B\n1XHEXCPCODE Error_Value: 00000000\n1XHEXCPCODE Signal_Code: 00000080\n1XHEXCPCODE Handler1: F7169E6A\n1XHEXCPCODE Handler2: F711400A\n1XHEXCPCODE InaccessibleAddress: 00000000\nNULL\n1XHEXCPMODULE Module: \/lib\/libcairo.so.2\n1XHEXCPMODULE Module_base_address: D5436000 \n\n\nCAUSE\n\"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit libraries were missing. \n\n\n\nRESOLVING THE PROBLEM\nInstall the missing libraries \"adwaita-gtk2-theme\" (32 and 64 bit) and \"adwaita-gtk3-theme\" 64 bit. Please contact RedHat to obtain the missing libraries."}]},{"id":"DEV_Q003","question":"Is there a way set a timeout for shell task?\n\nI have run into couple of shell task in Urbancode, for example start websphere server, or run a test.bat file using the shell task, The problem I have, though the task is successful executed, it keeps ruining this shell task and does not moving to the next task. Can I set a time out for the shell task","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q004","question":"Error #2070\n\nI purchased the SPSS grad pack and put one of the licenses on one computer and another on this one. This computer crashed and I was forced to reformat the hard drive. Subsequently, I lost SPSS in the process. After reinstalling the program, when I attempted to open a data set I received this error:\n\nError # 2070 The application is unable to communicate properly with the license server. The license server may be down, or there may be other network-related communication or DNS issues interfering. This command is not executed. Specific symptom number: 3","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q005","question":"I am getting a random invalid handle exception for my MQ .NET client applicatoin.\n\nWhile running a MQ .NET application, I get the following exception at random times:\n\n Event Type: Error\n Event Source: ClientApplicationName\n Event Category: None\n Event ID: 0\n Date: 8\/12\/2015\n Time: 7:19:51 AM\n User: N\/A\n Computer: TXPILAP01\n Description:\n System.ComponentModel.Win32Exception (0x80004005): The handle is invalid\n at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32\n processId, Boolean firstModuleOnly)\n at System.Diagnostics.ProcessManager.GetModuleInfos(Int32 processId)\n at System.Diagnostics.Process.get_Modules()\n at IBM.WMQ.Nmqi.UnmanagedNmqiMQ.MQCONNX(String pQMgrName, MQCNO&\n pConnectOpts, Hconn parentHconn, Phconn phconn, Int32& pCompCode,\n Int32& pReason)\n at IBM.WMQ.Nmqi.UnmanagedNmqiMQ.MQCONNX(String pQMgrName,\n MQConnectOptions pConnectOpts, Phconn phconn, Int32& pCompCode, Int32&\n pReason)\n at IBM.WMQ.MQQueueManager.Connect(String queueManagerName)\n at IBM.WMQ.MQQueueManager..ctor(String queueManagerName, String\n Channel, String ConnName)\n at ClientApplicationName.ServiceAgents.Integration.MQISA.\n InitializeQueueManager(String queueManagerName)\n at ClientApplicationName.ServiceAgents.Integration.MQISA.SendRequest\n (String request)","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q006","question":"After applying cumulative fix, why does xmlaccess use the base portal instead of the virtual portal when attempting an export or import?\n\nAfter applying a cumulative fix (CF) to WebSphere Portal 8.5 (with no other CF currently applied), attempts to export from or import to a virtual portal result in the action occurring against the base portal. This can be confirmed when looking at the exported xml and seeing the following in the initial comment of the export: \nvirtual portal: none (default virtual portal) ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q007","question":"Which Socket Gateway should I be using with Netcool Omnibus (NOI) ?\n\nWhich Socket Gateway should I be using with Netcool Omnibus (NOI) ?\n\nThere are 2 versions of the gateway; nco-g-socket-java-2_0 and nco-g-socket-10_0 Users may be confused what version they should download or use ","answer":"A new version of the Netcool\/OMNIbus Socket Gateway will be available to download from August 6, 2015.","is_impossible":false,"contexts":[{"filename":"swg21625776.txt","text":"Title: IBM Netcool\/OMNIbus Integrations Release Notice - Socket Gateway (nco-g-socket-java-2_0) - United States\n\nText:\nrelease note; downloads; nco-g-socket-java; Java Gateway for Socket NEWS\n\nABSTRACT\n A new version of the Netcool\/OMNIbus Socket Gateway will be available to download from August 6, 2015. \n\nCONTENT\n \n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com\/support\/knowledgecenter\/SSSHTQ\/omnibus\/gateways\/socketjavagw\/wip\/concept\/socketjavagw_instl_cnfgr_gateway.html [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHTQ\/omnibus\/gateways\/socketjavagw\/wip\/concept\/socketjavagw_instl_cnfgr_gateway.html]\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm]\n\nNetcool\/OMNIbus V8.1\n\nThe Netcool\/OMNIbus V8.1 version of this gateway supports the following Operating Systems:\n\nAIX, Linux, Solaris, Windows and zLinux.\n\nIf you are running Netcool\/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this package, use the Find by part number field to search for part number: CN6I1EN\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 CN6GZEN AIX CN6H1EN HPUX on Itanium CN6H2EN Linux CN6H3EN Linux for zSeries CN6H4EN Solaris CN6H5EN 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]"}]},{"id":"DEV_Q008","question":"How can I export a private key from DataPower Gateway Appliance?\n\n\n\nHow can I export a private key from DataPower Gateway appliance?\n\n","answer":"HSM-enabled DataPower appliances support the export of private keys using the crypto-export command.","is_impossible":false,"contexts":[{"filename":"swg21412061.txt","text":"Title: IBM How to export and import keys from an HSM-enabled IBM WebSphere DataPower SOA Appliance - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance? \n\nANSWER\nHSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met: \n\n * HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n * The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n * HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.\n\n\nEach HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about hsm-clone-kwk, red keys, or the hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :- \n\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization). \n\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable. \n\nFinally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command). \n\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import. \n\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time. \n\nFor additional information refer to the online Info Center [http:\/\/publib.boulder.ibm.com\/infocenter\/wsdatap\/v3r8m2\/index.jsp?topic=%2Fxi50%2Fwelcome.htm] and search for \"PIN entry device\".\n\nNote: You will need to sign into the documentation portal with your IBM Registration ID and password."}]},{"id":"DEV_Q009","question":"\"The transaction log for database BPMDB is full\" error message is seen when running BPMInstallOfflinePackage\n\nDuring our latest deployment of a larger process application we received the following error\n\nThe transaction log for database 'BPMDB' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases\nWhy does this happen. The transaction log for the database is 80GB which should be sufficient.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q010","question":"We transferred the database to an external database on our Portal 8.5 environment and now seeing errors, EJPDB0085W and EJPFD0016E in the logs\n\n\n\nAfter transferring the Portal database we seeing the following....\n\n [3\/1\/16 6:22:19:481 CST] 00000071 DataStoreServ W com.ibm.wps.services.\n datastore.DataStoreServiceImpl checkCorrectSetup EJPDB0085W: The\n character encoding of the database is not UTF-8.\n [3\/1\/16 6:22:19:528 CST] 00000071 Servlet E com.ibm.wps.engine.\n Servlet init EJPFD0016E: Initialization of service failed.\n com.ibm.wps.util.DataBackendException:\n EJPDB0160E: The sanity checks of the database layer failed.\n at com.ibm.wps.services.datastore.DataStoreServiceImpl.\n checkCorrectSetup(DataStoreServiceImpl.java:712)\n at com.ibm.wps.services.datastore.DataStoreServiceImpl.\n init(DataStoreServiceImpl.java:288)\n\n...\n\n [3\/1\/16 6:22:19:824 CST] 00000071 DatabaseInsig W com.ibm.wps.datastore.\n dbinsight.DatabaseInsight checkCharacterEncodingForOracle EJPDB0166W:\n The character encoding of database domain [[Domain: jcr]] is not\n correct. The value [WE8MSWIN1252] is set for key [NLS_CHARACTERSET] in\n parameter section [NLS_DATABASE_PARAMETERS] where expected values only\n can contain one of [[UTF8, AL16UTF16, AL32UTF8, UTFE]].\n\\","answer":"At this point there is no way to salvage the database in its current state. The entire Portal database must be dropped and recreated using the specifications provided in the InfoCenter at this link: \n\n\nhttp:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.e [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/index.jsp?topic=\/com.ibm.wp.ent.doc\/config\/aix_oracle_create_db.html]","is_impossible":false,"contexts":[{"filename":"swg21317981.txt","text":"Title: IBM 'EJPDB0160E: The sanity checks of the database layer failed' error occurs during startup after successful database transfer - United States\n\nText:\nEJPDB0160E: The sanity checks of the database layer failed. EJPDB0160E TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After receiving a 'Build Successful' message during a database transfer for IBM\u00ae WebSphere\u00ae Portal, you attempt to start WebSphere_Portal and receives this error message, \"EJPDB0160E: The sanity checks of the database layer failed\". \n\nSYMPTOM\nThe entire error message and stack trace will appear like this in the SystemOut.log: \n\n=======================================================================================\n\n[8\/19\/08 15:51:50:788 EDT] 0000001e DataStoreServ W com.ibm.wps.services.datastore.DataStoreServiceImpl checkCorrectSetup EJPDB0085W: The character encoding of the database is not UTF-8.\n[8\/19\/08 15:51:50:822 EDT] 0000001e Servlet E com.ibm.wps.engine.Servlet init EJPFD0016E: Initialization of service failed.\ncom.ibm.wps.util.DataBackendException: EJPDB0160E: The sanity checks of the database layer failed.\nat com.ibm.wps.services.datastore.DataStoreServiceImpl.checkCorrectSetup(DataStoreServiceImpl.java:669)\nat com.ibm.wps.services.datastore.DataStoreServiceImpl.init(DataStoreServiceImpl.java:288)\nat com.ibm.wps.services.Service.init(Service.java:107)\nat com.ibm.wps.services.Service.init(Service.java:83)\nat com.ibm.wps.services.ServiceManager.createService(ServiceManager.java:391)\nat com.ibm.wps.services.ServiceManager.initInternal(ServiceManager.java:285)\nat com.ibm.wps.services.ServiceManager.init(ServiceManager.java:179)\nat com.ibm.wps.services.ServiceManager.init(ServiceManager.java:114)\nat com.ibm.wps.engine.Servlet.init(Servlet.java:239)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:199)\nat com.ibm.ws.wswebcontainer.servlet.ServletWrapper.init(ServletWrapper.java:319)\nat com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1230)\nat com.ibm.ws.wswebcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:152)\nat com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:99)\nat com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:849)\nat com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:771)\nat com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:491)\nat com.ibm.ws.webcontainer.webapp.WebApp.commonInitializationFinish(WebApp.java:328)\nat com.ibm.ws.wswebcontainer.webapp.WebApp.initialize(WebApp.java:290)\nat com.ibm.ws.wswebcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:90)\nat com.ibm.ws.wswebcontainer.VirtualHost.addWebApplication(VirtualHost.java:157)\nat com.ibm.ws.wswebcontainer.WebContainer.addWebApp(WebContainer.java:665)\nat com.ibm.ws.wswebcontainer.WebContainer.addWebApplication(WebContainer.java:618)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.install(WebContainerImpl.java:335)\nat com.ibm.ws.webcontainer.component.WebContainerImpl.start(WebContainerImpl.java:551)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1303)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1138)\nat com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:569)\nat com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:817)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:949)\nat com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2122)\nat com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:342)\nat com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1473)\n\n======================================================================================\n\n\nCAUSE\nThe database was not created using UTF-8 character encoding. \n\n\nDIAGNOSING THE PROBLEM\nOn an Oracle\u00ae environment you can run these SQL statements to determine the character sets: \n\n\n\nSELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER IN ('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET'); \nSELECT PROPERTY_VALUE FROM DATABASE_PROPERTIES WHERE PROPERTY_NAME IN \n('NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET'); \n\nIn this case the customer had these results for both SQL statements:\n\n============================= \nPROPERTY_VALUE \n------------- \nWE8ISO8859P1 \nAL16UTF16 \n=============================\n\nIf the database character sets had been setup correctly then both lines would have read \"AL16UTF16\". In this case NLS_CHARACTERSET returns \"WE8ISO8859P1\" which is not a supported format. If the database had been setup correctly both lines would have produced \"AL16UTF16\". \n\n\n\nRESOLVING THE PROBLEM\nAt this point there is no way to salvage the database in its current state. The entire Portal database must be dropped and recreated using the specifications provided in the InfoCenter at this link: \n\n\nhttp:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/topic\/com.ibm.wp.e [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/index.jsp?topic=\/com.ibm.wp.ent.doc\/config\/aix_oracle_create_db.html]\nnt.doc\/config\/aix_oracle_create_db.html [http:\/\/publib.boulder.ibm.com\/infocenter\/wpdoc\/v6r1m0\/index.jsp?topic=\/com.ibm.wp.ent.doc\/config\/aix_oracle_create_db.html] \n\nThis is the specific information in the Information Center pertaining to character encoding:\n\n=============================\n\nAll databases must be created using UNICODE Database and National character sets such as UTF8, AL32UTF8, or AL16UTF16. \n\n============================="}]},{"id":"DEV_Q011","question":"How to proceed when jextract utility is throwing an OutOfMemory error ?\n\n\n\nI was getting a crash and was told to provide a \"jextracted core dump\". I ran the jextract command as instructed:\n\n\/java\/jre\/bin\/jextract [CORE_PATH]\n\nbut I am getting now an OutOfMemory error when jextract itself is running so I cannot proceed with the original crash investigation.","answer":"Sometimes the core dump is much larger than the default heap size can manage, and the recommendation is to increase the heap size using the -J-Xmx option.","is_impossible":false,"contexts":[{"filename":"swg21577379.txt","text":"Title: IBM How to process an IBM SDK core dump with Jextract (AIX, Linux, Windows) - United States\n\nText:\ncrash; coredump; dumps; dump; dmp; dmps; jextracted; jextract; userdump; dtfj TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How do you process a raw core dump using Jextract? \n\nJextract is a tool provided with the IBM SDK to process and compress a core dump for later processing with tools such as DTFJ, which can be downloaded with IBM Support Assistant. \n\nRESOLVING THE PROBLEM\nYou can process a core dump with Jextract, as long as the dump itself was produced by the IBM WebSphere Application Server JVM and is processed on the same system as the dump. \n\nA processed dump can be used in both the Eclipse Memory Analyzer Tool [http:\/\/www.ibm.com\/developerworks\/java\/jdk\/tools\/mat.html] and the DTFJ Dump Analyzer [http:\/\/www.ibm.com\/developerworks\/java\/jdk\/tools\/dumpanalyzer\/]. Both are included as downloadable tools from within IBM Support Assistant Workbench [http:\/\/www.ibm.com\/software\/support\/isa\/]. \n\n\n\n\nLocating the Core Dump \n\nFor WebSphere Application Server installations, the default location for the core dumps is in the profile's root directory: <WAS_HOME>\/profiles\/<PROFILE_NAME>\/ \n\nThe file extension will usually be *.dmp, but on some versions of AIX and Linux, the file may simply be named core. The process id and the date stamp are normally appended to the name of the file. \n\n\n\n\nProcessing the Dump \n\nExecute the jextract command on the same system and installation of WebSphere Application Server that the core dump was produced on. If you don't use the full path on AIX or Linux, make sure to use .\/jextract (including the dot-slash) so the correct executable is picked up. \n\nReplace [COREDUMP_PATH] with the full path plus filename of the core dump produced. \n\n \n\nIf you do not know if compressed references is enabled, scroll to the FAQ section for a brief explanation. \n\n \n\nDetermining the Java Directory \n\nBecause different profiles on WebSphere Application Server 8.5.5.X and later can use different SDKs, the java directory inside the installation folder can differ. To determine the path, check the process list for the application server process and see which folder the java executable is being launched from. \n\n \n\nNOTE: If you are on WebSphere Liberty and are using an IBM SDK, the entire path to that SDK will differ. \n\n \n\n\n\n\n32-bit JVM and\n64-bit JVM with Compressed References disabled\nAIX\/Linux: \n<WAS_HOME>\/<JAVA_DIR>\/jre\/bin\/jextract [COREDUMP_PATH]\n\nWindows: \n<WAS_HOME>\\<JAVA_DIR>\\jre\\bin\\jextract.exe [COREDUMP_PATH]\n\n\n\n\n64-bit JVM with Compressed References enabled\nDoes not apply to WebSphere Application Server 6.1\nAIX\/Linux: \n<WAS_HOME>\/<JAVA_DIR>\/jre\/bin\/jextract -J-Xcompressedrefs [COREDUMP_PATH]\n\nWindows: \n<WAS_HOME>\\<JAVA_DIR>\\jre\\bin\\jextract.exe -J-Xcompressedrefs [COREDUMP_PATH] \n\n \n\n\n\n\nMax Heap Size \n\nTo adjust the max heap size, you can add -J-Xmx to adjust the size. For example, -J-Xmx1024m allows for a max heap size of 1024 MB when jextract is run. \n\n \n\n \n\n\n\n\nFiles Generated \n\nThe output will determine where the compressed data is stored (usually a .zip extension, .sdff is seen on older environments). Check the location of the core dump as that will be the most common location. \n\nCore files are usually compressible since a lot of data is zero; 10x compression can be expected in the resulting zip file \n\n \n\nIf you find XML files in the output directory, this may mean jextract failed, as these files are supposed to be placed automatically within the SDFF or ZIP file. \n\n \n\n\n\n\nError Messages \n\nEyeCatcher Error\nUnable to find J9VMRAS eyecatcher\nError. Internal failure detected during jextract \n\nThis error message indicates that jextract failed to identify the dump. This could be due to a number of things, including \n\n* The dump was not produced by WebSphere Application Server\n* The dump was produced from a native library or component such as a JNI component or database driver.\n* (AIX only) The dump generated is in an incompatible dump format due to an AIX OS issue (see APAR IZ88097 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IZ88097] for more details). \n\n \n\nOut of Memory Error \n\nSometimes the core dump is much larger than the default heap size can manage, and the recommendation is to increase the heap size using the -J-Xmx option. \n\n \n\n\n\n\nFAQ \n\nHow do I determine if compressed references is enabled? \n\nCompressed references were first introduced in 64-bit builds of IBM SDK 6.0. If WebSphere Application Server is at version 7.0.0.3 or higher, it will be enabled by default; see APAR PK75174 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1PK75174]. \n\nChecking the JVM arguments in the admin console can verify if compressed references was enabled manually. However, it's best to check the ps output or the javacore for the argument -Xcompressedrefs \n\nIf you find the argument -Xnocompressedrefs has been added, this means it's disabled (see page 7 of this document [ftp:\/\/public.dhe.ibm.com\/software\/webserver\/appserv\/was\/WAS_V7_64-bit_performance.pdf] for more info)) \n\n \n\nWhat happens to jextract if I cannot determine if compressed references was enabled? \n\nIf you run jextract and did not realize compressed references was enabled, the output will ask you to rerun jextract and add the following argument: -J-Xcompressedrefs \n\n\n\nRELATED INFORMATION\n MustGather: Crash on AIX [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21055387]\nMustGather: Crash on Linux [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21104706]\nMustGather: Crash on Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21053924]\nGenerating Userdumps on Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21138203]\nCrash on AIX produces no core or a truncated core [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21052642]\nCrash on Linux produces no core or a truncated core [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21115658]"}]},{"id":"DEV_Q012","question":"I receive the following during UDX compilation Can't exec \"\/nz\/kit\/bin\/adm\/nzudxcompile\": Argument list too long\n\n","answer":"This ARG_MAX kernel parameter adjusted to much larger from kernel release version 2.6.23, that is 2621440 (http:\/\/www.in-ulm.de\/~mascheck\/various\/argmax [http:\/\/www.in-ulm.de\/~mascheck\/various\/argmax]). \n\nBut we support upto Redhat 5.11 in Twinfin which is less than kernel release 2.6.23. So we have no way to allow ARG_MAX larger than 131072 at this time.","is_impossible":false,"contexts":[{"filename":"swg21959723.txt","text":"Title: IBM UDX compilation error - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n English \n\nPROBLEM(ABSTRACT)\n Following error can be met during UDX compilation.\nCan't exec \"\/nz\/kit\/bin\/adm\/nzudxcompile\": Argument list too long \n\nSYMPTOM\nnzudxcompile command returns an \"Argument list too long\" error and aborts.\n\n\nCAUSE\nARG_MAX configuration parameter limits the number of argument list in command line. In this case the client used more than 131072 argument with many program *.c files.\n\nDIAGNOSING THE PROBLEM\nCheck ARG_MAX value in the command line: \n\n$ getconf ARG_MAX\n131072\n\n\nRESOLVING THE PROBLEM\nThis ARG_MAX kernel parameter adjusted to much larger from kernel release version 2.6.23, that is 2621440 (http:\/\/www.in-ulm.de\/~mascheck\/various\/argmax [http:\/\/www.in-ulm.de\/~mascheck\/various\/argmax]). \n\nBut we support upto Redhat 5.11 in Twinfin which is less than kernel release 2.6.23. So we have no way to allow ARG_MAX larger than 131072 at this time."}]},{"id":"DEV_Q013","question":"Additional steps to apply fix pack to Decision Center\n\n\n\nWe are upgrading ODM 8.8.1 Decision Center to the latest 8.8.1.3.\n\nAre there any additional steps to apply the fixpack to Decision Center after we install the fixpack with Installation Manager?","answer":"As with any software product, even if you do not have any issues with running your current configuration, you should apply the latest modification or fix pack to take advantage of these benefits: \n\n * Anticipate and avoid the risk of encountering defects already fixed. \n * Apply the latest product improvements that are available (performance, for example). \n * Maintain a serviceable system and be able to install an interim fix when required.","is_impossible":false,"contexts":[{"filename":"swg21665766.txt","text":"Title: IBM When and how to apply a modification or fix pack - United States\n\nText:\nfix pack update bug correction APAR TECHNOTE (FAQ)\n\nQUESTION\n When and how should I apply a modification or fix pack to my JRules or Operational Decision Management (WODM\/ODM) installation?\n\n\nCAUSE\nThe Operational Decision Manager version numbers use the standard IBM formatV.R.M.Fwhich stands for Version.Release.Modification.Fixpack. See the V.R.M.F Maintenance Stream Delivery Vehicle terminology explanation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27008656] for more details. \n\n\nModification and fix pack numbers are the third and fourth digits in the IBM product version number, for example: 8.5.M.F. \n\n\nModification and fix packs include only bug fixes, so they do not affect the product functionality or your data.\n\n\nSee the following technotes to find out which update your installation need:\n\n\n * Finding the version of ODM product and fixes [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21627850] to determine the exact product versions that are installed on your machine.\n \n * Find the version of ODM components [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21400738] to determine the exact module or library versions that are deployed on your servers.\n \n * Operational Decision Manager Download document [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24031636] to learn about the latest modification or fix pack that is available for your product version. \n \n * IBM Operational Decision Manager detailed system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27023067] to verify that your configuration is supported with your current product version.\n \n * IBM Support Lifecycle [http:\/\/www.ibm.com\/software\/websphere\/support\/lifecycle\/] to verify that your current version does not reach end of support in the near future.\n\n\n\nReferring to the last two documents above, you may find out that you need to migrate to the latest product version to ensure continued support of your applications. In that case, refer to technote Migrating to the latest version of Operational Decision Management [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21589725]. \n\nThat being said, make sure to consider migrating to the latest version or release ( V.R.M.F) of the product as soon as possible to benefit from the latest added features and improvements. \nANSWER\nAs with any software product, even if you do not have any issues with running your current configuration, you should apply the latest modification or fix pack to take advantage of these benefits: \n\n * Anticipate and avoid the risk of encountering defects already fixed. \n * Apply the latest product improvements that are available (performance, for example). \n * Maintain a serviceable system and be able to install an interim fix when required.\n\n\n\nWHEN TO UPDATE\nThe latest modification or fix pack should be installed as soon as it is available. \n\nYou can subscribe to the IBM Support My Notifications [https:\/\/www.ibm.com\/support\/mynotifications] to be notified of any fix pack releases, and you can also bookmark the Operational Decision Manager Download document [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24031636] page, which lists the latest modifications or fix packs. \n\nSee the technote Fix pack release notification for Operational Decision Manager [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21665593] to find out when a modification or fix pack will be available.\n\n\n\n\n\n\nBEFORE UPDATING\n\n\nThe databases used in the sample server are deleted and recreated during the update. If you are using those databases and want to save the existing content, perform the following steps before updating: \n * Stop the sample server. In the folder <ODM_HOME>\/shared\/data\/derby, create an archive file containing the resdb and rtsdb folders. Save the archive file, such as zip file, in the data folder. After installation, unzip the archive file in the folder <ODM_HOME>\/shared\/data\/derby to restore your databases before restarting the sample server. \n\n\n\nA new profile is also created for the sample server, at the first server start following the installation of a modification or fix pack. \n\nIf you want to continue using the same ports, you must delete the existing profile prior. In the <ODM_HOME>\/shared\/bin folder, from the command line, run the command ..\/tools\/ant\/bin\/ant forcedestroyprofile. \n\n\nNote: The sample server is not designed to be used in a production system. For a production system, you must create a dedicated profile and database that you update using the following steps. \n\n\n\n\nUPDATING\n\n\nEach modification or fix pack page provides instructions on how to download and run the installer, in addition to providing a list of corrections that are included in the update. \n\nThe fix pack installation updates the following files and folders: * JAR libraries in the installation directories, including <ODMInstallDir>\\<Module>\\lib. \n * EAR and WAR applications in the <ODMInstallDir>\\<Module>\\applicationservers\\<App Server> folders.\n\n\nOnce this is done, you perform these tasks: * Repackage your client applications with the up-to-date libraries. \n * Reapply product customizations to the up-to-date Java EE modules (EARs and WARs).\n\n\n\nNote that all customizations you developed before the update, for example modifications of the descriptors, must be reapplied to the new, up-to-date EARs and WARs. It is a good idea to document and automate those customizations using scripts to make the process easier and error-proof. \n\nFinally, you must update the client applications and ODM modules on your server or servers with the same settings as you deployed previously. If you redeploy the application, follow again the documentation instructions to deploy all ODM modules to your servers [http:\/\/pic.dhe.ibm.com\/infocenter\/dmanager\/v8r5m1\/topic\/com.ibm.odm.distrib.config\/topics\/odm_distrib_config.html]. \n\nKeep in mind that applying a modification or a fix pack does not require any data migration, so your projects and database remain the same. \n\nUPDATING RULE EXECUTION SERVER\n\n\nUpdate the following applications in the application server: * jrules-res-xu-<server>.rar jrules-res-management-<server>.ear jrules-ssp-<server>.ear jrules-res-htds-<server>ear \n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\nNote: Updating the eXecution Unit RAR file requires a restart of the server. \n\n\nUPDATE DECISION CENTER\n\n\nUpdate the following application in your application server: \n * jrules-teamserver-<server>.ear\n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\nUPDATE THE EVENTS RUNTIME\n\n 1. Stop the event runtime application, wberuntimeear. \n 2. Uninstall the following applications, if they exist: * wbefileconnector \n * wbehttpconnector \n * wbejdbcconnector \n * wbejmsconnector \n * wbesoapconnector\n \n \n 3. Update the application wberuntimeear. \n 4. Start the application wberuntimeear.\n\n\nMake sure you do not change the class loading policies for applications and modules ( parent last for all ODM modules). \n\n\n\n\nADDITIONAL CONSIDERATIONS\n * Again, in addition to applying the latest modification or fix pack, consider migrating to the latest version or release (V.R.M.F) of the product as soon as possible to benefit from recently added features and improvements. See our technote Migrating to the latest version of Operational Decision Management [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21589725] for more information. \n * For JRules 7.1, you can refer to the JRules 7.1 list of fix packs [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27019787] and also Upgrading JRules to the latest V7.1 fix pack [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21474292] to learn how to apply the fix packs. But note that JRules 7.1 reaches end of support in September 2015 (see the IBM Support Lifecycle [http:\/\/www.ibm.com\/software\/websphere\/support\/lifecycle\/] page). To ensure continued product support, plan an upgrade to the latest product version before that date.\n\nRELATED INFORMATION\n Fix pack release notification for ODM [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21665593 ]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere ILOG JRules Maintenance Platform Independent 7.1, 7.0"}]},{"id":"DEV_Q014","question":"Installing fixpacks with Installation Manager - when did it change from using updateInstaller, starting in which version of WebSphere\n\nI was using updateInstaller to install fixpacks, and there was a separate fixpack for WebSphere and separate for the JDK, independent of each other. Now I understand that with Installation Manager there is a single package containing both the WebSphere App server fixpack as well as the JDK. When did this occur, starting with which version of WebSphere ? ","answer":"","is_impossible":false,"contexts":[{"filename":"swg21138332.txt","text":"Title: IBM Java SDK Upgrade Policy for the IBM WebSphere Application Server - United States\n\nText:\nupgrade policy TECHNOTE (FAQ)\n\nQUESTION\n What is the Java\u2122 SDK upgrade policy for the IBM\u00ae WebSphere\u00ae Application Server? \n\nCAUSE\nUpdating to the latest compatible Java SDK could help you resolve problems more quickly.\n\nANSWER\nThe IBM WebSphere Application Server Java SDK can be upgraded to the latest service release for the same Java SDK version. \n\nList of WebSphere Application Server fix packs and the corresponding Java SDK versions [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27005002]\n\nPolicy Summary by WebSphere Application Server release:\n\nWebSphere Application Server V8.0, V8.5, V8.5.5\nStarting with V8.0 and applicable to all subsequent releases and fixpacks, there is one install package that contains updates for both WebSphere Application Server and Java SDK. Applying fixpacks of WebSphere Application Server also upgrades the SDK that is packaged and bundled within the fixpack. Additionally, separate Java SDK fixpacks are also available that contain just the SDK updates which can be applied to upgrade the SDK.\n\nWebSphere Application Server V7.0\nAny V7.0 fix pack can upgrade to the latest Java SDK 1.6.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.1\nAny V6.1 fix pack can upgrade to the latest Java SDK 1.5.0 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V6.0\nAny V6.0 fix pack can upgrade to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.1\nAny V5.1 fix pack can upgrade to the latest Java SDK 1.4.1 and any V5.1.1 can be upgraded to the latest Java SDK 1.4.2 service release packaged for WebSphere Application Server.\n\nWebSphere Application Server V5.0\nAny V5.0 fix pack can upgrade to the latest Java SDK 1.3.1 service release packaged for WebSphere Application Server.\n\n\n\nDetails of Java SDK Upgrade Policy\n\nWebSphere Application Server leverages the Java SDK as a base component. This results in unique support issues, including:\n\n\n * Matching Java SDK service releases to Application Server releases and fix packs\n \n \n * Delivering updates and fixes associated with the Java SDK on any given Application Server release.\n\n\nIn an effort to resolve customer Java SDK situations as quickly as possible, WebSphere Application Server Support has done a quickest-path-to-resolution analysis, determining the most direct way to collect problem information. \n\nIn some cases, problem resolution might include finding shortcuts to resolve symptoms. One shortcut is an immediate upgrade to a newer compatible Java SDK service release, before gathering detailed problem determination data. \n\nThere are multiple advantages to performing an immediate Java SDK upgrade as a quicker path to resolution over a full Problem Determination (PD) process: \n 1. There is a continuous stream of fixes going into the Java SDK. Many problems encountered by customers are resolved by these fixes.\n \n \n 2. When a new problem is encountered, applying the latest Java SDK is a quick way to determine if related fixes change the symptoms or correct the problem.\n \n \n 3. Many documented Java SDK fixes have common symptoms. Frequently, limited PD data does not isolate the problem to a single root cause.\n \n\n\nThese factors highlight the advantage of applying a newer Java SDK before working through a full PD cycle. \n\nJava SDK and WebSphere Application Server software are updated frequently. To avoid compatibility issues for customers, WebSphere Application Server Support maintains this Java SDK Upgrade Policy. \n\nWebSphere Application Server Support details: \nhttp:\/\/www.ibm.com\/software\/webservers\/appserv\/support.html [http:\/\/www.ibm.com\/software\/webservers\/appserv\/support.html] \n\nIdentifying compatibility limitations between WebSphere Application Server releases and Java SDK service releases that have not been tested together reduces risk. \n\nImportant: Using a Java SDK not specifically packaged with WebSphere Application Server and supplied by IBM, or in violation of the Java SDK Upgrade Policy, is not supported by IBM WebSphere Application Server Support for Java SDK problems. RELATED INFORMATION\n Verify Java SDK version shipped with WebSphere fix pack [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27005002]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"}]},{"id":"DEV_Q015","question":"DFHTS0001 0C4 AKEA at offset 3A1E in DFHTSPT\n\nWhy is my CICS region getting message DFHTS0001 reporting an abend 0C4\/AKEA at offset X'3A1E' in DFHTSPT? My CICS region was running normally and eventually received this abend.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q016","question":"How to configure DC to look on a different App server for the SSP?\n\n\n\nI have a single Application server with the RES console installed, and then a separate application server with the XU, the ssp ear, etc. on that one. Each app server is configured separately with respective ports. for example, mgmt server (with the RES console only) has port 8000, and the runtime server (with all of the runtime components) has port 9000.\n\nThe problem I am running into is the following:\n\nWhen I am trying to run a DVS test suite from Decision Center against RES, (my server endpoint in Decision Center is configured as http:\/\/hostname:port\/res)\n\nI am getting a \"the host and port are responsive but the \"\/testing\/sspService\" cannot be found. This is expected if it is looking on the same server as the RES console since the application (ssp) is not deployed there.\n\nHowever, I cannot seem to configure the RES console to not assume that the ssp is running on the same port.","answer":"First remember to pack all your XOMs (eXecutable Object Model) into the ssp.war following the documentation [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/topic\/com.ibm.websphere.ilog.jrules.doc\/Content\/Business_Rules\/Documentation\/_pubskel\/JRules\/ps_JRules_Global720.html]. \n\nThen make sure the SSP (ssp.war) is deployed on each server along with a XU connection factory and the appropriate datasource definition. \n\n \n\nThen create your own SSP resolver, add it to the teamserver.war and set the teamserver.defaultSSPResolver.class property to this class following this specification [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/index.jsp?topic=\/com.ibm.websphere.ilog.jrules.doc\/html\/api\/html\/ilog\/rules\/teamserver\/model\/testing\/IlrSSPResolver.html]. \n\n \n\nBy implementing your own method IlrSSPResolver.getSSPURL(String serverName,URL url), you will be able to point to something else than the default provider. \n\nThe default provider uses the url of the Rule Execution Server passed in parameter and replaces the application name with testing. \n\nA simple implementation can use the server name to return a specific server URL.","is_impossible":false,"contexts":[{"filename":"swg21502095.txt","text":"Title: IBM Distribute Decision Validation Service tests on different Rule Execution Server instances - United States\n\nText:\nSSPResolver; SSP TECHNOTE (FAQ)\n\nQUESTION\n Can I configure Rules Team Server to distribute the Decision Validation Service tests to multiple application servers? \n\nCAUSE\nWith a Rule Execution Server environment defined on a domain with multiple servers it is possible to define which Rule Execution Server instances will be used to execute the Rule Team Server Decision Services\n\nANSWER\nFirst remember to pack all your XOMs (eXecutable Object Model) into the ssp.war following the documentation [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/topic\/com.ibm.websphere.ilog.jrules.doc\/Content\/Business_Rules\/Documentation\/_pubskel\/JRules\/ps_JRules_Global720.html]. \n\nThen make sure the SSP (ssp.war) is deployed on each server along with a XU connection factory and the appropriate datasource definition. \n\n \n\nThen create your own SSP resolver, add it to the teamserver.war and set the teamserver.defaultSSPResolver.class property to this class following this specification [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/index.jsp?topic=\/com.ibm.websphere.ilog.jrules.doc\/html\/api\/html\/ilog\/rules\/teamserver\/model\/testing\/IlrSSPResolver.html]. \n\n \n\nBy implementing your own method IlrSSPResolver.getSSPURL(String serverName,URL url), you will be able to point to something else than the default provider. \n\nThe default provider uses the url of the Rule Execution Server passed in parameter and replaces the application name with testing. \n\nA simple implementation can use the server name to return a specific server URL. \n\nfor example you can have 2 servers defined in RTS: \n\n * testingServer1 http:\/\/host1:9080\/res \n * testingServer2 http:\/\/host1:9080\/res\n\n\nAnd your SSP provider can evaluate the SSP URL as follow : \nif ( serverName.equals(\"testingServer1\") )\n{\nreturn ( new URL( \"http:\/\/server1:9080\/testing\" ) );\n}\nelse if ( serverName.equals(\"testingServer2\") )\n{\nreturn ( new URL( \"http:\/\/server2:9080\/testing\" );\n}\nelse \nreturn( new URL( \"http:\/\/host1:9080\/testing\" )); \n\n \n\nThen when running a DVS test the execution will be dispatched according to the server you choose. \n\n \n\nFor a more elaborate implementation you can have a dependency with the project being tested so that you can distribute the DVS execution based on a project: \n\n\nManagerBean bean = ManagerBean.getInstance() ; \nIlrSession session = bean.getSession(); \nIlrRuleProject project = session.getWorkingBaseline().getProject();\nString pname = project.getName(); \n\n.\n\nRELATED INFORMATION\n#Repackaging the XOM for remote testing [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/topic\/com.ibm.websphere.ilog.jrules.doc\/Content\/Business_Rules\/Documentation\/_pubskel\/JRules\/ps_JRules_Global720.html]\nIlrSSPResolver [http:\/\/publib.boulder.ibm.com\/infocenter\/brjrules\/v7r1\/index.jsp?topic=\/com.ibm.websphere.ilog.jrules.doc\/html\/api\/html\/ilog\/rules\/teamserver\/model\/testing\/IlrSSPResolver.html]"}]},{"id":"DEV_Q017","question":"Can I perform a silent install of fix packs for IIB or WMB Toolkit?\n\nHow do I perform a silent install of fix packs for IBM Integration Bus (IIB) or WebSphere Message Broker (WMB) Toolkit?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q018","question":"Why am I getting error SqlIntegrityConstraintViolationException when deploying a process application?\n\nAfter reinstalling Process Center (or using separate Process Centers to deploy to one Process Server) you get a deployment failure error on the Process Server:\njava.lang.Exception: java.lang.Exception:com.lombardisoftware.client.delegate.BusinessDelegateException:PreparedStatementCallback; SQL [update LSW_SNAPSHOT set CREATED_ON =?,NAME = ?,ACRONYM = ?,DESCRIPTION = ?,SEQ_NUM = ?,ERROR_COUNTER =?,ORIG_CREATED_ON = ?,ACTIVATED_ON = ?,STATUS = ?,ARCHIVED_ON =?,LAST_MODIFIED = ?,REPOSITORY_BRANCH_ID = ?,CREATED_BY_USER_ID =?,BRANCH_ID = ?,PROJECT_ID = ?,LAST_MODIFIED_BY_USER_ID = ?,CHANGE_DATA= ?,IS_ACTIVE = ?,IS_BLA_ACTIVE = ?,IS_STARTED = ?,IS_INSTALLED =?,IS_BLA_INSTALLED = ?,IS_TIP_DEPLOYED = ?,IS_DEFAULT =?,TIP_DEPLOYMENT_IN_PROGRESS = ?,IS_ARCHIVED = ? where SNAPSHOT_ID = ?]; Error for batch element # 1: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=2;BPMBDBA.LSW_SNAPSHOT, DRIVER=4.11.69; nested exception iscom.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: Error forbatch element # 1: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,SQLERRMC=2;BPMBDBA.LSW_SNAPSHOT, DRIVER=4.11.69\nHow can I deploy my application?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q019","question":"Help with Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IIB and WMB (CVE-2015-0138)\n\nI need to understand details regarding Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker (CVE-2015-0138). This is also commonly referenced as \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS\/SSL client and server vulnerability. Where can I find this information? ","answer":"The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS\/SSL client and server vulnerability affects IBM\u00ae Runtime Environment Java\u2122 Technology Edition 6SR16 (and earlier) used by WebSphere Message Broker and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7SR8 (and earlier) or 7R1 (and earlier) used by IBM Integration Bus.","is_impossible":false,"contexts":[{"filename":"swg21700397.txt","text":"Title: IBM Security Bulletin : Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker (CVE-2015-0138) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n The \u201cFREAK: Factoring Attack on RSA-EXPORT keys\" TLS\/SSL client and server vulnerability affects IBM\u00ae Runtime Environment Java\u2122 Technology Edition 6SR16 (and earlier) used by WebSphere Message Broker and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition 7SR8 (and earlier) or 7R1 (and earlier) used by IBM Integration Bus. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-0138 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-0138]\nDESCRIPTION: A vulnerability in various IBM SSL\/TLS implementations could allow a remote attacker to downgrade the security of certain SSL\/TLS connections. An IBM SSL\/TLS client implementation could accept the use of an RSA temporary key in a non-export RSA key exchange ciphersuite. This could allow a remote attacker using man-in-the-middle techniques to facilitate brute-force decryption of TLS\/SSL traffic between vulnerable clients and servers. \n\nThis vulnerability is also known as the FREAK attack. \n\nCVSS Base Score: 4.3\nCVSS Temporal Score: See http:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691 [http:\/\/exchange.xforce.ibmcloud.com\/#\/vulnerabilities\/100691] 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 Integration Bus V9, V10 \nIBM Integration Bus Toolkit V9,\nWebSphere Message Broker V7 and V8 \nWebSphere Message Broker Toolkit V7 and V8\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10 IT07823 \nIT07802 The APARs are available in fixpack 10.0.0.1\nhttp:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040056 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24040056] IBM Integration Bus V9 IT07823 An interim fix is available from IBM Fix Central.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/Integration+Bus&release=All&platform=All&function=aparId&apars=IT07823]\n\nThe APAR is targeted to be available in fix pack 9.0.0.4. IBM Integration Toolkit V9 IT07802 An interim fix is available at [http:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v90\/MB900301\/]\nhttp:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v90\/MB900301\/ [http:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v90\/MB900301\/] WebSphere Message Broker\nV8\nIT07736 An interim fix is available from IBM Fix Central.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 8.0.0.6. WebSphere Message Broker Toolkit V8 IT07802 An interim fix is available at [http:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v80\/MB800501\/]\nhttp:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v80\/MB800501\/ [http:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v80\/MB800501\/] WebSphere Message Broker\nV7\nIT07736 An interim fix is available from IBM Fix Central.\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Message+Broker&release=All&platform=All&function=aparId&apars=IT07736]\n\nThe APAR is targeted to be available in fix pack 7.0.0.8. WebSphere Message Broker Toolkit V7 IT07802 An interim fix is available at\nhttp:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v70\/MB700702\/ [http:\/\/public.dhe.ibm.com\/software\/websphere\/studiotools\/wmbt\/v70\/MB700702\/] \nYou should verify applying this fix does not cause any compatibility issues. \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] WORKAROUNDS 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 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\nThe vulnerability was reported to IBM by Karthikeyan Bhargavan of the PROSECCO team at INRIA \n\nCHANGE HISTORY\n 01-Apr-2015: Original Copy Published\n01-Jun-2015: Added V10 & Toolkit fix links\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 IBM Integration Bus Security AIX, HP-UX, Linux, Solaris, Windows 10.0, 9.0 \nPRODUCT ALIAS\/SYNONYM\n WMB IIB"}]},{"id":"DEV_Q020","question":"ODR OOM issue\n\nI got ODR OOM after upgrading the WAS to v8553. No configuration or traffic load changing. Is there any known way to solve the problem? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q021","question":"How to refresh a DataPower WebService Proxy which WSDL got changed?\n\nI have made changes to a WSDL stored in DP local filesystem.\n\nHow can I make the WSP reflect this change since DataPower Gateway 7.1.0 WebService Proxy WebGUI doesn't offer the \"Refresh\" button anymore?\n\nIs there a best practice to refresh the WSP if I modified my WSDL?","answer":"In a WS Proxy, you can refresh WSDL from an URL using WSDL Cache policy. However, if the WSDL is hosted on the DataPower appliance, such as in local:\/\/\/, rather than on an external URL, the WSDL Cache Policy does not apply. \n\nFor instance, changes made to local:\/\/\/test.wsdl are not picked up by WS Proxy although there is a WSDL Cache policy setting the URL Match expression to local:\/\/\/test.wsdl. \n\nThis issue was reported to Quality Engineering but it was determined that the DataPower device is working as designed. The device will not poll WSDL files on the local store.\n\nThe WSDL Cache policy works with WSDL files hosted on an external URL.\n\nTo refresh a WSDL in the local:\/\/\/ directory, disable and re-enable the service.","is_impossible":false,"contexts":[{"filename":"swg21298897.txt","text":"Title: IBM WSDL Cache Policy not refreshing from WSDL in local:\/\/\/ directory - United States\n\nText:\ndatapower; wsdl cache refresh; wsdl; cache; refresh TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You created a Web Service Proxy (WS Proxy) based on a .wsdl file and want to refresh when there are changes in the .wsdl file. The file is located on the DataPower appliance under the \"local\" directory. You created a WSDL Cache Policy to specify the local .wsdl file for the URL Match expression, but the web service proxy state is not being refreshed when there are changes in the file. \n\nSYMPTOM\nThe WSDL Cache Policy is not refreshing from a WSDL in the local:\/\/\/ directory.\n\n\nRESOLVING THE PROBLEM\nIn a WS Proxy, you can refresh WSDL from an URL using WSDL Cache policy. However, if the WSDL is hosted on the DataPower appliance, such as in local:\/\/\/, rather than on an external URL, the WSDL Cache Policy does not apply. \n\nFor instance, changes made to local:\/\/\/test.wsdl are not picked up by WS Proxy although there is a WSDL Cache policy setting the URL Match expression to local:\/\/\/test.wsdl. \n\nThis issue was reported to Quality Engineering but it was determined that the DataPower device is working as designed. The device will not poll WSDL files on the local store.\n\nThe WSDL Cache policy works with WSDL files hosted on an external URL.\n\nTo refresh a WSDL in the local:\/\/\/ directory, disable and re-enable the service."}]},{"id":"DEV_Q022","question":"where is the websphere application server 9.0.0.4 fix for developers\n\nI am using the was 9.0.0.0 in rad\/rsa 9.6.1 for Windows. I cannot upgrade to the 9.0.0.4 fixpack, because there is no developer edition. On the downloadpage there are Base, Network Deployment, DMZ Secure Proxy Server and IBM Web Enablement for IBM i, but no Developers! See link text For was 8.5.5.10 there exists a developers edition. Where can I download the Websphere Application Server fix pack 9.0.0.4 Developers?","answer":"WAS recently renamed WAS for Developers (WAS4D) to WAS ILAN (see here [https:\/\/developer.ibm.com\/wasdev\/downloads\/#asset\/WAS_traditional_for_Developers]). In response to this change, RAD 9.6 now packages WAS ILAN available in the RAD_WS_9.6_WASTE_9.0.zip file. It has the same capabilities and updates that RAD users expect.","is_impossible":false,"contexts":[{"filename":"swg22005352.txt","text":"Title: IBM Upgrade Rational Application Developer 9.6 to use Websphere Application Server ILAN - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Customers see different content in the Rational Application Developer (RAD) Websphere Application Server (WAS) download compared to prior RAD releases.\n\nDuring install of this new WAS ILAN version, customers now see explicit wording saying this a no cost, non-supported and non-warranted version of WebSphere Application Server traditional. While this has always been the case for this developer version, refer to evaluation software page & FAQ below, seeing these words during install may be a new information for some users.\n\n\nCAUSE\nNew WAS packaged in RAD: \n\nRational Application Developer for WebSphere packages WebSphere Application Server for development and test purposes. WAS recently renamed WAS for Developers (WAS4D) to WAS ILAN (see here [https:\/\/developer.ibm.com\/wasdev\/downloads\/#asset\/WAS_traditional_for_Developers]). In response to this change, RAD 9.6 now packages WAS ILAN available in the RAD_WS_9.6_WASTE_9.0.zip file. It has the same capabilities and updates that RAD users expect. \n\nSupport for this new WAS packaged in RAD:\nNew message during installation has worried users, however, users with an active support contract for their production WebSphere Application Server are entitled for support on the developer machine as long as an active support contract is in place for the production server.\n\n\n * Evaluation software page: https:\/\/www.ibm.com\/developerworks\/downloads\/ws\/wasdevelopers\/index.html [https:\/\/www.ibm.com\/developerworks\/downloads\/ws\/wasdevelopers\/index.html] \n * FAQ: https:\/\/www.ibm.com\/developerworks\/downloads\/ws\/wasdevelopers\/faq-wasdevelopers.html [https:\/\/www.ibm.com\/developerworks\/downloads\/ws\/wasdevelopers\/faq-wasdevelopers.html]\n\n\nRESOLVING THE PROBLEM\nTo change\/upgrade RAD 9.6 WAS4D to WAS ILAN. \n\nAdd the following repository to Installation Manager: https:\/\/www.ibm.com\/software\/repositorymanager\/com.ibm.websphere.ILAN.v90\/ [https:\/\/www.ibm.com\/software\/repositorymanager\/com.ibm.websphere.ILAN.v90\/]"}]},{"id":"DEV_Q023","question":"No trace is logged in Decision Warehouse, and no records in EXECUTION_TRACES table for a certain ruleset\n\n\n\nFor a certain ruleset, no trace is logged in DW, and no records can be found in EXEUTION_TRACES table of DW database.\n\nServer logs do not contain any messages about the execution traces for this ruleset.\n\nThe issue reproduces only for this project. For other projects deployed in RES, traces are being logged in DW. Also, the same project generates execution traces in other environments.\n\nThe following properties have been set:\n\n monitoring.enabled = true\n monitoring.filters = INFO_EXECUTION_DATE=true,INFO_EXECUTION_DURATION=true,INFO_TOTAL_TASKS_EXECUTED=true,INFO_TOTAL_RULES_NOT_FIRED=true,INFO_EXECUTION_EVENTS=true,INFO_TOTAL_TASKS_NOT_EXECUTED=true,INFO_TOTAL_RULES_FIRED=true,INFO_RULESET_PROPERTIES=true\n ruleset.bom.enabled = false (for true value, the problem still occurs)\n ruleset.sequential.trace.enabled = true\n ruleset.trace.enabled = true\n\nHow can I diagnose this issue?","answer":"If an issue arises during DW trace persistence at runtime, the related messages and stack traces are only available programmatically through the following API: ilog.rules.res.session.IlrSessionResponse.getWarnings() \n\nSo it is possible for an error to remain silent if the warnings above are not explicitly logged by the application.","is_impossible":false,"contexts":[{"filename":"swg21433278.txt","text":"Title: IBM Obtaining debug information during Decision Warehouse trace capture - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I obtain debug information when the trace is saved to the Decision Warehouse ? \n\nCAUSE\nTo minimize the impact of Decision Warehouse (DW) monitoring on the processing of ruleset executions, possible failures to save the trace to the database may remain silent (no stack trace in the logs of the application server). \n\nANSWER\nIf an issue arises during DW trace persistence at runtime, the related messages and stack traces are only available programmatically through the following API: ilog.rules.res.session.IlrSessionResponse.getWarnings() \n\nSo it is possible for an error to remain silent if the warnings above are not explicitly logged by the application. \n\nIt is however possible to customize the DW trace and log additional debug information even when the application does not explicitly log the above mentioned warnings. The attached sample uses the java.util.logging API to append to the ilog.rules.support.debugtrace.DebugTraceDAO logger the following: \n\n * at SEVERE level any exception that occurred while attempting to persist the trace to the database \n * at INFO level a summary of the trace with ruleset path information and a list of execution events \n * at FINEST level the list of session response warnings and the full execution trace XML (beware this can be a very large amount of information going to the log, possibly several megabytes)\n\n\nBy default only INFO level and above messages (including SEVERE) are typically visible in the application server logs. So the first two set of information above should be visible, while the FINEST level should require specific configuration of the Java logging to be visible. \n\nInstructions \n\nBundle the attached jrules-debugtrace.jar sample in the Rule Execution Server (RES) application that is performing ruleset executions: * If you are using JRules Hosted Transparent Decision Service (HTDS), in jrules-res-htds-<appserver>.ear\/jrules-res-htds-<appserver>.war\/WEB-INF\/lib \n * If you are using JRules Scenario Service Provider (SSP) in jrules-ssp-<appserver>.ear\/jrules-ssp-server.war\/WEB-INF\/lib \n * If you are executing rules from your application, the sample should be packaged alongside the RES session library that your application already bundles \n\n\n\njrules-debugtrace.jar [\/support\/docview.wss?uid=swg21433278&aid=2]jrules-debugtrace.jar [\/support\/docview.wss?uid=swg21433278&aid=1] \nIf you are interested in learning about the implementation of this DW trace you can use the following eclipse project : \n\njrules-debugtrace-src.zip [\/support\/docview.wss?uid=swg21433278&aid=4]jrules-debugtrace-src.zip [\/support\/docview.wss?uid=swg21433278&aid=3] \nRELATED INFORMATION\n#A simplified Chinese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21665639]\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 Enterprise"}]},{"id":"DEV_Q024","question":"Why is my .NET client not connecting and the QMgr records a DBCS error (AMQ6048)?\n\nI upgraded to WMQ 7.5.0.x client and now my .NET application fails to connect to the QMgr. The error received on the QMgr side was AMQ6048. What's going on?\n AMQ6048: DBCS error\n\n EXPLANATION:\n WebSphere MQ is unable to convert string data due to a DBCS error.\n Conversion is from CCSID 1208 to CCSID 1252.\n ACTION:\n Check the WebSphere MQ Application Programming Reference Appendix and\n the appropriate National Language Support publications to see if the\n CCSIDs are supported by your system.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q025","question":"How to import a certificate in ITCAM for Data Power ?\n\nHow can I import a certificate in ITCAM for Data Power?","answer":"Import the certification file into the agent by doing the following command:\n\nNote : You can use either .cer or .pem. \nMake sure the file is in ASCII not binary. \nWhere the \/usr\/ITM\/JRE is your Java location and <fileName> is your file name.","is_impossible":false,"contexts":[{"filename":"swg21959588.txt","text":"Title: IBM Importing a Certificate for the ITCAM Agent for Data Power (BN Agent) - United States\n\nText:\nCAMDPALL CAMDPSEC Certification Import Importing TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n How to import a Certificate for the TCAM Agent for Data Power (BN Agent) ? \n\nCAUSE\nCertification is missing. \nTrouble shooting Hint - The trace log will show an error that looks like this:\n[2015-05-28T05:58:45.248-0430] - ERROR - BODAPPS57 - pool-1-thread-2 - \ncom.ibm.management.soa.dp.monitor.agent.server.KBNSomaCPUUsage.getCPUUsa \nge - [subnode=DPPROD02; hostname=10.0.49.25;] occured exception \njavax.net.ssl.SSLHandshakeException: Received fatal alert: \nhandshake_failure \n\n\nANSWER\n \n\nImport the certification file into the agent by doing the following command:\n\nNote : You can use either .cer or .pem. \nMake sure the file is in ASCII not binary. \nWhere the \/usr\/ITM\/JRE is your Java location and <fileName> is your file name.\n\nex: \n\/usr\/ITM\/JRE\/aix526\/jre\/bin\/keytool -import -trustcacerts -alias \nligitalsso -keystore \/usr\/ITM\/JRE\/aix526\/jre\/bin\/lib\/security\/cacerts \n-storepass <fileName> -file \/NEWSSL-sscert.cer \n\n\n\nPRODUCT ALIAS\/SYNONYM\n ITCAM Agent for Data Power"}]},{"id":"DEV_Q026","question":"DNS cache is not updating even when DNS server is updated\n\n\n\nDatapower DNS is still showing old IP address even after the DNS server was changed few days ago.\n\nHow can i change DNS cache so it shows the new IP Address?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q027","question":"How to create batches for bulk upload\n\n\n\nI am new in datacap 9.0 .I just started developing with datacap studio and currently I have learned to recognize, capture and export the data into filenet.\n\nNow I want to Create batches of image or pdf files so that I can process images and pdf .\n\n \n\nAs per requirement client is sharing document at one shared location.I need to pickup all the documnets from shared location. For creating batches which tool I should use? how it works?\n\n \n\nCan anyone help how I proceed with this.\n\n \n\nRegards,\n\nChhaya Sahu\n","answer":"Set skipsamebatch for VScan tasks 1. Run Rulerunner Manager. \n 2. On the Rulerunner tab, stop the service. \n 3. On the Rulerunner Login tab, click Connect. \n 4. On the Workflow tab, expand the hierarchy on the right and highlight VScan. \n 5. In the Settings section in the lower right, set skipsamebatch to 1. \n 6. Highlight the line labeled <dbs> above VScan in the thread hierarchy. \n 7. Set skipsamebatch to 1 there also. \n 8. Click Save, then go back to the Rulerunner tab and start the service.","is_impossible":false,"contexts":[{"filename":"swg21618564.txt","text":"Title: IBM Batches left in running state by Rulerunner with IBM Datacap Taskmaster Capture - United States\n\nText:\nrule runner; batches; multiple; running TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When running batch creation tasks, such as VScan, with Rulerunner, multiple batches may be created and\/or left in the running state. \n\nCAUSE\nRulerunner is a very efficient service and will overdrive the Rulerunner Server if too many tasks or threads are assigned.\n\nRESOLVING THE PROBLEM\nTurn off Mixed Queuing \n\n 1. Run Rulerunner Manager. \n 2. On the Rulerunner tab, stop the service. \n 3. On the Rulerunner Login tab, click Connect. \n 4. Select the Workflow tab. \n 5. On the Rulerunner Settings subtab, uncheck Mixed Queuing. \n 6. Click Save, then go back to the Rulerunner tab and start the service.\n\n\nSet skipsamebatch for VScan tasks 1. Run Rulerunner Manager. \n 2. On the Rulerunner tab, stop the service. \n 3. On the Rulerunner Login tab, click Connect. \n 4. On the Workflow tab, expand the hierarchy on the right and highlight VScan. \n 5. In the Settings section in the lower right, set skipsamebatch to 1. \n 6. Highlight the line labeled <dbs> above VScan in the thread hierarchy. \n 7. Set skipsamebatch to 1 there also. \n 8. Click Save, then go back to the Rulerunner tab and start the service.\n\n\nFor Datacap Taskmaster 8.0.1, the procedures are the same but some tabs will have different names. \n\nIf you are still experiencing this issue the problem may be with your DataCap Object (DCO). Correcting DCO issues will resolve batches left in running state. RELATED INFORMATION\n VScan Intermittently Aborts [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21573034 ]"}]},{"id":"DEV_Q028","question":"Help with Security Bulletin: Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WSRR (CVE-2015-4911)\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2015-4911). Where can I find this information? ","answer":"CVEID: 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)","is_impossible":false,"contexts":[{"filename":"swg21975747.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2015-4872 CVE-2015-4911 CVE-2015-4893 CVE-2015-4803) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n WebSphere Application Server is shipped as a component of WebSphere Service Registry and Repository. Information about security vulnerabilities affecting WebSphere Application Server have been published in a security bulletin. \n\nVULNERABILITY DETAILS\nPlease consult the security bulletin WebSphere Application Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21969620] for vulnerability details and information about fixes.\nIn addition to to CVE-2015-4872 WebSphere Service Registry and Repository is vulnerable to the following issues.\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 \n\nPrinciple Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server Network Deployment V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server Network Deployment V8.0 WebSphere Service Registry and Repository V7.5 WebSphere Application Server Network Deployment V7.0 WebSphere Service Registry and Repository V7.0 WebSphere Application Server Network Deployment V7.0 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\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 v2 Guide [http:\/\/www.first.org\/cvss\/v2\/guide] \nOn-line Calculator v2 [http:\/\/nvd.nist.gov\/CVSS-v2-Calculator] \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 02 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."}]},{"id":"DEV_Q029","question":"Recurrent RES StaleConnectionException\n\nHow to prevent rule execution failing because of recurrent StaleConnectionException on ODM 8.8 Rule Execution Server? ","answer":"Configure the WebSphere Application Server data source connection pool so as to eliminate occurrences of StaleConnectionException :\n\n Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout\n Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout","is_impossible":false,"contexts":[{"filename":"swg21496354.txt","text":"Title: IBM JRules or ODM module fails to access database with StaleConnectionException - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n JRules and ODM modules such as Rule Execution Server (RES) and Rule Team Server (RTS) \/ Decision Center (DC) may fail to access their data source with the following type of exception present in the log:\n\ncom.ibm.websphere.ce.cm.StaleConnectionException: Io exception: Connection timed out \n\nSYMPTOM\nThe problem may occur when a JRules or ODM module accesses its data source after a period of database access inactivity. For example: \n\n * The first user accessing a RTS \/ DC server that remained idle overnight experiences a failure upon logging and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred at that time. \n * After a RES server has been processing execution requests normally for some time, an attempt to deploy a ruleset update fails and the server log shows an com.ibm.websphere.ce.cm.StaleConnectionException occurred upon an attempt to invalidate a ruleset or to retrieve its definition.\n\n\nCAUSE\nThe underlying network connection for a data source is no longer valid although the data source itself remains considered active from the WebSphere Application Server data source connection pool management perspective. An attempt by a JRules module to try and access its data base through one such data source connection provided by the Application Server may then fail. \nThe network connection of a data source may become invalid for a number of reasons, one typical example is that a firewall between the Application Server and the Database has a policy to discard network connections that remain idle for some time.\n\n\nENVIRONMENT\nThe exception com.ibm.websphere.ce.cm.StaleConnectionException is specific to WebSphere Application Server environments. But a similar issue can be experienced with Weblogic, see: Rule Execution Server on WebLogic unable to load ruleset after period of inactivity [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21615801]\n\n\n\nRESOLVING THE PROBLEM\nConfigure the WebSphere Application Server data source connection pool [http:\/\/publib.boulder.ibm.com\/infocenter\/wasinfo\/v7r0\/index.jsp?topic=\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/udat_conpoolset.html] so as to eliminate occurrences of StaleConnectionException : \n\n * Set the Minimum connections to 0 to avoid situations where a connection is kept in the pool to meet the minimum requirement, even though it may have been idle for longer than Unused timeout \n * Set the values for Unused timeout and Reap timeout so that the sum does not exceed any network level idle connection timeout\n\n\nThe document Troubleshooting stale connection problems [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21247168#SCETroubleshooting] provides further information. RELATED INFORMATION\n#RES unable to load ruleset after period of inactivity [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21615801]\nTroubleshooting stale connection problems [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21247168#SCETroubleshooting]\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 Enterprise"}]},{"id":"DEV_Q030","question":"For HP-UX how to write verbose gc output to a log file other than the native_stdout?\n\nA 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 HP-UX? ","answer":"Add the following parameters to the generic JVM arguments: \n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xverbosegc:file= \/tmp\/gc_pid$$.vgc","is_impossible":false,"contexts":[{"filename":"swg21636533.txt","text":"Title: IBM Writing Verbose GC To A Specified Log In Solaris and HP-UX - United States\n\nText:\nverbosegc log rotation HP Solaris JVM rotate file TECHNOTE (FAQ)\n\nQUESTION\n How can I write verbose gc output to a log file other than the native_stdout? \n\nCAUSE\nBy default, Solaris and HP-UX do not write verbose GC to a log file. This must be configured.\n\nANSWER\n \n\nWAS 8.5.0.2 (and higher), WAS 8.0.0.6 (and higher), WAS 7.0.0.27 (and higher):\n\nSolaris:\nAdd the following parameters to the generic JVM arguments:\n\n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xloggc:\/tmp\/gc.log\n\nTo enable log file rotation:\n-XX:+UseGCLogFileRotation\n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M\n\n\nnotes:\n-Xloggc:<fileName> \n\n * ex: -Xloggc:\/tmp\/gc.log \n\n-XX:+UseGCLogFileRotati o n * Enabled GC log rotation, requires -Xloggc \n\n-XX:NumberOfGClogFiles= <num_of_files> * Set the number of files to use when rotating logs, must be >= 1. The rotated log files will use the following naming scheme, <filename>.0, <filename>.1, ..., <filename>.n-1. \n\n-XX:GCLogFileSize=<number>K (or M) * The size of the log file at which point the log will be rotated, must be >= 8K. \n\n\nHP: \nAdd the following parameters to the generic JVM arguments: \n-XX:+PrintGCDetails \n-XX:+PrintGCDateStamps \n-XX:+PrintHeapAtGC \n-Xverbosegc:file= \/tmp\/gc_pid$$.vgc \n\nTo enable log file rotation: \n-XX:+UseGCLogFileRotation \n-XX:NumberOfGCLogFiles=10\n-XX:GCLogFileSize=10M \n\nnote : $$ maps to the PID of the java process RELATED INFORMATION\n 6941923 : RFE: Handling large log files produced by lon [http:\/\/bugs.sun.com\/bugdatabase\/view_bug.do?bug_id=6941923]\nEnabling verbose garbage collection (verbosegc) in WebS [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg21114927]\nWhere to set generic JVM arguments in WebSphere Applica [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg21417365]\nVerify Java SDK version shipped with IBM WebSphere Appl [http:\/\/www-01.ibm.com\/support\/docview.wss?rs=180&uid=swg27005002]\nHP-UX Java 6.0.18 - Handling large GC log files [http:\/\/h20000.www2.hp.com\/bc\/docs\/support\/SupportManual\/c03119431\/c03119431.pdf]\nHP-UX Java 7.0.05 - Handling large GC log files [http:\/\/h20000.www2.hp.com\/bc\/docs\/support\/SupportManual\/c03123467\/c03123467.pdf]\nOracle - Java HotSpot VM Options [http:\/\/www.oracle.com\/technetwork\/java\/javase\/tech\/vmoptions-jsp-140102.html]"}]},{"id":"DEV_Q031","question":"Unable to run Test Suites against clustered SSP from Decison Center console\n\nI have a clustered Decision Server where XU and SSP are deployed on cluster members and Rule Execution Server (RES) console is deployed on a standalone server outside of the cluster. IHS and a load balancer is configured on top of the cluster. In Decision Center, the RES server URL is configured with the load balanced IP. Test Suite fails to run from Decision Center console in this configuration.\n\nAfter clicking on Run from Decision Center console, the process starts, but after a few seconds, execution stops with a message: Cannot execute the scenario suite xxx. The operation was aborted by user.\n\nNo errors shown in Decision Center and Decision Server server logs. The only error seen is from the browser and no stack trace is displayed.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q032","question":"IBM Content Navigator v2.0.3 is adding a .dat extension to a CSV file during Download action on a document.\n\nIBM Content Navigator v2.0.3 is adding a .dat extension to a CSV file during Download action on a document. Why is this the case?","answer":"If the mime type of the document as shown in system properties in ICN is not text\/csv, then Navigator cannot recognize the document and a .dat extension will be added upon download.","is_impossible":false,"contexts":[{"filename":"swg21994175.txt","text":"Title: IBM Content Navigator v2.0.3 is adding a .dat extension to a CSV file during Download action on a document. - United States\n\nText:\nicn; csv; download; mimetype; mime type TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Content Navigator v2.0.3 is adding a .dat extension to a CSV document during Download action on the document. \n\nSYMPTOM\nA .dat extension is added to the CSV document upon download.\n\n\nCAUSE\nA CSV document is basically a plain text file. If the mime type of the document as shown in system properties in ICN is not text\/csv, then Navigator cannot recognize the document and a .dat extension will be added upon download. The correct mime type for a CSV file is text\/csv. \n\nRESOLVING THE PROBLEM\nIf there are CSV document already in the content repository with a mime type that is not text\/csv, then in order to view them in a text editor (ex. Notepad), you may use the following workaround:\n- save the document to the local machine with .dat extension\n- right click on the .dat file and click Open With... \n- click 'Choose your default program...'\n- then select Notepad or another text editor of your choice\n- select the checkbox 'Always use the selected program to open this type of file'\n\nThe other alternative is to change the mimetype of the document in the content repository using a custom solution written using the repository's client APIs."}]},{"id":"DEV_Q033","question":"Limitations of sylog-TCP log target using DataPower Gateways\n\nI 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. Why is this? How can I workaround it. ","answer":"Configure a server daemon to listen and capture the DataPower devices events.","is_impossible":false,"contexts":[{"filename":"swg21269136.txt","text":"Title: IBM DataPower off-device logging: a configuration example - United States\n\nText:\ndatapower; 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\u00ae WebSphere\u00ae DataPower\u00ae 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."}]},{"id":"DEV_Q034","question":"Profiler for WebSphere 8\n\n\n\nHi,\n\nWe noticed that a was application server uses 1,4 Go of memory at startup, we would like to understand what java classes are using most part of it.\n\nIs a Java profiler provided by default with WAS 8.0 ? Is there something to activate via the WAS admin console ?\n\n \n\nThanks a lot","answer":"Health Center is a very low overhead monitoring tool. It runs alongside an IBM Java application with a very small impact on the application's performance (less than 1%). Health Center monitors several application areas, using the information to provide recommendations and analysis that help you improve the performance and efficiency of your application.","is_impossible":false,"contexts":[{"filename":"swg21413628.txt","text":"Title: IBM Java Health Center Client - a low overhead monitoring tool - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How can I monitor and diagnose my WebSphere Application Server environment without impacting performance? \n\nANSWER\nAlso see: Extracting data from Java Health Center [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21423006] \n\n * Java\u2122 Health Center: \n Health Center is a very low overhead monitoring tool. It runs alongside an IBM Java application with a very small impact on the application's performance (less than 1%). Health Center monitors several application areas, using the information to provide recommendations and analysis that help you improve the performance and efficiency of your application. Health Center can save the data obtained from monitoring an application and load it again for analysis at a later date. \n \n Starting with IBM Java 5 SR8 or IBM Java 6 SR1, The Health Center client can be installed within the IBM Support Assistant Team Server [http:\/\/www.ibm.com\/software\/support\/isa\/teamserver.html].\n \n The Health Center client has several different views, each reporting data regarding a different aspect of the JVM. The views available are: \n \n \n * Classes: Information about classes being loaded CPU: Processor usage for the application and the system on which it is running Environment: Details of the configuration and system of the monitored application Garbage Collection: Information about the Java heap and pause times I\/O: Information about I\/O activities that take place Locking: Information about contention on inflated locks Method Trace: Information about method use over time Native Memory: Information about the native memory usage Profiling: Provides a sampling profile of Java methods including call paths Threads: Information about the live threads of the monitored JVM WebSphere\u00ae Real Time for Linux: Information about real-time applications \n \n \n \n To Install Health Center: \n Health Center Client is installed as a plug-in for IBM Support Assistant (ISA), therefore, ISA must be installed prior to obtaining the Java Health Center. \n \n * \n * IBM How to Install and Update Problem Determination Tools for IBM Support Assistant Team Server\n * \n * \n * Generic JVM Argument\n * \n * \n * \n * \n (WebSphere) Java Version Generic JVM Argument Java 7.0 and later\n Java 6.0 SR5 and later\n Java 5.0 SR10 and later -Xhealthcenter Java 6.0 SR1 through SR4\n Java 5.0 SR8 and SR9 -agentlib:healthcenter -Xtrace:output=perfmon.out \n \n \n\n * * \n * Connecting to an application by using the Health Center client\n * \n * \n * \n * BEST PRACTICE:\n * \n * \n * Platform Requirements\n * \n * \n * \n * Note\n * \n * inside \n * \n * \n * Start the Health Center client, open the help documentation, then navigate to IBM Support Assistant>Problem Determination Tools>IBM Monitoring and Diagnostic Tools - Health Center>Monitoring a running application>Installing Health Center and install the agent from there. \n * \n \n \n\nRELATED INFORMATION\n IBM Monitoring and Diagnostic Tools for Java - Health C [http:\/\/www.ibm.com\/developerworks\/java\/jdk\/tools\/healthcenter]\nHC 01 Overview of Health Center features [http:\/\/www.youtube.com\/watch?v=5Tcktcl0qxs]\nIBM Monitoring and Diagnostic Tools for Java - Getting [http:\/\/www.ibm.com\/developerworks\/java\/jdk\/tools\/healthcenter\/getting_started.html]\nIBM Support Assistant [http:\/\/www.ibm.com\/software\/support\/isa\/]"}]},{"id":"DEV_Q035","question":"Help with Security Bulletin: API Connect is affected by a Node.js denial of service vulnerability (CVE-2017-14919)\n\nI need to understand details regarding Security Bulletin: API Connect is affected by a Node.js denial of service vulnerability (CVE-2017-14919). Where can I find this information? ","answer":"CVEID:CVE-2017-14919 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-14919]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by an uncaught exception flaw in the zlib module. By making 8 an invalid value for the windowBits parameter, a remote attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134286 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134286]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:H)","is_impossible":false,"contexts":[{"filename":"swg22013168.txt","text":"Title: IBM Security Bulletin: API Connect is affected by a Node.js denial of service vulnerability (CVE-2017-14919) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM API Connect has addressed the following vulnerability. \n\nNode.js is vulnerable to a denial of service, caused by an uncaught exception flaw in the zlib module. By making 8 an invalid value for the windowBits parameter, a remote attacker could exploit this vulnerability to cause the application to crash. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2017-14919 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-14919]\nDESCRIPTION:Node.js is vulnerable to a denial of service, caused by an uncaught exception flaw in the zlib module. By making 8 an invalid value for the windowBits parameter, a remote attacker could exploit this vulnerability to cause the application to crash.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134286 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134286]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:H) \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\nV5.0.0.0 - 5.0.6.4 5.0.6.5 LI79994 Addressed in IBM API Connect V5.0.6.5.\n\nFollow this link and find the \"APIConnect-Portal\" package.\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\nV5.0.7.0 - 5.0.7.2 5.0.8.2 LI79994 Addressed in IBM API Connect V5.0.8.2.\n\nFollow this link and find the \"APIConnect_Management\" and \"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.6.2&platform=All&function=all] IBM API Connect\n\nV5.0.8.0 - 5.0.8.1 5.0.8.2 LI79994 Addressed in IBM API Connect V5.0.8.2.\n\nFollow this link and find the \"APIConnect_Management\" and \"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.6.2&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 08 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."}]},{"id":"DEV_Q036","question":"Port number error starting 9.0 Launcher\n\n\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. Why am I seeing this? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q037","question":"Help with Action required for IIB H.E.V9 and WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q038","question":"ODM 8.7 TeamServer users active authoring rules and they get kicked out - transaction timeout or session timeout?\n\nSome 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-<appserver>.ear\\teamserver.war\\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout.\n\nYou will find the property in the file web.xml defined as below:\n...\n<context-param>\n<description>Modify the timeout value that is associated with transactions (in seconds)<\/description>\n<param-name>ilog.rules.teamserver.transaction.timeout<\/param-name>\n<param-value>600<\/param-value>\n<\/context-param> ","is_impossible":false,"contexts":[{"filename":"swg21451229.txt","text":"Title: IBM Rule Team Server\/Decision Center is timing out while performing certain operations - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to resolve \"Transaction timed out after 601 seconds\" error while performing certain operations in Rule Team Server (RTS)\/Decision Center (DC)? \n\nSYMPTOM\nWhile generating ruleapps in RTS\/DC, the following error is thrown after a few minutes (typically 5 or 10 minutes): \n\nOn WebLogic: \n\nRule Team Server has encountered an unexpected error. The internal error message is: #{SelectionBean.asynchAction}: javax.faces.el.EvaluationException: java.lang.RuntimeException: java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 601 seconds BEA1-5057DF8C316E1C1224CD]'. No further JDBC access is allowed within this transaction. \n\n... \n\n \n\nOn WebSphere: \nTimeoutManage I WTRN0006W: Transaction XXX has timed out after 300 seconds.\nTimeoutManage I WTRN0124I: When the timeout occurred the thread with which the transaction is, or was most recently, associated was Thread[WebContainer : 3,5,main]. The stack trace of this thread when the timeout occurred was: \nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.errorRecovery(IlrEarleyParser.java:1046)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.buildCharts(IlrEarleyParser.java:772)\nilog.rules.brl.parsing.parser.earley.IlrEarleyParser.parse(IlrEarleyParser.java:511)\n...\n\n\nCAUSE\nThe transaction timeout for RTS\/DC is set to 10 minutes by default in the teamserver web module deployment descriptor (WEB-INF\/web.xml), and application servers also have container level transaction timeouts that are configurable. If a transactional operation performed by RTS\/DC takes longer than these timeouts to complete, the transaction is rolled back and the operation is not completed.\n\n\n\nRESOLVING THE PROBLEM\nIf you perform time consuming operations in large repositories, you can increase the timeout value in the web.xml file of the RTS\/DC EAR file (jrules-teamserver-<appserver>.ear\\teamserver.war\\WEB-INF) by changing the value of the property ilog.rules.teamserver.transaction.timeout. \n\n\nYou will find the property in the file web.xml defined as below:\n...\n<context-param>\n<description>Modify the timeout value that is associated with transactions (in seconds)<\/description>\n<param-name>ilog.rules.teamserver.transaction.timeout<\/param-name>\n<param-value>600<\/param-value>\n<\/context-param> \n... \n\nAnother place to look for are application server specific transaction timeout configurations. For example, for WebSphere Application Server, check the \"Maximum transaction timeout\" and increase it as needed as described here [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.doc\/info\/ae\/ae\/tjta_settlog.html].\n\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Operational Decision Manager Platform Independent 7.5 Enterprise Business Integration IBM Operational Decision Manager Platform Independent 8.0.1, 8.0 Enterprise"}]},{"id":"DEV_Q039","question":"How do I upgrade my virtual DataPower Appliance from 5.0 firmware to 6.0+ firmware?\n\nWhen attempting to upgrade my Virtual DataPower Appliance from 5.0.0.8 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.","is_impossible":false,"contexts":[{"filename":"swg21638268.txt","text":"Title: IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States\n\nText:\n 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"}]},{"id":"DEV_Q040","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\n\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 after install & configure the WebSphere Plugin 8.5 version on a Apache 2.4 webserver 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).","is_impossible":false,"contexts":[{"filename":"swg21600618.txt","text":"Title: IBM web server Plugin may need LD_LIBRARY_PATH when used with Apache 2.2 - United States\n\nText:\n 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]"}]},{"id":"DEV_Q041","question":"Has ITCAM for J2EE 7.1.1 IF4 been released?\n\nHas ITCAM for J2EE 7.1.1 IF4 been released? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q042","question":"Why is my Portal 8.5 install saying it cannot detect WAS?\n\nWhen I try to install WebSphere PortaV8.5, I am getting the message\n\nThe required version 8.5.5 or later of WebSphere Application Server has not been detected on this system. Select the WebSphere Application Server Package to install WebSphere Application Server and WebSphere Portal.\n\nThe required IBM WebSphere SDK Java Technology Edition version 7.0 or later is not detected on this system. Select the IBM WebSphere SDK Java Technology Edition package to install it.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q043","question":"Where I can get ITNM 4.2.0.1 GA version download details with Part number?.\n\nHow to download and install IBM Tivoli Network Manager IP Edition Version 4.2 Fix Pack 1 (GA) using the Passport Advantage Web site?. ","answer":"Download all of the parts that you need, both required and optional. The parts are listed in the sections below.\n 2. Unpack each of the parts into a single temporary directory on your system.\n 3. Follow the instructions in the Installing [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/install\/task\/ins_installing.html] section of the IBM Knowledge Center to install the product.","is_impossible":false,"contexts":[{"filename":"swg24042656.txt","text":"Title: IBM Download IBM Tivoli Network Manager IP Edition Version 4.2.0.1 for AIX, Linux - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This document describes how to download and install IBM Tivoli Network Manager IP Edition Version 4.2 Fix Pack 1 using the Passport Advantage Web site. \n\nDOWNLOAD DESCRIPTION\n\n\nIBM\u00ae Tivoli\u00ae Network Manager IP Edition discovers networks, including layer 1 optical networks, and layer 2 and 3 IP networks. Network Manager also discovers mobile networks (including LTE). In addition, Network Manager integrates network topology information with alert data from IBM Tivoli Netcool\/OMNIbus so that operators can visualize and understand the layout of complex networks, and diagnose and solve network problems in real time.\n\nAfter logging into IBM's Passport Advantage Online Web site at https:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm], click Software download & media access, then click Download finder, then select Find by product description and type in Tivoli Network Manager. Expand the Tivoli Software eAssembly, and select the images you wish to download from that list. All Tivoli Network Manager IP Edition download images are described below.\n\nMore information\nThe IBM Tivoli Network Manager IP Edition V4.2 library of publications are available from IBM Knowledge Center at https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/common\/welcome.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/itnm\/ip\/wip\/common\/welcome.html]\n\nDownloading and installing the product\n\n 1. Download all of the parts that you need, both required and optional. The parts are listed in the sections below.\n 2. Unpack each of the parts into a single temporary directory on your system.\n 3. Follow the instructions in the Installing [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/install\/task\/ins_installing.html] section of the IBM Knowledge Center to install the product. \n\n \n\n\n\nSupported operating systems\n\nOn IBM\u00ae PowerPC-based systems, the following versions are supported:\n\n * AIX\u00ae 6.1 iSeries and pSeries\n * AIX 7.1 iSeries and pSeries\n\nOn Intel and Advanced Micro Devices (AMD) x86 processors, the following versions are supported:\n\n * Red Hat Enterprise Linux 6 (x86-64)\n * Red Hat Enterprise Linux 7 (x86-64)\n * SuSE Linux Enterprise Server (SLES) 11.0 (x86-64) SP2 and SP3\n\nDownloadable parts\n\nThere are downloadable parts for each supported platform upon which IBM Tivoli Network Manager IP Edition can be installed. Refer to the tables below for details about what each part contains. At a minimum, you must download the required parts.\n\nRequired parts\n\nTo install IBM Tivoli Network Manager IP Edition V4.2.0.1 Multilingual, you need to download the following parts: \n\nPart # Description CNE9VEN IBM Tivoli Network Manager IP Edition 4.2.0.1 for Linux Includes the base product including the core components, the GUI components, and the topology database scripts.\n\n(English, Brazilian Portuguese, French, German, Italian, Spanish, Japanese, Korean, Hungarian, Polish, Russian, Simplified Chinese, and Traditional Chinese)\n\nCNE9WEN IBM Tivoli Network Manager IP Edition 4.2.0.1 for AIX Includes the base product including the core components, the GUI components, and the topology database scripts.\n\n(English, Brazilian Portuguese, French, German, Italian, Spanish, Japanese, Korean, Hungarian, Polish, Russian, Simplified Chinese, and Traditional Chinese)\n\nCNE9UML IBM Tivoli Network Manager IP Edition V4.2.0.1 Quick Start Guide. \nDB2 is the default topology database in Network Manager 4.2. Network Manager 4.2 also supports Oracle Database version 12c Enterprise Edition with Partitioning option.\n\n\n\nPart # Description CRYY2ML IBM DB2 10.5 Enterprise Server Edition for Tivoli Netcool\/OMNIbus, Network Manager, and Netcool Configuration Manager \n\nOptional parts \n\nThese optional parts are included in this eAssembly.\n\nPart # Description CRYY6ML IBM Tivoli Monitoring V6.3.0.2 and Monitoring Agent for Network Manager IP Edition V4.2 CN933EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for Linux CN934EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for AIX CN935EN IBM Tivoli Monitoring Agent for Network Manager V4.2 for Windows CJ0R8ML Jazz for Service Management v1.1.3 for Tivoli Netcool\/OMNIbus, Network Manager, Netcool Configuration Manager, and Network Performance Insight CJ0S1ML Websphere Application Server 8.5.5.9 and SDK Java 7 for Tivoli Netcool\/OMNIbus, Network Manager, and Netcool Configuration Manager \nPREREQUISITES\nFor software and hardware prerequisites, see the Planning for installation section in the Network Manager 4.2 documentation on the IBM Knowledge Center.\n\nURL LANGUAGE SIZE(Bytes) Planning for installation [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHRK_4.2.0\/install\/task\/pln_planninginst.html] English 1 \nINSTALLATION INSTRUCTIONS\nTo install the product, follow the instructions in the IBM Tivoli Network Manager IP Edition V4.2 Quick Start Guide. The Quick Start Guide is in multiple languages.\n\nURL LANGUAGE SIZE(Bytes) Quick Start Guide [https:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27048605] English 1 \nDOWNLOAD PACKAGE\nDownload IBM Tivoli Network Manager IP Edition V4.2.0.1 from the Passport Advantage Online Web site.\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Download Network Manager 4.2.0.1 for AIX and Linux 22 Sep 2016 English 1 HTTPS [https:\/\/www-01.ibm.com\/software\/how-to-buy\/passportadvantage\/pao_customers.htm] \nTECHNICAL SUPPORT\n \n\n You can access IBM Tivoli Product support at https:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliNetworkManagerIPEdition.html [https:\/\/www.ibm.com\/software\/sysmgmt\/products\/support\/IBMTivoliNetworkManagerIPEdition.html]\n\n You can access Passport Advantage Online support at https:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare.html [https:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare.html]"}]},{"id":"DEV_Q044","question":"Help with Security Bulletin: IBM WebSphere MQ and IBM MQ Managed File Transfer is affected by an undefined behavior because of insecure file permission vulnerability (CVE-2017-1699)\n\nI need to understand details regarding Security Bulletin: IBM WebSphere MQ and IBM MQ Managed File Transfer is affected by an undefined behavior because of insecure file permission vulnerability (CVE-2017-1699). Where can I find this information?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q045","question":"How can I get a new authorization code for my new computer?\n\nI purchased a new computer and would like to install spss 18 on it. I have the gradpack. However, the authorization code failed when I attempted to install the software on my new machine. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q046","question":"Cannot delete folder in Box collab folder\n\n\n\nIn an ICM 5.3.0 environment integrated with Box, after setting up Box Collaboration, case worker can create Box collaboration folder, and can create folders and files under Box collaboration folder, however, they cannot delete the their folders and files.\n\nCase worker's default permission is 'Viewer Uploader' and case worker cannot add permission more than editor (Editor\/Co-owner\/Owner). So case worker can add new folder\/file and edit file, but cannot delete folder\/file.\n\nThe question is, why cannot case worker have permission more than editor?","answer":"There is no support for deleting documents and\/or folders from a Box Collaboration folder created via Case Manager at this time.","is_impossible":false,"contexts":[{"filename":"swg22002589.txt","text":"Title: IBM Deleting Box folders and content from IBM Case Manager 5.3.0 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n After configuring Box as a repository for Case Manager, Case Client users would like to delete documents and\/or folders created under the Box collaboration folder. There does not appear to be any mechanism to perform this deletion. \n\nANSWER\nThere is no support for deleting documents and\/or folders from a Box Collaboration folder created via Case Manager at this time. Case workers who created the Box collaboration folder will have Viewer\/Uploader permission on the Box Collaboration folder, and therefore, will not be able to delete content within a Box collaboration folder as this may result in missing data in the associated cases. Users who are invited to collaborate on the Box collaboration folder have the same restriction. \n\nHere is a link to Box collaboration permissions to clarify what permissions a Viewer\/Uploader has\nhttps:\/\/community.box.com\/t5\/How-To-Guides-for-Sharing\/What-Are-The-Different-Access-Levels-For-Collaborators\/ta-p\/144 [https:\/\/community.box.com\/t5\/How-To-Guides-for-Sharing\/What-Are-The-Different-Access-Levels-For-Collaborators\/ta-p\/144]"}]},{"id":"DEV_Q047","question":"I need to move my perpetual license of SPSS v24 to my new machine.\n\nI have my authorization code first given to me, but since we did not renew our support contract we can't seem to download the software. I was originally told that I could download the trial version and it would have the authorization wizard where I could input the code and move forward. But the only downloadable version is subscription version with no authorization wizard. How do I move forward? ","answer":"If the Software Subscription and Maintenance has expired you will not be able to download the software from Passport Advantage Online.\nIn this case, you would need to renew your software Subscription and Maintenance.\n\nYou can order the Media CD copy of the software your company purchased. The software version is the one up to the time your subscription has expired.","is_impossible":false,"contexts":[{"filename":"swg22013294.txt","text":"Title: IBM Access and download SPSS software - United States\n\nText:\nentitlements; software; download TECHNOTE (FAQ)\n\nQUESTION\n Can I download the software without active Subscription and Maintenance? \n\nCAUSE\nexpired entitlements\n\nANSWER\n \n\nOfficial statement by IBM eCustomer Care Team (Passport Advantage Online help desk):\n\nWe would like to inform you that you can only access and download software that has active Subscription and Maintenance from Passport Advantage Online.\nIf the Software Subscription and Maintenance has expired you will not be able to download the software from Passport Advantage Online.\nIn this case, you would need to renew your software Subscription and Maintenance.\n\nYou can order the Media CD copy of the software your company purchased. The software version is the one up to the time your subscription has expired.\nThe sales department will be able to advise you if the Media CD is available.\nYou can find your local contact for the IBM Sales Department at: https:\/\/www.ibm.com\/planetwide\/ [https:\/\/www.ibm.com\/planetwide\/]"}]},{"id":"DEV_Q048","question":"Need to understand what exact counters are needed for the ITM IIS agent?\n\nNeed to understand what exact counters are needed for the ITM IIS agent to collect website details and web site status. unable to find what \ncounters are required in the IIS doc. ","answer":"To resolve this problem, install IIS 6.0 management compatibility pack on your Windows Server.","is_impossible":false,"contexts":[{"filename":"swg21685441.txt","text":"Title: IBM No data visible in Web Sites workspace for ITCAM for IIS (Q7) Agent - United States\n\nText:\n5724C0FWATR; 5742C0FWA; 5724B97ISTR; 5724B97IS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After successfully installing and configuring the ITCAM agent for Microsoft IIS (q7), no data appears for IIS websites and no alerts occur when the web server is stopped. Similar issue may also occur for ITCAM agent for Microsoft .NET Framework (qf). \n\nSYMPTOM\nITCAM agent for IIS agent \n\n Agent shows no data for Web Sites running on the IIS Server in TEP.\n\nITCAM agent for .NET (qf)\nFollowing symptoms may occur:\n1) The Windows Application event log shows following event, and some data :\nFaulting application name: kqfclient.exe, version: 0.0.0.0, time stamp: 0x52ce696f \nFaulting module name: kqfclient.exe, version: 0.0.0.0, time stamp: 0x52ce696f \n...\nFaulting application path: C:\\PROGRA~2\\ibm\\ITM\\TMAITM~1\\kqfclient.exe \n\n2) No data is displayed in some workspaces, such as Web Sites view of Web Server workspace.\n\n\nCAUSE\nThe required IIS role services and the IIS v6.0 Management Compatibility pack are not installed. \n\n\nRESOLVING THE PROBLEM\nTo resolve this problem, install IIS 6.0 management compatibility pack on your Windows Server. \n\n\nNote the following:\n1) The symptom, cause and the remedial action mentioned in this technote applies to both .NET Framework agent and the ITCAM for IIS agent.\n2) Even if you have IIS 7.0 - you should install the IIS 6.0 Management Compatibility Pack. This is not a part of IIS 6.0, but instead is a compatibility pack that is needed for higher IIS versions (IIS 7, 7.5, 8, 8.5). This option is found under the role services for IIS Web server.\n\nDetailed instructions are as follows:\n\n(i) Ensure the following IIS Role Services are installed:\n-------------------------------------------------------------------------------\nIIS 6 Management Compatibility\nIIS 6 Metabase Compatibility\nIIS 6 WMI Compatibility\nIIS 6 Scripting Tools\nIIS 6 Management Console\n\n[\/support\/docview.wss?uid=swg21685441&aid=1] [\/support\/docview.wss?uid=swg21685441&aid=1]\n\n(ii) Ensure the IIS v6.0 Management Compatibility pack is installed:\n---------------------------------------------------------------------------------------------------\n1. On the Master or Replica host, open the Server Manager and select the Roles option. \nClick the Add Roles button.\nThe first page of the Add Roles Wizard appears.\n\n2. Click Next. The Select Server Roles window appears.\n\n3. Select the Web Server (IIS) check box, and then click Next.\nA pop-up message appears, asking you whether to add features required for Web Server (IIS).\n\n4. Click Add Required Features.\nThe Select Server Roles window appears.\n\n5. Click Next.\nThe Web Server (IIS) window appears.\n\n6. Click Next.\nThe Select Role Service window appears.\n\n7. On the Role Services list, select the IIS 6 Management Capability check box.\n\n8. Click Next, and follow the Wizard instructions until the completion of the installation.\n\nRestart the agent."}]},{"id":"DEV_Q049","question":"Why am I getting a DSRA7019W message when I try to use the Oracle 10g driver in WAS 8.5.5.x?\n\nI am getting the following message when I configure my WAS 8.5.5.x datasource to use the Oracle 10g driver:\nDSRA7019W: Oracle10gDataStoreHelper or a subclass of it must be used when configuring WebSphere DataSources to run using Oracle 10g jdbc driver.\nHow can I resolve this issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q050","question":"Why AUTOMATIC value for NUM_IOSERVERS is changed after applying 10.5FP7?\n\nWhy AUTOMATIC value for NUM_IOSERVERS is changed after applying 10.5FP7?","answer":"Yes, it is expected. Due to IT09990, we changed the fomula for calculating the number of prefetchers to start at database activation time.","is_impossible":false,"contexts":[{"filename":"swg21991890.txt","text":"Title: IBM NUM_IOSERVERS=AUTOMATIC behaviour is changed from 10.5FP7 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n After updating to 10.5FP7 from an older fixpack level, I noticed that AUTOMATIC value for NUM_IOSERVERS is changed even though any settings are not changed. Is it expected bahavior? \n\nANSWER\nYes, it is expected. Due to IT09990, we changed the fomula for calculating the number of prefetchers to start at database activation time.\nUntil 10.5FP6, we use following fomula:\nnumber of prefetchers =\nmax( max( max over all table spaces( parallelism setting ),\nnumber of cores * number of SMT threads ), 16 )\n\nStarting from 10.5FP7, we use following fomula:\nnumber of prefetchers =\nmax( max( max over all table spaces( parallelism setting ),\nnumber of cores * number of SMT threads ), 12 )\n\nSo you can see the following output in 10.5FP6 and FP7:\n\nFP6:\n$ db2 get db cfg | grep NUM_IOSERVERS\nNumber of I\/O servers (NUM_IOSERVERS) = AUTOMATIC(16)\n\nFP7\n$ db2 get db cfg | grep NUM_IOSERVERS\nNumber of I\/O servers (NUM_IOSERVERS) = AUTOMATIC(12)\n\nRELATED INFORMATION\n num_ioservers - Number of I\/O servers configuration par [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.admin.config.doc\/doc\/r0000333.html]"}]},{"id":"DEV_Q051","question":"We got a NullPointerException when bootstrapping the object store or accessing Site Preferences\/Access Role on WorkplaceXT\n\n\n\nAfter logging into FileNet Workplace XT, a java.lang.NullPointerException error is logged when bootstrapping the object store or when accessing Site Preferences\/Access Role.\n\nHere's the error stack,\n\nError Stack Trace extracted from the J2EE Application Server error log:\n\njava.lang.NullPointerException\n\nat org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:421)\n\nat com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRoleMembers(PrefAccessRolesInfoPage.java:254)\n\nat com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRole(PrefAccessRolesInfoPage.java:220)\n\nat com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.renderAdminRole(PrefBootstrapInfoPage.java:131)\n\nat com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.render(PrefBootstrapInfoPage.java:303)","answer":"In FEM, change the User Display Name Attribute or Group Display Name Attribute to a valid LDAP entry such as cn, displayName or uid and restart the FileNet Content Engine and Workplace XT instances.","is_impossible":false,"contexts":[{"filename":"swg21495799.txt","text":"Title: IBM FileNet Workplace XT NullPointerException when bootstrapping the object store or accessing Site Preferences\/Access Role - United States\n\nText:\njava.lang.NullPointerException; workplacext bootstrap; user display name TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After logging into FileNet Workplace XT, a java.lang.NullPointerException error is logged when bootstrapping the object store or when accessing Site Preferences\/Access Role. \n\nSYMPTOM\nError Stack Trace extracted from the J2EE Application Server error log: \n\njava.lang.NullPointerException \n\n at org.apache.jasper.runtime.JspWriterImpl.write(JspWriterImpl.java:421) \n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRoleMembers(PrefAccessRolesInfoPage.java:254) \n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefAccessRolesInfoPage.renderRole(PrefAccessRolesInfoPage.java:220) \n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.renderAdminRole(PrefBootstrapInfoPage.java:131) \n\n at com.filenet.wcm.apps.server.ui.info.prefs.PrefBootstrapInfoPage.render(PrefBootstrapInfoPage.java:303)\n\n\nCAUSE\nThis behavior may occur if an invalid entry has been specified in the User Display Name Attribute or Group Display Name Attribute setting in the Directory Services Configuration in FileNet Enterprise Manager (FEM). \n\nWorkplace XT attempts to resolve the user names and groups defined within the Access Roles based on the Directory Service configuration defined in FEM. If the user name query resolves to null or if there is an invalid entry a NullPointerException error may occur. \n\n\nRESOLVING THE PROBLEM\n In FEM, change the User Display Name Attribute or Group Display Name Attribute to a valid LDAP entry such as cn, displayName or uid and restart the FileNet Content Engine and Workplace XT instances."}]},{"id":"DEV_Q052","question":"Why do I still get \"certificate expired\" error after adding new certificate?\n\n\n\nThe remote SSL vendor has provided us a new certificate to replace an expiring one. We have added the new certificate to the appropriate Datapower validation credential, however, connections are still failing with \"certificate expired\":\n\nmpgw(Inbound_MPG): tid(51005)[request][10.20xx.xx] gtid(51345): certificate validation failed for '\/C=US\/O=People Services\/OU=IT\/CN=test.site.com' against 'My_ValCred': certificate has expired","answer":"If the replacement certificate has the same file name of the expired certificate, you MUST disable\/enable the certificate object in order to clear all cached references to the expired certificate.","is_impossible":false,"contexts":[{"filename":"swg21500046.txt","text":"Title: IBM Replacement of an expiring certificate on the IBM WebSphere DataPower SOA Appliance - United States\n\nText:\nSSL HTTPS TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n What is the procedure for replacing an expiring certificate that is in use on the DataPower appliance with a newly obtained certificate? \n\nCAUSE\nOnce you have obtained a new certificate from your certificate authority and are ready to replace the expiring one currently in use by your DataPower configuration with this new certificate, there is no single prescribed manner in which to perform the replacement operation. The following information presents some options for formulating an approach that best fits your environment.\n\nRESOLVING THE PROBLEM\nFirst, know your certificate material. It's not uncommon for newer certificates to be chained, so it is not a one for one replacement; the existing certificate on the DataPower appliance may need to be replaced by more than one certificate. Therefore, it is important to ensure you have the full certificate chain, as appropriate (i.e, the personal, intermediate and root certificates). Certificate authorities may send two certificates in the chain and expect the third one to be downloaded from their website. \n\n\nHere's a screenshot of a sample chain. Notice that you can check the 'Certification Path' tab if there are any remaining certificates in the chain. Also note the chain of \"Issued To\" and \"Issued By\" identities.\nExampleCertificateChain.jpg [\/support\/docview.wss?uid=swg21500046&aid=2]ExampleCertificateChain.jpg [\/support\/docview.wss?uid=swg21500046&aid=1]\n\n\nAs for the certificate configuration on DataPower, the appliance will reference the actual key and certificate files stored in the cert: directory by file name. Navigation in the WebGUI to the SSL Proxy Profile -> Crypto Profile -> Crypto Key and Certificate objects will show the current files referenced by the configuration.\n\n[\/support\/docview.wss?uid=swg21500046&aid=3] [\/support\/docview.wss?uid=swg21500046&aid=3]\n\n\nFor example, your DataPower configuration may currently reference the existing files cert:\/\/\/current-key.pem and cert:\/\/\/current-cert.pem.\n\n[\/support\/docview.wss?uid=swg21500046&aid=4] [\/support\/docview.wss?uid=swg21500046&aid=4]\n\nAs long as the replacement file(s) are NOT named the same as these files (i.e. the new ones are named cert:\/\/\/new-key.pemand cert:\/\/\/new-cert.pem for example), it is safe to load the new file(s) into the cert: directory at any time ahead of the replacement operation. Your existing configuration will not use the new files, so long as the Crypto Key and Certificate Objects still refer to the files associated with the expiring certificate (i.e. cert:\/\/\/current-key.pem and cert:\/\/\/current-cert.pem). \n\n[\/support\/docview.wss?uid=swg21500046&aid=5] [\/support\/docview.wss?uid=swg21500046&aid=5]\n\nHaving both expiring and replacement files in the cert: directory at once allows for the capability to modify the configuration to point to the new files or revert it back to the expiring files relatively easily or to configure a new SSL Proxy Profile object that references the new files. The new SSL Proxy Profile could be used to test independently of the currently running configuration using a new test service such as an XML Firewall. \n\nYou can navigate directly to the key and certificate objects using these paths: \nObjects \u2192 Crypto Configuration \u2192 Crypto Certificate.\nObjects \u2192 Crypto Configuration \u2192 Crypto Key \n\nAnother view is from Control Panel -> Keys and Certificate Management.\n\n[\/support\/docview.wss?uid=swg21500046&aid=6] [\/support\/docview.wss?uid=swg21500046&aid=6]\n\nEither way, note how the configuration ultimately references the files in the cert: directory and plan ahead for how you prefer to reference the new files. \n\nThey may be swapped out within the existing Crypto Configuration objects (i.e. update the objects to reference the new file(s) or to revert to the expiring ones as needed). \n\nAlternatively, a new separate set of Crypto Configuration objects that reference the new files may be created and replacement performed at the Crypto object level by updating the configuration to reference the new replacement Crypto Configuration objects.\n\nImportant Note: If the replacement certificate has the same file name of the expired certificate, you MUST disable\/enable the certificate object in order to clear all cached references to the expired certificate.\n\nFor more information on certificates, refer to the product documentation specific to your firmware and appliance type. Navigate to the Administrator's Guide, under \"Managing the Appliance\" - \"Working with keys and certificates\" from the WebSphere DataPower Product Documentation Portal [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21377654]."}]},{"id":"DEV_Q053","question":"After uninstalling Portal 8.0 only from my WAS environment my subsequent attempts to install Portal 8.0 into that same existing WAS fails.\n\n\n\nI installed Portal 8.0.0.1 CF12 with an existing WAS 8.0.0.8 application server and everything was successful. I want to script my install so I uninstalled Portal 8.0.0.1 only and was left with an existing WAS 8.0.0.8...as before. However, when I attempt to reinstall Portal 8.0.0.1 into that same existing WAS 8.0.0.8 to test my scripting I get the following error immediately:\n\nERROR: The required version 8.0.0.5 or later of WebSphere Application Server has not been detected on this system. Select the WebSphere Application Server Package to install WebSphere Application Server and WebSphere Portal.\n\nIIM shows WAS as installed, so I am not sure what is causing this behavior when it installed fine just a few hours ago.\n","answer":"Navigate to the AppServer folder and remove the following files (they are regenerated with a reinstall of Portal):\n\nlib\/ext\/commons-codec-1.3.jar\nlib\/ext\/commons-httpclient-3.0.1.jar\nlib\/ext\/openid4java-full-0.9.5.jar\nlib\/ext\/wp.auth.base.sua_RedirectServletFilter.jar\nlib\/ext\/wp.auth.base.sua_loginmodule.jar\nlib\/ext\/wp.auth.tai.jar\nlib\/wp.user.connections.jar\nlib\/wp.wire.jar\nplugins\/com.ibm.patch.was.plugin.jar\nplugins\/com.ibm.wp.was.plugin.jar\nplugins\/wp.ext.jar\nproperties\/jndi.properties","is_impossible":false,"contexts":[{"filename":"swg21635341.txt","text":"Title: IBM Portal 8 installation unable to detect the WebSphere Application Server - United States\n\nText:\nportal reinstall fails; install into existing WAS fails TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nThe IBM Installation Manager is unable to detect that a WebSphere Application Server exists when attempting to install Portal.\n\nSYMPTOM\nThis issue seems to manifest when an existing Portal has been uninstalled and WebSphere Application Server is not uninstalled. When Portal install is attempted again, but this time to install into the existing WebSphere Application Server then Installation Manager will throw an excecption that notes that it is unable to detect WebSphere Application Server on the system \n\nWe have also seen an issue where the install fails indicating the version of WAS detected is insufficient and we see an exception like this in IIM logs:\n\n\n49 INFO 00:03.14 This Cumulative Fix requires that IBM\nWebSphere Portal Server version 8.0.0.0 be previously installed. You\nmust first install the base release and then update it with the\nCumulative Fix. You cannot install them at the same time.\n50 ERROR 00:03.15 The required version 8.0.0.5 or later of\nWebSphere Application Server has not been detected on this system.\nSelect the WebSphere Application Server Package to install WebSphere\nApplication Server and WebSphere Portal.\n51 INFO 00:03.21 Stopping Installation Manager.\n52 INFO 00:03.28 No log properties file found in:\n\/home\/wasadmin\/var\/ibm\/InstallationManager\/logs\n\n\n\nCAUSE\nThe issue is caused by Portal files that are not correctly removed from the AppServer folder structure when Portal is uninstalled.\n\n\nENVIRONMENT\nPortal 8.0.0.x and WAS 8.0.0.x\n\n\n\n\nRESOLVING THE PROBLEM\nNavigate to the AppServer folder and remove the following files (they are regenerated with a reinstall of Portal):\n\nlib\/ext\/commons-codec-1.3.jar\nlib\/ext\/commons-httpclient-3.0.1.jar\nlib\/ext\/openid4java-full-0.9.5.jar\nlib\/ext\/wp.auth.base.sua_RedirectServletFilter.jar\nlib\/ext\/wp.auth.base.sua_loginmodule.jar\nlib\/ext\/wp.auth.tai.jar\nlib\/wp.user.connections.jar\nlib\/wp.wire.jar\nplugins\/com.ibm.patch.was.plugin.jar\nplugins\/com.ibm.wp.was.plugin.jar\nplugins\/wp.ext.jar\nproperties\/jndi.properties\n\nSelect the Recheck Status button. It should now say \"All prerequisites are met.\""}]},{"id":"DEV_Q054","question":"What are the mustgather for RDz integrated debugger issues or z\/OS Debugger?\n\nWhat logs could be collected when experiencing a problem with the integrated debugger in Rational Developer for System Z ?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q055","question":"Table \"\".\"\" could not be found\n\n\n\nWhen doing a table mapping with DB2 as source, selecting a table which contains special characters on column comments like:\n\nCOMMENT ON COLUMN .. IS 'Test comment \u20181\u2019 complete';\n\nMapping fails with following error message: Table . could not be found in the database. ","answer":"Reinsert data with codepage conversion enforced by setting the operation system codepage matching to the codepage of data to be inserted","is_impossible":false,"contexts":[{"filename":"swg21412846.txt","text":"Title: IBM Wrong codepoints for non-ASCII characters inserted in UTF-8 database using CLP - United States\n\nText:\nCLP; insert; codepage; unicode; wrong codepoints; CharConversionException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n During insert from the CLP there is no codepage conversion if operating system codepage and database codepage are both UTF-8. In this case data to be inserted should also be in UTF-8 encoding.\n\nIf data has a different encoding then the database codepage (this can be verified using any hex editor), then the operating system codepage should be changed to match the data's encoding in order to enforce the data conversion to the database codepage. \n\nSYMPTOM\nError executing Select SQL statement. Caught by java.io.CharConversionException. ERRORCODE=-4220 \n\n Caused by: \njava.nio.charset.MalformedInputException: Input length = 4759 \nat com.ibm.db2.jcc.b.u.a(u.java:19) \nat com.ibm.db2.jcc.b.bc.a(bc.java:1762) \n\n\nCAUSE\nDuring an insert of data using CLP characters, they do not go through codepage conversion.\nIf operating system and database codepage both are UTF-8, but the data to be inserted is not Unicode, then data in the database might have incorrect codepoints (not-Unicode) and the above error will be a result during data retrieval. \n\nTo verify the encoding for data to be inserted you can use any editor that shows hex representation of characters. Please verify the codepoints for non-ASCII characters that you try to insert. If you see only 1 byte per non-ASCII characters then you need to force the database conversion during insert from CLP to UTF-8 database. \n\nTo force codepage conversion during insert from the CLP make sure that the operating system codepage is non-Unicode and matching to the codepage of data when you insert data to Unicode database from non-Unicode data source. \n\nProblem Details\nAn example problem scenario is as follows:\n\n\n 1. Create a database of type UTF-8:\n \n CREATE DATABASE <db> USING CODESET utf-8 TERRITORY US \n \n \n 2. Create a table that holds character data:\n \n CREATE TABLE test (col char(20)) \n \n \n 3. Check operating system locale:\n \n locale LANG=en_US.UTF-8 \n LC_CTYPE=\"en_US.UTF-8\" \n \n \n 4. Insert the non-ASCII characters '\u00c3' , '\u00b3', '\u00a9' which have codepoint 0x'C3', 0x'B3',0x'A9' in codepage 819 into the table:\n \n INSERT INTO test VALUES ('\u00c3')\n INSERT INTO test VALUES ('\u00b3')\n INSERT INTO test VALUES ('\u00a9') \n \n \n 5. By running the following statement, you can see that all INSERT statements caused only one byte to be inserted into the table:\n \n SELECT col, HEX(col) FROM test\n \n \n \u00c3 C3\n \u00b3 B3\n \u00a9 A9\n \n However, the UTF-8 representation of those characters are: 0x'C383' for '\u00c3', 0x'C2B3' for '\u00b3', and 0x'C2A9' for '\u00a9'.\n So these three rows in the table contain invalid characters in UTF-8. \n \n \n 6. When selecting from a column using the JDBC application, the following error will occur. This is expected because the table contains invalid UTF-8 data:\n Error executing Select SQL statement. Caught by java.io.CharConversionException. ERRORCODE=-4220\n Caused by:\n java.nio.charset.MalformedInputException: Input length = 4759\n at com.ibm.db2.jcc.b.u.a(u.java:19)\n at com.ibm.db2.jcc.b.bc.a(bc.java:1762) \n \n \n \n 7. Delete all rows with incorrect Unicode codepoints from the test table:\n DELETE * from test \n \n \n 8. Change the locale to one that matching codepage of data to be inserted:\n export locale=en_us. One of the way to determine the codepage for your data can be found here: http:\/\/www.codeproject.com\/Articles\/17201\/Detect-Encoding-for-In-and-Outgoing-Text [http:\/\/www.codeproject.com\/Articles\/17201\/Detect-Encoding-for-In-and-Outgoing-Text]. If you prepare data yourself using some editor please check the documentation for your editor to find out how to set up the codepage for data being prepared by the editor. \n \n \n 9. Insert data to the table:\n INSERT INTO test VALUES ('\u00c3')\n INSERT INTO test VALUES ('\u00b3')\n INSERT INTO test VALUES ('\u00a9') \n \n \n 10. Verify that inserted data were converted to UTF-8 during insert:\n SELECT col, HEX(col) FROM test\n \n \n \u00c3 C383\n \u00b3 C2B3\n \u00a9 C2A9 \n \n \n 11. Run your java application selecting Unicode data. No exception should be reported. \n\n\n\n\nENVIRONMENT\nUNIX, Linux, Unicode database\n\n\n\nDIAGNOSING THE PROBLEM\nVerify that non-ASCII data have a proper Unicode codepoints in Unicode database\n\n\n\nRESOLVING THE PROBLEM\nReinsert data with codepage conversion enforced by setting the operation system codepage matching to the codepage of data to be inserted\n\nRELATED INFORMATION\n Export data: [http:\/\/www.ibm.com\/developerworks\/db2\/library\/techarticle\/0210lau\/0210lau.html]"}]},{"id":"DEV_Q056","question":"When I try to deploy an application on a cluster, why is it throwing an ADMA8019E error in the admin console?\n\nThe application is being deployed at the cluster scope, but my namespace bindings are defined at the cell scope. The error I'm seeing in the admin console is:\n\nADMA8019E: The resources that are assigned to the application are beyond the deployment target scope. Resources are within the deployment target scope if they are defined at the cell, node, server, or application level when the deployment target is a server, or at the cell, cluster, or application level when the deployment target is a cluster. Assign resources that are within the deployment target scope of the application or confirm that these resources assignments are correct as specified.\n\nI don't see any actual issue with how the JNDI lookup is occurring once the application is deployed. Should I be concerned about this error?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q057","question":"Help with Action required for IIB H.E.V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux (CVE-2017-12150, CVE-2017-12151, CVE-2017-12163)\n\n\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. This is related to CVE-ID:\nCVE-2017-12150\nCVE-2017-12151\nCVE-2017-12163\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q058","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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\nThis is related to CVEID:\nCVE-2017-14739\nCVE-2017-14741\nCVE-2017-14989\nCVE-2017-15015\nCVE-2017-15016\nCVE-2017-15017\nCVE-2017-15032\nCVE-2017-15033\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q059","question":"Help with vulnerability have been identified in WebSphere Application Server shipped with WSRR\n\nI need to understand details regarding Multiple vulnerabilities have been identified in WebSphere Application Server shipped with WebSphere Service Registry and Repository (CVE-2017-1583). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q060","question":"DFHAP1203I and DFHSR0601 with 0C1 in EQA10OSM after upgrading to CICS TS 5.2\n\nWhy is my CICS region failing during startup with message DFHAP1203I followed by DFHSR0601 after I upgraded to CICS Transaction Server for z\/OS (CICS TS) V5.2? A system dump shows an abend 0C1 occurring in the Debug Tool for z\/OS module EQA10OSM. \nI receive the following messages:\nDFHAP1203I Language Environment is being initialized. \nDFHSR0601 Program interrupt occurred with system task III in control. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q061","question":"Why does my JVMSERVER remain in a \"BEING DISABLED\" state?\n\nWhen I try to disable a JVMSERVER it becomes hung and remains in a \"BEING DISABLED\" state. This also occurs when I shut down the CICS region. The CICS region ultimately has to be cancelled. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q062","question":"Where can I find more details about WMB Fix Pack 8.0.0.5?\n\nWhere can find more information about WebSphere Message Broker (WMB) Fix Pack 8.0.0.5?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q063","question":"Hide a page in dotedit step\n\n 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 delete 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.","is_impossible":false,"contexts":[{"filename":"swg21509510.txt","text":"Title: IBM How to delete a document hierarchy node in IBM Datacap Taskmaster Capture - United States\n\nText:\ndco 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 *"}]},{"id":"DEV_Q064","question":"Is MQ or MQ Appliance impacted by Sweet32 Birthday Attack if we are running triple-DES cipher.?\n\nIs MQ or MQ Appliance impacted by Sweet32 Birthday Attack if we are running triple-DES cipher.?","answer":"The following versions are affected: \n\n * IBM MQ * Maintenance levels between 8.0.0.0 and 8.0.0.5 \n * 9.0.0.0 only\n \n \n * IBM MQ Appliance * Maintenance levels between 8.0.0.0 and 8.0.0.5\n \n \n * IBM WebSphere MQ * Maintenance levels between 7.0.1.0 and 7.0.1.14 \n * Maintenance levels between 7.1.0.0 and 7.1.0.8 \n * Maintenance levels between 7.5.0.0 and 7.5.0.7","is_impossible":false,"contexts":[{"filename":"swg21995099.txt","text":"Title: IBM Security Bulletin: IBM MQ and IBM MQ Appliance are vulnerable to SWEET32 Birthday attack (CVE-2016-2183) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A security vulnerability affects IBM MQ and IBM MQ Appliance, that could allow an attacker to obtain sensitive information when using a channel CipherSpec that uses the Triple-DES algorithm. The affected CipherSpecs are:\n\n- TRIPLE_DES_SHA_US\n- FIPS_WITH_3DES_EDE_CBC_SHA\n- ECDHE_ECDSA_3DES_EDE_CBC_SHA256\n- ECDHE_RSA_3DES_EDE_CBC_SHA256 \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-2183 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-2183]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error in the DES\/3DES cipher, used as a part of the SSL\/TLS protocol. By capturing large amounts of encrypted traffic between the SSL\/TLS server and the client, a remote attacker able to conduct a man-in-the-middle attack could exploit this vulnerability to recover the plaintext data and obtain sensitive information. This vulnerability is known as the SWEET32 Birthday attack.\nCVSS Base Score: 3.7\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/116337 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/116337] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nThe following versions are affected: \n\n * IBM MQ * Maintenance levels between 8.0.0.0 and 8.0.0.5 \n * 9.0.0.0 only\n \n \n * IBM MQ Appliance * Maintenance levels between 8.0.0.0 and 8.0.0.5\n \n \n * IBM WebSphere MQ * Maintenance levels between 7.0.1.0 and 7.0.1.14 \n * Maintenance levels between 7.1.0.0 and 7.1.0.8 \n * Maintenance levels between 7.5.0.0 and 7.5.0.7\n \n \n\nREMEDIATION\/FIXES\n IBM MQ V9.0 \n\n * Apply Fix Pack 9.0.0.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27048059]\n\nIBM MQ V8.0 & IBM MQ Appliance V8.0 * Apply Fix Pack 8.0.0.6 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0.0.6&platform=All&function=all]. \n * Apply Fix Pack 8.0.0.6 for IBM MQ Appliance [https:\/\/www.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].\n\nIBM MQ V7.5.0 * Apply APAR IV90867 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=7.5.0.7&platform=All&function=aparId&apars=IV90867&source=fc].\n\nIBM MQ V7.1.0 * Apply APAR IV90867 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=7.1.0.8&platform=All&function=aparId&apars=IV90867&source=fc].\n\nIBM MQ V7.0.1 * Users of MQ 7.0.1 should contact IBM support to request an interim fix for APAR IV90867.\n\nWORKAROUNDS AND MITIGATIONS\nAll versions of MQ can mitigate the vulnerability either by switching to an alternative CipherSpec or by enabling secret key reset. \nResetting SSL\/TLS secret keys [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_9.0.0\/com.ibm.mq.sec.doc\/q014310_.htm]\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 20 February 2017: Original version published\n21 March 2017: Removed applicability to 9.0.1 release\n4 April 2017: Added details for 7.0.1 fix\n24 May 2017: Details for 9.0.0.1 added\n19 June 2017: Removed HP & Solaris Specifics for 9.0.0.1 \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=swg21999690]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere MQ SSL Platform Independent 9.0, 8.0, 7.5, 7.1, 7.0.1 All Editions"}]},{"id":"DEV_Q065","question":"How do I enable my Applications to show up in the App Health view for the WAS agent?\n\nHow do I enable my Applications to show up in the App Health view for the WAS agent?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q066","question":"Help with Action required for IIIB V9 and 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. Where can I find this information? ","answer":"IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-8677, CVE-2016-8678 CVE-2016-9298, CVE-2014-9915, CVE-2016-10046, CVE-2016-10047, CVE-2016-10048, CVE-2016-10049, CVE-2016-10050, CVE-2016-10051, CVE-2016-10052, CVE-2016-10053, CVE-2016-10054, CVE-2016-10055, CVE-2016-10056, CVE-2016-10057, CVE-2016-10058, CVE-2016-10059, CVE-2016-10060, CVE-2016-10061, CVE-2016-10062, CVE-2016-10063, CVE-2016-10064, CVE-2016-10065, CVE-2016-10066, CVE-2016-10067, CVE-2016-10068, CVE-2016-10069, CVE-2016-10070, CVE-2016-10071, CVE-2016-10144, CVE-2016-10145, CVE-2016-10146, CVE-2017-5506, CVE-2017-5507, CVE-2017-5508, CVE-2017-5511, CVE-2017-6498, CVE-2017-6499, CVE-2017-6500, CVE-2017-6501, CVE-2017-6502, CVE-2016-10252 and CVE-2017-6497 \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.","is_impossible":false,"contexts":[{"filename":"swg22000947.txt","text":"Title: IBM Action required for IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 for security vulnerabilities in Red Hat Linux - United States\n\nText:\n FLASH (ALERT)\n\nABSTRACT\n IBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 require customer action for security vulnerabilities in Red Hat Linux. \n\nCONTENT\nIBM Integration Bus Hypervisor Edition V9.0 and WebSphere Message Broker Hypervisor Edition V8.0 ship with versions of Red Hat Enterprise Linux (RHEL) Server that are vulnerable to CVE-2016-8677, CVE-2016-8678 CVE-2016-9298, CVE-2014-9915, CVE-2016-10046, CVE-2016-10047, CVE-2016-10048, CVE-2016-10049, CVE-2016-10050, CVE-2016-10051, CVE-2016-10052, CVE-2016-10053, CVE-2016-10054, CVE-2016-10055, CVE-2016-10056, CVE-2016-10057, CVE-2016-10058, CVE-2016-10059, CVE-2016-10060, CVE-2016-10061, CVE-2016-10062, CVE-2016-10063, CVE-2016-10064, CVE-2016-10065, CVE-2016-10066, CVE-2016-10067, CVE-2016-10068, CVE-2016-10069, CVE-2016-10070, CVE-2016-10071, CVE-2016-10144, CVE-2016-10145, CVE-2016-10146, CVE-2017-5506, CVE-2017-5507, CVE-2017-5508, CVE-2017-5511, CVE-2017-6498, CVE-2017-6499, CVE-2017-6500, CVE-2017-6501, CVE-2017-6502, CVE-2016-10252 and CVE-2017-6497 \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"}]},{"id":"DEV_Q067","question":"BPM AppTarget startup hangs during startup\n\n\n\nDuring startup of the apptarget, JVM hangs with the following messages\n\n[9\/8\/14 14:11:01:709 CDT] 0000001f wle W com.lombardisoftware.server.core.GroupCore getAllGroups() CWLND0004W - The system has been waiting for the group replication lock to be released for the last 10 minutes. [9\/8\/14 14:11:32:810 CDT] 00000022 ThreadMonitor W WSVR0605W: Thread \"server.startup : 0\" (0000001f) has been active for 654582 milliseconds and may be hung. There is\/are 1 thread(s) in total in the server that may be hung. at java.lang.Thread.sleep(Native Method) at java.lang.Thread.sleep(Thread.java:896) at com.lombardisoftware.server.core.GroupCore.getAllGroups(GroupCore.java:545) at com.lombardisoftware.server.ejb.security.SecurityCore.listAllGroups(SecurityCore.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) ... [9\/8\/14 14:21:02:662 CDT] 0000001f wle W com.lombardisoftware.server.core.GroupCore getAllGroups() CWLND0004W - The system has been waiting for the group replication lock to be released for the last 20 minutes. [9\/8\/14 14:31:03:193 CDT] 0000001f wle W com.lombardisoftware.server.core.GroupCore getAllGroups() CWLND0004W -The system has been waiting for the group replication lock to be released for the last 30 minutes. [9\/8\/14 14:41:03:749 CDT] 0000001f wle W com.lombardisoftware.server.core.GroupCore getAllGroups() CWLND0004W -The system has been waiting for the group replication lock to be released for the last 40 minutes.","answer":"You will edit the wimconfig.xml file directly. However, before you edit the file, make a backup copy of it. Edit the wimconfig.xml file and search forconnectTimeout. Change this value from connectTimeout=\"20\" to connectTimeout=\"0\" and save the file. \n \n \n A complete restart of the WebSphere Application Server \/ IBM Business Process Manager environment is required to make this change take effect.","is_impossible":false,"contexts":[{"filename":"swg21615427.txt","text":"Title: IBM The 'Manage Group' Add User search in the Process Admin Console does not return available users for IBM Business Process Manager (BPM) - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When you search for a user within the 'Manage Group' in the Process Admin Console for IBM Business Process Manager, a more specific search keyword does not result in any entries. In addition, an LDAP timeout message is added to the SystemOut.log file. \n\nSYMPTOM\nWhen you do a broad search with a small keyword, you expect to receive many entries in return. When your search is more specific, you use a longer keyword to try to narrow the search. However, when you expect fewer returns from your search, it does not happen. The user list remains empty. \n\nYou can find the following exception in the SystemOut.log file:\n\n[8\/7\/12 14:02:59:435 CEST] 000000xx exception E com.ibm.ws.wim. \nadapter.ldap.LdapConnection search(String, String, Object[], \nSearchControls) CWWIM4520E The 'javax.naming.NamingException: LDAP \nresponse read timed out, timeout used:20000ms.; Remaining name: \n'DC=xxx,DC=xxx,DC=xxx,DC=com'; Resolved object: 'com.sun.jndi. \nldap.LdapCtx@196fbd6a'' naming exception occurred during processing. \n[8\/7\/12 14:02:59:435 CEST] 00000068 exception E com.ibm.ws.wim. \nadapter.ldap.LdapConnection search(String, String, Object[], \nSearchControls) \ncom.ibm.websphere.wim.exception. \nWIMSystemException: CWWIM4520E The 'javax.naming.NamingException: LDAP \nresponse read timed out, timeout used:20000ms.; Remaining name: \n'DC=xxx,DC=xxx,DC=xxx,DC=com'; Resolved object: 'com.sun.jndi. \nldap.LdapCtx@196fbd6a'' naming exception occurred during processing. \nat com.ibm.ws.wim.adapter.ldap.LdapConnection.search \n(LdapConnection.java:2951) \nat com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache \n(LdapConnection.java:2781) \nat com.ibm.ws.wim.adapter.ldap.LdapConnection.search \n(LdapConnection.java:2971) \n...\n\n\nCAUSE\nIn some cases, LDAP might take longer to respond on a more specific search, which results in an LDAP timeout. \n\n\n\nRESOLVING THE PROBLEM\nTo resolve this issue, increase the LDAP timeout limit by using one of the following options: \n\n \n\n * Option 1 \n Use the wsadmin command:\n $AdminTask updateIdMgrLDAPServer {-id AD -connectTimeout 0} \n $AdminConfig save \n \n \n After it is saved, view the wimconfig.xml file and make sure you see connectTimeout=\"0\" \n \n \n You can find the wimconfig.xml file in the following locations in the deployment manager configuration: * {WAS_HOME}\\profiles\\profile_name\\config\\cells\\cell_name\\wim\\config\\wimconfig.xml\n \n \n * profile_root\/conf\/cells\/cell_name\/wim\/config\/wimconfig.xml\n \n \n \n A complete restart of the WebSphere Application Server \/ IBM Business Process Manager environment is required to make this change take effect.\n \n \n * Option 2 \n You will edit the wimconfig.xml file directly. However, before you edit the file, make a backup copy of it. Edit the wimconfig.xml file and search forconnectTimeout. Change this value from connectTimeout=\"20\" to connectTimeout=\"0\" and save the file. \n \n \n A complete restart of the WebSphere Application Server \/ IBM Business Process Manager environment is required to make this change take effect.\n\n\nNote: The connectTimeout increment value is in seconds of time. The example value 0 is to wait indefinitely. Different values can be set accordingly. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5 Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5, 8.0.1, 8.0, 7.5.1, 7.5"}]},{"id":"DEV_Q068","question":"Getting java.lang.StackOverflowError, how to resolve it?\n\n\n\nGetting the following StackOverflowError when executing a dump namespace:\n\nTRACE START:\n\n java.lang.StackOverflowError at java.util.regex.Pattern$Branch.match(Pattern.java:4513) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4626) at java.util.regex.Pattern$Curly.match1(Pattern.java:4196) at java.util.regex.Pattern$Curly.match(Pattern.java:4145) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4567) at java.util.regex.Pattern$Branch.match(Pattern.java:4511) at java.util.regex.Matcher.match(Matcher.java:1232) at java.util.regex.Matcher.matches(Matcher.java:570) at com.ibm.rmi.corba.IIOPAddrImpl.(IIOPAddrImpl.java:107) at com.ibm.rmi.corba.Corbaloc.parseObjAddr(Corbaloc.java:231) at com.ibm.rmi.corba.Corbaloc.parseObjAddrList(Corbaloc.java:181) at com.ibm.rmi.corba.Corbaloc.parseCorbaloc(Corbaloc.java:145) at com.ibm.rmi.corba.Corbaloc.(Corbaloc.java:120) at com.ibm.rmi.corba.ORB.createObjectURL(ORB.java:3731) at com.ibm.rmi.corba.ORB.createObjectURL(ORB.java:3698) at com.ibm.rmi.corba.ORB.string_to_object(ORB.java:3694)\n\n","answer":"When a stack overflow occurs, the amount of stack space required by the program exceeds what is configured for the stack in the Java\u2122 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.","is_impossible":false,"contexts":[{"filename":"swg21162896.txt","text":"Title: IBM Diagnosing a java.lang.StackOverflowError - United States\n\nText:\nStackOverflow; 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\u2122 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<size> \n * \n * <size>\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=<size> \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<size> \n * \n * <size>\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<size> \n * \n * <size>\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 * <<Thread stack may follow this message>>\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: <analyzererror> \n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"}]},{"id":"DEV_Q069","question":"Why is my MQ client application getting error AMQ9050 regarding SYSTEM.PROTECTION.POLICY.QUEUE ?\n\nFailing to connect from a MQ client application to a MQ server queue manager that does not have MQ AMS (Advanced Message Security) component installed. \nExample: MQ v8 client trying to connect to a remote qmgr running MQ v7.0.1.x, getting \nerror AMQ9050 regarding SYSTEM.PROTECTION.POLICY.QUEUE.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q070","question":"Help with Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition(CVE-2016-3092)\n\nI need to understand details regarding Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition(CVE-2016-3092). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q071","question":"Why is Connection Refused on the ITCAM Managing Server?\n\nITCAM Data Collector connection to the Managing Server fails with Connection Refused. ","answer":"Instead of host name, specify a \u201cvalid\u201d IP address for the MS in the <MS_HOME>\/bin\/setenv.sh file, and in ITCAM 6.1, the ms.properties file.","is_impossible":false,"contexts":[{"filename":"swg21260969.txt","text":"Title: IBM ITCAM Data Collector connection to the Managing Server fails with Connection Refused. - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Data Collector (DC) connection may fail with \u201cConnection Refused\u201d if the Managing Server\u2019s(MS) host name can resolve to an IP address that cannot reach the MS. \n\nCAUSE\nThe DC obtains the MS kernel\u2019s network address from the MS. If a host name is specified for the kernel, and any of it\u2019s resolved IP addresses cannot reach the MS from the DC, ITCAM\u2019s connection attempt will fail if one of these \"invalid\u201d IP\u2019s is used.\n\nRESOLVING THE PROBLEM\nInstead of host name, specify a \u201cvalid\u201d IP address for the MS in the <MS_HOME>\/bin\/setenv.sh file, and in ITCAM 6.1, the ms.properties file. This solution usually works except when there is a firewall with Network Address Translation (NAT) enabled. In that case, you must make network changes so that all the resolved IPs can reach the MS. \n\nChange as directed:\n\nITCAM 6.0 ( or earlier )\nIn MS_home\/bin\/setenv.sh:\nKERNEL_HOST01=<ip addr of MS>\nKERNEL_HOST02=<ip addr of MS>\n\nITCAM 6.1\nIn MS_home\/bin\/setenv.sh:\nKERNEL_HOST01=<ip addr of MS>\nam_socket_bindip=<ip addr of MS>\nam_socket_exportip=<ip addr of MS>\nIn MS_HOME\/etc\/ms.properties, modify \u201ckernel.hosts\u201d specifying MS IP address:\nkernel.hosts=<ip addr of MS>CBSPort:RFSPort:RMIPort - usually -\nkernel.hosts=<ip addr of MS>9122:9120:9118\n\nExample:\nkernel.hosts=9.12.20.220:9122:9120:9118\n\nExample of the error message:\nThis example is from z\/OS, but the problem can occur on any platform.\n\n<PPECONTROLLER, 60014b53-f7e9-db01-4272-2a9f50388c89.511, \n9.12.20.161> Unable to join Kernel WSRT7.pdl.pok.ibm.com:9120 - \njava.net.ConnectException: EDC8128I Connection refused. \n(errno2=0x76630291); nested exception is: \njava.net.ConnectException: EDC8128I Connection refused. \n(errno2=0x76630291) \n\nTo determine IP addresses for a given MS host name [issue on the DC]:\nnslookup <MS_host_name> \n\nTo test basic connectivity, for each IP address listed by NSLOOKUP, issue:\nping <ip_address>"}]},{"id":"DEV_Q072","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect WMB and IIB\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect WebSphere Message Broker and IBM Integration Bus. Where can I find this information? ","answer":"If you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities, refer to the \u201cIBM Java SDK Security Bulletin\u201d, located in the References section for more information.","is_impossible":false,"contexts":[{"filename":"swg22005345.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect WebSphere Message Broker and IBM Integration Bus - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n Multiple security vulnerabilities exist in the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 6 Service Refresh 16 Fix Pack 41 and earlier releases used by WebSphere Message Broker, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 7 Service Refresh 10 Fix Pack 1 and earlier releases used by WebSphere Message Broker and IBM Integration Bus, and the IBM\u00ae Runtime Environment Java\u2122 Technology Edition Version 7R1 Service Refresh 4 Fix Pack 1 and earlier releases used by IBM Integration Bus. These issues were disclosed as part of the IBM Java SDK updates in April 2017. WebSphere Message Broker and IBM Integration Bus have addressed the applicable CVEs \n\nVULNERABILITY DETAILS\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities, refer to the \u201cIBM Java SDK Security Bulletin\u201d, located in the References section for more information.\n\nCVEID: CVE-2017-3511 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3511]\nDESCRIPTION: An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 7.7\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/124890 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/124890] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H) \n\nCVEID: CVE-2017-1289 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1289]\nDESCRIPTION: IBM SDK, Java Technology Edition is vulnerable XML External Entity Injection (XXE) error when processing XML data. A remote attacker could exploit this vulnerability to expose highly sensitive information or consume memory resources.\nCVSS Base Score: 8.2\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125150 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/125150] 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:N\/A:L) \n\nCVEID: CVE-2016-9840 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9840]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120508 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120508] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:L\/PR:N\/UI:R\/S:U\/C:N\/I:N\/A:L) \n\nCVEID: CVE-2016-9841 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9841]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an out-of-bounds pointer arithmetic in inftrees.c. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120509 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120509] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:L\/PR:N\/UI:R\/S:U\/C:N\/I:N\/A:L) \n\nCVEID: CVE-2016-9842 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9842]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by an undefined left shift of negative number. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120510 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120510] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:L\/PR:N\/UI:R\/S:U\/C:N\/I:N\/A:L) \n\nCVEID: CVE-2016-9843 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9843]\nDESCRIPTION: zlib is vulnerable to a denial of service, caused by a big-endian out-of-bounds pointer. By persuading a victim to open a specially crafted document, a remote attacker could exploit this vulnerability to cause a denial of service.\nCVSS Base Score: 3.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120511 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/120511] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:L\/PR:N\/UI:R\/S:U\/C:N\/I:N\/A:L)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V10.0.0.0- 10.0.0.8 \n\nIBM Integration Bus V9.0.0.0- 9.0.0.7 \n\nWebSphere Message Broker V8.0.0.0 - 8.0.0.8\n\nREMEDIATION\/FIXES\n\n\n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10.0.0.0- 10.0.0.8 IT20410 The APAR is available in fix pack 10.0.0.9 (on all platforms except HP) http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043686 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043686]\n\nIBM Integration Bus V9.0.0.0- 9.0.0.7 IT20410 The APAR is available in fix pack 9.0.0.8 (on all platforms except HP) http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043751 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043751]\n\nWebSphere Message Broker V8.0.0.0 - 8.0.0.8 IT20410 The APAR is available in fix pack 8.0.0.9 (on all platforms except HP) https:\/\/www.ibm.com\/support\/docview.wss?uid=swg24043806 [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg24043806]\n\n\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\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] \nIBM Java SDK Security Bulletin [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22002169] \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 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. \n\nRELATED INFORMATION\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"}]},{"id":"DEV_Q073","question":"What should I do if I observed \"ghost queue building up\" issue?\n\nThere are lots of ghost queues in the system, which have already took up most of file system space. What can I do under such situation?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q074","question":"Help with Security Bulletin: Security Vulnerability in IBM WebSphere Application Server affects IBM SOA Policy Gateway Pattern for AIX Server 2.5 (CVE-2015-1920)\n\nI need to understand details regarding Security Bulletin: Security Vulnerability in IBM WebSphere Application Server affects IBM SOA Policy Gateway Pattern for AIX Server 2.5 (CVE-2015-1920). Where can I find this information? ","answer":"CVEID: CVE-2015-1920 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C)","is_impossible":false,"contexts":[{"filename":"swg21959169.txt","text":"Title: IBM Security Bulletin: Security Vulnerability in IBM WebSphere Application Server affects IBM SOA Policy Gateway Pattern for AIX Server 2.5 (CVE-2015-1920) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A vulnerability in WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1920 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM SOA Policy Gateway Pattern for AIX Server version 2.5\n\nREMEDIATION\/FIXES\nCustomers should install WebSphere Application Server Interim Fix PI38302 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039898] \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 8 June 2015: 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."}]},{"id":"DEV_Q075","question":"My BPM 8.5.5 system has internet access. But I cannot upgrade to 8.5.6 from IM directly\n\nI have a BPM 8.5.5 system with internet access. But when I tried to upgrade BPM to 8.5.6 from Installation Manager with \"Update\", it failed with java.lang.NullPointerException","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q076","question":"Why is Oracle agent (rz) reporting listeners and services as 'Inactive' even when those are active?\n\nOn Unix\/Linux, the Extended Oracle agent sends false alert for listener status. All listeners and services in Net Service Connection workspace show as inactive.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q077","question":"I need to transfer my SPSS 24 licence to a new computer\n\nI need to transfer my SPSS 24 license to a new machine. I have only used my activation code on one computer so far, and that computer was found to be defective which has led me to get a new computer. I was able to download SPSS 24 Gradpack onto the new computer, but every time I put in the activation code, the program gives me an error message saying that I am not allowed to generate any new licenses.","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"DEV_Q078","question":"WebSphere MQ Hypervisor Edition requires customer action for the GNU C library (glibc) vulnerabilities (CVE-2015-1472)\n\nWhere can I find additional information on what action is required?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q079","question":"Why am I getting error SqlIntegrityConstraintViolationException when deploying a process application?\n\nAfter reinstalling Process Center (or using separate Process Centers to deploy to one Process Server) you get a deployment failure error on the Process Server:\njava.lang.Exception: java.lang.Exception:com.lombardisoftware.client.delegate.BusinessDelegateException:PreparedStatementCallback; \n....\ncom.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: Error forbatch element # 1: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505,SQLERRMC=2;BPMBDBA.LSW_SNAPSHOT, DRIVER=4.11.69","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q080","question":"Why is the OUTPUT_TYPE specified in the properties file for the custom scripting feature ignored?\n\n\n\nWhy is the OUTPUT_TYPE specified in the properties file for the custom scripting feature ignored in ITM V6?\n\nSpecifying \"I\" for INTEGER, or \"F\" for FLOAT for the OUTPUT_TYPE doesn't work, but specifying OUTPUT_TYPE=S results in STRING type for the first token.","answer":"OUTPUT_TYPE (STRING|INTEGER|FLOAT - Optional - default string). It defines the type of the first token returned by each row of the script;","is_impossible":false,"contexts":[{"filename":"swg21960062.txt","text":"Title: IBM OS Agents Version 6.3.0 FixPack 5 Scripting Feature - United States\n\nText:\n FIX README\n\nABSTRACT\n This feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency. \n\nCONTENT\n(C) Copyright International Business Machines Corporation 2015. All rights reserved.\nComponent: IBM(R) Tivoli(R) Monitoring OS Agents, Version 6.3.0 FixPack 5\n\nDate: 30 June 2015\n\nContents:\n\n1.0 Introduction\n1.1 Quick Start\n2.0 New Attribute groups\n3.0 Parameters in OS agent environment files\n4.0 Parameters in property file\n5.0 Examples of property file\n6.0 Examples of private situations \n7.0 Custom Scripts and Custom Scripts Runtime workspaces\n8.0 Known problems and limitations\n9.0 Troubleshooting\n10.0 Quick Start Scenario\n\n\n1. Introduction\n===============\n\nThis feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency.\n\nThe feature is enabled by default. The administrator can enable\/disable it by setting a new environment variable \nKXX_FCP_SCRIPT=true\/false (default true)in the agent configuration file, where XX can be:\n\n- LZ for Linux OS agent \n- UX for Unix OS agent\n- NT for Windows OS agent\n\nThis is an overview of the scripting feature; details will be provided in the following sections.\n\nThe OS agent loops, at a configurable interval, looking for script definition property files (*.properties) in a configurable directory path.\nThe property files are parsed and OS Monitoring Agent spawns a new process named \u201cfcp_daemon\u201d if at least one valid script definition is found. This new daemon is responsible for scheduling the script executions and gathering all information regarding running scripts.\n\nAccording to another configurable interval, the OS agent loops getting the execution script results from the fcp_daemon.\nThe OS Agent is able to parse the script standard output, splitting each row in up to 16 attributes.\nAn event is sent for each standard output row of the script and these events can be caught by pure event situations.\n\n1.1 Quick Start\n================\nThe feature is enabled with default values as soon as the OS agent is started. The only action to start using the feature is the following:\n- create a property file under default directory (on Linux\/UNIX is $CANDLEHOME\/localconfig\/<product code>\/scripts_definitions, on Windows is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions) using as an example the provided template script_property.txt.\n\nOnly two properties are required:\nATTRIBUTE_NAME=Any name used to uniquely identify the script definition inside the property file.\nSCRIPT_PATH_WITH_PARMS=The fully qualified path of the script with arguments. \n\nNot only shell scripts but also perl and other types of scripts can be used. You just need to specify the full command to execute in the SCRIPT_PATH_WITH_PARMS property. \nFor example, \"perl C:\\IBM\\scripts\\ITM_Custom_Scripts\\date.pl\". In this example you need to make sure that the location of \"perl\" can be resolved by the agent through the PATH variable in its environment. Specify the full path where \"perl\" is installed otherwise.\n\nFurther properties and details can be found in this document and in the template script_property.txt under $CANDLEHOME\/localconfig\/lz\/scripts_definitions. \n\n\n2. New Attribute groups\n=======================\n\nTwo new attribute groups have been added for this feature as detailed below. Statistic and execution data of all the scripts are stored in these two tables. The name of the property file (Property_File) and the attribute name defined in the property file (Attribute_Name) are the 2 key fields of these two tables. These two keys must be used in situation conditions to filter rows related to a specific script.\n\nAttribute group: KXX_Custom_Scripts (multiple rows), table: KXXSCRPTS (sampled).\nDescription: Configuration and statistic data gathered using custom scripts. It contains a row for each defined script, information on the fcp_daemon and on property files:\n\nAttribute Size Description\n=========================== ===== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Name 512 The name of the script.\nScript_Path 512 The fully qualified path name of the script with arguments.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting.\nStandard_Output_Type 4 Standard output type of the script.\nStatus_Code 4 The status of the script. It includes general errors, configuration errors, the status or the execution code returned by the \nScript Provider.\nExecution_Start 16 The time when the last execution of this script started.\nExecution_Duration 4 The duration of the last execution of this script, in seconds. When timing out, the value of the configured timeout is returnd.\nAverage_Execution_Duration 4 The average duration, in seconds, of all the execution of the script.\nRefresh_Interval 4 The interval, in seconds, that the agent attempts to start this script.\nNumber_of_Collections 4 The count of execution attempts of this script since agent started.\nIntervals_Skipped 4 The count of occurrences where an execution of this script is skipped because the previous execution is still running.\nProperty_Group 64 The name of the property group.\nReturn_Code 4 Integer value returned by the Script.\nCust_Label_Str1 16 Label for custom string attribute #1\nCust_Label_Str2 16 Label for custom string attribute #2\nCust_Label_Str3 16 Label for custom string attribute #3\nCust_Label_Str4 16 Label for custom string attribute #4\nCust_Label_Str5 16 Label for custom string attribute #5\nCust_Label_Int1 16 Label for custom integer attribute #1\nCust_Label_Int2 16 Label for custom integer attribute #2\nCust_Label_Int3 16 Label for custom integer attribute #3\nCust_Label_Int4 16 Label for custom integer attribute #4\nCust_Label_Int5 16 Label for custom integer attribute #5\nCust_Label_Float1 16 Label for custom floating point attribute #1\nCust_Label_Float2 16 Label for custom floating point attribute #2\nCust_Label_Float3 16 Label for custom floating point attribute #3\nCust_Label_Float4 16 Label for custom floating point attribute #4\nCust_Label_Float5 16 Label for custom floating point attribute #5\nStandard_Error 2048 Script Standard Error in a unique row\n\nIn addition to script definitions, the table may report rows to return errors found on property files and they are identified by @ANY@ as Attribute_Name. Moreover, a row is always used to report the status of fcp_daemon and it is identified by @ANY@ as Property_File and @ANY@ as Attribute_Name.\n\nAttribute group: KXX_Custom_Scripts_Runtime (multiple rows), table: KXXSCRRTM (pure).\nDescription: Data gathered using custom scripts. It contains the output rows of the scripts currently running:\n\nAttribute Size Description\n======================= ==== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Path 512 The fully qualified path of the script.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting. \nReturn_Code 4 Integer value returned by the Script.\nRow_Number 4 Output row number.\nStandard_Output_Type 4 Standard output type of the script.\nStandard_Output_String 2048 Script Standard Output in String Format.\nStandard_Output_Integer 8 Script Output in Integer Format\nStandard_Output_Float 8 Script Output in Floating Point Format (2 decimals).\nCust_Attr_Str1 64 Custom string attribute #1\nCust_Attr_Str2 64 Custom string attribute #2\nCust_Attr_Str3 64 Custom string attribute #3\nCust_Attr_Str4 64 Custom string attribute #4\nCust_Attr_Str5 64 Custom string attribute #5\nCust_Attr_Int1 8 Custom integer attribute #1\nCust_Attr_Int2 8 Custom integer attribute #2\nCust_Attr_Int3 8 Custom integer attribute #3\nCust_Attr_Int4 8 Custom integer attribute #4\nCust_Attr_Int5 8 Custom integer attribute #5\nCust_Attr_Float1 8 Custom floating point (2 decimals) attribute #1\nCust_Attr_Float2 8 Custom floating point (2 decimals) attribute #2\nCust_Attr_Float3 8 Custom floating point (2 decimals) attribute #3\nCust_Attr_Float4 8 Custom floating point (2 decimals) attribute #4\nCust_Attr_Float5 8 Custom floating point (2 decimals) attribute #5\n\nNote: different status conditions can be monitored using the Status_Code field in the statistic table KXX_Custom_Scripts. \nThe following detailed list provides different values for the Status_Code field: \n\nInitial general statuses\nUNKNOWN_ERROR (status code=0) --> Error\nNO_ERROR (status code=1) --> Informational\n\nGeneral daemon statuses\nFEATURE_NOT_ENABLED (status code=40) --> Informational\nDAEMON_STARTING (status code=2) --> Informational\nDAEMON_STARTED (status code=3) --> Informational\nDAEMON_STOPPING (status code=4) --> Informational\nDAEMON_STOPPED (status code=5) --> Informational\nDAEMON_STOPPING_AT_AGENT_STOP (status code=6) --> Informational\nDAEMON_STOPPED_AT_AGENT_STOP (status code=7) --> Informational\nDAEMON_ERROR (status code=8) --> Error\nDAEMON_ERROR_NO_RESTART (status code=9)-> Fatal Error\n\nGeneral directory statuses\nERROR_OPENING_PROP_DIRECTORY (status code=10) --> Error\nPROP_DIRECTORY_NOT_FOUND (status code=11) --> Error\nNO_SCRIPT_DEFINED (status code=12)--> Warning\n\nProperty file statuses\nPROP_FILE_NOT_FOUND (status code=13) --> Error\nERROR_OPENING_PROP_FILE (status code=14) --> Error\n\nScript definition statuses\nSCRIPT_ADDED (status code=15) --> Informational\nSCRIPT_CHANGED (status code=16) --> Informational\nSCRIPT_REMOVED (status code=17) --> Informational\nSCRIPT_INACTIVE (status code=18) --> Informational\nNO_SCRIPT_PATH (status code=21)--> Error\nSCRIPT_PATH_INVALID (status code=22)--> Error\n\nExecution statuses from the fcp_daemon\nFACTORY_UNKNOWN_ERROR (status code=23) --> Error\nFACTORY_NO_ERROR (status code=24)--> Informational\nGENERAL_ERROR (status code=25)--> Error\nOBJECT_NOT_FOUND (status code=26)--> Error\nOBJECT_CURRENTLY_UNAVAILABLE (status code=27)--> Error\nNO_INSTANCES_RETURNED (status code=28)--> Error\nNO_RESPONSE_RECEIVED (status code=29)--> Error\nAUTHENTICATION_FAILED (status code=30)--> Error\nACCESS_DENIED (status code=31)--> Error\nTIMEOUT (status code=32)--> Error\nNOT_IMPLEMENTED (status code=33)--> Error\nRESPONSE_TOO_BIG (status code=34) --> Error\nGENERAL_RESPONSE_ERROR (status code=35)--> Error\nSCRIPT_NONZERO_RETURN (status code=36)--> Error\nSCRIPT_NOT_FOUND (status code=37)--> Error\nSCRIPT_LAUNCH_ERROR (status code=38)--> Error\nINVALID_TOKEN_TYPES(status code=39) --> Error\n\n3. Parameters in OS agent environment files\n===========================================\n\nIt is possible to customize the feature setting parameters in the OS agent environment files:\n- $CANDLEHOME\/config\/lz.ini file for the Linux OS agent\n- $CANDLEHOME\/config\/ux.ini for the UNIX OS agent\n- %CANDLE_HOME%\\TMAITM6_x64\\KNTENV for Windows 64bit OS agent\n- %CANDLE_HOME%\\TMAITM6\\KNTENV for Windows 32bit OS agent\n\nThe scripting feature is enabled by default. To disable it set:\n- KXX_FCP_SCRIPT=false\n\nOther parameters can be defined inside the agent environment files based on specific needs:\n\n- KXX_FCP_SCRIPT_DEFINITIONS (default location on Linux\/UNIX is $CANDLEHOME\/localconfig\/<product code>\/scripts_definitions, on Windows it is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions)\nThe location where property files are stored.\n\n- KXX_FCP_SCRIPT_INTERVAL (default 60 sec)\nOS agent uses the value of this variable as loop interval in seconds to check execution of running scripts and it sends events if the filter condition is satisfied. The minimum value is 30 seconds, the maximum value is 300 seconds. Invalid values will be reset to the default.\nNote: this parameter is ignored if KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT (see definition below).\n\n- KXX_FCP_SCRIPT_SYNC_INTERVALS (USE_AGENT|USE_SCRIPT|NO - default USE_AGENT)\nIf the agent looping interval defined by KXX_FCP_SCRIPT_INTERVAL is bigger than the script execution frequency, it can happen that data produced by some of the script execution loops is lost.\nTo avoid this behaviour the script execution frequency can be synchronized with the agent looping interval setting the KXX_FCP_SCRIPT_SYNC_INTERVALS to:\n- USE_AGENT; the value of each script execution frequency is forced to be the maximum between KXX_FCP_SCRIPT_INTERVAL and EXECUTION_FREQUENCY defined in its property file. \n- USE_SCRIPT; the agent looping interval is dynamically set to the minimum frequency value (EXECUTION_FREQUENCY in property file) between all of the defined scripts . The value set by KXX_FCP_SCRIPT_INTERVAL is ignored. The frequency of the scripts remain the ones defined in the property files. When using USE_SCRIPT, the agent looping interval may change every time a script definition is added, changed or removed. In any case, it cannot be lower than the value set by KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT or bigger than 300 seconds.\n- NO; no synchronization is performed and some execution results could be lost.\n\n- KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL (default 300 sec) \nAt startup and at every interval defined by this variable, the OS agent checks for any changes in scripts or property files.\nNote that if KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL is less than the agent looping interval it will be reset to the agent looping interval. The maximum allowed value is the default, 300 seconds.\n\n- KXX_FCP_USER (default OS agent user)\nThis parameter is valid only on linux and unix platforms. It defines the user used to spawn fcp_deamon process if different from OS agent process user; all the scripts are executed by this user. Note that the user owner of the OS agent must have correct permission to spawn the fcp_daemon process. On windows a different user must be defined as login of the service \"Monitoring Agent for Windows OS - FCProvider\". The user must have \"Full Control\" permission to CANDLE_HOME and scripts repository directories. For more information please refer to official IBM Monitoring documentation: \nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0.2\/com.ibm.itm.doc_6.3fp2\/oswin\/running_as_a_non-admin_user.htm [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0.2\/com.ibm.itm.doc_6.3fp2\/oswin\/running_as_a_non-admin_user.htm]\n\n- KXX_FCP_MAX_CDP_DP_THREAD_POOL_SIZE (default 10)\nIt defines the maximum concurrent number of scripts to be executed. Maximum value is 32.\n\n- KXX_FCP_MAX_DAEMON_RESTARTS (default 4)\nThe OS agent watches the fcp_daemon: if an abnormal exit of process occurs, the OS agent restarts it. This is done for the KXX_FCP_MAX_DAEMON_RESTARTS (times at a day). \nThe value 0 must be used to avoid the restart; if -1 is set, the OS agent retries to restart fcp_daemon forever. The restart counter is reset at OS agent restart.\n\n- KXX_FCP_SEND_SCRIPT_RUNTIME_EVENTS (default: true)\nIf set to false, the OS agent stops sending events for each row of script standard output. In this case script outputs are visible on TEP console workspaces but no situations will be displayed and no historical collection data will be collected. \n\n- KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT (default: 5 seconds) \nIt is used when KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT. In this condition, it sets the minimum value of the OS agent looping interval.\nUsing low values for the the OS agent looping interval (less than 5 seconds) is highly invasive and can impact OS agent performances. If a frequent data collection is needed (e.g. every second), it is strongly suggested to customize a script that caches data at the needed frequency and returns the collected data to the OS agent at an higher interval (e.g. every 60 seconds).\n\n\nThe following Agent Builder (CDP) variables can also be used to control the behavior of the fcp_daemon:\n\n- CDP_DP_REFRESH_INTERVAL (default 60 sec) Global script scheduled start time. Used if the frequency is not passed in the script property file.\n\n- CDP_DP_SCRIPT_TIMEOUT (default 30 sec) Global script execution maximum time. When the execution time of a script exceeds this limit, its Status_Code is set to TIMEOUT\n\n- CDP_DP_KILL_ORPHAN_SCRIPTS (Y|N - default N) Global behaviour used by fcp_daemon process for timing out scripts. When set to 'Y', the scripts are killed, otherwise they are abandoned. This value is ignored for a specific script if the KILL_AFTER_TIMEOUT key is set in the script property file\n\n- CDP_MAXIMUM_ROW_COUNT_FOR_CPCI_DATA_RESPONSES (default 1000) Global value added for performance reasons to limit the maximum number of output rows returned by the scripts. Additional rows after this limit are ignored. Allowed values are positive integer. Invalid values means no limit.\n\nThe fcp_daemon also supports the other environment variables used to control Agent Builder agents. For a complete list see the official Agent Builder documentation here:\nhttp:\/\/publib.boulder.ibm.com\/infocenter\/tivihelp\/v61r1\/topic\/com.ibm.itm.doc_6.3\/agentbuilder63_user.pdf [http:\/\/publib.boulder.ibm.com\/infocenter\/tivihelp\/v61r1\/topic\/com.ibm.itm.doc_6.3\/agentbuilder63_user.pdf]\n\n4. Parameters in property files \n===============================\n\nThe KXX_FCP_SCRIPT_DEFINITIONS directory contains a list of *.properties files. Each property file contains a list of \nscripts to run with respective properties in the form of key=value. The properties that can be defined (case in-sensitive) are: \n\n- ATTRIBUTE_NAME (Required - string max 256 characters).\nIt is a name of your choice that defines a specific script and its attributes. The characters that can be used for the \nATTRIBUTE NAME name can be alphabetical, numeric and only the underscore can be used as a special character. If other special characters (even a blank is considered this way) are used they get converted into underscore (_).\nWhen multiple scripts are listed inside the same property file, more different ATTRIBUTE_NAME must be defined (one for each script). It must be the first value specified for each defined script and delimits the start of the properties set for the specific script until the next ATTRIBUTE_NAME.\n\n- SCRIPT_PATH_WITH_PARMS (Required - string max 512 characters).\nIt defines the full path to the script with parameters, separated by a blank. No special characters can be used in the script path name. \nValues containing blanks must be enclosed in single (') or double quotes (\").\nEnvironment variables can be passed, but only enclosed in ${...} for all the platforms. Environment variables must be available in the OS agent process context.\n\n- EXECUTION_FREQUENCY (Optional - default 60 sec).\nIt indicates the script execution frequency.\n\n- CUSTOM_NAME (Optional - string max 256 characters)\nThe user can fill it with a description of the script.\n\n- IS_ACTIVE (true|false - Optional - default true). \nIt activates the script. If false, the script is not executed.\n\n- DISABLE_USE_AGENT_SYNC (true|false - Optional - default false). If true, the EXECUTION_FREQUENCY of the script is respected also if the global variable KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_AGENT.\n\n- KILL_AFTER_TIMEOUT (true|false - Optional - default value defined by the CDP_DP_KILL_ORPHAN_SCRIPTS variable). \nWhen true the script is killed after timeout (a timeout occurs when script execution is greater than the value specified by CDP_DP_SCRIPT_TIMEOUT parameter in OS agent configuration file) otherwise it is ignored. In both cases no data is collected. Note that when KILL_AFTER_TIMEOUT is set, only the script defined in property file is killed and not child processes (if any) spawned by the script. This feature is not supported by Solaris and Windows 32 bit OS agents and any timing out scripts are abandoned. \n\n\nOutput rows returned by a script are parsed. The script returns a standard output (called hereafter as first token). When the script returns more values in the output row they are added as additional tokens for a maximum of 5 strings, 5 integers and 5 floats following a predefined syntax as described below:\n\n- OUTPUT_TYPE (STRING|INTEGER|FLOAT - Optional - default string). It defines the type of the first token returned by each row of the script;\nOUTPUT_TYPE can be:\n1. STRING (default): strings up to 2048 characters. When used, the \"Standard_Output_String\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n2. INTEGER: allows getting numeric values between -9223372036854775806 and 9223372036854775806. When used, the \"Standard_Output_Integer\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n3. FLOAT: allows getting numeric values between -92233720368547758.06 and 92233720368547758.06,(with 2 decimal\nprecision). When used, the \"Standard_Output_Float\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n\n- TOKEN_TYPES (STRING|INTEGER|FLOAT - Optional).\nIt defines the output type of additional tokens after the first one. The user can define a maximum of 5 strings, 5 integers and 5 floats. It is a list of types separated by commas:\n<token_type>,<token_type>,\u2026\ntoken_type can be empty or one from (case insensitive):\n- STRING or S\n- INTEGER or I\n- FLOAT or F\nIf <token_type> is empty, the corresponding token is skipped.\nExamples of the same valid layouts:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_TYPES=String,integer,S,,,Float,,f,FLOAT\n\n- TOKEN_LABELS (STRING - maximum 16 characters each label - Optional). \nIt defines the labels of the tokens defined in TOKEN_TYPES. This value is a list of token labels separated\nby commas, and must correspond to the tokens defined by TOKEN_TYPES. \ne.g.:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_LABELS=Cpu Name,Cpu number,Description,,,value 1,,value 2,value 3 \nIt is ignored if TOKEN_TYPES is not set.\n\n- TOKEN_SEPARATOR (Optional - default semicolon \";\"). \nIt sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one.\n\n\nThe following two parameters allow you to filter the rows output of a script; they are applied by the OS agent only to the first token and they must be used together:\n\n- FILTER_VALUE (Optional).\nThe value used for comparison. It is required if FILTER_OPERATOR is defined.\nIf the OUTPUT_TYPE is a string, the filter value must reflect exactly the string value returned by the script that is intended to be filtered, without any additional quotes (no wildcards allowed).\n- FILTER_OPERATOR (Optional).\nThe operator used for the comparison. It is required if FILTER_VALUE is defined. Accepted FILTER_OPERATOR values include:\n= (equal to)\n!= (different from)\n> (bigger than) only for numeric type\n>= (not lower than) only for numeric type\n< (lower than) only for numeric type\n<= (not bigger than) only for numeric type\n\n\n\n5. Examples of property file\n============================\n\n#First script definition: script ex_script1.sh is launched every 150 seconds, it returns float values and only the output rows equal to 0.5 will be considered by the agent.\n\nATTRIBUTE_NAME=sample1 \nSCRIPT_PATH_WITH_PARMS=\/opt\/ibm\/itmd4255a\/localconfig\/lz\/scripts_definitions\/ex_script1.sh\nEXECUTION_FREQUENCY=150\nOUTPUT_TYPE=FLOAT\nFILTER_VALUE=0.5\nFILTER_OPERATOR==\n\n#Second script definition: script ex_script2 is launched every 60 seconds, it returns integer values and only the rows different from 0 will be considered by the agent.\n\nATTRIBUTE_NAME=ex_script2\nSCRIPT_PATH_WITH_PARMS=${CANDLE_HOME}\/tmp\/check_out.sh\nEXECUTION_FREQUENCY=60\nOUTPUT_TYPE=INTEGER\nFILTER_VALUE=0\nFILTER_OPERATOR=!=\n\n#Third script definition: script ex_script3.sh is launched every 120 seconds with 3 input parameters (the first input parameter is an integer, the second and third are string). It's killed if it hangs or if the execution time is greater than the timeout value.\n\nATTRIBUTE_NAME=ex_script3 \nSCRIPT_PATH_WITH_PARMS=\/opt\/scripts\/ex_script3.sh 1 \"second input parameter\" \"third input parameter\" \nEXECUTION_FREQUENCY=120\nOUTPUT_TYPE=STRING\nKILL_AFTER_TIMEOUT=TRUE\n\n#Fourth script definition: script cpu_mem_percentage.sh is launched every 50 seconds and returns the cpuid as standard output string and 2 float for Idle and Used CPU percentage and 2 integers for Memory and Virtual Memory usage. The pipe is used as separator to parse the output. An example of row that must be returned by the script is: \ncpu2|35,5|65,5|3443|123800\n\nATTRIBUTE_NAME=cpu and mem Usage\nSCRIPT_PATH_WITH_PARMS=${SCRIPT_HOME}\/cpu_mem_percentage.sh\nOUTPUT_TYPE=STRING\nTOKEN_TYPES=F,F,I,I\nTOKEN_LABELS= Idle CPU %, Used CPU %, Virt MEM used MB, MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=50\n\n6. Examples of private situations \n==================================\n\nThe private situations definitions can be inserted into the xx_situations.xml under $CANDLEHOME\/localconfig\/lz for linux or $CANDLEHOME\/localconfig\/ux for unix or %CANDLE_HOME%\\localconfig\\nt for Windows to monitor scripts execution.\nExamples below are for the Linux OS agent:\n\n<PRIVATESIT>\n<!-- Sends an alert if the script defined by attribute name \"demo\" in property file \"demo.properties\" returns a row equal to \"demo.log\" -->\n<SITUATION>FCP_CheckLOGFileExists_pr<\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts_Runtime.Property_File *EQ 'demo.properties' *AND *VALUE KLZ_Custom_Scripts_Runtime.Attribute_Name *EQ 'demo' *AND *VALUE KLZ_Custom_Scripts_Runtime.Standard_Output_String *EQ 'demo.log']]>\n<\/CRITERIA>\n<\/PRIVATESIT>\n\n<PRIVATESIT>\n<!-- Sends an alert if a script exits with a return code different from zero -->\n<SITUATION>FCP_ScriptRetCode_pr<\/SITUATION>\n<CRITERIA>\n<![CDATA[*IF *VALUE KLZ_Custom_Scripts.Return_Code *NE 0]]>\n<\/CRITERIA>\n<\/PRIVATESIT>\n\n<privatesit>\n<!-- Sends an alert when script path is not defined in a property file -->\n<SITUATION NAME=\"FCP_NOPTAH\" INTERVAL=\"000030\" ><\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ NO_SCRIPT_PATH]]>\n<\/criteria>\n<\/privatesit>\n\n<privatesit>\n<!-- Sends an alert when a script cannot be launched -->\n<SITUATION NAME=\"FCP_ScriptLaunchErr\" INTERVAL=\"000060\" ><\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ SCRIPT_LAUNCH_ERROR]]>\n<\/criteria>\n<\/privatesit>\n\n\n7. Custom Scripts and Custom Scripts Runtime Workspaces\n=======================================================\n\nA new OS agent navigation item has been added in the TEP console. It contains two workspaces: \"Custom Scripts\" and \"Custom Scripts Runtime\". \n\n\"Custom Scripts\" workspace contains the following views:\n- \"Factory Daemon Status\" table view showing informational\/warning\/error events related to the fcp_daemon process.\n- \"Properties Files error\" table view showing problems related to property files.\n- \"Number of execution per script\" bar chart view summarizing the executions of defined scripts\n- \"Defined Scripts\" table view showing detailed information of defined scripts.\n\n\"Custom Scripts Runtime\" workspace is called clicking on the anchor of a specific script and provides information on script execution. The views provided by default on the TEP console are to be intended as example workspaces with all available custom attributes. Users can duplicate and customize workspaces to filter out fields that are not needed according to the output returned by their scripts.\n\n\n8. Known problems and limitations\n===================================\n\n- The Scripting Feature is not supported on Windows 2003 64-bit systems.\n- Kill after timeout does not work on Solaris and Windows 32 bit OS agents.\n- The fcp_daemon may stop executing scripts in Windows 32 bit If some scripts do not complete within the time out period and the user has turned on intensive tracing. If this happens the data reported on the TEP will reflect the last time the script was actually run. It is also possible that the OS agent will stop returning data. Terminating the fcp_daemon process will allow the agent to resume proper operation.\n- SCRIPT_NONZERO_RETURN is returned instead of SCRIPT_NOT_FOUND or SCRIPT_LAUNCH_ERROR on Solaris.\n- The scripting feature does not provide full Native Language Support; some issues may be found using Nationalized characters in property files or script outputs.\n- On windows OS agent there is no possibility of executing scripts residing on a mapped network drive.\n\n9. Troubleshooting\n===================\n\nStandard KBB_RAS1 variable will apply to the OS agent and to the fcp_daemon processes.\nTo apply a specific trace setting to fcp_daemon only, use the KXX_FCP_KBB_RAS1 variable; when KXX_FCP_KBB_RAS1 is set, the value specified by KBB_RAS1 is ignored by fcp_daemon.\n\nTo trace the operations logged by the OS agent core threads of the feature:\nKBB_RAS1=ERROR (UNIT:factory ALL)\n\nTo trace scripting queries from the ITM server and events sent to the server, add the entries:\n(UNIT:klz34 ALL) (UNIT:klz35 ALL) on Linux OS agent\n(UNIT:kux48 ALL) (UNIT:kux49 ALL) on Unix OS agent\n(UNIT:knt84 ALL) (UNIT:knt85 ALL) on Windows OS agent\n\nTo view tema traces to verify private situation execution, add the entries:\n(UNIT:kraavp all) (UNIT:kraapv all)\n\nTo see the execution of the scripts and how the data from the scripts is being parsed set:\nKXX_FCP_KBB_RAS1=Error (UNIT:command ALL)\n\nTo troubleshoot problems in the communication between the os agent and fcp_daemon add this trace level to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket FLOW) (UNIT:cpci FLOW)\n\nTo see the interaction between the OS agent process and the fcp_daemon in detail add to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket ALL) (UNIT:cpci ALL)\n\n\n10. Quick Start Scenario\n=========================\n\nThe following section describes the minimum steps needed to configure a linux OS agent to run 2 custom scripts.\n\nCustom Scripts descriptions\n===========================\nLet's suppose the user has 2 scripts under a directory \/scripts_repo:\n\n- checkDIRsize.sh that checks the size of a specified directory passed as input parameter. Its output is an integer like the following: \n\n4594740\n\n- cpu_mem_usage.sh that checks the used CPU percentages and used Swap Memory megabytes. Its output is returned in the following form:\n\ncpu1|96,5|23800\n\nwhere the first token is the CPU id, the second token is the used CPU percentage, the third token is the used swap memory in megabyte.\n\nCustomization needed to have the linux OS agent run above scripts\n==============================================================\nThe feature is enabled with default values as soon as the OS agent is started:\n\n- you could create one or two property files (<Any Name>.properties)under the default directory $CANDLEHOME\/localconfig\/lz\/scripts_definitions. In this example let's create 2 property files one for each script called checkDIRsize.properties and cpu_mem_usage.properties:\n\n#CheckDIRsize.properties\nATTRIBUTE_NAME=OPT_DIR_SIZE\nSCRIPT_PATH_WITH_PARMS=\/scripts_repo\/checkDIRsize.sh \/opt\nEXECUTION_FREQUENCY=20\nOUTPUT_TYPE=INTEGER\n\n#cpu_mem_usage.properties \nATTRIBUTE_NAME=cpu_mem_usage\nSCRIPT_PATH_WITH_PARMS=\/scripts_repo\/cpu_mem_percentage.sh\nOUTPUT_TYPE=string\nTOKEN_TYPES=F,I\nTOKEN_LABELS= Used CPU %, Swap MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=10\n\n- There is no need to restart the OS agent after adding (or changing) the 2 property files above: the OS agent checks script definition directory with a specified time interval (default value 300 seconds). Open the TEP console and under the \"Custom Scripts\" workspace the scripts details and results are shown.\n\nChange History:\n----------------------\n2017-01-09: Added new item under \"8. Known problems and limitations\" that the Scripting Feature is not supported on Windows 2003 64-bit systems."}]},{"id":"DEV_Q081","question":"What are the files created in $TEMP on startup of IIB or WMB?\n\nWhat are the 0 byte files created in $TEMP\/.com_ibm_tools_attach directory upon IBM Integration Bus (IIB) \/ WebSphere Message Broker (WMB) startup?\nFor example: The following files are created on UNIX \/ Windows if $TEMP is \/tmp:\n\/tmp\/.com_ibm_tools_attach\/_attachlock\n\/tmp\/.com_ibm_tools_attach\/_master\n\/tmp\/.com_ibm_tools_attach\/_notifier","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q082","question":"Help with Security Bulletin: IIB is affected by Web UI security vulnerability (CVE-2017-1694)\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by Web UI security vulnerability (CVE-2017-1694). Where can I find this information? ","answer":"CVEID: CVE-2017-1694 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1694]\nDESCRIPTION: IBM Integration Bus transmits user credentials in plain in clear text which can be read by an attacker using man in the middle techniques.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134165 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134165] 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)","is_impossible":false,"contexts":[{"filename":"swg22011695.txt","text":"Title: IBM Security Bulletin: IBM Integration Bus is affected by Web UI security vulnerability (CVE-2017-1694) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM Integration Bus has addressed the following vulnerability \n\nVULNERABILITY DETAILS\n\nCVEID: CVE-2017-1694 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-1694]\nDESCRIPTION: IBM Integration Bus transmits user credentials in plain in clear text which can be read by an attacker using man in the middle techniques.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134165 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/134165] 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\nIBM Integration Bus V10.0.0.0 - V10.0.0.9 \n\n IBM Integration Bus V9.0.0.0 - V9.0.0.9\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation \/ Fix IBM Integration Bus V10.0.0.0 to V10.0.0.9 APAR IT21391 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.9 APAR IT21391 The APAR is available in fix pack 9.0.0.10\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044363 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044363] 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.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 15th Dec 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\nRELATED INFORMATION\n#"}]},{"id":"DEV_Q083","question":"How do you configure the IBM HTTP Server 7 to 8.5 on z\/OS for Host On-Demand V11?\n\nThe IBM HTTP Server powered by Domino will no longer be shipped with z\/OS 2.2, so how can system administrators of Host On-Demand convert to the IBM HTTP Server V7 to V8.5?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q084","question":"Is ITCAM for J2EE 7.1.1 agent supported on RHEL7.x?\n\n\n\nWhen I try to install IBM Tivoli Composite Application Manager Agent for J2EE V7.1.1.0,Linux on x86, English (CN0PKEN) on RHEL 7.2 64-bits\n\nI am getting the following error message:\n\ninstall.sh failure: KCI1138E could not determine the machine's architecture.\n\nIs ITCAM for J2EE 7.1.1 supported on RHEL7?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q085","question":"Event Dashboard breaks with Japanese filter\n\nEvent Dashboard breaks when a filter is created with the browser language set to Japanese. This issue occurs in WebGUI 8.1 Fix Pack 11. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q086","question":"Upgraded to IBM HTTP Server 7.0.0.41, is TLS 1.2 supported?\n\n\n\nWe are recently upgraded to IBM HTTP Server 7.0.0.41 and believe it supports TLS 1.0.\n\nPlease let us know what configuration changes or fix pack we need to apply to support TLS 1.2.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q087","question":"Is WMB v7 compatible with MQ v8?\n\nThis Q&A is abstracted from a PMR\nPlanning a tiered upgrade, MQ then broker.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q088","question":"CQWEB can\\'t retrieve repository dropdown list options in RedHat Linux, how to deal with it ?\n\nI setup a cq demo env in redhat linux with oracle database, CQ 7.1.2, LRKS 8.1.3, Linux CQ client can login CQ as the following picture 1, but CQWEB login page can't retrieve the repository dropdown list options as the following picture 2. I used cqreg to register CQ database:\n\ncqreg add_dbset -v ORACLE -s 192.168.0.84 -d ESBDB -u cqadmin -p cqadmin -dbset CQ_DEMO_ORACLE -co LOB_TYPE=CLOB -force\n\nWhat's matter for this happen? ","answer":"Normally, at the end of a ClearQuest installation on UNIX\u00ae based platforms, the cqreg initialize command runs automatically. The command creates the registry structure for database sets. During the installation, the command did not run successfully.","is_impossible":false,"contexts":[{"filename":"swg21320206.txt","text":"Title: IBM ERROR: Default DB path is not set, when adding database set on RHEL 5 - United States\n\nText:\n1320206; ClearQuest; Command Line Tools; CQ; cqreg; add_dbset; initialize; CQ_DATABASES; CQDB_rgys; registry; db set; db_set; Default DB path is not set; Use cqreg initialize first; linux; RHEL; RHEL5 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains why the error, \"Default DB path is not set\", occurs when adding a connection with IBM\u00ae Rational\u00ae ClearQuest\u00ae on RedHat Enterprise Linux\u00ae (RHEL) 5. \n\nSYMPTOM\nWhen running the command cqreg add_dbset, this error occurs:\n\n\"Default DB path is not set\"\n\"Default version is 7.0.0\"\n\/opt\/rational\/clearquest\/CQDB_rgys\/cqdb_registry\/7.0.0 does not exist. Use cqreg initialize first. \n\nCAUSE\nNormally, at the end of a ClearQuest installation on UNIX\u00ae based platforms, the cqreg initialize command runs automatically. The command creates the registry structure for database sets. During the installation, the command did not run successfully.\n\nDIAGNOSING THE PROBLEM\nVerify that the CQDB_rgys directory exists, as defined in the installation options. The following is the default registry location: \n\n\n\/opt\/rational\/clearquest\/CQDB_rgys\/cqdb_registry\/\n\nIf not present, then the cqreg initialize command was not successful.\n\n\nRESOLVING THE PROBLEM\nRun cqreg initialize. The add_dbset command will run successfully afterwards. However, should the same error persist, make sure the command is run as the root user. \n\n\n\nAlso make sure that the CQ_DATABASES environment variable is set to the desired registry path. If it is not, set the variable accordingly, then run the previously mentioned commands again."}]},{"id":"DEV_Q089","question":"Security Bulletin: Vulnerability identified in OpenSSL shipped with IBM API Connect (CVE-2016-8610)\n\nI need to understand details regarding Security Bulletin: Vulnerability identified in OpenSSL shipped with IBM API Connect (CVE-2016-8610). Where can I find this information? ","answer":"VULNERABILITY DETAILS\nCVEID:CVE-2016-8610 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8610]\nDESCRIPTION:SSL\/TLS protocol is vulnerable to a denial of service, caused by an error when processing ALERT packets during a SSL handshake. By sending specially-crafted packets, a remote attacker could exploit this vulnerability to cause the application to stop responding.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118296 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118296]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:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.6.1\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/First Fix IBM API Connect 5.0.0.0 - 5.0.6.1 LI79599 Apply IBM API Connect V5.0.6.2 or later [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] \nWORKAROUNDS AND MITIGATIONS\nNone","is_impossible":false,"contexts":[{"filename":"swg22002063.txt","text":"Title: IBM Security Bulletin: Vulnerability identified in OpenSSL shipped with IBM API Connect (CVE-2016-8610) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n An SSL vulnerability was disclosed by the OpenSSL Project. IBM API Connect has addressed the applicable CVE. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-8610 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8610]\nDESCRIPTION:SSL\/TLS protocol is vulnerable to a denial of service, caused by an error when processing ALERT packets during a SSL handshake. By sending specially-crafted packets, a remote attacker could exploit this vulnerability to cause the application to stop responding.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118296 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118296]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:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM API Connect V5.0.0.0 - V5.0.6.1\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/First Fix IBM API Connect 5.0.0.0 - 5.0.6.1 LI79599 Apply IBM API Connect V5.0.6.2 or later [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+API+Connect&release=5.0.6.2&platform=All&function=all] \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 04 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."}]},{"id":"DEV_Q090","question":"RTW eclipse license error\n\n I get a RTW eclipse license error on IM stating server is available, but license is not available. License is imported fine on license key admin and RPT floating license and RIT floating license shows on the pc end on license key admin 8.1.3, but not showing on IM. \n\nRTW 8.5\n\nWhat to do? ","answer":"Navigate to IBM Rational License Key Center [http:\/\/www-01.ibm.com\/software\/rational\/support\/licensing\/] website. \n \n \n \n 2. Return and generate the license [https:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg21308308] file for IBM Rational Test Workbench Floating License. \n \n \n \n 3. Download and Import the license file again.\n \n \n \n 4. Click on Start > IBM Rational > LMTools > Start\/Stop\/Reread tab to stop and start the license server.\n \n \n \n 5. Next, click on Start > IBM Rational > LMTools > Server Status to perform status enquiry and look for 'Users of ibmrit' line.\n \n \n \n 6. Reactivate [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21403623] the floating license for Rational Integration Tester using Rational Installation Manager.","is_impossible":false,"contexts":[{"filename":"swg21608473.txt","text":"Title: IBM Configuring floating license for Rational Integration Tester results in a warning 'The server is available, but does not serve license keys for IBM Rational Integration Tester' - United States\n\nText:\nRational Integration Tester; License error; Users of ibmrit; PACKAGE ibmrtw ibmratl COMPONENTS=\"ibmrit ibmrft ibmrpt ibmrpt_pvu; The server is available; but does not serve license keys for IBM Rational Integration Tester TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to configure the floating license for IBM Rational Integration Tester using IBM Installation Manager leads to the warning 'The server is available, but does not serve license keys for IBM Rational Integration Tester'. \n\nSYMPTOM\nSteps to reproduce:\n\n\n 1. In Rational Integration Tester client, Click on Start > IBM Installation Manager > Manage Licenses.\n \n \n \n 2. Highlight Rational Integration Tester from the List of Installed Products.\n \n \n \n 3. Configure floating license support [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21403623] for Rational Integration Tester.\n \n \n \n 4. Clicking on \"Test Connection\" results in the below message:\n -------------------\n 'The server is available, but does not serve license keys for IBM Rational Integration Tester'.\n -------------------\n\n\nCAUSE\nThe PACKAGE ibmrtw block (as shown below) is missing which displays the components of IBM Rational Test Workbench Suite. \n-------------------\nPACKAGE ibmrtw ibmratl COMPONENTS=\"ibmrit ibmrft ibmrpt ibmrpt_pvu\"\n-------------------\n\n\nDIAGNOSING THE PROBLEM\nOn the license server, launch Rational License Key Administrator. \n\n\n\n\n 1. Verify if there are 5 lines of 'IBM Rational Test Workbench License' key served by the license server as shown below:\n [\/support\/docview.wss?uid=swg21608473&aid=1] [\/support\/docview.wss?uid=swg21608473&aid=1]\n \n \n \n 2. If the lines are not displayed, perform a status enquiry by clicking on Start> IBM Rational> LMTools > Server Status. \n \n \n \n 3. If the line 'Users of ibmrit' is missing, follow the steps below to resolve the problem. \n\nRESOLVING THE PROBLEM\nSteps to resolve: \n\n 1. Navigate to IBM Rational License Key Center [http:\/\/www-01.ibm.com\/software\/rational\/support\/licensing\/] website. \n \n \n \n 2. Return and generate the license [https:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg21308308] file for IBM Rational Test Workbench Floating License. \n \n \n \n 3. Download and Import the license file again.\n \n \n \n 4. Click on Start > IBM Rational > LMTools > Start\/Stop\/Reread tab to stop and start the license server.\n \n \n \n 5. Next, click on Start > IBM Rational > LMTools > Server Status to perform status enquiry and look for 'Users of ibmrit' line.\n \n \n \n 6. Reactivate [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21403623] the floating license for Rational Integration Tester using Rational Installation Manager.\n\nRELATED INFORMATION\n#License Requirements for Rational Integration Tester [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21605379]\nA simplified Chinese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21674212]"}]},{"id":"DEV_Q091","question":"Deploying RuleRunner on a separate server\n\n\n\nHello everyone,\n\nI am trying to have a setup as follows:\n\nServer 1: Running Full Datacap Features\nServer 2: Running only the RuleRunner service\n\nI managed to deploy Server 1 successfully and all modules are working.\n\nOn Server 2, I installed the following:\nDatacap Client, Rulerunner, and connectors\n\nI updated the Application Manager on server 2 to point to \\\\server1\\Datacap\\datacap.xml\n\nI can successfully open that path from Server 2 using internet explorer.\n\nWhen I try to open any application such as TravelDocs using Datacap Deskstop from server 2, I receive the following error:\n\nUnable to connect to Datacap application TravelDocs.\n\nAny hints as to what the issue might be ?\n\nRegards\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q092","question":"What versions of WSAS using Oracle 12c are supported?\n\nWhat versions of WSAS using Oracle 12c are supported?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q093","question":"How do I run the prerequisite scan for jazzSM?\n\nHow do I run the prerequisite scan? ","answer":"In this particular case, in order to properly run the prerequisite scanner, the codes for DASH and JazzSM should be passed like this: \n\n * \n * \n * \n\n\nThe above will provide a detailed","is_impossible":false,"contexts":[{"filename":"swg21696179.txt","text":"Title: IBM JAZZ 1.1.0.3 for WebGUI (Pre-Req) not installing. - United States\n\nText:\nTIPL2INST; DASHL2INST; CRIMA1217E; prereq_checker.bat; prereq_checker.bat TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Installation of Dashboard Application Service Hub (DASH) and Jazz for Service Management (JazzSM) components is failing even though the installation prerequisite scan apparently passed. \n\nCAUSE\nUpon further investigation, it was discovered the customer had only used the product code for DASH during prerequisite scan. \n\nDIAGNOSING THE PROBLEM\nDuring installation the following error is seen in the GUI installation window and logs: \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 * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nThe above error typically means there is not enough room on the system for software to deploy and the installation to complete successfully. \nRESOLVING THE PROBLEM\nIn order to accurately determine if the installation prerequisites have been met, the user must pass both product codes to the prerequisite scanner. In this case, the user must pass the codes for DASH and Jazz simultaneously to the prerequisite scanner script. \n\nThe following table contains the product codes for the various integration services:\n[\/support\/docview.wss?uid=swg21696179&aid=1] [\/support\/docview.wss?uid=swg21696179&aid=1] \n\nIn this particular case, in order to properly run the prerequisite scanner, the codes for DASH and JazzSM should be passed like this: \n\n * \n * \n * \n\n\nThe above will provide a detailed listing of the prerequisites for both products along with which items have passed and which items have failed and need to be addressed before the installation will succeed."}]},{"id":"DEV_Q094","question":"How do I upgrade my virtual DataPower Appliance from 5.0 firmware to 6.0+ firmware?\n\nWhen 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":"","is_impossible":false,"contexts":[{"filename":"swg21638268.txt","text":"Title: IBM Supported Upgrade and Downgrade paths for DataPower Virtual Edition - United States\n\nText:\n 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"}]},{"id":"DEV_Q095","question":"Why do I get error when I try to save application in APMUI?\n\nI am using APMUI 7.7 IF1. Following error occurs when I try to save application:\n\n \n\nCTGAZ0001E: The application cannot be saved because the application repository is not available.\nmessages.log of scr server shows that it is listening at 17310 port:\n\n \n\nA CWWKT0016I: Web application available (default_host): http:\/\/apmhost:17310\/SCRCLUSTER_SCR_oslc.html\nBut apmui is referring to this URL with port 8080 (APM_UI.log):\n\n \n\nhttp:\/\/apmhost:8080\/SCRCLUSTER_SCR_oslc\/scr\/gettime","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q096","question":"I am using persistent messages, but I never got the messages\n\nI am using persistent messages, but I never got the messages. How can I determine what happen to the messages?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q097","question":"Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089)\n\nI need to understand details regarding Security Bulletin: MQ Explorer directory created with owner '555' on Linux x86-64 vulnerability affects IBM MQ (CVE-2016-6089). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q098","question":"Help with Security Bulletin: Multiple Vulnerabilities identified in IBM Java SDK affect WSRR and WSRR Studio\n\n\n\nI need to understand details regarding Security Bulletin: Multiple Vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio.\n\nThis is related to CVEID:\nCVE-2018-2633\n\nWhere can I find this information?","answer":"CVEID:CVE-2018-2633 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H)","is_impossible":false,"contexts":[{"filename":"swg22013955.txt","text":"Title: IBM Security Bulletin: Multiple Vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 6 used by WebSphere Service Registry and Repository and WebSphere Service Registry and Repository Studio. These issues were disclosed as part of the IBM Java SDK updates in January 2018.\n\nThese issues are also addressed by WebSphere Application Server Network Deployment shipped with WebSphere Service Registry and Repository. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2018-2633 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2633]\nDESCRIPTION:An unspecified vulnerability related to the Java SE JNDI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137885]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H) \nCVEID:CVE-2018-2603 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2603]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137855 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137855]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\nCVEID:CVE-2018-2579 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2579]\nDESCRIPTION:An unspecified vulnerability related to the Java SE Libraries component could allow an unauthenticated attacker to obtain sensitive information resulting in a low confidentiality impact using unknown attack vectors.\nCVSS Base Score: 3.7\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137833 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137833]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:U\/C:L\/I:N\/A:N) \n\nCVEID:CVE-2018-2602 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2018-2602]\nDESCRIPTION:An unspecified vulnerability related to the Java SE I18n component could allow an unauthenticated attacker to cause low confidentiality impact, low integrity impact, and low availability impact.\nCVSS Base Score: 4.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137854 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/137854]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:R\/S:U\/C:L\/I:L\/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\nWebSphere Service Registry and Repository V8.5 and V8.0 and WebSphere Service Registry and Repository Studio V8.5 are affected.\n\nREMEDIATION\/FIXES\nFor all releases of WebSphere Service Registry and Repository Studio, upgrade to WebSphere Service Registry and Repository Studio V8.5.6.1_IJ04332 [http:\/\/www.ibm.com\/support\/fixcentral\/quickorder?product=ibm%2FWebSphere%2FWebSphere+Service+Registry+and+Repository&fixids=8.5.6.1-WS-WSRR-Studio-MultiOS-IFIJ04332]\n\nFor WebSphere Service Registry and Repository the issues are addressed by WebSphere Application Server.\n\n\n\nPrincipal Product and Version(s) Affected Supporting Product and Version WebSphere Service Registry and Repository V8.5 WebSphere Application Server V8.5.5 WebSphere Service Registry and Repository V8.0 WebSphere Application Server V8.0 \nRefer to the following security bulletin for vulnerability details and information about fixes addressed by WebSphere Application Server shipped with WebSphere Service Registry and Repository: \n\nSecurity Bulletin: Multiple Vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server January 2018 CPU [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22013818] 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 14 March 2018: 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."}]},{"id":"DEV_Q099","question":"Is ITCAM Agent for WebSphere Applications 7.2.0.0.7 available?\n\nIs ITCAM Agent for WebSphere Applications 7.2.0.0.7 available? ","answer":"7.2.0.0.7 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0007&includeSupersedes=0&source=fc] 7.2.0.0.14 March 9, 2017","is_impossible":false,"contexts":[{"filename":"swg21652265.txt","text":"Title: IBM ITCAM Agent for WebSphere Applications V7.2 fixes - United States\n\nText:\n FIX README\n\nABSTRACT\n IBM Tivoli Composite Application Manager Agent for WebSphere Applications V7.2 fixes\n\n\nCONTENT\n\nInstallation Instructions \n\nRefer to the README file located in Fix Central for additional information \n\n\n\nDownload \nWhat is Fix Central? [http:\/\/www.ibm.com\/systems\/support\/fixes\/en\/fixcentral\/help\/faq_sw.html] Embedded DC RELEASE DATE APAR numbers 7.2.0.0.8 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0008&includeSupersedes=0&source=fc] 7.2.0.0.15 April 17, 2018 PI84591 7.2.0.0.7 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0007&includeSupersedes=0&source=fc] 7.2.0.0.14 March 9, 2017 IV85603 PI05433 PI67994 PI52132 PI52407 PI71243 PI22174 PI71124 PI22832 PI77911 7.2.0.0.6 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0006&includeSupersedes=0&source=fc] 7.2.0.0.13 May 6, 2016 PM92340 PI33522 PI47001 PI53858 PI00024 PI50832 PI48106 PI53964 PI41634 PI53691 PI52367 PI51119 PI57148 PI59839 PI42952 PI39907 PI42603 PI30133 PI35027 PI35893 PI34945 PI39525 PI43321 PI48106 PI53964 PI41634 PI53691 PI11450 PI16745 PI18682 PI21062 PI24319 PI25035 PI25663 PI27187 PI33891 PI34061 PI35680 PI36215 PI37162 PM70256 PM74078 PM75193 PM75581 PM87883 PM93570 IV47342 IV69645 7.2.0.0.5 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0005&includeSupersedes=0&source=fc] 7.2.0.0.10 Oct 8, 2014 PM98778 PI06311 PI07084 PI22743 PI08200 PM88373 PM99070 PM94101 IV47342 PI06761 PI08473 PI08257 7.2.0.0.4 7.2.0.0.9 This is Limited Availability Interim Fix. Please contact Customer Support to obtain this fix . 7.2.0.0.3 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0003&includeSupersedes=0&source=fc] 7.2.0.0.8 Oct 10, 2013 PM93570 7.2.0.0.2 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0002&includeSupersedes=0&source=fc] 7.2.0.0.7 Aug 23, 2013 7.2.0.0.1 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?product=ibm\/Tivoli\/Tivoli+Composite+Application+Manager+for+Applications&release=All&platform=All&function=fixId&fixids=7.2.0.0-TIV-ITCAMAD_WS-IF0001&includeSupersedes=0&source=fc] 7.2.0.0.5 Jul 17, 2013 PM81890; PM77662; PM79101; PM82318; PM80120; PM88932; PM76203"}]},{"id":"DEV_Q100","question":"ITCAM Agent for WebSphere DataPower 7.1 agent support for TLS\n\nDoes the ITCAM Agent for WebSphere DataPower 7.1 agent support TLS?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q101","question":"Help with Security Bulletin: WMB and IIB Toolkit cannot connect to a remote WMB broker or IIB node with a TLS-compliant cipher (CVE-2015-0118)\n\nI need to understand details regarding Security Bulletin: WebSphere Message Broker Toolkit and IBM Integration Toolkit cannot connect to a remote WebSphere Message Broker broker or IBM Integration Bus node with a TLS-compliant cipher (CVE-2015-0118). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q102","question":"Event Log Hashing - Performance?\n\nI'm curious how much performance is affected by hashing events and flows. I don't see that information in the admin guide for 7.3.1. Can someone list that out by algorithm?","answer":"The overhead of writing these files is negligible, regardless of the hashing method selected.","is_impossible":false,"contexts":[{"filename":"swg21965783.txt","text":"Title: IBM QRadar: Enabling On Event and Flow Hashing integrity checks with HMAC - United States\n\nText:\nHashing; QRadar; HMAC; integrity; hashed message authentication code; authentication TECHNOTE (FAQ)\n\nQUESTION\n What is the performance impact of using HMAC, and how does QRadar handle key management?\n\n\n\nANSWER\nThe overhead of writing these files is negligible, regardless of the hashing method selected. HMAC is no more expensive than the default options supported by QRadar previously. Once enabled the \nHMAC keys are added to new Events and Flows as they are written. When attempting to run the integrity check, it will take some time depending on the amount of data being validated. It will not cause performance issues, assuming the system is not at maximum load for disk input. \n\nFrom more information on HMAC please refer to the section Checking the Integrity of Event and Flow Logs in the QRadar Administration Guide.\n\nQRadar 7.3.0 Administration Guide [http:\/\/public.dhe.ibm.com\/software\/security\/products\/qradar\/documents\/7.3.0\/en\/b_qradar_admin_guide.pdf] \n\nQRadar 7.2.8 Administration Guide [http:\/\/public.dhe.ibm.com\/software\/security\/products\/qradar\/documents\/7.2.8\/en\/b_qradar_admin_guide.pdf] \n\n \n\n \n\nWhere do you find more information? \n\n\n\n\n[\/support\/docview.wss?uid=swg21965783&aid=1] [http:\/\/ibm.biz\/QRadar-KC] [\/support\/docview.wss?uid=swg21965783&aid=2] [https:\/\/ibm.biz\/qradarforums] [\/support\/docview.wss?uid=swg21965783&aid=3] [http:\/\/ibm.biz\/qradarknowledge] [\/support\/docview.wss?uid=swg21965783&aid=4] [http:\/\/ibm.biz\/SecSuptUTube] [\/support\/docview.wss?uid=swg21965783&aid=5] [http:\/\/ibm.biz\/qradarsoftware] [\/support\/docview.wss?uid=swg21965783&aid=6] [http:\/\/ibm.biz\/MyNotification] [\/support\/docview.wss?uid=swg21965783&aid=7] [http:\/\/ibm.biz\/SuptRegQuikStart]"}]},{"id":"DEV_Q103","question":"How to resolve SessionBeanTimeoutException in WebSphere Application Server?\n\nIn one of my j2EE-applications I get com.ibm.ejs.container.SessionBeanTimeoutExceptions with the following caused by section:\nCaused by: com.ibm.ejs.container.SessionBeanTimeoutException: Stateful bean CMStatefulBeanO(BeanId(server1# mySessionBean.jar# StdEJBReader, A5667152-014B-4000-E000-9AD20A8E643B), state = METHOD_READY) timed out ... 26 more\nDo you know how to resolve such SessionBeanTimeoutExceptions in general?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q104","question":"Java plugin not loading into rhapsody\n\nI had installed rational rhapsody 8.2 in my machine. I tried to add the profile of the Simple plugin.sbs from the path C:\\ProgramData\\IBM\\Rational\\Rhapsody\\8.2\\Samples\\ExtensibilitySamples\\Simple Plug-in, finally it is found that the Simple plugin is failed to load in the Rhapsody process space.\nI had tried to add the JavaAPILogFile=D:\\RhapsodyLogFile\\Logs.txt for collecting the logs and while loading plugin nothing is written into the log file.\n\nWhen i launched the rhapsody the following is written into the logs\n\nEnter: RhapsodyAppServer_attachToRhapsodyApplication\nEnter: RPApplication_getTheJavaPluginsInterfaceNative\nExit: RPApplication_getTheJavaPluginsInterfaceNative\n\n \n\nPlease help me to resolve this issue ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q105","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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\nThis is related to CVEIDs:\nCVE-2018-1000001\nCVE-2017-16997\nCVE-2017-1000408\nCVE-2017-1000409\nCVE-2017-17426\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q106","question":"Why does WebSphere DataPower spike with a high CPU rate when a WebSphere MQ connection is unavailable?\n\nI have noticed when my MQ backends go down unexpectedly it can result in a high CPU rate on DataPower. And how can I resolve this? ","answer":"The solution to the issue of having DataPower vulnerable to the MQ Queue Manager being inaccessible is to change the Retry Attempts parameter on the Configure MQ Queue Manager window from 0 to some number.","is_impossible":false,"contexts":[{"filename":"swg21431301.txt","text":"Title: IBM WebSphere DataPower spikes with high CPU when WebSphere MQ connection is unavailable - United States\n\nText:\nretries; high CPU; MQ queue manager; Retry Interval; Retry Attempts; Long Retry Interval TECHNOTE (FAQ)\n\nQUESTION\n Why does WebSphere DataPower spike with a high CPU rate when a WebSphere MQ connection is unavailable? Is there a solution to this issue? \n\nCAUSE\nIf the value of Retry Attempts is set to 0 on the DataPower MQ Queue Manager object, this negates the benefits of the Long Retry Interval since it will not be used. DataPower will retry forever using the specified Retry Interval. The default setting of Retry Attempts as 0 and Retry Interval as 1 second is provided to preserve backward compatibility. However, these default values should be changed to take advantage of Long Retry Interval feature available in firmware.\n\nANSWER\nThe solution to the issue of having DataPower vulnerable to the MQ Queue Manager being inaccessible is to change the Retry Attempts parameter on the Configure MQ Queue Manager window from 0 to some number. As an example, change the parameters as follows: \n\n * Retry Attempts - change the default of 0 to 6 Retry Interval - change the default of 1 to 10 seconds Long Retry Interval - change the default of 1800 to 600 seconds (10 minutes) \n\n\nIn the event that the Queue Manager is down or a connection is not established, the above example configuration will allow the MQ QM Object to retry 6 times with 10 second intervals. After 6 attempts, the MQ QM object will retry every 10 minutes. \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration WebSphere DataPower Integration Appliance XI50 Firmware 3.8 Business Integration WebSphere DataPower Low Latency Appliance XM70 Firmware 3.8"}]},{"id":"DEV_Q107","question":"Why the exception \"BO Service is not supported or disabled in this profile\" when trying to publish from IID to a local Process Server?\n\nWhen trying to publish a project from IBM Integration Designer (IID) to the local Process Server, it fails with error ADMA5014E in SystemOut.log. The FFDC log is showing exception of BO Service is not supported or disabled in this profile; Trace:\n\nFFDC Exception:java.lang.ExceptionInInitializerError SourceId:com.ibm.ws.bpm.cmdfrmwrk.task.WBICleanupTask ProbeId:200 java.lang.ExceptionInInitializerError at java.lang.J9VMInternals.initialize(J9VMInternals.java:259) \n....\nCaused by: java.lang.IllegalStateException: BO Service is not supported or disabled in this profile. at com.ibm.ws.bo.BOCore.init(BOCore.java:107) ....","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q108","question":"Why do I get \"OSS version is not suitable for installation\" when attempting to install the MQ 5.3.1 base version on a HP Integrity NonStop Server BladeSystem?\n\nI am trying to install the MQ 5.3.1 base version on a HP Integrity NonStop Server BladeSystem, but it complains saying that the \"OSS version is not suitable for installation\". My OSS version is J06.14 and it looks to be a supported version according to the System Requirements site:\n\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27006797\n\nWhy am I getting this error message?","answer":"For the HP Integrity NonStop Server H-Series systems, the following system\nsoftware versions are the minimum mandatory level for V5.3.1.12:\n\n- H06.23.01 or later","is_impossible":false,"contexts":[{"filename":"swg27048240.txt","text":"Title: IBM Readme for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12 - United States\n\nText:\n PRODUCT README\n\nABSTRACT\n This readme provides information for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12. \n\nCONTENT\nDESCRIPTION\n\n\n============\n\nThis file describes product limitations and known problems.\nThe latest version of this file can be found here:\nhttps:\/\/ibm.biz\/mqreadmes [https:\/\/ibm.biz\/mqreadmes]\n\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\nUPDATE HISTORY\n20 May 2016 - Updates for IBM WebSphere MQ for HP NonStop Server, Version 5.3.1, Fix Pack 12\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n--------------------------------------------------------------------\nCONTENTS\n========\n\nIntroduction\nAbout this release\nInstallation, migration, upgrade and configuration information\nUn-installation information\nKnown limitations, problems and workarounds\nDocumentation updates\nContacting IBM software support\nNotices and Trademarks\n\nINTRODUCTION\n============\n\nWelcome to IBM(R) WebSphere(R) MQ for HP NonStop Server, Version 5.3.1.12\n\nThis release notes file applies to the latest WebSphere MQ cross-platform\nbooks (for Version 5.3), and to the WebSphere MQ for HP NonStop Server,\nVersion 5.3 specific books (WebSphere MQ for HP NonStop Server System\nAdministration Guide and WebSphere MQ for HP NonStop Server Quick\nBeginnings).\n\nThe content of these release notes applies to the WebSphere MQ for HP\nNonStop Server product unless otherwise stated.\n\nThis release notes file contains information that was not available in\ntime for our publications. In addition to this file, README,\nyou can find more information on the WebSphere MQ Web site:\n\nhttp:\/\/www.ibm.com\/software\/integration\/wmq\/ [http:\/\/www.ibm.com\/software\/integration\/wmq\/]\n\nFor current information on known problems and available fixes,\nSupportPacs(TM), product documentation and online versions of this and\nother readme files see the Support page of the WebSphere MQ Web site at:\n\nhttp:\/\/www.ibm.com\/software\/integration\/wmq\/support [http:\/\/www.ibm.com\/software\/integration\/wmq\/support]\n\nABOUT THIS RELEASE\n==================\n\nNomenclature\n------------\nThe terms \"WMQ V5.3.1\" and \"WMQ V5.3.1.0\" both refer to the same WMQ Refresh\nPack without subsequent service installed. Throughout this readme, references\nto \"WMQ V5.3.1.x\" refer to WMQ 5.3.1 with or without subsequent service\ninstalled.\n\nNew in this release\n-------------------\n\nThis is the twelfth FixPack for IBM WebSphere MQ V5.3.1 for HP NonStop Server,\nand is designated V5.3.1.12, with associated APAR IT15471.\n\nThis release is cumulative for all service and internal defect correction \nperformed since WMQ 5.3.1 was released. \n\nAll native object and executable files distributed with this FixPack have the\nfollowing version procedure strings:\n\nT0085H06_31MAY2016_V53_1_12_<buildid> (Where buildid is the internal build\nidentifier)\n\nThe Non-native library distributed with this FixPack has the following \nversion procedure string:\n\nT0085H06_28FEB2015_V53_1_11 \n\nIf upgrading from V5.3.1.5 or later releases, this FixPack does NOT require \nTNS (non-native) applications to be re-bound with the MQI library. More on \nthis is described later on in this readme.\n\nIBM have not identified any new HP NonStop Server system software problems\nsince V5.3.1.6 was released. The current set of recommended solutions is \ndescribed later on in this readme.\n\nIBM recommends that you ensure that your HP NonStop Server system software\nproducts are at SPR levels that incorporate these fixes (solutions) as a\npreventive measure. IBM has tested WMQ with these fixes in our own\nenvironment before making the recommendations.\n\nImportant note about SSL channels\n---------------------------------\n\nThis release includes a new version of openSSL (1.0.2h) to maintain currency\nwith known vulnerabilities discovered since the version shipped with V5.3.1.\nA new version of the SSLupdate.pdf document was provided with the V5.3.1.10\nfixpack, and is also included with this this release, located in the \n<install_path>\/opt\/mqm\/READMES\/en_US directory. If you use SSL channels you\nshould review the revised version of SSLupdate.pdf prior to installing this\nfixpack.\n\nThe following SSL information applies if you are upgrading from WMQ V5.3.1 and\nare using SSL channels. The following procedure is not required if you have \nalready installed WMQ V5.3.1.1\n\nSeveral of the fixes in this and previous FixPacks that relate to SSL channels\nchange the way that SSL certificates are configured with WebSphere MQ. If\nyou use SSL channels you will need to review the new documentation supplement\nSSLupdate.pdf for information about this change and make configuration changes\nPlease also see the Post-installation section below for a summary of the\nrequired changes.\n\nIn V5.3.1.10 Patch1 and all later releases, CipherSpecs that use the SSLv3\nprotocol were deprecated. Continued use of SSLv3 CipherSpec's is not recommended\nbut may be enabled by setting the AMQ_SSL_V3_ENABLE environment variable.\nIn addition to that Env01=AMQ_SSL_V3_ENABLE=1 has to be added to the MCA stanza \nof the queue manager's qmproc.ini file.\n\nWith OpenSSL 1.0.2h the following CipherSpecs have been deprecated:\nDES_SHA_EXPORT1024\nRC4_56_SHA_EXPORT1024\nRC4_MD5_EXPORT\nRC2_MD5_EXPORT\nDES_SHA_EXPORT\nTLS_RSA_WITH_DES_CBC_SHA\n\nWhile WMQ V5.3.1.12 does still support these weak CipherSpecs for compatibility\nreasons, they are deemed as not secure and should not be used. \n\nPlease check product documentation to confirm the CipherSpec is valid and consult\ndocumentation for any instructions when adding new environment variables.\n\n\nImportant note about WebSphere MQ V5.3 classes for Java and JMS\n---------------------------------------------------------------\n\nFixpack V5.3.1.10 resolved an incompatibility between NonStop Java 7 and the\nWMQ product libraries - that fix is also included in V5.3.1.12.\nThe method used to configure Java in V5.3.1.10 and later differs from \nthat in releases prior to V5.3.1.10. The Java.pdf document shipped in the \n<install_path>\/opt\/mqm\/READMES\/en_US directory was updated to reflect the\nchange. Java\/JMS users migrating from versions prior to 5.3.1.10 should \nreview the updated document.\n\nImportant note about instmqm for V5.3.1\n---------------------------------------\n\nSince FixPack V5.3.1.5, IBM provided a modified WebSphere MQ product\ninstallation script, instmqm, for any level of V5.3.1. The new installation\nscript includes a workaround for the OS problem introduced in G06.29\/H06.06\nwhere the OSS 'cp' command creates Guardian files in Format-2 form during an\ninstallation rather than Format-1. This change caused problems binding and\ncompiling non-native and native COBOL applications, as well as wasting a lot of\ndisk space because of the very large default extents settings for the Format-2\nfiles created by OSS cp.\n\nInstmqm has been modified in FixPack V5.3.1.5 to work around this change in OSS\ncp by forcing all Guardian files in an installation to be created as Format-1.\nThe use of the new installation script is recommended for all new V5.3.1\ninstallations.\n\nExisting installations that are not affected by the application relink or\nrebind problems can remain as they are.\n\nProduct fix history\n-------------------\n\nThe following problems are resolved in FixPack V5.3.1.12:\n\nAPAR IT08589 - WebSphere MQ V6 or V7 queues become \"missing\" from clusters. Application\ncalls to MQOPEN (sometimes MQPUT1, MQPUT) suffer queue name lookup\nerrors (Examples: 2085, 2082) when they try to access the affected \ncluster queues. \n\nAPAR IT10388 - When the receiving QMgr has its channel set with SSLCAUTH(OPTIONAL),\nthe Nonstop Queue Manager insists on sending a certificate to \nidentify itself. The remote side, however, does not require one\n\nAPAR IT11557 - Updated OpenSSL library to version 1.0.2h. This update deprecates sslchiph \ncipherspec TLS_RSA_WITH_DES_CBC_SHA and fixes various security \nvulnerabilities.\n\nAPAR IT12856 - When a node is removed from an MQ cluster and there is an automatically\ndefined cluster sender channel from a MQ node on NonStop to the removed\nnode, the sender channel on NonStop can go into state INITIALIZING and\nstay there for up to 60 minutes instead of being deleted after the first\nretry interval has expired.\n\nAPAR IT12875 - When a message is put into a remote\/cluster queue within a TMF user\ntransaction and while the corresponding transmit queue is empty or almost\nempty, it can take up to 60 seconds after the end of the transaction\nuntil the message is transmitted. As a side effect automatic channel \nstarts can also be delayed.\n\nAPAR IT12894 - Java 7 SSL clients behave differently than previous versions which \nresulted in an RC 2009 error on its connection attempt. This\nis fixed with V.5.3.1.12.\n\nAPAR IT14169 - When a CPU is stopped, some sender channels were not recovered \nand stayed in inactive state. \n\nAPAR IT15316 - Memory allocation during MCA and LQMA creation and initialization was\nnot handled properly and may result in an unresponsive system.\n\nAPAR IT15317 - Under some conditions agents stay alive but don't accept new\nconnections. That is the case if an agent has reached the maximum \nnumber of connections it is allowed to handle during its lifetime\nbut the agent can't terminate before the last connection has been \nclosed.\n\nAPAR IT15490 - A configured process name rule has not been applied because it \nwas defined with lower case characters, while the operating \nsystem interface delivered upper case process names. Since the name\ncomparison then fails the configuration is not applied.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.12:\n\nIN000100 - The CRTMQM command may fail with error 1017 if queue managers are \ncreated in parallel.\n\nIN000101 - The installer has been enhanced to properly support SMF virtual disks\nif the system revision is on H06.26 and newer or J06.15 and newer.\n\nIN000102 - Removed access to uninitialized memory within mqconn which may result in\nRC 2059 MQRC_Q_MGR_NOT_AVAILABLE.\n\n\nFixes introduced in previous fixpacks\n=====================================\nThe following problems were resolved in FixPack V5.3.1.11:\n\nAPAR IT03572 - In V5.3.1.10, the dspmqver -V command displays the string \n\"VPROC\" rather than the VPROC string encoded in the product.\nV5.3.1.11 corrects this problem.\n\nAPAR IT04083 - Error 30 received by Queue Server in a complex Queue Manager \nconfiguration using MQGMO_SET_SIGNAL. This is a result of\nthe limit on the number of outstanding messages sent by the \nprocess not being set to the same value as the internal counter.\nThis results in the Queue Server reporting \"Guardian error 30 \nattempting to send signal notification\" in the queue manager \nerror log.\n\nAPAR IT04533 - Cluster sender channels fail to start following a CPU failure\non a 2 CPU system when the Repository Manager and Channel Server\nare both in the same CPU. Following the CPU failure, the Queue\nManager error log repeatedly reports message AMQ9422 \n\"Repository manager error, RC=545284114\" \n\nAPAR IT04876 - Some ssl channels with mismatched sslchiph cipherspecs run \nsuccessfully because protocol versions are not compared. \n\nAPAR IT05353 - Mitigation for SSLV3 POODLE Attack - CVE-2014-3566 \n\nAPAR IT07330 - WebSphere MQ V5.3.X Process does not write FDC (First \nFailure Symptom Report) records when the current FDC file is\nphysically full. This can result in processes experiencing error\nconditions, but the error condition not being reported in the \nFDC file. This fix changes the error handling to identify this\nscenario and switch to a new FDC file with an incremented \nsequence number \n\nAPAR IV19854 - The master repository manager in a partial repository \nunnecessarily subscribes to each cluster queue manager that\nit is aware of. This causes a significant increase in the number\nof subscriptions that are made, and in large clusters this can\ncause performance problems. \n\nAPAR IY87702 - SIGSEGV resulting from failed getpwnam. In some circumstances\ngetpwnam can return a success value in errno, but a null\npointer as the user record. This results in a SIGSEGV from \namqoamd. This change adds a check for this condition and handles\nit correctly. \n\nAPAR IY91357 - Altering a channel definition unintentionally resets the \nSSLPEER() attribute for the channel. \nWhen a channel with SSLPEER information is modified to include\neither MSGEXIT or MSGDATA attributes, the SSLPEER attribute \nbecomes blank. V5.3.1.11 resolves this problem. \n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.11:\n\n909 - In the GA release, the TFILE was opened with depth 100 in the\nGuardian NonStop process pairs. In configurations with large\nlarge numbers of connecting applications\/threads, this could\nresult in probe QS270000 errors from nspPrimary, with an Arith1\nvalue of 83 (0083 Attempt to begin more concurrent transactions \nthan can be handled). This change increases the TFILE open depth\nto 1000. The default value can be changed from 1000 to a value\nbetween 100 and 1000 using MQTFILEDEPTH environment variable.\nIf a value < 100 or > 1000 is specified, a value of 100 will\nbe used, and an FDC will be reported with the text\n\"Invalid MQTFILEDEPTH specified - using default\"\n\n1380 - In the cra library, several FFST code sites report an error \nwithout reporting the name of the channel involved in the error\ncondition. This change adds the channel name to the FFST report\nin cases where the channel name is available to the calling code\n\n1471 - In earlier releases of 5.3.1, if a garbage argument string is \nsupplied to dspmqfls, the command abends rather than reporting a\nusage message. V5.3.1.11 resolves this problem\n\n1597 - In earlier releases of 5.3.1, the dspmqfls output shows a \nQueue\/Status server value. Status servers were part of the V5.1\narchitecture but are not present in 5.3.1. V5.3.1.11 changes the \nmessage to reflect the fact that all objects are now managed by\nQueue Servers.\n\n2230 - In earlier releases of 5.3.1, the runmqsc command \n\"DISPLAY QSTATUS(*) TYPE(HANDLE) ALL\" does not cleanly handle a\nscenario where there are more than 500 handles. Attempts to use\nthe command when there are more than 500 handles to be returned\nresults in FFSTs with probe NS013000 from nspReply, and probe\nQS264002 from qslHandleHandleStatus. See later section on\n\"KNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\"\n\n4158 - Slow memory leak in MQDISC in non-native library. In prior\nreleases, the non-native implementation of MQDISC contained a\nslow memory leak. This resulted in applications performing \nrepeated MQCONN\/MQDISC operations during the process lifetime\neventually receiving a MQRC_STORAGE_NOT_AVAILABLE error from\nMQCONN, and an FFST for probe ZS219001 from zstInsertPCD. The\nproblem can also manifest as a probe XC130006 from \nxehExceptionHandler inside an MQOPEN call.\n\n4395 - If memory allocation for internal working storage fails during\nan attempt to create a dynamic queue, the LQMA assoicated with\nthe operation will ABEND, rather than returning a completion\ncode of 2071 (MQRC_STORAGE_NOT_AVAILABLE). This change resolves\nthe problem.\n\n4421 - If an attempt to start an OAM server detects an existing OAM\nserver in the CPU, in prior releases, the FFST generated did not\ninclude the process name. This change amends the FFST to\ninclude the process name of the offending process, where that\nname can be determined. \n\n4428 - The altmqfls command \"resetmeasure\" was incorrectly documented\nin the original version of the SysAdmin guide. See later section\n\"DOCUMENTATION UPDATES\"\n\n4496 - In earlier versions of this readme file, the instructions on \nhow to reassign Queue Server for \nSYSTEM.CLUSTER.TRANSMISSION.QUEUE are incorrect. Refer to the\n\"KNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\" section for the\ncorrect procedure.\n\n4523 - If an OAM server attempts to start in a CPU, and there is \nalready an OAM server registered, prior to V5.3.1.11, the OAM\nsubsystem reported that there was a rogue process, but not\nthe name of the process. This change enhances the error\nreporting to report the name of the rogue process. \n\n4726 - Prior to this fixpack, the instmqm script did not check for\nsaveabend files and FFSTs generated during the validation\nphase of the installation. V5.3.1.11 adds this check.\n\n4774 - The cobol binding library, MQMCB, was shipped without symbols in\nFixPack V5.3.1.10, which causes applications to fail. V5.3.1.11\nresolves this issue. \n\n4800 - During instmqm, the script checks for the UNIX socket server.\nIn prior releases, in the event that this check failed, the\nerror message referred to the old UNIX socket server ($ZPMON).\nThis has been changed to refer to the new UNIX socket subsystem\n$ZLSnn, \"nn\" is the CPU number.\n\nAPAR IC85889 - UNEXPECTED IPC MESSAGES RECEIVED FOLLOWING PROCESS\nTERMINATION CAUSE EC TO ABEND REPEATEDLY\nIf a process sends an unexpected message to the MQECSVR\nprocess pair, the primary process will abend resulting in a\ntakeover by the backup process. The new primary process will\nthen abend. The only resolution is to restart the queue manager. \n\nAPAR IC87007 - PRIMARY QUEUE SERVER ABEND FOLLOWING TRANSACTION ABORT\nIn some circumstances, aborts of global units of work \ninvolving MQGETs of messages greater than 52k will result in an \nabend of the primary queue server responsible for the queue. \nThis renders the queue manager unresponsive \n\nAPAR IC87627 - WEBSPHERE MQ V5.3.1.8 FDC FILES DO NOT CONTAIN ENOUGH ERROR \nINFORMATION\n\nAPAR IC89128 - LISTENER FAILS TO START FOLLOWING UPGRADE TO \nHP J06.14\/H06.25 OR T9050J01-AWT\/T9050H02-AWS\nIn some configurations, the listener process will not run\nfollowing an upgrade to J06.14\/H06.25 or the installation of \nT9050J01-AWT\/T9050H02-AWS. The failure is dependent on the\nnumber of OSS processes running and their distribution between\nthe CPUs on the system. This problem also affects endmqlsr.\n\nAPAR IC89751 - CLUSSDR Channels do not restart without manual intervention\nafter CPU crash.\nIf a CLUSSDR or SDR channel is running in an MCA that is in the \nsame CPU as the Primary Channel Server, and that channel has \nbeen running for at least 5 minutes, and that CPU crashes, the \nchannel will not automatically restart. \n\nAPAR IC92511 - TERMINATION OF SLAVE REPOSITORY MANAGER RESULTS IN CLUSTER \nCHANNEL DELETION. In some cases this can result in a manually\nstopped cluster sender channel starting unexpectedly when they\nare dynamically recreated. \n\nAPAR IC92570 - MULTIPLE CLUSTER RECIEVER CHANNELS OR LONG RUNNING CLUSRCVR \nCHANNELS CAUSE METADATA FDC'S\n\nAPAR IC93289 - WEBSPHERE MQ R531 ON HP-NSS CLUSTER PUB SUB MESSAGES FAIL\nWITH AMQ9538 - COMMIT CONTROL ERROR \n\nAPAR IC94647 - Closing dynamic queues with MQCO_DELETE or MQCO_DELETE_PURGE\nwith an outstanding MQGET with signal results in multiple FDCs \nand an orphaned dynamic queue\n\nAPAR IC96947 - Backup Queue Server generates \"Open handle points to unused \nentry in default page\" FFST following LQMA termination \n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.10:\n\n4607 - Analyze lock logic in queue server takeover does not take account\nof temporary dynamic queues\n4679 - Exhaustion of message quickcell (MQC) space available to queue \nserver results in unstable queue manager\n4563 - RDF compatible message overflow file setting requires queue \nmanager restart \n4560 - Slave repository managers issue channel manipulation commands \nthat should be performed only by the master\n4557 - Write NonStop specific trace information to product standard \ntrace files rather than platform-specific file\n4556 - Internal Queue manager query array size can cause problems \nwith clusters containing more than 10 queue managers\n\n\nThe following problems were resolved in FixPack V5.3.1.9:\n\nAPAR IC51322 - CODE CHANGES FOR OPTIMIZATION OF DEFAULT CONVERSION\nDelay in processing seen during the default conversion between\nclient and server. The channel attempts normal conversion first,\nincluding attempting to load a conversion table before dropping\nthrough to the default conversion. Once default is required \nfor a specific set of code pages, this is now remembered \nand the attempt to perform normal conversion skipped.\n\nAPAR IY76799 - A FAILED CALL TO GETPEERNAME RESULTS IN A LEAKED SOCKET FILE\nWMQ amqrmppa (channel) process leaks a file descriptor in\nthe rare circumstance that a call to the getpeername function\nfails. Such a failed call is reported in the WMQ error logs for\nthe queue manager via an AMQ9213 message reporting that the\ngetpeername call has failed. The failure of\nthe getpeername call is the result of preoblems external to \nWMQ. This problem could also cause the WMQ listener process\n(runmqlsr) to run out of file descriptors, if there is\nno queue manager running, and lots of connections come in,\nwhilst these connections fail with getpeername problems.\n\nAPAR IY95706 - SIGSEGV IMMEDIATELY FOLLOWING RETURN FROM ZFUDOESOBJECTEXIST\nAn amqzlga0 process or amqrmppa process will raise an XC130004 \nFDC and the amqzlga0 process will end. The abrupt termination of\nthe amqzlga0\/amqrmppa process may cause channels or applications\nconnected to the queue manager to fail\n\nAPAR IZ06131 - RECOVER FROM SYSTEM.AUTH.DATA.QUEUE CORRUPTED BY USER ERROR\nApplications receive MQRC_NOT_AUTHORIZED (2035) error\nsetmqaut returns MQRC_UNKNOWN_OBJECT_NAME (2085) and fails to\nset new authorities. Records are missing from the \nSYSTEM.AUTH.DATA.QUEUE, determined by a mismatch between the \noutput from amqoamd -m -s, and the authorities that customers \nbelieve they have set for users and objects. This fix allows \nrecovery from this situation using setmqaut without the need \nto recreate the queue manager \n\nAPAR IC74903 - SSLPeer value slash (\/) causes SSL handshake to fail\nUsing slashes in the Distinguished Name name fields such as CN,\nO, OU, L, will fail SSLPEER value verification, and as such SSL\nHandshake, due to an MQ parsing error. MQ uses slashes (\/) to\ndelimit the distinguished name values when matching the SSLPEER\nvalue with the information contained in the certificate.\n\nAPAR IC82919 - xcsAllocateMemBlock returning xecS_E_NO_MEM\nQueue manager (receiver channel side) with API exits generate\nFDCs containing probe ZF137003 and error log entries for AMQ9518\nin the form of - File '\/mqs\/WMQtest\/var\/mqm\/@ipcc\/AMQRFCDA.DAT'\nnot found.\n\nAPAR IC80942 - Authority commands produced by amqoamd command is not usable if\nauthorization is \"+None\"\n\nUsing the setmqaut command with commands generated by amqoamd\nresults in a failure e.g\n\"setmqaut -m qmgrname -n name -t queue -g group +None\"\nreturns:\n\"AMQ7097: You gave an authorization specification that is not\nvalid.\"\n\nAPAR IC81429 - MQRC error 2003 received if an overflow file record is missing\nIf a portion of a message that should be stored the queue \noverflow file is missing, the generation of an FFST is \nsuppressed and a 2003 reason code is returned. All subsequent \nnon-specific MQGETs from the queue fail, since the partial \nmessage cannot be retrieved. \n\nAPAR IC81420 - Queue Server abend during simultaneous GET and BROWSE\nWhen a message larger than 56k is being browsed (MQGET with\none of the MQGMO_BROWSE_* options) from a client application \nusing message groups, and another process is simultaneously \nperforming a destructive MQGET on the same message. The primary\nqueue server terminates, and more or more of the following\nprobes are generated :QS003002, AO211001, AO200002, ZI074001,\nNS026006\n\nAPAR IC81367 - FixPack 5318 MQMCB Guardian library is not usable\nThe COBOL wrapper libraries were changed from type LINKFILE to\nDLL in the v5.3.1.8 Fixpack, and the packaging unintentionally\nstripped the symbols from the Guardian variant of the library\nZWMQBIN.MQMCB. During the link phase of a cobal program build\nthe following fatal error is encountered:\n\"Cannot use file specified in CONSULT or SEARCH directive\"\nProblem affects building in Guardian only.\n\nAPAR IC83299 - CPU Failure during mqget of persistent messages in global\nunit of work results in incorrectly deleted records in queue and\noverflow files\n\nIf a CPU fails where multiple applications are performing FIFO\nMQGETs from the same queue, and the following conditions are \ntrue:\n* The primary queue server is running in the failing CPU\n* Some (but not all) of the applications are running in the\nfailing CPU\n* None of the LQMAs are running in the failing CPU\n* The applications are using global units of work\n* Applications in the failing CPU have completed MQGET operations\nbut not committed the transactions\nThere is a failure window where an application not in the\nfailing CPU will remove an additional message record from the \nqueue file.\n\nAPAR IC83197 - Queue Server open handle management cannot handle backup\nrestart cases where handles from non-contiguous pages are \nsynced by the primary\n\nQueue servers with more than 3000 queue opens do not \ncorrectly handle a NonStop takeover. The queue manager becomes \nunresponsive and requires a restart to resolve the error \nsituation. When the queue server hangs, the backup queue server\nproduces a large number of FFST entries with the following \nprobe ids:\nQS165004 from qslSetHandle\nQS192007 from qslAddOpener\nQS190005 from qslHandleOpen\n\nAPAR IC83569 - Persistent Reference messages sent over a channel cause Commit \nControl Error\n\nWhen a persistent reference message is put to a queue, FFST's\nwith probe CS075003 are generated with the following error \ninformation\nMajor Errorcode :- rrcE_COMMIT_CONTROL_ERROR\nMinor Errorcode :- OK\nComment1 :- Error 2232 returned from lpiSPIHPNSSTxInfo\nIn addition, Sender channels will go into a retry state and\nqueue manager error logs will contain 'Commit Control' errors\n\nAPAR IC83699 - Cluster cache maintenance asynchronous time values result in\ncache content divergence\n\nRepository queue managers report FFST with probe RM527002\nfrom rrmHPNSSGetMetaPacket and Comment1 field \n\"Meta data mis-match Expected: metalen=4\". The problem \nresolved by this APAR is one of several possible causes of\nthese symptoms.\n\nAPAR IC83328 - Permanent dynamic queues are not deleted in some cases when\nMQCO_DELETE is used on MQCLOSE.\nPermanent dynamic queues are not deleted as expected after \ntermination of the last application that has the queue open.\n\nAPAR IC83228 - Repository manager\/Channel server deadlock\nListener process hangs on queue manager startup for 5 \nminutes then generates an FFST with probe RM264002 \nfrom rfxConnectCache\nComment1 :- Gave up waiting for cache to be initialized\nComment2 :- Tried 300 times at 1 second intervals. \nThis problem also occurs sometimes when attempting\nto use runmqsc while the queue manager is starting\n\nAPAR IY90524 - segv in xcsloadfunction for channel exit\nWebSphere MQ channel process (amqrmppa) terminates with FFST\nshowing probe id XC130003 due to a SIGSEGV SIGNAL with\na function stack as follows:\nMQM Function Stack\nccxResponder\nrrxResponder\nrriAcceptSess\nrriInitExits\nxcsLoadFunction\n\nAPAR IC81311 - MQGET implementation masks reason codes in some cases\nAttempting to perform an MQGET after a Local Queue Manager\nAgent (LQMA) process fails or has been forcibly terminated\nresults in a MQRC_UNEXPECTED_ERROR (2195). This is incorrect.\nThe result should be MQRC_CONNECTON_BROKEN (2009)\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.9:\n\n4363 - MQA process opener field is sometimes corrupted in MQGET with \nset signal operations\n4388 - Guardian sample uses the wrong link directive\n4339 - Shared hconn rendered unsuable by changes in 5317\n4123 - FASTPATH bound connect processing does not correctly set reason\ncodes in some cases\n4039 - Backup queue server abend during commit after MQGET\n3826 - altmqfls --qsize does not report failure correctly\n4116 - enhance SDCP to find installed version of OSSLS2 (T8620)\n\nThe following problems were resolved in FixPack V5.3.1.8:\n\nAPAR IC54121 - Cluster channel in a retrying state will no longer start \nautomatically if the following commands are issued \nSTOP CHANNEL() MODE(QUIESCE) STATUS(INACTIVE).\nThe channel will fail to start once communication\nto the remote system is restored. A manual start and\nstop of the channel is required to restore normal\nchannel operation\n\nAPAR IC54459 - Channel stays in binding state for a long time when it contains\nan invalid conname value. During this period, all requests to \nthe channel are ignored.\n\nAPAR IC60204 - Comamnd server experiences a memory leak when namelist\ninquireies are performed with names values.\nThe leak is observed when a PCF MQCMD_INQUIRE_NAMELIST or\nMQCMD_INQUIRE_NAMELIST_NAMES is requested that has one or \nmore names attributes.\n\nAPAR IC70168 - High CPU usage from backup Queue Server performing browse\noperations on queues with high queue depth.\nWhen a queue has a very high queue depth (CURDEPTH) a browse\ncan cause the cpu usage of the backup Queue Server to increase\nto 100%. Backup queue server CPU usage becomes significant at\na queue depth of 15000, with CPU use reaching 100% at a queue\ndepth of approx. 38000 messages.\n\nAPAR IC70947 - qmproc.ini file validation does not detect incorrect CPU syntax.\nCPU lists in the qmproc.ini file that do not use comma\ncharacters to separate CPU numbers in the list are ignored, but\nthey are not reported as an error. This can lead to unexpected\nCPU assignements for WMQ processes.\n\nAPAR IC71839 - RESET QUEUE STATISTICS PCF returns incorrect values.\nWhen using WebSphere MQ v5.3 for HP NonStop Server PCF command\nReset Queue Statistics, intermittently some of the values\nassociated with a queue will not be returned correctly.\n* HighQDepth - The maximum number of messages on the queue\nsince the statistics were last reset.\n(parameter identifier: MQIA_HIGH_Q_DEPTH).\n* MsgEnqCount - The number of messages enqueued (the number of\nMQPUT calls to the queue), since the\nstatistics were last reset.\n(parameter identifier: MQIA_MSG_ENQ_COUNT).\n* MsgDeqCount - The number of messages dequeued (the number of\nMQGET calls to the queue), since the\nstatistics were last reset.\n(parameter identifier: MQIA_MSG_DEQ_COUNT).\n\nIncorrect values may also be returned incorrectly for the\ncommand Inquire Queue Status\n* LastGetTime - Time at which the last message was\ndestructively read from the queue\n(parameter identifier: MQCACF_LAST_GET_TIME).\n* LastPutTime - Time at which the last message was\nsuccessfully put to the queue\n(parameter identifier: MQCACF_LAST_PUT_TIME).\n\nAPAR IC71912 - MQMC Channel menu display shows incorrect channel status.\nIn some instances, the MQMC Channel Menu display will not\nshow a change in channel status, and attempts to refresh the\nscreen or recycle the MQS-MQMSVR Pathway server do not correct\nthe problem. RUNMQSC continues to show the correct status. \nThe MQMC channel monitor panel does show the running channels\ncorrectly.\n\nAPAR IC73800 - A queue manager with the MaxUnthreadeAgents parameter defined\nin the QMPROC.INI file with a value greater than 812\nreports unexpected process termination FDCs and or ERROR 22\nFDCs.\n\nAPAR IC74994 - Queue manager reports message sequence number error and\nproduces FDCs with probe CS094005, major error code\nrrcE_CREATE_SYNC_FAILED following a queue manager\nrestart. \n\nAPAR IC75298 - In some complex cluster configuations with large numbers of\ncluster members, large numbers of objects, or frequent changes\nto cluster objects, the repository managers in a queue\nmanager are unable to distribute a complete set of object \nmetadata information, resulting in repeated FDCs from \nrrmHPNSSGetMetaPacket, with probe RM527001, and cluster objects\nnot being visible in some CPUs in the queue manager reporting the\nproblems.\n\nThe fix for the problem adds a new configurable parameter to\nallow the repository metadata buffers to be increased to handle\nlarger configurations, and changes the reporting of the metadata\nerrors to include information on the amount of storage requested\nby the repository managers. The default size of the buffer is \n512K, this is sufficient for most configurations. If the buffer \nsize is insufficient, the queue manager reports FDCs from \nrrmHPNSSPutMetaPacket that indicate the present size of the\nbuffer and the size demanded.\n\nThe buffer size is configured using an environment variable, \nAMQ_CLUSTER_METABUFFER_KILOBYTES. To change the value, the \nenvironment variable should be specified in the \n\"RepositoryManager\" stanza of the qmproc.ini file of the queue\nmanager using the following syntax:\n\nEnv0n=AMQ_CLUSTER_METABUFFER_KILOBYTES=x\n\nWhere \"n\" is the number of the environment variable, and \"x\" is\nthe required new size of the buffer in kilobytes. In a default\nconfiguration, environment variables are not present in the \nRepositoryManager stanza, hence \"n\" will be 1. If the \nconfiguration has existing environment variables specified in\nthis stanza, the value of \"n\" selected should be the next \navailable value. \n\nAPAR IC75356 - Partial repository queue managers in complex configurations\nwhere applications connected to the partial repository queue\nmanager attempt to open large numbers of nonexistant objects\ncan suffer from a build up of subscription objects on the \nSYSTEM.CLUSTER.REPOSITORY.QUEUE such that the TMF lock limits\nfor the volume containing the queue file are breached when the\nqueue is reconciled. This produces 2024 errors during operations\non the SYSTEM.CLUSTER.REPOSITORY.QUEUE The following error \nmessage appears in the QMgr error logs.\nEXPLANATION: The attempt to get messages from queue\n'SYSTEM.CLUSTER.REPOSITORY.QUEUE' on queue manager 'xxx' failed \n\nAPAR IY57123 - Attempts to put to a clustered queue via a queue manager\nalias when the queue has been opened using BIND_AS_QDEF\nfail. Following this fix, queue name resolution functions\nas described in the Application Programming Guide.\n\nAPAR IY78473 - Cluster workload management is not invoked if a queue is\nresolved using clustered queue manager aliases where there\nare multiple instances of the alias in the cluster.\n\nAPAR IY86606 - Cluster subscriptions are created for non-clustered queues\nwhen MQOPEN is called with non-clustered ReplyToQ or \nReplyToQMgr. This can result in a build up of subscriptions\nin partial repositories in the cluster. The error was \nintroduced by IY8473.\n\nAPAR IZ14977 - Queue manager cluster membership missing when namelists are\nused to add and remove queue managers from clusters. This can\nresult in the queue manager not acting as a repository for\none or more clusters, or other queue managers in the cluster\nnot recognizing that a given queue manager is a repository\nfor the cluster.\n\nAPAR IZ20546 - The repository manager process (amqrrmfa) consumes high CPU\nresources on an hourly basis for several minutes, and\napplications are unable to issue messaging MQ API calls\nduring this period. The problem is observed only in \nconfigurations where clustered queue manager aliases are\nused and they resolve to more than 50 destinations.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.8:\n\n1228 - COBOL Binding library mqmcb does not contain VPROC information\n1378 - FDC's cut as a result of errors from PATHWAY SPI operations do\nnot report the associated Guardian error code \n1566 - WMQ service installation tool svcmqm does not correctly detect\nand report that files it is attempting to modify are in use,\nas is the case where WMQ applications are still runnning. \n1606 - Certain FDCs containing comment text have the comment text\ntruncated \n1710 - In some cases on heavily loaded systems, the EC re-allocates\nan MCA that has already been told to terminate. This results in\nFDC's cut with probe EC134000, from eclDeallocMCA.\n2534 - WMQ service installation tool svcmqm does not log some aspects\nof its progress, making diagnosing some installation problems\ndifficult\n2856 - WMQ service installation tool should not attempt SECURE\noperations in installations where SAFEGUARD is enabled\n2943 - crtmqm does not correctly handle validation of the command line\nif a specified CPU number is invalid\n3037 - If the var\/mqm\/errors directory contains non-mqm user files \nthe WMQ service data collection tool, sdcp, does not capture the \nMQM group FDC and ZZSA files.\n3128 - WMQ Service data collection tool, sdcp, does not capture VPROC \nof the AF_UNIX R2 socket process\n\n\nThe following changes were released in FixPack V5.3.1.7:\n\nAPAR IC65774 - Under given conditions, the response time measured for MQGET\noperations when using SSL activated channels with multi-threaded\nMCA agents are found to be longer than that measured when using \nSSL activated channels with unthreaded MCA agents. This problem \nis seen with both distributed and cluster queue managers. \nMoreover, this problem does not occur prior to WMQ V5.3.1.5 \nrelease. A DELAY was introduced as part of an APAR(IC57744) fix\nin WMQ V5.3.1.5 release for mutli-threaded SSL channels which\ncaused this difference in measured response time. The problem is\nnow rectified in this release. \n\nAPAR IC67032 - Improvement to LQMA FDC during MQCONN processing. At times, when\napplication dies during MQCONN processing, LQMA's generate FDCs\nfor this rather unusual event to let the user take any \ncorrective action and\/or find the root cause. The problem can \noccur with a standard bound application in a very narrow timing\nwindow when the application connects with the LQMA agent but \ndies before the LQMA gets a chance to read the incoming message\nfrom the application. When LQMA detects this situation, it \ncleans up and generates an FDC. But unfortunately, the FDC does\nnot contain the application information. To let the user \nidentify the mis-behaving application and to possibly take\ncorrective action, LQMA FDC will be updated to include \napplication information. The updated FDC will contain the\nfollowing information :\n\nComment1 :- Application died during MQCONN Processing.\nComment2 :- Application: <Application PID> \n\nAPAR IC67057 - Unused LQMA agents(processes or threads) are found during MQCONN \nprocessing. During MQCONN processing if a standard bound \napplication fails to connect successfully to an allocated LQMA\nprocess or thread (depending on your configuration), then that\nLQMA process or thread remains in a hanging state for ever and\ndo not get re-used by Execution Controller for any further \nMQCONN processing. If an LQMA agent process ever goes into this \n\"limbo\" state, ecasvc utility shows \n\"Allocated, Pending Registration\" flag if it is unthreaded LQMA \nor a positive number against \"Conns Pending\" flag if it is a \nmulti threaded LQMA. If this problem occurrs multiple times, \nthen depending on the user configuration, it might lead to LQMA \nresource problems where Execution Controller will run out of \navailable LQMA agents to serve application MQCONN requests.\n\nAPAR IC65966 - runmqsc <queue manager name> causes FDC on a CPU due to missing\nOSS shared memory files (shm.x.x) for that CPU. Due to a yet\nunknown reason, the queue manager shared memory files for a\nparticular CPU on the system are deleted even when the queue\nmanager is in running state. This prevents any new MQ connection\nrequests from succeeding for the same queue manager on the\naffected CPU. This patch contains changes that will better\nprotect WMQ shared memory files and will prevent accidental\ndeletion of files by WMQ programs. The changes in this patch\nwill also report any such incidence by producing FDC files. The\nFDC file produced by this detection mechanism will contain the\nfollowing information :\nComment1 :- xcsIC_QUEUE_MANAGER_POOL being destroyed.\n\nAPAR IC67569 - When WMQ Queue Server detects an error due to invalid context\ndata during the completion of a TMF transaction started by the\nQueue Server for a PUT or GET no-syncpoint persistent message\noperation, it marks the message on the queue object as \naccessible. This causes the Queue Server to FDC with \n\"Record not found\" on any subsequent MQGET operation to retrieve\nthe same message. The particular message on the queue that has \nthis problem remains in this limbo state forever and can not be\nretrieved. However other messages on the same queue that do not\nhave this problem can be retrieved without any problem using \ntheir msgids. The Queue Server has been revised to correct this\nbehavior such that detection of inconsistent context data during\nMQPUT\/MQGET is logged in the form of an FDC but is otherwise \ncommitted as a normal operation. This will resolve the problem\nof MQGET failing on the retrieval of the message.\n\nAPAR IC68569 - Channel server FDCs during starting\/stopping of channels. The \nproblem occurrs due to a defect in the product where the channel\nserver erroneously closes its open to Queue Server but assumes \nthat its open to Queue Server is valid. The open handle \nto Queue Server after it is closed, gets reused by another open\nand hence any subsequent communication by Channel Server to \nQueue Server always fails. Typically, this problem is seen when\nthe Channel Server experiences transient socket errors with the \nchannel agent (MCA) and it wants to close the socket connection.\nAfter closing the socket connection, Channel server sends a \nmessage to Execute Controller process to de-allocate the MCA\nwith which it had socket error with. It is during this \ncommunication between the Channel Server and the Execution\nController when the Channel Server erroneously closes the open\nto the Queue Server.\n\nAPAR IC69572 - Channel server abends due to illegal address reference during\nadopt MCA processing. This problem happens if the Queue Manager\nhas enabled adopt MCA processing to a remote WMQ Queue Manager\nthat does not send a remote queue manager name during channel\ninitialization\/negotiation. The remote Queue Manager field\nremains NULL and during the Adopt MCA processing logic,\nthe channel server incorrectly references the NULL pointer and\nabends. \n\nAPAR IC69932 - SNA WMQ listener fails to start the channel when HP SPR \nT9055H07^AGN is present on the NonStop system. HP, in its SPR\nSPR T9055H07^AGN, changed the behavior of sendmsg() API if '-1'\nis used as a file descriptor to the API. This caused \nincompatibility with WMQ SNA listener process. WMQ code has now \nbeen revised to work with the updated sendmsg() behavior. \n\nAPAR IC69996 - WMQ Queue Server generates FDC with reply error 74. When an\napplication with a waiting syncpoint MQGET suddenly dies \nbefore getting a reply, the Queue Server can cause FDC \nsometimes. This happens in a narrow timing window when a message\nbecomes available on the queue and the Queue Server starts \nprocessing the waiting MQGET request. If the application dies\nafter Queue Server starts processing the waiting MQGET request, \nthen Queue Server detects the inherited TMF transaction error \nand replies back with error 2072 (MQRC_SYNCPOINT_NOT_AVAILABLE).\nHowever in this case, Queue Server erroneously does not delete\nits internal waiter record for MQGET. When the timer pops for\nthe waiter record, Queue Server attempts to reply back with\nno message available but the call to Guardian REPLYX procedure\nfails with error 74 as the reply to the same request has already\nbeen made(with error MQRC_SYNCPOINT_NOT_AVAILABLE). This causes\nthe Queue Server to FDC.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.7:\n\n363 - WMQ Queue Server under certain conditions fails to handle non-persistent\nand persistent segmented messages at the same time.\n1317 - Support for parallel execution of multiple endmqm programs on the same\nQueue Manager. \n1404 - MQGET WAIT is not being rejected with error 2069 when there is an \nexisting MQGET set signal on the same queue handle. \n1434 - svcmqm utility fails when install files are open but does not tell the \nuser which files are open. \n1566 - svcmqm does not exit immediately when 'cp' command fails to copy \nbinaries during fixpack installation.\n1679 - WMQ Queue Server generates FDC while failing to open the message \noverflow file during retrieval of very large messages (equal to or \nlarger than 'Message Overflow Threshold' displayed with dspmqfls \nutility).\n1709 - instmqm changes related to the use of \/opt directory for the creation of\nbackup archive file.\n1789 - Port of distributed APAR IY66826. Cluster sender channel does not start\nand Queue Manager cache status remain in STARTING state.\n1780 - Port of distributed APAR IY85542. RESET CLUSTER command does not remove \ndeleted repository entry.\n1993 - Enhancement to WMQ mqrc program to print messages related to errors \nbeing returned on NonStop platform.\n2018 - WMQ lqma agent process leaks catalog file open.\n2181 - svcmqm does not output the fixpack that is being installed.\n2282 - instmqm -b archives everything under \/opt directory.\n2290 - Enhancement to Execution Controller process to aid development dubugging\nand troubleshooting.\n2534 - svcmqm has no log of its progress.\n2580 - Potential SEGV in internal function call during Pathway serverclass \nstarting.\n2632 - Incorrect message output in FDC generated by WMQ Queue Server during \nnsrReply function call.\n2633 - WMQ Command Server memory leak found in CLEAR QL command.\n2842 - WMQ Repman process priority was not set correctly when the \nqmproc.ini 'AllProcesses' stanza Priority attribute is configured. \n\nThe following serviceability fixes were made to the SDCP tool:\n\n1971 - sdcp data was not collected correctly when there is a default \nQueue Manager defined.\n2211 - sdcp testing of the permission of \/tmp directory.\n2289 - sdcp logging of progress to a file to aid in sdcp problem diagnosis.\n2298 - sdcp performance improvement.\n2531 - sdcp logging of scheduled CPU information.\n2582 - sdcp capture of Pathway data for PATHMON, PATHWAY, TCP, PROGRAM\nand TERM attributes.\n\nThe following APAR fixes were released in V5.3.1.6:\n\nAPAR IC60204 - A Memory leak occurs with repeated DISPLAY NAMELIST command. The\nleak is observed only when the NAMELIST(s) has one or more NAMES\nvalues defined. The problem is observed from within the runmqsc\nDISPLAY NAMELIST command, or from the PCF\/MQIA equivalent. Tools\nthat request NAMELIST data via the command server with PCF\/MQIA\nrequests such as WMQ Explorer will cause the WMQ command server\nmemory to grow.\n\nAPAR IC61324 - An orphan MCA problem occurs when a connection request from WMQ\nLISTENER or CHANNEL SERVER process to an MCA process fails. WMQ\nExecution Controller (EC) process fails to recognize the\nsituation and does not re-use the MCA process for future agent\nallocation requests. Over a period of time, this problem can\ncause the queue manager to run out of MCA resources which may\nlead to a situation where no new channel can be started. The\nproblem is observed during heavy load conditions where the WMQ\nExecution Controller(EC) process hands over a selected MCA\nprocess to LISTENER\/CHANNEL SERVER before the MCA process\nbecomes ready to accept connection requests.\n\nAPAR IC61551 - The use of cluster administrative command\nRESET CLUSTER ACTION(FORCEREMOVE), to forcibly remove a Queue\nManager out of the cluster can cause FDCs. The problem can cause\nmultiple FDCs and sometimes abend in WMQ REPMAN process in a\nslave role. Once the command has been issued and the error has\noccurred, the concerned Queue Manager must be restarted to\nrestore the clustering function to normal operation. The problem\noccurs because WMQ REPMAN process in a master role does not\ndistribute the RESET CLUSTER ACTION(FORCEREMOVE) command to the\nslave REPMAN processes correctly.\n\nAPAR IC61651 - When a NAMELIST object with one or more NAMES values is defined\nfor a Queue Manager and a dspmqfls command is issued to retrieve\nthe details of either all objects under the Queue Manager or\nthe specific NAMELIST object, FDCs are seen from the WMQ LQMA\nprocess. The problem exists for both unthreaded and\nmulti-threaded LQMA process. The problem occurs because WMQ LQMA\nprocess does not allocate sufficient memory for NAMES buffer\nduring dspmqfls processing.\n\nAPAR IC61660 - A PCF RESET QUEUE STATISTICS command causes the WMQ QUEUE SERVER\nprocess to FDC. The problem occurs during a timing window when\nthere is an outstanding unit of work on the queue and a\nRESET QUEUE STATISTICS command is processed and then the\noutstanding unit of work is backed out. RESET QUEUE STATISTICS\ncauses certain internal counters inside WMQ QUEUE SERVER to be\nreset to zero without taking into account the outstanding unit\nof work. If the outstanding work is later backed out for any\nreason, the already reset counters become negative which causes\nan internal consistency check to fail within the QUEUE SERVER\nprocess and the FDC is generated.\n\nAPAR IC61681 - WMQ QUEUE SERVER causes FDC during MQCLOSE processing on a\ncluster alias queue. The problem occurs during MQCLOSE\nprocessing of a cluster QALIAS object hosted by a different\nQUEUE SERVER than that hosts the target local queue. MQOPEN\nincorrectly failed to allocate an internal handle for the QALIAS\nobject if it was a cluster alias queue. This lead to the FDC\nduring MQCLOSE processing.\n\nAPAR IC61846 - When a START CHANNEL command is issued after WMQ trace is\nenabled, the SSL channel logs a Queue Manager error message and\nfails to start.\nThe problem exists only for a SSL channel, no such problem\nis found for regular (non-SSL) channel. The problem occurs\nbecause of an incorrect implementation of NULL terminated string\nto store SSL Cipher data.\n\nAPAR IC61920 - WMQ on NonStop reports an extra EMS message when the generation\nof an FFST is reported.\nThe intention behind the second EMS message was to report the\ncase when the open of the generated FFST file fails but the\ncheck to see the status of the opened FFST files was missing\nin the code.\n\nAPAR IC62341 - A Security error from the WMQ OAM server is not propagated\ncorrectly. It was reported as MQRC_UNKNOWN_OBJECT_NAME instead\nof MQRC_NOT_AUTHORIZED. When running the Java IVP (MQIVP) to NSK\nwith a non-mqm user specified as the MCAUSER in the SVRCONN\nchannel, and if the non-mqm group isn't given authorization,\nMQIVP fails to connect to the Queue Manager\nwith an authorization failure (MQRC_NOT_AUTHORIZED) but it is\nreported incorrectly as a MQRC_UNKNOWN_OBJECT_NAME error.\n\nAPAR IC62389 - A REFRESH CLUSTER command within a cluster with more than two\nrepositories causes the Repository Manager to fail. The problem\nis not common in normal cluster operation but is likely if\nextensive administrative changes are being made to the cluster\nthat includes a REFRESH CLUSTER command. Incorrect distribution\nof channel status information across multiple copies of the\nREPOSITORY MANAGER cache in different CPUs of the system lead to\nthe FDC.\n\nAPAR IC62391 - Sometimes cluster queues are not visible on CPUs hosting WMQ\nREPOSITORY MANAGER process in a slave role. This is a cluster\nqueue visibility problem across the CPUs. Any attempt to open\nthe cluster queue on CPUs that have the visibility problem\nresults in error MQRC_UNKNOWN_OBJECT_NAME or\nMQRC_CLUSTER_RESOLUTION_ERROR.\nThe problem does not occur on the CPU that hosts WMQ REPOSITORY\nMANAGER process in a master role.\n\nAPAR IC62449 - The WMQ QUEUE SERVER does not log storage related problems to\nthe Queue Manager log. Some of NSK storage related errors like\nerror 43 and error 45 are useful errors for which corrective\naction can be taken to restore normal operation.\nThe WMQ QUEUE SERVER now logs these errors to Queue Manager log.\n\nAPAR IC62480 - Port of IZ51686. Incorrect cache object linkage causes\nunexpected failures (AMQ9456) based on coincidental event\nsequences.\n\nAPAR IC62511 - Port of the following clustering-related APARs from other\nplatforms and versions:\nIZ14399 - Queue managers successfully rejoin a cluster when\nAPAR IY99051 is applied but have mismatching sequence\nnumbers for the cluster queue manager object and its\nassociated clusters.\nIZ21977 - MQRC_OBJECT_CHANGED(2041),\nAMQ9511 SYSTEM.CLUSTER.TRANSMIT.QUEUE,AMQ9448,\nRepository manager ends.\nIZ37511 - Generation of an FDC by the Repository Manager causes\nit to terminate.\nIZ14977 - Missing cluster information when Namelists are used\nto add and remove queue managers from multiple\nclusters at once.\nIZ36482 - Changes to CLUSRCVR shared using a Namelist not\npublished to all clusters.\nIZ10757 - Repository Manager process terminates with error\nRRCI_CLUS_NO_CLUSRCVR_DEFINED.\nIZ41187 - MQRC_CLUSTER_PUT_INHIBITED was returned when an out-\ndated object definition from the cluster repository\nwas referenced.\nIZ34125 - MQ fails to construct and send an availability message\nwhen REFRESH CLUSTER REPOS (YES) is issued on a queue\nmanager with more than 1 CLUSRCVR.\n96181 - Object changed problems with the Repository manager.\nIY97159 - Repository Manager process tries to access the cache\nwhile restoring the cache, resulting in a hang.\nIZ44552 - AMQ9430 message after REFRESH CLUSTER.\n135969 - Refresh bit not set when demoting QM to partial repository.\n\nAPAR IC62850 - The md.Priority of a message was not being set to the queue\nDEFPRTY when a no syncpoint MQPUT is performed using\nMQPRI_PRIORITY_AS_Q_DEF while there is a waiting MQGET.\nA syncpoint MQPUT with a waiting MQGET does not have this\nproblem.\n\nAPAR IC63081 - A WMQ application abends in the MQI library when attempting to\nenqueue messages to a Distribution LIST with one queue entry.\nAlso in certain circumstances, WMQ applications may receive\nincorrect status and reason code while using Distribution LISTS.\n\nAPAR IC63105 - A Memory leak occurs in the WMQ COMMAND SERVER with repeated\nDISPLAY QSTATUS command. The leak is observed only when\nTYPE HANDLE is used with the above command. The problem also\noccurs from within runmqsc DISPLAY QSTATUS command, or from the\nPCF\/MQIA equivalent. Tools that request queue status data via\nWMQ COMMAND SERVER with PCF\/MQIA requests such as WMQ Explorer\nwill cause the WMQ COMMAND SERVER memory to grow.\n\nAPAR IC63271 - When an MQ application delays in replying to the HP system OPEN\nmessage from the WMQ QUEUE SERVER and an MQ message arrives on\nqueue during this period, the MQ message did not get delivered\neven after the reply to the HP system OPEN message is made.\n\nAPAR IC63757 - In a standard bound application, a memory leak occurs in WMQ\nLQMA process during MQCONN\/MQDISC processing. The problem occurs\nwith both unthreaded and multi-threaded LQMA process. If the\nLQMA agents are configured to have high use count\n(MaxAgentUse for unthreaded LQMA and MaxThreadedAgentUse for\nmulti-threaded LQMA) and WMQ Execution Controller process\nre-uses the same LQMA process to satisfy a application MQCONN\nrequest, then the heap memory of LQMA process grows even if\napplication calls MQDISC to disconnect from the\nQueue Manager.\n\nAPAR IC64297 - WMQ Queue Manager becomes non-responsive because the\nWMQ QUEUE SERVER does not clean up the internal queue manager\nobject opens. The QUEUE SERVER internal links for\nMQOPEN of the Queue Manager object were not\nbeing released during the MQCLOSE processing. This causes a\nbuildup of QUEUE SERVER memory as the application repeated\nMQOPEN of the queue manager object repeatedly. When either\na MQDISC occurred or the application process ended,\nthe QUEUE SERVER cleans up its internal lists for the process.\nThis resulted in a perceived QUEUE SERVER loop and\nnon-responsive WMQ as there were\nover 246,000 opens found of the Queue Manager object with a\nhigh mark of 548,000 within the QUEUE SERVER when a dump of the\nQueue Server was analyzed.\nMQOPEN of other MQ objects (qlocal, qalias, qremote etc.) do not\nhave this issue.\n\nAPAR IC64373 - The COBOL copybook now includes missing definitions for MQGET\nSET SIGNAL processing.\n\nAPAR IC64435 - An incorrect persistence attribute was being set for a\nnon-persistent message on XMIT queue. When MQPUT of a\nnon-persistent message is done using MQPER_PERSISTENCE_AS_Q_DEF\nattribute to a remote queue while the channel is idle, the MD\nMD data in transmit queue header contained\nMQPER_PERSISTENCE_AS_Q_DEF value of (2).\n\nAPAR IC64630 - It takes longer for unthreaded SSL sender channel to end when\ncommunication to the remote Queue Manager is lost. The problem\noccurs because the unthreaded MCA process running the SSL channel\nfails to timeout correctly causing the channel to end differently\nthan non-SSL channels. The problem is observed only with SSL\nchannels and no such problem is visible with regular SSL \nchannels. \n\nThe following fixes discovered during IBM's development and testing work are\nalso released with V5.3.1.6:\n\n1096 - An MQGET BROWSE operation can return prematurely with no message\navailable as well as can cause a waited GET to hang indefinitely.\n1513 - amqrrmit erroneously reports multiple master REPMAN processes.\n1587 - Enhancements to Execution Controller log messages pertaining to\nThreshold and MaxAgent capacity situations. For unthreaded agents,\nthe \"max unthreaded agents reached\" message will now be logged when the\nMaxUnthreadedAgent is allocated to perform work. In previous releases,\nthe message was logged when the MaxUnthreadedAgent was added to the idle\npool, which actually left one agent still available for use.\nFor threaded agents, messages have been enhanced to display separate\nThreshold\/Maximum messages for agents and threads. In previous releases,\n\"further connections refused\" was displayed when the MaxThreadedAgent\nwas started, which actually left MaximumThreads connections still\navailable for use. In this release \"further connections refused\" will be\ndisplayed when the MaximumThread is allocated for use.\nAlso in this release, messages will be logged when the number of agents\nor threads, after having exceeded the threshold or reached maximum,\nfall below the Maximum or threshold limit.\n1669 - ZCG_FFST does not report the error code for a TMF error.\n1675 - The Execution Controller now provides an API to mark MCAs that are no\nlonger used.\n1670 - Correction to missing component data in a FDC generated by the\nQueue Manager server(MQS-QMGRSVR00) process(amqqmsvr).\n1678 - Queue server abends due to uninitialized FFST inserts.\n1706 - dmpmqaut -m <qmgr> sometimes only reports the first QALIAS object and\nFDCs in kpiEnumerateObjectAuthority.\n1710 - The Execution Controller sometimes allocates an MCA that it has\npreviously asked to end\n1712 - Cluster queue manager STATUS and queue visibility problems in slave\nREPMAN.\n1734 - Fixes\/Updates to MQ tracing mechanism.\n1735 - Subscription id distribution.\n1751 - Fixes\/Updates to MQ tracing mechanism.\n1807 - Changes to improve service and debug capability of Execution Controller\nstarted processes.\n1873 - \"*\" subscriptions are generated incorrectly causing them to be ignored.\n1989 - Fix for channel server hanging problem while opening REPMAN process.\n2003 - LQMA now FDCs when a invalid message is received.\n\nThe following serviceability fixes were made to the SDCP tool:\n\n1659 - sdcp is not capturing the PSTATE of backup processes.\n1676 - sdcp takes too long.\n1690 - sdcp MQ utilities are not using the correct Queue Manager name if\nthe name is mangled because of non-alphabetic characters.\n1702 - sdcp doesn't collect all relevant Saveabend files.\n1705 - sdcp workaround to avoid APAR IC61651.\n1971 - sdcp now gives correct output for default Queue Manager.\n\nThe following APAR fixes were released in V5.3.1.5:\n\nAPAR IC55607 - FDC files can fail to be written, or written to the wrong file\nFDCs can be suppressed or overwritten when application processes\nraise FDCs under User IDs that are not members of the MQM group.\nIn addition, because FDC files are named with the CPU and PIN of\nthe generating process, and PIN is reused frequently on\nHP NonStop Server, FDCs from different processes can be appended\nto the same file.\n\nThe format of the file name for FDCs is:\nAMQcccpppp.s.FDC\n\nwhere ccc is the CPU number\npppp is the PIN\ns is the sequence number\n\nIn V5.3.1.4 and earlier releases, the sequence number was\nalways set to 0. This fix introduces the use of the sequence\nnumber field to ensure that FDCs from different processes are\nalways written to different files, and that FDCs can always be\nwritten. FDC files are created with file\npermissions \"rw-r----\" to prevent unauthorized access to the\nFDC data.\n\nAPAR IC57435 - Attempts to end a queue manager with either -t or -p following\na cpu failure in some cases did not work as a result of\ndamage to the WMQ OSS shared memory files. The shared memory\nmanagement code was revised to tolerate OSS shmem\/shm files\ncontaining invalid data. Invalid data in these files is now\nignored and memory segment creation will continue normally.\n\nAPAR IC58165 - Triggered channels sometimes do not trigger when they should\nSome attributes of a local queue that determine if trigger\nmessages get generated are not kept up to date for long-running\napplications. The most critical attribute is the GET attribute\nthat controls whether MQGET operations are enabled for a queue\nor not. If the application opened the triggered queue while\nthe queue was GET(DISABLED), and the queue is subsequently\nmodified to be GET(ENABLED), triggering will not occur when it\nshould.\n\nAPAR IC58377 - Trace data is not written when PIDs are reused for processes\nrunning under different User IDs.\nTrace files are named according to the CPU and PIN of the process\nthat is being traced. On HP NonStop Server, since PINs are\nrapidly reused, it is likely that a process attempting to write\ntrace data will encounter an existing file written with the same\nCPU and PIN. The traced process will be unable to write data if\nthe original file was written (and therefore owned) by a\ndifferent User ID.\n\nThis fix introduces a sequence number into the trace file names\nto prevent trace file name collisions.\n\nThe format of trace file names will change from:\n\nAMQccppppp.TRC to AMQccppppp.s.TRC\n\nwhere s is a sequence number that will usually be 0.\nTrace files are now created with file permissions \"rw-r----\"\nto prevent unauthorized access to the trace data.\n\nAPAR IC58717 - The Queue Server backup process generates FDCs showing ProbeId\nQS123006 from qslHandleChpPBC when attempting to locate a browse\ncursor message, with the comment text of\n\"Error locating Last Message in Browse Cursor checkpoint in\nBackup\" or \"Error locating Last Logical Message in Browse Cursor\ncheckpoint in Backup\". The problem appears only when running a\nnumber of parallel browse \/ get applications for the same queue\nobject.\n\nAPAR IC58792 - strmqm fails to delete orphaned temporary dynamic queues if the\nassociated touch file is missing. This results in these queues\nremaining in the object catalog indefinitely, and FDC files\nbeing generated each time the queue manager is started,\nreflecting the fact that the queue could not be deleted. The\nhousekeeping function was modified to always silently remove\ntemporary dynamic queue objects from the catalog, whether or\nnot they are damaged. FDC files are no longer generated.\n\nAPAR IC58859 - wmqtrig script does not pass TMC with ENVRDATA correctly.\nIf ENVRDATA is part of the PROCESS definiton used by\nrunmqtrm to trigger applications the TMC is not delivered to\nthe application correctly. The problem does not occur with\nblank ENVRDATA. Additionally, ENVRDATA or USERDATA attributes\nthat contain volume names ($DATA for example) are not processed\ncorrectly by the wmqtrig script.\n\nAPAR IC58891 - Sender channels that were running in a CPU that failed are not\nrestarted in some circumstances. Sender channels that are not\nrestarted report \"AMQ9604: Channel <...> terminated\nunexpectedly\" in the queue manager error log, and the channel\nserver create FDCs with ProbeID RM487001, Component\n\"rriChannelTerminate\".\n\nAPAR IC58976 - A server channel without a specified CONNAME enters a STOPPED\nstate when the MCA process running the channel is forcibly\nstopped or ends following a CPU failure. The channel state\nshould be set to INACTIVE following this type of event. To\nrecover the situation the channel has to be manually restarted\nor stopped using MODE(INACTIVE).\n\nAPAR IC59024 - The copyright data in the COBOL COPYBOOK CMQGMOL file\nis incorrect.\n\nAPAR IC59126 - Context data is missing in COA message.\nWhen an MQPUT application sends a message with COA report\noption, the generated replied COA message does not contain\ncontext data eg. PutDate, PutTime, etc.\n\nAPAR IC59364 - Queue Server primary incorrectly commits an WMQ message in\ncertain cases where the backup process has failed to process\nan internal checkpoint message. This causes an inconsistency\nbetween the primary and backup processes when an MQGET is\nattempted on this message, resulting in FDCs with the comment\ntext \"Invalid Message Header context in Backup for Get\" from\nComponent \"qslHandleGetCkp\". The queue object is no longer\naccessible via MQGETs, but can be recovered by stopping the\nbackup process.\n\nAPAR IC59388 - V5.3 OAM Implementation contains migration logic which may be\ntriggered erroneously in some circumtances, removing authority\nrecords from the SYSTEM.AUTH.DATA.QUEUE. This change removes the\nmigration logic, since there are no previous versions of the\nOAM which require migration.\n\nAPAR IC59395 - Threaded LQMA actual usage is one larger than the configured\nmaximum use count in the qmproc.ini file. Unthreaded LQMAs\nand MCAs (both threaded and unthreaded) do not suffer from this\nproblem.\n\nAPAR IC59428 - In some circumstances where connecting applications terminate\nunexpectedly during the MQCONN processing, either by external\nforcible termination, or as a consequence of other failures that\n\nresult in termination, the resulting error can cause the LQMA\nprocess handling the application to terminate. This will\ncause collateral disconnections of all other applications using\nthe same LQMA, with the application experiencing either a 2009\n(connection broken) or 2295 (unexpected) error. The problem\nwindow occurs only during one section of the connect protocol\nand has been observed only on very busy systems with repeated\nmultiple forced terminations of applications.\n\nAPAR IC59742 - qmproc.ini file will fail validation if configured with both\nMinIdleAgents=0 and MaxIdleAgents=0.\n\nAPAR IC59743 - Queue Manager server expiration report generation is not fully\nconfigurable. The frequency with which the queue manager server\ngenerates expiration reports is configurable but the number of\nreports generated is not. This change introduces a new\nenvironment variable (MQQMSMAXMSGSEXPIRE), to allow\nconfiguration of the number of expiration reports generated\nat any one time. The parameter can be added to the WMQ\nPathway MQS-QMGRSVR00 serverclass:\nALTER MQS-QMGRSVR00, ENV MQQMSMAXMSGSEXPIRE=<1-99999>\nIf this value is not specified in the queue manager\nserverclass configuration, the value defaults to 100.\n\nAPAR IC59802 - Memory leak occurs with repeated DIS CHSTATUS SAVED command.\nA memory leak exists in the Channel Saved Status query. This\nleak is observed within either the runqmsc DISPLAY CHSTATUS\n\nSAVED command, or the PCF\/MQIA equivalent. Tools that request\nsaved channel status data via the Command Server with PCF \/ MQIA\nrequests such as WMQ Explorer will cause the Command Server\nmemory to grow.\n\nAPAR IC60114 - WMQ processes or user application processes generate FDCs\nreferring to \"shmget\" following forcible termination of the\nprocess or failure of the CPU running it. This is a result of\nthe Guardian C-files (Cnxxxxxx) for a CPU becoming corrupt\nduring an update operation, rendering the file and associated\nshared memory segment unusable. C-file update operations are\nnow performed atomically to prevent this problem.\n\nAPAR IC60135 - Improve servicability of the \"endmqm -i\" command to prevent the\ncommand from waiting indefinitely for the queue manager to end.\nFollowing this change after a specified number of seconds, the\ncommand will complete with the message \"Queue Manager Running\"\nand return to the command line with exit status 5.\n\nAPAR IC60175 - Description is not available (security\/integrity exposure)\n\nAPAR IC60361 - Memory leak occurs in SVRCONN channel MCAs which repeatedly open\nlocal queue objects.\n\nAPAR IC60455 - WMQ Broker restart may not work correctly.\nIf the WMQ Broker is restarted using strmqbrk\/endmqbrk,\nsubsequent attempts to restart the broker may fail, and 2033\nerrors my arise when running the test broker samples and\nrecycling the broker processes.\n\nAPAR IC60119 - System Administration manual incorrectly states the default\nvalue of the TCP\/IP Keepalive is \"ON\"\n\nThe following fixes discovered during IBM's development and testing work were\nreleased with V5.3.1.5:\n\n1403 Erroneous SVRCONN channel ended message.\nSVRConn channels should not generate \"Channel Ended\" messages in\nthe error log, but in some circumstances, threaded svrconn\nchannels do generate these messages.\n1451 Internal changes relating to trace and FDC files sequence numbers\n1453 Problem with MQCONN after restart of broker\n1516 strmqm fails with invalid ExecutablePath attribute (qmproc.ini)\n1560 Port of V51 MQSeries for Compaq NonStop Kernel APAR IC57981.\nBackup Queue Server runs out of memory processing non-persistent\nmessages in 27K range. \n1564 runmqlsr abends in nssclose after a previous 'socket' calls fails\n1570 Added Agent type to EC logged threshold and max agent messages.\n1576 Change ECA interface to V4\n1577 Queue Server message expiration deletion phase log message\n1583 Blank channel status entries can get created triggering\nchannels when AdoptMCA is enabled.\nUnder certain timing situations, when triggered channels are\nused and AdoptMCA is enabled for the queue manager, blank\nchannel status entries can be created with the JOBNAME\nreferencing the Channel Initiator (runmqchi), for example:\nAMQ8417: Display Channel Status details.\nCHANNEL() XMITQ()\nCONNAME() CURRENT\nCHLTYPE() STATUS(BINDING)\nMSGS() BATCHES()\nJOBNAME(5,333 $MQCHI OSS(318898190)) RQMNAME()\nThis problem does not cause any immediate functional problem,\nhowever the blank entries consume channel status table entries\nand therefore could prevent legitimate channel starts in the\nevent that the status table becomes full.\n1594 C++ unthreaded libraries use threaded semaphores\n1596 Improved cs error reporting\n1597 EC started processes sometimes not started in intended CPU\n1598 NSS Incorrect component identifiers used in some parts of zig\n1608 Queue status errors on failure of a no syncpoint persist message\nput or get\n1601 Tracing details to the EC to augment the Entry and Exit trace\ncalls\n1611 LQMA Queue manager attribute corruption\n1613 Enhanced LEC Failure Handling\n1615 The EC may allow the os to choose in which cpu a MCA will start\n1616 Channel server comp traps have potential performance impact.\n1621 MQCONN does not report valid reason code when agent pool is full\n1622 After a channel is started dis chs displays \"binding\" in some\ncircumstances when it should display \"running\"\n1623 Incorrect message when MCA allocation fails\n1626 Addition of Service information collection tool (SDCP)\n\nNew platform support was released in V5.3.1.4:\n\nFixpack V5.3.1.4 introduced support for the HP Integrity NonStop BladeSystem\nplatform, NB50000c. Use the H-Series (Integrity) package of WebSphere MQ\nfor execution on the BladeSystem. Please refer to the Hardware and Software\nRequirements section for details about the levels of the J-Series software\nrequired.\n\nThe following APAR fixes were released in V5.3.1.4:\n\nAPAR IC57020 - runmqtrm does not function correctly and produces errors in some\ncases.\nWhen a triggered application is a guardian script file\n(ie filecode 101). runmqtrm produces an \"illegal program\nfile format\" error. Triggering also does not work correctly\nfor COBOL or TAL applications.\n\nAPAR IC57231 - The execution controller starts repository processes at the\nsame priority as itself in some cases, and does not take\naccount of the values set in the qmproc.ini file.\n\nAPAR IC57420 - Repository manager restart following failure causes cluster\ncache corruption in some circumstances.\nIf a repository manager abends while a queue manager is under a\nheavy load of cluster-intensive operations, in some\ncircumstances the repository manager that is restarted can\ndamage the cluster cache in the CPU in which it\nis running. This can prevent further cluster operations in that\nCPU and cause WMQ processes to loop indefinitely. This release\nchanges the repository startup to prevent this from happening.\n\nAPAR IC57432 - OSS applications that attempt to perform MQI operations from\nforked processes encounter errors.\nIf an oss WMQ application forks a child process, that child\nprocess will encounter errors if it attempts to perform MQI\noperations. Some operations may succeed, but will result\nin the generation of FDC files.\n\nAPAR IC57488 - MQMC channel menu display display error after channel is\ndeleted.\nIf a channel is deleted while the channel menu in MQMC\nis displayed, refreshing the channel menu produces the\nerror: \"Unknown error received from server. Error number\nreturned is 1\" and will not correctly display the channel\nlist without restarting MQMC.\n\nAPAR IC57501 - unthreaded sender channels to remote destinations with\nsignificant network latency may fail to start with timeout\nerrors.\n\nAPAR IC57524 - Applications launched locally from remote nodes cannot access\nsome of the queue manager shared memory files due to default\nsecurity on those files.\n\nAPAR IC57627 - Handling of TMF outages to improve operational predictability.\nIf TMF disables the ability to begin new transactions\n(BEGINTRANS DISABLED), WMQ does not always react in a\npredictable or easily diagnosed manner, and applications can\nsuffer a variety of different symptoms. If TMF is stopped\nabruptly (STOP TMF, ABRUPT) queue managers can become unstable\nand require significant manual intervention to stop and restart.\nRefer to item 18 in \"Known Limitations, Problems and\nWorkarounds\" later in this README for more information.\n\nAPAR IC57712 - altmqfls --qsize with more than 100 messages on queue fails.\nWhen a altmqfls --qsize is performed with more the 100 MQ\nmessages in the queue the processing fails.\n\nAPAR IC57719 - FDCs from MQOPEN when an error exists in alias queue manager\nresolution path. If a queue resolution path includes a queue\nmanager alias, and the target of the alias does not exist,\nthis will produce an FDC, rather than just failing the\nMQOPEN as would be expected.\n\nAPAR IC57744 - CPU goes busy when stopping a threaded SSL receiver channel\nusing MODE(TERMINATE).\nIf a stop channel mode(terminate) is used to stop an SSL\nreceiver channel that is running in a threaded MCA, the CPU\nwhere the MCA is running in begin using large amounts of CPU\ntime (95% range). This is due to a problem in the threads\nlibrary.\n\nAPAR IC57876 - Very infrequently, messages put via threaded LQMAs can in some\ncircumstances contain erroneous CCSID information. This has\nbeen observed to cause conversion errors if the message is\ndestined for a channel that has the CONVERT(YES) set.\nUnthreaded LQMAs do not suffer from this problem.\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.4:\n\n993 - Due to the way that default file security was used, file security for\ncertain shared memory files used by the queue manager (SZ***) may\n\ninadvertently change in a way that prevents applications not in\nthe mqm group from issuing MQCONN. File permissions were rationalised\nin this release to reflect those used for other shared memory files.\n1458 - Resolve Channel command generates FFSTs.\nWhen resolving In-Doubt channels, FFSTs were generated by the Channel\nServer and the MCA. Although the channels were successfully resolved,\nthe In-Doubt status in a DIS CHS query was not correctly updated.\nWhen resolving In-Doubt channels using the COMMIT option the following\nerror message was displayed \"AMQ8101: WebSphere MQ error (7E0) has\noccurred.\"\n1493 - The validation of the qmproc.ini file does not report the error case\nwhere multiple ChannelsNameMatch entries are specified ChlRule1.\n1498 - Instmqm does not support installation of the product on\nIntegrity NonStop BladeSystem platforms.\n1507 - Some Execution controller messages were missing \"Action\" descriptions\nwhen reported in the error log.\n1517 - In the qmproc.ini file, the AppRule4-SubvolMatch argument was not\nworking\n1522 - Communications Component Function ids and probes are incorrect. This\nresulted in misleading or missing information in trace files generated\nfor support purposes.\n1546 - MQBACK operation incorrectly reports error during broker operations\n1549 - Channel Server doesn't shutdown after takeover.\nIf the Primary Channel Server process is prematurely ended, for\nexample by a CPU crash, the Backup Channel Server process becomes the\nnew Primary process. Subsequent attempts to use endmqm will hang\nbecause the new Primary Channel Server process will not end.\n\n\nThe following documentation APARs are addressed by the V5.3.1.4 readme:\n\nAPAR IC55404 - REFRESH QMGR PCF command is not documented in the Programmable\n\ncommand formats manual.\n\nAlso - please check the \"Limitations\" and \"Known Problems and Workarounds\"\nsections later on in this readme for updates.\n\nThe following APAR fixes were released in V5.3.1.3:\n\nAPAR IC54305 - The HP TNS (non-native) C compiler generates Warning 86 when\ncompiling MQI applications\nAPAR IC55501 - The altmqfls command does not return the correct completion\nstatus; it always returns success\nAPAR IC55719 - Non-native MQINQ binding does not deal with some null pointer\nparameters correctly\nAPAR IC55977 - Channel retry does not obey SHORTTMR interval accurately enough\nAPAR IC55990 - Trigger data changes not being acted upon if they were made\nwhile the queue was open, leading to incorrect triggering\nbehavior\nAPAR IC56277 - Command Server can loop with INQUIRE QS command with a single\nparameter\nAPAR IC56278 - A remote RUNMQSC DIS QS command always times out\nAPAR IC56309 - MCAs do not disconnect from some shared memory when ending,\nwhich causes a slow memory leak, and under some conditions an\nabend\nAPAR IC56458 - Channel Server loops after installing V5.3.1.2 due to corrupt\ndata on SYSTEM.CHANNEL.SYNCQ\nAPAR IC56493 - Cannot use \"qualified\" hometerm device names with V5.3.1.2\nAPAR IC56503 - Channel Server and MCA can deadlock after repeated STOP CHANNEL\nMODE(FORCE) or MODE(TERMINATE) commands\nAPAR IC56536 - Unthreaded responder channels don't de-register from the EC when\nan error occurs during or before channel negotiation. For\nexample, bad initial data will cause this. Unthreaded MCAs\nbuild up and eventually reach the maximum which prevents further\nchannel starts\nAPAR IC56681 - C++ unthreaded Tandem-Float SRLs have undefined references\n\nAPAR IC56834 - endmqm -p can sometimes leave MCA processes running\n\nThe following fixes discovered during IBM's development and testing work were\nreleased with V5.3.1.3:\n\n663 - Guardian command line utility return status is not the same as the OSS\nutilities return status\n1402 - Add additional tracing when testing for inconsistencies in processing\na channel start in the Channel Server\n1416 - Ensure that the Channel Server can support the maximum BATCHSZ of 2000\n1446 - Pub \/ Sub command line utilities do not behave well if no broker has run\nsince the queue manager was created\n1470 - EC abends attempting to start a non-executable REPMAN\n1474 - Pub \/ Sub broker process handling corrections for the EC\n1476 - The EC checkpoints the number of threads running in agents incorrectly\n1477 - Enhancement to ecasvc utility: the creation date\/time of LQMAs, MCAs,\nand REPMEN are now displayed\n1487 - Enhancement to ecasvc utility: changed the display of Agent attributes\nto use the \"real\" qmproc.ini attribute names. Added a new option,\nthat displays information about all connected applications\n1494 - A small memory leak occurs for the delete channel operation\n1508 - Multiple qmproc.ini environment variables don't get propagated to\nagents or repmen\n1509 - The EC failed to stop an MCA that was hung when a preemptive shutdown\nwas initiated\n\nThe following documentation APARs were addressed by the V5.3.1.3 readme:\n\nAPAR IC55380 - Transport provider supplied during install is not propagated to\nPathway configuration by crtmqm. Please see the documentation\nupdate below made for Page 17 of the \"Quick Beginnings\" book.\n\nThe following APAR fixes were released in V5.3.1.2:\n\nAPAR IC52123 - LQMA abend handling rollback of a TMF transaction in MQSET\nAPAR IC52963 - The PATHMON process is not using configured home terminal for\nMQV5.3 on HP Nonstop Server\nAPAR IC53205 - FDC from Pathway runmqlsr when STOP MQS-TCPLIS00\nAPAR IC53891 - There is a memory leak in the Channel Server when processing\nthe DIS CHS command\nAPAR IC53996 - C++ PIC Guardian DLLs missing.\nAPAR IC54027 - MQRC_CONTEXT_HANDLE_ERROR RC2097 when loading messages using\nMO71\nAPAR IC54133 - Multi-threaded LQMA should not try to execute Unthreaded\nfunctions if qmproc.ini LQMA stanza sets MaximumThreads=1\nAPAR IC54195 - runmqtrm data for Trigger of Guardian application not\nreinitialized\nAPAR IC54266 - MinThreadedAgents greater than PreferedThreadedAgents causes\nMQRC 2009 error\nAPAR IC54488 - MCA's abend after MQCONN\/MQDISC 64 times.\nAPAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped\nAPAR IC54517 - upgmqm does not handle CPUs attribute for PROCESS specifiction\nin a SERVERCLASS\nAPAR IC54583 - SSL channel agent can loop if an SSL write results in a socket\nI\/O error\nAPAR IC54594 - EC abends with non-MQM user running application from non-MQM\ndirectory\nAPAR IC54657 - Channel stuck in BINDING state following failed channel start\ndue to unsupported CCSID.\nAPAR IC54666 - Queue Server deadlock in presence of system aborted\ntransactions.\nAPAR IC54798 - upgmqm fails with Pathway error on 3 or more status servers that\nrequire migration from V5.1 queue manager.\nAPAR IC54841 - When a temporary dynamic queue is open during \"endmqm -i\"\nprocessing an FDC is generated\nAPAR IC55008 - Added processing that will cause Channel Sync data to be\nHardened at Batch End\nAPAR IC55073 - altmqfls --qsoptions NONE is not working as specified\nAPAR IC55176 - Abend in MQCONN from app that is not authorized to connect (2035)\nor with invalid Guardian Subvolume file permissions\nAPAR IC55500 - QS Deadlock with Subtype 30 application using MQGMO_SET_SIGNAL\nAPAR IC55726 - Channel stuck in BINDING state following failed channel start\n\ndue to older FAP level\nAPAR IC55865 - Abend on file-system error writing to EMS collector\n\nThe following fixes discovered during IBM's development and testing work were\nalso released with V5.3.1.2:\n\n1122 - Invalid\/incomplete FFST generated during MQCONN when Guardian\nsubvolume cannot be written to.\n1392 - Add support for Danish CCSID 65024\n1397 - Command Server fails to start and EC reports failure to initialize\na CPU - error 12 purging shared memory files.\n1409 - Guardian WMQ command fails when invoked using Guardian system() API\n1413 - MCA looping after SSL socket operation fails\n1419 - altmqfls --volume attempted using a open object causes FDCs\n1439 - On non-retryable channel, runmqsc abends while executing RESOLVE CHANNEL\ncommand\n\nThe following documentation APARs were addressed by V5.3.1.2:\n\nAPAR IC53996 - C++ PIC Guardian DLLs missing.\n\noriginally released in V5.3.1.1 Patch 1:\nAPAR IC53891 - There is a memory leak in the Channel Server when\nprocessing the DIS CHS command\n\noriginally released in V5.3.1.1 Patch 2:\nAPAR IC54583 - SSL channel agent loops\n\noriginally released in V5.3.1.1 Patch 3:\nAPAR IC54666 - Queue Server deadlock in presence of system aborted\ntransactions.\n\noriginally released in V5.3.1.1 Patch 4:\nAPAR IC54512 - OSS runmqsc loops if Guardian runmqsc is TACL stopped\n\nThe following APAR fixes were released in V5.3.1.1:\n\nAPAR IC52737 - When in SSL server mode and the sender is on zOS a list of CAs\nthat the server will accept must be sent to the zOS sender\nduring the SSL handshake\n\nAPAR IC52789 - upgmqm support for upgrading V5.1 queue managers that do not use\nOAM (created with MQSNOAUT defined). Also add diagnostics as to\nreasons and preventative actions for failure to create a PATHMON\nprocess\n\nAPAR IC52919 - Problems in synchronization of starting a queue manager when\nmultiple Queue Servers are defined\n\nAPAR IC52942 - Trigger Monitor holds Dead Letter Queue open all the time\nAPAR IC53240 - Correct sample API exit to build for PIC and SRL\/Static\nAPAR IC53243 - Start of many applications simultaneously causes LQMA FDC\nAPAR IC53248 - Kernel not informing repository cache manager of updates to\ncluster object attributes\n\nAPAR IC53250 - Flood of FDCs when trace is enabled before qmgr start\nAPAR IC53254 - Browse cursor mis-management left locked message on queue.\nIn addition, browse cursor management was not correct in the\nevent that a syncpoint MQGET rolls back\n\nAPAR IC53288 - Cluster Sender channel is not ending until the HBINT expired\nAPAR IC53383 - upgmqm was losing the MCAUSER attribute on channels\nAPAR IC53492 - TNS applications fail in MQPUT with more than 106920 bytes of\ndata\n\nAPAR IC53524 - SVRCONN channels are not ending after STOP CHANNEL if client\napplication is in a waited MQGET\n\nAPAR IC53552 - OAM uses getgrent() unnecessarily, causing slow queue manager\nstartup\n\nAPAR IC53652 - Guardian administration commands don't work with VHS or other\nprocesses as standard input or output streams\n\nAPAR IC53728 - ECONNRESET error when Primary TCP\/IP process switched should\nnot cause listener to end\n\nAPAR IC53835 - Assert in xtrInitialize trying to access trace shared memory\n\nThe following documentation APARs were addressed by V5.3.1.1:\n\nAPAR IC51425 - Improve documentation of crtmqm options\nAPAR IC52602 - Document ClientIdle option\nAPAR IC52886 - Document RDF setup ALLSYMLINKS\nAPAR IC53341 - Document OpenTMF RMOPENPERCPU \/ BRANCHESPERRM calculation\n\nThe following fixes discovered during IBM's development and testing\nwork were also released with V5.3.1.1:\n\n634 - Correct function of altmqfls option to reset measure counter\n822 - Message segmentation with attempted rollback operation failed\n862 - PCF command for Start Listener fails\n903 - Channel status update problems during shutdown after Repman has ended\n922 - Channel status incorrect when attempting to start a channel and the\nprocess management rules prevent the MCA thread or process from starting\n929 - Incorrect response records when putting to distribution list\n1012 - Two of the sample cobol programs give compilation error\n1059 - C-language samples use _TANDEM_SOURCE rather than __TANDEM\n1064 - errors checkpointing large syncpoint MQPUT and MQGET operations\nwhen transactions abort\n1069 - Not able to delete CLNTCONN channels\n1108 - Error logged when MCA exits because maximum reuse count is reached\n1152 - strmqm -c option gives unexpected error if executed after strmqm\n1176 - Sample cluster workload exit not functioning correctly\n1177 - QS backup abend on takeover with local TMF transactions\n1180 - Segmentation of messages on transmission queues by the queue manager\nwas incorrect.\n1182 - Replace fault tolerant process pair FDCs with log messages for better\noperator information when a takeover occurs\n1185 - Opens left in all three NonStop Server processes after divering CPUs\n1208 - Trace info is incorrect for zslHPNSS functions. FFSTs show incorrect\ncomponent and incorrect stack trace info\n1210 - FFSTs generated by criAccessStatusEntry when starting channel with\nsame name from another queue manager\n1213 - Pathway listener generates FDCs on open of standard files\n1229 - Permanent dynamic queues being marked as logically deleted on last close\n1240 - Channel Server needs to update status for unexpected thread close\n1244 - Speed up instmqm\n1246 - implement workaround for the regression in the OSS cp command introduced\nin G06.29\/H06.06 where a Format 2 file is created by default when\ncopying to Guardian\n1247 - Fixes to SSL CRL processing, added CRL reason to message amq9633\n1253 - SSL samples required updating to reflect enhanced certificate file\norganization - cert.pem and trust.pem\n1254 - Fix an MQDISC internal housekeeping problem\n1256 - MCA does not exit after re-use count if an error occurs during early\ninitialization\n1260 - Speed up strmqm when performed on very busy systems with large number\nof CPUs by minimizing calls to HP FILE_GETOPENINFO_ API\n1264 - Correct the handling of the option to make Message Overflow files\naudited in QS\n1266 - Improve diagnostic information of FFST text for semaphore problem\n1271 - After sequence of 2 CPU downs, EC, QS and CS still have openers\n1272 - Improve protection in svcmqm when files in the installation are open\n1273 - Memory leak in the command server caused by unreleased object lists\n1277 - Don't FFST if initialization fails because the mqs.ini file doesn't\nexist\n1281 - LQMA thread doesn't end when CPU containing application goes down\n1288 - Channels not retrying after CPU failure that also causes takeover of CS\n1290 - MQDISC when connection broken doesn't tidy up transaction\n1291 - Correct the syncpoint usage when amqsblst is used as a server. Enhance\namqsblst for fault tolerant behavior - makes amqsblst attempt to\nreconnect and reopen objects on 2009 errors so it can be used during\nfault tolerant testing\n1294 - Application process management rules don't always work correctly\n1297 - Correct file permission of trace directory and files - changed\npermission of trace directory to 777\n1301 - No queue manager start or stop events generated\n1302 - instmqm function get_Guardian_version should look for string\n\"Software release ID\"\n1306 - instmqm validation fails when Java is not installed - issue a warning\nif the java directory doesn't exist and continue the installation\n1310 - OSS Serverclasses not restarting in Pathway if they end prematurely\n1313 - EC process management can exceed maximum number of threads for LQMA\n1317 - REFRESH CLUSTER command with REPOS(yes) fails\n1319 - MQPUT and MQPUT1 modifying PMO.Options when creating a new MsgId\n1324 - MQPUT returned MQRC_BACKED_OUT when putting message that required\nsegmentation to local queue\n1325 - Trace state doesn't change in servers unless process is restarted\n1340 - QS error handling MQPUT checkpoint. Also can lead to zombie messages on\nqueue requiring queue manager restart to clear\n1341 - MQGET not searching correctly in LOGICAL_ORDER for mid-group messages\n1346 - EC initial memory use too high. Initial allocation was approximately\n18 megabytes\n1351 - Upgrade logging format to V6.x style\n1353 - MQGET of 210kbyte NPM from queue with checkpointing disabled caused\nmessage data corruption at offset 106,906\n1355 - xcsExecProgram sets current working directory to \/tmp - changed to\ninstallation errors directory\n1357 - instmqm fails to create an OSS symbolic link after a cancelled install\n1362 - MsgFlags showing segmentation status should still be returned in\nMQGET even if applications specifies MQGMO_COMPLETE_MSG\n1364 - endmqlsr sometimes hangs\n1366 - Correct trace, FDC and mqver versioning information for V5.3.1.1\n\nAll fixes that were previously released in V5.3.0 and V5.3.1 are also included\nin this release. For information on fixes prior to V5.3.1.1, please refer to\nthe readme for V5.3.1.3 or earlier.\n\nBackward compatibility\n----------------------\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is interoperable over channels\nwith IBM MQSeries(TM) V5.1 for Compaq NSK, as well as any other current or\nearlier version of IBM MQSeries or IBM WebSphere MQ on any other platform.\n\nProduct compatibility\n---------------------\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is not compatible\nwith IBM WebSphere MQ Integrator Broker for HP NonStop Server.\nFor other compatibility considerations, review the list of suitable\nproducts in the WebSphere MQ for HP NonStop Server Quick Beginnings book.\n\nIBM WebSphere MQ V5.3.1 for HP NonStop Server is compatible with any\ncurrently supported level of IBM WebSphere MQ Client. IBM WebSphere MQ V5.3.1\nfor HP NonStop Server does not support connections from WebSphere MQ\nExtended Transactional Client.\n\nINSTALLATION, MIGRATION, UPGRADE AND CONFIGURATION INFORMATION\n==============================================================\nHardware and Software Requirements\n----------------------------------\n\nThe list of mandatory HP operating system and SPR levels has changed\nsince the V5.3.1.1 release. Please read the following information carefully,\nand if you have any questions, please contact IBM.\n\nFor the HP Integrity NonStop Server H-Series systems, the following system\nsoftware versions are the minimum mandatory level for V5.3.1.12:\n\n- H06.23.01 or later\n- SPR T8306H01^ABJ or later\n- SPR T8994H01^AAM or later\n- SPR T8397H01^ABD or later\n- SPR T1248H06^AAX or later\n\n\nFor the HP Integrity NonStop BladeSystem J-Series systems, the following\nsystem software versions are the minimum mandatory level for V5.3.1.12:\n\n- J06.14.00 or later\n\nNote that V5.3.1.12 is not supported on G-Series systems\n\nRecommended SPRs\n-----------------\nIt has become increasingly complicated to document fixes made by HP\nfor some of their products, as the products themselves often have multiple\nthreads (H01, H02, G01, G06 etc..) that can be used on multiple OS levels.\n\nTo make it more convenient for our customers to determine whether they already\nhave a recommended fix installed, or to find the appropriate fix in Scout on\nthe NonStop eServices Portal, we are now referencing particular problems by\ntheir HP solution number.\nIf you wish to determine whether your particular level of an SPR contains\nthe solution, review the document included when you downloaded the product\nfrom Scout or review the softdocs in Scout for the solution number for that\nproduct.\n\nWe have added more information about the specific problems reported,\nwhat the symptoms are, workarounds to these problems if relevant,\nand the likelihood of it happening.\nPlease note:\nWhere versions are inside parentheses beside an HP solution #,\nthose versions only are affected by that particular solution.\n\nProduct ID: T0845 - Pathway Domain Mgmt Interface\/TS\/MP 2.5\nProblem: PATHCTL file can be corrupted if a pathway serverclass abends. \nSymptom: Pathway unusable\n(Reported as possible by HP but not independently confirmed by IBM).\nHP Solution: 10-120322-2183\nLikelihood: Possible\nWorkaround: None\nRecovery: May be possible to re-configure the WMQ serverclasses in some circumstances.\n\nProduct ID: T1248 - pthreads\nProblem: Threaded server application, MCA - amqrmppa_r, causes 100% CPU\nutilization\nHP Solution: 10-080818-5258 (H07, H06, G07)\nSymptom: CPU 100% busy while processing SSL channels. MCA process consumes\nall available CPU. May be communication errors on channels\nLikelihood: Certain when attempting to Stop SSL Channels using Mode Terminate\n\nif priority of MCA process is higher than Channel Servers\nWorkaround: For SSL channels use unthreaded MCAs or upgrade to WMQv5.3.1.4\nRecovery: None, CPUs will go back to normal after about 5 mins\n\n\nProblem: Assert in spt_defaultcallback for threaded MCAs, amqrmppa_r\nHP Solution: 10-080519-3266 (H06, G07)\nSymptom: FDCs from MCAs, plus MCAs abend (qmgr log message), channels fail\nand restart. Error 28 seen in FFST from MCA process on WRITEREADX\ncall\nLikelihood: Rare.\nWorkaround: Use unthreaded MCAs\nRecovery: None, MCAs will abend but MCAs and associated channels will\nrestart\n\nProduct ID: T6533 - STDSEC-STANDARD SECURITY PROD\nProblem: The GROUP_GETINFO_ Guardian procedure call used by dspmqusr returns error 590 with\ngroup ID greater than 65535.\nSymptom: dspmqusr abends with AMQ7047: An unexpected error was encountered by a command.\nFFST generated reports error 590.\nHP Solution: SOLN 10-091111-6280\nLikelihood: Definite if a user is created in group with a group ID greater than 65535,\neg. SECURITY-ENCRYPTION-ADMIN and that user id added as a principal.\nWorkaround: Members of a group with group ID greater than 65535 cannot be added as WMQ principal\nRecovery: None\n\nProduct ID: T8306 - OSS Sockets Version: H04, H02, G12, G10\nProblem: OSS socket APIs fail with ENOMEM (4012) error.\nHP Solution: 10-081205-7769. (H04, G12)\nSymptoms: Channels fail to start, Error log and FFSTs indicate error 4012.\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU.\n\nProblem: CPU halt %3031 and CPU Freeze %061043 after CPU down testing.\nSymptoms: All processes in the CPU will end,,, backup NonStop processes\nwill take over. Error log will indicate backup servers have taken\nover.\nHP Solution: 10-080827-5452. (H04, H02, G12, G10)\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU\n\n\nProduct ID: T8397- OSS Socket Transport Agent\nProblem CPU Halt %3031 or CPU Freeze %061043\nSymptoms All processes in the CPU will end, backup NonStop processes will\ntake over. Error log will indicate backup servers have taken over.\nHP Solution: 10-080827-5452 (H02, H01, G11)\nLikelihood: Rare\nWorkaround: Reload CPU\n\nProblem: OSS socket APIs fail with ENOMEM (4012) error.\nSymptom: Channels fail to start. Error log and FFSTs indicate error\n4012.\nHP Solution: 10-081205-7769 (H02, G11)\nLikelihood: Rare\nWorkaround: None\nRecovery: Reload CPU\n\n\nProduct ID: T8607 - TMF\nProblem: Multiple issues involving lost signals with OpenTMF\nSymptom: Channel Server indicates Sequence number mismatches. Channel\nserver generates FDCs that report file system error 723.\nHP Solution: 10-081027-6812, Hotstuff HS02990. (H01)\nLikelihood: Rare, but may occur if audit trail is 90% full, or operator stops\nTMF.\nWorkaround: Monitor audit trail size\nRecovery: Stop primary channel server process.\n\nSymptom: Queue Manager completely freezes up, Log messages every 10 seconds\nfor 50 attempts.\nHP Solution: 10-081027-6812, Hotstuff HS02990. (H01)\nLikeihood: Very likely if STOP TMF, ABRUPT command is issued while Queue\nManagers are running.\nWorkaround: Do not issue STOP TMF, ABRUPT command while queue managers are \nrunning until the SPR has been installed.\nRecovery: Restart Queue Manager.\n\n\nProduct ID: T8620 - OSS file system Version: G13,H03, H04\nProblem: lseek() fails with errno 4602.\nSymptoms: FFSTs generated in xcsDisplayMessage component\nHP Solution: SOLN 10-071012-8159 (G13,H03, H04)\nLikelihood: Likely\nWorkaround: Turn off OSS Caching in all disks\nRecovery: None needed, problem is benign.\n\nSymptoms: Queue Manager slowdown along with (sometimes) lost log messages\nin busy queue managers. System suffered major OSS lockups and CPU\nhalts\nHP Solution: SOLN 10-071012-8159 (G13,H03, H04)\nLikelihood: Rarely\nWorkaround: None\nRecovery: Stop and restart all Queue Managers and Listeners. Reload CPUs.\n\nIf you use SNA channels with V5.3.1, we recommend the latest levels of the\nHP SNAX or ACI Communication Services for Advanced Networking (ICE) be used\nfor the SNA transport. The following versions were verified by IBM with this\nrelease of WMQ:\n\nACI Communication Services for Advanced Networking (ICE)\n- v4r1 on both HP Integrity NonStop Server and S-Series systems\n\nHP SNAX\n- T9096H01 on HP Integrity NonStop Server (H-Series) systems\n\nIf you use the WebSphere MQ V5.3 classes for Java and JMS for HP NonStop Server\nyou will need to install HP NonStop Server for Java Version 1.4.2 or later.\nThe Java.pdf supplemental document in the <install_path>\/opt\/mqm\/READMES\/en_US\ndirectory has been updated in this release. Java\/JMS users should review the \nupdated document.\n\nUpgrading to V5.3.1.12\n---------------------\n\nFor systems running H Series operating systems, you may upgrade\nany prior service level of WebSphere MQ V5.3.1.x for HP NonStop Server to\nV5.3.1.12 level using this release. For NonStop BladeSystem running J series\noperating systems, you may upgrade from version V5.3.1.4 only, since V5.3.1.4\nis the earliest supported version on J series. If you need to perform a full\ninstallation on a J series system from the original installation media, see the\nsection later in this readme file for instructions.\n\nThe installation tool, svcmqm, is used to upgrade existing installations\nto this level. Additionally, the placed files for any prior level of V5.3.1\ncan be overlaid with the new files from V5.3.1.12 and then instmqm can be used\nto create new installations at the updated V5.3.1.12 level.\n\nYou must end all queue managers and applications in an installation if you\nwant to upgrade that installation to V5.3.1.12.\n\nYou do not need to re-create any queue managers to upgrade to V5.3.1.12.\nExisting queue managers (at any V5.3.1.x service level) will work with\nV5.3.1.12 once an installation has been properly upgraded.\n\nIf you use SSL channels, and are upgrading from WMQ V5.3.1, you must perform\na small reconfiguration of the Certificate store before running any SSL\nchannels after you have upgraded. The steps that are required are described\nbelow in the Post-Installation section. If you do not perform this\nreconfiguration, SSL channels in the upgraded V5.3.1.12 installation will\nfail with the log messages similar to the following:\n\nFor sender channels:\n\n09\/29\/07 08:52:43 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)\nAMQ9621: Error on call to SSL function ignored on channel\n'ALICE_BOB_SDRC_0000'.\n\nEXPLANATION:\nAn error indicating a software problem was returned from a function which is\nused to provide SSL support. The error code returned was '0xB084002'. The error\nwas reported by openssl module: SSL_CTX_load_verify_locations, with reason:\nsystem lib. The channel is 'ALICE_BOB_SDRC_0000'; in some cases its name cannot\nbe determined and so is shown as '????'. This error occurred during channel\nshutdown and may not be sufficiently serious as to interrupt future channel\noperation; Check the condition of the channel.\nACTION:\nIf it is determined that Channel operation has been impacted, collect the items\nlisted in the 'Problem determination' section of the System Administration\nmanual and contact your IBM support center.\n---- amqccisx.c : 1411 ------------------------------------------------------\n09\/29\/07 08:52:44 Process(0,483 $Z8206) User(MQM.ABAKASH) Program(amqrmppa)\nAMQ9001: Channel 'ALICE_BOB_SDRC_0000' ended normally.\n\nEXPLANATION:\nChannel 'ALICE_BOB_SDRC_0000' ended normally.\nACTION:\nNone.\n\nFor client or receiver channels:\n\n-------------------------------------------------------------------------------\n09\/29\/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)\nAMQ9620: Internal error on call to SSL function on channel '????'.\n\nEXPLANATION:\nAn error indicating a software problem was returned from an function which is\nused to provide SSL support. The error code returned was '0x0'. The error was\nreported by openssl module: SSL_load_client_CA_file, with reason: CAlist not\nfound. The channel is '????'; in some cases its name cannot be determined and\nso is shown as '????'. The channel did not start.\nACTION:\nCollect the items listed in the 'Problem determination' section of the System\nAdministration manual and contact your IBM support center.\n---- amqccisx.c : 1347 ------------------------------------------------------\n09\/29\/07 08:05:28 Process(1,802 3 $X0545) User(MQM.HEMA) Program(amqrmppa_r)\nAMQ9228: The TCP\/IP responder program could not be started.\n\nEXPLANATION:\nAn attempt was made to start an instance of the responder program, but the\nprogram was rejected.\nACTION:\nThe failure could be because either the subsystem has not been started (in this\ncase you should start the subsystem), or there are too many programs waiting\n(in this case you should try to start the responder program later). The reason\ncode was 0.\n\nWMQ Application re-compile Considerations :\n\nYou do not need to re-compile any applications to upgrade to V5.3.1.12.\n\nWMQ Application linkage Considerations :\n\na) If upgrading from V5.3.1.5 or later releases (including patch releases) :\n\nExisting applications will continue to work with V5.3.1.12 release. However, \nIBM strongly recommends that if you are upgrading from a release prior to \n5.3.1.7, you review the impact of APARs IC67057 and IC68569 that were fixed in\nthe V5.3.1.7 release. Please also note internal defect 4158 that is fixed in \nV5.3.1.11. The IC67057, IC68569 and internal defect 4158 fixes will not be \neffective in non-native applications unless the applications are relinked \nusing the HP BIND utility. \n\nb) If upgrading from V5.3.1.4 or earlier releases (including patch releases) :\n\nYou MUST use the HP BIND utility to relink any non-native applications prior\nto using them with V5.3.1.12. If an application is not re-bound with the \nV5.3.1.12 WMQ product, MQCONN API calls will fail with a MQRC 2059 and the \nWMQ EC process will output an FDC when the MQI incompatibility is detected, \nas follows:\n\nProbe Id :- EC075003\nComponent :- ecaIsECup\nComment1 :- Application MQ API not compatible, relink application\nComment2 :- <process cpu,pid process name>\nComment3 :- <application executable name>\n\nInstallation from Electronic Software Download H or J Series based systems\n-----------------------------------------------------------------------------\n\nThese instructions apply to installing WebSphere MQ for HP NonStop Server,\nVersion 5.3.1.12, from the package downloaded from IBM. Please note the\nadditional restrictions for upgrading J Series systems to this version.\n\nUse svcmqm to update an existing installation from the V5.3.1.12 placed files.\n\n1. Unzip the fixpack distribution package - wmq53.1.12.tar.zip.\nThe fixpack distribution package contains the following files:\n\nreadme_wmq_5.3.1.12 - this README\nwmq53.1.12_H07.tar.Z - H-Series H06 Package\n\n2. Identify the correct fixpack package to install:\n\nFor H-Series (H06) or J-Series systems (J06) use: wmq53.1.12_H06.tar.Z\n\n3. Upload the compressed fixpack archive to the OSS file system in binary mode.\nYou may wish to store the compressed archive, and the expanded contents\nin a location where you archive software distributions from IBM.\nIf you do this, you should store the compressed archive in a directory\nthat identifies the version of the software it contains,\nfor example, \"V53112\".\n\nmkdir -p \/usr\/ibm\/wmq\/V53112\nupload (in binary mode) the correct compressed tarfile to this directory\n\n4. Extract the fixpack compressed tarfile using commands similar to:\n\ncd \/usr\/ibm\/wmq\/V53112\nuncompress wmq53.1.12_H06.tar.Z\n\ntar xvof wmq53.1.12_H06.tar\n\n5. Locate your WMQ V5.3.1.x installation(s). The service installation procedure\nrequires the full OSS path names of the opt\/mqm and var\/mqm directories for\neach WMQ installation to which the fixpack will be installed.\n\n6. Logon to OSS using the WMQ installation owner's userid\n\n7. End all Queue Managers defined in the WMQ Installation.\nendmqm <qmgr name>\n\nEnsure all Queue Managers defined in the WMQ installation\nare ended.\ndspmq\n\nEnsure that the WMQ installation is at a suitable V5.3.1 level.\nmqver -V\nSee later notes concerning version requirements for NonStop BladeSystem\ninstallation.\n\n8. End any non-Pathway listeners for Queue Managers defined in the\nWQM installation:\nendmqlsr -m <qmgr name>\n\n9. Verify that no files in the Guardian subvolumes of the installation to\nbe updated are open. The installation cannot proceed safely unless all\nfiles in these subvolumes are closed. Use the TACL command 'FUP LISTOPENS'\nfor the files in all three subvolumes - an absence of output indicates\nthat no files are open. If files are shown to be open, use the output\nfrom the command to identify processes that are holding files open.\n\n\n10. Backup your WMQ Installation; the fixpack cannot be uninstalled.\ninstmqm -b can be used to back up an installation. Please refer\nto the readme file included with release WMQ V5.3.1.\n\n11. Install the fixpack by running the supplied service tool (svcmqm).\nSvcmqm requires the location of the OSS var tree as well\nas the OSS opt tree. These locations can be supplied automatically by\nrunning svcmqm in an OSS shell where the environment variables for the\nWMQ installation being updated have been established (typically by\nsourcing \"wmqprofile\"). If this is the case, svcmqm does not require the\n-i and -v parameters. \n\nFor example:\ncd \/usr\/ibm\/wmq\/V53112\nopt\/mqm\/bin\/svcmqm -s \/usr\/ibm\/wmq\/V53112\/opt\/mqm\n\nIf the environment variables for the WMQ installation are not established in \nthe environment of svcmqm or if you want to update a WMQ installation other\nthan the one that your current WMQ environment variable points to, then \nthe locations of the OSS opt and var trees must be supplied explicitly using\nthe svcmqm command line parameters -i and -v.\n\nFor example:\n\ncd \/usr\/ibm\/wmq\/V53112\nopt\/mqm\/bin\/svcmqm -s \/usr\/ibm\/wmq\/V53112\/opt\/mqm\n-i \/wmq1\/opt\/mqm\n-v \/wmq1\/var\/mqm\n\nsvcmqm will prompt to confirm the location of the OSS opt tree for the\ninstallation to be updated.\nType \"yes\" to proceed.\n\nSvcmqm will then update the installation. The current WMQCSTM file for\nthe installation will be renamed to BWMQCSTM as a backup copy, before it\nis regenerated. Note that any changes to the WMQCSTM file you have made\nwill not be copied to the new WMQCSTM file, however they will be preserved\nin the backup copy made before the WMQCSTM file was regenerated.\n\n12. Repeat Steps 5-11 for any other WMQ installations that you want to update\nwith this fixpack.\n\n13. You can install this fixpack in the WMQ placed installation files so that\nany future WMQ product installations will include the fixpack updates.\n\nTo do this, locate your WMQ placed installation filetree containing the\nopt directory, make this your current working directory (use 'cd') and\nthen unpack the contents of the tar archive for this fixpack over the placed\nfile tree. For example, if the placed files are located in the default\nlocation \/usr\/ibm\/wmq\/V531, for a H-Series system:\n\ncd \/usr\/ibm\/wmq\/V531\ntar xvof \/usr\/ibm\/wmq\/V5319\/wmq53.1.12_H06.tar\n\nInitial Installation on a NonStop BladeSystem\n---------------------------------------------\n\nThese instructions apply to installing WebSphere MQ for HP NonStop Server on\na NonStop BladeSystem using the original installation media, in conjunction\nwith the 5.3.1.12 package downloaded from IBM. NonStop BladeSystem platforms\nare not supported prior to V5.3.1.4, and a \"from scratch\" installation requires\neither V5.3.1.4 or later files to be overlaid on a set of placed files\nfrom the base product media prior to performing the installation.\nYou do NOT need to perform these steps if you have already installed V5.3.1.4\non your NonStop BladeSystem. In this case, follow the standard installation\nsteps earlier in this readme file.\n\n1. Place the files for the Refresh Pack 1 (5.3.1.0) version of WebSphere MQ\n\nfor HP NonStop Server on the target system. Refer to the \"File Placement\"\nsection in Chapter 3 of the \"WebSphere MQ for NonStop Server Quick\nBeginnings\" guide. Pages 11-13 describes how to place the files.\nDo not attempt to install the placed files using the instmqm script\nthat was provided with V5.3.1.0 at this time. The V5.3.1.0 version of\ninstmqm does not support installation on NonStop BladeSystem.\n\n2. Unzip the 5.3.1.12 fixpack distribution package - wmq53.1.12.tar.zip.\nThe fixpack distribution package contains the following files:\n\nreadme_wmq_5.3.1.12 This README\nwmq53.1.12_H06.tar.Z H-Series H06 Package\n\n3. This installation requires the wmq53.1.12_H06.tar.Z package.\nLocate the WMQ placed installation filetree containing the opt directory\nprepared in step 1 above, and upload the wmq53.1.12_H06.tar.Z fixpack\narchive to this location in binary mode.\n\n4. Extract the fixpack compressed tarfile using commands similar to:\n\ncd \/usr\/ibm\/wmq\/V53112\nuncompress wmq53.1.12_H06.tar.Z\n\n5. Unpack the contents of the extracted tar archive for this FixPack over the\nplaced file tree. For example, if the placed files are located in the default\nlocation \/usr\/ibm\/wmq:\n\ncd \/usr\/ibm\/wmq\ntar xvof \/usr\/ibm\/wmq\/V53112\/wmq53.1.12_H06.tar\n\n6. Use the extracted instmqm script in this FixPack to install the product\nusing the updated installation file tree and the instructions in Chapter 3\nof \"WebSphere MQ for NonStop Server Quick Beginnings\" guide, pages 13-29.\nBefore beginning, review the list of changes to Chapter 3 detailed in the\n\"Documentation Updates\" section at the end of this README file. Note also\nthat the list of installed files displayed will differ from those shown in the\nexamples in the manual.\n\nPost-Installation\n-----------------\nIf upgrading from WMQ V5.3.1, read the following post-installation instructions:\n\nNon-Native TNS Applications:\n\nRe-BIND any non-native (TNS) applications. See \"Upgrading to V5.3.1.12\" above \nfor more information.\n\nRe-binding non-native (TNS) is REQUIRED if upgrading from V5.3.1.4 or earlier\nreleases but is RECOMMENDED if upgrading from V5.3.1.5 or later fixpack for \nincorporation of APARs IC67057, IC68569 and internal defect 4158. \n\nIf you use SSL channels and have not already installed V5.3.1.1:\n\nEdit the SSL certificate store, cert.pem and move all the CA certificates\nto a new file, trust.pem, stored in the same directory as cert.pem. The\nonly items that should remain in cert.pem are the queue manager's personal\ncertificate, and the queue manager's private key. These two items should\nbe located at the start of the cert.pem file. All other certificates\n(intermediate and root CAs) must be moved to trust.pem. The trust.pem file\nmust be in the same directory as cert.pem, as configured in the queue\nmanager's SSLKEYR attribute.\n\nUpdate the copy of the entropy daemon program that you run for SSL channels\non the system with the new version (...opt\/mqm\/ssl\/amqjkdm0).\n\nEnable new support for Danish CCSID 65024:\n\nCustomers who wish to enable the new support for Danish CCSID 65024\nshould do the following to install the revised ccsid.tbl file:\n\nIssue the following commands on OSS:\n\n1. Logon to OSS using the WMQ installation owner's userid\n2. End all Queue Managers defined in the WMQ Installation.\nendmqm <qmgr name>\n3. Source in the installation's wmqprofile\n. $MQNSKVARPATH\/wmqprofile\n4. cp -p $MQNSKOPTPATH\/samp\/ccsid.tbl $MQNSKVARPATH\/conv\/table\/\n5. Start queue managers\n\nGuardian C++ DLLs:\n\nEnsure that the WMQ Guardian C++ DLLs are 'executable' by using \"FUP ALTER\"\nto set their FILECODE to 800 (for H-Series or J-Series). Use commands similar \nto the following:\n\n1. Logon to TACL using the WMQ installation owner's userid\n\n2. OBEY your WMQ Installation's WMQCSTM file\n3. VOLUME [#param MQNSKOPTPATH^LIB^G]\n4. FUP ALTER IMQI2,CODE 800\n5. FUP ALTER IMQI2T,CODE 800\n6. FUP ALTER IMQI3,CODE 800\n7. FUP ALTER IMQI3T,CODE 800\n8. Logoff\n\nGuardian Subvolume File Permissions\n\nThe WMQ Guardian Installation Subvolume and all WMQ Guardian Queue\nManager Subvolumes must accessible to both MQM group members\nand to users that run WMQ application programs.\n\nEnsure that:\n\nAll members of the MQM security group have read, write, execute\nand purge permission to these subvolumes.\n\nAll users that run WMQ application programs, have read, write\nand execute permission to these subvolumes\n\nRestart Queue Managers:\n\nRestart the queue managers for the installation you have\nupdated with this fixpack.\n\nUNINSTALLATION INFORMATION\n==========================\n\nThis fixpack cannot be automatically uninstalled if a problem occurs\nduring the update of an installation using svcmqm.\n\nYou should use the instmqm -b option to create a backup of an\ninstallation before applying the service. If a problem occurs\nor you need to reverse the upgrade at a later date, use the\ninstmqm -x option to restore a backup of the installation at the\nprior service level.\n\nKNOWN LIMITATIONS, PROBLEMS AND WORKAROUNDS\n===========================================\n\nThis section details known limitation, problems, and workarounds for\nWebSphere MQ for HP NonStop Server, Version 5.3.1.12.\n\nLimitations\n-----------\n\n1. The current implementation of Publish \/ Subscribe is restricted to run\nwithin a single CPU. The control program and all \"worker\" programs run in\nthe CPU that was used to run the 'strmqbrk' command.\nThe Publish\/Subscribe broker does not automatically recover in the event\nof CPU failures.\n\n2. The current memory management implementation in the Queue Server limits\nthe total amount of non-persistent message data that can be stored on all\nthe queues hosted by a single Queue Server to less than 1Gb. The limit of\nnon-persistent message data on a single queue can not exceed approximately\n1Gb therefore, even if a single Queue Server is dedicated to that queue.\n\n3. The number of threads in threaded agent processes (LQMAs or MCAs) or in MQI\napplications, is limited to a maximum of 1000 by the limit on open depth of\nthe HP TMF T-file.\n\n4. API exits are not supported for non-native (TNS) applications. Any other\nexit code for non-native applications must be statically bound with the\nTNS application.\n\n5. Cluster workload exits are only supported in \"trusted\" mode. This means\nthat a separate copy of each exit will run in each CPU and exit code in\none CPU cannot communicate with exit code in another CPU using the normal\nmethods provided for these exits.\n\n6. Upgmqm will not migrate the following data from a V5.1 queue manager:\nmessages stored in Message Overflow files (typically persistent messages\nover 200,000 bytes in size) will not be migrated. If the option to\nmigrate message data was selected, the upgrade will fail. if the option\nto migrate message data was not selected, the upgrade will not be\naffected by the presence of message overflow files.\nclustering configuration data - all cluster related attributes of objects\nwill be reset to default values in the new V5.3 queue manager.\nSNA channel configuration - channels will be migrated, but several of the\nattributes values will need to be changed manually after the upgrade.\nchannel exit data - attributes in channels that relate to channel exit\nconfiguration will be reset to default values in the new V5.3 queue\nmanager.\nIn all cases where upgmqm cannot migrate data completely, a warning message\nis generated on the terminal output as well as in the log file. These can\nbe reviewed carefully after the upgrade completes for further actions that\nmay be necessary.\n\n7. Java and JMS limitations\n\nThe Java and JMS Classes do not support client connections. WebSphere MQ\nfor HP NonStop Server does not support XA transaction management, so the\nJMS XA classes are not available. For more detail, please refer to the\nJava and JMS documentation supplement, Java.pdf.\n\n8. Control commands in Guardian (TACL) environment do not obey the RUN option\n\"NAME\" as expected\n\nA Guardian control command starts an OSS process to run the actual\ncontrol command - and waits for it to complete. When the NAME option is\nused, the Guardian control command process uses the requested name, but\nthe OSS process cannot and is instead named by NonStop OS.\n\nIf the Guardian control command is prematurely stopped by the operator\n(using the TACL STOP command for example) the OSS process running the\nactual control command may continue to run. The OSS process may need to be\nstopped separately and in addition to the Guardian process.\n\n9. Trace doesn't end automatically after a queue manager restart\n(APAR IC53352) and trace changes do not take effect immediately\n\nIf trace is active and a queue manager is restarted, the trace settings\nshould be reset to not trace any more. Instead, the queue manager\ncontinues tracing using the same options as before it was restarted.\nThe workaround is to disable trace using endmqtrc before ending, or while\nthe queue manager is ended.\n\nAlso, changes to trace settings do not always take effect immediately\nafter the command is issued. For example, it could be several MQI calls\nlater that the change takes effect. The maximum delay between making a\ntrace settings change and the change taking effect would be until the end\nof the queue manager connection, or the ending of a channel.\n\n10. Some EMS events generated to default collector despite an alternate\ncollector being configured (APAR IC53005)\n\nAn EMS event message \"FFST record created\" is generated using the OSS\nsyslog() facility whenever an FDC is raised by a queue manager. This\nEMS event cannot be disabled, and goes to the default collector $0. For\nOSS processes, an alternate collector process can be specified by\nincluding an environment variable in the context of these processes\nas in the following example:\n\nexport EMS_COLLECTOR=\\$ALT\n\nGuardian processes always use the default collector because HP do not\nprovide the ability to modify the collector in the Guardian environment.\nHP is investigating if a change is possible. No fix for this problem\nhas yet been identified.\n\n11. The use of SMF (virtual) disks with WMQ is not supported on Release\nVersion Updates prior to H06.26 and J06.15 because of restrictions\nimposed by the OSS file system. For more details, please refer to the\nHP NonStop Storage Management Foundation User's Guide Page 2-12.\n\n12. The maximum channel batch size that can be configured (BATCHSZ attribute)\nis 2000. If you need to run channels with batch sizes greater than 680\nyou must increase the maximum message length attribute of the\nSYSTEM.CHANNEL.SYNCQ to 60000.\n\ne.g. from RUNMQSC - ALTER QL (SYSTEM.CHANNEL.SYNCQ) MAXMSGL (60000)\n\n13. The SYSTEM.CHANNEL.SYNCQ is a critical system queue for operation of\nthe queue manager and should not be altered to disable MQGET or MQPUT\noperations, or to reduce the maximum message size or maximum depth\nattributes from their defaults.\n\n14. Currently, the cluster transmission queue (SYSTEM.CLUSTER.TRANSMIT.QUEUE)\ncannot be moved to an alternative Queue Server because it is constantly\nopen by several internal components. The following procedure (which\nrequires a \"quiet\" queue manager, and a queue manager restart) can be\nused to achieve this reconfiguration. Do not use this procedure on a\nqueue manager that is running in production. Read and understand the\nprocedure carefully first since it includes actions that cause\ninternal errors to be generated in the queue manager.\n\n1\/ Rename the OSS repository executable (opt\/mqm\/bin directory)\nmv amqrrmfa amqrrmfax \n2\/ From OSS enter 'ps -f | grep amqrrmfa | grep X '\nwhere X is the Queue Manager name.\n3\/ kill -9 those processes returned from step 2\nAt this point the EC will start continuously generating FDCs and\nlog messages as it attempts to, and fails, to restart the repository\nservers that were stopped. Perform the remaining steps in this\nprocedure without delay to avoid problems with excessive logging\nsuch as disk full conditions.\n4. Verify the processes are stopped\nFrom OSS enter 'ps -f | grep amqrrmfa | grep X '\nWhere X is the Queue Manager name\n5. Issue the altmqfls --server command to move the cluster transmission\nqueue to an alternate queue server\n6. Issue dspmqfls to verify the alternate server assignment\n7. Rename the OSS repository executable back to the expected name\nmv amqrrmfax amqrrmfa\n8. End the queue manager using preemptive shutdown. The EC will generate\nFDCs ending because of the earlier attempts to start a repository\nmanager while the executable was renamed. There will be FDCs and\nEC Primary process failover\n\nComponent :- xcsExecProgram\nProbe Description :- AMQ6025: Program not found\nComment1 :- No such file or directory\nComment2 :- \/opt\/mqm\/bin\/amqrrmfa\n...\nAMQ8846: MQ NonStop Server takeover initiated\nAMQ8813: EC has started takeover processing\nAMQ8814: EC has completed takeover processing\n...\nThe EC may have to be manually TACL stopped if quiesce or immediate\nend is used thus the need for the preemptive shutdown\nendmqm -p <qmgr name>\n9. Rename the repository manager executable to the original name\nmv amqrrmfax amqrrmfa\n10. Restart the queue manager\nstrmqm <qmgr name>\n\n15. In Guardian\/TACL environments, support for some WMQ command-line programs\nhas been deprecated for WMQ Fixpack 5.3.1.3 and later.\n\nThe affected command-line programs are:\n\namqoamd\namqrdbgm\namqrfdm\ncrtmqcvx\nendmqlsr\nrunmqchi\nrunmqchl\nrunmqdlq\nrunmqlsr\nrunmqtrm\n\nThese programs will continue to function for now, however their use in\nGuardian\/TACL environments is discouraged. Support for these programs\nin Guardian\/TACL environments may be withdrawn completely in a future\nWMQ 5.3 release\/fixpack.\n\nIBM recommends that customers use the OSS version of these programs instead.\n\nCustomers who want to route output from WMQ OSS tools to VHS or other Guardian\ncollectors should use the OSSTTY utility. OSSTTY is a standard utility\nprovided by OSS and is described in the HP publication \"Open System Services\nManagement and Operations Guide\".\n\nNote: See Item 3. in \"Known problems and workarounds\" for a description of\nrestrictions when using the MQ Broker administration commands in the\nGuardian\/TACL environment.\n\n16. Do not use WebSphere MQ with a $CMON process that alters attributes of WMQ\nprocesses (for example the processor, priority, process name or program\nfile name) when they are started. This is not a supported environment since\nthere are components in WMQ that rely on these attributes being set as\nspecified by WMQ for their correct operation.\n\n17. Support for forked processes\n\nMQI Support from forked processes in OSS is subject to the following\nrestrictions:\n1. If forking is used, MQI operations can be performed only from child\nprocesses. Using MQI verbs from a parent process that forks child\nprocesses is not supported and will result in unpredictable\nbehavior.\n\n2. Use of the MQI from forked processes where the parent or child is\nthreaded is not supported.\n\n18. TMF Outage handling\n\nTMF outage handling was significantly improved with V5.3.1.4, however there\nis still a limitation in V5.3.1.6 and later to be aware of:\n\n1. If a STOP TMF, ABRUPT command is issued, TMF marks all open audited\nfiles as corrupt and the queue manager cannot perform further\nprocessing until this condition is rectified by restarting TMF.\nIn this state, the queue manager will freeze further operation, and log\nthe condition in the queue manager log file every 10 seconds for a\nmaximum of 50 attempts. Whether or not TMF is restored within this\ntimeframe, the WMQ queue manager should be restarted to reduce the risk\nof any undetected damage persisting.\n\n19. Triggering HP NSS non-C Guardian applications\n\nThe MQ default Trigger Monitor process, runmqtrm, at present cannot\ndirectly trigger the following application types:\n\nGuardian TACL scripts or macro file\nCOBOL application\nTAL application\nAn OSS script file (wmqtrig) provides indirect support for these\nfiles types. To use this script, the PROCESS definition APPLTYPE should\nbe set to UNIX, and the APPLICID should refer to the script as in\nthe following examples:\n\nFor a TACL script called \"trigmacf\":\nAPPLICID('\/opt\/mqm\/bin\/wmqtrig -c \\$data06.fp4psamp.trigmacf')\nAPPLTYPE(UNIX)\n\nFor a COBOL or TAL application called \"mqsecha\":\nAPPLICID('\/opt\/mqm\/bin\/wmqtrig -p \/G\/data06\/fp4psamp\/mqsecha')\nAPPLTYPE(UNIX)\n\n\nNotes:\n1. TACL scripts use the wmqtrig script with a \"-c\" option.\nThe -c option should use the Guardian representation for file name\nof the TACL script file, with the special character ($) escaped,\nfor example:\n\n\\$data06.fp4psamp.trigmacf\n\n2. COBOL and TAL applications use the wmqtrig script with a \"-p\" option.\nThe -p option must use the OSS representation for the file name of\nthe application, for example:\n\n\/G\/data06\/fp4psamp\/mqsecha\n\n3. C applications can be triggered directly by specifying\n\nAPPLICID('$DATA06.FP4PSAMP.MQSECHA')\nAPPLTYPE(NSK)\n\nTo trigger a PIC application using the WMQ Pathway MQS-TRIGMON00\nserverclass, a DEFINE is required:\n\n=_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 <Guardian MQ binary Volume.Subvolume>\n\nFor example:\nALTER MQS-TRIGMON00,\nDEFINE =_RLD_LIB_PATH,CLASS SEARCH,SUBVOL0 $DATA06.FP4PBIN\n\n4. If the \"-p\" option is used, gtacl passes the complete MQTMC2 structure\ntext (which is 560 bytes) to the application being triggered, whereas if\nthe \"-c\" option is used, limitations in TACL will cause the triggered \napplication to receive 520 bytes only.\nApplications intended to be triggered using -p option must handle the \ncomplete 560 character startup character string.\nThis can cause problems, particularly with COBOL applications;\nSince a COBOL GETSTARTUPTEXT call can process only 529 characters,\ntriggering a COBOL application with the -p option (560 character startup\nstring) can result in a memory overwrite and application abend.\nIn this case, the -c option should be used instead of the -p option.\"\n\n20. Maximum numnber of LQMA processes\n\nThe maximum number of LQMA processes per queue manager is 1417. Attempts to\nconfigure a MaxUnthreadedAgents value of 1418 or greater in the qmproc.ini file\nwill result in FDCs when the queue manager attempts to start the 1418th LQMA.\n\n21. Limitation on ProcessNameRoot values in qmproc.ini file\n\nThe ProcessNameRoot value used in the qmproc.ini file for the MCA, LQMA and \nRepositoryManager stanzas must be unique across all queue managers in all\ninstallations on the system. If the values are not unique, two queue \nmanagers attempting to create a new process name at the same time may attempt\nto use the same sequence of names, resulting in heavy load on the OSS\nnameserver and\/or FDCs with probes EC062000 from eclStartMCA or EC065000 from\neclStartLQMA. This may result in the queue manager becoming unresponsive.\n\n22. BIND\/REPLACE Warning 9\n\nThe use of BIND\/REPLACE when re-binding non-native (TNS) applications with \nthe latest WMQ TNS Library is supported, however, when using this command, \nyou may encounter many Bind 'warning 9' messages. These warnings are safe to\nignore, as the changes made in the MQMTNS library are completely contained\nwithin that library and there is no external affect on an application that\nwould link with that library. Please refer to document \nID mmr_ns-4.0.6050052.2565545 in KBNS which has been updated by HP to include\nthis information. \n\n23. PING CHANNEL uses the =TCPIP^PROCESS^NAME DEFINE as opposed to the \nvalue set in the qmproc.ini file.\n\nIf the TCPIP^PROCESS^NAME DEFINE is invalid, attempts to issue a \nPING CHANNEL request will fail with the following message -\n\":AMQ9212: A TCP\/IP socket could not be allocated.\"\n\n24. Using multiple cluster receiver channels for a queue manager can cause the \nmaster and slave repository managers to get out of sync in some configurations, \nthis results in FFSTs from rrmHPNSSGetMetaPacket with Comment1 field \n\"Meta data mis-match Expected: metalen=xx\".\nThe root cause of this problem has not been identified definitively, but it is\nrecommended that cluster configurations do not use multiple cluster receiver \nchannels for the same cluster on a given queue manager.\n\n25. Format 2 Queue and Queue overflow files are not supported\n\nIf an attempt is made to use altmqfls to change extent size or max extents of \na Queue or Queue overflow file such that the new file size would require a\nformat 2 file, the attempt will fail and an FDC file containing the following\n\nProbe Id :- XC066050 \nComponent :- xgcDupPartFile \n... \nMajor Errorcode :- xecF_E_UNEXPECTED_RC \nMinor Errorcode :- krcE_UNEXPECTED_ERROR \nProbe Description :- AMQ6118: An internal WMQ error has occurred \n(20800893) \n...\nArith1 :- 545261715 20800893 \n\n26. RUNMQSC DISPLAY QSTATUS(*) TYPE(HANDLE) ALL can return only 500 handles\n\nThe current implementation of DISPLAY QSTATUS can handle only 500 queue\nhandles. In prior releases, executing the command in a scenario where there\nwere more than 500 handles resulted in an error return and large numbers of \nFFSTs (see internal defect 2230 earlier in this readme). These errors are the\nresult of a design limitation with the DISPLAY QSTATUS implementation. \nThe processing of the command has been modified to handle the scenario cleanly\nand return only the first 500 handles retrieved, as supported by the design.\n\nKnown problems and workarounds\n------------------------------\n1. FDCs from Component xcsDisplayMessage reporting xecF_E_UNEXPECTED_SYSTEM_RC\n\nOn RVUs H06.06 and later:\n\nThese FDCs occur frequently on queue manager shutdown, and at times during\nqueue manager start, from processes that write to the queue manager log\nfiles at these times, typically the cluster repository cache manager\n(amqrrmfa) and the EC (MQECSVR). No functional problem is caused by these\nFDCs, except that the queue manager log file misses some log messages\nduring queue manager shutdown. The FDCs report an unexpected return code\nfrom the HP lseek() function. An example of an FDC demonstrating this\nproblem follows:\n\nProbe Id :- XC022011\nComponent :- xcsDisplayMessage\nProgram Name :- $DATA06.RP1PBIN.MQECSVR\nMajor Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC\n\nMQM Function Stack\nnspPrimary\neclShutdownOK\nxcsDisplayMessageForSubpool\nxcsDisplayMessage\nxcsFFST\n\n6fffe660 000011FA ....\n6fffe670 2F686F6D 652F726F 622F4D51 \/home\/test\/MQ\n6fffe680 352E332F 5250312F 50726F64 2F776D71 5.3\/RP1\/Prod\/wmq\n6fffe690 2F766172 2F6D716D 2F716D67 72732F51 \/var\/mqm\/qmgrs\/Q\n6fffe6a0 4D312F65 72726F72 732F414D 51455252 M1\/errors\/AMQERR\n6fffe6b0 30312E4C 4F47 01.LOG\n\nThis problem is fixed by the following HP SPRs\n\nT8620ACL (OSSFS) for G06 HP OS\nT8620ACM (OSSFS) for H06 HP OS\n\n2. APAR IC54594 - EC abends with non-MQM user running application from non-MQM\ndirectory.\n\nStatically-bound TNS applications that are not relinked after installing \nFixpack 5.3.1.4 have additional considerations. For these applications, \nqmproc.ini Application Rules 2 and 4 will not work if the application \nis located in a non-MQM directory.\n\n3. The Guardian control commands for the Publish \/ Subscribe broker\n(strmqbrk, endmqbrk, dspmqbrk ... etc) will not work correctly unless they\nare run in the same CPU as the broker is running in, or was last running in.\n\nPlease use the equivalent OSS commands instead of the Guardian versions, or\nensure that the Guardian Publish \/ Subscribe broker commands run in the same\nCPU as the broker was or is running in.\n\n4. Queue managers occasionally do not delete Temporary Dynamic Queues the \nwhen the last application closes them. The cause of this is unknown at present.\nThe problem is rare and unlikely to cause significant impact on queue \nmanager operation unless the queues are present in very large numbers.\nQueues orphaned in this way cannot be used by applications, and are removed\nunconditionally as a part of the normal garbage collection activity during \na queue manager restart.\n\nDOCUMENTATION UPDATES\n=====================\n\nPlease note that several supplements to the documentation have been provided\nwith fixpacks since V5.3 was originally released. These supplements have\nbeen released in Adobe Acrobat format and can found in the\nopt\/mqm\/READMES\/en_US directory of any installation as well as the original\nsoftware distribution tree (placed files). The following supplements have\nbeen released to date (the name of the file describes the content):\n\nExits.pdf\nJava.pdf\nPubsub.pdf\nSNAChannels.pdf\nSSLUpdate.pdf\nUpgmqmreadme.pdf\nSdcp.pdf\n\nAlso please note that the current published versions of the cross-platform\n(\"family\") books contain references to the IBM MQSeries V5.1 for Compaq NSK\nproduct which is the previous major version of WebSphere MQ for HP NonStop\nServer. Consequently, these references may not be accurate with respect to\nthe functional support provided by V5.3.1.\n\nWebsphere MQ Programmable Command Formats and Administration Interface\n(SC34-6060-03)\n-----------------------------------------------------------------------\n\nChapter 3 - PCF Commands and Responses in Groups\n\nPage 19: Add \"Refresh Queue manager\" as a supported command\n\nChapter 4 - Definitions of Programmable Command Formats\n\nPage 173: Add the following new command:\n\nRefresh Qmgr\n\nThe Refresh Qmgr (MQCMD_REFRESH_Q_MGR) command refreshes the\nExecution Controller (EC) process management rules.\n\nThis PCF is supported only on WebSphere MQ V5.3 HP NonStop Server.\n\nRequired parameters:\nNone\n\nOptional parameters:\nNone\n\nError codes\n\nThis command might return the following in the response format\nheader, in addition to the values shown on page 18.\n\nReason (MQLONG)\n\nThe value can be:\nMQRCCF_PARM_COUNT_TOO_BIG\n\nParameter count too big.\n\nWebSphere MQ for HP NonStop Server Quick Beginnings (GC34-6626-00)\n------------------------------------------------------------------\n\nChapter 1 - Planning to install WebSphere MQ for HP NonStop Server\n\nPage 1: the baseline release level for V5.3.1 on the HP Integrity NonStop\nServer is now H06.05.01\nPage 1: the typical approximate storage requirements are as follows:\n+ OSS files placed before installation:\nH-Series: 160Mb\n+ For each installation:\nH-Series: Guardian 220Mb, OSS 350Mb, Total 570Mb\n+ For each queue manager:\nH-Series: Guardian 9.5Mb, OSS 0.2Mb, Total 10Mb\nPages 2 & 3: please review the section \"Hardware and Software\nRequirements\" in these release notes for the details of all other updated\nrequirements\nChapter 3 - Installing WebSphere MQ for HP NonStop Server\n\nPage 12: Product Selection dialog. The names of the products have been\nupdated to \"WebSphere MQ V5.3.1\" and \"WebSphere MQ V5.3.1 Integrity\".\nPage 14: instmqm now includes the function of creating an automatic\nbackup archive of a successful installation, as follows:\nInstmqm has been enhanced to provide the ability to back-out an ungrade\ninstallation, and the ability to archive and restore installations\nindividually. Before instmqm starts to make changes to a system, it will\nautomatically create an archive of the current installation (OSS opt tree\nand Guardian installation subvolumes only) in the root directory\ncontaining the opt tree in OSS. If a failure occurs during installation,\nand instmqm has made changes, the user will be asked if they wish to\nrestore the installation to its original state using the archive created\nbefore changes were made. At the end of a successful installation,\ninstmqm will now automatically create a backup archive of the new\ninstallation.\n\nInstmqm also supports two new command line options to support creating\nand using backup archives independently from an installation:\n\n-b create a backup archive of the installation\n-x restore an installation from a backup archive\n\nThese options may not be combined with any other options. Both options\nrequire the user to respond to questions at the terminal.\n\nA backup archive file is an OSS pax file, created as follows:\n\n+ the Guardian PAK utility is used to create a backup of the three\nGuardian subvolumes for the installation in a file named \"WMQSAVED\"\n+ the PAK backup file is copied to the OSS opt directory of the\ninstallation that is being archived\n+ the entire OSS opt tree of the installation (which now includes\nWMQSAVED) is then archived by the OSS pax utility\n\nBackup archive files are always created in the directory that holds the\nOSS opt tree for the installation. Archive files created automatically\nby instmqm are named \"mqarchive-yymmdd-hhmmss\" where \"yymmdd\" and\n\"hhmmss\" are numeric strings of the date and time that the backup archive\nwas created - for example: \"mqarchive-061005-143606\".\n\nPage 15: instmqm has new command line options as described in these\nrelease notes for creating and restoring backup archives\nPage 17: the SnaProviderName and TcpProviderName fields of the\nQmgrDefaults stanza in the instmqm response file are used to populate\nthe proc.ini file to provide installation wide defaults for channels.\nPlease note that these fields do not get used for the default listener\nconfiguration either on the command line (runmqlsr) or in the queue\nmanager's Pathway environment. Users must manually configure the\ntransport names for all listeners.\nPage 28: in addition to the manual methods for cleaning up after a failed\ninstallation, instmqm will offer the option to restore the previous\ninstallation from a backup archive in the event of a failure while\nupgrading a V5.3 installation to V5.3.1 level. These release notes\ndescribe the additional function.\nIf an installation was initially created without SSL (selection of the\ninstallation type \"CORE\" for instmqm), the following procedure can be\nused to update the installation to include SSL components. In the\ninstructions below, <MQInstall> refers to the location of the\ninstallation that needs to be updated and <PlacedInstall> means the\nlocation of the complete set of placed files for the level of WMQ that\ncorresponds to the installation being updated. All queue managers\nmust be ended before attempting this procedure.\n1. mkdir <MQInstall>\/opt\/mqm\/ssl\n2. chmod 775 <MQInstall>\/opt\/mqm\/ssl\n3. cp <PlacedInstall>\/opt\/mqm\/ssl\/* <MQInstall>\/opt\/mqm\/ssl\n4. chmod 775 <MQInstall>\/opt\/mqm\/ssl\/amq*\"...\n5. cp <MQInstall>\/opt\/mqm\/ssl\/openssl <MQInstall>\/opt\/mqm\/bin\n6. chmod 664 <MQInstall>\/opt\/mqm\/ssl\/openssl\n7. chmod 774 <MQInstall>\/opt\/mqm\/bin\/openssl\n8. cp <MQInstall>\/opt\/mqm\/ssl\/amqjkdm0 <MQInstall>\/opt\/mqm\/bin\n9. chmod 775 <MQInstall>\/opt\/mqm\/bin\/amqjkdm0\n10. mv <MQInstall>\/opt\/mqm\/lib\/amqcctca\n<MQInstall>\/opt\/mqm\/lib\/amqcctca_nossl\n11. mv <MQInstall>\/opt\/mqm\/lib\/amqcctca_r\n<MQInstall>\/opt\/mqm\/lib\/amqcctca_r_nossl\n12. cp <MQInstall>\/opt\/mqm\/ssl\/amqccssl <MQInstall>\/opt\/mqm\/lib\/amqcctca\n13. cp <MQInstall>\/opt\/mqm\/ssl\/amqccssl_r\n<MQInstall>\/opt\/mqm\/lib\/amqcctca_r\n14. chmod 775 <MQInstall>\/opt\/mqm\/lib\/amqcctca*\n15. The <MQInstall>\/var\/mqm\/qmgrs\/<qmgr name> directory should have an\n\nssl directory which is where you will store the certificate related\nfiles (cert.pem, trust.pem etc.)\n16. The <MQInstall>\/opt\/mqm\/samp\/ssl should exist already with the ssl\nsamples\n17. If the entropy daemon is not configured on the system this will need\nto be performed. Refer to the WMQ V53 HP NonStop System\nAdministration Chapter 11 page 165-167\n18. Install the certificates per the updated instructions, SSLupdate.pdf\nfound in <MQInstall>\/opt\/mqm\/READMES\/en_US\n\nChapter 5 - Creating a Version 5.3 queue manager from an existing Version 5.1\nqueue manager\n\nPages 37 & 38: this section is completely replaced by the documentation\nsupplement Upgmqmreadme.pdf supplied with this release.\nChapter 7 - Applying maintenance to WebSphere MQ for HP NonStop Server\n\nPages 44 & 45: the tool for applying maintenance is named \"svcmqm\" and\nnot \"installCSDxx\".\nPage 44: in step 3 of \"Transferring and preparing the PTF for\ninstallation\", the top level directory of the PTF is opt, and is not\nnamed differently for each PTF. Therefore it is important to manually\ncreate a directory specific to each PTF, download the PTF to that new\ndirectory and then expand the archive within the new directory.\nPage 44: in step 2 of \"Running the installation script for a PTF\", the\n\nsvcmqm tool has a different command line from that documented for\n\"installCSDxx\". svcmqm takes three parameters:\nsvcmqm -i installationtree -v vartree -s servicepackage\nwhere \"installationtree\" is the full path to the location of the opt\/mqm\ndirectory of the installation to be updated\n\"vartree\" is the full path to the location of the var\/mqm\ndirectory of the installation to be updated\n\"servicepackage\" is the full path to the location of the opt\/mqm\ndirectory of the maintenance to be installed\nFor example:\nsvcmqm -i \/home\/me\/wmq\/opt\/mqm -v \/home\/me\/wmq\/var\/mqm\n-s \/home\/me\/wmqfiles\/opt\/mqm\n\nwhich will update the installation in \/home\/me\/wmq\/opt\/mqm and\n\n\/home\/me\/wmq\/var\/mqm from the maintenance package in directory tree\n\/home\/me\/wmqfiles\/opt\/mqm.\n\nIf either or both the \"-i installationtree\" and \"-v vartree\" parameters\nare omitted, svcmqm will use the current setting of the appropriate\nenvironment variable - either WMQNSKOPTPATH or WMQNSKVARPATH.\n\nWebSphere MQ for HP NonStop Server System Administration Guide (SC34-6625-00)\n-----------------------------------------------------------------------------\n\nChapter 2 - An introduction to WebSphere MQ administration\n\nPage 16: before running any control commands on OSS or NonStop OS it is\nnecessary to establish the environment variables for the session. When\nan installation is created a file called wmqprofile is also created in\nthe var\/mqm directory that will establish the environment for an OSS\nshell. Likewise, a file is also created in the NonStop OS subvolume\ncontaining the WMQ NonStop OS samples called WMQCSTM that can be used\nto set up the appropriate environment variables for a NonStop OS TACL\nsession.\nTo establish the WMQ environment for an OSS shell session:\n\n. wmqprofile\n\nTo establish the WMQ environment for a NonStop OS TACL session:\n\nobey WMQCSTM\n\nThe same steps are required before running any applications in the\nOSS or NonStop OS environment.\n\nChapter 4 - Administering local WebSphere MQ objects\n\n\nPage 48: when creating a Process definition, the default value for\nthe APPLTYPE attribute is \"NSK\" (indicating a Guardian program)\nChapter 7 - WebSphere MQ for HP NonStop Server architecture\n\nPage 80: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\nChapter 8 - Managing scalability, performance, availability and data\nintegrity\n\nPage 104: the last paragraph of the OpenTMF section should be reworded\nas follows:\nNo special administrative actions are required for this use of TMF.\nWebSphere MQ uses and manages it automatically. You must ensure that\nthe RMOPENPERCPU and BRANCHESPERRM configuration parameters of TMF are\nset to appropriate values for your configuration. Please see Chapter 12\n\nTransactional Support - Configuring TMF for WebSphere MQ for\ninformation on how to calculate the correct values. The HP TMF Planning\nand Configuration Guide describes the subject of resource managers and\nheterogeneous transaction processing.\n\nChapter 9 - Configuring WebSphere MQ\n\nPage 119: the CPUS section should state that the default can be\noverridden using the crtmqm -nu parameter. See Chapter 18 - The control\ncommands for a description of how to use this parameter with crtmqm.\nPage 120: the section describing the ARGLIST attribute of a TCP\/IP\nListener should also mention the use of the optional -u parameter to\nconfigure channels started by the listener as unthreaded processes.\nThe default is to run incoming channels as threads in an MCA process.\nPage 130: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\nPage 133: Figure 23 remove :\nOAM Manager stanza #\nOamManager:\nPage 136: the Exit properties section should state that the only\n\nsupported way of configuring and running a Cluster Workload (CLWL) Exit\nfor HP NonStop Server is in FAST mode. The CLWLMode setting in qm.ini\nis required to be set to FAST, which is the default for WebSphere MQ\non this platform.\nPage 139: the MQIBindType attribute of the Channels stanza is set by\ncrtmqm to FASTPATH. This should not be changed, except under the\ndirection of IBM Service.\nPage 140: the AdoptNewMCA=FASTPATH option is always required for\nthis platform in order for the adoption of MCAs to be effective. The\n\"Attention!\" box after the description of the FASTPATH option should\nbe ignored.\nPage 140: add the following description of the ClientIdle attribute:\nClientIdle=seconds\n\nClientIdle specifies the number of seconds of inactivity to permit\nbetween client application MQI calls before WebSphere MQ terminates\nthe client connection. The default is to not terminate client\nconnections however long they remain inactive. When a client connection\nis terminated because of idle activity, the client application receives\na connection broken result (2009) on its next MQI call.\n\nChapter 11 - Working with the WebSphere MQ Secure Sockets Layer (SSL) support\n\nA documentation supplement has been written to replace the sections on\nPage 170 (Preparing the queue manager's SSL files) to Page 176 (Building\nand verifying the sample configuration) because of changes to the files\nthat WebSphere MQ uses to hold certificates. The documentation supplement\nis called SSLupdate.pdf, and can be found in the opt\/mqm\/READMES\/en_US\ndirectory of an installation.\n\nChapter 12 - Transactional Support\n\nPage 185: The descriptions of the TMF attribute RMOPENPERCPU in the\n\nResource manager configuration section is modified as follows:\nRMOPENPERCPU\n\nEach WebSphere MQ thread or process that handles transactions has\nan open of a Volatile Resource Manager in the CPU it runs in. In\naddition, each application thread or process using the MQI also has\nan open. The minimum requirement for this configuration parameter\n\nis therefore the sum of:\n+ all Queue Server processes in that CPU\n+ all LQMA and MCA threads running in that CPU\n+ all MQI application threads running in that CPU\n+ 10 (to account for miscellaneous queue manager processes that\ncould be running in that CPU)\nYou should calculate the peak values of these numbers across all CPUs\nand add a safety margin to arrive at the correct value for your system.\nThe HP default value of 128 for this parameter is often suitable for\nsmall configurations, but unsuitable for medium or large ones.\n\n\nPage 186: add the following paragraph to the Troubleshooting section\nfor Configuring TMF:\nIf the RMOPENPERCPU value is not configured to allow sufficient opens\nof resource managers in a CPU, WebSphere MQ connections will fail with\nan unexpected return code, and FDCs will be generated reporting an\nerror with the TMF_VOL_RM_OPEN_. The workaround is to distribute\napplications and queue manager processes in the CPU that exceeds\nthe limit to other CPUs. The correct remedy is to schedule an outage\nand modify the TMF configuration.\n\nPage 186: add the following paragraph to the Troubleshooting section\nfor configuring TMF:\nIf TMF is stopped, or new transactions are disabled, and WMQ requires\nan internal \"unit of work\" (TMF transaction) to perform an update to\na protected resource requested by an MQI call, that call will fail\nand the reason code returned will be MQRC_UOW_NOT_AVAILABLE (2255).\n\nNote that in some cases, updates to protected resources may be\nrequired by MQI operations do not directly perform messaging\noperations - for example, MQOPEN of a model queue that creates a\npermanent dynamic queue. If MQI calls return MQRC_UOW_NOT_AVAILABLE,\ncheck the status of the TMF subsystem to determine the likely cause.\n\nChapter 14 - Process Management\n\nPage 197: the MQSC command to reload the process management rules is\nREFRESH QMGR TYPE(NSPROC) and not RESET QMGR TYPE(NSPROC)\n\nPage 200 and 204: the default value for the maximum number of unthreaded\nagents is now 200. The default value for the maximum number of threaded\nagents is now 20. the default value for the maximum use count for\nthreaded agents is now 100.\n\nPage 203: add a new paragraph titled \"Pathway\":\nPathway\nThis stanza contains 3 attributes:-\n- ProcessName\n- DynamicProcessName\n- Hometerm\nProcessName is the name of the Queue Managers pathmon process.\nIf the -np option was specified at queue Manager creation, \nthe value of ProcessName will be set to the value of that option \nwhen the qmproc.ini file is created\nIf DynamicProcessName is set to Yes, the system will generate a name\nfor the pathmon process at the time the Queue Manager starts.\nIf the value is set to no, the value of the ProcessName attribute\nwill determine the pathmon process name for the queue manager \nHometerm specifies the value of the hometerm attribute for the Queue \nManager pathmon process \nIf the -nh opton was specified at queue manager creation, the \nvalue of Hometerm will be set to the value of that option, \notherwise the default of $ZHOME will be used.\n\nPage 204: the \"valid attribute values\" for the attribute \"ExecutableName\"\nshould be stated as \"File name part only of the program to run for the\nLQMA or MCA process\".\n\nPages 203 - 205, Table 20: Process Management: Keyword definition Summary\nThere are a number of errors in the Process Management Keyword\ndefinition table:\n\n1. Environment variables:\nENVxx should be Envxx\n\n2. Executable Name to Match:\nExecNameMatch should be ExeNameMatch\n\n3. Fail if CPU unavailable:\nFailOnCPUunavail should be FailOnCPUUnavail\n\n4. Preferred number of Threaded Agents:\nPreferedThreadedAgents should be PreferredThreadedAgents\n\nDefault values:\n\n5. MaxThreadedAgents: change from 10 to 20\n\n6. MaxUnthreadedAgents: change from 20 to 200\n\n7. MaxThreadedAgentUse: change from 10 to 100\n\nPages 199 - 201, Table 16. Process management: agent attributes\n\nThe same default value changes are required:\n\n1. Maximum number of unthreaded agents: 200\n2. Maximum number of threaded agents: 20\n3. Maximum reuse count for threaded agents: 100\n\nChapter 15 - Recovery and restart\n\nPage 216: Configuring WebSphere MQ, NonStop RDF, and AutoSYNC to support\ndisaster recovery\nTo configure RDF to work with a existing WMQ V53 queue manager:\nEnd the WMQ V53 queue manager.\nUsing the HP BACKUP or PAK utility specifying the AUDITED option\nBackup the primary site Guardian WMQ queue manager subvolume.\nUsing the HP RESTORE or UNPAK utility specifying the AUDITED option\nRestore the files on the backup site.\nEnsure that on the backup system that the alternate key file\nattribute (ALTKEY) for files amqcat and amqpdb of each queue\nmanager are set to the correct (backup system) node name\nPage 217: the example of the altmqfls command to set the RDF\ncompatibility mode for large persistent messages is correct but too\nsimplistic. Please use care when using altmqfls to set the queue options\n\n(--qsoptions parameter) and refer to the reference section for the\ncontrol commands for a complete description of using this option.\nPage 217: the bullet point that describes the configuration of AutoSYNC\nfilesets is incorrect when it states that NO ALLSYMLINKS should be\nspecified. Replace sub-bullet item number 2 with the following text:\n2. The entire queue manager OSS directory structure\nvar_installation_path\/var\/mqm\/qmgrs\/qmname.\n\nYou must specify the absolute path name of the queue manager's\ndirectory. Specify the ALLSYMLINKS option for this fileset to\nensure that AutoSYNC correctly synchronizes the symbolic link\n(G directory) in the queue manager's directory to the NonStop OS queue\nmanager's subvolume on the backup system.\n\nChapter 16 - Troubleshooting\n\nPage 230: after the section \"Is your application or system running\nslowly?\", insert the following new section:\nAre your applications or WebSphere MQ processes unable to connect?\n\nIf connection failures are occurring:\n\nis the User ID under which the application runs authorized to\nuse this queue manager?\nare SAFEGUARD permissions preventing read access to the WebSphere\nMQ installation files by the User ID running the application?\nare the environment variables established for the application\nprocess, so that the correct installation of WebSphere MQ is being\nused?\nif necessary, has the application been relinked or rebound with\nany static MQI libraries that it uses?\nis a resource problem preventing the queue manager from allowing\nthe connection? Review the troubleshooting section under TMF\nConfiguration on Page 185 and 186 for information about the\nRMOPENSPERCPU TMF attribute.\n\nChapter 18 - The control commands\n\nPage 93: The example of the --resetmeasure option is missing a mandatory\nparameter having the value \"YES\" or \"NO\". The paragraph on page 93 describing\nthe --resetmeasure option should be replaced with the following\n\n\"The queue server can maintain the Measure counter only if it is included \nin an active measurement. If it is not included in an active measurement, \nand messages are put in the queue and removed from the queue, the value \nof the counter will no longer represent the current depth of the queue. \nIf the counter is subsequently included in an active measurement, you can \ncause the queue server to reset the Measure counter to the current depth \nof the queue by using the --resetmeasure parameter on the altmqfls command, \nas follows: altmqfls --qmgr QMGR --type QLOCAL --resetmeasure TEST.QUEUE YES\"\n\nPage 244: The mandatory YES|NO parameter is missing from the syntax diagram\n\nPage 247: The mandatory YES|NO parameter is missing from the description\nof the option\n\nPage 243: the control commands for the Publish \/ Subscribe broker are\nnot referenced here. Refer to the WebSphere MQ V6.0 Publish\/Subscribe\nUser Guide and the documentation supplement for Publish\/Subscribe on\nHP NonStop Server - Pubsub.pdf.\nPage 255: if the OSS environment variable or Guardian PARAM MQPATHSEC\nis defined and set to one of the standard NonStop OS security attributes\n(A, N, C, G, O, or U) when crtmqm is run, the default PATHWAY SECURITY\nattribute value of \"G\" will be overridden by the value of the environment\nvariable \/ PARAM. This can be used to restrict access to the queue\nmanager's Pathway environment. The current Pathway attributes can be\ndisplayed in PATHCOM using the INFO PATHWAY command.\nPage 255: the -nu parameter for setting the default CPUS attribute\nin Pathway serverclasses does not accept all the values that Pathway\nallows for this attribute. The only accepted values (and the result in\nPathway configuration) are of the form:\n-nu value Pathway CPUS attribute\n-------- ---------------------\n-nu a CPUS (a:0)\n-nu a:b CPUS (a:b)\n\nMore complex Pathway serverclass CPUS attributes settings must be\nconfigured after the queue manager has been created, using the HP\nPATHCOM utility.\n\nChapter 23 - API exits\n\nPages 373-375: please review the updates to this section in the\ndocumentation supplement for API exits for HP NonStop Server called\nExits.pdf. This supplement has been extensively revised for V5.3.1.1\nto clarify the requirements and process for creating and integrating\nexits with WebSphere MQ.\n\nAppendix B - Directory structure\n\nPages 430 and 431: there is a new G symbolic link to the Guardian\nsubvolume containing the product executables in\n...\/var\/mqm\/qmgrs\/@SYSTEM\nPage 431: the content of the ssl directory is revised with V5.3.1.1\nas follows:\nThis directory contains up to four files used by the SSL support:\n\nThe queue manager certificate and private key store (cert.pem)\nThe trusted certificates store (trust.pem)\nThe pass phrase stash file for the queue managers certificate\nand private key store (Stash.sth)\nThe certificate revocation list file (optional - crl.pem)\n\nAppendix F - Environment variables\n\nPage 446: there are several environment variables that are used by the\nGuardian sample build scripts to locate the header files and the\nlibraries. Suitable settings for these are established in the\nWMQCSTM file (in the Guardian samples subvolume). The environment\nvariables, and their meanings, are:\nMQNSKOPTPATH^INC^G include file\/header subvolume\nMQNSKOPTPATH^BIN^G binaries subvolume\nMQNSKOPTPATH^LIB^G binaries subvolume\nMQNSKOPTPATH^SAMP^G samples subvolume\n\nIn addition, an HP environment variable is also required (and set in\nWMQCSTM) that locates the OSS DLLs for dynamic loading from Guardian.\nThe environment variable is ^RLD^FIRST^LIB^PATH.\n\nPage 468: add after the \"Queue Server Tuning parameters\" section\n\nQueue Manager Server tuning parameters\n\nMQQMSHKEEP If this ENV is set for the MQS-QMGRSVR00 serverclass, its value\nspecifies a numeric value in seconds to override the default housekeeping\ninterval of the queue manager server. The default interval is 60 seconds.\nThe housekeeping interval controls how frequently the queue manager\nserver generates expiration reports. The permitted range of values is 1-300.\nValues outside this range will be ignored and the default value will be used.\n\nMQQMSMAXMSGSEXPIRE If this ENV is set for the MQS-QMGRSVR00 serverclass,\nits value specifies a numeric value to override the default maximum number\nof expiration report messages that are generated during housekeeping\noperations by a queue manager server. The default maximum number of expiration\nmessages generated is 100. The permitted range of values is 1-99999. Values\noutside this range will be ignored and the default value will be used.\n\n\nAppendix H - Building and running applications\n\nBuilding C++ applications,\n\nTable 47 - there is no multi-threaded library support in\nGuardian so there should not be an entry for a\nmulti-threaded guardian library\n\nTable 48 - the name of this table should be \"Native non-PIC\"\n\nReferences to G\/lib symbolic links have changed with WMQ 5.3.1 to lib\/G\n\nNote that the MQNSKVARPATH and MQNSKOPTPATH environment variables must\nbe established in the environment, before an application starts up.\nThey cannot be programmatically set once a program is running by using\nputenv().\n\nPage 461: Building COBOL applications\n\nAdd the following text:\n\n\"In both the OSS and Guardian environment, the CONSULT compiler\ndirective referencing the MQMCB import library must now be used along\nwith correct linker options. Refer to the BCOBSAMP TACL script described\nin Appendix I for more information.\"\n\nAppendix I - WebSphere MQ for NonStop Server Sample Programs\n\nPages 465-466: The section \"TACL Macro file for building C Sample Programs\"\nis replaced by the following:\n\nBCSAMP - Build a C-Language Sample.\n\nThis TACL script will compile and link a C-language sample into an\nexecutable program. The script expects that the WMQ environment has\nbeen established using WMQCSTM.\n\nBCSAMP usage:\n\nBCSAMP <type> <source>\n\n<type> The type of executable program that should be built.\n\nValid values are:\n\npic A native PIC program\ntns A non-native TNS program\n\n<source> The filename of the source module to be compiled and linked\n\nThe <source> filename should end with a 'C'. The final program name is\nthe same as the source filename with the trailing 'C' removed.\n\nPage 467: The section \"TACL Macro files for building COBOL Sample\nPrograms\" is replaced by the following:\n\nBCOBSAMP - Build a COBOL Sample.\n\nThis TACL script will compile and link a COBOL sample into an executable\nprogram. The script expects that the WMQ environment has been established\nusing WMQCSTM.\n\nBCOBSAMP usage:\n\nBCOBSAMP <type> <source>\n\n<type> The type of executable program that should be built.\n\nValid values are:\n\npic A native PIC program\ntns A non-native TNS program\n\n<source> The filename of the source module to be compiled and linked\n\nThe <source> filename should end with an 'L'. The final program name is\nthe same as the <source> filename with the trailing 'L' removed.\n\nPage 469: The section \"TACL Macro files for building TAL sample programs\"\nis replaced by the following:\n\nBTALSAMP - Build a TAL Sample.\n\nThis TACL script will compile and link a TAL sample into an executable\nprogram. The script expects that the WMQ environment has been established\n\nusing WMQCSTM.\n\nBTALSAMP usage:\n\nBTALSAMP <source>\n\n<source> The filename of the source module to be compiled and linked\n\nThe final program name is the same as the <source> filename with the\ntrailing character removed.\n\nAppendix J - User exits\n\nrefer to the documentation supplement Exits.pdf for updated information\nabout configuring and building user exits. This supplement has been\nextensively revised for V5.3.1.1 to clarify the requirements and process\nfor creating and integrating exits with WebSphere MQ.\nThe description of compile options for PIC unthreaded, threaded and\nGuardian dlls in this document is incorrect. The option specified as\n\"-export all\" should be \"-export_all\".\n\nAppendix K - Setting up communications\n\nPage 482: The TCP\/IP keep alive function\n\nBy default, the TCP\/IP keep alive function is not enabled. To enable\nthis feature, set the KeepAlive=Yes attribute in the TCP Stanza in the\nqm.ini file for the queue manager.\nIf this attribute it set to \"yes\" the TCP\/IP subsystem checks periodically\nwhether the remote end of a TCP\/IP connection is still available. If it is\nnot available, the channel using the connection ends.\nIf TCP stanza KeepAlive attribute is not present or is set to \"No\", the\nTCP\/IP subsystem will not check for disconnection of the remote end.\n\nChapter 9 \"Configuring WebSphere MQ\" page 140 describes the TCP stanza\nattributes.\n\nAPAR IC58859: wmqtrig script\nThe wmqtrig script processing the -c option, for triggering a TACL macro\/script\nfile, will not normally propagate the TMC data to the macro\/script file.\nSome applications may need the TMC for processing. A switch used in conjunction\nwith the -c option, -5.1, has been added which will pass the TMC data to a TACL\nmacro\/script file with the wmqtrig script. Define the APPLICID attribute with\nthe -5.1 switch, for example:\nAPPLICID(\/wmq\/opt\/mqm\/bin\/wmqtrig -5.1 -c \\$data06.test.trigmac)\n\nSSLupdate.pdf page 7\n-----------------------------------------------------------------------------\n\nThe SSLupdate.pdf document was first released with Fixpack 5.3.1.1\n\nThe SSL test scripts expect that a default TCP\/IP process ($ZTC0) is\nconfigured on the system to be used during the test. The configuration\nwill need modification if a non-default TCP\/IP process does not exist\non the system or another TCP\/IP process is used to communicate with the\npartner system. The ALICE.sh and\/or BOB.sh scripts that setup of the\nlistener (runmqlsr) will need modification to add the -g option to use a\nnon-default TCP\/IP process.\n\nCONTACTING IBM SOFTWARE SUPPORT\n===============================\n\nIBM Software Support provides assistance with product defects. You might\nbe able to solve you own problem without having to contact IBM Software\nSupport. The WebSphere MQ Support Web page\n(http:\/\/www.ibm.com\/software\/integration\/wmq\/support\/ [http:\/\/www.ibm.com\/software\/integration\/wmq\/support\/]) contains\nlinks to a variety of self-help information and technical flashes. The\nMustGather Web page\n(http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21229861 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21229861])\ncontains diagnostic hints and tips that will aid in diagnosing and\nsolving problems, as well of details of the documentation required by\nthe WebSphere MQ support teams to diagnose problems.\n\nBefore you \"Submit your problem\" to IBM Software Support, ensure\nthat your company has an active IBM software maintenance contract, and\n\nthat you are authorized to submit problems to IBM. The type of software\nmaintenance contract that you need depends on the type of product you\nhave:\n\nFor IBM distributed software products (including, but not limited to,\nTivoli(R), Lotus(R), and Rational(R) products, as well as DB2(R) and\nWebSphere products that run on Windows or UNIX(R) operating systems),\nenroll in Passport Advantage(R) in one of the following ways:\nOnline: Go to the Passport Advantage Web site at\nhttp:\/\/www.lotus.com\/services\/passport.nsf\/WebDocs\/Passport_Advantage_Home [http:\/\/www.lotus.com\/services\/passport.nsf\/WebDocs\/Passport_Advantage_Home],\n\nand click \"How to Enroll\".\nBy phone: For the phone number to call in your country, go to the \"Contacts\"\npage of the IBM Software Support Handbook at\nwww.ibm.com\/support\/handbook [www.ibm.com\/support\/handbook], click 'contacts' and then click the name of \nyour geographic region.\nFor customers with Subscription and Support (S & S) contracts, go to the\nSoftware Service Request Web site at\nhttp:\/\/www.ibm.com\/support\/servicerequest [http:\/\/www.ibm.com\/support\/servicerequest].\nFor customers with IBMLink(TM), CATIA, Linux(R), S\/390(R), iSeries(TM),\npSeries(R), zSeries(R), and other support agreements, go to the IBM Support\nLine Web site at\nhttp:\/\/www.ibm.com\/services\/us\/index.wss\/so\/its\/a1000030\/dt006 [http:\/\/www.ibm.com\/services\/us\/index.wss\/so\/its\/a1000030\/dt006].\nFor IBM eServer(TM)) software products (including, but not limited to,\nDB2(R) and WebSphere products that run in zSeries, pSeries, and iSeries\nenvironments), you can purchase a software maintenance agreement by working\ndirectly with an IBM sales representative or an IBM Business Partner.\nFor more information about support for eServer software products, go to the\nIBM Technical Support Advantage Web site at\nhttp:\/\/www.ibm.com\/servers\/eserver\/techsupport.html [http:\/\/www.ibm.com\/servers\/eserver\/techsupport.html].\n\nIf you are not sure what type of software maintenance contract you need,\ncall 1-800-IBMSERV (1-800-426-7378) in the United States. From other\ncountries, go to the \"Contacts\" page of the IBM Software Support\nHandbook at www.ibm.com\/support\/handbook [www.ibm.com\/support\/handbook], click 'contacts' and then \nclick the name of your geographic region. for phone numbers of people\nwho provide support for your location.\n\nTo contact IBM Software support, follow these steps:\n\n1. \"Determine the business impact of your problem\"\n2. \"Describe your problem and gather background information\"\n3. \"Submit your problem\"\n\nDetermine the business impact of your problem\n\n\nWhen you report a problem to IBM, you are asked to supply a severity\nlevel. Therefore, you need to understand and assess the business impact\nof the problem that you are reporting. Use the following criteria:\n\n---------------------------------------------------------------+\n\nSeverity 1 The problem has a critical\nbusiness impact: You are unable\nto use the program, resulting in\na critical impact on operations.\nThis condition requires an\nimmediate solution.\n\n---------------------------------------------------------------+\n\nSeverity 2 This problem has a significant\nbusiness impact: The program is\nusable, but it is severely\nlimited.\n\n---------------------------------------------------------------+\n\nSeverity 3 The problem has some business\nimpact: The program is usable,\nbut less significant features\n(not critical to operations) are\nunavailable.\n\n---------------------------------------------------------------+\n\nSeverity 4 The problem has minimal business\nimpact: The problem causes\nlittle impact on operations, or\na reasonable circumvention to\nthe problem was implemented.\n\n---------------------------------------------------------------+\n\nDescribe your problem and gather background information\n\nWhen describing a problem to IBM, be as specific as possible. Include\nall relevant background information so that IBM Software Support\nspecialists can help you solve the problem efficiently. See the\nMustGather Web page\nhttp:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21229861 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21229861] for\ndetails of the documentation required. To save time, know the answers to\nthese questions:\n\nWhat software versions were you running when the problem occurred?\nDo you have logs, traces, and messages that are related to the problem\nsymptoms? IBM Software Support is likely to ask for this information.\nCan you re-create the problem? If so, what steps do you perform to\nre-create the problem? Did you make any changes to the system? For example,\ndid you make changes to the hardware, operating system, networking software,\nor other system components? Are you currently using a workaround for the\nproblem? If so, please be prepared to describe the workaround when you\nreport the problem.\n\nSubmit your problem\n\nYou can submit your problem to IBM Software Support in one of two ways:\n\nOnline: Go to the Submit and track problems tab on the IBM Software Support\nsite at http:\/\/www.ibm.com\/software\/support\/probsub.html [http:\/\/www.ibm.com\/software\/support\/probsub.html]. Type your\ninformation into the appropriate problem submission tool.\nBy phone: For the phone number to call in your country, go to the \"Contacts\"\npage of the IBM Software Support Handbook at\nwww.ibm.com\/support\/handbook [www.ibm.com\/support\/handbook], click 'contacts' and then click the name \nof your geographic region.\n\nIf the problem you submit is for a software defect or for missing or\ninaccurate documentation, IBM Software Support creates an Authorized\nProgram Analysis Report (APAR). The APAR describes the problem in\ndetail. Whenever possible, IBM Software Support provides a workaround\nthat you can implement until the APAR is resolved and a fix is\ndelivered. IBM publishes resolved APARs on the Software Support Web site\ndaily, so that other users who experience the same problem can benefit\nfrom the same resolution.\n\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++ ++\n++ COPYRIGHT, NOTICES AND TRADEMARKS ++\n++ ++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n* IBM WebSphere MQ for HP NonStop Server, Version 5.3.1.12\n* Statement: Licensed Materials - Property of IBM\n* (c) Copyright IBM Corp. 1999, 2016\n* All rights reserved.\n* U.S. Government Users Restricted Rights - use,\n* duplication or disclosure restricted by GSA\n* ADP Schedule Contract with IBM Corp.\n* Status: Version 5.3.1.12\n* Created: May 20, 2016\n\nNOTICES AND TRADEMARKS\n======================\n\nIBM may not offer the products, services, or features discussed in this\ndocument in all countries. Consult your local IBM representative for\ninformation on the products and services currently available in your\narea. Any reference to an IBM product, program, or service is not\nintended to state or imply that only that IBM product, program, or\nservice may be used. Any functionally equivalent product, program, or\nservice that does not infringe any IBM intellectual property right may\nbe used instead. However, it is the user's responsibility to evaluate\nand verify the 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 does\nnot give you any license to these patents. You can send license\ninquiries, in writing, to:\nIBM Director of Licensing\n\nIBM Corporation\nNorth Castle Drive\nArmonk, NY 10504-1785\nU.S.A.\n\nFor license inquiries regarding double-byte (DBCS) information, contact\nthe IBM Intellectual Property Department in your country\/region or send\ninquiries, in writing, to:\nIBM World Trade Asia Corporation\nLicensing\n2-31 Roppongi 3-chome, Minato-ku\nTokyo 106, Japan\n\nThe following paragraph does not apply to the United Kingdom or any\nother country\/region where such provisions are inconsistent with local\nlaw: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS\nPUBLICATION \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR\nIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nNON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.\nSome states do not allow disclaimer of express or implied warranties in\ncertain transactions; therefore, this statement may not apply 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\nAny references in this information to non-IBM Web sites are provided for\nconvenience only and do not in any manner serve as an endorsement of\nthose Web sites. The materials at those Web sites are not part of the\nmaterials for this IBM product, and use of those Web sites is at your\nown risk.\n\nIBM may use or distribute any of the information you supply in any way\nit believes appropriate without incurring any obligation to you.\n\nLicensees of this program who wish to have information about it for the\npurpose of enabling: the exchange of information between\nindependently created programs and other programs (including this one)\nand (ii) the mutual use of the information that has been exchanged,\nshould contact:\nIBM Canada Limited\nOffice of the Lab Director\n8200 Warden Avenue\nMarkham, Ontario\nL6G 1C7\nCANADA\n\nSuch information may be available, subject to appropriate terms and\nconditions, including in some cases payment of a fee.\n\nThe licensed program described in this document and all licensed\nmaterial available for it are provided by IBM under terms of the IBM\nCustomer Agreement, IBM International Program License Agreement, or any\nequivalent agreement between us.\n\nAny performance data contained herein was determined in a controlled\nenvironment. Therefore, the results obtained in other operating\nenvironments may vary significantly. Some measurements may have been\nmade on development-level systems, and there is no guarantee that these\nmeasurements will be the same on generally available systems.\nFurthermore, some measurements may have been estimated through\nextrapolation. Actual results may vary. Users of this document should\nverify the applicable data for their specific environment.\n\nInformation concerning non-IBM products was obtained from the suppliers\n\nof those products, their published announcements, or other publicly\navailable sources. IBM has not tested those products and cannot confirm\nthe accuracy of performance, compatibility, or any other claims related\nto non-IBM products. Questions on the capabilities of non-IBM products\nshould be addressed to the suppliers of those products.\n\nAll statements regarding IBM's future direction or intent are subject to\nchange or withdrawal without notice, and represent goals and objectives\nonly.\n\nThis information may contain examples of data and reports used in daily\nbusiness operations. To illustrate them as completely as possible, the\nexamples include the names of individuals, companies, brands, and\nproducts. All of these names are fictitious, and any similarity to the\nnames and addresses used by an actual business enterprise is entirely\ncoincidental.\n\nThis information may contain sample application programs, in source\nlanguage, which illustrate programming techniques on various operating\nplatforms. You may copy, modify, and distribute these sample programs in\nany form without payment to IBM for the purposes of developing, using,\nmarketing, or distributing application programs conforming to the\napplication programming interface for the operating platform for which\nthe sample programs are written. These examples have not been thoroughly\ntested under all conditions. IBM, therefore, cannot guarantee or imply\nreliability, serviceability, or function of these programs.\n\nTrademarks\n\nThe following terms are trademarks of International Business\nMachines Corporation in the United States, other countries,\nor both: DB2, eServer, IBM IBMLink, iSeries, Lotus, MQSeries, pSeries,\nPassport Advantage, Rational, s\/390, SupportPac, Tivoli, WebSphere, zSeries.\n\nUNIX is a registered trademark of The Open Group in the United States\nand other countries.\n\nMicrosoft Windows is a trademark or registered trademark of Microsoft\nCorporation in the United States, other countries, or both.\n\nJava and all Java-based trademarks and logos are trademarks or registered\ntrademarks of Sun Microsystems, Inc. in the United States, other countries,\nor both.\n\nLinux is a trademark of Linus Torvalds in the United States, other\ncountries, or both.\n\nOther company, product or service names may be the trademarks\nor service marks of others."}]},{"id":"DEV_Q109","question":"Help with Security Bulletin: Authentication vulnerability affects IIB V10.0.0.4 onwards (CVE-2016-8918 )\n\nI need to understand details regarding Security Bulletin: Authentication vulnerability affects IBM Integration Bus V10.0.0.4 onwards (CVE-2016-8918 ). Where can I find this information? ","answer":"CVEID: CVE-2016-8918 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8918]\nDESCRIPTION: In non-default configurations, IBM Integration Bus could allow a remote user to authenticate without providing valid credentials.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118528 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118528] 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:H\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21995079.txt","text":"Title: IBM Security Bulletin: Authentication vulnerability affects IBM Integration Bus V10.0.0.4 onwards (CVE-2016-8918 ) - United States\n\nText:\nWMB IIB SECURITY BULLETIN\n\nSUMMARY\n Web user accounts can be authenticated against an LDAP server, in IBM Integration Bus V10.0.0.4 and later versions. However, under some circumstances it is possible for a remote user to be authenticated without providing valid credentials. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-8918 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8918]\nDESCRIPTION: In non-default configurations, IBM Integration Bus could allow a remote user to authenticate without providing valid credentials.\nCVSS Base Score: 5.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118528 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118528] 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:H\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM Integration Bus V10\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation\/Fix IBM Integration Bus V10 IT15920 The APAR is available in Fix Pack 10.0.0.7 \nhttps:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg24043068 [https:\/\/www-304.ibm.com\/support\/docview.wss?uid=swg24043068] \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 2 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"}]},{"id":"DEV_Q110","question":"Why does our Websphere application server hang when we apply Microsoft patch on our database server?\n\nWhy does our Websphere application server hang when we apply Microsoft patch on our database server?","answer":"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.","is_impossible":false,"contexts":[{"filename":"swg21220832.txt","text":"Title: IBM Purging the connection pool of a WebSphere Application Server data source using the data source MBean - United States\n\nText:\nwas 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"}]},{"id":"DEV_Q111","question":"StaleConnectionException errors with BPM databases\n\nThere is much published documentation about stale connections to databases on the web, and yet stale connections continue to be a very common problem, at least with BPM databases. The condition can manifest itself in different ways. The most common experience of a stale connection is from error messages in the log or FFDCs that contain \"StaleConnectionException\".","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q112","question":"Why does nco_confpack -export fail with the message \"Tool in menu but not found\"?\n\nI tried to export OMNIbus configuration using nco_confpack command and I get the following message:\r\nTool in menu but not found, menu: AlertsMenu, tool: Close\r\nI've also tried using it with -list command and I get the same error. ","answer":"Recreate the tool and associate it with the menu and try to run the command again.","is_impossible":false,"contexts":[{"filename":"swg21672071.txt","text":"Title: IBM Netcool conf pack command - United States\n\nText:\ntool; menu; not found; confpack TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Migrating to a new version of Omnibus, running nco_confpack:\n\n$OMNIHOME\/bin\/nco_confpack -list -server NCOMS -user ncadmin -file \/tmp\/nco_confpack.list \n\nReceived this error: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY. \n\nSYMPTOM\nThe command fails and the following error is received: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY.\n\n\nCAUSE\nThe menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.\n\nRESOLVING THE PROBLEM\nRecreate the tool and associate it with the menu and try to run the command again."}]},{"id":"DEV_Q113","question":"How to access Rule Team Server or Rule Execution Server on WAS 7 over HTTPS?\n\nWhen trying to connect to Rule Team Server or Rule Execution Server on WebSphere Applicaiton Server (WAS) 7.0 over HTTPS, why do I still get an SSLHandshakeException after setting the property \"ilog.rules.res.allowSelfSignedCertificate\"to \"true\" ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q114","question":"Any difference between DB2 z\/OS V9.1 + IBM Cobol and DB2 LUW V10.5 FP7 + MF Cobol?\n\nWe are planning below migration.\n\n[Current]\nDB2 z\/OS V9.1 + IBM Cobol\n[New]\nDB2 AESE V10.5 FP7 \/ AIX V7.1 + Micro Focus Cobol (MF Cobol)\n\nAny known limitation or things what we need to concern?\n","answer":"DB2 LUW precompile, prep write different code to DB2 z\/OS?","is_impossible":false,"contexts":[{"filename":"swg21989702.txt","text":"Title: IBM DB2 LUW precompile, prep may write different code to DB2 z\/OS - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why does DB2 LUW precompile, prep write different code to DB2 z\/OS? \n\nCAUSE\nIt is an expected current DB2 LUW behavior.\n\nANSWER\nHere is an example. \n\n------------------------------ \n<Before PRECOMPILE> \n01 BLOB1 USAGE ID SQL TYPE IS BLOB(10485760). \n\n<PRECOMPILE on z\/OS> \n01 BLOB1. \n02 BLOB1-LENGTH PIC S9(9) COMP. \n02 BLOB1-DATA. \n49 FILLER PIC(10485760). \n\n<PRECOMPILE on LUW> \n01 BLOB1. \n02 BLOB1-LENGTH PIC S9(9) COMP. \n02 BLOB1-DATA PIC(10485760). \n------------------------------ \n\nAs above, we see DB2 z\/OS has below two lines:\n------------------------------ \n02 BLOB1-DATA. \n49 FILLER PIC(10485760). \n------------------------------ \nbut DB2 LUW writes only one line as below for above two lines part.\n------------------------------ \n02 BLOB1-DATA PIC(10485760). \n------------------------------ \n\nIt is an expected current DB2 LUW behavior and we don't have any hidden \noption to generate the cobol declarations similar to z\/OS precompiler.\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 scenario.\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\/]\n\nRELATED INFORMATION\n PRECOMPILE command [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0001964.html]\nCOBOL compiler configurations [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.apdv.embed.doc\/com.ibm.db2.luw.apdv.embed.doc-gentopic3.html]"}]},{"id":"DEV_Q115","question":"Help with Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031)\n\nI need to understand details regarding Security Bulletin: Apache Commons FileUpload Vulnerabilities in IBM WebSphere MQ File Transfer Edition component (CVE-2016-1000031). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q116","question":"Upgrading from ibm bpm 8.5 to ibm bpm 8.5.5\n\n\n\nHi there,\n\nI was wondering if it is possible to upgrade from ibm bpm 8.5 to 8.5.5 ? is this possible? please suggest. thanks \n","answer":"V8.5 Refresh Pack 5 is intended to be used on IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, and IBM Business Process Manager Advanced - Process Server installations.","is_impossible":false,"contexts":[{"filename":"swg27042065.txt","text":"Title: IBM Installation instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 - United States\n\nText:\n8.5.5 Installation Instructions; install; 8.5 refresh pack PRODUCT README\n\nABSTRACT\n This document provides instructions for installing V8.5 Refresh Pack 5 for the IBM Business Process Manager products. The same instructions should be used to update the Process Center and the Process Server. \n\nCONTENT\n\n\nTAB NAVIGATION\n * Refresh Pack download [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037683 ]\n * Refresh pack installation instructions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042065]- selected tab,\n * Profile upgrade instructions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066]\n * Recommended interim fixes [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037612]\n\nThis refresh pack is a cumulative maintenance package for a specific product and applies to all distributed operating systems. It is a single package that bundles a number of individual fixes.\n\nV8.5 Refresh Pack 5 is intended to be used on IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, and IBM Business Process Manager Advanced - Process Server installations.\n\nBy installing V8.5 Refresh Pack 5, you will raise the fix level of your product, either IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server, to Version 8.5.5.\n\nNote: You can roll out maintenance incrementally in an IBM Business Process Manager installation that consists of a Process Center and multiple Process Servers. This approach allows you to continually run production applications during the upgrade and regression test period. See [http:\/\/www14.software.ibm.com\/webapp\/wsbroker\/redirect?version=matt&product=was-nd-mp&topic=trun_svr_conf_backup] Performing a rolling upgrade [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/tmig_rolling_upgrade.html] in the product documentation.\n\nTable of Contents \n\n * Problems addressed in this refresh pack \n * Refresh pack prerequisites \n * Installing the refresh pack \n * Upgrade instructions for installations with existing profiles \n * Installing V8.5 Refresh Pack 5 \n * Upgrading the Process Designer \n * Refresh pack install verification \n * Rolling back V8.5 Refresh Pack 5 \n * Reference \n * Trademarks and service marks\n\n\n\n\u00a9 Copyright International Business Machines Corporation 2014. All rights reserved. \nUS Government Users Restricted Rights \u2013 Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. \n\n \n\nPROBLEMS ADDRESSED IN THIS REFRESH PACK\n\n\nThe fixes addressed in V8.5 Refresh Pack 5 are explained in the Fix List for the IBM Business Process Manager Version 8.5 products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27039722]document. \nBack to top\n\n\nRefresh pack prerequisites\n\nTo use this refresh pack, you must have Version 8.5 for the IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server product installed.\n\nYou must have WebSphere Application Server V8.5.5 Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037250] installed or you must install WebSphere Application Server V8.5.5 Fix Pack 2 during the upgrade process. This fix pack must be downloaded using FTP. In addition, you must install the fix pack image for all operating systems and platforms.\n\nWhen you decompress the following two files to the same location, it creates the full WebSphere Application Server V8.5.5 Fix Pack 2 repository that includes all WebSphere Application Server packages for all supported operation systems and architectures: \n\n * 8.5.5-WS-WAS-FP0000002-part1.zip 0.814 GB \n * 8.5.5-WS-WAS-FP0000002-part2.zip 1.59 GB\n\n\n\nHardware and software prerequisites for IBM Business Process Manager Express [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/express\/sysreqs\/], IBM Business Process Manager Standard [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/standard\/sysreqs\/], IBM Business Process Manager Advanced [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/sysreqs\/], and IBM Business Process Manager Advanced - Process Server [http:\/\/www.ibm.com\/software\/integration\/business-process-manager\/advanced\/sysreqs\/]are available on the web on their respective Hardware and Software Support pages. Important: If you receive a message warning that the ulimit setting is lower than recommended, set the ulimit value to 8192. Refer to Warnings about GTK or ulimit on Linux or UNIX when installing or migrating [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.admin.doc\/topics\/rins_trbl_warnings.html].\n\n\nBack to top\n\n\n\nINSTALLING THE REFRESH PACK\n\n\n\nUpgrade instructions for installations with existing profiles \n\nIf you have been using IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server V8.5 and you have created profiles, additional steps are required. Also, if you installed the product using the Typical installation, a profile was created and you must follow these steps. These steps include backing up the profile, stopping all Java\u2122 processes, and sequencing the upgrade. Before you continue with the refresh pack installation, follow the appropriate documentation for details and return to this document, when instructed, to complete the Version 8.5 Refresh Pack 5 installation. \n\nImportant: \nDepending on the source version and topology, instructions for updating the database vary. The product might not continue to run successfully if you do not follow the instructions. \n\nIf you are upgrading the environment from an IBM Business Process Manager 8.5 product to V8.5 Refresh Pack 5, follow the steps in Profile upgrade instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066]. \n\nBack to top\n\n\n \n\n \n\nInstalling V8.5 Refresh Pack 5 \n\n\n\nIf you have existing profiles under this installation, before you continue with the refresh pack installation, see [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038089]Profile upgrade instructions for IBM Business Process Manager Version 8.5 Refresh Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066] for details on the steps to follow for the various topologies. Return to this document, when instructed, to complete the Version 8.5 Refresh Pack 5 installation.\n\n\nDownload repositories to the local system\nThe IBM Installation Manager must be at a minimum level of Version 1.6.0 before you start the IBM Business Process Manager 8.5 Refresh Pack 5 installation updates. The Installation Manager detects an available update if you are connected to the Internet on the workstation on which you are planning to complete the IBM Business Process Manager 8.5 Refresh Pack 5 update activities. WebSphere Application Server V8.5.5 Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037250] is a prerequisite to IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server V8.5 Refresh Pack 5.\n\nIf the machine where you are upgrading the product has Internet access, skip the following steps. \n\n 1. Download the appropriate refresh pack using the Version 8.5 Refresh Pack 5 for the IBM Business Process Manager products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037683] document. Download bpm.8550.delta.repository.zip to a temporary disk location. \n \n \n 2. Download and installWebSphere Application Server Version 8.5.5 Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035935], if it is not yet installed. IBM Business Process Manager no longer bundles the WebSphere Application Server fix pack. This fix pack, which is required for IBM Business Process Manager, is available through Fix Central.\n \n \n When you decompress the following two files to the same location, it creates the full WebSphere Application Server V8.5.5 Fix Pack 2 repository that includes all WebSphere Application Server packages for all supported operation systems and architectures:\n \n \n 8.5.5-WS-WAS-FP0000002-part1.zip 0.814 GB\n 8.5.5-WS-WAS-FP0000002-part2.zip 1.59 GB\n \n \n 3. Unpack the repositories to any directories that you choose. Note where you have unpacked the repositories. You should unpack each repository to its own directory.\n\n\nYou can install the fix packs by using one of the following options: \nGraphical user interface (GUI) of IBM Installation Manager to update an installation \nCommand line interface of IBM Installation Manager for a silent installation \n\nGraphical user interface (GUI) of IBM Installation Manager to update an installation \n\n 1. Start the Installation Manager. \n \n \n On Windows operating systems with Internet access, click Start > Programs > IBM > IBM_BUSINESS_MANAGER_PRODUCT > Update. Then skip to step 3b.\n \n \n If you are on a Linux or UNIX-based system, start IBM Installation Manager using the install_location\/IBMIM command. On Windows operating systems, use the install_root\\IBMIM.exe command. See Installation directories for the product and profile [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/rins_installation_paths.html] for more information on where Installation Manager is installed.\n \n \n Note: On Microsoft Windows operating systems, right-click install_root\\IBMIM.exe and select Run as administrator.\n \n \n 2. Add repositories to the IBM Installation Manager preferences.\n \n \n Click File > Preferences. Under Repositories, select one of the following options: * If you have Internet access, ensure that the Search service repositories during installation and updates option is selected.\n \n \n * If you do not have Internet access, add the location of all the local repositories that you downloaded from the Download repositories to local system section. 1. Click Add Repository. \n \n \n 2. Type or browse to the repository.config file for the IBM Business Process Manager repository that you have unpacked.\n \n \n 3. Click OK. \n \n \n 4. Repeat this process for the interim fix repositories and the WebSphere Application Server fix pack repository, if necessary.\n \n \n 5. Click OK to save the new repository settings.\n \n \n \n \n \n \n 3. Use the following steps to install graphically: 1. Click Update.\n \n \n 2. Select the Package Group where you have installed IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server.\n \n \n 3. Click Next > to continue.\n \n \n After Installation Manager checks the service repositories, the Update Packages window opens and the IBM Business Process Manager Express, IBM Business Process Manager Standard, IBM Business Process Manager Advanced, or IBM Business Process Manager Advanced - Process Server Version 8.5 Refresh Pack 5 is shown, unless there is a later fix pack available from the live update repository.\n \n \n If you are installing WebSphere Application Server Version 8.5.5 Fix Pack 2, that is also shown.\n \n \n 4. Ensure that the refresh pack and fix pack are selected. Clear the Show recommended only check box, so that you will be able to see the WebSphere Application Server interim fixes in the next step. Click Next >. If you have Internet connectivity or have added local interim fix repositories, another Update Packages window opens. A list of interim fixes is displayed. \n \n \n 5. Select all the recommended interim fixes for IBM Business Process Manager V8.5.5 and all the recommended interim fixes for WebSphere Application Server. Refer to Recommended interim fixes for IBM Business Process Manager V8.5 Refresh Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24037612]. \n \n \n 6. Ensure that the interim fixes are all selected and then click Next > to continue. The Licenses window opens.\n \n \n 7. Read and accept the terms of the license agreements by selecting the appropriate button and click Next > to continue. The Features window opens. All of the installed features will be selected.\n \n \n 8. Click Next > to continue. The Summary window opens. All of the features that need to be updated are shown. The disk space that is required to perform the update is shown at the bottom.\n \n \n 9. Click Update to start the update. The updates are downloaded either from the live update repository or from your local repository. The updates are installed. After the installation of the updates is complete, you receive a confirmation.\n \n \n\n * \n\nNote:During a full installation when you have Internet access, follow the normal installation instructions for a full installation. Go to Install Packages> Check for Other Versions and Extensions. All of the latest versions are discovered. Follow the instructions to select the Show all versionscheck box, and then proceed with the full installation as normal. \nBack to top\n\n\n\n\nCommand line interface of IBM Installation Manager for a silent installation \n\nInstallation Manager offers a command-line interface to update your product installation silently. \n 1. Use the following command to update your IBM Business Process Manager product to V8.5 Refresh Pack 5:\n \n \n IM_INSTALL_LOCATION\/tools\/imcl install PACKAGE_IDS FIX_IDS -acceptLicense -installationDirectory INSTALL_DIR-repositories REPOSITORIES-log LOG_FILE\n \n \n Update the variables in the previous command specifically for your installation using the following information:\n \n * IM_INSTALL_LOCATION\n This variable represents the location where Installation Manager is installed. See Installation directories for the product and profile [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/rins_installation_paths.html] for more information on Installation Manager default installation directories.\n \n \n * PACKAGE_IDS\n This variable represents the list of packages to be updated. Package IDs are separatedby spaces. Use the following list to get the correct package IDs for your product.\n \n * IBM Business Process Manager Express\n com.ibm.bpm.EXP.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Standard\n com.ibm.bpm.STD.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Advanced\n com.ibm.bpm.ADV.v85\n com.ibm.websphere.ND.v85 \n * IBM Business Process Manager Advanced - Process Server\n com.ibm.bpm.PS.v85\n com.ibm.websphere.ND.v85\n \n \n \n \n * FIX_IDS\n This variable represents the interim fix IDs for any interim fixes that you need to install.\n \n \n * INSTALL_DIR\n This variable represents the installation directory of the product.\n \n \n * REPOSITORIES\n This variable represents the location of the refresh pack and interim fix repositories.\n \n \n Note: Use commas to separate multiple locations.\n \n \n * LOG_FILE\n This variable represents the location and name of the silent log file to write.\n \n \n By including the -acceptLicense parameter, you agree to the terms and licenses of this product.\n \n \n \n \n 2. After updating the command for your environment, run the command from the tools directory under the Installation Manager install location. \n \n The following command is an example in which only the IBM Business Process Manager refresh pack needs to be applied:\n C:\\Program Files (x86)\\IBM\\Installation Manager\\eclipse\\tools\\imcl install com.ibm.bpm.PS.v85 -acceptLicense -installationDirectory C:\\IBM\\BPM\\v8.5 -repositories C:\\BPM855_repository -log silent_update.txt \n 3. When the silent refresh pack installation completes, check the log files to ensure that the installation completes successfully. A success message that is similar to the following text displays on the command line:\n \n Updated to com.ibm.bpm.ADV.v85_8.5.5000.20140604_1130 in the C:\\IBM\\BPM\\v8.5 directory\n \n\n\n\nFor additional information about silent installations, visit the product documentation links in the following table: Product Content Links IBM Business Process Manager Express [http:\/\/pic.dhe.ibm.com\/infocenter\/dmndhelp\/v8r0m1\/topic\/com.ibm.wbpm.imuc.stbpm.doc\/topics\/inst_sil_cmd_lin.html]AIX [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.stbpm.doc\/topics\/inst_sil_cmd_aix.html]\nLinux [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.stbpm.doc\/topics\/inst_sil_cmd_lin.html]\nWindows [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.stbpm.doc\/topics\/inst_sil_cmd_win.html] IBM Business Process Manager Standard AIX [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.sbpm.doc\/topics\/inst_sil_cmd_aix.html]\nLinux [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.sbpm.doc\/topics\/inst_sil_cmd_lin.html]\nSolaris [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.sbpm.doc\/topics\/inst_sil_cmd_sol.html]\nWindows [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.sbpm.doc\/topics\/inst_sil_cmd_win.html] IBM Business Process Manager Advanced AIX [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpm.doc\/topics\/inst_sil_cmd_aix.html]\nLinux [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpm.doc\/topics\/inst_sil_cmd_lin.html]\nSolaris [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpm.doc\/topics\/inst_sil_cmd_sol.html]\nWindows [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpm.doc\/topics\/inst_sil_cmd_win.html] IBM Business Process Manager Advanced - Process Server AIX [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpmps.doc\/topics\/inst_sil_cmd_aix.html]\nLinux [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpmps.doc\/topics\/inst_sil_cmd_lin.html]\nSolaris [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpmps.doc\/topics\/inst_sil_cmd_sol.html]\nWindows [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.ebpmps.doc\/topics\/inst_sil_cmd_win.html] \n\nAlternatively, you can use the Interactive Installation and Configuration Guide [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/bpm_roadmap_form.html]and follow the instructions. \nBack to top\n\n\n \n\nUpgrading the Process Designer \n\nAfter you update your Process Center with a fix pack, refresh pack, or interim fix, you must update the Process Designer to the same level. To make the updates, download the Process Designer file again and run the installation. Only the fixes or changes are applied.\n\n\nAbout this task\nWhen you install the fix pack, refresh pack, or interim fix, the IBM Process Designer.zip file is updated also. You must download it and install the updated Process Designer to the directory where you already installed Process Designer.\n\n\nProcedure \n\n 1. Open the Process Center.\n \n \n 2. Click the IBM Process Designer Download option. \n \n \n 3. When you are prompted, save the IBM Process Designer.zip file to your file system. This file contains everything that you need to install and run IBM Process Designer. Depending on your network connection, the download might take several minutes to complete.\n \n \n 4. Extract the contents of the IBM Process Designer.zip file to a temporary directory on your file system.\n \n \n 5. Open a command window and change to the directory where you extracted the contents of the IBM Process Designer.zip file. \n \n \n Important: If you are running Microsoft Windows 7, Windows Vista, or Windows Server 2008, right-click the command prompt and select Run as administrator.\n \n \n 6. Run one of the following commands to update the Process Designer. Use the same command that you used to install the Process Designer. * Default location (C:\\IBM\\ProcessDesigner\\v8.5) * installProcessDesigner_admin.bat \n * installProcessDesigner_nonadmin.bat\n \n \n \n \n * Different location * installProcessDesigner_admin.bat install_location \n * installProcessDesigner_nonadmin.bat install_location\n \n \n \n If the location has spaces in the directory name, put the whole location in quotation marks. The following examples show how to install to a different location. * installProcessDesigner_admin.bat D:\\IBM\\PD \n * installProcessDesigner_admin.bat \"D:\\Process Designer\\\"\n \n \n \n \n\n\nResults \nIBM Process Designer is updated. Only the fixes or changes are applied. Installation messages are recorded in the %TEMP%\\IBMProcessDesignerInstall.log file, where the %TEMP% variable is typically set to C:\\Documents and Settings\\current_user_name\\Local Settings\\Temp.\n\n\nBack to top\n\n\n\nRefresh pack install verification \n\nFor upgrades of installations with existing profiles, refer to the Identifying profile update errors [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066#identify] section under the Profile upgrade tab for details on verifying the refresh pack installation. \n\nNote: Installation Manager on the Microsoft Windows operating system does not recognize profile update errors. When you upgrade an installation on Windows, you must look at the Identifying profile update errors [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066#identify] section, even if Installation Manager ends with the following message: The packages are updated. \nBack to top\n\n\n\nRolling back V8.5 Refresh Pack 5 \n\nYou can roll back the refresh pack to a previous version by using one of the following options:\nGraphical user interface (GUI) of IBM Installation Manager to roll back an installation\nCommand line interface of IBM Installation Manager for a silent roll back of a refresh pack\n\nNote: The following procedure rolls back only the product binary. Any existing profiles that were upgraded during a refresh pack installation are not rolled back; you must restore the profiles from the backup you took before you upgraded the product. Any new profiles created after the upgrade cannot be reused; you must delete and recreate the profiles after you have completed the rollback process.\n\n\nGraphical user interface (GUI) of IBM Installation Manager to roll back an installation\n\n\n 1. Close all programs that were installed using Installation Manager before rolling back.\n \n \n 2. Start Installation Manager. See Installation directories for the product and profile [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/rins_installation_paths.html] for more information on where Installation Manager is installed.\n \n \n 3. From the Start page of the Installation Manager, click Roll back to start the Roll back packages wizard.\n \n \n 4. On the Roll Back Packages page, from the Package Group Name list, select the package group that contains the packages that you want to roll back and click Next.\n \n \n 5. Select the version of the package to which you want to roll back and click Next. \n \n \n 6. Read the summary information and click Roll Back to roll back the package. \n \n \n When the rollback process completes, a message that confirms the success of the process is displayed near the top of the page. \n \n \n 7. Optional: Click View log file to open the log file for the current session in a new window. \n \n \n 8. Click Finish to close the wizard. \n \n \n 9. Close Installation Manager. \n \n \n 10. Restore the backed up data from the original version.\n\n\n\nBack to top\n\n\n\nCommand line interface of IBM Installation Manager for a silent rollback of a refresh pack \n\nInstallation Manager offers a command-line interface to silently roll back your product installation to the previous version. In the instructions, it is assumed that you completed all of the necessary profile, database, and refresh pack-specific data backup tasks, which are described in Profile upgrade instructions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27042066], before you migrated to Version 8.5 Refresh Pack 5. This data is restored after you complete the rollback task. \n\n 1. Use the following command to roll back your IBM Business Process Manager product to V8.5.0.0.\n \n \n IM_INSTALL_LOCATION\/tools\/imcl rollback PACKAGE_IDVERSION-installationDirectory INSTALL_DIR-log LOG_FILE\n \n \n Update the following variables for your installation: * IM_INSTALL_LOCATION\n This variable represents the location where Installation Manager is installed. See Installation directories for the product and profile [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS_8.5.5\/com.ibm.wbpm.imuc.doc\/topics\/rins_installation_paths.html] for more information on Installation Manager default installation directories.\n \n \n * PACKAGE_ID\n This variable represents the package ID of the product installed.\n \n \n * VERSION\n This variable represents the original version of the product. Rolling back returns your installation to this version. This version will be Version 8.5.0.0. If you have upgraded directly from Version 8.5.0, see the Details for rolling back to Version 8.5.0.0 information. \n \n * Details for rolling back to Version 8.5.0.0 * IBM Business Process Manager Express\n Package ID: com.ibm.bpm.EXP.v85\n Version: 8.5.0.20130504_0134 \n * IBM Business Process Manager Standard\n Package ID: com.ibm.bpm.STD.v85\n Version: 8.5.0.20130504_0135 \n * IBM Business Process Manager Advanced \n Package ID: com.ibm.bpm.ADV.v85\n Version: 8.5.0.20120504_0137 \n * IBM Business Process Manager Advanced - Process Server\n Package ID: com.ibm.bpm.PS.v85\n Version: 8.5.0.20120504_0137\n \n \n * Details for rolling back to Version 8.5.0.1\n IBM Business Process Manager Express\n Package ID: com.ibm.bpm.EXP.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Standard\n Package ID: com.ibm.bpm.STD.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Advanced\n Package ID: com.ibm.bpm.ADV.v85\n Version: 8.5.1.20131107_1830\n \n IBM Business Process Manager Advanced - Process Server\n Package ID: com.ibm.bpm.PS.v85\n Version: 8.5.1.20131107_1830 \n \n \n \n * INSTALL_DIR\n This variable represents the installation directory of the product.\n \n \n * LOG_FILE\n This variable represents the location and name of the silent log to write.\n \n \n \n \n \n \n 2. After updating the command for your environment, run the command from the tools directory under the Installation Manager installation location. \n \n The following command is an example:\n \n C:\\Program Files (x86)\\IBM\\Installation Manager\\eclipse\\tools\\imcl rollback com.ibm.bpm.EXP.v85_8.5.1.20131107_1830 -installationDirectory C:\\IBM\\BPM\\v8.5 -log silent_rollback.txt\n \n \n 3. When the rollback completes, check the log files to ensure that the rollback completed successfully. A success message displays on the command line:\n \n Rolled back to com.ibm.bpm.EXP.v85_8.5.1.20131107_1830 in the C:\\IBM\\BPM\\v8.5 directory. \n \n \n 4. Restore the profile and the database backup taken prior to installing Refresh Pack 5.\n \n\nBack to top\n\n\nReference\n\nYou can find additional information on any of these topics in the IBM Business Process Manager [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFPJS\/welcome] product documentation.\n\nFor further information on the update strategy or obtaining updates, see the support page for your product.\n\nIBM Business Process Manager Express Support page [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Express]\nIBM Business Process Manager Standard Support page [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Standard]\nIBM Business Process Manager Advanced Support page [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced]\nIBM Business Process Manager Advanced Process Server Support page [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/WebSphere\/IBM_Business_Process_Manager_Advanced]\n\n\nBack to top\n\n\nTrademarks and service marks: \nFor trademark attribution, visit the IBM Terms of Use [http:\/\/www.ibm.com\/legal] Web site. \nBack to top\n\n\n\n\n\n\nORIGINAL PUBLICATION DATE\n 2013\/11\/15 \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation \/ Configuration AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5 Business Integration IBM Business Process Manager Express Installation \/ Configuration Linux, Windows 8.5.5 PRODUCT ALIAS\/SYNONYM\n BPM"}]},{"id":"DEV_Q117","question":"Migrating ITCAM for AD 7.1 agent to ITCAM for WebSphere Applications v7.2 agent\n\nIs there a suggested migration path from ITCAM for AD v7.1 agent to ITCAM for WebSphere Applications v7.2 agent and Data Collector?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q118","question":"db2top abnormally ended with core dump during monitoring SQL statements\n\nI'm using DB2 9.7 FP6. The db2top utility abnormally ended with a core dump during monitorning SQL statements with following stack trace in the trap file. What is the cause of the problem?\n\n <StackTrace>\n -------Frame------ ------Function + Offset------\n 0x0900000010127AEC waddnstr + 0x6C\n 0x0900000010134E90 waddstr + 0x10\n 0x0900000010135440 vw_printw + 0x40\n <\/StackTrace>","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q119","question":"Why does the Dataserver service change from Healthy to Vulnerable after logging into StoredIQ Application Stack?\n\nWhy does the Dataserver service change from Healthy to Vulnerable after logging into StoredIQ Application Stack? ","answer":"This could be due to amount of Memory allocated to the dataserver.","is_impossible":false,"contexts":[{"filename":"swg21997033.txt","text":"Title: IBM Dataserver services changing from Healthy to Vulnerable - United States\n\nText:\nSIQ TECHNOTE (FAQ)\n\nQUESTION\n Why does the Dataserver service change from healthy to Vulnerable after logging into appstack? \n\nCAUSE\nMemory allocated was not the supported number\n\nANSWER\n \n\nThis could be due to amount of Memory allocated to the dataserver. \n\n 1. Login to the Dataserver \n 2. Click on Administration > Dashboard tab \n 3. Review the Application status and make sure it is green \n 4. Click on Controller Link \n 5. Review and confirm that all services are running fine \n 6. If needed, make changes to memory"}]},{"id":"DEV_Q120","question":"Why do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3?\n\nWhy do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3? ","answer":"This happens when the BIRT Reports is running in Standalone mode and happens due to a new configuration - report.standalone.userid","is_impossible":false,"contexts":[{"filename":"swg21982354.txt","text":"Title: IBM Server Error Message when running BIRT Reports after upgrading to Atlas 6.0.3.3 - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why do we get server error message when running BIRT reports after upgrading to Atlas 6.0.3.3? \n\nCAUSE\nThis happens when the BIRT Reports is running in Standalone mode and happens due to a new configuration - report.standalone.userid\n\nANSWER\n \n\n 1. Navigate to Atlas Properties Folder \n 2. Edit AtlasReportConfig.properties \n 3. Uncomment the property #report.standalone.userid=1 \n 4. Save the change \n 5. Restart both Atlas and Atlas Reports application server instances"}]},{"id":"DEV_Q121","question":"Job Execution Node for IIB V10\n\nI'm looking for a way in IIB V10 to execute\/invoke scripts or jobs on different operating systems like windows or System i (AS400). After a little research i found out that there is a Job Execution Node for the IIB V9, which seems to cover the requirements. Is there a Job Execution Node for the IIB V10, or an other appropriate node for the requirements?\n","answer":"The JobExecutionNode, a Java-based plugin, allows you to execute operating system commands, and invoke jobs in the form of batch\/shell scripts from within the message flow. The jobs can be specified on the node property or as a part of the input message.","is_impossible":false,"contexts":[{"filename":"swg24017225.txt","text":"Title: IBM IA9Z: WebSphere Message Broker - Job Execution Node - United States\n\nText:\nia9z; Job Execution; Batch files; Shell scripts DOWNLOADABLE FILES\n\nABSTRACT\n WebSphere Message Broker \u2013 Job Execution Node \n\nDOWNLOAD DESCRIPTION\nYou might need to invoke operating system commands, windows batch files, or Unix shell scripts (henceforth referred to as jobs) from within the message flow. You might also want to schedule jobs at a specific time\/interval\/frequency.\n\n\nThe JobExecutionNode, a Java-based plugin, allows you to execute operating system commands, and invoke jobs in the form of batch\/shell scripts from within the message flow. The jobs can be specified on the node property or as a part of the input message. \n\nPossible Uses \n\n * You can execute operating system commands, and invoke jobs in the form of batch\/shell scripts from within the message flow. \n * You can schedule the tasks at a specific time (using Timer nodes) and execute them from the Message flows. \n * You can enrich the message by using the result\/output of the job execution.\n\n\nNew in this Release \n\u2022 Works with IIB V10. \n\nDetails \nAuthors: Amar Shah, Shravan Kudikala, ISL-Messaging \nCategory: 2 \nReleased: 26Oct07 \nLast Updated: 09Dec15 \nCurrent SupportPac Version: 1.5 \n\u00bbPlease note that the version number shown in the right-hand pane is the version of the MQ or WBI product that this SupportPac applies to. The date is the last webpage refresh. \n\nTo view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage. [http:\/\/www-306.ibm.com\/software\/integration\/support\/supportpacs] PREREQUISITES\nIBM Integration Bus - V9 or higher\nWebSphere Message Broker \u2013 V6.1 or higher.\n\nINSTALLATION INSTRUCTIONS\nUnzip the SupportPac and read the user manual. Details are inside the user manual guide.\n\nURL LANGUAGE SIZE(Bytes) ia9z.pdf [ftp:\/\/public.dhe.ibm.com\/software\/integration\/support\/supportpacs\/individual\/ia9z.pdf] US English 402008 \nDOWNLOAD PACKAGE\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options ia9z.zip 26 Nov 2013 US English 626688 HTTP [http:\/\/www14.software.ibm.com\/cgi-bin\/weblap\/lap.pl?popup=Y&li_formnum=L-TMAN-785DAH&accepted_url=ftp:\/\/public.dhe.ibm.com\/software\/integration\/support\/supportpacs\/individual\/ia9z.zip] \nTECHNICAL SUPPORT\n Category 2 SupportPacs are provided in good faith and AS-IS. There is no warranty or further service implied or committed and any supplied sample code is not supported via IBM product service channels. \n\nYou may submit a question and return email address using the 'rate this page' below, but a response is not guaranteed.\n\nPlease read the license information contained within the zip file of this SupportPac to determine if you want to use it. \n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Integration Bus Standard 9.0"}]},{"id":"DEV_Q122","question":"Importing Asset GL Errors\n\n When importing or syncing with assets, I receive the following error for the glaccount.\n\nInternal Server Error\nError 500: nested exception is: psdi.util.MXAccessException: BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field.\n ","answer":"Add the following field or tag to your inbound message. For example, if you are sending XML: \n\n<NEWORGID>xxx<\/NEWORGID> \n\nwhere xxx is the ORGID value. \n\nMake sure that NEWORGID is included on the object structure. \n\nGo To Integration > Object Structures and query the object structure. \n\nFrom the Select Action menu drop down, select Exclude\/Include Fields and select the Non-Persistent Fields tab. Include NEWORGID.","is_impossible":false,"contexts":[{"filename":"swg21969653.txt","text":"Title: IBM BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. - United States\n\nText:\nTAPEINTEGRATION; asset; MIF TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When importing ASSET using the Integration Framework you receive the following error after applying an IFIX or FIXPACK:\n\nBMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field. \n\nCAUSE\nThis error is occurring due to a fix made for APAR IV67500 and included in a Maximo 7.5.0.6 or later ifix. The fix requires that the neworgid is included in the message.\n\nDIAGNOSING THE PROBLEM\nYou will see a stack trace similar to the following in the system out log: \n\npsdi.util.MXAccessException: BMXAA4198E - The GL attribute TLOAMNEWGLACCOUNT on object {1} requires an organization. Specify a value in the Organization field. \nat psdi.mbo.Mbo.getOrgForGL(Mbo.java:6976) \nat psdi.mbo.MboGLValue._setValue(MboGLValue.java:59) \nat psdi.mbo.MboValue.setValue(MboValue.java:1141) \nat psdi.mbo.Mbo.setValue(Mbo.java:2175) \nat \npsdi.app.asset.FldMoveModifyAssetNewGLAccount.initValue(FldMoveModifyAssetNewGLAccount.java:53) \nat psdi.mbo.MboValue.initValue(MboValue.java:404) \nat psdi.mbo.MboValue.isNull(MboValue.java:507) \nat psdi.mbo.Mbo.isNull(Mbo.java:2839) \nat \npsdi.iface.app.asset.MaxAssetProcess.setAdditionalData(MaxAssetProcess.java:85) \nat \npsdi.iface.mos.MosProcessImpl.setMainMaximoTable(MosProcessImpl.java:767\n) \n...\n\n\nRESOLVING THE PROBLEM\nAdd the following field or tag to your inbound message. For example, if you are sending XML: \n\n<NEWORGID>xxx<\/NEWORGID> \n\nwhere xxx is the ORGID value. \n\nMake sure that NEWORGID is included on the object structure. \n\nGo To Integration > Object Structures and query the object structure. \n\nFrom the Select Action menu drop down, select Exclude\/Include Fields and select the Non-Persistent Fields tab. Include NEWORGID."}]},{"id":"DEV_Q123","question":"Resource registry with IIB\n\n\n\nHi Team, \n\nI do had a scenario to be accomplished in IIB, in which one input should be passed from MQ and the other should be passed from FILE(for this i have been using Resource Registry Concept) and in order to specify mrc file i have modified dtx.ini file which is located in Integration server Insatllation directory but when the flow has been deployed an exception is being raised with the error message stating \"Source not found\" .\n\nFYI - When i tried the RR from Design Studio it is working absolutely fine.\n\nIs there something i need to configure\/modify so that the mrc file will be accessible to the map in IIB flow as well.","answer":"WebSphere Transformation Extender maps that are called from WebSphere Message Broker can use the WebSphere Transformation Extender Resource Registry. WebSphere Message Broker itself does not provide any facility for working with resource registries in areas of the message flow outside of the WebSphere Transformation Extender plugin.","is_impossible":false,"contexts":[{"filename":"swg21419540.txt","text":"Title: IBM Clarification of WebSphere Message Broker support of Resource Registry with WebSphere Transformation Extender for Message Broker - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Does IBM\u00ae WebSphere\u00ae Message Broker support a Resource Registry file from IBM WebSphere Transformation Extender for Message Broker? \n\nANSWER\nWebSphere Transformation Extender maps that are called from WebSphere Message Broker can use the WebSphere Transformation Extender Resource Registry. WebSphere Message Broker itself does not provide any facility for working with resource registries in areas of the message flow outside of the WebSphere Transformation Extender plugin. \n\nIn the WebSphere Transformation Extender for Message Broker documentation, the following sentence in the topic \"Setting resource registry on execution groups:\" \n\n\nConfigure WebSphere Message Broker to use the WebSphere Transformation Extender Resource Registry by setting the resource configuration (.mrc) file on execution groups. \n\n\n\n\nShould read: \n\n\nConfigure WebSphere Transformation Extender for Message Broker to use the WebSphere Transformation Extender Resource Registry by setting the resource configuration (.mrc) file on the WebSphere Message Broker execution groups."}]},{"id":"DEV_Q124","question":"Is there a scripting feature in ITM?\n\nIs there a scripting feature in ITM? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q125","question":"Error when using profilePath parameter with BPMConfig to create a profile\n\nWhen 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 <profile_path> must not exist. com.ibm.bpm.config.util.ConfigException: The profile path <profile_path> must not exist. at com.ibm.bpm.config.BPMConfig.createDmgrProfile(BPMConfig.java:1833) at com.ibm.bpm.config.BPMConfig.configureDeploymentEnvironment(BPMConfig.java:6\n...","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q126","question":"Why is WebSphere MQ connection failing when enabling SSL with AMQ9640 SSLPEER peer name error?\n\nWhy is WebSphere MQ connection failing when enabling SSL with AMQ9640 SSLPEER peer name error?\nexample client side error:com.ibm.mq.jmqi.JmqiException: CC=2;RC=2399;\n \nAMQ9640: SSL invalid peer name, channel '?',\n \nattribute 'OID.0.9.2342.19200300.100.1.3 (x2)'.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q127","question":"Help with Security Bulletin: Vulnerability in IBM Java Runtimes affect Websphere Business Modeler Advanced and Websphere Business Modeler Basic (CVE-2015-0138)\n\nI need to understand details regarding Security Bulletin: Vulnerability in IBM Java Runtimes affect Websphere Business Modeler Advanced and Websphere Business Modeler Basic (CVE-2015-0138). Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q128","question":"IIS\/SSL related error after appliying FP41 on WAS7.0\n\n\n\nhi\n\nGetting below error while hitting the application URL, after upgrading fix pack from 7.0.0.29 to 7.0.0.41\n\nSSLHandshakeE E SSLC0008E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: Client requested protocol SSLv3 not enabled or not supported","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q129","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)\n\nI 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":"\n\nCVEID: 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 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\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 for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:H\/Au:N\/C:P\/I:P\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21962588.txt","text":"Title: 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\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 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."}]},{"id":"DEV_Q130","question":"Improve Performance of Decision Center and Rule Team Server (RTS)\n\nHow can I improve the performance of ODM Decision Center and WebSphere ILOG Rule Team Server (RTS)? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q131","question":"Refining search results by content type in Quickr doesn't work as expected\n\nQuestion: Refining of search results returned in the Search Center by clicking on content types eg: blogs and wikis does not return any reduced result set. The only refining content type which works is 'files' ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q132","question":"What is the meaning of value \"unknown\" for ITCAM WAS Application Status attribute?\n\nWhat is the meaning of value \"unknown\" for ITCAM WAS Application Status attribute?","answer":"By default baselining gets enabled with a situation WasAppDiscoverd. This situation is enabled by default and will discover new applications then run a take action to start the baselining. So if this situation is not enabled then you should enable it and assign to the ITCAM App Server managing system list.","is_impossible":false,"contexts":[{"filename":"swg21653905.txt","text":"Title: IBM How to enable Baselining in your monitored application. - United States\n\nText:\ntema enable baselining Unknown application health status CAMADALL CAMADINST TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Steps to enable Baselining in your monitored application. \n\nANSWER\nThe health of the monitored application is calculated against an internally stored baseline threshold. The baselining of the application is a process that uses a pre-defined mathematical and statistical method to automatically calculate a threshold based on response time information typically collected over a period of time (few days to few weeks.) \n\nBy default baselining gets enabled with a situation WasAppDiscoverd. This situation is enabled by default and will discover new applications then run a take action to start the baselining. So if this situation is not enabled then you should enable it and assign to the ITCAM App Server managing system list. \n\nYou want to do baselining with normal or typical load on the server over a period of few days to few weeks, or even few months. The performance of the application under this load is considered good (you will see \"Good\"\" in the Application Health views) and deviation from this performance indicates degrading health (\"Bad\" or \"Fair\" in the Application Health views) of the monitored application. \n\nTo start baselining for your application server, please follow these steps: \n\n(Note 1: in this example, I've used a WebSphere-based application but you can also do the same for any application on your J2EE agent also.) \n\n(Note 2: Before beginning baselining, make sure you have typical or normal load on the server to set the baselining threshold values.) \n\n1. Login to your TEPS, select Application Health, right-click on it, go to Workspace and select Application Registry. Look at the panels on the right and observe the baselining columns. If they're blank, your baselining has not been started. \n\n2. Next select Application Health, right-click on it, go to Workspace and select Application Health status. If you see Unknown, then you know the baselining has not started or not been calculated. \n\n3. High-lite your application, select the small yellow chain link in the first unnamed column and select Application Configuration Details. See screenshot here: \n\n[\/support\/docview.wss?uid=swg21653905&aid=1] [\/support\/docview.wss?uid=swg21653905&aid=1] \n\n4. In the bottom panel on the right select the line that says All and high-lite it. Then right-click it, select Take Action and Select. In the pull-down, select Start_Baselining and enter the Period (2 days), Update_Interval (every 2 hours), and Run_Clean set to 1 (clean start.) If you wish, you can change these values to whatever you want. \n\nSee screenshots here:\n[\/support\/docview.wss?uid=swg21653905&aid=2] [\/support\/docview.wss?uid=swg21653905&aid=2]\n[\/support\/docview.wss?uid=swg21653905&aid=3]\nHit OK twice and you should get a Command completed successfully message. (Note: If you get a Baselining_Already_Active message in the pop-up window, then you should do another Take Action and Stop_Baselining first if you want to do the baselining again.)\n\nOnce you have the baselining active, let it run for the period of time with typical load on the server. After the baselining is complete, the Unknown values in the Application Health should now change to Good or Fair or Bad depending on threshold values.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Web Resources ITCAM for Web Resources (J2EE TEMA) AIX, HP-UX, Linux, Solaris, Windows, Solaris Opteron 6.1, 6.2 Advanced \nPRODUCT ALIAS\/SYNONYM\n ITCAM ITCAM4AD ITCAMfAD TEMA ITCAM for Web Resources"}]},{"id":"DEV_Q133","question":"Do I need to backup \/opt\/ibm-ucd\/server\/var\/sa\/dialogue ?\n\nMy UCD server has so many files in \/opt\/ibm-ucd\/server\/var\/sa\/dialogue that ls goes out of memory trying to list them all. Looking at another (small) server I can see that the files within are roughly 2k on average, and judging by the apparent size of the directory (100Mb) I've probably got 50000+ files in there.\n\nDo I need to backup this directory? From what I've read, I believe this directory contains records of in-flight communication between UCD and the agents - but assuming the server is down, is it safe to assume that no such activity is occurring? Can I periodically clean this directory?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q134","question":"I am receiving AC power supply failures on my DataPower 9235 appliance. How can I resolve this?\n\n\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.\nDo i need to replace the power supplies?","answer":"This problem is caused by a highly intermittent error that may allow the sensor reading mechanism to get into a bad state. This bad state then generates the false error messages.","is_impossible":false,"contexts":[{"filename":"swg21512291.txt","text":"Title: IBM WebSphere DataPower M\/T 9235 appliance might incorrectly report failure of both power supplies - United States\n\nText:\n 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 \u2192 System Control \u2192 In the \u201cShutdown\u201d section choose \u201cReboot System\u201d then click \u201cShutdown\u201d \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"}]},{"id":"DEV_Q135","question":"DataPower upgrade message Loading firmware failed: Preserve user modified data failed: Insufficient flash space available Could not install firmware image. The system will not reboot.\n\nIn the process of upgrading my IBM DataPower Gateway I saw the following message:\n\"Loading firmware failed: Preserve user modified data failed: Insufficient flash space available Could not install firmware image. The system will not reboot.\"\nWhat does this mean and what are the appropriate next actions? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q136","question":"Compose tab appears disabled and project is not editable in Decision Center\n\nI have upgraded my ODM version and a project in Decision Center appears non editable :\n\nthe compose tab is disabled\nin explore tab there are no new nor edit button","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q137","question":"What things are important to consider when installing a fix pack for IIB running on a multi-instance environment?\n\nI am planning to apply a fix pack to my current version of IBM Integration Bus (IIB) using multi-instance brokers and I am looking for any important information regarding the process.\n\nFor example:\n\n \n\n- installation and verification tasks\n \n\n- is it possible to back out this fix pack in case there are issues\n \n\n- any specific tasks for multi instance configuration","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q138","question":"How to fix the DB2 errors in Portal ?\n\nHow could we fix the below DB2 errors in WebSphere Portal:\n\nDB2 SQL Error: SQLCODE=-551, SQLSTATE=42501, SQLERRMC=WPUSER;SELECT;JCR.SHORTCUT_SEQ, DRIVER=4.15.113\n\nDB2 SQL Error: SQLCODE=-727, SQLSTATE=56098, SQLERRMC=2;-551;42501;WPUSER|SELECT|JCR.SHORTCUT_SEQ, DRIVER=4.15.113","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q139","question":"Help with Security Bulletin: IBM WebSphere MQ is affected by a privilege escalation vulnerability (CVE-2017-1612)\n\nI need to understand details regarding Security Bulletin: IBM WebSphere MQ is affected by a privilege escalation vulnerability (CVE-2017-1612).","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q140","question":"Why get SQL1227N when replay db2look output on DB2 V9.7 FP11?\n\nWhy get below SQL1227N when replay db2look output on DB2 V9.7 FP11?\n\n -----\n UPDATE SYSSTAT.COLUMNS SET COLCARD=4, NUMNULLS=1, SUB_COUNT=-1, SUB_DELIM_LENGTH=-1, \n AVGCOLLENCHAR=7, HIGH2KEY='', LOW2KEY=' ', AVGCOLLEN=12 WHERE COLNAME = 'COL1' \n AND TABNAME = 'TAB1' AND TABSCHEMA = 'DB2INST1'\n DB21034E The command was processed as an SQL statement because it was not a\n valid Command Line Processor command. During SQL processing it returned:\n SQL1227N The catalog statistic \"\" for column \"HIGH2KEY\" is out of range for\n its target column, has an invalid format, or is inconsistent in relation to\n some other statistic. Reason Code = \"3\". SQLSTATE=23521\n -----","answer":"It is an known limitation of current DB2 V9.7 and above versions' runstats.","is_impossible":false,"contexts":[{"filename":"swg21979066.txt","text":"Title: IBM Runstats may update unexpected HIGH2KEY and LOW2KEY statistic values which may cause SQL1227N - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why is SQL1227N returned when replay db2look output? \n\nCAUSE\nIt is an known limitation of current DB2 V9.7 and above versions' runstats.\n\nANSWER\nIf we run an example scenario below, at the end of script \"db2 -tvf db2_SAMPLE.sql\" \n\ngets SQL1227N.\n--- repro.sh ---\n#!\/bin\/sh\n\ndb2 -v \"drop db sample\"\ndb2 -v \"create db sample\"\ndb2 -v \"connect to sample\"\ndb2 -v \"drop table db2inst1.tab1\"\ndb2 -v \"create table db2inst1.tab1 ( col1 varchar(10) )\"\ndb2 -v \"insert into db2inst1.tab1 values (NULL),(' '),(' '),(' ')\"\ndb2 -v \"runstats on table db2inst1.tab1\"\ndb2 -v \"terminate\"\ndb2 -v \"connect to sample\"\ndb2look -d sample -a -e -m -o db_SAMPLE.sql\n\ndb2 -v terminate\ndb2 -v \"drop db sample\"\ndb2 -v \"create db sample\"\ndb2 -v \"connect to sample\"\ndb2 -tvf db_SAMPLE.sql | tee test.log\n# replay db2look output and gets SQL1227N at this point\ndb2 -v terminate\n----------\n\nHere is the SQL1227N message:\n-----\nUPDATE SYSSTAT.COLUMNS SET COLCARD=4, NUMNULLS=1, SUB_COUNT=-1, SUB_DELIM_LENGTH=-1, \nAVGCOLLENCHAR=7, HIGH2KEY='', LOW2KEY=' ', AVGCOLLEN=12 WHERE COLNAME = 'COL1' \nAND TABNAME = 'TAB1' AND TABSCHEMA = 'DB2INST1'\nDB21034E The command was processed as an SQL statement because it was not a\nvalid Command Line Processor command. During SQL processing it returned:\nSQL1227N The catalog statistic \"\" for column \"HIGH2KEY\" is out of range for\nits target column, has an invalid format, or is inconsistent in relation to\nsome other statistic. Reason Code = \"3\". SQLSTATE=23521\n-----\nAs above, UPDATE SYSSTAT.COLUMNS statement gets SQL1227N at col1 varchar(10).\nIt is caused by runstats, writes an unexpected HIGH2KEY and LOW2KEY statistic values.\n\nHere is work arounds:\n\nWork around #1\n1. $ db2set DB2_STATISTICS=USCC:0\n** this variable is available for V10.1 FP4 and above.\n2. $ db2 terminate\n3. $ db2start\n4. $ repro.sh\n\nWork around #2\n1. Edit SQO1227N causing UPDATE statements' COLCARD=4 to 3 in db_SAMPLE.sql file.\n2. Replay by running \"db2 -tvf db_SAMPLE.sql\" \n\nWork around #3\n1. Do not insert\/import space(s) data, such as \" \", \" \".\n\nNote:\nThis behavior might be changed without notice in the future. We can confirm whether this technote\nis valid or not by following sample scenario 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\/]\n\nRELATED INFORMATION\n RUNSTATS command [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSEPGG_10.5.0\/com.ibm.db2.luw.admin.cmd.doc\/doc\/r0001980.html?lang=en]"}]},{"id":"DEV_Q141","question":"Why is OCR is putting multiple lines on one line?\n\nI am running an APT application, and multiple detail lines are getting put on a single line within my .TXT file. Is there something I can do about this? ","answer":"Add the following action prior to NormalizeCCO. \n\n * \n * \n\nThe first parameter is the percentage of a line that two words must be offset to be considered as separate lines. If the value is not set, the default is 50. In the example, if two words are vertically offset by more than 35% of the height of the words, then they are considered to be on separate lines. Lower values are more likely to split words into separate lines. Higher values are more likely to merge words into a single line.","is_impossible":false,"contexts":[{"filename":"swg21701910.txt","text":"Title: IBM NormalizeCCO merging lines with IBM Datacap Taskmaster Capture - United States\n\nText:\nnormalizecco; merge lines; recognition TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n After running NormalizeCCO, words on separate lines are merged into a single line of text when using IBM Datacap Taskmaster Capture. \n\nSYMPTOM\nIn the following image, Word 1 and Word 2 are on separate lines, but after NormalizeCCO is run may show in a single line as Word Word 1 2. \n\n[\/support\/docview.wss?uid=swg21701910&aid=1]\n\n\nCAUSE\nWhen text is not cleanly printed in lines, such as when the font varies or the text is vertically offset, Datacap may not always be able to locate text when loading field values. The NormalizeCCO goes through the CCO file, and cleans up all the entries so they appear in regular lines. For most images this improves ultimate recognition results, but for some complex images, NormalizeCCO cannot determine where to separate the lines and merges all words into a single line.\n\n\nRESOLVING THE PROBLEM\nAdd the following action prior to NormalizeCCO. \n\n * \n * \n\nThe first parameter is the percentage of a line that two words must be offset to be considered as separate lines. If the value is not set, the default is 50. In the example, if two words are vertically offset by more than 35% of the height of the words, then they are considered to be on separate lines. Lower values are more likely to split words into separate lines. Higher values are more likely to merge words into a single line. \n\n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Not Applicable Windows 9.0.1, 9.0.0"}]},{"id":"DEV_Q142","question":"Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null\n\nWhen using BPM, I see runtime exceptions saying that this SQL error occurs: Invalid operation: result set is closed. ERRORCODE=-4470, SQLSTATE=null\n\nFor example:\n\nCWLLG2015E: An unexpected runtime exception occurred. See exception for more details. Error: Wrapped com.lombardisoftware.core.TeamWorksRuntimeException:","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q143","question":"How can I configure J2EE Tomcat DC to run as Windows Service?\n\nI'm trying to configure ITCAM J2EE v7.1.1 Tomcat DC to run as a Windows Service but it fails. Is this type of configuration supported? If so, what is the right procedure to do that?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q144","question":"CICS CM CCVI abends AEXZ on startup in CCVIINIT\n\nWhy am I receiving an message DFHAC2236 with an abend AEXZ each time that I attempt to startup a newly installed CICS Configuration Manager (CICS CM) server using the CCVI transaction? It looks like it is starting up, but after about 10 seconds it fails with the AEXZ. The last messages I see in the CICS MSGUSR indicate it successfully opened the TCPIPSERVICE:\nDFHSO0107 mm\/dd\/yyyy hh:mm:ss applid TCPIPSERVICE CCVBASIC has been opened on port nnnnn at IP address nnn.nn.nn.nnn.\nDFHDU0203I mm\/dd\/yyyy hh:mm:ss applid A transaction dump was taken for dumpcode: AEXZ, Dumpid: 1\/0001.\nDFHAC2236 mm\/dd\/yyyy hh:mm:ss applid Transaction CCVI abend AEXZ in program CCVIINIT term ????. Updates to local recoverable resources will be backed out.\nCEEMSG shows:\nCEE3250C The system or user abend AEXZ was issued. From compile unit CCVIINIT at entry point CCVIINIT at compile unit offset +0000832E at entry offset 18E8854E.\nIf CCVI is run a few more times, it eventually seems to initialize the server successfully. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q145","question":"Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time?\n\nWhy is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time?","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. Please refer to the\n Recommended Updates page for delivery information:\n http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg27004980","is_impossible":false,"contexts":[{"filename":"swg1PI47826.txt","text":"Title: IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States\n\nText:\n 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"}]},{"id":"DEV_Q146","question":"Gettting error CRIMC1020E: zip im.properties not found during BPM Fix Pack install\n\nDuring the BPM 7.5.1.2 Fix Pack install from the IBM Installation Manager, error window pop up with:\n\nCRIMC1020E: zip im.properties 1.0.0.200911091101 not found ERROR: `zip im.properties 1.0.0.200911091101` not found in [path to sca.1.0.1.17.fp]. CRIMC1020E: zip config.registry 1.0.0.200911092301 not found\n\u2026\u2026\n\nHow can I resolve this error to complete the Fix Pack installation?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q147","question":"TEP to TEPS communication issues with different Java versions\n\nRecent Java updates have caused connection problems when logging into the TEPS via the TEP client (Browser or Java Web Start). Is there an updated list of known issues?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q148","question":"How do I have to prepare WAS and BPM servers, if DST or time zones will change?\n\nDaylight Saving Time (DST) or time zones will change in our country (e.g. 26.10.2014 in Russia).How do I have to prepare the WAS and BPM servers in our environment?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q149","question":"Why SSH connections fail after upgrade to v7.5.2 and above?\n\nWhy SSH connections fail after upgrade to v7.5.2 and above? The same configuration works on v7.2. ","answer":"Disabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices.","is_impossible":false,"contexts":[{"filename":"swg21974106.txt","text":"Title: IBM Late breaking updates to DataPower 7.5 documentation - United States\n\nText:\n NEWS\n\nABSTRACT\n \n\nThe version 7.5 documentation for IBM DataPower Gateway is not the latest available information. This document covers late breaking updates that are not in IBM Knowledge Center.\n\nLast updated, October 2017.\n\n\n\nCONTENT\nThe late breaking updates in this document apply to DataPower Gateway version 7.5 documentation. \n\n\n\n\n\n\n\nTo access specific updates, click the appropriate link: * Upgrade\n * \n * Installation\n * \n * GatewayScript\n * \n * File management\n * \n * Monitors\n\nTo view the change history of this document, see Change history\n\n\nThe corrections in the following sections apply to DataPower Gateway version 7.5 in IBM Knowledge Center.\n\n\n\n\n\n\n\n\n\n\nUpgrade * \n * Disabled diffie-hellman-group-exchange-sha1 and diffie-hellman-group1-sha1 algorithms by default. Disabled MD5-based MAC algorithms. Limited DH-GEX to 4096 bits for Cisco devices. \n * \n * \n * enable-legacy-kex yes\n * \n * The enable-legacy-kex command for the SSH server profile in available in 7.5.2.0. The enable-legacy-kex command for the SSH client profile is available in 7.5.2.7. \n * \n * \n * Default cipher suites * chacha20-poly1305@openssh.com (CHACHA20-POLY1305_AT_OPENSSH.COM)\n * \n * aes128-ctr (AES128-CTR)\n * \n * aes192-ctr (AES192-CTR)\n * \n * aes256-ctr (AES256-CTR)\n * \n * aes128-gcm@openssh.com (AES128-GCM_AT_OPENSSH.COM)\n * \n * aes256-gcm@openssh.com (AES256-GCM_AT_OPENSSH.COM)\n * \n * arcfour256 (ARCFOUR256)\n * \n * arcfour128 (ARCFOUR128)\n * \n * aes128-cbc (AES128-CBC)\n * \n * 3des-cbc (3DES-CBC)\n * \n * blowfish-cbc (BLOWFISH-CBC)\n * \n * cast128-cbc (CAST128-CBC)\n * \n * aes192-cbc (AES192-CBC)\n * \n * aes256-cbc (AES256-CBC)\n * \n * arcfour (ARCFOUR)\n * \n * rijndael-cbc@lysator.liu.se (RIJNDAEL-CBC_AT_LYSATOR.LIU.SE)\n \n Default KEX algorithms * curve25519-sha256@libssh.org\n * \n * ecdh-sha2-nistp256\n * \n * ecdh-sha2-nistp384\n * \n * ecdh-sha2-nistp521\n * \n * diffie-hellman-group-exchange-sha256\n * \n * diffie-hellman-group14-sha1\n \n Default MAC algorithms * umac-64-etm@openssh.com\n * \n * umac-128-etm@openssh.com\n * \n * hmac-sha2-256-etm@openssh.com\n * \n * hmac-sha2-512-etm@openssh.com\n * \n * hmac-sha1-etm@openssh.com\n * \n * umac-64@openssh.com\n * \n * umac-128@openssh.com\n * \n * hmac-sha2-256\n * \n * hmac-sha2-512\n * \n * hmac-sha1\n \n \n * \n * \n * The SSH client always initiates the banner exchange. During the SSH2 banner exchange, use CR+LF termination for the banner. The SSH client ignores any message from the SSH server until the banner exchange. \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nInstallation * \n * show other-sensors\n * \n * show sensors-other\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nGatewayScript * \n * clear gatewayscript-cache path\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nFile management * \n * isamwebroot local policyframework \n\n\nBack to top\n\n\n\n\n\n\n\n\n\n\nMonitors * \n * type\n * \n * block\n * \n * shape\n * \n * type command\n * \n\n\nBack to top\n\n\n\n\n\n\n\n\n\nChange history \nLast modified: 30 October 2017. * 30 October 2017: Added information about nonexisting block keyword for Message Filter Action type command. \n * 19 October 2017: Added information about which directories you can create and remove subdirectories. \n * 19 July 2016: Added data about the wrong command troubleshooting command in the installation documentation. \n * 17 June 2016: Added data about the undocumented Global command. \n * 22 March 2016: Created for 7.5.\n\nBack to top"}]},{"id":"DEV_Q150","question":"Is Java 7 supported for BPM?\n\nWhat versions of BPM, if any, support Java 7?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q151","question":"QUESTION_TITLE\n\nQUESTION","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q152","question":"Why are we no longer able to login to the WAS Administrative Console after adding an Active Directory Server as registry?\n\n\n\nWe have WAS ND 8.5.5.10 in use and have added our Active Directory Server to the Federated Repositories. Via the Administrative Console we used 'root' as base entry for this registry. After restarting the dmgr, we see NameNotFoundExceptions like the following in SystemOut.log:\n\n [12\/22\/16 17:00:24:214 CET] 00000001 exception E com.ibm.ws.wim.adapter.ldap.LdapConnection search(String, String, Object[], SearchControls) CWWIM4520E The 'javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031001E5, problem 2001 (NO_OBJECT), data 0, best match of:\n ''\n \\u0000]; Remaining name: '\/'; Resolved object: 'com.sun.jndi.ldap.LdapCtx@4ca226a8'' naming exception occurred during processing.\n at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3279)\n at com.ibm.ws.wim.adapter.ldap.LdapConnection.checkSearchCache(LdapConnection.java:3122)\n at com.ibm.ws.wim.adapter.ldap.LdapConnection.search(LdapConnection.java:3299)\n at com.ibm.ws.wim.adapter.ldap.LdapConnection.searchEntities(LdapConnection.java:3520)\n at com.ibm.ws.wim.adapter.ldap.LdapAdapter.search(LdapAdapter.java:3524)\n at com.ibm.ws.wim.ProfileManager.searchRepository(ProfileManager.java:5331)\n\nFurthermore, we are no longer able to login to Administrative Console and get displayed the error message Invalid User ID or password.\n\nWhy does this happen and how can we fix this?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q153","question":"Can we create Match design specification db in xmeta\n\nCould you please let me know if we can create schema for Match design\nspecification database in xmeta db.","answer":"You should start from an empty Database; using the default XMETA Database is not recommended because it can become corrupt.","is_impossible":false,"contexts":[{"filename":"swg21409481.txt","text":"Title: IBM Information Server QualityStage Match Designer Database creation - United States\n\nText:\nMD Match Designer Matching Match InformationServer QualityStage TECHNOTE (FAQ)\n\nQUESTION\n How do I configure the Match Designer Database in Information Server? \n\nANSWER\nThis Technote outlines the following procedures. \n\n 1. Prerequisites \n 2. What is the Match Database\u2019s purpose? \n 3. Setting the database up. \n 4. Configuring the Match Designer for use with the Database. \n 5. On going maintenance \n\n\nPrerequisites \nThe following must exist before using the Match Designer functionality. 1. Match Specification built for use in match designer. \n 2. Create a data set that contains the data you will run the match analysis on. \n 3. Create a corresponding frequency data set to be used in the match analysis. \n 4. DSN for local PC \n 5. Create Database in which to perform the Match analysis processing. \n a) Sizing of Database \n b) Character sets required \n c) Permission's for users \n\n\nAdditional information is also available with in the WebSphere QualityStage User Guide. \n\nWhat it\u2019s the Match Database\u2019s purpose? 1. The results Database is used to test the match specifications (logic) designed for use in match jobs. \n 2. This functionality enables the user to get a baseline of how good the match criteria are, based on the match logic developed for use in the application. \n 3. The results Database stores statistics and match results based on your data. For Example: How many matches, duplicates, and unmatched records. \n 4. This functionality allows developers to change matching logic on the fly and retest within minutes. \n\n * There is nothing from this Database that is used in production runs so it should never be created on or moved to a production box. \n * The Match Designer is to be used for development purposes only with a \"subset\" of the full volume data. If additional match modifications are required continue to use a subset of data not conduct testing with full volume data. \n * Determining the subset size of data to use in the Match Designer will vary depending on the clients environment and resources. Each client should run several iterations to determine the optimal subset to utilize in the Match Designer step. \n * To obtain the most accurate matching thresholds a full volume run should be performed in the DataStage Designer.\n\n\nCreating the Database 1. You should start from an empty Database; using the default XMETA Database is not recommended because it can become corrupt. \n 2. There are certain requirements on how the Database is to be created. \n a) If Oracle: CHARACTERSET should be set to AL32UTF \n b) If SQL: default is fine. \n c) If DB2: create as codepage UTF-8 and page size 32K \n d) Permission\u2019s - Each user has to have the ability to create tables, write and read rights in the DB. \n e) The minimum DB space required will be calculated as follows = Number of Passes in match specification (X) Number of Input Records (X) Input Record Length (+) 100 filler.\n f) If this is a distributed installation, you need to have ODBC defined in your client and on the server. They must have the same name. \n\n\nConfiguring the Match Designer for use with the Database 1. Via the DataStage Designer navigate to the your match specification to work with \n 2. Double click and a window will appear indicating: \n \u201cThe ODBC Data Source Name (xxxxxxx) currently specified for this Match could not be found. Please create a DSN by this name or run a Test Environment Update to configure a different DSN for this Specification.\u201d \n 3. Select the \u201cOK\u201d button \n 4. Select option \u201cConfigure Specification\u201d \n 5. From drop down select \u201cTest Environment\u201d \n 6. For \u201cSample Information\u201d navigate to the location of your data set(s) created for analysis. \n 7. Under \u201cFrequency Information\u201d navigate to the location of your frequency data set(s) created for use. \n 8. Section \u201cTest Results Database\u201d fill the following information in. \n a. Select the DSN created for the will allow the connection to the Database. \n b. Enter user name required \n c. Password required \n d. Test Connection \n e. Configuration File Location; these are the nodes located in your environment for use. Please make sure this matches the location of where the data sets reside on the server. \n 9. Once connection is established hit the \u201cUpdate\u201d button. This will populate the Database with the required fields (not data) to populate when you perform the test specification. \n 10. The final step is to perform the Test All Passes. Please note this make take a few moments depending on the size of the files used. \n\n\nOngoing Maintenance 1. For each new run, results are cleared and rewritten to the DB. \n 2. Each user should have their own respective Databases to avoid rewriting over previous results. \n 3. There are separate tables holding results for each design. And from one user it is no problem to use a single Database and multiple designs. \n 4. Per the recommendation above in \"Creating the Database\" this database should not be your XMETA database. If you used the XMETA DO NOT RUN THIS STEP. When you are done testing you can drop the DB altogether."}]},{"id":"DEV_Q154","question":"Why are some Datatypes corrupt after Impact cluster failover\/failback ?\n\n\n\nRunning Impact 7.1.0.11. The symptom is whenever Impact does a failover, a couple DataTypes\nturn out empty.\n\nI've checked the type files before and after Impact failover and the difference happens in the property\n\n*.SQL.USERPARAMETERS\n\nThis property no longer exists for the corrupted datatypes\".\n","answer":"\"a new property is added to increase the file size limit:\n\n\n\n * \n\n\nAdd the property to $NCHOME\/impact\/etc\/<SERVERNAME>_server.props file \nwhere size limit can be 8192, 16384, 32768, etc.. \" \n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact. \n\nThe APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter. \n\nThe character length includes the whole USERPARAMETERS property name as well as the definition.","is_impossible":false,"contexts":[{"filename":"swg21598417.txt","text":"Title: IBM DataType incorrect on Secondary - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; data; type; datatype; .type; replication; cluster; sync; error; 500; mark; invalid TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The DataType is not being correctly replicated across the ImpactServer Cluster \n\nSYMPTOM\nThe .type file of the Secondary ImpactServer configuration is truncated with the error message: \n\n * \n * \n\n\nCAUSE\nAPAR \"IZ81446: IMPACT 511 CLUSTER UNABLE TO REPLICATE DATATYPES WITH USERPARMETERS VALUES IN EXCESS OF 16,000 CHARACTERS.\" [link below] \n\n\n\n\n\nRESOLVING THE PROBLEM\nAdditional comments associated with APAR IZ81446 release notes: \n\n\n\"a new property is added to increase the file size limit:\n\n\n\n * \n\n\nAdd the property to $NCHOME\/impact\/etc\/<SERVERNAME>_server.props file \nwhere size limit can be 8192, 16384, 32768, etc.. \" \n\nThe property would have to be added to all ImpactServers in the Cluster and would require a restart to enable - ensuring that the ImpactServer started as Primary had the correct, uncorrupted .type file to be replicated across the Cluster. Also ensure that there are no trailing white-space characters on the property as these invalidate properties in lower versions of Impact. \n\nThe APAR is not an issue in Impact 6 and 7, but one would still have to include this property with an appropriate value to handle a large character length for the USERPARAMETERS parameter. \n\nThe character length includes the whole USERPARAMETERS property name as well as the definition. \n\nFor example one would add the property: \n\n * \n\n\nto the files: \n\n * \n * \n * \n\n\nwhere one wished to allow the replication of a DataType between two ImpactServers called NCI1 and NCI2 in a Cluster where the USERPARMETERS property line were 20,000 characters long. \nRELATED INFORMATION\n APAR IZ81446 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IZ81446]"}]},{"id":"DEV_Q155","question":"What exactly is \"wpcollector\" in WebSphere Portal Server?\n\nI'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.","is_impossible":false,"contexts":[{"filename":"swg21445430.txt","text":"Title: IBM Automated data collection capability provided by wpcollector tool - United States\n\nText:\nwpcollector isalite isa lite data collection collector diagnostics TECHNOTE (FAQ)\n\nQUESTION\n What are the benefits of the wpcollector tool? How do I use this tool? \n\nANSWER\nWpcollector is a command line tool that automates the collection of portal logs and configuration files. Using automated log collection early in the Case life cycle can greatly reduce the number of doc requests that are made by Support. \n\nWpcollector is delivered with WebSphere Portal beginning with the 7.0 release. If tracing is required for the problem scenario, you must manually enable traceStrings and recreate the problem PRIOR to running wpcollector. \n\nTo run wpcollector, please follow the steps, below:\n\n\n\n * If IBM Support has requested tracing, enable it as instructed by the L2 Support Engineer and then recreate the problem. If no tracing is requested, proceed to the step, below: \n \n\n\n * If using Microsoft Windows, Unix\/Linux, or IBM i, run the following script from the <wp_profile_root> [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/reference\/wpsdirstr.dita]\/PortalServer\/bin\/ directory to begin the collection: * \n * \n * Unix\/Linux: wpcollector.sh \n * i: wpcollector.sh \n * \n * Tip: To specify the option for collecting files for the Deployment Manager profile, use the \"dmgr.root\" parameter. For example: \n * wpcollector.bat -Ddmgr.root=\/opt\/IBM\/WebSphere\/profiles\/dmgr_profile\n \n \n * If using IBM z\/OS, proceed as follows [..\/reference\/wpsdirstr.html%5C]: * \n * \n * In the Portal configuration panel, select Collect Diagnostics. \n * Follow the Customization Dialog instructions for submitting the Collect Diagnostics job (EJPSLOGS). \n * \n * Tip: To collect data from the Deployment Manager, the only requirement is to submit the job from the system where the Deployment Manager is installed (i.e. so it can access the files). There is no prompt in the ISPF panel for this.\n \n \n * Locate the wp.mustgather-<timestamp>.zip file in the <wp_profile_root> [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/reference\/wpsdirstr.dita]\/filesForAutoPD\/ directory and follow the instructions in \"Exchanging information with IBM Technical Support for problem determination\" [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21153852] to manually FTP the collection to IBM. If using z\/OS, there may be additional z\/OS-specific files required, such as WebSphere Portal servant region or controller region joblogs. Wpcollector currently does not collect these files. Your L2 Support Engineer will inform you in the event these files are needed and provide instructions for collecting them. \n \n\n\n * If tracing was requested and enabled, please follow the instructions provided by the L2 Support Engineer to disable tracing from the environment\n\nRELATED INFORMATION\n Data Collection and Symptom Analysis [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/trouble\/tbl_apdt_over.dita?lang=en]"}]},{"id":"DEV_Q156","question":"Help with Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693\n\nWhere 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\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: See 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) ","is_impossible":false,"contexts":[{"filename":"swg21998655.txt","text":"Title: IBM Security Bulletin: Malicious File Download vulnerability in IBM Business Process Manager (BPM) and WebSphere Lombardi Edition (WLE) - CVE-2016-9693 - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n A comma separated file (CSV) download feature exists in IBM BPM and WLE and is available for anonymous users. An attacker can craft a URL that can trigger a download of attacker-supplied content under an attacker-supplied file name onto the victim's machine. \n\nVULNERABILITY DETAILS\nCVEID:CVE-2016-9693 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-9693]\nDESCRIPTION:IBM Business Process Manager has a file download capability that is vulnerable to a set of attacks. Ultimately, an attacker can cause an unauthenticated victim to download a malicious payload. An existing file type restriction can be bypassed so that the payload might be considered executable and cause damage on the victim's machine.\nCVSS Base Score: 7.1\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/119517 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/119517]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:C\/C:L\/I:L\/A:L) \n\nAFFECTED PRODUCTS AND VERSIONS\n- WebSphere Lombardi Edition V7.2.0.0 - V7.2.0.5\n- IBM Business Process Manager Advanced V7.5.0.0 - V7.5.1.2\n- IBM Business Process Manager Advanced V8.0.0.0 - V8.0.1.3\n- IBM Business Process Manager Advanced V8.5.0.0 - V8.5.7.0 including cumulative fix 2016.12\n\nREMEDIATION\/FIXES\nInstall IBM BPM or WLE interim fix JR57149 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1JR57149]as appropriate for your current version. \n\n\n * IBM Business Process Manager Advanced [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Advanced&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Standard [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Standard&release=All&platform=All&function=aparId&apars=JR57149] \n * IBM Business Process Manager Express [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/IBM+Business+Process+Manager+Express&release=All&platform=All&function=aparId&apars=JR57149] \n * WebSphere Lombardi Edition [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&product=ibm\/WebSphere\/WebSphere+Lombardi+Edition&release=All&platform=All&function=aparId&apars=JR57149]\n\n\nAs IBM Business Process Manager V7.5 and WebSphere Lombardi Edition are out of general support, customers with a support extension contract can contact IBM support to request the fix. The fix disables the vulnerable URL and uses HTML5 features to trigger CSV download without server interaction. \n\nFor WebSphere Lombardi Edition 7.2.0.0 through 7.2.0.5 \n\n * Install Fix Pack 5 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034270] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149] \n\nFor IBM BPM V7.5.0.0 through V7.5.1.2: * Upgrade to minimal Refresh Pack 1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24031230], install Fix Pack 2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036462] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.0.0.0 through V8.0.1.3 * Upgrade to minimal Refresh Pack 1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033777], install Fix Pack 3 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037734] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.0.0 through V8.5.0.2 * Install Fix Pack 2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040683] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.5.0 * Apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.6.0 through V8.5.6.0 CF2 * Install CF2 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041303] as required by iFix and then apply iFix JR57149 [https:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\n\nFor IBM BPM V8.5.7.0 through V8.5.7.0 CF 2016.12 * Install CF 2016.12 [https:\/\/www.ibm.com\/support\/docview.wss?uid=swg27048992] and then apply iFix JR57149 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm~WebSphere&function=aparId&apars=JR57149]\n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nIMPORTANT NOTE\n IBM strongly suggests that all System z customers be subscribed to the System z Security Portal to receive the latest critical System z security and integrity service. If you are not subscribed, see the instructions on the System z Security web site [http:\/\/www.ibm.com\/systems\/z\/solutions\/security_subintegrity.html]. Security and integrity APARs and associated fixes will be posted to this portal. IBM suggests reviewing the CVSS scores and applying all security or integrity fixes as soon as possible to minimize any potential risk. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\nACKNOWLEDGEMENT\nThe vulnerability was reported to IBM by Nalla Muthu S and Prasath K \n\nCHANGE HISTORY\n 24 Feb 2017: initial version published \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Express Security Linux, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration IBM Business Process Manager Standard Security AIX, Linux, Solaris, Windows 8.5.7.CF201612, 8.5.7.CF201609, 8.5.7.CF201606, 8.5.7, 8.5.6.2, 8.5.6.1, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5, 8.0.1.3, 8.0.1.2, 8.0.1.1, 8.0.1, 8.0, 7.5.1.2, 7.5.1.1, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Lombardi Edition Security AIX, HP-UX, Linux, Solaris, Windows 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2"}]},{"id":"DEV_Q157","question":"How do I configure TLS\/SSL for an IIB web service provider and consumer?\n\nI'm investigating ways and technologies for use with IIB to run a web service that runs as both a provider and consumer. I'm looking at HTTP and SOAP messages\/nodes. At a high level it might look like this:\nHTTPInput (TLS over HTTPS) -> Compute -> HTTPRequest (SSL over HTTPS) -> Compute -> HTTPReply\nor\nSOAPInput (TLS over HTTPS) -> Compute -> SOAPRequest (SSL over HTTPS) -> Compute -> SOAPReply\nDoes anyone have more details\/references beyond the knowledge center on how to configure the TLS\/SSL portions?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q158","question":"Must the TOKEN_SEPARATOR value be enclosed in quotes for the custom scripting feature?\n\nMust the TOKEN_SEPARATOR value be enclosed in quotes for the custom scripting feature?","answer":"TOKEN_SEPARATOR (Optional - default semicolon \";\"). \nIt sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one.","is_impossible":false,"contexts":[{"filename":"swg21960062.txt","text":"Title: IBM OS Agents Version 6.3.0 FixPack 5 Scripting Feature - United States\n\nText:\n FIX README\n\nABSTRACT\n This feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency. \n\nCONTENT\n(C) Copyright International Business Machines Corporation 2015. All rights reserved.\nComponent: IBM(R) Tivoli(R) Monitoring OS Agents, Version 6.3.0 FixPack 5\n\nDate: 30 June 2015\n\nContents:\n\n1.0 Introduction\n1.1 Quick Start\n2.0 New Attribute groups\n3.0 Parameters in OS agent environment files\n4.0 Parameters in property file\n5.0 Examples of property file\n6.0 Examples of private situations \n7.0 Custom Scripts and Custom Scripts Runtime workspaces\n8.0 Known problems and limitations\n9.0 Troubleshooting\n10.0 Quick Start Scenario\n\n\n1. Introduction\n===============\n\nThis feature allows users to define scripts to run at Tivoli Monitoring OS agents sites at a defined frequency.\n\nThe feature is enabled by default. The administrator can enable\/disable it by setting a new environment variable \nKXX_FCP_SCRIPT=true\/false (default true)in the agent configuration file, where XX can be:\n\n- LZ for Linux OS agent \n- UX for Unix OS agent\n- NT for Windows OS agent\n\nThis is an overview of the scripting feature; details will be provided in the following sections.\n\nThe OS agent loops, at a configurable interval, looking for script definition property files (*.properties) in a configurable directory path.\nThe property files are parsed and OS Monitoring Agent spawns a new process named \u201cfcp_daemon\u201d if at least one valid script definition is found. This new daemon is responsible for scheduling the script executions and gathering all information regarding running scripts.\n\nAccording to another configurable interval, the OS agent loops getting the execution script results from the fcp_daemon.\nThe OS Agent is able to parse the script standard output, splitting each row in up to 16 attributes.\nAn event is sent for each standard output row of the script and these events can be caught by pure event situations.\n\n1.1 Quick Start\n================\nThe feature is enabled with default values as soon as the OS agent is started. The only action to start using the feature is the following:\n- create a property file under default directory (on Linux\/UNIX is $CANDLEHOME\/localconfig\/<product code>\/scripts_definitions, on Windows is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions) using as an example the provided template script_property.txt.\n\nOnly two properties are required:\nATTRIBUTE_NAME=Any name used to uniquely identify the script definition inside the property file.\nSCRIPT_PATH_WITH_PARMS=The fully qualified path of the script with arguments. \n\nNot only shell scripts but also perl and other types of scripts can be used. You just need to specify the full command to execute in the SCRIPT_PATH_WITH_PARMS property. \nFor example, \"perl C:\\IBM\\scripts\\ITM_Custom_Scripts\\date.pl\". In this example you need to make sure that the location of \"perl\" can be resolved by the agent through the PATH variable in its environment. Specify the full path where \"perl\" is installed otherwise.\n\nFurther properties and details can be found in this document and in the template script_property.txt under $CANDLEHOME\/localconfig\/lz\/scripts_definitions. \n\n\n2. New Attribute groups\n=======================\n\nTwo new attribute groups have been added for this feature as detailed below. Statistic and execution data of all the scripts are stored in these two tables. The name of the property file (Property_File) and the attribute name defined in the property file (Attribute_Name) are the 2 key fields of these two tables. These two keys must be used in situation conditions to filter rows related to a specific script.\n\nAttribute group: KXX_Custom_Scripts (multiple rows), table: KXXSCRPTS (sampled).\nDescription: Configuration and statistic data gathered using custom scripts. It contains a row for each defined script, information on the fcp_daemon and on property files:\n\nAttribute Size Description\n=========================== ===== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Name 512 The name of the script.\nScript_Path 512 The fully qualified path name of the script with arguments.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting.\nStandard_Output_Type 4 Standard output type of the script.\nStatus_Code 4 The status of the script. It includes general errors, configuration errors, the status or the execution code returned by the \nScript Provider.\nExecution_Start 16 The time when the last execution of this script started.\nExecution_Duration 4 The duration of the last execution of this script, in seconds. When timing out, the value of the configured timeout is returnd.\nAverage_Execution_Duration 4 The average duration, in seconds, of all the execution of the script.\nRefresh_Interval 4 The interval, in seconds, that the agent attempts to start this script.\nNumber_of_Collections 4 The count of execution attempts of this script since agent started.\nIntervals_Skipped 4 The count of occurrences where an execution of this script is skipped because the previous execution is still running.\nProperty_Group 64 The name of the property group.\nReturn_Code 4 Integer value returned by the Script.\nCust_Label_Str1 16 Label for custom string attribute #1\nCust_Label_Str2 16 Label for custom string attribute #2\nCust_Label_Str3 16 Label for custom string attribute #3\nCust_Label_Str4 16 Label for custom string attribute #4\nCust_Label_Str5 16 Label for custom string attribute #5\nCust_Label_Int1 16 Label for custom integer attribute #1\nCust_Label_Int2 16 Label for custom integer attribute #2\nCust_Label_Int3 16 Label for custom integer attribute #3\nCust_Label_Int4 16 Label for custom integer attribute #4\nCust_Label_Int5 16 Label for custom integer attribute #5\nCust_Label_Float1 16 Label for custom floating point attribute #1\nCust_Label_Float2 16 Label for custom floating point attribute #2\nCust_Label_Float3 16 Label for custom floating point attribute #3\nCust_Label_Float4 16 Label for custom floating point attribute #4\nCust_Label_Float5 16 Label for custom floating point attribute #5\nStandard_Error 2048 Script Standard Error in a unique row\n\nIn addition to script definitions, the table may report rows to return errors found on property files and they are identified by @ANY@ as Attribute_Name. Moreover, a row is always used to report the status of fcp_daemon and it is identified by @ANY@ as Property_File and @ANY@ as Attribute_Name.\n\nAttribute group: KXX_Custom_Scripts_Runtime (multiple rows), table: KXXSCRRTM (pure).\nDescription: Data gathered using custom scripts. It contains the output rows of the scripts currently running:\n\nAttribute Size Description\n======================= ==== =========================\nSystem_Name 32 This is the managed system name of the agent.\nTimestamp 16 This is the local time when the data was collected.\nProperty_File 256 The name of the property file.\nAttribute_Name 96 The attribute name that is defined in the properties file. The attribute is used for metric identification.\nScript_Path 512 The fully qualified path of the script.\nCustom_Name 96 The custom name that is defined in the properties file. It is used for custom reporting. \nReturn_Code 4 Integer value returned by the Script.\nRow_Number 4 Output row number.\nStandard_Output_Type 4 Standard output type of the script.\nStandard_Output_String 2048 Script Standard Output in String Format.\nStandard_Output_Integer 8 Script Output in Integer Format\nStandard_Output_Float 8 Script Output in Floating Point Format (2 decimals).\nCust_Attr_Str1 64 Custom string attribute #1\nCust_Attr_Str2 64 Custom string attribute #2\nCust_Attr_Str3 64 Custom string attribute #3\nCust_Attr_Str4 64 Custom string attribute #4\nCust_Attr_Str5 64 Custom string attribute #5\nCust_Attr_Int1 8 Custom integer attribute #1\nCust_Attr_Int2 8 Custom integer attribute #2\nCust_Attr_Int3 8 Custom integer attribute #3\nCust_Attr_Int4 8 Custom integer attribute #4\nCust_Attr_Int5 8 Custom integer attribute #5\nCust_Attr_Float1 8 Custom floating point (2 decimals) attribute #1\nCust_Attr_Float2 8 Custom floating point (2 decimals) attribute #2\nCust_Attr_Float3 8 Custom floating point (2 decimals) attribute #3\nCust_Attr_Float4 8 Custom floating point (2 decimals) attribute #4\nCust_Attr_Float5 8 Custom floating point (2 decimals) attribute #5\n\nNote: different status conditions can be monitored using the Status_Code field in the statistic table KXX_Custom_Scripts. \nThe following detailed list provides different values for the Status_Code field: \n\nInitial general statuses\nUNKNOWN_ERROR (status code=0) --> Error\nNO_ERROR (status code=1) --> Informational\n\nGeneral daemon statuses\nFEATURE_NOT_ENABLED (status code=40) --> Informational\nDAEMON_STARTING (status code=2) --> Informational\nDAEMON_STARTED (status code=3) --> Informational\nDAEMON_STOPPING (status code=4) --> Informational\nDAEMON_STOPPED (status code=5) --> Informational\nDAEMON_STOPPING_AT_AGENT_STOP (status code=6) --> Informational\nDAEMON_STOPPED_AT_AGENT_STOP (status code=7) --> Informational\nDAEMON_ERROR (status code=8) --> Error\nDAEMON_ERROR_NO_RESTART (status code=9)-> Fatal Error\n\nGeneral directory statuses\nERROR_OPENING_PROP_DIRECTORY (status code=10) --> Error\nPROP_DIRECTORY_NOT_FOUND (status code=11) --> Error\nNO_SCRIPT_DEFINED (status code=12)--> Warning\n\nProperty file statuses\nPROP_FILE_NOT_FOUND (status code=13) --> Error\nERROR_OPENING_PROP_FILE (status code=14) --> Error\n\nScript definition statuses\nSCRIPT_ADDED (status code=15) --> Informational\nSCRIPT_CHANGED (status code=16) --> Informational\nSCRIPT_REMOVED (status code=17) --> Informational\nSCRIPT_INACTIVE (status code=18) --> Informational\nNO_SCRIPT_PATH (status code=21)--> Error\nSCRIPT_PATH_INVALID (status code=22)--> Error\n\nExecution statuses from the fcp_daemon\nFACTORY_UNKNOWN_ERROR (status code=23) --> Error\nFACTORY_NO_ERROR (status code=24)--> Informational\nGENERAL_ERROR (status code=25)--> Error\nOBJECT_NOT_FOUND (status code=26)--> Error\nOBJECT_CURRENTLY_UNAVAILABLE (status code=27)--> Error\nNO_INSTANCES_RETURNED (status code=28)--> Error\nNO_RESPONSE_RECEIVED (status code=29)--> Error\nAUTHENTICATION_FAILED (status code=30)--> Error\nACCESS_DENIED (status code=31)--> Error\nTIMEOUT (status code=32)--> Error\nNOT_IMPLEMENTED (status code=33)--> Error\nRESPONSE_TOO_BIG (status code=34) --> Error\nGENERAL_RESPONSE_ERROR (status code=35)--> Error\nSCRIPT_NONZERO_RETURN (status code=36)--> Error\nSCRIPT_NOT_FOUND (status code=37)--> Error\nSCRIPT_LAUNCH_ERROR (status code=38)--> Error\nINVALID_TOKEN_TYPES(status code=39) --> Error\n\n3. Parameters in OS agent environment files\n===========================================\n\nIt is possible to customize the feature setting parameters in the OS agent environment files:\n- $CANDLEHOME\/config\/lz.ini file for the Linux OS agent\n- $CANDLEHOME\/config\/ux.ini for the UNIX OS agent\n- %CANDLE_HOME%\\TMAITM6_x64\\KNTENV for Windows 64bit OS agent\n- %CANDLE_HOME%\\TMAITM6\\KNTENV for Windows 32bit OS agent\n\nThe scripting feature is enabled by default. To disable it set:\n- KXX_FCP_SCRIPT=false\n\nOther parameters can be defined inside the agent environment files based on specific needs:\n\n- KXX_FCP_SCRIPT_DEFINITIONS (default location on Linux\/UNIX is $CANDLEHOME\/localconfig\/<product code>\/scripts_definitions, on Windows it is %CANDLE_HOME%\\localconfig\\nt\\scripts_definitions)\nThe location where property files are stored.\n\n- KXX_FCP_SCRIPT_INTERVAL (default 60 sec)\nOS agent uses the value of this variable as loop interval in seconds to check execution of running scripts and it sends events if the filter condition is satisfied. The minimum value is 30 seconds, the maximum value is 300 seconds. Invalid values will be reset to the default.\nNote: this parameter is ignored if KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT (see definition below).\n\n- KXX_FCP_SCRIPT_SYNC_INTERVALS (USE_AGENT|USE_SCRIPT|NO - default USE_AGENT)\nIf the agent looping interval defined by KXX_FCP_SCRIPT_INTERVAL is bigger than the script execution frequency, it can happen that data produced by some of the script execution loops is lost.\nTo avoid this behaviour the script execution frequency can be synchronized with the agent looping interval setting the KXX_FCP_SCRIPT_SYNC_INTERVALS to:\n- USE_AGENT; the value of each script execution frequency is forced to be the maximum between KXX_FCP_SCRIPT_INTERVAL and EXECUTION_FREQUENCY defined in its property file. \n- USE_SCRIPT; the agent looping interval is dynamically set to the minimum frequency value (EXECUTION_FREQUENCY in property file) between all of the defined scripts . The value set by KXX_FCP_SCRIPT_INTERVAL is ignored. The frequency of the scripts remain the ones defined in the property files. When using USE_SCRIPT, the agent looping interval may change every time a script definition is added, changed or removed. In any case, it cannot be lower than the value set by KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT or bigger than 300 seconds.\n- NO; no synchronization is performed and some execution results could be lost.\n\n- KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL (default 300 sec) \nAt startup and at every interval defined by this variable, the OS agent checks for any changes in scripts or property files.\nNote that if KXX_FCP_SCRIPT_DEFINITIONS_CHECK_INTERVAL is less than the agent looping interval it will be reset to the agent looping interval. The maximum allowed value is the default, 300 seconds.\n\n- KXX_FCP_USER (default OS agent user)\nThis parameter is valid only on linux and unix platforms. It defines the user used to spawn fcp_deamon process if different from OS agent process user; all the scripts are executed by this user. Note that the user owner of the OS agent must have correct permission to spawn the fcp_daemon process. On windows a different user must be defined as login of the service \"Monitoring Agent for Windows OS - FCProvider\". The user must have \"Full Control\" permission to CANDLE_HOME and scripts repository directories. For more information please refer to official IBM Monitoring documentation: \nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0.2\/com.ibm.itm.doc_6.3fp2\/oswin\/running_as_a_non-admin_user.htm [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSTFXA_6.3.0.2\/com.ibm.itm.doc_6.3fp2\/oswin\/running_as_a_non-admin_user.htm]\n\n- KXX_FCP_MAX_CDP_DP_THREAD_POOL_SIZE (default 10)\nIt defines the maximum concurrent number of scripts to be executed. Maximum value is 32.\n\n- KXX_FCP_MAX_DAEMON_RESTARTS (default 4)\nThe OS agent watches the fcp_daemon: if an abnormal exit of process occurs, the OS agent restarts it. This is done for the KXX_FCP_MAX_DAEMON_RESTARTS (times at a day). \nThe value 0 must be used to avoid the restart; if -1 is set, the OS agent retries to restart fcp_daemon forever. The restart counter is reset at OS agent restart.\n\n- KXX_FCP_SEND_SCRIPT_RUNTIME_EVENTS (default: true)\nIf set to false, the OS agent stops sending events for each row of script standard output. In this case script outputs are visible on TEP console workspaces but no situations will be displayed and no historical collection data will be collected. \n\n- KXX_FCP_OVERRIDE_MIN_FREQUENCY_LIMIT (default: 5 seconds) \nIt is used when KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_SCRIPT. In this condition, it sets the minimum value of the OS agent looping interval.\nUsing low values for the the OS agent looping interval (less than 5 seconds) is highly invasive and can impact OS agent performances. If a frequent data collection is needed (e.g. every second), it is strongly suggested to customize a script that caches data at the needed frequency and returns the collected data to the OS agent at an higher interval (e.g. every 60 seconds).\n\n\nThe following Agent Builder (CDP) variables can also be used to control the behavior of the fcp_daemon:\n\n- CDP_DP_REFRESH_INTERVAL (default 60 sec) Global script scheduled start time. Used if the frequency is not passed in the script property file.\n\n- CDP_DP_SCRIPT_TIMEOUT (default 30 sec) Global script execution maximum time. When the execution time of a script exceeds this limit, its Status_Code is set to TIMEOUT\n\n- CDP_DP_KILL_ORPHAN_SCRIPTS (Y|N - default N) Global behaviour used by fcp_daemon process for timing out scripts. When set to 'Y', the scripts are killed, otherwise they are abandoned. This value is ignored for a specific script if the KILL_AFTER_TIMEOUT key is set in the script property file\n\n- CDP_MAXIMUM_ROW_COUNT_FOR_CPCI_DATA_RESPONSES (default 1000) Global value added for performance reasons to limit the maximum number of output rows returned by the scripts. Additional rows after this limit are ignored. Allowed values are positive integer. Invalid values means no limit.\n\nThe fcp_daemon also supports the other environment variables used to control Agent Builder agents. For a complete list see the official Agent Builder documentation here:\nhttp:\/\/publib.boulder.ibm.com\/infocenter\/tivihelp\/v61r1\/topic\/com.ibm.itm.doc_6.3\/agentbuilder63_user.pdf [http:\/\/publib.boulder.ibm.com\/infocenter\/tivihelp\/v61r1\/topic\/com.ibm.itm.doc_6.3\/agentbuilder63_user.pdf]\n\n4. Parameters in property files \n===============================\n\nThe KXX_FCP_SCRIPT_DEFINITIONS directory contains a list of *.properties files. Each property file contains a list of \nscripts to run with respective properties in the form of key=value. The properties that can be defined (case in-sensitive) are: \n\n- ATTRIBUTE_NAME (Required - string max 256 characters).\nIt is a name of your choice that defines a specific script and its attributes. The characters that can be used for the \nATTRIBUTE NAME name can be alphabetical, numeric and only the underscore can be used as a special character. If other special characters (even a blank is considered this way) are used they get converted into underscore (_).\nWhen multiple scripts are listed inside the same property file, more different ATTRIBUTE_NAME must be defined (one for each script). It must be the first value specified for each defined script and delimits the start of the properties set for the specific script until the next ATTRIBUTE_NAME.\n\n- SCRIPT_PATH_WITH_PARMS (Required - string max 512 characters).\nIt defines the full path to the script with parameters, separated by a blank. No special characters can be used in the script path name. \nValues containing blanks must be enclosed in single (') or double quotes (\").\nEnvironment variables can be passed, but only enclosed in ${...} for all the platforms. Environment variables must be available in the OS agent process context.\n\n- EXECUTION_FREQUENCY (Optional - default 60 sec).\nIt indicates the script execution frequency.\n\n- CUSTOM_NAME (Optional - string max 256 characters)\nThe user can fill it with a description of the script.\n\n- IS_ACTIVE (true|false - Optional - default true). \nIt activates the script. If false, the script is not executed.\n\n- DISABLE_USE_AGENT_SYNC (true|false - Optional - default false). If true, the EXECUTION_FREQUENCY of the script is respected also if the global variable KXX_FCP_SCRIPT_SYNC_INTERVALS is set to USE_AGENT.\n\n- KILL_AFTER_TIMEOUT (true|false - Optional - default value defined by the CDP_DP_KILL_ORPHAN_SCRIPTS variable). \nWhen true the script is killed after timeout (a timeout occurs when script execution is greater than the value specified by CDP_DP_SCRIPT_TIMEOUT parameter in OS agent configuration file) otherwise it is ignored. In both cases no data is collected. Note that when KILL_AFTER_TIMEOUT is set, only the script defined in property file is killed and not child processes (if any) spawned by the script. This feature is not supported by Solaris and Windows 32 bit OS agents and any timing out scripts are abandoned. \n\n\nOutput rows returned by a script are parsed. The script returns a standard output (called hereafter as first token). When the script returns more values in the output row they are added as additional tokens for a maximum of 5 strings, 5 integers and 5 floats following a predefined syntax as described below:\n\n- OUTPUT_TYPE (STRING|INTEGER|FLOAT - Optional - default string). It defines the type of the first token returned by each row of the script;\nOUTPUT_TYPE can be:\n1. STRING (default): strings up to 2048 characters. When used, the \"Standard_Output_String\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n2. INTEGER: allows getting numeric values between -9223372036854775806 and 9223372036854775806. When used, the \"Standard_Output_Integer\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n3. FLOAT: allows getting numeric values between -92233720368547758.06 and 92233720368547758.06,(with 2 decimal\nprecision). When used, the \"Standard_Output_Float\" attribute of KXX_Custom_Scripts_Runtime is filled in by the first token.\n\n- TOKEN_TYPES (STRING|INTEGER|FLOAT - Optional).\nIt defines the output type of additional tokens after the first one. The user can define a maximum of 5 strings, 5 integers and 5 floats. It is a list of types separated by commas:\n<token_type>,<token_type>,\u2026\ntoken_type can be empty or one from (case insensitive):\n- STRING or S\n- INTEGER or I\n- FLOAT or F\nIf <token_type> is empty, the corresponding token is skipped.\nExamples of the same valid layouts:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_TYPES=String,integer,S,,,Float,,f,FLOAT\n\n- TOKEN_LABELS (STRING - maximum 16 characters each label - Optional). \nIt defines the labels of the tokens defined in TOKEN_TYPES. This value is a list of token labels separated\nby commas, and must correspond to the tokens defined by TOKEN_TYPES. \ne.g.:\n- TOKEN_TYPES=S,I,S,,,F,,F,F\n- TOKEN_LABELS=Cpu Name,Cpu number,Description,,,value 1,,value 2,value 3 \nIt is ignored if TOKEN_TYPES is not set.\n\n- TOKEN_SEPARATOR (Optional - default semicolon \";\"). \nIt sets the string to be used as separator to split the output row in tokens. It is ignored if TOKEN_TYPES is not set. Empty value (blank) is accepted as separator and multiple consecutive blanks in output rows are considered as a single one.\n\n\nThe following two parameters allow you to filter the rows output of a script; they are applied by the OS agent only to the first token and they must be used together:\n\n- FILTER_VALUE (Optional).\nThe value used for comparison. It is required if FILTER_OPERATOR is defined.\nIf the OUTPUT_TYPE is a string, the filter value must reflect exactly the string value returned by the script that is intended to be filtered, without any additional quotes (no wildcards allowed).\n- FILTER_OPERATOR (Optional).\nThe operator used for the comparison. It is required if FILTER_VALUE is defined. Accepted FILTER_OPERATOR values include:\n= (equal to)\n!= (different from)\n> (bigger than) only for numeric type\n>= (not lower than) only for numeric type\n< (lower than) only for numeric type\n<= (not bigger than) only for numeric type\n\n\n\n5. Examples of property file\n============================\n\n#First script definition: script ex_script1.sh is launched every 150 seconds, it returns float values and only the output rows equal to 0.5 will be considered by the agent.\n\nATTRIBUTE_NAME=sample1 \nSCRIPT_PATH_WITH_PARMS=\/opt\/ibm\/itmd4255a\/localconfig\/lz\/scripts_definitions\/ex_script1.sh\nEXECUTION_FREQUENCY=150\nOUTPUT_TYPE=FLOAT\nFILTER_VALUE=0.5\nFILTER_OPERATOR==\n\n#Second script definition: script ex_script2 is launched every 60 seconds, it returns integer values and only the rows different from 0 will be considered by the agent.\n\nATTRIBUTE_NAME=ex_script2\nSCRIPT_PATH_WITH_PARMS=${CANDLE_HOME}\/tmp\/check_out.sh\nEXECUTION_FREQUENCY=60\nOUTPUT_TYPE=INTEGER\nFILTER_VALUE=0\nFILTER_OPERATOR=!=\n\n#Third script definition: script ex_script3.sh is launched every 120 seconds with 3 input parameters (the first input parameter is an integer, the second and third are string). It's killed if it hangs or if the execution time is greater than the timeout value.\n\nATTRIBUTE_NAME=ex_script3 \nSCRIPT_PATH_WITH_PARMS=\/opt\/scripts\/ex_script3.sh 1 \"second input parameter\" \"third input parameter\" \nEXECUTION_FREQUENCY=120\nOUTPUT_TYPE=STRING\nKILL_AFTER_TIMEOUT=TRUE\n\n#Fourth script definition: script cpu_mem_percentage.sh is launched every 50 seconds and returns the cpuid as standard output string and 2 float for Idle and Used CPU percentage and 2 integers for Memory and Virtual Memory usage. The pipe is used as separator to parse the output. An example of row that must be returned by the script is: \ncpu2|35,5|65,5|3443|123800\n\nATTRIBUTE_NAME=cpu and mem Usage\nSCRIPT_PATH_WITH_PARMS=${SCRIPT_HOME}\/cpu_mem_percentage.sh\nOUTPUT_TYPE=STRING\nTOKEN_TYPES=F,F,I,I\nTOKEN_LABELS= Idle CPU %, Used CPU %, Virt MEM used MB, MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=50\n\n6. Examples of private situations \n==================================\n\nThe private situations definitions can be inserted into the xx_situations.xml under $CANDLEHOME\/localconfig\/lz for linux or $CANDLEHOME\/localconfig\/ux for unix or %CANDLE_HOME%\\localconfig\\nt for Windows to monitor scripts execution.\nExamples below are for the Linux OS agent:\n\n<PRIVATESIT>\n<!-- Sends an alert if the script defined by attribute name \"demo\" in property file \"demo.properties\" returns a row equal to \"demo.log\" -->\n<SITUATION>FCP_CheckLOGFileExists_pr<\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts_Runtime.Property_File *EQ 'demo.properties' *AND *VALUE KLZ_Custom_Scripts_Runtime.Attribute_Name *EQ 'demo' *AND *VALUE KLZ_Custom_Scripts_Runtime.Standard_Output_String *EQ 'demo.log']]>\n<\/CRITERIA>\n<\/PRIVATESIT>\n\n<PRIVATESIT>\n<!-- Sends an alert if a script exits with a return code different from zero -->\n<SITUATION>FCP_ScriptRetCode_pr<\/SITUATION>\n<CRITERIA>\n<![CDATA[*IF *VALUE KLZ_Custom_Scripts.Return_Code *NE 0]]>\n<\/CRITERIA>\n<\/PRIVATESIT>\n\n<privatesit>\n<!-- Sends an alert when script path is not defined in a property file -->\n<SITUATION NAME=\"FCP_NOPTAH\" INTERVAL=\"000030\" ><\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ NO_SCRIPT_PATH]]>\n<\/criteria>\n<\/privatesit>\n\n<privatesit>\n<!-- Sends an alert when a script cannot be launched -->\n<SITUATION NAME=\"FCP_ScriptLaunchErr\" INTERVAL=\"000060\" ><\/SITUATION>\n<criteria>\n<![CDATA[*VALUE KLZ_Custom_Scripts.Status_Code *EQ SCRIPT_LAUNCH_ERROR]]>\n<\/criteria>\n<\/privatesit>\n\n\n7. Custom Scripts and Custom Scripts Runtime Workspaces\n=======================================================\n\nA new OS agent navigation item has been added in the TEP console. It contains two workspaces: \"Custom Scripts\" and \"Custom Scripts Runtime\". \n\n\"Custom Scripts\" workspace contains the following views:\n- \"Factory Daemon Status\" table view showing informational\/warning\/error events related to the fcp_daemon process.\n- \"Properties Files error\" table view showing problems related to property files.\n- \"Number of execution per script\" bar chart view summarizing the executions of defined scripts\n- \"Defined Scripts\" table view showing detailed information of defined scripts.\n\n\"Custom Scripts Runtime\" workspace is called clicking on the anchor of a specific script and provides information on script execution. The views provided by default on the TEP console are to be intended as example workspaces with all available custom attributes. Users can duplicate and customize workspaces to filter out fields that are not needed according to the output returned by their scripts.\n\n\n8. Known problems and limitations\n===================================\n\n- The Scripting Feature is not supported on Windows 2003 64-bit systems.\n- Kill after timeout does not work on Solaris and Windows 32 bit OS agents.\n- The fcp_daemon may stop executing scripts in Windows 32 bit If some scripts do not complete within the time out period and the user has turned on intensive tracing. If this happens the data reported on the TEP will reflect the last time the script was actually run. It is also possible that the OS agent will stop returning data. Terminating the fcp_daemon process will allow the agent to resume proper operation.\n- SCRIPT_NONZERO_RETURN is returned instead of SCRIPT_NOT_FOUND or SCRIPT_LAUNCH_ERROR on Solaris.\n- The scripting feature does not provide full Native Language Support; some issues may be found using Nationalized characters in property files or script outputs.\n- On windows OS agent there is no possibility of executing scripts residing on a mapped network drive.\n\n9. Troubleshooting\n===================\n\nStandard KBB_RAS1 variable will apply to the OS agent and to the fcp_daemon processes.\nTo apply a specific trace setting to fcp_daemon only, use the KXX_FCP_KBB_RAS1 variable; when KXX_FCP_KBB_RAS1 is set, the value specified by KBB_RAS1 is ignored by fcp_daemon.\n\nTo trace the operations logged by the OS agent core threads of the feature:\nKBB_RAS1=ERROR (UNIT:factory ALL)\n\nTo trace scripting queries from the ITM server and events sent to the server, add the entries:\n(UNIT:klz34 ALL) (UNIT:klz35 ALL) on Linux OS agent\n(UNIT:kux48 ALL) (UNIT:kux49 ALL) on Unix OS agent\n(UNIT:knt84 ALL) (UNIT:knt85 ALL) on Windows OS agent\n\nTo view tema traces to verify private situation execution, add the entries:\n(UNIT:kraavp all) (UNIT:kraapv all)\n\nTo see the execution of the scripts and how the data from the scripts is being parsed set:\nKXX_FCP_KBB_RAS1=Error (UNIT:command ALL)\n\nTo troubleshoot problems in the communication between the os agent and fcp_daemon add this trace level to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket FLOW) (UNIT:cpci FLOW)\n\nTo see the interaction between the OS agent process and the fcp_daemon in detail add to both KBB_RAS1 and KXX_FCP_KBB_RAS1:\n(UNIT:cps_socket ALL) (UNIT:cpci ALL)\n\n\n10. Quick Start Scenario\n=========================\n\nThe following section describes the minimum steps needed to configure a linux OS agent to run 2 custom scripts.\n\nCustom Scripts descriptions\n===========================\nLet's suppose the user has 2 scripts under a directory \/scripts_repo:\n\n- checkDIRsize.sh that checks the size of a specified directory passed as input parameter. Its output is an integer like the following: \n\n4594740\n\n- cpu_mem_usage.sh that checks the used CPU percentages and used Swap Memory megabytes. Its output is returned in the following form:\n\ncpu1|96,5|23800\n\nwhere the first token is the CPU id, the second token is the used CPU percentage, the third token is the used swap memory in megabyte.\n\nCustomization needed to have the linux OS agent run above scripts\n==============================================================\nThe feature is enabled with default values as soon as the OS agent is started:\n\n- you could create one or two property files (<Any Name>.properties)under the default directory $CANDLEHOME\/localconfig\/lz\/scripts_definitions. In this example let's create 2 property files one for each script called checkDIRsize.properties and cpu_mem_usage.properties:\n\n#CheckDIRsize.properties\nATTRIBUTE_NAME=OPT_DIR_SIZE\nSCRIPT_PATH_WITH_PARMS=\/scripts_repo\/checkDIRsize.sh \/opt\nEXECUTION_FREQUENCY=20\nOUTPUT_TYPE=INTEGER\n\n#cpu_mem_usage.properties \nATTRIBUTE_NAME=cpu_mem_usage\nSCRIPT_PATH_WITH_PARMS=\/scripts_repo\/cpu_mem_percentage.sh\nOUTPUT_TYPE=string\nTOKEN_TYPES=F,I\nTOKEN_LABELS= Used CPU %, Swap MEM used MB\nTOKEN_SEPARATOR=|\nEXECUTION_FREQUENCY=10\n\n- There is no need to restart the OS agent after adding (or changing) the 2 property files above: the OS agent checks script definition directory with a specified time interval (default value 300 seconds). Open the TEP console and under the \"Custom Scripts\" workspace the scripts details and results are shown.\n\nChange History:\n----------------------\n2017-01-09: Added new item under \"8. Known problems and limitations\" that the Scripting Feature is not supported on Windows 2003 64-bit systems."}]},{"id":"DEV_Q159","question":"Help with Security Bulletin: IIB is affected by WebAdmin Session Timeout vulnerability (CVE-2017-1693)\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by WebAdmin Session Timeout vulnerability (CVE-2017-1693). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q160","question":"How to increase the HTTP Session time-out value for Workplace application on WebSphere Application Server?\n\nWe 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","is_impossible":false,"contexts":[{"filename":"swg21163875.txt","text":"Title: IBM HTTP Session time-out settings and overwrite precedence rules - United States\n\nText:\nWebSphere 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\u00ae WebSphere\u00ae 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 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-config> \n * \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<session-timeout>60<\/session-timeout>\n * \n * \u00a0 \u00a0 \u00a0 <\/session-config>\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"}]},{"id":"DEV_Q161","question":"Netcool\/Impact 7.1.0: The StateChange value being used by the OMNIbusEventReader is too high\n\n The value being used is a date and time in the future and as such is preventing the EventReader from capturing the current events. ","answer":"The simplest solution is to manually reset the EventReader StateChange value via the GUI. Stop the EventReader, open it for edit, click the \"Clear State\" button, exit the editor and restart the EventReader.","is_impossible":false,"contexts":[{"filename":"swg21610844.txt","text":"Title: IBM EventReader stops reading events, StateChange value too high - United States\n\nText:\nnetcool; impact; netcool\/impact; nci; event; reader; eventreader; omnibus; omni; omnibuseventreader; state; change; statechange; date; time; datetime; value; future; high; stamp; timestamp; advanced; advance; forward; ahead; before; after; current; jrexec; jrexecaction; jrexecserver; jrexecaction()' server; action; function; command; line; interface; cli; commandlineinterface TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n How to deal with an EventReader that is using an inadvertently future dated StateChange value. \n\nSYMPTOM\nThe EventReader stops acquiring events that are pertinent for processing because it is using a StateChange value that is too high.\n\n\nCAUSE\nAn event has had its StateChange value artificially increased by some unknown component (Probe, Trigger, etc) to reflect a future date. The EventReader captures the event and then uses the highest captured StateChange value in its outgoing SQL to capture pertinent events.\n\nDIAGNOSING THE PROBLEM\nPertinent events are not being processed. Looking in the EventReader log file the number of events being captured in each Read is 0. Testing the SQL being used in an nco_sql session produces a 0 result too. Testing the SQL again in an nco_sql session without the \"and StateChange >= 1234567890\" clause returns all the unprocessed rows.\n\nRESOLVING THE PROBLEM\nSomething has \"future dated\" the StateChange value of an event in the ObjectServer, the EventReader captured the event and, since the EventReader will use the highest StateChange value captured in the previous poll in the SQL of its next poll, this then future dated the value used in the EventReader. The EventReader will persist with this value (and will increment it by 1 every other poll) until such a time as it captures an event with a higher StateChange value.\n\n\n\n\n\nThe simplest solution is to manually reset the EventReader StateChange value via the GUI. Stop the EventReader, open it for edit, click the \"Clear State\" button, exit the editor and restart the EventReader.\n\nAn alternate solution is to perform this operation via the Command Line Interface:\n\n\n\n * telnet [Hostname] [Port]\n\n\nwhere [Hostname] is the resolvable hostname of the ImpactServer host and [Port] is the CLI port number (2000, by default). You will need to supply a suitable username (admin, for example) and password. Then at the READY prompt enter the series of commands: \n\n * Update Service set Running=false where Name='[EventReaderName]';\n * \n * Update Service set ClearState=true where Name='[EventReaderName]';\n * \n * Update Service set Running=true where Name='[EventReaderName]';\n\n\nwhere [EventReaderName] is the name of the EventReader that requires this restart process. \n\nIn cases where the likelihood of StateChange being inappropriately incremented in this fashion is quite high, one might wish to automate this process and have a Policy hunt for such occurrences. Please find following an example of a \"hunter\" Policy to capture any reoccurrence of this issue: \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 * ANN=\"AcquireStateChange\"; \n Log(2,ID+ANN); \n Script=\"\/opt\/IBM\/netcool\/impact\/bin\/CheckState.sh\"; \n Parameter=\"password\"; \n JRExecAction(Script, Parameter, false, 30); \n NumExecOutput=Length(ExecOutput); \n Log(3,ID+ANN+\": NumExecOutput: \"+NumExecOutput); \n \n If(NumExecOutput >= 1) \n { * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * Log(ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is greater than CurrentTime: \"+HumanCurrentTime); \n Log(ID+ANN+\": !!! Clearing EventReader State !!!\"); \n Script=\"\/opt\/IBM\/netcool\/impact\/bin\/ClearState.sh\"; \n Parameter=\"password\"; \n JRExecAction(Script, Parameter, false, 30); \n * \n * \n * \n * \n * \n * Log(1,ID+ANN+\": CurrentStateChange: \"+HumanStateChange+\" is less than CurrentTime: \"+HumanCurrentTime); \n * \n * \n * \n * \n * \n * Log(ID+ANN+\": !!! There is some freaky stuff happening here !!! - CurrentStateChange: \"+HumanStateChange+\" and CurrentTime: \"+HumanCurrentTime+\" !!! \"); \n * \n \n } \n Else \n { * \n \n } \n * \n * \n * \n * \n * \n * Log(3,ID+ANN+\": No UnprocessedEvents\"); \n * \n * \n * \n * \n * \n * \n\n\nAs you can see this is designed to be run by a PolicyActivator and checks for events that have been around in the ObjectServer for a while (a minute) and are pertinent for processing by Impact (ImpactFlag = 1), but have not. If it finds any it then acquires the StateChange value from the .state file via JRExecServer using the example script referred to in the above example Policy as CheckState.sh: \n\n * \n * \n * \n * \n * \n * \n * \n\n\nIf the Policy finds the string it extracts the StateChange value and compares it against the current time and, if StateChange exceeds the current time, it undertakes the stop, clear and restart of the EventReader to bring StateChange back into line. \n\nThis examples a simple script to use the Command Line Interface to stop the EventReader, clear the StateChange value and restart the EventReader and is referred to in the above exampled Policy as ClearState.sh: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nPlease note that the ClearState.sh script should not contain any spaces or special characters otherwise calling EOF will throw errors. Also, in latter versions of Impact, the username and password should be those of the tipadmin. Additionally, rather than have the password sitting clear case in a script one can pass it as a JRExecAction Parameter from the Policy - still clear case but the relevance of the variable can be made less obvious. \n\nBoth of these scripts are called by the JRExecAction() function in the example Policy and this in turn requires the JRExecServer to be running on the ImpactServer host(s *). \n\n* - The JRExecServer will be used by the current Primary ImpactServer only, as all EventReaders and PolicyActivators are run on the current Primary only but, if and when failover occurs and the Secondary ImpactServer becomes Primary, this new Primary will require access to a running, local JRExecServer. So, JRExecServer has to be running on both Primary and Secondary ImpactServer hosts to ensure availability in case of failover. Some additional information about the JRExecAction() function is available from the TechNote \"JRExecAction() function usage\" [Link Below] \nRELATED INFORMATION\n JRExecAction() function usage [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21515756]"}]},{"id":"DEV_Q162","question":"Is there a security vulnerability in the IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager?\n\nIs there a security vulnerability in the IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager?","answer":"Please consult the security bulletin Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2015-7450) [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21970575] for vulnerability details and information about fixes.","is_impossible":false,"contexts":[{"filename":"swg21972146.txt","text":"Title: IBM Security Bulletin: A security vulnerability has been identified in IBM WebSphere Application Server shipped with IBM Tivoli Netcool Configuration Manager (CVE-2015-7450) - United States\n\nText:\nITNCM; Security Bulletin; CVE-2015-7450; websphere SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere Application Server is shipped as a component of IBM Tivoli Netcool Configuration Manager. Information about a security vulnerability affecting IBM WebSphere Application Server has been published in a security bulletin. \n\nVULNERABILITY DETAILS\nPlease consult the security bulletin Vulnerability in Apache Commons affects IBM WebSphere Application Server (CVE-2015-7450) [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21970575] for vulnerability details and information about fixes.\nCVEID: CVE-2015-7450 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-7450]\nDESCRIPTION: Apache Commons Collections could allow a remote attacker to execute arbitrary code on the system, caused by the deserialization of data with Java InvokerTransformer class. By sending specially crafted data, an attacker could exploit this vulnerability to execute arbitrary Java code on the system.\nCVSS Base Score: 9.8\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/107918 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/107918] 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\n \n\nPrincipal Product and Version(s) Affected Supporting Product and Version ITNCM version 6.4.1.3\nITNCM version 6.3.0.6 Embedded IBM WebSphere Application Server eWAS 7.0 REMEDIATION\/FIXES\n \n\n<Product VRMF APAR Remediation\/First Fix ITNCM 6.4.1.3 IF001 none http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=ibm~Tivoli&product=ibm\/Tivoli\/Tivoli+Netcool+Configuration+Manager&release=6.4.1.3&platform=All&function=fixId&fixids=ITNCM_6.4.1.3_IF001&includeRequisites=1&includeSupersedes=0&downloadMethod=http [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=ibm~Tivoli&product=ibm\/Tivoli\/Tivoli+Netcool+Configuration+Manager&release=6.4.1.3&platform=All&function=fixId&fixids=ITNCM_6.4.1.3_IF001&includeRequisites=1&includeSupersedes=0&downloadMethod=http] ITNCM 6.3.0.6 IF004 none http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7ETivoli&product=ibm\/Tivoli\/Tivoli+Netcool+Configuration+Manager&release=6.3.0.6&platform=All&function=all [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7ETivoli&product=ibm\/Tivoli\/Tivoli+Netcool+Configuration+Manager&release=6.3.0.6&platform=All&function=all] \nFor ITNCM 6.2.x IBM recommends upgrading to a fixed, supported version\/release\/platform of the product. \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] *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."}]},{"id":"DEV_Q163","question":"How to fix XAER_RMFAIL messages in WebSphere Portal's SystemOut.log?\n\nSystemOut.log contains various exceptions with caused by statements like:\nCaused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL\nError: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.14.88 \nand: \nCaused by: com.ibm.db2.jcc.am.SqlException: [jcc][t4][2041][11392] [4.14.88] Error executing XAResource.commit(). Server returned XAER_RMFAIL. ERRORCODE=-4203, SQLSTATE=null ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q164","question":"When should I use conversation sharing in DataPower MQ queue managers?\n\nMQ version 7.0 introduced a new feature, conversation sharing. Are there any special values on DataPower when configuring conversation sharing?","answer":"The default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is \nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.","is_impossible":false,"contexts":[{"filename":"swg21647231.txt","text":"Title: IBM When to enable Conversation Sharing in DataPower MQ Queue Manager (mq-qm) object - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When to enable Sharing Conversations in DataPower MQ Queue Manager (mq-qm) object along with SHARECNV attribute of the MQ SVRCONN channel? \n\nRESOLVING THE PROBLEM\nIBM WebSphere MQ server version 7.0 and later releases provide sharing conversations (SHARECNV) attribute on SVRCONN channel that specifies the maximum number of conversations that can share each TCP\/IP channel instance. This feature can be configured in DataPower as it uses client connection with queue manager SVRCONN channel. \nThe default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is \nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.\n\nThere are three use cases to configure Sharing Conversations in DataPower mq-qm object: \n\nCase #1 : The negotiated sharing conversations value is 0 - The channel runs in a mode similar to WebSphere MQ V6 and does not uses features such as\n\n\u00b7 Administrator stop-quiesce\n\u00b7 Heartbeating \n\u00b7 Read ahead \n\u00b7 Client asynchronous consume\n\nSet a value of 0 or 1 on the Sharing Conversations attribute of the mq-qm object in DataPower to disable sharing conversations regardless of the IBM WebSphere MQ SVRCONN setting.\n\nCase #2: The negotiated sharing conversations value is 1 - The channel supports IBM WebSphere MQ V7 and later release features as outlined in case #1, but each TCP\/IP channel instance has a single conversation.\n\nSet a value of 1 on the Sharing Conversations attribute and select \"on\" in Share Single Conversation attribute of the mq-qm object in DataPower as shown in the following picture and a value of 1 on IBM WebSphere MQ SVRCONN setting.\n\nThe Share Single Conversation attribute is only visible when \"Sharing Conversations\" is configured with value of \"1\" and then <RETURN> key is entered. For values greater than 1, the \"Share Single Conversation\" attribute is hidden in the mq-qm object.\n[\/support\/docview.wss?uid=swg21647231&aid=1] [\/support\/docview.wss?uid=swg21647231&aid=1] \n\nCase #3: The negotiated sharing conversations value is 2 or more - The channel supports IBM WebSphere MQ 7 and later release features and each TCP\/IP channel instance supports 2 or more conversations.\n\nSet a value of 2 or more on the Sharing Conversations attribute of the mq-qm object in DataPower and on the MQ SVRCONN channel.\n\nOn average, processing of messages from client applications is 15 percent slower when using SHARECNV(10) as compared to SHARECNV(0). Please refer to Performance Implications of Sharing [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.csqzaf.doc\/mi12240_.htm]\nConversations on Client-connection Channels. [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.csqzaf.doc\/mi12240_.htm].\n\nSince DataPower uses a connection pool in processing MQ messages, there are no additional benefits of using sharing conversations with the mq-qm object. However, in situations when mixed message sizes are used by the same mq-qm object, using case #2 will benefit mq-qm object as it will use new buffer management feature of IBM WebSphere MQ Version 7 when making MQGET API call.\n\nWhen using a negotiated shared conversations value of 0 as in case #1, mq-qm object uses maximum message size as the buffer pool for the MQGET API call. However, when mixed message sizes are processed by the same MQ Front Side Handler (FSH), it requests buffer pool based on maximum message size configured in the mq-qm object. The use of fixed buffer pool for small and large messages can deplete MQ server's allocated buffer and contribute to unexpected termination of MQ SVRCONN channel instance and may terminate the queue manager. In such a situation, using a negotiated sharing conversations value of 1 as in case #2 will benefit DataPower mq-qm object as it will use IBM WebSphere MQ Version 7 Read Ahead feature and the new buffer management feature for MQGET API call. IBM WebSphere MQ V8 release provides enhanced performance for case #2, when the negotiated sharing conversations value is 1.\n\nFor DataPower firmware releases 7.0.0.x, 7.1.0.x, 7.2.0.x and earlier, one should follow case #1 and use a negotiated sharing conversations value of 0. If you configure these firmware versions with case #2 or case #3, DataPower device may reload or hang due to connection instability and generate many MQ errors with Reason Code - 2009 and 2059. \n\nCases #2 and #3 can be used in firmware releases 7.5.0.x, 7.5.1.x and later. We suggest to use a value of 10 or less in Sharing Conversations attribute of the mq-qm object and verify the configuration empirically to make sure that IBM WebSphere MQ server can sustain load from DataPower with the negotiated Sharing Conversations of 10.\n\nNote: In order to use sharing conversations, make sure you have applied APAR IV24821 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IV24821] (\"Client C application process hangs after cancelling thread\") to the IBM WebSphere MQ server. IV24821 is included in IBM WebSphere MQ V7.0.1.10 and later, IBM WebSphere MQ V7.1.0.3 and later, IBM WebSphere MQ V7.5.0.1 and later, and IBM WebSphere MQ V8.\n\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the distributed platform.\n\nrunmqsc <qmgr>\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n1 : display chs(CHANNEL3) maxshcnv curshcnv\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.x1.x2.x3) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(1) MAXSHCNV(1) <---- Negotiated Sharing Conversations value of 1\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.y1.y2.y31) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(0) MAXSHCNV(0) <---- Negotiated Sharing Conversations value of 0\n\nend\n--------------------------------------------------------------------------------------------------------------------------------------------\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the z\/OS System.\n\n\n\nconnect to <qmgr>\nOn z\/OS system, options for issuing the commands are described at http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.ref.adm.doc\/q085120_.htm [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.ref.adm.doc\/q085120_.htm]. \n\/+RTP8 DIS CHSTATUS(channel_name) MAXSHCNV CURSHCNV\nwhere \"+RTP8\" is the command prefix."}]},{"id":"DEV_Q165","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. \nHere are the messages I receive:\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","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q166","question":"Which version of the WebSphere MQ Resource Adapter is shipped with WebSphere Application Server?\n\nWhich version of WebSphere MQ JCA resource adapter is shipped with WebSphere Application Server ? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q167","question":"How do I recreate all the Oracle Text indexes for the Atlas database\n\nHow do I recreate all the Oracle Text indexes for the Atlas database ? ","answer":"Shutdown the application server running the Atlas applications. \n 2. Locate the script drop_ctxsys_indexes.sql to drop the Oracle Text indexes from the following folder in the Atlas release:\n Atlas\\Schema\\Deploy\\smf\\db\\etc\\oracle \n 3. Open up a command window to that directory and execute the script using SQL Plus:\n sqlplus <user>\/<password>@<database> @drop_ctxsys_indexes.sql \n 4. Locate the scripts, setup_ctxsys_objects.sql and create_ctxsys_indexes.sql, used to create the Oracle Text preferences and indexes from the following folder in the Atlas release. The <version> folder will differ depending on which version you are currently running.\n Atlas\\Schema\\Deploy\\smf\\db\\release\\<version>\\oracle\\create\\schema \n 5. Open up a command window to that directory and execute the scripts using SQL Plus.\n sqlplus <user>\/<password>@<database> @setup_ctxsys_objects.sql\n sqlplus <user>\/<password>@<database> @create_ctxsys_indexes.sql \n 6. Start the application server running the Atlas applications.","is_impossible":false,"contexts":[{"filename":"swg21580830.txt","text":"Title: IBM Recreate all the Oracle Text indexes - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I recreate all the Oracle Text indexes for the Atlas database \n\nANSWER\nThere are situations where the Oracle Text indexes used by the application may need to be recreated. For example, after importing data from a production database to a test database, the Oracle Text indexes will not be transferred. This will require you to recreate them in order for certain functions in Atlas to work properly. \n\nIf you have access to the Atlas release files from the version you are currently using you can follow these instructions. You will need the ability to access the Atlas database using the Oracle SQL Plus tool. \n\n \n\n 1. Shutdown the application server running the Atlas applications. \n 2. Locate the script drop_ctxsys_indexes.sql to drop the Oracle Text indexes from the following folder in the Atlas release:\n Atlas\\Schema\\Deploy\\smf\\db\\etc\\oracle \n 3. Open up a command window to that directory and execute the script using SQL Plus:\n sqlplus <user>\/<password>@<database> @drop_ctxsys_indexes.sql \n 4. Locate the scripts, setup_ctxsys_objects.sql and create_ctxsys_indexes.sql, used to create the Oracle Text preferences and indexes from the following folder in the Atlas release. The <version> folder will differ depending on which version you are currently running.\n Atlas\\Schema\\Deploy\\smf\\db\\release\\<version>\\oracle\\create\\schema \n 5. Open up a command window to that directory and execute the scripts using SQL Plus.\n sqlplus <user>\/<password>@<database> @setup_ctxsys_objects.sql\n sqlplus <user>\/<password>@<database> @create_ctxsys_indexes.sql \n 6. Start the application server running the Atlas applications.\n\n[attachment \"recreate_oracle_text_3.0.2.x.zip\" deleted by Nicholas Tsang\/San Jose\/IBM] [attachment \"recreate_oracle_text_3.1.x.zip\" deleted by Nicholas Tsang\/San Jose\/IBM] [attachment \"recreate_oracle_text_4.x.zip\" deleted by Nicholas Tsang\/San Jose\/IBM] [attachment \"recreate_oracle_text_5.x.zip\" deleted by Nicholas Tsang\/San Jose\/IBM] \n\nHISTORICAL NUMBER\n 1075"}]},{"id":"DEV_Q168","question":"IBM Integration Designer could not connect to the DataPower appliance.\n\nI am using WDP XI52 with Firmware 7.0.0.7 and IID 7.5.1. When I try to connect WDP from [DataPower Appliances] View in IID, I got a error message as follows : \"SSL handshake on the connection to the DataPower appliance \"x.x.x.x\" was not successful. Contact the DataPower administrator.\" This situations occurred since WDP Firmware had upgraded from 7.0.0.2 to 7.0.0.5. (Now it was upgraded to 7.0.0.7)\nCould you please let me know what I should check to solve this problem? Please note that this WDP works normally and a network is normal. Also, I can connect it by using WebGUI and SSH terminal. And I've checked that IP , XML Management Interface Port, Web Management Service Port and account\/password are correct.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q169","question":"Migrating to JRules v7.1\n\nHow do I migrate to WebSphere ILOG JRules v7.1? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q170","question":"ODR OOM issue\n\nI got ODR OOM after upgrading the WAS to v8553. No configuration or traffic load changing. Is there any known issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q171","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?","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:","is_impossible":false,"contexts":[{"filename":"swg1PI34677.txt","text":"Title: IBM PI34677: MBEANSTARTER LOADEXTENSIONS FAILED TO LOAD EXTENSION - United States\n\nText:\n A FIX IS AVAILABLE\nFixes integrated in WebSphere Portal 8.5.0.0 Combined Cumulative Fixes [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037786]\n\n\nSUBSCRIBE\nYou can track all active APARs for this component.\n\n\n\nAPAR STATUS\n * CLOSED AS PROGRAM ERROR.\n \n \n \n\nERROR DESCRIPTION\n * During Portal Start-Up following error is shown:\n --------------------\n 0000005e MBeanStarter E com.ibm.wps.\n \n scripting.server.MBeanStarter loadExtensions failed to load\n extension:\n key: ServerExt.applications \/ value:\n com.ibm.wps.scripting.server.\n ApplicationServerExtensions\n \n \n \n \n \n\nLOCAL FIX\n * 1) open the WAS admin console\n 2) navigate to Resources > Resource environment providers > WP\n ScriptingService > Custom properties\n 3) you should see an entry with the name\n \"ServerExt.applications\" and value\n \"com.ibm.wps.scripting.server.ApplicationServerExtensions\"\n 4) delete this entry, save and restart the server.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * A code fix for this issue is integrated into the WebSphere\n Portal & WCM Combined Cumulative Fix 05 (PI31198 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI31198]) for Portal\n 8.5.0.0 available from Fix Central:\n \n http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent\n =ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al [http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm\/WebSphere&product=ibm\/WebSphere\/WebSphere+Portal&release=Al]\n l&platform=All&function=aparId&apars=PI31198\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * Added a task to remove the outdate resource environment\n provider entry.\n \n \n \n \n \n\nTEMPORARY FIX\n\nCOMMENTS\n\nAPAR INFORMATION\n * APAR NUMBER\n PI34677\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * REPORTED COMPONENT ID\n 5724E7600\n \n \n * REPORTED RELEASE\n 850\n \n \n * STATUS\n CLOSED PER\n \n \n * PE\n NoPE\n \n \n * HIPER\n NoHIPER\n \n \n * SPECIAL ATTENTION\n NoSpecatt\n \n \n * SUBMITTED DATE\n 2015-02-10\n \n \n * CLOSED DATE\n 2015-03-10\n \n \n * LAST MODIFIED DATE\n 2015-03-10\n \n \n\n * APAR IS SYSROUTED FROM ONE OR MORE OF THE FOLLOWING:\n \n \n \n * APAR IS SYSROUTED TO ONE OR MORE OF THE FOLLOWING:\n \n \n \n\nFIX INFORMATION\n * FIXED COMPONENT NAME\n WEBSPHERE PORTA\n \n \n * FIXED COMPONENT ID\n 5724E7600\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R850 PSY\n UP"}]},{"id":"DEV_Q172","question":"What's the procedure to drop an user in Cognos Disclosure Management?\n\n\n\nO.S AIX 7.1\n\nCognos Disclosure Management 10.2.4 What's the procedure to drop an user in Cognos Disclosure Management","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q173","question":"ORA-01795 Error accessing Decision Center Business Console 8.7\n\nI am working with ODM 8.7.0.0 when accessing the Business Console I am getting the below error message :\nORA-01795: maximum number of expressions in a list is 1000\nThe diagnostics do not contain any warning nor error.\nThe logs contain below exception : \n java.lang.RuntimeException: java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000\n...\n Caused by: java.sql.SQLException: ORA-01795: maximum number of expressions in a list is 1000","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q174","question":"Datacap on Citrix\n\n Hi All,\n\nCan we operate Datacap thin clients on citrix?\n","answer":"Remote users that access Datacap over a WAN can use Taskmaster Web-based \"thin clients\", or FastDoc Capture operating in offline mode.","is_impossible":false,"contexts":[{"filename":"swg21658019.txt","text":"Title: IBM Deploying IBM Datacap Taskmaster Capture on a WAN - United States\n\nText:\nWAN LAN architecture deployment TECHNOTE (FAQ)\n\nQUESTION\n What are the best practices for deploying Datacap servers and clients on a wide area network (WAN)? \n\nANSWER\nRemote users that access Datacap over a WAN can use Taskmaster Web-based \"thin clients\", or FastDoc Capture operating in offline mode. Datacap thick clients (DotScan, DotEdit) and utilities (NENU, Fingerprint Maintenance Tool) require LAN communication speeds and low latency for responsive performance. \n\nConnect all Datacap Taskmaster Servers, Rulerunner Servers, Web Servers, file servers and databases to a single high performance LAN for best results. Network delays between Taskmaster Server, shared files and databases causes degraded performance of Job Monitor and data intensive operations. \n\nSome customers successfully operate Datacap thick clients in remote sites using Citrix or other remote access technology. IBM has not tested or sought certification with Citrix, and does not provide support for Citrix. If you deploy Datacap clients on Citrix and encounter issues, IBM may require you to reproduce the issues outside of Citrix as part of the investigation. \n\nConsult the IBM Redbooks titled \"Implementing Imaging Solutions with IBM Production Imaging Edition and IBM Datacap Capture\", section 2.5, for deployment recommendations and diagrams.\n\nRELATED INFORMATION\n IBM Redbooks Production Imaging Edition [http:\/\/www.redbooks.ibm.com\/abstracts\/sg247969.html?Open]"}]},{"id":"DEV_Q175","question":"Would like to know if WebSphere Extreme Scale is leap year and leap second compliant. Is there any documentation that talks about this?\n\nWould like to know if WebSphere Extreme Scale is leap year compliant. Is there any documentation that talks about this? ","answer":"WebSphere Application Server and the SDK are leap year compliant.","is_impossible":false,"contexts":[{"filename":"swg21578744.txt","text":"Title: IBM WebSphere Application Server Is Leap Year Compliant - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We have had questions from clients planning for leap year years (containing February 29th) asking if WebSphere Application Server Leap Year Compliant, and if any problems are expected stemming from WebSphere Application Server or associated IBM products due to Leap Year. \n\nThere are no known or expected problems.\n(Details below) \n\nRESOLVING THE PROBLEM\nWebSphere Application Server and the SDK are leap year compliant. IBM Java (SDK \/ JDK) has been doing leap year testing\/verification since 1996, including the non-leap year 2000 without a problem. Basically leap years in Java are explicitly supported by the GregorianCalendar class - that is it's function - and this class is tested with every release of Java as it is part of Java's core functionality. So any Java code which uses the GregorianCalendar class will behave correctly. \n\nWebSphere Application Server performs no specific leap year testing since it runs on top of the SDK which is compliant, and uses function from it. We are not aware of any issues in the past with WebSphere Application Server associated with leap year. \n\nFrom a JDK perspective, Java applications which use the GregorianCalendar class will be leap-year compliant - see the spec at: \n\n(Same info in the links for the various JDK's) \n\nhttp:\/\/docs.oracle.com\/javase\/6\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/6\/docs\/api\/java\/util\/GregorianCalendar.html] \n\nhttp:\/\/docs.oracle.com\/javase\/7\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/7\/docs\/api\/java\/util\/GregorianCalendar.html]\n\nhttp:\/\/docs.oracle.com\/javase\/8\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/8\/docs\/api\/java\/util\/GregorianCalendar.html] \n\n\nSpecifically: \n\n\"The only difference between the Gregorian and the Julian calendar is the leap year rule. The Julian calendar specifies leap years every four years, whereas the Gregorian calendar omits century years which are not divisible by 400.\" In other words the Gregorian Calendar follows modern leap years. The correct operation of the class is tested by the Java Compliance Kit (JCK) which is run against every release of the JVM. So Java applications would need to assert that they are using GregorianCalendars to claim leap-year compliance."}]},{"id":"DEV_Q176","question":"Would like to know if WebSphere Extreme Scale is leap year and leap second compliant. Is there any documentation that talks about this?\n\nWould like to know if WebSphere Extreme Scale is leap second compliant. Is there any documentation that talks about this? ","answer":"WebSphere Application Server and the SDK are leap year compliant.","is_impossible":false,"contexts":[{"filename":"swg21578744.txt","text":"Title: IBM WebSphere Application Server Is Leap Year Compliant - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n We have had questions from clients planning for leap year years (containing February 29th) asking if WebSphere Application Server Leap Year Compliant, and if any problems are expected stemming from WebSphere Application Server or associated IBM products due to Leap Year. \n\nThere are no known or expected problems.\n(Details below) \n\nRESOLVING THE PROBLEM\nWebSphere Application Server and the SDK are leap year compliant. IBM Java (SDK \/ JDK) has been doing leap year testing\/verification since 1996, including the non-leap year 2000 without a problem. Basically leap years in Java are explicitly supported by the GregorianCalendar class - that is it's function - and this class is tested with every release of Java as it is part of Java's core functionality. So any Java code which uses the GregorianCalendar class will behave correctly. \n\nWebSphere Application Server performs no specific leap year testing since it runs on top of the SDK which is compliant, and uses function from it. We are not aware of any issues in the past with WebSphere Application Server associated with leap year. \n\nFrom a JDK perspective, Java applications which use the GregorianCalendar class will be leap-year compliant - see the spec at: \n\n(Same info in the links for the various JDK's) \n\nhttp:\/\/docs.oracle.com\/javase\/6\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/6\/docs\/api\/java\/util\/GregorianCalendar.html] \n\nhttp:\/\/docs.oracle.com\/javase\/7\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/7\/docs\/api\/java\/util\/GregorianCalendar.html]\n\nhttp:\/\/docs.oracle.com\/javase\/8\/docs\/api\/java\/util\/GregorianCalendar.html [http:\/\/docs.oracle.com\/javase\/8\/docs\/api\/java\/util\/GregorianCalendar.html] \n\n\nSpecifically: \n\n\"The only difference between the Gregorian and the Julian calendar is the leap year rule. The Julian calendar specifies leap years every four years, whereas the Gregorian calendar omits century years which are not divisible by 400.\" In other words the Gregorian Calendar follows modern leap years. The correct operation of the class is tested by the Java Compliance Kit (JCK) which is run against every release of the JVM. So Java applications would need to assert that they are using GregorianCalendars to claim leap-year compliance."}]},{"id":"DEV_Q177","question":"After AIX TL\/SP\/FP update my TSAMP cluster no longer functions.\n\nAfter applying update to AIX to bring it up to 7100-05-01-1731 which includes RSCT 3.2.3.0 I noticed that neither IBM.GblResRM nor IBM.RecoveryRM would stay operative in \"lssrc -g rsct_rm\" output. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q178","question":"Need support info for ITCAM and WAS 8.5.5.x monitoring\n\nWhat ITCAM for AD\/WAS versions and maintenance levels support monitoring of WAS 8.5.5.x?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q179","question":"Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735)\n\nI 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)","is_impossible":false,"contexts":[{"filename":"swg22014367.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:U\/C:L\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION\/FIXES\nFor MQ 5.3 \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"DEV_Q180","question":"Help with Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920)\n\nI need to understand details regarding \"Security Bulletin: Security Vulnerability in IBM PureApplication System (CVE-2015-1920)\". Where can I find this information? ","answer":"CVEID: CVE-2015-1920\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C) ","is_impossible":false,"contexts":[{"filename":"swg21964873.txt","text":"Title: IBM Security Bulletin: Security Vulnerability in IBM PureApplication System. (CVE-2015-1920) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM PureApplication System contains IBM WebSphere Application Server, which has a security vulnerability that could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2015-1920 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2015-1920]\nDESCRIPTION: WebSphere Application Server could allow a remote attacker to execute arbitrary code by connecting to a management port and executing a specific sequence of instructions.\nCVSS Base Score: 9.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/102404] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:C\/I:C\/A:C) \n\nPlease consult the security bulletin: Security Vulnerability in IBM WebSphere Application Server [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21883573]for additional vulnerability details and information\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V2.1\nIBM PureApplication System V2.0\nIBM PureApplication System V1.1 \n\nREMEDIATION\/FIXES\nThe solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1\n\u00b7 Web Application Pattern Type V2.0.4.2\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-2.0.4.2-sys&includeSupersedes=0&source=fc]\n\n\u00b7 Web Application Pattern Type V1.0.4.2\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=All&platform=All&function=fixId&fixids=webapp-1.0.4.2-sys&includeSupersedes=0&source=f]\n\nIBM PureApplication System V2.0 \nThe solution is to upgrade to IBM PureApplication System V2.0.0.1 Interim Fix 5\n\nIBM PureApplication System V1.1 and earlier:\nContact IBM customer support for upgrade options.\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 19 August 2015: Original Version Published\n11 September 2015 Updated for IBM PureApplication System v2.0 \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."}]},{"id":"DEV_Q181","question":"Get all data that\\'s registred today\n\nVersion: \nMxLoader 4.7.4\n \n\nProblem:\nIs it possible to do something like this:\nreportdate >= TODAY()?\n\nI cant get it to work but i would like to get all the data that has been registred today today. \n","answer":"The getdate() MSSQL function can be replaced by value from DB2 CURRENT DATE special register. On Oracle, sysdate is used to retrieve the current date. \n\nEXAMPLE : MSSQL and transdate <= ( getdate() - 35) \n\n DB2 and transdate <= ( CURRENT DATE - 35 DAYS) \n\n Oracle and transdate <= ( sysdate - 35)","is_impossible":false,"contexts":[{"filename":"swg21569933.txt","text":"Title: IBM Current Date function for DB2, SQL Server and Oracle - United States\n\nText:\nTPAEMSSQL; TPAEDB2; getdate; TPAEDATABASE; TPAEORACLE TECHNOTE (FAQ)\n\nQUESTION\n What would be the equivalent of MSSQL getdate() function for Maximo running on DB2 or Oracle? \n\nANSWER\nThe getdate() MSSQL function can be replaced by value from DB2 CURRENT DATE special register. On Oracle, sysdate is used to retrieve the current date. \n\nEXAMPLE : MSSQL and transdate <= ( getdate() - 35) \n\n DB2 and transdate <= ( CURRENT DATE - 35 DAYS) \n\n Oracle and transdate <= ( sysdate - 35) \n\n \n\nRELATED INFORMATION\n URL [http:\/\/publib.boulder.ibm.com\/infocenter\/db2luw\/v9r7\/index.jsp]"}]},{"id":"DEV_Q182","question":"Help with Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IIB and WMB\n\n\n\nI need to understand details regarding \"Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker\" This is related to\nCVE-2017-10115\nCVE-2017-10116\nCVE-2017-10109\nCVE-2017-10108\n\nWhere can I find this information?","answer":"CVEID:CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876]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:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22010090.txt","text":"Title: IBM Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect IBM Integration Bus and WebSphere Message Broker - United States\n\nText:\nIIB; WMB SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilities in IBM\u00ae SDK Java\u2122 Technology Edition, Version 7.1.4.10 and IBM\u00ae Runtime Environment Java\u2122 Versions 7.0.10.10 and 7.1.4.10 used by IBM Integration Bus and WebSphere Message Broker. These issues were disclosed as part of the IBM Java SDK updates in Jul 2017. \n\nVULNERABILITY DETAILS\n\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the \u201cReferences\u201d section for more information.\n\nCVEID:CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876]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:N\/A:N) \n\nCVEID:CVE-2017-10116 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H) \n\nCVEID:CVE-2017-10108 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10108]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128869 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128869]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\nCVEID:CVE-2017-10109 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10109]\nDESCRIPTION:An unspecified vulnerability in Oracle Java SE related to the Java SE, Java SE Embedded, JRockit Serialization component could allow an unauthenticated attacker to cause a denial of service resulting in a low availability impact using unknown attack vectors.\nCVSS Base Score: 5.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128870 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128870]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\nIBM Integration Bus V9.0.0.0 - V9.0.0.8 and V10.0.0.0 - V10.0.0.9 \n\nWebSphere Message Broker V8.0.0.0 - V8.0.0.9\nWebSphere Message Broker V7.0.0.0 - V7.0.0.8\n\nREMEDIATION\/FIXES\n \n\nProduct VRMF APAR Remediation \/ Fix IBM Integration Bus V10.0.0.0 - V10.0.0.9 IT21764 The APAR is available in fix pack 10.0.0.10 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043943]\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 - V9.0.0.8 IT21764 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] WebSphere Message Broker V8.0.0.0 - V8.0.0.9 IT21764 Contact IBM support to request a fix for APAR IT21764 WebSphere Message Broker V7.0.0.0 - V7.0.0.8 IT21764 Contact IBM support to request a fix for APAR IT21764 \n\nWebsphere Message Broker V7 and V8 are no longer in full support; IBM recommends upgrading to a fixed, supported version\/release\/platform of the product. \n\nIf you are a customer with extended support and require a fix, contact IBM support. \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] \nIBM Java SDK Security Bulletin [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg22006695] \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 15th November 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\nRELATED INFORMATION\n# \n\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 7.0, 8.0 \nPRODUCT ALIAS\/SYNONYM\n IIB\nWMB"}]},{"id":"DEV_Q183","question":"Is there a support's guide to the MTTrapd probe ?\n\nWhere do you download the Support's guide to the MTTrapd [SNMP] probe ?","answer":"The attached Support's guide to the SNMP probe provides details on how best to configure the probe, troubleshoot issues and how to use third party products to test the probes behaviour.","is_impossible":false,"contexts":[{"filename":"swg21607690.txt","text":"Title: IBM Support's Guide to the SNMP [MTTrapd] probe - United States\n\nText:\nnco_p_mttrapd; snmp; rules file; probe; snmpsend; snmptrap; test; testing; snmpv3 TECHNOTE (FAQ)\n\nQUESTION\n MTTrapd probe : How can you troubleshoot configuration issues? \n\nANSWER\nThe MTTrapd (SNMP) probe is a Generic probe used to process SNMP traps.\nIt is a multi-threaded probe and supports both UDP and TCP traps\/informs.\n\nThe attached Support's guide to the SNMP probe provides details on how best to configure the probe, troubleshoot issues and how to use third party products to test the probes behaviour.\n\nThe latest probe version is:\nRelease ID: 20.0.2\nOr higher.\n\nRELATED INFORMATION\n Where to locate the latest MTTrapd probe release 20.0.2 [https:\/\/developer.ibm.com\/answers\/questions\/414820\/where-do-you-download-the-mttrapd-probe-release-20\/]\n\n\nSNMP_MTTRAPDProbe_SupportsGuide_22.pdf [\/support\/docview.wss?uid=swg21607690&aid=2]SNMP_MTTRAPDProbe_SupportsGuide_22.pdf [\/support\/docview.wss?uid=swg21607690&aid=1]"}]},{"id":"DEV_Q184","question":"Why am I seeing \"CWSXM0100E: Multiple replies have been produced for a single request flow in module\" ?\n\nWe are building a simple mediation module, consisting only of the request flow. The mediation module has one service invoke calling an external service through web service binding. Upon testing the process, we observe see that the service invoke is being called twice. There is no Fan-in or fan -out in the request flow. Below is the error: \"Caused by: com.ibm.wsspi.sibx.mediation.flow.MediationRuntimeException: CWSXM1023E: Exception when calling flow action: CWSXM0100E: Multiple replies have been produced for a single request flow in module\" ","answer":"This error occurs when a mediation primitive is wired more than once to the next mediation primitive. It might seem to be a single wire. However, upon closer inspection, more than one wire exists. \n\n\nBy mistake, primitives might be wired more than once when there is only one wire. See the following screen shot:\n[\/support\/docview.wss?uid=swg21584783&aid=1]\n\nIf you move the primitives in question, however, you notice that there are more wires underneath:","is_impossible":false,"contexts":[{"filename":"swg21584783.txt","text":"Title: IBM A CWSXM0100E error is received for WebSphere Enterprise Service Bus (WESB), WebSphere Process Server (WPS), or IBM Business Process Manager (BPM) Advanced - United States\n\nText:\nCWSXM0100E; multiple; replies; single; request TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a single request is sent to a Mediation Flow Component in WebSphere Enterprise Service Bus, WebSphere Process Server, or Business Process Manager Advanced, services can be invoked more than once. \n\nSYMPTOM\nThe following error message can be observed in the SystemOut.log file:\n\nCWSXM0100E: Multiple replies have been produced for a single request flow in module <module_name> \n\nMore than one invocation can occur from a single request.\n\nCAUSE\nThis error occurs when a mediation primitive is wired more than once to the next mediation primitive. It might seem to be a single wire. However, upon closer inspection, more than one wire exists. \n\n\nBy mistake, primitives might be wired more than once when there is only one wire. See the following screen shot:\n[\/support\/docview.wss?uid=swg21584783&aid=1]\n\nIf you move the primitives in question, however, you notice that there are more wires underneath:\n\n[\/support\/docview.wss?uid=swg21584783&aid=2]\n\n\n\nRESOLVING THE PROBLEM\nTo solve this problem, complete the following steps: \n\n 1. Delete any redundant wires. \n \n \n 2. Save the project.\n \n \n 3. Redeploy the application to the server.\n\nRELATED INFORMATION\n#IC67220: OUTSTANDING PROCESSING OCCURS IN AN AGGREGATIO [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IC67220]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Advanced Mediation AIX, Linux, Solaris, Windows, z\/OS 8.0, 7.5.1, 7.5.0.1, 7.5 Business Integration WebSphere Process Server Mediation AIX, HP-UX, Linux, Solaris, Windows, z\/OS 7.0.0.4, 7.0.0.3, 7.0.0.2, 7.0.0.1, 7.0, 6.2.0.3, 6.2.0.2, 6.2.0.1, 6.2"}]},{"id":"DEV_Q185","question":"What can I do when I receive CWZIP9602E, CWZIP9604W and CWZIP4514E with Call Home?\n\nI received the following critical events after enabling CallHome on my PureApplication System v.2.0.0.1:\nCWZIP4514E: Configuration Settings for Call Home are not configured properly.\nCWZIP9602E: Service53 is failed offline at node and cannot be restarted.\nCWZIP9604W: Service53 failed. The high availability component will attempt to recover the service.\nWhat can I do?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q186","question":"Silent uninstall of ITCAM for MQ agent fails\n\nRunning silent uninstall of the ITCAM for MQ agent with this command: start \/wait setup \/z\"\/sfMQ_Silent_Uninstall.txt\" \/s \/f2\"C:\\temp\\silent_setup.log\" fails with this message in the Abort_*.trc file: SEVERE: You must agree to the License Agreement.\n\nThe MQ_Silent_Uninstall.txt does contain this line: License Agreement=I agree to use the software only in accordance with the installed license.","answer":"Specify the complete path to the silent response file while launching the silent install.","is_impossible":false,"contexts":[{"filename":"swg21608744.txt","text":"Title: IBM Silent Install - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Silent install of any of the Tivoli Monitoring components fails. \n\nCAUSE\nWhen the complete path to the silent response file is not specified as part of the command invoking the silent install, it fails with the following error message in the log file: \n\n------------------------------------------------------------\n08-16-2012 09:52:31: Silent install configuration file: silent_response.txt\n08-16-2012 09:52:31: \n08-16-2012 09:52:31: AgentDeployRunning=FALSE.\n08-16-2012 09:52:31: \n08-16-2012 09:52:31: SEVERE: You must agree to the License Agreement.\n08-16-2012 09:52:31: SEVERE: Silent install config error.\n08-16-2012 09:52:31: Silent install config error.\n------------------------------------------------------------\n\n\n\nRESOLVING THE PROBLEM\nSpecify the complete path to the silent response file while launching the silent install. \n\ne.g.\nsetup \/z\"\/sfE:\\TEMP\\silent_response.txt\" \/s \/f2\"C:\\temp\\itm6_agent_setup.log\""}]},{"id":"DEV_Q187","question":"Help with Security Bulletin: Multiple Vulnerabilities identified in IBM Java SDK affect WSRR\n\nI need to understand details regarding Security Bulletin: Multiple Vulnerabilities identified in IBM\u00ae Java SDK affect WebSphere Service Registry and Repository, in particular CVE-2017-10115. Where can I find this information? ","answer":"CVEID:CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876]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:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22007002.txt","text":"Title: IBM Security Bulletin: Multiple Vulnerabilities in IBM\u00ae Java SDK affects WebSphere Application Server July 2017 CPU - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabiltities in the IBM\u00ae SDK Java\u2122 Technology Edition that is shipped with IBM WebSphere Application Server. These issues were disclosed as part of the IBM Java SDK updates in July 2017. These may affect some configurations of IBM WebSphere Application Server Traditional, IBM WebSphere Application Server Liberty and IBM WebSphere Application Server Hypervisor Edition. \n\nVULNERABILITY DETAILS\nFor information on the IBM Java SDK that is now bundled with WebSphere Application Server Version 8.5.5 refer to the Knowledge Center link in the References section. \n\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\" located in the References section for more information.\nHP fixes are on a delayed schedule. \n\nCVEID: CVE-2017-10102 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10102]\nDESCRIPTION: An unspecified vulnerability related to the Java SE RMI component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128863 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128863] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:N\/S:C\/C:H\/I:H\/A:H) \n\n\nCVEID:CVE-2017-10116 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10116]\nDESCRIPTION:An unspecified vulnerability related to the Java SE, Java SE Embedded, JRockit Security component could allow an unauthenticated attacker to take control of the system.\nCVSS Base Score: 8.3\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128877]for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:H\/PR:N\/UI:R\/S:C\/C:H\/I:H\/A:H) \n\nCVEID:CVE-2017-10115 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-10115]\nDESCRIPTION:An unspecified vulnerability related to the Java SE, Java SE Embedded, JRockit JCE component could allow an unauthenticated attacker to obtain sensitive information resulting in a high confidentiality impact using unknown attack vectors.\nCVSS Base Score: 7.5\nCVSS Temporal Score: Seehttps:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/128876]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:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM SDK, Java Technology Editions shipped with WebSphere Application Server Liberty up to 17.0.0.2. IBM SDK, Java Technology Editions shipped with IBM WebSphere Application Server Traditional Version 9.0.0.0 through 9.0.0.4, 8.5.0.0 through 8.5.5.12, Version 8.0.0.0 through 8.0.0.13, Version 7.0.0.0 through 7.0.0.43. \n\n * This does not occur on IBM SDK, Java Technology Editions that are shipped with WebSphere Application Servers Fix Packs 17.0.0.3, 9.0.0.5 8.5.5.13, 8.0.0.14, and 7.0.0.45 or later. \n\nREMEDIATION\/FIXES\nDownload and apply the interim fix APARs below, for your appropriate release \n\nFor the IBM Java SDK updates: \n\nFor WebSphere Application Server Liberty: \nFor the IBM SDK, Java Technology Version that you use, upgrade to WebSphere Application Server Liberty Fix Packs as noted below or later fix pack level and apply one of the interim fixes below: \n\nUpgrade to WebSphere Application Server Liberty Fix Pack 8.5.5.1 or later then apply Interim Fix PI84267 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043903] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043639]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 50 Upgrade to WebSphere Application Server Liberty Fix Pack 8.5.5.1 or later then apply Interim Fix PI84265 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043898] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043628] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043320]: [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041667] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041197] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040406] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039958] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039665] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039312] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038810] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038089] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036966] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24036508] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035400] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035008] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034806] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034592] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037534] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037709] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036966] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24036508] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035400] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035008] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034806] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 FP10 For IBM SDK, Java Technology Edition Version 7R1 and IBM SDK, Java Technology Edition Version 8, please refer to IBM Java SDKs for Liberty [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27049903] \n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Liberty (17.0.0.3) or later. \n \n \n\nFor Version 9 WebSphere Application Server Traditional: Update the IBM SDK, Java Technology Edition using the instructions in the IBM Knowledge Center Installing and updating IBM SDK, Java Technology Edition on distributed environments [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSEQTP_9.0.0\/com.ibm.websphere.installation.base.doc\/ae\/tins_installation_jdk.html] then use the IBM Installation manager to access the online product repositories [http:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSEQTP_9.0.0\/com.ibm.websphere.installation.base.doc\/ae\/cins_repositories.html]to install the SDK or use IBM Installation manager and access the packages from Fixcentral [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042430]. \n\n\nFor V8.5.0.0 through 8.5.5.12 WebSphere Application Server Traditional and WebSphere Application Server Hypervisor Edition: \n\nFor information on the IBM Java SDK that is now bundled with WebSphere Application Server Version 8.5.5 refer to the Knowledge Center link in the References section. \n\nUpgrade to WebSphere Application Server Traditional Fix Packs as noted below or later fix pack level and then apply one or more of the interim fixes below: \n\n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.1 or later then apply Interim Fix PI84266 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043902] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043636] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043321]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 Fix Pack 50 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.1 or later then apply Interim Fix PI84265 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043898]: [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043628] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042554] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042119] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039958] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039665] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039312] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038810] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038089] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036966] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24036508] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035400] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035008] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034806] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034592] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037534] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037709] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036966] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24036508] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035400] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035008] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034806] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7 Service Refresh 10 FP10 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.2 or later then apply Interim Fix PI84264 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043899]: [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043627] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041671] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041668] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041194] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040407] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040157] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039961] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039687] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039311] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038809] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038165] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036966] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24036508] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035400] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035008] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034806] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034592]Will upgrade you to IBM SDK, Java Technology Edition, Version 7R1 Service Refresh 4 FP10 \n * Upgrade to WebSphere Application Server Traditional Fix Pack 8.5.5.9 or later then apply Interim Fix PI84261 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043900] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043624]: [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042939] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042552] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24042111] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040158] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039956] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039668] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24039304] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038812] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24038093] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24037708] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036967] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036505] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035398] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034998] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034447]Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 4 FP10 \n * For environnments that have been upgraded to use the new default IBM SDK Version 8 bundled with WebSphere Application Server Fix Pack 8.5.5.11 or later: Apply Interim Fix PI84263 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043901] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043625]: Will upgrade you to IBM SDK, Java Technology Edition, Version 8 Service Refresh 4 FP10 \n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 13 (8.5.5.13) or later. \n\n\n\nFor V8.0.0.0 through 8.0.0.13 WebSphere Application Server and WebSphere Application Server Hypervisor Edition: Upgrade to WebSphere Application Server Fix Pack 8.0.0.7 or later then apply the interim fix below: \n\n * Apply Interim Fix PI84268 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043904]: [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043640] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036967] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24036505] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24035398] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034998] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24034447]Will upgrade you to IBM SDK, Java Technology Edition, Version 6R1 Service Refresh 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033359]Fix Pack 50\n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 14 (8.0.0.14) or later.\n\n\nFor V7.0.0.0 through 7.0.0.43 WebSphere Application Server and WebSphere Application Server Hypervisor Edition: Upgrade to WebSphere Application Server Fix Pack 7.0.0.31 or later then apply the interim fix below: \n\n * Apply Interim Fix PI84269 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043905] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043641]: Will upgrade you to IBM SDK, Java Technology Edition, Version 6 Service Refresh 16 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24033359] Fix Pack 50\n\n--OR-- * Apply IBM Java SDK shipped with WebSphere Application Server Fix pack 45 (7.0.0.45) or later.\n\n\nFor unsupported versions of the above products, IBM recommends upgrading to a fixed, supported version of the product. 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.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] \nIBM Java SDK Security Bulletin [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22006695] \nIBM Java SDK Version 8 bundled with WebSphere Application Server [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSAW57_8.5.5\/com.ibm.websphere.nd.doc\/ae\/covr_javase6_eos.html] \nIBM Java SDKs for WebSphere Liberty [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27049903] \nIBM SDK Java Technology Edition Version 8.0 for WebSphere Liberty using archives [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043502] \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 August 2017: original document published\n06 September 2017: replaced CVE-2017-10107 with CVE-2017-10102 \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=swg22009279]\n\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Application Servers WebSphere Application Server Hypervisor Edition"}]},{"id":"DEV_Q188","question":"Is there a support's guide to the CORBA Probes?\n\nWhere can I download the support's guide to the IBM CORBA probes?","answer":"GENERIC_CORBA_SupportsGuide_20.pdf","is_impossible":false,"contexts":[{"filename":"swg21614208.txt","text":"Title: IBM Support's Guide to IBM CORBA probes - United States\n\nText:\ncorba; 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]"}]},{"id":"DEV_Q189","question":"How to wrap table column text in list tab for a specific table?\n\nI would like to wrap the text of table column into new a line. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q190","question":"Is it possible to use Java large pages (-Xlp) parm with ITCAM? Is this supported?\n\nIs it possible to use Java large pages (-Xlp) parm with ITCAM? Is this a supported feature?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q191","question":"Why does my install of the latest Installation Manager on a Linux Ingram Server not function?\n\nWhy does my install of the latest Installation Manager on a Linux Ingram Server not function?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q192","question":"Cannot open module in exclusive edit - (no such file or directory)\n\n Hello.\n\nI have a module, that I can open normally, but when I try to open it in Exclusive Edit it tells me that \"no such file or directory\"\n\nIs this a known problem?","answer":"This issue has been identified as a product defect under APAR PM50525","is_impossible":false,"contexts":[{"filename":"swg21511831.txt","text":"Title: IBM DOORS module fails to open in exclusive edit mode results in error \"unable to open module ...no such file or directory\" - United States\n\nText:\nmissing session file; file not found; can not open module; open module exclusive edit fails; PM50525 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Attempts to open a module exclusive edit in IBM Rational DOORS result in the error \"DOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\". \n\nSYMPTOM\nA module with a large number of sections is used mostly in shareable edit mode. \n\nYou can open the module Read-only , or Shareable-Edit; but not in exclusive edit. \n\nSteps to reproduce: \n\n 1. Login to DOORS\n \n \n 2. Click the Project, or folder, icon that contains the module\n \n \n 3. Click the module icon in the DOORS Explorer window\n \n \n 4. Click File > Open> Exclusive Edit (Ctrl + E)\n \n\n\nExpected result: The module should open in Exclusive edit mode. \n\nActual result: The module will not open in exclusive edit module; however it will open in read only mode, or shareable edit mode. If you attempt to check the database integrity for issue the module is not flagged for any problems. \n\nThe full error message is as follows:\n\nDOORS report\nUnable to open module '\/A Project\/Requirements' No such file or directory\"\nC:\\Program Files (x86)\\IBM\\Rational\\DOORS\\9.5\\data\\v6data\\20\\m00000021.mod\\current.ver\\s1000005.dtc\n\n\nimage \n\n[\/support\/docview.wss?uid=swg21511831&aid=1] [\/support\/docview.wss?uid=swg21511831&aid=1]\n\nCAUSE\n This issue has been identified as a product defect under APAR PM50525 [http:\/\/ibm.com\/support\/docview.wss?uid=swg1PM31236].\n\n\n\nRESOLVING THE PROBLEM\nThis error indicates that a user session file is corrupted on the database server. \n\nThis defect is resolved in IBM Rational DOORS Version 9.4.0.1 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27036720#9401] \n\n \n\nWORKAROUND: \n\nthe following options can be used to correct this problem: \n\n * Retrieve the missing file from system backup and insert it into the module current.ver directory\n \n The advantage of inserting the missing session file is you do not need to restart the database server.\n\nWarning these two option should only be performed by Rational Support. Modifications to the files in your DOORS database could result is data corruption and jeapordize your DOORS database. Send the session.ixc file to support for repair\n\nFrom the module directory listed in the error message provide support the file session.ixc\nChoosing to have support repair the session index file requires you to have all users log out \nand shut down the DOORS database server until the repaired file is returned and inserted \nto replace the existing data file for the module.\n\nCreate a replacement session file \nFrom the module directory listed in the error message provide support the file session.ixc\nAdjacent session files will be required in order to to create the replacement. \nYour support engineer will identify these files from the session index file.\nNo work can be performed in the effected module until the replacement session file is restored\nfor the effected module. \n\n\nNote: Generally the repair is only required for one user session file. However in circumstances where DOORS reports a missing session file for a module- the event that caused this may have effected session files for other users connected to the module. For this situation you may need to perform a successive repair to the index file."}]},{"id":"DEV_Q193","question":"Are there any probes that can connecto the Nokia NSP EPC v17.9 and Nokia NSP RAN v17.3 using JMS\/HTTP?\n\nThe customer has asked if there are any probes that can connect to their Nokia servers, both of which use a HTTP\/JMS interface:\n\n Nokia NSP EPC v17.9 \n Nokia NSP RAN v17.3 ","answer":"This probe is written to support Nokia Network Functions Manager for Packet release 17.3.","is_impossible":false,"contexts":[{"filename":"swg22005197.txt","text":"Title: IBM Tivoli Netcool\/OMINbus Integrations Release Notice - Probe for Nokia Network Functions Manager for Packet (nco-p-nokia-nfmp-1_0) - United States\n\nText:\nrelease 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]"}]},{"id":"DEV_Q194","question":"How to generate Javacores automatically in on hung threads reported in SystemOut.log for WebSphere Application Server?\n\nNeed Javacores to be generated on hung threads messages reported in SystemOut.log for WebSphere Applicaiton Server.Example:WSVR0605W: Thread has been active for and may be hung. There are in total in the server that may be hung.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q195","question":"TLS protocol with ITCAM for Datapower\n\nWe have a DataPower appliance with TLS security protocol enabled. Can we configure ITCAM for DataPower appliance v7.1 to specifically use the TLS protocol v1.2 (not v1.0)?\n","answer":"TLSv1.2 is supported by using the same fix.","is_impossible":false,"contexts":[{"filename":"swg21959224.txt","text":"Title: IBM TLS support and DataPower appliance - United States\n\nText:\nCAMDPALL CAMDPSEC TLS 1.0 1.2 TECHNOTE (FAQ)\n\nQUESTION\n Is this HotFix for TLS 1.0 (http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21694441 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21694441]) able to support also TLS 1.2? \n\nANSWER\nYes, TLSv1.2 is supported by using the same fix.\nJust an additional NOTE: As the default version expected is TLSv1, if you have disabled TLSv1 in the DataPower appliance (use only TLSv1.2), then please make sure to manually modify the value of KBN_SOMA_PROTOCOL to TLSv1.2."}]},{"id":"DEV_Q196","question":"Error while installing SpSS modeler trial version\n\nI have downloaded the SPSS modeller trial version (18.1) (64 bit) and trying to install the same. I get the following error 1152: Error extracting modelerClient64.msi to the temporary location\n","answer":"When an IBM SPSS compressed image is launched, files compressed within it are extracted to the temporary location assigned to the signed in user i.e. \/Documents and settings\/... or \/users.\nThe possibility of these files downloaded improperly exists. You can use a tool such\nas MD5 to verify the file content or simply attempt downloading a second time and test.\n\nOther possible causes of this error:\n- Available space within the temporary location noted by the installer.\n- Ability to write in the temporary location noted by the installer.\n\n\nANSWER\nTransfer the files again, resolved the issue.","is_impossible":false,"contexts":[{"filename":"swg21577970.txt","text":"Title: IBM Installing Modeler gives 1152: Error extracting <path to user temp storage> to the temporary location - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n What causes an 1152 error during extraction of Modeler self extracting executable? \n\nCAUSE\nWhen an IBM SPSS compressed image is launched, files compressed within it are extracted to the temporary location assigned to the signed in user i.e. \/Documents and settings\/... or \/users.\nThe possibility of these files downloaded improperly exists. You can use a tool such\nas MD5 to verify the file content or simply attempt downloading a second time and test.\n\nOther possible causes of this error:\n- Available space within the temporary location noted by the installer.\n- Ability to write in the temporary location noted by the installer.\n\n\nANSWER\nTransfer the files again, resolved the issue. \n\nRELATED INFORMATION\n Need more help? Our Modeler forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/modeler\/?smartspace=predictive-analytics]"}]},{"id":"DEV_Q197","question":"Help with Security Bulletin: WMB and IIB are affected by 'Information Disclosure' vulnerability\n\nI need to understand details regarding Security Bulletin: WebSphere Message Broker and IBM Integration Bus are affected by 'Information Disclosure' vulnerability. Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q198","question":"Why is CSV002I occurring for CSQADITB?\n\nAn application is getting repeated errors: \nCSV002I REQUESTS FOR MODULE CSQADITB EXCEED MAXIMUM USE COUNT\n\nRestarting the application clears the error messages for a while. Why is this occurring?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q199","question":"How do I resolve a WSVR0605W hung thread issue in the WebSphere MQ Resource Adapter?\n\nThe following WebSphere MQ Resource Adapter hung thread can prevent an application server from starting...\n\nWSVR0605W: Thread \"WMQJCAResourceAdapter : 6\" (0000001b) has been active for 698530 milliseconds and may be hung. There is 1 thread(s) in total in the server that may be hung. at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:167) at com.ibm.ejs.container.MessageEndpointFactoryImpl.createEndpoint(MessageEndpointFactoryImpl.java:498) at com.ibm.mq.connector.inbound.WorkImpl.run(WorkImpl.java:149)","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q200","question":"Improve Performance of Rule Designer (ODM) and Rule Studio (JRules)\n\nHow can I improve the performance when working with ODM Rule Designer or WebSphere ILOG JRules Rule Studio? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q201","question":"Why are HTML documents not rendering and just shown as plain text after upgrading and installing ifixes to BPM?\n\nAfter upgrading BPM, my HTML documents that were once rendering are no longer being displayed correctly and are being shown as plain text. This is happening in multiple web browses. ","answer":"Install IBM Business Process Manager interim fix JR50092 as appropriate for your current IBM Business Process Manager or WebSphere Lombardi Edition version.","is_impossible":false,"contexts":[{"filename":"swg21679979.txt","text":"Title: IBM Security Bulletin: Insufficient control over MIME types in Business Process Manager (BPM) and WebSphere Lombardi Edition document feature (CVE-2014-3075) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n You cannot restrict file uploads by MIME type in a document list coach view. As a result, potentially malicious files, such as HTML that contains embedded JavaScript can be uploaded and run in the browser. \n\nVULNERABILITY DETAILS\nCVE ID: CVE-2014-3075 [https:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=cve-2014-3075]\nDESCRIPTION: \nIBM BPM document management feature might allow a remote attacker to include arbitrary files. A remote attacker might upload a file from a remote system, which might be viewed in an iframe by other end users.\n\nCVSS Base Score: 4.0\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/93817 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/93817] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:L\/Au:S\/C:N\/I:P\/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\n \n\n * IBM Business Process Manager Standard V7.5.x, 8.0.x, and 8.5.x \n * IBM Business Process Manager Express V7.5.x, 8.0.x, and 8.5.x \n * IBM Business Process Manager Advanced V7.5.x, 8.0.x, and 8.5.x \n * IBM WebSphere Lombardi Edition V7.2.0.x\n\nREMEDIATION\/FIXES\nInstall IBM Business Process Manager interim fix JR50092 as appropriate for your current IBM Business Process Manager or WebSphere Lombardi Edition version. \n\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=JR50092] \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=JR50092] \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=JR50092] \n * IBM 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=JR50092]\n\n\nIf you are using earlier unsupported versions, IBM strongly recommends that you upgrade to a supported version. \n\nThe fix introduces additional functionality to the product with two server-side configuration options. One option is for file uploads and other option is for file downloads. \n * A server-side configuration option is introduced, which allows you to specify an optional white-list of MIME types. MIME types that are included in the list are allowed for uploads, but all other MIME types are blocked from uploads. \n * A server-side configuration option is introduced, which allows you to specify an optional black-list of MIME type mappings. Each MIME type mapping allows for a conversion to be made from a specific MIME type to a specific MIME type upon download.\n\n\nThe following example is a sample configuration of new options, which you can configure in the 100Custom.xml file: \n\n<server> \n<!-- mime type white list which specifies mime types accepted for --> \n<!-- upload to document list or document attachment --> \n<document-attachment-accepted-mime-types> \n<!-- specifies whether to allow a null mime type for upload --> \n<allow-null-mime-type>false<\/allow-null-mime-type> \n<!-- lists the mime types allowed for upload --> \n<mime-type>text\/plain<\/mime-type> \n<mime-type>img\/png<\/mime-type> \n<\/document-attachment-accepted-mime-types> \n\n<!-- mime type black list which specifies mappings from unacceptable --> \n<!-- mime types to acceptable mime types for download from --> \n<!-- document list or document attachment --> \n<document-attachment-download-mime-types> \n<!-- will map text\/html mime type to text\/plain mime type --> \n<mime-type-map> \n<from>text\/html<\/from> \n<to>text\/plain<\/to> \n<\/mime-type-map> \n<!-- missing <to> element implies mapping to content\/octet-stream --> \n<mime-type-map> \n<from>application\/pdf<\/from> \n<\/mime-type-map> \n<\/document-attachment-download-mime-types> \n<\/server> \n\nNote: The default configuration, which does not include the configuration information that is provided in the 100Custom.xml file, acts as a blacklist for the text\/html MIME type and maps it to the text\/plain MIME type. Providing a configuration in the 100Custom.xml file overrides the default configuration. As a result, for text\/html to remain on the blacklist, it should be explicitly added to the 100Custom.xml file. 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.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 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 2014-08-29 - initally published\n2014-11-03 - updated summary and CVSS information (loweing CVSS from 6.5 to 4.0) \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 IBM Business Process Manager Standard Security AIX, Linux, Linux zSeries, Solaris, Windows 8.5.5, 8.5.0.1, 8.5, 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 Express Security Linux, Linux zSeries, Windows 8.5.5, 8.5.0.1, 8.5, 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, Linux zSeries, Linux\/x86, Solaris, Windows, Windows Vista, Windows XP 7.2.0.5, 7.2.0.4, 7.2.0.3, 7.2.0.2, 7.2.0.1, 7.2 \nPRODUCT ALIAS\/SYNONYM\n BPM"}]},{"id":"DEV_Q202","question":"Why is installation manager cores when try to install netcool using GUI mode in AIX 7.1?\n\nIBM Installation Manager Cores when running in GUI mode on AIX 7.1 ","answer":"To use the GUI, the gtk+ RPM and dependencies must be available on AIX. \n\n\nInstall this set of RPMs on AIX:","is_impossible":false,"contexts":[{"filename":"swg21631478.txt","text":"Title: IBM Required gtk libraries for IBM Installation Manager on AIX - United States\n\nText:\ngtk; motif TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Installation Manager requires gtk libraries to support the graphical user interface (GUI). \n\nSYMPTOM\nInstallation Manager reports errors when the gtk libraries are not installed. \n\nExamples of the reported errors:\n\n\n * SWT library could not be loaded:\n\n\n\n# .\/install\n00:00.92 ERROR [main] org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory safeLogged\nCould not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\njava.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:\n\/root\/Desktop\/InstallationManager\/configuration\/org.eclipse.osgi\/bundles\/633\/1\/.cp\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\nswt-pi-gtk (Not found in java.library.path)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk-4234.a (A file or directory in the path name does not exist.)\n\/root\/.swt\/lib\/aix\/ppc\/libswt-pi-gtk.a (A file or directory in the path name does not exist.)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:331)\nat org.eclipse.swt.internal.Library.loadLibrary(Library.java:240)\nat org.eclipse.swt.internal.gtk.OS.<clinit>(OS.java:22)\nat java.lang.J9VMInternals.initializeImpl(Native Method)\n...\nThe displayed failed to initialize. See the log \/root\/Desktop\/InstallationManager\/configuration\/1361168761043.log for details. \n * Segmentation error occurs when the gtk libraries are installed but are not at the required versions\n\n\n\nUnhandled exception\nType=Segmentation error vmState=0x00040000\nJ9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033\nHandler1=F0739208 Handler2=F05F5F1C\nR0=D3D9FDCC R1=3013EEF0 R2=F077B69C R3=F0779450\nR4=00000000 R5=00000000 R6=00000000 R7=00000000\nR8=1220000F R9=1220000F R10=F0687A0C R11=000034E0\nR12=03222C60 R13=30C7DD00 R14=31FAA028 R15=F05851EC\nR16=00000007 R17=00000000 R18=F073B388 R19=30C7DD50\nR20=32935C30 R21=31FAA040 R22=00000000 R23=30000BC8\nR24=10010E04 R25=F05F7130 R26=30148364 R27=0000007E\nR28=CFACCBB8 R29=F073AB7C R30=D3DC1410 R31=F0779430\nIAR=D3DB63A8 LR=D3D9FDE8 MSR=0000D032 CTR=D3DE0E70\nCR=22004084 FPSCR=82000000 XER=0000001B TID=00000000\nMQ=00000000\nFPR0 329d3fd000000110 (f: 272.000000, d: 6.943460e-65)\nFPR1 41e0000000000000 (f: 0.000000, d: 2.147484e+09)\nFPR2 c1e0000000000000 (f: 0.000000, d: -2.147484e+09)\nFPR3 4330000001e00000 (f: 31457280.000000, d: 4.503600e+15)\nFPR4 4330080000000000 (f: 0.000000, d: 4.512396e+15)\nFPR5 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR6 4133851800000000 (f: 0.000000, d: 1.279256e+06)\nFPR7 4330080000138518 (f: 1279256.000000, d: 4.512396e+15)\nFPR8 005f0031002e0034 (f: 3014708.000000, d: 6.897895e-307)\nFPR9 002e0038002e0076 (f: 3014774.000000, d: 8.344265e-308)\nFPR10 0032003000310033 (f: 3211315.000000, d: 1.001324e-307)\nFPR11 0030003200320035 (f: 3276853.000000, d: 8.900720e-308)\nFPR12 3fe8000000000000 (f: 0.000000, d: 7.500000e-01)\nFPR13 4028000000000000 (f: 0.000000, d: 1.200000e+01)\nFPR14 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR15 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR16 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR17 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR18 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR19 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR20 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR21 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR22 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR23 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR24 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR25 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR26 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR27 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR28 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR29 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR30 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nFPR31 0000000000000000 (f: 0.000000, d: 0.000000e+00)\nTarget=2_40_20110203_074623 (AIX 7.1)\nCPU=ppc (8 logical CPUs) (0xc0000000 RAM)\n----------- Stack Backtrace -----------\n(0xD3D9F81C)\n(0xD43D5E48)\n(0xD43D8698)\n(0xD43D1D38)\n(0xD43D1B24)\n(0xD3E4ABA0)\n(0xD43D3058)\n(0xD43D3200)\n(0xD0F0ED18)\n(0xD0F1536C)\n(0xD0F19438)\n(0xD2B1DF48)\n(0xD2AE7780)\n(0xD2AE7A30)\n(0xD1516BAC)\n(0xD2AE78E4)\n(0xD2AE7E24)\n(0xD2AEC6C4)\n(0x100013C0)\n(0xD04FCD88)\n---------------------------------------\nJVMDUMP006I Processing dump event \"gpf\", detail \"\" - please wait.\nJVMDUMP032I JVM requested System dump using '\/opt\/IBM\/InstallationManager\/eclipse\/core.YYYY0318.095945.7798784.0001.dmp' in response to an event\nNote: \"Enable full CORE dump\" in smit is set to FALSE and as a result there will be limited threading information in core file.\nJVMDUMP010I System dump written to \/opt\/IBM\/InstallationManager\/eclipse\/core.YYYY0318.095945.7798784.0001.dmp\nJVMDUMP032I JVM requested Java dump using '\/opt\/IBM\/InstallationManager\/eclipse\/javacore.YYYY0318.095945.7798784.0002.txt' in response to an event\nJVMDUMP010I Java dump written to \/opt\/IBM\/InstallationManager\/eclipse\/javacore.YYYY0318.095945.7798784.0002.txt\nJVMDUMP032I JVM requested Snap dump using '\/opt\/IBM\/InstallationManager\/eclipse\/Snap.YYYY0318.095945.7798784.0003.trc' in response to an event\nJVMDUMP010I Snap dump written to \/opt\/IBM\/InstallationManager\/eclipse\/Snap.YYYY0318.095945.7798784.0003.trc\nJVMDUMP013I Processed dump event \"gpf\", detail \"\".\nSegmentation fault (core dumped)\n\nCAUSE\nInstallation Manager is an Eclipse Rich Client Program application based on the open source project found at http:\/\/www.eclipse.org [http:\/\/www.eclipse.org]. Eclipse changed the window system requirement from motif to gtk on UNIX operating systems. For AIX, this Eclipse window system change requires the gtk libraries to be installed to support the GUI. For Installation Manager, the GUI is the wizard mode of operation. \n\nYou can use Installation Manager without the gtk libraries. For information on console mode, command-line mode, or silent mode; see the Installation Manager Information Center [http:\/\/pic.dhe.ibm.com\/infocenter\/install\/v1r6\/topic\/com.ibm.cic.agent.ui.doc\/topics\/c_modes.html]. Silent mode uses a response file and command-line mode is supported by all packages. For console mode, check your product documentation to verify that the product supports console mode.\n\n\nRESOLVING THE PROBLEM\nTo use the GUI, the gtk+ RPM and dependencies must be available on AIX. \n\n\nInstall this set of RPMs on AIX:\n\n\natk-1.12.3-2.aix5.2.ppc.rpm\ncairo-1.8.8-1.aix5.2.ppc.rpm\nexpat-2.0.1-1.aix5.2.ppc.rpm\nfontconfig-2.4.2-1.aix5.2.ppc.rpm\nfreetype2-2.3.9-1.aix5.2.ppc.rpm\ngettext-0.10.40-6.aix5.1.ppc.rpm\nglib2-2.12.4-2.aix5.2.ppc.rpm\ngtk2-2.10.6-4.aix5.2.ppc.rpm\nlibjpeg-6b-6.aix5.1.ppc.rpm\nlibpng-1.2.32-2.aix5.2.ppc.rpm\nlibtiff-3.8.2-1.aix5.2.ppc.rpm\npango-1.14.5-4.aix5.2.ppc.rpm\npixman-0.12.0-3.aix5.2.ppc.rpm\nxcursor-1.1.7-3.aix5.2.ppc.rpm\nxft-2.1.6-5.aix5.1.ppc.rpm\nxrender-0.9.1-3.aix5.2.ppc.rpm\nzlib-1.2.3-3.aix5.1.ppc.rpm\n\nThe installed RPMs must be of the minimum versions listed above.\n\nTo install the RPM versions specified above take the following steps: \n\n\n 1. Download the gtk2_bundle_v2.tar package [ftp:\/\/ftp.software.ibm.com\/aix\/freeSoftware\/aixtoolbox\/ezinstall\/ppc\/] (version 'v2') containing all the RPMs and the install script to a new directory. \n \n \n 2. Decompress the tar file. \n You can use the command tar -xvf gtk2_bundle_<version>.tar to decompress the file.\n \n \n 3. Open the decompressed directory gtk2_bundle_<version> and run the install.sh script.\n \n The script will check if the required RPMs are installed at the compatible level. If they are not, the script will prompt to install the compatible versions.\n \n \n 4. Verify the environment variable LIBPATH contains a path to the installed libraries. \n For example LIBPATH=\/opt\/freeware\/lib\/\n\n\nNote that if you download and install RPMs individually, we have found that the following libraries are incompatible: * glib2-2.14.6-2 and gtk2-2.10.6-5 \n\nRELATED INFORMATION\n#Unreadable characters in the GUI when using X11 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21661861]"}]},{"id":"DEV_Q203","question":"Why WebSphere Application Server transactions are rolled back with these StaleConnectionExceptions?\n\nWhy WebSphere Application Server transactions are rolled back with these StaleConnectionExceptions?\nMy transactions are rolled back and the following errors are seen in the WebSphere Application Server logs:\n\nConnectionEve A J2CA0056I: ........ ........ Connection reset:java.net.SocketException: Connection reset [15\/03\/04 1:04:33:046 JST] 00000024 SystemOut O INFO Error executing internal sql (executing callable statement) com.ibm.websphere.ce.cm.StaleConnectionException: IO?G??\u00f1[: Connection reset at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at \n...\nSee original exception message: ...... with SQL State : 08003 SQL Code : 17008 ..... .....\nCaused by: java.sql.SQLRecoverableException: .......DSRA0010E: SQL State : 08003 SQL Code : 17008","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q204","question":"Best WTX Version to Upgrade to\n\nWe're a longtime TSI \/ Mercator \/ Ascential \/ WTX user (1996) in the govt. sector and need to upgrade from v8.3.0.3 to remain under support. The project is very stable, limited to translating 270\/271 and similar proprietary formats with only about a dozen maps. Our upgrade will be in April, 2016. What stable WTX version would you folks recommend? ","answer":"IBM WebSphere\u00ae Transformation Extender V8.4.1.3 is now available through Passport Advantage.","is_impossible":false,"contexts":[{"filename":"swg21903101.txt","text":"Title: IBM WebSphere Transformation Extender V8.4.1.3 is available - United States\n\nText:\n8.4.1.3 NEWS\n\nABSTRACT\n May 15, 2015 \n\nIBM WebSphere\u00ae Transformation Extender V8.4.1.3 is now available through Passport Advantage.\n\nBuild ID: 8.4.1.3(14) \n\nCONTENT\n \n\nFix List WebSphere Transformation Extender V8.4.1.3 Fix List [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045607] \nMain Release Notes page WebSphere Transformation Extender product release notes [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27008337] \nWTX 8.4.1.3 Release Notes Release Notes for IBM WebSphere Transformation Extender V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045520] Release Notes for IBM WebSphere Transformation Extender for z\/OS V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27038485] Release Notes for IBM WebSphere Transformation Extender for Integration Servers V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045575] Release Notes for IBM WebSphere Transformation Extender Launcher Agent V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27040398] Release Notes for IBM WebSphere Transformation Extender for Launcher Hypervisor V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045686] Release Notes for IBM WebSphere Transformation Extender Secure Adapter Collection V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045670] Release Notes for IBM WebSphere Transformation Extender Documentation V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg27045648] \nWTX 8.4.1.3 Download Documents WebSphere Transformation Extender Design Studio V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24039974] WebSphere Transformation Extender with Command Server V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24039973] WebSphere Transformation Extender with Launcher V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24039999] WebSphere Transformation Extender with Launcher Hypervisor Edition V8.4.1.3 - AIX [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24039976] WebSphere Transformation Extender with Launcher Hypervisor Edition V8.4.1.3 - RHEL [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24040001] WebSphere Transformation Extender Launcher Agent V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24040000] WebSphere Transformation Extender for Application Programming V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24040002] WebSphere Transformation Extender for Integration Servers V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24040004] WebSphere Transformation Extender Secure Adapter Collection V8.4.1.3 [http:\/\/www.ibm.com\/support\/docview.wss?rs=2320&uid=swg24040003] \n\nIBM PassPort Advantage Online [http:\/\/www-01.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm]"}]},{"id":"DEV_Q205","question":"Launching IBM Rational Software Architect application results in Error: Java was started but returned exit code = -1\n\nAt times when you launch Rational Software Architect (RSA) application, you might encounter the following error: Error: Java was started but returned exit code = -1 ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q206","question":"Why does nco_confpack -export fail with the message \"Tool in menu but not found\"?\n\n\n\nI tried to export OMNIbus configuration using nco_confpack command and I get the following message:\n\nTool in menu but not found, menu: AlertsMenu, tool: Close\n\nI've also tried using it with -list command and I get the same error.\n\nWhy is this happening?","answer":"The menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.","is_impossible":false,"contexts":[{"filename":"swg21672071.txt","text":"Title: IBM Netcool conf pack command - United States\n\nText:\ntool; menu; not found; confpack TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Migrating to a new version of Omnibus, running nco_confpack:\n\n$OMNIHOME\/bin\/nco_confpack -list -server NCOMS -user ncadmin -file \/tmp\/nco_confpack.list \n\nReceived this error: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY. \n\nSYMPTOM\nThe command fails and the following error is received: Tool in menu but not found, menu: AlertsMenu, tool: CLEAR_LWY.\n\n\nCAUSE\nThe menu AlertsMenu has a tool in it called CLEAR_LWY, however the tool no longer exists.\n\nRESOLVING THE PROBLEM\nRecreate the tool and associate it with the menu and try to run the command again."}]},{"id":"DEV_Q207","question":"Improve Performance of Decision Validation Services (DVS) and Decision Warehouse\n\nHow can I improve the performance of Decision Validation Services (DVS) and Decision Warehouse? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q208","question":"Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task\n\nWhile attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task.\n\nThe ConfigTrace.log shows the following...\n\nimport-nodes:\n\n--- Exception Thrown --- C:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include s\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task execution failed with response code 404 due to exception : Not Found . Please check the server log for more information.\n","answer":"Please make the following change in the WAS Admin Console...\nApplications > WebSphere enterprise applications >\nJavaContentRepository > Target specific application status > Check the\nbox for the WebSphere_Portal server > Click Enable Auto Start > Save\nchanges > restart Portal\n\nAfter making this change please attempt the CF upgrade again.","is_impossible":false,"contexts":[{"filename":"swg21691034.txt","text":"Title: IBM Error TASK001X while upgrading Portal 8.0.0.1 to 8.0.0.1 CF14 during import-nodes sub-task - United States\n\nText:\nupgrade; TASK001X; import-nodes; 404 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nWhile attempting to upgrade Portal to CF14 the upgrade fails during the import-nodes sub-task.\n\nSYMPTOM\nThe ConfigTrace.log shows the following...\n\nimport-nodes:\n\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\n\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\nat org.apache.tools.ant.Task.perform(Task.java:364)\n\nat org.apache.tools.ant.Target.execute(Target.java:341)\n\nat org.apache.tools.ant.Target.performTasks(Target.java:369)\n\nat\norg.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)\n\nat\norg.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleChe\nckExecutor.java:37)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\n\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n\n... 75 more\n\n\nCAUSE\nThe customer had previously disabled the autostart on several applications to improve the Portal startup time\n\nENVIRONMENT\nPortal 8.0.0.1\nWindows\n\nDIAGNOSING THE PROBLEM\nfrom ConfigTrace.log...\n\nWed Nov 19 16:49:42 CST 2014\nTarget started: import-nodes\n\nimport-nodes:\n--- Exception Thrown ---\nC:\\Portal8\\PortalServer\\jcr\\wp.content.repository.install\\config\\include\ns\\jcr.install_cfg.xml:826: com.ibm.icm.jcr.task.TaskException:\nTASK001X: Remote task execution failed with response code 404 due to\nexception : Not Found . Please check the server log for more\ninformation.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n840)\nat\norg.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)\n\n...\n\nCaused by: com.ibm.icm.jcr.task.TaskException: TASK001X: Remote task\nexecution failed with response code 404 due to exception : Not Found .\nPlease check the server log for more information.\nat\ncom.ibm.icm.jcr.task.AbstractRemoteTask.execute(AbstractRemoteTask.java:\n825)\n... 75 more\n\nFrom here I reviewed the SystemOut.log at the same timestamp and see\nthe following...\n\n[11\/19\/14 16:49:43:804 CST] 00000042 filter E\ncom.ibm.ws.webcontainer.filter.FilterInstanceWrapper doFilter\nSRVE8109W: Uncaught exception thrown by filter Extensible Filter:\njava.io.FileNotFoundException: SRVE0190E: File not found:\n\/jcr\/remotetask\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor._processEDR(\nDefaultExtensionProcessor.java:893)\nat\ncom.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.processEDR(D\nefaultExtensionProcessor.java:874)\n\nBoth of these messages seems to indicate a problem with the WCM\nstartup. This code is contained in the following\napplication....JavaContentRepository.ear.\n\nLooking at your last Portal startup I saw this below which occurs\nduring the wcm application startup....\n\n[11\/19\/14 15:57:54:566 CST] 00000009 ApplicationMg A WSVR0200I:\nStarting application: wcm\n\n....\n\n[11\/19\/14 16:00:36:812 CST] 00000005 TimeoutManage I WTRN0006W:\nTransaction\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000149CA10760B000000012830B348BBD991CDC4031D0DFCED27CDD500F13F7FC95B79\n00000001 has timed out after 120 seconds.\n[11\/19\/14 16:00:36:831 CST] 00000005 TimeoutManage I WTRN0124I: When\nthe timeout occurred the thread with which the transaction is, or was\nmost recently, associated was Thread[server.startup : 0,5,main]. The\nstack trace of this thread when the timeout occurred was:\njava.lang.Thread.blockedOn(Thread.java:1076)\nsun.reflect.GeneratedMethodAccessor21.invoke(Unknown Source)\nsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcce\nssorImpl.java:37)\njava.lang.reflect.Method.invoke(Method.java:611)\n\nKnowing this I further reviewed the SystemOut.log to see where the JCR\nweb module gets loaded during startup....it should begin like this...\n\nSRVE0169I: Loading Web Module: JCRContentRepository.\n\nYour startup does not have this. This prompted me to review the\ndeployment.xml from the JavaContentRepository application directory at\nthis location...\n\nPortal8\/wp_profile\/config\/cells\/C001389391Cell\/applications\/JavaContentR\nepository.ear\/deployments\/JavaContentRepository\/deployment.xml\n\nThe contents show the following...\n\n<targetMappings xmi:id=\"DeploymentTargetMapping_1335003370698\"\nenable=\"false\" target=\"ServerTarget_1335003370698\"\/>\n\nThe enable=false means that you have this application set to not\nautostart. Because of this it is not starting during Portal startup\nand therefore is not available when the config task attempts to\ncommunicate with it during the upgrade...and therefore causes the\nproblem.\n\nRESOLVING THE PROBLEM\nPlease make the following change in the WAS Admin Console...\nApplications > WebSphere enterprise applications >\nJavaContentRepository > Target specific application status > Check the\nbox for the WebSphere_Portal server > Click Enable Auto Start > Save\nchanges > restart Portal\n\nAfter making this change please attempt the CF upgrade again."}]},{"id":"DEV_Q209","question":"How to change the maximum string length for properties in FileNet Administration Console for Content Engine (ACCE)\n\nI am trying to change the maximum string length in ACCE like we do in FileNet Enterprise Manager, but in the more Tab, I am not seeing the option. In this case, how can I change it? ","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","is_impossible":false,"contexts":[{"filename":"swg21696083.txt","text":"Title: IBM How to overwrite property definition properties in a class via IBM Administration Console for Content Platform Engine (ACCE)? - United States\n\nText:\nACCE; CE; Property; FEM TECHNOTE (FAQ)\n\nQUESTION\n With IBM FileNet Enterprise Manager (FEM), we can follow the steps below to overwrite the property definition in a document class\n\n1. Launch FEM\n2. Expand the object store and document class tree. Right click on the document class and select \"Properties\"\n3. Go to \"Properties Definitions\" tab, highlight the property definition and click \"Edit\"\n4. Make the modification and click OK\n5. Click OK again to save the change\n\nHow to perform the same operation with FileNet Content Engine - ACCE? \n\nANSWER\nFollow the below steps to update the property definition properties on ACCE: \n\n\n\n\n 1. Launch ACCE \n 2. Expand the object stores folder and click the object store to open the Object store tab \n 3. Expand the Data Design folder and Classes folder. Click the document class to open Document Class tab \n 4. From Properties tab, open Property Definitions drop down and select the property definition you want to modify \n 5. ACCE will open that property definition in a new Properties tab \n 6. Modify the property definition as required \n 7. Go back to the Class Definition tab and click Save"}]},{"id":"DEV_Q210","question":"startNode failed with ADML3000E after a deployment failure\n\nClient had a deployment failure due to \"Too many open files\" error.\n\nAfterwards, the startNode failed with ADML3000E:\n\nWhat could cause the \"Too many open files error?","answer":"When the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application.","is_impossible":false,"contexts":[{"filename":"swg21067352.txt","text":"Title: IBM Too Many Open Files error message - United States\n\nText:\nwasrun; wasjdk; open; files; too; ProblemDeterminationDocument; JCC was appserver app server TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This technote explains how to debug the \"Too many open files\" error message on Microsoft Windows, AIX, Linux and Solaris operating systems. \n\nSYMPTOM\nThe following messages could be displayed when the process has exhausted the file handle limit: \n\njava.io.IOException: Too many open files\n\n[3\/14\/15 9:26:53:589 EDT] 14142136 prefs W Could not lock User prefs. Unix error code 24.\n\nNew sockets\/file descriptors can not be opened after the limit has been reached. \n\n\nCAUSE\nSystem configuration limitation.\n\nWhen the \"Too Many Open Files\" error message is written to the logs, it indicates that all available file handles for the process have been used (this includes sockets as well). In a majority of cases, this is the result of file handles being leaked by some part of the application. This technote explains how to collect output that identifies what file handles are in use at the time of the error condition.\n\n\nRESOLVING THE PROBLEM\n\n\n\n\nDetermine Ulimits\n\nOn UNIX and Linux operating systems, the ulimit for the number of file handles can be configured, and it is usually set too low by default. Increasing this ulimit to 8000 is usually sufficient for normal runtime, but this depends on your applications and your file\/socket usage. Additionally, file descriptor leaks can still occur even with a high value. \n\nDisplay the current soft limit:\nulimit -Sn\n\nDisplay the current hard limit:\nulimit -Hn\n\nOr capture a Javacore, the limit will be listed in that file under the name NOFILE:\nkill -3 PID\n\n\nPlease see the following document if you would like more information on where you can edit ulimits:\nGuidelines for setting ulimits (WebSphere Application Server)\nhttp:\/\/www.IBM.com\/support\/docview.wss?rs=180&uid=swg21469413 [http:\/\/www.ibm.com\/support\/docview.wss?rs=180&uid=swg21469413]\n\n\nOperating Systems \n\nWindows By default, Windows does not ship with a tool to debug this type of problem. Instead Microsoft provides a tool that you can download called Process Explorer [http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb896653]. This tool identifies the open handles\/files associated with the Java\u2122 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"}]},{"id":"DEV_Q211","question":"You want to know how to make persistent the events that indicate when a queue manager has started and stopped.\n\nYou want to know how to make persistent the events that indicate when a queue manager has started and stopped.","answer":"First, a baseline scenario is described in which when using the defaults, there is only 1 record in the SYSTEM.ADMIN.QMGR.EVENT queue, regardless of how many times you restart the queue manager.\n\n\nSecond, a modification is done to the SYSTEM.ADMIN.QMGR.EVENT queue to indicate that the default persistence is enabled, and thus, subsequent events from the stop\/start of the queue manager will be kept in the queue.\nalter ql(SYSTEM.ADMIN.QMGR.EVENT) defpsist(YES)","is_impossible":false,"contexts":[{"filename":"swg27050154.txt","text":"Title: IBM How to make persistent the events for starting and stopping an MQ queue manager - United States\n\nText:\n WHITE PAPER\n\nABSTRACT\n This techdoc provides all the necessary steps to help you monitor the queue SYSTEM.ADMIN.QMGR.EVENT to audit the start and the stop for a MQ queue manager. \n\nCONTENT\nFirst, a baseline scenario is described in which when using the defaults, there is only 1 record in the SYSTEM.ADMIN.QMGR.EVENT queue, regardless of how many times you restart the queue manager.\n\n\nSecond, a modification is done to the SYSTEM.ADMIN.QMGR.EVENT queue to indicate that the default persistence is enabled, and thus, subsequent events from the stop\/start of the queue manager will be kept in the queue.\nalter ql(SYSTEM.ADMIN.QMGR.EVENT) defpsist(YES)\n\nCaveat:\nIf you want to have persistent messages in the SYSTEM.ADMIN.QMGR.EVENT queue you will need to have discipline and a procedure to get and remove the messages, otherwise, the queue will eventually fill up.\n\n\n\nFile: How to make persistent the events for starting and stopping an MQ queue manager.pdf \n\nHow to make persistent the events for starting and stopping an MQ queue manager.pdf [\/support\/docview.wss?uid=swg27050154&aid=2]How to make persistent the events for starting and stopping an MQ queue manager.pdf [\/support\/docview.wss?uid=swg27050154&aid=1]\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM MQ Capability AIX, HP-UX, Linux, Solaris, Windows 9.0, 8.0, 7.5"}]},{"id":"DEV_Q212","question":"Datacap 9.0.1 Application Manager not saving database configs\n\n\n\nHi All,\n\n \nI have installed Datacap 9.0.1 and there is a issue of not connecting to Admin and engine DB with Datacap 9.0.1.\n \nThe problem is there for saving admin and engine db configurations.\n \nWhen selected the path it saves but after tab out and tab in it clears admin and engine DB configurations.\n \nEven I tried with exporting and importing keys but no luck.\nRepair and re-install of Datacap is also done but no luck.\n \nPlease let me know if any of had faced similar kind of issue and any solution for it.\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q213","question":"Can I migrate or convert Workplace XT created Search Templates to Content Navigator?\n\nWhen migrating from Workplace XT to Content Navigator, can I covert or migrate XT created search templates to the ICN version of managed search templates?","answer":"Workplace XT created search templates are also supported in ICN with the restriction that the search template cannot be edited in ICN.","is_impossible":false,"contexts":[{"filename":"swg21648471.txt","text":"Title: IBM Does IBM Content Navigator support Workplace XT created stored searches and search templates? - United States\n\nText:\nstored search; search template; WPXT; Workplace XT; ICN; navigator; IBM Content Navigator TECHNOTE (FAQ)\n\nQUESTION\n Does IBM Content Navigator support Workplace XT created stored searches and search templates? \n\nANSWER\nWorkplace XT created stored searches are supported in IBM Content Navigator (ICN). \nICN can be used to only run these stored searches with the following restriction: \n- stored searches that return both documents and folders are not supported.\nThese stored searches cannot be edited in ICN.\n\nWorkplace XT created search templates are also supported in ICN with the restriction that the search template cannot be edited in ICN.\n\nPlease also note that ICN can only create native search templates, but not stored searches."}]},{"id":"DEV_Q214","question":"Why is my PDWDB flooded with irrelevant tracking data which is not related to process instances ?\n\nMy PDWDB does show a huge amount of data residing on the PDWDB table\/view for TASKS. Most of the data does only have an ID and is not related to process instances ? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q215","question":"When should I use conversation sharing in DataPower MQ queue managers?\n\nMQ version 7.0 introduced a new feature, conversation sharing. Are there any special values on DataPower when configuring conversation sharing?","answer":"The default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is \nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.","is_impossible":false,"contexts":[{"filename":"swg21647231.txt","text":"Title: IBM When to enable Conversation Sharing in DataPower MQ Queue Manager (mq-qm) object - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When to enable Sharing Conversations in DataPower MQ Queue Manager (mq-qm) object along with SHARECNV attribute of the MQ SVRCONN channel? \n\nRESOLVING THE PROBLEM\nIBM WebSphere MQ server version 7.0 and later releases provide sharing conversations (SHARECNV) attribute on SVRCONN channel that specifies the maximum number of conversations that can share each TCP\/IP channel instance. This feature can be configured in DataPower as it uses client connection with queue manager SVRCONN channel. \nThe default setting of sharing conversations (SHARECNV) value is zero in DataPower mq-qm object. The same default value for MQ SVRCONN channel is 10. The sharing conversations value is \nnegotiated between MQ server and DataPower and the lower value takes effect. However, in current versions of the DataPower firmware, the sharing conversations setting of 1 is treated as 0 when negotiating with MQ server.\n\nThere are three use cases to configure Sharing Conversations in DataPower mq-qm object: \n\nCase #1 : The negotiated sharing conversations value is 0 - The channel runs in a mode similar to WebSphere MQ V6 and does not uses features such as\n\n\u00b7 Administrator stop-quiesce\n\u00b7 Heartbeating \n\u00b7 Read ahead \n\u00b7 Client asynchronous consume\n\nSet a value of 0 or 1 on the Sharing Conversations attribute of the mq-qm object in DataPower to disable sharing conversations regardless of the IBM WebSphere MQ SVRCONN setting.\n\nCase #2: The negotiated sharing conversations value is 1 - The channel supports IBM WebSphere MQ V7 and later release features as outlined in case #1, but each TCP\/IP channel instance has a single conversation.\n\nSet a value of 1 on the Sharing Conversations attribute and select \"on\" in Share Single Conversation attribute of the mq-qm object in DataPower as shown in the following picture and a value of 1 on IBM WebSphere MQ SVRCONN setting.\n\nThe Share Single Conversation attribute is only visible when \"Sharing Conversations\" is configured with value of \"1\" and then <RETURN> key is entered. For values greater than 1, the \"Share Single Conversation\" attribute is hidden in the mq-qm object.\n[\/support\/docview.wss?uid=swg21647231&aid=1] [\/support\/docview.wss?uid=swg21647231&aid=1] \n\nCase #3: The negotiated sharing conversations value is 2 or more - The channel supports IBM WebSphere MQ 7 and later release features and each TCP\/IP channel instance supports 2 or more conversations.\n\nSet a value of 2 or more on the Sharing Conversations attribute of the mq-qm object in DataPower and on the MQ SVRCONN channel.\n\nOn average, processing of messages from client applications is 15 percent slower when using SHARECNV(10) as compared to SHARECNV(0). Please refer to Performance Implications of Sharing [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.csqzaf.doc\/mi12240_.htm]\nConversations on Client-connection Channels. [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSFKSJ_7.0.1\/com.ibm.mq.csqzaf.doc\/mi12240_.htm].\n\nSince DataPower uses a connection pool in processing MQ messages, there are no additional benefits of using sharing conversations with the mq-qm object. However, in situations when mixed message sizes are used by the same mq-qm object, using case #2 will benefit mq-qm object as it will use new buffer management feature of IBM WebSphere MQ Version 7 when making MQGET API call.\n\nWhen using a negotiated shared conversations value of 0 as in case #1, mq-qm object uses maximum message size as the buffer pool for the MQGET API call. However, when mixed message sizes are processed by the same MQ Front Side Handler (FSH), it requests buffer pool based on maximum message size configured in the mq-qm object. The use of fixed buffer pool for small and large messages can deplete MQ server's allocated buffer and contribute to unexpected termination of MQ SVRCONN channel instance and may terminate the queue manager. In such a situation, using a negotiated sharing conversations value of 1 as in case #2 will benefit DataPower mq-qm object as it will use IBM WebSphere MQ Version 7 Read Ahead feature and the new buffer management feature for MQGET API call. IBM WebSphere MQ V8 release provides enhanced performance for case #2, when the negotiated sharing conversations value is 1.\n\nFor DataPower firmware releases 7.0.0.x, 7.1.0.x, 7.2.0.x and earlier, one should follow case #1 and use a negotiated sharing conversations value of 0. If you configure these firmware versions with case #2 or case #3, DataPower device may reload or hang due to connection instability and generate many MQ errors with Reason Code - 2009 and 2059. \n\nCases #2 and #3 can be used in firmware releases 7.5.0.x, 7.5.1.x and later. We suggest to use a value of 10 or less in Sharing Conversations attribute of the mq-qm object and verify the configuration empirically to make sure that IBM WebSphere MQ server can sustain load from DataPower with the negotiated Sharing Conversations of 10.\n\nNote: In order to use sharing conversations, make sure you have applied APAR IV24821 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg1IV24821] (\"Client C application process hangs after cancelling thread\") to the IBM WebSphere MQ server. IV24821 is included in IBM WebSphere MQ V7.0.1.10 and later, IBM WebSphere MQ V7.1.0.3 and later, IBM WebSphere MQ V7.5.0.1 and later, and IBM WebSphere MQ V8.\n\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the distributed platform.\n\nrunmqsc <qmgr>\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n\ndisplay chs(CHANNEL3) maxshcnv curshcnv\n1 : display chs(CHANNEL3) maxshcnv curshcnv\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.x1.x2.x3) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(1) MAXSHCNV(1) <---- Negotiated Sharing Conversations value of 1\nAMQ8417: Display Channel Status details.\nCHANNEL(CHANNEL3) CHLTYPE(SVRCONN)\nCONNAME(9.y1.y2.y31) CURRENT\nSTATUS(RUNNING) SUBSTATE(RECEIVE)\nCURSHCNV(0) MAXSHCNV(0) <---- Negotiated Sharing Conversations value of 0\n\nend\n--------------------------------------------------------------------------------------------------------------------------------------------\nIn order to identify the negotiated Sharing Conversations status, the following MQ commands are used in the z\/OS System.\n\n\n\nconnect to <qmgr>\nOn z\/OS system, options for issuing the commands are described at http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.ref.adm.doc\/q085120_.htm [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSFKSJ_8.0.0\/com.ibm.mq.ref.adm.doc\/q085120_.htm]. \n\/+RTP8 DIS CHSTATUS(channel_name) MAXSHCNV CURSHCNV\nwhere \"+RTP8\" is the command prefix."}]},{"id":"DEV_Q216","question":"Error message 1311 when attempting to install SPSS 23 on Windows 10.\n\n\n\nI have downloaded SPSS 23 onto a Windows 10 operating system. The computer previously had SPSS, however the computer crashed and SPSS needs be installed on the new operating system. When trying to install the program the following error message appears Error 1311. Source file not found.\n\nScreenshot attached.\nerror-messg.png (50.7 kB)","answer":"Stop the installation. Extract all of the files in the compressed (.zip file) to a new folder, and run the installer executable ('setup.exe') from that new folder.","is_impossible":false,"contexts":[{"filename":"swg21480262.txt","text":"Title: IBM During installation IBM SPSS product(s) displays message including 1311. - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n You received product installation media in the form of a compressed file (.zip). During installation an error presents with the following content \n\n\"Error 1311. Source file not found\" and the installation does not continue. \n\nSYMPTOM\n'Error 1311. Source file not found' during installation.\n\n\nCAUSE\nOperating systems allow opening compressed (zip) files without extracting them. Some required files are not automatically extracted and are not available to be used during the installation process.\n\nRESOLVING THE PROBLEM\nStop the installation. Extract all of the files in the compressed (.zip file) to a new folder, and run the installer executable ('setup.exe') from that new folder.\n\n\n\nMicrosoft Windows operating systems\n(1) Right-click the compressed file (.zip).\n(2) Select the 'Extract All' drop-menu option.\n(3) Select the 'Extract' button.\n(4) When complete, a (new) folder containing the extracted (decompressed) files will appear in the same location as the compressed (zip) file.\n(5) Run the product installer from the (new) folder containing the extracted (decompressed) files according to the product installation instructions. \n\n \n\n Macintosh operating systems\n(1) Right-click (Control+click) on the compressed file (.zip).\n(2) Select the 'Open With' drop-down menu option.\n(3) Select 'Archive Utility' from the available options. \n(4) The Archive Utility window displays with a progress bar.\n(5) When complete, a new folder will contain the extracted (decompressed) files in the same location as the compressed file (.zip).\n(6) Run the product installer from the new folder which contains the extracted (decompressed) files.\n\nRELATED INFORMATION\n Need more help? Our Statistics forum is Live! [https:\/\/developer.ibm.com\/answers\/topics\/statistics.html?smartspace=predictive-analytics]\n\n\n\n\nHISTORICAL NUMBER\n 76802"}]},{"id":"DEV_Q217","question":"What process do i neet to follow to upgrade our SPSS Modeler deployment (concurrent license) from v16 to v18?\n\nWe have 5 users with SPSS Modeler 16 installed using the Concurrent license manager supplied for that version. We need to upgrade to v18. Do we need to upgrade the license manager as well? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q218","question":"Why is MQ pattern showing installed MQ version as 8.0.0.2, instead of 8.0.0.4 when client tries to deploy pattern at the MQ 8.0.0.4 version in PureApplication System?\n\nIn the pattern, it was clearly showing MQ version 8.0.0.4. After deployment, client checked the MQ version on the Virtual Machine and it shows 8.0.0.2 instead.\n","answer":"A new maintenance.py lifecycle script is available to enable installation and migration of the latest maintenance level of IBM MQ contained in the pattern-type.","is_impossible":false,"contexts":[{"filename":"swg21984588.txt","text":"Title: IBM MQ 8.0.0.4 FAILS TO INSTALL ON CERTAIN IBM PURE APPLICATION SYSTEM LEVELS - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Users observe errors when attempting to install or migrate to IBM MQ 8.0.0.4 using IBM Pure Application System. \n\nSYMPTOM\nUsers observe errors when attempting to install or migrate to IBM MQ 8.0.0.4 using the following levels of IBM Pure Application System: \n\n * 2.1.2.0 \n * 2.2.0.0 and later\n\n\n\nThis affects users with IBM MQ Pure Application System pattern-types 1.0.0.2 and earlier. \nCAUSE\nBecause of an interface change in IBM Pure Application System 2.1.2.0, and in 2.2.0.0 and greater, installation and upgrade of IBM MQ at the latest maintenance level contained in the pattern-type fails. The installation appears to succeed, but IBM MQ 8.0.0.2 is installed and the subsequent fixpack update is not applied. This affects IBM MQ Pure Application System pattern-types 1.0.0.2 and earlier, leading to the following restrictions: \n\n * For IBM Pure Application System releases earlier than 2.1.2.0 and at version 2.1.2.1, you can install all versions of IBM MQ contained in the pattern-type. You can also apply maintenance to running pattern instances. \n * For IBM Pure Application System 2.1.2.0, 2.2.0.0 and later, you can install IBM MQ 8.0.0.2 only. You cannot install later versions e.g., 8.0.0.4. You cannot apply maintenance to running pattern instances.\n\nRESOLVING THE PROBLEM\nA new maintenance.py lifecycle script is available to enable installation and migration of the latest maintenance level of IBM MQ contained in the pattern-type. \n\n\nThis update, and installation steps, can be obtained from IBM Fix Central:\n\nhttp:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0&platform=All&function=fixId&fixids=1.0.0.2-WS-MQ-Pure-LAIT15252&includeSupersedes=0&source=fc [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=8.0&platform=All&function=fixId&fixids=1.0.0.2-WS-MQ-Pure-LAIT15252&includeSupersedes=0&source=fc]\n\n\nAPAR IT15252 has been raised for the IBM MQ development team to address this issue within future releases of the IBM MQ Pure Application System pattern-type."}]},{"id":"DEV_Q219","question":"Big increase in the amount of trace spool data from TSAMP\n\nRecently it was noticed that our trace spool directories were filling up much quicker. There are thousands of refreshOpState messages in the trace files. What is causing all these messages all of a sudden ? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q220","question":"Help with Security Bulletin: TLS padding vulnerability affects IBM PureApplication System (CVE-2014-8730)\n\nI need to understand details regarding \"Security Bulletin: TLS padding vulnerability affects IBM PureApplication System (CVE-2014-8730)\". Where can I find this information? ","answer":"CVEID: CVE-2014-8730 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-8730]\nDESCRIPTION: IBM PureApplication Server bundles IBM HTTP Server, which could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plain text of secure connections.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99216 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99216] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (AV:N\/AC:M\/Au:N\/C:P\/I:N\/A:N)","is_impossible":false,"contexts":[{"filename":"swg21960375.txt","text":"Title: IBM Security Bulletin: TLS padding vulnerability affects IBM PureApplication System (CVE-2014-8730) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n Transport Layer Security (TLS) padding vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack affects IBM PureApplication System. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2014-8730 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2014-8730]\nDESCRIPTION: IBM PureApplication Server bundles IBM HTTP Server, which could allow a remote attacker to obtain sensitive information, caused by the failure to check the contents of the padding bytes when using CBC cipher suites of some TLS implementations. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) like attack to decrypt sensitive information and calculate the plain text of secure connections.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99216 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/99216] 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\n\nThis vulnerability affects all versions and releases of IBM HTTP Server (powered by Apache) component in all editions of WebSphere Application Server and bundling products. IBM PureApplication Server bundles WebSphere Application Server in its Web Application Pattern.\n\nIBM PureApplication System V1.1\nIBM PureApplication System V2.0\nIBM PureApplication System V2.1\n\nREMEDIATION\/FIXES\nThe solution is to apply an update to the Web Application pattern type included in IBM PureApplication System:\n\nIBM PureApplication System V2.1 \n\n * \n * \n * http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=2.1.0.1&platform=All&function=fixId&fixids=webapp-2.0.4.1-sys&includeSupersedes=0\n * \n * \n * \n * \n * http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=2.1.0.1&platform=All&function=fixId&fixids=webapp-1.0.4.1-sys&includeSupersedes=0\n\n\nIBM PureApplication System V2.0 \n\n * \n * \n * http:\/\/www-933.ibm.com\/support\/fixcentral\/swg\/downloadFixes?parent=PureSystems&product=ibm\/WebSphere\/PureApplication+System&release=2.0.0.1&platform=All&function=fixId&fixids=webapp-2.0.2.1-vaea-20150610&includeSupersedes=0\n\n\nIBM PureApplication System V1.1 and earlier: \n\n * \n * \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 19 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."}]},{"id":"DEV_Q221","question":"App Connect Professional (formerly Cast Iron) Studio not launching\n\nWhen trying to start App Connect Professional (formerly Cast Iron) Studio tool, the application appears but after few seconds it crashes with no error message or warning. ","answer":"Start the Studio through the command line interface using the following command: \n\n\nCastIronStudio.exe -J-Xmx1024m \n\n\nIn this command, \"1024\" is the new memory size that will be allocated to the Studio instead of the default value of 512. This numeric value is in MB.","is_impossible":false,"contexts":[{"filename":"swg21452870.txt","text":"Title: IBM Increasing size of heap memory allocated to Cast Iron Studio - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I increase the size of the heap memory allocated to the Cast Iron Studio? \n\nANSWER\nStart the Studio through the command line interface using the following command: \n\n\nCastIronStudio.exe -J-Xmx1024m \n\n\nIn this command, \"1024\" is the new memory size that will be allocated to the Studio instead of the default value of 512. This numeric value is in MB. \n\nNote: There are no benchmark figures on the max value for a given machine configuration that is supported as max memory by Studio. Use garbage collection from Studio to free up unused space, Also, try XML Schema preference settings and see if the use of memory is within the default value of 520 MB or a permissible increased value.\n\nFor additional questions related to Increasing heap memory size, open a service request with IBM Cast Iron Support. More information about using the IBM Service Request tool is available here [http:\/\/www-01.ibm.com\/software\/support\/servicerequest\/quick_start.html].\n\n \n\nHISTORICAL NUMBER\n 00001529 \n\nPRODUCT ALIAS\/SYNONYM\n Cast Iron Solution\nCast Iron Operating System\nCast Iron Studio"}]},{"id":"DEV_Q222","question":"Help with Action required for IIB H.E. V9 & WMB H.E. V8 for security vulnerabilities in Red Hat Linux\n\n\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\nThis is related to CVEID: CVE-2017-16546\n\nWhere can I find this information?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q223","question":"Can I use Chrome browser for viewing Monitor 801 Cognos report viewer widget ?\n\nSome users use Chrome browser with Business Monitor and have reported issues when trying to view Cognos reports from Report Viewer widget within Business Space.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q224","question":"How do we set HttpOnly and secure flag in Oracle Weblogic 12c to secure IBM Atlas?\n\nHow do we set HttpOnly and secure flag in Oracle Weblogic 12c to secure IBM Atlas? ","answer":"Perform steps as mentioned below:\n\n1. Undeploy any existing PolicyAtlas deployments using Oracle Weblogic console\n\n2. Open the PolicyAtlas.ear file using a tool like 7zip or similar and update weblogic.xml file with the changes below:\n\n\n<wls:session-descriptor>\n<wls:cookie-secure>true<\/wls:cookie-secure>\n<wls:cookie-http-only>true<\/wls:cookie-http-only>\n<wls:url-rewriting-enabled>false<\/wls:url-rewriting-enabled>\n<\/wls:session-descriptor>\n\n3. Save the changes by updating the ear file.\n\n4. Redeploy the updated ear file using Oracle Weblogic console","is_impossible":false,"contexts":[{"filename":"swg21696267.txt","text":"Title: IBM Setting HttpOnly and secure flag in Oracle Weblogic 12c - United States\n\nText:\nweblogic; weblogic.xml; secure cookies Atlas TECHNOTE (FAQ)\n\nQUESTION\n How do we set HttpOnly and secure flag in Oracle Weblogic 12c to secure IBM Atlas? \n\nCAUSE\nTo prevent session hijacking and securing the cookie\n\nANSWER\n \n\nPerform steps as mentioned below:\n\n1. Undeploy any existing PolicyAtlas deployments using Oracle Weblogic console\n\n2. Open the PolicyAtlas.ear file using a tool like 7zip or similar and update weblogic.xml file with the changes below:\n\n\n<wls:session-descriptor>\n<wls:cookie-secure>true<\/wls:cookie-secure>\n<wls:cookie-http-only>true<\/wls:cookie-http-only>\n<wls:url-rewriting-enabled>false<\/wls:url-rewriting-enabled>\n<\/wls:session-descriptor>\n\n3. Save the changes by updating the ear file.\n\n4. Redeploy the updated ear file using Oracle Weblogic console"}]},{"id":"DEV_Q225","question":"Non-admin users cannot access webDAV filestore. What is the likely reason?\n\n\n\nA non-admin user trying to access the webDAV filestore is unable to do so and they see the below exception in the portal logs:\n\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":"Authenticated user does not have the attribute defined in the backend user registry which matches the attribute defined in the store.puma_default.user.fbadefault.filter property in WP PumaStoreService Resource Environment Provider.","is_impossible":false,"contexts":[{"filename":"swg21664629.txt","text":"Title: IBM Policy (EJQAB0067E) and JCR Login (WSP0005E) exceptions in System*.logs - United States\n\nText:\nEJQAB0067E; WSP0005E; LoginException; policy; theme; attribute; JCR TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nPolicy (EJQAB0067E) and JCR Login (WSP0005E) exceptions occur in the System* logs when accessing Portal pages after user authentication.\n\nSYMPTOM\nSystemOut.log shows:\n\n[datestamp] 00000241 PolicyService E com.ibm.wps.policy.services.PolicyService getPolicy Exception calling storage api: com.ibm.portal.WpsException: EJQAB0067E: An error occurred while getting the policy root. \n[datestamp] 00000241 PolicyManager E com.ibm.wps.policy.services.PolicyManagerServerSideImpl getPVSByPath throwing exception. PVS type not found for theme\/SingleTopNav\n\nSystemErr.log shows:\n\n[datestamp] 00000241 SystemErr R javax.jcr.LoginException: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.: WSP0005E: Error calling IConnectionManager.logon() for reason: User id can not be null.\n....\n[datestamp] 00000241 SystemErr R Caused by: com.ibm.icm.da.DBAccessException: User id can not be null\n[datestamp] 00000241 SystemErr R at com.ibm.icm.da.portable.connection.Logon.logon(Logon.java:177)\n\n\nCAUSE\nAuthenticated user does not have the attribute defined in the backend user registry which matches the attribute defined in the store.puma_default.user.fbadefault.filter property in WP PumaStoreService Resource Environment Provider. Such attribute is used by JCR when querying for theme policy information.\n\nDIAGNOSING THE PROBLEM\nCollect the following: \n\n * LDIF export of a sample user that hits this problem (if the backend user registry is LDAP) * If you cannot determine a specific user causing the error, you can use the following tracestring to confirm:\n \n *=info:com.ibm.wps.policy.services.*=finest:com.ibm.wps.policy.commands.*=finest\n \n Then look for the following line in trace.log: com.ibm.wps.policy.services.PolicyService PolicyService() ENTRY userid contructor: {DN of user} \n \n \n * Resources.xml - can be found under * <wp_profile>\/config\/cells\/<cellname>\/clusters\/<clustername>\/ for cluster \n * <wp_profile>\/config\/cells\/<cellname>\/nodes\/<nodename>\/servers\/<portalservername>\/ for standalone\n \n \n\nLocate the WP PumaStoreService Resource Environment Provider in resources.xml and confirm if there is a defined property name for store.puma_default.user.fbadefault.filter. If not, then the default and active value for such property is \"uid\". If it does exist, then verify the attribute defined for the value. Then check the LDIF export for the user to confirm if such attribute is defined. \nRESOLVING THE PROBLEM\nCreate\/update the store.puma_default.user.fbadefault.filter custom property for the WP PumaStoreService Resource Environment Provider via the Integrated Solutions Console to an attribute that exists for all Portal users in the backend user registry (for example, \"cn\").\n\nRELATED INFORMATION\n#Puma Store Service [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Puma_Store_Service_wp8]\nSetting service configuration properties [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/Setting_service_configuration_properties_wp8?OpenDocument&sa=true]"}]},{"id":"DEV_Q226","question":"How to check IBM Java ORB build version in WebSphere Application Server?\n\nJust a simple question:How to check IBM Java ORB build version in WebSphere Application Server?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q227","question":"Is Java 7 supported for BPM?\n\nWhat versions of BPM support Java 7?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q228","question":"javax.xml.bind.UnmarshalException org.xml.sax.SAXParseException: The reference to entity must end with the ; delimiter.\n\n\n\nAfter an upgrade from JRules to ODM we are receiving errors because of an ampersand in our data. This used to work before.\n\nCaused by: javax.xml.bind.UnmarshalException\n- with linked exception: [org.xml.sax.SAXParseException: The reference to entity \"NIGHT\" must end with the ; delimiter.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q229","question":"Can I hide left menu pane for specific application?\n\nIs it possible to disable the left navigation pane menu for certain application? ","answer":"You can include systemnav=\"false\" in the application presentation XML in order to disable the left navigation pane. \n\nThe following changes in the incident.xml file will disable the left navigation menu pane of the Incident application. \n\nEdit the incident.xml from :- \n\n<presentation apphelp=\"com.ibm.tusc.doc,incident\/incident.html\" beanclass=\"com.ibm.tsd.pminc.webclient.beans.PmIncidentAppBean\" id=\"incident\" mboname=\"INCIDENT\" orderby=\"TICKETID\" resultstableid=\"results_showlist\" version=\"7.1.0.0\"> \n\nto :- \n\n<presentation apphelp=\"com.ibm.tusc.doc,incident\/incident.html\" beanclass=\"com.ibm.tsd.pminc.webclient.beans.PmIncidentAppBean\" id=\"incident\" mboname=\"INCIDENT\" orderby=\"TICKETID\" resultstableid=\"results_showlist\" version=\"7.1.0.0\" systemnav=\"false\">\n\nImport back the incident.xml and save. With this configuration, the left Navigation Pane menu is no longer visible in the Incident application.","is_impossible":false,"contexts":[{"filename":"swg21609958.txt","text":"Title: IBM Hide left menu pane for specific application - United States\n\nText:\nTPAESCCD; menu; navigation; hide; disabled; systemnav TECHNOTE (FAQ)\n\nQUESTION\n How to disable the left navigation pane menu of an application? \n\nANSWER\nYou can include systemnav=\"false\" in the application presentation XML in order to disable the left navigation pane. \n\nThe following changes in the incident.xml file will disable the left navigation menu pane of the Incident application. \n\nEdit the incident.xml from :- \n\n<presentation apphelp=\"com.ibm.tusc.doc,incident\/incident.html\" beanclass=\"com.ibm.tsd.pminc.webclient.beans.PmIncidentAppBean\" id=\"incident\" mboname=\"INCIDENT\" orderby=\"TICKETID\" resultstableid=\"results_showlist\" version=\"7.1.0.0\"> \n\nto :- \n\n<presentation apphelp=\"com.ibm.tusc.doc,incident\/incident.html\" beanclass=\"com.ibm.tsd.pminc.webclient.beans.PmIncidentAppBean\" id=\"incident\" mboname=\"INCIDENT\" orderby=\"TICKETID\" resultstableid=\"results_showlist\" version=\"7.1.0.0\" systemnav=\"false\">\n\nImport back the incident.xml and save. With this configuration, the left Navigation Pane menu is no longer visible in the Incident application."}]},{"id":"DEV_Q230","question":"Java.io.NotSerializableException in WAS\n\nWe are experiencing the Java.io.NotSerializableException exception. I see this error: WTRN0047E:java.io.NotSerializableException. Anyone experienced this before?","answer":"With persistent sessions enabled, any object that is put into the HTTPSession must implement the serializable interface in order for session manager to store the session data outside of JVM.\n\nWhen PMI is enabled, there is a counter for session data size. In order to evaluate this counter, the session data must be serialized into a byte array stream. Any object that is put into the HTTPSession must implement the serializable interface in order for session manager to convert the session data objects into byte array stream.","is_impossible":false,"contexts":[{"filename":"swg21066791.txt","text":"Title: IBM Java.io.NotSerializableException thrown when persistent sessions or PMI is enabled - United States\n\nText:\nserializable; NotSerializableException; java.io.NotSerializableException; waseng; session; httpsession; httpsessions; persistent; ProblemDeterminationTool; ProblemDeterminationDocument TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When Persistent sessions or PMI is enabled and a Java.io.NotSerializableException occur in logs, you will see the following example error message. \n\n\n[10\/4\/02 10:11:10:172 EDT] 28b7c18b SessionContex X WTRN0047E:\njava.io.NotSerializableException: COM.ibm.db2.jdbc.app.DB2Connection\n\n\n\nCAUSE\nThe class name at the end of the exception is the object that does not implement the java.io.Serializable or java.io.Externalizable interface. In most instances, this object is the attribute that was put into the session object; however, sometimes this object is referenced by an attribute of the session object. \n\n To determine which attribute of the session object references this non-serializable object, access the SessionInspectServlet.\n\n\nRESOLVING THE PROBLEM\nImplement the Java.io.Serializable or Java.io.Externalizable interface\n\nWith persistent sessions enabled, any object that is put into the HTTPSession must implement the serializable interface in order for session manager to store the session data outside of JVM.\n\nWhen PMI is enabled, there is a counter for session data size. In order to evaluate this counter, the session data must be serialized into a byte array stream. Any object that is put into the HTTPSession must implement the serializable interface in order for session manager to convert the session data objects into byte array stream.\n\nFor example:\n\npublic classMyObject implementsSerializable{\n}\/\/end of class MyObject\n\nCheck that all objects placed in the HTTPSession implement the java.io.Serializable or java.io.Externalizable interface.\n\n\n 1. Acess the SessionInspectServlet\n \n If the class name printed in the exception is not an object that is explicitly placed into the HTTPSession, use the SessionInspectServlet to determine the attribute in the HTTPSession that references a non-serializable object. \n\n\n\nSessionInspectServlet helps application writers to determine if application is written to support session persistence. SessionInspectServlet helps to: \n\n * Determine attributes present in the session\n \n * Determine serializable and non-serializable attributes in the session\n \n * Determine the size of each serializable attribute in session\n \n * Determine if serializable attribute is implemented properly (if serializable attribute and all its internals are serializable)\n\n\nServlet serializes and deserializes attributes into memory to simulate session persistence; therefore, application writers need not turn on session persistence to run this servlet. However, you can run it with persistent sessions enabled. \n\nHow to Access the SessionInspectServlet: \n 1. com.ibm.ws.webcontainer.httpsession.SessionInspectServlet is shipped with WebSphere Application Server. It is already in the classpath and does not need to be added to the application. \n \n Define a servlet\/uri entry for class SessionInspectServlet. If ServeServletsByClassnameEnabled is set to true (check the ibm-web-ext.xmi file in the WEB-INF directory of your webModule) in your webModule, servlet\/uri definition is not needed. \n \n 2. Restart your Web module.\n \n 3. Open a browser and access your Web module from the browser, then navigate the application in the browser to populate the session.\n \n 4. Press Crtl+N to open a new browser, then access the SessionInspectServlet in the new browser by calling the URI that you defined in step 2. If you are using ServeServletsbyClassname, the URI will be \"webapp_context_root\\servlet\\com.ibm.ws.webcontainer.httpsession.SessionInspectServlet\". This displays the session details at that moment. You can access the servlet as you navigate your application to determine the session contents as you go along. Note: The servlet does not support attributes in the session that are outside the WebSphere Application Server scope. That is, session contents need to be accessed by the server class loader scope.\n\n \n\nCross reference information Segment Product Component Platform Version Edition Application Servers Runtimes for Java Technology Java SDK"}]},{"id":"DEV_Q231","question":"What IBM Business Process Manager version is affected by the Apache Commons FileUpload vulnerability CVE-2016-1000031?\n\nWhat IBM Business Process Manager version is affected by the Apache Commons FileUpload vulnerability CVE-2016-1000031? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q232","question":"CICS TS support for IBM SDK Java Version 8\n\nDo any of the current releases of CICS Transaction Server for z\/OS (CICS TS) support the new IBM SDK, Java\u2122 Technology Edition V8? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q233","question":"How does configuring \"hung threads detection\" impact performance of a production WAS server?\n\nI took a pmr about hung issue on Solaris. Customer said he couldn't collect MG data because the issue always happened at night. So I let him to configure hung detection policy by adding JVM arguments (alarm threads hung). He said it was production server and worried about any impact performance.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q234","question":"TCR 2.1.1 Fixpack 2 installation failed\n\n\n\nI need to install Fixpack 2 on my TCR 2.1.1 environment, but the installation keeps failing with error:\n\n ACUOSI0050E External command action failed with return code 1.\n\nI was not able to understand why it is failing. Can you please help providing suggestion to perform a correct troubleshooting ?\n\nThanks","answer":"If it is expected you run the Fixpack installation with a non-root user, double check the permission bit for the involved directory tree and in case temporary set them to give write authorization to the user account you are installing the FixPack with. \n\nThen run again the installation program.","is_impossible":false,"contexts":[{"filename":"swg21666489.txt","text":"Title: IBM TCR 2.1.1 FixPack 2 failing with ACUOSI0050E - United States\n\nText:\nACUOSI0050E; BUILD FAILED; copyEAR.sh; tcr211_Embedded_FP2; failed to copy; permission denied; TCR; FP2; FixPack 2 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Installation of TCR 2.1.1 FixPack 2 fails with the following error message:\nACUOSI0050E External command action failed with return code 1. \n\nDIAGNOSING THE PROBLEM\nLooking at the the file IBM_Tivoli_Common_Reporting_2.1_1_FP2.log you can find additional details about the failure.\nIn some cases it can show the procedure failing at this step:\n\nErrors: [com.ibm.ac.si.ap.action.ExternalCommandActionException: \nACUOSI0050E External command action failed with return code 1. \nInvocation string: \n[\/opt\/IBM\/tivoli\/tipv2Components\/TCRComponent\/conf\/tcr211_Embedded_FP2\/copyEAR.sh, \/opt\/IBM\/tivoli\/tipv2Components\/TCRComponent, \n\/opt\/IBM\/tivoli\/tipv2, TIPProfile], \ncom.ibm.ac.common.hosts.UpdateFailedException: : ] \n\nso while executing the script copyEAR.sh. \n\nLooking at the TCRComponent\/logs, you can find all the STDOUT and STDERR streams for the installation scripts, including the failing copyEAR.sh. \nSo you can check into tcr211_Embedded_FP2_run_cognos_copy_ear_update.err to understand what caused the installation failure.\nIf you find a message like:\n****\nBUILD FAILED \n\/opt\/IBM\/tivoli\/tipv2Components\/TCRComponent\/cognos\/temp\/build.xml:298: Failed to copy \n\/opt\/IBM\/tivoli\/tipv2Components\/TCRComponent\/cognos\/webcontent\/tivoli\/ITM\/images\/newWindow_16.gif to \n\/opt\/IBM\/tivoli\/tipv2\/profiles\/TIPProfile\/installedApps\/TIPCell\/IBM Cognos 8.ear\/p2pd.war\/tivoli\/ITM\/images\/newWindow_16.gif due to java.io.FileNotFoundException \n\/opt\/IBM\/tivoli\/tipv2\/profiles\/TIPProfile\/installedApps\/TIPCell\/IBM Cognos 8.ear\/p2pd.war\/tivoli\/ITM\/images\/newWindow_16.gif (Permission denied) and I couldn't delete the corrupt\n\/opt\/IBM\/tivoli\/tipv2\/profiles\/TIPProfile\/installedApps\/TIPCell\/IBM Cognos 8.ear\/p2pd.war\/tivoli\/ITM\/images\/newWindow_16.gif\n***\n\nthis indicates a lack of permission for the user account you used to run the installation, on the directory tree involved with this operation.\n\n\n\nRESOLVING THE PROBLEM\nIf it is expected you run the Fixpack installation with a non-root user, double check the permission bit for the involved directory tree and in case temporary set them to give write authorization to the user account you are installing the FixPack with. \n\nThen run again the installation program.\n\n \n\nPRODUCT ALIAS\/SYNONYM\n Tivoli Common Reporting V2.1.1"}]},{"id":"DEV_Q235","question":"Security Bulletin: A vulnerability in IBM Java Runtime affects IBM WebSphere MQ (CVE-2016-3485)\n\nI need to understand details regarding Security Bulletin: A vulnerability in IBM Java Runtime affects IBM WebSphere MQ (CVE-2016-3485). Where can I find this information?\n","answer":"CVEID: CVE-2016-3485 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-3485]\nDESCRIPTION: An unspecified vulnerability related to the Networking component has no confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 2.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/115273 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/115273] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:N\/S:U\/C:N\/I:L\/A:N)","is_impossible":false,"contexts":[{"filename":"swg22001630.txt","text":"Title: IBM Security Bulletin: A vulnerability in IBM Java Runtime affects IBM WebSphere MQ (CVE-2016-3485) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n There are multiple vulnerabilites in IBM\u00ae Runtime Environment Java\u2122 Versions 6 and 7 that are used by IBM WebSphere MQ. These issues were disclosed as part of the IBM Java SDK updates in July 2016. \n\nVULNERABILITY DETAILS\nIf you run your own Java code using the IBM Java Runtime delivered with this product, you should evaluate your code to determine whether the complete list of vulnerabilities are applicable to your code. For a complete list of vulnerabilities please refer to the link for \u201cIBM Java SDK Security Bulletin\u201d located in the \u201cReferences\u201d section for more information. \n\nCVEID: CVE-2016-3485 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-3485]\nDESCRIPTION: An unspecified vulnerability related to the Networking component has no confidentiality impact, low integrity impact, and no availability impact.\nCVSS Base Score: 2.9\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/115273 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/115273] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:L\/AC:H\/PR:N\/UI:N\/S:U\/C:N\/I:L\/A:N)\n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ 9.0.0.x Long Term Support (LTS)\nMaintenance level 9.0.0.0 only\n\nIBM MQ 9.0.x Continuous Delivery Release (CDR)\nContinuous delivery update 9.0.1 only\n\nWebSphere MQ 8.0\nMaintenance levels between 8.0.0.0 and 8.0.0.5\n\nIBM MQ Appliance 8.0\nMaintenance levels between 8.0.0.0 and 8.0.0.5\n\nWebSphere MQ 7.5\nMaintenance levels between 7.5.0.0 and 7.5.0.7\n\nWebSphere MQ 7.1\nMaintenance levels between 7.1.0.0 and 7.1.0.7\n\nREMEDIATION\/FIXES\nIBM MQ 9.0 \nApply fix pack 9.0.0.1 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=9.0.0.1&platform=All&function=all&useReleaseAsTarget=true] or latest Continuous Delivery level\n\nWebSphere MQ 8.0\nApply fix pack 8.0.0.6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21995100] \n\n \n\nWebSphere MQ 7.5\nApply fix pack 7.5.0.8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg22005413]\n\nWebSphere MQ 7.1\nApply fix pack 7.1.0.8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg27024302]\n\n\nFor unsupported versions of IBM WebSphere MQ, IBM recommends upgrading to a fixed, supported version of the product.\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] \nIBM Java SDK Security Bulletin [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21986642] \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 Published: 12 July 2017\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#"}]},{"id":"DEV_Q236","question":"Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect\n\nI need to understand details regarding Security Bulletin: Multiple vulnerabilities in IBM Java Runtime affect API Connect (CVE-2016-5546, CVE-2016-5548, CVE-2016-5549, CVE-2016-5547, CVE-2016-2183, CVE-2017-3511). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q237","question":"Traffic across domains seems unexpected\n\n\n\nI have two Multi-Protocol Gateways (MPGWs) configured, each in their own domain:\n\n Domain A\n MPGW_A\n FSH_A (1.2.3.4:443)\n Domain B\n MPGW_B\n FSH_B (0.0.0.0:443)\n\nThe FSH_B is disabled, thus MPGW_B cannot take traffic. However, if I modify the config for MPGW_B (i.e. just change a Stylesheet parameter) the traffic goes to MPGW_B somehow. How is this happening? FSH_B is still disabled.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q238","question":"recently installed Impact 7.1.0. fixpack 3, now when ever start the secondary impact server, the primary servers logging stops? How can I fix this?\n\nwhen NCI1 is running by itself, all logging is functioning. When NCI2\nis started, logging stops on NCI1 and the \"reader\" logs indicate that\nthe readers have stopped. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q239","question":"Cannot launch RFT 8.2\n\n\n\nHello.\n\nCould anyone can help to see why I cannot launch RFT 8.2? When I launch RFT. I get an error message--\"An error has occurred. See the log file...\" I check the log file. It shows\n\n!SESSION Mon Nov 04 12:46:16 CST 2013 ------------------------------------------\n!ENTRY org.eclipse.equinox.launcher 4 0 2013-11-04 12:46:16.359\n!MESSAGE Exception launching the Eclipse Platform:\n!STACK\njava.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter\n at java.net.URLClassLoader.findClass(URLClassLoader.java:423)\n at java.lang.ClassLoader.loadClass(ClassLoader.java:653)\n at java.lang.ClassLoader.loadClass(ClassLoader.java:619)\n at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:616)\n at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)\n at org.eclipse.equinox.launcher.Main.run(Main.java:1407)\n at org.eclipse.equinox.launcher.Main.main(Main.java:1383)\n\nIf I launch RFT with -clean or -vm option, the same phenomenon occurs.","answer":"Delete the user's .eclipse\/ibm.software.delivery.platform_7.5.0_???? directory. \n\nFor example: \n\nrm -rf \/home\/joe\/.eclipse\/ibm.software.delivery.platform_7.5.0_1529064711 \n\n \n\nThen relaunch the package.","is_impossible":false,"contexts":[{"filename":"swg21330011.txt","text":"Title: IBM Non Administrator usage must be manually cleaned up - United States\n\nText:\nRN1.2.1; SRX TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When a eclipse based package is installed by an administrator and used by a non-administrator, out of date eclipse configuration cruft is left behind in the user's .eclipse\/ folder that may affects the correct functioning of the currently installed package(s). \n\nSYMPTOM\nThe p2 based eclipse package does not start up correctly for non-administrator or it takes abnormal amount of time (10 minutes) to start up. The log file in the user's .eclipse\/ibm.software.delivery.platform_7.5.0_???? folder, for example: \/home\/joe\/.eclipse\/ibm.software.delivery.platform_7.5.0_1529064711\/configuration\/1225137678916.log, may contain an entry like: \n\n!MESSAGE Exception launching the Eclipse Platform: \n\n!STACK \n\njava.lang.ClassNotFoundException: org.eclipse.core.runtime.adaptor.EclipseStarter \n\nat java.net.URLClassLoader.findClass(Unknown Source) \n\nat java.lang.ClassLoader.loadClass(Unknown Source) \n\nat java.lang.ClassLoader.loadClass(Unknown Source) \n\nat org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source) \n\nat org.eclipse.equinox.launcher.Main.basicRun(Unknown Source) \n\nat org.eclipse.equinox.launcher.Main.run(Unknown Source) \n\nat org.eclipse.equinox.launcher.Main.main(Unknown Source)\n\n\n\nCAUSE\nThis issue has been identified as Eclipse defect 255268 [https:\/\/bugs.eclipse.org\/bugs\/show_bug.cgi?id=255268]. Review the Bug report for more details.\n\n\n\nRESOLVING THE PROBLEM\n \n\n \n\nWORKAROUND: \n\nDelete the user's .eclipse\/ibm.software.delivery.platform_7.5.0_???? directory. \n\nFor example: \n\nrm -rf \/home\/joe\/.eclipse\/ibm.software.delivery.platform_7.5.0_1529064711 \n\n \n\nThen relaunch the package. \n\n\n\n\n\n\n\n\n\n\nCross Reference information Segment Product Component Platform Version Edition Software Development Rational Application Developer for WebSphere Software Not Applicable 7.5.2 All Editions"}]},{"id":"DEV_Q240","question":"Port number error starting 9.0 Launcher\n\n\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.","is_impossible":false,"contexts":[{"filename":"swg21986219.txt","text":"Title: IBM Launcher failure when 'On Success' is set to Delete and 'On Failure' is set to Commit - United States\n\nText:\nWTX 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."}]},{"id":"DEV_Q241","question":"When and why Apache Storm process of ITNM creating db2 files in \/tmp?\n\n\n\nWhen and why should the following files be generated ?\n\n\uff1e-rwxrwxrwx poll ncoadmin \/opt\/IBM\/tivoli\/netcool\/var\/precision\/storm\/workers\/74089823-da35-4f8e-85e4-1454a928eee2\/tmp\/connlicj.bin\n\n\uff1e-rwxrwxrwx poll ncoadmin \/opt\/IBM\/tivoli\/netcool\/var\/precision\/storm\/workers\/74089823-da35-4f8e-85e4-1454a928eee2\/tmp\/jccdiag.log\n\n\uff1e-rwxrwxrwx poll ncoadmin \/opt\/IBM\/tivoli\/netcool\/var\/precision\/storm\/workers\/74089823-da35-4f8e-85e4-1454a928eee2\/tmp\/license.lock\n\n\uff1e-rwxrwxrwx poll ncoadmin \/opt\/IBM\/tivoli\/netcool\/var\/precision\/storm\/workers\/74089823-da35-4f8e-85e4-1454a928eee2\/tmp\/serverlist.lock","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q242","question":"IBM Support Assistant data collector for BPM\n\nWhat can I use to obtain some standard information in order to debug my IBM Business Process Manager environment? ","answer":"The new data collector in IBM Business Process Manager V8.5 is designed for ease of use to gather some of the standard information that is needed to debug IBM Business Process Manager issues.","is_impossible":false,"contexts":[{"filename":"swg21641516.txt","text":"Title: IBM A new IBM Support Assistant data collector exists in the IBM Business Process Manager (BPM) Version 8.5 products - United States\n\nText:\nISA data collection datacollection logs bpmdc isadc NEWS\n\nABSTRACT\n The new data collector in IBM Business Process Manager V8.5 is designed for ease of use to gather some of the standard information that is needed to debug IBM Business Process Manager issues. This command-line tool can gather log file or configuration information and upload it to a Problem Management Record (PMR). This collector is also included in IBM Business Process Manager V8.0.1 Fix Pack 3. \n\nCONTENT\nThe script gathers various product information, compresses it into a .zip file, and can optionally send the compressed file to IBM for a PMR. You can also use this tool to compress the data without sending it to IBM. The command is profile_root\/bin\/bpmdc\nThe profile_root variable is the base profile directory for the profile from which you want to get data. \n\nCommon Examples \n\nTo gather the logs and upload them to ECURep: \nC:\/MyProfileDirectory\/bin\/bpmdc -PMR=12345.678.901 -uploadToIBM=yes \n\nTo gather the logs and config directory: \n\nC:\/MyProfileDirectory\/bin\/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -config=yes \n\nTo gather logs for installation issues: \n\nC:\/MyProfileDirectory\/bin\/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -type=Install \n\nTo gather 3 java cores from MyAppServer at 60 second intervals: \n\nC:\/MyProfileDirectory\/bin\/bpmdc -PMR=12345.678.901 -uploadToIBM=yes -type=Dump -server=MyAppServer -soapport=8881 -user=admin -password=admin -dumptype=Thread -count=3 -interval=60 \n\n\n\n\n\nCommand Line Parameter Default Value Description PMR None This parameter is the 11-digit PMR number to which the data is associated. Use one of the following forms for this value: 12345.678.901 or \"12345,678,901\"\nNote: Comma characters can be an issue on the Microsoft Windows command-line if you do not surround the value with the double quote characters. uploadToIBM no This parameter specifies whether to upload the data to the IBM ECURep site for a particular PMR. You can set this value to yes or no. outputDirectory install_root\/BPM\/isadc This parameter specifies the path to the directory where the output collection .zip file will be stored. type General This parameter specifies which type of collection to run. The valid values are General, Install, or Dump(8.5.5). config no With a general collection, when you set this parameter to yes, the config directory is included. You can set this value to yes or no. help No values When you include this parameter with the command, a description of the command options is displayed. Server Connection options added in 8.5.5 \nRequired for -type=Dump server No default This option specifies the server from which you wish to collect JVM dumps. soapport No default This option specifies the SOAP port for the server. user No default This option specifies the user with wsadmin access to the server to which you are connecting. password No default This option specifies the password for the user. Dump options added in 8.5.5 \nAvailable for -type=Dump dumptype Thread This option specifies the type of Java\u2122 virtual machine (JVM) dump to trigger: \nThread - Javacore or thread dump. \nHeap - A Heap dump is generated.\nSystem - System dump is also generated and has JExtract run on it. count 1 This option specifies the number of JVM dumps to trigger during the collection. interval 0 This option specifies the interval in seconds to wait between JVM dumps. \n\nYou can run the command without any parameters, which results in the general collection being run and the logs directory is compressed into a .zip file. \n\n\nThe output file name has the following format: PMRnumber . type _ timeStampValue .zip\nIn V8.5.5 the format is changed to: PMRnumber . ProfileName_type _ timeStampValue .zip \n\n\nThe data gathered is based on the profile where the command is run. If it is run from the installation directory, then the default profile is used. \n\n\nNote: Be sure to run the command from the profile from which you wish to gather data. \n\n\nGeneral collection \nThe \"General\" collection gathers the following information: * Profile logs directory (profile_root\/logs). The collected files include all of the server log files and trace under this profile directory. \n * The results of the versionInfo-maintenancePackages command. \n * (Optionally) The profile config directory (profile_root\/config). This directory is only collected when the -config=yes option is used.\n\n\nNote: The limitation with this collection is that it does not gather log files and trace if it goes to a custom directory outside of the Profile logs directory. It is not recommended that you change the log file locations from the default as it makes it more difficult for other people to find them. \n\nInstall collection\nThe \"Install\" collection gathers the following information that is listed in the Collect troubleshooting data for installation or upgrade problems with IBM Business Process Manager products [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21506937] document: \n\n * Any temporary launchpad log files. \n * Installation Manager Data directory \n * The results of the versionInfo -maintenancePackages command \n * Installation logs directory \n * Profile logs directory \n * Database upgrade script log files \n * Various configuration files that are related to the installation process\n\n\n\n\nJVM Dump collection The \"Dump\" collection type triggers various JVM dumps on a target server within a profile prior to gathering the general collection and generated dumps. \n\nWith the provided server connection options, the command will connect to the server using the soapport to make a wsadmin connection with the user and password. Depending on the dump type, it will trigger various JVM dumps until the count amount is reached. The dumps are triggered a set number of seconds apart based on the interval that is set. \n\nThe collection will gather the general collection files like \/logs and version information in addition to the dump files like Javacores, heap dumps and system dump .zip files. \n\n * Thread - This type will trigger Javacores or thread dumps to be produced for the JVM. \n * Heap - This type will trigger heap dumps to be generated. \n * System - This type will trigger system dumps to be generated. It will also run JExtract on the dump prior to the upload, which can take some time depending on the heap size. \n\n\n\nCommon usage The following list provides some common usage scenarios for this command: \n\n * After an issue occurs, use the basic bpmdc command to compress the log files for the profile into a .zip file. \n * Recreate your issue after setting a trace string using the administrative console [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/ttrb_entrrs.html] or wsadmin [http:\/\/pic.dhe.ibm.com\/infocenter\/wasinfo\/v8r0\/topic\/com.ibm.websphere.nd.multiplatform.doc\/info\/ae\/ae\/txml_troubleshooting.html]. \n Then, run the bpmdc command to collect the log files and send them to IBM. \n * After opening a PMR, use bpmdc-PMR=PMRnumber-uploadToIBM=yes with the most relevant type options to upload data. \n * IBM Support provides a specific command or set of commands to run for your environment that gets the needed data. \n * IBM Support provides a traces string that needs to be gathered with the commands. With trace enabled, you recreate the issue or wait for a reoccurrence before running the provided commands to gather and upload the data to IBM.\n\nRELATED INFORMATION\n A simplified Chinese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21644209]\n\n\n \n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard General AIX, Linux, Linux zSeries, Solaris, Windows 8.5 Business Integration IBM Business Process Manager Express General Linux, Linux zSeries, Windows 8.5 \nPRODUCT ALIAS\/SYNONYM\n BPM"}]},{"id":"DEV_Q243","question":"Using cobol copybooks\n\nSometimes, there will be errors\/fields missing in typetree, while importing cobol copybooks. Is there any format for copybooks(specifically to be used in wtx), that we need to follow? ","answer":"Some files are not correctly overwritten \/ modified during the upgrade.","is_impossible":false,"contexts":[{"filename":"swg21684407.txt","text":"Title: IBM COBOL Copybook importer is missing in WTX Design Studio 8.4.1.1 if installed over 8.4.1.0 - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n When installing IBM WebSphere Transformation Extender (WTX) Design Studio 8.4.1.1 on the Windows platform over the top of an IBM WTX 8.4.1.0 installation, the COBOL Copybook importer may be missing after the upgrade. \n\nSYMPTOM\nThe COBOL Copybook importer option no longer appears in the list of available importers.\n\n\nCAUSE\nSome files are not correctly overwritten \/ modified during the upgrade.\n\nENVIRONMENT\nIBM WebSphere Transformation Extender 8.4.1.1 Design Studio on Windows\n\nRESOLVING THE PROBLEM\nInstall WTX Design Studio 8.4.1.1 in an empty directory, and then perform any installation customization."}]},{"id":"DEV_Q244","question":"How to clear Errors Found in crm_mon\n\nHow to clear Errors Found in crm_mon ","answer":"The following steps can be used to clear each failed resource using cib_tool.pl. \n\n[root@system pts]# \/opt\/nz-hwsupport\/pts\/cib_tools.pl\nheartbeat is running on ha1\nheartbeat is running on ha2\nNo split brain detected on ha1\nNo split brain detected on ha2\nCRM running on ha1\nCRM running on ha2","is_impossible":false,"contexts":[{"filename":"swg21694876.txt","text":"Title: IBM Errors Found in crm_mon - PureData System for Analytics - United States\n\nText:\nfencing route; crm_mon; failed resources; netezza TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Failed resources are found when checking the cluster status using crm_mon. \n\nRESOLVING THE PROBLEM\nThe following steps can be used to clear each failed resource using cib_tool.pl. \n\n[root@system pts]# \/opt\/nz-hwsupport\/pts\/cib_tools.pl\nheartbeat is running on ha1\nheartbeat is running on ha2\nNo split brain detected on ha1\nNo split brain detected on ha2\nCRM running on ha1\nCRM running on ha2\n\n\n\n\nCIB tools\n\n============\nLast updated: Fri Jan 16 18:32:06 2015\nCurrent DC: system (487fb699-c9d5-4dfc-af3c-8358070c151a)\n2 Nodes configured.\n3 Resources configured.\n============\n\nNode: system2 (e3c03746-26c0-4e7e-9e10-c654c1117c18): online\nNode: system (487fb699-c9d5-4dfc-af3c-8358070c151a): online\n\nResource Group: nps\ndrbd_exphome_device (heartbeat:drbddisk): Started system\ndrbd_nz_device (heartbeat:drbddisk): Started system\nexphome_filesystem (heartbeat::ocf:Filesystem): Started system\nnz_filesystem (heartbeat::ocf:Filesystem): Started system\nfabric_ip (heartbeat::ocf:IPaddr): Started system\nwall_ip (heartbeat::ocf:IPaddr): Started system\nnz_dnsmasq (lsb:nz_dnsmasq): Started system\nnzinit (lsb:nzinit): Started system\n\nFailed actions:\nfencing_route_to_ha2_start_0 (node=system, call=29, rc=1): Error\nfencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\n\nFailed resources are detected\nOptions to choose from:\n\n1: Add addtional mount\n2: Add virtual ip\n3: Disable stonith\n4: Enable stonith\n5: Clear Failed resource\n6: Delete a Resource\n7: Display Resources\n\ne: Exit\n\nChoose an option:5\n\n\n============\nLast updated: Fri Jan 16 18:32:15 2015\nCurrent DC: system (487fb699-c9d5-4dfc-af3c-8358070c151a)\n2 Nodes configured.\n3 Resources configured.\n============\n\nNode: system2 (e3c03746-26c0-4e7e-9e10-c654c1117c18): online\nNode: system (487fb699-c9d5-4dfc-af3c-8358070c151a): online\n\nResource Group: nps\ndrbd_exphome_device (heartbeat:drbddisk): Started system\ndrbd_nz_device (heartbeat:drbddisk): Started system\nexphome_filesystem (heartbeat::ocf:Filesystem): Started system\nnz_filesystem (heartbeat::ocf:Filesystem): Started system\nfabric_ip (heartbeat::ocf:IPaddr): Started system\nwall_ip (heartbeat::ocf:IPaddr): Started system\nnz_dnsmasq (lsb:nz_dnsmasq): Started system\nnzinit (lsb:nzinit): Started system\n\nFailed actions:\nfencing_route_to_ha2_start_0 (node=system, call=29, rc=1): Error\nfencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\n\nFailed resources are detected\nFailed resources that can be cleared:\n\n0. fencing_route_to_ha2_start_0 (node=system, call=29, rc=1): Error\n1. fencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\nSelect a resource to clear(Input number next to resource to select or\npress enter to return):0\ncrm_resource[11082]: 2015\/01\/16_18:32:21 info: Invoked: crm_resource -r\nfencing_route_to_ha2 -C -H system\n\n\nResource Cleared Succesfully!\n\nCIB tools\n\n============\nLast updated: Fri Jan 16 18:32:23 2015\nCurrent DC: system (487fb699-c9d5-4dfc-af3c-8358070c151a)\n2 Nodes configured.\n3 Resources configured.\n============\n\nNode: system2 (e3c03746-26c0-4e7e-9e10-c654c1117c18): online\nNode: system (487fb699-c9d5-4dfc-af3c-8358070c151a): online\n\nResource Group: nps\ndrbd_exphome_device (heartbeat:drbddisk): Started system\ndrbd_nz_device (heartbeat:drbddisk): Started system\nexphome_filesystem (heartbeat::ocf:Filesystem): Started system\nnz_filesystem (heartbeat::ocf:Filesystem): Started system\nfabric_ip (heartbeat::ocf:IPaddr): Started system\nwall_ip (heartbeat::ocf:IPaddr): Started system\nnz_dnsmasq (lsb:nz_dnsmasq): Started system\nnzinit (lsb:nzinit): Started system\nfencing_route_to_ha2 (stonith:apcmastersnmp): Started system\n\nFailed actions:\nfencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\n\nFailed resources are detected\nOptions to choose from:\n\n1: Add addtional mount\n2: Add virtual ip\n3: Disable stonith\n4: Enable stonith\n5: Clear Failed resource\n6: Delete a Resource\n7: Display Resources\n\ne: Exit\n\nChoose an option:5\n\n\n============\nLast updated: Fri Jan 16 18:32:33 2015\nCurrent DC: system (487fb699-c9d5-4dfc-af3c-8358070c151a)\n2 Nodes configured.\n3 Resources configured.\n============\n\nNode: system2 (e3c03746-26c0-4e7e-9e10-c654c1117c18): online\nNode: system (487fb699-c9d5-4dfc-af3c-8358070c151a): online\n\nResource Group: nps\ndrbd_exphome_device (heartbeat:drbddisk): Started system\ndrbd_nz_device (heartbeat:drbddisk): Started system\nexphome_filesystem (heartbeat::ocf:Filesystem): Started system\nnz_filesystem (heartbeat::ocf:Filesystem): Started system\nfabric_ip (heartbeat::ocf:IPaddr): Started system\nwall_ip (heartbeat::ocf:IPaddr): Started system\nnz_dnsmasq (lsb:nz_dnsmasq): Started system\nnzinit (lsb:nzinit): Started system\nfencing_route_to_ha2 (stonith:apcmastersnmp): Started system\n\nFailed actions:\nfencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\n\nFailed resources are detected\nFailed resources that can be cleared:\n\n0. fencing_route_to_ha1_start_0 (node=system2, call=15, rc=1): Error\nSelect a resource to clear(Input number next to resource to select or\npress enter to return):0\ncrm_resource[17386]: 2015\/01\/16_18:32:37 info: Invoked: crm_resource -r\nfencing_route_to_ha1 -C -H system2\n\n\nResource Cleared Succesfully!\n\nCIB tools\n\n============\nLast updated: Fri Jan 16 18:32:39 2015\nCurrent DC: system (487fb699-c9d5-4dfc-af3c-8358070c151a)\n2 Nodes configured.\n3 Resources configured.\n============\n\nNode: system2 (e3c03746-26c0-4e7e-9e10-c654c1117c18): online\nNode: system (487fb699-c9d5-4dfc-af3c-8358070c151a): online\n\nResource Group: nps\ndrbd_exphome_device (heartbeat:drbddisk): Started system\ndrbd_nz_device (heartbeat:drbddisk): Started system\nexphome_filesystem (heartbeat::ocf:Filesystem): Started system\nnz_filesystem (heartbeat::ocf:Filesystem): Started system\nfabric_ip (heartbeat::ocf:IPaddr): Started system\nwall_ip (heartbeat::ocf:IPaddr): Started system\nnz_dnsmasq (lsb:nz_dnsmasq): Started system\nnzinit (lsb:nzinit): Started system\nfencing_route_to_ha2 (stonith:apcmastersnmp): Started system\n\nNo failed resources"}]},{"id":"DEV_Q245","question":"Problem with XMLLIB->VALIDATEEX during XML Validation\n\nI am using XMLLIB VALIDATEXX in WTX 8.3.0.5 for XML Validations and it is running fine on Windows.\nWhen deployed same code on zos map is executing in loop(output card having rule with xmllib method call is not completing) \nPlease suggest.Thanks","answer":"Add the XML toolkit xml4c library directory to the LIBPATH environment variable.\n\nExample:\n\nexport LIBPATH=$LIBPATH:\/usr\/lpp\/ixm\/xslt4c-1_11\/lib\/","is_impossible":false,"contexts":[{"filename":"swg21988389.txt","text":"Title: IBM Map does not complete when using xmllib functions on z\/OS - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Transformation Extender map does not complete when using xmllib functions on z\/OS.\n\nExample map rule using xmllib function:\n\n=NUMBERTOTEXT( xmllib->VALIDATEEX( \"ipo.in.xml\", \"urn:hl7-org:v3 http:\/\/www.example.com\/IPO [http:\/\/www.example.com\/IPO] ipo.xsd\", \"numtotext.log\" ) )\n\n\nSYMPTOM\nMap execution is incomplete and JOBLOG reports the following error:\n\n1CEE3501S The module libxslt4c.1_11_0q.dll was not found.\n\n\nCAUSE\nThe XML toolkit xml4c library directory is missing from LIBPATH environment variable.\n\n\nRESOLVING THE PROBLEM\nAdd the XML toolkit xml4c library directory to the LIBPATH environment variable.\n\nExample:\n\nexport LIBPATH=$LIBPATH:\/usr\/lpp\/ixm\/xslt4c-1_11\/lib\/"}]},{"id":"DEV_Q246","question":"What is the latest version of the Log File Agent?\n\nWhat is the latest version of the Log File Agent?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q247","question":"IID 8.5.7 failed to start due to \"Java was started but returned exit code=-805306369\"\n\nWe have installed new IID 8.5.7 on Windows 7 on VMware. The installation was successed. However, IID failed to launch always. The dialog shows \"Java was started but returned exit code=-805306369\". The IID log shows BundleStatusException. How do we resolve this?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q248","question":"missing VM manager data\n\n\n\nwe are missing VM manager data for 13 servers. error: invalid credentials - suspended. there are no recent changes done for the ID\/pwd.\n\nplease suggest the action need to be taken.\n1039699\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q249","question":"Help with Security Bulletin: IBM WebSphere MQ Administration command could cause denial of service (CVE-2016-8971)\n\nI need to understand details regarding Security Bulletin: IBM WebSphere MQ Administration command could cause denial of service (CVE-2016-8971). Where can I find this information?\n","answer":"CVEID: CVE-2016-8971 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8971]\nDESCRIPTION: IBM MQ could allow an authenticated user with queue manager permissions to cause a segmentation fault. This would result in the machine needing to be rebooted to resume normal operations.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118862 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118862] 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:H)","is_impossible":false,"contexts":[{"filename":"swg21998663.txt","text":"Title: IBM Security Bulletin: IBM MQ administration command could cause denial of service (CVE-2016-8971) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n An administration command can cause IBM MQ to access an invalid memory address, leading to a segmentation failure and causing the queue manager to become unresponsive. \n\nVULNERABILITY DETAILS\nCVEID: CVE-2016-8971 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2016-8971]\nDESCRIPTION: IBM MQ could allow an authenticated user with queue manager permissions to cause a segmentation fault. This would result in the machine needing to be rebooted to resume normal operations.\nCVSS Base Score: 5.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118862 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/118862] 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:H) \n\nAFFECTED PRODUCTS AND VERSIONS\nIBM MQ V9.0 Long Term Support Release \n\nIBM MQ V9.0.0.0 only. \n\nIBM MQ V8.0 \n\nIBM MQ V8.0.0.0 - V8.0.0.5 maintenance levels.\n\nREMEDIATION\/FIXES\nIBM MQ V9.0 Long Term Support Release \n\nApply 9.0.0.1 [https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=9.0.0.1&platform=All&function=all&useReleaseAsTarget=true] maintenance level. \n\nIBM MQ V8.0 \n\nApply 8.0.0.6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21995100] maintenance level.\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 20 February 2017: Original version published.\n23 February 2017: Minor corrections to wording.\n21 June 2017: Add 9.0 LTS applicability \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=swg21999232]"}]},{"id":"DEV_Q250","question":"Help with Security Bulletin: IIB is affected by Node.js security vulnerability ( CVE-2017-1000381 and CVE-2017-11499 )\n\nI need to understand details regarding Security Bulletin: IBM Integration Bus is affected by Node.js security vulnerability ( CVE-2017-1000381 and CVE-2017-11499 ). Where can I find this information? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q251","question":"MQ jobs and some user jobs are in semaphore wait (SEMW) status\n\nAfter upgrading WMQ on IBM i, MQ jobs and some user jobs are in a semaphore wait (SEMW) status. I've tried to end and restart MQ, performed cold start, delete and rebuild MQ system with no luck. Where do I need to look?\n","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q252","question":"How to resolve the StaleConnectionException in WebSphere Application Server?\n\nI see this exception in WebSphere Application Server J2c and RRA traces:\n\nWSRdbManagedC > preTestConnection Entry WSRdbManagedConnectionImpl@51a507f2 query: SELECT 1 FROM DUAL WSRdbManagedC 3 Exception java.sql.SQLException: ORA-02396: exceeded maximum idle time, please connect again DSRA0010E: SQL State = 61000, Error Code = 2,396 at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440) at \n...\nEntry java.sql.SQLException: ORA-01012: not logged on ..... OracleDataSto < findMappingClass return Exit class com.ibm.websphere.ce.cm.StaleConnectionException","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q253","question":"Want to find out if Microsoft Edge is supported with ICC?\n\nWant to find out Microsoft Edge is supported with ICC? ","answer":"Microsoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2.","is_impossible":false,"contexts":[{"filename":"swg27042658.txt","text":"Title: IBM Prerequisites for IBM Content Collector Version 4.0.1 - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n This document details the system requirements for IBM Content Collector Version 4.0.1. \n\nCONTENT\n \n\nAlways up-to-date system requirement reports can be dynamically generated by using the Software Product Compatibility Reports (SPCR) tool [http:\/\/www-969.ibm.com\/software\/reports\/compatibility\/clarity\/index.html]. \n\nFrom the Content Collector product tabs below you can select detailed system requirement reports for different contexts (by Operating System, by component). Note that clicking a link will always generate a new, up-to-date report.\n\nImportant:\nBecause 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 forward compatible.\n\nAlways check for the latest IBM Content Collector security bulletins in the IBM Support Portal and make sure to have the required fixes applied.\n\nPRODUCT REQUIREMENTS FOR IBM CONTENT COLLECTOR\n * All versions [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27040212] \n * Version 4.0.1- selected tab, \n\n * HARDWARE REQUIREMENTS\n \n * Content Collector server\n * Client workstations\n * SOFTWARE PREREQUISITES\n \n * Operating system and software\n * Web application server\n * COLLECTION SOURCE SYSTEMS\n \n * Lotus Domino\n * Microsoft Exchange\n * SMTP email\n * Microsoft SharePoint\n * IBM Connections\n * File system\n\n * ARCHIVE SYSTEMS\n \n * IBM Content Manager\n * IBM FileNet P8\n * LEGACY RESTORE\n \n * Legacy restore\n * RETENTION POLICY DISTRIBUTION SUPPORT\n \n * Retention Policy Distribution Support\n * OPTIONAL SOFTWARE\n \n * Optional software\n\n\n\n\n\nIBM CONTENT COLLECTOR PRODUCTS\n * Content Collector for Email\n\n * Content Collector for File Systems\n\n * Content Collector for IBM Connections\n\n * Content Collector for Microsoft SharePoint\n\n\n\n\n\nLegend \n\nx86 Intel 32-bit processors, including IBM System x, eServer xSeries, and BladeCenter servers X86-64 64-bit AMD Opteron (AMD64) and Intel Xeon (EM64T) processors, including IBM System x and BladeCenter servers \n\nHARDWARE REQUIREMENTS\nIBM CONTENT COLLECTOR SERVER\nThe following table contains the minimum and the recommended hardware requirements for the server where IBM Content Collector is installed.\n\n \n\nHardware requirements Minimum Recommended Processor 2 dual-core processors\nx86 or x86-64 2 six-core processors\nx86 or x86-64 Processor speed 2.5 GHz > 3 GHz System memory (RAM) 4 GB 8 GB Hard disk Hard drive with sufficient capacity 2 enterprise class hard drives with 10000 RPM or better Disk space For IBM Content Collector program package, prerequisite software, temporary data, and log information 150 GB > 150 GB For each IBM Content Collector server that is intended to run an SMTP Receiver instance 750 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive documents from SMTP email systems, this storage must be on a fast NAS device and shared between all Content Collector servers. 1 TB redundant storage For IBM Connections archiving 10 GB redundant storage\n\nIf multiple Content Collector servers are deployed in a scale-out setup to archive IBM Connections documents, this storage must be on a fast NAS device and shared between all Content Collector servers. > 10 GB Supported virtualization environments for IBM Content Collector are VMware ESX and ESXi 4, 5, and 5.1 and Microsoft HyperV Server 2008, 2008 R2, and 2012.\n\nBack to top\n\nCLIENT WORKSTATIONS\nThe hardware capacity of connected client workstations must be sufficient to run the supported client applications:\n\n * Lotus Notes or Lotus iNotes\n * Microsoft Outlook or Outlook Web App\n\nIn addition, the minimum hardware requirements for mobile support are contained in the following form(OWA Extension mobile support on iPhone and iPad, iNotes Extension mobile support on iPad only) starting with IBM Content Collector 4.0.1 Fix Pack 2 \n\n \n\nHardware iOS Capacity iPad mini 9.x 16GB iPad with Retina 9.x 16GB iPhone 6 9.x 16GB For more information, see the client software documentation.\n\nBack to top\n\n\n\nSOFTWARE PREREQUISITES\nPREREQUISITES FOR THE IBM CONTENT COLLECTOR SERVER\nThe following section describes the operating system and other software that is required on the system where IBM Content Collector Server is installed.\n\nOPERATING SYSTEM\nIBM Content Collector can be installed on servers with one of the following operating systems:\n\nOperating systems Editions Architectures Fixes Windows Server 2008 * Standard Edition \n * Enterprise Edition\n\n * 32-bit (x86) \n * 64-bit (x86-64)\n\nService Pack 2 Windows Server 2008 R2 * Standard Edition \n * Enterprise Edition\n\n * 64-bit (x86-64)\n\nService Pack 1 Windows Server 2012 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] Windows Server 2012 R2 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] Windows Server 2016 * Datacenter Edition \n * Standard Edition\n\n * 64-bit (x86-64)\n\n[\/support\/docview.wss?uid=swg27042658&aid=1] IBM Content Collector does not support Server Core and Nano server installations. Note that if IBM Content Collector is installed on Windows Server 2012 R2, you can use only IBM Content Manager Enterprise Edition V8.5 as an IBM Content Manager target repository.\n\n\nREQUIRED SOFTWARE\nThe following software must be installed on the server where IBM Content Collector is installed.\nImportant: \n\n * On a 64-bit operating system, IBM Content Collector Server runs in 32-bit compatibility mode. Therefore, IBM Content Collector Server requires the 32-bit version of all software prerequisites. \n * For performance reasons, do not colocate the IBM Content Collector Server and the archive system on one server in a production environment. This setup can be used for testing or demonstration purposes, but it is not officially supported.\n\nSoftware Required for which scenarios Notes DB2 Information Integrator for Content Required for IBM Content Manager V8.4 repositories See IBM Content Manager. IBM Content Manager V8 API Required for IBM Content Manager V8.5 repositories See IBM Content Manager. FileNet Content Engine .NET and Java clients Required for IBM FileNet P8 repositories See IBM FileNet P8. IBM FileNet IDM Desktop 4.0.x Required for IBM FileNet Image Services repositories [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft .NET Framework 4.0 or 4.5 Always required When using Microsoft .NET version 4.5 on a Windows Server 2008 or Windows Server 2008 R2 operating system, Microsoft .NET Framework 4.5.1 is required. Lotus Domino 8.5.0 server with the latest fix pack \nLotus Domino 8.5.3 FP6 server\nLotus Domino 8.5.4 server\nIBM Domino 9.0 or 9.0.1 FP2 server\nIBM Domino 9.0.1 FP4 server\nIBM Domino 9.0.1 FP5 server\nIBM Domino 9.0.1 FP6 server\nIBM Domino 9.0.1 FP7 server\nIBM Domino 9.0.1 FP8 server Required if you want to archive Lotus Notes documents The Lotus Domino server provides a Lotus Notes API for processing Lotus Notes documents. Microsoft Outlook 2007 Service Pack 3 (or later)\nMicrosoft Outlook 2010 Service Pack 1 (or later)\nMicrosoft Outlook 2013\nMicrosoft Outlook 2016 Required if you want to archive email from Microsoft Exchange servers The Microsoft Outlook client provides the Messaging API (MAPI) for email processing. Microsoft Windows DST update KB 955839 [http:\/\/support.microsoft.com\/kb\/955839] Always required [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft Windows Server 2008 R2 SP1 hotfix KB 2732673 [http:\/\/support.microsoft.com\/kb\/2732673]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2728738 [http:\/\/support.microsoft.com\/kb\/2728738]\nMicrosoft Windows Server 2008 R2 SP1 hotfix KB 2831013 [http:\/\/support.microsoft.com\/kb\/2831013]\nMicrosoft Windows Server 2008 R2 hotfix KB 2831154 [http:\/\/support.microsoft.com\/kb\/2831154] Required if the File System Connector is used [\/support\/docview.wss?uid=swg27042658&aid=1] Back to top\n\nWEB SERVER APPLICATIONS\nIBM WEBSPHERE APPLICATION SERVER\nIBM Content Collector requires IBM WebSphere Application Server to run the Configuration Web Service and to perform search and restore operations. Typically, there is no need to check for compatible versions because IBM Content Collector comes with an embedded version of WebSphere Application Server Version 8.0.\n\nHowever, you can deploy some of the IBM Content Collector web applications to an external web application server. IBM Content Collector supports the base edition of IBM WebSphere Application Server for AIX, Linux, and Windows. The Network Deployment edition is not supported. Always install the latest fix pack. The following versions are supported: \n\n * 8.0.0.13 \n * 8.5\n\nIf you use an external web application server, make sure that the following prerequisites that are required for IBM Content Collector Server are also installed on the separate web application server: \n\n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package \n * Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package ATL Security Update \n * Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package \n\nHow to get: \n\nYou can purchase IBM WebSphere Application Server from the following website: WebSphere Application Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27024129]\n\nIBM CONTENT COLLECTOR WEB APPLICATION BROWSERS\nThe IBM Content Collector web applications support the following browsers: \n\nBrowsers Versions Mozilla Firefox * 14 \n * 17 or 24 Extended Support Release (ESR) \n * 24 \n * 28 \n * 31 Extended Support Release (ESR) \n * 32 \n * 33 \n * 34 \n * 35\n\nMicrosoft Internet Explorer * 8 \n * 9 \n * 10 \n * 11\n\nMicrosoft Edge * 20\n\nChrome * 60\n\nMicrosoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2. \n\nHow to get: \n\nYou can obtain Mozilla Firefox from www.mozilla.com [http:\/\/www.mozilla.com] and Microsoft Internet Explorer from www.microsoft.com [http:\/\/www.microsoft.com].\n\nBack to top\n\n\n\nCOLLECTION SOURCE SYSTEMS\nLOTUS DOMINO\nSERVER AND CLIENTS\nThe following table describes the supported versions of Lotus Domino for Domino mail servers and the supported versions of Lotus Notes for Notes mail clients:\n\nServer software Client software Other software requirements Notes * Lotus Domino 8.5.0 \n * Lotus Domino 8.5.1 \n * Lotus Domino 8.5.2 \n * Lotus Domino 8.5.3 FP6 \n * Domino 9.0 \n * Domino 9.0.1 FP2 \n * Domino 9.0.1 FP4 \n * Domino 9.0.1 FP5 \n * Domino 9.0.1 FP6 \n * Domino 9.0.1 FP7 \n * Domino 9.0.1 FP8\n\n * Lotus Notes 8.5.0 \n * Lotus Notes 8.5.1 \n * Lotus Notes 8.5.2 \n * Lotus Notes 8.5.3 FP6 \n * Notes 9.0 (along with the Browser plug-in) \n * Notes 9.0.1 (along with the Browser plug-in) \n * Notes 9.0.1 FP2 \n * Notes 9.0.1 FP4 \n * Notes 9.0.1 FP5 \n * Notes 9.0.1 FP6 \n * Notes 9.0.1 FP7 \n * Notes 9.0.1 FP8\n\n * Windows 7 Service Pack 1 (32-bit and 64-bit) \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Mac OS X 10.8.x (32-bit and 64-bit) \n * Mac OS X 10.9.x (32-bit and 64-bit) \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Mozilla Firefox 14 \n * Mozilla Firefox 17 or 24 Extended Support Release (ESR) \n * Mozilla Firefox 24 \n * Mozilla Firefox 28 \n * Mozilla Firefox 31 Extended Support Release (ESR) \n * Mozilla Firefox 32 \n * Mozilla Firefox 33 \n * Mozilla Firefox 34 \n * Mozilla Firefox 35 \n * Microsoft Internet Explorer 8 \n * Microsoft Internet Explorer 9 \n * Microsoft Internet Explorer 10 \n * Microsoft Internet Explorer 11 \n * Microsoft Edge\n\nOn Mac OS X, Lotus Notes R8.5.1 Fix Pack 2 or higher is required.\n\nOffline repositories, collecting additional archiving information, and automatic document retrieval is not supported for Lotus Notes clients on Mac OS.\n\nThe Notes 9.0 Browser plug-in provides these Content Collector functions: * Interactive restore \n * Settings \n * Help\n\n * Lotus iNotes 8.5.0 \n * Lotus iNotes 8.5.1 \n * Lotus iNotes 8.5.2 \n * Lotus iNotes 8.5.3 FP6 \n * iNotes 9.0 \n * iNotes 9.0.1 FP2 \n * iNotes 9.0.1 FP4 \n * iNotes 9.0.1 FP5 \n * iNotes 9.0.1 FP6 \n * iNotes 9.0.1 FP7 \n * iNotes 9.0.1 FP8\n\niNotes must have been configured when the Domino server was initially configured. Starting with IBM Content Collector 4.0.1 Fix Pack 6, IBM Lotus Domino\/Notes 9.0.1 FP7,FP8 are supported\n\nStarting with IBM Content Collector 4.0.1 Fix Pack 4, IBM Lotus Domino\/Notes 9.0.1 FP6 is supported \n\n Starting with IBM Content Collector 4.0.1 Fix Pack 2, IBM Lotus Domino\/Notes 9.0.1 FP4, FP5, Mozilla Firefox 35 and Microsoft Edge are supported. IBM Content Collector supports the latest fix packs of the server and client software. \n\nWindows 10 is supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nIf you want to use the IBM Content Collector Offline Repository in Notes, the following packages are required on the workstation that runs the Notes client, depending on the version of IBM Content Collector that was used to enable the Domino template: \n\nContent Collector version used to enable Domino template Required package on client workstation IBM Content Collector 2.2 (or earlier) Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update [http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=26347] IBM Content Collector 3.0, 4.0, or 4.0.1 Microsoft Visual C++ 2010 Redistributable Package [http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en] To use IBM Content Collector Search, Lotus Notes R8.5.1 or later with standard configuration is required. Basic configuration is not supported. \n\nIf you want to use IBM Content Collector Search in Notes against a database without an index, the following packages are required on the workstation that runs the Notes client:\n\n * Microsoft Visual C++ 2010 Redistributable Package [http:\/\/www.microsoft.com\/downloads\/details.aspx?FamilyID=A7B7A05E-6DE6-4D3A-A423-37BF0912DB84&displaylang=en&displaylang=en]\n * Microsoft Security Advisory: Insecure library loading could allow remote code execution [http:\/\/support.microsoft.com\/kb\/2533623] \n\n\n\nHow to get: \n\nYou can purchase Domino from the following website: IBM Domino [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24033984]\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running a Lotus Notes client on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenDesktop 7.0 Domino\/Notes 9.0\nCitrix XenDesktop 7.5 or later Application installed on server Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to server Lotus Domino\/Lotus Notes 8.5.3 or \nDomino\/Notes 9.0 Social Edition\nCitrix XenApp 6.5 Application streamed to client Lotus Domino\/Lotus Notes 8.5.1 or \nDomino\/Notes 9.0 Basic\nCitrix XenApp 6.5 Hosted application in your datacenter Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later Local Access App Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later Microsoft Application Virtualization applications (App-V) Domino\/Notes 9.0 \nCitrix XenDesktop\/Citrix XenApp 7.5 or later For the virtualization method application streamed to client, the following restriction applies:\n\n * Automatic client document retrieval does not work in the standard configuration of Notes client version 8.5, 8.5.3, or 9.\n\n \n\n\nBack to top\n\nMICROSOFT EXCHANGE\nSERVER\nThe following table describes the supported versions of Microsoft Exchange Server:\n\nServer software Notes * Microsoft Exchange Server 2007 Standard and Enterprise Edition with Service Pack 3 Update Rollup 11 \n * Microsoft Exchange Server 2010 Standard and Enterprise Edition with Service Pack 2 Update Rollup 4 or Service Pack 3 \n * Microsoft Exchange Server 2013 Standard and Enterprise Edition with Service Pack 1 (KB2860242 [http:\/\/support.microsoft.com\/kb\/2860242]) \n * Microsoft Exchange Server 2016 Standard and Enterprise Edition \n\nYou must not install Microsoft Exchange Server on the IBM Content Collector server. How to get:\nYou can purchase Microsoft Exchange Server from www.microsoft.com [http:\/\/www.microsoft.com].\n\nOUTLOOK EXTENSION\nBefore you add the IBM Content Collector Outlook Extension to a client workstation, ensure that the required software is installed on that workstation: \n\nOperating system Client application Other software requirements Notes * Windows 7 Professional Service Pack 1 \n * Windows 7 Ultimate Service Pack 1 \n * Windows 7 Enterprise Service Pack 1 \n * Windows 8 Professional Edition \n * Windows 8.1 Professional Edition \n * Windows 10 Professional Edition \n * Windows 10 Enterprise Edition\n\n * Microsoft Outlook 2007 Service Pack 3 \n * Microsoft Outlook 2010 Service Pack 2 \n * Microsoft Outlook 2013 \n * Microsoft Outlook 2016\n\n * .NET Framework 4.5 (or later)\n\nYou can install the IBM Content Collector Outlook Extension irrespective of the language in which Outlook is installed.\n\nAn Outlook logon profile containing the parameters for the connection to the Exchange server must exist.\n\nThere are different Outlook extension installable to be used with 32-Bit and 64-Bit versions of Microsoft Outlook * Mozilla Firefox 14, 17 or 24 ESR, 24, 28, 31 ESR, 32, 33, 34, or 35 \n * Microsoft Internet Explorer 8, 9, 10, or 11 \n * Microsoft Edge \n * Chrome 60\n\nMicrosoft Outlook 64 Bit version is supported starting with IBM Content Collector 4.0.1 Fix Pack 8 with Outlook Extension (64-bit) installable.\n\nWindows 10, Microsoft Edge and Microsoft Outlook 2016 are supported starting with IBM Content Collector 4.0.1 Fix Pack 2.\n\nChrome browser is supported starting with IBM Content Collector 4.0.1 Fix Pack 6\n\nVIRTUALIZATION\nThe following table describes the supported virtualization methods and software versions for running Outlook Extension on Citrix:\n\n\nVirtualization Method Required software Virtual desktop Microsoft Outlook 2010\nCitrix XenDesktop 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop 7.6 or later Hosted application in your datacenter Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later Local Access App Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later Microsoft Application Virtualization applications (App-V) Microsoft Outlook 2010\nCitrix XenDesktop\/Citrix XenApp 7.5 or later\nMicrosoft Outlook 2013\nCitrix XenDesktop\/Citrix XenApp 7.6 or later \n\n\nOUTLOOK WEB APP (OWA)\n Outlook Web App (OWA) Extension\n\nTo install the IBM Content Collector Outlook Web App Extension on the Exchange server, the following requirements must be met: \n\nExchange Server version (required) Other software requirements Notes * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2 \n * Microsoft Exchange Server 2013 SP1 \n * Microsoft Exchange Server 2016 \n\n.NET Framework 4.5 Full Profile (or later) The OWA Extension must be installed on the Exchange Server that has the Client Access Server (CAS) role. Outlook Web App (OWA) Service\n\nApart from the Outlook Web App Extension that is installed on the Exchange server, the Outlook Web App Service is installed on top of a Microsoft Internet Information Service (IIS) Server. The following table lists the operating system and other requirements for the OWA Service.\n\n \n\nExchange Server version Operating system for the Outlook Web App Service (required) Other software requirements * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * Windows Server 2008 Service Pack 2 \n * Windows Server 2008 R2 Service Pack 1\n\n * Microsoft IIS Server 6 or 7 \n * .NET Framework 4.5\n\n * Microsoft Exchange Server 2013 SP1\n\n * Windows Server 2008 R2 Service Pack 1 \n * Windows Server 2012 R2\n\n * Microsoft IIS Server 7.5 (or later)\n\n * Microsoft Exchange Server 2016 \n\n * Windows Server 2012 \n * Windows Server 2012 R2\n\n * .NET Framework 4.5.2\n\nIn the Internet Information Service (IIS) Manager: \n\n * Set the Web Service Extension ASP.NET V4.5 to Allowed. \n * Set the identity of the application pool where the OWA service resides to NetworkService. \n * Set the .NET Framework version to v4.5 \n * Disable the forms authentication method for the OWA Service (afuowa) after the installation. IBM Content Collector OWA Service does not support forms authentication in Microsoft IIS 7.0. \n\n\nHow to get: \n\nYou can purchase Microsoft IIS Server and .NET Framework from www.microsoft.com [http:\/\/www.microsoft.com].\n\n\nOutlook Web App (OWA) client \n\nTo be able to use the Outlook Web App functions, clients require the following software on their workstations: \n\n \n\nExchange Server version Software prerequisites for OWA clients * Microsoft Exchange Server 2007 Service Pack 3 (or later) \n * Microsoft Exchange Server 2010 SP2\n\n * .NET Framework 2.0 (or later) \n * Microsoft Internet Explorer 8, 9, or 10\n\n * Microsoft Exchange Server 2013 SP1\n\n * Microsoft Internet Explorer 9, 10 or 11 \n * Google Chrome 13 \n * Microsoft Edge\n\n * Microsoft Exchange Server 2016 \n\n * Microsoft Internet Explorer 10 or 11 \n * Microsoft Edge\n\nThe following restrictions apply: \n\n * IBM Content Collector OWA support does not work with if the option \"Use the blind and low vision experience\" in the OWA settings is used. \n * IBM Content Collector OWA support works only with OWA Premium Mode. \n * IBM Content Collector OWA support on Exchange 2010 supports only the Internet Explorer browser and not Apple Safari, Mozilla Firefox, and so on although Microsoft OWA 2010 supports other browsers. \n * IBM Content Collector OWA support on Exchange 2013 supports the Google Chrome browser in Apple Mac OS X 10.9.x (32-bit and 64-bit) \n * Microsoft Edge is supported starting with IBM Content Collector 4.0.1 Fix Pack 2 \n * IBM Content Collector OWA support on Exchange 2016 is supported starting from IBM Content Collector 4.0.1 Fix Pack 3 Back to top\n \n \n \n \n \n\nSMTP EMAIL\nIBM Content Collector can archive SMTP\/MIME email. The source mail system requires a specific setup to send all SMTP\/MIME email to be processed to IBM Content Collector. \nIn addition to SMTP forwarding for Microsoft Exchange and Lotus Domino, the respective setup has been tested for these mail systems:\n\n\n\nMail system Notes Microsoft Exchange Online See technote 1648828 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21648828] for information about how to set up journal forwarding from Microsoft Exchange Online to IBM Content Collector. Google Mail for Business See technote 1648572 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21648572] for information about archiving email from Google Mail for Business with IBM Content Collector. \nBack to top\n\nMICROSOFT SHAREPOINT\nThe following table describes the supported versions of Microsoft SharePoint: \n\n \n\nMicrosoft SharePoint Notes Microsoft SharePoint Server 2010 with Service Pack 2 (Standard or Enterprise edition) [\/support\/docview.wss?uid=swg27042658&aid=1] Microsoft SharePoint Foundation 2010 with Service Pack 2 Microsoft SharePoint Server 2013 with Service Pack 1 (Standard or Enterprise edition) Only functionality that is also provided by Microsoft SharePoint 2010 is supported. Microsoft SharePoint Foundation 2013 with Service Pack 1 Microsoft SharePoint Server 2016 (Standard and Enterprise edition) Only functionality that is also provided by older Microsoft SharePoint servers is supported. \nMicrosoft SharePoint Foundation edition is no longer available in the SharePoint Server 2016 release. As an alternative end users can use 180 days trial for Standard or Enterprise edition.\n\nHow to get:\nYou can purchase Microsoft SharePoint from www.microsoft.com [http:\/\/www.microsoft.com].\n\nBack to top\n\nIBM CONNECTIONS\n\nThe following table describes the supported versions of IBM Connections: \n\n \n\nIBM Connections IBM Connections 4.5 Documents from IBM Connections can be archived in the following archive systems: \n\n * IBM Content Manager Enterprise Edition (all supported versions) \n * IBM FileNet P8 Content Engine 5.1 or later with IBM Content Search Services\n\nHow to get: \n\nYou can purchase IBM Connections from the following website: IBM Connections [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034473].\n\nBack to top\n\nFILE SYSTEM SUPPORT\nThe following table describes supported file systems. \n\nFile system Notes NTFS V3.1\n\nDepending on the repository capabilities, the maximum supported file size is up to 30 GB.\n\nIBM Content Collector supports Microsoft SMB Protocol versions 1.0, 2.0 and 3.0 for Windows file server ReFS (Windows 2012) Novell Netware V6.5 SP 8 Novell Open Enterprise Server 2 SP3\nNovell Open Enterprise Server 11 Samba V3.3 Services for NFS for Windows 2008, 2008 R2, 2012, 2016 Windows Server 2016 is supported as File System collection source starting with IBM Content Collector 4.0.1 Fix Pack 8\n\nRestriction: If IBM Content Collector is installed on Windows 2008 and you are archiving from Novell file servers, Novell Client 2 SP1 IR 6 or later must be installed. \n\nThe File System Repository Connector also allows for archiving to cloud file systems. \n\n\nBack to top\n\n\n\nARCHIVE SERVERS\nIBM CONTENT MANAGER\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the connector that is required on the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required connector on IBM Content Collector Server Notes IBM Content Manager Enterprise Edition V8.4.2 Fix Pack 3 and V8.4.3 Fix Pack 3\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27036382]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3. Use the Setup Type Connector.\n\nSupport for IBM Content Manager V8.4 on Linux requires a Linux 32-bit system on an Intel platform or Linux for System z. For details, see the technote Content Manager Enterprise Edition Version 8.4 support for 32-bit \/ 64-bit for Linux\/UNIX\/Windows [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21293849].\n\nImportant: For IBM Content Manager Enterprise Edition V8.4.3, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 on AIX, text search requires IBM Content Collector Text Search Support V4.0.\n\nImportant: For IBM Content Manager Enterprise Edition V8.5, apply the fix that is described in Security Bulletin: Content Manager Enterprise Edition and use of Oracle Outside In Technology Security Vulnerability (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660964]. IBM Content Manager Enterprise Edition V8.5 Fix Pack 4\n\nFor the required level of the database management system, see the IBM Content Manager system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038464]. * AIX \n * Linux \n * Windows\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5 Fix Pack 4. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nConfigure item types to be enabled for indexing by Net Search Extender and not DB2 Text Search.\n\nIf you use IBM Content Manager Version 8.5 Fix Pack 4 on AIX, text search requires IBM Content Collector Text Search Support V4.0. IBM Content Manager for z\/OS Version V8.4.2, V8.4.3, and V8.4.3 Fix Pack 1\n * z\/OS\n\nIBM Content Manager Version 8 connector The connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3, V8.4.3, or V8.4.3 Fix Pack 1. Use the Setup Type Connector.\n\nIBM Content Manager for z\/OS can be used as a repository for files and Microsoft SharePoint documents. Email documents are supported starting with V8.4.3 Fix Pack 1. Text search is not supported. IBM Content Manager for z\/OS V8.5 * z\/OS\n\nIBM Content Manager Version 8 connector On 64-bit systems, the connector is provided by the configuration manager that is included in IBM Content Manager Enterprise Edition V8.5. On 32-bit systems, the connector is provided by IBM Information Integrator for Content V8.4.2 Fix Pack 3 or V8.4.3 Fix Pack 3.\n\nText search is not supported. How to get:\nYou can purchase IBM Content Manager from the following websites:\n\n\n * Content Manager Enterprise Edition [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035460]\n * Content Manager for z\/OS [http:\/\/www.ibm.com\/software\/products\/us\/en\/conmanzos]\n\nTEXT-SEARCH FUNCTION\nTo enable the text-search function (full-text search) for a Content Manager archive system, the IBM Content Collector indexer for text search must be installed. While IBM Content Collector supports archiving to Content Manager archive systems with DB2 databases or Oracle databases, the text-search function is not supported for archive systems with Oracle databases.\n\n The indexer for text search requires IBM Content Manager Enterprise Edition and the following software:\n\nNet Search Extender\nThe required version depends on the version of DB2 that is used by IBM Content Manager. Additional Net Search Extender e-fixes (required) Notes AIX Power 6.1 and 7.1 IBM Net Search Extender 9.1 for DB2 V9.1 Fix Pack 8 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24024133] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] IBM Net Search Extender and the required fix packs and e-fixes must be installed on the IBM Content Manager server. Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.5 for DB2 V9.5 Fix Pack 5 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24025481] Windows\n\nIC58821\nIP22989 Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 9.7 for DB2 V9.7 Fix Pack 4 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029745] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.1 for DB2 V10.1 Fix Pack 2 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24033997] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 AIX Power 6.1 and 7.1 IBM Net Search Extender 10.5 for DB2 10.5 Fixpack 6 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24040522] [\/support\/docview.wss?uid=swg27042658&aid=1] [\/support\/docview.wss?uid=swg27042658&aid=1] Linux or Linux for System z (RHEL) 5.0 and 6.0\nLinux (SLES) 10 and 11 Windows Server 2008, 2008 R2, and 2012 How to get: \n\nYou can download IBM Content Manager fix packs and Net Search Extender e-fixes from the following websites:\n\n * Content Manager fix packs [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27009038]\n * Net Search Extender e-fixes [ftp:\/\/public.dhe.ibm.com\/ps\/products\/db2extenders\/fixes]\n\nBack to top\n\nIBM FILENET P8\nREPOSITORY SOFTWARE\nThe following table describes the supported operating systems and the FileNet APIs that are required for the IBM Content Collector server: \n\nArchive system (repository software) Operating system Required APIs on IBM Content Collector Server Notes IBM FileNet P8 Content Engine 5.0.0.1, 5.1 Fix Pack 2, 5.2, or 5.2.1 \n\nFor the required level of the database management system, see the IBM FileNet P8 system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27013654]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the FileNet P8 Content Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the FileNet P8 Content Engine Client installer. [\/support\/docview.wss?uid=swg27042658&aid=1] Important: For IBM FileNet P8 Content Engine 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. IBM Content Foundation V5.2 or V5.2.1 \n\nFor the required level of the database management system, see the IBM Content Foundation system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27038265]. * AIX \n * Linux \n * Solaris \n * Windows\n\n.NET Clients The .NET Clients component is provided through the IBM Content Foundation Content Platform Engine installer. Java Clients (Other Applications) The Java Clients component is provided through the IBM Content Foundation Content Platform Engine installer. [\/support\/docview.wss?uid=swg27042658&aid=1] Important: For IBM Content Foundation V5.2.0, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. IBM FileNet Image Services 4.1.2 or 4.2 * AIX \n * HP-UX \n * Solaris \n * Windows\n\nIBM FileNet IDM Desktop IBM FileNet Image Services can only be used as a repository for files. It is not suitable for email. Text search and retrieving archived content through stub links is not supported. If you use IBM FileNet P8 with IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported.\n\nImportant: The fix pack level of the Content Engine of IBM Content Collector Server must match the fix pack level of the Content Engine server for both the .NET Clients and the Java Clients components.\n\nHow to get: \n\nYou can purchase FileNet P8 from the following websites:\n\n\n * FileNet Content Manager [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034227]\n * Content Foundation [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034868]\n * FileNet Image Services [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24020652]\n\nTEXT-SEARCH FUNCTION\nThe text-search function (full-text search) for FileNet archive systems with IBM Legacy Content Search Engine requires Autonomy IDOL K2. With IBM Legacy Content Search Engine (Verity), dynamic retention management is not supported\n\nTo use the text-search function (full-text search) for FileNet archive systems with IBM Content Search Services, IBM Content Collector Content Search Services Support must be installed on the Content Search Services server. If the Content Search Services server runs on AIX, Linux, or Solaris, ensure that Java 1.6 is installed. \n\nContent Search Services Support requires the following FileNet P8 components: \n\n\nFileNet P8 components Required on which server Operating system Notes IBM FileNet P8 Content Engine 5.1 Fix Pack 3 with IF001 or later, or 5.2 Fix Pack 2 with IF001 or later, or 5.2.1\nIBM Content Foundation V5.2 or V5.2.1 FileNet P8 Content Engine server * AIX \n * Linux \n * Solaris \n * Windows\n\nInterim Fixes are available on Fix Central [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=FileNet+Product+Family&product=ibm\/Information+Management\/FileNet+Content+Engine&release=5.1.0.0&platform=All&function=all].\n\nThe FileNet P8 Content Engine server must be configured to use Content Search Services. IBM FileNet P8 Content Search Engine Client 5.1 Fix Pack 2 or Content Search Engine Client 5.2 Content Search Services server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe client component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. IBM FileNet P8 Content Search Services 5.1 with IF005 or later, or 5.2 with IF002 or later, or 5.2.1\n\nFor details about the supported operating systems, see the IBM FileNet P8 system requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27013654]. Content Search Services server * AIX \n * Linux \n * Windows\n\nInterim Fixes are available on Fix Central [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=FileNet+Product+Family&product=ibm\/Information+Management\/FileNet+Content+Search+Services&release=5.1.0.0&platform=All&function=all].\n\nImportant: For IBM FileNet P8 Content Search Services 5.1 and 5.2, apply the fix that is described in Security Bulletin: IBM FileNet Content Manager and IBM Content Foundation \u2013 Oracle Outside In Technology security vulnerabilities (CVE-2013-5791, CVE-2013-5763) [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21660219]. Java Clients (Other Applications) 5.1 Fix Pack 2 or 5.2 * Content Search Services server \n * IBM Content Collector server\n\n * AIX \n * Linux \n * Solaris \n * Windows\n\nThe Java Clients component is provided through the FileNet P8 Content Engine Client 5.1 installer or the FileNet P8 Content Engine 5.2 installer. .NET Clients 5.1 Fix Pack 2 or 5.2 IBM Content Collector server * AIX \n * Linux \n * Solaris \n * Windows\n\nThe .NET Clients component is provided through the FileNet P8 Content Engine installer. \nThe text-search function (full-text search) for IBM Content Foundation requires the Content Search Services component. Back to top\n\n\n\nLEGACY RESTORE\n\nLegacy restore provides access to documents that were archived with IBM CommonStore for Lotus Domino or IBM CommonStore for Exchange Server. Legacy restore supports the same archive systems as the CommonStore products and has the same system requirements to connect to these archive systems as the CommonStore products:\n\nSystem requirements for IBM CommonStore for Lotus Domino [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27010342]\nSystem requirements for IBM CommonStore for Exchange Server [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27010343]\n\nIn addition, Legacy Restore also supports the archive systems IBM Content Manager Enterprise Edition V8.5 and IBM Content Manager for z\/OS V8.5. \n\nThere are some limitations when using IBM Content Collector Legacy Restore instead of the CommonStore products, including the following restrictions: \n\n * IBM Content Collector Legacy Restore provides read-only access to documents, but no write access. \n * For documents that are stored in Content Manager OnDemand or Content Manager for z\/OS, search is not supported. \n * For multi-part document model item types in Content Manager 8, only the first part can be previewed.\n\nIBM Content Collector Legacy Restore supports the same operating systems as IBM Content Collector Server. \n\nBack to top\n\n\n\n\n\n\nRETENTION POLICY DISTRIBUTION SUPPORT\nTo use IBM Content Collector Retention Policy Distribution Support, you must install IBM Atlas Policy Suite, which is the client interface in Global Retention Policy and Schedule Management for managing document retention schedules.\n\nThe following table describes the supported versions of IBM Atlas Policy Suite:\n\n\n\nIBM Atlas Policy Suite IBM Atlas Policy Suite 6.0.3 How to get: \n\nYou can purchase IBM Atlas Policy Suite from the following website: IBM Atlas Policy Suite [https:\/\/www.ibm.com\/support\/entdocview.wss?uid=swg24036335]. \n\nBack to top\n\n\n\n\n\n\nOPTIONAL SOFTWARE\nThe following table describes the software that is required if you want to use optional functions of IBM Content Collector:\n\nFunction Software Use IBM eDiscovery Manager to search and collect archived documents IBM eDiscovery Manager V2.2.1 or V2.2 Fix Pack 4 Use IBM Content Classification to classify documents IBM Content Classification V8.8 Declare records against documents in a FileNet P8 archive system IBM Enterprise Records V5.1.1, V5.1.2, or V5.2 Fix Pack 1 Access documents in an archive system IBM FileNet Workplace XT V1.1.5 Fix Pack 1 or Fix Pack 2\nIBM Content Navigator V2.0, V2.0.1, V2.0.2, V2.0.3, V3.0 or V3.0.1 How to get: \n\nYou can purchase these products from the following websites:\n\n * IBM eDiscovery Manager [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035931]\n * IBM Content Classification [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24029115]\n * IBM Enterprise Records [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24035858]\n * IBM Content Navigator [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg24034327]\n\nBack to top\n\n\n\nIBM CONTENT COLLECTOR PRODUCT REPORTS\nCONTENT COLLECTOR FOR EMAIL\nREQUIREMENTS\nBY PLATFORM\n * Mac OS [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Mac OS]\n\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&osPlatforms=Windows]\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1385722855736]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862A48C058E511E3A11D923472D26C14]\n * Legacy Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8626C65058E511E3A11D923472D26C14]\n * Notes Client Extension [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862AE50058E511E3A11D923472D26C14]\n\n * Outlook Extension [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Desktop_862BA85058E511E3A11D923472D26C14]\n * Outlook Web App Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862789A058E511E3A11D923472D26C14]\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_862825E058E511E3A11D923472D26C14]\n\n * SharePoint Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8628E93058E511E3A11D923472D26C14]\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1385722855736&duComponentIds=Server_8629857058E511E3A11D923472D26C14]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR FILE SYSTEMS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6D064B0C7E811E4A93F4F818B63D91A]\n\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C89C80C7E811E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=F4E90710C7E811E4A93F4F818B63D91A&duComponentIds=Server_F6C9D500C7E811E4A93F4F818B63D91A]\n\n\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR IBM CONNECTIONS\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE258D0C7ED11E4A93F4F818B63D91A]\n\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE035F0C7ED11E4A93F4F818B63D91A]\n\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=1B231CA0C7ED11E4A93F4F818B63D91A&duComponentIds=Server_1CE1BC90C7ED11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n \n\n\n\n\n Back to top \n\nCONTENT COLLECTOR FOR MICROSOFT SHAREPOINT\nREQUIREMENTS\nBY PLATFORM\n * Windows [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&osPlatforms=Windows]\n\n\n * Supported Hypervisors [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/vesForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nREQUIREMENTS\nBY COMPONENT\n * FileNet P8 Content Search Services Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3176240C7EB11E4A93F4F818B63D91A]\n * Server [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3151850C7EB11E4A93F4F818B63D91A]\n\n * SharePoint Support [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E315DBA0C7EB11E4A93F4F818B63D91A]\n * Text Search Support for Content Manager [http:\/\/www.ibm.com\/software\/reports\/compatibility\/clarity-reports\/report\/html\/softwareReqsForProduct?deliverableId=E13A64E0C7EB11E4A93F4F818B63D91A&duComponentIds=Server_E3169EF0C7EB11E4A93F4F818B63D91A]\n\n\n\n\nRELATED REQUIREMENTS\nNo related requirements.\n\n\n\n\n Back to top"}]},{"id":"DEV_Q254","question":"Why do I receive the message, \"IKJ79154I INSTALLATION EXIT IKJEESX0 REQUESTED TERMINATION. \" for a TSO SEND command?\n\nIf you issue the TSO SEND command in a batch job and receive this message:\n\nIKJ79154I INSTALLATION EXIT IKJEESX0 REQUESTED TERMINATION.\nIKJ79154I REASON CODE X'00000004'.","answer":"coded a facility class for the FEK.CMD.SEND and FEK.CMD.SEND.CLEAR.","is_impossible":false,"contexts":[{"filename":"swg21980860.txt","text":"Title: IBM RDz TSO EXIT IKJEESX0 TERMINATES with RC04 - United States\n\nText:\nIKJEESX0 TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n IBM Rational Developer for z Systems (RDz) using TSO Send command may result in the error IKJ79154I for TSO EXIT IKJEESX0, RC 04\n\n\nSYMPTOM\nIssuing the TSO SEND command in a batch job may terminate with this message: \n\nIKJ79154I INSTALLATION EXIT IKJEESX0 REQUESTED TERMINATION. \nIKJ79154I REASON CODE X'00000004'. \n\n\nCAUSE\nThe RDz TSO Send command will invoke a TSO exit, IKJEESX0 (FEKEESX0) that will terminate with a reason code of 4 if you have not coded a facility class for the FEK.CMD.SEND and FEK.CMD.SEND.CLEAR.\n\nThe exit provided by RDz checks to see if the user has the authority to issue the TSO Send command by executing the RACROUTE macro:\n\n\nRACROUTE REQUEST=AUTH,CLASS=(R5),ENTITYX=(rEntityBL), *\nWORKA=(R0),RELEASE=2.2,ATTR=READ,LOG=NOSTAT, *\nMF=(E,AUTHCHK) \n\n\n\n\nRESOLVING THE PROBLEM\nCode the appropriate security definitions for FEK.CMD.SEND and FEK.CMD.SEND.CLEAR. \n\nBelow is an example from the Knowledge Center > Configuring > Host Configuration Guide that will allow everyone to send messages, and only users able to issue operator commands to clear the message buffer: \n\n \n\n\nRDEFINE FACILITY (FEK.CMD.SEND.**) UACC(READ) -\nDATA('z\/OS EXPLORER - SEND COMMAND') \n\n\nRDEFINE FACILITY (FEK.CMD.SEND.CLEAR.**) UACC(NONE) -\nDATA('z\/OS EXPLORER - CLEAR SEND BUFFER') \n\n\nPERMIT FEK.CMD.SEND.CLEAR.** CLASS(FACILITY) -\nID(STCRSE) ACCESS(READ) \n\n\nSETROPTS RACLIST(FACILITY) REFRESH \n\n\n\nRELATED INFORMATION\n RDz V9.5 Knowledge Center Host Configuration Guide [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSQ2R2_9.5.0\/com.ibm.guide.hostconfig.doc\/topics\/sendmsg.html?lang=en]\nzOS Explorer 3.0 Knowledge Center Host configuration Gu [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSBDYH_3.0.0\/com.ibm.zexpl.config.hostconfig.doc\/topics\/sendmsg.html?lang=en]"}]},{"id":"DEV_Q255","question":"The BPM Messaging engine is not active after DB2 Fix Pack upgrade. How to resolve this problem?\n\nThe database used by BPM was recently upgraded to 10.1 Fix Pack 4.After the upgrade, the messaging engine cluster is not started up\n\nHow can I resolve this issue?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q256","question":"mqsireportdbparms missing?\n\nThe mqsireportdbparms command described in the following knowledge center topic is missing from the IIB installation.\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/# !\/SSMKHH_9.0.0\/com.ibm.etools.mft.doc\/an09156_.htm (http:\/\/www-01.ibm.com\/support\/knowledgecenter\/# %21\/SSMKHH_9.0.0\/com.ibm.etools.mft.doc\/an09156_.htm)","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q257","question":"How to control SDMS database size?\n\n\n\nHi,\n\nITCAM 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?\n\nThanks","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.","is_impossible":false,"contexts":[{"filename":"swg21959281.txt","text":"Title: IBM ITCAM for SOA KD4SDMS database size grows - United States\n\nText:\nCAMSOAALL 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."}]},{"id":"DEV_Q258","question":"What is the meaning of value \"unknown\" for ITCAM WAS Application Status attribute?\n\nI am getting alerts from a situation containing the following statement in its formula\n\n*IF *VALUE Application_Health_Status.Application_Status *NE Running\n\nI've found out this happens because the application status for one application is \"Unknown\" in the Application Health workspace.\n\nWhy was the application status\"Unknown\", what does it mean? ","answer":"If you see Unknown, then you know the baselining has not started or not been calculated.","is_impossible":false,"contexts":[{"filename":"swg21653905.txt","text":"Title: IBM How to enable Baselining in your monitored application. - United States\n\nText:\ntema enable baselining Unknown application health status CAMADALL CAMADINST TECHNOTE (FAQ)\n\nTHIS DOCUMENT APPLIES ONLY TO THE FOLLOWING LANGUAGE VERSION(S):\n US English \n\nQUESTION\n Steps to enable Baselining in your monitored application. \n\nANSWER\nThe health of the monitored application is calculated against an internally stored baseline threshold. The baselining of the application is a process that uses a pre-defined mathematical and statistical method to automatically calculate a threshold based on response time information typically collected over a period of time (few days to few weeks.) \n\nBy default baselining gets enabled with a situation WasAppDiscoverd. This situation is enabled by default and will discover new applications then run a take action to start the baselining. So if this situation is not enabled then you should enable it and assign to the ITCAM App Server managing system list. \n\nYou want to do baselining with normal or typical load on the server over a period of few days to few weeks, or even few months. The performance of the application under this load is considered good (you will see \"Good\"\" in the Application Health views) and deviation from this performance indicates degrading health (\"Bad\" or \"Fair\" in the Application Health views) of the monitored application. \n\nTo start baselining for your application server, please follow these steps: \n\n(Note 1: in this example, I've used a WebSphere-based application but you can also do the same for any application on your J2EE agent also.) \n\n(Note 2: Before beginning baselining, make sure you have typical or normal load on the server to set the baselining threshold values.) \n\n1. Login to your TEPS, select Application Health, right-click on it, go to Workspace and select Application Registry. Look at the panels on the right and observe the baselining columns. If they're blank, your baselining has not been started. \n\n2. Next select Application Health, right-click on it, go to Workspace and select Application Health status. If you see Unknown, then you know the baselining has not started or not been calculated. \n\n3. High-lite your application, select the small yellow chain link in the first unnamed column and select Application Configuration Details. See screenshot here: \n\n[\/support\/docview.wss?uid=swg21653905&aid=1] [\/support\/docview.wss?uid=swg21653905&aid=1] \n\n4. In the bottom panel on the right select the line that says All and high-lite it. Then right-click it, select Take Action and Select. In the pull-down, select Start_Baselining and enter the Period (2 days), Update_Interval (every 2 hours), and Run_Clean set to 1 (clean start.) If you wish, you can change these values to whatever you want. \n\nSee screenshots here:\n[\/support\/docview.wss?uid=swg21653905&aid=2] [\/support\/docview.wss?uid=swg21653905&aid=2]\n[\/support\/docview.wss?uid=swg21653905&aid=3]\nHit OK twice and you should get a Command completed successfully message. (Note: If you get a Baselining_Already_Active message in the pop-up window, then you should do another Take Action and Stop_Baselining first if you want to do the baselining again.)\n\nOnce you have the baselining active, let it run for the period of time with typical load on the server. After the baselining is complete, the Unknown values in the Application Health should now change to Good or Fair or Bad depending on threshold values.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Tivoli Composite Application Manager for Web Resources ITCAM for Web Resources (J2EE TEMA) AIX, HP-UX, Linux, Solaris, Windows, Solaris Opteron 6.1, 6.2 Advanced \nPRODUCT ALIAS\/SYNONYM\n ITCAM ITCAM4AD ITCAMfAD TEMA ITCAM for Web Resources"}]},{"id":"DEV_Q259","question":"Subnodes are still present on TEP after unconfiguring SOA DC\n\nAfter unconfiguring the ITCAM for SOA DC via the unconfig.sh script, I can still see SOA subnodes and workspaces on TEP.The Websphere instances were restarted and are no longer collecting data and forwarding to the D4 agent.I have shut down the ITCAM agent and deleted the offline entries for the managed systems, but the subnodes appear back once you restart the ITCAM agent.How can I remove them?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q260","question":"Crash happened due to \"PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577)\"\n\nCrash 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.","is_impossible":false,"contexts":[{"filename":"swg24041394.txt","text":"Title: IBM PI50993:Apache HTTPComponents vulnerabilities in WebSphere Application Server (CVE-2012-6153, CVE-2014-3577) - United States\n\nText:\nPI50993; 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"}]},{"id":"DEV_Q261","question":"Why is the reload() not clearing the attribute cache so I can see my newly updated LDAP data in real time?\n\nYou 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. Why is that?\n","answer":"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.","is_impossible":false,"contexts":[{"filename":"swg1PI47826.txt","text":"Title: IBM PI47826: VMM DOES NOT CLEAR THE CACHE IF CLEARENTITY MODE IS USED. - United States\n\nText:\n 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"}]},{"id":"DEV_Q262","question":"Table \"\".\"\" could not be found\n\n\n\nWhen doing a table mapping with DB2 as source, selecting a table which contains special characters on column comments like:\n\nCOMMENT ON COLUMN .. IS 'Test comment \u20181\u2019 complete';\n\nMapping fails with following error message: Table . could not be found in the database. What's the reason for the error?","answer":"During an insert of data using CLP characters, they do not go through codepage conversion.\nIf operating system and database codepage both are UTF-8, but the data to be inserted is not Unicode, then data in the database might have incorrect codepoints (not-Unicode) and the above error will be a result during data retrieval.","is_impossible":false,"contexts":[{"filename":"swg21412846.txt","text":"Title: IBM Wrong codepoints for non-ASCII characters inserted in UTF-8 database using CLP - United States\n\nText:\nCLP; insert; codepage; unicode; wrong codepoints; CharConversionException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n During insert from the CLP there is no codepage conversion if operating system codepage and database codepage are both UTF-8. In this case data to be inserted should also be in UTF-8 encoding.\n\nIf data has a different encoding then the database codepage (this can be verified using any hex editor), then the operating system codepage should be changed to match the data's encoding in order to enforce the data conversion to the database codepage. \n\nSYMPTOM\nError executing Select SQL statement. Caught by java.io.CharConversionException. ERRORCODE=-4220 \n\n Caused by: \njava.nio.charset.MalformedInputException: Input length = 4759 \nat com.ibm.db2.jcc.b.u.a(u.java:19) \nat com.ibm.db2.jcc.b.bc.a(bc.java:1762) \n\n\nCAUSE\nDuring an insert of data using CLP characters, they do not go through codepage conversion.\nIf operating system and database codepage both are UTF-8, but the data to be inserted is not Unicode, then data in the database might have incorrect codepoints (not-Unicode) and the above error will be a result during data retrieval. \n\nTo verify the encoding for data to be inserted you can use any editor that shows hex representation of characters. Please verify the codepoints for non-ASCII characters that you try to insert. If you see only 1 byte per non-ASCII characters then you need to force the database conversion during insert from CLP to UTF-8 database. \n\nTo force codepage conversion during insert from the CLP make sure that the operating system codepage is non-Unicode and matching to the codepage of data when you insert data to Unicode database from non-Unicode data source. \n\nProblem Details\nAn example problem scenario is as follows:\n\n\n 1. Create a database of type UTF-8:\n \n CREATE DATABASE <db> USING CODESET utf-8 TERRITORY US \n \n \n 2. Create a table that holds character data:\n \n CREATE TABLE test (col char(20)) \n \n \n 3. Check operating system locale:\n \n locale LANG=en_US.UTF-8 \n LC_CTYPE=\"en_US.UTF-8\" \n \n \n 4. Insert the non-ASCII characters '\u00c3' , '\u00b3', '\u00a9' which have codepoint 0x'C3', 0x'B3',0x'A9' in codepage 819 into the table:\n \n INSERT INTO test VALUES ('\u00c3')\n INSERT INTO test VALUES ('\u00b3')\n INSERT INTO test VALUES ('\u00a9') \n \n \n 5. By running the following statement, you can see that all INSERT statements caused only one byte to be inserted into the table:\n \n SELECT col, HEX(col) FROM test\n \n \n \u00c3 C3\n \u00b3 B3\n \u00a9 A9\n \n However, the UTF-8 representation of those characters are: 0x'C383' for '\u00c3', 0x'C2B3' for '\u00b3', and 0x'C2A9' for '\u00a9'.\n So these three rows in the table contain invalid characters in UTF-8. \n \n \n 6. When selecting from a column using the JDBC application, the following error will occur. This is expected because the table contains invalid UTF-8 data:\n Error executing Select SQL statement. Caught by java.io.CharConversionException. ERRORCODE=-4220\n Caused by:\n java.nio.charset.MalformedInputException: Input length = 4759\n at com.ibm.db2.jcc.b.u.a(u.java:19)\n at com.ibm.db2.jcc.b.bc.a(bc.java:1762) \n \n \n \n 7. Delete all rows with incorrect Unicode codepoints from the test table:\n DELETE * from test \n \n \n 8. Change the locale to one that matching codepage of data to be inserted:\n export locale=en_us. One of the way to determine the codepage for your data can be found here: http:\/\/www.codeproject.com\/Articles\/17201\/Detect-Encoding-for-In-and-Outgoing-Text [http:\/\/www.codeproject.com\/Articles\/17201\/Detect-Encoding-for-In-and-Outgoing-Text]. If you prepare data yourself using some editor please check the documentation for your editor to find out how to set up the codepage for data being prepared by the editor. \n \n \n 9. Insert data to the table:\n INSERT INTO test VALUES ('\u00c3')\n INSERT INTO test VALUES ('\u00b3')\n INSERT INTO test VALUES ('\u00a9') \n \n \n 10. Verify that inserted data were converted to UTF-8 during insert:\n SELECT col, HEX(col) FROM test\n \n \n \u00c3 C383\n \u00b3 C2B3\n \u00a9 C2A9 \n \n \n 11. Run your java application selecting Unicode data. No exception should be reported. \n\n\n\n\nENVIRONMENT\nUNIX, Linux, Unicode database\n\n\n\nDIAGNOSING THE PROBLEM\nVerify that non-ASCII data have a proper Unicode codepoints in Unicode database\n\n\n\nRESOLVING THE PROBLEM\nReinsert data with codepage conversion enforced by setting the operation system codepage matching to the codepage of data to be inserted\n\nRELATED INFORMATION\n Export data: [http:\/\/www.ibm.com\/developerworks\/db2\/library\/techarticle\/0210lau\/0210lau.html]"}]},{"id":"DEV_Q263","question":"How can I check the health of my IBM PureApplication System?\n\nHow can I check the health of my IBM PureApplication System?\nAre there steps to verify that my system is healthy? Is this something I can do, or does IBM have to verify the health of my system? ","answer":"Consider forwarding the PureApplication System Events to an external monitoring system, such as IBM Netcool\/OMIbus. and enabling the call home feature. \n\n \n\nWith PureApplication System firmware versions 2.1.0.1 or newer you can use the System Health check report to see a consolidated view of some of the PureApplication System UI pages. \n\nSystem > System Troubleshooting, click on System Health Check.","is_impossible":false,"contexts":[{"filename":"swg21675742.txt","text":"Title: IBM Health Checks and Introduction to Troubleshooting on a PureApplication System - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n This document describes how to check the health of your system, and when needed, where to start troubleshooting a problem on a PureApplication System. \n\nRESOLVING THE PROBLEM\nUse this document to confirm the health of your system. \n\nConsider forwarding the PureApplication System Events to an external monitoring system, such as IBM Netcool\/OMIbus. and enabling the call home feature. \n\n \n\nWith PureApplication System firmware versions 2.1.0.1 or newer you can use the System Health check report to see a consolidated view of some of the PureApplication System UI pages. \n\nSystem > System Troubleshooting, click on System Health Check. \n[\/support\/docview.wss?uid=swg21675742&aid=1] [\/support\/docview.wss?uid=swg21675742&aid=1] \n\nThe Lite Health Checks section lists a set of items which you can review every couple of days. These checks take about 15 minutes. \n\nFull Health Checks lists a set items you can review every week to help you confirm your system is operational. There are more checks in this section. \n\nIntroduction to Troubleshooting and Contacting IBM Support and sending in your information are included to help when the information found during a health check is not as expected. \n\nThe checks include accessing information on both the System and Workload console. You will need System and Workload administration access. \n\n\n\nLITE HEALTH CHECKS \nAlong with forwarding the events to a monitoring system, you might want to check the following items every couple of days. This should take about 15 minutes. \n\nIf the information displayed is not as expected, expand all sections of the web page and copy the page to a word processing document. Proceed to the Contacting IBM Support and sending in your information section of this document. Start with Step 1 where you will add this information from a word processing document. \n\n \n\n \n\nCheck Web Console Page Description High Availability Status of the system System Console > Troubleshooting, then expand the High Availability section. Under Service Code, the overall status should be \"Online\"when this feature is working properly. Problems System Console > System > Problems This view should be empty. However, if problems have been identified by the system, they will be listed here. \n\nYou can sort problems by any of the column headers. The \"Created on\" date is usually the most helpful. Investigate any problems that are reported here. When the issue has been resolved or determined to not be a real problem, delete the records. \n\nProblems are not automatically deleted from this view. It is important to delete problems on resolution. Problems are often (but not always) associated with Events. There may be some overlap between information in this view and that presented in the Event Viewer.\nSearch the Support Portal [http:\/\/www.ibm.com\/support\/entry\/portal\/product\/puresystems\/pureapplication_system]for content that may help you avoid opening a service request. Events System Console > System > Events Events which have been identified by the system will be listed here. You can sort Events by any of the column headers but the \"Updated on\" and \"Severity\" are usually the most helpful. Some of the events are from problems experienced by the workload users and are critical to that workload but not to the entire system. Look for \"critical\" and \"Call HOME events\" \nSearch the Support Portal [http:\/\/www.ibm.com\/support\/entry\/portal\/product\/puresystems\/pureapplication_system]for content that may help you avoid opening a service request.\n\nCompute Nodes System Console > Hardware > Compute Nodes Click on any Errors or Warning Events and review the \"Health statistic\" and other information on these pages. \n\nCheck that none of the nodes are in quiesced or stopped state. Click on each compute node in the system. Look for the word \"Temperature\". There are 2 values. Ambient Temperature and Maximum Ambient Temperature. Hover over the 'temperature icons' for these field to see the expected temperature range. \n\n\nOn the W1700, a compute node with an LED on might be an indication of a AIX Operation System problem on one if the Virtual Machines which is or was running. See: Node <node_nn> message: (System Event) system hardware failure, CMM Event: 77777703, Node Event: B200A101, Check log (Informational LED) is lit on compute node. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21669085] This is not a hardware problem\n\n\n\nManagement Nodes System Console > Hardware > Management Nodes Look at the status of elements and events associated with the two PureSystems Manager nodes and the other two. \n\nClick on any Errors or Warning Events and review the \"Health statistic\" and other information on these pages. \n\nOne of the PureSystem Managers should be marked as the leader with the word \"Primary\" in the \"Type\" field. \n\nAny errors that are listed for management nodes can indicate significant problems. Job Queue System Console > System > Job Queue. You want to ensure that jobs are starting and finishing on this page. \n\nCheck the Started Queue for failures. \n\nClick the check-box to show internal jobs to get a complete picture of the job queue. \n\nIt is quickest to sort by \"Status\" which will pull all failures to the top. Failures of individual deployment jobs should be reviewed with the team managing the system workload. Scan the information to look for pervasive system issues here. Failed Deployments Workload Console > Instances > All Instances Look over the list of all instances to find those that are failed that appear to be stuck initializing. \n\nA large number of deployments in these failed or stalled states can indicate system wide problems that should be investigated. A few failed or error deployments will occasionally be there because of the way that these systems are being used by the team managing the work loads. Confirm all is well with the team working on these projects. \n\nScan the information to look for pervasive system issues here. FULL HEALTH CHECKS \n\n\nAlong with forwarding the events to a monitoring system, you might want to check the following items every week. The \"Lite Health Check\" are included in the \"Full Health Check\" list below. \n\nIf the information displayed is not as expected, expand all sections of the web page and copy the page to a word processing document. Proceed to the Contacting IBM Support and sending in your information section of this document. Start with Step 1 where you will add more information to the word processing document. \n\n\nCheck Web Console Page Description High Availability Status of the system System Console > Troubleshooting, then expand the High Availability section. Under Service Code, the overall status should be \"Online\" when this feature is working properly. Temperature System Console > Hardware > Infrastructure Map Click on the \"Temperature\" in the top menu bar. \n\n \n\n\n\n\nCheck the temperature values for the system Hover over the value to see acceptable range for this value. When checking component status in the following checks, look at the Temperature readings for the component. \n\nThen check the temperature of each component in the following systems using the information under \"Component Status\" below. \n\nPrior to V2.0, the temperature check on the storage node component is incorrect. Check for events concerning storage node (V7000 Storewize ) component instead. \n\n\n\nComponent Status System Console > Hardware > Infrastructure Map \n\n\nFor the components in the system, check the status shown on the web page. \n\nIf there is a red \"!\" , in the picture of the rack, click on the icon. The \"Default section\" will be presented with more information. If there are numbers after the red \"!\", click on the number and review the events posted. Check the \"Updated on\" column to see when the event was posted. \n\n[\/support\/docview.wss?uid=swg21675742&aid=2] System Console > Hardware > Infrastructure Map Click on \"Switch to Tree View\" \n\nFlex Chassis > \n\nChassis Management Module\n\nCheck that there are 2 Chassis Management Modules (CMM) and a primary and secondary listed for each chassis. Look for any alerts and review the information shown on the web page. \nClick on each Chassis in the system. Look for the word \"Temperature\". There are 2 values. Ambient Temperature and Maximum Ambient Temperature. Hover over the 'temperature icons' for these field to see the expected temperature range. \n\n[\/support\/docview.wss?uid=swg21675742&aid=2] System Console > Hardware > Compute Nodes Click on any Errors or Warning Events and review the health statistic and other information on these pages. \n\nCheck that none of the nodes are in quiesced or stopped state. \nClick on each compute node in the system. Look for the word \"Temperature\". There are 2 values. Ambient Temperature and Maximum Ambient Temperature. Hover over the 'temperature icons' for these field to see the expected temperature range. \n\n \n\nOn the W1700, or W2700, a compute node with an LED on might be an indication of a AIX Operation System problem on one if the Virtual Machines which is or was running. See: Node <node_nn> message: (System Event) system hardware failure, CMM Event: 77777703, Node Event: B200A101, Check log (Informational LED) is lit on compute node. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21669085] This is not a hardware problem\n\n[\/support\/docview.wss?uid=swg21675742&aid=2] System Console > Hardware > Infrastructure > Management Node\n\nCheck the management nodes to make sure they are powered on and available. \n\nOne of the PureSystem Managers should have 'primary' in the type field. \n\nReview the \"Health statistic\" \n\nLook at the status of elements and events associated with the two PureSystems Manager nodes and the two Manager nodes. Click on any Errors or Warning Events and review the health statistic and other information on these pages. \n\nOne of the PureSystem Managers should be marked as the leader with \"Primary\" in the \"Type\" field. \n\nAny errors that are listed for any management nodes can indicate significant problems. [\/support\/docview.wss?uid=swg21675742&aid=2] System Console > Hardware > Storage Devices Look at all the Storage Nodes and Storage Node Expansions to make sure the Disk Drives, LUNs, and Storage Controller Ports are all available for each node. Prior to V2.0, the temperature check on the storage node component is incorrect. Check for events concerning storage node (V7000 Storewize ) component instead. \n\nIn V2. the temperature is under the \"Canister\" section. Hover over the temperature gauge icon to confirm the temperatures are normal. \n\nProblems System Console > System > Problems This view should be empty. \n\nHowever, if problems have been identified by the system, they will be listed here. You can sort problems by any of the column headers but the \"Created on\" date is usually the most helpful. Investigate any problems that are reported here and when the issue has been resolved or determined to not be a real problem, delete the records. \n\nProblems are not automatically deleted from this view. It is important to delete them on resolution. Problems are often (but not always) associated with Events. There may be some overlap between information in this view and that presented in the Event Viewer. Events System Console > System > Events Events which have been identified by the system they will be listed here. You can sort Events by any of the column headers but the \"Updated on\" and \"Severity\" are usually the most helpful. Some of the events are from problems experienced by the workload users and are critical to that workload but not to the entire system. \n\nJob Queue System Console > System > Job Queue. You want to ensure that jobs are starting and finishing on this page. \n\nCheck the Started Queue for failures. \n\nClick the check-box to show internal jobs to get a complete picture of the job queue. It is quickest to sort by Status which will pull all failures to the top. Failures of individual deployment jobs should be reviewed with the team managing the system workload. Scan the information to look for pervasive system issues here. Failed Deployments Workload Console > Instances > All Instances Look over the list of all instances to find those that are failed that appear to be stuck initializing. \n\nA large number of deployments in these failed or stalled states can indicate system wide problems that should be investigated. A few failed or error deployments will occasionally be there because of the way that these systems are being used by the team managing the work loads. Confirm all is well with the team working on these projects. Validate Shared Services Workload Console > Instances > Shared Services Validate that shared services are running for all appropriate cloud groups and appear to be in good health. Work with the local patterns administrator to confirm the list of shared services that should be running for this system. \n\nNOTE: It is not unusual for shared services to be stopped or not deployed for various reasons depending upon the use of the system. Check with the patterns administrator on the expected status of shared services. INTRODUCTION TO TROUBLESHOOTING \n\n\n 1. The first action is to open up a word processing document to capture the output of any the following steps which shows the problem. Use this technote entitled Organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] concerning the problem for IBM Support. Copy this template into your word processing document. \n 2. Check System Console > System > Problems This view should be empty. 1. However, if problems have been identified by the system, they will be listed here. You can sort problems by any of the column headers but the \n \"Created on\" is usually the most helpful. Investigate any problems that are reported here and when the issue has been resolved or determined to not be a real problem, delete the record. \n 2. Problems are not automatically deleted from this view. It is important to delete entries on resolution. Problems are often (but not always) associated with Events. There may be some overlap between information in this view and that presented in the Event Viewer. \n 3. Search the support portal [http:\/\/www.ibm.com\/support\/entry\/portal\/product\/puresystems\/pureapplication_system] [http:\/\/www.ibm.com\/]to see if there is an explanation of the message in the product documentation center, a technote, or APAR document. \n 4. Otherwise, if you have problem listed which you would like IBM to investigate, export the problem. Add this to the document created with the organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] technote. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n \n \n 3. Check the event log: System Console > System > Events 1. If Events have been identified by the system, they will be listed here. You can sort Events by any of the column headers but the \"Updated on\" and \"Severity\" are usually the most helpful. Investigate any problems. \n 2. Some of the Events are from problems experienced by the workload users and are critical to that workload but not to the entire system. Check with the workload users to see if they are testing or also finding problems. \n 3. Search the support portal [http:\/\/www.ibm.com\/support\/entry\/portal\/product\/puresystems\/pureapplication_system] to see [http:\/\/www.ibm.com\/] if there is an explanation of the message in the product documentation, a technote, or APAR document. \n 4. Check if the Event lists a hardware component and a hardware error. Look for the failing serial number, name or rack location number. 1. This document has a list of Events which you might see. Look under \"Check these known problems first\" in this technote. MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21666454] \n 2. Check the status of the hardware component via: System Console > Hardware > Infrastructure Map.Try the \"Switch to Tree View\" option. \n 3. If the symptoms describe an Event which requires investigation by IBM, save a copy of the information and gather the information listed in MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454] [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21666454]\n \n \n 5. Otherwise, if you find an Event which you would like IBM to investigate, save the Event. You can export the one event. Use the organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] technote to prepare to work with IBM Support. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n \n \n 4. Check the job queue: System Console > System >Job Queue 1. Under \"Started Jobs Queue\", check that jobs are running. If not, check the \"Display Internal Jobs\" check box. Refresh the screen using the \"double arrows' under the \"Started Jobs Queue\" line. Confirm that there were internal jobs running, and successfully completing. Wait 10 minutes. If there are no internal jobs running or completing, save a capture of this screen. Then obtain a system collection set for IBM Support. Use the organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] technnote to prepare to work with IBM Support. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n 2. Look at the \"Status\" column for failed jobs. Wait and check this page again as you want to ensure that jobs are moving in the Started Queue and that there are not a large number of failures. Failures of individual deployment jobs are usually not a concern unless all deployment jobs seem to be failing. \n 3. Consult with your team using the system to deploy business solutions to be sure these are expected failures, or that they are aware and working on the problem. \n 4. To help you debug failed deployments, gather files via the Work Load Console. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. \n 5. A \"Pending\" job is not actually running -- it is just queued up to run at some point in the future. The \"Internal Backup Job\" is queued up to run every day. You will always see this job in the queue as \"Pending\". \n 6. Otherwise, if you want IBM to investigate, use the organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] technote to copy the web page for IBM Support. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n \n \n 5. Check the storage nodes: System Console > Hardware > Storage Devices. Look at all the Storage Nodes and Storage Node Expansions to make sure the Disk Drives, LUNs, and Storage Controller Ports are all available for each node. 1. Check the \"Total\" and \"Available\" counts for Disk Drives, LUNS, and Ports. The values should be equal. \n 2. If there is a problem, click on the \"Generate\" button on the \"Request System Logs\" line on the web page. This technote describes how to save and sending the logs: in MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454] Proceed to the Contacting IBM Support and sending in your information section of this document.\n \n \n 6. Check the Management Nodes: System Console > Hardware > Management Nodes. Look at the status of elements and events associated with those elements. 1. There are two PureSystems Manage nodes and the two virtualization manager nodes. One of the PureSystem Managers should be marked as the leader with the word \"Primary\" in the \"Type\" field. Look for any errors that are listed for any management nodes as they can indicate significant problems. \n 2. If you do see a problem for IBM to investigate, click on the \"Generate\" button on the \"Request System Logs\" line on the web page. This technote describes how to save and sending the logs: MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454] Proceed to the Contacting IBM Support and sending in your information section of this document\n \n \n 7. Check the High Availability Status of the system: System Console > Troubleshooting, then expand the High Availability section. 1. In the table, there are service code and status column. The status column should show a status of \"Online\" when this feature is working properly. \n 2. If the status is not \"Online\", paste this RESTAPI into the browser URL and save the output: https:\/\/<rack_ip>\/admin\/resources\/service_status Copy this information into the word processing document and Proceed to the Contacting IBM Support and sending in your information section of this document \n \n \n 8. Check Chassis temperature: System Console > Hardware> Flex Chassis. Open the selection. There are 2 values: \"Ambient Temperature\" and \"Maximum Ambient Temperature\". Hover over the 'temperature icons' for these field to make sure the temperature is within range. If there is a red \"!\" , in the picture of the rack, click on the icon. The \"Default section\" will be presented with more information. 1. This document has a list of Events which you might see. One is concerning temperature. Look under \"Check these known problems first\" in this technote: MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454] \n 2. If there are numbers after the red \"!\", click on the number and review the events posted. Check the \"Updated on\" column to see when the event was posted. \n 3. If you do see a problem for IBM to investigate, click on the \"Generate\" button on the \"Request System Logs\" line on the web page. This technote describes how to save and send in the logs: MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454]. Proceed to the Contacting IBM Support and sending in your information section of this document\n \n \n 9. Check the Network Switches: System Console >Hardware-> Networking devices. Click on each switch. 1. Look on the Events line for the red \"!\". If there is a number, click on the number to investigate the Event posted by the system. \n 2. Confirm the switch shows the \"Power Status\" and \"Status\" as \"Available\". \n 3. If you do see a problem for IBM to investigate, click on the \"Generate\" button on the \"Request System Logs\" line on the web page. This technote describes how to save and send in the logs: MustGather: Chassis Management Module, IBM Storwize V7000, Top of Rack Switch, San Switch, and Management EndPoint problems for IBM PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21666454]. Proceed to the Contacting IBM Support and sending in your information section of this document\n \n \n 10. Check the DNS connectivity: System Console > Settings. Expand Domain Service (DNS) and use the \"Lookup host name or IP address\". Confirm you can connect to the expected IP addresses by IP and hostname. Consult with your team which manages the DNS sever for advice. \n 11. Check for failed deployments: Workload Console > Instances > All Instances. 1. A few failed or error deployments will occasionally be there because of the way that these systems are being used and should not be of concern. Confirm all is well with the team working on these projects. \n 2. A large number of deployments in these failed or stalled states can indicate system wide problems which should be investigated. Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n \n \n 12. The Troubleshooting chapters in the PureApplication System product documentation has more troubleshooting topics. \n 13. Otherwise, if you see other problems which you would like IBM to investigate, use the organize your problem information [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21654210] technote to copy the web pages into a document to show the problem to IBM Support. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] Check the MustGather Read first for PureApplication System [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21610259] for information to gather. Proceed to the Contacting IBM Support and sending in your information section of this document. \n\n\n \n\nCONTACTING IBM SUPPORT AND SENDING IN YOUR INFORMATION\n\n\nUse the following technotes to contact IBM Support and send in the MustGather information: \n\n * Contacting IBM PureApplication System Support [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21609051] to open a PMR. \n * Use the IBM Secure Diagnostic Data Upload Utility [http:\/\/www.ibm.com\/de\/support\/ecurep\/send_java-tool.html] also called the Java Utility to upload the PureApplication System [http:\/\/www.ibm.com\/de\/support\/ecurep\/send.html]collections to greatly reduce the time to upload large files. \n * Exchanging information with IBM PureApplication System Technical Support for problem determination. [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21596913] [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21596913] \n * Review the PureApplication System Customer Support Plan [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21613951] \n * Do not send any confidential information from your company."}]},{"id":"DEV_Q264","question":"Gettting error CRIMC1020E: zip im.properties not found during BPM Fix Pack install\n\nDuring the BPM 7.5.1.2 Fix Pack install from the IBM Installation Manager, error window pop up with:\nCRIMC1020E: zip im.properties 1.0.0.200911091101 not found ERROR: `zip im.properties 1.0.0.200911091101` not found in [path to sca.1.0.1.17.fp]. CRIMC1020E: zip config.registry 1.0.0.200911092301 not found\n\u2026\u2026\nHow can I resolve this error to complete the Fix Pack installation","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q265","question":"Will the Leap Second 2015 update have any impact with FileNet Content Manager?\n\nWill the Leap Second 2015 update have any impact with FileNet Content Manager?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q266","question":"How to install Packaging utility?\n\nHow to install Packaging utility? ","answer":"Use Installation Manager to install and update Packaging Utility.","is_impossible":false,"contexts":[{"filename":"swg24037641.txt","text":"Title: IBM Packaging Utility 1.8 - United States\n\nText:\nservice release; modpack; mod pack; upgrade; refresh; refresh pack DOWNLOADABLE FILES\n\nABSTRACT\n IBM Packaging Utility 1.8 has been made generally available and contains any fixes for client-reported and internally found defects. \n\nDOWNLOAD DESCRIPTION\n \n\nTable of Contents Sections Description * What's new\n\nThe Change history section provides an overview on what is new in this release with a description of any new functions or enhancements when applicable.\n\n * Impact assessment\n\nThe How critical is this fix section provides information related to the impact of this release to allow you to assess how your environment may be affected.\n\n * Prerequisites\n\nThe Prerequisites section provides important information to review prior to the installation of this release.\n\n * Download package\n\nThe Download package section provides the direct link to obtain the download package for installation in your environment.\n\n * Installation instructions\n\nThe Installation instructions section provides the installation instructions necessary to apply this release into your environment.\n\n * Known problems\n\nThe Known side effects section contains a link to the known problems (open defects) identified at the time of this release.\n\nSupporting Documentation Document Description * Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27036456]\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.\n\n * IBM Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.auth.ui.doc\/helpindex_pu.html]\n\nIBM Knowledge Center provides an entry point to product documentation. You can view, browse, and search online information related to the product.\n\n * Fix List [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27036454#tab_1.8]\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.\n\nPREREQUISITES\n \n\nPrerequisites include: Review the Detailed System Requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27036456] for any prerequisites required for this release.\n\nBack to top\n\nINSTALLATION INSTRUCTIONS\n \n\nUse Installation Manager to install and update Packaging Utility. If Installation Manager is installed, you can use the Packaging Utility repository on www.ibm.com to install or update Packaging Utility without downloading files. If Installation Manager is not installed, you must download the Packaging Utility files. Installation Manager is included in the Packaging Utility download packages.\n\nThe installer package for Packaging Utility is pu.offering.disk.platform_version.zip where platform indicates the operating system and version indicates the version of Packaging Utility. The installer package contains files for only one platform. Using this package, you can install Packaging Utility and Installation Manager by running the install command. You can also add this package as a repository in Installation Manager and use the package to update Packaging Utility.\n\nThe fix pack package for Packaging Utility is pu.update_version.zip. The fix pack contains files for all supported platforms. You can add this fix pack as a repository to update Packaging Utility. You cannot install Packaging Utility or Installation Manager with this fix pack.\n\nPackaging Utility is available in 64-bit mode. Review information information about bit mode for installation or updates: Packaging Utility bit mode information [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.auth.ui.doc\/topics\/r_pu_bit_mode.html].\n\nFor more information about Packaging Utility and Installation Manager, Review the Installation Manager Knowledge Center [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W\/im_family_welcome.html].\n\n\nINSTALL OR UPDATE PACKAGING UTILITY WITHOUT DOWNLOADING FILES\nYou must have Internet access and Installation Manager must be installed to install or update Packaging Utility without downloading files. The Packaging Utility repository located on www.ibm.com contains the latest version of Packaging Utility.\n\nYou must have an IBM user name and password to access the repository. To register for these credentials, go to: http:\/\/www.ibm.com\/account\/profile.\n\n\nIBM Knowledge Center topics that are specified by operating system for installing and updating Packaging Utility. The installation topics contain information about downloading the Installation Manager installation files. \n\nOperating System Action Packaging Utility topic located in the IBM Installation Manager Knowledge Center Windows\nLinux\nUNIX\nMac OS X operating system Installation Installing Packaging Utility in wizard mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.auth.ui.doc\/topics\/r_pu_wm.html] Installing Packaging Utility by using console mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_console_install.html] Installing or updating Packaging Utility by using imcl commands [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_install_imcl.html] Update Updating Packaging Utility in wizard mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.auth.ui.doc\/topics\/t_pu_update.html] Updating Packaging Utility by using console mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_console_update.html] Installing or updating Packaging Utility by using imcl commands [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_install_imcl.html] IBM z\/OS Installation Installing Packaging Utility by using console mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_console_install.html] Installing or updating Packaging Utility by using imcl commands [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_install_imcl.html] Update Updating Packaging Utility by using console mode [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_console_update.html] Installing or updating Packaging Utility by using imcl commands [http:\/\/www.ibm.com\/support\/knowledgecenter\/SSDV2W_1.8.0\/com.ibm.cic.commandline.doc\/topics\/t_pu_install_imcl.html] \nBack to top\n\nDOWNLOAD PACKAGE\n \n\nThe following sections provide detailed information related to this release.\n\nClick the FC link below to obtain the release from Fix Central.\n\n\n\nHOW CRITICAL IS THIS FIX?\n \n\nImpact Assessment Impact Description Recommended This is a service release. It contains new features as well as fixes for client-reported and internally found defects.\n\nTest Results\n\nClose [x]\n\nDEFINITIONS\nRegression: An error in the Maintenance Delivery Vehicle [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27008656] (MDV) that produces incorrect or unexpected behavior causing a supported feature to stop functioning as designed. \nThis includes: \n\n * Coding errors that cause a regression\n * Documentation or packaging problems that cause a regression\n * Errors reported in a new function delivered in a MDV that cause a regression\n\nIncomplete: An error in the MDV has not regressed, but does not work as designed. \nThis includes: \n\n * Fixed APARs which did not solve the original problem but did not break anything new\n * APARs reporting documentation errors, such as readme errors, that cause problems applying an MDV but do not lead to a regression\n\n\n\n\nNotes: * Regression and incomplete APARs are considered fix-in-error or MDV-in-error\n * Definitions above apply only to valid APARs that result in product fixes (APARs returned as working-as-designed are not assessed for being fix-in-error)\n * Issues in major releases due to new functionality do not apply in this definition\n\nThere are no known regressions to report.\n\nBack to top\n\n\n\nPROBLEMS SOLVED\n \n\nDefects resolved Click the Fix List link in the table of contents above to review a list of the problems solved in this release.\n\n\n\nKNOWN SIDE EFFECTS\n \n\nReview the following list of known issues and open defects: There are no known issues report.\n\nOPEN DEFECTS\nReview the following list of open defects for IBM Installation Manager and Packaging Utility [https:\/\/www-947.ibm.com\/support\/entry\/myportal\/search_results\/rational\/ibm_installation_manager?sn=spe&q=%22APAR%20status%22%20OPEN&prod=N340276G72802P18&filter=language:en&productContext=864296863#q%3D%22APAR%20status%22%20OPEN%26filter%3DDC.Type%3ACT748%2Blanguage%3Aen%26prod%3DN340276G72802P18] on the IBM Support Portal.\n\nReview technote 1461170: Open APARs for Rational products available on the Web [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21461170] for information on how to configure your MyNotifications subscription account and subscribe to the APARs you are interested in following.\n\nBack to top\n\n\n\nCHANGE HISTORY\n \n\nWhat's new No new features or functions.\n\nBack to top\n\nClick the link in the Download Options column:\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] Packaging Utility downloads (1.8) 11 Sep 2014 English 1 FC [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/quickorder?parent=ibm%7ERational&product=ibm\/Rational\/IBM+Packaging+Utility&release=All&platform=All&function=all&source=fc] [ ] \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"}]},{"id":"DEV_Q267","question":"Can you enable the reporter feature with IBM Rational Rhapsody Architect Software Floating license?\n\nCan you enable the reporter feature with IBM Rational Rhapsody Architect Software Floating license? ","answer":"The license features that come incorporated with IBM Rational Rhapsody Tools & Utilities Add on keys are as follows: \n\n * ReporterPro \n * Reporter","is_impossible":false,"contexts":[{"filename":"swg21606028.txt","text":"Title: IBM License features incorporated in \"Tools and Utilities\" key while generating Rational Rhapsody licenses - United States\n\nText:\nTools and Utilities; License Feature TECHNOTE (FAQ)\n\nQUESTION\n What are the features incorporated with the \"Tools and Utilities\" License key for IBM Rational Rhapsody? \n\nCAUSE\nYou would like to know all the features of the Tools and Utilities license key\n\nANSWER\nThe license features that come incorporated with IBM Rational Rhapsody Tools & Utilities Add on keys are as follows: \n\n * ReporterPro \n * Reporter \n * RPGetConnected \n * RPGetConnectedWind \n * RPGetConnectedVxw \n * RPGetConnectedSol \n * RPGetConnectedN \n * RPGetConnectedG \n * RPUNCS \n * RPTcSEAddon \n * RPGraphPanel \n * RPRG \n * RPRG_DOORS \n * RPRG_X2TXT \n * RPRG_REQPRO \n * RPRG_RP \n * RPRG_SIMULINK \n * RPRG_TAGGER \n * RPRG_CALIBERRM \n * RPUSimulink \n * RPXMI \n * RPTAUXMI\n\n\nNote: Important functionalities of Rational Rhapsody such as Gateway [ RPRG], Import and Export of XMI files in Rhapsody [RPXMI], Panel Diagrams [RPGraphPanel] and Reporter Plus [ReporterPro] among others are covered\n\nRELATED INFORMATION\n Rational DOORS license features [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21607708]\nRational TAU License features [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21608087]\nRational Build Forge features [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21608803]\nRational Dashboard [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21608812]"}]},{"id":"DEV_Q268","question":"ODR OOM issue\n\nI got ODR OOM after upgrading the WAS to v8553. No configuration or traffic load changing. Do I need a fix pack?","answer":"The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.9.","is_impossible":false,"contexts":[{"filename":"swg1PI53566.txt","text":"Title: IBM PI53566: ON DEMAND ROUTER MEMORY LEAK WHEN UPGRADING APPLICATIONS UNDER LOAD - United States\n\nText:\n FIXES ARE AVAILABLE\nPI53566:on demand router memory leak when upgrading applications under load [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24041964]\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.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24043844]\n8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg24044479]\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 * The On Demand Router (ODR) has a memory leak related to\n HttpRouteAction objects such that when the system is under load\n and there are configuration changes such as uninstalling and\n installing applications it is possible that multiple, redundant\n HttpRouteAction objects can be created with registered\n listeners for ODC tree changes but never removed. This will\n eventually fill up the available heap space and cause an Out Of\n Memory issue on the ODR. Restarting the ODR will correct the\n problem.\n \n \n \n \n \n\nLOCAL FIX\n * Restart the ODR.\n \n \n \n \n \n\nPROBLEM SUMMARY\n * ****************************************************************\n * USERS AFFECTED: All users of IBM WebSphere Application *\n * Server Intelligent Management using the *\n * java On Demand Router (ODR). *\n ****************************************************************\n * PROBLEM DESCRIPTION: An Out Of Memory error can be seen on *\n * the On Demand Router because *\n * HttpRouteAction objects can *\n * accumulate. *\n ****************************************************************\n * RECOMMENDATION: *\n ****************************************************************\n There is a code bug where HttpRouteAction objects can\n accumulate because they are not freed. This is particularly\n noticeable when there are routing rules present, many\n applications installed, and multiple configuration changes\n happening on the system (such as installing or removing\n applications). Over time this can cause exhaustion of the\n available heap and an Out Of Memory error for the On Demand\n Router.\n \n \n \n \n \n\nPROBLEM CONCLUSION\n * The area of code was corrected to release the HttpRouteAction\n objects. This fix supercedes PI51978 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1PI51978].\n \n The fix for this APAR is currently targeted for inclusion in\n fix pack 8.5.5.9. 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 PI53566\n \n \n * REPORTED COMPONENT NAME\n WEBSPHERE APP S\n \n \n * REPORTED COMPONENT ID\n 5724J0800\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-12-04\n \n \n * CLOSED DATE\n 2016-01-22\n \n \n * LAST MODIFIED DATE\n 2016-03-23\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 APP S\n \n \n * FIXED COMPONENT ID\n 5724J0800\n \n \n\nAPPLICABLE COMPONENT LEVELS\n * R700 PSY\n UP\n \n \n * R850 PSY\n UP"}]},{"id":"DEV_Q269","question":"Executing a scenario suite with a Scenario Service Provider (SSP) over HTTPS\n\nHow to configure the machines hosting the WebSphere Operational Decision Management modules with regard to HTTPS when executing scenario suites ?\nHow to avoid the exception below while requesting from Decision Center the execution of a scenario suite on Scenario Service Provider (SSP) over HTTPS ?\n Exception caught while contacting RES ilog.rules.res.util.http.IlrConnectionException: IO error when contacting \"\/res\/repositoryService\"\n ....\n Caused by: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: unable to find valid certification path to requested target","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q270","question":"What version \/ level of Java JRE and GSKit is included with each WebSphere MQ version?\n\nWhat version \/ level of Java JRE and GSKit is included with WebSphere MQ? for each MQ version? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q271","question":"Problem with Postal database in Parascript\n\n Hi\n\ni am working with Parascript and i have installed successfully in my local system by folloing this guide [ Parascript FieldScript for Taskmaster Guide ]\n\nhere i can able to create vocabulary file, but storing multiple values into this the values are overridden and i do not understand how to create a postal database and access it\n\nis that postal database is separate component ,,?? do we need to get somewhere and install ,,? they just mention in Guide the use of actions only\n\nand does this parascript really helps to get better recognize.","answer":"The address information in the USPS database on the data disk is automatically disabled 105 days after the date of issue. IBM refreshes the data disk on the 14th day of every month, or the previous business day. You must ensure that you obtain the refreshed data from Passport Advantage on a regular schedule so that you avoid issues that are associated with disabled address information.","is_impossible":false,"contexts":[{"filename":"swg24031674.txt","text":"Title: IBM Download Parascript FieldScript for IBM Datacap Taskmaster Capture V8.0.1, V8.1.0, and IBM Datacap V9.0.0. - United States\n\nText:\n DOWNLOADABLE FILES\n\nABSTRACT\n This document contains information about obtaining Parascript FieldScript for IBM Datacap Taskmaster Capture Versions 8.0.1 and 8.1.0, and for IBM Datacap Version 9.0.0. \n\nDOWNLOAD DESCRIPTION\nParascript FieldScript for IBM Datacap Versions 8.0.1, 8.1.0, and 9.0.0, and the associated data disk that contains the United States Postal Service (USPS) database are available for download only through Passport Advantage. \n\nThe address information in the USPS database on the data disk is automatically disabled 105 days after the date of issue. IBM refreshes the data disk on the 14th day of every month, or the previous business day. You must ensure that you obtain the refreshed data from Passport Advantage on a regular schedule so that you avoid issues that are associated with disabled address information.\n\nPREREQUISITES\nSee the following website for detailed system requirements.\n\nURL LANGUAGE SIZE(Bytes) Hardware and software requirements [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27043811] English 15234 \nINSTALLATION INSTRUCTIONS\nSee the Parascript(R) FieldScript(R) for IBM Datacap Taskmaster Capture Version 8.0.1 Guide for installation instructions.\n\nClick on the other links for related information.\n\nURL LANGUAGE SIZE(Bytes) Parascript FieldScript for Taskmaster Guide [http:\/\/www.ibm.com\/e-business\/linkweb\/publications\/servlet\/pbi.wss?CTY=US&FNC=SRX&PBL=GC19-3374-00] English 55555 IBM Datacap Publication Library [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27043856] English 1000 Parascript FieldScript with Datacap V8.1.0 & V9.0.0 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27035840] English 1000 \nDOWNLOAD PACKAGE\nTo download Parascript FieldScript, sign in to Passport Advantage [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm] by using your IBM ID. If you are not a returning customer or you do not have an IBM ID, you can register to obtain an IBM ID.\n\nAfter you sign in to Passport Advantage, you can select the software to which you are entitled to download.\n\nClick the HTTP link to go to the Passport Advantage Online website.\n\n\n\n\nDownload RELEASE DATE LANGUAGE SIZE(Bytes) Download Options Passport Advantage Online 16 Dec 2011 English 1024 HTTP [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm] \nTECHNICAL SUPPORT\n Passport Advantage Online support:\nhttps:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare.html [https:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare.html]\n\nIBM Datacap Taskmaster Capture V8.0.1 and V8.1.0 support: http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Information_Management\/Datacap_Taskmaster_Capture [http:\/\/www.ibm.com\/support\/entry\/portal\/Overview\/Software\/Information_Management\/Datacap_Taskmaster_Capture] \n\nCross reference information Segment Product Component Platform Version Edition Enterprise Content Management Datacap Taskmaster Capture"}]},{"id":"DEV_Q272","question":"z\/OS Connect Enterprise Edition 3.0 and 2.0 compatibility with CICS TS 5.4\n\nCan z\/OS Connect Enterprise Edition V3.0 and V2.0 be used with CICS Transaction Server for z\/OS (CICS TS) V5.4? I want to make sure there are no compatibility problems. I would also like to know if there are any specific tasks that I need to perform for the z\/OS Connect Enterprise Edition V3.0 and V2.0 when upgrading to CICS TS V5.4. ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q273","question":"Why am I now seeing an SqlDataException for Unsupported ccsid, encoding, or locale after moving to Java 8.0 with WebSphere Application Server 8.5?\n\n\n\nThe requests using the DB2 JDBC driver are failing with:\n\ncom.ibm.db2.jcc.am.SqlDataException: [jcc][t4][10275][10041][4.19.56] Unsupported ccsid, encoding, or locale: \"Cp037\". ERRORCODE=-4220, SQLSTATE=22021\n\nCaused by: java.io.UnsupportedEncodingException: Cp037 at sun.io.Converters.getConverterClass(Converters.java:319) at sun.io.Converters.newConverter(Converters.java:373) at sun.io.ByteToCharConverter.getConverter(ByteToCharConverter.java:98) at com.ibm.db2.jcc.am.s.(Unknown Source) at com.ibm.db2.jcc.am.q.a(Unknown Source) ... 42 more","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q274","question":"VMware agent SSL hand shake failure after ESX upgrade\n\n\n\nWe did an update to our VCentre server, bringing it to 5.5 update 3e, i.e. 5.5.0,4180647 As a result the VMware agent does not connect now and logs this error:\n\nSEVERE: Connection.open: SSL handshake failed to: 192.168.1.2\n\nWe switched off SSL certification validation but it did not solve.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q275","question":"Jobtask long description\n\nHow do I modify the JP sheet to include the JOBTASK Long description in the query. I have tried JOBTASK.DESCRIPTION.DESCRIPTION_LONGDESCRITION and other combinations but they do not seem to work. ","answer":"Maximo 6.x MEA \n\n1. Go To Integration -> Integration Object \n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION \n\nMaximo 7.x MIF\n\n1. Go To Integration -> Object Structures \n\nClick Select Action -> Exclude\/Include Fields \n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION \n\nMaximo 6.x\/7.x XML\n\nAdd the long description tag to the inbound XML:\n\n<DESCRIPTION_LONGDESCRIPTION>xxxxx<\/DESCRIPTION_LONGDESCRIPTION> \n\nDo not include the HASLD tag. This column will be set automatically.","is_impossible":false,"contexts":[{"filename":"swg21417266.txt","text":"Title: IBM Including long descriptions in the Maximo Enterprise Adapter - United States\n\nText:\nlong description; ldkey; hasld; MEA; TPAEINTEGRATION TECHNOTE (FAQ)\n\nQUESTION\n How do I include long descriptions when sending data in using the Maximo Enterprise Adapter (MEA) or Maximo Integration Framework (MIF)? \n\nANSWER\n \n\nMaximo 6.x MEA \n\n1. Go To Integration -> Integration Object \n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION \n\nMaximo 7.x MIF\n\n1. Go To Integration -> Object Structures \n\nClick Select Action -> Exclude\/Include Fields \n\nOn the Persistent Fields tab, exclude HASLD\nOn the Non-Persistent Fields tab, include DESCRIPTION_LONGDESCRIPTION \n\nMaximo 6.x\/7.x XML\n\nAdd the long description tag to the inbound XML:\n\n<DESCRIPTION_LONGDESCRIPTION>xxxxx<\/DESCRIPTION_LONGDESCRIPTION> \n\nDo not include the HASLD tag. This column will be set automatically.\n\nThe same process will work for sending data in using flat files and interface tables, however, you must use an alias for DESCRIPTION_LONGDESCRIPTION on DB2 and SQL Server since the column name is longer than 18. If your object structure has multiple MBOs with long descriptions, you will have to use an alias to identify each column name uniquely.\n\n \n\n\nCross reference information Segment Product Component Platform Version Edition Systems and Asset Management Maximo Enterprise Adapter Not Applicable"}]},{"id":"DEV_Q276","question":"MessageSet Project cannot be referenced in multiple Applications\n\n\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":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q277","question":"Is transient user support available for SAML integration with WebSphere Portal 8.0?\n\nI am looking to leverage the SAML TAI provided by WebSphere Application Server for my WebSphere Portal 8.0 environment. Is transient user support available so that I do not have to maintain a local account in my Portal user registry for every external user which is verified and trusted by my identity provider? ","answer":"Transient user support [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/overview\/new_cf08.dita?lang=en] has been introduced for SAML TAI [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/wcm\/wcm_secure_int_tai_auth.dita?lang=en] starting with Cumulative Fix (CF) #8 for 8.5. Refer to the WebSphere Portal Security blog [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/8f2bc166-3bdc-4a9d-bad4-3620dbb3e46c\/entry\/portal_transient_user_support_with_was_saml_tai_business_case_clarification?lang=en] for more details regarding the business case and implementation details.","is_impossible":false,"contexts":[{"filename":"swg21665086.txt","text":"Title: IBM CWWIM1011E during PUMA lookup using SAML Trust Association Interceptor - United States\n\nText:\nSAML; SSO; TAI; PUMA; CWWIM1011E; InvalidUniqueNameException TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM\nAfter configuring the Security Assertion Markup Language (SAML) SAML Trust Association Interceptor (TAI) in WebSphere Application Server, you attempt to access WebSphere Portal after authenticating to your Identity Provider (IdP), but you are unable to view the Portal page.\n\nSYMPTOM\n- Portal page is blank \n\n- SystemOut.log contains the following error at the time of the problem occurrence:\n\ncom.ibm.websphere.wim.exception.InvalidUniqueNameException: CWWIM1011E\nThe '<userId>' unique name is not valid.\n\n\nCAUSE\nSAML TAI parameter sso_<n>.sp.idMap = is configured to use \"idAssertion\" which results in the userid instead of the fully distinguished name of the user to be set in the JAAS subject. Portal then uses this value to query Virtual Member Manager (VMM) via findUserByIdentifier() and the failure occurs since the value is not formatted as a distinguished name.\n\n\nDIAGNOSING THE PROBLEM\n- Collect Portal Login troubleshooting data [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21592791] \n\n- Look for the following in security.xml:\n<interceptors xmi:id=\"TAInterceptor_<identifier>\" interceptorClassName=\"com.ibm.ws.security.web.saml.ACSTrustAssociationInterceptor\">\n...\n<trustProperties xmi:id=\"Property_<identifier>\" name=\"sso_1.sp.idMap\" value=\"idAssertion\"\/> \n\nNote: There may be more than one sso_<n>.sp.idMap property (for example, sso_1.sp.idMap, sso_2.sp.idMap, etc). \n\n\nRESOLVING THE PROBLEM\n \n\nOption #1: \n\nThe idAssertion value means that no entry is necessary for the user in the user registry, which is not supported in WebSphere Portal by default. Update the sso_<n>.sp.idMap property via the Integrated Solutions Console to use the value \"localRealm\" instead of \"idAssertion.\" \n\nThe localRealm value ensures that WebSphere Application Server will complete the JAAS Subject with the full distinguished name for the user by querying the user registry and thus Portal will pass the correct format to VMM. \n\nOption #2: \n\nTransient user support [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/overview\/new_cf08.dita?lang=en] has been introduced for SAML TAI [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/wcm\/wcm_secure_int_tai_auth.dita?lang=en] starting with Cumulative Fix (CF) #8 for 8.5. Refer to the WebSphere Portal Security blog [https:\/\/www.ibm.com\/developerworks\/community\/blogs\/8f2bc166-3bdc-4a9d-bad4-3620dbb3e46c\/entry\/portal_transient_user_support_with_was_saml_tai_business_case_clarification?lang=en] for more details regarding the business case and implementation details. \n\n \n\nNote: WebSphere Portal also provides transient user support when configured with OpenId authentication [http:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSHRKX_8.5.0\/mp\/security\/use_openid.dita?lang=en].\n\nRELATED INFORMATION\n Understanding the SAML Trust Association Interceptor [http:\/\/www.ibm.com\/developerworks\/websphere\/techjournal\/1307_lansche\/1307_lansche.html]\nWebSphere Portal Support Statement [http:\/\/www-10.lotus.com\/ldd\/portalwiki.nsf\/dx\/WebSphere_Portal_Support_Statement_wp8]"}]},{"id":"DEV_Q278","question":"Can I change the UUID value on the Messaging Engine?\n\nAfter dropping the SIB object, a new UUID value was generated for the new SIB object. However, the messaging application points to the old UUID value.\nIs it possible to change the new UUID value back to the old value?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q279","question":"Are there any known issue or limitation to LOAD data using ADMIN_CMD stored procedure?\n\nHello,\n\nWe have JDBC applications on WebShpere, LOAD data using ADMIN_CMD. Now, we are planning to use them under XA environment. Are there any known issue or limitation to LOAD data using ADMIN_CMD under XA environment?","answer":"It is an known current limitation of DB2.","is_impossible":false,"contexts":[{"filename":"swg21988939.txt","text":"Title: IBM ADMIN_CMD('load from ...') using JDBC in XA transaction gets SQL30090N - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n Why does ADMIN_CMD('load from ...') using JDBC in XA transaction get SQL30090N? \n\nCAUSE\nIt is an known current limitation of DB2.\n\nANSWER\nHere is an example message from a jdbctrace.log \n\n-------------------\n[jcc] BEGIN TRACE_DIAGNOSTICS\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03] java.sql.SQLWarning\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] DB2 SQLCA from server\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlCode = 20397\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlErrd = { 0, 2, 0, 0, 0, 0 }\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlErrmc = SYSPROC.ADMIN_CMD;SQL30090;^@\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlErrmcTokens = { SYSPROC.ADMIN_CMD, SQL30090, ^@ }\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlErrp = DB2LOAD\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlState = 01H52\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03][Sqlca@f3177864] SqlWarn =\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03] SQL state = 01H52\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03] Error code = 20397\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03] Tokens = SYSPROC.ADMIN_CMD;SQL30090;^@\n[jcc][Thread:WebContainer : 0][SQLWarning@2cab0b03] Stack trace follows\ncom.ibm.db2.jcc.am.SqlWarning: DB2 SQL Warning: SQLCODE=20397, SQLSTATE=01H52, \nSQLERRMC=SYSPROC.ADMIN_CMD;SQL30090;^@, DRIVER=4.19.49\n-------------------\n\nSymptoms:\n- It does not throw any exception and the application finished without any problem but \nthe data is not actually loaded into the table.\n- If the same operation without XA transaction, it is succeeded and loaded data.\n- From jdbctrace, SQL20397W and SQL30090N are logged.\n\nThe reason why:\nThe cause of the problem is LOAD does internal commit near the beginning of \noperation. The load internal commit got back SQL30090 error is standard \nbehavior in XA environment. So ADMIN_CMD + LOAD does not work on XA.\n\nWorkaround:\nUnfortunately, there is no way to do ADMIN_CMD + LOAD on XA.\n\nRELATED INFORMATION\n LOAD command using the ADMIN_CMD procedure [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSEPGG_10.5.0\/com.ibm.db2.luw.sql.rtn.doc\/doc\/r0023577.html ]\nSQL30090N [https:\/\/www.ibm.com\/support\/knowledgecenter\/en\/SSEPGG_10.5.0\/com.ibm.db2.luw.messages.sql.doc\/doc\/msql30090n.html ]\nA Japanese translation is available [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21996128]"}]},{"id":"DEV_Q280","question":"Is WebSphere Transformation Extender (WTX) supported for IBM Integration Bus V10?\n\nWhen will WebSphere Transformation Extender (WTX) be supported for IBM Integration Bus V10?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q281","question":"'Save and Close' and 'Save' buttons grayed out in desktop configuration\n\nIn IBM Content Navigator, when configuring a desktop, the 'Save and Close' and 'Save' buttons may be disabled. ","answer":"One of the required fields in the configuration does not have a value","is_impossible":false,"contexts":[{"filename":"swg21975568.txt","text":"Title: IBM 'Save and Close' and 'Save' buttons grayed out in desktop configuration - United States\n\nText:\nICN; Content Navigator; Save; Save and Close; Button TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n In IBM Content Navigator, when configuring a desktop, the 'Save and Close' and 'Save' buttons may be disabled. \n\nCAUSE\nOne of the required fields in the configuration does not have a value\n\nRESOLVING THE PROBLEM\nIBM Content Navigator configuration tabs that contain required fields are flagged with a red asterisk to the side of the tab label. For a desktop configuration, General, Repositories, Layout, and Menus tabs contain required fields. Make sure all these fields have a value. The following screen shot provides an illustration of the tabs that contain required fields. \n\n[\/support\/docview.wss?uid=swg21975568&aid=1] [\/support\/docview.wss?uid=swg21975568&aid=1]"}]},{"id":"DEV_Q282","question":"Does the IBM Netcool Omnibus ServiceNow Gateway support Geneva Release ?\n\nUsers of this gateway are asking if we support the latest release of ServiceNow Geneva instance?","answer":"Enhancement to allow the gateway to accommodate a change in REST API behavior between ServiceNow versions Eureka\/Fiji compared to Geneva.","is_impossible":false,"contexts":[{"filename":"swg21978428.txt","text":"Title: IBM Tivoli Netcool\/OMINbus Java Gateway for ServiceNow (nco_g_servicenow-3_0) - United States\n\nText:\nrelease notice; downloads; Netcool\/OMNIbus Java Gateway for ServiceNow; nco_g_servicenow NEWS\n\nABSTRACT\n This new gateway will be ready for downloading on November 24, 2016. \n\nCONTENT\n \n\nThis version addresses the following enhancement requests:\n\n * RFE 85941: Enhancement to add HTTP proxy support. New property updated to specify the HTTP proxy with optional port.\n * RFE 88118: Enhancement to allow the gateway to accommodate a change in REST API behavior between ServiceNow versions Eureka\/Fiji compared to Geneva.\n\nYou can download the installation package from the IBM Passport Advantage website: \nwww.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm [http:\/\/www.ibm.com\/software\/howtobuy\/passportadvantage\/pao_customers.htm]\n\nYou can access the latest version of the guide written for this gateway on the IBM Knowledge Center:\n\nwww.ibm.com\/support\/knowledgecenter\/SSSHTQ\/omnibus\/gateways\/snowgw\/wip\/concept\/snowgw_intro.html [https:\/\/www.ibm.com\/support\/knowledgecenter\/SSSHTQ\/omnibus\/gateways\/snowgw\/wip\/concept\/snowgw_intro.html]\n\nNetcool\/OMNIbus V8.1\n\nIf you are running Netcool\/OMNIbus V8.1, a single package contains versions of the gateway for all supported Operating Systems. To obtain this new package, use the Find by part number field to search for part number: CNFT1EN\n\n Note: The Netcool\/OMNIbus V8.1 version of this gateway supports the following Operating Systems: AIX, Linux, Solaris, Windows and zLinux. \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 CNFQ2EN AIX CNFQ3EN HP-UX Integrity CNFQ4EN Linux for zSeries CNFQ5EN Linux CNFQ6EN Solaris CNFQ7EN 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: https:\/\/www-112.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare_emea.html [https:\/\/www-112.ibm.com\/software\/howtobuy\/passportadvantage\/paocustomer\/docs\/en_US\/ecare_emea.html]"}]},{"id":"DEV_Q283","question":"Hello - I recently installed SPSS 20, my temporary period for running spss has expired, I am in need of the actual license code to fully install. my Lock code is: 4-20C30\n\nHello - I recently installed SPSS 20, my temporary period for running spss has expired, I am in need of the actual license code to fully install. my Lock code is: 4-20C30 . please help! ","answer":"For installation & licensing issues on Student version and Graduate pack, contact your vendor.","is_impossible":false,"contexts":[{"filename":"swg21592093.txt","text":"Title: IBM SPSS Student Version and Graduate Pack Resources - United States\n\nText:\nSPSS Support Acquisition Statistics Stats Grad Pack Student TECHNOTE (FAQ)\n\nQUESTION\n Where do I get support for IBM SPSS Student Version or Graduate Pack software? \n\nANSWER\nStep 1: \nFor installation & licensing issues on Student version and Graduate pack, contact your vendor. \n\n * Hearne [http:\/\/www.hearne.software\/Software\/SPSS-Grad-Packs-for-Students-by-IBM\/FAQ] \n * On the Hub [http:\/\/onthehub.com\/] \n * StudentDiscounts.com [http:\/\/studentdiscounts.com\/contact-us.aspx] \n * JourneyEd [https:\/\/www.journeyed.com\/contact] \n * thinkEDU [https:\/\/thinkedu.desk.com\/] \n * Studica [http:\/\/www.studica.com\/technical-support]\n\n\n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics SPSS Amos Windows Not Applicable Grad Pack, Shrinkwrap, Campus Business Analytics SPSS Modeler Platform Independent Not Applicable Business Analytics SPSS Text Analytics for Surveys Windows Not Applicable Business Analytics SPSS Statistics Platform Independent Not Applicable Campus Edition, Grad Pack, Student Version"}]},{"id":"DEV_Q284","question":"iLMT - incomplete virtualisation hierarchy\n\n\n\nthis query is regarding support case 1109598 that has been raised.\n\nIf we set up an account is this providing access to information for other accounts\/servers where we use the same ESX hosts for multiple customers. What specifically is being asked in terms of logical structure and permissions of the account?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q285","question":"Why is the file db2jcc.jar missing after an upgrade to BPM V8.5.7 CF2016.12?\n\nAfter upgrading to IBM Business Process Manager V8.5.7 Cumulative Fix 2016.12, I have encountered several JDBC related exceptions during my process application development. It seems that the file db2jcc.jar was removed during the installation of the cumulative fix pack. What happened? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q286","question":"Executing an in-flight task for a deactivated snapshot for WebSphere Lombardi Edition and IBM Business Process Manager (BPM)\n\nWhy do in-flight tasks stop after the snapshot has been deactivated? This question pertains to WebSphere Lombardi Edition V7.2 and IBM Business Process Manager V7.5.1.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q287","question":"Why I am not able to login to StoredIQ Dataserver and Getway using ssh?\n\nWhy I am not able to login to StoredIQ Dataserver and Getway using ssh? ","answer":"Restriction in remote login using ssh","is_impossible":false,"contexts":[{"filename":"swg22001558.txt","text":"Title: IBM Unable to login to StoredIQ Dataserver and Gateway using ssh - United States\n\nText:\nStoredIQ ssh TECHNOTE (FAQ)\n\nQUESTION\n Why I am not able to login to StoredIQ Dataserver and Getway using ssh? \n\nCAUSE\nRestriction in remote login using ssh\n\nANSWER\n \n\n 1. Review the file \/etc\/ssh\/sshd_config on the specific server using console \n 2. Make sure PermitRootLogin is set to yes \n 3. Save the change in the file \n 4. Restart the appliance"}]},{"id":"DEV_Q288","question":"Is Java 8 supported for BPM?\n\n\n\nI understand that support for Java 6 on WebSphere Application Server is ending April 2018, see: http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21999583\n\nNow I can switch to Java 7. But what about Java 8? Does BPM 8.5.6 support Java 8?","answer":"IBM BPM V8.5.6.0 Java 6 or Java 7*","is_impossible":false,"contexts":[{"filename":"swg21639640.txt","text":"Title: IBM Some versions of IBM Business Process Manager (BPM) and IBM Business Monitor do not support certain Java versions running with WebSphere Application Server Network Deployment V8.5 - United States\n\nText:\nibpma85relnotes; ibpms85relnotes; ibpme85relnotes; iid85relnotes; ibpma8501relnotes; ibpms8501relnotes; ibpme8501relnotes; iid8501relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Java 6\u2122 on WebSphere Application Server V8.5 reaches end of service (EOS) in April 2018. For more information, see the \"Software withdrawal and service discontinuance: IBM WebSphere Application Server V7 and V8 and select IBM WebSphere products and part numbers - Some replacements available\" announcement (http:\/\/www.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/3\/897\/ENUS916-143\/index.html&request_locale=en [http:\/\/www.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/3\/897\/ENUS916-143\/index.html&request_locale=en]). \n\nExtended support is not offered for Java 6, so you should use Java 7 or Java 8 instead. If Java 7 is not supported on your current version, you must upgrade to IBM Business Process Manager (BPM) V8.5.7 and IBM Business Monitor V8.5.7. If Java 8 is not supported on your current version, you must upgrade to IBM BPM V8.6.\n\nIBM BPM zOS V8.5.0.2 supports Java 7.1 (IBM WebSphere Application Server V8.5.5.5 as a prerequisite). \n\nIBM Process Designer in IBM BPM V8.5.7.0 CF 2017.03 or later versions is bundled with Java 7. \n\nRESOLVING THE PROBLEM\nUse the appropriate Java version for the version of IBM BPM or IBM Business Monitor you are using: \n\nProduct version Supported Java version IBM BPM V8.6 Java 8* IBM BPM V8.5.7.0 Java 6 or Java 7* IBM BPM V8.5.6.0 Java 6 or Java 7* IBM BPM V8.5.5.0 Java 6 IBM BPM V8.5.0.x Java 6 [\/support\/docview.wss?uid=swg21639640&aid=1] [\/support\/docview.wss?uid=swg21639640&aid=1] IBM Business Monitor V8.5.7.0 Java 6 or Java 7* Business Monitor V8.5.6.0 Java 6 or Java 7* Business Monitor V8.5.5.0 Java 6 [\/support\/docview.wss?uid=swg21639640&aid=1] [\/support\/docview.wss?uid=swg21639640&aid=1] *Java snippets, Java conditions, and Java expressions in BPEL processes must use Java 6 constructs instead of Java 7 or Java 8 constructs. \nFor more information, see the following resources: \n * Verify Java SDK version shipped with IBM WebSphere Application Server fix packs [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27005002] \n * Support for Java 6 with Business Process Manager and Business Monitor ending April 2018 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21999583] \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation \/ Configuration AIX, Linux, Solaris, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Express Installation \/ Configuration Linux, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Monitor Installation AIX, Linux, Solaris, Windows, z\/OS 8.5.7, 8.5.6, 8.5.5 Business Integration IBM Business Process Manager Advanced Installation \/ Configuration AIX, Linux, Solaris, Windows, z\/OS 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Family Installation \/ Configuration AIX, Linux, Windows 8.6.0.0 IBM Business Process Manager Server Express \nPRODUCT ALIAS\/SYNONYM\n BPM\nMonitor"}]},{"id":"DEV_Q289","question":"A NullPointerException appears in BPC Explorer in BPM after upgrading, how do I resolve this?\n\n null pointer exception happens when using the business process choreographer explorer. This occurs in BPM 8.5.5.0 after upgrading from WPS 7. The exception stack in SystemOut.log is the following.\nwebapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[Faces Servlet]: java.lang.NullPointerException at com.ibm.bpc.explorer.ConnectionFactoryImpl.<init>(ConnectionFactoryImpl.java:69) at com.ibm.bpc.explorer.util.BFMUtils.getBFMConnection(BFMUtils.java:301) at com.ibm.bpc.explorer.util.BFMUtils.getBusinessFlowManagerService(BFMUtils.java:310) \n.....","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q290","question":"Is using a monitored JBoss server with ITCAM supported in a Windows Service?\n\nIs 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 because this involves changes to the JBoss native connector files and this is currently not supported.","is_impossible":false,"contexts":[{"filename":"swg21967756.txt","text":"Title: IBM Is using a monitored JBoss Application Server with ITCAM for J2EE supported in a Windows service? - United States\n\nText:\nJ2EE 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"}]},{"id":"DEV_Q291","question":"Is Java 8 supported for BPM?\n\n\n\nI understand that support for Java 6 on WebSphere Application Server is ending April 2018, see: http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21999583\n\nNow I can switch to Java 7. But what about Java 8? Does BPM support Java 8?","answer":"IBM BPM V8.5.6 and V8.5.7 support Java 6 and Java 7, but do not support Java 8.","is_impossible":false,"contexts":[{"filename":"swg21639640.txt","text":"Title: IBM Some versions of IBM Business Process Manager (BPM) and IBM Business Monitor do not support certain Java versions running with WebSphere Application Server Network Deployment V8.5 - United States\n\nText:\nibpma85relnotes; ibpms85relnotes; ibpme85relnotes; iid85relnotes; ibpma8501relnotes; ibpms8501relnotes; ibpme8501relnotes; iid8501relnotes TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Java 6\u2122 on WebSphere Application Server V8.5 reaches end of service (EOS) in April 2018. For more information, see the \"Software withdrawal and service discontinuance: IBM WebSphere Application Server V7 and V8 and select IBM WebSphere products and part numbers - Some replacements available\" announcement (http:\/\/www.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/3\/897\/ENUS916-143\/index.html&request_locale=en [http:\/\/www.ibm.com\/common\/ssi\/ShowDoc.wss?docURL=\/common\/ssi\/rep_ca\/3\/897\/ENUS916-143\/index.html&request_locale=en]). \n\nExtended support is not offered for Java 6, so you should use Java 7 or Java 8 instead. If Java 7 is not supported on your current version, you must upgrade to IBM Business Process Manager (BPM) V8.5.7 and IBM Business Monitor V8.5.7. If Java 8 is not supported on your current version, you must upgrade to IBM BPM V8.6.\n\nIBM BPM zOS V8.5.0.2 supports Java 7.1 (IBM WebSphere Application Server V8.5.5.5 as a prerequisite). \n\nIBM Process Designer in IBM BPM V8.5.7.0 CF 2017.03 or later versions is bundled with Java 7. \n\nRESOLVING THE PROBLEM\nUse the appropriate Java version for the version of IBM BPM or IBM Business Monitor you are using: \n\nProduct version Supported Java version IBM BPM V8.6 Java 8* IBM BPM V8.5.7.0 Java 6 or Java 7* IBM BPM V8.5.6.0 Java 6 or Java 7* IBM BPM V8.5.5.0 Java 6 IBM BPM V8.5.0.x Java 6 [\/support\/docview.wss?uid=swg21639640&aid=1] [\/support\/docview.wss?uid=swg21639640&aid=1] IBM Business Monitor V8.5.7.0 Java 6 or Java 7* Business Monitor V8.5.6.0 Java 6 or Java 7* Business Monitor V8.5.5.0 Java 6 [\/support\/docview.wss?uid=swg21639640&aid=1] [\/support\/docview.wss?uid=swg21639640&aid=1] *Java snippets, Java conditions, and Java expressions in BPEL processes must use Java 6 constructs instead of Java 7 or Java 8 constructs. \nFor more information, see the following resources: \n * Verify Java SDK version shipped with IBM WebSphere Application Server fix packs [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg27005002] \n * Support for Java 6 with Business Process Manager and Business Monitor ending April 2018 [http:\/\/www.ibm.com\/support\/docview.wss?uid=swg21999583] \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Integration IBM Business Process Manager Standard Installation \/ Configuration AIX, Linux, Solaris, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Express Installation \/ Configuration Linux, Windows 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Monitor Installation AIX, Linux, Solaris, Windows, z\/OS 8.5.7, 8.5.6, 8.5.5 Business Integration IBM Business Process Manager Advanced Installation \/ Configuration AIX, Linux, Solaris, Windows, z\/OS 8.5.7, 8.5.6, 8.5.5, 8.5.0.2, 8.5.0.1, 8.5 Business Integration IBM Business Process Manager Family Installation \/ Configuration AIX, Linux, Windows 8.6.0.0 IBM Business Process Manager Server Express \nPRODUCT ALIAS\/SYNONYM\n BPM\nMonitor"}]},{"id":"DEV_Q292","question":"Content Engine System Health Page page doesn't reflect correctly, Fixed Content Advise and Storage Area showing unavailable.\n\nContent Engine System Health Page page doesn't reflect correctly, Fixed Content Advise and Storage Area showing unavailable. ","answer":"Verify the Content Engine Bootstrap User has Full Control on the Object Store and all associated Storage Areas. \n \n \n 2. Inspect Storage Area security by right-clicking on the Object Store\n \n \n 3. Choose Properties\n \n \n 4. Select the All Properties radio button and view the Storage Area property name\n \n \n 5. Click on the drop down list to select the Storage Area. \n \n \n 6. The Storage Area properties screen will appear. \n \n \n 7. Verify the Security tab allows the Content Engine Bootstrap User has Full Control.","is_impossible":false,"contexts":[{"filename":"swg21566663.txt","text":"Title: IBM The FileNet Content Engine Health Page may report the Fixed Content Device and Storage Areas as unavailable - United States\n\nText:\nce health page; storage areas unavailable TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n The Content Engine Health Page (http:\/\/<CEserver>:<port>\/P8CE\/Health ) provides the status for different areas of the FileNet P8 system. When viewing the page, both the Fixed Content Devices and the Storage Areas may display red icons instead of checkmark green icons. \n\nSYMPTOM\nRed icons are displayed next to the Fixed Content Devices and Storage Areas even though users can add and access content.\n\n\nDIAGNOSING THE PROBLEM\nThe p8_server_error log may contain the following E_ACCESS_DENIED error: \n\nyyyy-mm-ddThh:mm:ss nnnnnn ENG FNRCE0241E - ERROR method name: postLoadSecurity principal name: <username> Global Transaction: false User Transaction: false Exception Info: The requester has insufficient access rights to perform the requested operation.\ncom.filenet.api.exception.EngineRuntimeException: E_ACCESS_DENIED: The requester has insufficient access rights to perform the requested operation.\nat com.filenet.engine.retrieve.IndependentClassRetriever.postLoadSecurity(IndependentClassRetriever.java:1390)\nat com.filenet.engine.retrieve.RetrieverClassBase.loadNonScalarProperties(RetrieverClassBase.java:633)\nat com.filenet.engine.retrieve.IndependentClassRetriever.loadNonScalarProperties(IndependentClassRetriever.java:1298)\nat com.filenet.engine.retrieve.IndependentClassRetriever.loadObject(IndependentClassRetriever.java:1119)\n...\n\n\n\nRESOLVING THE PROBLEM\n \n\n 1. Verify the Content Engine Bootstrap User has Full Control on the Object Store and all associated Storage Areas. \n \n \n 2. Inspect Storage Area security by right-clicking on the Object Store\n \n \n 3. Choose Properties\n \n \n 4. Select the All Properties radio button and view the Storage Area property name\n \n \n 5. Click on the drop down list to select the Storage Area. \n \n \n 6. The Storage Area properties screen will appear. \n \n \n 7. Verify the Security tab allows the Content Engine Bootstrap User has Full Control."}]},{"id":"DEV_Q293","question":"BPM installation packages and deployment options\n\nWhat is the difference between \"Advanced\" and \"AdvancedOnly\" options for BPM deployment environment? What is the difference between \"BPM Advanced\" and \"BPM Advanced - Process Server\" installation images?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q294","question":"Error #2070\n\nI purchased the SPSS grad pack and put one of the licenses on one computer and another on this one. This computer crashed and I was forced to reformat the hard drive. Subsequently, I lost SPSS in the process. I am now reinstalling with the single user copy option.\n\nThe error it gave me now when I attempted to authorize the program with the original authorization number I received was:\n\nAuthorization in progress ... (removed) Authorization failed.: You are not allowed to generate any more new licenses. End Of Transaction. All permitted authorizations for the provided authorization code(s) have been utilized. No additional authorizations are permitted on this code. If you think this is an error, please contact IBM Corp. Customer Service at spssls@us.ibm.com ( http:\/\/www-01.ibm.com\/software\/analytics\/spss ) with your product and purchase details. Click \"Finish\" to exit.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q295","question":"Why are we seeing high CPU and hung threads in WebSphere Application Server?\n\nDuring the job execution in WebSphere Compute Grid we are seeing high CPU along with many hung threads reporting\nWSVR0605W from BatchFileLoggerInfo.getDirectoryList method.\nIn Sysprint many threads are hung with this stack:\nBossLog: { 0426} <time stamp> SYSTEM=CPU4 CELL=FGDCELL NODE=FGDNODE4 CLUSTER=WFGDS1 SERVER=WFGDS14 PID=0X060835 TID=0 X2ED98E0000000162 t=8897F0 c=UNK .\/bbgrjtr.cpp+733 tag= ... BBOO0221W: WSVR0605W: Thread \"WebSphere WLM Dispatch Thread t=008a6b70\" (0000006a) has been active for 683953 milliseconds and may be hung.\n....","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q296","question":"Does the BPM internal Document Store work with IBM DB2 pureScale?\n\nI use IBM DB2 pureScale with my BPM installation. During startup of the server and initialization of the internal document store I see hanging threads in the systemOut.log and the process will not finish. How can this be solved? ","answer":"The lock timeouts can be avoided by only having a single DB2 pureScale member active during FileNet CM addon installation. Once addon installation has completed successfully, the other members can be brought back online.","is_impossible":false,"contexts":[{"filename":"swg21663414.txt","text":"Title: IBM FileNet Content Manager object store addon creation fails on IBM DB2 pureScale - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Excessive lock duration during FileNet CM object store addon creation may result in SQL lock timeouts that will cause addon installation to fail. \n\nSYMPTOM\nDB transactions are rolled back due to SQL timeout.\n\n\nCAUSE\nWhen multiple DB2 pureScale members are active during FileNet CM addon creation, excessive SQL locking may occur, resulting in a potential lock timeout. This can result in transactions being rolled back, thereby resulting in the addon installation failing.\n\nDIAGNOSING THE PROBLEM\nExamine both the P8 error log and the DB2 diagnostic logs for each active member for lock timeout error messages similar to the following:\n\n\nDB2 (db2diag.log):\nFUNCTION: DB2 UDB, lock manager, sqlplWaitOnWP, probe:999 \n\n MESSAGE : ZRC=0x80100044=-2146435004=SQLP_LTIMEOUT\n\"LockTimeOut - tran rollback Reason code 68 \n\nP8 (p8_server_error.log): \ncom.filenet.api.exception.EngineRuntimeException: FNRCE0019E: E_DEADLOCK_ERROR: The operation could not be completed due to a deadlock error. A retry might be appropriate.\nCaused by: com.ibm.db2.jcc.am.SqlTransactionRollbackException: DB2 SQL Error: SQLCODE=-911, SQLSTATE=40001, SQLERRMC=68, DRIVER=4.15.82\n\nNote: The SQLERRMC=68 suggests that the root cause is a SQL lock timeout even though the P8 error message and SQLCODE suggest a deadlock occurred.\n\n\nRESOLVING THE PROBLEM\nThe lock timeouts can be avoided by only having a single DB2 pureScale member active during FileNet CM addon installation. Once addon installation has completed successfully, the other members can be brought back online."}]},{"id":"DEV_Q297","question":"res-deploy-xom ant task does not deploy xom based on checksum difference when xom is a .zip extension\n\nQuestion: Is re-naming the WebSphere Portal installation directory and cell name for an existing clustered installation possible? ","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q298","question":"can Datacap support to Arabic language?\n\ncan Datacap support to Arabic language?","answer":"Support for Arabic requires that customers license NovoDynamics NovoVarus separately and install it on the Rulerunner machine where the Datacap Studio actions for Arabic (Datacap.Libraries.NovoDynamics) will be running.","is_impossible":false,"contexts":[{"filename":"swg27035841.txt","text":"Title: IBM Datacap Taskmaster Capture 8.1.0 Language Support - United States\n\nText:\n PRODUCT DOCUMENTATION\n\nABSTRACT\n This document provides details about the languages that are supported by the different IBM Datacap Taskmaster Capture Version 8.1.0 components. \n\nCONTENT\n\n\nThe following tables show the languages that are supported in the corresponding Datacap Taskmaster 8.1.0 component.\n\nNotes\n\n * OCR-S\/OCR-SR: Nuance engine\n * OCR-A: ABBYY engine \n * OCR-N: NovoDynamics engine \n * ICR-C: RecoStar engine\n * Legal Dict.: OCR-S Legal Dictionary\n * Financial Dict.: OCR-S Financial Dictionary\n * Medical Dict.: OCR-S Medical Dictionary\n * ICR-P: Parascript engine\n * \n * Admin\/Install doc.: Administration\/installation documentation\n\nLanguages:\n\n * A through C\n * D through E\n * H through N\n * P through Sa\n * Se through Z\n\nAfrikaans through Czech\n\nImportant:\n\n Support for Arabic requires that customers license NovoDynamics NovoVarus separately and install it on the Rulerunner machine where the Datacap Studio actions for Arabic (Datacap.Libraries.NovoDynamics) will be running.\n\nFor Chinese (traditional) OCR-S\/OCR-SR support, HKSCS extensions are not supported.\n\nFor Chinese (simplified) and Chinese (traditional), OCR-A is recommended instead of OCR-S\/OCR-SR, because OCR-S confidence calculation might return high confidence for replaced characters.\n\nTable 1\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-N OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Afrikaans Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Albanian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Arabic Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported<\/td><td width= [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif][\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Bosnian (Latin) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Catalan Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Chinese (simplified) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Chinese (traditional) [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Croatian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Czech Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 1 continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Afrikaans Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Albanian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Arabic [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Bosnian (Latin) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Catalan Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Chinese (simplified) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Chinese (traditional) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Croatian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Czech Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Back to top\n\nTable 2 Danish through Estonian\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Danish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Dutch Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Dutch Belgian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] English Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Esperanto Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Estonian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 2 Danish through Estonian continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Danish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Dutch Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Dutch Belgian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] English Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Esperanto Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Estonian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Back to top\n\nTable 3 Faroese through Greek\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Faroese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Finnish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] French Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Gaelic Irish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Gaelic Scottish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] German Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Greek Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 3 Faroese through Greek continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Faroese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Finnish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] French Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Gaelic Irish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Gaelic Scottish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] German Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Greek Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Back to top\n\nTable 4 Hebrew through Norwegian\n\nImportant: OCR-A support for Hebrew and Japanese requires the IBM Datacap Taskmaster Capture interim fix, 8.1.0.2-Datacap-Taskmaster-WIN-IF-OCRA:0609577 [http:\/\/www.ibm.com\/support\/fixcentral\/swg\/selectFixes?product=ibm\/Information+Management\/Datacap+Taskmaster+Capture&release=All&platform=All&function=fixId&fixids=8.1.0.2-Datacap-Taskmaster-WIN-IF-OCRA%3A0609577&includeSupersedes=0], which is available at IBM Support Fix Central [http:\/\/www.ibm.com\/support\/fixcentral].\n\nFor Japanese, OCR-A is recommended instead of OCR-S\/OCR-SR, because OCR-S confidence calculation might return high confidence for replaced characters.\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Hebrew Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Hungarian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Icelandic Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Italian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Japanese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Latvian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Lithuanian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Maltese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Norwegian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 4 Hebrew through Norwegian continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Hebrew Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Hungarian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Icelandic Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Italian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Japanese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Latvian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Lithuanian [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Maltese Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Norwegian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Back to top\n\nTable 5 Polish through Sami Southern\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Polish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Portuguese (Brazil) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Portuguese (Portugal) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Rhaeto-Romanic Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Romanian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Russian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Sami Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Sami Northern Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Sami Southern Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 5 Polish through Sami Southern continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Polish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Portuguese (Brazil) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Portuguese (Portugal) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Rhaeto-Romanic Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Romanian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Russian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Sami Sami Northern Sami Southern Back to top\n\nTable 6 Serbian through Turkish\n\nLanguage Data Entry DotEdit and DotScan FastDoc Taskmaster Web OCR-S OCR-SR Legal Dict. Financial Dict. Medical Dict. Serbian (Cyrillic)* Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Serbian (Latin) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Slovak Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Slovenian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Spanish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Swahili Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] [\/support\/docview.wss?uid=swg27035841&aid=1] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Swedish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Turkish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] [\/support\/docview.wss?uid=swg27035841&aid=1] Table 6 Serbian through Turkish continued\n\nLanguage OCR-A ICR-C ICR-P IBM Content Classification Admin\/Install doc. Online Help Serbian (Cyrillic)* [\/support\/docview.wss?uid=swg27035841&aid=1] Serbian (Latin) Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Slovak Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Slovenian Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Spanish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Swahili Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Swedish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Turkish Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] Supported [http:\/\/www.ibm.com\/i\/v16\/icons\/confirm.gif] *Important: Datacap Taskmaster Version 8.1.0 does not expose a user interface to select the Serbian Cyrillic recognition option, but support for Serbian (Cyrillic) is invoked through the implementation of actions in Datacap Studio. See the technical document, Setting the OCR\/S recognition language to Serbian (Cyrillic) [http:\/\/www.ibm.com\/support\/docview.wss?&uid=swg27040327]. \n\nBack to top"}]},{"id":"DEV_Q299","question":"Netcool\/Impact 6.1.1: Policy Custom Function not getting variable value\n\n\nNetcool\/Impact 6.1.1: Policy Custom Function not getting variable value\n\nCustom Function call:\n\n ProcessFunction(GotNodes[0].AlertKey); \n\nof a result set acquired by GetByFilter:\n\n GotNodes=GetByFilter(ObjServ_Alerts_DT, Node=\"'\"+@Node+\"'\", False); \n\nstill fails to use the acquired variable even when there is a value for both GotNodes and GotNodes[0].AlertKey","answer":"Assigning the variable prior to the function call will ensure that the value is passed to the User Defined Function.","is_impossible":false,"contexts":[{"filename":"swg21500040.txt","text":"Title: IBM User Defined Function not receiving provided variable - United States\n\nText:\nnetcool\/impact; nci; netcool; impact; user; defined; user defined function; UDF; UserDefinedFunction; UserDefined; custom function; CustomFunction; function; sql; null; variable; value; call; error; exception; functioncall TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n A variable provided in a User Defined Function call is not received within the function action. \n\nSYMPTOM\nThe User Defined Function call is of the style: \n\n * \n * \n\n\nand MyResultSet was acquired in a previous GetBy - for example: \n\n * \n\n\nand this was proven to have received a result: \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nAny attempt to use that value in the User Defined Function will report a NULL style error if it is not able to handle a null value or just simply fail to produce the expected results. \n\nRESOLVING THE PROBLEM\nAssigning the variable prior to the function call will ensure that the value is passed to the User Defined Function. Using the above example we can rewrite this as: \n\n\n\n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n * \n\n\nThis is similar to the behaviour and work-around recorded in the TechNote \"Unsolicited SQL updates from User Defined Function\" [ link below], which was recorded as IZ67227: \"UNSOLICITED SQL UPDATE STATEMENT PRODUCED BY FUNCTION CALL WHEN LOOPING THROUGH GETBY* RESULT SET\" [ link below]. \nRELATED INFORMATION\n Unsolicited SQL updates from User Defined Function [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg21421783]\nIZ67227 [http:\/\/www-01.ibm.com\/support\/docview.wss?uid=swg1IZ67227]"}]},{"id":"DEV_Q300","question":"DB2 Non Reclaimable Storage .\n\nWe 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?\n","answer":"to 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 ","is_impossible":false,"contexts":[{"filename":"swg21438047.txt","text":"Title: 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\n\nText:\nSQL1763N; 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]"}]},{"id":"DEV_Q301","question":"SPSS 24 License\n\n\n\nHi, Just restored my Mac from a back up. My license code stoped working. I get this message \"Authorization in progress ... (-------------------------------------) Authorization failed.: You are not allowed to generate any more new licenses. End Of Transaction.\nNo additional authorizations are permitted on this code. For assistance go to www.ibm.com\/planetwide and select your country in order to place a support case online or by phone. Please have your IBM Customer Number or purchase details available. \"\n\nCan you please help ?","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q302","question":"How can I export a private key from DataPower Gateway Appliance?\n\n\n\nIs it possible to export a private key from DataPower Gateway Appliance?","answer":"HSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met: \n\n * HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n * The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n * HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.","is_impossible":false,"contexts":[{"filename":"swg21412061.txt","text":"Title: IBM How to export and import keys from an HSM-enabled IBM WebSphere DataPower SOA Appliance - United States\n\nText:\n TECHNOTE (FAQ)\n\nQUESTION\n How do I export and import private keys between the same or different Hardware Security Module (HSM) enabled IBM WebSphere DataPower SOA Appliance? \n\nANSWER\nHSM-enabled DataPower appliances support the export of private keys using the crypto-export command. For key export to work, various conditions must be met: \n\n * HSMs must be initialized and in the same key sharing domain on exporting and importing machines \n * The private key in question must be marked exportable at keygen time (see keygen's exportable option) \n * HSMs on exporting and importing machines must share internal key-wrapping keys (see hsm-clone-kwk command). A key-wrapping key is a key that encrypts another key.\n\n\nEach HSM has a special key inside of it, the key-wrapping key, that is used to encrypt exported private keys (and to decrypt imported private keys). If the goal is to restore exported keys to the same appliance, then you don't need to worry about hsm-clone-kwk, red keys, or the hsm-domain parameter. That is because the key-wrapping key at import time will already match the key-wrapping key at export time (since the HSM device is the same). If the goal is to move exported keys from one appliance to another one, then all of the steps in this section must be followed :- \n\nFirst, the two HSMs in question must be both be initialized and in the same key sharing domain. This means that they must both be initialized in the same mode (both in Security Level 2 or both in Security Level 3). In Security Level 2 mode, they must have used the same hsm-domain parameter during hsm-reinit (this parameter has a default value that is the same on all appliances). In Security Level 3 mode, they must have used the same red PED key during hsm-reinit (and the second initialization must not have overwritten the key value from the first initialization). \n\nSecond, the key to be exported must be exportable. The exportability of keys is immutable. It is determined at keygen time, and it is controlled by that command's exportable parameter. If a key was created outside of the appliance (not using keygen), then it is always considered exportable. \n\nFinally, before the crypto-export crypto-import sequence, the key-wrapping keys must be synchronized using the hsm-clone-kwk command. This command must be run four times: once on the source HSM appliance (with the key-wrapping key you are copying), once on the destination HSM appliance, once again on the source HSM appliance, and once again on the destination HSM appliance. Each time the command is run, it will need the output file from the previous step (as the input to the current step) which must be moved manually (usually with the copy command). \n\nOnce all of this has been done, then private keys may move from system to system with crypto-export and crypto-import. \n\nNote that the non-HSM appliance can export keys immediately at keygen time, but never at a later time. \n\nFor additional information refer to the online Info Center [http:\/\/publib.boulder.ibm.com\/infocenter\/wsdatap\/v3r8m2\/index.jsp?topic=%2Fxi50%2Fwelcome.htm] and search for \"PIN entry device\".\n\nNote: You will need to sign into the documentation portal with your IBM Registration ID and password."}]},{"id":"DEV_Q303","question":"Why are the users unable to login to Web GUI 8.1 after I modify timeout to 2147483647 in security.xml file ?\n\n\n\nI followed the Web GUI 8.1 reference guide here to switching off the session timeout\n\nhttp:\/\/www-01.ibm.com\/support\/knowledgecenter\/SSSHTQ_8.1.0\/com.ibm.netcool_OMNIbus.doc_8.1.0\/webtop\/wip\/task\/web_adm_settimeout.html\n\nAfter I edited \/config\/cells\/JazzSMNode01Cell\/security.xml file, modified timeout setting to 2147483647, users are not able to login anymore.","answer":"1. On DASH server, navigate to <JazzSM Home>\/profile\/config\/cells\/JazzSMNode01Cell\/applications\/isc.ear\/deployments\/isc\/isclite.war\/WEB-INF\n\n\n2. Take a backup of consoleProperties.xml\n\n\n3. Open consoleProperties.xml in edit-mode.\n\n\n4. Search for \"LTPAFIX\" and change the value from \"true\" to \"false\".","is_impossible":false,"contexts":[{"filename":"swg21690658.txt","text":"Title: IBM Setting a big session time-out value in DASH causes session lock-out - United States\n\nText:\nDASHL2; session; time-out; timeout; cannot login; locked out ; 2147483647; security.xml TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Using a big value (2147483647) for the session timeout setting in DASH, to achieve the maximum time between timeouts, is causing users to be locked out completely. \n\nSYMPTOM\nAfter entering the user ID and password in the login page, and then pressing the \"continue\" button,\nthe login page does not change, stuck at \"processing\" and then returns to the login page again.\" \n\nAll users get essentially locked out completely from DASH sessions.\n\n\nCAUSE\nIn order to maximize the time between session timeouts, the customer is setting the timeout parameter in the security.xml file to 2147483647.\n\nThis timeout parameter used in the security.xml file is a WAS setting, but DASH is using a javascript call (settimeout), which causes a condition that prevents a login, if the timeout value is really big. \n\n\nNote: 2147483647 is the maximum positive value for a 32-bit signed binary integer in computing.\n\n\nRESOLVING THE PROBLEM\nThis condition that prevents logins can be averted by setting the custom property LTPAFIX in the consoleProperties.xml to \"false\". \n\n\nPlease follow this steps: \n\n1. On DASH server, navigate to <JazzSM Home>\/profile\/config\/cells\/JazzSMNode01Cell\/applications\/isc.ear\/deployments\/isc\/isclite.war\/WEB-INF \n\n \n2. Take a backup of consoleProperties.xml \n\n \n3. Open consoleProperties.xml in edit-mode. \n\n \n4. Search for \"LTPAFIX\" and change the value from \"true\" to \"false\". \n\n\nExample: \n\nBefore \n===== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"true\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\nAfter \n==== \n<consoleproperties:console-property id=\"LTPAFIX\" value=\"false\"\/> \n<\/consoleproperties:ibm-portal-consoleproperties> \n\n5. Save the file. \n\n \n6. Restart DASH server."}]},{"id":"DEV_Q304","question":"Does IBM DataPower Gateway Appliance support the HTTP CONNECT method?\n\nDoes IBM DataPower Gateway Appliance support the HTTP CONNECT method for SSL proxy requests? ","answer":"SSL 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.","is_impossible":false,"contexts":[{"filename":"swg21612222.txt","text":"Title: IBM How to Proxy SSL request from DataPower to Remote Proxy Server? - United States\n\nText:\nForward 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."}]},{"id":"DEV_Q305","question":"Cognos Analytics - Images not displayed in PDF\/Excel, working in HTML\n\nI've just completed an upgrade to Cognos Analytics 11.0.3. When running existing reports in HTML, the images are displayed but when I try to run them in PDF\/Excel they are not. ","answer":"Open up IIS 7.5 \n 2. Click on the root folder of your Cognos installation (E.g. C1021GA) in the navigation pane on the left side \n 3. When the root folder is selected, double-click 'Authentication' \n 4. Ensure that anonymous access is enabled \n 5. Repeat steps 3 and 4 for the image folder and it's parent folder. \n 6. If the user is concerned about security, they may want to restrict the child-folders (E.g. cgi-bin) and change the authentication settings accordingly \n 7. Run the report in export as Excel 2007 and PDF","is_impossible":false,"contexts":[{"filename":"swg21656263.txt","text":"Title: IBM How to troubleshoot images not appearing in PDF\/Excel in Report Studio - United States\n\nText:\n TECHNOTE (TROUBLESHOOTING)\n\nPROBLEM(ABSTRACT)\n Unable to view images in reports in PDF\/Excel output when using Report Studio\/Workspace. \nHowever images are visible in HTML format when reports are run actively. \n\nSYMPTOM\nUnable to view images in reports in PDF\/Excel output when using Report Studio\/Workspace. \nHowever images are visible in HTML format when reports are run actively.\n\nThe PDF\/Excel outputs will have a placeholder image. This will be in the form of an empty black box (PDF) or will be a missing pictures icon (Excel).\n\n\nCAUSE\nThere are a few common causes for this issue: \n\n 1. The permissions of the folder which contains the image, have not been configured correctly \n 2. The image is not within the directory which is specified \n 3. The directory where the image is meant to be stored, does not exist in the specified location\n\nDIAGNOSING THE PROBLEM\nTo find out the root cause of this problem, you will need to use tools that monitor and record all actions attempted against the Operating System Registry. \n\nIn THIS scenario the tool used was Process Monitor and the Web Server was IIS 7.5. \n\n \n\n 1. Download Process Monitor tool (Make sure you run it from the same machine Cognos is installed on) \n 2. Open up the report in Cognos Workspace \n 3. Load up Process Monitor \n 4. You will notice the current processes immediately being captured and displaying in the window. Press the Capture \/ Ctrl+E Icon (Magnifying Glass) to stop the capture of events. \n 5. Press the Clear \/ Ctrl+X icon (Eraser) to remove all the recorded entries. \n 6. Press the capture icon in process monitor \n 7. Export the report to Excel 2007\/PDF \n 8. Save the file anywhere \n 9. Press the Capture icon again in process monitor to stop the capturing of events. \n 10. Press the Find Icon \/ Ctrl+F and type \"[Image Name]\" to make sure the filter image event was captured. \n 11. You should be able to see the reason why the image could not be saved under the 'Result' column.\n\n\nRESOLVING THE PROBLEM\nIf the image is found but cannot be accessed due to permission configuration issue: \n\n \n\n 1. Open up IIS 7.5 \n 2. Click on the root folder of your Cognos installation (E.g. C1021GA) in the navigation pane on the left side \n 3. When the root folder is selected, double-click 'Authentication' \n 4. Ensure that anonymous access is enabled \n 5. Repeat steps 3 and 4 for the image folder and it's parent folder. \n 6. If the user is concerned about security, they may want to restrict the child-folders (E.g. cgi-bin) and change the authentication settings accordingly \n 7. Run the report in export as Excel 2007 and PDF\n\n\nIf the image\/ directory is not located: \n\nPlace the image\/directory in the specified location \n\n\n\nCross reference information Segment Product Component Platform Version Edition Business Analytics Cognos Business Intelligence Cognos Workspace Windows 10.2.1, 10.2"}]},{"id":"DEV_Q306","question":"Unable to view batches in DotEdit\n\n\n\nHi all,\n\nIs there any limitation to view batches in Dot Edit client application, because I am unable to see batches with QID more than 1119.\n\nAlso unable to see batches with status as \"Pending\". \n","answer":"Backup the \\Datacap\\DotEdit\\apps.ini file. If the file does not exist, create a new one or copy it from \\Datacap\\tmweb.net. \n 2. Open it in notepad.exe or other editor. \n 3. Find the app to be modified (for example [APT]). If it does not exist, create a new section with the application name listed between square brackets. \n 4. Add a new line containing BatchLimit=xxx, where xxx is the number of batches to be displayed. \n 5. Save the file.","is_impossible":false,"contexts":[{"filename":"swg21642839.txt","text":"Title: IBM How do I adjust the number of batches that DotEdit displays in IBM Datacap Taskmaster Capture? - United States\n\nText:\nbatch; list TECHNOTE (FAQ)\n\nQUESTION\n I want to increase the number of batches that IBM Datacap DotEdit displays. It only displays 100 and there are more than 100 batches available. What needs to be done to increase the list? \n\nCAUSE\nThe default limit is 100 rows, but this number can be modified by editing the file \\Datacap\\DotEdit\\apps.ini file.\n\nANSWER\nPlease do the following: \n\n 1. Backup the \\Datacap\\DotEdit\\apps.ini file. If the file does not exist, create a new one or copy it from \\Datacap\\tmweb.net. \n 2. Open it in notepad.exe or other editor. \n 3. Find the app to be modified (for example [APT]). If it does not exist, create a new section with the application name listed between square brackets. \n 4. Add a new line containing BatchLimit=xxx, where xxx is the number of batches to be displayed. \n 5. Save the file.\n\n\nAdditional information: \n * For version 8.1, Fix Pack 1 or newer must be installed. \n * Increasing the number of batches displayed is known to cause a slowdown in perceived response time due to gathering and formatting of the batch list. \n * The optimum number will vary due to system conditions, infrastructure and user expectation. \n * The DotEdit batch list will be slower to display than the batch list in Taskmaster Web, due to architectural differences between the applications."}]},{"id":"DEV_Q307","question":"Help with Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735)\n\nI need to understand details regarding Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 for HP NonStop Server (CVE-2017-3735). What versions of the product are affected?","answer":"All versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server","is_impossible":false,"contexts":[{"filename":"swg22014367.txt","text":"Title: IBM Security Bulletin: Vulnerabilities in OpenSSL affect WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server (CVE-2017-3735) - United States\n\nText:\n SECURITY BULLETIN\n\nSUMMARY\n IBM WebSphere MQ 5.3 and IBM MQ 8 for HPE NonStop have addressed a vulnerability in which OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate \n\nVULNERABILITY DETAILS\nCVEID: CVE-2017-3735 [http:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2017-3735]\nDESCRIPTION: OpenSSL could allow a remote attacker to obtain sensitive information, caused by an error while parsing an IPAddressFamily extension in an X.509 certificate. An attacker could exploit this vulnerability to trigger an out-of-bounds read, resulting in an incorrect text display of the certificate.\nCVSS Base Score: 4.3\nCVSS Temporal Score: See https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047 [https:\/\/exchange.xforce.ibmcloud.com\/vulnerabilities\/131047] for the current score\nCVSS Environmental Score*: Undefined\nCVSS Vector: (CVSS:3.0\/AV:N\/AC:L\/PR:N\/UI:R\/S:U\/C:L\/I:N\/A:N) \n\nAFFECTED PRODUCTS AND VERSIONS\nAll versions of WebSphere MQ 5.3 and MQ 8 for HPE NonStop Server\n\nREMEDIATION\/FIXES\nFor MQ 5.3 \n\n * \n * \n * \n * \n * \n * \n * \n * \n * \n * https:\/\/www-945.ibm.com\/support\/fixcentral\/swg\/selectFixes?parent=ibm%7EWebSphere&product=ibm\/WebSphere\/WebSphere+MQ&release=5.3.1.14&platform=HP+NonStop&function=all\n * \n\nFor MQ 8 \n * \n\n * \n * here\n * \n\nWORKAROUNDS AND MITIGATIONS\nNone\n\nGET NOTIFIED ABOUT FUTURE SECURITY BULLETINS\n Subscribe to My Notifications [ http:\/\/www-01.ibm.com\/software\/support\/einfo.html] to be notified of important product support alerts like this. \n\nREFERENCES\nComplete CVSS v3 Guide [http:\/\/www.first.org\/cvss\/user-guide] \nOn-line Calculator v3 [http:\/\/www.first.org\/cvss\/calculator\/3.0] \n\nRELATED INFORMATION\nIBM Secure Engineering Web Portal [http:\/\/www.ibm.com\/security\/secure-engineering\/bulletins.html] \nIBM Product Security Incident Response Blog [http:\/\/www.ibm.com\/blogs\/psirt] \n\n*The CVSS Environment Score is customer environment specific and will ultimately impact the Overall CVSS Score. Customers can evaluate the impact of this vulnerability in their environments by accessing the links in the Reference section of this Security Bulletin. \n\nDISCLAIMER\nAccording to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an \"industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response.\" IBM PROVIDES THE CVSS SCORES \"AS IS\" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY."}]},{"id":"DEV_Q308","question":"Suppose I can well describe my problem and my symptoms - what is the best way to find a matching solution or a known code fix (APAR)?\n\nSuppose I can well describe my problem and my symptoms - what is the best way to find a matching solution or a known code fix (APAR), in particular if I want to void opening a PMR.","answer":"-","is_impossible":true,"contexts":[]},{"id":"DEV_Q309","question":"Help with Security Bulletin: Vulnerability in Diffie-Hellman ciphers known as Logjam affects WMB & IIB (CVE-2015-4000)\n\nI need to understand details regarding Security Bulletin: Vulnerability in Diffie-Hellman ciphers known as Logjam affects IBM WebSphere Message Broker and IBM Integration Bus (CVE-2015-4000). This vulnerability is commonly referred to as \"Logjam\". Where can I find this information?","answer":"-","is_impossible":true,"contexts":[]}]